BBM-STD-79-FOUR_D_PLANNING-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft
1 Planning use and controlled baseline#
This standard addresses. The appointed planner owns schedule logic, calendars and baseline/forecast; the BIM Coordinator owns model-to-activity mapping and simulation configuration; discipline leads own source scope; the construction/logistics and competent safety/temporary-works functions own their respective method reviews. Confirm actual holders and delegated powers through BBM-STD-55. A sequence animation is a review aid, never evidence that construction is safe, complete or achievable.
Use EIR and LOIN, federation, quality, dictionary, MIDP and TIDP. The delivery plans control information commitments; the appointed construction programme controls construction activities. Link their milestones without treating them as interchangeable schedules. Use the editable 4D forms with paired empty templates and a controlled synthetic sequence. Register the standard and dependencies through BBM-STD-51 before office adoption.
Before work freeze SimulationBriefID/revision, purpose/decision, relevant EIR/milestone, included zones/systems/phases and explicit exclusions; approved programme ID/revision/hash and baseline decision; ActivityID and WBS dictionaries; source models/revisions/hashes and receiving tool/full build; time zone, date/time precision, data date, calendars, constraints, progress rules and permitted audience. Missing schedule approval is a Draft/Hold state, not a baseline inferred from a filename. Re-run the simulation whenever the approved programme revision or a linked source model revision changes; a simulation built on a superseded revision is withdrawn from review until it is re-run. Keep alternative scenarios identified separately; selecting one in playback does not approve it.
SYN-SIM79 R01 is an invented three-object logistics training example for Z01. SYN-SCH79 R01 is the planned baseline; SYN-MOD79 R01 contains temporary scaffold TW01 and permanent partitions W01/W02. All times are Asia/Dubai. Calendar SYN-CAL79 is seven days/week 08:00-16:00, no holidays, fixture only. Dates below are half-open intervals [start,finish); displayed finish 16:00 is the end of a working day, not an extra day. Durations are working hours, not unrestricted elapsed time. The planner must select actual contractual calendars before real use. A real UAE project calendar includes the Ministry of Human Resources and Emiratisation (MoHRE) midday outdoor-work break (set each year by ministerial decision; dates and hours taken from that year's decision, not from this standard), the UAE public holidays as announced for that year, the contractual working week/weekend and any site-specific restrictions; each calendar row records the source decision and date checked.
2 Activity, object and temporary-works links#
Preserve source ActivityID/WBS and native object occurrence identity with source container/revision, location/Zone_ID and type; keep Asset_ID only where applicable, separate from native UniqueId/IFC GlobalId. Each LinkID records task type (construct, temporary install/remove, demolish, hold or approved equivalent), object/selection rule and resolved membership snapshot, phase, time interval, quantity/progress basis, allocation scope and map revision. Name-only search is not stable identity. Re-evaluate saved search membership at each refresh and compare explicit keys/counts.
Many objects may join one activity; one object may join several activities only for declared different phases/portions or install/remove events. A duplicated identical ActivityID/object/type/scope/interval is an error. Where split progress is needed, use nonoverlapping portions or an approved weight rule whose sum equals the intended complete scope; repeated display is not repeated physical work. Summary/WBS rows are not duplicate measurable activities. Nongeometric approvals, inspections, curing or procurement tasks need a declared event/zone representation and owner; do not create fake geometry merely to improve coverage.
| Activity / WBS | Planned interval / hours | Object link | Constraint |
|---|---|---|---|
| A10 / SYN.Z01.TW | 2026-10-19 08:00 to 16:00 /8 h | TW01 install | Temporary scaffold available after 16:00 |
| A20 / SYN.Z01.PART | 2026-10-20 08:00 to 2026-10-21 16:00 /16 h | W01 and W02 construct | Finish-to-start after A10; approved scaffold retained |
| A30 / SYN.Z01.TW | 2026-10-22 08:00 to 16:00 /8 h | TW01 remove | Finish-to-start after A20 |
Define visual states explicitly: TW01 installation shown in progress during A10; available after A10 finish until A30 start; removal shown during A30; absent after A30 finish. W01/W02 show not started/in progress/complete using A20 intervals. Review 19 October 16:00,20 October 08:00,21 October 16:00 and 22 October 16:00. Four link records cover three objects and three leaf activities. Two TW01 links are intentional install/remove, not a duplicate. Report link count separately from unique-object count.
3 Refresh, coverage and controlled change#
Import into an isolated named simulation baseline, record import settings and field mappings, task dates/types, build/profile and source hashes. Compare programme and model refresh separately before combining. Reconcile added/retired activities, changed WBS/logic/calendars, new/replaced/deleted geometry, selection membership, IDs and transforms. Do not assume synchronisation deletes retired tasks or resources; check both source and simulation populations. No automated source write-back is authorised by a simulation brief alone. Where the programme must move between tools (BEP V0.5 §9.2 lists Synchro PRO and Navisworks), an optional open 4D profile row in BBM-STD-74 carries the schedule as IFC IfcWorkSchedule/IfcTask with IfcRelAssignsToProcess links to the objects; it is qualified like any other exchange profile and does not replace the native programme.
Coverage report lists required unique objects, linked/unlinked/excluded objects with reasons, leaf activities linked/geolocated/nongeometric/unrepresented, duplicate/conflicting allocations and out-of-scope links. Denominators freeze to the approved scoped source set and data date. Fixture R01 is 3/3 unique objects and 3/3 leaf activities represented by 4 links, with 0 unexplained omissions. These are expected fixture counts, not a measured native result. A passing percentage cannot conceal one omitted mandatory activity or temporary-works dependency.
Preserve approved baseline, current forecast and recorded actuals in distinct fields. Every update has ChangeID, author, source revisions, difference report, impact on downstream tasks/logistics/safety and independent planner/map checks. SYN-CH79-01 forecast delays A20 finish to 22 October 16:00; A30 forecast must move to 23 October 08:00-16:00 under the same calendar. The original baseline remains 21/22 October respectively. Leaving A30 at 22 October 08:00 overlaps incomplete A20 and fails the stated dependency. Approved information-delivery changes propagate by one ChangeID into TIDP/MIDP; programme approval remains with the appointed planner/authoriser.
4 Planned, recorded and forecast progress#
Show separate planned progress at data date, evidence-supported actual progress and remaining-work forecast. Each actual record requires ActivityID/object or portion, measurement method/quantity/unit and denominator, observation date/time, authorised observer, source record/photo/survey/inspection reference and revision, acceptance limits and verification. A coloured object, task date, model save, claim or AI interpretation is not field evidence. Actual dates cannot be future observations. Keep not started, unknown and measured zero distinct; do not populate missing actual dates with planned dates.
Synthetic data date 20 October 2026 16:00: A20 has 8/16 planned hours elapsed, giving 50% planned under an explicitly uniform-hour assumption. Its measured-work fixture says W01=6 m2 of 10 m2, W02=0 m2 of 10 m2, yielding 6/20=30% recorded progress; the signed source is represented only by invented SYN-OBS79 R01 and no actual observation is claimed. Difference is -20 percentage points; it is not earned value or proof of labour productivity. Forecast completion remains the planner's evidence-based remaining-work decision. A10=100% and A30=0% in the fixture do not justify averaging activity percentages without agreed weights.
Use approved physical-quantity or milestone rules appropriate to the task; distinguish installed, inspected, tested and accepted. Record partial completion, rework and rejected work without silently erasing history. If observation coverage is incomplete report unknown portions and confidence limits; a weighted result must show its actual weights, consistent units and dated denominator. Any claimed progress status carried to a dashboard retains this evidence lineage under BBM-STD-83 when adopted.
5 Constructability, logistics and review outputs#
At each baseline/source/change review the planner checks schedule logic/calendars; construction manager checks workface/plant/laydown/delivery routes; logistics reviewer checks occupied access/egress interfaces; temporary-works designer checks required support/install/remove dependencies; competent safety lead checks hazards and control evidence, with each hazard ID from the ISO 19650-6:2025 structured health and safety records (BBM-STD-88) linked in the Reviews form to the ActivityID and time interval where it applies; discipline coordinators check permanent/temporary spatial scope and transfers. Appointed technical/safety approvals remain separate from information acceptance. Refer design and residual hazards to BoD, authority register and Manual 9.4; do not invent safe distances or a lawful work method.
Define plan/perspective and critical-time views, saved camera, legend, source/baseline/data-date overlay, selection visibility, time step/playback rate, output resolution/codec and formats to the approved review brief. Show baseline/planned, actual and forecast as labelled modes, with unknown and excluded scope visible. Inspect critical boundaries rather than relying on an animation that skips a short clash. Deliver underlying schedule/link/configuration manifest alongside review stills/video so a receiver can reproduce the stated state; a video is not an editable programme.
Issue79-01 deliberately removes TW01 at 20 October 08:00 while A20 is incomplete. Record unsafe/unreviewed support-sequence concern, affected links/tasks/revisions, accountable temporary-works/construction reviewers, permitted interim restriction, correction and independent retest evidence at critical times. Expected correction retains TW01 through A20 and removes it under A30. The synthetic disposition is Hold pending competent review; no safe scaffold design or site sign-off is fabricated. Use BBM-STD-68 nonconformity/corrective-action records for recurring/systemic defects.
6 Reproducibility, tests and receiving decision#
Workbook forms: Brief, Activities, Links, Progress, Coverage, Changes, Reviews, Tests and Acceptance with empty counterparts. Values and expected outcomes are manually maintained training specifications; no executable simulation, native model or signed progress evidence is delivered. Recompute after edits. The receiver must later record actual tool builds, source/output hashes, import/log files, saved profile and screenshots at named times, discrepancy IDs and independent reviewer.
Reset each test to R01. T79-01 omits W02 link: 2/3 objects represented and orphan required object W02; Fail, restore L79-03. T79-02 moves A20 start to 19 October 08:00: predecessor A10 incomplete; Fail, restore 20 October 08:00. T79-03 duplicates L79-02 exactly: duplicate pair/scope; Fail, remove duplicate while retaining TW01 install/remove. T79-04 reports 100% actual from the completion colour without observation: Hold, restore dated 6/20 record and evidence limitation. T79-05 advances scaffold removal into A20: Fail, restore A30 timing and obtain competent review. T79-06 applies forecast change without moving A30: Fail, preserve baseline and move forecast A30 to 23 October. Reproduce positive and adverse states in the selected tool, capture actual results and correct/retest independently; all such executions remain Not executed.
Release only the exact reviewed source/schedule/link/configuration package for its approved purpose. Producer checks, independent planner/coordination review, scoped delivery authorisation and receiver acceptance remain distinct signed records. Missing mandatory links, inconsistent source revisions, unreviewed safety implications or unsupported actual progress hold affected reliance regardless of animation quality. Retain failed/retested states and immutable baselines under BBM-STD-76. Office adoption, project calendars/logic, actual host simulation and receiving-use acceptance remain explicit activation holds.
References#
- Matrix, plan outline 32; office Glossary 5.3, BEP 3.2, MIDP/TIDP and linked owners retain terminology and authority.
- Autodesk TimeLiner workflow, task fields compared with Bentley baseline/synchronisation: link membership and preserved baselines matter; visual defaults are not project schedule decisions. Tool-version documentation is not installed qualification.
- MoHRE for the annual midday-break decision, checked 2026-11-04 (year-specific dates are read from that year's decision).
- NIBS NBIMS-US v4 BEP and BCA Guide v2, historic benchmark (2013) inform use-led execution planning.
- ISO 19650-2:2018 clauses 5.6/5.7 reading pointers for production/delivery and IMI Framework (formerly UK BIM Framework, renamed May 2025) archived Guidance Part A ed2. ISO 19650-1, -3, -5 and ISO 7817-1 give lifecycle, security and LOIN context; ISO 19650-6:2025 structured H&S information and ISO 16739-1:2024 (IfcTask/IfcWorkSchedule), checked 2026-11-04; BS EN 17412-1:2020 is legacy predecessor. Licensed clause verification remains required for formal conformity.
- ADM Code October 2020 sections 3.1/3.2 has a historical infrastructure-specific 4D profile; it is not a universal current UAE mandate. DM/DMT/DDA applicability routes remain in BBM-STD-57; DDA design service does not make a simulation an authority approval. Checked 16 October 2026; confirm actual project route/editions.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 16 October 2026 | First controlled draft. |
| V0.2 | 4 November 2026 | closure: UAE calendar content (MoHRE midday outdoor-work break, public holidays, contractual weekend) in §1; ISO 19650-6:2025 hazard links in §5 via BBM-STD-88; optional open 4D profile (IfcWorkSchedule/IfcTask) via BBM-STD-74 in §3; IMI Framework naming; links to MIDP/TIDP V0.3; spacing fixed. + cross-doc pointer pass. |