Skip to main content

NEXUS AI / WRITTEN FOR ENGINEERING TEAMS WHO OWN CONTRACTORS

A contractor's drawing, checked before it reaches the GIS.

Deliveries arrive in whatever the contractor's own tools produce. Project Import makes bringing them in a repeatable step instead of a redrawing job whose thoroughness depends on who picked it up.

Book a technical session Watch the 8-min walkthrough

Contractors, developers and engineering firms deliver designs in CAD, in geospatial exports, sometimes in a spreadsheet of coordinates. Each one has to be brought in, checked and turned into something the GIS will accept. Done by hand that is redrawing, and how carefully it is checked depends on who happens to be doing it that week.

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

    The substation feeder extension from Halcrow just came in. DWG, same as always.

  2. Nexus

    Imported. Running the analysis checks against it now.

  3. Nexus

    Checks complete. Most of it passes. Four items did not: three conductors with no specification against them, and one structure outside the project boundary. Nothing has been posted. Do you want the list?

  4. You

    Yes — and send it back to them.

  5. Nexus

    Here are the four. The rest is staged and ready to post to the GIS as a project with your validation attached, once the four are resolved or you decide to post without them.

  • The delivered design file — DXF, DWG, GeoJSON, shapefile, and tabular formats such as CSV
  • The utility's GIS, through Gateway — where what passes is posted as a project
  • The analysis checks and validation the utility requires

Project Import

Someone else’s drawing arrives as a file and leaves as a checked project in your GIS.

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

Book a technical session