An open CPS architecture can help manufacturers make better use of data from equipment that was not designed to operate as one connected system. In a factory, machines may come from different vendors, use different communication protocols and span multiple generations. Connecting them to a shared platform is not just a networking task: it also requires consistent interfaces, useful applications and clear rules for participation.
Cyber physical systems (CPS) link physical equipment with software that analyzes data and can inform actions in the physical environment. In factory automation, this creates a feedback loop between production assets and digital tools. The approaches taken by FANUC FIELD and Mitsubishi Electric EDGECROSS illustrate two ways of organizing such an industrial IoT platform.
What an open CPS architecture means for manufacturing
A manufacturer can build a closed CPS around its own products: sensors collect information, software analyzes it, and results are returned to those products. A factory-wide system has a different challenge. It may need to work across machine tools, robots, programmable logic controllers (PLCs) and other equipment made by multiple suppliers.
An open CPS aims to collect and use data from this broader mix of assets. âOpenâ does not mean that every device or application connects without conditions. Equipment still needs compatible interfaces, and platform operators must decide how applications are reviewed, accessed and supported.
The proposed architecture separates the system into three layers:
- Physical domain: The machines, robots, controllers and other assets operating at the production site.
- IoT platform: A middle layer that receives, stores and organizes data in a common format.
- Cyber domain: Applications and software that analyze data or provide services to users.
Interfaces link the platform to the two domains. A Physical API defines how equipment data and functions can be accessed. Because factory assets may use different protocols and formats, converter software can be needed to make their data compatible with the platformâs interface. A Cyber API provides application developers with structured access to platform data and services.
Why APIs and edge processing matter
APIs turn a complex integration problem into a set of defined interactions. Rather than letting every application connect to every machine in a different way, a platform can establish rules for data access and exchange. These rules can make it easier for third-party developers to build applications that work within the platform, while keeping access mediated by its interfaces.
Where data is processed is another important design choice. In an edge-heavy approach, processing takes place near the production site rather than relying entirely on the cloud. This can support quicker responses and reduce the need to send all data beyond the site. The source describes both FIELD and EDGECROSS as using edge processing, with real-time data analysis and feedback handled close to production equipment.
For operations teams, this architecture shifts attention from connectivity alone to the complete data path: how equipment is connected, converted, analyzed and acted upon. A platformâs value depends on whether its interfaces can accommodate the assets in use and whether available applications address site-level needs.
FANUC FIELD and Mitsubishi EDGECROSS compared
FANUCâs FIELD system is an open, edge-heavy platform designed to share machine data across FANUC equipment and products from other brands. It uses converter interfaces to integrate different equipment and provides APIs for applications. Third-party applications and converters are reviewed by FANUC before being offered through the FIELD system store.
Mitsubishi Electricâs EDGECROSS also connects production equipment to an edge-processing layer. Data is collected from the production site, analyzed at the edge, and either processed there or sent onward to the cloud. Applications for functions such as process simulation, data analysis, system monitoring and energy monitoring are available through its marketplace.
The two platforms differ not only in technical implementation but also in how they are governed. FIELD is operated under FANUCâs leadership, and the company reviews applications before they can be sold through its store. EDGECROSS is managed through a consortium, and partner companies can open stores more freely. These models reflect different balances between centralized control and a more distributed platform structure.
Applications developed for one system are not automatically compatible with the other. API design, data formats and interaction rules differ, just as applications built for distinct mobile platforms may not work across both. For system integrators and plant teams, platform selection therefore has implications for application choices and future integration workânot simply the initial connection of equipment.
Platform governance affects the factory ecosystem
A CPS platform connects more than machines and software. It brings together equipment suppliers, platform operators, application developers and industrial users. Governance establishes who can participate, what they can access and what standards they must meet. It can also shape application quality and the trust that participants place in the platform.
There is no single governance model in the examples. A more centralized review process can give the platform owner greater control over which applications reach users. A consortium approach can distribute oversight among participating organizations. Each choice affects how a platform balances openness, control and responsibility for applications.
Network effects also matter. More compatible equipment can make a platform attractive to application developers; useful applications, in turn, can give equipment suppliers and users a reason to participate. But growth is not only a matter of adding participants. The quality of equipment integration and software matters, as does the ability to maintain reliable rules for access and interaction.
Practical considerations for automation decision-makers
When evaluating an industrial IoT platform, technical and organizational questions should be considered together:
- Asset compatibility: Identify the equipment, protocols and data formats that need to be integrated, including older or mixed-vendor assets.
- Interface strategy: Understand how Physical APIs, converters and Cyber APIs mediate connections between equipment, the platform and applications.
- Processing location: Determine which data needs edge analysis and feedback, and which information may be sent to the cloud.
- Application governance: Review how applications are developed, assessed, distributed and maintained.
- Ecosystem fit: Consider how platform ownership and participation rules align with the suppliers, integrators and developers needed at the site.
Conclusion: treat CPS as a socio-technical system
Open CPS architecture offers a way to coordinate heterogeneous factory equipment, shared data and software applications through a layered platform. The comparison of FIELD and EDGECROSS shows that edge processing and APIs are only part of the design. Application review, platform ownership and participation rules also shape how the ecosystem develops.
For industrial automation teams, the practical implication is to assess the whole systemânot just device connectivity. A suitable platform must fit the siteâs equipment and data needs while providing workable interfaces and governance. The technical architecture and the organization around it together determine how effectively a CPS can support factory operations.
Access Official Technical PDF