Beruflich Dokumente
Kultur Dokumente
The Contractor is to supply and install a Flight Information Display System (FIDS) to make flight
information available for information display purposes. The primary functions required from the
FIDS are:
The scope of Works includes Contractor design, manufacture, procurement of equipment and
software, transportation, storage, installation, testing and commissioning of the FIDS including
training of the Employer’s staff for the operation and maintenance. Particular requirements are
presented below:
A. The FIDS shall be suitable for serving 1MPA (Million Passenger per Annual), and
support at least 100 display clients.
B. The Contractor shall obtain all necessary governmental or regulatory approvals.
C. The Contractor shall co-ordinate the entire necessary interfaces with all other works and
all other (sub) contractors.
D. The number of required FIDS displays are as follows:
E. The Contractor shall provide all the necessary fixture for the installation of FIDS displays,
including wall mount bracket, suspension bracket, floor stands and housing etc.
F. The location that each FIDS display shall be provided are indicated as follows:
Departure
Wall Mounted / 37” Baggage Claim
Floor Stand / 42”
Check-in Counters
Ceiling Suspended / 37”
Arrival Departure
Departure Wall Mounted / 42” Wall Mounted / 42”
Wall Mounted / 42”
Arrival
Wall Mounted / 42”
Departure
Wall Mounted / 42” Arrival
Wall Mounted / 42”
FIRST FLOOR
Departure + Arrival
Departure + Arrival Wall Mounted / 42”
Wall Mounted / 42”
Boarding Gates
Ceiling Suspended / 37”
Departure
Wall Mounted / 42”
Departure Arrival
Wall Mounted / 42” Wall Mounted / 37”
Departure
Wall Mounted / 42” Departure
Wall Mounted / 37”
Departure
Wall Mounted / 37”
SECOND FLOOR
The Contractor shall submit the following information during the Project:
The FIDS shall be based on modern and widely accepted processing principles to minimize the
investment and to avoid special development or integration. The following design concepts must
be incorporated in the proposal.
A. Packaged Product:
Manual operation must be minimized and centralized in AODB; the core system of
Airport Special IT Systems, and manual input and intervention for FIDS must be
minimized. Essential information for airport operation such as flight master table, flight
movement updates and airport resource allocation shall be maintained in AODB and all
the relevant information shall be replicated to FIDS without human intervention.
Since collaboration between each components of Airport IT Systems plays most valuable
role in the modern airport operation, and thus “packaging” of the systems as a whole is
the key approach for the successful deployment of Airport Special IT systems. Therefore,
FIDS and AODB to be implemented for PIA shall be one packaged product that has been
thoroughly integrated and available on the market for at least 10 years.
All the functional requirements stipulated in the following chapters shall be natively
supported by the base product and any special customization, alteration, development or
integration to satisfy these requirements will not be appreciated in order to secure the
stable operation and high availability, and to ensure that sufficient and continued
maintenance activities such as applying security updates to eradicate any system
vulnerability and software upgrade to comply with up to date international regulations
and standards shall be provided throughout the system lifetime.
The architecture of the system must be based on open system and market standards. This
must take into account:
TCP/IP protocol,
Standard development tools such as JAVA, MS ASP etc.,
Browser clients with no specialized software.
C. Security Module:
Users must be registered on the system before access is allowed. A unique identification
and encrypted password, modifiable by the user must control access. System functions
must be assigned as per each registered user to prevent unqualified actions.
Servers shall provide redundancy and/or load sharing thus a set of multiple servers fully
replicated are required. Additional servers can be added in the future to increase capacity.
Within the FIDS, any given device shall be configured to determine if there is
connectivity to its pre-defined primary server. If the primary server is not available, the
device shall automatically connect to an alternate server to update or retrieve the
information as required. For this purpose, the load of the FIDS must be controlled and
appropriately distributed among servers, to ensure that there is not a single point of
failure.
E. Remote Support:
It must be possible to restart the application locally as well as from a remote location.
Facilities must exist to allow third-level support to access and maintain application
processes.
F. System Monitoring:
It is required that all critical components of the system, hardware and software, be
monitored programmatically so that any actual or potential system malfunctions shall be
notified immediately via email, SMS or SMTP to other monitoring facilities.
G. Event Driven:
H. Expandability:
The FIDS shall meet the requirements for the expandability in the foreseen future. Once
installed the users should be able to easily expand and enhance the system by adding
servers, workstations and software modules as required.
The display device client must operate on widely accepted web browsers with no
specialized software.
The Contractor shall design a system that includes all the hardware, software, peripherals, and
networking necessary to operate and maintain a fully functional FIDS. All the requirements given
present the minimal acceptable requirements for the system.
5.1 SERVERS
A. Hardware:
1. Microsoft Windows Server 2012 R2 or newer product with latest Service Pack
2. Microsoft SQL 2014 Standard Edition or newer product with latest Service Pack
3. Internet Explorer 10.0 or later
A. Hardware:
C. 16 million colors
A. The most current version of Microsoft SQL, at the time of implementation, shall be used
to support the database.
B. The software shall be well documented for maintenance purposes and designed using a
modular approach that allows for easy configurations and future growth of the system.
C. The FIDS front end shall use a Graphical User Interface (GUI).
5.5 PERFORMANCE
A. The FIDS shall be designed to support the operational, functional, and performance
requirements for the overall capacity and peak hour capacity of the Airport to include the
operational requirements of the Airport. All software and network devices shall perform,
without degradation, at the scheduled periods and response times for the FIDS to be
considered available. All systems shall operate 24x7.
B. As the FIDS is a critical component for distributing information of the airport operation,
it is essential that the FIDS system maintain a high availability. The FIDS shall be
available at least 99.99 percent of the time. Being available should mean, the server and
workstation are fully functional.
C. The time required to restart and resynchronize the FIDS servers after a complete system
failure shall not exceed Fifteen (15) Minutes. In the event of a power outage, the
dedicated UPS shall take over immediately.
In principal, the entire dynamic information including flight schedule and resource use
such as aircraft stand, check-in counters allocation, boarding gate assignments and
baggage conveyor, as well as all these updates shall be automatically replicated from
AODB. Manual intervention shall be limited to the additional information input
described below or in case the information feed from AODB is somehow suspended.
B. Human Inputs:
A number of functions at the airport will have access to workstations where personnel
can show additional information which is used to enrich the information related to the
airport operation such as emergency alerting and PA. The personnel who have access to
these facilities are either airport officials, airlines or designated personnel from other
FIDS shall fit into the overall airport information distribution system as the output media to the
different organizations that operate at the airport as well as to the public using the airport. There
are a number of high-level system requirements that are important:
Assembly of information
Formatting of information
Mixing of channels
Assigning channels to devices
Manual information input
Display system statistics
Display system monitoring
A. Assembly of Information:
1. The display system must select different information elements and assemble display
pages for the different areas of the airport such as public concourse, departures gate
lounge, baggage claim, arrival lobby etc.
2. Some of these information elements are linked to flight movements and flight status
changes must be reflected. Other information elements are notices that may change
as time progresses. Depending on the display area, information such as
advertisements can also be displayed.
3. The display system must have the level of parameterization to allow administrator to
set-up the assembly rules for the different displays. Once the data elements have
been assembled, they need to be formatted.
B. Formatting of Information:
1. The information display system must format the assembled display pages
appropriately for the different displays. This formatting needs to be done with
different templates to allow for the inclusion of graphics as well as other static and
system data elements such as airline logos, clock and header information.
2. A specific selection of information may have to be formatted with different
templates to allow for different display types.
3. The formatted information, ready for display, needs to be mixed together.
C. Mixing of Channels:
1. The majority of the information used by the display system is received from AODB;
however, there are a few areas where the information display system should allow
for manual input:
a. When the automated feed from AODB is not operational, flight information
needs to be maintained directly on the FIDS by a simple user interface using
web browser.
b. Special information display notices such as urgent departure notices, PA
and emergency alert must be manually entered directly into the FIDS. These
notices are data elements that get assembled into the display pages.
The Special Display User Environment shall be provided as a simple user
interface using web browser for updating the special displays and entering
notices into the FIDS system for display on relevant channels.
2. The display system must keep some usage statistics that include logs of manually
prepared information and other activities.
1. The display system needs to keep some statistics to enable the airport authority to do
capacity planning.
2. Where the information display system displays advertisements it is important to
keep full statistics to enable the airports authority to invoice for the “air time”.
1. The FIDS is a critical system for the effective operation of the airport. To manage
the availability of display systems an effective system monitoring facility is required.
Such system must report to a management facility failures of any unit including
standby elements so that corrective actions can be taken in timely manner.
2. System monitoring shall be done to ensure that all critical processes running on each
FIDS servers are active and stable. The System Monitor shall attempt to recover the
state of any critical process that has failed. All actions of the system monitoring
shall be logged.
3. The display devices shall also have a self-diagnostic program. When an error
condition is detected, the display device shall restart itself in an attempt to resolve
the problem.
4. If the restarting and resuming the service was not successful in case including but
not limited to the following, the display device shall raise an alert to draw attention
from the operator requesting immediate intervention, and such alert shall be logged
in the system log file.
The FIDS shall provide the configuration capability which shall be intuitive and easy to operate.
Such configuration capability shall include but not limited to the following:-
A. Administrator Environment:
The FIDS administrator interface shall be used to update the operational characteristics
of the FIDS environment. This includes the following:
The information display system has a large number of system parameters that define the
display pages and assignments of devices. These parameters need to be maintained by the
FIDS administration environment.
Users shall be able to manage and maintain the information stored in the Display
Database with simple operation client using widely accepted web-browser.
C. Page Generator:
The Page Generator will be used to generate each the display pages. The process involves
the selection and filtering of flight information from the FIDS database using SQL
statements. Resulting information will then be merged with predefined page templates to
provide HTML pages that can be presented on the web browser of display devices.
D. Channel Mixer:
Various pages shall be sequenced and sent to one or more display devices. The concept
of channels is used to allow for the logical grouping of pages and assignment to display
devices. The Channel Mixer will be responsible for determining what channel a display
device belongs to and what page sequence must be sent to the display device.
E. Advertisement Mixer:
A. The Contractor shall develop a System Acceptance Test plan that should be reviewed by
the Employer at least 30 days prior to the test date.
B. The plan shall address all requirements identified in the Specifications and test all the
Contractor supplied cabling, hardware, and software components. The plan shall follow
accepted industry testing practices and have a method of independent verification
described.
C. The Test shall be carried out collaboratively in conjunction with AODB, as well as by
FIDS independently.
D. The Contractor shall provide all materials and test equipment as required. Test equipment
must have a certification that it has been recently calibrated using recognized industry
standards.
E. Any specified item that does not satisfy the requirements of the Specifications shall be
replaced, upgraded, or added by the Contractor as necessary to correct the noted
deficiencies. After correction of a noted deficiency, re-testing shall be performed to
verify the effectiveness of the corrective action.
7.2 TRAINING
A. The Contractor shall conduct on-site training prior to system acceptance testing for a
group of system administrators for power user’s operation and maintenance, and a group
of end users for user operation. The number of trainees per group will not exceed ten.
B. Initial setup with basic configuration, including AODB shall be completed by the
contractor, as well as typical airline information (logo, sample flight master table for
scheduled flights, etc.) prior to the training.
C. All initial training shall be completed prior to final acceptance of the system.
D. The Contractor shall have an adequate staff of trained personnel on-site during the first
week of “live” operations.
E. Additional training shall be offered at additional cost per person per hour basis.