Adroit’s experts, the authors of AACE Recommended Practice PS-19 Linear Scheduling Method (LSM)

On October 16, 2019, AACE international announced that it has released Recommended Practice PS-19 Linear Scheduling Method for the review of AACE Planning and Scheduling Subcommittee. After the first round of review, this industry guideline will be released for public review in December 2019.

Adroit’s experts, Dr. Amin Terouhid, PE and Dr. Maryam Mirhadi, PMP, are the authors of AACE Recommended Practice PS-19 Linear Scheduling Method.

This recommended practice (RP) is intended to serve as a guideline, not a standard. As a recommended practice of AACE International, the main objectives of this Recommended Practice (RP) are as follow:

  • provide an overview of the Linear Scheduling Method
  • define characteristics and applications of the Linear Scheduling Method
  • delineate the steps and main considerations in developing, updating, and managing linear schedules
  • highlight main considerations in interpreting linear schedule
  • identify the computer software applications that are used to develop linear schedules

After the release of this Recommended Practice, the Association for the Advancement of the Cost Engineering (AACE international), which is one of the globally-known associations in the fields of cost engineering and project management will release this recommended practice to its members and project management professionals throughout the globe. 

AACE Planning & Scheduling Professional (PSP) Certification Course – Sponsored by the AACE New York Metro Section

Adroit is pleased to announce the Planning & Scheduling Professional (PSP) Certification Training Course. This training course is for those practitioners who are interested to obtain AACE International’s project Planning and Scheduling Professional (PSP). AACE New York Metro is the sponsor of this training.

Time: Oct 05, 9:00 AM – Oct 06, 5:00 PM

Location: 485 Lexington Ave, New York, NY 10017, USA

About the Event: The course will have two full days of instruction on October 5th and October 6th. The course will be taught by Dr. Amin Terouhid. Dr. Terouhid is a Principal Consultant with Adroit Consultants, LLC and 15 years of experience working on several large and mega projects internationally and throughout the United States. Dr. Terouhid is a recognized expert in the areas of project management, project planning, scheduling, control, schedule delay analysis, loss of productivity, and dispute avoidance and resolution.

Dr. Terouhid was a recipient of the 2018 AACE Technical Excellence Award. He has received his Ph.D. in construction management from the University of Florida, and holds the following professional certificates: Professional Engineer (P.E.) – Texas, Project Management Professional (PMP), Decision and Risk Management Professional (DRMP), and Planning and Scheduling Professional (PSP).

To find out more and register, please check out the following link:

https://www.aacei-nyc.org/events-1/aace-planning-scheduling-professional-psp-certification-course

Note: The AACE New York Metro Section is a section of AACE International focused on providing technical presentations and networking events for project control professionals in the New York Metro Area. AACE International has been certifying individuals since 1976 offering Certified Cost Professional (CCP), Certified Cost Technician (CCT), Certified Estimating Professional (CEP), Certified Forensic Claims Consultant (CFCC), Earned Value Professional (EVP), Decision and Risk Management Professional (DRMP), Certified Scheduling Technician (CST) and Planning & Scheduling Professional (PSP). AACE’s certifications are independently accredited by the Council of Engineering and Scientific Specialty Boards.

Adroit’s Amin Terouhid, Ph.D., PE is the featured speaker at the AACE Delaware section meeting

The presentation will be about project schedule deficiencies. Here is a brief overview of the presentation:

  • This presentation will explore the main types of activity relationships including mandatory, discretionary, scenario-based, and improper relationships and highlights the main considerations that project scheduling professionals need to give to assigning proper activity relationship types. It will also explore various types of mandatory relationships including physical, imposed, and safety relationships between activities and discusses some of the main shortcomings of project schedules from the activity relationships point of view. It will also examine the implications of these shortcomings from the schedule management, project control, and forensic claims perspective.
Date: Wednesday, May 15, 2019; Time: 6:00 pm Social half hour, 6:30 pm Dinner, 7:00 pm Meeting will be called to order.
Location: DoubleTree by Hilton Philadelphia Airport (Across Rt. 291 from the Sheraton) located at 4509 Island Ave Philadelphia, PA (Island Ave and Route 291), Call 215-365-4150 for directions.

To register or for more details, please contact us or the AACE Delaware section.

Adroit to Present a CMAA Webinar on May 9, 2019

Please join Adroit’s Amin Terouhid, Ph.D., PE and Maryam Mirhadi, Ph.D., PMP for the following CMAA webinar:

Topic: Performing Project Schedule Constructibility Reviews: What to Look For

Abstract:

An important question that needs to be answered once a project schedule is prepared is how a project team can ensure the schedule is prepared in an appropriate and a reasonable manner. Schedule constructibility reviews are expected to answer such questions. Such reviews aim to build confidence in project schedules by evaluating the schedules and creating a basis for further improvements. This webinar will discuss the main considerations in reviewing construction project schedules and identifies the main areas for review and assessment.

Webinar Date: May 9, 2019 @ 2-3 pm EDT

Provided by: Construction Management Association of America (CMAA)

Register now!

Adroit will be providing a training seminar on risk management at the 2019 AACE International Conference & Expo

Adroit will be providing the following training seminar at the 2019 AACE International Conference & Expo in New Orleans, LA on June 14 and June 15, 2019: Decision & Risk Management Professional (DRMP) Certification Exam Preparation.

This seminar is designed to help professionals study for AACE International’s (AACE) certification in Decision and Risk Management (DRM); and to provide a summarized review of relevant topics considered essential for DRMP knowledge. The selected topics are those outlined in AACE International’s Recommended Practice 11R-88 —Required Skills and Knowledge of Cost Engineering— and in AACE International’s Skills and Knowledge of Cost Engineering. This seminar is structured in a concise, systematic, and straightforward lecture format and covers primarily key topics in investment decision-making and risk management. The course material contains tutorials, exercises, and memo-writing assignment; and covers the key skills and knowledge used by DRM professionals.

Learning Objectives and Measurement

-To prepare and equip DRM professionals who are preparing to take the AACE International
DRMP certification examination with the knowledge and skills essential for DRMP knowledge
-To identify, understand and explore the Decision and Risk Management (DRM) processes
within the Total Cost Management Framework
-To describe how each of the Decision and Risk Management (DRM) processes can be
planned and implemented
-To learn how to apply investment decision-making and risk management practices under
different circumstances

Content

In covering investment decision-making, topics such as the structuring, evaluation, agreement, and implementation processes will be discussed and tools and techniques of decision making will be explored. Other key topics that will be covered as part of investment decision-making module are as follows:
-Cost vs. pricing: concepts, classifications, tools and techniques
-Lifecycle costs: project and asset
-Monetary versus opportunity costs
-Economic and financial analysis
-Engineering economics
-Decision-making terminology and concepts
-Basic concepts in probability and statistics
-Decision modeling and analysis

In covering risk management, topics such as plan risk management, assessment, treatment,
and control will be addressed. Other key topics that will be covered as part of the risk
management module are as follows:
-Risk management terminology and concepts
-Risk and uncertainty: concepts, classifications, tools and techniques
-Risk identification
-Risk assessment
-Risk analysis: qualitative and quantitative
-Sensitivity and decision-tree analysis
-Risk treatment: risk response strategies
-Risk monitoring, control, and reporting
-Specific Risk Management

Agenda

  1. Investment decision-making – Day 1
    Morning session:
    1. Introduction to TCM and its essential knowledge areas
    2. AACE International’s Canons of Ethics
    3. Structuring, evaluation, agreement, and implementation processes
    4. Cost vs. pricing: concepts, classifications, tools and techniques
    Afternoon session:
    5. Lifecycle costs: project and asset
    6. Monetary versus opportunity costs
    7. Economic and financial analysis
    8. Engineering economics
    9. Decision-making terminology and concepts
    10. Basic concepts in probability and statistics
    11. Decision modeling and analysis

    B. Risk Management – Day 2
    Morning session:
    12. Risk management terminology and concepts
    13. Risk and uncertainty: concepts, classifications, tools and techniques
    14. Plan risk management
    15. Risk identification
    Afternoon session:
    16. Risk assessment
    17. Risk analysis: qualitative and quantitative
    18. Sensitivity and decision-tree analysis
    19. Risk treatment: risk response strategies
    20. Risk monitoring, control, and reporting
    21. Specific Risk Management 

Instructor: Amin Terouhid, Ph.D., PE

Dr. Terouhid has served as a project management expert since 2003, and is currently a principal consultant at Adroit Consultants, LLC.  He has received a Ph.D. in construction management from the University of Florida, and holds the following professional certificates: Professional Engineer (P.E.) – Texas, Project Management Professional (PMP), Decision and Risk Management Professional (DRMP), and Planning and Scheduling Professional (PSP).

Dr. Terouhid’s expertise in project management is focused on project planning and control, cost engineering, risk management, and project claim analysis. His experience also includes forensic construction claims, and he has experience serving as an expert in assessing construction claims.  He is the author of AACE Recommended Practices 89R-16, 92R-17, and 91R-16, and the recipient of the 2018 AACE Technical Excellence Award.

For more information and to register, please see check out this link.

Variation and Variation Orders: Important Considerations

Introduction

A variety of reasons may increase or decrease the amount of work required by a contract. These increases or decreases are either directed or constructive. This article briefly describes each of these main categories of variation. It also outlines the potential implications of variations and variation orders from the time and cost management perspectives.

In general, owners have the contractual right to make changes to the work outlined in the original contract. The terms variations, modification, and changes are often used interchangeably.

Variation types

Since variations not only impact contract scope of work but also they potentially have time and cost implications, it is important to identify various types of variations and recognize potential effect of each type of variation on contracts. Examples of the most common variations include:

  • Changes in means and methods or material to be installed
  • Differing or unforeseen site conditions not envisioned in the original contract price
  • Modifications that change the planned work sequence as originally envisioned
  • Changes to the scope of work due to constructability issues or conflicts between work elements
  • Changes in plans and specifications
  • Corrections made due to errors or omissions
  • Modifications as a result of the actions or inactions of third-parties

Directed variations

A directed variation is issued when the owner specifically directs the contractor to make a change. This type of variation may or may not affect the contract price. A directed variation that influences only the schedule is an example of a directed variation with no effect on the contract price. As another example, a directed variation that impacts a project’s configuration, work sequence, or space requirements may adversely influence labor and equipment productivity on-site. A directed variation with cost impact may reduce or add the contract price. Directed variations are typically not complicated because the owner specifically directs the contractor to make a change and as such, directed variations are easier to deal with.

Constructive variations

Constructive variations, on the other hand, occur as a result of non-owner-directed events that implicitly necessitate a variation. Unlike directed variations, the owner does not specifically direct the contractor to make a change in case of a constructive variation. Instead, as a result of non-owner-directed events or actions or inactions of the owner, the contractor is forced to modify the scope specified in the contract or incur additional costs. Typically, constructive variations are not easy to recognize because they generally occur due to non-owner-directed events or circumstances. In addition, in case of a constructive variation, the owner does not typically have an explicit acknowledgment of a variation to the original scope of work set forth in the contract. Examples of the most common types of constructive variations include:

  • Verbal communications that implicitly necessitate making changes
  • Deficient drawings or specifications
  • Ambiguity in architect-provided responses to information requests
  • Differing site conditions
  • Over-inspection

Implications

Although deductive variations exist, variations typically increase contract prices. This increase is due to increases to direct material, labor, and equipment prices. Nevertheless, the impacts of variations are often not limited to direct costs. Variations often result in the loss of efficiency and as such, the adverse effects of variations need to closely be examined to ensure their consequences are fully evaluated.

Conclusion

It is important to identify variations in a timely manner, especially in case of constructive variations whose effects are not explicit and readily recognizable. The reasons for each variation need to properly be identified and documented in proper tracking logs. Moreover, the effects and implications of each variation need to properly be documented to ensure sufficient documentation and historical records are readily accessible to substantiate contractual entitlements.


Author: Dr. Maryam Mirhadi, PMP, PSP | CEO and Principal Consultant

 If your project has been affected by multiple variations or variation order and they have adversely affected labor or equipment productivity on-site, or if you are interested to investigate the extent of time and cost impacts due to variation orders, Adroit will be able to assist in assessing these impacts. For more information, please contact us.

Evaluating Activity Logic Relationships: A New Perspective

Project schedules are among the key project artifacts that are used as a basis for project control. They are one of the most effective ways that a project team can use to coordinate their activities. Project schedules play a key role in making such coordination and to facilitate achieving a project’s time objectives. However, project schedules can play this role only if they are prepared in a reasonable manner. The reasonableness of project schedules can be evaluated from various perspectives including consistency, clarity, completeness, and feasibility of construction plans.

The following are some of the main considerations that need to be given to developing project schedules to ensure they are reasonable:

  • The schedule is complete and entails all the activities that are needed to successfully implement the scope of work
  • Proper logical relationships (including finish-to-start, start-to-start-, start-to-finish, or finish-to-finish relationships along with proper lag and lead values) are used in creating the project network
  • An appropriate combination and choosing of activity relationships (including mandatory, preferential, and scenario-based relationships) are created to define activity dependencies
  • The schedule accounts for the technical, physical, and technological constraints of performing the work
  • The schedule meets proper contractual milestones, identifies all interim and ultimate contractual deliverables, and satisfies time and resource constraints outlined in the contract
  • The schedule is clear, reasonable, and complete
  • Different sections of the schedule are consistent in terms of the timeline, work priorities, and work sequence

As noted above, activity dependencies are among the key main considerations in developing well-prepared schedules. A project network not only contains project activities but also defines activity dependencies (also known as activity ties or activity relationships). A variety of activity dependencies exists, and activity relationships are categorized in different ways.

Activity dependencies can be categorized based on the nature of dependencies that exist between project activities. From this perspective, activity dependencies are often categorized into the following two types of dependencies:

  • Mandatory dependency (also known as hard logic): This relationship represents a dependency that is necessary or inherent in the nature of the work.
  • Discretionary dependency (also known as soft, preferred, or preferential logic): This type of dependency represents preferential logic that is used to establish a desired sequence of work despite alternative sequences that are acceptable.

It is important to note, however, that mandatory and discretionary relationships are not the only activity relationships that are used in project schedules. To better identify activity dependencies, it is suggested that activity dependencies are further categorized as shown in Figure 1.

Figure 1. Activity relationship types

As this figure shows, mandatary relationships can further be broken down into the following three types:

  • Imposed relationships: Imposed relationships are those relationships that need to be built into a project schedule to satisfy legal, regulatory or contractual requirements. An example includes a contractually-imposed requirement that mandates using a phased approach (where a portion of work has to be implemented after another portion) in completing certain elements of work.
  • Physical relationships: This relationship represents a dependency that has to be established between two or more activities due to the nature of the work. An example of dependencies that are inherent in the nature of the work is the need to place a foundation first before erecting a column atop the foundation.
  • Safety relationships: This relationship represents a dependency that has to be established between two or more activities to ensure safety considerations are accounted for in sequencing project activities. An example of a safety relationship is the need to avoid concurrent logic in scheduling two activities that cannot be undertaken simultaneously because of safety concerns (e.g., a crew that cannot work on the second floor of a building because of the ongoing work on the first floor).

Sometimes, project scheduling professionals use scenario-based relationships to define dependencies between project activities. The current article uses the term scenario-based to characterize these relationships because depending on the implementation strategy chosen to execute a project, scenario-based relationships may or may not be used in defining work sequences. Resource relationships are examples of scenario-based relationships. Resource relationships are often added to the project schedule due to resource management concerns (e.g., resource constraints).

For example, if a contractor needs to implement two non-causally-related activities, each of which requiring a crane, the contractor may decide to add a finish-to-start relationship between the two activities if the contractor has only one crane in its possession. In this example, the two activities are not causally related; however, based on the scenario described, the contractor has established a relationship between these two activities to satisfy its resource constraint. If the contractor had two cranes in its possession, defining a dependency between the two activities was unnecessary because as noted above, the activities are presumably not causally linked. Therefore, it is reasonable to recognize the above-referenced activity relationship as a scenario-based relationship because these relationships may or may not be used depending on the implementation scenario or strategy used.

Not all scenario-based relationships are resource relationships; therefore, in Figure 1, scenario-based relationships are broken down into the two main types of resource relationships and others. An example of other scenario based dependencies includes a dependency that is established between two activities based on an assumed what-if scenario to manage a likely change in the project scope of work. This relationship may or may not be required to be established depending on whether the change occurs or not.

The last category of activity relationships is improper relationships that consist of redundant, incorrect logic, and logic loops. Incorrect logic relationships can further be categorized into errors, missing logic, out-of-sequence, and improper use of lags and leads. These relationships will be described in greater depth in a future article.

Planning and scheduling professionals need to make informed decisions in selecting and using the right relationship type. In general, it is suggested that only mandatory relationships are used in developing project schedules unless the use of discretionary or scenario-based relationships is justified. Similarly, the use of preferential relationships may not be appropriate in demonstrating that a schedule follows a reasonable logic. It is recommended that, instead of resource constraints, planning and scheduling professionals use resource leveling techniques to ensure the schedule is not bounded by too many dependencies that could have otherwise been accounted for.

Assessing activity relationships is critical in preparing or investigating time extension requests or delay assessments because a proper delay analysis has to be based on a reasonable schedule. A delay analysis based on a project schedule that contains questionable activity relationships is defective. Project planning and scheduling, forensic scheduling experts, and claim management professionals need to ensure project schedules are free of improper relationships. Otherwise, the schedule will not be reliable or reasonable and it may not serve its purpose.


Author: Dr. Amin Terouhid, PE, PMP, PSP | Principal Consultant

If you are interested to find out more about the main considerations in developing or evaluating project schedules, please contact us. Adroit’s consultants have demonstrated their expertise in developing, updating, constructability review, and forensic evaluation of project schedules and will be able to assist. You may also be interested to read the following articles:

Schedule constructability review, what does it entail?

Adroit to Present a CMAA Webinar on February 21, 2019

Please join Adroit’s Amin Terouhid, Ph.D., PE and Maryam Mirhadi, Ph.D., PMP for the following CMAA webinar:

Topic: Adverse effects of schedule deficiencies from the claim administration perspective

Abstract:

Project schedules provide a basis for communication, execution, monitoring and controlling, and reporting and offer a platform for measuring project progress and performance. In addition, courts bank on project schedules to assess time extensions or time-related compensation requests. As such, project time schedules are one of the key inputs without which many construction claims cannot properly be prepared or investigated. Construction contractors should give proper attention to preparing detailed and reasonable project schedules throughout the project to ensure the project schedules remain acceptable and reliable over the course of the project, and they reasonably represent the plans as well as the actual progression of work. In this webinar, some of the main issues with project schedules, especially those that adversely affect claim administration efforts, will be discussed.

Webinar Date: Feb 21 @ 2-3 pm EDT

Provided by: Construction Management Association of America (CMAA)

Register now!

Assessing Concurrent Delays: A Challenging Exercise

Concurrent delays frequently occur in construction projects, especially in complex construction projects in which various contracting parties implement and are responsible for a variety of activities over the project life cycle. Assessing concurrent delays is among the most challenging forensic delay analysis practices because, contractual, legal, and technical considerations add several layers of complexity to cases of concurrent delays.

A project network not only contains project activities but also defines activity dependencies (also known as activity ties or activity relationships). Two or more delayed activities in a project network may be identified to be concurrent when they, partly or wholly, overlap one another. Therefore, a project network is a key tool to identify what activities partly or wholly overlap and what their dependencies are. Courts, boards of contract appeals, and experts, however, are inconsistent in their approach to defining concurrent delays.

Definitions

Experts rely on different references for the definition of concurrent delays. In the United States, one of the technical references that is commonly-cited in delay claims is AACE International Recommended Practice (RP) 10S-90, entitled Cost Engineering Terminology. RP 10S-90, however, does not offer one single definition of concurrent delays. Two of these definitions are provided below (AACE International, 2017, p. 21);

(1) Two or more delays that take place or overlap during the same period, either of which occurring alone would have affected the ultimate completion date.

(2) Concurrent delays occur when there are two or more independent causes of delay during the same time period. The “same” time period from which concurrency is measured, however, is not always literally within the exact period of time. For delays to be considered concurrent, most courts do not require that the period of concurrent delay precisely match. The period of “concurrency” of the delays can be related by circumstances, even though the circumstances may not have occurred during exactly the same time of period.

Another commonly-cited technical reference is AACE International RP 29R-03, entitled forensic schedule analysis. RP 29R-03 identifies that the following tests must be proven to ensure concurrent delays exist (AACE International, 2011):

  1. Two or more unrelated, independent delays exist. One of these delays can a delay arisen from a force majeure event.
  2. None of the delays identified in Step 1 can be a voluntary delay.
  3. Not all delayed activities identified in Step 1 are the responsibility of only one contracting party.
  4. The project completion date would have been delayed in the absence of any of the delays identified in Step 1.
  5. The delayed work has to be substantial (i.e., not easily correctable).

The meaning of concurrent delay is different in the English Law. The following are two excerpts that help illustrate the meaning of concurrent delay under the English law:

  • True concurrent delay is the occurrence of two or more delay events at the same time, one an Employer Risk Event, the other a Contractor Risk Event, and the effects of which are felt at the same time… In contrast, a more common usage of the term ‘concurrent delay’ concerns the situation where two or more delay events arise at different times, but the effects of them are felt at the same time. In both cases, concurrent delay does not become an issue unless each of an Employer Risk Event and a Contractor Risk Event lead or will lead to Delay to Completion. Hence, for concurrent delay to exist, each of the Employer Risk Event and the Contractor Risk Event must be an effective cause of Delay to Completion (not merely incidental to the Delay to Completion) (The Society of Construction Law, 2017).
  • Concurrent delay is used to denote a period of project overrun which is caused by two or more effective causes of delay which are of approximately equal causative potency (Marrin, 2012).

Entitlements

Concurrent delays typically entitle contractors to time extension, but not time-related delay damages. In other words, if a contractor is able to demonstrate the presence of concurrent delays, it may be entitled solely to time extension for the net period of the concurrent delay.

It is important to note that in some cases, two or more delays occur concurrently (overlap one another to some extent), all of which are the responsibility of one single contracting party. In that case, the net effect of the concurrent delays have to be taken into account in assessing delays. For instance, if two overlapping 5 day owner-caused delays exist, entirely overlapping each other, the contractor is only entitled to a single 5-day time extension. As another example, if a contractor is found to be responsible for a 10-day delay, 7 of which are concurrent with another contractor-caused delay, the contractor is ultimately responsible for 10 days of delay, not 17 days.

In a similar way, if both an owner and a contractor concurrently contribute to the occurrence of a critical path delay (i.e., a delay that ultimately results in the delay of the project completion date), none of the contracting parties is typically entitled to collecting delay damages from the other party unless delay responsibilities can be apportioned between the parties.

In the event of a concurrent delay, the time impact of a contractor-caused delay on a project’s longest path may be greater in magnitude than the time impact of an owner-caused delay. Under such circumstances, it is sound to expect that the owner is entitled to collect delay damages for the excess impact. Conversely, the time impact of an owner-caused delay on a project’s longest path may exceed the time impact of a contractor-caused delay. Thus, it is critical to perform forensic schedule analysis and closely examine the cases of concurrency to properly allocate responsibilities for delays and specify proper entitlements.

Although definitions of concurrent delays exist in the literature, any assessment of concurrent delays has to start with performing a liability analysis (i.e., entitlement assessment) based on contractual rights and duties of contracting parties. Performing such liability assessments is necessary because the contract may specify how the cases of concurrency are characterized and how they are supposed to be assessed and/or dealt with.

The lack of clear contractual procedures for concurrent delays increases the likelihood of delay-related disputes. As noted above, courts, boards of contract appeals, and experts are inconsistent in their approach to characterizing and assessing concurrent delays. Therefore, it is important that the parties exercise due diligent in preparing unambiguous contract language that facilitates successful resolution of delay-related matters before they result in a conflict.

Moreover, if a party is in a position to negotiate over the provisions of a contract, it is recommended that it negotiates to reach an agreement, prior to signing the contract, on definitions of and procedures for assessing various types of delays including concurrent delays. Such definitions and procedures combined with the use of sound forensic schedule analysis techniques can play key roles in minimizing and/or successful resolution of delay-related disputes.

References:

AACE International. (2011). Recommended Practice No. 29R-03 Forensic Schedule Analysis. Morgantown, WV, USA: AACE International®.

AACE International. (2017). Recommended Practice No. 10S-90 Cost Engineering Terminology. Morgantown, WV, USA: AACE International®.

Marrin, J. (2012). Concurrent Delay Revisited 2. Presented at the Society of Construction Law Meeting, London, England (December 4, 2012).

The Society of Construction Law. (2017). Delay and Disruption Protocol, 2nd edition (DDP2). Retrieved from https://www.scl.org.uk/sites/default/files/SCL_Delay_Protocol_2nd_Edition.pdf

 

Author: Dr. Amin Terouhid, PE, PMP, PSP | Principal Consultant

 Amin Terouhid is a construction claims expert and a Principal Consultant with Adroit Consultants, LLC. He was a recipient of the 2018 AACE Technical Excellence Award.

 

Note: If you are interested to find out more about the main considerations in assessing concurrent delays, please contact us. Adroit’s consultants have demonstrated their expertise in performing delay analysis and will be able to assist. You may also be interested to read the following articles:

Adverse effects of schedule deficiencies on claim administration

Mandatory, Discretionary, Scenario-based, and Improper Activity Relationships: Theoretical and Practical Considerations

Project networks play important roles in carrying out construction activities in a timely manner, and they are among the key means of communication that project teams use to coordinate their efforts throughout the process of construction. Project networks are also among the key project artifacts that are used for preparing or investigating time-related claims and for determining entitlements to time extensions and/or delay damages. Therefore, it is important to have a more in-depth knowledge of activity dependencies and their types.

Activity dependencies are among the key characteristics and building blocks of project schedules. A project network not only contains project activities but also defines activity dependencies (also known as activity ties or activity relationships). A variety of activity dependencies exists, and activity relationships are categorized in different ways.

The four main types of activity dependencies include Finish-to-Start (FS), Start-to-Start (SS), Start-to-Finish (SF), and Finish-to-Finish (FF). The following briefly describes these relationship types:

  • Finish-to-Start (FS): The successor activity cannot start unless the predecessor activity finishes.
  • Start-to-Start (SS): The successor activity cannot start unless the predecessor activity starts.
  • Start-to-Finish (SF): The successor activity cannot finish unless the predecessor activity starts.
  • Finish-to-Finish (FF): The successor activity cannot finish unless the predecessor activity finishes.

Activity dependencies can also be categorized based on the nature of dependencies that exist between project activities. From this perspective, activity dependencies are often categorized into the following two types of dependencies:

  • Mandatory dependency (also known as hard logic): This relationship represents a dependency that is necessary or inherent in the nature of the work.
  • Discretionary dependency (also known as soft, preferred, or preferential logic): This type of dependency represents preferential logic that is used to establish a desired sequence of work despite alternative sequences that are acceptable.

To better identify activity dependencies, it is suggested that activity dependencies are categorized as shown in Figure 1.

Figure 1. Activity relationship types

As this figure shows, mandatary relationships can further be broken down into the following three types:

  • Imposed relationships: Imposed relationships are those relationships that need to be built into a project schedule to satisfy legal, regulatory or contractual requirements. An example includes a contractually-imposed requirement that mandates using a phased approach (where a portion of work has to be implemented after another portion) in completing certain elements of work.
  • Physical relationships: This relationship represents a dependency that has to be established between two or more activities due to the nature of the work. An example of dependencies that are inherent in the nature of the work is the need to place a foundation first before erecting a column atop the foundation.
  • Safety relationships: This relationship represents a dependency that has to be established between two or more activities to ensure safety considerations are accounted for in sequencing project activities. An example of a safety relationship is the need to avoid concurrent logic in scheduling two activities that cannot be undertaken simultaneously because of safety concerns (e.g., a crew that cannot work on the second floor of a building because of the ongoing work on the first floor).

Sometimes, project scheduling professionals use scenario-based relationships to define dependencies between project activities. The current article uses the term scenario-based to characterize these relationships because depending on the implementation strategy chosen to execute a project, scenario-based relationships may or may not be used in defining work sequences. Resource relationships are examples of scenario-based relationships. Resource relationships are often added to the project schedule due to resource management concerns (e.g., resource constraints).

For example, if a contractor needs to implement two non-causally-related activities, each of which requiring a crane, the contractor may decide to add a finish-to-start relationship between the two activities if the contractor has only one crane in its possession. In this example, the two activities are not causally related; however, based on the scenario described, the contractor has established a relationship between these two activities to satisfy its resource constraint. If the contractor had two cranes in its possession, defining a dependency between the two activities was unnecessary because as noted above, the activities are presumably not causally linked. Therefore, it is reasonable to recognize the above-referenced activity relationship as a scenario-based relationship because these relationships may or may not be used depending on the implementation scenario or strategy used.

Not all scenario-based relationships are resource relationships; therefore, in Figure 1, scenario-based relationships are broken down into the two main types of resource relationships and others. An example of other scenario based dependencies includes a dependency that is established between two activities based on an assumed what-if scenario to manage a likely change in the project scope of work. This relationship may or may not be required to be established depending on whether the change occurs or not.

The last category of activity relationships is improper relationships that consist of redundant, incorrect logic, and logic loops. Incorrect logic relationships can further be categorized into errors, missing logic, out-of-sequence, and improper use of lags and leads. These relationships will be described in greater depth in a future article.

Planning and scheduling professionals need to make informed decisions in selecting and using the right relationship type. In general, it is suggested that only mandatory relationships are used in developing project schedules unless the use of discretionary or scenario-based relationships is justified. Similarly, the use of preferential relationships may not be appropriate in demonstrating that a schedule follows a reasonable logic. It is recommended that, instead of resource constraints, planning and scheduling professionals use resource leveling techniques to ensure the schedule is not bounded by too many dependencies that could have otherwise been accounted for.

Assessing activity relationships is critical in preparing or investigating time extension requests or delay assessments because a proper delay analysis has to be based on a reasonable schedule. A delay analysis based on a project schedule that contains questionable activity relationships is defective. Project planning and scheduling, forensic scheduling experts, and claim management professionals need to ensure project schedules are free of improper relationships (i.e., redundant, incorrect logic, and logic loops). Otherwise, the schedule will not be reliable or reasonable and it may not serve its purpose.

Author: Dr. Amin Terouhid, PE, PMP, PSP | Principal Consultant

 

Note:

If you are interested to find out more about the main considerations in developing or evaluating project schedules, please contact us. Adroit’s consultants have demonstrated their expertise in developing, updating, constructability review, and forensic evaluation of project schedules and will be able to assist. You may also be interested to read the following articles:

Adverse effects of schedule deficiencies on claim administration

Schedule constructability review, what does it entail?

The Key Issues with Dangling Activities