Location: | pf_sources table |
Required for: | Providing source energization into the model |
Used by: | All ADMS modules to determine energization sources |
Notes: | Generally default data is acceptable though FLA accuracy is dependent on getting impedances correct. |
Location: | pf_loads table; ultimately used in the pf_loads_profile_view, which combines the loads with their load profile data. The pf_loads_profile_view table is a near replica of the pf_loads table with the exception of the profile_id column. If no data exists for a device in the pf_loads_profile_override the profile_id data will come from the pf_loads table but as soon a device is populated with a value in the pf_loads_profile_override table the profile_id data will come from that table instead. Please see the Load Profile Data section below for more information. |
Required for: | Modeling the point of consumption of energy |
Used by: | All ADMS modules to determine where power is utilized |
Usage: | Aside from SCADA measurements, the flow of power around the network is determined by the expected load size at each point of consumption. Therefore accurate load data is particularly important for Load Flow accuracy. Additional the mixture of Constant Power, Constant Current and Constant Impedance load is important in optimization applications for determining optimal configurations. |
Location: | pf_load_interval_data: Contains default, customer class, and/or device specific load profiles. Data within this table can come from the Power Flow Engineering Data workbook and/or the NMS Profile Adapter. Typically default profiles and customer class profiles will be defined in the Power Flow Engineering Data workbook and imported into this table. These records will have a default indicator set within the table. The Profile Adapter can also be setup to write to this table with device specific profiles. The adapter will not touch any profiles that are marked as a default. pf_loads_profile_override: This table is only written to by the NMS Profile Adapter and is used to mark which profiles have been loaded by the adapter and are device specific. This is used to override the value in profile_id within table pf_loads. For example, a load may initially be configured with a profile_id of "Residential" but once the adapter loads a specific profile for the device a value will be placed in table pf_loads_profile_override of "T10520". Once this takes place the view pf_loads_profile_view which is a combination of pf_loads and pf_loads_profile_override will pick up the fact a specific profile is available and the profie_id column will be populated with data from pf_loads_profile_override instead of pf_loads. pf_loads_profile_samples: This table is only written to by the NMS Profile Adapter and is used to track how many times different day type/hour/temperature combinations have been sampled. The frequency at which certain data points have been sampled is used in the averaging algorithm by the adapter. |
Required for: | Modeling the changes in load consumption over time and temperature |
Used by: | All ADMS applications to improve the accuracy of power flow. Particularly important for applications where future forecasts are required, these are: Feeder Load Management, FLISR, Suggested Switching and Optimization |
Notes: | Load profile data is used to model how load changes over time. A single load profile represents the change in load levels over a 24-hour period. Multiple profiles may be associated with a single load to represent different load behavior for different types of day (for example, weekday, weekend) and for different temperatures (for example, 80°F - 90°F, 90°F - 100°F). The use of load profile data improves the accuracy of the DMS applications by providing more realistic loading scenarios for the current or predicted analysis time period. For example, profiles are used to verify switch plans, determine suggested switching recommendations, and generate daily and seasonal peak limit alarms. The Oracle Utilities Network Management System supports a variety of sources of load profile data such as load class profiles or individual transformer profiles. Once processed, all profile data is placed in the pf_load_interval_data table. For load class profiles, the profile_id column in the pf_loads table can be set to point to the appropriate data in the pf_load_interval_data table. For transformer specific profiles, the adapter will populate a table pf_loads_profile_override; this table will be used to specify which transformers have specific profiles as opposed to just load class profiles. Anything defined in the pf_loads_profile_override table will override the profile_id field in the pf_loads table. Please see the "Modeling Loads" section in Chapter 8 of the Oracle Utilities Network Management System Configuration Guide for more information. |
Location: | pf_xfmrs, pf_xfmrs_tanks table, pf_xfmr_limits for seasonal, temperature, and dynamic ratings. |
Required for: | Modeling the locations where voltage is changed and/or regulated |
Used by: | All ADMS applications to determine accurate voltage levels across the network Feeder Load management and FLISR to generate overload and voltage violations. Optimization to determine regulation parameters for optimal network configuration. |
Notes: | Some data (for example, regulation parameters) can be defaulted if voltage accuracy is not critically important. FLA requires accurate impedance information to correctly determine fault currents • As of NMS v2.4+, projects will not be required to populating indicators specifying if grounds or neutrals are present on the primary and secondary windings. This information will be inferred from the transformer winding type specified for each device. The various winding types supported and details about the grounding information can be found in the Power Flow Engineering Data workbook. • As of NMS v2.5+, two new transformer winding types have been made available for unique cases. A Zigzag winding has been added which is a single winding transformer that can be used as a grounding bank to create a grounding point on delta configured circuits. The second new type is a Scott winding that takes 3 phases at 120Degree rotation and converts to 2 phases with 90Degree rotation. • The following configuration will be needed if transformers operate at a different voltage level than the system base. The primary and secondary ratios will need to be adjusted for the voltage the transformer outputs at the neutral tap position. The voltages configured for the unit should be based on what the voltages base that should be used for displaying results. For example, if a transformer had voltages levels from 138kV to 13.8kV on network at a 13.2kV system base, the primary ratio would be set to 1, the secondary ratio set to 1.04, the primary voltage would be set to 138kV, and the secondary voltage set to 13.2kV. If the device is auto regulating, the voltage target would then be set in P.U. based on a 13.2kV system base. With this scenario, the transferrer would output 13.8kV assuming no load and a 138kV input at the neutral LTC position. The power flow details would indicate this in the balloon as 1.04P.U. based on a 13.2kV system base. |
Location: | pf_capacitors table |
Required for: | Power flow, in particular to determine reactive power flow |
Used by: | All DMS applications to determine accurate load flow. Optimization to determine regulation parameters for optimal network configuration. |
Notes: | Capacitors have significant impact on power flow. The reactive flow around the network affects current magnitude, voltage and power factor. Some data (for example, regulation parameters) can be defaulted if voltage accuracy is not critically important. Capacitors must be modeled shunted off the feeder. The device should either be directly connected to the feeder or with a handful of devices to create a simple path between the device and feeder (for example, conductors and switch). If things like bypasses or junctions exist between the capacitor and feeder the NMS tracing during power flow services (PFService, FLMService, FLTService, and VVOService) startup may not be able to properly identify the monitored device for regulation. By default, amp and var regulating capacitors monitor the flow near the connection point. If the default location is incorrect, the actual metering location can be specified in the source data. |
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. |
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. |
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. |
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. |