Specifier
Specifier
You leave before it shows
Your documents commit the building to years of operation you will not see. You leave at the end of construction. Your part comes earlier: sizing correctly and making acceptance verifiable. Today, a commissioning engineer tests a few points and validates a few scenarios, which is all the time allotted to handover allows. When the requirements in your documents are attached, in a building model, to each item of equipment and each point, the whole installation can be checked against what you wrote.
Design teams, consulting engineers, AMO (owner's representatives): before the first package goes out to tender, the number of points, the permitted protocols and what will have to be proven at handover are written into your documents.
The model
The building described once, exhaustively, in a model that every phase of its life reads.
Situations
Two things your documents can prevent
- Sample-based acceptance
With no evidence to have them corrected, defects accepted at handover are paid for over years. We make possible acceptance testing that can be re-run after every change and checks the installation point by point against the project documents (owner's brief, specification, sequence of operations, the French CCTP technical specification and points lists).
Learn more
- A building re-entered for every tool
The building described once, exhaustively, in an open model (Haystack, Brick) that later services read without re-entering anything.
Learn more
Our approach
A modelled installation becomes verifiable
Sizing based on a reference model of the portfolio: spaces, uses, equipment, what serves what, metering and distribution. Supervisory software is licensed in blocks of points. The metering and energy distribution plans come out of it. Acceptance testing against the requirements: each requirement becomes an element of the model. For example the function of an item of equipment, the range of a setpoint or the trigger condition of an alarm. Revision-controlled as-built documentation produced and regenerated from the model. A model written to open standards, exportable to Haystack and Brick, which stays with the building owner and lets another contractor take over the portfolio.
The starting point
The project documents
They set the expectations, the framework the installation fits into, and the reference for its validation.
Built into the model
Each requirement is attached to the equipment, the point or the sequence it concerns. The model holds what is installed and what is expected.
Validated against them
Acceptance testing checks point by point that the installation does what your documents promise. It is re-run whenever the installation changes.
The owner's brief
It describes uses, spaces and expected service levels. Every integration choice is traced back to what the building must deliver.
The design documents
Specification, sequence of operations, CCTP (the French technical specification), drawings and points lists. These contract documents go into the study.
Your IT systems
The B(I)OS fits into them. It respects your networks, your security, your directories and your naming conventions. It connects to your business applications: maintenance, room booking and energy suppliers.
Let's talk about a document you are drafting
Tell us which project and what stage it has reached. The demo will start from there.