1. CIM and 61850 UML Overview Terry Saxton Xtensible Solutions

2. GWAC* Stack and the CIM Standards
*GWAC – GridWise Architecture Council

3. An Organizing Framework for CIM Standards
Layered Reference Architecture for TC57
See : 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
Layer 1 - Information and Semantic Models
Information Model
Generalized model of all utility objects and their relationships
Application independent, but defines all concepts needed for any application
CIM UML
Layer 2 - Context
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
Profiles
Layer 3 - Message Syntax
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
Message/File Format (XSD, RDF Schema, OWL)

5. From Information Model to Syntactic Model Ex: Energy Transaction
Abstract
Model
Information/ Semantic Model
From Information Model to Syntactic Model Ex: Energy Transaction
Context/ Profiles
UML World
Message Assembly
XML Syntactic World
<?xml version="1.0" encoding="UTF-8"?>
<xsd:element name=« MT_EnergyTransaction">
<xsd:sequence>
<xsd:element name=« EnergyTransaction"/>
<xsd:element name=« Name"/>
<xsd:element name=« Type"/>
</xsd:sequence>
</xsd:element>
Message Syntax
Syntactic
Model

6. 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 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
61850 UML
(.eap)
(.xmi)
jCleanCim
UML validation
UML statistics
UML doc gen
Profiling tool
Product1 / XMLEditor
Product2 / XMLEditor2
profile definition
scPheromfialegeneration
profile doc gen
Instance (.icd,.scd,.???)
IEC ,7-3,...
Ste(.pdoc/.pdf/.html) 1a
UML validation and statistics
IEC
(SCL.xsd configuration)
Validation tool
IEC ?
(.??? – on-line exchange, e.g.
(.log)
Web service)
Web publication, ...
Paper publication

9. Today’s main usage objectives of the IEC 61850 UML model (reminder)
Improve data model Auto-generated
quality and reactivity standard from the
UML model Access through
the web of the
data model
MMooddeelilinngg tteeaamm IEIECC CenCentrtraall OOffffiicece
ppuubbliliccaattiioonn IEIECC CenCentrtraall OOffffiicece content and
hhtmtmll WWeebb ppuubblilicacattiioonn structure
UMUMLL pdfpdf pdfpdf pdfpdf MMooddeell
((eeaapp,, xmxmii)) xmxmll hhtmtmll Download
uummll xmxmll ((ddaatata machine-readable
mmooddeell)) data model
Tissue process
IInntteerrnnaall ttoo
IIECEC Integrate Tissues
AAddddiittiioonnaall FFoorrmmaall
ddeelliivveerryy
sosoftftwwaarree ttooooll
Today’s main usage objectives of the
IEC UML model
Improve data model quality and reactivity
Auto-generated standard from the UML model
Access through the web of the data model content and structure
Modeling team
IEC Central Office publication
IEC Central Office Web publication
html
UML
pdf
pdf
pdf
Model (eap, xmi)
Download machine-readable data model
xml
html
uml
xml (data
model)
Tissue process
Internal to IEC
Integrate Tissues
Additional software tool
Formal delivery

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 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 UML
Primary purpose for 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 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 XSD or use none of it
Usable parts of for product developers are the standard XSDs

12. 61850 UML and Copyrights Way Forward
61850 UML appears to be copyrighted by IEC
Current understanding of Christoph Brunner, WG10 Convener, who was responsible for initial development of standards and later for generation of UML
However, adding data types to the OpenFMB model that map 1:1 to data types should be permissible, as long as compliance to 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 equivalent data types or other properties.

13. Questions?