ODN As-Built Records: Feeder, Distribution, Drop and Splice Data Model

Project inputs that narrow the product family

Create a field record structure that can trace an optical path end to end. Start with the operating requirement and installation boundary, then separate system requirements from product claims so each supplier knows which evidence must accompany the offered configuration.

• Assign stable IDs to every cable, fibre, node and port.
• Separate design, installed and in-service states.
• Link splice and splitter relationships to test records.
• Define who approves and publishes as-built changes.

Relevant products from our communications portfolio

The products below connect the ODN as built records decision to real catalogue families and verified site photography. They are starting points, not a claim that every configuration described here is a standard stock item; confirm model, interface, rating, drawing and testing scope with the project team.

• Intelligent Optical Distribution Network (IODN) — use this product page as a configuration reference when you assign stable IDs to every cable, fibre, node and port. Confirm the offered model, interfaces, drawings and available evidence before quotation.
• 24-Core SMC Fiber Distribution Box — use this product page as a configuration reference when you separate design, installed and in-service states. Confirm the offered model, interfaces, drawings and available evidence before quotation.
• Equipment-Side ODF Frame — use this product page as a configuration reference when you link splice and splitter relationships to test records. Confirm the offered model, interfaces, drawings and available evidence before quotation.

For adjacent configurations, browse ODN & Fiber Distribution and compare those options against the ODN as built records inputs above, including identifier convention.

Selection boundaries to verify

This table connects ODN inventory, automated identification, optical cross-connect governance, ODF capacity and auditable change control to the decision on ODN as built records. It is a decision aid rather than a universal performance table: exact capacity, environmental class, electrical or optical limits and certifications must come from the selected model, applicable project documents and verifiable test evidence.

Reference point: ITU-T L.207: Passive node elements with automated ID tag detection and ITU-T L.250: Topologies for optical access networks frame the terminology or method used for this ODN as built records comparison. They do not approve a product configuration; apply the edition named by the contract and local authority.

A practical product-selection workflow

1. Step 1: Define the operating scenario and document identifier convention. Record Identifier convention as an explicit input. Origin, destination, length and status.
2. Step 2: Map interfaces, installation constraints and required asset fields. Record Required asset fields as an explicit input. Port hierarchy, capacity and occupancy.
3. Step 3: Compare candidate configurations against the decision table and record exceptions. Record GIS or OSS interface as an explicit input. Test file, date, method and technician.
4. Step 4: Request model-specific drawings, ratings and test evidence before releasing the purchase specification. Record Test-record format as an explicit input. Origin, destination, length and status.

Common mistakes to avoid

• Selecting from a catalogue image before identifier convention is fixed.
• Treating a category-page description as model-specific compliance evidence.
• Leaving handover package undefined until after quotation.

What to include in the RFQ or design input

For ODN as built records, a complete request reduces back-and-forth and prevents a catalogue image from being mistaken for a verified configuration. Record the following fields, identify which values are mandatory or provisional and attach route, interface or layout drawings where relevant.

• Identifier convention
• Required asset fields
• GIS or OSS interface
• Test-record format
• Approval workflow
• Handover package

Sources and standards

The references below define terminology, scope or test methods relevant to ODN as built records. They do not certify an offered product; confirm the edition adopted by the contract and destination authority.

1. ITU-T L.207: Passive node elements with automated ID tag detection (03/2018; in force and reviewed 2026-10-16). Use it to verify the terminology and scope relevant to ODN as built records; the source does not certify a specific offered product.
2. ITU-T L.250: Topologies for optical access networks (01/2024). Use it to verify the terminology and scope relevant to ODN as built records; the source does not certify a specific offered product.
3. ITU-T L.208: Requirements for passive optical nodes — distribution box (08/2019). Use it to verify the terminology and scope relevant to ODN as built records; the source does not certify a specific offered product.

Source review: Links and cited editions for ODN as built records were checked on 2026-10-16. Confirm the edition adopted by the project contract and the authority having jurisdiction.

Related guidance

Intelligent ODN (IODN): Automated Identification, Inventory and Maintenance Workflow  •  24-, 48- or 72-Core ODF Unit: Working Fibres, Reserve and Patch Access  •  Jumper-Free Optical Cross-Connect Cabinets: Box, Cassette or Plug-In Architecture

——END——