Heritage Operations Processing System
 
Back to Home | Back to HOPS Support
For each competence a Refresh Period will be set. This is the length of time in which if the staff member does not do a turn in that position the competence will be considered 'LAPSED'.

In a department that requires that their staff don't go more than six months between shifts, the Refresh Period is set to 6 months.

In the case of a department whose rosters aren't on HOPS, these staff will do turns but HOPS won't know about it so they would all go to 'lapsed'. The Refresh Period should be the same time length as the Competence Length, so that nothing can ever lapse.
Each competence will also be given an expiry date.

This is the date on which the user will be considered not competence any longer, regardless of how many turns they have done and how long ago their last one was.

This is useful for, say, enforcing bi-annual rules exams. Each time a person takes the rules their competence can be reset with an expiry date two years in the future. If they do their bi-annual rules again in that time, the competence is reset again for another two years. If they don't, the competence will expire.

The expiry time can be set to any length.

For non-safety-critical roles, the competence can be set to 'Does Not Expire'.

A competence will also expire if any of the competence elements on which it is dependent expire.


HOPS is continually being developed and updated. Sometimes the screen shots in these help files might lag behind the most up-to-date views of the screens. Generally, however, the functionality of the page will be the same, albeit with a slightly different format or layout.

Thank you very much indeed to Emma Patrick for writing these support pages.