Problem Forward Scheduling Jobs in 5.0

I received an email from support yesterday re this issue. It seems
there is an index problem, along with another change, that causes
forward scheduling to move very slow.

The next patch should take care of it.

Lonnie Drew
Southern Tool, Inc.
lonniedrew@...
ldrew@...

--- In vantage@y..., "Lonnie Drew" <lonniedrew@c...> wrote:
> Has anyone experienced job scheduling problems in 5.0? We went
live
> over the weekend and first noticed the problem monday.
>
> When we backward schedule a job it takes a few seconds, when
forward
> scheduling the same job- it crawls.
>
> For example we let it run an hour, just to see what would happen,
and
> barely 30% completed.
>
> Applied the 326 patch to no avail. Tried a couple of database
> conversion routines per support instruction.
>
> Any ideas anyone?
>
> Lonnie Drew
> Southern Tool, Inc.
> 256-831-2811 x243
> ldrew@s...
Has anyone experienced job scheduling problems in 5.0? We went live
over the weekend and first noticed the problem monday.

When we backward schedule a job it takes a few seconds, when forward
scheduling the same job- it crawls.

For example we let it run an hour, just to see what would happen, and
barely 30% completed.

Applied the 326 patch to no avail. Tried a couple of database
conversion routines per support instruction.

Any ideas anyone?

Lonnie Drew
Southern Tool, Inc.
256-831-2811 x243
ldrew@...
We have the same problem. I am sending our database to them tomorrow.
Good to know someone else has the same issue. Let me know if you figure
anything out. Thanks.

Alex Neutgens
Controller
Circuit Check, Inc.
Phone 763-694-4110
Fax 763-694-4151

-----Original Message-----
From: Lonnie Drew [SMTP:lonniedrew@...]
Sent: Tuesday, July 10, 2001 4:42 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Problem Forward Scheduling Jobs in 5.0

<< File: ATT00024.htm >>
We used to forward schedule in 3.0. When we got to 5.0 that didn't work for us, so Epicor suggested backward scheduling. It took a LOT LOT of finaggalling (sp??) to get MRP to work the way we needed it to - which works in a mediocre sort of way. But overall it's better than before.

The first time we processed MRP is took HOURS (like 10 to 15). After that, the Net Changes for MRP don't take nearly as long.

Troy Funte
Liberty Electronics


----- Original Message -----
From: Lonnie Drew
To: vantage@yahoogroups.com
Sent: Tuesday, July 10, 2001 5:42 PM
Subject: [Vantage] Problem Forward Scheduling Jobs in 5.0


Has anyone experienced job scheduling problems in 5.0? We went live
over the weekend and first noticed the problem monday.

When we backward schedule a job it takes a few seconds, when forward
scheduling the same job- it crawls.

For example we let it run an hour, just to see what would happen, and
barely 30% completed.

Applied the 326 patch to no avail. Tried a couple of database
conversion routines per support instruction.

Any ideas anyone?

Lonnie Drew
Southern Tool, Inc.
256-831-2811 x243
ldrew@...



To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please go to: http://groups.yahoo.com/group/vantage/files/. Note: You must have already linked your email address to a yahoo id to enable access.

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]
We have the same problem. Unfortunately, the way we work,
we almost always have to forward schedule. Do you have an open
calll number with support? If so, could you let us know what
it is, that way we can reference that and add our name to the
list of customers with an issue with forward scheduling.


----- Original Message -----
From: "Lonnie Drew" <lonniedrew@...>
To: <vantage@yahoogroups.com>
Sent: Tuesday, July 10, 2001 5:42 PM
Subject: [Vantage] Problem Forward Scheduling Jobs in 5.0


> Has anyone experienced job scheduling problems in 5.0? We went live
> over the weekend and first noticed the problem monday.
>
> When we backward schedule a job it takes a few seconds, when forward
> scheduling the same job- it crawls.
>
> For example we let it run an hour, just to see what would happen, and
> barely 30% completed.
>
> Applied the 326 patch to no avail. Tried a couple of database
> conversion routines per support instruction.
>
> Any ideas anyone?
>
> Lonnie Drew
> Southern Tool, Inc.
> 256-831-2811 x243
> ldrew@...
>
>
>
> To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
How many operations, assembly/material items, and what type of calculations
per operation, pcs per hr etc..., and what is the typical job quantity for a
typical forward or backward reschedule?

-----Original Message-----
From: Alex Neutgens [mailto:alex.neutgens@...]
Sent: Tuesday, July 10, 2001 4:47 PM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] Problem Forward Scheduling Jobs in 5.0


We have the same problem. I am sending our database to them tomorrow.
Good to know someone else has the same issue. Let me know if you figure
anything out. Thanks.

Alex Neutgens
Controller
Circuit Check, Inc.
Phone 763-694-4110
Fax 763-694-4151

-----Original Message-----
From: Lonnie Drew [SMTP:lonniedrew@...]
Sent: Tuesday, July 10, 2001 4:42 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Problem Forward Scheduling Jobs in 5.0

<< File: ATT00024.htm >>


To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
This a major issue to us also and preclude us from going to 5.0 until
forward scheduling works in a timely manner.

-----Original Message-----
From: Tim Care [mailto:ecfmis@...]
Sent: Wednesday, July 11, 2001 8:32 AM
To: pmcguire@...
Subject: Re: [Vantage] Problem Forward Scheduling Jobs in 5.0


We have the same problem. Unfortunately, the way we work,
we almost always have to forward schedule. Do you have an open
calll number with support? If so, could you let us know what
it is, that way we can reference that and add our name to the
list of customers with an issue with forward scheduling.


----- Original Message -----
From: "Lonnie Drew" <lonniedrew@...>
To: <vantage@yahoogroups.com>
Sent: Tuesday, July 10, 2001 5:42 PM
Subject: [Vantage] Problem Forward Scheduling Jobs in 5.0


> Has anyone experienced job scheduling problems in 5.0? We went live
> over the weekend and first noticed the problem monday.
>
> When we backward schedule a job it takes a few seconds, when forward
> scheduling the same job- it crawls.
>
> For example we let it run an hour, just to see what would happen, and
> barely 30% completed.
>
> Applied the 326 patch to no avail. Tried a couple of database
> conversion routines per support instruction.
>
> Any ideas anyone?
>
> Lonnie Drew
> Southern Tool, Inc.
> 256-831-2811 x243
> ldrew@...
>
>
>
> To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>


To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
The call number is 710912MPS. I am having our database delivered to Epicor today. I will let you know if I here anything.

We have an average of 50 assemblies, 150 operations and 200 parts on a job. It also runs slow (1/2 hour) on a job with 1 assembly.

Alex Neutgens
Controller
Circuit Check, Inc.
Phone 763-694-4110
Fax 763-694-4151

-----Original Message-----
From: Peter McGuire [SMTP:pmcguire@...]
Sent: Wednesday, July 11, 2001 8:26 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Problem Forward Scheduling Jobs in 5.0

<< File: ATT00010.htm >>
Sorry I haven't replied earlier. Putting out fires since the upgrade.
I'll try to answer questions posted since.

My first thought was a corrupted or inactive index, required by the
forward scheduling routine. That idea thrown out since so many
others with same problem.

The scheduler is having to make due with backward scheduling. My
understanding is that for certain jobs he has a date in mind to
start. He's guessing at an end date and rescheduling until the begin
date is acceptable.

Our jobs typically have 1-2 subassemblies, one with from 2-4
operations and 2-4 materials. The parent part has 20-30 operations
with usually an additional 2 or so materials. Part quantities per
job can range from 1 to 1000+.

Our call number on this issue is 711034MPS, but since Alex is sending
database it might be better to reference his.

I'll be sure to post any resolution.

Lonnie Drew
ldrew@...
lonniedrew@...


--- In vantage@y..., Alex Neutgens <alex.neutgens@c...> wrote:
> We have the same problem. I am sending our database to them
tomorrow.
> Good to know someone else has the same issue. Let me know if you
figure
> anything out. Thanks.
>
> Alex Neutgens
> Controller
> Circuit Check, Inc.
> Phone 763-694-4110
> Fax 763-694-4151
>
> -----Original Message-----
> From: Lonnie Drew [SMTP:lonniedrew@c...]
> Sent: Tuesday, July 10, 2001 4:42 PM
> To: vantage@y...
> Subject: [Vantage] Problem Forward Scheduling Jobs in 5.0
>
> << File: ATT00024.htm >>
Lonnie,

It doesn't sound like your jobs have a large number of assemblies and
operations. Your scheduler could approximate the start date and
back-schedule. Once the job is scheduled, forward or backward, you can
do a drag and drop on the job visual scheduling board to get not only
the start date when you want it, but you can also schedule each assembly
by itself and/or by operation within the assembly. We just went live on
5.0 Monday, but have been scheduling far more complex jobs this way for
the past two years on 3.0. This works well, especially if you are
trying to balance out capacity problems or finite your final operations
to the ship date and/or the capacity of the assembly/pack-out
department. We will probably do this for some time to come until we can
get any level of confidence in finite scheduling.

Steve
-----Original Message-----
From: Lonnie Drew [SMTP:lonniedrew@...]
Sent: Wednesday, July 11, 2001 10:11 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Problem Forward Scheduling Jobs in
5.0

Sorry I haven't replied earlier. Putting out fires since the
upgrade.
I'll try to answer questions posted since.

My first thought was a corrupted or inactive index, required by
the
forward scheduling routine. That idea thrown out since so many
others with same problem.

The scheduler is having to make due with backward scheduling. My

understanding is that for certain jobs he has a date in mind to
start. He's guessing at an end date and rescheduling until the
begin
date is acceptable.

Our jobs typically have 1-2 subassemblies, one with from 2-4
operations and 2-4 materials. The parent part has 20-30
operations
with usually an additional 2 or so materials. Part quantities
per
job can range from 1 to 1000+.

Our call number on this issue is 711034MPS, but since Alex is
sending
database it might be better to reference his.

I'll be sure to post any resolution.

Lonnie Drew
ldrew@...
lonniedrew@...


--- In vantage@y..., Alex Neutgens <alex.neutgens@c...> wrote:
> We have the same problem. I am sending our database to them
tomorrow.
> Good to know someone else has the same issue. Let me know if
you
figure
> anything out. Thanks.
>
> Alex Neutgens
> Controller
> Circuit Check, Inc.
> Phone 763-694-4110
> Fax 763-694-4151
>
> -----Original Message-----
> From: Lonnie Drew [SMTP:lonniedrew@c...]
> Sent: Tuesday, July 10, 2001 4:42 PM
> To: vantage@y...
> Subject: [Vantage] Problem Forward Scheduling Jobs in 5.0
>
> << File: ATT00024.htm >>


To access the Files Section of our Yahoo!Group for Report
Builder and Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have
already linked your email address to a yahoo id to enable access.

Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
Thanks for the info. I just passed it along to production control.
You may have saved me physical injury....

I gather that you believe finite capacity is the culprit, which is
what support also suggested. We tried turning off finite capacity
for the work centers in the first assembly, and the next two work
centers in the parent. Then tried to schedule the job and watch
progress. It still seemed to hang at first workcenter of the first
assembly. Source code for the scheduling routine would be
interesting to see about now.

Lonnie


--- In vantage@y..., Steve Wirtz <SWirtz@m...> wrote:
> Lonnie,
>
> It doesn't sound like your jobs have a large number of assemblies
and
> operations. Your scheduler could approximate the start date and
> back-schedule. Once the job is scheduled, forward or backward, you
can
> do a drag and drop on the job visual scheduling board to get not
only
> the start date when you want it, but you can also schedule each
assembly
> by itself and/or by operation within the assembly. We just went
live on
> 5.0 Monday, but have been scheduling far more complex jobs this way
for
> the past two years on 3.0. This works well, especially if you are
> trying to balance out capacity problems or finite your final
operations
> to the ship date and/or the capacity of the assembly/pack-out
> department. We will probably do this for some time to come until
we can
> get any level of confidence in finite scheduling.
>
> Steve
Lonnie,

We don't finite capacity anything now. We infinite schedule and look at
our work center capacity and load. We also like to keep the pressure on
the shop. If we don't, they won't meet the rates they need. Also, if
there is a problem that delays a job, e.g. material, non-conformance,
etc., and we have finite scheduled the work center, we find the work
center feeling very comfortable as they now have plenty of time to
finish the next operation. The shop management and supervisors like the
added pressure as it provides a challenge for them. Don't get me wrong,
they will scream if there is a lot more load than they can handle.

When we schedule a job we look at work centers that may have a capacity
problem and look at the work center visual scheduling board after
initial scheduling of the job. Then we drag and drop the operations to
fit in the work center scheduling board, then go back and finish the
detail job scheduling by drag and drop. This may take a little extra
time, but we end up with a pretty good finite schedule having handling
our work center capacity area. In the case of two jobs with tight
committed delivery dates, infinite scheduling (with watching our
capacities) allows us to schedule more hours than in the normal day
which well can make up with overtime, added labor or other workarounds.

You can check your work center capacity by the priority dispatch reports
and looking at your visual scheduling board. We set up a shop load
report in report builder which gives us our shop load in hours by work
center by day. This is better than just looking at priority dispatch
and the work center visual scheduling board for us as it also includes
the crew sizes and totals the labor for the operation.

Steve

-----Original Message-----
From: Lonnie Drew [SMTP:lonniedrew@...]
Sent: Wednesday, July 11, 2001 11:21 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Problem Forward Scheduling Jobs in
5.0

Thanks for the info. I just passed it along to production
control.
You may have saved me physical injury....

I gather that you believe finite capacity is the culprit, which
is
what support also suggested. We tried turning off finite
capacity
for the work centers in the first assembly, and the next two
work
centers in the parent. Then tried to schedule the job and watch

progress. It still seemed to hang at first workcenter of the
first
assembly. Source code for the scheduling routine would be
interesting to see about now.

Lonnie


--- In vantage@y..., Steve Wirtz <SWirtz@m...> wrote:
> Lonnie,
>
> It doesn't sound like your jobs have a large number of
assemblies
and
> operations. Your scheduler could approximate the start date
and
> back-schedule. Once the job is scheduled, forward or
backward, you
can
> do a drag and drop on the job visual scheduling board to get
not
only
> the start date when you want it, but you can also schedule
each
assembly
> by itself and/or by operation within the assembly. We just
went
live on
> 5.0 Monday, but have been scheduling far more complex jobs
this way
for
> the past two years on 3.0. This works well, especially if you
are
> trying to balance out capacity problems or finite your final
operations
> to the ship date and/or the capacity of the assembly/pack-out
> department. We will probably do this for some time to come
until
we can
> get any level of confidence in finite scheduling.
>
> Steve



To access the Files Section of our Yahoo!Group for Report
Builder and Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have
already linked your email address to a yahoo id to enable access.

Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
Your message is being forwarding to production control, maybe it will
help them think 'out of the box'.

In regard to the forward scheduling bug, if your workcenters aren't
set for finite capacity, can you successfully forward schedule a
job? If so then the theory, that there is a relationship between
this bug and work centers being set for finite capacity, is shot
down. Just the programmer in me trying to find cause and effect.

Thanks for the assistance,

Lonnie
ldrew@...
lonniedrew@...

--- In vantage@y..., Steve Wirtz <SWirtz@m...> wrote:
> Lonnie,
>
> We don't finite capacity anything now. We infinite schedule and
look at
> our work center capacity and load. We also like to keep the
pressure on
> the shop. If we don't, they won't meet the rates they need. Also,
if
> there is a problem that delays a job, e.g. material, non-
conformance,
> etc., and we have finite scheduled the work center, we find the work
> center feeling very comfortable as they now have plenty of time to
> finish the next operation. The shop management and supervisors
like the
> added pressure as it provides a challenge for them. Don't get me
wrong,
> they will scream if there is a lot more load than they can
handle.
>
> When we schedule a job we look at work centers that may have a
capacity
> problem and look at the work center visual scheduling board after
> initial scheduling of the job. Then we drag and drop the
operations to
> fit in the work center scheduling board, then go back and finish the
> detail job scheduling by drag and drop. This may take a little
extra
> time, but we end up with a pretty good finite schedule having
handling
> our work center capacity area. In the case of two jobs with tight
> committed delivery dates, infinite scheduling (with watching our
> capacities) allows us to schedule more hours than in the normal day
> which well can make up with overtime, added labor or other
workarounds.
>
> You can check your work center capacity by the priority dispatch
reports
> and looking at your visual scheduling board. We set up a shop load
> report in report builder which gives us our shop load in hours by
work
> center by day. This is better than just looking at priority
dispatch
> and the work center visual scheduling board for us as it also
includes
> the crew sizes and totals the labor for the operation.
>
> Steve
Lonnie,

We only do infinite scheduling. Most of our work centers do have finite
scheduling. The finite portion only works when you are scheduling an
individual job. As we schedule an individual job, we don't want that
job to be scheduled all within one day because of infinite work center
scheduling. So as we are a one shift operation and we have shown 8.0
hours of a day, infinite scheduling will still take an operation with 16
hours run time and spread that over two or three days. In 5.0 it should
also finite schedule from one assembly to another. In 3.0 scheduling
did not link well with parent assemblies, where in 5.0 it is supposed to
link better to higher assemblies.

We since we drag and drop, we have taken most of the move and queue
times out of our work centers. We found that added unrealistic pad to
the schedules and again took the pressure off the shop. We have been
detail scheduling for 1.5 years now and will only put them back in when
we really understand the system and Vantage does a better job of
scheduling. About 6-8 months ago, we brought in Epicor's Scheduling
Expert, Steve Wieland (SP?) for a two day training class primarily in
scheduling. I believe Steve used to run all of Epicor's training
classes. He was outstanding. We found that our specific needs training
was less expensive and more worthwhile for several people here than
sending 1 person to a class at Epicor. Steve wanted to get out and
visit with users once in awhile. I would recommend you contact him and
see if he can answer your questions and/or would be willing to provide
another onsite training class.

I ran an experiment for you a short time ago by scheduling two jobs.

Job 1, Has 9 Assemblies and 17 Total 0perations. It took less than a
minute to forward schedule (didn't time that accurately) and 5 seconds
to back schedule.

Job 2, (One of our more complex jobs), Has 33 Assemblies and 86 Total
Operations. It took 6.5 minutes to forward schedule and 50 seconds to
back schedule.

These times are longer than 3.0, but 5.0 does more scheduling functions.


I would be willing to talk with your folks if I could be of assistance.
I know 3.0 scheduling pretty well, but since we just went live with 5.0
on Monday, I've got a lot more to learn.

Hope some of this helps,

Steve



-----Original Message-----
From: Lonnie Drew [SMTP:lonniedrew@...]
Sent: Wednesday, July 11, 2001 3:10 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Problem Forward Scheduling Jobs in
5.0

Your message is being forwarding to production control, maybe it
will
help them think 'out of the box'.

In regard to the forward scheduling bug, if your workcenters
aren't
set for finite capacity, can you successfully forward schedule a

job? If so then the theory, that there is a relationship
between
this bug and work centers being set for finite capacity, is shot

down. Just the programmer in me trying to find cause and
effect.

Thanks for the assistance,

Lonnie
ldrew@...
lonniedrew@...

--- In vantage@y..., Steve Wirtz <SWirtz@m...> wrote:
> Lonnie,
>
> We don't finite capacity anything now. We infinite schedule
and
look at
> our work center capacity and load. We also like to keep the
pressure on
> the shop. If we don't, they won't meet the rates they need.
Also,
if
> there is a problem that delays a job, e.g. material, non-
conformance,
> etc., and we have finite scheduled the work center, we find
the work
> center feeling very comfortable as they now have plenty of
time to
> finish the next operation. The shop management and
supervisors
like the
> added pressure as it provides a challenge for them. Don't get
me
wrong,
> they will scream if there is a lot more load than they can
handle.
>
> When we schedule a job we look at work centers that may have a

capacity
> problem and look at the work center visual scheduling board
after
> initial scheduling of the job. Then we drag and drop the
operations to
> fit in the work center scheduling board, then go back and
finish the
> detail job scheduling by drag and drop. This may take a
little
extra
> time, but we end up with a pretty good finite schedule having
handling
> our work center capacity area. In the case of two jobs with
tight
> committed delivery dates, infinite scheduling (with watching
our
> capacities) allows us to schedule more hours than in the
normal day
> which well can make up with overtime, added labor or other
workarounds.
>
> You can check your work center capacity by the priority
dispatch
reports
> and looking at your visual scheduling board. We set up a shop
load
> report in report builder which gives us our shop load in hours
by
work
> center by day. This is better than just looking at priority
dispatch
> and the work center visual scheduling board for us as it also
includes
> the crew sizes and totals the labor for the operation.
>
> Steve



To access the Files Section of our Yahoo!Group for Report
Builder and Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have
already linked your email address to a yahoo id to enable access.

Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
Steve,

Rereading my last message, I stated incorrectly "if your workcenters
AREN'T set for finite scheduling, and you can can forward schedule,
then the proposed cause is in question". I should have said "ARE set
for finite scheduling".

From your test, you were able to forward schedule an individual job
with finite capacity workcenters. Since we can't with the same
scenario, something else must be causing this mess. 6.5 minutes to
forward schedule a single job is still a long time (but a lot better
than our 1.5 HOURS to get 33%).

Thank you for your offer. I'll let production control know there are
resources available. (This is my first involvement with scheduling
over the last 3.5 years - it's been smooth sailing until now)

Thanks again,

Lonnie

--- In vantage@y..., Steve Wirtz <SWirtz@m...> wrote:
> Lonnie,
>
> We only do infinite scheduling. Most of our work centers do have
finite
> scheduling. The finite portion only works when you are scheduling
an
> individual job. As we schedule an individual job, we don't want
that
> job to be scheduled all within one day because of infinite work
center
> scheduling. So as we are a one shift operation and we have shown
8.0
> hours of a day, infinite scheduling will still take an operation
with 16
> hours run time and spread that over two or three days. In 5.0 it
should
> also finite schedule from one assembly to another. In 3.0
scheduling
> did not link well with parent assemblies, where in 5.0 it is
supposed to
> link better to higher assemblies.
>
> We since we drag and drop, we have taken most of the move and queue
> times out of our work centers. We found that added unrealistic pad
to
> the schedules and again took the pressure off the shop. We have
been
> detail scheduling for 1.5 years now and will only put them back in
when
> we really understand the system and Vantage does a better job of
> scheduling. About 6-8 months ago, we brought in Epicor's Scheduling
> Expert, Steve Wieland (SP?) for a two day training class primarily
in
> scheduling. I believe Steve used to run all of Epicor's training
> classes. He was outstanding. We found that our specific needs
training
> was less expensive and more worthwhile for several people here than
> sending 1 person to a class at Epicor. Steve wanted to get out and
> visit with users once in awhile. I would recommend you contact him
and
> see if he can answer your questions and/or would be willing to
provide
> another onsite training class.
>
> I ran an experiment for you a short time ago by scheduling two jobs.
>
> Job 1, Has 9 Assemblies and 17 Total 0perations. It took less than
a
> minute to forward schedule (didn't time that accurately) and 5
seconds
> to back schedule.
>
> Job 2, (One of our more complex jobs), Has 33 Assemblies and 86
Total
> Operations. It took 6.5 minutes to forward schedule and 50 seconds
to
> back schedule.
>
> These times are longer than 3.0, but 5.0 does more scheduling
functions.
>
>
> I would be willing to talk with your folks if I could be of
assistance.
> I know 3.0 scheduling pretty well, but since we just went live with
5.0
> on Monday, I've got a lot more to learn.
>
> Hope some of this helps,
>
> Steve