17
DraftS05-CON-010v0.1Source imported
Section 67 of 102
66. Operational Events and State Transitions
Stable section ID: S05-CON-010-SECTION-67 · 42 content blocks
Material changes in building condition shall be represented as Operational Events.
Operational Events may include:
- Sensor observations.
- Threshold crossings.
- Commands.
- Equipment responses.
- Alarm activations.
- Component insertion or removal.
- Interface lock changes.
- Configuration changes.
- Occupancy-mode changes.
- Agent actions.
- Human overrides.
- Maintenance actions.
- Inspection results.
- Communication failures.
- Cybersecurity events.
- Emergency declarations.
- Recovery milestones.
Every material event should identify:
- Event identity.
- Source.
- Time.
- Affected component or zone.
- Previous state.
- New state or requested state.
- Evidence.
- Confidence.
- Initiating authority.
- Related command or task.
- Operational consequence.
- Required acknowledgment or response.
State transitions shall occur only through recognized transition rules. Transitions affecting safety, authority, configuration, or protected systems may require additional evidence, approval, or verification.
An event indicating a transition shall not always prove that the transition completed. System05 shall distinguish between:
- Transition requested.
- Transition authorized.
- Transition initiated.
- Transition physically observed.
- Transition verified.
- Transition failed.
- Transition reversed.
Events shall remain ordered, correlated, and traceable so that the sequence leading to an operational condition can be reconstructed.