GPU Procurement Lead Times in India, Mapped

Someone will ask you, in a meeting that has already gone too long, how many weeks a GPU takes in India. If you answer with a single integer, you are guessing. Lead time is a function of whether the card or the server is actually listed and in stock on GeM, whether you are buying a whole node from an OEM, whether the accelerator is import-bound, whether your specification is odd, and whether finance will accept a rate reasonableness certificate when the market is moving.

This article is a map of those variables for CIOs writing indents for state data centres, PSU plants and campus DCs. It is not a price list. Prices and stock change. It is not a table of average weeks from a survey we did not run. Whenever you see a range below, read it as a planning envelope that you must replace with a dated quotation and a live GeM search the week you file.

Also remember you may not need the card you first circled. Many collectorate and grievance agents run on CPU if the workflow is draft-and-retrieve rather than image generation. The longest lead time is the one you should not have started.

The routes, not the weeks

Route A is a configuration already sold on GeM as a goods item — a workstation, a server with an accelerator, or a listed GPU where stock is showing. If Rule 149 conditions apply and the item is available on GeM, that is the default store window. Available is a live fact. A catalogue card with zero stock and a twelve-week promise is not a store shelf. Search on gem.gov.in the morning you write the note, take a screenshot, and file it.

Route B is a GeM bid or custom bid for a bill of materials an integrator will assemble. You are now in bid time plus assembly plus delivery plus inspection. Route C is OEM import or high-end data-centre GPU servers that are not sitting in an Indian warehouse. You are now in allocation, freight, customs, and whatever end-use or authorisation paperwork the current export regime requires. Those regimes change. Your OEM's written lead-time letter is the artefact, not a blog. Route D is capacity you do not buy: a share of an existing SDC or NIC cluster, a time-slice on a research GPU, or a CPU-only design. This route's lead time is a political negotiation, not a vessel ETA. It is often the only route that fits a POC calendar.

Envelopes are for conversation. Quotations and live GeM pages are for the file.

Route	What moves the date	Planning envelope (replace with quotes)	Usual failure
GeM listed stock	Actual stock, not the catalogue photo	Can be short if the SKU is in hand; can be indent and wait if not	Treating a listing as inventory
GeM bid / integrator kit	Bid clock, clarifications, kit assembly	Often a quarter-shaped object once you add inspection	Spec so unique that only one kit exists
OEM import / DC GPU node	Allocation, freight, customs, end-use paper	Can exceed a fiscal year for scarce SKUs; do not invent a week count	Verbal assurance from a sales engineer
Share existing capacity	Whose job gets delayed	Weeks of meetings, not boats	No written share, so the card vanishes on quarter-end
Do not buy — CPU design	Model choice and eval honesty	Engineering weeks, not import weeks	Quietly assuming a GPU will turn up

Specification games that add months

Naming a single consumer SKU that a local shop can buy but a government file cannot easily inspect. Naming a data-centre SKU that no GeM seller will bid because they cannot get allocation. Mixing liquid cooling into a room that has none. Requiring a brand when an equivalent accelerator would do. Each of these turns a goods purchase into a negotiation.

Write performance and interface needs (VRAM class, power, cooling, driver support for the runtime you already chose) and let bidders offer listed equivalents. If you truly need one SKU, say why in the note and accept that you have narrowed the market. Do not forget the boring companions: risers, PSUs, rails, optics, the server that can actually host the card, and the AMS / warranty shape GeM or the OEM will honour in your city. A card without a host is a paperweight with an invoice.

How to put dates in the note without inventing statistics

Attach three artefacts: a dated GeM search (or a sentence that the SKU is not available there), a written OEM or integrator lead-time letter with a quotation date, and your own critical-path list (bid opening, inspection, rack, acceptance). If those three disagree, the note should say so and pick the conservative path for any public commitment.

Never brief a minister with a single week-count pulled from a WhatsApp. Brief the route and the artefacts. If the political need is sooner than the conservative path, change the architecture (CPU, shared SDC, smaller workflow). Do not change the vessel's ETA by optimism. Re-check stock the week of award. GPU markets move. A listing that was true in April may be vapour in July.

1. Decide whether you need a GPU at all for the first workflow.
2. Search live GeM and file the screenshot.
3. Ask two routes for written, dated lead times — do not average verbal ones.
4. Write cooling, power and host server into the same indent.
5. Commit publicly only to the conservative artefact.
6. Revisit stock and allocation before you promise a go-live.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Just tell us the number of weeks.

A number without a route is a guess you will have to eat. Bring the GeM screenshot and the OEM letter. If leadership still wants a number, give the conservative artefact's date and label it as that artefact's date.

We will buy from the local grey market to save time.

A government file that rests on grey-market serial numbers is a future CAG conversation. If time is the constraint, change architecture or borrow under a movement order. Do not launder a shop-counter card through a technical committee.

Cloud GPUs in Mumbai solve lead time.

They solve hardware lead time and reopen the outbound and tenancy questions this cluster of articles exists to answer. Say that trade explicitly. Do not smuggle it in as a procurement convenience.

A two-week indent that does not invent a market

1. Day 1–2: confirm the workflow actually needs a GPU; write the CPU alternative.
2. Day 3–5: live GeM search, OEM/integrator letters, power/cooling survey of the room.
3. Day 6–8: choose a route; write why others were not chosen.
4. Day 9–10: file screenshots and letters; set a revisit date before award or go-live.

How this shows up in the file

The indent should carry the route, the dated artefacts, the conservative public date, and the fallback if allocation slips. A later CIO should see why you did not wait for a mythical SKU. Update the file when stock changes. A stale screenshot is how optimism becomes a lie.

Inspection, acceptance and the week after the box arrives

Lead time does not end when the courier calls. Government acceptance can add a burn-in, a serial-number check, a stock entry, and an argument about whether the card in the box matches the bid. Write acceptance tests in the indent. A box that sits in a store for three weeks because nobody booked the inspection is still your lead time. It just changed rooms. Warranty and on-site versus return-to-base matter more in a district than in a Bengaluru DC.

Sharing and time-slicing without a fist-fight

If route D is a share of an existing cluster, write the share: which hours, which queue, whose job loses, who can preempt, what happens at quarter-end when the owner wants the card back. Verbal shares evaporate. A one-page MoU between two government units is ugly and useful.

Export controls and what you should not role-play

High-end accelerators can sit in export-control conversations that change. Your job is not to interpret another country's regulation in a blog sentence. Your job is to ask the OEM for a written statement on whether they will sell the quoted SKU to your legal entity for your stated end use, and in what envelope of time. File the letter. If the letter is mush, treat the route as hostile to any public date. Do not ask a local shop to get the same card as a way around a letter. Serial numbers have memories. So do auditors.

This article is informational field guidance for Indian public institutions, not legal, procurement or engineering advice. Confirm against the current Gazette, GFR, GeM portal terms, OEM quotations and your counsel before you file it.