ArchHubBABOOMDownload

Office Directory

BBM-STD-03 · V0.3 · This is the office's private operational directory.

Download WordAll standards

BBM-STD-03-DIRECTORY-V0.3 · Office standard · Revision date 4 November 2026 · Draft for office adoption · Private restricted master

Summary and document control#

FieldValue
PurposeIdentify the verified people, organisations, appointments, teams and roles needed for information exchange, access administration and escalation
ScopeOffice standards and training ownership; appointment-specific contacts, project register and CDE access responsibilities; no passwords, tokens or private identity documents
RevisionV0.3; replaces V0.2 after approval; V0.1 source records remain immutable migration evidence in the restricted master
Source ownerAhmed Fargaly, as stated in V0.1; present authority and availability not independently verified
Recommended accountable owner(Directory owner; full text in section 7)
Approval / access owner(office approval; full text in section 7)
Master location(controlled master location; full text in section 7)
Distribution(audience-specific views; full text in section 7)
Review(membership review cadence; full text in section 7)
Effective date / approvalNot yet set; record approver, authority, date, revision and next review before activation
RevisionDateChangeEvidence status
V0.121 October 2025, as suppliedPeople/projects index with direct personal contacts and historical targetsHistoric export; current membership/access unverified
V0.214 October 2026Linked register schema; private views; exchange/deputy/escalation routing; joiner/leaver procedure; source validation registerEditorial revision complete; live verification and office adoption pending
V0.32026-11-04Closes rows: UAE PDPL personal-data rules (1), source roster and project rows moved to the restricted master (4, 5), ISO/IEC 27001:2022 access controls and MFA (3), IMI Framework naming, links to BBM-STD-55/82, decision links to BBM-STD-11 V0.2, each decision stated once (7), references completed + cross-doc pointer pass (BBM-STD-90 §4, BBM-STD-87 §6, authority registration fields per BBM-STD-55/85)Prepared in standards-closure batch B3; live verification and office adoption pending

This is the office's private operational directory. It is not the generic TBP directory, an authority to grant access, or evidence that every stakeholder can access the CDE. Never copy its populated people/project records into TBP or a public template. A role-only blank form may be reused only through the approved generic-content process.

The standards basis is ISO 19650-1:2018 for parties/teams, ISO 19650-2:2018 for delivery appointments, ISO 19650-5:2020 for proportionate sensitivity/access controls and ISO 29481-2:2025 for exchange-interaction context. IMI Framework (formerly UK BIM Framework, renamed May 2025) Guidance A edition 2 (2021) and Guidance C edition 1 (2020), both archived editions, support resource allocation and CDE workflow. ISO/IEC 27001:2022 (+ Amd 1:2024) Annex A supplies the identity and access controls in section 3, and the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) governs the personal data in this register (section 1). Penn State BIM Project Execution Planning Guide v2.2 (2019) supplies infrastructure planning context. NPSA security-minded guidance supports distribution and lifecycle review. These sources do not prescribe the proposed office IDs, deadlines or job-title powers below; no detailed ISO clause compliance is claimed.

Objectives#

(Directory objectives; full text in section 7)

Historical 2025 dates do not prove completed targets.

ObjectiveMeasurable acceptanceOwner / when
DIR-OBJ-01: verified routing100% active exchanges have a verified primary, deputy and authorised escalation contactDirectory owner; before the exchange baseline is released
DIR-OBJ-02: least necessary access100% active memberships link to an approved permission set, sponsor and successful access testAccess approver and CDE administrator; before activation and after scope change
DIR-OBJ-03: current lifecycleZero known leavers retain approved active memberships after the agreed termination time; every active record has a review dateDirectory owner with HR/appointment sponsor and IT; at termination and monthly review
DIR-OBJ-04: evidenced readiness100% assigned critical tasks link to capability/capacity evidence or an explicit mobilisation holdTask-team manager / competence owner; before task allocation

1 Private custody and audience-specific views#

Perform a sensitivity assessment before collecting or aggregating records. The office directory can reveal relationships, project participation, access privileges and operational coverage even when individual names are ordinary business contacts. Limit fields and audiences accordingly, using ISO 19650-5:2020 and NPSA guidance as the basis; the security triage is in BBM-STD-87.

A register of people and contacts is personal data and follows the PDPL rules in BBM-STD-90 §4. It is processed under the UAE Personal Data Protection Law, Federal Decree-Law No. 45 of 2021 (effective 2 January 2022), and any Executive Regulations listed on uaelegislation.gov.ae at project start, and under the DIFC or ADGM data protection regime where a party is established there. For each record class, record the lawful basis, purpose, retention class and the data-subject request route. Exporting a Directory view outside the UAE needs a recorded cross-border transfer basis before release. Retention classes and the legal-owner schedule are owned by BBM-STD-90.

(audience-specific views; full text in section 7)

These are local view names, not ISO security classifications.

ViewIncluded informationAudience / controls
Restricted identity masterPerson ID, minimum business identity/channel, verified role links, lifecycle status and validation evidenceDirectory owner, authorised HR/IT/security administrators and scoped appointment sponsors; audit read/export access
Appointment contact viewOnly verified business contact, organisation, appointment/team role, deputy, exchange/escalation route and review date for that appointmentAuthorised appointment participants; no unrelated projects, personal phones or full privilege inventory
Role-only office viewRole, function, approved role channel or controlled link, standards/training ownership and escalation functionApproved office users; no named candidate roster, private channels or sensitive appointment associations

Use a business role mailbox or the minimum verified business channel where practical. Do not include personal mobile numbers, home details, identity documents, credentials, medical information or individual performance/assessment details. Exceptional contact needs require necessity, approved purpose/audience and retention review; do not expand the master by convenience. Do not send the directory to public search or people-finder services to validate contacts.

(export expiry; full text in section 7)

(retention by record class; full text in section 7)

2 Linked register and field specification#

(linked register keys; full text in section 7)

(source-row quarantine; full text in section 7)

Register / primary keyRequired fieldsValidation / relationship
Organisation / OrgIDLegal/business display name, verified organisation code, organisation sponsor, approved domain/channel and verification dateUnique code; no inferred legal identity from an email domain
Appointment / AppointmentIDControlled appointment/protocol reference, appointing party, lead appointed party, appointed parties, scope, start/end, delegated authority referenceLinks to verified OrgIDs; actual appointment defines authority, reliance and precedence
Team / TeamIDAppointmentID, delivery/task-team designation, discipline/function, accountable manager and deputyDelivery team and task team are distinct; membership must be in scope
Person / PersonIDBusiness display name, OrgID, minimum verified business channel, identity verification source/date, lifecycle statusName/email alone does not prove identity; no secrets; protect contact fields
Membership / MembershipIDPersonID, AppointmentID or office-only scope, TeamID, role/function, sponsor, delegate/deputy MembershipID, validity dates, approval and last/next reviewOne person may hold several roles; verify capacity and conflicts; deputy cannot inherit unapproved powers
Authority registration / MembershipIDFor the authority-facing functions in BBM-STD-55 (consultant of record, authority portal submitter): authority and emirate, registration or account reference, discipline scope, validity dates, verified-by/date and deputy registrationReference only, never credentials; registration and eligibility rules are owned by BBM-STD-85; expired or unverified registration holds the submission function
Exchange route / ExchangeIDRequirement/exchange ID, producing team, recipient, primary/deputy memberships, check/authorise/accept functions, channel, escalation and timingAll active role links verified; appointment authorisation and receiving acceptance separately assigned
Access / AccessIDMembershipID, CDE/platform/environment, permission-set ID, allowed/denied actions, scope, approver, administrator, expiry, grant/revoke/test evidenceRegister records approval/evidence; platform enforces permissions. No passwords or access tokens
Review / ChangeIDRecord IDs, reason, requester, evidence, approver, before/after scope, effective time, test and notification linksPreserve audit history; do not overwrite issued exchange identities

(dates and time zones; full text in section 7)

Use verified organisation-local hours/time zone. Active required fields cannot be TBD; not-applicable needs a reason and owner.

Membership template#

MembershipIDPersonID / OrgIDAppointmentID / TeamIDRole ID (BBM-STD-55) / delegated authority referenceSponsor / deputyBusiness channel referenceValid from / toStatus / last verified / next review
[complete][verified identity][scope or office-only][Role ID from BBM-STD-55; controlled authority reference][verified membership links][restricted master or approved role channel][dates][evidence link and dates]

Information-exchange contact and escalation template#

ExchangeID / requirement / due dateProducer / checkerDelivery authoriserReceiving acceptorPrimary / deputyAuthorised CDE channelEscalation / response window / evidence
[complete][scoped memberships][appointment authority][receiving-party authority][verified links][actual workflow/container IDs][role, trigger, working calendar, record]

Producer check, delivery-team authorisation and appointing/receiving-party acceptance are separate functions. Do not infer any of them from job title or RACI alone. An appointed deputy needs matching delegated scope and tested access. The directory records the routing; the appointment and approval records grant authority.

Access and authorised-channel template#

AccessID / membershipPlatform / environment / scopePermission set: allowed / denied actionsApprover / administratorGrant / expiry / revoke timeAllowed + denied test / evidenceChannel and formal-record rule
[complete][exact tenant/project/container; no secret URLs][e.g. own-team WIP edit / other-team edit denied][actual roles][timestamps + offset][test user, actions, expected/actual result][formal exchange, issues and urgent-notification routes]

(formal and urgent channels; full text in section 7)

Record exact tools, tenant/project scope and workflow before readiness. Email/chat alone is not formal acceptance unless explicitly defined by appointment. Editable files, sync and Revit Publish groups do not confer release authority.

3 Procedure: join, move, review and leave#

Private identity and scoped appointment records support tested permissions, ongoing review and evidence of removal.

Access controls in this section align to ISO/IEC 27001:2022 Annex A 5.15 (access control), 5.16 (identity management), 5.17 (authentication information), 5.18 (access rights) and 8.2 (privileged access rights). CDE and issue-platform accounts use multi-factor authentication. Administrator and other privileged memberships are reviewed monthly, with the reconciled membership list kept as evidence. The full ISO/IEC 27001:2022 Annex A map and security review triggers are owned by BBM-STD-87 §6.

3.1 Joiner#

  1. Sponsor requests the minimum identity/membership record, appointment scope, role, primary/deputy route, start/end and required information access. The directory owner checks duplicate person records and sensitivity.
  2. Verify identity and business channel with the relevant organisation sponsor or existing trusted appointment contact. Record method, verifier/date and evidence without collecting unnecessary identity documents. Never send messages merely to “test” a source-export address without a real authorised onboarding purpose.
  3. Confirm appointment authority, role delegation, capability/capacity and awareness briefing. Record who can check, authorise and accept; a blank delegation is a hold for that function.
  4. Information/security approver approves scope and permission set. The administrator grants only those permissions; owner and administrator functions may be combined only where the office approves the arrangement and retains review evidence.
  5. Test sign-in and representative allowed actions, plus a safely attempted denied action in an appropriate test scope. Verify the deputy independently. Record expected and actual results; a row saying “access granted” is not a test.
  6. Directory owner changes status from pending verification to active only after identity, authority, channel, dates and tests pass. Publish only the scoped approved view and notify the relevant participants through the authorised channel.

3.2 Mover, deputy change and periodic review#

Reassess need and conflicts when organisation, appointment, role, project, absence cover or permissions change. Remove obsolete privileges rather than adding new access indefinitely. Transfer open issues and ownership; verify the replacement primary/deputy, delegation and channel. Re-test affected actions, update dates and replace affected exports. Keep the before/after approval record.

(membership review cadence; full text in section 7)

Include dormant, supplier, role-channel and relevant service accounts; a vacancy/expired review holds mobilisation/routing.

3.3 Leaver and urgent suspension#

(leaver revocation; full text in section 7)

  1. Sponsor/HR or appointment authority provides the effective time and scope. Administrator disables/removes relevant memberships, sessions, project access, shared links and role-channel access as applicable. Directory contains references to actions, never revoked credential bytes.
  2. Transfer open issues, document ownership and required central/cloud authoring responsibilities through the supported tool procedure; do not manipulate an active model simply because the directory changed.
  3. Test that the former account cannot access the affected scope. Reconcile access logs/membership lists and invalidate old directory views. Preserve required evidence and apply retention/removal rules.
  4. Owner marks membership inactive, records revocation/test evidence and confirms current primary/deputy coverage. Closure requires readback from the actual platform, not just a completed ticket.

3.4 Escalation and incidents#

(escalation windows; full text in section 7)

S1/S2/S3 issue response follows Clash matrix section 7; routine contact escalation cannot extend an issue deadline.

Suspected security incidents, imminent safety issues and access needed for urgent duty-holder action use the approved security/safety incident route immediately. Record actual incident roles and verified channels before activation. Do not assume an ISO appointment label makes someone an emergency contact. Preserve evidence, restrict further disclosure, and follow the authorised incident plan; sensitive details do not belong in the wider contact view.

4 Source roster validation and controlled migration#

Contact and project rows supplied by earlier directory exports (V0.1) are candidate records, not active contacts. None carries current appointment, deputy, expiry or access-test evidence. The rows, their function labels and their organisation and stage claims are held only in the restricted Directory master, never in this standard, a template or TBP. Quarantine every source row until a sponsor verifies it against current office and appointment records; this standard keeps only the blank reconciliation worksheet below.

Source validation is structural and syntactic only. Display-name differences can be legitimate and do not prove an error or impersonation; a malformed channel is never guessed or used. Retain raw source bytes; record a verified correction as a new controlled value with provenance.

Reconciliation and activation worksheet#

Candidate / raw source rowCurrent PersonID / OrgIDAppointment / team / role evidenceVerified channel / method / dateDeputy / authority / capacity evidenceAccess grant + test / approverResult / reviewer / next review
[SRC-Pnn][map or reject duplicate/stale][trusted controlled record][restricted evidence][membership and references][AccessID and actual test][active / hold / retired + reason]

Do not assert that “all CDE stakeholders have access”. Validate each actual membership. Do not import the entire old roster merely because names/emails exist. The adoption gate is verified current scope, not transcription accuracy.

5 Projects and appointment readiness#

Source project rows are held in the restricted master under the same quarantine rule. No original date or status is carried as current. Ambiguous legacy labels (for example "IFC" meaning issued for construction or a schema exchange, and "DD") are mapped to the actual stage and exchange definitions before use.

ProjectID / controlled title linkAppointmentID / organisation rolesDelivery team / lead / deputyActual stage + decisionNext ExchangeID / due / recipientCurrent BEP + MIDP baselineReadiness / owner / next review
[private record][appointing, lead appointed, appointed][verified memberships][stage 0–7 if RIBA adopted; decision][definition; no ambiguous IFC][controlled IDs and revisions][pass / hold with evidence]

RIBA Plan of Work 2020 stages are 0 Strategic Definition, 1 Preparation and Briefing, 2 Concept Design, 3 Spatial Coordination, 4 Technical Design, 5 Manufacturing and Construction, 6 Handover and 7 Use. The nine TBP manual phases are learning/process groupings and are not nine RIBA stages. “Developed Design” is legacy stage terminology; map it explicitly. Procurement can overlap stages 4/5; the directory must reference the actual appointment programme, not infer it from a file suffix or LOD.

6 Standards, training and competencies#

(training time and competence; full text in section 7)

Do not activate a critical task role without actual capability/capacity or authorised supervision/remediation.

Controlled itemOwner / deputyRequired referenceSelf-check / review
Office OIR(OIR owner; full text in section 7)Approved BBM-STD-02 revision and office decision registerObjective/decision/exchange trace maintained
Office terminology(glossary owner; full text in section 7)Approved BBM-STD-00 revision; source/edition contextConflicting aliases mapped before issue
Manual / BEP / plans(Manual owner; full text in section 7)
(BEP owner; full text in section 7)
(TIDP/MIDP ownership; full text in section 7)
(office approval; full text in section 7)
Approved edition register; actual appointment BEP/TIDP/MIDPNo assumption that a prepared revision is adopted
Workshop guides(training time and competence; full text in section 7)Approved guide revision, exercise and tool-build evidenceTask-based artifact and result; private assessment details in restricted record
Role definitionsOwner of BBM-STD-55Every membership Role ID resolves to a BBM-STD-55 role definitionNo membership is activated with a role that BBM-STD-55 does not define
Competence assessmentOwner of BBM-STD-82Assessment record per BBM-STD-82 for every critical-task membershipGaps hold the role or set an approved supervised scope
Installed CDE / authoring tools(build and profile freeze; full text in section 7)
(office CDE platform; full text in section 7)
Actual build, licence/support and exchange-test recordInstalled capability separately verified from source guidance
Membership / critical taskRequired competence + capacityEvidence / assessor / dateGap / supervised scope / action dueReview trigger / owner
[complete][actual task; available hours/cover][restricted assessment link][hold or approved limited scope][role/tool/appointment change]

7 Acceptance criteria and decision register#

Record every operational check below and actual publication approver before an active view is released.

  • Every active contact has organisation, appointment or office-only scope, team, role, validity, trusted channel evidence and named sponsor.
  • Every exchange has primary/deputy coverage, separate check/authorise/accept roles, actual channels, escalation and deadline/calendar.
  • Every access record has approval, minimum permissions, grant/expiry and actual allowed/denied tests; denied tests do not expose another team's private information.
  • Sensitivity and distribution are approved; role-only and appointment views exclude irrelevant identities/privileges. No credential bytes or unnecessary personal data appear.
  • Source candidates are explicitly verified, retired or held. Zero unverified candidate rows appear as active memberships. Any source channel found malformed is corrected from trusted evidence before use.
  • Monthly review reconciles actual platform access; leaver closure includes revocation readback and replacement coverage.
  • Current office holder/deputy, master location, effective date, records schedule and incident route are entered; unfilled particulars block affected activation.

Decision register#

Each office decision used by this Directory is stated once here; other sections cite it by ID. The canonical record is BBM-STD-11.

Decision (BIM Manager, 2026-10-14): The task-team lead owns the TIDP commitment; the LAP owns the coordinated MIDP baseline; every approved delivery-row change must propagate by the same ChangeID before the affected new commitment takes effect. Basis: Separate production ownership and coordinated delivery authority with exact source-row lineage and review evidence G-F. Authority: TIDP section 2, ownership and change propagation.

Decision (BIM Manager, 2026-10-14): The BIM Manager is the office information standards owner and glossary custodian, supported by discipline, CDE, security and asset-information contributors; record a distinct deputy and actual holder in the private Directory before activation. Basis: One standards function avoids competing terminology owners; actual staffing and delegation require evidence G-A.

Decision (BIM Manager, 2026-10-14): The BIM Manager owns the Manual and its maintenance; appoint a distinct deputy with capacity and record actual role holders in the private Directory before activation. Basis: Policy maintenance needs accountable ownership and resources G-A.

Decision (BIM Manager, 2026-10-14): The BIM Manager acts as office information management lead and owns the OIR document; each business function owns its applicable requirement and authorised business decision. Basis: Document maintenance and business authority are distinct functions G-A, G-D.

Decision (BIM Manager, 2026-10-14): Assign Ahmed Fargaly, in the office BIM/information management function, as accountable Directory owner; the director records role acceptance, capacity and a distinct deputy before activation. Basis: Retains the existing author-based choice without inventing a deputy or operational appointment evidence G-A.

Decision (BIM Manager, 2026-10-14): The office director approves office standards and business requirements after relevant QMS, security, safety and business-owner reviews; project departures require the actual appointment authority and recorded scope/date. Basis: Office governance does not transfer contractual or statutory powers G-A, G-E.

Decision (BIM Manager, 2026-10-14): Keep controlled masters in the restricted office standards CDE with document ID, revision, approval and exact URI; distribute read-only approved office views and retain superseded editions without overwriting issued project baselines. Basis: Controlled identity, access and history must survive publication and change G-C, S05.

Decision (BIM Manager, 2026-10-14): Use ISO 8601 dates (YYYY-MM-DD), access timestamps with UTC offset, and explicit units/source for service intervals; validate chronology and receiver mappings with actual calendars/time zones. Basis: Unambiguous dates/units support traceable schedules and exchanges S16, G-F.

Decision (BIM Manager, 2026-10-14): Freeze authoring/exporter/checker/receiver full builds, presets, dictionaries and profile hashes; upgrades require impact, compatibility, receiver and recovery tests with controlled change approval. Basis: Infrastructure qualifies for a purpose through actual capability evidence P02, S04.

Decision (BIM Manager, 2026-10-14): Use records/legal-owner-approved retention by record class and actual legal/contract duties; apply legal holds, preserve approvals/accepted evidence and revoke redundant access; no universal deletion period, and missing schedules hold affected activation. Basis: Security/protocol guidance supports proportionate records control, not invented jurisdiction-wide periods S05, S37.

Decision (BIM Manager, 2026-10-14): Review active Directory memberships monthly and at joiner/mover/leaver, deputy/expiry, incident or appointment change; sponsors verify roles/channels and CDE administrators reconcile actual memberships/exports. Basis: Current routing/access requires evidence beyond stale titles S05, G-A.

Decision (BIM Manager, 2026-10-14): Adopt DIR-OBJ-01–04: 100% active exchanges have primary/deputy/escalation, 100% memberships have approved/tested access, zero known leavers retain access after termination, and critical tasks have capability/capacity evidence or hold. Basis: Routing, access and competence are mobilisation gates, not historical completion claims S05, G-E.

Decision (BIM Manager, 2026-10-14): Use Restricted identity master, Appointment contact view and Role-only office view with section 1 minimum fields/audiences; authorise exports separately and exclude private channels, unrelated memberships and assessment details. Basis: Audience-specific views minimise aggregated relationship/personal exposure S05, P06.

Decision (BIM Manager, 2026-10-14): Expire Directory exports after 30 calendar days or earlier relevant appointment/role/access change; replace affected extracts promptly and use approved retention for removal. Basis: Export freshness and retention are separate controls S05.

Decision (BIM Manager, 2026-10-14): Use stable ORG-nnn, APT-nnn, TEAM-nnn, PER-nnn, MEM-nnn, EX-nnn and ACC-nnn linked keys; preserve system aliases and one person identity across memberships; assign permanent ProjectIDs after sponsor verification. Basis: Linked identities separate organisation, appointment, role and access G-A, G-F.

Decision (BIM Manager, 2026-10-14): Use CDE for formal submission/authorisation/acceptance, approved issue platform for coordination, and verified role channels for urgent notice recorded back in CDE; appointment alternatives require mapping. Basis: Notification/sync/browser Publish do not establish acceptance G-C, S04.

Decision (BIM Manager, 2026-10-14): Revoke at agreed departure/role-end timestamp and immediately on authorised urgent suspension; verify revocation and update Directory/views within one working day; transfer planned custody first, urgent security action takes priority. Basis: Access changes require timely verified completion S05.

Decision (BIM Manager, 2026-10-14): Escalate routine queries primary to deputy after one working day without acknowledgment, then task-team manager/delivery IM after one further day; immediately escalate for deadline/risk and apply stricter appointment windows. Basis: Routing respects actual authority, calendars and deadlines G-A, S04.

Decision (BIM Manager, 2026-10-14): Quarantine 20 contacts as SRC-P01–SRC-P20 and 3 source project rows pending sponsor verification; allocate permanent identity/appointment keys from trusted evidence only and correct SRC-P20 privately without guessing. Basis: Historic labels/status do not prove active identity, access or delegation S05, G-A.

Decision (BIM Manager, 2026-10-14): Reserve 2 hours/week for assigned training where capacity permits and task-team approval is recorded; competence/training owner and technical assessor require inspectable outcomes for critical-role activation or approved supervised remediation. Basis: Competence/capacity differ from attendance P08, G-E.

Decision (BIM Manager, 2026-10-14): LAP owns project BEP, maintained by delegated IM with recorded deputy/project authoriser; review every exchange milestone and material team/tool/requirement change. Basis: Appointment functions determine ownership and authority S02, G-E.

Decision (BIM Manager, 2026-10-14): Select Autodesk Construction Cloud as office default for agreed model/document workflows; qualify actual tenant/modules/permissions/formal transactions; appointment-mandated alternatives/bridges require one authoritative mapping. Basis: Retains office ACC method without assuming configured capability A03, G-C.

Decision (BIM Manager, 2026-10-14): Record defaults as decided office policy on 2026-10-14 with linked IDs; activation still requires actual authorised holders, scoped registers, signed rights, installed builds and passing mobilisation/receiver evidence; preserve NOT EXECUTED/NOT VERIFIED facts. Basis: Founder-authorised choices settle defaults without fabricating contract approval or implementation G-E, S04.

Decision IDRecommended valueRequired approver / evidence
DIR-D01 ownerOffice director; role acceptance and capacity
DIR-D02 keys/schemaInformation lead; actual system mapping
DIR-D03 access/distribution
Security/information owner; actual permission and filtered-export tests
DIR-D04 lifecycle
HR/appointment sponsor, IT and directory owner; workflow and evidence
DIR-D05 escalationAppointment authorities; calendar and verified channels
DIR-D06 rosterOrganisation/project sponsors; completed validation worksheet
DIR-D07 retention/readiness

Records/legal, IT and task-team authorities; retained evidence
Research / gapCoverage
T11.1 organisation/team/role/appointmentSection 2 linked schema, templates and source reconciliation
T11.2 exchange/deputy/escalationSections 2 and 3.4
T11.3 CDE access and authorised channelsSections 2, 3 and actual-permission gate
T11.4 minimisation and sensitivitySections 1 and 4; private source data not redistributed
T11.5 owner/review/joiner/leaverSummary, section 3 and DIR-D01–04
O04 P1/P2/P3Private ownership and lifecycle; corrected schema plus source validation/hold register; role-only view
Drafting crosswalk items C01/C04/C07/C08/C11/C12/C14 (closed; decisions in BBM-STD-11)Actual appointment powers, private custody, managed exchange, corrected stage meanings and evidenced readiness

References#

Research references are scoped guidance, not certification or a claim that current office membership has been verified. Entries checked 2026-11-04 are marked; the others are the researched editions.

  • S01 — ISO, ISO 19650-1:2018 — Concepts and principles, 2018. https://www.iso.org/standard/68078.html
  • S02 — ISO, ISO 19650-2:2018 — Delivery phase of the assets, 2018. https://www.iso.org/fr/standard/68080.html
  • S05 — ISO, ISO 19650-5:2020 — Security-minded approach to information management, 2020. https://committee.iso.org/cms/live/live/en/sites/isoorg/contents/data/standard/07/42/74206.html
  • S19 — ISO, ISO 29481-2:2025 — Information delivery manual: interaction framework, edition 2, 2025. https://www.iso.org/standard/88516.html?browse=tc
  • S21 — RIBA, RIBA Plan of Work 2020, 2020. https://www.riba.org/work/insights-and-resources/riba-plan-of-work/
  • G-A — IMI Framework (formerly UK BIM Framework, renamed May 2025), Guidance A — The information management function and resources, edition 2, February 2021. https://www.ukbimframework.org/wp-content/uploads/2021/02/Guidance-Part-A_The-information-management-function-and-resources_Edition-2.pdf (archived edition)
  • G-C — IMI Framework (formerly UK BIM Framework, renamed May 2025), Guidance C — Facilitating the CDE workflow and technical solutions, edition 1, September 2020. https://ukbimframework.org/wp-content/uploads/2020/09/Guidance-Part-C_Facilitating-the-common-data-environment-workflow-and-technical-solutions_Edition-1.pdf (archived edition)
  • G-D — IMI Framework (formerly UK BIM Framework, renamed May 2025), Guidance D — Developing information requirements, edition 2, February 2021, archived edition. https://www.ukbimframework.org/wp-content/uploads/2021/02/Guidance-Part-D_Developing-information-requirements_Edition-2.pdf
  • G-E — IMI Framework (formerly UK BIM Framework, renamed May 2025), Guidance E — Tendering and appointments, edition 2, February 2021, archived edition. https://www.ukbimframework.org/wp-content/uploads/2021/02/Guidance-Part-E_Tendering-and-appointments_Edition-2.pdf
  • G-F — IMI Framework (formerly UK BIM Framework, renamed May 2025), Guidance F — About information delivery planning, edition 1, September 2020, archived edition. https://ukbimframework.org/wp-content/uploads/2020/09/Guidance-Part-F_About-information-delivery-planning_Edition-1.pdf
  • S04 — ISO, ISO 19650-4:2022 — Information exchange, 2022. https://www.iso.org/standard/78246.html
  • S16 — ISO, ISO 23386:2020 — Methodology to describe, author and maintain properties in interconnected data dictionaries, edition 1, confirmed 2025. https://www.iso.org/standard/75401.html
  • S37 — IMI Framework (formerly UK BIM Framework), Information protocols supporting the delivery phase (BS EN ISO 19650-2) and the operational phase (BS EN ISO 19650-3) of assets — Guidance, edition 3, August 2022; Information Protocol template for BS EN ISO 19650-2 Ed 6. https://ukbimframework.org/resources/ (checked 2026-11-04)
  • A03 — Autodesk Revit Help, Workflow: Revit Cloud Worksharing; About Revit Cloud Worksharing, Revit 2026. https://help.autodesk.com/cloudhelp/2026/ENU/Revit-Cloud/files/GUID-ABFFFEE6-2C6D-4779-B508-A1C4BC0C4885.htm
  • P08 — Autodesk, Autodesk Certified Professional — Revit for Architectural Design, live programme. https://www.autodesk.com/certification/all-certifications/revit-architectural-design-professional
  • ISO 27001 — ISO/IEC, ISO/IEC 27001:2022 — Information security management systems, edition 3, with Amd 1:2024. https://www.iso.org/standard/82875.html (checked 2026-11-04)
  • PDPL — UAE, Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data, effective 2 January 2022, Active. https://uaelegislation.gov.ae/en/legislations/1972 (checked 2026-11-04)
  • P02 — Penn State Computer Integrated Construction Research Program, Define Supporting Infrastructure for BIM Implementation, BIM Project Execution Planning Guide v2.2, 2019. https://psu.pb.unizin.org/bimprojectexecutionplanningv2x2/chapter/define-supporting-infrastructure-for-bim-implementation/
  • P06 — NPSA, Security-Minded Approach to Digital Engineering, undated. https://www.npsa.gov.uk/security-best-practices/build-it-secure/security-minded-approach-digital-engineering