1 Descriptions of Function

Transcription

1 The Use Case #4 implements integrated management of s 1 Descriptions of Function 1.1 Function Name Date , Version 1.13 implements integrated management of s 1.2 Function ID L Brief Description The utility implements integrated management of s (DER), which includes (DG), storage and Demand Response (DR). In scenario 1 The utility monitors and manages feeder voltage profile and may use a smart algorithm. (Voltage Profile). In scenario 2 The utility uses installed equipment and other distribution control equipment such as Load Tap Changer and Capacitor Bank Controls to address peaking resource requirements. (Peaking ). In the final scenario 3 The utility uses installed equipment and other distribution control equipment such as Load Tap Changer and Capacitor Bank Controls to address a transmission constraint contingency. (Transmission Constraint). 1.4 Narrative Given the level of sophistication of today s electrical grid, there is a limit to the how widespread renewable energy resources can be introduced into the electrical system. The intermittent nature of these resources complicates their integration into the grid. Conditions such as cloud transients can substantially reduce the output of photovoltaic (PV) installations. This variability increases the complexity of scheduling and delivering energy to the grid, and can ultimately reduce grid stability. This use case describes how monitoring the real-time status, with a very granular time stamp (1 second) of renewable energy resources can increase the utility s effectiveness in handling this variability. Possessing real-time status information about renewable resources and feeder loads allows the utility to take UC-4 Version December 15, 2009

2 appropriate actions based on sudden increases or decreases in energy needs on the system. The utility could also install distributed renewable generation to supplement or defer grid upgrades where space, economics, or other constraints prevent the expansion of substations or the building of new distribution lines. A possible means of balancing this intermittency is to deploy energy storage devices as either participating renewable generation or load resources. The integrated use of energy storage devices introduces a need for real-time communications to monitor and control these resources. In general, examples of energy storage resources that can discharge energy instantaneously include batteries, flywheels, superconducting magnetic energy storage, ultra-capacitors, and aggregated plug-in electric vehicles. Also, Demand Response can be treated in a similar manner to actual. This requires that the response characteristics of the load be understood and even be dispatchable (load control). can reduce the peak loading on the grid. It can also help support line voltage at the end of long distribution circuits. The communications infrastructure for advanced metering can provide mechanisms that enable distributed generation and demand response to be deployed with greater safety and enhanced overall system reliability. The infrastructure should support monitoring of the operation, identification of for safety concerns, provide interfaces to the systems with pricing information and other signals when there are needs or incentives for the operation, and provide an interface to the for other applications such as voltage control, VAR control, and harmonic control. about availability and characteristics should be made available as part of the power system operations and for planning purposes (with appropriate aggregation). The utility monitors the distribution system in real-time. This monitoring includes the system voltage levels, current levels, frequency, power factor, phase balancing, and the status and output of any distributed generation and storage. The information is aggregated and monitored by an integrated management application. The application is able to determine alarms conditions and provide alarm notifications to system operators along with guidance information on which actions need to be taken. operators will be able to control utility owned distributed generation, storage, and other resources (such as capacitors, regulators, and tap changers) to help mitigate system disturbances for which local/manual correction is not done. operators will, also, have access to any control mechanisms agreed upon with the to be able to dispatch the owned distributed generation, distributed storage, or load control options (dynamic pricing and demand response events) to help mitigate the system disturbance. In addition this application will be able to respond automatically to defined scenarios without human intervention. Scenario 1 UC-4 Version December 15, 2009

3 implements integrated management of, storage and Demand Response. In scenario 1 - monitors and manages feeder voltage profile and may use a smart algorithm. Voltage Profile. The utility has also implemented a demand response system enabling the utility to request load reductions by the in accordance with applicable tariffs. The utility implements a that takes field measurements from the system (Net/Billing Meter),, PV inverters, battery charging systems, Load Tap Changer Controls and capacitor controllers. The automatically determines the optimal energy resource mix to control the voltage on the feeder to achieve a reduction in the duty cycle for the Load Tap Changer and cap bank control equipment while maintaining feeder voltage within ANSI Range A limits. Scenario 2 implements integrated management of, storage and Demand Response. Peaking. communicates to inverter controllers (via 2-way communications) for the purpose of control and optimization of, storage and Demand Response. In scenario 2 the utility uses installed equipment and other distribution control equipment such as Load Tap Changer and capacitor controls to address peaking resource requirement. Scenario 3 uses installed equipment and other distribution control equipment such as Load Tap Changer and capacitor controls to address a transmission constraint. 1.5 Actor (Stakeholder) Roles Describe all the people (their job), systems, databases, organizations, and devices involved in or affected by the Function (e.g. operators, system administrators, technicians, end users, service personnel, executives, SCADA system, real-time database, RTO, RTU, IED, power system). Typically, these actors are logically grouped by organization or functional boundaries or just for collaboration purpose of this use case. We need to identify these groupings and their relevant roles and understand the constituency. The same actor could play different roles in different Functions, but only one role in one Function. If the same actor (e.g. the same person) does play multiple roles in one Function, list these different actor-roles as separate rows. UC-4 Version December 15, 2009

4 Grouping (Community), Actors Functioning from the s. Group Description Actors that perform their specific functions from the premises. Actor Name Actor Type (person, device, system etc.) Actor Description Person Residential or small business energy user that has a contract with the utility to receive electrical service from the utility and have a meter installed (possibly an Meter). The may or may not participate in programs provided by the utility including pricing events, load control or distributed generation. Display Device Home Area Battery and Predefined Device Display device that receives energy and event information from the and presents it to the. HAN. Any side automation that can make use of utility signals to affect energy usage within the premises will be considered as the Home Area for this project. Home Area can affect, lighting, security, etc. The will not own Home Area. The storage batteries used to store the electrical energy and the monitoring system to change the charge/discharge rate and status of the batteries. system may be capable of communicating key data to other applications. owned by the. The is one of the communications radios that could be under glass of the Meter. (There are two radios built in to the Meter. One is for the and is a longer range radio. The other is for the and it has a smaller range.) This is the communication resource to the and the Home Area (if available). The completes a profile upon installation that will determine how the premise will function under different circumstances (pricing, UC-4 Version December 15, 2009

5 Grouping (Community), Actors Functioning from the s. Group Description Actors that perform their specific functions from the premises. Actor Name Actor Type (person, device, system Actor Description etc.) Profile t Credit Meter Net/Billing Meter Device Device Device etc.). This profile is programmed into the t. that the or agent of the owns and operates at its premise. CEMS. owned premise system which interfaces with the Home Area and the to provide services for load management and distributed generation. Additionally, may provide the ability to control owned equipment independent of the.. Credit Meter is a revenue grade meter used to measure the energy supplied by Ditributed. The Credit Meter information is recorded and forwarded to the PV Program Manager. Advanced electric revenue meter capable of two-way communications with the utility. A device that serves as a gateway between the utility, site, and load controllers of the. The meter measures, records, displays, and transmits data such as energy usage, generation, text messages, event logs, etc. to authorized systems (i.e., the t ) and provides other advanced utility functions. Net/Billing Meter is a bi-directional revenue grade meter used to measure energy supplied by the or used by the. Advanced electric revenue meter capable of two-way UC-4 Version December 15, 2009

6 Grouping (Community), Actors Functioning from the s. Group Description Actors that perform their specific functions from the premises. Actor Name Actor Type (person, device, system Actor Description etc.) Device communications with the utility. A device that serves as a gateway between the utility, site, and load controllers of the. The meter measures, records, displays, and transmits data such as energy usage, generation, text messages, event logs, etc. to authorized systems (i.e., the ) and provides other advanced utility functions. at the site belonging to the that can be used for control of real and reactive power output. Meter Device Advanced electric revenue meter capable of two-way communications with the utility. A device that serves as a gateway between the utility, site, and load controllers. The meter measures, records, displays, and transmits data such as energy usage, generation, text messages, event logs, etc. to authorized systems (i.e., the ) and provides other advanced utility functions. Grouping (Community), The Actors. Group Description Actors that perform their specific function as a part of the. Actor Name Actor Type (person, device, system etc.) Actor Description The Host utility. Advanced Metering Infrastructure. Advanced electric revenue metering system capable of two-way communications between the and the UC-4 Version December 15, 2009

7 Grouping (Community), The Actors. Group Description Actors that perform their specific function as a part of the. Actor Name Actor Type (person, device, system Actor Description etc.) utility. A device that serves as a gateway ( ) between the utility, site, and load controllers of the. The meter measures, records, displays, and transmits data such as energy usage, generation, text messages, event logs, etc. to authorized systems (i.e., the ) and provides other advanced utility functions.. Enterprise Service Bus DER. Works in conjunction with the and receives field measurements from the system (Net/Billing Meter),, PV inverters, battery charging systems, Load Tap Changer Controls and capacitor controllers in addition to weather forecast information for the purpose of controlling the distribution network. The utility implements a that takes field measurements from the system (Net/Billing Meter),, PV inverters, battery charging systems, Load Tap Changer Control and capacitor controllers. The application automatically determines the optimal energy resource mix to control the voltage on the feeder to achieve a reduction in the duty cycle for the Load Tap Changer and cap bank control equipment while maintaining feeder voltage within ANSI Range A limits. The ESB will act as a message broker between applications. The applications will communicate via the ESB. Such an approach has the primary advantage that it reduces the number of point-to-point connections required to allow applications to communicate. UC-4 Version December 15, 2009

8 Grouping (Community), The Actors. Group Description Actors that perform their specific function as a part of the. Actor Name Actor Type (person, device, system Actor Description etc.) t t Availability and Control Device equipment at the utility s site that will be used for the charge/discharge and monitoring of the storage battery system. NMS. is the utility back office system that is responsible for remote two-way communications with the Meters to retrieve data and execute commands. The has the responsibility to balance load on the communications network resulting from scheduled meter reads and to retry meters when communications fail. is the component responsible for monitoring the health of the system, managing and implementing remote firmware updates, configuration changes, provisioning functions, control and diagnostics. MDMS. that gathers, validates, estimates and permits editing of meter data such as energy usage, generation, and meter logs. It stores this data for a limited amount of time before it goes to a data warehouse (Meter Data Archive), and makes this data available to authorized systems and authorized personnel. DRAACS. and subsystems responsible for maintaining an estimate, with a known precision, of how much resource is available for dispatch. Availability and Control is also responsible for accepting requests for blocks of energy and/or capacity and implementing that request by issuing load control requests. Availability and Control contains an optimization function that can determine the optimal set to request curtailment from based upon a UC-4 Version December 15, 2009

9 Grouping (Community), The Actors. Group Description Actors that perform their specific function as a part of the. Actor Name Actor Type (person, device, system Actor Description etc.) Service Representative Load Tap Changer Controls Person Device variety of factors/parameters, including the size and location of the desired Demand Response resource. Availability and Control is expected to track the "as implemented" response to load control requests and issue additional load reduction requests to selected sets until authorized load reduction target is met. Availability and Control uses measured responses to load demand requests to refine its internal model. Note: Any Availability and Control in use today may be parts of other systems being used. No platform exists to bring it into an operational tool today. CIS. Maintains contact information, calculates and formats bills, receives, and applies payments for individual accounts. The system is responsible for storing information such as site data, meter number, rates, and program participation. CSR. Staff employed by the utility who respond to complaints, to outage notifications, or to requests to activate, modify and/or terminate delivery of service. Service Representatives also enroll a in utility sponsored programs and answer questions related to the energy consumption and cost data of the. Many off-cycle reading, billing, work orders and diagnostics requests are initiated by the Service Representative in response to contact. Load Tap Changer Controls. Tap changing device that senses voltage and changes taps to raise or lower the voltage to remain in a set bandwidth. These are deices that act automatically generally after sensing the voltage out-of-bandwidth for 30 seconds. Capacitor Bank Device Cap Bank Controls. The control units used to monitor and operate banks of UC-4 Version December 15, 2009

10 Grouping (Community), The Actors. Group Description Actors that perform their specific function as a part of the. Actor Name Actor Type (person, device, system Actor Description etc.) Controls Power Operations Person capacitors on the lines. The Capacitor Bank Controls are used for power factor correction on the s system. The banks are measured in voltamperes reactive (VAr). The Capacitor Bank Controls work autonomously or can be controlled by SCADA. PO. Initiates dynamic pricing data or demand response events to mitigate transmission reliability requirements Operations Grid Control Center t t Person DO. Operating over the distribution system, using SCADA and to make decisions concerning the distribution grid. Initiates dynamic pricing data or demand response events to mitigate distribution reliability and voltage profile requirements. GCC. The Grid Control Center controls grid operations through the, SCADA and in the control area. The Grid Control Center will communicate to grid operators to ensure grid reliability and also signals. DMS. A system that integrates the functions of SCADA, outage management, work management, distribution load management, reactive control, and asset management into a single console and set of applications. EMS. The controls grid operations in the control area. The will communicate to substation RTUs to ensure grid reliability. LAMBDA Also called "system lambda," a term describing the cost of the next kilowatt hour that could be produced from dispatchable units on an electric supply UC-4 Version December 15, 2009

11 Grouping (Community), The Actors. Group Description Actors that perform their specific function as a part of the. Actor Name Actor Type (person, device, system Actor Description etc.) system. Wholesale Power Group Person WPG. Takes all resources available and determines optimum generation mix on economic basis Device at the utility s site belonging to the utility that can be used for control of real and reactive power output. Device that the owns and operates. 1.6 exchanged Describe any information exchanged in this template. Object Name Voltage Out of Range Event Begin Object Description When the voltage at a node on a feeder gets out of range in compliance with ANSI A standards. An alert sent from an Meter. This alert jumps queue and is sent to the. The alert is from voltage being out of ANSI A range. This is taken from ANSI C Electrical Power s and Voltage Ratings (60HZ). To begin the UC-4 Version December 15, 2009

12 Object Name Affected and Affected Area Selected Assets Operational Command Block VAR Based Capacitor Switching Capacitor Bank Controls Operational Command Load Tap Changer Controls Operational Command Condition Data Demand Response Event Notification Demand Response Selected s Listing Object Description and area information for an event. A listing of Selected Assets chosen to meet the requirements of the Demand Response Event. A command that will evoke a change in piece of equipment. Command sent between equipment types to evoke an. The operational state of the specific equipment. The is the signal sent from the to inform the and the Availability and Control the status of the equipment. The operational state of a specific group of system equipment assets. A command sent to the Capacitor Bank Controllers that prevents further switching. An Open or Close Command sent to the Capacitor Bank Controls to effect a change on the status of the equipment. A Raise Tap or Lower Tap Command sent to the Load tap Changer. Controls to effect a change on the status of the equipment. The condition of the electrical system, including equipment status and voltage, current and load parameters Event notification that will be sent to the and compared to the Predefined Profile. This comparison will affect the status of the equipment controlled at the premise. Selected set of customers chosen to meet the requirements of the Demand Response Event. UC-4 Version December 15, 2009

13 Object Name Demand Response Event Notification with the Selected s Override Net/Billing Meter Read Request and an Read Request Net/Billing Meter Read Request Credit Meter Read Request Net/Billing Net/Billing and Credit Total Load Affected Calculation Object Description Event notification that will be sent to the and compared to the Predefined Profile. This comparison will affect the status of the equipment controlled at the premise. This notification will also include the selected set of customers chosen to meet the requirements of the Demand Response Event. When the chooses to Override a selected Demand Response Event, they will be required to acknowledge the event on their Display by pushing the Acknowledge button and entering the correct Override Code onto the Display. When the Display receives the correct Override Code it will send a Demand Response Override Function to the, which will allow the controlled premise devices to act accordingly. of the premise equipment. A request for an Net/Billing Meter Read and a request for an Credit Meter Read. A request for an Net/Billing Meter Read. A request for an Read Meter data for a specific. This data includes voltage, current, load and power quality parameters. Meter data for a specific and meter data for a specific Net/Billing Meter. This data includes voltage, current, load and power quality parameters. The calculation for the total load that was affected by the Demand Response Event. This affected load is calculated by the from the before Demand Response Event and after Demand Response Event metering data. UC-4 Version December 15, 2009

14 Object Name Total Load Affected Voltage Out of Range Event Alert History Data Relevant Voltage Out of Range Event Alert History Data Peaking Requirements and Pricing Signal s Required for the Next Day Confirmed s Required for the Next Day s s Credit Object Description The calculated total load that was affected by the Demand Response Event. This affected load is calculated by the from the before Demand Response Event and after Demand Response Event metering data. Historical data concerning a specific Voltage Limit Event Alert All relevant historical data concerning a specific Voltage Limit Event Alert. This relevant historical data will be compiled and saved. Asset requirements to meet a Peaking Event that includes Pricing signals. Asset required to meet the expected loading requirements of the next day. The Confirmation of the assets required to meet the expected loading requirements of the next day. the s capabilities to meet system requirements. The system was scheduled for use. the s capabilities to meet system requirements. The system was scheduled for use. the capabilities to meet system requirements. The system was scheduled for use. the capabilities to meet system requirements. The system was scheduled for use. Meter data for a specific. This data includes voltage, current, UC-4 Version December 15, 2009

15 Object Name Insufficient s a Demand Response Load Reduction Event Demand Response Load Reduction Event Notification Demand Response Load Reduction Event Notification with the Selected s Dispatch Transmission Constraint Scenario Transmission Report Available Strategy Confirmed s Event History Data Relevant Event History Data Object Description load and power quality parameters. Insufficient equipment assets to meet the system demands. A request for a Demand Response Event to assist in meeting the system requirements. Event notification (designed to lower the loading on the system) that will be sent to the and compared to the Predefined Profile. This comparison will affect the status of the equipment controlled at the premise. Event notification (designed to lower the loading on the system) that will be sent to the and compared to the Predefined Profile. This comparison will affect the status of the equipment controlled at the premise. This notification will also include the selected set of customers chosen to meet the requirements of the Demand Response Event. A report of the energy resources that have been dispatched. Emergency system condition in which the available load is not sufficient to meet the system demands. Report of the Available Transmission assets. Available s asset required to meet the expected loading requirements of the next day. The Confirmation of the assets required to meet the expected loading requirements of the next day. Historical data concerning a specific Event All relevant historical data concerning a specific Event. This relevant historical data will be compiled and saved. UC-4 Version December 15, 2009

16 Object Name Available s Object Description s available to meet system requirements or needs. 1.7 Activities/Services Describe or list the activities and services involved in this Function (in the context of this Function). An activity or service can be provided by a computer system, a set of applications, or manual procedures. These activities/services should be described at an appropriate level, with the understanding that sub-activities and services should be described if they are important for operational issues, automation needs, and implementation reasons. Other sub-activities/services could be left for later analysis. Activity/Service Name Activities/Services Provided 1.8 Contracts/Regulations Identify any overall (human-initiated) contracts, regulations, policies, financial considerations, engineering constraints, pollution constraints, and other environmental quality issues that affect the design and requirements of the Function. Contract/Regulation Service Contract Pricing Contract Impact of Contract/Regulation on Function No can operate on the s system in a manner that is detrimental to the or other customers. The has signed a Pricing Contract to allow them to adjust their loads and/or source with pricing. Policy From Actor May Shall Not Shall Description (verb) To Actor UC-4 Version December 15, 2009

17 Constraint Type Description Applies to 2 Step by Step Analysis of Function 2.1 Steps to implement function Scenario 1 monitors and manages feeder voltage profile and may use a smart algorithm. Voltage Profile Preconditions and Assumptions Describe conditions that must exist prior to the initiation of the Function, such as prior state of the actors and activities Identify any assumptions, such as what systems already exist, what contractual relations exist, and what configurations of systems are probably in place Identify any initial states of information exchanged in the steps in the next section. For example, if a purchase order is exchanged in an activity, its precondition to the activity might be filled in but unapproved. Actor///Contract The The The The The Preconditions or Assumptions PV inverters are set up to autonomously respond to ANSI A out-of-range voltage conditions. PV can be at substation or anywhere on the feeder. PV can be anywhere the residence is located, anywhere on the feeder. All controllable are utility controlled within tariff agreements Assuming a full system IEEE 1547 and other standards have evolved to support advanced applications. SCADA has the logic to determine priorities and control between volt or VAR control. UC-4 Version December 15, 2009

18 Actor///Contract The The The The The Preconditions or Assumptions will block switching of capacitor control for VARs/Power Factor if control is already being used for voltage control. The cause of the voltage being out-of-range is due to cloud transient and therefore requires a system control response vs. an individual control (due to energy storage) resulting in low voltage. PV inverter is providing voltage regulation within its capabilities and VAR support. When PV and the inverter are combined with storage, the control is integrated together as one actor. The has control over the inverter. During an emergency situation, grid stability, the can isolate the inverter from the grid. The will not be able to override this situation with their. This is only for emergency situations. The uses a smart algorithm to determine the optimum asset dispatch including storage,, capacitor bank, Load Tap Changer and Demand Response. The smart algorithm will be a part of the. Operations can call a Demand Response event in this scenario Steps Describe the normal sequence of events, focusing on steps that identify new types of information or new information exchanges or new interface issues to address. Should the sequence require detailed steps that are also used by other functions, consider creating a new sub function, then referring to that subroutine in this function. Remember that the focus should be less on the algorithms of the applications and more on the interactions and information flows between entities, e.g. people, systems, applications, data bases, etc. There should be a direct link between the narrative and these steps. The numbering of the sequence steps conveys the order and concurrency and iteration of the steps occur. Using a Dewey Decimal scheme, each level of nested procedure call is separated by a dot.. Within a level, the sequence number comprises an optional letter and an integer number. The letter specifies a concurrent sequence within the next higher level; all letter sequences are concurrent with other letter sequences. The UC-4 Version December 15, 2009

19 number specifies the sequencing of messages in a given letter sequence. The absence of a letter is treated as a default 'main sequence' in parallel with the lettered sequences. Sequence 1: Sequence 2: Do step 1 1.2A.1 - In parallel to activity 2 B do step 1 1.2A.2 - In parallel to activity 2 B do step 2 1.2B.1 - In parallel to activity 2 A do step 1 1.2B.2 - In parallel to activity 2 A do step Do step nested step nested step Do step Do step 2 # Event Primary Actor Name of Description of Producer Receiver Name of Info Exchanged Additional Notes IECSA Environments # Triggering event? Identify the name of the event What other actors are primarily responsible for the? Actors are defined in section1.5. Label that would appear in a process diagram. Use action verbs when naming activity. Describe the actions that take place in active and present tense. The step should be a descriptive noun/verb phrase that portrays an outline summary of the step. If Then Else scenarios can be captured as multiple Actions or as separate steps. What other actors are primarily responsible for Producing the information? Actors are defined in section1.5. What other actors are primarily responsible for Receiving the information? Actors are defined in section1.5. (Note May leave blank if same as Primary Actor) Name of the information object. objects are defined in section 1.6 Elaborate architectural issues using attached spreadsheet. Use this column to elaborate details that aren t captured in the spreadsheet. Reference the applicable IECSA Environment containing this data exchange. Only one environment per step. UC-4 Version December 15, 2009

20 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments 1.1 A distribution node ( Net/Billing Meter) detects a Voltage Out of Range Event. Net/Billing Meter Voltage Out of Range Event Net/Billing Meter (distribution node) detects a Voltage Out of Range Event Alert (voltage out of ANSI A standards) and the alert, jumping queue, to the t via the Infrastructure. Net/Billing Meter t Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure Voltage Out of Range Event to the Voltage Out of Range Event to the The t the Voltage Out of Range Event Alert to the t t t Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure. UC-4 Version December 15, 2009

21 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Voltage Out of Range Event to the Voltage Out of Range Event to the The t the Voltage Out of Range Event Alert to the t Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure Voltage Out of Range Event to the. Voltage Out of Range Event to the. The t the Voltage Out of Range Event Alert to the t. t t Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure. UC-4 Version December 15, 2009

22 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Voltage Out of Range Event acknowledg ed. Operations Voltage Out of Range Event acknowledg ed. The Operations acknowledges the Voltage Out of Range Event Alert at the t. Operations Operations Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure. 1.2 Begins Operations Begins The Operations acknowledges the Voltage Out of Range Event Alert and begins the. (From the t station.) Operations Begin UC-4 Version December 15, 2009

23 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Collects Data Collects Data The collects data from the t concerning affected equipment and area. Affected and Affected Area Selects Assets Selects Assets The, using an algorithm, selects certain Battery and, certain Capacitor Bank Controls and certain Load Tap Changer Controls to help correct the Voltage Out of Range Event Alert. Selected Assets Asset list developed from algorithm UC-4 Version December 15, 2009

24 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Sends selected Assets to the Sends selected Assets to the The Operational Command for the selected s to the t. t Selected Assets UC-4 Version December 15, 2009

25 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments 1.3 Operational Command to Operational Command to The t Operational Command for the selected s to the t t t Operational Command Operational Command to Operational Command to The t Operational Command for the selected s to the. t Operational Command UC-4 Version December 15, 2009

26 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Operational Command to the Operational Command to the The Operational Command for the selected s to the Operational Command Operational Command to the. Operational Command to the. The processes Operational Command and it to the selected. Operational Command UC-4 Version December 15, 2009

27 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments responds to Operational Command responds to Operational Command The selected Battery And processes Operational Command and responds accordingly. Operational Command to the. to the. The selected Battery And a Battery And to the. 1.4 to the. to the. The a Battery And to the. UC-4 Version December 15, 2009

28 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments to the. to the. The a Battery And to the t. t to the. to the. The t a Battery And to the t. t t updates. updates. The t updates the. t t UC-4 Version December 15, 2009

29 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Profile to the. Profile to the. The t Sends the Updated to the. t --END of the Steps blocks VAR Based Capacitor Switching blocks VAR Based Capacitor Switching t blocks VAR based capacitor switching decision logic when ANSI A voltage is out-ofrange t Capacitor Bank Controls Block VAR Based Capacitor Switching UC-4 Version December 15, 2009

30 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments 1.6 Capacitor Bank Controls Operational Commands to The Capacitor Bank Controls Operational Commands to The The Capacitor Bank Controls Operational Command for the selected Capacitor Bank Controls to the t. t Capacitor Bank Controls Operational Command Capacitor Bank Controls Operational Commands to Capacitor Bank Controls Capacitor Bank Controls Operational Commands to Capacitor Bank Controls The t Capacitor Bank Controls Operational Command for the selected Capacitor Bank Controls via SCADA. t Capacitor Bank Controls Capacitor Bank Controls Operational Command UC-4 Version December 15, 2009

31 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Capacitor Bank Controls respond accordingly. Capacitor Bank Controls Capacitor Bank Controls respond accordingly. The selected Capacitor Bank Controls respond accordingly. Capacitor Bank Controls Capacitor Bank Controls Capacitor Bank Controls Operational Command 1.7 Capacitor Bank Controls send to Capacitor Bank Controls Capacitor Bank Controls send to The selected Capacitor Bank Controls send an to the t via SCADA. Capacitor Bank Controls t 1.8 updates the updates the The t updates the. t t UC-4 Version December 15, 2009

32 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments 1.9 to the to the The t Sends the Updated to the. t --END of the Cap Bank Steps Load Tap Changer Controls Operational Command to the Load Tap Changer Controls Operational Command to the The Load Tap Changer Controls Operational Command for the selected Load Tap Changer Controls to the t. t Load Tap Changer Controls Operational Command UC-4 Version December 15, 2009

33 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Load Tap Changer Controls Operational Command to Load Tap Changer Controls Load Tap Changer Controls Operational Command to Load Tap Changer Controls The t Load Tap Changer Controls Operational Command for the selected Load Tap Changer Controls via SCADA. t Load Tap Changer Controls Load Tap Changer Controls Operational Command Load Tap Changer Controls respond accordingly. Load Tap Changer Controls Load Tap Changer Controls respond accordingly. The selected Load Tap Changer Controls respond accordingly. Load Tap Changer Controls Load Tap Changer Controls Load Tap Changer Controls Operational Command Load Tap Changer Controls send to Load Tap Changer Controls Load Tap Changer Controls send to The selected Load Tap Changer Controls send an to the t via SCADA. Load Tap Changer Controls t UC-4 Version December 15, 2009

34 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments updates the updates the The t updates the. t t to the to the The t Sends the Updated to the. t --END of Load Tap Changer Part-- UC-4 Version December 15, 2009

35 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Voltage Out of Range Event Net/Billing Meter Voltage Out of Range Event An Net/Billing Meter (distribution node) detects a Voltage Out of Range Event Alert (voltage out of ANSI A standards) and the alert, jumping queue, to the t via the Infrastructure. Net/Billing Meter t Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure Voltage Out of Range Event to the Voltage Out of Range Event to the The t the Voltage Out of Range Event Alert to the t t t Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure. UC-4 Version December 15, 2009

36 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Voltage Out of Range Event to the Voltage Out of Range Event to the The t the Voltage Out of Range Event Alert to the. t Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure Voltage Out of Range Event to the Voltage Out of Range Event to the The t the Voltage Out of Range Event Alert to the t. t t Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure. UC-4 Version December 15, 2009

37 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Voltage Out of Range Event acknowledg ed by the Operations Operations Voltage Out of Range Event acknowledg ed by the Operations The Operations acknowledges the Voltage Out of Range Event Alert at the t. Operations Operations Voltage Out of Range Event Voltage Out of Range Event jumps queue and is reported back to the t via the Infrastructure collects data collects data The collects data from the t concerning affected equipment and area. t Affected and Affected Area UC-4 Version December 15, 2009

38 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments updates system data and the Condition Data to the Operations. updates system data and the Condition Data to the Operations. t updates system data and the Condition Data to the Operations. t Operations Condition Data Operations determine a Demand Response Event is necessary. Operations Operations determine a Demand Response Event is necessary. Operations review the system condition data and determine that a Demand Response Event is required for system reliability. Operations Operations Condition Data UC-4 Version December 15, 2009

39 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Operations the Demand Response Event Notification to the Availability and Control. Operations Operations the Demand Response Event Notification to the Availability and Control. Operations the Demand Response Event Notification to the Availability and Control. Operations Availability and Control Demand Response Event Notification The Demand Response Event Notification will include current system load, affected area and reduction amount Availability and Control assembles Demand Response Selected s Listing to meet the event needs. Availability and Control Availability and Control assembles Demand Response Selected s Listing to meet the event needs. Availability and Control assembles the Demand Response Selected s Listing to meet the needs of the Demand Response Event Notification. Availability and Control Availability and Control Demand Response Selected s Listing This notification will only be sent out to the selected customers. UC-4 Version December 15, 2009

40 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Availability and Control assembles Demand Response Selected s Listing to meet the event needs. Availability and Control Availability and Control assembles Demand Response Selected s Listing to meet the event needs. Availability and Control the Demand Response Event Notification with the Selected s to the t. Availability and Control t Demand Response Event Notification with the Selected s Availability and Control assembles Demand Response Selected s Listing to meet the event needs. Availability and Control Availability and Control assembles Demand Response Selected s Listing to meet the event needs. Availability and Control the Demand Response Event Notification with the Selected s to the. Availability and Control Demand Response Event Notification with the Selected s UC-4 Version December 15, 2009

41 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments Availability and Control assembles Demand Response Selected s Listing to meet the event needs. Availability and Control Availability and Control assembles Demand Response Selected s Listing to meet the event needs. Availability and Control the Demand Response Event Notification with the Selected s to the t. Availability and Control t Demand Response Event Notification with the Selected s provides the Demand Response Event Notification with the Selected s to the. provides the Demand Response Event Notification with the Selected s to the. The t Demand Response Event Notification with the Selected s out to the via the Infrastructure. t Demand Response Event Notification with the Selected s UC-4 Version December 15, 2009

42 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments provides the Demand Response Event Notification with the Selected s to the. provides the Demand Response Event Notification with the Selected s to the. The delivers the Demand Response Event Notification with the Selected s to the selected customer s t. t Demand Response Event Notification with the Selected s provides the Demand Response Event Notification with the Selected s to the Display. provides the Demand Response Event Notification with the Selected s to the Display. The delivers the Demand Response Event Notification with the Selected s to the selected customer s Display. Display Device Demand Response Event Notification with the Selected s UC-4 Version December 15, 2009

43 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments A. 1 chooses to Override chooses to Override chooses to Override by entering the correct code into the Display. Display Device Override The Override steps are an alternate subset of steps in this scenario and are OPTIONAL. The would use these steps if they chose to Override the Demand Response Event Notification. If the Override is not chosen please move on to Step # B.1. UC-4 Version December 15, 2009

44 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments A. 2 Display override signal to the Display Device Display override signal to the Display acknowledges correct code and override signal to the t. Display Device t Override The Override steps are an alternate subset of steps in this scenario and are OPTIONAL. The would use these steps if they chose to Override the Demand Response Event Notification. If the Override is not chosen please move on to Step # B.1. UC-4 Version December 15, 2009

45 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments A. 3 responds accordingly. responds accordingly. t receives the override signal and responds accordingly. t t Override The Override steps are an alternate subset of steps in this scenario and are OPTIONAL. The would use these steps if they chose to Override the Demand Response Event Notification. If the Override is not chosen please move on to Step # B.1. UC-4 Version December 15, 2009

46 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments B. 1 compares Demand Response Event Notification and responds accordingly. compares Demand Response Event Notification and responds accordingly. The t compares the Demand Response Event Notification with the Selected Predefined Profile and acts accordingly t t Demand Response Event Notification with the Selected s This is the normal set of steps for this sequence. Please move on to Step # to the. to the. The t to the. t UC-4 Version December 15, 2009

47 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments to the. to the. The Delivers the to the t via the Infrastructure. t t to the Availability and Control. to the Availability and Control. The t delivers the to the Availability and Control. t Availability and Control UC-4 Version December 15, 2009

48 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments to the Meter Data. to the Meter Data. The t delivers the to the t. t t Availability and Control an Net/Billing Meter Read Request and an Read Request. Availability and Control Availability and Control an Net/Billing Meter Read Request and an Read Request. Availability and Control an Net/Billing Meter Read Request and an Credit Meter Read Request to the t. Availability and Control t Net/Billing Meter Read Request and an Credit Meter Read Request UC-4 Version December 15, 2009

49 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments A.1 a request to the Net/Billing Meter for an Meter read. a request to the Net/Billing Meter for an Meter read. The t the Net/Billing Meter Read Request to the Net/Billing Meter via the Infrastructure. t Net/Billing Meter Net/Billing Meter Read Request B.1 a request to the for an Meter read. a request to the for an Meter read. The t the Credit Meter Read Request to the via the Infrastructure. t Credit Meter Read Request UC-4 Version December 15, 2009

50 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments A.2 Net/Billing Meter delivers Net/Billing Net/Billing Meter Net/Billing Meter delivers Net/Billing The Net/Billing Meter delivers Net/Billing Meter Data to the t via the Infrastructure. Net/Billing Meter t Net/Billing B.2 delivers Data. delivers Data. The delivers Credit to the t via the Infrastructure. t Credit UC-4 Version December 15, 2009

51 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments the Net/Billing and Data. the Net/Billing and Data. The t the Net/Billing and Credit to the Availability and Control. t Availability and Control Net/Billing and Credit the Net/Billing and Data. the Net/Billing and Data. The t the Net/Billing and Credit to the t. t t Net/Billing and Credit UC-4 Version December 15, 2009

52 Name of Description of Name of Info IECSA Producer Receiver Exchanged Environments the Net/Billing and Data. the Net/Billing and Data. The t the Net/Billing and Credit to the t. t t Net/Billing and Credit UC-4 Version December 15, 2009