HQ085221S0001_C2BMC_BAA_20201214.pdf

Advanced Research Opportunity (ARO)

Broad Agency Announcement (BAA)

Missile Defense Agency (MDA)

MDA BAA Announcement HQ0852-21-S-0001

COMMAND AND CONTROL, BATTLE MANAGEMENT,

AND COMMUNICATIONS (C2BMC)

December 14, 2020

Missile Defense Agency

5222 Martin Road

Redstone Arsenal, AL 35898

This Advanced Research Opportunity (ARO) Broad Agency Announcement (BAA) is intended to fulfill requirements for scientific study and experimentation directed toward advancing state-of-the-art technologies and/or increasing knowledge and understanding as a means to identify and develop robust innovative concepts, stimulate technology innovation, and exploit breakthroughs in science.

This ARO BAA identifies MDA C2BMC research/exploratory development areas of interest and provides prospective offerors information on the preparation of white papers along with evaluation factors.

THIS BAA DOES NOT FOCUS ON SPECIFIC SYSTEMS OR HARDWARE SOLUTIONS.

THIS ANNOUNCEMENT IS NOT FOR THE ACQUISITION OF TECHNICAL, ENGINEERING, OR

OTHER TYPES OF SUPPORT SERVICES.

THIS PAGE INTENTIONALLY BLANK

Table of Contents

SECTION I: INTRODUCTION

SECTION II: SUMMARY INFORMATION

A. Agency Name

B. Program Name

C. Broad Agency Announcement Title

D. Broad Agency Announcement Number

E. North American Industry Classification System (NAICS) Code/Title

F. Response Date

G. Anticipated Awards

H. Total Funding Availability for Award(s)

I. Timeline

J. Types of Instruments that May Be Awarded

K. Points of Contact (POCs)

L. Other Information

SECTION III: RESEARCH OPPORTUNITY DESCRIPTION

B. Synopsis

C. Description

D. White Paper Submission

E. Marking

F. Data Rights

G. Industry Day Announcement

H. Government Furnished Information (GFI)

I. Organizational Conflict of Interest (OCI)

I. C2BMC BAA OCI POC

K. Cybersecurity

SECTION IV: AWARD INFORMATION

SECTION V: ELIGIBILITY INFORMATION

SECTION VI: APPLICATION AND SUBMISSION INFORMATION

A. Submission Process

B. Requirements of White Papers

C. Rough Order of Magnitude (ROM)

SECTION VII: EVALUATION INFORMATION

A. Evaluation Process

B. Evaluation Criteria

C. Evaluation Team

SECTION VIII: AWARDS

ANNEX 1: TECHNOLOGY READINESS LEVELS

ANNEX 2: ORGANIZATIONAL CONFLICT OF INTEREST (Jun 2012)

ANNEX 3: OCI ANALYSIS/DISCLOSURE FORM

OCI Disclosure Form

ADVANCED COMPONENT DEVELOPMENT AND PROTOTYPES

SECTION I: INTRODUCTION

This publication constitutes a Broad Agency Announcement (BAA) issued under the provisions of

Federal Acquisition Regulation (FAR) 6.102(d)(2), providing for the competitive selection of advanced component development and prototypes and that part of development not related to the development of a specific system or hardware procurement. This posting fulfills the requirement for full and open competition.

The Missile Defense Agency (MDA) Command and Control, Battle Management, and

Communication (C2BMC) system is integrated into many of the other Ballistic Missile Defense

Systems (BMDS) program elements.

The C2BMC Program employs a spiral development strategy to deliver enhanced and new C2BMC capabilities to the Warfighter. The C2BMC Program provides:

(1) The communications links and connectivity between Ballistic Missile Defense Elements and command centers;

(2) A battle management function that supports engagement planning and coordination to optimize BMDS effectiveness and efficiency;

(3) Control and data management of the BMDS radars, to include Mobile Sensor Integration, accepting threat track data from multiple sensors and correlating them into a single system track;

(4) Cybersecurity enhancements;

(5) Real-time awareness of the BMD battle as it unfolds; and,

(6) An advanced planning capability which enables Warfighters to place BMDS assets in ideal locations to counter various threat scenarios.

Each spiral program includes the necessary software capabilities, hardware, network connectivity, deployment, training, and Contractor Logistics Support (CLS) for an operational capability.

PURPOSE

The MDA C2BMC contracting office (BCK) invites innovative technical approach concept “white” papers that address operationally focused C2BMC capabilities and/or agile mechanisms to monitor, acquire, track, and engage adversary weapons during any phase of an attack. MDA seeks to identify, adapt and acquire emerging technologies that enhance the performance of C2BMC capabilities, which include addressing the development of Command and Control (C2) of Long

Range Discrimination Radar (LRDR) for Homeland Defense (S8.2-5), Engage on Remote technology (Spiral S8.2-3), early development of Ballistic Missile Defense (BMD) System Track

(BST) with System Level Integrated Discrimination (S8.2-7), radar and radio frequency (RF) communications, computer science, signal, and data processing, and artificial intelligence / machine learning.

MDA C2BMC will not issue paper copies of this announcement. C2BMC reserves the right to select for award all, some, or none of the white papers in response to this announcement. The cost of responding to this BAA is not an allocable and allowable cost as set forth in accordance with

FAR Part 31. Such costs shall be excluded from any billing, claim, or proposal applicable to a

Government award. It is the policy of C2BMC to handle all white papers and proposals submitted under this BAA as sensitive, competitive information, and to disclose their contents only for the purposes of evaluation and potential award.

The issuance of this BAA does not commit the Government to any contract, agreement, or other arrangements. Furthermore, this BAA shall not be construed as a commitment by the Government for any procurement of supplies or services nor does it constitute a solicitation or a promise of a solicitation in the future.

SECTION II: SUMMARY INFORMATION

A. Agency Name

Missile Defense Agency

B. Program Name

Command and Control, Battle Management, and Communications (C2BMC)

C. Broad Agency Announcement Title

Command and Control, Battle Management, and Communications

D. Broad Agency Announcement Number

HQ0852-21-S-0001

E. North American Industry Classification System (NAICS) Code/Title

541715 - Research and Development in the Physical, Engineering, and Life Sciences

F. Response Date

This announcement remains open for 36 months after announcement, or until superseded by future versions. White papers are evaluated as they are received and may be submitted at any time.

Calls for white papers which are placed under this BAA will provide the specific information related to due dates. Late bid and proposal provisions will apply to any white papers submitted for this BAA (in accordance with FAR 52.215-1(c)(3)), when applicable.

G. Anticipated Awards

Multiple awards are anticipated under this BAA. However, the Government is under no obligation to make any awards. The number of awards made under this BAA will depend on the quality of the white papers received and the availability of funds. The issuance of this BAA does not commit the Government to any contractual agreement or arrangements.

H. Total Funding Availability for Award(s)

The Government does not have a specified amount of funding available for BAA awards.

However, funding may be provided throughout the open period of this BAA to pursue promising and innovative concepts of interest with any and all qualified sources.

Funding of research within C2BMC areas of interest has been determined by funding constraints and priorities set during the fiscal year 2021-2022 (FY21-22) budget cycles.

I. Timeline

Anticipated timeline for this BAA is 36 months from the posting date.

J. Types of Instruments that May Be Awarded

The Government may award from this BAA in the form of a Cooperative Agreement (CA), Technology Investment Agreement (TIA), Other Transaction (OT), or FAR-based contract. Any award(s) resulting from this BAA will incorporate all applicable FAR, Defense Federal

Acquisition Regulation Supplement (DFARS), and local MDA clauses.

K. Points of Contact (POCs)

1. Technical Questions:

Leonard Halley

UNCLASSIFIED E-mail: leonard.halley@mda.mil

2. Award Questions and All Unclassified Award Communications:

Samuel Cornelius

UNCLASSIFIED E-mail: samuel.cornelius@mda.mil

3. BAA Program Administration Group

UNCLASSIFIED E-mail: C2BMC-BAA@mda.mil

4. Security Questions:

Mr. Jeffrey Cassell

UNCLASSIFIED E-mail: jeffrey.cassell@mda.mil

L. Other Information

Any research conducted on or resulting from any type of award made from this BAA must comply with United States Laws and regulations on “Export Control,” including the

International Traffic in Arms Regulations (ITAR) and the Export Administration Regulations

(EAR). MDA approval is required prior to any non-U.S. citizen performing classified or unclassified work on a BAA award.

SECTION III: RESEARCH OPPORTUNITY DESCRIPTION

B. Synopsis

Submissions utilizing technology with a Technology Readiness Level (TRL) of 3 or higher are desired; justify TRL using DoD Technology Readiness Assessment (TRA) Guidance, April

2011. When applicable, prototyping and fielding on a condensed timeline is desired. Topics of interest for this BAA are listed below.

1. Provide operationally focused C2BMC capabilities meeting Combatant Command Mission requirements while optimizing system performance and effectiveness. Capabilities may address one or more of the following:

a. Command, Control, Communications, Intelligence and Networks (C3I&N) and BM state-of-the-art advancement

C3I&N and BM state-of-the-art advancement technologies are focused on innovative, non-traditional hardware / software / techniques whose emergence will cause a paradigm shift in command, control, and battle management. Revolutionary capabilities may include implementation of a quantum computer based architecture, computer vision, and application of quantum computing & information processing.

b. Enhancing battlefield, engagement, and overall situational awareness

Enhancing battlefield, engagement, and overall situational awareness includes, but is not limited to, sensors and techniques that sample the entire spectrum of events, clues, and indicators available in a given theatre and provide the Warfighter Battle

Manager with near real time assessments of the systems capability and possible degradation. Sampling technologies may include RF sensors, Electro-

Optical/Infrared (EO/IR) sensors, communication systems, and cyber techniques. In addition to data collection, interesting technologies will improve communication & coordination between geographically dispersed systems and operators; maintain real time accounting of weapon system inventories; while minimizing data processing overhead. Also included are technologies that monitor the battlefield environment, develop engagement plans that are optimized to key conditions, and actively manage sensing and weapon resources to ensure engagement success.

c. Communications and networking

Communications and networking are core C2BMC capabilities that enable system level health and status monitoring, alert state commanding, sensor and weapon system tasking, engagement coordination, and post intercept assessment. Candidate technologies include, but are not limited to, advanced, integrated system concepts, signal processing, data visualization, data compression, and operations in stressing environments. In addition, technology that enhances target detection, acquisition, and tracking, will be considered.

d. Improvements to existing BMDS infrastructure

Improvements to existing BMDS infrastructure includes the innovative upgrades to hardware and software components necessary to maintain BMDS performance and effectiveness. Improvements are expected in, but not limited to, enhanced modularity, security, scalability, extensibility, and resiliency within the construct of an open systems architecture. Also included are innovative approaches and technologies that enable collaborative development of system capabilities by multiple contractors and more efficient installation and fielding of resultant system upgrades to all operational sites, to include those in host and partner nations. Solutions are envisioned to include cloud computing and storage capabilities.

e. Operations advancement in Electronic and Cyber Protection

Operations advancement in Electronic and Cyber Protection capabilities will require innovative methods of ensuring the security of C2BMC systems in the face of an electronic attack or cyber event as well as the resiliency to maintain operations while rapidly negating cyber threats, to include anti-access/anti denial environments.

Technologies include, but are not limited to, improved response time and effectiveness of cyber protection mechanisms, while ensuring minimal interruption to operations. C2BMC will consider technologies that improve cyber situational awareness, anomaly/intrusion detection, and enhance operational responsiveness of deployed systems against emerging cyber threats.

f. Indications and Warnings derived from analysis of Geospatial and Geopolitical conditions

Indications and Warnings including Left of Launch, Geospatial and Geopolitical, as well as other predictive analysis techniques and technologies that are required to maintain global situational awareness, support persistent surveillance, and enable preplanning of response scenarios. Technologies are expected to include, but are not limited to, capability for interactive collaboration and integrated operations with

Intelligence, Services, and R&D communities.

g. Exploitation of enemy threat systems

Exploitation of enemy threat systems includes the capability to rapidly identify vulnerabilities in threat systems and to develop mechanisms to exploit and negate these threats. Candidate technologies are expected to include artificial intelligence / machine learning (AI/ML) techniques to manipulate high fidelity models & simulations of hardware, software, signals and systems, to rapidly identify vulnerabilities and exploitation mechanisms. Candidate solutions that utilize AI/ML enabled modeling and simulation technologies which support/improve system level detection, tracking, and discrimination; engagement optimization; sensor and weapons resource management, will also be considered.

h. Artificial Intelligence / Machine learning (AI/ML)

The future Integrated Battle Management capability will require rapid assessment of large amounts of data from globally dispersed sensors and weapon systems. AI/ML techniques are able to examine data at a speed and granularity human operators cannot. Results from AI/ML assessed data will provide the Warfighter Battle

Manager, and other users of C2BMC data, with sufficient rationale to support accurate decisions on recommended courses of action. The MDA/BC Program

Office will consider AI/ML developed technologies which support/improve: system level detection, tracking, and discrimination; engagement optimization; sensor and weapons resource management.

i. Decision engineering and autonomy

Decision engineering and autonomy technologies include optimization, reasoning, and decision engineering methodologies to enable the Warfighter Battle Manager to delegate lower order tasks to decision engines while developing better informed, optimal decisions utilizing decision support tools. Technologies will include capabilities to provide enhanced and timely courses of action, improve: sensor and weapon tasking; engagement optimization; and sensor and weapon resource management.

j. Non-Traditional sensor data exploitation and integration

Non-Traditional sensor data exploitation and integration including, but not limited to, novel utilization of existing sensing systems, application of emerging innovative technologies, and infrastructure enhancements that are modular, adaptable, and extensible, to allow rapid insertion of new and diverse capabilities into the C2BMC architecture. Examples may include shared use of commercial systems, passive radio interferometry, and hybrid Radio & Optical sensors. Particularly interesting are sensing systems to enhance surveillance, acquisition, tracking, discrimination and target selection.

k. Computer Science, Signal, and Data Processing

The future Integrated Battle Management capability will be required to ingest very large quantities of data from globally dispersed sensors and weapon systems, mine the data for actionable information, and provide the Warfighter Battle Manager with sufficient rationale to support an accurate course of action decision, all in near real-time. The MDA/BC Program Office is seeking hardware & software technologies that enable the BMDS to improve performance, speed, accuracy, and efficiency by leveraging advances in computational, signal and data processing. The MDA/BC

Program Office will consider proposed hardware and software technologies from the sub-system level through the system level. Technologies include: hardware & computer peripherals; advanced algorithms including sensor fusion & data encryption; hardware to remediate obsolescence.

l. Radar and RF Communications

The future Integrated Battle Management capability is envisioned as a robust System of Systems that provides the Warfighter Battle Manager with near real-time communications and decision support data. The MDA/BC Program Office will develop High Reliability / Low Latency Communications to enable this capability.

The MDA/BC Program Office will consider proposed technologies at the sub-system

/ component level through the integrated system level. Technologies include, but are not limited to, very large scale communication and management concepts (System of

System, System of Services, etc.); communication concepts that enable near real-time data sharing of very large data sets in challenging electro-magnetic environments using multiple, alternative, low latency communication paths and exploiting various

Radar & RF phenomenologies.

C. Description

Provide a white paper describing the Offeror’s proposed technological innovations to meet the detection, engagement planning, and engagement execution challenges. Describe the Offeror’s estimated schedule and rough order of magnitude (ROM) cost to implement and execute technology maturation tasks described.

Describe the Offeror’s ability to execute the steps required to mature the proposed technology to a fieldable state and produce results including demonstrated capability to design, fabricate, and test prototype technology components and subsystems. Describe the modeling and simulation capability necessary to analyze a technology concept and mature it to the prototyping phase.

Describe the manufacturing capability necessary to realize a prototype design and create hardware test articles as applicable. Describe the testing necessary to achieve intended TRL and the recommended availability of those facilities for testing.

For each technology proposed, describe how the Offeror will accomplish:

1. Technology Definition, Prototype Design, and Demonstration

a. Identify specific challenges of current and advanced threats and proposed component technology

b. Define the analysis and design approach for technology prototypes, as appropriate, that links prototype characteristics to current and advanced threats needs

c. Describe the relevant environments necessary to demonstrate technology readiness

d. Describe the application of open systems and modularity to maximize technology applicability across potential users

e. Identify specific development activities and tests necessary to increase technology maturity to TRL 5

f. Describe within which current and advanced threats architecture element the component technology applies (e.g., sensor, communication, weapon, command and control) and where it fits in the kill chain, or describe the new architecture element

g. Describe if the component technology makes the current industry standard obsolete

h. Identify performance benefits to current and advanced threats architecture

2. Modeling, Simulation, and Test

a. Describe models and simulation capability appropriate to the component technology, including the heritage of re-used models and new models required

b. Describe component testing, limitations, and plans for mitigation and/or improvement. Examples of testing may include, but are not limited to:

1) Component testing, such as material coupons, scene generation

2) Subscale testing, such as wind tunnel testing

3) Flight testing

3. Technology Maturity and Risk Assessment

a. Describe your risk management process to include identifying, assessing, and developing mitigation strategies for program risks

b. Present risk assessments

c. Define the key technology risks

d. Assess the technical maturity of proposed component technology in accordance with

TRL definitions in Annex 1. Provide the data justifying the assessed TRL

e. Outline key aspects of transitioning technology into current and advanced threats architecture

4. Program Planning

a. Develop a technology component schedule for all tasks associated with the technology maturation, development, test, and transition

b. Describe in detail the approach, technical objectives, and how the schedule will be executed. Milestones should indicate when specific technology objectives are expected to be met and should identify the specific accomplishments necessary to proceed to the next task

D. White Paper Submission

The appropriate security classification guide (SCG) must be followed by those interested parties submitting white papers. Contact the MDA Security POC listed in this document for specific classification instructions for any situation where no clear SCG direction is available or known, and the Offeror believes the work would merit classification due to either technical and/or quantitative performance or capabilities. Offerors must possess all required personnel security clearances, facility clearances, and other infrastructure requirements necessary to conduct or perform such classified work.

Offerors shall fully describe technology applicability to C2BMC, current technology maturity level, maturation activities and milestones, achievable TRL, and how this technology advances the current state-of-the-art. Offerors will provide schedule and cost estimates for technology maturation and demonstration. Each Offeror may submit more than one component technology

(unique article under development), however each component technology must be a separate white paper submission. Organizations may submit multiple concept papers addressing the same area of research interest.

In order to maximize cost efficiencies for the next generation of C2BMC solutions, submissions shall include a “data management approach” including a description as to how the Offeror plans to satisfy the Government’s desire to obtain the necessary license rights and delivery of technical data and computer software (to include computer software documentation) to allow third party sustainment/maintenance. The Government is particularly sensitive to assertions that may be made for technical data and/or software relating to critical system modules and components; as well as to any assertions for information associated with key components and hardware and/or software interfaces, which may affect the planned strategy.

Offerors shall identify any additional Government Furnished Information (GFI) needed for contract performance in their white papers, to include title, description, rationale, date required, and impact if not received.

All models, algorithms, simulations, and/or software modified or developed will be delivered with no less than Government purpose rights as defined in the DFARS 227.7103-5, if applicable.

Exceptions are expected for commercial-off-the-shelf software (e.g., MATLAB).

E. Marking

White paper submissions must comply with the instructions set forth in this document. Offerors are responsible for adequately marking information contained in their submission. Offerors shall mark any technical data, computer software, and computer software documentation that is associated with existing Government data rights accordingly. Offerors shall provide the appropriate markings in accordance with the DFARS as such on a page-by-page basis, if applicable.

F. Data Rights

Offerors 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. Include all proprietary claims to results, prototypes, and/or deliverables. If no restrictions are intended, then the offeror should state “NONE.”

Data rights will be specifically negotiated to satisfy the Government’s needs for all FAR-based contracts, Other Transactions, and Agreements. The appropriate data rights clauses will be incorporated based on the type of award.

G. Industry Day Announcement

C2BMC does not anticipate any industry day(s) in support of this BAA.

H. Government Furnished Information (GFI)

GFI may be provided, upon request, to aid in the preparation of white papers. Any technical data furnished by the Government in response to topic inquiries, is in an "as is" condition without warranty as to its accuracy, completeness, or adequacy.

The offerors shall use this GFI at their own risk. The Government assumes no responsibility for such furnished data/documentation, nor will the Government have any liability for a respondent's submission should such data/documentation prove to be inaccurate, incomplete, or otherwise defective.

The following documents are available for white paper preparation upon request:

1. BMDS Security Classification Guide (SCG)

2. MDA Core Standards

3. MDA Mission Assurance Provisions

4. MDA Parts, Materials, and Processes

5. Risk Management Instructions

I. Organizational Conflict of Interest (OCI)

OCIs can deprive the Government of the independent, objective advice of its supporting contractors. OCIs occur when a contractor may be unable to provide impartial advice or assistance, when its objectivity in performing a contract is impaired, or when it may obtain an unfair competitive advantage. A contractor can obtain an unfair competitive advantage by obtaining access to non-public information or when it is in a position to favor its own products or services. See Annex 2 for more information.

MDA maintains a strict OCI policy adhering to the FAR Part 3, FAR Subpart 9.5, and DFARS

Part 209. As a matter of general policy, contractors which provide advisory and assistance services to MDA, particularly in systems engineering and technical assistance (SETA), acquisition support, management support, and quality assurance functional areas, cannot develop or support the development of MDA's research and development efforts. This separation of contractual responsibilities is critical to ensuring MDA obtains the independent, objective advice it requires, particularly in establishing requirements for our major research and development efforts and in evaluating contractor performance of those requirements.

All offerors and proposed subcontractors shall disclose in their white paper submittal, whether they are providing any of the above mentioned advisory and assistance services or similar support to any MDA-funded contracts or subcontracts; BMDS-related contracts or subcontracts;

and any non-BMDS related business relationships with firms doing business with or in support of MDA. All facts relevant to the existence or potential existence of an OCI shall be disclosed.

All disclosures shall state which office(s) the Offeror supports, identify the prime contract numbers, provide a description of the services being performed, and a preliminary non-binding

OCI assessment addressing if an actual or potential OCI exists. White papers that fail to fully disclose existing or potential OCIs will be rejected without evaluation and withdrawn from further consideration for an award.

If a prospective offeror believes that an OCI exists or may exist, the Offeror should promptly notify MDA by e-mailing their contact information and a summary of the potential conflict to the C2BMC contracting office for a formal assessment, prior to preparing a white paper submittal.

1. MDA Technical, Engineering, Advisory, and Management Support (TEAMS)

Potential OCIs between TEAMS and other MDA acquisitions are highlighted in the MDA

TEAMS OCI Memorandum incorporated into each TEAMS draft and final solicitation.

Questions related to OCI issues or restrictions specific to a TEAMS solicitation/contract should be forwarded to the applicable TEAMS Contracting Officer by the prime contractor.

Subcontractors supporting TEAMS are required to contact their applicable TEAMS prime contractor for any OCI issues or restrictions specific to a TEAMS subcontract.

DFARS clause 252.209-7009, Organizational Conflict of Interest—Major Defense Acquisition

Program, is included in all TEAMS SETA solicitations/contracts. For the purposes of applying the prohibitions identified in DFARS 252.209-7009, efforts for the C2BMC BAA should be considered part of research, development, test, and evaluation (RDT&E).

The MDA TEAMS contracts require attention by the C2BMC BAA Contracting Officer with respect to potential or actual OCIs. Each potential OCI must be examined individually on the basis of its particular facts.

2. Preliminary, Non-Binding OCI Assessments

Individual contractors and contractor teams are invited to submit a request for preliminary, non-binding OCI assessments from date of this notice through submission of a white paper under the C2BMC BAA. Please complete Annex 3 of this notice (C2BMC BAA OCI

Analysis/Disclosure Form) and submit to the applicable POC per the submittal instructions provided in this announcement. The C2BMC BAA OCI Analysis/Disclosure Form, once filled in by the contractor, will be treated as Controlled Unclassified Information (CUI). Include a proposed Mitigation Plan, if applicable.

Note: It is the responsibility of the contractors and contractor teams to ensure OCI analysis and disclosure forms are current, accurate, and updated to reflect any changes or new contract awards that may result in an actual or potential OCI for the C2BMC BAA competitions.

I. C2BMC BAA OCI POC

Submit all OCI questions/comments concerning this notice and any requests for a preliminary, non-binding OCI assessment to the Contract Specialist, Samuel Cornelius at samuel.cornelius@mda.mil. As part of the OCI assessment request, complete and submit Annex

3, and include a Mitigation Plan, if applicable. Please note the BAA and applicable topic area in the subject line of the e-mail.

K. Cybersecurity

Please state in your White Paper whether your company is National Institute of Standards and

Technology (NIST) 800-171 r1 compliant at the time of submission or when it will be compliant if awarded any follow on contracts from the White Paper.

SECTION IV: AWARD INFORMATION

The funded amount and period of performance of each white paper selected for award may vary depending on the research area, listed in Section III(B), and the technical approach to be pursued by the offer selected.

Award(s) may occur anytime during the open BAA period as well as six months after the BAA closing date. The Government reserves the right to select for award any, all, part, or none of the white papers received in response to this announcement. The Government intends to evaluate and recommend award(s) without discussions based upon its evaluation of white papers; however, the

Government reserves the right to hold discussions if deemed necessary. Discussions with the POCs do not constitute a commitment by the Government to subsequently fund or award any white paper submission. Only Contracting Officers are legally authorized to commit the Government.

This effort requires the lead Principal Investigator (PI) and/or Program Manager (PM) of offerors submitting a proposal under this program to hold a U.S. citizenship. Approval is required from

MDA for any non-U.S. citizen to perform work on MDA research contracts.

The BAA covers export-controlled technologies. Research in these areas is limited to “U.S.

persons” as defined in the International Traffic in Arms Regulations-22 CFR § 120.1 et seq.

Cost sharing is not expected and will not be used as a factor during the merit review of any white paper here under. However, the Government may consider voluntary cost sharing if proposed.

SECTION V: ELIGIBILITY INFORMATION

The Government will accept white papers for review from U.S. industry, accredited colleges and universities, and nonprofit organizations. Federally Funded Research and Development Centers

(FFRDCs) and University Advanced Research Centers (UARCs) are eligible as a subcontractor as long as they are permitted under the sponsoring agreement or charter between the Government and specific FFRDC or UARC. Other interested organizations and Government agencies should contact the technical POC, Leonard Halley, at leonard.halley@mda.mil.

Teaming partnerships are encouraged and teams may submit white papers in any and all areas.

However, the Contractors are responsible for negotiating appropriate Associate Contractor

Agreements (ACAs) and Non-Disclosure Agreements (NDAs) with other contractors as necessary to implement the exchanges of technical data and other information required, ensure total system end-to-end performance, and also to protect technical data and other information from unauthorized disclosure or use. These agreements must not restrict any of the Government’s rights established pursuant to this or any other award The offerors must be willing to cooperate and exchange software, data, and other information in an integrated program with other contractors, as well as with system integrators, selected by C2BMC.

Each Prime and Subcontractor will be required to meet NIST SP 800-171 R1 requirements to develop a System Security Plan (SSP) and Plan of Action and Milestones (POAM) resulting in the implementation of cybersecurity controls on their contractor owned and operated network.

Contractors are advised that, should they be selected to proceed to the next phase of this process, the Government will request their SSP and POAM for evaluation and may require the development of an Information Management and Control Plan (IMCP). These and any additional cybersecurity requirements will be clearly defined in the follow-on solicitation documents. Any vendor not meeting or unable to meet the requirements for Cybersecurity may not be eligible for award.

SECTION VI: APPLICATION AND SUBMISSION INFORMATION

A. Submission Process

This BAA will utilize a two-step process:

1) Step one will be the evaluation of the Offeror’s white paper submission. This step will preclude unwarranted efforts on the part of an Offeror whose proposed white paper is found to be of no interest to C2BMC.

2) Step two will be a request to submit a formal proposal for selected white papers that are found to be consistent with the intent of this BAA and which are of interest to the C2BMC.

Offerors are reminded that this BAA is for the acquisition of advanced component development and prototypes for scientific study and experimentation directed toward advancing state-of-the-art technologies, increasing knowledge or understanding, rather than focusing on a specific system or hardware solution. White papers related to the development of a specific system will not be accepted as they are non-conforming with FAR 6.102(d)(2).

White papers will be accepted starting from the date of publication of announcement and continue to be accepted the entire period of time that the BAA is open.

C2BMC intends to use e-mail for all correspondence concerning HQ0852-21-S-0001

Unclassified electronic (e-mail) questions concerning this announcement shall be sent to the attention of the Contract Specialist, Samuel Cornelius at C2BMC-BAA@mda.mil. The subject line of the e-mail shall read “HQ0852-21-S-0001 White Paper Submission.” The white paper must be a Microsoft Word compatible or PDF format attachment to the e-mail.

If interested in this opportunity, please respond to C2BMC with the following:

• A white paper of 5 pages, which succinctly describes the proposed technical approach, as well as its rationale and objectives, methodology, knowledge points, expected results, risk assessments, and potential contribution to the C2BMC architecture.

Additional Documents (Not included in white paper page count)

• White paper rough order of magnitude (ROM) cost estimate

• A suggested program plan

• A description of the Offeror’s technical capabilities, relevant experience, and facilities

NOTE: DO NOT SEND THE FOLLOWING:

• Hardcopies of white papers (including facsimiles)

• ZIP files

• Password protected files

B. Requirements of White Papers

White papers shall address the entire suggested period of performance. The Executive Summary and Program Description as described below shall not exceed the 5 page limit and anything beyond that limit will not be evaluated. The document shall have one-inch margins on all sides, single-spaced, and use Times New Roman 12 point font. Landscape format is only acceptable on charts and graphs. Use of a diagram(s) or figure(s) to depict the essence of the proposed solution is encouraged. White papers must be valid for a period of not less than 180 days after the submission date.

Offerors may mark their white papers with the restrictive language that is stated in FAR 52.215-

1(Alt. 1). It is the Offeror’s responsibility to clearly define to the Government what is considered restrictive data in accordance with DFARS 252.227-7016.

Unnecessarily elaborate brochures or proposals are not desirable and may be counted as part of the proposal’s page count.

Multiple white papers addressing different topic areas may be submitted by the same organization, however each white paper may only address one concept based on the stated

Government areas of research interest referenced in this BAA. Organizations may submit multiple concept papers addressing the same area of research interest. Offerors may update a current white paper or proposal at any time during the effective announcement period.

1. Title Page (not included in page count):

a. Labeled with “C2BMC BAA WHITE PAPER” and include BAA Number

HQ0852-21-S-0001

b. Title

c. Name, title, telephone, fax numbers, and e-mail address of Offerors technical POC

d. Name, title, telephone number, e-mail address, official mailing address, and signature of the authorized contracting representative

e. Date offer is submitted

f. Abstract paragraph not to exceed 250 words

g. Small business status

2. Executive Summary (not included in page count, not to exceed 1 page in length)

3. Program Description (included in page count):

Describe the techniques, methods, materials, or ideas that will be addressed in this white paper, their innovation, and to what degree they advance the state-of-the-art technologies.

a. Describe the proposed program, objectives, and approach. A description of the innovation and benefits to C2BMC of the proposed approach and relationship to previous efforts should be discussed.

4. Program Plan and Milestone Chart (not included in page count):

Describe in detail, the management plan, technical objectives, and how the plan will be executed. Milestones should indicate when specific objectives are expected to be met in the overall schedule of the program and should identify the specific accomplishments necessary to proceed on to the next task. Describe in detail the critical path of activities for the entire research project and define areas of risk with the risk mitigation plan.

5. Resumes (not included in page count):

Include only the key personnel resumes. Key personnel includes individuals whose name or credentials provide credibility to the proposal.

6. Description of Relevant Prior Work (not included in page count):

Include a list of relevant efforts funded by internal research funds and contracts funded by others for the past five years. For each effort, provide the title of effort, contract number, funding organization (customer), and a brief summary of results.

C. Rough Order of Magnitude (ROM) Cost

Provide Tables 1 and 2, as listed below, for the entire performance period with white paper submission. Additional information, such as breakout by task, is acceptable but not required.

Note: ROM cost is not included in total page count.

TABLE 1: Proposed Effort ROM Cost Element Summary

Year 1 Year 2 Totals

Total Direct Labor (TDL) Cost

Total Direct Materials (TDM) Costs

Total Other Direct Costs (TODC)

Total Indirect Costs (TIDC)

Fee or Profit

TOTAL ESTIMATED PRICE

TABLE 2: Subcontract/Inter-organizational Transfers and Consultants Price Summary

SUBCONTRACTOR NAME

SUBCONTRACT

TASKS

ESTIMATED PRICE

TOTALS

The cost of preparing white papers in response to this BAA is not considered an allowable direct charge to any resulting contract or to any other contract.

SECTION VII: EVALUATION INFORMATION

A. Evaluation Process

The evaluation team will independently evaluate each white paper submitted and provide written recommendations for award or non-award to the BAA Selection Official (BSO) based on a peer or scientific review process in accordance with FAR 35.016. Individual white paper evaluations will be based on acceptability or unacceptability without regard to other white papers and proposals submitted under this BAA. White papers submitted will be evaluated as they are received. The technical and cost information will be evaluated at the same time during the evaluation process.

B. Evaluation Criteria

The evaluation criteria of the white paper include Technical Merit, Capabilities, Management, and Relevance to C2BMC as described below:

1. Technical Merit

a. Does the white paper represent quality research by adequately addressing objectives, scientific methods or engineering practices, expected results and validation of results?

b. Does the proposed research have applicability to the existing/emerging BMDS?

c. Does the proposed research have a clear potential to mitigate critical performance gaps or greatly enhance current capabilities or the affordability of the system?

d. Does the proposed research extend beyond state-of-the-art or represent an innovative game changing technology?

2. Capabilities

a. Does the white paper adequately justify the PI’s and/or key personnel’s qualifications, capabilities, and experience critical to achieving the research objectives?

b. Does the offering institution provide adequate techniques and facilities to complete the proposed task?

c. Does the proposed team include individuals, groups, or institutions recognized as leaders in their field with a strong record of accomplishment in the area of proposed research (e.g., patents, papers, citation, and products) or have a one-of-a-kind capability?

3. Management

a. Does the white paper provide a set of clearly defined tasks and objectives, a logical schedule with appropriate flow between activities, and a list of products?

b. Does the rough order of magnitude cost appear reasonable?

c. Does the white paper demonstrate program management capabilities; e.g., shows the critical path of activities for the entire research project (base plus option years if applicable); provides resource loaded milestone schedules (base plus option years if applicable); defines areas of risk and risk mitigation strategies; and lists products with associated metrics?

4. Relevance to C2BMC & Priority

These criteria will provide the final basis for award selections by the BSO and will be determined directly by the BSO. The ROM cost will be used to determine if there are sufficient funds available for the proposed effort.

C. Evaluation Team

White papers submitted under this BAA will be protected from unauthorized disclosure. The cognizant Program Manager and other Government scientific, engineering, and technical experts will perform the evaluations and selections of the white papers under this BAA. Restrictive notices notwithstanding, one or more support contractors may be utilized as subject-matter-expert technical consultants.

The Government may use selected FFRDCs, UARCs, non-Government contracted support, and other non-Governmental personnel to assist in the evaluation and administrative handling of white papers and proposals submitted in response to this announcement. These persons are bound by appropriate non-disclosure agreements and organizational conflict of interest statements to protect proprietary and source selection information.

Submission of white papers under this BAA constitutes the Offeror’s acknowledgment and consent to the use of non-Government support contractors during the evaluation process.

SECTION VIII: AWARDS

The BSO will make recommendations for awards or non-awards based on the evaluation criteria noted above and MDA funding and technology priorities. The BSO will forward a list of award or non-award selections to the C2BMC Contracts office for further action. The C2BMC Contracts office will then notify selected and non-selected offerors of the evaluation decision and may request formal proposals from the selected offerors.

DO NOT SUBMIT THE TECHNICAL AND COST PROPOSALS UNTIL YOU RECEIVE

A REQUEST FROM THE CONTRACTING OFFICER FOR THIS INFORMATION.

ANNEX 1: TECHNOLOGY READINESS LEVELS

TRL 1 Basic principles observed and reported.

This is the lowest level of technology readiness. Scientific research begins to be translated into applied research and development. Examples might include paper studies of a technology’s basic properties.

TRL 2 Technology concept and/or application formulated.

Invention begins. Once basic principles are observed, practical applications can be invented.

Applications are speculative and there may be no proof or detailed analysis to support the assumptions.

Examples are limited to analytic studies.

TRL 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.

TRL 4 Component and/or breadboard validation in laboratory environment.

Basic technological components are integrated to establish that they will work together. This is relatively “low fidelity” compared to the eventual system. Examples include integration of “ad hoc” hardware in the laboratory.

TRL 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 it can be tested in a simulated environment.

Examples include “high-fidelity” laboratory integration of components.

TRL 6 System/subsystem model or prototype demonstration in a relevant environment.

Representative model or prototype system, which is well beyond that of 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.

TRL 7 System prototype demonstration in an operational environment.

The prototype is near, or at, planned operational system. Represents a major step up from TRL 6, requiring demonstration of an actual system prototype in an operational environment such as an aircraft, vehicle, or space. Examples include testing the prototype in a testbed aircraft.

TRL 8 Actual system completed and 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.

TRL 9 Actual system proven through successful mission operations.

The actual application of the technology in its final form and under mission conditions, such as those encountered in Operational Test and Evaluation (OT&E). Examples include using the system under operational mission conditions.

The above matrix, taken from the DoD Technology Readiness Assessment (TRA) Desk book, lists the various technology readiness levels and descriptions from a systems approach for both hardware and software. DoD components may provide additional clarifications for software.

ANNEX 2: ORGANIZATIONAL CONFLICT OF INTEREST (Jun 2012)

A. Purpose:

The primary purpose of this clause is to aid in ensuring that:

1) The Contractor's objectivity and judgment are not biased because of its present or planned interests which relate to work under this contract;

2) The Contractor does not obtain unfair competitive advantage by virtue of its access to non-public information regarding the Government's program plans and actual or anticipated resources; and

3) The Contractor does not obtain unfair competitive advantage by virtue of its access to proprietary information belonging to others.

B. Scope:

Organizational Conflict of Interest (OCI) rules, procedures, and responsibilities as described in

FAR Subpart 9.5 shall be applicable to this contract and any resulting subcontracts.

1) The general rules in FAR 9.505-1 through 9.505-4 and the restrictions described herein shall apply to performance or participation by the Contractor and any of its affiliates or their successors-in-interest (hereinafter collectively referred to as "Contractor") in the activities covered by this contract as prime Contractor, subcontractor, co-sponsor, joint ventures, consultant or in any similar capacity.

2) The Missile Defense Agency’s OCI policy is in MDA Policy Memorandum 51, “Organizational Conflict of Interest,” May 30, 2012.

C. Access to and Use of Nonpublic Information:

If the Contractor, in performance of this contract, obtains access to nonpublic information such as plans, policies, reports, studies, financial plans, or data which has not been released or otherwise made available to the public, the Contractor agrees that without prior written approval of the Contracting Officer, it shall not:

1) Use such information for any private purpose.

2) Release such information.

D. Access to and Protection of Proprietary Information:

The Contractor agrees to…