Given below is the information for the IT project we discussed in our Week 5 commentary and its network diagram. In the Week 5 commentary, we crashed the project by three days, i.e., from 20 to 17 days by crashing Activity C for two days and Activity F by a day. Now proceeding from here:
Activity ID Predecessor Normal Time
(Days) Crash Time
(Days) Normal Cost Crash Cost ($'000) ($'000)
A - 5 2 $100 $205
B - 6 3 $140 $205
C - 7 5 $140 $200
D A, B 6 2 $100 $340
E C 3 1 $120 $200
F C 8 5 $580 $700
G D, E, F 5 3 $400 $660
Note: A "fully crashed schedule" means a project that has been crashed until the cost of crashing exceeds the marginal gain associated with eliminating overhead cost (which is $100,000 per day for this project). o Continue crashing the project until the cost of crashing exceeds the marginal gain associated with eliminating overhead cost ($100,000 per day). o Assume you have begun the project under the fully crashed schedule and you are now at the end of Day 6. Tasks A and C are finished, but Task B will require two more days of work. What corrective crashing decisions might you make to increase the likelihood that you can complete the schedule within the remaining 14 days? Are there any tasks you might consider uncrashing? What other actions could you consider?
Submission: You must submit your answers to this exercise in the form of a single word document. You may cut and paste your excel work on this word document. Name your file as: LastName_FirstName_CrashingProjectExercise.docx
Activity ID Predecessor Normal Time (Days) Crash Time (days) Normal Cost Crash Cost Crashed Days Days Available Crash Cost/Day
A 5 2 $ 100.00 $ 205.00 0 3 $ 35.00
B 6 3 $ 140.00 $ 205.00 1 2 $ 21.67
C 7 5 $ 140.00 $ 200.00 2 0 $ 30.00
D A,B 6 2 $