/ THE SHORT ANSWER
- 01Assess at workflow level because data, value and risk vary across the operation.
- 02Use a score to expose evidence gaps, not to manufacture certainty.
- 03Require a decision brief that names the next move, owner, test and stop rule.
/ dotSuper point of view
Readiness is not enthusiasm, tooling or a strategy deck. It is the observable ability to improve one workflow safely, measurably and with an accountable owner.
Six dimensions that belong in the assessment
They are not a government certification or universal standard.
They are a decision tool for a bounded manufacturing use case.
| Dimension | Question | Evidence of readiness |
|---|---|---|
| Operating value | What loss, delay or decision should improve? | Baseline, volume, consequence and target |
| Process stability | Is the current workflow understood well enough to change? | Observed steps, variants, exceptions and owner |
| Information readiness | Are representative inputs available and governed? | Coverage, quality, rights, revisions and refresh path |
| Technical fit | Is AI the lightest adequate method? | Method comparison, integration path and performance test |
| Human control | Where must people judge, approve or intervene? | Authority matrix, fallback and escalation |
| Ownership | Who runs, reviews and improves the system? | Named operator, maintainer, documentation and review rhythm |
A score is useful only when every point has evidence
Zero means the answer is unknown.
One means the team has assumptions or partial evidence.
Two means the workflow has representative evidence and a workable plan.
Three means the condition is proven under the proposed operating boundary.
Do not average away a critical zero.
A missing owner, unavailable source, unacceptable failure mode or unbounded safety consequence can block a pilot even when the other dimensions score well.
EXAMPLE, NOT A BENCHMARK
A readiness profile should reveal the bottleneck.
Illustrative scores for a document-assistance workflow. Scores must be supported by local evidence.The example should lead to foundation work before a broad pilot. It is not a score for another organisation.
View the chart data
| Dimension | Score | Observed gap |
|---|---|---|
| Operating value | 3 | None inside the proposed boundary |
| Process stability | 2 | Exception ownership |
| Information readiness | 1 | Revision and permission control |
| Technical fit | 2 | Representative evaluation set |
| Human control | 2 | Escalation response time |
| Ownership | 1 | Maintainer and review rhythm |
Four legitimate decisions can leave the assessment
Its job is to make the next investment sharper.
The decision may be to build, repair the foundation, procure, or stop.
| Decision | Use it when | What happens next |
|---|---|---|
| Build a bounded pilot | Value, information, control and ownership are strong enough | Test one workflow with a baseline and stop rule |
| Repair the foundation | The use case matters but process, data or ownership is weak | Fix the blocking condition before development |
| Procure | The workflow is standard and a proven capability fits the boundary | Run vendor and integration due diligence |
| Stop | Value is small, risk is disproportionate, or evidence cannot support the system | Document the reason and review trigger |
What should leave the room after fifteen working days
The output must be usable by the team even if it chooses a different build partner.
- One sentence defining the constraint and business consequence.
- A workflow map showing normal work, exceptions and handoffs.
- A baseline with source, period and known limitations.
- A representative evidence set and explicit data gaps.
- A human-authority map with review, override and escalation.
- A build, repair, procure or stop decision with an owner and review date.
Questions for an assessment provider
A workshop that only lists use cases may be useful for awareness, but it is not the same as readiness evidence.
- Which workflow-level evidence will you inspect?
- How will you compare AI with simpler process or automation changes?
- What would make you recommend that we do not build?
- Which outputs can another team use without you?
- How are operational, technical and human risks recorded?
What this page cannot conclude
- 01The scorecard is a dotSuper operating framework, not an official Bharat 4.0 or NIST assessment.
- 02It does not certify compliance, safety, cybersecurity or production fitness.
- 03Each site and workflow requires representative evidence and responsible domain review.
Sources
- 01Bharat 4.0 Digital Readiness Assessment ToolNational Productivity Council, Government of India · accessed Sep 7, 2026
- 02Transforming Small Businesses: An AI Playbook for India’s SMEsWorld Economic Forum and the Office of the Principal Scientific Adviser to the Government of India · accessed Sep 7, 2026
- 03AI Risk Management FrameworkNational Institute of Standards and Technology · accessed Sep 7, 2026
- 042026 Roadmap on Artificial Intelligence and Machine Learning for Smart ManufacturingNational Institute of Standards and Technology · accessed Sep 7, 2026
- 05Artificial Intelligence for ManufacturingNational Institute of Standards and Technology · accessed Sep 7, 2026
Our editorial standard · Found an error? Send a correction with its source.
/ CITE OR SHARE THIS GUIDE
Make the evidence easy to verify.
When you reference this guide, link to its canonical URL. That gives readers one stable place for the evidence, limitations and future updates.
dotSuper Research Desk. (September 7, 2026). AI Readiness Assessment for Manufacturing: Score the Workflow, Not the Ambition. dotSuper. https://dotsuper.net/feeds/applied-systems/ai-readiness-assessment-manufacturing