Route alternatives and cost comparison

Compare existing infrastructure and new line options by distance, materials and cost.

Last updated: 10 November 2026

Prepare the comparison

Compare routes assesses planning alternatives between two endpoints. It can use existing infrastructure records and, with editing permission, proposed new trenches or aerial lines. This is separate from circuit path search, which follows connected fibers and ports.

Costs use the organisation's unit prices. An authorised organisation administrator manages these through Unit prices. Do not interpret an item without a price as having zero cost.

Create alternatives

1. Open Compare routes from the map tools.
2. Use Select on map for Endpoint A and Endpoint B; enter a node or coordinates if needed. Coordinate order is longitude, latitude.
3. Set Cable count, Wavelength (nm) and, if needed, Maximum distance (m).
4. Select the alternatives to compare: Lowest cost, Existing infrastructure and Shortest.
5. Complete Segments to avoid if needed.
6. To propose a new line, set New aerial line class, Surface or Sag (%), then use Draw new segment; finish with Use line.
7. Select Compare.

Read the result

Candidate cards show length, existing and new duct usage, aerial lines, poles and cost items. Inspect a candidate with Show on map. Under Difference table, read each alternative's differences against Baseline candidate; download the result with CSV.

If Missing price appears, complete the missing prices and repeat the comparison. In this situation, the Lowest cost candidate may have been generated by distance. Amounts are in TRY, excl. VAT.

Fiber loss is a preliminary estimate only. After creating the circuit, inspect Optical budget for splices, equipment and the complete circuit budget. If infrastructure occupancy warnings appear, check the relevant segment and duct records.

Transfer a selected candidate to a design

1. For a candidate containing proposed lines or ducts, select Write to design branch.
2. Enter Design name and an optional Description.
3. Use Write to design branch to create a separate design workspace.
4. Review the proposal there and follow validation, review and publication.

A comparison result alone does not change the base project. A candidate using only existing infrastructure, with no proposed records, may have no new line or duct to write into a design.