← Blog

Does your CMMS think every asset is a box? Most of your infrastructure isn't.

The assumption that assets are discrete objects is fine for simple operations environments but it falls apart the moment your operation includes the two kinds of asset that most asset-rich businesses actually depend on: the ones with length, or area.

Open most maintenance systems and you'll find the same hidden assumption: an asset is a discrete thing you can walk up to, tag, and photograph. A pump; truck; rooftop AC unit. A box.

That assumption is fine for simple operations environments but it falls apart the moment your operation includes the two kinds of asset that most asset-rich businesses actually depend on: the ones with length, or area.

Think about what a water utility really owns. Sure, there are pumps and valves. Boxes, essentially. But the thing that keeps the town in water is a network: mains and branches and risers, each segment with its own material, age, and condition, connected in a topology where a failure has downstream consequences. Think about a council, a food processor, a forrest commission, a vineyard, a rail operator, or a property portfolio. Their most valuable and most regulated assets are pipes, cables, ducts, roads, drainage runs, parcels, zones, permit boundaries. Lines and areas. Not boxes.

So where does all of that live today? In my experience, one of three places:


  • A GIS that the operations team can look at but often can't directly update due to seat license restrictions, and is owned by a different department on a different budget.
  • A consultant's drawing — a PDF, a CAD file, an as-built from a project that finished years ago. A static picture from who-knows-when instead of a living document.
  • A spreadsheet. Again a document of unknown provenance. Or perhaps just someone's memory.


None of those are the system where the work orders, the sensors, the technicians, and the history live. So the richest part of the asset base is disconnected from the day-to-day of running it.

Why the market left this gap

This isn't an oversight — it's economics. Modeling linear and areal assets properly has, until now, meant one of two things: an enterprise EAM platform like IBM Maximo or SAP (with linear asset management as a separately-licensed module); or a collection of disjointed vertical apps and add-ins coupled with a separate GIS program. Eye-watering licensing fees, long implementations, specialist staff or consultancy bills. That's viable for a national rail network or a Tier-1 utility. It is completely out of reach for the small-to-mid-sized operators who, collectively, run most of the world's actual infrastructure.

So those operators did the rational thing: they bought a lightweight CMMS that models boxes, and they kept their networks and land somewhere else. The tool and the reality diverged, and everyone learned to live with the gap.

What changes when all three live together

The premise behind Lucendus is simple to say and hard to build: point, linear, and areal assets as first-class citizens in one registry and that's the same registry the work, the telemetry, the people, and the audit trail already use.

Concretely, that means a water main isn't a line on a separate map. It's an asset. It has segments, each with its own condition. It's bound to the zone it serves and the crew that maintains it. When a sensor flags pressure loss, the event lands on the asset, not in a different silo. A parcel or a compliance zone is an asset too, with real geometry, not a note in a text field. One source of truth, three geometries, no six-figure GIS project bolted on the side.

And alongside that place and shape awareness, every ticket, observation record, event, reading, and more includes place references and route planning between places.

The question worth asking

If you run an asset-rich operation, here's a diagnostic I'd offer: what fraction of your asset base is boxes, and what fraction is lines and areas? Then ask where each fraction lives, and whether the people doing the work can see it.

If place, shape, size, or network is part of your asset picture, then it should be baked into every dimension of your operational tooling. Otherwise, that gap is costing you in response time, in institutional knowledge, and in the quiet tax of reconciling systems that were never designed to understand that critical dimension of daily operations.

It doesn't have to be that way anymore, and it doesn't require an enterprise budget to fix.

Lucendus is the Operations Intelligence Platform for asset-rich SMEs unifying assets, maintenance, service, and spatial intelligence in one system. If your infrastructure is more than a collection of boxes, we'd be happy to show you what a unified solution looks like. sales@365mesh.com