Tactical Software Management System Requirements-RFI.pdf

Request for Information (RFI): Tactical Software Management System Application

Reference Number: RFI-SW-2024-001 Issuing Office: Department of the Army, Program Executive Office Date of Issuance: May 18, 2026 Response Due Date: June 1, 2026

1.0 INTRODUCTION

This is a Request for Information (RFI) for market research purposes only, issued by the Department of the Army. This is not a solicitation for proposals, proposal abstracts, or quotations. The purpose of this RFI is to gain knowledge of the capabilities, capacity, and qualifications of potential contractors to develop a software tracking and release application for disconnected tactical systems. The information provided will help the Government in developing a future acquisition strategy.

2.0 BACKGROUND

The Army's current software management processes for disconnected tactical systems are inefficient and pose significant operational risks. The management of software release approvals and compliance tracking is highly manual, relying on disparate tools like ETMS2, email, and PM-local SharePoint sites. Fragmented and siloed execution across PMs results in a lack of centralized Army-wide visibility, long delays in software release approvals, and hinders the Army's ability to make informed decisions about cyber readiness for disconnected tactical systems. The absence of an integrated management system to track software versions installed on hardware baselines prevents accurate compliance reporting and timely incident response, leading to potential mission degradation and increased cybersecurity vulnerabilities.

The Government is seeking a centralized, cloud-based platform to streamline and automate the software tracking and release process, from approval to distribution and compliance reporting. The proposed Tactical Software Management System application will provide end-to-end visibility, enabling commanders to accurately assess cyber readiness, reduce the time required to deploy critical software updates, and improve overall operational effectiveness.

3.0 REQUIRED CAPABILITIES

The Government is seeking information on solutions that can meet the following requirements, as detailed in the attached document:

3.1 System Integration & Interoperability

• API connectivity to authoritative data sources (e.g., GCSS-Army, MMIS, Army Vantage) to link software versions to hardware baselines. Integration with GCSS- Army data may be facilitated via a two-way API with Army Vantage.

• Capability to report software versions down to the system serial number level. The solution must associate software with both the Major End Item (parent platform) and the Target Component (child) directly receiving the software update. If the specific Target Component is not serialized in GCSS-Army, the system must default to tracking compliance against the Major End Item's serial number.

3.2 Core Functionality & User Management

• A cloud-based software repository for storing and managing software packages, accomplished by integrating with the existing Army Software Innovation Center (ASIC) software repository (“REPO”) via API for package storage and retrieval, rather than developing a new file repository.

• Support for Common Access Card (CAC) user authentication.

• Scalability for large-scale deployments and an efficient process for onboarding new users and systems.

• Functionality for end-users to report the completion of software updates within the application.

3.3 Workflow & Process Automation

• Ability for administrators to create and manage distinct workflows for Full, Conditional, and Urgent software materiel releases (SMR) or software releases (SR) with unique approval chains in accordance with AR 770-3.

• Support for assigning alternate or delegate approvers, and the ability to process workflow steps in parallel.

• Automated email notifications and alerts for required actions and outstanding approval signatures, capable of reaching users across the Army environment.

• Ability for users to upload documents and add comments within the workflow, including capturing formal “get-well plans” and risk acceptance signatures from gaining Commands for conditional or urgent releases.

3.4 User Interface & Visualization

• Intuitive dashboards and analytics to summarize software compliance and cyber readiness by UIC.

• Visual representation of software release status, including progress bars and completion percentage for a given software release.

3.5 Physical Media & Shipment Tracking

• Capability to track physical media shipments, monitor status, and record delivery dates from origin to final destination without loss of visibility.

• Functionality to encrypt data for shipment on physical media and decrypt it upon receipt.

3.6 Metrics & Reporting

• Capability to generate metrics on timeliness, performance, security, and logistics, specifically including:

o Timeliness: Total end-to-end processing time for a release; duration a release package pends in a specific approver's queue; average time from software deployment to user-reported installation completion; and deviations from planned fielding dates.

o Performance: Overall patch compliance rates across targeted systems;

software download failure rates; and identification of hardware (by Line Item Number / National Stock Number) experiencing the highest download failure rates.

o Security & Logistics: Percentage of physical media shipments tracked accurately from origin to destination without loss of visibility, and data encryption/decryption success rates.

o Format: The system must provide the capability for authorized users to export all reporting data in common, non-proprietary formats such as CSV or XLSX for external analysis.

4.0 INFORMATION REQUESTED

Interested parties are requested to submit a capabilities statement that addresses the following:

1. Company Information: Company name, address, point of contact, CAGE code, and business size/socio-economic status.

2. Capability Narrative: A detailed description of your company’s ability to meet the requirements outlined in Section 3.0. Please describe your technical approach and any existing or past solutions that demonstrate this capability.

3. Technical Feedback: Provide any feedback on the feasibility of the requirements.

Are there any technical challenges, risks, or alternative approaches the Government should consider?

4. Estimated Timeline & Cost: A rough order of magnitude (ROM) for the timeline and cost, including a breakdown of estimated costs for the initial development, annual licensing/maintenance, and any tiered pricing based on the number of users or systems.

5.0 SUBMISSION INSTRUCTIONS

Responses to this RFI are due by June 1, 2026. Please submit your response electronically to the below: with the subject line "Response to RFI-SW-2024-001: Tactical Software Management System Application". The submission should not exceed 7 pages.

Nekeya Sanders, Contract Specialist nekeya.r.sanders.civ@army.mil

Lindsay Vierheller, Contracting Officer Lindsay.m.vierheller.civ@army.mil

6.0 DISCLAIMER

The Government is not obligated to and will not pay for any information received in response to this RFI. Any information submitted by respondents is strictly voluntary. This RFI does not commit the Government to contract for any supply or service whatsoever.

mailto:nekeya.r.sanders.civ@army.mil mailto:Lindsay.m.vierheller.civ@army.mil