Government GeM Tender BOQ Guide for CCTV & Networking: Compliance, Specs, and Vendor‑Neutral Drafting

Why a Vendor‑Neutral BOQ Matters on GeM

GeM (Government e‑Marketplace) mandates transparent, competition‑driven procurement. A BOQ (Bill of Quantities) that favours a single OEM can be rejected for violating the Competition Act, 2002 and the Make in India (MII) policy. This guide shows how to write a technically sound, OEM‑agnostic BOQ for CCTV and networking projects, ensuring compliance with Indian regulations and international security standards.

Core GeM Tender Requirements for Surveillance & Networking

• All equipment must be Make in India certified or have a valid Domestic Content Ratio (DCR) ≥ 40%.
• Cybersecurity clauses must reference Indian Computer Emergency Response Team (CERT‑In) guidelines.
• For any imported hardware, the tender must include a NDAA‑compliant statement (no prohibited Chinese components).
• Each network device must support MAC address binding and 802.1X authentication for endpoint security.
• Documentation must include OEM‑independent performance parameters (resolution, frame rate, storage, PoE power).

Step 1 – Draft Technical Specifications Without OEM Bias

Write specifications in functional terms. Avoid brand names, model numbers, or proprietary protocols. Use the following template:

1. Camera type (e.g., IP dome, bullet, PTZ)
2. Resolution (minimum 1080p, optional 4K)
3. Frame rate (≥ 25 fps for live monitoring)
4. Compression (H.265/H.264, bitrate ≤ 4 Mbps @ 1080p)
5. Night‑vision range (≥ 30 m IR)
6. Power (PoE 802.3af/at, 12 V DC optional)
7. Environmental rating (IP66 for outdoor, IK10 for vandal‑proof)
8. Security features (TLS 1.2, AES‑256 encryption, MAC binding)
9. Certification (MII, CE, FCC, optional UL)

This approach lets the evaluation committee compare offers on equal footing while still meeting performance goals.

Step 2 – Incorporate Make‑in‑India (MII) Certification

KAS Info Tech, an ISO 9001:2015 certified and GeM‑empanelled partner, has delivered over 850 police‑station installations across Rajasthan using MII‑compliant cameras from Hikvision, CP Plus, and Dahua. Follow this checklist to satisfy MII:

• Verify the Domestic Content Ratio (DCR) on the vendor’s certificate.
• Require a Declaration of Origin for each major component (lens, sensor, PCB).
• Include a clause that at least 40 % of the bill of material must be sourced from Indian manufacturers (e.g., chassis, power supplies).
• Ask for the latest MII compliance report (valid for 12 months).

Step 3 – Enforce MAC Address Binding & Cybersecurity Compliance

Network security is non‑negotiable for public‑sector surveillance. The BOQ should mandate:

• All IP cameras and NVRs must support static MAC address binding in the switch configuration.
• Switches must be managed, support 802.1X, and have firmware signed by the OEM.
• Implementation of segmented VLANs for video, management, and guest traffic.
• Periodic penetration testing by a CERT‑In accredited partner (KAS Info Tech offers this as a post‑deployment service).

Step 4 – Address NDAA Restrictions for Imported Gear

The U.S. National Defense Authorization Act (NDAA) bars procurement of equipment containing prohibited Chinese components. To stay compliant:

1. Require a Supplier Declaration confirming no prohibited components (e.g., Huawei, ZTE) are present.
2. Prefer OEMs that publish a Supply‑Chain Transparency Report (Hikvision and CP Plus provide this).
3. Include a clause allowing the agency to audit the supply chain within 30 days of delivery.

Sample BOQ – CCTV & Networking (Rajasthan Police Case Study)

The above BOQ was the basis for the Rajasthan Police tender that secured 850+ station deployments. KAS Info Tech supplied the technical validation, ensuring all items met MII, NDAA, and cybersecurity clauses.

Rajasthan Police Procurement Case Study

Challenge: The state required a uniform surveillance system across 850 police stations, each with limited power and bandwidth. The tender demanded OEM‑neutral specs, MII compliance, and MAC‑binding capability.

Solution by KAS Info Tech:

• Prepared a detailed functional specification matrix (see Section 1) that eliminated brand bias.
• Validated each shortlisted vendor’s MII certificate and performed a Supply‑Chain Risk Assessment for NDAA compliance.
• Implemented a centralized VLAN architecture using Cisco Catalyst switches (OEM‑agnostic reference) with MAC address binding enforced via Cisco ISE.
• Delivered end‑to‑end training for 150+ police IT staff, reducing post‑deployment support tickets by 40 %.

Result: The project was completed within 6 months, under the allocated budget of ₹7.5 million, and received commendation for “best‑practice procurement” from the Rajasthan State IT Department.

Drafting Checklist – Ready for GeM Submission

1. Define functional requirements (resolution, frame rate, storage) without OEM names.
2. Insert MII compliance clause (minimum 40 % domestic content).
3. Specify MAC address binding and 802.1X authentication for all network devices.
4. Include NDAA‑compliant supplier declaration and audit right.
5. Attach a Performance Test Plan (e.g., 24‑hour video retention, bandwidth calculation).
6. Provide a cost breakdown in INR, using realistic market rates (refer to KAS Info Tech price list).
7. State warranty (minimum 2 years on‑site) and post‑installation support (24/7 helpline: +91 80581 22233).
8. Obtain ISO 9001:2015 compliance certificate from the vendor.
9. Submit the BOQ in the GeM portal with proper categorisation (CCTV‑Surveillance, IT‑Networking).

Conclusion

Creating a GeM‑compliant BOQ for CCTV and networking projects is a disciplined exercise in functional specification, regulatory awareness, and risk mitigation. By following the steps above, procurement officers can avoid single‑OEM traps, satisfy MII and NDAA mandates, and secure robust, future‑proof surveillance infrastructure. KAS Info Tech’s proven track record across Rajasthan Police, Indian Railways, and major retail warehouses demonstrates that a well‑crafted BOQ translates directly into successful, on‑time deployments.