National ITS Architecture and Maintenance TOPR 2 Task D.pdf

Task Order Proposal Request (TOPR)

Task Order # T-12-0002:

National ITS Architecture Evolution and Support

Contract: DTFH61-11-D-000XXX

COTR: Steve Sill, HOIT-1, 202-366-1603

Overall Task: Task Area D: V2x Cooperative Systems Engineering and Architecture Maintenance and Evolution.

Due Date for Proposal: September 12, 2011 (same as proposal submission)

Please refer to Task Order Procedures delineated in Section G of the contract for additional information on Task Order Proposal submission requirements.

No. of Copies Required: An electronic copy of the Task Order Proposal shall be emailed to the Contracting Officer and the Contracting Officer Technical Representative.

Proposed Task Order Start Date: TBD

Proposed Task Order End Date: TBD

FHWA Contacts: Carolyn Wilson, Contract Administrator, HAAM-20A, 202-366-0867

Note: This TOPR is being solicited under RFP No. DTFH61-11-R-00023. The work covered by this TOPR is being funded by the Intelligent Transportation Systems Joint Program Office (ITS JPO). The Government may award either a Cost-Plus-Fixed Fee (CPFF) Task Order or Firm- Fixed-Price (FFP) Task Order as a result of this TOPR. Proposals will be evaluated in accordance with the selection criteria stated herein.

The Government reserves the right to conduct discussions with the Offeror(s) if the Contracting Officer determines that discussions are necessary.

DESCRIPTION OF WORK

Background

This task order will comprise Task Area D (described in detail below) from the National ITS Architecture Evolution and Support contract for FY 2012 and 2013.

Task D: V2x Cooperative Systems Engineering and Architecture Maintenance and Evolution

Task Objectives: The objectives of the work requested for Task D: V2x Cooperative Systems Engineering and Architecture Maintenance and Evolution are the following:

1. Support the ITS cooperative systems Engineering Program currently working to define a detailed level ITS architecture for vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) communications-centric ITS.

2. Integrate the detailed-level V2x cooperative systems architecture developed as part the ITS cooperative systems Systems Engineering Program into the National ITS Architecture Program; and maintain, upgrade, and enhance the functionality of that ITS architecture in the same manner as the National ITS Architecture.

3. Participate in international ITS standards and ITS architecture harmonization activities as appropriate to the maintenance and evolution V2x cooperative systems architectures.

Task Description: As a minimum, the following work shall be conducted:

The contractor shall coordinate with the developers of the V2x cooperative systems architecture as necessary to assure a smooth transition from the architecture developer into maintenance and support to the extent that this effort has not been completed by the time of award of the contract.

Specific activities may include:

1. Participating in and support international architecture and standards harmonization activities in support of the maintenance and evolution of the V2x cooperative systems architecture as appropriate.

2. Developing white papers and other documents and/or conducting briefings covering the V2x cooperative systems architecture and deployment issues at forums that may include the ITS America Annual Meeting, the Transportation Research Board Annual Meeting, et cetera, as directed by the U.S. DOT.

3. Maintaining the V2x cooperative systems architecture configuration control.

4. Remaining informed of relevant V2x cooperative systems developments and deployments that may require changes to the V2x cooperative systems architecture.

Fully developing descriptions of those changes, proposing such changes to U.S. DOT for approval, and implementation.

5. Soliciting recommendations for alterations to the National ITS Architecture from relevant stakeholder groups including U.S. DOT modal administrations; state, regional, and local governmental entities; and/or appropriate ITS, automotive, and surface transportation industry representatives.

6. Evaluating other proposed changes to the V2x cooperative systems architecture to determine their impact on other on-going U.S. DOT activities and integrate them into the V2x cooperative systems architecture.

7. Maintaining the integrity of the V2x cooperative systems architecture including the architecture definition. Providing web-based changes to reflect all formal updates.

8. Maintaining the V2x cooperative systems architecture website.

9. Evolving and maintaining current the existing Turbo Architecture software tool to accommodate the V2x cooperative systems architecture or developing and maintaining current a similar V2x cooperative systems architecture software tool.

STAFFING REQUIREMENTS

The following staff is deemed to be necessary for the successful completion of this task:

• Program Manager

• Principal Investigator

• Systems Engineer

• Software Engineer

• Communications Engineer

• Transportation/Other

The following is a description of the qualifications for proposed staff on this task.

Program Manager

The Program Manager must have substantial experience in managing complex systems engineering efforts. He/she must have a good understanding of current transportation issues, including traffic management, freight and fleet management, and transit management, as well as institutional, deployment and interoperability issues. He/she must be familiar with the broad aspects of Intelligent Transportation Systems (ITS) goals and technologies, and with the major ITS development programs. The Program Manager must be able to direct the efforts of a diverse set of technical disciplines and organizations and must have a proven track record for organizing and executing programs within budget and schedule. He/she must have good communication skills to clearly articulate program objectives and results and to achieve consensus within U. S.

DOT, the Architecture Team, and various stakeholder organizations. An offeror shall propose one and only one individual to serve in this particular discipline/area of expertise.

Principal Investigator

The Principal Investigator must be a skilled engineer from one of the critical disciplines who has technical knowledge and understanding in each of the key areas—systems engineering, communications engineering, transportation engineering, and software engineering. He/she must have a good understanding of current transportation issues, including traffic management, freight and fleet management, transit management, as well as institutional, deployment, and interoperability issues. The Principal Investigator must be familiar with the broad aspects of ITS goals and technologies, and with the major ITS development programs, and will be expected to operate closely with the Program Manager and be able to understand and articulate the issues and policies faced by the Program Manager. An offeror shall propose one and only one individual to serve in this particular discipline/area of expertise.

Systems Engineer(s)

The Systems Engineer(s) should be experienced in the development of system architectures, special software tools to support the development of an architecture, and be knowledgeable of all aspects of ITS. He/she should be familiar with traffic sensor types, sensor processing approaches, traffic and signal control systems, and with communications system applications and should have the technical expertise necessary to integrate these various technologies. He/she should be capable of the detailed understanding of the National ITS Architecture, as well as the Turbo Architecture software tool, and in general, be capable of integrating changes, modifications and new user services into the current National ITS Architecture. An offeror may propose one or more individuals to serve in this particular discipline/area of expertise.

Software Engineer(s)

The Software Engineer(s) should be familiar with the various software languages and data base techniques that are used by the National ITS Architecture. He/she must be capable of defining software system designs, sizing, and evaluating the processing and storage requirements for these systems in support of the current National ITS Architecture. He/she should have current knowledge regarding the software implementation of current traffic management and signal control systems in support of the National ITS Architecture as well as the Turbo Architecture software tool. An offeror may propose one or more individuals to serve in this particular discipline/area of expertise.

Communications Engineer(s)

The Communications Engineer(s) must be knowledgeable of the various communications media and modulation techniques that support ITS applications. This includes terrestrial radio systems, satellite communications, beacon (IR and microwave) systems, cellular telephone, cable, and other localized signaling systems. The Communications Engineer(s) shall be capable of performing communications system performance studies, analyzing potential coverage areas, and evaluating the effectiveness and/or constraints on various user access protocols and information coding techniques. An offeror may propose one or more individuals to serve in this particular discipline/area of expertise.

Transportation/Traffic Engineer(s)

The Transportation/Traffic Engineer(s) must be familiar with traditional traffic management systems, signal control techniques, surveillance sensors, and sensor data processing. He/she must also be familiar with advanced traffic management system approaches, such as video traffic surveillance, sensor and probe vehicle data fusion, changeable message signs, predictive/adaptive traffic management and control, and advanced traveler information systems.

An offeror may propose one or more individuals to serve in this particular discipline/area of expertise.

REPORTING REQUIREMENTS

The contractor is required to provide monthly progress reports addressing work completed, forecasts, and hours expended. The contractor shall furnish an electronic copy of a monthly progress report to the COTR and the Contract Administrator, on or before the 15th of the month following the calendar month being reported.

Each report shall contain concise statements covering the work performed during the previous calendar month by subtask. Additional specific items to be covered in the monthly report must include:

• Meetings Attended

• Task Order Funding Status Update

• Work to be Accomplished during Next Reporting Period

• Issues Encountered

Quarterly progress reports include the same information detailed above for the monthly progress reports. In addition to this material, the quarterly progress reports must include a table of the hours and diagrams of funding expended on the task order during the three month reporting period.

DELIVERY/PERFORMANCE SCHEDULE

Deliverables covering this task shall include:

• Monthly progress reports by the 15th of the following month

• Quarterly progress reports

• Quarterly progress briefings for the COTR

• Material progress report input for ITS JPO program reviews

• Participate in and support international architecture and standards harmonization activities in support of the maintenance and evolution of the V2x cooperative systems architecture as needed.

• Developing white papers and/or deliver briefings covering the V2x cooperative systems architecture and deployment issues at stakeholder forums.

• Document maintenance of the V2x cooperative systems architecture configuration control.

• Develop descriptions of changes to the V2x cooperative systems architecture resulting from V2x cooperative systems developments and deployments; propose such changes to U.S. DOT for approval, and implementation.

• Solicit and document recommendations for alterations to the National ITS Architecture from relevant stakeholder groups including U.S. DOT modal administrations; state, regional, and local governmental entities; and/or appropriate ITS, automotive, and surface transportation industry representatives.

• Maintain the integrity of the V2x cooperative systems architecture including the architecture definition and maintain the V2x cooperative systems architecture website to reflect all formal updates.

• Maintain and update the current the existing Turbo Architecture software tool to accommodate the V2x cooperative systems architecture or developing and maintaining current a similar V2x cooperative systems architecture software tool.

Informational Note: All electronic and information technology deliverables rendered under this task order must comply with Section 508 of the Rehabilitation Act and the Access Board Standards available for viewing at http://www.section508.gov. Unless otherwise indicated, the contractor represents by signature on this task order that all deliverables comply to the best of their ability with the Access Board standards.

PAYMENT OF FEE

The Government will pay the Contractor up to the negotiated amount of the fee stated in the task order upon the timely and satisfactory completion of all work requirements under the order.

ADDITIONAL TASK ORDER PROPOSAL INSTRUCTIONS

Travel and Other Direct Costs are anticipated under this task order. Travel is not expected to exceed $25,000 with Equipment/Materials not expected to exceed $4,000 each year for FY 2012 and FY 2013.

Level of Effort:

The estimated level of effort for Task Area D for FY 2012 and FY 2013 by year is given below.

Labor Category Task Area D Program Manager 450 hours Principal Investigator 600 hours Systems Engineer(s) 1,750 hours Communications Engineer(s) 200 hours Transportation Engineer(s) 800 hours Software Engineer(s) 200 hours Administrative 190 hours Total 4,190 hours a year