Section C is what i really needed ,and I will surely give thumbs up and good remarks for the life saver who help me to do my section C first.....I uploaded section B because the the section C refers it. thank you

Section C-Crashing the Project Upper level management has now seen your project plan. They need the project fully installed prior to the new fiscal year, because they want to make a positive announcement to shareholders. This means that the project must be completed in 40 days. They have indicated that all resources needed will be available. Using the following costing data, and using your project design from Section B, provide a log that demonstrates the most cost-effective way to reduce the project duration down to no more than 40 days There are two ways that you can quickly speed up the project. The first is to use outsourced services. The activities are coded according to the type of labour - General, Skilled, and Unskilled. Activities that use General labour must be internal, and these durations cannot be crashed. Skilled and unskilled labour can both be outsourced. The second way that costs can be reduced is to lessen the waiting time to receive the new workstations. Currently the cost is $1,000 to configure the workstations and deliver in 20 days. However, there is an option to reduce the delivery time to 10 days if the configuration fee is increased to $5,000. Indirect costs for the project are estimated to be $500/d. See the following page for the data required and a template of the activity log. I 1) ii) Create a completed data table and activity log that demonstrates crashing the project to 40 days using the most cost-effective means. Use the standard methodology used in class. What are the new direct, indirect and total costs for the project? Even if we did not need to reduce the project duration, would it have made sense to do so, and to what point? What new risks have been introduced by crashing the project in this way? iv) This section is worth 20 points. Predecessor Crash Duration 2 8 A Duration 2 10 3 2. 6 C D A E B 10 1 Activity SW Decision Stakeholder input ID Data Sources 08 Setup Draft Di Design Data Cleaning Spec Workstation Ur Testing bate Validation DE Test Order workstations UI Sign off Load data install workstations integrate UL. Database Final User test E E Cost type General Unskilled Skilled Unskilled Skilled Unskilled General Skilled Skilled Unskilled Unskilled General Unskilled Unskilled Skilled General 1 15 Norrmal Cost 600 2,000 900 400 1,800 2,000 200 4,500 3,600 1.000 1,000 300 800 1,600 1.500 2.400 10 3 Crash Cost 500 3,500 1,400 450 2,800 2,700 200 7.000 5,600 1.800 5.000 300 1,350 2,700 2,100 2,400 DF 5 20 K 1 10 H M 1 4 8 3 LM N,O 5 8 3 Section B - Network Design Having chosen the software project, you are now provided with a work breakdown structure (WBS) for the project, provided by your IT department. These estimates are based on four similar software installations completed during the past two years. ID Predecessor A Duration 2 10 3 B A C A A 2 D E F B 6 C 10 1 H Activity SW Decision Stakeholder Input ID Data Sources DB Setup Draft UI Design Data Cleaning Spec Workstation UI Testing Data Validation DB Test Order workstations UI Sign off Load data install workstations integrate UI, Database Final User test 15 1 DF 12 5 20 K G L H 1 M 4 N 8 LM 5 8 P NO 1) Construct a network design logic diagram using this WBS. Use the ID and activity description to clearly identify each note. Complete a forward pass and backward pass and identity the slack times. Identify and clearly indicate the critical path. Discuss critical path sensitity, and how sensitive this network is to changing the critical path iv) This section is worth 20 marks. Section C-Crashing the Project Upper level management has now seen your project plan. They need the project fully installed prior to the new fiscal year, because they want to make a positive announcement to shareholders. This means that the project must be completed in 40 days. They have indicated that all resources needed will be available. Using the following costing data, and using your project design from Section B, provide a log that demonstrates the most cost-effective way to reduce the project duration down to no more than 40 days There are two ways that you can quickly speed up the project. The first is to use outsourced services. The activities are coded according to the type of labour - General, Skilled, and Unskilled. Activities that use General labour must be internal, and these durations cannot be crashed. Skilled and unskilled labour can both be outsourced. The second way that costs can be reduced is to lessen the waiting time to receive the new workstations. Currently the cost is $1,000 to configure the workstations and deliver in 20 days. However, there is an option to reduce the delivery time to 10 days if the configuration fee is increased to $5,000. Indirect costs for the project are estimated to be $500/d. See the following page for the data required and a template of the activity log. I 1) ii) Create a completed data table and activity log that demonstrates crashing the project to 40 days using the most cost-effective means. Use the standard methodology used in class. What are the new direct, indirect and total costs for the project? Even if we did not need to reduce the project duration, would it have made sense to do so, and to what point? What new risks have been introduced by crashing the project in this way? iv) This section is worth 20 points. Predecessor Crash Duration 2 8 A Duration 2 10 3 2. 6 C D A E B 10 1 Activity SW Decision Stakeholder input ID Data Sources 08 Setup Draft Di Design Data Cleaning Spec Workstation Ur Testing bate Validation DE Test Order workstations UI Sign off Load data install workstations integrate UL. Database Final User test E E Cost type General Unskilled Skilled Unskilled Skilled Unskilled General Skilled Skilled Unskilled Unskilled General Unskilled Unskilled Skilled General 1 15 Norrmal Cost 600 2,000 900 400 1,800 2,000 200 4,500 3,600 1.000 1,000 300 800 1,600 1.500 2.400 10 3 Crash Cost 500 3,500 1,400 450 2,800 2,700 200 7.000 5,600 1.800 5.000 300 1,350 2,700 2,100 2,400 DF 5 20 K 1 10 H M 1 4 8 3 LM N,O 5 8 3 Section B - Network Design Having chosen the software project, you are now provided with a work breakdown structure (WBS) for the project, provided by your IT department. These estimates are based on four similar software installations completed during the past two years. ID Predecessor A Duration 2 10 3 B A C A A 2 D E F B 6 C 10 1 H Activity SW Decision Stakeholder Input ID Data Sources DB Setup Draft UI Design Data Cleaning Spec Workstation UI Testing Data Validation DB Test Order workstations UI Sign off Load data install workstations integrate UI, Database Final User test 15 1 DF 12 5 20 K G L H 1 M 4 N 8 LM 5 8 P NO 1) Construct a network design logic diagram using this WBS. Use the ID and activity description to clearly identify each note. Complete a forward pass and backward pass and identity the slack times. Identify and clearly indicate the critical path. Discuss critical path sensitity, and how sensitive this network is to changing the critical path iv) This section is worth 20 marks