Availability Demonstration Plan

Suvarnabhumi Airport Rail Link and City Air Terminal
Availability Demonstration Plan
SYSTEM ASSURANCE
Submission No. EIF/0032
Prepared by : Reviewed by : Released by :
Tittelbach Maatsch Rprich Name
I MO TK ED OSS I MO TK ARL I MO TK ARL Department
11-Mar-2009 11-Mar-2009
Date
Signature
Airport Rail Link Consortium 4-Mar-2009 ARL and CAT Contract (EIF=!$TEA+AG&AQB_0032_A Copyright Siemens Limited 2009. All Rights Reserved.
Availability Demonstration Plan System Assurance Submission No. EIF/0032
1 of 18
Availability Demonstration Plan_A.doc
Overview of Changes
Version A
Issue 4-Mar-2009
Changed Chapters All
Reason for Change New issue
2 of 18
Table of Contents
1 1.1 1.2 1.3 1.4 2 2.1 2.1.1 2.1.2 2.1.3 2.2 2.2.1 2.2.2 2.2.3 2.3 2.3.1 2.3.2 2.3.3 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 General .............................................................................................................................4 Purpose ...........................................................................................................................4 Scope ..............................................................................................................................4 Applicable Documents ....................................................................................................4 Abbreviations...................................................................................................................4 System Characteristics...................................................................................................5 Availability .......................................................................................................................5 Availability Objectives ...................................................................................................5 Availability Parameter ...................................................................................................5 Demonstration of APDP ..................................................................................................6 Reliability .........................................................................................................................7 Reliability Objectives .....................................................................................................7 Reliability Parameter .....................................................................................................7 Demonstration of MTBSAF ...........................................................................................8 Maintainability..................................................................................................................9 Maintainability Objectives .............................................................................................9 Maintainability Parameter .............................................................................................9 Demonstration of MTTR............................................................................................. 11 Availability Demonstration Period.............................................................................. 12 Failure Recognition Board............................................................................................ 13 Relevant roles .............................................................................................................. 13 Failures during Demonstration Period.......................................................................... 14 Data Recording ............................................................................................................ 15 Schedule of the Availability Demonstration.................................................................. 15 Availability Demonstration Process.............................................................................. 16 Documentation of Availability Demonstration .............................................................. 18
3 of 18
1 General
1.1 Purpose
This Availability Demonstration Plan shall define the availability demonstration activities of the Consortium to demonstrate that the contractual requirements for reliability, maintainability and availability will be met for the ARL and CAT System. The main objectives of the Availability Demonstration Plan are: to define the responsibility for the reliability-, maintainability- and availability demonstration activities to describe the specific tasks to be performed for reliability-, maintainability- and availability demonstration to schedule the planned reliability-, maintainability- and availability demonstration activities
1.2 Scope
This Availability Demonstration Plan describes the reliability-, maintainability- and availability demonstration activities that will be carried out by the Consortium according to the Contract, and based on the System Assurance Plan /SAP/. This plan defines the objective and the scope of the system assurance activities that will be undertaken to demonstrate the reliability, maintainability and availability of the ARL and CAT system. Aspects of reliability are shown in chapter 2.2. Aspects of maintainability are shown in chapter 2.3. Aspects of availability are shown in chapter 2.1.
1.3 Applicable Documents

/ADP/ /ADR/ /SAP/ /V6P1/ /MTTR/ Availability Demonstration Procedure; EIF/0034 Availability Demonstration Report; EIF/0033 System Assurance Plan; OPM/0014 Contract, Volume 6: Particular Specification, Part 1: General MTTR Description; EIF/0030
1.4 Abbreviations
ARL CAT DP E&M
Airport Rail Link Consortium 4-Mar-2009 ARL and CAT Contract (EIF=!$TEA+AG&AQB_0032_A
Airport Rail Link City Air Terminal Demonstration Period Electrical and Mechanical
Availability Demonstration Plan System Assurance Submission No. EIF/0032 4 of 18
Copyright Siemens Limited 2009. All Rights Reserved.
Suvarnabhumi Airport Rail Link and City Air Terminal FRB MTBSAF MTTR MTTRep RDT SAP Failure Recognition Board Mean Time Between Service Affecting Failure Mean Time To Restore Mean Time To Repair Reliability Demonstration Testing System Assurance Plan
Availability Stage
The 4 Availability stages to demonstrate the system availability, contain either 3 or 4 Demonstration Periods; will also named stage within the document Period for demonstration of system availability during stages 1 to 4 of requested availability demonstration Scheduled train run between a start and a terminal (no round trip) station for passenger transport Sum of all operating hours (passenger operation) of the overall transportation system performed within a Demonstration Period according to the actual time table Trains that are unable to move and obviate scheduled passenger operation
Demonstration Period Trip Operational Time
Stalled trains
2 System Characteristics
2.1 Availability
2.1.1 Availability Objectives
Based on /V6P1/ the following parameter will be demonstrated during the Availability Demonstration: Mean Time between Service Affecting Failures MTBSAF (/V6P1/, chapter 2.3.7 (1)) (in fact this is a reliability requirement and will be handled in chapter 2.2) Availability Performance (/V6P1/, chapter 2.3.7 (2))
2.1.2 Availability Parameter

The availability performance to be demonstrated for the defined Demonstration Periods (as summarized in Table 1) during Availability Demonstration is defined as:
APDP =
TST;DP TM;DP TST;DP

Availability Performance as required for Demonstration Period Trips missed during Demonstration Period Trips started in time during Demonstration Period
Availability Demonstration Plan 4-Mar-2009 System Assurance Submission No. EIF/0032
with:
APDP TM;DP TST;DP
Airport Rail Link Consortium
5 of 18
ARL and CAT Contract (EIF=!$TEA+AG&AQB_0032_A
Suvarnabhumi Airport Rail Link and City Air Terminal A started trip will be considered as missed trip if it exceeds the limit of arrival time as per Table 1 defined for the respective Demonstration Period at the terminal station because of a technical failure according to chapter 3.3. Delays caused by stalled trains will not considered as missed trip. Availability Performance will be calculated for each Demonstration Period and documented in the respective Demonstration Period Availability Note. A trip has to be considered as started if boarding of passengers for a respective scheduled train run has been started. A started trip will be considered as missed trip if it exceeds the limit of arrival time as per Table 1 defined for the respective Demonstration Period at the terminal station because of a technical failure according to chapter 3.3. The operational time of a Demonstration Period is considered as sum of all operating hours of passenger transportation performed within the Demonstration Period according to the actual time table.
2.1.3 Demonstration of APDP

The Availability Demonstration consist of 4 Stages each with 4 Demonstration Periods. The Stages 1 to 3 are progressive stages of availability growth in order to reach the highest requirements defined for Stage 4 which has the highest requirements. Therefore the requested Availability Performance in stages 1 to 3 is only are guide to finally reach the rarget availability performance in Stage 4. The Consortium will define the start of each Stage. During the execution of stage based on the daily evaluations by a Failure Recognition Board (s. chapter 3.1) all Demonstration Periods will be closed. The respective Stage will be closed when all Demonstration Periods are run. An overview of the defined Demonstration Periods to demonstrate the availability performance is given in the table below:
Guidance Criteria ID Duration of DP Availability performance 98% 98% 98% 98% 99% 99% 99% 99% 99,5% 99,5% 99,5% 99,5% Punctuality criteria (trips completed within ) +/- 15 min +/- 10 min +/- 5 min +/- 2 min ARLC +/- 15 min +/- 10 min +/- 5 min +/- 2 min ARLC +/- 15 min +/- 10 min +/- 5 min +/- 2 min
Availability Demonstration Plan 4-Mar-2009 ARL and CAT Contract (EIF=!$TEA+AG&AQB_0032_A System Assurance Submission No. EIF/0032
Responsibility ARLC
Availability Stage 1 DP1-1 DP1-2 DP1-3 DP1-4 DP2-1 DP2-2 DP2-3 DP2-4 DP3-1 DP3-2 DP3-3 DP3-4 4 consecutive days 4 consecutive days 3 consecutive days 3 consecutive days 4 consecutive days 4 consecutive days 3 consecutive days 3 consecutive days 4 consecutive days 4 consecutive days 5 consecutive days 5 consecutive days
Availability Stage 2
Availability Stage 3
6 of 18
Guidance Criteria ID Duration of DP Availability performance 99,5% 99,5% 99% of of of 1 per month 1 per period 2 in the first 3 month Punctuality criteria (trips completed within ) +/- 5 min +/- 2 min +/- 1 min Failure of train to be ready for revenue operation Closure of any station for passengers Service disruption for more than one hour Maintainer Operator Operator Responsibility ARLC
Availability Stage 4 DP4-1 DP4-2 DP4-3 DP4-4a DP4-4b DP4-4c 10 consecutive days 10 consecutive days 4 consecutive days First 9 month revenue service First 9 month revenue service First 9 month revenue service
Table 1: Overview Demonstration Periods The demonstration of Demonstration Period DP4-4a is n the responsibility the maintenance organization and is not within the scope of the Consortium. Therefore the maintenance organization has to demonstrate this figure. The demonstration of Demonstration Periods DP4-4b and DP4-4c are in the responsibility of the operator and not within the scope of the Consortium. Therefore the operator has to demonstrate these figures.
2.2 Reliability
2.2.1 Reliability Objectives
The relevant requirements for the overall system reliability demonstration are defined in /V6P1/, chapters 2.3.4 (1), 2.3.4 (2), 2.3.6 (1) and 2.3.7 (1).
2.2.2 Reliability Parameter

The Mean Time between Service Affecting Failures MTBSAF is defined as time between trips missed during Demonstration Period. It is defined as:
MTBSAF =
t
1
TM
Mean Time between Service Affecting Failures Operational time of Demonstration Period n Demonstration Periods from DP1-1 to DP4-3 (as summarized in Table 1) Trips missed during all Demonstration Periods
with:
MTBSAF tn n TM
A started trip will be considered as missed trip if it exceeds the limit of arrival time as per Table 1
Airport Rail Link Consortium 4-Mar-2009 ARL and CAT Contract (EIF=!$TEA+AG&AQB_0032_A Availability Demonstration Plan System Assurance Submission No. EIF/0032 7 of 18
Suvarnabhumi Airport Rail Link and City Air Terminal defined for the respective Demonstration Period at the terminal station because of a random technical failure according to chapter 3.3. Delays caused by stalled trains will not considered as missed trip. The operational time of a Demonstration Period is considered as sum of all operating hours of passenger transportation performed within the Demonstration Period according to the actual time table. The MTBSAF will be calculated for the Availability Demonstration and documented in the respective Availability Demonstration Report.
2.2.3 Demonstration of MTBSAF

The MTBSAF will be demonstrated during the whole Availability Demonstration. The general approach to demonstrate the MTBSAF is: 1. Identification of all service affecting failures occurring during a Demonstration Period (including failures in the depot area for demonstration of SIG depot reliability requirements) 2. Identification of cause for the failure (s. chapter 3.3); allocation to the relevant subsystem if applicable 3. Documentation of relevant service affecting failures for Demonstration Period; Availability Stage and whole Availability Demonstration in the respective documents (s. chapters 3.6 and 3.7) 4. Calculation of the MTBSAF for the overall system during whole Availability Demonstration in the Availability Demonstration Report 5. Calculation of the MTBSAF for the subsystems as defined in their Reliability Demonstration Test Plan based on the documented relevant service affecting failures during the whole Availability Demonstration in the respective Reliability Demonstration Test Reports of the subsystems. This procedure is shown in Figure 1 below.
Figure 1: Demonstration of MTBSAF

Suvarnabhumi Airport Rail Link and City Air Terminal Generally it has to be noted that the demonstrated MTBSAF can not be used as evidence for MTBF predicted by the subsystems. On the other hand it can be assumed that the predicted MTBF of the subsystems are reached when the required availability can be demonstrated during the availability demonstration as defined in chapter 2.1.
2.3 Maintainability
2.3.1 Maintainability Objectives
The relevant MTTR requirements for the overall system are defined in /V6P1/, chapters 2.3.4 to 2.3.6. The relevant qualitative requirements for the overall system are defined in /V6P1/, chapter 2.3.5: (3) The following MTTR shall be achieved (a) 15 minutes for train-borne equipment (b) 15 minutes for train detection equipment (c) 30 minutes for other trackside equipment (d) 15 minutes for equipment located in equipment rooms or control rooms
2.3.2 Maintainability Parameter

A description of the MTTR is given in /MTTR/. The general approach and the detailed approach regarding MTTR for the overall system as defined in this document is repeated in the following chapters. The detailed approach for MTTRep per each subsystem is described in the respective test/demonstration document of the subsystems.
2.3.2.1 General Approach

As summarized in /MTTR/ requirements are defined regarding maintainability and restoring service of the transit system. These requirements have to be generally divided into requirements on the overall system level and requirements, which are relevant for the subsystems. For the subsystems the requirements are mainly maintenance centered and corresponding to the technical characteristics of the systems. They are additionally defined in particular specifications for the several subsystem. On the overall system level the requirements are revenue service centered and corresponding to the equipment that is required to perform revenue service after technical integration of the subsystems. An overview of this general interpretation is given in Figure 2 below.
9 of 18
Figure 2: General Approach
2.3.2.2 Contractual Requirements on the Overall System level

The MTTR that is requested in chapter 2.3.5 of /V6P1/ is a performance parameter of maintenance service provider and the operator. In order to optimize operational impacts of technical failures it specifies the time, which is needed to restore the operation of trains. There will be generally two possible ways to restore revenue service: rectification of a failure, so that a high level of revenue service is possible (according to chapter 4 of /MTTR/) or replacement of a failed element with a functioning one, as defined for the sub-systems
In that meaning the MTTR on the overall system level will be described as Mean Time To Restore with the objective to resume revenue service in the quickest possible way. For that also switching to redundant equipment will be considered as restore activity. The MTTR will be considered for the failures as mentioned in clause (2) of chapter 2.3.5 of /V6P1/ up to this point, where a defined level of operation is restored. The MTTR for the several groups of equipment, which are defined in clause (3) of 2.3.5 of /V6P1/, will be calculated as follows:
MTTRGE =
i =1
N i MTTRi
n i
i =1
Ni
10 of 18
Suvarnabhumi Airport Rail Link and City Air Terminal with: N E GE Number of elements of the equipment E in the system Special equipment that belongs to the group of equipment as defined in clause (3): train-borne equipment; train detection equipment; other trackside equipment; and equipment located in equipment rooms or control rooms. Mean Time To Restore the revenue service in case of failures of equipment E Failure rate of the equipment Number of different groups of equipment (4)
MTTR n
This calculation will be performed for each of the defined group of equipment defined in clause (3) of 2.3.5 of /V6P1/. The Mean Time To Restore measurement will include on site diagnostics and restore activity up to the point that the system is restored to a high level of revenue service.
2.3.3 Demonstration of MTTR

The demonstration of the MTTR for the groups of equipment as referenced in chapter 2.3.1 will be done as part of the Availability Demonstration on the overall system level. The general approach to demonstrate the MTTR of the equipment groups is: 1. Prediction of MTTR of all equipment of the subsystem based on theoretical estimations, field experiences and references; 2. Calculation of MTTR for the defined groups of equipment (train-borne equipment; train detection equipment; other trackside equipment; equipment in rooms) 3. Selection of an adequate number of equipment to be practically demonstrated within factory acceptance tests, installation tests or commissioning tests; definition of these equipment in the Maintainability Demonstration Test Plan of the subsystem; 4. Agreement of the selected equipment by approval of the Maintainability Demonstration Test Plan of the subsystem; 5. Perform maintainability demonstration as defined in the respective approved documents of the subsystem (e.g. Maintenance Demonstration Test Plan of the subsystem); 6. Demonstration of required MTTR for defined groups of equipment within the Availability Demonstration Report based on demonstration reports of the subsystems and calculation as defined in chapter 2.3.2.2.
11 of 18
Suvarnabhumi Airport Rail Link and City Air Terminal This procedure is shown in Figure 3 below.
Figure 3: Demonstration of MTTR
3 Availability Demonstration Period

An outline of the organization of the Availability Demonstration Period is given in this chapter. Details regarding Failure Recognition Board, Relevant roles, Failures during Demonstration Period, Data Recording, Schedule of the Availability Demonstration, Availability Demonstration Process and Documentation of Availability Demonstration
will be described in detail in a separate Availability Demonstration Procedure /ADP/.
12 of 18
3.1 Failure Recognition Board

For the evaluation of the system performance of all Availability Stages a joint team of representatives from the Employer, the Consortium, the Operator and the Maintainer has to be nominated. The Failure Recognition Board consist of two regular representative of each party mentioned above. The special roles of the Chair of the Failure Recognition Board, the Consortium Availability Demonstration Manager and the Operator Availability Demonstration Manager has to be appointed. After completion of Demonstration Periods DP1-1 to DP4-3 the Consortium will prepare its Availability Demonstration Report and withdraw from the Failure Recognition Board. The chair of the Failure Recognition Board will be appointed by the Consortium. The Failure Recognition Board will meet on every day of Availability Demonstration (during Demonstration Periods DP1-1 to DP4-3, see Table 1 and chapter 3.5) to evaluate the causes of delays of trips that are measured during the daily operation of a Demonstration Period. In case of an unclear allocation of a situation caused a relevant delay the Failure Recognition Board has to perform an adequate investigation of the situation to clarify the cause of the delay. For that reason appropriate experts may invited to the meeting to support the process. All evidences has to be considered as attachment to the Daily Availability Note (see chapter 3.7). When the availability for the respective Demonstration Period is calculated by the Consortium the Failure Recognition Board will release the Demonstration Period Availability Note for this Demonstration Period by one signature of each party.
3.2 Relevant roles

Various roles have to be appointed for a successful performance of the Availability Demonstration. To ensure a smooth running of the demonstration all relevant persons should be nominated at least one month before start of the demonstration. The following roles have to be filled out:
Consortium Availability Demonstration Manager

The Consortium Availability Demonstration Manager has to be appointed by the Consortium. He has to define the demonstration conditions (e.g. needed O&M staff and trains) declare the Consortiums readiness for performance of the next Demonstration Period, calculate the daily availability calculate the availability of the Demonstration Period prepare relevant Consortium documents.
Operator Availability Demonstration Manager

The Operator Availability Demonstration Manager has to be appointed by the Operator (during Trial Run and revenue operation during availability demonstration). He has to Implement the demonstration conditions as defined by the Consortium Availability Demonstration Manager Document the starting times of scheduled trips Document the arrival time at the terminal stations of scheduled trips. prepare the Daily Operation Report
Availability Demonstration Plan 4-Mar-2009 ARL and CAT Contract (EIF=!$TEA+AG&AQB_0032_A System Assurance Submission No. EIF/0032 13 of 18
Chair of the Failure Recognition Board

The Chair of the Failure Recognition Board will be appointed by the Consortium and has to Lead the meetings of the Failure Recognition Board prepare the minutes of the meetings
Regular Members of the Failure Recognition Board

The Regular Members of the Failure Recognition Board will be appointed by the Employer, the Maintainer and the Operator. They have to Take part to the meetings of the Failure Recognition Board
Drivers
The driver have to prepare driver reports for unexpected events and delays as part of their regular activities.
Maintainer
The maintainer have to prepare maintenance reports as part of their regular activities.
OCC Staff
The OCC staff has to prepare OCC reports for unexpected events and delays as part of their regular activities. All roles will be appointed for the whole Availability Demonstration. All persons as representatives of their party have to be authorized by this party to act as described in this plan.
3.3 Failures during Demonstration Period

All failures identified by the Failure Recognition Board (see chapter 3.1) will be categorized as follows: Random technical failure of E&M equipment Repeated systematic failures Poor Maintenance (e.g. incorrect or not carried out activities) Faulty operation (e.g. by driver or OCC staff) Unexpected passenger behavior (e.g. passenger look the door) Force majeure, third party, external influences (e.g. unexpected weather conditions)
Only random technical failure of E&M equipment that directly cause a relevant delay according to the respective Availability Stage will be considered for calculation of system availability APDP. Failures caused by poor maintenance not according to the submitted maintenance procedures or caused by faulty operation are not considered for calculation of system availability APDP. It is in the responsibility of the maintainer and operator to provide evidence of proper maintenance and operation.
14 of 18
Suvarnabhumi Airport Rail Link and City Air Terminal Repeated systematic failures (installation and design failures) are not considered for calculation of system availability APDP. Force majeure, impact from third party or external influences (extreme weather, animals) or unexpected passenger behavior will be not considered for calculation of system availability APDP.
3.4 Data Recording

There are different kinds of data recording required: Operational data and Technical data. departure time of departed trips during Demonstration Period, arrival time of departed trips during Demonstration Period, point of time of failure relevant for operation, external cause of failure (e.g. passenger, obstacle, staff).
Operational data, e.g. drivers reports, are valid data to document:
These data will be collected and provided by the operator. Technical data are valid data to evaluate causes of delays, e.g. failures of technical equipment, impact of third party or faulty operation. These data will be collected and provided by the operator and the Consortium.
3.5 Schedule of the Availability Demonstration

The general is as follows, a further detailed schedule will be sent later prior to the start of the Availability Demonstration as part of the Availability Demonstration Procedure /ADP/: Day 990: begin of Trial Run; Demonstration Stage 1 shall start within one month after this day. Day 1080: begin of consideration of additional availability criteria as summarized in Table 1 on page 7.
15 of 18
Figure 4: Schedule of the Availability Demonstration The different Demonstration Stages (as listed in Table 1) contains 3 or 4 Demonstration Periods a 3 to 10 days. The length of the stages are in detail (sum of required days per Demonstration Period): Stage 1: Stage 2: Stage 3: Stage 4: 14 days 14 days 18 days 24 days
That means that Availability Demonstration will be performed on 70 days during Trial Run and the early phase of Revenue operation.
3.6 Availability Demonstration Process

The Availability Demonstration Process that will be implemented for each Availability Stage is given in Figure 5 below:
16 of 18
Consortium: Definition of demonstration conditions declaration Ready for next Availability Stage (1-4)
Operator: Implementation of demonstration conditions declaration Ready for Demonstration
Related Document: Demonstration Description for Demonstration Stage
Operator: Start Availability Stage (1-4)
Operator: Start Demonstration Period
Operator: Daily operation
Operator: Counting of start and arrival times of planned trips Failure Recognition Board: Data collection; Assessment of delayed trips; Allocation of responsibility Consortium: Calculation of daily availability based on decisions made by the FRB N Y Consortium: Calculation of availability of DP based on daily availability calculation
Related Document: Daily Operation Report
Related Document: Minutes of meeting
Related Document: Daily Availability Note
All days of DP performed?
Related Document: DP Availability Note
All DP of Demonstration Stage performed? Y
Consortium: Prepare Availability Report for stage based on availability of DP
Related Document: Availability Report for Stage (1-4)
N Y
All Demonstration Stages performed?
Consortium: Prepare Availability Demonstartion Report based on Availability Report for stages
Related Document: Availability Demonstration Report
Failure Recognition Board: Approval of Availability Demonstration Report
Figure 5: Demonstration Process After completion of Demonstration Periods DP1-1 to DP4-3 (as defined in chapter 2.1.3) the Consortium Availability Demonstration Manager will prepare the final Availability Demonstration Report /ADR/.
3.7 Documentation of Availability Demonstration

The top level documents for the Availability Demonstration are requested by the Contract. The first requested document is this Availability Demonstration Plan. The second requested document is the Availability Demonstration Report. The objective of the Availability Demonstration Procedure /ADP/ is to define details regarding organizational aspects of the Availability Demonstration as outlined in this chapter; e.g. details for the below listed second level documents. The objective of the Availability Demonstration Report /ADR/ is to document the successful performance of the Availability Demonstration according to this Availability Demonstration Plan. The Availability Demonstration Report is a necessary input document to the Final System Assurance Report. The second level documents for the Availability Demonstration are shown in Figure 5. These are: Demonstration Description for the Demonstration Stage (1 4) Daily Operation Report Minutes of the meetings of the Failure Recognition Board Daily Availability Note Demonstration Period Availability Note Availability Demonstration Report for Demonstration Stage (1 - 4)
The third level of documentation for the Availability Demonstration are documents to support the process of evaluation of delays; e.g. driver reports, system reports. These documents will be referenced or prepared by request of the Failure Recognition Board and will then be an attachment of the Daily Availability Note.
18 of 18

Availability Demonstration Plan - A

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Availability Demonstration Plan - A

Hochgeladen von

Copyright:

Verfügbare Formate

Suvarnabhumi Airport Rail Link and City Air Terminal

Submission No. EIF/0032

Prepared by : Reviewed by : Released by :

Tittelbach Maatsch Rprich Name

I MO TK ED OSS I MO TK ARL I MO TK ARL Department