Fiber Testing Field Guide

Fiber OTDR and Power-Loss Acceptance Guide
use each test for the question it can answer.

Fiber acceptance starts with a documented link and loss budget. Use insertion-loss testing to establish end-to-end loss against that budget, use OTDR testing when the scope requires event location and trace evidence, verify polarity and identification, inspect and clean connectors, reconcile every strand and route, preserve bidirectional results where required, and deliver native files, readable reports, splice records, as-builts, exceptions, and signed acceptance.

1996
Founded
900+
Deployments
10,000+
Sites served
all 50 states
Coverage

SRS Networks is a nationwide IT infrastructure deployment partner headquartered in South San Francisco, California, serving multi-site enterprises across the 48 contiguous states, Alaska, and Hawaii since 1996. This page turns field-delivery requirements into a scope, comparison, and acceptance record a buyer can use.

Fiber acceptance evidence matrix

EvidenceWhat it establishesWhat it does not establish alone
Loss budgetExpected end-to-end allowance from the approved designActual installed performance
Insertion-loss testMeasured end-to-end loss and polarity under the defined methodPrecise location of every event
OTDR traceEvent location, distance, reflectance, and distributed-loss evidenceA direct substitute for insertion-loss acceptance
Connector inspectionEnd-face condition at the inspected interfacePerformance of the complete link
Splice scheduleFiber identity, tray or enclosure, and planned/actual splice mappingMeasured optical performance
As-built routeWhere the accepted cable, enclosures, and terminations are locatedCondition of each strand

Begin with the loss budget

Calculate the allowable link loss from the approved fiber type, wavelength, length, connectors, splices, passive devices, engineering margin, and application or owner requirement. A tester limit cannot repair a loss budget that was never defined.

Separate end-to-end loss from event location

An optical loss test set and an OTDR answer related but different questions. Use insertion-loss testing for direct end-to-end acceptance and OTDR traces for distance and event analysis when required; do not substitute one merely because only one instrument is available.

Preserve trace context

An OTDR file without wavelength, direction, launch and receive configuration, refractive index or group index setting, pulse and range settings, and link identification is difficult to audit. Keep the native trace and the readable export.

Field Guide

Build the acceptance record step by step

1. Define the fiber link and budget

Acceptance limits should come from the designed link, not from a generic number applied after installation.

Link inventory

Record endpoints, route, cable and fiber type, strand count, connector types, splices, splitters or other passive elements, intended applications, wavelengths, and any spare or dark strands included in acceptance.

Loss contributors

List the length-dependent fiber allowance, connector pairs, splices, passive devices, design margin, and any owner or application maximum. Identify whether values are design assumptions, component ratings, or measured results.

Test population

State whether every strand is tested, which wavelengths and directions are required, how polarity is verified, and which links require OTDR traces in addition to insertion-loss results.

Reference method

Document the test-cord reference method, connector interfaces, launch and receive arrangements, and applicable project or manufacturer procedure before production testing begins.

2. Prepare connectors and instruments

Contaminated interfaces and unstable references can dominate the measurement. Control them before interpreting results.

Inspect and clean

Use the project-approved inspect-clean-inspect process for accessible interfaces and record damaged connectors. Never assume a new test cord or factory-terminated connector is clean.

Test cords

Use cords and adapters appropriate to the fiber and connector under test. Identify reference-grade requirements, mandrels or mode-conditioning requirements when applicable, and maximum acceptable test-cord condition.

Instrument setup

Record equipment IDs, software, wavelength, reference state, units, fiber settings, and service or calibration status required by the project. Verify date and time before creating the final result set.

Pilot link

Review representative short, long, connector-rich, splice-rich, multimode, and single-mode links as applicable before running the full population. Confirm naming and exports while the setup can still be corrected.

3. Run and interpret insertion-loss testing

Direct end-to-end loss should be compared to the documented budget using the agreed method.

Result identity

Tie each result to the cable, strand, endpoints, wavelength, direction when required, and reference method. The strand schedule and tester file should use the same identifier.

Budget comparison

Compare measured loss to the approved budget and record the margin. Investigate unexpected gains, unstable values, large directional differences, or results that cluster near the limit according to the project's acceptance rule.

Polarity

Verify transmit-to-receive continuity and document array-connector or duplex polarity using the designed method. A low-loss result on the wrong pair is not an accepted circuit.

Correction

Preserve the original result, cleaning or repair action, and final retest. Recurring contamination, poor terminations, macrobends, or reference problems may justify auditing more than the failed strand.

4. Acquire and review OTDR traces

OTDR traces require competent setup and interpretation; automatic event tables are a starting point, not the entire review.

Launch and receive fiber

Use launch and receive arrangements appropriate to the project so the near and far end connections can be evaluated. Record their lengths and keep them distinct from the link under test.

Acquisition settings

Select range, pulse width, averaging, wavelength, thresholds, and fiber settings suitable for the link. Keep the native trace so another qualified reviewer can inspect the waveform and event table.

Direction

When the specification requires bidirectional testing or event-loss averaging, preserve both directions under paired identifiers. Dissimilar backscatter can produce different apparent event losses by direction.

Trace review

Check link length, launch and receive events, connectors, splices, reflectance, non-reflective events, end event, and unexplained features. Confirm that automated event detection did not merge or omit closely spaced events.

5. Close out the optical plant

Testing becomes operational evidence only when it reconciles to the physical route and strand records.

Native evidence

Deliver native loss-test and OTDR files plus readable exports, organized by site, link, strand, wavelength, and direction. Include the instrument and setup record used to interpret them.

Plant records

Include route and riser diagrams, enclosure and tray records, splice matrix, termination and adapter schedule, rack or panel elevations, spare-strand status, and labeled photographs.

Exceptions

Identify damaged, unavailable, reserved, noncompliant, or owner-accepted strands and their disposition. Do not make an exception disappear by excluding it from the final report population.

Acceptance

Reconcile the strand count, close the punch list, identify any warranty submission, and obtain approval from the named owner representative before archiving the system of record.

When this is not the right approach

This guide does not establish the loss budget, test method, wavelength, direction, event threshold, or pass limit for a specific design. The executed specification, supported applications, manufacturer requirements, and responsible qualified designer control those values.

Straight answers

No. Insertion-loss testing directly measures end-to-end loss under the selected reference method. An OTDR estimates loss from backscatter and provides distance and event-location evidence. A project may require both because they answer different acceptance and troubleshooting questions.

Put a field-executable scope in front of the crew

Email the site count, geography, schedule, and current documents. Cheryl routes the request to the right deployment lead.

Plan Fiber Acceptance
partners@srsnetworks.com · (866) 224-3636