Most CMMS and EAM implementations treat equipment and its location as the same thing. An asset gets a code, gets installed, and everything attaches to it directly. That works until the asset gets replaced. Then the history either gets lost, or someone invents a messy naming convention to preserve it. The Position model is the proper solution.
The problem with location-free asset records
When you treat "Chiller-01" as both the physical machine AND the location it sits in, you hit a wall the first time something gets replaced. You end up with options that all cause problems:
- Rename the old and reuse the code. Old asset becomes "Chiller-01-OLD", but now the work orders and history attached to "Chiller-01" span two different physical machines.
- Retire the old code, use a new one. "Chiller-07" replaces "Chiller-01", but now your "cost by asset" reports for this location are split across two codes forever.
- Edit the existing asset's attributes. Serial number, purchase date, warranty all get overwritten, and any historical question becomes unanswerable.
The solution: separate Position from Asset
A Position is the permanent functional or physical slot where something lives. An Asset is the physical equipment that's currently occupying that slot. Positions are long-lived. Assets come and go.
Position
Example: Chiller Bay 3, Building 5
Permanent. Describes role and location. Has its own code. Outlives any single asset.
Asset
Example: Carrier 30HX-250, Serial #C24-5671
Physical equipment. Has a serial, warranty, purchase date. Gets replaced, retired, or moved.
How replacement works with the Position model
Old asset replaced with new. In a Position-based system:
- Position "Chiller Bay 3" remains unchanged.
- Asset "Chiller-01" is marked decommissioned. Its warranty, serial, and full maintenance history remain linked to it.
- Asset "Chiller-07" is created and linked to Position "Chiller Bay 3".
- Future work orders attach to Chiller-07. Position-level cost reports continue uninterrupted.
What you get
You can answer "What has this position cost us over 10 years?" (sum across 4 chillers), or "What was the mean lifespan of chillers in this position?" (retirement dates across equipment), or "Which warranty covered this failure?" (traced to the specific asset).
What to store where
Position Attributes
- Position Code
- Description
- Parent location
- Functional role
- Expected asset class
- Active / Inactive status
Asset Attributes
- Asset Code
- Manufacturer & Model
- Serial Number
- Install date
- Warranty start/end
- Status (active/decom)
- Currently-linked Position
Business rules that keep it clean
- A Position can exist with no asset installed (awaiting replacement, new build).
- An Asset must be linked to exactly one active Position at a time.
- Decommissioning an asset does NOT delete its history.
- Maintenance history is traceable BOTH by Position (continuous) and by Asset (discrete).
- Work orders attach to the currently-installed asset; reports can roll up to the position.
What the Position model enables in reporting
- Position cost history, total spend across all assets that have ever occupied it
- Mean lifespan by position type, how long do chillers typically last in this environment?
- Vacant position tracking, which slots are awaiting equipment?
- Warranty cost-avoidance, which specific asset was under warranty for which claim?
- Replacement planning, positions whose current asset is nearing end-of-life
Which systems support this natively
Most enterprise EAMs support a Position layer out of the box: IBM Maximo (Locations vs Assets), Hexagon EAM (Positions/Slots), SAP PM (Functional Location vs Equipment). Most lightweight CMMS tools don't, which is fine for single-site operations with stable equipment, and a problem everywhere else.
Conclusion
The Position vs Asset distinction looks like a minor modeling choice. It isn't. It determines whether your system can answer real asset lifecycle questions for decades, or whether you'll be explaining messy workarounds to auditors every year. If your assets ever get replaced, and they will, use the Position model.
Written by Muhammad Abbas
Enterprise integration specialist. See also: Asset Hierarchy Design for CAFM and EAM.
