IEC TC57 WG14: System Interfaces For Distribution Management

1
IEC TC57 WG14System Interfaces For Distribution
Management

• Status Report For IEC TC57
• Beijing, China
• October 2002
• Contact Greg Robinson, BearingPoint,
• For Further Information
• E-mail gmrobinson_at_bearingpoint.net

2
Utility Application Integration Standards
Collaboration
TC57
OpenApplicationGroup
W3C
WG9DistributionFeeders
WG7ControlCenters
SPAG
WG14 DMS
WGs 3,10,11,12 Substations
EPRI UCA2 Project
CIM
WG13 EMS
EPRI CCAPI Project
OLEProcess Control (OPC)
Object Mgmt. Group
ebXML - TBD
3
IEC TC57 WG14 Interface Reference Model
Information http//support.ces.com/wg14
4
The IEC 61968 Concept
VRU
Accounts Payable
General Ledger
Information Exchange Model
Budgeting
...
The Integration Bus Middleware Common
Language
Data Warehouse
Materials Management
Event History
Facilities Management
Human Resources
Application Connector
The Common Language Is Based On The Common
Information Model (CIM) Specified In IEC
Standards. It Is Defined In The Information
Exchange Model (IEM). The Physical
Implementation Of The IEM Varies Based On
Selected Technologies.
5

Some Major EAI Features
Real Time Monitoring Analysis
Business Process Automation
Communication Integration
Message Broker Functionality
Connectors / Adapters (Data Integration)
Other Applications...
Outage Management
Distribution Automation
Work Management
14
6
Dist Wires Model
Grid Wires Model
DAC
VRU
OMS
EMS
...
Event History
7
Ontologies

• Establish
• a common vocabulary
• a consensus on its interpretation
• Basis for machine-readable meta-data
• accessed by applications and/or message
  definitions
• thus avoid semantic conflicts
• The Common Information Model (CIM) Provides An
  Ontology For Utilities

8
Integration Bus
(Source DistribuTECH 2002 paper)
9
An Example Of Using IEC 61968 Standards At A
Utility - PacifiCorp
(Source DistribuTECH 2002 paper)
10
IEC TC57 WG14 Example Integration Scenario for
Extension Implementation
2
Maintenance Construction
Network Model Customer Attachments
Operation
3
1
Planning
Extension Project Job
Switching Schedule
Record
Optimization
Asset
Management
3
3
3 Customer Affected
Switching Schedule
Switching Schedule
See Usecase Network Extension Planning
Approved Extension Project
Safety Document(Issue/Cancel)
See Use Case Network Edit
Extension Project Job Complete
Safety Document(Issue/Cancel)
Planned Outage
10
Planned Outage Status
13
9,11
9,11
Changes to Network
4
8
7,12
Network Extension Planning
4
Network
Planned Outage
6
Start Extension Project
Operation
7,11
Changes to Network
8
Planned Outage Status
13
Extension Project Job Complete
5
(This Example Integration Scenario Was Submitted
to IEC TC57 WG14 By Midlands Electricity and M3i)
Planned Outage Status
Customer
11
Created Switching Schedule Message Type Top
Level
12
Control Area Of Message Type
Message Type Names Are In Control Area. They
Are Created By Combining Verbs with CIM Nouns.
13
Message Types Used For Information Exchange Are
Created By Combining Verbs with CIM Nouns.
14
(Verbs Continued)
15
Created Switching Schedule Message Type 2nd
Level Elements
16
The CIMs Operational Package
Note how these attributes are referenced on the
next slide in the Message Type Created Switching
Schedule
17
Schedule Step Segment Of CreatedSwitchingSchedule
- Elements From Schedule Step Class Attributes
Inheritance
18
Namespace Is Used To Reference Reusable
Definitions
Multiple Messages Reference The Definitions
Contained In One CIM XML XSD Base File
19
Schedule Step Segment - Elements From Schedule
Step Class Associations
20
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)
• The OAGs model is therefore provided as a
  default ERP model in the CIM. However, Other
  models (e.g., SAP) can be substituted for all or
  portions of the OAG model as appropriate.

21
IEC 61968 Part 1 The Interface Architecture

• Provides For An Adaptable Utility Infrastructure
• Partitions Distribution Management Application
  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 That Can Be
  Changed Inexpensively
• A Stable Basis For Enterprise-Wide Integration
• It Transcends The Life Cycle Of Individual
  Application Systems And Middleware

22
IEC 61968A Series Of Standards

• Part 2 The Glossary
• Parts 3-10 DMS Interface Standards
• Will Be Developed In Accordance With New Work
  Item Proposals (NWIPs)
• Each NWIP Covers A Different Business Function
  Identified In Part 1s Interface Reference Model
  (IRM)
• Interfaces Are Defined For Each Abstract
  Component Identified In The IRM Supporting The
  Business Function

23
IEC 61968A Series Of Standards

• Part 11 Distribution Model
• Part Of The Proposed TC57 Common Information
  Model (CIM), Which Is An Extension Of The WG13
  CIM.
• 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.

24
Active WG14 Teams

• Editor Team
• Vertical Teams (61968-3-10)
• Part 3 Team Network Operations (Just Finished)
• 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 and 9 Team Customer Support and Meter
  Reading And Control
• Modeling Team (61968-11)
• Supports Vertical Teams With Consistent Model
  Necessary To Define Information Exchange
• Rather Than Inventing Everything, Extensions Are
  Being Harmonized (WG13, WG10/11/12, OAG,
  MultiSpeak, others?)
• Releases updated CD in step with Part 3-9
  releases to support review process.
• Use Case Team (Technical Report)
• Releases updated report in step with Part 3-9
  releases to support review process.

25
Schedule Delays

• Model Driven Message Type Definitions
• To make IEC 61968 standards most effective and
  relevant, WG14 had to resolve issues regarding
  the transformation of the TC57 Common Information
  Model (CIM) into message types, which was
  impacting IEC 61968 parts 3-9.
• This has now been resolved through tools that
  translate the CIM into XML schema files coupled
  with a process for generating consistent message
  type definitions.
• Resources
• A critical mass of specialists is required for
  each part.
• This has been accomplished over the course of the
  project, but more depth is still sought in
  Customer Information Systems and Metering.
• The critical issues are sufficiently resolved to
  enable WG14 to have much better success in
  maintaining schedule.

26
(No Transcript)
27
Proposed IEC TC57 WG14 Milestones
61968 Initial Development Complete July 2004
Rotterdam
London
Bilbao
Vienna
Rome
Bath
TBD
TBD
Williamsburg
Paris
Heidelberg
Montreal
Oslo
Minnesota
Grindelwald
Key West
San Diego
Midlands
Keystone
Davos
Miami
1/04
1/97
1/98
1/99
1/00
1/01
1/02
1/03
Prototype Business Functional Area Standards
Development (Parts3-10)
CD -3 -4
Develop Inter-Application Integration Framework
CDV -3
CD -1 -2
Revised CD -4
CDV -4
Revised CD -1 -2
CDV -1
FDIS -1
CD -10
CDV -10
INF CD -11
CD - 5, 6, -7, -8, -9, -11
CDV
INF TR Use Cases
INF TR
TR