ODN Product Schedule Builder

How to Choose ODN Products and Build a Controlled Product Schedule for FTTH

Map every node on your network diagram to a product function, capacity, interface and approval requirement. This ODN product schedule approach creates a shortlist that procurement and engineering can verify before any model selection.

Category Products

Browse All ODN Products

Explore published BWNFiber products across access terminals, distribution boxes, closures, splitters, fiber assemblies, cables, connectors and supporting components.

Page Role Boundary

When to Use This Schedule Builder vs Other BWNFiber Pages

This page = function mapping + controlled ODN product schedule builder (diagram → shortlist → RFQ inputs).

General Products page (/products/) = broad Fiber Optic & FTTH Components catalog.

Quick ODN Solutions (/quick-odn/) = preconnected architecture (hub / sub / end) with coordinated BOM.

Category owner pages = detailed model selection and transactional approval.

ODN education page (/odn/) = definition and ODN version evolution.

Your situationRecommended pageWhy
You have a network diagram and need a verifiable product shortlistThis pageFocuses on node-to-function mapping, capacity rules and interface control
You want a ready-made preconnected FTTH architectureQuick ODN SolutionsProvides hub/sub/end system view and recommended BOM
You already know the exact product family and need model specsCategory owner pageModel-level datasheets, drawings and configuration options
You need a general overview of all fiber productsGeneral Products catalogBroad entry point across management, assemblies and accessories
Function Mapping

Assign ODN Products by Network Function

Start from the diagram. Every product line in the ODN product schedule must have a clear function and node reference.

FunctionTypical ProductsKey Schedule Fields
Cable ManagementAccess terminals, distribution boxes, splice closures, patch panelsInternal layout, cable entries, mounting, accessibility
Passive DistributionPLC / FBT splitters, adapters, connector interfacesRatio, package, termination, loss limits
Fiber & AssembliesFeeder, distribution, drop, indoor cables + preterminated assembliesFiber type/count, construction, length, install method
Components & ToolsConnectors, attenuators, trays, sleeves, test toolsInterface match, field workflow, acceptance tests
Core Work Product

How to Build a Complete ODN Product Schedule

Each row must be complete enough for engineering review and procurement. Incomplete rows cause re-quote cycles.

How to build an ODN product schedule in 5 steps

  1. List every node and cable segment from the network diagram and give each a unique reference.
  2. Assign one primary function (routing, joint protection, splitting, termination, access or test) to each node.
  3. Separate working fibers, reserve fibers, splitter outputs, adapter ports, splices and cable entries. Apply the project growth policy.
  4. Lock the interface-control schedule for every unique connection type.
  5. Attach required documents, quantities and accessories before shortlisting any specific model.

Required fields for every schedule row

Network Stage & NodeFeeder / distribution / drop / premises + unique node reference
Product FunctionRouting, joint protection, splitting, termination, access, test
CapacityWorking fibers, reserve fibers, splices, splitter outputs, ports, cable entries — separated
Optical InterfaceFiber type, connector family, polish, keying, adapter, hardened mating
Cable RouteAerial / duct / buried / indoor + construction, OD, length, strength member
EnvironmentDimensions, material, sealing, mounting, required IP / impact / UV evidence
DocumentsCurrent datasheet, drawing, port map, install guide, test limits, conformity evidence

Capacity calculation rule (non-negotiable)

Never apply a single maximum fiber count to every product. Separate working vs reserve, active vs planned take-up, splitter outputs vs adapter ports, splices vs cable entries. Apply the project growth policy at each node. Single-number selection is a frequent cause of later shortage or unnecessary cost.

Worked capacity example (illustrative node)

ItemValueNote
Active subscribers planned48Current take-rate target
Growth reserve30%Project policy
Working fibers required48
Reserve fibers16Rounded up
1×8 PLC outputs needed8Secondary split stage
Adapter ports to specify≥ 16Allow maintenance access
Cable entries1 oval + 2 branchMust match enclosure design

This is an illustrative example only. Actual numbers must come from your diagram, take-rate study and optical budget.

Interface Control Schedule (copyable template)

FieldRequired ValueExample / Notes
Fiber typeG.652.D / G.657.A1 / G.657.A2
Connector familySC / Mini SC / LC / hardened
PolishAPC / UPC
Keying / polarity
Adapter type
Cable diameter / gland
Splitter terminationConnectorized / bare / splice
Mating assemblyConfirm interchangeability — do not assume

Fill one row per unique interface. Similar-looking hardened connectors are a frequent source of field failures when interchangeability is assumed.

Architecture Choice

Traditional Splice vs Pre-terminated Decision

FactorTraditional field-splicePre-terminated / Quick ODN style
Field skill requiredHigh (fusion splicing)Lower (plug-and-play)
Deployment speedSlowerFaster
Length flexibilityHighConstrained by pre-cut lengths
Quality consistencyDepends on crew and conditionsFactory-controlled
Best fitComplex routes, uncertain lengths, high customizationStandardized overhead or mixed routes where labor or schedule is the binding constraint

Many projects use a hybrid approach. Record the chosen method per node inside the ODN product schedule.

Risk Control

Common ODN Product Selection Mistakes to Avoid

  • Using one maximum fiber count for every enclosure — leads to shortage at high-growth nodes or unnecessary cost at low-demand nodes.
  • Selecting by product name instead of internal layout — a “distribution box” and a “splice closure” can have completely different maintenance workflows.
  • Assuming similar-looking hardened connectors are interchangeable — mating failures are expensive and common when interface-control schedules are missing.
  • Skipping the interface-control schedule — fiber type, polish, keying and gland compatibility must be locked before model selection.
  • Treating category names as technical specifications — final approval requires the current model datasheet, drawing and the completed schedule.
  • Omitting growth policy and take-rate — active subscriber count alone under-sizes the network.
Schedule Discipline

Map Products to the Diagram

  • Node reference + network stage
  • Function and reference family
  • Separated capacity (working / reserve / ports)
  • Full interface definition
  • Environment and mounting
  • Quantities, accessories, labels
Approval Gate

Approve Models Only After Schedule Is Complete

  • Exact model + revision
  • Dimensions and internal layout
  • Optical / mechanical / environmental limits
  • Interface and cable-entry match
  • Install and test procedure
  • Project-required conformity evidence

Rule: Category name is not a technical specification. Complete the ODN product schedule first.

Model Evidence (Strict Scope)

BWN-ODN-8/16: 8 or 16 preconnectorized ports, 1×8 or 1×16 PLC, PP material, IP68, one oval cable entry up to 18 mm, two branch entries up to 14 mm.

BWN-FAT-4A: 5 Mini SC ports, 1×4 PLC, PP material, 198 × 101 × 70 mm, IP68, wall / pole / aerial mounting.

These values apply only to the named models and revisions. No catalog-wide performance, compatibility or certification claims are inferred from them. Always verify the current datasheet and drawing for the exact configuration under consideration.

FAQ

ODN Product Schedule Questions

What is an ODN product schedule?

A controlled list that maps every network node and cable segment to a product function, capacity, interface, installation environment and required approval documents. It turns a diagram into a verifiable bill of materials before any model is shortlisted.

How do I calculate working vs reserve fiber in an ODN?

Separate active working fibers from reserve fibers at every node. Apply the project growth policy (commonly 20–40 %) to the active count. Also separate splitter outputs, adapter ports, splices and cable entries. Never use one maximum number for the whole schedule.

What documents are required to approve ODN products?

Current datasheet, dimensional drawing, optical or port map, cable and interface schedule, installation guide, test limits and project-specified conformity evidence for the exact model and revision. Category-level claims are not sufficient.

How can I avoid mismatched connectors in FTTH ODN?

Create an interface-control schedule that records fiber type, connector family, APC or UPC polish, keying, adapter type, cable diameter, gland, splitter termination and mating assembly. Similar-looking hardened connectors must not be assumed interchangeable.

When should I use pre-terminated ODN instead of field splicing?

Choose pre-terminated or Quick ODN style when deployment speed, labor skill availability or quality consistency is the binding constraint. Choose traditional field splicing when routes are complex, lengths are uncertain or high customization is required. Record the method per node.

What is the difference between a splice closure and a distribution box in the schedule?

Splice closures primarily protect cable joints and house splice trays. Distribution boxes and access terminals combine splicing, splitting, adapters and accessible ports. Select by actual internal layout and maintenance workflow, not by product name.

Can I use one maximum fiber count for all ODN enclosures?

No. This is a common cause of later shortage or unnecessary cost. Separate working fibers, reserve fibers, splitter outputs, adapter ports, splices and cable entries, then apply the growth policy at each node.

What information should be in an ODN RFQ?

Network diagram, node schedule, fiber counts, split plan, optical budget, connector interfaces, cable routes and lengths, enclosure locations, mounting method, quantities, accessories, labels and required approval documents.

How does take-rate affect ODN product capacity?

Take-rate determines active subscriber count and therefore working fiber and splitter-output demand. Planned take-up plus growth reserve must be calculated separately so that ports and fibers are neither under- nor over-specified.

What is an interface control schedule for fiber networks?

A table that locks fiber type, connector family, polish, keying, adapter, cable diameter, gland, splitter termination and mating assembly for every unique interface. It is the primary tool for preventing field mating failures.

Should category names be used as technical specifications?

No. Final approval requires the current model page, datasheet, drawing and the completed ODN product schedule.

How do I map an ODN diagram to a product shortlist?

List every node and cable segment, assign one primary function, separate capacities, lock the interface-control schedule, attach required documents, then shortlist families. Only after the schedule is complete should specific models be selected on their owner pages.

Typical Use

Where the Schedule Approach Applies

FTTH Access Networks

Coordinate feeder to drop products against take-rate and growth policy so that capacity is neither short nor wasted.

Outside-Plant Distribution

Match closures, boxes and cable constructions to aerial, duct, handhole or buried routes with correct sealing and mounting evidence.

Premises and Rack Termination

Control patch panels, wall outlets, assemblies, adapters and test access at equipment and subscriber locations.

From Diagram to Verifiable Shortlist

Ready to Build Your ODN Product Schedule?

Send the network diagram, node list, capacity targets, interface requirements and documents for a focused product-family review. The output is an RFQ-ready shortlist grounded in a complete schedule.

Submit Diagram for Schedule Review