订单管理系统中英文对照外文翻译文献
仓库管理系统外文翻译英文文献
仓库管理系统外文翻译英文文献核准通过，归档资料。
未经允许，请勿外传～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 ofconfusion among companies looking for software solutions for their operations.Even though WMS continues to gain added functionality, the initialcore functionality of a WMS has not really changed. The primary purposeof 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 fromone software vendor to another, however the basic logic will use a combination of item, location, quantity, unit of measure, and1order 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 uselivedocuments 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 couldbenefit from some of the functionality but is the benefit great enoughto 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. That’s ri ght, 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 collectionwill 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 servicethe customer by reducing cycle times. Expectations of inventoryreduction and increased storage capacity are less likely. Whileincreased 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 are2lot 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.SetupThe 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 is…well… sort of. In reality most operations have a much morediverse 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 pick3from, replenish from/to, and put away to, and in what sequence these events should occur (remember WMS is all about “directed” m ovement). 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 storedin 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 didn't think there were any realapplications 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 of4space 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.It’s very common to combine multiple logic methods to determine the best location. Forexample 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 variesfrom 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 onusing automated material handling equipment such as carousels, ASRS units, AGNS, pick-to-light systems, or separation systems, you’ll 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.5Advanced Shipment Notifications (ASN). If your vendors are capableof sendingadvanced 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 relatedto 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 I’m necessarily against capacity planning in warehousing, I just think most operations don’t really need it and can avoid the disap pointment of trying to make it work. I am, however, a big advocate of labor tracking for individual productivity measurement. Most WMS maintain enough datato 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 hasalready 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 ofother 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 t his as aunilateral 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 systems6as a point of reference, it is unlikely that this add-onfunctionality will match the functionality of best-of-breed 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 mayfind these WMS based business systems are a good fit.Implementation TipsOutside of the standard “don’t underestimate”, “thoroughlytest”, “train, train, train” implementation tips that apply to any business software installation ,it’s i mportant to emphasize that WMSare very data dependent and restrictive by design. That is, you need to have all of the various data elements in place for the system tofunction 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 competitive. It’s just impo rtant to note that every solution hasits 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 )的演变与许多其他软件解决方案是非常相似的。
ERP系统中英文对照外文翻译文献
ERP系统中英文对照外文翻译文献ERP系统中英文对照外文翻译文献(文档含英文原文和中文翻译)ERP系统在财务报告内部控制的作用【摘要】：萨班斯-奥克斯利法案法例中强调，ERP系统的重要作用是运用内部控制反映公司的基本建设，为此ERP系统软件开发供应商也增加了对内部控制的应用。
他们认为，这些内置的控制和其他功能将帮助企业改善其财务报告内部控制就如萨班斯法案要求的那样。
这项研究测试，通过检查萨班斯法案第404条在1994年和2003年之间实施ERP 系统的公司合规内控数据。
其结果表明，应用ERP 的公司相对于未应用ERP的样本公司较少报告内部控制弱点。
它还发现，这种差异存在一般控制和特别控制中。
关键词：企业资源规划；ERP；萨班斯-奥克斯利法案；萨班斯法案第404条；内部控制1简介2002年的萨班斯法案要求企业将其内部控制的有效性的报告与财务报告作为一个整体努力，以减少欺诈和恢复完整的财务报告过程的一部分。
ERP系统软件开发供应商已强调，ERP系统的重要作用是运用“内置”控制反映公司基本建设。
他们在营销理念强调了产品的功能，声称这些系统将帮助企业按萨班斯法案所要求提高内部控制的有效性。
这些供应商的声明激发了关于ERP系统对内部控制的影响一项有趣的实证问题研究。
具体来说，是不是实现ERP系统的企业或多或少可能比未实现ERP系统的公司较少在其年度报告报告内部控制弱点？已经进行过这特定区域研究的经验/档案相对较少的，因为之前萨班斯法案内部控制的数据并没有被公开报道。
这项研究的方法通过在文献资料检查一个已经宣布实施ERP系统和一个还没有类似的公司控制样本公司的抽样调查的内部控制数据来发现差距。
内部控制是在公司使用的以解决代理问题的许多机制之一。
其他的机制还包括财务报告，编制预算，审计委员会和外部审计（Jensen和佩恩2003）。
研究表明，内部控制降低了代理成本（Abdel-khalik 1993；Barefield 等，1993），有些甚至争辩说，即使没有萨班斯法案的要求，企业也有经济诱因报告内部控制（Deumes和Knechel，2008年）。
供应商管理中英文对照外文翻译文献
中英文对照外文翻译文献(文档含英文原文和中文翻译)互利共赢的供应商质量控制前言近年来，随着对供应链的重视，供应商管理正逐渐成为企业和学术界的关注对象，IS09000族标准以及QS 9000标准都对供应商的管理提出了相应的要求，与供应商管理有关的研究成果正逐渐增多，一些软件巨头也推出了供应商关系管理的软件，但是在这些研究成果和应用软件中，涉及到的供应商质量控制的内容只是一些最基本的要求，而供应商质量控制恰恰是供应商管理的最基本、最重要的内容。
另一方而，质量管理界对质量控制的研究取得了大量的成果，遗憾的是这些成果大多依然局限于企业的内部控制，仅仅研究从企业内部各环节如何改善产品的质量，而基于供应链的角度来研究质量控制的成果尚不多见。
因此，系统地研究经济全球化形势下供应商质量控制的理论与方法，将有助于推动我国企业产品质量的快速提高和供应链竞争优势的形成与巩固。
1、质量与企业共存质量一直是一个随着时代的变化而不断变化的概念，人们对质量的认识也往往因关注点不同而有所不同。
如，早在1908年，通用汽车公司的工程师们在皇家汽车俱乐部会员们的面前拆解了3辆凯迪拉克轿车，并把这些零件混在一起，而后从中选择零件重新组装成车，然后驾车绝尘而去。
这令在场的会员极为震惊，认为凯迪拉克车质量之高令人惊叹。
显然在当时，汽车零件具有互换性是一种了不起的质量特性，这也是福特公司的N型车和T型车取得辉煌成功的重要原因。
时至今日，即使农用三轮车的零部件也具有极高的互换性，零部件的标准化和互换性已经是理所当然的事情，不再是吸引顾客的重要质量特性。
可见质量的内涵是不断变化的。
那么究竟什么是质量呢?（1）市场竟争就是企业间对“顾客”的争夺，在日益激烈的“顾客”争夺战中，质量、价格、交付(交付日期、方式和手段)和服务是企业常用的四个法宝，其中质量是根本，离开质量其他三项将变得毫无意义，因此可以说质量己成为市场竞争的焦点。
它反映了产品是否能够反映顾客需求、能否满足顾客需求，从面决定了产品的市场前途。
中英文文献翻译-仓库管理系统( WMS )
英文原文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.Have a flexible location system.Utilize user-defined parameters to direct warehouse tasks and use liveHave 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 con tinue to run. That’s 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.SetupThe 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 locationsinto 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 is…well… 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 assigni ng 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 didn't 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.It’s 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, you’ll wa nt 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 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 bigadvocate 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 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 ofbest-of-breed 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 TipsOutside of the standard “don’t underestimate”, “thoroughly test”, “train, train, train” implementation tips that apply to any business software installation ,it’s 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 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 competitive. 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.中文译文仓库管理系统（ WMS ）仓库管理系统（ WMS ）的演变与许多其他软件解决方案是很像的。
存货管理中英文对照外文翻译文献
中英文对照外文翻译文献(文档含英文原文和中文翻译)原文:Controls for inventory management best Practices Material Source: Accounting control best practices Author: Steven M.B r a g g Overview: An enormous number of advanced systems are involved in the procurement ,handling ,and shipment of inventory ,all of which require different types of controls .In this chapter ,we discuss control systems for a wide range of system complexities, ranging from paper-based inventory acquisition systems ,through bar-coded trackingsystems，cross docking ,pick-to-light systems, and zone picking ,and on to controls for manufacturing resources planning and just-in-time systems .As usual ,the number of controls that could be installed may appear to be oppressively large ,and could certainly interfere with the efficient running of inventory-related activities .Consequently ,always be mindful of the need to install only those controls that are truly necessary to the mitigation of significant risks.4-1Controls for basic inventory acquisitionThis section describes controls over the acquisition of inventory where there is no computerization of the pross.Section4-9,'Controls for Manufacturing Resources Planning, presents a more advanced application in which purchase orders are generated automatically by the computer system.The basic acquisition process centers on the purchase order authorization，as shown in Exhibit 4.1,The warehouse issues a renumbered purchase requisition when inventory levees run low ，which is primary authorization for the creation of a multipart purchase order .One copy of purchase order goes back to the warehouse ，where it is compared to a copy of the purchase requisition to verify completeness ；another copy goes to the accounts payable department for eventual matching to the supplier invoice .A fourth copy is sent to the receiving department ，where it is used to accept incomingdeliveries，while a fifth copy is retained in the purchasing department .In short ,various copies of the purchase order drive orders to suppliers ,receiving ,and payment.The controls noted in the flowchart are described at greater length next ，in sequence from the top of the flowchart to the bottom.*Warehouse ：Prepare a renumbered purchase requisition .In the absence of a formal inventory management system, the only people who know which inventory items are running low are the warehouse staff. They must notify the purchasing department to issue purchase orders for inventory replenishments. To ensure that these requisitions are made in an orderly manner, only renumbered requisition forms should be used, and preferably they should be issued only by a limited number of warehouse staff. By limiting their use, it is less likely that multiple people will issue a requisition for the same inventory item.*Purchasing: Prepare a renumbered purchase order. The primary control over inventory in a basic inventory management system is through the purchases function ,which controls the spigot of inventory flowing into the warehouse, This control can be eliminated for small-dollar purchase for fittings and fasteners, which are typically purchased as soon as on-hand quantities reach marked reorder points in their storage bins (visual reorder system).Since the purchase order is the primary control over inventory purchases,you can avoid fake purchaseorders by using renumbered forms that are stored in a locked cabinet.*Verify that purchase order matches requisition .Once the warehouse staff receives its copy of the purchase order; it should compare the purchase order to the initiating requisition to ensure that the correct items were order. Any incorrect purchase order information should be brought to the attention of the purchasing staff at once.*Reject unauthorized deliveries, to enforce the use of purchase orders for al inventory purchases, the receiving staff should be instructed to reject all deliveries for which there is no accompanying purchase order number.*Match receipts to purchase order authorization. Once an order is received, the warehouse staff should enter the receiving information into a receiving report and send the receiving report to the accounts payable department for later matching to the supplier invoice and purchase order, It should also send a copy of the report to the purchasing department for further analysis.*Cancel residual purchase order balances. Upon receipt of the receiving report from the receiving department, the purchasing staff compares it to the file of open invoices to determine which orders have not yet been received and which purchase orders with residual amounts outstanding can now be cancelled .Otherwise, additional deliveries may arrive well after the date when they were originally needed.*There-way matching with supplier invoice for payment approval. Upon receipt of the receiving report, the accounts payable staff matches it to the supplier invoice and authorizing purchase order to determine if the quantity appearing on the supplier invoice matches the amount received and that the price listed on the supplier invoice matches the price listed on the purchase order. The department pays suppliers based on the results of these matching processes.The next control is supplemental to the primary controls just noted for the inventory acquisition process.*Segregate the purchasing and receiving functions. Anyone ordering supplies should not be allowed to receive it, since that person could eliminate all traces of the initiation order and make off with the inventory .This is normally considered a primary control, but it dose not fit into the actual transaction flow noted earlier in Exhibit 4.1 and so is listed here as a supplemental control.*Require supervisory approval of purchase orders. If the purchasing staff has a low level of experience ,it may be necessary to require supervisory approval of all purchase order before they are issued, in order to spot mistake ,This approval may also be useful for large purchasing commitments.*Inform suppliers that verbal purchase orders are not accepted. Suppliers will ship deliveries on the basic of verbal authorizations,which circumvents the use of formal purchase orders. To prevent this, periodically issue reminder notices to all suppliers that deliveries based on verbal purchase orders will be rejected at the receiving dock.*Inform suppliers of who can approve purchase orders. If there is a significant perceived risk that purchase orders can be forged ,then tell suppliers which purchasing personnel are authorized to approve purchase orders and update this notice whenever the authorization list changes. This control is not heavily used, especially for large purchasing department where the authorization list constantly changes or where there are many suppliers to notify. Usually the risk of purchase order forgery is not perceived to that large.4-2 Control for basic inventory storage and movementThis section describes control for only the most basic inventory management system, where there is no perpetual inventory tracking system in place, no computerization of the inventory database ,and no formal planning system, such as manufacture resources planning(MRPII)or just-in –time(JIT). When there is no perpetual inventory tracking system in place, the key control tasks of the warehouse staff fall into four categories:1. Guard the gates .The warehouse staff must ensure that access to inventory is restricted, in order to reduce theft and unauthorized use of inventory .This also means that warehouse staff must accept onlyproperly requisitioned inventory and must conduct a standard receiving review before accepting any inventory.2. Orderly storage .All on-hand inventories must be properly organized, so it can be easily accessed, counted, and requisitioned.3.Accurate picking ,The production department depends on the warehouse for accurate picking of all items needed for the production process ,as is also the case for picking of finished goods for delivery to customers.4. Timely and accurate requisitioning, when there is no computer system or perpetual card file to indicate when inventory levels are too low, the warehouse staff must use visual reordering systems and frequent inventory inspections to produce timely requisitions for additional stock.Exhibit 4.2 expands on the general control categories just noted .In the general category of “guarding the gates,” controls include rejecting unauthorized deliveries as well as inspecting ,identifying ,and recording all receipts .The orderly storage goal entails the segregation of customer-owned inventory and the assignment of inventory to specific locations .To achieve the accurate picking goal calls for the use of a source document for picking ,while the requisitioning target requires the use of pre numbered requisitions and document matching .A number of supplement controls also bolster the control targets.The controls noted in the flowchart are described at greater length next, in sequence from the top of the flowchart to the bottom .Also; a few controls from the last section (concerning requisitions and receiving) are repeated in order to form a complete picture of all required controls.*Reject unauthorized deliveries .To enforce the use of purchase orders for all inventory purchase, the receiving staff should be instructed to reject all deliveries for which there is no accompanying purchase older number.*Conduct receiving inspections with a checklist .The receiving staff is responsible for inspecting all delivered items .if staff members perform only a perfunctory inspection all delivered item .If staff members perform only a perfunctory inspection ,then the company is at risk of having accepted goods with a variety of problems .To ensure that a complete inspection is made ,create a receiving checklist describing specific inspection points ,such as timeliness of the delivery ,quality ,quantity ,and the presence of an authorizing purchase order number .Require the receiving staff to initial each item on the receiving checklist and then file it with the daily receiving report.*Identify and tag all received inventory .Many inventory items are difficult to identify once they have been removed from their shipping containers ,so it is imperative to properly identify and tag all received items prior to storage.*Put away items immediately after receipt .It is difficult for the warehouse staff to determine whether more inventory should be requisitioned if the inventory is sitting in the receiving area rather than in its designated location. Consequently, a standard part of the receiving procedure should be to put away items as soon after receipt as possible.*Conduct daily reordering review .When there is no perpetual inventory system ,the only way to ensure that sufficient quantities are on hand for expected production levels is to conduct a daily review of the inventory and place requisitions if inventory items have fallen below predetermined reorder points.*Issue pre numbered requisitions to the purchasing department .The warehouse should issue only pre numbered requisitions to the purchasing department .By doing so, the warehouse staff can maintain a log of requisition numbers used and thereby determine if any requisitions have been lost in transit to the purchasing department.*Verify that purchase order matches requisition, once the warehouse staff receives its copy of purchase order, it should compare the purchase order to the initiating requisition to ensure that the correct items were ordered .And incorrect purchase order information should be brought to the attention of the purchasing staff at once.译文:存货管理控制最佳实务概述:存货的采购、处理、和装运过程涉及很多先进的系统，所有这些都需要不同类型的控制措施。
智能物流系统中英文对照外文翻译文献
智能物流系统中英文对照外文翻译文献智能物流系统在现代物流行业中发挥着重要的作用。
本文翻译了一篇关于智能物流系统的外文文献，提供了中文和英文对照的版本。
Title: A Translation of Foreign Literature on Intelligent Logistics SystemsAbstract:Introduction:Main Body:1. Definition of Intelligent Logistics Systems- 中文：智能物流系统是指应用人工智能和物联网技术，对物流过程进行智能化管理和优化的系统。
- English: Intelligent logistics systems refer to systems that apply artificial intelligence and Internet of Things technologies to intelligently manage and optimize logistics processes.2. Key Features of Intelligent Logistics Systems- 中文：智能物流系统的主要特点包括即时监控、自动化处理和智能决策等。
- English: The key features of intelligent logistics systems include real-time monitoring, automated processing, and intelligent decision-making.3. Benefits of Intelligent Logistics Systems- 中文：智能物流系统的应用带来了许多好处，包括提高运输效率、降低成本和减少错误率等。
- English: The application of intelligent logistics systems brings numerous benefits, including improved transportation efficiency, cost reduction, and error rate reduction.Conclusion:This translation provides an insight into the concept, functions, and benefits of intelligent logistics systems. Understanding these aspects is essential in harnessing the potential of such systems in the logistics industry.Reference:[Insert reference to the original foreign literature here]以上为智能物流系统中英文对照外文翻译文献的简要内容翻译。
餐饮管理系统中英文对照外文翻译文献
餐饮管理系统中英文对照外文翻译文献(文档含英文原文和中文翻译)外文:A Comparative Study of Web Application Design ModelsUsing the Java TechnologiesAbstract.The Servlet technology has been the most widely used technology for building scalable Web applications. In the events, there are four design models for developing Web applications using the Java technologies: Model 1, Model2, Struts, and JavaServer Faces (JSF). Model 1 employs a series of JSP pages; Model 2 adopts the Model-View-Controller pattern; Struts is a framework employing the Model 2 design model; and JSF is a new technology that supports ready-to-use components for rapid Web application development. Model 1 is not recommended for medium-sized and large applications as it introduces maintenance nightmare. This paper compares and evaluates the ease of application development and the performance of the three design models (Model 2, Struts, and JSF) by buildingthree versions of an online store application using each of the three design models, respectively.1 IntroductionToday, Web applications are the most common applications for presenting dynamic contents. There are a number of technologies for building Web applications, the most popular of which is the Servlet technology . This technology gains its popularity from its superiority over other technologies such as CGI and PHP .Servlets are cumbersome to develop, however, because sending HTML tags requires the programmer to compose them into a String object and send this object to the browser. Also, a minor change to the output requires the servlet to be recompiled. To address this issue, Sun Microsystems invented JavaServer Pages (JSP) . JSP allows HTML tags to be intertwined with Java code and each page is translated into a servlet. A JSP page is a servlet. However, compilation occurs automatically when the page is first requested. As a result, changing the output does not need recompilation. In addition, JSP enables the separation of presentation from the business logic through the use of JavaBeans and custom tag libraries. The norm now in developing Javabased Web applications is to use servlets along with JavaServer Pages.In the later development, there are a number of design models for building servlet/JSP applications: Model 1, Model 2, Struts , and JSF . Model 1 and Model 2 were first mentioned in the early specifications of JSP. Model 1 strictly uses JSP pages, with no servlets, and Model 2 uses the combination of both servlets and JSP pages. The terms of Model 1 and Model 2 have been used ever since. Model 1 is suitable for prototypes and very small applications, and Model 2 is the recommended design model for medium sized and large applications.As Model 2 gained more acceptances in the industry, an open source initiative to build the Struts Framework was initiated. Struts perfects Model 2 by providing the controller part of the Model-View-Controller of Model 2. In addition, Struts provides better page navigation management and several custom tag libraries for more rapid development. Despite its steep learning curve and the fact that it was never defined in any specification, Struts has been gaining popularity as thealternative to Model 2.JavaServer Faces is built under the Java Community Process under JSR-127.Sun Microsystems proposed this technology in the hope that JSF will be the ultimate model for building Java Web applications. The most important feature of JSF is the availability of ready-to-use components such as extensible UI components, easy page navigation, input validators, data converters and JavaBeans management.The problem facing servlet/JSP programmers are to choose the most appropriate design model. Clearly, JSF provides a better solution in regard to development time. However, some people are not sanguine to adopt this technology for fear of performance penalty due to the overhead of the JSF implementation.We build three versions of an online store application named BuyDirect using Model 2, Struts and JSF. The parameters compared are the number of lines of code, the number of classes, and the performance measurement results. We investigate which of the design models allows the most rapid development process. We evaluate the performances of the applications built upon these models. We provide some suggestions to perfect the existing design models to make development more rapid.The rest of the paper is organised as follows. Section 2 discusses the issues in Web development. Section 3 explains how the three design models address these development issues. Section 4 provides the details of the hardware and software used in these experiments. Section 5 presents the experiment results and analysis. Section 6 reviews the related work. Section 7 concludes by offering some suggestions to improve the existing design models.2 Java Web Development IssuesAll Java Web development uses the Servlet technology as the underlying technology. As such, all Java Web applications have certain issues that need to be addressed:User Interface. The user interface is what the client browser renders as HTML tags. Any server-side component used in the application must be encoded intothe corresponding HTML elements. Besides for displaying the content and data, the user interface is also responsible in receiving input from the user.●Input Validation. User input needs to be validated. There are two types of inputvalidation, server-side and client-side. As the name implies, the server-side input validation is performed on the server after the input reaches the server.Client-side input validation is done on the browser, usually by using JavaScript or other scripting languages. The advantages of using client-side input validation are prompt response and reducing the server workload. The server-side input validation should always be performed regardless the presence of client-side validation because there is no guarantee the user browser's scripting feature is being on and malicious users can easily work around client-side validation.●Model Objects. Model objects in Java-based Web applications are in the formsof JavaBeans. Model objects make up the Model part of the MVC based design model. A model object can be used to bind a component value to be used at a later stage. In addition, it can encapsulate business logic required for processing.●Page Navigation. Almost all Web applications have multiple pages that the usercan navigate from one to another. All MVC-based design models use a servlet as the Controller part. This servlet also acts as the sole entry point to the application. Which page to be displayed after the current request is determined by the value of a specified request parameter. Managing page navigation is critically important.3 Web Application Design ModelsThe Model 2 design model is based on the Model-View-Controller (MVC) design pattern. As explained by Burbeck , there are three main modules in MVC, the Controller, the View, and the Model. The Controller acts as the central entry point to the application. All user interactions go through this controller. The View contains the presentation part of the application, and the Model stores data or encapsulates business logic of the application. In the later development, the Struts Framework provides a common framework to easily build Model 2 applications.Then, the last initiative is the JavaServer Faces, which also employs the MVC design pattern.In the following sections, we discuss these three design models and explain how each design model addresses the development issues specified in the previous section.3.1 Model 2A Java Web application that is based on the Model 2 design model has one servlet(called the Controller servlet) that serves as the Controller part. All requests are first handled by this servlet, which immediately dispatches the requests to the appropriate views using RequestDispatcher objects. Views in the Model 2 design model are represented by JSP pages. To store data, a Model 2 application uses JavaBeans, which are the Model part of the application. In addition to storing data, the JavaBeans also encapsulate business logic. Each HTTP request carries an action parameter that indicates which view to dispatch this request to. The programmer must code the HTML tags for user interface in all JSP pages in the application and write input validation code. In addition, the model objects are managed by individual JSP pages.3.2 StrutsThe Struts Framework is an improvement of the Model 2 design model. It provides a default Controller servlet so that the user does not have to write and compile one. Struts alleviates the task of page navigation by allowing navigation rules to be present in its application configuration file (an XML document). Changes to the navigation rules do not require recompilation of a Java servlet class. In addition to easier page navigation, Struts provides custom tag libraries that define tags representing HTML elements. One of these tags is used for error handling and Struts is therefore capable of displaying localized error messages in support for internationalization. Struts applications use JavaBeans as their models, just like the Model 2 design model. In addition, Struts programmers have to write their own input validation code.3.3 JSFJSF also employs a controller servlet that is called FacesServlet. This servlet is the only entry point to a JSF application. JSF also uses JSP pages as its views and JavaBeans as its model objects. Unlike Model 2 and Struts, however, JSF provides ready-to-use user interface components that can be written on JSP pages. Upon an invocation of a page of a JSF application, the FacesServlet constructs a component tree that represents the JSP page being requested. Some of the components can also trigger events, making JSF event-driven. For page navigation, JSF uses an approach similar to Struts, i.e., by allowing navigation rules to be defined in an application configuration file (again, an XML document).What distinguishes a JSF application from non-JSF servlet/JSP application is that JSF applications are event-driven. The user interface of a JSF application is one or many JSP pages that host Web components such as forms and input boxes. These components are represented by JSF custom tags and can hold data. A component can be nested inside another, and it is possible to draw a tree of components. Just as in normal servlet/JSP applications, you use JavaBeans to store the data the user entered.4 Function EnvironmentThe software and hardware details for our experiments are described below.4.1 The Servlet ContainerA Java Web application runs in a servlet container, which is the engine that processes the incoming HTTP requests for the resources in the application. For this research project, we use Tomcat, an open source servlet container from the Apache Software Foundation. The version we use is 6.0.Basically, a servlet container processes a servlet by performing the following tasks:- Creating the HttpRequest Object- Creating the HttpResponse Object- Calling the service method of the Servlet interface, passing the HttpRequest and HttpResponse objects.4.2 Testing ClientsFor performance testing, we emulate multiple users using JMeter 1.9 , also from the Apache Software Foundation. JMeter allows the user to choose the number of threads to perform testing. Each thread emulates a different user. JMeter also lets us choose how many times a test will be done. To test a Web application using JMeter, you direct requests to certain IP address, context path, and port number. You can also specify request parameters to be included in each HTTP request. As the output, JMeter notifies the response time of the server in milliseconds for a test. From the response time, we derive the number of hits/seconds the server is capable of serving.4.3 HardwareWe use different computers for running the applications and for testing, so as to obtain maximum performance measurement accuracy. The computer running the application is a XP machine having the following hardware specifications: Intel Core 1GHz CPU with 1G RAM. The computer running the testing clients is a Windows 2000 machine running JMeter. The computer has the following specifications: Intel Core 1GHz CPU with 1G RAM.5 ResultsWe obtain experimental results in two categories: the ease of development and performance. The ease of development category compares the number of classes and the number of lines of code. These numbers indicate how easy it is to develop an application by following a certain design model. An application with the fewer number of classes or the number of lines of code indicates that the application is relatively easier to build. The application with the more number of classes indicates that the application takes more time to develop.The performance measurement results are obtained by comparing two operations. The Search operation is the most common operation in such an application,and the Browse operation.5.1 Ease of Application DevelopmentAs Table 1 shows, it takes the most effort to implement the Model 2 design model. Using Struts alleviates the problem a bit, and the best saving in the development comes if one uses JSF.Table 1. The number of classes and the number of lines for the applications under studyThe Model 2 design model is characterised by the presence of a Controller servlet and a number of JavaBeans classes (as the Model) and JSP pages (as the Views). The Controller servlet is responsible for page navigation rules that employ a series of if statements. Model 2 application programmers must also code for the input validation that in this research is implemented inside a number of custom tag libraries. The other classes in the Model 2 design model are custom tag library and the tag library descriptors responsible for input validation and data display. In fact, input validation takes 590 lines of code, or almost 30% of the total amount of code.In the Struts application, the Controller servlet is provided by the framework, therefore a Struts programmer saves time for not having to write one. However, he/she still needs to write page navigation rules in the Application Configuration file, which is easier than writing a servlet because the Application Configuration file can be edited using a text editor and no compilation is necessary. Input validation must still be done manually, even though the Struts Framework provides an error handling mechanism. The number of classes and the number of lines of code for input validation are almost similar to the Model 2 application. In Struts, the other classes are Action classes to which the default Controller servlet dispatches requests.In JSF input validation comes free through the availability of validatorcomponent. As a result, a JSF application developer can skip this task. In addition, page navigation takes the same course as Struts, i.e. by utilising an Application Configuration file. The other classes in JSF are a ContextListener, an ActionListener, and a Database utility class.5.2 Performance MeasurementFor each operation, we measure the server response time (in milliseconds) for 1 to 10 concurrent users. The number of users is specified by setting the number of threads in Jmeter. Each test is conducted 10 times and the average is taken. Each operation is discussed further is the following sub-sections.5.2.1 Search OperationThe Search operation whose name or description matches the keyword. There is one SQL SELECT statement performed. Figure 2 compares the three versions of applications for the Search operation.Fig. 2. The performance comparison for the Search operation For the Model 2 application, the average server response time for one user is 173 ms and for 10 users is 919 ms. For the Struts application, these numbers are 189 ms and 900 ms, respectively. For the application built using JSF, the average server response time is 210 ms for one user and 932 ms for 10 users. The increase of the response time is proportional to the increase of the number of concurrent users, which means that the server is still able to cope with the load.The Model 2 application has the least overhead, therefore the averageperformance should be better than the Struts and JSF applications. However, the Struts application performs as well as the Model 2 application. This is because the server has enough memory to load all Struts libraries required to run Struts. Also, note that page navigation rules in Struts are loaded and stored in an object called ActionMapping. Therefore, given an action request parameter, the next page of navigation is obtained through a look-up. On the other hand, the Model 2 application uses a series of if statements to find the next page of navigation, given the action request parameter.The JSF application performs slightly worse than the other applications in almost all numbers of concurrent users. This could be due to the time taken by the JSF implementation to construct a component tree for each page requested. However, the difference in server response time between JSF and other applications is not that significant.5.2.2 Browse OperationThe Browse operation,like the Search operation, there is one SQL SELECT statement performed. Figure 3 gives the test results for this operation.Fig. 3. The performance comparison for the Browse operation On average, the Model 2 application performs the best because it has the least overhead. The average server response time is 111 ms for one user and 899 ms for 10 users. The Struts application has comparable performance, with one user average server response time of 180 ms and 10 user response time of 920 ms. The JSF lacks a bit behind the two applications with these numbers being 190 and 1009ms respectively. The increase of the server response time is proportional to the increase of the number of concurrent users, which means the server is able to serve those users well. The average performance measurement results of the Browse operation are very similar to the ones for the Search operation because the database operations of both operations are also similar.6 Related WorkCompare the performance of database-based Web applications using Java servlets, PHP version 3, and Common Gateway Interface (CGI). After a series of benchmark tests that performs data retrieval from a MySQL database, find that the solution of Java servlets with persistent database connection has the best performance. PHP3 using persistent database connections performs fairly well when compared to the CGI solution,also mention the advantages of using Java servlets. According to these authors. Java servlets are an excellent choice to meet the requirement of e-commerce (such as online shopping) applications and are able to handle client requests in a highly interactive mode.Comparing PHP 4, Java servlets, and Enterprise JavaBeans. Measure the performance of these three architectures using two applications. Study reveals that PHP4 is more efficient than Java servlets, and the EJBs perform even worse than servlets. However, note that servlets, being part of the Java solution, provides the flexibility of being able to be ported to another system with a different operating system.7 ConclusionWe find that it is most rapid to build Web applications using JSF. Model 2 applications are the least rapid but give the best performance. Struts applications sit in the middle of the other two design models in both comparisons.We make some suggestions that could improve the Servlets technology in general and enhance the performance of applications based on both design models. Struts. Struts is not based on any specification and there is no documentation that discusses its internal working. Therefore, it is hard to know what have been implemented and what could be improved.●The Servlets Technology. The Servlet 2.3 Specification does not define anycaching mechanism. There is no mention of caching in the upcoming Servlet2.4 Specification either. Despite the dynamic nature of the content of a Webapplication, some contents do not change very often. For example, the categories of products that a user can browse in an online store application probably only change once in a month. If those semi-static contents must be generated from the database every time they are requested, a lot of programming resources will be wasted. Servlet programmers get around the absence of caching by writing an object that caches certain content. However, since there is no standard for caching, many programmers write the same piece of code again and again.●Model 2.The main drawback is that the page navigation rules are hard-coded inthe Controller servlet. This means any minor change to the program flow will require the Controller servlet to be re-compiled. The solution to this problem is to provide a mapper that reads the page navigation rules when the application starts. The code could be conveniently written in the init method of the Controller servlet. This method is only executed once, i.e. the first time the servlet is loaded into memory. If the properties file needs to be re-read every time it changes, the programmer can check the timestamp of the properties file for each request, and compares it with the previous read of this file. If the timestamp is more current than the previous read, the mapper can be re-constructed. This feature can be enabled and disabled by using an initial parameter in the Context object. At the development phase, this feature should be enabled. At deployment, this feature should be off. The use of the properties file to store the page navigation rules also makes it possible to avoid a series of if statements in the Controller Servlet, which can be time-consuming for every request. Instead, a HashMap can be used, with action request parameters as keys and the next JSP pages as values. The other disadvantage of this design model is the absence of standard components for input validation and user interface. However, this has been solved in JSF.●JSF. JSF provides solutions to common problems in Web development, such aspage navigation management, UI components and input validators. However, because this technology is still very young, there are not too many UIcomponents available, forcing programmers to combine JSF with non-JSF servlets/JSP pages. JSF is event-driven. JSF programmers determine the behavior of a JSF application by writing event listeners, just like those listeners in a Swing application. In JSF version 1.0, there are currently two types of events that can be triggered: ActionEvent and ValueChangedEvent. However, this is good enough to provide sufficient level of interactivity between the application and its users. Adding more types of events will definitely make JSF more appealing.References［1］．Cecchet, E., Chanda A., Elnikety S., Marguerite J., Zwaenepoel W.: Performance Comparison of Middleware Architectures for Generating Dynamic Web Content. Proceeding of the 4th International Middelware Conference, 2003.［2］．Cecchet, E., Marguerite, J., and Zwaenepoel, W.: Performance and Scalability of EJB Applications. Proceedings of OOPSLA’02, 2002.基于Java技术的Web应用设计模型的比较研究摘要Servlet技术在建立可扩展性Web应用中是被应用最广泛的技术。
外文文献及翻译-物料管理系统(MMS)
外文文献及翻译-物料管理系统(MMS)本文介绍了物料管理系统(MMS)的相关外文文献及翻译。
1. 文献标题： A review of material management system in construction industry文献标题： A review of material management system in construction industry- 作者： John Smith作者： John Smith- 出版年份： 2015出版年份： 2015该文献综述了建筑行业中物料管理系统的现状和发展趋势。
介绍了物料管理系统在建筑项目中的重要性和作用，并提出了一些物料管理系统的关键要素。
该文献还讨论了物料管理系统在提高项目效率和降低成本方面的影响。
2. 文献标题： Implementation of an integrated material management system for manufacturing industry文献标题：Implementation of an integrated material management system for manufacturing industry- 作者： Jane Chen作者： Jane Chen- 出版年份： 2018出版年份： 2018该文献介绍了制造业中一种集成化物料管理系统的实施方法。
文章详细说明了该系统的架构和功能，并介绍了该系统在物料采购、库存管理和供应链协调方面的优势。
研究还分析了实施该系统对制造业企业的影响和效益。
3. 文献标题： Material management system for construction projects using RFID technology文献标题： Material management system for construction projects using RFID technology- 作者： Peter Wang作者： Peter Wang- 出版年份： 2016出版年份： 2016该文献介绍了一种利用射频识别(RFID)技术的物料管理系统，用于建筑项目中的物料追踪和管理。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
中英文对照外文翻译(文档含英文原文和中文翻译)MySQL and JSP Web applicationsJSP developers encounter unique problems when building web applications that require intense database connectivity. MySQL and JSP Web Applications addresses the challenges of building data-driven applications based on the JavaServer Pages development model. MySQL and JSP Web Applications begins with an overview of the core technologies required for JSP database development--JavaServer Pages, JDBC, and the database schema. The book then outlines and presents an Internet commerce application that demonstrates concepts such as receiving and processing user input, designing and implementing business rules, and balancing the user load on the server. Through the JDBC (Java DataBase Connector), the developer can communicate with most commercial databases, such as Oracle. The solutions presented in MySQL and JSP Web Applications center on the open source tools MySQL and Tomcat, allowing the reader an affordable way to test applications and experiment with the book'sexamples.So What Is JSP All About?If you meet the requirements mentioned, you should already have a pretty good idea what the answer to this question is. JSP is all about doing highly object-oriented Web sites that can leverage all the best practices of modern software engineering. These practices include things such as SQL databases and UML-based design. This isn't to say that JSP is a cure-all and that using it will automatically make your Web site a paragon of engineering art. It's just as possible to design bad Web sites in JSP as with any other technology. That's why, as you go through the text, you will see how to incorporate the best practices and how to avoid the pitfalls of convenience when projects get stressful. JSP itself is an evolutionary step along the path that started with the first static Web servers, moved through CGI-enabled servers, and finally the first generation of script-enabled servers. JSP is less a Web server with a Java component than it is a Java engine that understands the Web.JSP grew out of Java servlets. Servlets allow the developer to handle the incoming Web requests using a Java program that has access to all the normal information that a Common Gateway Interface (CGI) program would. In addition, the servlet has access to session-persistent objects. These are Java objects that are associated with a specific user session and can be used to store state between requests. Servlet programming was a major step forward in allowing developers to write well-structured modular Web applications using an object-oriented language. It also solved the problem of state persistence, allowing more information to reside on the server during a transaction and less to have to pass back and forth between the user and the server. Servlets still suffered from one major problem. Because they eventually need to spit out HTML, the HTML coding had to be embedded in the servlet code. This led to code fragments like the one shown here:Out.println("<HTML>\n<HEAD>\n<TITLE>Thank you forRegistering</TITLE></HEAD>\n");Out.println("<IMG SRC=\"thanks.jpg\" WIDTH=200 HEIGHT=100 ALIGN=\"LEFT\”>");This kind of embedding gets very old very fast when you have to code a lot of pages. In addition, having to escape all of the quotation marks can lead to a lot of confusing andhard-to-find errors if you leave out a backslash. Eventually, a still-better idea emerged. Suppose that you could combine the best of static HTML pages and with the interactive capabilities of servlets. The result was JavaServer Pages (on the Microsoft side, the result was Active Server Pages). As Figure I.1 shows, JSP is a complicated beast. In the next chapter, you'll walk through this flow in detail, but for the moment, here are the major steps:1. A request comes in from a browser using the normal HTTP request format.2. The Web server hands off the request to JSP. JSP looks at the filename and finds the appropriate JSP file.3. The .jsp file is converted into a .java file, containing Java code that will create a class whose name is derived from the .jsp filename.4. JSP then compiles the .java file using javac to produce a .class file. Note that the two previous steps are skipped if a .class file already exists and is newer than the .jsp file.5. An instance of the newly created class is instantiated and sent the _jspService message.6. The new instance looks to see if there is already an instance of the er object called user existing in the session object space for the currently connected user. If not, one is instantiated.7. As part of servicing stuff.jsp, the user instance is called with the getUserName() method.8. If the JSP processing requires access to information in a database, it uses JDBC to make the connection and handle the SQL requests.As you can see, a tremendous amount of power is available in the JSP world. Developers are free to write Web pages that look mostly like HTML, except where callouts to Java are required. But, at the same time, they are free to develop fully fleshed-out object-oriented applications using all the features that Java can bring to bear. They also get all the benefits of servlets, including session persistence.Why Do We Need Databases?Well, one reason is so that Larry Ellison of Oracle can afford to keep himself on Prozac when he thinks about Bill Gates. A more serious answer is the same reason that drove man to first press a stick against a piece of wet mud: because it's good to write things down. Web servers are marvelous creatures, but they're a bit like idiot savants. Ask them to serve a Web page or run a piece of Java, and they perform like a champ. But start asking them to remember what they didfive minutes ago, and they develop amnesia faster than a character in a soap opera.The first and most important reason that you use databases is that there's a lot in an e-commerce transaction that you need to remember and track:•A user's name, address, credit card, and other information previously entered on a registration page•hat the user might have put into a shopping car t and left from a previous transaction•What items are in stock, along with their price, description, and so on•Orders that need to be fulfilled, orders that have been shipped, and items that have been backordered .Now, you could store all this information in a flat file on the server's hard disk, but there are other important properties that you want to have for this data:•You want to be able to back out a transaction if part of it fails.•You want to be able to locate the data somewhere more secure than the Web server, which could be in a DMZ or outside the firewall altogether.•You want to be able to access data such as user data or products quickly, even if there are thousands or millions of them.When you add these items to the shopping list, only a relational database will really do the job effectively.MySQLMany sites don't need the battleship strength (and price tag) of Oracle. MySQL is an open-source SQL database available for anyone to use, with many (although not all) of the features of its big brothers, such as Oracle.MySQL is available for just about any computer that has decent power—it is fairly lightweight on the processor and easy to install (10 minutes, as opposed to multiple hours for Oracle).So, perhaps you are wondering, what's the catch? What are you not getting in MySQL that makes people turn to Oracle? Well, MySQL is a neat little package, but it is missing some things that would be nice to have in a perfect world.A major feature that MySQL does not offer is database consistency checking. You can useforeign key tags in your schema, but MySQL cheerfully ignores them. A lot of DB As I know would consider this a very bad thing.A foreign key constraint prevents you from creating inconsistent data. For example, let's suppose that you had a scheme that looked like this:CREATE TABLE USER (USERID INTEGER,FIRST_NAME V ARCHAR(80),LAST_NAME V ARCHAR(80));CREATE TABLE PURCHASE (USERID FOREIGN KEY USER(USERID),ITEM INTEGER,QUANTITY INTEGER);In a database such as Oracle's, if you created an entry in the PURCHASE table with a user ID of 3, there would have to already be a user ID of 3 in the USER table or an error would occur. Similarly, you couldn't delete user 3 from USER if it was referenced in PURCHASE.The MySQL folks make a pretty impassioned argument in their documentation that depending on foreign keys for data integrity is a bad idea anyway, but convincing your DBA of this philosophy is likely to degrade into a religious debate.In addition, some other features are missing, such as subselects and select into. But probably the other major piece that you will miss is the rollback/commit functionality. MySQL does implement rollback and commit for certain types of tables, but not all of them. Again, the MySQL folks offer their own spin on why this is okay, but being able to roll back transactions is (in my opinion) important enough to make sure that you have it available.Rollback allows you to set a savepoint on the database before starting to do a series of transactions with it, and be able to either roll back to the original state or commit the changes at the end. For example, when recording a purchase, you need to record a debit against the user's account and enter a record into the shipping table so that you'll know later to ship the item. Let's say that the second part fails. You wouldn't want to charge the user but not ship the item. Thus, you'd want to roll back to the state before the transaction began.So, MySQL isn't a full-blown production database—at least, not yet. It's still good enoughfor probably 90% of the e-commerce sites in the world, however. And version 4.0, which is in alpha as of this writing, addresses a number of these concerns, including row-level locking and transaction control.Putting Tomcat and MySQL TogetherCombining Tomcat and MySQL provides a powerful, reliable, and free platform that you can use to learn, develop, and deploy JSP applications. And, best of all, the code that you develop using this platform will run nicely using iPlanet and Oracle or WebSphere and SQL Server.As a learning tool the two together are almost "reference implementations" of their respective protocols (JSP and SQL). As a result, you won't pick up any nasty vendor-proprietary bad habits while you're getting up to speed.In addition, you can enjoy the knowledge that you are supporting the open-source software movement. Open-source software is code that is made freely available under one of several public licenses, frequently the GNU General Public License (GPL).Why is it good to support this movement? There are two sides to this answer: one technical and one political. Technically, it's a good thing because open-source software tends to encourage the development of open standards such as JSP and JDBC, allowing youto choose your tools from among a larger group rather than being locked into one vendor's proprietary solution. It's a positive thing politically because it keeps the large companies honest. WebLogic and iPlanet have to stay competitive and responsive because they know that there's a free solution out there if they aren't. And when you use open-source software, you are sending a message that your overriding concerns are features and reliability, not having a large company to sue if something goes wrong.MySQL和JSP的Web应用程序JSP开发人员构建Web应用程序时遇到需要强大的数据库连接的特殊问题。