仓库管理系统外文翻译本科毕业论文

1、Warehouse Management Systems (WMS )The evoluti on of warehouse man ageme nt 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 manu facturi ng, tra

2、n sportati on man ageme nt, order man ageme nt, 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 pla nning raw material requireme nts in a manu facturi ng en vir onment.Soon MRPe

3、volved into manufacturing resource planning (MRPII), which took the basic MRP system and added scheduli ng and capacity pla nning logic. Eve ntually MRPII evolved into enterprise resource planning (ERP), incorporating all the MRPII functionality with full finan cials and customer and ven dor man age

4、me nt fun ctio nality.Now,whether WMS evo Iving in to a warehouse-focused ERP system is a good thi ng 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, Tr

5、ansportation Management Systems, Supply Chain Planning, Advaneed Planning and Scheduling, and Manufacturing Execution Systems will only in crease the level of con fusi on among compa nies look ing for software soluti ons for their operati ons.Even though WMS continues to gain added functionality, th

6、e initial core functionality of a WMS has not really changed. The primary purpose of a WMS is to con trol the moveme nt and storage of materials within an operati on and process the associated transactions. Directed picking, directed replenishment, and directed put away are the key to WMS. The detai

7、led setup and processing within a WMS can vary sig nifica ntly from one software ven dor to ano ther, however the basic logic will use a comb in ati on of item, locati on, qua ntity, unit of measure, and order information to determine where to stock, where to pick, and in what sequence to perform th

8、ese operati ons.At a bare minimum, a WMS should:Have a flexible locatio n system.Utilize user-defi ned parameters to direct warehouse tasks and use live docume nts to execute these tasks.Have some built-in level of integration with data collection devices.Do You Really Need WMS?Not every warehouse n

9、 eeds a WMS. Certa inly any warehouse could ben efit from some of the fun ctio nality but is the ben efit great eno ugh to justify the in itial and ongoing costs associated with WMS? Warehouse Management Systems are big, complex, data intensive, applications. They tend to require a lot of initial se

10、tup, a lot of system resources to run, and a lot of ongoing data man ageme nt to con ti nue to run. That s right, you need to manage your wehrouse management system. Often times, large operations will end up creating a new IS department with the sole resp on sibility of managing the WMS.The Reality:

11、The implementation of a WMS along with automated data collection will likely give you in creases in accuracy, reduct ion in labor costs (provided the labor required to main tai n the system is less tha n the labor saved on the warehouse floor), and a greater ability to service the customer by reduci

12、ng cycle times. Expectations of inven tory reducti on and in creased storage capacity are less likely. While in creased accuracy and efficiencies in the receiving process may reduce the level of safety stock required, the impact of this reduct ion will likely be n egligible in comparis on to overall

13、 inven tory levels. The predo minant factors that con trol inven tory levels are lot siz in g, lead times, and dema nd variability. It is un likely that a WMS will have a sig nifica nt impact on any of these factors. And while a WMS certa inly provides the tools for more orga ni zed storage which ma

14、y result in in creased storage capacity, this improveme nt 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 y

15、our curre nt 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 han dli ng equipme nt, etc.SetupThe setup requireme nts of WMS can be ex

16、te nsive. 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

17、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

18、operati ons will n eed to set up each item this way, most operatio ns will ben efit by creati ng 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 gro

19、up 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 cre

20、ate three different groups (P1, P2, P3) for the three different sized forward pick ing locati ons you use for your CD pick ing. You the n set up the qua ntity of sin gle 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 als

21、o be setting up case quantities, and pallet quantities of each CD group and quantities of cases and pallets per each reserve storage locati on 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

22、sett ing up the physical characteristics of the product and locations is only part of the picture. You have set up eno ugh 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 loc

23、ation to pick from, replenish from/to, and put away to, and in what seque nee these eve nts should occur (remember WMS is all about “ directed ” movemeYt)u do this by assigning specific logic to the various comb in ati ons of item/order/qua ntity/locatio n in formatio n that will occur.Below I have

24、listed some of the logic used in determining actual locations and seque nces.Location Sequence This is the simplest logic; you simply define a flow through your warehouse and assig n a seque nee nu mber to each locati on. In order pick ing this is used to seque nee your picks to flow through the war

25、ehouse, 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 desig nat

26、es an area, you will n eed to comb ine this with some other type of logic to determ ine exact locati on 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 pie

27、ce pick and case-pick operations, however, they can also be used for sec on dary 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 gen erally refer to areas where products are not stored in

28、 desig nated fixed locati ons. Like zone logic, you will n eed some additi on al logic to determ ine exact locati ons.First-in-first-out (FIFO). Directs picking from the oldest inventory first.Last-in-first-out (LIFO). Opposite of FIFO. I did nt thi nk there were any real applications for this logic

29、 until a visitor to my site sent an email describing their operati on that distributes perishable goods domestically and overseas. They use LIFOfor their overseas customers (because of Ion ger in-tran sit times) and FIFO for their domestic customers.Pick-to-clear Logic directs picking to the locatio

30、ns with the smallest quantities on hand. This logic is great for space utilizatio n.Reserved Locations This is used when you want to predetermine specific locati ons to put away to or pick from. An applicati on for reserved locatio ns would be cross-dock ing, where you may specify certa in qua ntiti

31、es of an inbound shipme nt 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 in ches per un it) and the n comp

32、ares this to the cube capacity of the locati on 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 i

33、mpractical.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

34、 date to determine locations to pick from or replenish from.It very com mon to comb ine multiple logic methods to determ ine 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

35、may cha nge the logic based upon curre nt workload.During busy periodsyou may chose logic that optimizes productivity while during slower periods you switch to logic that optimizes space utilizati on.Other Functionality/ConsiderationsWave Picking/Batch Picking/Zone PickingS upport for various pick i

36、ng methods varies from one system to another. In high-volume fulfillment operations, pick ing logic can be a critical factor in WMS selecti on. See my article on Order Pick ing for more info on these methods.Task Interleaving Task interleaving describes functionality that mixes dissimilar tasks such

37、 as pick ing and put away to obta in 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 n ext pick. In large warehouses this can greatly reduce travel time, not only increasing productivi

38、ty, but also reducing wear on the lift trucks and sav ing on en ergy costs by reduc ing lift truck fuel consumption. Task interleaving is also used with cycle counting programs to coordi nate a cycle count with a pick ing or put away task.Integration with Automated Material Handling Equipment. If yo

39、u arepla nning on using automated material han dli ng equipme nt such as carousels, ASRS units, AGNS, pick-to-ght systems, or separation systems, you ll want to consider thisduring the software selection process. Since these types of automation are very expe nsive and are usually a core comp onent o

40、f your warehouse, you may find that the equipme nt will drive the selecti on of the WMS. As with automated data collecti on, you should be work ing closely with the equipme nt manu facturers duri ng the software select ion process.Advanced Shipment Notifications (AS N)If your ven dors are capable of

41、 sending adva need shipme nt no tificatio ns (preferably electr oni cally) and attach ing compliance labels to the shipments you will want to make sure that the WMS can use this to automate your recei ving process. In additi on, if you have requireme nts to provide ASNs for customers, you will also

42、want to verify this functionality.Yard Management Yard management describes the function of managing the contents (inven tory) of trailers parked outside the warehouse, or the empty trailers themselves. Yard man ageme nt is gen erally associated with cross dock ing operati ons and may in clude the m

43、an ageme nt of both inbound and outbo und 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

44、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 determ ine capacity and load. Manu facturi ng has bee n using capacity pla nning for decades with mixed results. The need to factor in efficiency and utiliza

45、tion to determine rated capacity is an example of the shortcomings of this process. Not that I mecessarily against capacity planning in warehousing, I just think most operations don t really need it andavoid the disappointment of trying to make it work. I am, however, a big advocate of labor track i

46、ng for in dividual productivity measureme nt. Most WMS mai ntai n eno ugh data to create productivity report ing. Since productivity is measured differently from one operation to another you can assume you will have to do some minor modificatio ns here (usually in the form of custom report in g).Int

47、egration with existingaccounting/ERPfeystems Uni ess the WMS ven dor has already created a specific in terface with your acco untin g/ERP system (such as those provided by an approved bus in ess part ner) you can expect to spe nd some significant programming dollars here. While we are all hoping tha

48、t integration issues will be magically resolved someday by a standardized interfice, we isn t there yet. Ideally you want an integrator that has already integrated the WMS you chose with the bus in ess software you are using. Si nce this is not always possible you at least want an integrator that is

49、 very familiar with one of the systems.WMS + everything else = ? As I men ti oned at the beg inning 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 d

50、on t see this as a unilateral move of WMS from an addbn module to a core system, but rather an opti onal approach that has applicatio ns in specific industries such as 3PLs. Using ERPsystems as a point of reference, it is unlikely that this add-on functionality will match the functionality of best-o

51、f-breed applicati ons available separately. If warehous in g/distributi on is your core bus in ess function and you don twant to have to deal with the integration issues of incorporating separate financials, order processing, etc. you may find these WMS based bus in ess systems are a good fit.仓库管理系统

52、（WMS ）仓库管理系统（WMS ）的演变与许多其他软件解决方案是非常相似的。最初的系统用来控制物料在仓库内的流动和贮存，仓库的作用正在延伸到包括轻 型制造业，交通运输管理，订单管理，和完整的会计制度中。利用与先前的业务 有关的软件，制造资源计划，作为一个比较，材料需求计划（MRP ）开始作为一个规划要求，原材料的生产环境的系统。 物料需求计划很快演变成以 MRP系 统，补充调度和容量规划为基础的逻辑制造资源计划 （MRPII系统）。最终MRPII 系统演变成企业资源规划（ERP ），吸收所有的MRPII系统的功能包括充分的财 务与客户和供应商管理功能。现在，无论仓库管理系统演变成一个以仓库为

53、中心 的ERP系统是一件好事或不可达的辩论。 清楚的是，在仓库管理系统，企业资源 规划，布局规划要求，交通运输管理系统，供应链计划，高级计划与排程，以及 制造执行系统之间扩大重叠功能性只会增加那些寻找软件解决方案业务的公司 混乱水平。尽管仓库继续获得额外的功能，最初的仓库管理系统的核心功能还没有真正 改变。其主要目的是控制管理系统在工艺操作相关联的交易中的流动和材料储 存。定向采摘，定向补充，定向收集是仓库的关键。从一个软件供应商到另一个 在一个管理系统中详细的安装和处理可以有一个很大的差别，但是其基本逻辑将使用相结合的项目，地点，数量，度量单位，并以收集信息以确定在哪里储存， 在哪里挑选，以

54、及以何种顺序执行这些操作。一最低限度，一个仓库管理系统应采取下列措施有一个灵活的定位系统。利用用户定义的参数，指导仓库任务和使用 Live文件来执行这些任务。有一些内置的一体化和数据收集设备结合体。您是否真的需要仓库管理系统？并非每一个仓库需要一个仓库管理系统。 当然，任何仓库可受益于其中一些 功能，但这些受益是否足以证明管理系统最初的和正在进行的相关费用是正确 的？仓库管理系统是大的，复杂的，数据密集型的应用。他们往往需要大量的初 始安装，很多系统资源的运行，很多正在进行的数据管理为继续运行。没错，你 需要管理”你的仓库管理”制度。一般情况下，大规模的行动最终将建立一个新的IS部门用来唯一负

55、责管理仓库管理系统。二现实实施一个仓库管理系统用来自动的数据收集将可能使你的准确性增加，减少劳动力成本（提供需要维持系统的劳动力少于物品保存在仓库楼需要的劳动力） 和更好地来服务客户以降低周期。预期库存减少和增加存储容量的可能性较小。 虽然在接收过程中增加了准确性和效率可能降低库存安全水平，但这种降低产生的影响与整体库存水平相比可以忽略不计。控制库存水平批量最主要的因素是多 种尺寸，交货时间和需求的变化，仓库管理系统将对任何因素有重大影响是不可 能。而且同时仓库管理系统确实的为更多的有组织的存储提供工具，因为这种存储可能会导致更多的存储容量，相对于这种改善您之前的仓库管理系统是多么草 率啊。除

56、了劳动效率，决定实施仓库管理系统的决定因素，往往与一些能满足您 的客户的需求有更多关联，比如您目前的系统不支持（或不太支持）像先进先出， 交叉对接，自动挑选补充，波采摘，多种跟踪，停车场管理，自动数据采集，自 动材料处理设备等。三设置仓库管理系统的设置需求是广泛的，每个项目和地点都必须保持在详细或分 组类似项目和地点分类。一个例子，项目详细程度的特点将包括确切尺寸和重量， 每个项目在每个单位的项目储备（项目，案件，托盘等），以及信息，如是否可 以与其他物品混在一个位置，无论是的最高层次，最大堆叠高度，最高量的位置， 危险性分类，半成品或原材料，快与慢动，等。尽管一些行动将需要用这种方式 设立每

57、个项目，但大多数业务将有利于创造群体的类似产品。例如，如果你是一个音乐CD分销商，您将创建集团单一 CD和双张CD，保持详细的尺寸和重量 的资料在组一级，只需要对每个项目附上组代码。您可能会需要对特殊物品保持 详细的资料，如盒装套或 CD的特别包装。您也可以为地域的不同类型在您的仓 库里创造群组。一个例子是，为您用于 CD采摘的三种不同大小前瞻性采摘地点 建立3个不同群体（小一，二，三）。然后，您可以建立单一的光盘数量，将适 合P1，P2和P3的位置，多种双张CD适合在小一，二，小三的位置等。您可能 还设立案件的数量，每个CD组光盘数量，货箱的数量和光盘的每个后备存储位置 组。如果这听起来很简

58、单，但在现实中很多业务有更多元化的产品组合，将需要更多的系统设置。而且建立产品的物理特性和产品的位置只是蓝图的部分。你设定的使系统知道产品可以适合哪里并且多少产品将满足这个地方已经足够了。您现在需要建立必要的信息，以让系统决定从哪些位置选择，补充，并采集，并在 这些事件应该出现这些序列中（记得仓库管理就是指示”流动）。你分配具体逻辑的的做法使各种组合项目/订单/数量/位置信息将出现。下面我列出一些用于确定实际位置和序列的逻辑位置顺序。这是最简单的逻辑；您只需确定流经你的仓库和为每一个地点分 配序列编号。为了挑选这是把您选择的在流经的仓库排序， 在采集逻辑将寻求在第一位置的顺序适合的产品。区逻辑。由于把你的储存地点分到区，您可以直接采摘，收集，或补充或 特定地区的仓库。自区逻辑唯一指定的一个地区，则需要再加上一些其他类型的 逻辑，以确定确切位置在禁区内。固定的位置。逻辑使用预先确定的固定地点，每一项目中分拣，采集 ，和 补充。固定地点是一块采摘挑选和个案选择的行动最常用的首要位置， 但是，它 们也可用于二级存储。随机地点。由于电脑不能真正随机（也不想要他们）的任期随机位置有点误 导。随机地点一般指的是产品不会储存在指定的固定地点的地方。 如Zone逻辑, 您将需要一些额外的逻辑，以确定确切位置。先入先出（FIF 0的）。首先指示挑选最古老的库存。最后，先出（LIFO