Background
During the development of API Standard Version 1, the API WG had determined the need for a Configuration Management capability but, at that time, it was beyond the scope of that effort to develop it. Funding was secured to support the development of API Standard Version 2 with the main purpose to include this capability. The purpose of the Configuration Management capability is to provide a uniform interface, both in user interface and programmatically, for ATC controller units to set/manage/view system wide parameters. This is analogous to the Control Panel Utility of Windows Operating Systems. The parameters to be configured may include Time, Ethernet Ports, Device Driver Information, Operating System Version Information, API Library Information, and Host EEPROM information as described in the ATC Standard 5.2b, Section B.3.3. The benefits of the API Standard Version 2 are as follows:
Next Steps
The API Working Group is now in the development of the API Standard Version 2. Progress can be tracked in the "SDO Process" and "Project Plan" tables below. Please see also the next section on "Participation."
Participation
We are looking for additional public sector members in the ATC API Working Group to assist in the development of API Standard Version 2. Please contact Mr. Siva Narla (snarla@ite.org).
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.
(For complete details on the steps of the Standards Development Process please click here.)
|
SDO Process Step
|
Date
|
|
Jointly Approved Standard |
9/01/2011
|
| Appeals |
None
|
|
Notice of Intent to Adopt |
8/10/10
|
|
Recommended Standard |
8/19/10
|
| Committee Comments |
None
|
|
Comments Report |
8//05/10
|
|
User Comment Draft (UCD)
|
4/27/2010
|
(For complete details on the steps of the Standards Development Process please click here.)
|
Step No.
|
Project Plan
|
Step Status
|
Start Date
|
Completion Date
|
| 97 | Publish ATC API V2 Standard |
Completed
|
8/22/2011
|
9/1/2011
|
| 79 |
Develop ATC API V2 Recommended Standard
|
In Progress
|
4/27/2010
|
12/07/2010
|
| 63 |
Develop ATC API V2 UCD Standard |
Completed
|
3/23/2010
|
4/27/2010
|
| 52 |
Develop Design Content |
Completed
|
3/02/2010
|
3/22/2010
|
| 40 |
Develop Standards Requirements Content |
Completed
|
12/14/2009
|
3/01/2010
|
| 26 |
Develop Concept of Operations (ConOps) Content
|
Completed
|
10/14/2009
|
2/15/2010
|
| 24 | Authorization to Perform |
Completed
|
10/13/2009
|
10/13/2009
|
| 7 | Systems Engineering Management Plan v01.02 (SEMP) |
Completed
|
12/22/2008
|
7/21/2009
|
| 6 | Project Management Plan v01.02 (PMP) Project Management Plan v01.03 (PMP) PDF | Word |
Completed
|
11/17/2008
|
7/21/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
|