Conveyor Belt

2193 Words9 Pages
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: Constrain Enhance Accept Assignment Develop the WBS outline using the software available to you. TABLE A2.6 Conveyor Belt Project; WBS Conveyor Belt Project…show more content…
Remember the old saying, "A project plan is not a schedule until resources are committed." This exercise illustrates this subtle, but very important, difference. Part A Using your files from Part 2 input resources and their costs if you have not already done so. All information is found in Tables A2.7 and A2.8. Prepare a memo that addresses the following questions: 1. Which if any of the resources are overallocated? 2. Assume that the project is time constrained and try to resolve any overallocation problems by leveling within slack. What happens? 3. What is the impact of leveling within slack on the sensitivity of the network? Include a Gantt chart with the schedule table after leveling within slack. 4. Assume the project is resource constrained and resolve any overallocation problems by leveling outside of slack. What happens? What are the managerial implications? 5. What options are available at this point in time? Include a Gantt chart with the schedule table after leveling outside of slack. Note: No splitting of activities is allowed. Note: No partial assignments (i.e., 50 percent). All resources must be assigned 100 percent. When you show the resource-constrained network to top management, they are visibly shaken. After some explanation and negotiation they make the following compromise with you: • The project must be completed no later than February 2, 2012 (530 days). • You may assign two additional development teams. TABLE A2.8
Open Document