Skip to main content

Audit Trail

The Audit Trail records every data change in OpSee: every create, update, and delete operation, with the old and new values, the user who made the change, and the timestamp. This is essential for regulatory compliance, troubleshooting, and accountability.

Audit trail view

Viewing audit logs​

Navigate to Admin → Audit Trail.

Filtering​

Use the filter panel to narrow down the logs:

FilterDescriptionExample
TableWhich database table was changedm_equipment, a_availability
ActionType of operationINSERT, UPDATE, DELETE
UserWho made the change"john.doe"
Date rangeTime periodLast 24 hours, last week, custom range
Record IDSpecific recordView all changes to record #42
ModuleApplication moduleEquipment, OEE, Production
IP AddressClient IPFilter by location or device

Log entry details​

Each audit entry contains:

FieldDescription
TimestampExact date and time of the change
UserWho performed the action
ActionINSERT, UPDATE, or DELETE
TableWhich data table was affected
Record IDThe specific record that changed
Old valuesJSON of values before the change (for UPDATE/DELETE)
New valuesJSON of values after the change (for INSERT/UPDATE)
IP AddressClient IP address
Session IDAuthentication session identifier

Record history​

To see the complete change history of a specific record:

  1. Click on any audit entry
  2. Click View record history
  3. See every change ever made to that record, in chronological order

This is useful for investigating when and why a specific equipment configuration, schedule, or OEE setting was modified.

Audit statistics​

The statistics view provides visual breakdowns:

  • Actions by type: how many INSERTs vs. UPDATEs vs. DELETEs
  • Activity by table: which modules have the most changes
  • Activity by user: who is making the most changes
  • Daily activity: trends over time

Audit statistics

:::tip Use statistics for anomaly detection Unusual spikes in audit activity can indicate problems: mass deletions, unauthorized changes, or system issues. Review audit statistics regularly. :::

Compliance use cases​

RequirementHow audit trail helps
ISO 9001Prove that process changes are tracked and authorized
FDA 21 CFR Part 11Electronic records with who/what/when tracking
GMPDemonstrate data integrity and traceability
Internal reviewsInvestigate configuration changes that affected production

Next steps​

Prerequisites​

  • Architecture Overview
  • Cockpit — complementary module