Publication / document availability
29-Aug-2026 04:30 PM (IST).
Loading
Loading…
Loading…
DC-PDD · Srinagar, Jammu And Kashmir2026_PDD_322698_1
Written by TenderKart AI from the documents published when it was generated. Check the tender for later corrigenda before you bid.
29 Aug 2026
25 Sept 2026
₹1.6 L
All important dates as they stand after corrigenda: publication, pre-bid/clarification deadline, bid submission deadline, bid opening, and bid validity period.
29-Aug-2026 04:30 PM (IST).
Online pre-bid meeting: 03-Sep-2026 02:30 PM (IST). No separate calendar deadline for written queries is stated in the issued NIT/SBD; Clause 8.6 only points to the NIT/portal.
Submission starts 09-Sep-2026 04:30 PM and closes 25-Sep-2026 03:00 PM (IST), as amended by Corrigendum 1.
26-Sep-2026 11:30 AM (IST), as amended. Financial opening is separately notified only to technically qualified bidders.
180 calendar days from bid opening, extendable by up to 90 calendar days by mutual written consent; EMD validity must be extended correspondingly.
Tender value or estimated cost, EMD/bid security (amount, acceptable forms, validity), tender document fees, performance security, and key payment terms.
Rs. 80 Lacs, inclusive of GST.
Rs.1,60,000 by scheduled-commercial-bank CDR or FDR only, pledged to the Chief Executive Officer, IT&C Division, KPDCL, Bemina, Srinagar. Upload the scan with the bid; only the successful bidder supplies the original. Valid for bid validity (including extension) plus 45 days, minimum 225 days from bid opening.
Rs.1,000. J&K bidders must use e-Challan/Treasury Receipt credited to M.H-0801-Power; out-of-State bidders may alternatively use a demand draft in favour of the CEO, IT&C Division, KPDCL, payable at Srinagar.
PBG equal to 10% of accepted contract value, due within 15 calendar days of LoI; scheduled commercial bank in India; valid for the full contract plus 6 months and renewable for extension. Returned within 60 days after satisfactory completion including exit management; partial invocation is permitted.
Accepted contract value is paid in 16 equal three-monthly instalments. I-1 becomes due on KPDCL signing the Readiness Acceptance Certificate (RAC) and covers the first service period; I-2 to I-16 are in arrears. Complete undisputed invoices are processed within 30 calendar days, subject to the budget/fund-allocation clause.
Base prices are firm for 48 months; GST follows the prevailing statutory rate. Following Corrigendum 2, pricing excludes migration, any separate middleware product, and message broker; the CSP invoice is in KPDCL's name but must be settled directly by the MSP and recovered through quarterly instalments, with proof of payment attached.
Every pass/fail eligibility and qualification requirement: experience and past performance, turnover/net worth, registrations and certifications, consortium/JV rules, and debarment or blacklisting conditions.
Bidder must be an India-registered company, LLP, partnership firm or other legal entity, and must have continuously operated for the 5 years immediately preceding bid submission.
Minimum average annual turnover of Rs.1 Crore per year during FY 2023-24, FY 2024-25 and FY 2025-26, supported by audited financial statements. No minimum net-worth criterion is stated.
At least one completed or substantially completed cloud-infrastructure provisioning/managed-services project worth not less than Rs.40 Lakhs within the last 7 years, operational for at least 12 consecutive months. Consulting-only, private-cloud, on-premise and colocation projects do not qualify; subcontract experience qualifies only with an end-client reference confirming scope and value.
At bid submission, hold current partner/reseller/MSP/direct-customer or equivalent authorisation for the exact proposed cloud platform. It may be held by a disclosed named specialist sub-vendor only under Clause 4.C, with its signed availability undertaking; the prime remains solely responsible.
Proposed platform must be on the MeitY AMBUD register at bid submission, with infrastructure proposed in at least two listed cities lying in different BIS IS 1893 (Part 1): 2016 seismic zones.
Valid Indian GST registration and PAN are mandatory.
Bidder must not be currently debarred, blacklisted or suspended by any Central Government ministry/department/PSU or State Government at submission. Any past status must be supported by proof of revocation.
No conflict of interest under Clause 8.14; false/fraudulent eligibility claims may be rejected and reported. Misrepresentation, collusion, inducements, multiple identities or fronting can lead to rejection and possible debarment.
Consortiums and JVs are prohibited; the single bidder must independently meet all eligibility criteria. Credentials/financial capacity of affiliates, parents or subsidiaries cannot be relied on, and primary cloud provisioning/managed services cannot be subcontracted. Only disclosed specialist sub-vendors for limited components/platform authorisation are permitted.
Responsive bidders must score at least 70/100 technically; if none does, the threshold automatically reduces once to 60/100. Scoring is Solution Note 50, SLA certificates 20, proposed-platform experience 15 and ISO 27001 certification 15.
What is being procured: the work, supplies or services, deliverables and quantities, locations, phases, completion or delivery timelines, applicable standards, and notable exclusions.
Select an MSP to design, provision, implement and operate MeitY-empanelled cloud infrastructure and associated managed services for KPDCL's Integration Middleware Platform for 48 months from Go-Live, sized for 25-30 average requests/second with a 40-50% mid-month surge.
Production: 2 Windows application VMs in an HA pair (4 vCPU/16 GB/250 GB SSD each), 1 memory-optimised database VM (4 vCPU/32 GB/512 GB SSD), 1 hardened bastion VM, managed Layer-7 load balancer, WAF/network firewall, VPN gateway and at least 3 TB object/backup storage. UAT: 1 Windows app VM (2 vCPU/8 GB/100 GB SSD) and 1 database VM (2 vCPU/16 GB/256 GB SSD), scheduled rather than always-on.
Application tier must span at least two physically separate fault-isolated locations in one cloud region, with independent power/cooling/network. Database remains one VM with no live HA; resilience is daily automated backup and recovery. RDBMS is PostgreSQL or MySQL selected by KPDCL at HLD/implementation, not by the bidder. Production RTO is <=4 hours and RPO is <=24 hours.
24x7 monitoring/operations, incident and problem management, capacity management, patching, OS/database/runtime administration, IAM/MFA, WAF, DDoS, firewall, TLS 1.2+, KMS encryption, 12-month logging, daily backups with at least 30-day retention in a geographically separate Indian region, monthly integrity checks, and annual alternate-region IaC rebuild tests within 48 hours.
Enable CSC bill fetch/payment for all KPDCL consumer categories and provide a reusable hub for later BBPS, bank and government integrations. Cloud data/backups must stay in India; operational coordination and KPDCL-side connectivity are with IT&C Division at PDD Complex, Bemina, Srinagar.
T+0 contract/kick-off; KPDCL-owned tenancy by T+10; HLD/LLD and transition-in through T+21; build/hardening/testing T+22 to T+59; KPDCL VPN endpoints by T+35; UAT access by T+40; RAC/Go-Live by T+60. BBPS, bank and government-portal integrations are post-Go-Live and not RAC conditions.
HLD, LLD, logical/physical/security diagrams, as-built documentation, transition-in plan, project charter, runbooks/SOPs, infrastructure inventory/guide, quarterly service reports, capacity plans, hardening checklist, BOM and DR/security test reports.
KPDCL retains application development/code, business logic, functional configuration, integration/API programming, data entry/migration/conversion, KPDCL-application licences, application database objects, application middleware routes/adapters and application CI/CD. Corrigendum 2 confirms no separate middleware product or message broker is currently procured and migration is excluded.
The complete checklist of documents to submit — mandatory vs conditional, with any prescribed formats, proformas or annexures — plus how to submit: portal and mode, envelope/cover structure, digital signature requirements, signing and attestation rules, and physical originals with their deadline.
Submit only through jktenders.gov.in in two separate labelled packets/files: Techno-Commercial and Financial. No post/courier/email/in-person bid is accepted. Pricing in the technical packet causes disqualification.
Every bid document must carry a valid Class III(b) DSC in the authorised signatory's name. Upload PDFs except the prescribed portal BOQ in XLS; submit the financial-file password as the portal directs.
Authorised signatory must sign; all bid pages must be initialled. Documents must be signed/stamped, individually named by criterion, and mapped in the signed Document Index; unindexed documents are ignored. Keep certificate-type evidence to 5 pages and audited extracts to 15 pages per year.
Only the successful bidder, within 7 days of notification of award, must deliver a complete hard copy of the uploaded bid plus original CDR/FDR and original e-Challan/Treasury Receipt to the CEO, IT&C Division, KPDCL, Bemina, Srinagar. No other bidder submits hard copies.
Every corrigendum/addendum in order — what changed (original vs amended value), its impact, and the action for the bidder — ending with the values that finally apply.
Bid start moved 05-Sep-2026 04:30 PM to 09-Sep-2026 04:30 PM; submission close moved 21-Sep-2026 02:00 PM to 25-Sep-2026 03:00 PM; e-bid opening moved 24-Sep-2026 11:30 AM to 26-Sep-2026 11:30 AM. Bidder action: use only the revised dates.
All SBD references to an active-passive database HA pair are replaced: production database is one VM; resilience is backup/DR, not live failover. Bidder action: do not price or design a standby DB VM, but retain backup, patching and recovery.
Original bidder-proposed PostgreSQL/MySQL/equivalent requirement is replaced: KPDCL will specify PostgreSQL or MySQL at HLD/implementation and no RDBMS is proposed in the bid. Bidder action: accept either and exclude any proposal-dependent product selection.
Production RPO changes from <=1 hour to <=24 hours throughout; production RTO remains <=4 hours. Bidder action: align Form-4, Solution Note, DR design and SLA acceptance to backup-based RPO <=24 hours.
API gateway means secure WAF-protected exposure delivered through the existing managed Layer-7 load balancer and WAF, priced in Form-9 A.11 Networking; no separate API-management product/item. Bidder action: include function in A.11 without adding a line.
References to bidder-supplied middleware engine/product are removed. MSP only manages OS-level runtime prerequisites for KPDCL's own middleware application; application code/routes/adapters/business logic stay with KPDCL. Bidder action: do not nominate, licence or price middleware software.
'Multi-AZ' is restated as two physically separate, fault-isolated locations within the same region, each with independent power, cooling and network; rack/host-only isolation fails. Applies to application tier, not the single DB. Bidder action: evidence the physical fault isolation regardless of provider terminology.
Native-managed IAM/WAF/firewall/DDoS/monitoring/logging/KMS/load balancer are exempt from the platform-agnostic rule. Finding remediation is 72 hours generally, 15 calendar days for annual VAPT critical/high, or one month for annual cyber-audit critical/high, with the specific audit clause prevailing. Bidder action: price native controls and map remediation workflows by source.
No deduction where failure is caused by KPDCL or an external third party, but incident response/resolution clocks still apply. CSP-outage exclusion requires the CSP's published service-health incident report cross-referenced to ticket timestamps; MSP self-declaration is insufficient. Bidder action: preserve CSP and ticket evidence.
Migration, separate middleware product and message broker are excluded from current pricing. Although CSP bills KPDCL's tenancy, MSP must pay the CSP, maintain the account in good standing, and recover through quarterly instalments with payment evidence. Bidder action: remove excluded scope but fund CSP cash flow.
Final close/open: 25-Sep-2026 03:00 PM / 26-Sep-2026 11:30 AM. Final technical basis: two-fault-isolated-location application HA; single production DB VM; KPDCL-selected PostgreSQL/MySQL; production RPO <=24h and RTO <=4h; API exposure within A.11; no middleware product/message broker/migration; MSP pays CSP invoices. All other terms and dates remain unchanged.
Genuine conflicts within and across the documents (original vs corrigenda, clause vs annexure, tender document vs BOQ): both sides with citations, and which value prevails.
SBD Form-9 combines two production application VMs as A.1 (Qty 2), while BOQ_1083881.xls splits Primary and Secondary into 1.01 and 1.02, yielding 17 priced lines. The portal instruction says use the unmodified XLS, so upload and price all 17 BOQ lines; seek written confirmation because GCC 6.14 refers to Form-9 item rates for variations.
The SBD contents page describes EMD as 'DD / BG / NEFT', but the operative Clause 8.5 and NIT require CDR/FDR only. The operative clause/NIT prevail: submit scheduled-bank CDR/FDR only.
Original SBD required active-passive database HA even though its minimum table/Form-9 provided one production DB VM. Corrigendum 2 expressly resolves this to one VM with backup-based recovery; the corrigendum prevails.
Annexure B originally says RPO <=1 hour while Clause 3.5 uses daily backup and same-region RPO <=24 hours. Corrigendum 2 changes every production RPO reference to <=24 hours; that is final.
Original managed-services and inclusive-price text required middleware engine/message broker and migration costs, while other SBD text said no separate middleware tier. Corrigendum 2 excludes a separate middleware product, current message broker and migration; the corrected scope prevails.
Clause 6.6.1 defines 16 equal instalments using accepted contract value inclusive of GST @18%, but Clause 6.6.7/Form-9 says GST changes to the actual prevailing rate on each invoice. The specific tax clause should govern the GST component while the base remains fixed, but the tender does not explain how instalment equality/TCV is recalculated after a rate change; obtain clarification.
Only critical, tender-specific pre-bid queries that could materially change bid/no-bid, pricing, eligibility or contractual risk. Skip generic or obvious questions the documents already answer clearly.
Please issue a corrected harmonised schedule confirming whether the 17-line portal BOQ or 16-line SBD Form-9 controls evaluation and GCC 6.14 variations, and how A.1's two production VMs map to BOQ 1.01/1.02 unit rates.
Clause 4.6 requires hosting across two AMBUD-listed cities in different seismic zones, while Corrigendum 2 requires application HA across two fault-isolated locations within one region and the SBD separately uses another Indian region for backup/rebuild. Please define which workloads must run in each declared city and whether the second city is only backup/DR; this affects eligibility evidence and recurring cost.
Please confirm whether a statutory GST-rate change adjusts each quarterly invoice and the remaining TCV/instalment value, despite the stated 16 equal instalments based on an accepted TCV including GST @18%, and clarify its effect on PBG and 25% variation ceiling calculations.
Please state the decision date, required version/edition/extensions, sizing assumptions and any migration/compatibility dependencies for KPDCL's post-award PostgreSQL/MySQL selection, so bidders can validate operations tooling and fixed-price obligations before bidding.
Commercial, legal and execution risks a bidder should weigh: liquidated damages and penalties, unusual or one-sided clauses, tight timelines, and payment or security risks.
MSP may not suspend/degrade service for any payment or government budget delay; such delays are not KPDCL breach and bear no interest/financing charge. MSP termination is available only after 4 consecutive quarterly instalments remain unpaid plus a 60-day cure notice. Corrigendum 2 additionally makes MSP pay CSP invoices in KPDCL's name, increasing cash-flow exposure.
T+60 is hard Go-Live. MSP-attributable delay attracts 0.25% of accepted value per week/part for first 15 days, then 0.5% per week/part, capped at 10%; failure by T+150 permits default termination. KPDCL-caused approval/VPN/access delays are excluded with corresponding extension.
Availability shortfall costs 0.5% of instalment per 0.1% below 99%; incident and patch penalties also apply. The ordinary deduction cap is 15% per service period, but I-2 may absorb separate I-1 and I-2 caps up to 30%. Persistent breach can double rates, trigger step-in, PBG invocation, termination and re-procurement costs.
MSP bears infrastructure-attributable breach investigation/remediation costs and must notify KPDCL within 4 hours. It must comply with new CEA cyber-security provisions and KPDCL-specific requirements as they arise during 48 months, with price fixed except GST/approved variations.
If MeitY empanelment lapses, MSP must propose an alternative within 30 days and, if approved, migrate at no additional cost; KPDCL can require migration for sustained lapse, security concern or platform unavailability.
KPDCL can terminate for convenience on 60 days' notice, paying delivered services and reasonable documented wind-down only; MSP assignment needs KPDCL approval while KPDCL can assign to a successor/government authority without MSP consent. Pending disputes, MSP must continue performance.
Automatic scaling within the HLD ceiling receives no extra payment. If sustained beyond 7 days, KPDCL may reject the variation; MSP receives no compensation while awaiting/reaching rejection and must still preserve SLA pending decision. Retired instance series must be migrated to equal/better current generation at no added cost or SLA impact.
Corrigendum 2 deliberately removes database HA while retaining RTO <=4 hours and backup-based RPO <=24 hours. A single-VM failure must therefore be restored rapidly from daily backups; bidders should validate rebuild automation, data-loss tolerance and CSP recovery assumptions.
The inviting authority and relevant contacts: office, person, designation, address, phone and email — and which address receives physical submissions, if any.
Chief Executive Officer, Information Technology and Communication Division, Kashmir Power Distribution Corporation Limited (KPDCL). Office: PDD Complex, Bemina, Srinagar.
Email: [email protected]; telephone: 0194-2490821; fax: 0194-2490829.
The PDF digital signature records Tassaduq Nabi Chowdry; the tender body identifies the signing authority by designation as Chief Executive Officer, IT&C Division.
Successful-bidder hard copy and originals go to: Office of the Chief Executive Officer, IT&C Division (KPDCL), PDD Complex, Bemina, Srinagar. Technical and financial bid openings use the same office/venue.