Skip to main content

NEXUS AI / WRITTEN FOR OPERATIONS AND MAINTENANCE MANAGERS

Where crews keep going back, on the same screen as the network.

Repeat visits are obvious in hindsight and invisible in a work-order list. Read alongside the network model, they stop being anecdotes about a bad feeder and start being a map.

Book a technical session Watch the 8-min walkthrough

Everybody knows the feeder that keeps failing. Nobody can show it. The work-order system lists visits and the GIS holds the network, and nothing joins them, so the case for doing something about it is made from memory in a meeting rather than from evidence on a map.

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

    Where have we sent crews more than three times in the last twelve months?

  2. Nexus

    Reading work orders from the maintenance system and the network model through Gateway. 46 locations had four or more visits in that period. 31 of them sit on six feeders. Do you want them as a list by district, or on the map?

  3. You

    On the map, grouped by feeder.

  4. Nexus

    Here. The six feeders are highlighted with the repeat locations marked against the assets they belong to. Interruption history from the non-operational copy lines up on four of the six. Want that overlaid?

  • The maintenance and work-order system — read through Gateway
  • The Smallworld network model — read through Gateway
  • ADMS — read only, from a non-operational copy. Nexus takes no part in operating the network

Gateway

Connect a system once and every pod can use it, so nothing has to be re-integrated project by project.

Workspace

Ask across every connected system in plain language, then share the reports and dashboards that come back rather than exporting them.

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

Book a technical session