Sie sind auf Seite 1von 41

Resource Allocation

Resource Allocation
Some definitions Resource allocation, loading, leveling Expediting and crashing projects Goldratts Critical Chain

Some Definitions
Resource allocation There are generally two conditions:
Normal Crashed

Normal and Crashing


Normal: Crash:

No Free Lunch: Crashing Creates a Ripple Effect


Crashing buys time, but nothing comes free Potential cost areas
equipment/material labor other projects morale quality
5

Case: Architectural Associates, Inc.


Projects uniformly run late, thus over budget Is that the problem, or just the symptom?

Case: Architectural Associates, Inc. (contd)


PROBLEM: Deterministic task schedules Parkinsons Law: Work expands to fill the time available. RESULT: Issues arising early can be worked around, but late-occurring issues cant

Case: Architectural Associates, Inc. (concluded)


The Solution:
probabilistic time estimates Have staff schedule work for effectiveness and efficiency

When Trying to Crash a Project . . .


Two basic principles
1. Generally, focus on the critical path 2. Choose least expensive way to do it

Compute Cost per Day of Crashing a Project


Compute cost/time slope for each expeditable activity Slope = crash cost normal cost crash time normal time

10

An Example
Activity a b c d* e** Predecessor a a a b Days Cost (normal, crash) (normal, crash) 3, 2 2, 1 2, 2 4, 1 3, 1 $40, 80 20, 80 20, 20 30, 120 10, 80
11

* Partial crashing allowed ** Partial crashing not allowed

Example (contd): Cost per Day to Crash


Activity
a b c d e

$ Saved/ Day
40 60 30 70 (2 days)
12

A CPM Example

13

CPM Cost-Duration

14

Another Approach to Expediting: Fast-tracking/ Concurrency


Different terms for similar concept Fast-tracking (construction), Concurrent engineering (manufacturing) Both refer to overlapping project phases
15

Fast-tracking/Concurrency (contd)
Pros:
shorten duration reduce cycles meet demands

Cons:
increase cost

16

Cost, Schedule, or Performance: Pick Any Two


Assuming fixed performance tradeoff areas must be in time or cost Time-limited Resource-limited Over-determined

17

Resource Loading
Resource loading: amounts One project, or many
Identifies and reduces excess demands on a firms resources

18

Resource Usage Calendar

19

AOA Network

20

AON Network with Earliest/Latest Start/Finish Times

21

Modified PERT/CPM AOA

22

Load Diagrams

23

Resource Leveling
Resource leveling minimizes variations
shifting tasks within their slack allowances

Advantages
Less day-to-day manipulation Better morale, fewer problems/costs Levels costs, simplifies budgeting and funding
24

Network Before & After Resource Loading

25

Resource Loading Chart

26

Resource Loading Chart

27

Constrained Resource Scheduling


Two basic approaches
Heuristic Optimization

28

MSP Gantt with Resources

29

MSP Load Diagram, Showing Resource Conflict

30

MSP Load Diagram, Leveled

31

Network for Resource Load Simulation

32

Load Chart

33

Multiple Projects Resource Leveling


Schedule slippage Resource utilization In-process inventory

34

Task a Decomposed

35

Hierarchy of Gantt Charts

36

Flow Diagram

37

Goldratts Critical Chain


systemic problems plague project performance
Not randomly distributed

38

Some Systemic Causes of Late Projects


1. Thoughtless Optimism 2. Setting capacity equal to demand 3. Student Syndrome 4. Multitasking
39

Some Systemic Causes of Late Projects (concluded)


5. Schedule Complexity 6. Slack Time 7. Game playing

40

Critical Chain
Theory of Constraints

41

Das könnte Ihnen auch gefallen