In terms of Rules 65 of Public Procurement Rules, 2026 Grievance Redressal Committee (GRC) is notified for the subject procurement and notification copy is available on the procuring agency’s website and also available on EPADS v2.0 as well as Authority’s website at (www.ppra.gov.pk).
Pharmacy Council of Pakistan (Admin & Technical), Secretary PCP
304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad.
+92-519-218-995
secretary@pcpisb.gov.pk
The following specific data for the procurement of Goods to be procured shall complement, supplement, or amend the provisions in the Instructions to Bidders (ITB). Whenever there is a conflict, the provisions herein shall prevail over those in ITB.
BDS Clause Number
ITB Number
Amendments of, and Supplements to, Clauses in the Instruction to Bidders
BDS Clause Number 1
ITB Number 1.1
Name of Procuring Agency: Pharmacy Council of Pakistan (Admin & Technical)
The subject of procurement is: DESIGN, DEVELOPMENT, TESTING AND SOURCE CODE DELIVERY OF COMPREHENSIVE WEB-BASED PORTAL OF PHARMACY COUNCIL OF PAKISTAN
Expected commencement date: Sunday, December 6, 2026
BDS Clause Number 2
ITB Number 2.1
Financial year for the operations of the Procuring Agency: 2026-27
Name and identification number of the Contract: P190197
BDS Clause Number 3
ITB Number 4.6
JV/Consortium or Association Allowed: No
Number of JV/Consortium Members: Nil
BDS Clause Number 4
ITB Number 7.1
The Bidders may seek clarifications through EPADS v2.0: Clarification Date: Sunday, November 8, 2026
BDS Clause Number 5
ITB Number 8.1
Any addendum, in case issued, shall be published on Pharmacy Council of Pakistan (Admin & Technical) website and on EPADS v2.0.
BDS Clause Number 6
ITB Number9.1
List of documents required along with the bid:
BDS Clause Number 7
ITB Number 11.1
The qualification criteria to establish the supply / production capability of the bidder.
see Eligibility Criteria
BDS Clause Number 8
ITB Number 7.6
Services and Their related documents:
See section Required Services and Scope of Work
BDS Clause Number 9
ITB Number 13.1 & 13.2
Price schedule will be provided according to the format defined and acquired.
see section price schedule.
BDS Clause Number 10
ITB Number 7.6.2
Specifications:
see section of specifications.
BDS Clause Number 11
ITB Number 13.5
The price shall be Fixed.
BDS Clause Number 12
ITB Number 15.1
Currency of the Bids shall be : PKR
BDS Clause Number 13
ITB Number 16.1
The Bids/Bid Validity period shall be: 90 Days
BDS Clause Number 14
ITB Number 17.1
The amount of Bid Security shall be as defined in Bid Security Section for items and lots given in BDS 6
Instrument of Bid Security Shall be in the Name of :
The Bid Security shall be in the form of:
BDS Clause Number 15
ITB Number 17.3
The Bids security shall be valid for twenty-eight (28) days beyond the expiry of the Bids validity period specified in the bidding documents, for example the bid validity is 180 days so the bid security shall be valid for 180+28 = 208 days.
BDS Clause Number 16
ITB Number 18.1
Alternative Bids to the requirements of the bidding documents will not be permitted.
BDS Clause Number 17
ITB Number 21.1
Bid shall be submitted online on EPADS v2.0 whereas hard copy of the bid security should be submitted to the following;
304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad.
Bids that are not submitted on EPADS v2.0 shall be disqualified.
The deadline for Bids submission is: Wednesday, November 11, 2026 01:00 PM
BDS Clause Number 18
ITB Number 26.1
The Bids opening shall take place on EPADS v2.0.
Day : Wednesday
Date: Wednesday, November 11, 2026
Time : 02:00 PM
BDS Clause Number 19
ITB Number 32.1
Selection technique adopted will be: Quality and Cost Based Selection (QCBS)
see Evaluation Criteria
BDS Clause Number 20
ITB Number 49.1
The Performance guarantee shall: 0%.
The Performance Guarantee shall be acceptable in the form of: Nil
BDS Clause Number 21
ITB Number 51.1
Arbitrator shall be appointed by mutual consent of the both parties.
BDS Clause Number 22
ITB Number 53.1
Grievence against this procurement shall be submitted online on EPADS v2.0.
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.
| Required Registration |
|---|
|
FBR (NTN) FBR (GSTN) SECP |
Quality and Cost Based Selection (QCBS)
Weightage
| Technical Evaluation % | Financial Evaluation % |
|---|---|
| 60 | 40 |
| Technical Marks | 100 | |
|---|---|---|
| Passing Marks | 60 | |
| Technical Evaluation Criteria | ||
| Profile of the Firm (Years in business, software establishment setup, etc.) (Qualitative)(Doc Required) | 5 | |
| Strength of Permanent Technical and Managerial Staff
(Based on certified HR payroll and EOBI registration lists). (Quantitative)(Doc Required) • 5 or more permanent engineering staff = 5 marks • 3 to 4 permanent engineering staff = 3 marks • Less than 3 permanent engineering staff = 1 mark (5) | 5 | |
| ISO Certified Software Engineering Firm
(Active status for current financial year) (Qualitative)(Doc Required) • Valid ISO 9001 and/or ISO 27001 Software Engineering Quality Certification = 10 Marks • No valid ISO IT certification = 0 Marks. (10) | 10 | |
| Experience in Portal Architectures & Systems
(Similar automation contracts executed previously) (Qualitative)(Doc Required) • 05 or more core software portal contracts = 20 Marks • 03 to 04 core software portal contracts = 15 Marks • 01 to 02 core software portal contracts = 10 Marks. (20) | 20 | |
| Financial Strength & Standing
(Based on average annual turnover / tax paid in last 3 years) (Quantitative)(Doc Required) • More than 2 million PKR = 15 Marks • 1 to 2 million PKR = 10 Marks • Less than 1 million PKR = 05 Marks. (15) | 15 | |
| Affidavit of Clean Legal Track Record (non-blacklisting verification) • Requisite affidavit executed on judicial stamp paper confirming the entity has never been blacklisted or declared non-performer (Qualitative)(Doc Required) | 5 | |
| Affidavit of Resource Sufficiency & Integrity (Financial & anti-outsourcing execution capacity) • Requisite affidavit on judicial stamp paper ensuring in-house resource utilization and capability to sustain project pipelines (Qualitative)(Doc Required) | 5 | |
| Execution Plan / Project Methodology
(Accelerated 30-day timeline development/deployment sprints) (Qualitative)(Doc Required) • Good: Detailed architectural layout matching the 4-Week Sprint Roadmap = 15 Marks • Satisfactory: Standard execution workflow matching requirements = 10 Marks • Unsatisfactory: Weak delivery framework or generic timelines = 05 Marks. (15) | 15 | |
| Technical Capacity for Platform Scaling
(Concurrent traffic engine infrastructure) (Qualitative)(Doc Required) • Best Engineering Framework: Structural development architecture showing high scalability= 20 Marks • Medium Range Framework: Standard tier relational database architecture = 10 Marks • Low Quality Framework: Non-scalable baseline codebase architectures = 06 Marks. (20) | 20 | |
Positions Without Lots :
| Position | Delivery Schedule | Quantity | Bid Security |
|---|---|---|---|
| Design, Development, Testing, and Source-Code Delivery of Comprehensive Web-Based Portal of Pharmacy Council of Pakistan | Address: 304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad. Schedule: Strictly 30 Calendar Days from the Commencement Date of the Contract Award Quantity: 1/job |
1/job | 0 PKR |
| Application Support and Maintenance (Post-Warranty Period - First 6 Months) | Address: 304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad. Schedule: Month 7 to Month 12 post warrenty Quantity: 1/job |
1/job | 0 PKR |
| Application Support and Maintenance (Post-Warranty Period - First 6 Months) | Address: 304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad. Schedule: Month 13 to Month 24 Quantity: 1/job |
1/job | 0 PKR |
| Application Support and Maintenance (Post-Warranty Period - First 6 Months) | Address: 304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad. Schedule: Month 25 to Month 36 post Quantity: 1/job |
1/job | 0 PKR |
Yes
| Position | Related Services |
|---|---|
| Design, Development, Testing, and Source-Code Delivery of Comprehensive Web-Based Portal of Pharmacy Council of Pakistan | Development of Portal |
| Application Support and Maintenance (Post-Warranty Period - First 6 Months) | Support and Maintenance Post 6 Months |
| Application Support and Maintenance (Post-Warranty Period - First 6 Months) | Support and Maintenance from 12 to 24 Month |
| Application Support and Maintenance (Post-Warranty Period - First 6 Months) | Support and Maintenance from 24 to 36 Month |
Positions Without Lots :
Position: Design, Development, Testing, and Source-Code Delivery of Comprehensive Web-Based Portal of Pharmacy Council of Pakistan
Specifications / Requirements:
Complete design, engineering, deployment, and source-code delivery of a comprehensive web-based portal and mobile app (Android) for the Pharmacy Council of Pakistan. Must incorporate specialized active User Dashboards , role-based access control (RBAC), multi-factor authentication,1000+ institutes, centralized Student Enrollment Ledger to support 100,000+ student profiles, 8000+ Central Faculty Database, Automated Renewals Engine with automated triggers, and Raast banking hooks for computerized fee clearance. Final deliverables must include 100% uncompiled documented alphanumeric source code, database design schemas, and deployment trees optimized for the National Data Center (NDC) node. Execution of in-house resource capability under PPRA Rule 32(1)(f).Position: Application Support and Maintenance (Post-Warranty Period - First 6 Months)
Specifications / Requirements:
Warranty, Support and Maintenance Post-go-live support runs in two stages. Hosting is provided by PCP and is not part of either. Stage Duration Pricing Warranty 6 months from go-live Included in the development price Application support and maintenance 2.5 years, after warranty ends Quoted separately as an annual price (Annexure-III) During warranty, the Contractor fixes all defects at no extra cost and stabilizes the system after roll-out. Both stages cover: • Bug fixing and corrective maintenance. • Security patching of the application and its components. • Application monitoring, and support to PCP's hosting team for backups, restores and DR tests. • App updates for new Android and iOS versions and store policy changes. • Minor changes to configuration, reports and templates. • Helpdesk for PCP users during office hours, with escalation for critical issues. • Quarterly service reports on incidents and open issues.Position: Application Support and Maintenance (Post-Warranty Period - First 6 Months)
Specifications / Requirements:
4.21 Warranty, Support and Maintenance Post-go-live support runs in two stages. Hosting is provided by PCP and is not part of either. Stage Duration Pricing Warranty 6 months from go-live Included in the development price Application support and maintenance 2.5 years, after warranty ends Quoted separately as an annual price (Annexure-III) During warranty, the Contractor fixes all defects at no extra cost and stabilizes the system after roll-out. Both stages cover: • Bug fixing and corrective maintenance. • Security patching of the application and its components. • Application monitoring, and support to PCP's hosting team for backups, restores and DR tests. • App updates for new Android and iOS versions and store policy changes. • Minor changes to configuration, reports and templates. • Helpdesk for PCP users during office hours, with escalation for critical issues. • Quarterly service reports on incidents and open issues.Position: Application Support and Maintenance (Post-Warranty Period - First 6 Months)
Specifications / Requirements:
4.21 Warranty, Support and Maintenance Post-go-live support runs in two stages. Hosting is provided by PCP and is not part of either. Stage Duration Pricing Warranty 6 months from go-live Included in the development price Application support and maintenance 2.5 years, after warranty ends Quoted separately as an annual price (Annexure-III) During warranty, the Contractor fixes all defects at no extra cost and stabilizes the system after roll-out. Both stages cover: • Bug fixing and corrective maintenance. • Security patching of the application and its components. • Application monitoring, and support to PCP's hosting team for backups, restores and DR tests. • App updates for new Android and iOS versions and store policy changes. • Minor changes to configuration, reports and templates. • Helpdesk for PCP users during office hours, with escalation for critical issues. • Quarterly service reports on incidents and open issues.4. SCOPE OF WORK
4.1. The successful contractor will provide a secure, role-based, comprehensive web-based portal to digitize and automate the core regulatory, academic, inspection and administrative roadmap of the Pharmacy Council of Pakistan within a strict execution frame of 30 Days. The developer is fully bound under Rule 32(1)(f) to perform all development exclusively utilizing its own in-house engineering staff.
4.1.1 Core Functional Modules & Deliverables include but are not limited to:
4.1.2 User Roles & Access Management Dashboard Framework:
4.1.3 Secure Login and Access Infrastructure Setup:
4.2. The Contractor shall ensure that the software platform is engineered utilizing modern framework stacks, optimizing database queries to handle high concurrent user traffic from nationwide pharmacy institutes, faculty and student populations.
4.3. The Contractor shall ensure complete server-side encryption of all student and institutional records, protecting critical regulatory data.
4.4. The Contractor shall provide a full user training phase (conducted physically or via secure webinar channels) to all 7 user groups within the execution period.
4.5. The Contractor shall ensure the provision of complete system documentation including user manuals; administrator guides and architectural blueprints upon deployment.
4.6. The Contractor shall deploy the system on the secure designated public-cloud infrastructure or National Data Center nodes as finalized by the Procuring Agency.
4.7. The Contractor shall provide a 6-month post-deployment application software warranty covering critical bug-fixing, system logical stabilization and logic patching at zero supplementary development costs.
4.8. The Contractor shall comply with all relevant federal digital standards, e-governance guidelines, and cybersecurity parameters issued by the Ministry of IT.
4.9. The Contractor shall execute a formal Non-Disclosure Agreement with the Pharmacy Council of Pakistan prior to accessing legacy database elements.
4.10. As a contractual requirement of PCP, the State-Owned Entity shall execute the entire core portal development and source-code engineering through its own institutional resources. No private-sector entity shall be engaged for core system architecture, source-code development, database engineering, cybersecurity architecture or system integration. Any proposed outsourcing of a specialized ancillary component, if permitted, shall be separately disclosed, justified and approved and shall in all circumstances comply with the maximum limit prescribed under Rule 32(1)(f)(ii).
4.11. Integration with Provincial Pharmacy Council.
4.12. The Contractor shall provide a complete workflow and integration through API.
4.13. QR based application and registration certificate.
4.14. Online verification of the students.
4.15. The Contractor shall provide deployment installation scripts and configuration trees optimized for deployment on Pakistan-based National Data Center (NDC) node environments or cloud setups managed directly by PCP.
4.16. Scale the System Must Support
|
Item |
Volume |
|
Institutes |
About 1,000 (237 Pharm-D, 35 Post-Graduate, 716 Pharmacy Technician) |
|
Enrolled students |
About 100,000 (Pharm-D about 21,000 a year; Technician 35,000–40,000) |
|
Faculty |
About 8,000 |
|
Faculty-to-student ratio |
1:10 Pharm-D; 1:15 Technician |
|
Simultaneous inspection visits |
Report Generation and coordination |
|
Peak load period |
Student registration window, October to December |
4.1.4. What the system is for
One register for institutions, programmes, faculty, students, inspections, and pharmacists. Pharm.D and Pharmacy Technician are two programme types on the same institution record, not two systems.
A user should always land on work, not on a menu. The home screen answers three questions: what is due, what is blocked, and what was decided.
|
Question the user has |
Where they get the answer |
|
Can this college start Pharm.D? |
Institution profile, then NOC case, then decision letter |
|
Is accreditation still valid? |
Programme card: status, valid until, intake |
|
Is this teacher already claimed? |
Faculty ID search before linking |
|
Did this student finish? |
Student record: year, result, graduation |
|
Is this person a registered pharmacist? |
Public search by registration number |
Each university, college, or affiliated campus has one institutional account and an Institution ID, for example PCP-UNI-000123. People inside that account have jobs, not a shared password.
|
Role |
May do |
May not do |
|
Head of institution |
Submit applications, see decisions |
Edit an approved faculty link in place |
|
Principal or Dean |
Confirm programme data, respond to deficiencies |
See another institution |
|
Department administrator |
Maintain campus, labs, library |
Issue an NOC |
|
Data-entry officer |
Enter faculty and student drafts |
Submit without a second check |
|
Examination officer |
File annual results and evidence |
Change a locked year |
|
Finance officer |
Pay fees, see dues |
Alter academic records |
Once PCP has verified a faculty link, a later change opens a change request. The historical link stays visible on past NOCs and inspections.
|
Role |
Daily work |
|
Super administrator |
Users, roles, reference rules. Not routine case decisions. |
|
Secretary |
Council agenda, decisions, certificates. |
|
Registration officer |
Institution onboarding and pharmacist register. |
|
Inspection coordinator |
Teams, conflict check, schedule, report receipt. |
|
Panel member |
Checklist, photos, remarks. Own assigned visits only. |
|
Accounts officer |
Fees and outstanding dues that block submission. |
|
Verification officer |
Documents, faculty qualifications, duplicate checks. |
|
Step |
Who |
System does |
|
Create account |
Institution |
Sends email and mobile code |
|
Profile and affiliation |
Institution |
Saves draft; allows return later |
|
Campus and programme |
Institution |
One campus, then programmes under it |
|
Legal documents |
Institution |
Marks missing items before submit |
|
Verification |
PCP officer |
Accept, return, or reject with a reason |
|
Approval |
PCP |
Issues PCP-UNI-000123 and unlocks applications |
Every later NOC, accreditation, faculty link, student, and inspection hangs off this ID. If the institution has two campuses, each campus is a child record, not a second account, unless they are legally separate.
4.1.7. Pharm.D NOC as a Case File
The institution does not retype the approved profile. It opens New Pharm.D NOC, picks the campus, and fills only what is new: intake, faculty links, laboratories, library, and documents.
If a check fails, the screen lists the item and the rule, for example “Pharmacology: 1 teacher linked, 2 required for intake 50.” The user fixes that line. They are not sent back to page one.
|
Stage |
What the institution sees |
What PCP does |
|
Initial scrutiny |
In review |
Pass, or return a deficiency |
|
Deficiency |
Task with deadline and evidence needed |
Accept or reject the response |
|
Technical review |
In review |
Academic check against standards |
|
Inspection |
Date, team, and what to prepare |
Checklist on a tablet |
|
Council |
Awaiting decision |
Approve, defer, or reject |
|
Outcome |
NOC letter and number, or reasons |
Record is locked |
Defer is not a silent hold. It has a reason and a date to return. Reject states the grounds. Approve generates the NOC and writes the intake onto the programme card.
4.1.8. Accreditation and Renewal
Accreditation reads the same institution, faculty, and student records. The institution updates what changed and files a self-assessment. It does not rebuild the faculty list.
History stays on the programme card, for example accredited 2026–2029 for intake 100, renewal 2029–2032 for intake 120 pending. Old rows are not overwritten.
At 180, 120, 90, 60, and 30 days, and on the expiry date, the dashboard shows Renewal due with the date, and an email goes to the institution contacts. The institution opens the prepared file, confirms annual compliance, updates changes, and submits. Inspection and Council follow the same path as a first accreditation.
4.1.9. Pharmacy Technician
Same institution. Programme type is asked first: Pharm.D or Pharmacy Technician. The checklist, faculty rules, laboratory rules, and fee then load for that type. A college can hold both. Status of one does not hide the other.
4.1.10. Post Graduate Program Accreditation (MS/MPhil, and PhD)
Same institution. Programme type is asked first: MS/M.Phil. or PhD. Then asks for specific fields, i.e., Pharmaceutics, Pharmaceutical Chemistry, Pharmacognosy, Pharmacology, Pharmacy Practice/Clinical Pharmacy, or broadly Pharmaceutical Sciences or Pharmacy. The institute/University/HEI uploads the NOC for the PG programme issued by HEC. Then mention the faculty eligible for supervision. Fill the data in a separate PG module proforma of PCP.
4.1.11. Faculty: One person, One ID
Example record: PCP-FAC-000458, Dr Muhammad Ali, PhD Pharmacology, PCP registration, current institution, designation, Active. Institutions link this ID to a programme. They do not create a second Dr Ali.
Applied path: person registered, qualification checked, profile created, institution requests a link, PCP verifies, status becomes Active. Annual update is a task. Transfer, resignation, or retirement closes the link and keeps the history.
The duplicate check runs on registration number, CNIC where held, and a name-plus-institution warning. A spelling variant should offer “Did you mean PCP-FAC-000458?” rather than a new record.
4.1.12. Students and the Annual return
Student ID form: institution initials, year, serial. Examples: GU-2026-00012345, KUST-2026-00012345, QAU-2026-00012345. Store the institution ID as well, so a name change does not break the number. Suggested display: PCP-GU-2026-00012345.
Minimum fields: name, father’s name, CNIC, mobile, email, programme, session (morning, evening, or self-finance), year or semester, result, status.
Life of the record: enrol, validate, issue ID, progress, result, promote or repeat, graduate, degree check, eligible for registration. PCP can then count entrants, graduates, failures, and late completers by institution and year.
Each year the examination officer opens Annual student update, selects the year, and files enrolment, progression, pass, fail, repeat, graduates, withdrawals, and the result evidence. After PCP accepts it, that year locks. A later correction is a Correction request, with reason and evidence. The original figures remain visible.
4.1.13. Pharmacist Register and Public Check
The register holds personal data, university and graduation year, registration number, issue date, issuing council (Punjab, KP, GB, Balochistan, Sindh), and status Active or dormant. Practice place and designation are shown only if the pharmacist has confirmed them.
Public search by registration number returns name, number, category, status, and validity. It does not return CNIC, phone, email, or home address. A dormant or cancelled registration must say so in plain words.
4.1.14. Inspection and Deficiencies
Inspection is a module reused by NOC, accreditation, and renewal. Coordinator assigns a team. No member inspects an institution in their own province. The institution is notified of date and scope. The team uses a tablet: Compliant, Partially compliant, Non-compliant, or not applicable, plus remark, photo, and document. The report is submitted as a case file, not an email attachment.
A deficiency is a task, not a letter. Example: DF-2026-00452, Faculty, Outstanding, appoint a qualified teacher, 30 days, evidence is appointment letter and CV. The institution uploads and submits. PCP accepts or returns it. The dashboard counts outstanding items.
4.1.15. What each Dashboard Shows
Counts that open a list when clicked: institutions, active Pharm.D programmes, technician programmes, registered pharmacists, pending NOCs, pending accreditations, renewals inside 90 days, inspections this month, outstanding deficiencies, cases awaiting a decision. Charts by province, public or private, enrolment, graduates, faculty, and accreditation status sit below the task list, not above it.
ABC University, Active. Pharm.D: NOC approved, accreditation valid, 624 students, 38 faculty. Pharmacy Technician: NOC pending, 120 students. Action required: annual result due, faculty update due, renewal in 142 days, 3 deficiencies. Each line opens the task.
4.1.16. Messages, Files and Access: Email and a dashboard alert fire together for submission, receipt, return, deficiency, inspection date, decision, NOC, accreditation, expiry, and annual return. Every message is stored on the case.
Files sit under the institution: legal, university, NOC, accreditation by year, inspections, faculty, students, correspondence. Each file has version, date, uploader, type, verification, expiry, and a hash. Replacing a file adds a version. It does not delete the previous one.
Sign-in uses a password and a one-time code for officers and for anyone submitting a decision or a payment. An institution sees only itself. An officer sees assigned cases. A super administrator sees the system. Session timeout applies on shared office computers.
4.1.17. Suggested Bill Order
|
Phase |
What goes live |
Why first |
|
1 |
Onboarding, Institution ID, users |
Nothing else can attach without it |
|
2 |
Faculty ID and duplicate check |
Stops false faculty before NOC opens |
|
3 |
Pharm.D NOC case, fee, deficiency |
Highest-volume regulatory path |
|
4 |
Inspection checklist and report |
Used by every later decision |
|
5 |
Accreditation and renewal alerts |
Reuses NOC data |
|
6 |
Student ID and annual return |
Needs a stable institution first |
|
7 |
Pharmacist register and public verify |
Public trust piece; keep the screen small |
|
8 |
Technician programme rules |
Same engine, different checklist |
4.1.18. Further Digitization Points
These points extend the sections above. They cover identity checks, certificates, service levels, security, reporting, field work, and the move from paper. Figure 4 shows how the parts fit together.
|
Layer / Component |
Required / Proposed Technology |
|
Frontend |
React.js with Tailwind CSS / Bootstrap; responsive, mobile-friendly interface |
|
Backend |
Laravel (PHP) |
|
Database |
PostgreSQL / MySQL relational database |
|
Authentication |
Secure session/OAuth2-based login, email verification or credential based verification and role-based access control |
|
Third-party services |
SMS & Email delivery service for verification and notifications |
4.21 Warranty, Support and Maintenance
Post-go-live support runs in two stages. Hosting is provided by PCP and is not part of either.
|
Stage |
Duration |
Pricing |
|
Warranty |
6 months from go-live |
Included in the development price |
|
Application support and maintenance |
2.5 years, after warranty ends |
Quoted separately as an annual price (Annexure-III) |
During warranty, the Contractor fixes all defects at no extra cost and stabilizes the system after roll-out. Both stages cover:
PART 3 – CONDITIONS OF CONTRACT & CONTRACT FORMS
5. GENERAL CONDITIONS
5.1. The Client at its discretion can increase/decrease or modify the functional modules or user dashboard layouts on already negotiated project criteria and on the same terms & conditions. Any increase or decrease in scope shall be handled strictly via formal change-order procedures in accordance with the maximum variation limits prescribed under PPRA rules.
5.2. The Contractor shall ensure the active deployment of technical project teams and shall submit a weekly milestone progress report verified by the technical committee of the client.
5.3. The Contractor shall be liable to provide the complete functional scope at site; any technical failure or delayed sprint shall entitle the client to invoke structural delays penalties.
5.4. The Contractor will provide highly qualified software engineers, database architects and system analysts of sound technical standing and ensure all personnel maintain active clearance credentials.
5.5. The Contractor shall ensure disbursement of employee compensation to its project engineers via direct official bank transfers instead of cash payments.
5.6. The agreement shall be effective from the date of signing.
5.7. The Contractor entity shall be responsible to cover all operational costs of software engineering, including payment of salaries to its engineers as per statutory scales and all applicable federal levies. If any compliance breach is observed, the authority reserves the right to cancel the allocation.
5.8. Any structural modifications to legal statutory federal tax levies during the 30-day timeline lifecycle shall follow national corporate accounting protocols.
5.9. The Contractor will keep the Authority completely free of any liability for any third-party software licensing infringements or source code copy protection claims or any hidden charges not made aware during the contracting.
5.10. One-month prior notice in writing shall be served by either party for termination of contract.
5.11. The Authority shall process the contract payment on a milestone delivery basis or a unified lump-sum upon final complete launch and clearance of User Acceptance Testing (UAT).
5.12. The Contractor Entity shall possess an active standing of executing critical public-sector automation suites and software engineering platforms within Pakistan.
5.13. Affidavit to the effect that the contractor has not been blacklisted or declared non-performer by any Government Department or Regulatory Authority.
5.14. The Contractor must have the operational financial capacity to sustain project execution pipelines using its own institutional resources as per the undertaking.
5.15. The selected firm will provide a fully operational, live system within exactly thirty (30) days from the date of receipt of the formal work order. This delivery timeline may be extended exactly one (1) time, subject to the formal review, written approval and clearance of the procurement Committee of the Council. After which a fine of 0.2% of the total proposal value per calendar day will be charged to the firm for any delay beyond this deadline subject to a maximum of the total 10% contract value.
5.17. Proponent not 'active' on the active taxpayer list of FBR are not eligible.
5.19. The Proponent shall quote for the full complete development in the financial proposal on EPADS. Post-deployment minor configuration changes requested by the PCP within the first 6 months shall be executed without any supplementary invoicing.
5.20. Company or organization shall be bound to handover all the workflows, source code, system architecture, database design and pen testing cyber security reports to pharmacy council of Pakistan.
5.21. The Contractor shall provide a six (6) month warranty after go-live free of cost, followed by (2.5) years application support and maintenance under the service levels in clause 4.1.10, priced separately in Annexure-III.
5.22. The final proposal shall remain uploaded and active on the system for a minimum duration of 72hr hours. During this period, the proposal will be shared digitally with more than one entity categorized as State-Owned Enterprises (SOEs) currently available on the electronic Public Procurement Administrative (EPAD) platform.
5.23 The selected firm shall provide a fully functional mobile application version (android) of the portal free of cost, delivered under the same terms, conditions and delivery timelines specified for the web-based system.
5.24 6 months technical support will be provided by the contractor.
5.25 Software Backup including Database will be handed over to PCP.
5.26 Application should be mobile responsive.
5.27 Arrangement of Trainings sessions for officers of PCP.
5.28 System Backup creation protocols and automated database backup scripting logic must be compiled into the source architecture by the developer.
5.29 All standard software runtimes, frameworks and specialized developer libraries utilized in the application layer must be entirely open-source with least dependency on libraries.
For Individual Positions
| # | Position Title | Quantity | Unit Price (PKR) | Total Price (PKR) | Delivery Location | Delivery Period / Year | Country of Origin |
|---|---|---|---|---|---|---|---|
| 1 | |||||||
| 2 |
| # | Lot Title | Total Lot Price (PKR) | Country of Origin |
|---|---|---|---|
| 1 | [Lot 1 Title] |
The following Special Conditions of Contract shall supplement the General Conditions of Contract. Whenever there is a conflict, the provisions herein shall prevail over those in the Conditions of Contract. The corresponding clause number of the GCC is indicated in parentheses.
Number of GC Clause
Amendments of, and Supplements to, Clauses in the General Conditions of Contract
Definitions
The Procuring Agency is: Pharmacy Council of Pakistan (Admin & Technical), Secretary PCP 304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad.
Contractor is:
The title of the subject procurement is:DESIGN, DEVELOPMENT, TESTING AND SOURCE CODE DELIVERY OF COMPREHENSIVE WEB-BASED PORTAL OF PHARMACY COUNCIL OF PAKISTAN
Number of GC Clause 2
Applicable/Governing Law:
The Contract shall be interpreted in accordance with the laws of Islamic Republic of Pakistan
Number of GC Clause 3
Language:
The language of the Contract, all correspondence and communications to be given, and all other documentation to be prepared and supplied under the Contract shall be in English.
Number of GC Clause 4
Notices:
The addresses for the notices are:
Procuring Agency:
Pharmacy Council of Pakistan (Admin & Technical), Secretary PCP
304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad.
+92-519-218-995
secretary@pcpisb.gov.pk
Contractor/ Bidder:
[Name, address and telephone number].
The Contractor/ Bidder’s Representative(s)
[Name, address, telephone number and e-mail address]
Number of GC Clause 6.1
The Authorized Representatives are:
For the Procuring Agency:
Pharmacy Council of Pakistan (Admin & Technical), Secretary PCP
304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad.
+92-519-218-995
secretary@pcpisb.gov.pk
For the Bidder:
Name: ………………………
Designation: ……………..
Address: ……………………………..
Number of GC Clause 7
Effectiveness of the contract
The Contractor/Bidder shall be effective within ….. days from the date of signature of the Contract by both parties
Number of GC Clause 8
Commencement of Contract:
The Contractor/ Bidder shall provide Non-Consultancy Services from the effective date of contract.
Number of GC Clause 10.2
Expiration of Contract:
The time period shall be ………………….
Number of GC Clause 14
Termination
In the event of termination of the contract due to any reason as already defined in the General Conditions of Contract, the Bidder shall be responsible for providing to the Authority the Goods till the time of alternate arrangements.
Number of GC Clause 16
Conflict of Interest:
The Procuring Agency reserves the right to determine on a case-by-case basis whether the Bidder should be disqualified from providing goods or services due to a conflict of a nature described in Clause GCC 16.
Number of GC Clause 20
Liquidated Damages
If the Bidder fails to provide services as required under the contract or in case of any data loss/data breach or any incident compromising the data security or other such failures related to any services, the Bidder shall pay to the Procuring Agency as Liquidated Damages at a rate of 0.20% to 10.00% of the Contract value, in accordance with the extent of performance failure & the cost of investigating such incidents as judged by the Authority.
Number of GC Clause 21
Performance Guarantee:
Instrument of Performance Guarantee shall be in the Name of : Nil
The amount of performance guarantee shall be 0% of the contract price in acceptable form of Nil
Number of GC Clause 27
Currency of Payment:
All the payment to be released to the contractor/Bidder shall be in Pakistani Rupees.
Number of GC Clause 28
Payment terms:
Payment will be made to the Bidder against the procured Goods and services according to the actual invoice or running bills submitted by the Bidder against the services provided within the time given in the conditions of the contract.
Number of GC Clause 29
Identifying Defects:
The Authority reserves the right at any time to inspect the premises of the provider to inspect the goods and monitor the goods being provided.
For conformance to specifications and performance parameters, through Prior to delivery inspection (Inspection Report by Procurement Committee / Inspection Team)
For successful operation at site after complete installation, testing and commissioning of the equipment (Installation, Testing and Commissioning Report by Procurement Committee / Inspection Team)
The Contractor Firm is required to submit the following documents along with the final invoices:1. Invoice with covering letter. 2. User Acceptance Testing (UAT) clearance certificate signed by the PCP Committee. 3. System architecture manual and deployment log keys. 4. Declaration of in-house resource utilization.
CONFIDENTIALITY AND DATA SECURITYThe Contractor shall ensure that the proposed web portal, database architecture and mobile applications are built, hardened and maintained in strict compliance with the Pakistan Information Security Framework (PISF), the National Cyber Security Policy and the CERT Rules issued by the Government of Pakistan.The software development lifecycle must incorporate mandatory Secure Software Development Lifecycle practices.
Copies of the Supplier’s invoice showing Goods’ description, quantity, unit price, and total amount;
Manufacturer’s or Supplier’s Valid Warranty Certificate;
INTELLECTUAL PROPERTY AND SOURCE CODE all project-specific source code, configurations, database structures, documentation and deliverables developed specifically for PCP under this procurement shall be handed over to PCP upon completion and payment, subject to applicable Government rules and contractual terms.
Strict execution window of exactly thirty (30) calendar days from the Commencement Date of Contract for full live turnkey development and complete uncompiled source code delivery.Unexcused delay extending beyond the strict 30-day deadline triggers a fine of 0.2% of the total proposal value per calendar day subject to 1 time extension by the committee
Number of GC Clause 31
Following is the guidance for Dispute Resolution
Notwithstanding any reference to the arbitration herein, the parties shall continue to perform their respective obligations under the Contract unless they otherwise agree that the Authority shall pay the Bidder any monies due to the Bidder.
Arbitrator’s fee:
The fee shall be specified in Pak Rupees, as determined by the Arbitrator, which shall be shared equally by both parties.
Appointing Authority for Arbitrator:
By the Mutual Consent or in accordance with the provisions of Arbitration Act, 1940, in case the parties fail to reach a consensus on the name of sole arbitrator, any party may submit an application to the Chief Justice Islamabad High Court for appointment of sole arbitrator. The Chief Justice IHC may appoint a former judge of any High Court or Supreme Court as the sole arbitrator to resolve the dispute between the parties.
Rules of procedure for arbitration proceedings:
Any dispute between the Authority and a Bidder who is a national of the Islamic Republic of Pakistan arising in connection with the present Contract shall be referred to adjudication or arbitration in accordance with the laws of the Islamic Republic of Pakistan including Arbitration Act 1940, however above provision shall prevail in referring the case to the Arbitrator.
Place of Arbitration and Award:
The arbitration shall be conducted in English language and place of arbitration shall be at Islamabad. The award of the arbitrator shall be final and shall be binding on the parties.
Date: [insert date (as day, month and year)]
Bid No.:P190197
To: Pharmacy Council of Pakistan (Admin & Technical), Secretary PCP 304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad.
We, the undersigned, declare that:
We understand that, according to your conditions, Bids must be supported by a Bid Securing Declaration.
We accept that we will be blacklisted and henceforth cross debarred for participating in respective category of public procurement proceedings for a period of (not more than) six months, if fail to abide with a bid securing declaration, however without indulging in corrupt and fraudulent practices, if we are in breach of our obligation(s) under the Bid conditions, because we:
We understand this Bid Securing Declaration shall expire if we are not the successful
Bidder, upon the earlier of (i) our receipt of your notification to us of the name of the successful Bidder; or (ii) twenty-eight (28) days after the expiration of our Bid.
THIS AGREEMENT made the _____ day of __________ 20_____ between Pharmacy Council of Pakistan (Admin & Technical), Secretary PCP 304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad.
(hereinafter called “the Procuring Agency”) of the one part and [name of Bidder] of [city and country of Bidder] (hereinafter called “the Bidder”) of the other part:
WHEREAS the Procuring Agency invited Bids for provision of goods, viz., DESIGN, DEVELOPMENT, TESTING AND SOURCE CODE DELIVERY OF COMPREHENSIVE WEB-BASED PORTAL OF PHARMACY COUNCIL OF PAKISTAN (P190197) and has accepted a Bids by the Bidder for the provision of Services in the sum of [contract price in words and figures] (hereinafter called “the Contract Price”).
NOW THIS CONTRACT WITNESSETH AS FOLLOWS:
1. In this Contract words and expressions shall have the same meanings as are respectively assigned to them in the Conditions of Contract referred to.
2. The following documents shall be deemed to form and be read and construed as part of this Contract, In the event of any ambiguity or conflict between the Contract Documents listed below, the order of precedence shall be the order in which the Contract Documents are listed below:-
3. In consideration of the payments to be made by the Procuring Agency to the Bidder as hereinafter mentioned, the Bidder hereby covenants with the Procuring Agency to provide the Goods related services and to remedy defects therein in conformity in all respects with the provisions of the Contract.
4. The Procuring Agency hereby covenants to pay the Bidder in consideration of the provision of Goods and the remedying of defects therein, the Contract Price or such other sum as may become payable under the provisions of the contract at the times and in the manner prescribed by the contract.
IN WITNESS whereof the parties hereto have caused this Contract to be executed in accordance with their respective laws the day and year first above written.
Signed, sealed, delivered by __________________the ________________ (for the Procuring Agency)
Witness to the signatures of the Procuring Agency:
………………………………………………
Signed, sealed, delivered by __________________the ________________ (for the Procuring Agency)
Witness to the signatures of the Bidder: …………………………………………………
Contract Number: Contract Value: Contract Title:
Dated:
[Name of Supplier] hereby declares that it has not obtained or induced the procurement of any contract, right, interest, privilege or other obligation or benefit from Government of Pakistan or any administrative subdivision or agency thereof or any other entity owned or controlled by it (GoP) through any corrupt business practice.
Without limiting the generality of the foregoing [Name of Supplier] represents and warrants that it has fully declared the brokerage, commission, fee etc. paid or payable to anyone and not given or agreed to give and shall not give or agree to give to anyone within or outside Pakistan either directly or indirectly through any natural or juridical person, including its affiliate, agent, associate, broker, consultant, director, promoter, shareholder, sponsor or subsidiary, any commission, gratification, bribe, finder's fee or kickback, whether described as consultations fee or otherwise, with the object of obtaining or inducing the procurement of a contract, right, interest, privilege or other obligation or benefit in whatsoever form from GoP, except that which has been expressly declared pursuant hereto.
[Name of Supplier] certifies that it has made and will make full disclosure of all agreements and arrangements with all persons in respect of or related to the transaction with GoP and has not taken any action or will not take any action to circumvent the above declaration, representative or warranty.
[Name of Supplier] accepts full responsibility and strict liability for making and false declaration, not making full disclosure, misrepresenting fact or taking any action likely to defeat the purpose of this declaration, representation and warranty. It agrees that any contract, right interest, privilege or other obligation or benefit obtained or procured as aforesaid shall, without prejudice to any other right and remedies available to GoP under any law, contract or other instrument, be voidable at the option of GoP.
Notwithstanding any rights and remedies exercised by GoP in this regard, [Name of Supplier] agrees to indemnify GoP for any loss or damage incurred by it on account of its corrupt business practices and further pay compensation to GoP in an amount equivalent to ten time the sum of any commission, gratification, bribe, finder's fee or kickback given by [Name of Supplier] as aforesaid for the purpose of obtaining or inducing the procurement of any contract, right, interest, privilege or other obligation or benefit in whatsoever form from GoP.
To: Pharmacy Council of Pakistan (Admin & Technical), Secretary PCP 304-A Evacuee Trust Complex Agha Khan Road F5/1, Islamabad.
WHEREAS [name of Bidder] (hereinafter called “the Bidder”) has undertaken, in pursuance of Contract No. [reference number of the contract] dated [insert date] for provision of Non-Consultancy Services(hereinafter called “the Contract”).
AND WHEREAS it has been stipulated by you in the said Contract that the Bidder shall furnish you with a Bank Guarantee by a reputable bank for the sum specified therein as security for compliance with the Bidder’s performance obligations in accordance with the Contract.
AND WHEREAS we have agreed to give the Bidders guarantee:
THEREFORE, WE hereby affirm that we are Guarantors and responsible to you, on behalf of the Bidder, up to a total of [amount of the guarantee in words and figures], and we undertake to pay you, upon your first written demand declaring the Bidder to be in default under the Contract and without cavil or argument, any sum or sums within the limits of [amount of guarantee] as aforesaid, without your needing to prove or to show grounds or reasons for your demand or the sum specified therein.
This guarantee is valid until the: [insert date]
Signature and seal of the Guarantors
_____________________________________________________________________
[name of bank or financial institution]
_____________________________________________________________________
[address]
_____________________________________________________________________
[date}
This Contract shall be read as an indivisible whole. The Request for Proposal (RFP), the complete Technical and Financial Proposals, the Scope of Work, and all associated terms and conditions are hereby explicitly incorporated into this agreement. Any specification, milestone, or compliance criteria outlined previously shall be read as mandatory, binding, and strictly enforceable, whether reproduced herein or referenced line-by-line
UNDERTAKING (RESOURCE INTEGRITY & CAPACITY)
I/We, M/S [ ], Islamabad, hereby undertake and give firm statutory assurance to the Pharmacy Council of Pakistan that our entity is technically and financially robust, possesses fully available in-house software engineering personnel, and has the absolute capacity to execute the full design, engineering, development/deployment and launch of the web-based PCP Portal within the mandatory thirty (30) calendar days timeframe. We further declare that in accordance with PPRA Rule 32(1)(f), the portal development shall be conducted by our permanent staff and third-party private developer shall be sub-contracted or engaged for this project non outside as mentioned in 32(1)(f).
THIS AGREEMENT is made on the _______ day of _________ 2026 between 'Pharmacy Council of Pakistan (PCP), Islamabad of one part and 'M/S [ ] having its offices at (Address).
WHEREAS the Authority is desirous of availing the specialized software development, digital automation, installation and commissioning services of the Contractor for a comprehensive web-based PCP Portal as per rates, specifications, and accelerated 30-day turnaround terms contained in the letter of acceptance / proposal documents / negotiated financial quotation, and the contractor has accepted to provide the said services as per functional scope, timeline, and terms contained in the proposal blueprint for contract duration.
NOW THIS AGREEMENT WITNESSETH as follows:
1. In this agreement words and expressions shall have the same meaning as are respectively assigned to them in the Conditions of Contract.
2. The following documents shall be deemed to form and be read and construed as an integral part of this agreement, viz:
a) This Contract Agreement
b) The Letter of Acceptance / Work Order
c) The RFP baseline scope
d) The Technical Compliance Sheet and Financial Quotation submitted via EPADS
3. The aforesaid documents shall be taken as complementary and mutually explanatory of one another, but in the case of ambiguities, shall take precedence in the order set out above.
4. In consideration of the payment to be made by the Authority to the Contractor, the Contractor hereby covenants with the Authority to design, develop, secure, and deploy the complete portal in conformity in all respects with the 30-day timeline.
5. The Authority hereby covenants to pay to the Contractor in consideration of the development services the amount due in accordance with the provisions of the contract.
Submitted the Financial Proposal accordingly.
Copies of relevant Completion Certificates / active Work Orders / Contracts from Public/Reputable entities.
Human Resource list detailing permanent software developers, database managers, and QA teams
|
Active Taxpayer List (ATL) status verifications for NTN and General Sales Tax (GST) with FBR. |
|
FBR Tax Returns / Audited Statement for the last three consecutive financial years. |
Copies of relevant Completion Certificates / active Work Orders / Contracts from Public/Reputable entities
An affidavit executed on judicial stamp paper verifying that the entity has never been blacklisted
Financial Strength & Standing
(Based on average annual turnover / tax paid in last 3 years)