JTT Follow-On DRAFT SOO_23Aug2024.pdf

Air Force Life Cycle Management Center (AFLCMC)

Wing C2 Branch (C3CW)

Joint Targeting Toolbox (JTT) Follow-On

DRAFT Statement of Objectives (SOO)

Prepared by:

AFLCMC/C3CW

21 August 2024

1. Purpose:

The purpose of this acquisition is to obtain a highly qualified Contractor with determined expertise to develop, field, maintain, and support operations of the Joint Targeting Toolbox

(JTT) 6.x software series and to support the transition from and deprecation of the fielded legacy

JTT 5.x (JTT-CP – Capabilities Package). The Contractor shall provide engineering services including, but not limited to:

● Developing new software capabilities to address Government requirements

● Fielding, deployment, and software installation support

● Resolving technical debt

● Testing, training, Help Desk, and exercise support

During development of subsequent JTT 6.x software versions, the Contractor shall coordinate with the Government on requirements regarding interoperability with new data structures, integration with other Targeting Enterprise applications, and support to transition to modernized database connections, as required.

The Contractor shall provide sufficient personnel necessary to meet the objectives of this acquisition. The Contractor shall work professionally with other JTT and AFLCMC/C3C (Kessel

Run) contractors in support of the JTT Program Management Office (PMO) to further mission objectives.

2. Background:

2.1 System Description

JTT 6.x is a Government-owned and Government-led Command and Control (C2) weapons system. It works seamlessly across security domains and provides the targeting community an interoperable, collaborative capability to support both Joint and Coalition targeting operations.

As the Joint system of record for targeting and target list management, JTT imports and provides access to Joint Force commander’s guidance, objectives and tasks. It enables pairing of full spectrum targets to commander’s planning and execution, providing access, review, editing of targets and target lists in relation to commanders’ strategy-to-task data. It enables users to associate targets to strategic desired elements and display of operational data elements tied to strategic objectives.

JTT connects to National military intelligence databases to enable target creation, target queries, and nomination of targets on myriad target list types. It allows users to create, name, rename, maintain, save, search, and share Full Spectrum Electronic Target Folders (ETF). JTT also allows users to query temporal aspects of targets, including search, select, and view of time sequencing of Time on Target (TOT) and/or reconnaissance TOT. It also provides access to targeting/weaponeering data from external effects planning systems and enables users to create and manage target lists in a communications degraded environment.

The software enables target visualization on a map dashboard and allows for the export of targets and target lists to geospatial displays via Keyhole Markup Language (KML). JTT supports Joint Desired Point of Impact (JDPI) and weaponeering nomination for one or multiple

Air Tasking Orders (ATOs) and enables the user to create, store, manage, integrate, and disseminate operational assessment data and services.

2.2 Customer and User Descriptions

The Primary Stakeholders for the JTT Program are: Air Combat Command (ACC), Headquarters Air Force (HAF), and Joint Staff (JS). JTT is part of the Joint Targeting

Intelligence Modernization Integration (JTIM) effort to build an integrated and modernized solution for the Joint Targeting Enterprise and Combatant Commands (CCMDs). The Combatant

Command Intelligence-Enterprise Management Support Office (CCI-EMSO) is the lead integrator for JTIM under the Office of the Undersecretary of Defense for Intelligence and

Security (OUSD I&S).

JTT supports users across the Armed Forces, the Department of the Air Force (DAF), Joint Services, U.S. Intelligence Community (IC), CCMDs, and Coalition and Allied targeting communities. JTT supports Higher Headquarters activities, to include but not limited to: Major

Commands, Numbered Air Forces, Air Operations Centers, and Air Force (AF) Staffs and

CCMDs.

3. Mission and Scope:

3.1 Mission

JTT is an ACC-sponsored software capability which provides modernized, standardized, secure, automated decision support for Joint and Allied commanders worldwide. The system is deployed at C2 nodes at the National, Force, and Component elements in support of decision-makers and will include targeting capabilities compatible within the force/theater-level common operating environments (plan, execute, and assess).

JTT supports Joint/Coalition combat operations which include integrated air, ground, naval, and cyber targeting functions throughout the Joint targeting cycle. This includes objectives, target development, capabilities analysis, force assignment, force execution, and assessment, working seamlessly between multiple security domains. JTT gives the targeting community the ability to be interoperable and collaborative across the Joint Enterprise. JTT allows end - to - end target planning, via host/core service and Joint C2 systems, by targeteers and target specialists at all planning levels and nodes.

3.2 Scope:

The scope of this effort is for a services contract model:

● Technical and engineering services to support the transition from the legacy fielded

JTT 5.x software series to field the JTT 6.x baseline and deprecate JTT 5.x.

● Initial training, fielding, and deployment of new cloud and on-premises (OP) instances to correspond with the standup of JTT 6.x at each installation.

● Professional services using agile software development to support the JTT 6.x software series.

● Continuous operational support, integration, modernization, and development of new and existing features for JTT 6.x.

● Providing Help Desk assistance; follow-on, schoolhouse, and pre-exercise training;

exercise support; and field service support to Continental United States (CONUS) and

Outside Continental United States (OCONUS) JTT 6.x users.

● Implementing new and/or emerging standards and technologies into JTT 6.x, as directed by the Government.

● Implementing any software, integrations, interoperability, and infrastructure technologies necessary to support JTT 6.x, as directed by the Government; there is no hardware requirement for this acquisition.

4. Place of Performance

The primary place of performance will be the Contractor’s facility(ies). Activities in support of this contract may be performed at military installations, or remotely. Periodic travel will be required to both CONUS and OCONUS locations. All travel shall be conducted in accordance with the requirements of the scope of work.

5. Performance Objectives:

The first objective of this acquisition is to field the JTT 6.x software baseline currently in development and transition fielded JTT from the legacy JTT 5.x to the 6.x series. Second, this effort will support operations for JTT 6.x. Third, the acquisition seeks to enhance the 6.x series with new capabilities to fulfill emerging and future user-driven requirements. The following

Objectives sections are defined as the following:

5.1 Transition Objectives: Support to deprecate JTT 5.x and transition to the 6.x series.

5.2 Baseline Software Objectives: Testing, software development activities, and deployment to field JTT 6.x on cloud-based and OP instances, supporting AF, Joint, IC, Coalition, Allied (Foreign Military Sales - FMS), and other users across the U.S. Armed

Forces.

5.3 Follow-On Development Objectives: Software development activities to continue to modernize the JTT 6.x series and add new capabilities to the baseline.

5.4 Integration and Interoperability Objectives: Software development activities to promote integration of the JTT 6.x series with modern targeting applications and databases across the Targeting Enterprise.

5.5 Software Support Objectives: Includes engineering technical support, Help Desk, and Training objectives in support of the JTT 6.x fielding rollout and subsequent fielded versions in the 6.x series.

5.6 Management Objectives: Planning, execution, tracking, reporting, and staffing objectives to fulfill other Performance Objectives and Government requirements.

5.7 Cyber Security Objectives: Includes best practices for maintaining compliant and hardened security posture surrounding all software activities and deliverables.

5.1 Transition Objectives

5.1.1 Support deprecation of legacy JTT 5.x fielded system and transition to JTT 6.x baseline across Department of the Air Force (DAF), CCMD, IC, Joint, U.S. Armed Forces, Coalition, and Allied Targeting Enterprise.

5.1.2 Complete remaining development tasks/backlog items from JTT 6.x baseline software system to prepare for initial fielding to users.

5.2 Baseline Software Objectives

5.2.1 Complete Developmental Test and Evaluation (DTE), Operational Test and Evaluation

(OTE), and exercise-level testing that are prerequisites to fielding.

5.2.2 Field JTT 6.x baseline through Initial Operational Capability (IOC) and Full Operational

Capability (FOC).

5.2.3 Resolve JTT 6.x technical debt by prioritizing and fixing deficiencies and bugs, as directed by the Government.

5.2.4 Address all known Government requirements for the JTT 6.x baseline.

5.2.5 Install and deploy JTT 6.x baseline software to:

● Cloud platforms across various security domains and enclaves.

● Various CONUS and OCONUS OP/Denied, Degraded, Intermittent, or Limited

(DDIL) instances, as required.

5.3 Follow-On Development Objectives

5.3.1 Implement any software and infrastructure technologies necessary to support JTT.

5.3.2 Develop automation, where directed, within legacy and emerging software Application

Programming Interface (API) connections, configurations, and workflows, including, but not limited to:

● Theater Battle Management Core System (TBMCS)

● Master Air Attack Planning Toolkit (MAAP-TK)

● Kessel Run All-Domain Operations Suite (KRADOS)

5.3.3 Address new Government requirements for adding capabilities to the JTT 6.x software baseline as they arise.

5.3.4 Able to increase/scale contractor services to adjust for real world events and increase in stakeholder requirements to deliver new or improved features in an accelerated timeline.

5.3.5 Ensure new capabilities do not introduce additional deficiencies or bugs.

5.3.6 Adapt JTT 6.x data structures, UI/UX, and workflows to maintain currency with updates to Targeting Enterprise workflows, including, but not limited to:

● Critical Elements/Critical Target Elements (CE/CTE)

● Capability Solution Packages (CSP)

● Target Engagement Packages (TEP)

5.4 Integration and Interoperability Objectives

5.4.1 Maintain connection and interoperability with critical legacy databases and software APIs in the cloud and within AF Air Operations Center (AOC) instances, configurations, and workflows, including, but not limited to:

● Modernized Integrated Database (MIDB)

● MAAP-TK

● TBMCS

5.4.2 Onboard to Government-directed DevSecOps platform and provide continuing engineering support to maintain Continuous Integration/Continuous Deployment (CI/CD) for JTT 6.x.

5.4.3 Continuously integrate and interoperate with emerging modernized critical database APIs

(i.e. Machine-assisted Analytic Rapid-repository System - MARS) within the Targeting

Enterprise, as directed by the Government.

5.4.4 Integrate JTT 6.x with other AFLCMC/C3C, AF, and Joint Targeting Enterprise applications, as directed by the Government (i.e. KRADOS).

5.5 Software Support Objectives

5.5.1 Provide virtual engineering and technical expertise supporting cloud-based and OP installations/instances, as required.

5.5.2 Provide both permanent and periodic on-site engineering and technical expertise supporting cloud-based and OP installations/instances, as required; this includes, but is not limited to:

● AOCs

● FMS instances

● CCMDs, such as U.S. Indo-Pacific Command (INDOPACOM), U.S. Strategic

Command (USSTRATCOM), etc.

5.5.3 Provide 24/7/365 Help Desk support for JTT 6.x for global user base to triage and fix impromptu issues as they arise across various security domains.

5.5.4 Provide mobile/on-site training support to CONUS and OCONUS locations and across various security domains.

5.5.5 Provide virtual training support for JTT users across various security domains.

5.5.6 Provide virtual software administration training support to users across various security domains.

5.5.7 Provide mobile/on-site and remote support for CONUS and OCONUS exercises, as directed by the Government.

5.6 Management Objectives

5.6.1 Employ Agile software development methodology to maximize adaptability to new and fluid requirements.

5.6.2 Pursue innovative and collaborative approaches to staffing, tooling, technical approaches, planning, and materials in support of program objectives.

5.6.3 Develop regular reporting cadences on progress towards fulfilling program objectives and requirements.

5.6.4 Support external engagements with various AF, Joint, IC, Coalition, and Allied, stakeholders across the Targeting Enterprise, including, but not limited to:

● Stakeholder engagements

● Technical Exchange Meetings (TEMs)

● Test events

● Conferences

5.6.5 Employ effective cost management strategies to ensure successful program execution within resource constraints.

5.6.6 Identify, analyze, address, report, and track program risks and issues as they arise.

5.6.7 Employ user-centric development and design approaches to ensure user feedback into

User Interface/User Experience (UI/UX) updates (and associated front-end/back-end work).

5.6.8 Maintain and manage a backlog of new trouble tickets and user engineering requests;

implement upgrades in coordination with the Government.

5.6.9 Develop and track appropriate cloud user metrics for user activity, locations of current active OP instances, and other metrics as directed by the Government.

5.7 Cybersecurity Objectives

5.7.1 Manage code and software vulnerabilities appropriately and develop, test, and operate software securely in accordance with all applicable security requirements and best practices.

5.7.2 Continuously apply cybersecurity updates, upgrades, patches, and fixes to maintain secure system operations on all fielded instances.

5.7.3 Utilize current cybersecurity tools to automate and/or enhance vulnerability discovery, analysis, reporting, remediation and management.

5.7.4 Develop recommendations addressing how to maintain and/or improve the security posture of each version of software.

5.7.5 Provide support and required security artifacts to obtain, maintain, and renew all cybersecurity accesses and deployments across all relevant security domains and enclaves, as necessary, including, but not limited to:

● Authorities to Proceed (ATP)

● Authorities to Test (ATT)

● Authorities to Operate (ATO)

● Authorities to Connect (ATC)

● Certificates to Field (CTF) or equivalent software certification

6. Operating Constraints

6.1 Access to various secure spaces, accounts/tokens, domains and networks from performance location that are necessary to fulfill program objectives, including, but not limited to:

● Common Access Cards (CACs)

● Non-classified Internet Protocol Router Network (NIPRNet)

● Secret Internet Protocol Router Network (SIPRNet)

● Joint Worldwide Intelligence Communications System (JWICS)

6.2 All personnel who necessarily require access to, or may generate classified information and have an established Need To Know (NTK) must hold appropriate security clearances and adhere to proper information protection and operational security protocols and policies.

6.3 Facility security accreditation up to Top Secret in place by contract award and maintained through the complete life cycle of this acquisition and ability to access facility 24/7.

6.4 All personnel that require access to Department of Defense (DoD) Information Systems and are actively engaged in conducting information security functions, or require server system access, are DoD 8570 compliant.

6.5 Compliance with security provisions established by the Security Classification Guide (SCG) and standard DoD security procedures and regulations.

7. Acronyms:

ACC Air Combat Command

AF Air Force

AFLCMC Air Force Life Cycle Management Center

AOC Air Operations Center

ATC Authority to Connect

ATO Air Tasking Order

ATO Authority to Operate

ATP Authority to Proceed

ATT Authority to Test

C2 Command and Control

C3C Kessel Run Division, AFLCMC DAF PEO C3BM

C3CW WingC2 Branch of C3C, AFLCMC DAF PEO C3BM

CAC Common Access Card

CCI-EMSO Combatant Command Intelligence-Enterprise Management Support Office

CCMD Combatant Command

CI/CD Continuous Integration/Continuous Delivery

CONUS Continental United States

CTF Certificate to Field

DAF Department of the Air Force

DAF PEO C3BM

Department of the Air Force Program Executive Office: Command, Control, Communications & Battle Management

DevSecOps Development, Security, Operations

DDIL Denied, Degraded, Intermittent, or Limited

DoD Department of Defense

DTE Developmental Test and Evaluation

ETF Electronic Target Folder

FMS Foreign Military Sales

FOC Full Operational Capability

HAF Headquarters Air Force (Air Staff)

IC U.S. Intelligence Community

INDOPACOM U.S. Indo-Pacific Command

IOC Initial Operational Capability

JDPI Joint Desired Point of Impact

JTIM Joint Targeting Intelligence Modernization

JTT Joint Targeting Toolbox

JTT-CP Joint Targeting Toolbox-Capabilities Package

JS Joint Staff

JWICS Joint Worldwide Intelligence Communications System

KML Keyhole Markup Language

KRADOS Kessel Run All-Domain Operations Suite

MAAP-TK Master Air Attack Planning Toolkit

MARS Machine-assisted Analytic Rapid-repository System

MIDB Modernized Integrated Database

NIPRNet Non-classified Internet Protocol Router Network

NTK Need To Know

OCONUS Outside Continental United States

OP On-Premises

OTE Operational Test and Evaluation

OUSD (I&S) Office of the Undersecretary of Defense for Intelligence and Security

PMO Program Management Office

SCG Security Classification Guide

SIPRNet Secret Internet Protocol Router Network

SOO Statement of Objectives

TBMCS Theater Battle Management Core System

TEM Technical Exchange Meeting

TOT Time on Target

UI/UX User Interface/User Experience