OEC COMPLIANCE
What DEFINES
OEC COMPLIANCE
Conform to the “Architectural Guardrails“ of the OI4 based on existing industry standards:
- able to host OI4 compatible application container
- OI4 compatible and security enabled data bus for data exchange based on the industry standard MQTT.
- Supports data exchange between applications based on proven industry standards such as MQTT and OPC Pub/Sub
- Compatible to host the OEC Registry App as central infrastructure App for registering and finding user apps.
- The OI4 OEC Registry App is available for free as Open Source in addition with Open Source examples for user apps.
Supporting documents
OEC COMPLIANT
PRODUCTS
| PRODUCT NAME | Type | COMPANY | APPROVED ON | LINK |
|---|---|---|---|---|
| netFIELD OnPremise | Edge Device | Hilscher Gesellschaft für Systemautomation mbH | February 7th, 2025 | See here |
| netFIELD PROFINET Device | App | Hilscher Gesellschaft für Systemautomation mbH | February 7th, 2025 | See here |
| SIMATIC IPC Industrial Edge Device | Edge Device | Siemens | April 10th, 2025 | See here |
What’s in
for a user?
Development Guideline
The OI4 OEC Development Guideline enables interoperability and open data exchange between edge applications
Semantic
Semantics is one of the keys for Industry 4.0. The OI4 OEC message format based on OPC Pub/Sub provides the basis for interoperable data exchange between applications.
Essential Concepts
Provides essential concepts for modelling and identifying devices and applications (e.g. OI4Identifier)
Standardized Information
Provides standardized information of assets based on proven industry standards e.g. VendorNameplate model of OPC (OEC Master Assed Model)