購買設計請充值后下載，，資源目錄下的文件所見即所得，都可以點開預覽，，資料完整，充值下載可得到資源目錄里的所有文件。。。【注】：dwg后綴為CAD圖紙，doc,docx為WORD文檔，原稿無水印，可編輯。。。具體請見文件預覽，有不明白之處，可咨詢QQ:12401814
編號
無錫太湖學院
畢業(yè)設計（論文）
相關資料
題目： 機械零件的計算機管理系統(tǒng)
信機 系 機械工程及自動化專業(yè)
學 號： 0923078
學生姓名： 蔡天華
指導教師： 王士同 （職稱：教授）
（職稱： ）
2013年5月25日
目 錄
一、畢業(yè)設計（論文）開題報告
二、畢業(yè)設計（論文）外文資料翻譯及原文
三、學生“畢業(yè)論文（論文）計劃、進度、檢查及落實表”
四、實習鑒定表
無錫太湖學院
畢業(yè)設計（論文）
開題報告
題目： 機械零件的計算機管理系統(tǒng)
信機 系 機械工程及自動化 專業(yè)
學 號： 0923078
學生姓名： 蔡天華
指導教師： 王士同 （職稱：教授 ）
（職稱： ）
2012年11月20日
課題來源
參照老師意見，確立此題目
科學依據(jù)（包括課題的科學意義；國內外研究概況、水平和發(fā)展趨勢；應用前景等）
（1）課題科學意義
在機遇與挑戰(zhàn)并存的前提下，企業(yè)面臨著前所未有的競爭壓力，企業(yè)必須盡快的調整內部的產業(yè)結構，轉換管理方式，建立一套適合自身發(fā)展的管理系統(tǒng)來面對市場的挑戰(zhàn)。目前市面上流行的員工管理系統(tǒng)不少。但是，對于不同企業(yè)的員工管理系統(tǒng)來說，需要一個符合自己企業(yè)制度的員工管理系統(tǒng)，只需要一個操作方便，功能實用，能滿足企業(yè)對員工的日常管理就可以了。本系統(tǒng)的目的就是在于開發(fā)一個功能實用、操作方便，簡單明了的員工管理系統(tǒng)。
（2）機械零件的計算機管理系統(tǒng)國內外發(fā)展概況
人類進入21世紀以來，隨之信息化的飛速發(fā)展和世界經(jīng)濟的瘋狂增長，商業(yè)的復興，零件的管理無疑成為了國際國內的焦點。如何利用新時代的先進技術把這一傳統(tǒng)管理方式實現(xiàn)現(xiàn)代化和智能化已經(jīng)引起了國際國內業(yè)界的重視。因為這是企業(yè)管理中的一個重要環(huán)節(jié)和基礎。如果做好了企業(yè)的零件管理工作，對于保障企業(yè)生產的需要、降低成本、提高功效、減少積壓、加快物資周轉、杜絕浪費都有著積極的作用。通過對大中型工業(yè)企業(yè)零件管理方法的探討，來更好利用現(xiàn)代化的手段來提高零件管理的水平，從而增加企業(yè)盈利，增強企業(yè)的國際競爭力。
零件管理是企業(yè)管理的一個重要的環(huán)節(jié)和基礎。其基本工作是執(zhí)行零件出入庫動作和記錄保管貨物出入庫存信息，更重要的是管理系統(tǒng)可以即時提供各種相關報表，供管理者及時了解存貨狀況，以及時安排生產和適時作出合理的采購。
（3）應用前景
現(xiàn)代企業(yè)的物流系統(tǒng)日趨復雜，高效的物流系統(tǒng)要求有效地對企業(yè)的零件進行管理。目前的零件管理系統(tǒng)一般技術比較落后、性能較差且很不完備，人工干涉多，操作使用不方便，有的還故障率高而不實用。現(xiàn)階段零件管理的特點是信息處理量特別大，所管理的物資設備種類繁多，而且入庫單、出庫單、需求單等單據(jù)的發(fā)生量特別大，關聯(lián)信息多，查詢和統(tǒng)計的方式各不相同。因此在管理上實現(xiàn)起來有一定的困難。在管理的過程中經(jīng)常出現(xiàn)信息的重復傳遞等問題。倉儲管理部門越來越需要一套低成本、高性能、方便使用、功能完善的綜合零件管理信息系統(tǒng)。而現(xiàn)在計算機技術、網(wǎng)絡技術、的成熟與發(fā)展，為倉儲管理自動化提供了強有力的技術支持。課題以某零件應用背景，通過研究當前零件系統(tǒng)的管理現(xiàn)狀、存在問題以及現(xiàn)實需求，設計一個針對零件管理工作的管理信息系統(tǒng)。該系統(tǒng)能夠提供較為完備的功能，可以全面管理零件中儲存的商品和貨物，縮短了庫存信息流轉時間，使企業(yè)的物料管理層次分明，井然有序，為采購、銷售和生產提供依據(jù)，對于提高企業(yè)的經(jīng)營效率、加快零件管理的自動化具有重要的意義。
研究內容
① 調查研究、查閱文獻和搜集資料；
② 閱讀和翻譯與研究內容有關的外文資料；
③ 撰寫開題報告或文獻綜述，確定設計方案或研究方案；
④ 掌握visual studio等可視化編程工具；
⑤ 詳細設計方法（包括控制流程圖、功能模塊、數(shù)據(jù)流圖、程序框圖、開發(fā)關鍵技術等）或研究方法 ；
⑥ 設計或有關計算的源程序（或論點的證明或驗證）；
⑦ 撰寫畢業(yè)設計（論文）；
擬采取的研究方法、技術路線、實驗方案及可行性分析
（1）實驗方案
本課題的是根據(jù)一個車間的零件實際情況開發(fā)工作的，開發(fā)一個試用與此車間零件的信息管理系統(tǒng)?；贐/S結構的網(wǎng)絡版零件信息管理系統(tǒng)已經(jīng)時零件管理模式的主流。本系統(tǒng)采用動態(tài)網(wǎng)頁編程的最新技術——JSP技術開發(fā)基于B/S結構的零件信息管理系統(tǒng)，在功能上力求滿足該車間日常管理的需求，通過各種功能模塊的設計完成了企業(yè)利用Internet實現(xiàn)對零件信息進行管理的要求。通過建立基于B/S結構的零件信息管理系統(tǒng)，實現(xiàn)管理人員對零件信息管理的高效率和低成本，提高車間生產的工作效率，達到人、財、物盡其用，開源節(jié)流的目的。
（1） 研究方法
本課題的主要工作通過采用基于c語言的JSP技術構造動態(tài)網(wǎng)頁，充分發(fā)揮c語言所獨有的易用性、跨平臺性和安全性，運行效率高、安全可靠、使用性廣的員工信息管理系統(tǒng)。
研究計劃及預期成果
研究計劃：
2012年10月12日-2012年12月31日：按照任務書要求查閱論文相關參考資料，填寫畢業(yè)設計開題報告書。
2013年1月1日-2013年1月27日：填寫畢業(yè)實習報告。
2013年1月28日-2013年3月3日：按照要求修改畢業(yè)設計開題報告。
2013年3月4日-2013年3月17日：學習并翻譯一篇與畢業(yè)設計相關的英文材料。
2013年3月18日-2013年4月14日：C語言編輯
2013年4月15日-2013年4月28日：網(wǎng)頁編輯。
2013年4月29日-2013年5月20日：畢業(yè)論文撰寫和修改工作。
預期成果：
利用所開發(fā)的系統(tǒng)對車間零件的信息實施控制與管理。
特色或創(chuàng)新之處
1 可簡單的操作機械企業(yè)信息的管理（增、刪、改、查詢）。
2 對企業(yè)信息的管理實現(xiàn)了網(wǎng)絡化、信息化、圖形化和自動化。
已具備的條件和尚需解決的問題
① 解決在信息管理各個環(huán)結互不相通所造成的各種問題。
② 系統(tǒng)還需要完善界面的美觀，一些功能的完善，還需要算法的優(yōu)化。
指導教師意見
指導教師簽名：
年 月 日
教研室（學科組、研究所）意見
教研室主任簽名：
年 月 日
系意見
主管領導簽名：
年 月 日
英文原文
Warehouse Management Systems (WMS).
The evolution of warehouse management systems (WMS) is very similar to that of many other software solutions. Initially a system to control movement and storage of materials within a warehouse, the role of WMS is expanding to including light manufacturing, transportation management, order management, and complete accounting systems. To use the grandfather of operations-related software, MRP, as a comparison, material requirements planning (MRP) started as a system for planning raw material requirements in a manufacturing environment. Soon MRP evolved into manufacturing resource planning (MRPII), which took the basic MRP system and added scheduling and capacity planning logic. Eventually MRPII evolved into enterprise resource planning (ERP), incorporating all the MRPII functionality with full financials and customer and vendor management functionality. Now, whether WMS evolving into a warehouse-focused ERP system is a good thing or not is up to debate. What is clear is that the expansion of the overlap in functionality between Warehouse Management Systems, Enterprise Resource Planning, Distribution Requirements Planning, Transportation Management Systems, Supply Chain Planning, Advanced Planning and Scheduling, and Manufacturing Execution Systems will only increase the level of confusion among companies looking for software solutions for their operations.
Even though WMS continues to gain added functionality, the initial core functionality of a WMS has not really changed. The primary purpose of a WMS is to control the movement and storage of materials within an operation and process the associated transactions. Directed picking, directed replenishment, and directed put away are the key to WMS. The detailed setup and processing within a WMS can vary significantly from one software vendor to another, however the basic logic will use a combination of item, location, quantity, unit of measure, and order information to determine where to stock, where to pick, and in what sequence to perform these operations.
At a bare minimum, a WMS should:
Have a flexible location system.
Utilize user-defined parameters to direct warehouse tasks and use live documents to execute these tasks.
Have some built-in level of integration with data collection devices.
Do You Really Need WMS?
Not every warehouse needs a WMS. Certainly any warehouse could benefit from some of the functionality but is the benefit great enough to justify the initial and ongoing costs associated with WMS? Warehouse Management Systems are big, complex, data intensive, applications. They tend to require a lot of initial setup, a lot of system resources to run, and a lot of ongoing data management to continue to run. 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.
Setup
The setup requirements of WMS can be extensive. The characteristics of each item and location must be maintained either at the detail level or by grouping similar items and locations into categories. An example of item characteristics at the detail level would include exact dimensions and weight of each item in each unit of measure the item is stocked (each, cases, pallets, etc) as well as information such as whether it can be mixed with other items in a location, whether it is rack able, max stack height, max quantity per location, hazard classifications, finished goods or raw material, fast versus slow mover, etc. Although some operations will need to set up each item this way, most operations will benefit by creating groups of similar products. For example, if you are a distributor of music CDs you would create groups for single CDs, and double CDs, maintaining the detailed dimension and weight information at the group level and only needing to attach the group code to each item. You would likely need to maintain detailed information on special items such as boxed sets or CDs in special packaging. You would also create groups for the different types of locations within your warehouse. An example would be to create three different groups (P1, P2, P3) for the three different sized forward picking locations you use for your CD picking. You then set up the quantity of single CDs that will fit in a P1, P2, and P3 location, quantity of double CDs that fit in a P1, P2, P3 location etc. You would likely also be setting up case quantities, and pallet quantities of each CD group and quantities of cases and pallets per each reserve storage location group.
If this sounds simple, it 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 assigning specific logic to the various combinations of item/order/quantity/location information that will occur.
Below I have listed some of the logic used in determining actual locations and sequences.
Location Sequence. This is the simplest logic; you simply define a flow through your warehouse and assign a sequence number to each location. In order picking this is used to sequence your picks to flow through the warehouse, in put away the logic would look for the first location in the sequence in which the product would fit.
Zone Logic. By breaking down your storage locations into zones you can direct picking, put away, or replenishment to or from specific areas of your warehouse. Since zone logic only designates an area, you will need to combine this with some other type of logic to determine exact location within the zone.
Fixed Location. Logic uses predetermined fixed locations per item in picking, put away, and replenishment. Fixed locations are most often used as the primary picking location in piece pick and case-pick operations, however, they can also be used for secondary storage.
Random Location. Since computers cannot be truly random (nor would you want them to be) the term random location is a little misleading. Random locations generally refer to areas where products are not stored in designated fixed locations. Like zone logic, you will need some additional logic to determine exact locations.
First-in-first-out (FIFO). Directs picking from the oldest inventory first.
Last-in-first-out (LIFO). Opposite of FIFO. I 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/Considerations
Wave 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 want to consider this during the software selection process. Since these types of automation are very expensive and are usually a core component of your warehouse, you may find that the equipment will drive the selection of the WMS. As with automated data collection, you should be working closely with the equipment manufacturers during the software selection process.
Advanced Shipment Notifications (ASN). If your vendors are capable of sending advanced shipment notifications (preferably electronically) and attaching compliance labels to the shipments you will want to make sure that the WMS can use this to automate your receiving process. In addition, if you have requirements to provide ASNs for customers, you will also want to verify this functionality. ?
Yard Management. Yard management describes the function of managing the contents (inventory) of trailers parked outside the warehouse, or the empty trailers themselves. Yard management is generally associated with cross docking operations and may include the management of both inbound and outbound trailers.
Labor Tracking/Capacity Planning. Some WMS systems provide functionality related to labor reporting and capacity planning. Anyone that has worked in manufacturing should be familiar with this type of logic. Basically, you set up standard labor hours and machine (usually lift trucks) hours per task and set the available labor and machine hours per shift. The WMS system will use this info to determine capacity and load. Manufacturing has been using capacity planning for decades with mixed results. The need to factor in efficiency and utilization to determine rated capacity is an example of the shortcomings of this process. Not that I’m necessarily against capacity planning in warehousing, I just think most operations don’t really need it and can avoid the disappointment of trying to make it work. I am, however, a big advocate of labor tracking for individual productivity measurement. Most WMS maintain enough data to create productivity reporting. Since productivity is measured differently from one operation to another you can assume you will have to do some minor modifications here (usually in the form of custom reporting).
Integration with existing accounting/ERP systems. Unless the WMS vendor has already created a specific interface with your accounting/ERP system (such as those provided by an approved business partner) you can expect to spend some significant programming dollars here. While we are all hoping that integration issues will be magically resolved someday by a standardized interface, we isn’t there yet. Ideally you’ll want an integrator that has already integrated the WMS you chose with the business software you are using. Since this is not always possible you at least want an integrator that is very familiar with one of the systems.
WMS + everything else = ? As I mentioned at the beginning of this article, a lot of other modules are being added to WMS packages. These would include full financials, light manufacturing, transportation management, purchasing, and sales order management. I don’t see this as a unilateral move of WMS from an add-on module to a core system, but rather an optional approach that has applications in specific industries such as 3PLs. Using ERP systems as a point of reference, it is unlikely that this add-on functionality will match the functionality of best-of-breed applications available separately. If warehousing/distribution is your core business function and you don’t want to have to deal with the integration issues of incorporating separate financials, order processing, etc. you may find these WMS based business systems are a good fit. ?
Implementation Tips
Outside of the standard “don’t underestimate”, “thoroughly test”, “train, train, train” implementation tips that apply to any business software installation ,it’s important to 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.
中文譯文
倉庫管理系統(tǒng)（ WMS ）
倉庫管理系統(tǒng)（ WMS ）的演變與許多其他軟件解決方案是很像的。最初的系統(tǒng)用來控制物料在倉庫內的流動和貯存，倉庫的作用正在延伸到包括輕型制造業(yè)，交通運輸管理，訂單管理，和完整的會計制度中。利用與先前的業(yè)務有關的軟件，制造資源