Software

Ensure full communications between your new signal controllers and any central system you choose.

Under this contract, the Vendor shall provide all NTCIP Management Information Base (MIBs) files associated with the licensed controller software including manufacturer specific and extended objects and block object definitions. 

Vendor places no limitations under this contract on the use of the MIBs associated within the licensed controller software. Agency and its ITS partners are able to request MIBs from each associated vendor to support interoperability within their authorized use of the licensed software.

Hardware

Leverage the full power of your ATC Controller and ensure application portability between different manufactures’ controllers.

Controller motherboard and CPU shall support open architecture and be compliant with the ITE, AASHTO, and NEMA Standard Publication for ATC 5201 Advanced Transportation Controller Standard version 6.x.

All major components shall meet the environmental, design, and operating standards outlined in NEMA Standards Publication TS2-2003 v02.06, Section 2.   

These standards specify minimum requirements for the traffic signal controller except where requirements specified in this document exceed the aforementioned documents. 

In compliance with the ATC standard, the vendor shall include the current software development tool kit (SDK) including tool-chain and other necessary Linux Libraries for the ATC engine board and shall make the SDK publicly available for the lifetime of the product. 

The ATC hardware shall support an open architecture hardware and firmware platform interface for application programs to operate on the controller.  The controller shall include an interface conforming to the requirements of the ATC 5401 Application Programming Interface (API) standard (v02.x). Functionality provided in the industry standard Application Programming Interface Reference Implementation (APIRI) shall be required at a minimum.