2026.03.09 CSO Call 003_TRAC2ES.docx

Commercial Solutions Opening (CSO) Call 003 for Transportation Command "Medical" Regulating and Command & Control Evacuation System (TRAC2ES)

IT Programs & Support Services Division (TCAQ-D)

Instructions

See the current version of TRANSCOM25CSO001, Attachment 1: Phase I – Documentation Submission Requirements and the information provided herein.

Questions Due

Solution Briefs Due 10:00 AM (CT) on 19 March 2026

10:00 AM (CT) on 26 March 2026

Contract Specialists teyroko.s.perkins.civ@mail.mil emily.j.vosse.civ@mail.mil

Amy M. Miller Contracting Officer amy.m.miller50.civ@mail.mil

Background:

U.S. Transportation Command (USTRANSCOM) is the single manager for global patient movement for the Department of War (DoW)[footnoteRef:1], responsible for synchronizing transportation and medical evacuation to provide life-saving care to warfighters across the spectrum of military operations. [1: Department of War (DoW) is formerly known as Department of Defense (DoD). All references to Department of Defense (DoD), within CSO TRANSCOM25CSO001, are synonymous with references to DoW in this Call.]

TRAC2ES is a critical system for the DoW supporting global patient movement operations by integrating medical regulating, patient evacuation, and command and control decision support, ensuring efficient and secure patient movement across peace, war, and contingency scenarios. TRAC2ES handles sensitive data, including Personal Identifiable Information (PII) and Protected Health Information (PHI), and operates within both classified and unclassified environments.

Problem Statement:

USTRANSCOM seeks innovative solutions to enhance, sustain, and modernize TRAC2ES. The solution must address challenges in scalability, performance, cybersecurity, interoperability, and operational efficiency while ensuring compliance with DoW standards. Additionally, the solution must include options for transitioning TRAC2ES functionality to a secure, user-friendly mobile application to improve accessibility and operational efficiency in diverse operational environments. The solution must optimize TRAC2ES's capabilities to meet evolving mission requirements while ensuring compliance with DoW standards, including Zero Trust (ZT) principles. The solution must be deployable across UNCLASSIFIED and SECRET environments, support multi-cloud platforms (e.g., Azure, Amazon Web Services (AWS)) at impact levels 2, 4, 5 and 6, and align with agile methodologies (e.g., Continuous Integration (CI) / Continuous Deployment (CD)). USTRANSCOM is open to exploring innovative technology domains beyond the listed areas to address unknown challenges and improve operational efficiency. Solutions shall be adaptable, cost-effective, and capable of meeting DoW stakeholders’ needs within a short timeframe.

AoI Solution Attributes:

USTRANSCOM is requesting Phase I submissions for the TRAC2ES AoI. The Government's intent is to award a single contract to a Prime Contractor who demonstrates a comprehensive, integrated solution that addresses the capabilities outlined in the AoI solution attributes below. Offerors must describe how they will meet the requirements of each attribute, leveraging in-house expertise or a robust team of subcontractors.

· Implement Agile methodology for continuous improvement, defect resolution, and rapid feature deployment.

· Migrate TRAC2ES to a secure, cloud-agnostic environment using containerization and serverless computing across platforms like AWS and Azure at Impact Level (IL) 2-6.

· Establish robust CI/CD pipelines for automated builds, security scans, testing, and deployments.

· Integrate Artificial Intelligence (AI)-powered tools to enhance code quality, automate development, and accelerate delivery.

· Engineer Zero Trust Architecture (ZTA) with advanced Identity Credential and Access Management (ICAM) and micro-segmentation, aligned with DoW ZT strategy.

· Automate security compliance activities, including static code analysis, ensuring adherence to Risk Management Framework (RMF) and Security Technical Implementation Guide (STIG)s.

· Employ advanced encryption and data-centric security controls to protect PII/PHI at-rest and in-transit.

· HIPAA compliant as a Business Associate in accordance with Department of Defense Instruction (DoDI) 6025.18

· CMMC Level 2 self-assessment compliant in accordance with 32 CFR §170.16(a)(1)(ii).

· Leverage AI/ Machine Learning (ML) algorithms for optimizing patient movement, resource allocation, and operational forecasting.

· Provide scalable, Application Programming Interface (API)-first architecture for real-time data exchange with external systems, including Defense Enrollment and Eligibility Reporting System (DEERS), Mobility Enterprise Information System (MEIS), Operational Medicine Data Service (OMDS), and Advanced Analytics (ADVANA) Pegasus.

· Deliver advanced Business Intelligence (BI) tools with interactive dashboards, customizable reports, and data visualization.

· Design an architecture proven to be horizontally scalable to support 8,000 concurrent users while maintaining or exceeding 99.3% system availability.

· Develop secure, UNCLASSIFIED, user-friendly mobile applications that function effectively in disconnected, contested, and low-bandwidth Disconnected/Intermittent/Low Bandwidth (DIL) environments.

· Provide a modern, flexible training program with virtual, in-person, and on-demand content adaptive to software changes.

· Establish and operate a 24/7/365 global Tier II/III Service Desk, leveraging automation and advanced analytics to rapidly resolve user issues.

Solution Maturity:

Solutions should be sufficiently mature and may be expected to be deployed as a minimum viable product as soon as 30 days after award.

Prior Demonstration and Usage:

Companies should provide evidence demonstrating capability in relevant and/or representative environments and show experience in successfully fielding solutions into operations. White papers should annotate to what extent specifications and attributes included in the White Paper have been verified (e.g., usage in commercial environments, testing within academia, etc.).

Partnerships and teaming arrangements are encouraged.

Intellectual Property (IP):

The Government has previously obtained rights in the technical data and commercial, non-commercial software that has been delivered, furnished or provided. The Government generally expects any technical data, commercial, or non-commercial software provided to the Government under this contract, shall be consistent with the preexisting rights, unless—

(i) The parties have agreed otherwise; or

(ii) Any restrictions on the Government's rights to use, modify, reproduce, release, perform, display, or disclose the data have expired or no longer apply.

White paper and PowerPoint submission shall include the technical data and non-commercial and commercial software restrictions that will be asserted in a contract award.

Governing Guidelines and Directives:

The list of governing guidance and directives (Attachment 1) is provided as a reference to ensure offerors are aware of the relevant policies, standards, and frameworks that may inform the operational environment or implementation of their proposed solutions. While offerors are encouraged to consider these publications when developing their proposals, alignment with every listed directive is not a requirement for submission or award. The intent is to provide transparency regarding the context in which solutions may be applied, without restricting the ability to propose innovative, commercial, or non-traditional approaches.

Technical Data Package (TDP):

The TDP (Attachment 2) provides the file names within the TDP, pertaining to the technical requirements of this Call. To be granted access to the TDP, Offerors must complete, sign, and return the Non-Disclosure Agreement (NDA) TDP (Attachment 3) for each individual that will have access to this package to the Government POCs identified below. The TDP will be provided via DOD Secure Access File Exchange (SAFE).

Procedures:

Any award resulting from this CSO Call shall be in accordance with the CSO procedures detailed in TRANSCOM25CSO001. The instructions in the CSO, and any additional instruction as specified in this CSO Call posting, must be followed. The Government intends to conduct this CSO Call in two or three phases as detailed in the CSO.

Funding:

USTRANSCOM intends to award one Federal Acquisition Regulation (FAR)-based contract in Fiscal Year 2026 (FY26) under this CSO Call, with a performance period from June 1, 2026, to May 31, 2031 (12-month base period and 4 12-month option periods). The anticipated budget for this effort is $27,000,000 to $37,000,000 for the full period of performance. Award is subject to the availability of funds, and the Government reserves the right to make no award if no proposed solution meets the requirements.

Phase 1 Submissions:

The following information is being requested in response to this Call and should be emailed to the Contracting POCs.

Generic capability statements will not be evaluated and will be excluded from further award consideration. Additionally, only complete solutions addressing the Area of Interest (AoI) will be accepted; partial solutions will not be considered.

Questions:

Submit all questions via email to the Contracting POCs by the deadline. Questions and answers may be posted to SAM.gov.

Attachments:

1-Governing Guidance & Directives 2-Technical Data Package (upon request) 3-TDP Non-Disclosure Agreement