Skip to main content

NEXUS AI / GRID PLANNER

Drop a pin where the customer is. Get back a project in your GIS.

Grid Planner turns a connection request into a project. An engineer marks the point on the map; the pod builds the extension against the utility's own business rules, project standards and compliance rules, creates the project inside the GIS, validates it there, and leaves it ready for approval and posting.

Book a technical session See it running

Twelve seconds of the pod working. No sound, nothing to start, nothing to sit through.

Recorded in Grid Planner, working on sample data.

Watch the full recording

Connecting a new customer is the most repeated design work a distribution utility does, and most of it is not engineering judgement. It is the same sequence every time: find the nearest point of connection, lay in the extension, apply the standards, check it against the rules, build the project, route it for approval. Done by hand each one occupies a designer for hours, and the backlog sets how fast the utility can connect anybody.

  1. Place the connection point

    An engineer marks the point on the map — a new customer, an extension, added load.

  2. The extension is generated

    Against the utility's own business rules, its project and construction standards, and the compliance rules it works under. Not generic defaults.

  3. Review before it leaves

    The generated design appears on the pod's own map, where it can be looked at before it goes anywhere.

  4. The project is created in the GIS

    Not a drawing somebody has to redraw — a project inside the utility's GIS, validated against that system's own rule set.

  5. Available for approval and posting

    It then moves through the utility's normal approval and posting process. Grid Planner makes it available; your process decides.

The EXT001 preliminary LV extension package in Grid Planner, showing the package title, a description of three proposed pole structures and 292 m of secondary route, status chips reading preliminary issue, triphasic, 415 V and Smallworld synced, and buttons to download, share, email or print.
Where the five steps end up: a package, marked preliminary, synced to Smallworld.

A new customer connection

The most repeated design job there is, collapsed to the part that needs a person: deciding where the connection goes.

An extension, or added load

Same sequence, same standards, same validation — without a designer rebuilding it from first principles each time.

A connection backlog that sets the pace

When the queue decides how fast anyone gets connected, the sequence that produces each design is the thing worth shortening.

The preliminary design package, end to end.

Marked preliminary, and not for construction until a field survey has been done. The package carries that on its face rather than leaving it to be remembered.

Each connection is made by API or by a direct database connection, and is defined once rather than per project.

The utility's GIS, through Gateway
Direction: Read, and write — the project is created and validated there
Spatial Studio
Direction: Editing, export and import of generated designs
Workspace
Direction: Reports and indicators
Detail fields from the design package: service point, issue status reading preliminary and not for construction, nominal voltage 415 V, and source network recorded as an existing overhead transformer.
The fields the GIS and the approver both need, carried on the project rather than in an email.

Where it stops

  • Grid Planner makes a project available for approval and posting. Your own process runs the approval.
  • It is the front door, not a replacement for anything in your GIS. What it produces is a project your GIS's own design and quality tools carry through.
  • Compliance rules are yours. Grid Planner applies the rules you configure; it does not supply a regulatory regime.
  • The pod carries a map sized for this job. Seeing the design against every other layer is what Spatial Studio is for.

Who can see what

People sign in with the corporate directory account they already have, and what they are allowed to see is enforced in four places: at the platform, inside each pod, on the map, and in the answers that come back to them.

Where it stands

Available now

Grid Planner is the front door — where the request arrives and the design is generated — and what it produces is a project your GIS's own design and quality tools carry through approval and posting.

Technical walkthrough · 8 min

See it in action — watch the 8-minute Nexus AI Platform walkthrough.

Recorded directly in the platform, with English narration and no slide deck. GIS, ERP, ADMS, and maintenance answering together, without replacing the systems you already run. The link arrives after you register.

Watch the 8-minute walkthrough

Need to brief your leadership? The one-page brief

A technical session covers your estate, where the platform would run, and which pods come first.

Book a technical session