Design an LV or MV distribution network
The network designer turns reviewed site structures and design intent into distribution routes, poles, conductors, customer services and, where needed, transformer zones and an MV backbone.
A generated layout is a proposal with findings and assumptions. It becomes electrical model elements only when you commit it.
Before you run
Complete Site assessment and review the consumers to serve. Prepare the source location, demand basis, nominal voltages, conductor catalog, voltage and thermal limits, service-drop limits, route constraints and cost basis.
Background-map roads do not prove routing roads are loaded. Inspect the actual road and structure data. Treat absent terrain, land or equipment evidence as unknown.
Set the brief and run
- Open Network design from the plant workflow.
- Complete Design brief: answer What are you designing?, Where is the network fed from? and Who lays out the routes?
- Place the plant source or grid connection point. Review the intended LV/MV scope.
- Set the demand method and percentile. New runs can use the saved consumer-mix declaration; historical runs may retain RUS demand. Read that label before comparing totals.
- Set route corridors, exclusions and required paths as needed. Check proposed routes before a full design run.
- Review Parameters, including conductor, span, service, electrical and costing inputs.
- Select Run design. Follow the run status until it completes or reports a failure.
- Read the verdict and findings. Inspect unserved customers, voltage drop, thermal loading, route conflicts and the bill of materials.
Edit and compare
Use the map editing controls to adjust the supported layout or customer connections, then run the electrical/layout check. A moved pole can change lengths, service reach and costs. Read the new findings before accepting the change.
On a finished design, Rerun with conductor creates a separate alternative. Choose Every LV span or Only smaller spans, and Keep poles and routes or Re-route. Check the new run’s feasibility and bill. A smaller cable can be accepted as an evaluated alternative with violations; it is not thereby suitable.
With per-km costing, line rates cover the modeled installed line. Service connections and transformers are separate entries. Historical itemized designs retain their basis. Use cost recomputation when only unit prices change, then read the cost revision.
Commit and verify
Open the commit/electrical-check panel and inspect the proposed node, line, transformer and load counts. Read catalog assumptions and blockers.
Select Commit to model only when the proposed changes are the ones you intend. The commit creates electrical elements and runs a three-phase load-flow cross-check. Read whether that check converged and inspect the estimate-versus-PF3 gap and new violations.
Design estimates and solved bus voltages are different results. A completed routing run does not establish that the committed electrical model passes every check.
Resolve failures
| Failure | Next action |
|---|---|
| Required route fails before layout exists | Read the span and obstacle conflict; repair connected geometry, then check the route again. |
| Service is too long | Change the connection or route; the maximum service-drop length is a hard limit. |
| Site data are stale | Review the changed site and create a current run. |
| Some prices are missing | Supply reviewed rates or retain the unpriced/assumed status with the result. |
| Plant-site candidate has unknown land evidence | Treat it as screening; compare a separate run and obtain the missing site evidence. |
Use GIS and exports for QGIS, GeoPackage, GeoJSON and KML handoff. This is LV/MV distribution design, not tower, sag-tension, foundation or construction approval. Controls describe the September 2026 development build.