360 SA RFI PM LAV w NIWC input Final v.2.docx
DOCX document 36 KB Posted
- Attached to
- Survivability Upgrade via 360-Degree Situational Awareness Camera Systems for Combat Vehicles
- Solicitation number
- LAV-26-0003
- Issued by
-
Department of the Army
About this file
This is a Request for Information (RFI) issued by the United States Marine Corps Program Manager Light Armored Vehicle (PM LAV) in conjunction with the Army Contracting Command - Detroit Arsenal (ACC-DTA) to conduct market research on 360-degree Situational Awareness (360SA) camera systems for combat vehicles. The RFI seeks fully integrated, turnkey solutions that enable crews to operate vehicles from within the hull with all hatches and doors closed during land operations, with a target cost of less than $160,000 per vehicle. Solutions must be delivered as complete end-to-end systems including cameras, displays, processing units, video distribution hardware, control modules, and software without reliance on Government-furnished subsystems. The submission deadline is June 18, 2026, at 18:00 Eastern Standard Time, with responses limited to 30 pages in PDF or Microsoft Word format and submitted to Mr. Drew Pearson (drew.j.pearson2.civ@army.mil).
Key capability requirements include 360-degree field of view with specific forward and rear ground intercepts, high-definition resolution for day and night operations, infrared or thermal imaging, four to ten vehicle-mounted cameras consolidated into a single video output, and compatibility with existing LAV turret slipring bandwidth constraints. The system must meet environmental performance standards including durability under shock and vibration, weatherproofing to IP66/IP67 standards or MIL-STD-810 compliance, operational temperature range of -25°F to +140°F, and amphibious capability. Additional requirements encompass sensor fusion capabilities, real-time latency and refresh rates, integration with MFOCS tablets and battlefield management systems, ruggedization with EMI shielding, encrypted data communication, MOPP compatibility, modular installation options, cybersecurity with system redundancy, field-maintainable components, and maritime operational capability for ship-to-shore maneuvering and low-visibility coastal conditions. Vendors must submit company information, detailed technical specifications, itemized cost estimates for hardware and installation, performance test data, and evidence of commerciality and prior deployment history. This RFI is for informational purposes only and does not commit the Government to any contractual agreement.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 360 SA RFI PM LAV w NIWC input Final v.2.pdf |
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
REQUEST FOR INFORMATION (RFI)
PROGRAM OFFICE: Program Manager Light Armored Vehicles (PM LAV) SUBJECT: Survivability Upgrade via 360-Degree Situational Awareness Camera Systems for Combat Vehicles
1. INTRODUCTION
The United States Marine Corps (USMC), Program Manager, Light Armored Vehicle (PM LAV), with the assistance of the Army Contracting Command – Detroit Arsenal (ACC-DTA), is issuing this notice as a means of conducting market research. The goal is to better understand the availability of technology that supports enhancing platform survivability through the integration of 360-degree Situational Awareness (360SA) systems.
PM LAV is seeking fully integrated, turnkey 360SA systems that provide complete situational awareness and enable crews to operate the vehicle from within the hull with all hatches and doors closed on land (in swim operations or in water hatches are open). Solutions must be delivered as complete, end‑to‑end systems, including all required cameras, displays, processing units, video distribution hardware, control modules, software, and any other components necessary to provide a functional, cohesive capability without reliance on Government‑furnished subsystems. Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): While operating on land. In water, they operate with hatches open. The only hatch closed is the drivers. Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): Thanks changed This survivability upgrade is intended to significantly enhance LAV platform effectiveness at a target cost of less than $160K per vehicle, while improving crew protection, threat detection, and operational agility. Vendors should ensure proposed solutions represent a fully assembled, integrated, and operational system, not a collection of standalone components.
2. REQUESTED INFORMATION
Interested vendors are requested to submit detailed information on their 360SA camera systems, addressing the following key capability areas:
A. Core Camera Capabilities
1. 360-Degree Field of View (FOV):
· Full panoramic coverage with adjustable angles of regard and real-time viewing from all sides of the vehicle.
· Ground intercept visibility in front, rear, and sides to support closed-hatch operations.
· The SA System shall provide a total combined FOV of 360 degrees.
· Specific FOV requirements include:
· Forward FOV: 90° and 105° from centerline with ground intercepts at 10 m and 1 m respectively
· Rear FOV: 100° and 114° from centerline with ground intercepts at 1 m and 0.1 m respectively
2. Resolution & Image Quality: High-definition resolution (e.g., 1080p, 4K) for day and night clarity.
3. Low-Light Performance: Infrared or thermal imaging capabilities for night operations, obscurants, or low-visibility conditions.
4. Zoom Capability: Ability to toggle between wide and narrow views for threat verification.
5. Color Accuracy: Reliable color representation for maneuvering, local security, and identification of personnel, obstructions, and obstacles.
6. Camera Stitching:
· The 360SA solution shall ingest video from no fewer than four (4) and up to ten (10) vehicle‑mounted cameras and provide a single, consolidated to a single video output suitable for transmission through the turret slip ring or designated pass‑through port. Acceptable connections include fiber, ethernet, CAN Interface, and Twinax (but only 75 Ohm Coax to 100 Ohm twisted pair) and compatible video feeds or connections. Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): We need to have a mtg with PM-TCE, NIWC-A and lay down the requirement for the slip ring pertaining to 360sa and MARNAV. Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): Agree but doesn't change what we are looking for, they could also come back and state they could do this via Bluetooth or Secure Wifi. Thought Kim was driving the meeting to discuss this, if not we can drive
· The system shall include all necessary hardware, software, encoding/decoding modules, video processors, and network interfaces required to:
· Aggregate, encode, and/or compress multiple camera feeds into a unified digital video stream
· Ensure compatibility with existing LAV turret slip‑ring bandwidth and interface constraints
· Maintain synchronized, low‑latency situational awareness for the crew
· Operate as a fully integrated subsystem, requiring no Government‑furnished video components or additional integration work
· The vendor’s solution must deliver a complete, turnkey video‑processing architecture, including all cameras, displays, processors, control modules, cabling, and any other components required to provide a functional end‑to‑end capability.
B. Environmental Performance
1. Durability: Shock and vibration resistance for rough combat conditions.
2. Weatherproofing: IP-rated protection against dust, water, and extreme temperatures. Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): Immersion? MIL-STD 810 Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): Jon this would be the common MIL STD for this but if it meets IP66, IP 67 these are baseline standards that could be acceptable so we left it open, if they state MIL -STD 810 that covers the entire gambit shock, vib, weather etc, where IP standard could also meet most environmental especially for rain, submersion, etc.. Just leaving it more open .
3. Temperature Range: Operational capability from -25°F to +140°F.
4. Weather Resistance: Continued functionality in extreme temperatures, rain, snow, and sand/dust storms.
5. Amphibious Capability: Waterproofing suitable for amphibious vehicle integration.
6. Adaptability: Adjustable settings for urban combat, open terrain, and jungle operations.
C. Sensor & Processing Features
1. Threat Detection: Describe any onboard threat detection capabilities that enhance 360SA.
2. Sensor Fusion: Capabilities integrating EO/IR, radar, LiDAR, or other sensors to support comprehensive 360SA.
3. Latency & Refresh Rate: Must support real-time situational awareness for driving, swimming, and navigating.
D. Integration with Vehicle Systems
1. Compatibility: Integration with displays, turrets, fire control, and crew stations to support 360SA. Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): We have no monitors except the MFOCS tablet. The M242 doesn’t have any external feeds. Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): Above state end to end solution cameras, displays etc If they have open standards that is a data point for transition to ARV. Just want to understand what they can and cannot do.
2. Control Interface: Operator-friendly interfaces for monitoring and controlling 360SA views.
3. Power Supply: Must operate during silent watch or engine-off conditions to maintain 360SA.
4. Data Networking: Encrypted communication and interoperability with battlefield management systems. Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): MFOCS? Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): Could also be an open TAK ecosystem to other C2 systems, or if they have any connectivity to other data networks for transport. Wifi, LEO, IP based netowrk etc.. Future requirement to ARV E. Survivability in Combat
1. Ruggedization: Must maintain 360SA functionality under vibration, impact, and shock.
2. EMI Shielding: Protection against electromagnetic disturbances that could disrupt 360SA feeds.
3. Low Observability: Minimized RF or heat signatures to avoid detection while maintaining 360SA.
4. Battle Damage Resilience: Ability to retain partial 360SA functionality after damage.
F. Display & Accessibility
1. Operator Interface: Clear and intuitive interface for accessing 360SA views.
2. MOPP Compatibility: Operable by personnel in protective gear while maintaining full 360SA functionality.
3. Human Factors & Ergonomics:
· Rapid decision-making under stress using 360SA views
· Accessibility across crew stations
4. The system shall be capable of providing real-time video and control to a display(s) using industry standard video and control input/output.
G. Size, Weight, and Installation
1. Compact Form Factor: Must not obstruct 360SA camera placement or crew ingress/egress.
2. Ease of Installation: Modular components supporting flexible 360SA deployment.
3. Mounting Options: Turrets, sides, or roofs to optimize 360SA coverage.
4. Center of Gravity Impact: Describe any effect on vehicle dynamics due to 360SA system installation.
H. Safety & Cybersecurity
1. Data Protection: Encryption for data storage and transmission (if applicable).
2. System Redundancy: Backup systems to maintain functionality during failures.
3. Tamper Detection: Ability to detect unauthorized access or physical tampering.
I. Maintenance and Logistics
1. Ease of Maintenance: Field-repairable components and streamlined procedures. Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): Remove/Replace...PAOZZ Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): Doesn’t that imply remove and replace or the intent is for them to tell us how they expect to maintain
2. Lifecycle Costs: Long-term costs for spare parts, upgrades, and training.
3. Diagnostic Tools: Built-in self-diagnostic systems for remote troubleshooting.
4. Training Requirements: Describe operator and maintainer training needs.
J. Legal and Regulatory Compliance
1. Regulatory Standards: Adherence to military specifications (e.g., MIL-STD-810G/H).
2. Interoperability: Compatibility with allied forces’ systems and platforms.
3. Exportability: Indicate any ITAR or export restrictions.
K. Vendor-Specific Information
1. Technical Documentation: Specification sheets, certifications, and manuals.
2. Deployment History: Evidence of current deployments and performance.
3. Customization Options: Ability to tailor solutions to mission-specific needs.
4. Lead Time & Production Capacity: Estimated delivery timelines and scalability.
L. Maritime Operational Capability
| Vendors shall describe how their 360SA systems support operations in maritime and littoral environments, including during swimming operations, ship-to-shore maneuvering, and low-visibility coastal conditions. Systems must demonstrate suitability for integration on amphibious platforms such as the LAV, ARV, and ACV. | Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): Ship to shore and vice versa | Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): changed |
| Key capability areas include: | Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): Ask what technical readiness ie: TR 9 |
1. Environmental Hardening
a) Resistance to saltwater corrosion, humidity, and marine-grade vibration
b) Operational reliability in surf zones, splash conditions, and wet-deck environments
c) Compliance with amphibious vehicle standards for shock, thermal, and waterproofing
2. Sensor Placement & Field of View
· Optimized sensor layout for low-profile hulls and swimming posture
· Full situational coverage while submerged or partially submerged
· Ability to maintain visibility during wave impact, spray, and hatch-closed operations
3. Ocean Condition Awareness Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): When waterborne, they operate with hatches open w/PFD’s so they can egress. The LAV has no radar. SS, wave periodicity, set and drift, visibility are human observations. We need to talk with MGySgt on the ops. Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): Jon this is fishing a bit, but ACV had it in their RFI, we are gauging what if any Maritime operations they have applied their solution too.
· Detection and classification of surface vessels, navigation lights, and day shapes for collision avoidance
· Real-time tracking and ranging of contacts in fog, surf, and low-light conditions
· Fusion of EO/IR tracks with radar inputs for enhanced target confirmation
· Capability to assess sea state, wave patterns, and visibility conditions that may affect swimming performance or navigation
4. System Interoperability Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): Lav-25 doesn’t have a TAK requirement Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): LAR Bns have MCHH and MAGTAB those both have A-TAK on them for this purpose, but also lets us know if there are potential transition to ARV that we can considered
· Integration with TAK-based C2 systems, onboard mission computing, and USMC digital architecture
· Compatibility with autonomous navigation aids, if applicable
5. Operational Use Case Alignment
· Evidence of prior deployment or testing in maritime or amphibious environments
· Ability to support closed-hatch operations during land movement Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): Not IAW Operation manual Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): Changed
· Support for crew decision-making in dynamic coastal threat environments
3. SUBMISSION REQUIREMENTS
Interested vendors should provide:
1. Company Information: Name, contact details, and relevant experience.
2. Technical Information: Detailed descriptions of system features and compliance.
3. Cost Estimates: Itemized costs for hardware, installation, maintenance, and upgrades of the end to end solution. (Cameras, Displays, and other video components (what acquisition paths to purchases exists if any)
4. Test Data: Performance data, test results, and operational case studies.
5. Commerciality: Identify if a commercial solution is currently available.
6. Additional Documentation: Any other relevant information.
| 4. RESPONSE INSTRUCTIONS | Comment by Wiedemann, Jon W CIV USARMY TACOM (USA): Ask what technical readiness ie: TR 9 | Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): The section above outlines the operational fielding , which will indicate the TRL level. If the system is not at an operational but its TRL 6/7, they will tell us, and we can request a plan to increase the TRL. If we specifically ask for TRL 9, I suspect GVSC systems may not be able to meet that requirement.so on this one, choosing not to specifically ask. |
| · Submission Deadline: 18 June 2026, 18:00 eastern standard time | Comment by Bowmer, Billie L CIV USARMY ACC (USA): Update before posting | Comment by VanBuskirk, Richard J CIV USARMY TACOM (USA): Would like 2 weeks if possible |
· Point of Contact: Mr. Drew Pearson – Contract Specialist Email: drew.j.pearson2.civ@army.mil
· Submission Format: All responses must be unclassified. Electronic submissions are required in PDF or Microsoft Word format but must be in one combined document and no longer than 30 pages. Do not submit responses via SAM.gov. All electronic responses and questions for clarification shall be sent to Mr. Pearson at the email above.
· Confidentiality: All information will be used for internal research purposes only and will not be shared outside of authorized personnel.
5. DISCLAIMER
This RFI is issued for informational purposes only. The information in this notice is subject to change and does not commit the Government to any contractual agreement. Respondents WILL NOT be notified regarding information obtained related to this RFI. The Government will not award a contract based upon responses to this RFI. The Government shall not reimburse or pay any costs for preparing or submitting information in response to this notice. Any information submitted by respondents is strictly voluntary and does not obligate PM LAV, USMC, or ACC-DTA to issue any future contracts or purchases.
File details come from the government source that posted it. Updated .