Reading GeM's Terms for Software Warranties

The ATC said 'warranty: 12 months from the date of installation' because that sentence had lived in the department’s hardware bids since 2014. The seller accepted. In month four the agent began citing a superseded circular in citizen drafts. The stores section opened the warranty clause and discovered it spoke about defective goods, replacement, and on-site repair of equipment. Nobody had defined a defect in a model output.

GeM’s marketplace terms, service SLAs and bid-specific ATC do not form a single novel about software quality. They form a stack. The general terms handle offers, delivery, incidents and payment. Category SLAs may talk about uptime for a hosted service. Your ATC is the only place an agent-specific promise becomes markable. If you do not write it, you will try to squeeze a cognitive failure into a printer warranty and lose.

This teardown is for buyers who will sign, and for sellers who must not promise a hardware warranty they cannot perform. It is not a restatement of GeM’s legal pages. Those pages change. Open them. Then use the questions below to see what is still missing.

Three layers of promise, not one warranty box

Layer one is GeM’s general terms and the instrument you used — direct, bid, SLA contract. They allocate portal process, delivery acknowledgement, and incident consequences. They are not a specification of your agent.

Layer two is any category service-level language: response times, uptime, replacement of a failing subscription. Useful for a hosted seat. Awkward for an air-gapped install whose 'uptime' is a rack the department owns.

Layer three is your ATC and the seller’s technical bid. This is where warranty, defect-liability, maintenance, model-update policy, and exit have to be written in nouns. If layer three is empty, layers one and two will be asked to do work they were not drafted for.

What 'warranty' usually means — and what it will not do for an agent

In goods language, warranty is a promise that the article is free of manufacturing defects for a period, with repair or replacement as the remedy. Software can borrow that shape for installers that will not boot, connectors that will not authenticate, or a documented feature that is simply absent.

Software warranty is a weak tool for judgement quality. An agent that drafts a legally wrong notice may be working as designed and still be unacceptable. You need acceptance tests, human-in-the-loop duties, and a defect definition that includes 'material failure to meet the published evaluation set' — not only 'will not power on'.

Do not confuse warranty with AMC, ATS, or a reserved-instance support contract. Warranty is often included in the supply price for a limited period. Maintenance after that period is a separate commercial object. If you need four years of model updates on an air-gapped rack, write the update path and the years. A twelve-month hardware sentence will not smuggle them in.

Copying the left column from a printer bid leaves the right column empty. The right column is the purchase.

Phrase in the bid	What it reasonably covers	What you still need to write for an agent
12-month warranty from installation	Install fails, documented feature missing, critical defect repair	What 'installation' means on an SDC; what a critical defect is for outputs
On-site support next business day	A person or remote session as the instrument allows	Whether air-gap forbids remote; the jump-host rules; media for patches
99.5% uptime	A hosted service the seller controls	Who owns power, GPU, identity, and the network — usually you
Free upgrades during warranty	Patches the seller chooses to ship	Whether model weights change; who tests; who accepts; no silent training
Source-code escrow if default	Only if you actually contracted escrow	What is deposited — app, prompts, IaC, weights you are allowed to hold
Indemnity for IP	Third-party IP claims, if the clause exists and is scoped	Training-data provenance and output takedown process

Acceptance is when the warranty clock should start

Installation is the wrong clock if installation means 'containers scheduled'. Write provisional acceptance after a documented test on agreed scenarios, then final acceptance after a quiet period. Start warranty from the acceptance you defined, or you will spend six of twelve months arguing that the system was never really installed.

For agents, the test set is part of the specification. Include a small gold set the department owns: ten grievance drafts, five retrieval questions, two refusal cases. Warranty then has something to bite on besides feelings.

Sellers should not accept a warranty clock that starts on GeM delivery acknowledgement when the department has not provided the VLAN, identity or data. Split seller-caused delay from buyer-caused delay in the ATC. Otherwise both sides will file incidents in month two.

Updates, training, and the day the contract ends

Write whether the seller may change model weights during warranty. A silent upgrade that alters behaviour is not a gift. It is an untested release. Air-gapped buyers need a media path and a rollback.

Write that department data, prompts and traces are not used to train a general model. Warranty language about 'improvements' has been used by hosted vendors to justify exactly that. If you do not forbid it, do not be surprised.

Write exit: export of configurations, deletion certificate, return of media, and how long logs remain. A warranty that expires without an exit clause leaves the department running a black box they no longer have a right to support.

• Define defect classes: install, security, material quality against the gold set, documentation.
• Define remedies: fix, workaround, fee credit — not only 'replace the goods'.
• Define what is excluded: department-written prompts, third-party systems, hardware the buyer owns.
• Define update control: no production weight change without a signed release note.
• Define the no-training sentence in the same section, so it is not lost in a privacy annex.

How sellers should read the same page

If the ATC is a printer warranty, either ask a pre-bid question or price the risk of an undefined defect. Do not assume you only owe boot success.

If the ATC demands source-code escrow of foundation-model weights you do not have a right to deposit, say so in pre-bid. Promising escrow of weights you cannot escrow is a future default.

If uptime is written as if you own the SDC, qualify it in the technical bid to the components you control, or you will own every power cut.

Why rooms resist writing software sentences

These objections keep printer warranties alive. They are how month-four arguments are scheduled.

GeM terms already cover warranty. We should not clutter the ATC.

GeM terms cover marketplace process. They do not know your gold set, your air gap, or your no-training rule. Clutter is a clause you cannot mark. These sentences are the opposite.

If we define defects too clearly the sellers will inflate price.

They will price a known duty. The alternative is an unpriced fight in month four, plus an incident. Known rupees are cheaper than a stalled public service.

Warranty and AMC can be sorted after go-live.

After go-live you have leverage only if the contract said so. Post-award 'sorting' is either a new procurement or a gift. Write the years now.

Source-code escrow will solve quality.

Escrow solves a default-and-disappear problem, and only for the artefacts you actually deposited. It does not make a model correct. Do not treat escrow as a substitute for acceptance tests.

Five days to replace a printer warranty with a software one

Do this while the ATC is still a draft, not after L1 is visible.

1. Day 1: open the live GeM terms for your instrument and list what they already say about warranty, SLA and incidents. Do not paraphrase from memory.
2. Day 2: write defect classes and remedies for install, security, and gold-set quality. Define acceptance and the warranty start.
3. Day 3: write update control, no-training, and the air-gap patch path if relevant.
4. Day 4: write what happens after warranty — ATS/AMC years, or an honest end date.
5. Day 5: legal and CISO read. Remove any uptime sentence that assumes the seller owns your rack.

What goes in the file beside the GeM printout

File the live terms you relied on (downloaded that week), the ATC warranty section, the gold set used at acceptance, the acceptance certificate that starts the clock, and any release notes for weight changes during the period.

If you later raise an incident, quote the ATC defect class, not a feeling that 'the AI is bad'. Feelings are not warranty claims. Clauses are.

GeM terms, category SLAs and ATC text change. This teardown is not a restatement of portal legal pages and not legal advice. Download the current terms from gem.gov.in for the instrument you are using and have counsel read them against your ATC.