Getting started with CIM

Getting started with CIM
Lessons learned from a CIM POC
2 June 2016
Sander Jansen
Alliander digital grid department
Philip Jones
Xtensible - Solution Development
Digital grid department: IT/OT integration
• Architecture
• Servicedesk
• Projects
• Maintain systems
• Innovation (Livelab)
• Analytics
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
2
Alliander Situation
Situation
There are a lot of questions about the meaning of the data (e.g.
analysts) and long duration of projects due to the lack of
understanding the used semantics.
Complication
Alliander’s ambition is to become a data driven utility, to become
more efficient in operation and help the energy transition. Clear
understanding of semantics is needed for integration, flexibility and
market conformity.
Question
How do we get started with IEC CIM to overcome this challenges?
Answer
Learn to apply and use IEC CIM in a proof of concept with help of an
external consultant.
External consultancy:
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
3
Digital grids architectural vision
Information products
• Middle-out architecture
?
• Loosely coupled architecture with
canonical interfaces
• Standardized semantics through the
use of a “common model”
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
?
?
?
?
Information
services
Asset & Data
4
CIM POC Context: Manual Integration
Separate applications/GUI’s for
• Outage location calculation
• Short-circuit detection (iHost)
• GIS system topology
• Digging events
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
5
Historian
Ihost
Trace service
Herb demo app
Used MD3i steps starting with business modelling
Generate
map
Select
outage
Show
results
Trace
service
Ihost
Historian
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
Simplified
6
Sequence diagrams & Model existing interfaces
class iHost Interface Model
sd sd POC-002: Return Ev ent Data
(from Physical
Actors)
(from Physical
Actors)
(from Physical
Actors)
HERB Outage Engine
iHost-CIM
iHost
BinaryInput
BinaryInputEv ent
RtuUserData
-
Request Shortcircuit Event
(GetEventRequest)
Convert CIM GETOutage to iHost
Request()
RtuId: int
SiteName: string
UserData1: string
UserData2: string
UserData3: string
UserData4: string
UserData5: string
UserData6: string
+RtuUserData
0..*
-
Alarmed: boolean
+PointId
AlarmText: string
Name: string
0..*
Name2: string
PointId: unsigned integer
RtuId: unsigned integer
StatusText: string
Timestamp: date
+BinaryInput
+PointId
0..* 0..*
Alarmed: boolean
EventId: int
PointId: int
RtuId: int
Timestamp: int
+BinaryInputEvent
0..*
iHost Retrieve Event()
+RtuId
iHost Reply Events()
+RtuId
Convert iHost Reply
to CIM
EventResponse()
0..1
Request Shortcircuit Event(Events
(GetEventResponse))
0..1
Rtu
-
+RtuId
RtuId: unsigned integer 0..1
Name:
Author:
Version:
Created:
Updated:
iHost Interface Model
AL10129
1.0
14-10-2015 0:00:00
27-1-2016 0:00:00
3 calls
needed
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
7
Start mapping to IEC CIM
iHost resource
CIM
Rtu.RtuId
EndDevice.mRID
BinaryInputEvent.EventId
EndDeviceEvent.mRID
BinaryInputEvent.Timestamp
EndDeviceEvent.createdDateTime
BinaryInputEvent.Alarmed
RtuUserData.SiteName
RtuUserData.UserData2
Remark
EndDeviceEvent.status.value
EndDeviceEvent.status is a complex
type whereStatus.value is set to
True/False.
EndDeviceEventType
EnDeviceEventType =
"ShortCircuitEvent" (default)
SubStation.name
SubStation.mRID
GIS_behuizingsnummer
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
8
Build an CIM based message
class message_Ev ents
«md3i_S B _en..
Entities::Substation 1
«md3i_S B _en..
Entities::Bay
IdentifiedObject
1
0..1
0..*
«md3i_S B _enityt »
Entities::
CoordinateSystem
1
«md3i_S B _..
Entities::
Equipment
0..1
0..*
1
PowerSystemResource
«md3i_S B _enityt »
Entities::RemoteUnit 1
«md3i_S B _..
Entities::Location
0..1
1
0..*
«md3i_S B _enityt »
Entities::
PositionPoint
1
1
«md3i_S B _enityt »
Entities::EndDev ice
1
0..*
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
«md3i_S B _..
1
Entities::
EndDev iceEv ent
0..1
«md3i_S B _enityt »
Entities::
EndDev iceEv entType
Generate artifacts and build CIM POC
1. Model CIM message
2. Generate XSD
3. Generate Code
4. Finalize Code
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
10
ESM Modeling - MD3i
Reference
Reference
Model(s)
Model(s)
• Industry Standard Models
• Application Meta-Data
<<refine>>
Reference Base
Reference Base
Model(s)
Model(s)
<<refine>>
• Single, contiguous ESM
• Develop based on use case / project scope
• Gap analysis > Extend as needed
• Technology-specific model (e.g. XSD, DDL)
• Used to generate design artefacts
Semantic Model
(ESM)
<<realize>>
Implementation
Implementation
Model(s)
Model(s)
11
Model-Driven Design - MD3i
Design- & Development
Reference
Industry
Reference
Standards
Model(s)
Model(s)
Reference
Model
API
Model (ESM)
SM Context
Trfrm
Reference
Model
Implementation
Model(s)
Model(s)
Reference
Model
etc
Reference Model(s)
Gap analysis
Extension
Semantic Model
Implementation
Model (XSD)
XSD
WSDL
WSDL
WSDL
XSD
--XSD
-----------XSD
-----
Reference Base Model
Trfrm
Reference
Model
Implementation
Model (DDL)
Reference Base Model
Trfrm
XSD
CopyBook
Reference
Base
Model(s)
Reference
Base Model
Base
Model(s)
Run-Time
Service Design
Enterprise
Semantic Model (ESM)
- MD3i on Sparx EA
Semantic
Reference
Implementation
Business Vernacular
Application
Meta-Data
Process Design
Gap analysis
Extension
Reference Base Model
Trfrm
Gap analysis
Extension
Map & Develop
Test
Reference Base Model(s)
Semantic Model
Implementation
Model(s)
Run-time
Components
Demo Time
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
13
CIM POC Findings
We learned a lot:
• Business modelling is useful
• IEC CIM is big
• IEC CIM only is not enough: ESM
• Unclear semantics within Alliander
• Information identification is not unique
• Information is entered and stored redundantly in some cases
• Code generation for target technology (.net) has unique constraints
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
14
More CIM to come within Alliander!
CIM ready project
• Production capability for working with ESM/CIM
Technical integration infrastructure project
• Select technology to deploy CIM/ESM artifacts
Expand the CIM/ESM use project by project (with external support)
• Configuration management system project
• Real time data platform project
Related initiatives
• Openkonsequenz
• 61850/CIM gateway (M2M grids)
• Company wide discussion about semantics
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
15
Questions?
2 June 2016
CIMug 2016 Amsterdam - Getting started with CIM
16