Hotel digital twin: find the fault before the guest does.
One live 3D twin of your hotel, joined to the systems you already run. Every complaint, work order, certificate and contract credit lands on the asset behind it, with a price attached. Codset builds it end to end, in your cloud, on your servers or air-gapped.
Get the 90-day pilot plan
Eight pages, free, sent on screen as soon as you press the button.
- Why hotels lose money in plain sightSix systems, one fault logged three times.
- What the twin watchesComfort SLA, reviews, energy, certificates, the FM contract.
- How it runsRead-only connectors, a 3D model, a record of every decision.
- Under the hoodThe stack, the connectors, cloud, on-prem or air-gapped, and support.
- The 90 daysConnect, build and calibrate, run decisions.
- What we need from youAccess, drawings and two named people.
What the twin finds, in the demo hotel
Azure Crest Hotel and Residences, 402 rooms on 36 floors, from the Synopton hotel demo. Demo names and figures are illustrative.
- €8.9k purchase order, stoppedA fan-coil unit still inside its warranty. The claim costs €561 of labour, and the same model has failed 11 times across 4 buildings.
- 412 room nights too warmSold outside the comfort band this month, worth €51k in FM contract credits.
- €101k a year of energy wasteSix causes ranked by payback. A chiller efficiency drift is €50k on its own.
- Water on the guest route at 07:58Flagged by an existing CCTV camera, with the cordon placed before the repair.
How it runs in your hotel
Every figure carries its provenance: measured, modelled, published, assumed or forecast.
- ConnectRead-only links to the BMS, CMMS and helpdesk, the PMS and guest reviews, energy metering, CCTV and the FM contract itself.
- NormaliseEvery reading is tied to an asset, a unit, a timestamp and its source system.
- ModelA 3D twin built from floor plans and equipment lists, or loaded from your BIM, with rooms, plant and cameras where they really are.
- DetectComputer vision on the cameras the hotel already has: water on the floor, people in a closed zone, hygiene and safety checks.
- DecideAnswers that cite the twin's own data, and decision records with an owner, a deadline and a measured result.
- DeployYour cloud, your servers or air-gapped, with single sign-on, roles and an audit log. Nothing writes back to building systems.
Under the hood
The stack, the connectors and where it runs.
- 3D twinThree.js and WebGL in the browser, built from drawings or loaded from IFC and GLB.
- VisionDetection and tracking on existing RTSP and ONVIF camera streams.
- DataA time-series store and an asset graph; every value keeps its unit, timestamp and source.
- AI answersLanguage models grounded in the twin's own data, with citations, on hosted or local models.
- ConnectorsBACnet, Modbus, OPC UA, MQTT, SAP, Microsoft 365, Outlook, Teams, SharePoint, Power BI, your PMS and CMMS. Read-only.
- InstallationYour Azure, AWS or Google Cloud tenant, your own servers on Kubernetes or VMs, or fully air-gapped.
- SecuritySSO over SAML or OIDC, role-based access, an audit log, REST API and webhooks.
- SupportA named delivery lead, optional 24/7 on-call, scheduled updates. The code and IP are yours.
One hotel. 90 days.
- Weeks 1 to 2 · ConnectRead-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 calibrateThe 3D twin with every source mapped to it, calibrated against your own measurements. Usable from week six.
- Weeks 7 to 12 · Run decisionsYour team runs real decisions through it, each priced and owned. Then a close-out report.
Questions buyers ask
Do we need a BIM model of the hotel?
No. We build the 3D twin from layouts, drawings and an equipment list. If you have BIM, IFC or GLB models, we load them.
Does the twin change settings in our BMS?
No. Connectors are read-only. Accepting a recommendation drafts a decision record for people to agree; nothing is written back to building systems.
Can it run in our own cloud, on-premises or air-gapped?
Yes. It runs in your Azure, AWS or Google Cloud tenant, on your own servers, fully air-gapped with offline model updates, or hosted by us. Single sign-on, roles and an audit log come as standard. Data residency and retention are agreed during the pilot.
Which systems can it connect to?
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; and your PMS and CMMS over their APIs or exports. All connectors are read-only.
Who supports it after the pilot?
A named delivery lead from the team that built it, with optional 24/7 on-call support. Models, connectors and security patches are updated on an agreed schedule, and the code and IP built for you are yours.
How soon is the twin useful?
The twin is usable from week six of a 90-day pilot, and your team runs real decisions through it in weeks seven to twelve.
Our data is messy. Is that a problem?
It is normal. Anything that cannot be measured is labelled as assumed, so nobody mistakes an estimate for a reading.