796 excess materials, cleaning fluids, and empty material containers; the costs being considered as included in the contract items. Removal of curing compound from new Portland cement concrete pavement will be measured along the centerline of the line of curing compound being removed or by the unit each for symbols and legends, as appropriate. Measurement of a line of removal of curing compound will be based on a 4- inch wide line, and shall be measured by the linear foot, and in accordance with the items of work established in the bid schedule. Measurement for lengths of removal of curing compound with a plan width greater than 4 inches as shown on the plans or directed by the Engineer will be made by the same method and then adjusted by the following factor: Plan Width (inches) x Linear Feet 4 (inches) The plan width will include an extra 4 inches – 2 inches on each side – beyond the plan width of pavement marking and will be based on a continuous length of pavement marking lines unless indicated on the project plans. The cost for abrasive- blasting and grinding existing markings, not including temporary paint or tape lines, shall be paid for under separate items. No separate payment will be made for removing temporary paint or tape lines, the cost being considered as included in contract items. 709- 5 Basis of Payment: The accepted quantities of dual component pavement markings of the type specified in the bidding schedule, measured as provided above, will be pai d for at the contract unit price, complete in place, including pavement surface preparation and glass beads. The accepted quantities for removal of curing compound from new Portland cement concrete pavement, measured as provided above, will be paid for at the respective contract unit prices, under the items of work established in the bid schedule. 710- 1 Description: The work under this section shall consist of furnishing and installing a fully functional, automated, and portable Smart Work Zone (SWZ) system; operating, maintaining, and servicing the portable SWZ system; and relocating and removing various components of the system, as specified herein and in accordance with the project plans and specifications. TABLE OF CONTENTS INDEX 797 710- 1.01 Abbreviations: Wherever the following abbreviations are used in these specifications, the contract, or in other contract documents, they are to be construed the same as the respective expressions represented: CCTV Closed- Circuit Television CMB Changeable Message Board DMS Dynamic Message Sign DLMS Dynamic Lane Merge Subsystem FMS Freeway Management System GPS Global Positioning System GUI Graphical User Interface O&M Operations and Maintenance PDA Power Distribution Assembly PTZ Pan, Tilt, and Zoom QWS Queue Warning Subsystem SWZ Smart Work Zone TCP Traffic Control Plan TDC Traffic Data Collection TDCS Traffic Data Collection Subsystem TMCS Traffic Monitoring Camera Subsystem TOC Traffic Operations Center TTS Travel Time Subsystem VSL Variable Speed Limit VSLS Variable Speed Limit Sign TABLE OF CONTENTS INDEX 798 710- 1.02 Definitions: Wherever the following definitions are used in these specifications, the contract, or in other contract documents, the intent and meaning shall be interpr eted as follows:
The SWZ system is a broad range of portable communications- based information and electronic technologies placed in and around work zones to enhance transportation and improve safety and mobility. The real - time information and automation provided by the SWZ system is used by contractors and transportation agencies to alter traffic control strategies and provide traveler information to better inform motorists of upcoming traffic conditions, allow motorists the opportunity to alter their travel routes, and/or modify the travel behavior within work zones. The SWZ system is comprised of one or multiple SWZ subsystems that operate together.
The SWZ area is the area where SWZ field devices are deployed near, within, and/or around the project and work zo ne limits.
The active work space is the area that is anticipated to have the largest concentration of field personnel within the work zone during a specific day or construction shift. The personnel working in active work space are exposed to the dangers of an errant vehicle.
The work zone is the entire area in which traffic control is placed, both static signs and SWZ field devices.
The TDCS is a component of the SWZ system that is capable of detecting, processing, and disseminating real -time traffic information such as vehicle speeds, traffic volumes, and travel time/delay within and in advance of the work zone for use by other SWZ subsystems, third - party traveler information systems, and/or to archive work zone traffic conditions. This subsystem could also include the use of third- party data, solely, or in combination with site specific gathered data.
The QWS is a component of the SWZ system that uses the real -time TDCS information to determine traffic queue lengths. The QWS warns TABLE OF CONTENTS INDEX 799 approaching travelers of slowed or stopped traffic conditions through warning messages displayed on SWZ CMBs. When a queue begins to form, the QWS automates the display of warning messages on the associated SWZ CMB displays located in advance of the anticipated queueing areas. The QWS also alerts field personnel and remote SWZ system operators of the real -time queueing conditions.
The DLMS is a component of the SWZ system that uses the real -time TDCS information and SWZ CMBs, in advance of a lane closure, to instruct approaching travelers when to merge. When traffic volumes are high or a potential queueing condition is detected by the DLMS, the DLMS automates the display of messages that instruct drivers to merge later. When traffic volumes are low and a potential queueing condition is not detected in advance of the lane closure, the DLMS automates the display of messages that instruct drivers to merge earlier.
The TTS is a component of the SWZ system that uses the real -time TDCS information and SWZ CMBs, in advance of the work zone, to determine the approximate travel time between the SWZ CMB location and another fixed point as shown on the project plans, or at the end of the work zone. The TTS automates the display of messages on each CMB to inform the drivers of the associated travel time (at predetermined locations) through the work zone. In addition, the TTS is capable of comparing real -time TDCS information to historical travel time information to estimate the approximate travel delay that a driver can expect, when traveling through the work zone.
The TMCS is a component of the SWZ system that uses closed- circuit television (CCTV) cameras to provide real -time video streams that are monitored on- site by field personnel using a mobile display device and/or remotely by the Engineer, Traffic Operations Center (TOC) operators, and the Distri ct to view real -time roadway traffic conditions within the work zone.
The VSL subsystem is a component of the SWZ system that uses TDCS real -time traffic information and variable speed limit signs (VSLS) to dynamically reduce or increase regulatory speed limits in the work zone. Regulatory speed limits are dynamically reduced in the active work space. Regulatory speed limits are dynamically increased within the same area of the work zone when the construction personnel are not present. TABLE OF CONTENTS INDEX 800
The SWZ system software is a software platform that can receive, store, analyze, send, and display real -time information from the TDCS, QWS, DLMS, TTS, TMCS, and VSL subsystem field devices, Department furnished data from roadway sensors, or other third- party sources. The SWZ system software provides the required automation, GUI, user device applications, and system reports required to operate and maintain each respective SWZ subsystem deployed within the SWZ area. 710- 2 Materials (Equipment, Workers, Devices and Facilities): The SWZ system shall contain the selected SWZ subsystems including all necessary auxiliary field device equipment, the SWZ system software for each selected SWZ subsystem, the communications and third- party data services, system operations, maintenance, and support services to provide a complete SWZ system. The selected SWZ subsystems may consist of one or more of the following: TDCS, QWS, DLMS, TTS, TMCS, VSL, or other type of subsystem as indicated on the plans or specifications. The auxiliary field device equipment shall include all appurtenances such as traffic detectors, changeable message boards, CCTV cameras, variable speed limit signs, static SWZ signs, device trailers, mounting assemblies, communications and geolocating devices, power assemblies, wiring, and accessories. The communications services shall include all services needed for connecting the field devices to the remote SWZ system software and connecting the SWZ system software to the internet and communications service provider networks that the system users and Department representatives have access to for connectivity into the SWZ system. The system operations, maintenance, and support services shall include all services req uired to deploy, integrate, configure, test, operate, and maintain the SWZ system communications and geolocating devices, third -party data services, field devices, and software for continuous operations in and around the project work zones. 710- 2.01 General Requirements: The contractor shall submit the SWZ system and the associated field devices as part of the TCP and safety plan. Except as specified herein, all equipment, procedures used by workers, devices, and facilities shall conform to the requi rements of Subsection 701- 2 of the specifications. TABLE OF CONTENTS INDEX 801
The contractor shall submit a SWZ material proposal at the preconstruction conference or when reasonably feasible. If the contractor’s SWZ material proposal is not submitted at the preconstruction conference, each SWZ subsystem submittal shall be shown in the work schedule. The contractor's SWZ material proposal shall include the following and any other necessary documents to fully describe the proposed SWZ subsystems and field device items:
A Certificate of Compliance conforming to the requirements of Subsection 106.05 of the specifications shall be submitted for each SWZ subsystem assembly. The Department reserves the right to require Certificates of Compl iance for the subsystem functionality provided within the SWZ system software, for each field device assembly component, and for third- party data sources. The Department reserves the right to perform independent evaluations or tests on any SWZ System Softw are, equipment, or service supplied by the contractor in the work zone.
The credentials of the contractor’s designated SWZ technician(s) skilled in the operation of all the SWZ system equipment and software shall be submitted to the Engineer for approval. There shall be a designated SWZ technician for each shift of work and the qualifications of the designated technician(s) shall demonstrate the following:
system is in use and abl e to respond to the SWZ system issues in person within one hour of notification;
deployments, device configurations, system testing, trouble shooting, maintenance, and component level repair or replacement ; and
technologies on projects with roadway construction valued at one million dollars or more, or has relevant experience that is approved by the Engineer. TABLE OF CONTENTS INDEX 802 If the contractor would like to replace one or more SWZ technician(s), then the new technician(s) shall be approved by the Engineer prior to assuming these duties on the project.
A communications site assessment shall be submitted to the Engineer for approval at least six weeks before mobilizing field equipment for deployment in the project area. The communications site assessment shall identify the specific communications service(s) that the contractor has selected for connecting the field devices to the remote SWZ system software and for documenting the contractor’s approach for verifying these communications services are available within the project limits. The results of this com munications site assessment shall be summarized and indicate that the selected communications approach(es) provides sufficient data network capacity and coverage needed for proper SWZ system operations within and in advance of the work zone.
The contractor shall submit a SWZ system configuration plan to the Engineer for approval at least six weeks before mobilizing field equipment for deployment in the project area. The plan shall describe the system logic and field device layout concepts to be used. The SWZ system configuration plan shall demonstrate the following:
element within the SWZ area such as, but not limited to, TDC, CMB assembly, VSLS assembly, traffic monitoring camer a assembly, and auxiliary SWZ equipment for each type of anticipated TCP. Include how each of these device locations plays a role in the overall deployment concepts of the SWZ system ; and
subsystem (i.e., TDCS, QWS, DLMS, TTS, TMCS, and VSL) that describes how the system responds when various traveler information and system logic thresholds are reached. This includes, but is not limited, to the following:
and which Department representatives will receive the alert messages;
limits, controls, and display messages have been coordinated with the Department for initial system configuration; and TABLE OF CONTENTS INDEX 803
and display messages can be changed by system users via the SWZ software interface, and what system safeguards are in place to limit the ranges and messages that are selectable by these system users.
The contractor shall submit a SWZ system O&M plan to the Engineer for approval at least four weeks before mobilizing field equipment for deployment in the project area. The SWZ system O&M plan shall identify the contractor’s means and methods for deploying, operating, and maintaining the SWZ system equipment and software. The SWZ system O&M plan shall demonstrate the following:
assigned for every work shift. Contact information shall be provided for each SWZ technician so that the Engineer can notify the technician(s) of a SWZ system issue and the SWZ technician can respond to the SWZ system issue in person within one hour of notif ication;
and days/hours of support provided for the SWZ system software and each associated subsystem ; and
operations of SWZ field devices, including but not limited to:
changing construction activities, changing traffic queuing conditions, TCP changes, or as directed by the Engineer or contractor ;
setting different software logic thresholds and limits, setting days/times and system activities with the software scheduler, selecting different display messages to be posted on the SWZ CMB, changing user alerts and recipients receiving the alerts, changing system software users and levels of access, and making changes to the system logic, configuration, and users in general ; TABLE OF CONTENTS INDEX 804
maintenance log for all associated O& M activities; and
damaged, stolen, or has become an inoperable component of the overall SWZ system.
Schedule: A SWZ Software User Training Curriculum Outline and Schedule shall be submitted for each SWZ subsystem assembly. The training curriculum and contractor provided training shall reflect the actual needs of the Department’s system users and field personnel and include the following sections:
Collection;
Changes with the SWZ Software Configuration and Field Device Deployments . The contractor shall coordinate with the Engineer to identify mutually agreed upon training dates and times for each training class.
The contractor shall coordinate with the Engineer and provide a SWZ User Access Privileges submittal that clearly identifies each Department user by first and last name and the associated level of access that each of these users will have when logging into the system. TABLE OF CONTENTS INDEX 805 The contractor shall coordinate with the Engineer and provide a SWZ Alert Messages submittal that clearly identifies each Department stakeholder by first and last name, the associated types of system generated alerts they will receive and the method (email or text) the alert is received.
The contractor shall submit an example set of each required SWZ system data report to the Engineer for approval at least two weeks before deploying SWZ field equipment in the project area. The example set shall demonstrate the contractors proposed format for each report, the types of data included within each report, t he frequency of the data within the report (i.e., once per minute, five minutes, etc.), and the time period to by covered by each individual report (i.e., each report represents a days’ worth of data, a weeks’ worth of data, etc.). The SWZ system data reports shall be submitted on a weekly basis, in the approved format, and contain the actual work zone data collected during that week of SWZ system deployment. In accordance with the ADOT Work Zone Safety & Mobility Policy, to monitor and measure work zone i mpacts during construction, the SWZ system data report shall include the following sets of data:
Each SWZ system data report shall include the geolocation(s) that the data is associated with. If the intelligence of the SWZ subsystem(s) required in the project plans and specifications does not generate the above sets of data and the associated reports, then the SWZ system provided shall have the ability to support manual entry of this data and the ability to archive and generate reports of the manually entered data. The contractor's SWZ system data reports shall include any other information that may be required for each type of SWZ subsystem deployed.
A system acceptance testing procedures submittal shall be submitted for each SWZ subsystem assembly to demonstrate proper operation of all subsystems and device configurations. The testing procedures shall include the following: TABLE OF CONTENTS INDEX 806
Initial system and device testing is intended to demonstrate that each subsystem component provided and its associated configurations for the project work zone successfully achieves all of the required functionality, performance, and reporting requirements.
Individual SWZ field device location testing is intended to verify that a specific field device is conf igured correctly, communicating, and operating properly when moved in the SWZ area after initial system setup.
A Certificate of Analysis conforming to the requirements of Subsection
106.05of the specifications shall be submitted f or each SWZ subsystem
assembly each time the contractor deploys an associated field device component and completes the associated tests in accordance with the approved subsystem acceptance testing procedures.
Auxiliary SWZ equipm ent is considered incidental components that may be required to achieve a fully functional SWZ system. The following are some common types of auxiliary equipment and their associated minimum requirements:
All SWZ systems shall provide the necessary communications devices and services to connect the field devices to the remote SWZ system software and to connect the SWZ system software to the internet and communications service provider networks. The SWZ system communications shal l provide continuous service to the devices of the system operators, users, and Department representatives. The SWZ system communications devices and services provided shall be in accordance with the approved communications site assessment, as described i n Subsection 710- 2.01(A)(3) of the specifications. The SWZ system communications devices and services shall provide sufficient data network capacity and coverage needed for proper SWZ system operations within the SWZ area.
The geolocation of intelligent field devices and data sets reported shall be provided using a GPS device accurate within 3 meters (9.84 feet) of TABLE OF CONTENTS INDEX 807 the actual location or provided by some other method for geolocating devices and information, as approved by the Engineer. All SWZ systems shall provide a GUI that displays the actual deployed location of each intelligent device that is communicating with the SWZ system software using the approved geolocating method. All third -party information used by the SWZ system software and used within SWZ system data reports shall include the geolocation(s) associated with the information provided.
All SWZ system field devices shall be independently powered and shall be powered for operation continuously during all deployment periods within the SWZ area and shall be provided with a means for alerting remote system users and operators of a low power or loss of power condition. The SWZ system shall have the ability to archive and generate reports on power condition alert messages received from SWZ system field devices deployed within the SWZ area. This archived data shall include the associated device name and number and shall include the date and time of each alert message. All po wer supplies shall have capacity to support at least 72 hours of continuous operation. Examples of acceptable power supplies include:
replace batteries and equipment as necessary for continuous SWZ system operations in accordance with the approved SWZ system O&M plan;
shall clean and adjust the position of solar panels and replace equipment as necessary for continuous SWZ system operations in accordance with the approved SWZ system O&M plan; and
contractor shall replace fuel and equipment as necessary for continuous SWZ system operations in accordance with the approved SWZ system O&M plan.
When SWZ system field devices are mounted to portable trailers deployed within the SWZ area the portable trailers shall meet the following requirements: TABLE OF CONTENTS INDEX 808
area shall have a trailer number that is easil y visible from the first vehicle travel lane adjacent to the deployed trailer. All trailers deployed in the SWZ area shall have different numbers to uniquely identify and differentiate one trailer from another ;
support driving speeds up to 65- mph when being towed, and be equipped with a standard size trailer hitch;
leveling legs that can support the weight of a fully loaded trailer with the tires removed. The adjustable height of the legs should be able to raise the trailer wheels a minimum of 4 inches between the bottom of the wheels and a flat/level surface that the trailer is standing on. Each leg shall be independently adjustable to support leveling the base of the trailer when deployed on a sloped area;
the fully loaded trailer shall be capable of withstanding wind gusts up to 80 -mph without overturning or changing orientation;
brackets are provided for CMBs and VSLSs, they shall be provided with the ability to adjust the tilt angle of the display board in accordance with the display board manufacturer’s recommendations for the optimal viewing angle;
telescoping poles are provided to increase the mounting height of cameras and traffic detection devices, they shall be provided with the ability to rotate the pol e, from ground level, in support of adjusting the horizontal viewing/detection angle of the device(s) mounted towards the top of the pole; and
geolocating devices, local processing devices, batteries, and other PDA components, they shall be provided with security provisions to deter and delay theft of equipment inside the housing. TABLE OF CONTENTS INDEX 809
Equipment: Static traffic control devices for SWZ field equipment shall consist of furnishing, installing, maintaining, moving and removing barricades, warning signs, cones, and other traffic control devices, per the approved traffic control plans, through or around the SWZ system field device locations deployed in or adjacent to the work zone. The static traffic control devices for SWZ field equipment shall be provided in accordance with the requirements of Part VI of the current edition of the Manual on Uniform Traffic Control Devices (MUT CD) and the current edition of the associated ADOT MUTCD supplement. 710- 2.02 SWZ Traffic Data Collection (TDC) Location: Each TDC location shall be equipped with all detecting, processing, and disseminating equipment and functionality needed to deliver r eal-time traffic information. The traffic data collected, shall be practicable for the SWZ subsystem identified such as vehicle speeds, traffic volumes, and occupancy within an area of the roadway that provides a single direction of travel with one or more travel lanes for that location. If required in the project plans or special provisions, additional traffic data shall be collected for vehicle classification and all data shall be collected “per lane”. Each TDC location shall include all of the equipment necessary to provide a fully functional component of the SWZ system. A minimum of two TDC locations shall be provided to generate the required travel time and travel delay traffic information; unless a third- party traveler information system is used to pr ovide the travel time/delay for the location (i.e. a single route between two or more points). All TDC locations shall provide the SWZ system software the following information:
interval of one- minute;
interval, computed by the TDC locations, or computed by the SWZ system software based on the per minute data provided by the TDC location( s);
information provided shall be a representative sample of all travel lanes combined as one for the same direction of travel ; and
shall be time stamped with the actual date and time, with a TABLE OF CONTENTS INDEX 810 tenth of a second accuracy, for each one- minute time interval sent to the SWZ system software. Each TDC location deployed within the SWZ area shall have a number to uniquely identify that location and differentiate it from all other TCD locations. When the TDC location is comprised of field traffic sensor(s) the location number shall be displayed within the SWZ system software and shall be easily visible by field personnel at the location were the device(s) are mounted. When the field traffic sensors are mounted on a portable field device trailer the TDC location number used shall be the same number that is visible on the trailer. When third- party data is used to collect the traffic data, the location number only needs to be displayed within the SWZ system software to identify each location where the data is being collected. When third- party data is used to collect travel -times between two locations, a unique route number shall be used to identify the location of each different route. All TDC locations shall provide additional traveler information, as necessary, to achieve the functionality of other SWZ subsystems required by the project plans and specifications. 710- 2.03 SWZ Changeable Message Board (CMB) Assembly: Each SWZ CMB assembly shall be equipped with a changeable message display board and all processing and disseminating equipment, and have the functionality required to deliver automated messages generated by the SWZ system software to the travelling public via the message display boards of the SWZ CMB assembly. Each SWZ CMB assembly shall include all of the equipment necessary to provide a fully functional component of the SW Z system. Each SWZ CMB assembly shall be provided and deployed in accordance with the MUTCD requirements for portable changeable message signs (MUTCD Section 6F.60) and the following:
minimum of 18 inches, unless deployed on low speed facilities (40- mph or less). Shorter letter sizes may be used for SWZ CMB messages when deployed on low speed facilities provided that the message is legible from at least 650 feet ;
legibility requirements and not impair the driver’s vision; TABLE OF CONTENTS INDEX 811
that is used when communications with the SWZ system software are lost for a predetermined amount of time. The default message state shall support the following options:
SWZ system software.
controls. When the local manual override controls are used, the SWZ CMB shall:
messages;
phases, and a phase should consist of no more than three lines of text. Each phase should be capable of being understood by itself, regardless of the order in which it is read. Messages should be centered within each line of the legend. If more than one portable SWZ CMB is simultaneously legible to road users, then only one of the signs should display a sequential message at any given time ; and
seconds and the sum of the display times for both of the phases should be a maximum of eight seconds. Each SWZ CMB assembly deployed within the SWZ area shall have a unique number to identify that location and differentiate it from other SWZ CMB locations. When the SWZ CMB assembly is mounted on a portable field device trailer t he SWZ CMB assembly number used shall be the same number that is visible on the trailer. 710- 2.04 SWZ Traffic Monitoring Camera Assembly: Each traffic monitoring camera assembly shall be provided with all cameras, video processing and disseminating equipm ent, and functionality needed to provide real -time viewing of traffic and roadway conditions, from a remote location and through the SWZ system software. Each SWZ traffic monitoring camera assembly shall provide the ability to view all approaching directi ons of the roadway, relative to the camera assembly deployment location, using one or more cameras mounted at an appropriate mounting height for viewing the roadway and TABLE OF CONTENTS INDEX 812 traffic conditions. Each SWZ traffic monitoring camera assembly shall include all of the equipment necessary to provide a fully functional component of the SWZ system. All SWZ traffic monitoring camera assembly locations shall provide the following camera functionality:
interface display window ;
of each camera, remotely from the SWZ system software, locally at the camera assembly location, or both;
During daytime operations a color video stream shall be provided. During nighttime operations the camera shall function in low light conditions and support color, black- and- white, or both types of video streams;
Iris and auto- focus functionality, or both;
each approaching direction of the roadway, relative to the camera assembly deployment location, when a pan -tile-zoom functionality is provided for remote operations; and
Each traffic monitoring camera assembly location deployed within the SWZ area shall have a unique number to identify that location and differentiate it from other traffic monitoring camera assembly locations. When the traffic monitoring camera assembly is mounted on a portable field device trailer the traffic monitoring camera assembly location number used shall be the same number that is visible on the trailer. 710- 2.05 SWZ Variable Speed Limit Sign (VSLS) Assembly: Each VSLS assembly shall be provided with a changeable message display board for posting regulatory speed limits and all processing and dissemi nating equipment and functionality needed to deliver SWZ system software generated speed limits to the traveling public via the changeable message display board of the VSLS assembly. Each VSLS assembly shall include all equipment necessary to provide a fully functional component of the SWZ system. Each VSLS assembly shall be provided and deployed in accordance with the MUTCD requirements for Regulatory Speed Limit Signs (MUTCD Section 2B.13) and the following: TABLE OF CONTENTS INDEX 813
MUTCD, with white colored lighted pixels that display the speed limit message on a black background;
automatically adjust its light source to meet the MUTCD legibility requirements and not impair the driver’s vision;
software is lost for a predetermined amount of t ime. The default message state shall support the following options:
location; and
from the SWZ system sof tware.
override controls. When the local manual override controls are used, the VSLS display shall:
when moving the sign to a new deployment area.
used in advance of the first VSLS location deployed to inform road users of a variable speed limit zone where the speed limit may be reduced by more than 10 mph. The Variable Speed Zone Ahead warning sign shall be a similar shape, size, and color to the Reduced Speed Limit Ahead (W3- 5) or XX MPH Speed Zone Ahead (W3- 5a) sign type of the MUTCD ;
after the last VSLS location deployed to inform road users that the variable speed limit zone has ended. The End of Variable Speed Zone warning sign shall be a similar size and color to the Reduced Speed Limit Ahead (W3- 5) or XX MPH Speed Zone Ahead (W3- 5a) sign type of the MUTCD ; and
“VARIABLE SPEED ZONE AHEAD” warning sign and the “END OF VARIABLE SPEED ZONE” warning sign when TABLE OF CONTENTS INDEX 814 required in the project plans and specifications. When required, warning beacons shall comply with the MUTCD (Section 4L.03). Each VSLS assembly deployed within the SWZ area shall have a unique number to identify that location and differentiate it from other VSLS locations. When the VSLS assembly is mounted on a portable field device trailer t he VSLS assembly number used shall be the same number that is visible on the trailer. 710- 2.06 SWZ System Software: The SWZ system software shall receive, store, analyze, and display real - time information received from each TDC location, SWZ CMB assembly, VSLS assembly, traffic monitoring camera assembly, and the associated auxiliary SWZ equipment deployed within the project SWZ area, and provide the control logic, system configurations, automation, and commands for the SWZ CMB and VSLS display messages an d speed limits. The SWZ system software shall be provided with all hardware, device drivers, and auxiliary SWZ equipment necessary to provide a fully functional component of the SWZ system that is accessed remotely by system operators, users, and Department representatives via the internet and by using the software’s client interface provided for use during the project. The SWZ system software shall archive all loss of communications, low power, and loss of power alerts for the project duration. The SWZ system software vendor shall archive the following data for a minimum period of seven years after final project acceptance for downloading by Department representatives and this archived data shall be submitted to the Engineer in accordance with the Work Zone Data Exchange Common Core Data Specification version available on the bid opening date: All real- time traffic information received by the SWZ system software from all TDC locations deployed in the SWZ area and received by third-party sources, and all real -time traffic information generated by the SWZ system software within every one- minute time interval. All messages posted on all SWZ CMB assemblies deployed in the SWZ area. All speed limits on all VSLS assemblies deployed in the SWZ area. All geolocation data associated with these devices and the required device data. A date and time stamp that the data pertains to each data set. TABLE OF CONTENTS INDEX 815 The SWZ system software and services provided shall include setting limits and controls on the types of messages that can be displayed on SWZ CMB assemblies. See Section 710- 2.03 of the specifications, SWZ Changeable Message Board (CMB) Assembly for the detailed limits and controls. The SWZ system software and services provided shall include creating a “Message Library” of project specific and Engineer approved messages that can be displayed on the SWZ CMBs within the SWZ area. The SWZ system client interface shall: Not have a limit to the number of Department representatives that can access the SWZ system software independently from different locations throughout the State of Arizona using an internet link and web browser. The SWZ system software shall be configured to limit the level of access granted to different users to help protect against accidental and malicious acts that can impact the integrity of system performance, configurations, CMB display messages, and posted VSLS speed limits. Be a vendor hosted web site or software application(s) downloadable from one or more internet locations identified by the SWZ syst em software vendor(s). Be accessible using personal computers (PC) running a Windows operating system and mobile devices running an Apple or Android operating system. The version of Windows used shall be compatible with the versions supported by ADOT’s Engineer, District, and TOC. Include a GUI that displays the location of each TDC location, SWZ CMB assembly, VSLS assembly, and traffic monitoring camera assembly deployed within the project SWZ area on a map and provides the associated unique numbers that identifies each location. The SWZ system software shall be configured to use the same unique numbers that have been imprinted on the actual devices in the SWZ area. Provide the ability for Department representatives to see the current status of each TDC location, SWZ CMB assembly, VSLS assembly, and traffic monitoring camera assembly deployed within the project SWZ area, view all archived data received from these field devices and the archived results of manual and system processed commands sent to field devices which display messages and speed limits to the traveling public. The SWZ system software shall be comprised of the following subsystems integrated together as one complete system, as multiple separate software platforms, or any combination t hereof, as required by the project plans and special provisions: TABLE OF CONTENTS INDEX 816
The TDCS shall be integrated with each TDC location deployed within the SWZ area to receive, archive, process, and disseminate the real - time traffic information for use by the other SWZ subsystems and by the Department for historical information, documentation, and future analyses. The SWZ system GUI shall be configured to display each TDC location deployed within the SWZ area and the TDCS shall provi de the following:
impacted by construction activities within every one- minute time interval for data archiving ;
construction activities averaged together within a maximum time interval of one- minute for data archiving ;
compliance value based on the actual vehicle speed value compared to the posted speed limit value within every one- minute time interval for data archiving ;
beginning of the work zone and one at the end, averaged together within a maximum time interval of one- minute for data archiving for each direction of travel impacted by construction activities;
beginning of the work zone and one at the end, averaged together within a maximum time interval of one- minute for data archiving for each direction of travel impacted by construction activities. The travel delay values shall be based on the SWZ system generated real -time travel time data compared to a contractor provided “baseline set travel time data” that represents the typical travel time between the same two points, for each one- minute interval with each day of the week, when there was no construction or incident that would cause a travel delay;
are causing or anticipated to cause traffic queuing for each direction of travel. The contractor proposed maximum time interval for data archiving and the methods used to determine queue lengths shall be approved by the Engineer prior to SWZ system deployment within the work zone; TABLE OF CONTENTS INDEX 817
compliance, travel time, travel delay, and queue length values based on longer time intervals, as selected by the Department representative through the SWZ system client interface, for generating the associated traffic information reports;
compliance, travel time, travel delay, and queue length values based on longer time intervals and associated alert message thresholds approved by the Engineer to send SWZ system generated alert messages to Department representatives via email or text messages; and
within the SWZ area based on the following data generated by the SWZ system or input into the SWZ system, by the contractor, using the SWZ system client interface:
site; and
The TDCS shall be integrated with other required SWZ subsystems and receive, process, and disseminate additional types of the real -time traffic information that may be required by these other SWZ subsystems.
The QWS shall be integrated with the TDCS and the SWZ CMB assemblies to determine traffic queue lengths and warn approaching travelers of slowed or stopped traffic conditions. The SWZ system GUI shall be configured to display each SWZ CMB assembly and TDC location associated with the QWS and the QWS component of the SWZ system and services shall provide the following: TABLE OF CONTENTS INDEX 818
thresholds, within ranges approved by the Engineer, for the QWS automation logic that decides which queue warning message to display on each associated SWZ CMB location;
“Message Library” can be used by the QWS for each of the diff erent logic threshold scenarios;
by the Engineer, that a QWS generated message should be displayed on each SWZ CMB, before the QWS can change the message;
the process of displaying warning messages on the associated SWZ CMB assemblies located in advance of the anticipated queueing areas;
QWS displays and removes warning messages on the associated SWZ CMB assemblies; and
Department’s TOC operators via email and text messages asking them to consider displaying and removing queue warning related messages on specific FMS DMS locations in advance of the queueing area.
The DLMS shall be integrated with the TDCS and the SWZ CMB assemblies to determine traffic volumes and queueing conditions in advance of a lane or shoulder cl osure and instruct approaching travelers of when they should merge. The SWZ system GUI shall be configured to display each SWZ CMB assembly and TDC locations associated with the DLMS. The DLMS components of the SWZ system and services shall provide the f ollowing:
thresholds, within ranges approved by the Engineer, for the DLMS automation logic that decides which merge message to display on each associated SWZ CMB location;
“Message Library” can be used by the DLMS for each of the different logic threshold scenarios; TABLE OF CONTENTS INDEX 819
by the Engineer, that a DLMS generated message should be displayed on each SWZ CMB, before the DLMS can change the message;
condition is detected by the DLMS, the DLMS shall automate the process of displaying pre- approved messages on the associated SWZ CMB assemblies that instruct drivers to merge later ;
automate the process of displaying pre- approved messages on the associated SWZ CMB assemblies that instruct drivers to merge earlier ;
automatically changes messages on the associated SWZ CMB assemblies; and
asking them to consider adding or removing merge instructions displayed on specific FMS DMS locations in advance of the closure.
The TTS shall be integrated with the TDCS and the SWZ CMB assemblies to determine real time travel times and travel delays between each associated SWZ CMB assembly and an Engineer approved end destination point within the SWZ area. The TTS shall also provide display messages on each respective SWZ CMB with the travel tim e and travel delay information. The SWZ system GUI shall be configured to display each SWZ CMB assembly and TDC route associated with the TTS. The TTS component of the SWZ system and services shall provide the following:
thresholds, within ranges approved by the Engineer, for the TTS automation logic that decides which travel time or travel delay message to display on each respective SWZ CMB;
“Message Library” can be used by the TTS for each of the different logic threshold scenario; TABLE OF CONTENTS INDEX 820
by the Engineer, that a TTS generated message should be displayed on each SWZ CMB, before the TTS can change the message;
values will be displayed with the respective SWZ CMB display messages:
or ten, or round- up to the nearest multiple of five or ten; and
below this value respectively.
Department representatives when the TTS displays a specific type of message on one of the respective SWZ CMB, or if the travel times and travel delay values exceed a predetermined threshold.
The TM CS shall be integrated with all the SWZ traffic monitoring camera assembly locations within the SWZ area and provide real -time viewing of the associated camera video streams for field personnel using mobile display devices and remotely by the Engineer, the TOC operators, and the District to monitor real -time roadway traffic conditions within the work zone. The SWZ system GUI shall be configured to display the location of each SWZ traffic monitoring camera assembly and the TMCS component of the SWZ system and services shall provide the following:
traffic monitoring camera assembly location when selected from within the SWZ system GUI ;
of each SWZ traffic monitoring camera assembly;
operations for each SWZ traffic monitoring camera assembly;
TABLE OF CONTENTS INDEX 821
each SWZ traffic monitoring camera assembly, when PTZ cameras are deployed.
The VSL subsystem shall be integrated with the TDCS and the VSLS assemblies located in the SWZ ar ea to reduce regulatory speed limits within the area(s) of the work zone that has the largest concentration of construction personnel exposed to the danger of an errant vehicle and raises the speed limit when construction workers are not present. The conf iguration of the VSL subsystem shall include the unique number of a TDC location that is deployed near the center of the Active Work Space and this field device location shall be referred to as the Active Work Space TDC location. The VSL subsystem shall pr ovide system automation logic that changes the posted speed limits based on the real - time traffic information it receives from the Active Work Space TDC location. The VSL subsystem shall include a variable that represents the length of the Active Work Space and the ability to set a maximum value for this variable. This maximum value which represents the maximum allowable Active Work Space length shall be set to 2 miles, unless otherwise approved by the Engineer. The SWZ system GUI shall be configured to di splay the Active Work Space TDC location, the length of the Active Work Space, the location of each SWZ VSLS deployed within the work zone, and the real -time speed limit posted on each SWZ VSLS. The VSL subsystem component of the SWZ system and services shall provide the following:
value that can be posted on a VSLS for each direction of travel within the project limits;
frequency between changes that a VSL subsystem generated speed limit should be displayed on each VSLS, before the VSL subsystem can change the speed limi t;
loweri ng speed limits between any two consecutive VSLS locations within the same direction of travel ;
VSLS are in advance of the Active Work Space, within the Active Work Space, and subsequent to the Active TABLE OF CONTENTS INDEX 822 Work Space, each time the contractor moves the Active Work Space TDC location within the project limits;
speed limits within the Active Work Space and on the VSLS directly in advance of the Active Wor k Space, while dynamically raising the speed limits on the other VSLS devices to the maximum allowable speed limit for the work zone;
Active Work Space TDC real -time traffic information thresholds, within ranges approved by the Engineer, for the VSL subsystem automation logic that decides which speed limits to post each respective SWZ CMB ;
on all the VSLS to the maximum speed limit value or other user selectable lower value based on the time- of- day and day- of-week scheduler and manual overrides to the schedule;
1 sign type, per the MUTCD, with white colored lighted pixels for displaying the speed limit message on a black background; and
messages on the associated VSLS contain a user selectable speed limit value. 710- 3 Construction Requirements: The contractor shall coordinate with the Engineer and provide the SWZ software user training to the Department representatives. The contractor shall provide the Department representatives with SWZ software user access privileges including alert messages. The SWZ system shall be deployed in accordance with the approved TCP, communications site assessment, system configuration plan, and subsystem acceptance testing procedures and provide the required certificate of analysis. The contractor shall operate and maintain the SWZ system in accordance with the approved SWZ system O&M plan, relocate TDC locations, SWZ CMB assemblies, VSLS assemblies, traffic monitoring camera assemblies, and the asso ciated auxiliary SWZ equipment deployed within the project SWZ area as necessary to achieve the SWZ system operational objectives. The required certificate of analysis shall TABLE OF CONTENTS INDEX 823 be submitted to the Engineer each time one of the field device locations is moved. During deployment in the SWZ area, the contractor shall submit the required SWZ system data reports to the Engineer for approval within the Engineer approval time frames. Any deficiencies in the communications site assessment, SWZ system configuration plan, O&M plan, devices, equipment, services, or other elements of work listed herein will be brought to the attention of the contractor by the Engineer and all deficiencies shall be corrected before the close of that work shift, unless otherwise specified. 710- 4 Method of Measurement: SWZ system will be measured on a lump sum basis for a fully functional complete in place system. TDC location, SWZ CMB assembly, traffic monitoring assembly, and VSLS assembly will be measured by the each- day for each 24- hour day that the SWZ is in place and functional for the in- use condition, with no loss of communications or power failures for 98 percent of the construction work day. Measurement for payment of the TDC location, SWZ CMB assembly, traffic monitoring assembl y, and VSLS assembly will begin on the day they are installed in place and fully functional. When the elements are not needed, they shall be removed or covered and will not be measured unless they are required to stay on site in anticipation of future use or emergency use as determined by the Engineer. Should devices be required on site for these purposes, they will be measured and paid for at the contract unit prices. During non- working periods such as holidays and weekends, the elements in place will be m easured for payment. During these non- working periods the contractor shall conduct a minimum of one check per day to verify that the elements are in place and in satisfactory condition. Measurement for payment of static traffic control devices as shown on the TCP that are used in conjunction with the SWZ field equipment shall be paid for with their respective bid item. Elements of work which are lost, stolen, destroyed, or are deemed unacceptable by the Engineer, while in use on a project shall be replaced by the contractor at no additional cost to the Department . 710- 5 Basis of Payment: SMZ system, measured as provided above, will be paid for at the contract lump sum price, which price shall be full compensation for the work, complete in place, as specified herein and shown on the plans, including all materials, equipment, and labor necessary to facilitate the TABLE OF CONTENTS INDEX 824 SWZ system mobilization; obtain the Engineer’s approval of required submittal documentation; provide SWZ system software, the SWZ client interface and user training, initial system configurations and associated acceptance testing, SWZ software user access privileges, alert messages, and SWZ system data reports; provide system and equipment operations and maintenance, deployment location changes, and sup port services as needed to maintain a fully functional and operational SWZ system for the duration of the project; and removal of all SWZ equipment. Documentation of all lessons learned as a result of the SWZ installation, deployment, and removal shallal so be included in the lump sum payment. The accepted quantities of TDC locations, SWZ CMB assemblies, traffic monitoring camera assemblies, and VSLS assemblies measured as provided above, will be paid for at the contract unit price each for the type of location or assembly designated in the bidding schedule, fully deployed and in operation in the SWZ area, which price shall be full compensation for the work described and specified herein and on the plans, and all other components necessary to provide a com plete functional assembly for monitoring the SWZ area traffic conditions and controlling the SWZ operations. Eighty percent of the contract lump sum price for the SWZ system will be paid upon satisfactory installation of a fully functional system. Twenty percent of the contract lump sum price for the SWZ system will be paid upon final removal. No payment will be made for relocation of work elements and SWZ system configuration changes. No payment will be made for setting up or relocating the necessary elements of work and associated protective devices that are moved concurrently with the advancing operation or removal at the end of a shift. No payment will be made for the elements of work listed herein for non-working periods resulting from a suspension of w ork that, in the opinion of the Engineer, is due to the fault of the contractor. In any case, the contractor shall continue to be responsible for maintaining all SWZ system components in proper functioning condition at all times. SECTION 71 1-729 BLANK: TABLE OF CONTENTS INDEX 825 SECTION 730 GENERAL REQUIREMENTS FOR TRAFFIC SIGNAL AND HIGHWAY LIGHTING SYSTEMS : 730- 1 Description: It is the purpose of this section to provide general information necessary for completion of the work on traffic signal and highway lighting systems in accordance with the details shown on the project plans and requirements of these specifications. All electrical systems and appurtenances shall be complete, functional and in operating condition at the time of acceptance. 730- 2 Definitions: The words defined in the following subsection shall for the purpose of these specifications have the meani ngs ascribed to them pertaining to signals and lighting. 730- 2.01 Actuation: The operation of any type of controller initiated by a detector. 730- 2.02 Back Plate: A thin metal strip extending outward parallel to the signal face on all sides of a signal housing to provide suitable background for the signal indications. 730- 2.03 Controller: That part of the controller assembly which performs the basic timing and logic functions for the operation of the traffic signal. 730- 2.04 Controller Assembly: The complete assembly for controlling the operation of a traffic signal, consisting of a controller unit, and all auxiliary and external equipment housed in a weatherproof cabinet. 730- 2.05 Cycle: A complete sequence of signal indications. 730- 2.06 Detector: A device for indicating the passage or presence of vehicles or pedestrians. TABLE OF CONTENTS INDEX 826
A detector capable of sensing the passage or presence of a vehicle by a change in the inductance characteristics of the wire loop.
A detector capable of being actuated by the magnetic disturbance caused by the passage or presence of a vehicle.
A detector, for pedestrians, usually of the button type. 730- 2.07 Flasher: A device used to open and close signal circuits at a repetitive rate. 730- 2.08 Flashing Feature: This feature, when operated, discontinues normal signal operati on and causes a predetermined combination of flashing signal lights. 730- 2.09 Interval: The part or parts of the signal cycle during which signal indications do not change. 730- 2.10 Luminaire: The assembly which houses the light source and controls the light emitted from the light source. Luminaires consist of a housing, lamp socket, reflector, and glass globe or refractor when specified. 730- 2.11 Manual Operation: The operation of a signal controller unit by means of a hand- operated switch. 730- 2.12 Mounting Assembly: The framework and hardware required to mount the signal face(s) and pedestrian signal(s) to the pole. 730- 2.13 Pedestrian Signal: A traffic control signal for the exclusive purpose of directing pedestrian traffic at signalized locations. TABLE OF CONTENTS INDEX 827
730-2.14Pretimed Controller Assembly:
A controller assembly for operating traffic signals in accordance with a predetermined fixed- time cycle. 730- 2.15 Red Clearance Interval: A clearance interval which follows the yellow change interval during which both the terminating phase and the next right -of-way phase display red. 730- 2.16 Signal Face: An assembly controlling traffic in a single direction and consisting of one or more signal sections. Circular and arrow indications may be included in a signal assembly. The signal face assembly shall include the backplate and visors. 730- 2.17 Signal Indication: The illumination of a signal section or other device, or of a combination of sections or other devices at the same time. 730- 2.18 Signal Section: A complete u nit for providing a signal indication consisting of a housing, lens, reflector, lamp receptacle and lamp. 730- 2.19 Traffic Phase: A part of the time cycle allotted to any traffic movement or combination of movements receiving the right -of-way during one or more intervals. 730- 2.20 Traffic -Actuated Controller Assembly: A controller assembly for operating traffic signals in accordance with the varying demands of traffic as registered with the controller unit by detectors. 730- 2.21 Vehicle: Any motor vehicle normally licensed for highway use. 730- 2.22 Yellow Change Interval: The first interval following the green right -of-way interval in which the signal indication for the phase is yellow. TABLE OF CONTENTS INDEX 828 730- 3 Regulations and Codes: All electrical equipment shall conform to the current standards of National Electrical Manufacturers Association (NEMA), National Electric Safety Code (NESC), Underwriters' Laboratory Inc. (UL), or the Electronic Industries Association (EIA), when applicable. All materials and workmanship shall conform to the requirements of the National Electric Code (NEC), Illumination Engineers Society (IES), the American Society for Testing and Materials (ASTM), American Association of State Highway and Tr ansportation Officials (AASHTO), requirements of the plans, these specifications, and the Special Provisions, and to any other codes, standards, or ordinances which may apply. Whenever reference is made to any of the standards mentioned, the reference shall be construed to mean the code, ordinance, or standard that is in effect at the time of the bid advertisement. 730- 4 Equipment List and Drawings: The contractor shall note that approval by the Engineer is required before ordering or installing any material that is to be used on the project. The contractor shall submit a complete project material submittal for approval to the Engineer electronically by the pre- construction conference. I n addition to the electronic submission, the Engineer may request up to three hard copies. The project material submittal shall state all relevant information regarding materials and equipment to allow the Depar tment to procure exact replacements of any or all items on the project. To be acceptable, the material submittal shall be complete and contain all items supplied on the project by the contractor. The Department reserves the right to reject an incomplete or unclear material submittal. The materials on the submittal shall be identified by the contract project number, bid item numbers, catalog part numbers, catalog cuts, shop drawings for signal and lighting equipment, trade names, schedules for other pertinent information. The materials from any catalog cuts shall be clearly indicated by the contractor. Any material designations used in the contract documents shall be so noted on the materials list. If requested by the Engineer, the contractor shall submi t manufacturer shop drawings for review and approval and shall furnish Certificates of Compliance conforming to the requirements of Subsection 106.05 of the specifications. There shall be no substitutions for any of the materials on the list without prior written approval by the Engineer. Changes to the approved materials list shall be submitted in writing to the Engineer. If requested by the Engineer, the contractor shall submit samples of the proposed materials for inspections, testing, and approval by the Department. The Department will not be liable for any electrical materials procured or any labor performed prior to approval. TABLE OF CONTENTS INDEX 829 When the plans include lighting, the contractor shall submit photometric data sheets indicating the IES distribution classification for each type of luminaire submitted for approval to the Engineer electronically. In addition to the electronic submission, the Engineer may request up to three hard copies. In addition, the contractor shall submit data from the manufacturer detailing lamp socket positions in relation to lamps and optical systems furnished for each IES distribution type specified. If required by the Special Provisions, the contractor shall provide computer printout grids of both luminance and il luminance values for the spacing, height, roadway width, and type of luminaire submitted. The contractor shall provide complete wiring diagrams for controller assemblies and auxiliary controller cabinets at the time of delivery for testing. A mylar original and four sets of prints shall be provided with each controller assembly. The wiring diagram shall illustrate all circuits and components in detail. All components shall be identified by name or number so as to be clearly noted in the drawings. 730- 5 Warranties & Guaranties: Manufacturer's warranties and guaranties, furnished for materials and equipment used in the work, shall be delivered to the Engineer prior to acceptance of the project. Warranties and guaranties shall conform to the requirements of Subsection 106.13 of the specifications. 730- 6 Locations of Utilities: The locations of utilities shown on the project plans are approximate. All involved utilities may not be shown on the plans. In addition to the requirements of Subsection 107.15 of th e specifications, the contractor's attention is directed to the requirements of A.R.S. 40 -360.21 through .29 requiring all parties excavating in public streets, alleys or utility easements to first secure the locations of all underground facilities in the vicinity of the excavation. The contractor shall contact the Blue Stake Center at least two working days prior to commencing excavation, for information relative to the location of buried utilities within the project limits. 730- 7 Installation of Decals: The contractor shall furnish and install a maintenance unit number decal approximately 42 inches above the base- plate displayed on the traffic- side of the device at a 45 degree angle to the direction of travel, or as approved by the Engineer. The devices hall not be adjusted to make them 45 degrees. Each electrical cabinet and lighting pole, or other items as specified on the plans or as directed by the Engineer, shall receive a feature number decal. Feature number to be installed on each specific electri cal device shall be as shown on the pole schedule in the plans. TABLE OF CONTENTS INDEX