The problem arise to me in a typical jobshop environment where many hundreds
of tasks have to be optimized and first of all a feasibility analisys is
required.
All is working fine with Oz, and the prototype is running at many beta
testers without any problems (an Oz server and a VB frontend) , but the
question from the users is: "the schedule is not feasible, but why ?".
The question is not particularly bad, because every real user knows his/her
chikens (machines), but sometime some little problems come up from the
database possibly incongruent data.
So add each group of tasks (job) and see what happens is not a solution (not
the same of adding all in one time) and add every contraint (precedence,
resources, calendars,...) is simply impossible.
Any suggestions ?
-
Please send submissions to users@mozart-oz.org
and administriva mail to users-request@mozart-oz.org.
The Mozart Oz web site is at http://www.mozart-oz.org/.