Loxone delivery
Loxone Project Delivery — From Survey to Handover
The delivery sequence for a Loxone project: survey, interface audit, design, factory test, commissioning and handover, with the evidence each stage should produce.
Quick answer
Delivery runs from survey and interface audit through design, panel build, configuration, factory testing, site commissioning and handover. Each stage produces a document the next stage can check: point list, drawings, test sheets and as-builts. The programme depends on building readiness and third-party interfaces, so responsibilities and acceptance criteria must be agreed before work starts.
Survey and interface audit
Delivery starts with what exists, not with a product list. The survey records the plant, the existing controllers, the available protocols, the network, the cable routes and the areas that cannot be disturbed. The interface audit then asks a harder question for every system: who owns the data, who may write, what happens on failure and who supplies the gateway. This is where most project risk is found. A clear audit can remove scope that was never achievable; a vague one guarantees disputes later. The output is a short, signed report with photographs, a system list and a list of open questions, not a sales proposal; the open questions become design actions.
- Survey what exists before listing products
- Record who owns each interface
- Identify areas that cannot be disturbed
Design and factory work
Design turns the survey into a point schedule, a network diagram, panel drawings, an address plan and a sequence description. The panel is built and tested in the factory before it travels. Factory acceptance testing checks wiring, labelling, power, inputs and outputs, and as much of the logic as can be simulated without the real plant. It is cheaper to find a mislabelled terminal on a bench than on a ceiling. Configuration and graphics should be far enough advanced at this stage that the site team is commissioning, not still designing. The factory test should use the same naming and graphics as the site, so the panel is not a separate version of the truth.
- Design produces the point schedule and drawings
- Build and test panels before shipment
- Find labelling errors on the bench
Site commissioning
Commissioning is a sequence of proofs: point by point, room by room, system by system, then the cross-system behaviours. Each point is forced, read back and recorded. Each sequence is tested in normal operation and in failure. Alarms are raised, acknowledged and escalated. Trends are checked for interval and time stamp. The snag list is managed openly, with an owner and a close-out date. A building is not commissioned because the screens light up; it is commissioned when the written test evidence matches the design intent. Where a sequence cannot be tested without the real plant, record the assumption and return to it during seasonal commissioning, when the building is at design load.
- Test point by point, then by sequence
- Include failure and alarm cases
- Close snags with an owner and a date
Handover and support
Handover includes the as-built drawings, the point list, the project backup, software and firmware versions, credentials controlled by the owner, test records, training and a support route. Training should be role-based: operators learn the alarms and overrides, technicians learn the points and backups, managers learn the reports. Agree a defect period and a change process. The final question is practical: can the owner's team run the building next Monday without the project team on site? If the answer is no, the handover is not finished. A short post-handover review, held while the project team is still available, catches the gaps that training always exposes and turns them into actions before they harden. It is cheaper than discovering the same gaps in the first service call.
- Role-based training, not one session for all
- Owner-controlled credentials
- A support route after handover
Delivery stages
6 rows| Stage | Main output | Acceptance evidence |
|---|---|---|
| Survey | Existing-systems report and constraints | Signed survey notes and photos |
| Interface audit | Responsibility matrix and protocol list | Agreed point owners and gateway scope |
| Design | Point schedule, drawings and sequences | Reviewed design pack |
| Factory test | Built panel and configured controller | FAT record and snag list |
| Commissioning | Tested points, sequences and alarms | Signed point-by-point and sequence sheets |
| Handover | As-builts, backups, training and support | Handover certificate and training record |
Project images
3 images
Frequently asked
01How long does a project take?
It depends on scale, building readiness and third-party interfaces. The programme should be built from the point schedule and the commissioning sequence, not from a generic duration.
02Can work continue while the building is occupied?
Often yes, with phased areas, out-of-hours work and a clear isolation plan. The survey should identify areas where work would disrupt operations.
03What is the difference between FAT and SAT?
Factory acceptance testing proves the panel and configuration before shipment. Site acceptance testing proves the installed system against the real plant and the design intent.
04Who coordinates other trades?
The main contractor usually coordinates site access and sequencing. The automation integrator coordinates its own panels, gateways and commissioning, and must escalate interface gaps early.
05What do we receive at handover?
As-built drawings, point list, backups, software versions, credentials, test records, training and a support route. The exact list should be a contractual deliverable.
Next step
Bring us the building.
Tell us the building type, systems in scope and the outcome you need. We will map the shortest path to a working system.