Do not start a PLC splitter installation with the component. Start with the released documents. The splitter drawing, host enclosure, port map, and acceptance method must describe the same build. A module that is mounted and lit can still be impossible to hand over if nobody can identify its input, outputs, splice points, or test records later.
This page is for field execution after the PLC splitter design is approved. It does not select a split ratio, calculate a PON loss budget, or replace a model-specific enclosure manual. Use the splitter selection guide for design inputs, the splitter loss chart for budget work, the fiber optic splitter hub to browse product families, and the PLC splitter product category for published product options.
Quick answer
Use four controls: verify the released drawing and port map, prepare the host enclosure and fiber route, install the specified package, then verify the completed path and file its port-level record. Stop when the package, port identity, enclosure fit, or acceptance criterion conflicts with the release. Engineering must resolve that discrepancy before the network is connected.
The checklist treats the PLC splitter commissioning record as part of the job. The crew should not have to reconstruct it after leaving the site.
Buyer summary
Before comparing PLC splitter quotations, give every supplier the same released configuration: split arrangement, package, connector or splice interface, host enclosure, lead construction, port convention, quantity, destination, required documents, and commercial basis. Require the response to separate confirmed items, declared deviations, project approvals, and commercial conditions. A component datasheet or factory test record can support the supplied splitter, but it does not replace the installed-path test, as-built port map, exception record, or acceptance decision. Keep unresolved fields open until the responsible project authority or commercial owner closes them in writing.
Five decisions to retain from inquiry through handover
– Which released splitter configuration is being supplied and installed?
– Which host, interface, input, outputs, and downstream references belong to it?
– Which component and installed-path evidence must be produced?
– Who can approve a deviation, test criterion, retest, and final acceptance?
– Which price, quantity, document, packing, delivery, and validity conditions apply to the same technical line?
For a pre-installation document review, prepare the current splitter drawing, host enclosure reference, interface requirement, port-map convention, and acceptance-record requirement. Send that configuration to BWNFiber without asking either party to infer the package.
Gate 1: Release the installation package
Before the crew opens the enclosure, compare the physical item with the project release. A valid splitter can still be wrong for the site if its connector interface, package holder, port sequence, or test requirement differs from the drawing.
| Release item | Confirm before installation | Do not infer |
|---|---|---|
| Splitter identity | Model, split configuration, package, fiber/lead construction, connector or splice interface | That two similar labels are interchangeable |
| Receiving condition | Order/label identity, package damage, pigtail or connector condition, protective caps | That an intact outer carton proves the assembly is ready to install |
| Host location | Enclosure or rack position, tray/holder, cable entry and strain-relief method | That any ABS, cassette, LGX, or steel-tube package fits the host |
| Port map | Input identity, output numbering, destination or downstream cable reference | That color sequence alone proves the service mapping |
| Acceptance plan | Test method, working wavelengths, reference arrangement, limits, record format, reviewer | A generic loss or uniformity limit from another ratio or model |
Make a field pack before the enclosure is opened
The field pack should contain the drawing revision, the splitter and enclosure instructions, the port map, and the acceptance record template. Record the drawing revision used at the site. If the delivery label and release disagree, quarantine the discrepancy. Do not resolve it from memory. Confirm whether the assembly is connectorized, splice-only, or mixed, because the physical procedure changes with the interface.
Confirm the cable interface only when it reaches this enclosure
The splitter release does not select the feeder, distribution, or drop cable. If a cable enters this enclosure, the drawing must identify its fiber and cable type, route, and termination method. ITU-T G.652 covers conventional single-mode fiber such as G.652.D. ITU-T G.657 covers bend-insensitive single-mode fiber, including Category A fibers that are compliant with G.652. A G.657.A1 or G.657.A2 callout still does not supply the finished cable’s minimum bend radius.
Cable construction remains a separate route decision. For an aerial ADSS feeder, the route design must state the span, wind and ice loading where applicable, hardware, and installation method. For a drop cable using G.657.A fiber, the cable datasheet and building route still control bending, fastening, fire-performance, and jacket requirements. Loose-tube, tight-buffered, duct, direct-burial, armored, and drop constructions require different handling; the splitter article cannot select among them.
The same separation applies to cable properties. Fiber count must fit the splice, storage, and port plan. Tensile and crush requirements come from the route and cable specification. LSZH, flame performance, PE jacket, UV resistance, water protection, and rodent protection are different requirements and must not be treated as synonyms for “outdoor cable.” IEC 60794-1-1 provides a generic cable framework, not a blanket approval for a specific product.
Gate 2: Prepare the enclosure and fiber route
Prepare the route before exposing connector end faces or stripping fibers. The enclosure instructions and project drawing govern bend radius, tray capacity, cable-gland use, sealing, and mounting hardware. Keep input and output routes identifiable. Use the slack permitted by the host design, not improvised loops that later obscure a port or trap a fiber.
Check the interface, not just the dust cap
For connectorized interfaces, inspect, clean when required, then reinspect before mating. IEC 61300-3-35 defines end-face inspection procedures and criteria. The equipment and acceptance criteria still depend on the connector and project procedure. Keep caps on unused ports, but do not treat a cap as proof that an end face is clean.
For splice-only leads, use the specified stripping, cleaving, fusion-splicing, sleeve, and tray procedure for that fiber and enclosure. A splicer display is a process indicator. It is not the project acceptance record.
Match the control to the assembly type
| Build type | Installation control | Evidence to retain |
|---|---|---|
| Connectorized | Inspect, clean when required, reinspect, and mate only the mapped interfaces | Interface/inspection record and port identity |
| Splice-only | Follow the released preparation, splice-protection, and tray-routing procedure | Splice and route record tied to the splitter ID |
| Mixed | Apply both controls and identify the transition between the connectorized and spliced sections | Combined interface, splice, route, and port record |
The released design decides the interface. The field team applies the corresponding control.
Gate 3: Install the specified PLC splitter
The sequence below is package-neutral. A model manual may require a particular holder, latch, torque, seal, or route. Follow that instruction first.
- Confirm the specified tray, holder, cassette slot, or mounting point is ready. Support the package. Do not suspend it from pigtails or connectors.
- Verify the input against the port map before connecting or splicing. A boot color does not establish direction on its own.
- Complete one mapped output path at a time. For a connectorized assembly, inspect the interfaces and mate the identified connection. For a splice build, follow the released splice sequence and protect the joint before moving on.
- Route fiber through the specified guides, avoid pinch points, retain the allowed slack, and provide the specified strain relief. Recheck the route before a lid, tray, or panel is closed.
- Apply the site splitter ID so it reconciles with the drawing and port record. Add a subscriber assignment only when the project map confirms it.
When to stop rather than make it fit
Stop when a connector will not mate as specified, the assembly will not sit in the holder, a lead cannot follow the host instructions, a port number conflicts with the map, a seal cannot be restored, or a result fails the stated criterion. Do not reverse a port, change a connector type, or borrow an online limit to close the gap. Escalate it with the drawing revision and the physical discrepancy.
Gate 4: Verify and hand over the split point
Separate component checks from link checks
Component and link verification answer different questions. The component requirement checks the splitter against its own specification. ITU-T G.671 addresses transmission characteristics of optical components and subsystems, but does not supply a project-specific installation procedure or acceptance limit. The end-to-end test checks the completed cable plant, including the splitter, connectors, splices, and route. The Fiber Optic Association notes that PON splitter loss belongs in the link budget and that OTDR traces can document attenuation and loss events. The project procedure and test-equipment instructions determine methods and wavelengths, especially on a live network.
Here, component vs link testing is a scope distinction, not a choice between interchangeable tests. PLC splitter port mapping is complete only when each tested path matches the physical label, downstream reference, and splitter ID.
| Evidence | What it can answer | What it cannot decide by itself |
|---|---|---|
| Component attenuation result | Whether the passive component was measured against its specified method and limit | Whether the installed OLT-to-ONT path passes |
| Installed-path attenuation and optical return loss record | Whether the completed single-mode cable plant meets the approved link method and criterion | Whether every component was manufactured to its individual specification |
| OTDR trace | Event location, distance, loss and reflectance information within the method and instrument limits | Final acceptance when the project requires other measurements or directions |
| Connector end-face inspection | Whether contamination or defects meet the applicable inspection procedure | Attenuation, return loss, or end-to-end path acceptance |
IEC 61300-3-4 covers attenuation measurements for optical components. IEC 61280-4-2:2024 covers attenuation and optical return loss measurements for installed single-mode cabling plants, including plants with passive branching devices. The released acceptance plan still controls the required method, direction, wavelengths, uncertainty, limits, and network state.
Use the approved acceptance plan to complete the following handover record:
| Record | Minimum traceability | Owner to confirm |
|---|---|---|
| Installation identity | Site, enclosure/rack location, splitter ID, drawing revision, date | Field lead |
| Port map | Input reference; each active output and downstream reference | Project documentation owner |
| Physical review | Package secured, routes checked, seals/closures restored, unused interfaces protected | Installer / reviewer |
| Test evidence | Method, wavelengths, reference setup, measured records, equipment ID, accepted exceptions | Test lead |
| Handover | Open items, as-built revision, acceptance decision and named reviewer | Project authority |
Build a record that a later technician can use
File OTDR traces and optical-loss records under the same splitter ID used on the port map. A trace without a leg identifier is hard to use during a later fault investigation. On a live PON, do not introduce an instrument or wavelength unless the approved procedure confirms it is safe for the network state.
Log an exception before it becomes an as-built assumption
An exception is not a verbal workaround. If a released detail cannot be followed, record the affected splitter ID and port, drawing revision, observed condition, temporary network state, and the person authorized to decide the next action. Keep the item open until the revised drawing, approved disposition, or replacement work can be attached to the same record. This prevents a later technician from mistaking a field compromise for the released build.
| If this condition is found | Attach this to the record | Do not close the item until |
|---|---|---|
| Package or holder does not match the release | Photos or identification details, host location, drawing revision | Engineering or the document owner supplies an approved disposition |
| Port identity conflicts with the map | Input/output references and the affected downstream destination | The corrected map is issued and linked to the installation record |
| Test result cannot be evaluated against the plan | Test setup, result, equipment ID, and missing or conflicting criterion | The acceptance authority confirms the criterion and decision |
Worked exception example: a port-map conflict
Assume the released map assigns splitter SPL-07, output 12, to downstream cable D12, but the physical label at the enclosure shows output 11. This is an illustrative control example, not a BWNFiber project case. The installer should leave the disputed path unaccepted, record both identifiers and the drawing revision, attach a clear enclosure photo, and ask the document owner to issue a corrected map or disposition. Testing the path does not resolve the identity conflict: an optical pass cannot prove which output the project intended to connect. After the approved correction is issued, reconcile the physical label, port map, test filename, and as-built record before closure.
Before procurement release, turn the same fields into a technical clarification. Send BWNFiber the current configuration and required evidence list, and ask for each line to be returned as one of four states: confirmed for the quoted configuration, declared deviation, project approval required, or commercial condition. This request does not transfer engineering approval or installation acceptance to the supplier.
Five failures the handover record should prevent
| Failure | What it looks like later | Control at installation |
|---|---|---|
| The field crew did not have the current drawing | A valid splitter is in the wrong host position or port sequence | Release the drawing at the enclosure and record its revision |
| Interfaces were mated without inspection | A clean component inherits contamination at the connection | Use the specified inspection, cleaning, and reinspection procedure |
| A generic number replaced the project criterion | A path is accepted or rejected against the wrong ratio, grade, wavelength, or reference method | Use the accepted project plan |
| The enclosure closed before route review | Pinched fiber, missing strain relief, or an untraceable loop | Sign off the physical review before closure |
| Records were completed after the crew left | The port map has to be reconstructed | Enter each confirmed path during installation |
Prepare a project-based PLC splitter inquiry
Do not request a quotation using only a split ratio and quantity. A supplier needs enough detail to confirm the package, interface, host relationship, labeling, and document scope. Commercial inputs such as quantity, destination, response date, and price basis also need to be explicit. Mark unresolved fields as open.
Minimum RFQ inputs
Use this checklist to determine whether suppliers can respond to the same configuration. It does not replace the project’s engineering release.
| Buyer check | Ready only when | If not ready |
|---|---|---|
| Installation point | The host enclosure, rack, closure, or site reference is named | Mark the placement decision open |
| Package and interface | The required form factor and connectorized/splice interface are stated | Do not ask a supplier to assume a package |
| Port identity | Input, output convention, and downstream references are available | Attach the current port map or identify its owner |
| Technical authority | The drawing revision and acceptance-plan owner are identified | Request release before comparing responses |
| Evidence request | Required datasheet, drawing, test-record scope, labels, and packing documents are listed | Separate component documents from field acceptance evidence |
| Commercial request | Quantity, destination, requested response date, and desired price/delivery basis are stated | Ask for written clarification rather than an implied commitment |
| Pre-order verification | Required sample, first-article, drawing review, or document approval is named | Confirm availability, scope and acceptance criteria in writing |
| Exceptions | Open conditions and change-control owner are visible | Keep the inquiry conditional until they close |
What documents should a buyer request?
Request documents for the component and for the installed project separately. Depending on the released configuration, buyers may need a current datasheet, dimensional or package drawing, interface/pin or port identification, applicable enclosure instruction, declared test-record scope, packing/labeling record, and a written deviation list. The project acceptance plan, field test records, as-built port map, and acceptance decision belong to the installed split point; a factory component report does not replace them.
Treat the PLC splitter installation documentation as a controlled project set. Identify the revision, owner, affected splitter ID, and whether each record describes the supplied component or the installed link. Obtain written confirmation before treating a document, test record, certification, sample, delivery date, or capability as available for an order.
Common procurement mistakes
| Mistake | Why it creates risk | Better buyer action |
|---|---|---|
| Asking for a ratio without an installation point | The package, holder, interface, and port sequence may remain undefined | Tie every line to a host/enclosure or project reference |
| Comparing quotations with different interfaces or document scopes | An apparent price difference may describe different configurations | Normalize the released inputs and ask suppliers to list deviations |
| Treating a component report as an installed-network acceptance record | It does not prove the final route, connectors, splices, or mapping | Keep component evidence and field acceptance records separate |
| Assuming a sample, delivery date, MOQ, OEM/ODM option, or test service | These are commercial or operational commitments, not generic article facts | Obtain BWNFiber’s written confirmation for the exact project and order |
Normalize supplier responses before comparing price
A technically lower-priced quotation is not comparable when it omits a required interface, drawing, label convention, or test-record scope. Use a deviation-led comparison before evaluating commercial terms.
| Comparison field | Comparable response | Hold for clarification |
|---|---|---|
| Configuration | Same released split configuration, package, interface, lead construction, host reference, and port convention | Supplier substitutes or leaves a field open without a written deviation |
| Evidence | Requested datasheet, drawing, identification, and component test-record scope are explicitly included or excluded | A generic certificate or sample report is presented as proof for the quoted configuration |
| Exceptions | Every departure from the inquiry is listed with its effect and required approval | The response relies on an unstated equivalent, assumed enclosure fit, or inferred acceptance limit |
| Commercial basis | Quantity, destination, price basis, validity, and delivery terms refer to the same technical line | Price or lead time is compared before technical scope is normalized |
This table is a bid-normalization control, not a claim that BWNFiber supplies every document or service listed. Confirm the exact deliverables in the written quotation and approved order documents.
When a custom configuration needs engineering review
Ask for an engineering review when the required package, interface, labeling, port map, enclosure relationship, document scope, or acceptance method differs from a published option. Do not describe a custom configuration as available until BWNFiber confirms the drawing, BOM, test scope, commercial terms, and delivery conditions in writing.
Set international project inputs by country, not region labels
North America, Europe, the Middle East, Southeast Asia, Latin America, and Africa are not single technical or commercial specifications. A region name cannot select a package, cable, test method, certificate, label, Incoterm, packing method, or delivery date. Use the destination country, named authority, site conditions, tender documents, and written commercial terms.
| Market context | Confirm with the project or buyer | Do not assume from the region name |
|---|---|---|
| North America | Country and local jurisdiction, utility or operator specification, indoor/outdoor location, document language, labeling and receiving requirements | One code set, enclosure rating, connector, approval, price basis or lead time applies everywhere |
| Europe | Destination country, buyer-specified standards and declarations, installation environment, document language, packaging/labeling and importer responsibilities | A regional rule automatically proves the exact quoted product is compliant |
| Middle East | Country and project authority, indoor/outdoor exposure, heat, dust, UV, coastal conditions where applicable, document language and delivery basis | Every project requires the same temperature range, certificate, bilingual file or packing method |
| Southeast Asia | Country/operator requirements, humidity, rainfall, flooding, UV or coastal exposure where applicable, site access, document language and import documents | A tropical label replaces the exact enclosure, sealing, material or test requirement |
| Latin America | Destination country, utility/tender specification, altitude, coastal or tropical exposure where applicable, Spanish/Portuguese document needs and import labeling | One language, customs process, connector convention or delivery cycle applies to the whole region |
| Africa | Destination country and authority, route-specific heat, dust, UV, rainfall, flooding or coastal exposure, remote-site logistics where applicable, document language and receiving responsibility | Climate, certification, logistics, payment or procurement practice can be inferred continent-wide |
For every destination, request written confirmation of the exact configuration, required documents, inspection or sample scope, packaging and labels, delivery basis, requested date, and declared deviations. OEM/ODM, batch capacity, export experience, certification, testing, samples, MOQ, price, packing and lead time remain commercial or capability claims that BWNFiber must confirm for the quoted project.
FAQ
How do you install a PLC splitter?
Start with the released splitter drawing, enclosure manual, port map, and acceptance plan. Secure the approved package, establish the input identity, complete each mapped output without stressing fibers or contaminating interfaces, then verify the completed path and file the port-level record.
Is a pre-terminated PLC splitter installed the same way as a splice-only splitter?
No. Both need released port mapping, suitable mounting, route control, and verification. A connectorized build requires controlled inspection and mating; a splice-only build requires the approved splicing and tray procedure. The specific package manual governs both.
Do I need to test every splitter output?
Follow the accepted project method and the component specification. The handover record should make clear which paths were tested, with what setup and criterion. Do not substitute a sample test for a stated per-port requirement.
Can an OTDR alone approve a splitter installation?
No. OTDR traces help locate and document events, but they do not replace the approved component or end-to-end loss test. PON splitters also make OTDR traces direction- and network-state-dependent.
What should be included in a PLC splitter handover package?
The splitter and site identity, drawing revision, port map, physical-review record, test method and results, equipment identifiers, exceptions, as-built information, and the named acceptance authority.
What should be checked before installing a PLC splitter?
Confirm the splitter model, package, host enclosure, interface, port map, drawing revision, and required acceptance record. If any physical item conflicts with the release, stop before mounting or connecting it.
Can a PLC splitter be installed backwards?
Do not determine direction from boot or fiber color alone. Match the input and outputs to the product marking and released port map; if those sources conflict, quarantine the discrepancy for engineering review.
How do you prevent connector contamination during installation?
Keep unused interfaces protected and follow the approved inspect-clean-reinspect procedure before mating. A fitted dust cap protects the interface during handling, but it does not prove that the end face is clean or optically acceptable.
What if the splitter package does not fit the enclosure holder?
Do not force the package, modify the holder, or improvise the fiber route. Record the splitter and host identities, photograph or describe the conflict, and obtain an approved disposition or corrected hardware.
How should PLC splitter ports be labeled?
Use the project splitter ID and released port-map convention. Every active output should reconcile its physical label, downstream reference, and test record without relying on color alone.
What should an EPC contractor send with a PLC splitter inquiry?
Send the installation point, host enclosure, released package and interface, port-map convention, quantity, destination, drawing revision, and required component and field documents. Mark unresolved fields as open rather than allowing a supplier to assume them.
When should a field team stop and escalate?
Stop when the model, package fit, interface, port identity, seal, route, or acceptance criterion conflicts with the released documents. Resume only after the responsible project authority issues a documented disposition.
Request a controlled installation review
For an approved FTTH design, send BWNFiber the splitter drawing or configuration sheet, host enclosure, required interface, port-map convention, quantity, destination, and test-document requirement with your inquiry. Ask for a written response that distinguishes confirmed configuration details, declared deviations, items requiring project approval, and commercial conditions. The useful outcome is a response that can be checked against one released configuration, not a generic product recommendation. The project team retains final engineering approval, site procedure, and acceptance authority. In-service fault isolation is outside this page’s scope.
References
- Fiber Optic Association: Testing FTTH
- Fiber Optic Association: Fiber Optic Splitters for PONs
- IEC 61300-3-35:2022: Visual inspection of fibre optic connectors and fibre-stub transceivers
- ITU-T G.652: Characteristics of a single-mode optical fibre and cable
- ITU-T G.657: Characteristics of a bending-loss insensitive single-mode optical fibre and cable
- IEC 60794-1-1:2023: Optical fibre cables, generic specification
- ITU-T G.671: Transmission characteristics of optical components and subsystems
- IEC 61300-3-4:2023: Attenuation measurement of optical components
- IEC 61280-4-2:2024: Installed single-mode cabling attenuation and optical return loss measurements
Disclaimer: figures and settings are reference only, not a guarantee. Model-specific dimensions, bend limits, package mounting, optical limits, test wavelengths, and acceptance thresholds must be confirmed against the released design, current product datasheet, enclosure instructions, and project procedure before publication.
Last reviewed: 2026-09-30. Publication still requires a named FTTH technical reviewer.
Related product category: Bare Fiber PLC Splitters.
