Deciding Between AMC and Subscription Terms

A PSU in Vadodara bought GPUs, a rack, and a set of weights. The commercial schedule said three-year AMC, the way the last SCADA buy had said AMC. The vendor's 'AMC' included a mandatory support tunnel, a licence that died if the heartbeat failed, and a model-update stream that was priced per million tokens. On month four the tunnel was the product. The metal was a prop. Finance asked why an annual maintenance contract was paying for a hosted service. Nobody had a sentence.

This is a comparison for commercial cells and programme owners. Annual maintenance, in the Indian government habit, fits goods and owned stacks: you already bought the thing; you are paying to keep it patched, spare and attended. Subscription fits services you do not own: a seat, a token, a hosted model, a cloud SIEM. Agent platforms sit awkwardly in the middle. Hybrid is allowed. What is not allowed is lying to the file about which object you bought.

Air-gap claims and subscription heartbeats fight. If you need isolation, a pure SaaS subscription is usually the wrong instrument. If you need continuous model improvement from a vendor garden, an AMC on silent metal is the wrong instrument. Write the true mix.

Not legal advice. GeM category choice, GFR, and your accounts code still decide how the bill is classified. Read the live category and your PAO.

What each word is for

AMC assumes an asset on your books or at least in your custody: servers, an appliance, a licence file you can run offline, a codebase in escrow. The vendor's job is uptime, patches, spare parts, and a named response. If the asset cannot run when the vendor is unreachable, you do not have an asset. You have a subscription with a capital invoice at the front.

Subscription assumes an ongoing service: hosted inference, managed updates, a shared safety filter, a cloud console. Payment buys access, not a thing you can switch off the WAN and keep. That can be the right buy for a public catalogue search with no personal data. It is a hard buy for an air-gapped citizen file.

Hybrid is common and honest: you buy an appliance or a software licence (goods or a perpetual-ish right), plus a subscription for updates or for a hosted overflow, plus an AMC for the metal. Each line should stand if the others die. If the AMC is meaningless without the subscription, it is one subscription, split for optics.

Pick the row that matches the architecture you already wrote, not the row that matches last year's SCADA file.

If the architecture is…	Commercial shape that fits	Shape that fights the architecture
Owned on-prem / air-gapped runtime, offline licence, local logs	Licence or appliance + AMC for patches, media, on-call	Per-token SaaS with a heartbeat
Hosted model, vendor SOC, India-region or otherwise	Subscription with DPA, location, exit	AMC language that pretends you own the model host
On-prem runtime + hosted overflow for non-personal load	Hybrid: AMC on the box, subscription on the overflow, hard split of data classes	One blended fee with no split
Perpetual licence that still phones a garden	Rewrite the architecture, then pick	Either label — the phone-home is the real term

Air-gap and subscription often hate each other

A subscription that must meter tokens, validate seats, or push weights from a garden needs a path. That path is outbound. You can design a sneaker-net subscription — updates on media, billed annually, no heartbeat — but then you are back to an AMC with a different invoice title. Call it that.

If the political note demands air-gap and the commercial note demands a cheap per-query price, one of the notes is false. Bring them into one room before the bid.

What to put in each schedule so accounts can live with it

AMC schedule: asset list, patch cadence, media format, response times, spare GPU or spare appliance terms, exit assistance, and a statement that the stack runs if the vendor is unreachable for 90 days.

Subscription schedule: unit of measure, data classes allowed on the hosted side, location, training ban, subprocessors, exit export, and what happens when you stop paying (you lose access; say so).

Do not put manpower theatre in either schedule as a substitute for those artefacts. Headcount is not uptime.

• One line in the BoQ per object: metal, licence, hosted overflow, professional services.
• A 90-day vendor-unreachable test for anything labelled AMC.
• A data-class split for anything labelled subscription.
• A sentence on what happens to logs and embeddings when the term ends.

Price reasonableness changes with the object

You cannot benchmark an AMC against a SaaS list price and call it L1 logic. Compare AMC to other AMCs on similar owned stacks. Compare subscriptions to subscriptions with similar isolation and liability. A cheap subscription that fails the air-gap note is not cheap. A heavy AMC on a box that still phones home is a subscription with a capital disguise.

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.

Accounts only know AMC.

Then teach the object, or split the invoice so accounts can book an asset line and a service line. Do not mutilate the architecture to fit a familiar form. PAOs learn new objects when the note is clear.

Subscription is how we stay current on models.

Then buy a subscription for updates, on media or on a named hop, and keep production inference on the owned stack if isolation matters. Currency is a schedule. It is not a reason to surrender the runtime.

AMC is safer from a vigilance point of view.

AMC on a fake asset is not safer. It is a misdescription. Vigilance reads the architecture. Describe the buy you made.

We will decide AMC versus subscription after L1.

The shape changes who can bid and what DPA you need. Decide it in the RFP. Post-bid shape-shifting is how complaints are born.

A one-week commercial shape decision

Sit procurement, the SDC owner, the DPO and accounts in one meeting. The architecture PDF is the agenda.

1. Day 1: mark every component as owned-runnable-offline or hosted-access.
2. Day 2: assign AMC, subscription or professional services to each component. Kill blended fees.
3. Day 3: write the 90-day unreachable test for AMC lines and the data-class split for subscription lines.
4. Day 4: check GeM / CPPP category fit for each line. Do not force a goods code onto a hosted brain.
5. Day 5: note to the competent authority: this is the shape, and why last year's SCADA AMC is the wrong stencil.

How this shows up in the file

The note names the objects, the instrument for each, and the test that proves the label. It says air-gap and heartbeat cannot both be true for the same component. It says hybrid, if used, splits data classes.

If the vendor insists on one blended 'platform fee', ask them which components die when you stop paying. That answer is the real commercial shape.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation or engineering advice. Confirm against the current Gazette, GFR, GeM term, CVC instruction, CERT-In direction, DPDP text, departmental manual and your counsel before you file it.

How to put this in the RFP, not the preamble

A P2 Procurement who searches “AMC vs subscription government” is usually drafting or scoring a bid. “Deciding Between AMC and Subscription Terms” belongs in eligibility, the evaluation matrix, or a numbered annexure. If it only lives in the covering note, L1 will ignore it.

If you own the stack, AMC can keep it alive. If you are renting a brain in another network, you are in a subscription, even if the BoQ says AMC. Hybrids exist. Name the object. QCBS weights are a choice you must publish before opening. Accuracy is a task plus a dataset, not a slogan. SLAs for agents must name tool-calls, human gates and log export — uptime alone is a hosting metric.

Do not let a vendor write the specification and then bid on it. Record unsolicited proposals. Pay for pilots that touch personal data. Write exit before you write go-live.

1. Move the control from the preamble into a scored or eligibility row.
2. Attach a one-page definition (accuracy, SLA, language, data handling).
3. Require an artefact in the technical bid, not a slide.
4. Extend the bid date if a corrigendum is material.
5. Minute the demo on your data, offline if you claimed air-gap.

Close this loop before the next CAB

Put “Deciding Between AMC and Subscription Terms” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P2 Procurement, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “AMC vs subscription government” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.