Primavera P6 Training Sydney – Types of Project Constraints

primavera_P6_V8.2 training using metrics brisbanePrimavera P6 Project Constraints Types in Sydney

There are two types of constraints:

  • Project Constraints which includes the Project Start Date and Project Finish Date, and
  • Activity Constraints; the two most common are Start On or After (Early Start) and Finish On or Before (Late Finish).

External dependencies are applied to a schedule using Constraints and these may model the impact of events outside the logical sequence of activities. A constraint would be imposed to specific dates such as the availability of a facility to start work or the required completion date of a project.

Constraints on projects in Sydney should be cross-referenced to the supporting documentation, such as Milestone Dates from contract documentation, using the Notebook Topics function.

Project Constraints

A Project Start Date called Project Planned Start in P6 is the earliest date that any activity may be scheduled to start. An activity will start on the Project Start Date unless one of the following stop the activity starting on the Project Start Date::

  • There is a Calendar Non Work time, or
  • A constraint, or
  • A relationship.

A Project Finish Date is optional, but once set this controls Total Float (often referred to as Float in P6).

When a Project Finish Date constraint is assigned in Sydney then Total Float is calculated to this date.

  • The picture shows a project with a Project Finish date on Friday 26 September developing 5 days Total Float.

p6 project finish date

  • The picture shows a schedule with a Project Finish date of Friday 12,
  • This is earlier than the calculated finish date, thus calculating 5 days Negative Float:

p6 project finish date 2

Activity Constraints

Typical examples of activity constraints would be:

  • Start on or After for the availability of a site to commence work, and
  • Finish on or Before for the date that a total project must be completed or handed over.

Activity Early Start Constraint

  • An activity will no longer start on the Data Date when a Start On or After constraint is assigned
  • This is more commonly known as an Early Start constraint.

p6 project early start

NOTES: In P6 the time must always be displayed as P6 will often set constraints at 00:00hrs which is midnight and is not very often an appropriate time to set constraints.

Eastwood Harris Supplies Project Management Training Manuals, Project Management Training Presentations and Consulting on Primavera P6 and Microsoft Project 2010 across Australia.

Create a Project Using Primavera P6 – Primavera P6 Training Sydney Melbourne Perth

isbn#9781921059575 _Oracle Primavera P6 Training manual_V8-1Creating Projects in Sydney, Melbourne or Perth Using Primavera P6

To create a project in a Primavera database, you will need the following information:

  • An EPS Node, OBS Node in the database to assign the project,
  • Project ID (a code assigned to the project) and the Project Name,
  • The Project Start Date (and perhaps the Finish Date), and
  • The Rate Type. Primavera has five rates per resource and this option enables you to select a rate as the default resources rate.

It would also be useful to know other information such as:

  • Client name, and
  • Project information such as location, project number and stakeholders.

Defining the Calendars

Before you start entering activities into your schedule, it is advisable to set up the calendars. These are used to model the working time for each activity in the project. For example, a 6-day calendar is created for those activities that will be worked for 6 days a week. The calendar should include any public holidays and any other exceptions to available working days, such as planned days off.

Primavera Software has three types of calendars:

  • Global– which may be assigned to activities and resources in any project,
  • Project– these are project-specific calendars assigned to activities, and
  • Resource– that are assigned to resources.

Project and Resource calendars may be linked to Global calendars, enabling any changes to holidays made to a Global calendar to be inherited by the associated Project and Resource calendars.

Defining the Project Breakdown Structures

A project breakdown structure (PBS) is a way of categorizing the activities of a project into numerous codes that relate to the project. The codes act as tags or attributes of each activity.

During or after the activities are added to the schedule, they are assigned their PBSs so that they may be grouped, summarized, and filtered in or out of the display.

Primavera has two principal methods of assigning a PBS to your project:

  • The Work Breakdown Structure (WBS) function, which is comparable to the P3 and SureTrak WBS functions.
  • The Activity Code function that operates in a way similar to P3 and SureTrak.

Before creating a project, you should design your PBSs by asking the following questions:

  • Which phases are involved in the project (e.g., Design, Procure, Install and Test)?
  • Which disciplines are participating (e.g., Civil, Mechanical and Electrical)?
  • Which departments are involved in the project (e.g., Sales, Procurement and Installation)?
  • What work is expected to be contracted out and which contractors are to be used?
  • How many sites or areas are there in the project?

Use the responses to these and other similar questions to create the PBSs.

Eastwood Harris Supplies Project Management Training Manuals, Project Management Training Presentations and Consulting on Primavera P6 and Microsoft Project 2010 across Australia.