Home / Solutions / Third-Party Platform API and Data Sharing

Third-Party Platform API and Data Sharing

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.

Device-Edge-Cloud CollaborationCentralized MonitoringSystem Integration

Solution overview

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.

Applicable industries

  • Multi-industry industrial sites
  • Industrial parks
  • Manufacturing plants

Primary user roles

  • Automation engineers
  • System integrators
  • O&M staff

Problems addressed

  • Data must reach a customer or regulatory platform
  • Interface fields, keys and refresh periods differ, so transferred data cannot be used directly
  • Sharing scope, authentication, logging and data responsibility lack clear boundaries

Recommended product combination

CW

CW Edge Computing Gateway

Handles field acquisition and protocol conversion and acts as the edge data source or local interface provider

FEXLINK

FEXLINK IoT Platform

Maintains device, point and alarm models and provides project-confirmed API, MQTT or data export capability

SaaS

SaaS Cloud Deployment Option

Cloud deployment mode providing remote interfaces; authentication, quotas, data residency and service scope follow the actual configuration

System architecture and data flow

Third-Party Platform API and Data Sharing System TopologyFour-layer data flow across perception, edge control, platform and application for Third-Party Platform API and Data Sharing.01Perception layer
Field instruments, devices and gateways form a traceable data source and point model
02Edge / control layer
CW performs acquisition, necessary buffering and protocol conversion so that third parties do not access fie…
03Platform layer
FEXLINK provides authenticated data services, interface logs and a data dictionary
04Application layer
Customer systems, regulatory interfaces or partner platforms obtain the required data within authorization a…

Perception layer

Field instruments, devices and gateways form a traceable data source and point model

Edge / control layer

CW performs acquisition, necessary buffering and protocol conversion so that third parties do not access field devices directly

Platform layer

FEXLINK provides authenticated data services, interface logs and a data dictionary

Application layer

Customer systems, regulatory interfaces or partner platforms obtain the required data within authorization and return processing results

Data flow

  1. Both parties confirm data purpose, fields, keys, direction, period and sensitivity level
  2. The platform produces interface documentation or a data dictionary and assigns the caller a separate identity and permissions
  3. The caller requests data, and the platform validates identity, data scope, frequency and parameters
  4. The interface records request, response, failure reason and data time, retrying or alarming per policy
  5. Compatibility assessment, joint testing and a switchover plan are completed before interface version changes

Integration and interfaces

  • Project-confirmed HTTP API, MQTT or another customer-specified interface can be used; the protocol version follows the parties' documentation
  • Interface authentication can use project-supported tokens, certificates or customer identity mechanisms, with key rotation and revocation defined
  • Cross private network or public network connections require customer network approval, firewalls and access control
  • Where control results must be received from a third party, define write-back permissions, confirmation and failure handling separately

Applicable standards

  • Applicable project standards for industrial data exchange, interface security and cybersecurity; the final edition is confirmed against project location, industry and project documents
  • Interfaces follow project-confirmed HTTP API, MQTT or data dictionary specifications

Acceptance and delivery boundaries

Suggested acceptance dimensions

  • Check interface documentation, fields, keys, time format, data scope and call frequency
  • Verify identity authentication, rejection of unauthorized access, key expiry and access logs
  • Complete normal, empty, abnormal value and over-limit request tests, checking responses and error codes
  • Simulate network interruption, interface timeout and version change, and verify retry, recovery and compatibility documentation

Limitations and exclusions

  • Providing an API does not mean the third-party system has completed business integration; fields and flows still need joint acceptance
  • Interface permissions cannot replace network isolation and endpoint security
  • Data ownership, usage scope and redistribution rights must be confirmed in the project agreement; the platform does not grant them automatically
  • Unauthorized personal information, customer data or sensitive engineering documents must not be transferred through a sharing interface

Operational value

  • Provides field data to the business systems that need it in a controlled way
  • Reduces duplicate development and manual import through unified interfaces and a data dictionary
  • Makes data access, failures and changes traceable

Selection guidance

  • Define shared fields on a least-necessary basis rather than exposing all history and internal data by default
  • Where real-time performance is not critical, prefer batch interfaces; assess messaging or streaming only for real-time monitoring
  • For customer private networks or strict data residency, evaluate private deployment first
  • Interface quotas, concurrency and retention must be confirmed in the service or project configuration, not inferred from page defaults

Typical implementation patterns

  • Typical implementation pattern: an enterprise brings field device data into the platform through edge gateways, then provides agreed points and alarms to a customer energy or O&M system through a controlled API, with both parties using separate accounts and a test environment for joint commissioning. This is an anonymized typical pattern and does not represent specific customer platform or regulatory reporting results.

Before retrofit → With the solution

Before retrofit

  • Data must reach a customer or regulatory platform
  • Interface fields, keys and refresh periods differ, so transferred data cannot be used directly
  • Sharing scope, authentication, logging and data responsibility lack clear boundaries

With the solution

  • Provides field data to the business systems that need it in a controlled way
  • Reduces duplicate development and manual import through unified interfaces and a data dictionary
  • Makes data access, failures and changes traceable

How to evaluate the effect

01

Measurable signal

Field instruments, devices and gateways form a traceable data source and point model

02

Data source

CW Edge Computing Gateway · FEXLINK IoT Platform

03

Review method

Check interface documentation, fields, keys, time format, data scope and call frequency

04

Acceptance boundary

Providing an API does not mean the third-party system has completed business integration; fields and flows still need joint acceptance

Frequently asked questions

Can all points be opened to third parties?

Not recommended. Open fields on a least-necessary basis for the business purpose and configure data scope by caller identity.

How should API and MQTT be chosen?

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.

How are interfaces authenticated?

Use project-supported tokens, certificates or another identity mechanism, with separate accounts, permissions, key rotation and revocation.

How is data backfilled after an interruption?

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.

Can a regulatory interface be reused directly?

Obtain the regulator's formal interface specification, test environment and field requirements first; general API experience is not sufficient to establish compatibility.

Request a matched product combination and project review

Share the application, circuit conditions and existing system interfaces so engineers can confirm selection and implementation boundaries.

Contact FEXLINK