DARPA-BAA-15-33_PRIGM-NGIMU_Amendment_01_Final_For_Posting_6May2015.pdf

Broad Agency Announcement Precise Robust Inertial Guidance for Munitions (PRIGM):

Navigation-Grade Inertial Measurement Unit (NGIMU) Microsystems Technology Office

DARPA-BAA-15-33

April 15, 2015

(Amendment No. 01: As amended through 6 May 2015)

Table of Contents

Part I: Overview Information

Sec. I: FUNDING OPPORTUNITY DESCRIPTION A. Background and Description B. Program Objective C. Program Structure and Metrics D. Deliverables

Sec. II. AWARD INFORMATION Sec. III: ELIGIBILITY INFORMATION

A. Eligible Applicants B. Procurement Integrity, Standards of Conduct, Ethical Considerations, and

Organizational Conflicts of Interest C. Cost Sharing/Matching D. Other Eligibility Criteria

Sec. IV: APPLICATION AND SUBMISSION INFORMATION A. Address to Request Application Package B. Content and Form of Application Submission

1. Security Information

2. Proprietary Information

3. Proposal Submission Information

4. Full Proposal Format

5. Submission Dates and Times

6. Funding Restrictions

7. Other Submission Requirements Not Applicable

Sec. V: APPLICATION REVIEW INFORMATION A. Evaluation Criteria B. Review and Selection Process

Sec. VI: AWARD ADMINISTRATION INFORMATION A. Selection Notices B. Administrative and National Policy Requirements

1. Meeting and Travel Requirements

2. Human Subjects Research

3. Animal Use

4. Export Control

5. Subcontracting

6. Electronic and Information Technology

7. Employment Eligibility Verification

8. Additional Requirement and Responsibilities relating to Alleged Crimes by or against Contractor Personnel in Iraq and Afghanistan

9. System for Award Management (SAM) Registration and Universal Identifier

Requirements

10. Reporting Executive Compensation and First-Tier Subcontract Awards

11. Updates of Information Regarding Responsibility Matters

12. Representation by Corporations Regarding an Unpaid Delinquent Tax Liability or a Felony Conviction under any Federal Law

13. Cost Accounting Standards (CAS) Notices and Certification

14. Controlled Unclassified Information (CUI) on Non-DoD Information Systems

15. Safeguarding of Unclassified Controlled Technical Information

C. Reporting D. Electronic Systems

1. Representations and Certifications

2. Wide Area Work Flow (WAWF)

3. i-Edison

Sec. VII: AGENCY CONTACTS Sec. VIII: OTHER INFORMATION

A. Intellectual Property Procurement Contract Proposers

1. Noncommercial Items (Technical Data and Computer Software)

2. Commercial Items (Technical Data and Computer Software)

B. Non-Procurement Contract Proposers – Noncommercial and Commercial Items (Technical Data and Computer Software)

C. All Proposers – Patents D. All Proposers – Intellectual Property Representations E. Other Transactions (OTs):

Part I: Overview Information

• Federal Agency Name – Defense Advanced Research Projects Agency (DARPA), Microsystems Technology Office (MTO)

• Funding Opportunity Title – PRIGM:NGIMU

• Announcement Type – Initial Broad Agency Announcement (BAA)

• Funding Opportunity Number – DARPA-BAA-15-33

• Catalog of Federal Domestic Assistance Numbers (CFDA) – Not applicable

• Dates o Posting Date: April 15, 2015 o Proposers’ Day: April 17, 2015 o Full Proposal Deadline: June 3, 2015 o Estimated period of performance start: November 4, 2015

• Concise description of the funding opportunity: DARPA is soliciting research proposals in the development of navigation-grade inertial measurement units (IMUs) based on microelectromechanical systems (MEMS) technology. The objective of the PRIGM:NGIMU program is to develop navigation-grade inertial measurement units (NGIMU) by integrating MEMS gyroscopes and accelerometers into small form factor IMUs. PRIGM:NGIMU deliverables will provide drop-in replacements for currently deployed tactical-grade MEMS IMUs.

• Total amount of money available to be awarded: $25M - $30M

• Anticipated individual awards – Multiple awards are anticipated.

• Funding type – Program is anticipated to be funded in its entirety with 6.3 funds.

• Types of instruments that may be awarded – Procurement contract or other transaction.

• Any cost sharing requirements – None.

• Agency contact o Dr. Robert Lutwak, Program Manager

DARPA/MTO

BAA Coordinator: DARPA-BAA-15-33@darpa.mil

ATTN: DARPA-BAA-15-33

675 North Randolph Street Arlington, VA 22203-2114

PROPOSERS ARE CAUTIONED THAT EVALUATION RATINGS MAY BE LOWERED

AND/OR PROPOSALS REJECTED IF PROPOSAL PREPARATION (PROPOSAL FORMAT,

CONTENT, ETC.) AND/OR SUBMITTAL INSTRUCTIONS ARE NOT FOLLOWED.

mailto:name@darpa.mil

Part II: Full Text of Announcement

Sec. I: FUNDING OPPORTUNITY DESCRIPTION

The Defense Advanced Research Projects Agency (DARPA) is soliciting research proposals in the area of navigation-grade inertial measurement units (IMUs) based on microelectromechanical systems (MEMS) technology.

This BAA is being issued, and any resultant selection will be made, using procedures under Federal Acquisition Regulation (FAR) 35.016. Any negotiations and/or awards will use procedures under FAR 15.4, Contract Pricing, as specified in the BAA. Proposals received as a result of this BAA shall be evaluated in accordance with evaluation criteria specified herein through a scientific review process.

DARPA BAAs are posted on the Federal Business Opportunities (FedBizOpps) website, http://www.fbo.gov/. The following information is for those wishing to respond to this BAA.

A. Background and Description The DoD relies on GPS for ubiquitous and accurate positioning, navigation, and timing (PNT).

With the increased prevalence of intentional jamming, spoofing, and other threats to GPS signal integrity, access to robust GPS-based PNT is increasingly unassured in contested theaters and alternative sources of PNT are required. In particular, navigation of guided munitions represents the most immediate and demanding of GPS-denial challenges, due to the necessity of operating in highly contested theaters and the stringent requirements for minimization of cost, size, weight, and power consumption (CSWaP).

The Precise Robust Inertial Guidance for Munitions (PRIGM) program addresses the challenge of providing precise navigation of low-CSWaP platforms based on trajectory information provided by a high-performance inertial measurement unit (IMU).

Inertial navigation in three dimensions requires a minimal six degree-of-freedom IMU typically comprising six inertial sensors, e.g. three gyroscopes and three accelerometers. IMU performance, and thereby mission duration and circular error probability (CEP), is determined by individual sensor performance due to the relative importance of orientation in determining path of motion. Ring laser gyroscopes (RLGs) and interferometric fiber optic gyroscopes (IFOGs) emerged as practical, reduced-SWaP alternatives to conventional spinning-mass gyroscopes in the 1970s. While RLG/iFOG remains the technology of choice for high-value, high-CSWaP platforms, the vast majority of platform navigation requirements are driven by even lower CSWaP requirements. In the early 2000s, the U.S. Army led an effort to develop low-CSWaP IMUs based on microelectromechanical systems (MEMS) gyroscopes and accelerometers.

MEMS-based IMUs have been widely deployed across DoD and exhibit tactical-grade performance, which is capable of supporting inertial navigation of glide munitions with 10-meter circular error probable (CEP) for roughly 30 seconds. Thus, MEMS IMUs cannot maintain sufficient navigation accuracy for most missions unless augmented by GPS. In comparison, navigation-grade RLGs and iFOGs support autonomous navigation of glide munitions for up to 180 seconds. Recent developments, particularly under the DARPA Micro-technology for http://www.fbo.gov/

Positioning, Navigation & Timing (micro-PNT) program, have demonstrated laboratory prototype MEMS inertial sensors with performance levels approaching navigation grade.

However, significant research and development will be necessary to consistently and reproducibly realize robust MEMS gyroscopes and accelerometers that meet the performance objectives of this program and to integrate these devices into robust deployable IMUs.

B. Program Objective The objective of the PRIGM:NGIMU program is to develop navigation-grade inertial measurement units (NGIMUs) by integrating revolutionary MEMS gyroscopes and accelerometers into small form factor IMUs. The resulting PRIGM:NGIMU prototypes will be mechanical and electronic drop-in replacements for currently deployed tactical-grade MEMS IMUs. At the conclusion of the program, performers will deliver prototype IMUs capable of being tested in a simulated DoD environment while meeting the technical objectives in Table 1, below:

Table 1: PRIGM:NGIMU Program Objectives

Performance Metric Objective Units

Volume 82 cm

Weight 160 g

Power < 3 W

Operating temperature range -54 to +85 °C

Vibration DC to 2 kHz 7.7 gRMS

Shock survivability1 20,000 g

Bandwidth (min. @ -90° phase lag) 70 Hz

Gyroscope

Operating range ± 900 °/sec

Turn-on to turn-on bias repeatability2 0.01 °/hr, 1σ

Bias environmental sensitivity3 0.01 °/hr, 1σ

Scale factor repeatability4 5 ppm

Scale factor environmental sensitivity5 5 ppm

Accelerometer

Operating range ± 60 g

Turn-on to turn-on bias repeatability2 25 µg, 1σ

Bias environmental sensitivity3 25 µg, 1σ

Scale factor repeatability4 25 ppm

Scale factor environmental sensitivity5 25 ppm

Stability Specifications (Allan Deviation)6 τ [sec] Gyroscope σΩ(τ) [°/hr] Accelerometer σa(τ) [mg]

0.1 0.66 0.19

1 0.21 0.06

10 0.066 0.01

100 0.021 0.01

1000 0.01 0.01

1 0.5 – 15 msec, half-sine 2 4 hours on, 24 hours off, 4 hours on 3 -54°C to +85°C, 0-7.7 gRMS

(MIL-Std-810G minimum integrity test)

4 Relative to baseline scale factor, 4 hours on, 24 hours off, 4 hours on 5 Relative to baseline scale factor, -54°C to +85°C 6 -54°C to +85°C, maximum rate 3°C/minute

Program Milestones

The following milestones are based on the metrics outlined in Table 1. NGIMU prototypes must be designed in accordance with the baseline interface control document (ICD) and drawings (Attachments 3, 4). The ICD and system specifications will be refined throughout the program, based on inputs from government personnel and performers, to ensure that the NGIMU satisfies the most diverse set of DoD platforms.

Phase I (18 months)

Demonstrate MEMS-based gyroscopes and accelerometers meeting performance and environmental requirements defined by Table 1, including simulated, relevant military environments as described in Mil-Std 810G. A minimum of five each of prototype gyroscopes and accelerometers will be delivered to the government.

Phase II (12 months)

Demonstrate MEMS-based, navigation-grade, integrated IMU meeting SWaP and performance metrics defined in Table 1, excluding environmental requirements and shock survival. The IMU must be form, fit, and function compatible with the final program objectives. A minimum of two NGIMUs will be delivered to the government.

Phase III (12 months)

Successful development and demonstration of MEMS-based, navigation-grade IMUs meeting all requirements of Table 1, including environmental and shock survivability. A minimum of 10 prototype NGIMUs will be delivered to the government at the end of Phase III to be tested in a simulated, relevant DoD environment.

C. Program Structure and Metrics

Subject to availability of funding, the PRIGM:NGIMU program is expected to have an overall duration of 42 months. Proposers must identify measurable quantitative milestones throughout the full program duration, with each phase separately defined. These milestones must define a credible trajectory towards achieving the individual phase objectives and final program goals outlined above.

Performance will be continually evaluated based on the likelihood that progress will lead to achievement of the final program goals. DARPA does not guarantee continued funding (e.g., incremental funding within a phase or the exercise of a Phase option) in the event that intermediate milestones are not accomplished or if it should be determined that substantial progress is unlikely.

D. Deliverables

Proposals should include a detailed schedule of deliverables for independent assessment by the Government throughout the program. Proposers are especially encouraged to define test articles and deliverables that provide important benchmarks and indicate progress against the highest risk elements of their approach. The proposed deliverables should be consistent with government evaluation of the proposed goals.

Phase I: A minimum of five each of prototype gyroscopes and accelerometers will be delivered by month 16 of Phase I. Prototype sensors will be compatible with the universal inertial test system (UITS) platform used by approved government test facilities (Attachment 5).

Performance data will be provided to the government prior to delivery and initial evaluation at a DoD test lab.

Phase II: A minimum of two NGIMU prototypes will be delivered to an approved government test facility for independent evaluation against the performance objectives. Performance data will be provided to the government prior to delivery and initial evaluation at a DoD test lab.

Phase III: A minimum of 10 NGIMUs meeting performance objectives will be delivered at the end of Phase III. At the conclusion of Phase III, performers will provide DARPA with a firm fixed-price quotation to deliver an additional 50 NGIMUs.

Deliverables in each phase include quarterly technical and financial reports, support for quarterly reviews via teleconference, attendance and support to semi-annual program reviews, and a final report at the end of each phase.

Sec. II. AWARD INFORMATION

Multiple awards are anticipated. The amount of resources made available under this BAA will depend on the quality of the proposals received and the availability of funds.

The Government reserves the right to select for negotiation all, some, one, or none of the proposals received in response to this solicitation, and to make awards without discussions with proposers. The Government also reserves the right to conduct discussions if it is later determined to be necessary. If warranted, portions of resulting awards may be segregated into pre-priced options. Additionally, DARPA reserves the right to accept proposals in their entirety or to select only portions of proposals for award. In the event that DARPA desires to award only portions of a proposal, negotiations may be opened with that proposer. The Government reserves the right to fund proposals in phases with options for continued work at the end of one or more of the phases.

Awards under this BAA will be made to proposers on the basis of the evaluation criteria listed below (see section labeled “Application Review Information”, Sec. V.), and program balance to provide overall value to the Government. The Government reserves the right to request any additional, necessary documentation once it makes the award instrument determination. Such additional information may include but is not limited to Representations and Certifications. The Government reserves the right to remove proposers from award consideration should the parties fail to reach agreement on award terms, conditions and cost/price within a reasonable time or the proposer fails to timely provide requested additional information. Proposals identified for negotiation may result in a procurement contract or other transaction, depending upon the nature of the work proposed, the required degree of interaction between parties, whether or not the research is classified as Fundamental Research, and other factors.

In all cases, the Government contracting officer shall have sole discretion to select award instrument type and to negotiate all instrument terms and conditions with selectees. Proposers are advised that if they propose cooperative agreements, DARPA may select other award instruments, as it deems appropriate. DARPA will apply publication or other restrictions, as necessary, if it determines that the research resulting from the proposed effort will present a high likelihood of disclosing performance characteristics of military systems or manufacturing technologies that are unique and critical to defense. Any award resulting from such a determination will include a requirement for DARPA permission before publishing any information or results on the program. For more information on publication restrictions, see the section below on Fundamental Research.

Fundamental Research It is DoD policy that the publication of products of fundamental research will remain unrestricted to the maximum extent possible. National Security Decision Directive (NSDD) 189 established the national policy for controlling the flow of scientific, technical, and engineering information produced in federally funded fundamental research at colleges, universities, and laboratories. The Directive defines fundamental research as follows:

'Fundamental research' means basic and applied research in science and engineering, the results of which ordinarily are published and shared broadly within the scientific community, as distinguished from proprietary research and from industrial development, design, production, and product utilization, the results of which ordinarily are restricted for proprietary or national security reasons."

As of the date of publication of this BAA, the Government expects that program goals as described herein either cannot be met by proposers intending to perform fundamental research or the proposed research is anticipated to present a high likelihood of disclosing performance characteristics of military systems or manufacturing technologies that are unique and critical to defense. Therefore, the Government anticipates restrictions on the resultant research that will require the contractor to seek DARPA permission before publishing any information or results relative to the program.

Proposers should indicate in their proposal whether they believe the scope of the research included in their proposal is fundamental or not. While proposers should clearly explain the intended results of their research, the Government shall have sole discretion to select award instrument type and to negotiate all instrument terms and conditions with selectees. Appropriate clauses will be included in resultant awards for non-fundamental research to prescribe publication requirements and other restrictions, as appropriate.

For certain research projects, it may be possible that although the research being performed by the prime contractor is restricted research, a subcontractor may be conducting contracted fundamental research. In those cases, it is the prime contractor’s responsibility to explain in their proposal why its subcontractor’s effort is contracted fundamental research.

The following statement or similar provision will be incorporated into any resultant non-fundamental research procurement contract or other transaction:

There shall be no dissemination or publication, except within and between the contractor and any subcontractors, of information developed under this contract or contained in the reports to be furnished pursuant to this contract without prior written approval of DARPA’s Public Release Center (DARPA/PRC). All technical reports will be given proper review by appropriate authority to determine which Distribution Statement is to be applied prior to the initial distribution of these reports by the contractor. With regard to subcontractor proposals for Contracted Fundamental Research, papers resulting from unclassified contracted fundamental research are exempt from prepublication controls and this review requirement, pursuant to DoD Instruction 5230.27 dated October 6, 1987.

When submitting material for written approval for open publication, the contractor/awardee must submit a request for public release to the PRC and include the following information: (1) Document Information: document title, document author, short plain-language description of technology discussed in the material (approx. 30 words), number of pages (or minutes of video) and document type (e.g., briefing, report, abstract, article, or paper); (2) Event Information: event type (conference, principal investigator meeting, article or paper), event date, desired date for DARPA's approval;

(3) DARPA Sponsor: DARPA Program Manager, DARPA office, and contract number;

and (4) Contractor/Awardee's Information: POC name, e-mail and phone. Allow four weeks for processing; due dates under four weeks require a justification. Unusual electronic file formats may require additional processing time. Requests may be sent either by-mail to prc@darpa.mil or via 675 North Randolph Street, Arlington VA 22203- 2114, telephone (571) 218-4235. Refer to the following for link for information about DARPA’s public release process:

http://www.darpa.mil/NewsEvents/Public_Release_Center/Public_Release_Center.aspx.

Sec. III: ELIGIBILITY INFORMATION

All responsible sources capable of satisfying the Government's needs may submit a proposal that shall be considered by DARPA.

A. Eligible Applicants

1. Federally Funded Research and Development Centers (FFRDCs) and Government entities (e.g., Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they meet the following conditions: (1) FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector. (2) FFRDCs must provide a letter on official letterhead from their sponsoring organization citing the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and their compliance with the associated FFRDC sponsor agreement and terms and conditions. This information is required for FFRDCs proposing to be prime contractors or subcontractors. Government entities must clearly demonstrate that the work is not otherwise available from the private sector and provide written documentation citing the specific statutory authority and contractual authority, if relevant, establishing their ability to propose to Government solicitations. At the present time, DARPA does not consider 15 U.S.C. § 3710a to be sufficient legal authority to show eligibility. While 10 U.S.C.§ 2539b may be the appropriate statutory starting point for some entities, specific supporting regulatory guidance, together with evidence of agency approval, will still be required to fully establish eligibility. DARPA will consider FFRDC eligibility submissions on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the proposer.

2. Non-U.S. organizations and/or individuals may participate to the extent that such participants comply with any necessary nondisclosure agreements, security mailto:prc@darpa.mil regulations, export control laws, and other governing statutes applicable under the circumstances.

B. Procurement Integrity, Standards of Conduct, Ethical Considerations, and

Organizational Conflicts of Interest Current federal employees are prohibited from participating in particular matters involving conflicting financial, employment, and representational interests (18 U.S.C. §§ 203, 205, and 208). Once the proposals have been received, and prior to the start of proposal evaluations, the Government will assess potential conflicts of interest and will promptly notify the proposer if any appear to exist. The Government assessment does NOT affect, offset, or mitigate the proposer’s responsibility to give full notice and planned mitigation for all potential organizational conflicts, as discussed below.

Without prior approval or a waiver from the DARPA Director, in accordance with FAR 9.503, a contractor cannot simultaneously provide scientific, engineering, technical assistance (SETA) or similar support and also be a technical performer. As part of the proposal submission, all members of the proposed team (prime proposers, proposed subcontractors, and consultants) must affirm whether they (their organizations and individual team members) are providing SETA or similar support to any DARPA technical office(s) through an active contract or subcontract. All affirmations must state which office(s) the proposer, subcontractor, consultant, or individual supports and identify the prime contract number(s). All facts relevant to the existence or potential existence of organizational conflicts of interest (FAR 9.5) must be disclosed. The disclosure must include a description of the action the proposer has taken or proposes has taken to avoid, neutralize, or mitigate such conflict. If in the sole opinion of the Government after full consideration of the circumstances, a proposal fails to fully disclose potential conflicts of interest and/or any identified conflict situation cannot be effectively mitigated, the proposal will be rejected without technical evaluation and withdrawn from further consideration for award.

If a prospective proposer believes a conflict of interest exists or may exist (whether organizational or otherwise) or has questions on what constitutes a conflict of interest, the proposer should send his/her contact information and a summary of the potential conflict to DARPA-BAA-15-33@darpa.mil before time and effort are expended in preparing a proposal and mitigation plan.

C. Cost Sharing/Matching Cost sharing is not required. However, given the high potential for commercial application arising from this program, cost sharing is encouraged, particularly to the extent that it contributes to rapid transition of the technology to manufacturing and commercial availability, e.g. through capital investment in manufacturing or test infrastructure.

D. Other Eligibility Criteria

1. Collaborative Efforts Collaborative efforts/teaming are encouraged.

Sec. IV: APPLICATION AND SUBMISSION INFORMATION

A. Address to Request Application Package This solicitation contains all information required to submit a proposal. No additional forms, kits, or other materials are needed. This notice constitutes the total BAA solicitation. No additional information is available, except as provided at FBO.gov, nor will a formal Request for Proposal (RFP) or additional solicitation regarding this announcement be issued. Requests for the same will be disregarded.

B. Content and Form of Application Submission DARPA policy is to treat all submissions as source selection information (see FAR 2.101 and 3.104), and to disclose their contents only for the purpose of evaluation. Restrictive notices notwithstanding, during the evaluation process, submissions may be handled by support contractors for administrative purposes and/or to assist with technical evaluation. All DARPA support contractors performing this role are expressly prohibited from performing DARPA-sponsored technical research and are bound by appropriate nondisclosure agreements.

Submissions will not be returned. The original of each submission received will be retained at DARPA and all other non-required copies destroyed. A certification of destruction may be requested, provided the formal request is received at this office within 5 days after unsuccessful notification.

1. Security Information Classified submissions shall be transmitted in accordance with the following guidance.

Additional information on the subjects discussed in this section may be found at http://www.dss.mil/.

If a submission contains Classified National Security Information as defined by Executive Order 13526, the information must be appropriately and conspicuously marked with the proposed classification level and declassification date. Similarly, when the classification of a submission is in question, the submission must be appropriately and conspicuously marked with the proposed classification level and declassification date. Submissions requiring DARPA to make a final classification determination shall be marked as follows:

“CLASSIFICATION DETERMINATION PENDING. Protect as though classified____________________________(insert the recommended classification level, e.g., Top Secret, Secret or Confidential)”

NOTE: Classified submissions must indicate the classification level of not only the submitted materials, but also the classification level of the anticipated award.

Proposers submitting classified information must have, or be able to obtain prior to contract award, cognizant security agency approved facilities, information systems, and appropriately cleared/eligible personnel to perform at the classification level proposed. All proposer personnel performing Information Assurance (IA)/Cybersecurity related duties on classified Information Systems shall meet the requirements set forth in DoD Manual 8570.01-M (Information Assurance Workforce Improvement Program).

http://www.dss.mil/

Proposers choosing to submit classified information from other collateral classified sources (i.e., sources other than DARPA) must ensure (1) they have permission from an authorized individual at the cognizant Government agency (e.g., Contracting Officer, Program Manager); (2) the proposal is marked in accordance with the source Security Classification Guide (SCG) from which the material is derived; and (3) the source SCG is submitted along with the proposal.

DARPA anticipates that submissions received under this BAA will be unclassified. However, should a proposer wish to submit classified information, an unclassified email must be sent to the BAA mailbox requesting submission instructions from the Technical Office PSO.

Security classification guidance and direction via a Security Classification Guide (SCG) and/or DD Form 254, “DoD Contract Security Classification Specification,” will not be provided at this time, since DARPA is soliciting ideas only. If a determination is made that the award instrument may result in access to classified information, a SCG and/or DD Form 254 will be issued by DARPA and attached as part of the award.

Confidential and Secret Information Use transmission, classification, handling, and marking guidance provided by previously issued SCGs, the DoD Information Security Manual (DoDM 5200.01, Volumes 1 - 4), and the National Industrial Security Program Operating Manual, including the Supplement Revision 1, (DoD 5220.22-M and DoD 5200.22-M Sup. 1) when submitting Confidential and/or Secret classified information.

Confidential and Secret classified information may be submitted via ONE of the two following methods:

• Hand-carried by an appropriately cleared and authorized courier to the DARPA CDR.

Prior to traveling, the courier shall contact the DARPA Classified Document Registry (CDR) at 703-526-4052 to coordinate arrival and delivery.

OR

• Mailed via U.S. Postal Service (USPS) Registered Mail or USPS Express Mail. All classified information will be enclosed in opaque inner and outer covers and double-wrapped. The inner envelope shall be sealed and plainly marked with the assigned classification and addresses of both sender and addressee.

The inner envelope shall be addressed to:

Defense Advanced Research Projects Agency ATTN: DARPA/MTO, Dr. Robert Lutwak Reference: DARPA-BAA-15-33

The outer envelope shall be sealed with no identification as to the classification of its contents and addressed to:

Defense Advanced Research Projects Agency Security & Intelligence Directorate, Attn: CDR

Top Secret Information Use classification, handling, and marking guidance provided by previously issued SCGs, the DoD Information Security Manual (DoDM 5200.01, Volumes 1 - 4), and the National Industrial Security Program Operating Manual, including the Supplement Revision 1, (DoD 5220.22-M and DoD 5200.22-M Sup. 1). Top Secret information must be hand-carried by an appropriately cleared and authorized courier to the DARPA CDR. Prior to traveling, the courier shall contact the DARPA CDR at 703-526-4052 to coordinate arrival and delivery.

Sensitive Compartmented Information (SCI) SCI must be marked, managed and transmitted in accordance with DoDM 5105.21 Volumes 1

- 3. Questions regarding the transmission of SCI may be sent to the DARPA Technical Office PSO via the BAA mailbox or by contacting the DARPA Special Security Officer (SSO) at 703- 812-1970.

Successful proposers may be sponsored by DARPA for access to SCI. Sponsorship must be aligned to an existing DD Form 254 where SCI has been authorized. Questions regarding SCI sponsorship should be directed to the DARPA Personnel Security Office at 703-526-4543.

Special Access Program (SAP) Information SAP information must be marked in accordance with DoDM 5205.07 Volume 4 and transmitted by specifically approved methods which will be provided by the Technical Office PSO or their staff.

Proposers choosing to submit SAP information from an agency other than DARPA are required to provide the DARPA Technical Office Program Security Officer (PSO) written permission from the source material’s cognizant Special Access Program Control Officer (SAPCO) or designated representative. For clarification regarding this process, contact the DARPA Technical Office PSO via the BAA mailbox or the DARPA SAPCO at 703-526-4102.

Additional SAP security requirements regarding facility accreditations, information security, personnel security, physical security, operations security, test security, classified transportation plans, and program protection planning may be specified in the DD Form 254.

NOTE: prior to drafting the submission, if use of SAP Information Systems is to be proposed, proposers must first obtain an Authorization-to-Operate from the DARPA Technical Office PSO (or other applicable DARPA Authorization Official) using the Risk Management Framework

(RMF) process outlined in the Joint Special Access Program (SAP) Implementation Guide (JSIG), Revision 3, dated October 9, 2013 (or successor document).

2. Proprietary Information Proposers are responsible for clearly identifying proprietary information. Submissions containing proprietary information must have the cover page and each page containing such information clearly marked with a label such as “Proprietary” or “Company Proprietary.” Note, “Confidential” is a classification marking used to control the dissemination of U.S. Government National Security Information as dictated in Executive Order 13526 and should not be used to identify proprietary business information.

3. Proposal Submission Information The typical proposal should express a consolidated effort in support of one or more related technical concepts or ideas. Disjointed efforts should not be included into a single proposal.

Proposals may not be submitted by fax or e-mail; any so sent will be disregarded.

For All:

All administrative correspondence and questions on this solicitation, including requests for information on how to submit a full proposal to this BAA, should be directed to DARPA-BAA-15-33@darpa.mil. DARPA intends to use electronic mail for correspondence regarding DARPA-BAA-15-33. DARPA encourages use of the Internet for retrieving the BAA and any other related information that may subsequently be provided.

As noted on page 4 above, this BAA seeks only proposals for procurement contracts or other transaction agreements. Proposals seeking any other award instrument type (i.e., assistance instruments) will be considered non-compliant.

Proposers must submit proposals via DARPA's BAA Website (https://baa.darpa.mil). Visit the website to complete the two-step registration process. Submitters will need to register for an Extranet account (via the form at the URL listed above) and wait for two separate e-mails containing a username and temporary password. After accessing the Extranet, submitters may then create an account for the DARPA BAA website (via the "Register your Organization" link along the left side of the homepage), view submission instructions, and upload/finalize the proposal. Proposers using the DARPA BAA Website may encounter heavy traffic on the submission deadline date; it is highly advised that submission process be started as early as possible. Classified submissions and proposals requesting assistance instruments (cooperative agreements) should NOT be submitted through DARPA's BAA Website (https://baa.darpa.mil), though proposers will likely still need to visit https://baa.darpa.mil to register their organization (or verify an existing registration) to ensure the BAA office can verify and finalize their submission.

Technical support for DARPA's BAA Website may be reached at action@darpa.mil, and is typically available during regular business hours, (9:00 AM- 5:00 PM EST Monday - Friday).

NOTE: YOU MUST CLICK THE ‘FINALIZE FULL PROPOSAL’ BUTTON AT THE

BOTTOM OF THE CREATE FULL PROPOSAL PAGE. FAILURE TO DO SO WILL

RESULT IN YOUR PROPOSAL NOT BEING OFFICIALLY SUBMITTED TO THIS BAA

AND THEREFORE NOT BEING REVIEWED.

4. Full Proposal Format All full proposals must be in the format given below and must include all three phases to be considered compliant. Proposals shall consist of two volumes: Volume I – Technical and Management Proposal, and Volume II – Cost Proposal. All pages shall be printed on 8-1/2 by 11 inch paper with type not smaller than 12 point. Smaller font may be used for figures, tables and charts. The page limitation for full proposals includes all figures, tables, and charts. Volume I, Technical and Management Proposal, may include an attached bibliography of relevant technical papers or research notes (published and unpublished) which document the technical ideas and approach upon which the proposal is based. Copies of not more than three (3) relevant papers may be included with the submission. The bibliography and attached papers are not included in the page counts given below. The submission of other supporting materials along with the proposals is strongly discouraged and will not be considered for review. Section II of Volume I, Technical and Management Proposal shall not exceed 30 pages. All full proposals must be written in English.

a. Volume I, Technical and Management Proposal Section I. Administrative

A. Cover sheet to include:

(1) BAA number (DARPA-BAA-15-33);

(2) Lead Organization submitting proposal;

(3) Type of organization, selected among the following categories: “LARGE

ORGANIZATION”, “SMALL DISADVANTAGED ORGANIZATION”, “OTHER

SMALL ORGANIZATION”, “HBCU”, “MI”, “OTHER EDUCATIONAL”, OR

“OTHER NONPROFIT”;

(4) Proposer’s reference number (if any);

(5) Other team members (if applicable) and type of organization for each;

(6) Proposal title;

(7) Technical point of contact to include: salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), electronic mail;

(8) Administrative point of contact to include: salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), electronic mail;

(9) Total funds requested from DARPA, and the amount of cost share (if any); AND

(10) Date proposal was submitted.

B. Official transmittal letter.

Section II. Detailed Proposal Information

A. Innovative Claims – Describe the unique qualities of the proposed technology approach, teaming expertise, and experience that will lead to success of the proposed program.

B. Technology Basis – Describe the underlying MEMS inertial sensor technology to be implemented in the proposed NGIMU. Include performance and reliability data that establishes the current performance capabilities of the proposed technology. Identify specifications in Table 1 that are not currently met by existing technology and propose evolutionary advances to the technology to meet the program objectives. Include a description of any non-conventional processing requirements for the proposed technology basis, yield-limiting process steps, and process development required to provide a high yield of devices which meet or exceed the performance objectives of Table 1.

C. Detailed Technical Approach – This is the technical soul of the proposal. Present, in detail, the technical development path that will achieve the metrics and milestones of Part II, Section I.B (page 6). Include detailed analysis of the proposed technology to meet or exceed each of the metrics in Table 1. Also describe and analyze additional sensor error sources not listed in Table 1 (for example, at the IMU level: scale factor asymmetry, sensor misalignment, vibration rectification, etc.).

D. Test plan – Describe testing to be performed in each phase to verify compliance with performance objectives of Table 1. Where relevant, indicate availability or gaps in the proposer’s existing test infrastructure.

E. Risk analysis – Identify the major technical and programmatic risks in the program. Include a risk matrix. For each risk assign a probability of occurrence on a scale of 1-10, where 10 indicates a high likelihood that the risk will impact program success, as well as an assessment of impact, also on a scale of 1-10, where 10 indicates that the this risk would maximally limit the program from delivering prototypes on schedule or meeting performance objectives of Table 1. For any item with total risk (likelihood × impact) exceeding 40, include a plan for mitigating the risk and assessing risk reduction.

F. Schedule, milestones, and budget – Include a high-level schedule of major technical tasks, and measureable milestones by phase.

G. Technology Transfer – This program is expected to include development and demonstration of 10 NGIMU devices. In this section, the proposer should present a plan for transition to manufacturing and opportunities for early insertion demonstrations. If applicable, highlight institutional commitment to cost-sharing of concurrent or subsequent transition activities.

This should also address mitigation of life-cycle and sustainment risks associated with transitioning intellectual property for U.S. military applications, if applicable. See also Section VIII. “Intellectual Property.”

H. Comparison with other ongoing research, either internal or external to the proposing organization, indicating advantages and disadvantages of the proposed effort.

I. Biographies of key personnel J. Description of the facilities and equipment that would be used for the proposed effort. Where necessary, indicate gaps in available resources and present a mitigation strategy and schedule for obtaining access to the required resources.

K. Statement of Work (SOW) - In plain English, clearly define the technical tasks/subtasks to be performed, their durations, and dependencies among them. The SOW must not include proprietary information. For each task/subtask, provide:

1. A general description of the objective;

2. A detailed description of the approach to be taken to accomplish each defined task/activity;

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

4. Completion criteria for each task/activity - a product, event or milestone that defines its completion.

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

6. If applicable (keeping in mind – as noted on page 4 above – the PRIGM:NGIMU program will be funded with 6.3 funding), clearly identify any tasks/subtasks (prime or subcontracted) that will be accomplished on campus at a university.

Note: It is recommended that the SOW be developed so that each phase of the program is separately defined.

L. Summary Slide – One PowerPoint slide summarizing the proposed effort. A template slide is provided on the BAA website (Attachment 2). Submit this PowerPoint file in addition to Volumes I and II of your full proposal. This summary slide does not count towards the total page count.

Section III. Additional Information

b. Volume II, Cost Proposal – {No Page Limit} Cover sheet to include:

(1) BAA number (DARPA-BAA-15-33);

(2) Lead Organization submitting proposal;

(3) Type of organization, selected among the following categories: “LARGE

ORGANIZATION”, “SMALL DISADVANTAGED ORGANIZATION”, “OTHER

SMALL ORGANIZATION”, “HBCU”, “MI”, “OTHER EDUCATIONAL”, OR

“OTHER NONPROFIT”;

(4) Proposer’s reference number (if any);

(5) Other team members (if applicable) and type of organization for each;

(6) Proposal title;

(7) Technical point of contact to include: salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), electronic mail (if available);

(8) Administrative point of contact to include: salutation, last name, first name, street address, city, state, zip code, telephone, fax (if available), and electronic mail (if available);

(9) Award instrument requested: cost-plus-fixed fee (CPFF), cost-contract—no fee, cost sharing contract – no fee, or other type of procurement contract (specify), cooperative agreement, or other transaction;

(10) Place(s) and period(s) of performance;

(11) Total proposed cost separated by basic award and option(s) (if any) broken down by calendar year and by government fiscal year;

(12) Name, address, and telephone number of the proposer’s cognizant Defense Contract Management Agency (DCMA) administration office (if known);

(13) Name, address, and telephone number of the proposer’s cognizant Defense Contract Audit Agency (DCAA) audit office (if known);

(14) Date proposal was prepared;

(15) DUNS number;

(16) TIN number;

(17) CAGE Code;

(18) Subcontractor Information;

(19) Proposal validity period; and

(20) Any Forward Pricing Rate Agreement, other such approved rate information, or such documentation that may assist in expediting negotiations (if available).

Attachment 1, the Cost Volume Proposer Checklist, must be included with the coversheet of the Cost Proposal

For proposers without an approved cost accounting system who are proposing negotiation of a cost-type contract, DCAA must complete an SF 1408 prior to award. To facilitate this process, complete the SF 1408 found at http://www.gsa.gov/portal/forms/download/115778 and submit the completed form with your proposal. Proposals requesting a cost-type contract without this form may be deemed non-conforming to this solicitation. The Government recognizes that this form is intended for an auditor to use when evaluating a contractor's cost accounting system.

However, your preliminary responses to the questions will expedite the DCAA accounting system review. To complete the form, check the boxes on the second page, then provide a narrative explanation of your accounting system to supplement the checklist on page one.

The proposers’, to include eligible FFRDCs’, cost volume shall provide cost and pricing information (See Note 1), or other than cost or pricing information if the total price is under $700,000, in sufficient detail to substantiate the program price proposed (e.g., realism and reasonableness). In doing so, the proposer shall provide a summary cost breakdown, and a detailed cost breakdown by phase (if multiple phases are proposed), technical task/sub-task, and month for each technical area proposed to. The breakdown/s shall include, at a minimum, the following major cost item along with associated backup documentation:

Total program cost broken down by major cost items:

a. Direct Labor – a breakout clearly identifying the individual labor categories with associated labor hours and direct labor rates, as well as a detailed Basis-of- Estimate (BOE) narrative description of the methods used to estimate labor costs;

b. Indirect Costs – Including Fringe Benefits, Overhead, General and Administrative Expense, Cost of Money, Fee, etc. (must show base amount and rate);

c. Travel – Provide the purpose of the trip, number of trips, number of days per trip, departure and arrival destinations, number of people, etc.;

d. Other Direct Costs – Itemized with costs; Back-up documentation is to be submitted to support proposed costs;

e. Material/Equipment –

(i) A priced Bill-of-Material (BOM) clearly identifying, for each item proposed, the quantity, unit price, the source of the unit price (i.e., vendor quote, engineering estimate, etc.), the type of property (i.e., material, equipment, special http://www.gsa.gov/portal/forms/download/115778 test equipment, information technology, etc.), and a cross-reference to the Statement of Work (SOW) task/s that require the item/s. At time of proposal submission, any item that exceeds $1,000 must be supported with basis-of-estimate (BOE) documentation such as a copy of catalog price lists, vendor quotes or a written engineering estimate (additional documentation may be required during negotiations, if selected).

(ii) If seeking a procurement contract and items of Contractor Acquired Property are proposed, exclusive of material, the proposer shall clearly demonstrate that the inclusion of such items as Government Property is in keeping with the requirements of FAR Part 45.102. In accordance with FAR 35.014, “Government property and title,” it is the Government’s intent that title to all equipment purchased with funds available for research under any resulting contract will vest in the acquiring nonprofit institution (e.g., Nonprofit Institutions of Higher Education and Nonprofit Organizations whose primary purpose is the conduct of scientific research) upon acquisition without further obligation to the Government. Any such equipment shall be used for the conduct of basic and applied scientific research. The above transfer of title to all equipment purchased with funds available for research under any resulting contract is not allowable when the acquiring entity is a for-profit organization; however, such organizations can, in accordance with FAR 52.245-1(j), be given priority to acquire such property at its full acquisition cost.

f. Consultants – If consultants are to be used, proposer must provide a copy of the consultant’s proposed SOW as well as a signed consultant agreement or other document which verifies the proposed loaded daily / hourly rate and any other proposed consultant costs (e.g. travel);

g. Subcontracts – Itemization of all subcontracts. Additionally, the prime contractor is responsible for compiling and providing, as part of its…