***SPAM*** Best Practice For Setting Up Warehouses

Phil,

I agree with Jose. Keep in mind how you want to do cycle counting too. We
had one big warehouse, then split it up into multiple warehouses (raw stock,
Sub-assy stock, Finished goods stock, Floor stock, etc.) Now I can create
different cycle count rules for each. They are all physically separate
areas from each other.

Todd

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Jose Gomez
Sent: Thursday, May 30, 2013 1:49 PM
To: Vantage
Subject: ***SPAM*** Re: [Vantage] Best Practice For Setting Up Warehouses in
E9

I've always found best practice is that setup which best matches your
physical setup.


*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*


On Thu, May 30, 2013 at 1:46 PM, Philip <philco_71@...> wrote:

> **
>
>
> I am inquiring as to what is considered to be Best practice when
> setting up warehouses. Is there an advantage to setting up multiple
> warehouses in a single plant Vs setting Up 1 warehouse per plant with
multiple bins?
>
>
>


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



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
I am inquiring as to what is considered to be Best practice when setting up warehouses. Is there an advantage to setting up multiple warehouses in a single plant Vs setting Up 1 warehouse per plant with multiple bins?
I've always found best practice is that setup which best matches your
physical setup.


*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*


On Thu, May 30, 2013 at 1:46 PM, Philip <philco_71@...> wrote:

> **
>
>
> I am inquiring as to what is considered to be Best practice when setting
> up warehouses. Is there an advantage to setting up multiple warehouses in a
> single plant Vs setting Up 1 warehouse per plant with multiple bins?
>
>
>


[Non-text portions of this message have been removed]
multiple warehouses allow better granularity and control (without forcing manual selection of parts) when you routinely do cycle counting.
if you do a lot of backflushing, think it through as a resource group/resource to which backflush enabled material is linked will only backflush from the whse bin spec'd for the resource (so don't OVER complicate it and effectively box yourself out of backflushing effectively).
always good to make the system model reflect your 'real' model (so it is intuitiveand understandable by users) - but make sure that physical model really makes sense (current and anticipated future state of biz) and isn't just a (less than appropriate) legacy 'because we always did it this way' paradigm.
whse related config options that can be set at company level are worth looking at to set up as unique whse's (like receive defaults, etc.,).
remember that demand links (make to stock jobs receive to whse & job material requirements issue from/demand from whse's) are brought into job based on what you define as primary whse (and in some processes, primary bins for primary whse or any whse in general) for each part - so look carefully that you aren't overcomplicating (and go through constant thrashing of people in different areas of business changing primary to make THEIR apps for their processes default to what they desire at expense of other areas... That's where seeing what your version supports as company defaults comes in to get best of all worlds possible (and supplanting behavior with BPMs where needed to give consistency to biz process execution in the remaining areas where one setting that is optimal is NOT optimal for something else driven by it)
TEST, TEST, TEST and try and get as close to ideal from the start as possible (as once transactions occur through what may prove later to be bad decision whse's, you can't delete those whse's).
Â
We started out with TOO MANYÂ whses &Â bins, flip flopped to too few, and finally have reached a happy medium (not a painless transition).
Â
WIP movement is handled through whse bins as well adn, in retrospect, our use of 'real' (for inventory) whse bins for WIP is still a source of confusion to many to this day (even after nearly 5 yrs). Doing it again, I'd make WIP whse bins exclusive (and intuitively coded/named as such) to avoid such confusion.
Â
Also consider if you expect to use kanban processing as it can influence how you set things up... Same goes for 'offsite' whse's (say at a service vendor's facility so you and your planners have visibility to what is at their site (and you can even consider backflushing to extend that further)- rather than have inventory 'hiding' in the black hole of WIP.
Â
It seems like a simple aspect of the system but, in retrospect, is one of the more important ones to make use of the system a success (and simple - with as few customizations/BPMs/SC workflows as possible).
Â
I'd like to be able to give you very specific recommendations but it is one of those areas (much like capacity modeling through resource group/resource/capability set up & how you use them in methods of manufacture) that can be quite different inorder to be ideal for different companies (although fundamentals building blocks are obvously common... It's how and what you put together with them).
Â
Rob Brown
Versa Products


>________________________________
>From: Philip <philco_71@...>
>To: vantage@yahoogroups.com
>Sent: Thursday, May 30, 2013 1:46 PM
>Subject: [Vantage] Best Practice For Setting Up Warehouses in E9
>

>I am inquiring as to what is considered to be Best practice when setting up warehouses. Is there an advantage to setting up multiple warehouses in a single plant Vs setting Up 1 warehouse per plant with multiple bins?
>
>
>

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