2.1. Objective Function
The optimization model is designed to minimize the total HWZ cost, including all six components that were discussed above. Decision variables related to all site geometric design, TTC, and work management are set in the optimization.
Table 2 presents the decision variables considered and their influence on the various cost components, both directly and indirectly. The information on the effects of the decision variables on crash rates and on travel speeds are derived from the reviews in [
19,
35]. The cost components within the objective function are defined in terms of the additional cost caused by the HWZ presence compared to those of normal operations of the road section. Therefore, the values of some cost components may be negative. The overall optimization model is given by:
where,
is the total project cost.
is the agency cost.
is the temporary traffic control cost.
is the lost time cost.
is the vehicle operating cost.
is the emission cost.
is the crash cost.
X is the array of decision variables.
is the value of decision variable
i.
and
are the lower and upper bounds on the decision variable.
D is the project duration.
and
are the maximum allowed project duration and available budget, respectively.
TCMF is the total crash modification factor.
is the maximum acceptable value of this variable.
LT is the lost time.
is the maximum acceptable lost time.
are functions of the decision variables that define additional constraints, such as technical constraints or constraints on the geometric design of the HWZ.
2.2. Agency Cost
Agency cost is the direct project cost, which includes material, equipment, wages, and site overheads. As noted above, the previous studies listed in
Table 1 used coarse estimates of the hourly work rates and setup times, often ignoring the composition of tasks and their schedule within the project. However, tasks within the projects can be undertaken in several alternative ways (e.g., variations in equipment, number of workers, or crews), which lead to different project costs and work rates.
A location-based work schedule, which determines daily working hours for equipment and personnel including night work, is used within the model. Thus, it captures the effect of crew composition and the daily number of working hours on the agency cost. The schedule considers the working hours needed to complete the various tasks, setup times, and time lags among tasks. The decision variables that define the work schedule also affect other cost components through the project duration that they dictate. Finally, in some cases, the shoulders are used as temporary travel lanes [
20,
21]. The cost of their preparation for travel is also included. The agency cost is given by:
where,
,
EC, and
are the material, equipment, and workers’ wage costs, respectively.
is the cost of preparing the shoulders as a travel lane. The index
j signifies the working tasks within the project.
and
are the material quantity used in the task and its unit cost, respectively. The index
d signifies working days from the start of the work and for its entire duration.
and
are the number of working hours for equipment and workers, respectively.
and
are the corresponding hourly equipment costs and wages, respectively.
and
are the fractions of nighttime hours for equipment and workers, respectively.
ENAC and
WNAC are the corresponding additional cost of night work for equipment and workers.
IC is the daily indirect cost.
2.3. Temporary Traffic Control Cost
The TTC cost component extends the model presented in [
20]. TTC cost includes the cost of using temporary traffic control devices and wages for police patrols and flaggers. These costs have largely been ignored or only implicitly included as part of the agency costs. The TTC equipment cost depends on the length of the work zone, which dictates the quantity of equipment needed. The length of the work zone area that is separated with TTC from the travel lanes includes the workspace and a constant length composed of tappers and buffers. The workspace length is a decision variable in the model. Nighttime work increases both equipment and personnel TTC costs with the need for additional lighting equipment and the higher wages paid. The TTC cost is given by:
where,
and
are
TTC equipment costs and personnel wages, respectively.
is the workspace length on day
d.
is the length from the start of the shoulder taper until the end of the downstream taper, excluding the workspace.
is the
TTC daily rental cost.
is the cost of relocating the
TTC from one day to the next.
and
are the installation and removal costs for a distance unit, respectively.
OTTC is the cost of optional
TTC (e.g., VMS, DSD).
are the number of working hours on day
d.
and
are police and flagger hourly wages, respectively.
is the fraction of nighttime work on day
d.
and
are the corresponding nighttime additional costs for TTC equipment and wages, respectively.
2.4. Lost Time Cost
Increased travel times through HWZs are caused by reduced travel speeds due to changes in the road geometry and the delays at queues that form because of reduced traffic capacity in the HWZ bottleneck. These delays may cause a fraction of the travel flow to divert to alternative routes [
36], which reduces the delays on the HWZ route and increases travel times on the alternative routes. Most current models ignore the effects of diversions on the HWZ costs. The few studies that accounted for it, e.g., [
27,
28], assumed a constant diversion rate that does not depend on traffic conditions. This model explicitly captures diversion effects.
In this model, the traffic delay through the HWZ is separated into queue delay at the approach to the HWZ and increased travel time within the HWZ itself due to reduced speeds. This separation supports better estimation of vehicle operating and emissions costs that depends on speed and differs during queuing periods. The queue delay is caused when the flow approaching the HWZ exceeds its entry capacity. A deterministic quasi-dynamic point queue model is implemented to capture this delay. Each working day is divided into time slices. The sequence of queues at the end of the intervals is calculated by:
where the index
t signifies a time interval.
is the queue length on the point at the upstream end of the work zone at the end of interval
t on day
d.
is the demand traffic flow in the upstream section approaching the bottleneck at the HWZ entrance point.
T is the time length of the interval.
is the entry capacity to the section, which is calculated using procedures described in [
37].
where NOL is the number of open lanes in the section.
is a base capacity per lane.
, and
are adjustment factors for heavy vehicles, driver population, work activity, side of lane closure, rain, light condition, and nonadditive interaction effects that capture correlation among the adjustment factors, respectively.
The total delay to vehicles in the queue waiting to enter the HWZ section during the interval is given by:
where
is the queueing delay in interval
t to all vehicles.
The total queue lost time in the entire project (
QLT) is the summation of all queues caused by the HWZ:
The relevant time intervals may extend beyond the end of the workday because queues may still take time to dissipate. Reduced speeds within the HWZ result from changes in the free flow speed (FFS) and section capacity. This study implements the FHWA method to calculate FFS in the HWZ as a function of its geometric design [
35]:
where
is the base
FFS which is based on the posted speed limit.
are adjustment factors for lane width, lateral clearance, median type, and access points, respectively.
The prevailing travel time in the HWZ section is estimated based on the flow entering the section and using a flow-delay function. It is assumed that the entry capacity to the HWZ, which is defined by Equation (16), regulates traffic flow and ensures under-saturated conditions. Thus, the flow that can enter the section during a time interval is given by:
In the implementation, the travel times for vehicles within the HWZ section (and, through them, also travel speeds) are estimated with the Bureau of Public Roads (BPR) function:
where
is the travel time in the HWZ section.
is the workspace length at day
d.
L1 is the length of HWZ tappers and buffers.
and
are parameters.
is the travel speed. The values 0.15 and 4, respectively, are used in the case study.
Travel speeds that would prevail if an HWZ was not implemented are also calculated. The reduced travel speed lost time (
RSLT) captures the difference in travel time with the HWZ compared to without it.
RSLT is the summation of all reduced travel speeds’ delay caused by the HWZ:
where
is the normal travel speed in the section with no work.
The additional travel time through the HWZ may cause some travelers to bypass it by changing their routes. Diverted vehicles will experience the travel times on the alternative routes. They may also increase the travel times and queue delays to vehicles that were using these roads already, before the HWZ implementation. A route choice model is used to estimate the vehicle flows on the routes through the HWZ and alternative routes:
where
and
are the vehicle demand that chooses the HWZ and the alternative routes at interval
t and day
d, respectively.
is the total demand for travel that may use the HWZ section.
is a parameter.
and
are travel times on the two routes. The alternative route may be an aggregation of multiple routes. In the implementation, its travel time is assumed to be constant. However, increased section travel times and queue delays could be calculated in a way similar to that of the ones through the HWZ.
The calculation of the route flows and travel times is iterative. Given travel times on the two routes, route flows are calculated using Equations (23) and (24). The flow demands that arrive to the HWZ section ( are used to calculate updated section travel times and queue delays through the HWZ and the alternative route. The travel times and route flows are updated, and the process is repeated until convergence is reached.
The total lost time in the system is the summation of all queue delays and reduced speed delays for all vehicles. Its cost is obtained by multiplying it by a vehicle-type specific hourly rate, whose estimate is based on [
17]:
where
LT is the lost time. The index
y signifies the vehicle type (passenger cars, single-unit trucks, and combination trucks).
is the fraction of the total traffic of vehicle type y.
is the hourly cost rate of lost time.
2.7. Crash Cost
The model uses the Empirical Bayes (EB) method to estimate expected crash rates for the road section before the HWZ implementation. It uses Safety Performance Functions (SPFs) and actual crash records on the specific section to estimate expected crash rates with different severities. It is assumed that the area affected by the HWZ is from the start of the advanced warning area to the end of the downstream transition area. The EB crash rates are given by:
where the index
s signifies the crash severity.
is the expected yearly number of crashes without HWZ implementation per kilometer.
is the SPF weight in the EB estimate.
is the length of the area affected by the HWZ, excluding the work area itself.
Y is the number of years for counting crashes at the site.
is the rate per kilometer of crashes of severity
s observed at the site over
Y years.
U is an estimate of the uncertainty of the SPF model.
Crash Modification Factors (CMFs) are then applied to the expected crash rates to estimate their change due to HWZ implementation. They capture the individual effects of factors such as lane and shoulder width, presence of police patrols and flaggers, time of work, travel speed, lateral clearance, PCMs, DSD, and Truck Mounted Attenuators (TMAs). Their compound impact is calculated by the Total Crash Modification Factor (
TCMF). This research implements the Highway Safety Manual [
38] method to calculate
TCMF. The expected number of crashes on a road section depends on traffic flow through it. Thus, traffic diversion to alternative routes affects numbers of crashes both on the HWZ route and the alternatives:
where the index
m signifies the countermeasure.
is the crash modification factor of countermeasure
m for crash severity
s.
are the crash costs. AADT is the annual average daily traffic.
2.8. Solution Evaluation Procedure
The procedure to evaluate the objective function for a candidate solution, which includes site geometry, TTC, and work management decision variables, is presented in
Figure 1. First, a project schedule is built for this solution considering the characteristics of the project, including bill of quantities, project tasks, time lag among project tasks, available crew formations, project total length, and duration constraints. The output of the project schedule determines the project duration, time of work, workspace length, number of working hours for each task, and the fraction of night work for each task. This information is used to calculate the agency and TTC costs. The project schedule is also used as input to the traffic flow model, together with information on traffic flows through the HWZ and alternative routes.
Delays at HWZs may cause diversion of traffic flows to the alternative routes. A route choice model is used to estimate these flows using the travel times on the two routes. The traffic flow model estimates capacities and FFSs, travel times, speeds, and queue delays for the HWZ and alternative routes for each time period and day of work. The new flows are used to re-estimate speeds, delays, and travel times. The iterative process is repeated until convergence is obtained. The final travel times and delays are used in calculating lost time, vehicle operation, and emission costs. It is also used, together with crash records for the HWZ, to calculate crash costs. Finally, the total HWZ cost is the summation of the six cost components. The optimization is conducted using a genetic algorithm [
39]. Several GA parameters were tested to achieve the minimal cost. The values that yielded the best results were population size 200, number of generations 300, and crossover and mutation rates 0.8 and 0.01, respectively.