180 likes | 238 Views
OPC UA and CIM. Presenter: Sebastian Rohjans. CIMbaT - Generating CIM-based Address Spaces. Team: Jean-Francois Cabadi Klaus Piech Sebastian Rohjans Mathias Uslar. OPC Unified Architecture. OPC Foundation.
E N D
OPC UA and CIM Presenter: Sebastian Rohjans CIMbaT - Generating CIM-based Address Spaces Team: Jean-Francois Cabadi Klaus Piech Sebastian Rohjans Mathias Uslar
OPC Unified Architecture OPC Foundation • Vision: „The OPC Foundation vision in 2010 - 2012 is focused on the principle of delivering the best specifications, technology, certification and process to truly achieve multivendor multiplatform secure reliable interoperability for moving data and information from embedded devices all the way through the enterprise in industrial automation. [...]” [www.opcfoundation.org] • Member: >400 (worldwide)
OPC Unified Architecture Classic OPC Overview OPC Specifications OPC Security OPC Common Definitions OPC Complex Data OPC Alarms and Event OPC Historical Data Access OPC Commands OPC Data Access OPC XML DA OPC Batch OPC Data eXchange
OPC Unified Architecture Distribution of Classic OPC • > 20.000 products • Several thousand vendors • A couple of million installations • OPC preferred way to exchange data resp. integrate processes for: • 78% production systems and MES-applications • 75% HMI-/SCADA-systems • 68% process control systems and PLC • 53% ERP-systems
OPC Unified Architecture Classic OPC and CIM Generic Data Access (GDA) -403 High Speed Data Access (HSDA) - 404 Generic Eventing and Subscription (GES) -405 Time Series Data Access (TSDA) - 407 GID IEC 61970- CORBA (OMG) Data Access Facility (DAF) Data Access From Industrial Systems (DAIS) Historical Data Access From Industrial Systems (HDAIS) Unified Architecture Query (UA) OPC Alarms and Events (OPC A&E and A&E XML) OPC Data Access (OPC DA and DA XML) OPC Historical Data Access (OPC HDA and HDA XML) OPC
OPC Unified Architecture Where is OPC UA? Overview OPC Specifications OPC Unified Architecture OPC Security OPC Common Definitions OPC Complex Data OPC Alarms and Event OPC Historical Data Access OPC Commands OPC Data Access OPC XML DA OPC Batch OPC Data eXchange
OPC Unified Architecture Reasons for developing OPC UA • .NET is introduced onto the market as successor of COM/DCOM • Boundaries of DCOM • OPC-communications beyond firewalls • Platform-independent application of OPC • High-performance OPC-communication via Web Services • Unified data model • Support of complex data structures • Process data communication without loss of data • Better protection from unauthorized data access • Support of method calls
OPC Unified Architecture Overview Core Specification Access Type Specification VendorSpecificSpecifications Core Specification Access Type Specification Part 1 – Overview & Concepts Part 8 – Data Access Part 1 – Overview & Concepts Domain Specific Information Model Part 8 – Data Access Part 2 – Security Model Part 9 – Alarms & Conditions Part 2 – Security Model Part 9 – Alarms & Conditions DA AC HA Prog Part 3 – Address Space Model Part 10 – Programs Part 3 – Address Space Model Part 10 – Programs Part 4 – Services Part 11 – Historical Access Part 4 – Services Part 11 – Historical Access OPC UA Base Services Part 5 – Information Model Part 5 – Information Model Utility Specification Utility Specification Part 6 – Service Mappings Part 6 – Service Mappings Part 12 – Discovery Part 12 – Discovery Part 7 – Profiles Communication Web Service / OPC UA Binary OPC UA Data Model Modeling Rules Part 7 – Profiles Part 13 – Aggregates Part 13 – Aggregates
OPC Unified Architecture Application MES/ERP Server MES/ERP System OPC UA Server OPC UA Client SCADA OPC UA SCADA SCADA OPC UA Client OPC UA Server Controller OPC UA Server OPC UA Client OPC UA Server
OPC Unified Architecture Summary • Goals: • Improvement of Classic OPC standards to meet new requirements • Provide a platform-independent server-client-architecture based on an object-oriented and abstract data model to address new applications • Technical Implementation: • Abstract data and information model • Technology mappings • Object-oriented approach • Large set of services • Different client and server profiles for different requirements • Detailed security concept
OPC Unified Architecture OPC UA and CIM VendorSpecificSpecifications VendorSpecificSpecifications Domain Specific Information Model Common Information Model DA DA AC AC HA HA Prog Prog OPC UA Base Services OPC UA Base Services Communication Web Service / OPC UA Binary Communication Web Service / OPC UA Binary OPC UA Data Model Modeling Rules OPC UA Data Model Modeling Rules
OPC Unified Architecture OPC UA and CIM • Important requirements: • Applicable to extended CIM models (because in many cases deployed models include numerous enterprise-specific objects) • Platform-specific model (PSM) as basis: • All CIM-information will be preserved • Stereotypes are used to annotate UA-specific information • Design decisions can be stored and loaded • Handle new versions by difference models • Tool-Support: • Add-In for Sparx Enterprise Architect (the tool which is used to maintain the CIM)
OPC Unified Architecture OPC UA and CIM • Design descisions: • Abstract types • Direction of associations • Choice between Property and DataVariable • Data types • Access rights • Historical access • Root of the default views • Views • Mapping:
OPC Unified Architecture Harmonization of Smart Grid Data Models • Mapping CIM to OPC UA • Mapping IEC 61850 to OPC UA • Mapping general UML models to OPC UA?
OPC Unified Architecture Video
Thank You for Your Attention Questions? Contacts Dipl.-Inform. Sebastian Rohjans E-Mail: rohjans@offis.de Phone: +49 4419722-422 OFFIS Energy Escherweg 2 26121 Oldenburg Germany