Embed Size (px)
Citation preview
ORIGINAL
KENYATTA NATIONAL HOSPITAL
OPEN TENDER FOR
---------------------------------------------------- SUPPLY, DELIVERY, INSTALLATION, TESTING, COMMISSIONING AND SUPPORT OF THE ENTERPRISE RESOURCE PLANNING (ERP) SYSTEM AND SUPPORTING HARDWARE AND
SOFTWARE COMPONENTS
TENDER NO: KNH/T/67/2018-2019
THE CHIEF EXECUTIVE OFFICER KENYATTA NATIONAL HOSPITAL
P.O BOX 20723- 00202, NAIROBI.
Page 2 of 165
COPY
KENYATTA NATIONAL HOSPITAL
OPEN TENDER FOR
SUPPLY, DELIVERY, INSTALLATION, TESTING, COMMISSIONING AND SUPPORT OF THE ENTERPRISE RESOURCE PLANNING (ERP) SYSTEM AND SUPPORTING HARDWARE AND
SOFTWARE COMPONENTS ----------------------------------------------------
TENDER NO: KNH/T/67/2018-2019
THE CHIEF EXECUTIVE OFFICER KENYATTA NATIONAL HOSPITAL
P.O BOX 20723- 00202, NAIROBI.
TABLE OF CONTENTS
PAGE
* SECTION I INVITATION TO TENDER ……………….. 4
* SECTION II INSTRUCTIONS TO TENDERERS ………… 5
Appendix to Instructions to tenderers ……….. 24
* SECTION III GENERAL CONDITIONS OF CONTRACT…… 75
* SECTION IV SPECIAL CONDITIONS OF CONTRACT……………………82
* SECTION V SCHEDULE OF REQUIREMENTS AND PRICE……………83
* SECTION VI TECHNICAL SPECIFICATION………………………………….87
* SECTION VII STANDARD FORMS …………………………………………………89
7.1 FORM OF TENDER……………………………………….91
7.2 CONFIDENTIAL BUSINESS & QUESTIONNAIRE FORM……………………………………………………………93
7.3 TENDER SECURITY FORM……………………………95
7.4 CONTRACT FORM……………………………………….96
7.5 PERFORMANCE SECURITY FORM…………………97
7.6 BANK QUARANTEE FOR ADVANCE PAYMENT98
7.7 MANUFACTURER’S AUTHORIZATION FORM .. 99
7.8 LETTER OF NOTIFICATION OF AWARD……..100
7.9 REQUEST FOR REVIEW FORM…………………..101
7.10 SITE VISIT CERTIFICATE……………………………102
7.11 BANK DETAILS FORM………………………………….103
SECTION I INVITATION TO TENDER
TENDER REF NO: KNH/T/67/2018-2019
1.1 TENDER NAME: Supply, Delivery, Installation, Testing, Commissioning and of the Enterprise Resource Planning (ERP) System and supporting hardware and software components.
1.2 Kenyatta National Hospital invites sealed open tenders from eligible candidates for Supply, Delivery, Installation, Testing, Commissioning and Support of the Enterprise Resource Planning (ERP) System and supporting hardware and software components.
1.3 Interested eligible candidates may obtain further information from and inspect the tender documents at the office of the Deputy Director, Supply Chain Management located at the Hospital's Main Administration Block Room 6 from Monday to Friday during normal working hours.
1.4 A complete set of tender documents can be obtained from the office of the Deputy Director, Supply Chain Management located at the Hospital's Main Administration Block Room 6 from Monday to Tuesday between 9.00 a.m. to 4.00 p.m. upon payment of a non-refundable fee of Kshs. 1,000.00 per document in the form of Cash, Bankers Cheque or Money order made payable to Kenyatta National Hospital. Alternatively tender documents with detailed specifications and all conditions are obtainable from the KNH Website, (www.knh.or.ke or https//supplier.treasury.go.ke, IFMIS portal free of charge. Bidders are required to download the tender documents from the said websites and immediately email their names and contact details ( cell phone number, email address and company name to [email protected] or [email protected] for records and communication of any tender clarifications and addenda
1.5 Prices quoted should be net inclusive of all taxes, must be in Kenya Shillings.
1.6 Completed tender documents are to be enclosed in plain sealed envelopes marked with tender reference number and be deposited in the Tender Box at the entrance of the Supply Chain Department Offices and addressed to:
Chief Executive Officer Kenyatta National Hospital P. O Box 20723 – 00202 Nairobi
So as to be received on or before Thursday 11th October2018 Tenders will be opened immediately thereafter in the presence of the Candidates or their representatives who choose to attend
SIGNED For: Chief Executive Officer
SECTION II - INSTRUCTIONS TO TENDERERS Table of Clauses
Page
2.1 Eligible Tenderers .................................................... 6
2.2 Eligible Equipment .................................................... 6
2.3 Cost of Tendering ..................................................... 7
2.4 Contents of Tender Document ...................................... 7
2.5 Clarification of Tender Documents ................................. 7
2.6 Amendment of Tender Document .................................. 8
2.7 Language of Tender .................................................. 8
2.8 Documents Comprising the Tender ................................. 8
2.9 Tender Forms .......................................................... 9
2.10 Tender Prices .......................................................... 9
2.11 Tender Currencies .................................................... 10
2.12 Tenderers Eligibility and Qualifications ........................... 10
2.13 Equipment’ Eligibility and Conformity to Tender Document.11 2.14 Tender Security .............................................................. 12
2.15 Validity of Tenders ................................................... 13
2.16 Format and Signing of Tenders ..................................... 13
2.17 Sealing and Marking of Tenders ..................................... 14
2.18 Deadline for Submission of Tender ................................. 14
2.19 Modification and Withdrawal of Tenders .......................... 14
2.20 Opening of Tenders ................................................... 15
2.21 Clarification of Tenders .............................................. 15
2.22 Preliminary Examination ............................................. 16
2.23 Conversion to Single Currency ...................................... 17
2.24 Evaluation and Comparison of Tenders ............................ 17
2.25 Contacting the Procuring Entity .................................... 18
2.26 Award of Contract .................................................... 18
(a) Post Qualification………………………………… 18
(b) Award criteria …………………………………… 19
(c) Procuring Entity’s Right to Vary Quantities……. 19
(d ) Procuring Entity’s Right to Accept or Reject any
or all Tenders ………………………………….. 19
2.27 Notification of Award…………………………… 20
2.28 Signing of Contract………………………………. 20
2.29 Performance Security …………………………….. 20
2.30 Corrupt or Fraudulent Practices…………………. 21
SECTION II – INSTRUCTIONS TO TENDERERS 2.1 Eligible Tenderers
2.1.1 This Invitation for Tenders is open to all tenderers eligible as described in the Appendix to Instructions to Tenderers. Successful tenderers shall complete the supply, install, commissioning and support of the systems by the intended completion date specified in the tender documents.
2.1.2 The procuring entity’s employees, committee members, board members and their relative (spouse and children) are not eligible to participate in the tender unless where specially allowed under section 131 of the Act.
2.1.3 Tenderers shall provide the qualification information statement that the tenderer (including all members of a joint venture and subcontractors) is not associated, or have been associated in the past, directly or indirectly, with a firm or any of its affiliates which have been engaged by the Procuring entity to provide consulting services for the preparation of the design, specifications, and other documents to be used for the procurement of the equipment under this Invitation for tenders.
2.1.4 Tenderers involved in corrupt or fraudulent practices or debarred from participating in public procurement shall not be eligible.
2.2 Eligible goods
2.2.1 All goods to be supplied under the contract shall have their origin in eligible source countries.
2.2.2 For purposes of this clause, “origin” means the place where the goods are produced. Goods are produced when, through manufacturing, processing, or substantial and major assembly of components, a commercially-recognized product results that is substantially different in basic characteristics or in purpose or utility from its components
2.2.3 The origin of goods is distinct from the nationality of the tenderer and shall be treated thus in the evaluation of the tender.
2.3 Cost of Tendering
2.3.1 The Tenderer shall bear all costs associated with the preparation and submission of its tender, and the procuring entity, will in no case be responsible or liable for those costs, regardless of the conduct or outcome of the tendering process.
2.3.2 The price to be charged for the tender document shall not exceed Ksh 1000.00
2.3.3 The procuring entity shall allow the tenderer to review the tender document free of charge before purchase.
2.4. Contents of Tender Document
2.4.1 The tender document comprises the documents listed below and addenda issued in accordance with clause 2.6 of these instructions to tenderers
(i) Invitation to Tender
(ii) Instructions to Tenderers
(iii) General Conditions of Contract
(iv) Special Conditions of Contract
(v) Schedule of requirements
(vi) Technical Specifications
(vii) Tender Form and Price Schedules
(viii) Tender Security Form
(ix) Contract Form
(x) Performance Security Form
(xi) Bank Guarantee for Advance Payment Form
(xii) Manufacturer’s Authorization Form
(xiii) Confidential Business Questionnaire Form
(xiv) Declaration form
(xv) Request for Review Form
2.4.2 The Tenderer is expected to examine all instructions, forms, terms, and specifications in the tender documents. Failure to furnish all information required by the tender documents or to submit a tender
not substantially responsive to the tender documents in every respect will be at the tenderers risk and may result in the rejection of its tender.
2.5 Clarification of Tender Documents
2.5.1 A prospective tenderer making inquiries on the tender documents may notify the
Procuring entity in writing or by post at the entity’s address indicated in the
invitation for tenders. The Procuring entity will respond in writing to any
request for clarification of the tender documents, which it receives not later
than seven (7) days prior to the deadline for the submission of tenders,
prescribed by the procuring entity. Written copies of the Procuring entities
response (including an explanation of the query but without identifying the
source of inquiry) will be sent to all prospective tenderers that have received
the tender document.
2.5.2 The procuring entity shall reply to any clarifications sought by the tenderer within 3 days of receiving the request to enable the tenderer to make timely submission of its tender.
2.6 Amendment of Tender Documents
2.6.1 At any time prior to the deadline for submission of tender, the procuring entity, for any reason, whether at its own initiative or in response to a clarification requested by a prospective tenderer, may modify the tender documents by issuing an addendum.
2.6.2 All prospective tenderers that have obtained the tender documents will be notified of the amendment in writing or by post and will be binding on them.
2.6.3 In order to allow prospective tenderers reasonable time in which to take the amendment into account in preparing their tenders, the Procuring entity, at its discretion, may extend the deadline for the submission of tenders.
2.7 Language of Tender
2.7.1 The tender prepared by the tenderer, as well as all correspondence and documents relating to the tender exchange by the tenderer and the Procuring entity, shall be written in English language, provided that any printed literature furnished by the tenderer may be written in another language provided they are accompanied by an accurate English translation of the relevant passages in which case, for purposes of interpretation of the tender, the English translation shall govern.
2.8 Documents Comprising the Tender
2.8.1 The tender prepared by the tenderers shall comprise the following components.
(a) a Tender Form and a Price Schedule completed in accordance with paragraph 2.9, 2.10 and 2.11 below
(b) documentary evidence established in accordance with paragraph 2.12 that the tenderer is eligible to tender and is qualified to perform the contract if its tender is accepted;
(c) documentary evidence established in accordance with paragraph 2.13 that the equipment and ancillary services to be supplied by the tenderer are eligible equipment and services and conform to the tender documents; and
(d) tender security furnished in accordance with paragraph 2.14
(e) Confidential Business Questionnaire
2.9 Tender Form
2.9.1 The tenderer shall complete the Form of Tender and the appropriate Price Schedule furnished in the tender documents, indicating the equipment to be supplied, installed and commissioned and a brief description of the equipment, their country of origin, quantity, and prices.
2.10 Tender Prices
2.10.1 The tenderer shall indicate on the appropriate Price Schedule the unit prices where applicable and total tender price of the systems it proposes to supply under the contract.
2.10.2 Prices indicated on the Price Schedule shall be entered separately in the following manner:
(i) the price of the equipment quoted EXW (ex works, ex factory, ex warehouse, ex showroom, or off-the-shelf, as applicable), including all customs duties and sales and other taxes already paid or payable:
(ii) charges for inland transportation, insurance, and other local costs incidental to delivery of the equipment to their final destination; and
(iii) installation charges shall also be indicated separately for each equipment
2.10.3 Prices quoted by the tender shall remain fixed during the Tender’s performance of the contract. A tender submitted with an adjustable price quotation will be treated as non-responsive and will be rejected, pursuant to paragraph 2.22 unless otherwise agreed by the parties.
2.11 Tender Currencies
2.11.1 Prices shall be quoted in the following currencies:
(a) For equipment that the tenderer will supply from within Kenya, the prices shall be quoted in Kenya Shillings; and
(b) For equipment that the tenderer will supply from outside Kenya, the prices may be quoted in US Dollars or in another freely convertible currency.
(c) Cost of installation and commissioning will be in Kenya Shillings.
2.12 Tenderers Eligibility and Qualifications
2.12.1 Pursuant to paragraph 2.1. the tenderers shall furnish, as part of its tender, documents establishing the tenderers eligibility to tender and its qualifications to perform the contract if its tender is accepted.
2.12.1 The documentary evidence of the tenderers eligibility to tender shall establish to the Procuring entity’s satisfaction that the tenderer, at the time of submission of its tender, is from an eligible source country as defined under paragraph 2.1
2.12.2 The documentary evidence of the tenderers qualifications to perform the contract if its tender is accepted shall establish to the Procuring entity’s satisfaction;
(a) that, in the case of a tenderer offering to supply equipment/system under the contract which the tenderer did not manufacture or otherwise produce, the tenderer has been duly authorized by the equipment, Manufacturer or producer to supply the equipment
(b) that the tenderer has the financial, technical, and production capability necessary to perform the contract;
(c) that, in the case of a tenderer not doing business within Kenya, the tenderer is or will be (if awarded the contract) represented by an Agent
in Kenya equipped, and able to carry out the Tenderer’s maintenance, repair, and support obligations prescribed in the Conditions of Contract and/or Technical Specifications.
2.13 Equipment Eligibility and Conformity to Tender Document
2.13.1 Pursuant paragraph 2.2 of this section, the tenderer shall furnish, as part of its tender documents establishing the eligibility and conformity to the tender documents of all equipment which the tenderer proposes to supply under the contract
2.13.2 The documentary evidence of the eligibility of the equipment shall consist of statement in the Price Schedule of the country of origin of the equipment and services offered which shall be confirmed by a certificate of origin issued at the time of shipment.
2.13.3 The documentary evidence of conformity of the equipment to the tender documents may be in the form of literature, drawings, and data, and shall consist of:
a) a detailed description of the essential technical and performance characteristic of the equipment
b) a list giving full particulars, including available source and current prices of spare parts, special tools, etc., necessary for the proper and continuing functioning of the equipment for a period of two (2) years, following commencement of the use of the equipment by the Procuring entity; and
c) a clause-by-clause commentary on the Procuring entity’s Technical Specifications demonstrating substantial responsiveness of the equipment and service to those specifications, or a statement of deviations and exceptions to the provisions of the Technical Specifications.
2.13.4 For purposes of the commentary to be furnished pursuant to paragraph 2.13.3(c ) above, the tenderer shall note that standards for workmanship, material, and equipment, as well as references to brand names or catalogue numbers designated by the Procurement entity in its Technical Specifications, are intended to be descriptive only and not restrictive. The tenderer may substitute alternative standards, brand names, and/or catalogue numbers in its tender, provided that it demonstrates to the Procurement entity’s satisfaction that the substitutions ensure substantial equivalence to those designated in the Technical Specifications.
2.14 Tender Security
2.14.1 The tenderer shall furnish, as part of its tender, a tender security for the amount and form specified in the Appendix to Instructions to Tenderers.
2.14.2 The tender security shall be in the amount not exceeding 2 percent of the tender price.
2.14.3 The tender security is required to protect the Procuring entity against the risk of Tenderer’s conduct which would warrant the security’s forfeiture, pursuant to paragraph 2.14.7
2.14.4 The tender security shall be denominated in Kenya Shillings or in another freely convertible currency, and shall be in the form of
a) Cash b) A bank guarantee
c) Such insurance guarantee approved by the Authority d) Letter of credit.
2.14.5 Any tender not secured in accordance with paragraph 2.14.1 and 2.14.3 will be rejected by the Procuring entity as non responsive, pursuant to paragraph 2.22
2.14.6 Unsuccessful Tenderer’s tender security will be discharged or returned as promptly as possible as but not later than thirty (30) days after the expiration of the period of tender validity prescribed by the Procuring entity.
2.14.7 The successful Tenderer’s tender security will be discharged upon the tenderer signing the contract, pursuant to paragraph 2.27 and furnishing the performance security, pursuant to paragraph 2.28
2.14.8 The tender security may be forfeited:
a) if a tenderer withdraws its tender during the period of tender validity specified by the procuring entity on the Tender Form; or
b) in the case of a successful tenderer, if the tenderer fails:
i) to sign the contract in accordance with paragraph 2.27.or
ii) to furnish performance security in accordance with paragraph 2.28
c) If the tenderer rejects correction of an arithmetic error in the tender.
2.15 Validity of Tenders
2.15.1 Tenderers shall remain valid for 180 days or as specified in the tender documents after date of tender opening prescribed by the Procuring entity, pursuant to paragraph 2.20. A tender valid for a shorter period shall be rejected by the Procuring entity as non responsive.
2.15.2 In exceptional circumstances, the Procuring entity may solicit the Tenderer’s consent to an extension of the period of validity. The request and the responses thereto shall be made in writing. The tender security provided under paragraph 2.14 shall also be suitably extended. A tenderer may refuse the request without forfeiting its tender security. A tenderer granting the request will not be required nor permitted to modify its tender.
2.16 Format and Signing of Tender
The Procuring entity shall prepare two copies of the tender, clearly marking each “ORIGINAL TENDER” and “COPY OF TENDER,” as Appropriate. In the event of any discrepancy between them, the original shall govern.
2.16.1 The original and all copies of the tender shall be typed or written in indelible ink and shall be signed by the tenderer or a person or persons duly authorized to bind the tenderer to the contract. All pages of the tender, except for unamended printed literature, shall be initialed by the person or persons signing the tender.
2.16.2 The tender shall have no interlineations, erasures, or overwriting except as necessary to correct errors made by the tenderer, in which case such corrections shall be initialed by the person or persons signing the tender.
2.17 Sealing and Marking of Tenders
2.17.1 The Tenderer shall seal the original and each copy of the tender in separate envelopes, duly marking the envelopes as “ORIGINAL” and “COPY.” The envelopes shall then be sealed in an outer envelope.
2.17.2 The inner and outer envelopes shall:
(a) be addressed to the Procuring entity at the address given on he Invitation to Tender.
(b) bear the tender number and name in the Invitation to Tender and the words “DO NOT OPEN BEFORE Thursday, 11th October 2018 at 10.00am
2.17.3 The inner envelopes shall also indicate the name and address of the tenderer to enable the tender to be returned unopened in case it is declared “late”.
2.17.4 If the outer envelope is not sealed and marked as required by paragraph 2.17.2, the Procuring entity will assume no responsibility for the tender’s misplacement or premature opening.
2.18 Deadline for Submission of Tenders
Page 20 of 165
Tenders must be received by the Procuring entity at the address specified under paragraph 2.17.2 not later than Thursday, 11th October2018
2.18.1 The Procuring entity may, at its discretion, extend this deadline for the submission of tenders by amending the tender documents in accordance with paragraph 2.6, in which case all rights and obligations of the Procuring entity and candidates previously subject to the deadline will therefore be subject to the deadline as extended
2.18.2 Bulky tenders which will not fit in the tender box shall be received by the procuring entity as provided for in the Appendix.
2.19 Modification and Withdrawal of Tenders 2.19.1 The tenderer may modify or withdraw its tender after the tender’s submission,
provided that written notice of the modification, including substitution or withdrawal of the tenders, is received by the Procuring entity prior to the deadline prescribed for submission of tenders.
2.19.2 The Tenderer’s modification or withdrawal notice shall be prepared, sealed,
marked, and dispatched in accordance with the provisions of paragraph 2.17. A withdrawal notice may also be sent by cable, telex but followed by a signed confirmation copy, postmarked not later than the deadline for submission of tenders.
2.19.3 No tender may be modified after the deadline for submission of tenders.
2.19.4 No tender may be withdrawn in the interval between the deadline for
submission of tenders and the expiration of the period of tender validity specified by the tenderer on the Tender Form. Withdrawal of a tender during this interval may result in the Tenderer’s forfeiture of its tender security, pursuant to paragraph 2.14.7
2.20 Opening of Tenders
The Procuring entity will open all tenders in the presence of tenderers’ representatives who choose to attend, on Thursday, 11th October2018 at 10.00am. The tenderers’ representatives who are present shall sign a tender opening register evidencing their attendance.
2.20.1 The tenderers’ names, tender modifications or withdrawals, tender prices,
discounts and the presence or absence of requisite tender security and such other details as the Procuring entity, at its discretion, may consider appropriate, will be announced at the opening.
Page 21 of 165
2.20.2 The Procuring entity will prepare minutes of the tender opening.
2.21 Clarification of Tenders
2.21.1 To assist in the examination, evaluation and comparison of tenders the
Procuring entity may, at its discretion, ask the tenderer for a clarification of its tender. The request for clarification and the response shall be in writing, and no change in the prices or substance of the tender shall be sought, offered, or permitted.
2.21.2 Any effort by the tenderer to influence the Procuring entity in the Procuring
entity’s tender evaluation, tender comparison or contract award decisions may result in the rejection of the tenderers’ tender.
2.22 Preliminary Examination and Responsiveness
2.22.1 The Procuring entity will examine the tenders to determine whether they are
complete, whether any computational errors have been made, whether required sureties have been furnished, whether the documents have been properly signed, and whether the tenders are generally in order.
Arithmetical errors will be rectified on the following basis. If there is a discrepancy between the unit price and the total price that is obtained by multiplying the unit price and quantity, the unit price shall prevail, and the total price shall be corrected. If the candidate does not accept the correction of the errors, its tender will be rejected, and its tender security may be forfeited. If there is a discrepancy between words and figures the amount in words will prevail
2.22.2 The Procuring entity may waive any minor informality or non- conformity or irregularity in a tender which does not constitute a material deviation, provided such waiver does not prejudice or effect the relative ranking of any tenderer.
2.22.3 Prior to the detailed evaluation, pursuant to paragraph 2.23 the Procuring
entity will determine the substantial responsiveness of each tender to the tender documents. For purposes of these paragraphs, a substantially responsive tender is one, which conforms to all the terms and conditions of the tender documents without material deviations. The Procuring entity’s determination of a tender’s responsiveness is to be based on the contents of the tender itself without recourse to extrinsic evidence.
2.22.4 If a tender is not substantially responsive, it will be rejected by the Procuring
entity and may not subsequently be made responsive by the tenderer by correction of the non conformity.
2.23 Conversion to Single Currency
2.23.1 Where other currencies are used, the Procuring Entity will convert those
Page 22 of 165
currencies to Kenya Shillings using the selling exchange rate on the date of tender closing provided by the Central Bank of Kenya.
2.24 Evaluation and Comparison of Tenders
2.24.1 The Procuring entity will evaluate and compare the tenders which have been
determined to be substantially responsive, pursuant to paragraph 2.22
2.24.2 The Procuring entity’s evaluation of a tender will exclude and not take into
account
(a) in the case of equipment manufactured in Kenya or equipment of foreign origin already located in Kenya, sales and other similar taxes, which will be payable on the equipment if a contract is awarded to the tenderer; and
(b) any allowance for price adjustment during the period of execution of the contract, if provided in the tender.
2.24.3 The comparison shall be of the ex-factory/ex-warehouse/off-the-shelf price of the equipment offered from within Kenya, such price to include all costs, as well as duties and taxes paid or payable on components and raw material incorporated or to be incorporated in the equipment.
2.24.4 The Procuring entity’s evaluation of a tender will take into account, in
addition to the tender price and the price of incidental services, the following factors, in the manner and to the extent indicated in paragraph 2.23.5 and in the technical specifications:
(a) delivery and installation schedule offered in the tender;
(b) deviations in payment schedule from the specifications in the Special Conditions of Contract;
(c) the cost of components, mandatory spare parts and service;
(d) the availability in Kenya of spare parts and after-sales service for the equipment offered in the tender;
2.24.5 Pursuant to paragraph 2.24.4 the following evaluation methods will be applied
(a) Delivery schedule
(i) The Procuring entity requires that the equipment under the Invitation for Tenders shall be delivered at the time specified in the Schedule of Requirements. Tenders offering deliveries longer than the procuring entity’s required delivery time will be treated as non-responsive and rejected.
(b) Deviation in payment schedule Tenderers shall state their tender price for the payment of schedule outlined in the special conditions of contract. Tenders will be evaluated on the basis of this base price. Tenderers are, however, permitted to state an alternative payment schedule and indicate the reduction in tender price they wish to offer for such alternative payment schedule. The Procuring entity may consider the
Page 23 of 165
alternative payment schedule offered by the selected tenderer.
(c ) Spare parts and after sales service facilities
Tenderers must offer items with service and spare parts back-up. Documentary evidence and locations of such back-up must be given. Where a tenderer offers items without such back-up in the country, he must give a documentary evidence and assurance that he will establish adequate back-up for items supplied.
2.24.6 The tender evaluation committee shall evaluate the tender within 30 days of
the validity period from the date of opening the tender.
2.24.7 Preference where allowed in the evaluation of tenders shall not exceed 15%
2.25 Contacting the Procuring Entity
2.25.1 Subject to paragraph 2.21 no tenderer shall contact the Procuring entity on
any matter related to its tender, from the time of the tender opening to the time the contract is awarded.
2.25.2 Any effort by a tenderer to influence the Procuring entity in its decisions on
tender, evaluation, tender comparison, or contract award may result in the rejection of the Tenderer’s tender.
2.26 Award of Contract
(a) Post-Qualification
2.26.1 In the absence of pre-qualification, the Procuring entity will determine to its satisfaction whether the tenderer that is selected as having submitted the lowest evaluated responsive tender is qualified to perform the contract satisfactorily.
2.26.2 The determination will take into account the tenderer financial, technical, and production capabilities. It will be based upon an examination of the documentary evidence of the tenderers qualifications submitted by the tenderer, pursuant to paragraph 2.12.3 as well as such other information as the Procuring entity deems necessary and appropriate.
2.26.3 An affirmative determination will be a prerequisite for award of the contract to the tenderer. A negative determination will result in rejection of the Tenderer’s tender, in which event the Procuring entity will proceed to the next lowest evaluated tender to make a similar determination of that Tenderer’s capabilities to perform satisfactorily.
(b) Award Criteria
2.26.4 The Procuring entity will award the contract to the successful tenderer(s)
Page 24 of 165
whose tender has been determined to be substantially responsive and has been determined to be the lowest evaluated tender, provided further that the tenderer is determined to be qualified to perform the contract satisfactorily.
2.26.5 To qualify for contract awards, the tenderer shall have the following:
a) Necessary qualifications, capability experience, services, equipment and facilities to provide what is being procured.
b) Legal capacity to enter into a contract for procurement
c) Shall not be insolvent, in receivership, bankrupt or in the process of being wound up and is not the subject of legal proceedings relating to the foregoing.
d) Shall not be debarred from participating in public procurement.
(c) Procuring Entity’s Right to Accept or Reject Any or All Tenders
2.26.6 The Procuring entity reserves the right to accept or reject any tender, and to annul the tendering process and reject all tenders at any time prior to contract award, without thereby incurring any liability to the affected tenderer or tenderer of the grounds for the procuring entity’s action
2.26.7 The procuring entity may at any time terminate procurement proceedings before contract award and shall not be liable to any person for the termination
2.26.8 The procuring entity shall give prompt notice of the termination to the tenderers and on request give its reasons for termination within 14 days of receiving the request from any tenderer.
2.26.1 A tenderer who gives false information in the tender document about is qualification or who refuses to enter into a contract after notification of contract award shall be considered for debarment from participating in future public procurement.
2.27 Notification of Award
2.27.1 Prior to the expiration of the period of tender validity, the Procuring entity will notify the successful tenderer in writing that its tender has been accepted.
2.27.2 The notification of award will signify the formation of the Contract but will have to wait until the contract is finally signed by both parties. Simultaneous other tenderers shall be notified that their tenders have not been successful.
2.27.3 Upon the successful Tenderer’s furnishing of the performance security pursuant to paragraph 2.29, the Procuring entity will simultaneously inform the other tenderers that this tenders have not been successful
Page 25 of 165
2.28 Signing of Contract
2.28.1 At the same time as the Procuring entity notifies the successful tenderer that its tender has been accepted, the procuring entity will simultaneously inform the other tenderers that their tenders have not been successful.
2.28.2 Within fourteen (14) days of receipt of the Contract Form, the successful tenderer shall sign and date the contract and return it to the Procuring entity.
2.28.3 The parties to the contract shall have it signed within 30 days from the date of notification of contract award unless there is an administrative review request.
Page 26 of 165
2.29 Performance Security
2.29.1 Within Thirty (30) days of the receipt of notification of award from the Procuring entity, the successful tenderer shall furnish the performance security in accordance with the Conditions of Contract, in the Performance Security Form provided in the tender documents, or in another form acceptable to the Procuring entity.
2.29.2 Failure of the successful tenderer to comply with the requirements of paragraph 2.28 or paragraph 2.29 shall constitute sufficient grounds for the annulment of the award and forfeiture of the tender security, in which event the Procuring entity may make the award to the next lowest evaluated Candidate or call for new tenders.
2.30 Corrupt or Fraudulent Practices
2.30.1 The procuring entity requires that tenderers observe the highest standard of ethics during the procurement process and execution of contracts. A tenderer shall sign a declaration that he has and will not be involved in corrupt or fraudulent practices.
3.30.2 The Procuring entity will reject a proposal for award if it determines that the tenderer recommended for award has engaged in corrupt or fraudulent practices in competing for the contract in question.
3.30.3 Further a tenderer who is found to have indulged in corrupt or fraudulent practices risks being debarred from participating in public Procurement in Kenya.
Page 27 of 165
Appendix to Instructions to Tenderers
Notes on the Appendix to the Instructions to Tenderers
1. The Appendix to instructions to the tenderers is intended to assist the procuring entity in providing specific information in relation to corresponding clause in the instructions to Tenderers including in Section II and has to be prepared for each specific procurement.
2. The procuring entity should specify in the appendix information and requirement specific to the circumstances of the procuring entity, the equipment to be procured and the tender evaluation criteria that will apply to the tenders.
3. In preparing the Appendix the following aspects should be taken into consideration;
(a) The information that specifies and complements provisions of Section II to be incorporated
(b) Amendments and/or supplements if any, to provisions of Section II as necessitated by the circumstances of the equipment to be procured to be also incorporated
4. Section II should remain unchanged and can only be amended through the Appendix.
5. Clauses to be included in this part must be consistent with the public procurement law and the regulations.
APPENDIX TO INSTRUCTIONS TO TENDERERS
The following information regarding the particulars of the tender shall complement supplement or amend the provisions of the instructions to tenderers. Wherever there is a conflict between the provision of the instructions to tenderers and the provisions of the appendix, the provisions of the appendix herein shall prevail over those of the instructions to tenderers.
INSTRUCTIONS
TO
TENDERERS
REFERENCE
PARTICULARS OF APPENDIX TO INSTRUCTIONS TO TENDERS
2.1.1 Tender is open to local bidders specialized in the provision of the Enterprise Resource Planning (ERP) System and Supporting Hardware and Software.
2.1.4 Tenderer to provide a declaration on oath that neither the company nor the directors are subject to investigation or litigation on corruption and/or fraudulent practices.
2.3.2 A complete set of tender document can be obtained from the office of the DD, Supply Chain Management located at the Hospital's Main Administration Block Room 6 from Monday to Friday between 9.00 a.m. to 4.00 p.m. upon payment of a non-refundable fee of Kshs. 1,000.00 per document in the form of Cash, Bankers Cheque or Money order made payable to Kenyatta National Hospital. Alternatively tender documents with detailed specifications and all conditions are obtainable from the KNH Website, (www.knh.or.ke or https//supplier.treasury.go.ke, IFMIS portal free of charge. Bidders are required to download the tender documents from the said websites and immediately email their names and contact details ( cell phone number, email address and company name to [email protected] or [email protected] for records and communication of any tender clarifications and addenda.
2.5.1 Kenyatta National Hospital shall only send to all prospective tenderers that have received the tender document, written copies of responses to the queries relevant to the bid document or specifications that necessitate additional information for the clarification of the documents.
2.10.1 Price quoted shall include the total cost of supply, delivery, installation, testing, commissioning, training, civil works and pre shipment inspection and two years warranty.
Page 29 of 165
INSTRUCTIONS
TO
TENDERERS
REFERENCE
PARTICULARS OF APPENDIX TO INSTRUCTIONS TO TENDERS
2.12 The Documentary evidence of the tenderers qualifications to perform the contract if its tender is accepted shall be established to the Procuring entity’s satisfaction;
1. Registered offices and evidence of business premises. 2. A valid Tax compliance certificate which will be verified by KRA TCC
checker or proof that the authority of that the country of origin does not pay tax
3. Evidence that tenderer has the legal capacity to enter into a contract for the procurement;
4. Evidence that the tenderer is not insolvent, in receivership, bankrupt or in the process of being wound up and is not the subject of legal proceedings relating to the foregoing;
5. The person is not debarred from participating in procurement t proceedings
2.14.1 Tender Security shall be denominated in Kenya Shillings and Shall be in: a) Cash b) A bank guarantee c) Such insurance guarantee approved by the Authority
2.14.2 The tender security shall be Kenya Shillings three (3) million in the form
provided under 2.14.1. It can also be in currency easily convertible to Kenya Shillings 2.15 Tenders shall remain valid for 120 days from the deadline date of submission
of tender.
2.17.1 The bidders MUST submit combined technical & financial bid, one original and one copy of the tender, enclosed in the outer envelope
marked with the tender name and the tender identification number.
2.18.1 The day, date and time of closing the tender will be Thursday, 11th October, 2018 East African Time
2.18.2 Bulky tenders which will not fit in the tender box shall can be hand delivered on the opening day at the tender box
2.19.2 Any withdrawal notice shall NOT be sent by cable or telex but may be sent by email
2.20.1 Tender will be opened on Thursday, 11th October2018 East African Time
2.21.1 The request for clarification and the response shall be in writing though the:- Chief Executive Officer Kenyatta National Hospital P. O Box 20723 – 00202 Nairobi
2.24.7 Preference in allocation of marks is not applicable in this tender
Page 30 of 165
2.24 Evaluation and Comparison of Tenders
A. Preliminary Evaluation
Responsive No. Requirements
Responsive or Non Responsive
MR 1 Tender Security of Kenya Shillings Three million Kenya
Shillings (Kshs 3,000,000.00) valid for 150 days from the
date of tender opening. It can also be in currency easily
convertible to Kenya Shillings
MR 2 Submission of two Tender documents securely bound (Spiral or book) and clearly marked (original and copy) by the tenderer. No loose documents will be accepted
MR 3 All pages of both (Original & Copy) documents Must be Sequentially Serialized by the tenderer.
MR 4 Must Submit a copy of the Certificate of incorporation or Registration Certificate
MR 5 Must Submit a copy of Valid Tax Compliance certificate or a letter from the authority that the country of origin does not pay tax or tax exemption certificate.
MR 6 Must submit a dully filled up Confidential Business Questionnaire, signed and stamped
MR 7 Must submit dully filled form of tender, signed and stamped
MR 8 Attach a current certified bank statement for six months to demonstrate financial ability
MR 9 Evidence of physical registered office( attach utility bills/ lease agreement /rental payment receipt/ evidence of ownership of the premises)
MR 10 Audited accounts for the latest three consecutive years (2015, 2016 &2017) with an average turnover of at least Kenya Shillings three hundred million (Kshs 300,000,000.00)
MR 11 Tenderer to provide a declaration under oath that neither the company nor the directors are subject to investigation or litigation on corruption and/or fraudulent practices.
At this stage, the tenderer’s submission will either be responsive or non-responsive. The non-responsive submissions in any of the above mandatory requirements will be eliminated from the entire evaluation process and will not be considered further.
Page 31 of 165
B. Technical Evaluation
Step 1. Technical Mandatory Requirements BIDDERS WILL BE EVALUATED AS PER THE SYSTEM TECHNICAL PROPOSAL SUBMITTED The bidder MUST meet and satisfy all the requirements in this section. Only bidders who meet ALL the requirements for Step 1 will proceed to Step 2 of the Technical Evaluation. (TO BE IMPLEMENTED AS A TURNKEY PROJECT INCLUDING SET-UP OF THE SUPPORTING HARDWARE AND SOFTWARE COMPONENTS, INSTALLATION, TESTING, COMMISSIONING AND SUPPORT OF THE ERP AND INTEGRATION TO THIRD PARTY SYSTEMS) 1. ERP TECHNICAL MANDATORY REQUIREMENTS
ERP Technical Requirements
Item Mandatory Requirements Compliant (Y/N)
Detailed explanation with Cross-reference evidence
Database
1 Does database platform support scalability
2 The RDBMS must protect data from storage failures
3 DBMS capability for the database to perform backups and protection of data from various media failures
4 The Database platform supports high availability & geographical redundancy
5 DBMS capability to provide for proactive space management capabilities
6 Database provides a sophisticated alert notification system. DBAs can receive alerts via email, pagers, or directly by querying views inside the database server.
7 Segment maintenance operations online, i.e., the data is fully available for queries, updates, and deletes.
8 Database provides automatic performance diagnosis and monitoring technology, built inside the database server.
9 Database also provides rich reporting and base lining capabilities to facilitate comparative performance analysis.
10 Database also provides for the capability to identify and automatically tune high load SQL statements whenever the need arises.
11 Database ability to easily and accurately perform system and resource management.
Page 32 of 165
12 Database should provide capability to perform configuration management, provisioning and patching functionalities
13 Describe your database support of bit-map indexes (e.g. both dynamic and stored).
14 Does your solution provide any database encryption tools to protect payroll data
15 Does your RDBMS provide any foolproof logging capabilities
16 Does RDBMS provide any way of protecting payroll database logs from any modifications by administrators
17 Can your RDBMS be deployed in active environment
18 Does your RDBMS support any data redaction for sensitive data
19 Does your RDBMS support role segregation and rights assignment to different users
System Administration
20
All valid and failed login attempts must be logged with meaningful information that is actionable for investigative purposes if fraud is detected. However, passwords must not be logged.
21 The solution should support Multi-factor authentication (MFA) schemes
22 Each user must be authenticated with a unique user-id / username and password on the application. The User IDs / Usernames should be case sensitive
23
The solution should make a provision for authentication through digital certificates using Public Key Infrastructure (PKI) under the National Public Key Infrastructure.
24 The authentication should be configurable to use username/password and multi-factor authentication
25 The solution must prompt users to change their passwords the first time they log on to the application.
26
The solution must support password expiry features with a configurable frequency. This should be parameterized to allow flexibility in adjusting this value as required.
27 The solution must implement the following Password complexity requirements that should be configurable to support future password complexities:
28 The solution should implement a secure self-service password recovery mechanism in the event the user forgot their password.
29 The solution must support password lock out after a configurable number of unsuccessful login attempts.
30 The solution must expire a user account after the session has been idle for a period. This should be parameterized to allow flexibility in adjusting this
Page 33 of 165
value as required.
31 The system should allow the capture and storage of all relevant session information in a secure and auditable location
32 Roles should be granted permissions based on the principle of least privilege i.e. the solution should support an additive access model.
33 Access control must be granular to facilitate adequate separation of duties including the following:
34 Functions should be independently available for allocation to a role.
35 There should be separation of duties e.g. data entry, authorization and final approval.
36 The solution should log all access authorization requests to a secure and auditable location.
37
Error messages should be standard and not provide information alluding to the reason for the error allowing an attacker to deduce effective attack methods.
38
Every change to a database record should be identifiable to an application user with a record of the time of activity and type of operation on the record i.e. insert, update or delete.
39
All updates, inserts and deletes must be clearly traceable to an application user with corresponding time and source information (IP, module and function).
40 The solution should provide an interface to view and generate reports of the logs.
41
All valid and failed login attempts must be logged with meaningful information that is actionable for investigative purposes if fraud is detected. However, passwords must not be logged.
42 All password recovery reset attempts must be logged with meaningful information that is actionable for investigative purposes if fraud is detected.
43
All user and account management changes and attempts such as granting of roles and profiles, deactivation of users etc. must be logged and should include at minimum the following information: user effecting the changes, date and time stamp, IP address used, user affected
44 Bidder to state whether the system provides a backup and recovery facility.
45 Bidder to state whether the system support backup of database while in operation.
46 Bidder to state whether it is possible to schedule a backup/restore task.
Page 34 of 165
47 Bidders shall demonstrate all out of the box reports for the solution and show ability to generate both standardized and customized reports.
48
The bidder shall demonstrate that the solution has tools that provide easy to use wizards that will enable users to create customized reports. Users who perform this function will have to be trained on use of the tools.
49 Bidders shall demonstrate whether the reports are dynamic, with the provision for a drill-down capability.
50 Bidders to demonstrate whether the reports could be exported to Excel and PDF Formats and deliver HTML5 for internet & mobile users.
51 Bidders shall provide all requisite documentation
52 including but not limited to the following:
53 • System Architecture and Design
54 • User and technical manuals
55 • Training manuals
56
Bidders are required to demonstrate how the system has been designed for high availability in addition to showing how the system supports mission-critical business applications with minimal downtime.
57 The platform should be able to scale in performance capacity, incremental data volume growth and number of concurrent users.
58 Training
59 The Bidder must provide onsite functional training for the product
60 The Bidder must provide onsite technical training for the product
61 The bidder is expected to provide a methodology of evaluation of the training, learning and skills transfer
62
The bidder is expected to train the KNH project implementation team so that the team and the solution provider can have a common understanding of the proposed systems
Systems Security
63
Provide strong authentication & authorization and risk management and ensuring security and protection at data level by providing segregation of duties, raw level access, and encryption of data at rest and during data transfer.
64 Does your system provide clear roles and responsibilities segregation
65 Does your system provide capabilities to restrict user access rights at the following levels?
66 Transaction-limits the ability to perform system functions based on configured user roles and groups.
Page 35 of 165
67
Field Level security e.g. For example, The Kenyatta National Hospital can configure field-level security that only allows collection supervisors to change the status field of a payment agreement
68 Account Level Security-restricts access to specific citizens or citizen accounts
69 Does your system provide for configurable audit trails
70
Does your system support the auditing of data changes by users on fields, characteristics, or transactions? When a change is made to an audited field, the system captures the user, the date/time, the primary key of the row, the before/after images of the field value, and the database action performed.
71 Can your system be configured to capture details when specific records are searched for and displayed
72 Can your system be integrated to an LDAP solution
73
Can your systems provide administrators at Kenyatta National Hospital with the ability to mask certain data fields within the system allowing only specified users to view sensitive information such as personal identification numbers.
Document Management
74 Does your system have a document management integrated to it
75 Does your Document Management system provide workflow capabilities? Please explain
76
The system must have embedded document management and archiving capabilities that will enable Kenyatta National Hospital to have on each record an image, or document. The documents can be in any format like MS Word, PDF or other file formats
Finance Requirements
General Ledger
77 Ability to provide flexible chart of account structure that allows:
78 - Users to define length of account segments at time of installation
79 - Users to define account mask (e.g. numeric, alpha, alphanumeric etc.)
80 - Users to define elements of the account key (e.g. primary, secondary, third and fourth field segments)
81 - Users to define account segments (The number of segments can be increased or reduced)
82 Should provide account key that can support unlimited segments for account identification (e.g. branch, unit, product, account)
83 Ability to ensure that the account key is as per the set parameters
84 Ability to provide opportunity for user to define relationships between accounts
Page 36 of 165
85 Ability to edit and validate field combinations in the account key
86 Ability to allow the use of check digits to validate account numbers and other elements
87 Ability to capture an additional level of journal detail (e.g. deal number, employee number)
88 Ability to allow the use of miscellaneous data fields
89 Ability to allow edit of account/sub-account relationships with right controls in place
90
Ability to support separate and distinct ledgers or sub-ledger for specialized reporting purposes (e.g. Account performance tracking) or specific accounting purposes (e.g. fixed assets, employee accounting, syndicate deals)
91 Ability to provide memorandum accounts i.e. the off-balance sheet items e.g. Letters of credit
92 Ability to maintain book and tax data for selected accounts
93 Ability to maintain account balance limits
94 Ability to allow the user to specify transaction limits for individual accounts
95 Ability to allow the designation of accounts as "debit only" or "credit only" subject to controlled override by authorized personnel
96 Ability to delete or deactivate account automatically based on a user defined balance and activity criteria
97 Ability to allow the use of the same chart of accounts for actual, budgets and history
98 Ability to support multiple charts of accounts and different structures of accounts across departments and legal entities
99 Ability to support multiple charts for organizational units within the system
100
Ability to "roll up" detail G/L accounts into a "summary" G/L account automatically via multiple hierarchical structure relationships (e.g. unit income/expense accounts will "roll up" into a departmental revenue/expenditure summary control account)
101 Ability to segregate/identify revenues and expenses (e.g. products, department, branch, region)
102 Ability to add to or modify accounts and easily specify the account's relationship within various reporting hierarchies at the same time
103 Ability to maintain balances for statistical information (e.g. headcount, currency rates)
104 Ability to maintain average balances in original, reporting and functional currencies
105 Ability to support consolidation between subsidiary companies with similar/dissimilar charts of accounts
Page 37 of 165
106 Ability to maintain and report on historical, current, and future period balances for the following data types:
107 - Monetary
108 - Statistical
109 Ability to accept and process prior, current and future date journal entries based on user-defined control parameters
110 Ability to allow specification of the following dates on a journal entry:
111 - Activity date- Transaction date
112 Ability to accept credits and debits
113 Ability to support reversal of transactions via automatic journals or via credit notes for invoices.
114 Ability to allow processing of multiple entities in a single posting (i.e. inter branch and intercompany)
115 Ability to provide the ability to post journals on-line, real-time or batch
116 Ability to support standing and recurring entries with fixed, variable and mixed amounts (e.g. depreciation, prepayment)
117 Ability to support the entry of accruals
118 Ability to allow the user to specify the release date for recurring and/or reversing accrual entries
119 Ability to provide a reference number (i.e. audit trail) of all journal entries including the journal source, operator ID and voucher/check number, if applicable:
120 - On-Line – upon transaction
121 - Automatically by the General Ledger (e.g. Reversals and Recurring Entries)
122 - By Feeder Systems e.g. Reuters
123 - Through PC Uploads
124 Ability to reverse the effect of processing a duplicate general ledger posting with full audit trail reporting
125
Ability to post prior period adjustments which automatically adjust the ending balance in an account for the prior period and the corresponding beginning balance in the current period
126 Ability to perform fixed and variable cost allocations
127 Ability to provide on-line, real-time, full-screen editing and posting of journal entries
128 Ability to perform validation of accounts entered through on-line and batch journals
129 Ability to permit edit of fields on prior screens during input of multi-screen journal entries
130 Ability to restrict designated journals from posting to accounts (e.g. with long inactive period - dormant accounts)
131 Ability to perform all validations on a transaction at the same time regardless of the number of errors
Page 38 of 165
detected
132 Ability to balance journals in original currency
133 Ability to balance transaction totals to journal control totals on a total debit and credit basis
134 Ability to provide user-defined methods of error handling for incorrect and out-of-balance journals including the facility to correct errors on-line
135 Ability to include features that will automatically release and re-validate a batch or entry from the holding files after corrections have been made
136 Ability to perform edit/validation tests at input screens
137 Ability to maintain/correct detail suspense account entries on-line or in a batch mode
138 Ability to highlight invalid journal entries on-line or in batch mode
139 Ability to provide reconciliation between sub-ledger systems and the general ledger
140 Ability to produce a report displaying standard monthly journal entries expected but not posted during the current month
141 Ability to perform translation of foreign currency transactions on-line
142 Ability to support flexible accounting calendar that allows user to define multiple overlapping periods (e.g. month, quarter, half-year)
143 Allows automatic posting of profit-after-tax to statutory reserve based on user defined criteria
144 Ability to allow P&L to be closed out to retained earnings based on user specifications
145 Ability to support preliminary and final closing of P&L
146 Ability to permit closing of the current accounting period on any user-selected date
147 Ability to provide flexible month end cut-off dates for independent legal entities to support various (e.g. local, regulatory) reporting requirements
148 Ability to allow simultaneous posting to and reporting from current and future periods
149 Ability to maintain current and prior period ending dates independent of the system date
150 Ability to ensure that no entries remain un-posted in holding files at the time of closing
151 Provide the ability to close the current accounting period for a legal entity independent of the closing date for other legal entities on the system
152 Ability to allow each entity to establish its own accounting calendar and posting schedule
153 Ability to allow legal entities to report for various fiscal year-ends
Page 39 of 165
154 Ability to establish independent accounting periods and fiscal years for each unique entity
155 Ability to utilize an optional free-form reference or description field for each journal line entry and inquire/report on this field
156 Ability to ensure the narrative fields for account name and transaction description is at least 80 characters wide
157 Ability to balance on-line and batch journals before they are accepted for posting
158 Ability to maintain balances in the original transaction currency
159
Ability to support multiple base currencies. Please advise the limit. This is to allow processing of separate legal entities in a hub or regional processing center using the same resources.
160 Ability to support definable currency table (parameter)
161 Ability to provide facility to generate balance sheet and income statements in original and functional currencies for all views
162 Ability to accept journals in both originating and functional currency
163 Ability to accept local currency and functional equivalent currency journal entries from interfacing systems
164 Ability to convert local currency to functional equivalent currency within the G/L
165 Ability to provide reconciling controls between local and equivalent currency journal transactions
166 Ability to support a variety of rate tables including average, spot, month-end, forward, historical
167 Ability to access historical exchange rates based on activity date of posting
168 Ability to do automatic calculation using conversion amounts
169 Ability to allow the use of multiple functional currencies across different entities
170 Ability to calculate for specified periods, gains/(losses) into the functional currency based on the net asset/liability balance of the original currency
171 Ability to translate/restate financial results on a legal entity basis reflecting translation from the functional currency to multiple reporting currencies
172 Ability to allow each legal entity located in different countries to use different foreign exchange rates
173 Ability to calculate average foreign exchange rates
174 Ability to override pre-defined exchange on journal transactions
175 Ability to round off foreign conversion calculations
Page 40 of 165
176 Ability to accept exchange rate information from subscription services several times per day
177 Ability to support multi-company’s and consolidate group reporting.
178 Ability to summarize GLs into cost centers
179 Ability to create accounting and GL structures
180 Ability of the system to round off a posting with odd cents to the relevant decimal place
181 Ability of the system to link postings into sub ledgers into GL entries
182 Ability of the system to automate standard regulatory reports
183 Ability of the system to handle multiple transaction
184 Ability to check for duplicate accounts on time of account creation
185
Ability for the user to have full control over the opening and closing of accounting periods, with the ability to reopen closed periods if necessary with all the necessary controls and approvals. This ability will extend beyond the boundaries of any one financial year
186 Ability for the system to allow the roll forward of data set period closing balances into the new period opening balances (where applicable)
187 Ability to do profitability analysis by region, country, product, transaction, customer and account level
188 Ability to build expense allocation at transaction processing level
189
Ability for the system to have an expense processing module linked to customer account, business unit, cost centers and profit centers (ability to build a true customer profitability analysis tool)
190 Ability to support project accounting
191 Ability to measure key productivity indicators as listed below:
192 - Transactions per processor and Authorizers (Volumes)
193 - Transactions turn-around time based on time stamps in the system.
194 - Transactions processing and authorization times
195 - Errors and reversals
196 - Transaction peak times and service demand curves
197 Ability of the system to support import and export of data in various formats including Excel
198 Ability of the system to support mass account maintenance where changes or edits need to be done to multiple accounts at once.
Month and Year End Closing
199 Ability of the system to support generation of reports prior to or after any final closing routine
Page 41 of 165
200 Ability of the system to maintain account balances by:
201 - Year to date
202 - Period by period
203 Ability of the system to maintain prior year balances by:
204 - Year to date
205 - Period by period
206 Ability of the system to facilitate user-defined periods
207 Ability of the system to facilitate user-defined batches for month-end reports.
208 Ability of the system to facilitate automatic notification of unprinted reports (i.e. journals not printed before posting)
209 Ability of the system to freeze current point in time for reporting
210 Ability of the system to provide access to multiple years
211 Ability of the system to allow selected users to reopen a period to make adjustments
212 Ability of the system to automate the movement of balances from current to historical data set
213 Ability of the system to system should automatically reset itself for the next accounting period / year
214
Ability of the system to allow the processing of budget, routine inputs and journal transactions for the next accounting year while the current year is being finalized
Budgeting
215 Ability of the system to allow users to capture their budget vote details such as item name, amount etc.
216 Ability of the system to compile and add the total budget for all users in each department.
217 Ability of the system to allow divisional heads to review budget of their departments.
218 Ability of the system to compile the list of all departments into a single company budget.
219 Ability of the system to allow the Finance Director to review budgets of all departments.
220 Ability of the system to notify users once the budgets have been approved or revised.
221
Ability of the system to compare the budgets against actual at any time of the year (form company, divisional, department and individual staff level) specified and generate a variance analysis.
222 Ability to base the current year’s budget on the previous year.
223 Ability to prompt for reviews especially when budget is exceeded.
224 Ability of the system to scenario simulation in budgeting (sensitivity analysis)- (What if analysis).
Page 42 of 165
225 Ability of the system to allow divisions to compile their budgets
226 Ability of the system to compile a summary of all budget lines into a single company budget
227 Ability of the system to allow departments to requisition items based on the budget
228
Ability of the system to support bottom up and top down budgeting. If the consolidated budget is reduced by a certain percentage, the system should be able to revise the constituent votes budgets by a similar percentage.
229 Ability of the system to support budget forecasts.
230 Ability of the system to support product and project budgets
Accounts payable
231 Ability of the system to interface with the partner's online portal to allow suppliers to submit their invoices remotely.
232 Ability of the accounts payable module to receive data from the various core business systems and to consolidate all payables in the ledger.
233
Ability of the accounts payable module to update the various core business systems once payments have been made on payables generated from the core systems.
234
Ability of the system to prompt the Finance Department to process payment once supplier invoices have been approved by the respective departmental heads.
235 Ability of the system to calculate all payable taxes and other relevant charges.
236 Ability of the system to incorporate the payment authority matrix and prompt for review and approval of a payment.
237 Ability of the system to post transactions in the relevant ledgers.
238 Ability of the system to prompt finance to prepare payment once approval has been done.
239 Ability of the system to prompt the relevant department once approval has been done.
240 Ability of the system to send an alert and escalate if processing has not been done within the set period.
241 Ability of the system to alert finance to disburse payments once approved.
242 Ability of the system to alerts users once payment is made advising them on the remaining budget amount.
243 Ability to generate payment remittance statements.
244 Ability to generate report on payment instructions.
245 Ability of the system to process credit notes.
Page 43 of 165
246 Ability of the system to confirm that all transactions posted are within set budgets for specific cost centers or initiate a work flow to override.
247 Ability of the system to allow payments to be prioritized as low, medium and high urgency.
248
Ability of the system to track the execution of prioritized payments, monitor the duration it takes to affect the payment and raise alerts if urgent payments are delayed.
249 Ability of the system to support flexible discount rules
250 Ability of the system to support unlimited vendors and vendor categories
251 Ability of the system to support the creation of unlimited banks and bank accounts
252 Ability of the system to enforce matching of documents from purchase requisition, purchase order, goods received note, invoice and supplier payment.
253 Allow for intercompany allocation of expenses incurred by one company on behalf of another company in the Group.
254 Ability of the systems to track the location of dispatch of cheques e.g. capture name of branch a cheque has been dispatched to.
255
Ability of the system to track the duration between when cheques are dispatched and when they are collected, and to alert where the cheques have not been collected within a defined number of days.
Accounts Receivable
256. Manage Receivable processing
257. Manage incoming payments
258. Manage dishonored cheque Processing
259. Ability to capture Patient BIO Data
260. Allow capture of Contact Information
261. Enable capture of Emergency Contact Information
262. Provide the ability to use Biometric data to access patient data
263. Provide the ability to use Biometric data to determine who was holding the biometric scanner when the biometric data was accessed
264. Integration with 3rd Party validation systems (e.g. Police) to ensure biometric data provided matches known identities of individuals
265. Integration to NHIF to validate insurance Information in Realtime
266. Integration to MPesa for Realtime billing processing
Page 44 of 165
267. Provide a platform for Banks direct deposit
268. Enable Doctor Assignment during registration and view of doctor appointment calendar
269. Customizable Bill Settlement services
270. Provide the ability to track patient visits and medical history
271. Allow the ability to view patient prescription history
272. Integration with 3rd Party Insurance Platforms for real-time Insurance validation
273. Integration with Finance systems to provide real-time financial transaction data
274. Provide queue management solution that is visible to both patients and clinical staff.
275. Provide Realtime Outpatient management reporting customizable by job function or role.
276. Enable customizable Vital signs observation templates for Nurse triage
277. Enable customizable Chief complaint observation templates for Doctor triage
278. Provide the ability for Nurses to enter and modify biomedical information including Immunizations, Allergies and all other clinical observations
279. Enable automatic tracking and logging of access to patient files
280. Provide a Color-Coded System to track priority cases
281. Enable to automatic addition of ICD-10 Diagnostics codes
282. Provide audit trails of all inputs and access to the outpatient management solution
283. Ability to create customizable workflow management for routine tasks
284. The solution should provide auto alerts whenever the patient file is accessed highlighting Allergies, surgeries, etc. that will impact patient care process
285. Enable Doctor Assignment during registration and view of doctor appointment calendar
286. Customizable Bill Settlement services
287. Provide Realtime Outpatient management reporting customizable by job function or role.
288. Enable customizable Vital signs observation templates for Nurse triage
Page 45 of 165
289. Enable customizable Chief complaint observation templates for Doctor triage
290. Provide the ability for Nurses to enter and modify biomedical information including Immunizations, Allergies and all other clinical observations
291. Enable automatic tracking and logging of access to patient files
292. Provide a Color-Coded System to track priority cases
293. Enable to automatic addition of ICD-10 Diagnostics codes
294. Provide audit trails of all inputs and access to the outpatient management solution
295. Ability to create customizable workflow management for routine tasks
296. The solution should provide auto alerts whenever the patient file is accessed highlighting Allergies, surgeries, etc. that will impact patient care process
297. Provide the ability to Assign patients to specific Bed locations
298. Enable to ability to track Bed Transfer
299. Provide the ability to view a quick view of patients in specify beds
300. Provide the ability to track drugs and mediations given to patients and by whom
301. Provide the ability to create define a Treatment management Plan with Medication and Activity tracking
302. Ability to request Drug prescriptions from the Pharmacy, track usage and return surplus supplies back to the Pharmacy
303. Provide solution to track Nurse and doctor visits to patient
304. Ability to request blood supplies
305. Solution to Discharge a patient and create follow appointments or procedures based on Discharge Summary
Stores/Inventory Management – Supply Chain
307. The system should be able to do Items master Creation and controls
308. The system shall maintain a detailed item master information
309. The system shall generate a defined alpha numeric Item codes for all Inventories e.g. Drugs, medical Supplies
310. The system shall support unlimited inventory item types/groups e.g. Stationery, spare parts, service items etc.
Page 46 of 165
311.
The system shall allow multiple segmenting of item types; such as Stationery can be segmented into; Drugs, Paper, Pens etc.; Pens can also be further segmented into BIC pens, Nice etc.
312. The system shall allow multiple suppliers' information for individual and item types/groups
313. The system shall identify alternate/substitute items for the item / product
314.
The system shall create items with attributes that support Inventory, Issue, Projects, Contracts, Maintenance and Purchasing modules of the application
315. The system shall support multi-sites functionality for items stored at defined sites
316. The system shall Handle specific labeling requirements, packaging requirements
317. The system shall track inventory by Departments and Pharmacies etc.
318. The system shall Handle both stock and non-stock items as well as assemblies e.g. Medical Drugs vs. Keyboard.
319. The System shall generate alphanumeric/barcoding system
320. The System shall allow auto generation of multiple barcodes based on a user defined criterion
321. The System shall Printing barcodes on documents, labels, stickers
322. The system shall barcode scanning including using stationery and handheld devices
323. The system shall maintain product information using different product dimensions such as name, code, UOM, serial number etc.
324. The system shall maintain Reorder levels, EOQs
325. The system shall allow Conversion factor between Purchase Unit of Measure & Inventory Unit of Measure
326. The system shall provide Multiple UOM conversion tables
327. The system shall maintain item warranty status, period etc.
365.
The system shall be able to define technical specifications for the items with different Spec. attributes (width, length), form, diameter, shape, grade, etc.).
328. The system shall be able to maintain the minimum, maximum, re-order stock levels on: Item /group level
329.
The system shall provide real time alerts on the Item / Product to be replenished / transferred for the Item / Product below the pre-defined minimum levels
Page 47 of 165
330. The system shall provide to insure the inventory at the desired level, and as stock varies, the insurance value should be adjusted
331. The system shall define valuable methods; Weighted Average, Standard Cost, FIFO (first in first out),
332.
The system shall be able to value / cost the stock Item / Product across all locations, (i.e., have one cost pool. For example, Item / Product A should carry the same cost in all locations)
333. The system shall be able to allocate different costs at different locations
334. The system shall be able to enter the cost of returned used items
335. Ability to revalue inventory cost based on a user-defined mark-UP/down percentage or fixed value per category/Product
336.
System should have the facility to compute WIP (work in process) costs based on the quantity of items issued and the percentage of process completed at a given point in time.
337. The System shall allow Transfer of stock Items across groups/ categories
338. The system shall generate Stock transfer requests
339. The system shall route requests for appropriate approvals
340. The system shall process inventory transfers between warehouse locations, bins/shelves.
341. Ability to show stock in transit until received at destination
342. Maintain Max, Min & Re-order levels by location
343. Ability to generate weekly stock requirements list based on the following:
344. On Hand Quantity
345. On Order/In Transit Quantity
346. Min-Stock Level
347. Stock requirement for a period
348. Average Sales (Issue) for past 6 month
349. Month-to-date sales (Issue)
350.
Ability to generate system alerts on need to transfer stock from one location to another (e.g., if stock of an Item / Product is below minimum level in one location and stock of the same Item / Product is above re-order level in another location, system should automatically alert users to transfer from the latter location to the former)
Inventory Receipt, Issue & Reporting
351. Provide a complete integration with the Purchasing and Accounts payable module
Page 48 of 165
352. View all issued POs by suppliers and due dates
353. Receive stock based on only approved POs
354. Allow issue of multiple GRNs for multiple PO lines
355. Restrict receiving items beyond PO line quantities
356. Allow both full and partial receipts of PO lines
357. Allow creating a conformity checklist for inspection of items delivered for quality and quantity
358. Generate good inspection requests/warrants and distribute among defined user department inspection team.
359. Generate a Good Received Note with ability to match with inspection warrants
360. Record the purchase price / unit cost of all items received for each consignment as per the PO lines.
361. Allow attachment of signed inspection reports to support the GRN
362. Allow auto update of inventory master with all the goods received details on generation of GRN
363. Allow auto update of asset master with all the goods received details on generation of GRN
364. Allow auto generated, serialized GRN and provide for printing of GRN on pre-numbered accountable stationery.
365. The system shall Issue Stock based on approved stores requisition orders
366.
Ability to pick and dispatch Item / Products based on internal requests and track the following: Internal request number/SRO number, Requester, Item issued by lot no or batch no. or serial number
367. Reservation based on picking methods
368. Provide for printing of Goods issue notes on pre-numbered accountable stationery
369. Ability to issue stock with ability to identify the recipient order number for tracking and reporting.
370. Receive Items into stock, Directly into the stock, To Quality Control, Transit
371. Item received by lot no or batch no. or serial number
372. Automatic consideration of deliveries as complete when they are within a certain quantity tolerance
373. Ability to receive samples and track it and pay for their freight
374. Automatic allocation of inventory to backorders
375. Reallocation of reserved inventory across orders
376. Flagging of items below reorder points when allocated
377. Returned inventory management
378. The system should provide Stock count
Page 49 of 165
379. Define stock count cycle
380. Ability to define the cycle count per Item / Product or product category
381. Ability to allow Freeze the issue or receive of items during Counting Process
382.
Ability to generate count sheets based on user defined criteria: Quantity, (e.g., include Item / Products with quantity above xx pieces), Value, (e.g., include the Item / Products with unit value above certain value.) Item / Product Groups, Location, User defined fields, On a random Basis
383. Ability to sort the count sheets by: Item / Product, Locator/ bin number
384. Ability to count item / product using barcode scanning
385. Ability to process physical count adjustments
386. Ability to enter the physical count results with a different unit of measure from the Item / Product's stocking unit of measure
387. Route physical count adjustments for proper approvals prior to committing them to the system
388. Ability to identify the type of physical count adjustments as: Shortage, Damaged, Expired, Excess
389. Follow the prescribed write off / loss recording procedure, for all store’s shortages discovered during the physical count, or at any other time
390. Ability to identify the non-usable / non-sellable quantities as part of the physical count adjustment
391. Monitor stock status and availability
392. Ability to inquire on an item / group that has different product codes by conducting one search (The system should then show the available quantity by code number)
393. Ability to inquire on-line about the stock availability at various stock locations from any other location.
394. Ability to inquire on-line about the stock availability grouped by multiple locations.
395. Reports
396. Ability to report and inquire on the stock status at any date (historical or future) on Item / Product level and show the following information:
397. Stock position by location, (e.g., on hand, on purchase requisitions, on purchase orders.), Year to date issues Month to date issues
398. Ability to generate all inventory reports based on the user defined Item / Product and location groups
399. Report on all new items that are added in a certain period
Page 50 of 165
400. Ability to report on Stock value by location, Item / Product group and user defined groups
401. Ability to search by attribute for items, equipment and locations.
402. Item-wise cost comparison
403. Monitor fast- and slow-moving Item / Products
404. Ability to inquire / report on the slow- and fast-moving Item based on user defined criteria as follows: Location, Total issues, Number of issue transactions, Range of dates, Last issue transaction date, Product Cost/Value of stock
405. Ability to grade items by A, B, C categories.
406. Ability to categorize these Item / Products by percentage of issue
407. Ability to re-evaluate and regroup Item / Products based on top issue categories
408. Monitor the stock aging
409. Ability to generate stock aging analysis based on the receipt date
410. Ability to track the source document, (e.g., GRN - good received note- and voucher number) for each item or group of items
411. Report on Inventory Days
412. Monitor stock expiry status (for Lot controlled Items)
413. Stock holding enquiry
414.
Ability to inquire / report on the existing physical stock by product, manufactured date and expiry date to enable early tracking of the Products that will age/expire for liquidation management, (e.g., distribution before they expire)
415. Ability to generate Item / Product labels, including Item / Product code and Bar Code
416.
Ability to report on the transaction statistics by type (e.g., number of receipt transactions, shipments, transfers, returns, etc...) by Item / Product group and month
417. Report of historic material price movement, supplier wise comparison, and credit period.
418. Stock balance report by stores
419. Consolidated stock balances report for a group of stores
420. Detailed stock balances report
421. Stock movement report
422. Stock count sheets
423. Stock aging report
424. Damaged stock Report
425. issue orders with allocated / reserved stock
Page 51 of 165
426. Nonmoving Item / Products by category (Item / Products with no disbursement activities for the past 12 months)
427. Adjustment transactions report on stock
428. Returned Item / Products report
429. Access material forecasting and item availability information
430. Identify out of stock items or make substitutions with alternate parts, vendor, and location tracking capabilities
431. Access latest cost information and item levels instantly
Procurement
432. System must be able to maintain approved supplier lists by item.
433. System must support user-defined approved supplier status, which include business rules and restrictions.
434. The system shall restrict purchasing from un-approved supplier. However, this restriction shall not be limited to manager level.
435. System shall be able to maintain records of bid bonds, performance bonds, bank guarantee drawn in favor of Kenyatta National Hospital
436. The system shall alert the users about the validity / expiry of bid bonds, performance bonds and bank guarantee one month before its expiry.
437. The System shall be such that it shall be able to report the procurements made during a given date range.
Purchase Requisitions:
438. The system must be able to support manual purchase requisitions (PR) creation.
439. The system must be able to support automatic PR generation based on inventory replenishment recommendation.
440. The system must be able to have manual purchase order (PO) generation from PR.
441. The system must be able to tie PR number to PO and allow:
442. - PO search by PR number
443. - PR search by PO number
444. The system must be able to support requisition tracking and inquiry, and to alert Purchase department on the PR that shall be reviewed and processed.
Page 52 of 165
445. The system must allow users to combine multiple PR’s into one PO.
446. The system shall allow users to split one PR into multiple PO's.
447. The system must be able to source requisitions automatically from agreements and catalogs using approved supplier lists.
448. The system must be capable of distributing expenses across multiple cost centers, projects or departments.
449. The system must support multi-currencies.
Quotations:
450. Users must be able to generate request for quotation (RFQ) to be sent to suppliers.
451. The system must be able to track supplier response to RFQ.
452. The system must be able to support supplier quotation maintenance and inquiry.
453. The system must be able to support multiple price breaks.
454. Users shall be able to attach standard text document (e.g. terms and conditions) on all RFQ’s.
455. Users must be able to create, and update quotations based on supplier response.
456. The system shall alert users to review quotations that are going to expire in a certain time frame.
457. Price and discount table corresponds to individual suppliers and items
458. Automatic update of an item's record based on the item's most recent purchase price
459. Orders may be discounted manually or automatically based on the order line
460. Price adjustments such as quantity discounts are determined from a grade table
461. Pricing and discounting tables include effectivity dates
462. Automatically updates prices and discounts based on a percentage or fixed amount
463. Price rounding determined by established rates
464. Calculates PO price by searching price tables
465. POs may be generated in any currency
466. Suppliers may be chosen manually on the basis of best pricing or discounting
467. Users can manually enter requisitions, which update along with automatic entries
468. Procurement system allows multiple line items and delivery schedules
469. Quality codes included on purchase requisitions
470. Requisitions can be approved in real time
Page 53 of 165
471. Processes requests for quotation (RFQ)
472. Manage and update supplier's quotes for particular items
473. Purchase requisition reference to project, account, program, contract, and sales order
474. Quotation copies maintained for suppliers
475. Returned/awarded quote information (quote effectivity range, lead item, and minimum lots)
476. Manages supplier quotation file by item or product with purging based on user-defined criteria (for example, date)
477. Displays planned purchase orders
478. Support competitive quoting
479. Retain requisition history
480. Displays of planned purchase orders can be viewed grouped by style or style/option
481. Planned purchase orders can be changed and released at grouped levels of style or style/option
Purchase Order Creation and Maintenance:
482. The system must provide PO maintenance and inquiry functions to add, change, delete and list PO.
483. Users must be able to locate existing suppliers through flexible search facility during PO creation, maintenance and inquiry by:
- Supplier code
- Supplier name
- Contract no./PAN
- Others (as specified)
484.
Once a purchase order is confirmed, any further changes to the PO will create a PO new revision. The system shall provide a facility to track multiple revisions of the same PO.
485. Re-approval is required whenever a new PO revision is created.
486. The system must be able to control the approvals by amount, cost center, budget, account, item, category, Account code number and location.
487. Users shall be able to create the PO manually.
488. System shall support consolidate and centralize purchase requirements from multiple warehouses or locations or accounting centers.
489. There shall be facilities for users to inquiry all outstanding PO’s items by:
- PO number
- PR number
- PO number showing the status of PO
- Item/Part number
Page 54 of 165
- Item/Part category
- Due Date
- Supplier's name
- Others (as specified)
490. The system must be able to support blanket order (that is, an agreement to buy certain items at a predefined price over a certain period).
491. The system must have a facility to terminate a blanket order.
492. Users must be able to assign primary/preferred supplier for each item.
493. The system must have a facility to put a supplier on hold by:
494. - Prohibit the release of PO’s for the supplier
495. - Putting a specific item/supplier combination on hold
496. The users must be able to define multiple suppliers per item/part.
497. Users must be able to generate PO’s in multiple currencies.
498. User must have the option to store standard notes relating to items and/or suppliers to be displayed and/ or printed on PO.
499. Users must be able to define receiving early/late tolerances for each item/part.
500. The system must provide the option to prohibit it or issue a warning when a receipt violates such tolerances.
501. The system must be able to track the purchase price history.
502. Ability to customize the Purchase Order Summary screen to meet the users need.
503. MRP requisition converts to a purchase order
504. Conversion of a planned purchase order to a PO electronically forwarded to vendor automatically
505. Manually enter and send purchase order
506. Assigns sequential PO numbers automatically
507. Purchase order types including standard PO, blanket/contract, subcontract order/operation, purchase request, and return-from-stock
508. Purchase orders for miscellaneous (non-inventoried) items "Fast Path"
509. Quotation entry includes data fields for effectivity dates, and pricing discounts and percentages
510. POs include the vendor's quotation number
511. Quality codes included on purchase orders
512. Flow down of project or part notes to PO
Page 55 of 165
513. Vendor selection algorithm based on lowest price quote, strong delivery time, or preferred source status
514. Supplier and item data may set as defaults upon placing POs
515. Overrides default data with user-defined data by order
516. Order link to financial company for vendor selection
517. Orders and suppliers link to the financial company, which links to the warehouse for transactions
518. Control of default order type, order series, and warehouse code
519. Matrix of vendors, by item, approved as alternate suppliers
520. Contract and project number line item
521. Order line and customer order line split for multiple deliveries
522. Individual POs can handle more than one item
523. Codes for multiple deliveries of a specific item in a PO (may accommodate more than one date or location)
524. Purchase quantity includes the measurement unit and conversion (for example, "meter" or "piece")
525. System's item file correlates vendor part numbers to internal part numbers
526. System's item file maintains preferred vendors for specific parts as indicated by vendor number
527. Subcontracted purchase orders tied to work order operation; material supplied by either vendor or internal operation
528. Parts, supplies, and services purchases
529. Drop-ship, direct shipments, special order transit options traceable by serial number
530. Ship a complete order or portions of an incomplete order
531. Non-receivable items; No receipt expected
532. Maintains purchasing conditions for specific order items (e.g., seasonal or promotional items)
533. Selected items in an order may be flagged for defect checking
534. Notes for internal purposes may be excluded from printing or printed when they're intended for external display.
535. PO line item comments may be entered in a user-defined or standard predefined format
536. Line-item-specific delivery dates
537. Automatically calculates delivery times and dates
538. Purchase history is accessible in real time by supplier or part
Page 56 of 165
539. Cost tables and codes may be parameterized by supplier groups, individual suppliers, or companies
540. System-generated POs may be routed for online review and approval
541. Users control text entry and display formats
542. POs may be coded by their status as communicated by the MRP system. Codes should include planned, firm planned, and requisitioned
543. Purchase order line status includes released and closed indications
544. Purchase order status and confirmation notes on the product and supplier
545. Automatic system messages to follow up POs may be triggered by user-specified criteria
546. Confirms POs by product numbers or PO number
547. POs may be associated with contracts that require lot traceability
548. Automatically flags past due deliveries and supports inquiries on future deliveries
549.
Provision to track non-recurring charges associated with a line item of a purchase order, such as tooling or setup charges. Should be connected to the line item, but separately identifiable and reportable
550. Automatically generate a PO number and assign it for each PO sequence
551. Workflow management: on-line approvals
552. Supports purchase card activity
553. Rules based automatic on-line notification of engineering change number (ECN) activity
554. Option to automatically create and maintain sub-contracted POs upon creation of sub-contracted work order operations
555. Option to automatically close a sub-contracted work order upon receipt of associated sub-contracted PO
556. Allow multiple buyers to procure same item for separate business units
557. Manual entry of POs in matrix (grid) formatting style.
558. Purchase order details can be viewed grouped by style or style/option
559. Purchase order confirmations and shipment advice can be entered at style or style/option level
560. Attaching purchase orders to a letter of credit
561. Controls
562. Vendor
563. Specific Requirements
564. Multiple Tasks
Page 57 of 165
565. Vendor selection algorithm based on lowest price quote, strong delivery time, or preferred source status/ specification
566. Order link to financial company for vendor selection (Donor funds)
567. Orders and suppliers link to the financial company, which links to the warehouse for transactions (Donor funds)
568. Categorizes POs by single; recurring; maintenance, repair, and operations supplies; specific project; or job-triggered orders
569. Individual components may be divided for multiple lead times, including categories such as dock-to-stock and preparation lead times
570. Entities within a company link to a common legal entity (for example, business units, plants, sites, etc.)
571. Consolidates enterprise-wide purchasing as a central unit
572. Products classified within a purchase class default to a main vendor
573. Verifies (and holds if necessary) receiving transactions on the basis of controls defined during purchasing
574. Internal processing lead times provided based on products and warehouses
575. Retain PO data for audit purposes (PO with electronic approval)
576. Determines product availability by subtracting outgoing orders from incoming receipts
577. Forecasts the product reorder date (determined by stock estimates)
578. Purchase suggestion field contains products identified from available stock or reorder points
579. Additional orders may be generated to designate special order characteristics
580. Users may issue stock replenishment orders based on predefined terms
581. Calculates ABC classification (items categorized based on usage per year)
582. Identification codes for purchasing agents sorted by warehouse or other method
583. History of POS
584. Interface provides buyers with important purchasing criteria factors
585. Maintains PO history information by item
586. Users may maintain purchasing files from any terminal, PC, or workstation
587. Analyzes purchase statistics based on user-defined criteria
Page 58 of 165
588. In-depth reports on purchasing statistics defined by specific parameters
589. Determines, measures, and reports statistics for purchase budgets
590. Compares budgets
591. Users may authorize supplier invoices on the basis of packaging slips or line level
592. Reports shortages and schedule information to suppliers in real time
593. Tracks consigned inventory, in real time, to include inventory segregation and payment control
594. Online tracking of PO maintenance history
595. Controls
596. Order Management
597. Goods Receipt:
598. The system must provide on-line PO receipt transaction and automatic update of stock balance and PO status on receipt of items.
599. The system shall be able to keep track of lot and serial number during receiving.
600. There must be a facility to handle material rejects after inspection and reflect on the PO as outstanding quantity.
601. Ability to view expected receipts by promised date and the viewing of complete receiving history.
ASSET MANAGEMENT
602. Create and classify enterprise assets
603. Manage enterprise asset register
604.
Track enterprise assets (from fixed assets to movable assets, line assets (equipment, accessories), etc.), including location, status, ownership/assignee and maintenance responsibility, insurance, transfers and deactivation
605. Certification of physical inventory for locations
606. Manage asset conditions (condition analysis, root cause analysis of failures, probability of failure, criticality of the failure, etc.)
607. Track asset insurance values (replacement values)
608. Manage spares for each asset and assessment of spares requirement
609. Identify assets that have been missed and not updated by the physical inventory process (missing, lost, stolen, destroyed, etc.)
Page 59 of 165
610. Manage and track leased assets
611.
Generate management reports detailing cost of new assets acquired to replace an asset lost, missing, stolen, or destroyed; and insurance reporting for risk management
612.
Manage integration to relevant modules for effective management of enterprise assets, including Graphical Information Systems (GIS) to leverage geospatial data in the analysis of asset status
613.
Prioritize asset classes and assets according to criticality ranking by failure probability and consequence criteria chosen such as frequency of failures, availability, throughput, etc.
614. Manage enterprise asset reporting
615. Creation of commercial leases both as landlord and tenant e.g. Lease ending dates, rent escalations clauses, etc.
616. Space Management
617. Availability Management
Human Resource Technical Requirements
Item Mandatory Requirements Compliant
(Y/N) Detailed explanation with Cross-reference evidence
Employee Master Record and Maintenance
618. The system should enable Kenyatta National Hospital in Employees and Applicants Number’s Auto generation
619.
The system should be able to capture all the employee info. The basic data of an employee consists of, but is not limited to the following:
620. Employee Number
621. Employee Full Name
622. Employee Short Name (for use in search criteria)
623. Date of Birth
624. Gender
625. Spouse
626. Dependants
627. Original Employment Date
628. Employees Job Group
629. Employees Role and Position
630. Designation and Description
Page 60 of 165
631. Contract type
632. Contract Expiry Date
633. Department
634. Section/ Division
635. Work Location
636. Cost Center
637. Employment Status
638. Termination Date
639. Termination Cause (Code)
640. Address
641. Emergency/ Leave contact address
642. Banking details
643. Bank Account
644. Passport number/ID number
645. Labour card number
646. Driving License details
647. Capture assets linked to employee
648. Employee Salary's Currency
649. Acceptance of unlimited number of dependents details:
650. Dependent Name
651. Gender
652. Date of Birth
653. Relationship
654. Marital Status
655. Persons Photograph as Image (when required)
656. Dependents Data Actions:
657. Maintain Dependent’s data (spouse(s) and children)
658.
Validate any entitlements such as Educational Assistance, Housing Allowance, Leave Transportation, Child Allowance, etc., based on the dependents data available on the system.
659.
In case of any change in the number of dependents, generate necessary transactions to effect the change in entitlements,
660. Follow-up employee’s marital status and continuous eligibility of dependents
661. Maintenanceof multiple employee address and contact details.
662. Capturing data pertaining to: Visas, Labour Contracts, Passport, Driving License, etc.
Page 61 of 165
663. The proposed system should maintain details of any offence committed by the employee as below
664. Date of offence
665. Description of offence
666. Disciplinary action taken
667. Number of days of suspension
668. Keep a full record of all changes to Employee data.
669. The system should support attachment of employee picture.
670. The system should support attachment of passport copy or any other relevant document.
671. The system should support monitoring expiry dates / renewals and flag expired ones.
672. The system should support Tracking pre-employment history of the hospital employees
673.
The system should support tracking of each employee’s history right from hiring, grades, job assignment, probation/confirmation, transfer, promotions, salary/ benefits changes (including reasons/background), rewards, recognition, warning, grievances, disciplinary action, etc. till the employee leaves the enterprise. (Including reasons for leaving to analyse turnover).
674. The system should support protecting employee history from unintentional deletion
675. The system should support providing protection from setting up duplicate employee records
676.
The system should support linking of employee records with positions within the overall organization must be possible
677.
The system should support providing the ability to record contract type – permanent, temporary, casual and others
678.
The system should support triggering notifications which pass user-definable data items via email, distribution/work lists or online notifications. Event triggers to be end-user definable at the solution layer without requiring the
Page 62 of 165
configuration of database triggers
679.
The system should support allowing for termination of employee record at the end of the employment period without deletion.
680. Termination of the employee against one position whilst remaining employed against other positions
681.
The system should support Providing facilities to record skill components / competencies in each job description.
682. Providing an automated applicant tracking of new employees
683. Tracking internal job transfer candidates
684. The system should support Maintenance of changes in employee status data
685. The system should support adding additional Comments on the employee data
686. Providing centralized or decentralized data entry, or both as required
687.
Providing functionality on the company Intranet (e.g., adding, changing, and deleting employees; basic query and reporting capabilities, viewing of screens, forms, etc.)
688. Providing automatic interface to external modules that share the same information
689.
The system should support maintenance of information related to promotions, demotions and transfers
690.
The system should enable Kenyatta National Hospital in Handling historical information for employee activity: promotions, transfers, and salary changes.
691.
The system should display Information on how long an employee/person has held this position.
692. Assigning manager for each employee in that position.
Page 63 of 165
693.
The system should allow Kenyatta National Hospital in the capturing of employee skills, education and/or training
694.
Managing of skill data: Languages, Work History, Competencies, Ability to maintain skills inventory for employees, Certifications, Education, School/College /University Level.
695.
The system should provide a list of employees or departments information by combinations of nationalities, grades, age groups, gender, benefit types, overtime charges, salary increase or merits.
696.
The system should enable Kenyatta National Hospital to administrators/managers to perform On line approvals and updating of employee records and payroll with effective dates and tracking of these changes in a verifiable manner
697.
The system should enable the Kenyatta National Hospital to define different person types i.e. Employees, Applicants Consultants, registrars, Trainees etc.
Kenyatta National Hospital Work Structure
698.
The system should be able to capture and Reflect the Kenyatta National Hospital organization hierarchy and other position relationships in the unit/department/division.
699.
The system should allow for the defining and configuring of the reporting channels, hierarchies, organization (departments, sub divisions / divisions/ regions)
700. The system should be able to provide a graphical representation for Kenyatta National Hospital
701.
Automatic updateof the organization chart as soon as the employee status changes to show the position as vacant from the start date of deputation, study leave or separation from service by any mean.
702. The system should provide Capability to store Job descriptions.
703. Capability to store skills required for
Page 64 of 165
job a position.
704. The system should provide capability to Modify job description subject to given approvals
705. Maintaining user-defined grading scales and rates.
706. Users ability to create, edit and delete positions in the organization structure subject to given approvals
707.
Inclusion of the following data details: Code (Unit/Organization/Position); Job/Position(s); Approved Grade (Evaluated/Ranked); Job Type; Job Location; User Defined fields (No Available fields) in the Organizational position
708. Maintaining and managing competencies required for each Job/Position/Department...
709. Tracking the history of changes to the grading system as well as grade changes for all employees
710. Multiple grades within a position and ability to support identifying grades within a position
711. Automatic change to grades and associated information once the position has been changed
712. The system should provide capability to Track competencies of employees
713. The system should provide capability for Employee assignments to single or multiple jobs and grades
714.
The system should provide capability to maintain a historical record of Organizational charts as they appeared in different periods of the Organization
715. The system should provide capabilities to Handle station creation and definitions
716. Providing unique identifier for each position
717. The system should provide capability to Create any future-effective dated positions
718. Maintain job evaluation scores
719. Maintain employee career planning data
Page 65 of 165
720. Maintaining available positions, identifying authorized positions, vacant positions and filled positions
721. The system should provide capability to attach any required documents to a position record
722.
The system should provide capability to Track training needs, qualifications and certifications required for a position
Manpower Planning & Budgeting
723.
The system should enable Kenyatta National Hospital to Allocate budgeted positions for a period with start and end date. A position could be in budget for next year and it also could be for specific time period. This Facility should be available based on authority given
724. The system should provide capability to get monthly status of budgets and actual.
725. The system should provide capability to Flag deviations/shortfalls in budgeted headcount
726.
Support budget definition at the Organization, Job, Position or Grade Levels as well as a combination of criteria
727. Leave Management
728. The solution must provide leave management and recording facilities;
729.
The solution must allow recording of leave in working days and hours and forming different leave categories and types.
730. The solution must allow the definition of different sickness types and allowances.
731. The solution should facilitate the reporting and investigation of leave;
732. The solution should enable the storing and easy retrieval of sickness leave history;
733.
The solution should enable recording other reasons for leave to include extended or overseas study leave, unpaid leave, compassionate leave, dependent leave, career break and others
Page 66 of 165
734.
The solution should have self service facilities such as requesting, authorizing and recording of annual leave
735.
The solution should enable the automatic calculation of individual leave entitlements reflecting grade and employment start date if within first year of service
736.
The solution should provide the facility to attach notes of discussions/Doctor’s recommendations with employees concerning their sickness leave
Recruitment Requirements
737. The system should provide capabilities for applicants to do Online employment applications
738. The system should provide capabilities for Searching existing vacancies over the internet
739.
The system should provide capabilities for Vacancy to inherits the job objectives, accountabilities, qualifications, competencies that are stored in the job/position description, competency etc. screens.
740.
The system should provide capabilities to allow managers to raise Requisitions for vacancies to allow them to recruit
741.
The system should provide capabilities for to allow HR/Line manager to find an employee whose profile matches with the skill/competencies/qualifications specified for the vacancy
742.
The system should provide capabilities for the candidate once they apply for a particular vacancy their status will be updated to 'applied'.
743.
The system should provide capabilities for Recruitment agencies/Managers to be able to log on to the recruitment portal and enter details for potential candidates
744.
The application should Store resumes/CV's electronically and provide capabilities to search the electronic resumes based on key
Page 67 of 165
words
745.
System to provide capabilities to Retrieve suitable candidates for a vacancy using variety search methods such as key words etc.
746.
Mass update facility of applicant’s statuses (such as 1st interview to 2nd interview or transferring candidates to another manager)
747.
The system should provide capabilities for Online filtering of candidates based on their own competencies and the vacancies' requirements.
748. The system should provide capabilities for Support internal and external recruitment
749.
The system should provide capabilities for Maintaining templates for offer letters and generate contracts based on salary / grade / placement inputs. Also generating reference check letters
750.
The system should provide capabilities for automatic letter production at the various stages of the recruitment cycle must be provided
751.
Moving individuals through the recruitment cycle and of the successful candidate into the new employee processes
752. Supporting single/multiple levels of approval of the employment requisition.
753. Online tracking/monitoring of applicants through each stage of the recruitment cycle.
754. Searching for one or more applicants and then drill down into their detailed resume information.
755.
The system should provide capabilities for proposing/establishing a suitable salary offer for selected candidate based on proposed grade, position, qualification, experience, department rules and the details of interview report.
Page 68 of 165
756.
Alert generation if the necessary documents required from a successful candidate have not been received and entered in the system.
757.
The system should provide capabilities for automatic transfer of applicant’s details into employee details upon hiring.
758.
The system should provide capabilities for Execution of bulk changes/updates to applicants records in one single activity/screen.
759.
Identifying matching profiles by comparing jobs/positions required competencies to applicants' competencies.
760. ad-hoc reports
Termination of Employment
761.
The solution should allow for terminating the employee record at the conclusion of the employment period without deletion or historical records/data
762.
The system should provide a process of Terminating employment. This process should be supported by on-line security and audit trail
763.
The system should provide capability to reinstate records should termination be rescinded or individual re-employed after a break in service
764.
The solution must trigger notifications to specific Managers of the termination data (name, job title, short one-line job description, Department / Team, post location, employee number, line manager) via email, distribution/work lists or online notifications.
765.
In case of Termination of an employee the system must do an automatic notification to Pensions section, security team and other sections within Kenyatta National Hospital as appropriate to the category of employees.
766.
It should be possible to automatically generate letters upon completion of the termination process, entailing (a) the creation of an appropriate letter of termination, and (b) automatic
Page 69 of 165
notification to the appropriate manager
767.
An automatic reminder to payroll operators to check for and recover monies on termination of employment should be made during termination process
768. Training Management Requirements
769. The system should provide capabilities for Maintaining training management data requirements
770.
The system should provide capabilities for Recording competencies / mandatory training course attendance and qualification requirements by post
771. The system should provide capabilities for Recording unlimited number of training records per employee
772.
The system should provide capabilities for Booking delegates on training courses and / or open learning modules
773. On-line course solution forms and the facility to process the solution automatically.
774. Identifying and analyzing training needs (including any gaps) at individual and organizational level
775.
The system should provide capabilities for Notifying new employees/managers/Doctors/nurses etc. with specific course dates and details – automatic booking made for induction when new employee starts
776.
Facilitating the generation of a training & development plan built up from individually identified training needs with the means of recording training needs also available
777. Establishing the availability of the trainer
778. Establishing the availability of training center rooms and resources
779.
The system should support Skills Management & Training module interlinked with the Performance Management/Appraisal module, to identify training needs and to perform Training Needs Analysis
Page 70 of 165
780. The system should provide capabilities for handling management approvals for training applications
781.
The system should provide capabilities for evaluation of employee performance after completion of training program
782. The system should provide capabilities for enrolling employees and external trainees in courses.
783. Automatically scheduling trainees in a waitlist for any training once it becomes available.
784. Recognizing employee training programs and the skills expected to be gained from each program
785. Supporting evaluation of training courses
786. Having learners create their own learning paths that consists for courses they want to take
787.
The system should provide capabilities for constructing a learning path for an employee, to achieve goals, for instance for the next performance appraisal
788. The system should support generation of ad-hoc reports
789. The system should support performing of courses registration tasks
790. The system should support the validating course enrolment against previous courses taken
791. Storing and maintaining training budgets on organization level, area level, department level, etc.…
792. Handling skills acquired through that training assignment/course
793. The system should provide capabilities for Maintaining employee course history
794. The system should provide capabilities for Scheduled training notifications
795. The system should provide capabilities for Employee evaluation capability
796.
The system should provide capabilities for sending reminders to employees who have registered for an upcoming class
797. Storage of course descriptions and schedules
Page 71 of 165
798. Generating training confirmations for managers to distribute to employees without access to email
799. The system should support e-Learning training and tracking
800. Identification of the level achieved by an employee in a particular training program
801. Handling duration of the training and where it was done
802.
Managing data for each activity (budgets, maximum attendance, languages, success criteria, objectives, and sponsoring organizations ...
803.
The system should support scheduling of class events or sessions to employees or to a specific set of conditions
804.
The system should support the Tracking employees who are not taking training during a period, or not completed a training plan
805.
Setting up a training plan that will enable the employee to develop the skills and knowledge required to improve in the current job or move to the next job.
806. Performance Management Requirements
807.
Does the system incorporate a user defined performance appraisal process? Appraisal format and details Ratings / scores, Dates, Comments
808. Ability to fill target setting forms online
809. Ability to raise alerts to perform monthly appraisal feedback
810.
Ability to handle appraisal cycle as per Company Policy - Performance to be based on criteria and points and overall weight age to be calculated. Ability to include comments and attachments
811. The solution must allow the facility to record the assessment from appraisal discussions
812.
The workflow to operate on line performance review by supervisors for employees reporting as per the hierarchy / positions.
813. Describe how your system enables managers to define, track and
Page 72 of 165
measure performance for their employees
814. Ability to create a library of re-usable objectives
815.
Discuss how both single and multi-rater assessments (e.g., 360 appraisal) would be used by managers during the performance management process, including the automation of obtaining performance feedback from individuals and manager approvals to complete the process.
816. Automatic objective allocation
817. Ability of the system should to allow cascading objectives
818. Ability to record and track objective progress
819. Ability of the system Automatic create appraisals
820. The system should be supporting multiple types of appraisals
821. Ability to include competencies and objectives in the appraisal
822. Create and maintain appraisal and assessment templates
823. The system should support evaluating of employee advancement potential
824. Questionnaire administration should be supported in the system.
825. The system should support calculating final rating
826. Performance Management should be integrated with Training
827.
Assessing an employee’s key strengths and developmental areas. Developmental areas include competencies that the employee is lacking or needs to develop and improve.
828. The system should support defining of multiple appraisal templates
829. Providing advance notification of performance evaluations due alerts, and past due notices.
830.
Administering individual employee performance reviews, notifying supervisors of upcoming reviews, tracking and maintaining results and reporting/calculating results.
831. Reports
Page 73 of 165
HR Reports
832. The system should be able to generate the following Reports:
833. Absences Report including: Effective Date, Organization Unit Employee Date From, Date To, Absence Type
834.
Assignment Status Report including: Effective Date, Organization Structure, Version Parent Organization, Group, Job, Position, Grade, Payroll, Primary Person Type Assignment Status
835. Employee Summary Report
836. Full Applicant Details Report
837. Full Assignment Details Report
838. Full Person Details Report
839. Job and Position Skills Matching Report
840.
Organization Hierarchy Report including: Effective Date Organization Structure Version Parent Organization Managers Shown
841.
Position Hierarchy Report including: Effective Date Position Structure Version Parent Position Holders Shown
842. Termination’s Report
843. Employee Payroll Movements Report
Recruitment Reports
844. Candidate Detail - Competency (Skill)
845. Candidate Detail – Education
846. Candidate Detail - Employment History
847. Candidate Detail - Job Search Views
848. Candidate Detail - Personal Detail
849. Candidate Detail – Phone
850. Candidate Detail – Qualification
851. Job Posting Content Detail
852. Vacancy Detail - by Position
853. Vacancy Status
Payroll Reports
854. Earnings Audit Report
855. Payroll Exception Report
856. Void Payments Report
857. Leave Liability Report
858. Employee Benefit Eligibility Listing
859. Employee Benefit Enrollment Register
860. Employee by Supervisor Status - by
Page 74 of 165
Organization Hierarchy
861. Employee Primary Assignment with Salary and Grade Rate Detail - by Supervisor Hierarchy
862. Employee Salary Change Detail - by Years of Service
863. Employee Termination (Organization Hierarchy) Detail – Detail
864. Gross to Net Summary Report
865. Pay Advice
Payroll Requirements
866.
The proposed system should provide capabilities for defining compensations elements, allowances, associated benefits, remunerations and other facilities based on employee grade and integrating with the Payroll.
867.
The proposed system should provide capabilities for Creation and maintenance of separate policies for each of the different types of allowances based on grade, employee status, place of work, etc.
868.
The proposed system should provide capabilities for Performing the calculation and payment of overtime, attendance and other allowances
869.
The proposed system should provide capabilities for Making payments by the due date, direct to a specified bank account, by cash, or by cheque through the payables module
870.
The proposed system should provide capabilities for Calculation and payment of a supplementary run on any pay frequency
871.
The proposed system should provide capabilities for Calculation of retrospective amounts for salaries and allowances
872.
The proposed system should provide capabilities for Making corrections and reissue of inaccurate payments within a user defined timescale
873.
The proposed system should provide capabilities for Administration of allowances and deductions in line with statutory guidelines e.g. pension contributions, transport allowances, housing loans,
Page 75 of 165
entertainment allowance, tax, rent arrears recovery
874. The proposed system should provide capabilities for Deduction of loans and payments
875. Calculation of deductions based on the percent of earnings
876.
The proposed system should provide capabilities for Defining the Income Tax rates / brackets. For example, by salary brackets, year, gender, age, etc. according to the country rules and regulations
877. Maintaining year to date (YTD) balance of the Income tax deducted for each employee.
878.
Producing pay slips, in a format approved by the company, holding both monthly and cumulative payments/deductions/balances
879.
The proposed system should provide capabilities for Implementing national and local pay settlements including necessary retrospective adjustments and appropriate accountancy coding
880. Recording details of loans and advances disbursed to the employees of the company.
881.
The proposed system should provide capabilities for Defining and maintaining any number of user-defined payroll elements based on user-defined calculations
882.
The proposed system should provide capabilities for applying future commencement and completion dates for all allowances
883.
The proposed system should provide capabilities for calculating salary/ allowances on the basis of company rules/policy i.e. grades and benefits structure and maintaining different structure for different businesses.
884.
The proposed system should provide capabilities for computing end of service entitlements based on Kenyans labor laws
885. The proposed system should provide capabilities for maintaining
Page 76 of 165
employee grades and link them to the salary structures
886. The proposed system should provide capabilities for creation, allocation and maintenance of allowances
887.
The proposed system should provide capabilities for calculation & processing of allowances, deductions based on user-defined formulas.
888.
The proposed system should provide capabilities for defining pay type i.e. hourly, daily, weekly, monthly payment, as well as permanent, temporary, full time/part-time and facility for logging existing, on hold and resigned staff.
889.
The proposed system should provide capabilities for the recording of absences in working days and hours depending on individual working patterns and by type (nature of illness / injury against a pre-determined list).
890.
The proposed system should provide capabilities for recording other reasons for absence to include extended or overseas study leave, unpaid leave, compassionate leave, dependent leave, career break and others
891.
The proposed system should provide capabilities for creating accrual plans which allow users to reflect the rules by which leave, sick or other paid time off accrues over a year, including rules about vacation that may be carried forward into the next year.
892.
The proposed system should provide capabilities for Calculating salaries after accounting for unpaid leave information of each employee.
893.
The proposed system should provide capabilities for Calculating pension/commutation / gratuity for any employee based on the standard government formulas.
894. Calculating bonus/ increment on user defined parameters & generate bonus/ increment letters.
Page 77 of 165
895.
The proposed system should provide capabilities for running of multiple payroll to reflect different group of employees or different payroll calendars.
896.
The proposed system should provide capabilities for activating or deactivating specific deductions for any payroll cycle
897.
The proposed system should provide capabilities for administering each benefits option change through user-defined formula.
898.
The proposed system should provide capabilities for administering a different set of benefits for each employee.
899.
The proposed system should provide capabilities for employee’squalification for benefit enrollment.
900. The proposed system should provide capabilities for percentage or fixed amount option in payroll inputs.
901.
The proposed system should provide capabilities for Collecting data and report on potential disparate or adverse impact situations.
902.
The proposed system should provide capabilities for Maintaining the organization's current year's goals for action plan. Comparison of goals with actual results.
903.
The proposed system should provide capabilities for Handling management salary change requests using standard business processes.
904.
The proposed system should provide capabilities for Providing system-generated reports of service award eligibility.
905. Employee sick leave, vacation, leave of absence, job injury, personal holiday, maternity, pilgrimage…
906. The proposed system should provide capabilities for maintaining leave accruals by type of leave.
907. The proposed system should provide capabilities for tracking leave days taken, either paid or unpaid.
Page 78 of 165
908.
The proposed system should provide capabilities for handling non-standard hours (e.g., shifts, on call, holiday work, overtime, weekend work, special hours for cabin crew, Inflight, airport staff, etc.)
909. The proposed system should provide capabilities for Initiating post retirements benefit processing
910. The proposed system should provide capabilities for Initiating retiree death benefits processing
911. Using formulas to provide guidance to end users for complex rules
912.
The proposed system should provide capabilities for Managing creation of groups of employees with flexible criteria based on department, location, position, titles, local or foreign office, Science degree, fleet, etc.…)
913. Employee Bank details / Electronically deposits payroll to employee bank accounts
914.
Facility to automatically update the General Ledger system with the payroll cost, as per the business requirement.
915. Reversal to any mistake or adjustments done on the payroll and transferred
916.
Supporting multiple payroll cycles (e.g. weekly, monthly, daily, …etc.) with multiple employees pay groups or individual cases.
917. Automatic calculation of pay adjustments based on effective date of adjustment
918. Calculation of retroactive pay and process retroactive payment in the next payroll period
919.
Managing allowances per groups of employees with flexible criteria (period of calendar days, working days, fleet type, flying hours, …etc.).
920.
Calculating overtime pay based on the number of hours worked or flying hours or other user-defined rules during a designated overtime period.
921. Managing all Deductions cycles.
922. Managing deductions per groups of employees with flexible criteria with
Page 79 of 165
start and end dates.
923.
Calculating deductions based on parameterized values such as social security tax, income tax, and predetermined installments (deductions), according to rules and regulations defined by public or governmental organizations as per the company policy.
924.
Adding or deleting deductions at the organization, department, positions, etc. levels, as per the company payroll policies.
925. The proposed system should provide capabilities for Ability to process one-time deductions
926. The proposed system should provide capabilities for Deducting money for saving and other funds e.g.Sacco’s
927. Changing deduction rules for certain individual, groups, departments etc.
928.
Facility to allow cost of an employee to be split over different divisions/departments - both absolute amounts/percentage (%)/ hours basis. (For Basic as well as total salary cost).
929. The solution should produce pay slips, in a format approved by the organization.
930. The solution must undertake the calculation of deductions and amounts due to third parties
931. Self Service Requirements
932.
Solution allow one or more authorized users to determine which records may be accessed by either managers or users either as read only or with amendment rights.
933. The solution provides for managers to be able to view employee records of their subordinates
934.
Employees are able to access and update their own personal data such as name and address, bank details, next of kin details etc.
935. Managers approving employee transactions
936. Employees are able to request and record absences (e.g. sickness, annual leave, compassionate, study
Page 80 of 165
or parental leave) on a self-service basis
937.
Laundry Management
938. Enable scheduling of laundry and housekeeping services
939. Enable the scheduling of linen changes
940. Provide a solution to maintain the count the count of incoming and outgoing laundry items
941. Provide a configurable maintenance schedule for maintenance of equipment
942.
Allow for the capture of Real-time update quality indicators for cleanliness including fresh linen issue, damaged or missing items
943. Provide a stock ledger to maintaining a linen count and stock value to finance team.
Learning Management System
944. Provide a Global Nursing school calendar with School Terms and Class Schedules
945. Enable Online Study materials and homework submission
946. Enable Hostel and Transport Allocation for students
947. Create different views for Students and Faculty
948. Create Education system wide News and Events listings
949. Enable access to Payment gateways
950. Create and enable access to Library Systems
951. The solution must be available in multiple languages
952. The solution must have the ability to keep grades and results for students even after they leave the school
Fleet Management System
953. Ability to create requests for service, and track requests to completion
Page 81 of 165
954. Ability to track vehicles, and vehicle performance on a real-time basis
955.
Enable access to vehicle dashboard configuration like mileage, fuel consumption rate, Excessive idling and virtual odometer
956. Ability to review vehicle use logs like Hash Braking, Harsh Acceleration and Road Speed limit adherence
957. GEO Zone management with Panic Alerts, Vehicle Immobilization alerts and unauthorized movement alerts
958. Enable route replays to track vehicle movement history over a period of time
Queue Management
959. System supports up to 32 services and 64 counters.
960. Supports multiple dispensers of various types (Switch based, Touch Screen KIOSK and mixed).
961.
Built in Digital Signage for Promotional videos, slides and multilingual text on TV based Master Displays.
962. Token number displays for the counters.
963. Multilingual display and printing.
964. Multilingual Voice announcement
965. Modular Server- browser Client based design on Windows OS.
966. Nested and Multi service selection.
Page 82 of 165
967. Manual and Preconfigured multiservice forwarding.
968. Detailed management reports and analytical data.
969. Graphical reports.
970. Delay alerts to Management.
971. Dynamic load distribution.
972. Central Monitoring System.
973. Easy data backup and restore.
974. Multiple provisions for priority customers.
975. Option of form-based data collection against each token.
976.
Facility to add remarks to each token. The remarks are visible to every successive operator to whom this token is forwarded. Next operator can add his own remarks.
977. Reports of breaks taken by the operator.
978. Forward-back a token. An operator can forward-back a token to another service. On completion at forwarded service, the token is returned back
Page 83 of 165
to sender counter on priority.
979. Facility to call by Case Number, name or mobile No.
980. Facility to split services across several dispensers.
981. Facility to have time slot based multiple services for the same room.
982. Facility to have multiple token printing station spread across the network.
983. Facility to have separate Master Displays for each department.
Feedback Management
984. Ability to schedule all inquiries and appointments
985.
System to accept certain general and demographic information about the patient (Personal biodata)
986. System to have ability to allocate a unique number to patient
987.
System to capture date for Consultation Visit , Review/Follow-up Visit and Refill (Medicine) Visit
988. System to send alerts to patient /reminder on appointments and follow-ups
989. System to allow online appointment booking
Billing Management
990. System to allocate unique file number
991. Receive cash payment and issue receipt
Page 84 of 165
992. Prepare final bill and issue an invoice
993.
System to show Charges for the services automatically in the system depending upon the insurance/cash patient
994.
System to allow generating the invoice for OPD services and Receive cash payment for cash patient and issue receipt
995.
For credit patient prepare final bill and issue invoice to the insurance company.
996.
The cash counter user (Cashier) will have the option to enter discounts with authorization details
997. System to allow the amount to be received in various payment modes other than cash
998.
System to allow Refund Option for refund of services in case of non-performance of any or all the services
999.
System to allow cancellation and refunds at the user level with written authorization on the receipt
1000. System to allow integration and reconciliation with finance ERP system
1.15 Feedback Management
1001. Create a platform for patients to provide feedback for services and hospitality of the hospital
1002. Enable automatic routing of complaints and suggestions to the relevant department
1003.
Provide a mechanism for department acknowledgement of feedback and track the status of each transaction
1004.
Enable reporting, analysis and monitoring of Incidents/Complaints and the respective actions taken by the departments
Page 85 of 165
1.16 MIS Reporting BI & Analytics
1005. Provide a Dashboard based on role for Reporting
1006. Deliver management reporting capability
1007. Big data capabilities
1.17 Mobile App Solution
1008.
Provide a customer facing mobile app solution on the main platforms IOS and Android that gives patients and guests access to hospital solutions
1009.
Provide a mobile solution that creates virtual guidance to patients and guides on how to navigate the hospital to find resources
1010.
Provide an Employee only solution that can be remotely installed and removed from a device that allows employees to engage Human Resources and other employee only resources
1011.
Enable real-time tracking of usage of the mobile app solutions and analytics on which functionality is being used
1.18 IT Service Management
1012. Ability for users to create Incidents for systems and process failures
1013. Provide the ability to create standard Requests for service
1014.
Provide the functionality to escalate incidents that fall outside the agreed Service Level Agreements
1015.
Provide functionality to create Change Management before changes are introduced to production systems
1016. Provide functionality to track the status of Open and Resolved tickets
1017. Create Knowledge Base to track learned resolution procedures
1018. Create a process to track and resolve
Page 86 of 165
1.19 Reassignment Management
1019. Ability to create appointments at remote locations
1020. Ability for remote HMO to create appointments
1021. Provide functionality to allow subscribers to view their own records at other Hospitals
1.20 Contract Management
1022. Ability to store contract templates to manage contracts
1023. Ability to have automatic email Alerts,
1024. Custom Displays, Renamable Fields,
1025. Search Engine
1026. reporting capability, full-featured document management
1027. Ability to manage contracts approval process
1028. Hard-copy archive moved to/replaced by an electronic archive;
1029. One-stop repository for contracts of the organization;
1030. Compliance with contractual provisions i.e.
1031. Signing by e-signature;
1032. Sending for signing to external counterparties;
1033. Making comments upon approval/signing/rejection;
1034. Adjustment of negotiation process, i.e. option to amend the process;
1035. Monitoring of the course of negotiation process;
1.21 Project Management
Item Mandatory
Components SPECIFICATION
Compliant (Y/N)
Detailed explanation with Cross-reference
evidence
Page 87 of 165
1036. Project Management
1037. Project Lifecycle tracking
1038. Milestone Tracking
1039. Task Management
1040. Resource Management
1041. Role Based Login and Views
1042. Budget Management
1043. Customizable reporting
1044. Time and Expense Tracking
1045. Contact management
1.22 Service management
Item Mandatory
Components SPECIFICATION
Compliant (Y/N)
Detailed explanation with Cross-reference
evidence
1046.
Release Management - Plan releases by documenting the build and test plans, set start and end dates to update team members by creating announcements.
1047.
Incident Management - Reduce outages, improve agent productivity, meet SLAs, and manage the complete lifecycle of your IT tickets.
1048.
Problem Management - Isolate problems, link it to existing or past incidents, perform root cause analysis the timeline of events of your IT help desk system, and minimize disruptions to the business.
Page 88 of 165
1049.
Change Management - Plan, rollback changes with your cloud-based IT help desk tool and let relevant members evaluate and approve changes. Analyze and mitigate risks by assessing new changes before it's rolled out.
1050.
Reporting - Identify bottlenecks, make informed decisions, monitor help desk performance, and improve service delivery with predefined and custom reporting capabilities.
2. Hardware Technical Specifications
Hardware Technical Specifications
Item Mandatory Components
SPECIFICATION Compliant (Y/N)
Detailed explanation with Cross-reference evidence
Intel Nodes Qty- 2
1. Compute nodes Compute system should fit
in Standard 19-inch rack
2. Processors Workload support
Processor should support Multiple Unix and Linux Workloads concurrently
3
System Scalability
Must be capable of delivering a minimum peak result of 470 on CPU2017 Integer Rates, an independent benchmark result by Standard Performance Evaluation Corporation https://www.spec.org Better performance per core will be key to enabling Kenyatta National Hospital to curb on software licenses charged on a per core basis
Page 89 of 165
4.
Capacity on Demand
The system should provide Capacity on demand (Pay as you grow) Features on both Compute power (CPU) and Memory (RAM) to enable Kenyatta National Hospital consume the resources in a flexible manner
5.
Capacity on Demand features
Permanent Processor and/or Memory Capacity Upgrade on Demand Metered Processor and/or Memory Capacity on Demand Trial Processor and/or Memory CoD Utility CoD (To pay as per utilization) Multi System resource pooling
6. Virtualization Systems should provide
built-in System Hypervisor
7.
Required Processor performance
48 Processor cores (that can deliver a minimum peak result of 470 on CPU2017 Integer Rates)
8.
Enterprise Class Memory
System should be able to scale to a Minimum of 16TB Required: 1TB out of 1.5TB installed memory should be active memory. The rest of the capacity should be available on demand/pay as you grow basis.
9.
I/O Devices I/O devices (FC and Ethernet Adapters) should be capable of being virtualized and share across the systems/Virtual machines/Virtual instances to allow better system utilization
10.
Memory Resiliency
System Should provide up to 99.99% system Availability System should be capable of Memory Mirroring to prevent a system outage in the event of an
Page 90 of 165
uncorrectable error in memory being used by the system hypervisor. This is vital because the critical databases might be running in-memory
11.
Reliability requirements
System should not have any single point of failure and Should provide: Alternate processor recovery Redundant, hot-swappable power supplies and cooling fans Concurrent add/repair of Adapter drawers Hot-swappable disk bays in Internal Storage Hot-plug/blind-swap Adapter slots Dynamic processor deallocation/replacement Extended error handling on Adapters’ slots
12.
I/O (Adapters and connectivity)
12 x Base I/O Cards_ Production Servers
Minimum of (6x) 4port 1/10-Gigabit Ethernet Adapters (2 ports 1GB/s and 2 ports 10GB/s) - SR
Minimum of (6x) Dual-port 16GB/s Fiber channel Adapters
13.
Operating System Should support Multiples
Versions of RISC based Unix and Linux operating systems
Disk Storage Storage can be provided internally but External Storage is preferred to eliminate any single point of failure and allow for advanced SAN storage features such and Snapshots and non-proprietary data replication and storage management. Boot from SAN is also preferred. See Storage requirements
Page 91 of 165
below.
14. Storage Capacity
Optional of 4x 300GB 15k Disk Drives per Frame for internal capacity
16.
Resource Pooling
System Should be capable of sharing resources (at least Processor and memory) with other systems of the same type to manage the cost of resource activations
17.
Broad business application support
System should be able to provide support for multiple Business application
18 Support SLA
Production Support/Subscription for one Instance for 3 years. i.e. Quantities - 1
19 Local Support SLA
A minimum of three (3) years of support and service (Warranty)
20 Solution Training & Certification
Vendor-based certification class room training is required for at least two (2) Persons for 1 weeks. The bidder to meet all the cost for the training content including travel and accommodation for the persons attending the training. The training shall be in the manufacturer’s labs.
21 Capacity to deliver the service
Two (2) Certified Engineer with relevant qualifications (attach CVs and copies of certifications which must be specific to the following;
Proposed associated hardware. The Engineer must have a minimum of three years’ experience in installation and maintenance of the above systems.
22 Key Personnel Key Personnel Must be certified for storage implementation.
Page 92 of 165
Bidders must attach technical literature for item quoted and Manufacturers Authorization
SAN switches – Storage Feature QUANTITY 4
1 Form Factor 1U
2 SAN Switch type
48 Port SAN Switch
3
Speed 2,4,8 and 16 Gbps compatible 16 Gbps optimized Inter-Switch Links (ISLs)
4 Port on Demand capability
Scalable activation 24, 36 and 48 port activations All Ports should be activated
5 Media type 128 Gbps high-performance and resilient frame-based trunking
6 Memory Modules
Multitenancy in cloud environments through Virtual Fabrics, Integrated Routing, quality of service (QoS) and fabric-based zoning features
7 Performance 10 Gbps Fiber Channel integration on the same port
8 Data protection and security
In-flight data compression and encryption
9 High Availability
Hot Swappable and redundant Power supplies fan modules and small form-factor pluggable (SFPs)
10
Performance Produce an aggregate 768 Gbps full-duplex throughput
SAN STORAGE QUANTITY 2
Page 93 of 165
Item Mandatory Components
SPECIFICATION Compliant (Y/N)
Detailed explanation with Cross-reference evidence
1.
Form factor
Control enclosure: 2U rack mount, 24 drives
Expansion enclosure: 2U rack mount, 24 SFF/12 LFF drives
2.
Controller configuration
Offered storage shall be offered using two clustered controllers that are in active-active state and the storage array should be able to scale up to more than two controllers. Each controller enclosure should be able to support a minimum of 20 expansion enclosures.
3. RAID levels
RAID Support 0, 1, 5, 6, and 10; Distributed RAID 5 and 6
4.
Controller cache
Can support 64 GB (32GB per system) with optional 64GB per canister or 128GB per canister or upgradeable, Cache mirroring between the node canisters.
5. Drive technology
SAS and NL SAS HDDs and SAS SSDs. Intermix of HDDs and SSDs is supported.
6.
Drives
Total capacity 200TB with 10% on Flash drive
Should have intermix of flash drives and spinning disks 2.5 and 3.5
7.
Virtualization
Should support inbuilt and external virtualization for third party arrays without requirement of additional software or hardware
Page 94 of 165
8.
Host ports and back-end ports
1. Offered Storage shall have minimum of 4 host ports for connectivity to servers running at 16Gbps speed.
2. Offered storage shall also support additional Quad 10Gbps native ISCSI ports.
3. Offered storage shall have two additional IP ports for the storage-based replication. IP replication shall be optimized using SANrockIT technology to save on bandwidth costs.
4. Offered storage shall have a minimum of 4 SAS Back-end lanes running at 12Gbps speed.
9.
Data Protection and recovery
1. Offered Storage shall have support to make the snapshot and full copy (Clone) on the thin volumes if original volume is created on thick or vice-versa.
2. The storage array should have support for controller-based snapshots functionality for pointer-based snapshots (At-least 256 copies per file system),
3. Snapshot/snap clone software shall be licensed only once during acquisition and not on any future capacity upgrades
10.
Remote Replication
1. The storage array should support hardware-based data replication at the array controller level across all modern storage systems from various vendors.
Page 95 of 165
2. The replication shall use IP network connections for simplicity and lower cost
3. Replication shall support incremental replication after resumption from Link Failure or failback situations.
11.
Capacity Saving
1. Offered storage array shall be supplied with Thin provisioning as part of storage software
2. Offered storage shall be supplied with Real time compression to reduce on acquisition cost. Minimum data reduction ratio of 2:1 is required. Estimate free guarantee should be attached.
3. For effective capacity utilization, Real-time Compression shall operate immediately as data is written to disk, meaning that no space is wasted storing uncompressed data awaiting post-processing
12.
Support
The solution provider MUST have a back to back support agreement from Original OEM with:
• Global, 24x7 support for Severity 1 issues,
• Fast response times for critical issues,
• Unlimited number of support requests.
• Remote support.
• Product updates and upgrades
Page 96 of 165
13.
Support SLA
Production Support/Subscription for one Instance for 3 years. i.e. Quantities - 1
14. Local Support SLA
A minimum of three (3) years of support and service (Warranty)
15.
Solution Training & Certification
Vendor-based certification class room training is required for at least two (2) Persons for 1 weeks. The bidder to meet all the cost for the training content including travel and accommodation for the persons attending the training. The training shall be in the manufacturer’s labs.
16.
Support
The solution provider MUST have a back to back support agreement from Original OEM with:
• Global, 24x7 support for Severity 1 issues,
• Fast response times for critical issues,
• Unlimited number of support requests.
• Remote support.
• Product updates and upgrades
17.
Support SLA
Production Support/Subscription for one Instance for 3 years. i.e. Quantities - 1
18. Local Support SLA
A minimum of three (3) years of support and service (Warranty)
19.
Solution Training & Certification
Vendor-based certification class room training is required for at least two (2) Persons for 1 weeks. The bidder to meet all the cost for the training content including travel and
Page 97 of 165
accommodation for the persons attending the training. The training shall be in the manufacturer’s labs.
20.
Capacity to Deliver the Service
Two (2) Certified Engineer with relevant qualifications (attach CVs and copies of certifications which must be specific to the following;
Proposed associated hardware. The Engineer must have a minimum of three years’ experience in installation and maintenance of the above systems.
21.
Key Personnel
Key Personnel Must be certified for storage implementation.
Bidders must attach technical literature for item quoted and Manufacturers Authorization
3. Uninterrupted Power Supply Specifications
UPS REQUIREMENTS – QNTY 2
Item GENERAL FEATURES
MANDATORY SPECIFICATIONS
Compliant (Y/N)
Detailed explanation with cross-reference evidence
1 Topology Double-conversion online
2 Configuration Tower
3 Rating (VA/Watts)
120 kVA
4 UPS Bypass Automatic on overload or UPS failure
Page 98 of 165
5 Efficiency
Up to 98% High-efficiency mode, Up to 92% Double-conversion
6 Electrical Input
7 Connection Hardwired - see manual for terminal block layout
8 Input Cord Hardwired
9 Input Voltage Range
-15%, +20% from nominal (208V) at 100% load without depleting battery
10 Nominal Voltage
208V
11 Operating Frequency
50/60 Hz (40 to 72 Hz)
12 Input Power Factor
>0.99 typical
13 Input Current Distortion
5% THD
Electrical Output
14 Nominal Voltage
208/220, 3/4 wire
15 Output voltage regulation
±1% Static; ±5% dynamic at 100% resistive load change, < 20 ms response time
16 Output Receptacles
Hardwired - see manual for terminal block layout
17 Overload Capacity
150% for 40 ms / 125% for 30 seconds / 110% for 10 min
Battery
18 Battery Management
ABM (Cyclic) or float
19 Battery Type 9Ah, sealed, lead-acid, maintenance-free
20 Battery Replacement
Field-replaceable
21 Internal Batteries
Yes, has internal batteries. Field service upgrades needed to add external batteries (EBCs) to extend runtime
Communications
22 User Interface Graphical LCD with
Page 99 of 165
blue backlight
23 LEDs (4) LEDs for notice and alarm
24 Audible Alarms Yes
25 Communication Ports
(1) RS-232, (1) REPO
26 Communication Slot
(2) Mini-slot communication bays
27 Power Management Software
Intelligent Power Software Suite CD (included)
Environmental & Standards
28 Audible Noise < 64 dBA at 1 meter (noise less room) typical
29 Operating Temperature
0ºC (32ºF) to +30ºC (86ºF); Batteries recommended max. +25ºC (77ºF)
30 Safety markings
UL60950, EN55022/EN55024
31 EMC Markings IEC 62040-10
32 Markings UL, cUL
33 Storage Temperature
-25ºC (-13ºF) to +55ºC (131ºF) without batteries; +15ºC (59ºF) to +25ºC (77ºF) with batteries
34 Relative Humidity
5 –95%, non-condensing
35 Altitude < 1000m at +30°C (86ºF)
36 Capacity to Deliver the Service
Two (2) Certified Engineers with relevant qualifications (attach CVs and copies of certifications which must be specific to the following; Proposed associated hardware.
The Engineers two (2) must have a minimum of three years’ experience in installation and maintenance of the above systems.
Page 100 of 165
37
Warranty and support
A minimum of three (3) years hardware warranty from Original Equipment Manufacturer (OEM). A minimum of three (3) years maintenance and service
4. ICT Security Requirements
Security Requirements
ITEM
MANDATORY SPECIFICATIONS Compliant (Y/N)
Detailed explanation with cross-reference evidence
1 General Requirements
2 The OEM of the firewall must have at least 15 years of experience in the security market
OEM must have capacity and proficiency in providing Internet security solutions
3
The OEM must provide evidence of year over year leadership positions in enterprise firewall, UTM firewalls and intrusion prevention based on independent security industry data.
4
The OEM must be capable of serving the entire scope of security firewall requirements, including throughput, connection rate and next generation security application enablement for all network deployments, from small office to data center in a single hardware appliance.
5
The OEM must have a virtualized security firewall solution that can support the enablement of all next generation firewall security applications, including intrusion protection, application control, URL filtering, Anti-Bot, Anti-Virus, all managed from a central platform.
6
The next generation firewall must be capable of supporting these next generation security applications on a unified platform.
Stateful Inspection Firewall
Intrusion Prevention System
Page 101 of 165
User Identity Acquisition
Application Control and URL filtering
Anti – Bot and Anti – Virus
Anti – Spam and Email Security
IPSec VPN
Data Loss Prevention
Mobile Access
Security Policy Management
Logging and Status
Event Correlation and Reporting
7 These applications must be exclusively supplied by the OEM.
8
The solution must provide a mechanism to constantly educate end users of the security policy in real time.
9 The OEM must supply all industry certifications of the solution.
10
The solution must have the capability to provide a solution to mitigate Distributed Denial of Service attacks.
Firewall
11
The security firewall must use Stateful Inspection based on granular analysis of communication and application state to track and control the network flow.
12
The security firewall must be capable of supporting throughput, connection rate, concurrent connections requirements of the customer.
13 Solution must support access control for at least 150 predefined /services/protocols
14 Must provide security rule hit count statistics to the management application.
15
Must allow security rules to be enforced within time intervals to be configured with an expiry date/time.
16
The communication between the management servers and the security firewalls must be encrypted and authenticated with PKI
Page 102 of 165
Certificates.
17 The firewall must support user, client and session authentication methods.
18
The following user authentication schemes must be supported by the security firewall and VPN module: tokens (ie -SecureID), TACACS, RADIUS and digital certificates.
19
Solution must include a local user database to allow user authentication and authorization without the need for an external device
20 Solution must support DCHP, server and relay
21 Solution must support HTTP & HTTPS proxy
22 Solution must include the ability to work in Transparent/Bridge mode
23 Solution must support high redundancy
Support IPV6
24
Solution must support Configuration of dual stack firewall on a bond interface , OR on a sub-interface of a bond interface.
25
Solution must support IPv6 traffic handling on IPS and APP module, Firewall, Identity Awareness, URL Filtering, Antivirus and Anti-Bot.
26 Solution must Support 6 to 4 NAT, or 6 to 4 tunnel.
27 Solution must support AD integration using ipv6 traffic.
28 Solution must support Smart view tracker / smart log able to show ipv6 traffic.
29
Platform shall support ability to display IPv6 routing table (separated per customer security context in CLI and GUI (EMS/Portal).
Page 103 of 165
30
Solution shall support the folowing Ipv6 RFCs:
RFC 1981 Path Maximum Transmission Unit Discovery for IPv6
RFC 2460 IPv6 Basic specification
RFC 2464 Transmission of IPv6 Packets over Ethernet Networks
RFC 3596 DNS Extensions to support IPv6
RFC 4007 IPv6 Scoped Address Architecture
RFC 4193 Unique Local IPv6 Unicast Addresses
RFC 4213 Basic Transition Mechanisms for IPv6 Hosts and Routers – 6in4 tunnel is supported.
RFC 4291 IPv6 Addressing Architecture (which replaced RFC1884)
RFC 4443 ICMPv6
RFC 4861 Neighbor Discovery
RFC 4862 IPv6 Stateless Address Auto-configuration
INTRUSION PREVENTION SYSTEM
31
OEM must provide evidence of year over year leadership position of Gartner Magic Quadrant for Intrusion Prevention solutions and/Or Eneterprise network Firewall Gartner Magic Quadrant .
32
IPS must be based on the following detection mechanisms: exploit signatures, protocol anomalies, application controls and behavior-based detection.
33 IPS and firewall module must integrated on one platform.
34 The administrator must be able to configure the inspection to protect internal hosts only.
35
IPS must have options to create profiles for either client or server based protections, or a combination of both.
36 IPS must provide at least two pre-defined profiles/policies that can
Page 104 of 165
be used immediately.
37
IPS must have a software based fail-open mechanism, configurable based on thresholds of security firewalls CPU and memory usage.
38 IPS must provide an automated mechanism to activate or manage new signatures from updates.
39
IPS must support network exceptions based on source, destination, service or a combination of the three.
40
IPS must include a troubleshooting mode which sets the in use profile to detect only, with one click without modifying individual protections.
41 IPS application must have a centralized event correlation and reporting mechanism.
43
The solution administrator must be able to automatically activate new protections, based on configurable parameters (performance impact, threat severity, confidence level, client protections, server protections)
44
IPS must be able to detect and prevent the following threats: Protocol misuse, malware communications, tunneling attempts and generic attack types without predefined signatures.
45
For each protection the solution must include protection type (server-related or client related), threat severity, performance impact, confidence level and industry reference.
46 IPS must be able to collect packet capture for specific protections.
47
IPS must be able to detect and block network and application layer attacks, protecting at least the following services: email services, DNS, FTP, Windows services (Microsoft Networking), SNMP
48 OEM must supply evidence of leadership in protecting Microsoft vulnerabilities.
Page 105 of 165
50
IPS and/or Application Control must include the ability to detect and block peer to peer traffic using evasion techniques.
51 The solution administrator must be able to define network and host exclusions from IPS inspection.
52
Solution must protect from DNS Cache Poisoning, and prevents users from accessing blocked domain addresses.
53 Solution must provide VOIP protocols protections.
54
IPS and/or Application Control must detect and block remote controls applications, including those that are capable tunneling over HTTP traffic.
56 IPS must have SCADA protections.
57 IPS must have a mechanism to convert SNORT signatures.
58 Solution must enforce Citrix protocol enforcement.
59
Solution must be allow the administrator to easily block inbound and/or outbound traffic based on countries, without the need to manually manage the IP ranges corresponding to the country.
User Identity Acquisition
60
Must be able to acquire user identity by querying Microsoft Active Directory based on security events.
61
Must have a browser based User Identity authentication method for non-domain users or assets.
62.
Must have a dedicated client agent that can be installed by policy on users' computers that can acquire and report identities to the Security Firewall.
63. Must support terminal server environments
64. Impact on the domain controllers must be less than 3%.
Page 106 of 165
65.
Must be able to acquire user identity from Microsoft Active Directory without any type of agent installed on the domain controllers.
66. Must support Kerberos transparent authentication for single sign on.
67. Must support the use of LDAP nested groups.
68. Must be able share or propagate user identities between multiple security firewalls.
69. Must be able to create identity roles to be used across all security applications.
70. OEM must provide referenceable customer with more then 2,000 users deployed.
Application Control and URL Filtering
71. Application control database must contain more than 4000 known applications.
72. Solution must provide granular security control of at least 250,000 Web 2.0 widgets.
73.
Solution must not have any known published vulnerabilities in the last year to the existing architecture which can be exploited.
74.
Solution must have a URL categorization that exceeds 200 million URLs and covers more than 85% of Alexa’s top 1M sites.
75. Solution must be able to create a filtering rule with multiple categories.
76. Solution must be able to create a filtering for single site being supported by multiple categories.
77. Solution must have users and groups granularity with security rules.
78.
The security firewall local cache must give answers to 99% of URL categorization requests within 4 weeks in production.
79. The solution must have an easy to use, searchable interface for applications and URLs
80. The solution must categorize applications and URLs and applications by Risk Factor.
Page 107 of 165
81. The application control and URLF security policy must be able to be defined by user identities.
82. The application control and URLF database must be updated by a cloud-based service
83. The solution must have unified application control and URLF security rules.
84.
The solution must provide a mechanism to inform or ask users in real time to educate them or confirm actions based on the security policy.
85.
The solution must provide a mechanism to limit application usage based on bandwidth consumption.
86. The solution must allow network exceptions based on defined network objects
87.
The solution must provide the option to modify the Blocking Notification and to redirect the user to a remediation page.
88.
Solution must include a Black and White lists mechanism to allow the administrator to deny or permit specific URLs regardless of the category
89. Solution must have a configurable bypass mechanism
90. Solution must provide an override mechanism on the categorization for the URL database.
91. The application control and URLF security policy must report on the rule hit count.
Anti-Bot and Anti-Virus
92.
OEM must have an integrated Anti-Bot and Anti-Virus application on the next generation firewall.
93. Anti-bot application must be able to detect and stop suscpicous abnormal network behaviour .
94.
Anti-Bot application must use a multi-tiered detection engine, which includes the reputation of IPs, URLs and DNS addresses and detect patterns of bot
Page 108 of 165
communications.
95. Anti-Bot applications must be able to scan for bot actions.
96. Anti-Bot and Anti-Virus policy must be administered from a central console.
97.
Anti-Bot and Anti-Virus application must have a centralized event correlation and reporting mechanism.
98. Anti-virus application must be able to prevent access to malicious websites
99. Anti-virus application must be able to inspect SSL encrypted traffic.
100. Anti-Bot and Anti-Virus must be have real time updates from a cloud based service
101. Anti-Virus must be able to stop incoming malicious files.
102.
Anti-Virus and Anti-Bot policies must be centrally managed with granular policy configuration and enforcement.
SAND BOXING
103.
The solution must provide the ability to Protect against zero-day attacks before static signature protections have been created
104.
The solution must provide the ability for analyzing and detecting malware in business documents such as Adobe PDFs and MS Office files as well as EXE and Zip files
105. The solution must provide the ability for flexible deployment using local appliances or the cloud .
106. The solution must provide the ability for Zero false-positives
107.
The solution must provide the ability to emulate attacks targeting multiple Windows OS environments, at least :windows xp,windows 7 , windows 8
108. The solution must provide the ability to be centraly managed
Page 109 of 165
109.
The solution must provide the ability to Increase security with automatic sharing of new attack information with other firewalls in means of signature updates etc.
110. Device can inspect and block attacks passing in via HTTPS without additional device.
111. Device must support cluster installation.
112. Device can be deployed as a Mail Transfer Agent.
113. Device can be deployed inline, in cloud or offload the emulation to a nearby device
Anti-Spam & Email Security
114. Anti-Spam and Email security application must be content and language agnostic.
115.
Anti-Spam and Email security application must have real-time classification and protections based on detected spam outbreaks which are based on patterns and not content.
116.
The Anti-Spam and Email security application must include IP reputation blocking based on an online service to avoid false positives
117.
Solution must include a Zero-hour protection mechanism for new viruses spread through email and spam without relying solely in heuristic or content inspection
IPsec VPN
118. Internal CA and External third party CA must be supported.
119.
Solution must support 3DES and AES-256 cryptographic for IKE Phase I and II IKEv2 plus "Suite-B-GCM-128" and "Suite-B-GCM-256" for phase II.
120.
Solution must support at least the following Diffie-Hellman Groups: Group 1 (768 bit), Group 2 (1024 bit), Group 5 (1536 bit), Group 14 (2048 bit), Group 19 and Group 20
121. Solution must support data integrity with md5, sha1 SHA-256, SHA-384 and AES-XCBC
Page 110 of 165
122.
Solution must include support for site-to-site VPN in the following topologies:
Full Mesh (all to all),
Star (remote offices to central site)
Hub and Spoke (remote site through central site to another remote site)
123.
Solution must support the VPN configuration with a GUI using drag and drop object addition to VPN communities
124. Solution must support clientless SSL VPNs for remote access.
125. Solution must support L2TP VPNs, including support for iPhone L2TP client
126.
Solution must allow the administrator to apply security rules to control the traffic inside the VPN.
127.
Solution must support domain based VPNs and route based VPNs using VTI’s and dynamic routing protocols.
128. Solution must include the ability to establish VPNs with firewalls with dynamic public IPs
129. Solution must include IP compression for client-to-site and site-to-site VPNs
SECURITY MANAGEMENT
130. Security management application must be able to co-exist on the security firewall as an option.
131.
Security management application must support role based administrator accounts. For instance roles for firewall policy management only or role for log viewing only.
132.
Solution must include a Certificate-based encrypted secure communications channel among all OEM distributed components belonging to a single management domain
Page 111 of 165
133.
Solution must include an internal x.509 CA (Certificate Authority) that can generate certificates to firewalls and users to allow easy authentication on VPNs
134.
Solution must include the ability to use external CAs, that supports PKCS#12, CAPI or Entrust standards.
135. All security applications must be managed from the central console.
136. The management must provide a security rule hit counter in the security policy.
137.
Solution must include a search option to be able to easily query which network object contain a specific IP or part of it.
138.
Solution must include the option to segment the rule base using labels or section titles to better organize the policy
139. Solution must provide the option to save the entire policy or specific part of the policy.
140. Solution must have a security policy verification mechanism prior to policy installation.
141. Solution must have a security policy revision control mechanism.
142.
Solution must provide the option to add management high availability, using a standby management server that is automatically synchronized with the active one, without the need for an external storage device
143.
Solution must include a comprehensive map with all network objects and their connections that can be export to Microsoft Visio or to an image file
144. Solution must include the ability to centrally distribute and apply new firewall software versions
145.
Solution must include a tool to centrally manage licenses of all firewalls controlled by the management station
146.
Solution must have the capabilities for multi-domain management and support the concept of global security policy across domains.
Page 112 of 165
147.
The management GUI should have the ability to easily exclude IP address from the IPS signature definition
148.
The Log Viewer should have the ability to easily exclude IP address from the IPS logs when detected as false positive
149.
The management GUI should have the ability to easily get to IPS signature definition from the IPS logs
150.
The Log Viewer should have the ability view all of the security logs (fw,IPS ,urlf...) in one view pane (helpful when troubleshooting connectivity problem for one IP address )
151.
The Log Viewer should have the ability in the log viewer to create filter using the predefined objects (hosts ,network,groups,users...)
152.
The Log Viewer should have the ability in the log viewer to create custom multiple "saved filter" for use at a later time
THREAT PREVENTION UPDATE
153.
OEM must provide the details of its threat prevention update mechanism and its ability to handle zero day attacks across all next generation threat prevention applications including IPS, Application Control, URL filtering, Anti-Bot and Anti-Virus.
154.
OEM must provide details on the re-categorization of URL, under the circumstances that a website has been comprised and possibly distributing malware.
155. OEM should have the capability to provide incident handling
LOG & MONITORING
156.
The central logging must be part of the management system. Alternatively administrators can install deedicated Log Servers.
157. Solution must provide the option to run on the management server or on a dedicated server
Page 113 of 165
158. Solution must be able to run on an X86 based open servers listed on a hardware compatibility list.
159. Solution must have the ability to log all rules (+30k logs/sec)
160. Log viewer must have an indexed search capability
161.
Solution must have the ability to log all integrated security applications on the firewall and including IPS, Application Control, URL Filtering, Anti-Virus, Anti-Bot, Anti – Spam, User Identity, Data Loss Prevention, Mobile Access.
162.
Solution must include an automatic packet capture mechanism for IPS events to provide better forensic analysis
163. Solution must provide different logs for regular user activity and management related logs
164. Solution must be able to move from security log record to the policy rule with one mouse click.
165.
For each match rule or type of event Solution must provide at least the following event options: Log, alert, SNMP trap, email and execute a user defined script
166.
The logs must have a secure channel to transfer logging to prevent eavesdropping, Solution must be authenticated and encrypted
167.
The logs must be securely transferred between the firewall and the management or the dedicated log server and the log viewer console in the administrator’s PC
168.
Solution must include the option to dynamically block an active connection from the log graphical interface without the need to modify the rule base
169. Solution must support exporting logs in database format
170. Solution must support automatic switch of the log file, based on a scheduled time or file size
171. Solution must support adding exceptions to IPS enforcement from the log record
172. Solution must be able to associate a username and machine name to each log record.
Page 114 of 165
173.
Solution must include a graphical monitoring interface that provides an easy way to monitor firewalls status
174.
Solution must provide the following system information for each firewall: OS, CPU usage, memory usage, all disk partitions and % of free hard disk space.
175.
Solution must provide the status of each firewall components (i.e. firewall, vpn, cluster, antivirus, etc)
176. Solution must include the status of all VPN tunnels, site-to-site and client-to-site
177.
Solution must include customizable threshold setting to take actions when a certain threshold is reached on a firewall. Actions must include: Log, alert, send an SNMP trap, send an email and execute a user defined alert.
178.
Solution must include preconfigured graphs to monitor the evolution in time of traffic and system counters: top security rules, top P2P users, vpn tunnels, network traffic and other useful information. Solution must provide the option to generate new customized graphs with different chart types
179.
Solution must include the option to record traffic and system views to a file for later viewing at any time.
180.
Solution must be able to recognize malfunctions and connectivity problems, between two points connected through a VPN, and log and alert when the VPN tunnel is down.
REPORTING & EVENT CORRELATION
181. Solution must be fully integrated in the management application.
182.
Solution must include a tool to correlate events from all the firewall features and third party devices
183.
Solution must allow the creation of filters based on any characteristic of the event such as security application, source and destination IP, service, event type, event severity, attack name, country of origin and destination, etc.
Page 115 of 165
184.
The application must have a mechanism to assign these filters to different graph lines that are updated in regular intervals showing all events that matches that filter. Allowing the operator to focus on the most important events.
185. The event correlation application must supply a graphical view events based on time.
186. Solution must show the distribution of events per country on a map.
187.
Solution must allow the administrator to group events based on any of it characteristics, including many nesting levels and export to PDF.
188.
Solution must include the option to search inside the list of events, drill down into details for research and forensics.
189.
It the event list view Solution must include the option to automatically generate small graphs or tables with the event, source and destination distribution.
190. Solution must detect Denial of Service attacks correlating events from all sources.
191. Solution must detect an administrator login at irregular hour
192. Solution must detect credential guessing attacks
193. Solution must report on all security policy installations.
194.
Solution must include predefined hourly, daily, weekly and monthly reports. Including at least Top events, Top sources, Top destinations, Top services, Top sources and their top events, Top destinations and their top events and Top services and their top events.
195.
The reporting tool must support at least 25 filters that allow to customize a predefined report to be closest to administrator’s needs
Page 116 of 165
196.
Solution must support automatic reports scheduling for information that need to extract on regular basis (daily, weekly, and monthly). Solution must also allow the administrator to define the date and time that reporting system begins to generate the scheduled report.
197. Solution must support the following reports formats: HTML, CSV and MHT
198.
Solution must support automatic report distribution by email, upload to FTP/Web server and an external custom report distribution script
199.
The reporting system must provides consolidated information about:
The volume of connections that were blocked by security rule.
Top sources of blocked connections, their destinations and services
Top Rules used by the security policy
Top security attacks detected by enforcement point (perimeter) determining their the top sources and destinations
Number of installed and uninstalled policies in the enforcement point
Top networking services
Web activity by user detailing the top visited sites and top web users
Top services that created most load for encrypted traffic
Top VPN users performing the longest duration connections
MANAGEMENT PORTAL
200.
Solution must include a browser based access to view in read-only the security policies, manage firewall logs and users providing access to managers and auditors without the need to use the management application
201. Solution must include SSL support and configurable port
Page 117 of 165
DLP
202. OEM must have an option to add a fully integrated Data Loss Prevention application
203. DLP policy must be centrally managed with all other security applications
204. DLP application must have a mechanism for end user self-incident handling
205. DLP application must have over 500 pre-defined data types.
206.
DLP must have an open scripting language to create customer data types relevant to any organization
207. DLP must alert the data type owner when an incident occurs.
208. DLP application must cover transport types SMTP, HTTP/HTTPS, and FTP TCP protocols
MOBILITY
209.
The OEM should have an option to provide a fully integrated secure mobility solution on the next generation firewall.
210. The solution must support both managed and unmanaged access devices, such as BYOD
211. The solution should handle roaming devices when connecting off-perimeter.
212. by enforcing the same web security policy as if they are inside the perimeter.
213. Single management interface for both local and off-perimeter web security policy.
GOVERNANCE RISK AND COMPLIANCE
214.
OEM must have an option to provide a fully integrated Governance Risk and Compliance application
215.
OEM must have an option for Real Time Compliance Monitoring across all security services in the product
216.
OEM must have an option to Deliver real-time assessment of compliance with major regulations (PCI-DSS,HiPPA,SOX...)
Page 118 of 165
217.
OEM must have an option for Instant notification on policy changes impacting compliance
218. OEM must have an option to Provide actionable recommendations to improve compliance
219. OEM must have an option to recommend Security Best Practices
220.
OEM must have an option to Translate regulatory requirements into actionable security best practices
221.
OEM must have an option to Monitor constantly firewall configuration with the security best practices
222.
OEM must have an option to Generate automated assessment reports for compliance rating with top regulations
223.
OEM must have an option to Fully Integrate into Software Architecture & Management infrastructure
224.
OEM must have an option to Check compliance with every policy change for all Network Security Software Blades
SIZING AND RECOMMENDATION
225. OEM must have a dedicated hardware solution to meet all NGFW requirements of the customer.
226.
OEM must be able to supply a recommended hardware/software configuration based on the criteria of real world traffic and next generation security applications provided by the customer. OEM must be able to supply the recommended platform for any combination of these next generation firewall application, with supporting evidence that the appliance will perform as expected.
227. Internet Bandwidth requirements
228. Total Throughput requirements
229. Security firewall with 100 security rules
230. Network Address Translation enabled
231. Logging Enabled
232. Maximum Users
233. Traffic blend of HTTP, SMTP, DNS
Page 119 of 165
234.
NGFW such as;
Firewall
Intrusion Prevention
Application Control and URL filtering
Anti-Bot
Anti-Virus
IPsec VPN
Data Loss Prevention
Anti-Spam
Local or remote management
Clustering or high availability
Network Interface requirements
DAM - Database activity monitoring
ITEM MANDATORY SPECIFICATIONS Compliant (Y/N)
Detailed explanation with cross-reference evidence
General Requirements
235. Must be appliance based, software based or a combination of both
236. Must be Multi OS platform supporting: Solaris, Windows and Linux
237. Must provide for a separate storage audit trail away from monitored databases.
238. Audit trail should be secured by encryption.
239. All components must be centrally managed.
240. Must cover common databases like Oracle and SQL.
241. Solution must have provision for high availability.
242. The product must provide automated discovery of both new and existing database systems and Database tables on the network.
243. The product must keep the historical information about the systems and their configuration.
244. Must provide a comparison facility of different scan times.
245. Be able to identify rogue or test databases.
246. Support asset management and change management processes.
247. Product must perform data discovery and classification.
Page 120 of 165
248. Solution must detect sensitive data types, such as credit card numbers.
249. Must have inbuilt vulnerability assessment testing of supported databases.
250. Must have a provision for custom assessments.
251. Be able to identify missing patches for the monitored databases.
252. Be able to verify that default database accounts do not have “default” passwords.
253. Be able to measure compliance with known industry standards e.g. HIPAA, COBIT
254. Be able to measure compliance with firm’s ICT policy
255. Be able to present warnings on risk to data by highlighting the vulnerabilities and its effects on data.
256. Should have basic predefined reports and have ability to produce custom reports.
257. The solution must have virtual patching capabilities (Protecting the database from known vulnerabilities without deploying a patch or script on the system)
258. Provide tools for managing and mitigating risk to data stored in databases.
259. Be able to generate reports automatically and update administrators through emails.
260. Be able to manage/control the architecture and audit/security policies from a central console.
261. Product must have a method of archiving and restoring data.
262. Product must have a comprehensive tracking and logging facility for users.
263. The product must have an auditing process that is independent from the database platform being audited to allow for SODs
264. Be able to capture activity by a user by logging all activities including read, write and execute.
265. Must have inbuilt database security by being able to protect the DB from attacks such as database worms, denial of service attack and SQL injection.
Page 121 of 165
266. Provide real time protection and reports to security administrators. Be able to provide real-time blocking of attacks, monitor and be able to block activities of privileged user accounts.
267. Provide for quarantining or blacklisting user accounts that have violated policies.
268. Product must have forensic interrogation facility.
269. The solution must include a user rights management solution to review user rights and identify users with excessive rights. It should also be able to log user logon statistics.
SIEM -security information and event management
ITEM MANDATORY SPECIFICATIONS Compliant (Y/N)
Detailed explanation with cross-reference evidence
General Requirements
1.1
The Security Intelligence solution must provide central management of all components and administrative functions from a single web-based user interface. Please describe how your solution meets this requirement.
1.2
The administrator must be able to define role base access to the system by device, device group or network range. This includes being able restrict a user’s access to information to only those systems from a specific group of devices or network range. Please describe how your solution meets this requirement.
1.3
The administrator must be able to define role-based access to various functional areas of the solution. This includes being able to restrict a user’s access to specific functions of the solution that is not within the scope of a user’s role including, but not limited to, administration, reporting, event filtering, correlation, and/or dashboard viewing. Please describe how your solution meets this requirement.
Page 122 of 165
1.4
The solution must support auto-discovery of assets that are being protected or monitored. Please describe how your solution meets this requirement.
1.5
The solution must support automated classification of assets that are being protected Please describe how your solution meets this requirement.
1.6
The solution must support the detachment of selected dashboards from the UI for use in SOC or NOC deployments. Please describe how your solution meets this requirement.
1.7
The vendor of the Security Intelligence solution must provide and foster community-oriented information and experience sharing among users of the security intelligence solution. Describe your companies’ approach to this requirement.
1.8
The solution must support the ability to modify communications ports between components. Please describe how your solution meets this requirement.
1.9
The solution must provide an open API for access to data stored within the information database(s). Please describe how your solution meets this requirement.
1.10
The solution must provide the ability to encrypt communications between components. Please describe how your solution meets this requirement.
1.11
The solution must integrate with 3rd party directory systems as an authentication method. How does your solution integrate with a LDAP or AD solution for access provisioning to the SIEM system?
Operational Requirements
2.1 The solution must enable a phased role out of log management and security intelligence functions. Introduction of more analysis capabilities should minimize the need for additional system components and be enabled through license key upgrades. Please describe how your solution meets this requirement.
Page 123 of 165
2.2 The solution must provide a framework for future expansion and integration with other 3rd part solutions. Please describe how your solution meets this requirement.
2.3 The solution must demonstrate ‘ease of use’. Ease of use is critical to the successful deployment and on-going use of the solution. Describe the ease of use considerations and implementations within the solution.
2.4 The solution must support the automatic update of configuration information with minimal user intervention. For example, security taxonomy updates, vendor rule updates, device support, etc. Describe how the solution provides this functionality and detail the features that are updated.
2.5 The solution must support a web-based GUI for management, analysis and reporting. Please describe how your solution meets this requirement.
2.6 The solution must support high availability requirements in an embedded fashion andwithout the need for additional 3rd party software. Please explain meets this requirement to provide 24x7 availability and fault tolerance?
2.7 The solution must ensure all distributed system components continue to operate when any other part of the system fails or loses connectivity. (i.e., management console goes off-line all separate collectors still continue to capture logs). Please describe how your solution meets this requirement.
2.8 The solution must have an automated backup/recovery process. Please describe how your solution meets this requirement.
2.9 The solution must automate internal health checks and notify the user when problems arise. Please describe how your solution meets this requirement.
2.10 The solution must provide the ability to deliver multiple dashboards that can be customized to meet the specific requirements of different
Page 124 of 165
users of the system. Please describe how your solution meets this requirement.
2.11 The solution must deliver sample dashboards out of the box (i.e. for threat management, compliance management, etc.). Please describe how your solution meets this requirement.
2.12 The solution must deliver customizable dashboard widgets that can present relevant security information to the users of the system (i.e. event views, network activity views, incident views, etc.). Please describe how your solution meets this requirement.
2.13 The solution must maintain a database of all assets discovered on the network. This asset data must include important information about the asset as learned by the information collected (i.e. system attributes, network attributes, vulnerability state, etc.). The database must provide the ability to edit attributes when they cannot be learned (i.e. department, location, etc.). The user must be able to search this database. Please describe how your solution meets this requirement.
Architectural Requirements
3.1 The solution must enable deployments as software and/or appliance. Please describe how your solution meets this requirement.
3.2 The solution must integrate with other security and network intelligence solutions. Describe the level of integration and solutions supported.
3.3 The Security Intelligence solution must allow for customization to meet our unique requirements. Please describe how your solution meets this requirement.
3.4 The solution must easily expand to support additional demand. How does your solution scale to increase demand placed on the solution as the organization adds more devices, locations, applications, etc.? Please
Page 125 of 165
describe the impact to each of the proposed components of your solution (i.e. appliances, storage, management consoles, etc.)
3.5 The solution must support a distributed database for event and network activity collection such that all information can be access from a single UI. Please describe how your solution meets this requirement.
3.6 The solution must ensure the integrity of the information collected. What mechanisms does the solution provide to meet this requirement?
3.7 The solution must provide intuitive mechanisms for troubleshooting such as proactive notifications, command line utilities etc.
3.8 The solution must support a distributed model for correlation such that counters, sequences, identity lookups, etc.… are shared across all collectors. (i.e., look for 25 login failures from the same user name followed by a single successful login for that same user name, where events seen by a single collector do not exceed the threshold of 25, but across multiple collectors would exceed the threshold). Please describe how your solution meets this requirement.
3.9 The solution must support user extended taxonomy of events and fields. The user must be able to add their own unique event names (i.e., the ability to add in new fields that are not part of the vendors out of the box schema such as a failed called “SpecialID from my Custom Application”). Please describe how your solution meets this requirement.
3.10 The solution must allow for custom defined tagging of events. Please describe how your solution meets this requirement.
3.11 The solution must provide transparent retrieval, aggregation, sorting, filtering and analysis of data across all distributed components. Please describe how your solution
Page 126 of 165
meets this requirement.
Log Management Requirement
LOG,COLLECTION, RETENTION AND PROCESSING
4.1 The solution must have a log collection and archive architecture that supports both short-term (online) and long-term (offline) event storage. How does your solution manage, store, and archive the log data?
4.2 The solution must support log archives on 3rd party storage. Please describe how your solution meets this requirement.
4.3 The solution must provide capabilities for efficient storage and compression of collected data. Please describe how your solution meets this requirement.
4.4 The solution must support industrylog collection methods (syslog, WMI, JDBC, SNMP, Checkpoint LEA, etc.)? Please describe what collection methods are available in your solution.
4.5 The solution must provide agent-less collection of event logs whenever possible. Does your solution rely on agent technology? If so, please describe how this is used to collect and aggregate event data?
4.6 The solution must provide the ability to distribute both event storage and processing across the entire Log Management/SIEM deployment. Explain how your architecture will support this requirement.
4.7 The solution must support long-term access to detailed security event and network flow data. The system must be able to provide access to at least 6months’ worth of detailed information. Describe how the system provides access to this information.
LOG,COLLECTION, RETENTION AND PROCESSING
5.1 The solution must normalize common event fields (i.e. usernames, IP addresses, hostnames, and log source device, etc.) from disparate devices across a multi-vendor network. Please describe how normalization is performed and the standard event fields that are normalized out-of-the-box.
Page 127 of 165
5.2 The solution must provide a common taxonomy of events. Please describe how this is provided by the solution the standard event categories that are provided out-of-the-box.
5.3 The solution must provide the ability to store/retain both normalized and the original raw format of the event log for forensic purposes. Please describe how this requirement is met by the solution.
5.4 The solution must provide the ability to normalize and aggregate event fields that are not represented by the out-of-the-box normalized fields. Please describe how this requirement is met by the solution.
5.5 The solution must support/normalize event time stamps across multiple time zones. Describe you this requirement is met by the solution.
EVENT, FILTERING& ANALYSIS
6.1 The solution must provide near-real-time analysis of events. Please describe how this requirement is met by the solution.
6.2 The solution must provide long term trend analysis of events. Please describe how this requirement is met by the solution.
6.3 The solution must provide the ability to aggregate an analyze events based on a user specified filter. Please describe how this requirement is met by the solution.
6.4 The solution must provide more advanced event drill down when required. Please describe how this requirement is met by the solution.
6.5 The solution must provide a real-time streaming view that supports full filtering capabilities. Please describe how this requirement is met by the solution.
6.6 The solution must provide alerting based on observed anomalies and behavioral changes in network and security events. Please describe how this requirement is met by the solution.
6.7 The solution must support and maintain a history of user authentication activity on a per asset basis. Please describe how your solution meets this requirement.
Page 128 of 165
REPORTING
7.1 The solution must provide reporting on all items available for management via the GUI. Describe how the solution provides the ability to configure reports.
7.2 The solution must provide configurable reporting engine for customized report creation. Please describe how your solution meets this requirement.
7.3 The solution must support the ability to schedule reports. Describe the mechanisms and frequency at which reports can be scheduled.
7.4 The solution must provide templates for the easy creation and delivery of reports at multiple levels ranging from operations to business issues. Please describe the process for creating reports and the number of available reports.
7.5 The solution must provide ‘canned’ out-of-the-box reports for typical business and operational issues. Describe the reports and report types available.
7.6 The solution must provide ‘canned’ out-of-the-box reports for specific compliance regulations (PCI, SOX, FISMA) and control frameworks including (NIST, COBIT, ISO). Please describe how your solution meets this requirement.
7.7 The solution must provide a ‘Dashboard’ for quick visualization of security and network information. Please describe the components available in the dashboard and the frequency at which this information refreshes.
7.8 The solution must support the automated distribution of reports. Describe the mechanisms used to distribute reports.
7.9 The solution must support the capability to provide historical trend reports. Please describe how your solution meets this requirement.
7.10
The solution must support the ability to centrally deliver vulnerability reports. Please describe how your solution meets this requirement.
7.11
The solution must support the ability to centrally deliver asset reports. Please describe how your solution meets this requirement.
CORRELATION AND ALERTING
Page 129 of 165
9.1 The solution must provide alerting based on observed security threats from monitored devices. Please describe how your solution meets this requirement.
9.2 The solution must provide the ability to correlate information across potentially disparate devices. Please describe how your solution meets this requirement.
9.3 The solution must provide alerting based on observed anomalies and behavioral changes in network activity (flow) data. Describe any pre-packaged alerts and method for adding user-defined anomaly and behavior alerts.
9.4 The solution must provide alerting based upon established policy. (e.g., IM traffic is not allowed.) Describe the solutions ability to alert on policy violations.
9.5 The solution must support weighted alerts to allow for prioritization. Weights must be assignable based on multiple characteristics such as asset type, protocol, application, etc. Describe how the solution supports weighted alerts and the structure of assigning weights.
9.6 The solution must provide the ability to transmit alerts using multiple protocols and mechanisms to other management solutions
9.7 The solution must provide UI based wizard and capabilities to minimize false positives and deliver accurate results. Please describe how your solution meets this requirement.
9.8 The solution must limit the presentation of multiple similar alerts. Describe the solutions ability to minimize duplicate alarms.
9.9 The solution must support the ability to act upon receiving an alert. For example, the solution should support the ability to initiate a script or send an email message. Please describe how your solution meets this requirement.
9.10
The solution must support the ability to correlate against 3rd party security data feeds (i.e. geographic mapping, known botnet channels, known hostile networks, etc.). These 3rd party data feeds should be updated automatically by the solution. Please describe how your solution meets this requirement.
9.1 The solution must support the ability to
Page 130 of 165
1 correlate against 3rd party vulnerability scan results. Please describe how your solution meets this requirement.
9.12
The solution must monitor and alert when there is a disruption in log collection from a device. In other words, if logs are not seen from a server in X minutes then generate an alert. Please describe how your solution meets this requirement.
9.13
The solution must provide an out of the box mechanism to discover and classify assets by system type (i.e. mail servers vs. data base servers) to minimize false positives associated with poor asset classification. Please describe how your solution meets this requirement.
9.14
The solution must support correlation for a missing sequence. Example service stopped not followed by the service restarting within 10 minutes. Please describe how your solution meets this requirement.
9.15
The solution must support correlation for additive values over time. For example, alert when any SRC IP sends more than 1GB of data to a single port on a single DST IP in a one-hourperiod. Please describe how your solution meets this requirement.
9.16
The solution must provide a mechanism, to optimize rule tuning, which allows for the grouping of similar input values of a correlation rule that can be used by multiple rules. This grouping mechanism should allow for both static groups and groups that are dynamically created by other correlation rules. For example, the user of the system can define a group of banned ports/protocols that should be used across multiple correlation rules that monitor for inappropriate network activity. Please describe how your solution meets this requirement.
9.17
The solution must be able to be updated regularly, to stay aware of the latest threat information and research available.
NETWORK ACTIVITY MONITORING
10.1 The solution must display visual traffic profiles in terms of bytes, packet rates and number of hosts communicating. These displays must be available for
Page 131 of 165
applications, ports, protocols, threats and each monitoring point in the network. All these views must support network location specific view such that they can present information from a single location, the entire network or any other defined grouping of hosts. Please describe how your solution meets this requirement.
10.2 The solution must support application definition beyond protocol and port. The system must support the identification of applications using ports other than the well-known, and applications tunneling themselves on other ports (e.g., HTTP as transport for MS-Instant Messenger should be detected as Instant messenger - not HTTP). Please describe how your solution meets this requirement.
10.3 The solution must detect “zero-day” events. Describe how the solution detects and displays this information.
10.4 The solution must dynamically learn behavioral norms and expose changes as they occur. Detail the methods used by the solution and the method by which anomalies are displayed.
10.5 The solution must detect denial-of-service (DoS) and distributed denial-of-service (DDoS) attacks. Describe how the solution detects and displays this information.
10.6 The solution must detect and present views of traffic pertaining to observed threats in the network. Describe the types of threats and visualizations for this information in the Security Intelligence system.
10.7 The solution must profile traffic by TCP and UDP port. Please describe how your solution meets this requirement.
10.8 The solution must support traffic profiling associated with logical network design (e.g., Subnet/CIDR). Please describe how your solution meets this requirement.
10.9 The solution must identify network traffic from potentially risky applications (e.g. file sharing, peer-to-peer, etc.). Please describe how your solution meets this requirement.
10.1 The solution must display traffic
Page 132 of 165
0 profiles in terms of packet rate. This capability must be available for simple TCP analysis (TCP Flags, etc.) but rate-based information may be presented for other profiles (e.g., applications). Please describe how your solution meets this requirement.
10.11
The solution must profile and present information in multiple timeframes. Profiles must be available for week, day and hour. Describe the maximum and minimum timeframes available for profiling and analysis.
10.12
The solution must be able to profile communication originating from or destined to the internet by Geographic regions in real-time. Describe how this is accomplished.
10.13
The solution must create clearly independent and differentiated profiles from local traffic vs. traffic originating or destined for the internet. Please describe how your solution meets this requirement.
10.14
The solution must allow the user to create custom profiles and views using any property of a flow, log, data source or already profiled traffic. Describe how the Security Intelligence system supports this level of customization.
10.15
The solution must support traffic profiling based on IP addresses, groups of IP addresses, source/destination IP pairs etc. Please describe how your solution meets this requirement.
10.16
The solution must support the collection and analysis of packet capture data. Please describe how your solution meets this requirement.
10.17
The solution must provide the ability to extract specific, user defined, fields from packet capture data and use the fields in correlation rules. Please describe how your solution meets this requirement.
10.18
The solution must identify network traffic within a virtual network environment. Please describe how your solution meets this requirement.
ADVANCE THREAT MANAGEMENT
11.1 The solution must provide the ability to contextually link application
Page 133 of 165
activity on the network with security events from monitored devices. Explain how the solution uses network knowledge to validate security events.
11.2 The solution must provide the ability to contextually link reported security events with real-time knowledge of the assets that are being targeted. Explain how the solution uses knowledge of assets within the network to validate security
11.3 The solution must provide the ability to automatically weight the priority of reported security events according to the relative importance of the targeted asset. Please explain how this is accomplished
11.4 The solution must provide the ability to automatically weight the severity of reported security events according to the vulnerability of the targeted assets. Please explain how asset profiles are used to prioritize events
11.5 The solution must provide the ability to assign credibility ratings to monitored security devices. Please describe how your solution meets this requirement.
11.6 The solution must provide a real-time event view of monitored information in raw/original as well as processed/parsed format. Please describe how your solution meets this requirement.
11.7 The solution must be able to automatically change the credibility weightings of security devices in response to network-wide attacks. Please describe how your solution meets this requirement.
SIEM WORKFLOW
12.1 The solution must provide ability to send notification of correlated alerts via well-defined methods (i.e. SNMP trap, email, etc.)? Please describe how your solution meets this requirement.
12.2 The solution must provide embedded workflow capability that security operations staff can use to guide their work. Please describe how your solution meets this requirement.
12.3 The solution must provide bi-
Page 134 of 165
directional integration with 3rd party trouble ticketing/help desk systems that security operations staff may use to guide their work? Please describe how your solution meets this requirement.
12.4 The solution must provide a mechanism to capture all relevant aspects of a security incident in a single logical view. This view should include relevant events, network activity data, correlated alerts, vulnerability data, etc. Please describe how your solution meets this requirement.
12.5 The solution must provide a mechanism to annotate a security incident as it is addressed by the security operations staff. Please describe how your solution meets this requirement.
12.6 The solution must provide a mechanism to track security incidents across a wide range of relevant attributes (i.e. IP addresses, usernames, MAC address, log source, correlation rules, user defined, etc.). The user must be able to filter incidents along these defined attributes. Please describe how your solution meets this requirement.
13.1 The solution must be able to collect and normalize configuration from switches, routers, firewalls, and IPS. Please describe how your solution meets this requirement.
13.2 The solution must have the ability to compare the configuration on a device when configuration changes occur. Please describe how your solution meets this requirement.
13.3 The solution must be able to detect and notify configuration change that is outside some pre-defined policy baseline. Please describe how your solution meets this requirement.
13.4 The solution must be able to provide a Layer 2/Layer 3 topology of how the network is configured. This user must be able to filter this topology by network, port, and protocol. Please describe how your solution meets this requirement.
Page 135 of 165
13.5 The solution must be able to consolidate results from multiple vulnerability scanners, risk management solutions and external threat intelligence resources. Please describe how your solution meets this requirement.
13.6 The solution must prioritize the resulting list of vulnerabilities based on whether the network is configured in such a way to allow the vulnerability to be compromised. Please describe how your solution meets this requirement.
13.7 Vulnerability checking must be responsive to trigger conditions and activities in the network
13.8 The solution must allow the user to run “what if” attack scenarios (simulations) against network configuration. Please describe how your solution meets this requirement.
DATA SOURCE REQUIREMENTS
14.1 The solution must support the following vendor products.
14.2 The solution must support information collected from Microsoft based servers and end-user systems. Please describe your level of support for this type of product.
14.3 The solution must support information collected from Linux/UNIX based servers and end-user systems. Please describe your level of support for this type of product.
14.4 The solution must support information collected from mainframe servers. Please describe your level of support for this type of product.
14.5 The solution must support information collected from enterprise class database solutions. Please describe your level of support for this type of product.
14.6 The solution must support information collected from commercial applications (i.e. SAP, Web, etc.). Please describe your level of support for this type of product.
14.7 The solution must support information
Page 136 of 165
collected from Data Leak Protection (DLP) Security software and tools. Please describe your level of support for this type of product.
14.8 The solution must support information collected from proprietary applications. Please describe your level of support for this type of product.
14.9 The solution must support information collected for Database Activity Monitoring (DAM) Security software and tools. Please describe your level of support for this type of product.
14.10
The solution must support information collected from File Integrity/Activity Monitoring (FIM/FAM) Security software and tools. Please describe your level of support for this type of product.
14.11
The solution must support information collected from Identity and Access Management Security software and tools (IAM). Please describe your level of support for this type of product.
14.12
The solution must support information collected from Directories (i.e. AD, LDAP) products. Please describe your level of support for this type of product.
14.13
The solution must support information collected from Network flows (i.e. NetFlow, J-Flow, sFlow etc.) products. Please describe your level of support for this type of product.
14.14
The solution must support information collected from network management systems (i.e. McAfee ePolicy Orchestrator, Microsoft MOM, etc.). Please describe your level of support for this type of product.
14.15
The solution must support information collected from Network infrastructure (i.e. switches, routers, etc.). Please describe your level of support for this type of product.
Page 137 of 165
14.16
The solution must support information industry leading vulnerability scanners. Please describe your level of support for this type of product.
NETWORK (INCIDENT) FORENSICS
15.1 The Security Intelligence solution being offered must include full packet capture and network forensics capabilities
15.2 Incident forensics analysis tool must accept input from multiple third-party packet capture appliances.
15.3 Incident forensics capability must be usable by network analysts, without requiring a PhD level understanding of networking.
15.4 The packet capture and incident forensics capabilities should be especially well equipped, from a speed-of-searching standpoint.
15.5 The packet capture capability needs to be expansive and accommodating of the need to retain captured information for long periods of time.
Page 138 of 165
Step 2: Technical Scoring- Firm Evaluation
S/ Max Score
Score Awarded
No Evaluation Criteria
1. Experience and Technical Capability
a) Experience in supply, installation, testing, commissioning and support of an Enterprise Resource Planning(ERP) System and Supporting Hardware and Software components in a large and complex environment in public sector (letters from five referees confirming successful execution of contracts) 6 marks for each reference up to a maximum score of 30 marks
30
b) Minimum five years experience in implementation of similar solution, supported by proof of satisfactory project completion (4 marks for each proof up to a maximum score of 20 marks)
20
c) Experience of the Project Team (certified curriculum vitae and qualification documents )
1. Team leader (at least six years’ experience in similar Project) 1 mark for each year of experience maximum of 6 marks.
2. Project Manager (at least five years’ experience in similar Projects) 1 mark for each year of experience maximum of 5 marks.
3. Project Engineer-(Three project engineers-ERP and Supporting hardware and software respectively) (at least three years’ experience in similar projects) 1 marks for each year of experience maximum of 9 marks.
20
Page 139 of 165
S/ Max Score
Score Awarded
No Evaluation Criteria
2 Proof of concept a) Integration of the ERP with at least two standard Health Management Information Systems (HMIS)- 10 marks
b) Integration with at least three key third party systems(e.g. Mobile Payment Systems, Insurance e.t.c ) - 12 marks
c) Management Reporting-4 marks
d) Mobile App Solution-4 marks
30
100
Bidders who score 80 out of the maximum 100 marks will proceed to the financial evaluation. Those who score below 80 out of the maximum 100 marks will be eliminated at this stage from the entire evaluation process and will not be considered further.
C. Financial Evaluation
Stage 3 - Financial
Evaluation
Evaluation will
involve the
following
(a). Determination of evaluated price for each bid using the Following
i) There will be no corrections of arithmetic errors as per Public
Procurement & Assets Disposal Act 2015 Section 82.
ii) Conversion of all tender to same currency using a uniform exchange rate prevailing at the closing date of the Tender
Page 140 of 165
iii) Application of any discount offered on the tender
iv) Establish if items quoted for are within prevailing market rates from the
known retail outlets & Public Procurement Oversight Authority price index. A
written undertaking that the prices shall remain valid for 12 months from date
of contract in line with the Public Procurement and Asset Disposal Act 2015
section 139(3).
(b) Ranking of Bids according to their evaluated prices
All documents indicated above and all other technical documents required to qualify for the tender participation should be submitted together with the bid on or before the closing date. Any bid not accompanied by the documents shall be rejected as non responsive. Due diligence may be conducted prior to the award of the tender to confirm and verify the qualifications of the bidder who will recommended to be awarded the contract. Bids will be ranked according to their evaluated prices and award recommended to the lowest evaluated bidder
SECTION III: GENERAL CONDITIONS OF CONTRACT
Table of Clauses
Page
3.1 Definitions .................................................................. 25
3.2 Application ................................................................. 25
3.3 Country of Origin .......................................................... 25
3.4 Standards ................................................................... 26
3.5 Use of Contract Documents and Information .......................... 26
3.6 Patent Rights ............................................................... 26
3.7 Performance Security ..................................................... 26
3.8 Inspection and Tests ...................................................... 27
3.9 Packing ...................................................................... 28
3.10 Delivery and Documents .................................................. 28
3.11 Insurance ................................................................... 28
3.12 Payment .................................................................... 28
3.13 Price ......................................................................... 29
3.14 Assignments ................................................................ 29
3.15 Sub contracts .............................................................. 29
3.16 Termination for Default .................................................. 29
3.17 Liquidated Damages ....................................................... 30
3.18 Resolution of Disputes .................................................... 30
3.19 Language and law ......................................................... 30
Page 141 of 165
3.20 Force Majeure .............................................................. 30
3.21 Notices ...................................................................... 30
Page 142 of 165
SECTION III - GENERAL CONDITIONS OF CONTRACT 3.1 Definitions
3.1.1 In this Contract, the following terms shall be interpreted as indicated:-
(a) “The Contract” means the agreement entered into between the Procuring entity and the tenderer, as recorded in the Contract Form signed by the parties, including all attachments and appendices thereto and all documents incorporated by reference therein.
(b) “The Contract Price” means the price payable to the tenderer under the Contract for the full and proper performance of its contractual obligations
(c) “The Equipment” means all of the equipment, machinery, and/or other materials, which the tenderer is required to supply to the Procuring entity under the Contract.
(d) “The Procuring entity” means the organization purchasing the Equipment under this Contract.
(e) “The Tenderer’ means the individual or firm supplying the Equipment under this Contract.
3.2 Application
3.2.1 These General Conditions shall apply in all Contracts made by the Procuring entity for the procurement installation and commissioning of equipment to the extent that they are not super ceded by provisions of other part of contract.
3.3 Country of Origin
3.3.1 For purposes of this clause, “Origin” means the place where the Equipment were mined, grown or produced.
3.3.2 The origin of Equipment and Services is distinct from the nationality of the tenderer and will be treated thus in the evaluation of the tender.
Page 143 of 165
3.4 Standards
3.4.1 The Equipment supplied under this Contract shall conform to the standards mentioned in the Technical Specifications.
3.5 Use of Contract Documents and Information
3.5.1 The Candidate shall not, without the Procuring entity’s prior written consent, disclose the Contract, or any provision therefore, or any specification, plan, drawing, pattern, sample, or information furnished by or on behalf of the Procuring entity in connection therewith, to any person other than a person employed by the tenderer in the performance of the Contract.
3.5.2 The tenderer shall not, without the Procuring entity’s prior written consent, make use of any document or information enumerated in paragraph 3.5.1 above
3.5.3 Any document, other than the Contract itself, enumerated in paragraph 3.5.1 shall remain the property of the Procuring entity and shall be returned (all copies) to the Procuring entity on completion of the Tenderer’s performance under the Contract if so required by the Procuring entity
3.6 Patent Rights
3.6.1 The tenderer shall indemnify the Procuring entity against all third- party claims of infringement of patent, trademark, or industrial design rights arising from use of the Equipment or any part thereof in the Procuring entity’s country
3.7 Performance Security
3.7.1 Within twenty eight (28) days of receipt of the notification of Contract award, the successful tenderer shall furnish to the Procuring entity the performance security where applicable in the amount specified in Special Conditions of Contract.
3.7.2 The proceeds of the performance security shall be payable to the Procuring entity as compensation for any loss resulting from the Tenderer’s failure to complete its obligations under the Contract.
3.7.3 The performance security shall be denominated in the currency of the contract, or in a freely convertible currency acceptable to the procuring entity and shall be in the form of
a) Cash
b) Bank guarantee
c) Such insurance guarantee approved by the Authority
d) Letter of credit
3.7.4 The performance security will be discharged by the Procuring entity and returned t the Candidate not late than thirty (30) days following the date of completion of the Tenderer’s performance obligations under the Contract, including any warranty obligations, under the Contract
3.8 Inspection and Tests
3.8.1 The Procuring entity or its representative shall have the right to inspect and/or to test the equipment to confirm their conformity to the Contract specifications. The Procuring entity shall notify the tenderer in writing in a timely manner, of the identity of any representatives retained for these purposes.
3.8.2 The inspections and tests may be conducted in the premises of the tenderer. All reasonable facilities and assistance, including access to drawings and production data, shall be furnished to the inspectors at no charge to the Procuring entity.
3.8.3 Should any inspected or tested equipment fail to conform to the Specifications, the Procuring entity may reject the equipment, and the tenderer shall either replace the rejected equipment or make alterations necessary to make specification requirements free of costs to the Procuring entity.
3.8.4 The Procuring entity’s right to inspect test and where necessary, reject the equipment after the equipment arrival and installation shall in no way be limited or waived by reason of the equipment having previously been inspected, tested and passed by the Procuring entity or its representative prior to the equipment delivery.
3.8.5 Nothing in paragraph 3.8 shall in any way release the tenderer from any warranty or other obligations under this Contract.
3.9 Packing
3.9.1 The tenderer shall provide such packing and packaging of the equipment as is
required to prevent their damage or deterioration during transit to their final destination, as indicated in the Contract.
3.9.2 The packing, marking, and documentation within and outside the packages shall comply strictly with such special requirements as shall be expressly provided for in the Contract
3.10 Delivery and Documents
3.10.1 Delivery of the equipment, documents and installation of the same shall be made by the tenderer in accordance with the terms specified by Procuring entity in its Schedule of Requirements and the Special Conditions of Contract
3.11 Insurance
3.11.1 The equipment supplied under the Contract shall be fully insured against loss or damage incidental to manufacturer or acquisition, transportation, storage, and delivery in the manner specified in the Special conditions of contract.
3.12 Payment
3.12.1 The method and conditions of payment to be made to the tenderer under this Contract shall be specified in Special Conditions of Contract
3.12.2 Payments shall be made promptly by the Procuring entity as specified in the contract
3.13 Prices
3.13.1 Prices charged by the tenderer for equipment delivered and installation performed under the Contract shall not, with the exception of any price adjustments authorized in Special Conditions of Contract, vary from the prices by the tenderer in its tender.
3.13.2 Contract price variations shall not be allowed for contracts not exceeding one year (12 months)
3.13.3 Where contract price variation is allowed, the variation shall not exceed 10% of the original contract price.
3.13.4 Price variation requests shall be processed by the procuring entity within 30 days of receiving the request.
3.14. Assignment
The tenderer shall not assign, in whole or in part, its obligations to perform under this
Contract, except with the Procuring entity’s prior written consent
3.15. Subcontracts
3.15.1 The tenderer shall notify the Procuring entity in writing of all subcontracts awarded under this Contract if not already specified in the tender. Such notification, in the original tender or later, shall not relieve the tenderer from any liability or obligation under the Contract
3.16. Termination for Default
3.16.1 The Procuring entity may, without prejudice to any other remedy for breach of Contract, by written notice of default sent to the tenderer, terminate this Contract in whole or in part
(a) if the tenderer fails to deliver any or all of the equipment within the period9s) specified in the Contract, or within any extension thereof granted by the Procuring entity
(b) if the tenderer fails to perform any other obligation(s) under the Contract
(c) if the tenderer, in the judgment of the Procuring entity has engaged in corrupt or fraudulent practices in competing for or in executing the Contract
3.16.2 In the event the Procuring entity terminates the Contract in whole or in part, it may procure, upon such terms and in such manner as it deems appropriate, equipment similar to those undelivered, and the tenderer shall be liable to the Procuring entity for any excess costs for such similar equipment.
3.17. Termination for convenience
3.18. Liquidated Damages
3.18.1 If the tenderer fails to deliver and/or install any or all of the items within the period(s) specified in the contract, the procuring entity shall, without prejudice to its other remedies under the contract, deduct from the contract prices liquidated damages sum equivalent to 0.5% of the delivered price of the delayed items up to a maximum deduction of 10% of the delayed equipment. After this the tenderer may consider termination of the contract.
3.19. Resolution of Disputes
3.19.1 The procuring entity and the tenderer shall make every effort to resolve amicably by direct informal negotiation any disagreement or dispute arising between them under or in connection with the contract
3.19.2 If, after thirty (30) days from the commencement of such informal
negotiations both parties have been unable to resolve amicably a contract dispute, either party may require that the dispute be referred for resolution to the formal mechanisms specified in the SCC.
3.20. Language and Law
3.20.1 The language of the contract and the law governing the contract shall be English language and the Laws of Kenya respectively unless otherwise specified in the SCC
3.21. Force Majeure
3.21.1 The Tenderer shall not be liable for forfeiture of its performance security or termination for default if and to the extent that it’s delay in performance or other failure to perform its obligations under the Contract is the result of an event of Force Majeure.
3.22 Notices
3.22.1 Any notice given by one party to the other pursuant to this contract shall be sent to other party by post or by fax or Email and confirmed in writing to the other party’s address specified.
3.22.2 A notice shall be effective when delivered or on the notices effective date, whichever is later.
SPECIAL IV - SPECIAL CONDITIONS OF CONTRACT
Notes on Special Conditions of Contract
4.1 The clauses in this section are intended to assist the procuring entity in providing contract-specific information in relation to corresponding clauses in the General Conditions of Contract
4.2 The provisions of Section IV complement the General Conditions of Contract included in Section III, specifying contractual requirements linked to the special circumstances of the procuring entity and the equipment being procured. In preparing Section IV, the following aspects should be taken into consideration.
(a) Information that complement provisions of Section III must be incorporated and
(b) Amendments and/or supplements to provisions of Section III, as necessitated by the circumstances of the equipment being procured must also be incorporated.
SECTION IV - SPECIAL CONDITIONS OF CONTRACT
4.1 Special Conditions of Contract shall supplement the General Conditions of Contract. Whenever there is a conflict, between the GCC and the SCC, the provisions of the SCC herein shall prevail over these in the GCC.
4.2 Special conditions of contract as relates to the GCC
REFERENCE OF GCC SPECIAL CONDITIONS OF CONTRACT
3.4.1 Equipment shall be supplied as per the provided technical specifications.
3.7.1 The tenderer shall provide all necessary assistance, equipment, human resource and any other support required to ensure successful inspection.
KNH will carry out a joint testing and commissioning of the equipment with the supplier to confirm that as specified in the tender document, it is working as expected upon delivery.
3.8.1 The implementation of this project will be under the supervision of the quality assurance consultant procured by the KHN.
3.10.1 The delivery of all the equipments shall be at the point of installation within the hospital premises.
Delivery of all the equipments shall be made by the tenderer in accordance with the terms specified by Procuring entity in its Schedule of Requirements and the Special Conditions of Contract.
3.11.1 The equipment under the Contract shall be fully insured by the tenderer against loss or damage
incidental to manufacturer or acquisition, transportation and delivery as indicated under clause 3.10.1.
3.12.1 Payment will be made through electronic fund transfer within 30 days upon receipt of invoice after supply, delivery, inspection and acceptance of the equipment.
3.13.2 Contract price variation shall not be allowed within the first twelve months. Any variation thereafter shall
not exceed 10% of the original contract price.
3.15.1 Details pertaining any subcontractor (s) MUST be disclosed in the bid document
3.18.1 Any dispute arising from the interpretation or performance of this contract shall be resolved through arbitration. The arbitrator shall be appointed by the
Chairperson of the Chartered Institute Arbitrators - Kenya
SECTION - V- SCHEDULE OF REQUIREMENTS AND PRICES
Notes on Schedule of Requirements and Prices
5.1 The Procuring entity must state whether the contract is for procurement, installation and commissioning OR whether it is for installation and commissioning only, in which case, the equipment will have been procured separately.
5.2 The tenderers may use additional paper as will be necessary to indicate the details of their costing
SECTION V - SCHEDULE OF REQUIREMENTS AND PRICE PRICE QUOTED SHALL INCLUDE THE TOTAL COST OF SUPPLY, DELIVERY, INSTALLATION, TESTING, COMMISSIONING, TRAINING, SUPPORT AND TWO YEARS WARRANTY. (TO BE IMPLEMENTED AS A TURNKEY PROJECT INCLUDING SET-UP OF THE SUPPORTING HARDWARE AND SOFTWARE COMPONENTS, INSTALLATION, TESTING, COMMISSIONING AND SUPPORT OF THE ERP AND INTEGRATION WITH THIRD PARTY SYSTEMS)
ITEM UNIT QUANTITY RATE (KSHS)
AMOUNT (KSHS)
1. ENTERPRISE RESOURCE PLANNING (ERP) SYSTEM
Financial Management Supply Chain
Management Human Resource
Management Learning Management
System Queue Management Feedback Management Billing Management MIS Reporting BI &
Analytics Mobile App Solution IT Service Management Reassignment
Management Laundry Management Project Management Service management
LOT LOT
3. SUPPORTING HARDWARE AND SOFTWARE COMPONENTS
a) ERP Hosting Servers b) SAN Storage c) SAN Switches d) Security Information
Event Management solution
e) Unified Thread Management Solution
f) Network(Incident Forensics) solution
g) Database Monitoring Solution
2 2 4 1 2 1 1
LOT
ITEM UNIT QUANTITY RATE (KSHS)
AMOUNT (KSHS)
LOT LOT
6. Training
8. Less Discounts given Kshs.
9. Total Cost of Project as per specifications. Costs inclusive of all Taxes applicable
Kshs.
NOTE: Conditions for PC sums: All contingency sums and PC sums are subject to detailed B.O.Q and competitive bidding with relevant qualified subcontractors for the specialized works.
Authorized Official: Name Signature
Date
SECTION VI - TECHNICAL SPECIFICATIONS
6.1 GENERAL
6.1.1. These specifications describe the basic requirements for equipment. Tenderers are requested to submit with their offers the detailed specifications, drawings, catalogues, etc for the products they intend to supply.
6.1.2 Tenderers must indicate on the specifications sheets whether the equipment offered comply with each specific requirement.
6.1.3 All the dimensions and capacities of the equipment to be supplied shall not be less than those required in these specifications. Deviations from the basic requirements, if any, shall be explained in detail in writing with the offer, with supporting data such as calculation sheets, etc. The procuring entity reserves the right to reject the products, if such deviations shall be found critical to the use and operation of the products
6.1.4 The tenderers are requested to present information along with their offers as follows;-
(i) Shortest possible delivery period of each product
(ii) Information on proper representative and/or workshop for back-up service/repair and maintenance including their names and addresses
SECTION VI – TECHNICAL SPECIFICATIONS
TECHNICAL SPECIFICATIONS FOR THE ENTERPRISE RESOURCE PLANNING (ERP) SYSTEM AND SUPPORTING HARDWARE AND SOFTWARE COMPONENTS FOR KENYATTA NATIONAL HOSPITAL ARE AS ATTACHED ON THE TECHNICAL EVALUATION CRITERIA (TO BE IMPLEMENTED AS A TURNKEY PROJECT INCLUDING SET-UP OF THE SUPPORTING HARDWARE AND SOFTWARE COMPONENTS, INSTALLATION, TESTING, COMMISSIONING AND SUPPORT OF THE ERP AND INTEGRATION WITH ERP AND THIRD PARTY SYSTEMS)
SECTION VII - STANDARD FORMS
Notes on the Standard Forms:
7.1 Form of Tender
This form must be completed by the tenderer and submitted with the tender documents. It must also be duly signed by duly authorized representative of the tenderer.
7.2 Confidential Business Questionnaire Form
This form must be completed by the tenderer and submitted with tender documents
7.3 Tender Security Form When required by the tender document the tenderer shall provide the tender security either in the form included therein after or in another format acceptable to the procuring entity.
7.4 Contract Form The Contract form shall not be completed by the tenderer at the time of submitting the tenderer at the time of submitting the tender. The contract form shall be completed after contract award.
7.5 Performance Security form The performance security form should not be completed by the tenderer at the time of tender preparation. Only the successful tenderer will be required to provide performance security in the sum provided herein or in another form acceptable to the procuring entity.
7.6 Bank Guarantee for Advance Payment. When there is an agreement to have Advance payment, this form must be duly completed.
7.7 Manufacturer’s Authorization Form When required by the tender document, this form must be completed and submitted with the tender document. This form will be completed by the manufacturer of the equipment where the tender is an agent
7.1 FORM OF TENDER
Date Tender No________________________
To: Chief Executive Officer Kenyatta National Hospital P.O. Box 20713-00202 Nairobi [name and address of procuring entity] Gentlemen and/or Ladies: Having examined the tender documents including Addenda Nos.…………………………… [insert numbers].the receipt of which is hereby duly acknowledged, we, the undersigned, offer to supply deliver, install, test and commission ……………………………………………………………………………………………………………………………………………………
.(insert equipment description) in conformity with the said tender documents for the sum of ………………………………………………………………………………………………………………………………………… ……………………………………………………………………………………………………………………………………………..(total tender amount in words and figures). We undertake, if our Tender is accepted, to deliver, install, test and commission the equipment in accordance with the delivery schedule specified in the Schedule of Requirements. If our Tender is accepted, we will obtain the guarantee of a bank in a sum of equivalent to 5% percent of the Contract Price for the due performance of the Contract , in the form prescribed by Kenyatta National Hospital. We agree to abide by this Tender for a period of 120 days from the date fixed for tender opening of the Instructions to tenderers, and it shall remain binding upon us and may be accepted at any time before the expiration of that period. This Tender, together with your written acceptance thereof and your notification of award, shall constitute a Contract, between us. Subject to signing of the Contract by the parties. We understand that you are not bound to accept the lowest or any tender that you may receive. Dated this day of ______________20
[Signature] [in the capacity of] Duly authorized to sign tender for an on behalf of
7.2 CONFIDENTIAL BUSINESS QUESTIONNAIRE FORM
You are requested to give the particulars indicated in Part 1 and either Part 2(a), 2(b) or
2 (c) (Whichever applied to your type of business) and part 3(a) & 3(b) that is mandatory.
You are advised that it is a serious offence to give false information on this form
Mandatory
Part 1 – General:
Business Name ………………………………………………………………………………………………………………..
Location of business premises. ……………………………………………………………………………………..
Plot No………………………………………………… Street/Road ………………………………………………….
Postal Address …………………………….. Tel No. ………………..company Mobile ……………….
E mail address……………………………………..Contact Person ……………………Mobile…………………
Nature of Business,………………………………………………………………………………………………………………
Registration Certificate No. …………………………………………………………………………………………….…
Maximum value of business which you can handle at any one time – Kshs. ……………………………
Name of your bankers …………………………………………….. Branch. ……………………………
Complete part 2(a), 2(b) or 2(c)
Part 2 (a) – Sole Proprietor
Your name in full …………………………………………………….. Age …………………………………………….
Nationality ………………………………… Country of origin ………………………………………………………
Citizenship details …………………………………………………………………………………
Part 2 (b) Partnership
Given details of partners as follows:
Name Nationality Citizenship Details Shares
1. ……………………………………………………………………………………………………………………………………….
2. ………………………………………………………………………………………………………………………………………
3. ……………………………………………………………………………………………………………………………………
4. ……………………………………………………………………………………………………………………………………
5. .…………………………………………………………………………………………..……………………………………
Part 2 (c ) – Registered Company Private or Public
……………………………………………………………………………………………………….
State the nominal and issued capital of company: Nominal Kshs. …………………………………
Issued Kshs. ……………………………………….
Given details of all directors as follows
Name Nationality Citizenship Details Shares
1…………………………………………………………………………………………………………………………………………
2.………………………………………………………………………………………………………………………………………..
3.………………………………………………………………………………………………………………………………………….
4.…………………………………………………………………………………………………………………………………………
5 ……………………………………………………………………………………………………………………………………….
NB: If a Kenya Citizen, indicate under “Citizenship Details” whether by Birth,
Naturalization or Registration.
Sign ………………………………Date ……………………………Stamp………………...
Mandatory
Part 3 (a) – Pursuant to section 59(1)(a) ,(2) and (3) of the Public Procurement Assets and Disposal Act
related Regulations . This must be signed by all Directors Partner (s) /Sole Proprietor of the Company
(or any other applicable legislation in the Country of registration)
1 /we the Director(s) of Company/Firm ……………………………………………………….hereby declare that I /we
are not a board member , employee or even a relative to any employee of Kenyatta National Hospital.
Given details of partners /Directors /Sole proprietor as follows:
Name Nationality Citizenship Details Signature
1…………………………………………………………………………………………………………………………………………………..
2……………………………………………………………………………………………………………………………………………………
3…………………………………………………………………………………………………………………………………………………..
4………………………………………………………………………………………………………………………………………………….
5…………………………………………………………………………………………………………………………………………………..
Mandatory
Part 3(b) Public Procurement & Assets Disposal Act 2015 and related regulations or any other applicable
legislation in the Country of registration).
Pursuant to section 41 of the Public Procurement and Assets Disposal Act 2015, I/ we the
Directors/Partners/Sole Proprietor of this Company/Firm ……………………………………………………...confirm
that we have not been debarred in Kenya not to Participate in any Tender/Bidding in Kenya.
Name Nationality Citizenship Details Signature
1…………………………………………………………………………………………………………………………………………………..
2. ………………………………………………………………………………………………………………………………………………..
3. ………………………………………………………………………………………………………………………………………………..
4. ………………………………………………………………………………………………………………………………………………..
5 …………………………………………………………………………………………………………………………………………………
7.3 TENDER SECURITY FORM
Whereas ……………………………………………. [name of the tenderer] (hereinafter called “the tenderer”) has submitted its tender dated …………. [date of submission of tender] for the supply, installation and commissioning of ………………………………[name and/or description of the equipment] (hereinafter called “the Tender”) …………………………………………….. KNOW ALL PEOPLE by these presents that WE ……………………… ……………… of …………………………………………. having our registered office at ………………… (hereinafter called “the Bank”), are bound unto …………….. [name of Procuring entity} (hereinafter called “the Procuring entity”) in the sum of ………………………………….. for which payment well and truly to be made to the said Procuring entity, the Bank binds itself, its successors, and assigns by these presents. Sealed with the Common Seal of the said Bank this day of 20 .
THE CONDITIONS of this obligation are:-
1. If the tenderer withdraws its Tender during the period of tender validity specified by the tenderer on the Tender Form; or
2. If the tenderer, having been notified of the acceptance of its Tender by the Procuring entity during the period of tender validity:
(a) fails or refuses to execute the Contract Form, if required; or
(b) fails or refuses to furnish the performance security in accordance with the Instructions to tenderers;
We undertake to pay to the Procuring entity up to the above amount upon receipt of its first written demand, without the Procuring entity having to substantiate its demand, provided that in its demand the Procuring entity will note that the amount claimed by it is due to it, owing to the occurrence of one or both of the two conditions, specifying the occurred condition or conditions.
This tender guarantee will remain in force up to and including thirty (30) days after the period of tender validity, and any demand in respect thereof should reach the Bank not later than the above date.
[signature of the bank] (Amend accordingly if provided by Insurance Company)
7.4 CONTRACT FORM
THIS AGREEMENT made the day of 20 between ……………… [name of Procurement entity) of ……….. [country of Procurement entity] (hereinafter called “the Procuring entity) of the one part and …………………….. [name of tenderer] of ………….. [city and country of tenderer] (hereinafter called “the tenderer”) of the other part;
WHEREAS the Procuring entity invited tenders for [certain equipment ] and has accepted a tender by the tenderer for the supply of those equipment in the sum of …………………………… [contract price in words and figures] (hereinafter called “the Contract Price).
NOW THIS AGREEMENT WITNESSETH AS FOLLOWS:
1. In this Agreement 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 Agreement viz:
(a) the Tender Form and the Price Schedule submitted by the tenderer
(b) the Schedule of Requirements (c ) the Technical Specifications
(d) the General Conditions of Contract
(e) the Special Conditions of contract; and
(f) the Procuring entity’s Notification of Award
3. In consideration of the payments to be made by the Procuring entity to the tenderer as hereinafter mentioned, the tenderer hereby covenants with the Procuring entity to provide the equipment and to remedy the defects therein in conformity in all respects with the provisions of this Contract
4. The Procuring entity hereby covenants to pay the tenderer in consideration of the provisions of the equipment 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 Agreement to be executed in accordance with their respective laws the day and year first above written.
Signed, sealed, delivered by the (for the Procuring entity)
Signed, sealed, delivered by the (for the tenderer in the presence of
7.5 PERFORMANCE SECURITY FORM
To …………………………………………. [name of Procuring entity]
WHEREAS …………………………………… [name of tenderer] (hereinafter called “the tenderer”) has undertaken , in pursuance of Contract No. [reference number of the contract] dated 20 to supply ……………………………………………… [description of equipment] (hereinafter called “the Contract”).
AND WHEREAS it has been stipulated by you in the said Contract that the tenderer shall furnish you with a bank guarantee by a reputable bank for the sum specified therein as security for compliance with the Tenderer’s performance obligations in accordance with the Contract.
AND WHEREAS we have agreed to give the tenderer a guarantee:
THEREFORE WE hereby affirm that we are Guarantors and responsible to you, on behalf of the tenderer, up to a total of ………………………. [amount of the guarantee in words and figure] and we undertake to pay you, upon your first written demand declaring the tenderer 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 you needing to prove or to show grounds or reasons for your demand or the sum specified therein.
This guarantee is valid until the day of 20
Signed and seal of the Guarantors
[name of bank or financial institution]
[address]
[date] (Amend accordingly if provided by Insurance Company)
7.6 BANK GUARANTEE FOR ADVANCE PAYMENT
To ……………………………… [name
of Procuring entity] [name of tender] …………………..
Gentlemen and/or Ladies:
In accordance with the payment provision included in the Special Conditions of Contract, which amends the General Conditions of Contract to provide for advance payment, …………………………………………………. [name and address of tenderer](hereinafter called “the tenderer”) shall deposit with the Procuring entity a bank guarantee to guarantee its proper and faithful performance under the said Clause of the Contract an amount of …… …………………. [amount of guarantee in figures and words].
We, the ……………………………. [bank or financial institutions], as instructed by the tenderer, agree unconditionally and irrevocably to guarantee as primary obligator and not as surety merely, the payment to the Procuring entity on its first demand without whatsoever right of objection on our part and without its first claim to the tenderer, in the amount not exceeding …………………… [amount of guarantee in figures and words]
We further agree that no change or addition to or other modification of the terms of the Contract to be performed there-under or of any of the Contract documents which may be made between the Procuring entity and the tenderer, shall in any way release us from any liability under this guarantee, and we hereby waive notice of any such change, addition, or modification.
This guarantee shall remain valid in full effect from the date of the advance payment received by the tenderer under the Contract until ………… [date].
Yours truly,
Signature and seal of the Guarantors
[name of bank or financial institution]
[address]
[date]
7.7 MANUFACTURER’S AUTHORIZATION FORM
To [name of the Procuring entity] ………………….
WHEREAS …………………………………………………………[ name of the manufacturer] who are established and reputable manufacturers of ………………….. [name and/or description of the equipment] having factories at ………………………………… [address of factory] do hereby authorize ………………………… [name and address of Agent] to submit a tender, and subsequently negotiate and sign the Contract with you against tender No. ………………………. [reference of the Tender] for the above equipment manufactured by us.
We hereby extend our full guarantee and warranty as per the General Conditions of Contract for the equipment offered for supply by the above firm against this Invitation for Tenders.
[signature for and on behalf of manufacturer] Note: This letter of authority should be on the letterhead of the
Manufacturer and should be signed by an authorized person.
7.8. LETTER OF NOTIFICATION OF AWARD
Address of Procuring Entity
To:
RE: Tender No.
Tender Name
This is to notify that the contract/s stated below under the above mentioned tender have been awarded to you.
7.7.1 Please acknowledge receipt of this letter of notification signifying your acceptance.
7.7.2 The contract/contracts shall be signed by the parties within 30 days
of the date of this letter but not earlier than 14 days from the date of the letter.
7.7.3 You may contact the officer(s) whose particulars appear below on the subject matter of this letter of notification of award.
(FULL PARTICULARS)
SIGNED FOR ACCOUNTING OFFICER
7.9 FORM RB 1
REPUBLIC OF KENYA
PUBLIC PROCUREMENT ADMINISTRATIVE REVIEW BOARD
APPLICATION NO…………….OF ................. 20……...
BETWEEN …………………………………………….APPLICANT AND
…………………………………RESPONDENT (Procuring Entity)
Request for review of the decision of the…………… (Name of the Procuring Entity) of
……………dated the…day of ………….20……….in the matter of Tender No………..…of …………..20…
REQUEST FOR REVIEW
I/We……………………………,the above named Applicant(s), of address: Physical
address…………….Fax No……Tel. No……..Email ……………, hereby request the Public
Procurement Administrative Review Board to review the whole/part of the above
mentioned decision on the following grounds , namely:-
1. 2. etc. By this memorandum, the Applicant requests the Board for an
order/orders that: 1.
2. etc
SIGNED ……………….(Applicant)
Dated on…………….day of ……………/…20…
FOR OFFICIAL USE ONLY
Lodged with the Secretary Public Procurement Administrative Review Board on ………… day of………....20….………
SIGNEDBoard Secretary
Telegram: “MEDSUP, ”Nairobi KENYATTANATIONALHOSPITAL Tel.: 2726300-9 P.O. Box 20723- 00202-KNH Fax: 2725272 NAIROBI
BANK DETAILS FORM
INSTITUTION/COMPANY NAME:
(1)
(2)
AUTHORIZED PERSONS NAME
POSITION
TELEPHONE NO.
SIGNATURE
DATE
ACCOUNT NO.:
BANK NAME:
BANK CODE
BRANCH NAME:
BRANCH CODE
BANKERS CONFIRMATION THAT ACCOUNT DETAILS ARE AS STATED ABOVE
AUTHORISED SIGNATORY: 1) 2)
BANKERS STAMP:
KENYATTA NATIONAL HOSPITAL
ADDRESS OFFICIAL STAMP
SITE VISIT/ SURVEY CERTIFICATE
TENDER NO: KNH/T/67/2018-2019 Bidders Name: ………………………………………………………………………………………. Address: ………………………………………………………………………………………………. This is to confirm the above noted bidder visited KNH site on……………. at 10.00Am. Bidder’s Representative Name: ………………………………………Sign………………………… Date………………….. KNH Representative: Name: ……………………………….……Sign…………….. Date: ……………………………. This is to confirm the above noted bidder visited KNH site On ……………………………………………………………………………….. Bidders are advised to request for private site visit at the Hospital during the working hours through sending mail to [email protected] or Visiting the supply chain management office’s room no.6
