Must be able to use MS projectConveyor Belt Project- Part 1.docx
Download as DOCX, PDF0 likes64 views
The document outlines a project for a new computer-controlled conveyor belt that aims to enhance efficiency in item movement and positioning with high precision. It highlights the project's potential to be integrated into 30% of factory systems and emphasizes low costs and ease of future upgrades. Additionally, it provides a project priority matrix and tasks related to developing the work breakdown structure (WBS) using Microsoft Project.
1 of 3
Download to read offline
More Related Content
Similar to Must be able to use MS projectConveyor Belt Project- Part 1.docx (20)
Ad
More from jacmariek5 (20)
Ad
Must be able to use MS projectConveyor Belt Project- Part 1.docx
- 1. Must be able to use MS project Conveyor Belt Project- Part 1 Project Description The new computer-controlled conveyor belt is an exciting project that moves and positions items on the conveyor belt within < J millimeter. The project will produce a new system for future installations, and for replacement of those in the field, at a low cost. The computer-controlled conveyor belt has the potential to be a critical unit in 30 percent of the systems installed in factories. The new system is also easier to update with future technologies. The Project Priority Matrix for the Conveyor Belt Project (CBP) is: time scope cost constrain X enhance X accept X
- 2. *Table A2.9 has been developed for you to use in completing the project exercise Assignment action: Develop the WBS outline using Microsoft project. Question: Does this information (in the WBS) allow you to define any milestones of the project? Why or why not? What are they? TABLE A2.9 -Conveyor Belt Project; WBS Hardware Hardware specifications Hardware design Hardware documentation Prototypes Order circuit boards Operating systems Kernel specifications Drivers Disk drivers Serial I/O drivers Memory management Operating system documentation NetWork interface
- 3. Utilitites Utilities specifications Routine utilities Complex utilities Utilities documentation Shell System Integration Architectural decisions Integration first phase System hard/software test Project documentation Integration acceptance testing