In-house Automotive Global Company newsroom

ZF

Document Processing · IT Operations Automation

ZF needed to shorten development cycles, analyze large volumes of customer requirements, speed testing and validation, and estimate operating parameters that cannot be physically measured in products such as electric motors.

Reported impact

Business outcome

ZF says AI helps redesign and optimize products and development processes, shortens development cycles, enables faster and more reliable project estimation, and makes validation work cheaper and more efficient.

  • Cost Reduction
  • Productivity Improvement
  • Speed to Market

Solution

ZF uses in-house AI across its engineering lifecycle rather than in a single standalone app. A pilot run by the AI Tech Center ingests customer requests and requirement specifications, analyzes them for recurring or similar requirements, and surfaces related code, test specifications and tools so engineers in different divisions can reuse prior work and estimate new projects faster. In later development stages, AI methods are applied to simulation, testing and validation: AI agents orchestrate validation workflows, while machine-learning models act as non-linear approximators when enough data is available. ZF also combines hardware tests with AI evaluation to create Virtual Sensors that infer temperatures, speeds and positions that cannot be measured directly, and the cubiX control software uses machine learning for predictive trajectory control in chassis dynamics. The source does not name an external platform or dedicated data store; prior specs, code and measurement data are the working information base served back to developers and control functions.

Data flow

ZF feeds customer requests and requirement specifications into an internal AI pilot that detects recurring requirements and retrieves related code, test specifications and tools for engineers across divisions. In validation use cases, hardware-test measurements and simulation inputs are processed by ML models and AI agents to estimate hard-to-measure states and orchestrate validation; outputs are then consumed by developers and by control software such as cubiX.

Solution architecture

3 components · 3 layers
  1. Compute
    • Virtual Sensors Machine-learning capability that combines hardware tests and AI evaluation to infer temperatures, speeds and positions that cannot be measured directly.
  2. Serving
    • cubiX Chassis control software that applies machine learning to predictive trajectory control for AD and ADAS vehicle dynamics functions.
  3. Orchestration
    • AI Tech Center Central ZF AI team that runs the requirements-analysis pilot and supports divisions with AI use cases across development.

Architecture clues

  • AI agents are used to orchestrate validation of product designs.
  • The AI Tech Center is anchored within Corporate Research and Development in Friedrichshafen.
  • The requirements-analysis use case is described as an internal pilot project used across a globally active group.
  • Virtual sensor models combine hardware testing with AI evaluation to infer unmeasurable motor and drivetrain states.
  • cubiX applies machine learning inside chassis control and predictive trajectory control workflows.

Evidence from the source

"AI agents can orchestrate the validation of product designs and reduce development time as well."
"AI is of strategic importance for ZF because it helps us to redesign and optimize our products and development processes and develop more efficiently"
"Developers gain access to code, test specifications and other tools that can also be utilized for the new project – even if it's just to make the estimates faster and more reliable"
"Thanks to machine learning, the combination of hardware testing and AI evaluation, ZF developers can also obtain this information"
"The cubiX developers also use machine learning methods for this."
"There is an internal pilot project for this purpose. It identifies recurring or similar requirements in customer requests."
Transparency Evidence & methodology 70/100 reference value · 92% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value70/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence92%
  • Source authority25/25
    The deployment is described by the adopting organization or a government source.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. ZF

    ZF customer story

    First-party
    https://www.zf.com/mobile/en/technologies/artificial_intelligence/stories/ai_at_zf.html
    Source type
    Customer-published story
    Published
    Aug 26, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.