The Bay Area ITS Architecture can be modified as plans and priorities change, ITS projects are implemented, and the ITS needs and services evolve in the region. The Bay Area ITS
Architecture was developed with a ten-year time horizon. As the
Architecture is updated over time, it will be extended further into the future. The goal of maintaining the
Architecture is to keep an up-to-date regional ITS Architecture that is accessible and easily used for deploying ITS in the San Francisco Bay Area.
Responsibility for Maintaining the ITS Architecture
Just as a group of stakeholders were key to the development of the Bay Area ITS
Architecture, it is imperative that stakeholders stay involved in the on-going maintenance. Because changes can arise from many sources, and very likely will arise from sources outside the technical expertise of a single agency, it is
important for the maintenance committee to represent different
functional, technical and geographic areas. Representatives from traffic, transit, emergency management,
smart corridors and MTC comprise the
Maintenance Committee.
It is recommended that MTC continue to convene the Maintenance
Committee on an as-needed basis to advise MTC on maintaining the
regional architecture and other ITS policy and planning issues. In
the near term, the Maintenance Committee should focus on maintaining
the currency of stakeholder and project information in the
Architecture. It is recommended that MTC continue to take the lead role with overall responsibility and accountability for the Architecture maintenance.
The Maintenance Team has adopted a
procedure for submitting changes to the Architecture found here:
Method for Submitting and Approving Changes to the Architecture.
Currently, MTC is considering changes to
this maintenance approach to reduce the ongoing cost of keeping this
Architecture up-to-date. Options currently being considered
can be found in the Summary for
Policy-Makers.
