Planning & Serviceability

Evaluate service territories, mapped demand, nearest access nodes, distance risk, and expansion priorities.

Planning & Serviceability

Planning & Serviceability compares mapped demand with service territories and access nodes to identify expansion priorities.

Open Insights → Maps → Planning & Serviceability.

What the indicators mean

Indicator Meaning
Mapped demand Customer/demand records with usable coordinates
Serviceable Demand located inside a defined territory
Unserved Mapped demand outside defined territories
Access nodes Routers/OLTs available for proximity analysis
Build areas Saved service or planned territory polygons
Needs survey Estimated locations that are not construction-ready

The workspace displays mapped customers, serviceable and unserved demand, available access nodes, planned areas, and records requiring a field survey. Distance recommendations connect demand points to their nearest planning node and classify higher-distance candidates as warnings or critical opportunities.

Group administrators can draw a service/build territory with Draw service territory. Click the map to define the polygon, complete the shape, and give it a clear name.

Treat estimated or geocoded positions as planning signals—not construction-ready surveys. Verify coordinates, splitter capacity, PON budget, right-of-way, and actual cable route before approving a build.

Draw a build territory

  1. Select Draw service territory.
  2. Click around the boundary in sequence.
  3. Complete the polygon by clicking the first point.
  4. Enter a descriptive territory name.
  5. Refresh and confirm the polygon and demand classification.

Evaluate a service request

  1. Find the demand/customer location.
  2. Check whether it lies inside an active territory.
  3. Review its nearest node and straight-line distance.
  4. Confirm the node has suitable PON ports, splitter capacity, and optical budget.
  5. Conduct a route survey and record passive infrastructure in Custom Map Editor.
  6. Approve, redesign, or reject the build using verified field data.

Troubleshooting

Symptom Resolution
Covered count is zero Create service territories and verify customer coordinates.
Nearest node is unrealistic Add/correct Router and OLT coordinates; proximity uses available mapped nodes.
Distance differs from cable length Expected: recommendation distance is not a surveyed road/fibre route.
Polygon cannot be saved Use at least three points and ensure the logged-in role can manage territories.