Understanding Constraints and Relationships in Primavera P6 8.2
Upcoming SlideShare
Loading in...5
×
 

Understanding Constraints and Relationships in Primavera P6 8.2

on

  • 3,710 views

Read and understand the constraints and relationships in Primavera P6 8.2 software.

Read and understand the constraints and relationships in Primavera P6 8.2 software.

Statistics

Views

Total Views
3,710
Views on SlideShare
3,710
Embed Views
0

Actions

Likes
0
Downloads
103
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Understanding Constraints and Relationships in Primavera P6 8.2 Understanding Constraints and Relationships in Primavera P6 8.2 Presentation Transcript

    • Understanding Constraints in Primavera P6
    • Constraints are applied to Activities when relationships do not provide the required result and are often a result of External Dependencies.
    • Typical applications of a constraint are to constrain an activity to a date for:  The availability of a site to commence work.  The supply of information by a client.  The required finish date of a project.
    • Constraints are often entered against Milestone activities to represent contract dates and may be directly related to contract items using Notebook Topics. Constraints are covered in detail in the Constraints chapter.
    • Understanding Relationships
    • There are four types of dependencies available in Primavera P6:  Finish-to-Start (FS) (also known as conventional)  Start-to-Start (SS)  Start-to-Finish (SF)  Finish-to-Finish (FF)
    • Two other terms you must understand are: Predecessor, an activity that controls the start or finish of another immediate subsequent activity. Successor, an activity where the start or finish depends on the start or finish of another immediately preceding activity.
    • The following pictures show how the dependencies appear graphically in the Bar Chart and Activity Network (also known as PERT, Network Diagram and Relationship Diagram Views): The FS (or conventional) dependency looks like this:
    • Eastwood Harris Supplies Project Management Training Manuals, Project Management Training Presentations and Consulting on Primavera P6 and Microsoft Project 2010 across Australia.