BBM-STD-55-RESPONSIBILITIES-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft for office review and adoption
1 Purpose and appointment control#
Allocate information-management activities and information production separately, with one accountable function for each discrete activity and an identifiable producer, independent checker, coordinator, authoriser and accepting recipient for each delivery. This pack covers and. The practice director owns office organisation; the appointed Information Manager maintains project allocations. No chart or RACI letter grants contractual or statutory authority.
Use BBM-STD-51 for controlled identity and dependencies, the Directory for restricted actual holders, BEP 6.2 for the existing allocation baseline, and the editable matrices. The workbook contains blank chart, role-assignment, activity and production tables plus a coherent fictional SYN-P001 example. The project copy becomes the single allocation record; other documents reference its ID/revision.
| Control | Complete before mobilisation |
|---|---|
| Baseline | ProjectID, appointment/protocol IDs, matrix ID/revision, scope and effective dates |
| Authority | Delegating party, permitted decisions, limits, expiry, substitute/deputy conditions and signed evidence |
| Assurance | Competence evidence, independent-check arrangement and available staff hours for each commitment |
| Change | Same ChangeID in allocation, BEP, TIDP and MIDP; impact, approval and notified recipients |
2 Office chart and project appointments#
The functional chart describes reporting and escalation, not actual employment or a contractual chain. Keep named staff, contact details and personnel evidence in the private Directory, and publish only authorised role labels. The chart template records FunctionID, parent function, scope, deputy function, escalation route and restricted holder reference. Actual appointments can differ from office reporting.
| Office function | Reporting and scope | Deputy or escalation |
|---|---|---|
| Practice director (office director) | Office adoption, service scope and resource decisions | Recorded director delegate; commercial/legal matters to authorised owner |
| BIM Manager | Office standards and information-management competence | Named competent deputy in Directory; unresolved policy to director |
| Discipline lead | Discipline design scope, competent authors/checkers and technical interfaces | Scoped discipline deputy; unresolved design interface to Lead Design Consultant |
| QA/QC lead | Independent review method, nonconformance and corrective-action evidence | Competent independent deputy; unresolved release failure to authoriser |
| CDE/IT and Security leads | Access/configuration and sensitivity controls within separate delegated scopes; the Security Lead runs the security triage, security management plan and breach procedure in BBM-STD-87 | Qualified deputies; incidents to the nominated security decision owner |
| Design Safety Lead | Health and safety information requirements, structured risk records and their review triggers per BBM-STD-88 | Competent safety deputy; unresolved residual risk to the accountable design lead and appointing party |
| Asset-information lead (Asset Information Owner) | Operational requirement and receiving-system interface where appointed | Operator's nominated deputy; unresolved AIR to asset owner |
| Consultant of record (authority-registered) | Engineering consultancy registered with the permit authority for the emirate and discipline; signs authority submissions within its registration | Registered deputy engineer; registration number, emirate, discipline scope and expiry held in the Directory; the registration rule is the authority's current rule recorded in BBM-STD-85 and BBM-STD-57 §3 |
| Authority portal submitter | Uploads authority submissions (e.g. the Dubai BIM permit model) on the portal; uploads only containers authorised for submission | Named deputy with own portal account; account holder, eligibility evidence, emirate and expiry in the Directory; no shared credentials |
For each project, identify the appointing party (AP), lead appointed party (LAP), appointed parties/task teams and actual contractual relationships. The same organisation can be AP for a downstream appointment while remaining appointed upstream. A job title such as BIM Manager or coordinator is not automatically the AP, LAP, designer or acceptance delegate.
Map ISO information-management functions to actual appointment roles. ISO 19650-2:2018 clause 5.1.1 is the appointing-party function-allocation reading pointer; clause 5.4.2 concerns detailed delivery responsibility. Guidance A explains that the function can be distributed. Check licensed clauses before a compliance assertion. Combined roles require a recorded conflict assessment, capacity check and an independent review route. Author and checker must be different competent people for the same scope; a small team does not waive the check.
3 Activity RACI#
R performs the activity, A is the single accountable function, C is consulted and I is informed. A/R is one function holding both duties. Split distinct decisions instead of assigning several A entries. Every active row has one A and at least one R. Blank, orphan or duplicate-accountability rows hold their affected commitment.
The activity table below retains BEP 6.2.1 meanings and is completed by appointment scope. Appointment of the LAP by the AP and appointment of downstream teams by the LAP are separate activities; the legacy generic appointment row cannot make the LAP accountable for another party's appointment.
| Activity | Accountable function | Performer and consultation |
|---|---|---|
| Establish project information requirements | AP | LAP/assigned IM prepares; decision consumers consulted |
| Maintain the integrated Basis of Design | Lead Design Consultant | Competent discipline leads own their technical criteria; authority coordinator maintains external submissions; BIM Manager controls the information records; actual holders recorded per project |
| Security triage and security management plan | LAP | Security Lead performs per BBM-STD-87; AP consulted |
| Health and safety information | Design Safety Lead's appointing organisation (LAP) | Design Safety Lead and task teams perform per BBM-STD-88; operator consulted |
| Advise on CDE; set up/maintain CDE | LAP | Assigned IM performs; AP, task leads and recipient consulted |
| Provide the CDE | AP | LAP performs within appointment; IM consulted |
| Appoint the LAP | AP | AP's authorised procurement function; legal owner consulted |
| Appoint a downstream task team | LAP as downstream AP | Authorised appointment manager; task lead and IM consulted |
| Confirm and maintain BEP | LAP (owner) | Delegated information manager maintains; task leads perform their inputs; AP/recipient consulted |
| Submit to an authority portal | Consultant of record | Authority portal submitter performs after LAP submission authorisation; authority liaison consulted |
| Prepare and maintain TIDP | Task-team lead | Assigned producers perform; checker and IM consulted |
| Reconcile MIDP | LAP | IM/delivery planner performs; task-team leads consulted |
| Produce and independently check a container | Task-team lead | Distinct author and checker perform their separate steps |
| Authorise delivery-team submission | LAP | Delegated release function performs after review; recipient informed |
| Accept a received exchange for its intended use | AP or its documented delegate | Authorised recipient assesses; producer/LAP consulted |
The workbook includes a reusable blank role-column RACI and filled example. AP remains A for receiving acceptance unless an actual delegation names the recipient as A and removes the AP A from that row. A is a management allocation within scope, not a transfer of design liability, statutory duty or legal signing powers.
4 Detailed production responsibility#
The production matrix is one row per defined element/use/stage/exchange/delivery occurrence, not one row saying all models. Record RequirementID/revision, object population, discipline/use, milestone/ExchangeID, ContainerID and DeliveryID, producing task team, author, independent checker, coordinator, submission authoriser, accepting recipient and the authority/scope for each decision. Record input dependencies, TIDP/MIDP source rows and capacity commitments.
| Fictional production row | Scope and plan link | People and decision boundaries |
|---|---|---|
| PR-SYN-ME01 | AHU-001, VLV-001/002; mechanical coordination; EX-; DEL-SYN-ME01; TIDP ME-01 | SYN-MA01 author; SYN-MC01 checker; SYN-CO01 coordinator; SYN-LAP01 submission authoriser; SYN-RR01 proposed receiving reviewer; AP retains A |
| PR-SYN-ME02 | Same assets; equipment data use; EX-; DEL-SYN-ME02; TIDP ME-02 | SYN-MA02 author; SYN-MC02 checker; same coordinator/authoriser/recipient with separately recorded data-review scope |
| PR-SYN-ME03 | Same zone/interfaces; access/design note; EX-; DEL-SYN-ME03; TIDP ME-03 | SYN-MA03 competent designer; SYN-MC03 independent design checker; same release/receiving functions, without transferring discipline design responsibility |
These rows follow the existing synthetic TIDP and MIDP trace. EIR--M01/M02/M03 are preserved existing synthetic aliases for the later EIR allocation. No live person, acceptance delegation or delivery commitment is established. Fill actual authority evidence before using these rows.
5 Capacity and conflict resolution#
Before committing a delivery, the task lead records producer/checker competence, planned hours, available hours in the same period/calendar, leave/deputy cover and other commitments. Compare required and available capacity by role-holder and window. A nominated person with no hours is not an available owner. LAP resolves cross-team dependencies and coordinates the MIDP; task leads retain their TIDP preparation commitments.
| Synthetic adverse case | Correction | Required closure evidence |
|---|---|---|
| PR-SYN-ME01 has no checker and two teams both claim the same model scope | Hold that delivery; assign SYN-MC01 as independent checker and resolve one producing team/boundary | Corrected matrix revision, appointment scope, competence/capacity and task-lead acknowledgment |
| Acceptance RACI contains A under both AP and RR | Keep AP A until a valid delegation exists; if delegated, transfer the scoped A and remove duplicate | Delegation ID, recipient scope/date, corrected row and notification |
| Fictional author has 16 available hours but 24 committed hours in one window | Reallocate an authorised competent author or adjust the commitment through the actual programme authority | Updated hours, checker independence, same ChangeID in TIDP/MIDP and notified dependency owners |
The example hours illustrate an arithmetic conflict only, not an office productivity rate. Neither a deadline nor a RACI can bypass competence or mandatory checks. Escalation follows task lead, LAP/Lead Design Consultant, then the AP decision owner as applicable; legal, security and statutory decisions go to their actual competent owners. Record the unresolved question, affected scope, interim restriction, decision owner and actual decision date; no universal response SLA is invented.
6 Acceptance and change#
6.1 Completed synthetic reconciliation#
The workbook Function crosswalk maps every RACI column to an assignment or a production-row selection rule. Its Combined roles record identifies the same fictional holder for LAP and IM, the potential self-authorisation conflict, a separate competent review by SYN-MC03 and a scoped AP oversight decision. This is an example review record, not actual delegation or competence evidence.
Capacity allocations records author, checker, coordinator, authoriser and recipient hours by holder in W-, 4 November to 1 December 2026. Capacity totals reconciles every holder's required hours against available hours for that same window. Values are a manually reviewed snapshot; any input change requires recomputation from allocation rows before the commitment is accepted. They are not live staffing figures or an automatic Excel enforcement gate.
The Adverse production, Adverse RACI and Adverse capacity sheets contain the actual defective synthetic rows. CH- selects a specific correction: move an eight-hour non-delivery duty from SYN-MA01 to SYN-MA02. The first holder then needs 16 of 16 available hours; the second needs 24 of 32. Shared coordinator hours total six, receiving-review hours six, and the holder combining LAP/IM totals seven. The completed Change example records fictional decision, R01-to-R02 baseline changes, affected BEP/TIDP/MIDP references and recipient acknowledgments. Production example retains the stable delivery IDs and cites that fictional corrected MIDP R02. No source office TIDP/MIDP file is rewritten.
6.2 Release checks#
Check every active activity for one A and one or more R functions; every production row for one producing scope, a distinct competent checker, authoriser/recipient scope and valid plan links; every role for appointment, holder/deputy, competence and capacity. The reviewer must identify all planted orphans/duplicates in the workbook Conflict cases before approving the corrected example. No generic percentage can average away an absent mandatory owner.
At change, preserve the old allocation, assess duties/capacity/security/design impacts, obtain the actual authority's decision and update the matrix, role Directory reference, BEP, TIDP and MIDP by the same ChangeID before the affected new commitment takes effect. Record notices and acknowledgment. Mobilisation and receiver tests remain NOT EXECUTED in this office template.
References#
- R1. ISO, ISO 19650-1:2018 and ISO 19650-2:2018. Reading pointers: -2 clauses 5.1.1 and 5.4.2; public catalogues do not prove detailed clause compliance. Checked 2026-11-04.
- R2. IMI Framework (formerly UK BIM Framework, renamed May 2025), archived Guidance A edition 2 February 2021, function and resource allocation; archived Guidance E edition 2 February 2021, appointment context; resources. Checked 2026-11-04.
- R3. Writing plan, gap matrix, Glossary, office decisions and the current local drafts linked above. All examples are synthetic; actual holder records stay private.
- R4. Dubai Municipality circular 9-1-3 (BIM submitted with the permit through the authority portal). Checked 2026-11-04. Authority registration rules are held in BBM-STD-85.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-10-16 | First controlled draft |
| V0.2 | 2026-11-04 | closure: BEP V0.5 §6.2 link; authority-facing functions (consultant of record, authority portal submitter) via BBM-STD-85; BEP ownership per; cross-links and references re-checked + cross-doc pointer pass |