A major focus of the Info360 2019.1 release is reporting on the health of the sensor network and ability to perform with larger sets of data. With that in mind, several features have been implemented to streamline performance and data management as data continues to grow.

You will also notice that the user interface has been updated with a home page used to access the sensor health page, alerts, and analytics modules.

Sensor Health

Info360 now comes with a web page for reporting the health of your system as defined by connection status to the historian, agents, and individual sensors. This serves as a live dashboard to indicate whenever there are sensor problems that should be addressed.

Learn more here.

Data Authoring

Sensors can often report faulty data which cause problems in reports and analytics. Info360 now offers the ability to view and manually correct the data that is stored in the database. This feature is only available to users with Admin or Power User role permissions.

To get started, maximize a Historic Chart and click Authoring mode.

Learn more here.

Enhanced Analytics Environment

Biz Blocks are powerful customizable analytics tools, but it can be cumbersome to duplicate a set of equations for every zone of your system with varying inputs. To improve that workflow, we have created a multi-use analytics platform called "Tools" which can be found on the home page. It is now easy for us to generate an analysis process for any common procedure and add it on the back end to existing sites. If you have any requests for repeatable, common analysis procedures, let us know! We're happy to set something up and share it with your team. Over time as our user-community grows we'll be able to build a library of helpful tools. Keep an eye out for updates!

One key step in this process is the added ability to apply functions to groups of sensors. We've come across many cases where an analysis includes several input sensors, and when duplicating to other zones or areas, the number of sensors changes. Previously this requires manually updating the equations to include each sensor. Now the analysis can apply to a group of sensors, and when duplicated to another zone you just need to update to a new group of sensors.

The following new functions can perform analysis on multiple sensors:

  • MinList: MinList (TimeSeries, TimeSeries1,...) - Calculates the minimum value amongst list values in each time step.

  • MinIfList: MinIfList (Op, RHSValue,TimeSeries, TimeSeries1,...) - Calculates the minimum value amongst list values (=,<,>,>=,<=) RHS value in each time step.

  • MaxList: MaxList (TimeSeries, TimeSeries1,...) - Calculates the maximum value amongst list values in each time step.

  • MaxIfList: MaxIfList (Op, RHSValue,TimeSeries, TimeSeries1,...) - Calculates the maximum value amongst list values (=,<,>,>=,<=) RHS value in each time step.

  • AverageList: AverageList (TimeSeries, TimeSeries1,...) - Calculates the average value amongst list values in each time step.

  • AverageIfList: AverageIfList (Op, RHSValue, TimeSeries, TimeSeries1,...) - Calculates the average of list values (=,<,>,>=,<=) RHS value in each time step.

  • SumList: SumList (TimeSeries, TimeSeries1,...) - Calculates the sum amongst list values in each time step.

  • SumIfList: SumIfList (Op, RHSValue,TimeSeries, TimeSeries1,...) - Calculates the sum of list values (=,<,>,>=,<=) RHS value in each time step.

  • CountList: CountList (TimeSeries, TimeSeries1,...) - Counts the number of time series in the argument when the list values are not missing.

  • CountIfList: CountIfList (Op, RHSValue, TimeSeries, TimeSeries1,...) - Count the number of list values (=,<,>,>=,<=) RHS value in each time step.

Learn more about using functions here.

Performance Enhancements

Once again performance was a key driver in this release as our client's have been hosting more and more data as the application's uses expand. Based on preliminary tests on our largest client's server, this release results in data loading speeds that are 5x faster than before (in other words they take 20% of the loading time that was needed before)!

The following is a brief summary of changes made to improve performance (many of which the end user will never see):

  • The UI has been rearranged to only load requested content to the webpage at a given time. Users will notice now that tabs like Data Source only show 20 sensors at a time which can be cycled through using search, sorting, and paging.
  • The Info360 database has been further optimized for querying data, and each query throughout the code has been further streamlined for efficiently retrieving timeseries data with minimal overhead.
  • Info360 has been converted to be a 64-bit application, allowing it to leverage greater amounts of memory for processing and performance.
  • Large analytical expressions and Mass Balance calculations are now partitioned for improved performance and reliability.