---
title: 'Workspaces and screens'
description: 'Role-based workspaces for directors, zone leads, engineers, metrologists and security, the core screens of the Operations Center, and how server-side scope shapes what each role sees.'
section: 'Operations Center'
weight: 2
related:
  - operational-issues
  - execution-and-queue
  - kpi
---

import Image from '@/components/docs/Image.astro';

## Role-Based Workspaces

OHM adapts the interface, indicators, and data selections to the user's role.

<Image
  src="/images/operations-center/02-dashboard-about-light.webp"
  srcDark="/images/operations-center/02-dashboard-about-dark.webp"
  alt="The About Operational Health Matrix panel describing the module's purpose and the cycle from detection to verified resolution."
  caption="The About OHM panel: what the module does and the full operational cycle"
  width={1440}
  height={900}
/>

### Director

Sees:

- Ecosystem Health;
- critical Issues;
- massive incidents;
- SLA violations;
- distribution by region;
- root causes;
- backlog dynamics;
- key risks;
- department workload;
- predicted problems.

<Image
  src="/images/operations-center/03-dashboard-region-head-light.webp"
  srcDark="/images/operations-center/03-dashboard-region-head-dark.webp"
  alt="OHM dashboard opened by a regional head, showing health scores and issue counters restricted to a single region."
  caption="Regional head workspace — the same dashboard automatically scoped to the region's nodes"
  width={1440}
  height={900}
/>

### Zone Manager

Sees:

- Issues of their zone;
- unassigned work;
- Over SLA;
- Reopened;
- Verification Queue;
- Need Escalation;
- assignee workload;
- capacity;
- resolution effectiveness;
- chronic problems;
- typical root causes.

<Image
  src="/images/operations-center/04-dashboard-zone-lead-light.webp"
  srcDark="/images/operations-center/04-dashboard-zone-lead-dark.webp"
  alt="Zone lead dashboard with Over SLA, Reopened, Verification Queue and Need Escalation counters, zone problem types and engineer load against capacity."
  caption="Zone lead workspace: Over SLA, Reopened, Verification Queue, Need Escalation, zone problem types and engineer load vs capacity"
  width={1440}
  height={900}
/>

### Assignee

Sees:

- my active tasks;
- deadline and `Due in`;
- overdue tasks;
- high-risk tasks;
- tasks awaiting verification;
- comments;
- recent changes;
- recommended KB articles;
- similar successfully closed cases.

<Image
  src="/images/operations-center/05-dashboard-executor-light.webp"
  srcDark="/images/operations-center/05-dashboard-executor-dark.webp"
  alt="Engineer workbench listing personal tasks with hourglass due dates, risk counters, free zone tasks and a personal change feed."
  caption="Engineer workbench: hourglass due dates, personal risk counters, free zone tasks, personal change feed"
  width={1440}
  height={900}
/>

### Metrologist

Additionally sees:

- passport problems;
- physical consistency of data;
- sensor anomalies;
- verification of metrological actions;
- Evidence from specialized reports;
- history of replacements and calibrations.

### Security role

Sees only the permitted context:

- integrity signals;
- anomalous actions;
- configuration changes;
- confirmed security incidents;
- access log;
- Evidence chain.

Sensitive data and forensic Evidence are restricted by access policies.

## Core Screens

### Dashboard

The Dashboard shows ecosystem health and the operational context:

- Overall Health Score;
- Communication Health;
- Archive Health;
- Asset Health;
- Pressure Health;
- Security Health;
- Critical Issues;
- New Today;
- Overdue;
- Massive Incidents;
- SLA Violations;
- Root Cause Distribution;
- regional map;
- trend;
- Operations Feed.

<Image
  src="/images/operations-center/10-operations-feed-light.webp"
  srcDark="/images/operations-center/10-operations-feed-dark.webp"
  alt="Operations Feed panel streaming a live journal of actions performed across the fleet."
  caption="Operations Feed — a live journal of every action across the fleet"
  width={1440}
  height={900}
/>

### Operations

The main work list contains:

- ID;
- priority;
- snapshot status;
- workflow status;
- canon;
- asset;
- region;
- root cause;
- confidence;
- first detected;
- age;
- assignee;
- due date;
- SLA;
- reopen count;
- massive incident ID;
- blocking dependencies.

<Image
  src="/images/operations-center/06-operations-issues-light.webp"
  srcDark="/images/operations-center/06-operations-issues-dark.webp"
  alt="Operations issue list where each row shows priority, snapshot and lifecycle status, owner, SLA due date, AI root cause, severity and mass-incident link."
  caption="Operations · Issues: every row is a live object — priority, snapshot status, lifecycle status, owner, SLA due, AI root cause, severity, mass-incident link"
  width={1440}
  height={900}
/>

### Issue Card

The Issue card brings together:

- the problem passport;
- affected assets;
- Evidence;
- workflow;
- root cause;
- impact;
- tasks;
- comments;
- timeline;
- related Issues;
- dependencies;
- knowledge articles;
- actions;
- verification result;
- audit trail.

See [Operational issues](/en/platform/v3/operations-center/operational-issues) for the full issue card and lifecycle.

### Assets

The asset card shows:

- identifiers;
- type and model;
- region;
- configuration;
- firmware;
- telemetry status;
- Health Score;
- subscores;
- active Issues;
- history;
- recurring problems;
- related assets;
- completed work;
- documents.

See [Asset health](/en/platform/v3/operations-center/asset-health) for the health model behind these scores.

### Massive Incidents

The massive incidents screen shows:

- scale;
- time window;
- common signature;
- affected assets;
- shared versions and dependencies;
- suspected root cause;
- recovery progress;
- residual single Issues;
- post-incident analysis.

See [Massive incidents](/en/platform/v3/operations-center/massive-incidents) for incident correlation and lifecycle.

### Timeline

The Timeline is the unified operational history:

| Time           | Event                           |
| -------------- | ------------------------------- |
| 09:14          | Issue detected                  |
| 09:16          | Evidence attached               |
| 09:18          | Correlated with OHM-2026-001811 |
| 09:23          | Assigned to Integration-2       |
| 10:04          | Work started                    |
| 11:42          | Configuration corrected         |
| 12:10          | Awaiting verification           |
| 13:00          | First clean snapshot            |
| Next day 04:00 | Second clean snapshot           |
| 04:01          | Verified by data                |
| 04:02          | Resolved                        |

<Image
  src="/images/operations-center/14-scope-timeline-light.webp"
  srcDark="/images/operations-center/14-scope-timeline-dark.webp"
  alt="Responsibility-scope timeline chart with daily detected and resolved flows, period totals and the resulting flow balance."
  caption="Responsibility-scope timeline: the detected/resolved daily flow, period totals and flow balance"
  width={1440}
  height={900}
/>

<Image
  src="/images/operations-center/15-node-timeline-light.webp"
  srcDark="/images/operations-center/15-node-timeline-dark.webp"
  alt="Node timeline presenting the operations history of a single metering station as a git-style sequence of events."
  caption="Node timeline: git-style operations history of a single metering station"
  width={1440}
  height={900}
/>

### Analytics

Analytics contains:

- Root Cause Dashboard;
- problem distribution;
- recurrence;
- SLA trends;
- detector quality;
- asset health trends;
- regional comparison;
- topology impact;
- knowledge effectiveness;
- predicted risks.

<Image
  src="/images/operations-center/16-analytics-light.webp"
  srcDark="/images/operations-center/16-analytics-dark.webp"
  alt="Analytics screen with the Root Cause Dashboard, a region map, emerging problem clusters and the Knowledge Base."
  caption="Analytics: Root Cause Dashboard, region map, emerging problems and the Knowledge Base"
  width={1440}
  height={900}
/>

### Teams

Teams shows:

- capacity;
- open load;
- overdue load;
- P1 load;
- verification load;
- utilisation;
- assignment balance;
- backlog age;
- workload forecast.

See [KPI and team performance](/en/platform/v3/operations-center/kpi) for the indicators behind this screen.

### Operations Intelligence

Operations Intelligence brings together:

- emerging risks;
- anomaly clusters;
- predicted failures;
- probable root causes;
- similar incidents;
- recommendations;
- detector health;
- AI confidence;
- unexplained changes.

See [AI Operations Intelligence](/en/platform/v3/operations-center/ai-intelligence) for how these recommendations are produced.

## Scope and Filtering

All screens use a unified scope.

Examples:

- organization;
- region;
- district;
- owner zone;
- assignee;
- asset type;
- device model;
- firmware;
- operator;
- gateway;
- canon;
- priority;
- status;
- date range.

Scope is enforced on the server side and is not merely a UI filter.

This is important for:

- security;
- separation of responsibility;
- KPI correctness;
- regional management;
- scaling;
- preventing data leakage between departments.

<Image
  src="/images/operations-center/23-ref-zones-light.webp"
  srcDark="/images/operations-center/23-ref-zones-dark.webp"
  alt="Responsibility zones screen listing each zone's lead, engineers with capacity, and the canons assigned to the zone."
  caption="Responsibility zones: leads, engineers with capacity and each zone's canons"
  width={1440}
  height={900}
/>