Actions

Some types of events require manual user intervention, such as replacing a filter and replenishing a consumable.

Through Actions, users can be notified about tasks to be performed to continue using the machine or improve the quality of results, consumption, and performance.

For more information about how to configure actions and their visualization in the DPS, you can refer to the Aided Maintenance configuration guide.

To add a new Action Definition to a Thing Definition, you should:

1. Enter the Involvement / Actions page.

2. Select the Thing Definition to edit.

3. Press the Add Action button.

4. Provide the required information.

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

An Action Definition is described by the following sections:

• Name: the name of the action visible to users (e.g. act_00123).

• Label: the action friendly name used into the DPS as the alternative to the name which can be a code or something more technical.

• Description: the short text describing the action.

• Group: the name of the group the action belongs to.

• Work Time: the estimated time in minutes required to complete the action.

• Topic: the topic to which this action belongs

  • Consumables

  • Performance

  • Maintenance

  • Operations

• Type: one of the types defined in the Settings section (e.g. Check, Lubricate).

• Priority: the priority used to order actions

  • Low

  • Normal

  • High

• Icon: the icon to be displayed within the pages for this type of action.

• Due Period: the time period from the date of activation within which the action is recommended.

• Mandatory reason for the discard: if selected, when the action is discarded it will be requested to specify the discard reason through a note, or by selecting one of the discard reasons specified in the Settings section.

• Limit this action visibility depending on the user type: you can select the user-types that have visibility on the action of this type.

The condition verified by Servitly to activate an action of this type.

The activation condition can be:

Event Based

An event is activated (e.g. a failure occurs).

Period Based

The action is periodically activated (e.g. every X months).

You can specify metric based conditions to automatically mark an action as done or discarded according to the value of a specific metric. For instance, the action informing the user that a cartridge must be replaced, can be automatically mark as done, when the user replaces the cartridge and the machine publishes the new consumable level.

Within the Done Condition, if the Active Condition is based on an Event, it is possible to select whether the action is to be marked as DONE automatically when the event is closed.

In case the activation condition is period based, you can also define whether the action is Reschedule.
If selected, end-users will be able to change the periodicity of an action. For instance, the OEM proposes to check filters every month, but due to the utilization of the machine, the end-user may decide to check filters every 3 months.

Technical Description

Here, you can provide the text/html that describes in a more technical way what the user must perform to complete the action in the DPS.

Translations