To use AI in manufacturing, start with one specific decision on the line, such as rejecting cosmetic defects or counting mixed parts, then prove the data can support it, run a proof of concept on real parts, integrate with the line, validate against agreed acceptance criteria, and monitor and retrain once it is running. Most failed manufacturing AI projects skip the first two steps and start with a model.
This article is part of our guide to industrial AI, which explains where AI is used in manufacturing and the model types behind it. Here we lay out the implementation roadmap step by step, with the questions to answer and the deliverables at each stage.
The roadmap at a glance
| Step | Key question | Deliverable | Typical duration |
|---|---|---|---|
| 1. Pick the use case | Which decision is worth automating? | Ranked shortlist, one chosen | 1–2 weeks |
| 2. Define success | What must the system decide, how fast, how accurately? | Written acceptance criteria | 1 week |
| 3. Check data feasibility | Is the defect or fault visible in the data? | Sample images or signals, feasibility verdict | 1–3 weeks |
| 4. Proof of concept | Does a model meet the criteria on real parts? | PoC report with measured rates | 3–8 weeks |
| 5. Build and integrate | How does it connect to the line? | Installed system, PLC and MES links | Weeks to months |
| 6. Validate | Does it meet the criteria in production? | Validation report, sign-off | 2–6 weeks |
| 7. Run, monitor, scale | Is it still performing? Where next? | Monitoring, retraining plan, rollout | Ongoing |
Durations are typical ranges for an inspection or counting project and vary widely with complexity, data availability and the amount of custom handling equipment.
Step 1: Pick the right first use case
Score each candidate on four factors, 1 (poor) to 5 (good), and start with the highest total:
| Factor | Scores high when… |
|---|---|
| Value | Labor, scrap, escapes or downtime are costly today |
| Data | Images or signals can be captured, and examples of good and bad exist |
| Feasibility | The decision is visible to a camera or sensor and people can make it consistently |
| Risk | A wrong decision can be caught downstream; the line is not safety-critical |
Good first projects are repetitive, high-volume judgment tasks: cosmetic inspection, counting and sorting, test-result screening. Poor first projects need perfect accuracy from day one, depend on data nobody collects, or try to automate a decision experts themselves disagree on. If you are unsure whether a task needs AI at all, see deep learning vs rule-based machine vision.
Step 2: Define success before choosing technology
Write the acceptance criteria down and get quality, production and engineering to sign them:
- The decision: pass/fail, defect class, count, alarm
- Rate: parts per minute and the time budget per part (at 120 parts per minute, 60 ÷ 120 = 0.5 s per part)
- Escape rate: the share of bad parts allowed through, per defect type
- False-reject rate: the share of good parts rejected that the process can tolerate
- Outputs: reject signal, data to the MES, operator screen, reports
- Business case: payback = system cost ÷ monthly savings from labor, scrap, rework and avoided escapes
Step 3: Check that the data can support the decision
Before any model, confirm that the defect or fault actually shows up in the data. For vision, that means camera resolution, optics and lighting that make the smallest defect several pixels wide and visibly different from good parts. For sensor data, it means the right sensors sampled fast enough. Collect a small sample of good and bad parts and look at them. Our article on training data for AI visual inspection covers the resolution check and data volumes.
Step 4: Run a proof of concept on real parts
A proof of concept trains a first model on a representative sample and measures it on parts it has not seen. It should answer one question: can this approach meet the acceptance criteria? Report escape and false-reject rates per defect type, not a single accuracy figure, and list the failure cases. If results fall short, the usual fixes are better imaging and more consistent labels, not a bigger model.
Step 5: Build and integrate
The model is a small part of the production system. Most of the build is:
- Part handling and presentation: fixtures, conveyors, robots, reject mechanisms
- Imaging or sensing hardware sized for production speed
- Edge compute that meets the cycle time
- Integration with the PLC for triggers and rejects, and with the MES for results and traceability
- An operator interface for status, overrides and review of flagged parts
- Data logging for monitoring and retraining
Step 6: Validate in production
- Shadow mode. Run the AI alongside the current process without acting on it, and compare decisions.
- Known-good and known-bad sets. Challenge the system with sets of parts whose status is certain, including borderline parts.
- Measure against the criteria. Escape and false-reject rates per defect type, cycle time and uptime.
- Sign off and freeze. Record the model version, thresholds and results in a validation report.
Step 7: Run, monitor and scale
Processes change, so AI systems need upkeep: review flagged parts, feed escapes and false rejects back as training data, watch for drift in scores and retrain with re-validation. Once the first system is stable, reuse its data pipeline, hardware and validation method for the next use case. For defects that are rare or unpredictable, consider adding AI anomaly detection.
Build, buy or partner?
| Option | Works well when | Watch out for |
|---|---|---|
| Off-the-shelf smart camera with AI tools | One simple, well-lit inspection on a consistent part | Limited handling, integration and flexibility |
| In-house team | You have vision, controls and data engineers and many similar lines | Time to build skills; ongoing support load |
| Systems integrator | The job needs custom handling, multiple sensors or line integration | Choose one that tests on your parts before quoting |
Common mistakes
- Starting with a model instead of a decision and acceptance criteria
- Trying to fix poor lighting or imaging with more data
- Measuring overall accuracy instead of escapes and false rejects
- Leaving out operators until launch
- No plan or budget for monitoring and retraining
Ready to scope your first AI project?
Sciotex helps manufacturers pick the right first use case, tests it on real parts and builds the complete industrial AI system, from handling and imaging to models and line integration, designed, programmed, built and supported in the US since 1997.
Frequently asked questions
Pick one repetitive, high-value decision, write measurable acceptance criteria, confirm the data shows what the decision depends on, then run a proof of concept on real parts before building a production system.
Usually a high-volume judgment task with clear value and available data, such as cosmetic inspection, counting and sorting of variable parts, or screening test results.
A focused inspection or counting project often moves from use-case selection to a validated system in a few months, depending on data availability, custom handling equipment and integration scope.
The most common reasons are an unclear decision or acceptance criteria, imaging or sensor data that does not show the defect, inconsistent labels, and no plan for monitoring and retraining after launch.
Not necessarily. Many projects are delivered by an integrator or vendor; what the plant needs is people who own the process, the defect standard and the ongoing review of results.