يحايسلا يومنتلا ارتبلا ميلقإ ةطلس...The current system programmed using oracle form 6i with oracle DB ver.10g Source code is available for forms and reports

PETRA DEVELOPMENT AND TOURISM REGION AUTHORITY (PDTRA)

سلطة إقليم البترا التنموي السياحي

REQUEST FOR PROPOSAL (PETRA - Ticketing Solution)

موعد أقصاه الساعة الثانية عشره من ظهر يوم االربعاء تودع العروض في صندوق العطاءات في

51/1/9152الموافق

Date: 23 April 2019

RFP Ref. 1/9152لوازم

Deadline: 15 May 2019

PETRA - Ticketing Solution - 2019

1 March 16, 2019

Table of Contents

1. INTRODUCTION AND BACKGROUND .............................................................................................................. 3

1.1 BACKGROUND .......................................................................................................................................................... 3

1.2 RFP PURPOSE .......................................................................................................................................................... 4

1.3 RFP OBJECTIVES....................................................................................................................................................... 4

1.4 QUALITY ASSURANCE ................................................................................................................................................ 5

1.5 CLARIFICATION QUESTIONS......................................................................................................................................... 5

1.6 PERIOD OF VALIDITY .................................................................................................................................................. 5

2. DESCRIPTION OF PROJECT ............................................................................................................................. 6

2.1 PDTRA CURRENT ENVIRONMENT OVERVIEW ................................................................................................................ 6

3. SCOPE OF WORK ............................................................................................................................................ 9

3.1 SYSTEM REQUIREMENTS .................................................................................................................................... 10

3.2 MANAGEMENT AND MONITORING ...................................................................................................................... 15

3.3 ADMINISTRATION INTERFACE ............................................................................................................................. 15

3.4 REPORTS ........................................................................................................................................................ 16

3.5 FINANCIAL MANAGEMENT ................................................................................................................................. 16

3.6 INFRASTRUCTURE AND HARDWARE ...................................................................................................................... 17

3.7 THE WINNING BIDDER SHALL .............................................................................................................................. 20

4. DELIVERABLES .............................................................................................................................................. 22

4.1 PROJECT PLANNING & MANAGEMENT ................................................................................................................. 22

4.2 DELIVERING THE TICKETING P.O.S SYSTEM ............................................................................................................ 22

4.3 KNOWLEDGE TRANSFER & TRAINING ................................................................................................................... 23

4.4 MAINTENANCE AND WARRANTY ......................................................................................................................... 23

4.5 DELIVERING SUPPORTED HARDWARE AND INFRASTRUCTURE ..................................................................................... 24

4.6 INFORMATION AND SECURITY ............................................................................................................................. 24

5. TECHNICAL SPECIFICATIONS AND TOR ......................................................................................................... 25

5.1 GENERAL INSTRUCTIONS .......................................................................................................................................... 25

5.2 ADMINISTRATIVE COMPLIANCE .................................................................................................................................. 27

6. GENERAL SPECIFICATIONS ........................................................................................................................... 29

7. GENERAL TERMS AND CONDITIONS ............................................................................................................. 40

8. PRIME CONTRACTOR RESPONSIBILITIES ...................................................................................................... 40

9. OWNERSHIP OF PROPOSAL .......................................................................................................................... 41

10. SUBMISSION OF THE PROPOSALS ............................................................................................................ 42

11. PROPOSAL EVALUATION .......................................................................................................................... 43


2 March 16, 2019

Disclaimer Statement

This document is a request for proposals (RFP) and shall not be construed in whole or part as a direct

or indirect order, or as a request or authorization to perform work or provide goods. The Petra

Development and Tourism Region Authority is under no obligation to award a contract in response to

this RFP‟s proposals.

The information in this RFP is intended to enable the recipient to formulate a proposal in response to

the project requirements set forth. Although this RFP contains adequate information, bidders must

conduct their own independent diligent assessments and investigations regarding the subject matter of

this RFP.

The Petra Development and Tourism Region Authority does not guarantee the accuracy, reliability,

correctness and/or completeness of the information contained within this RFP and any attached

documents. The bidder shall be solely responsible for identifying and requesting any further information

that may be required to prepare a complete proposal.

This RFP shall constitute part of the contract that will be signed between the Petra Development and

Tourism Region Authority and the winning bidder.


3 March 16, 2019

1. Introduction and Background

1.1 Background Petra Development Tourism Regional Authority (PDTRA) is an independent legal, financial and

administrative Authority, founded in 2009, that aims to develop the region, economically, socially,

culturally, and as a tourist destination, as well as contributes to local community development.

The Authority is managed by a Board of Commissioners that consists of five members including the

President and Vice President and a member who is authorized to manage the Petra Reserve, the

members are appointed by the Prime Ministry and approved by His Majesty King Abdullah II.

Main PDTRA Objectives:

Administrate and supervise the Petra Region.

Manage and develop the tourism industry in Petra and coordinate with national and

international entities that are related to the economic sector.

Provide a desirable investment environment to engage in various economic activities.

Contribute to the development of comprehensive strategies for the protection, maintenance

and restoration of archaeological sites, in coordination with the Department of Antiquities.

Identify the areas and sites of heritage value in the region, which can be used for tourism

purposes.

Enhance the social status for the local committee and private institutions, and provide support

to the traditional crafts projects and the tourism industry.

Protect the environment in the region, including water resources, natural resources and

biodiversity, by setting the standards, rules and regulations.

Develop plans for human resource development.

The Petra Development & Tourism Region Authority (PDTRA) is working to capitalize on Petra’s

appeal and enhance the visitor experience in the Petra region. A UNESCO World Heritage site and a

national icon, “Petra is the best-known and most-visited attraction in the Hashemite Kingdom of

Jordan”. Since Petra’s win as one of the New 7 Wonders of the World, visitor numbers have skyrocketed

and demand is expected to increase in the future.


4 March 16, 2019

1.2 RFP Purpose The purpose of this Request for Proposal (RFP) is to identify and select a vendor with a proven

track record in ticketing software solutions, including general ticket sales (Ticket office, online, and

mobile application), subscriptions, patron account management, security, access control, point of sale,

Dashboards, financial and other reporting, staff training and other needs addressed in System

Requirements. The selected vendor must be capable of providing all services, including technical support

and adequate security, back up and business continuity protocols. The PDTRA desires a single vendor for

all services identified in the RFP. The scope of services should include all software, hardware, and

services required to support the implementation, data migration of ticket sales, support, and ongoing

ticket sales.

PDTRA is seeking an individual/organization to lead and manage Analyzing, designing, development and

complete delivery of (E-Ticketing System) that will satisfy PDTRA`s needs by providing detailed

functional non-functional design, and technical specifications of the (E- Ticketing Ticketing Solution) and

delivery system.

The new (E- Ticketing System) should provide the PDTRA management team a method for tracking

entrance and exit of visitors inside the Petra City through electronic gates, PDA's or other innovative

mechanism.

The new ticketing system is intended to enable the PDTRA to better manage visitor flows, regulate rate

of visitor entry to maintain compliance with carrying capacity constraints and allow for timed entry. The

system should also enable sale of add-on services and experiences such as guiding, horse and carriage

rides and other activities. Tickets shall be available online through the PDTRA website www.pdtra.gov.jo

& Visit Petra website www.visitpetra.jo as new E-Ticketing portal.

The vendor should develop a sub internet portal that satisfies the PDTRA’s needs under same domain of

PDTRA current website. Also, Activation online payment is needed using the method of (Visa card) or

other non-refundable credit cards.

E-Ticketing portal should Increase the user access to have online ticket booking by allowing them to

securely quickly and effectively make access.

1.3 RFP Objectives The objective of this RFP is to establish a long-term relationship with a vendor capable of

keeping current with the ticketing industry trends and best practices. The vendor should be capable of

solid accounting, in keeping with the PDTRA’s current and future needs. The vendor should also be

committed to the constant evolution and improvement of the proposed ticketing solution. The new

ticketing solution should strengthen the relationship between the PDTRA, our ticket buyers, our

stakeholders, and PETRA`s visitors.

http://www.pdtra.gov.jo/

http://www.visitpetra.jo/


5 March 16, 2019

1.4 Quality Assurance PDTRA desires a system that will be capable of satisfying its needs for a minimum Five Years.

1.5 Clarification Questions All inquiries in respect to this RFP are to be addressed to the Petra Development and Tourism Region

Authority in writing by e-mail or fax with the subject "RFP Ref, “PETRA-E- Ticketing Solution ". Inquiries

may be addressed only to:

[email protected] or Fax +962-3-2157091, by and may be received no later than first week after announced.

Responses will be sent in writing no later than10 days of announcing.

Table 1 – RFP Schedule of Events:

RFP Event

1 PDTRA Issues RFP

Bidders On-Site visit

3 Deadline for Written Questions

4 PDTRA Issues Responses to Written Questions

5 Deadline for Submitting a Proposal

PDTRA Notifies Short-listed vendors

Vendor Interviews and Presentations

(if needed).

6 PDTRA Completes Evaluations

7 PDTRA Notifies the winning vendor

8 Project Start Date

9 Project Delivery Date

1.6 Period of Validity Tenderers shall be bound to their technical and financial proposals for a period of 120 days from the

submission date stipulated in the RFP document.

mailto:[email protected]


6 March 16, 2019

2. DESCRIPTION OF PROJECT

2.1 PDTRA Current Environment Overview This summary aims at providing a comprehensive view of the current ( E-ticketing system) at the

PDTRA. It also intends to capture and convey the current state of the business using a number of

analytical tools to describe the current business practice and consequently provide bidders with a

complete view of the situation.

2.1.1 Current E-Ticketing system The current system programmed using oracle form 6i with oracle DB ver.10g

Source code is available for forms and reports at PDTRA

Printing tickets using bar code and thermal papers

The current system consists of several screens to control different user permissions and to issue the financial and statistical reports

The current system has screen of point sale that allowed issuing tickets.

After the second week of offering the tender, a tour will be announced about the current system.

2.1.2 Current Process flow

Currently, the ticketing system at PDTRA is conducted by e-ticketing system on site Point of Sale. The

stakeholders involved and their responsibilities are as follows:

I. The PDTRA Are responsible for issuing tickets to visitors

Monitoring tourist entrance to Petra City.

Monitoring and documenting nationality of tourist and other necessary statistics

Request additional tickets from the Department of Antiquities

Receive, store and conduct frequent inventories of tickets on hand

Handle cash from visitors

Deposit cash in Ministry of Finance bank account

Requests additional tickets from the Public Security Department

Receives, store and conduct frequent inventories of tickets on hand

Issues special prices and discounts approvals

Distribution to Beneficiaries


7 March 16, 2019

II. The Ministry of Finance Receives money deposited in bank account and consequently allocate

funds to the involved stakeholders.

III. Water Authority Receives money allocated for the water authority from the Ministry of Finance.

IV. The Visitor Center Collects statistical information on tourists visiting PDTRA.

V. PDTRA Council Legislative body for PDTRA

VI. Audit Bureau Audit and control the ticketing process flow.

VII. The Public Security Department Print serial numbered tickets upon request from DOA

2.1.3 Current Types of Tickets available

A. Ticket Model

1. One Day Ticket The One day ticket is valid for one visit for one day.

2. Two Days Ticket The Two days ticket is valid for one visit each day, for two day subsequently.

3. Three Days Ticket The Three days ticket is valid for one visit each day, for three day subsequently.

B. Service Tickets

C. Free tickets Tickets are submitted to be changed in price & type

2.1.4 Current E-Ticketing Hardware technical Specifications:

Item Description

Gate Alvarado Turnstile Gate

Reader Barcode Reader

Ticket Printer Zebra Ticket Printer (Zebra ZT410, ZM400)

Point of Sale Toshiba POS TxWave

Security Sophos Firewall

Servers HP Servers.


8 March 16, 2019

2.1.5 Current E-Ticketing (Back Office) Screens:

.1 اعدادات الجنسٌات 19 عدد الزوار المتواجدٌن

.2 مكاتب السٌاحة 20 مبٌعات الٌوم لكل النقاط

.3 الجهات المستفٌدة 21 مبٌعات حسب تارٌخ معٌن

.4 اعدادات نقطة البٌع 22 فحص حاله تذكرة

الزوارفئات 23 ادخال الحجوزات للمكاتب السٌاحٌه 5.

.6 فئات العمر 24 تعرٌف شرائح الخصم للبٌع المباشر و المدفوع مسبقا

.7 اعدادات انواع التذاكر)دخول وخدمات ( 25 االستعالم عن رصٌد مكتب سٌاحً

.8 تعرفة التذاكر 26 االستعالم عن ترصٌد التذاكر الغٌر محجوزة

التذاكرتفاصٌل طباعة 27 ارسالٌات الصنادٌق مجمل و مفصل 9.

.10 القطاعات 28 مستحقات الجهات المستفٌدة

.11 امناء الصنادٌق والمشرفٌن 29 مجامٌع مستحقات الجهات المستفٌدة

.12 مستخدمٌن القارئ المحمول 30 مبٌعات تذاكر الدخول والخدمات

المرور و انشاء مستخدم و صالحٌات المستخدم و تغٌٌر كلمه 31 التذاكر الغٌر مستخدمة و المستخدمة تغٌٌر حاله المستخدم

13.

.14 ملف المستخدمٌن 32 تقرٌر مبٌعات المكاتب السٌاحٌة

.15 طاقم العمل داخل الموقع 33 تقرٌر الوصوالت و تفاصٌل وصل

تقارٌر احصائٌة التذاكر/سنوي وشهري / حسب الجنسٌة و فئة العمر و الجنس و الجنسٌة

.16 ملف المركبات 34

.17 سجل الدخول الى النظام 35 تقرٌر حركات الصنادٌق

.18 فحص تذاكر الدخول 36 حركة دخول طاقم العمل

2.1.6 Site visit PDTRA will assign a date for site visit to fully understand the current system work flow and

available infrastructure.

PDTRA will announce on web site for all bidders before one week of site visit date.

Any question or clarification should send before that date to [email protected]

mailto:[email protected]


9 March 16, 2019

3. SCOPE OF WORK

PDTRA is looking for a vendor that can implement a complete solution that covers the E-Services

PDTRA wants to provide by:

Design, develop, test, and implement complete E-Ticketing for PDTRA.

Provide turnkey solution for E-ticket System including (Hardware and Software)

Secure Web Application Software with MS SQL Database

Allowed to connect in secure channel for database and other third party applications (Windows, Android, IOS ,…etc.)

The system shall be innovative means for the public to purchase tickets online for entry into the sites as sub portal under the same domain name of the PDTRA and visitpetra websites.

The bidder shall provide admin portal or management tool that is easy to access and shall able to manage the required services and tickets.

The winning bidder shall design, develop, test, implement and deploy ONLINE system in accordance to specifications. The winning company shall administer and conduct onsite training for the system.

New system should be compatible with JORDAN PASS ticket.

Migrate data from the current database to the new software

The bidder shall provide a Self-Service Kiosk and Payment Machine integrated to the new software.

The system shall provide ticket check mechanism

User-friendly and easy to use by citizens.

Flexible Contact Management.

Secure, Integrated System that provides all best practice capabilities.

Preferred to build the system using latest technologies

5 Years warranty and support.


10 March 16, 2019

3.1 System Requirements

3.1.1 General Specification

Customizable inventory management tool to allow management the capability to add, delete, modify ticketing inventory and business rules.

Automatic generation of a unique confirmation number for each transaction;

The System can generate and print different ticket with different identification mechanism such as (Barcode, QR, RFID, Passport Code, RFID, and/or Magnetics Strip Reader) or any other innovative means may provide by the bidder.

Tickets must be able to interface with electronic reading mechanisms to allow for interface with automatic entry & exit gate system.

The system will enable the public to purchase tickets used for multiple purposes through an online (website) purchase, offsite point of sale system, self-service kiosk & Jordan Pass Ticket.

The bidder must specify the requirements of his application (software and hardware requirements) and type of network layout (Server –Client or split workgroup).

The System Database must be MS SQL.

The System should be web-based application.

The System should provide a simple Arabic & English user interface and easy to use menus for the users.

The system shall provide all reports for tickets, permissions and financial, the reports must be daily, monthly and yearly.

User-friendly and easy to use by citizens.

The transfer of data is important as some data must be uploaded to the CMS.

Dashboards and Reports.

Alerts & Notification functionalities for the needed operations such as approvals and follow-ups. The sub portal shall provide capabilities to send notifications by E mail.

Secure, Integrated System that provides all best practice capabilities.

The sub portal should be built using latest Microsoft web design & development technologies.

Flexible Contact Management.

The System should provide different user level and permission for single and group of users.

The winning bidder is required to deliver the source code of any in-house developed solution, customizations, scripts or batch files that have been developed or provided for the PDTRA project. Additionally, the source code shall contain internal documentation and apply well defined standards to write the source code.

The proposed solution should have high availability technique for servers.


11 March 16, 2019

3.1.2 Point of Sale System Specification

Enable PDTRA operators to make sales onsite at Petra City based on availability, collect payments in cash and by credit card, print multiple ticket types rapidly, and make changes as needed and as authorized through predetermined roles and permissions;

The capability for onsite operators to override some requirements for collecting complete customer information in order to make rapid ticket sales onsite;

The System should be compatible with existing point of sale machine (Toshiba TxcWave with 1NR Recipient Printer)

The System should be fully comply with Passport reader MRZ , and archive scan copy of passport.

The bidder shall provide alternative methods for operating the POS system during emergency and other situations that result in disruption of connectivity with other locations in the country. This offline or other capability must allow field sites to operate the POS system independently for an indefinite period of time, and to process and complete ticket sales in an accurate, efficient and timely manner. Off-line processing of field transactions shall include a mean of collecting and recording payments. The winning bidder shall provide the capability to receive and send data to the central reservation system as soon as the emergency is resolved.

The winning bidder shall physically install the POS system onsite ensuring that connectivity to telecommunication lines are sufficient to support the POS operation. The government may choose to exercise this option at later dates when deploying this system to other destinations.

3.1.3 Online Ticket System

The online ticket reserved by filling a Form with the passport information about user and ticket type in the web site and all related data will be stored through the system database in order to issue ticket and reports.

The online user will be able to press payment button to be redirected to any company does not refund the money (such as visa) to complete the online payment process. Once the payment is done the status will be reflected on the E-ticket system with a paid notice

The online ticket well be check at Point of Sale system through Barcode readers, QR code, Passport code, RFID and/or magnetic strip readers,

After that, the point of sale system issues the ticket from system by passport code reader without enter the data again.

The system should be parameterized software capable to add update delete any type of ticket and ticket prices depending on specific date or duration

Simple, appealing, consistent and intuitive navigation.

Responsive across browsers and devices. The portal must be mobile-friendly for different smartphones and pads.

Correct in all new versions of browsers. The solution supports cross-browser capabilities and work using common browsers.


12 March 16, 2019

Fast-loading with a balance of text and graphics.

The sub portal should provide a simple Arabic and English user interface and easy to use menus for the users.

The CMS should allow PDTRA to send discounts and promotions for companies.

The portal design should comply with PETRA branding and them.

The CMS should have a logs for all transactions on the CMS done by the CMS users.

Individuals Online Login.

Through the online portal anyone can buy the ticket where the process should be as following:

1. The online ticket reserved by filling a Form with the passport information about user

and ticket type in the website and all related data will be stored through the system

database in order to issue ticket and reports.

2. The online user will be able to press payment button to be redirected to any company

does not refund the money (such as visa) to complete the online payment process.

Once the payment is done the status will be reflected on the E-ticket system with a

paid notice.

3. The user should receive confirmation Email.

Local Companies online Login.

For local companies it should register through the portal as following:

1. Submitting the company number in order for the portal to check from either the

companies control department or the ministry of industry, trade and supply - portal

should distinguish from number format - and then extract all other data, also from

companies control department or the ministry of industry, trade and supply.

2. After that, user can register by adding username, password, phone number, and email

address in order to create an account.

3. Account and all related data will be stored through the MS SQL Database in order to

issue reports.

4. User can change the password with verification through SMS.

5. The company can view historical data for the reserved tickets

6. The company can receive offers on the portal.


13 March 16, 2019

3.1.3 Self Service Ticket System

The System should support at least 2 languages. (Arabic, English, Frensh)



Support Credit Card Payment, and Cash Payment.

Support Cash recycler, ability to accept money and return changes to customer

Accepts all Jordanian Dinar denominations and recycles 5 (JD1, JD5, JD10, JD20, JD50)

Generate and print ticket (Same as Point of Sale System)

The System should be fully comply with Passport reader MRZ , and archive scan copy of passport.

The bidder shall provide alternative methods for operating the POS system during emergency and other situations that result in disruption of connectivity with other locations in the country. This offline or other capability must allow field sites to operate the Kiosk system independently for an indefinite period of time, and to process and complete ticket sales in an accurate, efficient and timely manner. Off-line processing of field transactions shall include a mean of collecting and recording payments. The bidder shall provide the capability to receive and send data to the central reservation system as soon as the emergency is resolved.

The System should send alert to the server in case of any error on the kiosk (e.g. paper is near empty).


14 March 16, 2019

3.1.4 Mobile Android Application – (Passes Application) This Android application can be used by tour guide companies or individual tour guides to be

apple purchase one or multi ticket and store digital copy of 2D Barcode in the user profile same as online Ticket application.

The System should support at least 2 languages. (Arabic, English)


Uploaded on Google Play Store


Secure application

Support multi payment method & Generate 2D Barcode.

Support personal or company account & profile

Support personal or company history.

Generate and store 2D Barcode for one or multi tickets.

This 2D Barcode can be used for validation and cash payment on Point of Sale application, also to issue the ticket.

2D Payment Barcode can be used at counter POS to easy load all data and information.

Account and all related data will be stored through the MS SQL Database in order to issue reports.

3.1.5 PDA Android Application – (Ticket Check Application).

Enable PDTRA operators to read ticket’s barcode by using Android handheld PDA

Enable PDTRA operators to validate date and time of tickets.

The system can show all ticket details, ticket type, visitor name, and picture if possible

Online System and synchronized with main ticket system.

Support WIFI and 4G.

3.1.6 Ticketing Solution High Availability Architecture

The proposed solution should ensure an optimal operational performance, even at times of Network disconnection, as following:

Item Description Proposed strategy

Gate High Availability (HA)

Kiosk High Availability (HA)

Point of Sale High Availability (HA)

Servers High Availability (HA)

Network No


15 March 16, 2019

3.2 Management and Monitoring

This solution shall provide the capability to run reports that will identify ticket numbers, entry and exit times, and the original customer information;

Management shall have the capability to run these reports at any time, on a date range basis for any time period;

All system should communicate with a central server that manages and monitors the Point of Sale, Online , kiosks Systems & Android checking system.

Users can login to the management and monitoring server through a web browser.

It is possible to define users and roles with each role having different set of access rights.

The server should provide monitoring dashboards that shows the healthy status of the kiosks.

Configuring the point of sale & kiosks systems remotely through the Administration portal.

Upgrade the point of sale & kiosks systems remotely through e management portal.

3.3 Administration Interface

The solution shall include an Administrative Interface, accessible only by authorized personnel

based on roles and permissions and shall provide the capability to:

Protect all personal and financial data; Provide a user interface for system administrative personnel so that data could be retrieved on-

site and at other administrative locations; Manage actions within the system through the assignment of various roles and permissions with

log-in identification and passwords to a variety of personnel; with appropriate authorization, personnel shall be able to perform the following tasks including but are not limited to:

o Provide management control of all ticketing inventory o Tickets shall be allocated by date and time of entry, management may modify entry

times and quantities per entry time; o Modify maximum number of tickets available (manage carrying capacity); o Override limits within the system; o Modify maximum number of tickets available (manage carrying capacity); o Set, and modify allocations of ticket quantities available for advance sale by ticket type; o Add, remove, and modify ticket types, prices, lengths of stay; o Modify the ticket change time frame; o Modify booking windows; o Override, change and modify fees to new and pre-existing ticket orders;

Customers purchasing multiple day tickets must choose specific dates within a given time frame. The time frame available shall be configurable and may be changed by management.


16 March 16, 2019

Automated generation of a unique confirmation number for each transaction and electronic notification of pertinent information to the customer upon completion of their on-line or contact center transaction.

3.4 Reports

The system shall provide easy access to a variety of reports. Report formats and content will be

negotiated and coordinated upon award. Reports will include operational, financial and statistical

data as defined upon award. The winning bidder shall propose a series of predetermined report

formats and content to include daily operational and financial reports and annual operational,

financial, and statistical reports.

Reports shall be available through an administrative applications to all authorized users; Access to reports will be defined based on user roles and permissions; All data can be queried on a date range basis for a time period of up to many years at a time. Dashboard screen for reports. Graphics and visual reports. Comparison reports reports by peak time

3.5 Financial management

Develop and Support effective and fully operational financial processes that will support the financial information requirements for the archeological sites

These processes shall include recording and tracking of all funds. Funds collected in a single transaction may need to be tracked and/or allocated to separate fund types.

The processes shall also accommodate, but are not limited to, user fee discounts, use of passes, certain group discount transactions, partial payment or deposit options, variable ticket prices, packaging of services, and fee waivers.

3.6 Tickets

The winning bidder should mention the technical specifications for the new tickets that are

compatible with the proposed solution, also provide PDTRA with a sample to test.

List the price of (200,000) tickets.


17 March 16, 2019

3.7 Infrastructure and Hardware

3.7.1 General Specification 1. The provided hardware shall be heavy duty.

2. All communication hardware should be redundant and should be made through

secure channels.

3. Well know brand with reference.

4. The bidder should specify each device and service cost. PDTRA have the right to add

or remove any proposed devices based on item cost provided by tender.

The hardware includes but are not limited to

No. Item Description Qty.

1 Ticket Printer Support 1D/2D Barcode, and RFID. 4

2 Outdoor Electronic access doors. 4

3 Access Control Terminal with RFID and Barcode. 4

4 Rugged Android PDA's (handheld) devices. 6

5 Document & Passport Reader 4

6 Self Service Kiosk 1

7 Any innovative tools needs (bar code printers, recipient printers, RFID readers…etc.) for enhancing ticket issue.

-----

3.7.2 Ticket Printer.

1D/2D Barcode, and RFID

Keep your critical operations running efficiently

The printer should be all-metal frame provides the rugged reliability for extreme

environments.

Support USB, Bluetooth and Ethernet. With optional Wireless Upgrade.

Include LCD Screen for easy configuration.

Manage & monitor all printers for one location.

Space-saving bi-fold door design.

Minimum Solution 203 DPI.

Add RFID capabilities at any time.

Minimum Print Speed 10 ips.

Industrial ticket printer


18 March 16, 2019

3.7.3 Outdoor Electronic Access Doors.

Outdoor use with Enclosure protection rating: IP54.

Resistant against corrosion, UV light, detergents and disinfectants.

Highly resistant to impacts, scratches and abrasion.

Smoothly operating motor drive system for comfortable passage through gate.

Automatic motor driven turning after reception of release signal by gentle hand touch.

2-way operation in entry and exit direction.

Free passage in both directions in case of power outage or alarm signal.

Warning notification in case of forced entry

Serving 35 persons per minute at least

Integrated pulse counter with separate counting for both directions

Integrated drive system for minimum 10 million opening and closing cycles

USB, Ethernet connectivity

The Access control Terminal should be fully integrated with the gate

3.7.4 Access Control Terminal with RFID and Barcode.

outdoor use, Dust protected, Water protected rating: IP 54

Multi-technology reader at the same time

Integrated & Activation of turnstiles, via relay outputs.

Secure data transmission between reader and data carrier

Clearly visible LED light (different colors) for indication of rates and status information.

Support Mobile tickets - 1D and 2D barcodes received by mobile phones.

Support RFID Technology.

Several API protocols for an easy integration with access control and ticketing systems

Large internal memory for offline ticket verification

USB, Ethernet connectivity

The access control terminal should support monitor display for showing door status ,

graphics and videos


19 March 16, 2019

3.7.5 Rugged Android PDA's (handheld) devices.

Rugged design with outdoor usage & protection rating: IP65.

Support 1D/2D Data capture.

Support Camera rear and front, with minimum 8MP for rear camera

Support Wi-Fi, 4G/LTE & Bluetooth.

Android Operating System.

Hot swap battery function.

Display, minimum 4.5”

All required chargers and accessories.

3.7.6 Document & Passport Reader and National ID Reader

Optical document authentication and verification

Accurate, true-color images, with anti-glare technology to reduce document laminate

reflections.

Removable hood for easy document and mobile device placement.

Reads 1D and 2D barcodes from paper and mobile devices.

When a document is placed the reader automatically detects it and initiate optical

reading, MRZ decoding, barcode reading.

Must provide feedback for the user LED (Different color different color) and Audio if

possible.

Jordan National ID scanning and reading .

The multi document scanner shall provide user feedback on read result:

o Visual: highly visible multicolor LED for GO/NO-GO feedback

o Acoustic: volume control buzzer

The reader should have the following Certifications : FCC, CE , WEEE, RoHS

The multi document scanner shall be equipped with:

o Security glass

o scan window glass that is scratch resistant to natural materials

o Scan window with a size to fit any barcode and passport document as the

same

3.7.7 Self Service Kiosk

Touch Screen 17” or 19”.

The kiosk should be Semi outdoor kiosk

Should include Passport & ID scanning, Barcode Scanner

Should Support Ticket Printer to print Barcode and RFID.

Cash Payment:


20 March 16, 2019

o Cash recycler, ability to accept money and return changes to customer.

o Accepts all denominations and recycles 5 (JD1, JD5, JD10, JD20, JD50)

o Cash box: 1400 notes

o Cash entry type: One by one.

o The kiosk can be developed to include coin recycler in the future.

Should be integrated with available Credit card machine (Visa machine or POS)

Should include Passport & ID scanning, Barcode Scanner

Administrator can login to the management and monitoring server through a web

browser.

The server should provide monitoring dashboards that shows the healthy status of the

kiosks.

In case of any error on the kiosk (e.g. paper is near empty), the kiosk sends an alert to

the server. The server logs the event and is able to send an e-mail alert to certain

persons.

The system should be based on Microsoft Technology.

The kiosk is based on Microsoft Windows 10.

The Server is based on Microsoft Windows Server 2012 and MS SQL 2012.

Communication between Kiosks and server is based on TCP/IP.

System administrators and users can login to the server through a web browser.

Should have Kiosk Control Card with Kiosk Control Card Back Panel LED Guide for the

Components, Door Sensor, Impact Sensor, Temperature Sensor, Water Sensor, Digital

Outputs and Inputs, Analog inputs

Should have 1000Va UPS

3.7.8 Any innovative tools needs

Any innovative tools & Infrastructure needs (receipt printers, , RFID readers , network infrastructure ,

network security , cabling , power …etc.) for enhancing ticket issue.

3.8 The winning bidder shall

Deploy a systematic project management and system delivery implementation plan

with pre-defined milestones and deliverables.

Provide source code for inhouse developed software.

Warranty and enhance support for all provided hardware and software for 5 years.


21 March 16, 2019

Provide specifications and suppliers of customizable ticket stock. The ticket stock shall

have at least one perforation in roll form. Electronic identification of each ticket must

be located on the main ticket stub so that multi-day tickets can be used after stubs

have been removed.

The winning bidder shall provide high availability technique for servers.


22 March 16, 2019

4. Deliverables

4.1 Project Planning & Management

The winning bidder shall utilize a systematic project management methodology in order to implement

the required project statement of work. Accordingly, the winning bidder is required to perform the

following activities at the minimum:

Assign a full-time project manager to oversee the project execution together with PDTRA project management for the contract duration. The project manager shall have at least five years experience in project management and shall not be replaced without the PDTRA’s prior approval.

The winning bidder is required to provide and maintain a comprehensive project plan that covers all project management knowledge areas (i.e. scope, quality, communications, time, resources…etc)

The winning bidder is required to provide a detailed time plan that clarifies the major milestones and deliverables, and shall be approved by PDTRA before activation.

The winning bidder is required to provide a well defined communication plan that illustrates the

audience, communication media, and communication frequency.

The winning bidder is required to provide a detailed deliverables distribution and acceptance

plan in regards to system documentation.

The winning bidder is required to provide a detailed Quality Assurance Plan (“QAP”) and final

acceptance procedures of project deliverables pertaining to the system.

The winning bidder is required to provide risk management and issues escalation plans.

The winning bidder is required to provide responsibilities matrix that shall be approved by

PDTRA assign each entities responsibility.

4.2 Delivering the ticketing P.O.S system

The winning bidder shall utilize a systematic system development methodology in order to implement

the required project statement of work. Accordingly, the winning bidder is required to perform

following activities at the minimum:

Analyze and understand the current business requirements of the P.O.S ticketing system and related systems in order to provide a detailed requirement specification document.

Provide a detailed architectural and functional design document with detailed functional, non-functional, and technical specifications of the proposed solution.

Develop, customize, and configure the reservation system in alignment with system requirements and technical specifications.

Perform proper testing of the developed system, which includes but is not limited to:


23 March 16, 2019

a. Unit testing b. Integration testing c. Pre-acceptance testing "alpha testing" d. User acceptance testing "beta testing"

Provide all hardware and tools related to the project including reservation tools and access gates to the site.

All software and hardware should be fully compatible with the PDTRA’s current infrastructure and software environment and tested after installation phase.

The winning bidder is required to deliver the source code of any in-house developed solution, customizations, scripts or batch files that have been developed or provided for the PDTRA project. Additionally, the source code shall contain internal documentation and apply well defined standards to write the source code.

All field P.O.S. system and ticketing hardware shall be controlled and administrated through centralized location (central control point).

All field reservation and ticketing hardware shall transmit notifications to administrators in case of warning or error events.

4.3 Knowledge Transfer & Training

The bidder shall include three courses for IT employees, minimum two employees each

course preferred to be ( Course in ASP.net , Oracle fusion & Oracle Reports Design ) or any other IT topic that will be decided by PDTRA IT .

The bidder shall include a detailed training plan for the stakeholders, system users, technical staff, administrators, and business personnel.

The training provided for each category shall be detailed sufficiently to allow the trainees - to use the system in an efficient and effective manner taking into consideration their duties and responsibilities.

The winning bidder will be responsible for training materials and any other costs related to training.

The winning bidder shall provide on-job training for PDTRA system administrators, developers, and technical staff. The PDTRA assumes that its technical team will participate in developing, customizing, and configuring the required system with the winning bidder.

The training should include a Professional training in all network device PDTRA’s Staff.

4.4 Maintenance and Warranty The Bidder shall commit to provide comprehensive and inclusive support and warranty services

for five years following final delivery of the entire system.

The warranty period will start upon the final acceptance of the delivered system.

The warranty will cover all bugs, errors, or defects in the software and hardware.

The maintenance will include 10 working man-days annually through the maintenance contract. The man-day will be calculated by PDTRA and Winning Bidder Project Managers.

The Bidder shall provide service Level agreement

The warranty services will cover replacement and/or repair of parts due to manufacturing defects or improper installation.


24 March 16, 2019

4.5 Delivering supported Hardware and Infrastructure

To comply with the current infrastructure, the winning bidder is required to perform the following

minimum activities:

Evaluate the existing infrastructure within the PDTRA and provide a high level description of the current infrastructure in order to ensure that the current infrastructure operates effectively with the prospective system.

Advise and supply additional hardware necessary for the system to operate in high availability.

4.6 Information and Security

Evaluate the security of the new applications and infrastructure related to the proposed solution(s) by

doing the following:

Appropriately assess, implement, test and deploy information security controls and measures to secure the System.

Develop Disaster Recovery plan.

Design and build secure connections between clients, the portal, and back-end systems.

Ensure that Portlets are protected against web application threats, such as dangerous URL and attacks such as uploading file, cross-site scripting, Session Hijacking…etc. The solution should ensure that it is not vulnerable to OWASP Top 10 (2013) vulnerabilities listed below, (an assessment report should be submitted in this regard):

Injection

Broken Authentication and Session Management

Cross-Site Scripting (XSS)

Insecure Direct Object References

Security Misconfiguration

Sensitive Data Exposure

Missing Function Level Access Control

Cross-Site Request Forgery (CSRF)

Using Components with Known Vulnerabilities

Invalidated Redirects and Forwards

Conduct a security risk assessment.


25 March 16, 2019

5. Technical Specifications and TOR

Shall, Should, Must & Will: These terms denote mandatory requirements.

May: The term “may” denotes an advisory or permissible action.

Winning Bidder: This term denotes the requirements that the winning bidder will commit to

comply with during the project period

Tenderer, Bidder, Supplier, Vendor: These terms denotes that the requirements that should be

proofed or submitted with the technical offer.

5.1 General Instructions

This document presents the technical specifications and terms of reference for developing and

delivering E-Ticketing system solution & related infrastructure.

5.1.1 An On-Site Ticketing Point of Sales System for the PDTRA The required solution is an onsite ticketing POS system to facilitate ticket sales for the PDTRA; the

solution shall allow dynamic contents (Text, Images, and Variables) to add description site benefited

from the service.

In order to achieve the project main goal, the project consists of the following components:

Component 1: Project Planning & Management

Component 2: e-Ticketing System for the PDTRA

Component 3: Knowledge Transfer & Training

Component 4: Maintenance and Warranty

5.1.2 Hardware Architecture Components Aiming to deliver but not limited the followings:

All network connections and cabling (Internal and external)

The licenses of Data Base application (MS SQL Server per users or per device)

all network terminal for each site (Switches ,Routers ,Firewall ) (If necessary)

Electronic Doors, Bar Code readers, P.O.S terminals …etc

Accordingly, and in align with RFP & Annexes bidders should indicate clearly in their financial offer all

costs related to deliver each Item, which include but not limited to :

Direct Product Cost: Such as the cost related to delivering the software application "either off-shelf or customized software", in addition to the cost of required hardware, licenses, application & required software …etc


26 March 16, 2019

Implementation and professional services Cost: The costs of necessary services required to detailed analysis, design, construction, configuration, test and implement the product in addition to integration , data migration and conversion, training ...etc

Training Cost: cost of the necessary services to deliver courses for training IT staff and end users training.

Support agreement Cost "After sales service"(Optional for PDTRA): The tenderer shall explicitly declare that cost of the annual support agreement cost which maybe singed after the warranty period ended.

Tenderers are invited to submit a sound and clear technical offer, which shows how they are going to

carry out the project activities, accordingly a systematic Project Management Methodology and

Software life cycle methodology should be used, additionally all the specifications tables should be filled,

missing information will result of losing evaluation points.

Tenderers are also invited to submit all information and documentations that shows their compliance

with Technical Specifications (i.e. Technical Documentation of proposed solution, proof of concept "if

necessary", etc.)


27 March 16, 2019

5.2 Administrative compliance

5.2.1 Economic and financial Capacity: The average annual turnover in the last two years of the tenderer must exceed at least one

time the financial proposal of the tender

The average of cash and cash equivalents at the beginning and end of each year are positive for the last two years.

Note: This information should be included in the Company Profile section of the technical

offer.

5.2.2 Professional capacity

At least 15 employees currently working in the company.

The Tenderer should insure that the key persons who work on this project satisfy the following criteria

Project Manager at least 5 years’ experience with minimum 5 years Project

Management experience

Network Administrator at least 5 years’ experience with minimum 3 years relevant

experience

Technical Team Leader at least 5 years’ experience with minimum 3 years relevant

experience

Database Administrator at least 4 years’ experience with minimum 2 years relevant

experience

Web designer at least 2 years’ experience with minimum 2 years relevant

experience

Note: This information should be included in the technical offer.


28 March 16, 2019

5.2.3 Technical capacity of tenderer

The tenderer has successfully completed at least (two) contracts related to the tender he/she

is bidding for, of at least the same value offered for the lot, in the past three years.

Number of employees in company’s payroll, minimum 25 Employees.

The tenderer should be a Microsoft partner.

5.2.4 Project objectives

The tenderer while preparing the technical offer should make sure that the proposed solution will end

up by achieving (but not limited to) the following objective:

The solution shall deliver the service through P.O.S. system onsite and other satellite locations.

The solution shall manage site capacity (number of visitations over time interval) and manage financial and statistical transaction

The solution shall manage entrance and exit flow to/from the site

The solution shall be dynamic and easily manage ticket type, number of services, ticket fees and also the solution shall promote site and site services

And the tenderer proposal shall clearly indicate their compliance to the proposed hardware and

infrastructure herewith or the tenderer should propose the needed hardware and infrastructure that

comply with the proposed solution


29 March 16, 2019

6. General Specifications

6.1 The winning bidder should make sure that the following generic specifications are satisfied for each module of the solution:

Ref # : Required Specifications: Supplied Specifications

Or Ref to Documentations

GR-1 Latest products models are being proposed wherever possible

GR-2 Products road maps are stable with proof.

GR-3 All provided products are 100% compatible with existing PDTRA

hardware and software solutions. "if some are not, kindly identify

and Explain"

GR-4 Solution interoperability with open system

GR-5 Solution is designed for rapid deployment and implementation

GR-6 Solution maintenance and support can be provided directly by

the supplier, if requested.

GR-7 Supplier has the capability to provide 24*7 support to

PDTRA- within 2 hours response time onsite.

GR-8 A bundled Maintenance and Support Service for at least 5 years

should be provided by the supplier for software and hardware


30 March 16, 2019

6.2 Advanced Reservation and On-Site Timed Ticketing system Ref # : Required Specifications: Supplied Specifications


PR-1 The Tenderer "Bidder" should name a dedicated full-time project

manager in order to manage this project; the Tenderer "Bidder"

project manager should coordinate closely with PDTRA project

manager, s/he must have sufficient experience in managing

similar projects, and shall not be replaced without an approval

from PDTRA.

PR-2 The Tenderer "Bidder" should use a proven project management

methodology, which shows the role and responsibilities of the

team, and should fulfill the SDLC (Software Development Life

cycle).

PR-3 The documentation, deliverables and milestones should be well

defined in the provided methodology.

PR-4 The Tenderer "Bidder" should provide an approximate project

plan/schedule that shows the estimated durations and proposed

activities that the Tenderer "Bidder" is going to use in order to

achieve the project goals, the project plan subject of PDTRA

approval

PR-5 Provide a well defined communication plan that illustrates the

audience, communication media and communication frequency.

PR-6 Provide a detailed deliverables’ distribution and acceptance plan

concerning solution documentation

PR-7 Provide a detailed Quality Assurance Plan (“QAP”), and final

acceptance procedures of project deliverables concerning the

solution.

PR-8 Provide risk management and issues escalation plan.


31 March 16, 2019

6.3 The winning bidder should commit to deliver the following reports and documentations: Ref # : Required Specifications: Supplied Specifications


The Winning Bidder should submit the following regular reports for approval during the project performance:

RR-1 Inception report - to be produced during the first month of the

project must include the project synopsis and context, the key

findings of the phase, the project organization, the quality

assurance plan and a detailed project plan.

RR-2 Bi-weekly Progress reports - To be produced for presentation to

the Project Coordination Committee, including the following

information :

Main tasks performed during the period and progress made in the development of the stages.

Key findings and decisions taken during the period.

Risk analysis of the project evolution: incidences, pending decisions, use of resources, schedule progress, etc.

Updated project plan.

RR-3 Final report - to be elaborated at the completion of the project,

the supplier will prepare this report summarizing the key

findings of the project development. The final report will cover

the project synopsis, a summary of project evolution, the review

of project stages and deliverables and a final chapter of the

lessons learned and recommendations.

In addition to regular reports, the winning bidder must submit the following technical reports :

RR-4 Quality assurance plan - To be submitted before the end of the

first month along with the Inception Report, it must include the

quality assurance approach, the description of quality assurance

tools and records and the scheduling of quality assurance

activities.

RR-5 Details design report - It is aimed to provide with the modelling

of the new PDTRA’s solution, including all the modules and

components. The detail design report will specifically include the

solution data model and the detailed network, infrastructure

and database design. The document will be the basis for the

further building and implementation stages of the new solution

and it must include the design principles, the solution

architecture, the overall module design and specification, the

data volumes, frequencies and performance expectations for the

solution.


32 March 16, 2019

Ref # : Required Specifications: Supplied Specifications


RR-6 Implementation plan - Must include the implementation

schedule, the description of stages and tasks and the

development and implementation resources.

Major millstones

RR-7 Training plan - The training plan must describe the required

training modules, the number of people that will need to be

trained and the duration of each training module.

RR-8 Testing plan - the winning bidder will define the testing strategy

and the framework within which the solution testing of the

project will operate. The testing plan will show the main

activities and milestones for project’s testing phase and the

detailed procedures for conducting the software tests and for

the overall acceptance of the solution.

RR-9 Application and infrastructure testing - Different types of interim

module tests will be conducted by the supplier in close

collaboration with the PDTRA. The documents for testing will be

standardized and each and every test done and executed will be

documented and preserved. The test results should be tabulated

and recorded in a structured format.

RR-10 Solution integration testing - A final application software and

solution integration test must be performed. It will supervise the

successful installation of all the solution’s modules and

infrastructure as well as its adequate integration and correct

interaction between each other. At this stage the supplier must

deliver to PDTRA all solution documentation (users,

administrators, etc) and a summary report of all the tests

conducted on the solution and the confirmatory/non-

confirmatory reports generated.


33 March 16, 2019

6.4 For the Hardware equipment’s, the winning Bidder should submit the following reports: For the Hardware equipment’s, the winning Bidder should submit the following reports:

RR-11 Each set of equipment should be provided with an

original set of operating and users’ manuals for all parts

of the equipment. These manuals shall be in English

language

RR-12 Each set of equipment shall be provided with an original

set of technical manuals for all parts of the equipment,

including all accessories. The manuals shall be supplied

English language.

RR-13 The obligatory documents for the provisional acceptance

:

Original certificate of origin by Chamber of Commerce

Report of Final test in the factory (quality control certificate)

Warranty document of the manufacturer and/or the supplier

Submission of reports: All reports should be formally submitted to the PDTRA project manager according to agreed

deliverables management and distribution plan. All reports should be submitted in English, in electronic format as

well as in hard copy.

DR-1 Documentation will be supplied and kept up-to-date

by the supplier during the different project stages. The

Tenderer will elaborate and transfer to PDTRA an

itemized list of all documentation transferred upon

completion of the project.

DR-2 The Winning "Bidder" will provide a minimum set of

documentation for all software including:

Engineering and technical documentation.

Support, operations and maintenance documentation.

End-user documentation. Preparation of end user and procedural manuals.

DR-3 End-user documentation will be provided in

Arabic/English language. The supplier could provide

solution administration and other technical

documentation in English, if such documents do not exist

in Arabic language. Documentation should be available in

electronic format as well as in hard copy, including the

documentation developed specifically for this project.

6.5 Component 2: Delivering e-ticketing system Timed ticketing system Review Section # 3 Scope of work Page # 8


34 March 16, 2019

Ref # : Required Specifications : Supplied Specifications


IR-1 Detailed description of the SDLC should be included in the

Tenderer "Bidder" proposal, with clear definitions of the

deliverables, milestones and major activities.

IR-2 The Tenderer should take into consideration the existing

hardware and information technology infrastructure,

licensees & facilities;

IR-3 All the software solutions, sub-solutions and modules and

hardware delivered to PDTRA should be compatible with

PDTRA current platforms, and IT infrastructure.

IR-4 The Tenderer "Bidder" working team must have proper

technical certifications issued by relevant authorized

institution.

IR-5 The Tenderer "Bidder" Working team must have proper

technical experience, and enough experience in similar projects

as indicated above.

IR-6 The Tenderer "Bidder" should insure that all software

modules are well tested and reliable.

IR-7 The Tenderer "Bidder" should indicate in his/her proposal the

testing techniques and testing tools that s/he is going to use

in the testing process.

IR-8 The winning bidder will make recommendations and training

to the appropriate number and skill of staff required to

operate, support, and maintain the solutions and the

products. Supplier will also make recommendations and

training with respect to the most appropriate operational and

administrative organization necessary to operate, support,

and maintain the solutions and the products.

IR-10 The Tenderer "Bidder" should provide maintenance support

services by means of direct or indirect support for a period of

5 years following the PDTRA’s final acceptance of the project.

The cost of these services has to be included within the scope

of the global price stated in the Financial Proposal.

IR-11 The Tenderer "Bidder" should specify in the Technical

Proposal the scope of the maintenance services they intend to

provide.

IR-12 The Tenderer "Bidder" should also demonstrate in his/her

proposal its capability for providing long-term maintenance

services after the above-mentioned period.

IR-13 The Tenderer "Bidder" must clearly indicate in its Financial

Proposal whether the specialized software is sold or licensed


35 March 16, 2019

Ref # : Required Specifications : Supplied Specifications


to PDTRA; if the software is licensed, Tenderer "Bidder" must

clearly indicate the cost of the license and whether if there is

any annual fee associated to the license

IR-14 The Tenderer "Bidder" must commit to deliver the source

code of all customization, configuration, scripts or batch files

etc, generated for the purpose of this project.

IR-15 The Implementation duration may not exceed 3 Months

6.6 Technical Specifications of an Advanced Reservation and On-Site Timed Ticketing system Review Section # 3 Scope of work Page # 8 Ref # Function: Specifications

F-DE-A1

The solution must be able to add/Update/Delete any

kind of tickets, services and fees as needed.

F-DE-A2

The solution must generate logs for all transaction and

operations.

F-DE-A3

The solution must be able to generate financial and

statistical data report and converted to different file

formats, such as Excel Sheets, Flat files, or reporting

tool.

F-DE-A4

The Back Office staff must able to make discounts,

update fees add, ticket as needed according to

permission and approval process

F-DE-A5

The solution must preserve the privacy the critical

data.

F-DE-A6 The solution must continue in operation (cash

payment )in case network failure, all transaction must

immediately synchronized after service recovery.

F-DE-A7 The solution must have administration side with user

and roles module

And all other needed module to define users privileges

and services (tickets ,services ,fees , discount …etc)

F-DE-A8 Handheld device or electronic doors can read tickets

code for entrance and exit confirmation


36 March 16, 2019

Ref # Function: Specifications

F-DE-A9 The solution should able to generate a report of the

current visitor’s number

6.7 Security F-SEC Security

F-SEC-G General

F-SEC-G1 The solution should enable the administrator to add

and remove users and identify users’ privileges

(include allowable data to access and functions to

perform).

F-SEC-G2 The solution should enable the administrator to

define a set of roles and groups, and the associated

privileges, to append the user to according to their

job needs.

F-SEC-G3 The solution should prevent unauthorized users

from reading or manipulating data, application

resources, devices, etc. that are created,

manipulated, or used by the application.

F-SEC-G4 The solution should prevent authorized users from

accessing and utilizing unauthorized solution

recourses.

F-SEC-G5 The solution must prevent authorized users from

using the solution to perform any function that they

are not authorized to perform.

F-SEC-G6 The solution should enable the administrator to

control and audit the authorized or unauthorized

events and the reconstruction and review of events

that may threaten the company's information

assets. And to provide accountability and audit

mechanism that restricts or remove privileges and

access rights that are abused or misused.

F-SEC-G7 The solution must inform the user when he/ she

makes any changes on the data and alerts the user

for any illegal transactions or operations.

F-SEC-G8 The solution must prevent modification of any data

that are designated as read-only.

6.8: Nonfunctional Specification Matrix: Review Section # 3 Scope of work Page # 8

Ref # : Area: Specifications :

NF-U Usability & Documentation


37 March 16, 2019

NF-U1 All kinds of users (operators, administrative and

power users) must be able to use the solution

efficiently after a reasonable training period.

NF-U2 All tasks (including business, administrative and

operational tasks) must be fulfilled in reasonable

time and click count.

NF-U3 All user interfaces must be consistent, logically

connected, and user friendly

NF-U4 Sufficient user help must be available in all parts of

the solution.

NF-U5 User help and the different kinds of user manuals

must be clear, easy to use, divided into modular

sections, and written in a simple business language.

NF-U6 The Network and solution design and technical

manual should be delivered.

NF-R Reliability

General

All modules and components of the product must maintain acceptable:

NF-R1 Accuracy of processing and output

NF-R2 Availability time percentage

NF-R3 Frequency of failure: expressed in terms of Mean

Time Between Failures (MTBF)

NF-R4 Severity of failure

NF-R5 Recovery time: expressed in terms of Mean Time To

Repair (MTTR)

NF-R6 Bugs or defect rate: expressed in terms of

bugs/KLOC (thousands of lines of code), or

bugs/function-point.

NF-R7 Bugs or defect rate: categorized in terms of minor,

significant, and critical bugs, where “critical” bugs

are not acceptable (e.g., complete loss of data or

complete inability to use certain parts of the

functionality of the solution)

NF-P Performance

General

All modules and components of the product must maintain acceptable:

NF-P1 Solution component shall able to serve at least

8,000 payment transaction daily in term of

Response time for a transaction and Capacity (e.g.,

the number of customers or transactions the

solution can accommodate), Resource utilization:


38 March 16, 2019

memory, disk, communications, printers card

readers ….etc

NF-S Supportability

General

NF-S1 All source code generated for this project must be

delivered to PDTRA along with its proper and full

documentation to be capable of supporting and

maintaining the product in the future.

NF-S2 All source code delivered should be well

documented according to well-known coding

standards.

NF-S3 The solution must provide a user friendly and

effective maintenance utility, which can be divided

into multiple usage privileges.


39 March 16, 2019

6.9 Implementation and Integration Review Section # 3 Scope of work Page # 8

NF-I Implementation and Integration

General

NF-I1 The solution must have a clear and specific

integration schema that defines the following areas:

Hardware Interfaces

Software Interfaces

Communications Interfaces and Protocols

NF-I2 Implement the solution free of bugs, errors or any

disruption, and in align with PDTRA’s current

infrastructure and software environment.

NF-PC Purchased Components

General

NF-PC1 All purchased components (if included) must be

from trusted third parties and well vendor.

NF-L Licensing, Legal, and Copy Rights

General

NF-L1 All software, programs, libraries, components, and

other materials used for the project must be legally

licensed and adhere to copy rights laws.


40 March 16, 2019

7. General Terms and Conditions The PDTRA reserves the right to reject a proposal if the bidder’s acceptance period is less

than 120 days.

The PDTRA will notify the bibbers for On-Site visit and survey tour, so that the bidders can experience the current (E-ticketing system) PDTRA has.

The PTDRA reserves the right to use any proposal including the proprietary information of any organization for the purpose of assisting the PDTRA in evaluating the proposals.

All participating parties shall protect the confidentiality of any identified proprietary and/ or business information obtained as a result of their participation in the evaluation.

The PDTRA reserves the right to sign an agreement without further discussions of the proposal submitted, based on the initial offers received.

The RFP including all appendices and the proposal of the selected contractor will become part of the contract initiated by the PDTRA.

Bidders shall submit their own standard contract terms and conditions as a response to this RFP.

If the contract negotiation period exceeds 30 days or if the selected bidder fails to sign the contract within seven calendar days of final drafting, the PDTRA may elect to cancel the award and award the contract to the next-highest-ranked bidder.

Non-negotiable contract terms include but are not limited to applicable taxes, assignment of contract, audit of records, record retention, content of contract/order of precedence, contract changes, governing law, claims or controversies, and termination based on contingency of appropriation of funds.

Should the winning bidder not submit their deliverable within proposed timeline; the payment amount will be reduced by 200 JD per day (Calendar Day).

Vendors will be notified for onsite demonstrations with PDTRA staff will provide an overview for the proposed solution in advance. This overview will be routed through prescribed features, performances and configurations. Also provide a listing of desired reports and information resulting from proposed solution. These proof-of-capabilities (“POC”) demonstrations are not intended to be a generic demonstration of the application, but rather a demonstration of specific product functionality deemed most critical to the PDTRA using requirements provided by the PDTRA. (If needed )

8. Prime Contractor Responsibilities The bidder shall be required to assume responsibility for all items and services offered in the proposal

whether or not the bidder produces or provides them directly. The PDTRA shall consider the wining

bidder to be the sole point of contact with regard to contractual matters, including payment of any and

all charges resulting from the contract.


41 March 16, 2019

9. Ownership of proposal All materials in any format submitted in response to this RFP shall remain the property of the PDTRA.

Selection or rejection of a response does not affect the ownership of proposals. All proposals submitted

will be retained by the authority and not returned to tenderers. Any copyrighted materials in this

context are not transferred to PDTRA.


42 March 16, 2019

10. Submission of the Proposals

The proposals must be submitted in one original issue marked “original”, and one copy marked “copy”.

All submitted documents, whether original or copies, must be duly signed and executed as stipulated

below.

All proposals, including annexes and all supporting documents must be submitted in a sealed envelope

bearing only:

The address; The reference code of this tender procedure, "RFP Ref." The words “NOT TO BE OPENED BEFORE THE TENDER OPENING SESSION” in the language of

the tender dossier and < ال يتم فتحه قبل جلسة فتح العروض>. The name of the bidder. The original and two copies of the technical proposal shall be placed in a sealed envelope clearly

marked “Technical proposal,” and the original and two copies of the financial proposal in another sealed envelope clearly marked with “Financial proposal”. The tender guarantees (Bid Bond) shall be placed in a third sealed envelope clearly marked “Tender Guarantees”. The three envelopes shall be placed into an outer sealed envelope or container (package).

The original proposals (technical and financial) shall be prepared in indelible ink. All documents shall contain no interlineations or overwriting except as necessary to correct errors made by the firm. Any corrections must be initialed by the person or persons who signed the proposals.

An authorized representative of the firm must initial all pages of the technical and financial proposals.

Bidders are solely responsible for the timely delivery of their complete proposal. Failure to meet the tender submission deadline date and time will result in rejection of the proposal.

A soft copy of each document (on CD) must accompany each hard copy.


43 March 16, 2019

11. Proposal Evaluation

11.1 General Bidders may not contact the PDTRA team or any member of the evaluation committee regarding this

tender, their tendering documents, and/or any other related issues from the time the received

proposals are opened until the final contract is successfully awarded. A bidder wishing to submit any

given information to the PDTRA shall do so in writing at the address indicated in the Data Sheet. Any

effort by the firm to influence the PTDRA and or members of the evaluation committee during the

evaluation and awarding period will result in immediate disqualification.

11.2 Evaluation Criteria The evaluation of the successful proposal shall be based on the highest level of receptiveness to the

PDTRA’s requirements and shall not be solely restricted to the lowest cost proposed.

A proposal to be considered unsuitable shall be rejected if it does not respond to important aspects of

the Terms of Reference or if it fails to achieve the minimum technical score indicated in the Data

Sheet.

The evaluation of the proposals received will be based on a combination of the technical proposal

evaluation, the financial proposal evaluation, and the time frame to conclude the assignment. The

criteria of the evaluation will comprise these key elements with a total of 100 points, which is divided

into several evaluation segments. A proposal which obtains less than 75/100 in the technical proposal

will disqualify and therefore not be evaluated financially.

Evaluation of Technical Proposals (70 points)

The technical proposal will be rated according to the following criteria: Qualifications and competence of personnel;10 pts. Adequacy of approach and methodology; 20 pts. Responsiveness to the TOR requirements; 25 pts Profile of the bidding firm and relevant experience; 10 pts The total time frame for implementing the complete project (maximum permissible duration is 4

months) 5 pts

Evaluation of Financial Proposals (30 points)

Please remember that the pricing component is to be submitted under separate cover.

If the technical proposal achieves the minimum of (75 % * 70), the financial evaluation will be taken into

account in accordance to these guidelines:

The total amount of points for the cost component is 50. The maximum number of points shall be allotted to the lowest fees proposed by the qualified bidders the points for the other proposals are computed by dividing the lowest proposal by each subsequent proposal, and multiplying the result by the total points allocated.


44 March 16, 2019

المناقصة

Appendix to Tender 5/9109لوازم العطاء رقم: تحديث وتطوير نظام التذاكر المشروع:

رقم المادة البيــــان التحديدات

اسم صاحب العمل: عنوانو:

0/0/9/9 0/3و

سمطة اقميم البترا التنموي السياحي ( 98االردن ص ب ) –البترا

اسم الميندس : عنوانو:

0/0/9/4

اسم المقاول: عنوانو:

0/0/9/3 0/3و

% ( من قيمة دخول العطاء 5) التعميمات كفالة المناقصة

%( من قيمة العقد 5) التعميمات كفالة اصالح العيوب

0/0/3/3 مدة اإلنجاز لألشغال

( يوما تقويميا من تاريخ أمر 091) المباشرة

)ــــــــــــ( يوما تقويميا 0/0/3/7 فترة اإلشعار بإصالح العيوب

األردنية السارية المفعولالقوانين 0/4 القانون الذي يحكم العقد

المغة العربية 0/4 المغة المعتمدة في العقد

المغة العربية 0/4 لغة االتصال

المدة التي سيمنح فييا المقاول حق الدخول إلى الموقع

( أيام تقويمية من تاريخ أمر 7) 9/0 المباشرة .

قيمة ضمان األداء قيمة ضمان األداء خالل فترة اإلشعار بإصالح

العيوب )ضمان اصالح العيوب(

% ( من "قيمة العقد المقبولة" 01) 4/9 %( من قيمة العقد ـــ)

مطموب 4/9 نظام توكيد الجودة

6/5 أوقات العمل المعتادة

الفترة المحددة لمباشرة العمل بعد التاريخ المحدد لممباشرة

( يوما، وتعتبر ىذه الفترة 05) 8/0 اإلنجازمشمولة ضمن مدة

( دينار عن كل يوم تأخير 011) 8/7 قيمة تعويضات التأخير


45 March 16, 2019

نموذج اتفاقية العقدForm of Contract Agreement

9109/ 5العطاء رقم: لوازم تحديث وتطوير نظام التذاكر :المشروع

9109. لسنة ...........من شير .......... ......حررت ىذه االتفاقية في ىذا اليوم

بين

.... عمى اعتباره "الفريق األول" .. سمطة إقميم البترا التنموي السياحي.صاحب العمل ........ و

....... عمى اعتباره "الفريق الثاني"................................................المقاول

لما كان صاحب العمل راغبا في أن يقوم المقاول بتنفيذ أشغال مشروع:

صالح أية عيوب فييا وتسميميا وفقا نجازىا وا ولما كان قد قبل بعرض المناقصة الذي تقدم بو المقاول لتنفيذ األشغال وا لشروط العقد،

فقد تم االتفاق بين الفريقين عمى ما يمي: والتعابير الواردة في ىذه االتفاقية نفس المعاني المحددة ليا في شروط العقد المشار إلييا فيما يكون لمكممات - 0

بعد. تعتبر الوثائق المدرجة تاليا جزءا ال يتجزأ من ىذه االتفاقية وتتم قراءتيا وتفسيرىا بيذه الصورة: - 9

........................ "كتاب القبول" -أ ........................ لمناقصة"كتاب عرض ا -ب .................. مالحق المناقصة ذات األرقام: ............... -ج شروط العقد )الخاصة والعامة( -د المواصفات وكما ىو وارد في نموذج استدراج العروض المرفق بطيو . -ىـ

4-د


46 March 16, 2019

( "قيمة العقد المقبولة" ) - 3

يوما تقويميا ( ) اإلنجاز""مدة نجازىا - 4 إزاء قيام صاحب العمل بدفع الدفعات المستحقة لممقاول وفقا لمشروط، يتعيد المقاول بتنفيذ األشغال وا

صالح أية عيوب فييا وتسميميا وفقا ألحكام العقد. وا صالح أية عيوب - 5 نجازىا وا فييا وتسميميا، يتعيد صاحب العمل بأن يدفع إلى إزاء قيام المقاول بتنفيذ األشغال وا

المقاول قيمة العقد بموجب أحكام العقد في المواعيد وباألسموب المحدد في العقد.

عمى ما تقدم فقد اتفق الفريقان عمى إبرام ىذه االتفاقية وتوقيعيا في الموعد المحدد أعاله وذلك وفقا لمقوانين وبناء المعمول بيا.

لثاني )المقاول(الفريق ا

الفريق األول )صاحب العمل(

التوقيع: ...........................................

االسم: .............................................

الوظيفة: ...........................................

................................وقد شيد عمى ذلك:

التوقيع: ...........................................

............................................. االسم:

مجمس المفوضين : رئيسالوظيفة

وقد شيد عمى ذلك: ................................


47 March 16, 2019

)كفالة حسن التنفيذ( نموذج ضمان األداء

Performance Guarantee

إلى السادة: .............................................................................................. يسرنا إعالمكم د كفل بكفالة مالية، المقاول: بأن مصرفنا: ............................................................................. ق

............................................................................ ..........................................................................................................

( / بخصوص العطاء رقم )

................................................................................... بمبمغ: ) المتعمق بمشروع: .. ........................ ( دينار أردني .....................................................

تنفيذ العطاء ..................... وذلك لضمان...................................................................... المحال عميو حسب الشروط الواردة في وثائق عقد المقاولة، وأننا نتعيد بأن

مع ذكر –بمجرد ورود أول طمب خطي منكم المبمغ المذكور أو أي جزء تطمبونو منو بدون أي تحفظ أو شرط –ندفع لكم األسباب الداعية ليذا الطمب بأن المقاول قد رفض أو أخفق في تنفيذ أي من التزاماتو

ى إجراء الدفع.وذلك بصرف النظر عن أي اعتراض أو مقاضاة من جانب المقاول عم –بموجب العقد وتبقى ىذه الكفالة سارية المفعول من تاريخ إصدارىا ولحين تسمم األشغال المنجزة بموجب العقد المحدد مبدئيا بتاريخ ........... شير ............... من عام ................................. ما لم يتم تمديدىا أو تجديدىا بناء عمى طمب

صاحب العمل.

ع الكفيل / مصرف: ..............................توقي المفوض بالتوقيع: .................................... التاريخ: ..............................................

Documents

يحايسلا يومنتلا ارتبلا ميلقإ ةطلس...The current system programmed using oracle form 6i with oracle DB ver.10g Source code is available for forms and reports