Classified as Internal

Classified as Internal

Exhibit C, Addendum 1: Specifications, Duties, and Scope of Work

Advanced Transportation Controller (ATC) 6/1/2026

Table of Contents

Acronyms

Definitions Data Field Data fields are used to display variable data and to allow the user to enter data.

Life of the product The time from the first production unit until the ATC is no longer produced or manufactured, plus an additional 5 years from the last production date.

Normal Operation The traffic signal controller operates and times signal vehicle movements at an intersection. This includes Emergency Vehicle Priority/Preemption, Transit Signal Priority, and Railroad Preemption.

An intersection in flash is not considered normal operation.

No external memory device is required for normal operation.

Background This procurement is for Advanced Transportation Controllers (ATCs) with traffic signal control software including the ATC Application Programming Interface (API). This specification includes ATCs with traffic signal control software potentially running intelligent transportation systems (ITS) and connected vehicle software.

ITS and connected vehicle application software are not part of this procurement.

Desired: Figure 1 on the next page clarifies the software desired by this ATC specification.

Desired: Figure-1

General Specification Overview The responder should submit a matrix showing their proposed controllers’ compliance with each line of the specifications (Sections 4 – 20) held here-in. If this is not submitted with the responder’s initial RFP response, it will be requested during evaluation. See more about this in Section 17.2.

This document is prepared for the State of Minnesota and Minnesota Cooperative Purchasing Venture (CPV) members for the purpose of placing on State contract Advanced Transportation Controllers (ATC’s) in accordance with “Advanced Transportation Controller (ATC) Standard 5201” and this document. Specifications for the ATC controller common to all form factors and cabinet interfaces are included in Section 7.2.

ATCs will be procured in different form factors and with different options. See Section 21 Bid Line Items for additional information.

This document includes a bid line item for training. This training will cover traffic signal controller operations and ATC controller maintenance. Requirements for this training are defined in Section 19.1 Live in Person Training Session.

Preference will be given to those that can meet the “desired” sections. Manufacturers will not be disqualified if they do not offer the “desired” features.

Shelf Mount For use in NEMA TS2 Type 1 Cabinets.

Rack Mount For use in Advanced Transportation Controller Cabinets.

Specifications detailing the types of cabinet interfaces are included in Section 8.2.

Build america buy america The provisions of the Build America, Buy America (BABA) Act, Public Law No.117-58 §§ 70901-70952, the Buy America law, 23 U.S.C. § 313, 2 CFR Part 184 and 23 CFR § 635.410 require the Contractor to furnish manufactured products and iron and steel products (including miscellaneous items such as fasteners, nuts, bolts, and washers).

1. Manufactured Products. Manufactured products means articles, materials, or supplies that have been processed into a specific form and shape, or combined with other articles, materials, or supplies to create a product with different properties than the individual articles, materials, or supplies.

Components that are wholly or predominantly steel, iron, or both must satisfy FHWA’s existing requirement for domestic iron and steel. This includes cabinets or other enclosures of intelligent transportation systems that incorporate steel or iron components.

(1) final assembly for all manufactured products incorporated into the project must take place in the United States; and (2) the cost of components of products that are mined, produced, or manufactured in the United States must be greater than 55% of the total cost of all components of the manufactured product.

2. Iron and Steel Products. In the case of iron and steel products, produced in the United States means that all manufactured processes from the initial melting stage through the application of coatings, occur in the United States. Foreign source materials are any domestic products taken out of the United States for any process (e.g., change of chemical content, permanent shape or size, or final finish of product).

Iron or steel products means articles, materials, or supplies that consist wholly or predominantly of iron or steel or a combination of both iron and steel.

Predominantly of iron or steel or a combination of both means that the cost of the iron and steel content exceeds 50 percent of the total cost of all its components. The cost of iron and steel is the cost of the iron or steel mill products (such as bar, billet, slab, wire, plate, or sheet), castings, or forgings utilized in the manufacture of the product and a good faith estimate of the cost of iron or steel components.

Prices must be based on furnishing domestic iron and steel, which includes the application of the coatings.

Raw materials such as iron ore, pig iron, processed, pelletized, and reduced iron ore, waste products (including scrap, iron or steel no longer useful in its present form from old automobiles, machinery, pipe, railroad rail, and steel trimmings from mills or product manufacturing) and other raw materials used in the production of iron or steel products may be imported from outside of the Unites States. Extracting, handling, or crushing the raw materials which are inherent to the transporting of these Materials for later use in the manufacturing process are exempt from the BABA Act.

The Contractor is required to submit a Certificate of Compliance upon delivery. This shall be accomplished by the Contractor submitting the appropriate Certificate of Compliance to the Department when the Materials are delivered to the Department. The Certifications of Compliance will certify the Materials are considered produced in the United States. The Certificate of Compliance must be signed and dated by the Manufacturer’s authorized representative and a statement: The Materials herein referenced are produced in the United States and comply with the requirements of 23 CFR § 635.410, 2 CFR Part 184, Public Law No.117-58 §§ 70901-70952, and 23 U.S.C. § 313.

Supporting documentation to demonstrate compliance with BABA Act provisions (such as mill test reports, manufacturer/supplier certifications, etc.) shall be organized and maintained by the Contractor from the date of delivery until six years from the date of delivery.

The Department may review the Contractor’s supporting documentation to verify compliance with the BABA Act provisions at any time upon request. The burden of proof to meet the BABA Act provisions rest with the Contractor. If the supporting documentation does not demonstrate to the Department that the manufactured products and iron and steel products identified in the Certificates of Compliance were produced in the United States, then the manufactured products and iron and steel products will be considered non-compliant and will be replaced at Contractors expense.

Standards References The following standards are to be considered included by reference:

CTI 4501 v01.01 Connected Intersections Implementation Guide.

Guidance to setting Up and Operating a Connected Intersection (CI)

NEMA TS2 2-2021

National Electrical Manufacturers Association (NEMA) Standards Publication TS 2-2021 Traffic Controller Assemblies with NTCIP Requirements Version 03.08.

ATC 5201

Advanced Transportation Controller (ATC) Joint Committee Recommended Standard

ATC 5201 V 06A.37

This is a connected intersection-ready Advanced Transportation Controller (ATC) Standard family developed by AASHTO, ITE, and NEMA.

ATC 5301

A Joint Standard of AASHTO, ITE, and NEMA Advanced Transportation Controller (ATC) Cabinet Standard Version 02

ATC 5301 V 02.02

This is a connected intersection-ready Advanced Transportation Controller (ATC)

ATC 5401

ATC 5401 V 02B.45

UCD Application Programming Interface (API) Standard for the Advanced Transportation Controller (ATC)

NTCIP 1201

NTCIP 1201 V 03

National Transportation Communications for ITS Protocol Global Object (GO) Definitions A major revision of NTCIP 1201 v02.32

NTCIP 1202

NTCIP 1202 v03B National Transportation Communications for ITS Protocol Object Definitions for Actuated Signal Controllers (ASC) Interface

NTCIP 2101

NTCIP 2101:2001 V 01.19

National Transportation Communications for ITS Protocol Point-to-Multi-Point Protocol over RS-232 Subnetwork Profile RFC 5905 NTPv4 Network Time Protocol version 4 (NTPv4) SNMPv3 Simple Network Management Protocol version 3 (SNMPv3) IPv6 Internet Protocol version 6 (IPv6) Internet Layer Protocol for Packet-switched Internetworking

HTTPS

Hypertext Transfer Protocol Secure (HTTPS)

WCAG 2.1

Web Content Accessibility Guidelines Section 508 Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. § 794d) ATC Requirements All Controller Form Factors Patents and Patents Pending List all patents or patents pending for the proposed controllers. This requirement includes hardware and software patents.

ATC Common Specifications ATCs submitted shall meet the minimum requirements listed in each item detailed in this section of the specification. If the ATC exceeds the requirements listed for a specific item, the controller will be considered in compliance with the specification.

The items listed in this section are required for all form factors of the controller.

Provide an ATC Controller that conforms to Advanced Transportation Controller (ATC) Standard 5201.

This MnDOT ATC Specification supersedes the Advanced Transportation Controller (ATC) Standard 5201 standard where differences occur between the documents.

Engine Board Details Provide an ATC Engine Board that conforms to the Advanced Transportation Controller (ATC) Standard and as follows.

0. Provide an engine board and CPU in accordance with ATC 5201 and as follows:

Minimum Processor:

32-bit, Dual Core

1.0 GHz

Minimum Required Memory:

2 MB Short Term Non-Volatile Memory 32 GB Long Term Non-Volatile Memory

1 GB DRAM,

or 2 MB Short Term Non-Volatile Memory 1 GB On Board Long Term Non-Volatile Memory, expandable to a minimum 32GB SDHC Class 10 SD card

1 GB DRAM

Provide at least two Ethernet ports with a minimum speed of 10/100 Mbit meeting the following:

1. Minimum of one RJ-45 WAN port on the exterior of the controller shell, Locate the second RJ-45 LAN port on the exterior of the controller, Supports TCP/IP communications protocols, Supports SNMPv3, and Desired: Linux Kernal to support Internet Protocol version 6 (IPv6).

Provide at least 2 Universal Serial Bus (USB) ports 2.0 or greater.

1. Accessible on the exterior of the controller.

Locate a minimum of one port on the front panel.

Desired: Provide at least 2 Universal Serial Bus (USB) ports 3.0 or greater.

USB Flash memory card support meeting the following requirements:

1. Hot swappable.

The memory card is not required to be present during normal operation.

Software supports storage of the entire ATC database.

Isolation and Electrostatic Discharge Protection Requirements Provide Isolation and Electrostatic Discharge Protection that conforms to Section 7 of ATC 5201.

Environmental and Test Procedures Provide test software, perform testing, perform inspection, and provide testing certification that conforms to Section 9 of the Advanced Transportation Controller (ATC) Standard 5201 with its subsections.

Electrical and Electronic Requirements

0. Input Voltages

1. Input power 89 VAC to 135 VAC, 60 Hz (±3 Hz), Performance and Material Requirements Provide materials that conform to Section 8 of ATC 5201.

0. Removable PROMS and EPROMS are not acceptable.

0. No fans for cooling may be used.

0. No storage devices with rotating parts may be used.

0. Weather resistant keypads mounted on the ATC front panel.

0. Coat the sides of printed circuit boards with a clear moisture proof and fungus proof conformal coating.

0. An aluminum or polycarbonate enclosure with a protective finish and enclosed electrical components.

0. Identify and permanently mark the I/O connections, fuse holders, indicators, etc. on the ATC’s front panel.

0. ATC Input/Output connectors, fuse holders, indications, displays, switches, and control devices required for the operation and adjustments of the controller mounted on the front panel or exterior of the controller unit.

Quality Control Provide materials that conform to Section 9 of ATC 5201.

Linux Operating System and Minimum Kernel Configuration Provide a Linux operating system (O/S) that conforms to Appendix A, ATC 5201.

Linux O/S Version

0. Use a Linux operating system with long-term support or super-long-term support kernel version that is currently supported by industry.

Minimum kernel version 5.10.

K. At any point in the life cycle, the engine board shall have a Linux kernel meeting the requirements of long-term support or super-long-term support.

Resource Isolation

0. Ensure the reliability and stability of the traffic signal control application.

Operating System Updates

0. Support complete O/S updates, including but not limited to driver updates, minor services, and entire Kernel, from at least one of the following:

1. Personal computer over an Ethernet connection either locally or remotely.

Directly from a USB flash drive plugged into the front panel of the ATC.

Desired: Supports both section 7.12.A.1. and 7.12.A.2.

Automate and package the update process as a simple executable file or macro/script enabling the user to perform the update within a few steps.

Desired: Allow for field installation of O/S updates in accordance with 7.12.A., without placing the signal into flash.

Required Device Driver Interfaces Provide device driver interfaces that conform to Appendix B, ATC 5201.

ATC Form Factors ATC Form Factors Provide ATCs with the following two form factors:

0. Rack mounted for use in a 19 inch Electronic Industries Alliance EIA -310-B rack.

Shelf mounted for use in NEMA TS2 Type 1 cabinets with or without A, B, C, and D connectors.

1. A, B, C, and D connectors are not a requirement for inclusion in the State contract, however if a manufacturer produces a controller with these connectors as an option a bid line item is included.

An enclosure sized equal to or less than the following dimensions:

11 inches Tall, 12 inches Deep,

17.5 inches Wide.

Dimensions exclude handles and/or rack mounting tabs.

Cabinet Interfaces

0. NEMA TS2 Type 1 Controller Cabinet

1. Support NEMA TS2 Type 1 Port 1, 15 pin SDLC.

Provide a Connection to a NEMA TS-2 Type 1 Cabinet that conforms to Section 3.3.1, and ATC 5201 Sections 4.4.3 and 5.2.3.1 Port 1.

Advanced Transportation Controller (ATC) Cabinet Standard, ATC 5301

1. Provide complete interoperability and connectivity for cabinet conforming to ATC 5301.

Display Provide a display as follows:

0. Viewable in the sun.

A monochromatic display.

1. Desired: Substitute the monochromatic display for a full color red, green, and blue (RGB) graphics display.

Screen size 5.00 inch diagonal minimum.

Properly displays and operates down to a temperature of -34˚ C (-22 ˚ F).

Located on the exterior front of the ATC.

Intersection Control Software NEMA TS 2 Operation Provide intersection control software meeting the functionalities and operations specified in the NEMA Standards Publication TS 2-2021 “Traffic Controller Assemblies with NTCIP Requirements” Version 03.08 or newer.

Cloned (Paired) Phases or Channels When installed in an ATC cabinet the controller shall support HDSP channel programming where 2 channels can be assigned to a single phase. The two channels would operate as one controlling a single intersection movement. For example, HDSP channels 2 and 23 would be mapped to phase 2 which is controlling a single intersection movement.

TS2 Loop Detector Status Support

0. Support NEMA TS 2-2021 Channel Status Reporting detailed in 6.5.2.26.3 in both TS2 (BIU) and ATC (SIU) cabinet architecture.

The ATMS shall be able to read the fault status and report the specific failure as described in NEMA TS 2-2021.

1. Normal operation Detector unit failure Open loop Shorted loop Excessive inductance change Faults described in this section are different than controller software programmable faults with names like:

1. No Activity Max Presence Erratic Count Configuration Error Support remote detector reset command from the ATMS through the ATC to detector rack.

Intersection Identification 128 Characters Support user programming of a data field composed of letters, numbers, and special characters 128 positions long that can be retrieved by the ATMS. This shall be done through proprietary MIB object until NTCIP 1202 can meet these standards. For example (TH99 & Main St Sys ID 12345678).

If the ATC manufacturer can demonstrate an alternative process that meets the intent of the specification as defined above, MnDOT would consider that acceptable and would be considered in compliance with this section of the specification.

Acceptance of the proposed process submitted by the manufacturer will be at the sole discretion of MnDOT.

Objects Named in Accordance with NTCIP All objects and functions available in the local control software shall be named and defined according to the current NTCIP standard.

NTCIP and Custom MIB’s

0. Provide clear, logical labels, and definitions for custom manufacturer specific management information database (MIB) objects and functions.

Supply the complete library of NTCIP Management Information Database (MIB) for the submitted ATC.

Include all manufacturer specific custom objects.

Indiana Traffic Signal Hi Resolution Data Logger Enumerations Include Indiana Traffic Signal Hi Resolution Data Logger Enumerations for Traffic Signal Systems Performance Measures Dated October 2020.

Future updates to the Data Logger Enumerations must be included in controller within one year of publication.

Advanced Traffic Management System (ATMS) Support Controllers must fully support and provide integration support for MnDOT’s current ATMS system for traffic signals. At the time of MnDOT’s request for proposal for current state-wide ATMS system is Q-Free’s Kinetic® Mobility. Fully supported is defined by providing the ATMS vendor with the full and complete copy of the MIB tables for basic NTCIP 1202 SNMP based communication as defined in section 9.6 for NTCIP and custom MIBs. Fully supported shall also include all documentation/integration support needed to implement industry accepted communication protocols or APIs chosen by the controller manufacturer that could be used in lieu of NTCIP 1202.

MnDOT’s ATMS may change in the future. If this occurs MnDOT will provide formal written notice of the ATMS change at minimum of six months prior to the change.

Serial Bus 2 (TS2 Type 1 Port 1 SDLC)

0. The controller must provide an ATC serial bus 2 that has the NEMA TS2 Type 1 Port 1 SDLC connector and full functioning protocol.

The controller must be able to be configured so that both Serial Interface Units (SIU’s) and Bus Interface Units (BIU’s) can be mapped and operated concurrently using separate serial buses.

Addressable SIU 10-13 (Input Functionality #2 Through #5) Support

0. Support ATC SIU cabinet modules that have user defined programmable inputs and outputs that has selectable addressing of SIU 10 – 13 (Input functionality #2 through #5).

SIU Communications Loss SIU Serial Bus 1 Critical Communications Loss Functionality shall be as follows:

0. The controller must support functionality where if SB1 communications are lost to an SIU with any preemption inputs programmed through it the controller will cause the cabinet to go into flash.

1. Flash command shall be selectable.

The type of flash can be programmed to be either soft flash (remote flash) or hard flash (CMU flash).

Programming of the flash type can be either latching or non-latching and is user selectable.

SIU Railroad Preemption Port I/O Verify

0. The controller must recognize a pair of differential SIU inputs where a SIU read value of 0 and 1 would be normal operation, a 1 and 0 will call Preemptor 1 (Flash) or a 0 and 0 will call for flash.

If the ATC manufacturer can demonstrate an alternative process that meets the intent of the specification as defined above, MnDOT would consider that acceptable and would be considered in compliance with this section of the specification.

Acceptance of the proposed process submitted by the manufacturer will be at the sole discretion of MnDOT.

Basic Functionalities Provide intersection control software as specified herein and meet the following requirements:

0. At least 32 programmable phases.

0. At least 8 configurable concurrent groups in 4 timing rings.

0. At least 32 overlaps.

0. At least 16 unique phase sequences programmed and operated by time of day.

0. Allow the user to specify specific phase order and sequence beyond basic phase pair reversal/switching.

0. Shall support Urban (Texas Diamond) interchange operation.

0. A minimum of 100 unique timing patterns, each with a unique:

1. Cycle length, free, or flash command.

Phase split table.

Offset.

Phase or pedestrian recall or omit (per pattern).

Programmable using phase based programming.

Easy configuration of:

1. Flashing Yellow Arrow functionality.

Pedestrian overlaps.

Leading Pedestrian Interval or exclusive pedestrian intervals.

Trailing green sequences for compound intersections.

Preemption routines in accordance with the NEMA TS-2 specification (v03.07).

Support 4(09)-15 (I) – Variable Mode Left- Turn Display (Shared Lane) Support FYA for approaches that are split phase, shared use, lane striped for both through movement and left turn movements using a cluster head assembly.

Follow the link below for additional information:

FHWA Approval 4(09)-15 (I) – Variable Mode Left- Turn Display (Shared Lane) MnDOT prefers this operation to be part of standard traffic control signal operation software without the need for user logic statements, however a single logic processor step would be an acceptable solution.

Detectors

1. Minimum of 128 individual detector inputs.

Each detector will have a programmable alphanumerical label, for example D1-1. This value shall be accessible remotely through MnDOT’s ATMS in section 8.9.

Minimum of 4 detector tables selectable by time of day.

1. Desired: Minimum of 8 detector tables.

Minimum of 128 detectors per detector table.

Ability to call multiple phases with one detector.

Refer to section 9.3 for loop detector status support.

Flashing Yellow Arrow in NEMA TS 2 Type 1 Cabinets

1. For NEMA TS2 type 1 cabinets NEMA mode G FYA channel configuration is required.

Flashing Yellow Arrow in ATCC’s

1. For ATC cabinets NEMA mode D FYA channel configuration is required.

Preemption

1. A minimum of 14 Preempt sequences.

1. Controller Inputs (7 through 14) recognize solid inputs to differentiate between different emergency vehicle preemption (EVP) calls.

Inputs 1 through 6 are dedicated to railroad preemption. These individual inputs are required for railroad preemption circuits which provide more efficient and safer preemption.

Inputs 1 through 6 are defined as follows:

1. Input 1:

All Red Flash Command Railroad and traffic control signal interconnect failure.

This input is used in a situation where if the interconnect cable that connects the traffic control signal cabinet and the railroad bungalow containing the railroad train detection equipment for railroad preemption should get damaged the intersection would be forced into flash as a safety precaution.

Input 2:

Gate Down, Dwell Operation.

The intersection will service phases that do not conflict with the railroad crossing.

Input 3:

Simultaneous Preemption.

Railroad preemption call is placed as the crossing arms begin their descent or railroad crossing warning lights activate.

Input 4:

Advanced Preemption.

Railroad preemption call is placed in advance of the crossing arms beginning their descent or railroad crossing warning lights becoming active. This allows a track clearance interval to start timing prior to the warning lights going active and the crossing gates beginning their descent.

Input 5:

Advanced Pedestrian Preemption.

Railroad preemption call is placed prior to the advanced preemption call and in advance of the crossing arms beginning their descent or railroad crossing warning lights becoming active. This allows the controller to omit pedestrian intervals while the input is active. This eliminates the worst case timing condition for cycling the intersection to the track clearance phases.

Input 6:

Undefined.

Reserved for future use.

Preempt inputs 1 through 6 have a priority where 1 is the highest priority and 6 is the lowest.

Inputs 1 through 6 have a higher priority than inputs 7 through 14.

Preempt (Priority) inputs 7 through 14 are serviced on a first come first served basis.

Ability to call one of two preemption routines (inputs 7 through 14) for a single intersection approach based on time of day and the use of Flashing Yellow Arrow (FYA) operation.

MnDOT uses two preemption routines for each vehicle approach of a traffic control signal system when flashing yellow operation is present. One routine is in effect when FYA is active, and the other routine is active when FYA is not active. This is typically done by time of day.

MnDOT requires a total of 8 inputs. These inputs could be configured as one actual hardware input for each approach that calls one of two routines based on time of day.

If the ATC manufacturer can demonstrate a programmable work around such that 14 total preempt inputs as defined above are not necessary MnDOT would consider that acceptable and the ATC would be considered in compliance with this section of the specification.

Acceptance of the proposed preempt workaround as submitted by the manufacturer will be at the sole discretion of MnDOT.

Priority.

1. A minimum of 6 sequences.

A minimum of six (6) sequences that operate with one of three of the following Input Modes:

Constant call, Check in/out, and Check in plus time.

Support ETA based solutions conforming to NTCIP 1211.

1. If the ATC manufacturer can demonstrate an alternative process that meets the intent of the specification as defined above, MnDOT would consider that acceptable and would be considered in compliance with this section of the specification.

Acceptance of the proposed process submitted by the manufacturer will be at the sole discretion of MnDOT.

Peer to Peer communications.

0. Desired: Peer-to-peer allows the ATCs to send messages to other ATCs connected in the same network via Ethernet communications regardless of manufacturer.

Allows the user to send the status of ANY Input/Output function in the controller as well as phase intervals, preempt intervals, etc.

The peer to peer communications includes a virtual relay type structure allowing the ATC on an interconnected system to pass a preempt call or other programmed feature or action to other ATCs running the same software application on the interconnected system.

This virtual relay structure links to the user logic for functionality and programmability.

Customizable Alarms

0. Minimum of 32 customizable alarms.

Desired: Minimum of 64 customizable alarms.

Provide the user with a definable name of each alarm. For example, Alarm 1 = Door Open.

Within an ATC cabinet, the controller shall allow the front and back cabinet door open alarms as read from SIU bus 1/CMU to be tied to alarm 1 regardless of which door is open.

Pattern Change During All Red

0. Desired: The controller to be configurable to only change patterns, actions, events, overlaps, FYA’s, etc. during all red intervals.

This avoids issues of transitioning between different overlap phasing (particularly with FYAs) which cause undesirable Indications causing intersections to go into flash.

User Interface (On Board Web Server)

0. In addition to the front panel display, provide an ATC with an on-board web server that hosts a graphical user interface for monitoring and configuring the intersection control software.

Shall be configured for HTTPS and provide a utility/process for importing signed certificates.

Must prompt for username and password prior to displaying any controller information when remotely accessing the controller over the network interface.

AH. No additional or proprietary ATC manufacturer locally installed client software shall be required to use the graphical user interface.

AI. Desired: Controller to support centralized authentication of users through industry accepted processes such as LDAP, RADIUS, OpenID, etc.

Input / Output Configuration

0. Intersection control software allows the user to dynamically configure and modify inputs and outputs on an individual basis.

AK. Can configure the signal output channels (phase/overlap to load-switch or HDSP) so that any phase, overlap, or pedestrian output can drive any available indication output in the traffic signal control cabinet.

AL. Allows the user to perform such configurations and modifications from the ATC front panel or through the web user interface, without the need for additional configuration software or downloading additional files to the ATC.

NTCIP Communications Specifications Compliance Due to the nature of standards development, newer standards could become accepted over the life of this contract. If a standard is published, the controller manufacturer shall implement that standard within two years of its publication. In the following paragraphs, this is referred to as the most current publication.

· Desired: 6 months from publication.

Provide an ATC that supports and utilizes the following:

0. NTCIP 1201: V 03 “National Transportation Communications for ITS Protocol Global Object (GO) Definitions” or the most current version.

Simple Network Management Protocol version 3 (SNMPv3) shall be used over SNMPv1 wherever subsequent published standards allow. SNMPv1 may be used for any standard which does not support v3.

NTCIP 1202: V 03A “National Transportation Communications for ITS Protocol Object Definitions for Actuated Traffic Signal Controller (ASC) Units” or the most current version.

An industry accepted white paper is currently being finalized and is posted alongside NTCIP 1202 V04 which is the most current recommended standard. MnDOT recognizes that controller manufacturers cannot currently meet the requirements of 1202 V04 as designed but could meet the requirements of the white paper as an interim solution on the path to 1202 V04. Implementation of the recommendations of this white paper or the full implementation of 1202 V04 will meet the requirements of 9.19.B and 9.19.C.

Network Time Protocol A. The ATC shall support the latest NTP specification.

1. Ability to configure primary and backup server.

Ability to be programmed via front panel terminal display.

Ability to be programmed from NTCIP 1202 or custom API as shown in section 10.3 of this document.

1. Ability to ignore NTCIP based time sets.

Signal Phase and Timing Messaging (SPaT)

0. Desired: The intersection control software to support the transmission of SPaT messages.

1. SPaT messages will be processed by an application running on the ATC which will receive the message from the traffic signal control software and export the SPaT message on the Ethernet bus to a communication device for transmission to vehicles in the vicinity.

The SPaT messages will use NTCIP 1202 to ensure interchangeability of different brands of roadside communications units.

Advanced User Programs (User Logic)

0. In addition to standard operations specified in the NEMA TS-2-2021 Standard, provide the intersection control software to include a user programmable logic statement processor where the user can develop advanced logic statements and operations to be used as custom solutions or for feature development.

In addition to standard Boolean logic, allow the user to specify conditions using all input and output functions including but not limited to phase indications and intervals, detector calls, preempt status, interval/service times, and greater or less than relationships.

1. For example, provide a way for the processor to allow the user to program the following condition in the ATC front panel:

a. (e.g., calls preempt 6 if phase 2 is green for more than 25 seconds. Also send a message to the downstream controller to start preempting phase 6 in 15 seconds if the coordinator is currently in transition).

Database Management

0. Provide software that allows the user to save to or select from the list of stored databases on the ATC from the front panel or web user interface.

0. Provide the ability to download event logs, diagnostic logs, VIOT logs, etc. via network connections to the ATMS.

0. Allow databases to transfer between a personal computer and the ATC via the following methods:

1. Ethernet connection using the web based user interface.

Standard FAT (or FAT-32) formatted USB flash drive using the ATC front panel user interface.

0. Provide software that allows a user interface to select and save a database from the USB flash drive to the ATC when multiple databases are located on the USB flash drive.

0. Allow the ATC to switch between the current and stored databases at any time.

0. Desired: Allow the intersection control software and the ATC to store a minimum of two traffic signal databases (timing files) on the ATC for both intersections at any given time.

47. Allow the ATC to set the selected database as “Active” at the end of the current sequence during an all-red condition timing less than 4 seconds.

Windows Based Controller Emulation Software

0. Supply at least one copy of a Windows based intersection control software emulation software package with no limits placed on the redistribution of this emulation software within any given governmental agency in Minnesota.

1. Agencies may not distribute this software to any “for-profit entity”.

Emulation software runs on Windows client version 11 or later.

Allow the user to program an ATC on a Windows based computer.

Allow a program to run a simulated intersection operating on a personal computer (PC) after the user has programmed the intersection control software.

Provide a program equipped with the same version as the firmware version supplied with the ATC.

Allow the user to program a complete traffic signal controller and be saved on a USB memory drive for transfer to an ATC.

For the life of the product supply and update the emulation program and the Linux software for the ATC at the same time and at no additional cost to the agency for updates.

Controller Software Maintenance and Licensing All software supplied with the controller shall be licensed to the purchasing agency when software is included in the original purchase of the ATC for a minimum of 15 years from the date of delivery. This would include any variation of purchased software as detailed in Section 21.

During this period, no annual licensing or maintenance fees may be charged by the controller manufacturer including 3rd party software integration support.

0. Software Bugs The manufacturer shall have in place a mechanism for documenting and listing current and resolved software bugs which are made available to users for review, including failures to comply with WCAG 2.1 and Section 508.

This documentation shall also include operational feature additions and improvements.

Documentation

1. The resolution of software bugs and fixes shall also be documented and distributed to users.

Failure to Comply Failure to comply with this requirement will result in the State’s discretion of the immediate removal of the ATC from the contract.

Open Protocol and Hardware Requirements Management Information Base (MIB) Provide all NTCIP Management Information Base (MIBs) files associated with the most recent version of software including all manufacturer specific and extended objects.

0. Include all standard and custom MIBs for traffic signal control.

Every MIB object shall contain a complete description.

Provide any newly developed custom MIBs for the life of the product.

MIB’s shall be provided to MnDOT and its ATMS vendor at the time of any new software release.

1. Submitted MIB’s shall not cause parsers to fail. Should parsers fail the manufacturer will assist the local agency with resolving the issue.

Application Programming Interface Desired: When required, provide the new full line industry standard Application Programming Interface (API) and toolkit for all new ATC engine boards in accordance with UCD ATC 5401.

MIB Files & APIs The agency and its CPV members are permitted to copy, re-distribute, or reuse the MIBs/APIs for internal use to support the authorized use of the licensed ATC software in conjunction with supporting the Agencies central ATMS software, Connected Vehicle Technology software, or other Intelligent Transportation System (ITS) software. The agency or CPV members will be allowed to share MIBS/APIs with a 3rd party software company that the agency or CPV members use for software development.

A nondisclosure agreement (NDA) shall not be required by the manufacturer for custom MIB’s/APIs to be supplied.

Software Tool Kit The current software development tool kit (including toolchain and other necessary Linux Libraries) for the ATC engine board shall be publicly available for the lifetime of the product.

Cybersecurity The ATC installed in a traffic signal cabinet, that is network connected to an ATMS operating as an intersection controller, must survive a network vulnerability scan which will include denial of service attacks (DoS).

Tool and Test Requirements

0. At time of contract, the State uses Tenable.sc™ security center.

https://www.tenable.com/products/tenable-sc

1. Required tool configuration provided upon request.

Network Security Vulnerability Identification and Resolution

0. For the life of the product when a MNIT network scan identifies vulnerabilities, these shall be resolved by the manufacturer.

Vulnerabilities shall be addressed and resolved within six months of discovery.

Intersection and Traffic Signal Management System Operation

0. During the scan the intersection shall continue to operate normally and traffic responsive as follows:

1. Proper cycling through vehicle and pedestrian movements Vehicle detection inputs Pedestrian detection Railroad preemption inputs Emergency vehicle inputs ATMS Ethernet Communications Port Failure Logging A. Desired: If the Ethernet port is required to be temporarily shut down due to excessive data transfers such as DoS attacks which cause excessive CPU and memory usage the controller must log this information for easy access by the user.

Compliance MnDOT will conduct network scanning including denial of service attacks (DoS) of the controller using the Tenable.sc™ security center tool while connected to existing MnDOT ATMS system where both the scanning tool and communications software are simultaneously trying to communicate with the controller. Failure to successfully complete testing as outlined in section 11.5 will disqualify the controller.

Warranty

0. A minimum two (2) year warranty from the date of purchase on the entire ATC assembly including material, workmanship, labor, power supply and modules.

54. Desired: A separate bid line item for the ability to extend to a total of six (6) year warranty length.

Repair

0. ATCs in need of repair or replacement will be removed from the field by the agency and shipped to the manufacturer for repair or replacement.

Costs

0. If the repair is covered by warranty the manufacturer is responsible for all costs related to shipping the repaired ATC back to the agency.

Product End of Life Notification Provide a formal notification document on company letterhead for the product end of life date for the ATC. Provide this notification for a minimum of one year before the planned end of life date.

Ramp Meter or Traffic Signal Operation Software Integration ATC manufacturers listed on the state contract agree to cooperate and integrate another manufacturer’s ramp metering or traffic control software with their ATC hardware if the State or CPV members choose specific ramp metering or intersection control software not provided by the ATC hardware manufacturer.

The third party software application vendor and the ATC manufacturer agree to share programming interfaces, NTCIP defined objects, or additional protocols as required for full integration of the software application onto the ATC.

The Minnesota Department of Transportation will develop its own 3rd party ramp metering software. The ATC manufacturer agrees to work with MnDOT to integrate the ramp metering software into the ATC.

Other Agencies

0. If an operating agency or local unit of government chooses to integrate an operating software package that is not listed on the state contract the requesting agency is responsible for procuring the required source codes and defining the terms and conditions of the software integration between the ATC hardware manufacturer and the 3rd party software manufacturer.

Software Development Terms and Conditions

0. Terms and conditions of the software development contract will contain a mechanism for the controller manufacturer and/or operating software manufacturer to be compensated for development hours required to integrate the new piece of MnDOT software to run on the ATC.

DESIRED Features The features in this section are not required. These features are preferred as they provide very useful tools for field operations.

Submit separate bid line items for each of the listed optional features shown in this section. The line item should reflect additional costs for the specific option to the base ATC price when each option is ordered with the ATC.

See Section 21, Bid Line Items of this document for additional details.

NEMA TS1 A, B, C, D Connectors, FSK Telemetry Module

0. Provides the ability of a shelf mounted controller to interface with NEMA TS1 style cabinets. This is not a preferred feature, however, to extend the life of existing deployed MnDOT NEMA TS1 traffic control signal cabinets this option is required.

If the manufacturer does not offer this option, they will still be considered for inclusion in the State contract provided the controller meets all the other requirements listed in this specification.

Global Positioning System (GPS) Module In addition to the ATC 5201, include a GPS module that allows the ATC coordinates to be calculated and transmitted via ATMS software.

0. Provide an industry standard Sub-Miniature Version A (SMA) connector.

1. On the external Maintain network time to aid in coordination.

Provides GPS coordinates for the ATC used in V2I software applications.

C1 Connector (For Ramp Metering)

0. Provide cabinet interface for the following connectors:

61. Front connector C50 (replaces C40).

61. Rear connector C1S.

61. Rear connector C11S.

61. Rear connector C12S.

Documentation and Test Software The requirements listed in this section are considered incidental to the RFP and are included in the specific controller line item bid.

Submit the required documentation in this section electronically.

Quality Control Testing Certification

0. Provide with each delivered unit a compliant test report in accordance with ATC Standard 5201 Sections 8 and 9.

Operation Manuals Provide ATC operation and maintenance manuals.

In Portable Document Format (PDF).

The manuals will be reviewed by MnDOT prior to final controller acceptance.

1. Revisions required by MnDOT to the manuals will be incorporated by the manufacturer.

Manuals required by this section may be redistributed internally by the purchasing agency as they see fit to support Department required maintenance.

Submittal Requirements Required Documentation As part of the initial contract submittal process, provide documents that show the proposed ATC meets every required line item contained within this document. This documentation includes but is not limited to the following:

0. List of patents and patents pending for proposed controllers to be supplied under this contract.

Controller data sheets for all form factors.

Operational manuals.

Completed Word document as required in Section 17.2.

The manufacturer shall note items where the…