Plan a new network
Define the service area, routes, endpoints, and capacity before field construction starts.
Fiber Optic Network & Infrastructure
Fiber optic design for backbone, feeder, FTTH, FTTB, and FTTx networks. Survey, HLD, LLD, core management, BOQ, and as-built documentation.
Define the service area, routes, endpoints, and capacity before field construction starts.
Review existing assets and available cores, then plan additional coverage and connections.
Align route drawings, splice records, and core allocation with the network as it exists in the field.
A cable route is only the beginning. LINK brings physical routes, optical paths, fiber allocation, and installation documents into one coherent design.
Backbone, feeder, distribution, and drop planning, with survey records for poles, ducts, closures, cabinet locations, and access constraints.
FTTH and FTTB planning within an FTTx strategy. Compare PON, dedicated point-to-point links, and protection options against the actual requirement.
Track cable IDs, tube/core allocation, splice trays, ODF ports, splitter inputs and outputs, and spare capacity from origin to endpoint.
Route drawings and core schedules should describe the same network. A consistent asset reference connects the cable, tube, core, splice, port, and endpoint so the design can be reviewed and maintained.
Explore the technical decisions behind your network. The final design follows your site conditions and agreed scope.
FTTx describes where fiber ends. We plan the feeder, distribution, drop, and building routes around the endpoints.
Fiber reaches the home or premises. Plan the feeder, distribution and drop path, terminal capacity, and customer termination.
Fiber terminates at a building entry point; the in-building network is defined separately. Extending fiber to each unit adds riser routes, floor distribution and unit drops.
Fiber stops at a curb-side cabinet or neighbourhood node. Document the fiber segment, active equipment, power requirements, and the final access medium.
Connect POPs and aggregation sites. Evaluate route diversity, fiber counts, expansion reserves, termination points, and the proposed protection mechanism.
Separate transport to distribution hubs, onward distribution, and the last connection to a premises. Keep cable and terminal identifiers consistent across drawings.
Plan optical routes between access sites, towers, offices, or aggregation points. Record endpoints, interface requirements, and available fiber infrastructure.
The service topology and physical cable route are separate decisions. We compare geography, capacity, fiber availability, maintenance, and recovery needs.
Multiple site-to-site routes provide path options for larger backbones. Compare fiber demand, route diversity, and the active network’s routing and protection behaviour; extra links do not remove shared infrastructure risks.
A linear route may use asymmetric taps to serve successive locations. Each tap changes the power available downstream, so evaluate the entire chain against equipment limits and maintainability rather than treating it as a standard equal-split tree.
A dedicated optical path connects endpoints. Useful where isolation or dedicated capacity matters; active equipment, fiber counts, and power need to be included in the design.
A passive splitter shares an OLT port among endpoints. Splitter location and staging affect loss, port utilisation, fiber demand, and maintenance access. GPON or XGS-PON selection follows the equipment and service requirements.
A physical loop offers possible alternate paths. Resilience depends on genuinely diverse routes and the matching active protection design; a ring drawing alone does not establish redundancy.
Combine routes to fit roads, geography, and demand. A linear cable route can carry several logical fiber paths; physical layout and optical service topology are documented separately.
Cable → tube → core → splice → port → endpoint. Every allocation is recorded against a consistent identifier so changes can be traced across drawings and installation records.
Define identifiers for cables, closures, cabinets, ODFs, ODPs, ports, and endpoints. Record location and revision so names remain consistent across CAD/GIS drawings and schedules.
Map each fiber by cable, tube, core number, and the project’s color convention. Mark working, spare, reserved, and unavailable fibers; color alone is not a unique asset ID.
Record incoming and outgoing cable/core pairs, closure and tray positions, express or midspan fibers, and termination points. Make each continuity change traceable.
Assign ODF panel and port references, splitter inputs and outputs, and ODP/terminal ports. Link these to upstream fibers and downstream drops to prevent duplicate allocation.
Trace a service path from its origin through every splice and patch to its endpoint. Reserve capacity for the agreed growth scenario and separate administrative reservation from physical availability.
Associate core paths with supplied test records, including direction and wavelength where available. Reconcile field deviations, retain source measurements, and issue a controlled as-built revision.
Review the design before construction, against equipment specifications, field conditions, and the agreed capacity.
Account for fiber length, connector and splice loss, splitter loss, and design margin. Check both maximum loss and receiver overload limits against the actual optics specification.
Review distance, expected subscriber take-up, split ratio, and shared capacity. A standard’s nominal rate is not a promised customer speed; equipment classes and deployment conditions matter.
Coordinate pole or duct access, cable slack, manufacturer bend limits, enclosure access, and building-entry constraints. Agree on inspection and test acceptance criteria before handover.
We agree on the scope before starting, then review the work with you at each stage.
Confirm coordinates, premises targets, existing assets, route feasibility, permissions, and the quality of the starting data.
Define the coverage, POP/OLT location, backbone and feeder routes, distribution areas, topology, and capacity assumptions.
Detail fiber paths, port and splice schedules, splitter placement, material quantities, and the optical checks required for each path.
Update drawings and records from actual installation changes and supplied acceptance results, keeping revisions traceable.
Choose a complete engagement or the stages you need. Deliverables are confirmed in the proposal.
Coordinates, asset inventory, route observations, photographs, and the constraints that inform the design.
Coverage and topology plans, major equipment locations, route layout, and capacity assumptions.
Detailed cable, core, splice, and port schedules with agreed naming rules and installation drawings.
Quantities linked to the design: cables, enclosures, termination hardware, splitters, and installation allowances.
Path loss estimates, equipment-specific limits, and margin assumptions documented for the proposed network.
Drawings and schedules reconciled to field changes, with test references where provided. Formats are agreed before work begins.
KMZ and documentation tools relevant to survey and planning workflows. The product catalog includes coordinate-to-boundary matching and photo-to-KMZ conversion.
sndapp.comTools for .sor file metadata, IOR, CRC, and event tables. Optical acceptance remains grounded in actual measurements and the agreed test procedure.
sor.sndapp.comSummaries of customer feedback.
The network survey and design process is quick. The team also responds promptly when we need help.
Yes. LINK can be scoped as a standalone stage or a complete package. We first check whether the available input data is sufficient for the requested deliverable.
No. Physical route diversity must be paired with the appropriate fiber paths, active equipment, protection design, and recovery behaviour. Two fibers in the same duct can share the same failure risk.
There is no universal ratio. Subscriber distribution, projected take-up, bandwidth sharing, total path loss, distance, and the specific OLT/ONT limits determine the design.
Provide the target area or route, homepass or endpoint targets, existing drawings and assets, equipment specifications, naming rules, required formats, and your project stage.
Tell us what you have in mind. We’ll help define the scope and the next step.