Detection Zone Programming Sample Clauses

Detection Zone Programming. Place the detection zones by means of a graphical interface using the radar return of vehicles travelling the roadway. On the monitor, superimpose the image of the detection zones on the lanes of traffic. Create the detection zones by using the mouse or pointing device to draw detection zones on the monitor. The detection zones must be capable of being sized, shaped and overlapped to provide optimal road coverage and detection. Save the detector configurations on disk, to download detector configurations to the RDS processor unit, and to retrieve the detector configuration that is currently running in the RDS processor unit. Use the mouse or pointing device to edit previously defined detector configurations so as to fine-tune the detection zone placement size and shape. Once a detection configuration is created, the system must provide a graphic display of the new configuration on a field monitor. If a vehicle occupies a detection zone, the detection zone on the live radar must indicate the presence of a vehicle, thereby verifying proper operation of the detection system.
View SourceView Similar (3)
Detection Zone Programming. Placement of detection zones must be by means of a graphical interface using the video image of the roadway. The monitor must show images of the detection zones superimposed on the video image of traffic while the VIVDS processor is running. The detection zones must be created by using the mouse or keypad to draw detection zones on the monitor. The detection zones must be capable of being sized, shaped and overlapped to provide optimal road coverage and detection. It must be possible to upload detector configurations to the VIVDS processor unit and to retrieve the detector configuration that is currently running in the VIVDS processor unit. The mouse or keypad must be used to edit previously defined detector configurations so as to fine tune the detection zone placement size and shape. Once a detection configuration has been created, the system must provide a graphic display of the new configuration on its monitor. While this fine-tuning is being done, the detection must continue to operate from the detector configuration that is currently called. When a vehicle occupies a detection zone, the detection zone on the live video must indicate the presence of a vehicle, thereby verifying proper operation of the detection system. With the absence of video, the card must have an LED that will indicate proper operation of the detection zones. Provide detection zones that are sensitive to the direction of vehicle travel. The direction to be detected by each detection zone must be user programmable. The vehicle detection zone should not activate if a vehicle traveling any direction other than the one specified for detection occupies the detection zone. Cross-street and wrong way traffic should not cause a detection.
View Source

Related to Detection Zone Programming

  • Programming Processor is not responsible for programming or reprogramming of fuel dispensers.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: ▇▇▇▇://▇▇▇.▇▇▇▇▇▇-▇▇▇▇▇.▇▇▇/508.htm.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, and ▇▇- ▇▇▇-▇▇▇, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.