The technical director of a seventy-person engineering firm in Zaragoza wraps up, in October, the asset inventory of a 120-hectare private business park: roads, street lighting, storm and foul sewers, hydrants, two transformer substations and signage. Six weeks of fieldwork, just over 4,000 elements and a clean GeoPackage with a documented data model. The park's management company receives it happily and asks the question nobody raised when the job was quoted: how do we load this into the CMMS our maintenance contractor uses?
The answer comes a week later. The CMMS accepts assets as rows in a table, with an address field and, at best, a single coordinate. Sewer pipes, road sections and green areas have nowhere to go. The contractor ends up keying in the point assets it cares about, with different codes, and the rest of the inventory stays in a shared folder.
Three months later, the management company asks the engineering firm to update the inventory. Nobody has touched the GeoPackage since delivery, the contractor's work orders do not carry the asset code, and the photos from each job are on the technicians' phones. The deliverable has become a snapshot that is ageing, and the chance to provide a recurring service around it has gone.
Three families of tool and what each leaves out
The first family is the general-purpose CMMS without mapping. It was built to maintain machines inside a plant, where an asset's location is a line and a bay. It handles the work order cycle, the preventive plan and the stores well, but treats location as text. When a map is added, it is usually a tab with markers that slows down as soon as the inventory grows, and it has no idea what to do with a two-kilometre line or a four-hectare polygon.
The second is the GIS without work orders. Geometry is flawless and spatial queries are instant: what is inside this plot, what is within two hundred metres of a fault. But there is no work order life cycle, no response time agreed with the client, no materials consumed, no cost per job. Data collection forms help to gather information, but a form is not a work order: it is not assigned, not scheduled and not closed with its cost.
The third is the enterprise asset management suite, which can cover both sides at the price of a separate GIS licence, an integrator and an implementation measured in quarters. For a mid-sized private operator, or for an engineering firm's portfolio, that effort is rarely justified.
Why it is a data model problem, not a screen problem
The usual temptation is to integrate: the GIS keeps the geometry, the CMMS keeps the work orders, and a process syncs them by asset code. It works for the first month. Then a technician corrects the position of a manhole in one tool and not the other, someone creates an asset in the CMMS with no geometry, and the code stops matching in a small percentage of cases nobody checks. After a year there are two versions of the truth about the same estate.
The root cause is that in one system the asset is a row with attributes and in the other a geometry with attributes. Until the asset drawn on the map is the same record that is assigned in the work order, consumes material and feeds the indicator, every figure needs a manual reconciliation. Outdoors that happens more often than in a plant, because the inventory changes with every works project, every extension and every field discovery.
What the engineering firm loses with each option
For an engineering or technical consultancy, the cost is not only in the client's tool. It is in the hours the project did not plan for. An illustrative example: if each annual update of a 4,000-element inventory takes two weeks of a GIS technician's time to reconcile what the GIS says with what the CMMS says, those two weeks recur every year, are rarely billed in full and add no new knowledge. They are pure rework.
The second cost is lost position. A firm that delivers an inventory the client cannot use is remembered as the supplier of a document, not as the partner who knows the condition of the estate. Continuity, whether as inventory updates, technical support to the maintenance contractor or audits of the preventive plan, depends on the deliverable staying alive inside a tool that people use every day.
What to require from maintenance software with GIS
With outdoor assets, a CMMS with GIS should meet a few verifiable conditions. It should store real geometry, points, lines and polygons, not just one coordinate per asset. It should import the formats an engineering firm works with, without retyping. The map should be the working screen and stay fast with a hundred thousand elements. It should allow spatial queries on assets and work orders together. The work order should be created, carried out and closed on the geolocated asset, with its cost. The technician should see the map on the phone without coverage. And the data should come out complete, geometry included, the day you want to take it elsewhere.
What Maptainer provides is exactly that combination: the inventory is stored as real geometry in PostGIS and imported from GeoPackage, Shapefile, GeoJSON, DXF or CSV; work orders, agreed response times, stores and the cost of each job live on the same data model; the corporate GIS can stay in use, with its WMS layers loaded inside; corrections proposed by technicians from the app arrive as requests that a manager approves; and the full export delivers assets, incidents, work orders and photos. For an engineering firm, that turns the delivered inventory into the basis of a service that continues after handover.
Questions for the next proposal
Before quoting for an inventory, ask the client where that data will live in six months and who will maintain it. If the answer is a CMMS without mapping, the proposal should explain how the fit will be solved, or accept that part of the work will be lost.
And before recommending a tool, five questions to the vendor save trouble. Whether a GeoPackage with lines and polygons can be imported without turning them into points. How many elements the map can handle before it paginates. Whether the technician sees the map and asset record without coverage. How field corrections return to the inventory, and who validates them. And whether the export delivers everything, geometry included, or just a table. Written answers say more than any demonstration.