New York State Regional ITS Architecture Home Page

About this Web Site

The purpose of this regional ITS architecture web site is to encourage use of the regional ITS architecture and gather feedback so that the architecture is used and continues to reflect the intelligent transportation system vision for each of the regions.  

Comments can be sent by email to the ConSysTec Program Manager Dr. Robert S. Jaffe, or by USPS to:

Consensus Systems Technologies Corp. 
PO Box 517, 17 Miller Ave.
Shenorock, NY 10587-0517

Regional ITS Architecure Development Process

• On May 19, 22 and 24, 2000 in Buffalo, NY, staff from ConSysTec and Ron Ice and Associates conducted and moderated a Western New York and Southern Ontario Regional ITS Architecture Workshop. This architecture was updated to Version 5.1 of the National ITS Architecture and to include several ITS Border Services by ConSysTec staff during Spring of 2005. This architecture is now known as the Buffalo-Niagara Bi-National ITS Architecture.
• On August 11, 14 and 16, 2000 in Albany, NY staff from ConSysTec Corp. and Ron Ice and Associates conducted and moderated a New York Statewide Services ITS Architecture Workshop.

• On June 24, 26, and 28, 2002 in Albany, New York, staff from ConSysTec Corp. and Ron Ice and Associates with support from the Rennselaer Polytechnic Institute conducted a Capital District Regional ITS Architecture Workshop. 

Prior to the regional workshop, the contractors collected available documentation on regional ITS system architectures that may have already been developed as well as documentation and other information on existing ITS deployments. This information was used to begin the process of developing a regional ITS architecture with the stakeholders of the region.

Having collected and assimilated information about the region into the draft Turbo Architecture database, we then conducted an intensive three day workshop (over a period of one week) with stakeholders representing all aspects of ITS.

The focus of the regional ITS architecture that we will have developed is to identify actual communication information exchange requirements between specific ITS elements in the regions. 

We first systematically identify the existing and future inventory of stakeholder ITS elements based on existing regional and corridor deployments, existing ITS architecture documentation, and stakeholder articulation of needs in the workshops. Next, we identify generic services through National ITS Architecture Market Packages, and where stakeholders indicate a need, we customize those Market Packages for specific applications (existing, planned (i.e. "programmed") or future) identified by the stakeholders. This customization identifies information exchange at the architecture flow level. Finally, we roll-up all information exchange requirements at the architecture flow level for each ITS entity in the region, and review this with the stakeholders in a final 1-day architecture workshop.

The results are the (draft) consensus regional ITS architectures for New York, documented here.