Naming convention worksheet

Use it with your own records.

1. Download the workbook and open 01 Naming policy.
2. Enter your site and room scope and the project or policy reference.
3. Use the blank amber table for actual records. The fictional example below it is a reference.
4. Insert table rows when needed. Keep identifiers as text, including leading zeros.
5. Follow guide 01 to complete the checks and record unresolved items.

Before you start

1. Identify the object class for this row and bring examples from an actual upcoming work package, including one value that already causes confusion.
2. Collect the approved location dictionary, existing allocation registers, and relevant print or record-field constraints. Mark an unavailable policy as missing rather than inventing its revision.
3. Name the person who can decide uniqueness scope and issuance rules, and choose a second reader who did not design the proposed syntax.

Complete the register

1. Enter one object type per rule row. Separate a cabinet's physical asset identity from the rack location address if the policy tracks both.
2. Describe the uniqueness boundary in words, then enter the full proposed pattern without substituting a short display label for the authoritative form.
3. Define each component in order and record permitted characters, separators, padding, and the handling of missing information.
4. Enter a complete fictional proof value while reviewing the draft; replace it with a clearly identified project example when the rule is ready for actual use.
5. Record the policy revision and allocation owner only when those decisions exist. Link the review pack that tests expansion, moves, and competing short identifiers.
6. Use the status field to distinguish draft review, unresolved decision, and approved rule. Enter verifier and verification date for the completed interpretation check.

Walk through the example

In the existing fictional row, Object type is Rack location, the scope is all DC01 halls, and the pattern is SITE-HALL-RACK. Read DC01-H1-R014 against the field meanings: site DC01, hall H1, rack location R014. AST-008421 is a separate asset identity and does not belong in this location pattern. The reviewer should test another hall to confirm why R014 alone is insufficient outside the local context. The permitted values then explain uppercase text and the illustrated rack range; they are fictional policy choices, not a standard's required syntax. NAM-01 rev 2 identifies the example decision being reviewed, while DEMO-NAM-REVIEW-01 points to its supporting interpretation exercise. For a real project, replace those example references with actual approved records. If the second reader cannot distinguish a movable cabinet from its location, leave the rule under review and resolve the field meanings before issuing production labels.

Handle common exceptions

A legacy identifier is still referenced by open work orders.

Retain it in an explicit crosswalk to the approved identity and record the transition owner; do not erase the only reference those work orders can resolve.

The full proposed value is truncated by a record field.

Hold approval of the affected format and document the actual constraint for the policy and system owners; do not silently remove a component.

Two teams have reserved the same sequence.

Record both reservations, stop competing issuance for those values, and obtain one allocation decision before printing.

Review and close

1. Have the second reader decode the example using only the recorded dictionary and identify the intended object type and scope.
2. Check the longest permitted value in the intended label and downstream record fields, preserving all significant characters.
3. Confirm how reservations, corrections, retirement, and any permitted reuse are documented by the issuance owner.
4. Retain the accepted dictionary and transition crosswalk with the policy revision; list any areas or object types that remain outside the approved scope.

Fields and filled example

Fictional values only. Scope: DC01 / H1 unless another location is shown. The downloadable register is blank for your actual observations.

Sources and scope

• TIA FOTC: TIA-606-D scope ↗

  Public scope overview; local patterns and review workflow are editorial examples, not normative syntax. The expanded triage, decision comparisons, scenarios, and closeout procedures are original editorial guidance.

  Read scope and linked guides