Skip to main content

NEXUS AI / WRITTEN FOR DESIGN AND ENGINEERING TEAMS

Place the point. Get back a project your GIS already accepts.

Connecting a customer is the same sequence every time, and most of it is not engineering judgement. Grid Planner collapses it to the part that needs a person.

Book a technical session Watch the 8-min walkthrough

A connection request arrives and a designer picks it up. 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. Hours each, every time, and the backlog decides how long a customer waits to be connected.

Illustrative exchange Written to show the shape of the interaction. Not a screenshot of a client system, and not a transcript of one.

  1. You

    New service at 14 Mill Road, 200 amp single phase. Point of connection is the pole on the corner.

  2. Nexus

    Marked. Generating the extension against your construction standards and the compliance rules configured for this territory. One moment.

  3. Nexus

    Here is the generated design on the map. It clears your business rules and the project standards. Do you want to look at it before I create the project in the GIS?

  4. You

    Looks right. Create it.

  5. Nexus

    Project created in the GIS and validated against its own rule set. It is available for approval and posting through your normal process.

  • The utility's GIS, through Gateway — the project is created and validated there
  • Your own business rules, project and construction standards, and compliance rules
  • Spatial Studio, where the generated design can be edited, exported and seen against every other layer

Grid Planner

Drop a pin where the customer is and get back a designed, rule-checked project sitting in your GIS.

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

Book a technical session