ESX Smart Edge Computing Gateway
Acquires device status on site and provides device or point identifiers to the platform
Equipment asset management starts with unique codes and stable master data, not with building a page first. Each device should be linked to type, model, installation point, commissioning date, responsible person and status, and maintenance records then link alarms, inspections and work orders through the device code. FEXLINK can record and query, but a trustworthy register cannot form automatically without import rules and responsible owners.
The solution brings device registers, installation points and maintenance history from spreadsheets and multiple systems into one model. The focus is coding rules, import templates, status changes, history retention and linkage with alarms and work orders.
Acquires device status on site and provides device or point identifiers to the platform
Provides on-site device status viewing and the necessary maintenance operation entry point
Stores device master data, installation points, responsibility relationships, maintenance records and historical status
Connects field device identifiers, communication status and operating data to the platform
Deployment mode for projects needing local data control; database, backup and permission responsibility are confirmed per project
Field devices, instruments and gateways provide device codes, operating status and communication status
Edge devices maintain the point-to-device relationship and retain necessary status during network loss
FEXLINK acts as the asset master data and maintenance record platform, linking alarms, work orders and historical data
On-site and back-office staff query devices, record maintenance and review lifecycle changes according to permissions
Field devices, instruments and gateways provide device codes, operating status and commu…
ESX Smart Edge Computing Gateway · HMI (Human-Machine Interface) Local Display Panel
Sample-check device code uniqueness and the completeness of required fields, installation points and responsible-person assignments
The platform register cannot replace the financial fixed asset ledger or the statutory equipment file; synchronization must be designed separately if needed
Yes, provided they are unique across the system and can be mapped to the old system. If the old number repeats at other sites, add a site or organization prefix and keep the mapping.
Distinguish installation point from physical device. The new device can take a new code while the installation point keeps its historical relationship, so location history and device identity are both traceable.
Yes, through a project interface, but the master data source, field mapping, synchronization frequency and conflict handling must be defined so that both sides cannot be edited freely.
At minimum device, time, maintenance type, cause, executor, result and attachments or references. Specific fields follow the organizational process.
The register can start from the existing device list and acquisition points, but unique codes, installation locations, owners and status must be added. Missing history should be marked as pending verification, not backfilled with unconfirmed records.
Share the application, circuit conditions and existing system interfaces so engineers can confirm selection and implementation boundaries.
Contact FEXLINK