4.5 Corrective Action Strategies

Match the Action to the Fault

After a fault is isolated, the Technician selects a corrective action. The action must match the diagnosed root cause; a mismatched action either fails to clear the fault or introduces a new one. The basic action-to-fault mapping:

Always start with the cheapest, least invasive action that matches the fault. Cleaning a connector is cheaper than re-terminating; re-terminating is cheaper than replacing a run; re-routing a macrobend is cheaper than pulling new cable.

Re-Terminate

Re-termination is the answer to most copper connector faults and a few fiber connector faults. Indications:

• Copper NEXT or return loss failure localized to a single termination.
• Wire-map fault (split pair, crossed pair) at a jack.
• A fiber connector with persistent high reflectance after cleaning.

Copper re-termination: remove the connector, re-strip to the correct length, maintain pair twist to within the category's allowance (≤ 13 mm Cat 6, less for Cat 6A), re-punch, re-test. Always cut the jacket back only as far as the connector allows; excessive jacket strip changes impedance and causes return loss.

Fiber re-termination: re-cleave and re-polish (or replace a field-polish connector); for fusion-splice-on connectors, re-splice. Verify with a microscope for end-face geometry and a VFL for continuity before re-testing.

Re-Splice

Fiber splice failures are usually high loss (≥ 0.5 dB on single-mode) or high reflectance (mechanical splice). Corrective action:

1. Open the splice closure.
2. Identify the bad splice (by OTDR distance or visual inspection).
3. Re-strip, re-cleave, re-arc the fusion splice; or re-seat a mechanical splice after cleaning.
4. Re-protect with the splice sleeve.
5. Re-test with the OTDR from one end and confirm the per-event loss is within allowance.

A splice that fails twice should be examined for fiber type mismatch (e.g., splicing OS2 to OS1, or single-mode to multimode), dirty cleaver, or worn electrodes on the splicer.

Re-Route

A macrobend or crushed cable cannot be cleaned or re-spliced; it must be re-routed to remove the bend or the crushing force. Indications:

• OTDR shows a non-reflective loss event at a bend in the cable path.
• Loss appears at 1550 nm but not 1310 nm on single-mode.
• Visual inspection shows a cable pulled tight around a corner or pinched by cable trays, conduit, or hardware.

Corrective action: re-support the cable so the bend radius is greater than the minimum (typically ≥ 10× cable diameter under tension, ≥ 30 mm for most premises cable), relieve the pinch point, and re-test at both wavelengths. If the cable has taken a set (kinked jacket), the section should be cut out and re-spliced or replaced.

Replace Cable

Cable replacement is the last resort. Indications:

• Cable jacket damage with exposed fibers or conductors.
• Water ingress into the cable core.
• A length of cable damaged by a staple, nail, or crush that cannot be spliced out.
• Category mismatch (e.g., Cat 5e in a Cat 6A required run).

For copper, replace the entire permanent link from the patch panel to the work area outlet; do not splice copper horizontal cable. For fiber, a damaged section can be cut out and a new section spliced in, provided the added splice loss stays within budget.

Document the Fix

A fault is not closed until it is documented. The record of corrective action includes:

• The original failed test result (saved).
• The diagnosed fault (specific — "split pair at work area outlet, pair 3").
• The action taken (specific — "re-terminated WAO jack to T568B, reduced untwist to 8 mm").
• Any parts replaced (with serial/lots where applicable).
• The post-fix test result, same standard and reference method.
• The Technician's identity and date.

Documentation supports warranty claims, future troubleshooting, and the as-built record.

Verify with a Re-Test

The re-test is the verification step. Requirements:

• Same standard and category as the original test.
• Same wavelength(s) and reference method for fiber.
• Same certifier or one of equivalent or higher capability.
• Same link definition (permanent link adapter vs. channel adapter).

A re-test that fails means the corrective action was wrong or incomplete — return to fault isolation, do not stack a second corrective action on top of the first.

When to Escalate

Escalate (rather than continue) when:

• The fault recurs after a verified corrective action — the root cause is upstream.
• The fault is on a backbone link beyond the Technician's scope (e.g., outside plant, requiring OSP certification).
• The fix would change the as-built design (e.g., re-routing a backbone) — that is a design change requiring RCDD or project approval.