ESX Smart Edge Computing Gateway
Handles device access, edge rules and alarm upload on site; specific device scale and rule capability are confirmed by model
The key to alarm closure is not more notifications, but defined levels, responsibility, acknowledgement deadlines, response actions and closure evidence. FEXLINK or ESX generates and manages alarm status, HMI provides on-site viewing, and SMS or third-party systems serve as notification channels. Whether alarms escalate automatically, must be confirmed on site, and how false alarms are handled must be configured according to organizational process, with audit records retained.
The solution targets sites that already have monitoring but lack a response process. Through alarm grading, dispatch, acknowledgement, handling, review and closure records, an alarm becomes a traceable O&M task.
Handles device access, edge rules and alarm upload on site; specific device scale and rule capability are confirmed by model
Provides on-site alarm viewing, acknowledgement and a controlled operation entry point; interface and permissions are configured per project
Carries alarm grading, responsible persons, notification, work order status, history and statistics
Provides an alarm source on circuits that need multi-parameter electrical monitoring; specific measurement capability is confirmed by model
Can take part in alarm correlation or analysis under project-confirmed version and interface conditions; model metrics and rollout require separate acceptance
Field devices, instruments and edge rules generate raw alarms or status changes
ESX or the gateway performs initial deduplication, delay and local prompting, and backfills after network recovery
FEXLINK unifies alarm levels, responsible persons, notification, work orders and closure status
O&M acknowledges and responds on the HMI or platform, while management reviews response and closure
Field devices, instruments and edge rules generate raw alarms or status changes
ESX Smart Edge Computing Gateway · HMI (Human-Machine Interface) Local Display Panel
Verify notification targets, deduplication, escalation and timeout behaviour by alarm level
Alarm acknowledgement does not mean the fault has been cleared; closure requires a response result or review evidence
No. An alarm is a status or event, while a work order is a handling task. An alarm may need no work order, or may generate one or several.
They can be deduplicated or merged by device, point, time and event characteristics while retaining first and latest occurrence times. The rule must not mask a continuing risk.
Only for low-risk scenarios that can be verified automatically. High-risk alarms, especially those involving safety, fire or critical equipment, require manual confirmation and response.
Inspect the raw data, device status, on-site response and later recurrence. The platform can record the false alarm cause, but a single acknowledgement must not permanently suppress similar events.
Yes, through a project interface, after defining work order creation, status synchronization, closure and cancellation rules to avoid status conflicts between the platform and the work order system.
Share the application, circuit conditions and existing system interfaces so engineers can confirm selection and implementation boundaries.
Contact FEXLINK