SETTING the Released flag to true & Mass Print flag to true is no big deal. (If you think you are going to autoprint directly from a BPM, I think you are in for a disappointment... Lower you sights and just mark them for mass print and then regularly do mass printing as part of your process).
Where I think you are really under-estimating complexity is triggering your processing. If ALL of your jobs only ever have one material detail - then triggering your process is reasonably simple as each receipt action cleanly can fulfill any unissued job requirements - and you'd KNOW it is the only required material for the job.
If your jobs have multiple material details (ours have 15-25 typically), I don;t see this as ever working. When jobs have multiple material details it is pretty common to have more than one with a shortage awaiting a receipt to fulfill.
How would your process handle that? Even if a job with two or more shortages had receipts within a day that cover the shortages, triggering a BPM on each individual receipt action would likely NOT show all other required materials as fully available. Certainly relying on super-simplified allocations < o/h won't cut it in most environments. You would literally have to do a time phase type calc on each Job Mtl detail (after each receipt) and verify all material detail requirements are covered (from a time phase perspective).
Not a simple task.
We take another approach, we use a BAQ based dashboard to allow production control to once/twice a day look at all jobs with open material detail requirements for just received parts that, prior to receipt, had o/h < allocations.
All these jobs (potentially) have been freed by the receipt to be pulled in and immediately released. They then check material status on each of these jobs (using time phase on components where allocations are still > o/h) and then make the decision on whether or not the job can be pulled in and released. (About 40% of our jobs are customer constrained by a "Not Before' earliest ship date they will accept - so this plays into the decision making as well.)
I'm not trying to discourage you... I hope you have a plan that handles these conditions (and are then willing to share with the rest of us!).
I'd love to here more detail.
This is one of the biggest complaints from our production control department since going live on Vantage.
On our legacy system, I was able to do a SQL based time phase on each open job material detail requirement (also pre-filtering based upon customer limitations to pulling in future scheduled jobs). They were then presented with a VERY focused list to zip through, confirm and (in most cases) pull in and release. (About an hour per day required.)
Vantage's BAQ (because of the inability to join a table into a query multiple times) has stymied all my efforts to fully reproduce. They now consume about 3 hours per day to get through receipt & pull job in & release. (It is not as effective either as opportunities for pull ins are missed because of the shear tediousness of the highly manual process.)
I'm all ears if you have another way in mind.
Rob
Where I think you are really under-estimating complexity is triggering your processing. If ALL of your jobs only ever have one material detail - then triggering your process is reasonably simple as each receipt action cleanly can fulfill any unissued job requirements - and you'd KNOW it is the only required material for the job.
If your jobs have multiple material details (ours have 15-25 typically), I don;t see this as ever working. When jobs have multiple material details it is pretty common to have more than one with a shortage awaiting a receipt to fulfill.
How would your process handle that? Even if a job with two or more shortages had receipts within a day that cover the shortages, triggering a BPM on each individual receipt action would likely NOT show all other required materials as fully available. Certainly relying on super-simplified allocations < o/h won't cut it in most environments. You would literally have to do a time phase type calc on each Job Mtl detail (after each receipt) and verify all material detail requirements are covered (from a time phase perspective).
Not a simple task.
We take another approach, we use a BAQ based dashboard to allow production control to once/twice a day look at all jobs with open material detail requirements for just received parts that, prior to receipt, had o/h < allocations.
All these jobs (potentially) have been freed by the receipt to be pulled in and immediately released. They then check material status on each of these jobs (using time phase on components where allocations are still > o/h) and then make the decision on whether or not the job can be pulled in and released. (About 40% of our jobs are customer constrained by a "Not Before' earliest ship date they will accept - so this plays into the decision making as well.)
I'm not trying to discourage you... I hope you have a plan that handles these conditions (and are then willing to share with the rest of us!).
I'd love to here more detail.
This is one of the biggest complaints from our production control department since going live on Vantage.
On our legacy system, I was able to do a SQL based time phase on each open job material detail requirement (also pre-filtering based upon customer limitations to pulling in future scheduled jobs). They were then presented with a VERY focused list to zip through, confirm and (in most cases) pull in and release. (About an hour per day required.)
Vantage's BAQ (because of the inability to join a table into a query multiple times) has stymied all my efforts to fully reproduce. They now consume about 3 hours per day to get through receipt & pull job in & release. (It is not as effective either as opportunities for pull ins are missed because of the shear tediousness of the highly manual process.)
I'm all ears if you have another way in mind.
Rob
--- On Sat, 12/6/08, bbvantage <bbutler@...> wrote:
From: bbvantage <bbutler@...>
Subject: [Vantage] BPM: Release Job When Sufficient Material is received
To: vantage@yahoogroups.com
Date: Saturday, December 6, 2008, 11:16 AM
I would like to create a BPM to release and print a job when
sufficient material is received. The idea is as follows;
On Material receipt check all open firm / unreleased jobs requiring
that material. If a job is found which fits this criteria
automatically release and print it.
One stumbling block would be multiple jobs using the same material,
and having the [total required for all jobs] > [available material].
This happens such a low percentage of time that I am willing to ignore
it.
The other side of this would be to automatically release and print
after a job is engineered if material is available.
Any ideas here would be appreciated.
Thank you,
Bruce