Post-Deployment Support Models for States

The UAT minutes were signed on a humid Thursday. The SI lead flew out on Friday. On Monday a retrieval index refused to load because a certificate had expired. The only person who knew the passphrase was on a flight. The departmental nodal officer had been transferred the previous week. The AMS annex said L1 L2 L3 as if those words were staff.

State governments already know this pattern from every other IT system. Agent stacks add a new failure mode: the model is up while the packet export is not; the chat is fluent while the corpus is a month stale; the vendor's India phone is answered by someone who cannot enter the air gap.

This comparison is for the officer writing the support chapter of an RFP or a GeM bid. It is not a ranking of firms. It is a ranking of seats: who is physically able to restore, patch, and explain a case when the original project team has dissolved.

Five seats, and what each can actually do at 2 a.m.

Support seats — fill names and roster facts before you score a bid.

Seat	Strength	Typical failure	Ask in the bid
SDC / SeMT operations	Already on the floor; knows power, identity, backup	Treats the agent as another VM; no prompt owner	Named shift, restore drill, who holds model keys
NIC or state NIC unit	Continuity across ministers; standard patterns	Capacity; not every workflow is a NIC product	Written scope: hosting only, or application too
OEM AMS on hardware / runtime	Parts, firmware, hypervisor	Stops at the metal; silent on RAG drift	RMA path into your city; no mandatory outbound call-home
SI AMC / application AMS	Knows the prompts, connectors, eval	People rotate; knowledge in a Slack the state does not own	Named people, shadowing, packet-export without the SI
Hybrid with departmental owners	Survives vendor exit if the paper is real	Owners are additional charge and vanish at transfer	Two named understudies; register updated on every transfer

What support means when the product is an agent

For a mail server, support is uptime and restore. For an agent, add four duties: corpus freshness, prompt and policy version control, packet export for a named case, and a human-gate that still works when the model is down.

Write those four as acceptance tests for the support year, not only for go-live. A vendor who can restart a pod but cannot export last Tuesday's scholarship file is not supporting a government system. They are supporting their own runtime.

CERT-In's log floor still applies. Support staff who ship traces to a personal laptop to debug are an incident, not a workaround. Put that in the AMS.

Money and calendar are design inputs

State budgets lapse. AMC invoices that arrive in March without a sanctioned head become informal WhatsApp support. Write the support year to the financial year you can actually pay, and say what happens on 1 April if the renewal is late — read-only, halt, or continue on departmental staff.

Transfer season is a support event. The bid should require a handover pack the incoming nodal officer can open without the outgoing officer's Gmail. If the only runbook is in the SI's Confluence, you bought a subscription to a memory you do not own.

Monsoon and election duty change who is in the hall. Overnight GPU jobs that need a human in the SDC will fail in those weeks. Design batch windows accordingly.

How to score support without theatre

Do not score 24x7 as a word. Score a tabletop: expire a certificate on staging, name a closed case, and time the restore and the packet. Do it once in UAT and once in month six.

Do not score a global SOC as a benefit if that SOC cannot enter your perimeter. An air-gapped stack with a foreign follow-the-sun desk is a contradiction. Score the desk that can actually type.

Prefer a thinner roster that has entered the hall over a thick escalation matrix of roles with no names. Names can change; the bid should force the update.

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.

We will decide support after go-live

Then you have decided on heroics. Price the seat now. A cheap go-live with no year-two roster is how systems become screenshots.

NIC will take it later

Ask NIC in writing. Later is not a handover. If they will only host, write that. Do not put their logo on application AMS they never signed.

The SI is local, we trust them

Trust is not a restore test. Demand the month-six drill with the named lead on leave.

24x7 is mandatory because citizens are 24x7

Many services are not. Match the charter. An unmanned night desk that cannot enter the air gap is theatre. A documented business-hours roster plus a halt state can be more honest.

Four weeks to a support chapter you can pay for

1. Week 1: list the five seats and put a real organisation against each, including none. Do not leave a blank looking like coverage.
2. Week 2: write the four agent duties — corpus, versions, packet, halt-safe gate — as measurable tests.
3. Week 3: price AMC against the financial year and write the 1 April behaviour. Get finance to initial that paragraph.
4. Week 4: run one tabletop on staging with the people who will actually be rostered, not the bid team. Fix the bid from what broke.

How this shows up in the file

Subject: Post-deployment support seats for agent workflows.

Uptime is not sufficient support. The file shall name the seat responsible for corpus freshness, prompt versions, case-packet export, and a safe halt. SDC hosting, NIC involvement, OEM AMS and SI AMC shall be written as separate seats, not as synonyms.

Renewal against the financial year and handover on transfer shall be stated. This note is an internal aid. It is not legal advice.

Shadowing before the SI lead's flight

Write a two-week shadow into UAT. The departmental understudy performs the packet export and the certificate rotation while the SI watches. If the understudy cannot finish, the UAT is not signed. That single habit kills more theatre than a twenty-page escalation matrix.

Prcept AI will not sell you a follow-the-sun desk that cannot enter your hall. We will put restore, packet export and corpus age into the AMS tests. If our named engineer is the only person who can do those things, we have failed the month-six drill and you should withhold the AMC milestone.

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

How to sequence this in a state, not a slide

“Post-Deployment Support Models for States” is a department problem. A P2 Procurement should name the legacy system, the officer who owns the file, and the citizen charter clock before buying “government IT support model”.

Go-live is a Thursday. Support is the next three summers. Compare who will be in the hall when the officer who signed the UAT has been transferred. Do not invent league tables of states. Read tenders and policies. Election Model Code of Conduct can freeze a rollout. NIC is a partner, not a villain. SDC readiness is GPU, power, ops and egress — not a logo.

• Audit the legacy store first.
• Keep mutation and money as officer actions.
• Map SLAs to the citizen charter.
• Budget change requests after go-live.

Close this loop before the next CAB

Put “Post-Deployment Support Models for States” 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. “government IT support model” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What the next file must contain

“Post-Deployment Support Models for States” earns a line in the noting only if a P2 Procurement can attach proof of “government IT support model.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “government IT support model.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.