| | 3 | |
| | 4 | !GnuMims is designed around the concept of one installation per site. Therefore the recommended configuration is one complete gnuMims installation per site. The reasoning for this is detailed bellow. Smaller sites and auxiliary sites can be supported in a single installation but for anything more a separate gnuMims installation |
| | 5 | |
| | 6 | == Inventory == |
| | 7 | |
| | 8 | Multiple storage locations are supported but an inventory item may only be stored in one location. |
| | 9 | |
| | 10 | An early gnuMims data model actually had the ability to store an inventory item in multiple locations but this was simply way too complicated and confusing to the end user. For example a technician wanting to use an inventory item has to be aware of which bin in which store on which site he is actually booking the item out from. This results in far to many human input errors so the model and interface were simplified. |
| | 11 | |
| | 12 | Further more storing an inventory item in multiple locations on a single site is generally bad for inventory levels and the opposite of inventory consolidation which is much preferred. |
| | 13 | |
| | 14 | To store an item in more than one location a separate inventory item with a unique name must be created along with all its own attributes. In this way items may be stored in depo's, auxiliary sites and remote stores. The re-order points etc may then be set appropriately for each. The inventory items may also be linked via the alternate item field. |
| | 15 | |
| | 16 | == Conclusion == |
| | 17 | |
| | 18 | With a little data admin a complete and separate gnuMims installation per site is the best configuration. |
