(San Moron Transportation Management System)

Construct a new regional Traffic Management Center in the San Moron Civic Center

This form needs to be filled out for all ITS projects. For all High Risk (Major) ITS projects, this completed form needs to be submitted to FHWA for review and approval prior to PE authorization (Phase 1 PE authorization).


For all High Risk (Major) ITS projects, a Systems Engineering Management Plan (SEMP), which includes the seven items below, must be submitted to FHWA for review and approval, prior to PE authorization for component detailed design (Phase 2 PE authorization). Required FHWA approvals are limited to High Risk (Major) ITS projects.


For guidance in filling out the seven items below, see last part of this exhibit.


1.       Identification of portions of the Regional ITS Architecture being implemented:

The portions of the ITS RA being implemented is the San Moron Transportation Management system. The subsystems involved are StateDOT D-22 Transportation Management System, San Moron Roadside Equipment, Sub-regional and Local City/County Fire Department Systems, Region Transit Operations System, and the 511 and Regional Archive System. The market packages involved are Public Transportation, Traveler Information, Traffic Management and Emergency Management. An information flow diagram can be found starting on page 69 in Appendix G of the Regional ITS Plan. All items are part of the Regional ITS Plan submitted to MPO in June 2004.


2.       Identification of participating agencies roles and responsibilities:

Currently, the participating agencies are City of San Moron, RT, StateDOT D-22 and key partner agencies of Titanium Valley ITS Program. The San Moron Police and Fire Departments and San Moron Emergency Operation Center are key stakeholders as well, Details of their roles and responsibilities are listed in Table 6, section 6.2 in the Regional ITS Plan submitted to MPO in June 2004. Roles and responsibilities will be further refined during the development of the Concept of Operations and included in the SEMP.


3.       Requirements definitions:

At a high functional level, the system shall have the ability to monitor and manage traffic flow at signalized intersections, modify the control of signals from a central location, communicate with other Transportation Management Center systems to transmit traffic information to other jurisdictions, monitor and diagnose field equipment remotely, and provide information related to traffic to the travelling public.

The requirements definitions will be further developed as part of the definition stage of the systems engineering process.


4.       Analysis of alternative system configurations and technology options to meet requirements:

The system engineer will undertake technology surveys, review similar systems, and possibly put together a request for information (RFI) from system suppliers. Interfaces to external partners will be pursued, e.g., Information Service Providers, public safety, other regional Transportation Management Centers. Emphasis will be put on use of off-the-shelf solutions. Alternative system configurations and technology options will be completely developed as part of systems engineering process.


5.       Procurement options:

Systems engineering technical assistance will be contracted to facilitate the development of a Concept of Operations, to define the requirements and the project architecture, to prepare the RFP for design and implementation, to assist in the review of proposals, to provide independent review services (verification and validation), and to generally provide technical assistance to the City during the life cycle of the ITS system. An ITS system development team (system integrator) will be secured with the RFP to perform the detailed design, develop any necessary custom hardware or software, integrate any COTS products and to verify the sub-systems and the system as a whole. Any infrastructure design and construction will be handled with standard PS&E approval and low-bid construction process. The procurement options will be further refined and documented in the Systems Engineering Management Plan (SEMP).


6.       Identification of applicable ITS standards and testing procedures:

The most applicable ITS standards are the National Transportation Communications for ITS Protocol (NTCIP) family of standards. The appropriate final ITS standards and testing procedures will be determined in the systems engineering process associated with High-Level Design determination, documented within the Interface Control Document (ICD).


7.       Procedures and resources necessary for operations and management of the system:

Additional staffing and/or training for the operations and management of the proposed facility will be initially addressed by the System Engineer and completed by the System Integrator.