An infrastructure conversation becomes more useful when it starts with endpoints and responsibilities. Dark fibre and managed capacity can place different equipment and operational duties on the customer. The correct choice depends on the project, not just a capacity target.
Write down the endpoints
Specify the actual facilities and handover locations, not only two city names. Record access arrangements, required interfaces and any existing equipment that the service must connect. A route description should identify the segments under consideration and distinguish confirmed availability from development opportunities.
Decide who operates the optical layer
For a dark fibre discussion, ask which party supplies, powers, monitors and maintains the optical equipment. For managed capacity, define the delivered interface and the provider’s operational boundary. Neither label alone explains maintenance access, spare equipment, fault isolation or the procedure for a change. Put those responsibilities in the scope.
Evaluate route evidence
Ask how the proposed route has been assessed and what remains to be confirmed. Where diversity matters, examine common facilities and physical segments as well as commercial providers. Cross-border work can involve several handovers; each needs its own technical and commercial review. Avoid treating a component’s performance specification as proof of an end-to-end route.
Agree what success looks like
Set out the required capacity, acceptance measurements, delivery dependencies and incident contacts before committing to an implementation schedule. Separate one-time deployment work from ongoing operation. A comparison sheet should include responsibilities and exclusions as well as prices, so that apparently similar proposals can be evaluated on equivalent terms.
PLANNING TAKEAWAY
Compare complete service responsibilities and verified route scope, not only fibre length or a bandwidth number.
ADNET’s public focus includes dark fibre, optical capacity and infrastructure development. Route feasibility and commitments are assessed for each project.
Sources & technical context
This guide supports early project discussions. It is general planning material, rather than a service quotation or a technical acceptance document.
