Solutions
Cost ReductionESG & ComplianceTenant Billing & EngagementProperty ManagementPortfolio OperationsUtility Data API
Product
PlatformElectricity MonitoringWater MonitoringGas MonitoringHeat MonitoringData SourcesHardwareUtility ConnectorsThird Party Infrastructure
Industries
All industriesLogisticsRetailOfficeResidentialHospitality
Case StudiesBlogPartners
NLPLDE
Book a Demo
Netherlands · EPBD Article 14/15

GACS: mandatory Dutch building automation.

Since January 1, 2026, Dutch non-residential buildings with HVAC capacity above 290 kW must have a certified GACS system in place. Rhino monitors all the utility data a GACS system is required to track, report, and store.

What GACS stands for
Gebouwautomatiserings- en controlesysteem. The Dutch implementation of the building automation requirement in EPBD Article 14/15. Regulated by RVO and the Ministry of Housing and Spatial Planning.
Rhino platform — GACS compliance monitoring
Scope and applicability

Which buildings are in scope and what does GACS require?

The regulation is clear on the threshold, the deadline, and the technical obligations. Here is what applies to your portfolio.

At a glance
290 kW
HVAC installed capacity. Buildings at or above this threshold must have GACS in place.
1 Jan
2026. The date GACS entered force for non-residential buildings in the Netherlands.
3 yr
Minimum data retention. The system must store consumption data for at least three years.

Office buildings

All non-residential offices where the total installed HVAC capacity (heating, cooling, ventilation) exceeds 290 kW. Applies regardless of EPC rating.

Logistics and industrial buildings

Warehouses, distribution centers, and industrial facilities with HVAC above the 290 kW threshold. Common in large logistics portfolios.

Retail, hospitality, and healthcare

Shopping centers, hotels, and healthcare facilities above the HVAC threshold. Residential buildings and small-scale commercial properties under 290 kW are excluded.

Educational and public buildings

Schools, universities, and government buildings that meet the HVAC threshold. Public-sector building owners are among the first to face enforcement review.

Is your building in scope?
If your non-residential building has HVAC above 290 kW, you needed a GACS system from January 2026. Talk to us about getting compliant.
Talk to Sales
Technical requirements

What a GACS system must be capable of.

The regulation specifies five functional requirements. The system must be able to perform all five to qualify as compliant.

Monitor per energy carrier

Continuous monitoring of energy consumption per energy carrier (electricity, gas, heat) and per technical system within the building. Not totals only: the data must be broken down by carrier and system.

See the platform

Detect and report anomalies

When consumption deviates significantly from expected levels, the system must notify the building operator automatically. Passive logging without alerting does not satisfy this requirement.

See platform alerts

Communicate with smart meters

The system must be capable of communicating with smart meters and the energy grid. This enables real-time data collection via P1 interfaces, WMBus, BACnet, or equivalent protocols.

See utility connectors

Generate periodic reports

The system must produce periodic energy performance reports, at minimum monthly, that the building operator can review and act on. These reports must cover consumption per carrier and flag efficiency trends.

See ESG & Compliance

Retain data for at least three years

All consumption data collected by the GACS system must be retained and accessible for a minimum of three years. This data must be available to enforcement authorities and building auditors on request. Cloud-stored data with an audit-accessible export satisfies this requirement.

See the Utility Data API
Rhino's role

Rhino covers every GACS requirement out of the box.

The technical specification that GACS requires maps directly to what Rhino does. Here is how each requirement is met.

Energy consumption per carrier and system

Rhino collects electricity, gas, water, and heat data at meter level. Meters can be assigned to systems, zones, and floors. The platform breaks consumption down by carrier and building area, exactly as GACS requires.

Anomaly detection with operator alerts

Rhino's alarm system flags consumption that exceeds configurable thresholds and sends notifications to building operators by email or in-platform alert. Alarms are logged with timestamps and deviation data for audit purposes.

Smart meter communication

Rhino connects to P1 ports on Dutch smart meters (DSMR standard), reads WMBus devices, and integrates with BACnet and Modbus systems. For meters without a direct connection, Rhino's own compact hardware devices install alongside existing infrastructure.

Periodic energy performance reports

Rhino generates automated consumption reports on configurable schedules (daily, weekly, monthly). Reports include consumption per energy carrier, period-over-period comparisons, and efficiency trend data. Delivered by email or accessible in the platform.

Three-year data retention

All metered data is stored in Rhino's cloud platform with no retention limits during your active subscription. Historical data is accessible via the dashboard, exportable to CSV, and available via the Utility Data API for external audit systems.

How Rhino connects to your building
Software-only: for buildings with P1-enabled smart meters, Rhino connects via the P1 port. No additional hardware. Active within days of setup.
Own hardware: for meters without a direct software connection (older gas, water, or heat meters), Rhino installs compact access points and end devices alongside the existing meter. No meter replacement needed.
WMBus / BACnet / Modbus: for buildings with existing BMS infrastructure or wireless meter networks, Rhino reads directly from the existing signal without additional hardware.
Low CAPEX: in all cases, Rhino connects to existing infrastructure. There is no need to replace meters, rewire systems, or install a separate BACS gateway. For most Dutch commercial properties, the total CAPEX is limited to hardware for meters that do not yet communicate digitally.
Common questions

GACS compliance, answered.

GACS (Gebouwautomatiserings- en controlesysteem) is the Dutch implementation of the EPBD Article 14/15 building automation requirement. It applies to non-residential buildings where the installed HVAC capacity exceeds 290 kW. This includes offices, logistics buildings, retail centers, and other commercial properties above the threshold. Hotels, healthcare facilities, and educational buildings are also in scope if their HVAC systems meet the threshold. Residential buildings are excluded. The requirement entered force on January 1, 2026.
A GACS system must continuously monitor energy consumption per energy carrier and per technical system. It must detect anomalies and notify the building operator automatically. It must log and retain all consumption data for a minimum of three years. It must communicate with smart meters and the energy grid. And it must generate periodic energy performance reports, at minimum monthly, for the building operator. All five functions must be present for the system to be compliant.
Non-compliance can result in enforcement action from local authorities (bouw- en woningtoezicht) and fines. RVO oversees the regulation and provides guidance. Beyond enforcement risk, non-compliance also affects EPC ratings and creates gaps in the metered data that CSRD energy consumption disclosures require. The GACS requirement is active: the compliance date of January 1, 2026 has passed, so buildings above the threshold that lack a qualifying system are already in breach.
GACS sits alongside BENG within the Netherlands' EPBD implementation. BENG (Bijna Energieneutrale Gebouwen) sets near-zero energy performance standards for new builds, calculated using the NTA 8800 methodology. GACS addresses existing large non-residential buildings and requires monitoring and automation infrastructure regardless of their BENG or EPC rating. A building can be fully BENG-compliant and still need GACS if its HVAC capacity exceeds 290 kW. The two standards apply at different points in the building lifecycle and are additive, not alternative.
Rhino meets the technical requirements set out in the GACS specification. It monitors energy consumption per carrier at meter and zone level, generates automated alerts when consumption deviates from expected patterns, retains historical data for multiple years, communicates with P1 smart meters and WMBus devices, and produces periodic consumption reports. For buildings with smart meters already installed, Rhino can be connected via software without new hardware. We recommend confirming specific compliance applicability with your energy advisor or RVO, as building-specific circumstances may apply.

GACS compliance starts with the right data.

If your non-residential building in the Netherlands has HVAC above 290 kW, you needed a GACS system in place from January 1, 2026. Rhino connects to your smart meters via software and covers every technical requirement from day one.

Further reading

From the Rhino blog.

All articles