A history of the

Common Information

Model

in Eskom

Lloyd Jones

11 March 2015

We exist to serve a customer

• Where are we going?

• Why do we need decisions and alignment?

• What is CIM?

• How does it affect the distribution business?

• Who should pay attention and why?

• How does it related to distribution as a business?

• How does it relate to Smart Grids?

• How will it be used (examples)

• Role of IEC in this regard

2

3© 2015 Electric Power Research Institute, Inc. All rights reserved.

Dispatchable Forecastable

Base Load

Generation

Load Following

Generation+ Bulk Energy

Storage+/–

Customer

Demand= Interruptible

Load–

The Power System

Possible Industry Structures Source BCG

4

Scenario 3: Vertical

IntegrationScenario 2: Deconstruction

Sales and Dx

System

Operators

Tx System Operator

Centralised

generation and

storage

Consumption Consumption Steered consumption

Sales

Centralised

generation and

storage

Centralised

generation and

storage

Trading

Metering and

communication

Sales and decentralised

markets

Distributed generation Distributed

Generation

and storage

Scenario 4: Unbundling

Customer

Scenario 1: Unbundling

Generation

Consumption

Sales

Trading

Centralised

generation and

storage

Distributed generation

Trading

Tx System Operator Tx System Operator

Tx System Operator

Dx

System

Operator

Dx

System

Operator

Dx

System

Operator

The Power System – Looking Forward

Generation Flexibility and

Cost Optimization

Distributed Energy

Resource

Integration

Integrated Energy, Environment and Grid Modeling

Intelligent Sensor Systems, Communications, Analytics

Dynamic Power System Requires an End-to-End Integrated Approach

6

Sample of the old (current) Power System Model

Generator AC Line Substation

Company

Load

Operates

Operates

Belongs

To

Member

Of

Owns

Load Area

Connects

To

Connects

To

Connects

To

7

Coherent business decisions require Information from Many Individual Systems

AM/FM/GIS

Mobile

SCADA

Work Mgmt

Customer

Information

Network

Management

Maintenance

& Inspection

HRFinancial

Contract

Management

ProtectionAsset

Planning

Risk

Analysis

Network

Planning

HistorianOutage

Management

Property

MgmtCompliance

The CIM

VENDOR

HELP!

Distribution

Information &

Strategy

ManagementEnabling the Distribution Business Vision by Leading Continuous Business Improvement

Best Practices Model

From <many to many> to <many to one>

[Slide Is Courtesy Of David Connelly, OAG]

Distribution

Information &

Strategy

ManagementEnabling the Distribution Business Vision by Leading Continuous Business Improvement

EMS Control

Centre

Customer

Interface

Facilities

ManagementWork

Management

Customer

Information

Distribution

Automation Engineering

Planning

DataBase

DataBaseDataBase

DataBase

DataBase

DataBase

DataBase

DataBase

Migration from Point-to-Point

Cloud?!

Distribution

Information &

Strategy

ManagementEnabling the Distribution Business Vision by Leading Continuous Business Improvement

EMS Control

Centre

Customer

Interface

Facilities

ManagementWork

Management

Customer

Information

Distribution

Automation Engineering

Planning

Middleware

(CIM compliant)

= IEC TC57 WG14 Standard Interfaces Specification

DataBase

DataBaseDataBase

DataBase

DataBase

DataBase

DataBase

The Integration Bus

“Transformer”

“Trfr”“Txr”

“Transf”

Distribution

Information &

Strategy

ManagementEnabling the Distribution Business Vision by Leading Continuous Business Improvement

Data

Warehouse

Materials

Management

General

LedgerCIS

Facilities

Management

Budgeting

Human

Resources

Payroll

The “Integration Bus” = EAI + Common Language

Information

Exchange

Model

Event History Work

Management

...

Accounts

Payable

= 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.

VRU

The “Integration Bus” Concept

Courtesy : Greg Robinson, Xtensible Solutions, Inc

Distribution

Information &

Strategy

ManagementEnabling the Distribution Business Vision by Leading Continuous Business Improvement

IEC TC57 Standards Emphasis

(NE)

Network

Extension

Planning

(CS)

Customer

Support

(MR)

Meter

Reading &

Control

(AM)

Records &

Asset

Management

(MC)

Maintenance

&

Construction

IEC 61968-4 IEC 61968-6

IEC 61968-7 IEC 61968-8 IEC 61968-9

(ACT)

Customer

Account

Management

(FIN)

Financial

(PRM)

Premises

(HR)

Human

Resources

(EMS)

Energy

Management &

Energy Trading

(RET)

Retail

IEC 61968-10

OAG

(SC)

Supply

Chain and

Logistics

(NO)

Network

Operation

IEC 61968-3

and IEC 61970

(OP)

Operational

Planning &

Optimization

IEC 61968-5 and

IEC 61970

IEC 61968-10

and IEC 61970IEC 61968-10 and

OAG

IEC 61968-10 and

OAG

IEC 61968-10 and

OAG

IEC 61968-10 and

OAG

IEC 61968-10 and

OAG

Utility Electric Network

Planning, Constructing,

Maintaining, and Operating

Enterprise Resource Planning,

Supply Chain, and General

Corporate Services

Recommended Standards Coordination Strategy

IEC TC57 and OAG Standards Emphasis

Interface Reference Model (IRM)

Courtesy of Working Group 14, Greg Robinson

13

The Common Language should provide relevant Information to a user regardless of source

Engineering

Concerns

Materials

Management

ConcernsConstruction

Concerns

Operations

ConcernsProtection

Concerns

Maintenance

Concerns

14

Industry wide GridWise Interoperability Framework

Role of CIM

Distribution

Information &

Strategy

ManagementEnabling the Distribution Business Vision by Leading Continuous Business Improvement 14

Business Process Automation

Other

Applications...

Outage

Management

Distribution

Automation

Work

Management

Communication Integration

Some Major EAI Features

Real Time Monitoring & Analysis

Connectors /

Adapters

(Data Integration)

Message

Broker

Functionality

Four Digital Mega-trends Shaping Business and the Requirements for Successful Digital Transformation

Mobile

Devices

reaching

ubiquity

On-demand Business

Intelligence increasing

Cloud

computing is

maturingSocial Media &

Collaboration

becoming the

norm.

Mobile Means

Always-On, Always-

Connected, Always-

Relevant

Social: Listen to

the Customer

and Respond in

Real-Time

Cloud Computing:

Digital Customer

Experience

Game-Changer

Big Data Brings Big

Opportunities

The Future Energy Landscape developed by the “BDI initiative Internet of Energy” Working Group

Large-scale power plants

Renewable energy (fluctuating)

Consumer (traditional)

Consumer (intelligent)

Grid control

Transmission grid

Distribution grid

Load flows

Internet of Energy

Integration technology

1 - Technologies for home automation and decentralised energy generation

2 - Intelligent grid management systems on the transmission and distribution levels

3 - Installed smart metering technology

4 - ICT as a link between the Internet of Energy and the technical infrastructure

5 - Applications and services implementing the coordination of the energy grid on the

economic level

18

Application of Information Model

SISCO SYSTEMS

Common model creates

understanding

Application 1 Application 2

19

Foundational Relationships Of The CIM

PowerSystemResourceElectrical Network Role Used For

Planning, Operations, etc.

AssetPhysical Plant Filling A Role

Such As A Transformer, Pole, etc.

LocationWhere To Find Something By

GPS, Address, Electronically, etc.

OrganisationEntities Performing Roles Such

As Operations, Tax Authority

ContactPeople Performing Roles Such

Dispatcher, Field Operator, etc.

DocumentInformation Containers Such As

Trouble Ticket, Work Orders, etc.

CustomerIndustrial, Commercial, & Residential

Which Can Have Multiple Accounts

20

Let’s Look at each Layer of the CIM

CIM UML

Information and Semantic Models

Context

Message Syntax

Profiles

XML/RDF

Schema

Information Model• Defines all concepts needed for any

application

Contextual layer restricts information model• Specifies which part of CIM is used for

given profile• Mandatory and optional• Restrictions• But cannot add to information model

File syntax• Can re-label elements• Change associations to define single

structure for message payloads• Mappings to various technologies can

be defined

21

Connectivity

and

Topology

Model

Business Process Automation Concept

4.4.3 execute

(connection) work

4.4.2 schedule

(connection) resources

4.4.1 receive acceptance

and initiate work

Distribution

Customers

4.3 Progress Connection

Enquiries

acceptances proposals

work for scheduling

scheduled work

plan EHV outages

outage

request

confirmed

outages

acquire rights and

properties

acquisition

requests

confirmed

acquisitions

manage asset dataasset data for

update

create/update customer

records

proposals

new/updated

customer

records

Maintain DUOS Customer

Billing Details

ASC and ASC

change data

Service Providers

contracted

services

manage engineering

policies and standards

engineering

standards

level 34.4 Deliver Connection Services

Business Process Automation Concept

project designer

connections commercial team

connections commercial team

request

off-site

property

acquisition

acquire rights and

properties

acquisition

requests

4.4.2 schedule

(connection)

resources

work for

scheduling

Distribution

Customersacceptances

4.3 Progress

Connection Enquiries

proposals

receive and

log

acceptance

create project

check and

process

monies

received

logged

acceptance

project

created

create new

customer

records

assigned

project

create/update

customer records

new/updated

customer records

update

connection

agreement

record

check on-site

property

agreements

MPANs

initiated

Maintain

Customer Billing Details

change data

produce

detailed

design

OK

property/wayleave

requirement

completed

design

assign projectpayment

processed

activity4.4.1 receive acceptance and initiate work

Business Process Automation Concept

project manager

plan EHV outages

prepare asset data

acquire rights and

properties

4.4.3 execute

(connection)

work

4.4.1 receive

acceptance and

initiate work

determine

resource

requirements

create

service

orders

identify

outage scope

confirm

resource

availability

confirm

materials

create

material

orders

arrange

outage

release work

for execution

schedule

work

confirm

wayleaves

prepare

switching

schedule

work for

scheduling

resource

requirements

material

requirements

material

availabilityconfirmed

materials

confirmed

resource

work

scopeoutage

scope

confirmed

acquisitions

confirmed

acquisitions

work for

scheduling

to-be asset

data

outage

request

confirmed

outage

outage

details

scheduled work

switching

schedule

scheduled

work

resource

requirements

activity4.4.2 schedule (connection) resources

Business Process Automation Concept

project manager

plan EHV outages

prepare asset data

acquire rights and

properties

4.4.3 execute

(connection)

work

4.4.1 receive

acceptance and

initiate work

determine

resource

requirements

create

service

orders

identify

outage scope

confirm

resource

availability

confirm

materials

create

material

orders

arrange

outage

release work

for execution

schedule

work

confirm

wayleaves

prepare

switching

schedule

work for

scheduling

resource

requirements

material

requirements

material

availabilityconfirmed

materials

confirmed

resource

work

scopeoutage

scope

confirmed

acquisitions

confirmed

acquisitions

work for

scheduling

to-be asset

data

outage

request

confirmed

outage

outage

details

scheduled work

switching

schedule

scheduled

work

resource

requirements

activity4.4.2 schedule (connection) resources

Business Process Automation Concept

project manager

plan EHV outages

prepare asset data

acquire rights and

properties

4.4.3 execute

(connection)

work

4.4.1 receive

acceptance and

initiate work

determine

resource

requirements

create

service

orders

identify

outage scope

confirm

resource

availability

confirm

materials

create

material

orders

arrange

outage

release work

for execution

schedule

work

confirm

wayleaves

prepare

switching

schedule

work for

scheduling

resource

requirements

material

requirements

material

availabilityconfirmed

materials

confirmed

resource

work

scopeoutage

scope

confirmed

acquisitions

confirmed

acquisitions

work for

scheduling

to-be asset

data

outage

request

confirmed

outage

outage

details

scheduled work

switching

schedule

scheduled

work

resource

requirements

activity4.4.2 schedule (connection) resources

Business Process Automation Concept

project manager

plan EHV outages

prepare asset data

acquire rights and

properties

4.4.3 execute

(connection)

work

4.4.1 receive

acceptance and

initiate work

determine

resource

requirements

create

service

orders

identify

outage scope

confirm

resource

availability

confirm

materials

create

material

orders

arrange

outage

release work

for execution

schedule

work

confirm

wayleaves

prepare

switching

schedule

work for

scheduling

resource

requirements

material

requirements

material

availabilityconfirmed

materials

confirmed

resource

work

scopeoutage

scope

confirmed

acquisitions

confirmed

acquisitions

work for

scheduling

to-be asset

data

outage

request

confirmed

outage

outage

details

scheduled work

switching

schedule

scheduled

work

resource

requirements

activity4.4.2 schedule (connection) resources

Business Process Automation Concept

project manager

plan EHV outages

prepare asset data

acquire rights and

properties

4.4.3 execute

(connection)

work

4.4.1 receive

acceptance and

initiate work

determine

resource

requirements

create

service

orders

identify

outage scope

confirm

resource

availability

confirm

materials

create

material

orders

arrange

outage

release work

for execution

schedule

work

confirm

wayleaves

prepare

switching

schedule

work for

scheduling

resource

requirements

material

requirements

material

availabilityconfirmed

materials

confirmed

resource

work

scopeoutage

scope

confirmed

acquisitions

confirmed

acquisitions

work for

scheduling

to-be asset

data

outage

request

confirmed

outage

outage

details

scheduled work

switching

schedule

scheduled

work

resource

requirements

activity4.4.2 schedule (connection) resources

Business Process Automation Concept

project manager

plan EHV outages

prepare asset data

acquire rights and

properties

4.4.3 execute

(connection)

work

4.4.1 receive

acceptance and

initiate work

determine

resource

requirements

create

service

orders

identify

outage scope

confirm

resource

availability

confirm

materials

create

material

orders

arrange

outage

release work

for execution

schedule

work

confirm

wayleaves

prepare

switching

schedule

work for

scheduling

resource

requirements

material

requirements

material

availabilityconfirmed

materials

confirmed

resource

work

scopeoutage

scope

confirmed

acquisitions

confirmed

acquisitions

work for

scheduling

to-be asset

data

outage

request

confirmed

outage

outage

details

scheduled work

switching

schedule

scheduled

work

resource

requirements

activity4.4.2 schedule (connection) resources

Business Process Automation Concept

call centre

records co-ordinator

project manager

check PME

log incident and

update caller

dangerous PME

reading

add/amend asset data

with as-built detail

collate data for update

create/update

customer records

4.4.2 schedule

(connection)

resources

create/update asset

recordsasset data for

update

as-built asset

data

connection

registration

data

close

service

orders

complete

time sheets

reconcile

materials

do work on

site

submit

outage data

scheduled

work

to-be asset

dataoutages in

place

work complete

materials reconciled

timesheets completed

PME check

required

completed work

records

3.6 control network

outage data

(diagram patches

and switching

schedule)

liaison liaison

closed

orders

4.4.3 execute (connection) work activity

Next step:Information is your only real asset

• Make lists

• Physical assets that your organisation owns

• Systems that operate

• Business workflows that you must do well

• Make a Map

• Assets down the left

• Systems across the top

• At the intersection write the attributes that the system uses

• Allocate responsibility for one attribute to one business owner who owns the system

• Start to report data quality

• Ask the business which intersection they need to improve

31

Now you can think about CIM…

Eskom Information Architect

Elmarie Van Der Merwe: vdMerwEe@eskom.co.za

Eskom Integration centre

Kabelo Letlape: LetlapKT@eskom.co.za

33

Example Circuit as a Single Line Diagram

EnergyConsumer

Breaker

SynchronousMachine

GeneratingUnit

Breaker

BusbarSection

Breaker

ACLineSegment

Current measurement represented by

Measurement connected to Terminal

34

Representing a Power Transformer as CIM

Objects

• A power transformer is not mapped to a single CIM class– Represented by a number of components with a single

PowerTransformer container class

– Two-winding power transformer becomes two TransformerWinding objects within a PowerTransformer container

• If a tap changer is present to control one of the windings– An instance of the TapChanger class is associated

with that particular winding

– Also contained within the PowerTransformer instance

35

Transformer Class Diagram

Inherits from Equipment, since does not conduct

electricity

Physically connected to network and conducts

electricity, so inherits from ConductingEquipment

Part of TransformerWinding, not

separate piece of equipment

Shell of transformer, containing windings,

insulation, magnetic core, etc.

36

CIM Mapping for Transformer 17-33

• Transformer 17-33 is

represented as four CIM

objects

37

Transformer Model Diagram from

61970-301CIM Base

ConductingEquipment(from Core)

Equipment(from Core)

PowerSystemResource(from Core)

RegulationSchedule

TapChanger

0..1

0..n

+RegulationSchedule

0..1

+TapChangers

0..n

WindingTest

HeatExchanger

TransformerWinding

0..n

+TapChangers

0..n

+TransformerWinding

1

1

0..n

+From_TransformerWinding1

+From_WindingTests

1

0..n

+To_WindingTest

+To_TransformeWindings

0..n

PowerTransformer

0..1

1

+HeatExchanger0..1

+PowerTransformer 1

1..n

1

+Contains_TransformerWindings

+MemberOf_PowerTransformer

1

38

Transformer Winding Attributes

Transformer Winding

b: Susceptance insulationKV: VoltageconnectionType: WindingConnectionemergencyMVA : ApparentPowerg: Conductancegrounded: Boolean r: Resistance r0: Resistance ratedKV: Voltage rated MVA: ApparentPower rground: ResistanceshortTermMVA: ApparentPowerwindingType: WindingTypex: Reactancex0: Reactancexground: Reactance

39

Example Circuit with Full CIM Mappings

• Maps to

– 17 CIM classes

– 45 CIM objects

• Could be

extended further

with addition of

objects for

– control areas

– equipment

owners

– measurement

units

– generation and

load curves

– asset data

CIM

Just do it