Fiber Loss Budget: How to Tell If Your Link Loss Is Acceptable

A light meter gives you a number — say, 2.4 dB of loss. Is that good? On a 500-meter link with two connectors, it is terrible. On a 10-kilometer span with six connectors and four splices, it is excellent. The number alone answers nothing. The loss budget is what turns a measurement into a verdict: the maximum loss the link is allowed to have, worked out from its length and its components before you measure anything. Measure against the budget, and "pass" becomes a fact instead of a feeling.

Building the budget, piece by piece

A link's budget is the sum of three things: the fiber itself, every connector pair, and every splice. Count connectors as pairs — each mated connection, not each connector end — and count every splice in the span, including the ones in trays you did not open.

Those are planning allowances — the figures you use to judge whether a link is in the right neighbourhood. Your site's specification is the limit that actually governs, and it wins every argument. If the site spec says 0.75 dB per connector pair, use 0.75. The method does not change; only the numbers do.

A worked example

Take a single-mode span between two data halls: 2.0 km long, four connector pairs (two panels at each end), two fusion splices in trays along the route, tested at 1550 nm.

Budget at 1550 nm:
  Fiber:      2.0 km x 0.25 dB/km  = 0.5 dB
  Connectors: 4 pairs x 0.5 dB      = 2.0 dB
  Splices:    2 x 0.1 dB            = 0.2 dB
  Total budget:                     2.7 dB

Measured loss (light source + power meter): 2.4 dB
Verdict: PASS, with 0.3 dB margin.

Now change one fact: the same span measures 3.6 dB. That is 0.9 dB over budget — a real fault, even if the link is passing traffic right now. A link running over budget has no margin left: the next dirty connector, the next temperature swing, or the next optic swap can push it over the receiver's sensitivity and take the link down at the worst possible time. Over budget is a fault to fix on this visit, not a note to file.

When the measurement is over budget

Work the loss down in order of cheapest fix first — never re-terminate blindly:

1. Inspect and clean every connector, then re-measure. A dirty connector is the most common cause of excess loss, and cleaning costs minutes. Scope before and after: if the loss drops back inside budget, the fault was contamination, and the ticket should say so — the next tech needs to know this span collects dirt, not that it "was fixed."
2. OTDR the span to segment the loss. If cleaning does not bring it inside budget, the OTDR shows which event is over its allowance. Fix only that event: a connector reading 1.2 dB against a 0.5 dB allowance gets re-terminated or replaced; a splice reading 0.4 dB against 0.1 dB gets re-spliced. A total-loss number cannot tell you which one — the trace can.
3. Check the wavelength. A span measured at 1310 nm and a budget calculated at 1550 nm (or the reverse) will disagree by the fiber-attenuation difference, and a bend fault shows up far worse at 1550 nm. Test at the wavelength the optics actually use, and write it in the ticket — a loss figure without its wavelength is unverifiable.
4. Re-measure end to end and record the margin. After the fix, the new measured loss and the remaining margin are the proof. A link that went from 3.6 dB to 2.5 dB against a 2.7 dB budget passes with 0.2 dB margin — thin, but a pass, and the thin margin itself is worth noting for the next visit.

Recording a loss-budget result in the ticket

A ticket that says "loss OK" cannot be re-checked. A ticket with the budget, the measurement, and the margin can. The minimum useful note:

Span: Hall A ODF-2 ↔ Hall B ODF-5 (2.0 km SM).
Budget @1550 nm: fiber 0.5 + 4 connector pairs 2.0 + 2 splices 0.2 = 2.7 dB.
Measured before: 3.6 dB (0.9 dB over budget).
Found: bulkhead connector at Hall B panel, 1.2 dB (allowance 0.5 dB), contamination on scope.
Action: cleaned + re-inspected (clean), re-terminated same panel position.
Measured after: 2.5 dB @1550 nm — PASS, 0.2 dB margin.

The shape to copy: the budget calculation itself, the before-and-after measurements, the wavelength, the faulty event with its own allowance, and the margin. That note lets the next tech verify the pass, spot the thin margin, and know exactly which panel to check first when this span acts up again.

See RackReady   Free sample   Fiber no-link checklist

Support: support@hasherventures.com

Free tool: turn your loss-budget findings into a structured ticket note with the RackReady Ticket Builder.