Configure to fit Presentation

1
XTENSIBLE SOLUTIONS GROUP
WG13Status Report
October 2002Beijing, China
2
Topics

• IEC WG13 Standards Efforts
• Common Information Model (CIM) Status
• Generic Interface Definition (GID) concepts
• Document Structure and Status

3
Membership WG13

• Canada 3
• China 1
• Finland 1
• France 2
• Germany 2
• Japan 3
• Netherlands 1
• Norway 1

• Russia 1
• Spain 2
• Sweden 1
• Switzerland 1
• UK 4
• USA 6
• Other 3

4
Related Activities

• China
• WG13 standards translated to Chinese
• Interoperability testing with CIM XML standards
  and models
• Japan
• In-country working group to track WG13 standards

5
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

6
CIM Packages
Generation
LoadModel
Outage
SCADA
Protection
Meas
Financial
Wires
EnergyScheduling
Topology
61968
Reservation
Core
Domain
7
CIM XML Standards

• CIM has been translated into XML
• For exchanging power system models
• For message-based information exchange between
  systems
• RDF (Resource Description Framework) schema and
  syntax used for CIM XML document
• Standard XML format that any EMS can understand
  using standard Internet and/or Microsoft
  technologies
• Automatically generated from the CIM Rational
  ROSE model using Xpetal tool
• NERC mandated use of this standard by Security
  Coordination Centers to exchange power system
  models by September 2001
• CPSM minimum requirements profile
• Other profiles possible

8
CIM XML Interoperability Tests

• EPRI sponsored interoperability tests based on
  the CIM XML standards
• Four interoperability tests successfully
  completed
• Exchanged 40-100 bus sample model files and
  real-world large scale models (12,000 bus) and
  several sample models (40 to 100 bus)
• Ran Power Flow Solutions
• Exchanged incremental and partial model update
  files
• Validated the use and acceptance of this standard
  by several suppliers who provide products to the
  electric utility industry
• Supported NERCs September 2001 mandate
• Test reports available from EPRI
• China carried out independent CIM XML
  interoperability tests

9
Related Activities

• CIM Implementations at Utilities
• Many uses starting with base CIM model standards
• Private extensions incorporated
• XML information exchange models based on CIM
• CIM Extensions for Market Operations
• EPRI project CIM Market Extensions (CME)
• Model Coordination and Harmonization
• Continued coordination with 61968 models (WG14)
• No major issues
• CIM use to support TASE.2 61870 standards (WG07)
• Configuration
• Harmonization with 61850 models
• Vision of seamless architecture
• Establish CIM User Group
• All CIM users/implementers
• Tutorials, issue compilation/resolution,
  training, publications, test suites

10
CIM Acceptance

• Over 30 utilities, ISOs and NERC
• Endorsed by other standards organizations
• 33 applications based on CIM
• 29 suppliers sell application/products based on
  CIM
• See CIM Reference List for Details
• Foundation for Model-Driven Integration
  architecture
• Provides common language for system integration
  messaging
• In use at multiple utilities

11
Some CIM Users

• Allegheny Power Operational Database Maintenance
  System
• BC Hydro Operator Training Simulator
• BC Hydro Voltage Stability Analysis
• California ISO Energy Management System
  Replacement
• China Light and Power Company, Hong Kong Data
  Repository System
• Commonwealth Edison Operator Training Simulator
• Consolidated Edison Feeder Management System
• Consumers Energy Advanced Network Applications
• Duke Energy Operational Database Maintenance
  System, Integration
• Duquesne Light SCADA EMS Integration
• East Midlands Electricity Integration
• Entergy Operational Database Maintenance System
• ERCOT-ISO Network Applications and EMS
  Replacement
• Florida Power and Light DMS and Asset Management
  Integration
• Kansas City Power and Light EMS, DMS, CIS and
  ICCP Integration

• Illinois Power SCADA and AGC system
• MAIN Operational Database Maintenance System
• MISO Operational Database Maintenance System
• NEPCO Jordan CCAPI Open Application Platform
• NERC Security Coordinator Power System Model
  Exchange
• Public Service New Mexico Operational Database
  Maintenance System
• Southern California Edison OMS, DA, EMS and WMS
  Integration
• Southern Company Energy Marketing ICCP Data
  Repository
• Southwest Power Pool Operational Database
  Maintenance System
• Toronto Transit Commission Operator Training
  Simulator
• WAPA Watertown Operations Advanced Network
  Applications
• WAPA Electric Power Training Center Operator
  Training Simulator
• WAPA Operational Database Maintenance System
• EGAT Operator Training Simulator
• WSCC Operator Training Simulator

(Source EPRI CCAPI Project)
12
CIM Status

• CIM exists as ROSE UML model and IEC standard (MS
  Word)
• UML ROSE (All 61970 packages)
• Visit ftp.macro.com/epriapi/downloads/Part_3_CIM
• Current Version 10 (cim10_011015.mdl)
• CIMChanges011029.xls
• IEC documents
• Part 301 approved as FDIS July 2002
• National country comments to be addressed
• Part 302 on hold
• Part 303 SCADA is CD
• RDF Schema Version for CIM Version 10
• XML Schema Version for combined WG13/14 models

13
Benefits of Using CIM Approach

• Data model driven solutions leads to
  interoperability
• Provides common semantics for information
  exchange between heterogeneous systems
• Used for CA to CA communications
• NERC mandated use of CIM and RDF Schema version
  for power system model exchange
• Provides for automatic generation of message
  payloads in XML
• Ensures common language for all messages defined
• Avoids proprietary message formats from vendors
  (based on internal schemas)
• Eliminates work of creating DTD for each message
• Alternative to EDI or CSV file formats

14
Benefits of Using CIM Approach

• Uses industry standard modeling notation
• UML, XML
• Permits software tool use for
• Defining and maintaining data models
• Single point of maintenance for changes
• Documenting data models
• Automatic generation of information payloads
• Automatically generate IDL, Java, C code

15
What Does CIM Compliance Mean?

• The CIM is not a database it is an information
  model (i.e., meta data)
• IEC maintains as normalized model
• Users can denormalize for specific application
  uses when building logical schemas or messages
  based on CIM
• IEC WG13/14 defining standard messages
• CIM compliance means that at the public interface
  the data representation complies with the CIM in
  terms of
• Semantics naming and meaning of data
• Symantics data type
• Relationships relation to other parts of the
  CIM so that the data relationships can be
  navigated

16
IEC 61970 as an Integration Framework
17
Dist Wires Model
Grid Wires Model
DAC
VRU
OMS
EMS
...
Event History
18
GID (Generic Interface Definition)

• Allow customer or software developer to create
  components without concern for the differences in
  the capabilities of the underlying infrastructure
  on different systems
• Lead to standard API for any application to
  exchange information or access data
• Based on EPRI Control Center API (CCAPI) project
  to specify application interfaces

19
Service Interfaces

• Generic Data Access (GDA)
• Request/Reply Interface
• Based on DAF (Data Access Facility) and CIM XML
• Generic Eventing and Subscription (GES)
• Publish/Subscribe Interface
• Based on OPC/DAIS (Data Access for Industrial
  Systems) Simple Eventing
• High Speed Data Access (HSDA)
• R/R and Pub/Sub Interface
• Based on OPC/DAIS DA
• Historical Data Access (HDA)
• R/R and Pub/Sub Interface
• Based on OPC HDA/HDAIS

20
TC57 Namespaces

• TC57PhysicalModels
• Containment hierarchies such as being discussed
  in CIMXML group
• TC57ClassModels
• Class hierarchies
• TC57ISModels
• A standard way of exposing a component interface
  (what message types a component supplies, as well
  as, the schema of each message type)

21
TC57 Physical Model
22
TC57 Class Model
23
TC57 IS Model
24
Example Integration Scenario
D M Maintenance Tool
NA
VSA
Control center applications need to be integrated
SCADA
AGC
25
Point-to-point Integration
Serves SE results
NA
VSA
Serves measurements
SCADA
Serves connections, ratings, etc.
D M Maintenance Tool
Archive
Standard Interfaces would lower costs and provide
flexibility
26
Point-to-point Integration
Bus architecture would minimize integration points
27
Message Bus Based Integration
A message bus provides more powerful and robust
infrastructure as well as easier system
configuration
28
GID and IEC
IEC
OMG
OPC
29
WG13 Document Tree
30
WG13 Document Status
31
Contact Information

• To get more information about CCAPI TF
• Dave Becker, EPRI (dbecker_at_epri.com)
• Terry Saxton, KPMG Consulting (tsaxton_at_bearingpoin
  t.net)
• To obtain CCAPI, CIM, and IEC drafts
• Use Browser
• URL ftp//ftp.macro.com/epriapi/downloads/
• Use FTP client software
• Host ID ftp.macro.com/epriapi/downloads/
• User ID anonymous
• Password ltyour email addressgt
• Check in appropriate folder for documents
• For IEC documents and CIM models
• IEC 61970 EMS API Terry Saxton, Convenor WG13