Skip to main content

NEXUS AI / WRITTEN FOR PLANNING AND ASSET-MANAGEMENT TEAMS

Asset ages in Smallworld. Unit rates in SAP. One answer.

The two halves of a replacement plan live in two systems, owned by two teams, reconciled by hand. Gateway connects both; Workspace answers across them and shares the result instead of exporting it.

Every budget season somebody rebuilds the same spreadsheet. Asset ages come out of the GIS, unit rates come out of the ERP, and the join happens in a workbook that nobody else can reproduce. The number that reaches the capital plan is defensible only by the person who built it, and they are on leave.

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

    Which distribution transformers are over 35 years old, and what are the current unit rates for replacing them?

  2. Nexus

    Reading asset ages from Smallworld and unit rates from SAP. 1,284 distribution transformers are over 35 years old. I can break the replacement programme down by feeder, by district, or by age band, with the SAP rate attached to each. Which do you want?

  3. You

    By district, oldest first.

  4. Nexus

    Here it is, oldest first. Nine districts, with the count, the age band and the rate against each. Do you want this as a report you can share with the planning group, or as a dashboard that updates as the SAP rates change?

  • Smallworld — asset ages, read through Gateway
  • SAP — unit rates, read through Gateway
  • The result consolidated in Workspace, shared with named people rather than exported

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