Timeline Realism in AI Tender Schedules

A mission director promised the chief secretary an air-gapped grievance agent 'before the next collection season'. The tender schedule gave six weeks from award to go-live, because a vendor demo in a hotel ballroom had taken forty minutes. The GPU quote that later arrived said allocation subject to export and a lead time measured in many weeks. The media SOP for the SDC did not exist. The SIEM team was mid-migration. The collection season arrived. The agent did not. The file now contains a explanation that begins 'due to unforeseen supply-chain issues', which is how departments describe clocks they refused to write down.

This is a qualitative field note, not a study. There is no honest national dataset that says 'an air-gapped agent POC takes N days'. Anyone who puts a fake N in a blog is selling certainty. What we can say, from the same kinds of files repeatedly, is that three clocks dominate and they are longer than a hosted SaaS pilot: physical media and isolation drills, accelerator or even CPU capacity that is actually on a government floor, and a log landing zone a SOC will accept. Write those clocks into the tender schedule. Do not write a ceremony date and hope the clocks feel ashamed.

Not legal advice and not a project-management certificate. Your indent, GeM delivery terms and finance concurrence still govern. This article is the conversation to have before the schedule is printed.

The three clocks a hosted demo hides

Media and isolation. If you mean air-gap, someone must write a media SOP, approve a courier or diode, hash the images, populate an internal registry, and run a soak with default-deny egress. That is not a weekend. It is policy plus bored engineers. A demo on a travel router with the SIM removed is not a data point on this clock.

Capacity. A silent GPU in a hotel is not a delivery date. Government indents, GeM availability, import paperwork, even a share of an existing SDC cluster, all have queues. CPU-only designs can be faster if they fit the eval. They are still not instant if the SDC has no spare power or rack space. Write the route: buy, share, or shrink the model. Each route has a different clock.

SIEM and identity. An agent that cannot land logs, and cannot attach to the department IdP, will be blocked by the CISO on the week you reserved for 'user training'. The SOC's queue is a clock. So is a joiner-leaver integration. Put them on the Gantt or they will sit on the critical path in silence.

Qualitative only. Use this to force a named owner and a honest predecessor, not to quote a national average.

Work the demo hides	Why it is longer than a hotel demo	What to put in the schedule
Media SOP + first hashed drop	Policy, courier, malware scan, two signatures	SOP approved before award or as a dated condition
Internal registry and isolated soak	Staging VLAN, pcap, 14-day licence interval	Soak complete before any production data
Accelerator or rack share	Indent, GeM, export, or a political share of an SDC queue	Named route in the bid; no silent 'customer to provide GPU'
SIEM landing + IdP	SOC backlog, schema fight, joiner-leaver	Landing zone owner named in the RFP
Held-out Indic eval	De-identification, rubric fights, officers' time	Set frozen before bid, not 'during implementation'
DPA and role map	Counsel queue, subprocessor list, training-ban redlines	No production data until signed — write the wait

POC, pilot, production — three different calendars

A POC on synthetic or public data can be short if the room and the model already exist. A pilot on production-like data is processing. It needs a DPA, a purpose, and usually a paid scope. Production needs restore tests and a human-gate design. Collapsing the three into 'go-live in six weeks' is how you skip the DPA and call it agile.

If political time is genuinely short, shrink the object: one language, one workflow, CPU if it scores, human gate on every send, no air-gap claim you cannot prove. A small true thing beats a large ceremony.

How to write the schedule in the RFP

Use predecessor language, not only dates. 'Isolated soak completes before production connector' is a rule. 'Go-live 15 November' is a wish. Wishes become liquidated damages that everyone later waives, which teaches bidders that your dates are decorative.

Ask bidders to submit a clock they will be held to, with the three hidden clocks visible. A bidder who says six weeks and also says 'customer to provide GPU, SIEM, media SOP and IdP' has not offered a six-week delivery. They have offered a six-week install after your unknown queue.

If you use liquidated damages, attach them to missed predecessors that the vendor owns, not to a ceremony the chief secretary picked.

• Name the department-owned predecessors and their owners.
• Forbid 'customer to provide GPU' without a dated indent path.
• Keep production data behind the DPA, even if the ceremony moves.
• Publish a short-scope fallback if the long-scope clock slips.

What this article is not

It is not a claim that hosted SaaS is always faster in a way you should accept. Hosted can be faster to a demo and slower to a defensible DPA. It is not a claim that GPUs always take a specific number of weeks — that number moves, and quoting a stale one would be a fake study. It is not permission to skip competition because timelines are tight. Tight timelines are a reason to shrink scope, not a reason to hand a vendor a PAC you cannot defend.

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.

The minister has announced a date.

Then take a one-page clock to the minister: what can be true by that date, what cannot, and the false sentence you are being asked to print. Most political offices prefer a smaller true launch. Give them that option in writing.

Other departments did this in a month.

Ask what they actually launched. A hosted FAQ with no personal data is not your air-gapped grievance agent. Do not import their calendar without importing their object.

Vendors will pad any honest schedule.

They might. That is why you ask for predecessors, not a single blob of weeks. Padding is visible when the soak, the media drop and the SIEM landing are separate lines.

We can parallelise everything.

You can parallelise writing and procurement. You cannot parallelise a GPU that is on a ship with a soak that needs the GPU. Honesty about the critical path is not pessimism.

A two-sitting schedule that can be printed

Sitting one is technical. Sitting two is political. Do not mix them or the date will win.

1. Sitting 1: list media, capacity route, SIEM, IdP, DPA, eval set. Name owners and unknown queues. No dates yet.
2. Between sittings: each owner returns a range, not a hero number.
3. Sitting 2: pick a scope that fits the political date, or pick a date that fits the scope. Write the fallback.
4. After: print predecessors in the RFP. Brief the evaluation committee not to score fantasy calendars as a benefit.

How this shows up in the file

The note lists the three clocks, the owners, and whether the political date forced a scope cut. It says no production data moves to hit a dais. It says the schedule is qualitative and local, not a cited national average.

If someone later writes 'unforeseen', the file should be able to show the clock was foreseen and ignored, or foreseen and accepted. Both are better than amnesia.

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 “AI project timeline tender” is usually drafting or scoring a bid. “Timeline Realism in AI Tender Schedules” belongs in eligibility, the evaluation matrix, or a numbered annexure. If it only lives in the covering note, L1 will ignore it.

A six-week air-gap POC is usually a hosted demo with the WAN unplugged for an afternoon. Media, GPU lead time and SIEM landing have their own clocks. Write those clocks, not a ceremony date. 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 “Timeline Realism in AI Tender Schedules” 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. “AI project timeline tender” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.