Asset and ecosystem health

Asset Health

At the center of the Operational Health Matrix stands not an event, not an alarm, and not a task, but the operated asset.

Each asset has its own operational state, which is continuously calculated based on telemetry, operating history, analytics results, and confirmed Operational Issues.

Asset Health makes it possible to assess not only the current state of the equipment, but also its change trend, operational risk, and impact on the overall resilience of the infrastructure.

Asset Health Model

Each asset is represented by a single digital profile.

flowchart TD
    A["Asset"] --> CFG["Configuration"]
    CFG --> TEL["Telemetry"]
    TEL --> EV["Evidence"]
    EV --> ISSUE["Operational Issues"]
    ISSUE --> MH["Maintenance History"]
    MH --> HS["Health Score"]
    HS --> PRED["Prediction"]

The asset card contains:

• identifiers;
• equipment type;
• manufacturer;
• model;
• serial number;
• region;
• coordinates;
• owner;
• organization;
• current configuration;
• change history;
• installed firmware;
• linked devices;
• maintenance log;
• active problems;
• resolved problems;
• the computed Health Score.

Health Domains

The asset’s state is assessed across several independent domains.

Each indicator is calculated independently.

Health Components

The Health Score is an aggregated indicator.

For example:

The final state is determined after normalizing all components.

Health States

Each asset is in one of the operational states.

Threshold values are defined by the organization’s policy.

Health Trend

OHM stores not only the current value, but also the direction of change.

flowchart TD
    EXC["Excellent"] --> GOOD["Good"]
    GOOD --> ATT["Attention"]
    ATT --> DEG["Degraded"]
    DEG --> CRIT["Critical"]

The system simultaneously calculates:

• degradation rate;
• duration of the current state;
• number of transitions;
• recurrence.

This makes it possible to identify equipment that is still working but rapidly losing stability.

Chronic Assets

An asset automatically receives the Chronic flag if the same Operational Issues recur persistently.

For example:

• five battery replacements in a year;
• constant archive loss;
• regular communication problems;
• multiple reopenings of the same canon.

Such equipment requires separate analysis, even if it is currently operating correctly.

Ecosystem Health

Asset Health assesses an individual device.

Ecosystem Health characterizes the state of the entire infrastructure.

The calculation includes:

• all active assets;
• all Operational Issues;
• problem criticality;
• massive incidents;
• data quality;
• the state of the communication infrastructure;
• operational KPIs.

Hierarchical Health

OHM calculates the state at every level.

flowchart TD
    A["Asset"] --> ST["Station"]
    ST --> D["District"]
    D --> R["Region"]
    R --> ORG["Organization"]
    ORG --> ECO["Entire Ecosystem"]

This makes it possible to instantly identify the region with the greatest impact on the overall indicator.

Weighted Aggregation

The Ecosystem Health calculation uses a weight for each asset.

The weight can take into account:

• equipment type;
• commercial significance;
• number of consumers;
• object category;
• volume of transported gas;
• impact on safety.

As a result, the failure of a backup facility does not have the same impact as the failure of a central node.

Operational Heat Map

The results are displayed as a heat map.

Each region is colored according to its current Health Score.

Additionally, the map displays:

• the number of Critical Issues;
• massive incidents;
• SLA breaches;
• Communication Health;
• Archive Health;
• a degradation forecast.

Health Score

The Health Score is an integral indicator of an object’s operational state.

It is intended for:

• comparing assets;
• assessing regions;
• ranking risks;
• assessing operational efficiency;
• analyzing dynamics.

The Health Score is not a replacement for telemetry and does not hide primary information.

It is an aggregated operational index.

Base Formula

The base model uses a weighted sum of domains.

where the sum of all weights equals one.

Domain Score

Each domain is calculated independently.

For example:

flowchart TD
    COM["Communication"] --> AV["Availability"]
    COM --> FR["Freshness"]
    COM --> SS["Session Stability"]
    COM --> SQ["Signal Quality"]
    AV --> CS["Communication Score"]
    FR --> CS
    SS --> CS
    SQ --> CS

The remaining domains are calculated in a similar way.

Penalty Model

Operational Issues reduce the final indicator.

The size of the penalty depends on:

• Severity;
• Priority;
• duration;
• recurrence;
• the confirmed Root Cause;
• business impact.

For example:

flowchart LR
    CI["Critical Issue"] --> PEN["Penalty"]
    PEN --> HSD["Health Score decreases"]

After confirmed remediation, the penalty is gradually lifted.

Recovery

OHM does not restore the Health Score instantly.

After remediation, a stabilization period applies.

This prevents a situation where a device continuously switches between the “healthy” and “faulty” states.

Historical Health

The full history of the indicator’s changes is stored for each object.

This makes it possible to analyze:

• degradation;
• the impact of repairs;
• maintenance effectiveness;
• seasonal changes;
• equipment service life.

The history is not recalculated retroactively.

Health Prediction

Given sufficient history, the system builds a forecast of Health Score changes.

The forecast uses:

• degradation rate;
• recurrence;
• seasonality;
• related events;
• maintenance quality;
• results of previous repairs.

The resulting forecast is used exclusively as an analytical recommendation and does not replace engineering judgment.