Paul,
FWIW...
demand of jobs which did not have the Engineered and the Released boxes
checked? [Scott's comment] see below
scheduling function as well when releasing a job to the floor? [Scott's
comment] see below
statement that I sent to our job planners seven months ago. I was
subsequently told by Epicor that this logic would remain the same in Vantage
8.0.
Job planners:
Yesterday, while reviewing job statuses specified in Vantage, I just
happened to notice the following statement in Vantage Help regarding the
"Engineered" status:
If you unmark the engineered toggle and the job had already been scheduled,
the schedule for the job will be removed.
This statement surprised me because it contradicted my understanding of
Vantage. Interestingly enough, when I contacted Vantage Support to confirm
the validity of the statement, the lady to whom I spoke was apparently just
as surprised. In fact, she placed my call on hold for quite some time while
she confirmed the statement internally. She eventually confirmed that this
has been the case since at least version 6.0.
While this statement may seem unimportant, it is not. The removal of a job
schedule from Vantage will have a significant ripple effect. The start
dates for the job operations will be removed from the system. In turn, when
the generate suggestions function is run, no suggestions will be generated
for material requirements related to operations that are missing start dates
and existing purchasing suggestions might even be removed. In turn, the
standard time-phased material requirements report and the custom suggested
material purchases sorted by planner report would be incomplete. Please see
the attached document, Purchasing Features in Vantage, that probably better
presents the potential impact of removing a job schedule from the system.
In any case, I believe the bottom line is the following. If you un-engineer
a job to make changes to it, be sure to re-run the job scheduling function
when you re-mark the engineered check box.
HTH.
Regards,
Scott
-----Original Message-----
From: Chris Robisch [mailto:blue.wine@...]
Sent: Tuesday, January 04, 2005 2:53 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Generating Suggestions (Purchasing Module)
You've asked a lot of questions but I'll just concentrate on the fact that
you're a custom engineering firm like Electroimpact rather than a
manufacturer. We'll have a job that consists of 1500 assemblies, 5000
operations and 5000 materials. The job may be open for 3 years or more
depending on the contract with the customer. The engineers have to order
material and see if it works immediately, not wait for the schedule to say
so. Therefore, the due date on the job is meaningless as is the default PO
date which comes from it. We schedule the job but only to provide the green
check mark for completed internal operations. Most materials automatically
have constraints -- the red dot -- because it's all one-of-a-kind stuff --
lead times and dates don't make sense. We're building machines that assemble
aircraft like the Airbus A380 wings.
Purchasing is the biggest bottleneck for us. Our engineers want it EASY to
do. Their time is too valuable too waste on information lost in purchasing
departments and software that assumes we're a manufacturer. Our biggest cost
is engineering, not materials. When Epicor realizes this scenario is a fact
of life for some companies, maybe they'll begin to furnish us some tools
that make sense in our environment.
FWIW...
> Is anyone else experiencing 25 minute processing times? [Scott's comment]here, typically 5-6 minutes
> Is there any DB housekeeping that shortens the processing time? [Scott'scomment] none that I know
> Could I run this as a scheduled process (say around midnight)? [Scott'scomment] I don't know
> Am I correct in assuming that if this process is run during working times(i.e. 8-5 when engineers have jobs open), the results do not include the
demand of jobs which did not have the Engineered and the Released boxes
checked? [Scott's comment] see below
> What is the exact role of the Scheduling function in Job Entry, withregards to generating purchasing function? Will I have to hit the
scheduling function as well when releasing a job to the floor? [Scott's
comment] see below
>Rather than restate the information to fit your questions, here is a
statement that I sent to our job planners seven months ago. I was
subsequently told by Epicor that this logic would remain the same in Vantage
8.0.
Job planners:
Yesterday, while reviewing job statuses specified in Vantage, I just
happened to notice the following statement in Vantage Help regarding the
"Engineered" status:
If you unmark the engineered toggle and the job had already been scheduled,
the schedule for the job will be removed.
This statement surprised me because it contradicted my understanding of
Vantage. Interestingly enough, when I contacted Vantage Support to confirm
the validity of the statement, the lady to whom I spoke was apparently just
as surprised. In fact, she placed my call on hold for quite some time while
she confirmed the statement internally. She eventually confirmed that this
has been the case since at least version 6.0.
While this statement may seem unimportant, it is not. The removal of a job
schedule from Vantage will have a significant ripple effect. The start
dates for the job operations will be removed from the system. In turn, when
the generate suggestions function is run, no suggestions will be generated
for material requirements related to operations that are missing start dates
and existing purchasing suggestions might even be removed. In turn, the
standard time-phased material requirements report and the custom suggested
material purchases sorted by planner report would be incomplete. Please see
the attached document, Purchasing Features in Vantage, that probably better
presents the potential impact of removing a job schedule from the system.
In any case, I believe the bottom line is the following. If you un-engineer
a job to make changes to it, be sure to re-run the job scheduling function
when you re-mark the engineered check box.
HTH.
Regards,
Scott
-----Original Message-----
From: Chris Robisch [mailto:blue.wine@...]
Sent: Tuesday, January 04, 2005 2:53 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Generating Suggestions (Purchasing Module)
You've asked a lot of questions but I'll just concentrate on the fact that
you're a custom engineering firm like Electroimpact rather than a
manufacturer. We'll have a job that consists of 1500 assemblies, 5000
operations and 5000 materials. The job may be open for 3 years or more
depending on the contract with the customer. The engineers have to order
material and see if it works immediately, not wait for the schedule to say
so. Therefore, the due date on the job is meaningless as is the default PO
date which comes from it. We schedule the job but only to provide the green
check mark for completed internal operations. Most materials automatically
have constraints -- the red dot -- because it's all one-of-a-kind stuff --
lead times and dates don't make sense. We're building machines that assemble
aircraft like the Airbus A380 wings.
Purchasing is the biggest bottleneck for us. Our engineers want it EASY to
do. Their time is too valuable too waste on information lost in purchasing
departments and software that assumes we're a manufacturer. Our biggest cost
is engineering, not materials. When Epicor realizes this scenario is a fact
of life for some companies, maybe they'll begin to furnish us some tools
that make sense in our environment.
----- Original Message -----
From: "Paul Siebers" <paul.siebers@...>
To: <vantage@yahoogroups.com>
Sent: Tuesday, January 04, 2005 11:09 AM
Subject: [Vantage] Generating Suggestions (Purchasing Module)
> All,
>
> After having our purchasing module sit dormant for a few years we are
ready to use it again. I noticed that "Generate Suggestions" function on
the in Purchase Management/General Operations menu takes a while to run.
> Our purchasing clerks usually run the suggestions first thing in the
morning, when they come in. I hate for them to idle while they are waiting
for the program to finish running. I am sure they don't mind, though.
>
> A few questions:
> Is anyone else experiencing 25 minute processing times?
> Is there any DB housekeeping that shortens the processing time?
> Could I run this as a scheduled process (say around midnight)?
> Am I correct in assuming that if this process is run during working times
(ie 8-5 when engineers have jobs open), the results do not include the
demand of jobs which did not have the Engineered and the Released boxes
checked?
> What is the exact role of the Scheduling function in Job Entry, with
regards to generating purchasing function? Will I have to hit the
scheduling function as well when releasing a job to the floor?
>
> TIA,
>
> Paul Siebers
[Non-text portions of this message have been removed]