AM 2_CIM Implementation in a DSO company practical ... - CIMug
AM 2_CIM Implementation in a DSO company practical ... - CIMug
AM 2_CIM Implementation in a DSO company practical ... - CIMug
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
IEN 2013 © wszelkie prawa zastrzeżone www.ien.gda.pl e-mail: ien@ien.gda.pl<br />
<strong>CIM</strong> <strong>Implementation</strong> <strong>in</strong> a <strong>DSO</strong> <strong>company</strong> –<br />
<strong>practical</strong> experiences<br />
Aleksander Babś<br />
Institute of Power Eng<strong>in</strong>eer<strong>in</strong>g<br />
14.06.2013
<strong>CIM</strong> – 'why should I care?'<br />
<strong>CIM</strong> is not a solution to all typical problems:<br />
• It will not automagically <strong>in</strong>crease data quality<br />
• It will not create the miss<strong>in</strong>g network data<br />
• It will not provide data models for every bus<strong>in</strong>ess activity<br />
• It will not immediately save money<br />
But it can:<br />
• Take some time to implement<br />
• Make the <strong>in</strong>troduction of new systems easier<br />
• Prevent vendor lock-<strong>in</strong> and make disparate system 'talk'<br />
• Save some money <strong>in</strong> the long run<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
2
The fast start<br />
Success factors:<br />
• Select applications with good documentation<br />
• Take the bare m<strong>in</strong>imum for a proof of concept<br />
• Secure sufficient and competent resources<br />
• Co-operate with application vendors<br />
• Make <strong>CIM</strong> run parallel to the exist<strong>in</strong>g <strong>in</strong>terfaces<br />
• Plan for '<strong>CIM</strong> Only' scenario<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
3
Integration scope<br />
Common<br />
Data<br />
Repository<br />
<strong>CIM</strong> selected<br />
<strong>CIM</strong> considered<br />
SCADA + DMS<br />
Asset<br />
management +<br />
GIS<br />
<strong>AM</strong>I<br />
Network<br />
analysis<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
4
Application analysis<br />
<strong>CIM</strong> – what version, what classes, what attributes<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
5
Application analysis<br />
'Low level' analysis:<br />
• Look at the database model and data – if available /<br />
accessible<br />
• Check export / import capabilities <strong>in</strong> any data formats<br />
• Do a complete 'GUI clickthrough'<br />
• Recreate topology fragments <strong>in</strong> <strong>CIM</strong>Phony as reference po<strong>in</strong>t<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
6
<strong>AM</strong>I –> Bill<strong>in</strong>g system <strong>in</strong>tegration<br />
Goal: expose energy usage measurements to bill<strong>in</strong>g applications<br />
• Data displayed and stored accord<strong>in</strong>g to the COSEM data model<br />
and correspond<strong>in</strong>g OBIS codes.<br />
• Object cod<strong>in</strong>g described <strong>in</strong> IEC 62056-61.<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
7
OBIS codes mapp<strong>in</strong>g<br />
OBIS – Object Identification System<br />
Example: Active Energy Import, A+<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
8
OBIS codes mapp<strong>in</strong>g<br />
1-0:1.8.1.255 0.26.0.1.1.1.12.0.0.1.0.0.128.3.72.0<br />
OBIS code<br />
<strong>CIM</strong> - Read<strong>in</strong>gType<br />
Measurement: Active Energy Import, A+<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
9
<strong>AM</strong>I -> SCADA basic <strong>in</strong>tegration<br />
Goal: make SCADA LV aware of the events monitored by <strong>AM</strong>I<br />
0-0:96.11.5.255<br />
Event ID 93<br />
OBIS code<br />
3.26.126.85<br />
<strong>CIM</strong> - EndDeviceEventType<br />
Event: Phase outage<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
10
Perspective <strong>CIM</strong> usage areas<br />
www.ien.gda.pl<br />
e-mail: ien@ien.gda.pl<br />
11
IEN 2013 © wszelkie prawa zastrzeżone www.ien.gda.pl e-mail: ien@ien.gda.pl