CW Edge Computing Gateway
Handles field acquisition and protocol conversion and acts as the edge data source or local interface provider
Third-party data sharing should first confirm the business purpose, the minimum data scope, system keys, interface direction and update period, then choose API or messaging. CW or the field gateway handles acquisition and conversion, FEXLINK handles the device model and data services, and SaaS or private deployment determines the network and data boundary. A working connection is only the first step; authentication, rate limits, error handling, data ownership and joint acceptance must all be defined.
The solution provides field data safely to a customer platform, regulatory interface or partner system. The focus is the data dictionary, access authorization, interface version and exception handling, not opening every point without limit.
Handles field acquisition and protocol conversion and acts as the edge data source or local interface provider
Maintains device, point and alarm models and provides project-confirmed API, MQTT or data export capability
Cloud deployment mode providing remote interfaces; authentication, quotas, data residency and service scope follow the actual configuration
Local deployment mode for projects on a customer private network, with data that must stay on site, or with a specified interface environment
Field instruments, devices and gateways form a traceable data source and point model
CW performs acquisition, necessary buffering and protocol conversion so that third parties do not access field devices directly
FEXLINK provides authenticated data services, interface logs and a data dictionary
Customer systems, regulatory interfaces or partner platforms obtain the required data within authorization and return processing results
Field instruments, devices and gateways form a traceable data source and point model
CW Edge Computing Gateway · FEXLINK IoT Platform
Check interface documentation, fields, keys, time format, data scope and call frequency
Providing an API does not mean the third-party system has completed business integration; fields and flows still need joint acceptance
Not recommended. Open fields on a least-necessary basis for the business purpose and configure data scope by caller identity.
API suits on-request queries and business exchange, while MQTT suits continuous message push. The choice depends on real-time requirements, system capability and interface requirements.
Use project-supported tokens, certificates or another identity mechanism, with separate accounts, permissions, key rotation and revocation.
It depends on the interface design. The platform should retain data time and receive time and support range-based retrieval or gateway-side buffering, with duplicate identification defined.
Obtain the regulator's formal interface specification, test environment and field requirements first; general API experience is not sufficient to establish compatibility.
Share the application, circuit conditions and existing system interfaces so engineers can confirm selection and implementation boundaries.
Contact FEXLINK