Asset Lifecycle Record
Lifecycle projection over item, events, work and ownership
Bundle → Layer → Finding → Questions Filled
3 bundles · 4 layers · 5 findings · 10 questions
Asset identity Which asset the record follows.
Asset registration
The asset's identifiers, type and location.
Asset identification
The tag, serial number and register entry of the asset.
- Which asset tag and serial number identify the asset in the register?
- Which product type or model does the asset instantiate?
Lifecycle history What happened to the asset over time.
Events and work
Installation, maintenance, failures, modifications and inspections.
Maintenance and failure history
Work performed and failures observed on the asset.
- Which maintenance, repairs and modifications were performed, and when?
- Which failures occurred, with what cause and downtime?
Condition and usage
Usage counters and condition assessments over time.
- What are the current operating hours, cycles or distance of the asset?
- What was the result of the most recent condition assessment?
Ownership and custody
Who owned, held or used the asset over time.
Ownership chain
Transfers of ownership and custody.
- Who owns the asset now, and who held it before?
- Are there leases, liens or other claims on the asset?
Lifecycle stage Where the asset stands between acquisition and disposal.
Stage and end of life
The current stage and planned disposal.
Current stage
Whether the asset is in service, idle, under repair or retired.
- Which lifecycle stage is the asset in, and since when?
- When is the asset planned for replacement or disposal, and how?
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- view-candidate
- Navigation path
- NAV.PHY.OBJ.AST
- Domain
- PHY.OBJ.AST
- Industry
- Cross-industry
- Tags
- assetlifecyclerecordphy.obj.ast
What it is Filled
An asset lifecycle record is a consolidated view of one physical asset from acquisition to disposal, bringing together its identity, the events that happened to it, the work done on it and its ownership over time. It is a projection over the item and related records, not the physical item itself and not a single work order or transaction.
Why it exists Filled
Lifecycle projection over item, events, work and ownership
Distinguishing features Filled
- It is a projection over item, events, work and ownership, not the physical item itself.
- It spans the whole life of one asset, whereas a work order covers one job.
- Distinct from a financial fixed-asset entry, which tracks book value rather than physical history.
- Distinct from a digital twin, which models behaviour; the lifecycle record keeps history.
What robots and AI may and may not do Filled
Must not
- Alter or delete past history entries instead of adding corrections.
- Record work as done without evidence from the work record.
- Transfer ownership in the record without a recorded transaction.
- Clear an asset as safe to use when required inspections are missing.
Only with a human decision
- Approving disposal or scrapping of an asset.
- Returning an asset to service after a safety-relevant failure.
May
- Assemble the history of an asset from linked work, event and ownership records.
- Report usage counters, failures and current lifecycle stage.
- Flag gaps in the history, such as missing inspections required by schedule.
- Propose maintenance or replacement based on recorded condition and usage.
Moral aspects Filled
- Incomplete histories can hide safety problems from later owners and users.
- Lifecycle records support repair, reuse and resale, which reduces waste.
- Records may name technicians and users, which needs care with personal data.
Who is affected
- Asset owners and operators
- Maintenance staff
- Later buyers and users of the asset
- People exposed to the asset in operation
Owners Filled
Steward
The asset manager of the owning organisation answers for the completeness of the lifecycle record.
Master systems
- Enterprise asset management systems
- Computerised maintenance management systems
- Fixed asset registers
Links to other meta-models Filled
parent
- WM-OBJ-001
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A lifecycle record is keyed to the asset tag or register number and the serial number of the item.
- Linked records carry their own work order, event and transaction identifiers.
Direct properties required Filled
- Operating hours or cycle counts read from the asset's counters.
- Distance travelled in kilometres for mobile assets.
- Condition ratings on the scale defined by the owner's assessment method.
- Measured wear or degradation indicators, with the unit given by the inspection method.
Recognition optional Filled
- A lifecycle record links one asset to dated events, work, usage and ownership changes.
- Often confused with the asset register entry, a single work order or a financial depreciation schedule.
Capabilities and actions required Filled
- History entries can be appended from work, inspection and transaction records.
- Usage and condition data can be trended to support maintenance and replacement decisions.
Hazards and failure modes required Filled
- Safety decisions based on incomplete or falsified history.
- Lost history when the asset changes owner or system.
- Mismatched records when tags are reused or swapped between assets.
Standards and interfaces required Filled
- ISO 55000 series for asset management.
- ISO 14224 for reliability and maintenance data exchange.
- EN 13306 maintenance terminology.
Context of use required Filled
- Used in industry, utilities, transport, facilities and fleets.
- Regulated sectors require lifecycle records for inspections and safety-critical components.
Sources Filled
- ISO 55000 Asset management - Vocabulary, overview and principles (ISO)
- ISO 14224 Petroleum, petrochemical and natural gas industries - Collection and exchange of reliability and maintenance data for equipment (ISO)
- EN 13306 Maintenance - Maintenance terminology (CEN)
Open questions
- Planned model: boundary questions, research and every section remain to be written.
Machine files
Provenance
planned (registry candidate) · todo
Built from: models/runtime-index.json, ver-cy/world-models/card-supplements/wm-obj-022-asset-lifecycle-record.json
Planned entry, hidden from the catalogue until researched.