Operations Center Guide
Use Operations Center to monitor alerts, exceptions, SLAs, ownership, escalation, executive summaries, playbooks, analytics, and cross-module signals.
The Operations Center helps teams see what needs attention across modules. It can surface overdue approvals, stock issues, failed syncs, failed payments, stuck workflows, pending transfers, scanner problems, vendor delays, report mismatches, and other operational exceptions.
System owners may also see health signals for scheduled workloads, queue processing, failed jobs, system logs, database storage, and observability links. Those signals help separate a user workflow issue from a platform, scheduler, queue, or integration problem.
What Operations Center Tracks
| Signal | Example | Typical Owner |
|---|---|---|
| Alert | Low stock, failed payment, failed sync, overdue task, or scanner issue. | Responsible team or organization admin. |
| Exception | Blocked receiving, stuck workflow, report mismatch, or transfer variance. | Operations lead or responsible team. |
| SLA | Approval, RFQ, receiving, or support response is overdue. | Approver, procurement lead, or support owner. |
| Executive summary | High-level view of open risks, delays, and operational pressure. | Managers and leadership. |
| Analytics | Trends by module, warehouse, vendor, workflow, or branch. | Managers and analysts. |
| System health | Scheduler, queue, failed jobs, database storage, logs, and owner-only service checks. | System owner or technical admin. |
Scheduled Workloads To Watch
- Low-stock reminders, approval digests, adjustment approval reminders, procurement request reminders, RFQ response reminders, PO delivery reminders, quotation expiry reminders, and overdue invoice digests.
- Workflow/integration failure digests, plan and billing risk reminders, security/device login digests, tenant deletion reminders, and queue/system health digests.
- Scheduled reports, cleanup jobs, retention jobs, sitemap generation, and queue worker heartbeats.
- If many reminders stop at once, check system health and queue status before troubleshooting each notification separately.
Exception Handling Workflow
- Open the alert or exception and identify the module, record, owner, and urgency.
- Check whether it affects one user, one record, one branch, or many teams.
- Assign or confirm the responsible owner.
- Follow the related playbook or module troubleshooting guide.
- Add notes, evidence, or status updates so others understand progress.
- Escalate if the issue blocks sales, receiving, finance close, supplier deadlines, or customer delivery.
- Close only after the record, report, sync, payment, transfer, or workflow is confirmed.
Common Playbooks
- Failed sync: check mapping, required fields, retry status, and external connector health.
- Stock mismatch: check filters, recent movements, transfers, returns, counts, and scanner records.
- Workflow stuck: check assigned approver, current step, SLA, and missing fields.
- Payment issue: check provider message, invoice, reference, and whether payment was deducted.
- Report mismatch: check date range, status filters, branch, warehouse, and source records.
- Reminder missing: check notification settings, reminder cadence, scheduler health, and whether there are qualifying records.
Common Mistakes
- Closing an exception before the source record is corrected.
- Escalating without record numbers or evidence.
- Assuming all alerts are system issues when many are access, status, or process issues.
- Leaving ownership blank, which delays follow-up.
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.