OPC UA: machine data with names, units and access rights
A measurement without context says little. GCG exposes machine data through OPC UA so PLCs, SCADA, historical data storage and IT systems can exchange values and understand their meaning. Access control and security are part of the design from the start.
- What it is
- A platform-independent communication protocol (IEC 62541) for industrial data exchange, successor to classic OPC (DA/HDA).
- Information modeling
- Data is described with meaning: names, units and structure.
- Configure security
- OPC UA provides certificates, message signing and encryption. These mechanisms need appropriate configuration and management. They do not automatically secure an installation.
- Platform-independent
- Connections across PLC brands and IT systems are possible when supported profiles, information models and security settings align.
What GCG works through
Define meaning
Which machine, measurement, unit and status are shared? We define the data contract so consumers use consistent information.
Limit access
Reading, writing and operating are different permissions. We restrict application access and define who manages certificates and trust lists.
Verify behavior
We test data quality, load, connection loss and certificate renewal. Configuration and test results are part of the handover.
Information model and communication services
OPC UA combines an information model with communication services. Beyond reading and writing, it can support subscriptions, events and methods. Companion Specifications define shared models for specific applications. Support varies by product and profile.
Frequently asked questions
Does OPC UA replace MQTT?
Does every application need write access?
Is OPC UA certification the same as CRA conformity?
Related expertise
Cyber Resilience Act
OPC UA supports security. CRA requires more.
For products within CRA scope, obligations extend beyond the chosen protocol: secure design, vulnerability handling and maintenance throughout the product lifecycle matter. Using OPC UA does not automatically make a product CRA-compliant.
We connect interface decisions to the technical documentation: access permissions, certificate management, secure settings, updates and verification. Applicability and the conformity route must be established for the specific product and the roles of the parties involved.
Our approach to CRA & industrial cybersecurityCRA: European Commission (opens in a new tab)
What needs to change in your installation?
Tell us what is already installed and what you are running into.