Fiber Access Terminal
Quick ODN Solutions: Preconnected FTTH Design & Buyer Specification Guide
BWNFiber Quick ODN is a project-specific, preconnected FTTH architecture for ISPs, contractors and network integrators. We help you control every node, interface, splitter stage, optical budget and cable length before volume production. Send your route plan for a 24-hour BOM review.
- Pre-terminated, factory-tested assemblies
- Node-controlled design with optical budget
- Project-specific BOM and pilot support
Category Products
Quick ODN Solutions Product Range
Fiber Distribution Box
SJ-FTTH-SK18-M 24-Port Outdoor Fiber Distribution Box
Fiber Distribution Box
BWN-SK18-24B 16 Ports Fiber Termination Box
Fiber Distribution Box
SJ-FTTH-SK18-A1 SC 16-Port Fiber Termination Box
Fiber Distribution Box
MBN-FOSC-A18-8 8 Core Fiber Optic Termination Box
Fiber Access Terminal
BWN-ODN-8/16 Optical Distribution Box
Fiber Distribution Box
SJ-FTTH-SK18-A2 24 Ports SC/LC FTTH Outdoor Box
Fiber Distribution Box
SJ-FTTH-SK18-B1 1X16 SC PLC FTTH Fiber Distribution Box
Fiber Access Terminal
MBN-FOSC-A17-16-2 FTTH NAP Optical Distribution Point 16 Ports IP68
Fiber Distribution Box
MBN-FOSC-A17-16 Fiber Optic Terminal Box 16 Cores Outdoor Waterproof
Fiber Distribution Box
SJ-FTTH-SK18-G 8 Cores FTTH Fat Box Wall Mounting Pole mounting
Page Role & Quick Answer
What This Page Covers
Page role: Primary owner for Quick ODN solution architecture, design controls and buyer specification. For basic definition and comparison numbers see the What Is Quick ODN guide. For urban / rural / MDU scenario layouts see the Case-Based Design Guide.
A Quick ODN solution is a route-specific preconnected FTTH architecture in which selected cables, splitters and terminal interfaces are factory-terminated and tested. It can reduce selected field-splicing work, but the network still has to be engineered around route geometry, subscriber demand, splitter topology, optical loss, connector compatibility, cable lengths, environmental conditions and maintenance access.
Decision Framework
Quick ODN vs Traditional ODN: Planning Risks That Matter
Neither architecture is automatically better. Compare them by route certainty, labor capability, restoration strategy and lifecycle control rather than assuming that preconnection always removes splicing or lowers total cost.
| Decision factor | Quick ODN / preterminated ODN | Traditional field-spliced ODN |
|---|---|---|
| Best fit | Repeatable routes with surveyed node positions, controlled interfaces and planned cable lengths. | Routes likely to change in the field or projects that need maximum cut-to-length flexibility. |
| Field work | More factory termination; selected connections are mated and inspected onsite. Transition or repair splices may remain. | More cable preparation, fusion splicing, protection and testing at network nodes. |
| Main planning risk | Wrong length, wrong connector revision, incompatible mating parts or an incomplete port map. | Variable workmanship, splice protection, enclosure resealing and technician availability. |
| Inventory model | Requires controlled assemblies, length bands, dust caps, adapters, labels and replacement spares. | Requires bulk cable, splice consumables, closures, pigtails and field tools. |
| Acceptance focus | Factory records plus onsite inspection, cleaning, mating, end-to-end loss and route verification. | Splice quality, tray routing, enclosure sealing and end-to-end optical tests. |
| Change tolerance | Lower when routes or node positions change after assemblies are produced. | Higher for onsite length changes, provided crews and equipment are available. |
Selection rule: use Quick ODN where route data and interface control are strong enough to move repeatable work into the factory. Keep field-spliced transitions where survey uncertainty, restoration requirements or existing-network conditions demand flexibility.
Network Architecture
Define the Quick ODN Route by Node
Start with premises passed, take rate, topology and optical budget. Then assign the node role, interfaces and cable assemblies. Do not treat Quick ODN as one universal product kit. Detailed node definitions and scenario layouts are covered in the Design Guide.
Feeder and HubFeeder handoff, primary split, distribution capacity and reserve
Sub and Branch NodeCascade interface, secondary split, branch route and service area
End and Subscriber TerminalDrop outputs, hardened adapters, port map and activation access
Drop to PremisesPreterminated drop length, routing, wall outlet and indoor handoff
Solution Design
How to Specify a Quick ODN Solution
Approve the network as a sequence of controlled nodes and interfaces. Every Hub, Sub and End location must map to the optical budget, port schedule, cable route and installation plan.
| Route and Topology | Document feeder origin, distribution routes, branch points, subscriber clusters, aerial, duct, façade or indoor segments and the transition between existing and new infrastructure. |
|---|---|
| Premises and Take Rate | State premises passed, active subscribers, forecast take rate, reserve policy and expansion stages for each service area rather than using one network-wide port number. |
| Feeder and Hub Capacity | Define feeder fibers, Hub inputs, primary split, express or cascade paths, distribution outputs, reserve capacity, splice requirements and maintenance access. |
| Splitter Stages and Budget | Map centralized or cascaded PLC or FBT ratios, wavelength plan, connector or splice interfaces and allowed loss at every path before selecting splitter modules. |
| Hardened Interface | Control connector family, APC or UPC polish, keying, threads or latch, sealing surface, adapter, dust cap and the exact mating cable assembly at each outdoor node. |
| Distribution and Drop Cable | Specify fiber type, construction, fiber count, connector ends, route length, slack, pulling direction, storage, coil or reel format and labels for every preterminated assembly. |
| Node Enclosure and Mounting | Confirm port map, splitter and splice layout, cable entries, dimensions, material, wall, pole or aerial mounting and model-specific environmental evidence. |
| Testing and Maintenance | Define factory and field test records required by the project, reference power, wavelength, acceptance limits, cleaning, inspection, port labels, spare caps and replacement method. |
| BOM and Approval Package | Issue a node list, port and splitter maps, cable-length schedule, interface-control record, model drawings, accessories, spares, quantities and construction method as one controlled package. |
Published BWNFiber Quick ODN Node Evidence
Architecture evidence: the current BWNFiber Quick ODN owner page describes feeder, distribution and drop layers and uses Hub, Sub and End node terminology. This page preserves that architecture without repeating unsupported rollout-speed or cost claims.
BWN-FAT-4A: the published record lists five Mini SC ports, a 1×4 PLC splitter, PP material, 198 × 101 × 70 mm dimensions, IP68 and wall, pole or aerial mounting.
BWN-FAT-8F: the published record lists nine Mini SC ports, a 1×8 or 1×9 PLC splitter, PP material, 313 × 101 × 81 mm dimensions, IP68, hot-plate welding and wall, pole or aerial mounting.
BWN-ODN-8/16: the model page lists 8 or 16 preconnectorized ports, 1×8 or 1×16 PLC splitters, PP material, IP68, one oval entry up to 18 mm and two branch entries up to 14 mm. Its several published fusion-capacity values are not assigned to one tray configuration here.
Scope control: these are model-specific examples, not a complete Quick ODN BOM. Interface compatibility, ratings, cable lengths, splitter stages and test limits must be approved for the project configuration.
How-To
How to Design a Quick ODN Network in Seven Steps
Freeze the design inputs in this order. Selecting boxes or splitter modules before the route, capacity and loss model are approved creates avoidable rework.
- Survey the route and existing network. Record feeder handoff, pole, duct, façade and indoor segments, node access, elevation changes, transition points and repair constraints.
- Model demand by service area. Separate premises passed, initial take rate, growth stages, subscriber ports, cascade ports, express capacity and operational reserve.
- Choose the split architecture. Compare centralized and cascaded PLC splitter layouts against route geometry, optical budget, fault isolation, inventory and future expansion.
- Assign every node role. Define what each Hub, Sub and End node receives, splits, passes through and presents to subscribers. Do not infer a port function from enclosure size.
- Freeze the interface-control record. Identify connector family, polish, keying, latch or thread, sealing surface, adapter, dust cap and approved mating assembly by exact revision.
- Build the cable-length schedule. Use surveyed route distance plus approved routing, elevation, storage and service slack. State tolerance, pulling direction, reel or coil format and labels.
- Pilot, test and release the BOM. Install a representative segment, verify the technician sequence and acceptance limits, then release controlled drawings, quantities, accessories and spares.
Technical Validation
Optical Budget, Interface and Acceptance Controls
A plug-and-play ODN still needs an end-to-end loss model and acceptance plan. Use the specified PON class and the approved OLT and ONT data; do not apply one generic budget to every network.
Build the worst-case optical path
Path loss = fiber attenuation + splitter loss + connector loss + splice loss + engineering margin. Calculate each planned wavelength and the longest or highest-loss path. Count every mated interface and transition, then compare the result with the applicable transceiver-class limits.
- Fiber length and specified attenuation by wavelength
- Each splitter stage and its maximum insertion loss
- All hardened and indoor mated connector pairs
- Planned fusion or mechanical splices and transitions
- Design margin for aging, repair and measurement uncertainty
Define evidence before ordering
Set acceptance limits in the project specification before the pilot. A factory pass result does not replace onsite inspection after transport, routing and mating.
- Visual inspection and connector-end cleaning procedure
- Insertion-loss test method, wavelengths and reference method
- Return-loss requirement where the system specification calls for it
- OTDR traces from agreed directions when event location is required
- Polarity, port-label and route-record verification
- Model, serial or batch traceability and failed-item disposition
| Reference | How to use it in a Quick ODN specification |
|---|---|
| ETSI GS F5G 003 | Supports the principle that factory-made connectors and assemblies for quick ODN construction require specified quality and reliability controls. |
| ITU-T G.984.2 | Use when the project is based on GPON physical-media-dependent requirements; confirm the actual optical class and equipment data. |
| ITU-T G.9807.1 | Use for XGS-PON physical-layer planning where applicable; do not mix its class limits with GPON assumptions. |
| IEC 61300-3-4 / IEC 61300-3-6 | Reference the agreed edition and laboratory method for attenuation and return-loss measurements of fiber-optic interconnecting devices. |
Specification notice: standards identify methods and system requirements; the purchase specification must still state the exact edition, product revision, wavelengths, reference method, sample plan and pass/fail limits. Figures and examples on this page are typical planning references only, not a guarantee of project performance.
Need a reusable loss-planning worksheet?Submit the project form and our team will follow up with the Quick ODN optical budget template.
Download the Quick ODN Optical Budget Template (Excel) Worked Examples
Typical Optical Budget Examples for Quick ODN
These examples illustrate how to build a worst-case path. They are planning references only. Always replace the values with the actual fiber attenuation, splitter maximum IL, connector IL, splice IL and margin required by the project specification and the approved OLT/ONT class.
Example A — Centralized 1×16 split (short urban route)
| Element | Assumed value | Contribution |
|---|---|---|
| Feeder fiber (3 km @ 0.35 dB/km @ 1490 nm) | 3 km | 1.05 dB |
| Feeder connector pairs (2) | 0.30 dB each | 0.60 dB |
| 1×16 PLC splitter (max IL) | — | 7.20 dB |
| Distribution / drop fiber (0.4 km) | 0.35 dB/km | 0.14 dB |
| Hardened connector pairs (2) | 0.30 dB each | 0.60 dB |
| Engineering margin (aging + repair + measurement) | — | 2.00 dB |
| Total estimated path loss | — | ~11.6 dB |
GPON Class B+ typically allows 28 dB. This path leaves substantial headroom. Confirm the actual OLT and ONT class limits before finalizing.
Example B — Cascaded 1×4 + 1×8 (longer mixed route)
| Element | Assumed value | Contribution |
|---|---|---|
| Feeder fiber (8 km @ 0.35 dB/km) | 8 km | 2.80 dB |
| Feeder + cascade connector pairs (3) | 0.30 dB each | 0.90 dB |
| 1×4 PLC (primary) max IL | — | 7.00 dB |
| 1×8 PLC (secondary) max IL | — | 10.50 dB |
| Distribution + drop fiber (1.2 km) | 0.35 dB/km | 0.42 dB |
| Hardened connector pairs (2) | 0.30 dB each | 0.60 dB |
| Planned transition splice (1) | 0.10 dB | 0.10 dB |
| Engineering margin | — | 2.50 dB |
| Total estimated path loss | — | ~24.8 dB |
This path is tighter against a 28 dB Class B+ limit. Cascaded designs require tighter control of every connector and splice. Always calculate the longest and highest-loss path separately for each wavelength.
How to use these examples: replace every assumed value with project-specific data (fiber type and measured attenuation, splitter data-sheet maximum IL, exact number of mated pairs, approved margin). Do not treat the totals as guaranteed performance.
Risk Control
Common Specification Mistakes in Quick ODN Projects
Most rework and acceptance failures come from incomplete inputs rather than component quality. Avoid these patterns before releasing the BOM.
- Ordering assemblies before the route is frozen. Surveyed length + approved slack must exist before any preterminated cable is manufactured. Late route changes create length mismatches that cannot be fixed in the field without new assemblies or unauthorized splices.
- Treating similar-looking outdoor connectors as interchangeable. Mini-SC, OptiTap-style and FastConnect families may look similar but differ in keying, thread, sealing surface and mating force. Require a model-level compatibility statement and physical mating verification in the pilot.
- Omitting length tolerance and slack policy. State the allowable length band, pulling direction, storage method and service-loop requirement. Without them, crews either leave excess cable that becomes a maintenance hazard or discover shortfall on site.
- Applying a single generic loss budget. Centralized and cascaded paths, different wavelengths and different numbers of connectors produce different totals. Calculate the worst-case path for every service area.
- Approving isolated components instead of a representative chain. A terminal, a splitter module and a drop cable may each pass factory tests yet fail when mated, routed and labeled together. The pilot must include the actual node-to-drop sequence.
- Leaving interface revisions uncontrolled. A later revision of the same connector family can change the sealing geometry or keying. Freeze the exact revision (drawing number or date code) in the interface-control record.
- Skipping outdoor environmental evidence. IP68 on a data sheet is not a blanket outdoor rating. Require model-specific ingress, impact, temperature and UV evidence that matches the installation method and climate.
Practical rule: if any of the above items is still open when the purchase order is issued, the project is carrying avoidable risk into production and field acceptance.
Procurement
Quick ODN Buyer Checklist
Send one controlled requirement package to candidate suppliers. A price comparison is not meaningful when bidders are quoting different node roles, connector systems, cable constructions or acceptance evidence.
Network inputs
- Route drawing and installation method
- Premises passed, take rate and growth stage
- PON type, optical class and loss budget
- Hub, Sub and End node schedule
Product controls
- Exact splitter ratios and port map
- Interface family and mating revisions
- Fiber, cable, jacket and length schedule
- Mounting, sealing, labels and accessories
Approval evidence
- Drawings and model-level data sheets
- Factory test records and sampling plan
- Pilot route and field acceptance method
- Spares, packaging and change control
Ask each supplier to mark assumptions and exclusions. Before volume production, approve a representative node-and-cable chain—not isolated components—so connector mating, cable handling, labeling, optical loss and the technician workflow are tested together.
Contact Us for a Quick ODN BOM ReviewMap Hub, Sub and End Nodes
Create a node schedule that connects the route, split design, port plan and cable assemblies without leaving interface decisions to field interpretation.
- Feeder handoff and existing-network transition
- Hub, Sub and End node identifiers and quantities
- Primary and secondary splitter paths
- Subscriber, cascade, express and reserve ports
- Preterminated cable types, ends and lengths
- Mounting, access, labels and service loops
Approve Interfaces Before Volume Deployment
Build and test a representative route segment that includes the actual nodes, mating interfaces, cable lengths, installation method and acceptance workflow.
- Approved node diagram and optical budget
- Exact terminal, splitter and cable revisions
- Interface-control and mating records
- Installation tools and technician sequence
- Inspection, cleaning and loss acceptance
- Replacement, spares and fault-isolation plan
Important: preconnected design can reduce or relocate selected field terminations, but it does not automatically remove every splice, transition or repair requirement.
FAQ
Quick ODN Specification & Procurement Questions
These answers focus on controllable design decisions: splitter stages, hardened interfaces, integration, port capacity, cable lengths, pilot packages and quotation inputs. Basic definitions are covered on the What Is Quick ODN page.
How should splitter stages be selected for Quick ODN?
Choose centralized or cascaded splitting from the optical budget, premises passed, take rate, route geometry, reserve policy and maintenance plan. Record every split ratio, wavelength, connector or splice interface and acceptance limit rather than selecting only by output count.
How should hardened interfaces be controlled in a Quick ODN design?
Specify connector family, polish, keying, thread or latch, sealing surface, adapter, dust cap and mating cable assembly for each node. Similar-looking outdoor interfaces should not be treated as interchangeable without a documented model-level compatibility statement.
Can Quick ODN be integrated with an existing fiber network?
It may be possible to connect preterminated nodes to existing feeder or distribution infrastructure through approved splice, adapter or patch interfaces. Survey the installed fiber, connectors, closures, available capacity, loss budget and route condition before defining the transition point.
How is Quick ODN port capacity calculated?
Separate feeder, cascade, splitter-input, subscriber, express and reserve ports. Apply the premises-passed and take-rate plan to every Hub, Sub and End node, then verify that the physical adapter count and splitter outputs match the approved port map.
How should preterminated cable lengths be specified?
Use a surveyed route length plus approved slack for routing, storage, elevation, access and replacement. State cable construction, connector ends, pulling direction, reel or coil format, label scheme and allowable length tolerance for every assembly.
Does every Quick ODN route eliminate field splicing?
No. Preconnected assemblies can reduce or relocate selected field terminations, but feeder joints, network transitions, repairs or topology-specific branches may still require splicing. The method must be defined node by node in the construction plan.
Are all Quick ODN terminals suitable for outdoor use?
No category-wide outdoor rating should be assumed. Check the exact enclosure, hardened adapters, seals, cable entries, mounting hardware and installation procedure, together with model-specific ingress, impact, temperature and UV evidence required for the site.
What should be included in a Quick ODN pilot and approval package?
Include the route drawing, node diagram, optical budget, port and splitter maps, cable-length schedule, interface-control record, model drawings, installation method, acceptance test plan, labels, accessories, spares and a representative pilot segment.
What information is needed for a Quick ODN quotation?
Send the route plan, premises passed and take rate, feeder availability, Hub, Sub and End node quantities, split architecture, optical budget, hardened interface, cable types and lengths, installation method, test requirements, accessories, spares and approval documents.
How do I calculate a typical optical budget for a cascaded Quick ODN?
Sum fiber attenuation by wavelength, maximum insertion loss of every splitter stage, every mated connector pair, planned splices and an engineering margin. Compare the total against the OLT/ONT class limits for the longest or highest-loss path. See the worked examples on this page for structure.
What are the most common specification mistakes in Quick ODN projects?
Ordering cables before the route is surveyed, treating similar-looking outdoor connectors as interchangeable, omitting length tolerance and slack, skipping the representative pilot chain, and applying a generic loss budget instead of the project-specific worst-case path.
Applications
Quick ODN Deployment Scenarios
Use preconnected architecture where the route can be surveyed, interfaces controlled and node access planned; verify the solution against actual construction conditions. Detailed scenario designs are in the Case-Based Design Guide.
Overhead and Low-Rise FTTH
Map pole or aerial Hub, Sub and End nodes, preterminated distribution lengths, subscriber ports, mounting access and drop routes by service area.
Façade and Mixed Urban Routes
Coordinate existing feeder transitions, compact node locations, cable storage, building access, subscriber drops and the local installation method.
Brownfield Network Extensions
Survey existing capacity and interfaces before adding preconnected branches, terminals or drops, and preserve a documented transition and test point.
Control Every Node, Interface and Cable Length
Need a Quick ODN Architecture Review?
Send BWNFiber your route plan, premises count, node schedule, split design, optical budget, interface requirements and cable lengths for a coordinated solution review.
Request a Quick ODN Review