Project Crashing Using Cpm

Only available on StudyMode
  • Download(s) : 238
  • Published : May 31, 2013
Open Document
Text Preview
Scamoail Ahmed - Project Mgmt assignment no 2
Q No 1 : What is meant by Project Crashing? How you incorporate Project Crashing through PERT-CPM?

Definition
1.Project Crashing is a technique / process by which a project can be expedited by compressing the project schedule. Explanation
2.When we say that a project completion time is XX days, we generally mean that the project will normally takes these number of days within a specified resource / budget constraint. We could make it take less time , but to do so we will have to increase our budget or resources or a combination of both. 3.We can however reallocate resources from one facet of the project and use it to speed up an activity that is lagging behind OR we can all together allocate new resources to our ACTIVITIES IN CRITICAL PATH. However care must be taken that, if the resources should always be withdrawn from activities that have more SLACK . In Short for project crashing we have to concentrate our efforts on THE CRIRICAL PATH i.e whatever efforts we have to do in term of time , resources or budget will be done on the critical path and these things have to be taken out either from the non-critical activities having enough SLACK or new allocation should be made. 4.While carrying out project crashing utmost care must be taken that appropriate activities are being crashed and that diverted resources are not causing needless risk and PROJECT SCOPE INTEGRITY

Example (Using PERT / CPM)
Example narrative
5.An aircraft gets damage as a result of ground accident, the damage was analyzed by the maintenance crew and timelines for the repair were analyzed using CPM which came out to be 6 days (8 hrs/ day), however the stake holder needed the repair to be completed in 3 days as the aircraft was needed for a VIP mission. Efforts were made to meet the timelines by working overtime, however still the timelines could not be met. Project crashing was carried out keeping in view the fact that PROJECT SCOPE INTEGRITY remains intact and the new timelines came out to be 34 hrs (2.21 days @ 16 hrs / day). Network diagrams are attached below for ref.

Activity| Description| Predecessor| Time|
A | Processing of work order (2 Hrs)| -| 2|
B | Induction of aircraft (1 hour)| A| 1|
C | Removal of damaged airframe components (10 Hrs)| B| 10| D| Removal of damage components from donor aircraft (16 hrs)| -| 16| E | Repair of damaged area (12 Hrs)| C,D| 12|
F| Installation of new airframe components (6 Hrs)| E,D| 6| G | Repair of fiberglass / plexi glass components (8 Hrs)| C| 8| H| Painting of fiber glass components (2 Hrs)| G| 2|
I| Installation of plexiglass / fiberglass components (4Hrs| H,F| 4| J| Sealing of damaged area (2 Hrs)| I| 2|
K| Quality check (1 Hrs)| J| 1|
L | Test flying (1 Hrs)| K| 1|
M | Completing paper work (1 Hrs)| K| 1|

Network Diagram without project crashing

13 21

24 32

G

8
3 13

6 16

C

10
2 3

5 6

B

1

0 2
4 6

A

2
FINISH
41 42

41 42

L

1
40 41

40 41

K

1
38 40

38 40

J

2
21 23

32 34

H

2
16 28

16 28

E

12
0 16

0 16

D

16

START

41 42

41 42

M

1
28 34

28 34

F

6

34 38

34 38

I

4

Figure No 1
Critical path identification without project crashing

13 21

24 32

G

8
3 13

6 16

C

10
2 3

5 6

B

1

0 2
4 6

A

2
FINISH
41 42

41 42

L

1
40 41

40 41

K

1
38 40

38 40

J

2
21 23

32 34

H

2
16 28

16 28

E

12
0 16

0 16

D

16

START

41 42

41 42

M

1
28 34

28 34

F

6

34 38

34 38

I

4

Figure No 2
Critical Path with project crashing
13 21

18 26

G

8
3 13

3 13

C

10
2 3

2 3

B

1

0 2
0 2

A

2
FINISH
33 34

33 34

L

1
32...
tracking img