Attachment__1_-_White_Paper_Template.docx
DOCX document 28 KB Posted
- Attached to
- Mitigation of Oil in the Water Column
- Solicitation number
- HSCG32-14-R-R00021
About this file
White Paper Descision Template
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Amendment_0002_-_Attachment__2_-_Statement_of_Work_Template.docx | DOCX document | |
| AMENDMENT_0001_TO_BAA_HSCG32-14-R-R00021.doc | DOC document | |
| BAA_HSCG32-14-R-R00021__Mitigation_of_Oil_in_Water_Column.docx | DOCX document | |
| Attachment__2_-_Statement_of_Work_Template.docx | DOCX document | |
| NOTICE_FOR_FILING_AGENCY_PROTESTS.doc | DOC document |
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
White Paper Description Template
[PROPOSED TITLE]
BAA # HSCG32-14-R-R00021
[Name of Principle Investigator (PI)] [PI’s Telephone Number and Email Address]
Executive Summary: (Not to exceed one page.)
Include a brief Executive Summary of the proposed technology, technique or strategy development. It should be part of the title page. Titles given to the proposals shall be descriptive of the work they cover and not merely a copy of the title of this BAA.
Technology Description: (Not to exceed three pages.)
This is the technical portion of the white paper. Describe your understanding of the technology gap statement in Section 61.0 of the BAA; describe your approach/strategy to close the gap; describe the proposed technology, technique or strategy and the science behind it; describe the attributes of your technology, technique or strategy as they relate to the qualities in Section 1.1 of the BAA, and identify the current Technology Readiness Level (TRL) of the proposed technology, technique or strategy. Use the TRL table on page 2 to indicate the current appropriate numeric level for your technological solution, and briefly validate your selection. For example, if your solution is at TRL 3, you should be able to cite analytical and/or laboratory studies that physically validated your analytical predictions. Tables, images, references, and graphs are allowed, but only include them if they add clarity to the description. If not proposing a technological solution, please provide a description of the current maturity of the technique or strategy. The TRL table will not count towards the page limit and can be removed from your white paper submission after selecting the appropriate TRL level.
Technology Development Plan: (Not to exceed one page.)
Describe the development required to bring the solution to a demonstrable state and cite the TRL of the item at the end of the contract. Describe also how the Coast Guard may independently test or demonstrate the technology, technique or strategy. Outline the research and technology development plan and include the anticipated period of performance. Using a table format similar to the one below, identify and schedule key milestones.
| Milestone |
| Schedule |
Expected Expenditures and Justifications: (Not to exceed one page.)
Include a Rough-Order-of-Magnitude (ROM) cost to develop the proposed technology, technique or strategy to a demonstrable level. The ROM cost consists of the total cost plus profit/fee, if any. The ROM should be consistent with any dollar value or ranges specified in the announcement, as well as the level of work being proposed. The ROM costs for the Concept Design phase and the Prototype Development phase (Government option) shall be listed separately.
Curriculum Vitae (CV): (Not to exceed one page.)
Provide brief CV sketches of the Primary Investigator and lead technical team members anticipated to be working on the project. Also, identify suppliers of the design/prototype.
NUMBER OF PAGES FOR THE WHITE PAPER, INCLUDING ATTACHMENTS, MUST NOT EXCEED 7 PAGES
Technology Readiness Level (TRL)
TRLs together make up a systematic metric, or measurement, system that supports assessments of the maturity of new technologies (materials, components, devices, etc.). TRLs are also used for the consistent comparison of maturity between different types of emerging technology. In general when new technology is invented or conceptualized, it would not fit basic safety regulations to apply it immediately to its planned application. Usually new technology is subjected to experimentation, refinement, and increasingly realistic testing. Once the technology has past enough tests and is proven safe, reliable, and functions by itself in its planned application, it can be incorporated into a system or subsystem.
Each TRL represents a specific timeframe within the overall development process of new technology depicted in Table 1. For the purpose of this BAA, TRL 1 is the initial stage of idea conception while TRL 9 is the stage where technologies are market ready and commercially available. Technologies that are market ready but have not been utilized in a ballast water system context are deemed to be at a TRL 5 or 6. Technologies proven to operate in a ballast water system context are given a TRL of 7 or higher.
Table 1: Technology Readiness Levels
| TRL |
| Description |
| 1. Basic principles observed and reported |
| Lowest level of technology readiness. Scientific research begins to be translated into applied research and development. Example might include paper studies of a technology's basic properties. |
| 2. Technology concept and/or application formulated |
| Invention begins. Once basic principles are observed, practical applications can be invented. The application is speculative and there is no proof or detailed analysis to support the assumption. Examples are still limited to paper studies. |
| 3. Analytical and experimental critical function and/or characteristic proof of concept |
| Active research and development is initiated. This includes analytical studies and laboratory studies to physically validate analytical predictions of separate elements of the technology. Examples include components that are not yet integrated or representative. |
| 4. Component and/or breadboard validation in laboratory environment |
| Basic technological components are integrated to establish that the pieces will work together. This is relatively "low fidelity" compared to the eventual system. Examples include integration of 'ad hoc' hardware in a laboratory. |
| 5. Component and/or breadboard validation in relevant environment |
| Fidelity of breadboard technology increases significantly. The basic technological components are integrated with reasonably realistic supporting elements so that the technology can be tested in a simulated environment. Examples include 'high fidelity' laboratory integration of components. |
| 6. System/subsystem model or prototype demonstration in a relevant environment |
| Representative model or prototype system, which is well beyond the breadboard tested for TRL 5, is tested in a relevant environment. Represents a major step up in a technology's demonstrated readiness. Examples include testing a prototype in a high fidelity laboratory environment or in simulated operational environment. |
| 7. System prototype demonstration in an operational environment |
| Prototype near or at planned operational system. Represents a major step up from TRL 6, requiring the demonstration of an actual system prototype in an operational environment, such as in an aircraft, vehicle or space. Examples include testing the prototype in a test bed aircraft. |
| 8. Actual system completed and 'flight qualified' through test and demonstration |
| Technology has been proven to work in its final form and under expected conditions. In almost all cases, this TRL represents the end of true system development. Examples include developmental test and evaluation of the system in its intended weapon system to determine if it meets design specifications. |
| 9. Actual system 'flight proven' through successful mission operations |
| Actual application of the technology in its final form and under mission conditions, such as those encountered in operational test and evaluation. In almost all cases, this is the end of the last "bug fixing" aspects of true system development. Examples include using the system under operational mission conditions. |
Attachment 1 to BAA
File details come from the government source that posted it. Updated .