8.1 Arterial Progression Principles & Actuated-Coordinated Operation

8.1 Arterial Progression Principles & Actuated-Coordinated Operation

[!NOTE] IMSA Level III Examination Focus: Senior Traffic Signal Field Technicians must possess an advanced understanding of coordinated arterial traffic signal operations. Mastery of subsystem cycle length selection, split allocation, offset calculations, yield point logic, fixed versus floating force-offs, time-space diagram construction, progression bandwidth efficiency formulas, and lead-lag phase sequencing is essential for optimizing corridor flow and troubleshooting field coordination anomalies.

---

1. Principles and Objectives of Arterial Progression

Isolated traffic signal operation evaluates vehicular demand exclusively at a single junction, serving local actuations without regard to conditions at adjacent intersections. While efficient for isolated rural intersections or widely separated urban nodes, isolated operation on closely spaced arterials results in random vehicle arrivals, frequent stops, excessive fuel consumption, elevated emissions, and heightened risk of rear-end collisions within queuing zones.

Arterial coordination synchronizes multiple adjacent traffic signals to establish continuous flow along a primary roadway corridor. The primary objective is to facilitate the uninterrupted movement of vehicle platoons—dense clusters of vehicles traveling together at a consistent speed—through successive green lights without stopping.

+-----------------------------------------------------------------------------+
|                   PLATOON PROPAGATION AND DISPERSION DYNAMICS              |
+-----------------------------------------------------------------------------+
| Intersection A (Stop Bar)                 Intersection B (Downstream)       |
| [Compact Platoon Released]                 [Dispersed Platoon Arrives]       |
| ===[V1][V2][V3][V4][V5]===>               ===[V1]  [V2]   [V3]    [V4]  [V5]|
| <---- Dense Headways ---->                 <------ Spread Headways ------>  |
|                                                                             |
| Upstream Green Departure                   Platoon expands as faster cars    |
| creates tightly bunched                    pull ahead and slower cars lag.   |
| vehicular platoon.                         Bandwidth must envelope core.     |
+-----------------------------------------------------------------------------+

Platoon Dispersion Mechanics

When a traffic signal turns green, waiting vehicles accelerate and discharge at saturation flow headways (typically $1.9\text{ to } 2.1\text{ seconds per vehicle}$, or roughly $1,800\text{ to } 1,900\text{ passenger cars per hour per lane}$). As the compact platoon travels downstream along an arterial link, it disperses:

• Faster drivers accelerate ahead of the platoon median speed.
• More cautious drivers or heavy commercial vehicles lag behind.
• Mid-block friction (driveways, parking maneuvers, visual distractions, and lane changes) stretches the platoon over time and distance.

Platoon dispersion is modeled analytically by Robertson's Platoon Dispersion Model: $q_t(i + t_a) = F \cdot q_s(i) + (1 - F) \cdot q_t(i + t_a - 1)$ Where:

• $q_t(i + t_a)$ = arrived flow rate at the downstream intersection during time step $i + t_a$
• $q_s(i)$ = initial discharge flow rate at the upstream signal during time step $i$
• $t_a$ = minimum link travel time (calculated as link distance divided by average free-flow speed)
• $F$ = platoon smoothing factor, defined as: $F = \frac{1}{1 + \alpha \cdot t_a}$ Here, $\alpha$ represents the empirical platoon dispersion factor (typically $0.35$ for moderate arterial friction down to $0.25$ for well-controlled, access-managed arterials). As travel distance and travel time ($t_a$) increase, $F$ decreases, indicating greater platoon dispersion and requiring wider downstream green windows or tighter signal spacing to maintain cohesive progression.

Core Benefits of Coordinated Operations

1. Stop and Delay Reduction: Halts along the arterial corridor can be reduced by $20%\text{ to } 50%$, cutting overall travel time and intersection approach delay.
2. Fuel and Emissions Savings: Accelerating from a full stop consumes significantly more energy than cruising at uniform speed. Smoothed progression reduces fuel consumption by $10%\text{ to } 15%$ and reduces carbon monoxide ($CO$), nitrogen oxides ($NO_x$), and volatile organic compounds ($VOC$).
3. Safety Improvement: Progression reduces unexpected stops at the onset of yellow change intervals, cutting rear-end collisions along the arterial by up to $30%$.
4. Queue Spillback Suppression: Coordinated green waves flush standing queues from downstream intersection approaches before the arrival of the upstream platoon, preventing gridlock from spilling back across preceding intersections.

---

2. Fundamental Coordination Parameters

To coordinate a subsystem of traffic signals, four fundamental operational parameters must be defined within the local controllers: Cycle Length, Splits, Offsets, and Coordination Reference Points.

+-----------------------------------------------------------------------------+
|                   FOUR CORE COORDINATION TIMING PARAMETERS                  |
+-----------------------------------------------------------------------------+
| 1. CYCLE LENGTH (C)  | Uniform background cycle time across the corridor    |
| 2. PHASE SPLITS (S)  | Seconds or % of cycle allocated to each phase (G+Y+R)|
| 3. OFFSET (O)        | Time delta from master reference to local green/yield|
| 4. REFERENCE POINT   | Cycle benchmark: Start of Green or End of Green/Yield|
+-----------------------------------------------------------------------------+

1. Cycle Length ($C$)

The Cycle Length is the total time required for a signal controller to execute one complete sequence of all phases (including vehicular greens, pedestrian walk/clearance intervals, yellow change, and red clearance). In a coordinated system:

• Uniformity Rule: All intersections operating within a coordinated subsystem must share the exact same cycle length (or an exact integer fraction/multiple, such as a double-cycle $C/2$). If intersection A operates on a $90\text{-second}$ cycle while intersection B operates on a $100\text{-second}$ cycle, their phase relationships will constantly drift relative to each other, destroying progression.
• Critical Intersection Principle: The corridor cycle length is governed by the single critical intersection—the intersection requiring the longest cycle length to satisfy its capacity demands (highest combined critical lane volumes). All other intersections in the subsystem must adopt this cycle length, even if their local traffic could be accommodated in a shorter cycle.
• Cycle Length Optimization (Webster's Formula): The theoretical minimum delay cycle length ($C_0$) is derived from Webster's equation: $C_0 = \frac{1.5 L + 5}{1 - Y}$ Where:
• $L$ = total lost time per cycle across all critical phases (typically $L = \sum (t_L) \approx 3\text{ to } 5\text{ seconds}$ per phase for start-up lost time and clearance lost time).
• $Y$ = sum of critical flow ratios: $Y = \sum \left(\frac{v_i}{s_i}\right)$, where $v_i$ is design lane volume and $s_i$ is saturation flow rate (e.g., $1,900\text{ vphpl}$). As $Y \to 1.0$, required cycle length approaches infinity.

2. Phase Splits

A Phase Split is the total duration of time allocated to an individual phase within the cycle length, expressed either in seconds or as a percentage of the cycle. The split must encompass all intervals associated with that phase: $\text{Split} = \text{Green Time } (G) + \text{Yellow Change Interval } (Y) + \text{Red Clearance Interval } (R_{\text{clear}})$ If pedestrian service is enabled on that phase, the programmed split must also satisfy the minimum pedestrian requirements unless pedestrian split exceedance logic is configured: $\text{Split}_{\text{ped}} \ge \text{Walk} + \text{Pedestrian Change Interval (FDW)} + Y + R_{\text{clear}}$

Under standard NEMA dual-ring concurrent operation:

• The sum of splits for sequential phases on Ring 1 across Barrier 1 must equal the sum of splits on Ring 2 across Barrier 1: $\text{Split}(\phi 1) + \text{Split}(\phi 2) = \text{Split}(\phi 5) + \text{Split}(\phi 6)$
• Similarly, across Barrier 2: $\text{Split}(\phi 3) + \text{Split}(\phi 4) = \text{Split}(\phi 7) + \text{Split}(\phi 8)$
• The total split sum across both barriers equals the cycle length: $\sum \text{Splits}_{\text{Barrier 1}} + \sum \text{Splits}_{\text{Barrier 2}} = C$

3. Offsets

The Offset is the time difference (expressed in seconds or as a percentage of the cycle) between a designated reference point in the local cycle and a master system background cycle clock (or master time-base reference, such as midnight / UTC GPS time zero).

• Offsets determine when green initiates at downstream intersections relative to upstream intersections.
• The ideal one-way travel offset ($O_{i,j}$) between intersection $i$ and intersection $j$ separated by distance $d_{i,j}$ with design progression speed $v$ is: $O_{i,j} = \frac{d_{i,j}}{v} \pmod C$

4. Coordination Reference Points

The coordination reference point defines which specific event in the local controller's cycle aligns with the calculated offset time from the system background clock.

---

3. Actuated-Coordinated Operations: Yield Points & Force-Offs

Modern arterial systems operate in actuated-coordinated mode. In this mode, the main-street coordinated phases (usually Phase 2 and Phase 6) are designated as non-actuated or "coordinated recall" phases, while cross-street phases (Phases 4 and 8) and left-turn phases (Phases 1, 3, 5, 7) operate semi-actuated, serving vehicle and pedestrian calls only upon detection demand.

+-----------------------------------------------------------------------------+
|                ACTUATED-COORDINATED CYCLE CLOCK & FORCE-OFFS                |
+-----------------------------------------------------------------------------+
| Local Cycle Clock: [0 s -----------------------------------------------> C] |
|                                                                             |
| Coordinated Phase (2+6) Green   | Non-Coordinated Phases (4+8, 1+5)          |
| ===============================>|-----------------------------------------> |
|                                 ^                      ^                    |
|                             YIELD POINT            FORCE-OFF                |
|                       (Earliest drop of main)   (Mandatory drop of side)    |
|                                                                             |
| [Early Return to Green]: If side street terminates early due to gap-out,     |
| unused green time immediately returns to Phase 2+6!                         |
+-----------------------------------------------------------------------------+

The Yield Point and Permissive Windows

• Yield Point: The precise second in the local cycle clock at which the controller is permitted to terminate the coordinated phase green and yield right-of-way to conflicting side-street or left-turn calls.
  • If calls exist on non-coordinated phases at the Yield Point, the controller initiates the coordinated yellow change and red clearance intervals and serves the demanding phases.
  • If no calls exist at the Yield Point, the controller remains dwelling in the coordinated phase green until a valid actuation is registered.
• Permissive Period: A defined time window following the Yield Point during which the controller continues to monitor for incoming calls on non-coordinated phases. In older dual-permissive controllers, a second window allowed pedestrian phases or lagging left turns to be served without losing cycle synchronization.

Fixed Force-Offs vs. Floating Force-Offs

A Force-Off is an internal command executed by the coordination logic that forcibly terminates a non-coordinated phase, forcing it to enter its yellow change interval regardless of whether vehicle detections are still holding the green extension timer.

The distinction between Fixed Force-Offs and Floating Force-Offs is one of the most critical operational concepts in traffic signal systems engineering:

+-----------------------------------------------------------------------------+
|                   FIXED FORCE-OFF vs. FLOATING FORCE-OFF                    |
+-----------------------------------------------------------------------------+
| FIXED FORCE-OFF (Mandatory for Progression):                                |
| Phase 4 Scheduled Split = 30s. Force-Off programmed at Cycle Second 80.     |
| - Scenario A: Starts at Sec 50 -> Runs 30s -> Hits Force-Off at Sec 80.     |
| - Scenario B (Early Start): Starts at Sec 40 -> Runs max to Sec 80 (40s)    |
|   OR if it gaps out at Sec 60, unused 20s RETURNS TO COORDINATED GREEN!     |
|   CYCLE STABILITY: Absolute background clock is perfectly maintained.       |
|                                                                             |
| FLOATING FORCE-OFF (Progression Destroyer):                                 |
| Phase 4 programmed split = 30s. Force-Off floats 30s from actual green start|
| - Starts at Sec 50 -> Force-off at Sec 80.                                  |
| - Starts late at Sec 65 -> Force-off FLOATS to Sec 95!                      |
|   RESULT: Pushes coordinated phase green back by 15s; breaks platoon band! |
+-----------------------------------------------------------------------------+

| Operational Feature | Fixed Force-Off | Floating Force-Off | | :--- | :--- | :--- | :--- | | Termination Trigger | Fixed absolute time point on the local cycle clock (e.g., exactly at second 75 of a 100s cycle). | Relative duration counter starting from the instant the phase turns green (Green Duration = Split $-$ Yellow $-$ Red). | | Early Start Handling | If an actuated phase starts early (because a preceding phase gapped out), it is still forced off at its scheduled absolute clock second. | The phase is allowed to run for its full split duration from its actual start point, shifting downstream phases later. | | Unused Split Time | Any unused time from phases that gap out or omit returns directly to the coordinated phase ("Early Return to Green"). | Unused time may be absorbed by subsequent non-coordinated phases, delaying return to the main street. | | Impact on Progression | Maintains rigid background cycle integrity. Coordinated green window is preserved or expanded; progression bands are protected. | Erodes progression bandwidth. Coordinated green start drifts, causing approaching platoons to slam into red displays. | | IMSA Level III Standard | Mandatory standard for all multi-phase actuated-coordinated arterial networks. | Generally restricted to isolated operations or non-critical secondary side-street rings. |

[!IMPORTANT] Field Engineering Takeaway: Under Fixed Force-Off operation, non-coordinated phases can never consume more than their scheduled split time, but they can consume less if traffic demand is light. This unused time is captured by the coordinated phase, widening the green window for the arterial platoon. Under Floating Force-Offs, phases that start late push the rest of the cycle back, causing the coordinated phase to lose green time and breaking progression bands across the corridor.