Core Capabilities

Connect, Store, Detect, Visualize, Resolve

The value of a monitoring and alerting system isn't in feature count — it's in whether these five steps form a closed loop. Below we detail each capability's scope and delivery boundaries to avoid overpromising.

Request DemoView Products
01

AI Intelligent Alert Engine

Traditional monitoring relies on fixed threshold alarms, producing high false-alarm rates and alert storms. The platform embeds an AI time-series analysis model that learns each device's historical operating patterns, detects slow drift and hidden anomalies, auto-merges duplicate alerts, and routes graded alerts to ensure O&M staff focus on real risks.

Common Current State

Fixed thresholds: only trigger when limits are crossed — slow degradation goes unnoticed. One fault floods the screen with dozens of alerts.

Platform Approach

Dual threshold + trend logic: each device establishes a normal baseline. Duplicate alerts merged within time windows, graded as urgent/normal and routed per person.

  • Three rule types coexist: threshold, rate-of-change, and trend drift alerts
  • Same-device same-type alerts auto-merged within time windows to eliminate alert storms
  • Delayed confirmation filters transient interference like door openings and start/stop events
  • Alert grading, per-person, per-shift routing with auto-escalation on timeout
  • Alert acknowledgment and clearing actions fully logged for process traceability

Scope: AI conclusions serve as O&M reference signals — they do not replace on-site detection instruments, protection devices, or legally mandated periodic inspections.

02

Multi-Protocol Device Access

Supports MQTT, Modbus-RTU/TCP and other mainstream industrial IoT protocols. Compatible with mature third-party DTUs and sensors — no proprietary hardware required. Reuse your existing data acquisition hardware for rapid device integration.

Common Current State

Changing monitoring type means changing hardware and redoing installation. Project costs scale linearly with points added.

Platform Approach

Hardware procured independently or reused by customer. The platform connects via point table — adding new points is just a configuration task.

  • MQTT attribute reporting / command dispatch, supporting per-device keys and topic conventions
  • Modbus-RTU and Modbus-TCP register direct read with custom point tables
  • Compatible with mainstream DTUs, acquisition gateways, and temperature/humidity/vibration/current/water meter/gas meter signals
  • Heartbeat and online status detection — separate alerts for acquisition faults vs. device faults
  • Pre-integration point table and protocol documentation provided; simulated data available during commissioning

Scope: No hardware brand lock-in, no proprietary sensor development. On-site cabling and low-voltage work are the customer's or their contractor's responsibility.

03

Time-Series Data Storage & Playback

Built on a time-series database for massive device sensor data storage. Long-span historical curve queries enable complete fault process replay for root cause analysis.

Common Current State

Data scattered across local instruments or spreadsheets — impossible to reconstruct what happened after an incident.

Platform Approach

Continuous time-series storage + event markers. Any time-range curve playback, with minute-level alignment for post-incident review.

  • High-frequency raw data and downsampled aggregated data tiered storage — long-span queries without curve lag
  • Historical curve multi-indicator overlay comparison with same-period cross-day comparison support
  • Alert events linked with surrounding data display for intuitive fault progression visualization
  • Data export reports for shift handovers, audits, and long-term trend analysis
  • Auto-aging cleanup by retention policy — storage footprint stays manageable

Scope: Retention duration and export scope are determined by subscription plan. Critical data should be periodically exported and retained by the customer.

04

Visual Data Dashboard

Real-time overview of all device online status, real-time parameters, and alert statistics. Custom dashboards accessible via PC browser.

Common Current State

Big screens look impressive, but what operators really need — "which point has a problem right now" — is hard to see.

Platform Approach

Dashboard prioritizes anomalies: online rate, pending alerts, and out-of-range points at the top. Normal data collapsed.

  • Device online rate, alert statistics, and pending items on first-screen overview
  • Drill-down by area/workshop/building/shed — hierarchy aligned with on-site management structure
  • Real-time data auto-refresh with anomalous points auto-pinned and highlighted in emphasis colors
  • Role-based dashboard configuration: management sees trends, operators see action items
  • Direct PC browser access — no client installation required

Scope: Web-based primary interface. Custom spliced LED walls and 3D visualization projects are not offered.

05

Mobile Work Order Closed-Loop

Alerts generate maintenance work orders with one click. Maintenance staff receive alerts via WeChat mini-program, accept work orders, check in on-site, and capture photos — full closed-loop management.

Common Current State

Alerts sent to group chats. Who handles them, whether they're handled, and what the result was — all requires chasing people down.

Platform Approach

Alert → Work Order → Dispatch → Check-in → On-site Record → Archive. Every step has an accountable person and timestamp.

  • One-click alert-to-work-order conversion, also supports scheduled periodic maintenance work orders
  • Mini-program: accept order, on-site check-in, photo capture, per-item record entry
  • Full work order status visibility: pending acceptance, in progress, pending confirmation, archived
  • Archived records bulk exportable as standardized documents by device or time range
  • Historical work orders accumulate as device health records supporting future maintenance decisions

Scope: Mini-program requires customer to complete enterprise entity registration and verification. The platform does not handle payment or value-added telecom qualification on the customer's behalf.

Delivery Process

From Survey to Expansion — Five Steps to Go Live

Each step has clear deliverables. Customers can evaluate whether to continue at any stage, avoiding large-scale overhaul all at once.

  1. 01

    Requirements & Site Survey

    Confirm monitoring targets, point count, on-site power and network conditions. Define alert owners and handling workflow.

    Deliverable: Point list & alert specification draft
  2. 02

    Protocol & Point Table Integration

    Reuse existing DTUs and sensors. Map registers and ranges per point table. Platform-side access configuration completed.

    Deliverable: Commissioning-verified access checklist
  3. 03

    Rule Configuration & Trial Run

    Configure thresholds, trend rules, and graded routing. Calibrate false alarms with real operational data — typically 1–2 weeks of observation.

    Deliverable: Production-ready alert rule baseline
  4. 04

    Work Order Workflow & Training

    Set up equipment ledgers and maintenance templates. Train administrators and field personnel. Define on-duty and escalation mechanisms.

    Deliverable: Go-live sign-off & operations manual
  5. 05

    Expansion & Annual Service

    Scale from pilot points to full plant/zone. Annual rule optimization, report adjustments, and capacity upgrades.

    Deliverable: Quarterly operations report

Assess Feasibility for My Site

CallRequest Demo