资源目录
压缩包内文档预览：
编号：122571939
类型：共享资源
大小：403.23KB
格式：ZIP
上传时间：2021-04-20
上传人：221589****qq.com
认证信息
个人认证
李**（实名认证）
湖南
IP属地：湖南
40
积分
- 关 键 词：
-
基于
PLC
立体仓库
设计
- 资源描述：
-
基于PLC的立体仓库的设计,基于,PLC,立体仓库,设计
- 内容简介：
-
编号无锡太湖学院毕业设计（论文）相关资料题目： 机械零件的计算机管理系统 信机 系 机械工程及自动化专业学 号： 0923078学生姓名： 蔡天华 指导教师： 王士同 （职称：教授） （职称： ）2013年5月25日目 录一、毕业设计（论文）开题报告二、毕业设计（论文）外文资料翻译及原文三、学生“毕业论文（论文）计划、进度、检查及落实表”四、实习鉴定表无锡太湖学院毕业设计（论文）开题报告题目： 机械零件的计算机管理系统 信机 系 机械工程及自动化 专业学 号： 0923078 学生姓名： 蔡天华 指导教师： 王士同 （职称：教授 ） （职称： ）2012年11月20日 课题来源参照老师意见，确立此题目科学依据（包括课题的科学意义；国内外研究概况、水平和发展趋势；应用前景等）（1）课题科学意义在机遇与挑战并存的前提下，企业面临着前所未有的竞争压力，企业必须尽快的调整内部的产业结构，转换管理方式，建立一套适合自身发展的管理系统来面对市场的挑战。目前市面上流行的员工管理系统不少。但是，对于不同企业的员工管理系统来说，需要一个符合自己企业制度的员工管理系统，只需要一个操作方便，功能实用，能满足企业对员工的日常管理就可以了。本系统的目的就是在于开发一个功能实用、操作方便，简单明了的员工管理系统。（2）机械零件的计算机管理系统国内外发展概况人类进入21世纪以来，随之信息化的飞速发展和世界经济的疯狂增长，商业的复兴，零件的管理无疑成为了国际国内的焦点。如何利用新时代的先进技术把这一传统管理方式实现现代化和智能化已经引起了国际国内业界的重视。因为这是企业管理中的一个重要环节和基础。如果做好了企业的零件管理工作，对于保障企业生产的需要、降低成本、提高功效、减少积压、加快物资周转、杜绝浪费都有着积极的作用。通过对大中型工业企业零件管理方法的探讨，来更好利用现代化的手段来提高零件管理的水平，从而增加企业盈利，增强企业的国际竞争力。零件管理是企业管理的一个重要的环节和基础。其基本工作是执行零件出入库动作和记录保管货物出入库存信息，更重要的是管理系统可以即时提供各种相关报表，供管理者及时了解存货状况，以及时安排生产和适时作出合理的采购。（3）应用前景现代企业的物流系统日趋复杂，高效的物流系统要求有效地对企业的零件进行管理。目前的零件管理系统一般技术比较落后、性能较差且很不完备，人工干涉多，操作使用不方便，有的还故障率高而不实用。现阶段零件管理的特点是信息处理量特别大，所管理的物资设备种类繁多，而且入库单、出库单、需求单等单据的发生量特别大，关联信息多，查询和统计的方式各不相同。因此在管理上实现起来有一定的困难。在管理的过程中经常出现信息的重复传递等问题。仓储管理部门越来越需要一套低成本、高性能、方便使用、功能完善的综合零件管理信息系统。而现在计算机技术、网络技术、的成熟与发展，为仓储管理自动化提供了强有力的技术支持。课题以某零件应用背景，通过研究当前零件系统的管理现状、存在问题以及现实需求，设计一个针对零件管理工作的管理信息系统。该系统能够提供较为完备的功能，可以全面管理零件中储存的商品和货物，缩短了库存信息流转时间，使企业的物料管理层次分明，井然有序，为采购、销售和生产提供依据，对于提高企业的经营效率、加快零件管理的自动化具有重要的意义。研究内容 调查研究、查阅文献和搜集资料； 阅读和翻译与研究内容有关的外文资料； 撰写开题报告或文献综述，确定设计方案或研究方案； 掌握visual studio等可视化编程工具； 详细设计方法（包括控制流程图、功能模块、数据流图、程序框图、开发关键技术等）或研究方法 ； 设计或有关计算的源程序（或论点的证明或验证）； 撰写毕业设计（论文）；拟采取的研究方法、技术路线、实验方案及可行性分析（1）实验方案本课题的是根据一个车间的零件实际情况开发工作的，开发一个试用与此车间零件的信息管理系统。基于B/S结构的网络版零件信息管理系统已经时零件管理模式的主流。本系统采用动态网页编程的最新技术JSP技术开发基于B/S结构的零件信息管理系统，在功能上力求满足该车间日常管理的需求，通过各种功能模块的设计完成了企业利用Internet实现对零件信息进行管理的要求。通过建立基于B/S结构的零件信息管理系统，实现管理人员对零件信息管理的高效率和低成本，提高车间生产的工作效率，达到人、财、物尽其用，开源节流的目的。（1） 研究方法本课题的主要工作通过采用基于c语言的JSP技术构造动态网页，充分发挥c语言所独有的易用性、跨平台性和安全性，运行效率高、安全可靠、使用性广的员工信息管理系统。研究计划及预期成果研究计划：2012年10月12日-2012年12月31日：按照任务书要求查阅论文相关参考资料，填写毕业设计开题报告书。2013年1月1日-2013年1月27日：填写毕业实习报告。2013年1月28日-2013年3月3日：按照要求修改毕业设计开题报告。2013年3月4日-2013年3月17日：学习并翻译一篇与毕业设计相关的英文材料。2013年3月18日-2013年4月14日：C语言编辑2013年4月15日-2013年4月28日：网页编辑。2013年4月29日-2013年5月20日：毕业论文撰写和修改工作。预期成果：利用所开发的系统对车间零件的信息实施控制与管理。特色或创新之处1 可简单的操作机械企业信息的管理（增、删、改、查询）。2 对企业信息的管理实现了网络化、信息化、图形化和自动化。已具备的条件和尚需解决的问题 解决在信息管理各个环结互不相通所造成的各种问题。 系统还需要完善界面的美观，一些功能的完善，还需要算法的优化。指导教师意见 指导教师签名：年 月 日教研室（学科组、研究所）意见 教研室主任签名： 年 月 日系意见 主管领导签名： 年 月 日英文原文Warehouse Management Systems (WMS).The evolution of warehouse management systems (WMS) is very similar to that of many other software solutions. Initially a system to control movement and storage of materials within a warehouse, the role of WMS is expanding to including light manufacturing, transportation management, order management, and complete accounting systems. To use the grandfather of operations-related software, MRP, as a comparison, material requirements planning (MRP) started as a system for planning raw material requirements in a manufacturing environment. Soon MRP evolved into manufacturing resource planning (MRPII), which took the basic MRP system and added scheduling and capacity planning logic. Eventually MRPII evolved into enterprise resource planning (ERP), incorporating all the MRPII functionality with full financials and customer and vendor management functionality. Now, whether WMS evolving into a warehouse-focused ERP system is a good thing or not is up to debate. What is clear is that the expansion of the overlap in functionality between Warehouse Management Systems, Enterprise Resource Planning, Distribution Requirements Planning, Transportation Management Systems, Supply Chain Planning, Advanced Planning and Scheduling, and Manufacturing Execution Systems will only increase the level of confusion among companies looking for software solutions for their operations. Even though WMS continues to gain added functionality, the initial core functionality of a WMS has not really changed. The primary purpose of a WMS is to control the movement and storage of materials within an operation and process the associated transactions. Directed picking, directed replenishment, and directed put away are the key to WMS. The detailed setup and processing within a WMS can vary significantly from one software vendor to another, however the basic logic will use a combination of item, location, quantity, unit of measure, and order information to determine where to stock, where to pick, and in what sequence to perform these operations. At a bare minimum, a WMS should:Have a flexible location system.Utilize user-defined parameters to direct warehouse tasks and use live documents to execute these tasks.Have some built-in level of integration with data collection devices.Do You Really Need WMS?Not every warehouse needs a WMS. Certainly any warehouse could benefit from some of the functionality but is the benefit great enough to justify the initial and ongoing costs associated with WMS? Warehouse Management Systems are big, complex, data intensive, applications. They tend to require a lot of initial setup, a lot of system resources to run, and a lot of ongoing data management to continue to run. Thats right, you need to manage your warehouse management system. Often times, large operations will end up creating a new IS department with the sole responsibility of managing the WMS. The Claims: WMS will reduce inventory! WMS will reduce labor costs! WMS will increase storage capacity! WMS will increase customer service! WMS will increase inventory accuracy! The Reality: The implementation of a WMS along with automated data collection will likely give you increases in accuracy, reduction in labor costs (provided the labor required to maintain the system is less than the labor saved on the warehouse floor), and a greater ability to service the customer by reducing cycle times. Expectations of inventory reduction and increased storage capacity are less likely. While increased accuracy and efficiencies in the receiving process may reduce the level of safety stock required, the impact of this reduction will likely be negligible in comparison to overall inventory levels. The predominant factors that control inventory levels are lot sizing, lead times, and demand variability. It is unlikely that a WMS will have a significant impact on any of these factors. And while a WMS certainly provides the tools for more organized storage which may result in increased storage capacity, this improvement will be relative to just how sloppy your pre-WMS processes were. Beyond labor efficiencies, the determining factors in deciding to implement a WMS tend to be more often associated with the need to do something to service your customers that your current system does not support (or does not support well) such as first-in-first-out, cross-docking, automated pick replenishment, wave picking, lot tracking, yard management, automated data collection, automated material handling equipment, etc.Setup The setup requirements of WMS can be extensive. The characteristics of each item and location must be maintained either at the detail level or by grouping similar items and locations into categories. An example of item characteristics at the detail level would include exact dimensions and weight of each item in each unit of measure the item is stocked (each, cases, pallets, etc) as well as information such as whether it can be mixed with other items in a location, whether it is rack able, max stack height, max quantity per location, hazard classifications, finished goods or raw material, fast versus slow mover, etc. Although some operations will need to set up each item this way, most operations will benefit by creating groups of similar products. For example, if you are a distributor of music CDs you would create groups for single CDs, and double CDs, maintaining the detailed dimension and weight information at the group level and only needing to attach the group code to each item. You would likely need to maintain detailed information on special items such as boxed sets or CDs in special packaging. You would also create groups for the different types of locations within your warehouse. An example would be to create three different groups (P1, P2, P3) for the three different sized forward picking locations you use for your CD picking. You then set up the quantity of single CDs that will fit in a P1, P2, and P3 location, quantity of double CDs that fit in a P1, P2, P3 location etc. You would likely also be setting up case quantities, and pallet quantities of each CD group and quantities of cases and pallets per each reserve storage location group. If this sounds simple, it iswell sort of. In reality most operations have a much more diverse product mix and will require much more system setup. And setting up the physical characteristics of the product and locations is only part of the picture. You have set up enough so that the system knows where a product can fit and how many will fit in that location. You now need to set up the information needed to let the system decide exactly which location to pick from, replenish from/to, and put away to, and in what sequence these events should occur (remember WMS is all about “directed” movement). You do this by assigning specific logic to the various combinations of item/order/quantity/location information that will occur. Below I have listed some of the logic used in determining actual locations and sequences. Location Sequence. This is the simplest logic; you simply define a flow through your warehouse and assign a sequence number to each location. In order picking this is used to sequence your picks to flow through the warehouse, in put away the logic would look for the first location in the sequence in which the product would fit. Zone Logic. By breaking down your storage locations into zones you can direct picking, put away, or replenishment to or from specific areas of your warehouse. Since zone logic only designates an area, you will need to combine this with some other type of logic to determine exact location within the zone. Fixed Location. Logic uses predetermined fixed locations per item in picking, put away, and replenishment. Fixed locations are most often used as the primary picking location in piece pick and case-pick operations, however, they can also be used for secondary storage. Random Location. Since computers cannot be truly random (nor would you want them to be) the term random location is a little misleading. Random locations generally refer to areas where products are not stored in designated fixed locations. Like zone logic, you will need some additional logic to determine exact locations. First-in-first-out (FIFO). Directs picking from the oldest inventory first. Last-in-first-out (LIFO). Opposite of FIFO. I didnt think there were any real applications for this logic until a visitor to my site sent an email describing their operation that distributes perishable goods domestically and overseas. They use LIFO for their overseas customers (because of longer in-transit times) and FIFO for their domestic customers. Pick-to-clear. Logic directs picking to the locations with the smallest quantities on hand. This logic is great for space utilization. Reserved Locations. This is used when you want to predetermine specific locations to put away to or pick from. An application for reserved locations would be cross-docking, where you may specify certain quantities of an inbound shipment be moved to specific outbound staging locations or directly to an awaiting outbound trailer. Maximize Cube. Cube logic is found in most WMS systems however it is seldom used. Cube logic basically uses unit dimensions to calculate cube (cubic inches per unit) and then compares this to the cube capacity of the location to determine how much will fit. Now if the units are capable of being stacked into the location in a manner that fills every cubic inch of space in the location, cube logic will work. Since this rarely happens in the real world, cube logic tends to be impractical. Consolidate. Looks to see if there is already a location with the same product stored in it with available capacity. May also create additional moves to consolidate like product stored in multiple locations. Lot Sequence. Used for picking or replenishment, this will use the lot number or lot date to determine locations to pick from or replenish from. Its very common to combine multiple logic methods to determine the best location. For example you may chose to use pick-to-clear logic within first-in-first-out logic when there are multiple locations with the same receipt date. You also may change the logic based upon current workload. During busy periods you may chose logic that optimizes productivity while during slower periods you switch to logic that optimizes space utilization. Other Functionality/ConsiderationsWave Picking/Batch Picking/Zone Picking. Support for various picking methods varies from one system to another. In high-volume fulfillment operations, picking logic can be a critical factor in WMS selection. See my article on Order Picking for more info on these methods. Task Interleaving. Task interleaving describes functionality that mixes dissimilar tasks such as picking and put away to obtain maximum productivity. Used primarily in full-pallet-load operations, task interleaving will direct a lift truck operator to put away a pallet on his/her way to the next pick. In large warehouses this can greatly reduce travel time, not only increasing productivity, but also reducing wear on the lift trucks and saving on energy costs by reducing lift truck fuel consumption. Task interleaving is also used with cycle counting programs to coordinate a cycle count with a picking or put away task. Integration with Automated Material Handling Equipment. If you are planning on using automated material handling equipment such as carousels, ASRS units, AGNS, pick-to-light systems, or separation systems, youll want to consider this during the software selection process. Since these types of automation are very expensive and are usually a core component of your warehouse, you may find that the equipment will drive the selection of the WMS. As with automated data collection, you should be working closely with the equipment manufacturers during the software selection process. Advanced Shipment Notifications (ASN). If your vendors are capable of sending advanced shipment notifications (preferably electronically) and attaching compliance labels to the shipments you will want to make sure that the WMS can use this to automate your receiving process. In addition, if you have requirements to provide ASNs for customers, you will also want to verify this functionality. Yard Management. Yard management describes the function of managing the contents (inventory) of trailers parked outside the warehouse, or the empty trailers themselves. Yard management is generally associated with cross docking operations and may include the management of both inbound and outbound trailers. Labor Tracking/Capacity Planning. Some WMS systems provide functionality related to labor reporting and capacity planning. Anyone that has worked in manufacturing should be familiar with this type of logic. Basically, you set up standard labor hours and machine (usually lift trucks) hours per task and set the available labor and machine hours per shift. The WMS system will use this info to determine capacity and load. Manufacturing has been using capacity planning for decades with mixed results. The need to factor in efficiency and utilization to determine rated capacity is an example of the shortcomings of this process. Not that Im necessarily against capacity planning in warehousing, I just think most operations dont really need it and can avoid the disappointment of trying to make it work. I am, however, a big advocate of labor tracking for individual productivity measurement. Most WMS maintain enough data to create productivity reporting. Since productivity is measured differently from one operation to another you can assume you will have to do some minor modifications here (usually in the form of custom reporting). Integration with existing accounting/ERP systems. Unless the WMS vendor has already created a specific interface with your accounting/ERP system (such as those provided by an approved business partner) you can expect to spend some significant programming dollars here. While we are all hoping that integration issues will be magically resolved someday by a standardized interface, we isnt there yet. Ideally youll want an integrator that has already integrated the WMS you chose with the business software you are using. Since this is not always possible you at least want an integrator that is very familiar with one of the systems. WMS + everything else = ? As I mentioned at the beginning of this article, a lot of other modules are being added to WMS packages. These would include full financials, light manufacturing, transportation management, purchasing, and sales order management. I dont see this as a unilateral move of WMS from an add-on module to a core system, but rather an optional approach that has applications in specific industries such as 3PLs. Using ERP systems as a point of reference, it is unlikely that this add-on functionality will match the functionality of best-of-breed applications available separately. If warehousing/distribution is your core business function and you dont want to have to deal with the integration issues of incorporating separate financials, order processing, etc. you may find these WMS based business systems are a good fit. Implementation TipsOutside of the standard “dont underestimate”, “thoroughly test”, “train, train, train” implementation tips that apply to any business software installation ,its important to emphasize that WMS are very data dependent and restrictive by design. That is, you need to have all of the various data elements in place for the system to function properly. And, when they are in place, you must operate within the set parameters.When implementing a WMS, you are adding an additional layer of technology onto your system. And with each layer of technology there is additional overhead and additional sources of potential problems. Now dont take this as a condemnation of Warehouse Management Systems. Coming from a warehousing background I definitely appreciate the functionality WMS have to offer, and, in many warehouses, this functionality is essential to their ability to serve their customers and remain competitive. Its just important to note that every solution has its downsides and having a good understanding of the potential implications will allow managers to make better decisions related to the levels of technology that best suits their unique environment. 中文译文仓库管理系统（ WMS ）仓库管理系统（ WMS ）的演变与许多其他软件解决方案是很像的。最初的系统用来控制物料在仓库内的流动和贮存，仓库的作用正在延伸到包括轻型制造业，交通运输管理，订单管理，和完整的会计制度中。利用与先前的业务有关的软件，制造资源计划，作为一个比较，材料需求计划（ MRP ）开始作为一个规划要求，原材料的生产环境的系统。 物料需求计划很快演变成以MRP系统，补充调度和容量规划为基础的逻辑制造资源计划（ MRPII系统）。最终MRPII系统演变成企业资源规划（ ERP ），吸收所有的MRPII系统的功能包括充分的财务与客户和供应商管理功能。现在，无论仓库管理系统演变成一个以仓库为中心的ERP系统是一件好事或不可达的辩论。清楚的是，在仓库管理系统，企业资源规划，布局规划要求，交通运输管理系统，供应链计划，高级计划与排程，以及制造执行系统之间扩大重叠功能性只会增加那些寻找软件解决方案业务的公司混乱水平。 尽管仓库继续获得额外的功能，最初的仓库管理系统的核心功能还没有真正改变。其主要目的是控制管理系统在工艺操作相关联的交易中的流动和材料储存。定向采摘，定向补充，定向收集是仓库的关键。从一个软件供应商到另一个在一个管理系统中详细的安装和处理可以有一个很大的差别，但是其基本逻辑将使用相结合的项目，地点，数量，度量单位，并以收集信息以确定在哪里储存，在哪里挑选，以及以何种顺序执行这些操作。 最低限度，一个仓库管理系统应采取下列措施 有一个灵活的定位系统。 利用用户定义的参数，指导仓库任务和使用Live文件来执行这些任务。 有一些内置的一体化和数据收集设备结合体。 您是否真的需要仓库管理系统？ 并非每一个仓库需要一个仓库管理系统。当然，任何仓库可受益于其中一些功能，但这些受益是否足以证明管理系统最初的和正在进行的相关费用是正确的？仓库管理系统是大的，复杂的，数据密集型的应用。他们往往需要大量的初始安装，很多系统资源的运行，很多正在进行的数据管理为继续运行。没错，你需要“管理”你的仓库“管理”制度。一般情况下，大规模的行动最终将建立一个新的IS部门用来唯一负责管理仓库管理系统。 声明1仓库管理系统将减少库存！2仓库管理系统将减少劳动力成本!3仓库管理系统将增加存储容量！ 4仓库管理系统将提高客户服务！5仓库管理系统将增加库存的准确性 ！ 现实 实施一个仓库管理系统用来自动的数据收集将可能使你的准确性增加，减少劳动力成本（提供需要维持系统的劳动力少于物品保存在仓库楼需要的劳动力）和更好地来服务客户以降低周期。预期库存减少和增加存储容量的可能性较小。虽然在接收过程中增加了准确性和效率可能降低库存安全水平，但这种降低产生的影响与整体库存水平相比可以忽略不计。控制库存水平批量最主要的因素是多种尺寸，交货时间和需求的变化，仓库管理系统将对任何因素有重大影响是不可能。而且同时仓库管理系统确实的为更多的有组织的存储提供工具，因为这种存储可能会导致更多的存储容量，相对于这种改善您之前的仓库管理系统是多么草率啊。除了劳动效率，决定实施仓库管理系统的决定因素，往往与一些能满足您的客户的需求有更多关联，比如您目前的系统不支持（或不太支持）像先进先出，交叉对接，自动挑选补充，波采摘，多种跟踪，停车场管理，自动数据采集，自动材料处理设备等 。设置 仓库管理系统的设置需求是广泛的，每个项目和地点都必须保持在详细或分组类似项目和地点分类。一个例子，项目详细程度的特点将包括确切尺寸和重量，每个项目在每个单位的项目储备（项目，案件，托盘等），以及信息，如是否可以与其他物品混在一个位置，无论是的最高层次，最大堆叠高度，最高量的位置，危险性分类，半成品或原材料，快与慢动，等。尽管一些行动将需要用这种方式设立每个项目，但大多数业务将有利于创造群体的类似产品。例如，如果你是一个音乐CD分销商，您将创建集团单一CD和双张CD ，保持详细的尺寸和重量的资料在组一级，只需要对每个项目附上组代码。您可能会需要对特殊物品保持详细的资料，如盒装套或CD的特别包装。您也可以为地域的不同类型在您的仓库里创造群组。一个例子是，为您用于CD采摘的三种不同大小前瞻性采摘地点建立3个不同群体（小一，二，三）。然后，您可以建立单一的光盘数量，将适合P1，P2和P3的位置，多种双张CD适合在小一，二，小三的位置等。您可能还设立案件的数量，每个CD组光盘数量,货箱的数量和光盘的每个后备存储位置组。如果这听起来很简单，但在现实中很多业务有更多元化的产品组合，将需要更多的系统设置。而且建立产品的物理特性和产品的位置只是蓝图的部分。你设定的使系统知道产品可以适合哪里并且多少产品将满足这个地方已经足够了。您现在需要建立必要的信息，以让系统决定从哪些位置选择，补充，并采集，并在这些事件应该出现这些序列中（记得仓库管理就是“指示”流动）。你分配具体逻辑的的做法使各种组合项目/订单/数量/位置信息将出现。 下面我列出一些用于确定实际位置和序列的逻辑1) 位置顺序。这是最简单的逻辑;您只需确定流经你的仓库和为每一个地点分配序列编号。 为了挑选这是把您选择的在流经的仓库排序，在采集逻辑将寻求在第一位置的顺序适合的产品。 2) 区逻辑 。由于把你的储存地点分到区，您可以直接采摘，收集，或补充或特定地区的仓库。自区逻辑唯一指定的一个地区，则需要再加上一些其他类型的逻辑，以确定确切位置在禁区内。 3) 固定的位置。 逻辑使用预先确定的固定地点，每一项目中分拣，采集 ，和补充。固定地点是一块采摘挑选和个案选择的行动最常用的首要位置，但是，它们也可用于二级存储。4) 随机地点。由于电脑不能真正随机（也不想要他们）的任期随机位置有点误导。 随机地点一般指的是产品不会储存在指定的固定地点的地方。如Zone逻辑，您将需要一些额外的逻辑，以确定确切位置。5) 先入先出（ FIFO的）。首
- 温馨提示:
1: 本站所有资源如无特殊说明，都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
2: 本站的文档不包含任何第三方提供的附件图纸等，如果需要附件，请联系上传者。文件的所有权益归上传用户所有。
3.本站RAR压缩包中若带图纸，网页内容里面会有图纸预览，若没有图纸预览就没有图纸。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 人人文库网仅提供信息存储空间，仅对用户上传内容的表现方式做保护处理，对用户上传分享的文档内容本身不做任何修改或编辑，并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容，请与我们联系，我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。
人人文库网所有资源均是用户自行上传分享，仅供网友学习交流，未经上传用户书面授权，请勿作他用。
川公网安备: 51019002004831号