From Vision to Execution
How could a Maharashtra AI Competency & Delivery Centre actually work?
In Part 1, I explored the concept of a statewide AI competency capability for Maharashtra State
The difficult part begins now.
Creating an AI Centre is relatively easy.
Creating a Centre that government departments actually use, trust and benefit from is much harder.
The implementation model therefore needs to be practical, measurable and designed around existing government structures.
Maharashtra already has an EIT&AI Department with a broad mandate covering AI, digital governance, cybersecurity, data governance and emerging technologies. The Department's published documents also show the State is putting structures around IT project approvals and the Directorate/Commissionerate.
The proposed AI Competency & Delivery Centre should therefore be designed as an execution and enablement capability within the existing ecosystem, rather than as a parallel bureaucracy.
1. Start with the mandate
The Centre's mandate could be expressed in five words:
Identify. Enable. Govern. Scale. Measure.
Identify
Find high-value government problems where AI may help.
Enable
Provide architecture, skills, reusable components and implementation support.
Govern
Establish responsible AI, security, data and procurement guardrails.
Scale
Move successful pilots into production and across departments/districts.
Measure
Track actual public value.
This keeps the Centre focused on outcomes rather than technology demonstrations.
2. Suggested operating model
A lean structure could have seven capability groups.
1. AI Strategy & Architecture
Responsibilities:
- statewide AI reference architecture
- use-case prioritisation
- technology evaluation
- interoperability
- cloud/AI infrastructure guidance
2. AI Engineering & Platforms
Responsibilities:
- reusable AI components
- RAG platforms
- AI agents
- document intelligence
- evaluation frameworks
- APIs and integration patterns
3. Data & AI Governance
Responsibilities:
- data classification
- privacy
- data quality
- responsible AI
- model governance
- auditability
4. Cybersecurity
Responsibilities:
- AI-specific security
- prompt injection risks
- data leakage controls
- identity and access
- vendor security assessment
5. AI Academy
Responsibilities:
- employee training
- role-based learning
- AI certification
- AI Champions programme
- learning analytics
6. Innovation & Ecosystem
Responsibilities:
- startups
- universities
- research institutions
- industry partnerships
- AI sandbox
- challenge programmes
7. Benefits & Programme Management
Responsibilities:
- business cases
- pilot management
- KPIs
- benefits realisation
- portfolio reporting
The Centre does not need hundreds of employees.
It needs high-quality people with strong architecture, government-domain, AI, data and programme-management capability.
3. The AI Champion network
Every department could nominate an AI Champion.
Every district could nominate an AI Champion.
The Champion need not be an AI engineer.
The role is to understand:
- What problems exist?
- Which processes are suitable for AI?
- What data is available?
- What risks exist?
- How could a pilot be measured?
The Centre then provides the specialist capability.
This creates a network:
State AI Centre
↕
Department AI Champions
↕
District AI Champions
↕
Operational teams
This may be more scalable than trying to build a large AI team in every department.
4. Create a State AI Use-Case Registry
This could become one of the Centre's first practical assets.
Every department submits potential AI opportunities.
Each opportunity is recorded against criteria such as:
- citizen impact
- government productivity
- financial impact
- feasibility
- data readiness
- implementation complexity
- cybersecurity risk
- legal/regulatory risk
- scalability
- expected time to value
The Centre can then classify opportunities as:
Quick Win
Can be implemented rapidly with relatively low risk.
Strategic Pilot
Potentially significant impact but requires validation.
Platform Opportunity
Reusable across multiple departments.
Research Challenge
Requires research or experimentation.
Not Suitable for AI
Important category.
Not every problem needs AI.
5. Use a common AI project lifecycle
Every government AI project could follow a standard lifecycle:
Stage 1 — Problem Definition
What government problem are we solving?
Stage 2 — Baseline
How does the existing process perform?
For example:
Current processing time = 5 days
Stage 3 — AI Hypothesis
What could AI potentially improve?
Stage 4 — Data Assessment
Is the necessary data available, accurate and legally usable?
Stage 5 — Prototype
Build the smallest useful version.
Stage 6 — Evaluation
Test:
- accuracy
- reliability
- security
- bias
- cost
- usability
Stage 7 — Controlled Pilot
Deploy to a limited user group.
Stage 8 — Benefits Measurement
Compare with the baseline.
Stage 9 — Scale / Stop
If it works, scale.
If it does not, stop or redesign.
This last step is important.
Government should be comfortable stopping AI pilots that do not demonstrate value.
6. Build an AI Sandbox
The Centre could establish a controlled environment where startups, universities and technology companies can experiment with government-approved datasets and problems.
A challenge could be framed as:
“Can AI reduce processing time for this government workflow by 30% while maintaining or improving accuracy?”
Multiple teams could propose solutions.
Government gets evidence.
Startups get a real-world problem.
Universities get research opportunities.
The successful approach can then be evaluated for production deployment.
7. Create a reusable AI platform
The Centre could define a common technical architecture rather than forcing every department to create its own.
Potential building blocks:
Identity & Access
↓
Secure Data Layer
↓
AI Gateway
↓
Model Layer
↓
RAG / Knowledge Layer
↓
AI Agent / Workflow Layer
↓
Application & Citizen Interface
↓
Monitoring & Audit
This would not necessarily mean one technology vendor.
The architecture should ideally allow model, cloud and technology substitution where practical.
That reduces the risk of vendor lock-in.
8. Government AI Marketplace
A validated internal catalogue could contain:
| Capability | Possible users |
|---|---|
| Document Intelligence | Multiple departments |
| Translation | Statewide |
| Knowledge Assistant | Officers |
| Data Analyst Assistant | Departments |
| Grievance Classification | Citizen services |
| Meeting Assistant | Government offices |
| Scheme Analytics | Departments/districts |
| Citizen Information Assistant | Public-facing services |
Before starting a new project, departments could check:
Does an approved capability already exist?
If yes, reuse it.
If not, create a new capability with reuse in mind.
9. The 100-day implementation plan
Days 1–30: Discover
Establish the Centre's core team.
Create:
- AI inventory
- existing project inventory
- department AI Champions
- data readiness assessment
- skills assessment
- AI opportunity registry
Identify the first 10–15 candidate use cases.
Days 31–60: Prioritise
Select a small portfolio.
For every selected project define:
- problem
- baseline
- expected benefit
- owner
- data
- risk
- cost
- timeline
- success metric
No vague AI projects.
Every project gets an outcome.
Days 61–100: Pilot
Launch a handful of carefully selected pilots.
For example:
Government knowledge assistant
Document intelligence
Employee productivity assistant
District analytics
Citizen-service assistant
The objective is not to launch dozens of pilots.
It is to demonstrate credible, measurable results.
10. First-year implementation roadmap
Quarter 1
Foundation
- Centre
- governance
- AI inventory
- use-case registry
- AI Champions
Quarter 2
Pilot
- 5–10 high-value pilots
- employee AI training
- AI sandbox
- reusable components
Quarter 3
Scale
- successful pilots across departments
- district deployments
- AI marketplace
- advanced training
Quarter 4
Institutionalise
- benefits dashboard
- annual AI impact report
- statewide AI architecture
- next-year portfolio
11. The Maharashtra AI Dashboard
A senior leadership dashboard could answer five questions.
1. Adoption
How many departments are using AI?
2. Productivity
How many hours have been saved?
3. Citizen impact
Has service delivery improved?
4. Financial impact
What measurable cost avoidance or value has been generated?
5. Capability
How many government employees have developed practical AI skills?
The dashboard should show outcomes, not activity.
12. Training should become continuous
Instead of one annual AI training programme, create an AI learning ecosystem.
15-minute
AI awareness modules.
60-minute
Role-specific productivity courses.
Half-day
Department-specific workshops.
Multi-day
AI practitioner programmes.
Advanced
AI engineering and architecture programmes.
The Centre can also map and reuse existing government, university and industry courses.
The result:
Learn → Apply → Measure → Improve
13. Responsible AI gateway
Before a high-impact AI system reaches production, it could pass through an AI assurance process.
Questions include:
Data
Is the data appropriate?
Security
Can information leak?
Accuracy
How is the model evaluated?
Human oversight
Where must a human remain responsible?
Transparency
Can users understand the system's role?
Monitoring
How will performance be tracked after deployment?
Exit
What happens if the AI system fails?
This creates a government AI safety net.
14. Funding model
The Centre could use a portfolio approach.
Central capability funding
For:
- architecture
- governance
- shared infrastructure
- training
- reusable components
Department funding
For domain-specific implementations.
Innovation funding
For startup and university pilots.
Outcome-based scaling
Larger investment only after successful pilot evidence.
This reduces the risk of making large technology investments before the value is demonstrated.
15. What about revenue generation?
This should be treated as a secondary objective, not the reason for creating the Centre.
After Maharashtra develops mature capabilities, it could explore knowledge-sharing or permissible professional services for other public institutions, subject to government rules.
Potential offerings could include:
- AI governance frameworks
- government AI architecture
- training
- implementation methodology
- AI readiness assessments
- reusable solutions
The strategic principle would be:
Public-sector capability developed in Maharashtra can become knowledge capital that benefits the wider public sector.
Any commercial or cost-recovery model would need appropriate legal, procurement and conflict-of-interest safeguards.
16. How to avoid the five common government AI traps
Trap 1 — Buying technology before defining the problem
Solution: Problem-first use-case selection.
Trap 2 — Running endless pilots
Solution: Every pilot gets a baseline, deadline and scale/stop decision.
Trap 3 — Vendor lock-in
Solution: Open architecture and reusable interfaces.
Trap 4 — Training without adoption
Solution: Measure practical workplace usage, not just attendance.
Trap 5 — AI without governance
Solution: Responsible AI and cybersecurity embedded into the lifecycle.
17. What should the Centre NOT become?
This may be as important as defining what it should become.
It should not become:
❌ another procurement bureaucracy
❌ another generic training institute
❌ a technology showcase
❌ a vendor-selection office
❌ an organisation that tries to build every application itself
❌ a replacement for departmental ownership
Instead:
It should be the government's AI capability accelerator.
18. A possible success formula
The implementation model can be reduced to one equation:
AI Value = Problem × Data × People × Technology × Governance × Adoption
If any one of these is close to zero, the overall result suffers.
Excellent AI technology cannot compensate for a poorly defined government problem.
Good data cannot compensate for employees who do not adopt the solution.
A powerful model cannot compensate for weak governance.
And a successful pilot has little value if nobody scales it.
19. The 3-year destination
Year 1
Build capability
Centre + governance + champions + pilots.
Year 2
Scale capability
Departments + districts + reusable platforms + training.
Year 3
Institutionalise capability
AI becomes part of normal government architecture, project planning, workforce development and service transformation.
The ultimate goal is not to have an impressive AI Centre.
The ultimate goal is to make the Centre almost invisible.
Because AI capability will have become part of how government works.
Conclusion
Maharashtra does not need to wait for the perfect AI technology.
AI will continue to evolve.
Models will change.
Platforms will change.
Vendors will change.
The enduring advantage will be institutional capability.
The ability to identify the right problems.
The ability to evaluate AI realistically.
The ability to protect citizens and government data.
The ability to train people.
The ability to experiment quickly.
The ability to measure outcomes.
And the ability to scale what works.
That is the real case for a Maharashtra AI Competency & Delivery Centre.
Not an AI project.
Not an AI platform.
A permanent capability for AI-enabled governance.
Part 1 asked: “What could Maharashtra build?”
Part 2 asks: “How could Maharashtra build it?”
The next step is to turn the concept into a one-page operating model, organisational structure and 100-day action plan that can be evaluated by the EIT&AI Department and relevant government leadership.
