Two central portals, one workspace
Both portals run on the same NIC e-procurement software, so a tender looks alike on either: a Tender ID, an organisation chain naming the department, a set of key dates and a document bundle. Operavity crawls the latest active tenders on each and keeps the source portal on every tender, so you always know where to submit.
| Portal | Address |
|---|---|
| Central Government eProcure | eprocure.gov.in/eprocure/app |
| Central Government eTenders | etenders.gov.in/eprocure/app |
The same NIC format is used by the Jammu & Kashmir and Himachal Pradesh state portals and by DefProc, so central and state tenders sit side by side in one consistent layout.
What is captured from each CPPP tender
From the tender details page and the document bundle, the crawler is built to capture the following. Each value in the summary links back to where it was read.
- Organisation chain, Tender ID, title and work description.
- Tender value, tender category, product category and form of contract, where published.
- EMD amount, who it is payable to and where, and whether an exemption is allowed.
- Tender fee details, bid validity and work period.
- Location and pincode of the work.
- Published, document sale, clarification, submission end and bid opening dates.
- Pre-bid meeting details.
- Covers information, which tells you how the bid is split into envelopes.
- The tender documents, downloaded as the portal bundles them.
- Corrigendum links, attached to the tender they change.
Corrigenda stay with the tender they change
When a tender is amended, the NIC tender page carries a corrigendum link, which the crawler collects. On the portal that link is easy to miss. In Operavity it shows on the tender itself, so whoever owns the bid sees the change in the place they are already working.
Always read the latest corrigendum on the portal before you submit, and check the tender document for what it changes.
How a bid team uses it day to day
Morning: one list instead of two portal searches
Keywords for your trades match new tenders from both portals. The team opens one list, sorted by closing date, and stars the ones worth a closer look.
Assessment: the summary first, the PDF second
The summary shows value, EMD, dates and the eligibility clauses with page references. Turnover and experience are compared with your company profile as Pass, Fail or Unknown.
Preparation: shared, not scattered
Assign reviewers from estimation, technical or finance. Work the BOQ, send vendor quote requests from it, and tick off required documents. Submission dates and pre-bid meetings appear on the shared calendar.
Submission: on the portal
Operavity does not submit bids. Your team signs and submits on the portal itself, as it does today. Afterwards, record the submission in Operavity and follow the tender's status where the portal publishes it.
If you win
A won tender becomes a project in the same workspace. The BOQ carries over, with tasks, a Gantt view, expenses, vendors and documents, so the estimate you bid on is the plan you deliver against. For GeM work, see GeM tender management.
Questions
What is the difference between eProcure and eTenders?
Both are central government NIC e-procurement portals that Operavity groups under CPPP. Each has its own list of active tenders. Operavity integrates both and keeps the source portal on every tender.
Does Operavity show corrigenda for CPPP tenders?
Yes. Corrigendum links found on the tender page are attached to the tender they change, so the bid owner sees them on the same record.
Can I submit my CPPP bid through Operavity?
No. You submit on eprocure.gov.in or etenders.gov.in as usual. Operavity keeps the deadline, EMD and documents in view and records that the bid went in.
Do CPPP and state portal tenders appear together?
Yes. Tenders from both CPPP portals, GeM, DefProc and the integrated state portals share one list and one calendar, filterable by portal.