TOPIC CALL 3 Q and A.pdf

Questions Answers Q1: For each topic will there be a single award or multiple awards? A1: DTRA may award one or multiple awards.

Q2: Can a proposer submit multiple proposals on a given topic? A2: Yes

Q3: Can the government provide the estimated ceiling value for each or all of the topics?

A3: The offeror should submit what they deem appropriate for their submission to the topic(s).

Q4: When it says that "the to-be-developed capability is expected to function as microservice" is the government envisioning the capability to work as a single microservice?

A4: No, multiple microservices are anticipated to cover the breadth of capabilities required.

Q5: Is the T&D calculation part of the "to-be-developed capability" expected to run on different platforms, including Android?

A5: Yes, the solution should be flexible so that it can be adapted for multiple platforms (e.g., ARM, Linux, Windows, HTML).

Q6: Could the government provide technical documentation on CCMF software developer kit?

A6: The CCMF Services SDK provides a Java client library that facilitates the generation of fully initialized CCMF Scenario Wirings by providing users with a simplified interface to configure the JAXB input for each Component that comprises a valid CCMF Scenario. The CCMF SDK will be made available to any selected performer.

Q7: The Background mentions Nett Warrior and TAK as successful examples. Does the government require the proposed solution to work specifically with one or both of these systems or is it looking for a flexible solution that can work with alternative systems?

Could the government specify what systems it has in mind?

A7: At a minimum, the solution should work within the TAK ecosystem;

however, additional deployment platforms may be considered.

Q8: For the desired feature of “a minimal footprint and logistics requirements” for the host platform, could the government provide what specific devices (or examples) it has in mind and/or provide the specs for the size, weight, power, and logistics requirements so the proposed solution can meet the expectations?

A8: The commercially available end-user devices (e.g., smart phones, tablets) are the target platforms.

Q9: Could the government provide a list of data formats it has in mind so the proposed framework can adequately address the challenges associated with non-uniform data formats? Are there specific data formats beyond classic .JSON, .XML, .KMZ, .KML, text, .csv file formats that the government expects to see addressed in the solution?

A9: The envisioned solution is aiming to accommodate all common sensor data formats, including data available through integrated sensor architecture. The formats listed in the question are considered possible formats of data to be fused and further analyzed.

Q10: Are there any specific use cases beyond current world events or conflict areas that we should consider as part of the technology solution?

A10: Current world events serve as applicable use-cases.

Q11: Could you clarify if under topic CBI-02 the objective is to deploy decision aid capabilities (i.e., algorithms) to the edge for consumption by the Warfighter, or whether the Government desires a solution to support the bidirectional dissemination of data or information from the flagpole to the fighting hole (i.e., management of communication networks to support timely situational awareness)?

A11: Both, it is envisioned that proposed decision aid solutions can be leveraged to share information across multi-domain/echelon architectures and also have the ability to function on personal devices and in potentially disconnected environments.

Approved for Public Release

Sheet1