MES, job operation sequencing

Yahoo Archive
1
I am going to mention my biggest pet peeve with Vantage because it is
related to this problem. If you report quantities out of sequence,
it messes up the WIP location reporting and the work queues.

1. There is a job for 50.
2. All 50 are completed at step 10.
3. The work queue for step 20 will show 50 there. If you go into
Job Tracker and look at the Part Locations tab, all 50 will be at
step 20.
4. Now complete 10 parts at step 40. (The same problem exists
whether you report 10 or 50 or 5000 parts.)
5. Now the work queue for step 20 still shows 50 there, and the work
queue for step 50 shows 10 there, for a total of 60. If you look at
the Part Locations tab, it shows 50 at step 20 and 10 at step 50.

Both the work queue and the part location tab work off the PartWip
table. The WIP quantity on the job will still say 50, but the work
queues will be wrong and any reporting you have for wip location will
be wrong.

The worst thing about this is there is no way to correct the WIP
location. I thought I could do it with AMM, but can't. Epicor
agrees that the WIP location cannot be corrected once it is wrong.

Epicor 9 is addressing this.

-Peter

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:
>
> MES should be warning you that you are processing an OP before the
prior OP has any completed qty - but NO - It will not stop you from
reporting out of sequence.
>
> That said, you can put a pretty simple customization in place to
trap the errant entries before they are saved. If your are BPM
proficient (and I am not), that would be an even better wy to trap it
to prevent it as it would likely work across all apps (MES and full
license Labor Entry).
>
> Be careful: On 403 doing this freaked the Global out and you would
end up with a lot of still open, but unscheduled OPs. I believe it
was addressed in 404A (with an additional patch) and haven't yet
tested how 404B treats these common user errors.
>
> Rob Brown.
>
> --- On Thu, 5/29/08, Tony Hughes <thughes281@...> wrote:
>
> From: Tony Hughes <thughes281@...>
> Subject: [Vantage] MES, job operation sequencing
> To: vantage@yahoogroups.com
> Date: Thursday, May 29, 2008, 1:49 PM
>
>
>
>
>
>
> Is it correct that you can clock in to operations out of sequence?
>
> Example, we are testing MES to deploy.
> we created a job, opened MES, logged a user in, Start Production
Activity on that job, and by mistake picked Operation 20.
> 10 is not complete.
> I then logged in another user and Start Prod. Activity on that same
job, and picked Operation 80.
>
> This seems wrong, operations are sequenced for a reason.
>
> how do I make it so a job must be done in sequence?
> in other words, you can't log labor against op 20 until op10 is
Complete.
>
2
Is it correct that you can clock in to operations out of sequence?

Example, we are testing MES to deploy.
we created a job, opened MES, logged a user in, Start Production Activity on that job, and by mistake picked Operation 20.
10 is not complete.
I then logged in another user and Start Prod. Activity on that same job, and picked Operation 80.

This seems wrong, operations are sequenced for a reason.

how do I make it so a job must be done in sequence?
in other words, you can't log labor against op 20 until op10 is Complete.
3
It is correct, at least everytime I have used it. The reason you
can do that I think is for partial production. What if you only
have 1 of 5 units done but want to start op 20 for the first unit.
You might be able to make it work the way you want with a BPM or
customization.

--- In vantage@yahoogroups.com, Tony Hughes <thughes281@...> wrote:
>
> Is it correct that you can clock in to operations out of sequence?
>
> Example, we are testing MES to deploy.
> we created a job, opened MES, logged a user in, Start Production
Activity on that job, and by mistake picked Operation 20.
> 10 is not complete.
> I then logged in another user and Start Prod. Activity on that
same job, and picked Operation 80.
>
> This seems wrong, operations are sequenced for a reason.
>
> how do I make it so a job must be done in sequence?
> in other words, you can't log labor against op 20 until op10 is
Complete.
>
4
MES should be warning you that you are processing an OP before the prior OP has any completed qty - but NO - It will not stop you from reporting out of sequence.

That said, you can put a pretty simple customization in place to trap the errant entries before they are saved. If your are BPM proficient (and I am not), that would be an even better wy to trap it to prevent it as it would likely work across all apps (MES and full license Labor Entry).

Be careful: On 403 doing this freaked the Global out and you would end up with a lot of still open, but unscheduled OPs. I believe it was addressed in 404A (with an additional patch) and haven't yet tested how 404B treats these common user errors.

Rob Brown.

--- On Thu, 5/29/08, Tony Hughes <thughes281@...> wrote:

From: Tony Hughes <thughes281@...>
Subject: [Vantage] MES, job operation sequencing
To: vantage@yahoogroups.com
Date: Thursday, May 29, 2008, 1:49 PM






Is it correct that you can clock in to operations out of sequence?

Example, we are testing MES to deploy.
we created a job, opened MES, logged a user in, Start Production Activity on that job, and by mistake picked Operation 20.
10 is not complete.
I then logged in another user and Start Prod. Activity on that same job, and picked Operation 80.

This seems wrong, operations are sequenced for a reason.

how do I make it so a job must be done in sequence?
in other words, you can't log labor against op 20 until op10 is Complete.