ARPA-H TECH & MANAGEMENT (Other Transaction).pdf
PDF 424 KB Posted
- Opportunity number
- ARPA-H-SOL-24-105
- Issued by
-
Department of Health and Human Services
About this file
This document provides guidance for proposals submitted to the Advanced Research Projects Agency for Health (ARPA-H) Scalable Solutions Office (SSO) under the ARPA-H TECH & MANAGEMENT Other Transaction solicitation. The SSO seeks solutions that improve the scalability and affordability of healthcare through approaches such as scalable technologies and interventions, collaborative distribution networks, and biomanufacturing innovations. Eligible proposals should address at least one of the interest areas described for the SSO, which include technologies to enable scaling of provider capabilities, approaches for standardizing complex procedures, and manufacturing innovations to reduce costs and shorten production timelines. The Technical and Management proposal guidance outlines requirements for proposal structure and content, including a 20-page limit. Successful proposals will demonstrate a credible plan to achieve the project goals through measurable milestones and a defined task structure.
ARPA-H TECH & MANAGEMENT (Other Transaction) PDF
View the file
Other files
Show all 21
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
TECHNICAL & MANAGEMENT
This document should include all components described herein and must be submitted in .pdf, .odx, .doc, or .docx formats. All submissions must be written in English and all pages shall be formatted for printing on 8-1/2 by 11-inch paper with 1-inch margins and font size not smaller than 12 point. Font sizes of 8 or 10 point may be used for figures, tables, and charts.
Proposers are encouraged to submit concise, but descriptive, proposals. Specific examples of problems, approaches, or goals are preferred to qualitative generalities. The Government will not consider pages in excess of the page count limitations, as described herein. Proposals with fewer than the maximum number of pages will not be penalized. Additional information not explicitly called for in the Technical and Management Volume must not be submitted, but may be included as links in the bibliography. Any additional materials included in the proposal package will be considered for the reviewers’ convenience only and not evaluated as part of the proposal.
The Technical and Management Volume shall not exceed twenty (20) pages.
Page limit includes: Page limits do NOT include:
Technical figures, tables, charts Cover Sheet Section 1 through 4 described below Table of Contents
Bibliography (Optional) Task Description Document (TDD) Cost Proposal
NOTE: Each template attempts to provide proposers with guidance on development of proposal content. It is the proposer’s responsibility to ensure proposal content meets the applicable evaluation criteria. Content recommendations are displayed in blue font and should be deleted prior to abstract submission.
<PRIME ORGANIZATION LOGO (OPTIONAL)>
TECHNICAL AND MANAGEMENT
Proposal Title Proposer Organization
Type of Organization
Choose all that apply: Large Business, Small Disadvantaged Business, Other Small Business, HBCU, MI, Other Educational, or Other Nonprofit
Proposer’s Internal Reference Number, if any
Technical Point of Contact (POC)
Name:
Mailing Address:
Telephone:
Email:
Administrative POC
Name:
Mailing Address:
Telephone:
Email:
Award Instrument Requested Other Transaction Agreement Total Proposed Cost Total: $ Place(s) of Performance
Other Team Members (subawardees and consultants) if any
Technical POC Name:
Organization:
Organization Type:
Date Proposal was Prepared Proposal Validity Period (minimum 120 days)
TABLE OF CONTENTS
1. PROPOSAL SUMMARY 4
2. GOALS AND IMPACT 4
3. TECHNICAL PLAN 4
4. CAPABILITIES/MANAGEMENT PLAN 5
5. BIBLIOGRAPHY (OPTIONAL) 5
1. PROPOSAL SUMMARY
A. DISCUSSION
[Provide a synopsis of the proposed project, including answers to the following questions:
What is the proposed work attempting to accomplish or do?
How is the proposed work leading to improved health outcomes or improvements in the reliability of health systems?
How is it done today, and what are the limitations of present approaches?
What is new in your approach? Why do you think it will be successful at this time?
What are the key technical, programmatic, or translational risks in your approach, and how do you plan to mitigate or overcome these?
Who or what will be affected and what will be the impact if the work is successful?
What are specific applications of your project?
To ensure equitable access to all people, how will cost, accessibility, and user experience be addressed?
How might this effort be misperceived or misused (and how can you prevent that from happening)?
The summary should include a description of the key technical challenges, a concise review of the technologies proposed to overcome these challenges and achieve the project’s goal, and a clear statement of the novelty and uniqueness of the proposed work.]
B. INNOVATIVE CLAIMS TABLE
The following table should be used to link the technical goals, technical challenges and the proposed innovation and evidence. Thus, this section should succinctly describe the uniqueness and benefits of the proposed approach relative to the current state-of-the-art alternative approach.]
ANNOUNCEMENT
PG. PARA(S)
TECHNICAL
CHALLENGE
INNOVATION AND
EVIDENCE
PROPOSAL
SECTION(S), PG.,
PARA(S).
GOALS AND IMPACT
[Describe how the proposed effort will make a difference (qualitatively and quantitatively) if successful. Describe the innovative aspects of the project in the context of existing capabilities and approaches, clearly delineating the relationship of this work to any other projects from the past and present. . Address any plans and risks to achieve accessibility and adoption of technology. This section should include a summary of specific outcomes from the proposed research.]
TECHNICAL PLAN
[Present a credible plan to achieve the project’s goal. High-risk, high-reward projects are welcomed. Outline and address technical challenges inherent in the approach and possible solutions for overcoming potential problems. Provide appropriate measurable milestones
(quantitative if possible) at intermediate stages of the project to demonstrate progress; milestones should be clearly articulated and defined in time relative to the start of the project. Provide a schedule showing milestones, tasks, and the interrelationships among tasks. The task structure must be consistent with that in the Task Description Document (TDD).]
CAPABILITIES/MANAGEMENT PLAN
[Provide a summary of expertise of the proposed team, including any subawardees/consultants and key personnel who will be executing the work. Identify a principal investigator (PI) for the project and provide a clear description of the team’s organization including roles and responsibilities.]
BIBLIOGRAPHY (NO PAGE LIMIT)
[Provide a brief bibliography with each key personnel’s qualifications (resume), links to relevant papers, references, reports, etc.]
File details come from the government source that posted it. Updated .