The lifespan is not a feed of notes. It is a linked digital thread from design intent through manufacture, commissioning, operation, care, service, modification, transfer, restoration, repurpose and retirement. Every important change connects an exact…
Concept & directionLNK
The lifespan is not a feed of notes. It is a linked digital thread from design intent through manufacture, commissioning, operation, care, service, modification, transfer, restoration, repurpose and retirement. Every important change connects an exact baseline to an exact result while preserving the parts, people, tools, materials, software, evidence, rights and approvals involved.
Picture 6
The asset remains durable while configuration, state, condition, custody and approvals change on separate planes.
Avoid snapshot explosion
A robot moving a joint does not create a new engineering configuration every millisecond. The installed topology stays in ConfigurationSnapshot; pose and resource values belong in OperationalStateSnapshot. A discrete, safety-gated transformation can reference a MorphModeDefinition and a resulting configuration only when topology or controlled effectivity truly changes.
What is built, in what sequence, with which materials and tooling?
Procurement / supplier
What can be sourced, substituted, certified, costed and warranted?
Service / illustrated parts
What is maintained, removed, replaced, inspected and provisioned?
Software / calibration
What artifacts, dependencies, targets, partitions and parameters are required?
Material / substance
What grades, lots, compositions, regulated substances and mixtures are present?
Mass / balance
Which items and loads contribute to mass, CG/CB and inertia?
Cost / carbon
Which costs and environmental impacts are allocated under which method/boundary?
As-built / as-delivered
What physical configuration left production and entered custody?
As-maintained / as-repaired
What does service evidence say is installed and repaired?
As-operated / as-tested
What exact build, load, software, settings and connections produced the operation/result?
As-retired
What was removed, harvested, destroyed, recycled, retained or transferred?
BOM membership never proves installation; a realized placement and installation event are required.
One item can appear in product, function, location, power, fluid, data, control, safety, maintenance, ownership and certification structures simultaneously.
A configuration node can reference an item, material quantity, feature, software, calibration or data artifact; edges carry typed placement, connection and effectivity.
Exclusive slot occupancy cannot overlap. Shared cloud services, broadcast signals and non-exclusive functional providers use explicitly non-exclusive relations.
Applicability must evaluate to TRUE, FALSE, UNKNOWN or ERROR. Missing serial, configuration, jurisdiction or software data cannot become FALSE and cannot authorize work. Expressions may combine time, identifier ranges, design revisions, installed items, quantities, versions, relationships, jurisdiction, operation mode and namespaced domain operators.
calendar, distance, hours, starts, landings, laps, missions, pressure/thermal cycles, charge-equivalent cycles, throughput, exposure, condition threshold or named event
Applicability
target selector, configuration, design revision, installed options, software, jurisdiction, duty and environmental state
Prerequisites
isolation, safe state, access, cleanliness, environment, tools, support equipment, skills and permits
Procedure
ordered steps, warnings, parameters, target, hold points, witnesses, conditional branches and evidence
As found
condition, measurements, findings, contamination, faults, photos/scans and uncertainty
Work execution
actual workers, times, steps, parts, lots, materials, tools, deviations, interruptions and signoffs
Close / release
as-left condition, measurements, tests, unresolved findings, limitations, release authority and next due
Table
Meter rules
Distance, time, cycles, starts, launches, landings, pressure events, energy throughput and component-specific meters are independent. Resetting, replacing or overhauling never erases the prior reading. A component carries its meters when removed and reused; zero-time or life-reset status requires an explicit policy and authority.
#21.6 Care, wash, detailing, and preservation execution
Area
Record fields
Target + condition
surface/zone/component, configuration, contamination before, finish/coating and protected ports
location/privacy, weather, energization, runoff capture, waste, biosecurity and jurisdiction
Evidence + findings
before/during/after media, gloss/thickness/roughness, newly exposed damage and public derivative
Outcome
condition after, protection applied, cure/expiry, cost, provider, next care and story rights
The same contract supports a car-wash photo, salt removal from a truck, aircraft wash, underwater hull biofouling removal, blimp-envelope cleaning, RC-car bearing protection and museum conservation. A care task can finish successfully while independently creating a defect record when cleaning reveals damage.
purpose, authority class, runtime, input/output schemas, training provenance claims, evaluation, ODD, limitations and monitoring
Rollback
known-good artifact, compatibility, trigger, state migration, evidence and incident linkage
Table
Authority class is structural
A vehicle persona, diagnostic assistant and steering controller may all use AI models, but their allowed output ports, grants, evidence and safety partitions differ. Sharing a model/runtime concept never grants the social plane access to a physical-control interface.
#21.9 Restoration, repurpose, salvage, and retirement
Disposition
Required distinction
Preservation / conservation
Arrest deterioration and stabilize historic material without inventing original state
Repair / restoration
Restore function or a documented earlier state; mark and document replacement/reproduction parts
Reconstruction / replica / recreation
Create missing or representative material under a new or explicit continuity relationship
Restomod / rebuild
Combine historic continuity with deliberate modern change; disclose removed/retained substance and identity policy
Repurpose / second life
Same component/asset can gain a new duty, configuration, approvals and responsible operator
Part harvest
Donor, removal, as-removed condition, traceability, inspection, reuse eligibility and new custody
Unsalvageable disposition
Quarantine, permanent service ineligibility, mutilation or controlled research/display use
Recycle / destroy / consume / lose
Material outputs, hazardous inventory, facility, certificates, retained evidence and identity disposition
