technical appendix a - iaa.gov.il...iaa tender for a-vdgs version 1.0 appendix a – technical...

Version 1.0 IAA Tender For A-VDGS

Chapter 7 – SOW & Bidder’s Details Appendix A – Technical Requirements

of 78 File Name: IAA_A-VDGS-RFP-Appendix-A__Chapter 7 - SOW and Bidder Details

Saved: August 28, 2016

Technical Appendix A -

The A-VDGS

System Requirement Definition

Chapter 7

Scope of Work and Bidder’s Details

Amendment Record

Issue Date Reasons For

Change

Section

Amended Author Remarks

Version 1.0 16.8.2016 IAA

References and Related Documents Document Description

IAA_A-VDGS - Appendix A - Technical

Requirements - Glossary

Abbreviations and Terms





Table of Contents

7. The Project's Scope of Work (SOW) .............................................................................. 3

7.1 Background and Highlights .......................................................................................... 3 7.1.1 Chapter Objectives .......................................................................................................................... 3 7.1.2 Overview of the Project's Objectives ............................................................................................... 3 7.1.3 Overview of the Project's Implementation ..................................................................................... 3 7.1.4 The A-VDGS Project Interrelation with Other Ongoing Projects ..................................................... 4 7.1.4.1 Setting-Up Concourse E: Current Status & Major Relevant Milestones .......................................... 4 7.1.4.2 Setting-Up Concourse Passengers Loading Bridges of Concourse E: Current Status & Major Relevant Milestones ...................................................................................................................................... 5 7.1.5 Major Future Expansion Options ..................................................................................................... 5 7.1.5.1 Option1 – Expanding the system to Concourse A (O) ..................................................................... 5 7.1.5.2 Option 2 – Expanding the system to Remote (Hard) Stands (O) ..................................................... 5

7.2 The Bidder, Project Team & Organization – Reference Model .................................. 6 7.2.1 Involved Parties (Including Subcontractors) .................................................................................... 6 7.2.1.1 The Bidder's and Subcontractors Details (Q) ................................................................................... 6 7.2.2. Project's Organization.................................................................................................................... 13 7.2.3. Bidder's Project Team .................................................................................................................... 15

7.3. Project's Implementation Process ............................................................................... 19 7.3.1. Introduction ................................................................................................................................... 19 7.3.2. Setting Up the Basic System / Project Plan – Overview ................................................................ 19 7.3.2.1. Setting Up the WP#CS Central System / Project Plan – Overview ................................................. 19 7.3.2.2. Setting Up the WP#BCD System / Project Plan – Overview .......................................................... 23 7.3.2.3. Setting Up the WP#E System / Project Plan – Overview ............................................................... 25 7.3.3. Setting up Future Options ............................................................................................................. 26 7.3.4. Formal Reviews .............................................................................................................................. 27 7.3.5. Major Sub- Stages – Activities and Deliverables Overview ........................................................... 28 7.3.6. Project Plan .................................................................................................................................... 46 7.3.7. Tests ............................................................................................................................................... 49 7.3.8. Training ........................................................................................................................................ 59 7.3.9. Documentation ............................................................................................................................. 62 7.3.10. Involvement of the Bidder in the CFE activities ............................................................................. 64 7.3.11. Installation Requirements ............................................................................................................. 65

7.4. Project Management / Governance – Reference Procedures .................................... 68 7.4.1. Introduction ................................................................................................................................... 68 7.4.2. Managerial Procedure Objectives ................................................................................................. 68 7.4.3. Forums & Meetings ....................................................................................................................... 69 7.4.4. Reviews .......................................................................................................................................... 73 7.4.5. Reports .......................................................................................................................................... 74 7.4.6. Deliverable Management .............................................................................................................. 75 7.4.7. Quality Assurance .......................................................................................................................... 76 7.4.8. Risk Management .......................................................................................................................... 77





7. The Project's Scope of Work (SOW)

7.1 Background and Highlights

7.1.1 Chapter Objectives

1. This chapter describes the Project's Scope of Work (SOW) and provides

requirements for the implementation project, including tasks, outputs, principles

and project management methodology that the Supplier shall undertake during the

Contract Period.

2. The requirements in this chapter aim to minimize potential discrepancies of

expectations between the IAA and the Bidder. These requirements should enable

the Bidder to assess the scope and the depth of the response expected from it;

however, IAA shall endeavor that the actual execution of the Project will be made

as close as possible to the Bidder's best practices, standards, working procedures,

etc.

3. Section 2 above is subjected to IAA’s approval as stipulated in the Contract

regarding the 'Approved Project Execution Plan' and to the Revised Requirements

Definition (RRD) stage as stipulated in Section 7.3.5.3.17.3.5.3 Error! Reference

source not found.Error! Reference source not found.below.

7.1.2 Overview of the Project's Objectives

1. The IAA requests for Proposals for a complete integrative solution for A-VDGS

(Advanced Visual Docking Guidance System) solution as a Turnkey Firm Fixed

Price Project with as many COTS components as possible.

2. The Project’s Business Objectives and Goals and Project’s Schedule are concisely

described in Chapter 1 of the Technical Appendix A (The Technical Requirements),

in Section 1.1

3. The A-VDGS System’s Implementation Concept appear in Chapter 2, Section 2.4

of the Technical Appendix of the RFP.

7.1.3 Overview of the Project's Implementation

1. Please refer to Chapter 1, Section 1.5 and Chapter 2, Section 2.4 of the Technical

Appendix of the RFP.





7.1.4 The A-VDGS Project Interrelation with Other Ongoing Projects

1. In parallel with the A-VDGS project, IAA implements a few other significant

projects:

a. Setting Up Concourse E.

b. Setting Up the Passengers Loading Bridges (PLB) of Concourse E.

2. The Bidder shall fully cooperate throughout the term of the either the Supplier's

Selection Process (of the PLB’s) and/or the Contract with either the Bidders and/or

the Supplier of any existing or future system.

7.1.4.1 Setting-Up Concourse E: Current Status & Major Relevant Milestones

1. Timetable of Setting-Up Concourse E Project will be shared with the Awarded

Bidder at a later stage.

# Status Due

Date

Comments

1. Infrastructure

Readiness

Power Supply, Communication

Network, Civil Engineering

infrastructure are ready be tested by

the Selected Supplier.

2. Electronic Equipment

Installation Readiness

Dust free, Vibrations free, air-

conditioning, fire protection

approval, steady power supply, …

3. Calibration readiness All the Construction works have

been concluded, all temporary

obstacles, fences, etc. has already

been removed, all the Aprons are

paved and painted, and As Made

Surveyed Maps have been

submitted to the Selected Supplier.

4. Test Runs

5. Operational Activation 8/2017

2. The Bidder shall consider the above timetable in its Work Plan.





7.1.4.2 Setting-Up Concourse Passengers Loading Bridges of Concourse

E: Current Status & Major Relevant Milestones

1. IAA has not yet selected a supplier for the Passengers Loading Bridge. Information

shall be provided when available.

7.1.5 Major Future Expansion Options

1. The entire list of the Contract’s Options appears at Chapter 9 of the Technical


2. The Bidder shall be aware that any item in the BOQ can be purchased during the

lifecycle of the system. This includes the DSS unit, training, WS, Spare parts, etc.

3. Following are major Options which are based on the price of a single DSS unit.

7.1.5.1 Option1 – Expanding the system to Concourse A (O)

1. For this option, The Bidder shall propose a complete and integral future expansion

of the A-VDGS System with Concourse A.

2. The Bidder should propose the Project as extension of the TLV AP solution.

3. The Bidder should assume that for the Concourse A the quantities as quoted in

Chapter 9.

4. Commercial issues are detailed in Section 9.8 in Chapter 9 of the Technical

Appendix. It is highly recommended to read Section 9.8 in order to realize the terms

and conditions of this Option.

5. The Concourse A Option shall be an option for IAA which may be implemented at

any time during the life cycle of the system.

7.1.5.2 Option 2 – Expanding the system to Remote (Hard) Stands (O)

1. For this option, The Bidder shall propose a complete and integral future expansion

of the A-VDGS System with Remote (Hard) Stands.

2. The Bidder should propose the Project as extension of the TLV AP solution.

3. The Bidder should assume that for the Remote (Hard)) Stands the quantities as

quoted in Chapter 9.

4. As mentioned in Section 9.9 of the Technical Requirements, the implementation of

remote (hard) stands shall be based on the price for a single DSS.

5. The Remote (hard) Stands Option shall be an option for IAA, which may be

implemented at any time and any quantity during the life cycle of the system.





7.2 The Bidder, Project Team & Organization – Reference

Model

7.2.1 Involved Parties (Including Subcontractors)

7.2.1.1 The Bidder's and Subcontractors Details (Q)

1. The Bidder shall fill in the required information in the following table within the

following sub-sections.

# Party Company Contact

Person

Phone, Fax &

mail

1 Supplier / Integrator

Subcontractor 1

…

Subcontractor n

Local Support

Commercial representative

2. Local Subcontractor for the DSS’s Installation

a. The Bidder may have in-house all the capabilities and supplies required

by this Bid including support services; However the Bidder may, at its

sole discretion, to complement its capabilities, qualifications, products

and such using highly skilled Local Subcontractor with proven

successful experience in supplying services and goods as required in this

bid for de-installation of the existing DSS’s and installation of the new

DSS’s.

b. The Israeli Subcontractor for installation of DSS’s (hereinafter: The

Local Installation Subcontractor and / or LIS) shall comply with the

following requirements:

c. The LIS has participated in processes of supply and installation,

commencing from the year 2012, of at least 50 electronic devices (such

as: display signs, cameras, antennas, …), located at outdoors





environment, requires Height Work Permits and approved by Civil

Engineering Constructor(s) and an Electrical Engineer.

d. The LIS has supplied and installed such electronic devices, to at least 3

customers.

e. The LIS has employed at least 5 employees during the past 3 years with

an experience in the aforementioned installation processes.

f. The LIS is certified for a Quality Control system in accordance with the

ISO 9001:2000, or equivalent standards.

g. The following shall be considered as an advantage: (Q)

i. The LIS has acquired experience in working in an operational

airport at its airside.

ii. The LIS shall appoint a suitably qualified and experienced Project

Coordinator for the duration of the Installation Phase of this

project, hereinafter referred to as the ‘Local’ Project Coordinator.

iii. The ‘Local’ Project Coordinator is expected to be in Israel for the

whole duration of the Installation Phase of the Project.

iv. The ‘Local’ Project Coordinator may be either Israeli or foreign,

and must be able to converse fluently in the English language. It

is an advantage, but not a requirement, for the ‘Local’ Project

Coordinator to speak Hebrew.

3. For each of the involved parties (The Bidder and Subcontractors / local

support), the Bidder shall provide information according to the following

form. The Bidder may add as many copies as needed for the following form.

The Bidder shall provide information about all the involved parties and for

each party in a separated table. If the Bidder has provided that information in

Appendix C (the Bidder Statement) of the Invitation, a reference to the

appropriate form is needed.





Details Required Information #

Registered office address 1.

Company’s registration number, registration date,

country of registration

2.

Number of years under the same Corporate name 3.

Web Address 4.

Name of Owners (whether a company or an

individual)

5.

Name of CEO and tenure in this position 6.

Names of directors 7.

Free text information

such as: public or

private company,

branches etc.

Description of Company 8.

Number of years of experience as a Prime Contractor

in A-VDGS related projects:

9.

In Own Country

Internationally

Number of years of experience as a subcontractor in

A-VDGS related projects:

10.

In Own Country

Internationally

2015 2014 2013 2012 2011 Number of operational A-VDGS Clients:

As a prime contractor?

11.

In Own Country

Internationally

2015 2014 2013 2012 2011 Number of employees 12.

For each of the operational Systems as mentioned above in entry 11

as of year 2013, As a prime contractor, The Bidder is requested to

attach a copy of the Site Acceptance Tests.

13.





7.2.1.2. Division of Roles between the Involved Parties (Q)

1. The Bidder shall describe the parties involved in the implementation of the A-

VDGS project, and the division of Roles/Tasks.

7.2.1.3. Previous Cooperation between the Involved Parties (Q)

1. The bidder shall describe previous cooperation between the involved parties: (Q)

Involved parties Type and nature of joint activity

Customer Year Principal

contractor

1st sub-

contractor …

Local

Supp

ort

Proposal

to Tender Pilot

Operational

system

Current

Maint.

Other,

specify:

7.2.1.4. Subcontractors Management

1. The Bidder shall describe any Subcontractors involved during the project's

implementation and future options, as well as for the project's Warranty, Service

and Maintenance stages.

2. The Bidder shall describe the subcontractors' experience concerning with the

aforementioned activities. (Q)

3. The Bidder shall provide information as to the management methodology

concerning subcontractors/suppliers. The description shall include quality control,

risk analysis and a detailed description of the replacement strategy for the case

where the subcontractor failed in the execution of the work according to the

required standards. (Q)

4. The Bidder shall provide a Letter of authorization from the sub-contractor to the

Bidder allowing the Bidder to propose the sub-contractor’s services for this Tender.

7.2.1.5. Experience, Goodwill and Customers

1. The information provided by the Bidder in response to this section shall have

significant impact on the quality evaluation of the Bidder's Proposal. An advantage

in quality evaluation will be given to:

a. Operational provability (The more the offered A-VDGS is in

operational use, in as many Airports, longer duration in use, etc.).





b. Quantities supplied of the same or equivalent Systems such as offered

in the Bidder's Proposal.

c. Compliance with the related functional, performance and maintenance

requirements listed within this RFP.

2. Relevant Projects Completed (Q)

a. The Bidder shall provide information about both A-VDGS projects

completed by the Bidder (as a prime contractor), where the system had

been fully accepted by the client over the past five years (2011, 2012,

2013, 2014 and 2015) in the following table format.

b. In particular, The Bidder shall describe in detail one site, with similar

characteristics and complexities to those required for the A-VDGS

System in Israel, thus demonstrating the Bidder’s ability to deliver a

complete solution as required under this Tender's Document.

c. The Bidder shall fully describe in details a case study of a complete

Project in operation, most similar to the A-VDGS, including but not

limited to: Centralized System, Obstacle Detection and Alert Module,

the architecture, BOM, challenges, solutions, deployment time,

example documents of FAT and SAT (also of the COTS components),

lessons learnt, etc.

d. The Bidder should emphasize and detail any difference in

capabilities/technologies/bugs fixes between the future A-VDGS

Version and the described project. Also, if there are any major

changes, the Bidder shall explain how these are intended to be tested.

# Subject Remarks

1 Name of customer Add airport info:

Num of movements, number of passenger, layout,

number of gates, …

2 Current status Pilot, During Qualification Process, Operational,

Not In Use, … and Further business engagement

since originally signing the contract

3 Contact person details Information concerning the references shall

include at least the following information: name

of contact person, function, term of acquaintance,

nature of acquaintance, contact details (phone,

fax, email) and a written document that shall be





# Subject Remarks

signed by the contact person expressing that

he/she is aware that IAA may contact him/her for

this purpose.

4 Type of contract Main Contractor, Subcontractor (if so, to whom)

5 A-VDGS solution

project major

milestones

Project's Starting Date, Project's Acceptance's

Date, System Handover Date

6 Description of the A-

VDGS

Please refer Section c’ above.

10 System limitations and

constraints

11 Interfaces Such as A-SMGCS, Flight Plan info, Airport Info,

Electronic Flight Strip, others. Name the specific

system.

Certification /

Acceptance

Please provide information such as: System

certification date, who certified the system, how

long it took, Division of roles among the supplier,

the client and certifying body, content of examined

elements, whether it was necessary to certify the

Operational Staff as well, whether it was

necessary to certify the Technical Staff as well,

etc. The Bidder may attach the relevant

certificates to its Proposal.

Reference Letters The information concerning the references shall

include the following at least: name of the

company, name of reference, function, term of

acquaintance, nature of acquaintance, contact

details (phone, fax, email) and a written document

that shall be signed by the reference expressing

that he/she is aware that IAA may contact him/her

for this purpose.

*Additional pages may be added for more than one project.





3. All Projects in Progress

a. The Bidder shall provide information about all of its related projects that are

presently in progress, including those where the Bidder has received a letter

of intent, but a formal contract has not yet been awarded and/or entered into

force, in the format specified at Section 7.2.1.5

4. Experience: Geographical Spread (Q)

a. The Bidder shall provide information about all countries in which works

similar to the A-VDGS projects have been undertaken, in the last five years

(2011-2015):

# Country Details*

1

2

… … …

*Bidder is required to provide details of the project such as year of installation,

location where the System resides, operational status, further engagements

since the 1st installation, etc.

5. The Bidder shall elaborate about procedures to verify customer’s satisfaction (such

as surveys for examples) during the Project and afterwards during the Maintenance

and Operational Term and Future Expansions. The Bidder shall provide its

methodology, its forms and at least 2 recent forms (for each of the 3 activities that

are mentioned above: the Project, the Maintenance and Operational Term and

Future Expansions) that were filled by the Bidder's clients. (Q)





7.2.2. Project's Organization

7.2.2.1. Project Team Highlights

1. The Bidder shall refer to the following highlights while introducing the proposed key

persons for IAA's project (see clauses: 7.2.3.2, 7.2.3.3, 7.2.3.4, etc.). (Q)

2. The Selected Bidder is required to provide a Project Team (PT) fully capable of

managing, supervising and successfully executing the A-VDGS project – to provide

a comprehensive, integrative and seamless solution as required by this Tender. The

Bidder is required to present proven methodologies for the planning execution,

monitoring and control of similar previous projects. The methodologies shall include

all phases of the project lifecycle, such as starting with sites' surveys, update of

requirement definitions, design, execution, through acceptance tests and assimilation.

The Bidder is required to present its internal monitoring methodologies to ensure

accomplishment of the plan's objectives (such as internal follow up meetings, internal

review for the meaningful milestones, other channels of communication with the

participating parties, monitoring client's awareness and satisfaction, etc.) throughout

the project's lifecycle. The Bidder shall present its methodologies and best practices

for managing projects with remote international locations. (Q)

3. The PT shall include experts from different disciplines as required for such a project

with proven ability to handle the challenges in the following domains: (Q)

a. Management of a multi-disciplinary project endeavor.

b. Assembling a pragmatic and applicable technological solution.

c. Coordinated teamwork with subcontractors from Israel (if there are such

subcontractors) and abroad.

d. Interfacing with IAA external suppliers, equipment that shall be executed

in a harsh environment - at an operational airport.

e. Providing warranty, service and maintenance support for the A-VDGS

solution spanning over a long period of time.

4. The PT is expected to have thorough professional familiarity and experience with the

main supply components in the project, such as: A-VDGS, Infrastructure design and

execution and service and maintenance for a critical operational system requiring

maximal availability. (Q)





5. The PT members shall be first-class, motivated and responsible professionals who

are willing to engage in strenuous work, in possibly different time zones, maintain

maximal availability and be capable of delivering the required tasks under tight

schedules. They shall have full access to all relevant expertise and knowledge base

of the Bidder's group. They shall also be capable of interacting smoothly and

coordinating with IAA entities and suppliers. (Q)

6. IAA expects the Bidder to provide a formal authorization confirming that the PT

members are trained, skilled, qualified for their role in the Project and kept constantly

up to date with the best practices in their field of expertise, major suppliers and

products, solutions applied in other organizations (A-VDGS installations in other

airports), as well as having high level acquaintances in their field of expertise,

participate in relevant professional forums, etc. IAA expects to gain real added value

from highly competent professionals who stand in the forefront of world technology.

(Q)

7. The Bidder is required to have adequate operational backup capabilities to allow for

an efficient response to possible overloads (e.g. quantities/locations) that are

expected in such a project. (Q)





7.2.3. Bidder's Project Team

7.2.3.1. The Bidder's Proposed Project Team and Project Organization

Structure

1. All the details requested below shall be completed for all the team members involved

in project, including subcontractors (Q)

#

Work

er’s

Nam

e

Role in

the P

roject

Pro

fession

% Position Allotted to

IAA Project Expertise –

No. of

Projects

Seniority

in the

Field

Experience

in the Field Setting

Up the

System

Maintenance

Stage

2. The Bidder shall append an organizational chart, which must include all personnel

and lines of responsibilities of the IAA's Project (Q)

3. During the Supplier's selection process, IAA shall approve all personnel proposed by

the Bidder and have the right to interview key personnel and discuss changes if the

Bidder's choice is deemed unsuitable. (Q)

4. The following requirements for destined Key Persons in the projects depicts IAA’s

understanding of a suitable staffing for such a project; however, if the Bidder's

common / best practice is different, the Bidder should not restrict itself to the

following key persons and may offer its best staffing. (Q)

7.2.3.2. Details on the Project Executive

1. The Bidder shall appoint to the A-VDGS Project an Executive who will be the project

sponsor. The Executive will ensure the project's success and will be authorized to

make decisions and commitments on behalf of the Bidder Executive Management.

The Executive will be also an escalation contact for any major issues. The Executive

will be in direct contact with the Project Manager and with the Bidder’s top

management. (Q)

2. The Bidder’s A-VDGS Project Executive shall be able to communicate fluently in

the English language (written and oral) (P).





3. The Bidder shall provide a relevant CV of the Project Executive– this shall include

at a minimum: (Q)

a. Personal details (name, contact details).

b. Formal education, training and qualifications.

c. Position in the Company.

d. Relevant experience as a project manager / project executive of similar

projects.

e. Two references from the past 5 years while acting in similar capacity

(preferred if applicable)

f. Availability.

7.2.3.3. Details on the A-VDGS Project Manager

1. The Bidder shall appoint a suitably qualified and experienced Project Manager for

the duration of this project hereinafter referred to as the Bidder’s A-VDGS Project

Manager. (Q)

2. The Bidder’s A-VDGS Project Manager shall meet the requirements that are depicted

in Section 5.2 of the Contract – “The Supplier's Representative”

3. The Bidder’s A-VDGS Project Manager shall be assigned fully and solely to the

IAA’s A-VDGS Project (Q)

4. However, if the Bidder’s response to Section 2’ above is partially compliant, IAA’s

Project shall be the A-VDGS Project Manager principle occupation and not less than

80% of a full time job.

5. The Bidder’s A-VDGS Project Manager shall be able to communicate fluently in the

English language (written and oral).

6. The Bidder’s A-VDGS Project Manager is expected to be in Israel as needed during

the duration of the project, at least once a month or as per the project stages criticality

and steering committee meetings. (Q)

7. The Bidder shall provide a relevant CV of the destined Bidder’s A-VDGS Project

Manager – this shall include at a minimum: (Q)



c. Relevant experience in Project Managing of A-VDGS related projects.

d. Two references from the past 5 years.





e. Availability.

f. Compliance with clause 7.2.2.1 – Project Team Highlights.

8. The IAA shall reserve the right to interview the Bidder’s A-VDGS Project Manager.

This interview will take place in person at IAA premises.

9. If the Bidder’s A-VDGS Project Manager is replaced by the Bidder during the setting

up period of the Complete System, a notice period of 30 days must be given to the

IAA, which in turn reserves the right to interview and approve the replacement. The

replacement must spend at least 15 days in Israel with the incumbent Bidder’s A-

VDGS Project Manager to accomplish a full handover.

10. IAA reserves the right to request the replacement the Bidder’s A-VDGS Project

Manager at its discretion with a notice period of 30 days. The IAA shall reserve the

right to interview and approve the new Bidder’s A-VDGS Project Manager. The

replacement must spend 15 days in Israel with the incumbent Bidder’s A-VDGS

Project Manager to accomplish a full handover.

7.2.3.4. Details of the Senior Technical Manager

1. The Bidder shall appoint a suitably qualified and experienced Senior Technical

Manager for at least the duration of the Set-Up of Complete System project,

hereinafter referred to as the project A-VDGS Senior Technical Manager. (Q)

2. The A-VDGS Senior Technical Manager is expected to be in Israel as much as

needed during the duration of the aforementioned project, in particular during the

RRD and Design, Installation and Commissioning, Integration and Tests phases of

the project. (Q)

3. The A-VDGS Senior Technical Manager shall be able to converse fluently in the

English language.

4. The Senior Technical Manager shall at all times be under the direction of the Bidder's

Technical Executive Director (or CTO).

5. The Bidder shall provide a relevant CV of the A-VDGS Senior Technical Manager

– this shall include at a minimum: (Q)



c. Relevant experience in Project Managing of A-VDGS projects which

include a complete integrative solutions.






6. The Bidder shall provide a relevant CV of the Chief Technology Officer – this shall

include at a minimum: (Q)



c. Relevant experience in project managing of similar A-VDGS projects or

IT Implementation projects.

7. The IAA shall reserve the right to interview the A-VDGS Senior Technical Manager.

8. If the IAA’s A-VDGS Senior Technical Manager is replaced during the project term,

a notice period of 30 days must be given to the IAA, which reserves the right to

interview the replacement.

7.2.3.5. Details of the Installation Team Manager

1. The Bidder shall appoint a suitably qualified and experienced field engineer to

manage IAA’s installations during the Set Up of the Complete System Project. (Q)

2. The Installations and Technicians Team Manager shall be able to converse fluently

in the English Language.

3. The Installations and Technicians Team Manager is expected to be in Israel as needed

during the relevant Stages.

4. The Bidder shall provide a relevant CV of the Installations and Technicians Team

Manager – this shall include at a minimum: (Q)



c. Relevant experience in managing A-VDGS solution Installations.


5. The IAA shall reserve the right to interview the Installations and Technicians Team

Manager.





7.3. Project's Implementation Process

7.3.1. Introduction

1. Section 7.3 intends to provide information about the project's major stages, timetable,

major activities and deliverables.

2. The project life cycle in this chapter is presented as the minimal scope of

requirements. The Bidder is entitled and encouraged to propose enhancements and/or

slight amendments based on the Bidder's best practice, as well as to present examples

of deliverables similar to those requested during the various stages of the Project to

depict its abilities and execution practices (Q)

3. The above mentioned shall not derogate from the full and complete responsibility of

the Bidder for the performance of the Project in compliance with the System

Requirements as stipulated in chapters 1-9 and compliance with the provisions of the

Contract and completed within the defined timetable.

7.3.2. Setting Up the Basic System / Project Plan – Overview

7.3.2.1. Setting Up the WP#CS Central System / Project Plan – Overview

1. Refer to Clause 1.5.2 Implementation Major Stages, at Chapter 1 of the Technical


2. The following table provides more details to the major stages and milestones as well

as expected time table that IAA requires for the Complete WP#CS System

Implementation. [The high-level project plan is as specified in this section, and it

includes a separate SAT for WP#BCD (A-VDGS in Concourses B, C & D) and

WP#E (A-VDGS in Concourse E). The Bidder is requested to provide a Project Plan

as requested in this Technical Appendix of the RFP. However, the Bidder may add

an elective option of a different outline for the Project Implementation. A

comparative review of both concepts will be warmly welcomed. For avoidance of a

doubt it is clarified, that the outline as stipulated by IAA is the one that will oblige

the Bidder and that the cost in the Price Proposal Form should refer to IAA's outline.]

3. The Bidder shall insert its planned timeframe (number of months from ARO)

wherever this was not specified by IAA. (Q)





4. The Bidder is requested to distinguish between a formal Payment Milestone – in

which the Bidder should comply with IAA’s requirements (such as the HLD for both

stages) – and Informal Stages – which stands for expectations’ coordination solely.

5. The Completion of the Central system is a pre-requisite to any DSS in concourses B

C D and E. The Final Central System SAT shall be combined with the SAT of either

WP#BCD or WP#E whichever commenced last. Thus the total A-VDGS system SAT

shall be commenced when All DSSs are installed in B C D and E.

6. The commencement of the Soak Period of the Central system shall be combined with

the commencement of the SOAK period of either WP#BCD or WP#E whichever

commences last. Thus the total A-VDGS system SOAK shall be commenced when

All DSSs are installed in B C D and E.

7. Setting Up the WP#CS table:

Stage /

Milestone #

Stage / Sub-Stage

[Section number]

Due Date for

Finalizing The

Stage / Sub-

Stage (ARO

+# Months)

Comments

0. Signing the Contract ARO

Receipt of Order.

A payment milestone

1. Kick-Off

TBD By the

Bidder

A Draft Site Survey Plan,

Draft PEP’s Updates and

Draft RRD are expected 5

working days before the

Kick-off Meeting.

1.1. Sites Survey

1.2. Project Execution Plan (PEP)

Updates

If needed.

1.3. Revised Requirement Definition

(RRD) 7.3.5.3.1.

All other aspects but the

Technical Portion that has

already been done during the

Contract Signature’s Term.

2. System Design Review (Central

System, and Concourses B C D and

E)

TBD By the

Bidder

The Bidder shall submit all

the documents that will be

reviewed (see 2.1 – 2.6

below) at least 5 business

days before the Review.

2.1. High Level Design for the Central

System and both WP#BCD System

and WP#E 7.3.5.5.27.3.5.5.2





Stage /

Milestone #

Stage / Sub-Stage

[Section number]

Due Date for

Finalizing The

Stage / Sub-

Stage (ARO

+# Months)

Comments

2.2. Architecture 7.3.5.5.17.3.5.5.1

2.3. WP#CS, 7.3.5.5.37.3.5.5.3

2.4. WP#CS System – Site Engineering

Report. 7.3.5.4.17.3.5.4.1

2.5. WP#BCD System – FAT & SAT

Plan and Procedures

2.6. Presenting the System Maintenance

Program SMP

3. Setting-up WP#CS Central System

3.1. Manufacturing / Purchasing /

Development / Integration 7.3.5.6

3.2. FAT for Central System

Components 7.3.5.7

TBD By the

Bidder A payment milestone,

together with the IRR (See

entry 3.3 in this table).

3.3. Formal Review: IRR (Installation

Readiness Review): The Supplier

Accepts IAA’s Supplies. 7.3.5.7

TBD By the


together with the FAT (See


3.4. Delivering the System Components

to Israel 0

3.5. Setting Up the Central

System 7.3.5.9

3.6. Central System Preliminary

Acceptance Test (simulated data) ARO + 4m See Critical Mile Stone for

WP#BCD. The Central

System must be ready

before testing any DSS at B

C or D.

4. System and Service Acceptance

Tests

4.1. Final SAT Commencement of

AVDGS Central System 7.3.5.11

The CS Final SAT shall be

combined either the Final

SAT of WP#BCD, or WP#E

whichever will commence

later.

4.2. WP#CS System's Final SAT

Completion

TBD By the

Bidder

Overall System Acceptance

Formal Review: SAT.

A payment milestone





Stage /

Milestone #

Stage / Sub-Stage

[Section number]

Due Date for

Finalizing The

Stage / Sub-

Stage (ARO

+# Months)

Comments

4.3. Commencement of the Soak Period

and Activation of the System as

Fully Operational

Not Later

than ARO+10

Months

4.4. Soak Test Completion [7.3.5.12]

This is also the completion of Soak

Test for BCD and E as well. * Soak test as stipulated at the

aforementioned Sections is 3 periods of one

month (total of 3 months) for each stage of

the project separately. However, the final

duration for each soak test will be

discussed with the selected bidder based on

its best practice, subject to the IAA's

approval.

Ends with issuing a Final

Certificate of Acceptance

(COA) for WP#CS and

WP#BCD and WP#E A-

VDGS System by IAA

A payment milestone

5. Warranty, Service and maintenance

Period for WP#CS System 7.3.5.13]

5.1. Warranty, Period for WP#CS

System starts [Error! Reference

source not found.7.3.5.12]

Starts at the Commencement

of the First DSS Gate

Acceptance Tests either in B

C D or E

5.2. Service and Maintenance Period for

WP#CS WP#BCD and WP#E

System starts

Warranty period ends 24

months after the Supplier has

received from IAA the

Certificate Of Acceptance of

WP#CS and WP#BCD. The

Warranty for WP#E shall be

no less than 1 year. Please

refer to the Contract.





7.3.2.2. Setting Up the WP#BCD System / Project Plan – Overview

1. Refer to Clause 1.5.2 Implementation Major Stages, at Chapter 1 of the

Technical Appendix of the RFP.

2. The following table provides more details to the major stages and milestones

as well as expected time table that IAA requires for the Complete WP#BCD

System Implementation. [The high-level project plan is as specified in this

section, and it includes a separate SAT for WP#BCD (A-VDGS in

Concourses B, C & D) and WP#E (A-VDGS in Concourse E). The Bidder is

requested to provide a Project Plan as requested in this Technical Appendix

of the RFP. However, the Bidder may add an elective option of a different

outline for the Project Implementation. A comparative review of both

concepts will be warmly welcomed. For avoidance of a doubt it is clarified,

that the outline as stipulated by IAA is the one that will oblige the Bidder and

that the cost in the Price Proposal Form should refer to IAA's outline.]

3. The Bidder shall insert its planned timeframe (number of months from ARO)

wherever this was not specified by IAA. (Q)

4. The Bidder is requested to distinguish between a formal Payment Milestone

– in which the Bidder should comply with IAA’s requirements (such as the

HLD for both stages) – and Informal Stages – which stands for expectations’

coordination solely.

5. The SAT for WP#BCD shall commence only after completing the

Preliminary SAT of the CS. See WP#CS Project plan.

6. Setting Up the WP#BCD Table:

Stage /

Milestone

#

Stage / Sub-Stage

[Section number]

Due Date for

Finalizing The

Stage / Sub-

Stage (ARO

+# Months)

Comments

1. Setting-up WP#BCD System

1.1. Manufacturing / Purchasing /

Development / Integration 7.3.5.6

1.2. FAT 7.3.5.7 TBD By the

Bidder

A payment milestone, together

with the IRR (See entry 1.3 in this

table).





Stage /

Milestone

#

Stage / Sub-Stage

[Section number]

Due Date for

Finalizing The

Stage / Sub-

Stage (ARO

+# Months)

Comments

1.3. Formal Review: IRR (Installation

Readiness Review): the Supplier Accepts

IAA’s Supplies. 7.3.5.7

TBD By the

Bidder A payment milestone, together

with the FAT (See entry 1.2 in this

table).

1.4. Delivering the System Components to

Israel 07.3.5.8

1.5. Equipment for at least 2 Concourses is

stored at BGN Airport ready to be installed ARO + 5m

A Critical Milestone

1.6. Central system is ready for the first test of

DSS

See WP#CS [7.3.2.1]

1.7. Gates' Installation, Commissioning and

Acceptance 0

May last for a few weeks. One by

one replacement.,

Warranty, Starts for each Gate

separately.

2. System and Service Acceptance Tests

2.1. WP#BCD System's Final SAT

Commencement 7.3.5.11

2.2. WP#BCD System's Final SAT Completion TBD By the

Bidder

B C D gates. System Acceptance

Formal Review: SAT.

A payment milestone

2.3. Commencement of the Soak Period for

BCD and Activation of the System as

Fully Operational System (shutting down

the old system)

Not Later

than

ARO+10

Months

2.4. Soak Test Completion [7.3.5.12] * Soak test as stipulated at the aforementioned

Sections is 3 periods of one month (total of 3

months) for each stage of the project separately.

However, the final duration for each soak test will

be discussed with the selected bidder based on its

best practice, subject to the IAA's approval.


Certificate of Acceptance (COA)

WP#BCD System by IAA

A payment milestone

3. Warranty, Service and maintenance Period

for WP#BCD System

3.1. Warranty, Period for WP#BCD System

starts [7.3.5.13]

Starts at the Commencement of

each Gate Acceptance Tests

3.2. Service and Maintenance Period for

WP#BCD System ends

Warranty period ends 24 month

after the Supplier has received from

IAA the Certificate Of Acceptance

of WP#BCD for all gates.





7.3.2.3. Setting Up the WP#E System / Project Plan – Overview

1. Refer to Clause Error! Reference source not found.7.3.2.3 – WP#E System –

Implementation major milestones.

2. Setting Up the WP#E Table:

Stage /

Milestone

#

Stage / Sub-Stage

[Section number]

Due Date for

Finalizing The

Stage / Sub-

Stage (ARO

+# Months)

Comments

1. Setting-up WP#E System

1.1. Manufacturing / Purchasing / Development /

Integration 7.3.5.6

1.2. FAT 7.3.5.7 TBD By the


together with the IRR (See


1.3. Formal Review: IRR (Installation Readiness

Review): The Supplier Accepts IAA’s

Supplies. 7.3.5.7

TBD By the


together with the FAT

(See entry 1.2 in this

table).

1.4. Delivering the System Components to Israel 0

1.5. Central system is ready for the first test of

DSS

See WP#CS

1.6. Gates' Installation, Commissioning and

Acceptance 0

Installation of all 8 gates

2. System and Service Acceptance Tests

2.1. WP#E System's Final SAT

Commencement 7.3.5.11

2.2. WP#E System's Final SAT Completion TBD By the

Bidder

System Acceptance for

all 8 gates

Formal Review: SAT.

Note that if SAT of

WP#E commences after

SAT WP#BCD, this SAT

is actually the Final A-

VDGS system SAT.

A payment milestone

2.3. Commencement of the Soak Period and

Activation of the Gate E as Fully Operational

Not Later

than ARO + 6

Months

Warranty Starts after

SAT COA.





Stage /

Milestone

#

Stage / Sub-Stage

[Section number]

Due Date for

Finalizing The

Stage / Sub-

Stage (ARO

+# Months)

Comments

2.4. Soak Test Completion [7.3.5.12]

* Soak test as stipulated at the aforementioned Sections

is 3 periods of one month (total of 3 months) for each

stage of the project separately. However, the final

duration for each soak test will be discussed with the

selected bidder based on its best practice, subject to the

IAA's approval.


Certificate of Acceptance

(COA) WP#E System by

IAA. Note that if WP#W

ends after WP#BCD than

it is the Final Soak of A-

VDGS system.

A payment milestone

3. Warranty, Service and maintenance Period for

WP#E System

3.1. Warranty, Period for WP#E System starts

[7.3.5.13]

Starts at each tested gates

3.2. Service and Maintenance Period for WP#E

System starts

Warranty period ends 24

months after the Supplier

has received from IAA the

Certificate Of Acceptance

of WP#BCD and WP#CS;

However, minimal term

for the Warranty shall not

be less than 12 months.

7.3.3. Setting up Future Options

1. For each options listed in the corresponding clauses - in chapter 9, the Bidder shall

describe a tentative Project Plan and timetable for implementation (according the

example above at section 7.3.2 Setting Up the Option 1/2/… System / Project Plan –

Overview

The suggested format is the following table:

# Stage / Sub-Stage

Due Date for

Finalizing The Stage /

Sub-Stage (ARO + M)

Comments / details

1

2

.. … … …





2. Each option and proceeding in this respect shall be implemented in the manner

stipulated in the provisions regarding "Variations" in the Contract. However, the

prices stipulated for each option shall include all managerial tasks and statement of

work necessary to implement the option.

3. For options 1 and 2, each shall be considered as a Project in itself.

4. IAA shall be entitled to activate each option any time during the Contract Period.

5. The Bidder shall stipulate for each option all the relevant details required for the

implementation of each option as stipulated at 7.1.5.1 above.

6. For the avoidance of doubt, it is hereby clarified that for the performance of each

Option by the Bidder, the Bidder shall be entitled only to the sum stipulated by it for

the relevant Option in its Price Proposal.

7. The Bidder’s proposal shall refer to all the above. (Q)

7.3.4. Formal Reviews

1. This Section specifies the formal reviews that shall be executed throughout the

project. The schedule for the reviews shall be set in the project's Gantt chart as a

single milestone or a series of milestones (e.g. the SAT, Sites and Production

Readiness Reviews) as needed.

2. All the Reviews will be held in Israel in Ben Gurion Airport unless IAA approved in

writing another location.

3. The Bidder shall list and describe any additional recommended reviews as per its best

practice.

4. In addition, the Bidder and IAA can initiate technical design reviews (DR) or

managerial reviews (PMR) when and if needed, in order to attend unexpected or

special issues that might arise throughout the project. The following is valid for each

stage.

5. The Review Procedure is described in Section 7.4.4 below

6. List of Formal Reviews:

# Name Estimated

Schedule Responsibility

(1) RRD and PEP Review The Bidder

(2) High Level Design Review (PDR) The Bidder

(3) Installation Readiness Review (IAA’s

Supplies Readiness Review (per each site))

IAA





# Name Estimated

Schedule Responsibility

(4) SAT Readiness Review The Bidder

(5) SAT Review The Bidder

(6) Soak Readiness Review The Bidder

(7) Soak Review The Bidder

7.3.5. Major Sub- Stages – Activities and Deliverables Overview

7.3.5.1. General

1. The following list of major sub-stages shall not be considered to be exhaustive; some

of the sub-stages are not mentioned at all; however, the Bidder shall accept the

following milestones, responsibilities and elaborate in an equivalent manner all the

proposed sub-stages. (Q)

2. The Bidder shall describe the following:

a. The Bidder shall describe the involvement of the Bid Manager and the

Bid team in Setting-Up the WP#CS, WP#BCD and/or WP#E System.

IAA relates high importance to the Bid Manager's involvement at least

until completion and approval of the RRD stage. (Q)

b. The Bidder shall describe the proposed Executive Project Manager, The

Proposed Project Manager, the Proposed Technical Manager and other

key staff proposed (upon Bidder's discretion) in preparing and

approving the Proposal. (Q)

c. The handover / overlapping between the Bid Manager and the A-VDGS

/ A-VDGS Project Manager. (Q)

7.3.5.2. IAA's Approval for Each Stage

1. The Bidder shall accept that each stage is concluded only upon IAA's Approval of

completion. For example, the revised Requirement Definition stage is concluded by

IAA's approval of the RRD Summary document.





2. The Bidder shall accept that IAA's Approval, for each stage as described below, is a

threshold condition for proceeding to next stage and/or for a payment milestone, in

compliance with Section 11 and 20 in the Contract.

7.3.5.3. Kick-Off Meeting

1. On-Site Kick-Off Meeting (hereinafter KOM) would be held in Israel in order to

define and finalize technical and administrative issues of the Contract. The visit shall

last as many days as required to be able to include Approved Project Plan and the

RRD in the Contract.

2. Following are major activities and deliverables for the Kick-Off Stage:

# Activities Deliverables Responsibility

1. High Level Project Plan for

Executive

PEP Presentation

High Level Project Plan

Project Steering Committee

Defining the Review process

The Bidder

2. Project Work Plan Review

(PEPR)

Detailed Project Execution Plan.+

Baseline Freeze

The Bidder

PEPR – Summary document The Bidder

3. IAA's approval to Project

Execution Plan

PEP Approval document + Baseline

Freeze

IAA

4. Revised Requirement

Definition (a) Requirements'

Freezing.

Revised Requirement Definition

document

The Bidder

5. System Requirements

Review

RRD – Summary document The Bidder

6. IAA's approval of the RRD

Summary document

RRD Approval document IAA

7.3.5.3.1. KOM – The Approved Project Plan and RRD

1. The Contract, entitles the Awarded Bidder to submit a formal Project Execution Plan,

subjected to the terms and conditions in the aforementioned Contract’s Section. The

idea behind this plan is to try to find the “golden path” between IAA’s initial

requirements and procedures and the Bidder’s best practices. The Project Execution

Plan is a formal Annex of the Contract – Annex “C3”. Lineup – The RRD Technical

Portion





2. The RRD Document shall be derived from the IAA's Technical Requirements, the

Selected Bidder’s Proposal, the various clarifications that were submitted by the

Selected Bidder during the Bidder’s Selection Process and necessary updates to the

aforementioned documents that may have been created due to the long period that

has elapsed since originally writing these documents until their implementation.

3. Following is a ”Blocks Diagram” that illustrated the aforementioned text:

Figure 1 - Overview of the RRD Stage





4. Following is an example (from another Tender) for a single requirement during the

RRD stage:

5. For avoidance of a doubt, IAA explicitly declares that the RRD stage shall neither

influence nor change either the final cost or the timetable in any way. The meetings

are intended merely to "fine-tune" the requirements within the basic scope of the

project that shall serve the Contract and Project implementation.

7.3.5.4. Kick-Of Meeting (KOM), Site Survey and Site Engineering Report

1. On-Site Kick-off Meeting would be held in Israel in order to define and finalize

technical and administrative issues of the project. The visit may last for a few days,

which shall include the Official and Final Site Survey according to the Supplier's

methodology. The Bidder shall refer to the Contract for further details relating to the

Official and Final Site Survey.

2. A Draft Site Survey Plan is expected 5 working days before the Kick-off Meeting.

3. In general, the KOM is an opportunity for the Awarded Bidder to gather all the

information it needs for the design phase (for example: information about interfacing





system, etc.). The Bidder is most welcome to add activities to the KOM Plan upon

its experience and best practices (Q).

7.3.5.4.1. The Site Survey and the Site Engineering Report

1. The Sight Engineering Report (SER) should incorporate the following activities and

information:

a. Finalizing all System’s Components that should reside in IAA premises.

b. The Supplier should well define each component that requires supplies by IAA

such as: Space, Power Supply, and Communication Network, for all required

activities such as: locating, installation, commissioning, operating, maintenance,

etc.

c. IAA will decide the components exact locations.

d. During the Site Survey, the Supplier shall be acquainted with the existing and

planned conditions.

e. Shortly after the Site Survey, the Supplier is expected to send IAA a draft with

all needed preparation for locating, installing, commissioning, operating and

maintaining each component. That should include information such as:

i. Components’ Requirements.

ii. Existing Conditions.

iii. Required Site Preparations.

iv. Sharing the Preparations’ roles among the Supplier and IAA including

the desired timetable.

v. High level design of the connection / integration between the Supplier’s

supplies and IAA supplies, including demarcation points and acceptance

tests by the supplier to IAA’s supplies.

vi. Site Preparations should incorporate themes such as: removal of existing

equipment, space, power supply, communication network, access

control, air condition, furniture, demarcation points, etc.

vii. IAA will study the report and will comment on it to the Supplier.

viii. The Supplier shall amend its report until IAA’s approval.

f. During the Supplier’s Selection Process IAA will provide the Bidders a list of

Supplies that are available for the System / Project. IAA prefers that the Bidders

will adapt their solution to IAA’s constraints; however, if the Bidder needs

extra’s it should write it in its proposal. Meeting IAA constraints may contribute

to facilitate IAA’s preparation, which might be expressed in savings of time and

money. Hence, the closer the Bidder will be to IAA’s constraints, the higher

potential for quality grade that it will receive.





g. Timetable for providing the SER and its approval is crucial to IAA in order to

meet its desired due dates.

h. The Bidder is requested to elaborate in its response how it is about to meet IAA’s

challenge as depicted above (Q).

7.3.5.5. Design

1. Following are the Design Phase Characteristics / Highlights:

a. Architecture and High Level Design (as described below) shall be done for all

WP#CS, WP#BCD and WP#E.

b. IAA has no objection that the HLD and the DLD shall be joint to one phase.

c. Following are activities and deliverables for: Architecture, High Level Design

and Detailed Design.

7.3.5.5.1. Architecture / High Level Design for Both Stages

1. Architecture / High Level Design table:


1 Defining System Logical

Architecture

Defining System Modules and

Functionality

Defining System's Physical

Configuration

Defining System Sizing

System Architecture Document The Bidder

2 Analyzing the environment in which

The System shall be installed (see

note (a) below)

Site Engineering Report -

Required Infrastructure for the

System's installation, operation

and maintenance

The Bidder

3 Formation of System Interfaces

Specification

System Interfaces

Specification's document.

The Bidder

4 Specification of 3rd parties products

to be integrated in The System

3rd Party Products –

Specification for Purchase.

The Bidder






5 Formation of Administrative

Management Concept

A document, referring to

various issues, such as:

monitoring functionality, alert

levels, special site specific

principles, HMI, etc.

The Bidder

6 Formation of a Conceptual Test Plan

(see clause 7.3.7)

Conceptual Test Plan doc.

(STP)

The Bidder

8 Formation of a Conceptual Quality

Plan (see clause 0)

Conceptual Quality Plan doc.

(QAP)

The Bidder

9 Risk Identification and Analysis Risk Analysis and Mitigation

Plan Document

The Bidder

10 Updating the Project's Work plan Updated Project's Work plan

approved by IAA

The Bidder

11 System Architecture Review (SAR) SAR– Summary document The Bidder

12 IAA's approval to SAR SAR Approval document IAA

2. The Required infrastructure (table entry #2 above) shall refer, inter alia, to power

supply requirements, passive communication network, floating floor, survivability

requirements, air conditioning, floor space, height, access control, recommended

furniture both for operation and storage, lighting, separation of areas, windows, etc.

For more details, see 7.3.5.4 (SER).

7.3.5.5.2. High Level Design (for each Work Package separately)

1. High Level Design Activity Table:


1 Formation of a configuration

for each Working Positions for

the phase

Working Positions' Configuration

document

The Bidder

2 System Interfaces High Level

Specification

System Interfaces High Level

Specification's document

The Bidder

3 Design of HMI principles and

interaction flow

HMI Principles document The Bidder






4 Design of IAA’s specific

Requirements - High Level

Specification

IAA Specific Requirements -

High Level Specification

Document

The Bidder

5 Defining System Tests Description of all the System tests

(STD)

The Bidder

6 Formation of a Preliminary

Installation Plan

Preliminary Installation Plan

document

The Bidder

7 Formation of a Preliminary

Training and Assimilation Plan

Preliminary Training and

Assimilation Plan document

The Bidder

8 High Level Design Review

(PDR)

PDR– Summing Up document The Bidder

9 IAA's approval to PDR PDR Approval document

IAA

7.3.5.5.3. Detailed Design (for ALL Work Packages)

1. In this phase, IAA would not need to approve some of the deliverables of this stage. IAA

would merely approve receipt of the deliverables, but not their content. All deliverables

that do not need to be approved by IAA are marked – Not a formal deliverable. For the

avoidance of doubt, it is hereby clarified that the abovementioned shall not derogate

from the full and complete responsibility of the Selected Bidder for the performance of

the Project in compliance with all of the Functional Requirements and any other and/ or

additional requirement as stipulated in the Contract.

2. Detail Design Activity Table:


1. Detailed Specification for each

Working Position for the phase

Detailed Specification for each

Working Positions document –

The Bidder

2. Detailed system Architecture Detailed system architecture

including network and end

devices

The Bidder

3. Detailed Design of the System

Data Model (especially for new

developed items such as IAA’s

Specific Requirements)

Detailed Design of the System

Data Model document – Not a

formal deliverable

The Bidder






4. System Interfaces Detailed

Specification

System Interfaces Detailed

Specification's document

The Bidder

5. Detailed Design of The System

HMI

Detailed Design of The System

HMI document

The Bidder

6. Detailed Maintenance Plan Including maintenance procedure,

repair procedure, use cases

The Bidder

7. Defining System Tests

Scenarios

Test Cases Scenarios document

(TCS)

The Bidder

8. Preparing a Validation Matrix

("VRTM") [see 7.3.7.2 below]

VM document for IAA's

approval.

The Bidder

9. Detailed Design of an

Installation Plan

Detailed Design of an Installation

Plan document

The Bidder

10. Detailed Design of Training

and Assimilation Plan

Detailed Design of Training and

Assimilation Plan document

The Bidder

11. Detailed Design Review (DDR) CDR Summary document The Bidder

Note: IAA reserves the right to review and comment the CDR document, addressing The

Bidder's attention to potential design issues.

7.3.5.6. Manufacturing / Purchasing / Development / Integration

1. Manufacturing / Purchasing / Development / Integration Activity Table:


1. Manufacture / Develop / Purchase of

all the Work Packages components

(including interfaces)

The Bidder

2. Unit Test to each of the

aforementioned System Components

(IAA is entitled to review the

deliverables upon its sole discretion)

Unit Test Summary

document – Not a formal

deliverable

The Bidder

3. Integration of all the System

components (including interfaces)

The Bidder






4. Integration Test for the phase (IAA is

entitled to review the deliverables

upon its sole discretion)

Unit Test Summary

document – Not a formal

deliverable

The Bidder

5. FAT environment / Site Preparation FAT site ready for use The Bidder

6. Training Courses Adaptation Training Materials The Bidder

7. Sanity Test for the Stage Sanity Test Summary

document

The Bidder

8. Bidder’s approval to the Stage

readiness for FAT

A Stage ready for FAT The Bidder

7.3.5.7. FAT & IRR

1. An important activity at this step is testing and approving IAA’s supplies according to

the agreed method as stipulated in the approved SER.

2. FAT & IRR Activity Table:


1. FAT document preparation FAT document The Bidder

2. FAT document approval FAT document approval IAA

3. Basic training to IAA's FAT's

witnessing group in case they

attend the FAT

The Bidder

4. FAT for the version (including

interfaces)

The Bidder

5. FAT Review FAT Results – Summary document The Bidder

6. IAA Approval of FAT Review Approval of FAT Review

document

IAA

7. Formal version ready for shipping

to IAA

The Bidder

8. IAA’s Supplies Acceptance

Tests document preparation

CFE AT document The Bidder

9. CFE AT document approval CFE AT document approval IAA

10. CFE AT Execution The Awarded Bidder is welcome to

witness

IAA






1. FAT document preparation FAT document The Bidder

2. FAT document approval FAT document approval IAA

11. CFE AT Review CFE AT Results – Summary

document

IAA

12. IAA Approval of CFE AT

Review

Approval of CFE AT Review

document

The Bidder

7.3.5.8. Delivering the System Components to Israel (Q)

1. The Bidder shall define, in the same manner as the tables above, all activities upon its

discretion.





7.3.5.9. Setting Up the Central System (Q)

1. Installation, Commissioning and Training are major activities during this stage.

2. Following are major activities and deliverables for this stage:


1. Preparation of Up-to-date Plan

for Setting up the Central

System

Plan for Setting Up the Central

System including Tests Plan and

Procedures

The Bidder

2. Setting Up and Tests

Documents approval

Approval of the aforementioned

Plans

IAA

3. Setting the Central System and

the Test Environment in both

Core rooms

The Bidder

4. Setting the interfaces to AODB

and DCRS

Test environment and preparing for

the operational environment

5. Conducting the Bidder’s

Internal Tests

The Bidder

6. Coordinating with all External

Interfacing Systems for

individual testing

The Bidder +

IAA

7. Training Courses Both for the Technicians and the

Operational Staff

The Bidder +

IAA

8. Conducting the Central System

Tests – Preliminary CS SAT.

Preliminary Test. This test can be

integrated with the SAT tests of

WP#E. It is a pre-requisite to

WP#BCD.

The Bidder +

IAA

9. Preparing Central System Tests

Report

Central System Tests Results – The

entire report

The Bidder

10. Central System Tests Review Central System Tests Results –

Summary document

The Bidder +

IAA

11. IAA Approval of Central

System Tests Report

Approval of Central System Tests

Report document

IAA

12. Formal version ready for Gates’

Installation

The Bidder





7.3.5.10. Gates’ Docking Sub Systems Installation, Commissioning and

Acceptance (Q)

1. The Bidder shall define all activities for commissioning the Gate’s Docking Sub

System’s Acceptance Tests.

2. The Bidder must plan carefully the installation of the DSSs at gates B C D, with the

coordination and approval of IAA, since it has a great influence on the business

continuity of the A-VDGS / VDGS services in TLV airport. The Bidder shall submit

as part of this proposal its proposed plan for the transition from the old system to the

new one.

3. During the installation of DSSs in concourses B C D, the Operators in the Tower will

work with two systems in parallel, the old VDGS system and the new A-VDGS

system.

4. In this transition Interim period, the DSSs shall be replaced one by one utilizing the

new infrastructure (Fiber optic passive network, Dedicated Core rooms etc.). Thus, the

commissioning of each DSS for B C D shall be planned carefully and with minimum

down time. The transition must include the dismounting of the old PDU and mounting

the new DSS on the existing poles, and perform acceptance test in order to return the

gate into operational mode as soon as possible. The expected down time for each gate

shall be no more than 24 hours.

5. When dismounting the old PDU it is essential to reconnect the f/o ring cable in order

to retain the redundancy operation of the old system.

6. The installation stage for Concourse E shall not influence the Current VDGS system.

It will be depended on the concourse E readiness (a new concourse).

7. The Gates' DSS Acceptance tests shall be conducted only after complete acceptance

of the Central A-VDGS System.

8. Each Gate DSS Installation, Activation, Calibration and Acceptance Tests shall be

executed within up to 24 consecutive hours.

9. Once IAA approves a Gate’s Docking Sub System’s acceptance, the Bidder shall

commence the Warranty period according to the SLA (Chapter 8).

10. The following table depicts major activities for each Gate’s DSS acceptance..


1 Up-to-date Setting up

Gate’s DSS Plan document

preparation

Plan for Setting Up the Gates DSS

Tests Plan and Procedures.

The Bidder

2 Setting Up and Tests

Documents approval

Approval of the aforementioned

Plans.

IAA

4 Setting the Gates’ DSS’s For BCD: careful planning according

to IAA approval. Replacing the old

PDU one by one with minimum

influence on the current system

The Bidder

with IAA

approval






5 Conducting the Tests The Bidder +

IAA

6 Gates’ DSS’s Tests

Review

Gates’ DSS’s Tests Results –

Summary document

The Bidder

7 IAA Approval of Sites

Review

Approval of Gates’ DSS’s Tests

Review document

IAA

8 Formal version ready for Overall

System’s Final SAT

The Bidder

7.3.5.11. SAT

1. Following is the SAT Activities table:


1. SAT document preparation SAT document The Bidder

2. SAT document approval SAT document approval IAA

3. SAT Readiness Review Version Document Description

(VDD) for the SAT.

The Bidder

SAT Readiness Review - Summary

document

The Bidder

4. SAT for the formal System

Version

The final SAT for the CS shall be

combined with the final SAT of

BCD or E whichever starts later.

The Bidder

5. SAT report preparation SAT report The Bidder

6. SAT Review SAT Results – Summary document. The Bidder

7. IAA Approval of SAT

Results

Approval of SAT Results document IAA

8. Formal Version ready for Soak Test The Bidder

7.3.5.12. Soak Test

1. During this stage, IAA will study and review both the System Performance and the

Management Application(s) suitability to IAA needs.

a. The Supplier's specialist shall accompany this stage at IAA facilities in Israel

during the SOAK Period for at least two weeks with optional extension of





two more weeks. During this period the Supplier's specialists shall perform

All Maintenance procedures with the IAA relevant involved bodies.

b. During this stage, status meeting shall be held twice a month at IAA facility

in order to report and verify various relevant issues.

c. The SOAK of the Central system is combined with the SOAK of WP#BCD

or WP#E whichever starts later.

d. IAA aims to cover a wide spectrum of the A-VDGS services and scenarios.

e. At the end of this stage, based on the success of the soak period, the system

shall be announced ready for Operational Use.

f. The Bidder shall prepare a Soak Readiness Review (SORR) checklist that

will contain all pre-requisite tasks of both the Bidder and IAA responsibilities.

The SORR Checklist shall be coordinated and approved by IAA.

g. The SORR process shall follow the process described in section 7.3.4.

h. A document containing a list of anomalies / mal-functions and follow-up on

their repair shall be kept by the Bidder. IAA users or the Bidder will be able

to open entries in this table. This document will be reviewed periodically (by

meetings, conference call, and special visit by Bidder's engineers – all

according to the severity of the issues being addressed).

i. System adaptation issues shall be listed and fixed by the Bidder mainly during

the first half of the SOAK period. The timing of the System adaptation should

enable IAA a sufficient time to evaluate it. [IAA’s intention is that most fixes

will be done at the 1st half of the Soak period, which will enable IAA sufficient

time to evaluate the fixes contribution.]

j. Repairing anomalies / mal-functions that were found before or during the

SOAK period should be corrected during that period and are a prime

condition for a successful completion of the SOAK stage, and with it the

completion of the A-VDGS Project.

k. The Bidder shall pay attention to the activity in entry #6 in the table below.

The Soak incorporates 3 one month periods. Hopefully, both parties will be

able to execute it sequentially, however, if the fixes won’t suffice IAA and /

or the System will not be available for a significant period and / or the services

by the System will be unacceptable the Soak process will be halt and it will

resume upon resolving the issues that caused the halt.





7.3.5.12.1. A Possible Procedure for Anomalies reporting by IAA and Anomalies

Resolution by the Awarded Bidder (Q)

1. The Bidder shall introduce its proposed method to handle anomalies during the

Soak. The Bidder should note that IAA refers a very high importance to the Soak

Period, since it was proved to minimize / bridge the gaps between the written

requirement and the day to day needs to operate a the Message handling system in

the Israel. (Q)

2. The following procedure description is for expectations' coordination:

a. IAA will use a spreadsheet to report about anomalies.

b. The spreadsheet shall be managed by the Awarded Bidder.

c. The spreadsheet shall have 2 basic portions:

i. One that shall be filled by IAA.

ii. Another one that shall be filled by the Awarded Bidder.

d. IAA's portion shall incorporate all kinds of information that shall provide the

Awarded Bidder sufficient information to analyze the anomaly, to look into

the system logs, to select a solution path, to implement the solution and to test

its effectiveness in order that IAA will be able to close the anomaly.

e. IAA's portion shall include information such as:

# Information Item Description

1. Anomaly ID Unique identifier to each anomaly.

2. Severity 1 – Does not prevent SOAK continuing.

2 – Urgent; may prevent SOAK continuing.

3. Anomaly Status Open or Closed

4. Date Reported by

IAA

5. Contact Person to

discuss the

anomaly

6. Anomaly Type Such as: International Communication Line,

Interface …

7. Time UTC

8. A-VDGS System

Components

Involved

Such as: Server, Splitter, …






9. Description of the

anomaly

Free Text

10. Additional

Information as

needed

Such as referring to photograph and / or a

document etc.

11. Possible Relevant

Environmental

Circumstances

Such as Power Outage, Air-conditioning

Outage, IAA's Communication Network

disruptions etc.

12. Others (Q) Upon the Bidder's discretion

f. The Awarded Bidder's portion shall include information such as:


1. The Awarded

Bidder Anomaly

Label

According to its acquaintance with the

system's internal components.

2. The Awarded

Bidder Action Plan

For the various activities such as: data

gathering, analyzing the data, formation of a

conceptual solution …

3. The Awarded

Bidder Requests

from IAA

Such as: access to the Test or the Production

System, special inputs from interfacing

systems, etc.

4. Expected Next

Update to the

Action Plan

At that date IAA expects a status report about

the anomaly.

5. Others (Q) Upon the Bidder's discretion.

g. The Awarded Bidder's responsibilities are as follows:

i. Review the daily reports submitted from the IAA. The Awarded Bidder

will group and evaluate the anomalies.

ii. Will report to the IAA within 3-5 business days the next steps for

evaluation. This is to allow The Awarded Bidder to evaluate any

emerging patterns of system performance. This communication will be

performed via emails and conference calls as necessary.





7.3.5.12.2. Table of Relevant Activities, Deliverables and Responsibilities

1. SOAK Period Activities Table:


1 Soak Readiness Review (SORR)

checklist document preparation

Soak Readiness Review (SORR)

checklist document

The Bidder

2 SORR document approval SORR document IAA

3 Trial run of the system Periodical system approval and/or

punch list of problems

IAA

4 Status meeting in Israel with the

Supplier’s specialists onsite

Status meeting – Summary

document (including a list of those

problems that must be fixed +

schedule)

The Bidder &

IAA

5 Fix problems Fixed problems report

Open problems report

The Bidder

6 Reviewing the Fixed problems

and open problems reports

Soak test continuity approval IAA

7 Soak Period completion meeting Completion meeting – Summary

document

The Bidder

8 Completion of soak Period Completion of soak test approval -

issuing a Final Acceptance

Certificate

IAA

7.3.5.13. Go Live Period - System is ready for Operational Use


1 SLA period commencement

(See Chapter 8 of the Technical

Requirements)

Starts when the first DSS is

operational (in BCD or E)

The Bidder





7.3.6. Project Plan

7.3.6.1. Principles and Guidelines

1. The Project work plan shall refer to IAA's requirements as stipulated in

clauses 7.3.2 above.

2. The project work plan shall include all the stages / sub-stages of the project

as mentioned in clause 7.3.3. The plan shall be built in such a way that

clarifies for each milestone the activities that are prerequisites to the full

completion thereof. (Q)

3. The project work plan shall include all the formal reviews of the project and

also the reviews that will be defined during the project, as mentioned in the

Proposal.

7.3.6.2. Work Plan for Setting up the WP#CS WP#BCD and/or WP#E

System

1. Within the Bidder’s integrated project plan, the Bidder shall provide the

following:

a. A project plan detailing the tasks, sub-tasks, dependencies,

resources and timeframes, deliverables, etc. for each stage.

b. The Bidder shall explicitly specify all the tasks that are within

IAA’s “court” for each activity, as well as the timeframe it

allocated to each of IAA’s tasks.

c. For avoidance of a doubt, IAA states that the Bidder would not

assume that IAA would supply any equipment for the project’s

purposes, other than those that are explicitly declared in the tender

documents.

2. The Bidder shall gather all the above-mentioned IAA’s tasks into one

Appendix - "IAA's Activity/Tasks" that shall be submitted as part of the

Proposal. This appendix shall contain a complete list of all IAA's tasks

a. This Appendix shall be valid only after a written approval by

IAA. IAA's approval shall be an integral part of the Technical

Specification approval as stipulated in the Contract.





b. This Appendix shall be the sole source for any of IAA's tasks

within the Project. Any task and /or activity and /or work and / or

service and / or a Component etc., that are not mentioned in this

Appendix, and are required for the successful completion of the

Project, shall be deemed as The Selected Supplier's obligation

whatsoever.

c. For each task, the Bidder shall elaborate as follows:

# The

Task

Reference

within the

Bid

Relevant

Stage of the

Project

Due

date for

delivery

Reference to

a sample (if

applicable)

1

2

..

d. For avoidance of a doubt, IAA declares, that a task within the Bid

that is associated with IAA but is not included in this appendix,

shall not oblige the IAA.

e. Each of IAA’s tasks will be inspected by the Selected Bidder and

will be approved / commented in writing. The inspection /

approval shall be done prior to the installation of the relevant

Systems’ components.

f. The number of tasks and their impact on IAA's obligations shall

have significant impact on the technical evaluation of the Bidder's

response. (Q)

3. A Gantt chart of the project shall be submitted along with the Bidder’s

Proposal, as an MS-Project file and in Excel and PDF files. IAA encourages

the Bidder to use its own templates for the Gantt Charts. IAA described the

Project Major Stages through the timeline / phases of the Project; however,

the Bidder may use its standard template with the required adaptations. (Q)

4. Following is an example for illustration purposes solely:

a. A-VDGS Gantt (Partial Sample): Level 1 and 2





b. A-VDGS Gantt / Tests (Partial Sample): Level 3

c. A-VDGS Gantt / Installation (Partial Sample): Level 3

5. Any delay in the execution of any activity or milestone shall be announced in

writing to IAA.

6. The re-scheduling of a delayed activity/milestone shall be approved by IAA;

otherwise the original schedule of the activity/milestone shall remain valid.

7. Every new revision of the plan approved by IAA shall be set as a new baseline

for tracking and reporting purposes. The Bidder shall keep the history of all

the baseline plans and not override them.





7.3.7. Tests

1. The Bidder shall introduce its proposed test methodology, test plan, test

activities and deliverables throughout the whole lifecycle of the Project (Q).

2. The Test Program shall refer to IAA's requirement below (P).

7.3.7.1. General

1. The test program stands to prove that the A-VDGS system delivered by the

Bidder is fully compliant with the Bidder’s proposal and IAA Requirements.

2. Tests shall refer to:

a. Central System, HMI and interfaces.

b. Gates’ DSS’s Acceptance.

c. Overall System Acceptance (Successful SAT).

d. Overall Service Acceptance (SOAK Completion).

3. The Subsystems / Components Acceptance and the overall System

Acceptance tests are the sole responsibility of the Selected Bidder's.

4. The final system acceptance shall be based upon the successful execution of

functionality and performance tests. If the System fails to meet (for example)

the expected performance, it shall be the Bidder's obligation to correct and/or

to add components and/or to enhance the configuration etc. to meet the

required functionality and performance.

5. Note that the Final Acceptance Tests for the Central System is combined with

either WP#BCD or WP#E whichever starts last.

6. The Overall Service Acceptance / the Soak Test would be led by IAA;

however, the Selected Bidder shall accompany this phase.

7. Regarding the Overall System Acceptance, some parameters, particularly

those concerning system reliability, availability, and continuity of service,

shall need to be tested over an extended period of time. This may impose

constraints on the initial operational use of the system until adequate

statistical evidence has been obtained to provide the necessary degree of

confidence.

8. Subsystems / Components Acceptance tests shall include (for all Work

Packages where applicable):

a. The Central System (functionality, redundancy, HMI, interfaces

etc.).





b. IAA Specific Requirements.

c. Communication Network

d. Gates’ DSS’s.

e. Other, upon the Bidder's discretion.

9. System Acceptance tests shall include but not limited to:

a. Functional tests of A-VDGS operational process in the central

system

b. Functional tests of A-VDGS process at the DSS level (local and

connected)

c. Functional tests of the Technical CMM (Control Monitoring and

Management) application (including maintenance procedures,

reports, logs, information security etc.)

d. AODB interface test

e. DCRS interface test

f. NTP interface tests

g. Redundancy tests (servers (SW and HW, Data base, network, WS,

interfaces)

h. Performance and capacity tests

i. Network testing

j. Reliability and maintainability tests (e.g., replacing LRU, detecting

faults etc.)

k. Working position HMI and functions for each of the system roles

l. More tests as required by the VRTM document (see next clause)

7.3.7.2. Verification Requirements Table Matrix

1. The purpose of the Verification Requirements Table Matrix ("VRTM") is to

define for each RRD requirement its validation (testing / proving) method,

and the relevant phase(s) in the Program in which it is going to be conducted.

Composing a VRTM is part of the Program CDR.

2. The Bidder shall submit for IAA's approval a final VRTM well before the

beginning of the Acceptance tests, and before submission of the Test Plan

documents.





3. Each and every requirement in the RRD document should occupy a line in

the VRTM table with complete data to enable IAA to review it. In the

reviewing process IAA should be able to easily trace for each requirement

when it is going to be tested and the exact testing procedure / step designed

to prove it. (In case the VRTM is submitted before final test plan documents

are completed, IAA will verify the general validation method, and only later

the actual test procedures when submitted to IAA).

4. The following are considered to be the most important fields for the above-

mentioned tractability approval:

Requirement

ID

Validation Method Project stage

(e.g. SAT,

Sub-SAT,

etc.)

Procedure

document

name

Section Test

Case

Name /

step

testing, inspection,

demonstration,

analysis, etc.

These 3 fields are the ID of

the testing procedure / step

The combination <Procedure document name, Section, Test Case

Name/step> defines the exact procedure/step(s) designed to prove the specific

requirement.

5. Verification Method is how the requirement is going to be tested / proved /

demonstrated. To mention a few:

a. Product Qualification Tests

b. Test during FAT, Sub-SAT, SAT, SOAK

c. Laboratories tests

d. Compliance certificates with standards (such as FCC for

example)

e. Winning Bidder's declaration (to be minimized)

f. Written statement by a 3rd party vendor

g. Inspection / demonstration during training

h. Mathematical / Theoretical analysis

i. Real Field Measurements

j. Other

6. It should be noted that IAA has to approve the System Requirements

Validation as proposed by the Bidder. This may be done in two stages: First





IAA reviews and approves the VRTM: that all the RRD requirements are

addressed (completeness), the method of verification (i.e. testing, inspection,

demonstration, analysis, etc.) and at what stage(s) of the project this

validation shall be done. The second stage is to review and approve the actual

Test Plan documents which inter alia detail the exact test procedures or other

validation procedures.

7. Following is a “Block Diagram” illustrating an Overview of the VRTM:

7.3.7.3. IAA Expectation from a FAT / SAT / Sub SAT document

1. The Bidder shall provide IAA with a FAT / SAT document that shall cover,

at least, the following subjects (the following requirements intend to enlarge

the requirements in other Chapters, such as Chapter 5 rather than narrowing

them):

a. Test Environment: Hardware, Software, Other Test Equipment, Pre

AT (Acceptance Tests) conditions, Test data and data generation tools,

participants, Precautions, etc.





b. Safety Precautions

c. Test Forms: That shall incorporate, inter-alia the test procedures, the

steps in them, the expected results for each procedure / step.

d. Test Work Plan: Formatted Acceptance Test (AT) Documents which

shall specify at least the following:

i. What is going to be tested, when and under which

conditions?

ii. Who will participate in each test

iii. Timetable for results submission, presenting and discussing

the results with IAA, result approval by IAA, correcting

issues by the supplier.

iv. Retesting and Regression’s tests.

7.3.7.4. Factory Acceptance Test (FAT)

1. The purpose of the FAT is to demonstrate that all items of the intended A-

VDGS are correctly manufactured, or developed, and meet their individual

requirements.

2. The required FAT shall be performed and documented before shipment to

site.

3. The Bidder shall present to IAA in the FAT Test Plan document the intended

test, and define for each of the tests:

a. Test purpose – description of the system feature or requirement to be

tested.

b. Test Equipment –

i. Description of any test equipment and conditions needed to

perform the test.

ii. If proprietary test equipment is used, IAA would like The

Bidder to introduce it to IAA in order that IAA will gain

confidence in this test tool.

iii. For non-proprietary test equipment, IAA would like the

Bidder to attach the laboratory certificates that verify that the

test equipment is valid at the time of conducting the test.

c. Test Procedure - description of test method, including analysis of test

data.





4. IAA reserves the right to attend and witness the FAT execution.

5. Should problems materialize during the FAT or should the FAT results be

deemed unsatisfactory in any way by IAA, the problems shall be corrected

after (not during) the test and the status shall be solely defined by IAA.

6. The System Supplier shall take full economic responsibility for any required

retesting program. If during the test, additional tests become necessary, IAA

has the right to request their execution.

7.3.7.5. Site Acceptance Test (SAT)

1. The SAT shall prove that all System/Subsystem requirements at their site

specific installation and location are met.

2. The Bidder shall prepare a SAT Readiness Review (SARR) checklist

containing all SAT pre-requisite tasks with clearly defined division of roles

between the Bidder and IAA. The SARR Checklist shall be coordinated and

approved by IAA.

3. The SARR Review process shall follow the process described in section 7.3.4.

4. The SAT shall be carried out in IAA's facilities in accordance with SAT

Specification.

5. The SAT shall make use of both simulations and real data recordings as input,

if so required.

6. The Bidder shall provide IAA with the SAT documentation for approval prior

to SAT execution.

7. IAA representative(s) shall witness the SAT.

8. As the SAT shall include a number of live trials, IAA is prepared to provide

for the environment for such trials and operational/technical staff to perform

specified actions.

9. Before starting the SAT, all non-conformances and reservations recorded in

the FAT report shall be removed.

10. The SAT schedule shall be specified in the project work plan.

11. The Bidder shall provide the SAT report as scheduled in the project work

plan.

12. Results of each single test shall be mutually verified; however the PASS /

FAIL evaluation shall be approved solely by IAA.





13. Should problems materialize during the SAT or should the SAT results be

deemed unsatisfactory in any major way by IAA, the problems shall be

corrected after (not during) the test and the status shall be solely defined by

IAA.

14. The Bidder shall take full economic responsibility for any required retesting

programs. If during the test, additional tests become necessary, IAA has the

right to request their execution.

15. The Bidder shall provide a concise description for the SAT (Q)

7.3.7.6. SAT Closure

1. The Supplier shall fill for all failed test and / or for each anomaly occurred

and/or for each known bug / deficiency at SAT commencement the table

below:

2. The Correction Path Table:

# VRTM

Identifier

Problem /

Issue

Description

Reason

/

Theory

Proposed

Corrective

Action

Estimated

Contribution

to SAT

Results

Verification

Method

Verification

Due Date

Reference

to the Test

Case

Correction

Plan

Activities

Comments

3. A Waiver / Deviation Request shall incorporate the following information as

a minimum:

Req. # Contract

Paragraph Requirement Event

Procedure

Document

Test Case

Name

Product Test

Report

7.3.7.7. System Overall Acceptance Tests, Minimal Scope - Highlights

1. The following list of tests elaborates on some requested tests mentioned

at 7.3.7.1, and shall enlarge the Selected Bidder's test obligations rather than

reduce them.

2. The following not inclusive test types and areas shall be included in the SAT

plan proposed by the Bidder. Final test procedure shall be determined at the

detail design reviews.





7.3.7.7.1. General Tests

1. Start-up Time

2. Switch Over Time

3. Maximum Working Positions capacity

4. Maximum DSS capacity

5. Response time in various system tasks

6. Administration capabilities

7. Archive and data backup

8. Processing Delay

9. Common repair tasks (for testing MTTR of LRUs)

10. Stress Tests - including high loading, failure scenarios, wrong inputs, non-

valid values for system configurable items, etc.

11. The Bidder shall provide a concise description for the General Tests (Q)

7.3.7.7.2. Human – Machine Interface Tests

1. Special attention shall be made to testing HMI features that are not part of the

generic product, and were developed/ configured / adopted per IAA's

requirements.

7.3.7.7.2.1. General

1. HMI parameters & performance.

2. Multiple working position tests (e.g. various authorizations, etc.).

3. WP functionality.

4. Operational Data Management WP functionality.

5. Roles and authorization

6. Test environment mode

7. The Bidder shall provide a concise description for the HMI Tests (Q)

7.3.7.7.2.2. Maintenance working management positions

1. Please refer to the functionality described in Chapter 3

2. System components status and maintenance info display and reports

(Situation awareness picture, alerts, events, tasks etc.)





3. System performance degradation alerts and information display

4. System’s components configuration and management tools

5. System’s Events and Audible alerts management

6. Users and roles management

7. The Bidder shall provide a concise description for the Maintenance

Functionality Tests (Q)

7.3.7.7.3. Interfaces to Existing Airport Systems Tests

1. Per the requirements in Chapter 5.

2. Redundancy tests for interfaces

3. Interfacing to Test environment

4. The Bidder shall provide a concise description for the Interface to External

Airport Systems (Q)

7.3.7.7.4. System Availability Tests

1. Server redundancy tests

2. Network redundancy tests

3. Power failure and cold start-up

4. Work positions failure

5. The Bidder is encouraged to detail about other tests based on the proposed

architecture

6. The Bidder shall provide a concise description for the System Availability

Tests (Q)

7.3.7.7.5. DSS Tests

1. Detecting the A/C in straight and curved line

2. Detecting the A/C with obscure regions (like the Bridge)

3. Wrong A/C is approaching

4. A/C is not aligned to center line

5. The accuracy of the display reading compared to actual position of the A/C

6. Moving too SLOW or too Fast on the center line

7. STOP too Far conditions

8. On/OFF block messages to AODB

9. Obstacle detection tests

10. Repeating the tests for night, dawn, twilight, strong day light conditions

11. OCU tests





12. Local / connected mode tests

13. Other functional tests

14. Environmental Conditions Tests

15. The Bidder shall provide a Test plan of each DSS for a period of minimum

two weeks and at least 50 parking operations (Q). The aforementioned plan

shall cater for evaluation purposes solely.





7.3.8. Training

7.3.8.1. General

1. Training shall accompany, as an integral part of the project plan, each product,

module, sub-system or system that shall be delivered to the IAA. (PQ)

2. All training shall be performed either at IAA Premises in Israel or at the

Bidder's premises, according to IAA sole discretion. (PQ)

3. The bidder shall certify Technical-Users that participated in the technical

courses to perform system maintenance procedures. (PQ)

4. Practical training shall take place in class rooms which shall be equipped with

operational A-VDGS / A-VDGS end stations. (PQ)

5. The Bidder shall describe whether the class room will be part of the

operational A-VDGS / A-VDGS system or a standalone system with the same

capabilities for the training. (Q)

6. Both configurations shall not affect the operational system and disrupt its

performance and availability. (P)

7. All training shall include a theoretical and a practical part. (PQ)

8. The courses syllabus shall be coordinated with IAA and adapted to IAA

specific needs. (PQ)

9. The practical part shall include a real life system for the operational use. (Q)

10. The Bidder shall conduct a competency based training program to IAA's

Operational staff in accordance with the Project Plan at schedule. (Q)

11. The Bidder's trainers shall have formal training qualification and appropriate

experience. (PQ)

12. The Bidder shall issue a certificate of competency to each trainee that

successfully completes the training program. (PQ)

13. The bidder shall provide training courses in any case of a major system

change/update that affects the Technical and/or the Operational procedures.

(PQ)

7.3.8.2. Training Material

1. The Bidder shall provide course materials (manuals, drawings, presentations,

handouts, etc.) for each of the trainees. These materials shall cover all aspects

of the IAA system. (PQ)

2. The Bidder shall coordinate with IAA the exact amount of training material

hard copies at least one month prior to the planned training courses. (P)

3. In addition, all training materials shall be supplied to IAA in soft copies

(using removable media device – e.g. CD, DOK etc.). (PQ)





4. The Bidder shall provide the soft copies training material at least one month

prior to the planned training courses. (P)

5. Training material format shall be produced according to Documentation

format requirements as specified in section 7.3.10.7. (P)

7.3.8.3. Type of Courses

1. There are four categories of training courses: (Q)

a. Operational End Users training: System Operational use for all the A-

VDGS users. Including central system and OCU operation.

b. System Operational Managers/Experts training: That should

incorporate the operational management capabilities.

c. System Technical Users training: That should incorporate the entire

technical user’s capabilities.

d. System Technical Managers training: That should incorporate the entire

technical management capabilities.

2. The Supplier shall obligate to be able to provide certification / training course

for the system during the lifetime of the system. (PQ)

3. The A-VDGS Supplier shall provide the following training courses [The

selected bidder shall suggest the location for each course and/or merging

courses based on added value of such act and IAA approval]:

# of Cycles Location Schedule Participants Course Name #

1 Bidder’s

Premises

Prior to FAT Up to 6 Operational End

Users (1)

1 Bidder’s

Premises

Prior to FAT Up to 6 System technical

Users (2)

5 Israel Prior to 1st DSS

Acceptance

6 - 13 Operational End

Users (3)

1 Bidder’s

Premises

Prior to 1st DSS

Acceptance

Up to 6 System technical

Users (4)

1 Bidder’s

Premises

Prior to SAT 3 System technical

Management

(advanced

training)

(5)

1 Bidder’s

Premises

Prior to SAT 4 Operational

managers

/experts

(6)

4. Operational users’ courses duration shall be coordinated with IAA. For

courses that will be held in Israel, their duration should not exceed two





consecutive days due to operational constraints (shifts rosters). In case of

operational users’ courses longer than two days, IAA may require to split the

courses. (Q)

7.3.8.4. Expected Response

1. For each training course included in the Proposal, the following details shall

be included: (Q)

a. Course name.

b. Course syllabus

c. Course teacher name, profession and experience.

d. Course objectives, including the skills to be taught as well as how the

course participants will be examined on all aspects covered.

e. Course level, prerequisites and intended audience.

f. Course duration and schedule, including detailed timetable for each

day.

g. Course materials to be handed out to each one of the participants.

h. Recommended / maximum number of participants (included in the

Proposal).





7.3.9. Documentation

7.3.9.1. Details of documentation (PQ)

1. The Bidder is required to provide the necessary documentation for the safe

operation of The A-VDGS.

2. The Bidder shall undertake to revise the documentation with every upgrade

of The A-VDGS and/or peripheral hardware.

3. The documentation shall be tracked with version control mechanism.

4. The documentation shall be open to inspection by the IAA at any time.

5. The documentation shall be updated once a year as part of the Maintenance

Services

7.3.9.2. Specific requirements (Q)

1. Configuration documentation of the A-VDGS system.

2. Operational manuals

3. Bill of quantities

4. Spare part and consumable list

5. Site operating procedures, including change management, homologation

processes

6. Health and safety policy manuals

7. Operating and maintenance manuals

8. Service Level Agreement (SLA) & Service Delivery Plan (SDP)

9. ICD for data and / or services exchange with external information systems.

7.3.9.3. End User Manuals

1. Complete guides to the safe use of the A-VDGS system end devices and

peripherals for End-Users

2. Quick Reference Guides

3. Abbreviated version of the manuals for End-Users to include troubleshooting

of peripherals

4. The Bidder shall list all other documentation, which will be provided as part

of its basic Proposal. (Q)

7.3.9.4. Quantities

1. Note: The documentation shall be provided in the English Language. A soft

copy either on CD-ROM or another removable media device shall also be

provided to allow IAA to make additional copies for End-Users. (PQ)





7.3.9.5. Documentation List – Concentrated

1. The following table incorporates all requested documents as appear through

the Tender Documents. The list is introduced solely for tracking convenience

of all the involved parties.

2. The Documentation List:

Requirements

Documents

System

Application

Documents

Test

Documents

Project Management

Documents

Operations and

Maintenance

Documents

Revised

Requirement

Definition

(RRD)

System

Architecture

Conceptual

Test Plan

Program

Management Plan

Operational

User’s Manuals

Verification

Requirements

Table Matrix

(VRTM)

Site Engineering

Report

FAT

Procedure

and Plan

QA Plan and other

documents

Technicians

User’s Manual

System

Interfaces

Specifications

Installation Plan FAT Report Risk Management

Plan and other

documents

Version

Description

Document

HMI

Specifications

Inspection of the

Installed Base

Pre-SAT

Procedures

and Plan

Monthly reports

Interface Control

Document(s)

[ICD(s)] to the A-

VDGS / A-VDGS

sub-systems

Pre-SAT

Report

Steering Committee

Agenda and Report

Reviews Agenda and

Report

7.3.9.6. Other Documentation

1. The Bidder shall list all other documentation, which will be provided as part

of the System. (Q)

7.3.9.7. Documentation Format (P)

1. The Project's documents will be produced with MS Office (2010 version of

higher) tools (such as: MS Word, MS Excel, PowerPoint, Visio, etc.).

2. The Bidder shall submit PDF copies in addition to the Office documents, if

IAA asks for it.





3. All diagrams will be submitted in Visio or in AutoCAD format, or both, as

set by the IAA.

4. Gantt charts shall be submitted in all the following formats: MS Project, MS

Excel and PDF.

7.3.10. Involvement of the Bidder in the CFE activities

1. Following is a description regarding the Involvement of the Bidder in

Accompanying, Guiding and Controlling of other IAA's Contractors /

Interfacing Systems' contact persons

2. The Bidder shall support the IAA Infrastructure setup executed either by IAA

and / or by other IAA contractors, as follows:

# Stage Description of involvement

a. Requirements

definition

Provide the requirements definition document to the

design and/or executing entity in the station.

Work meetings for clarification of the requirements

definition (one or two meetings).

b. Assistance in

design

Telephone response to questions.

Work meetings.

c. Reviewing the

detailed plan

Reviewing the detailed plan.

Passing the comments document.

A work meeting aimed at clarification of comments

Reviewing the amended version of the detailed plan.

d. Purchasing,

execution,

installations

Telephone response to questions.

One or two on-site visits at the start of and during the

works.

e. Acceptance tests Full involvement in the tests.

f. Approval of the

infrastructures

Full and final approval of the infrastructures, verifying full

compliance and adequacy for the intended A-VDGS

System.





7.3.11. Installation Requirements

1. The Bidder shall describe in details his compliance with the requirements in

Sections 7.3.11.1, 7.3.11.2, 7.3.11.3 below. (Q)

7.3.11.1. General Characteristics of the required services

1. Variability Among Deployment Sites

a. In planning, execution and installation of all the relevant equipment and

supporting infrastructure (hereinafter the Element), the Bidder shall

take into account possible variations between the different positioning

sites, including such constraints as: positioning space constraints,

sources of electricity and data feed, temperatures and ventilation,

induction, service access, requirements dictated by other equipment

installed in the area, textures and structures of ceilings / walls / other

supporting infrastructures, method of mounting (wall mount, ceiling

mount, pole mount etc.), maximal accessibility for service personnel,

minimal disturbance to traffic in proximity of the Element, prevention

of direct lighting and other reflections and so forth.

b. For avoidance of any doubt, it is clarified hereby that no extra payments

whatsoever shall be paid to the selected Bidder due to the

aforementioned variability among deployment sites.

2. Planning and Construction Law

The Bidder must operate according to the Planning and Construction Law,

Israeli Standard 5435 and other official regulations.

3. Safety

The Bidder shall be aware of the existing hazards during the execution of

works on the airside and in the proximity of airplanes and other vehicles and

operate according to IAA's safety regulations.

4. Sub-Project

a. Each physical site in which the services and the goods specified in the

Technical Appendixes shall be required – shall be characterized as a

separate sub-project, including: capacity of work, time schedules etc.

b. The Bidder shall adjust to the required nature of work in IAA and

supply optimal response to such needs as:

i. Simultaneous execution of a number of sub-projects.

ii. Significantly reduced time-to-operation from raising a need to a

fully operational Element.





iii. Compliance with the actual target schedules as required in the

Project.

iv. Around the clock work and/or working during hours in which the

airport does not provide customer services and according to safety

regulations.

5. Execution Schedule

a. The Bidder shall work during hours that do not collide / conflict with

services for customers and/or movement of airplanes and/or other

works.

b. If the need arises, IAA at its sole, absolute discretion may order the

Bidder to work on Saturdays, Sundays, holidays, etc. (excluding Day of

Atonement). If there is a specific day on which the Bidder team cannot

work, it shall inform IAA in writing at least two months ahead of that

day.

7.3.11.2. Installation responsibilities

1. The Bidder shall carry out the installation of the Element in accordance with

its procedures as submitted to IAA for review.

2. The Bidder shall submit drawings to IAA for approval of any temporary

works, major equipment, etc. that it requires on site in the execution of the

Contract's Services.

3. During the installation, the Bidder shall coordinate its works with other

Subcontractors working in the same and adjoining areas, so as to ensure that

no delays are caused to work of others.

4. The Supplier shall review with IAA the installation sequence schedule prior

to starting the installation.

5. All mounting elements/brackets, either mounted on the wall or hanged from

the ceiling, shall be produced at a workshop prior to delivery to the site.

6. The mounting method to any building's element shall be reviewed, in

advance, by the building's constructor.

7. The selected Bidder shall verify the leveling of all elements in the horizontal

plan and in the vertical plan.

8. Upon completion of each task, the delivered equipment and working areas

shall be clean and in a working state and/or ready for immediate use.

9. The delivered equipment shall be protected against any damage until entering

into operation.

10. Throughout the installation period, the Bidder shall ensure that an appropriate

number of full time site supervisors are present at the site to ensure proper

installation of the System.

11. The installation work shall be executed in cooperation with the IAA.





12. All works shall be installed strictly in accordance with approved drawings,

specifications and procedures.

13. The Bidder shall provide and install all necessary equipment in connection

with the Element in order to ensure the correct and proper functionality. This

includes cabling, cable trays, supports, mountings, interface equipment with

networks or other systems, etc.

14. These associated deliveries or works shall be included in the Contract, unless

explicitly stated otherwise.

15. The Bidder shall inform IAA about the power consumption of all hardware

parts to be installed in order to allow IAA to provide either standard mains

voltage or guaranteed power using on-line UPSs.

16. The System Supplier shall be responsible for the ICD specification and

integration.

7.3.11.3. Installation Priorities and Considerations

1. The System Supplier, in cooperation with IAA and IAA’s designated

authorized representatives, shall investigate in detail and define solutions on

operational, functional or technical problems that may arise due to the

installation and operation of the equipment.

2. Whenever it is possible, the Bidder shall involve IAA personnel in installation

and preparation works.





7.4. Project Management / Governance – Reference Procedures

7.4.1. Introduction

1. This Section specifies the control and reporting tools and also additional rules

that shall serve as a basis for the management concepts to be implemented

throughout the execution of the project.

2. The Bidder may attach its own procedures for the Managerial Procedures. (Q)

7.4.2. Managerial Procedure Objectives

1. The management of the project shall be based upon the following managerial

elements:

2. Forums & Meetings

a. Steering Committee

b. Project Directorate (PD)

c. Technical Board

3. Procedures:

a. Project Management reviews (PMR)

b. Quality Reviews

c. Formal Reports

d. Risk Management

e. Quality Management

f. Test Management

4. The Bidder shall present its proposed Project Management / Governance

Procedures, which it trusts to be effective in bringing the A-VDGS Project to

completion, successfully, on time, on scope, on quality and on budget. (Q)





7.4.3. Forums & Meetings

7.4.3.1. General

1. After each meeting / forum the Bidder’s A-VDGS Project Manager shall be

responsible to deliver the minutes, including any relevant written materials,

in an official document that shall become formal once it is approved by IAA.

2. It is preferable that a meeting minutes draft is prepared during the meeting by

the Bidder's leader of the meeting, and is reviewed and agreed between both

parties during, or at the end of the meeting. The draft shall include the issues

that were discussed, agreements, resolutions, action items, risk and mitigation

thereof.

7.4.3.2. Steering Committee

1. The steering committee is a decision making forum who:

a. Receives and approves a consolidated status report prepared by the

project management team

b. Outlines strategic directions

c. Resolves high-priority and escalated issues

d. Directs and prioritizes activities at the operational and tactical levels

2. The steering committee is a joint IAA and Bidder’s Executive Level Forum

that is authorized to make decisions as described above. The committee shall

be convened and chaired by IAA’s Executive or anyone on his behalf, and

shall consists of:

a. IAA's management representatives and relevant stakeholders

b. Bidder’s Executive Manager

c. IAA’s Project Manager

d. Bidder’s Project Manager

e. Bidder’s Senior Technical Manager

3. The participation in the Steering Committee is mandatory. Any waiver shall

be coordinated and given with the prior consent of the Chairperson up to 5

days before the planned date of the Steering Committee. The Bidder’s

executive manager shall be responsible to nominate an appropriate

replacement and advise the Steering Committee forum in case of absence.

4. It shall be the Bidder’s A-VDGS Project Manager’s responsibility to prepare

an agenda and presentation documents (Microsoft Office format) prior to the

Steering Committee in coordination with the IAA’s Project Manager, and

distribute these files not later than 48-72 hours prior to the meeting.





5. Additional participants can be invited to the Steering Committee with the

prior consent of the chairperson.

6. The committee shall convene every 3 months in Israel or earlier upon a

specific need - on a schedule agreed with the Selected Bidder.

7.4.3.2.1. Minutes of the Steering Committee Meetings

1. The minutes of meeting shall be prepared by the Bidder's Project Manager

and approved by the IAA’s Project Manager prior to their distribution.

2. The Bidder's Project Manager shall prepare and publish after IAA approval,

up to 5 days after each meeting, a Word document titled "A-VDGS Steering

Committee – Meeting Minutes <date>".

3. The Minutes of Meeting shall include the following items:

a. Meeting Owner

b. Invitees

c. Participants

d. Unattended Invitees

e. Agenda – a predefined agenda shall be concluded between the

Bidder's Project Manager and the IAA’s Project Manager upon the

project line-up period

f. Meeting Decisions

g. Action Items - including the responsible person and the due date for

each item. These action items shall be tracked until closure and

reported on the subsequent Steering Committee.

h. Attachments – including the meeting status review report and any

other relevant materials.

7.4.3.3. Project Directorate (PD)

1. The mission of the PD is to enable effective coordination between all the

involved parties in the project both from IAA and among the Bidder's team

and subcontractors and also to enable control over the progress of the project.

2. The PD forum shall include:

a. Chairperson – the Bidder’s A-VDGS Project Manager

b. Bidder’s participants - Bidder’s A-VDGS Senior Technical

Manager and any other relevant team member(s) determined by the

A-VDGS Project Manager.

c. IAA’s participants - IAA’s Project Manager and additional

representatives on behalf of IAA determined by IAA’s Head of

Electricity Division Manager and Project Manager.





3. It will be possible, in coordination with IAA’s Project Manager, subject to

suitable security clearance, to invite additional participants to meetings of the

directorate.

4. The PD shall convene regularly on a weekly or a bi-weekly basis by

conference call, and every 6 weeks by a meeting at IAA. The responsibility

for the invitation of the PD is of the Bidder's A-VDGS Project Manager.

7.4.3.3.1. Minutes of the Project Directorate Meetings and / or Conference Calls

1. The minutes of the PD Meetings shall be prepared by the Bidder's A-VDGS

Project Manager and approved by the IAA’s Project Manager prior to

distribution.

2. The Bidder’s A-VDGS Project Manager shall prepare a detailed report with

the main management and technical subjects of the project, and submit it to

the PD 48-72 hours prior to the meeting, so the forum can review it before the

meeting.

3. Immediately after each meeting, the Bidder's A-VDGS Project Manager shall

prepare and publish, a Word document titled "A-VDGS Project Directorate –

Meeting Minutes <date>".

4. Each summary of the meetings shall include at least the following subjects:

a. Major comments made by the IAA’s Project manager

b. Major comments made by the Bidder’s Project Manager

c. Meeting Decisions

d. Work Plan Highlights for the near future

e. Main risks and concluded mitigation plan

f. New tasks or Action Items (including the responsible person and due

date for each item)

7.4.3.4. Technical Board

1. The technical board goal is to discuss and address imminent technical issues,

and escalate to the Project Directorate any unresolved issues.

2. A technical board shall be founded for the project to include:

a. Chairperson – Bidder’s Senior Technical Manager

b. Bidder’s Participants – relevant team members determined by the

Bidder’s Senior Technical Manager.

c. IAA’s participants - relevant technical experts determined by IAA’s

IAA Telecommunication Manager and Project Manager.

d. Optional participants - IAA’s Project Manager, Bidder’s A-VDGS

Project Manager

3. Additional participants may be invited to the technical board meetings in

coordination and with the prior consent of the IAA’s Project Manager.





4. The technical board shall convene every 6 weeks in a meeting at IAA, and by

conference call on a weekly basis or as necessary. The technical forum shall

be scheduled prior to the weekly PD forum meeting.

5. The initiative for a technical board meeting can be triggered by both IAA and

the Bidder, including the IAA’s Project Manager, and the Bidder’s A-VDGS

Project Manager or Senior Technical Manager. The responsibility for the

invitation of the forum shall be that of the Bidder’s Senior Technical

Manager.

7.4.3.4.1. Minutes of the Project's Technical Board Meetings

1. The minutes of these meetings shall be prepared by the Bidder’s Senior

Technical Manager and approved by the IAA Technical Manager prior to

their distribution.

2. The Bidder's Senior Technical Manager shall prepare and publish,

immediately after each meeting, a Word document titled "A-VDGS Technical

Board – Meeting Minutes <date>".

3. A summary of the meeting shall include at least the following subjects:

a. Previous meeting’s Action Items status

b. Made Decisions

c. List of newly opened issues and their status

d. Issue Highlights of the Work Plan for the near future

e. Identified risks and concluded mitigation plan

f. New tasks or Action Items (including responsible person and due

date for each item)





7.4.4. Reviews

7.4.4.1. Review Procedure

1. All the formal reviews shall be registered, as aforesaid, as a single milestone

or a series of milestones in the Project Management Plan including the

necessary precedent activities in the Gantt chart. All the technical and

managerial reviews that are to be established during the project shall also be

updated in the project plan.

2. Five (5) business days prior to the review, unless otherwise agreed upon

between the parties, the Bidder shall submit to IAA all the documentation

accompanying the review and the basis for their approval.

3. After the review, the Bidder shall prepare and publish a document titled

"<topic> Review Summary" (‘topic’ refers to each of the formal reviews

listed in the table above), and present it for the approval of IAA. The summary

shall include updates to the accompanying documentation of the review.

4. In case the review is associated with a milestone, its existence does not

constitute automatic approval of the milestone. Only after the review has

ended successfully and has been approved by IAA, the milestone will be

considered approved. IAA will approve the review, if the conditions for it are

matured, within 5 working days after its completion.

7.4.4.2. Readiness Review Procedure

1. The Bidder shall plan and create a comprehensive checklist, for each of the

readiness review activities and milestones that must be accomplished to

ensure the timely readiness of the relevant milestone.

2. This checklist shall include the list of the Bidder and IAA’s prerequisite tasks

/ actions, whose responsibility, due date, progress status and Red / Yellow /

Green (RYG) indicator for quick status visibility and tracking purposes. The

Bidder shall send the checklists for the review and approval of IAA.

3. The Review procedure of the Readiness activity shall be according to the

Review Procedure detailed in the previous clause.

4. The Bidder is requested to describe in its response how it is planning to meet

all the requirements above (1, 2 and 3) if he will be the selected Bidder (Q).





7.4.5. Reports

7.4.5.1. General

1. The Bidder is welcome to propose and introduce its reports that have been

successful in past projects. (Q)

7.4.5.2. Monthly Progress Report of the Project

1. By no later than the 5th of each month, the Bidder’s A-VDGS Project

Manager shall prepare and publish, with reference to the previous month, a

Word document titled: "A-VDGS Monthly Progress Report <- mmm-yyyy>"

and submit it for review and approval of the IAA’s Project Manager.

2. The report shall include at least the following clauses:

a. Executive Summary containing the status of the project in general, a

concise report in view of the progress time axis of the project, a report

on the main events during the previous month and details of the main

issues that require attention.

b. References to the main up-to-date Managerial Documents of the

project, with emphasis on an up-to-date Project Plan (Gantt), with clear

marking of any change from previous version, or deviation of actual vs.

plan, Customer (IAA) tasks, action Items status

c. Project risks and their mitigation plan, with emphasis on newly

observed risks.

d. Details of the main activities for the next month.

e. Staffing status, including but not limited to changes made and planned.

f. Procurement status of third party products.

g. Development status in view of subjects and components.

h. Status of formal deliverables.

i. Outstanding issues and recommended action plan.

7.4.5.3. Steering Committee Status Report

1. The Bidder’s A-VDGS Project Manager shall be responsible to prepare in

coordination and approval of the IAA’s Project Manager a Word document

titled: "A-VDGS Steering Committee status report”.

2. The Bidder’s A-VDGS Project Manager shall distribute the report no later

than 48-72 hours before the scheduled steering committee meeting.

3. The report shall include at least the following topics: (Q)





a. Goals (from previous meeting) status

b. Major and/or significant achievements accomplished during the

reporting period

c. Major Milestones Status – Actual vs. Plan

d. Action Items Status (from previous Steering Committee)

e. Outstanding Risks along with suggested Mitigation Plan to be

approved

f. Outstanding Open Issues along with suggested decision to be made

g. Production Readiness Status – Actual vs. Plan (when it becomes

relevant)

h. Main Change Request Status

i. Next Steps and/or Goals for the next period

7.4.6. Deliverable Management

7.4.6.1. General

1. The components / items that will be delivered within the project are defined

in Chapter 9 - BOQ to this technical appendix.

7.4.6.2. Method of Management

1. The various documents to be prepared within the project (including those for

analysis, design, testing, documentation, status reports etc.) shall be written

according to the standards defined in the Proposal. In special cases when

required, the Bidder can request to write a certain document according to

another standard that shall be presented to IAA for approval.

2. The table of contents and the template of each document included in the list

of the products of the project shall be presented to IAA, to the extent possible,

prior to the start of the work upon it and no later than 10 working days before

the time of its submission.

3. Submission of any formal document, including status reports, formal

products, formal addressing etc., shall be considered as having been carried

out if and only if this document was delivered in one, or more "hard copy"

(paper) and "soft copy" (CD) to IAA as agreed, and the IAA’s Project

Manager has confirmed their receipt.





7.4.7. Quality Assurance

1. The Bidder shall describe in its response how it complies with the

requirements in this section (Q)

7.4.7.1. General

1. Throughout the project, the Bidder shall take all measures in order to assure

that the supplied system and all the other products, including documents,

conform to the requirements detailed in the agreement and are of high quality,

according to the standards detailed in the documents of the agreement.

2. The Bidder shall implement a "quality assurance program" within the project

framework according to industry standards and the Bidder’s own QA

procedures and everywhere required as customary in the relevant field

internationally and based on "best practice" principles.

7.4.7.2. Organization and Responsibility

1. The Supplier shall assume sole responsibility for all issues of quality

assurance in the project, including implementation of the quality assurance

program of the project.

2. The Supplier shall appoint a quality assurance manager who shall be

responsible for the quality assurance processes that shall be applied in the

project.

3. In addition, one member of the project team shall be nominated as a quality

assurance monitor and shall serve as the quality assurance manager

representative in the project team.

7.4.7.3. Quality Assurance Plan

1. The Bidder shall prepare a quality assurance plan for the project, which shall

function as a tool for tracking and controlling quality assurance activities that

shall be carried out throughout the project.

2. The supplier shall make its best effort so that the quality assurance plan shall

include and address at least the following subjects:

a. Definition of quality assurance assignments and outputs in each

phase of the project's lifecycle.

b. Definition of the procedures and the standards by which the

system shall be developed.





c. Definition of the quality metrics (technical and managerial) that

shall allow for tracking the quality of the product and the progress

of the project.

d. Definition of the way in which data shall be collected as regards

to the quality metrics that were defined.

e. Definition of contents and times to perform the project's internal

quality audits.

f. Follow-up of essential issues such as: risk management and the

test plan.

7.4.7.4. Quality Audits

1. During the project, the supplier shall execute internal quality audits in order

to assure conformance to the quality requirements and plan.

2. At least one internal quality audit shall be made before each formal milestone.

The quality audits shall be indicated in the Gantt chart.

3. Following each quality audit, a report that summarizes the audit shall be

published.

7.4.8. Risk Management

1. The Bidder shall describe in its response how it complies with the

requirements in this section (Q)

2. The Bidder shall demonstrate its Risk Management Methodology by

analyzing the top 5 risks of IAA’s A-VDGS Project as it sees them (Q)

7.4.8.1. General

1. "Risk management" is intended to help in locating weak links, risk factors

and potential failures that may cause significant delays in schedules, cost

overruns and the contents downgrade of the project.

2. Throughout the project, a "Risk management" process shall be realized under

the full responsibility of the Bidder and according to the specifications,

meanings and contents detailed in this chapter.

3. Risk management shall include at least activities of: identification,

assessment, mitigation plan and performance tracking and repeat

measurement.





4. The Bidder’s A-VDGS Project Manager and IAA’s Project Manager shall

agree on all issues that require further clarification concerning the

methodology by which the risk management is to be realized.

7.4.8.2. Risk Management Methodology

1. The process of the risk management, as mentioned above, shall be based

mainly on a designated "risks forum" that shall be established to execute the

mission.

2. The risks forum shall include at least the following roles: the A-VDGS Project

Manager, the system engineer, the development manager, the tests manager,

IAA’s Project Manager and IAA QA Manager.

3. The Bidder’s A-VDGS Project Manager shall head the risk forum.

4. The risk forum shall convene each month in arrangement between the A-

VDGS Project Manager and IAA’s Project Manager.

5. Meeting minutes shall be written under the responsibility of the Bidder's

project manager.

6. The Bidder shall be responsible for maintaining a chart of detailed risks that

shall be updated continuously and on a timely manner that shall ensure the

risks mitigation or elimination. The structure of the chart shall be as detailed

in clause 7.4.8.3 below. The up-to-date chart shall be prepared and published,

each month, within 2 working days from day of the risk forum meeting.

7. The project risks and the mitigation plan shall be presented to the project

steering committee by the Bidder’s project manager.

7.4.8.3. Structure of the Risk Chart

1. The Risk chart shall include the following fields:

a. Risk Identification factors – risk identification number, type,

description, initiator, identification date.

b. Risk analysis factors – impacted areas/key success factors, risk

materialized date (the date in which the risk become real if not

addressed or mitigated), Severity, Probability, risk rank(*)

c. Risk Mitigation Plan – risk owner, mitigation plan, planned due date

(for mitigation), revised and actual due dates, and status report.