ELSFP Interface Qualification: Fiber Mapping, Polarization and Host Checks

WE / Western Optronics • Optical engineering

An ELSFP can fit the cage and deliver the expected optical power while the integration still needs a more basic answer: which light reaches which engine input, with which polarization reference?

For teams building CPO systems, a useful interface review connects three records: the optical drawing, the harness build record and the host’s resource map. This engineering note proposes a practical way to make those records agree before design release.

Our earlier articles cover the ELSFP’s architectural role and the CW power budget. Here, the focus is identity and acceptance evidence, not a new power calculation.

1. Freeze the drawing’s point of view

Start the interface record with a drawing revision and an explicit viewing direction. Label the module-side view and host-side view separately. Avoid a diagram that silently switches between looking into a connector and looking along a cable.

OIF-ELSFP-02.0 defines fiber naming, polarization orientation and DR/FR wavelength assignments for the specified MT-12 configurations. Use its Figure 36 and Table 5 when they apply; other assignments require the applicable ELSFP CMIS definition. [1, §3.4]

Then create one traceable entry per used feed. Include the source identifier, physical fiber position, wavelength requirement, harness route and destination input. Keep the engineering alias separate from the standard’s position name. An alias such as “S-A” helps a team discuss a path; it cannot replace a controlled pin-and-fiber drawing.

For unused positions, record the intended disposition rather than leaving an empty cell. Ask the assembly supplier to confirm it against the selected interface specification. This turns “not connected” into a reviewed design decision instead of an assumption made during build.

2. Separate mechanical fit from application acceptance

The OIF agreement explicitly notes that hard keying does not stop an 8PMF module from mating with a 4PMF port. The host must compare advertised CMIS capabilities with system needs and assign the required laser fibers. [1, §3.4.1]

For an integration review, create two sign-off lines: mechanical mating confirmed and application compatibility confirmed. A completed first line must not automatically complete the second. Record which module and firmware revisions were checked, and retain the capability readout used in the decision.

A useful review question is: “If a mechanically compatible replacement with different capabilities arrives, what evidence causes the host to accept or reject it?” Define that decision in the qualification plan before relying on a successful first installation.

3. Make the polarization reference measurable

OIF specifies an application-dependent polarization extinction ratio (PER), referenced to the line joining the module ferrule’s guide-hole centers. Its TPL2 measurement definition includes a characterized test patch cord. A PER value therefore needs a reference orientation and a known test setup. [1, §§3.4.1, 3.6.1]

Request a polarization evidence sheet with five fields: the applicable requirement, the reference axis, the measurement plane, the fixture identification and the stated test conditions. Ask how the supplier accounts for the fixture’s influence and measurement uncertainty. Do not turn an unqualified typical number into a guaranteed acceptance limit.

Also separate the module qualification from the installed-path qualification. If the purchasing decision depends on the condition at the engine input, ask for evidence at that boundary or a justified correlation to it. A module-only report should be labeled as such.

4. Reconcile the optical map with the host map

OIF’s management white paper places the ELS-to-OE relationship map in the host controller. It describes provisioned maps and possible verification or discovery methods; automatic discovery is not a universal assumption. The white paper is informative, not a replacement for the applicable specifications. [2, §§2, 5]

Use Figure 1 as a documentation exercise. If the harness record says S-A reaches OE-2/B but the host record says OE-1/A, the review has found a conflict even before discussing optical performance. Give the discrepancy an owner and reconcile both records against observed connectivity.

Keep evidence granular: one result per relevant feed, with fixture and assembly identifiers. “Light present” is a weaker record than “the identified source reaches the intended destination.” Any energized verification belongs under the system supplier’s approved procedures and laser-safety controls; this article is not a turn-on or connector-inspection procedure.

5. Ask for a compact, reusable evidence package

For a supplier review or internal design handoff, collect the following in one revision-controlled package:

1. Interface definition: the selected specification revisions, module and host connector drawings, and a feed-by-feed assignment list.
2. Assembly traceability: harness part and revision, endpoint labels, source and engine identifiers, and the build under evaluation.
3. Acceptance evidence: connectivity results, applicable polarization requirements and measurements, the separate power-budget report, and test conditions.
4. Host evidence: capability records, the installed resource map and the firmware revision used for the compatibility decision.
5. Change control: an owner for each exception and an explicit decision on what must be rechecked after a module, harness or firmware change.