BBM-STD-53-PIR-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft for office review and adoption
1 Purpose scope and decision ownership#
Project information requirements (PIR) describe the information the appointing party needs at project decision points. Maintain one controlled project set, selecting applicable organisational objectives and project brief needs rather than copying every possible output. This standard covers. The appointing-party representative owns the set; each requirement has one accountable decision owner, an information reviewer and a recorded acceptance route. The producer does not accept its own information on behalf of the appointing party.
Use Office OIR, Glossary, register controls, responsibilities, codes and submissions, UAE authority annex, BoD owner and AIR. The editable PIR forms contain blank registers and a complete synthetic decision trace. Project decision points, information delivery milestones and stage ends are separate records; receiving information before the decision leaves time for checking and correction.
| Scope control | Required entry |
|---|---|
| Project | Project ID, appointment boundaries, objectives, decision stages, included systems/assets and exclusions |
| Decisions | Unique PIR and Decision IDs, question, one accountable owner, options, needed evidence and permitted reliance |
| Authority | Appointing party and delegated recipient scope; technical information acceptance versus actual business/design/statutory decision |
| Timing | Delivery, receiving review/correction and decision dates; dependencies and any stage gate separately |
SYN-P001 is a fictional replacement-design exercise: decide whether the proposed AHU/valve layout can proceed to the next design step with maintainable withdrawal access. It covers AHU-001, VLV-001 and VLV-002 in the AIR fixture. It excludes procurement, fabrication, installation, safety certification and authority permission. A positive information check supports only this declared design decision; it does not establish physical clearance or operational handover.
2 Trace requirement to objective brief and BoD#
Preserve Office OIR identities. OIR-007 ordinarily feeds AIR-007 for maintenance; PIR-007 is applicable here specifically because a replacement project needs a design decision. Do not relabel operational AIR as PIR or treat a project decision as an AIM update. New EIR-011 is a local proposed delivery-coordination allocation; EIR-007 remains the operational allocation. Confirm these allocations in BBM-STD-54 before appointment. No existing EIR- component aliases are reassigned.
| Synthetic trace | Record and baseline |
|---|---|
| Objective and requirement | OIR-007 Office OIR V0.3; PIR-007 R01; decision DEC- |
| Brief | BR- R01: replacement layout shall permit the selected withdrawal task |
| BoD interface | CR-SYN-MAINT01 / SYN-BOD-MAINT01 R01 in this workbook; fictional owner record to reconcile with actual BBM-STD-12 |
| Quantified source | SYN-REQ-A01 R01: 600 mm clear withdrawal envelope, fictional supplier/task input, not a code or office-wide tolerance |
| Owner | SYN-AP01 appointing-party project decision owner; SYN-RR01 delegated information reviewer; SYN-LAP01 authorised submission function |
| Exchange and milestone | EIR-011 / EX- / DEL-SYN-ME01; supporting rows ME-01, ME-02, ME-03 in synthetic plan allocation |
The actual BoD owner confirms the criterion, provenance, applicability and decision consequence. A source identifier without the underlying current evidence is a hold. The workbook's fictional BoD row does not alter the existing BBM-STD-12 deliverable. Record other applicable PIR separately, with their own source and owner; no inference that this one example is a complete real-project PIR set.
3 Information quality uncertainty and acceptance#
For each decision specify objects, geometry/data/documents needed, source revision and provenance, applicable quality limits, uncertainty method, delivery timing, independent check and receiving evidence. A generic stage LOD label does not answer the decision question. Unknown or disputed input remains qualified and is escalated to its owner; missing mandatory evidence cannot be offset by a completeness percentage.
The example requires a coordinated mechanical model showing equipment and withdrawal envelope, a three-asset identity/class/location/system schedule and the source/access note plus exchange manifest. Select exact LOIN, formats and receiving tests through BBM-STD-54. Existing synthetic TIDP model/schedule/note aliases ME-01/02/03 remain intact.
| Test | Synthetic input and required interpretation |
|---|---|
| Source | SYN-REQ-A01 R01 requires 600 mm; missing/superseded source means Hold |
| Positive arithmetic fixture | Proposed clear dimension 650 mm, bounded uncertainty +/-10 mm under SYN-MEASURE01 R01; lower bound 640 mm is at least 600 mm |
| Negative arithmetic fixture | Proposed 605 mm with same +/-10 mm; lower bound 595 mm is below 600 mm: fail this criterion and return for correction |
| Unknown uncertainty | 650 mm with no defensible uncertainty/provenance: Hold, not assumed zero uncertainty |
| Reconciliation | Three unique asset IDs match model and schedule; all applicable required data/documents are present and accessible to SYN-RR01 |
All numbers and the bounded-interval method above are fictional scenario assumptions. They are not surveyed dimensions, universal design tolerances, probabilistic confidence claims or executed native model checks. The actual competent designer supplies appropriate measurement/analysis methods and limits. Information acceptance records exact submitted container revisions/hashes, criterion outcomes, reviewer and date; DEC- records the owner's separate decision and conditions. A permit remains a separate authority decision under BBM-STD-57.
Where an authority requires BIM with the permit, the PIR set includes an authority submission decision row. Dubai: DM circular 9-1-2 (13 Oct 2023; ED-DM-9-1-2) and circular 9-1-3 (15 Jan 2026, effective 1 Apr 2026; ED-DM-9-1-3) require architectural and structural BIM with the permit above the thresholds held in BBM-STD-51 §3 and BBM-STD-85, with drawings extracted from the model; this drives PIR/EIR timing.
| PIR row | Decision question | Required record |
|---|---|---|
| PIR-AUTH R01 | Does an authority BIM permit route apply, and when must the model be submitted? | Threshold test (storeys, built area, alteration type, building use) against BBM-STD-85; result Yes/No with instrument IDs; model/IFC profile (the schema and export setup stated by the authority, recorded in the BEP); submission milestone placed before the permit decision with time for portal validation and correction; owner = authority liaison (BBM-STD-55) |
4 AIR boundary and permitted reliance#
AIR-007 is owned by the asset-information lead/operator and supports ongoing maintenance. PIR-007 is owned by the project decision owner and supports choosing a replacement layout. Both refer to the same assets and source instruction without merging ownership. Delivery information is not installed evidence; later AIR exchanges need verified installed identities, actual instructions and receiving FM tests under BBM-STD-52. The example decision cannot authorise maintenance operation.
| Shared information | PIR use | AIR use |
|---|---|---|
| Asset ID/class/system/location | Identify proposed replacement-design scope and compare model/schedule | Maintain stable installed population and system/location relationships |
| Withdrawal instruction | Check design arrangement for a specified task | Retrieve current operating/maintenance instruction after accepted handover |
| Condition/inspection | Existing-condition input only when needed and source verified | Controlled inspection/update history with operator custody |
Record approved recipients, purpose, version and limitations. SU-COORD and Shared are suitability/CDE metadata, not permission for fabrication. Rights and downstream reliance must agree with the actual appointment/protocol; a workbook entry does not grant a licence.
5 EIR allocation milestones and changes#
Allocate each applicable PIR into the appointing party's EIR with requirement/exchange/milestone IDs, expected products, producer/checker, authorised submission and receiving decision. The lead appointed party allocates relevant downstream EIR and TIDP/MIDP rows without losing the original PIR source. EIR-011 is proposed for this example; BBM-STD-54 must establish its purpose-led LOIN and recipient tests before actual tender/appointment use.
CH-SYN-BASE01 is the initial fictional R01 baseline label, not an approved project change or office adoption. DEL-SYN-ME01 is the primary model trigger; supporting allocation rows retain DEL-SYN-ME02/03 and their respective MA02/MC02 and MA03/MC03 roles. The synthetic baseline submits EX- on 2026-11-26, reserves receiving review/correction to 2026-12-01 and places DEC- on 2026-12-02, before the separately fictional stage end 2026-12-03. Dates are scenario planning assumptions, not authority/ISO response periods. Existing model preparation/check dates remain unchanged.
On change, retain the previous requirement/revision; assess source/BoD/other PIR/AIR implications, obtain the actual owner's decision and propagate one ChangeID to EIR, project BEP, TIDP and MIDP. Record exact notified recipients, version, send/acknowledgment evidence and unresolved consequences. Proposed CH-SYN-PIR01 changes the decision date to 2026-12-04 and required submission to 2026-11-30; it is Open, not applied to current R01 dates. Synthetic notification rows are Pending; a visible register row is not receipt.
6 Use review and release checks#
Populate the blank PIR, decision, allocation and change forms; the example shows the minimum complete trace rather than a compulsory output quantity. Resolve IDs, sources, accountable owner, scope and permitted use, quality/uncertainty, timing, acceptance route and EIR/plan allocation. Reject duplicate PIR/Decision IDs, absent owners, delivery after the decision, unallocated mandatory requirements, broken source/criterion links and undefined uncertainty. Hold affected use until corrected or a scoped authorised departure is recorded; a departure cannot waive statutory duties.
The workbook Tests distinguish expected arithmetic/trace outcomes from actual Not executed receiving results. All required fields must pass, then SYN-RR01 records its information-review recommendation, SYN-AP01 records the scoped information acceptance, and SYN-AP01 records the project decision separately. Actual delegation may name a different authorised acceptance function and must be documented before use. This private draft does not execute DEC-, revise existing MIDP/TIDP, establish actual survey truth or activate an appointment.
References#
- R1. ISO, ISO 19650-1:2018, clause 5.4 PIR reading pointer; ISO 19650-2:2018, clause 5.1.2 project requirements and 5.2.1 appointing-party EIR. Catalogue evidence is not a licensed clause audit. Checked 2026-11-04.
- R2. IMI Framework (formerly UK BIM Framework, renamed May 2025), archived Guidance D edition 2 February 2021, sections 1.4.3/1.4.4, 1.5 and 2.6; resources. Paraphrased decision-led method, no paid text reproduced. Checked 2026-11-04.
- R3. Dubai Municipality, circular 9-1-2 (13 Oct 2023) and circular 9-1-3 (15 Jan 2026, effective 1 Apr 2026). Checked 2026-11-04.
- R4. Writing plan, gap matrix, BEP V0.5, MIDP, TIDP and local owner drafts linked above. Native and receiving-system checks remain future scoped work.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-10-16 | First controlled draft |
| V0.2 | 2026-11-04 | closure: PIR-AUTH authority submission decision row (DM 9-1-2/9-1-3 via BBM-STD-85); BEP V0.5 link; cross-links to current set versions; references re-checked |