【正文】 ple of the shortings of this process. Not that I’m necessarily against capacity planning in warehousing, I just think most operations don’t really need it and can avoid the disappointment of trying to make it work. I am, however, a big advocate of labor tracking for individual productivity measurement. Most WMS maintain enough data to create productivity reporting. Since productivity is measured differently from one operation to another you can assume you will have to do some minor modifications here (usually in the form of custom reporting). Integration with existing accounting/ERP systems. Unless the WMS vendor has already created a specific interface with your accounting/ERP system (such as those provided by an approved business partner) you can expect to spend some significant programming dollars here. While we are all hoping that integration issues will be magically resolved someday by a standardized interface, we isn’t there yet. Ideally you’ll want an integrator that has already integrated the WMS you chose with the business software you are using. Since this is not always possible you at least want an integrator that is very familiar with one of the systems. WMS + everything else = ? As I mentioned at the beginning of this article, a lot of other modules are being added to WMS packages. These would include full financials, light manufacturing, transportation management, purchasing, and sales order management. I don’t see this as a unilateral move of WMS from an addon module to a core system, but rather an optional approach that has applications in specific industries such as 3PLs. Using ERP systems as a point of reference, it is unlikely that this addon functionality will match the functionality of bestofbreed applications available separately. If warehousing/distribution is your core business function and you don’t want to have to deal with the integration issues of incorporating separate financials, order processing, etc. you may find these WMS based business systems are a good fit. Implementation Tips Outside of the standard “don’t underestimate”, “thoroughly test”, “train, train, train” implementation tips that apply to any business software installation ,it’s important to 7 emphasize that WMS are very data dependent and restrictive by design. That is, you need to have all of the various data elements in place for the system to function properly. And, when they are in place, you must operate within the set parameters. When implementing a WMS, you are adding an additional layer of technology onto your system. And with each layer of technology there is additional overhead and additional sources of potential problems. Now don’t take this as a condemnation of Warehouse Management Systems. Coming from a warehousing background I definitely appreciate the functionality WMS have to offer, and, in many warehouses, this functionality is essential to their ability to serve their customers and remain petitive. It’s just important to note that every solution has its downsides and having a good understanding of the potential implications will allow managers to make better decisions related to the levels of technology that best suits their unique environment. 倉庫管理系統(tǒng)（ WMS ） 倉庫管理系統(tǒng)（ WMS ） 的 演變 與 許多其他軟件解決方案是非常相似的 。 最初的系統(tǒng)用 來控制 物料在倉庫內的流動和貯存 ，倉庫的作用正 在延伸到 包括輕型制造業(yè)，交通運輸管理，訂單管理，和完整的會計制度 中 。利用 與先前的 業(yè)務有關的軟件，制造資源計劃，作為一個比較，材料需求計劃（ MRP ）開始作為 一個 規(guī)劃要求，原材料的生產環(huán)境 的系統(tǒng)。 物料需求計劃很快演變成 以 MRP 系統(tǒng) ， 補充調度和容量規(guī)劃 為基礎 的邏輯制造資源計劃（ MRPII 系統(tǒng)）。最終 MRPII 系統(tǒng)演變成企業(yè)資源規(guī)劃（ ERP ） ，吸收 所有的 MRPII系統(tǒng)的功能 包括 充分的財務 與 客戶和供應商管理功能 。 現(xiàn)在，無論倉庫管理系統(tǒng)演變成一個 以 倉庫為中心的 ERP系統(tǒng)是一件好事或不可達的辯論。清楚的是， 在 倉庫管理系統(tǒng)，企業(yè)資源規(guī)劃，布局規(guī)劃要求，交通運輸管理系統(tǒng)，供應鏈計劃，高級計劃與排程，以及制造執(zhí)行系統(tǒng) 之間 擴大重疊功能性只會增加 那些 尋找軟件解決方案業(yè)務 的 公司混亂水 平 。 盡管倉庫繼續(xù)獲得額外的功能，最初的倉庫管理系統(tǒng) 的 核心功能還沒有真正改變 。其主要目的是控制管理系統(tǒng) 在 工藝操作 相 關聯(lián) 的 交易 中的 流動和材料 儲存 。 定向 采摘， 定向補充， 定向收集是倉庫的關鍵 。從一個 軟件供應商到另一個 在一個 管理系統(tǒng) 中 詳細的安裝和處理可以 有 一個很大的差別，但是其基本邏輯將使用相結合的項目，地點，數量，度量單位，并以 收集 信息以確定 在哪里儲存 ，在 哪 里挑選，以及以何種順序執(zhí)行這些操作。 8 一 最低限度 ， 一個倉庫管理系統(tǒng)應采取下列措施 有一個靈活的定位系統(tǒng)。 利用用戶定義的參數， 指導 倉庫任務和使用 Live 文件來執(zhí)行這些任務。 有一些內置的一體化 和 數據收集設備 結合體 。 您是否真的需要 倉庫管理系統(tǒng) ？ 并非每一個倉庫需要一個倉庫 管理系統(tǒng) 。當然，任何倉庫可受益于 其中 一些功能，但這些 受益 是否 足以證明管理系統(tǒng)最初的和正在進行的相關費用 是正確的 ？倉庫管理系統(tǒng)是大的，復雜的，數據密集型的應用 。他們往往需要大量的初始安裝，很多系統(tǒng)資源的運行，很多正在進行的數據管理 為 繼續(xù)運行。沒錯，你需要 “ 管理 ” 你的倉庫 “ 管理 ” 制度 。一般情況下，大規(guī)模的行動最終將建立一個新的 IS 部門 用來 唯一負責管理倉庫管理系統(tǒng)。 二 聲明 1) 倉庫管理系統(tǒng)將減少庫存！ 2) 倉庫管理系統(tǒng)將減少勞動力成本 ! 3) 倉庫管理系統(tǒng)將增加存儲容量！ 4) 倉庫管理系統(tǒng)將提高客戶服務！ 5) 倉庫管理系統(tǒng)將增加 庫存的準確性 ！