How to CLOSE and LOCK a shift

OEE Coach, using normal shifts, assumes the shift registration is as long as the shift was planned to be (see: How to use SHIFTS)

The shift can not be closed if not all time has been accounted for.

At the end of the shift, the operator checks his shift-registration. The operator should be sufficiently trained to resolve all validation notifications (i.e. highly probable errors) in his shift and deliver not only a complete registration but also correct recording.

A a token this has been done he ‘closes’ the shift:

How to CLOSE a shift

As soon as all the shift duration has been registered and the registration is considered to be correct at the end of the current shift, go back to the data-satellite dashboard:

Here we see the currently running shifts (in this case just one)

Select the shift to close and press [End Shift]

The system ask to confirm, press YES

After closing, the shift disappears from the data-satellite’s dashboard. For the operator that’s it.

How to LOCK the shift

The teamleader might want to verify the registered data. He does that via OEE Coach [DATA] [VIEW DATA]

He selects which shifts he wants to see, verifies whether he sees no errors, open questions etc. and can now decide to lock the shift. This locking means nobody (unless authorized can alter the data anymore.

The shift can only be locked when there are no more validation errors.

When there are errors, the shift needs to be opened first (in the summary screen. modified, closed and the locked.

As you can see, the shift can not be removed when locked

Rules of tumb

1. As long as the shift is not closed, it is being owned by the operator. He is responsible of his machine and the correct collecting and reporting of his shift-data.
2. The shift can not be closed as long as it contains validation errors due to faulty or missing data.
3. A shift that is not closed yet, should not be edited, nor deleted, in the ‘view data’ screen since it is still in process by the operator. However, to allow adding remarks, or to delete erroneously entered shifts, this IS possible for those having the user rights to do so.
4. To have full understanding what is going on in his area, the teamleader should read- and verify the shiftdata and acknowledge them by locking the shift(s)
5. Once a shift is locked it should no longer alter nor being deleted: It has been verified and acknowledged by operator and teamleader and is now the basis for further analyses