Skip to main content
IronKernel Platform

AxialOps: Alert & Notification System

Rule-based threshold/trend/anomaly/fault alerts with escalation and CMMS auto-work-order handoff.

Problem

Rule-based threshold/trend/anomaly/fault alerts with escalation and CMMS auto-work-order handoff.

Capability

Proactive fault detection with configurable rules and real-time notifications.

How it works

  1. 1 Rule-based threshold/trend/anomaly/fault alerts with escalation and CMMS auto-work-order handoff.
  2. 2 Multi-channel delivery and notification control with suppression behavior to reduce alert fatigue.

Operational outcomes

  • Rule-based threshold/trend/anomaly/fault alerts with escalation and CMMS auto-work-order handoff.
  • Multi-channel delivery and notification control with suppression behavior to reduce alert fatigue.

Integration boundaries

  • Dashboard & Overview
  • Device Management

Proof model

Feature-level proof

  • Alert & Notification System scope is defined in product module catalog.

    verified

    docs/products/axialops/product.md · Module Catalog > Alert & Notification System

  • AxialOps dashboard and overview workflows are implemented in portal-facing service modules.

    verified

    docs/products/axialops/product.md · Module Catalog > Dashboard & Overview

    Code: backend/services/axialops/internal/modules/dashboardgateway

    Contract: proto/axialops/session/v1

  • AxialOps analysis workflows are implemented in axialops backend modules.

    verified

    docs/products/axialops/product.md · Module Catalog > Analysis Workbench

    Code: backend/services/axialops/internal

    Contract: proto/axialops/learning/v1

Solution routes that reuse this feature

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (0).

This feature is currently not linked to a named solution route. Review this behavior directly, then validate continuity through adjacent solution and feature-map routes.

Continuity routes for this capability

Route-level continuity checks where this feature appears in product-pair workflows.

This capability is currently mapped in adjacent solution and continuity routes. Browse linked solution routes first, then return here when cross-route continuity is expanded.