BMS specification template: the chapters a work-package spec must contain
A BMS specification template is a numbered list of requirements grouped into chapters that follow the life of the work package: scope and reference texts, functions, hardware, network and supervisory system, cybersecurity, energy performance, documentation and training, testing and acceptance, schedule. Two appendices carry the price: the points list and the priced breakdown. Everything else exists to make those requirements priceable by bidders and verifiable at acceptance.
Why a BMS spec is written as numbered requirements
A building management system is bought three times: by the bidder who prices it, by the integrator who programmes it and by the owner's team who accepts it. "The system shall be open and secure" means something different to each of them. "Each air handling unit is controlled on return-air CO2 with a setpoint adjustable from the supervisory system; evidence: functional test sheet signed on site" means the same thing to all three.
A workable convention is one prefix per chapter (F functional, M hardware, R network, C cybersecurity, P performance, D documentation, E testing) and four parts per requirement: identifier, statement, level or option where relevant, and the evidence expected at acceptance.
The chapters, in order
| Chapter | What it must contain | What goes wrong without it |
|---|---|---|
| 1. General and scope | Purpose, scope of works, dated reference texts, definitions, limits of works package by package (HVAC, electrical, fire safety, lifts, plumbing, IT). | Sensors, valves and panels fall between two packages and return as a change order. |
| 2. Functional requirements | Architecture levels, controller autonomy, control strategy per plant and zone, schedules, lighting, metering, alarms by priority, scenarios, remote operation, third-party integration. | Bids describe a product, not a behaviour. |
| 3. Hardware | Controllers and I/O with spare capacity, sensors with accuracy and mounting, actuators, panels, backed-up power, cabling, open protocols by use (BACnet/IP, MS/TP, Modbus, M-Bus, DALI-2, KNX, OPC UA). | A proprietary bus at automation level makes the owner captive. |
| 4. Network and supervisory system | Dedicated VLAN, server, licences in the owner's name with a stated point capacity, views, logging, reports, user profiles. | Licences stay with the integrator. |
| 5. Cybersecurity | The level selected, the requirement families, and what design, acceptance and maintenance owe to them. | One generic sentence, and default passwords at handover. |
| 6. Energy performance | Target ISO 52120-1 class justified function by function, measurement and verification. | "Compliant with the BACS decree" without naming the class. |
| 7. Documentation, training, as-built file | Drawings, updated points list, source programmes, configuration, inventory with versions, backup procedure, training with materials. | No sources, no licences: no other integrator can take over. |
| 8. Testing, acceptance, warranty, maintenance | Factory and site tests, point-to-point tests, functional scenarios, pre-acceptance inspections, proper-operation year, maintenance terms. | Acceptance on a demonstration rather than on signed test sheets. |
| 9. Schedule and phasing | Milestones, dependencies on other packages, phasing for an occupied building. | The BMS is programmed before the HVAC is balanced. |
Clauses most specs forget
- Limits of works, item by item. Who supplies, installs, wires and commissions each sensor, valve, actuator and panel.
- Spare capacity. Free inputs and outputs per controller and a licence margin on the supervisory system, stated as figures.
- Ownership and autonomy. Source programmes, configuration files, licences and passwords handed to the owner; a facility team able to change schedules, setpoints and alarm thresholds, create a user and restore a backup without the integrator.
- Time synchronisation. Controllers and supervisory system on the same clock, including over BACnet, so that logs and alarms read in order.
- A proper-operation year. A BMS is accepted over a heating and a cooling season, not in an afternoon.
Linking the spec to the points list and the price schedule
The points list is the pricing document. For each piece of equipment it lists the physical inputs and outputs and the bus points, with location, unit, alarm priority, logging interval and panel. A points list "to be established by the contractor" produces bids that cannot be compared and a change order at the first site survey.
The priced breakdown mirrors the chapters of the specification, with quantities drawn from the points list, so that every bidder prices the same thing in the same place. In French tenders the terms are the CCTP (particular technical specification), the DPGF (priced breakdown of the lump-sum price), the lot (work package), the OPR (pre-acceptance inspections) and the DOE (as-built file); an English template for a French project keeps them in italics with their meaning. The article on the BMS points list template goes through the columns and naming rules.
Testing and acceptance inside the spec
The testing chapter states the sequence (factory acceptance test, site self-inspection, point-to-point test of every input and output, functional test of every scenario, pre-acceptance inspections with the owner, acceptance, then a proper-operation year with seasonal checks) and the evidence for each step: signed sheets, exported trends, a reservation list with closure dates. It names the non-conformities that block acceptance whatever the overall pass rate. The cybersecurity clauses belong in chapter 5; the article on BMS cybersecurity requirements gives a checklist by family with the evidence for each.
Adapting to an existing building in France
For an existing non-residential building in France, the template carries the BACS decree. Article R. 175-2 of the French Construction and Housing Code (version in force since 28 December 2025, Légifrance) requires a building automation and control system in tertiary buildings whose heating or air-conditioning system, combined or not with ventilation, has a useful rated output above 290 kW, by 1 January 2025 at the latest, and above 70 kW, when that system is replaced and by 1 January 2030 at the latest. The 2030 date comes from Decree no. 2025-1343 of 26 December 2025, which amended the article; the obligation was created by Decree no. 2020-887 of 20 July 2020 and extended to 70 kW by Decree no. 2023-259 of 7 April 2023. The same article exempts an owner who produces a study showing that installing the system cannot be achieved with a payback period below ten years; the other technical building systems are connected to it where the connection can be achieved with a payback below ten years, public aid deducted.
The European frame is Directive (EU) 2024/1275 of 24 April 2024 on the energy performance of buildings: Article 13(9) sets the thresholds at 290 kW by 31 December 2024 and 70 kW by 31 December 2029, and Article 13(10) requires the system to monitor, log, analyse and allow adjustment of energy use, benchmark efficiency and detect efficiency losses in technical building systems. The functions are classified in ISO 52120-1:2021 (published December 2021). For the cybersecurity chapter, the French reference is the ANSSI guide ANSSI-PA-110, version 1.0 of 27 April 2026, with recommendations R1 to R26. The article on France's BACS decree details the thresholds and the exemption.
One legal point: Act no. 94-665 of 4 August 1994, Article 5 (Légifrance), requires, with the exceptions it lists, contracts to which a French public body is a party to be drafted in French. An English specification is a working document to prepare, price, review or negotiate; for a public owner, the contractual version is issued in French.
FAQ
Can an English specification be used for a tender in France?
As a working document, yes. For a public owner, Act no. 94-665 of 4 August 1994 requires the contract to be drafted in French, so the contractual specification is issued in French. For a private owner, the language of the contract is a matter for the parties and their counsel.
How many requirements should a BMS specification contain?
There is no right number: the count follows the plants, zones and interfaces. The template above carries 45 functional, 22 hardware and 15 network requirements for a fictitious administrative building.
Does the specification need to name an ISO 52120-1 class?
It should. "Compliant with the BACS decree" leaves bidders to choose the functions. Naming the target class of ISO 52120-1:2021 and listing the functions that justify it makes the energy performance chapter priceable and testable.