\n
Introduction<\/strong><\/h3>\n\n\n\n
The Finish-to-Finish (FF)<\/strong> relationship is another key type of activity dependency in Primavera P6<\/strong>. In this relationship, the successor activity cannot finish until the predecessor activity finishes<\/strong>. This type of relationship allows both activities to run simultaneously, but the completion of the successor depends on the completion of the predecessor.<\/p>\n\n\n\n
The FF relationship is useful when two activities are related in such a way that one cannot be fully completed until the other is done, even though they can progress in parallel.<\/p>\n\n\n\n
Key Characteristics of Finish-to-Finish (FF) Relationship<\/strong><\/h3>\n\n\n\n
\n
- Simultaneous Execution<\/strong>:<\/li>\n<\/ol>\n\n\n\n
\n
- Both the predecessor and successor activities can be performed concurrently. However, the successor activity cannot finish until the predecessor activity is finished.<\/li>\n<\/ul>\n\n\n\n
\n
- Partial Dependency<\/strong>:<\/li>\n<\/ol>\n\n\n\n
\n
- Unlike the Finish-to-Start (FS) relationship, the FF relationship doesn\u2019t require the predecessor to be completed before the successor begins. Only the finish of the successor is dependent on the finish of the predecessor.<\/li>\n<\/ul>\n\n\n\n
\n
- Suitable for Parallel Workflows<\/strong>:<\/li>\n<\/ol>\n\n\n\n
\n
- The FF relationship is often used in workflows where activities must be coordinated to finish together.<\/li>\n<\/ul>\n\n\n\n
\n
- Flexible Completion Times<\/strong>:<\/li>\n<\/ol>\n\n\n\n
\n
- While both activities can run in parallel, the FF relationship ensures that one can\u2019t be completed until the other finishes.<\/li>\n<\/ul>\n\n\n\n
Real-Life Examples of FF Relationship<\/strong><\/h3>\n\n\n\n
Example 1: Construction Project<\/strong><\/h4>\n\n\n\n
\n
- Predecessor Activity<\/strong>: Complete electrical wiring in a building.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Complete electrical system testing.<\/li>\n<\/ul>\n\n\n\n
In this case, the electrical wiring and system testing can occur in parallel, but the testing cannot be fully completed until all of the wiring has been installed. The FF relationship ensures that the project is completed efficiently while maintaining the necessary coordination between related tasks.<\/p>\n\n\n\n
Example 2: Event Planning<\/strong><\/h4>\n\n\n\n
\n
- Predecessor Activity<\/strong>: Finish decorating the venue.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Finish setting up the audio-visual equipment.<\/li>\n<\/ul>\n\n\n\n
In an event planning scenario, both tasks can progress simultaneously, but setting up the audio-visual equipment may depend on the completion of the decoration (e.g., finalizing the stage backdrop). The FF relationship ensures that both tasks finish around the same time to meet the event deadline.<\/p>\n\n\n\n
Example 3: Software Development<\/strong><\/h4>\n\n\n\n
\n
- Predecessor Activity<\/strong>: Finish writing the code for a software module.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Finish testing the module.<\/li>\n<\/ul>\n\n\n\n
The testing team can begin testing as soon as a part of the module is coded, but the testing cannot be fully completed until the entire module is written and delivered. The FF relationship ensures that testing ends only when the coding task is completed.<\/p>\n\n\n\n
Using FF Relationship in Primavera P6<\/strong><\/h3>\n\n\n\n
To create a Finish-to-Finish (FF)<\/strong> relationship in Primavera P6<\/strong>, follow these steps:<\/p>\n\n\n\n
\n
- Define the Activities<\/strong>: Ensure that you have both the predecessor and successor activities defined in your project.<\/li>\n\n\n\n
- Assign FF Relationship<\/strong>: In the Activity Details<\/strong> window, under the Relationships<\/strong> tab, assign the Finish-to-Finish (FF)<\/strong> dependency to the successor activity and link it to the predecessor activity.<\/li>\n\n\n\n
- Lag or Lead (Optional)<\/strong>: You can introduce lag<\/strong> or lead<\/strong> to adjust the timing of when the successor activity finishes compared to the predecessor.<\/li>\n<\/ol>\n\n\n\n
Lag and Lead in FF Relationship<\/strong><\/h3>\n\n\n\n
\n
- Lag<\/strong>: Lag introduces a delay between the finish of the predecessor and the finish of the successor. For example, if there\u2019s a 2-day lag, the successor activity will only finish 2 days after the predecessor activity is finished. Example<\/strong>: In a building project, if floor installation (predecessor) is completed, there might be a 2-day lag before final cleaning (successor) can be finished.<\/li>\n\n\n\n
- Lead<\/strong>: A lead (negative lag) allows the successor activity to finish slightly before the predecessor activity finishes. Example<\/strong>: If the painting of walls (predecessor) is nearly complete, the clean-up (successor) may finish slightly earlier with a lead, assuming the last areas of painting are finishing up.<\/li>\n<\/ul>\n\n\n\n
Advantages of FF Relationship<\/strong><\/h3>\n\n\n\n
\n
- Improves Project Efficiency<\/strong>: Allows multiple tasks to be worked on simultaneously while coordinating their finishes, improving overall project efficiency.<\/li>\n\n\n\n
- Flexible Coordination<\/strong>: The FF relationship allows tasks to be coordinated in parallel but only restricts their completion, providing more flexibility than sequential relationships.<\/li>\n\n\n\n
- Ideal for Complex Projects<\/strong>: FF relationships are useful in complex projects where tasks need to be coordinated to finish simultaneously, such as in construction, event management, and manufacturing.<\/li>\n<\/ul>\n\n\n\n
Limitations of FF Relationship<\/strong><\/h3>\n\n\n\n
\n
- Potential for Delay<\/strong>: If the predecessor activity is delayed, it may cause delays in the completion of the successor activity as well.<\/li>\n\n\n\n
- Coordination Challenges<\/strong>: Managing activities that are progressing simultaneously but must finish together requires careful coordination, especially when using lead and lag adjustments.<\/li>\n\n\n\n
- Limited Application<\/strong>: The FF relationship is not as commonly used as FS or SS, and is more specialized for activities that need to finish together.<\/li>\n<\/ul>\n\n\n\n
Real-Life Scenario of FF Relationship<\/strong><\/h3>\n\n\n\n
Example: House Construction<\/strong><\/h4>\n\n\n\n
Consider a house construction project<\/strong> where multiple finishing tasks are happening concurrently:<\/p>\n\n\n\n
\n
- Predecessor Activity<\/strong>: Finish tiling the floors.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Finish installing plumbing fixtures.<\/li>\n<\/ul>\n\n\n\n
In this case, both tiling and plumbing fixture installation can happen simultaneously in different parts of the house. However, the plumbing fixtures (such as sinks and toilets) might rely on the final completion of tiling to ensure proper placement and avoid damage to the floors. Using a Finish-to-Finish relationship ensures that both tasks complete around the same time without delaying the overall project.<\/p>\n\n\n\n
When to Use FF Relationship<\/strong><\/h3>\n\n\n\n
\n
- Simultaneous but Coordinated Tasks<\/strong>: Use FF relationships when two tasks can run concurrently, but the finish of one depends on the completion of the other.<\/li>\n\n\n\n
- Interdependent Activities<\/strong>: When one activity cannot be fully completed without the full completion of another, such as in testing and production, FF is ideal.<\/li>\n\n\n\n
- Project Optimization<\/strong>: FF relationships help optimize project timelines by allowing activities to progress together and only tie them together at the point of completion.<\/li>\n<\/ul>\n\n\n\n
Conclusion<\/strong><\/h3>\n\n\n\n
The Finish-to-Finish (FF)<\/strong> relationship in Primavera P6<\/strong> is a valuable tool for managing tasks that can be performed concurrently but need to be coordinated to finish together. It provides the flexibility to execute parallel activities while maintaining control over when both tasks are completed. By using lag and lead times, project managers can fine-tune the timing of these activities to optimize project schedules, making the FF relationship especially useful in complex and time-sensitive projects.<\/p>\n\n\n\n
Related Articles<\/h2>\n\n\n\n
\n
- Different Between Mitigation Programme and Recovery Programme in Construction Industry.<\/a><\/li>\n
- Guidance for Reviewing Variation Orders in Construction Projects.<\/a><\/li>\n
- Reviewing Variation Orders in Construction Contracts.<\/a><\/li>\n
- Essential Guidelines for Project Stakeholder Management.<\/a><\/li>\n
- Resource Leveling in Construction Projects Using Primavera P6: a Detailed Guide<\/a><\/li>\n<\/ul>\n\n
Related posts:
Method statement for start-to-start (ss) relationship in primavera p6.
Method statement for finish-to-start (fs) relationship in primavera p6.
- \n
- Simultaneous Execution<\/strong>:<\/li>\n<\/ol>\n\n\n\n
- \n
- Both the predecessor and successor activities can be performed concurrently. However, the successor activity cannot finish until the predecessor activity is finished.<\/li>\n<\/ul>\n\n\n\n
- \n
- Partial Dependency<\/strong>:<\/li>\n<\/ol>\n\n\n\n
- \n
- Unlike the Finish-to-Start (FS) relationship, the FF relationship doesn\u2019t require the predecessor to be completed before the successor begins. Only the finish of the successor is dependent on the finish of the predecessor.<\/li>\n<\/ul>\n\n\n\n
- \n
- Suitable for Parallel Workflows<\/strong>:<\/li>\n<\/ol>\n\n\n\n
- \n
- The FF relationship is often used in workflows where activities must be coordinated to finish together.<\/li>\n<\/ul>\n\n\n\n
- \n
- Flexible Completion Times<\/strong>:<\/li>\n<\/ol>\n\n\n\n
- \n
- While both activities can run in parallel, the FF relationship ensures that one can\u2019t be completed until the other finishes.<\/li>\n<\/ul>\n\n\n\n
Real-Life Examples of FF Relationship<\/strong><\/h3>\n\n\n\n
Example 1: Construction Project<\/strong><\/h4>\n\n\n\n
- \n
- Predecessor Activity<\/strong>: Complete electrical wiring in a building.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Complete electrical system testing.<\/li>\n<\/ul>\n\n\n\n
In this case, the electrical wiring and system testing can occur in parallel, but the testing cannot be fully completed until all of the wiring has been installed. The FF relationship ensures that the project is completed efficiently while maintaining the necessary coordination between related tasks.<\/p>\n\n\n\n
Example 2: Event Planning<\/strong><\/h4>\n\n\n\n
- \n
- Predecessor Activity<\/strong>: Finish decorating the venue.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Finish setting up the audio-visual equipment.<\/li>\n<\/ul>\n\n\n\n
In an event planning scenario, both tasks can progress simultaneously, but setting up the audio-visual equipment may depend on the completion of the decoration (e.g., finalizing the stage backdrop). The FF relationship ensures that both tasks finish around the same time to meet the event deadline.<\/p>\n\n\n\n
Example 3: Software Development<\/strong><\/h4>\n\n\n\n
- \n
- Predecessor Activity<\/strong>: Finish writing the code for a software module.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Finish testing the module.<\/li>\n<\/ul>\n\n\n\n
The testing team can begin testing as soon as a part of the module is coded, but the testing cannot be fully completed until the entire module is written and delivered. The FF relationship ensures that testing ends only when the coding task is completed.<\/p>\n\n\n\n
Using FF Relationship in Primavera P6<\/strong><\/h3>\n\n\n\n
To create a Finish-to-Finish (FF)<\/strong> relationship in Primavera P6<\/strong>, follow these steps:<\/p>\n\n\n\n
- \n
- Define the Activities<\/strong>: Ensure that you have both the predecessor and successor activities defined in your project.<\/li>\n\n\n\n
- Assign FF Relationship<\/strong>: In the Activity Details<\/strong> window, under the Relationships<\/strong> tab, assign the Finish-to-Finish (FF)<\/strong> dependency to the successor activity and link it to the predecessor activity.<\/li>\n\n\n\n
- Lag or Lead (Optional)<\/strong>: You can introduce lag<\/strong> or lead<\/strong> to adjust the timing of when the successor activity finishes compared to the predecessor.<\/li>\n<\/ol>\n\n\n\n
Lag and Lead in FF Relationship<\/strong><\/h3>\n\n\n\n
- \n
- Lag<\/strong>: Lag introduces a delay between the finish of the predecessor and the finish of the successor. For example, if there\u2019s a 2-day lag, the successor activity will only finish 2 days after the predecessor activity is finished. Example<\/strong>: In a building project, if floor installation (predecessor) is completed, there might be a 2-day lag before final cleaning (successor) can be finished.<\/li>\n\n\n\n
- Lead<\/strong>: A lead (negative lag) allows the successor activity to finish slightly before the predecessor activity finishes. Example<\/strong>: If the painting of walls (predecessor) is nearly complete, the clean-up (successor) may finish slightly earlier with a lead, assuming the last areas of painting are finishing up.<\/li>\n<\/ul>\n\n\n\n
Advantages of FF Relationship<\/strong><\/h3>\n\n\n\n
- \n
- Improves Project Efficiency<\/strong>: Allows multiple tasks to be worked on simultaneously while coordinating their finishes, improving overall project efficiency.<\/li>\n\n\n\n
- Flexible Coordination<\/strong>: The FF relationship allows tasks to be coordinated in parallel but only restricts their completion, providing more flexibility than sequential relationships.<\/li>\n\n\n\n
- Ideal for Complex Projects<\/strong>: FF relationships are useful in complex projects where tasks need to be coordinated to finish simultaneously, such as in construction, event management, and manufacturing.<\/li>\n<\/ul>\n\n\n\n
Limitations of FF Relationship<\/strong><\/h3>\n\n\n\n
- \n
- Potential for Delay<\/strong>: If the predecessor activity is delayed, it may cause delays in the completion of the successor activity as well.<\/li>\n\n\n\n
- Coordination Challenges<\/strong>: Managing activities that are progressing simultaneously but must finish together requires careful coordination, especially when using lead and lag adjustments.<\/li>\n\n\n\n
- Limited Application<\/strong>: The FF relationship is not as commonly used as FS or SS, and is more specialized for activities that need to finish together.<\/li>\n<\/ul>\n\n\n\n
Real-Life Scenario of FF Relationship<\/strong><\/h3>\n\n\n\n
Example: House Construction<\/strong><\/h4>\n\n\n\n
Consider a house construction project<\/strong> where multiple finishing tasks are happening concurrently:<\/p>\n\n\n\n
- \n
- Predecessor Activity<\/strong>: Finish tiling the floors.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Finish installing plumbing fixtures.<\/li>\n<\/ul>\n\n\n\n
In this case, both tiling and plumbing fixture installation can happen simultaneously in different parts of the house. However, the plumbing fixtures (such as sinks and toilets) might rely on the final completion of tiling to ensure proper placement and avoid damage to the floors. Using a Finish-to-Finish relationship ensures that both tasks complete around the same time without delaying the overall project.<\/p>\n\n\n\n
When to Use FF Relationship<\/strong><\/h3>\n\n\n\n
- \n
- Simultaneous but Coordinated Tasks<\/strong>: Use FF relationships when two tasks can run concurrently, but the finish of one depends on the completion of the other.<\/li>\n\n\n\n
- Interdependent Activities<\/strong>: When one activity cannot be fully completed without the full completion of another, such as in testing and production, FF is ideal.<\/li>\n\n\n\n
- Project Optimization<\/strong>: FF relationships help optimize project timelines by allowing activities to progress together and only tie them together at the point of completion.<\/li>\n<\/ul>\n\n\n\n
Conclusion<\/strong><\/h3>\n\n\n\n
The Finish-to-Finish (FF)<\/strong> relationship in Primavera P6<\/strong> is a valuable tool for managing tasks that can be performed concurrently but need to be coordinated to finish together. It provides the flexibility to execute parallel activities while maintaining control over when both tasks are completed. By using lag and lead times, project managers can fine-tune the timing of these activities to optimize project schedules, making the FF relationship especially useful in complex and time-sensitive projects.<\/p>\n\n\n\n
Related Articles<\/h2>\n\n\n\n
- \n
- Different Between Mitigation Programme and Recovery Programme in Construction Industry.<\/a><\/li>\n
- Guidance for Reviewing Variation Orders in Construction Projects.<\/a><\/li>\n
- Reviewing Variation Orders in Construction Contracts.<\/a><\/li>\n
- Essential Guidelines for Project Stakeholder Management.<\/a><\/li>\n
- Resource Leveling in Construction Projects Using Primavera P6: a Detailed Guide<\/a><\/li>\n<\/ul>\n\n
Related posts:
Method statement for start-to-start (ss) relationship in primavera p6.
Method statement for finish-to-start (fs) relationship in primavera p6. - Guidance for Reviewing Variation Orders in Construction Projects.<\/a><\/li>\n
- Interdependent Activities<\/strong>: When one activity cannot be fully completed without the full completion of another, such as in testing and production, FF is ideal.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Finish installing plumbing fixtures.<\/li>\n<\/ul>\n\n\n\n
- Coordination Challenges<\/strong>: Managing activities that are progressing simultaneously but must finish together requires careful coordination, especially when using lead and lag adjustments.<\/li>\n\n\n\n
- Flexible Coordination<\/strong>: The FF relationship allows tasks to be coordinated in parallel but only restricts their completion, providing more flexibility than sequential relationships.<\/li>\n\n\n\n
- Lead<\/strong>: A lead (negative lag) allows the successor activity to finish slightly before the predecessor activity finishes. Example<\/strong>: If the painting of walls (predecessor) is nearly complete, the clean-up (successor) may finish slightly earlier with a lead, assuming the last areas of painting are finishing up.<\/li>\n<\/ul>\n\n\n\n
- Assign FF Relationship<\/strong>: In the Activity Details<\/strong> window, under the Relationships<\/strong> tab, assign the Finish-to-Finish (FF)<\/strong> dependency to the successor activity and link it to the predecessor activity.<\/li>\n\n\n\n
- Successor Activity<\/strong>: Finish testing the module.<\/li>\n<\/ul>\n\n\n\n
- Successor Activity<\/strong>: Finish setting up the audio-visual equipment.<\/li>\n<\/ul>\n\n\n\n
- Successor Activity<\/strong>: Complete electrical system testing.<\/li>\n<\/ul>\n\n\n\n
- Predecessor Activity<\/strong>: Complete electrical wiring in a building.<\/li>\n\n\n\n
- While both activities can run in parallel, the FF relationship ensures that one can\u2019t be completed until the other finishes.<\/li>\n<\/ul>\n\n\n\n
- Flexible Completion Times<\/strong>:<\/li>\n<\/ol>\n\n\n\n
- The FF relationship is often used in workflows where activities must be coordinated to finish together.<\/li>\n<\/ul>\n\n\n\n
- Suitable for Parallel Workflows<\/strong>:<\/li>\n<\/ol>\n\n\n\n
- Unlike the Finish-to-Start (FS) relationship, the FF relationship doesn\u2019t require the predecessor to be completed before the successor begins. Only the finish of the successor is dependent on the finish of the predecessor.<\/li>\n<\/ul>\n\n\n\n
- Partial Dependency<\/strong>:<\/li>\n<\/ol>\n\n\n\n
- Both the predecessor and successor activities can be performed concurrently. However, the successor activity cannot finish until the predecessor activity is finished.<\/li>\n<\/ul>\n\n\n\n
