JTIC2S Capability Evolution RFI_18June2026.pdf

RFI Number: RFI-JTIC2S-2026 Date: May 26, 2026 Subject: Request for Information - Joint Targeting Integrated Command and Coordination Suite (JTIC2S) Commercially Available Capability

DISCLAIMER

THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY. THIS IS NOT A

REQUEST FOR PROPOSAL, QUOTE, OR BID. IT DOES NOT CONSTITUTE A

SOLICITATION AND SHALL NOT BE CONSTRUED AS A COMMITMENT BY THE

GOVERNMENT. RESPONSES IN ANY FORM ARE NOT OFFERS, AND THE

GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT FROM THIS

RFI. NO FUNDS ARE AVAILABLE TO PAY FOR PREPARATION OF RESPONSES TO

THIS RFI. ANY INFORMATION SUBMITTED BY RESPONDENTS TO THIS RFI IS

STRICTLY VOLUNTARY.

1.0 INTRODUCTION AND BACKGROUND

In 2022, the US Army initiated the modernization of the Joint Automated Deep Operations Coordination System (JADOCS). The development of JADOCS can be traced back to the Advanced Field Artillery Tactical Data System (AFATDS), a related system for coordinating, controlling, and executing fires that was developed in 1989 and first deployed in 1995.

The system, formerly known as the Automated Deep Operations Coordination System (ADOCS) was officially renamed the Joint Automated Deep Operations Coordination System (JADOCS) in 2003 and transitioned to the Product Manager for Fire Support Command and Control.

JADOCS has a history of evolutionary development:

• 2005: JADOCS began operating as a graduated Advanced Concept Technology Demonstration (ACTD) program.

• 2008: The Vice Chief of Staff of the Army approved JADOCS for acquisition program status under the Capabilities Development for Rapid Transition (CDRT) program.

• JADOCS v2.0: The CECOM Life Cycle Management Command, Software Engineering Center (SEC) completed the development of JADOCS v2.0.

Due to its aging software architecture and codebase, JADOCS is approaching obsolescence. The U.S. Army has initiated the development of a successor system called the Joint Targeting Integrated Command and Coordination Suite (JTIC2S), which provide fires targeting capability and a joint fires targeting common operational picture across forces. JTIC2S is currently under development by the US Army C5ISR Center at Aberdeen Proving Ground (APG), Maryland, with a multi-vendor approach to leverage industry expertise in building this next-generation system. JTIC2S development follows an agile, Development and Operations (DevOps)-centric model focused on iterative development, frequent user feedback, and continuous assessment.

• Development Cycle: A new Engineering Release (ER) is released after each Program Increment (PI) every thirteen (13) weeks.

• Current Status: To date, nine (9) ERs have been successfully released and assessed by Army units.

• Program Goal: Objective is full displacement of JADOCS for all Army users by the end of FY2026. Threshold is beginning displacement by end of FY2026.

• JTIC2S is an application that is part of the Army’s Next Generation Command and Control (NGC2) modernization effort.

This RFI supports the Army’s robust and innovative market research initiative and seeks to identify/assess either commercially mature solutions from industry partners and/or commercial interest to continue evolving JTIC2S capabilities.

2.0 DESIRED CAPABILITY AND EVOLUTION

The Army's high-level vision for JTIC2S capability and evolution includes (but is not limited to):

• Automation of planning, Joint / coalition coordination, and targeting process to the greatest extent possible.

• Integration of Artificial Intelligence/Machine Learning (AI/ML) for man-in-the-loop automation of targeting processes.

• Enhanced data fusion from multi-domain Joint interfaces (e.g., Link-16).

• Improved user interface/user experience (UI/UX) reducing cognitive load on operators, leveraging human factors engineers and user feedback.

• Transition to a cloud-native architecture for improved scalability and resilience (NGC2 Optimized).

• Sharing of data across common data fabric(s).

• Maximizing use of common services and applications as they are made available by NGC2.

• Context-aware, embedded training and cognitive assistance designed to minimize user cognitive load, promote intuitive operation, and dynamically facilitate task execution at the point of need.

The Army is seeking information on how industry partners have addressed similar capabilities. We are interested in learning about your experience and capabilities in these areas. Please provide information on when, how, and with what products or projects you have addressed the desired capabilities listed above. Please see Section

4.2 for further details

3.0 CURRENT DEVELOPMENT APPROACHES

The Army is assessing several broad approaches for the future of JTIC2S. To help inform our acquisition strategy, we are seeking information related to the following areas. Respondents are requested to provide information that can help the Government understand their capabilities and experience as they relate to one or more of the approaches listed below.

Areas for Information (Applicable to all approaches):

• Please describe your company's approach to leading agile development processes (e.g., Roadmap development, Program Increment planning, sprint reviews, demonstrations). We are interested in understanding your agile lifecycle and any milestone tracking methodologies you use.

• Please provide information on your experience with providing on-site support for incremental capability releases to facilitate DevOps with military units.

• We are interested in your experience with Model-Based System Engineering (MBSE) tools (e.g., MagicDraw) and the development of artifacts to support Joint interoperability requirements (e.g., AV-1, OV-3, OV-5b, SV-6). Please describe your experience and provide examples of artifacts, if possible.

• Please describe your experience with Army cyber procedures and approvals. We are interested in your processes for managing external dependencies, automating updates, and addressing cyber considerations, such as Security Technical Implementation Guides (STIGs) and Security Requirements Guides, and managing records in SIPR eMASS.

• To assist with our planning and budgetary analysis, please provide a Rough Order Magnitude (ROM) non-binding cost estimate for a notional solution based on the capabilities described in this RFI. The ROM could include potential licensing structures or other approaches. This estimate is for planning purposes only and will not be considered a binding offer.

• The Government can provide the source code for the current JTIC2S as requested. To request access to the source code, please contact the individuals listed below.

Ms. Licinda Peters, Contracting Officer at licinda.m.peters.civ@army.mil Mr. Walker Bazemore at walker.d.bazemore.civ@army.mil Ms. Curtissa Bond at curtissa.m.bond.civ@army.mil

Approach #1: Information on Mature Commercially Available Solutions

• Please provide information on any existing products your company has that you believe meet or exceed the capabilities of JTIC2S. We are interested in understanding their potential for future capability growth.

• Please describe your experience with programs where a new solution completely replaced a legacy system for all future development.

Approach #2: Information on Capability Migration

• Please provide information about any existing software solutions your company offers that could accelerate and offer advantages over the current JTIC2S.

• We are interested in your experience migrating specific, high-value capabilities (e.g., containerized services, data visualization services, targeting product services) from a legacy codebase into a new target software environment.

• Please describe your experience with solutions that have combined a new target environment with harvested capabilities from a legacy system.

Approach #3: Information on Continued Evolution of an Existing System

• Please provide information on your experience with evolving an existing system's capabilities.

• We are interested in your experience leveraging an existing codebase as the starting point for all future development on a project.

4.0 RESPONSE INSTRUCTIONS

4.1 Submission Format and Deadline

• Point of Contact: RFI submission responses shall be directed via email to:

PM_C2_Apps_RFI@army.mil with the email subject line “PM_C2_Apps_JTIC2S_Response” mailto:licinda.m.peters.civ@army.mi mailto:walker.d.bazemore.civ@army.mi mailto:curtissa.m.bond.civ@army.mil mailto:PM_C2_Apps_RFI@army.mil

• Submission Deadline: Information papers are due no later than (NLT) 23 June 2026, 1300 Eastern Standard Time (EST).

• Format: Microsoft Word or Adobe PDF, 12-point font, single-spaced, one-inch margins.

• Submissions will not exceed 10 pages (not including the cover page). The paper should focus on your solution’s preferred approach, your vision, and any processes you have in place to facilitate JTIC2S evolution.

• The submissions shall include the following information: Contact Information:

Company name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail of designated point of contact.

• Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information.

Please be advised that all submissions become Government property and will not be returned. In addition to Government civilians, Government support contractors may review and evaluate the whitepaper submission. As of now, PM C2 Apps has not identified the need for contractor support personnel to review RFI response(s). Should a need be identified, the RFI will be updated to include Proprietary Data Protection Agreement (PDPA) instructions.

4.2 Content of Response

Respondents should frame their submission around the information sought in Section 3.0. In addition to describing your company's experience and capabilities, the response should address the following questions to help us better understand the current landscape of technology and expertise:

Technical Approach & Innovation:

• What innovative technologies (e.g., specific AI/ML models, data fabrics, distributed ledger) have you implemented or would you recommend for a system like JTIC2S?

• How have you approached data rights and intellectual property in past government-industry partnerships?

• What is your perspective on the best approach to ensuring a system is adaptable to future threats and technologies?

Experience & Past Performance:

• Can you provide examples of similar systems you have developed or integrated for the Department of Defense (DoD) or other government agencies?

• What is your company's experience with DoD security standards and operating in a DevOps-centric environment?

Cost & Schedule:

• Within your ROM, what are some typical contract models or shared savings models that would effectively incentivize industry to exceed baseline delivery schedules while maintaining cost efficiencies?

• Based on your experience, what is a realistic range for a timeline for the development, testing, and deployment of a system like the one described?

Risk Management:

• From your perspective, what are the primary risks associated with integrating a new system like this with other government systems, and how have you managed those risks in the past to ensure interoperability?

5.0 OTHER COORDINATING INSTRUCTIONS

The Government representatives may or may not choose to meet with respondents to this RFI. Such meetings and discussions would only be intended to get further clarification of potential capability to meet the requirements. In addition, the Government intends to conduct a virtual industry day to facilitate a transparent exchange of information with interested parties on 02 June 2026, 1100, Eastern Standard Time (EST). Requests to participate in the Virtual Industry Day shall be submitted to the email address PM_C2_Apps_RFI@army.mil NLT 01 June, 1200 (EST) with the email subject line “PM_C2_Apps_JTIC2S_Industry_Day” and include the names, email addresses and company name of up to two participants per company. Upon approval, the participants will be provided with a meeting link. Additionally, C2 Apps encourages questions to be submitted prior to Industry Day. Questions can be submitted to the email address PM_C2_Apps_RFI@army.mil with the email subject line: “PM_C2_Apps_JTIC2S_Q&A”.

Follow-up Sessions: The Army will review all information papers and schedule separate half-day onsite sessions at APG with selected respondents to discuss and review the approaches provided. These sessions will cover:

- Clarification of the provided approach.

- Demonstrations of any solutions provided.

- Discussion of the respondent’s past performance and relevant experience

(e.g. targeting, Joint coordination, fires, etc.).

- Topics related to licensing, intellectual property rights, and data rights.

- Respondent’s experience and methodology regarding agile development practices, incorporation of user feedback through DevOps, cyber vulnerability reporting and remediation, CI/CD, configuration management, and other related areas.

Respondents seeking to review the JTIC2S source code must be prepared to sign a Non-Disclosure Agreement (NDA) pursuant to FAR 3.104 Procurement Integrity. The government shall safeguard all sensitive information related to an RFI for acquisition planning purposes, as well as any subsequent procurement, if applicable. When the government provides proprietary source code to a potential bidder, that code becomes part of the procurement information and must be protected from unauthorized disclosure. Government-owned source code is often categorized as Controlled Unclassified Information (CUI). Federal regulations mandate that agencies protect CUI, and requiring an NDA from external parties who are granted access is a primary method of ensuring that protection.

Do not submit classified material in response to this RFI. The government will not review or retain any classified submissions. Any links included within the document should be checked for readability/accessibility and not include classified material(s).

This RFI is open to all interested industry partners (including small businesses).

No solicitation exists currently. The government reserves the right to use information obtained from this RFI for acquisition planning purposes.

6.0 Questions

Any questions regarding this announcement and request that require a response that includes Controlled Unclassified Information (CUI) shall be submitted in writing via e-mail, NLT 11 June 2026, 1200 (EST), to the email address PM_C2_Apps_RFI@army.mil with the email subject line:

“PM_C2_Apps_JTIC2S_Q&A”. Verbal questions will NOT be accepted. Questions shall NOT contain proprietary or classified information.

7.0 Summary

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources that can provide tailorable warfighting application solutions in an Agile and DevSecOps environment. The information provided in the RFI is subject to change and is not binding on the Government. The Army has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.