NEXUS AI / WRITTEN FOR GIS DESIGNERS AND TECHNICIANS
500 poles from a design package, by instruction.
A designer describes what the package contains. Assistant creates the assets inside Smallworld, checks them against the network and your design rules, and stops before posting anything that failed.
A design package lands and someone types it in. Five hundred poles, one at a time, against standards that live partly in a manual and partly in people's heads. The mistakes surface weeks later, in a version that has moved on, in front of someone who cannot ask what was meant.
-
You
Create the poles from the design package for feeder 4412 — 500 of them, standard spacing, class 3.
-
Nexus
I can create 500 poles on feeder 4412 from that package. Before anything is posted I will check network connectivity and run your design-standard rules against them. Go ahead?
-
You
Yes.
-
Nexus
Created in the design version. 497 passed every rule. Three are flagged: two sit outside the right-of-way boundary and one has no upstream connection. Nothing has been posted. Do you want to look at the three?
- The Smallworld network model — read, and written to a design version
- Your own design-standard and connectivity rules
Assistant
Designers ask in plain language and the work happens inside Smallworld, with network integrity checked before anything is posted.
A technical session covers your estate, where the platform would run, and which pods come first.
Book a technical session