Comparison of MultiSpeak Connectivity Model and the IEC CIM NetworkDataSet

1
Comparison of MultiSpeak Connectivity Model and
the IEC CIM NetworkDataSet

• Gary A. McNaughton
• Cornice Engineering, Inc.

2
Outline

• Background on MultiSpeak and CIM
• Why MultiSpeak and CIM should be harmonized
• How harmonization can occur
• MultiSpeak and CIM power system data models

3
Standards for Integration of Distribution
Applications

• MultiSpeak
• Developed by NRECA in collaboration with key
  industry vendors
• Covers applications of interest to distribution
  utilities currently doesnt include power
  scheduling or generation
• Standard is mature, but scope is continuing to
  grow
• In use at over 200 utilities
• Mature interoperability testing program, applies
  to all interfaces
• Uses XML web services and batch transport
  profiles defined
• More information and specification available at
  www.MultiSpeak.org

4
Standards for Integration of Distribution
Applications

• CIM with Distribution Extensions
• Maintained by IEC Technical Committee 57
• Scope is larger than MultiSpeak, but is less
  mature
• Implementations based on CIM data model in place
  at dozens of utilities
• Implementation is messaging-based and transport
  agnostic, currently no transport profiles defined
• Interoperability testing is in place for two
  limited profiles (transmission and distribution
  power system model exchange)
• Core CIM in IEC 61970 distribution extensions in
  IEC 61968

5
MultiSpeak Point-to-Point Architecture
Prepaid Metering (PPM)
32
16
Payment Processing (PP)
33
Dynamic GIS Viewer (DGV)
11
Staking
Finance Accounting (FA)
31
29
Customer Relationship Management (CRM)
Static GIS Viewer (SGV)
21
28
Customer Billing (CB)
12
GIS
14
Call Handling (CH)
22
24
19
7
23
2C
2B
2A
Engineering Analysis (EA)
SCADA
4
8
Meter Reading (MR)
Load Profile (LP)
6
15
10
18
Connect/Disconnect (CD)
27
Outage Analysis (OA)
Outage Detection (OD)
5
9
25
Load Management (LM)
3
26
30
1
6
MultiSpeak Services Bus Architecture
7
Point-to-Point Outage Handling Example
8
Outage Handling Example - Bus Architecture
2x
9
Why Harmonize MultiSpeak and CIM?

• Both standards have value and likely will
  co-exist in market
• Both standards will undoubtedly be simultaneously
  implemented in some utilities
• Inter-company messaging will likely be required
  among companies using different standards

10
Steps in Harmonization

• Map MultiSpeak web service methods to WG14 CIM
  messages (use case steps).
• Compare WG14 and MultiSpeak data payloads for
  each use case step.
• Create electronic data payload transformation.
• Create adapter layer to handle data
  transformation and messaging conversion.

11
Harmonization Example

• Map MultiSpeak web service methods to WG14 CIM
  messages. Choose network connectivity
• Compare WG14 and MultiSpeak data payloads for
  each use case step.
• Create electronic data payload transformation.
• Create adapter layer to handle data
  transformation and messaging conversion.

12
Harmonization Example

• Map MultiSpeak web service methods to WG14 CIM
  messages.
• Compare WG14 and MultiSpeak data payloads for
  each use case step. Compare MultiSpeak
  Connectivity and CIM NetworkDataSet payloads
• Create electronic data payload transformation.
• Create adapter layer to handle data
  transformation and messaging conversion.

13
Sample Distribution Circuit
14
Basic Differences

• MultiSpeak can handle section-oriented or node
  oriented models CIM uses nodes.
• CIM can have terminals associated with nodes
  MultiSpeak does not have terminals.
• MultiSpeak does not explicitly model ground.
• One terminal devices have an implied ground.
• Three terminal devices are modeled with two
  terminals and implied ground.

15
MultiSpeak and CIM Equivalence
16
Fuse Equivalence Peeling the Onion

• CIM Fuse contains more than MultiSpeak fuse
• Equivalent is MultiSpeak overcurrentDeviceBank
  containing fuse units.
• MultiSpeak overcurrentDeviceBank contains more
  than a CIM Fuse
• Missing parts are in SwitchProperties child of
  the Fuse.
• CIM Fuse w/ SwitchProperties has more than
  MultiSpeak OCD w/ fuses
• Missing parts are in eaEquipment catalog

17
Steps in Harmonization

• Map MultiSpeak web service methods to WG14 CIM
  messages (use case steps).
• Compare WG14 and MultiSpeak data payloads for
  each use case step.
• Create electronic data payload transformation.
• Create adapter layer to handle data
  transformation and messaging conversion.

18
(No Transcript)
19
Steps in Harmonization

• Map MultiSpeak web service methods to WG14 CIM
  messages (use case steps).
• Compare WG14 and MultiSpeak data payloads for
  each use case step.
• Create style sheet data payload transformation.
• Create adapter layer to handle data
  transformation and messaging conversion.

20
Conclusions

• CIM and MultiSpeak are both complete, consistent
  data models for distribution modeling
• There are stylistic differences reflecting the
  needs and perspectives of the modelers
• The models are symantically and topologically
  equivalent
• It is possible to electronically convert payloads
  between the data models
• The two data models can co-exist if desirable

21
For More Information

• Technical Contact Program Contact
• Gary A. McNaughton Bob Saint
• Cornice Engineering, Inc. NRECA
• P.O. Box 2350 4301 Wilson Blvd.
• Pagosa Springs, CO 81147 Arlington, VA 22203
• Phone [phone] [phone]
• gmcnaughton_at_corniceengineering.com
  Robert.Saint_at_nreca.coop
• www.MultiSpeak.org