What we recommend you include when you submit a solution brief.

View Instructions

Work With Us - Open Solicitations - Commercial

Submit your commercial solutions to solve national security challenges with the help from DIU.

Peacetime Indications and Warning: Global Weather Sensing


Responses Due By

2022-05-30 23:59:59 US/Eastern Time

The Department of Defense (DoD) seeks commercial data solutions for global weather sensing via ground, air, and space-based platforms to improve global environmental situational awareness and analysis, improve performance of global and regional weather physics-based models, and improve performance of global machine learning-based models. The commercial data will be potentially utilized in weather forecasting and impact applications, to include climate change assessment. Priority is with commercial solutions that provide data from outside the Continental United States.


Solutions could include, but are not limited to, satellite constellations with remote sensing technology, ground-based commercial networks with specific weather parameter sensing and/or leveraging Internet-of-Things (IoT) technology, or airborne commercial platforms that actively or passively sense weather parameters. Data collected during this pilot will be made accessible for use in government-run Observing System Simulation Experiments (OSSE) and to evaluate improvements to the U.S. Air Force (USAF)’s current and emerging suite of numerical weather modeling. The data may also be used for machine learning efforts of data analysis, data curation, model training, and model metrics towards evaluating improvement to Air Force Weather’s current and emerging suite of operational machine learning models. The resultant commercial data sources and interfaces should be compatible with the USAF’s Weather Virtual Private Cloud (AFW-VPC), which currently leverages Amazon Web Services (AWS) Gov Cloud weather data computing architecture for subsequent storage and accessibility by USAF weather applications, data processing, and models. 





FAQs

N/A

Artificial Intelligence and Machine Learning for Processing Aerial Imagery


Responses Due By

2022-05-30 23:59:59 US/Eastern Time

The National Guard Bureau (NGB) operates in a multitude of operational domains and frequencies. Shared Situational Awareness (SSA) is a critical component of maintaining an organized and focused mission in order to ensure success. However, constant overturn in staffing, resourcing, and environment due to the nature of “on-call” Guardsmen results in a splintering in the overall SSA picture. Additionally current SSA tools used by the NGB are rapidly showing signs of aging. With multiple sources of ephemeral knowledge and a complex set of imagery analysis requirements, a need for AI/ML-driven knowledge curation and scene understanding naturally arises for domestic operations (DOMOPS).


The Department of Defense (DoD) is seeking software for unclassified processing, assessment, and dissemination of electro-optical aerial images of varying nadirs (collection platforms can range from handheld devices and/or aircraft mounted instruments). The solution will use artificial intelligence (AI) and machine learning (ML) algorithms to create better scene understanding of aerial imagery for various taskings and, ideally, result in lower runtimes and processing power needs compared to legacy systems.



EXHALE - Exhaled Breath Diagnostics


Responses Due By

2022-05-16 23:59:59 US/Eastern Time

Modern warfighters routinely operate in remote and austere environments where access to diagnostic testing or medical personnel is limited. In these environments, the risk of contracting an infectious disease is often high, and sudden illness can lead to mission failure. Existing mobile diagnostic testing equipment is often too large, too invasive, too slow, or too complex to be deployed in a complex operational environment. 


The Department of Defense (DoD) seeks submissions for a hand-held device capable of non-invasively detecting pre-symptomatic early infection of a human subject through an analysis of volatile organic components (VOC) and/or exhaled aerosols present in the subject’s exhaled breath. We envision that the device will allow on‐demand detection of an infected subject upon actively exhaling onto/into a sensor. Submissions should describe the development of a prototype that will be ready for independent testing with human subjects within 12 months of award. 


Specific capabilities of interest include:


  • Ability to detect infection 24-72 hours prior to symptom onset or in individuals without symptoms or with limited symptoms.
  • Ability to distinguish between healthy and infected humans with any of the following, including, but not limited to: two (2) respiratory diseases of viral origin (for example SARS‐CoV‐2, Influenza, or adenovirus) and two (2) bacterial etiologies (for example, Streptococcus pneumonia, Yersinia pestis, or Acinetobacter baumannii).
  • Explain how sensitive personal information will be encrypted and/or protected on the device and through data transmission.
  • Explain how the device can meet MIL-STD-810H.
  • Explain environmental impact for disposable components.
  • Ability to connect to compact and ubiquitous platforms such as cell phones, radios, or Android Team Awareness Kit (ATAK) devices. This device should support analytical software with:
    • AES-256 Encryption;
    • Capability to receive analytical upgrades (such as algorithms);
    • Standard charging connections (i.e. USB family, inductive); and
    • Connectivity via Bluetooth, Near-frequency Magnetic Induction (NFMI).
  • Specifications of this solution include:
    • Disposable mouthpiece for collection/detection of VOCs
    • Size Weight and Power (SWaP)
      • Breath sensor plus readout (unit) - portable size (e.g. <20 cm x 15 cm x 10 cm)
      • W: <1kg
      • P: Self‐contained (e.g., AA batteries)
    • Sensor module
    • Aim to achieve <$2,000 (hardware) and price per test < $5


Alternative (non-exhaled breath or exhaled aerosols) solutions may be considered. However, all solutions will be held to a similar standard with respect to ease of sampling. 


Submissions must include a description of a clinical study plan to identify breath signatures in human populations and to independently evaluate prototypes in human populations. The study plan descriptions must include the names and institutional affiliations of clinical investigators that will lead the studies. Study plans may be Food and Drug Administration (FDA) regulated or non-FDA regulated with local Institutional Review Board (IRB) oversight.


Companies will be expected to draft regulatory plans describing how the performer will complete all FDA submission requirements for a full submission. Initial conversations with the FDA for approval steps should be complete by the end of the award.


Companies must indicate in their written proposal the maturity of their technology and identify any commercial or other security applications that are using their solution. 


The government may recommend teaming arrangements among submissions offering complimentary capabilities to achieve desired effect. Companies are also welcome to present their own teaming arrangements in their solution briefs. However, if a component of a solution brief is compelling, the government may recommend that the provider of that component team with another solution provider. 


Companies without a Commercial and Government Entity (CAGE) code will be required to register in System for Award Management (SAM) if selected. The government recommends that prospective companies begin this process as early as possible. 


Companies must also provide a good faith representation of ownership or appropriate licensing/data rights to the solutions being presented or who or how the company intends to fulfill the needs.


Solicitation Phases:


Phase I: Solution Brief Evaluation - This phase will be executed in accordance with the DIU Commercial Solutions Opening (CSO) process. All solution briefs correctly submitted in response to an AOI will be evaluated against the stated criteria below.


  1. Relevance of the Solution Brief in addressing the AOI;
  2. Company’s approach and/or underlying technology is unique, underutilized and/or innovative to government application. In addition, the government finds this approach and/or underlying technology to be a compelling solution to the AOI problem statement.
  3. Technical merit and feasibility of the solution to address the government’s AOI problem statement.


Phase II: Demonstration/Pitch - This phase will be executed in accordance with the DIU CSO process with the following modifications. The pitch phase may be held in person. The Pitch Phase will require a recorded video demonstration of the baseline technology to be used to develop the proposed solution. The intent is to provide the evaluation team with an understanding of the current maturity of the proposed solution. The government will not provide funding for company participation in Phase II. Specific details will be provided if your company is invited to the Phase II Pitch.


Phase III: Proposal - This phase will be executed in accordance with the DIU CSO process and will consist of a collaboratively developed performance work statement (PWS), technical proposal, cost proposal, and the OTA terms and conditions.


Submission Requirements

Submissions should include an overview and technical details of the proposed solution. Inclusion of examples of the successful deployment of similar solutions in the commercial or public sectors is highly encouraged. 


Preference will be given to submissions that present a comprehensive and compelling solution to the problem statement and product requirements. Proposals should identify whether the submitter will employ subcontractors and, if so, which companies would deliver which capabilities. 


Any resulting agreement from this AOI will include language requiring your company to confirm compliance with Section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232). If you are unable to confirm compliance with the referenced law, the government will not be able to enter into an agreement with your company


Awarding Instrument:


This Area of Interest solicitation will be awarded in accordance with the Commercial Solutions Opening (CSO) process detailed within HQ0034-20-09-DIU posted to www.sam.gov in March 2020. Additionally this document can be found within the DIU Library at www.diu.mil/library.


References:


1. Amundson DE, Weiss PJ. 1994. Pneumonia in military recruits. Mil Med 159:629–631.

2. Sanchez JL et al., Respiratory Infections in the U.S. Military: Recent Experience and Control, ClinMicrobiol Rev. 2015, 28(3): 743‐800; https://www.ncbi.nlm.nih.gov/pmc

Unmanned Systems For Maritime Domain Awareness (MDA)


Responses Due By

2022-05-23 23:59:59 US/Eastern Time

In the context of international competition between states, the U.S. Navy maintains freedom of navigation and access to waterways around the world. This is critical to the free flow of goods and commerce, but there are insufficient assets to maintain a constant physical presence in the many critical maritime areas globally. However, with a network of unmanned and autonomous platforms, the Navy can maintain broad awareness, and react quickly as required.


To solve this, the Department of Defense (DoD) seeks state-of-the-art commercial solutions for Maritime Domain Awareness (MDA). Only solutions that are technically mature and immediately demonstrable will be considered. Solutions selected for this project will be required to participate in a 35 day DoD exercise in November/December 2022 at a location outside the continental United States. Transportation of equipment to and from the exercise from the mid-atlantic U.S. will occur via military aircraft. Alternate transportation will be by exception only and at the government’s discretion.


The DoD seeks the following hardware and software solutions:

  1. Specific unmanned and autonomous vehicle (UxV) capabilities, by class:
    1. Unmanned Surface Vessels (USVs)
      1. USVs must be capable of transit from a launch point to a patrol area up to 200 nautical miles (nm) away. 
      2. USVs must be capable of loitering/station-keeping in the patrol area. 
    2. Buoys and/or Fixed Sensors
      1. The government will consider platforms without propulsion/station keeping ability independent of USVs.
    3. Unmanned underwater vehicles (UUVs) and autonomous underwater vehicles (AUVs) must have a minimum endurance of 96 hours in an operational setting.
    4. Unmanned aerial vehicles (UAVs) designed for operation over a power/data tether and from a moving vessel will be considered.
      1. UAVs should be prepared to document compliance with applicable statutory and regulatory requirements related to manufacturing.
  2. General Capabilities Applicable to all classes of UxV:
    1. The government will consider the implications of speed and endurance capabilities of all proposed solutions.
    2. Must have sensors native or available for integration into the platform with no additional development/non-recurring engineering (NRE). The government will consider the implications of the type and characteristics of available sensors on the proposed solution. 
    3. Must be capable of transmitting mission data (defined below in 2.4.) beyond line of sight (BLOS), either natively or with a government furnished radio. The government will consider the type and characteristics of available communications modules - line of sight or BLOS - on the proposed solution.
    4. The government desires the platform mission data to be exportable in a common data format or via an application programming interface (API), and will consider the ease of ingesting and integrating mission data into other commercial and government systems. Examples of relevant types of mission event data includes (but is not limited to):
      1. Platform engineering operations and hull, mechanical, electrical (HME) data;
      2. Situational awareness data to include sensor feeds;
      3. Autonomy mission logs; and
      4. Edge processed data (e.g. autonomous target recognition (ATR)).
    5. The government desires a native capability to detect and identify surface vessels not equipped with an Automatic Identification System (AIS) transponder. Ideally, the capability is capable of characterizing the vessel behavior as regular or anomalous. The government also desires a generic object detection and avoidance capability native to the platform.
      1. This data should be available via the exportable dataset described in 2.4 (above).
    6. The government desires platforms to have native or available capability to receive abstract operator input (e.g. a mission objective) then decompose and prioritize that input into discrete tasks. This is sometimes referred to as “Mission Level Autonomy.” Commonality between platforms will be via this high-level command and control (C2) and the government will consider how much additional operator monitoring the platform requires to function
  3. Data Integration Platform
    1. The government desires the capability to receive disparate streams of mission event data over a BLOS data link and parse those non-homogenous streams for common data elements into a common schema. Examples of relevant types of mission event data includes (but is not limited to):
      1. Platform engineering operations and hull, Mechanical, Electrical (HME) data;
      2. Situational awareness data to include sensor feeds;
      3. Autonomy mission logs; and
      4. Edge processed data (e.g. ATR).
    2. The government desires the ability to integrate and visualize - geospatially - mission data information from multiple data sources (platforms) in a common operating picture (COP).
      1. The government will consider the ease at which this can be done
    3. Ideally, the government desires the ability to transfer data from a lower security domain to a higher security domain in near real time, without the use of physical media to facilitate transfer, while ensuring data integrity.
    4. Ideally, given sensor data from a platform, the government desires a capability to detect and identify surface vessels not equipped with an AIS transponder. Ideally, the capability is capable of characterizing the vessel behavior as regular or anomalous. The government also desires a generic object detection.


Coordinating Instructions

Vendors should address the following considerations in their submission:

  1. UxV platform solutions should address their method of launch and recovery, and any associated support equipment required.
  2. UxV platform solutions should address the existing communication modules in use or available, including make/model, and spectrum requirements. If awarded, the vendor will work with DoD Combatant Commander for spectrum approval.
  3. UxV platforms solutions should address the embedded onboard sensors, their capabilities and limitations.

FAQs

Awarding Process:

DIU


Question: Do vendors need to have security clearances to submit solutions to this AoI, and participate in prototyping?

Answer: No.


Question: Are you looking for a complete solution to all the areas mentioned, or are you open to capabilities that address a smaller subset that could be integrated into larger platforms to address the overall solution?

Answer: The government is considering technically mature and demonstrable-now solutions for (1) UxS *and/or* (2) data integration platforms.

  • Vendors with a mature UxS solution that meets the criteria listed in sections 1 and 2 above may submit. 
  • Vendors with a mature data integration system that meets the criteria listed in section 3 may also submit.
  • Vendors with both UxS solutions and data integration solutions may submit both solutions.
  • Vendors may submit more than one solution for any combination of the above.


Question: Can vendors propose a teaming or teamed solution?

Answer: Yes.


Question: Does the DIU intend to purchase the hardware proposed for this exercise?

Answer: Although DIU may purchase hardware when it issues Prototype Other Transaction Agreements, the purchase of hardware for prototyping is not the intent of this project.


Question: Is DIU planning to award multiple OTA contracts to different suppliers for each of the four classes listed in the call?

Answer: DIU may award more than one Prototype Other Transaction Agreement for this project.


Question: The CSO instructions (Section 3.2) state that the Executive Summary should be 1 page. Can offerors propose an exec sum that is less than 1 page and still be compliant with the submission requirements?

Answer: The executive summary may be less than one page.

Smart/Wearable Fatigue Tracking (SWiFT)


Responses Due By

2022-05-16 23:59:59 US/Eastern Time

Problem Statement: Fatigue is a major contributing factor to aircraft mishaps, both within and outside of the Department of Defense (DoD). Fatigue costs the U.S. Air Force (USAF) an estimated $140m every year and places aircrew and public lives at risk. In order to better manage fatigue-related mishaps, the DoD desires an advanced fatigue tracking system to mitigate risks and implement effective countermeasures. 


At present, U.S. military aviators are routinely tasked to operate long, mentally tasking, no-fail missions with limited tools to combat fatigue and minimal awareness of any fatigue related risks. The aviation operational risk management (AvORM) program is the current USAF solution for mitigating mishaps associated with pilot fatigue. Current AvORM practices involve a subjective (self-reported) assessment of fatigue to inform “go/no-go” decisions prior to flight. This approach is susceptible to error, given that individual self-reported ratings are often inconsistent with objective (physiological, behavioral) measures of fatigue. Moreover, the AvORM system is limited in its ability to assess future fatigue states and currently only employs a decades-old generic biomathematical model accounting for sleep opportunity and circadian factors. To better meet the challenges of the global mission environment, USAF aviators are in need of a modernized technical solution for tracking, anticipating, and combating fatigue.


The DoD seeks solutions for developing an algorithm that uses readily available commercial-off-the-shelf (COTS) wearables to track and predict cognitive fatigue. Algorithm solutions will be validated against gold-standard assessments of fatigue using the Psychomotor Vigilance Task (PVT). The successful algorithm should account for ≥ 60% of real-time cognitive fatigue and demonstrate a predictive capability of detecting future fatigue prior to fatigue onset. Companies are encouraged to design a solution that can be personalized to an aircrew member, is adaptable to different contexts and inputs, and that can provide both a fatigue snapshot and a fatigue outlook of at least 12 hours (for example, see the below figure). Outlook uncertainty should be low for shorter projections, but may increase significantly for longer projections (e.g., 12-24 hours).  


https://lh4.googleusercontent.com/V4ngkS-OhFrSIFs9bk_BEiVMKFp2kZiafi3ox9Vs21ZXbRN5wugRtJIyh31AOv0dctOW2aIKpV8HeruALpKHFtuNj9PXJugLlPaKii7IbhX9J4q4FCwIvWGG528n10KV_erFet3f


The algorithm must use input from COTS wearable devices. Solutions compatible with finger or wrist-worn devices will be favored over other wearables due to compatibility with cockpit environments, but will not be restricted to these types of wearables. The wearable devices must not have WiFi, microphone, or video recording technology and must be able to easily synchronize data to a cloud infrastructure and repository through existing mobile device applications. The wearable devices must be able to hold at least 12 hours of data on the device between cloud synchronization events. We encourage non-wearable companies with algorithm solutions to partner with a wearable device company for ease of data access. While the DoD has already identified candidate wearable devices to use, companies are encouraged to bring other non-invasive wearables to test, as well.  


This will be a competitive 12-month prototyping effort involving only U.S. companies, in conjunction with a human subjects research protocol through Naval Postgraduate School’s (NPS) Institutional Review Board (IRB). The protocol and data collection will all be managed through NPS to include aircrew data using the PVT, Automated Neurosychological Assessment Metrics (ANAM), and a variety of sleep and/or fatigue questionnaires. NPS may also employ research-grade neurophysiological sensors in order to compare against COTS wearables. Biometric data will be collected before, during, and after complex full motion Air Force simulator missions, as well as during live flights in USAF aircraft. The data will then be pushed to a government-owned data repository for selective distribution. 


The final deliverable includes a fatigue algorithm capable of scoring biometric data within one hour of data arrival. The successful company will be able to market this algorithm to the commercial sector, but the DoD will retain government purpose rights for usage.


The DoD will retain access to wearable sensor datasets for pre-identified government users. Any participating wearable company desiring to collect and utilize wearable data from government research participants using their own proprietary sensors must agree to allow the government to ingest the data into existing data repositories owned and operated by the government. Wherever possible, the vendor needs to provide access to the lowest level of sensor data available (e.g. electrocardiogram waveform in highest sampling rate available for heart-rate variability analysis). This access could come in the form of sensor data logs or API integration with the feature detection components on the device itself. This biometric data, along with other data, including responses on surveys and the psychomotor vigilance test, will then be made accessible to parties on this contract.    


Awarding Instrument:

This Area of Interest solicitation will be awarded in accordance with the Commercial Solutions Opening (CSO) process detailed within HQ0845-19-S-C001 (DIU CSO), posted to FBO in Apr 2019. Additionally this document can be found within the DIU Library at www.diu.mil/library.

Enhanced Protection of Information Capabilities (EPIC)


Responses Due By

2022-05-16 23:59:59 US/Eastern Time

Exploitation of digital footprints is a primary concern for the Department of Defense (DoD). The privacy and protection of DoD personnel in specialized professions is critical for safeguarding sensitive information and the lives of servicemembers and affiliated personnel. Yet, current practices and digital services continue to proliferate data that may be aggregated to identify and track DoD personnel. Without the knowledge and tools to manage and protect digital information, DoD personnel remain vulnerable through higher risk of information spillage and privacy breaches. Indeed, adversaries have exploited security gaps to gain access to sensitive DoD information. 


In response, the DoD seeks a blend of 3 separate technical, analytical, and training solutions to address key digital fingerprint security gaps with the following qualities:


  1. The DoD seeks technical solutions capable of customizing validated commercial technologies for onboarding, managing, and offboarding personnel and their data over the course of their career. These technologies and portals must be tailorable to allow for secure communications on unclassified channels. They should be hosted on a secured, cloud-based platform that enables protection of both the identities of the applicants and the requisite hiring entity, as well as the obfuscation of data throughout. The web portal should ensure modern and effective cybersecurity protocols throughout to include digital authentication compatibility (e.g., DoD Common Access Card (CAC) authentication), end-to-end encryption of data transmission, and secure data storage processes. The web portal will serve as a focal point for personnel, providing informational tools and integrating with screening/assessment algorithms, while enabling secure, obfuscated communication methods between entities. Example user interfaces should be capable of supporting all or some of the following components:
    1. An information page on which descriptive text, contact information, and multimedia files may reside.
    2. A Screening Tool that determines whether individual candidates are qualified to submit an application and determines access to other site features.
    3. An Application Portal with dynamic content and fields conditional on responses that is capable of securely receiving and temporarily storing applicant-provided files and information.
    4. An Alumni Network Platform with forums for information sharing and communication among separated personnel.
    5. A Communication App that can support direct secure end-to-end encrypted messaging and/or Voice over Internet Protocols (VoIP) calls among users.
  2. The DoD seeks specialized training solutions capable of providing instruction related to human intelligence, ubiquitous technical surveillance (UTS), and counterintelligence to assist in training personnel on how to best protect personal and organizational information. Tailored courses of instruction that can be iterated based on organizational needs and feedback, and implement the most current doctrine, tactics, techniques, and procedures through hands-on training, practical exercises, and role-playing scenarios are preferred.
  3. The DoD seeks analysis solutions from industry experts in managing an organization’s digital signature through continuous risk management. Specifically, the approach should focus on best practices related to safeguarding data footprints, attacks, and spillages. Successful solutions should be capable of analyzing organizational and individual processes; these solutions should leverage industry standards and best practices to reduce data vulnerabilities throughout the organization. Analysis tools should address one or both of the following:
    1. Continuous UTS analysis of an organization’s vulnerabilities and threats through the survey and assessment of organizational behavior and digital signature practices to guide recommendations of organizational risk management techniques and services.
    2. Implementation of user and entity behavior analytics (UEBA) with a Zero Trust approach to monitor for and flag deviations in patterns using data gathered on existing DoD systems operating in classified channels.

Notes

  • The DoD partner will be responsible for the majority of the integration of technical solutions into existing government software services. Therefore, technical proposals should be commercial on-premise or commercial Software as a Service (SaaS) solutions.
  • Multiple contract awards are planned, and a single company is not expected to provide a solution that covers all 3 solution areas. The most worthy product mix will include point-solutions with evidence of similar deployments to supplement an existing system.
  • Preferential consideration will be given to solutions that have been built and deployed for similar problem sets at similar scale. Specific examples of similarly scaled implementations of comparable criticality are expected.
  • The DoD may facilitate teaming arrangements among submissions offering complimentary capabilities to achieve desired effect. Companies are also welcome to present their own teaming arrangements in their solution briefs. 
  • If technology solutions are proprietary, companies must be able to describe the technology in use.
  • Academic research proposals are not desired.
  • Where required (technical and analysis solutions), existing authority to operate (ATO) and/or certification as a system of record are a plus. Vendors must possess or be able to obtain Federal Risk and Authorization Management Program (FedRAMP) Moderate/High accreditation along with Defense Information Systems Agency (DISA) Impact Level (IL)-4 provisional authority (PA) or offer solutions that are compatible with services that have already attained an ATO and are DISA IL-4-compliant. Final product(s) must be compliant with FedRAMP Moderate to High Impact Risk Level. For more information, see DISA DoD Cloud Authorization Process document.
  • This solicitation is open to U.S. vendors only, and selected companies must possess or be able to obtain a U.S. National Security Facility Clearance.
  • Companies without a Commercial and Government Entity (CAGE) code code will be required to register in the Systems for Award Management (SAM) if selected. The DoD recommends that prospective companies begin this process as early as possible.
  • Any resulting agreement from this AOI will include language requiring your company to confirm compliance with Section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232). If you are unable to confirm compliance with the referenced law, the government is unable to enter into an agreement with your company
  • This solicitation will be awarded as a 10 U.S.C. 4022 (formerly 10 U.S.C. 2371b) Other Transaction (OT) authority agreement. Any small business or non-traditional vendor is encouraged to apply. Vendors not meeting those conditions can qualify under the following conditions:
    • Teams with at least one non-traditional defense contractor or non-profit research institution with significant participation in the prototype project.
    • At least one-third of total costs must be paid by parties to the OT other than the government.

Non-Traditional Defense Contractor definition: An entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by DoD for the procurement or transaction, any contract or subcontract for the DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section (see 10 U.S.C 2302(9)).


Solution Brief Requirements:


Solution Briefs should not exceed five (5) written pages using 12-point font or, alternatively, Solution Briefs may take the form of briefing slides which should not exceed fifteen (15). Please note that there is a 10MB file upload limit.


Suggested Content:


  • Title Page (does not count against the page limit): Company Name, Title, Date, Point of Contact Name, E-Mail Address, Phone, and Address. Specifically identify the solicitation for which the Solution Brief is submitted. Indicate the solution area(s) of Technical, Training, and Analysis being addressed.
  • Executive Summary (one page): Provide an executive summary of the solution.
  • Technology Concept: Describe the unique aspects of your technology and the proposed work as it relates to the solicitation. Describe the data, including data elements, age and volume. Identify whether the effort includes a pilot or demonstration of existing technology (identified as commercially ready and viable technology), or the development of technology for a potential defense application. If development or adaptation is proposed, identify a suggested path to mature the technology. Identify aspects which may be considered proprietary.
  •  Company Information: Provide a brief overview of the company, including a summary of gross sales/revenue and investors funding rounds (if applicable). Provide a summary of product history, roadmap, and go-to-market strategy.
  • Unnecessarily elaborate brochures or proposals are not desired.
  • Including an existing customer list and/or customer case studies is encouraged.


Awarding Instrument:


This Area of Interest (AOI) will be awarded in accordance with the Commercial Solutions Opening (CSO) procedures outlined in HQ0845-20-S-C001, posted on SAM.gov, Updated Published Date: March 23, 2020. See https://sam.gov/opp/e00f6563e0c84a04adc0a36215663e15/view.