Fiber trunks and breakout legs are ambiguous

Examples are fictional local conventions. Unless another location is shown, the scope is DC01 / H1. Keep that scope with shortened identifiers.

How should a missing or unused fiber reference be recorded?#

A blank cell cannot tell a reviewer whether a fiber is unused, unverified, missing, or outside the work package. Retain the expected assembly position and give its state an explicit meaning. Apply the same rule to legs, cassette positions, or individual fibers at the level the project's record model uses.

Keep three questions distinct: Is the required population accounted for? Do the identities and destinations agree? Has the applicable technical evidence been accepted? A row can answer the first two while a polarity review remains pending. Use wording such as “mapping confirmed; technical review pending” instead of a broad pass.

The label scheme must follow the actual assembly documentation and controlling revision. Corning's EDGE procedure provides product-specific hierarchy context; it does not make this editorial status table a universal polarity method. Corning EDGE procedure.

Before closing the register, account for every expected position within the agreed scope. Preserve legitimate blanks as defined states and investigate omissions; do not delete unresolved entries to make the table appear complete.

When to use#

Use this guide for ambiguous trunk tails, fibers, or module destinations. Work from assembly records and permitted observations; this is documentation, not an optical test or connection procedure.

Corning's EDGE procedure S46998-A0007-P146, Issue 1, illustrates chassis, tray, module, and port identification and documentation of individual fiber strands in its recordkeeping sections. Its hierarchy is equipment-specific. Corning EDGE procedure

What to gather#

Collect the trunk identifier, exact assembly part and revision, manufacturer mapping document, chassis and module records, endpoint schedule, and any separate polarity-test evidence.

Method#

1. Match the trunk to its assembly record before naming its branches. Record the part or assembly revision so a similar connector arrangement cannot substitute for the intended map.
2. List the manufacturer's leg or fiber references exactly. Keep the distinction between a physical tail, an individual fiber, and a port; do not collapse them into one ambiguous number.
3. Record each termination's hierarchy, including the chassis, tray, and module where relevant. Use one row per mapped leg or fiber reference.
4. Compare the mapped rows with the controlled connection schedule. Record missing, repeated, spare, and unused references explicitly instead of assuming every visible position has the next number.
5. Review every populated and intentionally unused reference with a second reader. Retain unresolved map entries separately, and link polarity evidence without claiming that labels establish polarity.

Determine what is actually ambiguous#

Start by naming the object whose identity is uncertain: the complete trunk, a physical breakout leg, an individual fiber reference, a cassette, or a port. These objects can be related without sharing the same identifier. A report that says “fiber 1 wrong” is not specific enough to decide whether the problem is a missing parent identity, an incorrect assembly map, or an incomplete destination reference.

If the parent trunk is unknown, resolve that identity before numbering its branches. If the trunk is known but the leg reference is unreadable, preserve the observed condition and obtain the appropriate assembly evidence. If the leg reference is clear but its destination is uncertain, retain the leg identity and investigate the endpoint relationship through the approved process.

If a schedule repeats the same fiber number, compare the complete hierarchy. F01 in two different trunks or cassettes may describe two distinct references. The apparent duplicate may be missing parent context rather than duplicated physical identity. Conversely, two rows with the same complete trunk and leg key need a documented explanation.

Keep documentation uncertainty separate from optical test results. A completed mapping review establishes the reviewed identity relationships. It does not by itself establish polarity, continuity, insertion loss, or service readiness. Link the applicable separate evidence without inventing a technical result from the appearance of the labels.

Establish the parent assembly and controlling revision#

Collect the exact assembly identity, part reference, and revision information available for the installed object. Link the manufacturer or approved assembly mapping document that applies to that reference. A visually similar connector arrangement or another cable from the same project is not sufficient reason to reuse its map.

Record which document controls each relationship. An assembly document may describe leg or fiber references within the product, while the released connection schedule describes where those references are assigned in the installation. Preserve both when they answer different questions. A schedule cannot silently redefine an assembly marking just because a project uses another naming style.

If the assembly reference is unavailable or conflicting, keep the affected mappings held for the responsible owner. Record the observed markings and the missing document rather than creating a plausible sequence from physical order. The next authorized investigation should know whether it needs product identification, a revision decision, or endpoint evidence.

Check changes as part of the revision review. A replacement assembly, cassette relocation, or schedule update may invalidate a previous mapping comparison. Record the event and identify which rows need review. Do not discard the old reference before it has been linked to the superseding arrangement.

Keep trunk, leg, fiber, and port terms distinct#

Write a short glossary for the actual work package using the terms in its controlling documents. A leg is a physical branch when the assembly uses that concept. An individual fiber reference may identify a constituent within a larger connection. A port or adapter reference identifies a termination position. Avoid using the same bare number as shorthand for all three.

Use a complete row key that starts with the parent identity and adds the necessary child reference. Where a manufacturer's reference contains a letter or punctuation, preserve it exactly. Do not replace it with a local sequence that loses the ability to compare the row with the assembly documentation.

Record local aliases separately if the site needs them for work-order readability. The crosswalk should show the manufacturer's reference, the site's alias, and the destination relationship. The alias must not become the only surviving link to the actual assembly map.

When a physical leg contains more than one individually managed reference under the project model, represent the relationships at the level the records require. Do not assume that one visible connector always corresponds to one worksheet row. The controlling documentation and the work package determine the required granularity.

Capture the hierarchy on both sides#

Include the enclosure, chassis, shelf, tray, slot, cassette, module, adapter, and port levels that actually distinguish the installed endpoint. Not every installation uses every level, but omitting a necessary level can make a correct final fiber number ambiguous. Use the hardware's actual hierarchy rather than forcing it into a generic example.

Record the current location of a separately identified cassette or module without erasing that component's physical identity where it is tracked. A cassette moving from one slot to another changes a location relationship. Whether any associated assembly identity changes is a policy and equipment-model question for the responsible owner.

Keep complete site and hall scope with the review record. If the physical label uses a shortened reference, identify the controlled context through which it resolves to the full endpoint. A technician reviewing the map outside the immediate enclosure should still be able to distinguish both sides.

Check the relationship between the local parent hierarchy and the remote parent hierarchy. Matching F01 at each end is not enough if two cassettes each contain F01. The comparison must establish which trunk and which cassette or module each reference belongs to.

Account for every required reference#

Start from the complete set of references defined for the actual assembly and work package. Create an outcome for each required leg or fiber reference: mapped to a confirmed destination, intentionally unused, reserved under the plan, missing from the evidence, or unresolved. Use the site's supported status terms and explain any ambiguity.

Do not infer an unused state from an empty spreadsheet row. An empty row may mean the preparer forgot the reference. Similarly, a visible unconnected position is not enough to establish a future reservation. Record the released plan or owner decision that defines the intended state.

Compare the register with the assembly map and connection schedule in both directions. Every expected reference should appear in the register, and every register row should have an applicable parent and source. This catches both omissions and extra rows copied from another assembly.

Record repeated references with their complete keys before deciding they are errors. If the complete key repeats without a supported reason, hold the conflicting rows and ask the map owner to resolve them. Do not delete one to make the count agree.

Build a readable diagram from the verified register#

Use the diagram to explain the relationships already supported by the records. Show the parent trunk, each relevant branch reference, and the complete or clearly scoped destination. Keep labels near the lines they describe and distinguish assembly references from physical endpoint identities.

A diagram should state its scope and controlling map revision. If it simplifies the assembly by showing only selected legs, say which subset it represents and keep the complete register available. The two-leg examples in this library illustrate how to communicate relationships; they do not describe a universal breakout configuration.

When fiber numbers repeat, use separate branches or grouped hierarchy labels rather than visually merging them into one line. A viewer should be able to trace a selected row from the parent through the child reference to its intended destination without guessing which crossing line it follows.

Review the diagram against the register after each mapping change. A corrected spreadsheet and an unchanged reference diagram create competing instructions. Give the diagram an owner and revision so it remains connected to the same release as the label proofs.

Compare identity mapping with separate technical evidence#

The label register and any polarity or performance evidence should use compatible identifying references so the reviewer can establish what was tested or reviewed. Link the evidence to the relevant trunk, leg, fiber, or connection under the project model. Do not attach a test result only because its filename resembles the cable ID.

Record what the linked evidence actually covers. A result may apply to a specific assembly revision, path, or event. The responsible technical owner determines its applicability and acceptance under the project requirements. This guide's documentation reviewer should preserve that scope rather than expand it.

If identity mapping is resolved but the required technical review is pending, state both facts. “Map agrees with released schedule; separate polarity review pending” is more informative than a single broad “passed.” If the test record cannot be associated with the mapped object, retain that as a records discrepancy for the relevant owner.

Avoid deriving a mapping from color alone or presenting a diagram as a polarity test. Use the exact product documentation and approved verification process for technical conclusions. The worksheet's role is to retain the relationship and its evidence clearly enough for those conclusions to be attributed to the right object.

Scenario: a reused diagram points a leg to the wrong switch#

In a separate fictional case, trunk TRK-G08-301 in DC01 / H1 is governed by assembly record ASM-G08-301 revision 2. The local hierarchy is DC01/H1/R301/PNL-G08-301/SlotA/Adapter01. A copied drawing sends leg L2 to DC01/H1/R302/SW-G08-301/P02, but the released connection schedule assigns that leg to DC01/H1/R303/SW-G08-302/P12.

The reviewer preserves both claims under MAP-G08-301 and checks the applicable assembly reference and approved endpoint evidence. The investigation establishes that the drawing was copied from another work package. The manufacturer's leg reference remains L2; the installation destination is the field requiring correction.

The mapping owner updates the L2 row and the reference diagram, retaining the rejected destination in the discrepancy history. The label preparer generates the corrected leg face from the released row. Other required assembly references are compared independently so the successful L2 correction does not stand in for a whole-assembly review.

Closure includes the assembly revision, complete local and remote hierarchy, corrected diagram and proof references, and the independent mapping check. Any required polarity or performance evidence remains separately identified by its own owner and scope. The map correction is not described as proof of optical operation.

Scenario: two cassette references look identical in an export#

In another fictional case, TRK-G08-302 and TRK-G08-303 are separate parent assemblies in DC01 / H1. Their local cassettes each contain reference F01, and an export reduces both rows to “F01 to F01.” The receiving team cannot tell which remote cassette belongs to either row.

The reviewer restores the parent trunk and cassette hierarchy from the controlled records. One row belongs to DC01/H1/R304/PNL-G08-302/SlotA/F01; the other belongs to DC01/H1/R304/PNL-G08-302/SlotB/F01. Their remote references are retained with equally complete hierarchy. The diagnosis is a lossy export, not a reason to renumber factory fiber references.

The export owner corrects the field selection, and the mapping owner checks the restored rows against the actual assembly records. The diagram and label proofs preserve the distinguishing parent context. A second reader is asked to select each F01 relationship independently from the released export. Closure records the repaired output and the evidence supporting both rows.

Handle brownfield uncertainty and new-build preparation#

In an established installation, preserve observed markings and the last known map before proposing corrections. Identify whether the discrepancy arose from a replaced assembly, a moved cassette, an undocumented endpoint change, or incomplete records. Keep an unsupported candidate mapping visible as a candidate rather than printing it as fact.

Where access is limited, record exactly which parent and child references can be observed under the approved process. Assign missing evidence to the owner who can obtain it. Do not disturb adjacent operational fiber merely to complete the documentation review described here.

For a new build, align the assembly map, connection schedule, diagram, and print source before bulk preparation. Include unused or reserved references explicitly so the receiving team can distinguish intended omissions from missing work. Account for changes between staging and installed review.

When several assembly variants share a project, keep their part and revision references attached to their own maps. A batch-level statement that “all trunks are the same” should not replace the specific evidence needed to identify each installed assembly.

Close a complete and interpretable mapping record#

The final reviewer should be able to start with a physical parent or child reference and find its complete row, governing assembly map, destination evidence, and current disposition. They should also be able to start with an expected assembly reference and see whether it is mapped, intentionally unused, reserved, or unresolved.

Check that the diagram, print proofs, and editable register represent the same release. Preserve rejected mappings and superseded revisions as history while keeping the active view unambiguous. Record who owns later cassette, endpoint, or assembly changes.

Separate documentation closure from any technical acceptance that belongs to another process. Keep pending evidence visible with its owner. A complete-looking map becomes useful when its scope, omissions, and unresolved relationships are explicit enough for the next team to act on them correctly.

Worked example#

Fictional assembly DEMO-ASM-010 rev 1 defines these two leg references.

TRUNK F-010
 +-- LEG L1: DC01/H1/R014/CH01/T02/M-A/P01 -> DC01/H1/R021/PP02/19
 +-- LEG L2: DC01/H1/R014/CH01/T02/M-A/P02 -> DC01/H1/R021/PP02/20
Assembly map: DEMO-ASM-010 rev 1
Mapping review: example only
Polarity: not assessed by this identification example

This fictional map supplies the association; connector appearance, fiber color, and leg order do not establish it.

Common mistakes#

• Copying the map for a similar assembly revision.
• Using one number interchangeably for a tail, fiber, and port.
• Treating a complete label schedule as proof of optical polarity.

Verification#

• The assembly identifier and revision match.
• Leg and fiber terms have explicit meanings.
• Every required reference has one mapped row.
• Unused or unresolved references remain visible.
• Mapping review and polarity evidence are recorded separately.

Worksheet: Fiber trunk and breakout mapping sheet#

Fields define one row; sample values are fictional. Leave working-sheet dates blank until their recorded event occurs. Sample status: Example only.

Frequently asked questions#

Can the jacket or connector color identify the correct leg?#

Record any relevant manufacturer markings, but derive the association from the exact assembly documentation and verified endpoint references.

How should spare fibers appear?#

Retain their actual reference and mark the documented condition, such as unused or reserved. Do not delete them merely to make the worksheet shorter.

Is there a universal fiber numbering diagram we can copy?#

Use the exact assembly and installation documents governing the hardware. A generic diagram can help explain the structure of a record, but it cannot establish the installed leg, fiber, or cassette mapping. Replace every illustrative relationship with supported project references.

Should unused legs disappear from the label register?#

Keep required assembly references visible with their documented disposition. An explicit unused or reserved state distinguishes a planned condition from an omitted row. Use the site's actual status definitions and link the relevant plan or owner decision.

Can we close identity mapping while a polarity record is pending?#

Record the completed mapping review and the pending technical evidence separately. The project owner decides the overall acceptance state. Do not convert a successful identity comparison into a claim that polarity or performance has been verified.

More worked label examples

Two additional ways to apply this guide. Keep the exact identifiers and relationships consistent with your own approved records.

SCOPE: DC01 / H1; assembly map ASM-G08-101 r2
TRUNK FACE: [TRK-G08-101 | ASM-G08-101 r2]
LOCAL: PNL-G08-101 / SLOT A / ADAPTER 01
                         |
                     TRK-G08-101
                         +-- LEG L1 --> SW-G08-101 / P01
                         +-- LEG L2 --> SW-G08-101 / P02

LEG LABEL FACES
+---------------------------+  +---------------------------+
| TRK-G08-101 / L1          |  | TRK-G08-101 / L2          |
| TO SW-G08-101 / P01       |  | TO SW-G08-101 / P02       |
+---------------------------+  +---------------------------+
Map check: L1 <-> P01; L2 <-> P02
Polarity evidence: separate test/reference POL-G08-101

SCOPE: DC01 / H1; hierarchy check MAP-G08-201
TRUNK TRK-G08-201 -> PNL-G08-201 / SLOT A
TRUNK TRK-G08-202 -> PNL-G08-201 / SLOT B

LOCAL LABEL FACES
[TRK-G08-201 / SLOT A / F01]
[TRK-G08-202 / SLOT B / F01]

MAPPING PAIRS
TRK-G08-201 / F01 <-> PNL-G08-202 / SLOT C / F01
TRK-G08-202 / F01 <-> PNL-G08-202 / SLOT D / F01

Before schedule: F01 -> F01           ambiguous
After schedule: full hierarchy above distinct
Assembly refs: ASM-G08-201 r1; ASM-G08-202 r1
Identity evidence: EV-G08-201; polarity: separate review

Sources and applicability

• 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

Planning guides and companion documents

• Create a cable-color legend people can use
• Fiber assembly and mapping reference record
• Panel and switch port relationship schedule
• Cable-color meaning and transition planning register

Related guides