Synthetic data · thresholds placeholder · scenario time D0 06:40 (SYN)G-09
Executive Escalation Center
Which escalations need Core Group coordination now?
Scope Group · all entities
Period P07 MTD (SYN)
Last refresh 06:25 (SYN)
Clocks are rule-based; routing drafts are AI-generated until accepted
Sources and lineage
Workflow counters
EFF-002 Open critical alerts
1
EFF-006 Alerts without accepted owners
1
Overdue +2 h
EFF-007 Overdue actions
0
EFF-008 Average resolution time
2.5 days
EFF-009 Closed escalations · 30 d
11
▲ +3 vs prior
EFF-010 Repeat issues · 90 d
4
Critical-material supply · meter mapping
EFF-011 Root causes eliminated · YTD
8 of 9
78%
Focus of this page
Escalation ladder (levels and clock durations per escalation rule D-08)
AnswersAt which level is each escalation, and is any stuck?
L0 · Entity
2 items
Entity A1 · 2 items
Count only; owned in the Entity lens
L1 · Business
1 item
ALT-SYN-2047 MP03
Unowned · overdue +2 h
L2 · Core Group
1 item
INC-SYN-0142
War room active
L3 · Owner
1 decision
DEC-SYN-0219
Due 11:00
Alert without owner · routing draft (AI) awaiting human acceptance
Alert
Draft owner role
Draft due
Draft path
Decision required
Clock
Entity Executive · Entity A2 (AI draft)
D+3
L0 → L1 → L2
Approve contractor recovery plan
Overdue +2 h
Escalations
Issue
Severity
Exposure
Named owner (role)
Due
Status
Escalation
Next action
Critical
−₹56.2 m · ₹27.2 m (FCST)
Entity Executive · Entity A1
D0 11:00
War room active
L2 · on time
Owner decision DEC-SYN-0219
Medium
₹127.2 m value at risk
Unowned · routing draft: Entity Executive Entity A2
D0 09:00
Unowned
Overdue +2 h
Accept or reassign
Core Group actions
Accepting ownership is done by the entity role; Core Group can reassign or escalate (06 rows 2, 3, 8, 9, 14).