T

Io - Industrial
Bachelor International – B3

B3 – EEE/MIA – EXP2b
Nicolas Ferry
 Contents
1. Introduction
1.1 The 4th Industrial Revolution
1.2 IIoT Applications Sectors
1.3 Factory SI Organization

2. Factory SI – Pyramidal View

2.1 Factory View
2.2 Entreprise: Extended Enterprise, ERP
2.3 Management: MES
2.4 Supervision: SCADA, HMI, Dashboards, KPI
2.5 Production Line: Product Line, AGV, Cobots, PLM, smart-Tools (IIoT)

3. OPC-UA
3.1 Norm, Context-Problem, Architecture
3.2 Features
3.3 Inner OPC UA - Modeling
3.4 Inner OPC UA - Security
3.5 Inner OPC UA - Roadmap
Introduction - The 4th Industrial Revolution

3
1.2 Introduction - IoT Sectors
Transport
Smart Cities / Smart Buildings
Electric / Autonomous Vehicle,
- Energy management, public lighting,
Passenger flow, route optimization
Parking lots, traffic flow
- Supervision (Energy, HVAC, Security, ...) Stakes: Batteries, AI-Decision-making
CyberDefense, Security, Alarms
⮚ Stakes: Urban infrastructure E-Health
- Human-based systems: ECG,
Monitoring, health monitoring
⮚ Stakes: Personal / Medical Data
IoT Follow-up assistance: HAD/MAD
Industry 4.0 - IIoT
Improved productivity, operator comfort, Home Automation
Predictive maintenance, alert automation Electricity consumption
⮚ Stakes: management, Comfort (heating,
- Data recovery and aggregation shutters), Security (alarms), Health
- Communication network between the entities, ⮚ Stakes: Active or aging people.
- Logistics, Predictive Maintenance, Automated Stocks
- Supervision and Decision Support 4
1.3 Introduction – Factory View
ERP: Enterprise Management.
Production, Stock, Sales, Purchases, HR,
Business
MES: Management Process Supervision,
Management of personal, resources,
performance, documents, maintenance, prod.
Scheduling

SCADA: Operational Supervision.

HMI, Decicated HMI, or PC Supervision.

Control: Control/Communicate the process.

Automatons, PLC, PACS, Industrial PC, Cam
Video Process…

Sensors: Direct Equipments.

Machines, sensors, actuators, supply chain,
motors…
5
1.3 Introduction – IoT Industrial
Industry 4.0 = Digital Factory

Digital Factory

Digital Twin (VR/AR) - Realtime Data View

3. Open Platform Communications (OPC)

7
3. Open Platform Communications (OPC)
OPC International Norm: IEC-62541
- Open Standard for Industry communications.
- Standard: Architecture for OT (operational) and IT (Informatics) convergence.
- M2M Communications, client – serveur mode, publiser/subscriber mode.
- Interoperable: Compatible with almost all factory equipment vendors.
- Heteroclite: Supported various systems: Windows, Linux, VxWorks, Android…
- Scalable: to embedded systems (LAN) to system on the Cloud (WAN/Internet)
- Security with Access control, Authentification, Ciphering, Signing.
- Flexibility and adopted by industries: Automobile, Alimentation, Petrol, Energy,
building…

=> Open Standard for the Industry 4.0

OPC Organization (US) – R&D Center - 150 Members (Scheinder, ABB, Festo….)
- Writing the specifications, and managing evolution, realizing tests certification.
- Collaboration with other organisms.
- Promoting the OPC Technologies

8
3. Open Platform Communications (OPC)
Main Sectors:
- Industrial Automation
- Building Automation
- Embedded Devices
- Energy Management (Smart Grid)
- Manufacturing Enterprise Management
- Machine to Machine (M2M)
- Cloud based computing

> Link to OPC deployement guide (VDMA): VDMA OPC Guidelines for enterprise

9
3. Open Platform Communications (OPC)
Global Normalization for Industry 4.0 Revolution:
Industry 4.0 (GB), Industrie du Futur (FR), Industry 2025 (CH), Industrial IoT (US), others
similar to Alliance Industrie du Futur…

⮚ OPC-UA is mandatory for Industrie 4.0 (RAMI4.0)

Information +
Communication
layers

⮚ In France, OPC-UA will also be a key for the ‘‘Industrie du futur’’ reference model.
10
3. Open Platform Communications (OPC)
Problem of heterogeneity:
- Multiple different bus fields
- Heterogeneity in SI
- Maintenance cost
- Low Evolutivity
- No Standard
- Lack of confidentiality

Features:
- Interoperable
- Sustainable Systems
- Reduced costs
- Scalable
- Secure

11
3. Open Platform Communications (OPC)
OPC-UA Factory Network Architecture:

12
3. Open Platform Communications (OPC)

OPC Classic (1995-2010) OPC-UA: Unified Architecture (+2010)

- DCOM objects - Open Norm (open source license)
- Compatible Windows only - Interoperability (Linux, Windows, PLC…)
- Lower Security - Compatibility (widely adopted by indus.)
- No configurable Timeouts - Scalability (sensors to mainframes)
- Frequent DCOM config. issues - Security (signing, crypting, authentification)
- SOA – Architecture (Web Services)
- Remote Procedure Call / Event / Alarm
- Evolutivity (C++, .Net, Java, Python…)
- Models : Client/server or Pub/Sub Model 13
3. Open Platform Communications (OPC)
Inner OPC-UA Technology:
- Based on Oriented-Objects Prog.
- (Web-)Services Interfaces
- Features Discovery
- DA (Data Access)
- HDA (Historical Data)
- EA (Event / Alarms)
- Proc (Remote Procedure Call)

Two communication models:

- Client / Server Model (1)
- Publish / Subscribe Model
(2)

=> OPC represents real-life objects of the system by using Oriented-Objects modeling. 14
3. Open Platform Communications (OPC)
Address Space
View View View
(1) Object Model – (Objects Application) Client exposed
Objects Application

(2) Information Model Server embedded

(3) OPC Meta-Model

Inner OPC-UA Technology – Application Modeling:

- OPC UA Server exposes information througth an Address Space.
- Address Space is composed of severals objects.
- Objects are instances of Nodes interconnected by references.
- Each Node owns specific Attributes (ie: NodeID, NodeClass, BrowseName...)
- Address Space can be partitioned into Views which are collections of Nodes.
- Access can be granted to a View restricting visible Address Space to Client.
15
3. Open Platform Communications (OPC)
(1) Address Space - Object Model (Objects Application):
- The Objects are instance of Nodes defines into the Information Model.
- Read/Write operation can be performed and a Data change mechanism avoids polling.
- Methods can be invoked by Remote Procedure Call from an OPC Client.
- Objects can send Event Notifications when an alarm fired.
- Each Object are linked by references to others objets.

Object
Data Change
Notification Variables
- References to
Read/Write - others Objects

Invoke Methods
-()
Event -()
Notifications
16
3. Open Platform Communications (OPC)
(1) Address Space – Object Model:
The AddressSpace is a set of Objects that the OPC UA server makes available to clients.
Address
Space Object
Object
Variables
- Variables
- -
-
Object Methods
-() Methods
Variables
-() -()
-
-()
-

Methods
Object
-() Object
-() Variables
Variables
-
-
-
-

Methods
Methods
-()
-()
OPC Serveur Address Space
-() (PLC S7-1500) exposed to Client
-()
Fully-Meshed 17
network
3. Open Platform Communications (OPC)
(2) Information Model:
Objects are represented in the AddressSpace by a set of Nodes.
Address Space
Object
Object Variables
Object Object
Variables
Methods
Variables Variables
Methods
Methods Methods

Information Model Node Node

Attributes Attributes

Node
References References
Attributes

Node Node
References
Attributes Attributes

References References

18
3. Open Platform Communications (OPC)
(2) Information Model – Nodes:
Objects are instances of Nodes described by Attributes and interconnected by References.

A Node is the basic unit of information organization

- Nodes have attributes to describe the node (NodeId, BrowseName, DisplayName, NodeClass…)
- Nodes can be connected by References to form a fully-meshed network.

Node Attribute describe a Node

References defines relationships to other Nodes

Attributes

Node
References
Attributes

References

19
3. Open Platform Communications (OPC)
(2) Information Model - Nodes - Attributes:
Attributes are data elements that describe Nodes.

The mandatory Attributes of each Node class are:

- NodeId: Uniquely identifies the node whitin the address space of the
server. NodeIdis a structure composed of the index of the
namespace, the type identifier (numeric or string), and the identifier
(numerical value or string).
- NodeClass: Enumeration that identifies the NodeClass of a Node
(object, variable, method…)
- BrowseName: Used as a non-localized human-readable name when
browsing the AddressSpace to create paths out of BrowseNames.
(BrowseName are not unique like NodeId)
(1) Address Space - Exemple Properties
- DisplayName: Used as localized human-readable name to display the of a NodeClass Variable
name to the user.

20
3. Open Platform Communications (OPC)
Namespaces:
- Namespaces are used to ensure unicity of identifers that are issued by different organizations
(OPC Fundation, PLCopen, automation vendors…).
- A Namespace URI (Uniform Resource Identifier) that identifies the naming authority responsible
for assigning the identifier element of the NodeId.
- The list of all the Namespaces available in an OPC UA Server is available via the Node
NamespaceArray
- Index 0 of the NamespaceArray is reserved to OPC Fundation.

NamespaceArray in OPC Server

Examples of Namespace URI

21
3. Open Platform Communications (OPC)
(2) Information Model – Notation - NodeClass:

22
3. Open Platform Communications (OPC)
(2) Information Model – Example:

23
3. Open Platform Communications (OPC)
(2) Information Model – Built-in:
Base Information Model:
It defines necessary base object types, reference types,
variable nodes… defined in OPC UA Address Space.

Standard series specifications:

These specifications are part of the overall OPC UA standard series and defines the
information model associated with different access type:
- Data Access (DA) is defined in part 8
- Events & Alarms (EA) is defined in part 9
- Programs is defined in part 10
- Historical Access (HDA) is defined in part 11

24
3. Open Platform Communications (OPC)
(2) Information Model – Companion:
- Companion Specifications defines common profiles:
Robotics, CNC Machines, PackML, PLC…
- Specific Informations models of other organizations
are mapped onto OPC-UA and thus, become
portable.

Collaborations for Model Profiles standardization :

OPC market collaboration:

https://opcfoundation.org/markets-collaboration/
25
3. Open Platform Communications (OPC)
(2) Information Model – Vendor Specific:
- OPC Address Space can be extended by custom
Information Models.

Vendors ands users can create their own Information Model by:
- Using existing types of Objects and Variables or creating new ones, create Methods…
- Delivering UANodeSet file that contains all Nodes and References between nodes
inside this specific information model.

26
3. Open Platform Communications (OPC)
(3) OPC-UA Address Space Model (OPC Meta-Model):
- A meta-model typically defines the language and processes from which to form a model.
- The Address Space Model is the meta-model on which all OPC Information Models are
build-on. It’s an Object-Oriented Paradigm including type hierarchies and inheritance.

Key concepts:
- Object
- Variable
- Method
- View
- ObjectType
- VariableType
- DataType
- ReferenceType

27
3. Open Platform Communications (OPC)
Inner OPC Technology – Transport – Encoding Mode:
Binary protocol (UA Binary):
- Mandatory, Best performance,
smallest overhead.
- Minimum ressources
- Only one single port (4840)

WebServices (XML-SOAP)
- Optional, additional.
- Usable by tools (Java, .Net)
- Firewall friendly (http:80)

Hybrid (UA-Binary via https):

- Optional, less overhead than SOAP.
- Binary encoded in a https Frame
tcp.opc https http - Firewall friendly (https:443)
28
New Pub/Sub Mode: JSON, MQTT and AMQP native support.
3. Open Platform Communications (OPC)
Security is incorporated at all levels:
- Report on security audit leads by the BSI (GB): OPC-UA Security Analysis
- Deep inside security description: https://www.youtube.com/watch?v=pa82WydVtPY

- Levels of Security:

29
Based on established standard: AES, RSA, SHA, ECC
3. Open Platform Communications (OPC)
URI uniquely defines SecurePolicies:
# None (lowest security needs, startup tests, disable)
# Basic128RSA15 (deprecated)
# Basic256 (deprecated)
# Basic256Sha256 (high security needs)
# Aes128_Sha256_RsaOeap (average security needs)
# Aes256_Sha256_RsaPss (high security needs)
# PubSub-Aes128-CTR (average security needs)
# PubSub-Aes256-CTR (high security needs)

- OPC UA Servers identify which security policies they support.

- OPC UA Clients choose the security policy they want to use when connecting to server.

Notes: OPC Fundation deprecates weak Policies over time to maintain effective security.
30
3. Open Platform Communications (OPC)
OPC-UA Roadmap:
https://opcfoundation.org/about/opc-technologies/opc-ua/opcua-roadmap/

OPC-UA v1.04: 2019/2020: > 2021:

- Semantic levels - Deterministic communications - Transactions
- Interfaces and Addins Pub/Sub over TSN. - Metadata in the Cloud
- Pub/Sub - Field-level communications - Cloud-Relay
- JSON Web Token – OAuth2 - Companion standard - 5G - Deterministic
- Reverse Connectivity - Provisionning Services - Wifi 6, Wifi 7
- Sessionless Services - MQTT v5
- Security adds SHA-256, ECC - Semantic Validation
- Aliasname

31
Bibliography
Bibliography

This lecture is based on elements from:

• Exchanges with Wilfried Despagne and Jean-Jacques
LePape – Icam Vannes.
• Automate PLC – Siemens: Thierry Delaroche – Icam
Nantes
• English review: Ronan Denmat, Fernando Lopez
• From my own experience and my own projects.
Greetings

32