OPC Foundation History and Standards

Peter Seeberg
Business Development Manager,
Industrial Data Intelligence
Softing

4
Object Linking & Embedding for Process Control
1995

Release version 1.0 OPC (Classic) specification for Data Access (DA)
1996
https://opcfoundation.org/about/opc-foundation/history/

(Classic) OPC Alarms & Events (OPC AE) specification is released.
1999

(Classic) OPC Historical Data Access (OPC HDA), Batch and Security specification are released.
2001

OPC UA version 1.0 specification is released.
2006

Specific Models
Use case specific models
Industry specific models
Device / machine specific
models
Developed with
partner organizations
OPC UA – IEC 62541
OPC Foundation develops and maintains generic, neutral communication architecture with
 Information Model Framework

Specific Models
models
Developed with
 Communication Model

Specific Models
models
Developed with
 Communication Model
 Protocols

Specific Models
models
Developed with

IT Network
HMIs
Machine
Control
Field
Level
Client Server
OPC UA
Client
OPC UA
Server
OPC UA
Client
Sub
PubSub
Pub
Clouds
SCADA, MES, ERP,
OPC UA
Client
OPC UA
Server
OPC UA:
Technology and OS
independent
OPC
Client
OPC
Server
PLC
OPC Classic:
OLE for Process Control
proprietary
Edge/Cloud
Pub/Sub
Controller to Controller
Pub/SubPub/Sub
Today
Client
Pub Sub
Client
Pub Sub
Server
PubSub
“SOA PLC”
OPC UA
Client
OPC
Server
OPC UA
- over TSN
- over 5G
Industrial mobile apps
Field devices

 Trusted Information (CIA triad)
◦ Confidentiality
◦ Integrity
◦ Availability
 Access Control (AAA principle)
◦ Authentication
◦ Authorization
◦ Accounting (Auditability)
Information
Security
Availability

 Confidentiality
 Protect the privacy of data
Changed Value: Variable Y
Value 0
OPC UA
Information
and
Functionality
Prevented by
message
encryption
on the Transport
Layer

 Integrity
 Protect from data changes
OPC UA
Information
and
Functionality
Write: Variable X Value 1
Changed Value: Variable Y Value 0
Value = 0
Value =1
Prevented by
message
signatures
on the
Transport Layer

 Availability
 Protect the availability of the service at all times
Protected by
server design
(restricting the
message size
and returning no
security related
codes)
UA ServerUA Client

 Authentication
 Protect access from external users and applications
Application
Instance
Certificates
OPC UA
Information and
Functionality (e.g.
read, write)




Authentication by username and
password or X.509 certificate
on the application layer
Authenticate User
(e.g. username and password)

 Authorization
 Protect access from unauthorized persons and applications
OPC UA
Information and
Functionality (e.g.
read, write)
Authorize for specific
operations and information
(e.g. writing a specific value)








Authorization to read, write values of a node
or to browse the information model based
on the access rights of the information model,
access rights of the user or of the user’s role

 Auditability
Track important interactions
Write
Variable
change from
1 to 2 by Karl
Audit
Log
Write
Variable
change from
1 to 2 by Karl
Write
Variable
change from
1 to 2 by Karl
Tracks all important updates,
including who did it
UA Traffic
Accountability, by generating audit
events for security related operations

Who: Federal Office for Information Security (German Government BSI)
Why: Because of relevance of OPC UA for German Industry
What: Security Evaluation of OPC-UA – finalized March 2016
- Analysis of specification
- Analysis of Reference Implementation
 The specification analysis has revealed no systematic errors, and has thus
shown that OPC UA, in contrast to many other industrial protocols, provides a
high level of security.
 Commented version available (English + German)
 www.opcfoundation.org/security

BISM, 20.04.2018
OPC UA – Model A OPC UA – Model B OPC UA – Model C
OPC UA – Model A
OPC UA – Model B
OPC UA – Model C

BISM, 20.04.2018
OPC UA – Model XOPC UA – Model X OPC UA – Model X
OPC UA – Model X OPC UA – Model X OPC UA – Model X

BISM, 20.04.2018

BISM, 20.04.2018
37
Verticals
Automation
Engineering
Communication
Enterprise

BISM, 20.04.2018
OPC Unified Architecture
for
AutoID
Companion Specification

BISM, 20.04.2018
Working group started
AIM Germany + OPC Foundation

BISM, 20.04.2018
First release candidate available

BISM, 20.04.2018
First release candidate available
Now available: first official version of the
companion specification for AutoID devices
Please contact us, if you are interested: info@aim-d.de

BISM, 20.04.2018
One communication standard for the whole
AutoID world
 device independent
 technique independent
 manufacturer independent
 compatible to special manufacturer features

BISM, 20.04.2018
One communication standard
for the whole AutoID world
 RFID
 OCR
 Optical (1D/2D barcode)
 RTLS

BISM, 20.04.2018
Olaf Wilmsmeier
Business Development Manager RFID
Board Member of AIM Germany
E-Mail: olaf.wilmsmeier@harting.com
Phone: +49 5772 479359
WWW: www.HARTING-RFID.com

BISM, 20.04.2018
Platform Independent
Protocol Independent
Open Source
Extendible Information Model
Validation, Authentication and Encryption Built In
> 600 Members
Deployed > 50 Million Machines

+ +
= Cross Platform
Contributed by Microsoft
Most popular official OPC Foundation stack
.NET Standard OPC UA Stack
+
Commercial Partner:
Windows 10Azure

Presentation & Business Connections
Websites, Mobile Services
Dynamics, Notification Hubs
Azure Edge Analytics,
Azure ML on Edge,
Azure Functions,
Azure Edge Runtime
Azure ML on Edge,
Azure Functions,
Azure Edge Runtime
AzureIndustrial IoTCloudPlatform
Azure IoT Edge
On-Premises: Machine Interoperability Azure Cloud: Data Ingestion & Processing, Command & Control Azure Cloud: Presentation
IndustrialDevices
(OPCUAServers)
Hot Path Analytics:
Azure Stream Analytics, Azure Time Series Insights…
Azure IoT Hub
OEE, KPIs calculation
Alarms & Events
Telemetry based on OPC UA PubSub Information Model
Cloud-based Device Management
OPC Clients & Servers using OPC UA .NET Standard stack
OPC Publisher Module
OPC Proxy Module
UA Client/Server
(UA Binary over MQTT)
Firewall
Cold Path Analytics, ML, Functions & Storage:
Azure Machine Learning, Azure Data Lake, Azure CosmosDB Graph…
UA Client/Server
(UA Binary)
UA Pub/Sub
(JSON over AMQP/MQTT)
Azure ML on Edge,
Azure Functions,
Azure Edge Runtime
Micro-Services: OPC Twin, GDS Vault
OPC Twin Module
UA Client/Server
(UA Binary)
IoT Edge Methods/Properties
UA Client/Server
(UA Binary)
https://www.youtube.com/watch?v=QJ1DWTvGQxo

Azure IoT Connected Factory Architecture

Azure Industrial IoT Edge Gateway Partners

Thomas Burke
President
Veronika
Schmid-Lutz
Russ AgrusaMathias Damm Thomas HahnStefan HoppeZiad Kaakani Matt Vasey Shinji Oda
623 Members
(09-11-18)

IIC
Industrie 4.0
Japan IVI
Korea MII3.0Made in China 2025

 Faster configuration and start-up with fewer
support calls
 Proven reliability and interoperability
 Minimal integration risks and an investment in
quality that your production system can rely on

Compliance Interoperability
Robustness Resources
Product
+ more…

 Buy an Off-the-Shelf OPC UA Product
◦ Standalone
◦ Embedded
 Build your own OPC UA application
◦ Use an SDK

Your Code
Commercial / Open
Source
Commercial Samples Experience Support

Face-to-Face
• 3 Times a Year
• NA, Europe, Asia

BISM, 20.04.2018
Ja, dazu müssen Sie KEIN Mitglied der OPC Foundation werden!
https://opcfoundation.org/
- Klicken Sie auf „Become a member“  dann „Free Account“

BISM, 20.04.2018
Looking for more information?
https://opcfoundation.org/
Peter Seeberg
Business Development Manager,
Industrial Data Intelligence
Softing
peter.seeberg@softing.com
0151 -1749 8159

OPC Foundation History and Standards

Recommended

Recommended

More Related Content

Similar to OPC Foundation History and Standards

Similar to OPC Foundation History and Standards (20)

More from Peter Seeberg

More from Peter Seeberg (17)

Recently uploaded

Recently uploaded (20)

OPC Foundation History and Standards