BBM-STD-76-RECORDS_AND_RECOVERY-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft
1 Record classes and authorised custody#
This pack covers /085. Preserve Manual V0.5 sections 9.4, 12.2 and 12.5, office register and responsibilities as the existing controls. Apply BEP mobilisation/recovery and worksharing guide 22. The editable schedule and test forms separate approved rules, test specifications and actual evidence.
The records owner approves custody/classification with actual appointment and regulatory sources; legal specialists determine applicable holds/durations within their remit; IT owns backup/restore operation; Security Lead approves protected access and incident containment; model/data owners verify restored meaning; the project return-to-work authoriser makes the scoped reopening decision. Record holders/deputies and approvals before operating. This pack gives no legal advice; the retention schedule (BBM-STD-90 §3, record classes RC-01..RC-09) and the personal-data rules (BBM-STD-90 §4) are owned by BBM-STD-90 and ruled on by the legal owner; the office minimum there is 13 years after handover. Summary of the baseline BBM-STD-90 holds: under UAE decennial liability (Federal Decree-Law No. 25 of 2025, Civil Transactions Law, in force 1 Jun 2026, Art. 821: engineer and contractor jointly liable for 10 years from delivery; Art. 823 voids exemption clauses; Art. 824: claims barred 3 years after the collapse or defect; for contracts signed before 1 Jun 2026, Federal Law No. 5 of 1985 Art. 880), design, issue and approval records are kept at least 10 years after handover plus the 3-year claim period, and the final period per class is set by the legal owner.
Record classes include signed appointments/approvals, immutable issue/exchange sets and decisions, native worksharing models with dependencies, operational AIM and safety records, QA/change evidence, private training/competence records and transient working caches. Each schedule row requires ClassID, scope, custodian/storage and sensitivity, applicable source/edition/clause, trigger, duration/unit, holds, access, review, disposal authority and method. An unknown duration remains Unresolved—retain pending competent determination; it never means zero days. Retention begins at the defined event, not automatically a file modification date. Keep records necessary for continuing operational/safety obligations after delivery where required: the safety record class follows ISO 19650-6:2025 structured health and safety information (BBM-STD-88), and for Dubai buildings the records needed for the Quality & Safety Certificate inspections under Dubai Law No. 3 of 2026 (certificate needed after 20 years from completion, valid 10 years, 5 years once the building is 40 years old) stay with the AIM (BBM-STD-75 §6). Personal-data record classes (staff, training/competence, directory, learner and metrics records) cite the UAE PDPL (Federal Decree-Law No. 45 of 2021, effective 2 Jan 2022, plus any Executive Regulations listed on uaelegislation.gov.ae at project start) as their source value; their disposal and data-subject requests follow BBM-STD-90.
ISO 19650-1:2018 clauses 11/12 are collaborative-production/CDE reading pointers; -2:2018 clause 5.8 concerns close-out; -3:2020 clause 5 supplies operational-process context; -5:2020 supplies proportionate security context. The licensed text and actual appointment determine applicability. Office archive and IT procedures below are local selections, not copied ISO clauses or statutory durations.
2 Immutable issue records and portable archives#
Freeze each authorised issue with ExchangeID, exact native/export/drawing/data/doc versions, approvals/rejections, receipt/acceptance records and restrictions. Hashes prove byte identity, not technical adequacy or authority. Corrections create a new controlled revision linked by ChangeID; preserve the issued literal and decision trail. Apply existing eight-token external naming and project CDE mappings under BBM-STD-51, not a competing archive naming grammar.
ArchiveManifest records ArchiveID, container/asset ID, relative path, revision/state, bytes/SHA256, source URI, creation/issue time with timezone, owner, format/full build, sensitivity, rights, dependencies, retention class/trigger and retrieval index. Include linked models/Xrefs, coordinate baseline, fonts/plot resources where licensed, dictionaries, profiles, document links, issue records and viewer/export/readme sufficient for future interpretation. Register dependencies not distributable under licence as controlled references and establish a lawful retrieval route. Do not archive licence keys or cache copies of credentials.
Use one indexed archive authority and approved protected backup replicas with registered purpose, not uncontrolled working-tree duplicates. A cloud sync directory and vendor version history do not independently establish immutable archive or backup coverage. Test search by stable container/asset/exchange ID and retrieve a dated issued set without confusing it with current WIP. Verify manifest hashes and dependency resolution; migrate formats only under approved comparison with original retained. Every issued PDF is also archived as PDF/A (ISO 19005; the part, for example PDF/A-2 or PDF/A-3, is selected per class in the schedule) beside the native and issued files, with the validator name/version and its report recorded in the ArchiveManifest; a PDF/A copy never replaces the issued original. Sensitive originals and access metadata require protected custody; an open readme must not expose restricted system details.
3 Backup responsibility schedule and recovery targets#
Perform a business-impact review before setting a recovery point objective (RPO, tolerated data-loss interval) and recovery time objective (RTO, recovery time target). Record supported route, scope, full software/service builds, consistency method, backup owner/deputy, schedule/timezone, monitoring, protected independent location, encryption/key-recovery custody, retention/rotation, capacity, restoration method and evidence. No credentials or recovery secrets belong in the workbook. Confirm vendor/service entitlement, history limits, export restrictions and dependencies with actual administrators.
| Supported route to qualify | Backup and restoration requirements |
|---|---|
| File-based Revit/CAD | Protect consistent central/model plus associated backup data and linked dependencies; use supported central-backup recovery, preserve useful locals/unsynchronised changes and never manipulate live backup internals |
| Server/cloud worksharing | Use the supported service restore/version procedure for the actual tenant/model; verify native sync history separately from browser publication and include documents/permissions/issue data in assessed coverage |
| CDE issue/archive | Export or back up files with metadata, versions and formal decisions through the approved service; qualify what cannot be exported and arrange retrieval/custody before offboarding |
| AIM/records store | Consistent data/document/identity and history backup; recheck referential integrity, active/retired asset state, current documents and updater access after restore |
For the fictional SYN-BACK76-01 tabletop only, the business owner proposes RPO 4 hours and RTO 8 hours because the exercise assumes four-hour batch commitments and an eight-hour restart window. Illustrative schedule: consistent protected snapshot every 4 hours plus a separately protected daily copy, monitored each run. These are scenario assumptions needing measured capacity/support tests, not office SLAs, ISO values or a real backup configuration. Latest clean snapshot 08:00 and incident 11:00 implies 3 hours lost; service-ready 17:00 from incident 11:00 implies 6 hours recovery. Both expected values meet that fictional proposal, but only a real restore can establish actual performance. A contaminated or incomplete recent snapshot does not qualify merely because its timestamp meets RPO.
Maintain protected/offline or otherwise independently isolated backups appropriate to risk, separated administration and tested restoration. Backup job success and retained file size alone do not prove recoverability. Review after route/build/dependency changes, incidents and the approved test schedule; actual recurrence must be assigned, not inferred from an empty calendar. The Backup, Restore and Disposition forms map to the ISO/IEC 27001:2022 (+ Amd 1:2024) Annex A controls for information backup, information deletion, secure disposal or re-use of equipment and storage media, and access control; the exact control IDs are taken from the licensed text by the Security Lead and recorded in each form, and the security triage and security management plan are owned by BBM-STD-87.
4 Isolated restoration and return to work#
- Log IncidentID/time/scope and stop affected writes through the owning administrator. Preserve suspect central/service history, potentially useful locals and evidence. Do not delete caches or overwrite a live model as an experiment.
- Select a demonstrably clean supported recovery point, recording source backup URI/hash, completeness, malware/incident checks and expected lost transactions. Reconcile uncertain prior operations before replay. Preserve the previous state/recovery path.
- Restore into an isolated destination approved for the same sensitivity, with the exact compatible application/service route. Never point restored references or synchronisation at production until the return decision. Follow vendor-supported detach/save-as/new-central procedures where applicable; a copied live central is not automatically a valid restored central.
- Check file/hash inventory, opening/version/warnings, datum/control points and link paths, known geometry/object counts/IDs, sheets/tags/schedules, mandatory properties/units, documents, issue/history state, permissions and received exchange. For database/AIM, verify foreign keys and active/retired/replacement history. Register all missing/changed work and reconciled or explicitly excluded transactions.
- In a disposable coordinated test, verify fresh authorised sessions/locals, two-user borrow/sync/relinquish and denied-role behavior for worksharing, or equivalent route-specific transactions. A successful single-user open is insufficient.
- Independent technical owners sign scoped checks. The authorised project/IT/security decision records accepted baseline, limitations, lost/recovered work, user notification, new-session instructions and rollback trigger. Reopen only that scope and monitor the first coordinated transaction; any mandatory failure keeps it held.
The Restore form has requested/actual point and timestamps, measured RPO/RTO, actual tool/route, source/destination hashes, checks/observations, checker, decisions and evidence. Synthetic values are expected tabletop calculations only; actual status Not executed. No recovery command or restore is authorised on a real central or tenant by this editorial standard.
5 Holds offboarding and authorised disposition#
Maintain a protected Hold register with HoldID, issuing authority/reference, record/asset scope, effective date, preservation action, review owner/date and written release authority. On hold, suspend affected disposal including routine rotations where feasible; IT records platform limitations, overwritten historic gaps and necessary preservation/export action. Do not promise deletion or preservation capabilities that the service lacks. No destructive action is performed by this pack.
At joiner/mover/leaver or project close-out, inventory access, shared links, downloads, devices and third-party copies; transfer custody and test continued authorised retrieval before revoking obsolete access. Require scoped acknowledgements and document exceptions, lawful retention and backups. Turning off an account does not dispose of downloaded copies. Do not remove needed operator/safety access during an incomplete handover.
At authorised expiry, independently check class/trigger/duration/source and absence of holds, scope and approvals. Inventory exact copies/replicas/media and dependencies; preserve required evidence and related records. The records authority and technical/security owners approve the method and verification, then record actual disposal date, operator, files/media, outcome/certificate, exceptions and residual-backup expiry/access controls. Ordinary file deletion is not proof of secure sanitisation. For backups that cannot delete an individual record, document restricted continued custody, rotation/expiry and any post-restore reapplication of authorised deletion; no false immediate-erasure claim. Verify retrievability of retained records and absence of disposed active copies within the claimed scope.
6 Worked failure retest and activation conditions#
Synthetic REST76-NEG specifies a restore with an omitted linked model and a missing current O&M document: expected FAIL regardless of native file opening. The corrective case restores the complete dependency manifest into isolation and repeats geometry/data/access/exchange and worksharing checks. A separate permission-negative case denies the authorised receiver: repair role mapping, retest allowed and denied roles. Both remain Not executed; a fictional successful retest does not establish actual recoverability.
The Retention, Archive manifest, Backup, Restore, Restore checks, Hold and Disposition forms contain blank capture fields and synthetic instructions. Before activation resolve actual appointment/regulatory retention sources, adopted routes/builds, custody/permissions, RPO/RTO with justified schedules, clean/complete isolated recovery evidence, return-to-work authority and backup/disposal limits. Only an actual observed restore can establish the recoverability claim; editorial review establishes the pack's specification quality.
References#
- Existing office Manual/BEP/register/roles and guide 22 linked above; matrix /085. Paid-standard reading pointers are paraphrased and require competent licensed review.
- ISO 19650-1:2018, 19650-2:2018, 19650-3:2020, 19650-5:2020, catalogue scope/edition checked 2026-10-16; IMI Framework (formerly UK BIM Framework, renamed May 2025) resources for CDE/close-out explanation.
- CISA StopRansomware guide: independently protected backup and restoration testing context, checked 2026-10-16. No blanket compliance or office technology selection claimed.
- ISO/IEC 27001:2022 + Amd 1:2024; ISO 19650-6:2025; ISO 19005 PDF/A family (ISO catalogue, part 1), checked 2026-11-04.
- UAE legal sources, checked 2026-11-04: Federal Decree-Law No. 25 of 2025, Civil Transactions Law (Art. 821–824); Federal Decree-Law No. 45 of 2021, PDPL; Dubai Law No. 3 of 2026, Quality and Safety of Buildings. Owned by BBM-STD-90; no legal advice given here.
- NIST SP 800-34 Rev. 1, business-impact/recovery-target context; RPO glossary. Guidance is not a UAE retention statute.
- Autodesk Revit 2026 Recover a Workshared File, file-based recovery route. Actual project builds/cloud routes need separate qualification; source checked 2026-10-16.
- ISO 7817-1:2024 and retained BS EN 17412-1:2020 predecessor inform purpose-led restoration checks. DM circulars, DMT infrastructure guidance and DDA Circular 400 (held as a register row in BBM-STD-57; date and content not restated here) do not supply a universal records duration; actual applicability belongs to BBM-STD-57/records owner.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 16 October 2026 | First controlled draft. |
| V0.2 | 4 November 2026 | closure: decennial-liability retention baseline (Decree-Law 25/2025 Art. 821/824; 1985 law Art. 880 for older contracts) with the schedule owned by BBM-STD-90; ISO/IEC 27001:2022 + Amd 1:2024 controls mapped to backup/disposal; UAE PDPL source for personal-data classes; PDF/A (ISO 19005) archive copies; ISO 19650-6:2025 safety records; Dubai Law No. 3 of 2026 asset-life record need; links to Manual V0.4/BEP V0.5; spacing fixed. + cross-doc pointer pass. + template alignment (..148) |