Trend Analysis and Snapshots
Each time a report is generated, Control Architect saves a point-in-time snapshot of the fleet's alarm priority and state counts to MongoDB. These snapshots are the basis for the trend indicators (↑ / ↓ / →) shown in the Alarm Summary and ISA-18.2 KPIs
worksheets.
What a Snapshot Records
|
Data
|
Description
|
|
Alarm Priority Counts
|
Fleet totals for NOACTION, NONE, JOURNAL, LOW, HIGH, URGENT, EMERGNCY.
|
|
Alarm State Counts
|
Fleet totals for Enable, Disable, Inhibit.
|
|
Captured On (UTC)
|
Timestamp derived from the collection's CollectionContentDate metadata — the date the configuration data was exported to the collection, not the date the report was run.
|
|
Collection Name
|
The MongoDB collection the snapshot belongs to.
|
|
Database Name
|
The logical MongoDB database.
|
|
Captured By
|
Windows username of the user who ran the report.
|
|
Description
|
Optional free-text description (set at report generation time).
|
|
Snapshot Timestamp The snapshot timestamp uses the CollectionContentDate from the collection's metadata record rather than the current system time. This ensures the snapshot correctly reflects when the underlying configuration was captured, even if the report was generated days later.
|
How Trend Comparison Works
Each collection in the database represents a distinct point-in-time configuration export. When a report is generated or loaded, Control Architect:
1. Identifies the most recent snapshot from any other user collection in the same database — not the current collection.
2. Computes the delta (current − previous) for Critical%, Suppressed%, and Rationalization Score.
3. Writes a trend cell for each metric:
-
↑ +x.x% (improved) — metric moved in the favorable direction.
-
↓ −x.x% (worsened) — metric deteriorated.
-
→ no change — absolute delta < 0.1%.
For Critical% and Suppressed%, lower is better (↓ = improved).
For Rationalization Score, higher is better (↑ = improved).
Trend Cell Color Coding
|
Trend Direction
|
Cell Fill
|
|
Improved
|
Green
|
|
Worsened
|
Red
|
|
No change
|
No fill (neutral)
|
First Report — No Previous Snapshot
If no snapshot exists from another collection (e.g. this is the first report ever run, or only one collection exists in the database), the trend cells display:
↔ No prior collection
in italic text with no color fill. This is normal behavior and does not indicate an error.
Viewing All Snapshots
The Snapshot History panel (accessible from the Alarm Analysis Report view) lists all snapshots found across every user collection in the current database, sorted by collection name and then chronologically. Each entry shows the capture date, collection, database, and optional description.
Snapshot Storage
Snapshots are stored as JSON documents inside the MongoDB collection they belong to, using document type AlarmAnalysisSnapshot. Exactly one snapshot is retained per collection — repeated report generation for the same collection overwrites the previous snapshot rather than accumulating duplicates.
|
Best Practice To maintain a meaningful trend history, generate a report each time a new collection is created from an updated configuration export. Each collection-level snapshot then represents one point on the alarm rationalization progress timeline.
|
