Configuring the Energy Modeling report

Before you can use the modeling report, you must first create a model for your facility or process with the Create Model Report. This model is then used in the Use Model Report. You only use the Create Model report during configuration. After the model has been created, you do not need to run this report again, unless you want to create a new model.

To create a model and use the Energy Modeling report:

  1. Run the Create Model report with an initial set of parameters and analyze the results. Select No for the Save Model Configuration input parameter.

    TIP: Consider choosing a reporting period with normal consumption behavior to create your model. For example, a good period could be "Last Year".

  2. Based on the results, define sub-models and exception periods, if applicable.
  3. Re-run the Create Model report using sub-models, exception periods, and modified input parameters and analyze the results.
  4. Repeat steps 2 and 3 until you are satisfied with the accuracy of the model.
  5. Run the Create Model report one more time, select Yes for the Save Model Configuration and enter a meaningful model name. This saves your model to the database.
  6. Run the Use Model report with the model you created. Ensure that the sub-models and exception periods are correctly defined for the reporting period.
  7. (Optional) Setup a subscription to run the Use Model report on a regular basis. Select Yes for the Insert Date input parameter. This saves the model output data to the database. You can use this data in the Trends and Dashboards applications.

Defining a sub-model

Sub-models are used to improve the accuracy of the overall model by recognizing time intervals or operating conditions with different consumption characteristics. For example, using a sub-model that differentiates between weekdays and weekend days can be more accurate for processes that are influenced by a workweek pattern, than using a single model for all days. Which sub-model works best depends on the nature of the facility or process.

Sub-models are defined with the Modeling Configuration tool in the Settings > System > Modeling area of the Web Applications. Use one of the pre-defined sub-models or create your own.

To define a sub-model:

  1. In Modeling Configuration, select the Sub-Models tab.
  2. Click Insert in the top right corner of the window to switch to insert mode.
  3. Enter a Sub-Model Name, select a Minimum Aggregation Interval, and enter a Desired Label, and Condition in the input boxes at the top of the main display grid.

    The Condition must be a valid SQL query statement.

  4. Click Insert to the right of the input boxes to insert the new sub-model definition. The definition is moved to the bottom of the main display grid, below any pre-existing sub-model definitions.
  5. Click Search in the top right corner of the window to switch back to search mode.
  6. (Optional) To edit an existing definition, click Edit to the right of the definition in the display grid, or click any of the fields of the definition in the grid. To update the definition, after editing it, click Update , to cancel click Cancel . To delete a sub-model definition, click Delete .

Defining exception periods

Exception periods are special time intervals, such as holidays, with unpredictable consumption behavior that is different from the rest of the time period. Exception periods can be defined down to a specific time interval for a specific source and measurement.

You can either choose to model these exception periods separately, which means they will become a sub-model, or you can choose to exclude them from the model completely.

Exception periods override sub-model definitions if they cover the same time period. For example, you could define a holiday, a day your facility was in shutdown, or a day when you performed system tests, as an exception period. If that day was a weekend day and you are using a sub-model to differentiate between weekdays and weekend days, then the exception period overrides the sub-model, which means that special day will be modeled differently than a regular weekend day.

Exception periods are defined with the Modeling Configuration tool in the Settings > System > Modeling area of the Web Applications.

To define exception periods:

  1. In Modeling Configuration, select the Exception Periods tab.
  2. Click Insert in the top right corner of the window to switch to insert mode.
  3. Enter an Exception Period Name, select a Source and Measurement, enter a Desired Label, and Condition in the input boxes at the top of the main display grid.

    The Condition must be a valid SQL query statement.

    NOTE: The Desired Label is used to control if the exception period is excluded from the model, or if it is treated as a sub-model. Enter the text Delete as Desired Label if you want to exclude that period from the model. Enter any other text, for example a descriptive text such as Holiday, if you want to sub-model the exception period. An excluded exception period will be blank in the final model output graphic.

  4. Click Insert to the right of the input boxes to insert the new exception period definition. The definition is moved to the bottom of the main display grid, below any pre-existing exception period definitions.
  5. Click Search in the top right corner of the window to switch back to search mode.
  6. (Optional) To edit an existing definition, click Edit to the right of the definition in the display grid, or click any of the fields of the definition in the grid. To update the definition, after editing it, click Update , to cancel click Cancel . To delete an exception definition, click Delete .

See a Model creation example.