By BWNFiber | Evidence reviewed: 6 September 2026 | Engineering review required before publication
A PLC splitter splice-tray capacity calculation determines whether a selected splitter can be fusion-spliced, routed, protected, and serviced inside a selected tray and host. For a fully fusion-spliced 1×N device, start with N + 1 joints; for 2×N, start with N + 2. The count does not prove physical fit.
Procurement summary: Release a PLC splitter and splice-tray combination only when five records agree: the current splitter and host identities, the splice-position calculation, the populated physical-fit review, the mapped technical evidence, and the commercial offer. A nominal "24-core" tray or generic compatibility statement is insufficient. Confirm holder and sleeve capacity, body footprint, fiber routes, service movement, optical acceptance plan, permitted deviations, quantity, delivery basis, and document revision. If any drawing, route, test requirement, or approval owner is missing, keep the configuration on hold and request the specific evidence instead of accepting an unqualified yes-or-no answer in writing.
Use the worksheet only after the split ratio and PON architecture have been set. If those decisions are still open, start with the GPON splitter selection guide and the splitter loss and link-budget guide. The result here is a pass, hold, or redesign decision for one defined splitter, tray, and host combination.
If the model numbers are known but either current drawing is missing, ask BWNFiber for the model-level document list before calculating. That request identifies the evidence needed for review; it is not a compatibility approval.
30-second capacity release screen
Use this screen before reading the detailed method:
| Decision | Release condition | Stop signal |
|---|---|---|
| Identity | Splitter, tray, holder, host, topology, package, termination, and revisions are fixed | A family name, ratio, or catalogue image is standing in for a model record |
| Holder arithmetic | Every spliced input, spliced output, other splice, and named reserve position fits the usable holder arrangement | The calculation uses port count or nominal tray capacity instead of the installed holder |
| Physical fit | Body, sleeves, transitions, routes, labels, cover, hinge, tray stack, and service movement pass together | Only an empty-tray or body-only fit has been shown |
| Evidence | Current drawings, instructions, route overlay, mock-up or sample result, optical plan, and accountable approvals can be mapped to the configuration | A generic datasheet, certificate, or verbal compatibility statement cannot be mapped to the offered item |
| Commercial comparison | Price and schedule use the same technical revision, permitted deviations, document scope, quantity, and delivery basis | A cheaper or faster offer changes the package, termination, evidence, or acceptance scope |
A pass in one row does not close another. Any stop signal leaves the configuration on hold until the missing evidence is supplied or the design is revised.
What counts toward PLC splitter splice-tray capacity?
A nominal splice count is only one of four capacity checks. All four must pass for the proposed assembly.
| Capacity check | What to examine | Evidence needed | Hold the design when |
|---|---|---|---|
| Splice-holder capacity | Fusion or mechanical splices, sleeve dimensions, holder slots, layers, and removal access | Tray drawing, holder data, splice method, and sleeve specification | The required joints cannot be loaded and removed in the specified holder arrangement |
| Splitter-body accommodation | Body footprint, orientation, retention, fiber exits, and transition protection | Splitter drawing plus tray or host drawing | The body obstructs sleeves, routes, labels, latches, or service access |
| Fiber routing and storage | Separate input and output paths, crossovers, service slack, unused outputs, and identification | Route overlay and host routing instructions | A path creates a pinch point, uncontrolled bend, compressed loop, or blocked label |
| Host movement and closure | Cover clearance, hinge sweep, tray pivot, stacking, adjacent trays, and cable entries | Populated mock-up and host instructions | Normal opening, stacking, or closing transfers load to a fiber or component |
Enclosure fiber count, nominal tray splice count, and usable build capacity belong in separate fields. Before calculating, obtain the current model drawing from the bare fiber PLC splitter product page and identify the intended host on the fiber splice tray page. Catalogue labels alone cannot resolve the fit check.
How many splice positions does a PLC splitter require?
The count must follow the fiber paths assigned to splicing in this tray. Splitter ratio, subscriber-port count, and enclosure headline capacity are different quantities.
Required holder positions
= spliced inputs
+ spliced outputs
+ other assigned splices
+ named reserve positions
Fully fusion-spliced 1×N splitter: N + 1 base splices
Fully fusion-spliced 2×N splitter: N + 2 base splices
These formulas are engineering arithmetic, not values quoted from an IEC or ITU-T standard. They apply when every identified input and all N outputs are fusion-spliced in the planned assembly.
For several splitters in one tray or tray stack, count each device separately and add the results:
Base splitter splices for k devices
= sum of (spliced inputs for device i + spliced outputs for device i)
| Planned splitter arrangement | Transparent calculation | Base splitter splices | What the number does not prove |
|---|---|---|---|
| One fully fusion-spliced 1×8 | 1 + 8 | 9 | Tray compatibility or route capacity |
| One fully fusion-spliced 1×16 | 1 + 16 | 17 | That a nominal 24-splice tray is usable for the populated build |
| One fully fusion-spliced 1×32 | 1 + 32 | 33 | That one tray or one host can accommodate the device and all routes |
| Two independent fully fusion-spliced 1×16 splitters | 2 × (1 + 16) | 34 | That the two bodies, 34 sleeves, routes, and movement envelope fit together |
| One fully fusion-spliced 2×16 splitter | 2 + 16 | 18 | That both inputs are actually spliced in the proposed assembly |
| Connectorized or partly activated arrangement | Count only the paths physically spliced in this tray | Configuration-specific | Adapters, parking, stored leads, identification, and service access still consume other capacity |
Do not confuse two separate 1×16 splitters with one 2×16 splitter. The first arrangement has two inputs and 32 outputs, so it contributes 34 base splices when every lead is spliced. A 2×16 device has two inputs and 16 outputs, so it contributes 18. Neither count authorizes a tray model; it only establishes the first input to the four-gate fit review.
Worked screening example: A fully fusion-spliced 1×16 splitter contributes 17 splices. If the same tray also carries two pass-through splices and two named restoration positions, required holder capacity is 17 + 2 + 2 = 21. A tray advertised for 24 splices appears to have three unallocated positions, but it remains on hold until the body, sleeves, routes, and movement checks pass.
An arbitrary reserve percentage is not a defensible design input. Translate the operator's growth, restoration, and maintenance policy into named holder positions, route space, spare sleeves, or reserved tray locations.
Why port count, adapter count, and splice count differ
A subscriber port is a service interface. An adapter is a connector interface. A splice is a protected fiber joint. A connectorized output may bypass the splice holder in this tray, but it still needs an adapter or parking position, a controlled route, identification, and service access. A pass-through or repair splice creates the opposite case: it occupies a holder position without adding a subscriber port.
How should unused outputs be counted?
An unspliced output uses no splice-protection position. It still needs a defined storage path, protection, identification, and future access. Show whether each output is cut, parked, connectorized, stored in this tray, or routed elsewhere on the port map and route overlay.
How do you compare nominal and usable tray capacity?
Nominal capacity is useful for shortlisting. It becomes a release figure only after the selected holder, sleeve, splitter body, routes, movement envelope, and work sequence have been checked as one assembly.
| Published or requested field | What remains unknown | Check before release |
|---|---|---|
| "12-core" or "24-core" tray | Installed holder, sleeve method, splitter space, and access | Confirm usable slots, compatible sleeves, layer arrangement, and removal access |
| "Supports one PLC splitter" | Body dimensions, topology, exits, and retention | Match the model drawing to the specified holder or retention feature |
| "Fits a 1×8/1×16 splitter" | Package geometry and lead construction | Check body length, width, height, exit direction, fiber construction, and route plan |
| Enclosure maximum fiber count | Usable arrangement of the selected tray and stack | Review tray position, neighbors, hinge path, cover, entries, and reserve storage |
| Empty-tray fit | Sleeves, loops, labels, and maintenance handling | Populate the proposed build and exercise the cover and tray movement |
A single controlled worksheet is easier to review than a trail of separate emails.
| Worksheet field | Required entry | Source | Pass / hold |
|---|---|---|---|
| Project context | Country or jurisdiction, governing specification, indoor or outdoor host, mounting and access conditions | Project requirement and site plan | |
| Splitter identity | Manufacturer, model, revision, topology, package, fiber designation, coating or buffer construction, lead length, and termination | Current splitter drawing and data record | |
| Host identity | Closure, box, terminal, panel, or ODF; tray model; tray position; installed accessories | Current host drawing and instructions | |
| Holder demand | Spliced inputs, spliced outputs, other project splices, and reserve positions | Port map and splice schedule | |
| Holder arrangement | Holder type, usable slots, compatible sleeve, layers, and removal access | Tray drawing or reviewed mock-up | |
| Body accommodation | Footprint, orientation, retention, exits, and transition protection | Drawing overlay | |
| Routing and storage | Input path, output paths, service slack, crossovers, unused outputs, and labels | Route overlay | |
| Movement envelope | Cover, latch, hinge, tray pivot, stack, and neighboring components | Populated mock-up | |
| Decision | Pass, redesign, or evidence missing | Accountable reviewer |
Any row with an absent, out-of-revision, or conflicting source stays on hold. A catalogue image, ratio label, or verbal assurance cannot clear it.
Technical-review checkpoint: Use each open worksheet row as a precise consultation question. State the missing drawing, dimension, route decision, test record, or approval owner instead of asking whether the combination is "standard compatible."
How do you verify splitter-body and fiber-route fit?
Start the mechanical check by placing the splitter drawing at scale on the tray and host drawing. Include the retention feature, input and output exits, transition protection, sleeve bank, routes, service loops, labels, cover, latch, hinge, tray pivot, and adjacent trays. The purpose is to expose interference before a sample is built.
Input and output leads need separate route lengths:
Minimum planned lead length
= controlled route from body exit to splice point
+ specified service slack
+ specified preparation allowance
This expression is a planning method, not a universal pigtail length. Take the slack and preparation allowances from the project work instruction. A short lead can load the transition or force a direct path; an excessive lead can cross working areas, hide identification, or form an unserviceable coil.
Control the fiber transition
The point where a lead exits the splitter body deserves its own interface detail. The drawing should show support, movement control, and the route into the tray. The compact bare package is useful only when the host protects the body and transition without an improvised restraint.
Match the fiber designation to the route
Fiber designation and lead construction are separate inputs. ITU-T G.657 (08/2024) defines bending-loss-insensitive single-mode fiber, while ITU-T G.652 (08/2024) defines characteristics for single-mode optical fiber and cable. The current G.657 edition states that category A is a subset of G.652.D. It lists a minimum design radius of 10 mm for G.657.A1 and 7.5 mm for G.657.A2.
| Fiber designation on the ordered item | Relationship that matters here | Tray decision |
|---|---|---|
| G.652.D | Single-mode fiber covered by G.652; it does not inherit the G.657.A1/A2 bend values | Use the model-specific lead construction and permitted route; do not copy an A1 or A2 radius |
| G.657.A1 | Category A fiber compliant with G.652.D, with improved macrobending performance; G.657 (08/2024) gives a 10 mm minimum design radius | Treat 10 mm as a fiber-category design input, then check coating or buffer construction and host instructions |
| G.657.A2 | Category A fiber compliant with G.652.D, with a 7.5 mm minimum design radius in G.657 (08/2024) | Treat 7.5 mm as a fiber-category design input, then check coating or buffer construction and host instructions |
| Unstated or custom designation | Bend performance and interconnection assumptions are not established | Keep the route on hold until the model record identifies the fiber and construction |
The values above are not universal tray radii. They do not override the splitter manufacturer's lead construction, coating or buffer limits, reliability instructions, or the host's routing geometry.
Simulate the final movement envelope
An empty tray can conceal interference. A useful mock-up includes the intended holder, sleeves, body, routes, slack, labels, and neighboring trays. Move the hinge and stack through their service range and close the cover. The design stays on hold if a fiber is pinched, dragged across an edge, compressed, or loaded when another tray moves.
For an outdoor closure or distribution node, the host supplies cable entry, sealing, mounting, and environmental protection. The bare splitter does not inherit those properties. Use the fiber optic splice closure range to identify a candidate, then review the selected model and installed configuration.
Review the tray through its service lifecycle
For an FTTH distribution box or an outdoor ODN closure, the following is a pre-release verification scenario, not a customer case. An ISP or EPC team can adapt these review states to its approved host and work method. Reproduce the states that the installed tray will encounter instead of approving one static photograph.
| Review state | What to reproduce | Hold point |
|---|---|---|
| Initial installation | Body placement, sleeve loading and removal, splicer access, lead routing, and label placement | A technician must disturb another fiber or remove an unrelated component to complete the splice |
| Normal closure operation | Cover, latch, hinge, tray stack, cable entry, and the installed service loops | Opening or closing transfers load to a lead, transition, sleeve, or splitter body |
| Later maintenance | Access to one named output, adjacent-tray movement, reserve retrieval, label reading, and sleeve removal | The target path cannot be identified and serviced without moving an uncontrolled loop |
Jurisdiction does not change the splice arithmetic, but it can change the governing enclosure, fire, environmental, documentation, and acceptance requirements. Record the project country or jurisdiction and the controlling specification rather than assigning a generic regional rule.
What is the pre-installation go/no-go process?
- Freeze the configuration. Record the project jurisdiction and governing specification, then capture the splitter topology, package, fiber designation, lead construction, termination, model, and revision together with the host, tray position, splice method, sleeve, and acceptance plan.
- Calculate holder demand. Count spliced inputs, spliced outputs, other assigned splices, and named reserve positions.
- Overlay the drawings. Put the body, exits, sleeves, routes, labels, cover, hinge, and tray stack on one controlled drawing.
- Build the populated mock-up. Use a representative splitter sample when drawings cannot close the geometry. Include the intended holder, sleeves, route lengths, labels, cover, and neighboring trays.
- Close every hold. Change the tray allocation, splitter package, route, lead length, holder, or host through a documented design revision.
- Release the work pack. Issue the reviewed drawings, port map, splice schedule, routing plan, model instructions, test plan, and handover form.
After release, the installer should receive decisions rather than unresolved design choices. The work pack should state the retention method, handling limits, splice acceptance criteria, and host settings that apply to the selected parts.
Keep optical acceptance separate from capacity approval
Mechanical release and optical acceptance answer different questions. The first confirms that the assembly can be built, closed, opened, and serviced under the defined constraints. The second evaluates component or installed-path performance under a stated test method.
| Evidence layer | Supported conclusion | Record these fields | Outside its scope |
|---|---|---|---|
| Splitter component record | Model-specific attenuation, uniformity, return loss, PDL, directivity, wavelength range, or qualification when documented | Model, revision, ports, method, wavelengths, direction, reference planes, equipment, limits, results, and date | Tray routing, splice quality, connector condition, host fit, and as-built route loss |
| Installed-path acceptance | Performance of the completed path under the project procedure | Route ID, splitter port, method, wavelengths, direction, reference planes, equipment, limits, result, retest, and deviation status | Factory compliance outside that method or performance of another configuration |
IEC 60875-1:2024 gives generic requirements for passive non-wavelength-selective branching devices. ITU-T G.671 (05/2025) supplies definitions and transmission-characteristic context for optical components. These documents define scope; they do not certify a BWNFiber model or its fit in a host.
For measurement context, IEC 61300-3-4:2023 addresses attenuation, IEC 61300-3-6:2008 addresses return loss, and IEC 61300-3-2:2009 addresses polarization-dependent loss for single-mode devices. The acceptance plan must still define method, wavelengths, directions, reference planes, equipment, limits, and disposition.
Keep the quantities distinct. Fiber attenuation coefficient is normally expressed per unit length, while splitter or installed-path attenuation and insertion loss are measured across stated ports and reference planes. A number without the measurand, unit, wavelength, direction, method, and reference planes is not an acceptance limit.
An OTDR trace can support event location and route analysis. Treat it as proof of per-port component insertion loss only when the approved procedure defines that use. A light source and power meter, or another method with controlled reference planes, may be required by the project.
Which capacity failures should stop the design?
| Failure mode | What the team may see | Missed check | Required disposition |
|---|---|---|---|
| Ratio used as splice count | The holder runs out of positions during splicing | Inputs, other assigned splices, or reserves were omitted | Recalculate from the port map and splice schedule |
| Nominal count treated as usable capacity | Sleeves fit only when stacked or block removal access | Holder, sleeve, or layer constraints were skipped | Define a compatible holder arrangement or select another tray |
| Body fits only in an empty tray | Routes cross sleeves or the cover presses the body | The populated footprint and movement envelope were omitted | Redesign the layout and repeat the mock-up |
| Unused outputs ignored | Unlabeled leads are compressed or cannot be located later | Storage and route demand were treated as zero | Add protection, identification, storage, and access to the overlay |
| One pigtail length applied to every route | Leads are taut or coiled across working areas | Input and output paths were not measured separately | Measure each route class and revise the ordered lengths |
| Bare body held by an improvised method | The body moves or a transition carries load | No reviewed retention and transition detail exists | Obtain engineering approval or change the package or host |
| Enclosure capacity taken from a headline number | The tray stack or cable-entry arrangement blocks service | Whole-host constraints were not reviewed | Recheck installed trays, entries, accessories, and movement |
| Physical fit accepted as optical evidence | The assembly closes but lacks a test baseline | Mechanical and optical decisions were conflated | Execute the project test plan and retain the result by path |
If the tray cannot provide controlled retention, transition protection, and service access, consider a blockless mini PLC splitter or another protected package. Record the package change as a design revision and repeat the capacity review.
What should the released capacity record contain?
Once the design passes, promote the completed worksheet into the release record instead of creating a second, inconsistent file. Procurement, installation, acceptance, and maintenance then work from the same revision.
| Record block | Required fields |
|---|---|
| Controlled identity | Splitter and host manufacturer, model, revision, topology, package, lead construction, termination, tray position, holder, accessories, port map, and serial or lot identifier when applicable |
| Design basis | Splice and reserve counts, usable holder slots, sleeve method, tray allocation, drawing references, body retention, transitions, routes, labels, cover, hinge, stack, and mock-up result |
| Acceptance basis | PON budget reference, component and installed-path limits, methods, wavelengths, directions, reference planes, and equipment identifiers |
| As-built result | Result by path and port, date, operator, rework or retest status, and linked trace or worksheet filename |
| Deviations and release | Deviation, affected ports, corrective action, technical reviewer, record revision, and release date |
What procurement should lock before comparing offers
Price comparison becomes meaningful only when every offer refers to the same revision-controlled configuration. A comparable response identifies the splitter and host revisions, lead construction and termination, holder, sleeve and supplied accessories, declared deviations, available drawings and test records, quantity, packaging, and offered schedule. An offer stays on hold if it relies on phrases such as "standard tray compatible" without a model-specific drawing, or if the package changes without another fit review.
| Bid-comparison field | Comparable response | Hold or re-review trigger |
|---|---|---|
| Controlled identity | Named splitter, tray, host and accessory models with revisions | Family name only, missing revision, or a substituted package |
| Fiber and termination | Input/output lead construction, designation, length and connector or splice state | "Standard pigtail" with no model record or port map |
| Holder and sleeves | Holder type, usable slots, sleeve type, layers and supplied quantity | Nominal core count without the installed holder arrangement |
| Fit evidence | Current drawings plus the reviewed overlay or configuration-matched mock-up | Catalogue image, verbal compatibility claim, or drawing for another ratio |
| Optical evidence | Model/configuration, method, wavelengths, directions, reference planes, limits and results | Generic certificate or report that cannot be mapped to the offered item |
| Deviations and commercial basis | Declared deviations, quantity, packaging, schedule and validity on the same technical revision | Price or schedule compared before technical deviations are resolved |
Request the current model datasheet and drawing before technical approval. If those records do not resolve body, transition, sleeve, or route geometry, evaluate a representative sample in the populated host before volume release. A generic family datasheet or a test report for another ratio, package, termination, or revision is not evidence for the proposed build.
How should price and lead time be compared?
Compare commercial offers only after the technical configuration and permitted deviations are frozen. Ask every bidder to quote the same quantity, currency, trade term and destination, packaging and labeling scope, required documents, sample or pilot basis, quotation validity, approval date, and production and shipping milestones. These are RFQ fields, not BWNFiber promises. If a lower price or shorter schedule depends on a different package, termination, test scope, or document set, return the offer to technical comparison before treating it as an alternative.
How should an international capacity-review RFQ be localized?
A region name is not a technical specification. Use it to trigger project questions, then record the governing document, clause, revision, and approval owner. The prompts below are not regional defaults.
| Market context | Environment and installation questions to confirm | Standards, documents, and delivery questions to confirm |
|---|---|---|
| North America | Is the host in an indoor cabinet, aerial closure, underground vault, or another stated location? Which temperature, water, dust, utility, and service-access conditions apply? | Which operator, authority, client, or named ANSI/TIA or other requirement controls the offered configuration? Confirm traceability, labels, destination, trade term, and approval-to-shipment milestones. |
| Europe | Which indoor or outdoor host, fire boundary, cable interface, environmental class, and maintenance method apply to the exact supplied BOM? | Which IEC, EN, client, and applicable regulatory documents are named? Confirm required language, declarations, test records, packaging marks, destination, and delivery batches. |
| Middle East | What installed and storage temperatures, solar exposure, dust, salinity, humidity, and access constraints must the host system withstand? | Which authority or tender specification controls? Confirm submittal sequence, document approval, export packaging, storage exposure, destination, and milestone dates. |
| Southeast Asia | Does the site introduce condensation, persistent humidity, flood exposure, coastal salinity, heat, or repeated closure access? How is the host installed? | Which national operator or project specification applies? Confirm site-by-site labels, batch traceability, shipping and storage conditions, sample approval, and phased delivery. |
| Latin America | Do altitude, coastal exposure, pollution, temperature range, aerial or duct routing, and local maintenance access affect the selected host or tray arrangement? | Which utility, operator, authority, or tender document controls? Confirm Spanish or Portuguese documentation where requested, import and packing marks, destination, and partial-shipment rules. |
| Africa | Which heat, dust, humidity, coastal exposure, power-site access, transport, or remote-maintenance constraints apply to the actual location? | Which operator, authority, funding, or tender requirements apply? Confirm lot identification, spare strategy, protective packaging, destination, delivery stages, and acceptance records. |
For every market, separate splitter evidence from host and cable evidence. A host environmental rating, cable jacket property, or project certificate does not become a bare-splitter property. OEM/ODM, private-label, bulk-order, export-packaging, certificate, and test-report requirements belong in the controlled RFQ only when the buyer requests them and the supplier confirms the exact scope in writing. Order volume may change the approval, packaging, traceability, and delivery plan; it does not change the splice-count formula.
What should BWNFiber return after a capacity-review request?
BWNFiber's published project workflow moves from project inputs to engineering review, a sample-and-quotation stage with optional sample assemblies, then production and testing for approved items. For this tray-capacity task, the useful response is a three-state record rather than an unsupported yes/no compatibility claim.
| Response state | What it means | Buyer action |
|---|---|---|
| Confirmed | A submitted field matches a current model, drawing, instruction, or agreed requirement | Carry the referenced value and revision into the comparison record |
| Conditional | The proposed answer depends on the host, route, sample, test plan, project specification, or another named condition | Assign the condition, evidence owner, and due date before release |
| Hold | A required record is absent, out of revision, conflicting, or cannot be mapped to the offered configuration | Request the missing record or redesign; do not convert the gap into an assumption |
After the three states are recorded, the next step may be a document request, engineering clarification, configuration-matched sample and quotation, or project/order discussion. Production, test scope, quantity, price, lead time, OEM/ODM feasibility, packaging, and delivery terms remain subject to the written quotation and approved configuration.
Frequently asked questions
What is the difference between tray port count and splice capacity?
Port count describes service interfaces. Splice capacity describes protected joints. Available ports do not compensate for missing holder positions, route space, or body clearance.
How many tray splices does a fully spliced 1×8 PLC splitter need?
It contributes nine splices: one input plus eight outputs. Add every other splice and reserve position assigned to the same tray before checking usable capacity.
How many tray splices does a fully spliced 1×16 PLC splitter need?
It contributes seventeen splices: one input plus sixteen outputs. A nominal 24-splice rating leaves arithmetic headroom, but the completed assembly still needs a fit review.
Does a connectorized PLC splitter use splice-tray positions?
Only fiber paths physically spliced in the tray use splice-protection positions. Connectorized paths still need adapters or parking, controlled routing, identification, and access.
Do unused PLC splitter outputs count as splices?
Not while they remain unspliced. Record where each output is protected, stored, labeled, and made accessible for later activation.
Can two PLC splitters share one splice tray?
They can share a tray only when holder demand, both bodies, all routes, transitions, labels, service access, and tray movement pass as one populated build. Two fully spliced 1×16 devices contribute 34 base splices, not 18; 18 is the base count for one fully spliced 2×16 device. Adding the printed ratios is not a fit calculation.
Is a tray's advertised core capacity enough to approve a PLC splitter?
No. Use it to shortlist trays, then verify the holder, sleeves, splitter footprint, routes, cover, hinge, stack, and host configuration.
How much spare tray capacity should be reserved?
Follow the operator's documented growth, restoration, and maintenance policy. Convert it into named holder positions and route space instead of using a universal percentage.
How do I confirm that a bare splitter body fits the tray?
Overlay the model-specific splitter and tray drawings, then build a populated mock-up with the intended holder, sleeves, routes, labels, cover, hinge, and adjacent trays.
What bend radius should be used in the tray?
Start with the ordered fiber designation and lead construction. ITU-T G.657 (08/2024) gives a 10 mm minimum design radius for G.657.A1 and 7.5 mm for G.657.A2, but those category values do not override the splitter lead or host instructions. Never transfer them to G.652.D or an unidentified fiber.
Can a bare fiber PLC splitter be used in an outdoor closure?
Only a verified host can supply the required mounting, cable entry, sealing, and environmental protection. Do not transfer the host's IP or outdoor claim to the bare component.
What documents should accompany the capacity approval?
Retain the splitter and host drawings, port map, splice schedule, route overlay, holder and sleeve record, mock-up result, optical plan, deviations, as-built results, and accountable approvals.
Send a capacity-review pack
Send BWNFiber the information needed to review one defined configuration:
- project country or jurisdiction, site environment, governing specification, and whether a representative sample is required;
- splitter model, revision, topology, package, construction drawing, lead construction, termination, and port map;
- host and tray models, drawings, instructions, tray position, holder, sleeve method, and neighboring components;
- spliced inputs, spliced outputs, other assigned splices, and required reserve;
- route overlay, unused-output method, labels, cover, hinge, and tray-stack arrangement;
- PON budget plus component and installed-path acceptance limits;
- requested evidence, quantity, currency, trade term and destination, packaging and labeling requirements, quotation validity, required sample or pilot, and target approval, production, and shipping milestones.
Do not send only the split ratio and headline tray capacity. Contact us to send the splitter and tray drawings for a capacity review. The review response should separate Confirmed, Conditional, and Hold items, including deviations and available model-specific documents. Availability, commercial terms, compliance evidence, and technical release remain configuration-specific.
Technical references and scope
- IEC 60875-1:2024: generic specification for passive non-wavelength-selective fiber optic branching devices.
- ITU-T G.671 (05/2025): definitions and transmission-characteristic context for optical components, including branching components.
- IEC 61300-3-4:2023: attenuation measurement methods for optical components.
- IEC 61300-3-6:2008: return-loss measurement procedures.
- IEC 61300-3-2:2009: polarization-dependent-loss measurement methods for single-mode devices.
- ITU-T G.657 (08/2024) and ITU-T G.652 (08/2024): single-mode fiber and cable characteristics.
Technical notice: This worksheet screens a proposed design. It is not a guarantee of tray capacity, compatibility, or optical performance. Final release requires the ordered splitter, tray and host records, applicable work instructions, test plan, and approval by an accountable technical reviewer.
