Upload
phungdung
View
220
Download
0
Embed Size (px)
Citation preview
© ABB Group July 25, 2011 | Slide 1
Informationsmodellierung in AutomatisierungsmiddlewareAm Beispiel OPC UA und IEC 61850
Wolfgang Mahnke, Industrial Software Systems, ABB Forschungszentrum Ladenburg
Overview
Middleware in Automation
Why Information Modeling?
Standardized Middleware in Automation• Overview OPC Unified Architecture• Overview IEC 61850
Comparison of Modeling Concepts
Conclusion
© ABB Group July 25, 2011 | Slide 2
© ABB Group July 25, 2011 | Slide 3
Middleware in Automation A Simplified View
ERP (Enterprise Resource Planning)
MES (Manufacturing Execution System)
SCADA (Supervisory Control and Data Acquisition)
DCS (Distributed Control System)
PLC (Programmable Logical Controller)
DE: SPS (Speicherprogrammierbare Steuerung)
Devices: Actors and Sensors
Middleware
Different Level of Interoperability
Overview Information Modeling
Why Information Modeling?
• Not communicating Data but exchanging Information• Bringing Semantic into the Data• Provides Meta Data to the Data
• Engineering Unit for Measurement• Information on Measuring Device• Represent Control Logic like Function Blocks• Represent Domain Model like Breaker
Communication• Communicating Data• Common Syntax of Data
Information Model• Vendor-specific Information
Model• Semantic Provided• Common Meta Model
Standardized Information Model• Common Semantic• Common Understanding• Common Interaction
Sequences
Standardized Information Models in AutomationExamples
© ABB Group July 25, 2011 | Slide 5
ISA-88(Batch Control)
ISA-95(integration of control
system with enterprise system, MES)
CIM –IEC 61968+61970(power distribution and
transmission)
IEC 61131-3(Programming model for
control logic)
IEC 61850(substation automation)
Device Integration(EDDL, FDT, FDI)
CAEX – IEC 62424(Engineering)
ISO 15926(Lifecycle Information
Exchange)
ADI(Analyzer Devices)
© ABB Group July 25, 2011 | Slide 6
Application X ...
DCS ControllerPLC
Application Y
Problem of Classic OPC
DisplayApplication
TrendApplication
OPC OPC
DCS ControllerPLC
Solution -> Classic OPCData Access (DA)Historical Data Access (HDA)Alarms & Events (A&E)
OPC UA(First “real” release 2009)
DCOMretires
.NET New
communication architecture
Web Services
(SOA)
Better interoperability
to Non-Microsoft platforms
BetterIntegration(DA, HDA, AE)
Information Modeling New Features
Change StructuresHistorical Events
Programs
More Areas ofApplication
MES, ERP,Devices
Applied in Automation2500+ Companies 15000+ OPC Products
Overview OPC Unified ArchitectureBackground and Motivation
Base OPC UA Information Model [UA Part 5]
Overview OPC Unified ArchitectureStandard
© ABB Group July 25, 2011 | Slide 7
Overview: [UA Part 1] [UA Part 2]
Communication Infrastructure[UA Part 6]Web Services
UA TCP
OPC UA Services [UA Part 4]
Standard Information Models [UA Part 8,9,10,11][UA Devices], etc.
OPC UA Meta Model[UA Part 3]Object(Type)
Variable(Type)
etc.
Information Modeling with OPC UAStandardized Information Models
© ABB Group July 25, 2011 | Slide 8
In discussion
Base OPC UA Information Model(generic model, base types)
OPC UA for Devices(generic model how to represent devices)
OPC UA for Analyser Devices
(specific model for analyzer devices)
OPC UA for IEC 61131-3
(mapping of software model)
ISA-88(Batch Control)
MIMOSA(standard for plant
operations and maintenance)
ISA-95(integration of control
system with enterprise system, MES)
OMAC(integration of different
packaging line functions)
FDI(Field Device Integration)
In developmentReleased
Configuration
Configuration
Status
FactorySettings
AnalyserDeviceType
GetConfiguration
SetConfiguration
SpectrometerDeviceType
MethodSet
TwoStateDiscreteType (DataType: Boolean)
TrueState : PropertyType
FalseState : PropertyTypeOutOfSpecification
FunctionCheck
AnalyserStateMachine
<ChannelIdentifier>
Objects
TrueState
FalseState
TrueState
FalseState
Devices
Device1
Device2
Status
FactorySettings
GetConfiguration
SetConfiguration
MethodSet
OutOfSpecification
FunctionCheck
AnalyserStateMachine
<ChannelIdentifier>
TrueState
FalseState
TrueState
FalseState
Information Modeling with OPC UA
Objects are structuring the Address Space
ObjectTypes define Semantic and Sub-Structure of Objects
ReferenceTypesdefine Semantic of
References
Variables contains Data
Method defines Signature of a Method
Views as excerpts of
Address Space
DataTypes define simple or complex Data Structures
VariableTypes define Sub-Structure and Semantic of Variables
Overview IEC 61850Motivation
Initially developed for Substation AutomationAddresses
Engineering by SCL(Substation System Configuration Language)Communication
Very fast Communication inside the System(Level 2 Ethernet) – GOOSE and Sampled ValuesTCP/IP based Communication (MMS)
Information Modeling to provide SemanticFirst release 2004, strong adaption in Substation AutomationExtensions
IEC61400-25 Wind Turbines (based on IEC 61850)IEC 61850-7-410 Hydro PowerIEC 61850-7-420 Distributed Energy Resources (DER)
© ABB Group July 25, 2011 | Slide 10
Overview IEC 61850Standard
© ABB Group July 25, 2011 | Slide 11
Base Model: Common Data Classes [7-3]
Overview and Requirements: [1-5]
Communication Infrastructure[8-1, 9-1, 9-2]
MMS
GOOSE
Sampled Values
Abstract communication service interface (ACSI) [7-2]
Information Models [7-4, 7-410,7-420][61400-25], etc.
Configuration Language
[6]SCL (XML-based)
Meta Model[7-1, 7-2]Logical Node
Data Class
Overview IEC 61850Meta Model
© ABB Group July 25, 2011 | Slide 12
Information Exchange Model
Server Logical Dev ice
- LDName: ObjectName
Logical Node
- LNName: ObjectName- LNRef: ObjectReference
Data Obj ect
- DataObjectName: ObjectName- DataObjectRef: ObjectReference- m/o/c: CODED ENUM
DataSetBufferedReportControlBlock
UnbufferedReportControlBlock SettingGroupControlBlock Log
LogControlBlock
GOOSEControlBlock
MulticastSampledValueControlBlockUnicastSampledValueControlBlock
Common Data Class
- CDC-ID: Visible String
TypeFile
- Fi leName: Visible String255- Fi leSize: INT32U- LastModified: T imeStamp
Logical Node Class
- LD-ID: Visible String
Data Attribute
- DataAttributeValue: [Defined in Type]- DataAttributeName: Visible String- FunctionalConstraint: FC- TrioOp: TriggerCondition- m/o/c: CODED ENUM
1
0..*
1 1..* 0..1 1..*
1
0..*
1
0..*
1
0..*
1
0..*
1
0..1
1 1..*
1
0..*
1
1
0..*
1
0..*
0..*
+OfType 1
1 0..*
0..1
+hasSubObject 0..*
0..*
+OfType 1
1
0..1
Overview IEC 61850Information Model
© ABB Group July 25, 2011 | Slide 13
From IEC 61850 7-4
From IEC 61850 7-3
Comparison OPC UA and IEC 61850Modeling Concepts
© ABB Group July 25, 2011 | Slide 14
Concept IEC 61850 OPC UAHierarchy X XAggregation X XVariable X XFunction - XReference - XClass Partly XMethod - XInheritance - XData Type X X
Taken from: Mahnke, W., Gössling, A., Urbas, L.: Informationsmodellierung für Middleware in der Automatisierung,Automation 2011
Comparison OPC UA and IEC 61850Summary of Comparison
IEC 61850
Started with a meta model tailored for substation automation, including concrete logical node classes
Model can be extended for other domains by defining logical node classes, as done for wind turbines, hydro power, or Distributed Energy Resources (DER)
Not all investigated modeling concepts supported, e.g. subtyping, but suitable for the addressed domains
Addresses also Engineering
OPC UA (IEC 62541)
Provides a generic Model Model and base Information Model providing all investigated modeling concepts
Standardized Information Models using the concepts, like ADI, OPC UA for IEC61131-3 by PLCopen
Does not address Engineering
© ABB Group July 25, 2011 | Slide 15
Conclusion
Information Modeling becomes part of standardized automation middleware
IEC 61850OPC Unified Architecture
Standardized Information Models can increaseEngineering EfficiencyIntegrationInteroperability
Opportunities to use the provided Semantic – need to be integrated into current tool landscape
VDI / VDE GMA AK 5.16 Middleware in der AutomatisierungResult: VDI/VDE 2657 Blatt 1 "Middleware in der Automatisierungstechnik - Grundlagen" Next Action: Focus on Information Modeling
© ABB Group July 25, 2011 | Slide 16