ITS4US Deployment Accelerator 693JJ3-27-BAA-0001

BROAD AGENCY ANNOUNCEMENT (BAA)

693JJ3-27-BAA-0001

Federal Highway Administration

Office of Acquisition and Grants Management

ITS4US Deployment Accelerator

1.0 INTRODUCTION AND OVERVIEW

The United States Department of Transportation (USDOT) Intelligent Transportation Systems Joint

Program Office (ITS JPO) is announcing its intent to solicit proposals under this Broad Agency

Announcement (BAA) for the topic titled ITS4US Deployment Accelerator. This BAA is developed in accordance with Federal Acquisition Regulation (FAR) 6.101(b)(3)(ii) and FAR 35.102, which provides

USDOT an acquisition tool with the flexibility to make awards to meet present and compelling needs.

This BAA is an expression of interest only and does not commit the Government to pay any proposal preparation costs. All responsible, eligible sources capable of satisfying the Government's needs may submit a proposal. The Government reserves the right to award contracts that are determined to be of benefit to the Government in achieving the goals of this program.

1.1 Background

The ITS JPO collaborates across modal administrations to coordinate and plan the USDOT’s Multimodal

ITS Technology Research Program. This program improves transportation safety, mobility, and efficiency, and enhances productivity through the integration of innovative technologies into the nation’s transportation system.

ITS JPO delivers large-scale ITS deployment programs (e.g., ITS4US, V2X Accelerator, and Connected

Vehicle Pilots) addressing key transportation challenges and enhancing safety, efficiency, and mobility.

These programs develop, test, and deploy mature and emerging transportation technologies to operate at full-scale in real-world settings. These successful deployments also serve as replicable models that others can use to solve similar transportation challenges in their own localities more rapidly, and at lower cost and risk.

ITS JPO historically focused efforts to encourage replication of deployment successes on public outreach and publishing documentation, data, and code developed by the projects. Now, ITS JPO is looking to more proactively encourage replication and deployment through activities such as the cohorts program, which established a collaborative environment for vehicle-to-everything (V2X) deployers. However, engaging with various localities in different stages of the project/deployment life-cycle constrains the ability to expedite follow-on deployment.

Aligned with USDOT’s priority of advancing innovation, the ITS4US Deployment Accelerator Program aims to demonstrate the replicability of successful ITS4US deployment components, accelerated by knowledge and technology transfer. This acquisition will procure up to five contracts to conduct operational deployments to test integrated technology solutions designed to improve healthcare accessibility based on the successes of the ITS4US Heart of Iowa Regional Transit Agency (HIRTA)

Health Connector deployment.

In 2020, FHWA awarded the first phase of its ITS4US Deployment Program (BAA 693JJ3-20-BAA-

0004). The first phase enabled communities to showcase innovative business partnerships, technologies and practices that promote independent mobility for all. The five awardees were:

• HIRTA, Public agency/Other than Small

• Georgia Department of Transportation, Public agency/Other than Small

• Niagara Frontier Transportation Authority, Public agency/Other than Small

• University of Washington, University/Other than Small; and

• California Association of Coordinated Transportation (CALACT), Public agency/Other than

Small.

In 2022, in response to NOFO 693JJ322NF00001, four of the awardees were selected to continue https://www.acquisition.gov/far-overhaul/far-part-deviation-guide development toward deployment in Phase 2 and 3.1 In particular, the HIRTA Health Connector deployment was selected as part of USDOT’s strategy to support accessibility across all modes of transportation for all travelers. The third phase of ITS4US Deployment Program will expire on May 9, 2027.

The ITS4US Deployment Accelerator program will serve as a Proof-of-Concept for systematically replicating successful technology deployments across multiple locations nationwide. By creating a structured mechanism for knowledge transfer and deployment acceleration, this project aims to maximize

USDOT’s return on investment from successful innovations. This project aims to remove inefficiencies resulting from jurisdictions pursuing independent development by following the successful path charted by the recent, successful ITS4US HIRTA Health Connector deployment.

This initiative will establish a framework for rapidly scaling proven solutions by:

• Leveraging documented best practices from successful ITS JPO deployments

• Creating direct knowledge transfer channels between successful and follow-on deployers; and

• Providing coordinated technical support and seed funding2 to accelerate adoption.

If successful, this model could transform how innovations scale nationally, ensuring ITS JPO investments in successful programs generate maximum return through efficient replication across the country.

1.2 Legislative Authority

The legislative authority for this BAA is found under 23 U.S.C. 516 which states, in part: “The Secretary shall carry out a comprehensive program of intelligent transportation system research and development, and operational tests of intelligent vehicles, intelligent infrastructure systems, and other similar activities that are necessary to carry out this chapter.”

1.3 Purpose

The ITS JPO looks to accelerate the replication of innovative technology solutions developed by large-scale deployment projects that it sponsors. ITS JPO believes that successful demonstration of these solutions by multiple agencies validates the technology's maturity and readiness for broader implementation across the industry.

The purpose of this BAA is to award up to five operational deployments that will test integrated technology solutions developed and deployed by the ITS4US Deployment Program. Each awardee will integrate, test, and deploy solutions modeled on ITS4US deployment project documentation and its associated open-source software. In addition, the awardees will form a deployer cohort and receive

USDOT-funded technical support designed to accelerate implementation. Awardees can build faster, better, and cheaper by launching related efforts together, and use the insight of peers who have recently succeeded in addressing similar challenges.

For this solicitation, offerors must propose solutions designed to improve access to healthcare services based on the successes of the ITS4US HIRTA Health Connector deployment. These deployments will focus on:

• Integrating transportation scheduling capabilities directly into healthcare appointment booking systems, and

• Deploying trip planning applications to assist patients in reaching their appointments.

This acquisition will support the ITS JPO’s mission of improving safety and mobility through integration of innovative technologies into the nation’s transportation system.

1 CALACT was not selected to continue to Phase 2.

2 The funding provided in response to this solicitation may or may not cover the full expected cost of development and implementation.

2.0 CONTRACT GUIDELINES

Offerors shall propose their operational deployment that will test integrated technology solutions developed and deployed by the ITS4US Deployment Program guided by the requirements of this BAA and Attachment 1 – Performance Work Statement (PWS) and provide their technical proposal to integrate, test, and deploy mobility technology solutions that enhance healthcare accessibility for their community based on open-source software and documentation developed under the ITS4US Deployment

Program.

2.1 Schedule

The USDOT anticipates the following schedule for this BAA, note that the dates provided are estimates and are subject to change.

Solicitation Posted October 20, 2026 -

Questions Due November 4, 2026 9AM Eastern Time

Answers Provided November 18, 2026 -

Proposals Due January 11, 2027 9 AM Eastern Time

Award/s Made By March 2027 -

All correspondence, including the Q&A and proposal submissions, must be emailed to Contracting

Officer (CO) Vivian Riboli at vivian.riboli@dot.gov. All submissions must be received by the date and time indicated in the table above or may be excluded from evaluation and consideration for award.

During the Question and Answer (Q&A) period, all questions must be submitted using Attachment 3 -

Q&A Template, attached to this BAA. Questions that are duplicate or similar in substance may be removed. The Government will not respond to individual emails for the Q&A but will publicly post the

Q&A to SAM.gov for the benefit of all potential Offerors. Offerors are responsible for checking

SAM.gov for updates.

2.2 Communications Protocol

Any exchanges of information must be consistent with procurement integrity requirements of section 27 of the Office of Federal Procurement Policy Act (41 U.S.C. 423, as amended) (see FAR 3.104). Offerors are advised that any indication of interest from the Government, in the affirmative, is not meant to imply nor in any way impart an obligation on the part of the Government that an award will be forthcoming for the offered work or project.

2.3 Offeror Eligibility

This is an unrestricted BAA; however, eligibility is limited to responsible sources including, but not limited to, States or local Governments (or organizations of State or local Governments), universities or institutions of higher education, non-profit organizations, private individuals, corporations, and businesses or commercial organizations.

All Offerors must be registered in the Federal Government’s System for Award Management (SAM) system at the time of proposal submission.

2.4 Program Requirements and Project Funding Limits

Teaming Requirement

This effort has a teaming requirement. Proposals must include three roles: 1) a Mobility Services

Operator, 2) a Healthcare Partner and 3) a Software Integrator. Note that a single organization or entity may play one or more of these three required roles. If a single organization proposes to fulfill more mailto:vivian.riboli@dot.gov http://www.sam.gov/ than one role, it must clearly demonstrate that it possesses the specific experience and capability required for each role. See Section 3.1 of this document for additional details on teaming requirements.

Project Funding Limits

The estimated total value for this acquisition is $1,625,000 ($325,000 per award) over an 18-month period of performance. This value is considered to cover only the costs of the required performance and deliverables stated in the PWS.

Offerors may propose deliverable schedules within the total possible 18-month period of performance.

The Government has no preference on the timing of the system demonstration beyond the requirements outlined in Section 1.3.3. of Attachment 2 – Performance Work Statement (PWS),

2.5 Deliverable Requirements

REQUIREMENTS FOR IMPLEMENTING SECTION 508 STANDARDS

NOTE: The following applies to all FHWA contracts containing Information and Communication

Technology (ICT) as a deliverable.

In addition to the work requirements specified in this BAA, the Contractor shall ensure that all ICT deliverables denoted as 508 required in PWS Exhibit 2 meet the requirements of Section 508 of the

Rehabilitation Act and the ICT Final Standards and Guidelines (508 Refresh) at 36 CFR Part 1194.

As defined in the 508 Refresh, at 36 CFR Part 1194, Appendix A, E103.4, ICT is “Information technology and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content. Examples of ICT include, but are not limited to computers and peripheral equipment; information kiosks and transaction machines; telecommunications equipment; customer premises equipment; multifunction office machines; software; applications; Web sites; videos; and, electronic documents.”

Section 508 requires that all electronic products prepared for the Federal Government be accessible to persons with disabilities, including those with vision, hearing, cognitive, and mobility impairments.

Applicable Standards:

• Appendix A to Part 1194 – Section 508 of the Rehabilitation Act: Application and Scoping

Requirements

• Appendix B to Part 1194 – Section 255 of the Communications Act: Application and Scoping

Requirements

• Appendix C to Part 1194 – Functional Performance Criteria and Technical Requirements

Section 508 Refresh standards are available at https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh.

The Contractor shall adhere to the terms and requirements in FHWA Form 4260 Section 508 ICT

Conformance Criteria for Section 508 conformance. The Conformance Criteria document does not need to be completed when submitting a deliverable.

Deliverables identified for publication are subject to further USDOT review after technical acceptance but prior to publication. The Contractor is responsible for and shall make any and all changes to create

USDOT Publication Ready deliverables.

https://www.access-board.gov/ict/#about-the-ict-accessibility-standards https://www.access-board.gov/ict/#about-the-ict-accessibility-standards https://www.access-board.gov/ict/#about-the-ict-accessibility-standards https://www.access-board.gov/ict/#about-the-ict-accessibility-standards https://www.access-board.gov/ict/#about-the-ict-accessibility-standards https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh

2.6 Code Sharing

Software development, enhancements, alterations, or adaptations developed using Federal funding in this effort are intended to be shared as open-source resources in the USDOT ITS CodeHub. This includes documentation of the code, test datasets, and any other data or artifacts needed to independently modify, test, evaluate and execute the software. Existing applications developed prior to or outside of this effort need not be made open source; however, the Offeror must detail in their proposal what specific existing systems/hardware/software/applications will remain proprietary. Note that all code made available must adhere to guidelines on preparation for submission and accompanying metadata. Please see:

https://www.its.dot.gov/code/code-submission/.

NOTE: The government is interested in sharing enhancements to the three open source Health Connector software components that are the focus of this solicitation. Awardees are expected to further develop the

Health Connector code during performance of the contracts resulting from this solicitation, creating enhancements that the government seeks to share and encourage re-use and replication of the software after the conclusion of this initiative. The Health Connector software is a middleware solution integrating transportation scheduling systems (managed by a Mobility Services Operator) with healthcare appointment booking systems (managed by a Healthcare Partner). The government does NOT seek to share code resident in the transportation scheduling systems, healthcare appointment booking systems, or other supporting systems to which the Health Connector middleware connects and integrates.

Real-time sharing and/or joint development of a shared codebase among awardees is NOT anticipated.

Rather, each awardee is expected to develop and manage a separate codebase (i.e., a “fork”) during the development and testing phase, and submit the enhanced, forked codebase back to the CodeHub prior to the end of the period of performance in this effort.

2.7 Intellectual Property Rights

Awards will generally contain detailed clauses concerning patent rights, rights in technical data and computer software, data reporting requirements, and other terms and conditions, which shall be negotiated as part of the award process.

Offerors must describe any limitations on any intellectual property (inventions, trade secrets, copyrights, or trademarks) that will impact the Offeror’s performance of the contract or impact the Government’s subsequent use of any deliverable under the contract. The Offeror must describe the intellectual property in sufficient detail to describe the limitations (data assertions of the Offeror or any subcontractor, etc.), and to describe why or how the Government can accomplish the stated objectives of this BAA with the limitations described or proposed by the Offeror. No assertion of limited rights in patents or patent applications with respect to the open source Health Connector software will be accepted.

2.8 Patents

Offerors must list any known invention or discovery that is or may be patented that may require the

Government to obtain a license should the Offeror’s proposal be selected for award. Invention is defined in FAR 27.301 as “any invention or discovery that is or may be patentable or otherwise protectable under title 35 of the U.S. Code, or any variety of plant that is or may be protectable under the Plant Variety

Protection Act ( 7 U.S.C. 2321, et seq.).” If any patent or patent application is owned by the Offeror, the

Offeror must provide a statement, in writing, that it either owns or possesses the appropriate licensing rights to the patent or patent application for which the Government may require a license. If an Offeror does not own or have license rights to license the Government for any such patent or patent application, the Offeror must explain how the Government may obtain a license or whether the Offeror plans to obtain these rights on behalf of the Government.

https://www.its.dot.gov/code/code-submission/

For any patent or patent application listed above, the Offeror must provide the patent number or patent application publication number, a summary of the patent or invention title, and indicate whether the

Offeror is the patent owner. If a patent or invention is not licensed by the Offeror, identify the licensor.

Rights in patents, patent applications, and invention disclosures will be addressed in the patent rights clause to be included in the contract and therefore, as stated in section 2.8, no assertion of limited rights in patents or patent applications with respect to the open source Health Connector software will be accepted.

2.9 Proprietary Data Restrictions

Project proposals may contain data the Offeror does not want disclosed to the public for any purpose or used by the Government except for evaluation purposes. If the Offeror wishes to restrict such data, the cover page of the technical and cost/price proposals must be marked with the following legend, and relevant sheets marked as instructed.

This proposal includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed – in whole or in part – for any purpose other than to evaluate this proposal. However, if a contract is awarded to this Offeror as a result of – or in connection with

– the submission of these data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting contract. This restriction does not limit the

Government’s right to use information contained in these data if they are obtained from another source without restriction. The data subject to this restriction are contained in Sheets [insert numbers or other identification of sheets].

Each restricted data sheet shall be marked as follows:

Use or disclosure of data contained on this sheet is subject to the restriction on the cover page of this document.

2.10 Document, Data, and Code Rights

Offerors must explicitly detail in their proposal which components will remain proprietary; otherwise, the

Government shall maintain unlimited rights to all documents, data (suitably cleansed of personally identifiable information (PII), protected health information (PHI), and sensitive personally identifiable information (SPII)) and source code developed as a part of this BAA and identified for sharing with the research community. The Government's unlimited rights permit it to use, disclose, reproduce, and distribute the data and code for public sharing purposes. Additionally, the Government may identify certain documents, data, and/or source code that may not be used or sold without written permission from the Contracting Officer (CO).

NOTE: The government is primarily interested in sharing data that explains or reveals the operational status, effectiveness, and/or impact of the implemented middleware solution. The government specifically seeks to AVOID exposure to PII associated with providing the service enabled by the middleware, including PII (e.g., passenger names, location of residence), PHI (e.g., wheelchair use), or SPII (e.g., social security numbers).

2.11 Section 889 Compliance Requirement

Any contract awarded under this BAA must be compliant with Section 889’s “Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment” of Public Law 115-232, also known as the John S. McCain National Defense Authorization Act (NDAA).

• FAR 52.240-90 Security Prohibitions and Exclusions Representations and Certifications (SEPT

2025)

• FAR 52.240-91 Security Prohibitions and Exclusions (SEPT 2025) https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52#FAR_52_240_90 https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52#FAR_52_240_90 https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52#FAR_52_240_91

2.12 Executive Order 14398 Compliance Requirement

Any contract awarded under this BAA must be compliant with Executive Order 14398 titled “Ending

Illegal Discrimination and restoring Merit-Based Opportunity” issued on March 6, 2026. Offerors are encouraged to review the mandatory clause prior to submitting a proposal.

• FAR 52.222-90 Addressing DEI Discrimination by Federal Contractors (APR 2026)

3.0 PROPOSAL REQUIREMENTS

Proposals must be organized into two volumes:

Volume File Name File Format

I. Technical Proposal 693JJ3-27-BAA-0001_Vol I Tech_[Offeror Name] PDF

II. Price Proposal 693JJ3-27-BAA-0001_Vol II Price_[Offeror Name] PDF/ Excel

Project proposal documents must meet the following formatting requirements: Times New Roman size

11-point font, and single-spaced, single-sided letter size pages with 1” margins (minimum). Tables and graphics may use fonts smaller than 11-point, provided the text remains clearly legible when viewed at

100% zoom. Proposals must not contain promotional brochures, advertisements, taped recordings, or other extraneous material.

Proposals that do not include all of the information listed in Section 3.0 Proposal Requirements (including all subsections) may be removed from further evaluation.

Proposal Page Limits:

• There is a 15-page limit for Volume I only, subject to the exceptions and further restrictions described below. Proposal materials submitted over this page limit will not be reviewed.

• There is no page limit for Volume II.

Proposal submissions that are incomplete, materially lacking, or not responsive to the directions and technical requirements of this BAA may not be evaluated, or evaluated as is, without further opportunity for revision, at the discretion of the Government’s evaluation committee.

Proposals must be submitted via email to the CO by the designated date and time indicated in section 2.1.

Email submissions must include the BAA solicitation number in the subject line. Offerors are advised that the Government’s evaluation of a particular project for possible award is based solely on the contents of the Offeror’s proposal and the Offeror’s answers to any technical clarification questions, as transmitted through the CO.

3.1 Volume I: Technical Proposal

General Requirements

The technical proposal shall contain the following sections and appendices. Items marked with * do not count toward the page limit.

• Section 1: Cover Page* https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52

• Section 2: Technical Approach

• Appendix A*: Resumes

• Appendix B*: Formal letters of commitment or signed copies of Memoranda of Understanding

Section 1. Cover Page:

Project proposals must include a cover page containing the following information:

• Working title of the proposed project

• BAA Title and Solicitation Number

• “Volume I Technical Proposal”

• Name, phone number, mailing address, and e-mail addresses for the principal technical and contractual points of contact (person or persons authorized to negotiate on behalf of the Offeror and who can contractually obligate the Offeror’s organization)

• Unique Entity Identifier (UEI) from SAM.gov for all organizations (Offeror and partners) on the proposed team

• List of Secondary Offeror organization (project partners) names

• Date of submittal

• A statement disclosing the use of Super Intelligence (SI)3 tools in the development of the

Offerors’ proposal, and certification that all information provided is accurate and verified.

Section 2. Technical Approach

The Offeror shall describe and provide the following:

• Detailed technical approach and understanding to performing the work as stated in the PWS

(Attachment 2), including a delineation of project work proposed for each partner organization;

• A team that consists of (at a minimum):

Organization Type Illustrative Role Examples

Mobility Services

Operator

• Provides necessary access to scheduling system to cross-check with appointments.

• Provides mobility services for scheduled rides.

• Provides staff and rider training.

• Markets the new service/tool.

• Transit agency (operations or scheduling department)

• Non-emergency medical transportation provider

Software Integrator

• Implements or extends middleware for local vendors as open-source.

• Provides reporting capabilities for partner organizations.

• Transit agency

(Information Technology

[IT] department)

• IT consultant

• Mobility services vendor

Healthcare Partner

(public or private)

• Provides limited access to patients’ electronic health records (EHR) for scheduling purposes.

• Follows up with patients who do not have confirmed transportation for an upcoming appointment.

• Provides staff and patient training.

• Markets the new service/tool.

• Regional Health System

• Integrated Healthcare

Delivery System (IHDS)

• Medical Campus

• Department of Health

3 In accordance with Executive Order 14434, in this procurement, FHWA will use “Super Intelligence” and “SI” in place of “Artificial Intelligence” and “AI.”

Organization Type Illustrative Role Examples

Medicaid

Transportation

Broker*

• Provides mobility services operator with necessary access to broker system.

• Provides access to system components to expedite reconciliation with mobility services operator.

• Medicaid Transportation

Broker (State or local)

*Optional partner. Required only if implementing Medicaid broker middleware.

• Key Personnel Table:

o Deployment Lead (DL), Systems Engineering Lead (SEL), Project Management Lead

(PML) – See Attachment 2, Section 3.4 for detailed description/roles.

The Key Personnel table shall include the name, title, and a brief description of the duties the Key

Personnel will perform. Each of the Key Personnel roles must have a singular named individual.

No one individual can serve in more than one KP role. At least one Key Personnel shall be named for each partner organization. A single organization may offer more than one Key Personnel;

• Level of Effort table (table displaying organization and labor hours per (sub)task (names and cost information shall not be provided in the Technical Proposal);

• Proposal Summary Template (See Attachment #1); and

• Any other information that the Offeror wishes to bring to the attention of the Government.

The table below shows the estimated breakdown of the level of effort by task:

Task Estimated Level of Effort

Task 1: Project Management 10%

Task 2: Project Concept and Development 50%

Task 3: System Demonstration 30%

Task 4: Project Assessment 10%

Appendix A. Resumes

Resumes (3-page maximum per resume) are required for all key personnel. Additional staff resumes (2-page maximum per resume) may be submitted for up to five additional staff that are not key personnel, but these resumes are not required.

Appendix B. Formal letters of commitment or signed copies of Memoranda of Understanding

Appendix B must provide formal letters of commitment or signed copies of Memoranda of Understanding between partner organizations and the Prime Offeror that document financial and/or staff time commitment to this project. As noted above, Appendix B is not included in the Volume I page limit.

3.2 Volume II – Price Proposal

This volume consists of the following sections:

1. Cover page

2. Cost/Price Information

Section 1. Cover Page

The cover page for Volume II must include:

• Working title of the proposed project

• BAA Title and Solicitation Number

• “Volume II Business, Cost, and Pricing Data”

• Names, phone numbers, mailing address, and e-mail addresses for the principal technical and contractual points of contact (person or persons authorized to negotiate on behalf of the Offeror and who can contractually obligate the Offeror’s organization), and

• UEI from SAM.gov for all organizations (Offeror and partners) on the proposed team

• Date of submission

• A statement disclosing the use of SI tools in the development of the Offerors’ proposal, and certification that all information provided is accurate and verified.

• Conflicts of Interest - The Offerors shall provide a brief statement describing in a concise manner all past, present, or planned organizational, contractual, or other interest(s) that may affect the

Offerors' ability to perform the proposed contract in an impartial and objective manner. The

Contracting Officer will review the statement and may require additional relevant information from the Offerors. In accordance with FAR Subpart 9.5, all such information, and any other relevant information known to DOT, will be used to determine whether an award to the Offerors may create an actual or potential conflict of interest. If any such conflict of interest is found to exist, the

Contracting Officer may (a) disqualify the Offerors, or (b) determine that it is otherwise in the best interest of the United States to contract with the Offerors and include appropriate provisions to mitigate or avoid such conflict in the contract awarded.

Section 2. Cost/Price Information

All offerors shall provide the following:

a) Pricing Schedule. Complete the Pricing Schedule below:

# Deliverable Units Firm Fixed Price

1 Task 1A: Kickoff Meeting 1

2 Task 1B: Monthly Progress Reports Up to 18

3 Task 2A: Operational Concept Plan 1

4 Task 2B: Open-Source Code and associated artifacts 1

5 Task 3: Draft Demonstration Plan 1

6 Task 3: Final Demonstration Plan 1

7 Task 4A: Lessons Learned and Impacts Report 1

8 Task 4B: Program Reflection 1

Total Firm Fixed Price

b) Cost Breakdown

A fully detailed cost break-down showing costs by each major cost category, including (as applicable) direct labor, fringe benefits, subcontract costs, other direct costs (travel, equipment, etc.), and indirect costs. Total cost must match the total price provided in the pricing schedule.

The cost detail shall include (as applicable):

Direct Labor:

• Personnel by name or labor category

• Number of hours proposed (commercial organizations) or percent of effort

• Hourly unburdened labor rate (commercial organizations) or salary rate and basis (9- or

12-month basis)

• Fringe Benefits Rates applied

Other Direct Costs. Other Direct Costs shall be supported by explanation of estimating factors and other relevant supporting details. For example, travel costs shall be supported by detail on the estimated trips, number of travelers, and associated costs for airfare, per diem, other transportation, etc. A similar level of detail shall be provided for any meeting costs, equipment, duplication/printing charges, and other direct costs.

Indirect Costs. Discuss your proposed indirect rates for Phase 1. Identify the various indirect rates, what they are based on (e.g., labor overhead based on direct labor dollars) and how they are applied/calculated. State any differing indirect rate applications (for example if there is a different proposed indirect rate when applied to travel or material purchases than when applied to subcontractor costs). Offerors must provide dollar values as well as percentages.

Subcontractor Costs: Subcontractor costs should be fully detailed, and the information used by the proposer to analyze the price of the subcontract shall be provided. An SF-1411 is not required for this submission of your proposal.

c) Offerors shall submit all (if any) assumptions or conditions upon which the Cost/Price Proposal is based.

d) The Offeror may include within their price proposal a Milestone Payment Schedule that requests interim payments for deliverables and services completed (including draft deliverables and progress reports). The deliverables and services completed must be inspected and accepted by the

CO or their designated representative (COR/TOCOR). Milestone payments are not intended to be monthly percentages of the awarded order but rather payments for completed SOW services.

Any information submitted must support the cost/price proposed. Include sufficient detail or cross-references to clearly establish the relationship with the information provided to the price proposed.

Support any information provided by explanations or supporting rationale as needed to permit the

Government to evaluate the documentation. Such information is not considered cost or pricing data, and will not require certification in accordance with FAR 15.406.

4.0 EVALUATION AND AWARD PROCESS

The BAA evaluation process shall be conducted in accordance with FAR Subpart 35.102 (d) – (f).

Offerors will be notified of evaluation results electronically via e-mail. The Government anticipates the award of up to five contracts resulting from this BAA; however, the Government reserves the right to select for award any, all, some, or none of the proposals received in response to this announcement.

4.1 Evaluation Methodology

4.1.1 Project Proposal Evaluation

Proposals will be evaluated using three Evaluation Factors: Factor 1, Technical Merit and Importance to

Agency Programs; Factor 2, Availability of Funds; and Factor 3, Cost Realism/Reasonableness.

Evaluation Factors 1 and 2 are of equal importance and will be used to determine the highest technically rated proposals. Factor 3 will be evaluated only for proposals that are determined to be the highest technically rated.

The Government will select Offeror(s) for award based on the Evaluation Factors as described above and listed below. The Government reserves the right to conduct discussions and/or negotiations with Offerors directly to clarify any technical and cost/price details from the proposals. Offerors considered unresponsive to the Government’s communications in a timely manner, defined as meeting Government deadlines established and being responsive to the request may be removed from further consideration.

4.2 Evaluation Factors

Factor 1 – Technical Merit and Importance to Agency Programs. This factor will be evaluated based on the following sub-elements that are of equal importance:

• Technical Approach o The proposal includes a satisfactory technical approach for performing the PWS requirements.

o The proposal identifies which of the Health Connector components will be replicated and/or expanded within the scope of the project.

o The proposal demonstrates utilization of appropriate systems engineering methodology.

o The proposed concept is well aligned with the purpose of the initiative (see section 1.3).

o The proposal acknowledges the potential requirement to secure and allocate resources necessary to design and implement the system, beyond the resources provided by USDOT in response to this solicitation and provides an indication of how other resources will be identified and utilized.

• Team Qualifications and Public Partnership Strength o The proposal demonstrates that the proposed Offeror team has the technical capability to deploy the proposed system on the proposed timeline.

o The proposal includes adequate and proper staff with the qualifications for and experience to perform the PWS requirements.

o The proposed team is led by key personnel (Deployment Lead (DL), Systems Engineering

Lead (SEL), and Project Management Lead (PML)) with suitably extensive and relevant experience in software development and developing, deploying, and/or testing the key enabling technologies identified in the proposal as potential elements of the deployment concept.

o The proposed team has clearly identified and qualified organizations in the following key roles (note that a single organization may play one or more of the identified key roles as described above):

• A System Integrator leading software development and testing;

• A Mobility Services Provider providing transportation services to healthcare appointments and programmatic access to their scheduling software;

• A Healthcare Partner providing healthcare services and programmatic access to their scheduling software; and

• A Medicaid Transportation Broker providing programmatic access to their scheduling software, if applicable. (Note: Required only if using Medicaid middleware.)

o The proposal includes formal letters of commitment or signed copies of Memoranda of

Understanding showing strong partnerships between partner organizations and the Prime

Offeror.

o Preference may be given to Offerors proposing teams that require expanding middleware to one or more additional vendors not already included in the Health Connector open-source code. (Example: a new EHR vendor or transit scheduling software vendor.)

Factor 2 - Availability of Funds

The Government will consider the overall availability of funding for allocations or awards selected under this BAA.

Factor 3 – Cost Realism/Reasonableness

As noted above, cost reasonableness and realism analysis will only be conducted on the highest technically rated proposals, as determined by Evaluation Factors 1 and 2. Cost will be considered in the ultimate award decision, as the Government may choose not to make an award if the Contracting Officer is unable to determine whether the costs proposed are realistic and reasonable.

4.3 Award Selection and Notifications

After an awardee is selected, USDOT may enter into negotiations with the awardee regarding any aspect of the contract award. The Government reserves the right to remove an awardee from award consideration should the parties fail to reach agreement on contract terms, conditions and cost/price within a reasonable time, or if the Offeror fails to provide any additional information requested in a timely manner. All awards will be subject to the availability of funds. Only the Contracting Officer can legally commit the

Government to the expenditure of public funds under the BAA.

Awards received through this announcement are not controlled by general procedures of FAR Part 15

“Contracting by Negotiation,” rather they are awarded under the authority and procedures described in

FAR Part 35 “Research and Development Contracting.” Accordingly, given the inherent nature of a BAA, specific terms, conditions, and contract clauses, including FAR, USDOT, and FHWA terms and conditions, can only be determined based on the specifics of a proposed project, appropriate contract type, and entity type. Accordingly, contract clauses will be identified and defined prior to award.

5.0 ATTACHMENTS

Attachment 1 Proposal Summary Template

Attachment 2 Performance Work Statement (PWS)

Attachment 3 Q&A Template