← All perspectives
Surveillance Protocols Map Alerts

Source availability: know what stopped reporting

A flat curve may be a connection failure, not zero consumption. Monitoring source health avoids decisions on incomplete data.

Octowise Team

Server room whose data source availability must be monitored

A flat curve may be a connection failure, not zero consumption. Deciding on incomplete data means underestimating a drift or celebrating a “saving” that does not exist. Octowise exposes each source’s status per building (connected, error, paused, never synced) and can color the portfolio map accordingly.

Silence is not a data point

Energy dashboards often treat the last known point as if it were still true. A source down for three days skews signatures, operating conditions, and tertiary-decree baselines. The first reflex should be: “is it still reporting?”

Octowise statuses make that question visible in source lists (search, filter, record detail) rather than in an integrator log reserved for IT.

Portfolio visibility

The building map can color markers by source status. Blind sites appear before poorly rated DPE sites. That is often the right order of work: without data, no honest energy arbitration.

Lists let you filter by status and assign fixes. A building “in error” is no longer a feeling; it is a work item for the operator or integrator.

  • Statuses: connected, error, paused, never synced.
  • Portfolio map colored by source health.
  • Filterable lists to prioritize recovery.

Alert before the gap widens

A disconnected source can trigger a configurable alert, distinct from a consumption alert. You do not wait for the monthly review to discover the sports-hall meter has been silent since summer.

Availability history helps distinguish an incident (fiber cut, UPS) from structural drift (saturated controller, unstable VPN, an API key that expires every quarter).

A prerequisite for AI and compliance

Seasonal signatures, operating conditions, OPERAT pack: all assume continuous collection. Showing availability next to the AI score avoids commenting on a “healthy” building that is simply mute.

It is also an operations argument: the BMS is not “installed”, it is available. The integrator contract is discussed on that criterion, not only on acceptance day.