Curriculum CFOS/S Module 05

CFOS/S · Certified Fiber Optic Specialist, Splicing

Splice Testing & Verification

Explains visual fault location, OLTS, and OTDR testing methods used to verify completed splices and document results for acceptance.

Why a Splicer's Own Readout Is Never the Final Word

A fusion splicer's estimated loss and even a clean visual inspection of the fused joint tell a splicing specialist a great deal, but neither is an independent optical measurement through the actual completed link, and the CFOS/S Knowledge category on testing splices exists precisely because verification has to happen with dedicated test instruments separate from the splicing equipment itself. Three tools cover this verification work: the visual fault locator for quick continuity and gross fault checks, the optical loss test set for measuring actual end-to-end insertion loss against a loss budget, and the OTDR for characterizing the entire fiber length and pinpointing the location and magnitude of every event, splice included, along the route. Each tool answers a different question, and a competent splicing specialist knows which one to reach for depending on what needs verifying.

Verification is not a formality tacked onto the end of a splicing job. It is the step that actually confirms the job meets the design's loss budget, and it produces the documented record that everyone from the network operator to a future troubleshooting technician relies on when something goes wrong years later. A splice job without proper documented test results is, from a quality assurance standpoint, indistinguishable from a job that was never actually verified at all, regardless of how carefully the splicing itself was performed.

Visual Fault Location

A visual fault locator, commonly called a VFL, injects a visible red laser, typically around 650 nanometers, into the fiber and relies on the human eye to spot where light leaks out at a fault, whether a sharp macrobend, a poor mechanical splice, a broken fiber, or a connector that is not properly seated. VFLs are inexpensive, battery powered, and require no calibration record or complex setup, which makes them the go-to first check for continuity and gross fault location, especially on shorter cable runs and drop cables where the entire length might be physically accessible for visual inspection.

The VFL's fundamental limitation is that it only reveals faults severe enough to leak a meaningful amount of visible light, and it gives no quantitative loss value at all, so it cannot verify that a splice meeting a tight loss budget, say under 0.1 dB, is actually within spec. It also cannot see through jacketed cable or inside a sealed closure without physically exposing the fiber at the point of interest. A splicing specialist treats the VFL as a fast triage tool, useful for confirming a fiber is continuous and roughly locating an obvious problem like a broken fiber inside a closure, not as a substitute for quantitative OLTS or OTDR testing.

Optical Loss Test Set Measurement

An OLTS pairs a stabilized light source at the near end of the fiber with a calibrated power meter at the far end, and the difference between the launched power and the received power, expressed in dB, is the actual end-to-end insertion loss of the entire path, including every splice, connector, and the fiber's intrinsic attenuation across its length. This is the gold standard measurement for verifying a completed link against its design loss budget, since it measures exactly what a live signal will experience crossing that same path, unlike the splicer's own estimate, which only characterizes one splice in isolation without accounting for the rest of the link.

Correct OLTS testing requires reference-quality test jumpers and a proper reference measurement taken before testing the actual link, since any loss introduced by a dirty or damaged test jumper connector gets incorrectly attributed to the link under test if the reference step is skipped or done carelessly. Industry standard practice calls for testing at both the operating wavelength or wavelengths the system will actually use, and testing from both directions when practical, since a splice or connector's loss can occasionally differ measurably depending on which direction light travels through it, particularly with certain connector or splice defects. A splicing specialist reviewing an OLTS result compares the measured total loss against the link's designed loss budget, and a result that passes overall can still hide one bad splice if the budget has enough margin to absorb it, which is where OTDR testing becomes necessary to isolate individual event locations.

OTDR Testing and Event Analysis

An OTDR works by sending a series of short laser pulses down the fiber and measuring the tiny amount of light scattered backward, called backscatter, at every point along the fiber's length, then plotting that backscattered signal against distance to produce a trace. Splices, connectors, bends, and the fiber's own attenuation all show up as distinct features on this trace: a splice typically appears as a small, sharp step down in the trace's signal level, while a poor mechanical splice or a fault often shows a reflective spike combined with a loss step, and the fiber's continuous attenuation appears as the trace's steady overall downward slope between events.

Reading an OTDR trace accurately requires understanding a handful of well-documented quirks specific to the instrument. A gainer, an apparent increase in signal at a splice point rather than a loss, occurs when two fibers with slightly different backscatter coefficients are joined and is a measurement artifact rather than an actual gain in optical power; testing from both ends and averaging the two results is the standard way to get an accurate loss figure at a splice that shows a gainer from one direction. Dead zones near the instrument and near any strong reflective event can hide a second event that falls too close to the first, which is why OTDR testing on short links or closely spaced splices sometimes requires a launch cable ahead of the actual link under test to move the instrument's own dead zone away from the events of interest. OTDR results also depend heavily on selecting the correct index of refraction setting for the fiber under test, since an incorrect index setting shifts every distance measurement on the trace even though the loss values themselves remain accurate.

Documentation and Acceptance Standards

Every splice job needs a documented test record showing the method used, the measured results, the test wavelength, the equipment used including its calibration status, and a clear pass or fail determination against the project's specified acceptance criteria. This record protects the splicing specialist's own work, gives the network operator a baseline to compare against during future troubleshooting, and satisfies most contract and industry specifications that explicitly require documented acceptance testing before a splice job is considered complete. An OTDR trace file, in particular, becomes a permanent reference for that specific link, since any future OTDR test run at the same location can be directly compared against the original trace to identify new degradation or a new fault that has appeared since installation, which is often the fastest way to localize a problem on a route that already has a splicing specialist's original baseline on file.

Verifying a Completed Splice Job with OLTS and OTDR

This exercise covers the standard sequence for verifying a set of completed splices in a newly built or repaired outside plant link, combining OLTS insertion loss testing with OTDR event analysis to produce a complete, documented acceptance record. Assume all splicing and closure work from the previous modules is finished and the fiber run is ready for final testing.

  1. Gather the correct reference-quality test jumpers matching the connector type on the test equipment and the fiber type under test, inspecting each jumper's end face under a fiber scope before use.
  2. Set the OLTS light source to the system's actual operating wavelength or wavelengths and perform the reference power measurement using a known-good jumper pair before connecting to the link under test.
  3. Connect the OLTS source at the near end and the power meter at the far end of the link, then record the measured insertion loss.
  4. Repeat the OLTS measurement from the opposite direction if the job specification calls for bidirectional testing, particularly on links with a tight loss budget.
  5. Compare the measured total loss against the link's designed loss budget and flag the result as pass or fail before moving to OTDR testing.
  6. Connect the OTDR to the near end of the link, using a launch cable if the link is short enough that the instrument's dead zone could obscure near-end events.
  7. Set the OTDR's index of refraction to match the actual fiber type under test and select a pulse width appropriate to the link's length.
  8. Run the OTDR trace and allow it to complete a full averaging cycle rather than reading a single-shot trace, since averaging reduces noise and improves event resolution.
  9. Identify every event on the trace, including each splice, and record its loss value and distance from the near end.
  10. Test from the opposite end if any splice shows a gainer or an unusually low loss reading that seems inconsistent with the OLTS total, and average the two directional results for that splice.
  11. Compare each individual splice's OTDR loss value against the expected range for the splicing method used, flagging any outlier for possible re-splicing.
  12. Save the OTDR trace files and compile a documented test record including wavelength, equipment used, calibration status, measured results, and a final pass or fail determination for the job file.

What a bad job looks like

A common testing shortcut is relying only on the fusion splicer's own estimated loss and skipping independent OLTS or OTDR verification entirely, which leaves a job with no record of actual end-to-end performance and no way to catch a defect the splicer's imaging could not see, such as a bad cleave end face contributing scattering loss. This shortcut often goes unnoticed until the link is placed into service and performs worse than expected, at which point there is no baseline test record to compare against, making the eventual troubleshooting far slower than it would have been with a proper original trace on file.

Misreading an OTDR trace is another frequent failure, particularly around gainers and dead zones. A technician unfamiliar with these artifacts might see an apparent gain at a splice and conclude, incorrectly, that the splice actually improved signal, or might miss a second event hidden in a dead zone right after a strong reflective connector, reporting a route as clean when a real fault sits just past the point the instrument could resolve. Skipping the reference measurement step on an OLTS test, or using a damaged or dirty reference jumper, produces a systematic error that gets attributed entirely to the link under test, potentially failing a perfectly good splicing job because of a problem in the test setup rather than the actual work. All of these testing mistakes share a common thread: they produce a result that looks like a legitimate measurement but does not actually reflect the true condition of the link, which defeats the entire purpose of verification.

What the Exam Expects on Splice Testing

The CFOS/S exam covers this material under the Knowledge category for testing splices, specifically visual fault location, OLTS testing, OTDR testing, and documenting test results, and it favors questions requiring you to interpret a test result or trace feature correctly rather than just naming the instruments. Expect at least one gainer or dead zone question, since these are classic OTDR interpretation traps the exam uses to separate genuine understanding from memorized definitions.

Knowledge check

7-question self-check

0 understood

0 of 7 completed

Question 01

An OTDR trace shows an apparent gain, rather than a loss, at a splice location. What does this actually mean, and what should the technician do?

Check answer

Explanation

A gainer is a measurement artifact caused by joining two fibers with slightly different backscatter coefficients, not an actual increase in optical power at that point. The technician should test from the opposite end of the fiber and average the two directional loss readings to get an accurate loss value for that splice.

Mark your result

Question 02

Why is a visual fault locator not sufficient to verify that a splice meets a 0.1 dB loss budget?

Check answer

Explanation

A VFL only reveals faults severe enough to leak visible light and provides no quantitative loss measurement at all, so it cannot confirm a splice is within a specific numeric loss budget. Quantitative verification requires an OLTS or OTDR measurement instead.

Mark your result

Question 03

A splicing crew skips the OLTS reference measurement step and uses a visibly worn test jumper to test a completed link, which then fails against the loss budget. What is the most likely explanation?

Check answer

Explanation

The most likely explanation is that loss from the worn or dirty reference jumper is being incorrectly attributed to the link itself, since skipping a proper reference measurement means there is no baseline correction for the test setup's own loss contribution. The crew should redo the reference measurement with a known-good jumper before concluding the link actually fails.

Mark your result

Question 04

An OTDR trace of a newly built link shows a strong reflective spike immediately after the near-end connector, and no other events are visible for the first 50 meters. What should the technician be concerned about?

Check answer

Explanation

The technician should be concerned that the dead zone following that strong reflective event could be hiding a second event, such as a splice or a fault, located close to the connector. Using a launch cable to move the instrument's dead zone away from the events of interest would resolve this uncertainty.

Mark your result

Question 05

An OLTS measurement shows a link's total insertion loss passing well within budget, but the network later experiences intermittent problems traced to one bad splice on that route. How could this happen despite a passing OLTS result?

Check answer

Explanation

A passing total loss measurement can still hide one individual bad splice if the link's overall loss budget has enough margin to absorb that one high-loss event without exceeding the total limit. This is exactly why OTDR testing, which isolates the loss at each individual event location, is necessary in addition to an end-to-end OLTS measurement.

Mark your result

Question 06

Why does OTDR testing require setting the correct index of refraction for the specific fiber under test, and what happens if the wrong value is used?

Check answer

Explanation

The index of refraction setting converts the instrument's time-of-flight measurement into a distance value, so an incorrect setting shifts every distance reading on the trace even though the loss values at each event remain accurate. This can cause a technician to misidentify which physical splice or feature corresponds to which event on the trace.

Mark your result

Question 07

What should a complete splice test documentation record include, and why does the OTDR trace file specifically matter for future troubleshooting?

Check answer

Explanation

A complete record should include the test method, measured results, test wavelength, equipment used with its calibration status, and a clear pass or fail determination against the project's acceptance criteria. The OTDR trace file specifically matters because it serves as a permanent baseline that a future test on the same link can be directly compared against to quickly identify new degradation or faults that have appeared since installation.

Mark your result