Section 66 of 102
65. Safety System Representation
Stable section ID: S05-CON-007-SECTION-66 · 47 content blocks
A Safety System is a coordinated set of Components, Interfaces, rules, detection functions, protective actions, alarms, and evidence intended to prevent or limit harm.
Safety Systems may include:
fire detection;
fire suppression;
smoke control;
emergency lighting;
electrical protection;
gas detection;
water-leak isolation;
structural monitoring;
pressure relief;
emergency access;
robotic safety;
security and intrusion protection.
Each Safety System shall define:
Safety System ID;
protected hazard;
protected Zone;
initiating conditions;
sensors;
decision logic;
protective devices;
actuators;
alarms;
manual controls;
dependencies;
redundancy;
response time;
safe state;
test requirements;
authority;
certification.
Example:
safety_system Water_Leak_Protection {
hazard: uncontrolled_water_release;
protected_zone: @Kitchen_Zone;
- detection: [
- @Kitchen_Leak_Sensor_01,
- @Kitchen_Flow_Anomaly_Sensor
];
protective_action: close(@Kitchen_Branch_Shutoff);
local_controller: @Leak_Protection_Controller;
manual_override: @Kitchen_Manual_Shutoff;
}
The BDL declaration describes the required safety architecture. It shall not replace certified safety-system implementation or testing.
Safety dependencies shall be visible. A protective action shall not depend upon the same failure condition it is intended to control unless redundancy or independent protection is provided.
Bypass, impairment, inspection, and restoration states shall be represented explicitly.