The RM ecosystem — PMS, CHM, RMS, BI

Across the 14 lessons so far we’ve often touched the hotel’s technical systems — the PMS, the Channel Manager, the pricing engine, the reporting tools. Now we put them together into one picture, because a revenue manager can’t work without knowing the stack.

A modern hotel runs an ecosystem of 4 systems, where each system serves a specific purpose and the systems exchange data with one another in real time. A missing or poorly integrated system dramatically reduces the effectiveness of RM work — a badly configured Channel Manager causes double-booking, a missing RMS leads to reactive (not proactive) pricing, and a weak BI system makes questions like “which segment is slipping for November?” invisible.

The goal of this lesson is for you to know the four layers of the stack, see how they work together, and understand the integration points — because an RM operates through all of them.

The four layers

The four layers of the modern hotel stack:

The four layers are a continuous data circulation: the PMS collects the data on bookings, the CHM distributes the rates to the channels (and syncs incoming bookings back), the RMS analyzes the data and recommends pricing, the BI visualizes the whole picture for the human RM.

Now let’s go through them one by one.

1. PMS (Property Management System)

The PMS is the hotel’s “central database”. Everything that happens in the hotel is in some way recorded in the PMS:

• A guest books → it goes into the PMS.
• The receptionist checks them in → the PMS updates.
• The guest gets a bill after breakfast → a folio entry in the PMS.
• The check-out happens → the PMS closes the booking, releases the room.
• A room goes “out of order” (renovation, malfunction) → the PMS flags it.

Typical PMS systems on the market:

• Sabeeapp — a cloud PMS used in European and international markets. Hotel Peaqplus City uses this.
• Mews — European cloud, modern, fast user interface. Many independent boutique hotels choose it.
• Fidelio (today Oracle Hospitality OPERA, its cloud version being Opera Cloud) — the classic enterprise system, the PMS of the large international brands.
• Previo — Central-European (Czech origin), for small and medium hotels.
• Hostware — Central-European presence.

The PMS choice is a strategic decision in a hotel’s life — it lasts 5-10 years, because migrating to another system is expensive and risky. Every other system pulls data from the PMS, so the PMS has to be open (API, integration interfaces).

From an RM perspective the PMS is the source of truth: the actual occupancy, ADR and RevPAR are recorded here. Every other system copies and interprets this.

2. Channel Manager (CHM)

The Channel Manager is the translator between the hotel and the external distribution channels. In lesson 6 (Channels) we saw that a hotel sells its rooms through 8-15 channels — Booking, Expedia, Hotels.com, Agoda, the GDSs, its own web, metasearch, B2B distributors, etc.

Without a CHM the hotel would have to set rates and availability manually on each channel separately. That would be 2-3 hours of daily work, and a source of human error — double-booking is a common phenomenon on a weak integration.

With the CHM: the hotel sets a rate in one place (in the PMS or the RMS), and the CHM distributes it in real time to every channel. And an incoming booking is immediately synced back to the PMS, so availability drops automatically on the other channels.

Typical CHM systems:

• D-Edge — a leading European CHM, used by many hotels. Strong OTA integration + booking engine + GDS.
• Cubilis — Belgian origin, Central-European presence.
• SiteMinder — Australian origin, global, at many independent hotels.
• RateGain — Indian origin, often at larger chains.
• Bookassist — Irish origin, in a European position.

Hotel Peaqplus City uses D-Edge, because it integrates well with its PMS (Sabeeapp) and provides instant sync support for all of its OTA channels.

A classic source of faults with the CHM is integration errors — the OTA mapping (which rate plan + which room category corresponds on Booking.com), the distribution of restrictions, the booking sync. In a mature RM organization the CHM is audited monthly — otherwise the mapping errors skew the rates.

3. RMS (Revenue Management System)

The RMS is the “brain” — the system that supports the pricing, forecast and restriction decisions. This is where the question sits: “what should the BAR be tomorrow?”, “on which day do I need to introduce MLOS?”, “for which date is the transient segment’s pickup slowing?”

The classic PMS and CHM don’t deal with pricing decisions — they only move the data. The RMS is the one that analyzes the data and gives recommendations to the RM.

Peaqplus is in this category. A few concrete functions that make up an RMS:

Pickup analysis

We cover it in detail in lesson 16 (Pickup and booking pace). Peaqplus shows a daily pickup board: for each date, the current occupancy, last year’s same-point, the budget target, the expected final. The pickup board is the central element of the RM’s daily morning routine.

Same Point analysis

We cover it more deeply in lesson 18 (Same point analysis). Peaqplus shows the same-point built in alongside the pickup analysis: not an abstract YoY comparison, but at the same booking window (e.g. “30 days before check-in”). This is a dramatically better interpretive frame.

Forecast module

We cover it in lessons 19-20 and 38 (Forecasting). Peaqplus generates a daily forecast for the next 30-90 days, and uses hybrid logic: pickup trend + booking curve + manual corrections (events, holiday shift).

Smart Forecast Enhanced

An advanced function we cover at the expert level in lesson 55 (Smart Forecast Enhanced). Its essence: an AI-augmented, multi-layered forecast over a 60-90 day horizon — a statistical model + LLM-estimated anomaly signals + manual corrections.

DCAL (Day-Class-Arrival-Length)

We cover it in lessons 33-34 (DCAL). A matrix-like pricing approach, where the rate isn’t one number but a matrix as a function of the arrival day, the room category and the length of stay.

Pricing Engine

We cover it in lessons 35-36 and 56 (Dynamic pricing and ML-based recommendation). Peaqplus generates rule-based and ML-based rate recommendations — the RM reviews and documents the decision.

Insight Engine

We cover it in lessons 52-53 (Insight Engine, AI narrative). An AI analysis that tells you summary-style analyses in natural language: “The city break segment’s pickup is running 18% behind budget, mainly because of the moderation in corporate travel…”. The RM gets in 5 sentences what they’d otherwise read off 100 charts.

An RMS’s function list won’t fit in a single lesson — these are the main modules, and we return to each at the advanced/expert levels.

The key message: the RMS is the only system that thinks for itself — the others (PMS, CHM, BI) only move and display the data. The RMS is decision-support, and in a modern hotel it supports 50-70% of the revenue manager’s work.

4. BI (Business Intelligence)

BI is the layer of display and analysis — the reports, dashboards, ad-hoc queries, executive summaries. A BI tool reads from all the systems (PMS, CHM, RMS) and visualizes the data.

The classic BI approach is a web dashboard over a hotel-structured “data warehouse”. Here you find:

• The morning report — yesterday, month, year — aggregate metrics.
• The pace reports — the occupancy-pickup track for the next 30-90 days.
• The segment breakdown — monthly, date-level, by channel.
• The F&B and spa revenue — the data needed for TRevPAR.
• The compset analysis — own position vs. market average.
• The ad-hoc questions — “which corporate contract dropped out over the last 6 months?”

In a modern RM organization the BI is the central surface of the daily routine. If the PMS, the CHM and the RMS are all the “operation”, the BI is the understanding.

There’s no single dominant market solution for BI tools — a mid-size hotel often works at the level of Excel + its own SQL queries, while a larger hotel group runs an enterprise-grade web BI platform.

The data flow

The four layers’ data exchange is a continuous loop:

1. Booking process: a guest books on an OTA → the CHM receives it → the PMS records it.
2. Rate-update process: the RM decides a new BAR in the RMS → the new rate goes to the PMS → the CHM distributes it to all channels.
3. Forecast update: daily PMS export → the RMS processes it → a new forecast is generated → the BI displays it.
4. Report display: the BI reads from the PMS + RMS + CHM → it appears on the dashboard for the RM.

Between the four layers there are integration points — APIs, file export-import, real-time webhooks. A weak integration degrades the whole system:

• If the PMS → CHM integration is slow (e.g. a 30-minute refresh), the hotel risks double-booking.
• If the RMS → PMS integration isn’t real-time, the rate the RMS recommends reaches the channels with a 24-hour lag.
• If the BI doesn’t read from everywhere, the reports have holes.

A mature RM organization puts the stack under a monthly integration audit: is every data-movement point working, are there any slippages, what errors are showing up.

What a beginner RM needs to understand about the stack

A beginner revenue manager doesn’t operate the stack — but understands it and works with it. The minimums:

1. Knows which data comes from which system — in a discrepancy, they know where to look.
2. Understands the frequency of the data updates — a PMS export that runs at 22:00 won’t show, the next morning, the bookings that arrived at 23:00.
3. Recognizes integration errors — if Booking.com shows EUR 110 but your own system has 95, the CHM mapping is probably wrong.
4. Knows what they can and can’t ask of the stack — e.g. a classic PMS can’t necessarily pull a segment-level ALOS; that’s an RMS or BI function.
5. Knows where to flag it when something isn’t working — if the sales team sees the member rate isn’t syncing, then IT or the PMS vendor needs to look into it.

These are baseline skills. In lessons 16-32 (the intermediate level) we build on these more deeply: there we already work with the stack at the level of report reading, pace analysis and channel analysis.

Looking back over the whole beginner level

This was the beginner level’s last lesson. Across 15 lessons we’ve built the foundation of the RM discipline:

• 1. What RM is and why it matters
• 2. Perishable inventory as the root of the discipline
• 3–4. The three core KPIs + TRevPAR
• 5. The optimal mix vs. 100% occupancy
• 6–7. Channels, distribution, rate parity
• 8. Segments and markets
• 9–10. Seasonality and the booking window
• 11. Length of stay and ALOS
• 12. A day in the life of an RM
• 13–14. Rate structure and compset
• 15. The technical stack

These are the building blocks — each touches one conceptual area. At the intermediate level (lessons 16-32) we shift the focus toward the measurement and analysis tools: how to read pickup and pace, how to analyze the channel mix, how a forecast is built, how to run a revenue meeting. Deeper measurement, more mature decisions.

At the advanced level (lessons 33-50) comes the strategy and method: dynamic pricing, DCAL, group displacement, length-of-stay restrictions, leading a revenue meeting.

At the expert level (lessons 51-67) the data-driven and AI-supported RM takes centre stage: Insight Engine, AI narrative, Smart Forecast Enhanced, ML-based pricing engine.

With this map in your head, we can go further. Thank you for sticking with it this far — now comes the depth.

Key takeaways

• A modern hotel works on a 4-layer stack: PMS (central record), CHM (channel translator), RMS (decision support), BI (display).
• The four layers work together with real-time data exchange — a weak integration = double-booking, late rate updates, incomplete reports.
• The PMS is the source of truth — every other system pulls data from here.
• The RMS is the only system that thinks for itself — the others move and display the data. This is Peaqplus’s category.
• A beginner RM doesn’t operate the stack, but understands and works with it — the minimums: knowing the data source, the update frequency, and recognizing integration errors.