How to Build and Read an Optical Power Budget
A practical guide to transmitter power, receiver sensitivity, fiber attenuation, connector loss, splice loss and engineering margin.
The budget answers one basic question
An optical power budget estimates whether the light leaving the transmitter should still be within the receiver’s usable range after passing through the fiber path. Start with transmitter power in dBm, subtract expected losses, and compare the result with the receiver specification.
If the estimated receive power is above the minimum sensitivity, the difference is margin. A positive number is necessary, but a design with almost no margin may still be operationally fragile.
Account for every passive loss
Fiber attenuation is usually expressed in dB per kilometer and varies by wavelength and fiber type. Connectors, patch panels, splitters and splices add discrete losses. A route that looks short on a map can still have significant insertion loss if it passes through many passive events.
Use your organization’s engineering values rather than generic assumptions whenever possible. Acceptance criteria for a new splice or connector may be tighter than a rough planning estimate.
Margin is where real networks live
Engineering margin covers things the clean spreadsheet does not perfectly predict: aging, future repair splices, temperature, dirty connectors, measurement uncertainty and small route changes. A link that works only when every component performs at its best is not a comfortable design.
How much margin is required depends on the transport system, optic type, distance and company standards. Long-haul amplified systems and passive access networks have different design considerations from a simple point-to-point Ethernet optic.
Receiver maximum matters too
A receiver has both a minimum sensitivity and, in many cases, a maximum input level. Very short links with high-power optics can require attenuation to avoid overload.
That is why “more light” is not always better. Compare the estimated and measured receive level with the full acceptable operating range in the optic specification.
Use measurements to close the loop
During troubleshooting, compare the calculated expectation with DOM readings, power-meter measurements and OTDR results. Large unexplained differences are clues: contamination, bending, a poor splice, wrong patching, an unexpected splitter or a damaged span.
Clean and inspect connectors before assuming the fiber itself is bad. Contamination remains one of the simplest causes of optical trouble and one of the easiest to introduce during maintenance.