Practical Uses of PI AF Matt Rivett Sr. OSI PI Developer PJM Interconnection Date Forum Name
Agenda About PJM PI AF Infrastructure AF Databases Generator AGC Synchrophasor Thunder Storm Alert Server Monitoring Conclusion 2
PJM Vision Statement To be the electric industry leader today and tomorrow in reliable operations, efficient wholesale markets, and infrastructure development. 3
Reliability Grid Operations Supply/Demand Balance Transmission monitoring 1 PJM Focus on Just 3 Things Regional Planning 15-Year Outlook 2 Market Operation Energy Capacity Ancillary Services 3 4
PJM as Part of the Eastern Interconnection 27% of generation in Eastern Interconnection 28% of load in Eastern Interconnection 20% of transmission assets in Eastern Interconnection KEY STATISTICS PJM member companies 900+ millions of people served 61 peak load in megawatts 165,492 MWs of generating capacity 183,604 miles of transmission lines 62,556 2013 GWh of annual energy 791,089 generation sources 1,376 square miles of territory 243,417 area served 13 states + DC externally facing tie lines 191 21% of U.S. GDP produced in PJM As of 4/1/2014 5
PJM Control Room Many video walls and dispatcher workstations Majority of displays are PI Process Book Dispatchers and engineers build their own PI displays Reviewed by IT PI Support for performance reasons but not data 6
PI AF Infrastructure at PJM SQL Replication SQL Cluster AF Collective AF Server Primary AF Clients PI Process Book PI Data Link & Power Pivot PI Coresight SQL Cluster AF Server Secondary PI System Explorer Custom AF SDK Code 7
Generator Database Purpose Determine which PI tags are the correct PI tags for a piece of equipment Updated each night to ensure the most accurate information Requirements Access to source system model (Oracle database) A strict PI tag naming convention Custom AF SDK coding 8
Generator Database Source 9
Generator Database Source 10
Generator Database Source (CIMSPY) 11
Generator Database Source (CIMSPY) 12
Generator Database PI AF Top Level PECO Hierarchy Limerick Unit 01 13
Source vs PI AF Each attribute of the generator is automatically assigned appropriate PI tag If there is no associated PI tag a placeholder tag is substituted which has a snapshot value of No Result 14
Generator Database Automation Written by PJM PI administrator / developer Kireet Dholareeya.Net using AF SDK Loads source CIM model from Oracle database Builds hierarchy of pools, companies, stations and voltage levels using AF templates Adds generators using templates based on their types AF templates use inheritance All generators must have specific attributes Wind units have additional attributes, etc 15
Generator Database Tools Element Relative Process Book Coresight Displays 16
Automatic Generation Control (AGC) Database Purpose Detect data quality issues between PJM s many redundant systems Replicates PJM s tie line report Source to build reports and send notifications Requirements Access to source system model Currently using manual XML exports A strict PI tag naming convention Custom AF SDK coding 17
AGC Database PI AF PI Tag lookup done to translate source system IDs into PI tag names Calculation attributes created to replicate existing EMS screens Additional alarm states Deviation calculations 18
AGC Database Process Book ERD Element Relative Shows values from 5 different PI Collectives Real-time telemetered, AGC, SE & backup data 19
AGC Database Notifications In testing phase: Might require AF 2014 to write AF formula results to PI tags Using Notification Template 20
AGC Database Notification Example Subject: AGC Tie Deviation Violation on FALCONER-WARREN Name: FAL-WAR / FALCONER-WARREN Time: AGC Value: 64.9941101074219 MW SE Value: 71.0193710327148 MW Deviation: 6.02526092529297 MW Limit: 5.75 MW 21
Synchrophasor Database Purpose Initially developed for PI tag creation Recently added power calculations to investigate data quality issues Requirements Source meta data Provided in excel sheets, manually entered into PI AF using PI system explorer Attention to detail 22
Synchrophasor Database Source Excel File 23
Synchrophasor Database Model Meta data is manually entered in PI AF Once it is verified PI AF is used to create the PI tags Additional steps are required to add PMUs to output stream of PDC (C37118) and RTDMS (DNP3) 24
Synchrophasor PMU Template (Partial) Example of substitution in STAT attribute allowing PI tag creation using PI AF \\%@tag configuration pi collective%\%@zone%_%@data Type%_%@Equipment Type%/%@B1B2B3%:stat;ptclassname=classic;pointtype=Int 32;descriptor="%@STN%";exdesc="%@STN%:stat";span=6 5536;pointsource="%@tag configuration pointsource%";scan="%@enabled%";excmax=1 ;excdev=0;step=1;compmax=1;compdev=0;compdevpercent= 0;excdevpercent=0;location1="%@tag configuration location1%";location2="%@tag configuration location2%";location3="%@tag configuration location3%";location4="%@tag configuration location4%";location5="%@idcode%";instrum enttag=pmu\stat 25
Synchrophasor Calculated Template Calculates the complex, reactive and real power values from current and voltage phasors 26
Synchrophasor Power Calculation Process Book Element Relative 27
Synchrophasor Power Calculation Coresight Element Relative When requesting long periods of time, high CPU usage on Coresight server. 28
Synchrophasor Power Pivot Example Pick zone and/or manufacturer to display if any PMUs are in error Also displays latency and frequency 29
Thunder Storm Alert Database Purpose Experimenting with AF 2014 and event frames Detect when thunder storm alert is active and capture an event frame Requirements Data in PI and model manually created 30
Thunder Storm Alert Database Template Simple start and end triggers based off digital PI tag 31
Thunder Storm Alert Database Events Events that have been captured 32
Thunder Storm Alert Coresight Display Easy way to visualize event frames Select event frame and the displays updates with the data from the event 33
Server Monitoring Database Purpose PI Administrators to monitor the PI servers at PJM Notifications Visualization Requirements Server performance monitor data Interface health points 34
Server Monitoring Database Minimal data entry required Uses substitution to create PI tags 35
Server Monitoring Coresight Display PI Server Element Relative 36
Server Monitoring Coresight Display Windows Server Element Relative 37
Conclusion OSIsoft has greatly improved the capabilities of PI AF over the last few years The PI client tools are now at a point where they can take advantage of PI AF Event frames have great potential now that they can be easily generated PI Coresight is a good tool but it needs to be more customizable in simple things like layout and colors 38