ELSFP Power Budget: From Laser Output to Optical-Engine Input

ELSFP • CPO integration • Engineering & procurement

The laser’s output power is not the power that reaches an optical engine. Before choosing an ELSFP, define the optical path—and check that its lowest and highest delivered power fit the engine’s requirements.

For an AI data-center CPO design, this is a continuous-wave (CW) laser-feed budget. It is not the modulated transmitter-to-receiver link budget, and passing it does not establish bit-error-rate performance or system compatibility. If the architecture is new to you, start with what an ELSFP does in a CPO system.

Figure at a glance: assumed source 20–22 dBm → assumed path loss 2–4 dB → calculated engine input 16–20 dBm. Assumed engine acceptance: 14–21 dBm; chosen lower reserve: 2 dB.

1. Put the reference planes on the drawing

Mark a source-output plane and the optical engine’s CW-input plane. List every connector, fiber segment, coupling interface and any splitter between them. A loss belongs in the calculation only if it falls between those planes and is not already included in the quoted source power.

OIF-ELSFP-02.0 specifies optical power per wavelength per core at TPL2; its test setup uses a characterized optical patch cord. A nominal power class therefore is not, by itself, a guaranteed minimum at your engine. Align the supplier’s stated measurement plane and tolerances with your own diagram before subtracting loss. [1, §§3.5–3.6]

For procurement, request a marked-up interface drawing rather than accepting “output power” without a location. Confirm whether the connector or pigtail you intend to use is included in that value. Otherwise, two apparently comparable quotes can describe different boundaries.

2. Calculate both corners, not just the minimum

Use dBm for absolute optical power and dB for relative loss. Here, L is a positive attenuation: a 4 dB loss is subtracted from the source power. This convention follows the distinction explained by the Fiber Optic Association’s measurement reference. [2]

Compare the low corner against the engine’s required minimum plus your chosen design reserve. Compare the high corner against the engine’s allowed maximum. Do not assume extra laser power is always useful: a low-loss path can make the upper limit the controlling constraint.

These corner calculations form a conservative envelope when the source and path bounds apply over the same operating conditions. If temperature or control settings couple them, document the permitted combinations rather than claiming that every mathematical corner is physically realized.

3. A worked example—with no product claims

Assumptions only: one CW optical channel, source bounds of 20–22 dBm, total path attenuation of 2–4 dB, and an engine input window of 14–21 dBm. We choose a 2 dB lower-side engineering reserve. These are invented teaching values, not OIF limits, vendor ratings or a recommended operating point.

The last row is the useful purchasing insight: “it still turns on” and “it meets our margin policy” are different acceptance criteria. A connector change or added routing interface should trigger a budget update, not merely a check that light is present.

4. Make the loss allocation auditable

Build one budget per relevant optical path and wavelength. Do not pool the powers of independent channels into a single dBm number. Where a real architecture uses a splitter, include its specified division loss and excess loss once, at the correct boundary; do not assume every ELSFP-to-engine path uses one.

For each line item, record minimum and maximum loss, wavelength, temperature range, mating condition and evidence source. Treat typical values as estimates, not acceptance bounds. Allocate measurement uncertainty and degradation allowances explicitly, and check whether source tolerances or vendor guarantees already include them. Counting an allowance twice can reject a viable design; omitting it can hide a fragile one.

Power is only one gate. A passing budget does not verify wavelength alignment, polarization behavior, connector compatibility, thermal performance or host control. Keep those checks in the same evaluation plan without pretending this calculation covers them.

5. Ask suppliers for evidence that closes the budget

1. Source bounds: guaranteed minimum and maximum per channel, the measurement plane, and the operating conditions attached to those values.
2. Engine limits: the required and maximum permitted CW input power at a named interface, with the applicable wavelength and polarization conditions.
3. Path definition: connector types, fiber routing, any splitting, and a clear statement of what the quoted output already includes.
4. Verification plan: calibrated measurement method, reference-plane handling, uncertainty, sample configuration and pass/fail criteria—not just a typical screenshot.
5. Change control: which cable, connector, firmware or thermal changes require requalification of the budget.

Follow the equipment supplier’s laser-safety and interlock procedures. OIF’s Appendix B describes inspection, cleaning and link-loss verification before full-power operation. The arithmetic above is not permission to energize an unverified optical path or bypass a safety check. [1, Appendix B]