## IGNORE for Demand Response
### Governor Rules
#### 6.2.2 DRAS Governor Rules  
DRAS issues DR commands when contingency occurs and response is taken in the same area. If DRAS is not able to maintain power demand and supply, it asks PU to take action. DRAS computes the percentage of customers (who are enrolled in DR program) on a rotating basis [32] to send commands in order to mitigate contingency. **Command 4:** DER_DISPATCH (X% of customers in area Y). **Rule 4.1:** Required Policy  
**Steps:**  
1. The DRAS governor verifies whether the command is issued by PU. If PU issued this command, the PU governor would have verified the need of the command and signed it before sending it to DRAS. 2. The DRAS governor will verify the signature of the PU governor and ALLOW the command. If the command is not signed by the PU governor, that means it is originated from DRAS; jump to step 3. 3. The DRAS Y governor needs to check whether generation loss occurred or is about to occur in area Y. The DRAS Y governor receives information about the power supply and demand from local aggregators and about any contingency in all areas from the PU governor. Therefore, using the state information, the DRAS Y governor verifies whether there is (or will be) any generation loss in area Y. 4. If yes, it will ALLOW dispatching of the power to compensate the generation loss; otherwise DISALOW. **Rule 4.2:** Safety Policy **Steps:**  
1. Since the command is required to be implemented because of generation loss in area Y, the governor checks whether it is safe to execute. In area Y, the governor has power consumption readings, power supply readings, and the area frequency from aggregators. 2. It evaluates whether the power supply increase from X% DERs in that area will put the area frequency in a safe state. Each area has a certain power supply PS(t) that can be increased for a certain period before area frequency crosses the over-protection frequency threshold. 3. If the increase in supply is less than PS(t), it is safe--ALLOW; otherwise, DISALOW. **Command 5:** LOAD_CURTAILMENT (X% of customers in area Y; L\({}_{X}\) load to curtail at each customer; L MW load to be curtailed signed by the PU governor). **Rule 5.1:** Required Policy **Steps:**  
1. If generation loss occurs in area X and load curtailment needs to be performed in area Y, the command must be issued by PU, jump to step 2. If generation loss occurs in area Y and load curtailment needs to be performed in the same area, jump to step 3. 2. PU issued the signed load curtailment command to DRAS Y. When DRAS Y issues commands to all customers, the DRAS Y governor captures these commands and verifies the signature of the PU governor for the recent timestamp and verifies the total load that has to be curtailed using the signed information. If \(\sum_{x}Lx\cong L\), ALLOW; otherwise, DISALOW. 3. By leveraging the state information from the database, the DRAS Y governor determines whether there is any contingency in the same area. If there is no contingency in the same area, discard the commands. 4. If there is contingency in area Y, each governor has Z% (in addition to the generation loss) to which it will allow load drop commands to go through. This will provide the maximum load that can be dropped. Let Z = 10%. If contingency is of 20% generation loss, the governor has a load drop allowance of 20-30%. **Rule 5.2:** Safety Policy **Steps:**  
1. Every area has the total load P(t) that can be dropped over time so that the system remains in a safe state (the frequency never crosses the over-frequency threshold). P(t) is computed based on the power demand and supply in area Y through sensitivity analysis in the Power World simulator (described in Section 7.2). 2. Compute the total load curtailed as \(D(t)=\sum_{x}Lx\). If D(t) < P(t), ALLOW; otherwise, DISALOW. Note: The P(t) value for a time period is computed by the RTDS in reality. In this paper, we compute P(t) via Power World sensitivity analysis (described in Section 7.2).