Since 29 May 2026, BACS in EU non-residential buildings must support IEQ monitoring as well as energy monitoring under EPBD Article 13(10)(d) — a scope that began above 290 kW on 31 December 2024. An IEQ monitoring BMS must land zone temperature, humidity and ventilation evidence, with timestamps, in one system rather than a thermostat app.
Short answer
Article 13(10)(d) requires the BACS to be capable of monitoring indoor environmental quality, not controlling it. Practically that means zone-level temperature, humidity, ventilation rate or a documented proxy, and contaminant data where those sensors exist, each time-stamped and trended in one BMS that can export the record.
What changed, exactly: Article 13 in plain language
The recast Energy Performance of Buildings Directive, Directive (EU) 2024/1275, set a general transposition deadline of 29 May 2026. Article 13 decides which non-residential buildings must have a building automation and control system (paragraph 9) and what that system must be capable of (paragraph 10): monitoring, logging and analysing energy use; benchmarking against a reference; interoperating across proprietary technologies; and monitoring indoor environmental quality.
The four capabilities are cumulative. A BACS that only switches plant is no longer sufficient, because the record has to be interrogable by a third party — which is why the monitoring clauses change hardware lists more than the control clauses do.
13(9): the 290 kW and 70 kW thresholds
Non-residential buildings whose HVAC systems exceed an effective rated output of 290 kW must have a BACS, an obligation that applied from 31 December 2024; from 31 December 2029 the threshold drops to 70 kW (eu.bac, 29 May 2026). The trigger is rated plant output, not floor area, so scoping starts with the plant schedule: a compact building with large plant can be in scope while a larger, lightly serviced one is not.
13(10)(d): IEQ monitoring from 29 May 2026
Paragraph 10(d) requires the BACS to be capable of monitoring indoor environmental quality. It asks for capability rather than a performance guarantee, and the obligation attaches to the building's BACS, not to a single device. National transposition decides how strictly parameters and evidence are defined, which leaves a practical question: which points exist, where do their values land, and can you produce them six months later?
The four IEQ parameters and how to instrument each
The working descriptions are air temperature, relative humidity, ventilation rate and contaminants. Only the first two come routinely from HVAC control hardware; the last two are where specifications go wrong, because those instruments are usually bought by someone else.
Temperature and humidity: zone thermostat vs dedicated sensor
Where a zone already has a networked fan coil thermostat, it is the cheapest temperature point on the project: the device is powered, addressed and polled, and the value it reports is the value its control loop acts on. The TFHV-SK-FVVMD-S3-CK-M publishes room temperature and humidity over Modbus RTU at 9600 bps as an RS-485 slave; the wireless TFHV-SK-FVVMD-S3-CK-Z carries the same readings over a ZigBee 2.4 GHz link; the ZB-T9000 panel combines ZigBee and Modbus RTU in a room controller.
A dedicated sensor is better where humidity matters in its own right, or where the thermostat reads return air instead of occupied space. ZB-TnRH measures temperature and humidity on ZigBee and Modbus RTU (RS-485) and is configured from a PC. We publish no accuracy class for it, so agree the measurement uncertainty your evidence pack needs and record model, mounting height and position in the point schedule.
Ventilation rate and contaminants: what a controls vendor can and cannot supply
Matinal does not manufacture a CO₂, VOC or particulate sensor, and none is in our catalogue. ZB-TnRH measures temperature and humidity only. A specification reading "CO₂ monitoring by the controls supplier", written against our range, will not be met by a Matinal product, and we would rather say so before the submittal than during commissioning.
What the control layer does is carry, timestamp and store someone else's measurement. A third-party CO₂, VOC or particulate transmitter with a 0–10 V or 4–20 mA output can land on an analogue input — six universal inputs on IOM-633 and P-IOM633, twelve on MVC-WMB-1866BA — and becomes an ordinary BMS point with a name, a log and an alarm limit. Ventilation rate itself is rarely measured in a zone. It is evidenced by proxies: CO₂ as an occupancy-linked proxy, duct air velocity from a hot-film transmitter such as EE65 (0–10, 0–15 or 0–20 m/s ranges), differential pressure from a Dwyer MS series transmitter (50 Pa to 5 kPa), and damper or fan status from the controller. Each is evidence of a proxy, not a measurement of ventilation rate, and the evidence pack should name the proxy used.
Table 1. IEQ parameter, instrument and evidence artefact. Interfaces are as specified on the products named; none of these devices satisfies Article 13(10)(d) alone.
| IEQ parameter | Instrument | Protocol / interface | Evidence artefact |
|---|---|---|---|
| Air temperature, per zone | Fan coil thermostat (TFHV-SK-FVVMD-S3-CK-M, TFHV-SK-FVVMD-S3-CK-Z, ZB-T9000) or ZB-TnRH sensor | Modbus RTU, 9600 bps over RS-485; ZigBee with Modbus register read/write (0x0003H, 0x0006H) | Per-zone trend log at a fixed interval, exported as CSV with timestamps |
| Relative humidity | ZB-TnRH temperature and humidity sensor | Modbus RTU (RS-485); ZigBee | Humidity trend plus monthly minimum and maximum per zone |
| Ventilation rate — proxy 1 | Third-party CO₂ transmitter (not a Matinal product) | 0–10 V or 4–20 mA into an analogue input on IOM-633, P-IOM633 or MVC-WMB-1866BA | Concentration trend, alarm limits, sensor model and calibration date |
| Ventilation rate — proxy 2 | Duct air velocity transmitter, e.g. EE65; differential pressure transmitter, e.g. Dwyer MS series | 0–10 V or 4–20 mA into an analogue input; Modbus RTU or BACnet from the controller upward | Velocity or ΔP trend with the derivation to airflow documented in the O&M |
| Contaminants (VOC, particulate) | Third-party transmitter (not a Matinal product) | 0–10 V or 4–20 mA into an analogue input channel | Trend log with range, alarm threshold and the assumption behind it |
Proving it: trend logs, timestamps and exportable evidence
Compliance is argued from records, so the trend log is the deliverable, not a by-product. Seven things decide whether it survives scrutiny.
- A point, not a paragraph. Every parameter maps to a named point: object or register, units, range, location, sensor model.
- A declared interval. Fifteen minutes is a defensible default for zone temperature and humidity; shorter intervals cost storage without changing conclusions.
- Time synchronisation. One time source for the site, stated in the handover (BACnet time synchronisation or NTP), with the daylight-saving rule written down.
- Buffer depth sized on purpose, so a month of network outage cannot erase the period you must prove.
- Retention and export. A CSV export path, an agreed retention period, and a test export during commissioning.
- Alarms, not just numbers, so an out-of-range period is flagged when it happens rather than found in a spreadsheet.
- Ownership. The log belongs to the building owner: hand over credentials and the export procedure, not a screenshot.
Log storage is a head-end function: controllers hold configuration, and the long record lives in the BMS.
Where fan coil control meets IEQ (and where it doesn't)
The thermostat is the natural home for zone temperature. It is already installed, addressed and polled, and its measured value is the one the loop acts on. The Climate Control range covers that layer: the TFHV-SK-FVVMD-S3-CK-M fan coil thermostat with Modbus RTU RS-485 and dual-sensor cascade PI control, the TFHV-SK-FVVMD-S3-CK-Z wireless fan coil thermostat on ZigBee 2.4 GHz, and the ZB-T9000 ZigBee thermostat panel at 185–265 VAC.
Where that layer stops is equally clear. A thermostat cannot measure ventilation rate, CO₂, VOC or particulates, and it cannot supply the inputs behind PMV and PPD — operative temperature, air velocity, metabolic rate, clothing insulation. Adding a ZB-TnRH temperature and humidity sensor extends coverage to humidity and gives a second reading where mounting position is doubtful; it does not close the ventilation gap.
Consolidation is a separate decision from measurement. An MVC-WMB-1866BA intelligent field controller brings BACnet IP and MS/TP, two MS/TP and two Modbus RTU ports and twelve analogue inputs — the point where third-party transmitters meet the BACnet side of the building.
The wiring pattern is well established. A hotel guest room fan coil control scheme places one networked thermostat per room with central supervision; a university teaching building scheme scales the same idea across zones with different occupancy. Both are application scenarios showing how points are arranged. Neither is a measured compliance outcome, and neither should be cited as one.
The ASHRAE parallel: 90.1 splits efficiency from operational carbon
Europe is not moving alone. On 16 July 2026, ASHRAE announced that Standard 90.1 keeps energy efficiency as its core while the operational-carbon provisions from Addenda M and N move into a separate, aligned publication for the 2028 and 2031 cycles, with 153 committee members involved.
The logic is the same on both sides of the Atlantic: separate the design requirement from the measured outcome, and put the burden of proof on records. Article 13(10) describes BACS capability while measured performance sits in other instruments; 90.1 describes efficiency while a parallel document takes operational carbon. The device list proves capability; the trend data proves behaviour.
Claims discipline: EmpCo, BTL and what "certified" does not mean
Two habits cause most of the trouble here. The first is treating BTL certification as an efficiency endorsement. BACnet Testing Laboratories certifies conformance with the BACnet standard — interoperability, not energy performance — and more than 1,500 BTL-certified products exist worldwide (BIG-EU, August 2026). A certified product talks correctly; it does not save anything by itself.
The second is loose environmental language. The EU EmpCo Directive applies from 27 September 2026 and requires environmental claims to be substantiated, which rules out "IEQ-compliant thermostat" and unsupported percentage savings. EN ISO 52120-1 grades BACS capability into efficiency classes; a class describes what a system can do, not what it will save in a given building.
Our position is deliberately narrow. We state the protocol, the registers, the inputs and the supply range of a product; we do not claim that a thermostat or controller delivers IEQ compliance, because compliance belongs to the building's BACS and its records, and anything stronger needs measurement and verification on site.
Compliance checklist
Eight steps, in the order a project meets them. Each one produces a document, not a decision.
- Confirm scope against HVAC rated output — above 290 kW today, above 70 kW from 31 December 2029 — and file the calculation with the design intent.
- List the IEQ parameters the project will evidence, and name the proxy wherever a parameter is not measured directly.
- Choose an instrument per parameter per zone, including third-party transmitters, with model, mounting position and range.
- Map each instrument to a physical point, controller input or bus register, and write the interface into the point schedule.
- Bind every point to a named BMS object with consistent naming, units and range.
- Set the logging interval, time source, buffer depth and retention period, then test an outage and a restore.
- Configure alarm limits on temperature, humidity and any contaminant point, with an owner for each alarm.
- Export a twelve-month evidence pack — CSV trends, point schedule, sensor list, calibration dates — and hand it to the building owner.
Frequently asked questions
What does EPBD Article 13(10)(d) actually require?
That a BACS in scope can monitor indoor environmental quality — temperature, humidity, ventilation rate and contaminants — not that it must control them. The obligation attaches to the building's BACS, not to an individual device.
Which buildings are in scope?
Non-residential buildings above 290 kW of effective rated HVAC output since 31 December 2024, extending to those above 70 kW by 31 December 2029 (eu.bac, 29 May 2026). Check the plant schedule, not the floor area.
Do I need a CO₂ sensor?
CO₂ is the common proxy for ventilation rate, but the Directive names ventilation rate and contaminants conceptually, so check national transposition before treating CO₂ as mandatory. Matinal does not currently offer a CO₂ sensor — ZB-TnRH is temperature and humidity only. A third-party CO₂ transmitter can be carried on an analogue input and logged like any other point.
How does IEQ relate to EN ISO 52120-1?
The standard grades BACS capability into efficiency classes. Article 13(10) capabilities are what a compliant BACS must demonstrate; the class framework is one recognised way to describe that capability, and it is not a measurement of achieved savings.
Can fan coil thermostats carry IEQ data?
Yes for zone temperature, and for humidity where the device or a paired sensor measures it, provided the values are exposed on Modbus RTU or ZigBee. They cannot measure CO₂, ventilation rate or particulates, nor supply the full input set behind PMV and PPD.
How do I avoid over-claiming savings?
Separate certification from performance. BTL certifies BACnet conformance, not energy efficiency, and from 27 September 2026 EU environmental claims must be verifiable under the EmpCo Directive. Claim the points, the logging and the protocol; measure the savings or leave them out.
Sources
- eu.bac, "EPBD transposition deadline: time to turn BACS requirements into practice", 29 May 2026 — https://eubac.org/news/epbd-transposition-deadline-time-to-turn-bacs-requirements-into-practice/
- ASHRAE, "ASHRAE strengthens Standard 90.1 foundation with renewed emphasis on commercial building energy efficiency", 16 July 2026 — https://www.ashrae.org/about/news/2026/ashrae-strengthens-standard-90-1-foundation-with-renewed-emphasis-on-commercial-building-energy-efficiency
- BIG-EU, "BIG-EU insights", BACnet Journal newsletter, August 2026 — https://news.bacnetjournal.org/newsletter/august-2026/big-eu-insights/