OPERAT: from local preparation to declaration
XLSX pack, OPERAT identity, deadline reminders: reduce regulatory friction without outsourcing the manager's responsibility.
Octowise Team
The OPERAT declaration always arrives at the wrong time: incomplete data, disputed surfaces, energy vectors to reassemble, an attestation to find again. Octowise does not declare on the manager’s behalf. It structures preparation per building, pre-fills the XLSX pack, tracks connection status, and reminds teams of deadlines, including via push.
Reduce friction, not responsibility
The declarant remains responsible for what is sent to OPERAT. What Octowise removes is the yearly reconstruction of the file from emails and diverging spreadsheets. Surfaces, vectors, trajectories, and OPERAT identity live on the tertiary-decree record, next to the rest of the building.
The seven-step indicator makes blockers visible: missing baseline, missing climate zone, incomplete pack. You stop discovering the gap three days before the deadline.
A pack ready to complete
The XLSX pack is generated from portfolio data already captured. It remains a regulatory deliverable, not an “internal” export. The value is consistency: the surface used for OPERAT is the same as on the building record, not a “declaration version” copy.
Optional climate adjustment and degree days, when filled in, avoid the classic back-and-forth between the engineering firm and the manager when freezing the baseline.
- Pre-fill from the portfolio (surfaces, vectors, trajectories).
- 7-step readiness indicator per building.
- XLSX pack download without a parallel spreadsheet.
- Deadline reminders via scheduled scan and push alerts.
Connection and declaration tracking
When the OPERAT platform connection is configured, declaration status is read in Octowise rather than in a forgotten browser tab. The portfolio compliance view aggregates delays for energy / portfolio leadership.
A scheduled job (declaration-due scan) generates OPERAT-type alerts. On mobile, that type toggles independently from surveillance alerts: you can be reminded of a declaration without receiving every HVAC alarm.
OPERAT in the Measure → Act cycle
Preparing OPERAT without actually measuring consumption means declaring a poorly observed past. Hence the link to data sources, signatures, and action plans: the yearly declaration is no longer a disconnected exercise, but a checkpoint in continuous management.
Conversely, a clean OPERAT pack does not by itself improve a drifting site. Alerts and action plans remain the lever versus 2030–2050 targets.