The document provides instructions on how to load resources into a project scheduling tool. It explains how to create a resource sheet with the resource breakdown structure and availability. It then describes how to apply resources to activities in the schedule by assigning them in the task information or resource work views. Specific rules are outlined for applying labor and non-labor resources correctly. Finally, it discusses different views for reviewing the resources assigned to activities and the overall project resource usage and allocation.
1. Resource Loading the Scheduling Tool Create the “Resource Sheet” Apply the correct resources to activities Load the required resources Viewing resources
2. Create the Resource Sheet 1. 2. 3. Determine Resource Breakdown Structure Similar to Organizational Breakdown Structure (ie. Org Chart) except different functions may be further defined into skill groups/levels (eg. Engineer into Junior/Senior/Staff Engineer; Test Engineer into System Test Engineer/Component Test Engineer) Unique nomenclature assigned Determine resource availability From Charter and/or “Resource Contracts” (see Kicking off the Team) Rate information derived from HR/cost accounting system Pay rate, overtime rate, overhead rate Typical workday (eg. 7.5h, 8h, 12h) may be entered here or in standard work calendar
9. Viewing Activity Resources Task Info Box – check what resources assigned while doing other work “Resource Work” view – most useful for initial entry and systematic review “Resource Name” column – rarely used, for display or transfer to Excel
11. WORKED EXAMPLE: Table Construction Project Resource load the schedule for the Table Construction Project using “Table Construction – Sequencing Complete.mpp” Additional Info: See Org Chart, Project Charter and Responsibilities Allocation Matrix on next slide
12. WORKED EXAMPLE: Table Construction Project Project Charter excerpt: “…project will require one full time carpenter, will share a painter currently working on Projects A and B, and will require minimal support (approx 10%) from QA…”