DRAFT SOW.pdf

STATEMENT OF WORK (SOW) TITLE: Modernizing Command and Control for Future Naval Operations

1.0 BACKGROUND

PMW 150 The Command and Control Program Office) and the Naval Information Warfare Center Pacific (NIWC PAC) provide operational and tactical command and control capabilities by integrating real-time and near real-time representations of tactical situations while including Operational Picture, targeting support, chemical-biological warnings and tactical data link support for the Navy, Marine Corps, joint and coalition warfighters. This includes programs such as Global Command and Control System – Maritime (GCCS-M), Maritime Tactical Command and Control (MTC2), Nites Next, Command and Control Processor (C2P), Link 16 Network, Link Monitoring and Management Tool (LMMT), and a variety of other systems and sub-projects.

The work proposed under this project builds upon Basic and Applied Research performed by the contractor and funded through a variety of sponsors including but not limited to Office of the Secretary of War (OSW), NAVWAR, PEO C4I, Office of Naval Research (ONR) and NIPO in cooperation with the NIWC PAC. The intent of this proposed effort will be to further mature the technologies developed under these previous research programs, increase their Technology Readiness Level (TRL) and prepare them for transition to a number of possible Programs of Record.

This is a severable effort.

1.1 SCOPE

The main objective of this effort is to modernize and align Naval Command and Control for Integrated Joint/Coaliton Fires and make it deployable to afloat and ashore sites such as the Carrier Strike Groups (CSG) to include CRUDES/DDGs and Carrier Airwing assets, Expeditionary Strike Group (ESG), Marine Corps NMESIS, Army HIMARS, Airforce assets, Coalition Forces, Tactical Fleet Command Centers (TFCC), Operational Command Post (OCP) and the Maritime Operations Centers (MOC). This effort will enhance the warfighters’ decision-making and information gathering effectiveness by integrating and taking advantage of Machine Learning/Artificial Intelligence (ML/AI) approaches. The intent is to mature / modernize the technologies, increase their Technology Readiness Level (TRL) and prepare them for transition to a number of possible Programs of Record (PoR). This effort will include providing prototype validation, research and development, software development, implementation, test and verification for advanced C2 technologies.

Specifically, this effort will provide development of software products utilizing microservices, containers, service mesh, and kubernetes previously explored under the C2X project for use in command and control environment. The development work will include the design and implementation of container-based software, research and performance characterization of C2 application functionality, Artificial Intelligence, Machine Learning, Operations Research (AI/ML/OR), capturing and validating user stories, workflows, applying cybersecurity best practices, utilizing a DEVSECOPS pipeline, and related Navy Mission Essential Tasks, and development of associated technical documentation.

Development work will include but is not limited to:

a. Development, implementation, and testing of software code for the Rapid Asset Pairing Tool (RAPT),

b. Development, implementation and testing of software code for the Warfighting Capability Tool (WarCaT).

c. Development, implementation and testing of software code for the True Numbers (TN) data environment and evolving data analytics.

d. Developing, implementation and testing of software code for the Battlespace Integrated Graphics Styler

(BIGS).

e. Development, implementation and testing of software code for the Natural-language Ontologies for battlespace Visualizations and Analytics (NOVA).

f. Developing, implementation and testing software code for the Altering Current-state to an Effective

Desired-state (ACED).

g. Development, implementation and testing of software code for the Advanced Correlator- Navy (ACOR-N).

h. Development, implementation and testing of Large Language Models (LLM) to support operational requirements for planning and execution.

i. Development, implementation, and testing of AEGIS Combat System such REAPER and the Command, Control Combat System Interface (C3SI).

j. Development, implementation, and testing of the Naval Aviation Readiness Dashboard (NARD)

k. Integration of Generative AI (GENAI)

l. Implementation, and testing into the Command and Control Experimentation (C2X) Service Mesh Architecture for all applications.

m. Implementation, and testing into the Maritime Tactical Command and Control (MTC2) application for alignment with the PoR.

n. Implementation, and testing of applications to support Coalition Partners pursuant to Foreign Disclosure Office (FDO) guidance.

o. Delivering software builds, test, and cyber scan in the C2X DEVSECOPS environment and the Overmatch Software Armory (OSA), and posting containers in the OSA Software Artifactory.

p. Development of software for processing by information systems of human originated inputs and queries providing automated machine to machine data source ingest.

q. Development of Dynamic and/or probabilistic mission execution enablers of modern tools that would decrease the time of decision making by increasing situational awareness and understanding during operations

r. Development of Human-information system interaction capabilities in distributed computing environments, including command system applications by introducing ML/AI/OR methods to interpret displays/information in the Common Operating Picture (COP) and providing ‘ALERTS’ for recommended Pre Planned Responses (PPRs) based on the Commander’s Critical Information Requirements (CCIRs), and predictive enemy courses of action (ECOAs).

s. Development of Domain dependent and independent information detection, extraction, and retrieval using Natural language Processing (NLP) methods to ingest and interpret Navy-wide and CSG messages including OPTASKS/PPRs. Application of automation to aggregate historical information into a repository for design exploration and future application. Implementation of ‘real time’ application of AI tools for Current Operations enhancing awareness and applying prototype validation to current and future operations.

t. Development of new concepts in perception and visualization for display of current and future scenarios generated in real time where Warfare Commanders (WC) have assets with weapons ‘covering’ enemy platforms.

u. Utilization of C2X DEVSECOPS environment and OSA for implementation builds, code scanning, packaging into containers and testing deployments.

v. Provide support for operational deployment of C2X, exercises and experimentation.

w. Ensuring that software developed under this effort is running correctly within the CANES representative test environments in OSA, CSE, OPE, afloat, and/or the CTB hardware in the loop lab.

2.0 APPLICABLE DOCUMENTS

DODM 5200.01, Volume 1, DoD Information Security Program: Overview, Classification, And Declassification, Ch-2 28 July 2020 DODM 5200.01, Volume 2, DoD Information Security Program: Marking Of Classified Information, Ch-4 28 July 2020 DODM 5200.01, Volume 3, DoD Information Security Program: Protection Of Classified Information, Ch- 3 28 July 2020 DODI 5200.48, Controlled Unclassified Information (CUI), 6 March 2020 DoDM 5200.02, Procedures for the DoD Personnel Security Program (PSP) dtd Ch-1 29 October 2020 DOD 5205.02-M, DOD Operations Security (OPSEC) Program,Ch-2 29 October 2020 DoDM 5220.32, Volumes 1, National Industrial Security Program: Industrial Security Procedures for Government Activities, 1 August 2018, Ch-2 10 December 2021 DoDM 5220.32, Volumes 2, National Industrial Security Program: Procedures For Government Activities Relating To Foreign Ownership, Control, Or Influence (FOCI), 17 April 2014, Ch-2 10 December 2021 DoDI 5220.22, National Industrial Security Program (NISP) 32 CFR Part 117, National Industrial Security Program, Operating Manual (NISPOM), 24 February 2021 OPNAVINST 3432.1 (Series), DON Operations Security, 4 November 2011 OPNAVINST F3300.53D (Series), Navy Antiterrorism Program, 2 August 2021 SECNAVINST 5510.30C, Department of Navy Personnel Security Program, 24 January 2020 SECNAVINST 5510.36B, DON Information Security Program, 12 July 2019 SPAWARINST 3432.1 (Series), Operations Security Policy, 2 February 2005 DoDD 5205.02E, DoD Operations Security (OPSEC) Program, 20 June 2012, Ch-2 20 August 2020 National Security Decision Directive 298 (Series), National Operations Security Program (NSDD) 298, 22

January 1988 NIWCPACINST 5500.1C Security Manual, Ch-1 25 September 2019

3.0 PERFORMANCE REQUIREMENTS

3.1 Office of the Secretary of Defense (OSD)

As reflected under the scope above, the main technical objective of this program is to modernize the Navy’s command and control capabilities to provide Joint/Coalition Integrated support for Fires. This effort will be accomplished by enhancing the warfighters’ decision automation tools and information gathering effectiveness by integrating and taking advantage of ML/AI/OR approaches.

The contractor shall perform the tasks identified below to accomplish the above objectives of this effort.

A. Requirements

A.1. The contractor shall perform the following tasks.

A.1.1. The contractor shall gather and analyze system requirements for Processing by Information Systems of Human Originated Inputs and Queries and perform implementation tailoring for Fleet Naval Forces, Fires Coordination, Maritime Operations Center (MOC) and Coalition support. This will entail automation processes provided through software widgets/component development that enables ‘real time’ updates to status, including warfare conduct, state assessment of systems and munition by type and capability remaining, and prototype validation of which assets are suitable to conduct missions. Then composing most suitable assets, using the most appropriate capability, to perform the correct task, accomplishing the best result(s) achieving the required effect and on time is the ultimate goal.

A.1.2. The contractor shall gather and analyze system requirements for Dynamic and/or Probabilistic decision automation tools. The contractor shall develop decision aids tracking, evaluating and projecting key indicators, measures of performance and effectiveness to provide a comprehensive mission state and impact assessment. This will entail developing a suite of modern tools to decrease the time of decision making by increasing situational awareness and understanding during operations.

The contractor shall develop automated, updated, comprehensive status boards, integrated with modern processing, prototype validation (Machine Learning {ML}/Artificial Intelligence {AI}) and Operations Research (OR), implementing GENAI and LLMs, coupled with data ingest methods from disparate data sources to feed the applications to build understanding of the Common Operational Picture (COP) Area of Responsibility (AoR).

A.1.3. The contractor shall gather and analyze system requirements for Human/IS Interaction in Distributed Computing Environments, including C2 system applications. The contractor shall develop ML/AI/OR methods to interpret displays/information in the COP and provide ‘ALERTS’ for recommended Pre Planned Responses (PPRs) based on the Commander’s Critical Information Requirements (CCIRs), and predictive enemy courses of action (ECOAs). The contractor shall provide methods to label data on ingest and continue to train ML/AI technologies using new automated methods.

A.1.4. The contractor shall gather and analyze system requirements for Domain Dependent and Independent Information Detection Extraction and Retrieval. The contractor shall introduce the use of Natural language Processing (NLP) methods to ingest and interpret Navy-wide and CSG OPTASKS/PPRs, automation to aggregate historical information into a repository for prototype validation and future application, and ‘real time’ application of tools for Current Operations to enhance awareness and incorporate prototype validation to current and future operations data sets to support prediction with greater accuracy.

A.1.5. The contractor shall gather and analyze system requirements for new concepts in Perception and Visualization. The contractor shall create automated widgets that track maintenance, casualties, munitions, sensors, platforms, and communication status with detailed prototype validation of risk providing a marked increase in Situational Awareness for watch standers to support decreasing time of response thereby providing greater decision advantage to warfighters.

A.1.6 the contractor shall perform Software Engineering efforts that align to existing Development- Security-Operations (DEVSECOPS) platforms and policies. The contractor shall deliver software builds, test, and cyber scan in the C2X GITLAB environment and the Overmatch Software Armory (OSA) and post containers in the OSA Software Artifactory.

A.2 Software Engineering Approach

The contractor shall define a software development approach appropriate for the computer software effort to be performed. This approach shall be documented in a Software Development Plan (SDP)(CDRL A005). The contractor shall follow this SDP for all computer software to be developed or maintained under this effort.

The SDP shall define the contractor’s proposed life cycle model and the processes used as a part of that model. In this context, the term “life cycle model” is defined in IEEE/EIA Std. 12207.0. The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of the solicitation. In accordance with the framework defined in IEEE/EIA Std. 12207.0, the SDP shall define the processes, the activities to be performed as a part of the processes which support the activities, and the techniques and tools to be used to perform the tasks.

Because IEE/EIA Std. 12207 does not prescribe how to accomplish the task, the contractor must provide this detailed information so the Government can assess whether the contractor’s approach is viable.

The SDP shall contain the information defined by IEEE/EIA Std 12207.1, section 5.2.1 (generic content) and the Plans or Procedures in Table 1 of the IEEE/EIA Std. 12207.1. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include, as a minimum, specific standard, methods, tools, actions, strategies, and responsibilities associated with development and qualifications.

3.2 NAVWAR (PMW 150)

B. Requirements:

3.2.1 NAVWAR PMW 150 is another sponsor that intends to contribute funds toward the effort and ultimate goals identified under paragraph 3.1 above for all periods of performance.

3.3 Navy International Program Office (NIPO)

NIPO is another sponsor that intends to contribute funds toward specific portions of the contractor effort and ultimate goals identified under paragraph 3.1 above for all periods. The specific portions that NIPO intends to contribute funds toward are identified below.

C. Requirements

C.1. Contractor base period tasks:

C.1.1. Tasking / goals identified under A.1.1. C.1.2. Abbreviated tasking/goals identified under A.1.3 as follows: The contractor shall gather and analyze system requirements for Human/IS Interaction in Distributed Computing Environments, including Coalition for C2 system applications.

C.1.3 Similar to A.1.5 as follows: The contractor shall gather and analyze system requirements for new concepts in Perception and Visualization based on Coalition data sets. The contractor shall create automated widgets that track maintenance, casualties, munitions, sensors, platforms, and communication status with detailed prototype validation of risk providing a marked increase in Situational Awareness for watch standers to support decreasing time of response thereby providing greater decision advantage to warfighters.

C.1.4 Tasking / goals identified under A.1.6.

C.2. The contractor shall perform the following tasks during option period 1 as defined in the base period of performance.

C.3. The contractor shall perform the following tasks during option period 2 as defined in the base period

C.4. The contractor shall perform the following tasks during option period 3 as defined in the base period

C.5 The contractor shall perform the following tasks during option period 4 as defined in the base period

C.6 Software Engineering Approach identified under A.6.

3.4 NAVWAR (Overmatch)

D. Requirements:

NAVWAR is another sponsor that intends to contribute funds toward the effort and ultimate goals identified under paragraph 3.1 above for all periods.

3.5 Office of Naval Research (ONR)

E. Requirements:

E.1 Develop software capabilities as defined in the scope of work being done and perform Software Engineering efforts that align to existing Development-Security-Operations (DEVSECOPS) platforms and policies. The contractor shall deliver software builds, test, and cyber scan in the C2X GITLAB environment or other designated DEVSECOPS environment, the Overmatch Software Armory (OSA), and post containers in the OSA Software Artifactory.

E.2 Integrate developed capabilities with the Maritime Tactical C2 (MTC2) Program of Record (PoR) to demonstrate interoperability with a CSG planning tool, E.3 The minimum viable product (MVP) requirements include developing and containerizing capabilities and maturing the product for transition to the PoR. Containerized capabilities will need to be aligned to the CANES technology stack. A SOP procedure that moves code from the operational prototype to a productionized container will be aligned with the PMW150 S&T Facility and the Overmatch OSA environment.

4.0 ESTIMATED LONG DISTANCE TRAVEL (in support of above tasking / goals) It is anticipated that the travel will originate from the contractor facility in Buffalo NY

Place No of Personnel No of Days No of Trips

Base Period:

San Diego 2 5 4

San Diego 3 5 4

Option 1:

San Diego 2 5 4

San Diego 3 5 4

Option 2:

San Diego 2 5 4

San Diego 3 5 4

Option 3:

San Diego 2 5 4

San Diego 3 5 4

Option 4:

San Diego 2 5 4

San Diego 3 5 4

Travel costs related to transportation, lodging, meals, and incidental expenses are allowable subject to the limitations described at FAR 31.205-46.

Contractor personnel must adhere to all current DoD, SECNAV, OPNAV, and NIWC Pacific instructions related to foreign travel (if foreign travel is anticipated).

In the course of performance, travel in addition to that estimated above may be required to support the scope/tasking/goals in this SOW. If additional travel is necessary, the contractor shall comply with relevant SOW addendum text(s) and clauses for domestic or foreign travel.

5.0 PROPERTY REQUIREMENTS

• Government Furnished Property (GFP): None anticipated

• Government Furnished Information (GFI): None anticipated. See applicable documents section for relevant Government information.

• Government Property (incidental): None anticipated.

• Government Furnished Facilities: None anticipated.

• Contractor Acquired Property: None anticipated.

6.0 SECURITY

The security requirement for this tasking will be up to and including TOP SECRET. Most technical personnel performing on this task must be cleared to the SECRET level with the exception of select personnel performing tasks for paragraph 3.1, 3.2, 3.4, 3.5 who will need to be cleared at the TOP SECRET level. The work performed by the contractor will include access to unclassified and up to TOP SECRET data, information, and spaces. The contractor will be required to attend meetings classified up to TOP SECRET level. The contractor will be required to access TOP SECRET COMSEC, and SIPRNET at Government locations.

Contractors performing tasks up to the TS level shall only receive the North Atlantic Treaty Organization (NATO) awareness brief and complete the derivative classification training prior to being granted access to SIPRnet; training is provided by the facility security officer. Specific requirements provided in the Department of Defense Contract Security Classification Specification, DD Form 254.

The National Industrial Security Program Operating Manual (NISPOM) 32 CFR NISPOM Rule 117.8 implements contractor reporting requirements per SEAD 3. Contractors are required to report certain events such as those that have an impact on:: 1) the status of the facility clearance (FCL), 2) the status of an employee's personnel clearance (PCL);

may indicate the employee poses an insider threat the proper, 3) the proper safeguarding of classified information, and

4) or an indication that classified information has been lost or compromised. Contractors working under NIWC Pacific contracts will ensure information pertaining to assigned contractor personnel are reported to the Contracting Officer Representative (COR)/Technical Point of Contact (TPOC), the Contracting Specialist, and the Security's COR in addition to notifying appropriate agencies such as Cognizant Security Agency (CSA), Cognizant Security Office (CSO), or Department Of Defense Central Adjudication Facility (DODCAF) when that information relates to the denial, suspension, or revocation of a security clearance of any assigned personnel; any adverse information on an assigned employee's continued suitability for continued access to classified access; any instance of loss or compromise, or suspected loss or compromise, of classified information; actual, probable or possible espionage, sabotage, or subversive information; or any other circumstances of a security nature that would affect the contractor's operation while working under NIWC Pacific contracts.

Anti-Terrorism/force Protection (AT/FP) briefings are required to be completed annually for all personnel (military, DOD civilian, and contractor). The briefing is available at Joint Knowledge Online (JKO): https://jkodirect.jten.mil (prefix): JS; course number: US007; title: Level 1 Anti-terrorism awareness training, if experiencing problems accessing this website contact the JKO Help Desk (24 hours a day/7 days a week, jkohelpdesk@jten.mil, 757-203- 5654). This training can also be found on the Total Workforce Management Services (TWMS) site:

https://twms.navy.mil/selfservice. The website will allow contractors who do not have a CAC to access the training.

note: per OPNAVINST F3300.53D contractor employees must receive the AT/FP briefing annually.

6.1 Operations Security (OPSEC). OPSEC is a five step analytical process (identify critical information; analyze the threat; analyze vulnerabilities; assess risk; develop countermeasures) that is used as a means to identify, control, and protect unclassified and unclassified sensitive information associated with U.S. national security related programs and activities. All personnel working under this task will at some time handle, produce or process Critical Information or Critical Program Information, and therefore all Contractor personnel must practice OPSEC. All work is to be performed in accordance with DoD OPSEC requirements, and in accordance with the OPSEC attachment to the DD254.

6.2.1 Operations Security (OPSEC) Requirements

Security programs are oriented towards protection of classified information and material. Operations Security (OPSEC) is an operations function, which involves the protection of any critical information – focusing on unclassified information that may be susceptible to adversary exploitation. Pursuant to DoDD 5205.02E SECNAVINST 3070.2A, and NAVWARINST 3432.1, NAVWAR/NIWC Atlantic/NIWC Pacific’s OPSEC program implements requirements in DoD 5205.02-M – OPSEC Program Manual. Note: OPSEC requirements are applicable when contract personnel have access to classified information, unclassified Critical Program Information (CPI), Controlled Unclassified Information (CUI) or Department of Navy (DoN) networks.

6.2.2 Local and Internal OPSEC Requirement

Contractor personnel, including subcontractors if applicable, shall adhere to the OPSEC program policies and practices as cited in the NAVWARINST 3432.1 and existing local site OPSEC procedures. The Contractor shall development their own internal OPSEC program specific to the contract and based on NAVWAR/NIWC Atlantic/NIWC Pacific https://jkodirect.jten.mil/ mailto:jkohelpdesk@jten.mil https://twms.navy.mil/selfservice

OPSEC requirements. The Contractor’s program shall identify the current contractor site OPSEC Officer/Coordinator/POC.

6.2.3 OPSEC Training

Contractor shall track and ensure applicable personnel receive initial and annual OPSEC awareness training. Training may be provided by the government or by the contractor’s OPSEC Manager. Contractor training shall include, at a minimum, cover OPSEC as it relates to contract work; discuss the Critical Information applicable in the contract;

applicable review of government Critical Information and Indicators List(s) (CIIL); social media awareness and vulnerabilities; local threats; how to protect, transmit, and destroy controlled unclassified information; risks and guidance pertaining to geolocation-capable devices, applications, and services; and OPSEC review procedures for public release. The Contractor shall ensure that training materials developed by the Contractor shall be reviewed by the NAVWAR/NIWC Atlantic/NIWC Pacific OPSEC Officer, who will ensure it is consistent with NAVWAR/NIWC Atlantic/NIWC Pacific OPSEC policies. OPSEC training requirements are applicable for personnel during their entire term supporting NAVWAR/NIWC Atlantic/NIWC Pacific contracts and for the duration of DoN network access.

6.2.4 NAVWAR/NIWC Atlantic/NIWC Pacific OPSEC Program

If required, the Contractor shall participate in NAVWAR/NIWC Atlantic/NIWC Pacific OPSEC program briefings and working meetings, and complete any required OPSEC survey or data call within the timeframe specified.

6.3 Information Security

Pursuant to DoDM 5200.01 and DoDI 5200.48, the contractor shall provide adequate security for all CUI and Unclassified DoD information passing through non-DoD information system including all subcontractor information systems utilized on contract. If the contractor originates, adds to, or changes any of the DoD information, it must be marked in accordance with DODI 5200.48 and handled properly. The contractor shall disseminate CUI and unclassified DoD information within the scope of assigned duties and with a clear expectation that confidentiality is preserved. Examples of such information include the following: non-public information provided to the contractor, information developed during the course of the contract, and privileged contract information (e.g., program schedules, contract-related tracking).

6.4 Contractor Requirements for Intelligence Oversight

In compliance with DoDD 5148.13 paragraph 4.1.e and SECNAVINST 3820.3F, all contractor personnel conducting Intelligence or Intelligence-related activities or supporting those efforts under Department of Defense authorities shall report any Questionable Intelligence Activity (QIA) or Significant or Highly Sensitive Matter (S/HSM) to the Naval Information Warfare Systems Command Intelligence Oversight Program Manager or Senior Intelligence Officer.

6.4.1 Questionable Intelligence Activity (QIA): Any Intelligence or Intelligence-related activity when there is reason to believe such activity may be unlawful or contrary to an Executive Order, Presidential Directive, Intelligence Community Directive, or applicable DoD policy governing that activity.

6.4.2 Significant or Highly Sensitive Matter (S/HSM): An Intelligence or Intelligence-related activity (regardless of whether the Intelligence or Intelligence-related activity is unlawful or contrary to an Executive Order, Presidential Directive, Intelligence Community Directive, or DoD policy), or serious criminal activity by Intelligence personnel, that could impugn the reputation or integrity of the Intelligence Community, or otherwise call into question the propriety of Intelligence activities. Such matters might involve actual or potential:

- Congressional inquiries or investigations.

- Adverse media coverage.

- Impact on foreign relations or foreign partners.

- Systemic compromise, loss, or unauthorized disclosure of protected information.

7.0 DELIVERABLES

The contractor shall provide data deliverables in accordance with (IAW) the Contract Data Requirements List (CDRL). The contractor shall deliver any source code developed, along with end-user documentation IAW CDRL, as applicable. The contractor shall establish a practical and cost-effective system for developing and tracking the required CDRLs generated under each task. The contractor shall not develop any CDRL classified TOP SECRET with SCI.

8.0 PERFORMANCE CRITERIA

Not applicable.