Purpose
The purpose of the events layer is to define all possible event types that can occur on the product or location and that are worth to be recorded
Terms
- Event instance: a single occurrence of an event that happened at a given moment in time
- Event type (or Event definition): the type of event that occured
- Event class: a higher level for classifying event types
Event classes
We classify event types in these classes:
- failure → the product is blocked, down, unavailable
- major anomaly → the product is still working but something wrong has happened that affects product health and could potentially cause a failure in the short term; a short term action is needed to avoid this risk
- minor anomaly → the product is still working but something wrong has happened that could potentially affect product health in the long term; there is no risk of short term failure, therefore a programmable action is enough to deal with this case
- work session (or job) → these represent the jobs that the product performed and for which it was designed and purchased
- regular operations → these are operational events that are not the main ones
- maintenance → a maintenance operation has been performed on the product
Health impacting events → Needed actions
Event class | Needed action |
Failure | an immediate action is needed |
Major anomaly | a short term action is needed |
Minor anomaly | a programmable action is needed |
Event instances creation
Event instances can be created in the DPS system in two ways:
- detected automatically by processing RAW Data → a condition is checked against past values
- inserted manually by a user → a widget is exposed to the user
💡 Tips
- Avoid to consider any “machine alarm” as a failure. Try to evaluate its real impact on product health and choose its class accordingly