PDU outlet-to-PSU connection schedule

Use it with your own records.

1. Download the workbook and open 13 PDU to PSU.
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 13 to complete the checks and record unresolved items.

Before you start

1. Define the included cord population and full rack scope, distinguishing a device-level review from a full PDU or rack survey.
2. Collect the exact installed PDU outlet reference and the supplied device inlet reference, together with the current asset and connection schedules.
3. Confirm how the local policy distinguishes physical cord identity, connection-position identity, device asset ID, and hostname aliases.
4. Prepare a permitted evidence method for both endpoints and identify any endpoint that cannot be confirmed within the observation scope.

Complete the register

1. Enter one Cord ID per physical relationship and retain conflicting observed IDs as findings rather than silently selecting one.
2. Record Rack and PDU ID, then copy the exact Outlet ID with any bank or module context required by the installed reference.
3. Enter the Device asset ID and exact PSU/inlet ID separately; retain a hostname as supporting alias information where relevant.
4. Link evidence for each endpoint and state which relationship is documented, observed, or still unconfirmed.
5. Compare the row with the controlled schedule and flag duplicate cord assignments, duplicated exact outlets, or obsolete asset aliases for owner review.
6. Record the accepted pair and the decision reference, then generate both end faces from that same controlled relationship.

Walk through the example

For CRD-G13-301 in DC01 / H1 / R301, enter PDU-G13-301 and BANK B / O04 as the documented local endpoint. Preserve gpu-old-g13 / PSU2 from the original schedule in the discrepancy evidence. Link the current asset record showing that gpu-new-g13 refers to AST-G13-301, and avoid treating the alias change as proof of an inlet change. When the accepted observation supports PSU1, record DEC-G13-301 as the basis for the corrected asset-and-inlet pair. Draft reciprocal faces from that row, keeping CRD-G13-301 unchanged. After the authorized identification correction, compare each installed face with the accepted endpoint and attach both evidence references. Retain the old hostname and PSU2 claim in the history, remove any conflicting active assignment through the records process, and enter the actual review date. The result is a reviewed cord identity relationship with the scope and remaining limitations stated. Keep the bank designation attached to O04 throughout the comparison so the outlet cannot be mistaken for another bank.

Handle common exceptions

Only the PDU-side endpoint is accessible.

Complete that endpoint with its evidence but leave the inlet and overall relationship unconfirmed, naming the missing detail and responsible owner.

A hostname points to a replacement asset.

Use the replacement record to establish the current durable asset identity and review the affected cord relationship rather than inheriting the old asset automatically.

Two rows claim the same exact PDU outlet.

Preserve both rows and compare their physical and source evidence; record whether the resolution corrects a duplicate, alias, or endpoint mapping.

Review and close

1. Check that both end faces retain the same cord identity and correctly express the opposite endpoint or the approved fixed-end convention.
2. Confirm the accepted outlet notation against the correct PDU and the inlet notation against the correct supplied asset.
3. Resolve or explicitly retain competing assignments elsewhere in the schedule after a row is corrected.
4. Attach final evidence that identifies the installed cord and endpoints, not only the printed face text.
5. Reconcile the included relationship count, record the actual review date, and leave every inaccessible or unconfirmed endpoint visibly pending.

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

• NetBox: Power outlets ↗

  Software record model for outlet identity and relationships; not a prescribed physical label format.

  Read scope and linked guides