OPC UA. Enabling Industrie 4.0 Machines.

Transcription

1 Enabling Industrie 4.0 Machines

2 2 Enabling Industrie 4.0 Machines Content > Digitalization, Information, Communication > Key to success? > Requirements for Communication > RAMI 4.0 vs II RA > Client Server > Secured Middleware: Client/Server > Controller to Controller > SOA Orchestration > Sensor to Cloud > Publish/Subscribe > One to Many, Many to One > Time Sensitive Network > Summary

3 3 Enabling Industrie 4.0 Machines Interoperability > Digitalization > Communication > Information/Data > Semantic Interoperability > The common sense > Unification > Standardization 2016, ascolab GmbH

4 Enabling Industrie 4.0 Machines Requirements for Interoperability Standard > Independent: platform, vendor, language, operating system > Scalable: smallest sensors, embedded devices, controllers, PC, Cloud > Secure: encrypted, signed, authenticated > Information: modeled objects, type/instances, semantic > Function: data access, events, alarms, historic, methods, state machines 2016, ascolab GmbH

5 Enabling Industrie 4.0 Machines RAMI 4.0 vs. II RA > Industrie 4.0 Reference Arch. > Focus on industry/production > Automation, IT and Machinebuilders, Research > Complete value chain from order, production, live cycle, end user, recycling > Representation of all assets product and production, CPS > Data model, semantic, digital engineering, simulation > IIC Reference Architecture > Focus on Internet of Things > Mainly IT companies > Production and other branches > Cloud, BigData, Analytics > Representation of physical assets

6 Enabling Industrie 4.0 Machines Cloud Driven Approach > Central Storage, Analytics, Big Data > Multiple Protocols > RawData Driven (Edge) Cloud https No real Interoperability between devices!

7 Enabling Industrie 4.0 Machines - Interoperability > Std. Protocol > Std. Data Model > Std. Semantic (Edge) Cloud https Direct Interoperability (plug&play)!

8 Enabling Industrie 4.0 Machines Middleware > Secure Service Bus (Service Oriented Architecture) HMI SCADA MES ERP Cloud Analytics Engineering Diagnosis Middleware (Service Bus) Controller Machine Machine M 1 M Machine 2 Drives S S S S S S I/O Machine C 3 D D D

9 Enabling Industrie 4.0 Machines : Security analyzed by BSI Who: Federal Office for Information Security (German Government BSI) Why: Because of relevance of for German Industry What: Security Evaluation of OPC-UA finalized March Analysis of specification / Analysis of Reference Implementation Result: Available on BSI web and OPC web

10 Enabling Industrie 4.0 Machines Client Server > Active Client, passive Server HMI SCADA C MES Cloud Analytics Ident Diagnosis ERP C C C Middleware (Service Bus) S S C S Controller C M M C S S S Drives S S S I/O D D D

11 Enabling Industrie 4.0 Machines SOA Machine > Machine provides standard services > MES orchestrates production > LOT size one Invoke Service MES ERP UA Client UA Server M S S S

12 Enabling Industrie 4.0 Machines Example: SAP, Stäubli, Beckhoff, Asentics > LOT Size 1 > SAP Connected Manufacturing > Beckhoff TwinCat, XTS > Stäubli > Asentics > Honeywell >

13 Enabling Industrie 4.0 Machines SOA enabled by - Assets provide services (exposed as Server) - Assets can initiate actions (as Client) - DoJob(OrderNr) - Confirm JobDone(OrderNr) Data Center SAP Plant Connectivity Client Server Factory - Client / Server Communication done ONLY via method calls - (NO HANDSHAKE MECHANISM) Factory Server Client Server Client Server Server Transport System Robot Server Camera Camera Laser Printer

14 Enabling Industrie 4.0 Machines : PLC calls Services > PLCOpen Function Calls > PLC acts as Client > Call out of PLC into Cloud AMQP UA Client UA Server Cloud Gateway M S S S

15 Enabling Industrie 4.0 Machines Example: PLC to Cloud

16 Enabling Industrie 4.0 Machines Example: Azure IoT Support for

17 Enabling Industrie 4.0 Machines

18 Enabling Industrie 4.0 Machines Communication Concepts > Publish/Subscriber Communication Model > Generic Pub-Sub Information Model > Initial protocols selected, evaluation of other protocols ongoing Client/Server Services Protocols Vendor Specific Extensions Companion Information Models Built-in Information Models Meta Model Pub-Sub Model PubSubConfiguration Connections DataSets Protocols UA Secure Multicast AMQP, MQTT More to evaluate

19 Enabling Industrie 4.0 Machines SOA vs Pub/Sub > TCP based Request/Response > Connection/session context required (peer-to-peer) > High resource consumption when many connections (>500) > Private subscription for each client > Save transport, acknowledgement of every message > Late polling for DataChange, keep alive > Use Case: huge amount of flexible data > UDP based Pub/Sub > Connection-less, broadcast-style communication > Low resource consumption many subscribers (>1000) > Public subscription, same data for all clients > Fire and forget transportation > Cyclic publish of all data (could be deterministic) > Use Case: small amount of fixed data Both Needed!

20 Enabling Industrie 4.0 Machines Server and Publisher Client A Subscriber 1 Subscriber N Publish Message Oriented Middleware Server Client A Session Subscription DataSetWriter DataSet Publisher Address Space Application

21 Enabling Industrie 4.0 Machines Communication Extension (Pub/Sub) > Usecase driven: IoT > many-to-one (the cloud) communication > in global network (optionally use Relay/Broker) The Cloud Client (Subscriber) Sub AMQP (advanced message queuing protocol) prototyping Relay Broker (optional) Pub Server Pub OPC (Publisher) UA Server Pub OPC (Publisher) UA Server (Publisher)

22 Enabling Industrie 4.0 Machines Commnication Extension (Pub/Sub) > Usecase driven: M2M > Extremely fast one-to-many communication > in local network (maybe Time Sensitive Network (TSN)) Client (Subscriber) Sub Client (Subscriber) Sub Client (Subscriber) Sub prototyping UDP Secure Multicast Pub Server (Publisher)

23 Enabling Industrie 4.0 Machines Publish/Subscribe > Sub-Group of UA WG > Kick-off on June 8, 2015 > Over 70 WG members > Wireshark available > First demo finished

24 Enabling Industrie 4.0 Machines TSN Evaluation > Sub-Group of UA Working Group > Kick-off on June 8, 2015 > Over 80 WG members > TSN Evaluation > TSN is a standard real-time extension for Ethernet > Collection of use cases and requirements finished > Communication parameters and requirements already defined and integrated in PubSub definition > Configuration model discussion started

25 Enabling Industrie 4.0 Machines Pub/Sub Roadmap UA WG Use Cases collected UA WG UA WG First Draft Stable Draft Main definition phase UA WG Release Candidate UA WG PubSub Release UDP AMQP UA WG Stable TSN Draft PubSub Prototyping Prototyping Prototyping Prototyping Prototyping First sample applications available First multivendor demo at Hannover Fair Enhanced multivendor demo at SPS/IPC/Drives Complete PubSub implementations

26 Enabling Industrie 4.0 Machines Summary enables Industrie 4.0 Machines BECAUSE Data Modeling Generic object oriented modeling Objects with variables, methods and events Extensible type system History for data and events State machines, programs, alarms & condition Complex data Collaboration UA is IEC standard UA is base for other information models EDDL and FDT MIMOSA OMAC PLCopen Communication Integrated security mechanisms High speed UA TCP protocol Web services for internet Platform independent Built in robustness and fault tolerance Redundancy New Applications and use cases Profiles for different use cases Scalability Integration in embedded systems MES and ERP systems Specialized versions for different industries

27 27 Enabling Industrie 4.0 Machines Thanks for Your Attention! Uwe Steinkrauss Sales & Marketing Unified Automation GmbH O Brien Str. 2 D Schwabach Phone info@unifiedautomation.com