Industrial IoT and Business Operations · Study deck
Lessons from Real Deployments: Volkswagen Predictive Maintenance and Cross-Case Lessons
The maintenance lead wants early warning, but a false stop wastes production and a missed fault can damage the line.
Ada is your guide for this deck.

After studying this chapter
Learning objectives
You will be able to:
- explain Volkswagen's predictive-maintenance deployment path from pilot to plant-wide rollout
- evaluate why edge processing and multi-sensor fusion changed industrial alert performance
- recompute the payback and ROI logic behind the Volkswagen case
- compare Volkswagen and Barcelona case evidence using the six-phase deployment framework
Major section
VW Maintenance Prediction
The maintenance lead wants early warning, but a false stop wastes production and a missed fault can damage the line.
- The useful case is not the size of the factory.
- A strong return in one line or machine does not prove the same return everywhere.
- Under the Hood explains signal features, model checks, drift, placement, and why the wider Volkswagen numbers are context rather than proof for a new site.
Major section
Volkswagen Solution Architecture
The following 320-gateway, 85-TB/day automotive architecture is an illustrative design, not a reported deployment.
- The 320 edge gateways then do the work that makes the design affordable: they extract frequency features and run inference locally every 100 milliseconds, so only anomalies and summary statistics travel upward.
Major section
Volkswagen Lessons Learned
Edge Computing is Essential for Industrial IoT.
- Sending 85 TB/day of raw data would require about 7.9 Gbit/s sustained throughput before overhead; compare the provisioned uplink, latency and cloud costs with edge processing.
- Lesson: Process data at the edge; cloud is for training models and historical analysis.
- Sensor Fusion Dramatically Improves Accuracy.
- Retrofit Challenges Require Creativity.
Major section
Volkswagen Lessons Learned (continued)
Different failure modes have different signatures.
- Lesson: Establish data labeling processes early; engage technicians in recording failure modes.
- "Boy who cried wolf" effect: Three false alarms and technicians stop responding.
- Lesson: Optimize for minimizing false positives; user trust is fragile.
- Integration with Existing Systems is Critical.
Major section
Enterprise IoT Pitfalls
Many IoT budgets omit integration effort; list hardware, software, integration and change-management costs separately for the proposed deployment.
- Pitfall 1: Technology-First Thinking: Teams select sensors and platforms before understanding the workflow they need to improve.
- Pitfall 2: Ignoring the "Last Mile" of User Adoption: A technically strong system can fail if users do not trust its alerts.
- Pitfall 4: Planning for Deployment Without Planning for Maintenance: Sensor lifespan varies from 3-7 years.
Major section
Summary
Integrate with existing workflows (SAP work orders, municipal services) -- standalone dashboards fail.
- The hypothetical $23M/$47M model gives 5.9-month simple payback and 921.7% five-year ROI; its savings inputs require reconciliation before drawing a business-case conclusion.
- In the illustrative adoption model, test whether reducing false positives from 18% to below 5% improves technician response.
- Budget integration and change management from the actual work breakdown and pilot findings; measure the effort share before quoting one.
Deck summary
Key takeaways
The maintenance lead wants early warning, but a false stop wastes production and a missed fault can damage the line.
- The following 320-gateway, 85-TB/day automotive architecture is an illustrative design, not a reported deployment.
- Edge Computing is Essential for Industrial IoT.
- Different failure modes have different signatures.
- Many IoT budgets omit integration effort; list hardware, software, integration and change-management costs separately for the proposed deployment.
Retrieval practice
Recall check 1 of 5

Ada says: answer from memory, then check your reasoning.
Q1In the chapter's illustrative factory model, 30,000 sensors generate 85 TB/day, edge processing reduces cloud transmission by 99.8%, the uplink cannot carry the raw stream, and local alerts must arrive within 10 ms. If the edge gateways failed and raw data had to go through that uplink for cloud processing, what would be the most immediate operational impact?
Show answer
Answer: B The stated uplink cannot carry the raw stream, and an alert that depends on that transfer cannot meet the local 10 ms deadline.
Retrieval practice
Recall check 2 of 5

Ada says: answer from memory, then check your reasoning.
Q2In the chapter's illustrative automotive maintenance pilot, assume 87% prediction accuracy and an 18% false-positive rate. Technicians start ignoring alerts. Which modeled issue and metric should the team test first?
Show answer
Answer: A Correct for the stated model.
Retrieval practice
Recall check 3 of 5

Ada says: answer from memory, then check your reasoning.
Q3A mid-sized city has limited first-year budget and adequate existing network coverage for a parking and lighting pilot. Applying the chapter's phased-deployment lesson, which service strategy should it test first?
Show answer
Answer: D Parking and lighting offer two bounded, visible services to test; measure local outcomes before expanding.
Retrieval practice
Recall check 4 of 5

Ada says: answer from memory, then check your reasoning.
Q4In the chapter's illustrative automotive maintenance model, a plant runs predictive alerts beside its existing maintenance process for six months before cutover. What is the primary adoption purpose of this parallel period?
Show answer
Answer: A Running both paths gives technicians evidence to assess the alerts and build justified trust before changing the work process.
Retrieval practice
Recall check 5 of 5

Ada says: answer from memory, then check your reasoning.
Q5What joins a machine finding to asset priority, technician work, parts and outcome evidence?
Show answer
Answer: C The maintenance system joins the qualified finding to asset criticality, technician action, parts, outcome, and feedback that improves the next decision.
Q6Complete the deployment evidence gate for case-study alerts:
Show answer
Answer: A Deployment case-study alerts should connect model confidence and operational workflow before they become technician work.
Print reference
Answers 1 of 2
Answer key.
- B · The stated uplink cannot carry the raw stream, and an alert that depends on that transfer cannot meet the local 10 ms deadline.
- A · Correct for the stated model.
- D · Parking and lighting offer two bounded, visible services to test; measure local outcomes before expanding.
- A · Running both paths gives technicians evidence to assess the alerts and build justified trust before changing the work process.
Print reference
Answers 2 of 2
Answer key.
- C · The maintenance system joins the qualified finding to asset criticality, technician action, parts, outcome, and feedback that improves the next decision.
- A · Deployment case-study alerts should connect model confidence and operational workflow before they become technician work.