ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Manufacturing >> execution signals
http://www.istechforum.com/YaBB.pl?num=1135978265

Message started by JaySchmitendorf on 12/30/05 at 13:31:05

Title: execution signals
Post by JaySchmitendorf on 12/30/05 at 13:31:05

We do not know how to communicate progress events.

At the end of the day we want to know how many sequences have been completed on how many parts.
We want to think about pieces of work as flowing through our plant.

Sometimes we get huge variances and the system does not tell the supervisors until its too late.

We have orders for a 100 parts with 4 work center sequences that take between two hours and twenty minutes each.

Maybe we should learn to enter labor as .022 parts complete. Maybe we need a rebuild labor history program for work in process.

Our sales person has to go off line to find out where jobs are.

Do you have any suggestions?

Title: Re: execution signals
Post by Lynn Pantic on 01/02/06 at 14:48:49

Don't understand what you mean by 0.022 parts complete. If the job is for 100 pieces, then when the sequence is complete and they move on to the next operation, report the 100 pieces as complete using WO-M, DC-B or WO-F if you need to know part status.

Title: Re: execution signals
Post by JaySchmitendorf on 01/05/06 at 07:07:40

When the supervisors do batch labor entry, the system reports that we have completed 4 times too many or 400 pieces. We actualy only had 100 pieces flow through 4 different stations, 400 sequences 100 parts.

There must be some system setting we have wrong.
Please tell me some companies have this working correctly.