Being able to identify potential problems with your utility usage is absolutely critical to help you manage your energy effectively and help detect avoidable waste. The idea is that you set-up a number of monitoring strategies to notify you whenever an unusual pattern is identified on your periodic channels. This is useful in being able to efficiently determine where your energy usage has gone off trend so that investigative or corrective action can be taken quickly to prevent the exception from happening again and avoid potential waste.
A dynamic profile is where recent data is compared with preceding historical data to determine whether the recent usage might be suspect - i.e. the usage has gone 'off trend'. This is commonly known as precedent based targeting. The system will automatically review the data to notify you of these issues to help prompt proactive investigation to determine whether anything needs to change to bring usage back to something more normal. The sensitivity of these checks and how often they should be performed is entirely configurable. This is often referred to as "spike" or "drop" identification.
- every Monday for the past four weeks has used an average of 100 kWh, but the latest Monday has used 150 kWh.
- the weekly consumption for the previous 2 weeks has been 12,000 kWh, but last week was 15,000 kWh
Adding a Dynamic Profile Strategy
Adding a Monitoring Strategy
From the Strategy Configuration Tab, click
Choose the Strategy Type from the dropdown
Click OK to take you to the Monitoring Strategy Editor
Monitoring Strategy Details
The top section of the Monitoring Strategy Editor is common to all the different monitoring strategy types that can be setup.
The details that need to be entered are as follows:
The field is disabled and displays the Strategy Type being created
|Name||Empty||Enter a name - mandatory|
|Description||Empty||Enter a description - mandatory|
Choose the importance of any notifications that are created against this strategy. Available options are:
Fixed - allows you to drag and drop individual Channels. Click here for more details
Flexible - allows you to configure the set up to automatically include Channels, see below for more details
|Status||Off||Choose On or Off to determine whether the system performs the checks|
|Email||Empty||Tick if you want Sigma to send summary notifications that are raised on a regular basis.|
Enter email address(s) to send a summary notification to.
More than one email address can be entered, and will need to be separated with a comma.
|Send to Site Contact||Empty||Tick if you want to send an email to the Site Contact (entered in the Site Editor) with a summary of notifications that relate to the assets on their site only.|
Note, there are more options depending on which of the above you have chosen, see below for more details on the configuration options.
Channel Context Configuration
It is possible to define which periodic channels the strategy should run for. This will help you ensure your strategies continue to run as your energy estate evolves and assets change/get added.
A monitoring strategy can have a "context" of either:
- Fixed - assign the channels you want the strategy to run for on a case by case basis. Doing it this way will only run for the channels that you have specifically assigned so it will not run against new periodic channels that you might add unless you also specifically assign them to the strategy. Click here for instructions on how to do this.
- Flexible - configure the attributes of the channel that the strategy should run for when setting up the strategy (e.g. run for all channels, run for channels of commodity type x etc.). Doing it this way will help make sure that the strategy will run for the assets you want it to as they evolve or new assets are added - you don't have to specify the periodic channel when you add new ones.
Setting up Flexible configuration:
Choose Flexible from the Context dropdown,
to show the Flexible Context Configuration popup
Tick Yes to run for all Channels
Alternatively, leave as No and choose your own configuration using the dropdown options based on the attributes of the channel and their relates assets.
The available options are: Commodity, Data type, Unit, Site Property Keys, Meter Property Keys, Channel Property Keys.
For example, the above configuration would include all Electricity and Gas Channels that have a unit set to kWh. As new channels that match these parameters are added to your estate, the monitoring strategy would automatically include them when it runs.
Click Save to return to the Monitoring Strategy Editor to continue configuring the Strategy.
If you want to be notified of new issues by email, you can choose how often you should get an email and who the email should be sent to.
Enter the email address(es) you want to send the notification to. Any email addresses entered here will receive a summary of all notifications raised across the entire estate. Note: for more than one email, add a comma between the addresses
Tick Site Contact (entered in the Location tab in the Site Editor). If this option is selected, the site contact will receive an email containing a summary of notifications only for the sites that they are responsible for.
if you want to send an email to the
Recurrence: Choose from Daily, Weekly or Monthly (each option then has further choices for the configuration to configure exactly when the email will be sent).
Emails will contain a summary of new notifications that have been raised since the last email was received. It will also contain a summary of all the outstanding notifications.
Dynamic Profile Configuration
The Monitoring Strategy Editor also contains an Dynamic Profile Configuration section that allows you to set the specific configuration to use when finding and managing your data.
The settings entered here will control how recent data is compared with previous data to determine whether there is an issue. Ultimately, these options provide you with the tools to choose the granularity you want the check to be performed (e.g. aggregated week / day / hour aggregation or half-hourly) and what the system should use as historical data to compare that against.
Whilst each of the fields are explained below in more detail, please click here to jump to a table that provides a some example configurations and (e.g. I want to check a days behaviour with the behaviour on the same days over the last 2 weeks).
|Period to Monitor||Month|
This represents the period of time you want to compare to. Combined with the offset that can be defined, this will determine what the latest data will be compared to.
- Year (i.e. compare to previous year)
- Month (i.e. compare to same period last month)
- Week (i.e. compare to same period last week
- Day (i.e. compare to same period yesterday)
Please note, the period to Monitor selected will drive at what point in time the system will perform the checks and how it determines the latest period of time that is being checked.
- The last full calendar year of data (e.g. 01/01/2018 00:00 to 31/12/2018 24:00)
- The last full calendar month (based on data being available up until 24:00 on the last day of the month)
- The last full week (based on Sunday being the end of the week at 24:00)
- The last full day (based on data being available up until 24:00)
Click here to look at example configurations
|Interval to Monitor||Month|
This represents the interval within that period that you wish to monitor. The options available in the dropdown will depend on the Period to Monitor that has been chosen.
- Half Hour
- 15 Minutes
- Half Hour
- 15 Minutes
Click here to look at example configurations
|Source Profile From||Data Prior to Check Period|
- Data Prior to Check Period - this will compare recent data against the period of time directly prior to the period being checked.
- Data Ending on A Fixed Date - this will compare recent data against the period of time directly prior to the end date that has been specified.
Data Prior to Check Period is chosen...
compare recent data against the period of time directly prior to the period being checked.
|Offset (<period selected>)||1|
Specifying a number greater than one here specifies an offset as to how many prior periods should be skipped when determining the period of time to compare the recent behaviour against.
By default this would be "1" and this means:
- Year - compares against equivalent interval in year directly prior
- Month - compares against equivalent interval in month directly prior
- Week - compares against equivalent interval in week directly prior
- Day - compares against equivalent interval on day directly prior
Some examples where the offset may be changed to something other than "1":
- if a Period of Monthly, if the offset is one, it would compare the last month of data with the month directly prior. However, if you want to compare a month with the same month in the previous year, an offset of 12 could be specified.
- if a Period of Daily is used, if the offset is one, it would compare the last day of data with the day directly prior. However, if you want to compare a day with the same day in the previous week, an offset of 7 could be specified.
|<period selected> to Average||1|
This will define the number of prior periods of time that will be used to derive an average profile which the recent data can then be compared to to determine if it is suspect or not.
For example if the period selected is:
- Daily - it will source the data for equivalent intervals for the previous x days and calculate an average
- Weekly - it will source the data for equivalent intervals for the previous x weeks and calculate an average
Data Ending on a Fixed Date is chosen...
compare recent data against the period of time directly prior to the end date that has been specified.
|Fixed Date||Current Date|
Amend the Fixed date using the arrows or the calendar
|<period selected> to Average||1||As above - it will average the period directly prior to the period ending that has been specified.|
Use the tickbox to the left of the High Threshold label to enable/disable the high threshold check.
The value entered here is effectively the sensitivity of the upper limit that is permitted when the recent data is compared against the historical data (i.e. where the data spikes). This should be considered in conjunction with the type of threshold listed below.
Use the tickbox to the left of the Low Threshold label to enable/disable the low threshold check.
The value entered here is effectively the sensitivity of the lower limit that is permitted when the recent data is compared against the historical data (i.e. where the data drops). This should be considered in conjunction with the type of threshold listed below.
- Percent - this is to say that the exception should be raised if the recent data exceeds the permitted tolerance by a specified percentage
- Units - this is to say that the exception should be raised if the recent data exceeds the permitted tolerance by a specified number of units (e.g. 10 kWh or 5m3)
- Standard Deviations - this is to say that the exception should be raised if the recent data exceeds the permitted tolerance by a number of standard deviations from the mean
|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 daily check against the same day last 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".
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
The table below provides a summary of the different configuration options are available to help clarify how the system can be setup to perform the various checks for you, and what they actually mean.
|I want to be able to...||Period||Interval||Source Profile from||Offset||<Period> to average||Notes|
|compare the consumption for the last full year with the average of the 1 year(s) prior |
|Data Prior to Check Period||1||1|
Change the <period to average> to compare the latest year against the average of the preceding <x> years.
|compare the consumption for the last month with the same month last year|
|Data Prior to Check Period||12||1|
|compare the consumption for the last month with the average of the preceding 3 month(s)||Month||Month||Data Prior to Check Period||1||3||Change the <period to average> to compare the latest month against the average of the preceding <x> months.|
|compare the consumption for the last week with the average of the preceding 1 week(s)|
|Data Prior to Check Period||1||1||Change the <period to average> to compare the latest week against the average of the last <x> weeks.|
|compare the consumption for each day of the last week with the average of the same day for the preceding 2 weeks|
|Data Prior to Check Period||1||2||Change the <period to average> to compare each day against the average of the equivalent day in the preceding <x> weeks.|
|compare the consumption for each half hour with the average of the same half hour in the preceding 4 weeks||Week||Half Hour||Data Prior to Check Period||1||4||Change the <period to average> to compare the latest week against the average of the equivalent period in the last <x> weeks.|
|compare the consumption for each day with the average of the preceding day(s)|
|Data Prior to Check Period||7||1||Change the <period to average> to compare the latest day against the average of the previous <x> days.|
|compare the consumption for each half hour of the day with the average of the equivalent half hour(s) in the preceding 2 days||Day||Half Hour||Data Prior to Check Period||7||2|
Dynamic Profile Notifications
Notifications will be raised that are visible in the Notifications Tab of Data Monitoring.
Each notification will provide key details about the potential problem that has been found. For example, it will include details of the start and end time of the problem and the impact of the the issue (in the units of the applicable channel). The impact is the deviation between the actual usage and the expected usage as per the tolerances that have been set. This will help you identify the problems that have the largest impact and may need following up sooner.
Resolving Dynamic Profile Issues
The "Resolve" functionality ultimately allows you view the potential problem that has been raised in the context of the surrounding data - the problem periods will be clearly highlighted in red, helping you to visualise the impact.
Highlight the applicable Dynamic Profile Notification(s) in the list.
Click to open the Resolve Notifications popup
If you select notifications which include types other than gaps, then a prompt will be displayed to confirm which strategy type you want to work with as the options available are contextual to the type of data issue being worked.
The Resolve Notifications popup will be displayed, showing a list of the Notifications selected for resolution.
The graph at the top shows the profile for the first Notification in the list. Click on others in list to see the graph for that particular Dynamic Profile.
The graph has 5 areas:
- Black line - the actual channel data
- Green line - the acceptable lower threshold that has been calculated based on the settings in the data monitoring strategy
- Blue line - the acceptable upper threshold that has been calculated based on the settings in the data monitoring strategy
- 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.
Drag the mouse around the area to zoom in
to reset the zoom back to the default.
Actions - Dynamic Profile
Work All Notifications
Click Work Notification pop up: which will display the
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:
- Under Investigation
- Assigned to Third Party
- 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.
Ignore All Notifications
, then click to ignore all Notifications.
Ignoring a notification will make sure you are not notified of the same issue again for the same period of time.
Click to return to the Data Monitoring Activity to show a list of the Notifications as per the filter criteria that was previously set.