Data Tables

A custom MetrixND project must have the following data tables to be used as a Custom Model in the LT Load Forecasting Application. All data tables must have a Monthly periodicity and should not have a check in the Active Link check box for the variables.

When MetrixND projects are accessed by the Lont-Term module, each data table is updated with a record set compiled from the applicable data in the Project Database. Start and End dates for the record set are specified by the Estimation Start and End dates and the time span of the available data.

MonthlyData. When MetrixND projects are accessed by the Lonf-Term module, the MonthlyData table is updated with a record set compiled from the monthly load data determinants in the project database. The MonthlyData table:

  • Must be named "MonthlyData".
  • Must have the following variables: Hours, HLHHours, Energy, HLHEnergy, LLHEnergy, NCP, CP, Minload, TTSL, GSP, CA.

MonthlyWeather. This data table contains monthly weather data. When MetrixND projects are accessed by the Lonf-Term module, the Monthly Weather table is updated with a record set compiled from the LTWTHRDEGREEDAYDATA table. The Monthly Weather Data table:

  • Must be named "MonthlyWeather".
  • Must have the following variables: HDD50, HDD55, HDD60, HDD65, CDD60, CDD65, CDD70.

PeakWeather. This data table contains peak-day weather data. When MetrixND projects are accessed by the Lonf-Term module, the Peak Weather table is updated with a record set compiled from the LTWTHRPEAKAYDATA table. The Peak Weather Data table:

  • Must be named "PeakWeather".
  • Must have the following variables: CPAvg, CPLag, NCPAvg, NCPLag, TTSLAvg, TTSLLag, GSPAvg, GSPLag, CAAvg, CALag.

XVariables. XDriver variables and Model predicted values can be utilized in both Standard and Custom models as factors in the model. For custom models, a MetrixND table must be configured in the model template for each XDriver or Model that is assigned. For XDriver variables, there are specific naming conventions for the data tables and variable names that must be used in the MetrixND template.

  • XDriver variables. Each XDriver has a type, and only specific types are available to be used as model variables (e.g., Standard1, Standard2, and Standard3). The user can only add one variable of each type into a model. The internal data table in MetrixND must have a name that is the same as the XDriver type (e.g., Standard1, Standard2, or Standard3). There must be exactly one data variable in each table, also named the same as the XDriver type (e.g., Standard1, Standard2, or Standard3).
  • A single model can also be assigned to be used as a source of explanatory variables. The internal data table in MetrixND must have the name Model1 and the variable names in this data table must match the list of the modeling concepts: Hours, HLHHours, Energy, HLHEnergy, LLHEnergy, NCP, CP, MinLoad, TTSL, GSP, CA in that order.

ScenarioHours. The Scenario Hours data table contains the number of hours and high-load hours for each forecast month. When MetrixND projects are accessed by Lonf-Term module, this table is automatically updated. The Scenario Hour Data Table:

  • Must be named "ScenarioHours".
  • Must have the following variables: HOURS, HLHHOURS.

ScenarioMonthlyWeather. This table contains the monthly scenario weather data. This table is populated by the Lonf-Term module using the LTWTHRDEGREEDAYSCENARIO table for the selected scenario (base-scenario in the Models Module) for the long-term forecast. The Scenario Monthly Weather table

  • Must be named "ScenarioMonthlyWeather".
  • Will have the same variables as the MonthlyWeather data table.

ScenarioPeakWeather. This table contains the monthly scenario peak day weather data. This table is populated by the Lonf-Term module using the LTWTHRPEAKDAYSCENARIO table for the selected scenario (base-scenario in the Models Module) for the long-term forecast. The Scenario Peak Weather table

  • Must be named "ScenarioPeakWeather".
  • Will have the same variables as the PeakWeather data table

PeakData. This table contains daily peak data to support the use of multiple peak days in each month. This daily table is populated with the peak day data (Peak1, Peak2, …) for the peak days in each month and missing values for the non-peak days. The data will be populated on the first N days of the month. That is, the highest peak will be in the first of the month, the next highest value will be in the second of the month, and so forth.

  • Must be named "PeakData".
  • Will have two variables, Peak and Bad.

PeakDates. This table contains dates of each of the N Peaks. This table is used to line up the daily weather data for each of the N Peaks. This occurs on the StandardDailyPeakWthr transform table. The data will be populated on the first N days of the month. That is, the highest peak will be in the first of the month, the next highest value will be in the second of the month, and so forth.

  • Must be named "PeakDates".
  • Will have one variables, PeakDate.

DailyDryBulb. This daily table contains temperature data to support the use of multiple peak days in each month. This daily table is populated for all days, but data only get used in the models for the peak days and the days immediately prior to the peak days.

  • Must be named "DailyDryBulb".
  • Will have four variables, MaxVal, MinVal, AvgVal, Bad.

Scenario XVariables. Scenario versions XDriver variables and Model predicted values can be utilized in both Standard and Custom models as factors in the model. For custom models, a MetrixND table must be configured in the model template for each XDriver or Model that is assigned. For XDriver variables, there are specific naming conventions for the data tables and variable names that must be used in the MetrixND template.

  • XDriver Variables. Each XDriver has a type, and only specific types are available to be used as model variables (e.g., Standard1Scen, Standard2Scen, and Standard3Scen). The user can only add one variable of each type into a model. The internal data table in MetrixND must have a name that is the same as the XDriver type (e.g., Standard1, Standard2, or Standard3). There must be exactly one data variable in each table, also named the same as the XDriver type (e.g., Standard1, Standard2, or Standard3).
  • A single model can also be assigned to be used as a source of explanatory variables. The internal data table in MetrixND must have the name Model1Scen and the variable names in this data table must match the list of the modeling concepts: Hours, HLHHours, Energy, HLHEnergy, LLHEnergy, NCP, CP, MinLoad, TTSL, GSP, CA in that order.

Bad. If present, the Bad table contains Year and Month fields and a field for each of the model types. A 1 in the column for a particular model indicates the data has been marked as bad and should not be used for model-estimation. The Bad data table is updated with a record set compiled from monthly load data table. The Bad table:

  • Must be named “Bad”.
  • Must contain one Bad variable for each Model type with the following variable names: ENERGY, NCP, CUSTOMER_CF, GSP_CF, TTSL_CF, CA_CF, HLHFRAC, and MINRAT.