Alerts
4 active
One due
SLA
Due
NOP breach
Channel
One failure
Teams placeholder
Evidence
Open
Alert lineage
Operator Workbench
The screen starts with the bank decision, owner, blocker, and next handoff.
Route/realtime-alerts
Treasury owner / Risk checker / Operations
Primary decisionWhich alerts require acknowledgement, escalation, or evidence review?
Owner: Operational Risk
Current blockerNOP breach is unacknowledged and escalation timer is due.
Approvals and evidence control the next step.
Next actionOpen alert detail and acknowledge with owner note.
Acknowledge
Alert Center
Alerts are operational events with routing and evidence status.
| Severity | Type | Module | Metric | Owner | Age | SLA | Channel | Status |
|---|---|---|---|---|---|---|---|---|
| High | Breach | Market / FX | NOP ratio | Market Risk | 2h | Due | Unacknowledged | |
| High | Data failure | Data Harmonizer | Manual schedule | Data Ops | 45m | Open | Teams placeholder | Channel failure |
| Medium | Approval | Regulatory Reporting | Export evidence | Reg Reporting | 1h | Open | Pending | |
| Medium | Blocker | LCR / NSFR | HQLA policy | Liquidity Risk | 3h | Open | Open |
Acknowledge Alert Modal
Configuration and approval controls stay visible beside the workpaper flow.
| Field | Value | Evidence / action |
|---|---|---|
| Alert | NOP breach | Required |
| Action | Acknowledge / escalate / mute | Reason required |
| Owner | Market Risk | Required |
Required Inputs
Bank-provided inputs needed before this workspace can support official calculation evidence.
| Data requirement | Configuration status | Owner | Next action |
|---|---|---|---|
| Trigger | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Channel | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Recipients | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Escalation | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Quiet hours | Evidence needed | Bank data owner | Provide source extract or policy reference |
| Owner | Evidence needed | Bank data owner | Provide source extract or policy reference |
Operational States
The same screen accounts for empty, loading, blocked, validation, and approval states.
Loading stateSource checks runningLarge extracts stay in review until hash, row count, and schema validation finish.
Empty stateNo approved source rowsThe workspace shows required inputs and owner handoff instead of empty charts.
Blocked stateEvidence or approval missingOfficial output stays unavailable until the blocker is cleared by the owner.