A task is a unit of work, performed on a machine, by a person, at a particular time.
A task in innius has the following uses:
- it can be created manually, to register that something needs to happen to a particular machine, or to record that something has happened to a machine.
- it can be created as consequence of real-time data monitoring, based on machine rules.
- it is used as a vehicle to initiate maintenance / service orders, in an outbound flow to a CMMS or ERP system.
- it is used as a vehicle to record maintenance work, in an inbound flow from a CMMS or ERP system.
As an example:
A machine with a vibration sensor, emits a sensor value that exceeds the defined rule for axis vibration. The manufacturer has documented that in case of excessive vibration a maintenance activity must be performed to check the bearings of the axis and replace them if needed.
Therefore when the rule threshold is crossed it creates a new task for the machine, with 'maintenance' as the type, and adds a link to that task in the notification that is sent. A responsible maintenance engineer receives the notification and accepts the task. The task appears on his work list, with a given due date. When the maintenance engineer starts the maintenance work, he changes the status of the task to 'in progress'.
The activity refers to a maintenance guide in which the bearing inspection and replacement method are described. When he has completed the maintenance work, he adds an additional note, and again updates the status, this time to 'Done'. The completed activity is recorded on the machine timeline in innius. In addition, the work performed by the engineer is communicated with the back-office registration system.