Manage the network. Understand the area.
Pipes, roads and rail corridors extend over distance. Parcels, estates and operating zones cover an area. Lucendus connects their geometry with the assets, condition records and work that give a map operational meaning, helping teams investigate problems and plan activity in the right place.
Where disconnected records slow the work.
A point does not describe a whole asset
A single map pin cannot show which stretch of pipe has a different material, where a road defect sits or how far an inspection covered.
A map does not explain every connection
Nearby assets may belong to different networks. Teams need recorded connections and direction to follow a problem upstream or downstream.
Boundaries and work become disconnected
Site plans, parcel boundaries and asset lists can disagree. Staff spend time establishing which equipment and previous work belong to the area they are reviewing.
Connect distance, area and operational context.
Move from a location on a map to the records and relationships needed to investigate, maintain or renew the operation.
Linear records with meaningful sections
Store the geometry and measured length of pipes, roads and other linear assets. Record material or condition over defined sections without breaking the asset into a separate register entry for every change.
Locate work along the asset
Link defects, inspections, work orders and sensors to a position or range along a linear asset. Use chainage — distance along the asset — to give field teams a repeatable reference alongside the map.
Boundaries for parcels and operating areas
Represent land parcels, sites and operating areas with geographic boundaries and area records. Keep the place distinct from equipment located there, so replacing an asset does not replace the history of the site.
Queries across the network
Follow recorded connections upstream, downstream or in both directions. Use configured stopping rules to examine the relevant part of a network and relate the result to maintenance and service decisions.
Find assets by their spatial relationship
Search within a mapped area or by proximity, and identify the area containing a point or asset location. Compare geographic results with recorded location assignments when checking records or planning work.
Connect signals to a place and a response
Link sensor information to its asset and network context. Bring the relevant history into an investigation, then record inspection or maintenance work against the affected asset or section.
A sewer level rises within a council service area.
The operator needs to understand the connected network and the work already recorded around the sensor.
The team starts with the sensor and its linked manhole or pipe. The linear record identifies the relevant section, while upstream and downstream queries show the recorded connections to investigate. The service-area boundary provides geographic context for the response.
Operators review nearby readings, pipe condition and previous work before assigning an inspection or cleaning task. The crew records where it worked and what it found, preserving a useful reference for the next investigation.
The same approach supports road inspections by distance and maintenance planning across estates or utility sites. Network connectivity and spatial context help narrow the investigation; they do not establish the cause of an event on their own.
Start with trusted geometry and clear relationships.
Agree the authoritative GIS or survey source, asset identifiers, measurement reference and area boundaries. Validate network direction and any stopping rules against operational knowledge. A network trace follows recorded connections; it is not a hydraulic simulation or a certified isolation plan. Spatial containment describes geometry, not legal ownership. Confirm query coverage and incomplete results before using them for field decisions.
Start with a workflow your team knows.
Choose one network or operating area
Start with a pipe catchment, road corridor or estate where the team can validate records and recognise gaps.
Connect the records to the map
Bring geometry, asset identifiers, section attributes and boundaries. Agree how inspections, sensor locations and work will reference them.
Prove a practical query
Trace one connection or find assets in a known area. Check the result with the people who maintain it and use the findings in a real planning workflow.
Connected capabilities
- CapabilityAsset RegistryOrganise equipment, infrastructure, IT and biological assets with Lucendus. Connect asset identity, location, classification and work history in one registry.
- CapabilityAnalytics & AlertsConnect operational reports, asset context and alert response with Lucendus. Review the underlying work and assign responsibility for what needs attention.
- CapabilityServicingConnect planned maintenance, repairs, inspections and service response with Lucendus. Keep work orders, assets and completion history together.
Explore Linear and Areal Assets with your team.
Bring a network extract or site boundary and a recent inspection, sensor event or maintenance task. We can explore how distance, area and connected records would support your team.