BBM-STD-60-MEP_MODELLING-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft for office review
Revision history
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-10-16 | Initial controlled WIP draft. |
| V0.2 | 2026-11-04 | Closed audit rows: UAE FLS 2018 fire basis and Civil Defence route, 2.1 green-rating data (Al Sa'fat/Estidama), utility regulation record; IMI Framework naming; current set links; spacing fixes + cross-doc pointer pass. |
1 Common identities scope and information need#
This standard addresses, and with separate HVAC, electrical/ELV and plumbing/fire annexes. Mechanical, electrical and public-health/fire competent design leads retain their design/calculation duties; model authors implement approved information, independent discipline reviewers verify it, and the BIM Coordinator manages interfaces. Use BoD, EIR and LOIN, coordinates, templates, properties, Manual and BEP. The editable MEP pack supplies LOIN, HVAC, Electrical, Plumbing fire, Interfaces, Checks, Tests and Acceptance with blank counterparts.
Keep canonical Asset_ID for applicable maintainable occurrences, SystemID and SpaceID as stable relational keys under the dictionary. Map native system names/classifications, circuit/panel IDs and MEP space identities explicitly; a same-looking label is not a proven shared definition. Existing System_ID/Location_ID exchange aliases remain controlled BBM-STD-72 mappings, not a new parameter set. Map each MEP space to current architectural room/SpaceID/phase/revision and analytical zone/calculation owner, allowing justified aggregation. Preserve identity through exports, splits and replacements; retired assets are not silently reused.
For every discipline/use/stage/exchange record requirement IDs, object/system/space scope, geometry/data/documents, author/checker, recipient, exclusions and acceptance method. Coordination geometry includes required insulation and task envelopes. Calculation models require independently reviewed analytical inputs. Fabrication and authority submission are separate profiles activated only when appointed. Exact authoring/exporter/receiver builds, schema/presets, units, template and family hashes must be qualified on isolated copies. No native system, schedule or connector is created by this writing pack.
2 HVAC annex#
Use approved categories for equipment, terminals, ducts/pipes, fittings, accessories and insulation. Record SystemID, service/classification, type, phase, level/reference offset, actual geometric elevation meaning, material, section/nominal size, lining/insulation, design flow/temperature/pressure where required, calculation source and revision. Elevation may refer to centreline, top/bottom of bare service or outside insulation; label it explicitly. Distinguish ventilation demand, selected design flow and computed network flow. The competent mechanical engineer approves sizing method, friction/velocity limits, diversity, loss coefficients and equipment duty; a modeller cannot turn a schematic diameter into approved sizing.
Connectors require domain, system classification/type, position/orientation, shape/size, logical flow direction and configuration, parameter association/units and intended connected pair. The connection arrow shows connection orientation; verify calculated flow direction separately in the actual build. Confirm real connectivity and propagation in system browser/itemised schedules, not only coincident geometry. Test multiple connectors, primary/linked behavior where supported, equipment supply/return separation and declared intentionally open ends. Unexplained disconnected/foreign-system connectors fail affected scope. Rehosting/reloading a family must preserve source associations and existing instance values or undergo controlled migration.
SYN-H60 has AHU-060 on system SYN-SA60 serving terminals AT01/AT02, each expected 600 L/s, total 1200 L/s=1.2 m3/s. This is a synthetic conservation/conversion check, not ventilation or duct-sizing design. A connector reporting 1200 m3/s without conversion fails. The approved source requirement for the fixture is REQ--H R01; actual operating pressure, size and energy adequacy remain unverified until the engineer supplies design evidence. Check access to filters/coils/valves, withdrawal routes, lifting/task space and adjacent structure; generic box clearance is insufficient where the actual maintenance task needs another direction or route.
2.1 Green-rating data#
Statutory ratings set energy and water requirements that MEP model data must evidence: Al Sa'fat 2nd edition (January 2023): Silver Sa'fa is mandatory for all new buildings in Dubai; Estidama Pearl Rating System: minimum 1 Pearl for private and 2 Pearl for government-funded projects in Abu Dhabi (DMT, 8 January 2025; statutory minimums owned by BBM-STD-57 §2 and BBM-STD-85 §7). Carry system efficiency, water-fixture flow rates and metering points as model properties linked to the rating credit, the BoD criterion and BBM-STD-81. The rating edition and credit criteria are read from the rating system at project start; this standard sets no numeric value.
3 Electrical and ELV annex#
Keep panel, distribution system, circuit and connected-device IDs stable and traceable to Asset_ID/SpaceID where applicable. Record voltage, phase, poles, frequency, apparent/active power and power factor where required, connected versus demand load, approved diversity source, protective-device/cable assumptions and calculation reference. Electrical engineer owns loading, voltage drop, short-circuit, protective coordination, earthing and life-safety power design. Revit panel totals and a nominal connector load are information checks, not those engineering calculations. Record exact unit and stage of each value; VA is not interchangeable with W without the approved power factor context. Utility authority regulations for the plot (for example DEWA in Dubai or the Abu Dhabi distribution utility) are recorded by BBM-STD-51 §3 register ID with title, edition and source-check date; their titles and editions are not confirmed in this revision and are entered at project start. Panel and load schedules carry the utility's required fields.
Model containment, conduits/trays, bend/segregation interfaces and equipment access to purpose-led geometry; declare whether circuits are logical, physical routing or both. Routing lines alone do not prove connection. Schedule panel name/number, all circuit rows and loads from the same frozen revision. Check duplicate circuit references, unassigned devices, spare/space treatment, phase allocation, schedule filters and actual load totals. SYN-E60 is a single-phase arithmetic fixture with three circuits of 1000 VA each on SYN-PNL60: connected total 3000 VA. REQ--E requires exact integer-VA reconciliation in this exercise; it sets no cable, breaker or actual capacity requirement. Removing a circuit must change the itemised total to 2000 VA and be detected against the required three-circuit scope, even if the displayed schedule still looks complete.
ELV annex covers data, security, BMS and other appointed systems through explicit specialist boundaries. Record each device/network/system identity, logical/physical connection scope, space/location, supply/interface and responsibility. Fire alarm, emergency lighting, security and access-control dependencies require the relevant specialist design and authority route; do not infer them from a generic ELV symbol. Restrict security-system information by the Manual §9.4 sensitivity/access process. Specialist shop/fabrication and commissioning data are separately identified future requirements.
4 Plumbing drainage and fire annex#
Separate potable, non-potable, hot/cold, return, waste, vent, storm, fuel and fire services by approved system classification and design source. Record equipment/fixture IDs, service, material, size, design flow/pressure/temperature, insulation, valve/fitting identity and calculation provenance as applicable. The public-health/fire engineer approves demand, drainage/venting, fixture-unit method, hydraulic losses, pressure/zoning, backflow and protection requirements. Unknown is not numeric zero; N/A requires an applicability reason. Fire hazard classification, design density/area, hydraulic assumptions, pumps/tanks, coverage and specialist authority review cannot be replaced by a clash check. Fire systems follow the UAE Fire & Life Safety Code of Practice, September 2018 edition, plus the emirate Civil Defence authority's amendments current at project start, recorded in the BEP and the BBM-STD-51 §3 register; record the Civil Defence approval route and the approved fire contractor/consultant evidence for each fire system (route detail in BBM-STD-85).
For gravity networks identify upstream/downstream nodes, horizontal run, invert datum/units, segment/branch slope and flow direction. Distinguish internal invert from centreline/outer bottom and include pipe wall-thickness mapping where relevant. Model risers, fittings and cleanout/maintenance access; an elevation change can affect an entire connected branch, so recheck all dependent segments and low points after edits. SYN-D60 has a 10 m horizontal run with local inverts 1000 mm upstream/900 mm downstream, giving 100 mm fall and 1% gradient. It is a local arithmetic fixture with no geodetic tie or code-minimum claim. Reversing the endpoints gives an adverse fall relative to declared flow and must fail the fixture. The hydraulic/design source remains distinct from this geometric check.
SYN-F60 is an identity-only positive fixture on SYN-FP60: three occurrences FP-V01 (valve), FP-P01 (pipe) and FP-H01 (head), all Domain=Piping and SystemClassification=FireProtectionWet under the proposed SYN-X60 R01 mapping. Valve outlet V-OUT connects pipe start P-IN; pipe end P-OUT connects head H-IN; the valve inlet is the single declared intentionally open supply boundary. Native connector IDs/enum spelling are qualified in the actual build, while these logical keys remain stable. Receiver fields are Asset_ID, SystemID, ConnectorKey, Domain, SystemClassification and ConnectedTo; membership must be exactly those three occurrences with the stated two connected pairs. Mutating the head SystemID to SYN-DR60 or classification to Sanitary must fail identity comparison; restoring SYN-FP60/FireProtectionWet and both connected pairs is the positive retest expectation. This fixture sets no hydraulic load, pressure, coverage or fire approval. Fire models record approved system/protection scope, heads/devices/zones, hydraulic node identity, supply/valve/test/drain interfaces and corresponding design documents. Test native connector/system identity, schedule consistency, coverage representation and agreed receiving fields. Actual fire performance and compliance require competent independent review and applicable authority acceptance under BBM-STD-12/57; no fictional pressure or acceptance certificate is supplied.
5 Calculations access penetrations and specialist interfaces#
Design leads approve calculation inputs/results; authors record model-to-calculation mapping, source revision/hash and unresolved assumptions. IFC coordination, analytical/hydraulic/electrical exchange and fabrication formats have separate schemas/presets and receiving checks. Unsupported required semantics require an agreed complementary deliverable rather than silently disappearing. The construction/fabrication contractor verifies installation/manufacturing interfaces within its appointment; design authority does not transfer merely because a supplier supplied a model.
Each penetration has OpeningID, host/native ID/revision, service/system/size, insulation/firestop/access allowance, location/frame/unit and proposed/approved dimensions. Structural/architectural host owner approves geometry; competent fire designer approves rated assembly/penetration system; services designer confirms fit. No physical cut occurs on a modeller's assumed allowance. Builder's-work and firestop ownership, manufacturer evidence, installation constraints and issue/receipt dates are explicit. Proposed/unapproved penetrations hold affected host release. Link all approved changes to revised sources, calculations, schedules, drawings, TIDP/MIDP and notified recipient acknowledgments.
For REQ--A only, required task withdrawal space is 600 mm; positive clearance 650 mm with bounded uncertainty 10 mm has lower bound 640 mm and meets that fixture requirement. Clearance 605 mm with uncertainty 10 mm has lower bound 595 mm and fails. These fictional values do not define universal service clearance. Use the actual manufacturer's task, direction, route and uncertainty before project reliance; BBM-STD-50 governs pair/zone test semantics, not stage-based overlap allowances.
6 Discipline checks native fixtures and acceptance#
The workbook LOIN rows specify per-discipline geometry, data and documentation tied to synthetic BoD/EIR IDs. Checks separates competent design review from automatic completeness/connectivity checks. Tests gives isolated HVAC flow/unit/connectivity, electrical circuit/panel, plumbing slope/system, fire identity and service-access/penetration cases. Record each expected result, actual measurements, source/output hashes, full builds/profile, operator/date, failed evidence, correction and independent retest evidence. Reset each mutation from the positive baseline. A corrected unit label without a converted measured value is not a fix.
Review all scoped mandatory data/identities, native systems/connectors and itemised schedules, source calculation/design evidence, geometry/clearances/approved openings, issued sheets and recipient results. Full-sheet and critical-detail review follows BBM-STD-67; scripts cannot judge complete engineering content. Mandatory failure or missing competent approval holds affected scope regardless of overall completion percentage. Producer check, independent mechanical/electrical/public-health/fire review, coordination check, authorisation and receiver acceptance remain separate; record actual delegated functions and permitted use. Preserve and test reopening the compatible source baseline on rollback. Native models, system solving, engineering adequacy, fabrication/commissioning, authority acceptance and office adoption are Not executed here.
References#
- Office Manual V0.5, BEP V0.5, Glossary V0.3, BBM-STD-51/54/55/57/63/65/67/72, BoD BBM-STD-12 and MIDP/TIDP V0.3 are controlled prerequisite owners. Synthetic IDs below create no office adoption, appointment or native acceptance.
- ISO 19650-1:2018, clauses 5/11; ISO 19650-2:2018, clauses 5.1.4/5.6.3/5.6.4/5.7, are reading pointers for requirements, container checks, content review and exchange. ISO 19650-3:2020 addresses operational update context; ISO 19650-5:2020 security-minded lifecycle context. Public catalogues/guidance support scope and pointers, not a licensed clause conformity audit; no paid paragraphs copied.
- IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance Part 2, archived edition 5, explanatory only and IMI Framework Guidance Part D, archived edition 2, explanatory only inform purpose, responsibilities and review. ISO 7817-1:2024 is the current researched LOIN concepts reference; BS EN 17412-1:2020 BSI record is predecessor context. Preserve an adopted appointment edition until controlled change.
- BCA Singapore BIM Guide v2 (August 2013), historic benchmark, section 4 and appendices A/C, is a discipline/coordination benchmark. Its foreign statutory rules are not UAE mandates.
- DM circular index, ADM Code of Practice October 2020 sections 3.2/3.3, and DDA Final Design Approval, checked 2026-10-16, are separate jurisdiction interfaces. BBM-STD-57 must establish actual plot/authority/edition/profile before use; the ADM BIM Code of Practice is recorded once, with its verified scope and issue, in the BBM-STD-51 §3 edition register and applied only as BBM-STD-57 and BBM-STD-85 assign it; Dubai permit BIM (DM circulars 9-1-2 and 9-1-3) is profiled in BBM-STD-85. No UAE-wide threshold, calculation criterion or legal advice is supplied.
- Autodesk MEP connection selection Revit 2026, panel schedules Revit 2026, sloped pipe controls Revit 2024, checked 2026-10-16. Versioned authoring concepts only; adopted-build native and receiving qualification remains required.
- Current sources, checked 2026-11-04: IMI Framework resources (formerly UK BIM Framework, renamed May 2025); UAE Fire & Life Safety Code of Practice, September 2018; Al Sa'fat, Estidama Pearl minimums (DMT news, 8 Jan 2025). UAE requirement detail: BBM-STD-85.