Building BIOS Architecture

The Event Architecture provides the mechanism through which significant building occurrences are created, validated, transmitted, processed, stored, and consumed.

Every event shall follow a standardized envelope containing:

Event ID;

event type and version;

source identity;

subject identity;

building and location;

timestamp;

sequence number where applicable;

current configuration version;

preceding and resulting state;

severity;

measured or declared values;

data quality;

evidence reference;

required acknowledgment;

retention classification;

digital integrity information.

The architecture shall support:

real-time event delivery;

delayed delivery;

offline event storage;

ordered local sequences;

event replay;

filtered subscriptions;

event acknowledgment;

event correlation;

historical queries.

Event producers shall not determine final operational consequence unless they possess the required authority. A sensor may produce a high-temperature event, while the Policy Engine determines whether that event requires warning, shutdown, or emergency isolation.

The architecture shall prevent:

silent event loss;

duplicate processing of non-idempotent actions;

uncontrolled event storms;

low-priority events blocking critical events;

unauthorized event injection;

alteration of accepted historical events.

Events affecting configuration, safety, security, commissioning, maintenance, or control authority shall be preserved with higher integrity and retention requirements than routine telemetry.