Escalation of missed hourly / half-hourly Monitoring Programs

The time between can be critical in the event that a CCP defines checks to be performed within a specific timeframe (i.e. weight checks every 30 minutes). Currently, the user has to "add a line" when the next check is due, however there is nothing to alert the user when the check is due or completed outside of the time limits. Furthermore, when reviewing the records there is no indication of a missed/late check without scrutinizing the times of each individual line item. 

  • Guest
  • Apr 27 2015
  • Future consideration
  • Jun 11, 2015

    Admin Response

    It would be an administrative nightmare if the system produced an individual Monitoring Record for each and every half hourly check. At the end of an 8 hour shift you would have 16 different records to find and verify, and you couldn't possibly compare the times to see if they were conducted on schedule. Using a single Monitoring Record to represent a batch or shift with a time stamp column is far more effective and this has been proven once users know that this is possible and how it works.

    The operator knows the checks need to be done and does not need a reminder. The problem is when the operator does not do the checks that flags are raised and there is awareness of it. This is the real need - not the need to remind the operator. 

    So the solution is a feature that allows an escalation of hourly or half-hourly checks not conducted to the appropriate people under defined conditions e.g. 3 successive checks overdue on line 1 metal detector or 1 overdue check on a CCP. 

  • Attach files
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar