Fiber assembly and mapping reference record

Assembly identity#

Site/room scope: ______ | Parent trunk/assembly key: ______ | Record revision: ______

Manufacturer: ______ | Part number: ______ | Assembly revision: ______

Module or cassette reference: ______ | Installed viewpoint: ______

Collect the actual assembly documentation rather than choosing a generic map because the connector looks familiar. Record the manufacturer's polarity designation and connector configuration as documented values; use an explicit unknown state when evidence is missing. The field record does not design or verify the optical path by itself.

Reference and endpoint table#

Expected leg/fiber count and its source: ______. Observed references: ______. Unaccounted references: ______.

Keep cable identity, leg identity, port identity, and the technical mapping separate. A color or alphabetic leg mark may help read the assembly's documentation, but it does not independently establish which installed endpoint the leg reaches.

Separate acceptance questions#

Identity mapping evidence: ______ | Reviewed by: ______

Polarity or optical-path evidence required by the project: ______ | Owner: ______

Test-result reference and exact linked object key: ______

An identity review may conclude that a labeled leg corresponds to the documented endpoint while a required technical review remains pending. Preserve both states. Avoid changing a pending result to accepted simply because the label now reads clearly.

Fictional exception#

In scope DC01 / H1, trunk FIB-040 has documented leg L03 at the observed cassette port. Its source document establishes the ID mapping, but the applicable project polarity-review reference has not been supplied. The mapping row records the evidence already available and a separate owner for the pending technical acceptance. It does not default the missing field to Method A, B, or C.

Closure#

• Assembly part and revision match the actual equipment.
• Parent, leg, fiber, and port references remain distinct.
• Expected and observed counts reconcile or have explicit exceptions.
• Each accepted mapping has a source reference.
• Identity, technical review, and test evidence have separate statuses.
• Changed assembly revisions trigger review of the affected records and labels.

Use it with these guides