Focusing on task data entered, and the compliance status of this data, is only part of the real compliance picture. It is equally important to be able to easily see data which is not being collected.
Two new widgets have been added to the ZetaSafe dashboard
- Consecutive Unable to Complete (UtC)
- Consecutive Missed Scheduled Tasks
Whilst not explicitly linked, these two will widgets work together. Entering an 'unable to complete' note on a scheduled task event is not counted as entering a task, so where a task has a historic mixture of UtC notes and missed tasks the task will appear in both widgets, when this happens you should add both counts together to get a full picture of just how long it has been since this asset was tested.
Of course it might be the case, such as is common with Calorifiers, that there is no return pipe. Someone may, in the past, have entered a UtC or recorded some sort of erroneous result - this may set off a schedule and subsequently generate a large number of missed/UtC events.
It might not be so simple as 'someone has not completed the work', the ZetaSafe schedule may not match exactly the planned site visits; so there might be a large number of ad hoc tasks which were just outside of the tolerance period. Equally a task may have been scheduled in error, handheld users would have no control over this and may feel obliged to continue entering unable to complete notes. The widgets will help to increase the visibility of gaps arising around scheduling, that they might be dealt with more swiftly.
Consecutive Unable to Complete
- A task will show when there are 2 or more consecutive UtC notes which sign off scheduled events (missed scheduled events occurring in between are ignored by this count)
- Clicking the count will focus the schedule screen on the last entered UtC event which signed off a schedule
- The widgets shows the dates of the first and last UtC notes so it is clear how long the asset has been inaccessible
- A link is provided to the last task result entered, note: this task result may NOT sign off a schedule. Ad Hoc results will not clear the count for schedules marked as UtC.
- The count can only be removed from the widget by a result (Red, Amber or Green) which does sign off a schedule.
- Where no result has been entered, this will be stated in place of the above link
- Links to the asset and location are also provided
- The widget can be filtered on MCS, CTR and Compliance Scheme/Asset Type.
Consecutive Missed Scheduled Tasks
- A task will show when there are 2 or more consecutive missed scheduled tasks (ie red/missed events in the schedule) which sign off scheduled events (missed scheduled events occurring in between are ignored by this count)
- Clicking the count will display the schedule screen focused on the current time & day, where a schedule has expired, or been stopped, it might be necessary to look back over the schedule history to locate the last missed event.
- The widgets shows the date of the last schedule which was signed off.
- Where no schedule has ever been signed off this will be clearly stated in place of the above link.
- A link is provided to the last task result entered, note: this task result may NOT sign off a schedule. Ad Hoc results will not clear the count for schedules marked as missed, neither will unable to complete notes (even where they do sign off a schedule).
- The count can only be removed from the widget by a result (Red, Amber or Green) which does sign off a schedule.
- Links to the asset and location are also provided
- The widget can be filtered on MCS, CTR and Compliance Scheme/Asset Type.
Comments
0 comments
Article is closed for comments.