Procurement Support — GeM, CPPP, Limited Tenders

The single most common mistake in AV procurement is not made on the portal. It is made the week before. A solution that only works as a system gets quietly broken up into a list of line items, for the purchase section’s convenience. Every later difficulty traces back to that one cut. The wrong bidders show up. The L1 race favours commodity resellers. The system fails to cohere at commissioning. The audit query lands six months later. This page is about protecting against that cut.

01Before the portal, one decision

A bespoke conference room is not a digital signal processor plus an amplifier plus a handful of speakers plus a switcher plus a control processor plus cabling. Procured line by line, that list will pass file audit and fail at commissioning. The same is true of a hybrid classroom, an auditorium upgrade, a command centre. The parts are substitutable. The system is not.

The officer’s first decision is architectural. Is this being procured as a system, with one vendor responsible for integration and commissioning from start to finish? Or as a list, with the institution itself carrying the integration risk between vendors? Only the first is a realistic option for any room where audio, video, and control are meant to behave as one.

The rest of this page is about the portal mechanics that preserve that principle — and the ones that quietly break it.

02Four realistic portals

Four procurement portals cover almost every situation institutional buyers face in India. Each has its own compliance envelope. Each leaves its own audit trail.

CPPP — the Central Public Procurement Portal — is used by central ministries, departments, and autonomous bodies. State government e-procurement portals each run their own mechanics. The rules track the General Financial Rules closely, with state-level variations. IREPS — the Indian Railway e-Procurement System — serves the Railway Board and the zonal railways. GeM — the Government e-Marketplace — is by volume the dominant portal for most non-railway institutional buyers today.

On the first three — CPPP, state portals, IREPS — an integrated AV solution is straightforward to procure correctly. The scope of work carries the full technical specification. Bidders comply with that specification in their technical bid. Evaluation is on compliance and price. The solution holds together because the tender document, not the portal, defines what is being bought.

GeM is different, and the difference matters.

03GeM: the catalogue trap, and the two routes around it

GeM is catalogue-first by design. Its default flow invites a buyer to search the catalogue, add SKUs to a cart, and place an order. For commodity goods — stationery, furniture, standard hardware — this is efficient and appropriate. For an integrated AV solution it is a trap. The path of least resistance on the portal is almost always the wrong path for the room.

Three routes exist on GeM. Only two are correct for AV.

Catalogue-cart bunching — the wrong route. The buyer adds individual products to the bid as separate line items. Each line gets its own specification and its own L1 evaluation. The result is adversarial selection. The bid invites product resellers rather than system integrators. A reseller can quote the lowest per-item price on catalogue SKUs without carrying integration, commissioning, or any post-installation responsibility. Cabling gets priced against amplifiers. Acoustic treatment gets evaluated against interactive flat panels. At commissioning, no single vendor owns the room. When the room fails to behave as a system, no one is accountable. This route looks efficient on the purchase file. It fails in the room.

BoQ-based bid — the correct default. The buyer publishes a full Bill of Quantities as part of the bid document, with the solution specified as one integrated scope of work. Bidders quote against the complete BoQ, not against individual catalogue SKUs. Evaluation is on compliance with the BoQ plus price. This route holds the solution together on GeM. It invites system integrators rather than resellers. It leaves a clean, defensible audit trail. For most institutional AV requirements routed through GeM, this is the route.

Custom bid — for genuinely bespoke solutions. Some solutions are customised enough that even a BoQ would be a simplification. A multi-room command centre. A large auditorium upgrade with acoustic intervention. A campus-wide hybrid classroom rollout. For these, GeM permits a full custom bid, with scope of work, technical specifications, and evaluation criteria all defined bespoke. This is functionally equivalent to a CPPP open tender, routed through the GeM portal.

The practical rule is simple and admits no exceptions. An integrated AV solution is not available on GeM as a catalogue item. It never will be, because the scope changes with every room. A GeM procurement for such a solution must take the BoQ route or the custom bid route. The catalogue-cart route is not a shortcut. It is a different procurement altogether, and almost always the wrong one.

04Below the tender threshold

Two routes exist below the open-tender threshold. Both are legitimate when used correctly.

Limited tender is appropriate where the solution requires specialised capability held by a small pool of qualified vendors. That pool must be identified through a documented process — empanelment, prior work on comparable projects, or a technical shortlist approved at the appropriate level. The defensibility of a limited tender rests entirely on the quality of that empanelment documentation. Used correctly, it is a clean route. Used to paper over a closed preference, it is where vigilance queries begin.

Direct purchase is appropriate below the threshold set by the institution’s delegation of financial powers. The single-vendor justification must be recorded on the noting sheet and stand up at audit. For small recurring AV requirements — additions, modifications, break-fix work on an existing installation — direct purchase from a vendor already associated with the institution is often the cleanest route. Frequently, it is the only sensible one.

Neither route is a way around the open-tender process. Both are documented pathways with their own compliance envelope. Both require more defensive paperwork than the portal routes, not less.

05A spec framework for your actual room

A general model-specification library is not published on this site. Institutional AV solutions vary too much from room to room — in geometry, acoustic envelope, existing infrastructure, and institutional workflow — for a static template to be genuinely useful. A misleading template is worse than none.

Write to us with your room and your intent. A spec framework, drafted under independent AVIXA CTS-D and CTS-I supervision, will be returned for your actual requirement. It is technical scaffolding — the basis on which your purchase section can build a compliant tender document. On CPPP, on a state portal, on IREPS, or as a BoQ or custom bid on GeM.

Pre-sales, for a spec framework

pre-sales1@eapltechnologies.com

Typical response within four working days. A subject line that helps triage: Spec Framework — [Institution] — [Room Type].

The framework is not a tender template. What you do with it afterwards is entirely your procurement, on your portal, under your institution’s rules.

The rest of this page — the portals, the routes, the thresholds, the email address for a spec framework — is in service of two sentences worth repeating:

Procure the solution, not the parts. Procure it through the pathway you can defend.

Every institutional AV procurement that goes wrong goes wrong because one of those two sentences was relaxed. Under deadline pressure. Under the purchase section’s convenience. Under the default flow of a catalogue-first portal. The discipline of procuring AV well is the discipline of not relaxing them. The rest is portal mechanics.