Package 2 of 4
It checks your data on the required schedule, from every half hour to once a month, against rules agreed with you, and hands every exception to its owner with a recommended action.
Know about problems in time to act.
A report arrives because you scheduled it, even when there is nothing to flag. An alert works the other way round: it arrives only when something breaks - which is why it gets read.
Compass Control checks your data on the required schedule, from every half hour to once a month, against rules agreed with you. When a rule breaks, the exception enters a queue: which rule, what threshold, who owns it, how much money or time is at risk, and the recommended action. The alert reaches the right people and shows the transactions behind it. When everything is in order - silence.
For example, in Priority or NetSuite:
This is the starting catalogue. The rules themselves are set with each customer.
The catalogue is not closed: when an exception keeps coming back, it becomes a rule.
Alerts inherit permissions. A sales rep sees only alerts for their own customers.
No AI is used for monitoring. The checks are your rules, run on your existing server, and the data stays on it.
The system recommends. A person approves.
Every exception has an owner and a recommended action. The system recommends, and a person approves every write-back into your ERP.
Compass Control is not a robot posting into your ERP on its own.
Monitoring itself uses no AI and runs on your existing server, so it carries no additional monthly running cost. Setup is priced per project.
Useful is not enough. It has to be measurable and owned.
The examples above are a starting point. We set three things with you: