17
DraftS05-CON-010v0.1Source imported
Section 73 of 102
72. Operational History and Data Provenance
Stable section ID: S05-CON-010-SECTION-73 · 31 content blocks
System05 shall preserve sufficient Operational History to reconstruct material building conditions, decisions, commands, changes, and interventions.
Operational history may include:
- State transitions.
- Sensor observations.
- Commands and feedback.
- Agent recommendations and actions.
- Human approvals.
- Overrides.
- Alarms.
- Maintenance.
- Inspections.
- Component replacement.
- Configuration changes.
- Cybersecurity events.
- Emergency operations.
- Recovery actions.
Data Provenance shall identify:
- Who or what created the record.
- Source system.
- Creation time.
- Applicable component or building.
- Original data type.
- Processing or transformation history.
- Version.
- Integrity status.
- Authority level.
- Confidence.
- Supporting evidence.
- Subsequent corrections.
Corrections shall not erase the original record when the original is required for audit, safety, contractual, or regulatory purposes. Instead, the correction shall be linked to the earlier record with its reason and authority.
Retention periods shall reflect safety, lifecycle, privacy, warranty, legal, and operational requirements. Personal information shall not be retained merely because storage is technically available.