University Website Development and Maintenance

Tender release / publication

Tender document released / issued on 14/07/2026.

• Tender No. क्रमांक/भण्डार/2032/2026.
• No corrigendum changes this date.

Bid submission deadline

Last date for submission of bids is 06/08/2026.

• No clock time is printed in the tender PDF for submission.
• No pre-bid meeting or clarification deadline is stated in the documents.

Technical bid opening

Technical bid opens on 10/08/2026.

• Financial bid opening date is left blank (---) in the tender details and important-dates table.

Contract duration and deployment timeline

Documents conflict on contract length; initial deployment/upgrades required within 90 days of Work Order.

• Clause 5 states initial contract period of three (3) years, extendable on satisfactory performance and mutual consent.
• Clause 6.1 states initial contract of two (2) years from Agreement execution, extendable by one (1) further year on satisfactory review, with any further extension needing written approval.
• Bid validity period is not stated in the tender documents.

Estimated / tender value

No estimated tender value or project cost is stated; BOQ estimated rates are zero.

• BOQ is an item-rate schedule with three priced lines and Estimated Rate shown as 0 for each item.
• Because tender value is not fixed, EMD stated as 3% of total tender value cannot be computed from the documents alone.

Tender fee

Tender fee is ₹2000/-.

• Tender Fee and EMD details are to be included in the Technical Bid.
• Acceptable instrument/mode for paying the tender fee is not specified in the documents.

EMD / bid security

EMD is 3% of total tender value; MP MSEs and MP-recognized Startups are exempt with prescribed proof.

• No fixed rupee EMD amount, bank account, DD/BG format, or EMD validity/claim period is printed in the tender PDF.
• Exemption under Madhya Pradesh Store Purchase & Service Procurement Rules, 2015 (as amended) for Micro & Small Enterprises of Madhya Pradesh and Startups recognized by the Government of Madhya Pradesh, on submission of valid Udyam Registration Certificate, Startup Recognition Certificate, or other prescribed evidence.

Performance security and security deposit

E-PBG of 3% of tender value (valid 60 days beyond contract completion) and Security Deposit of 10% of total tender value are both stated.

• PBG may be invoked fully or partly for SLA failure, repeated security breaches, data loss/breach from negligence, exit/handover failure, or material breach; University decision is final.
• Documents do not clarify whether the 10% Security Deposit is in addition to, or in lieu of, the 3% E-PBG.

Payment terms

Maintenance payment is proposed via a nominal charge on student fee collection pages; additional development is paid separately after approval and acceptance; quarterly payment release is also stated for additional work.

• Bidder must state in the Financial Bid the proposed percentage or amount of the student-fee maintenance charge sufficient to cover entire maintenance cost; University decides final approval, collection and disbursement.
• Additional development (new apps/modules/APIs etc. outside routine maintenance) needs prior written estimate approval; payment only after completion, UAT/acceptance, and handover of source code/docs/credentials.
• Clause 8 also states quarterly payments shall be released only after satisfactory completion and ICT Cell certification.
• Structure modifications within existing website attract no extra payment unless classified by University as additional development.

BOQ / financial bid price items

Financial bid/BOQ has three lines: Annual Website Maintenance (per year), Cloud Hosting optimized configuration, and Any Other Charges (Domain and Cloud Hosting Charges), grand total inclusive of taxes.

• Annexure II financial format matches the BOQ line items.
• Bidder must also detail proposed cloud hosting environment (architecture, CPU/RAM/storage/OS/bandwidth, uptime, SSL/WAF/IDS/IPS, backup/DR, GoI cloud compliance).

Legal registration and experience

Registered Indian company/firm with ≥3 years' experience in website design, development, hosting & maintenance.

• Supporting document: Certificate of Incorporation/Registration.

Past performance / similar projects

At least three (3) similar projects for Government / Universities / PSU.

• Supporting documents: Work Orders / Completion Certificates.

Financial capacity / turnover

Average annual turnover of ₹25 Lakh in the last three financial years.

• Supporting documents: Audited Financial Statements / CA Certificate.
• Same ₹25.00 lakh three-year average turnover is restated in the MSME note.

MSME registration requirement

Note under eligibility states the bidder shall be a registered MSME eligible under Digital MSME / MSME Innovative Scheme.

• Note also says bidder shall possess adequate technical capability for secure, scalable, cloud-based, accessible website solutions and shall be eligible for Government support, including reimbursement of up to 75% of project cost subject to MoMSME guidelines.
• This MSME mandate is not listed as a row in the main eligibility table and may conflict with open participation language elsewhere.

Registrations and certifications

Valid PAN, GST and ISO certifications required; ISO 9001/27001 preferred.

• Supporting documents: copies of certificates.
• Qualified technical manpower on payroll required, supported by Employee List / Organisational Chart.

Blacklisting / debarment status

Bidder must not be blacklisted by any Government or PSU; self-declaration on letterhead required.

• Annexure IV also requires confirmation that no legal or financial case is pending against the firm.
• University may debar/blacklist the developer for serious breach, repeated non-performance, security violations, false information, or contractual non-compliance for a period decided by competent authority.

Consortium / JV

No consortium or joint-venture rules are stated in the documents.

• Sub-contracting is restricted: no sub-contracting without written approval; vendor remains fully responsible for subcontractor actions.

Technical verification gate

Bidder must present a website demo at technical verification when called; qualification follows a satisfied technical committee report.

What is being procured

Comprehensive website maintenance, future development, hosting and security audit for the official University website www.mcbu.ac.in.

• Work covers takeover of existing system/source code/database/structure after agreement, with continuity and no downtime.
• Location/context: Maharaja Chhatrasal Bundelkhand University (MCBU), Near Panna Naka, Chhatarpur (M.P.) – 471001.
• BOQ title: University Website Development and maintenance.

Core technical deliverables and standards

Modern open-source stack, bilingual Hindi/English site, GIGW & WCAG 2.1 AA compliance, MeitY-empanelled cloud hosting, annual CERT-IN audit/VAPT, SSL/WAF, CDN, 24×7 monitoring, SEO benchmarks.

• Tech stack examples: ReactJS, Next.js, Node.js, Laravel or equivalent.
• Responsive cross-browser design; integrate with university systems such as Samarth/ERP/MIS if required.
• Secure admin dashboard with RBAC; automatic backups, content versioning and rollback.
• Student application for information, attendance and other facilities is listed under technical requirements.
• Google Lighthouse score ≥ 80; Core Web Vitals compliance; SEO-friendly URLs & schema.
• No GPL-restricted components without approval; license list mandatory.
• Mobile app integration clause notes web-based app / PWA / Android app and API-ready architecture.
• Optional/future-ready AI chatbot for university information and admission/exam FAQs in Hindi & English.

Maintenance, structure changes, email and user management

Routine content/bug/performance maintenance; structural changes at no extra cost; official @mcbu.ac.in webmail support; comprehensive RBAC user management.

• Maintenance includes updates of content/news/notifications/tenders, bug/broken-link fixes, performance/DB tuning, quarterly reports to ICT Cell.
• Structural modifications need prior written ICT Cell approval; University decides whether a change is routine or additional development.
• Email scope: provisioning IDs, IMAP/POP/SMTP, spam/AV, mailbox storage/backup, device support; ownership of domain/email stays with MCBU.
• User management: Super Admin/Admin/Editor/Department User roles, audit logs, password policies; all credentials remain MCBU-owned.

Hosting, security, DR and compliance targets

MeitY CSP hosting only; DC & DR in separate seismic zones ≥200 km; 99.9% uptime; RTO ≤4 hours; RPO ≤24 hours; India data localization; IT Act / CERT-IN / DPDP compliance.

• Daily backups and periodic restoration tests; quarterly backup verification & restoration drills.
• Firewall, IDS/IPS, WAF; log retention 180 days; analytics and monthly usage reports.
• In addition to annual CERT-IN audit, facilitate at least one independent third-party or internal security assessment every six months; remediate at no extra cost.
• Source-code escrow updated every quarter or on major releases.

Future development, content ownership and training

Future modules/UI redesign/MIS-API integration; University owns content and all IP/source code; vendor provides CMS, training and manuals.

• Content changes need written approval; vendor supports formatting, publishing and archival.
• Minimum training sessions, user manuals, admin manuals and video tutorials required.
• All source code, designs, databases, APIs, documentation and IP under the contract are sole perpetual property of MCBU; no reuse/resell/license to third parties.

Timelines and contract term for delivery

Initial deployment/configuration/upgrades within 90 days of Work Order; contract term stated as either 3 years or 2+1 years (see contradictions).

• Exit management: minimum 30-60 days transition support, zero-downtime migration, knowledge transfer, no additional cost.

Submission mode and cover structure

Two-bid system: Technical Bid and Financial Bid in two separate clearly labelled sealed envelopes, submitted by the deadline.

• NIT language invites sealed tenders; General Terms require two sealed envelopes.
• BOQ is an e-procurement Item Rate template that must be uploaded after filling relevant columns without modification, indicating an online financial-upload component as well.
• Incomplete or conditional bids are summarily rejected.
• Digital signature class is not specified in the tender PDF.
• No separate physical-originals deadline or receiving desk beyond the University address is stated.

Signing / attestation rules

Bidder authorized signatory must sign with seal; non-blacklisting and undertaking annexures are on company letterhead.

• Section 11 provides bidder signature block with seal, name, designation, firm, date and place.
• Issuing authority block shows Registrar, MCBU.

Financial bid content rules

Financial bid must show item-wise costs, taxes/charges and grand total in words and figures; only technically qualified bidders' financial bids are opened.

• Also disclose student-fee maintenance charge percentage/amount under payment clause 7.

No corrigenda issued in the workspace documents

No corrigendum/addendum files are present; original tender values in websitepdf.pdf, Tendernotice_1.pdf and BOQ_627680.xls apply as printed.

• Final dates from tender PDF: issue/release 14/07/2026; bid submission last date 06/08/2026; technical opening 10/08/2026; financial opening not fixed in document.
• Final fee/security text: tender fee 2000/-; EMD 3% of total tender value (MP MSE/Startup exemption available); E-PBG 3% valid 60 days beyond completion; Security Deposit 10%.
• Tendernotice_1.pdf contains only a digital signature block and no substantive corrigendum content.

Contract duration: 3 years vs 2+1 years

General Terms clause 5 sets initial contract at three years; clause 6.1 sets two years plus one-year extension.

• Original/general clause: 'The initial contract period shall be three (3) years, extendable further based on satisfactory performance and mutual consent.' (p.7).
• Later specific clause 6.1: initial two (2) years from Agreement, extendable one (1) year on performance review; further extension needs written approval (p.10).
• Documents do not state which clause prevails; bidders should seek written clarification before pricing multi-year commitment.

Evaluation method: L1 vs highest combined score

Clause 8.1 simultaneously says financial evaluation is L1 among technically qualified bidders and that the highest combined Technical+Financial score wins.

• These are mutually inconsistent award methods; no QCBS weightages are provided.
• Bidders cannot know whether pure lowest price or scored combination will decide the award.

EMD amount undefined while stated as 3% of tender value

EMD is 3% of total tender value, but no tender/estimated value is given and BOQ estimated rates are 0.

• Cannot compute a rupee EMD from the documents.
• No instrument instructions are provided either.

Performance security stacking: 3% E-PBG and 10% Security Deposit

Both E-PBG 3% and Security Deposit 10% are listed under the same EMD/PBG heading without clarifying if cumulative.

• If cumulative, post-award security burden is 13% of tender value plus any retention/payment risks from the student-fee model.

Sealed physical envelopes vs e-procurement BOQ upload

Tender text requires two sealed envelopes, while BOQ instructs online upload of an unmodified template.

• Mode of submission (pure offline, pure online, or hybrid) is not reconciled in the documents.

Open tender vs mandatory MSME bidder note

Eligibility table admits registered companies/firms generally, but the following Note says the bidder shall be a registered MSME.

• Unclear whether non-MSME firms are ineligible or whether the Note only describes preferred/scheme-linked bidders.

Which contract term applies: 3 years or 2+1?

Ask ICT Cell/Registrar to confirm binding contract duration and extension rights before pricing.

• Material to multi-year staffing, hosting commitments and security deposit tenure.

Confirm award method and any technical score weightage

Seek written clarification whether selection is pure L1 after technical qualification or QCBS/combined scoring, and request score matrix if any.

• Current clause 8.1 states both methods.

How is EMD rupee amount to be calculated and paid?

Request declared tender value or fixed EMD amount, acceptable instruments, beneficiary details, and validity.

• Also confirm whether non-MSME bidders are eligible despite the MSME Note, and exact exemption proofs for MP MSE/Startups.

Is Security Deposit 10% in addition to E-PBG 3%?

Clarify post-award security quantum, form, timing of deposit/return, and whether EMD is adjusted into PBG/SD.

Student-fee maintenance charge payment model mechanics

Ask how percentage/amount is approved, when developer is paid, who bears payment-gateway risk/shortfall if collections are low, and whether BOQ annual maintenance price replaces or coexists with this model.

• This revenue model can make recovery contingent on student fee traffic and University disbursement norms.

Submission mode: sealed envelopes, portal upload, or both?

Confirm exact offline address/deadline for sealed envelopes and any mandatory mptenders.gov.in online packet/DSC requirements.

• Also ask whether physical originals of fee/EMD must accompany the sealed bid.

Scope boundary for no-cost structural changes vs paid additional development

Request objective criteria/examples distinguishing routine structure modification from chargeable new modules, and whether student app / chatbot / mobile app are in base scope or optional/paid.

• University's decision is final and binding under clause 5.2, creating pricing risk.

SLA uptime penalties and incident response clocks

99.9% uptime is mandatory; uptime below 99.5% attracts 5% of monthly invoice; critical issues ≤4 hours and high-severity bugs ≤24 hours.

• PBG can also be invoked for SLA failure and security non-compliance.

One-sided termination and no-compensation rights

University may terminate wholly/partially at any time without assigning reason; no claim for compensation, loss of profit or damages is entertained.

• Developer early exit requires 6 months' written notice plus full handover of source code, backups, credentials and documentation.
• Force majeure beyond 60 days also lets University terminate without financial liability.

Broad indemnity and cyber liability

Developer must indemnify MCBU for data breaches, cyber-attacks, IT/CERT-IN/data-protection violations, IP infringement and negligence; fully liable for all direct damages; indemnity survives termination.

• Combined with mandatory MeitY hosting, CERT-IN/VAPT, six-monthly extra audits and escrow, residual security liability remains high.

Payment recovery risk from student-fee add-on model

Maintenance recovery depends on a University-controlled nominal charge on student fee pages and University disbursement norms, not a simple fixed monthly invoice commitment.

• Bidder must propose percentage/amount sufficient to cover entire maintenance cost, but final mechanism is University-determined.
• Additional development unpaid if done without prior written approval.

Tight go-live and high compliance scope

Full initial deployment/configuration/upgrades within 90 days, plus GIGW/WCAG, bilingual content, MeitY DC-DR, student app, email services and integrations.

• No-cost structural change clause and University's final classification of change orders can expand unpaid work.
• IP and source code become sole perpetual property of MCBU; escrow must be updated quarterly.

High security-deposit burden and PBG invocation breadth

Documents state E-PBG 3% (60 days beyond completion) and Security Deposit 10%, with wide PBG invocation triggers including exit-support failure.

• Ambiguity on whether both run together increases cash-lock risk.

Domain/email control and post-exit residual duties

MCBU retains exclusive domain/DNS/webmail ownership; developer gets only limited revocable access and must not host/route/store official mail on third-party systems without approval.

• On termination/expiry, immediate access revocation and full handover are mandatory; retention/use/disclosure of MCBU data attracts legal action.

Inviting / issuing authority

Registrar, Maharaja Chhatrasal Bundelkhand University (MCBU), Chhatarpur (M.P.).

• BOQ Tender Inviting Authority: Registrar , M.C.B.U. Chhatarpur.
• Document issuing signature block: Registrar, Maharaja Chhatrasal Bundelkhand University (MCBU), Chhatarpur (M.P.).
• Tender managed with MCBU ICT Cell references throughout scope/approvals.

Office address for the University

Near Panna Naka, Chhatarpur, Madhya Pradesh – 471001.

• Same address is repeated in the NIT body.
• Documents do not expressly designate a separate physical bid-receiving room/counter beyond this University address and the sealed-envelope submission instruction.

Phone and email

Phone and email fields in the tender document are left blank; no contact numbers or email IDs are printed.

• Website referenced: www.mcbu.ac.in.