Solutions overview — HMS EE, HospitalityPro HR, CloudTV and ContactPro+
What each application does, a suggested architecture for a hotel or a group, the benefits of running them together, integrations with PMS, POS, CRM, accounting and TV screens, and answers to common questions
هذا المحتوى متاح بالإنجليزية والفرنسية والإسبانية.
The PANGEA application family gives a hotel or a hotel group four applications that each work alone and that link to each other when the hotel wants: HMS Entreprise Edition (HMS EE) for accounting, management and analytics, HospitalityPro HR for the staff, CloudTV for every screen of the property (room TVs, kiosks, digital signage) and ContactPro+ for business contacts and leads.
Run together, they share one rule: HMS EE is the accounting system of record and the only application that talks to the hotel's OPERA PMS and MICROS Simphony POS. The other applications send their documents and requests to HMS EE through signed, idempotent, retried links (hms-link/1.0, hr-sync/1.0) and receive back the results. Local work never waits for the other side.
HMS Entreprise Edition
Accounting, workforce, analytics, front-office link to OPERA and MICROS, central console
HospitalityPro HR
Planning, time clock, leave, people, payroll preparation
CloudTV
Digital signage and hotel TV: welcome, channels, services, phone remote
ContactPro+
Digital business cards, lead capture, contacts and CRM sync
The four applications and their links
| Link | Between | What travels | Status |
|---|---|---|---|
| hms-link/1.0 | HMS EE ↔ CloudTV | Customers and plan periods to accounting; for the hotel TV: rooms, stays (guest, language, group, agenda), requests (room status, DND, maintenance, department tasks, 911, postings, room moves), results, feed health, live bill | Built |
| hms-link/1.0 | HMS EE ↔ ContactPro+ | Customers and documents to accounting; reference data and posting results back | Built |
| hr-sync/1.0 | HMS EE ↔ HospitalityPro HR | Organisation, employees, contracts, shifts, leave, punches, advances, loans, pay periods, payroll entries, payouts | Built |
| Screen channels | HMS EE → CloudTV | Dashboards, announcements, corporate content (switch off by default) | Built |
| Screen channels | HospitalityPro HR → CloudTV | Posts marked "show on screens", birthdays (first names), awards, open positions | Built |
| Revenue feed | HMS EE → HospitalityPro HR | Daily revenue and occupancy for labour ratios and staffing | Built |
| Cameras | HikCentral → HMS EE → CloudTV | Short-lived live addresses for a screen; CloudTV holds no camera credential (separate switch, off by default) | Built |
| tasks-sync/1.0 | Any two of HMS EE, HR, CloudTV, Vwayaj | Tasks of shared projects, with roles, never people | Built HR, CloudTV, Vwayaj · In build HMS EE |
| Licensing API | Hub ↔ each PANGEA installation | Packages, modules, units, status, usage | In build |
Every link is paired with a single-use code valid 30 minutes (HML1., HRS1., TSK1.), signed, idempotent (each event applied once), retried (10 s, 1 min, 5 min, 30 min, 2 h, then every 6 h) and reconciled; secrets are stored encrypted.
How a guest request flows
Standalone or integrated
| Mode | What runs | When it fits |
|---|---|---|
| Each application alone | Every application is complete without the others; links are optional | A hotel that needs only signage, only HR, or only accounting |
| CloudTV standalone (no PMS, no POS) | Stays by hand or by rooming-list import (CSV/XLSX or an OPERA arrivals export); requests handled in CloudTV; no bill shown to guests | Hotels without OPERA/Simphony, or while the links are being set up |
| CloudTV "With HMS EE" | Rooms and stays from OPERA via HMS EE; requests to OPERA/Simphony; live bill when the feed is live | Hotels on OPERA (Cloud or 5) and/or Simphony |
| Full suite | HMS EE + HR + CloudTV + ContactPro+ linked | Groups that want one flow from guest and staff to accounting |
The account mode setting (Standalone / With HMS EE) in CloudTV is In build; switching later keeps all data, and stays made by hand are merged with OPERA's reservations when the link comes back.
Results and benefits together
The benefits below follow from features that exist; no figure is promised. Their size depends on the hotel: its systems, its data quality, its staff's adoption and its processes.
| Area | Benefit when the applications run together | Features behind it | Depends on |
|---|---|---|---|
| Operations | One record per request, from the room TV to the department's task board and to OPERA or Simphony, with status in sync both ways; nothing lost when a link is down | hms-link requests, HMS EE task boards, retries, "To enter by hand" list, CloudTV offline queue | OPERA/Simphony interfaces live; departments set up |
| Guest experience | Personal welcome in the guest's language, phone as remote without installation, services and room service from the TV, wake-up alarms, messages, a bill that respects OPERA's Print Rate | CloudTV hotel TV, stay feed from HMS EE, live bill rules | TV models and network; OPERA data quality |
| Revenue and upsell | Ordering made easy on every TV and phone; charges posted by item mapping; advert overlays with proof of ad for advertisers | Services, orders, item mapping, adverts and BI campaign reports | The hotel's offer and prices; guest use |
| Staff efficiency | Staff data entered once in HR and shared with accounting; planning driven by revenue and occupancy; requests routed to the right department; HR news on staff screens | hr-sync, revenue feed, planning and time clock, HR channels, tasks | Adoption by managers; HR set-up |
| Accounting accuracy | Documents posted once, by their owner, with posting results returned; nightly reconciliation of the links; daily PMS/POS import; bank reconciliation | HMS EE ledger, hms-link idempotency and reconciliation, connectors | Chart of accounts and mappings |
| Compliance and control | Who did what and when in every application; secrets encrypted; backups every night; documents archived once; local labour rules and privacy texts | Activity log (hash chain), 2FA, daily backup 00:01, Paperless-ngx, HR labour rules, legal pages | Hotel's own policies; legal review where marked |
| Sales and relations | Business contacts captured from cards and scans, synced to the CRM, linked to accounting customers | ContactPro+, CRM sync, hms-link | CRM in use |
Integrations
Product names are used only to identify compatible systems. No third-party logo is shown in this document: vendors' logos are shown with the vendors' permission only.
| Category | System | Through | Status |
|---|---|---|---|
| PMS | OPERA Cloud | HMS EE · OHIP | Built |
| OPERA 5 | HMS EE · OXI | Built | |
| OPERA 5 IFC8 TV | HMS EE IFC8 adapter | Built (to verify with the hotel) | |
| Any PMS with a file export | HMS EE generic CSV/JSON connector (HTTPS or SFTP) | Built | |
| Mews Cloudbeds Apaleo protel | New HMS EE connector on their public APIs | Possible on request | |
| POS | MICROS Simphony | HMS EE · BI API (sales) and transaction services (checks) | Built |
| MICROS Simphony | CloudTV point-of-sale interface (keep off when HMS EE posts) | Built | |
| Any POS with a file export | HMS EE generic CSV/JSON connector | Built | |
| Lightspeed Toast Square POS | New connector on their public APIs | Possible on request | |
| CRM | HubSpot | ContactPro+ (create or update by e-mail) | Built |
| Zapier · signed webhook | ContactPro+ | Built | |
| Salesforce Microsoft Dynamics 365 Zoho CRM Pipedrive | Through the Zapier hook or webhook today; a direct connector on request | Possible on request | |
| Accounting | HMS EE (system of record) | hms-link from CloudTV, ContactPro+, Vwayaj; hr-sync from HR | Built |
| Zoho Books | HMS EE push (journals, bills, vendors) | Built | |
| Payroll bureau / software | HR payroll export profiles, SFTP folders, REST API | Built | |
| QuickBooks Online Xero Sage Odoo | New HMS EE push connector | Possible on request | |
| TV screens | Samsung Tizen | CloudTV TV app (.wgt) | Built |
| LG webOS | CloudTV TV app (.ipk) | Built | |
| Android TV Google TV | CloudTV app 2.0.0 (.apk), boxes and sticks | Built | |
| Any modern browser | CloudTV player: smart TV browser, Fire TV stick, Chromebox, Raspberry Pi, PC, kiosks | Built | |
| Samsung hospitality LG Pro:Centric | Hotel-mode settings, power-on with the key card, USB cloning; per-brand guides | In build (to verify on a device) | |
| Wake-on-LAN | Agent API and reference agent for TVs that are fully off | Built | |
| Other | HikCentral Professional | HMS EE (people, door events, attendance); cameras on CloudTV screens | Built off by default |
| Biometric terminals (ISAPI) | HospitalityPro HR time clock | Built | |
| Paperless-ngx | Document archive of all applications | Built | |
| Stripe CMI Square Fortis Payoneer | Plan purchase and subscription billing | Built | |
| Background music service | CloudTV zones, now playing (server key) | Built |
"Possible on request" means: the vendor publishes an interface; a connector is not built; scope, licences and effort are assessed with the hotel before any commitment.
Status legend used in this document: Built exists in the code of the deploy branch · In build described in the integration guides or specifications as being built · Possible on request common market systems with public interfaces, to be assessed and built on request.
Hosting and security
- Data: PostgreSQL 16 on its own database machine over TLS (verify-full), one database per application — the applications and their databases stay apart and exchange data only through the signed links.
- Secrets: credentials of connectors, payment providers and links encrypted at rest (AES-256-GCM); never returned to the browser; never in git.
- Accounts: two-factor authentication (required for the platform consoles), roles and scopes, idle sessions closed.
- Traceability: an activity log in every application (changes before → after, exports, e-mails, calls to other systems), append-only and hash-chained.
- Backups: a complete daily set at 00:01 (database, files, financial documents in CSV and PDF, manifest with SHA-256) with grandfather-father-son retention, plus copies outside the server.
This overview describes only what the applications' code, documentation and integration guides contain on 20/11/2026. Each integration is marked Built, In build or Possible on request. Benefits are qualitative; no figure is promised — results depend on each hotel's set-up, systems, contracts and use.