According to Global Market Insights, the global Intelligent Transportation System (ITS) market is expected to grow from USD 54.3 billion in 2026 to USD 135.3 billion by 2035, at a CAGR of 10.7%[1]. As the ITS market continues to expand, transportation applications are extending across a wider range of vehicle types and deployment scenarios, reshaping the role of in-vehicle computing.
As in-vehicle workloads expand from telematics and fleet management to real-time analytics and edge AI, transportation deployments require increasingly different levels of computing performance, connectivity, vehicle interfaces, and environmental protection. A fleet management deployment for a modern commercial truck, for example, may prioritize vehicle interfaces and connectivity. If it must also support compute-intensive workloads or operate in harsh conditions, greater computing performance and ruggedness may be required.
Such diverse requirements make a one-size-fits-all approach increasingly difficult across different vehicle types and deployment scenarios. When a single configuration does not match the workload, system integrators may need additional gateways or interface devices, increasing installation space, cabling, integration, and validation effort while making the in-vehicle architecture harder to adapt.
To move beyond a one-size-fits-all approach, DFI offers purpose-built in-vehicle platforms spanning multiple computing tiers—from vehicle data collection and fleet integration to high-performance edge AI in harsh environments. As in-vehicle applications extend into edge AI, differences in real-time processing and computing performance requirements become more pronounced, making it especially important to match each workload with the right compute. Beyond the right compute, a solution-ready platform must also provide the I/O, connectivity, expansion, and ruggedness required for each vehicle deployment. Together, these capabilities enable DFI platforms to address diverse in-vehicle application needs.
|
Model |
Challenge |
DFI Solution |
Proof Pointn |
Key Specs |
|
VC900-M8M
|
Vehicle operating and motion data often come from separate sensors or interfaces. This complicates data collection, synchronization, and cloud transmission. |
Consolidates vehicle data, motion sensing, and cloud connectivity on a single compact platform, reducing the need for separate interfaces and computing devices. |
Served as the T-Box platform for vehicle data collection and cloud communication in ARTC's Level 4 autonomous shuttle project. |
NXP i.MX8M / 1× CAN Bus / 6-axis IMU / 1× GbE / 4× COM / 2× USB 3.1 Gen1 / 1× Micro USB (OTG) / 9–36V vehicle power input with ACC/IGN / fanless operation from -20°C to 70°C
|
|
VC700-ASL
|
Vehicle data, positioning, networking, and peripheral functions are often spread across separate systems, making system connectivity and integration more difficult. |
|
Enabled existing patrol vehicles to add edge computing, positioning, connectivity, and AI capabilities in a European police fleet modernization project. |
Intel® Atom® X7000RE Series / 2× CAN 2.0B (CAN FD available upon request) / J1939 / GNSS / 2× GbE (M12 X-code) / built-in OOB remote management / 2× Mini-PCIe / 3× M.2 expansion.
|
|
VCX700-MTH
|
Edge AI and other advanced in-vehicle applications require higher computing performance, but harsh deployment environments can make it difficult for existing platforms to deliver both high performance and reliable operation. |
Combines Intel® Core™ Ultra processing with an IP67-rated fanless ruggedized design and wide-temperature operation, delivering high-performance computing with reliable operation in harsh in-vehicle environments. |
|
|
The three DFI in-vehicle systems introduced above provide computing foundations for different workloads—from telematics and fleet integration to rugged edge AI. After selecting the system that best matches the workload, system integrators can extend compatible platforms with DFI’s M.2 modules according to the vehicle interfaces and capabilities required for each application.
M2-CAN2 and M2-CANF support different scales of CAN/CAN FD integration, while M2-GNSS adds multi-constellation positioning for location- and tracking-based applications. This system-and-module approach allows system integrators to adapt the selected DFI system to specific deployment requirements by adding only the vehicle interfaces and capabilities needed for each application.
Typical Expansion Needs
Powertrain Integration: Additional CAN channels may be required to connect transmission control units, driveline sensors, and exhaust aftertreatment systems. M2-CAN2 or M2-CANF can add the required CAN/CAN FD connectivity, depending on the number of vehicle systems and CAN networks involved.
Body & Chassis Integration: Multiple CAN networks may be required to connect instrument clusters, driver displays, ADAS sensors, EBS/ABS, air suspension, TPMS, and other subsystems. For deployments involving more ECUs or CAN networks, M2-CANF adds CAN/CAN FD channels while reducing reliance on separate external interface devices.
Trailer Integration: Dedicated CAN connectivity may be required for trailer lighting, liftgate controls, trailer ABS, and cargo sensors such as temperature or door-status monitoring. M2-CAN2 or M2-CANF can add the required connectivity according to the number of trailer devices and CAN networks involved.
Vehicle Positioning & Tracking: When vehicle positioning, tracking, or route management is required, M2-GNSS adds multi-constellation positioning through a compact M.2 module supporting GPS/QZSS, GLONASS, BeiDou, and Galileo.
Combining CAN and GNSS for Advanced Fleet Operations
On compatible DFI systems with multiple M.2 expansion slots, CAN and GNSS modules can be installed simultaneously. CAN connectivity provides access to vehicle operating and status data, while GNSS adds location and movement information. Together, these data sources provide a system-level foundation for integrated fleet operations, spanning from vehicle condition monitoring and fleet tracking to route optimization and dispatch, while also supporting predictive maintenance analysis.
In-Vehicle Expansion Module Guide
|
Criteria |
M2-CAN2 |
M2-CANF |
M2-GNSS |
|
Best For |
|
|
Vehicle Positioning |
|
Capability |
2× CAN 2.0A/2.0B/FD |
4× CAN 2.0A/2.0B/FD |
|
|
Choose When |
|
|
Vehicle location / tracking is required |
|
Form Factor |
M.2 3042 B+M Key, PCIe or USB 2.0 (by SKU) |
M.2 2280 M Key, PCIe |
M.2 2230 E Key, USB 2.0 |
By combining a workload-aligned base platform with modular vehicle-interface expansion, DFI gives system integrators two levels of flexibility: selecting the right computing foundation first, then adapting it to vehicle-specific requirements. Together, these capabilities deliver four practical benefits:
DFI addresses in-vehicle deployment needs at multiple levels. Customers can select a Commercial Off-The-Shelf (COTS) platform that matches the workload and extend the required vehicle interfaces and capabilities through modular M.2 expansion. DFI also provides Design Manufacturing Service (DMS), supporting customer-specific needs from customization and system integration to validation and production. Together, these capabilities provide a deployment-ready in-vehicle computing foundation for diverse vehicle types and deployment requirements—delivering the right compute for every vehicle and flexible expansion for every deployment.