Background
The Product Manager Tactical Training System (PdM TTS) is responsible for supporting ranges that utilize the TRACR II software. An emerging requirement includes the integration of Group 1 UAS training into these existing ranges. This Request for Information (RFI) aims to gauge industry interest and understanding of the Interface Control Document (ICD) to ensure a common communications interface is established. The Government team is developing a software compliance test tool to validate conformity, which will be released to respondents later.
Work Details
PdM TTS seeks proposals from vendors outlining their plan and methodology to demonstrate that their drone solution can successfully integrate with and operate according to the specifications within the UAS TRACR II ICD. Proposals should include:
- Implementation Plan: A high-level plan for implementing UAS TRACR II ICD communication protocols on existing UAS platforms.
- Testing and Validation Methodology: A comprehensive description of testing procedures, simulation environments, and/or physical tests used to verify compliance with the ICD.
- Verification of Message Handling: Demonstrating correct parsing, processing, and generation of relevant messages defined in the ICD, including command and control messages and status telemetry.
- Behavioral Compliance: Validating that the UAS exhibits correct behaviors in response to commands such as path execution, landing protocols, and handling acknowledgments and fault conditions.
- Network Communication: Ability to communicate over IP-based networks, handling point-to-point and point-to-multipoint messages.
- Message Processing: Correct implementation of message headers and processing various message types, including acknowledgment logic.
- Control States: Demonstration of managing transitions between control states (No Control, Pilot Control, Central Control) as defined in the ICD.
- Command Execution: Correctly receiving, acknowledging, and executing key command messages.
- Required Hardware: Listing all hardware required beyond the UAS needed for communication with the TRACR II Computer.
Place of Performance
Orlando FL 32826 UNITED STATES
Bidder Requirements
Respondents must provide administrative information including Company Name, CAGE Code, UEI Number, Point of Contact details (Name, Phone, Email). Additionally, a brief summary of experience implementing similar cross-network data transfer solutions in DoD or highly regulated environments is required.
Incumbent Analysis (see Incumbents section for more detail)
This opportunity appears to have a confirmed incumbent and/or closely related prior contract based on Riptide Software’s award for “TARGETRY RANGE AUTOMATED CONTROL AND RECORDING (TRACR II) SUITES” covering multiple locations (Hawaii, Alaska, North Carolina, and Germany) under W900KK20D0004-W900KK25FA135 valued at $2,859,539. The current RFI focuses on demonstrating Group 1 UAS compliance with the UAS TRACR II Interface Control Document, including implementing and validating the ICD’s command/control messaging, telemetry, network communication, and control-state behaviors—capabilities that align with delivering and integrating TRACR II range control/recording functionality.
PURPOSE: Product Manager Tactical Training System (PdM TTS) is requesting information from interested offerors regarding Group 1 UAS compliance with the TRACR II ICD
BACKGROUND: PdM TTS is responsible for supporting ranges that utilize the TRACR II software. An emerging requirement includes integration of Group 1 UAS training into these existing ranges. This RFI is intended to gauge industry interest and understanding of the ICD to ensure a common communications interface is established. Please note that the Government team is currently developing a software compliance test tool to validate conformity. This will be released to respondents at a later date.
REQUEST FOR INFORMATION (Technical): PDM TTS is seeking proposals from vendors outlining their plan and methodology to demonstrate that their drone solution can successfully integrate with and operate according to the specifications within the UAS TRACR II ICD. The proposal should clearly describe the approach for implementing and validating the required interfaces and behaviors.
Respondents should describe their proposed validation strategy, including but not limited to:
Implementation Plan: A high-level plan for implementing the UAS TRACR II ICD communication protocols on existing UAS platforms.
Testing and Validation Methodology: A comprehensive description of the testing procedures, simulation environments, and/or physical tests that would be used to verify full compliance with the ICD. This should cover all applicable messages and behaviors.
Verification of Message Handling: The approach to demonstrate correct parsing, processing, and generation of all relevant messages defined in the ICD, including command and control messages, and status telemetry.
Behavioral Compliance: The methodology to validate that the UAS exhibits the correct behaviors in response to commands, such as path execution, landing protocols, and handling of acknowledgements and fault conditions.
Network Communication: Ability to communicate over IP-based networks, handling point-to-point and point-to-multipoint messages, and correctly interpreting network endpoint data.
Message Processing: Correct implementation of the message header and processing of various message types, including acknowledgment logic and handling of message sequencing.
Control States: Demonstration of the UAS correctly managing and transitioning between control states (No Control, Pilot Control, Central Control) as defined in the ICD.
Command Execution: The ability to correctly receive, acknowledge, and execute key command messages.
Required Hardware: List all hardware required beyond the UAS needed to communicate with the TRACR II Computer (including radios, ground station, etc.).
Additionally, respondents are encouraged to comment on any portions of the ICD that are not clear, and to propose any changes that would make implementation more robust.
COMPANY PROFILE: To assist the Government in determining if this can be set aside for small businesses, please provide the following administrative information:
Company Name, CAGE Code, and UEI Number.
Point of Contact (Name, Phone, Email).
Business Size Standard and Socio-Economic Status (e.g., Small Business, 8(a), HUBZone, SDVOSB, WOSB) under NAICS Code: 541512 for Computer Systems Design or 541511 for Custom Computer Programming).
A brief summary of your company's experience implementing similar cross-network data transfer solutions in DoD or highly regulated environments.
SUBMISSION INSTRUCTIONS: The Government is exploring a range of acquisition strategies and plans to utilize the information gained from this White Paper to help further shape the acquisition strategy. Responses should be limited to a five (5) page max white paper, not including cover page, cover letter, table of contents and any other documentation submitted in response to Past Performance. Any proprietary concepts of information should be clearly identified as such. Submitted data and information will not be returned. Any information submitted in response to this RFI Notice is strictly voluntary. This notice is for information and planning purposes. The Government will not pay or otherwise reimburse respondents for information submitted. Industry is encouraged to suggest alternative NAICS codes that may better align with the requirements.
All correspondence and questions regarding this notice shall be directed to the Contracting Office POC and Program Office POC listed below:
POINT OF CONTACT INFORMATION:
Contracts POC: Reuel Dunn: reuel.p.dunn.civ@army.mil, 520-714-5529
Program POC: James Efantis: james.efantis2.civ@army.mil, 407-284-7334
Disclaimer: This notice does not constitute an invitation for bids or a request for proposal and is not a commitment by the U.S. Government to procure subject products or services nor will the Government reimburse any parties for costs associated with this request. The Government will use the information received to forge its acquisition strategy. Additionally, all submissions become Government property and will not be returned. No basis for a claim against the Government shall arise as a result from a response to this RFI.
