Re: Labor Reporting - Kronos

Eons ago, we implemented Kronos and BPCS Ver. approx. 3 ½ for labor
reporting, and time & attendance. We ended the Kronos part at their PC,
where they combined the individual transactions, (including the shift
spanning midnight), into employee reporting records. They also did the error
checking, looking for missing job start, job end, lunch on, lunch off,
quantity reporting etc. Those transactions in error were written to a
separate file for correction through the Kronos network. The file containing
records judged to be good were uploaded by our MIS to the AS/400. From
there, MIS fed those records to a modified JIT600 so they could be
transacted as if keyed in. Errors caught here, (i.e. Shop order closed too
soon), were spit out to another error report for correction through BPCS.

Problems:
We, or Kronos underestimated the storage requirements at the data collection
terminal, so Shop Order detail verification could not be performed at the
terminal. We had approx. 3,000 valid Shop Orders open at one time.

All in all, the use of Kronos went smoothly. There were initial start up
issues that Kronos responded to quickly.  However, after about 6 months we
decided that the cost of collecting the data far outweighed the benefits
derived from having the data in that much detail. Too much time was spent by
employees running to the terminal to clock on and off jobs - lots of short
run Shop Orders. Too many error reports to chase down and correct.
Eventually we dropped individual employee reporting and went to part
completion reporting, and backflushing of labor & material. The only thing
that remained in use was time & attendance, still in use today.

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---