One Resource, Two Warehouses

system · March 6, 2009, 2:27pm

Yup. That will work if you only have one backflush whse/bin per part.

We have up to half a dozen (so must control at resource).

If you can get away with it though, it doesn't get any easier than that. (Great idea!)

Rob

--- On Fri, 3/6/09, Rick Bird <rbird@...> wrote:

From: Rick Bird <rbird@...>
Subject: [Vantage] Re: One Resource, Two Warehouses
To: vantage@yahoogroups.com
Date: Friday, March 6, 2009, 10:13 AM

I beleive I have found a possible 4th option. I tripped across this option while working on a backflushing problem call with Phil G. @ Epicor, this sounds like something that would work for us.

Option 4: Logic provided below option description
1. Leave the Resource/Resource Group Backflush Warehouse & Bin's blank.
2. Confirm that all parts have a Primary Warehouse & Primary Bin properly configured.
3. Do NOT add/remove any Operations or Resources/Resource Groups, leave as is.
Here is why this may work:
Per the backflush Hierarchy publish on Page 9733MPS, if configured as above any parts related to an operation will backflush from that parts Primary Warehouse & Primary Bin, #2 below:

AMM Warehouse Backflush Hierarchy:

1. FROM THE RESOURCE GROUP (of the linked job operation) Backflush warehouse and bin - IF it exists and if a positive on hand quantity exists at this location if they are defined. (can also use a Resource backflush WH and Bin IF that is the scheduling requirement on an operation if no RG is related to the Operation)

2. USE THE PRIMARY BIN FOR THE PART IN THE ALLOCATED WAREHOUSE.
(JobMtl.WarehouseCo de) if it is defined. Allocated WH is the WH
selected in the job's material requirement sequence screen -- which defaults to the material part's primary WH from the part master).

3. If Primary bin is NOT defined for the part in the allocated warehouse back in the part master then take the first bin with a positive on hand quantity. If no qty exists in any bin, then .....

4. Use the first bin in the list of warehouses for this warehouse.

5. If for some reason no warehouse/bin can be determined then the part will not be back flushed.

For the vast majority of our parts this will work because the component parts are stored in the same warehouse as the product being produced, and we do not have a lot of warehouse bins, like maybe a half dozen(we do not employ the bin concept as an actual BIN). For instance, we are producing a Scaffold frame, well the raw materials are stored in SCAF/RAW and the locks and such are stored in SCAF/ASSEM. Well, when welding is welding a raw part, the Weld operation will backflush that raw part from that parts primary bin in SCAF, which is RAW. Later when the paintline is attaching locks to the painted frame, the locks and powder are stored in SCAF/ASSEM and that is their primary bin, so when the PAINT Op reports the parts will then backflush from..... the same location.

I think this will work, for exceptions, and we do have them, I can attempt employing, either my Option 2 or Rob's Option 3, depending. I think this approach to the solution will result in the least amount of re-engineering, which is a big deal here. My only concern is:
will the changes made to the resource/resource groups, automatically updated their referenced OPs? If so, then how do I get the OP's to then update the methods (I've noticed that if I make change to an OP it does not affect any already deployed methods). Maybe I should post this in another Post.

Please, provide feedback on my 4th Option, on any opinions, or anything I am not thinking about. AND what type of problems is there with updating Resources/Groups and getting those to update OPs and/or Methods?

--- In vantage@yahoogroups .com, "Rick Bird" <rbird@...> wrote:
>
> We have a problem here that maybe someone can enlighten us on how to
> deal with.
> Almost every machine (presses, drills, benders, etc) is used on jobs
> that manufacture parts for both of the Divisions of our business
> (scaffold & aerial work platforms). Right now we have one to one
> relationship between the resource and an operation, for instance:
> Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> tube for scaffolding, or larger square tube for work platforms. But
> the raw material that feeds the op (resource) is stocked in different
> Warehouse/Bin' s. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> AWP/RAW) Inventory is stocked per accounting, they need to know on
> hand inventory costs for each division. But the resource is only be
> configured to backflushed from one predetermined warehouse/bin. What
> is the best way to set up resources/operation s to fit this situation?
> Since this is not configured correctly, it is causing On Hand
> problems since depending on what division a job is manufacturing for
> the resource may backflush from the wrong bin (SCAF when it should be
> AWP). The option of NOT backflushing will not work because of the
> huge number of parts that would have to be manually issued, for which
> we do not have the man power for.
>
> Options we have come up with:
> 1. configuring 2 resource records for each resource (ex: AWP Saw &
> SCAF Saw), the only problem with that is that there is actually only
> ONE physical saw and then scheduling of the resource becomes a
> problem, since it sees that there are two resources available to
> schedule when there is actually only one.
>
> 2. Configure 1 resource, but place that resource in two resource
> groups, one for AWP and one for SCAF. Once again our concern is the
> same, will Vantage schedule the Resource Group in respect of there
> being only one Resource to schedule or not? Does the Resource Group
> backflush bin config override the Resource backflush bin?
>
> Neither really addresses the issue correctly.
> any have any ideas based on maybe what your company does?
>

system · March 3, 2009, 9:43am

We have a problem here that maybe someone can enlighten us on how to
deal with.
Almost every machine (presses, drills, benders, etc) is used on jobs
that manufacture parts for both of the Divisions of our business
(scaffold & aerial work platforms). Right now we have one to one
relationship between the resource and an operation, for instance:
Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
tube for scaffolding, or larger square tube for work platforms. But
the raw material that feeds the op (resource) is stocked in different
Warehouse/Bin's. (Scaffold = SCAF/RAW & Aerial Work Platforms =
AWP/RAW) Inventory is stocked per accounting, they need to know on
hand inventory costs for each division. But the resource is only be
configured to backflushed from one predetermined warehouse/bin. What
is the best way to set up resources/operations to fit this situation?
Since this is not configured correctly, it is causing On Hand
problems since depending on what division a job is manufacturing for
the resource may backflush from the wrong bin (SCAF when it should be
AWP). The option of NOT backflushing will not work because of the
huge number of parts that would have to be manually issued, for which
we do not have the man power for.

Options we have come up with:
1. configuring 2 resource records for each resource (ex: AWP Saw &
SCAF Saw), the only problem with that is that there is actually only
ONE physical saw and then scheduling of the resource becomes a
problem, since it sees that there are two resources available to
schedule when there is actually only one.

2. Configure 1 resource, but place that resource in two resource
groups, one for AWP and one for SCAF. Once again our concern is the
same, will Vantage schedule the Resource Group in respect of there
being only one Resource to schedule or not? Does the Resource Group
backflush bin config override the Resource backflush bin?

Neither really addresses the issue correctly.
any have any ideas based on maybe what your company does?

system · March 3, 2009, 11:53pm

Instead of focusing on the resources, look to putting the inventory into the same warehouse. Place different PARTCLASSes on the material for the different divisions. When they run stock status report, sort by PartClass to get the inventory level.

Now you can have many different materials in the same backflush warehouse - hope that helps.

--- In vantage@yahoogroups.com, "Rick Bird" <rbird@...> wrote:
>
> We have a problem here that maybe someone can enlighten us on how to
> deal with.
> Almost every machine (presses, drills, benders, etc) is used on jobs
> that manufacture parts for both of the Divisions of our business
> (scaffold & aerial work platforms). Right now we have one to one
> relationship between the resource and an operation, for instance:
> Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> tube for scaffolding, or larger square tube for work platforms. But
> the raw material that feeds the op (resource) is stocked in different
> Warehouse/Bin's. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> AWP/RAW) Inventory is stocked per accounting, they need to know on
> hand inventory costs for each division. But the resource is only be
> configured to backflushed from one predetermined warehouse/bin. What
> is the best way to set up resources/operations to fit this situation?
> Since this is not configured correctly, it is causing On Hand
> problems since depending on what division a job is manufacturing for
> the resource may backflush from the wrong bin (SCAF when it should be
> AWP). The option of NOT backflushing will not work because of the
> huge number of parts that would have to be manually issued, for which
> we do not have the man power for.
>
> Options we have come up with:
> 1. configuring 2 resource records for each resource (ex: AWP Saw &
> SCAF Saw), the only problem with that is that there is actually only
> ONE physical saw and then scheduling of the resource becomes a
> problem, since it sees that there are two resources available to
> schedule when there is actually only one.
>
> 2. Configure 1 resource, but place that resource in two resource
> groups, one for AWP and one for SCAF. Once again our concern is the
> same, will Vantage schedule the Resource Group in respect of there
> being only one Resource to schedule or not? Does the Resource Group
> backflush bin config override the Resource backflush bin?
>
> Neither really addresses the issue correctly.
> any have any ideas based on maybe what your company does?
>

system · March 4, 2009, 3:27am

brz_larson:

I'm not quite getting how ignoring the resource & making both Divisions share a warehouse - and I assume you also mean Bin as backflush is based upon the resource's (that the material is related to in the method via the OP) defined backflush whse/bin - resolves the Rick's issue in a way that would satisfy Accounting (assuming material is also kept separate for each Division.

Also, at least up to our version 405a, an apparent bug somewhere in the job data details and/or processing for backflushing 1st looks at the resource group's (that contains the scheduled resource) backflush whse/bin and, only if NOT left null, THEN looks to the actual resource's backflush whse/bin.

Also up to 405a, changing a resource's backflush whse/bin does not 'fix' existing methods... You actually have to recreate the OP from scratch to pull in the correct data (that definitely is NOT in any of the method related tables' data definitions - but would seem to be copied into the method at the time of creation).

If it does - Great! (and I'd sure like to understand it better!)

If it doesn't - you have 3rd resource based option (that we use and I know has worked from 404 through 405a).

Question Rick: Were you able to model your 2nd option (one resource that is under two resource groups)? My understanding is that a resource can only exist within one group.

3rd option: Keep your current single resource (which sounds finite based upon the concerns you expressed) - which is good as this is the basis of the 'trick' that makes this option work. Keep it finite with a calendar that truly represents the single saw capacity - but set your set your direct & burden (and quoting) cost rates to $0.00/hr.

Now create another resource group ("SAW2DIV"?) with 2 resources under it that also represent your SAW - in this case SCAF-SAW & AWP-SAW. Define the finite capacities of each of these resources to match your capacity of your original saw resource. These resources should be set up with your valid direct & burden (and quoting) cost rates.

Also set the new resource groups backflush whse/bin to one of your related whse/bins (either SCAF/SAW or AWP/SAW) and then set each resource's backflush whse/bin to the specific appropriate whse bin.

Now create two standard OPs: "SawSCAF" & "SawAWP".

"SawSCAF" will have resource SCAF-SAW as the primary detail & your original saw resource as the secondary detail.

"SawAWP" will have resource SCAF-AWP as the primary detail & your original saw resource as the secondary detail.

Change your jobs/methods to specifically call for either the appropriate specific new SawSCAF or SawAWP standard OP (and relink the appropriate materials to the OPs).

By having the primary scheduled SawSCAF OP resource as SCAF-SAW, materials will backflush from SCAF/SAW whse bin (defined for that resource) when the OP is reported complete.

By having the primary scheduled SawAWP OP resource as AWP-SAW, materials will backflush from AWP/SAW whse bin (defined for that resource) when the OP is reported complete.

By having your secondary scheduled OP resource (for both new standard OPs) as your single original finite resource, the scheduler will see THAT resource's capacity as the constraining capacity when attempting to scheduled multiple job-OPs into it.

You've now retained your single saw capacity but enabled backflushing from two different whse/bins... It all then becomes a matter of calling out the correct standard OP in the method/job details.

Caveat: I've never tried this trick with 3 potential capacity limiting resources (or resource groups) called out in a Std OP (and I wouldn't be surprised if that breaks the scheduler & you don't get the desired capacity contraint expected) - but for just 2, it works.

This trick works well when you have multiple machines available (potentially 24x7) in a department but a fixed labor pool to operate those only some of those machines within a shift.

Each person becomes a department labor resource - finite capacity - under a department resource group: This resource GROUP called as the secondary OP detail acts as the constraining capacity... The machine resources are the primary OP detail & can then simply control backflushing if you do it.

Hope that makes sense.

Rob

--- On Tue, 3/3/09, brz_larson <bl_larson@...> wrote:
From: brz_larson <bl_larson@...>
Subject: [Vantage] Re: One Resource, Two Warehouses
To: vantage@yahoogroups.com
Date: Tuesday, March 3, 2009, 11:53 PM

Instead of focusing on the resources, look to putting the inventory into the same warehouse. Place different PARTCLASSes on the material for the different divisions. When they run stock status report, sort by PartClass to get the inventory level.

Now you can have many different materials in the same backflush warehouse - hope that helps.

--- In vantage@yahoogroups .com, "Rick Bird" <rbird@...> wrote:

>

> We have a problem here that maybe someone can enlighten us on how to

> deal with.

> Almost every machine (presses, drills, benders, etc) is used on jobs

> that manufacture parts for both of the Divisions of our business

> (scaffold & aerial work platforms). Right now we have one to one

> relationship between the resource and an operation, for instance:

> Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut

> tube for scaffolding, or larger square tube for work platforms. But

> the raw material that feeds the op (resource) is stocked in different

> Warehouse/Bin' s. (Scaffold = SCAF/RAW & Aerial Work Platforms =

> AWP/RAW) Inventory is stocked per accounting, they need to know on

> hand inventory costs for each division. But the resource is only be

> configured to backflushed from one predetermined warehouse/bin. What

> is the best way to set up resources/operation s to fit this situation?

> Since this is not configured correctly, it is causing On Hand

> problems since depending on what division a job is manufacturing for

> the resource may backflush from the wrong bin (SCAF when it should be

> AWP). The option of NOT backflushing will not work because of the

> huge number of parts that would have to be manually issued, for which

> we do not have the man power for.

>

> Options we have come up with:

> 1. configuring 2 resource records for each resource (ex: AWP Saw &

> SCAF Saw), the only problem with that is that there is actually only

> ONE physical saw and then scheduling of the resource becomes a

> problem, since it sees that there are two resources available to

> schedule when there is actually only one.

>

> 2. Configure 1 resource, but place that resource in two resource

> groups, one for AWP and one for SCAF. Once again our concern is the

> same, will Vantage schedule the Resource Group in respect of there

> being only one Resource to schedule or not? Does the Resource Group

> backflush bin config override the Resource backflush bin?

>

> Neither really addresses the issue correctly.

> any have any ideas based on maybe what your company does?

>

system · March 4, 2009, 4:47pm

brz_larson:
Wow, that's a lot to think over.
I read it over, and I must say, I think that will work.
But I have this same question on call 1152298PSC with Epicor and while working through that, my tech discovered that the backflush logic is not being handled as published on Page 9733MPS (AMM Warehouse Backflush Hierarchy), so that needs fixed first before I can test it. (it's broken in 407 and probably 405). Test it and report it if you can!

But back to your suggestion, I think it genius and it should work for what we need to do. I will wrap my head around it and then test it and let you know.

Thanks for the quick response!

system · March 4, 2009, 5:46pm

The problem there is you double the inventory because with each part
class you have a Part ID No part can have more than one class.

For a 6" Dia 5.8"ID Steel tube, you would have two part ID's one for
each part class. Might as well put a suffix (or prefix) on the part ID
and use that as your identifier for the parts.

Charlie Smith

Smith Business Services / 2W Technologies LLC

www.vistaconsultant.com <http://www.vistaconsultant.com/> /
www.2WTech.com

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of brz_larson
Sent: Tuesday, March 03, 2009 11:53 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: One Resource, Two Warehouses

Instead of focusing on the resources, look to putting the inventory into
the same warehouse. Place different PARTCLASSes on the material for the
different divisions. When they run stock status report, sort by
PartClass to get the inventory level.

Now you can have many different materials in the same backflush
warehouse - hope that helps.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Rick Bird" <rbird@...> wrote:

>
> We have a problem here that maybe someone can enlighten us on how to
> deal with.
> Almost every machine (presses, drills, benders, etc) is used on jobs
> that manufacture parts for both of the Divisions of our business
> (scaffold & aerial work platforms). Right now we have one to one
> relationship between the resource and an operation, for instance:
> Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> tube for scaffolding, or larger square tube for work platforms. But
> the raw material that feeds the op (resource) is stocked in different
> Warehouse/Bin's. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> AWP/RAW) Inventory is stocked per accounting, they need to know on
> hand inventory costs for each division. But the resource is only be
> configured to backflushed from one predetermined warehouse/bin. What
> is the best way to set up resources/operations to fit this situation?
> Since this is not configured correctly, it is causing On Hand
> problems since depending on what division a job is manufacturing for
> the resource may backflush from the wrong bin (SCAF when it should be
> AWP). The option of NOT backflushing will not work because of the
> huge number of parts that would have to be manually issued, for which
> we do not have the man power for.
>
> Options we have come up with:
> 1. configuring 2 resource records for each resource (ex: AWP Saw &
> SCAF Saw), the only problem with that is that there is actually only
> ONE physical saw and then scheduling of the resource becomes a
> problem, since it sees that there are two resources available to
> schedule when there is actually only one.
>
> 2. Configure 1 resource, but place that resource in two resource
> groups, one for AWP and one for SCAF. Once again our concern is the
> same, will Vantage schedule the Resource Group in respect of there
> being only one Resource to schedule or not? Does the Resource Group
> backflush bin config override the Resource backflush bin?
>
> Neither really addresses the issue correctly.
> any have any ideas based on maybe what your company does?
>

[Non-text portions of this message have been removed]

system · March 5, 2009, 8:31am

Charlie,
What are your thoughts on Robert Brown's suggestion? I'm attempting to absorb and put it together in my mind. I'll need to test this out in our Pilot DB.
-Rick

--- In vantage@yahoogroups.com, "CharlieSmith" <CSmith@...> wrote:
>
> The problem there is you double the inventory because with each part
> class you have a Part ID No part can have more than one class.
>
> For a 6" Dia 5.8"ID Steel tube, you would have two part ID's one for
> each part class. Might as well put a suffix (or prefix) on the part ID
> and use that as your identifier for the parts.
>
>
>
> Charlie Smith
>
> Smith Business Services / 2W Technologies LLC
>
> www.vistaconsultant.com <http://www.vistaconsultant.com/> /
> www.2WTech.com
>
>
>
>
>
>
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of brz_larson
> Sent: Tuesday, March 03, 2009 11:53 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: One Resource, Two Warehouses
>
>
>
> Instead of focusing on the resources, look to putting the inventory into
> the same warehouse. Place different PARTCLASSes on the material for the
> different divisions. When they run stock status report, sort by
> PartClass to get the inventory level.
>
> Now you can have many different materials in the same backflush
> warehouse - hope that helps.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Rick Bird" <rbird@> wrote:
> >
> > We have a problem here that maybe someone can enlighten us on how to
> > deal with.
> > Almost every machine (presses, drills, benders, etc) is used on jobs
> > that manufacture parts for both of the Divisions of our business
> > (scaffold & aerial work platforms). Right now we have one to one
> > relationship between the resource and an operation, for instance:
> > Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> > tube for scaffolding, or larger square tube for work platforms. But
> > the raw material that feeds the op (resource) is stocked in different
> > Warehouse/Bin's. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> > AWP/RAW) Inventory is stocked per accounting, they need to know on
> > hand inventory costs for each division. But the resource is only be
> > configured to backflushed from one predetermined warehouse/bin. What
> > is the best way to set up resources/operations to fit this situation?
> > Since this is not configured correctly, it is causing On Hand
> > problems since depending on what division a job is manufacturing for
> > the resource may backflush from the wrong bin (SCAF when it should be
> > AWP). The option of NOT backflushing will not work because of the
> > huge number of parts that would have to be manually issued, for which
> > we do not have the man power for.
> >
> > Options we have come up with:
> > 1. configuring 2 resource records for each resource (ex: AWP Saw &
> > SCAF Saw), the only problem with that is that there is actually only
> > ONE physical saw and then scheduling of the resource becomes a
> > problem, since it sees that there are two resources available to
> > schedule when there is actually only one.
> >
> > 2. Configure 1 resource, but place that resource in two resource
> > groups, one for AWP and one for SCAF. Once again our concern is the
> > same, will Vantage schedule the Resource Group in respect of there
> > being only one Resource to schedule or not? Does the Resource Group
> > backflush bin config override the Resource backflush bin?
> >
> > Neither really addresses the issue correctly.
> > any have any ideas based on maybe what your company does?
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · March 5, 2009, 8:32am

Robert,
Thank you for your quick response. I am trying to put this together in my head and then I plan on testing it out in out pilot DB.

-Rick

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...> wrote:
>
>
> brz_larson:
>
> I'm not quite getting how ignoring the resource & making both Divisions share a warehouse - and I assume you also mean Bin as backflush is based upon the resource's (that the material is related to in the method via the OP) defined backflush whse/bin - resolves the Rick's issue in a way that would satisfy Accounting (assuming material is also kept separate for each Division.
>
> Also, at least up to our version 405a, an apparent bug somewhere in the job data details and/or processing for backflushing 1st looks at the resource group's (that contains the scheduled resource) backflush whse/bin and, only if NOT left null, THEN looks to the actual resource's backflush whse/bin.
>
> Also up to 405a, changing a resource's backflush whse/bin does not 'fix' existing methods... You actually have to recreate the OP from scratch to pull in the correct data (that definitely is NOT in any of the method related tables' data definitions - but would seem to be copied into the method at the time of creation).
>
> If it does - Great! (and I'd sure like to understand it better!)
>
> If it doesn't - you have 3rd resource based option (that we use and I know has worked from 404 through 405a).
>
> Question Rick: Were you able to model your 2nd option (one resource that is under two resource groups)? My understanding is that a resource can only exist within one group.
>
> 3rd option: Keep your current single resource (which sounds finite based upon the concerns you expressed) - which is good as this is the basis of the 'trick' that makes this option work. Keep it finite with a calendar that truly represents the single saw capacity - but set your set your direct & burden (and quoting) cost rates to $0.00/hr.
>
> Now create another resource group ("SAW2DIV"?) with 2 resources under it that also represent your SAW - in this case SCAF-SAW & AWP-SAW. Define the finite capacities of each of these resources to match your capacity of your original saw resource. These resources should be set up with your valid direct & burden (and quoting) cost rates.
>
> Also set the new resource groups backflush whse/bin to one of your related whse/bins (either SCAF/SAW or AWP/SAW) and then set each resource's backflush whse/bin to the specific appropriate whse bin.
>
> Now create two standard OPs: "SawSCAF" & "SawAWP".
>
> "SawSCAF" will have resource SCAF-SAW as the primary detail & your original saw resource as the secondary detail.
>
> "SawAWP" will have resource SCAF-AWP as the primary detail & your original saw resource as the secondary detail.
>
> Change your jobs/methods to specifically call for either the appropriate specific new SawSCAF or SawAWP standard OP (and relink the appropriate materials to the OPs).
>
> By having the primary scheduled SawSCAF OP resource as SCAF-SAW, materials will backflush from SCAF/SAW whse bin (defined for that resource) when the OP is reported complete.
>
> By having the primary scheduled SawAWP OP resource as AWP-SAW, materials will backflush from AWP/SAW whse bin (defined for that resource) when the OP is reported complete.
>
> By having your secondary scheduled OP resource (for both new standard OPs) as your single original finite resource, the scheduler will see THAT resource's capacity as the constraining capacity when attempting to scheduled multiple job-OPs into it.
>
> You've now retained your single saw capacity but enabled backflushing from two different whse/bins... It all then becomes a matter of calling out the correct standard OP in the method/job details.
>
> Caveat: I've never tried this trick with 3 potential capacity limiting resources (or resource groups) called out in a Std OP (and I wouldn't be surprised if that breaks the scheduler & you don't get the desired capacity contraint expected) - but for just 2, it works.
>
> This trick works well when you have multiple machines available (potentially 24x7) in a department but a fixed labor pool to operate those only some of those machines within a shift.
>
> Each person becomes a department labor resource - finite capacity - under a department resource group: This resource GROUP called as the secondary OP detail acts as the constraining capacity... The machine resources are the primary OP detail & can then simply control backflushing if you do it.
>
> Hope that makes sense.
>
> Rob
>
> --- On Tue, 3/3/09, brz_larson <bl_larson@...> wrote:
> From: brz_larson <bl_larson@...>
> Subject: [Vantage] Re: One Resource, Two Warehouses
> To: vantage@yahoogroups.com
> Date: Tuesday, March 3, 2009, 11:53 PM
>
>
> Instead of focusing on the resources, look to putting the inventory into the same warehouse. Place different PARTCLASSes on the material for the different divisions. When they run stock status report, sort by PartClass to get the inventory level.
>
> Now you can have many different materials in the same backflush warehouse - hope that helps.
>
>
>
> --- In vantage@yahoogroups .com, "Rick Bird" <rbird@> wrote:
>
> >
>
> > We have a problem here that maybe someone can enlighten us on how to
>
> > deal with.
>
> > Almost every machine (presses, drills, benders, etc) is used on jobs
>
> > that manufacture parts for both of the Divisions of our business
>
> > (scaffold & aerial work platforms). Right now we have one to one
>
> > relationship between the resource and an operation, for instance:
>
> > Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
>
> > tube for scaffolding, or larger square tube for work platforms. But
>
> > the raw material that feeds the op (resource) is stocked in different
>
> > Warehouse/Bin' s. (Scaffold = SCAF/RAW & Aerial Work Platforms =
>
> > AWP/RAW) Inventory is stocked per accounting, they need to know on
>
> > hand inventory costs for each division. But the resource is only be
>
> > configured to backflushed from one predetermined warehouse/bin. What
>
> > is the best way to set up resources/operation s to fit this situation?
>
> > Since this is not configured correctly, it is causing On Hand
>
> > problems since depending on what division a job is manufacturing for
>
> > the resource may backflush from the wrong bin (SCAF when it should be
>
> > AWP). The option of NOT backflushing will not work because of the
>
> > huge number of parts that would have to be manually issued, for which
>
> > we do not have the man power for.
>
> >
>
> > Options we have come up with:
>
> > 1. configuring 2 resource records for each resource (ex: AWP Saw &
>
> > SCAF Saw), the only problem with that is that there is actually only
>
> > ONE physical saw and then scheduling of the resource becomes a
>
> > problem, since it sees that there are two resources available to
>
> > schedule when there is actually only one.
>
> >
>
> > 2. Configure 1 resource, but place that resource in two resource
>
> > groups, one for AWP and one for SCAF. Once again our concern is the
>
> > same, will Vantage schedule the Resource Group in respect of there
>
> > being only one Resource to schedule or not? Does the Resource Group
>
> > backflush bin config override the Resource backflush bin?
>
> >
>
> > Neither really addresses the issue correctly.
>
> > any have any ideas based on maybe what your company does?
>
> >
>

system · March 5, 2009, 9:02am

What if you make two saw resources, each with half the capacity of the saw and make them both members of the saw resource group? The part class suggestion for material tracking should work also. It does not sound like the same material is being used for both scaffolding and work platforms correct?

----- Original Message -----
From: brz_larson
To: vantage@yahoogroups.com
Sent: Tuesday, March 03, 2009 10:53 PM
Subject: [Vantage] Re: One Resource, Two Warehouses

Instead of focusing on the resources, look to putting the inventory into the same warehouse. Place different PARTCLASSes on the material for the different divisions. When they run stock status report, sort by PartClass to get the inventory level.

Now you can have many different materials in the same backflush warehouse - hope that helps.

--- In vantage@yahoogroups.com, "Rick Bird" <rbird@...> wrote:
>
> We have a problem here that maybe someone can enlighten us on how to
> deal with.
> Almost every machine (presses, drills, benders, etc) is used on jobs
> that manufacture parts for both of the Divisions of our business
> (scaffold & aerial work platforms). Right now we have one to one
> relationship between the resource and an operation, for instance:
> Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> tube for scaffolding, or larger square tube for work platforms. But
> the raw material that feeds the op (resource) is stocked in different
> Warehouse/Bin's. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> AWP/RAW) Inventory is stocked per accounting, they need to know on
> hand inventory costs for each division. But the resource is only be
> configured to backflushed from one predetermined warehouse/bin. What
> is the best way to set up resources/operations to fit this situation?
> Since this is not configured correctly, it is causing On Hand
> problems since depending on what division a job is manufacturing for
> the resource may backflush from the wrong bin (SCAF when it should be
> AWP). The option of NOT backflushing will not work because of the
> huge number of parts that would have to be manually issued, for which
> we do not have the man power for.
>
> Options we have come up with:
> 1. configuring 2 resource records for each resource (ex: AWP Saw &
> SCAF Saw), the only problem with that is that there is actually only
> ONE physical saw and then scheduling of the resource becomes a
> problem, since it sees that there are two resources available to
> schedule when there is actually only one.
>
> 2. Configure 1 resource, but place that resource in two resource
> groups, one for AWP and one for SCAF. Once again our concern is the
> same, will Vantage schedule the Resource Group in respect of there
> being only one Resource to schedule or not? Does the Resource Group
> backflush bin config override the Resource backflush bin?
>
> Neither really addresses the issue correctly.
> any have any ideas based on maybe what your company does?
>

[Non-text portions of this message have been removed]

system · March 5, 2009, 9:06am

Greg,
To the best of my knowledge, no, the same material is not being used for both divisions. Although, it could happen (or maybe is), so that flexibility would be good to have.
-Rick

--- In vantage@yahoogroups.com, "gclauser" <gclauser@...> wrote:
>
> What if you make two saw resources, each with half the capacity of the saw and make them both members of the saw resource group? The part class suggestion for material tracking should work also. It does not sound like the same material is being used for both scaffolding and work platforms correct?
>
> ----- Original Message -----
> From: brz_larson
> To: vantage@yahoogroups.com
> Sent: Tuesday, March 03, 2009 10:53 PM
> Subject: [Vantage] Re: One Resource, Two Warehouses
>
>
> Instead of focusing on the resources, look to putting the inventory into the same warehouse. Place different PARTCLASSes on the material for the different divisions. When they run stock status report, sort by PartClass to get the inventory level.
>
> Now you can have many different materials in the same backflush warehouse - hope that helps.
>
> --- In vantage@yahoogroups.com, "Rick Bird" <rbird@> wrote:
> >
> > We have a problem here that maybe someone can enlighten us on how to
> > deal with.
> > Almost every machine (presses, drills, benders, etc) is used on jobs
> > that manufacture parts for both of the Divisions of our business
> > (scaffold & aerial work platforms). Right now we have one to one
> > relationship between the resource and an operation, for instance:
> > Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> > tube for scaffolding, or larger square tube for work platforms. But
> > the raw material that feeds the op (resource) is stocked in different
> > Warehouse/Bin's. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> > AWP/RAW) Inventory is stocked per accounting, they need to know on
> > hand inventory costs for each division. But the resource is only be
> > configured to backflushed from one predetermined warehouse/bin. What
> > is the best way to set up resources/operations to fit this situation?
> > Since this is not configured correctly, it is causing On Hand
> > problems since depending on what division a job is manufacturing for
> > the resource may backflush from the wrong bin (SCAF when it should be
> > AWP). The option of NOT backflushing will not work because of the
> > huge number of parts that would have to be manually issued, for which
> > we do not have the man power for.
> >
> > Options we have come up with:
> > 1. configuring 2 resource records for each resource (ex: AWP Saw &
> > SCAF Saw), the only problem with that is that there is actually only
> > ONE physical saw and then scheduling of the resource becomes a
> > problem, since it sees that there are two resources available to
> > schedule when there is actually only one.
> >
> > 2. Configure 1 resource, but place that resource in two resource
> > groups, one for AWP and one for SCAF. Once again our concern is the
> > same, will Vantage schedule the Resource Group in respect of there
> > being only one Resource to schedule or not? Does the Resource Group
> > backflush bin config override the Resource backflush bin?
> >
> > Neither really addresses the issue correctly.
> > any have any ideas based on maybe what your company does?
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · March 5, 2009, 9:30am

Rick,
Sometimes you can try to be so flexible you end up tying yourself into knots. If a material is only sometimes used in the other division it might be better to issue it rather than backflush it on those rare occasions.
Greg

----- Original Message -----
From: Rick Bird
To: vantage@yahoogroups.com
Sent: Thursday, March 05, 2009 8:06 AM
Subject: [Vantage] Re: One Resource, Two Warehouses

Greg,
To the best of my knowledge, no, the same material is not being used for both divisions. Although, it could happen (or maybe is), so that flexibility would be good to have.
-Rick
--- In vantage@yahoogroups.com, "gclauser" <gclauser@...> wrote:
>
> What if you make two saw resources, each with half the capacity of the saw and make them both members of the saw resource group? The part class suggestion for material tracking should work also. It does not sound like the same material is being used for both scaffolding and work platforms correct?
>
> ----- Original Message -----
> From: brz_larson
> To: vantage@yahoogroups.com
> Sent: Tuesday, March 03, 2009 10:53 PM
> Subject: [Vantage] Re: One Resource, Two Warehouses
>
>
> Instead of focusing on the resources, look to putting the inventory into the same warehouse. Place different PARTCLASSes on the material for the different divisions. When they run stock status report, sort by PartClass to get the inventory level.
>
> Now you can have many different materials in the same backflush warehouse - hope that helps.
>
> --- In vantage@yahoogroups.com, "Rick Bird" <rbird@> wrote:
> >
> > We have a problem here that maybe someone can enlighten us on how to
> > deal with.
> > Almost every machine (presses, drills, benders, etc) is used on jobs
> > that manufacture parts for both of the Divisions of our business
> > (scaffold & aerial work platforms). Right now we have one to one
> > relationship between the resource and an operation, for instance:
> > Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> > tube for scaffolding, or larger square tube for work platforms. But
> > the raw material that feeds the op (resource) is stocked in different
> > Warehouse/Bin's. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> > AWP/RAW) Inventory is stocked per accounting, they need to know on
> > hand inventory costs for each division. But the resource is only be
> > configured to backflushed from one predetermined warehouse/bin. What
> > is the best way to set up resources/operations to fit this situation?
> > Since this is not configured correctly, it is causing On Hand
> > problems since depending on what division a job is manufacturing for
> > the resource may backflush from the wrong bin (SCAF when it should be
> > AWP). The option of NOT backflushing will not work because of the
> > huge number of parts that would have to be manually issued, for which
> > we do not have the man power for.
> >
> > Options we have come up with:
> > 1. configuring 2 resource records for each resource (ex: AWP Saw &
> > SCAF Saw), the only problem with that is that there is actually only
> > ONE physical saw and then scheduling of the resource becomes a
> > problem, since it sees that there are two resources available to
> > schedule when there is actually only one.
> >
> > 2. Configure 1 resource, but place that resource in two resource
> > groups, one for AWP and one for SCAF. Once again our concern is the
> > same, will Vantage schedule the Resource Group in respect of there
> > being only one Resource to schedule or not? Does the Resource Group
> > backflush bin config override the Resource backflush bin?
> >
> > Neither really addresses the issue correctly.
> > any have any ideas based on maybe what your company does?
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

system · March 5, 2009, 12:45pm

Clarification: Modeling your saw capacity using two resource groups:

1. One with a single 8 hr finite capacity zero cost resource that will be the SECONDARY OP detail - and controls overall capacity limit on the saw to 8 loaded hrs.

2. One with two resources each also with 8 hrs capacity (one reflecting scaffold division work, the other reflecting platform division work), labor rates entered to cost the OPs as you desire & each with it's own backflush whse Bin (one for Scaffolding, one for Platforms). One or the other of these resources is the PRIMARY OP detail so platform versus scaffold work backlfush materials from desired whse bins (and labor costs accumulate in the job WIP).

You don't have to (nor SHOULD you) set each saw to half a days capacity (as your work mix probably never perfectly matches a 50-50 split on any given day).

It is the single common resource used as the secondary OP detail that limits total load to you finite 8 hrs per day (if that is your capacity) - and then allows any mix of scaffold & platformk load totally 8 hrs to be loaded daily.

This is a pretty common capacity modelling method that works on most finite scheduling systems when better native methods don't exist (as on Vantage).

Rob

--- On Thu, 3/5/09, gclauser <gclauser@...> wrote:

From: gclauser <gclauser@...>
Subject: Re: [Vantage] Re: One Resource, Two Warehouses
To: vantage@yahoogroups.com
Date: Thursday, March 5, 2009, 9:00 AM

What if you make two saw resources, each with half the capacity of the saw and make them both members of the saw resource group? The part class suggestion for material tracking should work also. It does not sound like the same material is being used for both scaffolding and work platforms correct?

----- Original Message -----
From: brz_larson
To: vantage@yahoogroups .com
Sent: Tuesday, March 03, 2009 10:53 PM
Subject: [Vantage] Re: One Resource, Two Warehouses

Instead of focusing on the resources, look to putting the inventory into the same warehouse. Place different PARTCLASSes on the material for the different divisions. When they run stock status report, sort by PartClass to get the inventory level.

Now you can have many different materials in the same backflush warehouse - hope that helps.

--- In vantage@yahoogroups .com, "Rick Bird" <rbird@...> wrote:
>
> We have a problem here that maybe someone can enlighten us on how to
> deal with.
> Almost every machine (presses, drills, benders, etc) is used on jobs
> that manufacture parts for both of the Divisions of our business
> (scaffold & aerial work platforms). Right now we have one to one
> relationship between the resource and an operation, for instance:
> Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> tube for scaffolding, or larger square tube for work platforms. But
> the raw material that feeds the op (resource) is stocked in different
> Warehouse/Bin' s. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> AWP/RAW) Inventory is stocked per accounting, they need to know on
> hand inventory costs for each division. But the resource is only be
> configured to backflushed from one predetermined warehouse/bin. What
> is the best way to set up resources/operation s to fit this situation?
> Since this is not configured correctly, it is causing On Hand
> problems since depending on what division a job is manufacturing for
> the resource may backflush from the wrong bin (SCAF when it should be
> AWP). The option of NOT backflushing will not work because of the
> huge number of parts that would have to be manually issued, for which
> we do not have the man power for.
>
> Options we have come up with:
> 1. configuring 2 resource records for each resource (ex: AWP Saw &
> SCAF Saw), the only problem with that is that there is actually only
> ONE physical saw and then scheduling of the resource becomes a
> problem, since it sees that there are two resources available to
> schedule when there is actually only one.
>
> 2. Configure 1 resource, but place that resource in two resource
> groups, one for AWP and one for SCAF. Once again our concern is the
> same, will Vantage schedule the Resource Group in respect of there
> being only one Resource to schedule or not? Does the Resource Group
> backflush bin config override the Resource backflush bin?
>
> Neither really addresses the issue correctly.
> any have any ideas based on maybe what your company does?
>

[Non-text portions of this message have been removed]

system · March 5, 2009, 12:47pm

You'd have that flexibility using the multiple resource capacity modelling technique.

(We do it now.)

Rob

--- On Thu, 3/5/09, Rick Bird <rbird@...> wrote:

From: Rick Bird <rbird@...>
Subject: [Vantage] Re: One Resource, Two Warehouses
To: vantage@yahoogroups.com
Date: Thursday, March 5, 2009, 9:06 AM

Greg,
To the best of my knowledge, no, the same material is not being used for both divisions. Although, it could happen (or maybe is), so that flexibility would be good to have.
-Rick
--- In vantage@yahoogroups .com, "gclauser" <gclauser@.. .> wrote:
>
> What if you make two saw resources, each with half the capacity of the saw and make them both members of the saw resource group? The part class suggestion for material tracking should work also. It does not sound like the same material is being used for both scaffolding and work platforms correct?
>
> ----- Original Message -----
> From: brz_larson
> To: vantage@yahoogroups .com
> Sent: Tuesday, March 03, 2009 10:53 PM
> Subject: [Vantage] Re: One Resource, Two Warehouses
>
>
> Instead of focusing on the resources, look to putting the inventory into the same warehouse. Place different PARTCLASSes on the material for the different divisions. When they run stock status report, sort by PartClass to get the inventory level.
>
> Now you can have many different materials in the same backflush warehouse - hope that helps.
>
> --- In vantage@yahoogroups .com, "Rick Bird" <rbird@> wrote:
> >
> > We have a problem here that maybe someone can enlighten us on how to
> > deal with.
> > Almost every machine (presses, drills, benders, etc) is used on jobs
> > that manufacture parts for both of the Divisions of our business
> > (scaffold & aerial work platforms). Right now we have one to one
> > relationship between the resource and an operation, for instance:
> > Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> > tube for scaffolding, or larger square tube for work platforms. But
> > the raw material that feeds the op (resource) is stocked in different
> > Warehouse/Bin' s. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> > AWP/RAW) Inventory is stocked per accounting, they need to know on
> > hand inventory costs for each division. But the resource is only be
> > configured to backflushed from one predetermined warehouse/bin. What
> > is the best way to set up resources/operation s to fit this situation?
> > Since this is not configured correctly, it is causing On Hand
> > problems since depending on what division a job is manufacturing for
> > the resource may backflush from the wrong bin (SCAF when it should be
> > AWP). The option of NOT backflushing will not work because of the
> > huge number of parts that would have to be manually issued, for which
> > we do not have the man power for.
> >
> > Options we have come up with:
> > 1. configuring 2 resource records for each resource (ex: AWP Saw &
> > SCAF Saw), the only problem with that is that there is actually only
> > ONE physical saw and then scheduling of the resource becomes a
> > problem, since it sees that there are two resources available to
> > schedule when there is actually only one.
> >
> > 2. Configure 1 resource, but place that resource in two resource
> > groups, one for AWP and one for SCAF. Once again our concern is the
> > same, will Vantage schedule the Resource Group in respect of there
> > being only one Resource to schedule or not? Does the Resource Group
> > backflush bin config override the Resource backflush bin?
> >
> > Neither really addresses the issue correctly.
> > any have any ideas based on maybe what your company does?
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · March 5, 2009, 7:06pm

It's doable. I yield to Rob as he is a production modeling genius. :0

I can see the technique and I would just have to get my head around the
scheduling processes for v8.03.

I would reengineer a couple of parts in your testbed and try it. See how
it manages the resources. Once you are satisfied, there will probably be
a bunch of re-engineering that has to occur.

Nice job Rob.

Charlie Smith

Smith Business Services / 2W Technologies LLC

www.vistaconsultant.com <http://www.vistaconsultant.com/> /
www.2WTech.com

________________________________

Clarification: Modeling your saw capacity using two resource groups:

1. One with a single 8 hr finite capacity zero cost resource that will
be the SECONDARY OP detail - and controls overall capacity limit on the
saw to 8 loaded hrs.

2. One with two resources each also with 8 hrs capacity (one reflecting
scaffold division work, the other reflecting platform division work),
labor rates entered to cost the OPs as you desire & each with it's own
backflush whse Bin (one for Scaffolding, one for Platforms). One or the
other of these resources is the PRIMARY OP detail so platform versus
scaffold work backlfush materials from desired whse bins (and labor
costs accumulate in the job WIP).

You don't have to (nor SHOULD you) set each saw to half a days capacity
(as your work mix probably never perfectly matches a 50-50 split on any
given day).

It is the single common resource used as the secondary OP detail that
limits total load to you finite 8 hrs per day (if that is your capacity)
- and then allows any mix of scaffold & platform load totally 8 hrs to
be loaded daily.

This is a pretty common capacity modeling method that works on most
finite scheduling systems when better native methods don't exist (as on
Vantage).

Rob

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Rick Bird
Sent: Thursday, March 05, 2009 8:32 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: One Resource, Two Warehouses

Charlie,
What are your thoughts on Robert Brown's suggestion? I'm attempting to
absorb and put it together in my mind. I'll need to test this out in our
Pilot DB.
-Rick

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"CharlieSmith" <CSmith@...> wrote:

>
> The problem there is you double the inventory because with each part
> class you have a Part ID No part can have more than one class.
>
> For a 6" Dia 5.8"ID Steel tube, you would have two part ID's one for
> each part class. Might as well put a suffix (or prefix) on the part ID
> and use that as your identifier for the parts.
>
>
>
> Charlie Smith
>
> Smith Business Services / 2W Technologies LLC
>
> www.vistaconsultant.com <http://www.vistaconsultant.com/> /
> www.2WTech.com
>
>
>
>
>
>
>
>
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf

> Of brz_larson
> Sent: Tuesday, March 03, 2009 11:53 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: One Resource, Two Warehouses
>
>
>
> Instead of focusing on the resources, look to putting the inventory

into

> the same warehouse. Place different PARTCLASSes on the material for

the

> different divisions. When they run stock status report, sort by
> PartClass to get the inventory level.
>
> Now you can have many different materials in the same backflush
> warehouse - hope that helps.
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com> ,

> "Rick Bird" <rbird@> wrote:
> >
> > We have a problem here that maybe someone can enlighten us on how to
> > deal with.
> > Almost every machine (presses, drills, benders, etc) is used on jobs
> > that manufacture parts for both of the Divisions of our business
> > (scaffold & aerial work platforms). Right now we have one to one
> > relationship between the resource and an operation, for instance:
> > Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> > tube for scaffolding, or larger square tube for work platforms. But
> > the raw material that feeds the op (resource) is stocked in

different

> > Warehouse/Bin's. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> > AWP/RAW) Inventory is stocked per accounting, they need to know on
> > hand inventory costs for each division. But the resource is only be
> > configured to backflushed from one predetermined warehouse/bin. What
> > is the best way to set up resources/operations to fit this

situation?

> > Since this is not configured correctly, it is causing On Hand
> > problems since depending on what division a job is manufacturing for
> > the resource may backflush from the wrong bin (SCAF when it should

be

> > AWP). The option of NOT backflushing will not work because of the
> > huge number of parts that would have to be manually issued, for

which

> > we do not have the man power for.
> >
> > Options we have come up with:
> > 1. configuring 2 resource records for each resource (ex: AWP Saw &
> > SCAF Saw), the only problem with that is that there is actually only
> > ONE physical saw and then scheduling of the resource becomes a
> > problem, since it sees that there are two resources available to
> > schedule when there is actually only one.
> >
> > 2. Configure 1 resource, but place that resource in two resource
> > groups, one for AWP and one for SCAF. Once again our concern is the
> > same, will Vantage schedule the Resource Group in respect of there
> > being only one Resource to schedule or not? Does the Resource Group
> > backflush bin config override the Resource backflush bin?
> >
> > Neither really addresses the issue correctly.
> > any have any ideas based on maybe what your company does?
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

system · March 6, 2009, 10:13am

I beleive I have found a possible 4th option. I tripped across this option while working on a backflushing problem call with Phil G. @ Epicor, this sounds like something that would work for us.

Option 4: Logic provided below option description
1. Leave the Resource/Resource Group Backflush Warehouse & Bin's blank.
2. Confirm that all parts have a Primary Warehouse & Primary Bin properly configured.
3. Do NOT add/remove any Operations or Resources/Resource Groups, leave as is.
Here is why this may work:
Per the backflush Hierarchy publish on Page 9733MPS, if configured as above any parts related to an operation will backflush from that parts Primary Warehouse & Primary Bin, #2 below:

AMM Warehouse Backflush Hierarchy:

1. FROM THE RESOURCE GROUP (of the linked job operation) Backflush warehouse and bin - IF it exists and if a positive on hand quantity exists at this location if they are defined. (can also use a Resource backflush WH and Bin IF that is the scheduling requirement on an operation if no RG is related to the Operation)

2. USE THE PRIMARY BIN FOR THE PART IN THE ALLOCATED WAREHOUSE.
(JobMtl.WarehouseCode) if it is defined. Allocated WH is the WH
selected in the job's material requirement sequence screen -- which defaults to the material part's primary WH from the part master).

3. If Primary bin is NOT defined for the part in the allocated warehouse back in the part master then take the first bin with a positive on hand quantity. If no qty exists in any bin, then .....

4. Use the first bin in the list of warehouses for this warehouse.

5. If for some reason no warehouse/bin can be determined then the part will not be back flushed.

For the vast majority of our parts this will work because the component parts are stored in the same warehouse as the product being produced, and we do not have a lot of warehouse bins, like maybe a half dozen(we do not employ the bin concept as an actual BIN). For instance, we are producing a Scaffold frame, well the raw materials are stored in SCAF/RAW and the locks and such are stored in SCAF/ASSEM. Well, when welding is welding a raw part, the Weld operation will backflush that raw part from that parts primary bin in SCAF, which is RAW. Later when the paintline is attaching locks to the painted frame, the locks and powder are stored in SCAF/ASSEM and that is their primary bin, so when the PAINT Op reports the parts will then backflush from..... the same location.

I think this will work, for exceptions, and we do have them, I can attempt employing, either my Option 2 or Rob's Option 3, depending. I think this approach to the solution will result in the least amount of re-engineering, which is a big deal here. My only concern is:
will the changes made to the resource/resource groups, automatically updated their referenced OPs? If so, then how do I get the OP's to then update the methods (I've noticed that if I make change to an OP it does not affect any already deployed methods). Maybe I should post this in another Post.

Please, provide feedback on my 4th Option, on any opinions, or anything I am not thinking about. AND what type of problems is there with updating Resources/Groups and getting those to update OPs and/or Methods?

--- In vantage@yahoogroups.com, "Rick Bird" <rbird@...> wrote:
>
> We have a problem here that maybe someone can enlighten us on how to
> deal with.
> Almost every machine (presses, drills, benders, etc) is used on jobs
> that manufacture parts for both of the Divisions of our business
> (scaffold & aerial work platforms). Right now we have one to one
> relationship between the resource and an operation, for instance:
> Resource: 524 (a saw) --> OP "Saw." Well this saw may be used to cut
> tube for scaffolding, or larger square tube for work platforms. But
> the raw material that feeds the op (resource) is stocked in different
> Warehouse/Bin's. (Scaffold = SCAF/RAW & Aerial Work Platforms =
> AWP/RAW) Inventory is stocked per accounting, they need to know on
> hand inventory costs for each division. But the resource is only be
> configured to backflushed from one predetermined warehouse/bin. What
> is the best way to set up resources/operations to fit this situation?
> Since this is not configured correctly, it is causing On Hand
> problems since depending on what division a job is manufacturing for
> the resource may backflush from the wrong bin (SCAF when it should be
> AWP). The option of NOT backflushing will not work because of the
> huge number of parts that would have to be manually issued, for which
> we do not have the man power for.
>
> Options we have come up with:
> 1. configuring 2 resource records for each resource (ex: AWP Saw &
> SCAF Saw), the only problem with that is that there is actually only
> ONE physical saw and then scheduling of the resource becomes a
> problem, since it sees that there are two resources available to
> schedule when there is actually only one.
>
> 2. Configure 1 resource, but place that resource in two resource
> groups, one for AWP and one for SCAF. Once again our concern is the
> same, will Vantage schedule the Resource Group in respect of there
> being only one Resource to schedule or not? Does the Resource Group
> backflush bin config override the Resource backflush bin?
>
> Neither really addresses the issue correctly.
> any have any ideas based on maybe what your company does?
>