Mission-Integrated Network Control (MINC)

Background
The objective of the MINC program is to ensure that critical data finds a path to the right user at the right time in highly contested, highly dynamic communication environments using secure control of any available communication or networking resources. The MINC approach is designed to interoperate with a heterogeneous mix of legacy and future systems to ensure timely and reliable delivery of data that is not guaranteed today. This capability replaces the manual, static configuration of individual, tactical networks and the associated limited internetworking capabilities. The growing emphasis on all-domain warfare compounds the complexity of controlling heterogeneous networks. MINC embraces these challenges by introducing the mosaic warfare concepts of optionality, diversity, and rapid adaptability to the orchestration of networks of networks.

Work Details
The MINC program will realize 'on-demand' connectivity between kill web services by focusing on the development and integration of three key capabilities: 1) Creating an 'always-on' network overlay to access available networking and communications resources and control parameters; 2) Using a cross-network approach for optimizing and managing network configuration and information flows; and 3) Creating a mission-driven approach in determining the critical information flows for kill web services. The program seeks to develop an integrated system of multiple, complex technologies organized into focus areas (FAs) of research including Secure Control Overlay, Distributed Network Orchestration, and Mission Integration.

Period of Performance
MINC is a three-phase program covering 48 months. The Phase 1 (base) period of performance is 18 months, the Phase 2 option is for 12 months, and the Phase 3 option is for 12 months. An additional 6-month transition effort is planned for the end of Phase 3.

Place of Performance
The program structure incorporates workshops and Development Security Operations (DevSecOps) cycles with transition partners. Proposals should address how their research and development plan will incorporate the DevSecOps model and how that will tie into their overall system integration as part of FA 3.