12-1 ELC 347 project management Week 13

12-2 Agenda Integrative Project –4 th part Corrected.. Fedd back sent –5 Th part due –Outline of deliverables (posted in WebCT)Outline of deliverables (posted in WebCT) Assignment 5 missing –Was due Nov 28 Student evaluations Today we will discuss Resource Management

12-3 Schedule for the final few Days Nov 28 –Assignment 5 due (missing) Nov 30 (today) –IP part 5 due –Discussion on resource Leveling (Chap 12) Dec 7 –IP part 6 Due (will be corrected and returned within 24 hours of receipt if turned in on time) –Quiz 3 Assigned (Chap 10, 11, 12, & 13) –Discussion on Project Evaluation and Control (chap 13) Dec Midnight –Resubmission of IP part 1 – 5 deadline Dec 10 AM –IP project (complete) due –Resubmission of Part 6 –IP project Presentation Dec noon –Quiz 3 Due One less quiz and 2 less assignments then was identified in syllabus

12-4 Resource Management Chapter 12 © 2007 Pearson Education

12-5

12-6 Types of Constraints  Technical  Physical  Resource  Materials  Human resources  Time  Mixed

12-7

12-8

12-9 Resource Loading The amounts of individual resources that a schedule requires during specific time periods. Resource loading table Resource NameWorkDetails5/55/125/195/26 Bob40 hrsWork8h32h Assign Bids40 hrsWork8h32h Carol40 hrsWork8h32h Calculate Cost40 hrsWork8h32h Ted40 hrsWork8h32h Documentation40 hrsWork8h32h Alice8 hrsWork8h Select Bid8 hrsWork8h

12-10 Resource Leveling (Smoothing) A multivariate, combinatorial problem Objectives To determine the resource requirements so that they will be available at the right time To allow each activity to be scheduled with the smoothest possible transition across resource usage levels

12-11 Prioritization Rules for Leveling 1.Smallest amount of slack 2.Smallest duration 3.Lowest ID number (FCFS) 4.Greatest number of successor tasks 5.Requiring the most resources

12-12 Resource leveling (method one) Develop resource leveling table Determine activity Late finish dates Identify resource Over allocation Level the resource loading table –Requires more than one run-through due to ripple effects Examine conflicts (apply rules) Select activity to be reconfigured Start over looking for more conflicts

12-13 Sample project

12-14 Task table ActivityDurationESEFLSLFSlack A50505 B C55 5 D E F G H I J K

12-15 Resource Needs ActivityDurationFloatHours/dayTotal hours A5630 B4128 C5420 D63318 E613 F6212 G43416 H7321 I53420 J3526 K5525 Total194

12-16 Resource Profile

12-17 Resource loading table

12-18 Resource Loading with LF dates

12-19 leveling resource leveling.xls

12-20 End result

12-21 A much better Way Use MS Project –Enter resources –Assign resources to tasks –Use Resource leveling tool –Sample resource leveling.mppSample resource leveling.mpp

12-22 Resource Loading charts Method two 1.Create a project activity network diagram 2.Develop resource loading table 3.Determine activity late finish dates 4.Identify resource over allocation 5.Resource level the loading table

12-23 Creating Resource Loading Charts Display the amount of resources required as a function of time. 0 A4 Res = 6 4 B5 Res = 2 5 D9 Res = 7 9 E11 Res = 3 4 C7 Res = 2 11 F12 Res = 6 1.Start with a network diagram

12-24 Creating Resource Loading Charts ActivityResourceDurationESSlackLF A64004 B21405 C D74509 E3290 F Produce a table that shows the duration, early start, late finish, slack, and resource(s) required for each activity.

12-25 Creating Resource Loading Charts A C B D E F Project Days Resources 3.Draw an initial loading chart with each activity scheduled at its ES. Resource imbalance

12-26 Creating Resource Loading Charts 4.Rearrange activities within their slack to create a more level profile. Splitting C creates a more level project. A C B D E F Project Days Resources C

12-27 efficiency

12-28 Key Parameters in Multi-Project Environments  Schedule slippage  Possible $ penalty  Resource utilization  More efficient is better  In-process inventory  Reduce back log

12-29 Prioritizing Resource Allocations in Multi-Project Environments First come first served Greatest resource demand Greatest resource utilization Minimum late finish time Mathematical programming