Can the installed splitter remain for XGS-PON or EPON?
An installed splitter may remain in service, but passive operation or a wideband label does not prove reuse. First, tie the installed unit to an exact model and revision. Then verify its documented optical band, the cutover or coexistence design, and the shortest and longest affected paths against the limits for the installed OLT and ONT/ONU. If any of those inputs is unresolved, the decision is Hold, not Retain.
Retain, replace or hold
| Decision | Use it when | Evidence required before release |
|---|---|---|
| Retain | Identity, optical band, interfaces, package and installed condition are confirmed; the implemented architecture is defined; all required path checks pass. | As-built identity, applicable product record, path calculations, inspection/test record and named approval. |
| Replace | A controlled requirement is shown not to comply and replacement is the agreed remedy. | Failed requirement, replacement specification, revised budget and change plan. |
| Hold | Identity, topology, loss, isolation, interface condition or acceptance criteria are still unknown. | Open-item register showing what evidence is missing, who owns it and how it will be closed. |
Representative brownfield decision
The following is an illustrative decision, not a customer case. An ISP plans to add XGS-PON to a live GPON tree. The field label identifies a 1×32 PLC splitter, but the model and revision cannot be traced. A current family page lists a suitable operating band. The correct status is Hold. The label supports the topology record, and the family page can help identify candidates, but neither proves the optical limits of the installed unit. Recover the applicable order record or drawing, or agree on an identification and measurement plan. Recalculate the path only after the coexistence design and installed asset are defined.
What each evidence source can and cannot prove
Compatibility evidence is useful only inside its stated scope. Use this table to prevent a convenient record from being treated as broader proof.
| Evidence source | What it can support | What it does not prove | Action if it is the only evidence |
|---|---|---|---|
| Field label or photograph | Location, visible port count, package, connector polish and identifiers | Operating band, insertion loss, uniformity, PDL or current condition of every path | Use it to search the asset register; keep the decision on Hold. |
| Current family webpage | Candidate product family and documents to request | Identity or limits of an older, custom or differently revised installed unit | Obtain the applicable archived order code, datasheet or drawing. |
| Archived datasheet and drawing | Model-level limits, interfaces, dimensions and stated environmental scope | That the installed unit is the named revision or still meets those limits | Tie the document to order/as-built evidence, then inspect or test as required. |
| Component or per-port test record | Results for the identified unit, sample or lot under the recorded method | Installed-route loss, connector condition, coexistence-device loss or untested wavelengths | Confirm traceability, method, wavelength, direction, limits and sampling scope. |
| Installed end-to-end result | Performance of the tested path under the recorded system and test conditions | Legacy component identity, untested branches or performance after an architecture change | Preserve it as a baseline and repeat the affected checks for the new design. |
| OTDR trace | Event location and comparative path evidence when the setup and topology are defined | Universal component insertion loss, optical return loss or complete system approval | Interpret it with the approved topology and pair it with the required power/loss records. |
Why a wideband label is not enough
An operating-band statement answers only whether the documented wavelength range is relevant. It does not close the system review. ITU-T G.9805 describes coexistence-element, multi-PON-module and splitter-based methods for sharing an ODN. The implemented method may add model-specific loss, isolation and wavelength-blocking requirements. Include those elements in the new calculation; do not transfer the old GPON result unchanged.
Cutover and coexistence require different evidence
A cutover removes the former service path before the new system becomes the operating design. Coexistence carries two or more PON generations on the ODN at the same time. The splitter review starts from the same installed identity, but the system evidence is different.
| Decision item | Service cutover | Simultaneous coexistence |
|---|---|---|
| Architecture record | Final XGS-PON or EPON path after the old service is removed | Implemented CEx, MPM or splitter-based coexistence path, including port mapping |
| Optical review | New-system upstream and downstream path window | Every active wavelength path, including added loss, isolation and wavelength-blocking requirements |
| Legacy equipment | Removal sequence, outage plan and rollback point | Behavior of the retained GPON OLT/ONT population and coexistence devices |
| Acceptance | Baseline, cutover result and rollback threshold | Separate acceptance criteria for each PON generation and the shared passive path |
| Release condition | New path passes and the migration authority approves the cutover | Both systems pass concurrently and the network owner approves the coexistence state |
Do not use a successful cutover calculation as proof that simultaneous coexistence will work. Do not require coexistence-specific hardware when the approved project is a clean cutover; document which architecture is actually being released.
Brownfield splitter evidence sequence
Review the installation in this order:
- Identify the installed asset. Record the site or node, splitter stage, input/output count, port map, package, labels, connector polish, pigtails and any model, serial or lot identifiers. Photographs can support identification; they cannot prove insertion loss or wavelength performance.
- Recover the applicable product record. Match the installed identity to the relevant current or archived datasheet and drawing revision. Check the operating band, maximum insertion loss for each required path, uniformity, polarization-dependent loss, return loss or directivity where specified, fiber, connectors, package and stated environmental scope. ITU-T G.671 provides terminology and transmission-parameter context for optical components; the exact limits still come from the applicable model record. If the record cannot be tied to the installed unit, keep the decision on hold.
- Define the network change. State whether the project is a service cutover or simultaneous coexistence. Record the OLT and ONT/ONU models, implemented optical class, coexistence method, wavelength-blocking requirements and any RF-video or monitoring wavelength used on the ODN.
- Recalculate the path window. Include every splitter stage, coexistence device, fiber section, mated pair, splice and other passive element at the relevant wavelengths. Check upstream and downstream, the shortest and longest paths, maximum-loss/sensitivity limits, minimum-loss/overload limits and the network owner's design reserve. Keep the assumptions with the fiber loss budget calculation.
If the route record distinguishes G.652.D feeder or distribution sections from G.657 A1/A2 drop sections, keep those sections separate and use the project-approved attenuation and bend-loss assumptions at each wavelength. The route-fiber category affects the path calculation; it does not approve the splitter. - Inspect the installed assembly. Verify the port map, APC/UPC interface schedule, end-face condition, pigtails, bend management, package fit and enclosure protection. For an outdoor closure or cabinet, record the condition of the enclosure, seals, cable entries, strain relief and any evidence of moisture or contamination. Do not treat an intact label as evidence that the optical paths still meet their limits.
- Set acceptance criteria before the change. Define test direction, wavelengths, instruments, reference method, per-port limits, sampling scope, failed-result disposition, permitted substitutions and release authority.
Component evidence and installed-route evidence answer different questions. IEC 61300-3-4:2023 covers attenuation-measurement methods for optical components. IEC 61280-4-2:2024 addresses installed single-mode cabling-plant attenuation and optical return-loss measurement. Neither citation supplies a project limit or proves a BWNFiber model. If OTDR is part of acceptance or fault location, record its wavelength, launch and receive conditions, route access, splitter topology and interpretation method. Do not substitute one OTDR trace for the component record or the agreed end-to-end acceptance result.
Do not recreate missing specifications from a current family page. A family page can help locate documents; it cannot identify an older or custom unit already in the field.
What the supplier can verify and what remains with the network owner
A component supplier can map a proposed order code to its datasheet, drawing and available test documentation. The network owner or its authorized designer must still approve the as-built identity, system architecture, path budget, field condition and migration method. In an RFQ, ask for a response against an exact configuration rather than a yes/no answer to "Is this splitter XGS-PON compatible?" For a replacement order, state whether the exact configuration needs a sample, per-port test record or first-article approval before volume release. Carrier specifications and project acceptance procedures take precedence over country-level assumptions.
EPON compatibility boundary
A splitter whose documented band covers the required wavelengths may be an EPON candidate, but that is not system approval. Verify the implemented Ethernet PON generation under the applicable IEEE 802.3 requirements, OLT/ONU limits, interfaces, optical paths and operator rules separately. A GPON or XGS-PON family statement is not EPON certification.
Compatibility decision record
Issue one decision record containing:
- ODN/tree identifier and revision;
- installed splitter identity and evidence source;
- old and new PON systems, equipment models and optical classes;
- cutover or coexistence architecture and device records;
- shortest- and longest-path calculations for both directions;
- interface, package and condition findings;
- open exceptions and remediation;
- final
retain / replace / holdstatus; - technical approver, approval date and change authority.
Use the fiber optic splitter product and configuration hub to identify candidate models, then request the document for the exact order code and revision. Keep candidate-product evidence separate from the record used to identify the installed unit.
Move a Hold decision into a reviewable inquiry
If the installed unit remains on Hold, do not ask for a generic compatibility confirmation. Send BWNFiber the OLT and ONT/ONU models, implemented optical class, current topology and installed splitter identifiers. Include the shortest- and longest-route records, cutover or coexistence method, interface schedule, quantity and required document format. Ask for a gap list and a candidate-configuration comparison against those inputs. Final ODN design and migration approval remain with the network owner or its authorized designer.
Technical notice: This is a review method, not approval of an installed splitter and not a guarantee of performance. Model data, test scope, availability, price, MOQ and lead time require current configuration-specific confirmation.
