Embed Size (px)
Citation preview
2
GWAC* Stack and the CIM Standards
Organizational
Technical
Informational
8: Economic/Regulatory Policy
7: Business Objectives
6: Business Procedures
3: Syntactic Interoperability
5: Business Context
2: Network Interoperability
4: Semantic Understanding
1: Basic Connectivity
Interoperability Categories
Political and Economic Objectives as Embodied in Policy and Regulation
Strategic and Tactical Objectives Shared between Businesses
Alignment between Operational Business Processes and Procedures
Awareness of the Business Knowledge Related to a Specific Interaction
Understanding of the Concepts Contained in the Message Data Structures
Understanding of Data Structure in Messages Exchanged between Systems
Mechanism to Exchange Messages between Multiple Systems across a Variety of Networks
Mechanism to Establish Physical and Logical Connections between Systems
CIM
*GWAC – GridWise Architecture Council
3
An Organizing Framework for CIM Standards
• Layered Reference Architecture for TC57– See 62357-1: Reference Architecture for Power System
Information Exchange, First Edition
• Based on UN/CEFACT – Layer 1: Information Model– Layer 2: Contextual Model– Layer 3: Message Syntax
• Rules for Message Assembly
4
CIM Layered Architecture
CIM UML
Layer 1 - Information and Semantic Models
Layer 2 - Context
Layer 3 - Message Syntax
Profiles
Message/FileFormat
(XSD, RDF Schema, OWL)
Contextual layer restricts information model• Specifies which part of CIM is used for given profile• Mandatory and optional• Restrictions• But cannot add to information model
Message syntax describes format for instance data• Serialization of instance data• Can re-label elements• Change associations to define single structure for
message payloads• Mappings to various technologies can be defined
Information Model• Generalized model of all utility objects and their
relationships• Application independent, but defines all concepts
needed for any application
5
From Information Model
to Syntactic Model
Ex: Energy Transaction
AbstractModel
Syntactic Model
<?xml version="1.0" encoding="UTF-8"?><xsd:element name=« MT_EnergyTransaction"><xsd:sequence> <xsd:element name=« EnergyTransaction"/> <xsd:sequence> <xsd:element name=« Name"/> <xsd:element name=« Type"/> </xsd:sequence> </xsd:element>
UML World
XML Syntactic World
Information/SemanticModel
Context/Profiles
MessageAssembly
MessageSyntax
6
CIM RDF
CIM/UML
CPSMProfile
CIMCIM Ext
Bridge Foreign
WG 14Profiles
OtherProfiles
Messages
XMLSchema
OWLDataBaseSchema
CIMRDF
XMLNDR
OtherRules
Information
Context
MessageAssembly
ExchangeSchema
Rules
UMLModelling
Logical Schemas
Bridging
WG 14Message Structure
WG 13File
Structure
Layered Architecture for CIM Standards
7
What is the CIM?
• It’s more than a set of standards – it’s a solution!• UML model can be customized or tailored to fit specific utility data
requirements– Private extensions– Merging and harmonizing with other standard models– Subset can be published as a standard from a different SDO
• Example: NAESB Open Field Message Bus (OpenFMB) based on combined CIM and 61850 object models
• New interface profiles can defined for information exchange• New design artifacts (e.g., XSDs) can be generated with same
tools used to develop the CIM standards
8
What can be derived from 61850 UML
In case of 61850, each section of SCL schema defines a profile, the union should be in UML
jCleanCim• UML validation• UML statistics• UML doc gen
IEC 61850-6(SCL.xsd configuration)
Instance (.icd,.scd,.???)
61850 UML(.eap) (.xmi)
• profile definition
• scPheromfialegeneration
• profile doc gen
Profiling tool
IEC 61850-7-4,7-3,...Ste(.pdoc/.pdf/.ht
ml) 1aUML validation and
statistics(.log)
Validation tool
Product1 / XMLEditor
IEC 61850-?(.??? – on-line exchange, e.g.
Web service)
Product2 / XMLEditor2
Web publication, ...
Paper publication
9
Today’s main usage objectives of theIEC 61850 UML model (reminder)
Improve data model Auto-generatedquality and reactivity standard from the
UML model Access through
the web of thedata model
MMooddeelilinngg tteeaamm IEIECC CenCentrtraall OOffffiiceceppuubbliliccaattiioonn IEIECC CenCentrtraall OOffffiicece
content and
hhtmtmllWWeebb ppuubblilicacattiioonn structure
UMUMLL pdfpdf pdfpdf pdfpdf MMooddeell((eeaapp,, xmxmii)) xmxmll hhtmtmll Download
uummll xmxmll
((ddaatatamachine-readable
mmooddeell)) data modelTissue process
IInntteerrnnaall ttoo
IIECEC
Integrate TissuesAAddddiittiioonnaall FFoorrmmaall
ddeelliivveerryy
sosoftftwwaarree ttooooll
html
IEC Central Office Web publication
UMLModel
(eap, xmi)
html
Additional software tool
IEC Central Office publication
Internal to IEC
Formal delivery
xml
uml
Modeling team
xml (datamodel)
Tissue process
Today’s main usage objectives of theIEC 61850 UML model
Auto-generated standard from the
UML model Access through the web of the
data model content and
structure
Download machine-readable
data model
Improve data model quality and reactivity
Integrate Tissues
10
CIM UML
• UML was developed first in 1996 as Foundation layer – Existed before first IEC CIM standard documents were published
• Complete normalized model of utility operations• Via profiling, subset of UML can be defined as a message payload• From beginning, recognized that the UML was useful for not only
generating IEC standards (e.g., XSDs) but also with extensions for– Generating standards for other SDOs (e.g., NAESB ESPI and ZibBee)– Generating enterprise semantic models and message payloads for utility projects
(e.g., ENTSO-E CGMES)– Auto-generation of Word documents fir IEC using JCleanCIM
• For many years CIM UML has been publicly available on the CIM User’s Group SharePoint site– Consequence: Cannot be copyrighted
11
61850 UML
• Reverse engineered from the published IEC 61850 standards about 3 years ago, using data tables and XSDs primarily for SCL (Substation Configuration Language) used to configure IEDs– Content of UML is/was limited to only what is required for each XSD – “UML is primarily union of SCL schemas”– No comprehensive model like CIM behind 61850 UML
• Primary purpose for 61850 UML is to improve– quality of the data models– Auto-generate XSDs for SCL (may be additional XSDs – not sure), and – ease of maintenance of Word documents (via auto-generation from the UML using
jCleanCIM tool
• Never intended that 61850 UML would be used for anything but generation of their standard models, XML schemas, and IEC MS Word documents. Consequence:– No customization/extension of UML for other purposes was envisioned– Thus no customization of XSDs – use 100% of 61850 XSD or use none of it– Usable parts of 61850 for product developers are the standard XSDs
12
61850 UML and Copyrights• 61850 UML appears to be copyrighted by IEC
– Current understanding of Christoph Brunner, WG10 Convener, who was responsible for initial development of 61850 standards and later for generation of 61850 UML
• However, adding data types to the OpenFMB model that map 1:1 to 61850 data types should be permissible, as long as compliance to 61850 standards is not claimed.
Way Forward• For logical reasons, precedent-setting applications and perhaps legal
reasons as well, it seems best to start with the CIM UML that would be expected to have most of the classes, attributes, and associations needed to define the contents of the OpenFMb message payload XSDs.
• Then extend the CIM base as needed based on use case requirements from 61850 equivalent data types or other properties.
13
Questions?
