Skip to content

Activity and Auditing

Tom Grounds - Personal edited this page Jun 20, 2026 · 2 revisions

Asset Intelligence maintains a complete and categorized history of events for each asset.

This allows you to understand:

  • What changed
  • When it changed
  • Why it changed
  • How the system reacted

Overview

The Activity view provides a timeline of asset-related events that can be filtered by category.

Available filters include:

  • All
  • Audit
  • Environment
  • Risk
  • Documents
  • Custody
  • Measurements

Each category represents a distinct type of system behavior.


Activity Categories


Audit

Audit events track user-initiated changes and system configuration updates.

These represent intentional modifications to the asset or its configuration.


Examples

  • Asset created
  • Asset name updated
  • Labels changed
  • Area (room) changed
  • Environment limits updated
  • Sensor mapping updated
  • Placement or exposure fields updated

Purpose

Audit events answer:

👉 “What did someone change?”



Environment

Environment events track changes in sensor-driven room conditions.

These reflect what is happening in the physical environment.


Examples

  • Temperature increased: 72°F → 78°F
  • Humidity dropped: 50% → 42%
  • CO₂ increased: 800 ppm → 1200 ppm
  • Sensor became unavailable
  • Sensor resumed reporting

Purpose

Environment events answer:

👉 “What changed in the real world?”



Risk

Risk events track changes in evaluated state.

These occur when the system determines that conditions have meaningfully changed.


Examples

  • Risk state changed: GREEN → AMBER
  • Risk state changed: AMBER → RED
  • Risk state changed: RED → GREEN
  • Confidence degraded due to missing sensors

Important

Risk changes are:

  • Evaluated by the decision engine
  • Confirmed by debounce rules
  • Recorded by the coordinator

Purpose

Risk events answer:

👉 “What changed in the system’s interpretation?”



Documents

Document events track changes to files and references associated with an asset.


Examples

  • Document uploaded
  • Document metadata updated
  • Document deleted
  • External reference added

Purpose

Document events answer:

👉 “What changed in the asset’s documentation?”



Custody

Custody events track ownership, responsibility, and movement of assets.


Examples

  • Asset checked out (loaned)
  • Asset checked in (returned)
  • Custody holder updated
  • Location detail changed

Purpose

Custody events answer:

👉 “Who has the asset and where is it?”



Measurements

Measurements track structured data collection sessions and profiling activity.

This is distinct from instant sensor readings.


Examples

  • Measurement session started
  • Measurement session completed
  • Measurement sensors assigned
  • Baseline profile generated
  • Environment baseline updated

Purpose

Measurements answer:

👉 “What has been observed over time?”



Event Structure

Each event typically includes:

  • Timestamp
  • Category (Audit, Environment, Risk, etc.)
  • Description of change
  • Asset reference
  • Source (system or user)

How Activity Is Generated

The system generates events through coordinated processing:

  1. Sensors update (Environment layer)
  2. Risk is evaluated (Evaluation layer)
  3. State transitions occur (Coordinator)
  4. Events are recorded in storage
  5. Activity is displayed in the UI

Relationship to Risk and Advisory

  • Risk shows the current state
  • Advisory explains what it means
  • Activity shows how you got there

Example Flow

  • Temperature rises → Environment event
  • Limit exceeded → Risk event
  • Advisory generated → Advisory event
  • User adjusts limits → Audit event

Filtering Activity

You can filter events by category:

  • Focus on configuration changes (Audit)
  • Review real-world changes (Environment)
  • Analyze system interpretation (Risk)
  • Track documentation updates (Documents)
  • Monitor movement (Custody)
  • Review long-term data (Measurements)

Real-World Use Cases


Troubleshooting

If an asset enters a risk state:

  • Check Environment events for changes
  • Check Risk events for transitions
  • Check Audit events for recent configuration changes

Pattern Analysis

Over time you can identify:

  • Repeating environmental issues
  • Rooms with poor sensor coverage
  • Assets frequently at risk
  • Opportunities for improvement

Validation

When making changes:

  • Update configuration
  • Observe resulting events
  • Confirm improved behavior

What the System Does NOT Do

The Activity system does not:

  • Perform evaluation logic
  • Modify asset state
  • Replace real-time monitoring
  • Store infinite history

It is a record of events, not the source of decisions.


Best Practices

✅ Use filters to isolate relevant activity
✅ Review history when investigating risk
✅ Track patterns over time
✅ Validate changes using Audit events
✅ Monitor Measurements for long-term trends


Summary

Activity and Auditing provides:

  • A categorized timeline of events
  • Visibility into system behavior
  • Insight into environmental changes
  • Traceability for asset management

Activity shows what happened.

Risk explains what it means.

Advisory helps you understand what to do next.

Clone this wiki locally