Tertiary decree and BACS: structuring compliance per building
2030–2050 trajectories, BACS register, ADEME DPE linkage: compliance works when each building has an actionable record, not an isolated spreadsheet.
Octowise Team
The tertiary decree and the BACS decree cannot be managed in an isolated spreadsheet. They require a per-building record: subject status, baseline, 2030–2050 trajectories, OPERAT identity, BMS functions, HVAC capacities, inspections. Octowise consolidates those pieces in the same portfolio repository as consumption, alerts, and action plans.
What the regulation actually requires
France’s Éco Énergie Tertiaire scheme requires consumption reductions on subject tertiary buildings, with 2030, 2040, and 2050 targets declared through OPERAT. The BACS decree requires, according to technical-system power tiers, the installation or upgrade of a building automation and control system, with inspection deadlines.
In practice, the hard part is not knowing the texts. It is knowing, for each asset in the portfolio, where the file stands, what is missing, and which deadline is closest, without rebuilding the information before every steering meeting.
An actionable tertiary-decree record
Octowise structures the tertiary-decree record per building: surfaces, energy vectors, reference baseline, optional climate adjustment, targets, and OPERAT identity. A seven-step indicator shows preparation progress, rather than an overly binary “done / not done” checkbox.
The OPERAT XLSX pack is pre-filled from data already captured. That does not replace the declarant’s responsibility, but it removes double entry and gaps between the declaration spreadsheet and the portfolio system.
- Subject status and 2030 / 2040 / 2050 trajectories documented on the building record.
- OPERAT identity (surfaces, vectors, attestation) in the same file.
- Downloadable XLSX pack, pre-filled from portfolio data.
- Upcoming declaration alerts, including mobile push.
A structured BACS register, not a PDF annex
Octowise’s BACS register documents BMS functions, nominal HVAC power, regulatory tiers, deadlines, and inspections. It underpins a BACS AI analysis distinct from general building analysis, and it relies on a confirmed ADEME DPE.
Without this register, teams pile attestations and diagrams in a shared folder. With it, deadlines become alerts, and compliance status can be read in the portfolio view alongside OPERAT status.
The multi-building compliance overview
The compliance page aggregates, across the portfolio, OPERAT status, BACS tier, overdue inspections, and DPE records nearing expiry. It is the executive review tool: which sites are ready, which ones block declaration, which ones risk a BACS deadline.
That view is only valuable if each building file is up to date. Hence the need to link DPE, tertiary decree, BACS, and alerts in the same system, rather than multiplying “committee version” files.