AWRA Ops Center puts alerts, anomalies and approvals on one command surface. Every Smart Alert can be given an owner and acknowledged with a note, and resolves itself when the condition behind it clears — so the board shows what is wrong now, who has it, and nothing that has already gone away.
Ops Center separates urgency from noise by grouping signals into Alerts, Anomalies and Approvals. Each stream lists the records behind every signal, one click from the record itself.
Alerts Hub
Seven Smart Alert checks — low stock, stockout risk, locations over capacity, late purchase orders, overdue invoices, below-cost items and adjustments awaiting approval — each with a severity, an owner, an acknowledgement and automatic resolution.
Anomaly Radar
Pricing anomalies before they cost you margin: items selling below cost, items under five per cent margin, and items with no selling price at all.
Approvals Command
One inbox for fourteen kinds of pending decision across inventory, procurement, sales, assets, compliance and HR — from stock adjustments and purchase orders to leave, overtime and payroll runs — plus unassigned helpdesk tickets.
An Alert Has A Lifecycle Now
Smart Alerts used to be recomputed and forgotten between two views. Each alert is now an occurrence: it opens when its condition appears, carries an owner and an acknowledgement while it lasts, and closes on its own when the condition clears.
Open
Condition appears
“Overdue invoices: 4 invoices are overdue.” First seen at 07:45. Assign it to the credit controller, who is notified in the app.
Acknowledged
Someone has it
Grace acknowledges with a note: “Chasing all four today, two promised by Friday.” Reopen it if the promise falls through.
Resolved
Condition clears
The last invoice is paid. The next time the board is checked, the alert closes with its resolution time. If invoices go overdue again, a fresh, unowned alert opens.
Acknowledging an alert nobody owns makes it yours, so “in hand” always has a name on it.
An acknowledgement never silences a recurrence — a returning condition is a new occurrence.
A cleared alert cannot be reassigned or acknowledged; the board tells you it has already cleared.
The in-app assistant reads the same owners and acknowledgements when you ask it about alerts.
Who Has It, At A Glance
The alerts board shows each live alert with its severity, the worst records behind it, and its state: open with no owner, owned, or acknowledged with a note. Filter by severity, or refresh the checks on demand.
5 items at or below reorder point · Owner: Faith W.
Acknowledged
Overdue invoices
4 invoices overdue · Owner: Grace N.
Acknowledged
Delayed purchase orders
2 orders past delivery date · Owner: Peter O.
Owned · open
Locations over capacity
Bay C-04 at 260 of 200 units · no owner
Open
Command Workflow In Practice
Ops Center follows a repeatable routine so teams move from detection to closure with less friction and a name on every open item.
01
Detect
Alerts, anomalies and the control tower recompute from your live records at least every fifteen minutes, or on demand.
02
Assign
Give each alert an owner from your active users. They are notified in the app with a link straight to it.
03
Acknowledge
The owner acknowledges with a note saying what is being done, and can reopen if the plan changes.
04
Resolve
Fix the underlying records — receive the order, collect the invoice, reprice the item — and the alert closes itself once the condition is gone.
Operational Intelligence
Ops Control Tower
One executive view of stock risk, delayed purchase orders, unpaid invoices, suspicious adjustments, pending payouts, overdue tasks, who is on leave today and payroll that is due.
The control tower gathers nine sections from across the modules into one triage layer, each with its own severity and drill-down links into the records behind it.
Inventory Integrity
Stock at risk by reorder point and days of cover, and stock adjustments ranked by how unusual they look against the item’s own movements.
Financial Oversight
Unpaid invoices by age, late purchase orders, pending payouts and payroll runs that are due.
Section
What it shows
Stock Risk
Items at or near reorder point, ranked with days of cover
Delayed Purchase Orders
Open orders past their delivery date
Unpaid Invoices
Customer invoices still owed, oldest first
Suspicious Adjustments
Adjustments out of line with the item’s movements
Pending Payouts
Payments waiting to go out
Overdue Tasks
Project tasks past their due date
On Leave Today
Who is away, so you know who cannot act
Blocked by Terminated Assignee
Work still assigned to someone who has left
Payroll Due
Payroll runs that are due
Ops Center — what the command surface does, and what we can add
What AWRA OpsHub does today
Three streams on one surface — Smart Alerts, the anomaly radar and the approvals hub — each linking to the records behind every signal.
An owner, an acknowledgement and a note on every Smart Alert, with an in-app notification to the person assigned.
Automatic resolution when an alert’s condition clears, and a fresh occurrence when it comes back.
Fourteen kinds of pending approval in one inbox, across inventory, procurement, sales, assets, compliance and HR.
A control tower of nine sections, from stock risk and suspicious adjustments to payroll due and work blocked by a leaver.
More we can add to your workspace
Owners and acknowledgements on anomalies and control-tower sections, matching what Smart Alerts carry today.
A resolved-alert history with time to acknowledge and time to resolve, for a monthly operations review.
Alert delivery by email, SMS or chat, beyond the in-app notification to the owner.
Escalation of an alert left unacknowledged, to the owner’s manager after a time you set.
Thresholds you set per alert, such as a different cover window or a minimum overdue amount.
Approval routing by value, sending a large purchase order to a different approver than a small one.
Each row in the middle column extends a command surface that already records alert occurrences, owners and acknowledgements. Tell us what your operations review needs to see.
Ops Center
Frequently asked questions
What is AWRA Ops Center?
A command surface with three streams: Smart Alerts for operational exceptions, the anomaly radar for pricing problems, and the approvals hub for every pending decision. The control tower adds an executive view across nine sections.
Can alerts be assigned to someone?
Yes. Each Smart Alert can be given an owner from the active users in your workspace, with an optional note. The owner is notified in the app with a link to the alert.
What does acknowledging an alert do?
It records who has the alert in hand and when, with a note if you add one. Acknowledging an alert that nobody owns makes you the owner. It can be reopened if the plan changes.
Do alerts close on their own?
Yes. When the condition behind an alert clears, the alert is marked resolved the next time the board is checked. If the condition returns, it opens as a new alert with no owner, so an old acknowledgement never hides a new problem.
What does the anomaly radar look for?
Items selling below cost, items priced under five per cent margin, and items with no selling price.
Which approvals appear in the hub?
Fourteen kinds across inventory, procurement, sales, assets, compliance and HR — including stock adjustments, procurement requests, RFQs, quotations, purchase orders, invoices, transfers, asset movements, deletions, item changes, leave, overtime and payroll runs — plus unassigned helpdesk tickets.
How current is the information?
Alerts and anomalies refresh at least every fifteen minutes and the control tower at least every ten, and each can be refreshed on demand.
Help Center
Need a quick answer while you read?
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.
We use necessary cookies for secure sessions. With your permission, we also use cookies and browser storage for preferences, analytics, and demo engagement. Privacy Policy
AWRA OpsHub
Cookie settings
Cookie Consent Manager
Necessary cookies stay on for login, CSRF protection, and security. You can choose the optional categories below.
Overview
General Information
AWRA uses cookies and browser storage to keep public pages secure, remember selected preferences, measure website performance, and manage demo engagement prompts.
You can choose whether functional and marketing engagement storage apply. Analytics measurement is always active in this AWRA setup.
These settings apply to AWRA public website experiences such as the homepage, feature pages, pricing calculator, blog, help center, and request-demo page. Authenticated dashboard and vendor portal sessions still rely on required security cookies.
Required
Always active
Functional
Optional
Analytics
Always active
Marketing
Optional
For more context on privacy handling, open the Privacy Policy.
Required Cookies
Required Cookies
Always Active
Required cookies and storage support basic website delivery, secure sessions, request protection, and remembering the consent choice itself.
These cannot be switched off from this manager because disabling them would break login/session behavior, form protection, or the ability to remember the privacy choice you save.
Cookie details
Session security: keeps secure server sessions working while browsing AWRA.
CSRF protection: helps verify form submissions and protect requests.
Consent record: stores the preference decision so the banner does not keep asking after a choice is saved.
Examples: Laravel session cookies, CSRF tokens, and the AWRA consent preference record.
Duration: session security can expire with the browser/session; saved consent can last longer so the same browser remembers the choice.
Functional Cookies
Functional Cookies
Functional storage improves the public website experience by remembering interface choices, helper states, dismissed notices, and short-lived interaction preferences.
Turning this off does not stop secure required cookies or analytics. It only limits optional convenience memory.
If disabled, AWRA may show some helper prompts again or forget non-essential display choices. Core public pages, contact forms, and request-demo forms still work.
Cookie details
UI preferences: remembered display choices and helper states where available.
Dismissed notices: session-level or preference-level memory for notices the visitor has closed.
Frequency helpers: optional browser storage that prevents repeated prompts when allowed.
Examples: localStorage or sessionStorage values for dismissed banners, guide/helper states, and lightweight public-page preferences.
Effect when off: AWRA avoids optional convenience memory unless it is also allowed through marketing and engagement preferences.
Analytics Cookies
Analytics Cookies
Always Active
Analytics helps AWRA understand public page performance, traffic patterns, and content usefulness so we can improve the marketing website.
This category does not by itself enable demo popups, exit-intent prompts, or advertising pixels. Those are controlled by Marketing & engagement.
In this AWRA setup, Google Analytics and Google Tag Manager measurement are treated as mandatory website measurement and remain active.
Cookie details
Google Analytics / GTM: measures aggregate traffic and page activity.
Performance insight: helps identify which public pages, docs, and demo paths visitors use.
Operational signal: supports website quality decisions without enabling demo popups by itself.
Examples: Google measurement identifiers such as GA/GTM tags and related browser identifiers set by Google scripts.
Use: page views, source/referrer trends, public content performance, and product education page effectiveness.
Marketing & engagement
Marketing & engagement
Marketing and engagement storage supports demo prompts, exit-intent prompts, campaign attribution, and future advertising pixels.
When disabled, AWRA will not auto-open demo or exit-intent popups. CTA buttons can still open a form because that is a direct visitor action.
When enabled, AWRA can remember that a visitor already saw, dismissed, or submitted a demo prompt so the same popup is not repeated aggressively.
Cookie details
Demo prompt memory: tracks whether an auto prompt or exit prompt was recently dismissed.
Demo submission memory: avoids asking again after a visitor submits a demo request.
Campaign context: keeps source page, referrer, and UTM context available for demo requests.
Examples: popup frequency caps, demo-submitted flags, engagement source fields, and UTM/referrer context.
Effect when off: auto demo prompts and exit-intent prompts stay blocked; normal navigation and manually clicked CTA buttons still work.