Section 75 of 102
74. Dependency Representation
Stable section ID: S05-CON-007-SECTION-75 · 40 content blocks
A Dependency defines a condition in which one Entity, function, state, or capability requires another Entity, resource, service, or condition.
Each Dependency shall define:
Dependency ID;
dependent Entity;
required Entity or capability;
dependency Type;
criticality;
minimum required capacity;
permitted interruption duration;
fallback;
loss behavior;
restoration sequence;
lifecycle applicability.
Example:
dependency HVAC_Power_Dependency {
dependent: @HVAC_Cartridge_01;
requires: @Electrical_System.power_capability;
minimum_capacity: 4.5 kW;
criticality: operational;
on_loss: controlled_shutdown;
}
Dependencies may be:
mandatory;
optional;
conditional;
redundant;
temporary;
commissioning-only;
emergency-only.
Common dependencies shall be represented explicitly:
- shared_dependency Control_Network_Dependency {
- required_by: [
- @HVAC_Cartridge_01,
- @Lighting_Controller_01,
- @Utility_Controller_01
];
provider: @BIOS_Control_Network;
}
- Two systems shall not be considered redundant if they depend upon the same unprotected resource.
- Circular dependencies shall be detected and evaluated for startup, shutdown, recovery, and failure conditions.