17
DraftS05-CON-014v0.1Source imported
Section 31 of 105
30. Preconditions, Triggers and Context
Stable section ID: S05-CON-014-SECTION-31 · 23 content blocks
- Rules may depend on preconditions, events, or contextual states.
- Preconditions define what must already be true before the Rule can be evaluated or an activity can begin.
Triggers may include:
- Design release.
- Manufacturing completion.
- Interface connection.
- Installation.
- Commissioning.
- Detected incompatibility.
- Damage or overload.
- Sensor alarm.
- Inspection finding.
- Maintenance interval.
- Configuration change.
- Software update.
- Ownership transfer.
- Hazard or regulatory change.
- Removal or reuse.
- Emergency declaration.
Context may include normal operation, temporary construction, maintenance mode, degraded operation, emergency mode, transport, storage, or post-event recovery.
Triggers shall be observable, declared, or derivable from controlled evidence. Safety-critical action shall not depend solely on an unavailable cloud service, uncertain AI inference, or a single unverified sensor.
Where several Rules are triggered by the same event, their execution order and dependencies shall be defined.
A missed trigger shall be recorded as a potential nonconformity and shall not be erased by later completion without review of the period of uncontrolled exposure.