Insights · 12 min read
Asset management software: the modules that matter, EAM vs CMMS vs ITAM, the IoT and hardware layer, cost drivers, and when building beats buying off the shelf.
By GGP Editorial
Most companies know what they own until an audit asks them to prove it. A plant knows it has pumps. A facilities team knows it has HVAC units. An IT department knows it has laptops. What they do not have is one place that says where each asset is, what it cost, when it was last serviced, what it is worth today, and whose name is on it.
What they have instead is a spreadsheet that three people edit, a maintenance log in someone's inbox, and a fixed-asset register in the accounting system that nobody has reconciled since it was set up. The gaps between those three are where money leaks. Equipment gets serviced twice because there is no history. Warranty work gets missed. Assets get written off at the wrong value. An audit that should take a morning takes a month of evenings.
This article is for operations directors, facilities managers, IT leaders, and the founders building software for them. It covers what an asset management system actually is, the modules that matter, the hardware layer, what drives the cost, and when building beats buying.
The naming needs clearing up first, because "asset management" means two different things depending on who is asking.
To a finance firm, asset management means running an investment portfolio. That is not this article. This is about physical and digital assets: machines, vehicles, tools, facilities, servers, laptops, software licenses. The things a business owns, uses, and eventually retires.
Within that world there are three overlapping categories, and it helps to separate them because each has a different center of gravity.
| Category | Focus | Typical buyer |
|---|---|---|
| CMMS (maintenance) | Work orders, preventive maintenance, downtime | Maintenance and facilities teams |
| EAM (full lifecycle) | Purchase, depreciation, maintenance, disposal, and the money behind each asset | Operations and finance leadership |
| ITAM (IT assets) | Hardware, software licenses, warranties, compliance | IT and procurement |
A CMMS answers "what needs fixing and when." EAM answers "what do we own, what is it worth, and what does it cost to keep." ITAM answers "what hardware and licenses do we have, and are we compliant." A real system usually starts as one of these and grows toward the others. The advantage of building it yourself is that you decide where the center of gravity sits.
ISO 55000 is the standard people cite for asset management, and it is a useful reference. The practical definition is simpler: an asset management system is one source of truth for every asset, its condition, its history, and its cost, from the day it arrives to the day it is scrapped.
The system splits into modules. Not every operation needs all of them, but the list is the same across industries.
| Module | What it does | Why it matters |
|---|---|---|
| Asset registry | One record per asset: ID, location, owner, supplier, serial, purchase date, cost | The foundation every other module references |
| Work orders | Create, assign, and track maintenance jobs from request to completion | Turns "it's broken" into a tracked job with a history |
| Preventive maintenance | Schedules based on time, usage, or meter readings | Prevents the failures that cost the most |
| Spare parts and inventory | Track parts, stock levels, reorder points | A cheap part on backorder can idle an expensive machine |
| Procurement and suppliers | Request, approve, receive, and track warranty | Connects the asset to where it came from |
| Condition monitoring | Sensor data: vibration, temperature, runtime, location | Moves maintenance from a calendar to actual condition |
| Depreciation and financials | Value, depreciation schedule, write-off, insurance | Keeps the fixed-asset register in sync with accounting |
| Mobile app | Scan a barcode, log a job, view history in the field | The interface the field actually uses |
| Reporting | Utilization, downtime, cost per asset, backlog | The part leadership actually reads |
A manufacturing plant tracking production equipment wants the first five plus condition monitoring. An IT team tracking laptops and servers wants the registry, procurement, warranty, and license compliance, and can skip work orders. The module list should follow the operation, not the other way around.
A build is not "make a database of things we own." The database is the easy part. Here is the real work.
An asset is not one row in a table. It is an identity plus a location, a parent-child relationship (a pump belongs to a line belongs to a plant), a maintenance history, a cost history, and a set of attributes that change by type. A laptop has a serial number and a warranty. A generator has engine hours and a service schedule. Getting the model right at the start makes reporting and IoT work later. Getting it wrong means a rebuild.
The technicians and warehouse staff are the people who make the system real or make it fail. If the mobile app is slower than the paper form it replaced, they will not use it. The app needs barcode scanning, offline support, and a job list that works in a plant with patchy signal. This is the same offline discipline as any field system, which our fleet management article covers in more depth.
Accounting and ERP integration is usually the first and most important. Depreciation, purchase orders, and asset values need to flow between systems without rekeying. Then comes procurement, single sign-on, and whatever field service or warehouse system you already run. Every integration is a line item, and some are genuinely slow to work with.
If you add condition monitoring, you are now building a small real-time pipeline. Sensors report every few seconds or minutes, and a few thousand tagged assets becomes a lot of events per day. Decide early how that stream is stored, downsampled, and queried. Retrofitting it later is expensive.
Half the value of an asset system lives on the asset itself, not in the cloud. The usual pieces:
Each device speaks its own protocol, and integration is not a two-week task. The teams that treat it as one lose two months. The discipline is the same as any IoT development project: get the data path working end to end with one real asset before you commit to scale. Our article on IoT device management platforms covers the pattern.
Predictive maintenance is where the sensors pay off. Instead of servicing every pump on a calendar, you service the one whose vibration signature changed. The honest caveat is that prediction needs history. A model cannot spot an anomaly until it has seen months of normal data, so plan condition monitoring first and prediction second.
This category has mature vendors. IBM Maximo, SAP, Infor, and IFS cover heavy enterprise EAM. Fiix, MaintainX, UpKeep, Limble, and eMaint cover the maintenance-focused middle. ServiceNow and Lansweeper cover ITAM, and Snipe-IT is a free open-source ITAM option.
If your operation is standard, buying is usually right. We tell prospects this directly, and it is the short version of our custom software vs SaaS comparison. The fit breaks in a few specific situations.
Unusual assets or processes. A vendor built around pumps and motors fights you when your assets are lab instruments, rented equipment, or offshore rigs.
Deep integration with your own systems. If asset data has to flow into a custom ERP, a procurement system, or a field service tool you already run, a packaged tool usually means middleware and manual export.
Per-asset pricing at scale. Asset SaaS is often priced per asset or per user. A plant with tens of thousands of tagged assets reaches a point where the subscription costs more per year than a build, and you still do not own the data.
Compliance and audit requirements. If you need to prove chain of custody, calibration history, or specific depreciation methods to an auditor, you usually end up customizing a packaged tool anyway.
Asset software is not priced per feature. The cost follows the number of asset types, the hardware and IoT surface, and the integrations. Market ranges across development shops look like this:
| Scope | What it includes | Typical range |
|---|---|---|
| MVP | Registry, work orders, preventive maintenance, barcode scanning, mobile app | $40,000–$90,000 |
| Mid-tier | MVP plus spare parts, procurement, depreciation, accounting/ERP integration | $90,000–$200,000 |
| Enterprise | Add IoT condition monitoring, predictive maintenance, multi-site, custom reporting | $200,000+ |
These are ranges to plan with, not quotes. The spread is wide because the scope is. The main drivers:
For a fuller picture of where the money goes, our custom software development cost article walks through it, and estimating a custom software project explains how to scope it so the number stays honest. The same budget levers as any MVP build apply if you want to keep it lean.
A sensible sequence is this. Scope the asset types and lifecycles you will support first, and decide what "done" means: which modules, which integrations, which hardware. Build the registry and the data model next, because everything else hangs off them. Then work orders and preventive maintenance, then the mobile app, then accounting and procurement integrations. IoT and predictive maintenance come last, once the registry is clean and there is history to learn from.
Treat the first release as an MVP. A system that tells you where every asset is, what it cost, and when it was last serviced is useful on day one. A system that tries to model every depreciation rule and every sensor on day one ships late and over budget.
How much does an asset management system cost to build?
Market ranges run roughly $40,000–$90,000 for an MVP, $90,000–$200,000 for a mid-tier system, and $200,000 and up for an enterprise build with IoT. The number follows asset types, hardware, and integrations, not a flat per-feature price.
Should I build or buy asset management software?
Buy if your operation is standard and your volume is low. Build if your assets or processes are unusual, if asset data needs to flow into your own systems, if per-asset pricing has compounded, or if you have specific audit and compliance requirements.
What is the difference between EAM, CMMS, and ITAM?
A CMMS is maintenance-focused and answers what needs fixing. EAM covers the full lifecycle including cost and depreciation. ITAM tracks hardware, software licenses, and warranties. Most systems start as one and grow toward the others.
Do I need IoT sensors and predictive maintenance?
Not on day one. Barcode or RFID identification gives most of the value cheaply. Condition sensors and predictive maintenance pay off once you have clean asset data and months of history to learn from.
How long does a build take?
A focused MVP usually ships in three to four months. A full system with IoT, several integrations, and multi-site support typically runs eight to twelve months.
An asset management system earns its keep on the day of the audit and the day of the unexpected failure. The spreadsheet looks fine until someone asks where the money is.
GlobeSoft builds asset, maintenance, and field systems as part of our broader work on business software and IoT. If you are deciding between buying and building, or you have an asset base that no off-the-shelf tool models cleanly, describe the assets and the systems they need to touch. We will help you scope it and give you a number you can trust.
Tell us what you are building and where you are today. We typically reply within 24 hours.
