In terms of Rule 65 of Public Procurement Rules, 2026, the Grievance Redressal Committee (GRC) has been notified for the subject procurement. The notification is available on the Procuring Agency's website and on PPRA's website.
Overseas Employment Corporation (OEC) (Overseas Employment Corporation (OEC))
Deputy Director
EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory
+92-300-313-3559
ddit@oec.gov.pk
The following specific data for the Framework Agreement shall complement, supplement, or amend the provisions in the Instructions to Applicants/Bidders (ITB). Whenever there is a conflict, the provisions herein shall prevail over those in ITB.
FDS Clause Number
ITB Number
Amendments of, and Supplements to, Clauses in the Instructions to Applicants/Bidders
FDS Clause Number 1
ITB Number 1.1
Identification Number of the Framework Agreement: FFW10060
The Procuring Agency is: Overseas Employment Corporation (OEC) (Overseas Employment Corporation (OEC))
Framework Agreement Title: Implementation of Cloud-Based Odoo in OEC
FDS Clause Number 2
ITB Number 2.1
The name of Procuring Agency is: Overseas Employment Corporation (OEC) (Overseas Employment Corporation (OEC))
The name of Framework Agreement is: Implementation of Cloud-Based Odoo in OEC
FDS Clause Number 3
ITB Number 2.2
Participating / Authorized Procuring Agencies under this Framework Agreement:
ITA Number 4.2
Maximum number of members in a Joint Venture (JV): Nil
FDS Clause Number 4
ITB Number 3.1
Framework Type: Open Framework Agreement
FDS Clause Number 5
ITB Number 4.1
Framework Duration: 36 Months Lot Title : ODDO Implementation Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory Address: EOBI Building House, 6th Floor, Sector G-10/4,, Islamabad Capital Territory
Commencement Date: Expired after the framework duration of 36 months from the award date.
Expiry Date:
Position
Delivery Schedule
Quantity
Odoo User Subscriptions/Licenses (Year 1)
Quantity: 05/license
Quantity: 05/license
10
Odoo.sh cloud hosting — 02 worker server, 200 GB storage, 02 staging branch (Year 1).
Quantity: 1/license
1
Odoo Implementation (Year 1)
Quantity: 1/job
1
Odoo License Renewal (Year 2)
Quantity: 10/license
10
Odoo.sh Cloud Server Renewal (Year 2)
Quantity: 1/license
1
Additional Odoo Licenses (Year 2)
Quantity: 10/license
10
Post-Implementation Support & SLA Services (Year 2)
Quantity: 1/job
1
Odoo License Renewal (Year 3)
Quantity: 20/license
20
Odoo.sh Cloud Server Renewal (Year 3)
Quantity: 1/license
1
Post-Implementation Support & SLA Services (Year 3)
Quantity: 1/job
1
FDS Clause Number 6
ITB Number 5.1
A list of debarred firms and individuals is available on PPRA website: https://ppra.gov.pk
FDS Clause Number 7
ITB Number 7.1
For clarification, the Applicant shall seek clarifications through: EPADS v2.0
FDS Clause Number 8
ITB Number 7.1 & 8.2
Information related to the Framework Agreement shall be published on: EPADS v2.0
FDS Clause Number 9
ITB Number 7.2
Pre-Bid Meeting: Clarification Date: Wednesday, September 30, 2026
Pre-Bid Meeting: Wednesday, September 30, 2026 03:00 PM
Venue: EOBI Building House, 6th Floor, Sector G-10/4,
FDS Clause Number 10
ITB Number 10.1
This Framework Agreement Document has been issued in the language: English
FDS Clause Number 11
ITB Number 11.1(d)
Additional documents to be submitted through {SYSTEMSHORTTITLE}:
No
FDS Clause Number 12
ITB Number 14.2
Source for determining exchange rates: Not Applicable
FDS Clause Number 18
ITB Number 16.1
Deadline for Bid Submission:
Day: Thursday
Date: Thursday, October 8, 2026
Time: 11:30 AM
FDS Clause Number 19
ITB Number 17.1
Opening of Bids shall be conducted through: EPADS v2.0
Day: Thursday
Date: Thursday, October 8, 2026
Time: 03:00 PM
Virtual participation link: https://vendors.epads.gov.pk/
FDS Clause Number 20
ITB Number 21.1
Margin of Domestic Preference: Not Applicable
FDS Clause Number 21
ITB Number 22.1
Framework Award Basis: Least Cost Based Selection (LCBS)
FDS Clause Number 22
ITB Number 23.1
Suppliers admitted to the Framework Agreement shall not be guaranteed any minimum quantity, value, or volume of business unless otherwise stated in the Framework Agreement.
FDS Clause Number 23
ITB Number 29.1
Framework-related complaints / grievances shall be submitted in writing through: EPADS v2.0
A complaint may challenge:
End-to-End Responsibility:Â The Implementation Partner shall provide every service, resource, subscription, environment, tool, configuration, custom component, integration, migration activity, and document necessary to place the Odoo Enterprise ERP solution into reliable production operation and support it for the full Framework Agreement term, including project mobilisation and governance; business-process discovery and fit-gap analysis; lawful Odoo Enterprise subscriptions and OEM support; solution architecture, configuration, and approved customisation; data migration and reconciliation; functional, integration, and user-acceptance testing; environment provisioning, deployment, monitoring, backup, and disaster recovery; change management, training, and documentation; and Go-Live, Hypercare, warranty, and ongoing support.
Business Process Study and Fit-Gap Analysis:Â The Implementation Partner shall conduct structured workshops with OEC's Finance, HR, Administration, Procurement, IT, and Internal Audit stakeholders to document current-state processes and controls, define approved future-state workflows and approval levels, and prepare a traceable Requirements Catalogue and Fit-Gap Register. The Business Process Analysis Report and Requirements Catalogue shall be approved by OEC in writing before detailed build begins.
Odoo Enterprise Licensing and Subscriptions:Â The Implementation Partner shall supply genuine, OEC-traceable Odoo Enterprise subscriptions based on the latest stable and officially supported release, together with Odoo.sh cloud hosting, structured as follows:
Year 1: Ten (10) Odoo user subscription licenses (five (05) activated on PO issuance, five (05) as-needed); Odoo.sh cloud hosting comprising one (01) worker server, thirty (30) GB storage, and one (01) staging branch.
Year 2: Renewal of the existing ten (10) licenses and hosting subscription upon expiry; procurement of up to ten (10) additional licenses on an as-needed basis.
Year 3: Renewal of all existing licenses (up to a maximum of twenty (20), or the actual number acquired) and hosting subscription upon expiry.
Subscriptions shall be renewable directly by OEC or through another authorised provider, and the Bidder shall provide evidence of current Odoo partnership/authorisation enabling lawful supply and support.
Solution Design:Â The Implementation Partner shall prepare a Solution Design Document (SDD) covering system architecture, module configuration, role and permission matrix, integration catalogue, data model and migration design, report/dashboard catalogue, and security architecture, and obtain OEC's written approval before production development.
Mandatory Functional Scope:Â The solution shall, at minimum, cover the following module families, configured around OEC's approved processes and controls:
Finance, Budgeting and Treasury — chart of accounts, general ledger, accounts payable/receivable, budgeting and commitment control, maker-checker approvals, bank reconciliation, and financial reporting.
Human Resources, Attendance and Payroll — employee master records, recruitment and onboarding, attendance/leave management, Pakistan payroll configuration, payslips, and payroll accounting with field-level security for sensitive data.
Procurement and Contract Management — procurement planning, vendor registration, RFQ/tender register, purchase orders, goods receipt and three-way matching, and contract repository with EPADS reference linkage.
Inventory and Stores — item master, receipts/issues/transfers, stock valuation, and physical verification.
Fixed Assets — asset registration, capitalisation, depreciation, transfers, and disposal, reconciled to the General Ledger.
Administration, Fleet, Travel and Facilities — vehicle and fuel management, travel requests and claims, and facility/service requests.
Projects, Tasks and Timesheets — project plans, milestones, budgets, and portfolio dashboards.
Documents, Workflow and Correspondence — controlled document repositories, configurable approvals, and templates.
Helpdesk and Knowledge Management — service request/incident logging with SLA tracking.
Management Information and Analytics — role-based dashboards, drill-down reporting, and scheduled statutory/management/audit reports.
Odoo Implementation (Year 1):Â Implementation shall be carried out module by module, following issuance of the Purchase Order, in accordance with the approved scope of work and Solution Design Document. The implementation cost shall be quoted as a lumpsum for Year 1 and paid as Monthly Remuneration Cost, disbursed against satisfactory completion of milestones/modules as verified by OEC.
Hosting and Technical Architecture:Â The Bidder shall propose and justify a supportable deployment model (Odoo.sh, private/on-premises cloud, or another approved platform), documenting: production topology and application/database sizing for the approved three-year user and transaction growth; separated Development, Test, UAT/Training, and Production environments, with production data masked before non-production use; approved network zones, firewall rules, and SSL/TLS termination; high-availability design with no single point of failure; data residency confined to OEC-approved locations; OEC-controlled administrative access with a named infrastructure responsibility matrix; and a tested exit-portability plan enabling OEC to export the complete database, filestore, custom modules, configuration, and logs without proprietary lock-in. All recurring hosting, storage, backup, monitoring, and support charges shall be itemised for each of the three years.
Integrations:Â All integrations shall use secure, documented, and supportable APIs, files, or approved middleware, with each interface having a defined owner, frequency, data contract, authentication method, encryption, error handling, and reconciliation control. No integration shall rely on undocumented direct database writes, and credentials shall be maintained in an OEC-approved secrets mechanism rather than embedded in source code. The confirmed integration list will be finalised during discovery but shall address, at minimum, the following expected interfaces:
OEC Online Job Portal and other operational platforms — controlled exchange of approved finance, revenue, fee, payment, cost-centre, and reference data, without direct database coupling.
Government e-Office — document/reference linkage or approved interoperability without bypassing mandatory e-Office controls.
Banking and payment channels — bank statement import, payment instructions/advice, and reconciliation through formats/APIs approved by OEC and the relevant bank.
Attendance/biometric devices — attendance events, device/user mapping, exception handling, and reconciliation.
Email and SMS gateways — system notifications, alerts, and approved transactional messages with delivery status and templates.
Identity provider/directory — single sign-on, multi-factor authentication, and user lifecycle integration using OEC-approved standards where technically available.
Tax/statutory systems — approved imports/exports or reference capture required for tax and statutory reporting.
Business Intelligence/data export — read-only, governed extracts or APIs for approved analytics without undermining ERP security or data ownership.
All APIs and interface artefacts shall be versioned and handed over with test cases and support procedures.
Data Migration:Â The Implementation Partner shall profile source datasets, define mapping and cleansing rules, execute at least two rehearsal migrations before final cut-over, reconcile record counts and balances, and obtain written sign-off from OEC data owners before go-live.
Testing, Quality Assurance and Non-Functional Requirements:Â The Implementation Partner shall execute a risk-based testing programme covering functional, integration, migration, performance, security (including independent vulnerability assessment and penetration testing before Go-Live, with zero open Critical/High findings), and user acceptance testing, maintained through a Requirements Traceability Matrix. The solution shall meet, at minimum: production availability of 99.5% monthly (excluding approved maintenance); 95% of standard transactions completing in under 3 seconds; a Recovery Point Objective of 30 minutes and Recovery Time Objective of 4 hours; 24x7 monitoring with defined incident escalation; and 100% reconciliation of financial, payroll, inventory, and fixed-asset migration data.
Implementation Methodology and Phases:Â The project shall be executed through eight (08) phases, each requiring OEC's written approval before proceeding to the next:
Phase 1 – Mobilisation and Planning: kick-off, governance, detailed plan, and stakeholder/quality/security/risk plans.
Phase 2 – Discovery and Business-Process Review: process maps, Requirements Catalogue, Fit-Gap Register, and approved Business Process Analysis Report.
Phase 3 – Solution Design: approved SDD, architecture, role/segregation-of-duties matrix, and prototype.
Phase 4 – Configuration and Build: configured and approved custom modules, reports, forms, and integrations demonstrated in Development/Test.
Phase 5 – Migration and System Testing: migration rehearsals, functional/integration/regression/performance/security tests, and reconciliation.
Phase 6 – UAT, Training and Readiness: OEC-executed UAT, role-based training, and signed Go-Live approval.
Phase 7 – Cut-over and Go-Live: final migration, production deployment, reconciliation, and smoke testing.
Phase 8 – Hypercare and Final Acceptance: 90-day stabilisation, KPI/SLA evidence, defect closure, disaster-recovery test, and Final Acceptance Certificate.
Deliverables and Acceptance:Â The Implementation Partner shall produce and obtain OEC's written acceptance of, at minimum: Inception Package; Business Process and Requirements Package; Solution Design Package; Configured Prototype; Feature-Complete UAT Release; Migration Rehearsal Package; Testing and Security Package (including VAPT results); UAT Completion Certificate; Training and Documentation Package; Go-Live Readiness Certificate; Production Go-Live Certificate; and Hypercare and Final Handover Package. Each deliverable shall be accepted only against its defined minimum content and acceptance basis, with no deemed acceptance.
Training, Change Management and Knowledge Transfer:Â The Implementation Partner shall provide role-based, hands-on training for executives/management, end users, super users/functional administrators, system administrators, technical/developer staff, and helpdesk/support personnel, using the final configured solution, together with complete training materials, administrator/developer guides, and post-training assessment.
Documentation and Handover:Â All architecture, configuration, security, data migration, testing, and training documentation shall be supplied in searchable and editable formats and formally handed over to OEC, along with source code, repositories, credentials, and an asset/licence/subscription renewal register.
Post-Implementation Support and SLA Services (Years 2 and 3):Following Go-Live and completion of Year 1, the Implementation Partner shall provide ongoing technical support and maintenance under a defined Service Level Agreement (SLA), commencing upon completion of the preceding contract year and continuing through Year 3. The scope of support shall not be limited to incident resolution and maintenance; any enhancement, modification, or additional functionality required in the Odoo system shall also be delivered through this SLA. The SLA shall define incident classification and priority levels (P1–Critical, P2–High, P3–Medium, P4–Low/Request) with corresponding response, restore, and resolution times; support channels and escalation procedures; corrective and preventive maintenance; enhancement/change request handling; and periodic SLA compliance reporting. Support costs shall be quoted as a fixed monthly cost for each contract year.
Scope Control:Â Minor configuration refinements and defect correction required to meet approved requirements are included in the Contract Price. A change is chargeable only when OEC alters an approved baseline requirement or requests a genuinely new outcome, subject to documented impact analysis and written approval.
The Overseas Employment Corporation (OEC) intends to enter into an Open Framework Agreement, for a period of 36 months, for the "Implementation of Cloud-Based Odoo in OEC," covering the procurement, implementation, configuration, customisation, integration, training, and post-implementation support of an Odoo Enterprise Resource Planning (ERP) solution.
OEC's corporate-support functions currently rely on standalone applications, spreadsheets, and manually coordinated approvals, resulting in fragmented data, delayed reconciliations, and limited visibility. This engagement will establish a unified Odoo Enterprise ERP platform integrating Finance, Human Resources and Payroll, Procurement, Inventory, Fixed Assets, Administration, Projects, Document Workflow, Helpdesk, and Management Information/Analytics on a single governed system, with approved delegation of powers, segregation of duties, and audit controls embedded throughout.
Under this Framework Agreement, the single Lot "ODDO Implementation" covers: procurement of ten (10) Odoo user subscription licenses and Odoo.sh cloud hosting in Year 1; module-by-module ERP implementation in Year 1 (business process study, solution design, configuration, data migration, integration, testing, training, and Go-Live); renewal of existing licenses and hosting, procurement of up to ten (10) additional licenses, and Post-Implementation Support & SLA Services in Year 2; and renewal of existing licenses (up to twenty (20)) and hosting, together with continued Post-Implementation Support & SLA Services, in Year 3.
Call-off Contract(s) will be issued against this Framework Agreement on a Least Cost Based Selection (LCBS) basis. The selected Implementation Partner shall deliver a secure, scalable, and upgrade-safe solution, and provide the human resource capacity, methodology, and support structure necessary for successful, sustainable operation without undue vendor dependency.
No
Lot Title : ODDO Implementation
Position: Odoo User Subscriptions/Licenses (Year 1)
Specifications / Requirements:
s
During the first year of the contract, the Procuring Agency shall procure up to ten (10) Odoo user subscription licenses for OEC staff. Of these, five (05) licenses shall be required and activated initially upon issuance of the Purchase Order (PO). The remaining five (05) licenses shall be procured on an as-needed basis during the course of the year, and the actual number required may be less than five (05), depending on operational need.
The Supplier shall quote a per-license unit rate (not a lump sum) for this item, to enable procurement of additional licenses as and when required. Rates shall be provided in the financial format.
All applicable taxes must be included in the quoted cost.
Position: Odoo.sh cloud hosting — 02 worker server, 200 GB storage, 02 staging branch (Year 1).
Specifications / Requirements:
During the first year of the contract, the Procuring Agency shall procure Odoo.sh cloud hosting, hosted on Odoo's own platform, comprising two (02) Odoo.sh worker server, two hundred (200) GB of storage, and two (02) staging branch. The hosting subscription shall be activated upon issuance of the Purchase Order (PO) and shall remain active for the duration of Year 1 of the contract.
The Supplier shall quote an annual rate for this item in the financial format enclosed with this tender.
All applicable taxes must be included in the quoted cost.
Position: Odoo Implementation (Year 1)
Specifications / Requirements:
During the first year of the contract, the Supplier shall carry out implementation of the Odoo ERP system for OEC on a module-by-module basis, in accordance with the scope of work which i mentioned with this tender document. Each module shall be configured, tested, and deployed as per the sequence and timelines defined in the implementation plan agreed with the Procuring Agency.
The total cost of implementation shall be quoted as a lumpsum for Year 1, divided into equal Monthly Remuneration Cost installments, and disbursed to the Supplier upon satisfactory completion of milestones/modules as verified by the Procuring Agency.
All applicable taxes must be included in the quoted cost.
Position: Odoo License Renewal (Year 2)
Specifications / Requirements:
During the second year of the contract, the Supplier shall renew the existing ten (10) Odoo user subscription licenses procured in Year 1, upon their expiry, as and when directed by the Procuring Agency.
The Supplier shall quote a per-license annual renewal rate here and in the financial format enclosed with this tender. All applicable taxes must be included in the quoted cost.
Position: Odoo.sh Cloud Server Renewal (Year 2)
Specifications / Requirements:
During the second year of the contract, the Supplier shall renew the Odoo.sh cloud hosting subscription procured in Year 1, comprising two (02) Odoo.sh worker server, two hundred (200) GB of storage, and two (02) staging branch, upon expiry of the Year 1 subscription, so as to ensure uninterrupted hosting services.
The Supplier shall quote an annual renewal rate for this item in the financial format enclosed with this tender.
All applicable taxes must be included in the quoted cost.
Position: Additional Odoo Licenses (Year 2)
Specifications / Requirements:
During the second year of the contract, the Procuring Agency may procure up to ten (10) additional Odoo user subscription licenses for OEC staff, over and above the existing ten (10) licenses, as and when required. The actual number of additional licenses procured may increase or decrease based on operational need, and the Procuring Agency reserves the right not to procure any additional licenses if not required.
The Supplier shall quote a per-license unit rate (not a lump sum) for this item, in the financial format enclosed with this tender, to remain available as a provision for the duration of 2nd Year Contract.
All applicable taxes must be included in the quoted cost.
Position: Post-Implementation Support & SLA Services (Year 2)
Specifications / Requirements:
Following successful Go-Live and completion of Year 1 implementation, the Supplier shall provide ongoing technical support and maintenance services for the Odoo ERP system during Year 2, in accordance with a defined Service Level Agreement (SLA).
The scope of support under this SLA shall not be limited to incident resolution and maintenance; any enhancement, modification, or additional functionality required in the Odoo system during Year 2 shall also be handled and delivered through this SLA.
The SLA shall define, at a minimum:
Incident classification and priority levels (P1–Critical, P2–High, P3–Medium, P4–Low/Request), with corresponding Response Time, Restore/Workaround Time, Target Resolution Time, and Support Coverage for each priority tier.
Support channels, help desk mechanism, and escalation procedures.
Corrective maintenance (defect resolution, root cause analysis) and preventive maintenance (system health checks, performance and security reviews).
Enhancement/change request handling, including request logging, impact assessment, effort estimation, approval, development, testing, and deployment.
Support for Odoo Enterprise updates, bug fixes, and security patches.
Periodic SLA compliance reporting, including incidents logged, resolution status, enhancements delivered, and performance observations.
The Supplier shall maintain a qualified support team, including functional consultants, technical support personnel, and developers, to ensure continuity of support and enhancement delivery throughout Year 2.
The Supplier shall quote a fixed monthly support cost for this item, in the financial format enclosed with this tender. All applicable taxes must be included in the quoted cost.
Position: Odoo License Renewal (Year 3)
Specifications / Requirements:
During the third year of the contract, the Supplier shall renew all existing Odoo user subscription licenses procured in Years 1 and 2 (up to a maximum of twenty (20) licenses, or the actual number of licenses acquired across both years, whichever applies), upon their expiry, as and when directed by the Procuring Agency.
The Supplier shall quote a per-license annual renewal rate in the financial format enclosed with this tender.
All applicable taxes must be included in the quoted cost.
Position: Odoo.sh Cloud Server Renewal (Year 3)
Specifications / Requirements:
During the third year of the contract, the Supplier shall renew the Odoo.sh cloud hosting subscription (comprising two (02) Odoo.sh worker server, two hundred (200) GB of storage, and two (02) staging branch), previously renewed in Year 2, upon expiry of the Year 2 subscription, so as to ensure uninterrupted hosting services.
The Supplier shall quote an annual renewal rate for this item in the financial format enclosed with this tender.
All applicable taxes must be included in the quoted cost.
Position: Post-Implementation Support & SLA Services (Year 3)
Specifications / Requirements:
Continuing from Year 2 support services, the Supplier shall provide ongoing technical support and maintenance services for the Odoo ERP system during Year 3, in accordance with the defined Service Level Agreement (SLA).
The scope of support under this SLA shall not be limited to incident resolution and maintenance; any enhancement, modification, or additional functionality required in the Odoo system during Year 3 shall also be handled and delivered through this SLA.
The SLA shall define, at a minimum:
Incident classification and priority levels (P1–Critical, P2–High, P3–Medium, P4–Low/Request), with corresponding Response Time, Restore/Workaround Time, Target Resolution Time, and Support Coverage for each priority tier.
Support channels, help desk mechanism, and escalation procedures.
Corrective maintenance (defect resolution, root cause analysis) and preventive maintenance (system health checks, performance and security reviews).
Enhancement/change request handling, including request logging, impact assessment, effort estimation, approval, development, testing, and deployment.
Support for Odoo Enterprise updates, bug fixes, and security patches.
Periodic SLA compliance reporting, including incidents logged, resolution status, enhancements delivered, and performance observations.
The Supplier shall maintain a qualified support team, including functional consultants, technical support personnel, and developers, to ensure continuity of support and enhancement delivery throughout Year 3.
The Supplier shall quote a fixed monthly support cost for this item, in the financial format enclosed with this tender. All applicable taxes must be included in the quoted cost.
All Active Taxpayers shall be eligible to participate in the procurement process, unless expressly excluded or otherwise restricted under the Eligibility Criteria specified by the Procuring Agency.
| Bidder's Type | Required Registration |
|---|---|
|
Sole Proprietorship Partnership Firm Company (Private Limited) |
FBR (NTN) FBR (GSTN) SECP |
| Eligibility Criteria | Document |
|---|---|
| Tax Registrations: The bidder must be registered with Federal Board of Revenue (FBR) for Income Tax (NTN) and Sales Tax (GST). Copies of NTN and GST registration certificates are required. The bidder should appear on the Active Taxpayer List (ATL) for Income Tax and have a compliant status in Sales Tax (Attach evidence of NTN, GST and ATL status printout) | Yes |
| Local Presence: The bidder should have an operational office or development center in Pakistan. Presence in Islamabad/Rawalpindi, or the ability to deploy project staff there when required, is preferred for coordination. Firms from other regions are not disqualified, provided on-site presence for meetings/deployment can be assured when needed. Evidence: office address with proof (rent/ownership documents). | Yes |
| Bidder is not blacklisted: An Affidavit on stamp paper (Annex-II) must be provided, stating that “the bidder/firm is not blacklisted or debarred by any Federal/Provincial Government, Department, or Agency in Pakistan, and is not involved in any corrupt or fraudulent practices. | Yes |
| Bid Security: Bidder has furnished the required Bid Security (as mentioned in the tender document (Attach Pay Order/Draft or receipt)) | Yes |
| Interested bidders shall deposit a non-refundable Tender Fee of Rs. 3,000/- into the Corporation’s account No. PK26 HABB 0001127927495901 (Account Title: O.E.C Corp. Pvt) maintained at HBL, Aabpara Branch, Islamabad. (A copy of the paid deposit slip must be attached with the bid document (as proof of payment.) | Yes |
| Pre-Bid Meeting: Attendance at the mandatory pre-bid meeting is a prerequisite for eligibility. The bidder or an authorized representative must attend the session to gain a clear understanding of the existing system architecture, planned enhancements, development requirements, and underlying technologies. OEC's official attendance record shall serve as the basis for verification. Non-compliance shall result in rejection of the bid. | No |
Least Cost Based Selection (LCBS)
Bidders shall submit their financial proposal strictly as per the enclosed specimen (Mandatory).
Bidders shall submit the Black List Declaration form strictly as per the enclosed specimen (Mandatory).
Mandatory to read and ubmit the proposal accordingly
Bidders shall have a minimum of seven (07) years of experience in Odoo ERP implementation, and shall furnish details of all relevant contracts undertaken during the last three (03) years in the format prescribed in the attached proforma, stating the Procuring Agency/Client, Contract Value, Year of Execution, Goods/Services Supplied, and Country of Destination. Of these, the bidder shall demonstrate at least three (03) successfully completed Odoo ERP implementations within the last five (05) years, covering material configuration and customisation across a minimum of three (03) core Odoo module families, supported by signed contracts/work orders, completion or client acceptance certificates. Contracts or projects not substantiated with the required documentary evidence shall not be considered towards meeting this eligibility requirement.
Bidders shall demonstrate a minimum annual turnover of PKR 150 million in the most recent completed financial year, and an aggregate turnover of PKR 300 million over the last three (03) completed financial years. Bidders shall complete the attached Financial Situation and Performance proforma in full, providing Total Assets, Total Liabilities, Total Equity/Net Worth, Current Assets, Current Liabilities, Working Capital, Total Revenue, Profits Before Taxes, and Cash Flow from Operating Activities for each of the last three (03) completed financial years, along with copies of independently audited financial statements (and tax returns, where required) corresponding to the years declared. Figures in foreign currency shall be converted to PKR using the applicable exchange rate as specified in the tender.
For last three years