MES Work Queue and Resource Scheduling Board

Jason,

Even in 8.03 (.3 when piloting thru .405a we are now live), the resource scheduling board is a disappointing hunk-o-junk.

It sounds like the 8.00 version you are on is only doing 'what if' schedule changes that are not being updated to be the true schedule. Never having endured 8.00 (thank goodness), I can't say whether it is a bug or if you are failing to take an additional action to make your 'what if' manual changes to become the actual schedule.

Point of clarification: MRP is not a scheduler (except if you tell it to schedule any new unfirmed jobs it generates).

Rob

--- On Tue, 11/18/08, Jason Abramczyk <jasona@...> wrote:
From: Jason Abramczyk <jasona@...>
Subject: [Vantage] MES Work Queue and Resource Scheduling Board
To: vantage@yahoogroups.com
Date: Tuesday, November 18, 2008, 7:03 PM











We currently use the multi resource scheduling board for moving job

operations from the resources that are scheduled by MRP to different

resources. Every operation is manually re-scheduled this way.

The work queue from MES still shows each operation at the orignal MRP

scheduled resource and original scheduled time. Logical thinking tells

me that this is the way that it is meant to work but because we

manually re-schedule everything (basically ignoring MRP which i beleive

is ridiculous) work queue will never work correctly for us.

Has anyone noticed the same thing? We are currently on 8.00.811b.



Thanks,



Jason.
We currently use the multi resource scheduling board for moving job
operations from the resources that are scheduled by MRP to different
resources. Every operation is manually re-scheduled this way.
The work queue from MES still shows each operation at the orignal MRP
scheduled resource and original scheduled time. Logical thinking tells
me that this is the way that it is meant to work but because we
manually re-schedule everything (basically ignoring MRP which i beleive
is ridiculous) work queue will never work correctly for us.
Has anyone noticed the same thing? We are currently on 8.00.811b.

Thanks,

Jason.