Fiber trunk and breakout mapping sheet

Use it with your own records.

1. Download the workbook and open 08 Fiber breakout.
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 08 to complete the checks and record unresolved items.

Before you start

1. Identify the complete parent assembly, exact part or revision reference, and the controlling assembly map.
2. Collect the released connection schedule and the actual hierarchy used by chassis, trays, slots, cassettes, modules, and ports.
3. Define whether each row represents a leg, individual fiber reference, or another object in the project's model.
4. Identify the mapping owner and the separate owner of any required polarity or performance evidence.

Complete the register

1. Enter Trunk ID and Assembly revision from the actual parent relationship, preserving observed markings exactly.
2. Record Local hierarchy with every level required to distinguish the termination.
3. Enter Leg or fiber reference with its object type and original notation; keep local aliases separate.
4. Enter the complete Remote endpoint or an explicit unresolved state supported by the evidence.
5. Describe Map result against the released assembly and connection records, including intentionally unused or reserved references.
6. Link separate Polarity evidence with its actual scope or pending status, then record the mapping owner, evidence, verifier, date, and supported review status.

Walk through the example

The original fictional row maps trunk F-010 under DEMO-ASM-010 revision 1. Its local hierarchy is DC01/H1/R014/CH01/T02/M-A/P01, its child reference is Leg L1, and its remote endpoint is DC01/H1/R021/PP02/19. The neighboring example row for L2 uses a different local port and remote port. Those associations come from the fictional assembly map, not from connector appearance or the order of the drawn branches. Start by replacing the example parent and revision with the exact installed assembly reference. Then retain every hierarchy level needed to distinguish the local and remote terminations. Map result records the documentation comparison, while Polarity evidence remains explicitly separate. In real work, record the applicable test reference or its pending state rather than copying 'not assessed' without review. The verifier should account for all required references, including intentionally unused ones, and confirm that the label proof and diagram match the released register.

Handle common exceptions

The assembly part or revision is unknown.

Preserve observed markings, hold affected mappings, and obtain the controlling reference through the assembly owner.

Two rows both say F01 without parent context.

Restore trunk and cassette hierarchy from controlled evidence; do not renumber or delete a row merely to remove the apparent duplicate.

The map agrees but a test record cannot be linked to the same assembly.

Record the identity review separately and assign the evidence-link discrepancy to the responsible technical owner.

Review and close

1. Reconcile the register against all required assembly references in both directions.
2. Check repeated fiber numbers using their parent trunk and cassette hierarchy.
3. Confirm that labels and diagrams reflect the same released mapping revision.
4. Preserve rejected candidates and unexplained references as visible exceptions.
5. Verify that technical evidence is attributed to the correct object without treating label agreement as a technical test.

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

• Corning: EDGE procedure ↗

  February 2022 equipment-specific hierarchy examples; label mapping does not establish polarity. The expanded triage, decision comparisons, scenarios, and closeout procedures are original editorial guidance.

  Read scope and linked guides