One Equipment ID Must Survive Model, BOM, and Commissioning

Two hundred and sixty-three rows are recorded as verified against the commissioning index [MODELED]. The index's own writing rule is that every card, scene and ledger row is not executed. Those two facts sit on the same identifier. A single primary key runs down all 573 rows of the object register, and on each row that key is joined by a bill-of-materials anchor, a procurement package reference and a commissioning reference in three further columns of the same 35 [MODELED]. One equipment identifier therefore survives from a model element to a purchase line to a commissioning card without being rebuilt by hand. Recomputing the file confirms 573 rows against 573 unique keys, 36 distinct bill-of-materials anchors and 29 distinct procurement package references [MODELED].

The key is enforced, not conventional

A regular expression constrains every key to a building-or-outdoor segment followed by a container and one to three further segments. Empty values are refused outside a named whitelist. Padded whitespace is refused. The header order is checked position by position. The parent reference of every row resolves inside the file, with self-reference and path mismatch both trapped. The chain is held by machine assertion. That is what separates it from a naming convention that survives until the first hurried revision. The port instance key extends the same rule one level down, composing itself from the object key and a port token so that an endpoint cannot exist without naming its parent.

The commissioning index states the same identifier must also survive in the piping diagram, the native model, the supervisory point list, the commissioning script, the spare-parts ledger and the maintenance work order. This register carries the object primary key, a bill-of-materials anchor, a procurement package reference and a commissioning catalogue reference. It does not start a native model. It has no piping, supervisory, spare-parts, work-order, started or witnessed columns. Those six joins remain a rule without objects on this file.

Shape comes with the key. Twenty containers carry the 573 rows, from 190 in the electrical core down to two in an alternative outdoor primary yard, across 26 system codes and 97 distinct object classes, split 278 rows at the equipment level and 295 at the component level [MODELED]. A reader who has the key also has the location, the system and the class without consulting a second document. That is the property making the bill-of-materials and commissioning joins possible.

Verified Is a Catalogue Hit, Not a Witnessed Test

The commissioning column may draw only on a closed anchor set of 84 published by the commissioning index [MODELED]. Anchors outside it are rejected. An earlier generation of internal catalogue numbers was withdrawn instead of being mapped. A row claiming verification without an anchor is rejected as well. Against 573 rows, 263 are recorded as verified against that index, 280 as unverified and 30 as not applicable [MODELED]. Rather less than half the register currently reaches its commissioning card.

The assertion list includes a specific trap for the failure that matters most here: a row citing a study by the engineer of record as if it were commissioning evidence. Two key paths are additionally forced to specific integrated-test anchors, so the feeder cases cannot be left to a generic reference. A verified row means the reference resolves inside that closed set. It does not mean anything was witnessed. The index forbids claiming otherwise.

The Key Proves Traceability, Not Purchase or Witness

The register's own scope table states that the chain proves traceability and nothing further. No row has released a procurement quantity: the released count is zero, the sum of released quantities is zero, and the commercial gate holds 378 rows as not applicable and 195 as not released [MODELED]. The maturity column is dominated by assumption, 294 rows of 573, against 38 parametrically derived rows and 2 recorded as fact [MODELED]. An identifier reaching all three documents still points at an assumption-grade field in more than half the cases.

Six machine assertions guard the boundary between the model-state vocabulary and the commercial gate, each blocking one specific misreading: a held row carrying a procurement quantity; a non-active row carrying a procurement quantity; a quantity present while the gate is not released; a non-active row marked released; a type placeholder row marked released; a released row with no procurement package number. Those are proven by injection tests run in two shell environments and refused in both.

Limits and open items

Confirmed: the object primary key is the only cross-file identifier on this register; a verified commissioning reference means the catalogue anchor resolves, not that a test was witnessed; no row has released a procurement quantity. [FACT]

Modelled and unfrozen: 573 rows, 35 columns, 573 unique keys; 36 bill-of-materials anchors and 29 package references; 263 verified, 280 unverified and 30 not applicable against 84 recognised anchors; 294 assumption rows, 38 derived and 2 graded as fact; 378 not-applicable and 195 not-released commercial-gate rows; 20 containers, 26 system codes and 97 object classes. [MODELED]

Open: the 280 unverified rows; reverse references from the bill of materials, the procurement file and the commissioning index back to this key; the piping, point-list, spare-parts and work-order joins the index requires. If the commissioning index is reissued with a changed anchor set, the 263 verified rows revert to unverified until the register is re-run. Only a joint reissue by the object model owner and the commissioning author closes that. No such reissue is scheduled. Nothing here has been sealed. Nothing has been purchased. [HOLD]

Which of the Six Named Systems Can Resolve the Key?

The useful test is not whether 573 unique identifiers exist. It is which of the six systems the commissioning index named can currently resolve one of them without a person in the middle.

© 2026 K&K Data Service Inc. All rights reserved. Reproduction or republication is permitted only with clear attribution to K&K Data Service Inc. and a working hyperlink to the canonical URL of this article. Excerpts must preserve the technical context, maturity labels, assumptions, and limitations. No excerpt may imply project approval, field validation, certification, or endorsement that the original article does not state.

Source: K&K Data Service Inc., “One Equipment ID Must Survive Model, BOM, and Commissioning,” https://www.kkdatasvc.com/lab/bim-and-navisworks/one-equipment-id-across-model-bom-and-cx/.