GRASS by Lexel

[Eric Trube <JETrube@xxxxxxxxxxxxx>]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
We have been testing GRASS (graphical shop scheduler) in our test
environment and have run across some issues / constraints.

When moving up an operation (due to capacity issues at a particular work
center) we found that the operation itself and the subsequent operations are
moved up together, however the previous operations do not get moved up. This
can result in operation 0030 being scheduled to start before operation 0010!

I was told that this is a MAPICS constraint and that the previous operations
would have to be moved up manually. Of course this takes significantly more
time to make schedule adjustments.

Is anyone else using GRASS and is there a way around this?

Also when looking at the work center capacity view, the refresh time is
extremely slow. Just trying to scroll across the table takes a looooong
time.

If anyone can help or knows of another capacity planning tool out there that
could help us, I'd love to hear about it.

Thanks,
Eric

J. Eric Trube
Hoshizaki America, Inc.
Project Manager
770-487-2331 x775