Many existing legacy technology installments in hospitality are closed systems they are reluctant to open up to third-party integrations, applications and solutions, depriving the property and its guests from some very innovative and much-needed applications and services.

In the near to mid-term, any full-service 3-4-5-star hotel will need over 100 plus APIs (application programming interface) with third-party tech applications and solutions to be able to function and meet the basic needs and wants of today's tech-savvy travelers. These include mobile and contactless guest experience, mobile locks, issue resolution apps, guest messaging, virtual concierge, IoT devices and utility management, smart room technology, entertainment hubs, CRM programs, etc.

Until recently, this type of connectivity has been close to impossible or super expensive to achieve for properties with legacy technology installments of PMS,RMS, CRS, CRM and other components of the tech stack, which are hostile to any third-party interfaces by default.

Luckily for our industry, the future is already here in the form of two types of third-party technology integration platforms:

  • Cloud PMS with Open API like Opera Cloud PMS, StayNTouch, Protel, CloudBeds, Mews, etc. and their integration platforms, and
  • Independent integration hubs, like Impala, Hapi, APS, NoniusHub, etc., which are focusing on serving properties with existing legacy tech stack.

The question is, can the new integration hubs save our legacy tech-prone industry and elevate it to meet the demands of today's tech-savvy travelers?

Whilst I completely agree with the description of the problem, I take issue with the solutions offered by the author as being both simplistic and incomplete. 

TigerTMS (I feel I may refer to my company as the author has referenced several others) has been developing interface software for over 40 years - thousands of hotel properties worldwide use our software because it provides the middleware between disparate applications. An "Open API" is still a proprietary API that, whilst enabling connectivity to multiple other solutions, also re-enforces the PMS position at the centre of the software stack. Better to employ a middleware layer that allows hoteliers the freedom of choice to pick and choose best of breed applications with one single connection to the PMS not several.

Second, there is a distinct difference between types of "independent integration hubs" aka middleware. The purpose of many is to collect information from hotel systems and re-present this back to the hotelier in the form of a control panel, thereby optimising operational efficiencies. Others however - such as ours - are real-time, bi-directional interfaces that, put simply, make things work. The software oil that lubricates the machine. 

So the answer to the question posed is "Yes" - but first let's get a thorough understanding of the different options together with their implications. 

View all 15 views in this viewpoint