# Order Job Wiz Schedule all

Even if you are forward scheduling infinite capacity, the system will
calculate what it believes is the optimal start date based on the
parameters and information you've given it. Regardless if you have the
resources to actually execute its suggested schedule. While infinite
scheduling will not take into account capacity it will honor work days
as defined in a resource or resource group calendar.

From what I've seen forward usually begins at today's (current) date and
then calculates from the lowest level upwards all the components and
their start dates. Quantities and run times then determine the due
dates which then are the start times of subsequent operations (move and
queue times as defined are calculated there too - except the last
operation move on a given level and the first queue on an upper level ).
The entire premise of forward scheduling is based on the fact that you
will begin work on something today, or at a future date (an historical
date provides a solution that is not logical). Try selecting the
current date. If that provides the product too soon you can reschedule
it out further based on your initial results...

Currently we are having reasonable success with backward finite global
scheduling (90% of our orders are blanket). But even that is a misnomer
to some extent as we do not allow historical dates, and the system using
that logic will schedule back from the customer required date until it
hits the current date, at which point it will then finitely forward
schedule.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Michael McWilliams
Sent: Monday, July 06, 2009 6:54 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Order Job Wiz Schedule all

We would normally use forward scheduling. I don't see how I can set that
up only choose it if I am scheduling from Job Entry. Infinite capacity
but we do not have the schedule set up as 7 days. There is not any que
time or receive time. I did not know we could change historical dates
setting, but if it forces it to the current date we are alright with
that. Basically we have eliminated Job Entry by using the wizard with a
BPM to copy some custom fields. Right now we use the ship date to be the
start date because that is what it seems to set it to. However that does
not always seem to be the case. I have not been able to see it first
hand but get complaints about items being scheduled a month past the
Ship By on the order line.
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Rob
Bucek" <rbucek@...> wrote:
>
> That wholly depends on what methods are being used... are you forward
or
> backward scheduling? Finite or infinite? Does your system allow
> historical dates? Do you have receive time set for those parts? Move
> and queue for the scheduled resources are a factor with multiple
> operations that exist on a particular assembly (move time on last ops
> from a lower level and queue time on first ops of a higher level are
not
> honored).
>
>
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
> Of Michael McWilliams
> Sent: Monday, July 06, 2009 2:00 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Order Job Wiz Schedule all
>
>
>
>
>
> What logic does the schedule engine use in the Order Job Wizard to
> determine Start Date? It looks to me like it is making the start date
> the exact same date as the ship by date on the order if it is a single
> op & a business day earlier if it is a 2 op job. What other factors go
> into determining the start date it gives?
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]
What logic does the schedule engine use in the Order Job Wizard to determine Start Date? It looks to me like it is making the start date the exact same date as the ship by date on the order if it is a single op & a business day earlier if it is a 2 op job. What other factors go into determining the start date it gives?
That wholly depends on what methods are being used... are you forward or
backward scheduling? Finite or infinite? Does your system allow
historical dates? Do you have receive time set for those parts? Move
and queue for the scheduled resources are a factor with multiple
operations that exist on a particular assembly (move time on last ops
from a lower level and queue time on first ops of a higher level are not
honored).

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Michael McWilliams
Sent: Monday, July 06, 2009 2:00 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Order Job Wiz Schedule all

What logic does the schedule engine use in the Order Job Wizard to
determine Start Date? It looks to me like it is making the start date
the exact same date as the ship by date on the order if it is a single
op & a business day earlier if it is a 2 op job. What other factors go
into determining the start date it gives?

[Non-text portions of this message have been removed]
We would normally use forward scheduling. I don't see how I can set that up only choose it if I am scheduling from Job Entry. Infinite capacity but we do not have the schedule set up as 7 days. There is not any que time or receive time. I did not know we could change historical dates setting, but if it forces it to the current date we are alright with that. Basically we have eliminated Job Entry by using the wizard with a BPM to copy some custom fields. Right now we use the ship date to be the start date because that is what it seems to set it to. However that does not always seem to be the case. I have not been able to see it first hand but get complaints about items being scheduled a month past the Ship By on the order line.
--- In vantage@yahoogroups.com, "Rob Bucek" <rbucek@...> wrote:
>
> That wholly depends on what methods are being used... are you forward or
> backward scheduling? Finite or infinite? Does your system allow
> historical dates? Do you have receive time set for those parts? Move
> and queue for the scheduled resources are a factor with multiple
> operations that exist on a particular assembly (move time on last ops
> from a lower level and queue time on first ops of a higher level are not
> honored).
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Michael McWilliams
> Sent: Monday, July 06, 2009 2:00 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Order Job Wiz Schedule all
>
>
>
>
>
> What logic does the schedule engine use in the Order Job Wizard to
> determine Start Date? It looks to me like it is making the start date
> the exact same date as the ship by date on the order if it is a single
> op & a business day earlier if it is a 2 op job. What other factors go
> into determining the start date it gives?
>
>
>
>
>
> [Non-text portions of this message have been removed]
>