Custom alert management

Custom alert management enables you to define rule‑based alerts that monitor plant and device conditions in near real time. These alerts evaluate incoming data against configured conditions and notify users when abnormal or critical situations occur. Custom alerts help identify issues such as plant breakdowns, data unavailability, and device-level failures so that corrective action can be taken promptly.Alerts configured in this step rely on parameters and device hierarchy defined earlier in the onboarding flow. This ensures that alert conditions are evaluated using consistent data sources and calculated values.

What you can monitor with custom alerts

Each custom alert is created for a specific category, such as Plant or Inverter. The selected category determines the scope of the alert and the data available for defining conditions. Plant-level alerts evaluate aggregated plant metrics, while inverter-level alerts monitor conditions for individual inverters. Categories help organize alerts and ensure that conditions are applied at the correct level of the device hierarchy. This structure allows similar alert logic to be reused consistently across devices of the same type.

How alert conditions are evaluated

Alert conditions define the logic that determines when an alert is triggered. Conditions are expressed using parameter values, comparison operators, and logical expressions. For example, an alert can be triggered when active power is zero while irradiance values indicate available sunlight, or when expected data is not received from a device. Each alert includes a time window that specifies when the condition should be evaluated, such as operating hours or a full-day range. Evaluation frequency controls how often the condition is checked, while occurrence settings determine whether a single event or consecutive events are required before raising the alert. Severity levels indicate the criticality of the alert and help prioritize response.

What happens when an alert is triggered

Custom alerts are used throughout IBM® Maximo® Renewables to support operational monitoring and incident response. When an alert condition is met, the system flags the issue based on the configured severity and category. These alerts can then be surfaced in dashboards and monitoring views to provide timely visibility into plant and device health. By defining alerts during onboarding, you ensure that monitoring is active as soon as data ingestion begins, enabling early detection of performance and availability issues.