Capacitor Control Configuration
Capacitors can be configured with up to three controls: emergency control (control_e), Normal Control 1 (control_1), and Normal Control 2 (control_2). These controls determine when a capacitor switches ON or OFF. The configuration parameters are stored in the pf_capacitors table.
Control Types
The following control types are supported:
Control type
Description
0
Fixed
1
Voltage Regulated
2
Time Switched
3
Temperature Switched
4
Current Switched
5
VAR Switched
6
Power Factor Switched
7
Fixed Manual (Reserved for OPF)
8
Season Switched
Control Evaluation
Emergency control has the highest priority. If emergency limits are violated, the capacitor immediately switches ON or OFF according to the emergency thresholds.
In most OPAL implementations, Voltage Regulated control (Type 1) is configured as the emergency control. The capacitor turns ON when voltage falls below the ON threshold and turns OFF when voltage rises above the OFF threshold.
When the measured value lies between the emergency thresholds, the capacitor state is determined by Normal Control 1, Normal Control 2, the configured AND/OR logic, and Local Voltage Control (LVC). Normal controls are evaluated only when LVC is enabled.
AND logic: The capacitor turns ON when both normal controls are ON and turns OFF when both are OFF. If the normal controls have different ON/OFF results, the capacitor remains in its current state (indeterminate).
OR logic: The capacitor turns ON when Normal Control 1 is ON and turns OFF when both normal controls are OFF.
Time Based Control
Time-based control (Type 2) switches a capacitor ON and OFF according to a predefined day and time schedule. This control can be used where capacitor operation follows predictable daily or weekly load patterns.
To enable time-based control, set control_type_1 to 2. The ON and OFF thresholds specify switching times in HHMM format, where HH is the hour from 00 to 23 and MM is the minute from 00 to 59.
 
Parameter
Description
control_type_1
Set to 2 to enable Time Switched control.
ON_DAY
Day on which the capacitor turns ON. Values 0 to 6 represent Sunday through Saturday; 7 represents all days.
OFF_DAY
Day on which the capacitor turns OFF. Values 0 to 6 represent Sunday through Saturday.
control_1_on
ON time in HHMM format.
control_1_off
OFF time in HHMM format.
TimeVarOffDays
Flag specifying the days on which the capacitor remains OFF. Applies to both continuous weekly and specific day-based schedules.
Note: If TimeVarOffDays is set to 127, the capacitor will never turn ON when time-based control is configured.
Continuous Weekly Logic
If ON_DAY and OFF_DAY are not configured, the capacitor evaluates the configured ON and OFF times every day of the week. The weekday portion of the schedule is treated as any day, and TimeVarOffDays remains the only day-based filter.
Specific Day Based Logic
If ON_DAY and OFF_DAY are both configured, the capacitor turns ON at the specified ON_DAY and control_1_on time, and turns OFF at the specified OFF_DAY and control_1_off time. TimeVarOffDays continues to apply to the schedule.
Time Based Control Examples
Continuous Weekly Schedule
For example, the following configuration operates the capacitor every day from 02:00 to 15:00:
control_type_1 = 2
TimeVarOffDays = 0
ON_DAY = <not set>
OFF_DAY = <not set>
control_1_on = 0200
control_1_off = 1500
TimeVarOffDays can be used to block operation on specific days.
Specific Day Schedule
The following configuration operates the capacitor from Tuesday at 02:00 until Wednesday at 15:00:
control_type_1 = 2
TimeVarOffDays = 0
ON_DAY = 2
OFF_DAY = 3
control_1_on = 0200
control_1_off = 1500
Season Based Control
Season-based control (Type 8) allows a capacitor to operate within a defined date range during the year. This control can be used to manage reactive power support during seasonal load variations.
To enable season-based control, set control_type_2 to 8. The ON and OFF thresholds specify the start and end dates in MMDD format, where MM is the month and DD is the day. The capacitor switches ON at the configured start date and OFF at the configured end date.
 
Parameter
Description
control_type_2
Set to 8 to enable Season Switched control.
control_2_on
Start date in MMDD format.
control_2_off
End date in MMDD format.
TimeVarOffDays
Flag specifying the days on which the capacitor remains OFF within the season.
For example, the following configuration operates the capacitor between March 1 and April 1:
control_type_2 = 8
control_2_on = 0301
control_2_off = 0401
Distributed Energy Resources (DERs)
 
Location:
pf_dist_gen table
Required for:
Power flow, in particular to determine real power flow as impacted by distributed generation
Used by:
All ADMS applications to determine accurate load flow.
FLISR to determine phantom load during restoration.
Notes:
DERs have significant impact on power flow. The real power flow around the network affects current magnitude, voltage and power factor.
DER has the effect of masking load. If the DER supply is suddenly removed (for example, IEEE1547 disconnection rules) the network will suddenly have to cope with significant extra load.
Some data (for example, regulation parameters) can be defaulted if voltage accuracy is not critically important.
Distributed Energy Resource Profiles
 
Location:
pf_load_interval_data: Contains generation output curves for the configured DER within the model. The curves can be configured for a combination of DER type and/or device specific profiles. For example a PV panel could have multiple profiles to represent various output levels of cloud cover density. A diesel generator however may have various profiles to show percentage output.
pf_weather_zone_forecast: Contains the DER forecast for the weather affected DERs. This table will contain a key to the profile that should be used for the day and hour. For example it may specify to use the cloudy profile from 9am-12pm for the PV panels for a particular weather zone, then use from the partly cloudy profile from 12pm-3pm, and finally use the sunny profile from 3pm-6pm. The forecast data configured identifies the pieces of each profile configured in pf_load_interval_data to use for the specified date and time.
pf_der_forecast: Contains the DER forecast for non-weather affected DERs that have their own forecast schedule. For example it would be common to see utility scale batteries and gas based generators within this table. Similar to the pf_weather_zone_forecast table this contains profile keys that that map to which piece of the profile to use the specified date time.
pf_demand_response_forecast: Contains the demand response (DR) forecast for the various DR groups that have been configured within NMS. Similar to the pf_weather_zone_forecast table this contains profile keys that map to which piece of the profile to use the specified date time.
Required for:
Modeling the change in DER generation for different fuel types and varying weather conditions. For example a PV panel could have multiple profiles to represent various output levels of cloud cover density. A diesel generator however may have various profiles to represent percentage output.
Used by:
All ADMS applications to improve the accuracy of power flow. Particularly important for applications where future forecasts are required; specifically, Feeder Load Management, FLISR, Suggested Switching, and Optimization.
Notes:
Each DER is mapped to a particular fuel type (for example, Solar, Wind, Gas, and so on) and unique profiles can be provided to define how a particular fuel type behaves for varying conditions. For example solar profiles could be built for different degrees of cloudiness ranging from clear to cloudy that can be used to simulate how solar DERs behave. A customer also has the ability to also configure the weather zone that each DER belongs to and a forecast can be provided to each zone. For example it's partly cloudy, wind 10-15mph, 70F in the mountain zone but in the coastal zone it's sunny, wind 0-5mph, 80F. A customer has the ability to configure as few or as many weather zones as needed and can build DER profiles for varying conditions as well.
Oracle NMS provides a productized profile adapter that is capable of creating solar profiles based on the time of year and location of the utility. The curves generated by the adapter reflect a normalized output and within the power flow analysis are applied against the device specific kW output. The number of PV profiles generated to represent various levels of cloud density is configurable based on the customers' business requirements.
Switches and Fuses
 
Required for:
Generation of violations, Network Protection
Used by:
All ADMS applications that check violations. This includes: Feeder Load Management, FLISR, Suggested Switching and Optimization. Also used by topology processor for modelling Network Protector operations
Notes:
Predicting and reporting on violations is a core advantage of a DMS system. Having accurate ratings and protection settings will allow the applications to generate meaningful violations.
Data can be defaulted to reasonable values. Alternatively, they can be modeled as "Zero Impedance" devices to stop violation checking.
It should be noted that for protective devices that open to clear faults such as breakers, reclosers, and fuses the minimum pickup current should be used. For example a breaker may be rated for 2000Amps but the relay is configured to trip at values greater than 600Amps, in this situation a value of 600Amps should be configured for the devices normal, emergency short term, and emergency long term ratings.
For non-protective devices, the max continuous current rating of the device should be used which would represent the maximum amount of the current the device could handle before failing. If desired, a separate emergency short term and long term limit could also be provided for non-protective devices. These values would represent a limit that could be sustained for a short duration of time (for example, 2-4 hours for short term and 24 hours for long term).
Within NMS, capability exists to dynamically determine if protection reach issues exist on feeders. This occurs when the fault current on portions of a feeder are lower than the minimum pickup settings configured for the relay. In this situation the fault current would not be seen as fault current and the device would not open to clear the fault. This can occur when feeders are switched abnormally and the length extended by picking up portions of adjacent feeders. To take advantage of this functionality customers will need to configure the minimum pickup current for ground faults and for phase to phase faults for protective devices. For non-protective devices or if this is not desired functionality the values can be left null.
NMS has the ability to model Network Protection trip/reclose operations. Network Protectors are modelled as switches using optional columns in the pf_switches table.
Conductors
 
Location:
wire_size column of network_components table, pf_line_catalog
Required for:
Accurate determination of voltage in load flow applications, and the effects on short circuit currents.
Used by:
All ADMS applications that check violations. This includes: Feeder Load Management, FLISR, Suggested Switching and Optimization.
Applications where voltage change is important: Optimization
Applications where impedances are important: FLA, Protection Reach
Notes:
Conductor data has significant impact on most DMS applications.
Losses introduced by conductor impedances affect voltages throughout the network. Accurate conductor impedance data is critical for these applications.
Impedance data can be provided directly. It can also be calculated (by the Powerflow Engineering workbook) from construction data using Carson's modified equations.