A/B feed identification worksheet

Use it with your own records.

1. Download the workbook and open 11 A-B feeds.
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 11 to complete the checks and record unresolved items.

Before you start

1. List every included PDU under its full site, hall, and rack address. Distinguish asset identity from an approach note such as rear-left and record the viewpoint used for that note.
2. Collect the power drawing and legend by identifier and revision, and identify the owner who can resolve a disagreement between them and the visible wording.
3. Prepare observation references that connect each close-up of feed text to the correct PDU. Keep unavailable or unreadable PDU identities visibly unresolved.
4. Define the survey boundary and any excluded unit before recording results, so a partial review cannot be mistaken for a whole-rack conclusion.

Complete the register

1. Enter one row for each PDU and transcribe its existing ID without replacing it with A, B, left, or right.
2. Copy observed feed text literally, including missing words or damaged characters, and link the observation that shows which PDU carries it.
3. Enter the documented feed designation as a separate value. Cite the legend rule if short and long forms are treated as equivalent locally.
4. Copy the upstream source exactly as the approved drawing states it, preserving the parent distribution reference and circuit where provided.
5. Classify the row as matched, missing text, unreadable text, or a specified conflict; identify the evidence still needed for any unresolved relationship.
6. Record the responsible owner, accepted decision, and proposed face text. Keep printing readiness and installed verification as distinct stages of the same case.

Walk through the example

For the fictional PDU-G11-302 case in DC01 / H1 / R301, first enter the existing PDU identity and the observed FEED A wording. In the documented designation field, enter FEED B from PWR-G11-301 revision 4; do not change the observation to make the row look consistent. Link the context and close-up evidence and mark the row as a conflicting designation. The power-record owner then records DEC-G11-301, which supports the drawing relationship and identifies the copied label schedule. Add the accepted replacement text while retaining FEED A in the original observation. After the approved labeling work, link EV-G11-303 to the installed PDU-G11-302 face and compare it with the corrected schedule. Close this row only when that comparison is recorded. Leave the neighboring PDU-G11-301 as its own reviewed row and describe the result as an identity correction, with no implication about electrical independence or operating permission.

Handle common exceptions

The PDU ID itself is unreadable.

Create a bounded observation reference and obtain evidence linking the physical unit to its inventory identity before assigning a feed name.

The drawing and inventory cite different upstream references.

Preserve both revisions and assign the relationship to the power-record owner; hold the affected production text pending a documented decision.

A phased batch is printed but not installed.

Keep the row at the prepared stage, track its wave, and require evidence of the installed face before entering the final verification date.

Review and close

1. Confirm that every final face identifies the intended PDU and uses the designation accepted for that row.
2. Check that inventory, label schedule, drawing reference, and local legend now describe the same relationship.
3. Retain the original observation, replacement decision, and final installed evidence rather than replacing the before-state with the final text.
4. Account for obsolete labels associated with the change and identify any remaining unit whose path or wording is unresolved.
5. Enter the actual verification date and name the reviewed population; do not turn an identity match into a claim about power-path independence.

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

• Raritan: Advanced engineering ↗

  Manufacturer A/B differentiation example; no universal color code or proof of feed independence.

  Read scope and linked guides
• OSHA: 29 CFR 1910.333 ↗

  Electrical work-practice boundary only. The joined chain and fictional design discrepancy are original recordkeeping examples, with no operation or independence test.

  Read scope and linked guides