IEC TC57 Working Group14: System Interfaces For Distribution Management

1
IEC TC57 Working Group14System Interfaces For
Distribution Management

• Organizing Semantics For Effective
• Enterprise Application Integration
• Contact Greg Robinson For Further Information
• E-mail grobinson_at_xtensible.net

2
Topics

• Key Concepts
• Defining Message Types
• Overview of Work

3
Standards

• Play an essential role in growing markets by
• Lending an air of credibility to a technology
• Establishing rules of engagement in the
  marketplace
• Reducing risk for suppliers and consumers
• Standard interfaces insulate utility investments
  in application software from product specifics
  that will change as products evolve
• From the vendor perspective, a consistent
  architecture deployed across utilities enlarges
  the market for its applications, reduces risks,
  and provides economy of scale
• Reusable application interfaces allow utilities
  to migrate from one application to another with
  minimal loss of information that the utility
  created with the previous application
• For example Without the Structure Query Language
  (SQL89) standard, the relational database market
  would not have developed into the
  industry-dominating force we know today

4
Working Group 14 Establishing A Common Language
For Enterprise Application Integration In the
IEC 61968 Series of Standards
Information www.cimuser.org
5
Lowering Total Cost of Ownership More Than
Middleware is Needed
ltmany to manygt growth
ltmany to onegt growth
Total Cost of Ownership
Total Cost of Ownership
of Connections
of Connections
6
The building of the tower of Babelby Pieter
Bruegel, 1563Oil on oak panel, Kunsthistorisches
Museum, Vienna
Inter-Application Integration Solutions Always
Experience Scaling Problems Without A Common
Language For Information Exchange
7
How Utilities Are Leveraging AStandards-Based
Common Language
The Common Language Is A Canonical Data Model
Based On IEC TC57s Common Information Model
(CIM)
Dist Wires Model
Grid Wires Model
DAC
VRU
Outage Reporting
Information Exchange Model
Distribution Automation
OMS
CIS
EMS
...
Application Integration Middleware Common
Language
Event History
Data Warehouse
Substation Automation
Human Resources
Work Management
AM/FM/GIS
8
Decoupled Information Exchange
Dist Wires Model
Grid Wires Model
DAC
VRU
OMS
EMS
...
Event History
9
The Common Information Model (CIM) - What Is It?

• An information model representing real-world
  objects found in transmission and distribution
  operation and management
• Includes object classes, their attributes and
  relationships between classes/objects
• A tool to enable data access in a standard way
• Inspiration for logical data schemas (e.g., for
  an operational data store)
• Common language to navigate and access complex
  data structures in any database
• A tool to enable integration of
  applications/systems
• Provides a common language for exchanging
  messages between systems

10
The CIM Is Expressed In Unified Modeling Language
(UML) Notation
Class Name usually describes things in the real
world
Class Attributes describe significant aspects
about the thing
This Specialization indicates that a Pole is a
type of Structure. Since a Structure is a
type of Asset, the Pole inherits all of the
attributes from both Structure and Asset
For more information on UML notation (a
standard), refer to Martin Fowlers book UML
Distilled, Addison-Wesley
Associations connect classes and are assigned a
role that describes the relationship
11
Topics

• Key Concepts
• Defining Message Types
• Overview of Work

12
The IEC 61968-1 Interface Reference Model (IRM)
Provides The Framework For Identifying
Information Exchange RequirementsAmong Utility
Business Functions
13
Message Types Are Defined Based On Information
Exchange Requirements
14
Example Message Type Switching Schedule
Examining The Header
Examples In Next Two Slides
15
Message Types Are Created By Combining IEC 61968
Verbs With Information Exchange Topics, Referred
To As Nouns
16
(IEC 61968 Verbs - continued)
17
Example Message TypeSwitching Schedule
Examining The Payload
Note Details In Next Slide
18
Note All Elements In Every Message Type, such as
the ScheduleStep shown here, are Exactly as
they are Defined Once in the CIM
Snippet From A Message Type
Snippet From The CIM
19
Association Roles

• In this snipped from the CIM, note that a
  Document may be created or modified by several
  persons (ErpPerson)
• Each ErpPerson is associated with various
  Organisations
• Each ErpPerson has a specific role
  (DocErpPersonRole) relative to a given
  Document
• Examples RequestedBy, AuthoredBy, EditedBy,
  CheckedBy, ApprovedBy

20
Rendering Association Roles In Information
Exchange Schemas
21
CIM Development Collaboration
TC57
W3C
WG16Markets
OpenApplicationGroup
AHWG 07Harmonization
SPAG
WG14 Enterprise / DMS
WG 10 Substations
CIM
WG13 EMS
EPRI UCA2 Project
EPRI CCAPI CME Projects
22
TD ltgt ERP

• IEC TC57 WG14 And The Open Applications Group
  (OAG) Collaborate To
• Improve utilities' ability to integrate between
  TD applications (IEC TC57 domain) Enterprise
  Resource Planning (ERP) applications (OAG domain)
• Both support integration among disparate
  applications - inside and outside the company
  (i.e., e-commerce)
• OAG Business Object Documents (BODs) are
  therefore referenced (via namespace) for items
  like Purchase Orders, Bill Of Materials, etc.
• Note Integrating messages using namespace
  accomplishes desired objectives without dealing
  with the complexity of integrating model files.

23
Reasons For Using Graphics Markup Language (GML)
Scalable Vector Graphics (SVG)

• GML is being standardized through ISO
• CIM continues to focus on utility domain modeling
  by leveraging well supported graphics standards
  (i.e., GML SVG)
• CIM is more robust since rendering rules, for
  standards other popular graphics exchange
  formats, are now outside of the CIM
• Utilities are able to use the CIM with widely
  available technologies products and not be
  constrained by graphics limitations
• Adjustments were included in revised CD 61968-4,
  released January 4, 2004

24
Topics

• Key Concepts
• Defining Message Types
• Overview of Work

25
IEC 61968A Series Of Standards

• IEC 61968 Part 1 The Interface Architecture
• Provides for an Adaptable Utility Infrastructure
• Partitions Business Systems based on
• Things that are stable
• Abstract Application Component Interfaces
  represent stable technology elements
• Things that can be controlled by Utilities
  Suppliers
• Middleware Services that can be changed
  inexpensively
• Provides a stable basis for Enterprise-Wide
  Integration
• It Transcends the Life-Cycle of individual
  Application Systems and Middleware

26
IEC 61968A Series Of Standards

• Parts 3-10 Inter-Application Message Exchange
• Each Part covers a different Business Function
  identified In the Interface Reference Model (IRM)
• Interfaces are defined for each Business
  Sub-Function
• Use Cases and Activity Diagrams are used to
  articulate Information Exchange Requirements
  among Interfaces
• These are available in Part 12
• Message Types are then defined for each required
  Information Exchange
• Message Types may be implemented using different
  protocols
• A Message Type is a Canonical Data Model based on
  the CIM
• WG14 defines Message Types using XML Schema (XSD)

27
IEC 61968A Series Of Standards

• Part 2 The Glossary
• Part 11 Common Information Model
• The CIM defined by WG14, which is an extension of
  the CIM that is defined by WG13 (IEC 61970).
• Part 12 Technical Report DMS Use Cases
• Upon The Completion Of Parts 1-10, A Final Report
  Will Be Submitted To IEC That Will Contain All
  Use Cases That Were Utilized During The
  Development Of IEC 61968.
• Part 13 Common Distribution Power System Model
  Exchange
• (XML RDF)

28
WG14 Activities

• Standards Drafts are defined for parts 1, 2, 3,
  4, 6, 8, 11, 12, 13
• Active Vertical Teams (61968-3-10, 13)
• Part 4 Team Records Asset Management
• Part 6 Team Maintenance Construction
• Part 5 and 7 Team Operational Planning and
  Optimization and Network Extension Planning
• Part 8 Team Customer Support
• Part 9 Team Metering Reading and Control
• Part 13 Team Common Distribution Power System
  Model
• Modeling Team (61968-11) Support
• Develops a consistent model across business
  functions
• Collaborates with other standards development
  efforts as appropriate
• Releases in-work CD as needed to support review
  process
• Use Case Team (61968-12) Support
• Releases updated report as needed to support
  review process

29
Conclusion

• Basing a Utilitys Integration Infrastructure on
  the IEC 61968 Series of Standards
• Leverages Standards Optimized For EAI, SOA
  (Service-Oriented Architecture), and Web Services
• Improves Ability To Integrate Business Processes
  Across Applications
• Lowers Total Cost of Ownership Implementation
  Risks
• Facilitates Integration With ERP Applications
• Positions Utility To Benefit From Evolving
  Marketplace Of Conforming Applications
• Lowers Effort For Integrating Legacy Systems
• Facilitates Integration Needed In Mergers and
  Acquisitions