The Challenge
A leading automotive manufacturer faced a persistent problem of unplanned downtime which was affecting their production efficiency and bottom line. With twelve production lines operating constantly, any halt was costly, leading to not just financial losses but also impacting supply chain commitments. The manufacturer sought a robust solution to monitor equipment health, reduce downtime, and enhance productivity while controlling operational costs.
The Solution
Adyantrix was approached to provide a technology-driven solution that could address these issues head-on. Our team proposed deploying a sophisticated Industrial IoT platform designed to provide real-time data acquisition and predictive insights from the production lines.
The implementation commenced with an extensive evaluation of the manufacturer's existing infrastructure, followed by the customization of IoT sensors and devices that were seamlessly integrated along the twelve production lines. These sensors captured critical operational metrics such as temperature, vibration, and power consumption, which were instantaneously relayed to the IoT platform.
To enable data-driven decision making, the platform featured advanced analytics capabilities powered by machine learning algorithms. These algorithms were tuned to detect anomalies and predict maintenance needs before failures could occur, thereby enabling timely interventions.
Furthermore, the scalable cloud-based architecture allowed for robust data aggregation and processing. This ensured that plant managers could access real-time dashboards and reports from anywhere, facilitating informed decision-making.
Key Features
- Real-Time Monitoring: Enabled continuous observation of production parameters to detect deviations from optimal conditions.
- Predictive Maintenance: Leveraged machine learning to forecast potential equipment failures, reducing needless downtime.
- Cloud-Based Analytics: Provided insights into operational patterns and anomalies via accessible dashboards.
- Seamless Integration: Ensured IoT devices worked cohesively with existing systems for unified operations.
Key Results
As a result of the IoT platform deployment, the automotive manufacturer experienced a remarkable 35% reduction in unplanned downtime across its twelve production lines. This substantial decrease translated into millions in cost savings and improved overall efficiency of production operations.
Additionally, the manufacturer enjoyed enhanced visibility into their operational processes, enabling more refined control over production quality and timelines. The proactive maintenance approach fostered by the platform further reduced operational risks and improved the lifespan of critical machinery.
Through this successful engagement, Adyantrix not only delivered a cutting-edge technological solution but also empowered the manufacturer to sustain competitive advantages in a rapidly evolving industrial landscape.
Technical Approach
The platform was built on a layered IIoT architecture that separated edge computing, data transport, cloud processing, and application delivery into distinct tiers — each independently scalable and resilient.
At the edge, we deployed ruggedised IoT gateways (Siemens SIMATIC IOT2050) directly on each production line. These ran lightweight inference models locally, enabling sub-second anomaly flagging even during network interruptions. Sensors included tri-axial vibration accelerometers (sampling at 12.8 kHz), thermocouples for motor temperature, and Hall-effect current sensors for load anomaly detection.
Data transport used MQTT over TLS with message brokering on Eclipse Mosquitto, chosen for its low-latency publish/subscribe model suited to high-frequency industrial telemetry. A message schema aligned to the IEC 62541 (OPC-UA) standard ensured interoperability with the manufacturer's existing SCADA systems.
On the cloud side, we deployed the platform on Microsoft Azure using Azure IoT Hub for device management, Azure Stream Analytics for real-time CEP (complex event processing), and Azure Machine Learning for model training and retraining pipelines. The primary ML models were gradient-boosted decision trees (XGBoost) trained on 18 months of historical sensor data, with LSTM networks applied to rolling time-series windows for sequence-based failure prediction. Dashboards were built in Power BI Embedded with sub-30-second refresh cycles, surfaced through a custom React web portal accessible to plant managers and maintenance supervisors.
Implementation Highlights
The deployment unfolded across four phases over a 14-week programme:
-
Phase 1 — Sensor Audit & Baseline Capture (Weeks 1–3): We conducted a full asset register review across all twelve production lines, identifying 87 critical assets and 214 sensor-placement points. A two-week silent-monitoring period collected baseline telemetry without triggering any alerts, establishing the normal operating envelope for each asset class.
-
Phase 2 — Edge Infrastructure & Connectivity (Weeks 4–6): Gateways were installed in IP65-rated enclosures to withstand the factory floor environment. Industrial Ethernet cabling and 4G LTE failover were provisioned, achieving 99.7% uptime connectivity during the pilot period.
-
Phase 3 — Cloud Platform & ML Model Training (Weeks 7–11): The Azure environment was stood up with infrastructure-as-code (Terraform), ensuring repeatable, auditable deployments. Initial XGBoost models achieved a precision of 91% on the validation set; LSTM models added a further 4% improvement on time-to-failure predictions beyond the 48-hour horizon.
-
Phase 4 — Pilot Rollout & Tuning (Weeks 12–14): Three production lines went live first. Alert thresholds were iteratively tuned to reduce noise — the initial alert volume was halved within ten days through feedback loops with maintenance engineers. Full rollout to all twelve lines followed with zero production interruptions.
The single most significant challenge encountered was legacy PLC incompatibility. Several Fanuc and Mitsubishi PLCs predated OPC-UA support, requiring us to develop bespoke protocol translation middleware that polled proprietary Modbus registers and mapped them into the unified IEC 62541 namespace. This added approximately two weeks to Phase 2 but was essential for complete line coverage.
Measurable Outcomes
The headline 35% reduction in unplanned downtime represented roughly 1,840 recovered production hours annually across the twelve lines. At the manufacturer's average output value per line-hour, this equated to a conservatively estimated £4.2 million in recovered production value in the first year.
Additional measured outcomes included:
- Mean Time Between Failures (MTBF): Increased by 28% across monitored assets within six months of go-live, reflecting the impact of condition-based maintenance replacing calendar-based schedules.
- Mean Time to Repair (MTTR): Reduced by 41%, as maintenance teams arrived at fault sites with diagnostic context rather than starting investigations from scratch.
- Planned vs. Unplanned Maintenance Ratio: Shifted from 55:45 (planned:unplanned) pre-deployment to 79:21 within eight months — a structural improvement in maintenance maturity.
- Spare Parts Inventory Costs: Reduced by 18% as demand-driven ordering replaced precautionary stock-holding, enabled by accurate remaining-useful-life (RUL) estimates from the ML models.
- Energy Consumption: A secondary benefit emerged in the form of a 7% reduction in energy draw per unit of output, as the platform identified motors running in degraded states that were consuming excess current before failure.
The platform's ROI payback period was calculated at approximately 11 months against total project investment, including hardware, deployment, and the first year of managed cloud costs.
Lessons Learned
Several insights from this engagement have shaped how we approach IIoT deployments of comparable scale.
Legacy system compatibility must be assessed at the outset. In this project, PLC protocol diversity was underestimated during scoping. A dedicated one-week protocol audit prior to hardware procurement would have avoided the Modbus middleware rework in Phase 2.
Alert fatigue is the single biggest threat to adoption. The platform delivered strong ML accuracy on paper, but early in the rollout, maintenance teams were receiving upwards of 60 alerts per shift — many legitimate but indistinguishable in urgency. Investing time in alert stratification (P1 / P2 / P3 tiers with distinct notification channels) was essential to sustaining operator trust. We now treat alert design as a first-class deliverable equal in importance to model accuracy.
Edge inference pays for itself in reliability. The decision to run lightweight models locally on the gateways, rather than relying solely on cloud inference, proved critical during three network outage events. In each case, the edge layer continued to detect and log anomalies autonomously, with no gap in coverage.
Maintenance engineer involvement during model training improves relevance. Structured workshops with floor-level engineers during Phase 3 surfaced failure modes that were absent from the historical data log (because they had always been caught by experienced operators informally). Incorporating this tacit knowledge as labelled training examples noticeably improved model recall for early-stage bearing wear.
Why This Approach Worked
The success of this deployment came down to three structural decisions that distinguished it from typical IIoT pilots that stall at proof-of-concept stage.
First, the platform was designed for the full twelve lines from day one rather than treating the initial three-line pilot as a separate system. This meant the architecture, data schema, and cloud infrastructure were production-grade from the outset, avoiding the costly re-platforming that afflicts many IIoT programmes when they attempt to scale.
Second, we anchored the ML models to outcomes that maintenance engineers already cared about — specifically, preventing bearing failures, seal degradation, and motor overloads, the three fault categories responsible for over 60% of historical unplanned stoppages. This kept the analytics grounded in operational reality rather than optimising for statistical metrics disconnected from floor-level priorities.
Third, the integration with the manufacturer's existing CMMS (Computerised Maintenance Management System) meant that platform-generated work orders flowed directly into the scheduler that maintenance teams used every day. There was no parallel workflow to maintain, which is often where IIoT adoption breaks down. The platform became a productivity layer on top of familiar tools rather than a disruptive replacement, dramatically accelerating user acceptance.
Speak with our Custom Software Development team at Adyantrix to find out how we can support your next project.
Work with Adyantrix
If you are looking to tackle a similar challenge, Adyantrix has the expertise to help across the full project lifecycle. Our custom software development practice covers tailored applications built to your exact workflows. Our data engineering practice covers pipeline design, streaming, and data infrastructure. Our data analytics practice covers BI reporting and self-serve analytics platforms. Our cloud & DevOps practice covers cloud infrastructure, CI/CD, and platform engineering. Get in touch to discuss your requirements — no commitment required.
