I already have just what you described in place. I would say that 90%
of our jobs for the coming week (i.e. due in the coming week after we
run Global - Sunday nights) are already firmed in the system. We do
have some short lead time stuff that end up rolling in as MRP suggested
jobs.
We usually firm at least two weeks out during the week before MRP/Global
runs. You're right it does work like a charm.
It's those jobs that I want firmed just after MRP runs and subsequently
reprioritized before calculate global scheduling runs. To have someone
here consistently in the timing required wouldn't be feasible. Through
some savvy negotiation I'm actually getting a few hours of one on one
time with Epicor's lead programmer for their scheduling engine at
Perspectives...
Hopefully I can effectively get some help through him...
I've had some great success by targeting job priorities and having the
system produce a fairly favorable (for us) schedule. There is a bit of
tweaking yet to do but I have a very good road map now to get where I'm
going I think. I'm just short a few tools to get there.
The frustrating thing about their scheduling algorithm is that it
doesn't take into account the reality of the now. Out of the box Epicor
doesn't give us any ability to set Job priority automatically by a set
of user defined rules. In addition to change job priority the job must
be firmed. The system goes through these gyrations to determine what it
thinks is relative job priority and happily occupies capacity today for
a job due next month under the assumption that if I don't start it now
it might be late. That's all fine and dandy except when I go to our
customer today and tell him I shut his line down because we were working
on a job that we might be late on that he needs next month...actually it
might be worth having that conversation just to see the look on their
faces...
When were out there running jobs in the hundreds (and for some maybe
thousands) per week doing this manually is just not feasible. I created
a manual BPM (inspired by Nigel Kerly) to change job priorities based on
a set of criteria I define in the UD record and it works slick. This
just all needs to be tied together into one fluid process that doesn't
need to be babysitted and require someone to be away from their families
at odd hours of the week.
Rob Bucek
Manufacturing Engineer
PH: (715) 284-5376 ext 3111
FAX: (715)284-4084
<http://www.dsmfg.com/>
(Click the logo to view our site) <http://www.dsmfg.com/>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Sunday, October 25, 2009 4:24 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] MRP customizations
Rob,
I'll ask (re DTS).
If you are just batch firming, why not write yourself a date fenced, BAQ
(to only pull in unfirmed jobs) and use ti from Job Status Maintenance?
That app is intended to do the very thing you describe as wanting to do:
mass Firming (and engineering and releasing).
We using it for mass releasing (with custom BAQs to fit our process) &
it works like a charm.
Give it a try. (??)
Rob
________________________________
From: Rob Bucek <rbucek@... <mailto:rbucek%40dsmfg.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Thu, October 22, 2009 9:05:37 AM
Subject: RE: [Vantage] MRP customizations
Not that I didn't believe you Rob! I gave it a whack just to see what
it would do and you're very correct in your assessment. Without the BO
present, the process was a bit lacking. It would seem like a fairly
gravy work flow. Thanks for the input! Would he be willing to share
how he fired that DTS package off?
Rob Bucek
Manufacturing Engineer
PH: (715) 284-5376 ext 3111
FAX: (715)284-4084
<http://www.dsmfg com/>
(Click the logo to view our site) <http://www.dsmfg com/>
From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf
Of robertb_versa@ yahoo.com
Sent: Wednesday, October 21, 2009 7:56 PM
To: vantage@yahoogroups .com
Subject: RE: [Vantage] MRP customizations
Rob
Brian's idea sounds more appropriate as Firming is more than updating a
single field per record. It is a BO method that updates many things per
job.
SC sounds like the way to go!
Rob Brown
--- Original Message ---
From:"Rob Bucek" <rbucek@dsmfg. com <mailto:rbucek% 40dsmfg.com> >
Sent:Wed 10/21/09 4:56 pm
To:<vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> >
Subj:RE: [Vantage] MRP customizations
LOL thanks Brian!! That seems like another very legitimate solution to
my problem. I'll let you know how it turns out.
Rob Bucek
Manufacturing Engineer
PH: (715) 284-5376 ext 3111
FAX: (715)284-4084
<http://www.dsmfg com/>
(Click the logo to view our site) <http://www.dsmfg com/>
From: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
[mailto:vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> ]
On
Behalf
Of Brian W. Spolarich
Sent: Wednesday, October 21, 2009 3:50 PM
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
Subject: RE: [Vantage] MRP customizations
How about a scheduled BAQ that lists the jobs that MRP creates that gets
launched after MRP is done.
You can apparently give the BAQ Export Process program a full UNC path
as its output directory and it will put the file there. So you can say:
\\server\mfgsysdata \reports\ user\subdir\ foo.xml
And you could have ServiceConnect watch that directory.
Presumably if the user that Vantage/Progress is running as is permitted
to write to the share/directory you could host this directory elsewhere
(I have a domain account that the appservers run as).
You can't put 'subdir\foo. xml' in your 'Output to' field, as Vantage
will complain that the directory doesn't exist. But the fully-qualified
UNC path works.
That would be a relatively clean solution:
- Run MRP in a nightly task.
- Run a BAQ after the nightly task that outputs to a directory. The BAQ
lists the jobs that need attention (or at least includes them).
- Watch that directory as a SC InputChannel to kick off your workflow.
- Process the jobs in SC making decisions about whether to invoke
JobStatus.ChangeJob HeadFirm (I'm guessing that's the method).
I apparently need some of my own work to do today.
-bws
--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@advanced photonix. com
<mailto:bspolarich% 40advancedphoton ix.com>
<mailto:bspolarich% 40advancedphoton ix.com> ~ 734-864-5618 ~
www.advancedphotoni x.com
-----Original Message-----
From: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com>
[mailto:vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com> ] On
Behalf Of robertb_versa@ yahoo.com <mailto:robertb_ versa%40yahoo. com>
<mailto:robertb_ versa%40yahoo. com>
Sent: Wednesday, October 21, 2009 4:31 PM
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com>
Subject: Re: [Vantage] MRP customizations
Rob
Our IT manager has a process that unengineers make-direct jobs created &
scheduled by order job wizard. I believe it is BAM triggered (by new
JobHead records) that fires off a DTS package flip of the engineered
flag to unengineered.
Your need sounds trickier as Firming entails a BO method that does a
number of things (including changing the jobnum) so this might require
an SC solution.
Rob
--- Original Message ---
From:"Rob Bucek" <rbucek@dsmfg. com <mailto:rbucek% 40dsmfg.com>
<mailto:rbucek% 40dsmfg.com> >
Sent:Wed 10/21/09 1:20 pm
To:<vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com> >
Subj:[Vantage] MRP customizations
Anyone out there done any customization or tinkering with the DNA code
for
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
of our jobs for the coming week (i.e. due in the coming week after we
run Global - Sunday nights) are already firmed in the system. We do
have some short lead time stuff that end up rolling in as MRP suggested
jobs.
We usually firm at least two weeks out during the week before MRP/Global
runs. You're right it does work like a charm.
It's those jobs that I want firmed just after MRP runs and subsequently
reprioritized before calculate global scheduling runs. To have someone
here consistently in the timing required wouldn't be feasible. Through
some savvy negotiation I'm actually getting a few hours of one on one
time with Epicor's lead programmer for their scheduling engine at
Perspectives...
Hopefully I can effectively get some help through him...
I've had some great success by targeting job priorities and having the
system produce a fairly favorable (for us) schedule. There is a bit of
tweaking yet to do but I have a very good road map now to get where I'm
going I think. I'm just short a few tools to get there.
The frustrating thing about their scheduling algorithm is that it
doesn't take into account the reality of the now. Out of the box Epicor
doesn't give us any ability to set Job priority automatically by a set
of user defined rules. In addition to change job priority the job must
be firmed. The system goes through these gyrations to determine what it
thinks is relative job priority and happily occupies capacity today for
a job due next month under the assumption that if I don't start it now
it might be late. That's all fine and dandy except when I go to our
customer today and tell him I shut his line down because we were working
on a job that we might be late on that he needs next month...actually it
might be worth having that conversation just to see the look on their
faces...
When were out there running jobs in the hundreds (and for some maybe
thousands) per week doing this manually is just not feasible. I created
a manual BPM (inspired by Nigel Kerly) to change job priorities based on
a set of criteria I define in the UD record and it works slick. This
just all needs to be tied together into one fluid process that doesn't
need to be babysitted and require someone to be away from their families
at odd hours of the week.
Rob Bucek
Manufacturing Engineer
PH: (715) 284-5376 ext 3111
FAX: (715)284-4084
<http://www.dsmfg.com/>
(Click the logo to view our site) <http://www.dsmfg.com/>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: Sunday, October 25, 2009 4:24 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] MRP customizations
Rob,
I'll ask (re DTS).
If you are just batch firming, why not write yourself a date fenced, BAQ
(to only pull in unfirmed jobs) and use ti from Job Status Maintenance?
That app is intended to do the very thing you describe as wanting to do:
mass Firming (and engineering and releasing).
We using it for mass releasing (with custom BAQs to fit our process) &
it works like a charm.
Give it a try. (??)
Rob
________________________________
From: Rob Bucek <rbucek@... <mailto:rbucek%40dsmfg.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Thu, October 22, 2009 9:05:37 AM
Subject: RE: [Vantage] MRP customizations
Not that I didn't believe you Rob! I gave it a whack just to see what
it would do and you're very correct in your assessment. Without the BO
present, the process was a bit lacking. It would seem like a fairly
gravy work flow. Thanks for the input! Would he be willing to share
how he fired that DTS package off?
Rob Bucek
Manufacturing Engineer
PH: (715) 284-5376 ext 3111
FAX: (715)284-4084
<http://www.dsmfg com/>
(Click the logo to view our site) <http://www.dsmfg com/>
From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf
Of robertb_versa@ yahoo.com
Sent: Wednesday, October 21, 2009 7:56 PM
To: vantage@yahoogroups .com
Subject: RE: [Vantage] MRP customizations
Rob
Brian's idea sounds more appropriate as Firming is more than updating a
single field per record. It is a BO method that updates many things per
job.
SC sounds like the way to go!
Rob Brown
--- Original Message ---
From:"Rob Bucek" <rbucek@dsmfg. com <mailto:rbucek% 40dsmfg.com> >
Sent:Wed 10/21/09 4:56 pm
To:<vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> >
Subj:RE: [Vantage] MRP customizations
LOL thanks Brian!! That seems like another very legitimate solution to
my problem. I'll let you know how it turns out.
Rob Bucek
Manufacturing Engineer
PH: (715) 284-5376 ext 3111
FAX: (715)284-4084
<http://www.dsmfg com/>
(Click the logo to view our site) <http://www.dsmfg com/>
From: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
[mailto:vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> ]
On
Behalf
Of Brian W. Spolarich
Sent: Wednesday, October 21, 2009 3:50 PM
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
Subject: RE: [Vantage] MRP customizations
How about a scheduled BAQ that lists the jobs that MRP creates that gets
launched after MRP is done.
You can apparently give the BAQ Export Process program a full UNC path
as its output directory and it will put the file there. So you can say:
\\server\mfgsysdata \reports\ user\subdir\ foo.xml
And you could have ServiceConnect watch that directory.
Presumably if the user that Vantage/Progress is running as is permitted
to write to the share/directory you could host this directory elsewhere
(I have a domain account that the appservers run as).
You can't put 'subdir\foo. xml' in your 'Output to' field, as Vantage
will complain that the directory doesn't exist. But the fully-qualified
UNC path works.
That would be a relatively clean solution:
- Run MRP in a nightly task.
- Run a BAQ after the nightly task that outputs to a directory. The BAQ
lists the jobs that need attention (or at least includes them).
- Watch that directory as a SC InputChannel to kick off your workflow.
- Process the jobs in SC making decisions about whether to invoke
JobStatus.ChangeJob HeadFirm (I'm guessing that's the method).
I apparently need some of my own work to do today.
-bws
--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@advanced photonix. com
<mailto:bspolarich% 40advancedphoton ix.com>
<mailto:bspolarich% 40advancedphoton ix.com> ~ 734-864-5618 ~
www.advancedphotoni x.com
-----Original Message-----
From: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com>
[mailto:vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com> ] On
Behalf Of robertb_versa@ yahoo.com <mailto:robertb_ versa%40yahoo. com>
<mailto:robertb_ versa%40yahoo. com>
Sent: Wednesday, October 21, 2009 4:31 PM
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com>
Subject: Re: [Vantage] MRP customizations
Rob
Our IT manager has a process that unengineers make-direct jobs created &
scheduled by order job wizard. I believe it is BAM triggered (by new
JobHead records) that fires off a DTS package flip of the engineered
flag to unengineered.
Your need sounds trickier as Firming entails a BO method that does a
number of things (including changing the jobnum) so this might require
an SC solution.
Rob
--- Original Message ---
From:"Rob Bucek" <rbucek@dsmfg. com <mailto:rbucek% 40dsmfg.com>
<mailto:rbucek% 40dsmfg.com> >
Sent:Wed 10/21/09 1:20 pm
To:<vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com> >
Subj:[Vantage] MRP customizations
Anyone out there done any customization or tinkering with the DNA code
for
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]