RFI Data Distribution Replication and Restoration Question_Answers 112019.pdf

REQUEST FOR INFORMATION on Data Distribution, Replication and Restoration Q & A

1. What is the intended typical and maximum distance between Command Post nodes?

This is an operational parameter that will change based on mission type. Command Posts nodes could be located 1KM+ apart.

2. How many nodes might compose a Command Post: less than 10, dozens, hundreds, etc.?

Could change based on operations but typically will be no more than 8. That includes the equivalent of a Main and TAC

3. Is Wi-Fi technology the only wireless network technology being considered herein?

Not the only one considered, but the transport may change but Wi-Fi 2.4GHz is the lowest denominator.

4. Does the vision for the replication aspects of this system include the entirety of Command Post data at all of the distributed node locations (for complete redundancy) or a subset of data at the various distributed node locations that will be aggregated intelligently when required such as in Continuity of Operations (COOP) situations?

We anticipate replication of a subset, however the ability to replicate all nodes could add value. A threshold of 3 nodes but doctrine has not been established so must assume replications to more than 3.

5. Is the envisioned goal the ability to quickly move a Command Post while maintaining a limited set of services on the move? Then quickly being able to reform and resync the Command Post at the halt? Or is the vision to push services further down the echelons toward the company to provide a more distributed service architecture?

We are not envisioning pushing services to lower echelons. The focus is not on the move, the focus is survivability. This could change at later date if transport mechanisms improve that allows for the exchange of data while on the move.

6. As an alternative to the use case posed in Question #5, is the envisioned goal perhaps more kinetic in nature? Is the envisioned goal to disaggregate the Command Post and add mobility to its sub-components, thereby providing protection against loss of all Command Post data as a result of a single kinetic encounter?

At this stage mobility is not an objective, but dispersing the command post and having COOP is the primary objective.

7. Is the Government open to solutions other than a COTS solution to answer this requirement?

At current stage the government is looking for commercial products that can be integrated into the Command Post, unless a GOTS equivalent already exists.

8. Is there an incumbent for this work? If yes, who is the incumbent?

No

9. If this RFI results in a solicitation, what would be the anticipated solicitation timeline and subsequent period of performance?

This RFI is for Market Research only and will not result in a solicitation or contract per RFI paragraph one, “This is a sources sought announcement only. There is no solicitation available at this time. Requests for a solicitation will not receive a response.”

10. If this RFI results in a solicitation, what criteria would be used for the evaluation process?

This RFI is for Market Research only and will not result in a solicitation or contract per RFI

11. If this RFI results in a solicitation, what would be the primary place of performance?

This RFI is for Market Research only and will not result in a solicitation or contract per RFI

12. With regard to Data Distribution, Replication and Restoration RFI W56KGU-20-R-DDRR, can you provide what OS, Database, and applications are required to meet the stated requirements?

The components of CPCE: Wildfly Application Server, SQL Server, Static map binary data.

Hypervisor today is VMWare ESXi and Vcenter running VSAN as the virtual data, but are open to other solutions.