# Panel and switch port relationship schedule

## Scope and ownership

Schedule ID: ______ | Revision: ______ | Site/room/rack: ______

Panel or device: ______ | Module/slot scope: ______ | Record owner: ______

Define whether the schedule represents a panel face, a switch, or a connection path. A physical port's factory marking and the connected interface's name are separate references. Document the viewpoint and numbering order before entering rows.

## Connection schedule

| Row key | Local panel/device | Module/slot | Physical port | Cable key | Remote panel/device | Remote module/port | State | Evidence |
|---|---|---|---|---|---|---|---|---|
| ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ | ______ |

Keep optional service descriptions, VLANs, or customer aliases in separate fields keyed to the row. They can change without changing the physical port's identity. Record empty, reserved, unknown, and excluded states explicitly according to the site's vocabulary. A blank cell is not a verified unused port.

## Fictional mapping

In DC01 / H1, row MAP-001 describes R014 / PP01 / 07 connected by CAB-0042 to R021 / PP02 / 19. If a separate switch connection is also in scope, give that relationship its own row and record the switch's exact interface reference. Do not skip the intermediate panel because the operator ultimately wants to locate the switch.

## Data and print release

1. Reconcile row keys and cable keys with the approved source records.
2. Check duplicate endpoint assignments and explain legitimate exceptions through the actual topology.
3. Keep leading zeros and identifier punctuation intact during import.
4. Compare first, last, and reserved positions with the physical schedule.
5. Link the label output to its template and accepted physical proof.
6. Record changes and unresolved relationships before release.

## Acceptance

- [ ] Every printed position resolves to the correct schedule row.
- [ ] Both endpoints include enough context to identify the termination.
- [ ] Unused and unresolved states have not been conflated.
- [ ] Operational descriptions remain separate from physical identity.
- [ ] Evidence, reviewer, and current revision are retained.

Use the port-layout proof for dimensions and the endpoint worksheet for field verification. This schedule defines relationships; it is not a universal printer template or proof of connection performance.