How we work
From audit to operating year.
A four-stage delivery model with explicit deliverables, roles and client inputs.
The model
Clear scope. Clear handover.
IBMS projects fail when responsibilities are vague. Our delivery model makes the boundary explicit: what we do, what you provide, and what the building team owns after handover.
It is deliberately sequential. Each stage produces a document the next stage depends on, so decisions are made once, with the right people in the room.
Discover & audit
We map the systems, protocols, existing pain points and the decisions the building needs to support.
Deliverables
- System and protocol inventory
- Interface and point-schedule gap list
- Scope and risk register
Client inputs
- Existing drawings and system lists
- Access to the facility team
- Current pain points and priorities
Design the architecture
We turn the audit into a layer diagram, integration matrix and an alarm philosophy the project can be priced and built against.
Deliverables
- Layer and network architecture
- Integration matrix
- Alarm and interlock philosophy
- Scope of responsibilities
Client inputs
- Sign-off on scope and priorities
- Consultant coordination
- Budget and programme constraints
Deliver & commission
Configuration, graphics, interlocks, testing and operator training — with the building team, not around them.
Deliverables
- Configured platform and graphics
- Tested interlocks and alarms
- Operator training and documentation
- Commissioning records
Client inputs
- Site access and power/network
- Third-party vendor coordination
- Operator availability for training
Operate & optimise
Trends, energy baselines, alarm review and continuous tuning against the outcomes the project signed up for.
Deliverables
- Performance baseline and trend review
- Alarm and setpoint tuning
- Quarterly optimisation report (optional)
Client inputs
- Operating data and feedback
- Access to trend history
- A named operations owner
01 / Roles
Who does what.
The model only works when the boundary is written down.
| Role | Responsibility |
|---|---|
| Owner / developer | Defines the outcome, approves scope and budget, owns the data. |
| MEP consultant | Coordinates disciplines, reviews the design and manages the tender. |
| Loxone Intelligent Building | Audits, designs, configures, commissions and trains. |
| System integrator | Delivers subsystem interfaces and site works under an agreed scope. |
| Facility team | Runs the building, validates alarms and adopts the operating model. |
02 / Client inputs
What we need from you.
System list
The subsystems, vendors and versions already installed or specified.
Drawings and schedules
Single-line diagrams, network drawings, point schedules and floor plans.
Operating model
Who runs the building, where they sit, and what they need to see.
The outcome
The result the project will be measured on: energy, comfort, compliance, headcount or reporting.
03 / After handover
The building keeps learning.
Handover is not the end of the model. Trends, alarms and energy data are reviewed against the baseline, and the operating logic is tuned as the building settles.
A documented baseline
An alarm review cadence
A change-control path for setpoints and schedules
04 / FAQ
Questions, answered
The things owners, consultants and integrators ask us most.
How long does a project take?
Can you work with our existing integrator?
Do we need to replace our BMS?
What do you need from us to start?
What happens after handover?
Next step
Bring us the building.
Tell us the stage, the systems and the outcome. We will tell you what the delivery path looks like.