ASSET IDENTITY
The technical object
Equipment, component, functional location and serial identity establish what object the technical Ground describes.
DETERMINISTIC INTELLIGENCE · ASSET & INFRASTRUCTURE
Reconstruct the technical state behind the asset.
Know the asset. Know its condition. Know what it depends on.
Asset & Infrastructure Intelligence reconstructs technical identity, observed condition, maintenance history, failure events and dependency relationships into traceable deterministic state.
Asset · Condition · Maintenance · Dependency · Downtime · Exposure
01
ASSET GROUND
Establish the technical object before interpreting its condition.
Asset registers, equipment masters, serial numbers, functional locations, inspection records, measurements, alarms, maintenance orders, failure events and dependency relationships can establish one governed technical history.
Asset registers
Equipment masters
Serial numbers
Functional locations
Inspection records
Condition readings
Maintenance orders
Failure events
Downtime records
Dependency relationships
02
SEMANTIC DISCIPLINE
Asset identity is not condition. Condition is not prediction.
A technical object can be identified without knowing its current condition. A condition observation can establish state without establishing failure probability or remaining useful life.
OBSERVED CONDITION
Evidence through time
Measurements, inspections, alarms and failure events establish observed technical state under explicit semantics.
PREDICTION
A separate governed claim
Failure probability and remaining useful life require additional models and evidence beyond observed condition.
03
QUESTIONS
Asset questions answered from Ground.
Which assets show deteriorating observed condition?
Compare governed observations through time without inventing a predictive conclusion.
Which assets are overdue for inspection or maintenance?
Evaluate explicit technical populations against governed dates and maintenance rules.
What changed around a maintenance event?
Place pre-maintenance and post-maintenance observations on the same technical chronology.
Where is downtime concentrated?
Relate qualifying outage intervals to assets, failure events and technical locations.
Which components support a critical service?
Traverse explicit dependency relationships from component to service and site.
What cannot yet be established?
Incomplete condition history, incompatible measurement regimes and absent predictive Ground remain visible.
04
MEASURES
Define the technical population, event boundary and period behind every measure.
Downtime
Qualifying outage intervals
Governed elapsed time during which a defined asset population is established as unavailable.
Ground: asset identity · outage start · return-to-service event
Time since maintenance
Last qualifying maintenance event → reference time
Elapsed governed time since the most recent maintenance event satisfying the selected maintenance definition.
Ground: asset · maintenance event · governed clock
Critical dependency exposure
Defined dependents linked to a critical technical object
The governed population of assets or services connected through explicit dependency relationships.
Ground: dependency graph · criticality · technical population
05
CONDITION THROUGH TIME · ILLUSTRATIVE EXAMPLE — SYNTHETIC DATA
Follow observed technical condition through the asset history.
Condition history is a chronology of observations and events, not one opaque health score.
Synthetic example. A maintenance event is activity; post-maintenance observation is the Evidence of resulting technical state.
06
MAINTENANCE CHRONOLOGY · ILLUSTRATIVE EXAMPLE — SYNTHETIC DATA
Separate maintenance performed from condition demonstrated.
BEFORE
Observed condition
Elevated vibrationMeasurement M-442 · governed instrument regime
MAINTENANCE
Work performed
Bearing replacementMaintenance order MO-184
AFTER
Observed condition
Nominal vibrationMeasurement M-471 · same governed regime
Maintenance execution alone does not prove restored condition. The subsequent observation closes that claim.
07
DEPENDENCY & EXPOSURE · ILLUSTRATIVE EXAMPLE — SYNTHETIC DATA
Trace technical dependency without turning exposure into causality.
The relationship establishes dependency exposure. It does not by itself prove why a failure occurred.
08
DATA SUFFICIENCY
See what the available Asset Ground can establish.
Maintenance history
Asset identity and governed maintenance events are present.
The selected asset population has traceable maintenance event history.
Condition trend
Observations exist across changing measurement regimes.
Trend comparison is bounded where instruments, units or measurement semantics changed through time.
Remaining useful life
No governed predictive model is established.
Historical technical Ground alone does not establish remaining useful life or guaranteed failure prediction.
09
WHY THIS CONDITION?
Trace technical state back to observations and source records.
Condition, maintenance, failure and dependency conclusions remain connected to the technical records and semantic rules that establish them.
10
BOUNDARY
Observed technical state is not predictive or control authority.
Asset & Infrastructure Intelligence may establish asset identity, condition history, maintenance chronology, failure events, downtime, dependency relationships and defined exposure.
It does not silently infer remaining useful life, failure probability, root cause, optimal maintenance strategy, automatic replacement decisions, human performance or autonomous machine control.
11
DAILY DETERMINISTIC INTELLIGENCE
Search, navigate, compare and trace technical Ground without requiring AI.
SOURCE AUTHORITY
Technical systems remain authoritative.
EAM, CMMS, ERP, engineering, GIS, SCADA, monitoring and historian systems retain ownership of the records they establish.
TRACE CONDITION
Navigate the asset history.
Search equipment, compare condition histories, trace maintenance, inspect downtime and traverse technical dependency.
AI OPTIONAL IN DAILY USE
CUSTOMER-CONTROLLED COMPUTE
Deterministic asset intelligence does not require a generative model or a mandatory radius19-hosted SaaS runtime.
PRODUCT BOUNDARY
Observation is not autonomous technical control.
Asset Intelligence does not establish automatic source-data correctness, guaranteed failure prediction, autonomous maintenance decisions, control authority, automatic engineering correctness or operational writeback. It is not a generative copilot for ordinary daily use.
12
SOFTWARE LICENSE
Deploy Asset & Infrastructure Intelligence in customer-controlled infrastructure.
Asset & Infrastructure Intelligence is offered as software under a direct licensing and delivery relationship. Technical scope, source systems, reconstruction rules and deployment context determine the bounded product configuration.
Discuss Asset & Infrastructure Intelligence with radius19 ← Back to Products