C-1054(5)-Attachment-F-Version-02.docx

ATTACHMENT F, VERSION 02: TECHNICAL SPECIFICATIONS

Responder Name: _____________________________________________________

Instructions. Devices must meet the following mandatory requirements detailed by the State in this Attachment F, Sections 1-16. Mandatory requirements are followed by Comply? |_| YES or |_| NO boxes. A box must be checked for each mandatory requirement. A non-response or checking the “No” box will represent the device’s inability to comply with that mandatory requirement. Failure to comply with a mandatory requirement will eliminate the device from further consideration under this procurement unless all proposed devices are unable to comply with that requirement.

If a requirement asks for additional information after checking a box, Responder should provide that information on this form. The State reserves the right to ask Responders for clarification or additional information. Any response to such State clarification requests or questions may be rescored based on the information provided.

If a Responder checks “No” for a mandatory specification, the State reserves the right to clarify the Responder’s intent and meaning.

Responses to these requirements and questions should be given in this document only, with the exception of Section F.I.16, RFP Deliverables. Do not add links or refer to other documents within your response when responding to a requirement or a question.

Provide manufacturer name and model number of your proposed device(s):

F.I, Mandatory Requirements

1. Camera:

0. Must be a model already in production and available for purchase

0. Ability for Dynamic I/P frame rate with dynamic quality and compression rate adjustment

0. Minimum of 120dB Wide Dynamic Range (WDR)

0. Aspect Ratio 16:9

0. Day/Night Capabilities with IR Cut Filter

0. Signal-to-Noise Ratio >50dB

0. Iris Control Auto Iris with manual override

0. Backlight Compensation F.I.1, Camera: Comply? |_|YES |_|NO

1. Optics:

1. Minimum of 30X optical zoom

1. Angle of view; approximately 60 degree (wide)/2 degree (tele)

1. Full HD 1,920 x 1,080 (1080p) and capable of 60 Images per second F.I.2, Optics: Comply? |_|YES |_|NO

1. Sensitivity:

2. Low Light Down to 0.03 LUX minimum F.I.3, Sensitivity: Comply? |_|YES |_|NO

1. Image Processing:

3. Electronic Image Stabilization (EIS)

3. Ability to display azimuth on video temporarily while moving camera

1. Momentary or continuous display allowed F.I.4, Image Processing: Comply? |_|YES |_|NO

1. IP Stream:

4. Ability to simultaneously provide a minimum of two (2) independent H.264 streams

4. Ability to adjust resolution of each individual stream (minimum of two (2) unique streams)

4. Ability to multicast using H.264

4. Ability to unicast 5 simultaneous users F.I.5, IP Stream: Comply? |_|YES |_|NO

1. Network Interface:

5. Interface Ethernet (Minimum 100 mbps interface) Auto negotiate

5. Supports these protocols: TCP/IP, HTTP, HTTPS, ICMP, UDP, RTP, RTSP, NTP, IPv4, SNMP, ARP

5. Security Access Password protected

5. Must support Chrome and Edge browsers for user Interface

5. Ability for remote software update, rebooting, backup/restore/transfer configuration

5. ONVIF Profile S, Profile G, or Profile T

5. Administrative features include configuring network settings, user password assignments, setting video streaming properties, configuring camera imaging properties, defining presets and tours, and assigning camera ID labels.

F.I.6, Network Interface: Comply? |_|YES |_|NO

1. On Screen Display:

6. Camera must allow MnDOT to add, with variable size and position, MNDOT color logo with transparency from standard image file to the video stream. The State may request an example to demonstrate compliance with this specification. See example image here:

F.I.7, On Screen Display: Comply? |_|YES |_|NO

1. Positioning Drive:

7. Minimum vertical tilt from 40 degrees up to 80 degrees down

7. Minimum of 8 presets

7. 360° Continuous Pan Rotation

7. 1° to (70° Minimum) of rotation per second proportional pan

7. Proportional panning speed to zoom level

7. Designed to minimum of IP66 specification

7. Auto home, park

7. Presets, tours, sectors

7. Preset Accuracy: ±0.1° F.I.8, Positioning Drive: Comply? |_|YES |_|NO

1. Electrical:

8. PoE++, Input voltage 120VAC

8. Single CAT5E cable with PoE++

8. Built-in electrical transient/surge protection F.I.9, Electrical: Comply? |_|YES |_|NO

1. Power Supply:

9. Supplied as part of the camera assembly

0. Upon request, Responder must provide specific details of the Power Supply for the State to review.

F.I.10, Power Supply: Comply? |_|YES |_|NO

1. Mechanical:

10. Built in wiper

0. Upon request, Responder must provide drawing/schematic of wiper system including materials description for the State to review for durability. See F.I.16, RFP Deliverables, below; information submitted for that answer will count for this item as well.

10. Thermostatically controlled Window defroster/defogger heater

10. Minimum operation in wind speed of 75 MPH

10. Nominal Maximum dimensions of camera and tilt/pan unit:

3. 20” (twenty inches) high

3. 9” (nine inches) wide

3. 14” (fourteen inches) deep

10. Must have bolt pattern or adapter plate included with each camera to attach to MnDOT RTMC Standard mounting bolt hole pattern. See Figure 1, below. If Adapter plate is used, its finish must be powder coated to match color of camera housing.

4. Upon request, Responder must provide description of how the MnDOT RTMC Standard mounting bolt hole pattern will be utilized for the State to review for compatibility. The State requires a pole top mount and an optional side of pole mount.

10. Housing construction: Cast, extruded and sheet aluminum; stainless steel hardware.

5. Non-dome PTZ only. NO DOME-STYLE CAMERAS WILL BE CONSIDERED.

10. Weight not greater than 30# (thirty pounds) with Wiper and IOC

10. If provided with a pre-connectorized ethernet cable:

7. Must exit through the bottom of the PTZ unit, aligning with the 1.4” hole shown in Figure 1, below.

7. Attached Ethernet “connection cord” must be at least 36” in length, if provided.

7. No additional external cables are allowed.

7. RJ45 Ethernet connector on “connection cord” must have a Male field attachable IP67 rated outdoor shell connector.

F.I.11, Mechanical: Comply? |_|YES |_|NO

Remainder of this page intentionally left blank.

See next page for Figure 1: MnDOT Standard Camera Mount Bolt Pattern

FIGURE 1: MnDOT STANDARD CAMERA MOUNT BOLT PATTERN

1. Environmental:

11. Operational specifications meeting NEMA TS2 temperature range

11. Minimum of IP66 housing protection F.I.12, Environmental: Comply? |_|YES |_|NO

1. Certifications:

12. CE, Class A

12. FCC, Class A

12. UL Listed

12. NEMA TS-2 (Temp.) para 2.2.7.3 - 2.2.7.7

12. Meets NEMA Type 4X and IP66 Standards

12. ONVIF Profile S

12. ONVIF Profile G

12. ONVIF Profile T

12. Shock test per IEC 60068-2-27

12. Vibration per IEC60068-2-6

12. Impact resistance of housing was tested in accordance with IEC 62262 F.I.13, Certifications: Comply? |_|YES |_|NO

1. Accessories:

13. Wall mounts and pole mounts must be available for purchase as desired by MnDOT.

F.I.14, Accessories: Comply? |_|YES |_|NO

1. Warranty:

14. Manufacturer hardware warranty of 5 years with State of Minnesota as the owner.

0. For warranty returns, contractor or manufacturer pays shipping costs to and from MnDOT.

14. Must have ongoing manufacturer support and firmware bug/security patches for a minimum of 5 years after purchase.

14. Known firmware bugs or security vulnerabilities must be resolved within 6 months of notification.

F.I.15, Warranty: Comply? |_|YES |_|NO

1. RFP Deliverables:

15. Comprehensive data summary sheets describing proposed model(s) are preferred. Electronic manuals are acceptable. Hyperlinks are not acceptable.

0. If data sheet/manual does not give all information, provide additional data on company letterhead showing how the product meets requirements. Label your response as “F.I.16, RFP Deliverables.”

0. Marketing and publicity materials are discouraged.

15. Provide detailed drawings of proposed camera including wiper mechanism specifics and Power Supply specifics.

15. Provide detailed response of how the MnDOT RTMC Standard mounting bolt hole pattern will be utilized. The State desires a pole top mount, not a side of pole mount.

15. Before final award, at MnDOT’s request Responder must submit a sample unit meeting these specifications for review and testing. Testing duration shall be a minimum of 4 weeks and a maximum of 8 weeks. Responder pays for shipping sample unit to MnDOT and for return shipping to Responder.

F.I.16, RFP Deliverables: Comply? |_|YES |_|NO

F.II, Desirable (Preferred) Capabilities Instructions. The capabilities noted by the State in this Attachment F, Sections 17 and 18, are desirable (preferred) but not required. Desirable capabilities are followed by Comply? |_| YES or |_| NO boxes. A box should be checked for each desirable capability. A non-response or checking the “No” box will represent the device’s inability to comply with that capability. Devices that can provide these preferred capabilities may score higher.

1. Build America Buy America (BABA) - see link for requirements FHWA Announces Updates to Buy America Requirements to Promote Domestic Manufacturing in Transportation Projects | FHWA URL: https://highways.dot.gov/newsroom/fhwa-announces-updates-buy-america-requirements-promote-domestic-manufacturing Does the proposed product meet the BABA requirements effective October 2025?

F.II.17-2025 |_|YES |_|NO

Does the proposed product meet the BABA requirements effective October 2026?

F.II.17-2026 |_|YES |_|NO

In addition to checking a box for each item in Section 18, Responders may choose to add more information explaining how your proposed device meets each desired capability. The State reserves the right to ask Responders for clarification or additional information.

Responses to capabilities and questions below for Sections 18 and 19 should be given in this document only. Do not add links or refer to other documents within your response when responding to a desirable capability or a question.

Responders may add additional lines as necessary.

1. Additional Scoring Considerations:

17. Wide angle lens option available for the same PTZ setup. F.II.18a: Comply? |_|YES |_|NO

17. Higher than 30X optical zoom. F.II.18b: Comply? |_|YES |_|NO

17. Static non-PTZ option with same camera interface and management software.

F.II.18c: Comply? |_|YES |_|NO

17. Optional digital zoom. F.II.18d: Comply? |_|YES |_|NO

17. Management tools for mass software updates while deployed in the field.

F.II.18e: Comply? |_|YES |_|NO

17. Wiper designed for durability and serviceability. F.II.18f: Comply? |_|YES |_|NO

17. Provides H.265 video streams. F.II.18g: Comply? |_|YES |_|NO

17. Offers adjustable/programmable defroster/defogger temp setting. F.II.18h: Comply? |_|YES |_|NO

17. Supports logging to a Syslog server. F.II.18i: Comply? |_|YES |_|NO

17. Supports privacy mask and privacy zones. F.II.18j: Comply? |_|YES |_|NO

17. Low light capabilities better than requirement in F.I.3, Sensitivity, above, without infra-red (IR) spotlights attached externally to cameras.

F.II.18k: Comply? |_|YES |_|NO

17. Ability to provide the same or similar camera model accepting a SFP fiber network interface. May be used for small percentage of deployments.

F.II.18l: Comply? |_|YES |_|NO

17. Capability of inverting video for hanging installation, could be physical or through software.

F.II.18m: Comply? |_|YES |_|NO

17. Optional supported protocols, SNMP v3, SSH. F.II.18n: Comply? |_|YES |_|NO (If device supports either or both of these protocols, check “YES” and give details here.)

17. Highest possible image quality for human viewing and vision is essential. Human operators will observe camera feeds. Machine viewing is a secondary consideration. F.II.18o: Comply? |_|YES |_|NO

17. Supports MJPEG video. F.II.18p: Comply? |_|YES |_|NO

17. Ability to capture still image(s) at request to camera. F.II.18q: Comply? |_|YES |_|NO

F.III, Responder Experience Instructions. The State desires to work with Responders who have an established history supporting IP PTZ traffic cameras, and to procure camera models with an established history of being used in similar circumstances. Failure to respond to this question may result in a lower score.

18. Indicate here the number of years of experience the Responder has in providing and servicing IP PTZ traffic cameras: ______ years.

Provide information about similar deployments using the proposed and similar products. Include details about the environment, use case, and include the length of time the products have been deployed. You may include experience creating customized external traffic camera solutions. Responders may add lines and pages as necessary. The State reserves the right to request information about the number of years that the camera model offered has been in production.

Rev. 12/19 Page 1 of 15

Rev. 9.01.2021 image1.png image2.png