Tender Terms, Conditions & Specifications Document for ... · IT & Planning - Executive Department of E-Services - BPM Department 1 Dear Vendor/ Contractor: Please remember that non

IT & Planning - Executive Department of E-Services - BPM Department

1 Dear Vendor/ Contractor: Please remember that non compliance to all paragraphs of this document may disqualify your proposal.

Tender Terms, Conditions & Specifications Document for

Tender No ( 1434/5 )

E-SERVICES INFRASTRUCTURE CONSULTING SERVICE



TABLE OF CONTENTS

STATEMENT OF CONFIDENTIALITY ............................................................................................................... 4

INTRODUCTION ............................................................................................................................................. 4

BACKGROUND ........................................................................................................................................... 4

CORPORATE INFORMATION ..................................................................................................................... 4

BACKGROUND ....................................................................................................................................... 4

BOARD OF DIRECTORS .......................................................................................................................... 4

SFDA MAIN OBJECTIVES ........................................................................................................................ 4

SCOPE OF WORK ........................................................................................................................................... 5

PROJECT MANAGEMENT METHODOLOGY ............................................................................................... 6

METHODOLOGY AND QUALITY ASSURANCE METHODOLOGY ................................................................. 6

SYSTEM STUDY .......................................................................................................................................... 6

DOCUMENTATION .................................................................................................................................... 7

IMPLEMENTATION BY APPIAN .................................................................................................................. 8

DATA MIGRATION AND TECHNICAL REQUIRMENTS ................................................................................. 8

KNOWLEDGE TRANSFER ........................................................................................................................... 9

GOALS AND OBJECTIVES ........................................................................................................................... 9

DELIVERABLES ............................................................................................................................................. 10

TERMS & CONDITIONS ................................................................................................................................ 10

BIDDING INSTRUCTION ............................................................................................................................... 11

CONFIDENTIALITY ................................................................................................................................... 11

PROPOSAL COST ...................................................................................................................................... 11

CONTENTS AND FORMAT OF COMPANY RESPONSE .............................................................................. 11

TECHNICAL PROPOSAL ............................................................................................................................ 12

KEY ASPECTS EXPLANATION .................................................................................................................... 12

EXECUTIVE SUMMARY ........................................................................................................................ 12

COMPANY’S CORPORATE OVERVIEW ................................................................................................. 12

CREDENTIALS & CAPABILITIES ............................................................................................................. 12

SCOPE OF WORK ................................................................................................................................. 13

APPROACH AND METHODOLOGY ....................................................................................................... 13

PROJECT DELIVERABLES ...................................................................................................................... 13

ASSUMPTIONS & LIMITATIONS ........................................................................................................... 13

PROJECT TIMELINE/SCHEDULE ........................................................................................................... 13

PROJECT MANAGEMENT..................................................................................................................... 13

SUGGESTED PROJECT TEAM AND CV’S ............................................................................................... 13



FINANCIAL PROPOSAL ......................................................................................................................... 14

PRECONTRACT ............................................................................................................................................ 14

PRESENTATION........................................................................................................................................ 14

PROPOSAL EVALUATION ............................................................................................................................. 14

PROPOSAL REVIEW ................................................................................................................................. 14

EVALUATION AND SELECTION PROCEDURE ........................................................................................... 15

TECHNICAL EVALUATION ........................................................................................................................ 15

FINANCIAL EVALUATION ......................................................................................................................... 15

FINAL EVALUATION ................................................................................................................................. 15

QUESTIONS RELATING TO THE RFP ............................................................................................................. 16

Tender Terms, Conditions & Specifications ....................................................... اإلشارة المرجعية غير معّرفة! خطأ.

Public Tender General Terms & conditions ........................................................................................... 17

Bill of Quantities ...................................................................................................................................... 21

Bidders’ Compliance Check-List .............................................................................................................. 23

Bidder’s Information ............................................................................................................................... 22



STATEMENT OF CONFIDENTIALITY

The document contains certain proprietary and other sensitive information related to SFDA and its information systems. The Company(s) receiving this document is expected to treat this document and the information stated in the document as confidential and should ensure not to disclose the information or part of the information stated in this document, directly or indirectly, to any unauthorized persons within the firm or other entity without express written consent of SFDA IT department.

INTRODUCTION

BACKGROUND

The IT department in SFDA is issuing this Request for Proposal for the purpose of selecting a qualified contractor to provide Business Process Management (BPM) implementation /framework.

CORPORATE INFORMATION

BACKGROUND

SFDA is leading the effort to establish bases for conducting the regulatory business for food, drug and medical devices of Saudi Arabia. One of the objectives of the new authority is to combine, under one organization, all activities and services related to the above business currently carried out by various government bodies; such as Ministry of Agriculture Ministry of Commerce & Industry, the Ministry of Health, Saudi Arabian Standard Organization (SASO), and the representatives of the Customs and Ports and relevant activities of Municipalities. This approach shall ensure better, faster, more efficient procedures and ensure high quality standards for regulated products. SFDA was established under the Council of Ministers resolution no (1) dated 07/01/1424 H, as an independent body, with a Board Council headed by H.R.H the Crown Prince.

BOARD OF DIRECTORS

The Board of Directors is chaired by H.R.H the Crown Prince, deputy primer, Minister of Defense. The Board also includes H.R.H Minister of Municipal and Rural Affairs as vice‐chairman, all pertinent ministers (HRH Minister of Interior, Minister of Health, Minister of Commerce and Industry, Minister of Agriculture, Minister of Water and Electricity, Minister of Finance, Minister of Higher Education and Minister of Economic and planning), as well as the Director Manager of SASO, the Authority's Presidents, two representatives from the food & drug authority who are specialized in food and drug and four persons from the council of Saudi Chambers of Commerce and Industry.

SFDA MAIN OBJECTIVES



The main purpose of the SFDA establishment is to regulate, oversee, and control food, drug, medical devices, as well as to set mandatory standard specifications thereof, whether they are imported or locally manufactured. The control and/or testing activities can be conducted in the SFDA or other agency's laboratories. Moreover, the SFDA is in charge of consumers awareness on all matters related to food, drug and medical devices and all other products and supplies. The main objectives of SFDA can be outlined as follows:

Observe the safety, security, and effectiveness of food and drug for humans and animal. Observe the safety of complementary biological and chemical substances, cosmetics and

pesticides. Observe the safety of medical devices and its impact on public health. Ensure accuracy and safety of medical and diagnostic devices. Launch clear policies and procedures for food and drug, and plan to achieve and implement these policies. Conduct research and applied studies to identify health problems, their causes, determine

its impact on public, with the consideration of methods for research / studies evaluation. The authority shall establish scientific bases for awareness and consulting services and executive programs in the fields of food and drug. This can be accomplished through the recruitment of experts & specialists or through the partnership with research bodies such as King Abdulaziz City for Science and Technology (KACST) and/or universities research centers.

Control and supervise licenses procedures for food, drugs and medical devices factories. Disseminate and exchange information with local and international scientific and legal

agencies, and setting up a database for food and drug.

SCOPE OF WORK

SFDA is seeking to transform and consolidate its existing systems across different technologies to an Appian based BPM solution called as E – Service Infrastructure, including but not limited to the following high level functions:

HR Management Registration Compliance and Enforcement Licensing Clearance Finance, Billing and Payment Processing IT Internal The Primary objectives of E- Service are: Define a single technology platform (Appian BPM) for managing core business processes

and associated content across the company. Improve processes and operational efficiencies throughout the company, and move towards

a state of continuous improvement Reduce overall operational costs



Enable a move towards a more agile and robust architecture where we can assign ownership of specific functionality to the various software components that are specifically designed for, and best suited to providing those services.

E- Service is expected to be the one-stop shop for all SFDA BPM Processes in future.

PROJECT MANAGEMENT METHODOLOGY

The Respondent is expected to be strong to lead and project manage the implementation of the solution into the SFDA technical and business environment along with existing Appian resources. The activities to be provided shall include the following:

Development of an implementation strategy and plan to achieve the transform.

Development of a comprehensive implementation plan, including work breakdown structure and allocation of required resources.

Project timeline, staging and scheduling.

Prioritize, Manage and Track the tasks.

Project meetings and documentation.

Project reporting.

METHODOLOGY AND QUALITY ASSURANCE METHODOLOGY

The respondent should have proven expertise in establishing right methodology for the

Appian BPM implementation. Also should establish and implement appropriate quality

assurance procedures best suited for a BPM solution. The activities shall include:

Establish an implementation methodology

Plan project as per methodology and define road-map

Establish the different testing phases (unit, Integration, SIT etc)

Define testing strategies and test approach

Plan and Implement the testing phases

Define and implement BPM quality procedures and process

Define and implement BPM/Appian standards and Best practices across the different phases

SYSTEM STUDY



The respondent is expected to have established System Analysis, Business Analysis and Process modeling experience to study the existing systems at SFDA, identify the BPM processes in them, provide appropriate process improvement suggestions and design an Appian based solution. The activities shall include:

Study existing systems across technologies

Identify and record the current-state and to-be state of the systems

Do a due diligence and Identify systems and processes that can be moved to E Service

Prioritize the transformation

Identify BPM processes and document them using BPM notations

Identify process improvement areas and model them

Create Functional Specifications for the to-be BPM solutions

DOCUMENTATION

The respondent should have good documentation skills. The respondent can provide some of

their standard document templates including but not limited to the below:

System Study and Due Diligence

Project Plan and Work break Down structure

BPM Requirements Specification

BPM Technical Specification

BPM Unit test, System test, Integration Test Plan

BPM Work Flow diagrams, BPM Notations

BPM Screen mock-up

User Training Document

BPM Security and Access Control

Appian Deployment Checklist

Appian Standards Document



IMPLEMENTATION BY APPIAN

Implement and rebuild seven existing systems by Appian using all established methodologies (PM

and QA). The six required systems will be as follows:

One large system

Three medium systems

Two small systems

Please refer to the table below for Large, Medium, and Small systems definition:

System Size

Technical Complexity Process Complexity

Integrated Systems

Migrated Data

UI Complexity

Stakeholders Involved

# of Processes

Business Rules Complexity

Large 5+ 20GB+ High 5+ 8+ 8 out of 10

Medium 2 – 4 10 – 20 GB Medium 3 – 5 4 – 7 4 – 7 out of 10

Small 0 – 1 1 – 10 GB Low 1 – 2 1 – 3 1 – 3 out of 10

DATA MIGRATION AND TECHNICAL REQUIRMENTS

The E-Service BPM solution would be implemented using Appian. So the respondent is

expected to have proven expertise in Appian and related components. Some of the key

expectations including but not limited to the below are:

Executed Appian projects involving large scale Data Migration

Executed projects involving Workflows and approvals

Executed projects with different data sources like RDBMS, ERP, XML etc

Executed Appian multilingual projects preferably English and Arabic

Executed projects with extensive document management abilities

Executed projects with interfaces to other systems, databases using Web Services, Messaging service etc

Executed projects with Single sign-on and LDAP features

Payment processing via third party systems preferably using SADAD

Extensive and complex reporting on process data

Executed projects where processes are run as scheduled batch jobs

Provided scalable solutions



Provided backup/disaster recovery plans

Executed projects with Appian mobile based solutions. A lot of SFDA systems are expected to be on mobile

KNOWLEDGE TRANSFER

SFDA intends to reduce reliance on vendors and external consultants and become self-

sufficient as soon as possible. As part of the implementation process, SFDA would like our

technical personnel to become familiar with the application in the following areas:

Application programming, including but not limited to development tools, utilities,

queries, interfacing mechanisms, etc.

Data structure and object model

Application and database administration

User setup and maintenance

During the course of the implementation, we will need to be able to understand how the

capabilities offered by the solution can best be utilized by SFDA going forward. In order to

continue with process improvement exercises after the completion of the initial

implementation, our business analysts must develop knowledge in the following areas:

Process modeling & design features

Business rules implementation and maintenance

Defining, monitoring and reporting on process metrics

Human and system interfacing features and options

GOALS AND OBJECTIVES

The goal of this project is to acquire the services to implement a Business Process Management (BPM) application/framework with primary focus on human‐centric workflows in addition to system‐to‐system processes.

The objective of this project is focused on BPM application/framework and integration through existing and yet‐to‐be‐developed applications.

It is the objective of SFDA to separate process rules and controls from the business component using Oracle Business Rule Engine.



It is the objective of SFDA to separate process management functions from presentation and structured data interaction. To have a single portal that hosts only application –no content management is required. The single portal will host all SFDA’s future application and processes. All excising application will be re‐designed to run under this portal in the future.

DELIVERABLES The following shall be the deliverables for this project for every phase (including but not limited to

the below list)

Project Plan

Work Break Down structure & Estimates

Functional Specification

Design Documentation

Process Models

Test Cases for applicable testing phases

Training documentation as required

Appian Standards Document

Deployment Document

Status Reports

Six implemented systems using Appian

TERMS & CONDITIONS

The project should be planned for delivery in 12 months. There is no hardware should be delivered through this project. SFDA shall not be liable for any cost or expenses whatsoever incurred by the companies in the preparation of their proposals, or for attendance at any meeting related to this RFP. Non‐compliance with the requirements stated in this RFP will result in disqualification of

the proposal. SFDA shall have the right of selecting the implementer team, and if any member

dissatisfies SFDA, SFDA will have the right to ask for a replacement without any justifications.

SFDA reserves right to award contract to one or multiple vendors as deemed appropriate based on its assessment of best possible approach to meet SFDA requirements.

SFDA will provide appropriate personnel for the implementation of this project. SFDA will designate a Project Manager from its side, who will serve as the primary liaison between the SFDA and the companies and will coordinate overall management and administration of the project.



The Company's project manager, once assigned to the SFDA project, will not be changed or reassigned for another project without SFDA written consent.

The Company must replace any project staff that does not meet the SFDA’s expectations of professionalism and experience.

The Company must provide all documents related to this project, all deliverables, presentation, executive summaries in soft and hard copies. The soft copy should be in an editable format and SFDA reserves the right to modify any of those documents.

The Company should adhere to all governmental policies, regulations, and procedures. SFDA e-services will be on Appian 7.0; therefore, SFDA wants to migrate all existing service

(.net) to Appian. The bidder has to be an authorized Appian partner. The assigned team to this project has to be Appian certified team. The bidder must have experience in projects done by Appian in Saudi Arabia. A list of references for previous Appian projects in Saudi Arabia must be provided. The bidder must adhere to SFDA’s security and integration policies. Requirements gathering, analyses, and implantation phases have to be done in-site at SFDA

location. Implementer’s employees are required to commit to SFDA’s working hours (7:30 AM to

3:30 PM).

BIDDING INSTRUCTION

CONFIDENTIALITY

The document contains certain proprietary and other sensitive information related to SFDA and its information systems. The Company(s) receiving this document is expected to treat this document and the information stated in the document as confidential and should ensure not to disclose the information or part of the information stated in this document, directly or indirectly, to any unauthorized persons within the firm or other entity without express written consent of SFDA IT department.

PROPOSAL COST

SFDA shall not be liable for any cost or expenses whatsoever incurred by the companies in the preparation of their proposals, or for attendance at any meeting related to this RFP.

CONTENTS AND FORMAT OF COMPANY RESPONSE

The proposal shall consist of the complete response to the SFDA requirements and must be submitted (an original and two copies) on paper (hard copy) and on soft copy (via email). The hard copy will be used by SFDA to facilitate and expedite the review process. No other distribution of the proposal shall be made by the Company. The Company's proposal must contain a cover letter, on an official company letterhead, with an original signature(s) of authorized signatories to bind the Company to the provisions of this RFP. Proposals shall be prepared in standard format, providing a straightforward, concise description of the Company's ability to meet the requirements of the SFDA and should address only those services requested. Each original/copy of the proposal should be submitted in the following format:



Technical proposal package. Financial proposal package.

TECHNICAL PROPOSAL

The Technical proposal should contain sufficient details and information that will meet requirements as described in this document. At a minimum, the following key aspects should be addressed by Company in their technical proposal. Following key aspects should be addressed by Company in their proposal:

Executive Summary Company’s Corporate Overview Company’s Related Credentials and Capabilities Scope of work Approach/methodology Assumptions and Limitations (if any) Project Deliverables Project Timeline /Schedule Project Management Suggested Project Team and CVs.

KEY ASPECTS EXPLANATION

EXECUTIVE SUMMARY

Include an overall summary of the technical proposal.

COMPANY’S CORPORATE OVERVIEW

Background information and profile of the Company shall clearly illustrate that the Company has the experience in the area relevant to this RFP. The Company shall provide:

Company complete name and address and Company local office address. The company size. Number of employees. A short narrative description of the company’s organization. Principle type of business and total number of years in business. Technical licenses or certificates of offered services and products. Description of the Company's ability to provide the proposed services to SFDA.

CREDENTIALS & CAPABILITIES

The SFDA requires that the Company has previous experience(s) in designing and developing the required infrastructure and implementation plans. The Company shall provide:

A description of his previous experience(s) in similar projects.



References: The Company shall also provide a list of references where the Company has performed similar assignment. The references should include name, address, and the contact member of the client as well as a brief description of the scope of work performed.

SCOPE OF WORK

The Company shall illustrate in details the proposed scope of work it will be required to deliver to SFDA. The proposed scope of work should be in line with SFDA requirements stated in this RFP. APPROACH AND METHODOLOGY The Company shall illustrate the approach it plans to undertake for executing the project. The Company should illustrate overall approach as well as approach for specific subprojects that shall be delivered to address SFDA requirements. The approach should clearly highlight various sub‐projects and specific phases of the projects, work to be carried out in each project/phases etc and key deliverable that will be produced to address SFDA requirements. PROJECT DELIVERABLES

The Company should clearly illustrate key deliverables that shall be produced during the project and expected time schedule of delivery.

ASSUMPTIONS & LIMITATIONS

The Company may illustrate key assumption that it considers to be applicable to the project. Further, the Company may also illustrate key limitations that it considers applicable to its project delivery. PROJECT TIMELINE/SCHEDULE

As part of the proposal, the Company should include a high level project plan for the project highlighting its various phases and sub‐phases and their estimated duration. PROJECT MANAGEMENT

The Company shall follow an internationally recognized methodology for project management. The Company shall describe in his proposal his approach to manage this project including Project Management structure, Project management roles and responsibilities. Key Project Management Processes including Quality Assurance Processes to be used by the Company. SUGGESTED PROJECT TEAM AND CV’S

The Company shall include the resume of experts who will be assigned to the project. The SFDA requires that competent, experienced and highly skilled experts shall be provided in line with the specific requirements of the projects. However SFDA reserve the right to approve or reject the CVs.



Every suggest project member shall be supported with the following information:

The suggested role List of related previous projects that he worked in. For each of those related project provide

the following: • Size of the project (if available). • Number of your team in the project. • His role in that project.

FINANCIAL PROPOSAL

This portion of the proposal must be identified as the financial proposal package. Financial Data is defined as any information related, directly or indirectly, to the Company's proposed charges for services and deliverables. When preparing the financial proposal, the Company shall consider the following:

Financial Data must not be presented in any portion of the technical proposal. Financial Data consist of, but not limited to, costs, fees, prices, rates, discounts, or

identification of free service, labor or materials. All prices must be in Saudi Riyals(SAR) All prices shall include all costs including shipping, handing, customs, and import duties. Manner and mode of payments of the contract shall also be specified. The Company should breakdown the costs to match each deliverable in the technical

proposal.

PRECONTRACT

PRESENTATION

Companies may be required to provide presentations on the contents of their proposals prior to the selection of the winning Company; these presentations will be conducted on the SFDA premises. SFDA reserves the right to visit the Company premises and/or to request more clarification, if required.

PROPOSAL EVALUATION

This section provides an overview of the evaluation process.

PROPOSAL REVIEW

All proposals received from companies will be reviewed and evaluated by the SFDA evaluation committee. The SFDA evaluation committee will recommend for selection the proposal which meets the project requirements. After all technical and financial aspects are evaluated, SFDA, at its discretion, may eliminate proposals which did not meet the SFDA basic requirements.



EVALUATION AND SELECTION PROCEDURE

SFDA operates a competitive tender procedure and usually invites a number of suitably qualified Companies to submit proposals and awards contract(s) to the Company(s) whose services and/or solution best meets SFDA’s requirements. The evaluation and selection procedure typically involves the following activities:

Forming the Evaluation Committee. Receiving of responses. Preliminary evaluation and formulation of a shortlist of Companies. Evaluation report. Contractual negotiations. Determination of best option(s). Selection of Company. Announcement of successful Company.

TECHNICAL EVALUATION

Each proposal will be evaluated based on the response to the RFP and through the application of specific criteria designed by the SFDA. A proposal might be rejected at this stage if it does not respond to these specific criteria. Some key aspects that will be considered by evaluation team include:

Alignment of proposed scope in line with SFDA requirements. Clarity and adequacy of proposed deliverable of the project. Quality and adequacy of proposed vendor approach for executing this project. Proposed Timeline/ Duration of the project. Company's capabilities, qualifications and experience in projects of similar nature. Company’s ability to complete the requirements and work on time for this project, and the

detailed action plan including suggestions of schedule for implementation. The qualifications of the Company staff who will participate in this project, which includes,

among others, the general qualifications of the staff, relevant education, training, experience, familiarity with the region and language.

Regional presence of the Company office.

FINANCIAL EVALUATION

Financial proposal will be evaluated based on the prices quoted by Company for proposed services. SFDA will evaluate the financial proposal after the technical evaluations are completed. Financial proposal package score will be added to calculate the final score for each proposal. The proposal with the highest score will be recommended for selection by the SFDA as a winning Company.

FINAL EVALUATION

Proposals will be ranked according to their combined technical and financial evaluation score. The companies achieving the highest score will be short listed and contacted for further negotiations.



Based on the outcome of the negotiation process the Company offering the best overall solution to SFDA shall be awarded the contract.

QUESTIONS RELATING TO THE RFP

Companies who have technical questions regarding this Request for Proposal are kindly requested to direct them to: MR. ABDULLAH AL-HAQBANI BPM and Integration Director EMAIL: [email protected] ADDRESS: IT General Department E-Services Executive Department/ BPM and Integration Department

3292 Northern Ring Road – Al Nafel Area Riyadh 13312 – 6288 Kingdom of Saudi Arabia



Public Tender General Terms & conditions

1. Proposals shall be submitted in sealed envelopes marked with Tender Name. All

proposal pages shall be stamped with the official bidder’s stamp and delivered by the

bidder or his official representative to Contracts & Purchases Department or by

registered mail to 3292 Saudi Food & Drug Authority - Contracts & Purchases

Department- Northern Ring Road – Riyadh 13313-6288, no later than the specified

date.

2. The proposal shall be considered cancelled if any of its pages is not stamped by the

bidder

3. The proposal shall be considered cancelled if it is submitted after the specified date.

4. Prior to preparation of his proposal, the bidder shall investigate and make himself

familiar with the nature of the works to be executed, associated execution conditions ,

detailed information of works and the risks that may affect his proposed prices and

obligations.

5. The bidder shall submit together with his proposal, an initial bank letter of guarantee

(Bid Bond) to the amount of 1% to 2% of the total value of the project and valid for

ninety (90) days from the date of opening of envelopes . If the contract is awarded to

the bidder, he shall submit a final bank letter of guarantee to the amount of (5%) of

the total value of the project , within ten days from the date of the letter of intent.

6. In split tenders, the amount of the bid bond shall cover the total value of the proposed

items. Split bid bonds shall not be accepted

7. The bank letter of guarantee shall be issued in the bidder’s name

8. Preference shall be given to national and local products and other countries products

and services of the same category, if the proposal are equal.

9. Prices shall be quoted in Saudi Arabian Riyals

10. Saudi Food & Drug Authority shall have the right to cancel or reduce the quantity of

some items, in required.

11. If any of the special conditions of the tender requires that samples must be submitted,

then the proposal shall be considered incomplete if such samples are not submitted

with the proposal.



12. The following valid official documents shall be submitted:

a. Copy of Zakat & Income Certificate

b. Copy of Commercial Registration or License

c. Copy of Chamber of Commerce & Industry Membership Certificate

d. Copy of GOSI Certificate

e. Copy of Labor Office Certificate (Saudization)

f. Investment License, if the bidder is licensed according to “Foreign Investments “

Regulations

g. Contractor Classification certificate in the field of proposed works, if the value of the

contract requires classification certificate according to the provisions of Contractor

Classification Regulations

13. The Financial proposal shall be submitted in a separate envelope containing the

following:

a) A letter from the bidder specifying the total value of t he project

b) The required Official Documents.

c) Original Tender Condition & Specifications Document including completed Bill of

Quantities, with all pages duly stamped

d) A Compact Disk (CD) including all the above in a (PDF) file

14. The Technical proposal shall be submitted in a separate envelope containing the

following:

a) Copy of Tender Condition & Specifications Document with all pages duly

stamped, without mentioning prices

b) Catalogues ( if available or required by the special conditions)

c) A Compact Disk (CD) including all the above in a (PDF) file

d) Copy of Contractor Classification certificate in the field of proposed works, if the

tender or contract value requires classification certificate according to the

provisions of Contractor Classification Regulations

e) All requirements of the special conditions of the tender



15. In tenders where Contractor Classification certificate is required, proposal may be

submitted by a contractors consortium (joint venture), according to contractors

consortium classification conditions referred to in the Contractor Classification

Regulations, provided that th e following shall be observed:

a) The joint venture must be established before submission of the proposal, by virtue

of an agreement signed by the parties of the joint venture and attested by the

authorized authentication entities e.g. chamber of commerce & industry.

b) The joint venture agreement shall state that the joint contractors shall be r

collectively or individually committed to execute all required works and services by

the tender

c) The joint venture agreement shall specify the legal representative for both parties in

front of the government entity in order to finalize thee contracting process, sign the

contract and undertake responsibility of signatures and communication with the

respective government entity

d) The tender documents shall be signed and stamped by all joint venture parties.

Original joint venture agreement shall be attached to the proposal

e) None of the joint venture parties shall submit individual proposal, nor enter in a

joint venture with another bidder for the same project.

f) The joint venture agreement shall not be changed after submission , without the

approval of SFDA

16. Omission , erasure or deletion in prices list is not allowed. The bidder shall not delete or

make any change in any form, on any or other items. Any correction thereto shall be

made by re-writing in figure and words and appropriately signed and stamped by the

bidder. If the bidder is interested to make any additional special conditions, he shall

state them in a separate letter attached to his proposal, and refer to this letter in the

same proposal.

17. If the prices that have been subject to change, omission or erasure exceeded 10% of

the price list, the proposal may be ignored

18. The bidder shall not ignore or skip any item of the bid without providing prices , unless

it is otherwise allowed by the split- tender provisions

19. If any field of the bill of quantities is left blank, it shall be loaded to the total value of

the proposal, and is considered as approved by the contractor



20. The bid selection committee may recommend to reject the proposal if the prices

calculation errors, after corrected, exceeded 10% , mor or less, of the total value of the

bid, according to Articl 32-d, of the Implementation Bylaws of the Government Tenders

and Procurements Regulations.

21. SFDA may split this tender, wherever splitting achieves its best interests

22. SFDA shall have the right to audit the proposed prices in unit or total and make the

necessary material corrections. If any difference is found between the price in figure

and the priced in words the prices in words shall prevail. If any difference is found

between the unit price ant the total price, the unit price shall prevail.

23. The bill of quantities shall be filled out in ink and stamped on each page.

24. The quoted prices shall be inclusive of all expenses

25. Alternative offers are not allowed unless it otherwise provided in the special conditions

of the tender

26. SFDA may increase or decrease the quantity of the item in the percentages specified in

the Government Tenders and Procurements Regulations, during the validity of contract

period.

27. The validly period of the proposal shall be three months from the date of envelopes

opening

28. SFDA shall have the right to reject any of the delivered items if it is found that it does

not comply with SFDA conditions and specifications to which the bidder has committed

to in his proposal

29. If the contractor violated any of his contract obligations , he shall be subject to the

penalties and fines provided in the Government Tenders and Procurements Regulations

and its implementation Bylaws

30. Any items that are not covered by these terms and conditions shall be subject to the

provisions of Government Tenders and Procurements Regulations, issued by the Royal

Decree No. M/58 dated 4/9/1427H and its implementation Bylaws issued by H.E.

Minister of Finance Decree No. 362 dated 20/2/1428H



Bill of Quantities

No. Description Unit Quantity Unit Price Total Price

1 Establish Appian Project Management Methodology

Methodology 1

2 Establish Appian Quality Management Methodology

Methodology 1

3 Current Systems Evaluation Consultation 1

4 Document All systems Planed to be converted to Appian

Consultation 1

5 Plan to migrate all data in current system to the planed systems

Consultation 1

6 Large System Implementation 1

7 Medium System Implementation 3

8 Small System Implementation 2

Total Gross:



Bidder’s Information

Total Cost in Figures: ……………………………………………………………………………………………....................

Total Cost in Words: ……………………………………………………………………………………………………………….

Name of Company / Establishment:…………………………………………………………………………………………….

Name of Company / Establishment Manager……………………………………………………………………………….

P O Box No. (………………..) Zip Code: (……………..) City: (………………………………………………………………..)

Mobile No. (………………………………………………………………………..)

Telephone No. (……………………………………..) Fax No. (……………………………………..)

Official Stamp of the Company / Establishment:



Bidders’ Compliance Check-List

(To verify completeness of proposals)

No Item Bidder

1 Original Bid Bond ( )

2 Partnership of Joint-venture Agreement ( )

3 Copy of evidence of Commercial Registration (C.R) or approved License ( )

4 Copy of evidence of chamber of commerce & industry membership ( )

5 Activity schedule and detailed bill of quantities ( )

6 Copy of Zakat & Income Clearance Certificate ( )

7 Copy of GOSI Registration Certificate and payment of GOSI dues ( )

8 Copy of Investment License, if the bidder is licensed according to Foreign Investments Regulations

( )

9 Copy of meeting Saudization Percentage from Labor Office (Saudization Certificate)

( )

10 Are all documents duly stamped by the bidder ( )

11 Are the technical proposal and financial proposal seperate ( )