Vector and Jungheinrich develop common forklift platform

Vector and Jungheinrich develop common forklift platform

Jungheinrich and Vector are developing shared software for future forklifts. The electronics platform combines a common vehicle architecture, embedded software, and cloud connectivity, with no production launch timetable yet confirmed.


IN Brief:

  • Jungheinrich and Vector are jointly developing an electronics and embedded software platform for future connected forklift trucks.
  • The architecture covers vehicle communications, diagnostics, configuration, cybersecurity, functional safety, and over-the-air updates.
  • No first production vehicle, commercial deployment date, or measured operating improvement has been confirmed.

Jungheinrich and Vector are jointly developing a common electronics and software architecture intended for future generations of connected forklift trucks. The German partners are combining vehicle electrical and electronic systems, reusable embedded software, and cloud services to replace separate product-specific arrangements with a shared technical foundation.

The platform will connect vehicle components through a central control unit and support functions that can be developed and maintained across different forklift types and generations. Its technical scope includes communications, diagnostics, software updates, configuration management, functional safety, cybersecurity, and vehicle variant management. The companies have not identified a first production truck using the platform or supplied a timetable for commercial deployment.

Jungheinrich intends to reduce the repeated engineering work involved in introducing functions across different forklift families. Product-specific electronic controllers and software arrangements can require separate integration and validation whenever a feature is updated. A reusable foundation offers scope to share appropriate code and development tools, while retaining vehicle-specific checks for lifting capacity, actuators, drive systems, and safety behaviour. Neither company has published a measured reduction in development time.

In conventional industrial vehicle architectures, functions are distributed among electronic control units responsible for particular subsystems. Coordination between units depends on agreed data exchange and timing, while any change can have consequences for the broader control system. Jungheinrich and Vector are pursuing a more standardised arrangement around connected components and a central control unit. They have not published a complete wiring topology, controller specification, processor selection, or communication protocol list.

The programme uses Vector’s MICROSAR-based embedded software alongside architecture work, systems integration, virtual development environments, and testing technology. MICROSAR supplies software building blocks for embedded control systems, but the release does not specify the exact components selected for each forklift application. The collaboration also covers continuous integration and continuous delivery pipelines, intended to make software development and validation repeatable as the platform evolves.

Forklift electronics govern physical equipment that lifts, transports, and positions heavy loads close to workers and other machinery. Software changes affecting movement, braking, lifting, or alarms must therefore be assessed against applicable functional safety requirements and the specific vehicle configuration. The partners have identified functional safety and cybersecurity as separate platform domains, alongside diagnostics and configuration control; they have not announced platform-wide certification or an independently validated safety performance result.

Continuous cloud connectivity is intended to support remote diagnostics, fleet management, operational data collection, and over-the-air software updates. The companies have not announced a customer fleet already using these functions through the new platform. Remote updates must also operate within the safety and cybersecurity controls applicable to each truck; the announcement does not establish unrestricted changes to safety-critical vehicle behaviour or a particular remote maintenance schedule.

Remote diagnostics would depend on the availability of relevant machine signals, permissions to access them, and communications between the truck and the backend. Fleet management would add another software layer for organising information across multiple vehicles, potentially including different models and production generations. The release does not disclose a subscription model, connectivity coverage, cybersecurity certification, or a defined set of operational performance indicators.

Dr Stephan Lange, vice-president of electrics and electronics at Jungheinrich, described the design as providing “a common technology foundation on which we can develop vehicle functions faster”. His account presents the platform as an engineering basis for future functions, not evidence that every truck already operates on it. Engineers from both companies are working together to connect vehicle architecture, embedded control software, testing, and cloud systems.

Vector is contributing expertise across the development process, including platform architecture, integration, virtual testing, deployment workflows, and related engineering services. Dr Matthias Traub, its managing director and chief technology officer, characterised the objective as “connecting the necessary building blocks across system boundaries”. The breadth of the arrangement means the project covers both the control software installed on vehicles and the systems used to develop and maintain it.

Across a fleet containing different lifting capacities, battery configurations, chassis layouts, and operating environments, software reuse depends on explicit variant management. A common component might work on several models while its parameters, interfaces, or safety limits differ. Version tracking and configuration controls are therefore as important as code sharing when a manufacturer plans to maintain functionality across successive generations. The joint project names variant management as a core domain but gives no details of the initial vehicle configurations.

Development and verification will remain significant work. Reusing a software component does not remove the need to validate its behaviour on each relevant vehicle type, especially where machinery safety or interaction with physical actuators is concerned. The announced use of virtual development environments and CI/CD processes indicates how the partners plan to handle repeated development cycles, but no independent benchmark has yet quantified the time or cost they will save.

The collaboration establishes a common platform development programme rather than the launch of a finished forklift model or a fleet software service. Jungheinrich has yet to name the first compatible truck, a production timetable, commercial terms, or independent performance measurements. Those decisions will determine which diagnostics, update functions, and maintenance capabilities become available to operators and across which vehicle generations.


Stories for you


  • Gulf–China supertanker benchmark drops roughly 64%

    Gulf–China supertanker benchmark drops roughly 64%

    Gulf-to-China supertanker freight assessments have fallen sharply since October’s peak. Reuters cites about WS308 for 13 November, while the Baltic Exchange’s Week 46 report records WS310.71 for the same route; both show a roughly 64% retreat from October.


  • PepsiCo reveals uneven deforestation-free sourcing results

    PepsiCo reveals uneven deforestation-free sourcing results

    PepsiCo reports uneven results across five forest-risk agricultural commodity groups. Its 2025 deforestation-free sourcing figure was 94% for covered company-operated activities, against 59% for cocoa and 77% for palm oil.