Skip to content

Check: Volkswagen case and ROI arithmetic

Knowledge check · self-test

Check: Volkswagen case and ROI arithmetic

Review the original Volkswagen case and ROI arithmetic checkpoints.

Back to the chapter →

Review the original Volkswagen case and ROI arithmetic checkpoints.

::: {.callout-tip} ## Ada, Applications and calculation-audit guideCheckpoint: Volkswagen Case {.depth-l0} You now know why the Volkswagen case depends on workflow trust: - The factory context starts with 7,500 robots, 30,000 sensors, and 85TB/day of raw data. - In this hypothetical plant model, edge processing reduces transmitted bytes by 99.8% while the design targets alerts below 10 ms. - In this hypothetical adoption model, false-positive rate falls from 18% to below 5% as fusion-model accuracy reaches 87%; measure actual user response separately. ::: ::: {.callout-tip} ## Ada, Applications and calculation-audit guideCheckpoint: ROI Arithmetic {.depth-l0} You now know which numbers make predictive maintenance persuasive: - In the hypothetical $23M/$47M model, simple payback is 5.9 months; its savings inputs still require reconciliation. - At $1.3M/hour, preventing just 18 hours of unplanned downtime annually can pay for the system. - The five-year view compares $235M in savings against $23M investment for about 921.7% ROI. :::

Back to Lessons from Real Deployments: Volkswagen Predictive Maintenance and Cross-Case Lessons: Judge the Maintenance Claim at One Machine