Support Portal

SICK Field Analytics 1.3.1 Release Notes

SICK Field Analytics 1.3.1
Related Products
SICK Analytics Software Assurance
FieldAnalytics

Table of Contents

SICK Field Analytics 1.3.1 Release Out Now

Field Analytics 1.3.1 minor patch release for bug fixes related to Historian and Email Alerting Features 

Software download

Use cases of the new release

The 1.3.1 release is focused on fixing known issues with Historian.

  1. The limitation on Filter by Value in FA 1.2.2 has been removed. With FA 1.3.1, users can apply filter by values on a data source and any number of fields, especially since the Influx Query language does not support joining measurements.
  2. Pivoting view, which was not efficient by MySQL in FA 1.2.2 (Implemented by custom logic at application level), is now available. Aggregate functions in Pivoting view can be used as tabular view, and group by sec, minute per aggregate functions is supported.
  3. We are moving towards depreciation of tabular view which is record based results.
  4. As a first step, we are displaying pivoting as the default view which is key-value data representation. Tabular view remains supported for backward compatibility.
  5. Group by Value in Pivoting is now possible.
  6. New aggregate functions are available by default.
  7. Improved efficiency in data storage.

Customer required actions

If you are using a FA 1.3 instance, please upgrade immediately to the 1.3.1 version using the patch installer. 

Hardware & software compatibility

Operating System

  • Windows 11 (64 bit)
  • Windows 10 (64 bit)
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2016 (AWS)
  • Linux Ubuntu 20.04
  • Linux Ubuntu 22.04

Required Disk Space

  • Depends on application. Contact SICK product support for hardware requirements.
  • Minimum 2 GB for installation. 3-4 GB SSD Recommended

Required Disk Type

  • Solid State Drives (SSDs) with high-write endurance are highly recommended.

Processor

  • Minimum Intel Core i5
  • Recommended i7 (2.30 GHz)

Memory

  • 16 GB DDR3L or higher is recommended.

Screen Resolution

  • 1920 x 1080 (16:9) aspect ratio is recommended for optimal viewing.

Browsers

  • Google Chrome (version 128.0.6613.137)
  • Mozilla Firefox (version 130.0)
  • Microsoft Edge (version 128.0.2739.67)

Pre-requisite Software

  • Runtimes
    • Java Runtime Environment 17.0.6
  • Databases
    • MySQL 8.0.33 (MySQL Database is recommended for sites where heavy load is expected)
    • Influx v2.7.3 (Influx Database is recommended for historian to store the records)
  • Runtimes and Databases are bundled with the installation package and will be installed/updated automatically if they do not exist on the target machine.
  • Browser Recommended
    • Chrome (Latest version), Firefox (Latest version), Edge (Latest version)

Note: A license file is needed to access the FA application. This license is supplied separately and on request from the SICK Support.

Known limitations & issues

    Large data sets

  • When there are huge data sets which is more than 500,000 with more than one data source, when a user tries to perform a wild card search (meaning all data sources and all field names of all data sources are selected) user sees latency in the search
    Work around: Create a report per data source, then choose multiple reports as a data source for widgets.
  • We are moving towards encouraging users to a data source or a field as search parameters, depreciation of wild card search.

Group by value

  • Group by value was introduced in tabular view in FA 1.2 to display the field counts by value in table (Example: At Honda, customer wants to know the PASS, FAIL, NOMATCH for links based on time, like for linked=1, inspection status=pass, count=1), this are the scenarios where group by value is used
  • In pivoting aggregates are always group by event time and aggregate would not show the value as needed.  FA 1.3.1 supports group by value in pivot, tabular but is discouraged to use group by value with wild card search.
    Work around: Choose a data source, field, and perform group by values at granular of a minute.
  • Count with group by value with group by minute, influx shows the count of next minute add into the current minute until that minute is complete.
    For example: if my current time is 12:22:33, if I perform the search, the I see the count of 33 seconds added into the 12:22, we end up seeing the multiple rows of 12:22 until it reaches 12:23

Data Acquisition

  • Data is written into InfluxDB in batches per second. It takes approximately 1 second from data acquisition to retrieval on the historian.
  • For wild card search it might take 30sec-1min to see the results, this is specifically when a user creates a data source and goes back to historian and search immediately then there might be delay but we don’t see that issue if we choose the data source.

Known limitations & issues

Legal Information:

For Software, Software as a Service or Products containing Software, the following terms and conditions shall apply: (i) SICK’s General Terms and Conditions for the Supply of Software Products (“AVB Software SICK”, available at www.sick.com). And/or (ii) SICK’s General Terms and Conditions for Software as a Service (“AVB SaaS SICK”, available at www.sick.com).

 

This work is protected by copyright. Any rights derived from the copyright shall be reserved for SICK AG. Reproduction of this document or parts of this document is only permissible within the limits of the legal determination of Copyright Law. Any modification, abridgment or translation of this document is prohibited without the express written permission of SICK AG.

The trademarks stated in this document are the property of their respective owner.

© SICK AG. All rights reserved. Subject to Change without notice.

 

Original document:

This document is an original document of SICK AG.

 

About this document:

This document contains details of changes and their impacts. The respective operating instructions can be found at www.sick.com

Keywords:
Analytics, SICK Field Analytics, Field Analytics, 1.3.1, FA