I’m developing a forecast that requires base, high, and low scenarios.  After building the base scenario, the high and low scenarios are created by duplicating the base scenario process, changing the tables names from “Base” to “High” or “Low” and updating the equations.  The result is a structure where the variable names are identical, but the table names indicated the scenario as shown below.

 

Using this structure, I build a Report Object that exports the Residential Sales variables for comparison in a summary MetrixND file.  I create the Report object by dragging and dropping the variables into a single Report.  The comparison Report of the Residential sales is shown below.

 

I like to import the Report into a second MetrixND project file so I can develop comparison graphs and objects.  Using a second MetrixND project file helps me reduce the clutter of my project files pushing diagnostic and summary information away from my primary forecast models and variable development.

 
The problem is that the Report cannot be imported into a second MetrixND project file.  When I attempt to import the table, I get the following error because the three variables are named “Residential”.  The import process does not recognize that the variables come from different tables.

 

 

To solve the problem, I use the “In-Line” transformation in the Report Object.  In the Report Object, “right-mouse-click” to bring up the “Insert Inline Transform” option.

 

Selecting this option initiates the “Edit Transform” dialogue box.  To obtain the same results as before, I define a unique name (e.g. High) and set the formula to equal the High Residential sales variable.

 

Replicating the process three time (i.e. for High, Base, and Low), I construct the same Report Object as before, but I now have unique names for the Residential forecast values.

 

This Report can now be imported into a second MetrixND project file or the new Forecast Manager system.  The In-line transform feature of the Report Object is a useful to rename variables, create equations, or summarize results prior to exporting the data.  The ability to create new names makes the report a powerful tool for connecting a MetrixND project file to MetrixLT or Forecast Manager.

 

 

Mark Quan on EmailMark Quan on Linkedin
Mark Quan
Principal Forecast Consultant - Itron
Mark Quan is a Principal Forecast Consultant with Itron’s Forecasting Division. Since joining Itron in 1997, Quan has specialized in both short-term and long-term energy forecasting solutions as well as load research projects. Quan has developed and implemented several automated forecasting systems to predict next day system demand, load profiles, and retail consumption for companies throughout the United States and Canada. Short-term forecasting solutions include systems for the Midwest Independent System Operator (MISO) and the California Independent System Operator (CAISO). Long-term forecasting solutions include developing and supporting the long-term forecasts of sales and customers for clients such as Dairyland Power and Omaha Public Power District. These forecasts include end-use information and demand-side management impacts in an econometric framework. Finally, Quan has been involved in implementing Load Research systems such as at Snohomish PUD. Prior to joining Itron, Quan worked in the gas, electric, and corporate functions at Pacific Gas and Electric Company (PG&E), where he was involved in industry restructuring, electric planning, and natural gas planning. Quan received an M.S. in Operations Research from Stanford University and a B.S. in Applied Mathematics from the University of California at Los Angeles.