ATTACHMENT A.1_Technical & Management Proposal Model (VOL I).docx

Proposal Title

Prime Organization Name

☐ For-Profit ☐ Non-profit ☐ Academic

SAM.gov Universal Entity Identifier (UEI)

Contact Address - State

Proposer’s Internal Reference Number, if any

Email:

Organization:

(Repeat, as necessary)

Mailing Address:

Telephone:

Email:

Mailing Address:

Telephone:

Email:

Performer: _____% or $_________________

Place(s) of Performance

Date of Proposal Submission

Proposal’s Validity Period (minimum 120 days)

SUB-AWARDEE AND CONSULTANT

TEAM MEMBERS

(Add rows as necessary)

1. Organization Name:

Telephone:

Email:

☐ For-Profit ☐ Non-profit ☐ Academia

2. Organization Name:

Telephone:

Email:

3. Organization Name:

Telephone:

Email:

4. Organization Name:

Telephone:

Email:

Contents

Executive Summary In one page 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?

· How is it done today and what are the limitations of current approaches?

· What is new in your approach? Why do you think it will be successful?

· What are the emerging trends to achieve the stated objective and why might your approach provide a radically superior solution?

· 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?

· How might this effort be misperceived or misused (and how can you prevent that)?

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.

Goals and Impact In one page 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 plans and risks to achieve accessibility and adoption of technology. This section should include a summary of specific outcomes from the proposed research.

Innovative Claims Table (included in the Goals & Impacts page) The following table should be used to link the technical goals, technical challenges, and the proposed innovation and evidence. This section should succinctly describe the uniqueness and benefits of the proposed approach relative to the current state-of-the-art alternative approach and to emerging trends. Add rows as necessary.

Technical Plan In 10 pages or less:

· Present a credible plan to achieve the project’s goal that includes all the required experimental designs and aspects as laid out in the COSMOS ISO.

· Outline and address the technical challenges inherent in the approach and possible solutions for overcoming potential problems.

· Describe how the solution will achieve the Program Level requirements listed in the COSMOS ISO and its appendices.

· Provide appropriate measurable, quantitative milestones 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.

· Risk Mitigation/Contingency Plans and Alternative Approaches

· Identify potential areas of risk (e.g., technical, managerial, schedule, etc.) and propose solutions that maximize the scientific and health impact, budget considerations, and timeliness of deliverables.

· 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) Attachment A.2.

· The Gantt chart, Milestone and Deliverable Table and Technical Description Documents must have a unified numbering scheme where:

· TASKS represent the ongoing work

· MILESTONES represent Deliverable Items (e.g. reports, meeting attendance and presentations, completion of technical goals) which trigger payment.

Capabilities & Management Plan In two pages or less Expertise Provide a summary of the expertise of the team, including any subperformers, and key personnel who will be doing the work. A Principal Investigator (PI) for the project must be identified, along with a description of the team’s organization, including the breakdown by TA. All teams are required to identify a Project Manager/Integrator to:

serve as the primary point of contact (POC) to communicate with the ARPA-H PM team and OT/Contracts equivalent for each award instrument (e.g., Contracting Officer), coordinate the effort across the team, organize regular Performer meetings or discussions, facilitate data sharing, and ensure timely completion of milestones and deliverables.

Organization Provide a clear description of the team’s organization including an organization chart that includes, as applicable:

the programmatic relationship of team members the unique capabilities of team members the task responsibilities of team members the teaming strategy among the team members and key personnel with the amount of effort to be expended by each person during each year.

Coordination Provide a detailed plan for coordination, including explicit guidelines for interaction among collaborators/subperformers of the proposed effort. Include risk management approaches. Describe any formal teaming agreements required to execute this program.

Technical Description Document No page limit The TDD should provide a detailed task breakdown, citing specific tasks for each TA, and their connection to the milestones and program metrics. At time of submission, only a Phase I TDD is required. Work and tasking for Phase II will be solicited at a later date. The TDD must not include proprietary information. Please note the technical proposal must stand on its own as the TDD cannot be used to supplement the 10 pages of the technical proposal.

For each task/subtask, provide:

· A detailed description of the approach to be taken to accomplish each defined task/subtask.

· Identification of the primary organization responsible for task execution (prime awardee, sub-awardee(s), by name).

· A measurable milestone, i.e., a deliverable, demonstration, or other event/activity that marks task completion. Include completion dates for all milestones. Include quantitative metrics.

· A definition of all deliverables (e.g., data, reports, software) to be provided to the government in support of the proposed tasks/subtasks.

It is recommended the TDD be developed so that each TA and Phase of the program is separately defined.

Schedule and Milestones Using the provided format (Attachment A.3), provide a detailed schedule showing tasks (task name, duration, work breakdown structure element as applicable, performing organization), milestones, and the interrelationships among tasks. The task structure must be consistent with that in the TDD. Measurable milestones should be clearly articulated and defined in time relative to the start of the project.

Data Management and Sharing Plan (DMSP) Recommend NTE 2 pages The DMSP shall include all information included in the 6-Element plan format recommended by the National Institutes of Health (to view the 6-Element suggested format visit https://grants.nih.gov/grants/forms/data-management-and-sharing-plan-format-page). Note: this plan will not be specifically evaluated against Criteria 1-3 but will likely be used to give feedback for proposals that are selected for award negotiations.

Gantt Chart Timeline As Applicable to the proposed project, provide a detailed timeline in Gantt Chart Format. The Gantt chart labeling and legend should precisely match the task and milestone numbering in the Technical Plan and Technical Description Document for Phase I. You may submit a Phase II Gantt but it is not required. Work should be separated into Phase I and Phase II. When selecting a numbering scheme, MILESTONES should have serial, non-repetitive numbering across the entire workplan.

References Cited Not Included in The Page Limit For any references cited in the proposal, provide uniquely identifying bibliographic information in this section, including first author, title, source (e.g., journal or book), year of publication, volume and page numbers (if applicable), and a persistent identifier such as a DOI or PubMed ID, where available.

Biographical Information Not Included in the Page Limit

Provide a NIH Biosketch for each Key Person and major contributor to the project. See Attachment E for more information.

Letters of Support Not Included in the Page Limit

Provide letters of support.

1 Document Descriptions

Program Solicitation

N/A

Summary Goals & Impact Technical Plan Management Plan 1 Page 1 Page 10 Pages 2 Pages