BBM-STD-88-HEALTH_AND_SAFETY_INFORMATION-V0.1 | Office standard | 4 November 2026 | V0.1 | Private controlled WIP draft for office review
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-11-04 | First issue: closes rows (safety part), (IM-07 source),,, (H&S duties part),,,, (H&S flag/ID) (ISO 19650-6 content; §1.3 row "Health & safety information per ISO 19650-6:2025") + cross-doc pointer pass: BBM-STD-51 §3 register ID ED-ISO19650-6 cited; AIR row AIR-009 named |
1 Purpose ownership and scope#
This standard applies ISO 19650-6:2025 (edition 1, published 13 Jan 2025; it replaced PAS 1192-6, withdrawn 23 Jan 2025) to office projects; its edition record is register row ED-ISO19650-6 in BBM-STD-51 §3. It sets how health and safety (H&S) information is required, produced as structured records in the model and CDE, reviewed, updated and handed to operation. It owns the H&S information requirements and the risk record fields. The Manual §9.4 and Annex W2 S4–S5 keep the procedure summary and the synthetic HSI forms; their HSI record fields are those in §4.
H&S information supports the competent designers and duty-holders; it does not transfer or waive any designer, contractor or operator duty, and a model check or clash pass does not show that a hazard is controlled. ISO 19650-6 clause pointers are reading directions; check the licensed text before claiming conformity.
2 H&S information requirements#
H&S needs enter the requirement chain at each level; each row carries an ID that the records in §4 cite.
| Level | Requirement to state | Owner document |
|---|---|---|
| OIR | Which H&S decisions the organisation must make over the asset life (safe operation, maintenance access, hazardous materials, emergency response, alteration and demolition) | BBM-STD-02 OIR |
| AIR | Row AIR-009 (H&S information): residual hazards; safe maintenance and access methods; hazardous materials and their locations; isolation points; information the operator needs to update the records | BBM-STD-52 AIR |
| EIR | Per exchange: which H&S records are due, record fields (§4), format (native model properties, IFC, register), review status, recipient | BBM-STD-54 EIR and LOIN; IDS checks per BBM-STD-89 |
| Appointment | H&S information duties, hazard register fields, exchange points and owner in the appointment form and the responsibility matrix | BBM-STD-55; BBM-STD-56 |
| Delivery plan | H&S record deliveries with an H&S flag and record IDs on the TIDP / MIDP rows | TIDP, MIDP |
3 Roles#
| Role | Duty |
|---|---|
| Design Safety Lead (competent, named per project) | Owns the project H&S record set during delivery; assigns hazards to designers; arranges independent review |
| Discipline designers | Identify hazards in their design, record the control chosen and the residual risk |
| Independent competent reviewer | Reviews significance, evidence and residual-risk wording before a record is shared |
| Information manager / LAP | Controls exchange metadata, CDE access and the H&S flag on deliveries; does not judge safety adequacy |
| Contractor | Adds construction-stage hazards and as-built changes to the records |
| Asset / operator safety owner | Receives the records at handover, acknowledges understanding and owns updates in operation |
Named holders are in the restricted Directory.
4 Structured risk records in the model and CDE#
One record per hazard, kept in the H&S register in the CDE and linked to model objects by stable ID. Model objects carry only the link fields and the short control text; the full record stays in the register.
| Field | Content |
|---|---|
| HazardID / revision | HSI-<PROJ>-nnn-Rnn |
| Hazard | Description, cause, event, consequence |
| Lifecycle activity | Construction, operation, maintenance, cleaning, replacement, alteration, demolition; exposed group |
| Location and object | Zone / space ID and stable object ID (Asset_ID,, or element GUID) |
| Source | Model / document container ID, revision, hash; origin date; uncertainty and assumptions |
| Control | Prevention or control chosen, evidence, responsible designer |
| Review | Independent reviewer, method, date, decision |
| Residual risk | Remaining risk wording, action, owner, due date |
| Requirement link | AIR / EIR row ID |
| Exchange | Exchange ID, recipient, acknowledgment status |
| Sharing | SensitivityClass (BBM-STD-87) |
Model link properties. BBM_HSI.HazardIDs (list of HazardIDs) and BBM_HSI.ResidualControl (short text) on the affected objects, defined in BBM-STD-72. For IFC exchange, the IFC risk property set (Pset_Risk) is a candidate mapping, used only after a test export and the project IDS show the receiver reads it (BBM-STD-74).
Safety and security can pull apart: H&S information must reach its duty-holders even when the asset is security-sensitive. Use an approved reduced derivative (BBM-STD-87 S3) that keeps the hazard, control and limits; never drop essential safety information for security reasons.
5 Review and update triggers#
Reopen and update the affected records, with one ChangeID, at:
| Trigger | Action |
|---|---|
| Design change at any stage gate or coordination round | Designers re-check hazards linked to changed objects; reviewer re-checks changed records |
| Construction method or sequence change (BBM-STD-79 links hazard IDs to activity and time) | Contractor adds or updates construction hazards |
| As-built deviation or site survey change | Update location, object and source fields |
| Handover | Full review before transfer (§6) |
| In operation: incident, inspection, maintenance-method change, replacement, alteration, decommissioning | Operator safety owner updates the record and the AIM (BBM-STD-75 §6) |
| Periodic building inspection under Dubai Law No. 3 of 2026, where it applies (BBM-STD-85 §4) | Inspection findings reopen the linked records |
A record never gets overwritten as if it always passed: the old revision stays, and the new revision records why it changed.
6 Handover to operation#
At handover the Design Safety Lead and contractor deliver the H&S register, the linked models and the related documents as one exchange in BBM-STD-75. The receiving test checks: every open hazard has an owner and action; every record links to a live object or space in the AIM; source revisions match the as-built set; residual-risk wording survives in every format (native, IFC, register). The operator safety owner records acknowledgment: received version and hash, understanding of constraints, accepted or rejected with reason, update owner and next review trigger. A delivered link or read receipt is not acknowledgment. An unresolved mandatory hazard or missing acknowledgment holds the affected operation, not the whole handover. Records are kept as the safety record class in BBM-STD-76, retention per BBM-STD-90.
References#
- ISO 19650-6:2025, edition 1, 13 Jan 2025: https://committee.iso.org/standard/82705.html, checked 2026-11-04.
- PAS 1192-6 withdrawn 23 Jan 2025, as recorded in BSI Knowledge (source key BS1192-LEGACY in §3).
- ISO 16739-1:2024 (IFC 4.3.2.0) for property-set mapping: https://www.iso.org/standard/84123.html, checked 2026-11-04.
- Office: Manual §9.4 and Annex W2 S4–S5, BBM-STD-02, BBM-STD-52, BBM-STD-54, BBM-STD-75, BBM-STD-76, BBM-STD-87;.