Asset management and work order systems for public works

Reference article · 5 min read

Public works departments ask their software two questions. One is about today: a hydrant is leaking, a lift station is in alarm, who was sent, and what it cost. The other is about the next twenty years: what do we own, what condition is it in, and what has to be replaced before it fails.

A computerized maintenance management system, or CMMS, is organized around work. An enterprise asset management system, or EAM, is organized around assets, with work as one of several things that happen over a long life. Both dispatch crews and close work orders. Only one is built to say what a collection system will cost over its remaining life. Agencies that skip the distinction buy a capable work order tool and find later that it cannot carry a capital plan.

Where a CMMS stops and an EAM begins

A CMMS covers request intake, work order creation and assignment, labor and material charges, crew time, storeroom inventory, and recurring tasks. For a facilities shop or a fleet garage, that may be the whole job.

An EAM adds a durable asset registry. Each asset carries a location, installation details where known, inspection and condition history, a criticality rating, accumulated maintenance cost, and an expected replacement. Work orders attach to assets rather than standing alone.

The asset registry and how it relates to GIS

One authoritative location. Let GIS own geometry for spatially located assets and have the maintenance system reference those features by a stable identifier.
Identifiers that survive change. Pipes get split and pavement is re-segmented. Ask how work and inspection history follows the asset when the underlying feature changes.
A hierarchy you will use. A lift station holds pumps, motors, controls, and a generator. Record work at the level crews can report, and let the hierarchy roll cost upward.
Assets that are not on a map. Fleet, shop equipment, and buildings belong in the same registry. Decide which system is the point of entry for a new asset.

Condition assessment and criticality scoring

Condition and criticality are different measures and belong in separate fields. Condition is the state of the asset. Criticality is what happens if it fails. Risk is the combination, and risk should drive the work plan.

Most asset classes have an established inspection method, and using one keeps results comparable over time and across jurisdictions. Pavement condition indexes, standardized defect coding for sewer television inspection, and bridge inspection practices tied to federal inventory requirements are examples. These protocols and the rules referencing them are revised periodically, so confirm current versions with the issuing body or your state program office.

Criticality scoring combines consequence factors, such as redundancy, customers affected, safety and environmental exposure, and emergency repair cost, with an estimate of failure likelihood. Keep the weights configurable by staff rather than by the vendor, and be ready to explain the model to a board asked to fund the result. The same records feed capital planning, rate studies, and, for agencies that report infrastructure using the modified approach, financial statements as well. Confirm those requirements with your auditor.

Preventive maintenance crews can actually complete

Calendar based. Fixed intervals, such as hydrant flushing, generator exercise, or sign inspection.
Meter or runtime based. Pump hours, vehicle mileage, cycle counts.
Condition based. Triggered when an inspection score crosses a threshold.
Regulatory driven. Backflow testing, cleaning frequencies written into a permit, storm drain inspections. These carry reporting duties, so the system must produce the record, not just the work order.

Ask whether schedules float from the completion date or stay fixed, since that changes crew workload after a catch-up period. Route based maintenance that puts many similar assets on one work order keeps the queue readable. A schedule that generates more work than crews can close builds a backlog that hides real deferred maintenance.

Offline mobile use in the field

Mobile means different things across products. Require the ability to download a work area to a device, create and edit work orders and inspections with no connectivity, attach photographs and GPS coordinates, and synchronize later with clear handling of conflicting edits. A responsive web page that fails in a vault or a rural corridor is not offline capability.

Name the rest of the field work too: asset lookup by tag or barcode scan, inspection forms matching the standard, creating an asset the registry missed, and redlines routed to the GIS team.

What to ask vendors and require in the contract

Show the cost history. Ask to see maintenance cost for one asset over several years, then for an asset class, then for a service area, with inspection history beside it.
Configuration or project. Ask whether adding an asset class or inspection form is configuration or a vendor project with a price.
GIS integration terms. Ask which direction data flows, how often, and whether integration is in the base license or a separate line item.
An offline acceptance test. Write it into the contract: a full shift of edits without connectivity, then a sync that reports conflicts rather than dropping them silently, run by real crews on the devices they will carry.
Your data. Require export of assets, work history, inspections, attachments, and configuration in a documented format, on demand and at termination.
Licensing and conversion. Be precise about named users, concurrent users, assets, or devices, and state who cleans and loads legacy records to what standard.

Start with one asset class that has a clear owner, a hierarchy and identifier scheme written down before data is loaded, and crews running real work for a season before the next class begins.

HQT builds and integrates systems of this kind, including GIS connected asset registries and offline capable field applications.

Frequently asked questions

What is the difference between a CMMS and an enterprise asset management system?

A CMMS is organized around work: requests, work orders, labor and material charges, inventory, and recurring tasks. An enterprise asset management system is organized around a registry of assets, where each asset keeps its own location, condition history, criticality rating, cost history, and expected replacement, and work orders attach to those assets. Many products market both capabilities, so judge them by the data model rather than the label. A simple test is whether the system can show lifetime cost and inspection history for one asset, an asset class, and a service area without exporting to a spreadsheet.

Does a public works asset management system have to integrate with GIS?

For assets that live in the ground or along the right of way, integration is usually the difference between a usable registry and a duplicate one. The common pattern is to let GIS own the geometry and location while the maintenance system references those features by a stable identifier and holds the maintenance attributes. Before selecting a product, decide which system is the point of entry for new assets, how often the two synchronize, and how work and inspection history follows an asset when a pipe is split or a pavement segment is redrawn.

How should an agency score asset criticality?

Criticality is about consequence of failure, not current condition, so keep it in separate fields from condition ratings. Most scoring models combine consequence factors such as redundancy, customers or population affected, safety and environmental exposure, and the cost of an emergency repair, with an estimate of how likely failure is. Document the factors and weights, keep them adjustable by staff rather than by the vendor, and make sure the resulting ranking can be explained to a governing board that is asked to fund the work.

What should we require for offline mobile use by field crews?

Write the definition into the requirements instead of accepting the word mobile. Ask for the ability to download a defined work area to a device, create and edit work orders and inspections with no connectivity, attach photographs and GPS coordinates, and synchronize later with conflicting edits reported rather than silently discarded. Test it during evaluation and again during user acceptance testing, using real crews, in the places where signal actually drops, such as vaults, basements, and rural corridors.