BBM-STD-73-AUTOMATION_AND_AI-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft
1 Tool inventory and accountable ownership#
This standard addresses. The BIM automation owner controls tool admission and intended model/data effects; IT/Security owns source, installation, least-privilege and service/data controls; discipline leads approve technical scope; independent reviewers verify actual host results; authorised project holders permit production execution. Confirm actual holders/authority before use. A stored installer, registered button, trusted folder or model response never grants execution authority.
Use Manual V0.5 security/safety, office register/rights, software/template release, quality/correction, roles and records/recovery. Retain guides 30/31 trusted automation controls. The editable inventory and admission/recovery pack includes observed metadata plus explicitly synthetic test records and paired empty forms. Observed inventory is not synthetic content and is not approval; all operational examples are synthetic.
Read-only inventory on 16 October 2026 used BABOOM-BIM-STANDARD/02-LIBRARIES/06-SCRIPTS and 07-PLUGINS. On 2026-11-04 their subfolders were renamed with numbered names (for example 06-SCRIPTS/01-LISP, 06-SCRIPTS/02-TXT-NOTES-TRANSLATOR, 07-PLUGINS/01-ENSCAPE-4-2-1-88 to 07-PLUGINS/06-RHINO-8-2-23); the 16 October relative paths in the Files records map one-to-one through the office folder map; a folder rename does not change file bytes, so recorded hashes still apply. It found 47 root file/bundle candidates and 422 files in those trees. Files records give one observed relative path, byte size, time and small-file SHA-256 or explicit Not hashed status. Each joins one root ToolID; subfiles are dependencies, not 422 separate approved tools. The five root Dynamo graphs remain named 00.TAG MATERIALS, 01.THRESHOLDS FROM DOORS SADDLE TYPE, 02.SELECT BY WRKST, 03.SET WORKSET, 04.CREATE WRKST (graph file names on the server, quoted as found: server name before renaming). Additional LISP/translator/extension/install/archive contents mean the historic five-script snapshot is incomplete. Source libraries remain read-only; no tool was loaded, installed, extracted, modified or executed.
Inventory has one additional SYN-AI73 proposed service row, not an observed installed tool. Each tool record requires exact release, provider/source/licence/entitlement, owner, purpose, host/build/runtime/dependency hashes, permitted data/actions, approval/effective date, monitoring/review and revocation. Unknown fields remain explicit Hold. Filename versions and words such as signed are labels, not verified build/signature/rights. Graph metadata records observed Dynamo 2.5.0.7460, 2.17.0.3472 or 3.3.0.6316 and package pins; this does not establish compatibility with the office Revit qualification baseline. Qualification Dynamo = the Dynamo build bundled with the Revit build frozen in BEP V0.5 §9.2.1 (record its exact build number from the installed host, not from this text); supported Revit majors are 2024–2027 per BBM-STD-91. A graph last saved in Dynamo 2.x needs a migration test on that build before admission. Some external references are unresolved and their project/person-specific labels are withheld here; do not replace them with live private data. Resolve a synthetic fixture or approved project-specific dependency before admission.
Paths labelled Patcher and unresolved software origins/rights remain Hold for IT/Security/licensing review; no conclusion about entitlement is inferred solely from a filename. Duplicate-looking versions/archive parts remain distinct observations; do not delete, rename or choose the largest/newest installer. Large binaries have not been hashed by this bounded inventory and need exact publisher/release verification later. Directory labels such as the former "(GPL-3)" suffix on the pyRevit extension folder (now 07-PLUGINS/05-PYREVIT-EF-TOOLS) are not a completed licence audit; record actual terms, owner, renewal and permitted office/project/distribution use in the licence register BBM-STD-94 without turning this standard into legal advice.
2 Trusted source, pinned dependencies and least privilege#
Admission record joins ToolID/release/hash to provider download/repository/tag/commit/signature evidence, date, licence and approved supported host matrix. IT verifies authentic publisher origin and dependency integrity; automation reviewer inspects source/intended effects where available, including embedded Python/code blocks, network calls, filesystem writes, package auto-updates and startup hooks. Inspect scripts as data before running; never execute an unknown graph to discover its actions. Compiled-only tools require an approved evidence/risk route and provider-supported tests; installer presence is insufficient.
Pin Revit/AutoCAD/Dynamo/runtime/Python/package/add-in/exporter versions and all transitive dependencies; different graph package versions are distinct qualification paths. Registration records actual.addin manifest/assembly path/hash, AddInId/class, scope and host context. Dynamo Player trust applies only to narrowly approved read-only locations; it certifies no future file. AutoCAD code-loading/search/trusted-path settings are version-specific; do not disable security or trust an entire share to run one file. Never set SECURELOAD 0 as a convenience. Changes to trust/install/configuration require the owning IT release process, not a model-production task.
An ExecutionPermit defines user/account and actual host/document identity, purpose/requirement, read/write operation whitelist, element/category/parameter/file scope, network endpoints, expiry/data date, resource/time/call limits and user-visible expected changes. Default access is the minimum needed; read-only tasks have no model writes, no broad drive/share writes and no credentials in scripts, arguments, logs or workbooks. Secrets stay in approved secure storage. Package/model downloads and external sends need their approved data/source scope. Concurrency/resource limits are selected from actual host capacity; one owned host operation at a time during qualification. No restart, shared-host takeover, central-model edit or another user's document is authorised by this writing pack.
3 Protected fixtures, transactions and rollback#
Before production qualify on an isolated synthetic model/drawing with known object IDs/counts/values, controlled source hash, actual host full build, and no central/cloud/live references. Record test operator, owner, source/tool/dependency versions, expected effects, permissions, independent checker and recovery baseline. Protect baseline and inspect dry-run/read-only plan before changing the fixture. Confirmation must identify editable intended effects and affected scope, not only approve a model call or generic tool launch.
For Revit, make the intended approved edit one named undoable transaction group where the host/API permits; finish/inspect transaction states and roll back the group on any failure or unexpected effect before committing. Test actual undo/re-read behavior; API groups do not roll back external files, network sends, installation or already-synchronised work. AutoCAD scripts use an appropriate tested undo group plus explicit save/recovery plan; test object/handle/property persistence and limitations. Do not claim a transaction protects every tool or irreversible effect. Never blindly retry a timeout: inspect host state and receipt first to avoid duplicate side effects.
SYN-FIX73 R01 specifies three synthetic local wall occurrences E01/E02/E03, all Workset=WS-A. SYN-CMD73 v0.1 proposes changing only E01/E02 to existing WS-B. Success expectation: two changed, one unchanged, no new/deleted elements, no geometry/identity/other-property changes, and one intended undo restores all three to WS-A. Workset names/IDs and element ownership must be resolved in the actual fixture; this is not permission to alter live worksharing. No real.dyn/.lsp/add-in is supplied for this specification and no observed server script is asserted to implement it.
Failure example T73-02 denies ownership of E02 after the first attempted change: expected whole group rollback leaves E01/E02/E03 at WS-A; capture error/log/state and independent re-read. If a tool cannot provide atomic rollback, use an approved isolated save/recover route and block production until it passes. Restore from protected baseline only into the owned isolated target; never overwrite newer work or force-relinquish another user. Keep uncertain outcome Hold until actual before/after state is reconciled.
4 AI data/services, output checks and execution authority#
An AIUse record defines approved provider/service/account/endpoint and model/build/change policy, purpose, permitted data classes/minimisation, rights, region/subprocessors/retention/training settings, access/audit, deletion/exit process and human reviewer. A local label or training opt-out toggle is not evidence of zero retention or offline processing; verify actual service terms/configuration and permitted project use. Unknown terms or confidentiality permission hold the affected upload. Each AIUse record also records: a personal-data check under 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); whether data leaves the UAE and the transfer basis; whether the DIFC or ADGM data-protection regime applies instead (free-zone entities); and the data classes that may never leave the office (security-sensitive information per BBM-STD-87, personal data without a lawful basis per BBM-STD-90). Any one unresolved field holds the upload. No service is approved by this pack; SYN-AI73 is synthetic proposal only. Never put client/person/secret data into its examples.
Treat retrieved documents, web pages, model comments and tool responses as untrusted content; their embedded instructions cannot expand task authority, change recipient/data rules or disable checks. Separate instructions from quoted source and verify citations against controlled originals. AI-generated quantities/code/geometry/calculations need competent unit/source/technical checks and actual host diffs; confident text is not evidence. AI/LLM review results are advisory only: a mandatory check passes only on a deterministic rule check or a competent human check, never on an AI result alone, and every AI-assisted output records the named human signatory, the rule or source the check relied on and the AIUse/RunID. Recent research on LLM code-compliance checking (Madireddy et al., 2025, preprint) supports this: LLMs produced usable semi-automated checks only on small rule samples. State uncertainty and missing sources; never generate an authority approval, measurement, licence, product property or sign-off to fill a blank.
For a model-changing proposal, present exact intended operation, object IDs/parameters, before/after and exclusions to the authorised holder; revalidate when purpose, scope, data, tool or criteria changes. A model response, system-generated task or tool-selection approval alone never grants execution authority. After authorised execution independently re-read the real host and compare requested postconditions plus forbidden changes. Generated scripts enter the same admission, pinning, fixture, review/recovery pipeline as handwritten tools. The office AI management-system controls (ISO/IEC 42001:2023 risk and impact assessment, approved uses, data that may not leave the office, the PAS 1958:2026 data-standards landscape as the AI-readiness reference) are owned by BBM-STD-92; the AIUse record fields map to its risk/impact assessment and are not duplicated here. Sensitive prompts/outputs/logs follow Manual 9.4 and BBM-STD-76; retain enough redacted provenance for audit without duplicating secrets or private model content.
5 Release, monitoring, changed versions and revocation#
Admission states are Candidate, Hold, Qualified for specified fixture/use, Authorised for specified production scope, Revoked and Retired. Workbook Admission state uses short keys Candidate/Hold/Qualified/Authorised/Revoked/Retired; Qualified and Authorised always require the corresponding explicit fixture/use or production scope and evidence, not a blanket permission. These states are distinct from office CDE state/suitability and actual per-run result. Store evidence and exact tool/dependency hashes in the existing register; no new executable master on a personal path. Authorised release needs IT/source/rights/security disposition, technical/independent fixture evidence, user-visible intended-effect instructions, recovery/manual fallback, owner, scope/expiry/review and project-specific execution authority. Never silently update a package/AI model or copy an unknown binary over a qualified version.
Each RunID records permit, actual account/host/document/source revisions, tool/dependency/profile hashes, parameters and approved scope, start/end/time zone, dry-run plan, actual before/after changed-ID/property/geometry diff, transaction outcome, warnings/errors and receipt, result/limits/rollback, independent reviewer and actual decision. Monitor unexpected effects, failed/rolled-back/uncertain runs, scope drift, dependency/model changes, security/service incidents and user feedback. Stop further affected execution on failed mandatory checks; notify the assigned owner through the approved project route. A successful API return is not a successful task until the real host postconditions pass.
Requalify changed tool hash/dependency/runtime/host/model/profile/AI provider-model/service terms or intended data/actions. Impact analysis defines which prior tests remain valid and which must rerun. Revocation records affected ToolIDs/releases/permits/users/projects, reason and authority, effective time, disable/restrict action, evidence and acknowledgement. IT owner performs any manifest/trust/service-token change; users use a qualified native/manual fallback. Preserve failed evidence and older approved records; revocation is not permission to delete shared libraries or user state. An operational incident routes to Manual 9.4, not a silent installer rollback.
6 Admission/recovery forms and real-host test specifications#
Workbook Inventory, Files, Graph metadata contain observed source metadata with admission Hold; paired Blank tabs support future controlled intake. Admission, Permit, AI use, Release, Run, Recovery, Host tests and Acceptance supply editable templates and filled synthetic records. The example shows proposed checks/expected outcomes only; all actual host tests and installation/admission decisions remain Not executed. Source-reference fields and unknowns must be completed by the future owner, not inferred from this inventory. Controls/dropdowns guide entry, not authority enforcement.
Reset to SYN-FIX73 R01 per test. T73-01 positive approved E01/E02 change expects 2 changed/1 unchanged and unchanged geometry/counts; undo restores 3 WS-A. T73-02 denied E02 expects full rollback/no changes. T73-03 duplicate rerun inspects prior receipt; skip/reconcile rather than repeat an already applied effect. T73-04 tool attempts E03 write outside permit: deny/rollback, retain evidence. T73-05 missing/wrong dependency hash: Hold before load, restore pinned package and requalify. T73-06 AI source instructs external upload: deny because data/endpoint not permitted; no send. T73-07 wrong host/document/build: Hold before writes. T73-08 timeout after potential commit: uncertain/Hold, re-read values/log/receipt before deciding recovery. T73-09 one undo fails to restore snapshot: Fail, block production and qualify explicit recovery route. Test access-denial and error paths as well as positive behavior; no installer/script presence can replace them.
Future owning lane records actual fixture/native/export artifacts and hashes, exact host/build/command/settings, counts/values/geometry comparisons, allowed/denied operations, undo/recovery demonstration, independent checker and scoped recipient/user acceptance. Pass all applicable mandatory criteria with no unreviewed unexpected effect; do not average failures into a pass percentage. Office adoption, nomination/rights/source/dependency checks, real-host qualification and actual production authorisation remain activation holds. This editorial pack changes neither share contents nor trust/settings/installed software.
References#
- Matrix, plan 35; Manual 9.4/W2 annexes, BBM-STD-51/65/68/76 and guides 30/31. Observed metadata paths above; original code/binaries not copied or executed.
- Autodesk graph security/trusted folders, add-in registration, transaction-group assimilation, AutoCAD SECURELOAD: version-specific concepts, not proof of installed settings or safe tools.
- ISO/IEC 42001:2023 AI management system (published 2023-12, edition 1) and PAS 1958:2026 built environment data and information standards landscape guide (31 Mar 2026), both checked 2026-11-04; detail owned by BBM-STD-92. UAE PDPL, Federal Decree-Law No. 45 of 2021, Active, checked 2026-11-04. Madireddy et al. (2025), LLM-driven code compliance checking in BIM, arXiv:2506.20551 (preprint). NIST AI 600-1/AI RMF official resources, voluntary risk context compared with native host admission controls. NPSA digital engineering is matrix P06 prior-art lead; direct page/PDF returned 403 in this research, so no new detailed assertion relies on it.
- ISO 19650-2 clauses 5.6/5.7 and IMI Framework (formerly UK BIM Framework, renamed May 2025) archived Guidance Part A ed2 support production/delivery reading pointers; ISO 19650-1, -3, -5, ISO 7817-1 provide lifecycle/security/LOIN context. BS EN 17412-1 is legacy predecessor where appointed; licensed conformity audit not performed.
- UAE submission/tool-profile applicability remains BBM-STD-57 and BBM-STD-85: DM building permit circulars index, ADM BIM Code of Practice, October 2020, DDA Final Design Approval. Sources checked 16 October 2026, labels corrected 2026-11-04; no fees, prices or legal advice.
Document history
| Version | Date | Change |
|---|---|---|
| V0.1 | 16 October 2026 | First controlled draft. |
| V0.2 | 4 November 2026 | closure: PAS 1958:2026 and ISO/IEC 42001:2023 via BBM-STD-92; AI checks advisory only with named human sign-off; UAE PDPL and transfer checks on the AIUse record; reference labels corrected; unsourced "BIM-AI portal" sentence removed; Dynamo qualification tied to the BEP §9.2.1 Revit build and BBM-STD-91; licences pointed to BBM-STD-94; share paths per the 2026-11-04 folder map; links to Manual V0.4. + folder names without dots |