TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.

Slides:



Advertisements
Similar presentations
Title Slide – Technology or Company Name
Advertisements

Roadmap for Sourcing Decision Review Board (DRB)
Brian A. Harris-Kojetin, Ph.D. Statistical and Science Policy
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
[PROJECT NAME] Project Gating Presentation Presented to: [Audience Name] Presenter: [Your Name] Date: YYYY-MM.
Project Proposal Project ? Project Sponsor Project Manager Version
TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
Chapter 3 Project Initiation
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.
Fiscal Year 2008 Urban Areas Security Initiative Nonprofit Security Grant Program Investment Justification Questions, Criteria, and Prioritization Methodology.
Presented By: Thelma Ameyaw Security Management TEL2813 4/18/2008Thelma Ameyaw TEL2813.
What is a project? Project Management Institute definition
Action Implementation and Evaluation Planning Whist the intervention plan describes how the population nutrition problem for a particular target group.
Chapter 3: The Project Management Process Groups
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
Conducting the IT Audit
Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC) [Insert Project Name] Project Baseline Review (PBR) [Insert Date of PBR] 1.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Project Management Phases Class 6. Initiation & Planning – Agenda Overview of the project management phases Midterm paper details.
S/W Project Management
1 Framework Programme 7 Guide for Applicants
Literature Review and Parts of Proposal
1 Our Expertise and Commitment – Driving your Success An Introduction to Transformation Offering November 18, 2013 Offices in Boston, New York and Northern.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 6/25/2015 V2.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
10/10/2015 IENG 471 Facilities Planning 1 IENG Lecture END Project Report Requirements & Project Presentation Information.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
1 SPSRB Decision Brief on Declaring a Product Operational Instructions / Guidance This template will be used by NESDIS personnel to recommend to the SPSRB.
Research & Technology Implementation TxDOT RTI OFFICE.
Version, Date, POC Name 1 Purpose: Concisely state the scientific objective of the proposed basic research proposal. Product/Results: Identify the research.
NATIONAL INSTITUTES OF HEALTH CHALLENGE GRANT APPLICATIONS Dan Hoyt Survey, Statistics, and Psychometrics(SSP) Core Facility March 11, 2009.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
Design Proposal A document prepared to (a) justify the need for the project, (b) describe the engineering process to be taken, (c) outline the expected.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 16/25/2015 V2.
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
1 NASA WBS TASK #: QUARTERLY TECHNICAL PROGRESS REVIEW TASK # & TITLE:06-0xxxx Assessment of Electronic Widgets - Radiation QUARTER:XQ FY06.
Atlantic Innovation Fund Round VIII February 5, 2008.
Comparison of CA Evaluation Protocols, CA Framework, IPMVP and CPUC Policy Manual* A preface to group discussion *In terms of how they define.
BSBPMG501A Manage Application of Project Integrative Processes Manage Project Integrative Processes Unit Guide Diploma of Project Management Qualification.
1 Waste Discharge Authorization Application - British Columbia WG6 Application Process WG Document Review presented by Helga Harlander October x, 2008.
The Project Plan Plan Your Work, then Work Your Plan
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
[Project Title], #[Proj. ID] Lessons Learned Presented by [Name] [Date] Lessons Learned Template Version /07/2015.
EVALUATION OF THE SEE SARMa Project. Content Project management structure Internal evaluation External evaluation Evaluation report.
Team-Based Development ISYS321 Managing the Information Systems Project.
2/27/2016 IENG 471 Facilities Planning 1 IENG 464 – Conceptual Design Project Report & Presentation Requirements.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
Continual Service Improvement Methods & Techniques.
A research proposal is a document written for the purpose of obtaining funding for a research project.
Objective: Develop hybrid biological semiconductors which are EMP resistant and whose electronic properties can be directly manipulated by environmental.
Principal Investigator ESTCP Selection Meeting
Module 8: Effective Innovation Review and Selection Process
Systems Analysis and Design in a Changing World, 4th Edition
Principal Investigator ESTCP Selection Meeting
ISO 9001:2015 Auditor / Registration Decision Lessons Learned
STEP 7 - EXECUTION PHASE: MONITORING & CONTROLING
Principal Investigator ESTCP Selection Meeting
Executive Project Kickoff
Project Kick-off <Customer Name> <Project Name>
Chapter 3 Managing the Information Systems Project
Principal Investigator ESTCP Selection Meeting
Radiopharmaceutical Production
(Insert Title of Project Here) Kickoff Meeting
Presentation transcript:

TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE

Project Team ● This slide should list the PI and co-performer(s) names and organization(s). ● If you are executing your project with no co-performers, this slide is not required. NOTE: Throughout this template, recommendations are provided as to the number of slides needed for each section of the brief. Regardless of the number of slides you ultimately use, plan your brief to be no more than 30 minutes uninterrupted (not including your backup slides). 2

Problem Statement ● Clearly state the environmental problem the technology or methodology demonstration is addressing and its relevance and importance to DoD. ● Identify the current approach (if one exists) to this problem and its shortcomings. NOTE: Limit to one slide only. 3

Technical Objectives ● Briefly describe the technical objective(s) of your demonstration project overall. NOTES: 1. Limit to one slide only. 2. This section is meant to orient the selection committee on the overall objectives of the project. 4

Technology/Methodology Description ● Describe the technology or methodology in sufficient detail to provide an accurate and factual understanding of its theory, functionality, and operation. ● As appropriate, provide an overall schematic or flow diagram. ● Discuss how the technology or methodology is innovative. NOTE: Limit to two to three slides. 5

Technology/Methodology Maturity ● Provide evidence that the technology or methodology is mature enough for demonstration (include references and past funding history).  Provide a brief description of any previous related demonstrations.  Summarize data and studies justifying the expected performance.  Discuss any additional development, design, field, or laboratory work that is required prior to demonstration. NOTE: Limit to two to three slides. 6

Technical Approach ● Provide a detailed overview of how the project will be conducted to address the technical objectives. ● Include a brief description of the proposed demonstration site(s), if known. If the site has not yet been selected, discuss required site characteristics for an optimal demonstration. ● Provide the performance objectives. ● Provide a broad overview of the test design. Discuss the scope of proposed demonstration and relate the planned data collection to the performance objectives. ● Include a description of the data analyses that will be conducted to determine whether the success criteria for the performance objectives have been met. NOTE: This section should consist of several slides and should be the focus of the presentation. Additional descriptors are included in the full proposal instructions for all sections. 7

Technical Risks ● Identify potential issues of concern and technical risks in taking the technology or methodology from the research phase to proposed scale of demonstration. ● Identify any assumptions that have been made that, if not realized, could impact the successful implementation of the project. ● Discuss how risks will be managed. ● If the demonstration is not a full scale, discuss any scale- up issues that will remain at the conclusion of a successful demonstration. NOTE: Limit to one slide only. 8

Related Efforts ● Provide information on any relationship to other similar projects. ● Identify funding sources for these efforts. NOTE: Limit to one slide only. 9

Expected DoD Benefit ● Describe the expected benefit in terms of environmental impact and/or reduced cost, as applicable. ● Assess the environmental benefit per site or implementation and the expected aggregate benefit for DoD. ● Provide realistic projections of the number of DoD sites or facilities where the technology or methodology can be deployed. ● Discuss how the information obtained from the demonstration will enable adoption of the technology or methodology throughout DoD. ● Estimate the expected return on investment (cost of implementation versus savings) and the time for payback. ● Discuss the life cycle cost and advantages over current approaches, if one exists. NOTE: Limit to one to two slides. 10

Schedule of Milestones Tasks Q1Q2Q3Q4Q5Q6Q7Q8Q9Q10Q11Q12 1. Title 2. Title 3. Title 4. Title 5. Reporting DP FR C&P DP – Demonstration Plan FR – Final Report C&P – Cost & Performance Report Provide a project schedule with expected milestones and deliverables for the duration of the project in the form of a Gantt chart (example below). Ensure all required ESTCP deliverables are included, in accordance with the full proposal instructions. * Identify any decisions points. * 11

Schedule of Milestones (continued) ● Explicitly identify any development, design, baseline characterization, field, laboratory, or treatability work that is required prior to demonstration. ● Estimate the time required for the demonstration. Include the planned initiation and completion dates for critical events, including but not limited to equipment installation, monitoring, fieldwork, data analysis, and other key activities as appropriate. ● Include expected submission dates to the ESTCP Office for the first draft and completed final document for Demonstration Plans and Final Reports. Cost and Performance Reports are due when the final version of the Final Report is submitted. Separate first draft and final submission dates by a two-month period to allow time for ESTCP review. 12

Technology Transition ● Describe the method by which the technology or methodology will be transitioned to end user(s) or commercialized. ● Specify how technology transfer methods will differ to reach appropriate audiences (i.e., regulators, consultants, etc.). ● Describe any proposed guidance documents that will assist in future implementation (i.e., guidance, design, and/or protocol documents). ● Explicitly identify potential first DoD users and follow-on implementation. ● Identify any DoD or service programs that are responsible for technology or methodology implementation or relevant requirements or regulations that will effect transition. ● If there are known institutional or regulatory barriers that will affect the transition, they should be described in this section along with recommendations for addressing these barriers. NOTE: Limit to one to two slides. 13

Cost Estimate ● Provide a table that summarizes the requested ESTCP funds by performer by fiscal year. Cost should be listed in thousands of dollars ($K) and rounded to the nearest thousand. PerformerFY15 ($K)FY16 ($K)FY17 ($K) Performer Performer 2100 Performer 350 Total Grand Total700 14

Project Leveraged Funding ● Provide a table that delineates all leveraged funding for the project for each fiscal year. This should include direct funding support and in-kind support. If a performer is providing support (for example, XYZ Co. is receiving ESTCP funds but also providing in-kind support), then that should be indicated. PerformerFY15 ($K)FY16 ($K)FY17 ($K) Funding Source 1*2550 Funding Source 2*7565 Performer 3**30 Total Grand Total420 * Direct Funding Support ** In-Kind Support 15

Backup Slides

ESTCP Review Comments ● Provide a summary of the ESTCP review comments and responses here. ● Include any other support material here. 17