evidoria

← Back to browse

Good practice Imported

AI Curriculum Taskforce — India's MeitY-NASSCOM 'Triple Helix' Overhaul of the National B.Tech AI Curriculum

India · New Delhi · See the India profile · See the New Delhi profile

Evidence: Descriptive / self-reported Top 40% 53/100 · Ask Evidence Copilot about this practice

India's MeitY and NASSCOM's AI Curriculum Taskforce completed a national baseline study of B.Tech Computer Science programmes (May 2026) and recommended a 'triple helix' overhaul raising practical AI exposure from 25–30% to 40–75% and embedding Responsible AI in every semester.

25-30%
Current practical AI exposure in B.Tech CSE curricula (baseline) (as of May 2026)
40-75% (depending on specialisation)
Recommended practical AI exposure target
AI Curriculum Taskforce — India's MeitY-NASSCOM 'Triple Helix' Overhaul of the National B.Tech AI Curriculum

Details

Promoter
Ministry of Electronics and Information Technology (MeitY) & NASSCOM AI Curriculum Taskforce
Period
May 2026
Keywords
government, higher education, IT industry, curriculum reform

Context

India's Ministry of Electronics and Information Technology (MeitY) and NASSCOM formed a joint AI Curriculum Taskforce with industry experts to review Bachelor of Technology (B.Tech) Computer Science and allied programmes at Indian institutions, with findings reviewed by Union Minister Ashwini Vaishnaw on 28 May 2026.

Objectives

To overhaul the national B.Tech AI curriculum, closing gaps in Generative AI, MLOps and foundational-model teaching, raising practical AI exposure, and embedding Responsible AI and AI governance throughout every semester rather than as a standalone module.

Activities

The Taskforce completed a baseline study of existing B.Tech CSE programmes and recommended replacing lecture-based teaching with industry use-case learning from the first semester, a credit-linked semester-wise rollout with certificate, diploma and advanced-diploma exit points, capstone projects, structured train-the-trainer schemes, industry professionals as adjunct faculty, and a 'triple helix' government-industry-academia model for shared access to GPUs, edge devices and software platforms.

Results

The baseline study found that while AI content had expanded, most courses still under-taught Generative AI, MLOps and foundational-model development, with only 25-30% practical exposure; the Taskforce recommends raising this to 40-75% depending on specialisation.

Conclusions

This is a substantial national curriculum-reform recommendation package agreed in principle, with next steps toward formal AICTE adoption, but it remains at the pre-implementation stage with no evaluated results yet.

Implementation

Indicative cost
High (€500k–€5M) — Implies significant shared infrastructure investment (GPUs, edge devices, software platforms) across colleges; not itemised in sources.
Time to results
Long (> 3 years) — Baseline study completed by May 2026; phased rollout planned for semesters 5-8 of ongoing B.Tech batches and full integration for new cohorts, with the timeline still being finalised.
Staffing & skills
MeitY officials, NASSCOM, industry professionals as adjunct faculty, AICTE for formal adoption, college faculty for train-the-trainer schemes

Conditions for success

  • triple-helix government-industry-academia collaboration for shared GPU, edge-device and software access
  • structured train-the-trainer schemes and industry professionals as adjunct faculty
  • credit-linked, semester-wise rollout with certificate/diploma exit points to manage phased adoption

Common failure modes

  • still at recommendation/baseline-study stage with no student outcome data
  • formal AICTE adoption timeline not yet finalised as of the meeting

Where it fits

Governance type
government-industry-academia triple helix
Scale
national, all B.Tech CSE programmes
Income level
lower-middle income

Commonly funded by

National / regional programmes

Indicative funding routes for practices of this type — always check each programme's current calls and eligibility rules.

Do you run this practice? Claim it — verified implementers get a public contact pathway and can propose corrections.

Data sources

Where this practice's information was retrieved from, and when.

Attachments

Similar practices you may find useful