Asset Audit History provides a comprehensive, immutable record of every change made to your assets and their operational status. This complete audit trail ensures regulatory compliance, enables troubleshooting, and provides full transparency into who made what changes and when.
Without audit history tracking:No visibility into who changed asset data or statusCan’t investigate why assets are excluded from reportsNo compliance trail for regulatory auditsRisk of unauthorized changes going unnoticed
The Solution
With Asset Audit History:Complete record of all asset and status changesClear audit trail showing who, what, whenQuick investigation of data changesAudit-ready compliance documentation
Asset Audit History automatically captures every change to your assets, including:Asset Property Changes
Asset creation and initial configuration
Updates to asset properties (name, location, type, etc.)
Changes to extension properties and custom fields
Asset geometry modifications
Asset type changes
Status Changes
Status creation (initial operational status)
Status updates (active/inactive transitions)
Status deletion (removal of status periods)
Status overlap resolution
Automatic Tracking: All changes are automatically recorded by the system - no manual logging required. The audit trail is immutable and cannot be altered after creation.
Detailed Change Information
Each audit entry provides comprehensive information for investigation and compliance:
Field
Description
Purpose
Event Type
Type of change (Created, Updated, Deleted, etc.)
Understand what action occurred
Event Time
Precise timestamp of the change
Track when changes happened
User
Who made the change (user ID and name)
Accountability and investigation
Property Changes
Detailed before/after values for each property
See exactly what changed
Status Changes
Complete status change history by status ID
Track operational status transitions
Version
Sequential version number
Understand change sequence
Correlation ID
Link related changes together
Track bulk operations
Property-Level Change Tracking
See exactly what changed with detailed before-and-after comparison:
Asset Properties: Grouped by asset type (site, well, facility, etc.)
Status Properties: Grouped by status ID for status changes
Extension Properties: Custom fields and extensions tracked separately
Status Changes: When an asset is set to “Inactive,” the audit history provides the critical trail showing who made the change and when, explaining why detections from that asset are excluded from reports.
Investigating Excluded Assets
When an asset’s detections aren’t appearing in reports, check the audit history to see who set it to “Inactive” status and when. This helps you understand whether the exclusion is correct or needs to be addressed.Regulatory Compliance
Generate complete audit trails showing all asset and status changes for regulatory submissions. The immutable audit log provides defensible documentation for compliance audits.Troubleshooting Data Issues
When asset data appears incorrect or inconsistent, review the audit history to see what changes were made, by whom, and when. This helps identify the source of data issues quickly.Tracking Integration Changes
Monitor changes made by system integrations (marked as “System” user) to ensure your source-of-truth systems are correctly synchronizing asset data.Annual Data Audits
Review the complete history of asset status changes and property updates to maintain comprehensive compliance records and verify data integrity.
query GetAssetStatusHistory($assetId: ID!, $assetTypeId: ID!) { asset(id: $assetId, assetTypeId: $assetTypeId) { id auditing { history( assetId: $assetId assetTypeId: $assetTypeId filter: { eventTypes: [STATUS_CREATED, STATUS_UPDATED, STATUS_DELETED] } ) { eventType eventTime user { userName } statusChanges { id propertyChanges { propertyName oldValue { ... on StringValue { value } } newValue { ... on StringValue { value } } } } } } }}
GraphQL Federation: Asset Audit History is available through the GraphQL API with full federation support. See GraphQL API documentation for authentication and query details.
Assets created before the audit history feature was implemented may not have historical data. The system automatically initializes audit tracking when you first access the history for legacy assets, creating a baseline event. All changes going forward will be tracked.
How do I find out who set my asset to Inactive?
Go to the asset’s History tab
Filter by event type: STATUS_CREATED or STATUS_UPDATED
Look for entries where the status changed to “INACTIVE”
The User field shows who made the change
The Event Time shows exactly when it happened
Review Property Changes to see the status reason
This information is critical for understanding why an asset’s detections are excluded from reports.
Can audit history entries be modified or deleted?
No. The audit trail is immutable by design. Once a change is recorded, it cannot be altered or deleted. This ensures the integrity of your audit records for regulatory compliance and forensic investigation.
What's the difference between 'System' and user changes?
System changes: Made by automated integrations syncing data from your source-of-truth systems (e.g., Maximo, SAP). Most asset property updates come from these integrations.
User changes: Made by authenticated users manually updating asset data or status. The most important user action is setting assets to Active/Inactive status.
How far back does the audit history go?
For assets created after the audit history feature was deployed, the complete history is available from the asset’s creation. For legacy assets, history begins when the audit system was initialized for that asset (typically when first accessed) or when the audit history feature was activated.
Why do some changes show 'null' for old or new values?
Old value is null: The property was newly created (e.g., ASSET_CREATED event or new property added)
New value is null: The property was deleted (e.g., ASSET_DELETED event or property removed)
This is normal and helps distinguish between creation, updates, and deletions
What is a 'correlation ID' and why does it matter?
A correlation ID links related changes together, especially during bulk operations or batch imports. When you see the same correlation ID on multiple audit entries, it means those changes were part of the same operation or transaction. This helps you understand the context of changes.
Can I export audit history for compliance reporting?
Yes. You can use the GraphQL API to query audit history and export the data to your preferred format for compliance reporting. The API provides complete access to all audit trail information including timestamps, users, and property changes.