Published by department of transportation
-3.34 TEMPORARY FLASHING BEACON SYSTEMS
Download 6.74 Mb.
|
- Navigate this page:
- 12-3.34D Payment Not Used 12-3.35 AUTOMATED WORK ZONE INFORMATION SYSTEMS 12-3.35A General
- 12-3.35A(3) Submittals Reserved 12-3.35A(4) Quality Assurance
- 12-3.35B(2) General System Function Requirements
- 12-3.35B(3) Motorist Information Message Requirements
- 12-3.35B(4) System Communication Requirements
- 12-3.35B(5) Traffic Data Acquisition Requirements
- 12-3.35B(6) User Interface
12-3.34 TEMPORARY FLASHING BEACON SYSTEMS12-3.34A GeneralSection 12-3.34 includes specifications for installing temporary flashing beacon systems. A temporary flashing beacon system must comply with section 87. 12-3.34B Materials12-3.34B(1) GeneralReserved 12-3.34B(2) GeneratorsA generator system to power a temporary flashing beacon system must comply with section 12-3.33B(2). 12-3.34B(3) Sign PanelsThe sign panels installed on a temporary flashing beacon system must be stationary-mounted construction area signs complying with section 12-3.11. 12-3.34C ConstructionRelocate each system during the progress of the work such that the systems are located at the ends of the pavement at the end of each work shift. Use commercial power from an existing utility company or generator system to provide power to the temporary flashing beacon system. Do not use power from a private party to provide power to a temporary flashing beacon system. Commercial power must be 120 V(ac) or 120/240 V(ac). Make arrangements with the utility company for providing service. Protect the power source in a locked enclosure. Provide keys to all locks to the Engineer. 12-3.34D PaymentNot Used 12-3.35 AUTOMATED WORK ZONE INFORMATION SYSTEMS12-3.35A General12-3.35A(1) SummarySection 12-3.35 includes specifications for installing automated work zone information systems. 12-3.35A(2) DefinitionsReserved 12-3.35A(3) SubmittalsReserved 12-3.35A(4) Quality AssuranceAssign an on-site system coordinator. The coordinator must be available locally to service, maintain, and relocate system components as necessary. The coordinator must be accessible 24–7 while the system is deployed. If the system fails to perform as specified, perform any necessary remedial work and replace any failed components within 24 hours of notification of a system or component failure. 12-3.35B Materials12-3.35B(1) GeneralThe AWIS must be a proven system that has been successfully deployed and operated in actual work zones or congested areas. The system must acquire traffic data throughout the work zone and automatically display predetermined information to motorists without operator intervention after system initialization. Real-time information must be displayed to motorists using a PCMS. The sign must comply with section 12-3.32. The system must be controlled either locally or remotely by a dedicated controller or computer. Authorized users must be able to both locally and remotely override motorist information messages. Traffic sensors must not require adjustments after the initial deployment. 12-3.35B(2) General System Function RequirementsThe general system functions of the AWIS must be capable of: 1. Preventing any unauthorized users or systems from gaining access to the PCMSs through an industry authentication and encryption standard level of security. 2. Providing current operational status locally and remotely. Operational status must include current traffic data and messages, communications system, and power status. 3. Delivering notifications either by telephone, voice, or text messages to alert support staff of trouble conditions. 4. Generating trouble alerts for conditions such as (1) low roadside equipment power or voltage, (2) system communications failure, (3) low speed traffic detected, and (4) excessive delay detected. 5. Adjusting the thresholds of reduced speed and congestion-induced delay at which the system initiates a trouble alert. 6. Allowing programming of the hours during which the trouble condition alerting subsystem initiates notification to authorized users. 7. Measuring periodically and automatically the power levels of all equipment. Alert support staff, locally and remotely via a telephone message, in time to provide supplemental power before the system ceases to operate. 8. Displaying preprogrammed messages based on the time of day and day of week.
1. Displaying predetermined speed, delay, diversion, and closure messages to motorists when user-adjustable thresholds are exceeded. 2. Updating its speed and delay advisory messages at least once per minute. The actual message updates must be consistent with traffic conditions. 3. Selecting messages for each PCMS independently, based on the traffic conditions downstream of the sign. 4. Recording motorist information messages in a comma-separated values file with time and date stamps, including message overrides with user ID. 5. Displaying default messages when traffic conditions, system algorithms, and user parameters do not dictate that an advisory message should be displayed. 6. Displaying separate, independent, default messages on each PCMS. 7. Analyzing traffic parameters in work zones in which there are multiple speed limits. The following parameters for the selection and presentation of information messages must be adjustable by the user: 1. Message update frequency 2. Minimum delay necessary to trigger a delay advisory message 3. Persistence of delay before a delay message is displayed 4. Level of delay required to trigger a diversion message 5. Change in delay needed to cause a delay advisory message update 6. Change in downstream speed at which a speed advisory message update occurs
1. Operate independently of the public cellular phone system for receiving data to ensure reliable communications 2. Communicate independent of the line of sight or distance 3. Incorporate an error detection and correction mechanism to ensure the integrity of all traffic condition data and motorist information messages 4. Configure automatically during system initialization
The system must (1) archive the data with time and date stamps and (2) aggregate the data in operator-definable time increments, accessible 24–7 to the Engineer in a comma-separated values file. 12-3.35B(6) User InterfaceThe system must have a user interface to control the AWIS PCMS communications. The interface must be (1) software compatible with a Windows environment or (2) a web service accessed by a web browser. Provide any software on a CD or other Engineer-authorized data-storage device for installation at the Department's Transportation Management Center. The user interface must, at a minimum, provide the user with a list of AWIS PCMSs in the field, location information for each AWIS PCMS, and a real-time on-board display of the message in the field. Control options must, at a minimum, provide the user the ability to change the on-board messages and flash rate.
12-3.35C ConstructionObtain authorization for the message content and the threshold used for triggering the message before displaying any message on a PCMS. Provide complete setup and support for the AWIS PCMS communications. 12-3.35D PaymentNot Used Directory: esc esc -> Biblical Eschatology Presentation by: D. Paul Beck May 4, 2016 Ground Rules esc -> Mikael Håfstrӧm Screenplay by Miles Chapman and Arnell Jesko esc -> Escort affinity Program for Audi Club Members esc -> Preliminary entry form pistol esc -> Application form esc -> Request from Asian and Pacific Training Centre for Information and esc -> Constitution of the engineering student council university of maryland esc -> Subdisciplines of Earth Science Geology; study of the earth Download 6.74 Mb. Share with your friends:
|