Zahlen Operator Manual

3.5 — Supervisor Dashboard Documentation

Workload visibility, escalation pressure, SLA tracking, operator coordination, and governance readiness

Page Overview

The Supervisor Dashboard is the management-level operations surface for issuer intelligence work in Zahlen. It gives supervisors a consolidated view of alerts, processor action queue items, escalation guidance, aging work, ownership gaps, and operational pressure across issuer-health workflows.

In the src-0527A architecture, the supervisor operational dashboard is built by IssuerSupervisorOperationalDashboardService. The service deliberately aggregates already-computed alert, action queue, and escalation payloads rather than creating an independent interpretation layer. This keeps the dashboard deterministic, read-only, and aligned with the same issuer-health evidence used by operators.

The supervisor page is not intended to replace the Action Queue or the Investigation Workspace. It sits above those pages. Its purpose is to help supervisors understand where work is accumulating, where ownership is missing, where escalation is required, and where governance attention may be needed.

Supervisor principle

Use the Supervisor Dashboard to answer a management question: is issuer-health work visible, owned, moving, and governed? The page is designed to reveal pressure, not merely display activity.

Where the Supervisor Dashboard Fits

The Supervisor Dashboard appears after issuer monitoring and action queue generation. It receives evidence from the alert feed, the processor action queue, and the operational escalation service. It then presents a supervisor-facing summary of operational pressure and provides links back into investigation, timeline, replay, full records, alerts, action queue, and run-history views.

Alerts

Action Queue

Escalation Evaluation

Supervisor Dashboard

Investigation / Replay

Alerts represent issuer-health signals that have been elevated from raw monitoring data. The Action Queue converts those signals into work items. Escalation Evaluation determines whether work requires stronger supervisor attention. The Supervisor Dashboard summarizes that operational condition and directs supervisors toward the correct drill-down surface.

Workload Visibility

Workload visibility is the supervisor’s ability to see how much issuer-related work exists, how that work is distributed, and whether it is actively being handled. In Zahlen, workload visibility is represented through cards such as Alerts, Queue Items, Issuers, Critical, Warnings, Escalations Needed, and High Escalations.

Concept	Meaning in Zahlen	Supervisor interpretation
Alerts	Alerts are issuer-health signals that the monitoring layer has elevated because they represent meaningful operational behavior. They may reflect recovery degradation, response-code instability, issuer degradation, or other health-related conditions.	A rising alert count means the monitoring layer is seeing more conditions that deserve attention. Supervisors should compare alert growth against queue capacity and owner availability.
Queue Items	Queue items are actionable pieces of work derived from issuer-health signals. They include severity, priority, issuer identity, metric context, routing reason, task status, and links to investigation surfaces.	A high queue count indicates operational workload. Supervisors should determine whether work is accumulating faster than operators can investigate or resolve it.
Issuers	Issuers counts the distinct issuer cohorts represented in current alert or queue activity. An issuer cohort may include issuer BIN, country, and card brand context.	If many issuers are involved, the issue may be broader than a single bank. Supervisors should compare issuer spread with Network and Monitor surfaces.
Critical	Critical represents the highest severity category of operational risk. Critical items may indicate severe issuer degradation, outage-like conditions, or urgent operational instability.	Any critical value above zero should receive immediate supervisor attention and clear ownership.
Warnings	Warnings represent elevated but not yet critical issuer-health conditions. Warning activity often appears before a condition becomes severe.	Repeated warnings should not be ignored. Supervisors should watch for clustering by issuer, country, card brand, response code, or metric type.
Escalations Needed	Escalations Needed counts work items that the escalation service believes require stronger review based on severity, age, ownership, repeat behavior, task status, attribution, or metric context.	A high escalation count means ordinary queue handling may not be enough. Supervisors should review reasons and assign ownership quickly.
High Escalations	High Escalations identify the strongest escalation category. These are items that may combine critical severity, stale work, external attribution, fraud pressure, unresolved state, or repeat behavior.	High escalations should be treated as immediate management concerns. They may require cross-team coordination or governance review.

Escalation Pressure

Escalation pressure is the amount of operational force building inside the issuer workflow. It reflects not only how many alerts exist, but whether those alerts are severe, aging, unowned, repeated, unresolved, or associated with sensitive metric types such as fraud pressure or outage attribution.

In the source architecture, IssuerOperationalEscalationService evaluates each queue row using severity, queue name, item age, repeat count, owner, task status, attribution type, and metric name. The service returns an escalation level, target queue, suggested action, and a list of reasons. This design makes escalation explainable rather than arbitrary.

Concept	Meaning in Zahlen	Supervisor interpretation
Escalation Level	Escalation level is the severity of supervisor attention recommended by the system. The service supports levels such as none, low, medium, and high.	Use escalation level to decide whether ordinary triage is enough or whether management coordination is needed.
Should Escalate	Should escalate is a boolean decision that indicates whether the work item has crossed the threshold for supervisor review.	When should escalate is true, the item should not remain passively in the queue without ownership or follow-up.
Target Queue	Target queue identifies where the escalated work should be directed. Examples may include issuer-triage, issuer-risk, or issuer-escalations depending on severity and metric context.	Use target queue to verify that the work is routed to the correct operational team or review path.
Suggested Action	Suggested action is the supervisor-facing recommendation produced by escalation evaluation. It may instruct review of aging work, immediate investigation, or stronger escalation.	Read the suggested action before assigning work. It summarizes the system’s intended operational response.
Reasons	Reasons are the explainable causes behind the escalation decision. Reasons may include aging item, stale item, unowned item, critical severity, unresolved state, repeat count, fraud-related metric, or external attribution.	Reasons should guide action. If the reason is unowned item, assign ownership. If the reason is stale item, review why progress has stalled.

SLA Tracking

SLA tracking is the supervisor’s view of whether incidents and tasks are being handled within acceptable operational time boundaries. In Zahlen, the dedicated IssuerSupervisorSLAService consumes the current supervisor payload and produces read-only SLA summaries, queue-level pressure views, owner-level pressure views, breach counts, and stale unowned work views.

SLA stands for service level agreement. In this context, it does not need to mean a customer-facing contract. It means an internal operational expectation for how long work should remain open, unowned, unresolved, or breached before it receives supervisor attention.

Concept	Meaning in Zahlen	Supervisor interpretation
Open Incident Count	Open incident count measures how many issuer incidents remain active and unresolved.	A growing open incident count indicates workload accumulation. Supervisors should compare it with active task count and owner capacity.
Active Task Count	Active task count measures how many operational tasks remain in progress or require action.	A high active task count may be healthy if work is owned and moving. It becomes risky when combined with stale, breached, or unowned indicators.
Breach Incident Count	Breach incident count measures incidents that have exceeded the expected review or handling threshold.	Breach counts require supervisor review because they indicate work has crossed an operational time boundary.
Stale Unowned Incident Count	Stale unowned incident count identifies active incidents that have aged without a responsible owner.	This is one of the clearest supervisor risks. Stale unowned incidents should be assigned or escalated promptly.
Queue SLA Rows	Queue SLA rows summarize pressure by queue, including open work, active tasks, breaches, and stale unowned counts.	Use queue SLA rows to identify which operational queue is under the most pressure.
Owner SLA Rows	Owner SLA rows summarize workload and breach pressure by owner.	Use owner SLA rows to detect overload, imbalance, or responsibility gaps across operators.
Priority Band	Priority band classifies SLA pressure as healthy, watch, or critical based on breach counts, stale unowned counts, and open workload.	A watch band means supervisors should monitor closely. A critical band means the queue or owner requires active intervention.

Operator Coordination

Operator coordination is the supervisor’s ability to ensure that the right people are handling the right issuer-health work at the right time. Zahlen supports this through owner visibility, assigned operator fields, task status, last action timestamps, resolution status, workflow audit activity, operator attribution, and action recommendations.

The supervisor metrics layer, implemented by IssuerSupervisorOperationalMetricsService, derives pressure and throughput views from the existing dashboard payload. It calculates pressure index, actionability index, throughput index, queue metrics, owner metrics, velocity rows, health rows, and alert buckets. These are designed to help supervisors evaluate whether work is moving or stalling.

Concept	Meaning in Zahlen	Supervisor interpretation
Assigned Operator	Assigned operator identifies the person or operational role responsible for a queue item or task.	Unassigned items should be reviewed first when they are high priority, aging, breached, or unresolved.
Last Action At	Last action at records when the most recent operational action occurred.	If last action is blank or old, the item may be stalled even if it is technically owned.
Resolution Status	Resolution status indicates whether the item remains unresolved, resolved, or in another closure state.	Unresolved items with old timestamps or no owner should be treated as coordination risks.
Pressure Index	Pressure Index is a derived supervisor metric that combines breach incidents, stale unowned incidents, and critical health signals.	Higher pressure means the system is seeing concentrated operational stress. Supervisors should look for the queues or owners contributing most to the score.
Actionability Index	Actionability Index counts current actionable recommendations and automation candidates from the supervisor payload.	A high actionability index means the system has identified many possible next steps. Supervisors should decide which actions should be approved, assigned, or deferred.
Throughput Index	Throughput Index combines recent audit activity and operator action volume.	Use throughput to determine whether the team is actively moving work or whether pressure is accumulating without progress.
Alert Buckets	Alert buckets classify queue and owner pressure into healthy, warning, or critical groupings based on calculated scores.	Alert buckets help supervisors identify which teams, owners, or queues require intervention first.

Governance Readiness

Governance readiness is the degree to which operational work is explainable, owned, replay-validatable, auditable, and ready for management or compliance review. The Supervisor Dashboard contributes to governance readiness by preserving summary counts, escalation reasons, links to replay, links to full records, queue state, owner state, and operational recommendation context.

Governance readiness does not mean that every item is resolved. It means that the platform can explain the current operational state and show that work is being supervised according to deterministic evidence.

Concept	Meaning in Zahlen	Supervisor interpretation
Replay Linkage	Replay linkage connects a supervisor row to replay validation for the same issuer cohort and window.	Use replay before making governance-sensitive closure, escalation, or external coordination decisions.
Full Records Linkage	Full records linkage connects an alert or queue row back to the originating job records and evidence.	Use full records when the supervisor needs to verify the data behind an alert or escalation.
Escalation Explanation	Escalation explanation is the combination of escalation level, suggested action, target queue, and reasons.	A supervisor decision is stronger when it can cite why the system escalated the work.
Read-only Aggregation	Read-only aggregation means the dashboard summarizes existing alert, queue, and escalation evidence without mutating operational state.	This preserves supervisor visibility without accidentally changing the underlying investigation or task lifecycle.
Deterministic Ordering	Deterministic ordering ensures rows remain sorted by stable rules such as escalation rank, should-escalate state, timestamp, and event identity.	Stable ordering helps supervisors trust that queue presentation is consistent rather than arbitrary.
Operational Auditability	Operational auditability means the supervisor can trace work from summary counts into alerts, queue items, investigations, timelines, replay views, and source records.	Use auditability when decisions require review, compliance confidence, or cross-team explanation.

Recommended Supervisor Workflow

Supervisor step	What it means	Evidence to inspect	Recommended action
Check status	Read the banner and summary cards to understand whether the page is quiet, warning, or degraded.	Status banner, Alerts, Queue Items, Critical, Warnings, Escalations Needed.	If escalation activity is detected, move immediately to escalation guidance and unowned work.
Find pressure	Identify where operational pressure is concentrated.	Escalation level, reasons, target queue, queue count, breach count, stale unowned count.	Prioritize high escalations, breached work, stale unowned items, and repeated issuer cohorts.
Assign ownership	Ensure active work has a responsible operator.	Owner, assigned operator, last action at, task status.	Assign unowned work before investigating lower-priority items.
Validate evidence	Open investigation, timeline, replay, or full records before making high-confidence decisions.	Investigation link, Timeline link, Replay link, Full Records link.	Use replay and full records for governance-sensitive decisions.
Coordinate action	Move work toward triage, escalation, monitoring, or closure.	Suggested action, routing reason, resolution status, workflow audit.	Document or confirm the next action, especially for aging or escalated work.

How Supervisors Should Interpret This Page

A healthy supervisor state is not simply a low number of alerts. A healthy state means that active work is visible, routed, owned, moving, explainable, and supported by evidence. A small number of unowned or stale items may be more operationally serious than a larger number of well-owned and actively handled items.

Supervisors should pay particular attention to combinations of signals. An item that is warning-level, high-priority, unowned, unresolved, and aging deserves more attention than a new warning with a clear owner and recent action. Similarly, an issuer that appears repeatedly across alerts, queue rows, and escalation guidance may represent a systemic behavior pattern rather than isolated noise.

The Supervisor Dashboard should therefore be read as an operational pressure map. It helps leadership understand whether the issuer-intelligence workflow is under control, where risk is accumulating, and which items require coordination before they become governance or customer-impacting problems.

Governance note

Supervisor review is part of Zahlen’s broader deterministic governance philosophy. The dashboard should help a supervisor explain not only what happened, but why the work was elevated, who owns it, what evidence supports it, and what operational decision should happen next.