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 Duration 2 A B 10 3 A D A 2 B E F 6 10 1 15 G E 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 H 1 E F DF G 12 5 20 J K L M H 1 4 N 8 o K L, M NO 5 8 i) ii) 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 identify the slack times. Identify and clearly indicate the critical path. Discuss critical path sensitivity, and how sensitive this network is to changing the critical path. iv) 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) ii) iii) 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) ID Predecessor Crash Cost Duration 2. 600 A 10 B A 3 D A 2 E B 6 F 10 G E 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 E Cost type General Unskilled Skilled Unskilled Skilled Unskilled General Skilled Skilled Unskilled Unskilled General Unskilled Unskilled Skilled General 15 Normal Cost Crash Duration 600 2 2,000 8 9001 2 400 1 1,800 4 2,000 6 200 1 4,500 10 3,600 8 1,000 4 1,000 10 300 1 800 3 1,600 6 1,500 3 2,400 8 F 12 1 J 3,600 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 5 DF G K 20 L H 1 4 EZO 8 5 L, M NO 8