Process Audit Checklist for Manufacturing (VDA 6.3 Style)

By Stephanie Grant on May 29, 2026

process-audit-checklist-vda-6-3

At 2:14 AM on a Tuesday, a senior operator in a 500,000 sq ft assembly plant watches a critical station drop to 62% OEE. The PLC data says the line is down, but the ERP system — updated on a 15-minute batch cycle — still shows it running. By the time the discrepancy surfaces in the morning production meeting, the plant has lost 47 units of throughput, $23,000 in direct labor cost, and an hour of schedule buffer that cannot be recovered. The operations director knows the data is siloed, the latency is baked into the architecture, and the real-time picture simply does not exist. This is not a process failure. It is an information failure — and it is costing every shift.

MANUFACTURING · REAL-TIME OEE & DOWNTIME · 2026

Stop Guessing on OEE — See Every Second of Downtime, Live, Across Every Line

iFactory ingests PLC, SCADA, and historian data at sub-second latency on your plant network, computes true OEE in real time, and surfaces the exact root cause of every stoppage — before the shift ends.

18%
Average OEE gap between reported and actual
47
Units lost per hour of hidden downtime
<1 sec
Data-to-OEE latency with iFactory
$2.1M
Annual cost of uncaptured downtime in a 300,000 ft² plant
THE REAL COST OF BLIND SPOTS

Why Your OEE Dashboard Is Lying to You

Most manufacturers rely on ERP batch updates, manual shift logs, or SCADA averages that mask the granularity of every stoppage. The result is a chronic, invisible drain on throughput. Here is what that looks like on the plant floor.

01

Latency hides micro-stops

A 47-second jam at a conveyor merge — caused by a sensor misalignment — never appears in your ERP. But across 500 cycles per shift, those micro-stops burn 3.9 hours of productive time. That is $8,700 in lost output every day.

02

OEE is averaged into irrelevance

Your dashboard shows 85% OEE for the shift. But Line 3 actually ran at 62% for the first two hours after a changeover, and Line 7 hit 94% after lunch. A single average buries the root cause — and the opportunity to fix it.

03

Root cause is a guessing game

When a station drops below 70% OEE, your team spends 45 minutes walking the line, pulling logs, and cross-referencing PLC timestamps. By the time they find the issue — a misconfigured sensor on a pick-and-place — the line has lost 112 units.

04

Manual data entry costs double

Operators spend 20 minutes per shift keying downtime codes into a spreadsheet. The data is late, inconsistent, and never used for real decisions. That is 2 hours per operator per week — a $14,000 annual cost per line for data that is already wrong.

05

Reactive maintenance destroys throughput

Without real-time OEE, you cannot detect a gradual performance decay. A conveyor that slows by 3% over a week goes unnoticed until it fails. The emergency repair costs $6,200 in part replacement and 4 hours of downtime — $11,000 in total.

You cannot fix what you cannot see in real time. Book a 30-min walkthrough and we'll show you live OEE on your own plant data.

HOW IFACTORY DELIVERS REAL-TIME OEE

From Data Noise to Actionable Visibility in Four Steps

iFactory runs on an NVIDIA appliance inside your plant network. It connects directly to your PLCs, SCADA, and historians, computes OEE at sub-second latency, and surfaces the exact cause of every downtime event — without a cloud dependency or a data egress risk.

1

Connect to Any Data Source

We tap into your existing PLCs (Allen-Bradley, Siemens, Mitsubishi), SCADA systems, and historians — no new sensors, no IT project, no cloud gateway.

2

Compute True OEE in Real Time

iFactory calculates Availability, Performance, and Quality at sub-second intervals per station, per line, per shift — no batch averages, no delay.

3

Identify Root Cause Instantly

Every downtime event is tagged with the exact PLC signal, sensor, or alarm that caused it — eliminating the 45-minute walkthrough and the guesswork.

4

Act Before the Shift Ends

Real-time dashboards, alerts, and shift reports let operators and supervisors respond to OEE drops as they happen — not the next morning.

CAPABILITIES THAT CLOSE THE VISIBILITY GAP

What You Get with Real-Time OEE from iFactory

These capabilities are built into the platform — no add-ons, no custom development, no integration projects.

VISIBILITY

Sub-Second OEE Refresh

Every station, every cycle. OEE updates in under one second from the last PLC timestamp. No batch, no delay, no averaging that hides the truth.

ROOT CAUSE

Automated Downtime Classification

Every stoppage is automatically tagged with the exact PLC signal — sensor fault, jam, operator wait, maintenance lockout — so you know why, not just how much.

ALERTS

Real-Time Shift Alerts

When a station drops below a configurable OEE threshold, iFactory sends an alert to the supervisor's phone, tablet, or plant PA system — in seconds, not minutes.

TRENDING

Performance Decay Detection

iFactory tracks OEE trends over shifts, days, and weeks. A 2% per-shift decay triggers a flag before it becomes a 15% loss — giving you time to act.

REPORTING

Shift Reports in Under 10 Seconds

End-of-shift reports with OEE, downtime breakdown, and root cause summaries are generated automatically and delivered to email, Slack, or your MES.

INTEGRATION

Push to ERP or MES

iFactory can write OEE and downtime data back to your ERP, MES, or data lake — closing the loop between real-time operations and business systems.

MEASURABLE RETURN

The Financial Impact of Real-Time OEE

Manufacturers using iFactory see measurable improvements in OEE, reduced downtime, and lower manual data costs within the first 30 days of pilot.

OEE Improvement
14%
Average increase in OEE within 90 days of deployment
Downtime Reduction
23%
Reduction in unplanned downtime through root-cause visibility
Manual Data Cost Saved
$42K
Annual savings per line by eliminating manual downtime logging
Time to ROI
6 wks
Average time from pilot start to measurable ROI
WHAT YOU GET

iFactory Delivers Real-Time OEE — End to End

Every deployment includes the platform, the hardware, and the managed service. No hidden costs, no integration surprises, no cloud dependency.

Turnkey Pilot in 6–12 Weeks

We connect to your data sources, configure OEE models, and deploy a working pilot — no IT project, no custom development, no long lead times.

On-Premise NVIDIA Appliance

iFactory runs on your plant network — zero cloud dependency, zero data egress, zero latency. All data stays inside your four walls.

24x7 Managed Service

We monitor the appliance, update models, and provide support around the clock. You focus on running the plant, not maintaining software.

Pilot-to-ROI in One Quarter

We design the pilot to show measurable OEE improvement within 90 days — or we help you scale to full deployment.

No New Sensors Required

iFactory connects to your existing PLCs, SCADA, and historians. No additional hardware, no wiring, no field engineering.

End-to-End Ownership

We handle connectivity, computation, visualization, and reporting. You get a single source of truth for OEE, across every line, every shift.

FREQUENTLY ASKED QUESTIONS

Real Questions from Operations Leaders

How does iFactory compute OEE differently from my existing SCADA or ERP?
Most SCADA systems report average cycle times or aggregated availability. ERP systems update on batch cycles of 5 to 15 minutes. iFactory reads PLC data at sub-second intervals and computes OEE per station, per cycle — without averaging. This means you see every micro-stop, every performance dip, and every quality loss in real time, not as a smoothed-over number that hides the root cause.
What data sources do I need to provide for the pilot?
You need read-only access to your PLCs (via OPC UA, Modbus, or native protocols), SCADA historian, or a time-series database. No new sensors, no IT changes, no cloud connectivity. iFactory's on-premise appliance connects directly to your plant network. We handle the integration in the first week of the pilot.
How long does it take to see results?
The pilot takes 6 to 12 weeks from initial data connection to a working OEE dashboard. Most customers see measurable OEE improvements — typically 10 to 15% — within 30 days of the pilot going live. The first shift report with real-time OEE is usually available within two weeks of connection.
Can iFactory handle 500+ stations across multiple lines?
Yes. iFactory is built on an NVIDIA appliance that scales to thousands of data points per second. The platform is designed for large manufacturing sites with multiple lines, hundreds of stations, and complex production flows. We have deployed in plants with over 1,200 PLC data points across 14 lines.
What happens to my data if the internet goes down?
Nothing. iFactory runs entirely on your plant network. All data processing, OEE computation, and dashboard rendering happen on the local appliance. A WAN outage has zero impact on OEE visibility. The appliance continues to operate and store data locally until connectivity is restored.

Stop Guessing. Start Seeing Every Second of OEE.

iFactory delivers real-time OEE on your plant network — no cloud, no latency, no hidden costs. Book a 30-minute walkthrough and we'll show you live data from a real manufacturing line.


Share This Story, Choose Your Platform!