What Connections are Required to Build Clean Datasets for Useful AI Actions?
Artificial intelligence is the buzz of buzz words, but like practically everything else in the hotel technology world, it's hardly simple.
Notably, in the era of 'data is the new oil', companies are often forgetting the other caveat emptor catchphrase of, 'Garbage in, garbage out' (abbreviated as GIGO) that has been discussed in the latest HN Thematics with Shiji Group.
Because machines learn from correlation derived from massive data sets, incomplete or inaccurate databases can misinform an algorithm, produce negligible returns on the investment or, worst of all, result in jumbled personalization attempts that lead to service errors. It follows that a critical first step to having your data flow like black gold is to ensure you have the right plumbing hookups - integrations, interfaces, EDIs, APIs and so on.
And yet, there's a third classical adage that enters the picture here courtesy of Voltaire: 'Perfect is the enemy of the good enough'. In a modern sensibility, one might interpret this quote as, 'Move fast and break things'. And yet, as a cautionary tale, we are well aware of what happens when a tech company moves too fast and breaks one too many things (read: Cambridge Analytica).
There has to be an equilibrium between implementing now versus waiting for the perfect timing to do so. Hence, this balancing act between realizing the lucrative prospects of AI right now and avoiding GIGO-esque situations raises the questions: Which data connections are absolutely essential in order to build 'good enough' datasets for agentic AI to act upon? For each interface identified, why is it essential and what AI use cases can be realized from having unified, structured data amongst these systems?