DEMSAW CALL 0007 Questions and Answers 2_22 Dec 2021.pdf
PDF 265 KB Posted
- Attached to
- Call 0007 entitled "Directed Energy Modeling, Simulation, Analysis, and Wargaming (DEMSAW)"
- Solicitation number
- FA9541-21-S-0001Call0007
About this file
This call announcement solicits white papers for an Indefinite Delivery Indefinite Quantity (IDIQ) contract to provide Directed Energy Modeling, Simulation, Analysis, and Wargaming (DEMSAW) services to the Air Force Research Laboratory (AFRL) Directed Energy Directorate Wargaming and Simulation Branch. Key services required include developing directed energy concept models, creating mission-level scenarios, conducting simulations and analyses, and performing military utility assessments utilizing the Advanced Framework for Simulation Integration and Modeling platform. The scope also includes wargaming and concept development efforts to integrate concepts into a virtual range for evaluating military utility. Incumbent contractors are BlueHalo and Aegis Aerospace. White papers will be evaluated based on technical merit, relevance to the Directed Energy Military Utility program, and affordability. The preference is to award based on the initial white paper submission. The potential IDIQ contract has a minimum five-year period of performance with an additional five years optional.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DEMSAW CALL 0007: Questions and Answers
1. Are there any specific existing AFRL/RDM-developed AFSIM tools or plugins they would like to have developed or maintained? If so, what are they?
a. There are currently five AFSIM Directed Energy plugins that are developed and managed through RDM. They are written to be compliant with native AFSIM core code. The offeror will be responsible for the continued development of these plugins under the direction of a government configuration control authority.
2. Are there any specific DE modeling gaps for mission-based analysis in AFSIM that
AFRL/RDM is looking to address?
a. RDM will be looking to increase the number of available models and components to support the full kill chain as listed in the SOO and call. While the focus is on the military utility of DE concepts in mission level scenarios, the front end of the kill chain (find, fix, track, and target) is also important.
3. Are there any requirements for SETA contractors and having personnel maintained on site?
a. We do not currently have SETA contractors working for us. Contractors will be expected to work in secure facilities located on Kirtland AFB as necessary for task completion.
4. Regarding the real time image generation, does this HW/SW tool already exist or will it need to be developed? What are the imaging generation requirements for matching the weather and time of day for the DE models in AFSIM? If the HW is not GFE, what are the hardware requirements?
a. Tools (HW & SW) already exist for the creation of real time image generation and updates to these will be provided through the government.
5. Does AFRL/RDM already have VMs that will be used under this effort? If so, what vehicle types will be included in the simulations?
a. RDM has a current set of VMs, but obtains new VMs, or appropriate surrogates, from other sources as necessary to model the systems and platforms in studies.
6. Does AFRL/RDM already have SHaRE weapon parameter files that will be used? If so, what systems?
a. SHaRE datasets are not the responsibility of the offeror to create. The specific systems will change depending on the requirements of the study.
7. Do weapon parameter files need to be created for specific DE systems? If so, what systems will need to be characterized? Does test or characterization data already exist for those systems or would the offeror be responsible for collecting this data?
a. Weapon parameters will be the responsibility of the concept owner to provide.
RDM is responsible for ensuring any models created in RDM are verified against the provided parameters and validating against characterization data when available. The offeror will not be responsible for collecting characterization data.
8. What volume of space do these scenarios cover? Operating ceiling? Flight box dimensions?
a. Scenarios can be multi-domain from surface to space operations. Each scenario will be tailored to location and spaces as required by the study.
9. Has a contract vehicle been selected? If so, what type?
a. IDIQ including task orders. The IDIQ has a minimum POP of 5 years, but has the potential for up to an additional 5 years for a total of 10 years.
10. Are you familiar with a UARC contract and would you be interested in pursuing this avenue?
a. Yes, AFRL is familiar with UARC contracts and several other AFRL/RD divisions are currently utilizing UARC contracts. Given the nature of the requirement and the market research conducted, a closed Call announcement under the DETER ARA was considered the most appropriate avenue.
11. Is this contract a total replacement for multiple existing contracts of similar scope?
Meant to be umbrella contract?
a. Not specifically an umbrella contract but it does build upon prior research and development that was accomplished internally by the Government as well through multiple contracts.
12. Are there incumbents for this contract? Can you tell us the other contractors working on this?
a. Incumbents are BlueHalo and Aegis Aerospace.
13. Can you provide a POC for incumbent or existing contractor PMs to support teaming discussions?
a. For propriety, the Government does not intend to release the contact information for the incumbent or existing contractors; however, contact can be made through the respective corporate offices.
14. Is there a timeline for the review process, discussions with stakeholders and/or industry day, and the competitive solicitation?
a. As stated in the Call, our preference is to award off of the white paper and SOW.
However, if needed we will do a two-step process including RFP.
15. Can you explain the process of white paper review?
a. As stated in the Call, white papers are evaluated on technical merit, relevance to
DEMU program, and affordability. These are listed in order of priority (technical merit being first priority). The ROM will be evaluated to determine if sufficient funding is available.
16. Can you clarify the conflicts between the Standard Cover Template and the content required for the cover page. In the Call it states that we should make our white papers valid for 180 days, however in the template it suggests 12 months for white papers. Also, in the Call it states that we must show the classified level that the offeror is cleared, however, there is no location for this information on the cover page. Can clarification be given?
a. For responses to Call 0007, offerors may submit the required Cover Page in a format of their choosing; however, it must clearly identify the (11) required content elements and shall not exceed one page in length. Offerors shall include a statement on the validity of the white paper submission with a minimum of 180 days. Offerors shall include the information regarding the classified level on the cover page.
17. Can you clarify the marking requirements for the SOW? We understand that if this were a proposal, we would provide a non-proprietary version, however is this also true for the SOW being provided for the white paper as it reflects our proposed technical approach?
a. The Government prefers submissions of non-proprietary SOWs for the white paper responses; however, will accept submissions of proprietary SOWs. NOTE:
The final SOW incorporated into any resulting contract/arrangement shall be non-proprietary.
File details come from the government source that posted it. Updated .