home

meetings

contacts

Task No. 1, Project Management

The CONSULTANT shall provide a Project Manager who will act as the principal consultant contact for the DPW and other involved agencies. The designated Project Manager will be responsible for the completion of activities associated with the performance of this PROJECT, including the requirements and alternative analyses, system recommendation, conceptual design, and operations and maintenance and strategic plans. All required products must be delivered to DPW in a timely manner to the satisfaction of the DPW and the affected agencies. Additional responsibilities include the managing of project planning activities and the tracking of costs and resources associated with each aspect of the PROJECT.

The Project Manager shall oversee and participate in the day?to-day activities of the PROJECT and shall, therefore, have no concurrent assignments that would interfere with the successful and timely completion of the work related to the PROJECT.

1.1 Project Coordination

The CONSULTANT shall coordinate technical design activities with the involved public and private agencies for each system component of this PROJECT. This will include, but not be limited to, the following.

• Coordination with other consultants involved with projects in the Gateway Cities Forum area. These projects shall include, but not be limited to, the I-5 Major Investment Study, the I-105 and I-710/Atlantic Boulevard Corridors Traffic Signal Synchronization and Bus Speed Improvement Projects, and the I-5 Corridor Intercounty Smart Street Feasibility Study;
• Coordination with public and private agencies involved with local and regional ITS projects including Caltrans, DPW, MTA, and the I-5/Telegraph Road Corridor cities to avoid duplication of effort in design and construction;
• Coordination with other regional and sub-regional projects which may affect this PROJECT such as Project IMAJINE, the MTA's TMC Coordination Study, the San Gabriel Valley Signal Synchronization O&M Pilot Project, and any other Southern California Priority Corridor projects such as the Showcase Project;
• Coordination with the activities and projects of ITS Committees which may affect this PROJECT such as the Los Angeles/Ventura ITS Coordinating Committee and the Southern California ITS Priority Corridor Steering Committee;
• Participation in peer group meetings with CONSULTANTS in other forums to help resolve compatibility issues; and
• Participation in and providing technical input to the Gateway Cities? Public Works Officers (PWO) Subcommittee when requested to help resolve institutional issues.

1.2 Attend Project Meetings/Make Project Presentations

The CONSULTANT shall attend PROJECT meetings with DPW, MTA, Caltrans, and affected agencies or organizations as deemed necessary by the DPW to accomplish the tasks and subtasks of this phase. The CONSULTANT will also be required to make technical presentations, including the use of presentation materials and the distribution of handouts, as needed at monthly Gateway Cities' PWO or Signal Subcommittee meetings, DPW staff meetings, and any other meetings as requested by the DPW or the affected agencies.

The CONSULTANT shall obtain prior approval from the DPW on any presentation and handout materials to be distributed at any technical presentation of the PROJECT. The DPW shall be provided with a copy of the distributed materials.

The CONSULTANT shall prepare meeting minutes for any PROJECT meetings and distribute a copy to meeting participants. Meeting minutes shall summarize each discussion and action item.

Deliverables: 1.2.1) Presentation of material and handouts; and 1.2.2) meeting minutes.

1.3 Create and Maintain Project Web Page

The CONSULTANT shall provide and maintain a web page for the PROJECT. The web page shall be primarily accessed through the CONSULTANT's web site home page. Direct access to this web page from the DPW's web site shall also be provided. The web page shall be in a prominent location in the CONSULTANT's web site home page and the title of the web page shall be the name of the PROJECT. Prior to developing the web page software, the CONSULTANT shall submit to the COUNTY for review and approval the screen layout of the web page and all sub-pages.

The primary web page shall contain a brief description of the PROJECT. The description shall contain, at a minimum, information on the PROJECT limits, the involved agencies, the PROJECT objectives, and the DPW and CONSULTANT contact persons for the PROJECT. The web page shall also contain sub-pages with additional PROJECT information as follows:

• PROJECT status sub-page. This page shall contain a summary of the current status of the PROJECT. This information shall be updated monthly, at a minimum. This sub-page shall also contain downloadable, electronic files of the agenda and minutes of the most recent meeting as well as a copy of any current deliverable(s). Information on the date, time, and location of upcoming PROJECT related meetings within the next month shall be included.
• Documents sub-page. This page shall contain downloadable, electronic files of all final deliverables.

The CONSULTANT shall be responsible for maintaining the web page throughout the duration of the PROJECT and reviewing/updating the web site monthly, at a minimum. Prior to each update of the web page or sub-pages the CONSULTANT shall get approval from the DPW for the information to be posted.

Deliverables: 1.3.1)Screen layout of the web page and sub-pages; 1.3.2) Web site address.

1.4 Prepare Project Reports

The CONSULTANT shall prepare and submit written monthly progress reports and a final report to the DPW detailing the status of work being performed by the CONSULTANT. These reports shall be in a form acceptable to the MTA as part of its Quarterly Narrative Report. This report shall include, but not be limited to, a narrative of the tasks accomplished in that month, a review of any incomplete tasks and the reasons why they were not completed, an outline of the tasks anticipated to be accomplished in the next month, a summary of problems which occurred during the month, any anticipated problems, an updated PROJECT schedule, a list of outstanding issues and deliverables and the current status of those issues and deliverables, an invoice as required by this Agreement, and a summary of the percent completion for each task of the PROJECT.

The CONSULTANT shall also prepare claims, invoices, billings, and other financial information for review and approval by the DPW, as required by the Agreement.

Deliverables: 1.4.1) Monthly progress reports and final report; and 1.4.2) Financial reports, billings, and invoices.

Task No. 2, Stakeholders and Operational Objectives

The CONSULTANT shall identify primary agency stakeholders and potential participating stakeholders and users and their operational objectives relative to the five major system components of the PROJECT and future ITS elements to be integrated into the system.

The Consultant shall prepare individualized City Reports prior to the predesign meetings. Each report shall be tailored to each city and contain information on the City's existing traffic signal infrastructure and traffic control system, if applicable. The Consultant shall carry out an inventory of existing infrastructure for the three cities not part of the I-105 project and use previous work for the other agencies. The report shall contain a summary of the traffic signal infrastructure, any traffic control system deficiencies, and a description of potential upgrades to the City's infrastructure and system. The report shall also discuss the general merits and possible benefits and costs associated with those potential upgrades. This report shall be detailed enough so as to enable the CONSULTANT to develop a complete and comprehensive list of user and functional objectives for this PROJECT.

The CONSULTANT shall schedule and conduct PROJECT pre-design meetings with each of the primary agency stakeholders and potential participating stakeholders for the purpose of, but not limited to 1) identifying primary agency stakeholders for the operation and management of the system and other potential participating stakeholders and users that could benefit from the PROJECT; 2) identifying agency and stakeholder's operational objectives and user and system functional performance requirements; 3) obtaining design standards; 4) obtaining pertinent plans and the status of any project which may affect this PROJECT; and 5) discussing impacts on staffing and operations, management and maintenance costs.

Deliverables: 2.1) Draft Stakeholders' Operational Objectives Report; 2.2) Final Stakeholders' Operational Objectives Report; 2.3) Individual City Reports

Task No. 3, Requirements Analysis

3.1 ATMS User Requirements

The CONSULTANT shall prepare a User Requirements document which will define the user operational and functional requirements of the ATMS and include those aspects of the PROJECT related to the overall integration of the systems in the PROJECT and in the region. These documents will identify the system users and the desired system operations and functions. The document shall be complete, comprehensive, and provide enough information needed to proceed to the next task (System Functional Requirements). This document shall include, but not be limited to, the following information.

• Operational requirements;
  • Data
  • Future ITS elements
  • Information exchange
  • Level of control
  • Modes of operation
  • Security/access
• Inter-jurisdictional requirements;
• O&M requirements;
• Staffing and training requirements;
• Cost requirements; and
• Public relations.

The CONSULTANT will use the I-105 Corridor Traffic Signal Management and Control System (TSMACS) User Requirements as a starting point and modify the requirements using the findings of Task No. 2.

The CONSULTANT shall utilize any pertinent information obtained from other projects such as Project IMAJINE, where appropriate, for this PROJECT to avoid duplication of effort and unnecessary additional work and expense.

Deliverables: 3.1.1) Draft ATMS User Requirements Report; 3.1.2) Final ATMS User Requirements Report

3.2 ATMS Functional and Local City Control Site Requirements

Based on the User Requirements (Task No. 3.1), the CONSULTANT shall prepare the ATMS Functional Requirements by modifying the I-105 Corridor TSMACS Functional Requirements. This document shall identify the System functional requirements as it relates to the PROJECT user needs.

These requirements shall also contain recommendations on upgrades to the existing vehicle detection systems including the installation of new system detectors as necessary for full implementation of the ATMS and Integrated Systems.

This document shall be complete, comprehensive, and provide enough information to proceed to the next tasks (High Level Design Definition, Alternatives Analysis and Conceptual Design). The System Functional Requirements shall address, but not be limited to, the following requirements.

• Needs/requirements of existing systems;
• System performance;
• Equipment and technology;
• Availability of technology;
• Adaptability;
• Interoperability;
• Expandability to provide additional ITS elements;
• Implementation costs;
• Operations;
• Maintenance;
• System Interface;
• Existing infrastructure;
• Reliability;
• Flexibility;
• Extensibility;
• National and International Standards, such as National Transportation Communications for ITS Protocol (NTCIP); and
• Scalability.

The CONSULTANT shall utilize any pertinent information obtained from other projects, such as Project IMAJINE, where appropriate, for this PROJECT to avoid duplication of effort and unnecessary additional work and expense.

In addition, the CONSULTANT shall prepare requirements which define the user operational and functional requirements for the following.

• Typical local city control site requirements, specifications and furnishings; and;
• Typical local city control site computer hardware and software, not included in other components.

This document will begin by identifying the system users and the desired system operation and function for the typical local city control site. The CONSULTANT shall use the I-105 Corridor Local City Control Site Facility and Computer System User Requirements and modify these requirements to address the needs of this PROJECT.

Based on the User Requirements, the CONSULTANT shall go on to prepare the Functional Requirements defining the following:

• Typical local city control site equipment and furnishings; and
• Local city control site computer hardware and software, not included in other PROJECT components.

This document will identify the required functions for the hardware, software, and furnishing for the typical local city control site. This document shall identify the computer system functional requirements not completed under any other task that is required to provide a fully functional local city control site. This document shall be complete, comprehensive, and provide enough information to proceed to the next tasks (High Level Design Definition and Conceptual Design). The report shall include, but not be limited to, the following requirements.

Typical Local City Control Site

• Function;
• Space;
• Functional adjacency;
• Site development; and
• Staffing and training.

Computer System

• System performance;
• Equipment and technology;
• Availability of technology;
• Adaptability;
• Interoperability;
• Implementation costs;
• Operational;
• Computer system maintenance;
• System Interface(s);
• Existing infrastructure;
• Reliability;
• Flexibility; and
• Extensibility.

The CONSULTANT shall use the products of the I-105 Corridor Local City Control Site Facility and Computer System Functional Requirements and modify the requirements to address the needs of this PROJECT.

Additionally, the CONSULTANT shall build on previous work undertaken by related projects and committee work, and where applicable, make use of these completed work products to avoid any unnecessary work or duplication of effort in this assignment.

Deliverables: 3.2.1) Draft ATMS Functional and Local City Control Site Requirements Report

3.3 Integration System User Requirements

The CONSULTANT shall prepare a User Requirements document that defines the Transportation System Integration User Operational and Functional Requirements. This document will identify the system users and the desired system operation and function with respect to system integration. This document shall be complete, comprehensive, and provide enough information needed to proceed to the next task (System Functional Requirements). This document shall include, but not be limited to, the following.

• Operational requirements;
  • Data
  • Future ITS elements
  • Information exchange
  • Level of control
  • Modes of operation
  • Security
  • Functional requirements;
  • Interjurisdictional requirements;
  • Maintenance requirements;
  • Staffing and training requirements;
  • Cost requirements; and
  • Public relations/political considerations.

The CONSULTANT will modify the I-105 Corridor Integration System User Requirements using the findings of Task No. 2 as a starting point.

The CONSULTANT shall utilize any pertinent information obtained from other projects, such as Project IMAJINE, and the East San Gabriel Valley Pilot Project where appropriate, for this PROJECT to avoid duplication of effort and unnecessary additional work and expense.

Deliverables: 3.3.1) Draft Integration System User Requirements Report. 3.3.2) Final System User Requirements Report.

3.4 Integration System Functional Requirements

The CONSULTANT shall prepare a Transportation Integration System Functional Requirements document by modifying the I-105 Corridor Integration System User Requirements to meet the needs of this PROJECT's User Requirements (Task No. 3.5). This document shall identify the integration system functional requirements as it relates to the I-5/Telegraph Road Corridor system integration user needs. This document shall be complete, comprehensive, and provide enough information to proceed to the next tasks (High Level Design Definition, Alternatives Analysis and Conceptual Design) and shall include, but not be limited to, the following requirements.

• System performance;
  • Interface requirements between system components
  • Interface protocol standards
  • Interface requirements between systems within and outside the forum area
• Equipment and technology;
• Availability of technology;
• Adaptability;
• Interoperability;
• Expandability;
• Implementation costs;
• Operation;
• Maintenance;
• Existing infrastructure;
• Reliability;
• Flexibility; and
• Extensibility.

Deliverables: 3.4.1) Draft Integration System Functional Requirements Report.

3.5 Communications Requirements

The CONSULTANT shall obtain the information needed to identify the Communication System User and Functional Requirements. This may require may require follow-up visits to individual cities and agencies to discuss issues and concerns. This will also require field reviews to verify existing communication infrastructure. As part of this task, the CONSULTANT shall take into account any applicable information gathered on the Existing Conditions Section of the IMAJINE Project Report and the I-105 Corridor Project. Based on the input received from the corridor agencies, prior reports, requirements gathered from previous tasks and field reviews, the CONSULTANT shall prepare a Communications System User and Functional Requirements Report. This document shall identify the needs and concerns of the I-5/Telegraph Road Corridor agencies with respect to the communications infrastructure. This report shall also document the I-5/Telegraph Road Corridor communications requirements based on the transportation system design. This document shall include, but not be limited to, data communication requirements for any recommended system and component included in this system such as the following.

• The ATMS;
• City work stations/control sites;
• Future ITS field elements, such as CCTV, HAR, and CMS;
• Integration System Requirements;
• Nontransportation-related issues;
• Public relations issues;
• O&M issues;
• Expandability;
• Bandwidth requirement;
• Reliability;
• Redundancy;
• Diversity;
• Performance requirements;
• Communications system access points; and
• Potential bottlenecks and weak links.

Deliverables: 3.5.1) Draft Communications System Requirements Report.

3.6 Final System Requirements

The Consultant shall gather all draft requirements and comments and present the revised final versions of all user and functional requirements in a Final Report.

Deliverables: 3.6.1) Final System Requirements Report.

Task No. 4, High Level System Design

4.1 High Level System Design Report

Based upon the User and System Functional Requirements definition, the CONSULTANT shall prepare a Conceptual High Level Design definition of the systems in the complete project. This will address the following project elements:

ATMS

Based upon the User and System Functional Requirements definition, the CONSULTANT shall prepare a Conceptual High Level Design definition of the ATMS. This shall include, but not be limited to, the following.

• Development of a system architecture;
• Definition of the interface requirements; and
• Definition of the overall functionality of the systems.
• Discussion of necessary upgrades to existing vehicle detection systems and the installation of new system detection to the extent necessary to provide a fully operational ATMS

Local City Control Site Report

Based upon the User and Functional Requirements, the CONSULTANT shall prepare a Conceptual High Level Design definition of the typical local city control site. This shall include, but not be limited to, the following.

• Development of a system architecture;
• Definition of interface requirements; and
• Definition of the overall functionality of the system.

Additionally, this Task shall also include a preliminary schematic indicating a proposed layout of a typical layout for a local city control site.

Integrated Systems

Based upon the User and System Functional Requirements defined in the previous tasks, the CONSULTANT shall prepare a Conceptual High Level Design definition of the Transportation Integration System. The high level design definition shall include, but not be limited to, the following.

• Development of a logical system architecture;
• Definition of the interface requirements; and
• Definition of the overall functionality of the system.

Deliverables: 4.1.1) Draft High Level Design Definition Report; and 4.1.2) Final High Level Design Definition Report.

Task No. 5, Alternatives Analysis

5.1 ATMS Analysis

Based on the Functional Requirements and the High Level Design definition, the CONSULTANT shall perform an alternatives analyses to evaluate different ATMS and vehicle detection systems, where necessary, for use in the I-5/Telegraph Road Corridor. The CONSULTANT review shall include but not be limited to, existing ATMS owned or being developed by the COUNTY and affected agencies for use in this traffic forum to determine if they can meet the User and Functional Requirements as identified in the previous tasks. The CONSULTANT will use the findings of the Commercial off the Shelf Traffic Control System Analyses reports currently being completed by the South Bay Part III and I-105 Corridor projects as a starting point for this task. Once this review is complete the CONSULTANT shall update this report and tailor it to meet the requirements as developed in Tasks 3.1, 3.2, and 3.4. Additionally, the CONSULTANT shall also identify any new suppliers of systems, or any new systems provided by the surveyed suppliers that would be candidates for analysis. Any work beyond identifying these systems would be outside of the scope of this PROJECT.

A comparison matrix shall be prepared to determine the benefits and limitations of each system to be evaluated. This analysis will address, at minimum, the following.

• Conformance to User Requirements;
• Conformance to Functional Requirements;
• Software Requirements;
• Hardware Requirements;
• Communication Requirements;
• System performance;
  • Present
  • Future
• Estimated capital cost;
• Estimated O&M life cycle costs;
• Liability and risk;
• Maturity of technology;
• Adaptability;
• Interface requirements and ability;
• Licensing issues;
  • Ownership
  • Cost
• Staffing and training;
• Expandability;
• Flexibility;
• Control processes;
• Interoperability;
• System support capabilities;
• System Maintenance Requirements; and
• System readiness.

Additionally, the CONSULTANT shall include in its criteria for analysis that any required equipment shall be readily available, current state-of-the-art, off?the-shelf, and manufactured from well-established and reputable suppliers.

With respect to the detection systems, the analysis shall comprise a comparison of technologies and identification of functionality rather than an evaluation of specific products from individual suppliers.

The development of this PROJECT component shall clearly indicate which requirements, if any, cannot be met by each system or technology evaluated. The completed analysis should show that the recommended system is the most effective, reliable, and economical system available.

Deliverables: 5.1.1) Draft Systems Alternatives Analysis Document; 5.1.2) Final Systems Alternatives Analysis Document

5.2 Communications Analysis

Based on the User and Functional Requirements, the CONSULTANT shall perform an alternatives analyses which will evaluate several different communication alternatives for use in the I-5/Telegraph Road Corridor. It is anticipated the final system chosen will be a hybrid system, consisting of a combination of numerous communication types based upon the requirements of the component with which communication is required or desired. These elements will be combined in the most reliable, economical, and efficient way.

A comparison matrix shall be prepared to determine the benefits and limitations of each system. This analysis will address, at minimum, the following.

• Hardware requirements;
• Bandwidth requirements;
• Data transfer requirements;
• Estimated capital cost;
• Estimated O&M life cycle costs;
• Liability and risk;
• System performance;
• How well it satisfies current and future needs;
• Maturity of technology;
• Staffing and training requirements;
• Availability;
• Expandability;
• Flexibility;
• Control processes;
• Potential bottlenecks and weak links;
• Reliability; and
• Marketing potential.

Additionally, the CONSULTANT shall include in its criteria for analysis that any required equipment shall be readily available, current state-of-the-art, off?the-shelf, and manufactured from well established and reputable suppliers.

As part of this task, the CONSULTANT shall also explore the possibility of using existing fiber communication network installed by Caltrans.

Deliverables: 5.2.1) Draft Communication System Alternatives Analysis Report; and 5.2.2) Final Communication System Alternatives Analysis Report.

Task No. 6, Recommendations

6.1 Recommendations

The CONSULTANT shall prepare a comprehensive list of recommendations resulting from the design and analysis work carried out in the previous tasks. The areas to be addressed shall be:

ATMS

Based on the results of the ATMS Alternatives Analyses (Task No. 5.1) and careful consideration of the variables involved, the CONSULTANT shall prepare a detailed technical recommendations for the best ATMS's and vehicle detection system to be used in the I-5/Telegraph Road Corridor. The recommended ATMS's may involve the replacement and/or maintenance and integration of any existing traffic control systems. This working paper shall include a comprehensive discussion on why the particular system was selected and a discussion of the methodology used to make the recommendation.

Recommendations shall be for the development of "open systems" and shall include a review of potentially suitable systems for use in this forum. This development shall occur in close coordination with the I-105 Project, Project IMAJINE, and any applicable Southern California Priority Corridor ITS Steering Committee Projects, Los Angeles/Ventura County ITS Coordinating Committee Projects, and Regional Traffic Forum Projects throughout Los Angeles County to ensure a seamless environment with a common interface. The CONSULTANT shall build on previous work undertaken by these projects and committees and where applicable, use completed work products to avoid unnecessary work or duplication of effort in this assignment.

(Note: If an existing ATMS is not recommended as a result of this analysis and the CONSULTANT recommends the development and design of new system(s), the deliverable for this task shall include the reasons for these recommendations. In this instance, it is the County's intent to conduct a competitive solicitation process for the selection of a contractor for the design, development, and other services related to the implementation and integration of these new systems. CONSULTANT shall be precluded from participating in this solicitation.)

Local City Control Site

For the three cities not part of the I-105 Corridor Project, the CONSULTANT shall recommend the locations of the local city control sites and computer systems to be implemented with this PROJECT.The results of the I-105 Corridor Local City Control Site and Computer System Recommendations will be used as a starting point to identify variances from the typical layout for the remaining within the I-5/Telegraph Road Corridor. The computer systems to be recommended in this task shall include any necessary local city control site computer systems not previously covered herein for the I-5/Telegraph Road Corridor. The recommendation made by the CONSULTANT shall consider known effective means of satisfying the functional requirements. The analysis should show that the recommended sites are the most effective, reliable, and economical available. Therefore, a discussion on methodology is essential.

The recommendation should also identify the impacts, if any, for all seven jurisdictions in the project on the existing facilities in placing the local city control site at the recommended locations.

Communications

Based on the results of the Communication System Alternatives Analysis (Task No. 5.2) and careful consideration of the variables, the CONSULTANT shall prepare a detailed technical recommendation for the best Communication System to be used in the I?5/Telegraph Road Corridor. This report shall include a comprehensive discussion on why this combination of communication elements was selected and a discussion of the methodology used to make the recommendation.

Deliverables: 6.1.1) Draft System Recommendations Report; and 6.1.2) Final Systems Recommendation Report.

Task No. 7, Conceptual Design Report

7.1 Conceptual Design Report

At the completion of Task Nos. 1-6 of the PROJECT, the CONSULTANT shall prepare a detailed, comprehensive Conceptual Design of the I-5 Telegraph Road Systems accompanied by an Executive Summary report.

This Conceptual Design Report shall include maps, graphs, and subsystem technical reports summarizing the final conceptual recommendations for each system and be in a form detailed enough such that it can be used as the foundation for the detailed design.

The CONSULTANT will also be required to account for system elements in other consultant contracts which may affect CONSULTANT'S system design.

It is envisioned this report will be concise and easily understandable by non-technical personnel.

The areas to be addressed by the Conceptual Design are as follows:

ATMS

The CONSULTANT shall prepare a High Level Conceptual Design of the selected ATMS, vehicle detection system and its associated components as agreed upon by the DPW, MTA, and the affected agencies. This Conceptual Design shall consist of a detailed and comprehensive technical working paper defining the system architecture, interface, software, and hardware requirements, and the overall functionality of the system. This document should also include the conceptual design of the computer system hardware, and any associated peripherals, software, and software modules for the complete ATMS. System components shall be NTCIP compliant as far as each component has been defined. The Conceptual Design shall identify the amount, type (technology), and location of the vehicle detectors that form part of the Vehicle Detection System.

In addition to the items indicated above, the Conceptual Design shall include, but not be limited to, a configuration management plan, construction staging plans, and cut over plans (if necessary) showing the transition from any existing system(s) to the new system for each PROJECT component.

Local City Control Site

The CONSULTANT shall prepare a Conceptual Design of the typical local city control site, and associated equipment, furnishings and computer system(s) as agreed upon by the DPW, MTA, and the affected agencies as part of Task 6.1. The I-105 Corridor Local City Control Site and Computer System Conceptual Design can be used as a starting point. The Conceptual Design shall consist of a comprehensive technical working paper defining preliminary site locations and space requirements, system architecture, staffing, training, and interface requirements, and the overall functionality of each computer system and typical local city control site. The CONSULTANT shall discuss the adaptability of the typical Local City Control Site Conceptual Design to each of the affected local agencies of this PROJECT. For those agencies requiring changes to conform to the typical Local City Control Site Conceptual Design, the CONSULTANT shall-provide recommendations on necessary alterations to these proposed work spaces to provide the needed functionality. The CONSULTANT will also be required to account for other computer and component system requirements, such as those involved with other projects such as IMAJINE, and elements in other consultant contracts that may affect CONSULTANT'S design.

In addition to the items indicated above, the Conceptual Design shall include, but not be limited to, a configuration management plan, and cut over plans (if necessary) showing the transition from the existing to the new system for each system component.

This Conceptual Design document shall be in a form and detailed enough such that it can be used as the foundation for the detailed design.

Integration Systems

The CONSULTANT shall prepare the Conceptual Design of the Transportation Integration System component and its associated modules. This Conceptual Design shall consist of a detailed and comprehensive technical working paper defining the system architecture, interface requirements, and the overall functionality of the system, and a user interface prototype. The CONSULTANT will also be required to account for system elements in other consultant contracts that may affect CONSULTANT'S system design. System components shall be NTCIP compliant as far as each component has been defined.

Recommendations made by the CONSULTANT shall be for the development of "open systems" and shall be made after careful review of potentially suitable systems for use in this corridor. This includes completed systems or systems currently under development in other traffic corridors. This development shall occur in close coordination with the I-105 Corridor Project, Project IMAJINE, any applicable Southern California Priority Corridor ITS Steering Committee Projects, Los Angeles/Ventura County ITS Coordinating Committee Projects, and Regional Traffic Forum Projects throughout Los Angeles County to insure a seamless environment with a common interface.

In addition to the items indicated above, the Conceptual Design shall include, but not be limited to, a configuration management plan, construction staging plans, and cut over plans (if necessary) showing the transition from the existing to the new system for each system component.

Communications

The CONSULTANT shall prepare the High Level Conceptual Design of the selected Communication System and any associated components required to make the system operational, as agreed upon by the DPW, MTA, and the affected agencies. This Conceptual Design shall consist of a detailed and comprehensive technical working paper defining the system architecture, interface requirements, and the overall functionality of the system. The Conceptual Design shall provide for two-way communications between field controllers and office personnel. The CONSULTANT will also be required to account for system elements in other consultant contracts which may affect CONSULTANT'S system design. This Conceptual Design document shall be in a form and detailed enough such that it can be used as the foundation for the detailed design. System components shall be NTCIP compliant as far as each component has been defined.

If radio channels are proposed, the CONSULTANT must obtain the necessary approvals from the Federal Communications Commission before implementing the system. Any selected frequencies shall be free of any interference. A detailed radio path study must be prepared for every radio path in the entire system.

In addition to the items indicated above, the Conceptual Design shall include, but not be limited to, a configuration management plan, construction staging plans, and cut over plans (if necessary) showing the transition from the existing to the new system for each system component.

Deliverables: 7.1.) Draft Conceptual Design Report including Executive Summary

Task No. 8, Operations and Maintenance Plan

The CONSULTANT will be required to develop an Operations and Maintenance (O&M) plan for the proposed Conceptual Design of the PROJECT which provides a detailed breakdown of the total O&M costs including costs by jurisdiction as well as local and regional cost breakdowns, for the proposed system conceptual design.

At a minimum, the O&M plan must consider the required personnel skill levels and staffing costs, and the reoccurring and life cycle costs for capital facilities and space, equipment, material, supplies, procurement, and installation for the following:

• Recommended staffing plan (time of day, days of week) for operation of agency work stations and management of operations programs;
• Traffic signal control system and system loops infrastructure maintenance;
• Maintenance of other ITS field devices;
• Periodic operating system and software version upgrades;
• Periodic computer hardware replacement;
• Hardware and software technical support and maintenance;
• Computer database maintenance;
• Computer system configuration management;
• Telecommunications infrastructure operation and maintenance;
• Map database maintenance;
• Employee training; and
• Additional building maintenance, operations or communication costs to operate the agency and stakeholder work stations.

The costs shall be presented in annual terms, with total costs and breakdowns by jurisdiction, and in a clear and an easily understandable format, including graphs and charts, if necessary. The plan should be in a form which can be easily interpreted by both technical and non-technical personnel, such as city administrators and maintenance personnel. This plan shall also include a preliminary discussion on possible cost and resource sharing options, if any.

In addition, the O&M plan shall include a discussion on the system's potential for generating revenue, including potential annual revenue amounts, to offset the cost of operations and maintenance, such as the marketing of traffic data and surplus communications system capacity, and other forms of participation by the private sector.

Deliverables: 8.1) Draft Operation and Maintenance Plan Report; and 8.2) Final Operation and Maintenance Plan Report.

Task No. 9, Technical, Operational, and Institutional Issues

Upon completion of Task Nos. 1-8 of the PROJECT, the CONSULTANT shall prepare a document identifying major technical, operational, and institutional issues that have a potential for causing excessive delays or which may impede successful implementation of the PROJECT. This shall be based on the similar analysis carried out under the I-105 corridor project, but adapted to suit the particular situation of the I-5/Telegraph Road project. The document should provide a general discussion of each issue and should address mitigation approaches to ensure the successful and timely completion of this PROJECT. Individual issues to be addressed are as follows:

• Standards;
• Functional;
• Control;
• Architecture;
• Operational;
• Authority;
• Technology;
• Resource sharing;
• Responsibility;
• Interoperability;
• Standard Operating Procedures;
• Partnership Arrangements;
• Implementation;
• O&M Issues and Costs;
• Agency Coordination;
• Cost Sharing;
• Inter-jurisdictional;
• Staffing;
• Public Relations;
• Training; and
• Political.

The CONSULTANT shall address these issues in a comprehensive and detailed manner including appropriate mitigation measures.

Deliverables: 9.1) Draft Technical, Operational, and Institutional Issues Report; and 9.2) Final Technical, Operational, and Institutional Issues Report.

Task No. 10, City Concurrence

Based on the results of Task Nos. 87, 8 and 9, the CONSULTANT shall, with the assistance of the County, Gateway Cities Public Works Officers Signal Subcommittee and other agencies as appropriate, obtain city concurrence on the proposed Conceptual Design which will include the resolution of any outstanding Technical, Operational, and Institutional Issues. The CONSULTANT shall conduct a meeting with each primary agency to discuss the approval process and gain concurrence from these agencies on the proposed Conceptual Design. Meeting minutes will be produced indicating follow-up action items. Additional agency visits will be beyond the scope of the project.

This process shall include, if necessary, a demonstration of the system to be implemented with the PROJECT to obtain City concurrence. This demonstration shall include the integration prototype screens and a demonstration of an example traffic control system (with generic screens, not project specific).

Deliverables: 10.1) Letters/Resolutions indicating City Concurrence as appropriate. 10.2) Meeting Minutes

Task No. 11, Final Conceptual Design Report

The CONSULTANT shall use the results of Task No. 10 and to make appropriate changes to the Draft Conceptual Design Report provided in Task No. 7, and produce a Final Conceptual Design Report. This will not encompass significant changes in the Draft Conceptual Design. This will define the final system design and be in a form that will enable the initiation of Phase 2, Detailed Design.

Deliverables: 11.1) Draft Final Conceptual Design Report. 11.2) Final Conceptual Design Report.

Task No. 12, Strategic Implementation Plan

Building on the results of Task No. 11, the CONSULTANT shall work with the DPW, MTA, and affected jurisdictions to establish a Strategic Implementation Plan for the PROJECT. This plan shall include a comprehensive list of tasks anticipated to be completed in each of the phases 2-8 for each of the five identified components of the PROJECT. Each identified task must be accompanied by a brief description of the task's objective and a summary of how the CONSULTANT plans to achieve those objectives. Additionally, the description should also indicate deliverables and a list of the topics that will be addressed to successfully complete each task. The plan shall also include a comprehensive PROJECT budget, detailed enough for planning purposes, and a phased schedule of implementation for each component.

12.1 Scope of Work

The CONSULTANT shall prepare a Scope of Work document for phases 2-9 of this PROJECT that clearly describes, by individual tasks, the extent of the work to be performed. The Scope of Work document shall be organized by phases as described in the Introduction portion of this statement of work and shall include each component of this PROJECT as a separate, stand?alone item, as appropriate. The Scope of Work must include, but not be limited to, the following items.

• A listing of tasks and subtasks to be performed by the CONSULTANT for each phase and each component of the PROJECT;
• A description of the work to be performed for each task indicating what work will be performed within the task, what work is outside the scope of this PROJECT, e.g., what software will be developed by the CONSULTANT, and what software will be purchased. This description should also indicate what level of detail will be involved in the work to be completed for each task, by indicating which aspects of each task will be addressed; and
• A detailed description of the issues, topics, and parameters for each PROJECT component that will be considered when making a recommendation.
• A description of any agreements needed between the primary agencies in order to implement the PROJECT and provide for the operation and maintenance of the traffic control system. The CONSULTANT shall draft the scope of work for these agreements, if necessary.

Deliverables: 12.1.1) Draft Scope of Work Document; and 12.2.2) Final Scope of Work Document.

12.2 Project Budget

The CONSULTANT shall prepare a project budget indicating the anticipated use of funds. This PROJECT budget shall include, but not be limited to, an estimated cash flow chart by quarter and a breakdown of expenditures by task and subtask.

Deliverables: 12.2.1) PROJECT budget; and 12.2.2) cash flow chart.

12.3 Project Schedule

The CONSULTANT shall prepare a Project Schedule detailing the anticipated start and end dates of each task and subtask. The PROJECT Schedule shall include, but not be limited to, PROJECT milestones, schedule of deliverables, PROJECT duration, and the critical path. The PROJECT Schedule should also include appropriate agency review periods for each document and work product so as to provide a realistic estimation of the PROJECT's duration.

Deliverables: 12.3.1) PROJECT Schedule.

12.4 Strategic Plan Final Report

At the completion of Task 12 of the PROJECT, the CONSULTANT shall prepare a detailed, comprehensive report aggregating the information gathered in this task, including any recommendations as appropriate. This report shall be accompanied by an Executive Summary.

Deliverables: 12.4.1) Draft Strategic Plan Final Report; 12.4.2) Final Strategic Plan Final Report; and 12.4.3) Strategic Plan Final Report Executive Summary.