OpML BAA INDUSTRY DAY ANNOUNCEMENT

Special Notice Posted

A newer pre-solicitation was posted. See the latest pre-solicitation from .

Solicitation number
FA8750-19-S-7014
Agency
Air Force Research Laboratory Air Force Materiel Command, Department of Defense
Set-aside
No set-aside

Opportunity facts

NAICS code
541715 Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology)

Notice details come from SAM.gov. Updated .

About this opportunity

The Air Force Research Laboratory published a Special Notice announcing an Industry Day on August 2nd for its Operationalizing Machine Learning for Command and Control program. The Industry Day provided contractors an overview of the program's goal of identifying, developing, and evaluating applications of artificial intelligence and machine learning to support operational command and control processes.

The Special Notice informed contractors that the Industry Day would outline the program's objective to identify paired machine learning approaches and operational use cases in areas such as air combat and air mobility operations planning, decision-making, and management. Contractors were required to register by July 31st for the Industry Day, with attendance limited to 199 across all organizations. Eligible parties will have an opportunity to respond to the forthcoming solicitation for white papers evaluating prototype solutions later this year, with a focus on planning, operational/tactical decision-making, and operational execution management.

Notice text

2 versions

Update #2 · Latest ·

OpML BAA Questions and Answers
Aug 02, 2019


Presentation Questions
• Will the presentation materials (all Distribution D) be release via FBO, AMERDEC or other means? Distribution D material will be distributed via AMRDEC upon request to Distribution D qualified entities. Overview slides will be posted with Q & A on FBO.


• Can you tell us a bit about Flyleaf: Is it a "multidomain env." in a MLS sense, or air-cyber-space, or both? Additional info on Flyleaf will be available soon, most likely via AMRDEC upon request. In the meantime, Flyleaf is a program with a goal to create a capability within AFRL/RI to assess, in a multi-domain command and control (MDC2) context, the maturity and operational applicability of various C2 applications and micro-applications - all with a mind toward their transition to the Air Force ShadowOC infrastructure and architecture. Flyleaf is an unclassified program. Flyleaf's focus is on the multi-domains of air, space, and cyber.


• From Tom Clark's Brief: To date, every effort socialized through Kessel Run has required the industry partners to be from the greater Boston area. Is AFRL inferring that any further effort (beyond the scope of the BAA) may mean participation by a non-Bostonian company? Else, what was the purpose of specifically mentioning this? Kessel Run was only mentioned for context and to show that the OPML program is aware of Kessel Run and its mission to replace AOC WS 10.2.


• Where is CRC ID # generated? (Aircraft vs Geese) - from D. Marks presentation. Does the ID# have structure? What is the structure/key? Due to answer specificity, please contact OPML TPOC for Distribution D based answer to this question.


• Has UCI been applied to operational - level workflows? Yes


• How do AFRL AI/ML MDC2 efforts align with efforts currently underway or sponsored by the Office of the Chief Architect and those of AFLCMC C3I & N? AC2 CTC has briefed AI/ML based MDC2 efforts in its portfolio and coordinated with AFLCMC C3I & N and PEO Digital


• Where in the USAF, DoD, or OSD is the integration of CONOPS, IT, + Workforce Development being worked? Not sure to what portion of AF (C2, MDC2, ISR, etc.) this question refers to.
Technical Questions
• Are there any preferred tools or programming environment for the software prototype development and delivery in Task 1? Programing environments and tools are up to performer. Open-standards and industry best practices are encouraged. Lock-in and dependence of proprietary software is discouraged.


• The BAA shows the sources of some possible input data. Will the government provide some of such data to the project teams for testing and validation of the developed software prototype when executing the projects? We are not providing that data. Each performer is responsible for identifying specific data requirements and we will do our best to help with the acquisition.


• Will the program consider the uncertainty quantification in the contingency planning? It seems that this factor is not emphasized in some topic areas, although briefly mentioned in the program goal. Uncertainty quantification is of relevance, and is likely to be use-case specific.


• Related question; how much effort to put into building interfaces to other systems (e.g., to get air crew information for TACC missions)? The level of effort is dependent on the approach and domain. The focus is on the ML-based function. Other systems can be stubbed in.


• Is there an objective to push OpML processing out to the combat "edge", to the CRC's and to potentially account for disconnected operations? OPML does not have disconnected operations as an objective. The use of CRC's as it relates to Battle Management functions is considered within scope.


• What are the criteria upon which the AI/ML algorithms will be judged? The BAA provides criteria for source selection with respect to AI/ML application in task 1. The performer develops evaluation criteria following task-dependent templates in BAA. For task 2, we want simulation executions on the order of seconds.


• Technical Task 3 in the "Task 1 Technical Tasks" involves "with SME input, identify[ing] and develop[ing] input training data." Does AFRL envision a generative data approach driven by SME-provided heuristics? All approaches will be considered, "identifying and developing input training data" implies that the performer might develop the data using generative means. This is not necessarily the case. Finding a relevant dataset is sufficient. Generative approaches will be considered but are not required.


• Technical Task 7 in the "Task 1 Technical Tasks" describes developing a multi-domain use case or workflow for the proposed approach. Does AFRL envision this analysis to be restricted to varying capabilities/assets between domains, or should performers also consider different command chain hierarchies, operational languages, etc. between various services? No restrictions on developing a use case or workflow. The more detailed and realistic the workflow is to current operations, the better.


Programmatic Questions
• Are you open to follow up discussions in the next week of two? Yes, please contact the POC for availability.


• Can a company submit multiple proposals to Task 1? Yes, no limit to the number of white paper submissions from a single company.


• Are multiple related AF Threads acceptable as a single proposal? Yes, to be clear we are requesting whitepapers first.


• Are we restricted in classification of data (is this unclass only)? Yes, there are restrictions. Allowed classification levels are up-to-and-including SECRET, as mentioned in the BAA.


• P7, Under 'Task 2 Technical Tasks, 2. (Phase 2a) "Identify SMEs with relevant experience," - Can the SMEs be from, be asked to participate from the active Air Force, for example those serving on the Joint Staff or the Air Staff? Yes, it is up to the proposers to acquire SMEs, either as part of their internal team, or as a consultant.


• In the "potential evaluation criteria" tables of the operational threads attachment, there is no mention of evaluating ML approaches based on their required dataset sizes, training time requirements, or execution speeds. Are these metrics out of scope for this effort? Potential evaluation criteria, literally meant as "potential"; therefore, you are welcome to pick the one that makes most sense for your approach.


• The BAA mentions awards would be for 24 months, but the schedule including options is 27 months. Should we assume a 24-month schedule? Assuming this refers to Task 1. Task 1 schedule is a 9 Month prototype development + 6 Month refinement. Task 1 option is an additional 12 Month priced separately.


• Is on-site presence required/preferred? No, an onsite presences is not required.


• Is building on StreamlinedML a hard requirement? No, this is not a hard requirement.


• Can it be combined with other framework? You can combine with other frameworks, locked in and proprietary systems are discouraged. No end-to-end systems.


• Different/larger award range for Task 2? Please refer to the BAA.


• Will AFRL be integrator for Capstone? Yes


• In Table 2, what is meant by an "Air Thread"? Operational Workflows for those functions.


• How much weight of effort towards M & S dev is acceptable? Depends on your approach to the problem.


• Is there any preference on the teaming? (small business of large business, alone, or combinations with academia?) No, there is no preference.


• If the white papers we submit only answer partial portions of your requirement will you suggest possible partnerships? (Not everyone has or can provide a full end to end solution.) We are not asking for End-to-End solutions. Forming partnerships is the responsibility of the performers. The Government will not be recommending partnerships.


• In what format will the offeror deliver the design of the simulation and evaluation environment? And does Task 2 involve an evaluation of the environment itself by the USAF? We are open to any format for the simulation. Open-standards and industry best practices are encouraged. The USAF would incrementally evaluate the environment during the life of the contract.


• For this BAA, how much of focus is specificity vs. generality? I.e. engineering solution for a specific application vs. novelty of algorithmic approach? We are looking for a specific solution to an Operational process. Algorithmic approaches need not be novel.


Scope Questions
• Are there some threads more important than others (e.g. MOG Planning or Tactical Chat)? No, there is no preference of one thread over another.


• Is there interest in applications of AI/ML to operational C2 outside of the 8 threads in the BAA? Yes, the threads were meant as examples of potential areas. We are open to all applications to any operational C2 process.


• Will the government accept proposals that focus on future systems, e.g. UAVs vs. existing manned fighters? No, the focus of the BAA is on existing C2 processes and systems.


• Does AFRL have any interest in an anytime ML algorithmic approach, particularly for in-mission operational threads? All ML algorithmic approaches will be considered.


• Are there specific CONOPS of interest, e.g. A2AD, SEAD, COIN etc.? No. Choose the one that makes most sense (availability of data, well defined con-ops) for your proposed approach.


• Preferred domains for multi-domain? Air/Space/Cyber but we are open to others as long as they are within scope as described in the BAA.


• It was stated that algorithms for ISR are out of scope. What about algorithms/frameworks for ISR C2? Out of scope.


• Is it relevant to the BAA: The AI/ML mission planning in the presence of sections of Autonomous UAVs? Yes, mission planning is within scope as described in the BAA.


• Is it relevant to the BAA: The planning of new operations that include new Man Unmanned Teaming (MUM-T) in the battlespace? Yes, planning is within scope as described in the BAA.


• ISR not in scope, but how about multi-agent target tracking and engagement? This is application dependent, multi-agent tracking and engagement is within scope as long as the solution is applied to a non-ISR operational C2 problem.


• What is the level of interest in Nonlinear Independent Component Analysis? This area is of less interest unless data-driven or accurately mapped to a current process or workflow.


• What is level of interest in these machine learning attributes/capabilities: - Explainability (of autonomous decisions)? - Casual Reasoning? Both are of interest as long as they are applied to an operationally relevant problem within scope of the BAA.


• What is level of interest in these Technologies/Techniques: - Evolutionary Algorithms? - Information Theory? Both are of equal interest as long as they are applied to an operationally relevant problem.


• Is the Battle Management being considered only at the CRC level or also as applicable to JSTARS/AWACS/ASOC? Yes, applicable to all platforms listed in your question.


• What kind of Machine Learning (ML) algorithms will be considered? Any one that can solve the problems? There are no restrictions in algorithm consideration. The algorithm chosen should solve the problem in question.


• What is the scope for Battle Management (CRC) that ML should be applied to? I.E. Track on Radar, Discussion Support, ...? Currently there is no limit with respect to the CRC function.


• Are you looking for overall solutions or solutions for individual problems? The OPML BAA is looking for ML-based solutions to individual functions.


Repeat Questions
• Do you have preferred data sources? No, there are no preferred data sources. However, data should be representative of what is expected in the real world.


• Are their curated data sources? If so, what are they? No. Already answered.


• It is stated on p3 task 1 "The use of ML must leverage a repository of training data in order to improve the predictive assessment of future data points." Does this mean that you have a repository of data that we are required to use? No. Already answered.


• Do you have any repository of data? No. Already answered.


• Will the government provide any data sets to support machine learning/training? No. Already answered.


• Multiple whitepapers by a proposer? Yes


• Can offerors propose against multiple operational threads? Yes


• Is historical readiness data from AOC's available: - How many missions of varying types were scheduled vs. flown? - Maintenance of aircraft availability? - Would a DD254 be necessary, possible for this type of data? We are not providing this data.


• Where/how can we obtain more information about the Flyleaf environment? Already answered above.


• Would you consider AI/ML applications that support other functions of the AOC beyond those defined in the operational threads, such as spectrum management? Yes


• Since data cannot be provided, can AFRL provide detailed process map of the data types, structures API that will go into task 1 so industry has an accurate representation of the process flow needed to be improved. That is characterization of the data if not the real data. No, the government will not provide process maps, API's, etc. Process map, data types, etc., should come from proposer team as described in BAA.


.

Update #1 ·

OpML BAA Industry Day Announcement

The Air Force Research Laboratory/Information Directorate will be conducting an Industry Day on 02 August 2019 regarding upcoming Broad Agency Announcement (BAA) FA8750-19-S-7014 for the Operationalizing Machine Learning for Command and Control (OpML C2) program. The purpose of this meeting is to provide interested companies/entities with an overview of the problem space that the OpML program is attempting to address. This meeting hopes to address specific areas of interest, promote an early exchange of information, and provide an opportunity for both the Government and Industry to gather more information prior to the request for white papers that will be published on the Federal Business Opportunity web site.


A general session will be held from 0900 to 1200. After presentations, written questions will be accepted and answered after a short recess. For those that cannot make the industry day, a copy of the slides used will be posted to FBO as well as all the questions and answers.


The Industry Day session will be held at the Griffiss Institute, 725 Daedalian Drive, Rome, NY 13441. Registration for this event is required and can be done at: https://app.smartsheet.com/b/form/a0b78e36e975481ba3b9ab5d102e08c2
Check-in will be from 0830 to 0900.


Registration must be submitted no later than 31 July 2019. Registration submissions using the above email will not be accepted after 31 July 2019. Attendance is limited to no more than 199 people and registration will close when that number is met.


Attendance is limited to two individuals per CAGE code. Attendees are encouraged to submit written questions in advance. Note: This announcement is not a contract, request for proposal, a promise to contract, or a commitment of any kind. The Government will not assume liability for costs incurred by any attendee for presentations, marketing efforts or data offered for examination.


DESCRIPTION:
The Autonomous Command and Control Core Technical Competency (AC2 CTC) is seeking to identify, develop, and evaluate novel applications of Artificial Intelligence (AI) and Machine Learning (ML) to support operational aspects of Command and Control (C2). Our initial analyses considered wide-ranging applications of ML in the air combat and air mobility operations centers, as well as interesting applications for air battle management C2. The analyses have narrowed down the space of paired operational applications and their potential ML solutions to a manageable set of specifications without precluding the proposal of other unique and novel approaches. The sought-out solutions primarily focus on the problems of planning, operational and tactical level decision making, and operational execution management. The development of prototype applications, respective use-cases, workflows, and data requirements are critical to establish the viability and usefulness of the assessed candidate applications for assessment in an operational setting.



Technical POC:


Mr. Gennady Staskevich Mr. Carlos Merlos
AFRL/RISC AFRL/RISC
525 Brooks Rd 525 Brooks Rd
Rome, NY 13441-4505 Rome, NY 13441-4505
Telephone: (315)330-4889 Telephone: (315)330-4128
Email: gennady.staskevich@us.af.mil Email: garlos.merlos@us.af.mil



Dr. Alvaro Velasquez
AFRL/RISC
525 Brooks Road
Rome, NY 13441-4505
Telephone: (315) 330-2287
Email: alvaro.velasquez.1@us.af.mil

.

Attachments

Files attached to this notice, newest first
File Type Posted
OpML_Industry_Day_Presentation.pptx PPTX presentation

Notice history

Notices posted for this opportunity, newest first
Notice Type Posted
Operationalizing Machine Learning for Command and Control (OpML C2) Latest pre-solicitation Pre-Solicitation
OpML BAA INDUSTRY DAY ANNOUNCEMENT This notice · Original Special Notice

On GovTribe

Work this opportunity on GovTribe

  • Track it in your pipeline
  • Find teaming partners
  • Similar opportunities
  • Ask GovTribe AI about this opportunity