INERTIAL LABS / PRIME OPPORTUNITY INTELLIGENCE | October 9, 2026

Forterra’s new autonomous breaching system needs reliable navigation. Is its inertial sensor stack fully committed?

Thesis: Forterra announced a September 9, 2026 U.S. Army Engineer Autonomous Breaching Capability (EABC) award to supply its Mobile Autonomous Uncrewed Lanemaker (MAUL), integrating AutoDrive, TerraLink and Vektor. Inertial Labs can qualify whether CheetahNAV / INS-P / INS-DM modules might support vehicle localization, heading, or fallback in GPS-challenged environments. The existing navigation suppliers and architecture have NOT been established; no open subcontract is confirmed.

Verified program movement

  • Forterra’s Sept. 9 EABC announcement identifies Forterra as prime, its MAUL vehicle and the integration of AutoDrive, TerraLink and Vektor; this is an active autonomous engineering program.
  • Forterra’s July 31 Sandhills contract announcement provides corroborating operational work on autonomous breaching and terrain-shaping; this is a separate award, not proof of a MAUL sensor need.
  • Inertial Labs INS catalog lists INS-B/P/D/D-M for land vehicles and UGVs. The vendor describes sensor-fusion and extended navigation through GNSS degradation; actual performance is application dependent.
  • CheetahNAV tactical vehicle datasheet details a tactical GNSS-aided INS with moving map and dead reckoning; this is a candidate comparison, not proof Forterra needs crew displays.

Why Inertial Labs might fit

  • INS-P / INS-DM: potential inertial/heading input to Forterra’s vehicle state estimator where GNSS is unreliable, if the software architecture accepts third-party sensor feeds.
  • Rugged vehicle installation: sealed enclosures and low-SWaP OEM options could help within payload, power or environmental constraints, subject to genuine specifications.
  • CheetahNAV: may be less suitable as an entire parallel navigation unit if Forterra owns its core autonomy stack; focus first on sensor data/interfaces, not a replacement vehicle display.

Best entry routes

  • Forterra corporate business/engineering routing: info@forterra.com or +1 240-631-0008, published on Forterra’s own website. Ask for the MAUL/EABC autonomous vehicle localization and inertial-sensor integration lead, not a generic purchasing inquiry.
  • Josh Araujo — Forterra CEO: identified in a Forterra partner announcement. This confirms company leadership, not MAUL navigation design authority; use the published general channel first.
  • Specific MAUL sensor-selection lead: no current directly verified individual or published direct email was found. The immediate opportunity is to obtain that person’s business contact through official routing.

A useful partner approach

  • Send a one-page autonomous-vehicle INS comparison showing INS-P/INS-DM interface protocols, heading/inertial outputs, measured GNSS-outage drift, power, update rate and rugged qualifications. Acknowledge that vehicle-specific performance is not yet proven.
  • Ask Forterra’s MAUL technical integration team whether inertial/GNSS/alternative localization hardware has already been selected, and what aspects may remain open across MAUL or follow-on prototype iterations.
  • If an interface gap exists, propose a short localization architecture and data-timing review, followed by a limited GNSS-interruption integration test using a documented Inertial Labs model.
  • Do not pitch the full CheetahNAV moving-map package unless Forterra specifically needs an auxiliary crew navigation system; do not assume EABC supplier selections are open.

Suggested introduction

Subject: MAUL / EABC — GNSS-contested vehicle localization interface question

Hello Forterra team — Inertial Labs supplies rugged inertial navigation and heading modules for tactical and autonomous land vehicles. We reviewed Forterra’s MAUL/EABC announcement. We’re not assuming you have an open requirement, but would like to learn whether vehicle state estimation or alternative inertial sensing remains an evaluation question. Could you route a focused sensor/interface summary to the MAUL localization or autonomy-integration lead?

Technical qualification questions

  • Who currently supplies vehicle inertial sensors and owns AutoDrive localization fusion?
  • Does MAUL need a standalone INS, raw IMU, wheel-odometry aided heading or an entirely different positioning architecture?
  • Which latency, timestamp synchronization, environmental, power and anti-spoofing tests govern possible external modules?
  • Is a future engineering test or second-source evaluation legitimately available?

Risks / confidence and source ledger

High: dated Forterra prime award and manufacturer-published INS capabilities. Moderate: generic fit of inertial sensing to autonomous off-road vehicle localization. Low/unknown: unsourced navigation subsystem, sensor vendor selection, accepted interfaces and opportunity value. Avoid implying that Forterra asked for sensor suppliers.