Why Manual Refresh Creates Problems
One of the most common failures in catalog analytics is that the data is out of date by the time anyone looks at it. Teams push an ACES import and then wait days or weeks for someone to manually re-run the analysis. Decisions get made on numbers that do not reflect the current state of the catalog.
​
Clarity eliminates this problem with automated catalog analytics triggered on every ACES import. Every catalog update whether it is a new application batch, a correction, or a quarterly refresh — automatically triggers a full recalculation of all your analytics models.
How Event-Triggered Processing Works
The process is fully automatic from the moment your catalog changes:
​
Step 1 — Catalog or VIO Data Changes: An ACES import is submitted or a VIO data update is processed. Clarity detects the event automatically.
Step 2 — Model Recalculation: All analytics models tied to the affected data are queued for recalculation. Coverage counts, gap lists, period comparisons, and reference model benchmarks are all reprocessed.
Step 3 — Updated Report Available: The updated report reflects the current catalog state. Change values show exactly what happened between this event and the prior one.
Why Automated Catalog Analytics Matters
The benefits extend beyond convenience:
​
Accuracy: Your coverage percentage always reflects your current catalog, not last month's version.
No Bottlenecks: No waiting for an analyst to manually trigger a refresh before a meeting.
Auditability: Every change is documented with an event ID and timestamp, providing a full audit trail.
Measurable Progress: Tracking between events lets you measure the precise impact of each catalog update.
