Attachment 3 - DP2 TEMPLATE_VOL 2_TECHNICAL VOLUME.pdf

Instruction Page

SDA Small Business Innovation Research (SBIR) and Small Business Technology Transfer (STTR)

DIRECT TO PHASE II TEMPLATE – VOLUME 2:

FEASIBILITY DOCUMENTATION AND TECHNICAL PROPOSAL

These instructions and template apply to the Space Development Agency (SDA) Small Business Innovation Research/Small Business Technology Transfer (SBIR/STTR) Direct to Phase II Opportunities announced under BAA HQ085021S0001.

The template (beginning on the following page) is the format model that may be used to prepare the Direct to Phase II Technical Volume. Do not include the instructions provided on this page or any bracketed [ ] guidance in the template.

Disclosure

Proposers that include in their proposals data which they do not want disclosed to the public for any purpose, or used by the Government except for evaluation purposes, must:

(1) Mark the first page of each Volume of the Submission with the following legend:

"This proposal includes data that must not be disclosed outside the Government and must not be duplicated, used, or disclosed – in whole or in part – for any purpose other than to evaluate this proposal. If, however, a contract is awarded to this offeror as a result of – or in connection with – the submission of this data, the Government has 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 it is obtained from another source without restriction.

The data subject to this restriction are contained in pages [insert numbers or other identification of sheets]"; and

(2) Mark each sheet of data it wishes to restrict with the following legend:

"Use or disclosure of data contained on this page is subject to the restriction on the first page of this volume."

Format

The Technical Volume shall meet the following requirements:

• The Technical Volume must include two parts, Part 1: Feasibility Documentation and Part 2:

Technical Proposal.

• Each part is not to exceed the page count specified in the corresponding SBIR/STTR Opportunity

(SBO), regardless of page content

• Single-column format, single-spaced typed lines

• Standard 8 ½” x 11” paper format

• Page margins one-inch on all sides. A header and footer may be included in the one-inch margin.

• Font style of Times New Roman

• No font smaller than 10-point. For headers, footers, embedded tables, figures, images, or graphics that include text, a font size of smaller than 10-point is allowable, though proposers are cautioned that the text may be unreadable by evaluators.

Unless otherwise noted, any and all content in the Technical Volume will count toward the limit.

The DoD Submission website includes a section labeled Volume 5: Supporting Documents. Volume 5 is provided for small businesses to submit additional documentation to support the Technical Volume (Volume 2) and the Cost Volume (Volume 3). Each SBO will outline any Volume 5 allowances or requirements.

Delete this instruction page and begin the Technical Volume starting with the following page.

Proposal Number [xxx-xxx-xxxx] [Firm Name] BAA Number [HQ085021S0001]

[Remove this statement if not applicable.] Use or disclosure of data contained on this page is subject to the restriction on the first page of this volume.

[Title] Volume 2: Technical Volume

[Note: Remove the disclosure statement below if not applicable to your proposal. Refer to Instructions.] This proposal includes data that must not be disclosed outside the Government and must not be duplicated, used, or disclosed – in whole or in part – for any purpose other than to evaluate this proposal. If, however, a contract is awarded to this offeror as a result of – or in connection with – the submission of this data, the Government has 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 this data if it is obtained from another source without restriction. The data subject to this restriction are contained in pages <insert numbers or other identification of sheets>.

Part 1: Feasibility Documentation [Provide documentation to substantiate that the scientific and technical merit and feasibility described in the Phase I section of the SBO has been met and describes the potential commercial applications. Documentation should include all relevant information including, but not limited to:

technical reports, test data, prototype designs/models, and performance goals/results.

• Maximum page length for feasibility documentation will be specified by the SBO. If you have references, include a reference list or works cited list as the last page of the feasibility documentation. This will count towards the page limit.

• Work submitted within the feasibility documentation must have been substantially performed by the proposer and/or the principal investigator (PI).

• If technology in the feasibility documentation is subject to IP, the proposer must have IP rights.

• Include a one page summary on Commercialization Potential addressing the following:

i. Does the company contain marketing expertise and, if not, how will that expertise be brought into the company?

ii. Describe the potential for commercial (Government or private sector) application and the benefits expected to accrue from this commercialization.

• DO NOT INCLUDE marketing material. Marketing material will NOT be evaluated.]

Part 2: Technical Proposal

1. Identification and Significance of the Problem or Opportunity.

[Define the specific technical problem or opportunity addressed and its importance.]

2. Phase II Technical Objectives.

[Enumerate the specific objectives of the Phase II work, and describe the technical approach and methods to be used in meeting these objectives.]

3. Phase II Statement of Work (include Subcontractors and/or Research Institutions).

[Provide an explicit, detailed description of the Phase II approach. The Statement of Work should indicate what tasks are planned, how and where the work will be conducted, a schedule of major events, and the final product(s) to be delivered. The methods planned to achieve each objective or

[Remove this statement if not applicable.] Use or disclosure of data contained on this page is subject to the task should be discussed explicitly and in detail. This section should be a substantial portion of the Technical Volume section.

Proposers proposing research involving human and/or animal subjects are encouraged to separate these tasks in the technical proposal and cost proposal in order to avoid potential delay of contract award. Please note that funds cannot be released or used on any portion of the project involving human/animal subjects research or activities until all of the proper approvals have been obtained (see Sections 4.7 and 4.8 of HQ085021S0001).]

4. Related Work.

[Describe significant activities directly related to the proposed effort, including any conducted by the PI, the proposer, consultants or others. Describe how these activities interface with the proposed project and discuss any planned coordination with outside sources. The proposal must persuade reviewers of the proposer's awareness of the state of the art in the specific topic. Describe previous work not directly related to the proposed effort but similar. Provide the following: (1) short description, (2) client for which work was performed (including individual to be contacted and phone number), (3) date of completion, and (4) significant results.]

5. Relationship with Future Research or Research and Development.

(a) [State the anticipated results of the proposed approach if the project is successful.

(b) Discuss the significance of the Phase II effort in providing a foundation for a Phase III research and development or commercialization effort.]

6. Key Personnel.

[Identify key personnel who will be involved in the Phase II effort including information on directly related education and experience. A concise technical resume of the PI, including a list of relevant publications (if any), must be included. All resumes count toward the page limit for Volume 2, as specified in the SBO.]

[Principal Investigator Name] [School, Degree, Year]

Relevant Experience [A concise description of the principal investigator’s relevant technical experience and its application to this topic.]

Relevant Awards or Patents [List any awards received or patents granted or applications submitted for work related to this topic.]

Relevant Publications [List any publications relevant to this topic.]

[Repeat this format as necessary to address the qualifications of all key personnel.]

7. Foreign Citizens.

[Remove this statement if not applicable.] Use or disclosure of data contained on this page is subject to the

[Identify any foreign citizens or individuals holding dual citizenship expected to be involved on this project as a direct employee, subcontractor, or consultant. For these individuals, please specify their country of origin, the type of visa or work permit under which they are performing and an explanation of their anticipated level of involvement on this project. Refer to section 3.2 of HQ085021S0001for more information. Supplemental information provided in response to this paragraph will be protected in accordance with the Privacy Act (5 U.S.C. 552a), if applicable, and the Freedom of Information Act (5 U.S.C. 552(b)(6)). Note: If no foreign nationals will be involved in proposed work, the word “None” can be substituted for the table.]

Name [include direct employees, subcontractors, and consultants]

Foreign National (Yes/No)

Country of Origin

Type of Visa or Work Permit

Level of Involvement

(Role)

8. Facilities/Equipment.

[Describe available instrumentation and physical facilities necessary to carry out the Phase II effort. Justify equipment purchases in this section and include detailed pricing information in the Cost Volume. State whether or not the facilities where the proposed work will be performed meet environmental laws and regulations of federal, state and local Governments for, but not limited to, the following groupings: airborne emissions, waterborne effluents, external radiation levels, outdoor noise, solid and bulk waste disposal practices and handling and storage of toxic and hazardous materials.]

9. Subcontractors/Consultants.

[Involvement of a university or other subcontractors or consultants in the project may be appropriate. If such involvement is intended, it should be identified and described according to the Cost Breakdown Guidance offered in HQ085021S0001. For Phase II/Direct to Phase II, a minimum of one-half (50%) of the research and/or analytical work, as measured by direct and indirect costs, must be carried out by the proposing small business firm, unless otherwise approved in writing by the Contracting Officer. SBIR efforts may include subcontracts with Federal Laboratories and Federally Funded Research and Development Centers (FFRDCs). A waiver is no longer required for the use of Federal Laboratories and FFRDCs; however, proposers must certify their use of such facilities in Volume 1: Proposal Cover Sheet.

Subcontracts with other Federal organizations are not permitted. Note that universities cannot publically release information related to Export Controlled/ITAR restricted SBOs. (See Section 3 of HQ085021S0001 for detailed eligibility requirements as it pertains to the use of subcontractors/consultants.)

10. Prior, Current or Pending Support of Similar Proposals or Awards.

[If a proposal submitted in response to a corresponding SBO is substantially the same as another proposal that was funded, is now being funded, or is pending with another Federal Agency, or

[Remove this statement if not applicable.] Use or disclosure of data contained on this page is subject to the another DoD Component or SDA, you must reveal this on Volume 1: Proposal Cover Sheet and provide the following information:

a) Name and address of the Federal Agency(s) or DoD Component to which a proposal was submitted, will be submitted, or from which an award is expected or has been received.

b) Date of proposal submission or date of award.

c) Title of proposal.

d) Name and title of the PI for each proposal submitted or award received .

e) Title, number, and date of BAA(s) or solicitation(s) under which the proposal was submitted, will be submitted, or under which award is expected or has been received.

f) If award was received, state contract number.

g) Specify the applicable topics for each proposal submitted or award received.

Note: If this does not apply, state in the proposal "No prior, current, or pending support has been provided for proposed work."]

11. Commercialization Strategy.

[SDA is interested in dual use commercialization of SBIR/STTR projects that result in products sold to the U.S. military, the private sector market, or both, and expects explicit discussion of key activities to achieve this result in the commercialization strategy part of the proposal.

The Phase II commercialization strategy shall not exceed 5 pages, and will NOT count against the proposal page limit. The commercialization strategy should include the following elements:

a) Prior Transition and Commercialization Activities. Provide a summary of transition and commercialization activities conducted during Phase I, and the Technology Readiness Level (TRL) and/or Manufacturing Readiness Level (MRL) achieved. Discuss how the preliminary transition and commercialization path or paths may evolve during the Phase II project.

Describe key proposed technical milestones during Phase II that will advance the technology towards product such as: prototype development, laboratory and systems testing, integration, testing in operational environment, and demonstrations.

b) Problem or Need Statement. Briefly describe the problem, need, or requirement, and its significance relevant to a Department of Defense application and/or a private sector application that the SBIR/STTR project results would address.

c) Description of Product(s) and/or System Application(s). Identify the commercial product(s) and/or DoD system(s), or system(s) under development, or potential new system(s). Identify the potential DoD end users, Federal customers, and/or private sector customers who would likely use the technology.

d) Business Model(s)/Procurement Mechanism(s). Discuss your current business model hypothesis for bringing the technology to market. Describe plans to license, partner, or self-produce your product. How do you plan to generate revenue?

e) Target Market. Describe the market and customer sets you propose to target, their size, their growth rate, and their key reasons they would consider procuring the technology. Describe competing technologies existent today on the market as well as those being developed in the lab.

[Remove this statement if not applicable.] Use or disclosure of data contained on this page is subject to the

f) Funding Requirements. Describe your company’s funding history. How much external financing have you raised? Describe your plans for future funding sources (internal, loan, angel, venture capital, etc.).

g) Commercialization Risks. Describe the major technology, market and team risks associated with achieving successful transition of the technology. SDA embraces risks in cases where performers demonstrate an understanding of the risks and communicate a clear mitigation strategy.

h) Expertise/Qualifications of Team/Company Readiness. Describe the expertise and qualifications of your management, marketing/business development and technical team that will support the transition of the technology from the prototype to the commercial market and into government operational environments. Has this team previously taken similar products/services to market? If the present team does not have this needed expertise, how do you intend to obtain it? What is the financial history and health of your company (e.g., availability of cash, profitability, revenue growth, etc.)?

i) Anticipated Commercialization Results. Include a schedule showing the anticipated quantitative commercialization results from the Phase II project at one year after the start of Phase II, at the completion of Phase II, and after the completion of Phase II (i.e., amount of additional investment, sales revenue, etc.). After Phase II award, the company is required to report actual sales and investment data in its Company Commercialization Report at least annually.

Advocacy Letters (OPTIONAL): * Feedback received from potential Commercial and/or DoD customers and other end-users regarding their interest in the technology to support their capability gaps.

Letters of Intent/Commitment (OPTIONAL): * Relationships established, feedback received, support and commitment for the technology with one or more of the following: Commercial customer, DoD PM/PEO, a Defense Prime, or vendor/supplier to the Primes and/or other vendors/suppliers identified as having a potential role in the integration of the technology into fielded systems/products or those under development.

*Advocacy Letters and Letters of Intent/Commitment are optional, and should ONLY be submitted to substantiate any transition or commercialization claims made in the commercialization strategy. Please DO NOT submit these letters just for the sake of including them in your proposal. These letters DO NOT count against any page limit. Letters that are faxed or e-mailed separately will NOT be accepted.

In accordance with section 3-209 of DOD 5500.7-R, Joint Ethics Regulation, letters from government personnel will NOT be considered during the evaluation process.]

12. Technical Data Rights.

[Rights in technical data, including software, developed under the terms of any contract resulting from proposals submitted in response to this BAA, generally remain with the contractor, except that the Government obtains a royalty-free license to use such technical data only for Government purposes during the period commencing with contract award and ending twenty years after completion of the project under which the data were generated. This data should be marked with

[Remove this statement if not applicable.] Use or disclosure of data contained on this page is subject to the the restrictive legend specified in DFARS 252.227-7018 Class Deviation 2020-O0007. Upon expiration of the twenty-year restrictive license, the Government has unlimited rights to the SBIR data. During the license period, the Government may not release or disclose SBIR data to any person other than its support services contractors except: (1) For evaluation purposes; (2) As expressly permitted by the contractor; or (3) A use, release, or disclosure that is necessary for emergency repair or overhaul of items operated by the Government. See DFARS clause 252.227- 7018 Class Deviation 2020-O0007, “Rights in Noncommercial Technical Data and Computer Software – Small Business Innovation Research (SBIR) Program.”

If a proposer plans to submit assertions in accordance with DFARS 252.227-7017 Class Deviation 2020-O0007, those assertions must be identified and assertion of use, release, or disclosure restriction MUST be included with your proposal submission. The contract cannot be awarded until assertions have been approved. Regardless of the final type of instrument for award, provide any assertions stated above.

The following instructions apply to the fields in the table below (Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of Technical Data or Computer Software).

1) For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such item, component, or process. For computer software or computer software documentation identify the software or documentation.

2) Generally, development at private expense, either exclusively or partially, is the only basis for asserting restrictions. For technical data, other than computer software documentation, development refers to development of the item, component, or process to which the data pertain. The Government's rights in computer software documentation generally may not be restricted. For computer software, development refers to the software. Indicate whether development was accomplished exclusively or partially at private expense. If development was not accomplished at private expense, or for computer software documentation, enter the specific basis for asserting restrictions.

3) Enter asserted rights category (e.g., Government purpose license rights from a prior contract, rights in SBIR/STTR data generated under another contract, limited, restricted, or government purpose rights under this or a prior contract, or specially negotiated licenses).

4) Corporation, individual, or other person, as appropriate.

5) Enter “none” when all data or software will be submitted without restrictions.]

The Offeror asserts for itself, or the persons identified below, that the Government's rights to use, release, or disclose the following technical data or computer software should be restricted:

https://www.acq.osd.mil/dpap/policy/policyvault/USA000244-20-DPC.pdf https://www.acq.osd.mil/dpap/policy/policyvault/USA000244-20-DPC.pdf

[Remove this statement if not applicable.] Use or disclosure of data contained on this page is subject to the

Technical Data or Computer Software to be

Furnished with Restrictions

Basis for Assertion Asserted Rights Category

Name of Person or Organization

Asserting Restrictions

[(LIST)] [(LIST)] [(LIST)] [(LIST)]

[Completion of this table and submission of the proposal constitutes signature for the information listed in the table above.]