Hindustan Aeronautics Limited Veeam Data Platform Foundation Software License Tender India 2026

Bidders must be OEM or authorised distributors of Veeam Enterprise. Prepare data sheet aligned with offered licenses, provide OEM authorization, submit PAN, GSTIN, cancelled cheque, and EFT mandate. Ensure compliance with PAC for Schedule No. 1 and provide dedicated support contacts. Delivery terms may adjust with the 50% quantity option.

Required documents include PAN Card, GSTIN, Cancelled Cheque, EFT Mandate certified by bank, Data Sheet for the product, OEM authorization form with reseller details, and evidence of OEM eligibility for Schedule No. 1. Data sheet must mirror the offered software specifications to avoid rejection.

The tender specifies Schedule No. 1 for Veeam Data Platform Foundation software license available only to OEMs/distributors, and Schedule No. 2 for the Backup Server. Data Sheet alignment with product specifications is mandatory; mismatches may lead to rejection.

Delivery periods are governed by the option clause allowing up to 50% quantity variation; the added time is calculated as (Increased quantity ÷ Original quantity) × Original delivery period, with a minimum of 30 days, and may extend to the original delivery period as needed.

Bidders must declare GST as applicable; HAL reimburses GST as actual or at the lower applicable rate, limited to the quoted GST percentage. This is not HAL liability and must be managed by the bidder per GST regulations.

Submit an OEM Authorization Form with OEM details: name, designation, address, email, and phone. This applies to authorised distributors for Schedule No. 1, ensuring compliance with Veeam Enterprise licensing requirements.

Bidders must upload a Data Sheet that precisely matches the offered product specifications. Any unexplained mismatch can lead to bid rejection, so ensure feature-by-feature alignment before submission.

Schedule No. 2 is open to all bidders meeting the technical requirements for the Backup Server, separate from the PAC constraints of Schedule No. 1, enabling broader participation for the backup infrastructure component.