ESX Smart Edge Computing Gateway
Handles device access, edge computing and upload at some sites; device scale, points and network capability are confirmed by specific model
Multi-site unified monitoring should first establish unique codes for sites, gateways, devices and points, then unify the upload protocol, time basis and alarm grading. CW or ESX handles field access, and FEXLINK handles centralized monitoring, permissions and reports. Whether the platform supports a given site scale, deployment mode and third-party interfaces must be confirmed against the actual configuration; project capability cannot be estimated from site count alone.
The solution is for parks, distributed energy, water or outdoor facilities managed across many sites. The focus is to establish a scalable site tree and point semantics once, instead of each site using its own naming and alarm rules.
Handles device access, edge computing and upload at some sites; device scale, points and network capability are confirmed by specific model
Provides a local human-machine interface at sites that need on-site viewing or operation; interface and display capability are confirmed by model
Provides the site tree, device models, alarm center, permissions, history and reports
Handles site device access, protocol conversion, buffering and upload
Cloud deployment mode chosen per actual service configuration, suited to fast connection of multiple sites
Local deployment mode for projects with defined data residency, network isolation or O&M responsibility requirements
Field instruments, controllers and subsystems at each site connect to an edge gateway or ESX through project-confirmed interfaces
Edge devices perform acquisition, point mapping, necessary buffering and local alarms, and backfill after network recovery
FEXLINK organizes data by organization, region, site, device and point, and configures unified alarms and permissions
Provides multi-site overview, site details, alarm response, historical queries and reports, with each role viewing its own scope
Site Online Rate
The platform calculates the ratio of sites with normal communication to expected-online sites
Online rate change statistics by region and time window
The platform itself cannot fix site network, power supply or field device faults
At site-ID granularity; sites with normal communication heartbeat counted as online
No. Cloud service or local deployment can be chosen depending on data residency, network, O&M and account requirements. The interfaces and responsibility boundaries differ.
Visibility is determined by role and data permission. The platform should support authorization by organization, region or site and retain viewing and operation audit records.
During an outage the platform usually cannot receive data in real time; whether data is backfilled after recovery depends on edge buffering. Local site alarms should be handled at the site wherever possible.
Device types, point semantics, alarm levels and naming rules must be unified first and then mapped on the platform. Reusing each site's original alarm names hinders cross-site comparison.
Yes, through project-provided API or messaging interfaces, after confirming the data dictionary, authentication, frequency, network and both parties' responsibilities.
Share the application, circuit conditions and existing system interfaces so engineers can confirm selection and implementation boundaries.
Contact FEXLINK