Same rooms. New economics.
Pilot objective: measure on property meters, then replace the model with evidence.
A hotel may receive one energy bill for the whole building without a room-level map of where it goes. A proposed pilot on a small set of matched rooms would test whether room- and load-level metering can establish a defensible baseline. Any savings or scale case must come from that property's measured evidence.
Measure where energy goes. Quantify uncertainty. Review any proposed action. Then decide whether expansion is justified.
Technical scope, timing, and commercial structure are confirmed directly for a real pilot. The model beside you is an illustrative Cognitive Twin: it previews the interface, not a live customer property or measured result.
explore the interactive sample
A real-estate and smart-city advisory lens.
Smart City Labs reports that its operators and technologists have delivered $12 billion in development worldwide and that principals bring 30+ years of experience. Those are company-reported track-record figures; they are not evidence of a hotel software deployment or measured energy outcome.
Smart City Labs currently markets advisory services, Destination OS, and a Cognitive Twin. This page does not independently verify the generalized capabilities described on those product pages. The twin beside you is illustrative, and the Fibric relationship shown is a governed product pattern, not proof of a live generalized-kernel runtime.
company-reported track record →One building. One bill. No map of where it goes.
A hotel may receive one utility bill for the whole building without a room-level load map. ENERGY STAR has published a historical benchmark of $2,196 per available room each year; a current property requires its own tariff and meter evidence.1
The chart below is a hypothetical decoupling scenario, not 2020 customer data. It illustrates the question a pilot would test: how much of a specific property's electricity persists as occupancy changes, after accounting for weather, services, and operating conditions?
The first question: can a bounded, matched-room study produce evidence strong enough to justify any next step?
see the sample plant loadA handful of rooms. A defined measurement window.
A well-designed pilot should aim to produce a room-level load estimate, uncertainty and data-quality notes, and evidence for deciding whether any approved action or expansion is warranted.
The reference pilot scope focuses on energy use across five matched guest rooms. A property-specific design would confirm system access, metering, an occupancy method, consent, and operating safeguards before collection begins. Any proposed control change would require explicit property approval and would remain separate from independent room and life-safety controls.
The capabilities, by name
Energy metering proposed
Per-room time-series consumption, with the meter and validation method confirmed in the pilot design.
Occupancy evidence proposed
A property-specific method could compare approved door and presence signals. No single signal proves a room is vacant; consent, coverage, and false states require validation.
HVAC setback future · approval required
A future path could propose a bounded setback for a reviewed vacancy state. Controller behavior, comfort recovery, and independent safeguards must be commissioned first.
Lighting & TV trim future · approval required
A future path could propose a bounded change to supported standby or lighting loads. The sample does not establish hardware authority or recoverable savings.
Fault signal proposed review
A monitored deviation could be surfaced with its evidence for engineering review. Prediction quality and any work-order path would require property-specific validation.
Evidence, limitations, and a decision about what comes next.
Room- and load-level estimates only where meter coverage and validation support them, with missing states made explicit.
A bounded estimate with denominators, comparison method, uncertainty, and the possibility that no recoverable savings is demonstrated.
Observed deviations for engineering review, not a guaranteed prediction or automatic dispatch.
Evidence and limitations for a continue, change, or stop decision. Data rights and any reporting deliverables are contract-specific.
Start with the systems a property can support.
The dominant load is often the room's heat pump, and it is reached through HVAC and building-management interfaces rather than a plug. A proposed pilot would scope the actual systems, access, metering, and approvals at the property. The public twin uses sample values; only a deployed pilot could produce measured room-level evidence.
Where the energy may go is the first hypothesis to test. The sample shares below are planning assumptions, not industry facts. A future pilot would report only the loads its meter design can support.
| Room load | Illustrative range2 | Future pilot evidence |
|---|---|---|
| Heat pump (HVAC)candidate thermostat / heat-pump / BMS path | 40–60% | to be measured if in scope |
| Lightingcandidate lighting measurement | 15–20% | to be measured if in scope |
| Plug & always-oncandidate outlet metering | 12–18% | to be measured if in scope |
| TV & standbycandidate standby measurement | 5–8% | to be measured if in scope |
The cost of not knowing is the bigger number.
A pilot is intended to test what may be recoverable on a property's rooms, systems, and data. The calculator uses a hypothetical hotel spending $600,000 a year on energy and shows scenario math only. It is not a forecast, customer result, or savings guarantee.
that's $360,000 over 5 years at 12% reduction
Test it on a few rooms. Then decide whether to expand.
A pilot is small on purpose. If the property-specific evidence and controls are acceptable, the team can evaluate expansion to a floor, tower, or portfolio. Each stage still requires system access, connector validation, operating approvals, and fresh measurement; a small pilot does not prove automatic scale.
From your go-ahead to a number on the table.
This four-step sequence is illustrative. Timing, installation work, IT involvement, operating constraints, and deliverables depend on the property and are confirmed directly before a pilot begins.
Scope the pilot
Confirm the rooms, systems, access, approvals, funding, commercial terms, and a feasible schedule.
Confirm the install plan
Document the metering and integration work the actual property requires before committing to timing or room availability.
If approved, meter the scoped rooms
Over an agreed window, validated meters would collect the evidence their coverage supports. The public twin is only an illustrative interface.
Review the evidence
Review the collected room-level evidence, its limitations, and whether it supports any next-stage business case.
Actual prerequisites may include room access, facilities and IT review, system authorization, consent, safety review, and a working session. The property-specific scope determines what is required.
Commercial terms follow the verified scope.
Funding and payment structures are not promised by this page. Smart City Labs can discuss whether a conventional fee, shared-savings approach, financing, or another structure is appropriate after the technical and measurement scope is understood.
Access, stakeholders, metering, safeguards, timing, and price are confirmed directly.
Any shared-savings, energy-service, or financing structure is subject to separate diligence and agreement.
Evaluate whether a bounded hotel pilot is feasible.
The model beside you is a sample property. Any real pilot would be scoped from authorized rooms, systems, meters, consent, safeguards, and a defined comparison method. This page does not promise light installation, complete measurement, savings, or a path to whole-property control.
Smart City Labs shows how the governed pattern could apply to property operations.
This page is an illustrative product-direction sample. It does not prove that the generalized Fibric kernel is the live runtime underneath Destination OS. Fibric's broader platform is available through managed early access, with each supported signal and action path scoped and validated.
Scope the supported signals
Software and hardware sources require a connector, authorization, mapping, data-quality checks, and tenant scope. Replacing a system still requires implementation and parity testing.
The model proposes
In the reference contract, a model proposes a structured plan; deterministic policy and execution checks decide whether a supported action may proceed.
Control duplicate effects
Single-flight and idempotency controls reduce duplicate execution. Supported paths can leave an attributable record; downstream recovery depends on the connector and cannot make every action reversible.
One platform. Two ways in.
If you run a hotel, Smart City Labs can assess whether a bounded room-level measurement study is feasible. Scope, commercial terms, access, safeguards, and deliverables are confirmed directly. Fibric's generalized platform is managed early access. The model beside you is an illustrative sample, not a live property.