Draft NGC2 Prototype Statement of Objectives (SOO).docx

Work statement – TEMPLATE

Draft Statement of Objectives

13 JANUARY 2025

PROTOTYPE STATEMENT OF OBJECTIVES (SOO)

NEXT GENERATION COMMAND AND CONTROL (NGC2)

PROJECT MANAGER NGC2

U.S. ARMY PROGRAM EXECUTIVE OFFICE COMMAND, CONTROL, COMMUNICATIONS, AND NETWORK (PEO C3N)

Controlled by: PM NGC2 CUI Category:

Limited Dissemination Control:

POC:

TABLE OF CONTENTS

Next Generation Command and Control (NGC2)

1. Project Title: Next Generation Command and Control (NGC2)

2. Introduction The purpose of this prototyping effort is the design, integration, evaluation, and delivery of a scalable prototype software framework that enables seamless Soldier C2 experience to the edge through frictionless C2 data exchange access across echelons. This design will enable vendor diversity without vendor lock and faster time to capability, including improved deployment frequency over legacy systems (see Figure 1).

Figure 1. Notional NGC2 Data-Centric Architecture

3. Background NGC2 is a fundamental change in how the US Army conducts digital mission command. The NGC2 strategy shifts the mission command ecosystem from a conglomeration of bespoke ‘vertical’ systems - focused on niche warfighting function requirements- to a mission command environment built on a foundational integrated data layer. The integrated data layer will feature data extensibility, which will enable a multitude of options for mission command applications and data visualization. Additionally, the NGC2 environment will comport to current industry standards for Agile software delivery and administration.

In September 2024, NGC2 became a program of record under the Software Acquisition Pathway (SWP). The NGC2 SWP Planning Phase includes development of acquisition, contracting, test, and resourcing strategies. These strategies will be informed by cost estimates, and trace to both existing and new requirements and programs. Based on outcomes from initial limited prototyping, the Army will build and evolve product and technology roadmaps. NGC2-related products will synchronize existing Army and Joint modernization activities and inform divestment decisions and timelines.

4. Prototype Definition and Program Objectives

NGC2 intends to provide an integrated data layer across all echelons. While the initial priority should be to ensure that data ingest, curation and visualization are being executed reliably, it is critical that the prototype data layer can add new capability or functionality (extensibility) from Corps HQ to Platoon. The initial priority for echelon development is Corps or Division, since those HQs have similar use case requirements under the performance objectives in this SOO.

Initial prototyping will focus on the secure digital environment required to develop, test, and deploy required C2 capabilities. In addition, the prototype focus is on an integrated data layer necessary to manage and share C2 data across applications to provide a common operating picture for commanders with the minimum information required to make fast, accurate decisions in every environment. The most stressing case to be considered is data layer access to cloud native capabilities at the tactical edge in disrupted, disconnected, intermittent and low-bandwidth (DDIL) environments.

Based on its market research, the Army does not believe that any one company can provide a total solution for NGC2 on its own. As a result, the Army wants industry to form teams that they believe can best answer the NGC2 problem set, with each team having a designated team leader that would be accountable to the Army for submitting the RFP response and delivering the work of the team, if selected.

One of the objectives of this prototyping activity is to assess the role of the government in the delivery of the initial NGC2 capability. The awardees will be required to provide a proposed approach for the management of GFE/GFI, capability integration configuration control, and the proposed strategy to iterate improvements over the period of performance.

5. Performance Objectives Initial prototype use cases are limited in scope because the main effort is data integration and extensibility. NGC2 prototype performance objectives include:

· Integration: The Awardee(s) shall deliver a prototype able to execute the following tasks:

· Conduct operational and tactical planning prioritizing enemy (Red) and friendly (Blue) Position Location Information (PLI) onto a standardized map tile.

· Integrate tools with the ability to graphically portray tactical planning on a map. Applications and microservices displaying operational graphics, symbology, and workflows must conform to the Army Doctrine Reference Publication (ADRP) 1-02 standard.

· Collaborative activities which can be viewed remotely by other applications.

· Ability to access a cross-platform chat service. The chat service should be accessible from both IL4 and IL6 enclaves.

· Execute fire missions using both technical and tactical firing solutions. The workflow includes target nomination, target prioritization, firing unit selection, ammunition selection and ends with technical firing data to the firing unit over at IL6.

· Deliver a logistics Common Operating Picture (COP) that initially focuses on CLS III (Fuel) and Class V (Ammunition) commodity inventory. The application should also feature a predictive resupply workflow that complements the Fire mission use cases

· Integrate with unit furnished Line of Sight and Beyond Line of Sight transport fielded from Division to Platoon.

· Application integration with unit furnished Army end user devices such as Nett Warrior (NW) and Tactical Assault Kit (TAK) to send and receive data from Division to Platoon.

· Access and display information from the Army Intelligence Data Platform (AIDP).

· Deliver a sustainment CoP to plan movement and maneuver, support operations distribution, plans, and integration and lead movement and maneuver.

· Integrate with the Army’s Tactical Data Platform.

· Integrate with coalition C2 and warfighting systems in accordance with Multi-lateral Interoperability Programme 4 Information Exchange Specifications.

· Integrate with tactical edge computing and ability to access cloud-based services from the edge of the battlefield using unit furnished end user devices.

· Integrate with Protection tasks as Air and Missile Defense, CBRN Operations, Force Health Protection, Electromagnetic Protection, Physical Security and Personnel Recovery.

· Integrate with Tactical-Identify Credential and Access Management (T-ICAM) for network defense.

· Training and Fielding: The Awardee(s) shall deliver training sufficient enough to support demonstration and prototyping activities.

· Engineering: The Awardee(s) shall deliver and operate the NGC2 prototype on a mission command environment that provides both an IL4 (NIPR) and IL6 (SIPR) enclave. The prototype should be able to execute mission command across both enclaves. The priority for prototyping is IL6. The following features, and conformance standards are critical to the operating system during the prototyping phase:

· Reference Architecture (RA)

· Open Application Programming Interfaces (API)

· Software Development Kits (SDK)

· Interoperability Standards

· Data Models/Schema

· Common Services

· Centralized data ingest and data transformation services: analytics for data correlation and normalization; comport data into a common data model for consumption at the application layer

· Identity management

· Data tagging and discoverability

· Centralized application management and oversight

During the prototyping phase, the awardee(s) will support metrics in accordance with ASA(ALT)’s Software Metrics and Management Policy dated 26 April 2024 and an assessment of the alignment of their provided RA, API, and SDK to the principles of the US Army’s published Unified Reference Data Architecture including:

· Proposed modifications and improvements to the UDRA to facilitate a successful prototype

· Proposed mission threads and experiments to guide the government on UDRA development and maturation.

6. Place of Performance Place of Performance shall be primarily at Awardee facilities; however, the Awardee shall be required to travel/perform requirements both within the Continental United States (CONUS) and Outside Continental United States (OCONUS) according to specific requirements. The Awardee(s) will be required to perform at Government facilities when required. All locations or alternate locations of performance shall be determined and identified for each task. Travel in and around the primary place of performance may be required throughout the period of performance (PoP). Anticipated places of performance include, but are not limited to:

(CONUS)

· Fort Carson, CO

· Fort Cavazos, TX

· Aberdeen Proving Ground, MD

· Other Government-designated sites as required

(OCONUS)

· Other Government-designated sites as required

7. Delivery Schedule

· Awardee(s) shall have a demonstrated capability to pull services over IL4 enclaves to enter Phase 1.

· Awardee(s) shall have a demonstrated capability to pull services over IL6 enclaves to enter Phase 2.

· Awardee(s) shall be able to successfully demonstrate the fires thread over IL6 enclaves to enter Phase 3.

· The Government intends to employ the prototype at Project Convergence Capstone 6 (PCC6), in FY26. The Government shall consider the prototype to be complete after all vulnerabilities and fixes identified via experimentation during PCC6 have been implemented.

JAN 2025

image1.jpeg image2.png image3.png image4.png