Component States
The Digital Twin evaluates every component of your plant and assigns it a clear operational state, so you can tell at a glance whether a part is healthy, underperforming, offline, or simply not reporting data. These states turn raw telemetry into actionable insight about each component's condition.
State Overview
Component states are determined in two ways:
- Measured: Derived directly from component telemetry data
- Inferred: Deduced from parent component analysis when direct data is unavailable
Available States
Performance States
| State | Description | Source |
|---|---|---|
| Producing Normal | Component production is within the expected range, indicating healthy operation | Measured |
| Degraded Performance | Production is significantly below the expected threshold, indicating a performance issue that requires investigation | Measured |
| Overproducing | Production exceeds the expected threshold. This typically indicates a measurement error or configuration issue rather than actual overperformance | Measured |
Inference States
| State | Description | Source |
|---|---|---|
| Suspected Not Producing | The parent component shows a production deficit that matches this component's expected power contribution | Inferred |
| Inferred Producing | The parent component is producing normally despite missing data from this child component, suggesting the component is likely operational | Inferred |
| Inferred Degraded | The parent component shows a partial deficit that may be attributed to this component's reduced performance | Inferred |
| Inference Uncertain | Available evidence from the parent component is insufficient to reliably determine this component's status | Inferred |
Data Quality States
| State | Description | Source |
|---|---|---|
| No Measured Data | No timeseries data is available for this component. This could indicate a communication issue or that monitoring has not been configured | Measured |
| Inactive Component | The component consistently reports zero or -1, indicating the endpoint is not in use or the component is intentionally disabled | Measured |
| Logger Stuck | The data logger is reporting a constant non-zero value, indicating a hardware or communication malfunction | Measured |
| Measurement Conflict | The measured value significantly conflicts with the aggregated values from child components, suggesting a measurement or configuration error | Measured |
State Interpretation
Normal Operation
Components in Producing Normal state are operating as expected and require no attention.
Requires Investigation
The following states indicate issues that may require investigation:
- Degraded Performance: Actual performance problem
- Suspected Not Producing: Likely outage
- Inferred Degraded: Possible performance issue
- Measurement Conflict: Data quality problem
Configuration or Hardware Issues
These states typically indicate technical problems rather than operational issues:
- Overproducing: Check measurement calibration and configuration
- Logger Stuck: Check data logger hardware and communications
- Inactive Component: Verify component is expected to be active
- No Measured Data: Check communication and monitoring configuration
Insufficient Information
- Inference Uncertain: More data is needed for reliable status determination
Related Features
- Digital Twin — the monitoring engine that detects and assigns these component states
- Loss Detection — how non-producing states translate into quantified, confidence-rated energy loss
- Efficiency Detection — performance-ratio analysis behind the degraded and overproducing states
Technical Implementation
For the engineering detail behind component evaluation, see the Digital Twin Architecture.