Asset intelligence
Asset Management
Maintain the asset register, capture criticality and lifecycle context, and use evidence passports to understand condition, coverage and confidence.
Three views of asset assurance
Asset Health describes condition. Inspection Coverage shows how much intended scope was assessed. Evidence Confidence shows how strong and complete the supporting record is. InspectAssets keeps these separate so missing evidence cannot quietly become a healthy result.
The asset register
Assets belong to sites and form the unit most inspection work is conducted against. The register can be used to answer operational questions such as which assets are critical, which are overdue for attention, which carry compliance concerns and which require immediate review.
Authorised users can create, update, remove and export assets according to permission. Users with export_asset_register can take the structured register outside InspectAssets for approved analysis or reconciliation.
Adding and structuring an asset
- Choose Add Asset and assign the asset to the correct site.
- Complete identifying, type, lifecycle and operational information.
- Record consequence dimensions where they are known.
- Review the derived criticality and its rationale before using it to prioritise work.
- Save supporting documents, dates and other evidence that improves future decisions.
Criticality and consequence
Asset criticality can be low, medium, high or critical. InspectAssets supports five consequence dimensions:
When consequence information is entered, the platform can derive the asset criticality used by risk, inspection scheduling and action SLAs. This creates a more consistent basis for priority than relying on an ad-hoc label alone.
Decision Readiness
Decision Readiness asks a different question from Asset Health: does management have sufficiently current, complete and reliable evidence to rely on a decision? An asset can look healthy based on inspected items while still having low decision readiness because inspection coverage is partial, evidence is weak or unresolved limitations remain.
Asset Evidence Passport
The Asset Evidence Passport is the evidence-centred view for a single asset. Only information your account is authorised to see is displayed. It can bring together:
- Asset identity, site, lifecycle and criticality context.
- Calculated asset health, inspection coverage and evidence confidence.
- Inspection history and inspection evidence.
- Open or prior inspection limitations, including reason and age where available.
- Compliance, approval and other lifecycle evidence linked to the asset.
- Available machine-condition evidence, current condition events and machine-evidence policy position where Continuous Condition Evidence is enabled.
- Documents, cost/history information and supporting records available to your role.
Use the passport when a manager, auditor or engineer needs to understand not only “what is the latest condition?” but also “what evidence supports that conclusion, and what remains unknown?” Where enabled, Continuous Condition Evidence adds machine-condition context between inspections without making it mandatory by default.
Condition sources are connected from the asset passport
When Continuous Condition Evidence is enabled and your account has view_condition_evidence, the asset Passport includes a Condition sources card. It shows registered sources, the latest machine reading, open condition events and the current machine-evidence position. View-only users see a read-only indicator and cannot create or manage a source. Users with the additional manage_condition_devices permission can select Connect condition source; the connection workflow opens with the asset already bound. See Continuous Condition Evidence for the endpoint, token and first-reading steps.
System / Relationships
The Asset Evidence Passport can show how an asset is structurally connected to other assets in the same organisation. Relationship records are factual system context; they do not automatically mean that a fault, condition or risk on one asset applies to another.
| Relationship | How to read it |
|---|---|
| Parent / component | Records that one asset is the parent assembly and the other is a component. The Passport shows the direction as Parent of or Component of. |
| Dependency | Records that one asset depends on another. The Passport shows the direction as Depends on or Dependency for. |
| Connected asset | Records a peer connection without asserting parentage or dependency. |
Users with view_asset_relationships or normal asset-view access can review relationship context. Users with manage_asset_relationships or the existing asset-update authority can add, edit or archive a relationship. Archiving removes it from the active system view without deleting its history.
- Open the asset's Asset Evidence Passport.
- Find System / Relationships.
- Select Add relationship if your role allows management.
- Choose the relationship type, direction where relevant, and the related asset.
- Add factual notes only where they help explain the system structure, then save.
Relationship context is evidence, not a risk conclusion
A dependency or component link helps an engineer understand system context around inspections, condition events and limitations. InspectAssets does not turn the link itself into a failure-propagation or risk conclusion. Any such conclusion still requires supporting evidence.
Health records and calculated health
Health history supports trending over time, but the current inspection model distinguishes legacy/manual readings from calculated asset health. Overall Asset Health is derived from inspected condition and failed findings after submission. Unknown assessment states lower coverage/evidence confidence; they are not automatically treated as defects.
Management uncertainty
Asset views can surface the latest inspection unknowns and unresolved limitations separately from condition. This prevents a limitation such as inaccessible equipment or missing information from changing the health score while still ensuring decision-makers see it.
Scanning assets
Scan Asset uses the device camera to read an asset QR code and is gated by conduct_inspection. The next step depends on the matched record:
| Scan result | What happens |
|---|---|
| Scheduled/open inspection is available | InspectAssets can take you into the inspection workflow. |
| No current inspection is due | The asset record/passport can be opened instead. |
| No matching asset or inspection | The app reports that nothing matched; confirm the code or enter it manually. |
If camera access is unavailable, use manual code entry rather than abandoning the field workflow.
The Offline Queue
Field work can continue during poor connectivity. Unsynced items are stored locally and shown in the Offline Queue. Web states are queued, synced and failed. Mobile shows QUEUED or FAILED; a successful sync removes the entry and reports its result. See the mobile sync instructions. Open failed items to see the rejection and retry when appropriate.
Unsynced work exists on the device
Do not clear browser/site data while field items are still queued. Until a record is successfully synced, it may not exist on the server.
Asset Operations
Users with view_asset_operations receive a cross-portfolio operational view. The workspace summarises total assets and condition counts, shows asset-type distribution and recent assets, and lets the user select a site by name to load the assets registered there. This avoids requiring administrators to work with technical site IDs.
Use Asset Operations to understand the portfolio at a glance; use Asset Detail or the Evidence Passport when the decision depends on criticality, limitations, provenance or other underlying evidence.