N6893624R0005 Amendment 0001.docx

N6893624R0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 12-Aug-2024 11:00 AM to 22-Aug-2024 11:00 AM.

The following have been modified:

The following addresses and points of contact are provided:

Contract Specialist:

Name: Aretha Jones Phone: 760-793-3747 Email address: aretha.y.jones.civ@us.navy.mil

U.S. Postal Service Mailing Address:

COMMANDER

CODE D223000 (Aretha Jones)

NAVAIRWARCENWPNDIV

1 ADMINISTRATION CIRCLE, STOP 1303

CHINA LAKE, CA 93555-6108

Direct Delivery Address (UPS, FedEx, etc.):

COMMANDER

CODE D223000 (Aretha Jones)

NAVAIRWARCENWPNDIV

BLDG 02334, STOP 1303

CHINA LAKE, CA 93555-6108

Team Lead:

Name: Brad Watson Phone: (760) 977-2163 Email address: john.b.watson1.civ@us.navy.mil

U.S. Postal Service Mailing Address:

COMMANDER

CODE D223000 (Brad Watson)

NAVAIRWARCENWPNDIV

1 ADMINISTRATION CIRCLE, STOP 1303

CHINA LAKE, CA 93555-6108

Direct Delivery Address (UPS, FedEx, etc.):

COMMANDER

CODE D223000 (Brad Watson)

NAVAIRWARCENWPNDIV

BLDG 02334, STOP 1303

CHINA LAKE, CA 93555-6108

Contracting Officer:

Name: Bryan Gregory Phone: (760) 793-4313 Email address: bryan.v.gregory2.civ@us.navy.mil U.S. Postal Service Mailing Address:

COMMANDER

CODE D220000 (Bryan Gregory)

NAVAIRWARCENWPNDIV

1 ADMINISTRATION CIRCLE, STOP 1303

CHINA LAKE, CA 93555-6108

Direct Delivery Address (UPS, FedEx, etc.):

COMMANDER

CODE D220000 (Bryan Gregory)

NAVAIRWARCENWPNDIV

BLDG 02334, STOP 1303

CHINA LAKE, CA 93555-6108

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

STATEMENT OF WORK

STATEMENT OF WORK

Development and Fielding of Intelligence, Surveillance, Reconnaissance and Targeting (ISR&T) Systems December 11, 2023

INTRODUCTION

1.0 BACKGROUND

The Mission Engineering and Analysis (ME&A) Department (D580000) of the Naval Air Systems Command (NAVAIR), Naval Air Warfare Center Weapons Division (NAWCWD) supports Department of Defense (DoD) and Intelligence Community (IC) Agencies and Programs by providing Research, Development, Testing and Evaluation (RDT&E) technical assistance to current/future Intelligence, Surveillance, Reconnaissance, and Targeting (ISR&T) systems.

The range of Department ISR&T assistance extends from Analysis of Alternatives (AoA) evaluation and initial engineering design, through operational deployment of systems which is provided in context to enabling the development and employment of current/emerging Navy/Joint all domain warfare weapon systems. The Department serves as a focal point for defining system requirements, system design and integration plans, prototype systems development, and Testing and Evaluation for Programs and/or Agencies that field systems or components that support or derive ISR&T products.

2.0 SCOPE

The context of ISR&T DoD and IC sponsored RDT&E efforts focus on Joint All Domain Warfare Operations as aligned to the Joint All Domain Command Control (JADC2) vision. Primary emphasis is placed on Joint/Navy War at Sea (JWAS) Distributed Maritime Operations (DMO) offensive Over the Horizon (OTH) Information Warfare (IW), maritime Anti-Surface Warfare (ASuW) and land Strike Warfare (STW) deliberate & dynamic targeting operations involving National & Theater Overhead Intelligence, Surveillance, and Reconnaissance (ISR) and long-range weapon systems. Secondary emphasis is placed on Tactical/Organic Intelligence, Surveillance, and ISR, direct targeting operations and other Warfare Areas (e.g. Air Warfare, Anti-Submarine Warfare, Mine Warfare, Air & Missile Defense).

ISR&T efforts focus on enabling multi-echelon “Intel & Ops” Integrated Kill Chain operations working across DoD, IC and Special Access multi-level security operations. This involves the synchronization of Intelligence Tasking Collection, Processing, Exploitation Dissemination (TCPED) with Operations Command, Control, Communications, Computers, Intelligence (C4I) platform-weapon Operations Find, Fix, Track, Target, Engage, Assess (F2T2EA) engagement cycles. This includes ISR&T systems encompassing Imagery, Signals, Electronic, Communications, Measurement & Signals, Human, Moving, Full Motion Video, Open-Source Intelligence (IMINT, SIGINT, ELINT, COMINT, MASINT, HUMINT, MOVINT, FMV, OS) or other capabilities. This further includes Operational & Tactical Level of War (OLW-TLW) Command, Control, Communications, and Computers, Intelligence, Surveillance, Reconnaissance (C4ISR) Battle Management Aids (BMAs) for Combined Effects based targeting Course of Action (COA) decision-making in the planning and execution of mixed: air-surface-subsurface launched homogeneous & heterogeneous, kinetic & non/kinetic, cooperative & collaborative, autonomous & semi/autonomous, subsonic-supersonic-hypersonic and, standard & Net Enabled Weapons (NEWs).

ISR&T efforts also focus on advanced 6.2 Applied Research, for task research & development, 6.3 - Advanced Technology Development for science & technology task work to varied Technology Readiness Levels (TRL) as well as the 6.4 - Advanced Component Development & Prototypes for transition tasking of resultant technology enabled capabilities. Emphasis is further placed on:

a. modern highly software intensive Modular Open Systems Architecture (MOSA),

b. enhanced automation through the application of Artificial Intelligence and Machine Learning (AI/ML) technologies (e.g. Deep Learning Neural Networks, Expert Systems, Text Analytics, Decision Management),

c. machine to Machine (M2M) automation across highly geographically distributed multiple levels of security contested operating environments,

d. distributed forward deployed and reach-back processing configurations operating across multiple command echelon levels (e.g. web-enabled, cloud-based, standalone, platform embedded, mobile devices) and,

e. incorporation of Government off the Shelf (GOTS), Commercial Off the Shelf (COTS) or mixed Mostly off the Shelf (MOTS) components.

The ISR&T also encompasses the continuation and expansion on previous and ongoing support of the Surface Target Attack Monitor (STAM) Quick Reaction Capability (QRC), Dynamic INtegrated Operations (DINO) FNC, and Rapid Adaptive Planning Time Sensitive Targeting Offensive Responsive Strike (RAPTORS), FNC Targeting Support segment advanced prototypes transition to the Maritime Tactical Command Control (MTC2) and Distributed Common Ground Station (DCGS-N) Program of Record (PoR). Other ongoing support includes iSpy/CGSWeb software web services, Airborne ISR&T Video Targeting System (NVTS), Mobile Warfighter Tactical Assault Kit Portable Reference Imagery Mensuration Engine (PRIME), F/A-18 Digital Point Positioning Database Operational Area Planner (DAOP), Joint Standoff Weapon Autonomous Acquisition System Web Service (ATAWS), and Portable Geospatial Library (PGPL) Geospatial Database Management System (GDMS).

The ISR&T Statement of Work (SOW) tasks described further herein encompass any or all of the following major task elements: a) Concept Development, b) Concept Prototyping, c) Test & Evaluation, d) Fleet Experimentation, f) Transition Assistance and, and g) Fleet Liaison Assistance.

2.1 APPLICABLE REGULATIONS

Applicable documents and technical material (i.e., requirements documents, reference texts, specific design requirements, and other references) are defined below.

2.1.1 Department of Defense Specifications

2.1.1.2 32 CFR part 117, National Industrial Security Program Operating Manual (NISPOM), February 24, 2021

2.1.1.3 SECNAVINST 5510.36B, Department of the Navy Information Security Program, July 12, 2019

2.1.1.4 DoDI 5200.48 Controlled Unclassified Information (CUI), March 06, 2020

2.1.1.5 DoDD 5400.07, Freedom of Information Act (FOIA) Program, April 05, 2019

2.1.1.6 DoDI 5230.24, Distribution Statements on DoD Technical Information, January 10, 2023

2.1.1.7 SECNAVINST 5510.30C, Department of the Navy Personnel Security Program, January 24, 2020

2.1.1.8 OPNAVINST 3440.17A, Navy Installation Emergency Management Program, August 01, 2014

2.1.1.9 CJCSI 6212.01F, “Interoperability and Supportability of Information Technology and National Security Systems,” March 21, 2012

2.1.1.10 Director of Central Intelligence (DCI) Directive 6/3, “Protecting Sensitive Compartmented Information within Information Systems,” June 5, 1999

2.1.1.11 DODI 8523.01, “Communications Security (COMSEC), January 06, 2021

2.1.1.12 DoDD 5230.11, Disclosure of Classified Military Information to Foreign Governments and International Organizations, November 07, 2023

2.1.1.13 DoDI 8510.01, Risk Management Framework for DoD Systems, July 19, 2022

2.2 Department of Defense Standards

2.2.1 Compendium of Controlled Extensions (CE) for the National Imagery Transmission Format (NITF) Version 2.2,1 STDI0002

2.2.2 National Imagery Transmission Format Version 2.0 for the National Imagery Transmission Format Standard (MIL-STD-2500A) through Notice 3

2.2.3 National Imagery Transmission Format Version 2.1 for the National Imagery Transmission Format Standard (MIL-STD-2500B) through Notice 2

2.3 Additional Government Documents

2.3.1 AFDCGS-03-004, Rev 13, Air Force Distributed Common Ground System (AF DCGS) Block 10.2 Air Force Multi-INT Technical Requirements Document, October 10, 2006.

2.4 Related Programs Reference Documentation

2.4.1 CGS Technical Requirements Document (TRD) (updated July 31, 2007) provided by the Government within the posting

2.4.2 CGS v2.3 Software Requirements and Design Document (SRDD), January 24, 2008 provided by the Government within the posting

2.4.3 CGS v2.3 Interface Control Document (ICD), 24 January 08 provided by the Government within the posting

2.4.4 CGS Software Version Description Document (SVDD), Version 2.1.18 June 24, 2022 provided by the Government within the posting

2.4.5 CGSv2.3 Software User’s Manual (SUM), January 31, 2008 provided by the Government within the posting

2.4.6 Community Sensor Model Working Group (CSMWG) Requirements 3.0, 2010-11-15

2.4.7 Deputy Assistant Secretary of the Navy Research Development and Acquisition (DASN/RDA) Implementation of the Surface Track Data Content Standard, April 15, 2021

2.4.8 OPNAV/N9WD NAVPLAN Integration Framework (NIF) latest revisions

2.4.9 ONR Code 352 Dynamic Integrated Operations, Rapid Adaptive Planning Time Sensitive Targeting Offensive Responsive Strike (RAPTORS) and Cross Bow Future Naval Capabilities Technology Development Plans, latest revisions.

2.4.10 ONRG Fleet Experiments Technology Innovation Game (TIG) Process, May 2019

2.4.11 Institute of Electrical and Electronic Engineers (IEEE) 12207 Systems and software engineering Software life cycle processes, latest revision

2.4.12 Navy Overmatch Software Armory (OSA) and Continuous Integration Continuous Development (CICD) pipeline processes and tools, latest revisions

2.5 Information Technology Related Clauses for Statement of Work

2.5.1 Clinger-Cohen Act

a. DoDD 5000.01, The Defense Acquisition System, September 9, 2020

b. DoDI 5000.02, Operation of the Adaptive Acquisition “Framework“23 Jan 2020

c. OSD Memo, “Clinger-Cohen Act Compliance Policy,” July 13, 2010

d. SECNAVINST 5000.2E, “Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System,” September 1, 2011

2.5.2 Web Sites, Web Enablement and Application System Development

a. OMB Management of Federal Information Resources, OMB CIRCULAR NO. A-130 Revised, https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/circulars/A130/a130revised.pdf

b. OMB Policies for Federal Agency Public Websites, OMB M-05-04, https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05-04.pdf

c. Section 508, Rehabilitation Act of 1973, https://www.section508.gov/

d. DoD Web Policies and Guidelines, https://dodcio.defense.gov/DoD-Web-Policy/

e. US Navy CIO Website, DON Web Presence Policy: The Registration, Compliance of, and Investment in, All Unclassified Web Sites and Uniform Resource Locators, https://www.doncio.navy.mil/ContentView.aspx?id=577

2.5.3 Information Assurance (IA) Policies

a. ASD (NII) Directive-Type Memorandum (DTM) 08-027 – Security of Unclassified DoD Information on Non-DoD Information Systems, September 1, 2011

b. (Chairman of the Joint Chiefs of Staff Instruction) CJCSI 3170.01H (series), “Joint Capabilities Integration and Development System”, August 31, 2018

c. CJCSI 6211.02D (series) – “Defense Information System Network (DISN) Responsibilities,” August 4, 2015

d. CJCSI 5123.01G (series) – “Net Ready Key Performance Parameter (NR KPP),” 12 February 2015

e. CJCSI 6510.01F, “Information Assurance (IA) and Support Computer Network Defense (CND),” February 9, 2011

f. (Chairman of the Joint Chiefs of Staff Manual) CJCSM 6510.01B – “Cyber Incident Handling Program”, July 10, 2012

g. Defense Acquisition Guidebook (DAG)– Chapter 6 “Information Technology, and Business Systems,”; Section 2.2 “DoD Information Technology (IT) Acquisition”

h. DoD 8570.01-M, “Information Assurance Workforce Improvement Program”, December19, 2005 (Incorporating Change 2, February 25, 2010)

i. DoDD 8000.01 “Management of the Department of Defense Information Enterprise,” March 17, 2016

j. DoDD 8100.02, “Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG), April 14, 2004, Certified Current as of April 23, 2007

k. DoDI 8500.01, Cybersecurity, March 14, 2014

l. DoDD 8140.01, Cyberspace Workforce Management, October 5, 2020

m. DoDI 8330.01, “Interoperability of Information Technology (IT). Including National Security Systems (NSS),” September 27, 2022

n. DoDI 8510.01, “Risk Management Framework (RMF) for DoD Systems, July 19, 2022

o. DoDI 8520.02, “Public Key Infrastructure (PKI) and Public Key (PK) Enabling, May 18, 2023

p. DoDI 8551.01, “Ports, Protocols, and Services Management (PPSM),” May 31, 2023

q. DoDI 8580.1, “Information Assurance (IA) in the Defense Acquisition System,” July 9, 2004

s. DON CIO Memo 02-10, “Department of the Navy Chief Information Officer Memorandum 02-10 Information Assurance Policy Update for Platform Information Technology,” April 26, 2010

t. Committee on National Security Systems (CNSS) Policy No. 11, National Policy Governing the Acquisition of Information Assurance (IA) and IA-Enabled Information Technology Products

u. (Office of the Chief of Naval Operations) OPNAV INST 5239.1D, “U.S. Navy Cybersecurity Program,” July 18, 2018

v. SECNAV M-5239.1, “Department of the Navy Information Assurance Manual,” November 1, 2005

w. SECNAVINST 5230.15, “Information Management/Information Technology Policy for Fielding of Commercial Off the Shelf Software,” April 10, 2009

x. SECNAVINST 5239.3C, “Department of the Navy Cybersecurity Policy,” May 2, 2016

y. SECNAVINST 5239.19A, “Department of the Navy Computer Network Incident Response and Reporting Requirements,” September 4, 2019

3.0 REQUIREMENTS

The Contactor shall deliver ISR&T prototypes and technical assistance, components, modules, software, and systems through the performance of task orders. Specific activities to be performed as described in the following paragraphs.

3.1 Progress Status Reporting

The Contractor shall prepare and provide progress status reports in Contractor format on a monthly basis for each Delivery Order:

3.1.1 Monthly Progress Report

The contractor shall establish and maintain a management system for controlling cost, schedule, and performance using such tools as work breakdown structure (WBS), project scheduling software (e.g., Microsoft Project), briefing tools, cost performance reports, and/or others, as appropriate. The contractor shall provide Monthly Progress Reports for each Task Order, outlining work accomplished, problems encountered, problems solved, trip report(s), items delivered, and current schedule. Additional reporting items may be specified in Task Order requirements. Project Management efforts and project status will be summarized in monthly reports. (CDRL A001)

3.1.2 Monthly Task Order Expense Status Report

The contractor shall prepare and submit a monthly Task Order Expense Status Report reflecting Task Order status relative to expense of dollars and labor hours. The Report shall reflect the contractor’s “best estimates” of actual dollars and labor hours expended through the end of the previous month, and projections of monthly “burn rate,” “stop work” date, and variances from expected expense plan. (CDRL A002)

3.1.3 Task Order and Contract Summary Report

The contractor shall prepare and submit a monthly Task Order and Contract Summary Report. The Report shall provide financial and labor hour’s data for each Task Order and contract cumulative. (CDRL A001)

3.1.4 Contract Direct Labor Expenditure Report

The contractor shall submit a Contract Direct Labor Expenditure Report identifying the percentage of direct labor dollars expended by the Prime and Subcontractors. (CDRL A002)

3.1.5 Average Labor Cost Hourly Rate Report

The contractor shall submit an Average Labor Cost Hourly Rate Report documenting the current unburdened direct labor rates for Government use in estimating future costs. (CDRL A002)

3.2 Progress Status Reviews

The Contractor prepare and conduct Program Status Reviews (PSRs) with the Government. These reviews shall provide status and assess the following: a) technical progress, b) execution performance, c) risk and dependencies, d) Government/Contractor furnished property status, e) process improvement and, f) action items. The status reviews shall be held on a nominally Quarterly periodic basis as follows:

3.2.1 Kick-Off Review

The Contractor shall prepare within ten (10) days after authorization to proceed, the Contractor’s understanding of the tasks, technical approach, execution plan, deliverables, and metrics plus highlight initial views of system/software architecture updates.

3.2.2 Interim Reviews

The Contractor shall prepare and conduct interim PSRs on a quarterly basis to gauge execution progress performance and initial results with an object to align with major program Task phases or milestones.

3.2.3 Close-Out Review

The Contractor shall prepare and conduct at the end of the program a PSR to highlight program results against objectives to include any changes from the original plan, identify the status of all deliverables, and provide a program funding status history and review capability way forward transition recommendations.

The Contractor shall deliver PSR presentation material to the Government within thirty (30) days after conduct. (CDRL A004, A00D).

3.3 Performance Management and Controls

The Contractor shall implement the following project execution cost, schedule and technical performance management practices and processes constructs as applicable/tailored by individual Delivery Orders:

3.3.1 Management Tools

The Contractor shall implement tools for managing cost, schedule and technical performance. This includes Work Breakdown Structure (WBS), project scheduling, briefings, cost (labor, travel, expense) performance tracking or others tools as appropriate.

3.3.2 Integrated Master Schedule

The Contractor shall prepare and maintain and Integrated Master Schedule (IMS). The IMS shall be first prepared for the PSR Kick-Off based on the Contractor’s proposal and WBS and updated for subsequent PSRs. (CDRL A003, A00D)

3.3.3 Collaborative Sharing

The Contractor shall work implement Government compliant secure collaborative information sharing mechanisms (e.g. Encryption, SAFE, Inteldocs) for program performance management and technical task activities.

3.3.4 Exchange Meetings

The Contractor shall support preparation and participation in Contractor or Government initiated Technical Interchange Meetings (TEMs) and Working Groups (WGs) as applicable, either in-person or via teleconference to address needed areas of technical focus.

3.3.5 Stand-up Coordination Forums

The Contractor shall host and conduct periodic (e.g. weekly or bi-weekly) teleconference standup forums with Government partners to coordinate program task activities, schedules, events, prioritized action item tracking and deliverables.

3.3.6 Model Based Systems Engineering

The Contractor shall implement Model Based Systems Engineering (MBSE) DoD community of interest methods, standards, processes and tools. This shall include Unified Architecture Framework (UAF) aligned to support development of Department of Defense Architecture Framework (DoDAF) processes and artifacts. The Contractor shall establish and maintain an Integrated Modeling Environment (IME) aligned to the evolving Naval Operational Architecture (NOA) collaborative Systems Commands (X-SYSCOM) community of interest MBSE models, standards, processes, languages and tools (e.g. Systems Modeling Language, MagicDraw based Cameo Systems Modeler Environment). The Contactor IME approach shall be configured to support Government-Contractor collaboration across CUI, Secret and TS/SCI security level enclaves.

3.3.7 System/Software Development

The Contractor shall implement industry recognized systems/software engineering processes (e.g. IEEE 12207 standard) and modern agile software prototyping Development, Security, Operations (DevSecOps) using community best practices aligned to applicable DoD, DoN and IC objective Continuous Integration Continuous Deployment (CICD) guidance. This shall include collaborative Contactor/Government development, information assurance, testing, configuration/data management methods, processes and tools The Contractor shall prepare and maintain a Software Development Plan (SDP) that encapsulates the Contractor’s DevSecOps CICD implementation. The SDP shall be presented at the program Kick-Off Review for Government concurrence and submitted within thirty (30) days for approval. The Contractor shall update the SDP when significant changes are required to be presented at subsequent PSR for Government concurrence and submitted within thirty (30) days for approval. (CDRL A009, A004, A00D)

3.3.8 Network Privileges

The Contractor shall work with the Government to gain NGA or other Agency provided network privileges when applicable for system/software development and transition activities for users on Unclassified, Secret, and Top-Secret domains. The privileged users are required at the start of task to be able to rapidly develop, deliver, test and support transition and deployment activities (below). The Contractor shall work with and interface with the applicable Cloud Computing, Information Assurance and Information System Security and library data accesses organizations to provide updates for Unclassified, Secret, Top Secret versions. (CDRL A003, A007)

3.3.9 Risk Management

The Contractor shall implement DoD aligned methods, tools and processes to provide continuous systematic, objective, and repeatable Risk Management. This includes implementation of prioritized identification of inter-dependent Cost, Schedule and Program risk factors along with corresponding mitigation actions, monitoring to be presented at the PSR Kick-Off Review and updated for subsequent PSRs. (CDRL A003, A004, A00D)

3.3.10 Property Management

The Contractor shall maintain an active Federal Acquisition Regulation (FAR) based Government Furnished Property (GFP) management function encompassing software, equipment, information, and data. The Contractor shall prepare and establish a GFP list in Contractor format based on their proposal to be presented for review at the PSR Kick-Off Review and updated for subsequent PSRs to address status, issues, and actions. (CDRL A00K)

3.3.11 Program Security

The Contractor shall implement and maintain Program Security compliance policies identified in Section 6. The Contractor shall prepare an Operational Security (OPSEC) plan to be presented at the Contract PSR Kick-Off Review for Government concurrence and submitted within thirty (30) days for approval. The Contractor shall update the OPSEC plan when significant changes are required to be presented a subsequent PSR for Government concurrence and submitted within thirty (30) days for approval. (CDRL A00J).

3.4 Concept Development

The Contractor shall perform mission centered engineering, research and analysis to derive ISR&T concepts, capabilities and technology through the following tasks:

3.4.1 Concept Development Mission Engineering and Analysis

The Contractor shall apply warfare domain Subject Matter Expertise (SME) in the conduct of multi-disciplinary Joint All Domain Command and Control – Joint Warfare At Sea (JADC2-JWAS) Operations & Scenario Mission Engineering & Analysis (ME&A) to assist the Government in characterization of current & emergent ISR&T challenges, problems and gaps. This includes end-to-end kill chain assessments of System of System (SoS) or Family of System (FoS) to assess current Program of Record (PoR) or future programs effectiveness against defined threats, and to identify Joint/Naval warfighting gaps as well as the capability and capacity required to address emerging threats.

The Contractor ME&A performance shall include participation and contribution to periodic: a) Naval Aviation Capability Based assessment Integrated Process (NCIP), b) community From the Air, Sea, Land, Anti-Submarine Concept of Operations (CONOPS) & Concept of Employment (CONEMP) Working Groups, c) NRO Sponsored Sensor-to-Shooter (S2S) Working Group and, d) joint service Tactical Exploitation of National Capabilities (TENCAP) analysis efforts. This further includes the F-35 Joint Strike Fighter and other Special Access programs platform/weapons capabilities in the development of CONOPS/CONEMPS, kill chains, capability gap assessments, and recommendations to OPNAV on how the capability gaps can be filled.

The Contactor shall perform integrated Kill Chain Analysis (KCA), Product Chain Analysis (PCA) and/or Image Chain Analysis (ICA) in evaluations of current and proposed space-based, theater, and tactical ISR systems support to targeting operations as further focused on quality assurance of the ISR end products and capability gaps. The Contractor shall use specifications and requirements documentation to generate performance predictions, review potential system capabilities, and to identify opportunities for insertion of advanced technologies or capabilities. The Contractor shall provide information, modeling and simulation results, and analyses in the areas of sensor tasking, scheduling, collection, production, extraction and fusion, as they relate to and impact overall product quality (e.g. data fusion). The Contractor shall apply KCA/PCA/ICA skills associated with system design, analysis, verification, and technical issues; such as calibration, anomaly resolution, performance assessments, and potential enhancements. The Contractor shall also apply KCA/PCA/ICA expertise in evaluations of future ISR sensor trends; such as persistence, timeliness, wide area, multi-mode, and cross-platform collections, sensor cross-cueing, horizontal integration, and adaptable, scalable, modular, and open architected sensor architectures. Sensor trends shall be applied to studying a broad range of targeting payloads, including standard & future platforms, weapons and hypersonic vehicles.

The Contractor shall apply ME&A to assist the Government development of a Mission Technical Baseline (MTB) to outline the future year threats plus help identify approaches to mitigate previously identified gaps and risk. The Contractor shall assess the relative merits of potential capability gap solutions in terms of potential effectiveness and overall military worth to include assistance in kill chain scoring. As required the Contractor shall assist the Government Integrated Capability Technical Baselines (ICTB) technical documentation capture. The Contractor shall provide ME&A recommendations to the Government in planning, experiments, demonstrations, and prototyping of National Systems ISR&T capabilities to include theater/tactical air/surface sensors and tracking systems integration, quality control and performance analysis.

Results of ME&A activities shall be summarized in monthly reports and/or documented in technical reports, data, memoranda or briefing materials during the task period of performance. (CDRL A001, A003, A004)

3.4.2 Concept Development Emergent Technology Assessment

The Contractor shall analyze emerging commercial and military technologies and their potential benefit for potential implementation in future Government or Contractor prototype ISR&T system capabilities. The Contractor shall participate in Advisory or Working Group meetings, program reviews, integration forums, technical exchanges forums in addition to conducting online (e.g. open source, Government authorized sites) research analysis efforts in order to provide reports on emerging technologies for use by NAWCWD. These evaluations may be in response to data calls from the IC Agencies and DoD Agencies and Commands. The Contractor shall report on analyses and prepare materials associated with results, findings, recommendations and actions for presentation at review meetings. These materials and/or findings shall be summarized and/or attached in monthly reports or as individual Contractor tailored formatted reports, memoranda and and/or presentations (CDRL A001, A003, A00D)

3.4.3 Concept Development Systems Analysis

The Contactor shall apply structure systems engineering analysis processes in context to integrated kill chain ME&A results (above) in the derivation of ISR&T Concepts. This includes providing context to the Analysis of Alternatives (AoA) plus developing creative solutions (i.e. formulation, synthesis) aspects for identification and down-selecting preferred ISR&T Concepts.

The Contractor shall establish Measure of Effectiveness (MOEs) and further decompose corresponding Measures of Performance (MOPs) to support subsequent evaluation (e.g. mission effectiveness, performance, suitability, cost, maturity, risk) for the relative merits of alternate Concepts to address identified ME&A mission capability objectives and requirements below.

The Contractor shall apply MBSE methods and Government provided documentation to model, characterize and define candidate for ISR&T Concepts in context to the Naval Operational Architecture (NOA), Naval Long Range Fires Integrated Capability Concept (NICC), NAVPLAN Integrated Framework (NIF) or other framework (e.g. JADC2) where applicable. The Contractor shall perform decomposition of alternative concepts attributes as supported by MBSE analysis with derived DoDAF views to include but not limited to: operational concept, end-users, functional/data flow, interfaces, features, capabilities, performance, interoperability, security and standards. This includes the interaction of the system architecture and functions with current and/or projected SoS elements to identify AoA key drivers to the order of operations, roles, responsibilities, resources loading and technology impact. Concept systems AoA shall encompass muti-echelon warfare operations partitioning to include but not limited to: a) Joint, Theater, Tactical and Unit level command operations, b) forward deployed & reach back operations, and, c) distributed processing nodes (e.g. embedded, non-embedded, Cloud-based, portable). System AoA analysis shall further encompass the range of current and emerging PoR System of System (SoS) or Family of Systems (FoS) capabilities including as a minimum:

a. National/Tactical ISR Tasking, Collection, Processing, Exploitation and Dissemination ( TCPED)

b. Effects based Targeting and Tasking

c. Theater/Tactical Command & Control Find, Fix, Track, Target, Engage, Assess (F2T2EA)

d. Combat Unit Level Mission Planning and Rehearsal

e. Air, maritime surface & subsurface and ground launch platforms

f. Combined effects kinetic and non-kinetic weapon

g. Line of Site, Beyond Line of Site and Satellite Communications

h. Joint/Navy real-time, non-real-time and static tactical situation feeds

i. Distributed forward deployed and reach-back forces networks & infrastructure

j. Cross Domain Information Sharing

k. Test range telemetry, instrumentation, gateways and data collection

l. Evolving Joint and Navy community of interest BMAs

As part of the Concept systems analysis, the Contractor shall further consider the application of NAWCWD developed Concepts, systems and components to include but not limited to: iSpy, Common Geopositioning Services Web (CGSWeb), Surface Target Attack Monitor (STAM), Dynamic INtegrated Operations (DINO), Portable Reference Imagery (PRI), Navy Video Targeting System (NVTS), Portable Geospatial Product Library (PGPL), Geospatial Data Base Management System (GDMS), Digital Point Positioning Data Base Air Operations Planning (DAOP),) and, Autonomous Target Acquisition Web Service (ATAWS).

The Contractor shall apply MOE/MOP Figures of Merit with system level architecture AoA to rank order and down-select preferred ISR&T Concepts. The Contractor shall refine the preferred Concept definition description through further kill chain end-to-end decomposition level of detail as supported by MBSE analysis with derived DoDAF views.

Results of this task shall be documented in the technical reports, data, memoranda, briefings and/or reviews. (CDRL A003, A004, A00D)

3.4.4 Concept Prototyping Areas of Focus

The development of ISR&T Concept Prototypes shall require incorporation of current or advanced algorithms processing and systems/software engineering in order to create new capabilities or have the potential to make existing systems more usable, flexible and effective across ISR&T integrated kill chain operations. Key areas of focus for potential incorporation in Concept Prototypes include but are not limited to the following:

3.4.4.1 Sensor Model Development

The Contractor shall perform Modeling and Simulation (M&S), algorithm development, design and system/software prototyping techniques to create new sensor models or adapt existing sensor models that can be utilized with Common Geopositioning Services (CGS), Surface Target Attack Monitor (STAM), Navy Video Targeting System (NVTS) and/or other ISR&T applications. In the case of IMINT systems methods (e.g. sensor/platform to ground space) that support photogrammetric algorithms shall be used to derive information from imagery and/or FMV sources. In the case of SIGINT and other ELINT or MASINT systems, Radio Frequency propagation mathematics shall be implemented in order to interface with existing components and provide new capabilities. Development and refinement of sensor model software will be applied to emerging and changing sensor systems that can be used in the ISR&T access and may require coordination and interaction with other DoD agencies and their Contractors.

3.4.4.2 Photogrammetric Algorithm Development

The Contractor shall perform M&S, algorithm development, design and system/software prototyping of techniques for photogrammetric, geo-positioning, and error estimation propagation in order to improve the performance and/or reliability of current and proposed multi-INT based targeting or related systems. Applications of interest are expected to include the sensor models previously provided by the National Geospatial Agency (NGA) through the Mensuration Services Program (MSP) as well as advanced NAWCWD applications (e.g. PRI, NVTS, STAM). Tasks may also address improvements to and/or integration with CGS and/or applications that may have integrated or embedded CGS capabilities. The Contractor shall provide photogrammetric and technical evaluation reports on targeting capabilities and compliance with stated requirements. (CDRL A003)

3.4.4.3 Multi-INT Data Mining

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques to enable effective multi-INT data mining across ISR&T systems. These activities shall focus on client-side visualization tasks (e.g. spatial, temporal, notional visualization) and server side database query, database mining, rules generation, second tier processing, and access controls plus the ability to mine local and network data sets across multiple heterogeneous data sources.

3.4.4.4 Multi-INT Data Integration

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques to enhance utilization of Multi-INT data integration within ISR&T systems. These activities shall focus on client-side visualization tasks (e.g. spatial, temporal, notional visualization) and server side database integration across multiple disparate data sources at potentially different points on the network (e.g. local, network, in-flight, in-transit). The Contractor shall integrate multiple heterogeneous data sources in a coherent manner consistent with existing system displays and/or emerging user requirements.

3.4.4.5 Multi-INT Enhanced Positive Identification

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques for improving current and predicted Positive Identification (PID) from National, Theater and Tactical Multi-INT ISR collection systems to enhance mobile or stationary targeting operations in varied contested operating environments. This shall include research and evaluation of current and emerging techniques, the application of AI/ML technology and validation methods.

3.4.4.6 Multi-INT Intelligent Data Analytics

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques to enhance data analytics of Multi-INT ISR information to support targeting operations through the application of AI/ML based narrow, general and super intelligent systems technologies. This shall include a focus on improving ISR&T predictive analysis of Enemy Course of Action (e.g. movement, status, tactics, intent, and deception) and similarly own state predicted posture of kill chain engagement assets and ISR&T mission-making systems (e.g. status, readiness, loading, resources).

3.4.4.7 Cross Domain Information Sharing

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques to enhance implementation of Multiple Security Level Cross Domain Sharing (e.g. TSABI, SABI) of ISR&T information M2M across IC, DoD and Special Access enclaves. This shall include research and evaluation on the current & emerging methods (e.g. Guards, Gateways, Tagging) and integrated kill chain AoA for their impacts to ISR&T systems implementation (e.g. security protocols, interoperability, source information obscuration, data transfer performance, certification & accreditation). (CDRL A003, A007)

3.4.4.8 ISR-Weapons Suitability Assessment

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques for estimation of current or predicted ISR collection systems factors (e.g. accuracy, timing, latency, quality, modes, coverage, tasking) individually or combined to support standoff weapons Area of Uncertainty (AOU) acquisition of time sensitive moving or stationary targets in varied contested operating environment conditions. (A003, A007)

3.4.4.9 ISR-Weapons Quality Track Custody

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques that improve ISR collection systems and management to enhance maintaining weapons quality track custody (e.g. persistence, timing, accuracy, coverage, positive identification) for cooperative & non-cooperative moving targets of interest in varied contested operating environments aligned to the corresponding performance capabilities of weapon systems (e.g. execution profile, communications, guidance, control, sensors, target acquisition). This shall include research and evaluation of current & emerging systems capabilities, the application of AI/ML technologies and validation methods. CDRL A003, A007)

3.4.4.10 ISR-Weaponeering Aids

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques for enhancing the automation of combined effects weaponeering analysis to enable ISR-target-weapon pairing identification of the recommended number and mix of weapons to meet strike requirements. This shall include predicting the assessment of weapons engagement against targets of interest key factors (e.g. damage lethality, survivability, executability, hit assessment, resources) for varied environmental conditions accounting for combined ISR and weapons capabilities (e.g. acquisition, discrimination, identification, aimpoint selection, fusing, effect impact). This shall include the advancement of new techniques and validation methods in addition to the use of legacy tools (e.g. Joint Munitions Effectiveness Manual Weaponeering System & Surface Warfare Effects Tables, weapon specific Salvo tables, STAM salvo table, DINO dynamic salvo tables, Maritime Lethality Analysis Toolkit). (CDRL A003, A007)

3.4.4.11 Communications Connectivity

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques to enhance assessment and utilization Line of Site (LOS), Beyond Line of Site (BLOS) and Satellite Communications (SATCOM) for the ISR & Operations integrated kill chain planning and employment of long-range fires Net Enabled Weapon systems. This shall include research and evaluation of extended range communications connectivity driving factors (e.g. interoperability, compatibility, availability, performance, security, reliability) and varied multiple network/radio waveforms/protocols (e.g. TCP/IP, UDP/IP, IXP, Link16, JREAP) to support AoA on impacts to ISR&T systems implementation. (CDRL A003, A007)

3.4.4.12 Intelligent COA Decision Aids

The Contractor shall perform M&S, algorithm development, design and system/software prototyping in the development of techniques to enhance Operational & Tactical Level of Warfare commanders’ COA decision advantage in the planning and employment weapon systems for deliberate and dynamic time sensitive long-range fires targeting operations. This shall include a focus on the synchronization and optimization of integrated kill chain ISR and Operations aligned to target tasking, effects criteria and operational constraints. This shall include research and evaluation of current & emerging BMA capabilities, Human Machine Interface (HMI) factors, application of AI/ML technologies and validation methods. Results of this task, including design, attributes, prior factor analysis, limitations and implementation, shall be documented in the technical reports, data, memoranda, briefings and/or reviews. (CDRL A003, A004, A007, A00D))

3.4.5 Concept Development Testing and Evaluation Analysis

The Contractor shall perform testing and evaluation of Government identified developmental ISR&T systems and report on their performance. Prototype systems shall consider and complement ISR&T accesses, metrics, benchmarks, and tools already in use by the community of interest while including additional metrics, data, and potentially, tools to specifically address emerging capabilities. Additionally, the Contractor shall provide visualization tools supporting rapid analysis and decision-making based on human-factor considerations (i.e., ease of use, complexity, and intuitive user interfaces) in the evaluation and analysis environment. The Contractor shall document capabilities and limitations discovered, perform AoA to evaluate potential improvements and/or suggest alternative technical approaches to relevant techniques or technologies. The Contractor shall review, validate test plans and procedures and provide input back to the Government and/or development Contractor to support test of systems, components, and/or algorithms to evaluate performance and feasibility of integration with applicable Joint/Navy ISRT SoS ISR&T FoS. Results of this task shall be documented in the technical reports, data, memoranda, briefings and/or reviews. (CDRL A003, A004, A00D)

3.4.6 Concept Development Research Briefings and Demonstrations The Contractor shall prepare briefings describing developed concepts, demonstrations, system evaluations, and/or development plans. This shall include the preparation, coordination and assistance in conducting the briefings & presentations by the Contractor for the Government and/or other designated Contractors as required to: Acquisition program offices, Training Centers, Government directed sites, Working Groups, Conferences and/or Symposia. Content of these briefings and descriptions of demonstrations shall be provided to the Government for review as specified during the period of performance and prior to delivery to any audience outside NAWCWD. (CDRL A003, A004)

3.4.7 Concept Development Performance and Risk Analysis

The Contractor shall perform risk analyses and/or review performance analyses provided by the Government and provide reports of results. Areas for analysis shall include ISR&T developed Concepts or stem from Fleet, Program Offices, or NAWCWD recommendations as to areas of risk for meeting future Navy ISR&T system requirements. The Contractor shall provide inputs to trade studies, Analysis of Alternatives and performance evaluations in an effort to assist NAWCWD with identification of potential prototype and operational developmental efforts for future ISR&T system. Results of this task shall be documented in the technical reports, data, memoranda, briefings and/or reviews. (CDRL A003, A004, A00D)

3.4.8 Concept Development MBSE Systems Analysis

The Contractor shall provide training of Government designated program cleared personnel in applying MBSE systems analysis methods and tools in architecture design and review This shall include IME stand-up aligned to the established Navy collaborative X-SYSCOM NOA methods to include: developer guidelines for fleet use, decisional use, mission construction, model overview, approach, integrated dictionary, design requirements traceability, configuration management, processes, standards and tools. The Contactor shall provide training of Government designated program cleared personnel or alternatively provide cleared SME in the development of project specific models, advanced prototype or PoR specific models interfacing, system analysis, and documentation artifacts for results capture. The Contractor shall further facilitate familiarization, access and potential re-use of Navy collaborative X-SYSCOM NOA multi-domain specific models and model development activities to include working group forums, architecture reviews, performance metrics capture, progress assessment/reports and progress reviews. Additionally, configuration and process considerations for varied CUI, DoD Secret, TS/SCI and Special Access security enclave levels shall be applied. Results of this task shall be documented in the technical reports, data, memoranda, briefings and/or reviews. (CDRL A003, A004, A00D)

3.4.9 Concept Development Planning Assistance

The Contractor shall provide analyses of concept capabilities & technology insertion requirements and budget planning estimates necessary to acquire, develop, deploy, maintain, and support implementation of ISR&T developed Concept prototypes or stem from other NAWCWD, Fleet, Joint/Navy DoD or IC Program Offices requirements. This task shall include the preparation of project plans for prototype development proposals or execution of current and future year resources for ongoing projects. Documentation resulting from these tasks shall be provided to the Government for use in planning the potential issuance of future contracts or proposals to DoD agency calls for Science and Technology (S&T) proposals, Urgent Need Statements (UNS) or Urgent Operational Requirements (UORs). Results of this task shall be documented in the technical reports, data, memoranda, briefings and/or reviews. (CDRL A003, A004, A00D)

3.5 Concept Prototyping

The Contractor shall perform rapid prototyping of IS&T Concept Prototypes systems, segments and/or components as follows:

3.5.1 Concept Prototype Architecture

The Contractor shall perform systems/software engineering and analysis decomposition of preferred Concepts (Section 3.4) into system, software and hardware design artifacts at a suitable level for rapid prototyping implementation, Architecture development shall consider prototype interfaces, software, hardware and testing factors (Sections 3.5.2 through 3.5.6). The Contactor shall assess with internal & external functional, performance and user trade-off impacts deriving the preferred prototype architecture including the use GOTS, COTS or MOTS software/components for Embedded, Non-Embedded or Cloud-Based elements as applicable. The Contractor shall apply suitable methods and tools to capture the prototype architecture design to support Government review in the form of technical reports, presentations, briefings and/or design description documentation with activities summarized in monthly reports. The Contractor shall provide updates to system development architecture documentation to assist the Government with its Configuration Management in synchronization with changes to the software under appropriate orders. (CDRL A001, A003, A004, A006, A00D, A00F)

3.5.2 Concept Prototyping Interface Design and Documentation

The Contractor shall decompose, define and verify ISR&T Concept Prototype internal and external integrated kill chain interfaces, interoperability & compatibility including but not limited to: information exchange (e.g. data content, schemas, protocols, methods, security) and physical (e.g. networks, communications, electrical, hardware) as applicable. For interfaces involving external systems, the Contractor shall provide feedback or report issues and describe their potential impact on ISR&T facility.

For Concept Prototypes involving MLS or MSL unidirectional and bidirectional Cross Domain Sharing (CDS) (e.g.