Operations

  • 3 minute(s) read

During operation, the machine may generate events that relate to its normal operation, but which are noteworthy to be tracked through the use of operation events:

  • Information: events that normally occur during product operation, for instance, the product has started a new processing, completed a cycle, been shut down or started up.

  • Advice: events that do not relate to the operation of the product, but can be used to give advice to the operator. For example, reduce the speed for a higher quality of result, or, every N processing clean the tool.

An Operation event is described by:

  • Name: the name of the event (e.g. JOB_STARTED).

  • Title: the user-friendly name of the event (e.g. Job Started).

  • Description: the event description (e.g. Scheduled job T-123 started).

  • Group: the name of the group to which this event belongs.
    The group can be used to filters and groups events into the DPS pages.

  • Topics: the set of topics to which this event relates  (CONNECTION, CONSUMPTION, DOWNTIME, HEALTH, PRODUCTIVITY, QUALITY, UPTIME).
    Topics are predefined and can be used to filters and groups events into the DPS pages.

  • Active/Clear Conditions: the metric/property-based conditions used to activate/deactivate the event instance.
    In case of property-based condition, you can use only properties of type DATE.

  • Troubleshooting: a set of remedies the user can follow to fix the problem by himself.

  • Options: a set of variables that can be used to let the user customize the thresholds for event triggering.

  • Alert: how to notify the event to the users.

Note that a OPERATION event, by default is associated to INFORMATIONAL severity and INFORMATION category.  

Creating an Operation event

To add a new Operation event, you should:

  1. Enter the Events / Operation page.

  2. Select the Location or Thing Definitions tab, depending on where you want to create the event.

  3. In case of Thing Definition, select the Thing Definition to edit.

  4. Press the Add Event button.

  5. Provide the required information.

  6. Press the Save button and edit the additional information, if needed.

Editing an Operation event

An Operation event is described by the following sections:

General

The main section describing the event through these properties:

  • Name: specifies the name of the event, it is a free value (e.g. OP_START).

  • Title: the user-friendly name of the event (e.g. Operation Stated).

  • Description: the text describing the occurred event.

  • Severity: fixed to INFORMATIONAL.

  • Category: can be INFORMATION or ADVICE.

Within the event Title, and Description it is possible to use placeholders to include information about the thing, the event, and measures.

Dashboard

  • Event Template: the template used to display the event details in a dedicated dashboard.

Active and Clear Conditions

This section allows defining when the event must be activated or cleared.

For more details about how to define conditions refer to the Event Trigger Conditions article.

In case the event is not User Reported:

  • If the clear condition is not specified, the negated active condition is used.

  • To activate a new event, the activation timestamp of the clear condition must be prior to the activation timestamp of the active condition, and there are no events of the same type still active.

  • An event is periodically evaluated and is triggered only when the active condition changes from false to true and remains true for at least one evaluation interval (e.g. 60 seconds). This means that in case of metric-based conditions, metric values with a duration of less than one evaluation interval (e.g. 60 seconds) may not be detected in order to correctly trigger the event.

Technical Description and Remedies

Here you can describe more technically the event that has occurred and which are the causes and impacts. Optionally, you can provide a set of remedies, the user can follow to fix the problem by itself.

Remedies are presented to the user through the Thing Troubleshooting widget.

Options

This section allows defining options to be used within the event definition and whose value can be redefined by the end-user within the page by suing the thing-options widget.

For more details, see the Options article.

Alert

This section allows defining whether the Event must be notified to users through an Alert.

By clicking the Add Alert Button, you can create a new Alert for the event.