Download CIM for Enterprise Integration – Elektro Maribor case

We do IT in power
CIM for Enterprise
Integration – Elektro
Maribor case
Ljubljana
Friday, 14 June 2013
1
Introduction
• Overview:
Introduction
Why integrate?
What to integrate?
How to integrate?
Some implementaion examples
2
Introduction
• GDB, d.o.o:
•
•
•
•
•
•
Power engineering company
SCADA/DMS
Outage Management
AMI
WEB SCADA
CIM Integration Platform
• Elektro Maribor:
•
•
•
•
•
Electrical power distribution company
Cca. 220000 customers
20 Substations
110, 35, 20, 10, and 0,4 kV network levels
SCADA/DMS, Asset Management system (AM), AMI, GIS, Trouble Call
Management and other IT systems
3
Reasons for IT integration
• Same attributes are often present across various IT
systems/databases
 Data is not in sync across those systems
 Keeping data in order requires huge amount of “manual” work
 Administrating data manually requires area of expertise that
exceeds the neccessary requirements
• Data is source dependant
 IT system can only access those data that are provided directly
 Acquired data is not distributed to all systems that may want to
use it
4
Why CIM?
• Defined by open standards
 IEC 61970
 IEC 61968
• Interoperability
• Model Driven Architecture concept – MDA
 Transformation from PSM to PIM and back
• Service oriented Arhitecture concept – SOA
• Set of classes/attributes is updated & expanded on regular
basis
• Smart grid ready
5
Why CIM?
P2P integration
Iintegration
based
method
on CIM platform
IS 2
ISIS11
IS 6
IS 6
IS 2
Integration platform
IS 5
ISIS33
IS 4
IS 4
6
Integrated systems - SCADA/DMS
• Core IT system for control centres consists of the following
modules:




Data acquisition and control
Power system device model & connectivity (HV & MV levels)
Load Flow calculation subsystem and its derivative functionalities
Outage management subsystem
• Databases:
 Oracle relational database
 Process, vendor specific database (GE)
• Public APIs:
 Any Oracle supported API - used JDBC for Java
 Vendor specific APIs – DSI, DAP, ALM and others, which can be
accessed through C/C++ calls and callbacks using SO libraries
7
Integrated systems – GIS & AM
• Asset Management (AM)with GIS:




Asset data
Power system device model (MV and LV levels) in AM
Connectivity (MV and LV levels) in GIS
AM in GIS were already integrated for the functionalities that we needed
so we consider them as 1 IT system
• Database
 DB2 relational database
• Public APIs
 Any DB2 supported API - used JDBC for Java
8
Proposed
architecture
CIM Integracijska
platforma
AM/GIS (DB2)
SCADA/DMS (Oracle)
Oracle API
DSI, DAP, ALM APIs
Oracle API
JDBC
JNI
JDBC
Java server/client
Java server/client
Messaging in queuing system (JMS)
Open ESB (Glassfish)
GDA Client
HSDA Client
SOAP
Hardware – physical servers
GDA Server
HSDA Server
Basic CIM platform
CIM Services (WCF)
Existing IT systems
Additional services
Interfaces, middleware, protocols, frameworks
Integration bus
CIM database (Oracle)
CIM Server
9
Implemented
architecture
CIM Integracijska
platforma
AM/GIS (DB2)
SCADA/DMS (Oracle)
Oracle API
DSI, DAP, ALM APIs
Oracle API
JDBC
JNI
JDBC
Java server/client
Java server/client
Messaging in queuing system (JMS)
Open ESB (Glassfish)
GDA Client
HSDA Client
SOAP
Hardware – physical servers
GDA Server
HSDA Server
Basic CIM platform
CIM Services (WCF)
Existing IT systems
Additional services
Public interfaces and middleware
Integration bus
CIM database (Oracle)
CIM Server
10
Used technologies
• Basic CIM platform:
 Database: Oracle
 CIM services: WCF and .NET
 Web services using SOAP protocol
• CIM integration bus




ESB: Glassfish open ESB
Messageing and Queuing System: JMS
Messageing clients: Java
Data transformation: Business Process Execution Language (BPEL)
• API access
 JDBC – Java Database Connection
 JNI – Java Native interface (to communicate with C/C++)
11
Project schedule
• Basic CIM platform was already developed before the start of
Elektro Maribor project as well as some parts of CIM integration
bus
• Integration arhitecture:
 Finalizing CIM integration bus implementation
 Development and implementation of JMS clients and API servers for
purposes of communication with CIM
• SCADA/DMS integration:
 Finalizing JMS clients with functionalities of data exchange coordination
and API communication
 Data transformation and mapping was inplemented as a part of CIM
integration bus using Business Process Execution Language (BPEL)
• AM integration
 Some reconstructions of JMS client according to the nature of AM
 Logic for matching object from AM to an object in SCADA/DMS (now CIM)
12
Implementation – coupling AM and CIM objects
• Automatic binding:
 Defining common patterns in equivalent objects (names, descriptions,
topoligy points)
 Filtering by equipment containers
 Implemented in JMS client / API server
 Once the match is found, a link between AM and CIM objects is
permanently established using cim:Name class
• Manual binding:
 Changing objects’attributes in either of the two integrated IT systems
in order to comply with the logic of seeking common patterns
 Manually adding a related cim:Name object to existing
cim:IdentifiedObject
13
Implementation – WEB Editor
14
Implementation – data transformation
• Implemented as a separate
module inside open ESB
• Business Process Execution
Laguage (BPEL)
• Block diagrams instead of ifelse, switch-case clauses
• Provides an effective
method of transforming
additional objects and
attributes if neccessary
• Integrating additional IT
systems is easier
15
Implementation – data transformation
• SCADA/DMS:
• Equipment containers: region, subregion, substation, bay, voltage level
• Devices on HV level: energy source, switch, overhead line, transformer
• Devices on MV level: switch, transformer station, overhead line, underground
cable, bus
• Device topology
• SCADA points values
• AM:
• Equipment containers: substation, bay, voltage level
• Devices on MV level: switch, transformer station, overhead line, underground
cable
• Devices on LV level: switch, overhead line, underground cable, energy
consumer
• Device topology
16
What did we achieve?
• Effective integration of SADA/DMS and AM:
 There is much less discrepancy between equivalent objects in both
systems as data automatically flows from one system to antoher
 Much less manual administrative work
 Economical, technological and organizational benefits
• Union of data, found in both system serves as a solid basis
for:
 New functionalities
 Reporting services
 Eventual expansions integration of additional IT systems
17
WEB Reporting
18
Thank you for your attention
GDB d.o.o.
Tehnološki park 24
1000 Ljubljana
Slovenija
[email protected]
www.gdb.si
19