A building management system may improve visibility of heating, cooling, ventilation or other building services, but installing one is not automatically a saving. The business case should identify the operational problem, the systems included, the work needed to integrate them and the people who will use the data. Owners need to compare the full lifecycle and test what benefits can be measured. This topic connects the decisions of hotel owners; hotel operations; the Feathers Hospitality approach.
The system is only valuable when its data and controls support decisions the operator can act on.
At a glance
- Start with an operational problem and baseline.
- Include integration, commissioning, training and support costs.
- Measure performance after installation against agreed assumptions.
Describe the problem the system should solve
Record current issues such as limited visibility, inconsistent schedules, repeated manual checks or delayed fault detection. Identify which building services and property areas are affected. A broad aim such as “improve efficiency” is hard to verify unless the owner states the baseline and the change expected.
Check existing equipment and controls before proposing replacement. Some gaps may be addressed by commissioning, maintenance or clearer operating routines. A technology proposal should explain why a new platform is needed and what capability the current system cannot provide.
Define scope and integration needs
List the assets, sensors, controllers, networks, user roles and interfaces in scope. Confirm compatibility with existing plant and whether older equipment needs gateways or replacement. Identify systems that remain separate and how faults or readings move between them. Unclear scope can lead to extra work after approval.
Ask for the sequence of operation, data points and alarm rules in a form the operator can review. Confirm who owns configuration and how changes are documented. Do not assume that a dashboard alone creates coordination between a system, service contractor and property team.
Build a whole-life cost view
Include hardware, software or licences, engineering, cabling, network work, installation, commissioning, training, support, maintenance and future replacement. Record whether fees are fixed or recurring and what happens at contract end. Compare options over the same period and with consistent assumptions.
Estimate potential energy or labour effects from the baseline and a clear calculation. Use ranges when schedules, tariffs or occupancy are uncertain. Do not count the same saving under both energy and operating efficiency. Identify costs the owner would incur even if the project proceeds in phases.
Test operational usability and resilience
Ask who will review alerts and what action follows. Check role access, out-of-hours support, data export, backup, cybersecurity review and what happens if the network or vendor platform is unavailable. The control system should not create a single point of failure without an approved operating fallback.
Involve the people who will use it during design and commissioning. Test typical schedules, override permissions and safe behaviour during faults with competent specialists. Avoid exposing credentials in shared documents. Define who can change a setpoint and how a change is authorised and recorded.
Plan delivery and commissioning
Create a sequence for surveys, design, procurement, installation, testing, training and handover. Identify shutdowns, guest impacts, dependencies on electrical or mechanical work and the acceptance criteria for each stage. Confirm that access to technical areas and staff time are available when needed.
Require evidence that the system works with the installed equipment and representative operating conditions. List unresolved defects and temporary workarounds before final acceptance. Commissioning records should identify settings, test results and responsible parties so the operator is not left to reconstruct them later.
Review benefits after the system is in use
Set measures linked to the original problem: fault response, schedule accuracy, energy use under comparable conditions or reduced manual checks. Define a review period and collect data before installation. Adjust for occupancy, weather and changed equipment where relevant; raw consumption alone may not show whether performance improved.
Assign an owner for each benefit and a technical contact for issues. Review training and alarm quality, not just whether the platform is online. RICS planned-maintenance guidance and Turismo de Portugal sustainability resources can inform wider asset planning, but technical design and savings estimates require property-specific evidence.
Frequently asked questions
Should a building management system always pay for itself through energy savings?
No. Benefits may include operational visibility or fault response, but they should be defined and valued separately. Savings depend on the building, use and implementation.
What should approval require?
A defined problem, scope, lifecycle costs, integration plan, risks, acceptance criteria and measurable outcomes with owners and assumptions.