Post on 18-Dec-2015
Geographical Visualisation of CIM networks using Google
APIs
Alan McMorran
Network Topologies
• Common Power System Model (CPSM) CIM data contains topological data at a node-breaker level
• IEC 61970-301 does not natively support the embedding of single-line diagram layout or geographical position data
CDPSM
• The Common Distribution Power System Model (CDPSM) extends the CPSM and incorporates IEC 61968 classes for geographical data
• The Location and GmlPosition (formerly CoordinatePair) allows the geographical location of equipment to be embedded within the model
CDPSM
• The Location class has a 0..n association with Power System Resource
• For CDPSM the container classes, Substation and Line, have a corresponding Geographical Location
Location•locationType•locationCode•polygonFlag
GmlPosition•xPosition•yPosition•zPosition•sequenceNumber
PowerSystem Resource
Equipment
EquipmentContainer
SubstationLine
Google Maps
• Web based map and aerial imagery viewer
• Google provides a powerful API that is free to use for building non-commercial applications (pricing starts at $10k/year for Google Maps for Enterprise for intranet applications)
• Using Google Maps API, Canvas API, some custom Javascript libraries and back-end server processing, network layouts can be overlayed onto the map
Basic Embedding
• The simplest form of geographical embedding is single coordinates for substations
• Combining this with the network topology information within the CIM XML file allows a simple network diagram to be constructed
Basic Embedding
• EDF Aiguebelle network in the Alps
• Example of a LV distribution network
• Each marker represents a substation
• No line routing data
Enhancing the View
• Since the CIM data contains the electrical model, voltages can be easily extracted
• This in turn can be used to add colour to denote voltage to lines and substations
• Substation icons are drawn to represent the different voltages within a substation
Transmission Level
• The same process can be applied to Transmission networks
• A CIM electrical model of the Scottish Power network was taken from their EMS
• Geographical data was taken from their asset database, converted from UK Grid coordinates to Latitude and Longitude and embedded within the CIM XML file
Scottish Power
Line Routing Data
• CDPSM supports multiple coordinates for each location
• A sequencePosition denotes the order each coordinate should be drawn in
• This allows line routing data to be embedded along with the substation location data
Embedding Other Data
• Viewable data not limited to colours to denote voltage
• Simple to add additional data to the map depending on requirements
• Asset data extracted from SP Asset database integrated with EMS model
• Viewable through Google Maps interface
Embedding Asset Data
Enhancing View
• Additional data can be incorporated using the same interface
• Anything that can have a Location associated can be plotted on the map
• Anything associated with a Substation can be embedded in the marker details window
Aerial View
• As well as the map view Google Maps has aerial imagery
• Shows the accuracy of the data after conversion from UK Grid to Latitude and Longitude Scottish Power Charlotte Street 275/33kV
SubstationGlasgow, UK
Google Earth
• Full 3D model of the Earth with overlay of aerial and satellite imagery
• Google Earth allows overlay of data in a similar manner to Google Map
• Data is encoded in Keyhole Markup Language (KML), an XML schema
Google Earth Demo
Telemetry Processor
• Software developed using AI techniques by team within the University in conjunction with SP
• Processes SCADA data and classifies incidents using an expert system derived from protection engineers’ expertise
• Allows engineers to quickly identify and rectify faults on the network
• Resulting data put into custom MySQL database schema
Telemetry Processor
Telemetry Processor
Telemetry Processor
• Existing interface lists incidents and the corresponding events
• Suitable for viewing a list of incidents but difficult to identify clusters either temporally or spatially
• Raw data is from SCADA• No link with data from other systems (e.g. EMS, GIS, Asset, Work Management etc.)
• The CIM provides an avenue for both utilising other data in the existing processor and linking its results to other systems and applications
CIM Messaging
• Telemetry Processor results can be mapped to CIM and a corresponding message schema created
ActivityRecord
•Name•Description•Status•statusDateTime
Message NetworkActivity
FailureEvent
IncidentRecord
PowerSystemResource
Equipment
EquipmentContainer
Substation
ActivityRecord
•Name•Description•Status•statusDateTime
PowerSystemResource
0..n
0..n
0..n 0..n 0..n
CIM Messaging
• A client application polls the server for any events on the network in last x seconds and server returns resulting XML message
• Server-side data is generated from dynamic CIM model containing EMS/DMS, Location, SCADA and Telemetry Processor data in CIM format
Client Side
• Client side browser generates a network map from the CDPSM compliant (or enhanced CPSM) data on the server
• To highlights faults on the network, the incident’s substation and/or line identifier is included in the message payload
• The CIM message’s substation and/or line references are consistent with those used to generate the map view
Geographical Highlighting
• The event in each message is highlighted on the map
• The user can quickly identify clusters of faults
• Icons can be colour coded according to fault type
Temporal Tracking
• As well as showing the location a fault takes place it is useful to show how events relate to each other in the time-domain
• Timeline is a DHTML/Javascript widget developed by the SIMILE project at MIT for viewing time-based information
• A Javascript library decodes the CIM messages and uses the data to simultaneously plot the location on the map and on this Timeline
Temporal Tracking
• Multiple bands have different Interval units (milliseconds, hours, days, weeks and months)
• Timeline updated along with map as new events are received and processed
• Can be used to show real-time and historical network activity
Timeline Demos
EdF Aiguebelle
Scottish Power
Problems Encountered
• No consistent identifiers between EMS, Asset and SCADA data at SP
• Manual data cleansing and mapping was required in a number of cases
• Multiple coordinate systems must be converted for use with Google Maps (Lambert I-IV, UK Ordnance Survey, Latitude/Longitude)
• Performance issues in Google Maps with large complex distribution networks
Future Avenues
• Overlay of additional data including load demand & generation capacity
• Enhancing incident reports by using the combined electrical and geographical model (e.g. working out line fault locations from impedance)
• Remote access via palm-tops and sub-notebooks for on-site engineers
Questions?
• For more information and a demo of the Mercury software go to:–http://cimphony.org