The Hotel PMS (Property Management System) is the core system for hotel operations, managing key business data such as guest accommodations, tenants, bookings, cashiers, and house-states. The WiFi certification system interfaces with the PMS system, which allows WiFi to be no longer an isolated technology link but rather integrated into the depth of hotel business processes, achieving advanced functions like building number recognition, checkout network, differential services, data connection, etc.
Why do you have to connect with PMS?
Without matching PMS, the hotel WiFi certification system is run independently: the occupants are online via cell phone numbers or micro-credit certifications, the system does not know which room the guests live in, what members are and when to leave their homes, and WiFi services are completely out of touch with the hotel business processes. While this model can meet basic access needs, there are limitations: one is that a house number certification cannot be achieved, the tenants need mobile phone numbers or micro-letter information, and privacy is poor and cumbersome; The second is that there is no automatic out-of-house break-out, and the endpoint may continue to use WiFi if it remains within WiFi coverage (e.g. waiting for a taxi in the lobby), occupying bandwidth resources and having security concerns; the third is that differential services cannot be provided, and the system does not know about tenants ' type, membership level, number of days of stay, etc., and does not provide higher bandwidth and exclusive service to VIP members or administrative floor occupants; and the fourth is that data isolated island, WiFi system residents ' online data cannot be linked to PMS ' s residential information and cannot be analysed across systems and client drawings constructed. These problems can be resolved by docking with PMS: WiFi certification system provides real-time access to residential information, supports home number + family name certification, automatic out-of-house breakout, differential bandwidth and services according to type and size of dwelling, and in-depth analysis of WiFi data for online connection to guest information. For hotels, PMS is not connected to the host information."The flowers are in the top."The interface of PMS has become a basic requirement for the WiFi system, especially for mid-end hotels and chaining groups.
Technical approach to docking
The interface between the WiFi and PMS of hotels is based on several technical ways: first, an API interface, which is the most common and recommended approach. PMS provides a RESTful API or SOAP API interface where WiFi certification systems can access resident information (e.g., checking the name and residence status of the guest according to room number), receiving notice of changes in housing (e.g. occupancy, exit, change of premises). The advantages of API docking are real-time good, accurate data, flexible functionality, and two-way data synchronization; The disadvantage is that PMS manufacturers are required to provide an open API interface, with different PMS API protocols and data formats and a certain amount of work on docking development. Second, the database link, where WiFi certification systems directly access PMS databases (e.g. MySQL, SQL Server, Oracle etc.) and search for residential information and housing-state data. The advantage of this approach is that PMS manufacturers do not need API, which can be connected as easily as they have database access; The disadvantage is that direct reading of the database may affect PMS performance and changes in the structure of the database table can lead to a loss of interfaces, security is not as good as an API interface (data access rights need to be granted). Third, intermediate docking, which allows data exchange between WiFi and PMS through an intermediary system (e.g. hotel interface gateway, ESB enterprise service bus), intermediated items are responsible for protocol conversion, data mapping, message router etc. This approach is appropriate for multiple systems and complex inter-system interface large hotel groups, with the advantage of untraceing direct inter-system reliance to facilitate expansion and maintenance; and the disadvantage is increasing deployment and maintenance costs of intermediated items. The fourth is file transfer docking, where PMS regularly exports residential information and housing data to files (e.g. CSV, XML, JSON formatting), transmits them to the WiFi authentication system via FTP or shared folders, systematically updates local data after reading the files. This approach is simple, but it is not real-time (with delay in updating data) and only suits scenarios that are less demanding for real-time use. In practical applications, the API interface is mainstream and most of the mainstream PMS systems (e.g., mid-soft, west soft, Fidelio/Opera, stone-based, green cloud, different red) provide open API interfaces, which WiFi certification system manufacturers usually pre-connect to these mainstream PMSs, form standardized docking plugins, and the hotel will need only to have PMS interface addresses and account codes to complete the interface when deployed and not be customized for development.
Retrieval core business functions
WiFi certification system interfaces with PMS to achieve the following core business functions: first, room number + family name certification, guest entering room number and registration on Portal page, and WiFi interface to verify whether the room is validly occupied, that the residence name matches, and that it is released online after verification. This does not require a resident to provide cell phone numbers or micro-mail messages, privacy, simple operation, and the most popular way of certifying middle- and high-end hotels. Second, checkout automatic, when a room in PMS becomes a state."Checked out."The PMS informs WiFi via an interface that all terminal authentication sessions in the room are automatically terminated by WiFi, restored to uncertified status and prevented from returning to WiFi. Third, when a guest is admitted to the facility, PMS transmits the incoming information to WiFi, which can be pre-serviced for the room and even prepositioned with bandwidth and privileges based on the client ' s rank of membership and preferences. The guest can enter the room to connect to WiFi and then go directly online (exact or one key certification) and enhance the experience. Four are differential bandwidth and services, which automatically distribute differentiated bandwidth and privileges based on the information provided by PMS about tenants (room type, membership level, house price, occupancy number, etc.), such as 100 Mbps bandwidth for administrative floors and suite tenants, 20 Mbps bandwidth for regular tenants, additional bandwidth addition to VIP members and exclusive Portal pages. Five are billing links, and for WiFi services that charge fees on the basis of usage (e.g. high-end hotel ' s high-speed WiFi payment service), WiFi can synchronize user WiFi usage costs to PMS room bills, and customers leave their homes in a single settlement without having to pay separately for WiFi. Six are data association analyses, which link occupants ' online behavioral data (wifding time, traffic use, application preferences, access areas, etc.) with PMS 's residential information (room type, membership class, source channel, consumption amount), and provide deep client portraits and behavioural analysis that provides data support for hotel service optimization and marketing strategies. For example, WiFi, a user of different house-type customers, is analysed to optimize bandwidth distribution; the difference between members and non-members in their behaviour on the Internet is analysed and more targeted membership rights are developed.
Implementation points for the interface
The interface between WiFi certification system and PMS is a prudent project, with the following key implementation points: first, to confirm PMS interface capabilities, and before start of the project, to confirm with hotel PMS that PMS provides an open API interface, functional scope of the interface (whether resident queries are supported, home-state transfers, bill synchronization etc.), protocol and data formats for interfaces, frequency limits for interfaces and performance indicators. If PMS does not provide API, alternative means such as database direct connection or file transfer need to be assessed. second, network connectivity, WiFi authentication systems need access to PMS interface addresses. If PMS is deployed in the local hotel area network and WiFi is locally, both can communicate directly; if PMS is deployed on cloud ends (e.g., cloud PMS), WiFi needs to access cloud PMS API via Internet and needs to ensure stability and security of Internet connectivity (advised encryption using VPN or HTTPS). Third, data security, where the PMS contains personal information of a resident (name, cell number, identity card number, credit card information, etc.), is sensitive and data transfers between WiFi and PMS must be encrypted (HTTPS/TLS), data storage must be encrypted and access rights strictly controlled. The WiFi system should only acquire the minimum data set required for authentication (e.g. room number, residence name, occupancy status), complete personal information of a resident should not be obtained and stored, let alone used for purposes unrelated to WiFi certification. Fourth, error and downgrading, the PMS interface may be temporarily out of service due to network failures, PMS system maintenance, interface limit flow, etc. WiFi requires fault tolerance and downscaling mechanisms: when PMS interface is not available, the system can automatically switch to alternative authentication (e.g. mobile phone number authentication) to ensure that occupants remain able to access the Internet while recording and alerting failure logs; and when PMS interface is restored, it automatically returns to normal mode. Fifthly, testing and verification is completed with adequate tests including: the proper house number (correct home + family name, wrong house number, incorrect surname, returned house number, unoccupied room number, etc.), the check-out network test (checking whether terminal was downline after checking out), the occupancy opening test (checking WiFi automatically when checked in), differential bandwidth test (right distribution of bandwidth between different types of dwelling and membership grades), the interface abnormality test (mocking down behaviour when PMS interface is not available), performance test (response time and system stability for interfaces under high clearance request). Sixth is documentation and training, which, when completed, requires detailed docking documents (interface description, configuration parameters, fault check guidelines, etc.), training of hotel IT personnel and front desk staff to ensure that they are aware of the business processes and basic downtime methods after the interface.
Connectivity features of common PMS systems
The different brands of PMS have features in interface capabilities and interface patterns, and understanding these characteristics will help to better plan the docking programme. SMS (CSTC): has a high rate of ownership of the domestic high-end hotel market, provides a more sophisticated API interface, supports residential queries, home delivery, bill synchronization functions, etc. The interface protocol is dominated by WebService/SOAP, with relatively good documentation. SMS (Foxhis) is widely used in the domestic hotel market, offers both an API interface and a database view that is fully functional and a database view suitable for simple guest search scenarios. Stone-based PMS (Shiji): A large domestic hotel group is commonly used, has a full interface platform (Shiji Conect), supports interface with multiple third party systems and has a high degree of standardization but relatively formal interface processes that require application and configuration through the stone-based interface platform. Fedelo/Opera (Oracle): The international high-end hotel brand is commonly used, powerful but complex interfaces, usually require docking through Oracle ' s OPRA Cloud API or OHIP, which is more expensive to connect and suitable for international brand hotels. Green cloud PMS: representative of Cloud PMS provides RESTful API interfaces, modern interface design, clear documentation, relatively simple matching, small and medium hotels and fine hotels. Other examples of the PMS: Another mainstream cloud PMS provides an open API platform that supports multiple interfaces such as guests, housing and billings, which are easily docked to fit hotels and economic hotels. In practical projects, WiFi certification system manufacturers usually pre-interact the market-mainstreamed PMS systems, creating standardized match-to-link plugins and configuration templates, and when a hotel is deployed it can be connected only by selecting its equivalent PMS brand, filling in interface addresses and account codes, significantly reducing technical thresholds and implementation costs. For non-mainstream or customized PMS systems, custom development is required, with corresponding increases in the interface cycle and cost. In selecting a model, hotels should give priority to the WiFi certification system that has completed pre-connection with their own PMSs in order to reduce project risks and implementation costs.
The interface between the WiFi certification system and PMS is a key step in integrating WiFi services into hotel business processes. After this, the integration will be achieved through technical means such as API interfaces, database connectivity, intermediates, etc., the system can support advanced features such as house number recognition, out-of-bernet, access, differential services, bill linkage, data analysis, etc. and significantly improves the client experience and hotel operations. For hotels, PMS interfaces are not optional but rather a necessary condition for the WiFi system to be truly valuable, especially in the context of the deepening digitalization of the hotel industry, inter-system connectivity and data sharing will be an important basis for enhancing the core competitiveness of hotels.