Karen Mason
|
We are using data collection on our shop floor. Currently, SD-F data collection defaults has a shift schedule with a buffer. Both the Shift time and work order time default to the buffer time. It would be better to have the shift time stay as orginally recorded rather than "snapping" to the buffer time and have the work order default to the buffer time. We want to see exactly when an employee clocked in and out. Was it 30 seconds before start of shift (which means they never hit the floor on time) or was it the suggested 6 minutes in advance? Since we desire this information, we cannot use the buffer. That means that every beginning work order has to be adjusted to the actual start time in order to make the transfer to the payroll module accurate. On the same note, the lunch buffer does not work in a real factory setting where job costing is important. We want to know how long an employee is "out to lunch" and we want it coming from the appropriate work order. To accomplish this we go through a lot of gyrations. Employee clocks out of work order, clocks into indirect labor work order operation called "lunch". Since this actually accumulates time, we then have to enter a negative 1/2 hour to the same employee. It would be much better if they could "punch" into something that does not accumulate cost/time to their payroll.
|