Machine Customers

Here you can find a step-by-step guide about how to configure the Machine Customers use case into the DPS System.

By following this guide, the DPS will be able to monitor the wear and tear of the components of connected machines, and suggesting to DPS users the purchase and replacement of end-of-life spare parts.

Configuring the Machine Customers

1. If not yet done, follow the Contextual E-Commerce guide. This is the basis on which a more advanced sales experience can be built on.

2. Within the thing definition create a Wear Metric, this will be used to monitor the status of a machine part (e.g. Blade Group) subject to wear and tear.

3. By creating a wear metric, the Console will automatically create additional elements, you can customize according to your needs.

   1. Operation Event: the event activated when the wear status reaches the 100% of designed usage of the part (e.g. 100 working hours).

   2. Anomaly Event: the event activated when the wear status reaches the maximum tolerated usage of the part (e.g. 120%).
      This event replaces the previous one (which is historicized), and provides the user with a higher level of attention due to the risk that the machine may break down.

   3. Replacement Action: the action activated on both the previous events, and that suggest the user to change the worn part.

4. Into the Spare Part References (e.g. Bandsaw Blade M123) related to the machine part you are monitoring, you must select the Wear Metric and optionally redefine the Max Usage and Tolerance for a specific Product Model.
   This step binds the Spare Parts to the replacement Action, that can suggest their purchase when activated on a machine.

5. In the Customer view of the Thing Definition, you can place the Wear Status widget, that can provide the user with an overview of the machine wear status and quick access to Actions including spare parts to purchase.