To understand the most basic element of the schedule, we should first agree on the best practices. Under the conditions of these best practices, Oracle Primavera performs at its best:
- The schedule should follow the rules of a Critical Path Method (CPM) schedule. In such a schedule there is a list of all activities required to complete the project. Each activity has a duration to complete, and each activity has at least one predecessor and one successor relationship. The Start Project Milestone and Finish Project Milestone are the only exceptions to this rule. This creates a relationship-driven schedule in which one set of activities will be the longest path and the earliest the product can be delivered. The activities within that primary path are critical, meaning they must occur on the calculated dates in order to deliver the entire project on time.
- Lead times and Lag times are rarely used, though there are uses which are clear exceptions.
- Constraints are very rare within the schedule—and it is preferred they are not used at all. Dates are calculated by Oracle Primavera rather than input. See the baseline chapter for more on this topic.
- A logical sequence of activities is used which requires planning and agreement that one item begins before another, and so on. See the scheduling chapter for more on this topic.
- Progress is input and reported by the user with minimal auto-population of fields.
- A basic activity should be no longer than 80 hours of work or 14 days duration.
These practices, when used in combination, provide the best forecast and most accurate reporting of schedule performance, especially as the schedule should exactly mirror the work performance on the job site.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.