T2 BMC Call BAA Section V.B.3 Volume 1, Section 2 - Updated Proposal Instructions.pdf

MODIFIED PROPOSAL INSTRUCTIONS FOR T2 BMC3 MODULE COMPUTE CONCEPT

CAPABILITIES STUDIES ONLY

Section II: Summary of Proposal {NTE 4}

Note: The Summary of Proposal should not have any unique information not contained in the Detailed Proposal Information.

(1) Innovation: Succinctly describe the uniqueness and benefits of the proposed research relative to the existing body of research and industry work. Provide a basic description of the scientific or technical basis for the innovative claims.

(2) Results: Provide a short description of the deliverables associated with the proposed research – discuss the results, products, transferable technology, and transition path. i. Include in this section all proprietary claims to the results, prototypes, intellectual property, or systems supporting and/or necessary for the use of the research, results, and/or prototype. If there are no proprietary claims, this should be stated. For forms to be completed regarding intellectual property, see Section V.C.f of this BAA. There will be no page limit for the listed forms.

ii. Proposers responding to this BAA must submit a separate list of all technical data or computer software that will be furnished to the Government with other than unlimited rights. The Government will assume unlimited rights if proposers fail to identify any intellectual property restrictions in their proposals.

(3) Technical Rationale: Provide a short description of the impact of the proposed development on military mission capabilities, efficiency, or effectiveness.

i. Should include general discussion of other research in this area.

ii. The purpose of this section is to explain why the specific technical approach you chose is superior to other technical approaches. This section is not intended to expand on the military utility of your concept.

(4) Technical Approach: Provide a short description of the technical approach and constructive plan for accomplishment of technical goals in support of innovative claims and deliverable production.

(5) Experience: Describe the unique capabilities of project and corporate team members. Describe the proposer’s previous accomplishments and work in closely related research areas.

(6) Cost: Cost, schedule and measurable milestones for the proposed research, including estimates of cost for each task in each year of the effort delineated by the prime and major subcontractors, total cost and company cost share, if applicable. (Note: Measurable milestones should capture key development points in tasks and should be clearly articulated and defined in time relative to start of effort.)

Section III: Detailed Proposal Information {NTE 11, or NTE 21 if proposal total value exceeds $1 million}

(d) Statement of Work (SOW) In plain English, clearly define the technical tasks/subtasks to be performed, their durations, and dependencies among them. The page length for the SOW will be dependent on the amount of the effort. For each task/subtask, provide:

(1) A general description of the technical objective (for each defined task/activity);

(2) A detailed description of the approach to be taken to accomplish each defined task/activity in support of the innovative claims and deliverable production;

(3) Identification of the primary organization responsible for task execution (prime, sub, team member, by name, etc.);

(4) A top-level schedule for all major tasks and the completion criteria for each task/activity (a product, event or milestone that defines its completion). Please include where the effort could be partitioned into initial and future phases – future phases should be identified as options.

(5) Define all deliverables (reporting, data, reports, hardware, software, technology, products, etc.) to be provided to the Government in support of the proposed tasks/activities; and

(6) Clearly identify any tasks/subtasks (to be performed by either an awardee or subawardee) that will be accomplished on-campus at a university, if applicable.

Note: It is recommended that the SOW should be developed so that each Phase of the program is separately defined. The SOW is not included as part of the Volume I page limit. Do not include any proprietary information in the SOW.

(e) Technical Rationale:

(1) Provide the technical rationale for the objective requirement, including technology advancements and value-added to DoD capabilities and SDA’s proliferated architecture.

(2) Provide technical rationale, scientific basis, and any supporting analysis for the technical approach for each major task/activity.

(3) Provide a comparison of the technical objectives and technical approach with other ongoing research and existing state-of-the-art, indicating advantages and disadvantages of the proposed effort.

(f) Risk and Risk Reduction

(1) Provide an initial list of critical cost, schedule, technical and programmatic risk areas.

(2) Describe the formal process for identifying and tracking the risk elements that translate into critical and unique technologies, processes and system attributes associated with a technology objective.

(3) For each proposed risk reduction task: i. Provide a detailed discussion of the objectives of each of the proposed risk reduction tasks as well as quantifiable success metrics.

ii. Describe the approach for each risk reduction task.

iii. Describe the value of performing the risk reduction activities during the initial phase, as opposed to deferring them until future phases.

(4) Describe the process for identifying and evaluating applicable technologies available from other Government and industry R&D programs.

(5) Address mitigation of life-cycle and sustainment risks associated with transitioning intellectual property for U.S. military applications, if applicable.

(g) Results

(1) Describe the results, products, transferable technology and expected technology transfer/transition paths.

(2) Provide a description of all proprietary claims to the results, prototypes, intellectual property, or systems. If there are no proprietary claims, this should be stated. For forms to be completed regarding intellectual property, see Section

V.B.4.g – Intellectual Property. There will be no page limit for the listed forms.

(h) Organization

(1) Describe the programmatic relationship of corporate team members.

(2) Describe the responsibilities of corporate and project team members.

(3) Describe the teaming strategy among the team members.

(4) Identify the key personnel by name and include descriptions of their roles. SDA requires key personnel identified in the proposal to be assigned as proposed, and the resulting contract/agreement will indicate no substitution shall be made without prior approval of the Government.

(5) Describe the proposer’s previous accomplishments and work in closely related research areas.

(6) Submit a clearly defined organization chart for the project team which includes, as applicable:

• The programmatic relationship of team members; • The unique capabilities of team members;

• The task of responsibilities of team members;

• The teaming strategy among the team members; and

• The key personnel along with the amount of effort to be expended by each person during each year.

(i) Facilities

(1) Provide a description of any unique facilities necessary for execution of the proposed effort that would be used for the proposed effort.

(j) Project Management:

(1) Management Plan: i. Describe program management process that will be utilized to achieve the technical objective.

ii. Include a description of how the team will function and share technical and financial information among the team members and with the Government.

iii. Provide short (not to exceed one (1) page) résumés for the key personnel in key disciplines/risk areas.

(2) Schedule: Provide a detailed integrated schedule of all initial phase activities, including risk reduction tasks.

Proposals below $1 million shall provide an Integrated Master Schedule (IMS) at a minimum at WBS Level 2.

Proposals that exceed $1 million (total proposed value, regardless of potential cost share) shall provide an IMS at WBS Level 3.

i. Measurable critical milestones should occur no less than quarterly after the start of the effort. Additional interim non-critical management milestones are also highly encouraged at regular intervals. Milestones must not include proprietary information.

ii. Top-level schedules are required for optional phases and should be based on the proposer’s initial risk reduction strategy.

iii. Include key events and demonstrations as appropriate for the technology concept. An electronic copy of the IMS in MS Project or Project-compatible format shall be included with proposal submissions.

iv. All tasks in the IMS shall be linked and the ability to display the critical path shall be implemented.