The bottom line: Fiber splitter mode compatibility is confirmed only when the active equipment, every fiber segment, the exact splitter assembly, operating wavelengths and acceptance method agree in one documented optical path. A connector that fits or an output that shows power is not approval. If required evidence is missing or contradictory, place the configuration on HOLD.
Procurement summary: Use this guide when approving a new splitter, reviewing a replacement or investigating a poorly documented legacy link. Complete the release record with the path ID, active interfaces, fiber designation for every segment, wavelengths, exact splitter order code and document revision, applicable test method, reference planes, limits and results. Mark missing or conflicting mandatory evidence as HOLD. BWNFiber can compare the completed record with the proposed order code, controlled drawing and available model documents. The project authority remains responsible for system design, the adopted acceptance plan and final release.
Key takeaways for release
- Physical mating or detected optical power is screening evidence, not approval.
- A splitter family name is not an exact model record.
- Optical-fiber designation and cable construction are separate controls.
- Component characterization does not replace installed-link acceptance.
- Any unresolved mandatory field keeps the configuration on HOLD.
Quick navigation
- Check the five-layer evidence chain
- Identify the exact fiber and splitter records
- Set the component and installed-link test basis
- Investigate a suspected mismatch
- Complete the release record
- Prepare the procurement handoff
- Review the compatibility FAQ
What must match before a splitter can be released?
Review fiber splitter mode compatibility as one evidence chain. Every relevant layer needs an identified source and a current record.
| Evidence layer | What to record | Acceptable evidence examples | Why it matters |
|---|---|---|---|
| Active equipment | transmitter, receiver, interface, source type and application | approved equipment record, interface specification, project design | Defines the optical signal that enters the path and the receiver condition at the far end |
| Installed fiber path | fiber designation for every segment, splices, adapters and transitions | cable schedule, as-built record, traceable cable marking, approved inspection record | Prevents an undocumented segment or transition from being hidden inside a general "SM" or "MM" label |
| Exact splitter assembly | manufacturer, complete order code, port map, internal/pigtail fiber, package and document revision | current model datasheet, controlled drawing, order-code definition, model-specific test record | A product family or nearby model does not prove the selected assembly's construction or optical limits |
| Operating conditions | wavelength or range, direction, topology position and required interfaces | wavelength plan, interface schedule, application drawing | Keeps a result at one condition from being generalized to another |
| Acceptance basis | test method, launch condition, reference planes, direction, limit source and instrument status | approved inspection and test plan, project standard, calibrated test record | Makes a measured value interpretable and repeatable |
If these records are incomplete, keep the configuration on HOLD. Connector fit, detected power and PLC or FBT naming may help trace the path, but none closes a missing equipment, fiber, device or test record.
90-second compatibility triage
Use this triage before commissioning a test or accepting a substitution. It is a preliminary control, not the final approval record.
| Evidence available now | Provisional disposition | Next action |
|---|---|---|
| Exact path, exact splitter, operating conditions, approved method and conforming results are all traceable | candidate PASS | obtain the required approval and freeze the released configuration and revisions |
| The path is known, but the splitter is identified only by a family name, photograph or partial order code | HOLD | obtain the complete order code, controlled drawing and exact fiber/interface declaration |
| The splitter is identified, but the installed fiber, launch condition, reference planes or applicable limit is unknown | HOLD | close the missing path or test-basis field before comparing results |
| The connector mates or optical power is detected, but controlled records are incomplete | HOLD | preserve the observation for troubleshooting and complete the evidence chain |
| An approved requirement conflicts with the proposed device or a required result fails its applicable limit | REJECT | choose a documented configuration or obtain an authorized redesign |
If any row is HOLD, continue with the Mode Compatibility Release Record and name the missing record before asking a supplier to confirm compatibility.
Start with the decision you are trying to make
Mode compatibility is one engineering gate. If the unresolved question concerns fiber fundamentals, splitter selection or network architecture, use the relevant guide before starting the release record.
| Decision to make | Relevant BWNFiber resource | What it helps you decide |
|---|---|---|
| Compare single-mode and multimode fiber systems | Single Mode vs Multimode Fiber | Fiber characteristics and broad application trade-offs |
| Classify a splitter by technology, topology, package, fiber or connector | Fiber Optic Splitter Types | The correct splitter category and terminology |
| Select a GPON split ratio, calculate the ODN budget or prepare procurement requirements | Fiber Splitter Selection Guide | PON design, loss budget and supplier-selection inputs |
| Decide whether "coupler" and "splitter" records describe equivalent functions | Fiber Optic Coupler vs Splitter | Naming and substitution screening |
| Place a splitter in an access-network design | FTTx Solution | FTTx architecture and deployment context |
| Review high-density data-center connectivity | Data Center Solutions | MPO, active-interconnect and cabling-system design |
| Browse splitter families after requirements are defined | Fiber Optic Splitter product center | Product discovery and commercial inquiry |
| Approve an exact splitter in an identified optical path | This guide | Compatibility evidence, test basis and release disposition |
If the intended function is still unclear, resolve that first. A rigorous mode review cannot correct a component chosen for the wrong function.
Build the mode-compatibility evidence chain
1. Identify the system at both ends
Record the actual transmitter and receiver rather than relying on a network label. Include the active interface, wavelength plan and direction of use. If a passive branch is used differently in each direction, the design authority should identify every condition that needs approval.
Do not infer source behavior from the connector installed on the equipment. The connector is one interface attribute; it does not define the complete optical signal.
2. Identify every fiber segment
"Single-mode" and "multimode" are starting categories, not complete asset records. For single-mode paths, record the actual category, such as G.652.D, G.657.A1 or G.657.A2. ITU-T G.652 (08/2024) covers G.652.D, while ITU-T G.657 (08/2024) defines bend-loss-insensitive categories including A1 and A2. G.657 Category A fibers are compliant with G.652.D attributes, but that relationship does not approve a finished cable, pigtail or splitter assembly.
For multimode paths, record the exact OM category. IEC 60793-2-10:2019+AMD1:2022 covers A1-OM1 through A1-OM5 and distinguishes the 50/125 micrometer OM2, OM3, OM4 and OM5 bandwidth grades. A general "50/125" or "multimode" description is therefore incomplete for asset and test control.
Do not fill a documentation gap from jacket color, connector boot color or a nearby cable label. If a transition is intentionally engineered, identify its location and the document that approves it.
Use the fiber optic cable selection page for permanent route families and the fiber patch cord page for connectorized equipment or test links. Those category pages help classify the segment, but final approval still requires the exact model record.
These fiber standards identify fiber characteristics; citing one does not approve a complete splitter assembly. The G.657 fiber-category design radius also must not be copied into a finished cable or assembly bend limit. Use the approved product document for the applicable installation and long-term bend requirements.
Separate optical-fiber identity from cable construction
The compatibility record needs the optical-fiber identity for every segment. Cable construction and route conditions are separate controls. Bring them into the investigation when they help identify the asset or explain damage, but do not use them to infer the splitter's fiber mode.
| Review axis | Examples | What it controls | What it does not prove |
|---|---|---|---|
| Optical-fiber designation | G.652.D, G.657.A1/A2, OM3, OM4, OM5 | optical category and the applicable fiber/test context | finished-cable construction or splitter approval |
| Buffer and cable construction | loose tube, tight buffered, armored, ADSS, drop cable | handling, termination approach and route suitability for an exact cable design | single-mode or multimode compatibility by name alone |
| Installation method | self-supporting aerial, duct, direct burial | loading, protection, hardware and installation plan | optical category or acceptance limit |
| Mechanical limits | cable bend radius, tensile strength, crush resistance | installation, pulling, service and maintenance limits for the exact cable | a universal value that can be copied to another construction |
| Jacket and environmental requirements | LSZH, PE, UV resistance, flame-retardant performance, water blocking, rodent protection | the specified site, safety and environmental conditions | one combined property; each requirement needs its own evidence |
| Capacity and path identity | fiber count, used fiber, splice, adapter and patch-cord records | the physical route and ports under review | fiber mode without a controlled designation |
IEC 60794-1-2:2021 provides general guidance across optical-cable test methods, and IEC 60794-1-21:2015+AMD1:2020 covers mechanical test procedures. Neither source creates one tensile, crush or bend limit for every cable; the project must use the exact cable specification and applicable test plan.
Indoor projects may specify LSZH or another defined fire-performance class, while exposed outdoor routes often require PE and verified UV resistance. Treat those as separate requirements: jacket material does not by itself prove flame, water-blocking or rodent-protection performance.
For an aerial route, ADSS (all-dielectric self-supporting) cable selection belongs to the route design and should account for span, wind and ice loading, hardware, the electrical environment where applicable, and the installation method. Where an FTTH indoor or drop-cable design calls for bend-loss-insensitive single-mode fiber, record the exact G.657 category, cable construction, jacket/fire requirement and product bend limits. Duct installation and direct-burial or armored-cable selection likewise address route and mechanical exposure. The splitter review imports those approved cable decisions; it does not replace them.
3. Resolve the exact splitter, not the family name
IEC 60875-1:2024 provides a generic specification context for non-wavelength-selective fiber-optic branching devices. It does not make "splitter," "PLC," or "FBT" a sufficient order description.
To identify whether a splitter is single-mode or multimode, start with the complete order code and its controlled model document. Do not infer the answer from the package, connector shell or technology label.
For the selected assembly, capture:
- complete manufacturer and order code;
- input/output port map and required power distribution;
- declared internal and pigtail fiber;
- operating wavelength scope;
- connector family and polish, or splice interface;
- package and pigtail construction;
- datasheet or drawing number and revision;
- model-specific test limits and the record required by the project.
BWNFiber publishes, for example, a specific SM/MM FBT splitter record and a separate OM3 MPO-to-LC 1×2 assembly record. Use the exact applicable record. Do not transfer a specification or availability statement from one page to another configuration.
If the exact record is unavailable, request the current model-matched datasheet and controlled drawing through the fiber splitter product center. A generic catalog or specification from a nearby model does not close the HOLD item.
4. Keep interfaces separate from fiber mode
Record connector family, ferrule/interface, polish and fiber designation in separate fields. "LC," "SC," "APC," and "UPC" do not replace a fiber-mode declaration. A correct mechanical interface can coexist with an unverified optical path.
This separation also improves purchasing control: the buyer can see whether a proposed substitution changed the optical design, the connector schedule, or both.
5. Preserve document identity and revision
The evidence package must be traceable. Record the datasheet revision, controlled drawing number, order acknowledgement, lot or serial identity when applicable, and test-record identifier. At receiving inspection, keep the delivered label and lot record tied to the approved order code and drawing. A different pigtail, connector, package or fiber marking reopens the review before installation. Packaging or handling damage is a receiving nonconformance, not proof of a mode mismatch.
If the supplier changes the pigtail fiber, internal component, connector, wavelength scope or approved order code, reopen the compatibility review. Treat "same family" as a description, not as change-control approval.
Apply the workflow to the actual failure context
The following are engineering review scenarios, not published BWNFiber customer cases. They show why the same symptom can require different evidence.
| Scenario | Initial evidence | Main risk | First review action |
|---|---|---|---|
| FTTH indoor or drop segment | route record names G.657 but the splitter pigtail record is generic | the bend-insensitive route fiber is mistaken for proof of the passive device construction | resolve the exact G.657 category, splitter order code, pigtail declaration and interface schedule |
| ISP or metro legacy path | an as-built record names G.652.D, the passive device is unlabeled and light is present | detected power is treated as approval for an unidentified component | preserve the baseline, identify every transition and hold substitution until the device record or approved investigation closes the gap |
| Data-center multimode branch | records contain OM3, OM4 or OM5 labels and the connector fits | different multimode records or launch conditions are treated as interchangeable | confirm the exact category for every segment and define the launch/test basis before comparing loss results |
| Outdoor route after maintenance | loss changed after aerial, duct or buried-route work | cable stress or damage is misdiagnosed as splitter mode mismatch | inspect route and cable evidence separately, then isolate the passive device without changing several variables at once |
Separate device characterization from installed-link acceptance
Keep the component record and the installed-link record separate. They answer different questions and one does not replace the other.
| Decision question | Primary evidence | Do not substitute |
|---|---|---|
| What is this exact device specified to do? | controlled model datasheet/drawing and required model-specific test record | a generic theoretical split value or another family member's data |
| Is the multimode installed path acceptable? | approved project method with recorded launch condition, reference planes, wavelength, direction and limit | an unrecorded light source or a result produced under a different modal launch |
| Is the single-mode installed path acceptable? | approved project method with recorded reference planes, wavelength, direction and limit | a result at an unrelated wavelength or an undefined connector baseline |
| Is a replacement equivalent? | both complete order records, change review and the required verification results | matching connector, package or marketing family alone |
How should multimode splitter testing record the launch condition?
IEC 61280-4-1:2019+AMD1:2021 covers attenuation measurement for installed multimode cabling and includes passive devices in its scope. Multimode measurements are sensitive to how optical power is launched into the available modes. IEC TR 62614-2:2015 provides background on encircled flux and multimode launch conditions.
Therefore, a multimode test record should not contain only a loss number. It should identify the applicable method, source/launch condition, wavelength, reference method, test direction, reference planes, equipment and limit source. A value without those conditions may be unsuitable for comparison or release.
How should single-mode installed-plant testing be recorded?
IEC 61280-4-2:2024 covers attenuation and optical return loss measurements of installed single-mode cabling. Its scope notes that the principles can be applied to plants containing branching devices such as splitters.
That scope does not create one universal splitter pass limit. The project still needs an approved design basis, exact model data, applicable wavelength conditions, reference planes and acceptance criteria.
An end-to-end attenuation or insertion-loss result and an OTDR trace do not answer the same question. Use the approved loss method for link acceptance; use OTDR where the project test plan calls for event analysis or fault location. Record direction, launch and receive arrangements, wavelength, instrument settings and the reference basis. A clean-looking trace does not replace the required component record or end-to-end acceptance result.
When are two loss results comparable?
Two measurements are comparable only when the decision context and recorded conditions match. Screen the records field by field rather than comparing the displayed loss values alone.
| Comparison field | What must agree or be explicitly reconciled | HOLD trigger |
|---|---|---|
| Object under test | exact component or exact installed path, including ports and configuration | one result is for a device while the other is for a complete path, or the identity is incomplete |
| Wavelength and direction | the conditions required for the same decision | a result from one wavelength or direction is applied to another without an approved basis |
| Multimode launch, if applicable | source and launch condition required by the adopted method | launch condition is missing, different or not recoverable |
| Reference basis | reference method, reference planes, test leads and connector treatment | the zero/reference arrangement is unknown or materially different |
| Method and limit | adopted procedure, edition and acceptance-limit source | a method, edition or limit is assumed from another project or document |
| Instrument record | equipment identity, settings and calibration status required by the test plan | the instrument record cannot support repeatability or traceability |
A theoretical split-loss value or a typical product loss chart can support early optical-budget planning, but it cannot approve an exact assembly or installed path by itself. It does not resolve excess loss, port uniformity, connector and splice contributions, wavelength conditions, test uncertainty or the project's remaining margin. If a required comparison field differs, document the difference and keep the decision on HOLD.
How do project location and standards affect acceptance?
The optical mechanism does not change by country, but the governing documents can. Where premises cabling standards apply, a North American project may cite ANSI/TIA-568.3-E. An international customer-premises project may cite ISO/IEC 11801-1, while ISO/IEC 11801-5 addresses data-center premises. Telecom operators, utilities, authorities and contracts can add their own requirements.
Record the exact standard, edition, amendment, local adoption and order of precedence used by the project. Do not combine a component value, field-test method and acceptance limit taken from different specifications unless the design authority has approved that basis.
How should a fiber splitter mode mismatch be investigated?
A link may show optical power even when the assembly has not been approved for the intended service. Investigate the discrepancy in a controlled sequence:
- Freeze the proposed substitution. Record the part, affected path and reason for the change. A temporary troubleshooting connection is not an approved build.
- Preserve the last approved baseline, including its configuration, results and document revisions, before moving components.
- Trace every segment from transmitter to receiver, including splitter pigtails, adapters, splices, patch cords and deliberate transitions.
- Compare records before testing. If the project method permits sectional testing, change one variable at a time so the suspect element can be isolated.
- Define the test basis before collecting results. State wavelength, direction, relevant launch condition, reference planes, method, equipment and acceptance limit.
- Compare like with like. Keep device characterization, incoming inspection and installed-link acceptance as separate records.
- Assign PASS, HOLD or REJECT. Name the approving authority, the owner of each open item and the condition that will trigger another review.
Engineered legacy exceptions
A legacy multimode plant may be part of an explicitly engineered adaptation or conversion design. Treat that as a separate, documented system, not as evidence that arbitrary single-mode and multimode components can be mixed. The system owner should identify the adaptation element, supported topology, limits, test method and approval authority.
If those records are unavailable, the correct disposition is HOLD.
How should PASS, HOLD or REJECT be recorded?
| Disposition | Minimum meaning | Typical trigger | Required next action |
|---|---|---|---|
| PASS | The exact path, device and acceptance basis agree, and required results meet approved limits | all mandatory fields and evidence IDs are complete with authorized approval | release only the recorded configuration and revision |
| HOLD | Compatibility cannot yet be established | missing fiber identity, conflicting documents, unknown launch/reference condition, unavailable exact model record or pending test | assign an evidence owner and due condition; do not substitute or publish an approval claim |
| REJECT | The proposed configuration conflicts with an approved requirement or fails its applicable acceptance basis | documented mode/configuration mismatch, unapproved change or failed required result | select a different documented configuration or obtain a formal system redesign |
PASS is not transferable to a different port map, fiber, wavelength, package, order code or document revision unless the approving authority has explicitly included that change.
Who owns each part of the release decision?
Compatibility approval is shared work. A complete supplier reply can close device-document gaps, but it cannot approve the installed network on behalf of the project authority.
| Role | Evidence or decision owned | What the role cannot establish alone |
|---|---|---|
| System or design authority | intended topology, active interfaces, wavelengths, governing specifications, limits and approved exceptions | delivered-item identity or field-test execution |
| Supplier or manufacturer | exact order code, controlled product document, declared construction, applicable model limits and required traceability | site conditions, installed-path acceptance or project approval |
| Installer or test team | as-built path, reference setup, launch and receive conditions, instrument record and measured results | undocumented product construction or an unapproved design change |
| QA or commissioning authority | evidence completeness, deviation status and final disposition under the project process | a technical waiver that exceeds delegated authority |
| Procurement | order, revision, lot and substitution control; ownership and due dates for missing evidence | optical compatibility based on price, availability or matching appearance |
Name the accountable approval authority in the release record. If two roles disagree or an owner is absent, retain HOLD until the project process resolves the conflict.
Fiber splitter mode compatibility release record
Use this fiber splitter compatibility checklist in the project submittal, inspection plan or technical inquiry. Replace every placeholder with a source-backed value; do not turn "unknown" into an inferred answer.
| Record field | Project entry | Evidence ID / revision | Status | Owner / action |
|---|---|---|---|---|
| Project, path ID and topology position | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Transmitter and optical interface | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Receiver and optical interface | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Operating wavelength(s) and direction(s) | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Installed fiber designation by segment | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Splitter manufacturer and complete order code | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Splitter internal/pigtail fiber declaration | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Port map and power-distribution requirement | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Connector/splice interfaces and polish | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Component specification/test basis | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Installed-path test method and edition | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Multimode launch condition, if applicable | [enter/N/A] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Reference planes, leads and direction | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Acceptance limits and source | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Instrument ID and calibration status | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Test result record | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Open deviations or engineered exceptions | [enter/none] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Approved by and approval date | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
| Re-test/review trigger | [enter] | [enter] | [PASS/HOLD/REJECT] | [enter] |
The overall disposition cannot be more favorable than an unresolved mandatory field. If one required row is HOLD, the configuration remains HOLD.
What supplier documents are needed for fiber splitter approval?
Start with the completed release record. Ask only for the evidence needed to close its open fields:
- controlled order-code definition and drawing for the exact assembly;
- declared internal and pigtail fiber;
- supported wavelength and direction conditions;
- port map and required power-distribution data;
- applicable component limits and test basis;
- model-specific test report or certificate only when required and available;
- sample, first-article or lot verification plan when required by the contract;
- document revision, order acknowledgement and traceability fields required by the project;
- written evaluation of any proposed deviation or substitution.
Keep price, quantity, delivery and shipping questions in the commercial inquiry. They do not resolve optical compatibility.
When should a sample or lot be tested?
A sample should verify a defined configuration, not compensate for an undefined requirement. Before testing, freeze the order code, drawing revision, internal and pigtail fiber, connector or splice interfaces, port map, wavelengths, method and acceptance limits. If the contract requires first-article or lot testing, record the sample or lot identity and the scope of approval. A passing result does not authorize an unreviewed production change.
How should a supplier's compatibility response be reviewed?
A usable reply closes specific HOLD items and ties each answer to the proposed assembly. General reassurance does not change the disposition.
| Response element | Usable for review | Keep on HOLD when |
|---|---|---|
| Item identity | manufacturer, complete order code, drawing or datasheet number and revision match the offered item | only a family name, photograph or nearby model is supplied |
| Fiber and interfaces | internal/pigtail fiber, connector or splice interface, polish and port map are declared separately | the reply says only "SM/MM compatible" or relies on connector appearance |
| Operating scope | wavelength, direction and application conditions are stated for the exact assembly | the reply says "works" without defining the conditions |
| Test evidence | any required record identifies the tested item, method, wavelength, reference basis, result and applicable limit | a screenshot, certificate or report cannot be tied to the offered configuration |
| Deviation control | differences from the approved baseline and any required requalification are explicit | the replacement is called "equivalent" without a documented comparison |
Move from compatibility review to a procurement-ready inquiry
Compatibility review is one part of procurement, not the entire buying process. Use the following handoff so that product education, technical release and commercial evaluation remain separate decisions.
| Procurement stage | Decision or output | Use this page or route | Control before moving forward |
|---|---|---|---|
| 1. Recognize the problem | identify a suspected mismatch, undocumented device or proposed substitution | five-layer evidence chain and 90-second triage | state the exact path and unresolved condition; do not begin with a generic product request |
| 2. Understand the product type | establish the required technology, topology, ratio and package family | Fiber Optic Splitter Types and Fiber Splitter Selection Guide | complete the design choice before treating mode compatibility as the remaining question |
| 3. Define the application | record topology position, active interfaces, directions, wavelengths and installation context | application fields in the evidence chain; use FTTx Solution or Data Center Solutions for architecture | confirm that a passive splitter is the approved function for the identified path |
| 4. Confirm technical requirements | freeze the complete order code or requirement, fiber, port map, interfaces, package, wavelength scope and acceptance basis | release record | mark every mandatory field PASS, HOLD or REJECT and name the source |
| 5. Compare supplier responses | compare like-for-like evidence, not reassurance or a nearby model | supplier-response matrix | issue one frozen requirement and one document list to every supplier |
| 6. Evaluate price and delivery | compare commercial offers for the same approved configuration | fiber splitter product center or written quotation | keep quantity, destination, schedule, packaging, documents and commercial terms tied to the exact configuration; price or availability cannot close a technical HOLD |
| 7. Request documents or a sample | obtain model-matched records and, when required, a defined sample or first article | supplier-document and sample sections | identify the model, revision, sample scope, method and acceptance limits before testing |
| 8. Verify quality evidence | confirm that the submitted test record is traceable and comparable with the approved basis | component/link test and loss-comparability sections | verify item identity, method, wavelength, reference basis, result, limit and instrument record |
| 9. Start the inquiry | send a reviewable technical package rather than a general compatibility question | Contact BWNFiber | include the completed record, exact documents and named HOLD items |
| 10. Release the order or project discussion | carry the approved configuration into the quotation, order acknowledgement and project record | project authority plus the commercial owner | resolve deviations in writing; any controlled change triggers the applicable review before shipment or installation |
For a BWNFiber request, the working rule is simple: document first, test under the approved method, and release only the recorded configuration. Submit one frozen requirement for technical review. Once that requirement is complete, quantity, destination, schedule, packaging and required documents can move into the sample or quotation discussion without weakening the compatibility record.
When does a customized splitter require a new compatibility review?
Reopen the review when customization changes the topology, split ratio or port map; internal or pigtail fiber; connector, polish or splice interface; package or cable exit where routing is affected; wavelength scope; optical limits; complete order code; or controlled drawing revision. The project authority decides whether the change needs document review only, a new sample, repeated testing or a full release. A supplier should not carry an earlier approval onto a changed configuration without that decision.
What should an international project add to the release record?
A sales region is not a technical specification. Use the following prompts to capture the actual site, contract and destination conditions. The optical compatibility principle does not change by country, but the package, pigtails, enclosure, accepted test method, required declarations, document language and delivery controls can.
| Market context | Conditions to confirm when applicable | Governing-document input | Procurement and delivery handoff |
|---|---|---|---|
| North America | premises or outside-plant location; exposed UV, wind, ice, temperature and enclosure conditions | named operator, authority, contract and adopted ANSI/TIA, IEC or other method with edition | required document language, inspection plan, destination, quantity and delivery window |
| Europe | indoor or outdoor location; project fire, environmental and enclosure requirements | applicable national, EN, IEC or ISO/IEC reference and the exact declaration or evidence required for the supplied item | destination-language documents, labeling, traceability, packing and any contract-required approval before shipment |
| Middle East | actual ambient temperature, dust, UV, coastal exposure and cabinet or closure conditions | national, operator and tender requirements plus the stated IEC or ITU reference and edition | submittal sequence, required approvals, packaging, destination and schedule assumptions |
| Southeast Asia | actual humidity, rainfall, flood, heat or coastal exposure and the installation enclosure | local authority or operator requirements plus the adopted IEC, ITU or project method | moisture protection during transport, inspection/sample requirements, labeling and delivery window |
| Latin America | site-specific altitude, coastal, tropical, urban or cold-region conditions | country, operator and contract requirements; record the adopted standard and edition rather than assuming one regional rule | required Spanish, Portuguese or other project-language documents, destination marking, packing and customs-document list |
| Africa | site-specific heat, dust, rainfall, coastal exposure, remote access and enclosure conditions | operator, tender, national and project requirements plus the adopted IEC or ITU reference | batch traceability, transport protection, inspection hold points, destination and project schedule |
Attach an International Project Addendum to the release record with the destination country and site, environmental and enclosure conditions, installation location, authority/operator/contract, adopted standard and edition, required document language, exact certification or declaration request, inspection or sample plan, labeling/packing/traceability requirements, and commercial delivery inputs. Do not mark an unspecified certification as available, and do not use quantity, shipping or schedule information as optical-compatibility evidence.
Worked example: a replacement that looks compatible but is not ready for release
This is an illustrative review, not a BWNFiber project result. Assume the installed-path record identifies the fiber and operating wavelengths, while the proposed replacement has the same connector family and package as the approved splitter. The quotation lists only a product family. It does not include the complete order code, controlled drawing or pigtail-fiber declaration.
| Evidence item | Review state | Effect on the decision |
|---|---|---|
| Installed fiber and wavelength records | available | establishes part of the system baseline |
| Connector family and package | appear to match | supports mechanical screening only |
| Exact replacement order code | missing | device identity remains unresolved |
| Controlled drawing and fiber declaration | missing | optical construction cannot be checked |
| Installed-path test | not yet performed | cannot cure the missing device identity |
The disposition is HOLD. Procurement should request the exact order-code definition and controlled drawing before arranging acceptance testing. If the returned documents conflict with the project requirement, reject the substitution or obtain a formal redesign. If they agree, continue with the approved test and review process.
What causes fiber splitter compatibility failures?
| Failure pattern | Why the evidence is insufficient | Disposition |
|---|---|---|
| Approval from connector appearance | connector family, polish and fiber mode are separate attributes | record each attribute from controlled evidence |
| Data copied from another model | a different split, package or pigtail configuration may not represent the offered order code | HOLD until the exact record is available |
| One wavelength used to approve all wavelengths | a result cannot be extended beyond its documented condition | record and evaluate every required wavelength |
| Multimode result without launch and reference conditions | the value may not be comparable with the approved acceptance basis | HOLD until the conditions are recoverable or the test is repeated correctly |
| Link-up, power reading or instrument output treated as approval | the observation does not contain the full change-control and acceptance basis | retain it as investigation evidence, then complete the required review |
Fiber splitter compatibility FAQ
Can a single-mode splitter be used on multimode fiber?
Do not approve that substitution by default. Review the complete system, every fiber segment, the exact splitter, wavelength conditions and an applicable test basis. If the design uses an engineered adaptation, require its controlled system record and approval.
Why can a suspected mismatch still show optical power?
A power reading only shows that some optical energy reached the measurement point. It does not establish the required coupling behavior, loss, margin, stability or repeatability for the intended service.
Does an LC or SC connector prove whether a splitter is single-mode or multimode?
No. LC and SC identify connector families. Record fiber mode, connector polish and the exact assembly declaration separately.
Does PLC or FBT determine the fiber mode?
No. PLC and FBT describe device technologies. The exact model document must declare the fiber and operating conditions of the selected assembly.
Which fiber designation should be recorded?
Use the controlled designation for every installed and device pigtail segment, such as G.652.D, G.657.A1/A2 or OM3/OM4/OM5. G.657 Category A compatibility with G.652.D does not replace exact cable, pigtail and splitter records. A G.657 fiber-category design radius is also not a universal finished-cable bend limit.
Why does launch condition matter in multimode splitter testing?
Different modal launches can produce different attenuation results. Record the applicable method and launch condition, such as the project's encircled-flux requirement, so the result can be interpreted and repeated.
Can a loss result at one wavelength approve another wavelength?
Not automatically. Use the wavelength scope and test requirements stated by the exact product and project documents.
What is the difference between component insertion loss and installed-link loss?
Component data characterizes the exact device under stated conditions. Installed-link loss covers the assembled path and its connections, splices, fiber and passive elements under the project test method. Both may be required, but they answer different questions.
What documents provide the strongest compatibility evidence?
Use the exact order code, controlled drawing or datasheet, fiber and interface schedule, wavelength plan, applicable test plan and traceable results. Record document IDs and revisions so later substitutions can be compared.
How should an unlabeled legacy splitter be handled?
Place it on HOLD. Preserve the baseline, trace the path, seek installation and purchasing records, and use an approved investigation method. Do not infer mode from color, package or a power reading.
What should trigger a HOLD?
Any unresolved mandatory field: unknown fiber, incomplete order code, conflicting revisions, unapproved substitution, undefined launch/reference conditions, missing limit source or pending required test.
When must compatibility be reviewed again?
Reopen the record when the active interface, fiber segment, splitter order code, port map, wavelength plan, package/pigtail construction, test method, acceptance limit or controlled document revision changes.
Technical notice: This guide is a decision-control reference, not a product specification, system approval, certification statement or performance guarantee. The project authority must approve the applicable design, documents, methods and limits.
Request a fiber splitter mode compatibility review
Complete the Mode Compatibility Release Record before contacting BWNFiber. Send the path ID, active interfaces, exact fiber designations, wavelengths, complete splitter order code or requirement, document revisions and open HOLD items. If a required field is unavailable, identify it as HOLD rather than replacing it with an assumption.
Submit the completed evidence package through Contact BWNFiber. BWNFiber can review the proposed order code, drawing and available model documents against the requirements you submit. This review does not replace the project's site acceptance or approval authority. For product discovery, use the FBT splitter category or fiber splitter product center.
If the configuration is already frozen and ready for commercial evaluation, use the product center's sample or quote route and include quantity, destination, required schedule, packaging and document pack. Keep the same configuration identity across the compatibility record, quotation, approved sample and order acknowledgement.
Technical references
- IEC 60875-1:2024, generic specification for non-wavelength-selective fiber-optic branching devices.
- IEC 60793-2-10:2019+AMD1:2022, sectional specification for category A1 multimode fibers.
- IEC 60794-1-2:2021, general guidance for optical-cable test procedures.
- IEC 60794-1-21:2015+AMD1:2020, mechanical test procedures for optical cables.
- IEC 61280-4-1:2019+AMD1:2021, installed multimode cabling attenuation measurement.
- IEC 61280-4-2:2024, installed single-mode cabling attenuation and optical return loss measurement.
- IEC TR 62614-2:2015, multimode launch conditions and encircled-flux background.
- ITU-T G.652 (08/2024), characteristics of a single-mode optical fiber and cable, including G.652.D.
- ITU-T G.657 (08/2024), characteristics of bending-loss-insensitive single-mode fiber, including A1 and A2.
- ITU-T L.102 (11/2025), aerial optical-cable application and ADSS context.
- ITU-T L.103 (08/2024), indoor optical-cable mechanical and environmental context.
- ANSI/TIA-568.3-E, optical-fiber cabling and component standard for North American premises projects.
- ISO/IEC 11801-1:2017 with applicable amendments, common requirements for generic cabling in customer premises.
- ISO/IEC 11801-5:2017, generic cabling requirements for data-center premises.
