9.2 Activity Definition, Precedence & Dependencies

9.2 Activity Definition, Precedence & Dependencies

Quick Summary: Once the Work Breakdown Structure (WBS) decomposes scope into Work Packages, project schedulers translate those deliverables into discrete, executable Schedule Activities. Described by action-oriented verb-noun phrases, activities consume calendar time, labor, and capital resources. Under the Precedence Diagramming Method (PDM / Activity-on-Node), activities are sequenced using four fundamental logical dependencies: Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF). Schedulers must differentiate between non-negotiable mandatory dependencies (hard logic) and adjustable discretionary dependencies (soft logic), while prudently applying lags (delays) and leads (accelerations) without compromising schedule integrity.

---

1. Decomposing Work Packages into Scheduled Activities

In the Total Cost Management process, scheduling begins where WBS decomposition terminates. Work packages establish what deliverables must be produced and define the budgetary container. However, work packages cannot be executed directly on a jobsite or engineering office floor without defining the specific, ordered sequence of operational tasks required to build them.

An Activity (also called a Task) is a scheduled element of work that:

1. Has a definite, measurable beginning and end.
2. Consumes calendar duration.
3. Requires the expenditure of human effort, machinery, materials, or money.
4. Produces an interim work product or milestone contributing to the work package deliverable.
5. Can be assigned logical predecessors and successors in a network.

Syntactical Architecture: Nouns vs. Verbs

Whereas WBS elements are titled using nouns (1.3.2 Sludge Feed Pumps), schedule activities are strictly titled using action verbs combined with specific objects:

• "Excavate pump foundation pit"
• "Set pump baseplate on foundation pads"
• "Grout pump baseplate and align shafts"
• "Install suction and discharge spool piping"
• "Terminate 480V motor power leads"
• "Conduct uncoupled motor rotation test"

+-----------------------------------------------------------------------------------+
|              FROM WBS DELIVERABLES TO SCHEDULED CPM ACTIVITIES                    |
|                                                                                   |
|  WBS LEVEL 4 WORK PACKAGE:                                                        |
|  WP 1.3.1.2 Centrifuge Machine Rigging & Alignment                                |
|  (Budget: $85,000 | Accountable Owner: Mechanical Superintendent)                 |
|                                                                                   |
|  DECOMPOSED CPM SCHEDULE ACTIVITIES:                                              |
|  +---------+------------------------------------+----------+--------------------+ |
|  | ACT ID  | ACTIVITY DESCRIPTION (VERB + NOUN) | DURATION | PREDECESSORS       | |
|  +---------+------------------------------------+----------+--------------------+ |
|  | ACT-100 | Rig and place centrifuge base skids| 3 Days   | Foundation Cured   | |
|  | ACT-110 | Install vibration isolator mounts  | 2 Days   | ACT-100            | |
|  | ACT-120 | Precision optical laser alignment  | 4 Days   | ACT-110            | |
|  | ACT-130 | Torque anchor bolts to 450 ft-lbs  | 1 Day    | ACT-120            | |
|  | ACT-140 | QC Sign-off Alignment Acceptance   | 0 Days   | ACT-130 (Milestone)| |
|  +---------+------------------------------------+----------+--------------------+ |
+-----------------------------------------------------------------------------------+

---

2. Activity Attributes & The Role of Milestones

To construct an enforceable Critical Path Method (CPM) schedule, each activity is enriched with technical and administrative data known as Activity Attributes:

• Activity Identifier (ID): Unique alphanumeric code (e.g., ACT-120) that remains permanent throughout the project lifecycle.
• Activity Description: Clear verb-noun phrase specifying the physical task.
• Original Duration (OD): Estimated working time required to complete the activity under normal conditions using standard crew sizes.
• Activity Calendar: Specific working calendar governing the task (e.g., 5-day 8-hour workweek, 6-day 10-hour construction shift, or 7-day continuous concrete curing calendar).
• Resource Requirements: Quantities of craft labor trades, heavy equipment, and bulk materials required.
• Predecessor & Successor Links: Logical dependencies connecting the activity to adjacent network tasks.
• Constraints: External date limits (e.g., Start No Earlier Than, Finish No Later Than).

Milestones: Zero-Duration Anchor Points

A Milestone is a significant event in the project lifecycle that has zero duration ($D = 0$) and consumes no resources.

• Purpose: Milestones mark the completion of major deliverables, phase transitions, contractual commitment points, regulatory approvals, or financial billing gates.
• Network Function: In CPM logic, a milestone serves as an immediate successor to finishing activities and an immediate predecessor to subsequent phases.
• Examples: "Contract Award Executed", "Foundation Concrete Placement Complete", "Substation Energization Approved", "Substantial Completion Achieved".

---

3. The Four Dependency Classifications

Before drawing network arrows, project controls practitioners must rigorously analyze why two activities are linked. AACE International categorizes activity dependencies into four distinct classes:

+-----------------------------------------------------------------------------------+
|                         THE FOUR DEPENDENCY CLASSIFICATIONS                       |
+---------------+-------------------------------------------------------------------+
| MANDATORY     | Hard logic; physical laws of nature, structural safety, or        |
| (Hard Logic)  | contractual mandates. Cannot be altered or bypassed.              |
+---------------+-------------------------------------------------------------------+
| DISCRETIONARY | Soft / preferential logic; based on best practices, historical    |
| (Soft Logic)  | preferences, or resource availability. Can be modified to compress|
+---------------+-------------------------------------------------------------------+
| EXTERNAL      | Precedence driven by entities outside project team control        |
|               | (e.g., environmental permits, owner utility shutdowns, vendor QA)|
+---------------+-------------------------------------------------------------------+
| INTERNAL      | Precedence completely within the control of the project team      |
|               | (e.g., assembly sequence, design document inter-discipline reviews|
+---------------+-------------------------------------------------------------------+

1. Mandatory Dependencies ("Hard Logic")

• Definition: Dependencies that are inherently required by the physical nature of the work or by strict contractual/legal mandates.
• Physical Causality: You cannot pour concrete into a footing until the trench is excavated and the reinforcing steel rebar cage is placed. You cannot erect structural steel on elevated tiers until base connections are bolted and grouted.
• Immutability: Hard logic cannot be overridden during schedule optimization or schedule compression. Violating mandatory logic creates physical hazards, structural failures, or contract breaches.

2. Discretionary Dependencies ("Soft Logic" / "Preferential Logic")

• Definition: Dependencies established by the project team based on preferred construction sequencing, institutional trade knowledge, crew sharing, or equipment optimization.
• Flexibility: For example, on a housing development, a builder may choose to complete Building A before starting Building B so that a single framing crew can move sequentially between units. While this optimizes crew efficiency, it is not physically impossible to frame both buildings simultaneously if a second crew is hired.
• Compression Target: When a project faces schedule delays, discretionary dependencies are the primary target for schedule compression (e.g., restructuring sequential work into parallel execution via fast-tracking).

3. External Dependencies

• Definition: Relationships between project activities and external events or third parties outside the direct jurisdiction of the project team.
• Examples: Obtaining an EPA discharge permit before starting outfall dredging; delivery of owner-furnished high-voltage transformers by an electrical utility; municipal building inspector sign-off before closing drywall walls.

4. Internal Dependencies

• Definition: Precedence relationships between activities that fall entirely under the direct operational control of the project team.
• Examples: The mechanical piping team waiting for the structural steel crew to torque pipe rack trusses before hanging piping spools.

---

4. Precedence Diagramming Method (PDM / AON) Architecture

The Precedence Diagramming Method (PDM)—also known as Activity-on-Node (AON)—is the universal industry standard for CPM schedule development, utilized across all major software packages (e.g., Oracle Primavera P6, Microsoft Project).

PDM vs. Arrow Diagramming Method (ADM / AOA)

Historically, critical path scheduling relied on the Arrow Diagramming Method (ADM / Activity-on-Arrow AOA):

• ADM Limitations: In ADM, arrows represented activities, and circular nodes represented milestone events. ADM could model only Finish-to-Start relationships and required artificial, zero-duration "dummy activities" (drawn as dashed arrows) simply to maintain mathematical logic and prevent dual-activity identification conflicts.
• PDM Superiority: In PDM, rectangular nodes represent activities, and connecting arrows represent logical relationships. PDM completely eliminates dummy activities and natively supports four distinct relationship types alongside complex leads and lags.

+-----------------------------------------------------------------------------------+
|                    ADM (ACTIVITY-ON-ARROW) VS. PDM (ACTIVITY-ON-NODE)             |
|                                                                                   |
|  ADM (Obsolete):                                                                  |
|  ( Event 1 ) ------ Activity A (3d) ------> ( Event 2 )                          |
|        \                                      |                                   |
|         \                                     | [DUMMY ARROW: 0d]                 |
|          \                                    v                                   |
|           \------> Activity B (4d) ------> ( Event 3 ) ---> Activity C (2d) --->  |
|                                                                                   |
|  PDM / AON (Modern Standard):                                                     |
|  +----------------+                                                               |
|  |   ACTIVITY A   |                                                               |
|  |   Duration: 3d |----+                                                          |
|  +----------------+    |                                                          |
|                        +-----> +----------------+                                 |
|  +----------------+    |       |   ACTIVITY C   |                                 |
|  |   ACTIVITY B   |----+       |   Duration: 2d |                                 |
|  |   Duration: 4d |            +----------------+                                 |
|  +----------------+                                                               |
|  [No dummy activities required; nodes hold rich metadata]                          |
+-----------------------------------------------------------------------------------+

---

5. The Four Precedence Relationship Types

PDM enables four mathematical relationship types between a predecessor (P) and a successor (S).

+-----------------------------------------------------------------------------------+
|                     THE FOUR PDM PRECEDENCE RELATIONSHIPS                         |
+-------------------+--------------------+------------------------------------------+
| RELATIONSHIP TYPE | NOTATION & LOGIC   | MATHEMATICAL RESTRAINT                   |
+-------------------+--------------------+------------------------------------------+
| Finish-to-Start   | FS                 | ES(Successor) >= EF(Predecessor) + Lag   |
|                   | (Pred must finish) |                                          |
+-------------------+--------------------+------------------------------------------+
| Start-to-Start    | SS                 | ES(Successor) >= ES(Predecessor) + Lag   |
|                   | (Pred must start)  |                                          |
+-------------------+--------------------+------------------------------------------+
| Finish-to-Finish  | FF                 | EF(Successor) >= EF(Predecessor) + Lag   |
|                   | (Pred must finish) |                                          |
+-------------------+--------------------+------------------------------------------+
| Start-to-Finish   | SF                 | EF(Successor) >= ES(Predecessor) + Lag   |
|                   | (Pred must start)  |                                          |
+-------------------+--------------------+------------------------------------------+

1. Finish-to-Start (FS)

• The Classical Link: The successor activity cannot start until the predecessor activity finishes.
• Mathematical Formula: ES(Successor) >= EF(Predecessor)
• Real-World Application: Most common relationship in construction and engineering (comprising >85% of links in high-integrity schedules). Example: Trench excavation (Pred) must finish before pipe laying (Succ) can start.

2. Start-to-Start (SS)

• Parallel Initiation: The successor activity cannot start until the predecessor activity has started.
• Mathematical Formula: ES(Successor) >= ES(Predecessor) + Lag
• Real-World Application: Used to model overlapping, progressive phases. Example: Concrete paving (Succ) can start 2 days after subbase grading (Pred) starts (SS + 2d).

3. Finish-to-Finish (FF)

• Parallel Completion: The successor activity cannot finish until the predecessor activity has finished.
• Mathematical Formula: EF(Successor) >= EF(Predecessor) + Lag
• Real-World Application: Used when final testing, cleanup, or documentation depends on completing physical work. Example: Electrical inspection and testing (Succ) cannot finish until all cable pulling and terminations (Pred) finish (FF + 1d).

4. Start-to-Finish (SF)

• The Inverted Handover: The successor activity cannot finish until the predecessor activity starts.
• Mathematical Formula: EF(Successor) >= ES(Predecessor) + Lag
• Real-World Application: Highly uncommon in practice (<0.1% of links). Used in security shift rotations or IT system cutovers. Example: A legacy environmental monitoring system (Succ) cannot be shut down and decommissioned (finish) until the new SCADA automation system (Pred) starts operational monitoring.

---

6. Quantitative Modeling of Leads and Lags

Precedence logic often requires timing offsets between activities to reflect physical delays or accelerated overlaps.

Lag (Positive Lag: +L)

• Definition: A planned waiting time inserted into a relationship where calendar duration must elapse before the successor can proceed, without consuming resources.
• Mathematical Impact: Delays the Early Start (ES) or Early Finish (EF) of the successor activity: $\text{For an FS link with lag } L: \quad ES_S = EF_P + L$
• Physical Examples:
  • Concrete curing time (FS + 7 days)
  • Industrial coating paint drying time (FS + 24 hours)
  • Marine soil consolidation waiting period (FS + 14 days)

Lead (Negative Lag: -L)

• Definition: An acceleration of the successor activity that allows it to start before the predecessor activity finishes. Modeled mathematically as a negative lag.
• Mathematical Impact: Advances the Early Start of the successor: $\text{For an FS link with lead } L: \quad ES_S = EF_P - L$
• Physical Example: Initiating electrical rough-in 3 days before wall drywall framing is completely finished (FS - 3 days).

+-----------------------------------------------------------------------------------+
|                         LAG VS. LEAD TIMELINE COMPARISON                          |
|                                                                                   |
|  STANDARD FINISH-TO-START (FS with 0 Lag):                                        |
|  [Activity A: 4 Days]                                                             |
|                      [Activity B: 3 Days]                                         |
|                                                                                   |
|  FINISH-TO-START WITH POSITIVE LAG (FS + 2 Days):                                 |
|  [Activity A: 4 Days] ---> [2-Day Lag] ---> [Activity B: 3 Days]                 |
|                                                                                   |
|  FINISH-TO-START WITH LEAD / NEGATIVE LAG (FS - 2 Days):                          |
|  [Activity A: 4 Days]                                                             |
|          [Activity B: 3 Days]  <-- Starts 2 days prior to A's finish              |
+-----------------------------------------------------------------------------------+

---

7. Schedule Integrity Standards & Risks of Distorted Leads and Lags

AACE Recommended Practice 29R-03 (Forensic Schedule Analysis) and RP 52R-06 (Time Impact Analysis) establish rigorous standards regarding the use of leads and lags. Improper application can corrupt network calculations, invalidate Total Float, and obscure true critical paths.

Why Negative Lags (Leads) Are Discouraged

1. Logical Incoherence during Execution: If Activity A is delayed in the field, a negative lag (FS - 3) creates an absurd mathematical condition where Activity B's early start moves forward even though the predecessor is falling behind.
2. Masking Out-of-Sequence Work: Leads hide the physical reality that work is being executed out of sequence without formal engineering sign-off.
3. Better Modeling Alternative: Replace leads by decomposing the predecessor into two discrete activities and linking them via a standard FS link (e.g., divide Framing into Phase 1 Framing and Phase 2 Framing).

Why Excessive Positive Lags Are Penalized

1. Opaque Resource Planning: Lags consume calendar time but hide the reason for the delay. Project managers cannot assign labor, equipment, or budgets to a "lag arrow."
2. Calendar Inconsistencies: If an activity is on a 5-day calendar but the lag represents concrete curing (which cures 7 days a week including weekends), software lag defaults can introduce multi-day scheduling errors.
3. Better Modeling Alternative: Model significant waiting periods as explicit, zero-resource schedule activities: "Concrete Curing - Foundation Substructure" (Duration: 7 Days, 7-Day Calendar).

---

8. Step-by-Step Worked Sequencing Example: Pumping Station

Scenario: A cost technician must sequence the installation of a high-pressure booster pump assembly. The engineering team defines six activities:

1. ACT-10: Pour Reinforced Pump Foundation Pad ($D = 2$ days)
2. ACT-20: Concrete Curing Period ($D = 7$ days, mandatory cure before loading)
3. ACT-30: Erect Structural Base Frame ($D = 3$ days)
4. ACT-40: Anchor & Align Pump-Motor Skid ($D = 4$ days)
5. ACT-50: Install Suction & Discharge Manifold Piping ($D = 5$ days)
6. ACT-60: Hydrostatic Pressure Testing of Piping ($D = 2$ days)

Determining Precedence Logic & Links

• ACT-10 to ACT-20: Mandatory Hard Logic. ACT-20 is modeled as an explicit activity ($FS = 0$).
• ACT-20 to ACT-30: Mandatory Hard Logic. Base frame cannot be bolted down until concrete cures ($FS = 0$).
• ACT-30 to ACT-40: Mandatory Hard Logic. Frame must be erect before skid placement ($FS = 0$).
• ACT-40 to ACT-50: Discretionary Soft Logic. Mechanical superintendent allows piping fabrication to start 2 days after skid alignment begins using a Start-to-Start link with a 2-day lag ($SS + 2\text{d}$), but piping cannot finish until skid alignment is 100% complete ($FF + 2\text{d}$). This is a classic SS/FF ladder logic pair.
• ACT-50 to ACT-60: Mandatory Hard Logic. All piping installation must be 100% complete before hydrostatic pressure testing can begin ($FS = 0$).

---

9. Comparative Matrix: Dependency Types & Logic Links

---

10. CCT Exam Watch: High-Yield Precedence & Sequencing Traps

1. The Lead vs. Lag Sign Convention: A positive lag delays the successor ($+$ sign, pushes start date out). A negative lag (lead) accelerates the successor ($-$ sign, pulls start date forward). Schedulers frequently mix up the mathematical signs on exam day.
2. The Dummy Activity Trick: If an exam question asks "How many dummy activities are required in a Precedence Diagramming Method (PDM) network?", the answer is ZERO. Dummy activities are utilized exclusively in the obsolete Arrow Diagramming Method (ADM / AOA).
3. Start-to-Finish (SF) Rarity: Whenever a question describes two activities and asks which relationship is most appropriate, SF is virtually never the correct operational answer unless the scenario explicitly involves a continuous security/system handover where the old system cannot shut down until the new system starts.
4. Mandatory vs. Discretionary Identification: If a scenario states "The contractor prefers to use the same mobile crane for Activity 1 and Activity 2", this is discretionary (soft) logic, not mandatory logic, because the contractor could choose to rent a second crane if the project schedule required it.