TEO Signal Committee Meeting Minutes Meeting Date: 10/29/2013 Water s Edge Conference Rm 176 Meeting Time: 9:00am Noon

Transcription

1 TEO Signal Committee Meeting Minutes Meeting Date: 10/29/2013 Water s Edge Conference Rm 176 Meeting Time: 9:00am Noon Meeting Attendees: Jerry Kotzenmacher Sue Zarling Nicole Flint Peter Skweres Jesse Knox Ed Andrajack Robin DeLage Mike Posch Mike Schroeder Jim Deans Al Espanoza Chris Bosak Clint McCullough Alex Govrik Jeff Knofczynski Mike Gerbensky Roger Peterson Tod Becker Cindy Gross Linda Heath Kyle Holm Rachel Guan Ben Osemenam Jon Jackels Old Business- 1. ADA Pedestrian Accommodations No ped crossing sign - MnDOT Staff Attorney Nandana is reviewing the request for legal opinion on this signing issue. Ped station redesign The pedestrian station redesign has been completed and the detail is now posted on the OTST web site. The design was reviewed and approved by all interested offices including ADA, Signal Inspections, Maintenance, Concrete and Signal Design. The design uses a 4 bolt pattern base that fastens to the surface of the sidewalk (see web site The base of the ped station has an exact bottom bolt pattern and threaded top that must be provided by any manufacturer. Currently there is one approved manufacturer. A notable installation process is the anchor rods will be installed by drilling holes into the concrete, and then epoxy the stainless steel rods into the sidewalk. The reason behind the pedestrian pushbutton station redesign is to reduce the conflict between the concrete installers and the electrical contractor. The first installations should begin next construction season. As these new ped stations start getting installed provide any field observations to OTST. APS operations MnDOT subcommittee met. The recommendations were presented to a subcommittee of the NCITE Intersection Traffic Control Committee for uniform statewide APS operation on August 5th. The meeting minutes are attached. The next step is to get the meeting minutes into a usable format that all agencies can follow. Page 1 of 14

2 APS extension on poles A stand-alone spec has been written for the APS Mounting Spacer. It can be used as a retrofit or on new signals to meet ADA guidelines when installing APS buttons on signal poles. APS Mounting Bracket (Bosinator 5000) Chris Bosak has developed a draft detail for a mounting bracket that will allow APS push buttons to be installed on existing pole where the elevation may have precluded the placement of the APS button on an existing signal pole. This adaptor is being built and will be installed at an intersection in Mankato. Once the first units are installed the draft detail will be finalized and published on the OTST web site. APS Signs The signing material must be retro reflective, meeting standard MnDOT signing specifications with Braille symbols included. The City of St. Paul has had many issues with the Braille being incorrect and/or placed on the sign incorrectly. We will have to determine a way to verify this. If you have fading signs, get a list with the original special provisions covering the order form for APS signs to Peter. He has been working with Polara on this issue. PRIOSK Ped Station A newly designed ped station option was presented. The committee was asked to make recommendations on its use or non-use. Since MnDOT now has a ped station design that includes recommendations from all vested groups having an interest, is this new design (PRIOSK Ped Station) needed or wanted? Comments on the PROISK design included higher cost and drifting from a standard design. The committee determined it was better to stay with the standard design that was recently developed. APS Pushbutton Designations on plan layout The designations of APS Pushbuttons on the plan layout needs to be followed when installing buttons in the field. On turn on of a new APS system, the APS buttons are designated for each specific location on a corner. This needs to be checked the same day they are installed so there is no error in the installation. Part of the problem is each manufacturer of the APS designates them differently. Peter will check into the designation from the manufacturer and it will be determined if there is a change to the plans that might make the installation clearer for both manufacturers buttons. FYA Update D2 wants to modify a signal to FYA, but it has a Traconex controller. It was recommended that the controller should be replaced by an ASC controller. This would not be a problem, but the other signals in the Bemidji coordinated system are Traconex 390 s. The committee agreed that all the Traconex s in the system should be replaced with Econolite controllers. ESU Page 2 of 14

3 expressed that they have several ASC/2 s in stock that would work fine in the proposed use. Cindy will look into the modifications. Cabinet/Controller Committee See attached meeting minutes BNSF Letters - Response letters to BNSF will be reviewed on November 19 th. We are preparing the letters for final review by each of the districts involved (D1, D2, D3, D4, D8 and Metro). Once sent back to the districts, one final review will be requested. New Business Jon Jackels, ITS Jon is out of the OTST Intelligent Transportation System (ITS) Office. There are more electrical ITS type systems being installed on our highway system. As we know, these systems often rely on our signal operations and maintenance staff. ITS deployments are experimental on many projects. Many will fill a special safety need on the highway and often are unique, one of a kind installation. The unique nature of these deployments can result in systems that don t always perform as planned. Signal staff are the best qualified to observe and recommend practices for these systems, once deployed on the road. The ITS folks want to hear back any comments. There will be more systems installed in the future. How we work things out remains to be a question we can help answer. Some suggestions the group came up with: Use core specs and special provisions for ITS project. Reoccurring issues should be brought up. Asset management (AFMS), GPS, wiring diagrams, System ID Jon will inform districts when a new deployment happens in their districts. Updated plan sets will furnished. Rural Intersection Conflict Warning System (RICWiS) Jon updated the group on the latest large scale ITS project RICWS. There will be 49 intersections across the state (see attachment) that will get this system installed. 20 installed in 2013, 29 installed in All of these systems are under contract with the consultant/contractor for general maintenance and operation. MnDOT will be responsible for: Vandalism Knockdowns Locates Any other service need must be directed to Ken Hansen, MnDOT Project Manager at District experience with the RICWS installations is very important for this project. There may be a training session planned in the future. Contact Ken with any concerns or comments, good or bad! For more information, see attached project one pager or go to the project web site: Page 3 of 14

4 Special Provisions New signal Specs are out. The new spec book has reduced the need for many special provisions. Rarely used items will still have special provisions. The OTST web site will make it easier for the users. The sample special provisions posted are intended to be downloaded each time you have a project. Delete sections that you don t need for your specific project. This will ensure you are using the most current verbiage. The standalone rarely used special provisions on the web site will be slot in place the portions of the standalone specifications in the most appropriate location. The next release of the Standard Specifications for Construction book is scheduled to be in Signal and Lighting Certification Just a reminder that there must be a certified contractor on the job site anytime there is work being performed. Classes on the certification are now being offered. Metering of Luminaires on Signals Excel no longer applies flat rates for street lights on traffic signals. They will honor any existing contracts. On another related note.otst was contacted regarding concerns by the power company on street lights not being metered and cameras being set up using flat rate, not metering. At this point the power company has not contacted us and we have not verified the problem, but it should be watched to be sure that the hook ups are designed and installed correctly. LED Indications The re-occurring theme of agencies covering indications outages was discussed. Agencies claim that it s not the indication going out be rather some other type of electrical issue that MnDOT is responsible for. Metro has agreements with some agencies to provide the first call and charge the agency for work performed that is there responsibility. This is not as practical for many outstate locations since the drive time can be significant. A DDI recently opened in St Cloud and there was some concern over the brightness of some indications and the issue of being able to distinguish balls and arrows from a distance. It was recommended to not look into dimmable LED indications, but rather to wait a bit to see how people become use to the new design. Alpha Training There will be training sponsored by the vendor for this product on November 7 th at Arden Hills. Round Robin Roger Quazite hand hole. There is a sample product out at ESU. Stop by and take a look. Ben Swing away mast arm. Working with Standard Plate group to design as standard plate for the swing away hinge for the PA series pole. Some issues have come up based on differences in designs between the two pole manufacturers. These are being worked out. Page 4 of 14

5 Sue Considering having a once or twice a year signals meeting for the DTE s. She will be discussing this with them at the TEO Discussion group meeting. These meetings will cover items that need input from their level, including cost participation and other nonoperation/maintenance items. Next meeting: January 29th, 2014 Waters Edge Conference Room 176 9:00am 12:00noon Send Agenda items to Jerry K. Attachments The following information is all attachments to the Signal Committee meeting minutes: Attachments: Page 5 of 14

6 NCITE Statewide APS Operations Committee Meeting Date of meeting: Attendees: Jerry Kotzenmacher MnDOT Office of Traffic, Safety and Technology Nick Costello Washington County Todd Grugel MnDOT Office of Accessibility Nick Vangunst City of Minneapolis Peter Skweres MnDOT Office of Traffic, Safety and Technology Jesse Knox MnDOT Office of Traffic, Safety and Technology Sonja Piper City of St Paul Tony Kasper MnDOT Office of Traffic, Safety and Technology Roy Doron Hennepin County Sue Zarling MnDOT Office of Traffic, Safety and Technology Tim Bangsund MnDOT Metro Traffic Signal Operations Ken Rodgers MnDOT Office of Accessibility Blake Redfield City of St. Cloud This sub committee was established after discussion with the NCITE Intersection Traffic Control Committee stating that it was important to establish Accessible Pedestrian Signal (APS) operating standards that would be utilized by all agencies operating traffic control signals across Minnesota. The intent of this sub committee is to create operational consistency for users of the APS systems. After internal MnDOT discussion outlining a preferred APS operation, this state wide committee was set up to represent a broad range of city, county and state agencies to develop an operational standard to be used by all agencies. This sub committee will then make recommendations to the NCITE Intersection Traffic Control Committee with the final approval from the NCITE Executive board for statewide implementation. Currently, there are two APS buttons on the MnDOT Approved Products list. (Polara Engineering, distributed by Brown Traffic and Campbell Company, distributed by Traffic Control Corp.) One issue with making recommended operational practices is one product may offer a feature that another Page 6 of 14

7 manufacturer does not. We do not want to require an operation that one of the products on the APL currently does not offer unless the operation is required by the MnMUTCD. Operational practices standard per the MnMUTCD and FHWA guidance. These rules must be followed: Speech messages will be used during the walk indication when the pedestrian buttons are less than 10 apart. If 10 or more apart, the audible walk indication shall be a percussive tone. (MnMUTCD 4E.11) Speech walk messages and the percussive tone walk indication should be used on different quadrants of the same intersection during the walk interval if the button separation dictates this. (This was in a letter of from the FHWA) An audible countdown during the ped clearance interval will not be used. Per the MnMUTCD. Following the audible walk indication, accessible pedestrian signals shall revert to the pushbutton locator tone during the pedestrian change interval. (MnMUTCD 4E.11) This standard was questioned by many on the committee. Since it is an MUTCD standard, any arguments must be presented to the state and national MUTCD committees. This issue is beyond the scope of this committee. Length of extended push time to activate function shall be 2 seconds. (MNMUTCD 4E.13) A clear message will be used for the walk interval. Words such as Avenue and Street shall not be used except in cases such as downtown Minneapolis where there are both street and avenues crossing with the same numbers. Speech walk shall not contain any additional information, except they shall include designations such as street or Avenue where this information is necessary to avoid ambiguity at a particular location. (MnMUTCD 4E.11) If rest in walk is used the accessible walk indication should be limited to the first 7 seconds of the walk interval. The button would then go to the locator tone and can be recalled by a button press during the walk interval. This is guidance in the MnMUTCD (4E.11) There was considerable discussion at the meeting regarding ped recycle in this situation. With long cycle lengths it is advantageous to allow the ped cycle to restart provided there s adequate time left in the coordination program to allow a pedestrian re service without throwing the intersection out of coordination. Some visually impaired users would prefer to have the phase terminate and the ped cycle start at the beginning of the cycle to allow for better auditory cues from the intersection for when it s safe to begin to cross the intersection. The consensus of the committee was to leave this operational decision up to the individual traffic signal control operators using their best engineering judgment. First push or actuation on all APS installations: Page 7 of 14

8 Speech message on initial button push at times when the walk interval is not timing: It shall be the term wait. (MnMUTCD 4E.11) The MnMUTCD does not require that a speech message be used at this time, that was a committee decision. It does require that the message be wait if one is used. No Locator tone is audible during this time. First push will send a speech message wait. Will repeat wait every 4 seconds until the call is serviced. LED confirmation light will turn on and remain on to confirm call has been placed until the pedestrian phase is serviced. Will have confirmation of button activation (push) via sound and vibrotactile bounce. Walk Time functions with pedestrian buttons with 10 feet or more separation on a specific corner: The tactile button will vibrate during walk interval. A percussive tone consisting of multiple frequencies with a dominant component at 880Hz will be provided during the walk Interval. (MNMUTCD 4E.11) The extended push feature will be used for a speech message. The message will state wait.wait to cross Broadway at Grand Once walk time has expired, the APS button will resume emitting the locator tone. Walk Time functions with pedestrian buttons with less than 10 feet of separation on a specific corner: The tactile button will vibrate during walk interval. A speech message shall be given during the walk Interval (MnMUTCD 4E.10). The message shall be as follows: Broadway. walk sign is on to cross Broadway Once walk time has expired, the APS button will resume emitting the locator tone. Extended push or actuation (2 second actuation minimum): The extended push will give a speech message. The speech message should be simple and clear such as: Wait.wait to cross Broadway at Grand Complete message would play once and then the button would resume stating wait every 4 seconds until the call is serviced. Action: Tony will look into additional features of the extended push. It was suggested that the extended push provide both a speech message and extended time. LED confirmation light will turn on and remain on to confirm call has been placed until the pedestrian phase is serviced Will have confirmation of button activation (push) via sound and vibrotactile bounce. The extended push feature will be used for a speech message. The message will state wait wait to cross Broadway at Grand An extended push could change pedestrian timing giving additional time for pedestrians to cross. If this option is used, the extended push must provide the voice message and provide additional crossing time. If extended time is provided, MnMUTCD section 4E.13 requires an additional sign be placed by the APS pushbutton. The decision to provide additional pedestrian time with an extended push is up to the traffic control Page 8 of 14

9 signal operator along with the amount of additional ped clearance time. Since the meeting some investigating has been done in regards to adding pedestrian time with an extended push of the button. At the present time adding pedestrian time with an extended push cannot be clearly defined. The function operates through the controller by the APS button holding the pedestrian call input to the controller low for an extended time. All controllers do not offer this function and it is not clear that an extended pedestrian input duration is defined by NEMA. Extended time will not be a standard operation for extended push but could be used if engineering judgment calls for its use and the function is available. Potential problems using an extend time feature for the walk clearance: 1. It will create issues for countdown ped indications. 2. Shorter signal coordination cycles could not accommodate additional ped time. 3. Additional components in the traffic signal cabinet would be required.(wiring) 4. Controllers and signal coordination programs must support multiple ped intervals on a per phase basis. Walk Clearance time functions: No verbal count down Locator tone should be on If a call is placed during walk clear, a speech wait should be given and repeated every 4 seconds unless there is time to re service the pedestrian times and the controller is programmed for ped recycle. APS Preemption functions: Committee recommended not using the preemption audible function within the APS devices. May create confusion for pedestrians. Will evaluate conditions and possible APS functions for light rail when the new Central Corridor opens. Central Corridor will be using transit priority which is different than Hiawatha s rail preemption. General Notes: Manufacturer specific APS Programming sheet should be in all cabinets, with current program. The Polara button had several sounds for the rapid tick or walk interval. The committee decided Sound #3 was the best choice for this product. If it is decided by the operator to us pedestrian recycle, the pedestrian recycle option must be used in some controllers to have the ped call come up when there is still enough time to service the entire ped call. Without this option, the ped call will not be serviced until the next cycle, even when there is time available. Although the idea of a standard uniform statewide operation of the APS is ideal, the committee recognizes that there are unique circumstances at every signalized intersection using the APS. Engineering judgment may preclude these standards. Page 9 of 14

10 Side by side comparisons of the two APS currently on the MnDOT Approved Products List: Functional Question Can the Pause between WAIT messages be 6 seconds? What does the button do when pushing it during Don t Walk state? Can the EXTENDED PUSH feature be set to 2 seconds? Does EXTENDED PUSH allow for street name & direction messages Are Rapid Tick message sounds similar between buttons? What does the WALK Rapid Percussion sound do during a constant/long walk when set for continuous for WALK setting? What does the button do when pushed (IE sound, feel and visual indicators)? Does WAIT message start again if pushing button during Don t Walk? Expected Results We want 6 seconds between WAIT messages. Should go back to WAIT message, display LED call & vib-click button. MUT requires at least 2 seconds. We want street messages but don t need direction. Should be similar. We expect it to time out after a period both sound and vibrate. We need audio message (WAIT), button vib-click & indicator light. The WAIT message should restart, button vib- ADA button standards setup test Campbell Assessment Yes. Set for 0 to 16 seconds by 1 second increments. Zero value = no WAIT message used. Button acts just like column specifies. Yes. Extended push values go from 1 to 10 seconds by 1 second increments. Yes. Extended push can have any message added (or ordered) via WAV file format. Rapid tick sounds like wood dowels tapping together. Vendor can supply any sounds we wish to better match up. Walk percussion only sets to specific time values & stops after timing out or the WALK ending. Button acts as column states. Button vibe is a pager vibrator motor. Yes, button acts as state. Page 10 of 14 Polara 1 st Generation Assessment Yes. Wait message set for standard push & extended push of 4, 6, 8, 10 seconds. Button acts just like column states. Yes. Extended push goes from 1 second to 6 seconds by ½ second increments. Yes, extended push works like expected results state. Need street name ordered No percussion sound available as it is removed for addition of custom message sounds. No percussion sound. Custom message does end after 3 plays with FULL WALK selected. Button acts as column states. Button vibe is a solenoid bumping back of switch. Yes, button acts as state. Polara Ethernet Generation Assessment Yes. Wait message set for standard push & extended push of 4, 6, 8, 10 seconds. Button acts just like column states Yes. Extended push goes from 1 second to 6 seconds by ½ second increments. Yes, extended push works like expected results state. Need street name added (or ordered). Rapid tick sounds like snare drum or machine gun. Walk Percussion stops after 3 plays when set to FULL WALK. Otherwise time limiting values can be set. Button acts as column states. Button vibe is a solenoid bumping back of switch. Yes, button acts as state.

11 What DIRECTION messages area available (in case we decide to use them). What happens when pushing button during WALK cycle? click & indicator should activate. We want 8 directions available. Nothing should happen. No canned messages. All added as per order sheets. Walk button starts vibrating again and WALK percussion starts over. Both end as WALK terminates. North, Northeast, Northwest, East, West, South, Southeast & Southwest messages available. Nothing happens, no vib click, no call to controller, no LED lighting up but walk message does stay playing and button vibrates during walk North, Northeast, Northwest, East, West, South, Southeast & Southwest messages available Nothing happens, no vib click, no call to controller, no LED lighting up but walk message does stay playing and button vibrates during walk message time. message time. NOTE: Vib click refers to the button having a short burst of movement (pushes back) as you push in the button. This makes the button feel like it is toggling. Vibrate refers to the button actually vibrating over 1 or more seconds. Attachment: Controller/Cabinet Committee Meeting Minutes 10/18/2013 Attendees: Jerry Kotzenmacher Sue Zarling Ron Christopherson Peter Skweres Jesse Knox Alex Govrik Page 11 of 14

12 Marty Carlson Tim Bangsund Tony Kasper Kevin Schwartz Jim Deans (absent) Nicole Flint ASC/3 Current statewide software version is 2.51 Econolites latest software release is 2.57 Version 2.55 was installed at TH 36 at TH 5. The version was found to have coordination issues was re-installed at this location is the only software that can correctly accommodate the out of flash all red. Version 2.57 does not exit flash correctly. There are a number of Econolite controller issues being discovered by both Metro and CESU. In an effort to get a consistent and complete list, Tim and Jesse will get a common list of observed software problems to TCC. CESU will install 2.55 on TH 149 in Eagan. (Westcott, Opperman, Yankee Doodle) Start up all red The MUTCD now requires any signal in flash to re-start with a 6 second all red before going to mainline green. MnDOT cabinet versions are all different based on the year they were produced. This creates a problem for out of flash all red. Depending upon the vintage, each cabinet may need different options and modifications to guarantee the exiting out of flash in all red is always accomplished. A second door open switch will be installed on all 2013 Myers cabinets leaving the CESU and existing installed 2013 Myers cabinets. This will ensure that the traffic control signal will always start up in an all red condition when the door is closed. Care must be taken when the door is open and an operator wants to take a traffic control signal out of flash. In this instance the operator should cycle power to the controller to ensure the controller does power restart which will force the controller to execute its startup program. Districts need to review the startup program in each controller to ensure it is in compliance with the new MnMUTCD requirements. Once there is an Econolite software version that exits flash correctly the issue of retrofitting older cabinet versions will be revisited. All controllers should have 6 seconds of all red programmed in the controller start up. Then, all green for mainline. At a minimum a state wide e mail needs to be sent informing district operations personnel of the new requirements for traffic control signals exiting flash. CTC Preemption boards Page 12 of 14

13 CESU has received two CTC preemption systems and will install them on TH 149, Eagan. Ron has a field wire interface adaptor for the system that bolts to the side wall of the cabinet. The board will supports a 3 preemption program operation. Additional note: This note received from TCC one week after the meeting: 10/23/2013 Just because when it rains it pours attached is the ASC3 SW release notes for Some key items include coordinator fixes. This is a significant release, but will still have an issue coming out of flash in a TS1 cabinet. This is currently schedule for the end of the year. Matt Allwood Attachment: Rural Intersection Conflict Warning System (RICWS) Description As part of Minnesota s Towards Zero Deaths initiative, the Rural Intersection Conflict Warning System (RICWS) project s goal is to reduce fatal and serious injury crashes at rural stop controlled intersections. RICWS is a Design Build, Indefinite Delivery/Indefinite Quantity (ID/IQ) project that will deploy intersection conflict warning systems (ICWS) at 20 and up to 50 intersections statewide. Candidate intersections for the project were initially identified by counties and MnDOT district traffic staff through the systematic development of localized road safety plans, which outline specific safety investment priorities and projects based on crash data. Intersections were assessed and prioritized based on the road safety plans, which includes several risk factors including roadway geometry and past crash history. Intersections were secondarily prioritized by five year crash rates. Design Build contracting method was selected to deliver RICWS. Design Build gives the contractor team the ability to select innovative products such as detection and controller components and construction methods such as staging. Using Design Build also allows for faster construction time, which is important for a safety project, since design and construction can overlap. Page 13 of 14

14 ID/IQ is another contracting method added to RICWS which allows MnDOT to incrementally add up to 30 additional ICWS sites to the base contract in order to capitalize on established unit costs, design efficiencies and procurement efficiencies of the design build project. RICWS is the first project to use IDIQ contracting in Minnesota, not only allowing MnDOT Districts to add ICWS sites to the state highway system but Minnesota Counties to add sites to the county system as well. RICWS includes a three year contractor warranty (for all sites until December 2016). The warranty covers defects in materials and construction as well as malfunctions. The contractor has 72 hours to respond to warranty call outs. The Contractor will determine the cause of the malfunction and repair or replace equipment as necessary. Events outside of the contractor s control, such as knockdowns, weather related, or acts of vandalism are not included in the warranty. MnDOT has the option to extend the contractor warranty in one year increments for two additional years. RICWS is includes a Safetran ASC/3 signal controller, 334-Z controller cabinet, Rural Lighting and Flasher service cabinet, Canoga micro-loop detectors (major road), preformed loop detectors (minor road), static signing (major road), LED blank-out signs (minor road), and flashing beacons. To ensure a successful project, RICWS has three supporting contracts. RICWS Contract Development assisted MnDOT in preparing the RICWS contract documents and predesign build letting activities. Parsons Brinkerhoff and SEH, the state s General Engineering Consultant assisted in the creation of the RICWS Request for Qualifications, Instructions for Proposers, Request for Proposals (RFP), and RFP addendums and clarifications. RICWS Design and Construction Oversight assists MnDOT in oversight of the design build project by final design reviews, system testing, construction inspection, and warranty evaluation. SRF Consulting is assisting with oversight including testing for turn on acceptance and system acceptance at the end of the warranty. SRF will compile a warranty report after one year of operation and again at the end of the warranty period, documenting all service calls and work performed, mean time to failure, and material and labor costs associated with work performed. RICWS Reliability Evaluation will evaluate the first ICWS installed in Carver County (Truck Highway 7 at County State Aid Highway 33) by design build project for a minimum period of 30 days to demonstrate reliability of the system and the system performance requirements. The University of Minnesota will install a portable intersection surveillance system (ISS), collect data from the ICWS, and compare the data to the ISS system. The University will create the summary report every 96 hours and a final evaluation. Successful completion of this testing will ensure system reliability and allow the Design Build Contractor to continue to install systems at the other 19 and IDIQ locations. Benefits Reduce the number and severity of crashes at rural intersections Low cost safety improvement (alternative to geometric improvements) Next Steps MnDOT Safety Unit will be evaluating the ICWS for effectiveness at reducing severe and fatal crashes. Continue work with ENTERPRISE Pooled Fund Study including developing warrants for intersection conflict warning systems. Include a major road warning only for higher volume expressways in future projects. Page 14 of 14