Caltrio

Home

About

Contact

CONNECT TECH INC. / PRIME-SIDE OPPORTUNITY INTELLIGENCE | Research: October 10, 2026

Forterra’s new MAUL autonomous breaching vehicle has an open architecture. Is there room for a rugged Thor vision-compute module?

Prime: Forterra. Program: Army Engineer Autonomous Breaching Capability (EABC), Mobile Autonomous Uncrewed Lanemaker (MAUL). Prospect fit: Rogue-T5 NVIDIA Jetson Thor carrier, GMSL2/3 camera platforms and rugged edge compute. Current limitation: a real prime award and integration architecture are known, but an unfilled compute subcontract is NOT.

Why this is an actionable technical question

  • Forterra’s September 9, 2026 EABC announcement confirms a U.S. Army prime award for MAUL, combining AutoDrive, TerraLink and Vektor and describing modular mission-payload integration under its OASIS fabric.
  • Forterra’s April 28 MESA announcement separately references integrated autonomy, compute, sensors and communications on its new vehicle platform, demonstrating a continuing integration focus—not evidence of a MAUL vendor vacancy.
  • Connect Tech’s Rogue-T5 combines Jetson Thor support, two 10GbE plus 2.5GbE, four CAN ports and serial/GPIO interfaces, wide temperature range and a 92 × 108 mm carrier footprint.
  • Its GMSL camera platforms are a possible basis for a compact multi-camera data path, subject to actual vehicle sensors and software integration.

Potential technical point of entry

  • Sensor data ingestion: camera I/O plus Thor computing may complement an autonomous vehicle’s perception pipeline where a rugged intermediate carrier, camera board or custom I/O is desirable.
  • Flexible payload adapters: compact CAN, Ethernet and serial connectivity could be used for rapid prototype payload swaps, but Forterra may already have a standardized computing stack.
  • Custom integration capability: Connect Tech provides carrier customization and board-support packages; this could be more compelling than a complete alternate AI stack if Forterra wants a narrowly tailored compute/sensor interface.
  • Major unknown: whether the AutoDrive/OASIS architecture permits an outside Jetson Thor module and whether the computing/subsystem selection is already finished.

Best entry points

  • Patrick Acox — VP of Defense, Forterra: named and quoted in the official September 9 MAUL announcement. A public defense-program business routing contact, not necessarily the architect who picks computing modules.
  • Forterra corporate: info@forterra.com and +1 240-631-0008 from Forterra’s official website. Request the MAUL/AutoDrive perception and vehicle-compute integration owner.
  • Forterra supplier portal: linked in the footer of its program announcement; investigate registration only after an engineering need is qualified. No current publicly verified MAUL computing-engineer direct email has been found.

Concrete steps Connect Tech could take

  • Prepare one focused integration note keyed to Rogue-T5 and available GMSL3 camera solutions: camera-channel count, 10GbE architecture, I/O pinout, 12V power, 92 × 108 mm dimensions, thermals, development kit and documented software support.
  • Ask Forterra’s defense/engineering routing contact who owns MAUL’s sensor-to-AutoDrive compute architecture and whether carrier-board or rugged multi-camera interface choices remain open in this phase or a follow-on increment.
  • If an integration issue exists, propose a short architecture-review and lab demonstration with specific perception-data and latency measurements; do not pitch an entire replacement for Forterra’s AutoDrive stack.
  • If Forterra confirms that compute and sensor interfaces are fixed, stop the current pursuit; consider a future vehicle/payload interface only if the prime identifies an actual need. AUSA can be an optional routing venue, not the opportunity itself.

Suggested first approach

Subject: MAUL / EABC sensor-compute interface question — Jetson Thor carrier integration

Hello Forterra defense team — Connect Tech builds rugged NVIDIA Jetson carrier boards and multi-camera edge systems. We reviewed your EABC/MAUL program announcement and the OASIS integration approach. We are not assuming an open hardware requirement, but would like to understand whether any multi-camera perception, rugged compute or mission payload I/O interfaces remain a technical qualification question. Could you route a concise Rogue-T5/GMSL integration note to the appropriate MAUL/AutoDrive engineering lead?

Technical qualifying questions

  • Who owns MAUL’s perception-compute hardware and camera interface choices, and what is already committed?
  • Are third-party Thor carrier boards, GMSL camera modules or custom I/O adapters allowed by the architecture?
  • What are the tested shock/vibration, thermal, power, secure boot and software/cyber restrictions?
  • Is there a formal supplier qualification, test bench or later increment route worth exploring?

Confidence, limits and sources

High confidence: recent Forterra award and named executive, Connect Tech hardware portfolio. Moderate: technical adjacency of carrier/camera integration. Unknown: unassigned hardware package, compatibility, supplier eligibility, technical contact name or addressable revenue. MAUL contract value is not an estimate of a Connect Tech opportunity.