AutoTech 2027
June 22-23, 2027
Vibe Credit Union ShowplaceNovi, MI

Innovate, Integrate, Inspire: How Automakers Are Shaping the Future of Mobility

Matt Jones (Executive Director of Global Technology Platforms), Michael Ford (Director of Tech Platform for Hardware), and Santhosh Jogi (Executive Director of Software System Architecture) from Ford Motor Company delivered a candid assessment of the automotive industry's transformation challenges. The session revealed Ford's strategic pivot from hardware-centric to software-defined vehicle development, emphasizing that survival depends on fundamentally restructuring supplier relationships and accelerating development cycles from weeks to hours.

Session Summary

The Supplier Transformation Imperative

Jones opened with a provocative warning: suppliers must change or Ford's joint roadmap will fail. The company manages 33 top hats across 12 vehicle platforms, creating massive complexity that traditional supplier models cannot support. Ford's most newsworthy declaration was abandoning the quest for software ownership—instead demanding control through partnership. The company experienced production stoppages when suppliers reorganized internationally and lost code repositories, highlighting catastrophic risks in legacy supplier relationships. Ford now requires "always-on" supplier engagement, comparing the urgency to a broken water heater during Michigan winter with 180,000 employees depending on rapid fixes.

The Speed Crisis: Hours vs. Weeks

The presentation exposed a shocking disparity: Ford receives updated CAD drawings from suppliers in 2-4 hours via 30-year-old systems, while software updates take four weeks. This latency multiplies through 2.5-3 integration cycles, transforming what should be hours into months. Jones revealed that Ford's investment strategy follows a two-by-two matrix evaluating customer importance against iteration speed. High-iteration, high-importance features demand Ford control; low-iteration commodities remain with suppliers. The critical middle ground—features requiring rapid bug fixes like door modules that trigger recalls—necessitates new collaborative frameworks resembling software-era "Covent CAD exchange."

Zone Architecture Without Consolidation

Contrary to industry assumptions, Ford explicitly rejected zone controller consolidation. With hundreds of millions required to retool electrical architectures, the company prioritizes zone segregation over physical consolidation. This enables independent evolution of chassis/propulsion systems (10+ year cycles), body systems (moderate cycles), and communication/ADAS/IVI systems (annual or faster cycles). The energy management framework—generation, storage, and distribution—becomes the unifying architecture, allowing fine-grained software control over power states without rewiring vehicles for different engine combinations.

AI as Development Accelerator

Ford's AI implementation focuses on engineering productivity rather than customer-facing features. The company uses AI for knowledge repository mining, API generation from specifications, automated code wrapper creation, and comprehensive unit test framework development. Jones personally demonstrated this capability by advancing an open-source project (VISS-R) from version 3.0 to 3.2 with complete unit testing during a single Saturday afternoon—work that previously required six months. Ford developers now manage 200+ simultaneous pull requests using adversarial AI models (GitHub Copilot vs. Opus), with the lower-performing engineers handling 20-30 PRs compared to the previous 5-10 baseline.

The Integration Challenge

Ford positions itself as the perpetual integrator, never ceding master integrator status to suppliers. The company uses Linux, QNX, and Android alongside proprietary code, writing orchestration layers and applications atop this heterogeneous foundation. Jogi emphasized that software complexity dimensions "astronomically" exceed hardware complexity, requiring AI-assisted systems engineering to prevent communication breakdowns that historically caused failures. Ford's organizational structure separates software teams (by domain), hardware teams (by module), and integration/verification teams, with Santos overseeing the entire left side of the systems V-model.

Open Source Strategy

Ford clarified its pragmatic open-source stance: the company doesn't seek ownership but requires usage rights and maintenance capability. When open-source maintainers disappear, Ford maintains its own forks—no different from managing supplier bankruptcies. This approach proved superior when suppliers lost code repositories during reorganizations, while Ford's open-source components remained accessible and reproducible.

3 Key Takeaways

Supplier Relationships Must Evolve or Fail

Ford demands "always-on" supplier engagement with 2-4 hour software delivery cycles instead of four-week timelines. The company requires suppliers to integrate into Ford Software Studio environments for continuous build-integrate-test workflows, explicitly stating these capabilities are "non-negotiable" for achieving Ford's ambitions. IP remains with suppliers, but Ford demands partnership-based control for rapid iteration.

Zone Segregation Trumps Consolidation

Ford's architecture strategy prioritizes independent evolution cycles across vehicle zones rather than physical consolidation into zone controllers. By segregating chassis/propulsion (slow-changing) from body systems (moderate) and digital experiences (fast-changing), Ford can update software rapidly without hundred-million-dollar electrical architecture retooling costs, enabling different innovation speeds across the vehicle.

AI Drives 40x Engineering Productivity Gains

Ford's AI implementation transformed development speed from six-month projects to Saturday afternoon completions, with top developers managing 200+ simultaneous pull requests. This isn't about customer-facing AI features—it's about using AI as an engineering tool for code generation, testing, specification mining, and systems engineering communication, fundamentally changing how Ford competes on speed while maintaining quality and reducing complexity management costs.