Built For The Cloud: A Blueprint For Hotel Technology Success

Why Upgrading to True Cloud Hotel Technology is a No-Brainer for Many Hoteliers

Starfleet Research

According to the new groundbreaking report 'Built for the Cloud: A Blueprint for Hotel Technology Success' (currently available for complimentary download), hoteliers are upgrading to next-generation cloud solutions in record numbers. 

Today nobody questions the cost savings that come from streamlining operations across all hotel functions and all parts of the property (or properties). By now, everyone can agree that having a cloud PMS is a prerequisite to improving guest satisfaction, speeding guest services — from check-in and housekeeping to concierge and maintenance response times — and enabling guest-facing interfaces, including self-service options. 

Hoteliers know that only by harnessing the power of data and analytics — core features of a cloud PMS — can they present guests with relevant and personalized offers, messages and treatments, further engendering satisfaction and loyalty.

Infographic from Built for the Cloud: A Blueprint for Hotel Technology Success

But buyer beware: Not all cloud solutions billed as "next-generation" are worthy of that description. For that matter, not all cloud solutions are even truly cloud solutions. Fact is, some legacy on-premise solution providers, eager to jump on the cloud PMS bandwagon, engaged in what is commonly known as "cloud-washing."

Even today, solutions billed as cloud-based may not, in fact, be true cloud solutions. It is important to understand the difference between a "true cloud solution" and a "fake cloud solution."

Whereas the latter is built on software originally designed to run on-premise, a true cloud solution is built from the ground up, coded to perform as a fully-hosted cloud solution and optimized for tablet and mobile use. The solution provider hosts the solution across hundreds of servers and with multiple levels of data redundancy in a multi-tenant "pure cloud' environment. Customers typically access the same solution via an internet browser, allowing for instantaneous product upgrades.

A customization platform maintains property-specific changes following these software upgrades so that customers can gain immediate access to the latest functionality without having to re-implement custom changes and integrations.

Cloud-based solutions are not, in fact, always based in the cloud. Some of the dominant PMS legacy solutions that are currently in place across Europe, North America and Asia have been merely upgraded with a web front-end interface. The interface provides access via an internet browser on a computer, tablet or mobile device to the back-end software, which remains hosted on a local, on premise server.

Infographic from Built for the Cloud: A Blueprint for Hotel Technology Success

This type of cloud-based hospitality software, in which certain critical elements continue to reside on-premise — including, in many cases, the actual database housing the guest data — are known as hybrid cloud solutions. A web-native "true cloud" solution, on the other hand, is hosted on shared application servers in a public cloud environment and has the advantage of being more agile, flexible and open to multi-tenancy.

Another advantage relates to software release updates. With a true cloud solution, these upgrades are more seamlessly and frequently deployed and also included as part of the cost.

With respect to system upgrades, the shift from on-premise installation to cloud-based deployment have caused hoteliers to pay close attention to service level agreements and up-time guarantees. This is no surprise given that the PMS handles virtually all operations, including guest-facing service functions. Hotels that experience technology performance issues generally pay a dear price.

In the past, these issues have tended to arise most often during, or immediately following, system upgrades of on-premise, client-server software. Regardless of how much time and effort may have gone into quality assurance testing, new releases of hospitality applications with monolithic feature-laden code were bound to have performance issues. The problem was oftentimes related to the difficulty of simulating a hotel's customized software configuration, including the specific data streams that flowed into the PMS.

To help reduce potential performance issues related to system upgrades, solution providers would commonly implement user acceptance testing processes. This meant creating a copy of the production database and installing an advance copy of the new software release on the hotel's servers. Hotel staff would rigorously test the new system, trying to identify defects and reporting any bugs or performance shortcomings.

A benefit to this approach, in addition to reducing the risk of calamity, was that hotel staff could familiarize themselves with new interface as well as features and functionality prior to going live. Software fixes would be either installed as patches or incorporated into a new release, which, typically, would then be reinstalled and retested. The trial run process continued until all issues were resolved and the software was deemed to be relatively free of defects.

The software upgrade process for a true cloud PMS is very different. In sharp contrast to the process involving legacy systems and even, to a lesser degree, hybrid cloud solutions, this process tends to be largely hassle- and worry-free for hoteliers, who, in past, were often held partially responsible for any performance hiccups. With single-version development, all hotel customers are upgraded simultaneously, putting the onus on the solution provider to ensure that the software is delivered with unfaltering quality and performs in an error-free manner. It’s a far cry from the trials and tribulations of software upgrades of the past that many hoteliers remember all too well.

Note: “Built for the Cloud: A Blueprint for Hotel Technology Success” is now available for complimentary download. Click here to learn more and to download a free copy.



Logos, product and company names mentioned are the property of their respective owners.