RFQ813 - Attachment 1 - Traffic Video Detection System and Radar Detection Systems.docx
DOCX document 88 KB Posted
- Attached to
- Traffic Signal Detection System
- Solicitation number
- 813
- Issued by
- Idaho
About this file
RFQ 813 Summary: Traffic Video Detection System and Radar Detection Systems
This is an attachment to a Request for Quotation (RFQ) issued by the Idaho Transportation Department (ITD) for the purchase and delivery of traffic detection systems. The solicitation seeks two distinct systems: a SmartCity ITS Artificial Intelligence Video Detection System and an Econolite EVO Radar Detection System. The video detection system consists of two Currux Vision Standard GPU Servers with SmartCity ITS Software, analog camera adapters, SDLC and NTCIP modules, two Axis M4318-PLVE panoramic traffic monitoring cameras, power over Ethernet injectors, and all necessary cables, hardware, and mounting brackets. The radar detection system includes one EVO Radar Hub, Traffic Manager Software, two EVO Radar Sensor Units, built-in power supplies, interface cables, and installation hardware. Delivery is desired within sixty calendar days after Award and Ratification Order (ARO), FOB Destination with freight prepaid, to ITD District 3 in Garden City, Idaho. Delivery must occur Monday through Friday, 8:00 am to 4:00 pm local time, excluding state holidays. Vendors must submit quotes electronically via IPRO Powered by LUMA or email by the deadline established in the system. Award will be made to the lowest-cost responsive and responsible vendor(s) by line item, with the state reserving the right to make multiple awards or not to award if not in the state's best interest.
Vendors must be authorized distributors with written manufacturer agreements and must provide all required submittals including the price sheet, signature page, and documentation demonstrating compliance with specifications. All equipment must be warranted for a minimum of one year parts and labor from the acceptance date, with warranty including all parts, labor, and freight, and must be delivered within thirty calendar days of ITD's notice. Contractors must submit itemized invoices within thirty days of acceptance and will be paid in accordance with Idaho Code 67-2302. The file includes detailed technical specifications for both systems, including artificial intelligence GPU requirements, application software capabilities, panoramic camera specifications, radar hub and sensor specifications, and comprehensive environmental operating conditions. Vendors must provide manuals, online user guides, and ongoing software support including free application and AI model updates during the warranty period or active maintenance contract. The contact for this solicitation is Kirk Anderson, Contract Officer, at Kirk.anderson@itd.idaho.idaho.gov, and vendors are prohibited from communicating with ITD staff other than the RFQ Lead from the issue date until contract award or RFQ cancellation.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Exhibit 1 - Deliverable Acceptance Form.docx | DOCX document | |
| Insurance Requirements 2023.docx | DOCX document | |
| RFQ813 - Attachment 2 - Price Sheet - Traffic Control Detection System.xlsx | XLSX spreadsheet | |
| RFQ813 - Attachment 3 - Signature Page.docx | DOCX document | |
| Exhibit 2 - Contract Discrepancy Notice.docx | DOCX document | |
| State of Idaho Contract Terms and Conditions_2024.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFQ 813
ATTACHMENT 1 – REQUIREMENTS AND SPECIFICATIONS
TRAFFIC VIDEO AND RADAR DETECTION SYSTEMS
GENERAL INFORMATION
PURPOSE
The Idaho Transportation Department (ITD) is requesting quotes from qualified vendors for the purchase and delivery of a traffic video detection system and a radar detection system (Systems) in accordance with the specifications provided below.
SOLICITATION CONTACT`
The contact for this RFQ is:
Name: Kirk Anderson, Contract Officer Email: Kirk.anderson@itd.idaho.idaho.gov (preferred method of contact)
RESTRICTIONS ON COMMUNICATIONS
From the issue date of this RFQ, until a contract/purchase order is awarded or the RFQ is cancelled, vendors and their representatives are prohibited from communications (written or verbal) regarding this RFQ with the ITD staff, other than the ITD RFQ Lead. Any communications (written or verbal) with ITD staff other than the RFQ Lead may result in the submitting vendor being found Non-Responsible and Non-Responsive.
REQUIREMENTS AND SPECIFICATIONS
See Sections 1 and 2.
QUOTE
Your Quote may be submitted electronically via IPRO Powered by LUMA or email (see below for additional details). ITD will not be accepting manual submissions for this solicitation. Your Quote must include the Required Submittals listed below and be received prior to the deadline established in IPRO Powered by LUMA.
Electronic Submission:
IPRO – Enter your pricing in IPRO powered by LUMA (https://purchasing.idaho.gov/information-for-vendors/) and upload all Required Submittals.
Email:
Send an email to the Solicitation Contact (see Section 2) and attach all Required Submittals.
REQUIRED SUBMITTALS:
Attachment 2 – Price Sheet Attachment 3 – Signature Page Documentation, which demonstrates, to ITD’s satisfaction, that the offered item meets the requirements of the solicitation. Failure to provide satisfactory documentation may eliminate the Vendor from further consideration.
(See Section 1 – Requirements and Specifications)
AWARD
More than one (1) award may be issued for this RFQ. Award will be made to the responsive responsible vendor(s) with the lowest cost by Line Item.
The State reserves the right not to evaluate or make an award in the best interest of the State. The State also reserves the right to make multiple awards per manufacturer, in accordance with Section 67-9211 of Idaho Code in the best interest of the State.
Though it is not mandatory to submit your Quotation electronically via Luma powered by IPRO, all vendors participating in a solicitation issued through Luma powered by IPRO must establish an account in the Luma powered by IPRO system (even if submitting a quote outside of Luma powered by IPRO). It is free to establish an account and only takes a few minutes of your time.
SECTION 1: REQUIREMENTS
1. BraND NAME The brand names specified in this solicitation are intended to be descriptive, but not restrictive; indicative of the quality and characteristics of items that meet the minimum requirements. Vendors offering an “equal” must include documentation, which demonstrates, to ITD’s satisfaction, that the offered item(s) meets the requirement of the solicitation. In the event documentation is not satisfactory, ITD reserves the right to seek clarification from the Vendor. Failure to provide satisfactory documentation or a clarifying response to ITD may eliminate the Vendor from further consideration.
1. AUTHORIZED DISTRIBUTOR
Bidders must be an authorized distributor for the equipment being offered and are responsible for all warranty requirements. An authorized distributor must be defined as a company or organization that has a written agreement with the manufacturer to sell or service its products. Quotes from Contractors who are not an authorized distributor will not be considered.
ITD reserves the right to request authorized distributor documentation from the submitting vendors. Failure to provide submitting documentation as requested will result in a non-responsive quote.
WARRANTY
All Systems must be warranted for a minimum period of one (1) year parts and labor commencing from the effective date of acceptance by the ITD. During the warranty period, parts that are found to be defective will be repaired or replaced (at the option of the manufacturer without charge). Warranty must include all parts and freight to replace a defective warranted item. All warranty parts must be delivered to ITD FOB Destination, freight prepaid and allowed within thirty (30) calendar days after receipt of notice from ITD.
Awarded vendor is responsible for all warranty requirements. No third-party warranties will be allowed.
ACCEPTANCE
Documenting Acceptance - ITD’s Contract Monitor will be responsible for documenting Acceptance, in writing, using Exhibit 1 - Deliverable Acceptance Form. This document will be emailed to the Contractor’s Contract Manager as proof of Acceptance and approval to proceed with the invoicing procedures and required in Section 10, Invoicing.
Documenting Non-Compliance - ITD’s Contract Monitor will be responsible for documenting non-compliance, in writing, using Exhibit 2 - Contract Discrepancy Notice. This document will be emailed to the Contractor’s Contract Manager, providing details for each discrepancy that require corrective action. Invoicing must not occur until non-compliance has been corrected.
Correcting Non-Compliance - After receipt of the Contract Discrepancy Notice, the Contractor’s Contract Manager must respond, using the document, explaining how and when each discrepancy will be corrected. All discrepancies must be corrected and brought back into compliance with the Contract within thirty (30) calendar days after receipt of the notice from ITD. If the Contractor does not correct the discrepancies within this timeframe, ITD reserves the right to take further remedial action as detailed in Section 5, Remedial Action.
REMEDIAL ACTION
In addition to any remedies available to the State under law or equity, the State may it its sole discretion require one (1) or more of the following remedial actions if any of the service(s) does not conform to the Contract requirements: 1) require the Contractor to take corrective action to ensure that performance conforms to the Contract requirements, 2) require the Contractor to subcontract all or part of the Contract at no additional cost to the State, 3) withhold payment or require payment of actual damages caused by the Discrepancy, 4) terminate the Contract pursuant to Section 6, Termination of Contract, in addition to any remedies imposed by the State.
If ITD must perform or hire a separate contractor to perform any of the Contract’s requirements, which is the responsibility of the Contractor under the terms of the Contract, ITD may withhold the actual cost to ITD from the Contractor’s payment(s).
TERMINATION AND CURE
See Idaho Contract Terms and Conditions on the Attachments tab in IPRO powered by LUMA.
DELIVERIES
Delivery is desired within sixty (60) calendar days after ARO, FOB Destination, freight prepaid and allowed. ITD reserves the right to accept delivery dates outside of the desired delivery date if in the best interest of the State of Idaho.
Delivery must be made Monday through Friday, 8:00 am to 4:00 pm local time excluding state of Idaho recognized holidays (https://www.idaho.gov/government/holidays.html), unless otherwise approved in writing by ITD.
Delivery Location:
ITD District 3, 8150 W Chinden Blvd. Garden City, ID 83714 system Maintenance Ongoing software support by the supplier must include updates of the application software and AI models. These updates must be provided free of charge during the warranty period or while under an active maintenance contract.
The supplier must maintain an adequate inventory of parts to support maintenance and repair of all systems under warranty or extended warranty agreement.
MANUALS
Manuals must be provided at the time of delivery. The manufacturer must provide a web address for an online user guide or an electronic copy of the user guide within the client software.
Manuals must cover all systems to include drawings, schematics, applicable technical information, and component parts and installation guide.
INVOICING
The Contractor must submit its invoice within thirty (30) calendar days of acceptance to the billing contact identified on the Contract. Invoices submitted prior to acceptance, or without the required information listed below, will be returned to the Contractor for correction and resubmission. The following information must be included with each invoice:
Purchase Order Name and Number Invoice Number and Date Contractor Contact Information Itemization of Property delivered and accepted – description, quantity, unit of measure, unit price, and total invoice amount.
Invoices must be submitted electronically to:
D3AP@ITD.IDAHO.GOV
PAYMENT
Payment will be made in accordance with Idaho Code 67-2302 after receipt of the Contractor's itemized invoice and is accepted by ITD. Total payments under this Contract must not exceed the Total Price provided on Attachment 2 - Price Sheet unless otherwise modified in an amendment to this contract.
WARRANTY
The Equipment, including all accessories, must be warranted against all defects in material and workmanship by either the manufacturer or the Contractor for a period of no less than one (1) year.
Warranty must include all travel, parts, labor, and freight to replace a defective warranted item. All warranty work must be completed within thirty (30) calendar days after receipt of notice from ITD.
If any warranty work is to be performed, the Contractor may elect to authorize a dealer of its choice or authorize ITD to perform the necessary repairs in accordance with the manufacturer’s standards. If the Contractor authorizes ITD to perform any warranty work, it is the responsibility of the Contractor to guarantee that the work is completed in accordance with the manufacturer’s standards at the expense of the Contractor. Completion of warranty repairs by ITD which are authorized by the Contractor will not adversely affect the warranty.
Documentation - Warranty documentation and an acceptance letter agreeing to the special warranty provisions of the Equipment outlined above must be submitted with bid response.
INSURANCE
See Attachment 6 – Insurance on the Attachment Tab of RFQ813 IPRO powered by LUMA.
MODEL & ASSEMBLY
The Equipment must be the latest model of the manufacturer's current standard production, as offered to commercial trade. Though they are not specifically covered herein, all parts necessary to provide complete and functional Equipment must be furnished. All parts must conform in design, strength, quality of materials, and workmanship to current engineering practices and accepted standards of the industry. All parts must be the manufacturer’s standard unless otherwise specified in this RFQ.
SECTION 2: SPECIFICATIONS
ITEM 1 – VIDEO DETECTION SYSTEM
1. Smartcity ITS Artificial Intelligence System REQUIREMENTS The SmartCity ITS Artificial Intelligence System or equal, at a minimum must consist of the following in order to be considered for award:
Utilize video input from any IP, CCTV and analogue camera to collect video image data for the Artificial Intelligence GPU for purposes of detecting and classifying vehicles, pedestrians and bicyclists and generating traffic data and real time notifications with photo evidence;
Utilize and demonstrate tracking-based algorithms (in lieu of trip-line) to provide real-time vehicle, pedestrian and bicyclist detection outputs within two-hundred (200) ms of vehicle arrival);
Be able to detect either approaching or departing vehicles in multiple traffic lanes simultaneously.
Be able to issue detection calls based on vehicle class (car, light truck, heavy truck, bus, motorcycle, bicyclist, pedestrian);
Be able to communicate detection calls to the traffic controller using NTCIP and SDLC standard;
Provide flexible detection placement anywhere within the field of view of the camera. A single detection template must be able to replace one or more conventional detector loops;
Operate at a level of performance comparable to properly operating inductive loops, excluding issues of occlusion due to limitations imposed by camera placement;
Trigger a state of “all call” to the controller in the event of an equipment failure or system malfunction and;
Provided both presence and pulse detection for each detection template. In presence detection, the detection zone is active as long as a vehicle or pedestrian occupies the zone. In pulse detection, the detection zone provides a momentary, on/off detection that does not remain active, even if the vehicle or pedestrian stays within the zone.
1. ARTIFICIAL INTELLIGENCE GPU
The Artificial Intelligence GPU at a minimum must consist of the following in order to be considered for award:
Save object detection templates plans locally to support operation with or without monitoring equipment (monitor, laptop, remote connection) connected;
Be rack or shelf mountable, measuring no more than six (6) in wide, seven (7) in deep, and four (4) tall;
Be designed to operate reliably in the adverse environment found in the typical roadside traffic cabinet;
Operate at one-hundred and twenty to two-hundred and forty (120-240) VAC, requiring thirty (30) W or less power;
Be able to communicate with traffic controllers and web relays using solely IP network connection;
Not require shielding from other electronic devices, such as power supplies and communication equipment;
Must feature LAN and USB interface ports on the front surface of the unit.
Be able to interface with analog cameras via built-in analog camera adapter and BNC connector (four (4) channel) and;
Be able to communicate via SDLC with traffic controllers.
The Artificial Intelligence GPU must be designed to operate reliably in an operating temperature ranging from negative thirty-four to positive seventy-four degrees (-34°C to +74°)C at zero (0%) percent to ninety-five percent (95%) percent relative humidity, and have vibration and shock parameters of at least five (5) G RMS ten (10) to five-hundred (500) Hz and fifty (50) G, half sine eleven (11) ms, respectively.
The Artificial Intelligence GPU must comply with part 15 of the FCC Rules.
APPLICATION SOFTWARE
The Application Software at a minimum must consist of the following in order to be considered for award:
Must support the creation and modification of at least thirty (30) object detection templates within the graphical user interface;
Show images of the object detection templates superimposed on the video image of traffic;
Support the assignment of a Phase and Detector number to each road and crosswalk lane. These assignments can be modified at any time through the software;
Support direction of travel assignment within detection template;
Place a detection box around all detected and tracked objects (cars, pedestrians etc.);
Calculate and display speed for each detected object;
Calculate wait times for all detected objects when stopped;
Issue real-time notifications when one of the events of interest occurs (e.g. stopped lane, wrong direction, slow traffic);
Be able to send real-time notifications by means of email, text and in-browser notifications and;
Maintain a database of current and historical traffic data and allow for the user to run reports against this data to include traffic counts, turn movements, average speed, eight-fifth (85th) percentile speed, classification, wait times and arrivals on green at a minimum.
System components comply with the environmental requirements detailed in the NEMA TS 2 standard https://www.nema.org/docs/default-source/standards-document-library/nema-ts-2-2021-contents-and-scopeb71294ae-eb9a-45e2-a501-e5c0672dbd6b.pdf?sfvrsn=ef98a362_3.
PANORAMIC TRAFFIC MONITORING CAMERA
The Panoramic Traffic Monitoring Camera at a minimum must consist of the following in order to be considered for award:
Provide a minimum resolution of twelve (12) MP for panoramic imaging and a 360° field of view;
Include built-in IR illumination with individually controllable IR LEDs;
Support automatic day/night mode with an IR-cut filter;
Feature a one-half point three (1/2.3”) progressive scan RGB CMOS sensor;
Utilize a fixed focal length of one point two (1.2) mm, F2.2, providing a horizontal and vertical field of view of one hundred eighty-two (182)° degrees;
Maintain minimum illumination levels of:
Color mode: zero point one nine (0.19) lux at fifty (50) IRE, F2.2;
B/W mode: zero point zero four (0.04) lux at fifty (50) IRE, F2.2;
zero (0) lux with IR illumination activated;
Support a shutter speed range of one over eight thousand one hundred (1/8100) to zero point five (0.5);
Allow digital roll adjustment of plus or minus one hundred eighty (±180)° for flexible installation;
Support video compression formats including:
H.264 (Baseline, Main, and High Profile);
H.265 (Main Profile);
Motion JPEG (MJPEG);
Provide multiple resolution modes, including:
Overview: Up to two thousand nine hundred ninety-two by two thousand nine hundred ninety-two (2992x2992);
Panorama: Up to three thousand eight hundred forty by two thousand one hundred sixty (3840x2160);
Quad view: Up to three thousand five hundred eighty-four by two thousand six hundred eighty-eight (3584x2688);
Corridor mode: Up to two thousand five hundred sixty by one thousand nine hundred twenty (2560x1920);
Operate at up to thirty (30) fps at maximum resolution without WDR and up to twenty-five (25) fps with WDR enabled;
Feature Forensic WDR (up to one hundred twenty (120) dB dynamic range) for improved visibility in high-contrast scenes;
Provide two-dimensional (2D) and three-dimensional (3D) noise reduction for enhanced image quality in low-light conditions;
Support IPv4/IPv6, HTTPS, and standard network protocols for remote management;
Be compliant with ONVIF Profile G, S, and T for seamless integration with third-party systems;
Support open API for software integration, including metadata streaming and remote management;
Support Power over Ethernet (PoE) IEEE 802.3af at Type one (1), Class three (3), with a typical power consumption of six point four (6.4) W and a maximum of twelve point nine five (12.95) W;
Support microSD/microSDHC/microSDXC card storage and network-attached storage (NAS) recording;
Include built-in installation aids such as a pixel counter and level grid;
Be IP66-rated for water and dust resistance and IK10-rated for impact protection;
Operate within a temperature range of negative forty (−40)°C to fifty (50)°C (negative forty (−40)°F to one hundred twenty-two (122)°F and ten (10)–one hundred (100)% humidity (condensing);
Comply with NEMA TS two (2), ISO four eight nine two-point two (4892-2), and IEC six thousand sixty-eight-point two (60068-2) environmental standards;
Be firmware-upgradable with regular software updates.
SYSTEM COMPONENTS
Two (2) Currux Vision Standard GPU Servers:
Currux SmartCity ITS Software;
Analog camera adapter with four (4) channels;
SDLC Module;
NTCIP Module.
Two (2) Panoramic Traffic Monitoring Cameras:
AXIS M4318-PLVE Panoramic Camera;
Power over Ethernet (PoE) injector;
All necessary cable, hardware, fittings, and mounting brackets for complete installation and;
5.3 Field turn-on assistance.
ITEM 2 – RADAR DETECTION SYSTEM
1. eCONOLITE evo RADAR DETECTION SYSTEM REQUIREMENTS The Econolite EVO Radar Detection System or equal at a minimum must consist of the following in order to be considered for award:
Utilize forward-fire FMCW MIMO radar technology to provide high-accuracy vehicle, pedestrian, and bicycle detection;
Provide stop bar, advance, departure, pedestrian, and bicycle detection using a minimal number of sensors;
Detect and track up to five hundred twelve (512) objects simultaneously;
Provide a detection range of up to nine hundred (900) feet with a one hundred ten (110)-degree horizontal field of view;
Support departure detection for enhanced traffic movement analysis;
Provide real-time traffic data, including speed, object classification, vehicle counts, and estimated time of arrival (ETA);
Operate reliably in all weather and lighting conditions without performance degradation;
Comply with industry standards for environmental durability, including IP sixty-seven (67)-rated protection against water and dust ingress and;
RADAR HUB
The radar hub at a minimum must consist of the following in order to be considered for award:
Process detection data from connected radar sensors and convert it into industry-standard traffic controller messages;
Include an Intel quad-core one (1) GHz i seven (i7) processor and a dedicated three hundred (300) MHz I/O processor for efficient data processing;
Feature multiple communication interfaces, including:
NEMA TS two (2) SDLC and ATC / ITS SDLC interfaces;
TS one (1) & thirty-three (33)x PIO interface;
Two (2) ten/one hundred Ethernet ports;
Two (2) USB ports;
One (1) RS-two hundred thirty-two (RS-232) terminal port;
One (1) SD card slot;
Provide high-resolution logging of detection information for traffic analysis and optimization;
Support Power Line Communications (PLC) to enable Ethernet communication with radar sensors up to one thousand (1,000) feet away;
Feature built-in forty-eight (48)VDC six hundred (600)W and twelve (12)VDC (one hundred fifty (150)W power supplies for efficient power management;
Be designed for wall mount, shelf mount, and rack mount installation to fit various traffic cabinet configurations;
Operate within a temperature range of negative thirty-four point six (−34.6)°F to positive one hundred sixty-five point two (+165.2)°F (negative thirty-seven (−37)°C to positive seventy-four (+74)°C) for reliable field deployment;
Be NEMA TS two (2) compliant for temperature, voltage, transients, vibration, and shock and;
Be FCC Part fifteen (15) compliant for electromagnetic interference control.
RADAR SENSOR UNITS
The radar sensor units at a minimum must consist of the following in order to be considered for award:
Utilize a wide-angle detection approach to minimize the number of sensors required per intersection;
Feature a twenty-four point zero five (24.05)-twenty-four point two five (24.25) GHz (K band) frequency range for high-precision object detection;
Provide up to one hundred twenty (120) programmable detection outputs for flexible traffic control applications;
Support real-time tracking of vehicles, pedestrians, and bicycles for adaptive signal control;
Offer multiple mounting options for optimal positioning at intersections;
Support installation using shielded fourteen (14)-two (2) grounded cable for reliable connectivity;
Operate within a temperature range of negative forty (−40)°F to positive one hundred sixty-five (165)°F negative forty (−40)°C to positive seventy-four (+74)°C for deployment in extreme environments;
Consume twenty (20)-twenty-eight (28) VDC power at a maximum of thirty-six (36) W;
Feature an IP sixty-seven (67)-rated enclosure to protect against harsh environmental conditions and;
Provide Ethernet connectivity for seamless integration with the Radar Hub and Traffic Management System.
SYSTEM COMPONENTS
One (1) EVO RADAR Hub:
Traffic Manager Software;
Built-in power supplies for connected sensors;
All necessary interface cables for connectivity;
Two (2) EVO RADAR Sensor Units;
All necessary cable, hardware, fittings, and mounting brackets for complete installation and;
Field turn-on assistance.
Section 2 – ACRONYMS
| Term |
| Definition |
| AI |
| Artificial Intelligence |
| ATC |
| Advanced Transfer Cache |
| BNC |
| Bayonet Neill–Concelman |
| C |
| Celsius |
| CCTV |
| Closed-circuit television |
| F |
| Fahrenheit |
| FCC |
| Federal Communications Commission |
| FMCW |
| Frequency Modulated Continuous Wave Radar |
| FPS |
| Frames Per Second |
| G |
| Gravitational Constant |
| GPU |
| Graphics Processing Unit |
| Hz |
| Hertz |
| HTTPS |
| Hypertext Transfer Protocol Secure |
| IP |
| Internet Protocol |
| JPEG |
| Joint Photographic Experts Group |
| MJPEG |
| Motion Joint Photographic Experts Group |
| MP |
| Millions Of Pixels |
| IRE |
| Institute of Radio Engineers |
| IR LEDS |
| Infrared Light Emitting Diodes |
| LAN |
| Local Area Network |
| MHz |
| Megahertz |
| ms |
| Milliseconds |
| NEMA |
| National Electrical Manufacturers Association |
| NTCIP |
| National Transportation Communications for Intelligent Transportation System Protocol |
| ONVIF |
| Open Network Video Interface Forum |
| G RMS |
| Root Mean Square Acceleration |
| RGB |
| Red, Green, Blue |
| RS |
| Recommended Standard |
| SD |
| Secure Digital |
| SDLC |
| Synchronous Data Link Control |
| SDXC |
| Style-Driven eXpressive Sampling |
| USB |
| Universal Serial Bus |
| VAC |
| Volt Alternating Current |
| VDC |
| Volt Direct Current |
| W |
| Watt |
| WDR |
| Wide Dynamic Range |
1 | Page dcc
RFQ813 TRAFFIC VIDEO AND RADAR DETECTION SYSTEMS 02/2025
image1.png
File details come from the government source that posted it. Updated .