Next Gen OCS Questionnaire 20260922.docx
DOCX document 31 KB Posted
- Solicitation number
- FA8629-26-R-5017
About this file
This file is a questionnaire designed to gather market research information from potential contractors regarding the Next Generation Operational Control System (NGOCS) capability.
The questionnaire supports the Air Force Life Cycle Management Center (AFLCMC), Intelligence, Surveillance and Reconnaissance & Special Operations Forces (ISR & SOF) Directorate's market research for NGOCS, issued by the Special Warfare Contracting Office at Wright Patterson Air Force Base. The NGOCS addresses a documented capability gap: operators currently lack a lightweight, ruggedized, modular body-worn power, data, and edge-compute architecture capable of providing distributed processing capacity beyond the End User Device (EUD). Existing fielded systems rely on aging architecture with proprietary cabling and limited processing capabilities, forcing the EUD to manage all application processing, edge-server hosting, message routing, video data links, and peripheral management simultaneously. This creates latency, power depletion, and reliability bottlenecks during high-tempo combat operations that can compromise mission success. The questionnaire is part of a pre-solicitation Sources Sought/Request for Information (RFI) effort (Solicitation Number FA8629-26-R-5017) intended for informational and market research purposes only. Respondents are instructed to clearly mark any proprietary or competition-sensitive information in their submissions. The Government will not reimburse expenses associated with response preparation, and the collected information will inform the Government's acquisition strategy, statement of work/statement of objectives, and performance specifications development.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Next Gen OCS Requirements Compliance 20260922.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment 1 Next Gen OCS Questionnaire Answer every quantitative question (MRL, production capacity, lead time, MTBF, retention force, weight, power draw, etc.) with a single numeric value or range plus unit. Do not answer in narrative only.
1. Manufacturing Readiness and Sustainment
1.1. What is the current Manufacturing Readiness Level (MRL), average monthly production capacity, and lead time (in days)?
1.2. What is the documented Mean Time Between Failures (MTBF) based on fielded operations and/or testing?
1.3. What is your End-of-Life (EOL) notification policy?
1.4. Describe any possible product improvements that could be made or are planned for the solution.
1.5. Please include product warranty terms as applicable, along with any warranty limitations. If product warranty terms are not applicable, please include N/A.
2. Software and Firmware
2.1. What operating system or real-time kernel runs on the hub and compute module?
2.2. How are firmware and security patches distributed?
2.3. What client-side drivers, services, middleware, or proprietary software licenses are required to run on the EUD to control or route data through the hub?
2.4. Provide details for testing with ATAK (version numbers, tested plug-ins, TAK Server versions, and zero-configuration capabilities). Provide any government or independent test reports.
2.5. State the current Technology Readiness Level (TRL) of the compute module and any Modular Open System Approach (MOSA), Open Mission Systems (OMS), or Future Airborne Capability Environment (FACE) Alignment.
3. Hardware
3.1. List all specific EUD cases (e.g., Juggernaut, Kagwerks) and tactical peripheral equipment (e.g., AN/PRC-152A, AN/PRC-163, AN/PRC-167, Silvus, Persistent Systems MPU5, LRFs, DAGR/GPS) verified for plug-and-play operation.
3.2. Detail all physical connector types and supported protocols per port.
3.3. Are cable interface pinouts, wiring diagrams, and communication protocols proprietary or open standard?
3.4. Can third parties manufacture compatible cables without a license?
3.5. Can third party compute devices (e.g. Nvdia Jetson, Raspberry Pi, etc) interface with this product? If so, is there an applicable interface standard?
3.6. List spare parts that would potentially be included.
4. Networking
4.1. What networking architecture does the hub provide?
4.2. Is additional software required on the EUD or OCS Hub to manage networking?
4.3. Can multiple hubs form an interconnected local wired or wireless mesh without an external host computer or router? If yes, what networking topology, IP assignment, and routing protocols are supported?
5. Human Factors and Training
5.1. Specify the retention mechanism (push-pull, breakaway, threaded) and exact retention force (in foot-pounds or Newtons) required to disconnect each cable under emergency release.
5.2. How does the hub and cabling conform to standard tactical gear (MOLLE/PALS, plate carriers, cummerbunds)?
5.3. List specific tactical gear the system has been tested on.
5.4. How is the system designed to prevent snags?
5.5. Provide the details for New Equipment Training (NET) to include the process and cost.
6. Power Management
6.1. Does the system have the ability to read and manage power across the EUD, radio batteries, and other charging sources?
6.2. Is additional software required on the EUD or OCS Hub for power management?
6.3. Can automated power management configurations be setup (ex. Begin siphoning power from the EUD if radio batteries get below 20%)?
7. Security
7.1. Does the system hold any current NIAP, Common Criteria, CSfC, or 140-3 validations? If not, what is the planned timeline and roadmap for formal certification?
7.2. Detail all internal volatile and non-volatile memory (types, capacities, purposes).
7.3. Describe Data-at-Rest (DAR) protections, physical/logical zeroization mechanisms, and secure boot verification.
File details come from the government source that posted it. Updated .