# Colocation demarcation and ID crosswalk

> Preserve provider, cross-connect, and tenant IDs with A/Z demarcations, LOA references, and onward patching in the editable crosswalk.

Canonical page: https://datacenterlabeling.com/templates/colocation-demarcation

Download: https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx

Workbook tab: 20 Colo demarcation. The workbook includes all 30 registers.

Rackstamp provides editorial field guidance. IDs, cases, and worksheet entries are fictional examples unless identified otherwise. Distinguish local conventions from adopted standards. Source notes describe the evidence scope; a linked overview is not the full standard or a project approval.

## Before you start

1. Define the reviewed service scope, source organizations, full endpoint locations, and the boundary between provider demarcation and tenant onward connection.
2. Collect current provider and cross-connect records, applicable authorization references, tenant connection records, and their issue or revision information.
3. Identify which source defines A/Z orientation and which owners can resolve service identifiers, authorization details, and tenant patch records.
4. Preserve exact source strings, including punctuation and leading zeros, and distinguish current, historical, planned, and unresolved relationships.

## Complete the register

1. Enter Provider circuit, Cross-connect ID, and Tenant alias in separate fields without overwriting one party's reference with another party's nickname.
2. Record A demarcation and Z demarcation in the cited order orientation with complete site, room, panel or cabinet, and port context.
3. Cite the applicable LOA or accepted authorization reference by identifier and version and compare its endpoint detail with the service order.
4. Enter Tenant onward patch as a separate exact endpoint pair with its cable or relationship reference and responsible owner.
5. Describe discrepancies as exact competing claims, including source versions, rather than using a general names differ finding.
6. Record the accepted outcome from the responsible parties' process and retain superseded endpoint or identifier relationships historically.
7. Link evidence for the provider crosswalk and onward patch separately and publish only the supported review state for each boundary.

## Walk through the example

For CAR-G20-301, XC-G20-301, and WAN-G20-301 in DC01 / H1, retain each source ID in its own field. Record PNL-G20-301 / P06 from the observed demarcation and current provider record, but preserve P04 from LOA-G20-301 revision 1 as a conflicting authorization endpoint. Keep the row pending and assign the service-record owner; the tenant plan's agreement with P06 does not resolve that authority question. When the accepted process supplies revision 2 and DEC-G20-301, link them as the current basis and retain revision 1 historically. Record CBL-G20-301 from the demarcation to RTR-G20-301 / WAN1 as the separate onward patch. Check the provider relationship and tenant pair through their own evidence, recording any remaining pending state separately. Enter the actual review date without treating the worksheet as an order, an authorization, or proof of activated service. Retain the source order's A/Z orientation so a tenant viewpoint change cannot silently reverse the accepted endpoint relationship.

## Handle common exceptions

### Service IDs match but authorization and provider ports differ.

Preserve the exact endpoint claims and obtain the applicable current accepted reference through the responsible provider process before closing that relationship.

### A tenant alias is retained while the carrier circuit changes.

Record the old and new associations with their effective events and migration reference, preserving the alias without overwriting history.

### The provider demarcation is reviewed but the tenant patch is unconfirmed.

Close only the supported crosswalk fields and keep the onward endpoint pair pending with its own owner and evidence requirement.

## Review and close

1. Confirm each organization's exact reference is preserved and linked to the accepted current service scope.
2. Check A/Z orientation, full demarcation details, and the applicable authorization version against their actual source records.
3. Verify the onward tenant pair through its own evidence and leave it pending if only the provider relationship has been reviewed.
4. Retain historical references and effective events for migrations, renamed aliases, or revised endpoints.
5. Record the actual crosswalk-review date and avoid presenting identifier agreement as service ordering, activation, or performance acceptance.

## Fields and fictional filled example

| Field | What to record | Fictional example |
| --- | --- | --- |
| Provider circuit | Exact carrier or service-provider reference. | CIR-0048 |
| Cross-connect ID | Colocation provider's connection reference. | XC-0917 |
| Tenant alias | Tenant's internal service reference. | WAN-02 |
| A demarcation | A endpoint as defined by the source order. | DC01 / DEM-01 / 07 |
| Z demarcation | Z endpoint using the same order orientation. | DC01 / DEM-08 / 12 |
| LOA reference | Applicable authorization document identifier/version. | Fictional LOA-008 rev 2 |
| Tenant onward patch | Separate tenant-side endpoint relationship. | DEM-01/07 to EDGE-01/WAN1 |
| Status | Crosswalk review state or specific discrepancy. | Pending endpoint review |
| Evidence | Provider order and tenant-record references. | Fictional order ORD-0917; EX-20 |
| Owner | Service-record owner coordinating organizations. | Example tenant connectivity team |
| Verification date | Actual date the record relationship is checked. | Not verified (fictional) |

## Sources

- [Equinix: Cross-connect demarcations](https://docs.equinix.com/cross-connect/installation/xc-demarcations/): Provider-specific demarcation and customer onward-patching context; consult the actual service arrangement.
- [Equinix: Ordering a cross connect with an LOA](https://docs.equinix.com/cross-connect/ordering/xc-order-cc-with-loa/): Provider-specific authorization and ordering context. A worksheet neither authorizes nor orders service.