Slice
Line-shaped prototype
Vision or signal plus a documented override and fail-safe.
Manufacturing AI
Quality, maintenance, and documents on the line: vision, time series, and retrieval under safety, latency, and an operator who can override.
Created by Baljeet Dogra
Course Objectives
- Pick edge vs cloud because of latency and failure, not a vendor pitch.
- Design an inspection or maintenance slice with an operator veto.
- Retrieve procedures without hallucinating a torque spec.
- Write the fail-safe: what happens when the model is down.
What you will produce
Docs
Procedure RAG
Citations, abstention, no invented specs.
4 weeks curriculum
Expand a part for the syllabus. Content stays searchable when closed.
01 The line Week 1
Cycle time, safety, who is allowed to stop the line. OT/IT reality.
- OT/IT
- Safety
- Latency
- Roles
02 See and sense Week 2
Inspection images, simple signals, what a false negative costs.
- Inspection
- Signals
- Costs
- Data
03 Documents Week 3
SOPs, RAG, abstention, citations. Inventing a spec is a safety bug.
- SOPs
- RAG
- Abstention
- Audit
04 Edge and fail-safe Week 4
Where it runs, override, capstone drill.
- Edge
- Override
- Fail-safe
- Capstone
Who this is for
Engineers in industrial firms
A cloud demo will not survive the line. You need the constraints in the design.
Automation and quality leads
You know the process. You need AI that can be overridden.
Prerequisites
- Python
- Willingness to work with public/synthetic industrial data
- Respect for safety-critical constraints
Not a fit if
- Autonomous factory fantasies in four weeks
- People who will not design an override
Related: Computer Vision · AI Security & Privacy
Questions
Will we program PLCs?
No. You will design the AI slice and the interface to operations, not replace OT engineering.
Edge hardware required?
We simulate latency and failure. Optional edge if you have it; not a blocker.
Ready to start?
Four weeks to a line-shaped prototype with an override. Create an account to enrol.
Enrol now