Before you begin
- Dashboards and Production Monitoring
How it works
Follow the arrows from left to right. Each stage prepares the information the next stage needs.
- 01Recommended
Operational record
Use reports for repeatable operational and management views.
provides the information needed for - 02Recommended
Report or export
Use exports when controlled offline analysis or sharing is required.
provides the information needed for - 03Recommended
Review variance
Use the audit trail to see who changed configuration and when.
provides the information needed for - 04Recommended
Audit change
Link findings back to the affected Product, Line, Work Order, Task, or quality record.
provides the information needed for - 05Recommended
Correct process
This stage contributes to the outcome: Use reports and immutable history to explain production results and configuration changes.
Why this connection matters: Exports are snapshots and can become outdated.
Step-by-step in Forge
Navigation: Insights and Settings → Audit Trail
- Open the required report: Open Insights or the module's report page and choose the relevant report.
- Set filters: Select Plant, date range, Product, Line, Work Order, status, or other required scope.
- Review the records: Open suspicious totals or rows to inspect the underlying operational record.
- Export when required: Select Export or Download and retain the chosen filters with the file.
- Check changes: Open Settings → Audit Trail, search for the entity, and review who changed it and when.
Watch the task
Watch: Reports, Exports, and Audit Trail
GIF walkthrough placeholder for Reports, Exports, and Audit Trail.
Rules to remember
- Exports are snapshots and can become outdated.
- Audit history explains a change but does not replace configuration review.
- Sensitive or internal fields should not be added to the public cookbook.
Ready when
- Key reports have agreed filters and definitions.
- Exports are handled according to data policy.
- Configuration changes can be reconstructed from audit history.