Asset Lifecycle Record
Provide a governed, evidence-linked lifecycle projection for one physical item without creating another asset master.
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
- aggregate
- 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.
In scope
- One item master binding and a versioned projection profile
- Selected event, maintenance, condition, custody, ownership and disposition references
- Effective-time and knowledge-cutoff queries with source revisions and uncertainty
- Local snapshot revision, correction visibility, coverage gaps and recipient-specific export
Out of scope
- Physical item registration, identifier reassignment and item-master merges
- Maintenance planning, work execution, incident investigation and return-to-service approval
- Legal title determination, transfer execution, financial valuation and depreciation ledgers
- Physical disposal, recycling execution, operational control and digital-twin simulation
- Universal legal retention periods or sector-specific safety certification
Why it exists Filled
Provide a governed, evidence-linked lifecycle projection for one physical item without creating another asset master.
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.
Roles
- Projection steward
- Maintain view purpose, scope, source binding and coverage qualifications.
- Source custodian
- Assert source records and corrections within the separate master system authority.
- Evidence reviewer
- Resolve local mapping disputes and escalate identity, title or safety disputes to competent authorities.
- Access and records officer
- Approve recipient scopes, minimization, retention and local disposition within applicable policy.
- Consumer
- Interpret snapshots within declared time, coverage, source and authority limits.
Master systems
- Enterprise asset management systems
- Computerised maintenance management systems
- Fixed asset registers
Links to other meta-models Filled
references
- WM-OBJ-001 - Required single physical item master binding. Encodes frozen VIEW semantics because VIEW is not a research-schema relation; no second item identity, inheritance or master ownership.
composes
- WM-ACT-013 - Optional composition of linked maintenance history. Referenced maintenance records retain their work lifecycle, planning and execution authority; absence is reported rather than filled with fictional work.
aligned
- EPCIS 2.0 conceptual mapping - Map event and correction references only with explicit source versions and losses; no capture/query conformance claim and no mandatory use of its identifiers.
- CBV 2.0 conceptual mapping - Qualify stage, business-step and party-role codes without treating codes as proof of legal or operational effect.
- PROV-O and SOSA/SSN conceptual mappings - Preserve snapshot derivation and qualified observation links without claiming ontology implementation or measurement truth.
neighbor
- WM-OBJ-001 Physical Item Instance - The frozen VIEW relation forbids a second master identity. A required REFERENCE encodes this dependency in the narrower schema; aggregate means a derived view, not item containment or inheritance.
- WM-ACT-013 Maintenance - The frozen COMPOSE relation includes maintenance history as optional linked work records. Composition is by reference: no work-order lifecycle, scheduling or execution is moved here, and an unmaintained item can still have a view.
- Event and observation masters - The projection records source identifiers, revisions and selected qualified summaries; event capture, sensor operation, observation truth and event correction authority remain external.
- Ownership, custody, finance and disposal authorities - Role-specific claims and evidence are linked, not adjudicated. Custody and location do not establish title; a book-value change or identifier retirement does not prove destruction.
- Record and snapshot identity - A local view ID plus immutable revision identifies a projection artifact. Different views of the same master item can coexist without minting different assets. A lineage collection is not a physical assembly.
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:2024 - Asset management - Vocabulary, overview and principles - International Organization for Standardization
- ISO 14224:2016 - Collection and exchange of reliability and maintenance data for equipment - International Organization for Standardization
- EPCIS Standard - GS1
- Core Business Vocabulary Standard - GS1
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Semantic Sensor Network Ontology - World Wide Web Consortium
- Digital Thread for Smart Manufacturing - National Institute of Standards and Technology
- Date and Time on the Internet: Timestamps - Internet Engineering Task Force
- 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
- Verify exact source versions and current applicability, including the EPCIS URL/PDF release mismatch, relevant errata, licensed ISO clauses and source hashes outside the sandbox.
- Implement and test nested schemas, neighbor bindings and mappings with reused identifiers, late correction, counter reset, disputed ownership, missing work, redaction and post-destruction observation cases.
- Obtain independent external review and qualified sector-profile review before canonical or publishable-draft promotion.
- Independent external review is absent; Claude and Grok skipped under the owner-authorized waiver.
- Nested instance schemas, real mappings, neighbor version pins and conformance fixtures are incomplete.
- ISO paid clauses were not read; sector-specific safety, title, retention, financial, warranty and regulatory passport requirements are not specified.
- EPCIS URL patch version and PDF release label differ; exact source artifact pin requires coordinator verification.
- Full fleet analytics, predictive maintenance, cost calculations, sensor control and work execution are excluded.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-obj-022-asset-lifecycle-record/spec.yaml, ver-cy/world-models/card-supplements/wm-obj-022-asset-lifecycle-record.json