Improved Algorithms management

The way algorithms can be defined in the Console has been fully revised.

The new Insights / Algorithms page provides you with a single point where you can manage all the algorithms used in the DPS, including built-in (e.g. Connection Index) and custom ones.

Into an Algorithm Definition, you can specify inputs (metric based, event based or static values), a Python script, and outputs (also more than one). With this new approach, it is possible to reuse the same Algorithm definition in different places, setting specific inputs and reading a specific output. For example, in an Insight Metric, in addition to the Algorithm, it is necessary to configure the inputs and select the output to be used as the value for the metric.

A new Try Algorithm experience allows developers to test the script with different inputs, before being used, for instance, into an Insight Metric.

The creation of custom Insight metrics (with embedded Python script) is no longer available and thereafter it is necessary to create an algorithm to be used in Insight metrics. Don't worry, custom insights metrics you have currently defined will keep functioning, and they can be migrated quietly in the future. 

Work Session manual creation

The historical work session list widget now allows DPS users to manually create Work Session instances, by providing the Work Session Definition and a CSV file with historical data collected during the work session execution. This function can be used in all cases where a machine cannot publish data, for example, due to a network problem when used outdoors. To avoid the loss of information critical to the computation of the machine's productivity indicators, or operating reports, the machine operator will be able to manually upload such missing data in deferred, for example, at the end of the working day.

Work Session post computation algorithms

Algorithms can be used in Work Session Definitions to process collected data and perform a post computation at the end of a Work Session.

This can be used to enrich Work Sessions with helpful information, for instance:

• Quality: the outcome quality can be validated by using proprietary computational logic.
• Performance: performance can be computed according to the nature of the Work Session.
• Timing: in some cases the machine may be paused several times, and the effective Work Session duration, that is relevant for planning activities, cannot be easily calculated with standard time counters.

This additional information can be displayed and aggregated in the DPS, providing valuable data for users to make decisions. For example, Service Managers can highlight machines that have the worst quality or performance, and engage service to repair or investigate on them. Operation Managers can be informed of bad quality, poor performance, and time losses during operational activities. Technicians can access summary indicators of a specific Work Session type and compare them with other sessions, including those of other machines, in order to see if degradation of some kind is present.

Escalation on long-standing active events

Into an Automation definition, you can specify a condition to monitor events that have been active for too long time. For instance, in case a FAILURE remain active for more than a day, an external API can be invoked to engage the Service by opening the ticket and case on the legacy FSM (Field Management System) of the OEM.

Thing bulk deletion action

In the thing list, it is now possible to perform a mass deletion of things.

Back-office users can easily manage the deletion of multiple products when needed. Note that, to improve security, the DELETE permission has been separated from the WRITE permission. Nothing needs to be done in the Console, but now it will be possible to define which User Type can delete a certain object or not. For instance, Customer users should not be able to delete things.
  

Bug fixes (DPS)

• The Multi Metric List widget was not aware of the page context, so it was not possible to load data limited to a specific Event (e.g. Failure, Work Session).
• Organization and Partner users were unable to view the Grouped Thing List with customer-defined tags.