OPC UA Roadmap

 

The OPC UA road map highlights recent and future enhancements to the OPC UA standard. It provides a hint for next steps and the general vision.

In our road maps, you can learn about OPC UA innovations along three different timelines:

    1. Recent additions lists features that have been
      added to the latest version of the OPC UA standard
    2. Features in work lists hot topics that the OPC UA
      working group currently addresses and that are intended to be added as an
      addendum to the current version or to the next full version.
    3. Vision, provides a high-level and long-term
      perspective on innovations for the OPC UA Standard
Recent innovations in v1.04

2018/2019 – Features worked on

2020 and beyond – Vision

PubSub

§
New communication schema to enable and optimize OPC UA for
one-to-many, many-to-one, or many-to-many  configurations.

JSON Web Token, OAuth2

§
User identification using the authorization service
well-established in modern cloud applications (Azure, Google, Facebook, …)

Reverse Connectivity

§
Servers behind firewalls can use reverse connectivity.

SessionLess Services

§
Avoids session establishment for use cases where Servers are
called infrequently.

Security

§
New policies that use SHA256

Deterministic UA: Mappings to TSN

§
This project will add a transport mapping of OPC UA PubSub to
Time Sensitive Networking (TSN). Based on this mapping, deterministic data
exchange between UA applications is possible.

Cloud-Relay

§
The cloud-relay capability allows for connectivity between UA
applications even when both Client and Server are behind separate firewalls.

Topic-based PubSub

§
With topic we mean a named PubSub channel. By introducing
topics we advance the late-binding philosophy. The PubSub actors will simply be
configured with a topic name and will discover additionally required
attributes at runtime.

Relate with established semantic models

§
Although OPC UA provides extensive capabilities to create
information models it will often be beneficial to make use of existing models
like IEC CIM, eCl@ss, or IEC Common Data Dictionary. This project will define
means to relate Nodes in a UA AddressSpace with other models or dictionaries.

The following features are under consideration. No concrete
specification work has been initiated.

 

Transactions

§
With the increasing popularity of OPC UA in various industries,
we also see more and more scenarios where OPC UA is used for configuration.
Simple configuration tasks can be solved with Methods, for more complex
scenarios, transactions will be needed.

MetaData in the Cloud

§
When data are published to cloud applications, most of the meta
information that is in the Server’s AddressSpace is not part of these data.
The “MetaData in the Cloud” project targets this deficiency.

Harmonization of companion standards

§
Today, many organizations use OPC UA to model and expose their
existing information. More and more, however, the definitions overlap or are
identical. This project supports companion working groups to harmonize their
models.

Deterministic communication using 5G

§
The 5th generation wireless systems will provide
better performance and determinism. Similar to the TSN mapping a mapping of
PubSub to 5G protocols may be considered