Configuration
The script expects CSV files in the directory configured by forecastDir (default: $OPERATIONS_MODELS/derms_forecasts). Processed files are moved to its parsed_csvs subdirectory, and errors are logged in $OPERATIONS_MODELS/derms_forecasts/log.
The CSV formats are configured in PF_DERMS_ADAPTER_CONFIG, including column counts, column positions, header handling, and filename tokens. DER bid CSV files use dermsBidNumDataCol and dermsBidColumnMap. DOE schedule CSV files use dermsDOENumDataCol and dermsDOEColumnMap, and their filenames must contain dermsDOEFileToken (default: _doe), for example DER_BESS_1001_doe.csv. Token matching is case-sensitive. DOE schedules and traditional DER forecasts both have four columns by default, so column count alone cannot distinguish them.
If the input is an RDBMS table, then the forecast updates are expected in a database table. If the adapter is running on enterprise service network, then the forecast updates are expected in the DERMS_FORECAST_UPDATES table. If the adapter is running on operational service network, then the forecast updates are expected in the PF_DERMS_FORECAST_UPDATES table.
External Load and Gen Forecast CSV files are identified using the configured column count and the externalLoadGenFileToken filename token (default: ExternalForecast). The token is configured in PF_DERMS_ADAPTER_CONFIG and matched case-sensitively against the filename; it is not a filename extension.
PF_DERMS_ADAPTER_CONFIG
 
Name
Data Type
Description
parameter_name
VARCHAR2(32)
The name of the parameter. Required.
parameter_value_1
VARCHAR2(64)
Required parameter value.
parameter_value_2
VARCHAR2(64)
Optional parameter value.
parameter_value_3
VARCHAR2(64)
Optional parameter value.
 
The following parameters are configured in PF_DERMS_ADAPTER_CONFIG:
Parameter
Description
sourceDBServiceName
Sets the database service name, server name, and port details for the forecast updates table.
• parameter_value_1: server name. The default value is DB.
• parameter_value_2: port number.
• parameter_value_3: database service name.
operationalService
Sets whether the adapter is running on the operational service network or the enterprise service network.
• parameter_value_1: Yes | No
• Yes: operational service network
• No: the enterprise service network
useSqlLoader
Sets whether to use SQL Loader or NMS Import to load the data into NMS tables.
• parameter_value_1: Yes | No
• Yes: SQL Loader
• No: NMS Import or other process
forecastDir
The directory containing the forecast CSV file.
numDataCol
Define rule to specify the number of columns in raw CSV
dermsBidColumnMap
Defines the CSV columns.
• parameter_value_1: column name.
• parameter_value_2: column number.
 
The column numbering starts with 0, which is the first column in the table. The standard configuration is defined as follows:
 
• Column 0 = ForecastDate (mm/dd/yyyy HH24:MI:SS).
Note: All time stamps should be provided in Coordinated Universal Time (UTC).
• Column 1 = ResourceName
• Column 2 = Availability Pricing
• Column 3 = Utilization Pricing
• Column 4 = Bid kW
• Column 5 = Bid kVAr
• Column 6 = Minimum Output
dermsColumnMap
Defines the CSV columns.
• parameter_value_1: column name.
• parameter_value_2: column number.
 
The column numbering starts with 0, which is the first column in the table. The standard configuration is defined as follows:
 
• Column 0 = ForecastDate (mm/dd/yyyy HH24:MI:SS)
Note: All timestamps should be provided in Coordinated Universal Time (UTC).
• Column 1 = ResourceName
• Column 2 = PowerSourceType
• Column 3 = ForecastValue
forecastColumnMap
Defines the CSV columns for External Load and Gen CSV file
• parameter_value_1: column name.
• parameter_value_2: column number.
 
The column numbering starts with 0, which is the first column in the table. The standard configuration is defined as follows:
 
• Column 0 = ForecastDate (mm/dd/yyyy HH24:MI:SS)
Note: All timestamps should be provided in Coordinated Universal Time (UTC).
• Column 1 = ResourceName
• Column 2 = ForecastSource
• Column 3 = Forecastobject
• Column 4 = ForecastkW
• Column 5 = ForecastkVAR
headerPresent
Sets whether the CSV file has a header row or not.
• parameter_value_1: Yes | No
forecastnumDataCol
Define rule to specify the number of columns in External Load and Gen CSV file
dermsBidNumDataCol
Define rule to specify the number of columns in the DERMS Bid data CSV file.
dermsBidColumnMap
Defines the CSV columns.
• parameter_value_1: column name.
• parameter_value_2: column number.
 
The column numbering starts with 0, which is the first column in the table. The standard configuration is defined as follows:
 
• Column 0 = ForecastDate (mm/dd/yyyy HH24:MI:SS)
Note: All timestamps should be provided in Coordinated Universal Time (UTC).
• Column 1 = ResourceName
• Column 2 = AvailabilityPricing
• Column 3 = UtilizationPricing
• Column 4 = BidKw
• Column 5 = BidKvar
• Column 6 = MinimumOutput (minimum capable output for DER)
dermsDOENumDataCol
Number of columns in a DOE schedule CSV file. parameter_value_1 defaults to 4.
dermsDOEFileToken
Case-sensitive filename token identifying DOE schedule CSV input. parameter_value_1 defaults to _doe. Include this token in every DOE CSV filename, for example market_doe.csv.
dermsDOEColumnMap
Maps DOE fields to zero-based CSV column positions.
• parameter_value_1 is the field name; parameter_value_2 is the column number.
 
Defaults: ForecastDate = 0 (MM/DD/YYYY HH24:MI:SS, UTC);
ResourceName = 1; MaxImportKw = 2 (maximum import capacity in kW); MaxExportKw = 3 (maximum export capacity in kW).
externalLoadGenFileToken
Case-sensitive filename token for External Load and Gen Forecast CSV files.
parameter_value_1 defaults to ExternalForecast. This replaces the filename discriminator formerly configured by LOAD-GEN_EXTERNAL_INPUT_FILE_FORMAT.
vppScheduleFileToken
Identifies authoritative eVPP schedule CSV and JSON files by a token in the filename. The default is _vpp_schedule.
Place these files in the directory configured by forecastDir.
DOE Schedule CSV Format
Provide hourly DOE limits in the following default column order:
ForecastDate,ResourceName,MaxImportKw,MaxExportKw
ForecastDate is the start of the hourly period in MM/DD/YYYY HH24:MI:SS format, in UTC. ResourceName must match a GEN_NAME in PF_DIST_GEN. Import and export limits are in kW; represent an import (charging) limit as a negative value and an export limit as a positive value. Use zero when no import or export capacity applies.
Example data rows for DER_BESS_1001_doe.csv:
10/28/2026 00:00:00,DER_BESS_1001,-1500,3000
10/28/2026 01:00:00,DER_BESS_1001,-1200,2500
 
The example has no header, matching the product headerPresent default of no. If headerPresent is yes, prepend the field-name row shown above. Header handling must be consistent across all input CSV files. Adjust example dates to the forecast window accepted by the adapter and use a resource name present in the target model.
eVPP Schedule File Formats
CSV files must use this exact header:
external_id,operation,start_time,end_time,mw_reduction,mvar_reduction,price_per_mw
Use one or more REPLACE rows to supply the complete schedule for an external ID, or one CLEAR row to remove its complete schedule. Do not combine CLEAR and REPLACE rows for the same external ID.
JSON files must contain a top-level vpps array. Each entry contains externalId and a schedules array. Each schedule contains startTime, endTime, mwReduction, optional mvarReduction, and optional pricePerMw.
Start and end times must be offset-aware ISO-8601 timestamps; timestamps are normalized to UTC. End must be after start. Reduction values are in MW and MVAr. Positive values reduce managed load and negative values increase managed load. Price is optional informational dollars per MW.