Skip to main content

Assets

Concept overview​

  • Asset: equipment or an item we track and maintain. An Asset must specify an AssetType.

These are core building blocks used across many Cyzag products.

First implementation​

  • Title (required).
  • IDs/keys: standard unique identifiers as used by the backend.
  • Standalone: implemented as a separate entity for now, with simple CRUD.
  • AssetType: required field on Asset create/edit; drives which attributes and maintenance tasks are available for selection.

Planned relationships​

  • Assets linked to FunctionalLocations (where an asset lives or is operated).
  • OperatorRounds may reference Assets (which equipment to inspect).
  • Assets → AssetTypes (required relationship). See Asset Types page for details.

Relationships will be added after the isolated models are stable.

Last Known Value & Historical Readings​

One of the key features of the asset model in Blueprint is the ability to track both current state and historical trends for each asset attribute:

  • Last Known Value: Each asset attribute maintains its most recent reading, providing a quick snapshot of current asset condition
  • Historical Readings: All readings captured during operator rounds are stored with timestamps, operator, and context
  • Trending: Historical data enables trend analysis to identify degradation patterns or abnormal behavior over time
  • Audit Trail: Complete history of who recorded what value and when

This dual-view approach (current + historical) is built into the data model from the start, ensuring that every reading captured during an operator round contributes to both real-time monitoring and long-term trend analysis.

See Asset Readings & Checkpoints for details on how readings are captured and stored.

Usage in Blueprint​

  • CRUD for Assets with AssetType selection
  • Dynamic attribute forms based on the selected AssetType
  • Display of last known values for all asset attributes
  • Historical reading views showing trends over time
  • Offline support: create/edit offline, sync later

See also: