Harmonization of the Common Information Model and MultiSpeak

1
Harmonization of the Common Information Model and
MultiSpeak

• Gary McNaughton, P.E.
• Cornice Engineering, Inc.
• Robert Saint, P.E.
• National Rural Electric Cooperative Association

2
Acknowledgements

• The authors gratefully acknowledge their
  co-authors of IEC 61968-MultiSpeak
  Harmonization, a paper accepted for presentation
  at CIRED 2011. Material from that paper is
  included here. Co-authors include
• Gerald Gray, Guiding Principle Consulting (USA)
• John Simmins, EPRI (USA)
• David Haynes, Aclara (USA)
• Alan McMorran, Open Grid Systems, Ltd. (UK)
• Eric Lambert, EDF (France)

3
Overview

• What is MultiSpeak?
• Why different standards?
• What does harmonization mean?
• Rationale for harmonization
• Approach to harmonization
• Results of early efforts
• Harmonization deliverables

4
Introduction to MultiSpeak

• Developed by NRECA in collaboration with key
  industry vendors
• MultiSpeak Initiative is a group of about 70
  vendors that provide products and services to
  distribution utilities.
• Standard is mature, scope is continuing to grow
• Well defined, third-party compliance and/or
  interoperability testing program since 2001.
• In use at over 600 utilities in at least 15
  countries
• Standard based on UML class model, XML Schema and
  web services messaging

5
MultiSpeak Vendor Members

• NISC
• NorthStar Utilities Solutions
• NRTC
• Olameter, Inc.
• Open Systems International
• Oracle Utilities
• OSIsoft
• Ovace A Mamnoon
• Papros, Inc.
• Partner Software
• Powel
• Power System Engineering (PSE)
• Professional Computer Systems (PCS)
• Progress Software
• QEI
• R.W. Beck (SAIC)
• SageQuest
• SEDC
• Sensus

• ABB
• Aclara (DCSI TWACS)
• Albeado
• ATS
• AutoDesk
• C3-Ilex
• Capricorn Systems
• Carina Technology, Inc.
• Central Service Association
• CGI
• Cigital
• Clevest Solutions
• Cooper Power (Cannon Technologies)
• Cooperative Fusion
• Cooperative Response Center
• Cornice Engineering
• Daffron
• EFACEC (Advanced Control Systems)
• Elster Integrated Solutions

Dated 3/2011
6
Why there are different standards?

• Partly historical
• Partly due to fact that small utilities cant
  justify cost of participation in international
  standards groups, hence have been
  under-represented on IEC working groups
• The different standards serve needs of different
  communities

7
CIM Users

• CIM typically is implemented by large IOUs
• With large IT staffs
• Messaging middleware
• Need to customize application interfaces to match
  existing business processes and legacy
  applications
• This community values
• Customizability and flexibility in messaging
  approach
• The CIM approach assumes that
• Messaging middleware exists
• Interoperation within a utility is all that is
  required, except where interoperability among
  utilities is critical, (e.g., power system model
  exchange),

8
MultiSpeak Users

• MultiSpeak integration is typically used by
  utilities looking for an out-of-the box
  solution
• Often these are small utilities, often with few
  IT staff
• Typically such utilities do not have ESB or
  messaging
• Such utilities often value
• Simple interoperable solutions that require
  little customizability default choices made in
  MultiSpeak work
• Interoperation among utilities, not just within a
  utility
• The MultiSpeak approach
• Includes protocol features to address lack of
  messaging
• Focuses on interoperation, but supports
  customization
• Can be implemented over transports other than web
  services, although this acts against core value
  of interoperation

9
What does harmonization mean?

• Harmonized standards Equivalent standards on the
  same subject approved by different
  standardization bodies, which allow for
  establishment of interchangeability of products,
  processes and services, and for mutual
  understanding of test results or information
  provided according to these standards
• Source NIST Global Standards Information web
  site http//gsi.nist.gov/global/index.cfm/L1-5/L2
  -44/A-87

10
What harmonization is not

• Unified Standards Two standards that move over
  time towards using the same data model and
  service definitions. The end result is that a
  single standard exists.
• An example of this approach is the plan for
  unifying CIM and IEC 61850

11
Rationale for harmonization

• Neither standard is complete, nor does either
  completely serve the needs of all portions of the
  industry.
• CIM and MultiSpeak are complementary and
  semantically compatible but not interoperable.
• Separate standards continue to be a stumbling
  block for utility implementations and for vendor
  community.
• Small international utilities have the same needs
  as small US utilities, but may be constrained to
  use international standards no acceptable
  solution exists

12
Proposed approach to harmonization
Existing Situation
Proposed Approach
13
ESB adapter requires mapping

• CIM message to MultiSpeak web service method
  mapping, including header fields
• CIM payload to MultiSpeak payload mapping
• Appropriate round-trip error handling

14
CIM on-demand meter reading
15
MultiSpeak on-demand meter reading
16
Message header mapping
17
Top-level object field mapping
MultiSpeak has added optional IdentifiedObject
fields in V4.x to facilitate harmonization
18
Meter reading payload mapping
19
Early results of EPRI harmonization project

• Proof of concept ESB service is being developed
  for this use case
• Early results are promising
• Mapping is being developed for IEC 61968-9
  messages and corresponding MultiSpeak methods
• Mapping with proof of concept ESB service is
  expected to be released in 2nd Qtr 2011

20
Planned harmonization documents

• Series of mapping documents for IEC
  standardization, named IEC 61968-14-1-x, where x
  is the 61968 Part number.
• Current plan is for 61968-14-1-9 (Metering and
  Control) and 61968-14-1-13 (CDPSM)
• Series of profile documents to build MultiSpeak
  functionality using CIM classes and messaging,
  named 61968-14-2-x, where x is the 61968 Part.
• Will identify gaps and strengths in both
  standards
• Will accelerate development of missing CIM Parts

21
For Further Information, Contact

• Gary McNaughton Bob Saint
• Cornice Engineering, Inc. NRECA
• P.O. Box 155 4301 Wilson Blvd.
• Grand Canyon, AZ 86023 Arlington, VA 22203
• Phone [phone] [phone]
• gmcnaughton_at_corniceengineering.com
  Robert.Saint_at_nreca.coop
• www.MultiSpeak.org