1. Scheduling

2. Putting the activities in chronological order –Chicken or the egg Allows the PM to determine the time required to complete a project

3. Types of Schedules Depend on Viewer –Simple bar chart (Gantt chart) Tells owner progress –Activity on Node (AON) –Activity on Arrow (AOA) Used by PM, supers, foremen

4. Developing Activity Sequence Physical Relationship An activity cannot start until a previous one is complete Safety Relationship Performing activities which cause a safety hazard to other activities Resource Relationship The amount of resources available at any time Preferential Relationship Contractors preference on activity order

5. Constructing Bar Chart How should bar chart be laid out –Time on horizontal axis –Activity on vertical axis –Time of activity start based on position –Duration of activity based on length of line Day = start of day to start of day

6. Constructing Bar Chart What time unit should be used –Work days –Hours –Weeks –Bar chart size may dictate time units

7. Constructing Bar Chart Additional Info –Activity Value –Activity Cost –Activity Resource requirements

8. Constructing Bar Chart Work days or Calendar days –Work days harder to follow No weekends or holidays –Calendar days allow you to see concrete curing

9. Gantt Chart Looks like a horizontal bar chart Good for linear work Good for providing an overview of the project Not good for complex projects

10. Gantt Chart

11. Activity Network Development Network Models Activity on Node Precedence Diagram Method Activity on Arrow Network Characteristics Discrete Activities Deterministic Durations Deterministic Logic Activity Flow

12. Network Elements Activities Basic building block Represent tasks Must consume time and resources Milestones Notice to Proceed Building Enclosed Substantial Completion Project Complete Activity Relationships Physical, Safety, Resource, Preferential

13. Precedence Succeeding activities cannot start until preceding activities finished Changes in duration of one activity affect all succeeding activities

14. Activity on Node All activities occur at nodes Arrows connect nodes and show relationships

15. Activity on Node Basics: Unique Alphanumeric identifier Unique description Estimated Duration Succeeding activity cannot start until preceding activity is finished Need beginning and ending milestone to tie project together

16. Constructing an AON Network Sequential logic –All activities preceding must be finished before next activity can start Concurrent Logic –2 or more activities can be worked at one time

17. Constructing an AON Network Multiple Successor Logic –2 or more activities can be worked at one time after common predecessor is finished Multiple Predecessor Logic –2 or more activities need to be finished before next activity starts

18. Constructing an AON Network Combinational Logic –2 or more activities can be worked at one time after multiple predecessor activities are finished

19. Logic Errors and Problems Incorrect Logic Activities MUST have a logical connection Paint color does not control the roofing application Redundant Logic –Not incorrect –Can cause errors

20. Logic Errors and Problems –Logic Loops

21. Activity Numbering Numbering Activities can make it easier to use schedule Group like activities under the same general numbers –Activity Category WBS can make it easy to categorize resources used to each activity –Work Classification Numbers refer to a class of activity

22. Activity Numbering –Location Number activity based on location on project –Responsibility Numbers refer to who is responsible for work

23. Activity Numbering Numbering Conventions –Directional Numbers increase from start to finish of project –Numbering gaps Leave gaps between numbers to allow for additions to schedule –Even/Odd Numbering Even # = part of base contract Odd # = additional work