In terms of Rule 48 of Public Procurement Rules, 2004 Grievance Redressal Committee (GRC) is notified for the subject procurement and notification copy is available on the procuring agency’s website and on Authority’s website at (www.ppra.org.pk).
Ministry of Foreign Affairs (Ministry of Foreign Affairs (MOFA)), Deputy Director
Constitution Avenue, Sector G-5., Islamabad Capital Territory
+92-347-725-9108
adgs.sykb@mofa.gov.pk
1.1 The Procuring Agency (PA), as indicated in the Bids Data Sheet (BDS) invites Bids through EPADS v2.0 for the provision of Goods for as specified in the BDS and in Section V – Evaluation Criteria, Specifications & Schedule of Requirements. The name, identification, and number of items/deliverables are provided in the BDS. The successful Bidders will be expected to provide the goods within the specified period and timeline(s) as stated in the BDS.
2.1 Source of funds is referred in Clause-1 of Invitation for Bids.
3.1 A Bidder may be natural person, company or firm or public or semi-public agency of Pakistan or any foreign country, or any combination of them with a formal existing agreement (on Judicial Papers) in the form of a joint venture, consortium, or association. In the case of a joint venture, consortium, or association, all members shall be jointly and severally liable for the execution of the Contract in accordance with the terms and conditions of the Contract. The joint venture, consortium, or association shall nominate a Lead Member as nominated in the BDS, who shall have the authority to conduct all business for and on behalf of any and all the members of the joint venture, consortium, or association during the Bidding process, and in case of award of contract, during the execution of the contract.
3.2 Verifiable copy of the agreement that forms a joint venture, consortium or association shall be required to be submitted as part of the Bid.
3.3 The appointment of Lead Member in the joint venture, consortium, or association shall be confirmed by submission of a valid Power of Attorney to the Procuring Agency.
3.4 Any bid submitted by the joint venture, consortium or association shall indicate the part of proposed contract to be performed by each party and each party shall be evaluated (or post qualified if required) with respect to its contribution only, and the responsibilities of each party shall not be substantially altered without prior written approval of the Procuring Agency and in line with any instructions issued by the Authority.
(The limit on the number of members of JV or Consortium or Association may be prescribed in BDS, in accordance with the guidelines issued by the PPRA).
3.5 The invitation for Bids is open to all prospective suppliers, manufacturers, or authorized agents / dealers subject to any provisions of incorporation or licensing by the respective national incorporating agency or statutory body established for that particular trade or business. Procuring agencies shall specify the registration/licensing requirements for the foreign bidders keeping in view the requirement of that business.
3.6 A Bidder shall not have a conflict of interest. All Bidders found to have a conflict of interest shall be disqualified. A Bidder may be considered to have a conflict of interest with one or more parties in this Bidding process, if they:
3.7 A Bidder may be ineligible if –
3.8 As and when required, bidders shall provide to the Procuring Agency evidence of their eligibility, proof of compliance with the necessary legal requirements to carry out the contract effectively.
3.9 Bidders shall submit Bids relating to the nature, conditions and modalities of sub-contracting wherever the sub-contracting of any elements of the contract amounting to more than ten (10) percent of the Bid price is envisaged.
4.1 All goods and related services to be supplied under the contract shall have their origin in eligible source countries, and all expenditures made under the contract will be limited to such goods and services. For purpose of this Bid, ineligible countries are the countries declared ineligible by the Federal Government.
5.1 A bidder shall submit only one Bid, in the same bidding process, either individually as a Bidder or as a member in a joint venture or any similar arrangement.
5.2 The Bidder shall not engage a subcontractor for any portion of the contract if the value of such subcontracting exceeds thirty percent (30%) of the total contract amount.
6.1 Any cost incurred by the bidder relating to the preparation and submission of its Bid shall be borne by the bidder, and the Procuring Agency shall in no case be responsible or liable for those costs, regardless of the conduct or outcome of the bidding process.
7.1 The Goods required, Bidding procedures, and terms and conditions of the contract are prescribed in the Bidding Documents. In addition to the Invitation for Bids, the Bidding documents which should be read in conjunction with any addenda issued in accordance with ITB 9.1 include:
Section I -Invitation to Bids
Section II Instructions to Bidders (ITB)
Section III Bid Data Sheet (BDS)
Section IV Evaluation Criteria, Specifications, Schedule of Requirements
Section V Bid Forms
Section VI General Conditions of Contract (GCC)
Section VII Special Conditions of Contract (SCC)
Section VIII Contract Forms
7.2 The Bidder is expected to examine all instructions, forms, terms and specifications in the Bidding documents. Failure to furnish all the information required in the Bidding documents through EPADS v2.0 will be at the Bidder’s risk and may result in the rejection of his Bids.
8.1 A prospective Bidder requiring any clarification of the Bidding documents may notify the Procuring Agency through EPADS v2.0.
8.2 The Procuring Agency will within three (3) working days after receiving the request for clarification, respond to any request for clarification through EPADS v2.0 provided that such request is received not later than three (03) days prior to the deadline for the submission of Bids as prescribed in ITB 22
8.3 Copies of the Procuring Agency's response will be forwarded to all identified Prospective Bidders through EPADS v2.0, including a description of the inquiry, but without identifying its source.
8.4 Should the Procuring Agency deem it necessary to amend the Bidding document as a result of a clarification, it shall do so following the procedure under ITB 9.
8.5 If indicated in the BDS, the Bidder’s designated representative is invited at the Bidder’s cost to attend a pre-Bid meeting at the place, date and time mentioned in the BDS. During this pre-Bid meeting, prospective Bidders may request clarification of the schedule of requirement, the Evaluation Criteria or any other aspects of the Bidding document.
8.6 Minutes of the pre-Bid meeting, if applicable, including the text of the questions asked by Bidders, including those during the meeting (without identifying the source) and the responses given, together with any responses prepared after the meeting will be uploaded on EPADS v2.0. Any modification to the Bidding documents that may become necessary as a result of the pre-Bid meeting shall be made by the Procuring Agency exclusively through the use of an Addendum pursuant to ITB 9. Non-attendance at the pre-Bid meeting will not be a cause for disqualification of a Bidder.
9.1 Before the deadline for submission of Bids, the Procuring Agency for any reason, whether at its own initiative or in response to a clarification requested by a prospective Bidder or Pre-Bid meeting may modify the Bidding documents by issuing addenda through EPADS v2.0.
9.2 The Procuring Agency shall promptly publish the addendum through EPADS v2.0.
9.3 Any addendum issued including the notice of any extension of the deadline shall also be communicated through EPADS v2.0 to all the bidders who have already submitted their bids. Such bidders shall have the right to withdraw their already submitted bid and re-submit the revised bid prior to the original or extended bid submission deadline.
9.4 To give prospective Bidders reasonable time in which to take an addendum/corrigendum into account in preparing their Bids, the Procuring Agency may, at its discretion, extend the deadline for the submission of Bids through EPADS v2.0:
Provided that the Procuring Agency shall extend the deadline for submission of Bids, if such an addendum is issued within last three (03) days of the Bids submission deadline.
10.1 The Bid prepared by the bidder, as well as all correspondence and documents relating to the Bids exchanged by the Bidder and the Procuring Agency shall be written in the English language unless otherwise specified in the BDS. Supporting documents and printed literature furnished by the Bidder may be in another language provided they are accompanied by an accurate translation of the relevant pages in the English language unless otherwise specified in the BDS, in which case, for purposes of interpretation of the Bidder, the translation shall govern.
11.1 The Bid prepared by the Bidder shall constitute thedocuments required in the BDS.
Details of sample(s) where applicable and requested in the BDS.
1. Documentary evidence established in accordance with ITB that the Bidder is eligible and/or qualified for the subject bidding process;
2. Documentary evidence establish that the Bidder has been authorized by the manufacturer to deliver the goods into Pakistan, where required and where the supplier is not the manufacturer of those goods;
3. Documentary evidence establish that the goods and related services to be supplied by the Bidder are eligible goods and services, and conform to the Bidding Documents;
4. Bid security or Bid Securing Declaration furnished in accordance with ITB 18.
12.1 To establish the conformity of the bidder to the Bidding document, the Bidder shall furnish as part of its Bids the documentary evidence that Goods provided conform to the technical specifications and standards.
13.1 The Bidder shall furnish, as part of itsBid, all those documents establishing the Bidder’s eligibility to participate in the Bidding process and/or its qualification to perform the contract if its Bid is accepted.
14.1 The Bidder shall fill the Form of Bid furnished in the Bidding documents.The Bids Form must be completed without any alterations to its format and no substitute shall be accepted.
15.1 The Bids Prices quoted by the Bidder in the Form of Bid and in the Price Schedules shall conform to the requirements specified below or exclusively mentioned hereafter in the Bidding documents.
15.2 All items in the Schedule of Requirement must be listed and priced separately in the Price Schedule(s). If a Price Schedule shows items listed but not priced and neither explicitly denied, their prices shall be construed to be included in the prices of other items.
15.3 Items not listed in the Price Schedule shall be assumed not to be included in the Bid, and provided that the Bid is still substantially responsive in their absence or due to their nominal nature, the corresponding average price of the respective item(s) of the remaining substantially responsive Bidder(s) shall be construed to be the price of those missing item(s)
15.4 The Bid price to be quoted in the Form of Bid in accordance with ITB 14.1 shall be the total price of the Bid.
15.5 The Bidder shall indicate on the appropriate Price Schedule, the unit prices (where applicable) and total Bid price of the Goods it proposes to provide under the contract.
15.6 Prices quoted by the Bidder shall be fixed during the Bidder’s performance of the contract and not subject to variation on any account. A Bid submitted with an adjustable price will be treated as non-responsive and shall be rejected.
16.1 Prices shall be quoted in Pakistani Rupees unless otherwise specified in the BDS in accordance with Rule 30 (2) of the Public Procurement Rules, 2004.
17.1 Bids shall remain valid for the period specified in the BDS after the Bid submission deadline prescribed by the Procuring Agency. A Bid valid for a shorter period shall be rejected by the Procuring Agency as non-responsive. The period of Bid validity will be determined from the complementary Bid securing instrument, i.e. the expiry period of Bid Security or Bids Securing Declaration as the case may be.
17.2 The procuring agency shall ordinarily be under an obligation to process and evaluate the bid and to issue letter of award within the stipulated bid validity period.
17.3 Under exceptional circumstances, prior to the expiration of the initial Bid validity period, the Procuring Agency may request the Bidders’ consent to an extension of the period of validity of their Bids only once through EPADS v2.0, for the period not more than the period of initial bid validity. The Bid Security provided under ITB 18 shall also be suitably extended. A Bidder may refuse the request without forfeiting its Bid security or causing to be executed its Bid Securing Declaration. A Bidder agreeing to the request will not be required nor permitted to modify its Bid, but will be required to extend the validity of its Bid Security or Bid Securing Declaration for the period of the extension.
18.1 The Bidder shall furnish as part of its Bid, a Bid Security in accordance with Rule 25 of the Public Procurement Rules, 2004.
18.2 The original Bid Security shall be enclosed within the sealed envelope and to be submitted physically before closing time for submission of bids. Whereas, scanned copy of bid security shall be uploaded electronically through EPADS v2.0 before closing hours for submission of bids.
18.3 The Bidder who failed to submit the original Bids security before the submission deadline shall be disqualified straightaway.
18.4 The Bid Security or Bid Securing Declaration is required to protect the Procuring Agency against the risk of Bidder’s conduct which would warrant the security’s forfeiture, pursuant to ITB 18.7.
18.5 The Bid Security shall be denominated in the local currency, and it shall be a Bank Draft in the name of the Procuring Agency and valid for twenty-eight (28) days beyond the end of the validity of the Bid. This shall also apply if the period for Bids/Bid Validity is extended. In either case, the form must include the complete name of the Bidder.
18.6 The Bid Security shall be payable promptly upon written demand by the Procuring Agency in case any of the conditions listed in ITB 18 are invoked.
18.7 Unsuccessful Bidders’ Bid Security will be discharged or returned as promptly as possible, however in no case later than thirty (30) days after the expiration of the period of Bids Validity prescribed by the Procuring Agency pursuant to ITB 17. The Procuring Agency shall make no claim to the amount of the Bid Security, and shall promptly return the Bid Security document, after whichever of the following that occurs earliest:
18.8 The successful Bidder’s Bids Security will be discharged upon the Bidder signing the contract, or furnishing the Performance Guarantee.
18.9 The Bid Security may be forfeited or the Bid Securing Declaration executed:
19.1 Before Bid submission deadline, any Bidder may withdraw, substitute, or modify its Bid after it has been submitted through EPADS v2.0. Bids requested to be withdrawn, shall be returned unopened to the Bidders through EPADS v2.0.
20.1 The Bidder shall prepare and submit Bids with due diligence after carefully reading all the terms and condition before bid submission deadline through EPADS v2.0.
21.1 The Technical and Financial Bids if required to submitted, shall be submitted on EPADS v2.0.
22.1 Bids shall be received by the Procuring Agency through EPADS v2.0 before bid submission deadline.
22.2 The Procuring Agency may, under exceptional circumstances, extend the deadline for the submission of Bids, after recording reasons in writing and in an equal opportunity manner.
In such case, all rights and obligations of the Procuring Agency and the Bidders that were previously governed by the original deadline shall thereafter be subject to the revised deadline.
23.1 The Bid Evaluation Committee of the Procuring Agency shall open all Bids through the EPADS v2.0, on the date and time specified in the Bid Data Sheet (BDS).
23.2 The Bid Evaluation Committee shall generate minutes through EPADS v2.0 containing brief details of bid opening process. The record of the Bid opening shall include, as a minimum: the name of the Bidder, the Bid price if applicable, and the presence or absence of a Bid Security or Bid Securing Declaration.
23.3 The procuring agency shall live broadcast the opening of bids on national media or on their website or digital channels, if the volume of procurement exceeds five hundred million rupees in case of goods and services and one thousand million rupees in case of works.
23.4 In case the date of opening of bid has been declared as public holiday or the procuring agency fail to open bid due to any EPADS v2.0 related issues, the submission and opening of bids shall be shifted to the next working day on the same time.
23.5 In case of Single Stage One Envelope Procedure, the Bidders names, the Bid prices, the total amount of each Bid and, the presence or absence of Bid Security, Bid Securing Declaration and such other details as the Procuring Agency may consider appropriate, will be announced by the Bid Evaluation Committee.
24.1 To assist in the examination, evaluation and comparison of Bids of the Bidders, the Procuring Agency may, ask any Bidder for a clarification of its Bid including breakdown of prices.
24.2 The request for clarification and the response shall be sought through EPADS v2.0 before three days prior to the deadline for submission of bids. No change in the prices or substance of the Bids shall be sought, offered, or permitted.
24.3 The alteration or modification in the BIDS which in any way affect the following parameters will be considered as a change in the substance of a Bids:
24.4 From the time of Bids opening to the time of Contract award if any Bidder wishes to contact the Procuring Agency on any matter related to the Bids it should do so through EPADS v2.0.
25.1 Prior to the detailed evaluation of Bids, the Procuring Agency will determine whether each Bid:
25.2 The Procuring Agency's determination of a Bid's responsiveness will be based on the contents of the Bid itself.
25.3 A substantially responsive Bid is one which conforms to all the terms, conditions, and specifications of the Bidding documents, without material deviation or reservation. A material deviation or reservation is one that: -
25.3 If a Bids is not substantially responsive, it will be rejected by the Procuring Agency and may not subsequently be evaluated for complete technical responsiveness.
26.1 The Procuring Agency shall examine the Bids to confirm that all terms and conditions specified in the GCC and the SCC have been accepted by the Bidder without any material deviation or reservation.
26.2 The Procuring Agency shall evaluate the technical aspects of the Bids submitted, to confirm that all requirements specified in Schedule of Requirements and Technical Specifications of the Bidding documents have been met without material deviation or reservation.
26.3 If after the examination of the terms and conditions and the technical evaluation, the Procuring Agency determines that the Bid is not substantially responsive in accordance with ITB 25.2, it shall reject the Bid.
27.1 Bids determined to be substantially responsive will be checked for any arithmetic errors. Errors will be corrected as follows: -
27.2 The amount stated in the Bid will, be adjusted by the Procuring Agency in accordance with the above procedure for the correction of errors and, with the concurrence of the Bidder, shall be considered as binding upon the Bidder. If the Bidder does not accept the corrected amount, its Bid will then be rejected, and the Bid Security may be forfeited or the Bids Securing Declaration may be executed.
28.1 To facilitate evaluation and comparison, the Procuring Agency will convert all Bids prices expressed in the amounts in various currencies in which the Bids prices are payable. For the purposes of comparison of bids quoted in different currencies, the price shall be converted into a single currency specified in the bidding documents. The rate of exchange shall be the selling rate prevailing on the date of opening of financial bids specified in the bidding documents, in accordance with weighted average customer exchange rates list issued by the State Bank of Pakistan on that day.
29.1 The Bids, quotations, or proposals shall be evaluated by the respective evaluation committees as per evaluation criteria described in the Bidding Documents in accordance with Rule 29 and 30 of the Public Procurement Rules, 2004.
1. Least Cost Based Selection (LCBS)
After meeting the requirements of eligibility, qualification and substantial responsiveness, the bid in compliance with all the mandatory (technical) specifications/requirements and/or requisite quality threshold (if any), and having lowest evaluated cost (or financial proposal) shall be considered Successful Bid.
2. Quality and Cost Based Selection (QCBS)
In such combination, there shall be some specific weightage of both the technical features and financial aspects of the proposal. The financial marks shall be awarded on the basis of inverse proportion calculations. The successful bid shall be declared, on the basis of combined evaluation.
3. Quality Based Selection (QBS)
Atter meeting the requirements of eligibility, qualification and substantial responsiveness the bid in compliance with all the mandatory (technical) specifications/requirements and attaining highest marks in the Technical Evaluation considering all other qualitative and/or quantitative parameters (or point rated criteria) for technical proposal(s) such as working methodology, implementation plan, resource allocation, additional functionalities, risk management approach, knowledge transfer techniques, post implementation methodology etc. shall be treated as highest ranked bid. Later on, the financial proposal of highest ranked bidder shall be opened, however, in case of failure to proceed further with such a bidder, the procuring agency may resort to second highest bidder and so on.
29.2 In case of tie of bids, the bidders shall be provided an opportunity to offer their best and final monetary offer through EPADS v2.0. However, in no case the rates shall be higher than the original financial bids.
30.1 The procuring agency shall evaluate and compare bids, allow for preference to domestic bidders, while competing with the international bidders in accordance with the policies of Federal Government.
The percentage of preference, to be accorded shall be clearly mentioned in the bidding documents under the bid evaluation criteria.
31.1 Selection technique will be adopted for determining the Successful Bid in accordance with the criteria referred in the BDS or prescribed in the separate section titled as Evaluation Criteria.
31.2 In case where the Procuring Agency adopts the Cost Based Evaluation Technique and, the Bid with the lowest evaluated price from amongst those which are eligible, compliant and substantially responsive shall be the Successful Bid.
31.3 The Procuring Agency may adopt the Quality & Cost Based Selection Technique due to the following two reasons:
1. Where the Procuring Agency knows about the main features, usage and output of the products; however not clear about the complete features, technical specifications and functionalities of the goods to be procured and requires the bidders to submit their proposals defining those features, specifications and functionalities; or
2. Where the Procuring Agency, in addition to the mandatory requirements and mandatory technical specifications, requires parameters specified in Evaluation Criteria to be evaluated while determining the quality of the goods.
31.4 In such cases, the Procuring Agency may allocate certain weightage to these factors as a part of Evaluation Criteria, and may determine the ranking of the bidders on the basis of combined evaluation in accordance with provisions of Rule 2(1)(h) of the Public Procurement Rules, 2004.
32.1Where the Bid price is considered to be abnormally low, the Procuring Agency shall perform price analysis either during determination of Successful Bids or as a part of the post-qualification process.
32.2 The Procuring Agency may reject an Abnormally low financial bids.
32.3 In order to identify the Abnormally Low Bids (ALB) following approaches can be considered to minimize the scope of subjectivity:
32.4 The Procuring Agency will determine to its satisfaction whether the Bidder that is selected as having submitted the successful bid is qualified to perform the contract satisfactorily.
32.5 The determination will take into account the Bidder’s financial, technical, and production capabilities. It will be based upon an examination of the documentary evidence of the Bidder’s qualifications submitted by the Bidder, as well as such other information as the Procuring Agency deems necessary and appropriate. Factors not included in these Bidding documents shall not be used in the evaluation of the Bidders’ qualifications.
32.6 Procuring Agency may seek “Certificate for Independent Price Determination” from the Bidder and the results of reference checks may be used in determining an award of contract.
Explanation: The Certificate shall be furnished by the Bidder. The Bidder shall certify that the price is determined keeping in view of all the essential aspects such as raw material, its processing, value addition, optimization of resources due to economy of scale, transportation, insurance and margin of profit etc.
32.7 An affirmative determination will be a prerequisite for award of the contract to the Bidder. A negative determination will result in rejection of the Bidder’s Bids, in which event the Procuring Agency will proceed to the next ranked Bidder to make a similar determination of that Bidder’s capabilities to perform satisfactorily.
33.1 The Procuring Agency will award the Contract to the Bidder whose Bids has been determined to be substantially responsive to the Bidding documents and who has been declared as Most Advantageous Bidder.
34.1 The procuring agency shall not engage in negotiations with respect to scope and price with the bidder except when the procuring agency conducts a procurement using direct or negotiated contracting or a request for proposals with evaluation based on quality alone.
34.2 The procuring agency may negotiate with the most advantageous bid with a view to streamline the work or task execution, at the time of contract finalization on methodology, work plan, staffing, finalizing payment arrangements, delivery arrangements, minor amendments to the special conditions of the contract.
35.1 The Procuring Agency reserves the right to reject all bids or proposals at any time prior to the issuance of the Letter of Award, without incurring any liability, in accordance with Rule 33 of the Public Procurement Rules, 2004.
36.1 The Procuring Agency reserves the right at the time of contract award to increase or decrease the quantity of Goods originally specified in these Bidding documents provided this does not exceed by 15%, without any change in unit price or other terms and conditions of the Bids and Bidding documents.
37.1 Prior to the award of contract, the procuring agency shall announce and publish the result of bid evaluation on EPADS v2.0 in accordance with Rule 35 of the Public Procurement Rules, 2004.
37.2 The Bidder whose Bids has been accepted will be notified of the award by the Procuring Agency prior to expiration of the Bids/Bid Validity period. The Letter of Award will state the sum that the Procuring Agency will pay the successful Bidder in consideration for the delivery of Goods as prescribed by the Contract (hereinafter and in the Contract called the "Contract Price).
37.3 The Letter of award will constitute the formation of the Contract, subject to the Bidder furnishing the Performance Guarantee and signing of the contract.
38.1 Promptly after issuance of Letter of award, Procuring Agency shall send the successful Bidder the draft Contract, incorporating all terms and conditions as agreed by the parties to the contract.
38.2 Immediately after the Redressal of grievance by the GRC (if any), mandatory standstill period in accordance with Rule 35 of the Public Procurement Rules, 2004 and after fulfillment of all condition’s precedent of the Contract Form, the successful Bidder and the Procuring Agency shall sign the Contract.
39.1 Procuring Agencies (including beneficiaries of Government funded projects and procurement) as well as Bidders/Contractors under Government financed contracts, observe the highest standard of ethics during the procurement and execution of such contracts, and will avoid to engage in any corrupt and fraudulent practices.
40.1 The Grievance Redressal Committee shall address the grievance, if any submitted by any party, including the bidder, in accordance with Rule 48 of the Public Procurement Rules, 2004 to be read with Redressal of Grievances Regulations, 2021.
40.2 In case if any party or the bidder is not satisfied with the decision of the GRC or if it fails to decide within ten days, the bidder or the party may file an appeal before the Appellate Committee of the Authority in accordance with Rule 48 of the Public Procurement Rules, 2004 to be read with Redressal of Grievances Regulations, 2021.
41.1 The Procuring Agency shall initiate blacklisting proceedings against any bidder, supplier, or contractor in accordance with the Mechanism for Blacklisting Regulations, 2024, read with Rule 19 of the Public Procurement Rules, 2004.
41.2 The blacklisted/debarred bidder may file the review petition before the Authority in accordance with Rule 19 of the Public Procurement Rules, 2004 to be read with Procedure of filing and disposal of Review Petitions Regulations, 2021.
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 1
ITB Number 1.1
Name of Procuring Agency: Ministry of Foreign Affairs (Ministry of Foreign Affairs (MOFA))
The subject of procurement is: Subscription of endpoint security (XDR) &clientless VPN Licenses
Expected commencement date: Monday, August 10, 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: P54539
BDS Clause Number 3
ITB Clause Number 3.1
JV/Consortium or Association Allowed: No
Number of JV/Consortium Members: Nil
see section of eligibility criteria.
BDS Clause Number 4
ITB Number 8.1
The Bidders may seek clarifications through EPADS v2.0 : Clarification Date: Monday, July 20, 2026
BDS Clause Number 5
ITB Number 10.1
The Language of all correspondences and documents related to the Bids shall be in: English
List of documents required along with the bid:
BDS Clause Number 6
ITB Number 11.1
Items/Lots and threre related documents:
See section items and Lots
BDS Clause Number 7
ITB Number 12.1
Items / Lots Specifications:
see section of items specifications.
BDS Clause Number 8
ITB Number 15.6
The price shall be Fixed.
BDS Clause Number 9
ITB Number 16.1
Currency of the Bids shall be : PKR
BDS Clause Number 10
ITB Number 17.1
The Bids/Bid Validity period shall be: 90 Days
BDS Clause Number 11
ITB Number 18.1
The amount of Bid Security shall be as defined in Bid Security Section for items and lots given in BDS 6
The Bid Security shall be in the form of: Pay Order, Call at Deposit, Bank Guarantee
BDS Clause Number 12
ITB Number 20.1
Bid shall be submitted online on EPADS v2.0 whereas hard copy of the bid security should be submitted to the following;
Constitution Avenue, Sector G-5., Islamabad Capital Territory before bid submission deadline.
Bids that are not submitted on EPADS v2.0 shall be disqualified.
The deadline for Bids submission is: Monday, July 27, 2026 12:00 PM
BDS Clause Number 13
ITB Number 23.1
The Bids opening shall take place on EPADS v2.0.
Day : Monday
Date: Monday, July 27, 2026
Time : 12:30 PM
BDS Clause Number 14
ITB Number 31.1
Selection technique adopted will be: Least Cost Based Selection (LCBS)
see Evaluation Criteria
BDS Clause Number 15
ITB Number 41.1
Grievence against this procurement shall be submitted online on EPADS v2.0.
Arbitrator shall be appointed by mutual consent of the both parties.
| Bidder's Type | Required Registration |
|---|---|
|
Individual / Individual Consultant Sole Proprietorship Company (Private Limited) Company (Holding Company) Company (Limited by Guarantee) State Owned Enterprise (Private Limited) State Owned Enterprise (Public Limited) |
NADRA CITIZENSHIP (CNIC/NICOP) FBR (NTN) FBR (GSTN) |
Eligibile bidder(s) with substantially responsive bid(s) offering Least Cost Based Selection (LCBS) shall be consider for the award of contract(s).
Least Cost Based Selection (LCBS)
| Technical Marks | 100 | |
|---|---|---|
| Passing Marks | 65 | |
| Technical Evaluation Criteria | ||
| Manufacturer Authorization letter. Please attach a valid OEM Authorization letter (Relevant attach a valid participation letter from the principal) (Qualitative)(Doc Required) | 5 | |
| Relevant Projects completed in last 3 years related to End Point Protection solution with documentary proof be provided i.e. completion certificates issued by the clients etc.) (Qualitative)(Doc Required) 10 or more projects (10) 7 to 9 projects (7) 3 to 6 Projects (3) | 10 | |
| Pakistan Security Standards (PSS) compliance (Qualitative)(Doc Required) | 10 | |
| The bidder must provide a certificate of conformance that there are no backdoors, eavesdropping, or remote access mechanisms in their offered product/solution. NOTE: Any identified avenues for unauthorized access or data leakage may result in contract cancellation and blacklisting of the firm. (Relevant Certificate of conformance on stamp paper required) (Qualitative)(Doc Required) | 5 | |
| Firms must attach verifiable certificates of good/satisfactory performance from clients in projects of end point protection. (Qualitative)(Doc Required) 5 verifiable certificates of good/satisfactory performance from clients in projects (5) 4 verifiable certificates of good/satisfactory performance from clients in projects4 (4) 3 verifiable certificates of good/satisfactory performance from clients in projects (3) 2 verifiable certificates of good/satisfactory performance from clients in projects (2) 1 verifiable certificates of good/satisfactory performance from clients in projects (1) | 5 | |
| Proposal provides 24x7x365 helpdesk/TAC/onsite support as per compliance sheet (Affidavit on stamp paper required) (Qualitative)(Doc Required) | 5 | |
| Technical Engineers with end point protection Certified (Qualitative)(Doc Required) 5 x end point protection Certified Engineer (10) 3 x end point protection Certified Engineer (5) | 10 | |
| (Attach team educational documents and certifications) (Qualitative)(Doc Required) | 5 | |
| Technical Staff (IT/Cyber Security) workforce in Islamabad. Technical Team members details/ Hierarchical Structure of company along with degrees/professional certificates/diplomas etc (Qualitative)(Doc Required) 10 or > employees (5) 6 to 9 employees (3) 4 to 5 employees (1) | 5 | |
| Details with proof of number of years of Experience (Qualitative)(Doc Required) 7 to 10 years (5) 3 to 6 years (2) | 5 | |
| Local presence is must for vendor. Attach the Islamabad/Rawalpindi office details and phone number (Qualitative)(Doc Required) | 5 | |
| Firm must be on the Active tax payers list of Federal board of Revenue. (Qualitative)(Doc Required) | 5 | |
| Income Tax and Sales Tax Returns of F.Y. 2023-24 and 2024-25 (Qualitative)(Doc Required) Attached both F.Y returns (5) One return attached (2) | 5 | |
| Relevant ISO Certification of the company (Qualitative)(Doc Required) | 5 | |
| Financial Strength of the Company provide Financial statements/ Annual Turnover of FY 2024-25 (Qualitative)(Doc Required) 30 Million or more (5) 20 to 29 Million (3) 10 to 19 Million (2) | 5 | |
| Partner with OEM Please attach a valid OEM partnership letter/certificate. (Relevant attach a valid partnership letter) (Qualitative)(Doc Required) | 10 | |
Items Without Lots :
| Item | UNSPSC | Delivery Schedule | Quantity | Bid Security | Manufacturer / Dealer Authorization |
|---|---|---|---|---|---|
| Subscription of Endpoint Security | Network security and virtual private network VPN equipment software |
Address: Constitution Avenue, Sector G-5., Islamabad Capital Territory
Schedule: 27 Days
Quantity: 551/Qty
|
551/Qty | 2050000 PKR | Manufacturer Authorization form |
No
Items Without Lots :
Item: Subscription of Endpoint Security
UNSPSC: Network security and virtual private network VPN equipment software
Specifications / Requirements:
| Required features of XDR Solution to be deployed | ||
|---|---|---|
| Must have features | Compliance | |
| 1 | The XDR solution must natively embed a full-featured enterprise-grade automation and response engine capable of executing complex multi-vendor remediation playbooks directly within the core console, strictly avoiding platforms whose automation is limited to endpoint-centric workflows or requires a separately licensed orchestration module. | Â |
| 2 | The XDR solution must provide a visual drag-and-drop playbook builder natively within the console, strictly avoiding architectures that require code-first, terminal-based, or API-only playbook authoring. | Â |
| 3 | The XDR solution must provide more than one hundred out-of-the-box cross-domain incident response playbooks natively within the console, strictly avoiding architectures that require a separately licensed automation product. | Â |
| 4 | The XDR solution must offer a single unified on-premises gateway appliance capable of simultaneously acting as a log proxy, content cache, and distribution point for all XDR components, strictly avoiding architectures that require multiple disjointed collector tools for different data sources. | Â |
| 5 | The XDR solution must provide a native Model Context Protocol (MCP) server allowing customers to author custom MCP tools and enabling AI agents to consume third-party tools and data via a standardized open protocol, strictly avoiding closed AI ecosystems that limit agent extensibility to vendor-published capabilities. | Â |
| 6 | The XDR solution must provide a specialist agentic AI platform with distinct out-of-the-box agents dedicated to threat intelligence, email investigation, endpoint investigation, network security, IT operations, and automation engineering, strictly avoiding architectures that provide only a single generic generative AI chat assistant. | Â |
| 7 | The XDR solution must provide a centralized agent management hub allowing administrators to build custom AI agents via a no-code natural-language builder and assign them scoped actions (playbooks, scripts, AI prompts, MCP-integrated tools) with configurable human-in-the-loop approval enforcement, strictly avoiding platforms whose agent framework is vendor-controlled with no customer extensibility. | Â |
| 8 | The XDR solution must provide native single-click bulk UI actions (file retrieval, malware scan, endpoint isolation, script execution, memory collection) across thousands of selected endpoints or servers simultaneously from the management console, strictly avoiding architectures that require scripting API loops or command-line iteration to execute bulk response. | Â |
| 9 | The XDR solution must natively support bulk agent uninstallation and bulk agent version upgrades directly from the management UI, strictly avoiding architectures that require third-party endpoint-management tools or external scripts for these operations. | Â |
| 10 | The XDR solution must provide dedicated memory-corruption and exploit-mitigation protection modules natively across Linux, Windows, and macOS endpoints, strictly avoiding architectures that rely solely on machine learning or behavioral heuristics for exploit prevention. | Â |
| 11 | The XDR solution must utilize an agent architecture that natively supports peer-to-peer distribution of content updates and agent upgrades, strictly avoiding architectures that require a dedicated local update server or proxy infrastructure to minimize WAN consumption. | Â |
| 12 | The XDR solution must allow administrators to explicitly customize, weight, and override the automated incident severity scoring based on custom environmental variables (asset criticality, role, business context), strictly avoiding scoring architectures that are opaque or non-configurable by the customer. | Â |
| 13 | The XDR solution must manage all XDR components (endpoint, identity, network detection and response) entirely within a single unified web console, strictly avoiding architectures that force analysts to pivot between an XDR console and a separate SIEM, log management, or next-gen SIEM interface. | Â |
| 14 | The XDR solution must provide an on-premises execution engine (supporting Docker and Podman runtimes) that runs automation integrations, scripts, and actions against internal network resources, strictly avoiding architectures that require inbound firewall port opening or separate orchestration appliances. | Â |
| 15 | The XDR solution must include a built-in commercial malware sandbox that natively detonates files captured from both endpoint agents and integrated network firewalls, strictly avoiding architectures that require a separately purchased sandbox product or that rely exclusively on endpoint-side dynamic analysis. | Â |
| 16 | The XDR solution must support endpoint agent deployment on Windows, macOS, Linux, and ChromeOS platforms with a unified management policy framework. | Â |
| 17 | The XDR solution must provide kernel-mode and user-mode protection on Linux endpoints using both eBPF and kernel module implementations to ensure compatibility across distributions. | Â |
| 18 | The XDR solution must support agent operation on VDI environments including non-persistent desktop infrastructure. | Â |
| 19 | The XDR solution must support agent installation via MSI, PKG, RPM, and DEB packages with silent deployment parameters. | Â |
| 20 | The XDR solution must support SSO authentication via SAML 2.0 with identity providers including Okta and Azure AD. | Â |
| 21 | The XDR solution must provide granular role-based access control with scope-based access control restricting users to specific asset groups, data sources, or tenants. | Â |
| 22 | The XDR solution must support user group management with role inheritance and group-based permission assignment. | Â |
| 23 | The XDR solution must support native multi-tenant deployment covering both MSSP and enterprise parent/child tenant models. | Â |
| 24 | The XDR solution must support dynamic license allocation across child tenants with central licensing management. | Â |
| 25 | The XDR solution must support parent-child tenant content and configuration distribution including playbook, detection rule, and dashboard sharing. | Â |
| 26 | The XDR solution must provide Causality Chain analysis linking process, network, file, and registry activity across time into a single graph. | Â |
| 27 | The XDR solution must provide cross-host attack storyline visualization spanning endpoint, network, SaaS, and identity surfaces. | Â |
| 28 | The XDR solution must provide a dedicated SaaS Causality view for investigations originating in SaaS audit logs. | Â |
| 29 | The XDR solution must provide a dedicated Network Causality view for investigations originating in network telemetry. | Â |
| 30 | The XDR solution must support IOC rules for file hash, IP address, domain, and URL indicators with configurable severity and action. | Â |
| 31 | The XDR solution must support custom behavioral rules with customizable logic across process, file, network, registry, and authentication telemetry. | Â |
| 32 | The XDR solution must support correlation rules with configurable suppression windows and field-replacement syntax. | Â |
| 33 | The XDR solution must support scheduled correlation rules with defined time windows and server-side error troubleshooting. | Â |
| 34 | The XDR solution must support rule testing and preview prior to production deployment. | Â |
| 35 | The XDR solution must support rule import and export for content lifecycle management across environments. | Â |
| 36 | The XDR solution must provide MITRE ATT&CK framework coverage mapping with a dedicated tactics and techniques coverage dashboard. | Â |
| 37 | The XDR solution must support custom dashboards with drag-and-drop widgets, filters, and drilldowns. | Â |
| 38 | The XDR solution must support scheduled report generation in PDF and HTML formats with email distribution. | Â |
| 39 | The XDR solution must provide pre-built report templates for executive, operational, and compliance audiences. | Â |
| 40 | The XDR solution must provide AI-generated case summaries consolidating telemetry, impact, and context into a high-level report for triage and stakeholder communication. | Â |
| 41 | The XDR solution must support automatic case grouping based on shared indicators, behavioral similarity, and temporal proximity. | Â |
| 42 | The XDR solution must support case starring, watchlists, and featured field designation for analyst workflow prioritization. | Â |
| 43 | The XDR solution must support case resolution reasons, collaborative notes, and comment threads per case. | Â |
| 44 | The XDR solution must provide a collaborative virtual war room interface for real-time investigation with shared context. | Â |
| 45 | The XDR solution must provide a Work Plan interface for structured incident task management and progress tracking. | Â |
| 46 | The XDR solution must support issue exclusions, profile exceptions, and allow lists with scope-based applicability. | Â |
| 47 | The XDR solution must provide endpoint isolation (network quarantine) with configurable exclusions for management traffic. | Â |
| 48 | The XDR solution must support temporary pause and resume of endpoint protection with audit logging. | Â |
| 49 | The XDR solution must provide automatic and manual file quarantine with release and restore capability. | Â |
| 50 | The XDR solution must support file hash exception lists with bulk import from CSV. | Â |
| 51 | The XDR solution must support automatic file submission to an integrated commercial sandbox for unknown executable, macro, DLL, and script samples. | Â |
| 52 | The XDR solution must support third-party hash reputation lookup against external intelligence sources before executing destructive response actions. | Â |
| 53 | The XDR solution must support external dynamic lists (EDLs) for IP addresses and domains associated with detected threats. | Â |
| 54 | The XDR solution must provide host firewall management with centrally-managed rules per endpoint group. | Â |
| 55 | The XDR solution must provide device control for USB, CD-ROM, and external storage with granular per-class policies. | Â |
| 56 | The XDR solution must provide disk encryption visibility for BitLocker and FileVault, reporting encryption status and recovery-key presence. | Â |
| 57 | The XDR solution must provide a script prevention engine capable of inspecting PowerShell, VBScript, JavaScript, and macro execution. | Â |
| 58 | The XDR solution must provide anti-ransomware protection using behavioral detection and decoy file techniques. | Â |
| 59 | The XDR solution must provide agent tamper protection including an administrator-configurable uninstall password. | Â |
| 60 | The XDR solution must support outbound log and notification forwarding to syslog, Amazon S3, Amazon SQS, webhooks, Slack, email, and third-party SIEMs. | Â |
| 61 | The XDR solution must provide API key management with granular scope, expiration, and rotation controls. | Â |
| 62 | The XDR solution must maintain management audit logs for all administrative actions including rule edits, policy changes, and user access events. | Â |
| 63 | The XDR solution must allow administrators to define issue thresholds per case grouping policy to control case creation volume. | Â |
| 64 | The XDR solution must provide analytics sensor configuration per tenant, allowing customers to enable or disable individual analytics sensors based on licensing and data sources. | Â |
| 65 | The XDR solution must support a natural-language assistant able to generate and execute query language statements on the analyst's behalf. | Â |
| 66 | The XDR solution must provide AI-prompt role-based access control governing which users may author, edit, or execute prompts. | Â |
| 67 | The XDR solution must support a dedicated dashboard showing AI agent plans, user prompts, and associated cases. | Â |
| 68 | The XDR solution must include an autonomous Agentic AI "brain" that plans, reasons, and investigates complex threats using AI agents with access to full case context, capable of executing commands, playbooks, and scripts via natural language prompts. | Â |
| 69 | The XDR solution must provide an ecosystem-based Agentic architecture consisting of Agents (virtual personas with RBAC-bound roles), Actions (wrappers for playbooks, scripts, commands, AI prompts), Plans (parallel or sequential action sequences), Conversations (multi-turn contextual interactions), and Requests (user-goal triggers), strictly avoiding single-layer chatbot architectures. | Â |
| 70 | The XDR solution must include a centralized agent management hub providing unified management of agents and actions, with the ability to enable, disable, build, edit, duplicate, and delete agents and actions from a single interface. | Â |
| 71 | The XDR solution must include more than fifty out-of-the-box system actions and pre-built system agents covering case investigation, threat intel, email investigation, endpoint investigation, network security, IT operations, automation engineering, exposure management, and help-center documentation retrieval. | Â |
| 72 | The XDR solution must support customer-built custom AI agents with configurable agent name, description, color, specific instructions (role, instructions, output structure), public/private visibility, and up to four configurable conversation starters. | Â |
| 73 | The XDR solution must support registration of customer-authored scripts, integration commands, and AI prompts as custom actions, with configurable name, goal description, few-shot examples, per-action input/output selection, and per-action default values. | Â |
| 74 | The XDR solution must enforce automatic inheritance of the invoking user's RBAC and SBAC permissions onto all agent action executions, strictly avoiding architectures where agents operate with privileges exceeding the user's own permissions. | Â |
| 75 | The XDR solution must support explicit marking of any action as "sensitive" to require mandatory human-in-the-loop approval prior to execution, with the ability for administrators to toggle sensitivity on system actions per organizational policy. | Â |
| 76 | The XDR solution must provide a full audit dataset logging every agent plan, every executed action, the invoking user, the agent used, and the action outcome, for traceability and compliance. | Â |
| 77 | The XDR solution must provide full agent-plan transparency with the ability to expand and view the planned steps, executed actions, JSON artifacts produced, and the interpretation of the original user prompt. | Â |
| 78 | The XDR solution must provide a native Model Context Protocol (MCP) integration framework supporting connection to third-party MCP servers via stream able HTTP with both OAuth-based and authless authentication. | Â |
| 79 | The XDR solution must automatically discover tools exposed by connected third-party MCP servers on an hourly cadence (and on integration-instance save) and automatically register them as AI-consumable actions of type "MCP Tool." | Â |
| 80 | The XDR solution must include pre-built MCP content packs plus a Generic MCP connector for arbitrary third-party MCP servers, with multiple integration instances per MCP content pack. | Â |
| 81 | The XDR solution must support granular integration-permission controls restricting which roles may execute MCP-tool actions, with default "sensitive" marking on all auto-registered MCP tools until the administrator explicitly relaxes this. | Â |
| 82 | The XDR solution must include a downloadable platform-side MCP server (Docker or Python virtual environment deployment) that exposes the XDR platform's capabilities (cases, issues, assets, endpoints, compliance results, native query language statements) to any standards-compliant external MCP client via natural language. | Â |
| 83 | The XDR solution must allow customers to author their own MCP server tools using Open API specifications or Python modules, automatically collected by the MCP server at runtime for use against the platform's REST APIs. | Â |
| 84 | The XDR solution must include a dedicated Case Investigation agent embedded directly within the case card, providing dynamic log-data summarization, executive and technical overviews, focused contextual inquiries (issue deep-dives, asset relationships, artifact investigation), and an "Ask AI" entity-specific prompt pivot next to IP addresses, file hashes, and other entities. | Â |
| 85 | The XDR solution must include a dedicated Agentic Assistant dashboard showing pre-configured triggers, user-prompt activity, top automation rules, the five most-engaged agents over a rolling seven-day window, and an "Other Agents" drilldown to the agent management hub. | Â |
| 86 | The XDR solution must include a built-in Help Center Agent providing natural-language access to official product documentation, answering configuration and operational questions by retrieving concise, relevant information from the vendor's documentation site. | Â |
| 87 | The XDR solution must provide multi-chat session management allowing the analyst to run multiple concurrent Agentic conversations, switch between agents per chat, retain chat history organized by time period (today, yesterday, last seven days, older), and rename or delete past chats. | Â |
| 88 | The XDR solution must include intelligent prompt-intent clarification and automatic blocking of requests that appear exploitative or harmful to the platform or the organization's environment. | Â |
| 89 | The XDR solution must include a full native SOAR engine capable of creating, customizing, and running unlimited playbooks directly within the XDR console, with no separately licensed SOAR product required. | Â |
| 90 | The XDR solution must include a Playbook Catalog with searchable, preview-capable, one-click "Adopt" out-of-the-box playbooks drawn from the unified content marketplace, plus an organizational playbook repository view tracking adoption, enablement, automation-rule usage, and sub-playbook usage. | Â |
| 91 | The XDR solution must include a Task Library inside the playbook editor supporting pre-packaged rapid actions, Commands & Scripts, Sub-Playbooks, AI Prompt tasks, Manual Tasks (standard, conditional, data collection), Section Headers, and Blank Tasks. | Â |
| 92 | The XDR solution must support five distinct playbook task types, Standard (automated or manual), Conditional (decision-tree branching), Data Collection (user-survey input with multi-user response recording), AI Prompt (LLM invocation), and Section Header (collapsible grouping),with distinct visual icons for each type and origin. | Â |
| 93 | The XDR solution must support AI Prompt tasks embedded as first-class playbook tasks with configurable prompt text, variable inputs referenced via ${input} syntax, configurable temperature (0 to 2), configurable max-output tokens (default 2,500), and configurable indicator-extraction mode (none, inline, out-of-band). | Â |
| 94 | The XDR solution must include a Local AI Prompt mechanism that freezes a prompt's behavior inside a specific playbook against future library updates, preserving tested behavior even as the central Prompts Library evolves. | Â |
| 95 | The XDR solution must include a built-in Prompt Helper offering prompt-engineering guidance (clarity, specificity, role assignment, audience framing, output-format specification, few-shot prompting), plus a one-click "Optimize" function that refines prompt text against predefined system guidelines with an undo option. | Â |
| 96 | The XDR solution must include more than one hundred pre-built system AI prompt tasks covering use cases such as vulnerability-report summarization, phishing-email analysis, malware-behavior narratives, MITRE ATT&CK mapping, and IOC extraction. | Â |
| 97 | The XDR solution must support native sub-playbook invocation with configurable input/output scope (shared globally or private to the sub-playbook), and configurable sub-playbook loops for repetitive processing of arrays of entities. | Â |
| 98 | The XDR solution must include a native filter-and-transformer framework enabling analysts to extract, filter, format, and reshape context data within playbook tasks through a no-code UI, with the ability to author custom filter and transformer operators via tagged scripts. | Â |
| 99 | The XDR solution must support per-task error-handling semantics, Stop (halt on error), Continue (ignore error), and Continue-on-Error-Path (branch to an error-handling path),with configurable retry count and retry interval (default 30 seconds, maximum 800 seconds) per task. | Â |
| 100 | The XDR solution must include a full interactive playbook debugger supporting breakpoints, conditional breakpoints, task skipping, live input/output overrides (plain text, arrays, JSON), real-time context-data inspection, indicator-extraction inspection, and use of mock issues or existing issues as test data without modifying production issue state. | Â |
| 101 | The XDR solution must include native automation-rule authoring with a WHEN/IF/THEN construct, where WHEN is the trigger type (issue creation, case, audit log), IF is an arbitrary filter over issue fields, and THEN is an automated action chain invoking a rapid action, a playbook, or an agent, evaluated in strict priority order with only the first matching rule executing. | Â |
| 102 | The XDR solution must support automation rules that automatically trigger specialist AI agents with pre-written prompts on issue creation, with a built-in "Test Prompt" capability that runs a full plan-execution test against either a mock issue or a selected production issue before the rule is committed. | Â |
| 103 | The XDR solution must include an AI-powered Automation Engineer agent providing a conversational natural-language interface for script development, supporting initial full-script generation from a simple prompt, existing-script modification, iterative bug fixing, deprecated-API detection and replacement, logic simplification, script explanation, input validation, error-handling augmentation, and SDK/command syntax guidance. | Â |
| 104 | The XDR solution must support customer-deployed on-premises execution engines (Docker and Podman runtimes) that run integrations and scripts against internal-network resources, with native support for web proxy configuration, custom CA certificates, load-balancing groups across multiple engines, and per-script Docker image selection against customer-operated private image registries. | Â |
| 105 | The XDR solution must provide a collaborative incident workspace interface supporting ad-hoc execution of integration commands and scripts via a command-line interface during live investigations, plus native context-data management (issue, case, search), List management for cross-playbook persistent state, Data Collection tasks for multi-user surveys, and Communication tasks with email templating and reply handling all without requiring pivoting to an external SOAR console. | Â |
| 106 | The proposed XDR solution must be compatible with the existing IT& Network equipment. | Â |
| Required features of Clientless VPN Solution to be deployed | ||
| 1 | The proposed License must offer a remote user VPN agent for Windows, MAC, Linux, Chrome, iOS, and Android devices and support at least 1000 VPN Users | Â |
| 2 | The proposed License must support portal based and clientless SSL VPN | Â |
| 3 | The proposed License must support MFA | Â |
| 4 | The proposed License must offer a host information check feature by collecting & reporting device information & attributes. | Â |
| Host Information Profiling attributes based on Managed/Unmanaged certificates status, OS type, Client version, Host name, Host ID, Serial number, Mobile model, Phone number, Root/Jailbroken status, Passcode presence, Installed Applications, Patch presence & status, Firewall agent presence & status, Antimalware agent presence & status, Disk backup agent presence & status, Disk encryption agent presence & status, DLP agent presence & status, process list presence & status, registry key presence & status and Plist presence & status | ||
| 5 | The proposed License must support enforcing security policies based on device/host information profiles | Â |
| 6 | The proposed License must support the integration with Third Party MDM solutions like Air Watch or Mobile Iron | Â |
| 7 | The proposed License must support split tunneling based on IP addresses, domains, applications and Split DNS | Â |
| 8 | The proposed License must support VPN authentication override using cookies | Â |
| 9 | The proposed License must support the exclusion of video traffic from main remote user VPN tunnel | Â |
| Â | The proposed License must support trusted root certificates push to remote VPN user devices to help enable features like SSL offload | Â |
| 10 | The proposed License must support VPN gateway selection criteria based on source user-id, region, OS and IP address | Â |
| 11 | The proposed License must support Identification of managed devices using the endpoint serial number on gateways | Â |
| 12 | The proposed License must support Host information Profiles Check for allowing Hosts to access specific Apps and services after passing the Compliance check | Â |
| 13 | The proposed License must support Mobile app for endpoints running Chrome OS, iOS, Android, IoT, Linux and Windows 10 UWP | Â |
| 14 | The proposed License must support Split tunneling based on destination domain, client process, and video streaming application | Â |
| 15 | The proposed License must support adding a compromised device to the quarantine list | Â |
| 16 | The proposed License must be compatible with existing firewall and IT architecture | Â |
For Individual Items
| # | Item 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] |
1. Definitions
2. Application and Interpretation
2.1 These General Conditions shall apply to the extent that they are not superseded by provisions of other parts of the Contract.
2.2 In interpreting these Conditions of Contract headings and marginal notes are used for convenience only and shall not affect their interpretations unless specifically stated; references to singular include the plural and vice versa; and masculine include the feminine. Words have their ordinary meaning under the language of the Contract unless specifically defined.
3. Applicable Law
3.1 The contract shall be governed and interpreted in accordance with the laws of Pakistan, unless otherwise specified in SCC.
4. Governing Language
4.1 The Contract as well as all correspondence and documents relating to the Contract exchanged between the Bidder and the Procuring Agency, shall be written in the English language unless otherwise stated in the SCC. Supporting documents and printed literature that are part of the Contract may be in another language provided these are accompanied by an accurate translation of the relevant passages in English, in which case, for purposes of interpretation of the Contract, this translation shall govern.
5. Notices
5.1 Any notice, request, or consent made pursuant to this Contract shall be in writing and shall be deemed to have been made when delivered in person to an authorized representative of the Party to whom the communication is addressed, or when sent by registered mail, telex, telegram, or facsimile to such Party at the address specified in the SCC.
6. Delivery/Location
6.1 The Goods shall be delivered to such locations as the Procuring Agency may approve and as specified in SCC.
7. Authorized Representatives / Authority of Member in charge
7.1 Any action required or permitted to be taken, and any document required or permitted to be executed, under this Contract by the Procuring Agency or the Bidder may be taken or executed by the officials specified in the SCC.
8. Effectiveness of Contract
8.1 This Contract shall come into effect on the date the Contract is signed by both parties and such other later date as may be stated in the SCC.
9. Commencement of Services
9.1 The Bidder shall confirm availability of Key Experts and begin carrying out the Services not later than the number of days after the Effective Date specified in the SCC.
10. Program
10.1 Before commencement of the Services, the Bidder shall submit to the Procuring Agency for approval a Program showing the general methods, arrangements, order and timing for all activities. The Services shall be carried out in accordance with the approved Program as updated.
11. Starting Date/Expiration Date
11.1 The Bidder shall start carrying out the Services Five (05) days after the date the Contract becomes effective, or at such other date as may be specified in the SCC.
11.2 Unless terminated earlier pursuant to Clause GCC 15 hereof, this Contract shall expire at the end of such time period after the Effective Date as specified in the SCC.
12. Entire Agreement
12.1 This Contract contains all covenants, stipulations and provisions agreed by the Parties. No agent or representative of either Party has authority to make, and the Parties shall not be bound by or be liable for, any statement, representation, promise or agreement not set forth herein.
13. Modification
13.1 Any modification or variation of the terms and conditions of this Contract, including any modification or variation of the scope of the Services, may only be made by written agreement between the Parties. However, each Party shall give due consideration to any Bids for modification or variation made by the other Party.
13.2 In cases of any modifications or variations, the prior written consent of the Procuring Agency is required.
14. Force Majeure
14.1 Definition
For the purposes of this Contract, “Force Majeure” means an event which is beyond the reasonable control of a Party and which makes a Party’s performance of its obligations under the Contract impossible or so impractical as to be considered impossible under the circumstances.
14.2 No Breach of Contract
The failure of a Party to fulfill any of its obligations under the contract shall not be considered to be a breach of, or default under, this Contract in so far as such inability arises from an event of Force Majeure, provided that the Party affected by such an event (a) has taken all reasonable precautions, due care and reasonable alternative measures in order to carry out the terms and conditions of this Contract, and (b) has informed the other Party as soon as possible about the occurrence of such an event.
14.3 Extension of Time
Any period within which a Party shall, pursuant to this Contract, complete any action or task, shall be extended for a period equal to the time during which such Party was unable to perform such action as a result of Force Majeure.
14.4 Payments
During the period of their inability to perform the Services as a result of an event of Force Majeure, the Bidder shall be entitled to continue to be paid under the terms of this Contract, as well as to be reimbursed for additional costs reasonably and necessarily incurred by them during such period for the purposes of the Services and in reactivating the Service after the end of such period.
15. Termination
15.1 By the Procuring Agency
The Procuring Agency may terminate this Contract in case of the occurrence of any of the events specified in paragraphs (a) through (e) of this Clause. In such an occurrence the Procuring Agency shall give at least thirty (30) calendar days’ written notice of termination to the Bidder in case of the events referred to in (a) through (d); at least sixty (60) calendar days’ written notice in case of the event referred to in (e);
15.2 By the Bidder
The Bidder may terminate this Contract, by not less than thirty (30) calendar days’ written notice to the Procuring Agency, in case of the occurrence of any of the events specified in paragraphs (a) through (d) of this Clause.
16. General
16.1 Standard of Performance
16.2 Law Applicable to Goods
The Bidder shall deliver the goods in accordance with the Contract and in accordance with the Law of Pakistan and shall take all practicable steps to ensure that any of its Experts and Sub-Bidders, comply with the Applicable Law.
17. Conflict of Interests
17.1 Bidder Not to Benefit from Commissions and Discounts.
The remuneration of the Bidder shall constitute the Bidder’s sole remuneration in connection with this Contract or the Services, and the Bidder shall not accept for their own benefit any trade commission, discount, or similar payment in connection with activities pursuant to this Contract or to the Services or in the discharge of their obligations under the Contract, and the Bidder shall use their best efforts to ensure that the Personnel, any Subcontractors, and agents of either of them similarly shall not receive any such additional remuneration.
17.2 Bidder and Affiliates Not to be Otherwise Interested in Project
The Bidder agree that, during the term of this Contract and after its termination, the Bidder and its affiliates, as well as any Subcontractor and any of its affiliates, shall be disqualified from providing Goods for any project resulting from or closely related to the Services.
17.3 Prohibition of Conflicting Activities
Neither the Bidder nor its Subcontractors nor the Personnel shall engage, either directly or indirectly, in any of the following activities:
18. Confidentiality
18.1 Except with the prior written consent of the Procuring Agency, the Bidder and the Experts shall not at any time communicate to any person or entity any confidential information acquired in the course of the contract.
19. Insurance to be Taken Out by the Bidder
19.1 The Bidder(a) shall take out and maintain, and shall cause any Subcontractors to take out and maintain, at its (or the Subcontractors’, as the case may be) own cost but on terms and conditions approved by the Procuring Agency, insurance against the risks, loss or damage, and for the coverage, as shall be specified in the SCC; and (b) at the Procuring Agency’s request, shall provide evidence to the Procuring Agency showing that such insurance has been taken out and maintained and that the current premiums have been paid.
20. Bidder’s Actions Requiring Procuring Agency’s Prior Approval
20.1 The Bidder shall obtain the Procuring Agency’s prior approval in writing before taking any of the following actions:
(a) appointing such members of the Personnel not provided by the Bidder;
(b) changing the Program of activities; and
(c) any other action that may be specified in the SCC.
21. Reporting Obligations
21.1 The Bidder shall submit to the Procuring Agency the reports and documents in the numbers, and within the periods as prescribed by the Procuring Agency.
22. Liquidated Damages
22.1 If the Supplier fails to deliver any or all of the Goods or to perform the Services within the period(s) specified in the Contract, the Procuring Agency shall, without prejudice to its other remedies under the Contract, deduct from the Contract Price, as liquidated damages, a sum equivalent to the percentage specified in SCC of the delivered price of the delayed Goods or unperformed Services for each week or part thereof of delay until actual delivery or performance, up to a maximum deduction of the performance security (or guarantee) specified in SCC. Once the said maximum is reached, the Procuring Agency may consider termination of the Contract pursuant to GCC Clause 15.
22.2 Correction for Over-payment
If the Intended Completion Date is extended after liquidated damages have been paid, the Procuring Agency shall correct any overpayment of liquidated damages by the Bidder by adjusting the next payment certificate. The Bidder shall be paid interest on the overpayment, calculated from the date of payment to the date of repayment, at the rates specified in SCC.
22.3 Lack of performance penalty
If the Bidder has not corrected a Defect within the time specified in the Procuring Agency’s notice, a penalty for Lack of performance will be paid by the Bidder. The amount to be paid will be calculated as a percentage of the cost of having the Defect corrected, assessed as specified in the SCC.
23. Performance Guarantee
23.1 Within Seven (07) days from the issuance of acceptance letter from the Procuring Agency, the successful Bidder shall furnish the Performance Guarantee in shape of ------- at the discretion of the PA in the amount specified in SCC. In case the amount of Bids security is equal or greater than
23.2 The proceeds of the Performance Guarantee shall be payable to the Procuring agency as compensation for any loss resulting from the Supplier’s failure to complete its obligations under the Contract.
23.3 The Performance Guarantee shall be denominated in the currency of the Contract, or in a freely convertible currency acceptable to the Procuring agency and shall be in the acceptable form as specified in SCC.
23.4 The Performance Guarantee will be discharged by the Procuring agency and returned to the Supplier not later than thirty (30) days following the date of completion of the Supplier’s performance obligations under the Contract, including any warranty obligations, unless otherwise specified in SCC.
24. Fraud and Corruption
24.1 The Procuring Agency requires the Supplier to disclose any commissions or fees that may have been paid or are to be paid to agents or any other party with respect to the Bidding process or execution of the Contract. The information disclosed must include at least the name and address of the agent or other party, the amount and currency, and the purpose of the commission, gratuity or fee.
25. Sustainable Procurement
25.1 The Bidder shall conform to the sustainable procurement contractual provisions, if and as specified in the SCC.
26. Description of Personnel
26.1 The titles, agreed job descriptions, minimum qualifications, and estimated periods of engagement in the carrying out of the Services of the Bidder’s Key Personnel. The Key Personnel listed by title as well as by name are hereby approved by the Procuring Agency.
27. Removal and/or Replacement of Personnel
27.1 Except as the Procuring Agency may otherwise agree, no changes shall be made in the Key Personnel. If, for any reason beyond the reasonable control of the Bidder, it becomes necessary to replace any of the Key Personnel, the Bidder shall provide as a replacement a person of equivalent or better qualifications.
27.2 If the Procuring Agency finds that any of the Personnel have (i) committed serious misconduct or have been charged with having committed a criminal action, or (ii) have reasonable cause to be dissatisfied with the performance of any of the Personnel, then the Bidder shall, at the Procuring Agency’s written request specifying the grounds thereof, provide as a replacement a person with qualifications and experience acceptable to the Procuring Agency.
27.3 The Bidder shall have no claim for additional costs arising out of or incidental to any removal and/or replacement of Personnel.
28. Assistance and Exemptions
28.1 The Procuring Agency shall use its best efforts to ensure that the Government shall provide the Bidder such assistance and exemptions as specified in the SCC.
29. Change in the Applicable Law
29.1 If, after the date of this Contract, there is any change in the Applicable Law with respect to taxes and duties which increases or decreases the cost of the related Services rendered by the Bidder, then the remuneration and reimbursable expenses otherwise payable to the Bidder under this Contract shall be increased or decreased accordingly by agreement between the Parties, and corresponding adjustments shall be made to the amounts referred in the SCC.
30. Services and Facilities
30.1 The Procuring Agency shall make available to the Bidder and the Experts, for the purposes of the Services and free of any charge, the services, facilities and property described , at the times and in the manner specified in the SCC or terms of reference.
30.2 In case that such services, facilities and property shall not be made available to the Bidder, the Parties shall agree on (i) any time extension that it may be appropriate to grant to the Bidder for the performance of the Services, (ii) the manner in which the Bidder shall procure any such services, facilities and property from other sources, and (iii) the additional payments, if any, to be made to the Bidder as a result thereof.
31. Contract Price
31.1 The price payable shall be in Pakistani Rupees unless otherwise specified in the SCC. Prices charged by the Supplier for Goods delivered under the Contract shall not vary from the prices quoted by the Supplier in its Bid.
32. Terms and Conditions of Payment
32.1 Payments will be made to the Bidder according to the payment schedule stated in the SCC and as per actual invoice submitted by the Bidder.
32.2 Unless otherwise stated in the SCC, the advance payment shall be made against the provision by the Bidder of a bank guarantee for the same amount, and shall be valid for the period stated in the SCC. Any other payment shall be made after the conditions listed in the SCC for such payment have been met, and the Bidder have submitted an invoice to the Procuring Agency specifying the amount due.
33. Currency of Payment
33.1 Any payment under this Contract shall be made in the currency(ies) specified in the SCC.
34. Identifying Defects
34.1 The principle and modalities of Inspection of the Goods by the Procuring Agency shall be as indicated in the SCC. The Procuring Agency shall check the Bidder’s performance and notify him of any Defects that are found. Such checking shall not affect the Bidder’s responsibilities. The Procuring Agency may instruct the Bidder to search for a Defect and to uncover and test any service that the Procuring Agency considers may have a Defect. Defect Liability Period is as defined in the SCC.
35. Correction of Defects,and
Lack of Performance Penalty
35.1 The Procuring Agency shall give notice to the Bidder of any Defects before the end of the Contract. The Defects liability period shall be extended for as long as Defects remain to be corrected.
35.2 Every time notice a Defect is given, the Bidder shall correct the notified Defect within the length of time specified by the Procuring Agency’s notice.
35.3 If the Bidder has not corrected a Defect within the time specified in the Procuring Agency’s notice, the Procuring Agency will assess the cost of having the Defect corrected, the Bidder will pay this amount, and a Penalty for Lack of Performance.
36. Taxes and Duties
36.1 A Supplier shall be entirely responsible for all taxes, duties, fees, etc., incurred until delivery of the contracted Goods to the Procuring Agency.
37. Alternate Dispute Resolution
37.1 The disputes between the parties to the contract may be settled in accordance with Public Procurement Rules, 2004.
37.2 The procuring agency shall refer the matter to the Chief Justice Islamabad High Court or Managing Director PPRA or the Secretary Ministry of Law & Justice for appointment of Arbitrator.
37.3 The fee for the Arbitrator shall be specified in Pak Rupees as determined by the appointing authority which shall be borne and shared equally by the contracting parties.
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
Number of GC Clause 1
Definitions
The Procuring Agency is: Ministry of Foreign Affairs (Ministry of Foreign Affairs (MOFA)), Deputy Director Constitution Avenue, Sector G-5., Islamabad Capital Territory
The Supplier is:
The title of the subject procurement is: Subscription of endpoint security (XDR) &clientless VPN Licenses
Number of GC Clause 3
Applicable/Governing Law:
The Contract shall be interpreted in accordance with the laws of Islamic Republic of Pakistan
Number of GC Clause 4
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 5
Notices:
The addresses for the notices are:
Procuring Agency:
Ministry of Foreign Affairs (Ministry of Foreign Affairs (MOFA)), Deputy Director
Constitution Avenue, Sector G-5., Islamabad Capital Territory
+92-347-725-9108
adgs.sykb@mofa.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 7.1
The Authorized Representatives are:
For the Procuring Agency:
Ministry of Foreign Affairs (Ministry of Foreign Affairs (MOFA)), Deputy Director
Constitution Avenue, Sector G-5., Islamabad Capital Territory
+92-347-725-9108
adgs.sykb@mofa.gov.pk
For the Bidder:
Name: ………………………
Designation: ……………..
Address: ……………………………..
Number of GC Clause 8
Effectiveness of the contract
Number of GC Clause 9
Commencement of Contract:
Number of GC Clause 11.2
Expiration of Contract:
Number of GC Clause 15
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 17
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 17.
Number of GC Clause 22
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.50% to 2.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 23
Performance Guarantee:
The amount of performance guarantee shall be 5.00% of the contract price in acceptable form of Pay Order, Call at Deposit, Bank Guarantee
Number of GC Clause 32
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 33
Currency of Payment:
All the payment to be released to the contractor/Bidder shall be in Pakistani Rupees.
Number of GC Clause 34
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 being Brand New, bearing relevant reference numbers of the equipment (Certificate from supplier)
For Physical Fitness having No Damages (Certificate from supplier)
For the Country of Origin as quoted by the Supplier (Certificate from manufacturer)
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)
Copies of the Supplier’s invoice showing Goods’ description, quantity, unit price, and total amount;
Original and two copies of the usual transport document (for example, a negotiable bill of lading, a non-negotiable sea waybill, an inland waterway document, an air waybill, a railway consignment note, a road consignment note, or a multimodal transport document) which the buyer may require to take the goods;
Copies of the packing list identifying contents of each package;
Insurance Certificate;
Manufacturer’s or Supplier’s Valid Warranty Certificate;
Inspection Certificate issued by the Nominated Inspection Agency (if any), and the Supplier’s Factory Inspection Report;
Certificate of Origin.
The above documents would be required even if the equipment has already been imported and is available with the supplier ex-stock
The duration for the supply of licensed software shall not exceed 10 days from the issuance of Purchase Order.
The deployment for the supply of licensed software shall not exceed 5 days after license delivery.
Number of GC Clause 37
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.
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.:P54539
To: Ministry of Foreign Affairs (Ministry of Foreign Affairs (MOFA)), Deputy Director Constitution Avenue, Sector G-5., Islamabad Capital Territory
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 Ministry of Foreign Affairs (Ministry of Foreign Affairs (MOFA)), Deputy Director Constitution Avenue, Sector G-5., Islamabad Capital Territory
(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., Subscription of endpoint security (XDR) &clientless VPN Licenses (P54539) and has accepted a Bids by the Bidder for the provision of Goods 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: Ministry of Foreign Affairs (Ministry of Foreign Affairs (MOFA)), Deputy Director Constitution Avenue, Sector G-5., Islamabad Capital Territory
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 Goods(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}
Relevant Projects completed in last 3 years related to End Point Protection solution with documentary proof be provided i.e. completion certificates issued by the clients etc.)
Financial Strength of the Company provide Financial statements/ Annual Turnover of FY 2024-25