仓库管理系统外文翻译英文文献.doc

warehouse management systems (wms).the evolution of warehouse management systems (wms) is very similar to that of many other software solutions. initially a system to control movement and storage of materials within a warehouse, the role of wms is expanding to including light manufacturing, transportation management, order management, and complete accounting systems. to use the grandfather of operations-related software, mrp, as a comparison, material requirements planning (mrp) started as a system for planning raw material requirements in a manufacturing environment. soon mrp evolved into manufacturing resource planning (mrpii), which took the basic mrp system and added scheduling and capacity planning logic. eventually mrpii evolved into enterprise resource planning (erp), incorporating all the mrpii functionality with full financials and customer and vendor management functionality. now, whether wms evolving into a warehouse-focused erp system is a good thing or not is up to debate. what is clear is that the expansion of the overlap in functionality between warehouse management systems, enterprise resource planning, distribution requirements planning, transportation management systems, supply chain planning, advanced planning and scheduling, and manufacturing execution systems will only increase the level of confusion among companies looking for software solutions for their operations. even though wms continues to gain added functionality, the initial core functionality of a wms has not really changed. the primary purpose of a wms is to control the movement and storage of materials within an operation and process the associated transactions. directed picking, directed replenishment, and directed put away are the key to wms. the detailed setup and processing within a wms can vary significantly from one software vendor to another, however the basic logic will use a combination of item, location, quantity, unit of measure, and order information to determine where to stock, where to pick, and in what sequence to perform these operations. at a bare minimum, a wms should:have a flexible location system.utilize user-defined parameters to direct warehouse tasks and use live documents to execute these tasks.have some built-in level of integration with data collection devices.do you really need wms?not every warehouse needs a wms. certainly any warehouse could benefit from some of the functionality but is the benefit great enough to justify the initial and ongoing costs associated with wms? warehouse management systems are big, complex, data intensive, applications. they tend to require a lot of initial setup, a lot of system resources to run, and a lot of ongoing data management to continue to run. thats right, you need to manage your warehouse management system. often times, large operations will end up creating a new is department with the sole responsibility of managing the wms. the claims: wms will reduce inventory! wms will reduce labor costs! wms will increase storage capacity! wms will increase customer service! wms will increase inventory accuracy! the reality: the implementation of a wms along with automated data collection will likely give you increases in accuracy, reduction in labor costs (provided the labor required to maintain the system is less than the labor saved on the warehouse floor), and a greater ability to service the customer by reducing cycle times. expectations of inventory reduction and increased storage capacity are less likely. while increased accuracy and efficiencies in the receiving process may reduce the level of safety stock required, the impact of this reduction will likely be negligible in comparison to overall inventory levels. the predominant factors that control inventory levels are lot sizing, lead times, and demand variability. it is unlikely that a wms will have a significant impact on any of these factors. and while a wms certainly provides the tools for more organized storage which may result in increased storage capacity, this improvement will be relative to just how sloppy your pre-wms processes were. beyond labor efficiencies, the determining factors in deciding to implement a wms tend to be more often associated with the need to do something to service your customers that your current system does not support (or does not support well) such as first-in-first-out, cross-docking, automated pick replenishment, wave picking, lot tracking, yard management, automated data collection, automated material handling equipment, etc.setup the setup requirements of wms can be extensive. the characteristics of each item and location must be maintained either at the detail level or by grouping similar items and locations into categories. an example of item characteristics at the detail level would include exact dimensions and weight of each item in each unit of measure the item is stocked (each, cases, pallets, etc) as well as information such as whether it can be mixed with other items in a location, whether it is rack able, max stack height, max quantity per location, hazard classifications, finished goods or raw material, fast versus slow mover, etc. although some operations will need to set up each item this way, most operations will benefit by creating groups of similar products. for example, if you are a distributor of music cds you would create groups for single cds, and double cds, maintaining the detailed dimension and weight information at the group level and only needing to attach the group code to each item. you would likely need to maintain detailed information on special items such as boxed sets or cds in special packaging. you would also create groups for the different types of locations within your warehouse. an example would be to create three different groups (p1, p2, p3) for the three different sized forward picking locations you use for your cd picking. you then set up the quantity of single cds that will fit in a p1, p2, and p3 location, quantity of double cds that fit in a p1, p2, p3 location etc. you would likely also be setting up case quantities, and pallet quantities of each cd group and quantities of cases and pallets per each reserve storage location group. if this sounds simple, it iswell sort of. in reality most operations have a much more diverse product mix and will require much more system setup. and setting up the physical characteristics of the product and locations is only part of the picture. you have set up enough so that the system knows where a product can fit and how many will fit in that location. you now need to set up the information needed to let the system decide exactly which location to pick from, replenish from/to, and put away to, and in what sequence these events should occur (remember wms is all about “directed” movement). you do this by assigning specific logic to the various combinations of item/order/quantity/location information that will occur. below i have listed some of the logic used in determining actual locations and sequences. location sequence. this is the simplest logic; you simply define a flow through your warehouse and assign a sequence number to each location. in order picking this is used to sequence your picks to flow through the warehouse, in put away the logic would look for the first location in the sequence in which the product would fit. zone logic. by breaking down your storage locations into zones you can direct picking, put away, or replenishment to or from specific areas of your warehouse. since zone logic only designates an area, you will need to combine this with some other type of logic to determine exact location within the zone. fixed location. logic uses predetermined fixed locations per item in picking, put away, and replenishment. fixed locations are most often used as the primary picking location in piece pick and case-pick operations, however, they can also be used for secondary storage. random location. since computers cannot be truly random (nor would you want them to be) the term random location is a little misleading. random locations generally refer to areas where products are not stored in designated fixed locations. like zone logic, you will need some additional logic to determine exact locations. first-in-first-out (fifo). directs picking from the oldest inventory first. last-in-first-out (lifo). opposite of fifo. i didnt think there were any real applications for this logic until a visitor to my site sent an email describing their operation that distributes perishable goods domestically and overseas. they use lifo for their overseas customers (because of longer in-transit times) and fifo for their domestic customers. pick-to-clear. logic directs picking to the locations with the smallest quantities on hand. this logic is great for space utilization. reserved locations. this is used when you want to predetermine specific locations to put away to or pick from. an application for reserved locations would be cross-docking, where you may specify certain quantities of an inbound shipment be moved to specific outbound staging locations or directly to an awaiting outbound trailer. maximize cube. cube logic is found in most wms systems however it is seldom used. cube logic basically uses unit dimensions to calculate cube (cubic inches per unit) and then compares this to the cube capacity of the location to determine how much will fit. now if the units are capable of being stacked into the location in a manner that fills every cubic inch of space in the location, cube logic will work. since this rarely happens in the real world, cube logic tends to be impractical. consolidate. looks to see if there is already a location with the same product stored in it with available capacity. may also create additional moves to consolidate like product stored in multiple locations. lot sequence. used for picking or replenishment, this will use the lot number or lot date to determine locations to pick from or replenish from. its very common to combine multiple logic methods to determine the best location. for example you may chose to use pick-to-clear logic within first-in-first-out logic when there are multiple locations with the same receipt date. you also may change the logic based upon current workload. during busy periods you may chose logic that optimizes productivity while during slower periods you switch to logic that optimizes space utilization. other functionality/considerationswave picking/batch picking/zone picking. support for various picking methods varies from one system to another. in high-volume fulfillment operations, picking logic can be a critical factor in wms selection. see my article on order picking for more info on these methods. task interleaving. task interleaving describes functionality that mixes dissimilar tasks such as picking and put away to obtain maximum productivity. used primarily in full-pallet-load operations, task interleaving will direct a lift truck operator to put away a pallet on his/her way to the next pick. in large warehouses this can greatly reduce travel time, not only increasing productivity, but also reducing wear on the lift trucks and saving on energy costs by reducing lift truck fuel consumption. task interleaving is also used with cycle counting programs to coordinate a cycle count with a picking or put away task. integration with automated material handling equipment. if you are planning on using automated material handling equipment such as carousels, asrs units, agns, pick-to-light systems, or separation systems, youll want to consider this during the software selection process. since these types of automation are very expensive and are usually a core component of your warehouse, you may find that the equipment will drive the selection of the wms. as with automated data collection, you should be working closely with the equipment manufacturers during the software selection process. advanced shipment notifications (asn). if your vendors are capable of sending advanced shipment notifications (preferably electronically) and attaching compliance labels to the shipments you will want to make sure that the wms can use this to automate your receiving process. in addition, if you have requirements to provide asns for customers, you will also want to verify this functionality. yard management. yard management describes the function of managing the contents (inventory) of trailers parked outside the warehouse, or the empty trailers themselves. yard management is generally associated with cross docking operations and may include the management of both inbound and outbound trailers. labor tracking/capacity planning. some wms systems provide functionality related to labor reporting and capacity planning. anyone that has worked in manufacturing should be familiar with this type of logic. basically, you set up standard labor hours and machine (usually lift trucks) hours per task and set the available labor and machine hours per shift. the wms system will use this info to determine capacity and load. manufacturing has been using capacity planning for decades with mixed results. the need to factor in efficiency and utilization to determine rated capacity is an example of the shortcomings of this process. not that im necessarily against capacity planning in warehousing, i just think most operations dont 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 isnt there yet. ideally youll 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 dont see this as a unilateral move of wms from an add-on 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 add-on functionality will match the functionality of best-of-breed applications available separately. if warehousing/distribution is your core business function and you dont 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 tipsoutside of the standard “dont underestimate”, “thoroughly test”, “train, train, train” implementation tips that apply to any business software installation ,its important to 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 dont 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 competitive. its 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. 仓库管理系统（ wms ）仓库管理系统（ wms ）的演变与许多其他软件解决方案是非常相似的。最初的系统用来控制物料在仓库内的流动和贮存，仓库的作用正在延伸到包括轻型制造业，交通运输管理，订单管理，和完整的会计制度中。利用与先前的业务有关的软件，制造资源计划，作为一个比较，材料需求计划（ mrp ）开始作为一个规划要求，原材料的生产环境的系统。 物料需求计划很快演变成以mrp系统，补充调度和容量规划为基础的逻辑制造资源计划（ mrpii系统）。最终mrpii系统演变成企业资源规划（ erp ），吸收所有的mrpii系统的功能包括充分的财务与客户和供应商管理功能。现在，无论仓库管理系统演变成一个以仓库为中心的erp系统是一件好事或不可达的辩论。清楚的是，在仓库管理系统，企业资源规划，布局规划要求，交通运输管理系统，供应链计划，高级计划与排程，以及制造执行系统之间扩大重叠功能性只会增加那些寻找软件解决方案业务的公司混乱水平。 尽管仓库继续获得额外的功能，最初的仓库管理系统的核心功能还没有真正改变。其主要目的是控制管理系统在工艺操作相关联的交易中的流动和材料储存。定向采摘，定向补充，定向收集是仓库的关键。从一个软件供应商到另一个在一个管理系统中详细的安装和处理可以有一个很大的差别，但是其基本逻辑将使用相结合的项目，地点，数量，度量单位，并以收集信息以确定在哪里储存，在哪里挑选，以及以何种顺序执行这些操作。 一 最低限度，一个仓库管理系统应采取下列措施 有一个灵活的定位系统。 利用用户定义的参数，指导仓库任务和使用live文件来执行这些任务。 有一些内置的一体化和数据收集设备结合体。 您是否真的需要仓库管理系统？ 并非每一个仓库需要一个仓库管理系统。当然，任何仓库可受益于其中一些功能，但这些受益是否足以证明管理系统最初的和正在进行的相关费用是正确的？仓库管理系统是大的，复杂的，数据密集型的应用。他们往往需要大量的初始安装，很多系统资源的运行，很多正在进行的数据管理为继续运行。没错，你需要“管理”你的仓库“管理”制度。一般情况下，大规模的行动最终将建立一个新的is部门用来唯一负责管理仓库管理系统。 二 声明1) 仓库管理系统将减少库存！2) 仓库管理系统将减少劳动力成本!3) 仓库管理系统将增加存储容量！ 4) 仓库管理系统将提高客户服务！5) 仓库管理系统将增加库存的准确性 ！ 三 现实 实施一个仓库管理系统用来自动的数据收集将可能使你的准确性增加，减少劳动力成本（提供需要维持系统的劳动力少于物品保存在仓库楼需要的劳动力）和更好地来服务客户以降低周期。预期库存减少和增加存储容量的可能性较小。虽然在接收过程中增加了准确性和效率可能降低库存安全水平，但这种降低产生的影响与整体库存水平相比可以忽略不计。控制库存水平批量最主要的因素是多种尺寸，交货时间和需求的变化，仓库管理系统将对任何因素有重大影响是不可能。而且同时仓库管理系统确实的为更多的有组织的存储提供工具，因为这种存储可能会导致更多的