Insert Company Logo / Transmission Operator or Balancing AuthorityData Request and Specifications forData Provision / Version1.0
TOP-003-3
APPLICABILITY:BalancingAuthorities,GenerationOwners,GenerationOperators,Load
ServingEntities,TransmissionOperators,TransmissionOwners, Interchange Authorities, Distribution Providers
I. Purpose
PursuanttoNERCReliabilityStandardTOP-003-3,theTransmission Operator (TOP) or Balancing Authority (BA)requests datafromyourentityasdetailedinAttachment1.Specifically,TOP-003-3R5requiresthat each BalancingAuthority,GenerationOwner,GenerationOperator,LoadServingEntity, TransmissionOperator,TransmissionOwner, Interchange Authority and Distribution ProviderprovideitsTOP or BAwiththeoperatingdatathatit requirestoperformoperationalreliabilityassessmentsandtocoordinatereliableoperations withintheTOP or BA Area.
II. Introduction
Thedatarequestedincludes,butisnotlimitedto,real-timefacilitydata,scheduletypedata, facilityoutageinformation,andelectricalequipmentmodelingdata.Thisdataisnecessaryfor theTOP or BAtocarry-outitsfunctions,asdefinedbytheNERCReliabilityStandards,including:
•Real-TimeMonitoring
•SystemAlarmsandVisualizations
•AdvancedApplicationsandotherNetworkAnalysisTools
•Future,NextDayandnearReal-TimeEngineeringStudyAnalysis
•PostAnalysis,EventAnalysis,Trends,Forecasts,etc.
III. ExchangeofInformation and Data
ContactInformation
Eachentitywhichisrequiredtoprovidedatadirectlytoinsert company nameshouldappointasinglecontact personwhoisresponsibleforworkingwiththe TOP orBAinordertoprovidetherequesteddatainthe specifiedformat.Pleasenotifyinsert company nameofyourentity’scontactname,emailaddressandphonenumberatinsert email.
DataFormat
TheformatsforthedatatobedeliveredtotheTOP or BAareasfollows:
Inter Control Center Protocol Data (ICCP)
•RealtimeAnalogandStatuspointdataasdetailedinAttachment1.
•Thedataprovidermustincludedataqualityalongwiththedata.Thisdataqualityshall followtheICCPDataQualityStandardsasdescribedintheIECICCPUser’sGuide (870-6-505).Ifreal-timeICCPdatatransferisunavailableforanyreason,theresponsibleentitywill providecriticalreal-timesystemdataviaphonetotheTOP or BA’s real-timedesk.
ElectricIndustryDataExchange(EIDE)
•Scheduletypedataas identifiedinAttachment1 tobedeliveredelectronicallyonadaily basisasdesignatedinAttachment1,byEIDEprotocoloverhttps.
•If yourentityisunabletoperformEIDEoverhttps,thentheEIDEformattedfilescanbe deliveredtoaCompany nameSecureFileTransportProtocol(SFTP)site.
Company name’sEMStechnicalstaffwillworkwitheachentity’stechnicalstaffoneitherICCP or EIDE implementation.
Peak RC Coordinated Outage System(COS)
•Thiscentraloutagesystemhasawebfrontendforeasydataentry.Submissionscan beautomatedviaaWebServicesAPIbyworkingdirectlywiththesystemvendor.
•PlannedFacilityOutageinformationshouldincludetransmissionequipmentand generators.ThedetailsoftherequiredplannedoutagesubmittalsareintheCOSUser’s ManualsuppliedbyPeakRC.
•IfCOSisunavailable,theresponsibleentityshallsendplannedoutageinformationto
TopologyUpdate Processfor the West-wide System Model (WSM)
•TheWSMtopologyupdateswillbeprovidedthroughtheRCModelUpdateProcess.
ModelupdatesdetailsareinAttachment1belowandarerequirednolessthan30days priortotheactualchangeinthenetwork(additions,deletionsorchangesinenergized equipment).
Otherdataformatsandsubmittalprocessesincludetheuseofemail,uploadtoPeak’ssecure websitePeakrc.org,andphonecallstoinsert company nameOperators.
Questions
Insert company name’sengineeringandoperationsstaffwillworkwitheachentitytoanswer questions,requestsforclarificationortoaddressissuesrelatedtothetechnicalnatureofthedata.Pleasenotifyinsert emailwithyourquestionsabouttheTOP or BAdatarequest.
ithanyquestionsofalegalnature.
Effective date: January 1, 2017Page 1 of 29
Insert Company NameInsert Company Logo / Transmission Operator or Balancing AuthorityData Request and Specifications forData Provision / Version1.0
TOP-003-3
Attachment 1:
Thetablebelowcontainsthespecificdatainsert company namerequiresfromeachResponsibleParty. IndividualTOPsandGOPsarerequiredtoensuretheirdataisbeingprovidedeitherdirectlyor throughtheirassociatedBA.
1. Real-TimeNetworkMeasurementData
Req # / Responsible Party*See Note 1 / Data Request Effective Date / Data Source
Type / Data Item / Data Transfer Method / Data Update Frequency / Applicability
1.1 / Transmission Operator* / 4/1/2017 / Transmission / Real-time status pointsfor all
BES equipmentand other non-BES equipmentthat impactthe BES (see note 1). / ICCP / By exception / All
Adjacent
Shared facility
N/A
1.2 / Transmission Operator* / 4/1/2017 / Transmission / Real-time MWmeasurements or ampere ifMWnotavailable for all BES equipmentand other non-BESequipment thatimpactstheBES (see note 1). / ICCP / 10 sec
1.3 / Transmission Operator* / 4/1/2017 / Transmission / Real-time MVAR measurementsfor all BES equipmentandother non- BES equipmentthatimpact the BES (see note 1). / ICCP / 10 sec
1.4 / Transmission Operator* / 4/1/2017 / Transmission / Voltage measurementsfor all busses associatedwith BES equipmentandother busses associated non-BES equipmentthatimpactthe BES (see note1). / ICCP / 10 sec
1.5 / Transmission Operator* / 4/1/2017 / Transmission / Designated WECC Transfer Path data andstability related interface data:
•SOL (including dynamic limits) actual MW
•scheduled MWas applicable
•actual MW / ICCP / 10 sec
1.6 / Transmission Operator* / 4/1/2017 / Transmission / LTC tap position measurementsfor LTCs with high side voltage > 100kV. / ICCP / 10 sec
1.7 / Transmission Operator* / 4/1/2017 / Transmission / Phase shifter phase tap position. / ICCP / 10 sec
1.8 / Transmission Operator* / 4/1/2017 / Transmission / MW/MVAR measurements for measured loads. These loads may be equivalent representations ofyour distribution system. / ICCP / 10 sec
1.9 / Transmission Operator* / 4/1/2017 / Transmission / RAS Arming Status for all schemes that have an impactto the BES. An armed RAS implies thatitis 1) in service and 2) readyto perform an action (trip a unitfor example) ifa specific condition occurs on the power system. / ICCP / 10 sec
1.10 / Transmission Operator* / 4/1/2017 / Transmission / RAS in-servicestatus for all schemes that have an impactto the BES.
ICCP is the desired communicationmethod,if available. Phone call notifying that RAS is outof service (or returned to service) is required ifICCP notavailable. / ICCP or phone call to the RC upon change to RAS in- service status. / 10 sec
1.11 / Transmission Operator* / 4/1/2017 / Transmission / RAS associated analog arming values (e.g.Amp, MW,MVAR). (See note2 for example) / ICCP / 10 sec
1.12 / Transmission Operator* / 4/1/2017 / Transmission / Status ofNon-RAS devices thatperform automatic post-contingencyactions based on certain parameters such as under voltage or overloaded facilities. This mayinclude, butis notlimited to,certain generator run-back schemes or under voltage facilitytrippingschemes.
This is nota requestfor under-voltageor under- frequencyloadshedding information. / ICCP preferred. Ifnone available, phone call to RC upon status change. / 10 sec
1.13 / Transmission Operator* / 4/1/2017 / Operations
Data / Dynamicequipment ratings including all facilitieswith ratings thatvary with real- time system or ambientconditions (temp driven Facility Ratings,Topology driven Facility Ratings). / ICCP (if available) / 10 sec
2. Real-TimeBalancingAuthorityData
Req # / Responsible Party*See Note 1 / Data Request Effective Date / Data Source
Type / Data Item / Data Transfer Method / Data Update Frequency / Applicability
2.1 / Balancing Authority / 4/1/2017 / BA / InstantaneousBA Area Load
(See note5 for definition of BA Area
Load) / ICCP / 10 sec
2.2 / Balancing Authority / 4/1/2017 / BA / BA NetActual Interchange (asused in ACE calculation) / ICCP / 10 sec
2.3 / Balancing Authority / 4/1/2017 / BA / BA NetScheduled interchange (as used in ACE calculation) / ICCP / 10 sec
2.4 / Balancing Authority / 4/1/2017 / BA / BA Instantaneous ACE that is used
to satisfyCPSand DCS requirements. / ICCP / 10 sec
2.5 / Balancing Authority / 4/1/2017 / BA / BAAL high andlowlimits – one minute average values.This applies onlyto those entities thatare participating inthe Reliability Based Control (RBC) field trial. / ICCP / 1 min
2.6 / Balancing Authority / 4/1/2017 / BA / System frequency atmultiple locationswithinthe BA as requested bythe RC. / ICCP / 10 sec
2.7 / Balancing Authority / 4/1/2017 / BA / BA Scheduled frequency / ICCP / 10 sec
2.8 / Balancing Authority / 4/1/2017 / BA / BA Area Operating Reserve (as defined byNERC)
•Required
•Actual available / ICCP / 10 sec
2.9 / Balancing Authority / 4/1/2017 / BA / BA Area Operating Reserve - Spinning (as defined byNERC)
•Required
•Actual available / ICCP / 10 sec
2.9.1 / Balancing Authority / TBD / BA / BA Area ContingencyReserve (as
defined in the NERC glossaryand
WECC regional standards)
•Required
•Actual available
This itemwill replace 2.9 on the effective date. / ICCP / 10 sec
2.10 / Balancing Authority / 4/1/2017 / BA / BA Area ActualGeneration Total / ICCP / 10 sec
2.11 / Balancing Authority / 4/1/2017 / BA / Actual mostsevere single contingency(MSSC) ofyour balancing authority. This value should notbe a static Pmax ofthe largestgenerator,rather the actual MWoutput. This is NOTa request for the RSGMSSC. / ICCP / 10 sec
2.12 / Balancing Authority and Generator Operator / 4/1/2017 / Generator / Real-time status points (UCON status point designatingunit is or is notconnectedto the network)for units 10MWorgreater,or those units with automatic voltage control or black startcapability. / ICCP / By exception
2.13 / Balancing Authority / 4/1/2017 / Generator / All generators– real-time netMW output. / ICCP / 10 sec
2.14 / Balancing Authority / 4/1/2017 / Generator / All generators– real-time netMVAR output. / ICCP / 10 sec
2.15 / Balancing Authority / 4/1/2017 / Dynamic Transfer / Dynamic Schedule real-time dynamic signal used inACE calculation for each dynamicschedule. This is not the anticipated energy on the tag, rather a real-time calculation ofMWs associatedwith the dynamic schedule. / ICCP / 10 sec
2.16 / Balancing Authority / 4/1/2017 / Dynamic Transfer / Pseudo Tie real-time dynamicsignal. This is a real-time calculation of MWs associatedwith each pseudo tie used in ACE calculation.
Note:This is notan alternatemethod for inclusion in congestion management procedures pursuantto INT-004-3. / ICCP / 10 sec
2.17 / Balancing Authority / 4/1/2017 / Operations Data / Balancing Authoritytotalwind MW output. This isa single value– summation ofallwind generation currentlyonline. This value should representwindgeneration atthe bulk electric systemlevel. / ICCP / 10 sec
2.18 / Balancing Authority / 4/1/2017 / Operations Data / Balancing Authoritytotal solarMW output. This isa single value– summation ofall solargeneration currentlyonline. This value should representsolargeneration atthe bulk electric system level,notroof top solar for example. / ICCP / 10 sec
2.19 / Generator Operator / 4/1/2017 / BA / Change in status ofgenerating unit
Automatic Voltage Regulators(AVR), Power SystemStabilizers (PSS) or alternative voltage controlling device. / Phone call to RC Desk / Each occurrence lasting for 30 minutes or longer
2.20 / Balancing Authority / 4/1/2017 / BA / ATEC componentofACE / ICCP / 10 sec
2.21 / Balancing Authority / 4/1/2017 / BA / BA frequency bias ifa dynamic bias is used / ICCP / 10 sec
2.22 / Balancing Authority / 4/1/2017 / BA / Meter Error componentofACE / ICCP / 10 sec
3. ForecastData
Req # / Responsible Party*See Note 1 / Data Request Effective Date / Data Source Type / Data Item / Data Transfer Method / Data Update Frequency / Applicability
3.1 / Balancing Authority* / 4/1/2017 / BA / HourlyBA NetArea Interchange forecastthrough the end ofthe next business day. / EIDE/ Secure FTP / Daily submission by 10AM Pacific Prevailing Time.
3.2 / Balancing Authority* / 4/1/2017 / BA / HourlyOperating Reserve forecast ofBA Area through the end ofthe nextbusinessday. / EIDE/ Secure FTP / Daily submission by 10AM Pacific Prevailing Time.
3.3 / Balancing Authority* / 4/1/2017 / BA / HourlySpinning Reserve forecast ofBA Area for each day up toand including the next business day. / EIDE/ Secure FTP / Daily submission by 10AM Pacific Prevailing Time.
3.3.1 / Balancing Authority* / TBD / BA / HourlyContingencyReserve forecastofBA Area for eachday up to and including the nextbusiness day.
This itemwill replace 3.3 after the effective date. / EIDE/ Secure FTP / Daily submission by 10AM Pacific PrevailingTime.
3.4.1 / Balancing Authority* / 4/1/2017 / BA / HourlyBA Area load forecast. Required each dayfor the current daythrough the nextfourbusiness days.
(See note5 for examples ofload forecastsubmission) / EIDE/ Secure FTP / Daily submission by 10AM Pacific Prevailing Time.
3.4.2 / Balancing Authority* / 4/1/2017 / BA / HourlyBA Area load forecast. Required each hourfor the next4 hours.
(See note5 for examples ofload forecastsubmission) / EIDE/ Secure FTP / Hourly submissionreceived 10 min prior to the hour.
3.5 / Balancing Authority* / 4/1/2017 / BA / Hourly unitcommitmentfor all BA Area generation 50mwand above. Required for each dayup to and including the next business day. Forecasts mustbe submitted by 10AM Pacific Prevailing Time. / EIDE/ Secure FTP / Daily submission by 10AM Pacific Prevailing Time.
3.5.1 / Balancing Authority* / 4/1/2017 / BA / HourlyUnitCommitmentfor all BA Area generation thatqualifiesper the BES definition, includingany non-BES generation (asdetermined by the TOP or BAPeak), thatarenecessaryto support the accuracy ofOperational Planning Analyses and to determine SOLexceedance on BES Facilities.Required each day for the currentdaythrough the next fourbusiness days.
This itemwill replace item 3.5after the effective date.
(See note6 for definitions of generator forecastdata submissions) / EIDE/ Secure FTP / Daily submission by 10AM Pacific Prevailing Time.
3.5.2 / Balancing Authority* / 4/1/2017 / BA / HourlyUnitCommitmentfor all BA Area generation thatqualifiesper the BES definition, includingany non-BES generation (asdetermined by the TOP or BAPeak), thatarenecessaryto support the accuracy ofOperational Planning Analyses and to determine SOLexceedance on BES Facilities.Required each hour for the nextfourhours.
(See note6 for definitions of generator forecastdata submissions) / EIDE/ Secure FTP / Hourly submission received 10 min prior to the hour.
3.6.1 / Balancing Authority* / 4/1/2017 / BA / HourlyUnitDispatch MWfor all BA Area generation thatqualifiesper the BES definition, includingany non-BES generation (asdetermined the TOP or BAPeak), thatare necessaryto supportthe accuracy ofOperational Planning Analyses and to determine SOL exceedance onBES Facilities. Required each dayfor the current daythrough the nextonebusiness day.
(See note6 for definitions of generator forecastdata submissions) / EIDE/ Secure FTP / Daily submission by 10AM Pacific Prevailing Time.
3.6.2 / Balancing Authority* / 4/1/2017 / BA / HourlyUnitDispatch MWfor all BA Area generation thatqualifiesper the BES definition, includingany non-BES generation (asdetermined by the TOP or BAPeak), thatarenecessaryto support the accuracy ofOperational Planning Analyses and to determine SOLexceedance on BES Facilities.Required each hour for the nextfourhours.
(See note6 for definitions of generator forecastdata submissions) / EIDE/ Secure FTP / Hourly submission received 10 min prior to the hour.
3.7.1 / Balancing Authority* / 4/1/2017 / BA / HourlyOperational MaximumMW for all BA Areageneration that qualifies per the BES definition, includingany non-BES generation (as determined bythe TOP or BAPeak), thatare necessaryto supportthe accuracy ofOperationalPlanning Analyses and to determine SOL exceedance on BES Facilities.Required each dayfor the currentdaythrough the nextfourbusiness days.
(See note6 for definitions of generator forecastdata submissions) / EIDE/ Secure FTP / Daily submission by 10AM Pacific Prevailing Time.
3.7.2 / Balancing Authority* / 4/1/2017 / BA / HourlyOperational MaximumMW for all BA Areageneration that qualifies per the BES definition, includingany non-BES generation (as determined bythe TOP or BAPeak), thatare necessaryto supportthe accuracy ofOperationalPlanning Analyses and to determine SOL exceedance on BES Facilities.Required each hourfor the nextfourhours.
(See note6 for definitions of generator forecastdata submissions) / EIDE/ Secure FTP / Hourly submission received 10 min prior to the hour.
3.8.1 / Balancing Authority* / 4/1/2017 / BA / HourlyOperational Minimum MW for all BA Areageneration that qualifies per the BES definition, includingany non-BES generation (as determined bythe TOP or BAPeak), thatare necessaryto supportthe accuracy ofOperational Planning Analyses and to determine SOL exceedance on BES Facilities.Required each dayfor the currentdaythrough the nextfourbusiness days.
(See note6 for definitions of generator forecastdata submissions) / EIDE/ Secure FTP / Daily submission by 10AM Pacific Prevailing Time.
3.8.2 / Balancing Authority* / 4/1/2017 / BA / HourlyOperational Minimum MW for all BA Areageneration that qualifies per the BES definition, includingany non-BES generation (as determined bythe TOP or BAPeak), thatare necessaryto supportthe accuracy ofOperationalPlanning Analyses and to determine SOL exceedance on BES Facilities.Required each hourfor the nextfourhours.
(See note6 for definitions of generator forecastdata submissions) / EIDE/ Secure FTP / Hourly submission received 10 min prior to the hour.
4. DocumentationandProcedures
Req # / Responsible Party*See Note 1 / Data Request Effective Date / Data Source Type / Data Item / Data Transfer Method / Data Update Frequency / Applicability
4.1 / Balancing Authority and Transmission Operator / 4/1/2017 / Operations / EmergencyOperations Plans (limited to those affecting the BES) / Upload to secure folder in Peak website or Email / Annually and/or anytime the plan is updated.
4.2 / Balancing Authority / 4/1/2017 / Operations / Capacity and EnergyEmergency Plans / Upload to secure folder in Peak website or Email / Anytime the plan is updated.
4.3 / Transmission Operator / 4/1/2017 / Operations / Restoration Plans / Upload to secure folder in Peak website or Email / Annually and/or anytime the plan is updated
4.4 / Transmission Operator / 4/1/2017 / Operations / Under voltageand under frequencyloadshed plans / Upload to secure folder in Peak website or Email / Anytime the plan is
updated
4.5 / Transmission Operator / 4/1/2017 / Operations / Path procedures / Upload to secure folder in Peak website or Email / Anytime the plan is
updated
4.6 / Transmission Operator / 4/1/2017 / Operations / Geomagnetic Disturbance Operating Procedures / Upload to secure folder in Peak website or Email / Anytime the plan is
updated
4.7 / Balancing Authority and Transmission Operator / 4/1/2017 / Operations / Other procedures as appropriate or as requested by the TOP or BA, including documented mitigation plans, fire/weather protocols, regulatory protocols that could cause inability to follow directives, technical information concerning protective relays, voltage schedules. / Upload to secure folder in Peak website or Email / Anytime the plan is
updated
5. ScheduledandForcedOutageInformation
Req # / Responsible Party*See Note 1 / Data Request Effective Date / Data Source Type / Data Item / Data Transfer Method / Data Update Frequency / Applicability
5.1 / Transmission Operator* / 4/1/2017 / Planned Outage Data / Scheduled outages for BES transmission system elements or any non-BES transmissionelements (as determined by eitherthe TOP or by Peak) thatarenecessaryto support the accuracy ofOperational Planning Analyses and to determine SOL exceedance onBES Facilities. Planned transmissionoutages are to be submitted to COS by10AM Pacific Prevailing Time fourbusinessdays prior to the startofthe scheduled outage.
Plannedoutages thatare not submitted to COS by10AM Pacific Prevailing Time fourbusinessdays prior to the startofthe scheduled outagewill beconsidered late.
The start/end time/date ofplanned outages maybe adjusted in COS after initial submission;however,planned outages beginning the next business dayshould be final (for operations planning purposes) accordingto the following:
- The start date ofa planned outage shouldbe final by
- 8AM Pacific Prevailing Time one business day prior to the
- Startofthe outage.
- The start time ofa planned outage shouldbe final by5PM Pacific Prevailing Time one business day prior to thestartofthe outage. Outage start/end dates/timesshould be updated inCOS as soon aspracticable to reasonablyreflectthe planned or actualstart/end date/timeofthe outage.
- Scheduled outagesare encouraged to be submitted earlier than required.
Adjustments to initial scheduled outage submitted as soon as practicable.
5.2 / Balancing Authority* / 4/1/2017 / Planned Outage Data / Scheduled generator outagesand derates for units 50mwor greater. The RC considers a derate tobe any reduction in MWoutput50MW. Scheduled generation outages are to be submitted by10AM Pacific Prevailing Time atleastfourbusiness days prior to the startofthe scheduled outage.
Plannedoutages thatare not submitted to COS by10AM Pacific Prevailing Time fourbusinessdays prior to the startofthe scheduled outagewill beconsidered late.
The start/end time/date ofplanned outages maybe adjusted in COS after initial submission;however,planned outages beginning the next business dayshould be final (for operations planning purposes) accordingto the following:
•The start date ofa planned outage shouldbe final by 8AM Pacific Prevailing Time one business day prior to the startofthe outage.
•The start time ofa planned outage shouldbe final by 5PM Pacific Prevailing Time one business day prior to the startofthe outage.
Outage start/end dates/timesshould be updated inCOS as soon as practicable to reasonablyreflectthe planned oractual start/end date/time ofthe outage.
Outages can be cancelled atanytime as deemed necessarybytheTOP or BA.
(See note8 for acceptable examples ofplanned outage time adjustments)
Scheduled outages are encouraged to be submitted earlier than required. / COS / Submitted daily,ata minimum eachweek day.
Adjustments to initial scheduled outage submitted as soon as practicable.
5.2.1 / Balancing Authority* / 4/1/2017 / Planned Outage Data / Scheduled generator outagesand deratesfor all BA Area generation that qualifies per the BES definition, includingany non-BES generation (as determined bythe TOP or BAPeak), that are necessaryto support the accuracy ofOperational Planning Analyses and to determine SOL exceedance onBES Facilities.The RC considers a derate to be anyreduction in MWoutput50MW.Scheduled generation outages are to be submitted by10AM PacificPrevailing Time atleastfourbusinessdaysprior to the startofthe scheduled outage.