National ITS Architecture and Maintenance TOPR 1 Task A B C.pdf

Task Order Proposal Request (TOPR)

Task Order # T-12-0001:

National ITS Architecture Evolution and Support

Contract Number: DTFH61-12-D-000XXX

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

Overall Task: National ITS Architecture Evolution and Support

Subtasks: Task Area A: National ITS Architecture Evolution (Maintenance and Support) Task Area B: Deployment Support

Task Area C: Border Architecture Activities (Canada, Mexico, and other points of entry)

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, Contractor Administrator and the Contracting Officer Technical Representative (COTR).

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 have three subtasks comprising Task Areas A, B and C (described in detail below) from the National ITS Architecture Evolution and Support contract for FY 2012 and 2013. It is anticipated that by awarding a single task order for these 3 related task areas, the FHWA will simplify the overall administrative process including processing and approving the procurement request; staffing, reviewing, and placing the new task order on contract with applicable funding; and subsequently moving funds between subtasks as necessary to provide maximum utilization of the FHWA’s scarce resources.

Task A: National ITS Architecture Evolution (Maintenance and Support)

Task Objectives: The objectives of the work requested for Task A: National ITS Architecture Evolution (Maintenance and Support) are the following:

1. Support and manage the evolution of the National ITS Architecture to include changes due to deployment experiences, changes in requirements, and changes due to results from public and private sector ITS research programs and initiatives that will be integrated into the national transportation system and the National ITS Architecture.

2. Assist the U.S. DOT policymakers in defining policy consistent with the National ITS Architecture and in compliance with applicable surface transportation legislation (currently “SAFETEA-LU”) and applicable regulations including but not limited to 23CFR part 940 (“The Architecture Rule”). Ensure that the National ITS Architecture reflects any new federal policies that may be put into effect.

3. Maintain and upgrade the Turbo Architecture software tool and ensure that it conforms to the latest version of the National ITS Architecture.

4. Support the mapping of ITS standards to the National ITS Architecture and appropriately support elements of the ITS standards program to assure that this linkage remains consistent and robust.

5. Participate in international ITS standards and ITS architecture harmonization activities as appropriate to the maintenance and evolution of the National ITS Architecture.

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

The contractor shall provide advice, recommendations, and administrative and technical support to the U.S. DOT regarding issues that may specifically impact the National ITS Architecture, its maintenance and evolution. Specific activities may include:

1. Analyzing aspects of the National ITS Architecture program, attending specific ITS Joint Program Office (JPO) meetings and delivering required program status briefings and reports to the U.S. DOT.

2. Ensuring that necessary facilities, staff, and equipment required to effectively carry out the National ITS Architecture program objectives are available.

3. Providing the ITS JPO Architecture Program Manager strategic advice and recommendations concerning the direction and near-term future of the Architecture program.

4. Developing white papers and other documents and/or conducting briefings to address the

National ITS Architecture and deployment issues at forums that may include the ITS America Annual Meeting, the Transportation Research Board Annual Meeting, and others as directed by the ITS JPO Architecture Program Manager.

5. Providing the ITS JPO Architecture Program Manager technical advice and reviews of

ITS standards development, testing, and deployment efforts, especially as directly related to the National ITS Architecture.

6. Maintaining configuration control while addressing all updates to National ITS

Architecture documentation.

7. Remaining informed of relevant ITS developments and deployments that may require changes to the National ITS Architecture, proposing such changes when they are identified, and implementing them upon approval. As appropriate, 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.

8. Evaluating proposed changes to the National ITS Architecture to determine their impact on the National ITS Architecture itself and to other on-going U.S. DOT activities, and integrating them into the National ITS Architecture upon U.S. DOT approval.

9. Maintaining the integrity of the National ITS Architecture documentation set, especially the architecture definition. Providing CD-ROM versions of the National ITS Architecture to users upon request following all major updates. Providing web-based changes to reflect all formal updates to the National ITS Architecture.

10. Maintaining and enhancing the Turbo Architecture software tool as required to fully address upgrades to the National ITS Architecture definition and to respond to the FHWA Rule and FTA Policy on Architecture and Standards and other regulations/policies that may come into effect.

11. Ensuring that the Turbo Architecture software tool is consistent with the latest version of the National ITS Architecture and provide technical support as needed to users of the Turbo Architecture software tool.

12. Participating in National ITS Architecture-related activities within major U.S. DOT initiatives and research projects and integrate relevant elements into the National ITS Architecture.

13. Maintaining the National ITS Architecture website and all appropriate documentation, to include the latest versions of both the National ITS Architecture and Turbo Architecture.

Task B: Deployment Support

Task Objectives: The objectives of the work requested for Task B: Deployment Support is the following:

1. Provide ITS deployment support in the transportation planning process at the state, region, and Metropolitan Planning Organizations (MPOs) and on occasion, local levels.

2. Provide technical support in the maintenance and use of regional ITS architectures, and training support in the architecture and systems engineering process to users at the state and local level.

3. Participate in outreach and training efforts to explain and promote the use of the National ITS Architecture to Federal Highway Administration (FHWA) Resource Centers and division offices; and assist efforts to facilitate the use of the Architecture among state and local planners, implementers, integrators, and manufacturers.

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

The contractor shall provide overall support to the U.S. DOT in ensuring that the National ITS Architecture is considered in all local and national ITS deployments. The contractor shall provide limited training support to public sector (Federal) personnel and other users as may be directed by the Government. The contractor shall support architecture outreach efforts to U.S.

DOT Resource Centers and division offices, state and local implementers, other administrations within the U.S. DOT, and other stakeholders as required. Specific activities may include:

1. Providing technical assistance to the National ITS Architecture Field Support Team (AFST), FHWA division offices, other Federal employees, and FHWA contractors as needed to educate them on the National ITS Architecture and regional ITS architecture development, deployment, use, and maintenance. This may include ensuring they are consistent with requirements of applicable surface transportation legislation (currently “SAFETEA-LU”) and applicable regulations including but not limited to 23CFR part 940 (“The Architecture Rule”), the Federal Transit Administration (FTA) Policy on Architecture and Standards, and other regulations/policies that may come into effect.

2. Supporting further development and maintenance of the existing Regional ITS

Architecture Guidance Document. Coordinating with the FHWA and other FHWA contractors on any future architecture guidance documentation development.

3. Providing regional and project architecture technical reviews, including those that may be conducted on-site.

4. Evolve the architecture and systems engineering workshops, as well as the systems engineering process improvement reviews, to remain focused on current needs in the field using experience and lessons learned from the use and maintenance of regional ITS architectures and mainstreaming of systems engineering at the state, regional, MPO, and/or local levels. Using appropriate training methods including webinars and/or other innovative delivery techniques to appropriately balance training delivery costs and participant travel costs against the unique benefits of on-site training tailored to a specific region/site’s needs.

5. Presenting architecture and systems engineering workshops and systems engineering process improvement reviews at sites around the country and providing briefings on the process review findings and recommendations.

6. Developing white papers and other documents and/or conduct briefings encompassing a wide range of architecture topics including the relationship with the transportation planning process, regional and project architectures, V2x cooperative systems, and other current topics involving the National ITS Architecture.

7. Providing systems engineering process technical assistance.

8. Developing white papers and other documents and/or conduct briefings to address systems engineering and its relationship to the transportation planning process.

9. Facilitating workshops, charettes, meetings, and other forums that advance architecture use and maintenance and systems engineering mainstreaming.

Task C: Border Architecture Activities (Canada, Mexico, and other points of entry)

Task Objective: The objective of the work requested for Task C: Border Architecture Activities (Canada, Mexico, and other points of entry) is to continue to provide technical support to ITS architecture activities along the United States-Canada border and, to the extent possible, future ITS architecture activities along the United States-Mexico border. This may be expanded to include other surface transportation and air entry points, including ports.

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

The contractor shall provide advice, recommendations, and technical support to the U.S. DOT on issues associated with border architecture activities with Canada and with Mexico. Specific activities may include:

1. Engaging in activities that ensure consistency and integration of the U.S. National ITS Architecture with the ITS Architecture for Canada and the Mexico national ITS architecture.

2. Supporting the update and maintenance of the Border Information Flow Architecture with Canada.

3. Developing concepts of operation (CONOPS) and project architectures for ITS technology deployments for regions on both the United States-Canada border and United States- Mexico border.

4. Supporting international workshops and forums by providing technical assistance on border architecture elements specific to the respective regions.

5. Providing technical reviews and analyses of major ITS technology projects led or supported by FHWA in regions along the United States borders with Canada and Mexico.

6. Providing other technical support to emerging efforts on the United States borders with Canada and Mexico.

7. Providing support to any initiatives to develop border architecture(s) covering other surface transportation and air entry points, e.g. ports, into the U.S. as directed.

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 the entire 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

Subtask A deliverables include:

• Draft white papers and other documents and/or deliver briefings for stakeholders to address the National ITS Architecture and deployment issues as required.

• Draft advice papers for the ITS JPO Architecture Program Manager relaying strategic advice and recommendations concerning the direction and near-term future of the Architecture program.

• Conduct reviews of ITS standards development, testing, and deployment efforts leading to written technical advice for the ITS JPO Architecture Program Manager as required.

• Record configuration control of all updates to National ITS Architecture documentation.

• Document the maintenance and enhancing the Turbo Architecture software tool as required.

• Document the maintenance of the National ITS Architecture website as required.

Subtask B deliverables include:

• Written reports recording technical assistance given to the National ITS Architecture Field Support Team (AFST), FHWA division offices, other Federal employees, and other stakeholders covering the National ITS Architecture and regional ITS architecture development, deployment, use, and maintenance.

• Conduct regional and project architecture technical reviews.

• Update the architecture and systems engineering workshops using appropriate training methods including webinars and/or other innovative delivery techniques.

• Presenting architecture and systems engineering workshops and systems engineering process improvement reviews as needed at sites nationwide.

• Develop white papers and/or conduct briefings encompassing a wide range of architecture topics including the relationship with the transportation planning process, regional and project architectures involving the National ITS Architecture as required.

• Develop white papers and/or conduct briefings to address systems engineering and its relationship to the transportation planning process as needed.

• Facilitate workshops, charettes, meetings, and other stakeholder forums that advance architecture use and maintenance and systems engineering mainstreaming.

Subtask C deliverables include:

• Document support for the update and maintenance of the Border Information Flow Architecture with Canada.

• Develop concepts of operation (CONOPS) and project architectures for ITS technology deployments on both the United States-Canada border and United States- Mexico border as needed.

• Deliver technical assistance for international workshops and stakeholder forums on border architecture elements as needed.

• Deliver technical reviews, analyses and technical support of major ITS technology projects led or supported by FHWA in regions along the United States borders with Canada and Mexico as needed.

• Deliver support to any initiatives to develop border architecture(s) covering other surface transportation and air entry points, e.g. ports, into the U.S. as needed.

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 $35,000 with Equipment/Materials not expected to exceed $8,000 each year for FY 2012 and FY 2013.

Level of Effort:

The estimated level of effort for Task Areas A, B and C for FY 2012 and FY 2013 by year is given below.

Labor Category Task Areas A, B & C

Program Manager 850 hours Principal Investigator 1,200 hours Systems Engineer(s) 3,250 hours Communications Engineer(s) 400 hours Transportation Engineer(s) 1,500 hours Software Engineer(s) 400 hours Administrative 360 hours Total 7,960 hours per year