Fiber and project glossary
Use map, fiber connection, design, field work and optical measurement terms consistently.
Last updated:
On this page
How to read the termsMap and physical infrastructureFiber connectionsDesign and field workOptical and address recordsHow to read the terms
Bold names in this guide identify interface fields or buttons. Explanations use technical concepts; different screens may show different details of the same record. For example, the action labels Fiber strand assignment and Fiber strand record are retained, while the cable form field is Fiber count. This glossary explains how the names relate.
Map and physical infrastructure
| Term | Meaning and related topic |
|---|---|
| Node | A map point where cables can terminate or equipment can be placed. Not every point type accepts the same connections. Interface. |
| POP / Exchange | A facility point type for fiber equipment and connections. It is not a business or subscriber record. Drawing. |
| Field cabinet | A connection point with a map location to which equipment and cable endpoints can be linked. Fiber cables. |
| Splice closure | A node type recording cable fiber splices and equipment arrangement. Placing it in a manhole is separate from drawing it at the same map location. Shared site infrastructure. |
| Segment | A line section, such as a trench route or aerial line, through which other infrastructure records may pass. Segment length is not the sum of the lengths of cables passing through it. Quantities. |
| Route | An ordered relationship with the segments a cable or duct passes through. Geometric overlap does not create it automatically. Shared site infrastructure. |
| Subduct | A numbered passage within a duct, used in cable routes. It is placement information independent of the line geometry. Shared site infrastructure. |
| Location quality | Positioning method, confirmation and accuracy if known. Moving a point is not field confirmation. Drawing and editing. |
Fiber connections
| Term | Meaning and related topic |
|---|---|
| Fiber | A single optical transmission element inside a cable. Both Turkish “lif” and “kıl” mean fiber. Fiber count gives the cable total; Fiber strand record and Fiber strand assignment name actions on one fiber or a fiber range. Fiber assignment. |
| Tube | A section grouping fibers inside a cable. Colours help read records; the physical cable colour arrangement requires separate verification. Fiber cables. |
| Splice tray | Equipment that organises splices in slots. Tray placement is separate from connecting fibers. Splice diagram. |
| ODF | A panel recording fiber terminations and patch connections through ports. The interface label is ODF / patch panel, with Rear (termination) and Front (patch) faces. Splice diagram. |
| Rack | Parent equipment containing other equipment. U position and height describe physical placement; they do not independently verify field conditions. Splice diagram. |
| Port | A numbered equipment connection endpoint. Its type may also require face or direction information; the number alone does not identify the endpoint. Splice diagram. |
| Anchor | A specific fiber endpoint or equipment port used as the start or end of circuit search. It is not the same as the node itself. Technical circuits. |
| Technical circuit | A technical path formed by saved connections between two anchors. It is not a subscription or live service monitoring record. Technical circuits. |
| Constrained path | A circuit path searched for under selected traversal and avoidance conditions. The result depends on recorded topology and entered conditions. Technical circuits. |
| Shared risk | A shared dependency found in records, such as primary and backup paths using the same physical record. Finding no shared risk does not prove field independence. Technical circuits. |
Design and field work
| Term | Meaning and related topic |
|---|---|
| Design branch | A separate workspace prepared from the base project. Changes reach the base project through review, approval and publication. Design and approval. |
| Baseline | The base project to which a design belongs. Baseline advanced means it changed while the design was being prepared. Design and approval. |
| Work package | A record bringing together construction and handover tracking for a published design. It is not a general crew dispatch or support ticket system. Work packages. |
| As-built | Comparison of actual post-construction records with planned records. Differences and omissions are reviewed separately during handover assessment. Work packages. |
| Field package | Records for a defined area prepared for work on a device. Synchronisation and office review are separate from publication to the base project. Offline field work. |
Optical and address records
| Term | Meaning and related topic |
|---|---|
| Optical profile | Defines assumptions used in a calculation, such as fiber and connection losses. A profile and a measurement are different data. Optical budget. |
| OTDR | An optical line measurement approach assessed through distance and event information. A fault location on the map is an estimate calculated from the entered distance. OTDR positioning. |
| SOR | An optical measurement file from which supported metadata and event information can be read. Attaching it does not mean it has been parsed and applied to the record. Optical budget. |
| Unit | A planning record such as a flat or business premises within a building. It is not the same as the building record. Unit import. |
| Potential | A planning value based on building and unit information. An unknown value differs from a known zero. Addresses and buildings. |
| Technical endpoint | A demand or connection target that can be associated with infrastructure. An address declaration does not automatically create a connected technical endpoint. Addresses and buildings. |
For your first use, follow Your first workflow; keep the interface page open for screen names.