Emergency Voltage Reduction
This chapter describes the Emergency Voltage Reduction workflow in Flex Operations. It includes the following topics:
Introduction
Emergency Voltage Reduction (EVR) temporarily lowers distribution voltage targets across selected areas of the real-time network. By controlling eligible load tap changers (LTCs) and voltage regulators, EVR can produce an immediate, broad reduction in real power demand.
Use EVR during emergency operating conditions to relieve generation shortages or transmission constraints, reduce loading on stressed equipment, help stabilize frequency after a major generation loss, restore operating reserves, and avoid or delay rolling outages or automatic under-frequency load shedding. EVR can provide rapid load relief across a wide area, often with less customer disruption than opening feeder breakers.
EVR gives operators a guided workflow to:
• Define an immediate, scheduled, or manual voltage-reduction request.
• Find SCADA-controllable LTCs and voltage regulators in the selected scope.
• Calculate and review per-phase target setpoints, bandwidths, and low limits.
• Include, exclude, or edit individual device targets before execution.
• Create an EVR event and, when applicable, an EVR switching sheet.
• Monitor execution, review the EVR Report, and restore devices after the reduction is no longer required.
Note: The descriptions in this chapter reflect the default product workflow. Available controls, status text, permissions, and coordination with other DMS applications can vary by implementation.
Understanding Emergency Voltage Reduction
Supported EVR Operating Scenarios
Select the EVR workflow that matches the required operating outcome. The execution mode determines which records are created and whether device-control steps are submitted automatically.
 
Scenario
When to Use It
Result
Immediate Automatic EVR
Voltage reduction must begin as soon as the reviewed request is created.
Creates the EVR event and switching sheet and submits eligible reduction steps for immediate execution.
Scheduled Automatic EVR
Reduction is required during a defined future operating window.
Creates a scheduled sheet. Reduction steps are scheduled for the Start Date; restore steps are scheduled for the End Date when configured.
Manual EVR Review
The request must be recorded and reviewed before any control work is prepared.
Creates the EVR event and report but does not create or submit a sheet from the main tool.
Manual Sheet Generation
A manual EVR event has been reviewed, and the operator is ready to prepare control steps.
Generates a switching sheet for review from the EVR Report without submitting it for execution.
Pre-EVR Restoration
Devices must return to the settings in effect before the EVR operation.
Generates restore steps from captured pre-EVR setpoint, bandwidth, and low-limit values.
Nominal Restoration
Devices must return to configured nominal settings rather than the preceding operating settings.
Generates nominal restore steps when Power Flow data and licensing are available.
Operating Considerations
• Use Fetch Devices to confirm that the returned device population matches the intended operating scope.
• Analysis uses the current values available when the calculation runs. Rerun Analysis when SCADA values, scope, timing, or intended device participation changes before job creation.
• In Automatic mode, Create Job can submit device-control steps immediately. Complete the pre‑job review before selecting Create Job.
• A Ready calculation status confirms that EVR produced a device target eligible for execution. It does not replace any network, switching, or supervisory review required by local operating procedures.
• Before and after EVR, review current voltage-control and optimization modes and follow local coordination procedures.
Understanding EVR Records
EVR uses several related records. Understanding their purpose helps you determine where to define, review, execute, and audit an EVR operation.
 
Record
Purpose
Executes Controls
EVR Request
Defines the scope, reduction percentage, execution mode, restore mode, device category, overrides, and schedule.
No
Working Solution
Contains the fetched devices and their calculated or edited values for the current request.
No
Saved EVR Case
Stores a reusable snapshot of a request and its device solution. Opening it creates a working copy.
No
EVR Event
Provides the Work Agenda record used to track the EVR life cycle and access the EVR Report.
No, by itself
EVR Report
Provides request, calculation, sheet-generation, execution, and restore messages plus the device solution summary.
No
EVR Switching Sheet
Contains the reduction or restore operations that can be reviewed, scheduled, locked, and executed.
Yes, when submitted or executed
 
Execution Behavior
 
Request Choice
System Result
Operator Next Step
Automatic - Immediate
Creates or reuses the EVR event and sheet and submits the sheet for immediate execution.
Monitor the event, sheet, and actual SCADA values.
Automatic - Scheduled
Creates or reuses the event and scheduled sheet. The sheet remains queued until the first scheduled block is due.
Verify Start Date, End Date, device blocks, and Scheduled Time values.
Manual
Creates or reuses the EVR event and report. No sheet is created from the main tool.
Review the EVR Report and generate a review sheet when ready.
 
Restore Modes
 
Restore Mode
Value Source
Operational Use
Pre-EVR
Setpoint, bandwidth, and low-limit values captured for the EVR operation.
Return devices to the settings that were active before EVR.
Nominal
Nominal values provided through Power Flow.
Return devices to the configured nominal baseline, which can differ from pre-EVR settings.
 
Note: Nominal restore is available only when the required Power Flow data and license are present.
How EVR Calculates Device Targets
Target Setpoint Formula
For each enabled device phase with a usable current setpoint, EVR calculates the target setpoint using the requested reduction percentage:
Target setpoint = Current setpoint x (1 - Voltage Reduction % / 100)
For example, with a current setpoint of 122.4 and a reduction request of 3 percent, EVR calculates 122.4 x 0.97 = 118.728.
The calculation uses the current setpoint available when Analysis runs. If the device state or SCADA value changes after Analysis, rerun Analysis and review the solution again before creating the job.
Value Sources and Precedence
 
Value
Source or Precedence
Current Setpoint
Usable current SCADA value refreshed for Analysis.
Calculated Target Setpoint
Current setpoint reduced by the requested percentage.
Edited Target Setpoint
Operator-entered target for an active phase. Review it after any subsequent Analysis.
Target Bandwidth
Device-specific edit; otherwise, the global bandwidth override; otherwise, the current SCADA bandwidth, when available.
Target Low Limit
Device-specific edit; otherwise, the global low-limit override; otherwise, the current SCADA low limit, when available.
Pre-EVR Restore Value
Value associated with the device before EVR execution.
Nominal Restore Value
Nominal value supplied through Power Flow.
Low-Limit Validation
EVR compares the requested target with the applicable low limit. When the target is below that limit, the device is marked Blocked and is not eligible for reduction-step generation until the request is changed or an approved limit value is applied.
Note: Use Bandwidth Override or Limit Override only in accordance with approved operating procedures. An override changes the value used by EVR; it does not eliminate the need to validate the resulting operating condition.
Phases, Ganged Devices, and Display Units
EVR supports per-phase current, nominal, target, bandwidth, and low-limit values. Enter or review values only for active phases. For a ganged device, the generated switching block uses the applicable ganged control while retaining the values selected by EVR.
EVR stores setpoint, bandwidth, and low-limit values as per-unit quantities. Depending on system configuration, Flex Operations can display the values using a 120 V reference and allow you to edit them in those units. The tool converts edited display values back to per unit when they are saved.
Calculation Status and Operator Action
 
Calc Status
Meaning and Step Eligibility
Operator Action
Ready
EVR calculated a valid target. The row is eligible for generated steps when Use is set to Enable.
Verify the target, bandwidth, low limit, and intended phases.
Review
An operator-edited value is present. The row can be eligible for execution after review.
Confirm the edited values before job creation, especially after rerunning Analysis.
Disabled
The row is excluded by the Use setting and is not used for generated steps.
Re-enable only when the device should participate.
Blocked
The requested target conflicts with the applicable low limit and is not executable.
Decrease the reduction percentage, apply an approved override, or leave the device excluded.
No SCADA Setpoint
EVR has no usable current setpoint for the row. No reduction step can be generated.
Verify SCADA availability and quality, or exclude the device.
Error
EVR could not produce a valid row result. The row is not executable.
Review Message / Reason, correct the condition, and rerun Analysis.
 
Using the Emergency Voltage Reduction Tool
Starting the Emergency Voltage Reduction Tool
To start EVR:
1. Open Flex Operations.
2. Open the application menu.
3. In the DMS section, select Emergency Voltage Reduction.
4. Review the request definition before editing or fetching devices.
The Emergency Voltage Reduction tool contains a request-definition area, a device-review table, and actions for editing the request, fetching devices, running Analysis, creating a job, saving a case, and opening saved solutions.
Using the Main Actions
 
Action
Use
Fetch Devices
Discover eligible devices for the selected request scope and category.
Analysis
Refresh calculation inputs and calculate target values and row statuses.
Create Job
Create the EVR operational record and, in Automatic mode, create and submit the EVR switching sheet.
Save Case
Store the current request and device solution as a reusable saved case.
EVR Saved Solutions
Open the list of saved EVR cases from the File menu.
Understanding the Request Definition
The request definition controls device discovery, target calculation, job creation, scheduling, and restoration. Review all displayed values before fetching devices and again before creating the job.
 
Field
Operator Guidance
Zone / Region
Select the operating scope for device discovery. One or more zones can be shown, depending on configuration.
Voltage Reduction %
Enter a value greater than 0 and less than 100. EVR applies this percentage reduction to each eligible current setpoint.
Execution Mode
Select Automatic for sheet creation and submission, or Manual to create the event and report only.
Restore Mode
Select Pre-EVR or Nominal. Nominal requires Power Flow.
Device Category
Select All, LTC, or REG to specify which supported device types to find.
Bandwidth Override
Enable a global target bandwidth. Device-specific edits take precedence.
Limit Override
Enable a global target low limit. Device-specific edits take precedence.
Schedule Window
Enable scheduled execution. Confirm that the End Date is later than the Start Date.
Start Date
Time assigned to scheduled reduction blocks.
End Date
Time assigned to scheduled restore blocks when restore generation is configured.
 
Note: Your implementation can display additional request controls. Follow site procedures for any project-specific options not shown in this chapter.
Editing an EVR Request
To define or change an EVR request:
1. Select the Zone / Region and enter the Voltage Reduction %.
2. Select the Execution Mode, Restore Mode, and Device Category.
3. Enable and enter approved bandwidth or low-limit overrides, if required.
4. Enable Schedule Window and enter Start Date and End Date for a scheduled request.
Fetching Devices
Fetch Devices creates or updates the working solution with eligible devices for the current scope and category.
1. Confirm the request definition.
2. Select Fetch Devices.
3. Review the number and type of returned devices.
4. If no eligible devices are returned, verify the selected scope, device category, SCADA control availability, and user access.