Skip to main content

Asset Readings & Checkpoints

Overview​

Asset readings are the structured measurements captured during operator rounds. Unlike free-form observations, readings are tied to specific asset attributes (like "discharge pressure" or "bearing temperature") and stored in a way that supports both current-state monitoring (last known value) and historical trend analysis.

What is an Asset Reading?​

An asset reading is a single measurement captured at a specific point in time for a specific asset attribute. It includes:

  • Value: The actual measurement (numeric, text, boolean, or option depending on attribute type)
  • Timestamp: When the reading was captured
  • Operator: Who recorded the reading
  • Context: Which round and checkpoint the reading came from (if applicable)
  • Unit: The unit of measurement (inherited from the asset attribute definition)

Reading Types​

Readings can be captured for different types of asset attributes:

Numeric Readings​

  • Counters: Running hours, production counts, cycle counts
  • Decimals: Temperature (°C or °F), pressure (bar, psi), flow rate (L/min), vibration (mm/s), voltage, current, etc.

Other Reading Types​

  • Boolean: Pass/fail checks, on/off state
  • Text: Serial numbers, comments, free-form notes
  • Options: Dropdown selections (e.g., condition: Good/Fair/Poor)

Checkpoints​

A checkpoint is a stop on an operator round where specific readings are captured. Each checkpoint defines:

  • Target: Which asset or functional location to inspect
  • Attributes to Measure: Which asset attributes require readings at this checkpoint
  • Order: The sequence of this checkpoint within the round

For example, a round might have checkpoints like:

  1. Checkpoint 1: Pump P-101 → measure discharge pressure, suction pressure, bearing temp
  2. Checkpoint 2: Pump P-102 → measure discharge pressure, suction pressure, bearing temp
  3. Checkpoint 3: Heat Exchanger HX-201 → measure inlet temp, outlet temp, differential pressure

Last Known Value​

Every asset attribute maintains a last known value — the most recent reading recorded for that attribute. This provides:

  • Quick Status: See the current state of any asset at a glance
  • Dashboard Views: Display last known values across multiple assets for rapid assessment
  • Baseline for Comparison: New readings can be compared against the last known value to detect changes

The last known value is automatically updated every time a new reading is captured.

Historical Readings​

Every reading is also stored in a historical record with full context:

  • Timestamp: Exact date and time the reading was captured
  • Value: The measurement recorded
  • Operator: Who captured the reading
  • Round & Checkpoint: Which round and checkpoint this reading came from
  • Device: Which mobile device was used (for audit purposes)

This historical data enables:

  • Trend Analysis: Plot readings over time to identify degradation patterns
  • Audit Trail: Full traceability of who recorded what value and when
  • Comparison: Compare readings across different operators, shifts, or time periods
  • Threshold Detection: Identify when readings started to drift outside acceptable ranges (used in Phase 2)

Data Flow​

  1. Setup: Define asset types with required attributes (e.g., "Centrifugal Pump" requires "discharge pressure", "suction pressure", "bearing temp")
  2. Round Template: Create a round template with checkpoints, each specifying which asset and which attributes to measure
  3. Execute Round: Operator opens the round on mobile and walks through checkpoints
  4. Capture Reading: At each checkpoint, operator enters values for the required attributes
  5. Store Locally: Reading is stored on the mobile device (offline-first)
  6. Update Last Known Value: The asset attribute's last known value is updated (locally)
  7. Add to History: Reading is added to the historical record (locally)
  8. Sync: When connectivity is available, readings sync to the server
  9. Server Processing: Server updates last known values and historical records for all synced readings

Validation​

Readings are validated against the asset attribute's data type and constraints:

  • Numeric ranges: Min/max values defined on the attribute type (e.g., temperature must be -50 to 150 °C)
  • Required vs. optional: Some attributes may be required at certain checkpoints
  • Data type: Integer readings can't have decimals, boolean readings must be true/false, etc.

Validation happens on the mobile device before sync, ensuring data quality even when offline.

Relationship to Other Features​

Asset Attributes​

Readings are always tied to specific asset attributes. The attribute definition determines:

  • What type of value to collect (integer, decimal, boolean, text, option)
  • What unit of measurement to display
  • What validation rules to enforce
  • Whether the attribute is required or optional

See Asset Attributes for more detail.

Operator Rounds​

Operator rounds are the primary way readings are captured in Phase 1. Each checkpoint in a round specifies which readings to collect.

See Operator Rounds for the full round workflow.

Phase 2: Observations & Alerts​

In Phase 2, readings that exceed thresholds or show unusual patterns can be automatically flagged as observations or alerts for triage.

See Phase 2 Features for more information.

Mobile UX Considerations​

The mobile interface for capturing readings is optimized for:

  • Speed: Large touch targets, smart defaults, minimal taps to record a reading
  • Gloves: Interface works with thick work gloves
  • Sunlight: High contrast, readable in bright outdoor conditions
  • Noise: Visual feedback for successful data entry (no reliance on audio cues)
  • Poor Connectivity: All data stored locally first; sync happens in the background

Example: Pump Inspection Round​

Round Template: "Daily Pump Inspection"

Checkpoint 1: Pump P-101 (Centrifugal Pump)

  • Asset: Pump P-101
  • Attributes to measure:
    • Discharge Pressure (bar) - expected range: 40-50 bar
    • Suction Pressure (bar) - expected range: 2-5 bar
    • Bearing Temperature (°C) - expected range: 30-70 °C
    • Running Hours (counter) - cumulative
    • Condition (option: Good / Fair / Poor)

Captured Reading Example:

  • Discharge Pressure: 45.2 bar ✓ (within range)
  • Suction Pressure: 3.8 bar ✓ (within range)
  • Bearing Temperature: 68 °C ✓ (within range, but trending up — Phase 2 might flag this)
  • Running Hours: 12,847 hours
  • Condition: Good
  • Operator: Jane Smith
  • Timestamp: 2025-01-15 08:23:47
  • Round: Daily Pump Inspection - Instance #247

Result:

  • Last Known Value for each attribute is updated
  • Historical record stores this reading with full context
  • Operator moves to next checkpoint

See Also​