Hotel digital twin: find the fault before the guest does

The problem: your systems knew, they never talk

A guest complains that the room is too warm. The helpdesk logs a ticket, the building management system shows a fan-coil fault, the maintenance system raises a work order and procurement buys a new unit. The same fault is logged three times, and nobody checks the warranty register.

Hotels lose money in plain sight this way. Rooms are sold outside the comfort band agreed in the FM contract. Equipment that is still under warranty gets replaced at full price. Energy drifts upward for months before anyone looks. A leak on a service route is found by a guest, not by the camera that recorded it.

What the twin finds in a demo hotel

In the Azure Crest demo hotel (402 rooms on 36 floors, illustrative names and figures), the twin surfaces four things in one view:

• A €8.9k purchase order, stopped. The fan-coil unit is still under warranty. The claim costs €561 of labour, and the same model has failed 11 times across 4 buildings.
• 412 room nights too warm. Sold outside the comfort band this month, worth €51k in FM contract credits.
• €101k a year of energy waste. Six causes ranked by payback, with a chiller efficiency drift worth €50k on its own.
• Water on the guest route at 07:58. Flagged by an existing CCTV camera, with the area cordoned off before the repair.

Who a hotel digital twin is for

• Hotel owners and asset managers. who want comfort, energy and maintenance costs in one picture.
• General managers and directors of engineering. tired of finding faults through guest complaints.
• FM providers. who need to prove the comfort SLA they are paid against.
• Hotel groups and resort operators. comparing several properties on the same measures.

How it works

Connect. Read-only links to the BMS, the CMMS and helpdesk, the PMS and guest reviews, energy metering, CCTV and the FM contract itself.

Normalise. Every reading is tied to an asset, a unit, a timestamp and its source system.

Model. A 3D twin built from floor plans and equipment lists, or loaded from BIM, with rooms, plant and cameras where they really are.

Detect. Computer vision on the cameras the hotel already has: water on the floor, people in a closed zone, hygiene and safety checks.

Decide. Answers that cite the twin's own data, and decision records with an owner, a deadline and a measured result.

Every figure carries its provenance: measured, modelled, published, assumed or forecast.

What it connects to and where it runs

BMS, meters and plant over BACnet, Modbus, OPC UA or MQTT. Cameras over RTSP or ONVIF. SAP, Microsoft 365, Outlook, Teams, SharePoint and Power BI. Your PMS and CMMS over their APIs or exports. All connectors are read-only, so nothing is written back to building systems.

The twin runs in your Azure, AWS or Google Cloud tenant, on your own servers, fully air-gapped, or hosted by us. Single sign-on, roles and an audit log come as standard.

How Codset builds it

We build hotel digital twins end to end through our data and digital twins service, with sovereign deployment for groups with strict hosting rules. A pilot covers one hotel in 90 days:

• Weeks 1 to 2, connect. Read-only access to the systems you run, drawings or BIM, and one page of the questions the twin must answer.
• Weeks 3 to 6, build and calibrate. The 3D twin with every source mapped to it, calibrated against your own measurements. Usable from week six.
• Weeks 7 to 12, run decisions. Your team runs real decisions through it, each priced and owned, then a close-out report.

After the pilot, a named delivery lead from the same team supports it, and the code and IP built for you are yours. The free hotel twin pilot plan sets out what we connect and what you get by week six.

Fix it before the guest feels it

Tell us about the hotel: the number of rooms, the systems you run and the complaint you hear most. Write to info@codset.com, send a brief or download the pilot plan.

Questions buyers ask