BBM-STD-56-INFORMATION_PROTOCOL-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft for office review and adoption
1 Scope incorporation and authority#
This standard specifies the office information-protocol preparation and review records for. It is an appointment-annex checklist and particulars template, not operative legal terms or legal advice. The commercial/contract owner and appointed legal adviser settle actual drafting, governing law, procurement interfaces, hierarchy and execution. Technical staff define information scope within delegated duties; they do not grant legal rights, vary liability or execute an appointment through a BEP/CDE entry.
Use register and entitlements, responsibilities, EIR and LOIN, BEP V0.5 sections 1.7–1.10, AIR and PIR. The editable protocol review pack contains blank/populated particulars, incorporation/departure schedules, rights/reliance records, clause checklist, specialist reviews and transition records. The generic TBP H04 terms template is prior-art product/adoption content, not an executed office contract.
The signed governing agreement and valid amendments determine actual precedence, subject to applicable mandatory law/authority requirements. Record exact incorporated versions and precedence provisions; do not assume a universal relative order among appointment, protocol, EIR, BEP and standards. The BEP implements agreed information duties and cannot unilaterally change them. Refer unresolved conflicts to the contract owner and appropriate specialist; hold affected use pending the actual authorised resolution.
| Particulars group | Required completion |
|---|---|
| Appointment | Appointment/project/asset ID, delivery or operational phase, actual legal parties, authorised signatories and delegated functions |
| Governing instruments | Agreement/amendment IDs and exact incorporation/precedence provisions; law/forum/procurement selected by responsible owners |
| Information schedules | Exact EIR/LOIN, standards/methods, confirmed BEP, responsibilities, TIDP/MIDP, security and rights/reliance versions |
| Proof and control | Owner/status, specialist review/conditions, execution/effective date, distribution and recipient acknowledgments |
SYN-APP01 / SYN-P001 is the fictional mechanical replacement-design appointment in BBM-STD-54. SYN-PROT01 R01 labels its example particulars only. Actual legal parties, law/forum, execution and insurance evidence are Not provided; appointment activation is Hold. CH-SYN-BASE01 labels the initial fictional R01 fixture, not an authorised change or office adoption. No record deems acceptance by conduct or grants a right.
2 Reliance versions rights and contributors#
Record permitted purpose, relying recipient, exact model portion/container/version/hash, source/verification limits and actual authorisation/acceptance. Native editability, transfer, suitability or CDE state alone does not grant reliance. A coordination model does not automatically authorise fabrication, construction or operation. Identify interim exchanges separately from designated milestones, including how authors state the permitted scope and limitations for that version.
| Rights question | Particulars for owner/specialist resolution |
|---|---|
| Origin and authority | Project-created, background and third-party content; creator/owner and contributor authority to grant requested rights |
| Licence | Uses/recipients, copying/editing/derivatives, duration, transfer/sublicensing/revocation and lifecycle transition in actual agreed terms |
| Version and limits | Portions/container IDs, source/export revisions/hashes, accuracy/verification limits, actual approval and recipient evidence |
| Contributor duties | Identify content/permissions/restrictions, produce agreed information and notify defects/rights limitations through appointed routes |
| Downstream/reuse | Check recipient and sharing authority; unrelated project, public or AI reuse needs its own permitted basis |
Retain the BEP office decision: non-exclusive project-purpose licence is a negotiation baseline, with background IP retained and project/background/third-party rights scheduled. That baseline itself grants nothing. Contract/rights owners and the legal adviser settle actual particulars. BBM-STD-51 registers entitlements without keys or paid-standard redistribution.
REL- covers the fictional EX- mechanical model/schedule/note R01 for the designated reviewer and next-design-step purpose, excluding fabrication/operation/public reuse. Its state is Hold because actual hashes, licence and delegation are absent. REL- identifies an interim reference view whose exact portions and authorisation remain to be settled. Neither row is a licence grant or actual permitted reliance.
3 Duties exchange acceptance security and sharing#
The appointing function defines requirements/recipients/acceptance authority; the lead appointed party coordinates methods and delivery plans; task teams produce/check assigned products; the receiving reviewer evaluates exact submitted versions. Record delegated scope, deputies, competence and combined-role conflict checks under BBM-STD-55. Design responsibility stays with the appointed competent designer.
For SYN-APP01, SYN-MA01/02/03 produce ME-01/02/03, SYN-MC01/02/03 independently check, SYN-LAP01 authorises scoped submission, SYN-RR01 reviews/recommends and SYN-AP01 records information acceptance separately from DEC-. Preserve EIR-011-G/A/D, LOIN-SYN-ME01/02/03, EX- and DEL-SYN-ME01/02/03. Role IDs are fictional, not actual appointments.
| Control | Required evidence |
|---|---|
| Prepared/checked | Current requirement/source baselines; every applicable mandatory geometry/data/document check and issue disposition |
| Authorised/submitted | Exact manifest/revisions/hashes, permitted use, delegated authoriser, agreed CDE route and submission receipt |
| Reviewed/accepted | Recipient profile/build/test evidence; scoped recommendation/decision, conditions and correction route; upload is not acceptance |
| Protected/shared | Sensitivity/aggregation assessment and security triage per BBM-STD-87, permitted roles/downstream route, third-party rights, allowed/denied access tests and incident escalation |
| H&S information duties | Health and safety information production and exchange per ISO 19650-6:2025 (ED-ISO19650-6): hazard records, exchange points and owner, per BBM-STD-88 |
| CDE provider information security | Evidence that the CDE and hosting providers hold ISO/IEC 27001:2022 + Amd 1:2024 certification or equal (ED-ISO27001): certificate number, scope covering the service used, issuing body and expiry; reviewed at appointment and renewal |
Apply ISO 19650-5 proportionately through actual security assessment, appointment duties and CDE controls. Restrict sensitive asset/safety/security information and test recipient permissions. No credentials or personal signatory data belong in these role-label forms; actual private records remain with their owner. Record permitted locations/sharing, access withdrawal, incident duties, retention classes/legal holds and approved disposal. Select actual notification/retention requirements rather than inventing universal periods. Each downstream appointment needs its own scoped incorporation and rights check; sharing a file does not incorporate upstream terms automatically.
4 Responsibility limitations change suspension and transition#
The checklist identifies matters for competent contract/legal/insurance review. It selects no liability cap, warranty, indemnity, insurance limit or enforceability conclusion. Information management/coordination does not transfer another party's design duty. Receiving acceptance does not certify physical truth, waive statutory duties or settle liability by a spreadsheet status. Appropriate specialists determine actual consequences under incorporated terms and applicable law.
| Interface | Questions and evidence to settle |
|---|---|
| Responsibility/limitations | Design scope, permitted reliance, source accuracy/verification limits, exclusions and any fitness-for-purpose wording; specialist review |
| Liability/insurance | Actual duties, relevant covers/exclusions and professional scope; private evidence reviewed by contract/insurance owner |
| Change | Affected rights/requirements/source/versions/dates; authorised amendment route; one ChangeID across protocol/EIR/BEP/TIDP/MIDP and actual acknowledgments |
| Suspension/restart | Who instructs, affected scope/effective point, preserved baselines/evidence, continuing safety/records/access duties and restart authority |
| Exit/handover | Agreed deliverables/formats/rights, custodians, outstanding issues, receiving tests/receipt, retention/holds and authorised access withdrawal |
Operational handover needs AIR ownership, installed/provenance evidence, actual FM receiving tests and ongoing AIM custody under BBM-STD-52, BBM-STD-75 and BBM-STD-76 (draft dependencies, pinned at their current draft revision until adoption). Service ending alone does not erase records, terminate every licence or prove handover acceptance. Record continuing rights/duties from the actual appointment.
DEV- requests unrestricted public reuse; the fictional review rejects automatic scope expansion and refers any actual revised licence to rights/legal owners. DEV- flags unknown insurance compatibility and stays Open/Hold. No departure takes effect or changes a signed document. EXIT- and SUSP- specify transition/suspension questions; actual instructions, receipts, access changes and retention decisions are Not executed.
5 UK and AIA comparison and adaptation#
Use these primary approaches to frame review questions, then adapt through actual law/procurement/appointment owners. Neither becomes UAE or office law by citation. Edition facts for the IMI Framework (formerly UK BIM Framework, renamed May 2025) protocol are held once in BBM-STD-51 §3 entry ED-INFO-PROTOCOL: the Information Protocol template for BS EN ISO 19650-2 Ed 6 is adopted for new appointments, with protocol guidance ed.3 as explanatory guidance. Its delivery/operational templates and English-law context require appropriate appointment-specific review. The CIC BIM Protocol 2nd ed. 2018 (ED-CIC-PROTOCOL) is legacy: do not use it for new appointments. ISO 19650-2 clause 5.1.8 and ISO 19650-3 clause 5.1.13 are protocol reading pointers through public guidance, subject to licensed adopted-text review.
| Reference | Relationship and review consequence |
|---|---|
| IMI Framework Information Protocol template Ed 6 and guidance (ED-INFO-PROTOCOL) | Complete phase-appropriate project/asset and appointment particulars and incorporate the protocol into each relevant appointment; resolve hierarchy and downstream scope |
| AIA 2022 exhibits and | AIA describes -2022 as a project BEP used with E201/E202/E401/E402. The BEP is not itself intended as a contract exhibit; the selected exhibit establishes adherence obligations |
| AIA milestone/interim distinction | article 8 instructions distinguish designated milestone reliance from interim versions requiring specific authorisation; identify the actual selected exhibit/version arrangements |
| Adaptation | Record governing law/forum, procurement route, contract form/exhibit, design/insurance/security/rights interfaces, precedence and specialist decisions; do not splice US/UK clauses into unreviewed local terms |
AIA LOD/model-element arrangements do not automatically replace purpose-led LOIN. Reconcile purposes, objects, versions and recipient acceptance before any technical mapping. No AIA or paid-standard contractual clauses are copied into this office draft.
5.1 UAE legal interfaces (for the legal adviser)#
The checklist records these interfaces for the appointed legal adviser; it gives no legal conclusion. Instrument editions are held in BBM-STD-51 §3; the legal basis, retention schedule and personal-data rules are owned by BBM-STD-90 §2–§4.
| Interface | Instrument and review question |
|---|---|
| Decennial liability | Federal Decree-Law No. 25 of 2025 (Civil Transactions Law, effective 1 Jun 2026; ED-UAE-CTL): Art. 821 joint 10-year liability of engineer and contractor from delivery; Art. 823 voids exemption or limitation clauses; Art. 824 three-year claim period. Contracts signed before 1 Jun 2026: Federal Law 5/1985 Art. 880. Check that protocol limitations do not purport to limit this liability; records retention follows BBM-STD-90 |
| Copyright and model IP | The UAE copyright legislation in force, as listed on uaelegislation.gov.ae at appointment, identified by the legal adviser; check the licence particulars in section 2 against it |
| Personal data | Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (ED-UAE-PDPL) and any executive regulations listed on uaelegislation.gov.ae at project start: directory, role and signatory data; hosting and transfer (BBM-STD-90) |
| Governing law and forum | Onshore UAE courts or a financial free-zone jurisdiction (DIFC, ADGM) as the appointment selects; the adviser confirms which law governs the protocol |
| Language precedence | Which language version prevails where an Arabic text is required or provided; recorded in the precedence provisions |
6 Review forms and release conditions#
Complete the clause checklist against actual provisions and evidence. Incorporation records separate office-template revision from project-instance revision and name exact locators, incorporation/precedence decisions, owner and execution evidence. Departure records state request, affected scope, impact/alternative, specialist review, decision and effective baseline. Pending/rejected departures cannot silently enter the BEP.
Specialist records identify reviewer function/competence, materials/revisions, jurisdiction/procurement assumptions, findings/conditions, recommendation, authorised decision and evidence/date. The populated fictional review records are prepared issues marked Not executed, not invented professional opinions/signatures. Actual legal identities, advice, insurance evidence and execution remain in the restricted appointment record.
Actual activation requires reconciled particulars/incorporation, specialist decisions, authorised execution/effective date, confirmed roles/rights/security, resolved departures and acknowledged distribution. Positive/adverse test specifications cover completeness, missing incorporation, wrong versions, unsupported reuse, security and exit. Expected results prove no contract or native acceptance. This editorial WIP template remains Hold for appointment activation.
References#
- R1. IMI Framework (formerly UK BIM Framework, renamed May 2025), resources: Information Protocol template for BS EN ISO 19650-2 Ed 6, and Information protocols guidance edition 3, sections 2–5 and 7–8. Edition entry: BBM-STD-51 ED-INFO-PROTOCOL. Checked 2026-11-04; paraphrased review method, no legal clauses reproduced.
- R2. AIA Contract Documents, -2022 official instructions, synopsis/articles 2 and 8; official summary. Checked 16 October 2026; comparison only.
- R3. ISO 19650-2:2018, 19650-3:2020, 19650-5:2020; IMI Framework (formerly UK BIM Framework) archived Guidance E ed.2 February 2021. Protocol pointers -2 5.1.8 / -3 5.1.13 checked through public guidance; catalogue evidence is not licensed clause audit.
- R4. Writing plan, gap matrix, H04 and current office drafts linked above. BEP V0.5 negotiation baseline and actual-contract boundary retained.
- R5. CIC, CIC BIM Protocol 2nd edition (2018, legacy). Checked 2026-11-04.
- R6. UAE legislation portal: Federal Decree-Law 25/2025 Civil Transactions Law and Federal Decree-Law 45/2021 Personal Data Protection. ISO 19650-6:2025; ISO/IEC 27001:2022. Checked 2026-11-04.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-10-16 | First controlled draft |
| V0.2 | 2026-11-04 | closure: IMI Framework protocol template Ed 6, CIC BIM Protocol legacy; §5.1 UAE legal interfaces; one edition entry via BBM-STD-51 ED-INFO-PROTOCOL; H&S duties and CDE provider ISO/IEC 27001 evidence; BEP V0.5 link; BBM-STD-75/76 linked; references re-checked + cross-doc pointer pass |