Workspaces and screens

Role-Based Workspaces

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

Director

Sees:

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

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.

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.

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.

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.

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 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 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 for incident correlation and lifecycle.

Timeline

The Timeline is the unified operational history:

Analytics

Analytics contains:

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

Teams

Teams shows:

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

See KPI and team performance 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 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.