# Multi-site prefix and alias register

## Define the namespace

Register ID: ______ | Owner: ______ | Revision: ______

Scope of uniqueness: ______. Systems that consume this register: ______.

Decide whether a prefix identifies a physical site, a building, or an organizational unit. A geographic nickname and a commercial facility name may change independently of the physical location. Write which property the prefix represents and how changes will be handled.

## Prefix register

| Prefix | Stable site record key | Display name | Building/room scope | Local owner | Status | Effective from | Retirement reference |
|---|---|---|---|---|---|---|---|
| ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ |

Suggested status vocabulary: reserved, active, transition, retired. These are local administrative values, not equipment operating states. Choose one vocabulary and document it before import.

Fictional example: DC01 identifies site record SITE-001. Its display name changes from North Hall Campus to River Campus. The register retains SITE-001 and DC01 while updating the display name and its change reference. No physical object is renumbered solely because a business name changed.

## Alias crosswalk

| Old value | System or document using it | Current value | Object scope | Reason | Approved by | Change reference |
|---|---|---|---|---|---|---|
| ______ | ______ | ______ | ______ | ______ | ______ | ______ |

Do not enter a many-to-one mapping without explaining why the old values refer to the same object. Where one old prefix was reused across sites, combine it with its old system and location context before mapping. An ambiguous alias remains unresolved until evidence distinguishes its objects.

## Issue a new prefix

1. Search active, reserved, and retired values, including case and whitespace normalization used by receiving systems.
2. Confirm that the proposed prefix represents the agreed type of location.
3. Reserve the value and record its requesting team before generating dependent identifiers.
4. Test representative full-length identifiers in each downstream export and label template.
5. Obtain the issuance approval and publish the effective revision.

## Close a change

- [ ] Old and new values remain traceable in historical work records.
- [ ] Active exports resolve to one stable location key.
- [ ] Affected shortened labels still carry enough visible scope.
- [ ] Downstream teams received the effective revision.
- [ ] Retirement or reuse decisions were recorded explicitly.

Store the completed register with the naming policy. Keep contact details and facility access information in the access-controlled project system rather than placing them on public-facing labels.