A fixed profile is where recent data is compared with very specific thresholds that have been manually set to determine whether the recent usage might be suspect. Depending on the period being monitored will control the granularity that the check is being performed (i.e. hourly, daily or monthly). A number of units for each time interval is specified, and if the actual usage breaches that, then the exception will be raised. This is often referred to as "spike" or "drop" identification.
For example:
- check overnight consumption against a sensitive values to determine whether a low volume of energy is being used overnight as expected
- check monthly consumption against an outline budget that was set at the start of a financial year.
Adding a Fixed Profile Strategy
This basic workflow allows you to capture information and update the status of the Notifications, as per your own business processes. This is expected to be used to help you keep track of any investigative and follow-up actions which are been taken as a result of the Data Monitoring Notifications. For example: Highlight the Notification(s) you would like to update. Notifications can be selected in bulk, even across different strategy types. The Status will default to In Progress and is not editable - the Resolve and Ignore features will update the status. If you want to update the Sub-status, select the required option from the drop down list. The default options are: Pending Resolution You can customise the options available for selection to suite your needs here by using the Database Object Setup activity. You can also create reports in Energy Intelligence to keep track of the Notifications and their status, filtered as required to show the information as per your needs. If you want to update the Note for the Notification(s), then Tick Update Note and enter the note in the text box. Click OK to Save. This will update the status of the Notification to "Ignored" and will also prevent the same notification (for the same period and Impact) from being raised by the system again. If you want to update the Note for the Notification(s), then Tick Update Note and enter the note in the text box. You can view the Channel / amend the interval reading Data associated to the notification, if required. Please note, this option is only available if a single Notification is selected. Highlight the Notification for which you would like to edit the underlying monitoring strategy configuration.Adding Notes to Notifications
which will display the Work Notification pop up:
Ignoring Notifications
to open the Ignore Notifications pop up appears:
Editing Items
to open the Periodic HFD Channel Editor Editing Monitoring Strategies
to open the Monitoring Strategy Editor. Note, this is only an available option if Notification(s) relating to a single strategy are selected.Exporting to Excel
to download an Excel Spreadsheet of everything you see in the table
Fixed Profile Configuration
The bottom section allows you to set the specific fixed profile configuration to use when finding and managing your data.
| Field | Default | Description |
|---|---|---|
| Period to Monitor | Day | This controls the granularity at which the data will be checked against the thresholds that have been set. The options available are:
|
| Low Threshold | Ticked | A tickbox to indicate whether a low thresholds should be performed. This checks whether the recent data drops below the specified thresholds. |
| High Threshold | Ticked | A tickbox to indicate whether a low thresholds should be performed. This checks whether the recent data spikes above the specified thresholds. |
| Threshold Matrix | All values 0 | This matrix will change depending on the Period to Monitor selected. It is where the acceptable low and/or high threshold values are entered for the period of time being monitored (i.e. month of the year, day of the week, or hour of the day). |
| Raise a notification after X consecutive breaches | 1 | This setting allows you to control how sensitive the check is and whether it should only alert you if the issue is a consistent problem. For example, you maybe performing a check for each day of the week. You might only want it to tell you if a problem is found 2 days in a row, in this case this would be set to "2" and it will only raise notifications if the tolerances are exceeded on two consecutive days. |
Visualiser
Once you have set the Low and High thresholds, click 
to give you an example. Please note this is based on sample data to help show how the checks will be performed.
The graph has 5 areas:
- Black line - the sample "actual" channel data
- Green line - the acceptable lower threshold that has been calculated based on the settings in the data monitoring strategy (if it is enabled)
- Blue line - the acceptable upper threshold that has been calculated based on the settings in the data monitoring strategy (if it is enabled)
- Green area - acceptable region (i.e. the area between the acceptable upper and lower region)
- Red area - exception region (i.e. the area between the actual data line and the acceptable upper or lower threshold regions)
The different components of the graph can be enabled or disabled, just click on the different items in the legend which sits on top of the graph on the right hand side.
The visualiser screen also allows you to change the criteria, like in the underlying Monitoring Strategy Editor. Change the settings in the top section of the Visualise Dynamic Profile popup, then click 
Once you are happy with the criteria, click 
to return you to the Monitoring Strategy Editor. Alternatively, you can click Cancel if no changes were made.
Tip: Take note of the line at the bottom of the pop that explains what criteria you have chosen.
Click OK to save the Monitoring Strategy.
Once the Strategy has been set up, Sigma will review the data each night and create any relevant notifications in the Notifications tab