19.06.2014 Views

Strategic Deployment Plan - sacog

Strategic Deployment Plan - sacog

Strategic Deployment Plan - sacog

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5.3.2 Other Committees Involved<br />

Other committees are also in place to further aid in the maintenance process. The<br />

committee names and responsibilities are listed below:<br />

• ITS Partnership –Guide the direction and development of ITS deployment in<br />

the Sacramento Region.<br />

• Regional <strong>Plan</strong>ning Partnership – Ensure consistency of architecture with<br />

planning objectives.<br />

5.4 Frequency of Updates<br />

It is important that the Sacramento Regional ITS Architecture be kept up to date in order to guide<br />

ITS planning and deployment in the region and to keep within the intent of federal requirements.<br />

The most effective way to ensure that a regional ITS architecture stays up to date is to establish a<br />

regular schedule for updates. For this reason, the Sacramento Regional ITS Architecture will be<br />

updated at regularly scheduled intervals, in coordination with the Metropolitan Transportation<br />

<strong>Plan</strong>. The Metropolitan Transportation <strong>Plan</strong> is updated every three years. The Sacramento<br />

Regional ITS Architecture (including the Tahoe Regional ITS Architecture) will be updated six<br />

months in advance of the Metropolitan Transportation <strong>Plan</strong>.<br />

It is also noted that the updates of the Sacramento Regional ITS Architecture will require<br />

resources, whether the intention is to perform the updates in­house or contract them out. These<br />

resources should be programmed in the overall work program. Currently, the stakeholders have<br />

agreed that updates to the architecture will be done using an outside consultant. Cost sharing of<br />

the updates will be established by the stakeholders prior to selecting a consultant.<br />

5.5 What Architecture Components will be Updated?<br />

The Sacramento Regional ITS Architecture consists of several lists and documents in various<br />

formats, including reports, databases, and graphics. As events occur that may result in changes<br />

to the architecture, the various components of the architecture should be updated accordingly in a<br />

systematic fashion. A change to one of the architecture components (for example, the addition of<br />

a project or a stakeholder) often requires other components of the architecture to be updated as<br />

well. This is known as dependencies between architecture components.<br />

To ensure that updates are made in all the necessary locations, Table 5.2 has been developed to<br />

assist the architecture maintainer. This table may be consulted by the maintainer to track key<br />

components of the Sacramento Regional ITS Architecture and to ensure that all parts of the<br />

Sacramento Regional ITS Architecture are updated appropriately. The table describes the<br />

different components of the Sacramento Regional ITS Architecture, their status, their location<br />

(name of the file, document or database where the component can be found), the file format (e.g.<br />

Word, Turbo, Visio Drawing, etc.) and their common dependencies. This will help the<br />

maintainer organize the architecture prior to updating and make sure that all of the necessary<br />

components are updated.<br />

All outputs in the architecture need to be reviewed to ensure that any dependencies which are not<br />

documented in the above table are followed through. For example, a change made to the list of<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

81 Final Report<br />

September 2005

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!