We also have cases of 1 operator for 2 or more concurrent machine operations.
This is handled by
* paperwork fill out intelligently
* data entry intelligently
* & software modified to support

for example we added a command function key for keying in a bunch of labor tickets on a related set of jobs, where the screen is not cleared of all fields from one ticket to the next, but copy the controls that are common to the job

We've added to the reasonableness checks. For example, some human was keying time into the quantity field & quantity into the time field.. Instead of BPCS practice of find one oops & return screen, then fix that, find next oops, fix one at a time, we return screen with multiple lines of oops messages, highlighting multiple suspicious fields.

Result is much faster data entry.

However, we have moved away from tracking labor time.
The focus now is on accuracy of inventory counts, save clerical time transcribing data.
Costing has become based on material content, because with commodity costing, that fluctuation needs to be tracked & managed, while labor costs are pretty standard.

Al Macintyre

We use clock #s on real people doing direct labor, so we can examine
efficiency data on the people, the parts, other criteria.

We have a non-clock # for indirect labor (99999), and know to exclude that
clock # from certain reports. This clock # is used when supervisors etc.
temporarily help out somewhere.

Normal labor input is either machine or labor run time, with other codes
available for setup, downtime functions, where for example the machine is
being cleaned.

We altered the labor input screen, so instead of using letters for
functions, it is all numeric input & the program converts to appropriate
letter. This results in much faster data entry.

When labor is keyed in, if you leave the employee clock # unoccupied, you
will get a TEAM screen, where you can key in list of people who worked on
the same task, and BPCS should divide the time and effort between them, but
we wrote a program to fix the math.

We found out about this by printing the help text, then mapping
"What the heck do you do to get to THAT screen?"

>To All:
>A client uses 2 sets of work centers for the same physical machine. One set
>is for direct labor, the other for indirect labor.
>The use of 2 work centers for the same physical machine causes problems in
>both capacity reporting and shop order scheduling - capacity is doubled but
>more importantly scheduling doubles up and schedules shop orders
>The challenge the client is trying to overcome with this double work center
>approach is avoiding a multiple on indirect labor
> . an operator runs 3 machines in an eight hour shift - hours worked is
>8, not 24.
> . in the same work center an operator runs 2 machines in a 2nd eight
>hour shift - hours worked is 8, not 16.
>Disregarding the client's assumption having an operator monitor 3 machines
>is indirect labor, how are you handling this multiple machines/1 operator
>issue in your routings?
>Roy Luce
>Systems Plus - Midwest
>Direct: 847-540-9635
> 800-913-PLUS (7587)
>Cell: 847-910-0884
>Email: rluce@xxxxxxxxxxxxxxxxxxx
>This is the BPCS ERP System (BPCS-L) mailing list
>To post a message email: BPCS-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
>or email: BPCS-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/bpcs-l.
>Delivered-To: macwheel99@xxxxxxxxxx

This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.

Delivered-To: macwheel99@xxxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.