The MeitY-NICSI AI Empanelment RFE, Decoded

The slide in the investor update said 'empanelled with MeitY'. The footnote was a screenshot of a news story about reserved startup slots. The live PDF the founder had not opened was an RFE on the Central Public Procurement Portal issued through NICSI. A different tab had the IndiaAI compute empanelment, dated August 2024, for GPU cloud capacity. Two instruments. One slide. Zero chance of surviving a later customer question.

NICSI is National Informatics Centre Services Inc., a commercial arm that can empanel agencies and later issue work orders. NIC is the technical organisation. MeitY is the ministry. IndiaAI is a mission with its own RFEs. Collapsing those four names is the most expensive decoding error in Indian GovTech this cycle.

This teardown shows how to read an AI-related NICSI RFE when one appears, and how to refuse rumours about slot counts that were only ever a feature of a specific notice. It is not the notice. If you are bidding, the live PDF on eprocure.gov.in or the NICSI tender page is the only text that counts.

Four names, four jobs — stop mixing the letterheads

MeitY sets policy and can sponsor missions and RFEs. Seeing MeitY in a headline does not mean the Secretary will be your contracting party.

NIC builds and runs government digital infrastructure. Being 'known to NIC' is not an empanelment. NIC technical opinions and NICSI commercial orders are different papers.

NICSI, at nicsi.nic.in, is the company that publishes many empanelments, maintains vendor lists, and issues work orders to empanelled agencies for user departments. The user department still has a need. NICSI is not a ministry of AI.

IndiaAI Mission published an RFE on 16 August 2024 for empanelment of agencies providing AI compute and cloud services — a capacity instrument aimed at GPUs and cloud AI services over a stated period (coverage around that RFE has described a multi-year, on the order of 36 months, construct; confirm the live document). That RFE is not a ticket to build a district grievance agent under a NICSI application-software empanelment. Do not mash them.

What an RFE is — and what winning it is not

A Request for Empanelment is a filter. You become eligible to receive later work, often at discovered or ceiling rates, often through a second, smaller competition or a direct work order under the empanelment’s SOP. You do not, by being listed, hold a budget.

Press coverage of MeitY/NICSI AI-related empanelment designs has mentioned reserved slots for startups and MSMEs — for example, stories that described up to ten reserved startup seats and a similar MSME idea in a particular design. Treat every number as a feature of that RFE, to be verified on the live notice. It is not a standing law that 'India reserves ten AI slots'.

Empanelment duration, categories (products, services, manpower, cloud, application development), and whether later work is mandatory through NICSI all live in that PDF and in NICSI’s SOP notes. Read those, not a carousel post.

If your investor slide uses one logo for all five rows, redraw the slide before you redraw the product.

Instrument people confuse	Typical object	Typical prize if you win
NICSI category empanelment RFE	Agencies that can take work orders in a defined service category	Eligibility to be issued / compete for NICSI work orders in that category
MeitY/NICSI AI-specific RFE (when issued)	Whatever that notice defined — applications, platforms, services	Whatever that notice defined — never assume a budget
IndiaAI compute / cloud RFE (Aug 2024 lineage)	GPU and AI-cloud capacity for the Mission	Empanelment as a compute/service provider to Mission-approved users
GeM catalogue / bid	A specific purchase by a buyer	A contract and an invoice path
State IT empanelment	That state’s IT dept / corporation list	Eligibility for that state’s later work, under that state’s rules

How to decode the live PDF in one sitting

First page: who issues, on whose behalf, and the CPPP tender ID. If the issuer is NICSI, your contracting path later is likely a NICSI work order, not a MeitY grant.

Eligibility: legal entity, years, turnover, DPIIT/MSME reservations if any, whether consortium is allowed, whether a foreign parent kills you. Copy those sentences into a spreadsheet. Do not summarise.

Scope categories: map your actual product to one category. An on-prem agent is not GPU cloud. A GPU cloud is not a grievance workflow. Applying to the wrong category is a clean fail.

Evidence formats: many NICSI-style RFEs want work orders, CAs, self-declarations on their templates, and sometimes a presentation. Substituting a pitch deck for their Form-X is how technically good firms die.

Commercial: some RFEs are QCBS, some are rate discovery, some are technical empanelment with later rate negotiation under an SOP. The SOP on nicsi.nic.in is part of the reading list, even if it is an older office order. Confirm what still applies.

• Download corrigenda. The reserved-slot paragraph, if any, often moves there.
• Note the validity period of the panel and the last date to add documents.
• Note whether being empanelled creates any obligation to accept later work.
• Note the law of the contract — typically Indian law, Delhi or another stated jurisdiction.
• Note data, security and residency sentences if the category is AI application software.

After you are listed, the work has not started

User departments still have to indent. NICSI still has to issue. You may still face a limited competition among empanelled vendors. Rate cards can be ceilings, not invoices.

Keep the evidence pack warm. A work order six months later will ask for current GST, current manpower CVs, and a deployment note the RFE never needed in that detail.

Do not tell a district collector you are 'MeitY appointed national AI vendor'. Tell them you are empanelled under named RFE ID for named categories, and that their indent still needs sanction.

What we will not claim on a slide

Prcept AI will not treat a compute empanelment as a software empanelment, or a press slot-count as a statute. If we are on a panel, we will name the RFE, the category and the expiry.

If a reserved startup slot exists on a live notice, we will use it only if we meet that notice’s definition of startup on the opening day. DPIIT recognition is usually necessary and not always sufficient.

If we are not on the panel, we will still sell on GeM and on direct campus tenders. Empanelment is a route, not a religion.

Myths that grow around any MeitY/NICSI headline

Pin these to the war-room wall the week an RFE drops.

If NICSI empanels us we are the government’s AI vendor.

You are eligible for work orders in a category. So are the other empanelled firms. The user department still chooses and still pays through the path the SOP describes.

The slot count we saw in the newspaper is the rule.

The live notice is the rule. Press numbers describe a design. Corrigenda change designs. Verify on eprocure / NICSI.

IndiaAI compute empanelment lets us skip NICSI software RFEs.

It does not. Compute capacity and application work are different shops. Holding one card does not open the other drawer.

We can apply in every category to be safe.

Only if you can evidence every category without contradicting yourself. A GPU-cloud claim and an air-gapped-only claim in the same packet will be read together.

One week to decode and decide go / no-go

Start the day the CPPP ID is public, not the day a journalist calls.

1. Day 1: download RFE, annexures, corrigenda. Identify issuer, category, dates, consortium rule.
2. Day 2: split eligibility versus scoring. Map reserved-slot language, if any, to your current DPIIT/Udyam facts.
3. Day 3: map evidence you have versus forms they want. List gaps that cannot close before opening.
4. Day 4: pre-bid questions only on clauses that decide go/no-go.
5. Day 5: commercial read — rate model, later SOP, likely working-capital wait.
6. Day 6: go / no-go memo to founders. If go, open the evidence-pack checklist.
7. Day 7: assign owners. Refuse a second category unless evidence is independently real.

What goes in the file — decode memo, not a screenshot

Write a two-page memo: RFE ID, issuer, category applied, slot language as quoted (not paraphrased), your eligibility facts, gaps, go/no-go. Attach the downloaded PDFs with dates.

If you later tell a customer you are empanelled, that memo is what your sales team is allowed to say. No broader sentence survives.

What the next noting must contain

“The MeitY-NICSI AI Empanelment RFE, Decoded” belongs in a file, not only in a search result. A P5 GovTech Founder should be able to point at one artefact that proves “MeitY NICSI AI empanelment”: a packet capture, a processing schedule, a scored evaluation row, a dated notice, or a refusal rule. If the only evidence is a slide, you have a heading.

NICSI empanelment is not a statute and not the IndiaAI GPU cloud RFE. Decode the live notice: who issues work orders, what evidence counts, and which reserved slots exist only in that RFE. DPDP 2023 does not define sovereign AI and does not write a blanket localisation rule for every model hop. CERT-In’s 28 April 2022 directions still set specified incident clocks and 180-day log retention in India for in-scope events. The November 2025 AI governance text is guidance, not a statute. A Proprietary Article Certificate, when it is lawful, lives in GFR Rule 166 — not Rule 161.

Write three dated sentences under C4 Empanelment & Routes: what was decided, which designation owns it after the next posting order, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the designation that owns “MeitY NICSI AI empanelment”, plus a deputy.
• Attach one artefact a stranger can open next year.
• Name the instrument you are actually using — Act, direction, GFR clause, GeM term, or guideline paragraph.
• Leave unsourced percentages, GMV slides and house forecasts out of the noting.
• Revisit when the model, the SI, the notice, the region or the posting changes.

Empanelment designs change with each RFE and corrigendum. Slot counts reported in the press are not standing statutes. IndiaAI’s August 2024 compute RFE is a different instrument from NICSI application-software empanelment. This article is not the notice and not legal advice. Read the live PDF.