Dynamics GP Warehouse Management System Implementation

Sep 29
07:41

2010

Andrew Karasev

Andrew Karasev

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

We assume that at this point you are committed to Microsoft Dynamics GP Corporate ERP platform and this application is already in production. Now you are ready to the second phase, where you plan to organize your Supply Chain Management, Picking and Packing, Shipping and Receiving, Inventory Restocking, Cycle Counts on the warehouse floor and possibly custom barcoding based business procedures around Great Plains Dynamics GP

mediaimage
In this small publication we will review the options to consider in Warehouse Management System for Dynamics GP selection,Dynamics GP Warehouse Management System Implementation Articles implementation steps, optimal strategy for version upgrade, data integration, WMS and SCM reporting.  In Supply Chain Management theory WMS (the abbreviation for Warehouse Management System) is considered as central part (or at least as one of the “key parts” in SCM definitions, more geared toward production and just in time parts delivery).  This is why we do recommend you to make your philosophy and detail oriented homework in selecting the right WMS for your organization.  This paper is created primarily for IT managers, and if you are company owner or CEO, we recommend you to share this publication with your IT personnel, especially when you need clarification on some technology oriented definitions:
1. WMS review on the level of abstraction.  If you call to specific Warehouse Management Vendor, these people will begin to realize the strategy to sell your own WMS solution, and prior to that point, you need to understand the philosophy (it should arm you with the ability to compare and judge).  If you would imagine yourself in the shoes of WMS vendor – probably the most efficient WMS software winning market strategy would be the creation of the completely self-sufficient external standalone Warehouse management System with integration modules or connectors to major ERP applications (Axapta, Great Plains, Navision, Solomon, Oracle Financials, Accpac, SAP R/3 or Business One, etc.).  This strategy should enable the way of selling your WMS solution to the variety of customers and it doesn’t restrict you to the subset of ERP customers with just one Corporate ERP application.  Now, let’s try to speculate on putting yourself into WMS end customer shoes.  Here your concerns are likely to be about cost/reliability optimization. External WMS approach is definitely great option, however this direction suggests you to pay for complete or partial Distribution business logic in software licenses to the WMS vendor, and to your displeasure you already paid for similar logic in Dynamics GP Distribution modules licensing.  If you would like the idea to pay only once and capitalize on Dynamics GP Distribution modules, you should understand the concept of WMS extensions for Great Plains Dynamics, working out of GP databases and sharing the same tables, documents and master records
2. Warehouse Management System specification preparation phase.  Here you need to be satisfied with the proposed solution, prepared by your Dynamics GP Partner or Consultant.  Business Processes mapping for the WMS is typically centered around such procedures as Sales Order Fulfillment (in Dynamics GP SOP Sales Transaction Form), Inventory Replenishment (in GP POP Purchase Receipt screen), Inventory Transfer, Adjustment and Physical Count (in Dynamics GP you have exactly the same forms by their names)
3. Dynamics GP version concerns.  WMS implementation project is often comparable or even surpassing in its budget the original Great Plains software license cost and consulting hours.  Considering that fact, we do recommend you to be on the current or at least supported (directly by Microsoft Business Solutions technical support, as we are writing these lines in September 2010, the versions supported by MBS are Dynamics GP 2010/11.0, 10.0, 9.0) version.  We are happy to support your old Great Plains version, but we do not recommend you to consider legacy GP version as the base for Warehouse Management System implementation and integration with GP.  If you are on Great Plains 8.0, 7.5, 7.0, 6.0, 5.5, 5.0, 4.0 (including Great Plains Select on Pervasive SQL 2000/Btrieve or Ctree), or Great Plains Accounting for DOS, Windows and Macintosh 9.5, 9.2, 9.1 and earlier – we recommend you to consider version update all the way through Dynamics GP 10.0 or 2010
4. Placing order online and Dynamics GP WMS.  Here you are diving into B2B eCommerce strategy for Microsoft Dynamics GP, where placed orders are transferred to the warehouse for automatic picking and packing.  Ecommerce module for Great Plains is another “black horse”, where you do not want to make immediate decision and rather take your time for additional homework
5. Placing orders via EDI (Electronic Document Interchange) protocol.  This method is very similar to direct B2B or B2C ecommerce originated documents.  You might expect some hard selling techniques from Dynamics GP EDI ISV partners, suggesting purchase often overpriced EDI solution for Great Plains.  If your EDI channel is based on one or two simple protocols, we recommend you to program EDI integration in-house
6. Barcode scanners to consider.  Here you are in the hands of your WMS and Barcoding budget.  Barcode scanner should be compliant to Windows Mobile OS or at least to Text mode.  To be reasonably in price/reliability median, we recommend you to consider Symbol PDT 3000 Portable Data Terminal Series, or scanner with compatible features and processing power.  From the scanner info sheet: "Symbol Technologies' PDT 3000 Portable Data Terminals answer the need for hand-held data terminals that are high on features and performance, but low in price. Designed for efficient, economical data collection, the PDT 3000 Series packs the power of a 16-bit, DOS-based PC into a small, lightweight data terminal that goes anywhere to get the job done. Feature for feature, dollar for dollar, no other terminal surpasses the PDT 3000 Series for overall value. Its durable ergonomic design, standard DOS operating system, and flexible options put the PDT 3000 in a class by itself…"  This scanner cost is around $500.  Well of course there is drawback and for this scanner it is text only user interface, whoever we do believe that Warehouse Management Worker barcode scanning training cost and learning curve period would be comparable to the option to do that with the scanner with graphical user interface (and Windows CE operating system).  The savings could be significant if you plan to deploy WMS for hundreds of warehouses7. To request further support, please call us 1-866-528-0577, help@albaspectrum.com.  By the nature of our service we are available for WMS implementation USA, Canada nationwide.  Local service is available in Western Michigan: St. Joseph, Kalamazoo, Grand Rapids, Muskegon, Holland, New Buffalo; in Chicagoland, North Western Indiana, Southern California (Los Angeles, San Diego, Irvine, Orange County), Houston and Dallas areas of Texas