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

API Validation Suite


Background
The API Standard Version 1 was Jointly Approved by AASHTO, NEMA and ITE in September 2007. The purpose of the API Standard is to specify a universal software interface for ATC compliant controller units that facilitates software portability across manufacturers and enables interoperability of multiple applications on a single unit. It is anticipated that ATC controller units will soon be sold by manufacturers containing API software libraries and stating compliance to the API Standard. It is therefore critical for agencies, integrators and second party software developers to have an independent method to validate compliance to the API Standard.

The API Validation Suite is a set of test software that runs on the Engine Board of ATC Controller units (see ATC Standard 5.2b). Although the extensive combinations of field I/O devices and user inputs that are supported make comprehensive testing of the API libraries impossible, a set of practical tests can and still be performed. The development of this software includes a formal test plan, test descriptions, test software development, software descriptions and testing results.

Some of the benefits include:

  • Impartial testing common to the entire industry
  • Greater confidence and faster deployment of the ATC controllers and the API as manufacturers will have a level of provable compliancy
  • A tool for end users to call out in their specifications
  • Increased reliability of ATC controller units
  • Increased portability and interoperability of application programs on ATC controllers
  • Test software that can be expanded or enhanced

Next Steps
The API Working Group is now in the development of the API Validation Suite. Progress can be tracked in the "SDO Process" and "Project Plan" tables below. Please see also the next section on "Participation."

Participation
We are also soliciting help from the transportation community at large in the deployment of API Standard v2.06b. It is requested that agencies require manufacturers and vendors to require both API Standard v2.06b and the ATC Controller Standard in their specifications and requests for proposals (RFPs) for traffic control equipment. For further assistance, please contact Mr. Siva Narla (snarla@ite.org) or Mr. Ralph Boaz (rboaz@pillarinc.com).

Generally, we welcome participation at meetings, teleconferences, and document reviews from any and all interested parties. We will post a schedule of planned activities as they are determined and invite anyone interested to attend. Please keep in mind that we will need to know in advance if you wish to attend a particular meeting so that we can ensure adequate meeting facilities. In most cases, favorable hotel rates are available to meeting attendees. If you wish to attend any face-to-face meeting, please inform Mr. Siva Narla (snarla@ite.org). Teleconferences are open to everyone without advanced notice.

Tracking ATC API Validation Suite by the SDO Process
The SDO process is defined specifically for the production of standards and related documents. While similar review and oversight will occur in the development of the API Validation Suite, tracking by the SDO process does not apply. Please see "Project Plan" tracking below. (For complete details on the steps of the Standards Development Process please see: www.ite.org/standards/ITEStandardDevProcess.pdf)

Tracking ATC API Validation Suite by the Project Plan
(For complete details on the steps of the Standards Development Process please see: www.ite.org/standards/ITEStandardDevProcess.pdf)

Step No.
Project Plan
Step Status
Start Date
Completion Date
77

Finalize Documentation and API Validation Suite for Distribution

  • Validation Suite Distribution (Method of distribution and maintenance is being determined.)
  • API WG Teleconference Notes, December 15, 2010 PDF | Word
Completed
12/01/2010
12/31/2010
76

Demonstrate the API Validation Suite at Agency Site

  • API WG Meeting Notes, December 9, 2010 PDF | Word
Completed
12/09/2010
12/10/2010
68

Implement the API Validation Suite Software

  • API Validation Suite APIVSXML Specification Version v2.0 PDF | Word
Completed
8/06/2010
12/31/2010
57

Develop Software Design Description (SDD)

  • API Validation Suite Design Specification v2.0 PDF | Word
  • API WG Teleconference Notes, August 6, 2010 PDF | Word
Completed
5/21/2010
12/31/2010
44

Develop Software Requirements Specification (SRS)

  • API Validation Suite Software Requirements Specification v01.01 PDF | Word
  • API WG Teleconference Notes, May 26, 2010 PDF | Word
  • API WG Teleconference Notes, May 21, 2010 PDF | Word
  • Draft API Validation Suite Software Requirements Specification v01.00 PDF | Word
Completed
4/15/2010
5/21/2010
26

Develop Concept of Operations (ConOps) Content

  • API Validation Suite Concept of Operations v01.01 PDF | Word
  • Draft API Validation Suite Concept of Operations v01.00 PDF | Word
  • Draft API Test Plan v01.04 PDF | Word
  • API Working Group Meeting Notes, San Antonio, TX Aug. 12-14, 2009 PDF | Word
Completed
8/12/2009
4/15/2010
24 Authorization to Perform Completed
7/9/2009
7/9/2009
7 Systems Engineering Management Plan (SEMP) v01.05 PDF | WORD Completed
12/22/2008
5/18/2009
6
Project Management Plan (PMP) v01.06 PDF | WORD
Completed
11/17/2008
5/18/2009
Prior Draft
Std

Application Programming Interface (API) Standard for the Advanced Transportation Controller (ATC) Version 1 (v02.06b) Completed
01/14/04
09/21/07

 


Institute of Transportation Engineers
1627 Eye Street, NW, Suite 600 | Washington, DC 20006 USA
Telephone: +1 202-785-0060 | Fax: +1 202-785-0609
ite_staff@ite.org

Facebook Twitter LinkedIn YouTube Google+ Instagram Pintrest

ITE Canon of Ethics
2017 Institute of Transportation Engineers