What the Major Work and Asset Management Systems Actually Do After an Alarm

At 02:10 a high level alarm comes in from a lift station at the edge of the collection system. The on call operator acknowledges it, drives out, and finds one of two pumps tripped on overload with the wet well rising. By 03:00 the pump is out and the failure mode is clear enough to act on. By 06:00 nothing further has happened, because the seal kit is a special order, the person who can authorise a same day purchase is asleep, and the record of the last time this pump did this is in a work order that nobody can find.

Software was involved somewhere in that sequence. Which software, and what it actually did, is the subject of this guide.

This is a comparison of the major work and asset management systems a US water or wastewater utility is likely to be choosing between, written to be useful to somebody who will not buy anything from us. We publish it because the pages that currently answer this question are software listing directories whose shortlists are assembled from review volume and buyer co-consideration data rather than from any question about the work, and because a municipal buyer deserves a description of each product by what it is designed to do.

The question the comparison sites answer, and the one you actually have

Search for “Cityworks alternatives” and you will land on listing sites. It is worth looking at what they return. On 5 September 2026, SoftwareSuggest’s Cityworks alternatives page listed, in order: Software AG, Workiva, Cygnet Tax, QuickBase, Wipro, Intelex, GovPilot, Accela, NEOGOV and AMANDA. Workiva is financial and regulatory reporting software. Cygnet Tax is an indirect tax compliance product. Wipro is an IT services firm. NEOGOV sells human resources software to the public sector. By our reading, three of the ten are in a comparable business to Cityworks.

That is not a scandal, and it is not paid placement. SoftwareSuggest states on the same page that its ratings and reports contain no paid placements, and that alternatives are selected using buyers’ survey answers to which other vendors they considered, together with total review volume in the market. That is a method, and it is a perfectly reasonable one. It is simply not a procurement method, and it does not know what job you are trying to do. The consequence is that the first page of results for a genuine buying question is not a shortlist of products that do the same job, and a utility that treats it as one will spend weeks on demos that were never relevant.

The better question is not which of these is best. None of them is best, because they are not competing on a single axis. They differ in what they are authoritative over, what they hand off, and where they stop.

Three questions that decide this better than a feature grid

Which system holds your authoritative asset register today? For a large share of US water utilities the answer is Esri ArcGIS, because the pipes, valves, hydrants and manholes were mapped there first and every subsequent record hangs off that geometry. If that is true for you, a GIS centric product is not a preference, it is an architectural fit. If your authoritative register is a plant equipment list in an enterprise system, the fit runs the other way.

What has to happen in the first hour after an alarm, and who does it? Write down the actual sequence for a real incident from the last quarter. Who created the work order. Who found the drawing. Who checked the shelf. Who called the supplier. Who approved the spend. Then ask each vendor to show that exact sequence in their product, using your asset. The answers separate these products much faster than a feature matrix does.

What happens at the boundary where the system stops? Every product in this guide has a boundary. Some stop at the work order. Some carry a requisition into a financial system. None of them carries the repair across every system it touches. Knowing the boundary before you sign is the difference between a system that works and a system that gets blamed.

A note on names, because several of these changed recently

Several of the products here are mid rename, which matters when you write a specification or search for references.

Cityworks is being consolidated by Trimble into Trimble Unity Maintain, which Trimble’s product page presents as the future of Cityworks and AgileAssets and describes as the same ecosystem, with the locally installed Cityworks version being sunset in favour of the cloud product. Cityworks PLL, the permitting and licensing side, is now sold as Trimble Unity Permit, which Trimble’s page describes as “powered by the trusted capabilities of Trimble Cityworks PLL”.

Brightly Software is now Siemens Asset Management Software, announced in a Siemens post dated 14 July 2026 and at Siemens Transform the following day. Siemens states that the solutions, products and people customers rely on remain the same under the Siemens brand; Asset Essentials is still sold under that name on Siemens’ own product pages.

Cartegraph is now sold as OpenGov Enterprise Asset Management. OpenGov’s own product page no longer carries the Cartegraph name, though the capability listings and review sites still do.

Lucity is sold as CentralSquare Asset Management, powered by Lucity. Both names remain in circulation, sometimes in the same proposal.

The practical consequence is small but real: put both the old and new names in your solicitation, or you will exclude a bidder by vocabulary and fail your own reference checks.

The comparison

Product	Owner today	Typical fit	Authoritative over	First hour after an alarm
Trimble Cityworks, moving to Trimble Unity Maintain	Trimble, which announced the acquisition of Azteca Systems LLC, doing business as Cityworks, on 3 October 2019	Cities, counties and water or wastewater utilities whose asset data already lives in Esri ArcGIS	The work order, inspection and service request record tied to the GIS asset. Trimble states that the GIS remains the authoritative source of truth for asset data	A service request or work order is opened against the mapped asset. Trimble’s product page states that real time IoT sensor data, through ArcGIS Velocity, can trigger a work order automatically
IBM Maximo Application Suite	IBM	Larger utilities and multi utility enterprises with in house IT and a formal reliability programme	The enterprise asset register, work management, job plans, inventory and purchasing records	IBM’s documentation describes measurement points that set acceptable ranges for meter readings on an asset or location, and states that work orders can be generated when readings fall outside those ranges. Otherwise a person raises it
Asset Essentials	Siemens, which acquired Brightly Software in 2022 and retired the Brightly brand in July 2026	Mid sized public agencies, school districts, municipal departments and utility operations groups	Work orders, preventive maintenance schedules, asset records and parts inventory	A work request from operations becomes an assigned work order with priority and crew. Siemens’ product page also describes asset threshold monitoring using IoT sensors
Cartegraph, now OpenGov Enterprise Asset Management	OpenGov; Cox Enterprises took majority ownership in a transaction announced 27 February 2024	Small to mid sized cities, counties and public works departments, including water, wastewater and stormwater	Asset inventory and condition, work orders, service requests and capital planning scenarios	A service request, resident report or inspection finding becomes a work order on the mapped asset
Lucity, sold as CentralSquare Asset Management	CentralSquare Technologies, which acquired Lucity on 8 January 2019	Municipalities already running CentralSquare for finance, permitting or public safety	Public works work orders, requests, preventive maintenance and asset records, GIS enabled	Request intake becomes a work order against the GIS asset, inside the same suite as the rest of the agency’s records
eMaint	Fluke Reliability; Fluke is a Fortive operating company	Plants and utility operations groups that also use Fluke condition monitoring hardware	Work orders, preventive maintenance, parts, and condition readings against equipment	Fluke states that condition data crossing a defined threshold can open a work order, with sensor readings on the same record
Limble	Independently held; founded 2015 in Lehi, Utah; Goldman Sachs Asset Management led its 58 million dollar Series B in June 2023	Small to mid sized maintenance teams that want fast adoption on phones	Work orders, preventive maintenance, assets and parts	A request raised from a phone or an asset QR code becomes a work order and notifies the assignee
MaintainX	Autodesk, which completed its acquisition on 3 August 2026	Frontline and mobile first maintenance teams across facilities and industry	Work orders, procedures, assets, parts and the message trail attached to the job	A request becomes a mobile work order with the procedure attached, and the conversation stays on the record
Fiix	Rockwell Automation, which states that the transaction closed in December 2020	Industrial plants and utilities with a Rockwell control estate	Work orders, preventive maintenance, assets and parts, with industrial data connections	Fiix’s own page states that asset fault codes from eligible Rockwell devices, surfaced through FactoryTalk Optix, can create the work order, and that run hours or condition data can trigger one

Ownership sources for every row are in the Sources section. Product behaviour in the last column is drawn from vendor documentation and product pages; where a behaviour is asserted only by the vendor, the wording says so.

What each one is

The utility work and asset management group

Trimble Cityworks was built around a simple architectural decision: the GIS is the asset register, and the work management application reads and writes against it rather than keeping a parallel list. Trimble announced its agreement to acquire Azteca Systems, the company behind Cityworks, on 3 October 2019. Its strongest characteristic is that it does not ask a utility to duplicate its network. If your valves, mains and manholes are already correct in ArcGIS, the work history attaches to the same features your engineering and planning staff already use. It reaches past maintenance into inspections, service requests, capital projects and, through Trimble Unity Permit, permitting and right of way.

Cartegraph, now OpenGov Enterprise Asset Management, serves a similar public works audience with a different centre of gravity. It sits inside OpenGov’s wider government cloud, alongside budgeting, procurement and permitting, which is the argument for it: the asset and work records live next to the money records. OpenGov announced its acquisition of Cartegraph in July 2022, and Cox Enterprises took majority ownership of OpenGov in a transaction announced on 27 February 2024 at a reported 1.8 billion dollar valuation. It integrates with Esri GIS rather than being built on top of it, and it is commonly chosen by agencies that want condition scoring and capital scenario planning alongside daily work orders.

Lucity, sold as CentralSquare Asset Management, is the third of the public works specialists. CentralSquare acquired it on 8 January 2019 and positions it as the asset management component of a suite that also covers finance, community development, utility billing and public safety. Its strongest characteristic is consolidation: for an agency that already runs CentralSquare, asset management arrives inside a system its finance and clerk staff already administer. CentralSquare is privately held and backed by Bain Capital and Vista Equity Partners, among other investors.

Enterprise asset management

IBM Maximo, now sold as the Maximo Application Suite, is the heavyweight. It is a full enterprise asset management system covering the asset lifecycle from procurement through condition monitoring, reliability analysis, regulatory compliance and decommissioning, with modules for monitoring, health and prediction layered on top. Its strongest characteristic is depth and configurability. That is also its cost: Maximo repays utilities that have the internal capability to configure and maintain it, and is expensive to own without that capability. In the first hour after an alarm, IBM’s documentation describes measurement points that set acceptable ranges for meter readings on an asset or location, and work orders that can be generated when a reading falls outside the range. That is a genuinely automated path, and it is bounded: what it produces is a correctly formed work order.

Asset Essentials, now under the Siemens brand, sits between the public works specialists and the enterprise systems. Siemens acquired Brightly Software, formerly Dude Solutions, in a sale that completed in August 2022, and retired the Brightly name in July 2026 while keeping the product names. Its audience is concentrated in education, government, healthcare and facilities, which shapes it: it is strong on preventive maintenance programmes, work request intake from non technical staff, and reporting that a governing body will read. For a municipal utility that also maintains buildings, fleet and grounds, that breadth is the point.

The broader CMMS field

Four products belong to a different lineage. eMaint is the oldest of them, founded in 1986, acquired by Fluke in 2016, and now sold by Fluke Reliability, whose condition monitoring hardware feeds it directly. Limble and MaintainX are the mobile first generation, designed so that a technician with a phone can raise, complete and document work without training, and both have grown on that strength; Autodesk completed its acquisition of MaintainX on 3 August 2026, and Limble remains independently held. Fiix is owned by Rockwell Automation and sits inside Rockwell’s maintenance software portfolio, with the distinctive property that machine signals from eligible Rockwell devices can reach it through FactoryTalk Optix.

These are competent products, and for a small water system with a few dozen assets and no GIS programme, one of them may well be the right answer. The honest caveat is in the next section.

Where a utility system and an industrial CMMS genuinely differ

The difference is not quality. It is what the software assumes about your assets and your obligations.

Linear and geographically distributed assets. An industrial CMMS assumes equipment: a numbered pump, in a numbered building, with a maintenance history. A water utility also maintains hundreds of miles of main, thousands of service connections and dozens of lift stations spread across a county. Work is located as much as it is equipment referenced, crews are dispatched to coordinates, and a repair is often described by a segment rather than an asset number. Products built for utilities model that natively. Products built for plants can be made to model it, at a cost you should measure during evaluation rather than after.

Esri integration as architecture, not as a feature. There is a real difference between a product whose work orders are written against ArcGIS features and a product that synchronises with a GIS on a schedule. Both are legitimate. Only the first keeps one copy of the network. Ask which one you are buying, and ask what happens when the GIS team edits the network mid repair.

Public sector procurement and records. A municipal utility buys under a purchasing ordinance, publishes an agenda item, and answers public records requests. Software that has lived in that world tends to have the audit trail, retention behaviour, role separation and reporting a clerk and an auditor expect. Software that has not can usually be configured to comply, but the burden moves to you.

Scope beyond maintenance. The utility products extend past maintenance into service requests from residents, inspections, permits and right of way. That matters because the alarm at 02:10 is only one of the ways work arrives. A caller reporting a wet spot in the street is another, and in most utilities it is the more common one.

The honest common ground: every one of these is a system of record

This is the most important thing in the guide, and it is true of all nine products.

A system of record is the authoritative place a fact lives. The work order number, the asset it was written against, the labour hours, the parts issued, the completion date and the person who closed it. When a regulator, an auditor, a rate consultant or an attorney asks what happened, the system of record is the answer, and everything else is hearsay.

That design has properties that look like limitations and are not.

A system of record is conservative on purpose. It waits for a human being to assert a fact before it stores one, because a record that the software invented is worse than no record. It is structured around the transaction rather than the incident, because the transaction is what has to be auditable. It optimises for completeness at closeout rather than speed during the event, because the closeout is what has to survive ten years and a change of staff.

For a water utility those properties are not negotiable. Your discharge monitoring reports, your asset valuation, your capital plan, your rate case and your defence in a claim all rest on maintenance records being correct rather than fast. Any vendor who offers to make your system of record more permissive is offering you a problem.

It is also worth being clear about what these systems are not authoritative over. In most utilities the financial system of record is the ERP or the finance module, not the maintenance system. The requisition may start in the work order and it is approved somewhere else. That boundary is where a large share of repair delay lives.

What none of them is designed to do

Between the alarm and the closed work order sit a set of activities that are nobody’s product.

Reliability engineering has a vocabulary for this, and it is older than any of these products. IEC 61703, edition 2.0, dated August 2016 and adopted in Europe as EN 61703:2016, gives mathematical expressions for terms defined in the international dependability vocabulary, IEC 60050-192:2015. Its contents list treats the following as separate measures with separate clauses and separate vocabulary entries: mean repair time [192-07-21], mean active corrective maintenance time [192-07-22], mean time to restoration [192-07-23], mean administrative delay [192-07-26] and mean logistic delay [192-07-27], at clauses 6.4.19 through 6.4.23. The standard is telling you something plainly. The interval from fault to restored service is not one quantity. It is repair time plus the delays that surround it, and administrative delay and logistic delay are named, defined and measured separately because they behave differently.

There is a vocabulary trap inside that list, and it is worth knowing before you write a specification. In IEC usage, MTTR is mean time to restoration, which contains the delays. Mean repair time is the repair alone. A utility that reports “MTTR” without saying which measure it means is publishing two different numbers under one label. When a lift station pump takes thirty hours to return to service and three of those hours were spent working on the asset, the remaining twenty seven hours sit in the delays around the repair rather than in the repair.

That is the span in which the following happens, and it is worth naming precisely because none of the nine products is sold to perform it:

• Chasing evidence across systems. The trend before the trip is in the historian. The pump curve is on a shared drive. The last three repairs are in the work order system, described in free text by three different people. The manual is a PDF in a folder named after a contractor. Assembling those into one view is retrieval work, and while each product here stores its own piece of it faithfully, gathering the pieces that live in the other systems is not what any of them is sold to do.
• Verifying that a part is actually on the shelf. Every system on this list holds an inventory count. The count is a record of transactions, not an observation of the shelf. Confirming that the seal kit is physically present, that it fits the pump as installed rather than as drawn, and that the substitution somebody made in 2019 is documented, is a task performed by a person with a phone.
• Getting a supplier quote. Price, stock and lead time come from outside your systems entirely, at the speed of business hours and voicemail.
• Routing an approval. The decision is usually easy. The routing is what takes hours: finding who holds the authority at 03:00, getting the evidence in front of them in a form they can act on, and recording that they did.
• Keeping all of that moving while a technician works. These five activities are digital and they can run in parallel with the physical repair. In most utilities they run in series after it, because they are performed by the same person who is holding the wrench.

None of the nine describes this coordination work as its product, and it would be unfair to read that as a failing. A system of record records. What happens in administrative and logistic delay is coordination, and coordination has never had a system.

A checklist you can put in an RFP

These questions work on any of the products above, and on us. They are ordered roughly by how much time they save.

1. Walk one real alarm. Give the vendor a genuine incident from your last quarter, with your asset identifiers, and ask them to demonstrate the full sequence from alarm to closed work order in their product. Not a scripted demonstration. Yours.
2. Name the authoritative asset register. Ask explicitly whether the product writes against your GIS or keeps its own asset list synchronised with it, and what happens to open work when the GIS is edited.
3. State the alarm intake path. What, exactly, creates the work order: a person, a scheduled job, an event from the historian, or an integration you have to build. If it is an integration, who builds it and what does it cost.
4. Test the mobile case without signal. A lift station in a vault has no coverage. Ask what the technician can do offline and what happens on sync conflict.
5. Ask what the inventory count means. Is it a transactional balance, a cycle counted balance, or an observed one, and what does the product do when the shelf disagrees.
6. Trace the procurement handoff. Show the path from a part shortage to a purchase order in your finance system, naming every manual step and every person in it.
7. Trace the approval path. Who can authorise what, at what value, by what delegation, and what the product records when they do. Ask to see the time stamps.
8. Demand the audit trail specification in writing. What is recorded, by whom, immutable or editable, retained for how long, exportable how.
9. Ask about integration limits, not integration. Every vendor says they integrate. Ask for API rate limits, event or webhook support, the list of pre built connectors to systems you actually run, and one named reference customer using that connector.
10. Establish exit terms before entry. Full data export in a documented format, including attachments and history, at no additional charge, on demand. Get it in the contract rather than the proposal.
11. Separate one time cost from recurring cost. Licence, implementation, data conversion, integration, training and annual support belong on separate lines. Your finance office and, if you are pursuing state revolving fund money, your state programme both need them split.
12. Take three references of your own size, in your own state, with your own GIS. Ask them what they would specify differently. That question gets better answers than any question about satisfaction.

A note on the publisher’s position

This guide is published by EQUA AI, so state the interest plainly.

EQUA AIMMS is not a CMMS, an EAM or an ERP, and it does not replace one. The systems above remain the systems of record, and if what your utility needs is a work order system, buy one of them. AIMMS sits on top of the systems you already run and works the span this article has been describing: the administrative and logistic delay between the alarm and the closed work order. It brings the evidence together with each item traced to its source, tracks safety items, verifies parts against the installed configuration, coordinates suppliers and quotes, routes approvals to whoever your policy says holds the authority, writes back to your business systems where you have configured and approved that path, and preserves the repair history.

Two boundaries are structural rather than configurable. Operational connectivity is read only: AIMMS reads SCADA events and historian data and holds no write path to a PLC, DCS or control system, and it never issues a setpoint, restart, interlock or actuator command. And autonomy is defined by the customer: roles, permissions, spend limits, safety policies and approval gates decide what AIMMS may do, and every permitted action produces a time stamped receipt.

That is a different job from the one the nine products above are designed for, which is why this guide does not rank them and why a reader should be able to use it to choose one of them and be well served.

If you want the boundary drawn against your own operation rather than in the abstract, the 20 minute assessment produces one named workflow, the delay inside it, and where each of your existing systems stops.

Sources

Ownership and product facts, verified 5 September 2026.

• Trimble, Trimble to Acquire Cityworks to Expand Its Digital Asset and Infrastructure Management Solutions, 3 October 2019. Cited for Trimble’s agreement to acquire Azteca Systems LLC, doing business as Cityworks, and for Cityworks’ Esri Business Partner status.
• Trimble, Trimble Unity Maintain product page and Trimble Unity Permit product page, accessed 5 September 2026. Cited for the consolidation of Cityworks and AgileAssets into Trimble Unity Maintain, for the sunsetting of the locally installed Cityworks version, for the statement that the GIS remains the authoritative source of truth for asset data, for vendor stated automatic work order creation from real time IoT sensor data through ArcGIS Velocity, and for the statement that Trimble Unity Permit is powered by Trimble Cityworks PLL. These are vendor product pages and are cited as vendor statements.
• IBM, Condition monitoring overview, Maximo Manage documentation, and IBM Maximo Application Suite for energy and utilities, accessed 5 September 2026. Cited for measurement points setting acceptable ranges for meter readings and for work order generation when readings fall outside those ranges, and for the energy and utilities positioning.
• Clearlake Capital, Clearlake Capital Completes Sale of Brightly Software to Siemens, 3 August 2022. Cited for the completion of Siemens’ acquisition of Brightly Software, formerly Dude Solutions.
• Siemens, Brightly is now Siemens Asset Management Software, 14 July 2026, and Asset Essentials product overview, accessed 5 September 2026. Cited for the retirement of the Brightly brand, for the statement that the solutions, products and people customers rely on remain the same, and for Asset Essentials continuing under its own name, including asset threshold monitoring using IoT sensors.
• OpenGov, OpenGov Continues Expansion with Acquisition of Operations and Asset Management Leader Cartegraph, 27 July 2022, and OpenGov Enterprise Asset Management product page, accessed 5 September 2026. Cited for the acquisition and for the current product name and built in GIS integration.
• Cox Enterprises, Cox Enterprises Acquires Majority Ownership of OpenGov, 27 February 2024. Cited for majority ownership and the reported 1.8 billion dollar valuation.
• CentralSquare Technologies, CentralSquare Acquires Lucity, 8 January 2019, and Bain Capital, CentralSquare Technologies portfolio page, accessed 5 September 2026. Cited for the acquisition and for private equity backing by Bain Capital and Vista Equity Partners. Other institutional investors also hold positions in CentralSquare.
• Fluke, eMaint CMMS product page and Fluke Acquires eMaint Enterprises, and Fortive, Fortive operating companies, accessed 5 September 2026. Cited for eMaint as an offering of Fluke Reliability, for the 2016 acquisition, for Fluke as a Fortive operating company, and for the condition monitoring integration.
• Limble, Limble Announces 58M Series B Funding Round Led by Goldman Sachs Asset Management, 22 June 2023. Cited for the Goldman Sachs Asset Management led round, and for the founding year of 2015 and the Lehi, Utah dateline. No acquisition of Limble has been announced as of 5 September 2026.
• Autodesk, Welcoming MaintainX to Autodesk, 3 August 2026, and Autodesk to acquire MaintainX, 28 May 2026. Cited for the completed acquisition and the description of MaintainX as a mobile first CMMS platform.
• Rockwell Automation, Rockwell Automation Completes the Acquisition of Fiix Inc., 19 January 2021, which states that the transaction closed in December 2020, and Fiix, Condition based maintenance with Fiix and FactoryTalk Optix, accessed 5 September 2026. Cited for ownership and for vendor stated work order creation from asset fault codes on eligible Rockwell devices.
• International Electrotechnical Commission, IEC 61703:2016, Mathematical expressions for reliability, availability, maintainability and maintenance support terms, edition 2.0, 2016-08, adopted in Europe as EN 61703:2016. Cited for the treatment of mean repair time, mean active corrective maintenance time, mean time to restoration, mean administrative delay and mean logistic delay as separate defined measures at clauses 6.4.19 through 6.4.23, for their IEC 60050-192 vocabulary entry numbers, and for the standard’s basis in IEC 60050-192:2015. The contents list is visible in the publicly available preview of the standard; the full text is behind the IEC paywall.
• SoftwareSuggest, CityWorks alternatives, accessed 5 September 2026. Cited for the ten listed alternatives named in this article, and for the page’s own statements that its ratings and reports contain no paid placements and that alternatives are selected from buyer survey responses and total review volume. Listing sites change their contents, so this reflects the page on the date of access.

Scope note: product behaviour described above is drawn from vendor documentation and product pages as of September 2026 and is subject to change with releases. Nothing here is a recommendation of one product over another, and none of these vendors reviewed this article.