EMPLOYER’S REQUIREMENTS - DOTrdotr.gov.ph/images/Foreign_Assisted_Projects/2015/LRT2E...the paid...

EMPLOYER’S REQUIREMENTS

SUPPLEMENTAL INFORMATION LRT Line 2 Extension Project

AUTOMATIC FARE COLLECTION SYSTEM

LRT Line 2 Extension Project

Automatic Fare Collection System

Table of Contents Page Abbreviations 1 1.0 Introduction 1 2.0 System Description 3 2.1 Common Ticketing System 3 2.2 Operating Philosophy 4 2.3 Collation of AFCS Information 6 3.0 Minimum Performance Standard and Specification (MPSS) 6 4.0 Automatic Fare Collection System (AFCS) Requirements 6 5.0 Equipment, Design and Material Requirements 7 5.1 General 7 5.2 Design Requirements 8 5.3 Codes, Standards and Requirements 8 5.4 Special Responsibility of the Contractor 8 5.5 Point of sales/Analyser-Dispenser (Pos/AD) 8 5.6 Automatic Gates (AG) 10 5.7 Ticket Vending Machines (TVM) 13 5.8 Station Computer System (SCS) 16 5.9 Electrical Cabinet 17 6.0 Execution 20 6.1 Factory Testing 20 6.2 Detailed Design 21 6.3 AFC Equipment Installation Works 21 6.4 Facilities Works 24 7.0 AFCS Equipment Installation and Interface Details 24 7.1 General 24 8.0 Verification, Testing and Commissioning 25 8.1 General 25 8.2 Requirement 25 8.3 Installation/Verification Tests (IVT) 25 8.4 Site Acceptance Tests (SAT) 26 8.5 Integrated Tests (IT) 26 8.6 Commissioning File 26 8.7 Safety Certification 27 9.0 Warranty 27 9.1 General 27 9.2 Warranty Period 27 9.3 Responsibility of the Contractor 27 10.0 Spare Parts 27 10.1 General 27 10.2 Warranty Period Spare Parts 27 10.3 Supply of Consumables, Spare Components and Sub-Assemblies 28 10.4 Consumables 28 10.5 Unit Exchange Spares or Spare Components 28 10.6 Capital Spares/Spare Sub-Assemblies 28

Capacity Enhancement of Mass Trackwork, E&M Systems and Transit Systems in Metro Manila, Integration with Existing Systems LRT Line 2 - East (Masinag) Extension Project ________________________________________________________________________________________________________________

10.7 Approval 29 10.8 Delivery 30 11.0 Special Test Equipment, Portable Test Unit, Special Tools 30 11.1 General 30 11.2 Special Test Equipment 30 11.3 Portable Test Units (PTU) 31 11.4 Special Tools 31 12.0 Documentation 31 12.1 General 31 12.2 Documentation Requirements 32 13.0 Training 32 13.1 General 32 13.2 Training Plan 32 14.0 Contactless Tickets (Reference Only) 33 14.1 General 33

Section VI-4 Supplementary Information Page – AFC - 1 December 2015

Abbreviations

AC Alternating Current AD Analyser Dispenser

AFCS Automatic Fare Collection System AG Automatic Gates AS Australian Standard ASTM American Society for Testing and Materials BS British Standard CCS Central Computer System CICC Contactless Integrated Circuit Card CRU Card Reader Unit CSC Customer Service Center CTS Common Ticketing System o Degrees DB Distribution Board DNP Defect Notification Period EN Euro Norm ERB Emergency Release Button FAT Factory Acceptance Tests FOTS Fiber Optic Transmission System FSTP Foil Shielded Twisted Pair GCC General Conditions of Contract Hz Hertz IEC International Electrotechnical Commission IEEE Institute of Electrical and Electronics Engineers IET Institute of Engineering and Technology IP Ingress Protection IPC Illustrated Parts Catalogue ISO International Organization for Standardization IT Integrated Tests IVT Installation/Verification Tests LAN Local Area Network LCD Liquid Crystal Display LRBS Last Ride Bonus System LRT Light Rail Transit LRU Line Replaceable Units MCBF Mean Cycles Between Failures MJT Multi Journey Tickets mm Millimeter MPSS Minimum Performance Standard and Specification MRT Mass Rail Transit MTBF Mean Time Between Failures MTTR Mean Time To Repair NZS New Zealand Standard O&M Operation and Maintenance % Percent PAB Passenger Assistance Booth PCB Process Control Board



PCC Particular Conditions of Contract PEC Philippine Electrical Code Pos Point of Sales PPSP Particular Performance, Specification and Parameters PTU Portable Test Unit PVC Polyvinyl Chloride RCCB Residual Current Circuit Breaker RLF Repeat Last Function RTU Remote Terminal Unit SAT Site Acceptance Tests SCS Station Computer System SJT Single Journey Ticket SOW Scope of Works sq Squared SS Singapore Standard SVT Stored Value Ticket T&CP Testing and Commissioning Plan TOC Take Over Certificate TVM Ticket Vending Machine UPS Uninterruptable Power Supply V Volts VDU Video Display Unit XLPE Cross-linked Polyethylene



1.0 Introduction This Particular Performance, Specifications and Parameters (PPSP) defines the Employer’s Requirements for the detailed design, manufacturing, factory testing, delivery, installation, software/hardware upgrade, site testing, commissioning, warranty, supply of spare parts, consumables and sub-assemblies, special test equipment, special tools and documentation of the additional equipment for the Automated Fare Collection System (AFCS) of LRT Line 2 East Extension Project, including training of Employer’s personnel, wherever required.

The requirements under this Specification shall be read in conjunction with the Employer’s General Specifications and Requirements, General Conditions of Contract (GCC) and Particular Conditions of Contract (PCC).

All works under this section of “Employer’s Requirements” shall be carried out in full accordance with the governing codes and regulations which are made part of these specifications.

2.0 System Description

2.1 Common Ticketing System

An efficiently procured contactless Automatic Fare Collection (AFC) System will bring important benefits to the daily passengers using the light railway, to the authorities operating those lines and if developed efficiently and effectively also to the wider public.

The AFC System shall be installed on the newly constructed LRT Line 2 Extension as a part of “Common Ticketing System” (CTS). The AFC System will ensure seamless interconnection for travelers and will remove the current inconvenience of the need to buy individual tickets for individual lines. This will have a positive impact on the daily passenger flows using the LRT network.

The AFC System will allow the operating authorities to develop a service offering better needed facilities for the passengers, this will include the convenience of fare-charging arrangements, fare structures & fare policies. Like the AFC systems in Hong Kong, Taiwan, London, the Netherlands, Japan and other countries have shown, a well-designed AFC system improves customer satisfaction through various ways.

The AFC System will be developed and procured in line with current international best practice. It can facilitate the capabilities to service other transport modes such as buses, taxi cabs, etc., and may also serve as an electronic micropayment solution in convenience stores, or as an identifier for loyalty schemes, facility access and location based services.

Penalties/fare adjustments charged to violators shall be implemented as follows:

• Underpayment; • Overtime/Excess time; • Entry/exit time in same station; • Vandalism; and • Fraud/blacklist.



Passenger stations are permanently staffed and have separate paid and unpaid areas for the purpose of proof-of-payment enforcement. Appropriately positioned Automatic Gates (AG) physically separate the passenger in the paid and unpaid areas. A passenger may enter or exit the paid area only through the touch of a ticket on the card reader of a gate unit. The ticket will be encoded with fare information which will be read automatically when the passenger enters or exits the paid area.

2.2 Operating Philosophy

2.2.1 Single Journey Tickets (SJT)

The valid Single Journey tickets shall be purchased from either a Ticket Vending Machine (TVM) or from the staff-operated Ticket Booth.

A valid Single Journey Ticket (SJT) shall be encoded with a fare value equal to or more than the value of the journey and the SJT must enter the paid area.

To enter the paid area of any station the single journey ticket shall be presented to the Card Reader Unit (CRU) situated at the AG. On successful reading and validation of the ticket the AG shall automatically release to allow the passenger to enter the paid area.

If a problem occurs whereby the SJT cannot be read by the CRU the passenger shall be required to attend the Ticket Booth for customer assistance in getting the ticket revalidated or replaced.

When a passenger exits the paid area, the SJT shall again be presented to the CRU for reading and validation, once the CRU has validated the valid ticket the AG shall automatically release to allow the passenger to exist the paid area and the SJT will be captured.

Valid SJTs shall also be subject to a validity time period whereby the journey must be completed with a set period of time and the ticket surrendered to the AG CRU. If the ticket is not presented to the AG CRU within the set period of time the passenger must attend the Passenger Assistance Booth (PAB) for revalidation of the ticket upon payment of the appropriate penalty.

All validation of tickets and time monitoring of tickets shall be carried out via the AFCS Central Computer System (CCS) and the Station Computer System (SCS).

If the encoded fare value of the SJT is less than the appropriate value of the journey completed, the ticket shall be rejected by the CRU and the AG shall not release. In this case the passenger will then be required to attend the PAB for payment of the additional fee and re-validation of the ticket. The passenger shall then represent the card to an AG CRU to exit and upon successful reading of the ticket the ticket shall be captured by the CRU and the AG shall release allowing the passenger to exit the paid area.

2.2.2 Multi Journey Tickets (MJT)

For Multi Journey Tickets (MJT), a valid Stored Value Ticket (SVT) shall be applied and valid SVTs shall be encoded with a maximum fare value of P10,000.00 (adjustable) which



will allow multiple entries and exits of stations but the minimum value must be equal to or more than the value of the journey completed.

A valid SVT shall allow a passenger to enter a paid area of a station only when the value stored on the SVT is greater than or equal to the minimum fare set at the entry gate.

The SVT shall only be allowed exit when the remaining value on the SVT is greater than or equal to the price of an actual journey taken.

The principle of operation for a SVT shall be the same as a SJT whereby the passenger who wishes to enter the paid area of a station shall present their SVT to the CRU at the AG and on successful reading and validation of the ticket the AG shall automatically release to allow the passenger to enter the paid area.

If a problem occurs whereby the SVT cannot be read by the CRU the passenger shall be required to attend the Ticket Booth for customer assistance in getting the ticket revalidated or replaced.

When a passenger exits the paid area, the SVT shall again be presented to the CRU for reading and validation, once the CRU has validated the valid SVT the AG shall automatically release to allow the passenger to exist the paid area and deduct the fare value from the value stored within the ticket.

Any journey undertaken with a valid SVTs shall also be subject to a validity time period whereby the journey must be completed with a set period of time and the ticket presented to the destination AG CRU. If the SVT is not presented to the destination AG CRU within the set period of time when the passenger present their SVT the AFCS shall automatically adjust the balance of the SVT to compensate the appropriate penalty value. If there is insufficient value on the SVT the passenger must attend the PAB for revalidation of the SVT upon payment of the appropriate fee.

All validation of tickets and time monitoring of tickets shall be carried out via the AFCS Central Computer System (CCS) and the Station Computer System (SCS).

If the encoded fare value of the SVT is less than the appropriate value of the journey completed, the SVT shall be rejected by the CRU and the AG shall not release. In this case the passenger will then be required to attend the PAB for payment of the additional fee and re-validation of the ticket. The passenger shall then represent the card to an AG CRU to exit and upon successful reading of the ticket the AG shall release allowing the passenger to exit the paid area.

SVTs shall be able to have value added at the TVMs which shall be able to facilitate adding value to the SVT with the insertion of cash.

2.2.3 Last Ride Bonus System (LRBS)

The existing Last Ride Bonus System (LRBS) presently in use will be replaced by a Bonus Points System which is to be defined by the Scheme Provider



2.3 Collation of AFCS Information

All Information collated from the AFCS, such as revenue data, ticket sales, gate traffic and gate audit at the passenger stations shall be collected by a

Station Computer System (SCS), and additionally at a Central Computer System (CCS), which is located at the Employer’s Administration Building. A Remote Terminal Unit (RTU) located in the Treasury Room at Central Station provides local production of certain management reports.

Other information collated shall be the maintenance statistics such as TVM status and CRU status will be managed including all alarms.

3.0 Minimum Performance Standard and Specification (MPSS) The Contractor in designing the AFCS shall carryout the design in full accordance with the Minimum Performance Standard and Specifications. (MPSS), as stipulated in the AFC Concession Agreement.

4.0 Automatic Fare Collection System (AFCS) Requirements Whilst the long-term objective of the Employer is to be an active participant in creating a common ticketing system for the existing lines using SVT, the present situation is that existing lines will operate autonomously.

The Employer’s Requirements is for AFCS equipment to be installed at two (2) new stations – Emerald and Masinag. New AFCS equipment shall be fully compatible and shall be seamlessly integrated into the existing Line.

The Contractor in designing the AFCS shall include all equipment required to operate in accordance with the extension project requirements, increased passenger volumes and to interface with existing AFC system.

The Contractor shall ensure that the AFCS equipment and the ticketing system is fully capable of efficiently managing passenger traffic especially during peak hours, and is compatible with both existing Line 2 and Line 2 extension.

The fundamental functions to be performed by the AFCS shall include, but not be limited to the following:

• Ticket sales; • Control of access to the paid area of passenger stations; • Restructuring of operating parameters as required by the Central Computer System

(CCS); • Configuration of AFC equipment as defined by the CCS; • Collection, storage and reporting of patronage figures; • Status monitoring of all TVMs, AGs and CRUs; • Active Network Devices; and • Maintenance of revenue accounting records.



The main components of the AFC system to be supplied and installed under the East Extension project comprise of the following:

• Point of sales/Analyzer Dispenser (POS/AD ) - (situated in Ticket Booth); • Card Reader Units (CRU); • Automatic Gates (AG); • Ticket Vending Machine (TVM); • Station Computer System (SCS) hardware; and • Emergency Staff Gates and Stainless Steel Barriers required to complete gate arrays.

The Contractor shall ensure that all equipment is fully compatible with the newly existing AFC apparatus. Additionally, the Contractor shall also take into consideration the following in the provision of new equipment:

• Communications protocols between the SCS and AFC equipment (CRU, AG, TVM and POS/AD);

• Communications protocols between the SCS and existing CCS Data Server and RTU; • Interface facilities to provide integral operation of existing and new equipment shall be

adequately tested and line operation simulated; • Ticket encoding format is fully compatible with the existing system of LRT Line 1, LRT

Line2 and MRT Line 3; and • All works and equipment required subsequent to the supply of new apparatus not directly

compatible with the existing equipment.

The Contractor shall supply all computer hardware from equipment that is commercially available in the markets of the Philippines.

5.0 Equipment, Design and Material Requirements

5.1 General

The Contractor shall design and supply all equipment for use in tropical climate conditions and shall be suitable for the environment to be encountered without any accelerated deterioration.

All equipment shall be of proven technology with substantiated historical evidence of successful operation in similar climatic and environmental conditions.

Prototypes shall not be allowed.

Unless otherwise specified, input power for equipment shall be 230 VAC, 60Hz, single phase.

The Contractor shall supply all specific or special power supplies as required for reliable operation of their equipment.

The Pos/AD, AG, and TVM shall be supplied with internal battery.



The SCS shall be supplied with an Uninterruptible Power Supply (UPS) capable of supplying power for a period of not less than thirty (30) minutes. In the event of power failure, all on-going transactions and processes under process by the AFCS shall be terminated and all data in all AFCS equipment shall be saved and stored until restoration of power. The SCS and AFCS shall automatically reboot into service as soon as power supply has been resumed.

5.2 Design Requirements

The requirements specified in this Particular Performance, Specification and Parameters (PPSP) are the minimum requirements of design conformance and acceptable functionality. They are not intended to restrict innovation and flexibility within the design process, but set parameters for that process which shall not be contravened where emphasized. The Contractor’s design process shall ensure that all systems, subsystems, assemblies and components are complementary and compatible in form and function. Other design requirements not specifically mentioned in this PPSP but found and deemed necessary by the Contractor for the complete and efficient completion of the project shall be presented and submitted to the Engineer for review and consideration. The minimum design life of the AFCS components shall be ten (10) years.

5.3 Codes, Standards and Requirements

Codes, Standards and Requirements specified in this PPSP shall be interpreted as requirements for compliance. Where any specified codes, standards and / or requirements are in conflict with each other or with this PPSP, the more stringent requirement shall apply unless otherwise reviewed and agreed by the Engineer.

5.4 Special Responsibility of the Contractor

No examination, review and acceptance by the Engineer of the design, drawings and documents submitted by the Contractor, with or without amendment, or any agreement, acceptance or consent given by the Engineer for any equipment or part of the Works, shall absolve the Contractor from any of his obligations under the contract or any liability arising out of the designs, drawings and documents or equipment or part of the Works; this being a “Design and Construct Contract”.

5.5 Point of Sales/Analyzer-Dispenser (Pos/AD)

In order to meet the anticipated patronage stations shall be equipped with Pos/ADs as detailed in Table 5.5.1 – Number of Pos/ADs below.

Table 5.5-1 Number of Pos/ADs Station name No. Pos /ADs

Emerald 4 Masinag 4 TOTAL 8

The Contractor shall supply the Pos/ADs in the form of a console fitted with a dedicated keyboard and liquid crystal display (LCD) display with touch screen for the Agent, and a readers/encoders for contactless tickets.

A cash drawer shall be combined within the systems.



Passenger display units shall be provided to enable the customers to view the status of transactions. The display units shall be in both the English and Tagalog languages.

The display units shall be of the LCD, and shall be readable in low ambient light.

The Pos/AD shall operate in the following modes:

• In Service; • Normal Operation (sales are authorized after agent identification); • Stand-by (system awaiting use with no agent identified); • Out of Service (fault mode or stopped on SCS request); and • Maintenance Mode.

In maintenance mode, technicians shall be able to run diagnostic programs from the console.

Security of operations shall be implemented to ensure that only authorized staffs are allowed to operate the Pos/AD. A maximum of two shifts per accounting hour shall be able to be performed on each Pos/AD.

The time required to issue a ticket shall be less than 0.8 of a second from operator confirmation of the transaction to the completion of encoding. Should a ticket become void during the encoding process due to erroneous operation or mistaken passenger request, the action shall be recorded.

The Pos/AD shall be able to perform repetition of encoding the same ticket type as last issued (Repeat Last Function (RLF).

In the event ticket analysis is required to be performed, the Pos/AD shall be capable of performing the following functions:

• Analyzing the information encoded on the ticket; • Displaying the information read on each field; • Indicate any errors found on the ticket; and • Give the operating Agent the option of re-encoding ticket information if errors are

detected.

The Pos/AD shall be able to upgrade tickets upon analysis, this includes:

• When time of exit exceeds the time of entry plus the maximum journey time or maximum, time in the same station (if entry and exit is made in the same station);

• When over travel is committed by the passenger (excess fare); and • When there is an Entry/Exit mismatch on the ticket.

An analysis transaction shall be performed within 0.8 seconds. This includes terminal processing and communication time. The Pos/AD shall have a Blacklist capacity of at least one hundred thousand (100,000) Fare Media (unique identification numbers of Fare Media / Applications).



The Pos/AD shall be designed to manage all events and faults and shall be capable of updating its daily reports.

The Pos/AD shall automatically report on the number of tickets processed and the total amount of operations on a ‘per ticket’ basis per shift.

In the event of a communications failure between the Pos/AD and the SCS, all transaction data shall be safeguarded for a minimum period of seven (7) days. Upon request, the Pos/AD shall transmit this data to the SCS.

Alarm management and self-diagnostics tests shall be provided.

The Pos/ADs shall be connected to the SCS which shall perform audit, monitoring and control functions.

Data shall be transferred from the Pos/ADs to the SCS on a regular basis including status and audit information, which can be displayed on the SCS. Furthermore, Pos/AD accounting and maintenance data shall be capable of being displayed on the CCS and in printed form.

The Pos/AD to be supplied by the Contractor shall be fully compatible and workable within the present LRT Line 2 AFCS. Similarly, the reader/encoder device of the Pos/AD shall be capable of reading and issuing a tickets with common ticketing rules. The exchange of data between the Pos/AD and SCS shall be of the same encoding format and protocol as the existing system.

5.6 Automatic Gates (AG)

All Automatic Gates (AG) to be provided under the LRT Line 2 Extension Project shall be fully compatible both in function and operation with the existing AGs supplied for the LRT Line 1, LRT Line 2 and MRT Line 3 Common Ticketing System (CTS).

The Contractor shall supply the following AGs:

• 4 Specially for Entry Aisles; • 16 Bi-directional Aisles; and • 4 Specially for Exit Aisles.

The Contractor shall supply all necessary equipment, accessories, fittings, cables, etc., for the complete installation all the AGs.

An itemized directory of the stations are given in Table 5.6.1 – Gate Types, below. The detailed work requirement and quantities of gates is also provided in Clause 7 (AFCS Equipment Installation and Interface Details) of this specification.



Table 5.6-1 Gate Type

STATION NAME

AUTOMATIC GATES NOTE ENT

1 ENT2 REV EXT END1 END2 TOTAL

Emerald 1 1 6 2 1 1 12 Masinag 1 1 10 2 1 1 16 TOTAL 2 2 16 4 2 2 28

To fulfill the requirements of this project, up to six different types of gates shall be employed:

• Entrance Gate (ENT1)

This gate shall comprise of one Housing, one Turnstile, one Reader, and one Main Processor PCB. This type of gate shall not contain a Ticket Receptacle. This gate shall control the passage located to the left of the housing when viewed from the unpaid area.

• Entrance Gate (ENT2)

This gate shall comprise of one Housing and one Reader. This type of gate shall not contain a Turnstile and a Ticket Receptacle. This gate shall indirectly control the passage located to the left of the housing when viewed from the unpaid area.

• Bi-directional Gate (REV)

This type of gate shall consist of one Housing, one Turnstile, one Ticket Receptacle, two Readers, and one Main Processor PCB. This gate shall control the passage right side directly and left side indirectly of the housing when viewed from the unpaid area.

• Exit Gate (EXT)

This type of gate shall consist of one Housing, one Turnstile, one Ticket Receptacle, one Reader, and one Main Processor PCB. This gate shall control the passage located to the right of the housing when viewed from the unpaid area.

• END Gate (END1)

This type of gate shall consist of a Housing, one Turnstile and one Main Processor PCB. The gate shall be used for the end of the gate array and shall control the passage located to the right of the housing when viewed from the unpaid area.

• END Gate (END2)

This type of gate shall consist of only a Housing. No subsystems are required. The gate is used for the end of the gate array or the middle of entry and exit gates.

In accordance with their type, the AGs shall be capable of being operated in the following configurations:

• Controlled entrance, locked exit; • Controlled exit, locked entrance; • Free exit, locked entrance; • Locked entrance, locked exit; and



• Controlled entrance, controlled exit.

The differing configurations indicated above shall be determined by the SCS, which transmits the necessary commands to set the AGs in their preselected mode.

The AG CRU shall be the contactless type conforming to the following Standard:

Standard Number Standards Title

ISO/IEC 14443, Part 3 Identification cards -- Contactless integrated circuit cards -- Proximity cards -- Part 3: Initialization and anti-collision

The above Standard is applicable to Contactless Integrated Circuit Cards CICCs of Type A and of Type B, as described in the following Standard:


ISO/IEC 14443, Part 2 Identification cards -- Contactless integrated circuit cards -- Proximity cards -- Part 2: Radio frequency power and signal interface

ISO/IEC 14443 type A and type B smart card shall be adhered to achieve fast processing (less than 0.4 second) including blacklist checks, or equivalent with similar performances. The gate shall have a Blacklist capacity of at least one hundred thousand (100,000) Fare Media (unique identification numbers of Fare Media/Applications).

The gates shall automatically exchange data with the SCS via a communications link.

In the event of SCS communications link failure the AG shall be able to operate in a “standalone” mode but only if all the parameters are present. The operational data shall be stored for a minimum seven (7) days before SCS collection. The gates shall operate in the last mode transmitted by the SCS.

The Contractor shall ensure that the design of the AG mechanism allows only one person to enter the paid area for each release of the gate.

The AGs shall be designed to process not less than thirty five (35) passengers per minute. The passage width shall not be less than 500mm.

At entry AG tickets shall be read by the CRU for the contained data and be checked for validity. When the ticket is accepted, the gate shall release the Turnstile and the new data shall be recorded on the ticket. Ticket data shall be captured and stored in the gate and transferred upon request to the SCS.

At exit gates, Single Journey Ticket shall be inserted to the ticket slot and checked. When it is valid the exit gate shall be invalidated and stored in the gate housing for subsequent re-use after re-encoding. A receptacle shall be provided to collect the tickets. When the receptacle is near full, the AG shall transmit a corresponding status signal to the SCS. When the receptacle



is full, the AG shall transmit an “out-of-service” status signal. The minimum capacity of the receptacle shall be 3,000 tickets.

The Contractor shall include a luminous indicator on each end of the AGs, which shall provide guidance to passengers. This display shall include clear information inclusive of signs, which indicate “ENTRY” or “NO ENTRY” and “EXIT” or “NO EXIT”. An additional display for passenger information shall be furnished adjacent to the CRU, this display shall display either “TICKET ACCEPTED” or “TICKET REJECTED” in both English and Tagalog languages, together with a numeric indicator showing the remaining value on SVTs.

An audible alarm should be fitted inside the AGs. When front doors or covers have been opened, the audible alarm shall sound unless it has previously been cancelled by use of a key.

The Contractor shall provide a lockable top lid, hinged for good access to the ticket transport and collection unit in order to remove foreign objects and jammed tickets.

Override facilities shall be provided to enable a Station Official to release a selected gate for one operation, to lock all entry gates for preventing station overcrowding and to switch AGs into a “freewheeling” or other free-pass mode for speedy station evacuation in case of emergency. In the event of a fire alarm being raised all AGs shall automatically revert to “freewheeling” or other free-pass mode for an emergency evacuation of the station.

In the event of power failure, passengers inside the paid area shall be able to pass freely through the exit gates.

The AGs shall be designed to manage events and faults, and update its daily report on a regular basis. The AGs shall automatically report upon the number of tickets processed, the number of passages and the fare revenue per ticket type.

The status and report data shall be transmitted to the SCS over the respective communications link.

Alarm management and self-test diagnostics shall be provided. The AGs shall be connected to the SCS and shall update on a regular basis the status and audit information, which can be displayed at the SCS and can be printed via the CCS.

5.7 Ticket Vending Machines (TVM)

TVMs shall be floor/wall-mounted type of which back side faces to Station Staff Office or similar secured area and of which front side faces to open area outside fare control area of Station Concourse.

The following table 5.7.1 – Numbers of TVMs, indicates the number of TVMs that shall be installed in Line2 Extension stations.



Table 5.7-1 Number of TVMs

Station Name No. of TVMs

Emerald 9 Masinag 9 TOTAL 18

All TVMs shall be equivalent both functionally and operationally with the existing TVMs newly supplied for the LRT Line 1, LRT Line 2 and MRT Line 3 and the issued tickets shall follow the Common Ticketing rules.

The TVMs shall operate in the following modes:

• In Service, (sale ticket, add value and check balance); • Stand-by; • Out of Service (fault mode or stopped on SCS request); and • Maintenance Mode.

In maintenance mode, technicians shall be able to run diagnostic programs from the console.

An overhead display shall display “IN SERVICE” and information of irregular operation mode such as “COINS ONLY”, “BANK NOTES ONLY”, “CHECK BALANCE ONLY” and “ADD VALUE ONLY” shall be displayed.

In Service mode, the TVMs shall display the fare selection button, ticket type selection button (single journey and stored fare), and operation type selection button (ticket sales, check balance and add value). The readout shall be selectable in both the English and Tagalog languages.

The TVMs shall accept coins and banknotes. The selection of fares shall be via a touch screen. On selection the TVMs shall issue ticket and change as necessary.

The TVMs shall also be capable of displaying remaining value on the ticket inserted or placed onto the cradle as the check balance operations. The reading balance shall be performed within 0.8 seconds. This includes processing and communication time.

The time required to issue a ticket shall be less than two (2) seconds from the condition of issue being satisfied to the completion of issue of the ticket. Should a ticket become void during the encoding process due to wrong ticket media the media shall be captured and another media shall be issued.

In the event “CHECK BALANCE OF STORED TICKET”, the TVMs shall display the following information on the front display.

• Remaining stored fare value; and • Last Ride Bonus (LRB) point.



TVM shall have a Blacklist capacity of at least one hundred thousand (100,000) Fare Media (unique identification numbers of Fare Media/Applications).

The TVMs shall be designed to manage events and faults, and shall be capable of updating its daily reports. The TVMs shall automatically report on the number of tickets issued and the total amount of sales on a “per ticket price” basis and total amount of add value for stored value tickets.

The TVM shall at least accept as a valid payment method:

• All types of Php 1, 5 and 10 coins in circulation per January 2015, and one additional series of coins if introduced by BSP prior to Termination Date; and

• All types of Php 20, 50 and 100 banknotes in circulation per January 2015, and one additional series of banknotes if introduced by BSP prior to Termination Date.

If the price or fare to be paid by a Passenger is not a whole number in Pesos, the cash change returned to the Passenger may be rounded down to the nearest peso.

Accepted coins shall be stored inside the Coin Receptor to be recycled as the changes. The coins overflowed from Coin Receptor’s storage shall be dropped to the Coin Vaults. When the Coin Receptor is emptied the coins for change shall be supplied from the Change Hoppers.

Two Change Hoppers shall be provided for capacity of total 2000 coins. There are 2 change dispensers with 1000 coins each to supplement each of accepted coin type.

When any Coin Vault is near full, the respective TVM shall send a corresponding status signal to the SCS. When any Coin Vault is full, the respective TVM shall send an “out-of-service” alarm signal to the SCS. The minimum capacity of the Coin Vault shall be 800×2.

Accepted Banknotes shall be stored in lockable Banknote Vault inside the TVMs. When any Banknote Vault is near full, the respective TVM shall send a corresponding status alarm signal to the SCS. When any Banknote Vault is full, the respective TVM shall send an “OUT-OF-SERVICE” alarm signal. The minimum capacity of the Banknote Vault shall be 800.

A Receipt Printer shall be mounted to print customer receipts as required.

Alarm management and self-test diagnostics shall be provided. The TVMs shall be connected to the SCS which shall perform audit, monitoring and control functions. Data shall be transferred from the TVMs to the SCS on a regular basis including status and audit information, which can be displayed on the SCS. In addition, TVM accounting and maintenance data shall be capable of being displayed on the CCS and in printed.

In the event of SCS communications link failure the TVMs shall be able to operate in “standalone” mode if all the parameters are present. The operational data shall be stored for a minimum seven (7) days before SCS collection. The TVMs shall operate in the last mode transmitted by the SCS.



The TVM to be supplied by the Contractor shall be fully compatible and operational within the present LRT Line 2 AFC system. Similarly, the CRU device of the TVMs shall be capable of reading and issuing a ticket with common ticketing rules.

The exchange of data between the TVMs and SCS shall be of the same encoding format and protocol as the existing system.

The Contractor shall supply all equipment, accessories, fittings, cables and shall install all the TVMs.

5.8 Station Computer System (SCS)

The SCS shall be located in the air-conditioned Ticket Booth of the two new stations. Physically and logical access to SCS shall be limited to authorized employees.

The SCS shall be capable of performing multi-tasking operations that shall include but not be limited to the following:

• Poll the Pos/ADs, AGs and TVMs on a regular basis for statistical and revenue data. Arrange this information as appropriate in the database for further management reporting purposes.

• Provide all fault, statistical and accounting reports, and download this information when requested by the CCS.

• Monitor and poll Pos/ADs, AGs and TVMs for faults and alarms, and control switching of this equipment into and out of service.

The Contractor shall design the SCS to be completely compatible and workable with the present LRT Line 2 AFC system. Moreover, the exchange of data between the SCS and the AFCS equipment (Pos/ADs, AGs and TVMs) and between the SCS and CCS shall be of the same encoding format and protocol as the existing system.

The Manila environmental condition shall be considered when the SCS and its housing is designed and manufactured. In particular, the Ingress Protection (IP) rating shall be adequate for the prevention of moisture and dust. The IP ratings shall conform to the following Standards;


IEC 60529 Degrees of protection provided by enclosures (IP Code)

All control panel enclosures shall be protected against the ingress of rodents and other pests.

The Contractor shall provide a mock-up of the proposed SCS hardware is to be made available for approval prior to delivery.

All Local Area Network (LAN) data shall be transmitted via the Fiber Optic Transmission System (FOTS), which forms the backbone of the communications network.



All Telecommunications Works pertaining to the design of the Network, LAN and interfacing systems shall be designed by the Telecommunications Contractor.

Network interruption shall lead to automatic re-routing of network traffic without any data loss. The SCS service interruptions shall lead to either automated (e.g. reboot) or manual repair actions, also here without any data loss. The SCS shall function independent from CCS for at least seven (7) days.

Load increase is caused by station extensions. Scalability shall be in line with PTO/Line ten (10) years estimated growth.

The AFC Contractor shall interface and co-ordinate with all parties involved ensuring all information inclusive of equipment specifications are provided where necessary.

The Contractor shall ensure that no interruption in the revenue operation of the LRT Line 2 shall result during the installation, testing and commissioning of the SCS software and hardware

5.9 Electrical Cabinet

For the two new stations, Electrical Cabinet shall be installed in the PAB of each gate array. Additionally, there shall also be an Electrical Cabinet in the Ticket Booth for the power supply for the TVM, Pos/AD and SCS power.

Each electrical housing shall consist of the following:

• Isolation circuit breaker for isolating all outgoing supplies; • Individual circuit breakers to provide power supplies to the AFC equipment (Pos/AD,

AG, TVM and SCS). Circuit breakers and other devices shall fully comply with the following Standards and Code of Practice:


AS/NZS 3190 Approval and test specification - Residual current devices (current-operated earth-leakage devices)

BS IEC 1008-2-2

Specification for residual current operated circuit-breakers with integral overcurrent protection for household and similar uses (RCCBs). Applicability of the general rules to RCCBs functionally dependent on line voltage

BS EN 61008-1:2012+A2:2013

Residual current operated circuit-breakers without integral overcurrent protection for household and similar uses (RCCBs). General rules

SS 97 Residual current operated circuit-breaker without integral overcurrent protection for household and similar uses (RCCBs) - General rules

Philippine Electrical Codes (Current Edition)



• Interconnection terminal block with spare capacity; • Spare ways; • Visual check by indicator lights; and • An Emergency Release Button (ERB) is mounted in front of the Electrical Cabinet. The

gates shall be in freewheel mode when the ERB is activated. Operation of anyone of the ERBs shall set all AGs on the station into emergency exit (freewheel) mode.

The Contractor shall supply power and earthing cable including cable containment from the Electrical Room to each of the Electrical Cabinets installed inside the PABs and Ticket Booths. The Contractor shall pick up the Main AFC Power Supply at the Electrical Room of each station. The AFC Contractor shall interface and coordinate with all parties involved ensuring all information inclusive of equipment specifications are provided where necessary.

5.10 Installation Materials

• General

The Contractor shall supply and install new and additional cables, raceways and miscellaneous materials for the AFC equipment to satisfy the requirements of the AFC.

• Cables

Cables shall be multi-core, cooper conductor, insulated, non-shielded, non- armoured and equipped with outer jacket. The complete cable shall be pest resistant, water-tight and flame retardant, meeting the requirements of IEEE 383 Flame test or equivalent, and shall be suitable for installation in conduits and troughs.

The conductors shall be made of annealed high-conductivity copper and shall be of stranded construction. The wire before stranding shall meet the requirements of the following Standard or equivalent:


ASTM B3 Standard Specification for Soft or Annealed Copper Wire

Conductor stranding shall meet the requirements of the following Standard or equivalent:


ASTM B8 Standard Specification for Concentric-Lay-Stranded Copper Conductors, Hard, Medium-Hard, or Soft

All cable insulation shall be of Cross-linked Polyethylene (XLPE). Polyvinyl Chloride (PVC) insulation shall not be permitted under any circumstances.

The control cables shall be shielded and insulated rating for 600VAC.

https://www.google.com.ph/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0CCYQFjAC&url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FCross-linked_polyethylene&ei=MoxZVaDCJ8mVuASMkoC4Cw&usg=AFQjCNGx2QaQAsuWhZUGq9raEKWQZSHArQ



Accessories shall include cable terminations which shall be capable of withstanding temperature and voltage levels afforded by the cable. Terminations shall be complete with suitable wire lugs.

Category 5 (CAT 5) Foil Shielded Twisted Pair (FSTP) cable to be supplied and shall be in accordance to the following Standard:


ISO/IEC 11801 Information technology – Generic cabling for customer premises

The typical cable sizes are detailed in Table 5.10.1 – Cable Sizes, below:

Table 5.10-1 Cable Size

Designation From To Wire

Diameter (sq mm)

Power Electrical Cabinet Gate 4 Power Electrical Cabinet Pos/AD, SCS 2.5 Power Gate Gate 2.5

Grounding Electrical Cabinet All equipment (must not be cut) 6

Data SCS Pos/AD 0.75 Data SCS Gate 0.75 Data Gate Gate 0.75 data SCS Telecom System FSTP

Power Electrical Room

Distribution Panel Board

Electrical Cabinet 6

• Raceways

The Contractor shall use Class 3 galvanized rigid steel conduit and accessories sized in accordance with the requirements of the latest edition of Philippine Electrical Code (PEC) and the following Standards.


BS 4568-1 Specification for Steel Conduit and Fittings with metric thread if ISO form for Electrical Installations – Part 1: Steel Conduit, Bends and Couplers.

BS 4568-2 Specification for Steel Conduit and Fittings with metric thread if ISO form for Electrical Installations – Part 2: Fittings and Components.

For fittings and accessories, the Conductor shall:

Provide separate watertight hub fittings with a gasket, separate nylon insulated throat and a case hardened lockout;

Provide bushings of nylon-insulated metallic and grounding type;



Provide conduit straps, clamps and clamp backs made of galvanized malleable iron; Provide rigid steel conduit of 50mm diameter for cables to be used in Gate-to-Gate power

and data interconnections; and Provide rigid steel conduit and underfloor cable trunking for power cables from Electrical

Distribution Panel Board located at the Electrical Room to Electrical Cabinets. The raceways for the power and data cables from the Electrical Distribution Board (DB) to the Electrical Cabinets shall be provided by the AFCS Contractor.

The AFCS Contractor shall interface and co-ordinate with all parties involved ensuring all information inclusive of equipment specifications are provided where necessary.

• Miscellaneous Materials

The Contractor shall supply and install miscellaneous materials, as required to install and support AFC equipment and cables. These materials shall include those needed to level AFC equipment levelling and fixing cables, cable supports, raceways, seal floors and wall openings and the like.

The Contractor shall ensure that the design of support and hardware items is free from rough edges, burrs, and sharp corners.

Where used, metallic cleats shall be provided with rubber strip inserts to prevent damage to the cable.

The sealing materials to be supplied for sealing wall penetrations shall be of fire proof material and when sealed the opening shall be weatherproof.

A sample of all installation materials as well as materials shall be submitted by the Contractor for the Engineer’s review and acceptance. All samples shall be submitted prior to any installation by the Contractor.

6.0 Execution

6.1 Factory Testing

Factory Acceptance Tests (FAT) shall be carried out at the manufacturer’s facilities to be witnessed the Engineer’s and Employer’s Representatives to verify that the AFC equipment complies with contract requirements. In general, FAT shall be arranged as recommended in applicable industry standard.

Any materials or completed equipment not meeting the test requirements under this Specification shall be rejected, and where earlier consignments of similar materials or completed equipment have already been separately tested and released for dispatch, further proof on such consignments may be called for at the request of the Engineer/Employer.

The Engineer/Employer reserves the right to call for such additional test as may be necessary to prove compliance with the Specifications.



The reliability and availability of the AFC system component shall meet or exceed the following requirements as detailed in Table 6.1.1 – Reliability and Availability, below.

Table 6.1-1 Reliability and Availability

No. Equipment MCBF MTBF (hour)

MTTR (hour)

1 Pos / AD N.A. N.A. 1 or less 2 Automatic Gate 100,000 N.A. 0.5 or less 3 TVM 100,000 N.A. 0.5 or less

Where, MCBF: Mean Cycles Between Failures MTBF: Mean Time Between Failures MTTR: Mean Time To Repair

All materials to be used in the manufacture and installation of the AFCS equipment shall be subject to approval by the Engineer/Employer.

6.2 Detailed Design

The Contractor shall develop site and station specification specific detailed designs, and prepare “shop” and “as-built” drawings to update the existing drawings, these shall include, but not limited to the following:

• Platform and Mezzanine Layout Drawings including Power and Data Layout; • Installation Drawings; • Schematic Diagrams; • Wiring (Power and Data) Diagrams; • Connection Diagrams; and • Fabrication Drawings.

6.3 AFC Equipment Installation Works

6.3.1 Transportation of AFCS Equipment

The Contractor shall provide transportation of the new AFCS equipment from the Contractor’s storage area to the installation sites. This activity shall also include transportation of existing AFCS equipment from a particular location where the removal of AFCS equipment is required, to the stations where these AFCS equipment is to be relocated, installed, tested and commissioned.

6.3.2 Installation of AFCS Equipment

The Contractor shall install various types of AGs (Entry, Exit, Bi-directional and End) to form new gate arrays in accordance with the AFCS base plan lay-out drawings.

The Contractor shall install Pos/AD as indicated in the AFCS based plan lay-out drawings.

In all ticket sales positions in the ticket offices (Ticket Booth and PAB), the Contractor shall:

• Provide both power and data connections for future installation of Pos/AD



• Provide seating (revolving chair) for each counter top; submission of material sample for approval by Engineer is required prior to delivery.

The Contractor shall install, test and commission the new SCS Consoles, as indicated in the AFC base plan layout drawings.

The Contractor shall ensure that no interruption in the revenue operation of the LRT Line 1 will result due to the installation, testing and commissioning works of the AFCS equipment.

All tools, equipment and accessories shall be provided by the Contractor in the execution and completion of the above-mentioned works for the AFCS equipment.

The Contractor shall propose to the Engineer/Employer, the temporary works and methodologies involved in undertaking all the necessary activities in the installation of all AFCS equipment during and outside the Employer’s revenue hours. The proposal shall be reviewed and agreed by the Engineer/Employer prior to execution of the works.

The Contractor shall also, upon request from the Employer within six (6) months of the commencement of revenue service, re-locate up to 15% of the AFCS equipment installed at the new stations, in order to better serve the actual passenger flow. The adjustments in the modification of the affected stainless steel barriers and emergency staff doors, AFC equipment cabling and conduits shall be performed by the Contractor. The payment for the relocation of the gates shall be made from the Provisional Sum Item.

All equipment and materials supplied shall be indelibly labelled or otherwise identified to show its identity, type, version, function, location, rating or limitation as appropriate.

All works shall be in conformance with the latest version of the relevant Philippine Building/ Electrical Fire Codes.

6.3.3 Installation of Raceways

The Contractor shall install supporting members, fastenings, hangers, bracing, brackets, straps, bolts and angles as required.

Raceways shall be routed to building lines unless otherwise indicated.

Raceways shall be coordinated with other Contractors to ensure that the installation avoids conflict with other works.

All works shall be in conformity with the latest edition of the Philippine Electrical Code (PEC).

6.3.4 Installation of Cables

Multi-core cables shall be installed in conduits and trenches as indicated to complete the wiring systems.



A minimum separation of 90mm between power and data cables shall be provided to prevent potential electromagnetic and field interferences.

The maximum data cable length (RS422) from SCS to AFC Equipment (AG, TVM or Pos/AD is 100 meters.

Equipment earthing conductors shall be continuous throughout the full length of the equipment connection to the earthing bar.

All cables of AFC Equipment (power and data) shall be properly tagged.

Refer to Employer’s Requirements General Specifications Part 2 Section VI -2.

Cables passing through openings in equipment housings, ducts, raceways etc., shall be adequately protected from damage by chafing and rodent or water ingress in line with good installation practice.

6.3.5 Installation of Conduits

Rigid galvanised steel conduits shall be painted and coloured to match the station decoration.

Conduits shall not be less than 20mm diameter.

The total number of conductors permitted in a single conduit shall not exceed the cable percentage fill specified by the Philippine Electrical Code (PEC).

All cut ends of conduits shall be reamed or otherwise finished to remove rough edges.

When conduit enters a box or fitting, a bushing shall be provided to protect wire from abrasion.

Bends in conduits shall be not exceed 90o without a pull through box installed.

All conduits shall be securely fastened in place.

Where conduits cross a seismic movement joint, approved flexible conduit shall be used.

6.3.6 Installation of boxes and fittings

Conductors entering boxes or fittings shall be protected from abrasion.

All openings in boxes shall be adequately closed and sealed to prevent ingress of water and pests.

All boxes shall be rigidly and securely fastened in place.

Metal boxes and fittings shall be corrosion resistant or shall be galvanized to prevent corrosion.



Thickness of metal boxes shall not be less than 1.2mm thick. Covers and lids shall be of the same thickness as the box.

6.3.7 Drilling Method

Drilling of holes shall be done using the correct tools, i.e. Core Drilling Machine.

6.4 Facilities Works

6.4.1 Fabrication of barriers and Emergency Staff Gates

The Contractor shall supply and install stainless steel fixed barriers and Emergency Staff Gates to supplement the AGs in controlling access of passengers to the paid area as required for each station in accordance to the AFC base plan layouts.

Emergency Staff Gates shall be self-closing, bi-directional opening, and shall have the capability of being latched in the open position in the event of an emergency evacuation being required.

The Contractor shall provide and install manual locking mechanisms for all the Emergency Staff Gates. Locking mechanisms shall be installed on the paid side of the Emergency Staff Gates.

The design of barriers and Emergency Staff Gates shall be in keeping with station architecture and furniture and be subject to the agreement of the Engineer/Employer.

The Contractor shall install and fix the barriers and Emergency Staff Gates in place, using “dyna” bolts or similar fixings.

6.4.2 Termination of electrical grounding system at Electrical Room

A “Clean” earthing system for the AFC Equipment shall be provided by Electrical Works Contractor. This separate “Clean” earth shall be provided in each of the Electrical Rooms, following the Electrical Works Contractor Specifications. The AFC Contractor shall pick up the main “Clean” earthing bar at the Electrical Room of each Station.

7 .0 AFCS Equipment Installation And Interface Details

7.1 General

The Contractor shall perform detailed installation design and field investigations as required.

Various works shall be carried out with reference to the Scope of Works (SOW) and the AFCS Layout Drawings.

The Contractor shall secure all permits necessary for the execution of the works.

Measures shall be undertaken to ensure the health and safety of the public, Employer’s personnel and workers.



Work clearance requests shall be prepared by the Contractor and submitted to Employer / Engineer for review and agreement at least one week before the commencement of works. The request shall indicate the specific tasks to be undertaken, the area of work, the number of workers, date and time among others.

Prior to any works commencing, the Contractor shall submit to the Engineer / Employer for review and agreement a fully detailed Method Statement of all works to be carried out. No works shall commence until the Method Statements is agreed and accepted by the Engineer / Employer.

All activities related to the AFCS Works shall be subject to agreement of the Engineer before commencement of works.

8.0 Verification, Testing and Commissioning

8.1 General

Site Acceptance Tests (SAT) shall be carried out on site, subsequent to the installation of equipment and materials, to supplement the factory tests and to ensure proper operation of the AFCS equipment. The SAT shall verify both the autonomous operation of the AFCS system and the integrated operation.

8.2 Requirement

The Contractor shall fully observe the quality requirements of the Contract inclusive of all Safety Rules and Regulations in order to ensure all assembled equipment performs to the requirements of the AFCS system.

8.3 Installation/Verification Tests (IVT)

The Contractor shall submit a comprehensive Testing and Commissioning Plan (T&CP), which shall detail all the inspections and tests that shall be conducted. The T&CP shall be submitted in accordance with the conditions of the contract and prior to the commencement of any official tests. The T&CP shall be subject to the Engineer’s review and agreement.

To ensure the proper documentation of all sub-assemblies and their respective reference numbers of each AFC equipment installed (AG, TVM, Pos/AD and SCS), the Contractor shall record each AFC equipment to be commissioned in the specified Installation/Verification form via the Equipment Parts List.

The Contractor shall perform insulation tests, continuity tests and polarity tests on all cables (power, control, data and earth) that are terminated to the AFC equipment. These tests shall be carried out in full accordance with the following Standard and the current Philippine Electrical Code (PEC):




BS 7671 Requirements for electrical installations. IET Wiring Regulations. Sixteenth edition

The earth impedance shall be measured between the equipment earth connection and the test points (defined as any external point such as access doors or covers accessible to passengers / operators, or any internal part such as mechanical part of a module accessible to operators or technicians). Earth impedance shall be less than 0.2 ohms.

The continuity check, insulation between wires and insulation between wires and earth shall be performed on the power and signal cables of the AFCS equipment.

The Contractor shall perform Visual Inspection and Operation Check of all AFCS equipment in the stations and at the CCS. Operation check of all AFCS equipment shall be performed on Site, after equipment power-up and visual inspection. Test procedures shall be defined to ensure that all AFCS equipment is functional after installation.

8.4 Site Acceptance Tests (SAT)

The Contractor shall perform functional tests concerning all AGs, TVMs and Pos/ADs in stations that are linked with the SCS

The Contractor shall configure the Stations, check that all the AFCS equipment are integrated correctly, perform functional tests on the AGs, TVMs, and Pos/ADs, check that the applicable commands at the SCS are working and check the desired report output of the SCS.

The Contractor shall check the data transmission and reception between all station equipment and the SCS (downloading of data to the AFC equipment and uploading of data from the AFCS equipment).

8.5 Integrated Tests (IT)

The Contractor shall perform Integrated Tests (IT) to check the dialogue, data transmission and reception between the CCS and the SCS.

The Contractor shall perform tests on the following:

• Configuration of System Parameters at the CCS and SCS; • Encoding/Testing of tickets to be used during the Integrated Tests; • Tests at Station and Inter Station Level (Automatic Gates, TVMs, Pos/ADs and SCS); and • Final Tests on CCS- Station Data Processing and CCS reports.

8.6 Commissioning File

The Contractor shall perform and document the testing and commissioning of all AFCS Equipment with reference to Employer’s Requirements General Specifications Part 2 Section VI -2.



8.7 Safety Certification

Prior to the Employer’s issuance of the Taking Over Certificate, the Contractor shall submit a Safety Certificate in the approved format, for the integration of the new AFCS equipment to the Revenue Service with reference to Employer’s Requirements General Specifications Part 2 Section VI -2.

9.0 Warranty 9.1 General

The Contractor shall ensure that the design, materials and workmanship incorporated in the supply of the AFC equipment shall be free from defects and that the system and its related components and apparatus comply with their corresponding specification and/or relevant Engineer accepted/agreed data and drawings.

9.2 Warranty Period

The Contractor shall be responsible for making good any defect in or damage to any part of the AFC Equipment supplied which may appear or occur during the twenty-four (24) month Defect Notification Period (DNP) which shall commence from the date of Issuance of the Taking Over Certificate (TOC). If certain equipment has been in use prior to the Employer’s issuance of the TOC, the TOC shall be appropriately adjusted for this equipment.

9.3 Responsibility of the Contractor

The Contractor shall supply warranty and shall be responsible to make good any defect or damage without undue delay and at their own cost, for the repair and / or replacement of each component or apparatus which, under normal use and maintenance, becomes defective or inadequate during the warranty period, or during such period, fails to comply with this PPSP, technical data and / or Engineer accepted and agreed drawings.

The Contractor shall guarantee the continued availability of parts for the AFC equipment supplied for a period of ten (10) years after Site Acceptance. In the event such parts are no longer available in the market, the Contractor shall commit itself to supply compatible parts upon order on conditions prevailing in the market at the date of such order.

10.0 Spare Parts 10.1 General

The Contractor shall consider the use of consumables, spare parts/components and sub-assemblies throughout the life of the AFCS equipment supplied.

The Contractor shall additionally determine the use, supply and re-order quantities and timescales for each part.

The full quantity of spare parts, consumables and spare sub-assemblies as required by the contract shall be available and serviceable at the time of Taking Over of the works.

10.2 Warranty Period Spare Parts

The Contractor shall be required to provide sufficient spare parts and consumables to service the supplied AFCS Equipment during the DNP which shall be the “Warranty Period”. The spare



parts, consumables and spare sub-assemblies shall be used for the on-line preventive and corrective maintenance and for repairs.

10.3 Supply of Consumables, Spare Components and Sub-Assemblies

The Contractor shall recommend and supply consumables, spare components and sub- assemblies to support the operation and maintenance of the supplied AFCS equipment during the Defects Notification Period, wherein the delivery and supply of these spares shall take effect prior to the Employer’s issuance of the TOC, which shall be also the Warranty Period.

10.4 Consumables

The Consumables required during DNP shall be defined as components whose lifespan is directly related to the number of operation performed such as roller, belt etc. Consumable quantities shall be evaluated taking into account the following figures:

• Automatic Gates : 1,000 tickets per day, • TVMs : 1,000 tickets per day

The Consumable components shall be supplied to support the commercial Operation and Maintenance (O&M) of the supplied AFC equipment during the DNP and to be delivered prior to the Employer’s issuance of the TOC.

10.5 Unit Exchange Spares or Spare Components

Unit Exchange Spares or Spare Components, which suffer deterioration through daily usage, shall be defined as parts that are expected to require regular replacement under normal maintenance schedules such as motors, gears, rollers, electromagnets, sensors, etc.

The Unit Exchange Spares or Spare Components shall also be supplied to support the commercial operation and maintenance of the supplied AFC equipment during the Defects Notification Period and to be delivered prior to the Employer’s issuance of the TOC.

10.6 Capital Spares/Spare Sub-Assemblies

The Capital Spares/Spare Sub-Assemblies shall be Line Replaceable Units (LRU) which shall be complete modules (power supplies, ticket transports) whose standard exchange on site can be carried out easily and quickly. These LRUs are intended to be at the disposal of the field maintenance technicians, in order for them to quickly replace the failed equipment.

The Contractor as a minimum shall supply the following Capital Spares/Spare Sub- assemblies prior to the Employer’s issuance of the TOC:

Table 10.6-1 Capital Spares/Spare Sub-Assemblies

No. AFC Equipment Capital Spare / Subassembly Unit

Minimum Quantity Required

Automatic Gates 1-1 Ticket Collection Module One Assembly 2 1-2 Electronic Control Unit (ECU) One Piece 2 1-3 Turnstile Mechanism One Assembly 2



No. AFC Equipment Capital Spare / Subassembly Unit

Minimum Quantity Required

1-4 Validation Speaker One Assembly 1 1-5 Validation Indicator One Assembly 1 1-6 Maintenance Keypad One Assembly 1 1-7 Contactless Smartcard Module One Assembly 1 1-8 Gate End Display One Assembly 1 1-9 Passenger Information Display One Assembly 2

1-10 Power Supply Module One Assembly 2 1-11 Uninterruptible Power Supply (UPS)

One Assembly 2

TVM 2-1 Overhead Display One Assembly 1 2-2 Electronic Control Unit (ECU) One Piece 2 2-3 SJT Issuing Module

One Assembly 2

2-4 SVT Issuing Module One Assembly 2 2-5 Receipt Printer

One Assembly 1

2-6 Coin Handling Module

One Assembly 2 2-7 Banknote Handling Module

One Assembly 2

2-8 Ticket Reader/Encoder One Assembly 1 2-9 Touchscreen LCD

One Assembly 2

2-10 Maintenance Panel One Assembly 1 2-11 Power Supply Unit

One Assembly 2

2-12

Uninterruptible Power Supply (UPS)

One Assembly 2 Pos/AD

3-1 Pos Terminal(including Mouse) One set 1 3-2 Passenger Information Display One Assembly 1 3-3 Ticket Reader/Encoder One Assembly 1 3-4 Receipt printer One Assembly 1 3-5 Cash Drawer One Assembly 1 3-6 Uninterruptible Power Supply (UPS)

One Assembly 1

SCS 4-1 Communication Rack One Set - 4-2 Computer Set for SPS including Monitor,

Keyboard, Mouse and Accessories One Set -

4-3 Printer

One Assembly - 4-4 Uninterruptible Power Supply (UPS)

One Assembly 1

10.7 Approval

The Contractor shall submit the recommended list of spare components and sub-assemblies to the Engineer for approval, before supply and delivery.



10.8 Delivery

The Contractor shall manufacture and deliver the spare components, consumables and sub- assemblies to the Employer in a timely manner to ensure that sufficient spares are available prior to the Employer’s issuance of the TOC.

11.0 Special Test Equipment, Portable Test Unit, Special Tools

11.1 General

The Contractor shall supply Special Test Equipment, Portable Test Unit and Special Tools to be used by the Maintenance personnel in the maintenance shop activities and the Operation personnel.

11.2 Special Test Equipment

The special test equipment shall be used by maintenance shop engineers used to ascertain the proper operation of a failed sub-assembly after repair.

The special test equipment shall be composed of:

• 1 unit personal computer connected to the sub-assembly in test through RS422 or equivalent interface communication, and

• 1 unit power supply connected to the sub-assembly in tests.

The equipment shall be capable of verifying the performance of the sub-assembly and to identify the deficient module.

The tests shall be selected on a menu by the keyboard with the result of the tests displayed on the Video Display Unit (VDU).

Tests, which are typical but not limited to the following, shall be available for the Reader/Encoder of the Gate, TVM and Pos/AD:

• Full process cycling one time; • Full process cycling many times; • Reading of maintenance counters; • Reset the maintenance counters; and • Cycling motor test.

The Contractor shall supply one (1) set of:

• Ticket Receipt Machine/Reader Encoder Special Test kit; • Ticket Issuer/Reader Encoder Special Test kit: Coin Accepter/Dispenser Special Test Banknote Accepter Special Test

Equipment shall include all software and installation disks required.



11.3 Portable Test Units (PTU)

A Portable Test Units (PTU) shall be used for the purpose of preventive maintenance to verify the correct operation of AGs and TVM, and during corrective maintenance to troubleshoot the defective sub-assembly.

The Portable Test Unit (PTU) shall comprise of the following:

• Keyboard, • Alphanumeric display, and • Data connector for connection to the Main Processor PCB.

The PTU shall be capable of being connected into the AGs, and TVM electronic circuit without disrupting its operation.

The PTU shall be used by the maintenance engineer for:

• Uploading of data when at the same time the SPS is not connected; • Reading of statistical counters; • Reading of alarms, and • Controlling of the AGs under test mode.

The Contractor shall provide ten (10) of Portable Test Units.

11.4 Special Tools

The Special tools shall be used to adjust the mechanical modules in the workshop.

The Contractor shall provide one (1) set of special tools for each of the following:

• Gate ticket receipt machine • TVM ticket issuer • TVM Coin Accepter/Dispenser • TVM Banknote Accepter

12 .0 Documentation 12.1 General

The Contractor shall provide to the Employer, all documentation in English, for each type of AFC equipment delivered, in print and in Electronic format.

All documents shall be written in the English language and all drawings and illustrations drawn to System International (SI) units.

Whenever special software is required in the access of the supplied documents and drawings, the corresponding software, interface programs and hardware shall also be provided. All software that was custom designed for this project shall have no licensing restrictions.



12.2 Documentation Requirements

The Contractor shall provide to the Employer the following manuals (one original plus five properly bound oil, dirt and pest-resistant hard copies) as well as the manuals in electronic format:

• Operating Manuals; • Maintenance Manuals; • Electrical Files; • Spare Parts List Manual, Illustrated Parts Catalogue (IPC); and • Special Test and Tools Equipment Manual.

13.0 Training

13.1 General

The Contractor shall provide comprehensive training to the Employer’s Staff including full- time on-site management and coordination of the training program to ensure continuity of classes and proper distribution of training materials. In addition the Contractor shall give support to the instructors as required.

Specific objectives of each course developed by the Contractor shall be discussed in conjunction with the Employer, through a process to be mutually agreed between the Engineer/Employer and the Contractor.

Training manuals to be used during training shall be delivered to the Engineer/Employer at least one month prior to any training class. The training manuals shall be accurate, complete, and of professional quality.

Instructor and trainee manuals shall be provided for each course. In addition, the Contractor shall be responsible for the provision of, and where necessary, for developing and manufacturing, training aids and material in support of all training conducted as part of this Contract.

All training aids and materials shall be handed over to the Employer upon issuance of the TOC.

13.2 Training Plan

The Contractor shall submit a Training Plan which shall include the following:

• Details of the Contractor’s ability to carry out the necessary training; • Course details including duration, maximum number of trainees per session, facilities

required, and pre-requisites for completion of the course; and • Recommendations for additional training or alternative means by with the Employer’s

training objectives may be met.

The submitted Training Plan shall be submitted for review by the Engineer/Employer and will be implemented in a time frame such that complete and comprehensive training has been received by the designated employees of the Employer, prior to start of operation. The training plan shall be in different modules that may allow independent implementation covering the following areas:



• Operation Staff Training, • Maintenance Staff Training, and • SCS Staff Training.

Training Kits including hard and soft copies of all training material shall be provided by the Contractor for each of the instructors and trainees.

14.0 Contactless Tickets (reference only) 14.1 General

The Contactless Ticket will be provided by the Concessionaire.

• General

The Contactless Ticket shall meet the Common Ticketing System in all the attributes and containing information.

• Media Specification

Contactless smartcards ISO/IEC 14443 compliant and both of either type A or type B.

Size: 85.47mm – 85.72mm x 53.92mm – 54.03mm Thickness: Single Journey Ticket 0.50mm ±0.05mm Stored Value Ticket 0.80mm ±0.05mm

• Ticket Types

Single Journey Tickets, which shall be issued by the TVM or Pos/AD and shall be of common visual appearance;

Stored Value Tickets which shall be issued by the TVM or Pos/AD. Senior Citizens shall also qualify for discounted SVTs;

Employee Passes, which shall allow staff to undertake journeys without payment as well used for identification purposes to operate certain equipment; and

Test Tickets during maintenance operation.

AUTOMATIC FARE COLLECTION SYSTEM (ANNEX A) AUTOMATIC GATE LRT Line 2 Extension Project

Automatic Fare Collection System (Annex A) Automatic Gate

Table of Contents Page Abbreviations 1 A2.0 Maintenance and Diagnostics 2 A3.0 Gate Hardware Design 2 A3.1 Modular Design 2 A3.2 Major Modules of Gates 2 A3.3 Electronic Control Unit 3 A3.4 CSC Module 3 A3.5 Validation Indicator 3 A3.6 Validation Speaker 3 A3.7 Gate End Display 3 A3.8 Passenger Information Display Module (PID) 3 A3.9 Ticket Collection Module 4 A3.10 Turnstile Mechanism 4 A3.11 Maintenance Keypad 4 A3.12 Power Supply System 4 A3.13 Miscellaneous 5 A4. 0 General Specifications of The Gate 6 B2.0 Tvm Hardware Design 6 B2.1 Modular Design 6 B2.2 Major Modules of TVM 6 B2.3 Overhead Display 7 B2.4 Electronic Control Unit 7 B2.5 Single Journey Ticket Issuing Module 8 B2.6 Stored Ticket Issuing Module 8 B2.7 Receipt Printer 9 B2.8 Maintenance Panel 9 B2.9 Coin Handling System 9 B2.10 Banknote Acceptor 11 B2.11 Touch Screen LCD 11 B2.12 Contactless Smart Card (CSC) Add Value Module 11 B2.13 Power Supply System 12 B2.14 Miscellaneous 12 B3.0 General Specifications of The TVM 13 C1.0 General Description 13 C2.0 Hardware Specifications 13 C2.1 Pos Terminal 13 C2.2 Passenger Information Display 15 C2.3 Contactless Smart Card Reader/Writer Module 15 C2.4 Cash Drawer 15 C2.5 Receipt Printer 15 C2.6 Uninterruptible Power Supply (UPS) 16 C2.7 Miscellaneous 17 C3.0 General Specifications of the POS/AD 18 D1.0 General Description 18

D1.1 System Requirements 18 D1.2 Required Performance 18 D2.0 Hardware Specification 19 D2.1 Specifications for Station Computer 19 D2.2 Printer for Station Computer 20 D2.3 Uninterruptible Power Supply (UPS) 21 D2.4 Miscellaneous 22 D3.0 General Specifications of the Station Computer System 23 E1.0 General Description 23 E2.0 Hardware Specification 23 F1.0 General Description 25 F2.0 Hardware Specification – Core Switch & Network Switch 25 G1.0 General Description 27 G2.0 Horizontal Subsystem Cabling - Rj45 Patch Cords 27 G3.0 Patch Panels 28 G4.0 Cable Management System 28 G5.0 Power Cable Distribution 28 G6.0 Grounding 28 G7.0 Data Cabinets 28 H1.0 Performance Standards and Specifications 32


Section VI-4 Supplementary Information Page – AFC/A -1 December 2015

Abbreviations AC Alternating Current AD Analyzer Dispenser AFCS Automatic Fare Collection System AG Automatic Gates BIOS Basic Input /Output System CCS Central Computer System CF Compact Flash CRU Card Reader Unit CPU Central Processor Unit CSC Contactless Smart Card CSCR Contactless Smart Card Reader ECU Electronic Control Unit GUI Graphic User Interface I/O Input /Output LAN Local Area Network LCD Liquid Crystal Display MCBF Mean Cycles Between Failures MMI Man Machine Interface MP Maintenance Panel OS Operating System PAB Passenger Assistance Booth PID Passenger Information Display Pos Point of Sales RAM Random Access Memory RW Reader Writer SAM Security Application Module SCS Station Computer System SJT Single Journey Ticket SVT Stored Value Ticket TFT Thin Film Transistor TVM Ticket Vending Machine UPS Uninterruptable Power Supply USB Universal Serial Bus



Annex A Automatic Gate A1.0 General Description

The Automatic Gate (AG) shall consist of a walkway aisle between two steel gate cabinets. The control of passenger movement shall be done through a Turnstile Mechanism upon successful processing of passengers’ tickets through the contactless ticket reader-writer.

In the station, the transition area between the Paid Area and Free Area shall compose of a series of gate arrays with adjacent gate cabinets forming an aisle.

In event of emergency, station staff shall be able to use station computer or by pushing emergency button located in the station staff room (next to gate array) causing the turnstile barrier arm to drop freely to allow evacuation of passengers from paid area without obstruction.

A2.0 Maintenance and Diagnostics Diagnostic functions shall be available via the maintenance keypad located in the AG. The AG shall provide a series of diagnostic tests to enable a complete diagnostic of all modules and components.

Maintenance doors and top covers shall be designed to facilitate easy trouble shooting and replacement of components within the AG.A3.0 Gate Hardware Design.

A3.0 Gate Hardware Design A3.1 Modular Design

With the fast removing and installation methods of sub-modules, the time required to serving on site shall be reduced and availability of equipment shall be increased.

The mounting of the modules shall be designed to be tool free or with simple tools such as screw drivers, no complicated tools or equipment shall be required to remove or replace the modules.

A3.2 Major Modules of Gates

The Gate shall consist of the following main modules. The modules inside the Gate shall be all independent modules.

• Cabinet; • Ticket collection module (Exit and Bi-directional Gate only); • Electronic Control Unit (ECU); • Turnstile Barrier Mechanism; • Power Supply Unit; • Uninterrupted Power supply; • Validation Speaker; • Validation Indicator; • Maintenance keypad; • Contactless Smart Card Module; • Gate End Display; and • Passenger Information Display.



A3.3 Electronic Control Unit

The Electronic Control Unit shall control all the units/modules in the Gate and shall be easily removed and replace in the event of failure.

The Electronic Control Unit shall be the following or equivalent.

Table A3.3-1 ECU Specification

Items Specifications (ex; ETKD-SGS-MRT01-A01-01 from Tech-Kinetics)

Processor Intel ATOM D525,1.8Ghz Memory 2GB On-board RAM Drivers QNX 6.5 Drivers I/O 48 DI/O Input +9Vto +30V input

A3.4 CSC Module

The CSC module shall comprise of the CSC Readers and top covers. The readers are capable of handling multi-technology cards presented in the AFC system. Clear indication shall be provided to indicate the position where passenger should present their tickets.

A3.5 Validation Indicator

The AG shall be equipped with two Validation Indicators for visual feedback. Both indicators shall be located at the top of the AG for both passenger and station staff. This indicator shall be positioned ergonomically to provide any casual user or station staff to notice the colored display. The indicators are located on paid and free area of the gates. The validation Indicator shall provide two colors, mainly Red, Green.

A3.6 Validation Speaker

The Validation Speaker shall be provided to further enhance the validation result. A normal pitch indicates a successful transaction while a different tone tells that a failure has occurred. The AG shall be also provided configurable tone settings for different ticket type usage.

A3.7 Gate End Display

The AG shall be equipped with a Gate End Display which indicates the aisle direction and it is visible from at visible from at least A30 meters. This will alert passenger and direct them to the correct aisle. A Green arrow shall indicate tie AG aisle is unusable and a red cross indicates that the aisle is not accessible for passage. Any critical faults in the Gates shall trigger an unserviceable status to SCS.

A3.8 Passenger Information Display Module (PID)

The PID shall be positioned on top of the AG with an inclined and titled position for passenger to view conveniently blending into the Gate shape. The display unit shall be visible under strong ambient light in the station environment.



The Reversible aisle shall have two PID at both side of the Paid and Free area. The Entry and Exit aisle shall only have one at either side of Paid and Free area.

The GUI form part of the information to direct passenger on the usage of the tickets, or any other information that can be defined.

The PID shall have the capability of displaying English text which comes from the Gate application software.

The PID specification shall be the following or equivalent.

Table A3.8-1 PID Specification Items Specifications

Screen Diagonal 6.5 inch Active Area 132.48(H) × 99.3699.36(V) Pixels H × V 640×3(RGB) × 480

A3.9 Ticket Collection Module

The Exit and Reversible gates shall have an additional collection module to collect tickets from passenger exiting the paid area. This module shall allow tickets to be inserted and validated. Upon successful validation, the ticket shall be collected in the magazine and barrier is open to allow passage. If the ticket is not successfully validated, the inserted ticket shall be returned to the passenger via the same insert slot and clear indications shall be activated to alert the passenger.

A3.10 Turnstile Mechanism

The Turnstile Mechanism shall be designed to be at 120 degree, allowing only one passenger to walk through the aisle upon successful validation of their tickets.

The Turnstile Mechanism shall be controlled by the commands from the ECU to release the locking latch that locks the turnstile from turning. Once the passenger push the turnstile, it shall auto reset to 120 degree position again.

A3.11 Maintenance Keypad

The Maintenance Keypad shall be used for login/logout and selection for maintenance menu MMI of the Gate. It shall have numeric and function keys to use to navigate the maintenance screen. This keypad shall be placed inside the Gates and shall only be accessible to authorized operators accessing the Gates.

A3.12 Power Supply System

• UPS

The UPS, which is installed within the Gate cabinet, shall be used to provide orderly shutdown of the Gate when a source AC power failure occurs. The UPS also shall ensure that any on-going transaction be completed before going to power failure mode. The UPS shall be able to support Gate for up to fifteen (15) minutes of operation and is interfaced to the ECU.



The UPS shall be able to withstand disturbances and short interruptions of 1-20seconds, too the power supply with the minimum requirement being that no service interruption or loss of audit data from completed and partially completed transactions occurs.

This UPS shall ensure a temporary backup of the 220 V Power Supply. It shall include charging of the internal batteries, monitoring of the incoming main power supplies. It has an internal battery and electronic circuits which provides the power monitoring and stability usage.

• Power Supply Unit

The power supply unit shall ensure the power supply of the Gate equipment from the station mains.

A3.13 Miscellaneous

• Cable All cables shall be properly terminated at both end with secured clips, screws or interlocking mechanism to prevent loose connection. The cables at both ends are label with identification to prevent any mishandling during maintenance works.

Cable of same type shall be grouped together where control cables and power cables shall be separated out during cabling. All AC power cables shall be separated from telecommunication cables to prevent any interference.

• Grounding All the gate metal parts shall be grounded to protect to prevent electrical shock to patrons using the gate. These shall include all doors, covers and panels.

The grounding design and implementation shall comply with the International Electricity Regulation. The Gate also shall have grounding points which can be connected to the station main ground.

• Security Security shall be taken care of the Gate so that unauthorized personnel will not be allowed to access the Gate interior. Security lock shall be located at the maintenance access doors. Accessing the top lid panel and center panels shall depend on the latch hidden within the cabinet.

The gate shall be fitted with security locks that require unique key to access. The top lid cover can be open via a lock.

The access door of the gate when opened, shall only affect the aisle required for maintenance, the operation of the adjacent aisles shall not be affected by the maintenance aisle.

The Gate shall automatically goes Out of Service if any access door is opened.



A4. 0 General Specifications of the Gate

Table A4.0-1 General Specification of the Gate Items Specifications

Input Voltage 220 V+10%-15%, Power Maximum 300W Dimensions (L×W×H) Within 2000mm×300mm×120mm Weight Maximum 300Kg Aisle Width Minimum 500 mm Passenger Throughput ≥ 35 passenger per minutes SC Communication Ethernet 10/100/1000 Mbps Ticket Collection Magazine Minimum 650tickets per magazine (2 magazines) MCBF ≥ 100,000 Environment 0-50 degree / 25-80% RH

Annex B Ticket Vending Machine

B1.0 General Description The Ticket Vending Machine (TVM) shall be located in the free area in the station and provides services such as issue of Single Journey Tickets (SJT) and Stored Value Tickets (SVT). It shall support 2 types of cash payment with coins and banknotes. The TVM shall be linked to the SCS via the station LAN.

B2.0 TVM Hardware Design B2.1 Modular Design

With the fast removing and installation methods of sub-modules, the time required to serving on site shall be reduced and availability of equipment shall be increased.

The mounting of the modules shall be designed to be tool free or with simple tools such as screw drivers, no complicated tools or equipment shall be required to remove or replace the modules.

B2.2 Major Modules of TVM

The TVM consists of the following main modules.

• Housing; • Overhead Display; • Electronic Control Unit (ECU); • Single Journey Ticket (SJT) Issuing Module; • Stored Value Ticket (SVT) Issuing Module; • Receipt Printer; • Maintenance Panel; • Coin Handling Module;



• Banknote Handling Module; • Touchscreen LCD; • Power Supply Unit; and • Uninterruptible Power Supply (UPS).

B2.3 Overhead Display

The overhead operation mode display shall be use to indicate current equipment operating mode and operation mode, including Temporarily Out of Service, No Change, Closed, Coin Only or any other customizable message set by parameters or Mode Commands sent be Station Computer.

The Operation mode display shall use display of sufficient display size that allows easy identification of the operating mode to the passengers from a reasonable distance. The display shall be of sufficient contrast to allow easy reading in brightly lit areas.

The location of the operation mode indicator conforms to ergonomics and overall design of the TVM. The positioning shall be easily seen so as to alert the passengers of the current operating mode of the TVM before operation commences.

B2.4 Electronic Control Unit

The TVM shall be using the Electronic Control Unit (ECU) to work as the main control unit. The ECU shall be the central control for all functions of the TVM. This module shall include the Central Processor Unit (CPU), mother board, Random Access Memory (RAM) and, Compact Flash (CF) for storing of OS, Applications, Transaction Data and Audit Register.

The ECU shall be designed to work with the Maintenance MMI for testing and debugging for sub-modules.

It shall enable the TVM to be connected to a Station Computer System (SCS) through a local area network via its Ethernet port or working as a Stan-alone unit in the event that the link between the TVM and SCS is down.

The communication shall be re-established automatically once the link is up.

The ECU shall handle all the ticket processing and data transfer between the TVM and SC. In addition, the ECU shall interface with all the internal modules such as Ticket Reader, SJT Issuing Module, SVT issuing Module, Touchscreen LCD, Overhead Display, Coin handling Module, Banknote Validator, UPS, and Printer.

The ECU shall be based on a standard embedded PC and shall use readily available standard modules. The ECU shall have sufficient memory space for all programs and data required to control the TVM with 25% additional capacity. Serial ports, USB ports, and Ethernet port shall be provided for communication with the Station Computer and major sub-modules. The communication link shall be via differential line drivers and receivers. Digital I/O shall be provided for all functions requiring direct, real time control by the ECU.

The ECU shall be a light weight box that can be easily removed and replaced in the event of failure by single maintenance personnel.

The Electronic Control Unit shall be the following or equivalent.



Table B2.4-1 ECU Specification Items Specifications (ex; ITA-1910 series from Advantech)

Processor Intel ATOM D525,1.8Ghz Memory 4GB On-board RAM I/O Interfaces 2 VGAs 2 LANs 8 USBs 16 Serials (RS232/422/485)

48 DI/Os 3 Audios Input +9Vto +36V input Environment -25 to +60 degree (Operating without HDD)

0 to +40 degree (Operating with HDD)

B2.5 Single Journey Ticket Issuing Module

The Ticket Issuing Module shall manage the issuing of contactless Single Journey Tickets (SJT) in the Ticket Vending Machine (TVM).

Table B2.5-1 Single Journey Ticket Issuing Module Specification Items Specifications

Ticket Issuing Time ≤ 1 sec Ticket Capacity 650 × 2 ( 0.5mm thickness) Reject Bin Capacity 30 ( 0.5mm thickness)

B2.6 Stored Ticket Issuing Module

The Ticket Issuing Module shall manage the issuing of contactless Stored Value Tickets (SVT) in the Ticket Vending Machine (TVM).

The processing of the card shall consist of reading, writing and, verifying. The blank card shall be initially read to check if it is valid. Invalid cards shall be rejected into the reject bin. Valid card shall be then written with the appropriate value as selected by the passenger. The card shall be then verified to ensure that the correct value was written before dispensing to the passenger.

Smart Cards shall be stored in the ticket magazine of capacity of 150cards. The system shall monitor the number of tickets remaining in the magazine to give alarms when the magazine becomes ‘almost empty’ and ‘empty’. These alarms shall be sent to the SCS to alert the station operators of the tickets in the magazine.

The status report shall let the station operators know when it is time to replenish tickets to the magazine. The operation of the Card Issuing shall be dependent on the Payment System. When an appropriate fare has been paid to the Payment System the ticket shall be automatically taken from the magazine and processed and then dispensed.

The issuing module shall also be able to accept passenger card for enquiry or processing.

Table B2.6-1 Stored Value Ticket Issuing Module Specification Items Specifications

Ticket Issuing Time ≤ 1 sec



Ticket Capacity 150 ( 0.8mm thickness) Reject Bin Capacity 40 ( 0.8mm thickness)

B2.7 Receipt Printer

The receipt printer shall be included to print customer receipt and audit reports. It shall be designed to hold paper roll size of approximately 10cm. the printer shall be linked to the ECU.

Table B2.7-1 Receipt Printer Specification Items Specifications

Print Method Thermal Print font 12×24 / 9×17 / 24×24 Print column 42 average Word library Built-in word library Specification for Print paper Width 79.5mm thickness 0.06 - 0.15 Print speed 150mm / sec Reliability 37,000,000 lines 1,000,000 cuts

B2.8 Maintenance Panel

The Maintenance Panel (MP) shall be installed in the TVM to carry out instructions of special diagnostic task on the machine. The task shall also include various maintenance operations including shift data printing etc. it shall use 10.4” backlit TFT LCD panel with resistive touch screen to process all the instruction with ease.

B2.9 Coin Handling System

The inserted coins shall be validated by the Coin Accepter. The accepted coins shall be directed to one of the six tubes within the accepter. The Coin Accepter shall be able to be programmed to accept up to 8 different denominations of coins.

When the transaction is successful and tickets are issued to the patron, the coins held at the tubes shall be kept for coin- circulation as change.

When there is change to be given to the passenger, the change shall be given via the coin tube into the return tray. Should a need to perform an end-of-day clearing of the coins in the tube, coins shall be emptied into the coin vault.

TVM shall allow the re-circulation of coins collected from previous transaction as coin change for future transactions as to reduce the number of attempt to replenish coin hoppers, thus reducing the downtime of equipment.

The coin vaults shall be able to be safety removed from the TVM with authorized personnel holding the keys. The Coin vault shall be securely locked to the cradle once it is inserted in. only authorized personnel with the key shall be able to unlock and removed the vault from the cradle. Aperture of the vault shall be automatically closed when vault is removed.

The Coin Handling Module includes:



• Coin Acceptor; • Coin Hopper; • Coin Vault; and • Control Board.

Table B2.9-1 Coin Handling Module Specification Items Specifications

Coin Acceptor 1 peso, 5peso, 10peso (issued the latest) Coin Accepted Rate 1 coins per sec Coin Dispensing Rate 6 coins per sec Coin Vault 1 peso – 2000 coins approx. Coin Tube 6 tubes shall be available Coin Change Hopper 1 peso—1000 approx. per hopper

5 peso—800 approx. per hopper

• Coin Acceptor

The Coin Acceptor selected for TVM shall be a standard product commonly used for Automatic Fare Collection equipment.

The Coin Acceptor shall be able to accept the bellow denominations of Philippines Peso coins commonly used:

1 peso 5 peso 10 peso Spare for 2 coin denominations.

Coin shutter shall be implemented at the coin bezel and set to normally close:

Before a selection has been made or before the fare due is displayed; When a transaction has been accepted but before the ticket is issued; and When the machine is out of service.

• Coin Hopper

Two change hoppers shall be provided for an additional of change capacity of total 2000 coins. There shall be 2 change dispensers with 1000 coins each to supplement each of the accepted coin types. The coin hopper shall be able to handle Philippines Peso coins with denomination of 1 peso, 5 peso, 10 peso.

Table B2.9-1 Coin Hopper Specification Items Specifications

Coin Dispensing Rate Up to 4 coins per sec Capacity Up to 1000 coins (depending on size)

• Coin Vault



Coins vault shall be used to collect coins inside the TVM. Excess coins shall be routed to the coin vault when the circulating coin hoppers are full. When clearing the circulating coin change cassettes, coins shall be diverted to the vault. The vault shall be a secured box with 2 key locks, one to open the box and the other to open the coin inlet.

The material for coin vault shall be stainless steel. It shall be design to hold more than 1000 coins.

The coin vault when removed from cradle shall be totally sealed. A key shall be required to be removed from the locking cradle and a separate key to open the vault. The cash aperture of the coin vault shall automatically close when the cradle is unlocked.

B2.10 Banknote Acceptor

The Banknote Acceptor shall validate and accept or reject return, escrows and stack notes inserted by the user. Notes inserted but not validated shall be returned to the user immediately. Notes inserted and validated shall be held in the escrow pending the issue of tickets or cancellation. Upon completion of the transaction, the notes held in the escrow shall be transported into a note-box where they shall be stacked and retained until the removal of the note-box by authorized collectors. If transaction is cancelled before the issuing of tickets, the notes held in the escrow shall be returned to the user through the return note slot. The Banknote Acceptor shall have means to detect jammed noted in any section of the note acceptance.

It shall be possible to recognize new denominations when introduced into circulation. This reprogramming shall have to be done by the manufacturer of the Banknote Acceptor, whenever new note sets are released.

Table B2.10-1 Banknote Acceptor Specification Items Specifications

Capacity 20 peso, 50peso, 100peso banknotes (issued the latest) Escrow 15 notes Note-box capacity 1000 notes

B2.11 Touch Screen LCD

The Touch Screen LCD shall be positioned at center of the TVM with an inclined and tilted position for passenger to view conveniently. The display unit shall be clearly visible under strong ambient light in the station environment.

The touch Screen LCD shall have the capacity of displaying both of English and Tagalog text which comes from the TVM application software.

B2.12 Contactless Smart Card (CSC) Add Value Module

The CSC Add Value Module shall consist of the card cradle and CSC Reader Writer. The CSC-RW shall be used for add value to SVT. It shall be mounted on the upper front door. CSC shall be placed onto the cradle before any reading and writing is performed on the CSC. On completion, it shall be able to be removed by the passenger.



B2.13 Power Supply System

• UPS

The UPS, which is installed within the TVM housing, shall be used to provide orderly shutdown of the TVM when a source AC power failure occurs. The UPS also shall ensure that any on-going transaction be completed before going to power failure mode. The UPS shall be able to support TVM for up to 10 minutes of operation and is interfaced to the ECU.



• Power Supply Unit

The power supply unit shall ensure the power supply of the TVM equipment from the station mains.

B2.14 Miscellaneous

• Cable All cables shall be properly terminated at both end with secured clips, screws or interlocking mechanism to prevent loose connection. The cables at both ends are label with identification to prevent any mishandling during maintenance works.

Cable of same type shall be grouped together where control cables and power cables shall be separated out during cabling. All AC power cables shall be separated from telecommunication cables to prevent any interference.

• Grounding

All the TVM metal parts shall be grounded to protect to prevent electrical shock to patrons using the gate. These shall include all doors, covers and panels.

The grounding design and implementation shall comply with the International Electricity Regulation. The TVM also shall have grounding points which can be connected to the station main ground.

• Security Security shall be taken care of the TVM so that unauthorized personnel will not be allowed to access the TVM interior. Security lock shall be located at the maintenance access doors.

The TVM shall automatically go Out of Service if the front door is opened.

Two sets of security keys shall be provided for every TVM Cabinet for the operation and maintenance staffs usage.



Similarly, all cashboxes shall have dual key security system.

B3.0 General Specifications of the TVM

Table B3.0-1 General Specifications of the TVM Items Specifications

Input Voltage 220 V+10%-15%, Power Maximum 400W Dimensions (H×W×D) Within 1800mm×1000mm×750mm Weight Maximum 400Kg SCS Communication Ethernet 10/100/1000 Mbps Ticket Collection Magazine Minimum 650tickets per magazine (2 magazines) MCBF ≥ 100,000 Environment 0-50 degree / 25-80% RH

Annex C Point of Sales/Analyzer-Dispenser C1.0 General Description

The Point of Sales and Analyzer -Dispenser (Pos/AD) shall be installed in the air-conditioned Ticket Booth and Passenger Assistance Booth. The Pos/AD shall be capable of reading and encoding contactless smartcard media of ISO/IEC14443 Type A and B within proximity 40 centimeter and within 800 milliseconds of the transaction time including terminal processing and communication time.

C2.0 Hardware Specifications POS/AD shall consist of the following;

• Pos terminal with touch screen, keyboard and mouse • Passenger Information Display • Contactless Smartcard Reader/Writer Module • Receipt Printer • Cash Drawer • UPS

C2.1 POS Terminal

The following specification is the minimum for POS Terminal. The contractor shall be responsible for choosing a POS Terminal with the necessary performance.

Table C2.1-1 Pos Terminal Technical Specification Items Specifications

CPU Intel Dual-core 1.8GHz

Mother Board Chipset Intel Chipset



Items Specifications System Bus Frequency 800MHZ

RAM/Memory 4GB/DDR3

Hard Disk 250GB Solid State Hard Disk

HDD Type Solid State Hard Disk

Audio System Integrated AC 97

Network LAN: RTL 8103E (10/100 Mbps)

Optional: WIFI 802.11n

Interface USB 2.0

Video Memory Built-in INTEL EXTREME GMA3150

Video Capability Max shared memory 256MB

Standard 1*VGA, 4*USB2.0, 1*RJ-45,1*Parallel, 1*serial, PS/2 , earphone, mic

Material Metal

Color black

Power In 100~240V 50/60HZ

Power Out External Adapter DC12V 7A

Operating System Microsoft Windows

Standard AC adapter ,Power cord, Stand or wall mount

Display Size 15inches

Display Ratio (4:3)

Resolution 1024(H) X 768(V)

Contrast (500:1)

Response Time 5ms

Brightness 250cd/m2

View Angle 160°/140°

Max. Color 16.2M

Touch Size 15"

Touch Screen Type Standard: 4 wire resistive (Optional: SAW, infrared, 5 wire resistive etc.)

Operation Condition 5°C~+40°C (41°F~+104°F), 20%RH~80%RH, non-condensing max. wet bulb 26°C (78.8°F)

Storage Condition -20°C~60°C (-4°F~140°F), 10%RH~80%RH, non-condensing max. wet bulb 28.9°C (84.0°F)

Application Office work, Finance, Medical, school supplies, Bank, Catering, entertainment, Shopping and Jukebox and so



Items Specifications on

Warranty Three years; with 24 hours response time

C2.2 Passenger Information Display

The Passenger Information Display shall be a dots-matrix display which shows the fare amount and readout data to the passenger. The display shall be of sufficient display size and of sufficient contrast to allow easy reading in brightly lit areas.

C2.3 Contactless Smart Card Reader/Writer Module

The Contactless Smart Card Reader/Writer Module shall be a module which install the Contactless Smart Card Reader/Writer Unit (refer to Annex E). This module shall be used to read/write the tickets to analyze or dispense.

C2.4 Cash Drawer

The Secured Cash Drawer for POS/AD shall be included on the contractor’s offer. The cash drawer shall be connected directly to the USB port and it must be application software program supported to control the opening.

Specifications: • 2 Media Slots; • coin/5 bill money Tray; • All steel with stainless steel front face; • Above/under-the-counter installation; and. • Allows you to place keyboard and monitor on top

C2.5 Receipt Printer

The AFCS Contractor shall include the POS/AD Receipt Printer which will be directly connected to the Station POS Terminal. The specification of the roll paper shall be same as the existing system.

The following specification is the minimum for Receipt Printer. The contractor shall be responsible for choosing a printer with the necessary performance.

Table C2.5-1 Receipt Printer Technical Specification Items Specification

Print

Printing Method Thermal Line Resolution 203DPI, 8 dots/mm Printing Width 58mm(384 dots) Printing Speed 100 mm/s Print Density 1-5 line

Port USB / RS232 / Parallel port / Ethernet port

Memory Flash 2MB Character Set Typeface Font A:12*24, Font B 8*16 CHN:24*24



Items Specification Alphanumeric 95 Extended Character 128*14 International Character 15

Bar Code 1D UPC-A, UOC-E, EAN8, EAN13, CODE39,ITF, CODEBAR, CODE128, CODE93

Detection Detection Lack of paper detection LED Indicator Lamp

Power light Green Error LED Red

Power Input AC 100V-240V, 50-60HZ Output DC 9V-2A

Paper Spec

Paper Type Thermal paper Paper Width 58 mm Paper Thickness 0.56-0.1 mm Roll outside diameter 83 mm Max. Paper Loading Drag the paper structure

Software Order ESC / POS

Drive Windows 2000/ XP/ Vista/7/8/POS Ready/Linux/OPOS

Physical Property

Work environment Temperature:0-45℃, Humidity:10-95% Storage environment Temperature:-10-60℃ ,Humidity:10-95% Size 186(L)*114(W)*128(H)mm Net Weight 1.06kg(without paper roll)

Reliability Life 100km

C2.6 Uninterruptible Power Supply (UPS)

The UPS, which shall be installed on each Pos/AD system located at Ticket Booth and Passenger Assistance Booth (PAB) shall be used to provide orderly and automatic shutdown of the Pos/AD when a source AC power failure occurs. The UPS also shall ensure that any on-going transaction be completed before going to power failure mode.





Table C2.6-1 UPS Technical Specification Items Specifications

Input

Nominal Input Voltage 230V Input Frequency 47 - 63 Hz Input Connections IEC-320 C14 Input voltage range for main operations 175 - 295V Input voltage adjustable range for mains operation 160 - 286V

Output

Output Power Capacity 660 Watts / 1100 VA Max Configurable Power 660 Watts / 1100 VA Nominal Output Voltage 230V Output Connections (1) IEC 320 C13 (Surge Protection) (3) IEC 320 C13 (Battery Backup)

Batteries & Runtime

Battery Type Maintenance-free sealed Lead-Acid battery with suspended electrolyte : leak proof Included Battery Modules 1 Typical recharge time 24 hour(s) Replacement Battery RBC33 RBC™ Quantity 1 Typical Backup Time at Half Load 15.2 minutes (330 Watts) Typical Backup Time at Full Load 5.2 minutes (660 Watts) Runtime Chart

Surge Protection and Filtering

Surge energy rating 180 Joules Filtering Full time multi-pole noise filtering : 5% IEEE surge let-through : zero clamping response time : meets UL 1449 Data line protection RJ-11 Modem/Fax/DSL protection (two wire single line)

Environmental

Operating Environment 0 - 40 °C Operating Relative Humidity 0 - 95% Operating Elevation 0-3000 meters Storage Temperature -5 - 45 °C Storage Relative Humidity 0 - 95% Storage Elevation 0-15000 meters Audible noise at 1 meter from surface of unit 45.00 dBA Online Thermal Dissipation 180.00 BTU/h

C2.7 Miscellaneous

• Cables

All cables shall be properly terminated at both end with secured clips, screws or interlocking mechanism to prevent loose connection. The cables at both ends are label with identification to prevent any mishandling during maintenance works. Cable of same type shall be grouped together where control cables and power cables shall be separated out during cabling. AC power cable shall be separated from telecommunication cables to prevent any interference.

• Groundings

POS/AD shall be grounded to protect to prevent electrical shock to patrons using the POS/AD. The grounding design and implementation shall comply with the International Electricity Regulation. The Pos/AD also shall have grounding points which can be connected to the station main ground.



• Security

The POS/AD shall be placed in the Ticket Booth or the station Attendance Booth. Software and BIOS setup must be protected by password and other source of security features that will surely secure the POS/AD.

C3.0 General Specifications of the Pos/AD

Table C3.0-1 POS/AD General Specification Items Specifications

Input Voltage 220 V+10%-15%, Power Maximum 900W SCS Communication Ethernet 10/100 Mbps Environment 5-40 degree / 25-80% RH

Annex D Station Computer System

D1.0 General Description The Station Computer System (SCS) shall be located inside the Ticket Booth. The SCS shall be the one will control the Automatic Gates, Ticket Vending Machine and other equipment’s connected on the AFCS network locally. The SCS shall be linked to the CCS via the station Local Area Network and will be linked to the Core Switch for the Communication Backbone Network of Line 2.

• The computer system shall be a Mini Tower Server Based hardware specification. It shall at least be equivalent to better on the listed specifications.

D1.1 System requirements

• The SCS shall be in secure housing and hosting. • Capacity shall be sufficient to guarantee that all daily and or periodical data uploads and

downloads and additional processing is completed within the same 24-hour cycle. • Initial capacity shall support current PTO operations and planned extensions, and shall

include contingency for Level 1 Infrastructures and network outages. The contingency means that in case of recovery after delays, the system shall be able to process 1 additional day’s transaction load per day.

• All non-application components versions (e.g. operating systems, databases, etc.) shall be kept compliant with their respective vender’s releases and support policies.

• Security patches shall be tested and implemented immediately after being issued by the Vendors.

• By architecture and design the system shall set up scalable, i.e. increased production load may lead to commissioning of additional capacity, but shall not lead to changes in architecture or design.

D1.2 Required Performance

The Station Computer Systems shall perform the following at a Station:



Monitor and control all the Level 1 Infrastructures on same Station and at least the following functions shall be supported:

• Viewing the current setting and changing the setting of the direction of bidirectional gates.

• Viewing the current state and changing the operational state of Level 1 Infrastructure devices.

• Emergency related actions (i.e. opening of all Automatic Gates in case of a calamity). However back-up of emergency related actions will also be provided through direct control of the Automatic Gates that will work standalone (without Level 2 Infrastructure dependency)

• Generation of report of sales, entry and exit validation for Level 1 Infrastructure devices belonging to the Level 2 Infrastructure

D2.0 Hardware Specification D2.1 Specifications for Station Computer

The following specification is the minimum for Station Computer. The contractor shall be responsible for choosing a computer with the necessary performance.

Table D2.1-1 Specification of Station Computer Items Specifications

Processor Intel Xeon E5-1620 3.6 GHz, 6 Core Chipset Intel C602 Chipset Memory 8 GB (2 X 4GB) ECC DDR3 Memory (4 Channel Capable)

Connectors Three SATA / SAS Connectors RAID RAID 0, 1 support via Intel C602 chipset

O.S. Disk 1TB SATA Hard Disk x 2 unit (RAID-1) Optical DVD RW Display

(Video Card) No. of Displays supported – 1 nos. x High-End Graphic Card with 2GB

Memory, dual output 1920x1080 @ 32bpp, direct x 10 support Monitor 1 x 18.5”Monitor, with HDMI/DVI input, full HD 1080p

Ports Front Ports: Two USB 2.0, microphone, headphone Ports Rear Ports: Eight USB 2.0, two USB 3.0, one serial (9-pin), one Ethernet

(RJ-45), three analog audio ports Ports Audio: High Definition (HD) Audio

Speakers Internal speaker for business audio Ethernet Ethernet: Minimum of two (2) gigabit Ethernet; 1000Base-T

Slots full-length, full-height, PCIe 3.0 x16 – 2 Nos., full-length, full-height, PCIe 3.0 x16 (x4 electrical) – 1Nos.,

Slots full-length, full-height, 32-bit PCI 2.3 – 1 Nos. half-length, full-height, PCIe 2.0 x4 – 1Nos.

Power Supply 610 watts with variable speed fan Operating System Microsoft Windows 8 Professional 64 bit preloaded or better



Items Specifications Warranty 3 Years Comprehensive 24 hours Support

D2.2 Printer for Station Computer

As part of the Station Computer the contractor shall include a set of printer for the following purposes;

• Report Generation; and • Data gathering via print out.

The following specification is the minimum for Printer. The contractor shall be responsible for choosing a printer with the necessary performance.

Table D2.2-1 Specification of Printer Items Specifications

Print Method Laser Toner Type Printer

Speed (Page Per Minute) Print speed black: Normal: Up to 16 ppm Print speed color: Normal: Up to 4 ppm

Communications Connectivity, standard 1 Hi-Speed USB 2.0

Paper Handling

Paper handling input, standard 150-sheet input tray Paper handling output, standard 50-sheet output bin Duplex printing, Manual (driver support provided) Media sizes supported: A4, A5, A6, B5 (ISO, JIS), 8k, 16k, 10 x 15 cm, postcards (JIS single and double); envelopes (DL, C5, B5); custom: 76 x 127 to 216 x 356 mm Media sizes: custom 76 x 127 to 216 x 356 mm Media types: Paper (bond, brochure, color, glossy, letterhead, photo, plain, preprinted, pre-punched, recycled, rough), transparencies, labels, envelopes, cardstock Supported media weight: 60 to 176 g/m² (plain paper); up to 220 g/m² (glossy paper)

Specification for Print paper

Print technology :4-pass color laser Processor speed : 264 MHz Memory, standard : 8 MB SDRAM, 128 MB Flash Memory, maximum : 8 MB SDRAM, 128 MB Flash



Items Specifications

Power & Operating Requirement’s

Power: 110-volt input voltage: 110 to 127 VAC (+/- 10%), 60 Hz (+/- 3 Hz); 220-volt input voltage: 220 to 240 VAC (+/- 10%), 50 Hz (+/- 3 Hz) Power consumption: 295 watts (printing), 8 watts (ready), 3.1 watts (sleep), 0.8 watts (auto-off), 0.2 watts (off) Energy efficiency: ENERGY STAR® qualified Operating temperature range: 15 to 32.5º C Operating humidity range: 20 to 70% RH

Reliability Print quality black (best) Up to 600 x 600 dpi Print quality color (best) Up to 600 x 600 dpi Duty cycle (monthly, A4) Up to 15,000 pages

D2.3 Uninterruptible Power Supply (UPS)

The UPS, which shall be installed Station Computer (SCS), shall be used to provide orderly and automatic shutdown of the SCS when a source AC power failure occurs. The UPS also shall ensure that any on-going transaction be completed before going to power failure mode. The UPS shall be able to support SCS for up to 30 minutes of operation.



Table D2.3-1 Specification of UPS Items Specifications

Input

Nominal Input Voltage 230V Input Frequency 47 - 63 Hz Input Connections IEC-320 C14 Input voltage range for main operations 175 - 295V Input voltage adjustable range for mains operation 160 - 286V

Output

Output Power Capacity 660 Watts / 1100 VA Max Configurable Power 660 Watts / 1100 VA Nominal Output Voltage 230V Output Connections (1) IEC 320 C13 (Surge Protection) (3) IEC 320 C13 (Battery Backup)



Items Specifications

Batteries & Runtime

Battery Type Maintenance-free sealed Lead-Acid battery with suspended electrolyte : leak proof Included Battery Modules 1 Typical recharge time 24 hour(s) Replacement Battery RBC33 RBC™ Quantity 1 Typical Backup Time at Half Load 15.2 minutes (330 Watts) Typical Backup Time at Full Load 5.2 minutes (660 Watts) Runtime Chart

Surge Protection and Filtering

Surge energy rating 180 Joules Filtering Full time multi-pole noise filtering : 5% IEEE surge let-through : zero clamping response time : meets UL 1449 Data line protection RJ-11 Modem/Fax/DSL protection (two wire single line)

Environmental

Operating Environment 0 - 40 °C Operating Relative Humidity 0 - 95% Operating Elevation 0-3000 meters Storage Temperature -5 - 45 °C Storage Relative Humidity 0 - 95% Storage Elevation 0-15000 meters Audible noise at 1 meter from surface of unit 45.00 dBA Online Thermal Dissipation 180.00 BTU/h

D2.4 Miscellaneous

• Cables

All cables shall be properly terminated at both end with secured clips, screws or interlocking mechanism to prevent loose connection. The cables at both ends are label with identification to prevent any mishandling during maintenance works. Cable of same type shall be grouped together where control cables and power cables shall be separated out during cabling. All AC power cables shall be separated from telecommunication cables to prevent any interference.

• Grounding

All the SCS metal parts shall be grounded to protect to prevent electrical shock to patrons using the gate. These shall include all doors, covers and panels. The grounding design and implementation shall comply with the International Electricity Regulation. The SCS also shall have grounding points which can be connected to the station main ground.

• Security

The Station computer shall be placed on a secured cabinet with proper ventilations. Software and BIOS setup must be protected by password and other source of security features that will surely secure the station computer system.



D3.0 General Specifications of the Station Computer System

Table D3.0-1 Station Computer System General Specification Items Specifications

Input Voltage 220 V+10%-15%, Power Maximum 900W SCS Communication Ethernet 10/100/1000 Mbps Environment 5-32.5 degree / 25-70% RH

Annex E Contactless Smart Card Reader/Writer (CSCR/Writer)

E1.0 General Description The Reader Component is a physical hardware that contains all Fare Media and security logic required to complete any transaction with each supported Fare Media.

The contractor shall supply the Contactless Smart Card Readers; this shall be connected to the Automatic Gates, Ticket Vending machine mounted on it. For the Pos Analyzer it shall be connected thru USB and it will be used for loading and updating of the Stored Value and Single Journey Card. There will a standalone Ticket Analyzer that will check the current status of Smart Cards.

E2.0 Hardware Specification The CSCR/ Writer shall be provided by the AFCS Contractor that integrates to the Automatic Gates, Ticket Vending Machines and Pos Analyzer-Dispensers.

• General Specifications

CPU Type – Dual CPU Architecture 1 RF & 1 Application RF CPU – ARM7 48MHz AES, 256K Flash, 64KB SRAM Application CPU - ARM7 48MHz AES, 256K Flash, 64KB SRAM On board SRAM- 512KB SRAM On Board FLASH- 2 MB Real time clock 4 LED’s 1 Buzzer 4 Input & Output SPI LCD Interface

• Security Application Module (SAM)

Quantity – 4 Support ISO7816-3 T=0 and T=1 Protocol SAM Communication Speed – 36,000 BPS Support Class A, B & C –SIM Sized microprocessor smart cards ISO 7816 Compliant Protocol Parameter Selections with SAM – 19200, 38400, 76800, 230400 Baud Rate. Can power down SAM without affecting the normal operation of other active SAM

Devices.



• RF Specifications:

Operation Frequency – 13.56 MHz (+/- 50ppm) Output Power – 1.2 Watt Maximum Bit Rate – up to 414kbps Protocols Supported

- ISO 14443 A & B - MIFARE Classic - ISO 18092 - ISO 15693 - NFC - Reading Range ISO 7816 Memory Card Type – up to 10cm - Reading Range ISO 7816 CPU Card Type – up to 8.5cm

Antenna Ports – 2 x U. FL RF Ports, Multiplexed & Alternating Antenna – Shield with Ferrite/Spacer backed and stackable

• Radio Frequency Interface Requirements Specifications

Protocol Supported – RF & CARD - ISO 14443 A & B - ISO 15693 - ISO 18091 (NFC)

Communication Range for ISO 7816 – Memory Card Type – up to 10cm Communication Range for ISO 7816 – CPU Card Type – up to 8.5cm Communication Speed – up to 424kbps Operation Frequency – 13.56MHz RF Power Output – 1 Watt maximum RF Emissions – 1000uV/m @10m. RF Field Strength – 3.4 A/m @ 0 cm RF Cable Lost – 0.03 to 0.04 dB/10cm

• Contactless Smart Card Reader/Writer Pin Assignment

The CSCR/Writer shall have the following pin assignment.

Table E2.0-1 CSCR/Writer Pin Assignment PIN Purpose Signals 01 Reset SHDN 02

Power Power GND

03 Supply (+12v) 04

RS 485 / TTL

RX - 05 RX + (TTL - Rx) 06 TX - 07 RX + (TTL - Tx) 08

TXD

09

Signal Ground 10

RXD



Annex F Active Network Devices and Structured Cabling F1.0 General Description

The Contractor shall provide a Local Area Network (LAN) to interconnect the proposed AFC SPS equipment at each station with the existing newly commissioned AFC Common Ticketing system of LRT Line 2.

The contractor shall supply and provide LAN Switch and shall be installed on a 19 inch rack at the station’s Telecommunications Equipment Room (TER) and powered from a 220 VAC 60 Hz source with UPS. It shall be grounded to a grounding bus bar at the TER in accordance with local and international codes and standards

The system shall consist of UTP/STP cabling, conduit works suitable interfaces with the Telecommunications Equipment Room (TER) rack mounted LAN equipment, connects to the Fiber Optic Transmission System backbone.

F2.0 Hardware Specification – Core Switch & Network Switch The Core Switch shall be capable of layer-2 and layer-3 switching simultaneously for IPv4 and IPv6. It shall be Stackable Ethernet workgroup switches. It must be equipped with pluggable SFP and XFP transceivers at least 4 slots available on it that support short, long and very long distances and. The Core Switch shall be hot swappable redundant fans and power supplies with a minimum of 24 Ports per Switch.

Core Switch for the new stations and also Santolan Depot, Network Switch 2 units in each new stations. The two (2) network switch will segregate the East Bound and West Bound AFCS Equipment’s (Gates & TVM’s)

It must supports fine-grained controls for quality of service (QoS) and for security including network access control (NAC), along with full support for 802.3at compliant power over Ethernet (PoE) and additional 10Gig ports for smooth expansion of existing installations where PoE+ or SFP+ -

• Minimum Specifications:

Table F2.0-1 Network Switch Specification

Specifications 19” Stackable 10GigE plug-in module / 2 x 10 Gigabit SFP+ ports 24 Port RJ 45 Hot Swappable Power Supply - 2 units on board Per-port LEDs RJ-45: PoE, link/activity SFP: link/activity SFP+: link/activity Operating temperature: 0°C to +45°C (+32°F to +113°F) • Storage temperature: –10°C to +70°C (+14°F to +158°F) •Humidity (operating and storage): 5% to 95% non-condensing cyclic temperature and humidity tests of -5°C to +55°C, 5% to 90% Relative Humidity (RH) for the duration of ~185 hours as per GR-63-CORE



Specifications Interface and speeds • 24 and 48 ports 10/100/1000, 24 port100/1000Base-X • Modular 2x 10Gig SFP+ uplinks (For Core Switch only) • Wire rate at layer 2 and layer 3 on all ports Stacking capacity (full duplex/aggregated): 20/40 Gbps Compliance and Certifications FCC CRF Title 47 Subpart B (Class A) VCCI (Class A) AS/NZS 3548 (Class A) CE marking for European countries (Class A) EN 55022:2006+A1:2007 (EMI & EMC ) EN 61000-3-2:2006 EN 61000-3-3:1995 +A2:2005 EN 55024:1998 +A1:2001 +A2:2003 (Immunity) EN 61000-4-2: 2001 EN 61000-4-3:2002 EN 61000-4-4:2004 EN 61000-4-5:2001 EN 61000-4-6:2004 EN 61000-4-8:2001 EN 61000-4-11:2004 IEEE802.3: Hi-Pot Test (2250 V DC on all Ethernet ports) US UL 60950 •IEC 60950-1:2006+A11:2009 Electric/ Health and Safety Layer-3 routing and multicast IPV 4 Multiple VRF for network segmentation and Inter-VRF route leaking •Static routing, Routing Information Protocol (RIP) v1 and v2 •Open Shortest Path First (OSPF) v2, Intermediate System-to-Intermediate System (IS-IS), Border Gateway Protocol (BGP) v4 •Generic Routing Encapsulation (GRE) and IP/IP tunneling •Graceful restart extensions for OSPF and BGP •VRRP v2 •DHCP relay (including generic UDP relay) •ARP IPV 6



Specifications Static routing •Routing Information Protocol Next Generation (RIPng) •OSPF v3 •BGP v4 (with extensions to IPv6 routing) •Graceful restart extensions for OSPF and BGP •IS-IS v6 •Multi Topology Routing in IS-IS (M-ISIS) •VRRP v3 •Neighbor Discovery Protocol (NDP) •DHCP relay for IPv6 SUPPORTED STANDARDS IEEE standards •IEEE 802.1D (STP) •IEEE 802.1p (CoS) •IEEE 802.1Q VLANs •IEEE 802.1ad Provider Bridges (Q-in-Q/ VLAN stacking) •IEEE 802.1ag (Connectivity Fault Management) •IEEE 802.1ak (Multiple VLAN Registration Protocol) • IEEE 802.1s MSTP •IEEE 802.1w RSTP •IEEE 802.1X Port Based Network Access Control

Annex G Structured Cabling for Data and Power

G1.0 General Description The AFC system is an IP Based architecture it will require a Data Cable that will be connected via IP system. CAT 6 cables for all the TVM’s, Automatic Gates, SCS and POS shall be used.

A separate line of conduit for the following shall be required as listed below:

• UTP CAT 6 for Data; • Power; and • Grounding.

G2.0 Horizontal Subsystem Cabling - RJ45 Patch Cords

The Category 6A RJ45 Patch Cords Specifications: • Flexible cable, U/UTP, 4 x 2 x 0.14 (AWG 27/7), S/FTP, 4 x 2 x 0.14 (AWG 26/7), color

gray, mounted on both sides with factory terminated IDC contacts RJ45 connectors compliant with Cat.6A ISO component standard: IEC 60603-7-51 RJ45 category 6A ISO (500MHz), shielded. For the setting up of transmission channels of Class EA with up to 4 plugged connections according to ISO/IEC 11801 ed. 2.2, June 2011, EN 50173-1, May 2011 (DIN EN 50173-1).



• Complies with Category 6A ISO requirements of the standards ISO/IEC 11801 ed. 2.2, June 2011, EN 50173-1 May 2011, as well as ANSI/TIA/EIA 568-C.2, interoperable and backwards compatible with Category 6 and Category 5e.

• Suitable for 10GBase-T applications in acc. with IEEE 802.3an up to 500 MHz. Low-smoke in acc. With IEC 61034, flame-retardant in acc. with IEC 60332-3C and halogen-free in acc. with IEC 60754-1.

• Halogen-free and heavy metal free in acc. with the EU directives RoHS and WEEE can accommodate color-coding and mechanical coding "Easy Latch", "Data Safe Lock" and "Safe-Clip". Strain-relief function in acc. with TIA/EIA 568-C.

G3.0 Patch Panels

• Cables shall be terminated at the telecommunication closets on RJ45 patch panels located inside the Telecom Room.

• All horizontal station RJ45 patch panels shall be 24 ports. • The patch panel shall have color-coded designation strips to identify cable count.

G4.0 Cable Management System

The cable management system shall be used to provide a neat and efficient means or routing and protecting cables and patch cords on telecommunication racks and enclosures. The system shall protect network investment by controlling cable bend radius, and providing cable strain relief.

G5.0 Power Cable Distribution Power cable for Automatic Gates and Ticket Vending Machine shall part of the AFCS

Contractor. Below are the lists of power requirements.

Table G5.0-1 Number of Outlets Locations: Outlets 220Volts

Automatic Gates - East Bound 7 Ticket Vending Machines East Bound 6 PAB - POS Booth East Bound 3 Automatic Gates - West Bound 7 Ticket Vending Machines West Bound 6 PAB - POS Booth East Bound 3 Main Ticket Booth

Station Computer 3 POS Machines 4

Telecom Room (For Cabinet) 4 G6.0 Grounding

Grounding cables for Automatic Gates and Ticket Vending Machine shall part of the AFCS Contractor to include the equipment cabinet inside the Telecom Room.

G7.0 Data Cabinets



The AFCS Contractor shall supply a specific Data Cabinet for Station Computer located at the ticket booth, a separate Data Cabinet for RJ 45 Patch panel, Active Network Devices and UPS inside the Telecom Room.

The Data Cabinet shall be powder coated finish with venting on doors shall have cluster hole of 4.5mm square along the length of the panel. This is to achieve maximum airflow over the entire door surface. It shall also be equipped with dual airflow ventilation and surge protected power sockets. The finished data cabinet shall be powder coated and can be color matched to the side panels, or existing cabinets.

H1.0 Performance Standards and Specifications The AFC Contractor shall comply with the requirement stipulated in the PPP for the AFC System Project for LRT, as attached in this document. (Annex B –PPP for the Automatic Fare Collection System for LRT Lines 1 & 2 and MRT 3).

Annex B – MPSS (Execution Copy)

Annex B

PPP for the Automatic Fare Collection System Project for LRT Lines 1& 2 and

MRT 3

Minimum Performance Standards and Specifications


Page 2 of 62

Table of Contents Table of Contents ....................................................................................................................... 2 1 Introduction .......................................................................................................................... 3

1.1 Definition of MPSS ....................................................................................................... 3 1.2 Purpose of the Minimum Performance Standards and Specifications .......................... 3 1.3 Functional requirements ................................................................................................ 3 1.4 Non-functional requirements ......................................................................................... 4 1.5 Components sizing ........................................................................................................ 4 1.6 Scope of MPSS .............................................................................................................. 4 1.7 Definitions ..................................................................................................................... 4

2 From Effective Date until FSA Date ................................................................................... 5 2.1 Governing Codes for Implementation ........................................................................... 5 2.2 Ticketing Concept MPSS .............................................................................................. 6 2.3 Ticketing Rules MPSS .................................................................................................. 9 2.4 Tentative Fare Matrices at Pre-FSA Date ................................................................... 15 2.5 IT Management Framework MPSS ............................................................................. 17 2.6 Security MPSS ............................................................................................................ 18 2.7 Design Life MPSS ....................................................................................................... 19 2.8 Level 0: Contactless Media MPSS .............................................................................. 19 2.9 Level 1 - 3 Generic MPSS ........................................................................................... 22 2.10 Level 1 – 3 Specific MPSS ....................................................................................... 26 2.11 Level 2 and 3 Infrastructure Systems: Station Processing Systems and Line Central Systems ................................................................................................................................. 28 2.12 Level 4 Infrastructure (Central Clearing House) MPSS ........................................... 30 2.13 Fare Media Issuer MPSS ........................................................................................... 35

3 Operational Period Requirements ...................................................................................... 37 3.1 Overview of Key Performance Indicators ................................................................... 37 3.2 Performance Measurement and Management MPSS .................................................. 57 3.3 IT Management MPSS ................................................................................................ 57 3.4 Security Management MPSS ...................................................................................... 58 3.5 Level 0: Contactless Media MPSS .............................................................................. 59 3.6 Level 1 – 3: Generic MPSS ......................................................................................... 59 3.7 Level 1: Reader Component MPSS ............................................................................ 60 3.8 Level 2 and 3 MPSS .................................................................................................... 61 3.9 Level 4 Central Clearing House MPSS ....................................................................... 61 3.10 Fare Media Issuer MPSS ........................................................................................... 62


Page 3 of 62

1 Introduction This section explains the definition and scope of this annex, and included a clarification of the sizing specifications approach.

1.1 Definition of MPSS The Minimum Performance Specifications and Standards (MPSS) comprise the minimum functional requirements and minimum non-functional requirements of the contactless Automatic Fare Collection System (AFCS) as defined in the Concession Agreement. The Concessionaire shall transform the high level MPSS to process-, system- and technical specifications on component level in the Detailed Engineering Design. It is furthermore expected from the Concessionaire to comply with – and include – common- or industry best practice and standards.

1.2 Purpose of the Minimum Performance Standards and Specifications

• Establish the minimum requirements that the Concessionaire must comply with in reference to the Project.

• Create certainty for both the Grantor and the Concessionaire in the standards of performance expected of the Concessionaire.

• To implement a system of Key Performance Indicators (KPIs) for the Concessionaire and a penalty system for non-compliance with those Indicators.

• These MPSS form part of the Concession Agreement, and the Concessionaire is required to comply with all its provisions.

1.3 Functional requirements The functional requirements describe:

• Business support, such as: o Ticketing rules

o AFCS system functions o AFCS related processes

o System and data integrity: functional controls to ensure integrity of input, processing, data and output of the AFCS system functions and processes

• Availability, such as: o Periodical backup o Contingency processes

• Security, such as: o Access control processes o Confidentiality

• Scalability: securing all of the above while accommodating all developments during the Concession Period


Page 4 of 62

1.4 Non-functional requirements The non-functional requirements describe:

• Service levels, such as: o Performance of online and offline processing

o Capacity of hardware, software and networks

• Availability, such as:

o Minimum availability of the AFCS o Maintenance windows

o Backup and contingency systems

• Security, such as: o Access control

o Confidentiality o Security patching

• Scalability. In this Annex, only relevant elements of non-functional requirements are addressed, in line with what is stated in Section 1.2 on compliance with common- or industry best practice.

1.5 Components sizing The non-functional requirements are at minimal level, normal contingency is not included. Common practice in IT sizing is to size more than 100% of actual requirements to guarantee efficient use, e.g. maximum storage used is 80% of the maximum storage capacity. Sizing shall be compliant with product vendors’ recommendations for efficient use.

1.6 Scope of MPSS The scope of the MPSS covers the minimum requirements related to the Works and Services as defined in the Concession Agreement. Any matter that is not provided for in this MPSS shall be handled in a manner that does not contravene the Concession Agreement and its Annexes.

1.7 Definitions Capitalized terms used in the MPSS but defined in the Concession Agreement shall have the same meaning as defined in the Concession Agreement, unless its context as used herein clearly indicates otherwise. Capitalized terms not defined in the Concession Agreement are described in the body of the MPSS below.


Page 5 of 62

2 From Effective Date until FSA Date This section describes the minimum performance standards and specifications on the AFCS from Effective Date until FSA Date, including all Level 1 Infrastructures, Level 2 Infrastructures, Level 3 Infrastructures, Level 4 Infrastructure, Fare Media and Fare Media Issuer systems.

2.1 Governing Codes for Implementation The laws and regulations listed below may find application to the Works but shall not be restricted to the following:

2.1.1 Electrical i. Philippine Electrical Code

ii. Electrical Engineering Law, Republic Act No. (R.A.) 7920

2.1.2 Architectural i. National Building Code of the Philippines and Its Implementing Rules and Regulations,

Presidential Decree No. (P.D.) 1096

ii. Fire Code of the Philippines and Its Implementing Rules and Regulations, R.A. 9514 iii. Code on Sanitation of the Philippines and Its Implementing Rules and Regulations, P.D.

856 iv. Accessibility Law and Its Implementing Rules and Regulations, Batas Pambansa (B.P.)

344 v. Ordinances and Regulations of Local Government Units or other Government Agencies

2.1.3 Structural

i. NSCP Vol. 1 2010 ed. (National Structural Code of the Philippines) ii. Department of Public Work and Highway (DPWH) Standard Specifications (Blue Book)

2.1.4 Mechanical and Electro-Mechanical i. Philippine Mechanical Code, R.A. 8495

ii. Electronics Engineering Law, R.A. 9292

2.1.5 Money i. General Banking Law, R.A. 8791

ii. BSP Electronic Money Regulations, Bangko Sentral ng Pilipinas (BSP) Circular 649.


Page 6 of 62

2.1.6 Privacy i. Data Privacy Act, R.A. 10173

2.1.7 Information and Communications Technology Office and National Computer Center

i. Executive Order (E.O.) 47 (2011)

ii. Executive Order 269 (2004) iii. Executive Order 322 (1971)

iv. Executive Order 222 (2000) v. Executive Order 49 (2011)

2.1.8 Environmental

i. Ecological Solid Waste Management Act, R.A. 9003

2.1.9 Concessionary i. Senior Citizen’s Act, R.A. 9994

ii. Persons with Disability Act, R.A. 9442

2.2 Ticketing Concept MPSS

1. All concepts introduced in this section shall be fully parameterized such that configuration changes can be performed by the PTOs through their Level 3 Infrastructures, or by the Concessionaire on request from a PTO or the Scheme Provider.

2. The AFCS shall support the following concepts or equivalent concepts:

2.2.1 Global Concepts & Definitions 3. A Passenger means the person that intends to use or uses public transport services

provided by the PTOs. 4. A Right to Travel means the electronic ticket that authorizes the Passenger to avail of

public transport services by the PTOs. 5. A Passenger must be able to show proof of Right to Travel to get inside the Paid Area

of the transport network. PTO employees can inspect the Right to Travel in the Paid Area.

6. The Paid Area means the section within a Station of a PTO that requires a Right to Travel to be in.

7. To obtain a Right to Travel, the Passenger must present its Fare Media to a device performing validation, such as Automatic Gates and Mobile Inspection Devices.


Page 7 of 62

8. A Fare Media is a physical device issued by a Fare Media Issuer. It contains an Application – issued by the Concessionaire or any other Accepted Issuer as application provider – that stores Right to Travel, Products and/or Stored Value, and/or identification.

9. Stored Value Media are Fare Media implementing Stored Value.

10. The Stored Value Card is a specific form factor of a Stored Value Media described in Section 2.8.2.3.

11. A Product represents a contract between the Passenger and one or more PTOs and Accepted Participants A. It is described by the rules and parameters that define its validity and the conditions under which a Right to Travel is granted.

12. A Right to Travel is obtained if the validation device (e.g. Automatic Gate) selects a valid Product and/or deducts Stored Value or Last Ride Bonus Replacement points (see Section 2.3.5).

13. Stored Value is a valid payment method to obtain a Right to Travel to avail of the public transport services of all the PTOs and Accepted Participants A. Stored Value is thus interoperable. Nothing in this provision shall be construed as limiting the use of Stored Value as payment for public transport only.

14. Single Journey Media are Fare Media implementing Single Journey Product. The Single Journey Product means the Product with associated rules and parameters that limit the Right to Travel to a single trip on a single day on a single Light Rail Line. Single Journey Media are thus non-interoperable, only accepted by a single PTO or Accepted Participant A.

15. Interoperable Products are Products accepted by more PTOs or Accepted Participants A (e.g. monthly pass valid for LRT1 and MRT3).

16. The concessionary discount is implemented as a Product providing a discount on the nominal price of a Trip as deducted from Stored Value, or as a Single Journey Product with discounted price.

17. A Concessionary Passenger is a Passenger whose characteristics make it eligible for a concessionary discount.

2.2.2 Topology Concepts The LRT1, LRT2 and MRT3 currently employ a simple topology; 3 Light Rail Lines consisting of multiple Stations with currently no Station belonging to more than one line. The Concessionaire is recommended, but not required, to implement the ticketing rules contained in this document in such a way that more complex topological concepts if already present in Concessionaire’s off the shelf components, can easily be added later on to cater for the needs of new Accepted Participants A and B.

18. The Light Rail Lines in scope of the AFCS consists of three (3) Lines: LRT1, LRT2 and MRT3.

19. A Line consists of multiple Stop-points 20. Each Stop-point reflects one Station of LRT1, LRT2 or MRT3. Note that Stop-points

for other transport modalities may be addresses, bus stops, etc. 21. Each Stop-point belongs to at least one Line

22. The topology must support a Stop-point (Common Station) belonging to multiple Lines.


Page 8 of 62

2.2.3 Travel Concepts The AFCS shall support the following Travel Concepts. 23. A Trip means an elementary move of a Passenger on a single Line. A Trip always starts

with a check-in validation (CI), and may end with a check-out validation (CO), or another check-in validation or implicitly when the temporal validity of the Right to Travel ends. The Right to Travel associated with a Trip is defined by its Product (or implicit in case of Stored Value), its temporal validity and its topological validity.

24. A Transfer is the phase between two Trips for which the same Product (or implicit for Stored Value) is valid; the Product supporting Transfer; and the duration of the phase does not exceed the Maximum Transfer Time.

25. A Journey is a chronological sequence of Trips and Transfers linked to one or more Lines.

2.2.4 Temporal Concepts The Concessionaire shall ensure that the AFCS and its ticketing rules can cope with the following parameterized concepts – meaning that fares and ticketing rules are dependent upon the following and products are defined in terms of the following: 26. Calendar Concepts

1. Day of the week (Mon/Tue/Wed/Thu/Fri/Sat/Sun) 2. Holidays

3. Weekdays (Monday – Friday) 4. Weekend days (Saturday – Sunday)

5. Calendar days (e.g. 1 April 2015) 6. Week, Month, Year

27. Day types can be combined in most ways. Calendar days are assigned to Holidays, Days of the week to Weekday and Weekend days etc.

28. Time Concepts 1. Time Periods in which each time period has a start Time and an end Time

2. Time (i.e.. hh:mm:ss) 29. Time Periods can be linked to Calendar Concepts (e.g. ‘Period Off-peak 1’ (9:00 am –

11:59 am) to ‘On-peak Days’) 30. Duration Concepts

1. Seconds 2. Minutes

3. Hours 4. Days

5. Months 6. Years

31. Validity Period Concepts


Page 9 of 62

1. Fixed Validity Period (Linked to a start Time Concept and/or Calendar Concept and an end Time Concept and/or Calendar Concept, or a start Time Concept and/or Calendar Concept and a Duration Concept)

2. Sliding Validity Period (Linked to a start Time/Day Concept (determined at first usage of the Product) and a Duration Concept)

32. The Validity Periods define the limits to the temporal validity of the Product. 33. Product Usage Concepts

1. Unlimited Product Usage means that within the Validity Period, there is no limit on the number of Trips.

2. Limited Product Usage means that within the Validity Period, the usage of the Product is limited to a number of Trips.

2.2.5 Payment Concepts 34. Prepaid Mode indicates that the fare for the transport service is paid prior to traveling. 35. Direct Paid Mode indicates that the fare of the transport service is determined at the end

of a Trip and deducted from Stored Value or from LRB points.

2.2.6 Fare Concepts The initial fare concept is as follows: 36. Stop-point to Stop-point. A matrix defines the fares from a certain Stop-point to another

Stop-point. 37. The Concessionaire shall prepare the AFCS to deal with the following additional fare

concepts: 1. Flat Fare. There is a single fare for the availing of transport service.

2. Unified Fare. Adoption of a common set of fare rules by all PTOs (see also section 2.3).

2.2.7 Last Ride Bonus (LRB) Replacement Concept

38. A Last Ride Bonus (LRB) Replacement Product allows PTOs to provide incentives to Passengers traveling on Stored Value to make use of the transport network. Revenue losses incurred by PTOs as a result of the usage of this product is borne by the PTOs.

39. The LRB Replacement Product allows Passengers to accumulate LRB Points, if earned within the LRT1, LRT2 and MRT3 networks, than only earned during a check-out validation in Direct Paid Mode, provided that the Free Exit Duration has been exceeded and the Maximum Trip Duration has not been exceeded.

40. LRB Points are at least a valid payment method for fares paid through the Direct Paid Mode.

2.3 Ticketing Rules MPSS This section specifies the overall ticketing rules for the AFCS of the PTOs. These rules do not necessarily apply to a single level, such as Level 1 Infrastructures. In a classically designed AFCS, these ticketing rules are typically implemented on Level 1 Infrastructures in their interaction with the Fare Media. In an account-based fare collection system some of these rules may be implemented in back-office systems such as Level 3 Infrastructures or Level 4 Infrastructure.


Page 10 of 62

2.3.1 Single Journey 41. Single Journey Media shall contain a Single Journey Product. 42. A Single Journey Product is specific for a Line.

43. The Single Journey Product is only valid on the day of sale. 44. The Single Journey Product is priced according to the fare matrix (Stop-point to Stop-

point) from the point of origin to the point of stated destination. 45. The Single Journey Product is valid for any Trip with a fare up to the price of the

Product. 46. A Passenger may obtain a Single Journey Media, containing one Single Journey

Product, by specifying the required destination or the ticket price. The Single Journey Product is paid through the Prepaid Mode.

47. The Single Journey Media shall be made available from Ticketing Vending Machines (TVMs) and ticket sales booths inside the Stations.

48. Unused Single Journey Media are non-refundable. 49. Unused Single Journey Media returned to ticket offices are accepted but the PTOs shall

not give credit or refunds. 50. The Automatic Gate shall always capture the Single Journey Media when exit is granted

unto the Passenger. 51. A Passenger traveling with Single Journey Media shall pay the difference between the

actual fare and the Single Journey Product price if this price is lower than the fare before exit is granted.

52. A Single Journey Product has a Sliding Validity, which means that it is a valid up to a specified number of minutes after check-in on the product. The configurable number of minutes of the Sliding Validity is 120 minutes at Pre-FSA Date.

53. If the Single Journey Media is a contactless token, the Concessionaire shall engrave it with the Fare Medium Brand and made available in distinctive colors per line.

54. If the Single Journey Media is a contactless ticket, the Concessionaire shall it make it available in distinctive colors per line and easily distinguishable from Stored Value Media.

55. At Pre-FSA Date, the fare for a specific Trip using a Single Journey Media is the same for each hour on each calendar day.

2.3.2 Stored Value 56. Stored Value Media, amongst which Stored Value Cards, shall contain reloadable

Stored Value that will reside in the Application.

57. The Stored Value Cards shall be made available from TVMs and ticket sales booths. 58. As the Stored Value facility is reloadable, it will not have to support the existing Last

Ride Bonus. 59. The lowest value of Stored Value Sales (minimum top-up value) is the lowest non-

concessionary fare on all the Lines, rounded up to the nearest Peso. 60. The minimum top-up value is configurable.


Page 11 of 62

61. All Stored Value Sales between the minimum top-up value and the maximum top-up value with an increment of Php1.00 shall be supported.

62. The balance of Stored Value on a Stored Value Media shall never be less than zero (0) and never exceed a configurable maximum, prior to Pre-FSA Date to be agreed between the Concessionaire and the Program Office. The maximum is also the maximum top-up value. The AFCS shall support a maximum top-up of at least Php25,000.

63. Direct Paid Mode, using Stored Value as payment method, shall be automatically selected during the check-in validation if no valid prepaid product is present in the Application.

64. At check-in validation in Direct Paid Mode, an Entrance Fee shall be deducted from Stored Value. A Right to Travel is granted.

65. The Entrance Fee shall initially be equal to the minimum fare on a line (taking any applicable concessionary discounts into account). The Entrance Fee is configurable between zero (0) and the minimum fare in increments of Php 0.50.

66. At check out validation in Direct Paid Mode, the Trip fare is calculated. The difference between the Trip fare and any Entrance fee levied at check-in is deducted from Stored Value.

67. The price of a Trip will be according to a fare matrix of origin and destination stations. Supported fares are multiples of Php 0.50.

68. The fare may be discounted automatically during specified time of day or day of the week. Initially, no discount exists.

69. If the Passenger has insufficient Stored Value to pay the fare at check out, the Passenger must top-up the stored value to cover the complete fare before they are allowed to exit the Paid Area.

70. If the Passenger checks out at the same Station of check-in within a configurable number of minutes from check-in (Free Exit Duration), the Entrance Fee is refunded by increasing the Stored Value.

71. At Pre-FSA Date, the Free Exit Duration is zero (0) minutes. 72. If the Passenger checks out after the temporal validity of the Right to Travel ends

(Maximum Trip Duration), a configurable penalty fare based on the duration between check-out and the end of the temporal validity, is deducted on top of the matrix based fare.

73. Passengers who transfer between Lines, with a valid Right to Travel and within the maximum allowed transfer time (Maximum Transfer Duration) and complete their journey within the Maximum Journey Duration shall qualify for an Entrance Fee discount. This is fixed discount per sequence of check-ins and check-outs after the first check-in and check-out and may be modified from time to time by the PTOs (at Level 3 Infrastructure). The initial value of the discount is zero (0).

2.3.3 Concessionary Product 74. Law governs the eligibility criteria for concessionary fares.

75. As of January 2013, there are two (2) groups of concessionary Passengers, namely a) Persons with Disabilities, and b) Senior Citizens.


Page 12 of 62

76. The AFCS shall be able to support at least six (6) different groups of concessionary Passengers, including the existing groups.

77. Concessionary Products shall only be made available from the ticket sales booth located in Stations.

78. Concessionary (discounted) Single Journey Media shall only be provided by ticket offices to Passengers with an entitlement to concessionary fares.

79. Concessionary products on Stored Value Media are only provided on a Registered Fare Media.

80. Each Passenger eligible for concessionary travel shall not have more than one Stored Value Media with a concessionary product.

81. A validation with a concessionary product (Single Journey Product or Stored Value) is audibly and/or visually distinguishable from non-concessionary validations.

82. Discounts shall be according to a fare table/matrix, or counted as a percentage of the regular fare, rounded according to the following formula: Fare_Concessionary = Round ((100% – Discount_Percentage) * Fare_Regular) where Fare_Concessionary means the concessionary fare in Pesos,

Discount_Percentage means the percentage of discount that a concessionary Passenger type receives (as per LRTA),

Fare_Regular means the non-concessionary fare for a certain trip, and Round () is one of the following functions:

1. Round-up to the nearest whole Philippine Peso, or 2. The Rounding Convention applied in LRT1 Cavite Extension and Operation &

Maintenance:

83. For completed Journeys, the discount shall be applied with rounding to each Trip of the

Journey. Entrance Fee discounts shall be calculated in the same manner.

84. Passengers who qualify for Concessionary Products shall pay the regular price to obtain a Stored Value Card in the Stations.

85. The ticket office shall be able to check whether the Passenger already has an active Concessionary Product prior to activating a new Concessionary Product on a Registered Fare Media.

86. A blocked Registered Fare Media can be unblocked at a ticket office after deregistration and removal of a present Concessionary Product.


Page 13 of 62

2.3.4 Registered Fare Media 87. Passengers who claim the right to obtain discounted travel shall register their Stored

Value Media and personal information at a ticket office or station manager by submitting a registration form. The Concessionary Product is made available to the same person at the same place no later than seven (7) days after submission of the registration form.

88. Each Passenger shall only have one (1) Registered Fare Media with a concessionary product at any time. The AFCS shall ensure this.

89. Registered Fare Media with concessionary products are blacklisted/blocked for usage within 24 hours after the Passenger notifies the Concessionaire or PTO of such loss.

90. The AFCS shall securely store the personal details submitted on registration forms along with a record of what documentary evidence was provided with the registration forms. Data entry shall be manual, i.e. typed in.

91. Personal details will comprise of, or be a subset of: name, address, home phone number, cell phone number, day time phone number, e-mail address, gender, data of birth, discount entitlement, proof of discount entitlement (e.g. ID number), expiry date of entitlement.

2.3.5 Last Ride Bonus Replacement Product 92. The Concessionaire shall implement the Last Ride Bonus Replacement (LRB) Product

on Stored Value Media. This product may become operational within the LRT1, LRT2 and MRT3 networks after a configuration change.

93. An LRB point accumulator in the LRB Product shall keep count of LRB points accumulated. The accumulation method within the LRT1, LRT2 and MRT3 networks is to be defined but shall either be points per Trip paid through Direct Paid Mode or points per Stored Value spent on Trips or Journeys.

94. The LRB accumulator shall not provide the Passenger with the ability to convert LRB points to Stored Value.

95. The LRB points will accumulate until their value is sufficient to enable the Passenger to obtain a Trip paid for with LRB points. When this occurs, the Passenger will exit the system without charge and the LRB points will be deducted accordingly. The exit gate or validator (in the case of service gate users) will indicate that LRB has been applied.

96. The calculation method for spending LRB points for PTOs fares is to be defined but shall either be a certain amount of LRB points per Trip, or a certain amount of LRB points per Peso in Trip fare.

97. The above conversion rates of LRB points may be different for each Line and may be adjusted from time to time by the PTOs.

98. LRB points accrued on Fare Media with Discount Products shall be subject to different conversion rates than with non-discounted Fare Media.

99. LRB points may or may not be interoperable between the Light Rail Lines and other Accepted Participants A and B. If the LRB points are interoperable, the AFCS Level 4 shall provide for automatic clearing and settlement of LRB points or their monetary equivalent


Page 14 of 62

100. LRB points may be accumulated through methods other than through the PTOs, but only after consent (implying a commercial agreement) with the PTOs regarding spending these points for PTOs’ transport services.

2.3.6 Products 101. It is required that Fare Media and Application shall support Products. Each Stored

Value Media shall support at least 2 (two) Products.

102. Product Use Priority – in case multiple Products are present on a Fare Media – must be configurable parameter of the Product. The Product Use Priority signals the priority for product selection during validation.

103. Product Use Priority must be configurable. At Pre-FSA Date, the Product Use Priority is as follows (from highest priority to lowest priority):

1. Period Products, employee products

2. Discount Products 3. Concessionary Products providing discount (in combination with Stored Value or

Last Ride Bones Replacement) 4. Last Ride Bonus Replacement

5. Stored Value 104. Products may be valid from issuance or from first use, or may be valid for a calendar

period such as a day, week, month or year (See Temporal Validity). 105. Products supported in the AFCS shall be inclusive of Employee Products, Period

Products and Discount Products 106. Employee Products are only made available on Registered Fare Media and provide

unlimited trips on the Lines operated by a PTO. 107. Period Products are defined as valid for unlimited Trips or capped at a maximum

number of Journeys per period. 108. Period Products are valid on a Line, or interoperable for all Lines or a combination of

Lines. 109. The AFCS functionality related to Period Products shall at least be established through a

(test) implementation of the following Period Products: 1. Product 1: unlimited Trips, validity 1 month from sale, interoperable on all three

Light Rail Lines 2. Product 2: unlimited Trips, validity 1 month from first use, only valid on LRT1

3. Product 3: unlimited Trips between 9 am – 17 pm on weekdays and during the entire weekend, validity 3 calendar months, interoperable on all three Light Rail Lines

4. Product 4: 10 Journeys per work week, valid for 4 weeks from first use, interoperable on all three Light Rail Lines

110. Discount Products shall provide a percentage discount on Trips. Rounding is to be performed according to one of the functions provided in 82.

111. Discount Products are valid on a single Line, or interoperable for all Lines or a combination thereof.


Page 15 of 62

112. For avoidance of doubt, the distinction between Discount Products and Concessionary Products are twofold:

1. Eligibility for a Concessionary Product is governed by law, eligibility to Discount Products is governed by commercial agreements between the PTO(s) and Passengers;

2. Concessionary Products are Interoperable Products; Discount Products may or may not be Interoperable Products.

113. The AFCS functionality related to Discount Products shall at least be established through a (test) implementation of the following Discount Products:

1. Product 1: 25% discount on the fare, validity 1 month from sale, interoperable on all three Light Rail Lines

2. Product 2: 40% discount on the fare during off-peak hours, valid for 1 month from sale, only valid on MRT3

2.3.7 Faulty Fare Media 114. If the Stored Value and Products on Faulty Fare Media prior to their end date are still

readable by a Point of Sales or can be reconstructed using the Concessionaire’s records, these contents shall be transferred to the new Stored Value Card through a Point of Sales.

115. Replacement of Fare Media within the guarantee period stated in the Concession Agreement (Section 6.5.a.i.5) shall not count towards the volume of Single Journey Media provided free of charge as stipulated in Section 16.5.a of the Concession Agreement or the volumes of Stored Value Cards described in Section 16.5.b of the Concession Agreement.

2.4 Tentative Fare Matrices at Pre-FSA Date

116. The following fare matrices are for reference only. The Concessionaire shall configure the AFCS at Pre-FSA Date such that the applicable fare matrices are used.

Figure 1 - LRT1 Stored Value Fare Structure


Page 16 of 62

(Source: LRTA website ; SV= P100.00 , SVdiscounted = P100.00 sold for P80.00) Figure 2- LRT1 Single Journey Fare Structure

( SV = P100.00 , SVdiscounted= P100.00 sold for P80.00)

Line 1 Stored Value Ticket Fare Matrix

Baclar

an

EdsaLibert

ad

Gil Puya

t

V. Cruz

P. Quirin

o

P. Gil

U.N. Ave

nue

Centra

l Term

inal

Carried

o

D. Jose

Bamban

g

Tayuman

Blumentrit

t

A. San

tos

R. Pap

a

5th Ave

nue

Monumento

Balintaw

ak

Rooseve

lt

Baclaran 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 14.00 14.00 14.00 14.00 15.00 15.00 15.00 15.00 15.00 19.0 20.0

Edsa 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 14.00 14.00 14.00 14.00 15.00 15.00 15.00 15.00 19.0 19.0

Libertad 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 14.00 14.00 14.00 14.00 15.00 15.00 15.00 18.0 19.0

Gil Puyat 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 14.00 14.00 14.00 14.00 15.00 15.00 18.0 18.0

V. Cruz 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 14.00 14.00 14.00 14.00 15.00 18.0 18.0

P. Quirino 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 14.00 14.00 14.00 14.00 17.0 18.0

P. Gil 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 14.00 14.00 14.00 17.0 17.0

U.N. Avenue 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 14.00 14.00 17.0 17.0

Central Terminal 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 14.00 16.0 17.0

Carriedo 14.00 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 13.00 16.0 16.0

D. Jose 14.00 14.00 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 16.0 16.0

Bambang 14.00 14.00 14.00 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 15.00 16.0

Tayuman 14.00 14.00 14.00 14.00 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 15.00 15.00

Blumentritt 15.00 14.00 14.00 14.00 14.00 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00

A. Santos 15.00 15.00 14.00 14.00 14.00 14.00 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 14.00 15.00

R. Papa 15.00 15.00 15.00 14.00 14.00 14.00 14.00 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 14.00 14.00

5th Avenue 15.00 15.00 15.00 15.00 14.00 14.00 14.00 14.00 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 13.00 14.00

Monumento 15.00 15.00 15.00 15.00 15.00 14.00 14.00 14.00 14.00 13.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 13.00 13.00

Balintawak 19.0 19.0 18.0 18.0 18.0 17.0 17.0 17.0 16.0 16.0 16.0 15.00 15.00 15.00 14.00 14.00 13.00 13.00 13.00

Roosevelt 20.0 19.0 19.0 18.0 18.0 18.0 17.0 17.0 17.0 16.0 16.0 16.0 15.00 15.00 15.00 14.00 14.00 13.00 13.00

Single Journey Tickets :

P20.00

P12.00P15.00

Line 1 Single Journey Ticket Fare Matrix

Baclar

an

EdsaLibert

ad

Gil Puya

t

V. Cruz

P. Quirin

o

P. Gil

U.N. Ave

nue

Centra

l Term

inal

Carried

o

D. Jose

Bamban

g

Tayuman

Blumentrit

t

A. San

tos

R. Pap

a

5th Ave

nue

Monumento

Balintaw

ak

Rooseve

lt

Baclaran 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 20.00 20.00

Edsa 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 20.00 20.00

Libertad 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 20.00 20.00

Gil Puyat 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 20.00 20.00

V. Cruz 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 20.00 20.00

P. Quirino 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 20.00 20.00

P. Gil 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 20.00 20.00

U.N. Avenue 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 15.00 15.00 20.00 20.00

Central Terminal 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 15.00 20.00 20.00

Carriedo 15.00 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 15.00 20.00 20.00

D. Jose 15.00 15.00 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 20.00 20.00

Bambang 15.00 15.00 15.00 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00 20.00

Tayuman 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00 15.00

Blumentritt 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00

A. Santos 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00

R. Papa 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00

5th Avenue 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 12.00 15.00 15.00

Monumento 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 12.00 12.00 12.00 12.00 15.00 15.00

Balintawak 20.00 20.00 20.00 20.00 20.00 20.00 20.00 20.00 20.00 20.00 20.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00

Roosevelt 20.00 20.00 20.00 20.00 20.00 20.00 20.00 20.00 20.00 20.00 20.00 20.00 15.00 15.00 15.00 15.00 15.00 15.00 15.00


Page 17 of 62

Figure 3- LRT2 Fare Structure

(Source: LRTA website) Figure 4- MRT3 Fare Structure

NB: fare matrices as of Feb 2013.

2.5 IT Management Framework MPSS An industry standard IT management framework – e.g. ITIL V2 or V3 – or a proprietary or non-proprietary equivalent shall have been implemented to manage AFCS service support and service delivery:

117. Service support:

Single Journey Tickets :Stored Value Tickets : ( SV2 = P100.00 , SV4 = P 100.00 and sold for P80.00)

1-3 interstations = P12.00 4-6 interstations = P13.00 7-9 interstations = P14.00 10 interstations = P15.00

SJ Tickets has the same fare deduction levels as that of SV tickets (SV2 and SV4)

Line 2 Single Journey and Stored Value Ticket Fare Matrix

Recto

Legard

a

Pureza

V.Map

a

J.ruiz

Gilmore

Betty G

o- Belm

onte

Araneta

Cubao

Anonas

Katipunan

Santolan

0 1 2 3 4 5 6 7 8 9 10

Recto 0 12.00 12.00 12.00 13.00 13.00 13.00 14.00 14.00 14.00 15.00

Legarda 1 12.00 12.00 12.00 12.00 13.00 13.00 13.00 14.00 14.00 14.00

Pureza 2 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 14.00 14.00

V.Mapa 3 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00 14.00

J.ruiz 4 13.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00 13.00

Gilmore 5 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00 13.00

Betty Go- Belmonte 6 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00 13.00

Araneta Cubao 7 14.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00 12.00

Anonas 8 14.00 14.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00 12.00

Katipunan 9 14.00 14.00 14.00 13.00 13.00 13.00 12.00 12.00 12.00 12.00

Santolan 10 15.00 14.00 14.00 14.00 13.00 13.00 13.00 12.00 12.00 12.00

Note: For SV holders, P9.00 is the fare deduction for entering and exiting the same station (e.g. when the passenger changed his mind & will not ride the train anymore)

For SJ holders, the fare for entering and exiting the same station will depend on the encoded ticket value (e.g. when the passenger changed his mind & will not ride the train anymore)

O r

i g i

n S

t a

t i o

n s

D e s t i n a t i o n S t a t i o n s

O

D e s t i n a t i o n S t a t i o n s


Page 18 of 62

1. Incident management: restore and resume service as quick as possible after service interruptions and capture all relevant incident data.

2. Problem management: analyze incident data and determine which structural improvements need to be implemented.

3. Change management: determine, define and approve all required IT system changes, plan for development and testing and implement changes with a minimum of service interruptions.

4. Release management: implement system changes in a logical order and manage and control the implementation process.

5. Configuration management: register all system components to support the above-mentioned processes.

118. Service delivery: 1. Capacity management: monitor IT capacity utilization and match IT capacity to

current and forecasted business needs. 2. Availability management: monitor IT availability and undertake corrective

measures in case service levels are not met. 3. Continuity management: define and maintain actions and processes to restore IT

services in case of disasters (e.g. flooding). 4. Service level management: define and maintain the service catalogues in line with

business needs. 5. Security management: identify security threats and vulnerabilities and take

corrective actions in case of realistic risk exposure.

2.6 Security MPSS

119. The Concessionaire shall ensure that the AFCS security is fit-for-purpose and offers security by design within the context of the complete functional and security architecture of the AFCS, amongst which:

1. The Concessionaire shall design the AFCS such that the risk of outsider and insider fraud is minimized through the security architecture, audit trails, fraud detection and prevention.

2. The AFCS shall maintain the confidentiality, integrity and/or authenticity for each of the information elements in the AFCS that require confidentiality, integrity and/or authenticity.

3. Access to AFCS system components and documentation is limited to ‘need-to-know’ and ‘need-to-process’ only. Segregation of duties (e.g. ‘create’ and ‘release’ functions) is implemented for high impact system interaction (e.g. financial-, access control- or security-related). High impact system interaction is logged and kept for audit purposes. Access authorization is auditable, i.e. standard system functions provide insight in actual access rights at any time.

4. The AFCS security implementation must be considered fit-for-purpose for the period six (6) years hence at any time during the Concession Period in order to address the following considerations:


Page 19 of 62

i. Fare Media, once issued, cannot be upgraded easily and are used for at least four (4) years;

ii. An upgrade of the AFCS security implementation has a high impact and sufficient lead-time must be taken into account.

Thus, the security implementation as used in year 1 must be found fit-for-purpose in year 1 and for the next 5 years, i.e. until year 6; and that the security implementation in year 9 must be considered fit-for-purpose in year 9 and until year 14.

5. All cryptographic protocols employed by the AFCS shall be well-established, peer-reviewed and academically endorsed protocols and associated key-lengths that are considered fit-for-purpose for the entire lifetime of the AFCS. Remark: well-established, peer-reviewed and academically endorsed protocols are i.e. those that are endorsed by e.g. NIST or ECRYPT.

120. The Concessionaire shall have implemented a Security Life-Cycle Program, through which, on a yearly basis, the Concessionaire assesses whether the security architecture and implementation of the AFCS is still fit-for-purpose, and act thereupon.

121. AFCS security shall comply with national regulations and international standards (e.g. ISO/IEC 27001).

122. The AFCS shall protect the privacy of the Passengers as detailed in the Concession Agreement Annex P (Data Collection and Reporting Obligation).

123. All components using standard third party software (e.g. Windows, databases, browsers, etc.) are kept up-to-date in terms of releases and updates (as advised by the third party supplier) in order to optimize usability and security of the components.

124. AFCS systems are hardened, e.g. no unnecessary software installed, no unnecessary user accounts, or of similar nature or kind, in order to reduce vulnerability.

2.7 Design Life MPSS The minimum design life of the AFCS components at FSA Date is as follows: 125. Level 1 – 3: ten (10) years.

126. Level 0: four (4) years for each individual Fare Media after its issuance. 127. Security Architecture & Implementation: at least six (6) years at any time during the

Concession Period.

2.8 Level 0: Contactless Media MPSS This section lists the requirements to the Fare Media.

2.8.1 Functional Requirements 128. The Concessionaire shall issue at least two types of Fare Media:

1. Stored Value Cards. 2. Single Journey Media

129. Each Fare Media shall contain an Application implementing either at least Stored Value or at most Single Journey Products.

Remark: This implies that Fare Media containing Single Journey Products will only be used for Single Journey Media. Fare Media implementing Stored Value will at least


Page 20 of 62

support Stored Value. The Application is ideally an implementation of a national or industry standard (e.g. CEPAS, VDV-KA, ITSO, Calypso, APTA-CFMS, DESFire).

2.8.2 Non-functional Requirements

2.8.2.1 Technical Requirements

130. The Fare Media are compliant to the contactless protocol suite defined in ISO/IEC 14443-1/2/3 Type A or B. Remark: Testing of ISO compliancy according to ISO/IEC 10373-6.

131. A Fare Media implementing an Application with Stored Value shall, if compliant to ISO/IEC 14443 Type A or B, also be compliant to ISO 14443-4 (T=CL). Remark: This implies that Single Journey Products may be implemented on low cost Fare Media that do not support APDU based communication. When APDUs are used, no specific command set is prescribed (such as those from ISO/IEC 7816).

132. Fare Media of the same form factor shall all be compliant to the same contactless protocol (either Type A or B).

133. An Application implementing Stored Value shall at least contain a secure rewritable area where check-in and check-out information can be stored for, amongst others, inspection and validation purposes.

134. The Proximity Coupling Device (“PCD”) means the component in a Level 1 Infrastructure and Encoder/Sorters performing the function of communicating with the Fare Media.

135. The interface between Application and PCD shall be well-defined and described to such level that third parties (such as equipment manufacturers, certification institutes) can make a PCD that can perform all functions required during the operational life time of the Application (Initialization, Validation, Inspection, Sale, Top-up etc.).

136. The functional behavior of the Application shall be well-defined and described to such level that third parties (such as equipment manufacturers, certification institutes) can make a PCD that can perform all functions required during the operational life time of the Application (Initialization, Validation, Inspection, Sale, Top-up etc.).

137. If the Application is based on a national or de-facto industry standard, then the Application shall be a direct implementation of the national or industry standard, and not a proprietary implementation derived from the national or industry standard.

2.8.2.2 Performance Requirements 138. The validation of a Fare Media (check-in or check-out) shall be performed within four

hundred (400) milliseconds. Remark: This includes terminal processing and communication time.

139. An Inspection transaction shall be performed within eight hundred (800) milliseconds. Remark: This includes terminal processing and communication time.

140. A Stored Value Sales or Product sales transaction shall be performed within eight hundred (800) milliseconds, wherein the transaction is defined as the final interactions between Fare Media and PCD after product/top-up value selection and payment for the same.

141. All Fare Media shall function within the proximity of a PCD between zero (0) millimeter and forty (40) millimeter.


Page 21 of 62

142. All Stored Value Cards shall function within the proximity of a PCD between zero (0) millimeter and seventy (70) millimeter.

2.8.2.3 Form Factor Requirements 143. Stored Value shall at least be implemented on a Stored Value Card.

Remark: This implies that the interoperable Stored Value shall be made available by PTOs on a Stored Value Card to all Passengers, but other form factors may be issued as well (e.g. watch, mobile phone, key fob) by Concessionaire through other sales channels.

144. The Stored Value Card is a Fare Media with ID-1 format according to ISO/IEC 7810. Remark: Testing of compliancy according to ISO/IEC 10373-1.

145. The Single Journey Product is implemented on Fare Media that are reused after each Trip. Remark: It is up to the Concessionaire to select the form factor of the Single Journey Media.

146. The Single Journey Media is distinguishable for each line by its color. 147. The Single Journey Media shall bear the Fare Medium Brand

148. All Stored Value Media are visually uniquely identifiable to the Passenger and PTO. Remark: This means that a unique identification number must be printed, engraved or embossed on the Fare Media.

149. All Stored Value Media shall have an end date printed, engraved or embossed on them. Beyond this date, the Concessionaire is not required to guarantee and transfer the Stored Value balance in case of Faulty Fare Media. The end date shall be at least for four (4) years after their issuance.

150. All Stored Value Media shall bear the Fare Medium Brand, including logo, in such a way that that the medium is easily recognized as accepted by PTOs

151. All Stored Value Cards and Fare Media of the same size shall bear the Fare Medium Brand, including logo and payoff in such form that at least 20% of one side of the Stored Value Cards is allocated for same logo and payoff.

2.8.2.4 Security Requirements 152. Each Application is electronically uniquely identifiable and the Application shall offer

functions to establish the authenticity of the same identifier.

153. The Concessionaire shall ensure that the Application is fit-for-purpose and offers security by design within the context of the complete functional and security architecture of the AFCS and other uses of the Application Remark: the Application and functional design may be different for Fare Media implementing Stored Value vis-à-vis Fare Media implementing Single Journey Products. In both cases, the security architecture and Application must be fit-for-purpose.

154. The implementation of Fare Media and Application shall be fit-for-purpose and offer equivalent security as the design of Fare Media and Application. Remark: E.g. Common Criteria certified Fare Media and Application.

155. In case applications other than the Application are hosted on the Fare Media, these applications shall NOT interfere with the functionality and security of the Application.


Page 22 of 62

156. The Single Journey Media shall NOT host other applications. Remark: This limitation does not apply to the Fare Medias with Stored Value.

2.9 Level 1 - 3 Generic MPSS

2.9.1 Level 1 -3 Definitions 157. The Level 1 Infrastructure consists of:

1. Automatic Gates (AG), each being either a: i. Uni-directional Gate;

ii. Bi-directional Gate; iii. Wide Gate

2. Ticket Vending Machines (TVM) 3. Complete Point of Sales including Analyzer Dispenser (PoS+AD)

4. Reader Component (RC) 5. Mobile Inspection and Validation Device (MD)

158. Level 2 Infrastructure is defined to be a Station Computer System (SCS) 159. Level 3 Infrastructure consists of:

1. Central Computer System (CCS); 2. If required, Encoder/Sorters or equivalent systems (E/S) for Single Journey Media

recycling (see 163 below). 160. Service Operating Hours:

1. LRT1: 5.00 a.m. until 11.00 p.m. 2. LRT2: 5.00 a.m. until 11.00 p.m.

3. MRT3: 5.00 a.m. until 11.00 p.m.

2.9.2 Level 1 - 3 Quantities

161. The Concessionaire shall upgrade or replace prior to FSA Date the following quantities of Level 1 to Level 3 Infrastructures for the Existing Stations of the PTO as set out below:


Page 23 of 62

PROJECT INFORMATION MEMORANDUM 31 / 55

Systems as a Service With the rise of software or functions provided as a service, this model is being copied by AFC integrators. In order to minimize the start-up costs, proponents could offer to use (redundant) capacity in an existing clearing house, and reuse the operational processes that are already in place. There are many proven AFC issuance and clearinghouses in Asia that provide the functions required of the Manila Central Clearing House System 4.5. Equipment The tables below indicate the amount of Level 1 to Level 3 systems the Proponent will upgrade/replace and maintain. Table 5- Desired AFCS equipment LRT 1

Assumed LRT1 AFCS Equipment

Station TVM AG AD SCS CCS E/S

Baclaran 2 18 6 1 0 0

Edsa 3 31 9 1 0 0

Libertad 1 16 3 1 0 0

Gil Puyat 2 20 7 1 0 0

V. Cruz 1 10 4 1 0 0

P. Quirino 1 16 3 1 0 0

P. Gil 1 10 4 1 0 0

U.N. Avenue 1 16 5 1 0 0

Central Terminal 2 16 8 1 0 0

Carriedo 1 16 5 1 0 0

D. Jose 3 23 10 1 0 0

Bambang 0 8 2 1 0 0

Tayuman 1 11 3 1 0 0

Biumentritt 1 12 5 1 0 0

A. Santos 0 10 3 1 0 0

R. Papa 0 8 2 1 0 0

5th Avenue 1 16 6 1 0 0

Monumento 3 38 10 1 0 0

Balintawak 2 18 8 1 0 0

Roosevelt 2 18 8 1 0 0

Depot 0 0 0 0 1 4

Total 28 331 111 20 1 4


Page 24 of 62

162. The Encoder/Sorter must be delivered if strictly required per Concessionaire’s system,

meaning that if the Concessionaire requires a high throughput system for re-initialization of Single Journey Media, it shall deliver the same.

163. Four (4) Encoder/Sorters shall be made available to LRT1 if the Grantor so require, at no additional cost to PTOs or Grantor. Grantor will do so no later than Effective Date.


Table 6- Desired AFCS equipment LRT 2



Recto 8 35 3 1 0 -

Legarda 9 22 2 1 0 0

Pureza 6 14 2 1 0 0

V. Mapa 3 14 2 1 0 0

J. Ruiz 3 14 2 1 0 0

Gilmore 4 14 2 1 0 0

Betty Go 3 14 2 1 0 0

Cubao 16 40 3 1 0 0

Anonas 6 20 2 1 0 0

Katipunan 12 29 4 1 0 0

Santolan 12 13 3 1 0 0

Depot 0 0 0 0 1 2

Total 82 229 27 11 1 2

Table 7- Desired AFCS equipment MRT 3

Assumed MRT3 AFCS Equipment

Station TIM AG AD SCS CCS ES

North Avenue 2 20 8 1 0 0

Quezon Avenue 3 20 7 1 0 0

GMA-Kamuning 1 10 6 1 0 0

Araneta-Cubao 3 22 8 1 0 0

Santolan-Annapolis 1 10 5 1 0 0

Ortigas 2 10 5 1 0 0

Shaw Blvd 4 20 8 1 0 0

Boni 3 10 5 1 0 0

Guadalupe 2 8 7 1 0 0

Buendia 2 6 5 1 0 0

Ayala 2 10 5 1 0 0

Magallanes 1 10 5 1 0 0

Taft Avenue 2 15 7 1 0 0

Depot 0 0 0 0 1 4

Total 28 171 81 13 1 4


Table 6- Desired AFCS equipment LRT 2



Recto 8 35 3 1 0 -

Legarda 9 22 2 1 0 0

Pureza 6 14 2 1 0 0

V. Mapa 3 14 2 1 0 0

J. Ruiz 3 14 2 1 0 0

Gilmore 4 14 2 1 0 0

Betty Go 3 14 2 1 0 0

Cubao 16 40 3 1 0 0

Anonas 6 20 2 1 0 0

Katipunan 12 29 4 1 0 0

Santolan 12 13 3 1 0 0

Depot 0 0 0 0 1 2

Total 82 229 27 11 1 2

Table 7- Desired AFCS equipment MRT 3

Assumed MRT3 AFCS Equipment

Station TIM AG AD SCS CCS ES

North Avenue 2 20 8 1 0 0

Quezon Avenue 3 20 7 1 0 0

GMA-Kamuning 1 10 6 1 0 0

Araneta-Cubao 3 22 8 1 0 0

Santolan-Annapolis 1 10 5 1 0 0

Ortigas 2 10 5 1 0 0

Shaw Blvd 4 20 8 1 0 0

Boni 3 10 5 1 0 0

Guadalupe 2 8 7 1 0 0

Buendia 2 6 5 1 0 0

Ayala 2 10 5 1 0 0

Magallanes 1 10 5 1 0 0

Taft Avenue 2 15 7 1 0 0

Depot 0 0 0 0 1 4

Total 28 171 81 13 1 4


Page 25 of 62

164. The minimum amount of E/S (if required) shall be the minimum amount required to re-encode/initialize, during a single work-shift and taking non-availability and redundancy into account, the daily amount of Single Journey Media required for that Light Rail Line’s operations, with a minimum of 2 Encoder/Sorters,

165. The tables above do not differentiate between unidirectional gates, bi-directional gates and wide gates. The Concessionaire shall replace or refurbish any gate that currently is a unidirectional gate with a unidirectional gate or a bi-directional gate; a bi-directional gate with a bi-directional gate and a wide gate with a wide gate (if any).

166. For contingency purposes, Levels 1-3 Infrastructures can function to sell and accept Single Journey Media without an operational Central Clearing House.

2.9.3 Non-functional Requirements 167. The Concessionaire shall replace or rehabilitate the existing Automatic Gates of LRT1

and LRT2 168. The Concessionaire shall replace all Automatic Gates of MRT3.

169. All Level 1 Infrastructure equipment shall contain a PCD. 170. All Level 1 Infrastructure equipment shall accept ISO 14443 both type A and type B

Fare Media. Compliance of Level 1 Infrastructure devices with ISO 14443 standards shall be tested using the ISO 10373-6 framework (Appendix H).

171. All Level 1 Infrastructure equipment shall be compliant with (inter)national standards on resistance to environmental elements, i.e. those defined in IP Code (Ingress Protection Code), NEMA Rating (National Electrical Manufacturers Association) and IEC 60529. The level of compliance shall be in line with the operating environment of the Level 1 Infrastructure devices, the required performance and availability levels, and the minimum design life required for Level 1 Infrastructure equipment.

172. All Level 1 Infrastructure equipment shall have a blacklist capability of at least one hundred thousand (100,000) Fare Media (unique identification numbers of Fare Media / Applications).

173. To ensure secured transactions even when Level 1 Infrastructure is offline to the upper levels, all validation Level 1 Infrastructure equipment must be able to successfully execute and complete offline transactions and have sufficient offline transaction storage capability for these transactions for seven (7) days of offline activity. When the connection is re-established, the Concessionaire shall ensure that transactions are transmitted to upper levels automatically.

174. The Concessionaire shall perform upgrades of the network infrastructure and other utilities in the Stations or install new utility infrastructures if that is required to meet the requirements stipulated in the Concession Agreement and its Annexes. This includes communication infrastructure between Level 1 and 2, Level 2 and 3 and Level 3 and 4.

175. The Concessionaire shall assist the PTOs to the fullest extent possible to ensure that the initial AFCS configurations – insofar Level 1-3 Infrastructures settings are concerned – are active at Pre-FSA Date and FSA Date, or configure the same itself.


Page 26 of 62

2.10 Level 1 – 3 Specific MPSS

2.10.1 Level 1 Infrastructure: Automatic Gate

2.10.1.1 Functional Requirements 176. Automatic Gates shall have a configurable gate passage grant time of thirty (30)

seconds at Pre-FSA Date. This is the maximum duration between a validation by an Automatic Gate, and the completion of the passage through the gate by the Passenger having obtained a Right to Travel. After the grant time, passage is only allowed with a new Right to Travel.

177. The Passenger throughput capacity of rehabilitated Automatic Gates is equal to or higher than the current throughput capacity of gates.

178. The Passenger throughput capacity of new Automatic Gates is thirty-five (35) Passengers per minute or higher.

2.10.2 Level 1: Reader Component

2.10.2.1 Functional Requirements

179. The Reader Component (RC) is at least responsible for all AFCS security and Fare Media functions in a Level 1 Infrastructure device.

180. The Reader Component is a physical hardware that contains all Fare Media and security logic required to complete any transaction with each supported Fare Media.

181. Ticketing rules and ticketing logic may be part of the RC.

2.10.2.2 Non-functional Requirements 182. All interfaces to the Reader Component are well described, such that qualified system

integrators and/or qualified AFCS suppliers are able to integrate the RC fully into their own Level 1 Infrastructure equipment.

183. If not all functionality can be integrated into a single physical component, then reference source code, libraries and software development tools shall be supplied at no cost for functionality required to run on Level 1 Infrastructures not supplied by the Concessionaire or its Subcontractors

184. The Concessionaire shall keep all components using standard third party software up-to-date in terms of licenses, releases and updates (as advised by the third party supplier) in order to optimize usability and security of the components.

185. The RC shall provide a remote upgrade interface (including functional specifications) in order to keep standard third party software and firmware, Fare Media layout interpretation logic, ticketing rules and logic – if any – and security software and firmware up-to-date.

186. Each interface to the RC required for an integration into a Level 1 Infrastructure device is well-described (functional, non-functional, hardware, software) and tested.

187. If the RC implements ticketing logic and ticketing rules, the Concessionaire shall either:

1. Provide a software development kit allowing qualified vendors to remove, change, and add ticketing rules and logic to the RC; or


Page 27 of 62

2. Keep the ticketing logic and rules up-to-date with all optional and mandatory ticketing rules and logic as defined by the Scheme Provider.

188. The RC must achieve a contactless transaction performance in line with the performance stated in Section 2.8.2.2.

2.10.3 Level 1 Infrastructure: Ticket Vending Machine

2.10.3.1 Functional Requirements

189. The TVM shall at least provide the following use cases: 1. Fare Media sales

2. Stored Value Sales 3. Fare Media status enquiry

190. The interface of the TVM shall support two (user selectable) languages: 1. English

2. Tagalog 191. The TVM shall at least accept as a valid payment method:

1. All types of Php 1, 5 and 10 coins in circulation per January 2015, and one additional series of coins if introduced by BSP prior to Termination Date;

2. All types of Php 20, 50 and 100 banknotes in circulation per January 2015, and one additional series of banknotes if introduced by BSP prior to Termination Date.

192. With regard to above new series of banknotes or new series of coins, the Concessionaire shall ensure that cash and/or note collection systems in the TVM are updated to accept these series no later than four (4) weeks after the introduction of the same to the general public.

193. The TVM shall be able to return cash change. 194. If the price or fare to be paid by a Passenger is not a whole number in Pesos, the cash

change returned to the Passenger may be rounded down to the nearest Peso.

2.10.4 Level 1 Infrastructure: Point of Sales + Analyzer-Dispenser

2.10.4.1 Functional Requirements 195. The PoS/AD shall at least support the following use cases:

1. Fare Media sales (Single Journey Media and Stored Value Media)

2. Product sales, including Concessionary Products and Discount Products 3. Stored Value Sales

4. Product sales 5. Inspection of Fare Media / status enquiry

6. Registration of Fare Media 7. Deregistration of Fare Media

8. Transfer of Stored Value and Products on Faulty Fare Media to a new Fare Media


Page 28 of 62

2.10.5 Level 1 Infrastructure: Mobile Inspection and Validation Device

2.10.5.1 Functional Requirements 196. The Mobile Inspection/Validation Device shall at least support the following use cases:

1. Inspection of Fare Media / status enquiry

2. Validation of Fare Media

2.11 Level 2 and 3 Infrastructure Systems: Station Processing Systems and Line Central Systems

2.11.1 Functional Requirements

2.11.1.1 Business support 197. The Concessionaire shall ensure that each Station is fitted with (an interface to) a Level

2 Infrastructure: Station Computer System.

198. The physical Station Computer System is not required to be on a Station 199. The Station Computer Systems shall allow PTO and Concessionaire personnel to

perform the following at a Station: a. Monitor and control all the Level 1 Infrastructures on same Station and;

b. Monitor and control means that at least the following functions shall be supported: i. Viewing the current setting and changing the setting of the direction of bi-

directional gates. ii. Viewing the current state and changing the operational state of Level 1

Infrastructure devices. iii. Emergency related actions (i.e. opening of all Automatic Gates in case of a

calamity). However, back-up of emergency related actions will also be provided through direct control of the Automatic Gates (without Level 2 Infrastructure dependency).

iv. Generation of report of sales, entry and exit validation for Level 1 Infrastructure devices belonging to the Level 2 Infrastructure.

200. Each PTO shall have a Level 3 Infrastructure system, connecting to Level 4 and Level 2’s.

201. The Level 3 Infrastructure system shall function as:

a. A store-and-forward hub between Level 2 and 4 Infrastructure, or b. The PTO part of a messaging broker between Level 3 and 4 Infrastructure

c. An AFCS Management Information System, providing at least but not limited to: i. Real-time and periodic (daily, weekly, monthly and yearly) reports on the

operation, availability, maintenance state of Level 1-3 Infrastructures; Passengers, Stored Value Sales, Store Value Usage, and Farebox Revenue.

d. An AFCS monitor and control system, allowing at least but not limited to: i. Setting of parameters, such as:

1. Tariff matrices


Page 29 of 62

2. Supported products, discounts

ii. Registration of devices iii. Level 2 functions

iv. Tracking of incidents and their follow-up 202. Level 3 Infrastructure shall furthermore be capable of reconciliation of Level 4

Infrastructure settlement reports with Level 3 Infrastructure transaction data. 203. Communication handled by Level 2 and 3 Infrastructures shall comprise at least:

a. Transactions for upload to Level 4 Infrastructure. b. Configuration parameters for download to Level 1 Infrastructures.

c. Level 1 Infrastructure utilization and sales (e.g. TVM) data. d. Blacklist data download to Level 1 Infrastructure.

e. Level 1-3 Infrastructures equipment monitoring data. f. Level 1-3 Infrastructures software releases and updates.

g. And furthermore any other data required for AFCS services on Level 1 Infrastructure.

204. Level 2 and 3 Infrastructures contain integrity checks to ensure that: a. All communication is from and to scheme approved and registered devices.

b. All Level 1 Infrastructure’s data is uploaded to Level 3 Infrastructure c. Level 1 Infrastructure’s parameter data is installed on all Level 1 Infrastructure

devices. d. Level 1 Infrastructure software releases and or updates are installed on all Level 1

Infrastructure devices. e. And repair functions including logging in case of anomalies.

2.11.1.2 Security 205. Physical and logical access to Level 2 and 3 Infrastructures shall be limited to

authorized employees.

206. Secure housing and hosting of Level 2 and 3 Infrastructure equipment, e.g. in a secure data center or equivalent.

207. Level 1-3 Infrastructures shall be connected via a secure network.

2.11.1.3 Availability 208. Network interruption lead to automatic re-routing of network traffic without any data

loss. Level 1 and 2 Infrastructures service interruptions lead to either automated (e.g. reboot) or manual repair actions, also here without any data loss.

209. Backup and contingency processes which ensure business continuity and no data loss in case of system-, system components- and/or utilities outages and facilities non-availability and or non-accessibility and/or disasters in case of Level 3 Infrastructures.


Page 30 of 62

210. Level 1 Infrastructures function independent from Level 2 Infrastructure for at least 7 days. The same is valid for Level 2 and 3 Infrastructures. Thus allowing time for upgrades, backups and network/system failures without hampering the operation.

2.11.1.4 Scalability 211. Load increase is caused by station extensions (Level 2 Infrastructures) and PTO/line

extensions (Level 3 Infrastructures). Scalability is in line with PTO/Line ten (10) years estimated growth.

2.11.2 Non-functional requirements

2.11.2.1 Service levels 212. Capacity shall be sufficient to guarantee that all daily and or periodical data uploads and

downloads and additional processing is completed within the same 24-hour cycle.

213. Initial capacity to support current PTO operations and planned extensions and initial capacity shall include contingency (factor 2) for Level 1-2 Infrastructures and network outages.

214. A contingency factor two (2) means that in case of recovery after delays, the system is able to process 1 additional day’s transaction load per day.

2.11.2.2 Availability 215. The daily backups are stored in a secure secondary location at a distance that guarantees

availability in case of a disaster of any kind on the primary location. 216. Built in contingency, such as redundancy to ensure services continuity in case of

system- or system component outages and facilities access- or availability issues.

2.11.2.3 Security

217. All non-application components versions (e.g. operating systems, databases, etc.) are kept compliant with their respective vendor’s releases and support policies.

218. Security patches are tested and implemented immediately` after being issued by the vendors.

2.11.2.4 Scalability

219. By architecture and design the system is set up scalable, i.e. increased production load may lead to commissioning of additional capacity, but shall not lead to changes in architecture or design.

2.12 Level 4 Infrastructure (Central Clearing House) MPSS


2.12.1.1 Business support The Central Clearing House System shall provide the following functions: 220. Validation and clearing of all transactions, including Single Journey, Stored Value,

Discounted Products, Period Products and other products. These transactions include: a. Validation, including Stored Value Usage;

b. Product Sales;


Page 31 of 62

c. Stored Value Sales;

d. Application/Fare Media issuance and sales; e. Fare Media recycle;

f. Application blocking; g. Fare Media blocking.

221. Settlement of Stored Value Usage for all Accepted Participants. All transactions that represent a value are settled on a daily basis.

1. The Concessionaire shall function as the central counterparty to all Accepted Participants A, the PTOs, Accepted Issuers and Accepted Participants B accepting or selling Stored Value.

2. Each Accepted Participant A and each PTO that provides Stored Value Sales services and thus performs a load agent role, shall hold a settlement account with authorization for the Concessionaire to perform daily settlement of the Stored Value Sales facilitated by the Accepted Participant A or PTO.

3. The Concessionaire shall on a daily basis settle all Stored Value Sales and Stored Value Usage with the PTOs, Accepted Participants A and Accepted Participants B and transfer the net settlement value to or from the settlement account maintained by the respective Accepted Participants

222. Customer Management. All relevant organizations participating in the scheme are registered in the system.

223. Reporting: An array of reports can be generated.

a. Reporting comprises internal reporting as well as external reporting to PTOs and the Grantor. Reporting to PTOs and Grantor of PTOs (such as LRTA and DOTC) covers requirements on insight in travel, sales and revenue, service and quality levels, as well as control and audit information. Reporting to DOTC/LRTA provides insight in overall scheme service- and quality levels. Beside the known reporting requirements the system furthermore provides flexible reporting functions to create and process reports on new requirements. Refer to Annex P (Data Collection and Reporting Obligation) for the minimum requirements.

224. Fraud detection and analysis. Transactions are validated according to rules specifically targeted to detect insider and outsider fraud scenarios.

225. Blacklist management. Blacklists from different roles and Fare Media Issuers are consolidated for download to Level 1 Infrastructure devices.

a. The Concessionaire shall implement blacklist and blocking functions for all Fare Media and Level 1-3 Infrastructures. Blacklisting methods should closely follow the risks that the scheme participants and Passengers are exposed to.

226. Device management. All Level 1-3 Infrastructures are registered in the system.

227. System management processes shall be in place: a. Processes to support service delivery and service support are in place, as a

minimum: b. Release management is used to implement system changes in a logical order and

to manage and control the implementation process. To ensure a continuous


Page 32 of 62

alignment with evolving requirements there may be up to 4 major releases per year, i.e. 1 release per quarter. Furthermore there will be multiple minor releases for e.g. bug fixing. Maintenance windows define timing of release implementations.

228. System- and data integrity management process shall be in place:

a. The system processes authentic transactions only. Furthermore the system has built in process control, internal control and reconciliation functions. At least:

i. Accept transactions from registered and approved Level 3 Infrastructures only.

ii. Approve transactions from registered and approved Level 2 Infrastructures only.

iii. Ensure complete transaction (file) transfer between Level 3 and Level 4 Infrastructures.

iv. Approve transactions from registered and approved Level 1 Infrastructures only.

v. Received transaction completeness checks by e.g. sequence numbers checks and e-purse value versus transaction amounts.

vi. Incomplete trip data (CI or CO missing) is stored at least 1 month for later completion.

vii. Functions for documented clean up of old and irreparable incomplete trip data.

viii. Reconciliation of sent transactions and clearing results per Level 3. ix. Reconciliation of settlement payments and clearing results per Level 3. x. Reconciliation of load agent transactions and settlement payment to Level

4. xi. Registration of scheme provider approved devices only.

xii. Auditable authorization matrix.

b. Provide exception reporting in case of mismatches and/or other anomalies. Exception reporting may lead to blacklisting of Fare Media (applications), power of decision lies with the Central Clearing House.

229. The Concessionaire shall ensure a Scheme Network is in place.

230. The Scheme Network shall: a. Connect all Accepted Participants to Level 4 Infrastructure, amongst which the

Accepted Issuer(s). b. Connect Level 4 Infrastructure to external partner, e.g. banks.

231. Failed communication is detected. The party initiating the communication is responsible for – and able and equipped to – repair in case of failed communication.

2.12.1.2 Service Levels 232. The Central Clearing House System shall have a processing cycle of at most 24 hrs. 233. All transactions received in a processing cycle must be validated and cleared not later

than during the next processing cycle 234. All transactions which are cleared in a certain processing cycle must be settled on the

same day if the clearing processing cycle is finished on a Business Day, or the earliest next Business Day for processing cycles not finished on a Business Day.


Page 33 of 62

2.12.1.3 Availability 235. Backup processes guarantee availability of backups. Proven continuity of services after

restore of a backup.

236. Disaster recovery processes that describe roles, responsibilities, procedures, etc., to be used in case of failover to secondary disaster recovery facilities, are in place.

237. The Scheme Network is monitored and service interruption lead to automatic re-routing of network traffic without any data loss.

2.12.1.4 Security 238. System access is limited to ‘need-to-know’ and ‘need-to-process’ only. 239. Segregation of duties (e.g. ‘create’ and ‘release’ functions) is implemented for high

impact system interaction (e.g. financial-, access control- or security-related). 240. High impact system interaction is logged and kept for audit purposes.

241. Access authorization is auditable, i.e. standard system functions provide insight in actual access rights at any time.

242. Access to the Scheme Network is limited to Accepted Participants, Accepted Issuers and external partners only. The Scheme Network shall ensure the confidentiality and integrity of communication, and the authenticity of connecting entities and systems.

2.12.1.5 Scalability

243. Growth of the system will be initiated by: a. Extensions by PTOs.

b. Additional Accepted Issuers c. Additional Accepted Participants A and B.

d. Micropayment services through Agents. e. Other value added services.

244. The Central Clearing House shall support not only ‘2 step transactions’ as used in check-in/check-out in public transport, but also ‘check-in only or payment’ type of transactions which are foreseen to be used in other modes of public transport and in micro payment transactions and other transaction types for value added services.


2.12.2.1 Service levels 245. Initial capacity includes contingency for Level 1-3 Infrastructures failures and network

outages.

246. The Clearing and Settlement House shall take a contingency factor of two (2) or more into account. Remark: PTOs’ Level 3 Infrastructure send in transaction files to Level 4 Infrastructure for clearing and settlement. Level 4 Infrastructure requirements are – high level – to receive and process the daily transaction load within the same 24 hours cycle. However, because the Level 4 transaction load depends heavily on availability of Level 1-3 Infrastructures and because Level 1-3 Infrastructure availability and performance are outside the Level 4 monitoring scope, a contingency factor has to be built in to guarantee performance in case of recovery after Level 1-3 or network outages. A


Page 34 of 62

contingency factor 2 means that in case of recovery after delays the system is able to process 1 additional day’s transaction load per day.

247. Furthermore this contingency factor 2 means that 2 x the daily transaction load means at most a utilization of 100% of total capacity.

248. Offline Central Clearing House processing is at most a 24 hours cycle, settlement payments are processed on the next Business Day. Central Clearing House processing is transparent for Level 1-3, i.e. does not impact Level 1-3 in any way.

249. Initially the Scheme Network capacity is sufficient to accommodate the PTOs and known extensions to their Lines. The network capacity is sufficient to accommodate a 24-hour Central Clearing House processing cycle and Fare Media Issuer operations.

250. In case reasonable access to the PTOs’ existing internet or LAN connection is insufficient to meet the Scheme Network, the Concessionaire shall ensure that a separate Scheme Network communication infrastructure is established and maintained.

2.12.2.2 Security 251. The Concessionaire shall keep all non-application components versions (e.g. operating

systems, databases, etc.) compliant with their respective vendor’s releases and support policies.

252. The Concessionaire shall test and implement security patches immediately after being issued by the vendors.

253. The Scheme Network is a secure (e.g., but not by definition, a ‘virtual private network’) network with access limited to scheme provider approved scheme participants and external partner who are crucial for scheme operations only.

254. Network connections between Fare Media Issuer and Central Clearing House shall be point-to-point only.

2.12.2.3 Availability 255. The basic and most important requirement is that Level 4 Infrastructure outages shall

have no impact on the availability of the public transport services as delivered by the public transport operators. Central Clearing House availability is transparent for Level 1-3 Infrastructure, i.e. does not impact Level 1-3 Infrastructure in any way.

256. Data shall stay available online as long as needed for operational-, audit- or compliancy purposes. Older data is archived and stored in a secure environment as long as needed for operational, audit and compliancy reasons. Archived data can be restored for online access within twelve (12) hours.

257. The daily backups shall be stored in a secure secondary location at a distance that guarantees availability in case of a disaster of any kind on the primary location.

258. In case of a major disaster (e.g. flooding, earthquake, fire) in the Level 4 central facilities, contingency guarantees that services are restored within forty eight (48) hours. During the time of Level 4 non-availability, provisional settlement continues based on historical average settlement values.

259. Failure of individual components or services (e.g. power supply and cooling) does not lead to Level 4 non-availability. Redundancy will be built in wherever necessary.

260. Recovery- and restart mechanisms and processes will ensure resumption or continuity of services without data loss.


Page 35 of 62

261. Redundancy and recovery- and restart mechanisms will be tested after every major system upgrade, and at least once per year.

262. All Scheme Network connections have secondary connections and automatic failover.

2.12.2.4 Scalability 263. The Central Clearing House is assumed to be a typical scalable modular, off-the-shelf

system. By architecture and by design the system is set up scalable, i.e. increase of the transaction load, increase of the number of scheme participants and additional use for non-public transport services may lead to commissioning of additional processing-, storage- or network capacity, but shall not lead to changes in architecture or design and shall not lead to the need to redesign or replace the applications.

264. By architecture and design the Scheme Network is set up scalable, i.e. increase of network traffic and number of connections may lead to commissioning of additional network capacity, but shall not lead to changes in network architecture and network design.

265. The Program Office may verify the Central Clearing House and Scheme Network scalability, as part of acceptance testing as per Concession Agreement.

2.13 Fare Media Issuer MPSS


2.13.1.1 Business support 266. The Fare Media Issuer shall issue the transport application on Fare Media and is owner

of the Stored Value product. The Fare Media Issuer’s systems typically consist of functional modules that support:

a. Production of physical Fare Media. b. Loading, initialization and personalization of the Application on Fare Media.

c. Upload of relevant Fare Media personalization data to the Central Clearing House system.

d. Registration and storage of Transactions e. Providing customer support services to the Passengers regarding the Fare Media

and Stored Value f. Shipment of Fare Media to the PTOs.

267. The Concessionaire shall implement the following control and reconciliation functions: a. 100% of shipped Fare Media data is uploaded to Level 4 Central Clearing House.

b. Daily reconciliation of Central Clearing House Fare Media data against Fare Media.

c. Provide exception reporting in case mismatches and or other anomalies. 268. The Concessionaire is responsible for adequate management of the float as per the

Concession Agreement.


Page 36 of 62

2.13.1.2 Security 269. Access to the Fare Media Issuer facilities and systems is limited to authorized personnel

only.

270. The Fare Media Issuer shall securely store, process and back-up all key material

2.13.1.3 Availability 271. Backup and contingency processes which ensure business continuity in case of system-,

system components- and or utilities outages and facilities non-availability and or non-accessibility.


2.13.2.1 Service levels 272. The capacity to produce Stored Value Cards and Single Journey Media shall be

sufficient to produce the amounts forecasted by the PTOs. 273. Flexibility is built in to accommodate a shift from a large part of the current 60% to

70% single journey ridership to stored value ridership. 274. The Concessionaire shall guarantee Stored Value Cards and Single Journey Media

issued by the Concessionaire for a duration of at least four (4) years after their first sales to a Passenger, or fifty thousand (50,000) transactions, whichever comes first. Remark: This includes guarantees against delamination, breaking of the antenna weld, and the like. Durability tested according to ANSI NCITS 322-2008.

275. The Concessionaire shall deliver orders for Stored Value Cards and Single Journey Media within the forecasted purchase amounts to the PTOs within three (3) weeks after ordering.

2.13.2.2 Availability 276. The daily backups are stored in a secure secondary location at a distance that guarantees

availability in case of a disaster of any kind on the primary location. 277. Built in contingency to ensure services continuity in case of system outages and

facilities access- or availability issues.

2.13.2.3 Security 278. The Concessionaire shall keep all non-application components versions (e.g. operating

systems, databases, etc.) compliant with their respective vendor’s releases and support policies.

279. The Concessionaire shall test and implement security patches immediately after being issued by the vendors.

2.13.2.4 Scalability Growth of the Fare Media Issuer utilization will come from:

• Increased number of carrier users. • New types of carriers.

280. By architecture and design the system is set up scalable, i.e. increased production load may lead to commissioning of additional capacity, but shall not lead to changes in architecture or design.


Page 37 of 62

3 Operational Period Requirements This section lists the Minimum Performance Standards and Specifications that govern the period from Pre-FSA Date until the earlier of Termination Date and Expiration Date. Where requirements listed in section 2 are repeated, they are repeated to stress the importance these obligations.

3.1 Overview of Key Performance Indicators The following tables enumerates the Penalty Point Criteria, amongst which the Key Performance Indicators (KPIs), service levels per KPI, and measurement and reporting methods.


Page 38 of 62

KPI-1: Full Integrity of Transaction Life-Cycle Description The AFCS shall provide full and end-to-end auditable integrity of the

life-cycle of a Transaction Detail Interaction between the passenger and the AFCS shall be consistent with

the interaction between the Level 0 and Level 1 Infrastructure. For example, information displayed on automatic gates or TVM should be consistent with the Transaction of the passenger. Furthermore, interaction between the passenger and the AFCS shall be consistent with the settlement values.

Measurement The Concessionaire shall record and report all issues and complaints from PTO/passenger related to: 1. possible inconsistencies between the actual Transaction as intended by the passenger/PTO and Transaction data as displayed on Levels 1-3 Infrastructure or website 2. possible inconsistencies between intended Transaction and actual Transaction 3. inconsistencies between Transaction data and settlement values This criterion is not met and Penalty Points may be awarded in case it is established, through reporting by the Concessionaire or after investigation by Grantor or PTOs, that at least one of the following incidents have occurred during the measurement period, and the cause of the incident has not been resolved within thirty (30) days: 1. there is an irreconcilable difference between the information in a Transaction as produced and reported by the different levels of the AFCS (Level 0 to Level 4 Infrastructures); or 2. there is an irreconcilable difference between the information in a Transaction as produced and the settlement of the same Transaction after successful clearing; or 3. there is an irreconcilable difference between the information of a Transaction as produced and the information about the same Transaction as presented to the passenger on the Level 1 Infrastructure.

Definitions None Penalty Points NAP 4 per month Measurement period 1 month Reporting period 1 month Reporting requirement The Concessionaire shall report on all possible inconsistencies and

efforts undertaken to resolve the incident. In case the Concessionaire detects a failure to meet the required service level, the Concessionaire shall immediately notify the Grantor, Scheme Provider and affected Accepted Participants.

Allowed Resolution time Thirty (30) calendar days Assessment & award Per measurement period and per PTO Example Multiple passengers file complaints with LRT1 and LRT2 that the

balance on their Stored Value Cards seems incorrect after a single trip.


Page 39 of 62

Investigation shows that there is an inconsistency between the concessionary trip fare and remaining stored value shown at the gate and the actual concessionary trip fare and remaining stored value. From the time of filing of complaints, one (1) month passes before the Concessionaire has resolved the incident. The Concessionaire is awarded four (4) Points per month per PTO, in total sixteen (16) Penalty Points.


Page 40 of 62

KPI-2: Adequate Security System, Management, and Processes Description The AFCS security shall continue to be fit-for-purpose and offer sufficient

confidentiality, integrity, availability and/or authenticity for each of the information systems and data elements that require confidentiality, integrity, availability and/or authenticity.

Detail None Measurement This criterion is not met and Penalty Points may be awarded in case it is

established, through reporting by the Concessionaire or after investigation by Grantors or PTOs, that at least one of the following incidents have occurred during the measurement period: 1. A service is provided to a passenger and Transactions have been generated, but the passenger has not paid for the same; 2. The Concessionaire is not able to fulfill its obligations to a passenger as stipulated in the Conditions of Use Document; 3. A person has gained unauthorized access to Level 4 Infrastructure or Fare Media Issuer systems

Definitions None Penalty Points NAP 4 per month Measurement period 1 month Reporting period 1 month Reporting requirement The Concessionaire shall report on a monthly basis the state of the security

in the AFCS. In case the Concessionaire detects any of the incidents, the Concessionaire shall immediately notify the Grantor, Scheme Provider, affected Passengers and affected Accepted Participants.

Allowed Resolution time Zero (0) minutes Assessment & award Per measurement period and per PTO Example The Concessionaire detects that a hacker has gained access to its systems and

has been made a copy of all personal details of passengers with registered Fare Media. The Concessionaire notifies the Grantors, Scheme Provider and affected passengers. The Concessionaire is awarded four (4) Penalty Points per PTO, twelve (12) Penalty Points in total.


Page 41 of 62

KPI-3: Availability of Level 1 Infrastructure Devices Description i. For all Level 1 Infrastructure devices:

- 95% per PTO from Pre-FSA Date until one (1) year after FSA Date; - 98% per PTO from 1 year after FSA Date until Termination Date. ii. For the Encoder/Sorter: 100% availability per PTO to re-encode/initialize 100% of Single Journey Media on each day.

Detail None. Measurement i. This criterion is computed as the average availability of all Level 1

Infrastructure devices maintained by the Concessionaire for a specific PTO. The availability for each Level 1 Infrastructure device is measured as follows: (Service Operating Hours – Planned Downtime Hours – Unplanned Downtime Hours)*100% / (Service Operating Hours – Planned Downtime Hours) ii. The criterion for the Encoder/Sorter is computed as follows: the number of days in a month (m), minus the number of days in same month on which the PTO has not been able to re-encode/initialize 100% of it daily usage of Single Journey Media due to non-availability of the E/S (n), divided by the number of days in a month: 100%*(m-n)/m. This criterion is not met and Penalty Points may be awarded in case at least one of the measured service levels (i) and (ii) falls short of the required service level.

Definitions Service Operating Hours mean the hours that a Station is opened for service as specified para. 160 of the MPSS. Planned Downtime Hours mean the hours of non-availability of Level 1 Infrastructure devices which have been planned and agreed upfront between Concessionaire and PTOs to carry out repairs or works on Level 1 Infrastructure devices. Unplanned Down Time means the hours of non-availability of Level 1 Infrastructure devices other than Planned Downtime Hours.

Penalty Points NAP 6 per month Measurement period 1 month Reporting period 1 month Reporting requirement The Concessionaire shall report per PTO for all Level 1 Infrastructure devices

per device type and for all Level 1 Infrastructure devices. The reports shall be available no later than five (5) days after the period concerning the report.

Allowed Resolution time Zero (0) minutes Assessment & award Per measurement period and per PTO Example During a month after FSA Date without Planned Downtime Hours, the

Unplanned Downtime Hours were such that the availability for all Level 1 Infrastructure devices of LRT1 was 97.8%, for LRT2 99.1% and for MRT3 96%. Furthermore, one Encoder/Sorter of MRT3 was out of order for two (2) days, which resulted in MRT3 being unable to reinitialize all required Single Journey Media for two (2) days.


Page 42 of 62

The Concessionaire is awarded six (6) Penalty Points for LRT1 and six (6) Penalty Points for MRT3, twelve (12) Penalty Points in total.


Page 43 of 62

KPI-4: Category 4 Incident Resolution Times Description Category 4 incidents are on average resolved or managed to a lower level

(Category 2 or 1) within one (1) hour after detection. Detail Category 4 incidents comprise of the following:

1. Incidents related to Level 1 Infrastructure devices in a Station which pose a direct risk of bodily harm to passengers or employees of the PTO; 2. Incidents that result in unavailability of Level 1 Infrastructure devices in a Station during Peak Hours; or 3. Category 2 (as defined in KPI-6) incidents that are not resolved or managed to a lower level within one (1) hour prior to Peak Hours.

Measurement For each PTO, the average resolution time (or the time needed to manage the incident to a lower category) is calculated for all incidents in Category 4. The resolution time of an incident shall be measured, as the number of minutes within Service Operating Hours, from the incident being reported until the incident is confirmed as resolved or managed to a lower level. This criterion is not met and Penalty Points may be awarded in case the average resolution time for all Category 4 incidents affecting the same PTO in the aggregate over a period of one (1) month exceeds one (1) hour.

Definitions Peak Hours shall mean the hours between 7:00 am and 9:00 a.m.; and 5:00 p.m. and 7:00 p.m., or as may be agreed from time to time by the Concessionaire and PTO. One (1) hour means sixty (60) minutes.

Penalty Points NAP 6 per month Measurement period 1 month Reporting period 1 month Reporting requirement

The Concessionaire shall report for each PTO separately. The reports shall be available no later than five (5) days after the period concerning the report.

Allowed Resolution time

1 hour

Assessment & award Per measurement period and per PTO Example During a month there is only one incident; one that leads to an inoperable

TVM. The incident is detected by the Concessionaire’s systems at 2:15 p.m., an off-peak hour, and classified as a Category 2 incident. However, at 4:00 p.m., one hour prior to Peak Hours, the incident has not yet been resolved and the incident is raised to a Category 4 incident. The incident is finally resolved at 5.05 pm. As it is the only incident during the month, the average incident resolution time for Category 4 incidents is 65 minutes. The Concessionaire is awarded six (6) Penalty Points.


Page 44 of 62

KPI-5: Category 3 Incident Resolution Times Description Category 3 incidents are on average resolved or managed to a lower

level (Category 2 or 1) within three (3) hours after detection. Detail Category 3 incidents comprise critical incidents which may seriously

impact or obstruct service continuity, passenger throughput and/or revenue collection during Off-Peak Hours. Critical incident in this criterion shall mean: 1. more than twenty percent (20%) of Level 1 Infrastructure devices in a Station are unavailable at the same time; or 2. a single Encoder/Sorter is unavailable. Any incident of Category 3 does not change or replace the incidents and associated incident resolution times of each of the Level 1 Infrastructure devices that resulted in the Category 3 incident. Category 3 is an additional incident, and resolution of the Category 3 incident by itself does not constitute a resolution of each of the incidents resulting in the Category 3 incident.

Measurement For each PTO, the average resolution time (or the time needed to manage the incident to a lower category) is calculated for all incidents in Category 3. The resolution time of an incident shall be measured, as the number of minutes within Service Operating Hours, from the incident being reported until the incident is confirmed as resolved or managed to a lower level. This criterion is not met and Penalty Points may be awarded in case the average resolution time for all Category 3 incidents affecting the same PTO in the aggregate over a period of one (1) month exceeds three (3) hours.

Definitions Off-Peak Hours shall mean the Service Operating Hours not being Peak Hours. Three (3) hours shall mean one hundred eighty (180) minutes.

Penalty Points NAP 5 per month Measurement period 1 month Reporting period 1 month Reporting requirement

The Concessionaire shall report for each PTO separately. The reports shall be available no later than 5 days after the period concerning the report.


3 hours

Assessment & award Per measurement period and per PTO Example In a Station with twenty (20) Level 1 Infrastructure devices, an incident

occurs at 10:00 a.m. which leads to three inoperable devices. At 11:00 a.m., another two devices become inoperable. Apart from the five Category 3 incidents, at 11:00 a.m. a separate incident of Category 3 is


Page 45 of 62

created because 25% of devices in the Station are unavailable. At 2:30 p.m. the first three devices are available again. The incident resolution time for the Category 3 incident is therefore 210 minutes. As the only incident of Category 3 during the month, the Concessionaire is awarded five (5) Penalty Points.


Page 46 of 62

KPI-6: Category 2 Incident Resolution Times Description Category 2 incidents are on average resolved or managed to Category 1

within six (6) hours after detection. Detail Category 2 incidents comprise those incidents leading to unavailability of

any single Level 1 Infrastructure device during Off-Peak Hours. For the avoidance of doubt, if the number of Level 1 Infrastructure devices unavailable in a Station exceeds twenty percent (20%) of the devices in same Station, an additional Category 3 incident (see KPI No. 5) is established.

Measurement For each PTO, the average resolution time (or the time needed to manage the incident to a lower category) is calculated for all incidents in Category 2. The resolution time of an incident shall be measured, as the number of minutes within Service Operating Hours, from the incident being reported until the incident is confirmed as resolved or managed to a lower level. This criterion is not met and Penalty Points may be awarded in case the average resolution time for all Category 2 incidents affecting the same PTO in the aggregate over a period exceeds six (6) hours.

Definitions Six (6) hours shall mean three hundred sixty (360) minutes. Penalty Points NAP

3 per month

Measurement period

1 month

Reporting period 1 month Reporting requirement



6 hours.

Assessment & award

Per measurement period and per PTO

Example A single incident in a month causes a TVM to be unavailable. Such incident was reported by a PTO at 9:00 a.m. An incident of Category 2 is created. At 3:30 p.m. most functionality is restored and the incident is lowered to a Category 1 incident. The Concessionaire is awarded three (3) Penalty Points because the average resolution time of Category 2 incidents is 390 minutes.


Page 47 of 62

KPI-7: Category 1 Incident Resolution Times Description Category 1 incidents are on average resolved within twelve (12) hours after

detection. Detail Category 1 incidents comprise minor incidents which are those that cause

Level 1 Infrastructure devices to be available but with reduced functionality.

Measurement For each PTO, the average resolution time (or the time needed to manage the incident to a lower category) is calculated for all incidents in Category 1. The resolution time of an incident shall be measured, as the number of minutes within Service Operating Hours, from the incident being reported until the incident is confirmed as resolved or managed to a lower level. This criterion is not met and Penalty Points may be awarded in case the average resolution time for all Category 1 incidents affecting the same PTO in the aggregate over a period of one (1) month exceeds twelve (12) hours.

Definitions Reduced functionality shall mean the failure or improper functioning of the Level 1 infrastructure device which are not required for a passenger or PTO employee to perform a Transaction between a Fare Media and the Level 1 Infrastructure device, such as but not limited to: i. failure of displays on the automatic gates; ii. failure of lights and sounds emitted by the automatic gates; or iii. throughput capacity of the automatic gates lower than the minimum. Twelve (12) hours shall mean seven hundred and twenty (720) minutes.

Penalty Points NAP

1 per month

Measurement period

1 month




12 hours

Assessment & award


Example A single incident in a month causes a TVM to be unavailable. Such incident was reported by a PTO at 9:00 a.m. An incident of Category 2 is created. At 3:30 p.m. most functionality is restored and the incident is lowered to a Category 1 incident. The Concessionaire is awarded 3 Penalty Points for the Category 2 incident. The remainder of the functionality is restored at 10:00 a.m. the following day. The average incident resolution time for Category 1 incidents is therefore 750 minutes. The Concessionaire is awarded 1 Penalty Point.


Page 48 of 62

KPI-8: Adequate Offline Processing Description Automated fare collection systems shall be able to function offline for at

least seven (7) calendar days. Detail None Measurement Unavailability of one or more Level 1 Infrastructure devices or any

Encoder/Sorter due to the inability to function offline (as a result of a lack of network connectivity or otherwise inability to communicate with Levels 2 to 4 Infrastructure), within seven (7) days from start of said communication problem shall constitute a failure to meet the required service level.

Definitions None Penalty Points NTP 3 per incident per day Measurement period

1 day


The Concessionaire shall notify the Grantors and affected PTOs immediately for each failure to reach the required service level.

Resolution time Zero (0) minutes. Assessment & award


Example Due to a communications network failure in a Station which lasted for five (5) days, some Level 1 Infrastructure devices became unavailable on the second day. The Concessionaire is awarded twelve (12) Penalty Points for the four days of unavailability.


Page 49 of 62

KPI-9: Levels 1-3 Infrastructure daily processing and completeness of Transactions Description The Levels 1-3 Infrastructure shall:

(i) process ninety-nine point ninety-nine percent (99.99%) of Transactions and relay/communicate such Transaction to the Level 4 Infrastructure during the processing cycle in which the Transactions were performed/created; and (ii) apply ninety-nine point ninety-nine percent (99.99%) of configuration changes, blacklists and software updates to Levels 1-3 Infrastructure such that they become active no later than the next calendar day following the Transaction date.

Detail To ensure that all Transactions can be cleared/settled by the Concessionaire and support the day-to-day operations of the PTO, ninety-nine point ninety-nine percent (99.99%) of all Transactions performed by the Level 1 Infrastructure device must be relayed/communicated to Level 4 Infrastructure and ninety-nine point ninety-nine percent (99.99%) of all blacklist entries, configuration and software updates generated at Level 4 Infrastructure or Level 3 Infrastructure must be applied on Level 1 Infrastructure, provided that, in case of network/connection problems, or a system failure, the Transactions, blacklist entries, configuration and software updates are ninety-nine point ninety-nine percent (99.99%) processed and applied immediately following the restoration of the network connection.

Measurement This criterion is measured by Concessionaire and PTOs as follows: The total amount of Transactions, blacklist entries, configuration and software updates per PTO that were processed in their original processing cycle or, if earlier, the next processing cycle in case of a network/system failure (m) compared with the total amount of Transactions, blacklist entries, configuration and software updates per PTO that were scheduled to be processed in the processing cycle (n). The required service level is: m ≥ 0.9999 x n And is not met in case m < 0.9999 x n

Definitions None

Penalty Points NTP 4 per day Measurement period Per incident Reporting period 1 month

Reporting requirement The Concessionaire shall report the number of incidents

Resolution time Zero (0) minutes. Assessment & award Per measurement period and per PTO Example An automatic gate reboots during service operating hours and looses 150

Transactions that were not yet communicated to Level 2 Infrastructure of a PTO that submits on this particular day 1 million Transactions. Four (4) Penalty Points are awarded.


Page 50 of 62

KPI-10: Level 4 Daily Processing and Clearing of Transactions Description The Level 4 Infrastructure shall process and clear at least ninety-nine point

ninety-nine percent (99.99%) of received Transactions. Detail Ninety-nine point ninety-nine percent (99.99%) of all transport related

Transactions received during a processing cycle from Level 3 Infrastructure must be cleared no later than the next processing cycle, provided that, offline transactions of Level 1-3 Infrastructure shall be cleared on the day the connection to Level 4 Infrastructure is achieved, provided further, that the Concessionaire shall have an equal number of days to clear Transactions as the Level 1-3 Infrastructure is offline.

Measurement The number of Transactions cleared on a day (m) compared with the numbers of Transactions received during the previous processing cycle (n). The required service level is: m ≥ 0.9999 x n And is not met in case m < 0.9999 x n where n shall not exceed the number of Transactions performed between the Fare Media and Level 1 Infrastructure during the previous processing cycle plus one additional day’s worth of backlog Transactions performed during any other processing cycle.

Definitions None Penalty Points NTP 3 per day Measurement period 1 day Reporting period 1 month Reporting requirement The Concessionaire shall report in full and include the causes for processing

delay or lost Transactions Resolution time Zero (0) minutes. Assessment & award Per measurement period and per PTO Example The network connection between all Levels 3 and Level 4 Infrastructure has been

unavailable for one (1) day. After the connection is restored, the processing capacity of the Level 4 Infrastructure is insufficient to process and clear all the Transactions within the 1-day period from the moment the connection is restored. On the first day after the connection is restored, only 99% of the backlog of Transactions is processed. The Concessionaire is awarded three (3) Penalty Points per PTO, nine (9) Penalty Points in total.


Page 51 of 62

KPI-11: Level 4 daily settlements of Transactions Description Ninety-nine point nine percent (99.9%) of transport related Transactions that are

good for settlement are settled on the Business Day on which the Transactions are cleared, or the next Business Day if the Transactions were cleared on a day other than a Business Day. Deviations from one hundred percent (100%) must be resolved in five (5) Business Days, meaning that one hundred percent (100%) of transport related Transaction that are good for settlement are settled no later than the fifth (5th) Business Day from the day on which the Transactions were cleared.

Measurement The number or value of Transactions settled in a day (m) compared with the number or value of Transactions cleared and found good for settlement on a day (n). The required service level is: m ≥ 0.999 x n and n-m = 0 within 5 Business Days And is not met in case m < 0.999 x n or n-m ≠ 0 within 5 Business Days

Definitions None Penalty Points NTP 4 per day Measurement period 1 day Reporting period 1 month Reporting requirement The Concessionaire shall report in full and include the causes for processing delay

or lost Transactions Resolution time Zero (0) minutes. Assessment & award Per measurement period and per PTO Example The Concessionaire fails to perform settlement with LRT1 for one day, and

resolved this incident two days later. The Concessionaire is awarded four (4) Penalty Points.


Page 52 of 62

KPI-12: Timeliness of Fare Media delivery Description Orders for Stored Value and Single Journey Media by the PTOs of LRT1, LRT2

and MRT3 insofar as it is within the forecasted amounts shall be delivered within three (3) weeks from date of order, provided that, additional orders of Fare Media shall be delivered within sixteen (16) weeks from date of order.

Detail Not applicable Measurement The Concessionaire shall record the date of each order and record the date of

delivery of Fare Media. This criterion is not met and Penalty Points may be awarded in case the actual delivery of Fare Media to the PTO is not within three (3) or sixteen (16) weeks from the date of order, as the case may be.

Definitions None Penalty Points NAP 5 per order Measurement period Per order Reporting period 1 month Reporting requirement The Concessionaire shall report actual delivery time per order and include causes

for late delivery. Allowed Resolution time Not applicable Assessment & award Per measurement period and per PTO Example On the first day of week 1, a PTO places an (i) order for Fare Media that is fully in

line with the forecast, and (ii) additional order that is not within the forecast. The Concessionaire delivers the first in week 5, and the second order in week 18. The Concessionaire is awarded five (5) Penalty Points per order, ten (10) Penalty Points in total.


Page 53 of 62

KPI-13: Minimize Disruption during Construction Description During performance of the Works by the Concessionaire, the impact of the

Works in the Construction Area shall not lead to unavailability of more than five percent (5%) of existing Level 1 Infrastructure devices within a Station during Service Operating Hours.

Detail This criterion is effective from the date the first Construction Area is made available to the Concessionaire until FSA Date. This criterion shall take into account the mitigating measures employed by the Concessionaire to offset disruption.

Measurement The service level per Station is the weekly average of the daily service levels. The daily service level is computed as follows: 100%*(n-p)/m Where: (m) - the total number of existing operational Level 1 Infrastructure on same Station as determined/agreed by and between the Concessionaire and Grantor prior to a Station or a part of a Station becoming a Construction Area (n) - existing Level 1 Infrastructure device capacity on the same station that is unavailable for PTOs revenue operations due to performance of the Works by the Concessionaire. Unavailable devices for this criterion are those devices which are non-available for four (4) hours or more per day during Service Operating Hours. (p) - the additional effective capacity made available by the Concessionaire to offset the disruption. Effective capacity is expressed in terms of additional throughput capacity compared to throughput capacity of existing Level 1 Infrastructure devices. This criterion is not met and Penalty Points may be awarded in case the unavailability of Level 1 Infrastructure devices in a station during Service Operating Hours is higher than five percent (5%) measured over one (1) week. In case the said unavailability of Level 1 Infrastructure devices is higher than 15%, two additional Penalty Points are awarded. Any Penalty Points awarded under this criterion shall not count towards a Concessionaire Event of Default.

Definitions None Penalty Points NAP 6 per week per Station Measurement period

1 week


The Concessionaire shall report per PTO per Station. The reports shall be available no later than 5 days after the period concerning the report


Zero (0) minutes.

Assessment & award


Example A Station with twenty (20) operational Level 1 Infrastructure devices (m=20) is


Page 54 of 62

upgraded in the course of four weeks. During each of these weeks, five devices are unavailable (n=5). However, the Concessionaire is able to restore some of the devices in its original capacity as required during peak hours through employees with mobile validators and sales booths (p=3). The service level is 100%*(5-3)/20=10%. The Concessionaire is awarded six (6) Penalty Points per week, twenty-four (24) Penalty Points for the month in total.


Page 55 of 62

KPI-14: Timely and Complete Disclosure and Investigation Description Concessionaire has the obligation to disclose possible KPI-2 incidents,

investigate possible KPI-1 and KPI-2 incidents, and disclose the results of investigation and report on KPI-1 and KPI-2 incidents.

Detail i. For KPI-1 and KPI-2, the Concessionaire shall present the result of the investigation of all reported possible inconsistencies and security incidents as listed under KPI-1 and KPI-2 as soon as possible but not later than the end of the next Reporting Period. ii. For KPI-1 and KPI-2, the Concessionaire shall disclose any incident to the Grantor and PTOs as per KPI-2 not later than the Business Day following establishment of same incident by the Concessionaire. iii. For KPI-2, the Concessionaire shall disclose any possible incident to the Grantor not later than the Business Day following detection of the incident by the Concessionaire

Measurement This criterion is not met and Penalty Points may be awarded in case: i. For any possible KPI-1 and KPI-2 incident, the Concessionaire fails to present the result of investigations into the same prior to the end of the next Reporting Period; and ii. The Grantor establishes that a KPI-2 incident was not reported to the Grantor or reported more than one (1) Business Day after the Concessionaire detected the same incident or possible incident or was informed about the possible incident. Penalty Points are awarded for each occasion on which the Concessionaire fails to meet this criterion.

Definitions None Penalty Points NAP

1 per incident

Measurement period

Per incident


The Concessionaire shall report per PTO. The reports shall be available no later than five (5) days after the period concerning the report


Zero (0) minutes.

Assessment & award


Example The Concessionaire detects a possible irregularity with Transactions that might be caused by a cloned Stored Value Card (a possible KPI-2 incident) but fails to report this the following business day to the Grantor and fails to start an investigation. Two months later a passenger informs the Concessionaire that she has been traveling with a cloned Stored Value Card for two (2) months. The Concessionaire fails to report this the next business day to the Grantor. Because of inaction, the passenger informs the Grantor of the irregularity. The Concessionaire is awarded one (1) Penalty Point for its failure to report the possible incident, one (1) Penalty Point for failure to investigate, and one (1)


Page 56 of 62

Penalty Point for failure to report the actual incident, or a total of three (3) Penalty Points.


Page 57 of 62

3.2 Performance Measurement and Management MPSS

281. The Concessionaire shall develop procedures by which all desired MPSS can be measured, and supply the Grantor all necessary resources to effectively perform such measurements for validation and monitoring purposes. Refer to Annex P (Data Collection and Reporting Obligation) for further details.

282. Performance measurement will be a fundamental practice of the Concessionaire. The Concessionaire will adopt standards, systems and processes for:

1. Identifying and tracking progress against service levels and KPI’s. 2. Identifying opportunities for improvement.

3. Comparing performance against both internal and external standards. 283. The Concessionaire will follow a ‘Plan –Do – Check – Act’ cycle to:

1. To ensure customer requirements have been met. 2. To be able to set sensible objectives and comply with them.

3. To provide standards for establishing comparisons. 4. To provide visibility and a “scoreboard” for people to monitor their own

performance level. 5. To highlight quality problems and determine areas for priority attention.

6. To provide feedback for driving the improvement effort. 284. The analysis should provide:

1. A method of assessing the effectiveness of the management of quality.

2. A means of determining problem areas, opportunities, savings and action priorities.

3.3 IT Management MPSS The implemented IT management framework shall adequately manage the following:

285. Service support: 1. Incident management: restore and resume service as quick as possible after service

interruptions and capture all relevant incident data. 2. Problem management: analyze incident data and determine which structural

improvements need to be implemented. 3. Change management: determine, define and approve all required IT system

changes, plan for development and testing and implement changes with a minimum of service interruptions.

4. Release management: implement system changes in a logical order and manage and control the implementation process. To ensure a continuous alignment with evolving requirements there may be up to 4 major releases per year, i.e. 1 release per quarter. Furthermore there will be multiple minor releases for e.g. bug fixing. Maintenance windows define timing of release implementations.

5. Configuration management: register all system components to support the above-mentioned processes.


Page 58 of 62

286. Service delivery:

1. Capacity management: monitor IT capacity utilization and match IT capacity to current and forecasted business needs.

2. Availability management: monitor IT availability and undertake corrective measures in case defined service levels are not met.

3. Continuity management: define and maintain actions and processes to restore IT services in case of disasters (e.g. flooding).

4. Service level management: define and maintain the service catalogues in line with business needs.

5. Security management: identify security threats and vulnerabilities and take corrective actions in case of realistic risk exposure.

3.4 Security Management MPSS

287. The Concessionaire shall continue to ensure that the AFCS security is fit-for-purpose and offers security by design within the context of the complete functional and security architecture of the AFCS, amongst which:

1. The AFCS shall maintain the confidentiality, integrity and/or authenticity for each of the information elements in the AFCS that require confidentiality, integrity and/or authenticity.

2. Access to AFCS system components and documentation is limited to ‘need-to-know’ and ‘need-to-process’ only. Segregation of duties (e.g. ‘create’ and ‘release’ functions) is implemented for high impact system interaction (e.g. financial-, access control- or security-related). High impact system interaction is logged and kept for audit purposes. Access authorization is auditable, i.e. standard system functions provide insight in actual access rights at any time.

3. The AFCS security implementation shall be considered fit-for-purpose at any time during the Contract Period for the next six (6) years in order to cater for the fact that:

i. Fare Media, once issued, can not be upgraded easily and are used for 4 years;

ii. An upgrade of the AFCS security implementation has a high impact and sufficient lead-time must be taken into account.

This means that the security implementation as used in year 1 must be found fit-for-purpose in year 1 for the next 5 years, i.e. until year 6; and that the security implementation in year 9 must be considered fit-for-purpose until year 14.

4. All cryptographic protocols employed by the AFCS shall be well-established, peer-reviewed and academically endorsed protocols and associated key-lengths that are considered fit-for-purpose for the entire lifetime of the AFCS. Remark: well-established, peer-reviewed and academically endorsed protocols are i.e. those that are endorsed by e.g. NIST or ECRYPT.

288. The Concessionaire shall continue to execute the Security Life-Cycle Program, through which, on a yearly basis, the Concessionaire assesses whether the security architecture and implementation of the AFCS is still fit-for-purpose, and act thereupon.


Page 59 of 62

289. AFCS security shall continue to comply with national regulations and international standards (e.g. ISO/IEC 27001).

290. The AFCS shall continue to protect the privacy of the Passengers as detailed in Annex P (Data Collection and Reporting Obligation).

291. All components using standard third party software (e.g. Windows, databases, browsers, etc.) are kept up-to-date in terms of releases and updates (as advised by the third party supplier) in order to optimize usability and security of the components.

292. AFCS systems are hardened, e.g. no unnecessary software installed, no unnecessary user accounts, etc., in order to reduce vulnerability.

3.5 Level 0: Contactless Media MPSS This section lists the requirements to the Fare Media. Any Fare Media issued must continue to adhere to the requirements listed in para. 2.8.

3.5.1 Disposal 293. The Concessionaire shall collect all Fare Media that are broken or otherwise end-of-life

on a monthly basis from LRT1, LRT2 and MRT3, and arrange the environmentally friendly disposal of these Fare Media in accordance with existing environmental laws, rules and regulations

3.6 Level 1 – 3: Generic MPSS

294. The Concessionaire is responsible for the performance and availability of Level 1 – 3 devices.

295. Excluded from the performance and availability responsibility are the PTO Processes set out in the Concession Agreement.

296. The Concessionaire shall maintain a professional Maintenance Organization, which operates the following operational processes:

1. Monitoring and Reporting. All relevant aspects of the performance of the subsystem (Levels 1-3 Infrastructures of a specific line) shall be monitored on a weekly basis, including automated measurements and visual inspection. The organization shall provide monthly reports to the PTOs on the performance of all operational processes unless indicated otherwise.

2. Service Desk. The Service Desk shall be available during Service Operating Hours for telephone calls and e-mails of competent PTO-staff. 99% of telephone calls shall be answered within 30 seconds and e-mails shall be answered within 1 day.

3. Incident Management. There shall be an online Incident Management System in which authorized staff of both the PTO and the Concessionaire can enter, prioritize and review incidents. The system shall be 24/7 available.

4. Performance Analysis. The Concessionaire and the PTO involved shall perform a joint and detailed analysis of availability, problem occurrences and problem solving on a monthly basis with a view to continuously improve both the organization as well as the relevant system elements, according the process in section 3.2.

5. Change Management. The Concessionaire shall support a change management procedure, providing impact analysis, system changes and testing.


Page 60 of 62

6. Release Management. The organization shall be capable of supporting one release of AFCS system software per quarter, four releases per year. Each release shall be fully tested before deployment. When necessary the organization must be able to roll back the release within 24 hours.

7. Configuration Management. The organization shall ensure up-to-date documentation of all system components and its configuration.

297. The PTOs involved and the Grantor shall have the right to audit and benchmark the Maintenance Organization to assess performance in this regard once per year.

298. The Concessionaire shall carry out the following obligations to ensure that traffic disruption is minimized during maintenance (planned or otherwise) and its immediate surrounding area:

1. Safe, efficient and continuous passage of Passengers is provided. 2. The traffic carrying capacity of the Stations and immediate surrounding roads and

passageways is maintained. 3. Passenger traffic congestion and disruption to public transport is minimized.

4. Passenger and pedestrian safety and, as required, alternative means of walking within or near the construction area is provided.

299. Planned downtime may be agreed upon with the PTO at discretion of the PTO on an instance-by-instance basis.

300. For each line, if relevant detailed per station, the Concessionaire and the PTO involved shall maintain up-to-date Work Instructions and training material that shall be updated continuously to improve operations.

301. The Strategic Maintenance Plan shall be updated annually. Updates require approval by the PTO involved.

302. The maintenance organization shall execute the all strategic and support processes in conformance to the Strategic Maintenance Plan.

303. The maintenance organization shall work on the basis of Service Levels as stipulated in para. 3.1 and the other requirements. The Service Levels may be updated annually after mutual agreement between the PTO involved and the Concessionaire.

304. The Concessionaire shall maintain the network components it has installed or upgraded.

3.7 Level 1: Reader Component MPSS

3.7.1 Non-functional Requirements

305. The Concessionaire shall keep all components using standard third party software (e.g. Windows) up-to-date in terms of licenses, releases and updates (as advised by the third party supplier) in order to optimize usability and security of the components.

306. The Concessionaire shall keep the RC software and hardware up-to-date

307. If the RC implements ticketing logic and ticketing rules, the Concessionaire shall either: 1. Maintain the software development kit allowing qualified vendors to remove,

change, and add ticketing rules and logic to the RC, or 2. Keep the ticketing logic and rules up-to-date with all optional and mandatory

ticketing rules and logic as defined by the Scheme Provider


Page 61 of 62

3.7.2 Operational Requirements 308. The Concessionaire shall maintain a professional Support Organization, which shall

provide 30 man-days integration support per year to end-users of the RC. This includes, but is not limited to:

a. Introductory workshop

b. Specification clarification c. Integration support

d. Integration testing 309. The Concessionaire shall deliver the RC within 16 weeks to Accepted Participants upon

their request.

3.8 Level 2 and 3 MPSS

310. Levels 2 and 3 shall continue to adhere to the requirements listed in para. 2.11.

3.9 Level 4 Central Clearing House MPSS

311. The Levels 4 Central Clearing House shall continue to adhere to the requirements listed in para 2.12.

3.9.1.1 Business support 312. The DOTC/LRTA may select a third party with relevant expertise to perform (up to

twice a year) an audit on the effectiveness of controls and related reporting. Findings are followed up and fixes are planned and implemented in the next system release and/or business processes, i.e. within maximum 6 months.


3.9.2.1 Service levels 313. In case of recovery after either Level 3 failure, Scheme Network failure or Level 4

failure, the system is able to process 1 additional day’s transaction load per day.

314. The Concessionaire shall on a daily basis: a. Perform validation of transactions received during the prior processing cycle.

b. Clear these transactions. c. Determine which transactions are good for settlement according to the validation

rules. d. Be responsible for the settlement of stored value transactions received from PTOs

and other Accepted Participants. 315. On a daily basis, the Concessionaire shall provide to each PTO:

a. Clearing reports b. Settlement reports

c. Exception reports


Page 62 of 62

3.9.2.2 Availability 316. A third party may be selected by the Grantor to verify the effectiveness of the

redundancy and recovery/restart mechanisms on a yearly basis.

3.9.2.3 Scalability 317. In order to allow additional Fare Media Issuers after the initial period of exclusivity, a

well defined interface between the Central Clearing House and Fare Media Issuers shall be made available no later than FSA Date.

3.10 Fare Media Issuer MPSS

318. The Fare Media Issuer shall continue to adhere to the requirements listed in para. 2.13.

3.10.1.1 Business support 319. The DOTC/LRTA may select a third party with relevant expertise to perform (up to

twice a year) an audit on the effectiveness of controls and related reporting. Findings are followed up and fixes are planned and implemented in the next system release and/or business processes, i.e. within maximum 6 months.

END OF DOCUMENT

B I D D I N G D O C U M E N T S

Part 3

for

Procurement of Trackwork, Electrical and Mechanical Systems and Integration with Existing Systems for LRT Line 2 – East

(Masinag) Extension Project ______________________________

Employer: Department of Transportation and

Communications

Country: The Republic of the Philippines

Project: Capacity Enhancement of Mass Transit Systems in Metro Manila

Loan No.: PH-P255

CONTENTS OF BIDDING DOCUMENTS

PART 1 – BIDDING PROCEDURES JICA Standard Bidding Documents [SBD (Design Build) Trial Version July 2015] Option A: Single-Stage Two-Envelope Bidding (Without Prequalification)

Section I. Instructions to Bidders (ITB)

Section II. Bid Data Sheet (BDS)

Section III. Evaluation and Qualification Criteria (EQC)

Section IV. Bidding Forms (BF)

Section V. Eligible Source Countries of Japanese ODA Loans (ESC) PART 2 – EMPLOYER’S REQUIREMENTS Section VI. Employer’s Requirements

- Scope of Works (SOW)

- Technical Requirements (GS & TS)

- Drawings

- Supplementary Information PART 3 – CONDITIONS OF CONTRACT AND CONTRACT FORMS Section VII. General Conditions (GC) Section VIII. Particular Conditions (PC) Section IX. Annex to the Particular Conditions - Contract Forms

PART 3 – CONDITIONS OF CONTRACT AND CONTRACT FORMS

Capacity Enhancement of Mass Trackwork, E&M Systems and Transit Systems in Metro Manila, Integration with Existing Systems LRT Line 2 - East (Masinag) Extension Project

PART 3 - SECTION VII

GENERAL CONDITIONS

The General Conditions governing this Contract are the Standard General Conditions of Contract set forth in Part 3, Section VII of the Standard Bidding Documents for Procurement of Electrical and Mechanical Plant, and for Building and Engineering Works, Designed by the Contractor (Trial Version) published by JICA in July, 2015. Those General Conditions of Contract are available on the JICA’s web site shown below: http://www.jica.go.jp/english/our_work/types_of_assistance/oda_loans/ A copy of these General Conditions is not attached to these Bidding Documents/this Contract.

http://www.jica.go.jp/english/our_work/types_of_assistance/oda_loans/

Section VII - General Conditions December 2015


Page – GC - 1

Section VII. General Conditions (GC)

Notes on General Conditions

The Conditions of Contract comprise two parts:

(a) Standard General Conditions – GC (Section VII of the Bidding Documents); and

(b) Particular Conditions – PC (Section VIII of the Bidding Documents).

The General Conditions set forth in Part 3, Section VII of these Standard Bidding Documents for Procurement of Electrical and Mechanical Plant, and for Building and Engineering Works, Designed by the Contractor (Trial Version) issued by JICA in July 2015 (hereinafter referred to as “Standard GC”), are based on Conditions of Contract for Plant and Design Build prepared and copyrighted by the International Federation of Consulting Engineers (Fédération Internationale des Ingénieurs-Conseils, or FIDIC), FIDIC 1999, all rights reserved.

The use of these Standard GC, in all Bidding Documents/Contracts for Procurement of Electrical and Mechanical Plant, and for Building and Engineering Works, Designed by the Contractor financed by Japanese ODA Loans is required, and they shall be used without any modification.

The GC in this Section, read in conjunction with the Particular Conditions in Section VIII and other documents listed therein, should be a complete document expressing all the rights and obligations of the contracting Parties.

Any amendments and additions to the General Conditions, specific to the Contract in hand, should be introduced in the Particular Conditions. A number of such Particular Conditions, applicable to the above Conditions of Contract, are included in Section VIII.

The Particular Conditions take precedence over the General Conditions—see Sub-Clause 1.5, Priority of Documents, in the General Conditions.

The Particular Conditions (PC) complement the General Conditions (GC) to specify data and contractual requirements linked to the special circumstances of the country, the Employer, the Engineer, the sector, the overall project, and the Works. It is good practice to have a list of tax and custom regulations applicable in the country, to be provided as non-binding general information, attached to the Bidding Documents.

Part A, the Contract Data of the PC, includes data to complement GC in a manner similar to the way in which the Bid Data Sheet complements the Instructions to Bidders.

Part B, the Specific Provisions of the PC should specify country- or project-specific provisions for PC in each case.

Whoever drafts the PC should be thoroughly familiar with the provisions of the GC and with any specific requirements of the Contract. Legal advice is recommended when amending provisions or drafting new ones. Note that the PC provisions take precedence over those in the GC.

Clause numbers in the PC correspond to those in the GC.


PART 3 - SECTION VIII PARTICULAR CONDITIONS


Section VIII. Particular Conditions

Notes on Particular Conditions

The Particular Conditions (PC) complement the General Conditions (GC) to specify data and contractual requirements linked to the special circumstances of the country, the Employer, the Engineer, the sector, the overall Project and the Works. Whenever there is a conflict, the provisions herein shall prevail over those in the GC.

Part A, Contract Data of the PC, includes data to complement the GC in a manner similar to the way in which the Bid Data Sheet complements the Instructions to Bidders.

Part B, the Specific Provisions of the PC should specify country- or project-specific provisions for PC in each case.

Clause numbers in the PC correspond to those in the GC.


Section VIII-Particular Conditions of Contract Page-PC-1 December 2015

Particular Conditions (PC) Part A - Contract Data

Conditions of Contract Sub-Clause Data Employer’s name and address

1.1.2.2 & 1.3 Department of Transportation and Communications (DOTC) Address: Unit 165, 16th Floor, The Columbia Tower, Ortigas Avenue, Barangay Wack-Wack, Mandaluyong City, 1555 Philippines

Engineer’s name and address

1.1.2.4 & 1.3 CMX Consortium Address: 3rd Floor, Keystone Building, 220 Sen. Gil J. Puyat Avenue, Makati City, Philippines

Bank’s name 1.1.2.11 Japan International Cooperation Agency (JICA)

Borrower’s name 1.1.2.12 The Government of the Republic of the Philippines

Time for Completion 1.1.3.3 Eighteen (18) months Defects Notification Period 1.1.3.7 Two (2) years Sections 1.1.5.6 None Electronic transmission systems

1.3 Not Applicable.

Governing Law 1.4 Laws of the Republic of Philippines Ruling language 1.4 English Language for communications

1.4 English

Engineer’s Duties and Authority

3.1(B)(ii) All variations resulting in an increase of the Accepted Contract Amount in excess of one percent (1%) shall require approval of the Employer before taking action by the Engineer (PC Sub-Clause 13.1).

Performance Security 4.2 'The Performance Security will be in the form of a "demand guarantee" or "performance bond" in the amount(s) of ten (10) percent of the Accepted Contract Amount and in the same currency(ies) of the Accepted Contract Amount. Performance Security of this contract is in accordance with the ICC Publication No.758, the 6th paragraph, "The Employer shall return the Performance Security to the Contractor within 21 days after receiving a copy of the Performance Certificate" is deleted.

General Design Obligations 5.1 Period for notifying errors, faults and



Conditions of Contract Sub-Clause Data defects in the Employer’s Requirements: Twenty eight (28) days from Commencement Date

Normal working hours 6.5 Any eight (8) hours single shift between 7 AM to 7 PM

Delay damages for the Works

8.7 0.02% of the Contract Price per day

Maximum amount of delay damages

8.7 Ten percent (10%) of the final Contract Price

Provisional Sums 13.5.(b)(ii) Fifteen percent (15%) Total advance payment 14.2 Fifteen percent (15%) of the Accepted

Contract Amount payable in the currencies and proportions in which the Accepted Contract Amount is payable.

Repayment amortization rate of advance payment

14.2(b) Twenty percent (20%)

Percentage of Retention 14.3(c) Ten Percent (10 %) Limit of Retention Money 14.3(c) Ten percent (10%) of the Accepted

Contract Amount Plant and Materials

14.5(b)(i) Sub-Clause 14.5 does not apply.

14.5(c)(i) Sub-Clause 14.5 does not apply. Minimum Amount of Interim Payment Certificates

14.6 One percent (1%) of the Accepted Contract Amount

Maximum total liability of the Contractor to the Employer

17.6 The product of one (1) times the Accepted Contract Amount

Periods for submission of insurance: a. evidence of insurance. b. relevant policies

18.1

a. Fourteen (14) days b. Twenty eight (28) days

Maximum amount of deductibles for insurance of the Employer's risks

18.2(d) Maximum amount of deductibles per occurrence shall not exceed Five Million Philippine Pesos (Php 5,000,000.00).

Minimum amount of third party insurance

18.3 One Hundred Million Japanese Yen (JPY 100,000,000.00) for any one (1) incident in the Philippines with number of incidents unlimited.

Date by which the DB shall be appointed

20.2 Twenty eight (28) days after the Commencement Date

The DB shall be comprised of

20.2 Three (3) members

List of potential DB sole 20.2 None



Conditions of Contract Sub-Clause Data members Appointment (if not agreed) to be made by

20.3 President of FIDIC



Particular Conditions – B Specific Provisions

Definitions Listed Alphabetically

Delete “1.1.1.10 Schedule of Guarantees”.

Sub-Clause 1.1.1.10 The Contract

Delete Sub-Clause 1.1.1.10 and substitute:

“Schedule of Payments” means the document so named (if any) which is comprised in the Schedules.”

Sub-Clause 1.1.5.5 Works and Goods (Plant)

“’Plant’ means the apparatus, machinery and vehicles intended to form or forming part of the Permanent Works, including vehicles purchased for the Employer and the Employer’s Personnel and relating to the construction or operation of the Works”.

Sub-Clause 4.1 Contractor’s General Obligations

Insert as third paragraph: “The Contractor shall provide Project service vehicles, including drivers, fuel and consumables, maintenance and required comprehensive insurance, for the exclusive use of the Employer’s Personnel, including but not limited to the PMO and the Engineer, as specified in the Employer’s Requirements, General Specifications 16.0.”

Sub-Clause 6.2 Rates of Wages and Conditions of Labour

Insert as third and fourth paragraphs: “(1) The Government of the Republic of the Philippines shall, by itself

or through its executing agency, assume all fiscal levies and taxes imposed in the Republic of the Philippines on the Japanese employees engaged in the implementation of the Project with respect to their personal income derived from Japanese companies operating as suppliers and contractors for the implementation of the Project.

(2) In connection with such tax assumption, the Government of the Republic of the Philippines or its executing agency shall be responsible for the liquidation or settlement of such fiscal levies, duties, taxes and other similar charges.”

Sub-Clause 6.6 Facilities for Staff and Labour

Insert as second paragraph: “The Contractor shall purchase new, provide and maintain office equipment, supplies and consumables，and personal protection equipment (PPE) for the Employer’s/Engineer’s existing offices as specified in the Employer’s Requirements, General Specifications 16.1.”



Sub-Clause 7.3 Inspection Sub-Clause 9.1 Contractor’s Obligations Sub-Clause 13.1 Right to Vary

Insert as last paragraph “Provision for Inspection or Verification of Works in a Foreign Country: Contractor shall provide all travel, accommodation and expenses for the Employer’s/Engineer’s personnel to visit the Contractor’s manufacturing/fabrication plant to inspect or verify its capability to manufacture/supply the specified type, quality and quantity of E&M equipment in a foreign country as specified in the Employer’s Requirements, General Specifications 16.2.” The fourth paragraph of this Sub-Clause shall be read as follows:: “During trial operation, when the Works are operating under stable conditions, the Contractor shall give notice to the Engineer that the Works are ready for any other Tests on Completion, including performance tests to demonstrate whether the Works conform with criteria specified in the Employer’s Requirements.”

Delete Sub-Clause 13.1 (iv) (referring to Schedule of Guarantees).

Sub-Clause 14.1 The Contract Price

Insert after (d): (1) “Notwithstanding the provision of Sub-Clause 14.1 subparagraph

(b), the Government of the Republic of the Philippines shall, by itself or through its executing agency, assume: (a) all duties and related fiscal charges imposed in the Republic of

the Philippines on the Japanese companies operating as suppliers and contractors with respect to the import and re-export of their own materials and equipment needed for the implementation of the Project; and

(b) all fiscal levies and taxes imposed in the Republic of the Philippines on the Japanese companies operating as suppliers and contractors with respect to the payment carried out for and the income accruing from the supply of the products and/or services required for the implementation of the Project; and

(c) all fiscal levies and taxes imposed in the Republic of the Philippines on the Japanese employees engaged in the implementation of the Project with respect to their personal income derived from Japanese companies operating as suppliers and contractors for the implementation of the Project.

(2) In connection with such tax assumption, the Government of the Republic of the Philippines or its executing agency shall be responsible for the liquidation or settlement of such fiscal levies, duties, taxes and other similar charges.”

PART 3 - SECTION IX ANNEX TO THE PARTICULAR

CONDITIONS - CONTRACT FORMS

Section IX. Annex to the Particular Conditions - Contract Forms

Table of Forms

Letter Of Acceptance 1

Contract Agreement 2

Schedules 4

Contractor’s Proposal 5

Performance Security 6

Advance Payment Security 10

Retention Money Security 12


Section IX. Contract Forms Page-CF-1 December 2015

Letter of Acceptance [Insert letterhead paper of the Employer]

[Insert date] To: [Insert name and address of the Contractor]

This is to notify you that your Bid dated [insert date] for execution of Procurement of Trackwork, Electrical and Mechanical Systems and Integration with Existing Systems for LRT Line 2 – East (Masinag) Extension Project and [identification number, as given in the Contract Data]for the Accepted Contract Amount of the equivalent of [insert amount in words and figures] [insert name of currency], as corrected and modified in accordance with the Instructions to Bidders, is hereby accepted by our Agency. You are requested to furnish the Performance Security within twenty eight (28) days in accordance with the Conditions of Contract, using for that purpose one of the Performance Security Forms included in Section IX, Annex to the Particular Conditions - Contract Forms, of the Bidding Documents

Authorized Signature: Name and Title of Signatory: Name of Agency: Attachment: Contract Agreement



Contract Agreement THIS AGREEMENT made the [insert day] day of [insert month], [insert year], between Department of Transportation and Communications (DOTC) of the Republic of the Philippines (hereinafter “the Employer”), of the one part, and [insert name of the Contractor] (hereinafter “the Contractor”), of the other part:

WHEREAS the Employer desires that the Works known as Capacity Enhancement of Mass Transit Systems in Metro Manila should be executed by the Contractor, and has accepted a Bid by the Contractor for the execution and completion of these Works and the remedying of any defects therein,

The Employer and the Contractor agree as follows:

1. In this Agreement words and expressions shall have the same meanings as are respectively assigned to them in the Contract documents referred to.

2. The following documents shall be deemed to form and be read and construed as part of this Agreement. This Agreement shall prevail over all other Contract documents. (i) the Letter of Acceptance; (ii) the Letter of Bid ; (iii) the addenda Nos [insert addenda numbers, if any] (if any); (iv) the Particular Conditions ; (v) the General Conditions; (vi) the Employer’s Requirements; (vii) the completed Schedules; (viii) the Contractor’s Proposal and any other documents forming part of the Contract;

and (ix) the Acknowledgement of Compliance with Guidelines for Procurement under

Japanese ODA Loans. 3. In consideration of the payments to be made by the Employer to the Contractor as specified in

this Agreement, the Contractor hereby covenants with the Employer to execute the Works and to remedy defects therein in conformity in all respects with the provisions of the Contract.

4. The Employer hereby covenants to pay the Contractor in consideration of the execution and completion of the Works and the remedying of defects therein, the Contract Price or such other sum as may become payable under the provisions of the Contract at the times and in the manner prescribed by the Contract.

IN WITNESS whereof the parties hereto have caused this Agreement to be executed in accordance with the laws of [insert the laws of the borrowing country] on the day, month and year specified above.

Signed by _______________________ Signed by ______________________

for and on behalf of the Employer for and on behalf the Contractor



in the presence of in the presence of

Witness, Name, Signature, Address, Date Witness, Name, Signature, Address, Date



(List the items comprising Schedules. Typical Schedules are as followings)

SCH 1: Schedule of Prices

Note: Insert Schedule of Prices submitted with the Letter of (Price) Bid and finalized at signing of the Contract.

SCH 2: Schedule of Payment

Note: Insert Schedule of included in Bidding Documents and finalized at signing of the Contract (if any).

Schedules



Contractor’s Proposal

(List the items of Contractor’s Proposal comprising Technical Proposal)



Performance Security Option 1: (Demand Guarantee)

[Insert Guarantor letterhead or SWIFT identifier code]

Beneficiary: Department of Transportation and Communications (DOTC) Address: Unit 153, 15th Floor

The Columbia Tower, Ortigas Avenue Barangay Wack-Wack, Mandaluyong City 1555 Philippines

Date: [Insert date of issue] PERFORMANCE GUARANTEE No.: [Insert guarantee reference number] Guarantor: [Insert name and address of place of issue, unless indicated in the letterhead] We have been informed that [insert name of Contractor, which in the case of a joint venture shall be the name of the joint venture] (hereinafter called "the Applicant") has entered into Contract No. [insert reference number of the contract] dated [insert date] with the Beneficiary, for the execution of the Procurement of Trackwork, Electrical and Mechanical Systems and Integration with Existing Systems for LRT Line 2 – East (Masinag) Extension Project comprising Trackwork, Power Supply System, Overhead Catenary System, Signaling, Telecommunications System, Operations Control Center, and Automatic Fare Collection System (by Nominated Subcontractor); including all design, manufacture/test, delivery, storage, installation, site test, Systems Acceptance Test, carry out Interface/Integration of both LRT Line 2 Systems, commissioning, carry out all Systems Trial Operation and training of Employer’s operatives (hereinafter called "the Contract"). Furthermore, we understand that, according to the conditions of the Contract, a performance guarantee is required. At the request of the Applicant, we as Guarantor, hereby irrevocably undertake to pay the Beneficiary any sum or sums not exceeding in total an amount of [insert amount in figures] ([insert amount in words]),1 such sum being payable in the types and proportions of currencies in which the Contract Price is payable, upon receipt by us of the Beneficiary’s complying demand supported by the Beneficiary’s statement, whether in the demand itself or in a separate signed document accompanying or identifying the demand, stating that the Applicant is in breach of its obligation(s) under the Contract, without the Beneficiary needing to prove or to show grounds for its demand or the sum specified therein.

1 The Guarantor shall insert an amount representing the percentage of the Accepted Contract Amount

specified in the Letter of Acceptance, less provisional sums, if any, and denominated either in the currency(cies) of the Contract or a freely convertible currency acceptable to the Beneficiary.



This guarantee shall expire, no later than the [insert the day] day of [insert month], [insert year]2, and any demand for payment under it must be received by us at this office indicated above on or before that date. This guarantee is subject to the Uniform Rules for Demand Guarantees (URDG) 2010 Revision, ICC Publication No. 758, except that the supporting statement under Article 15(a) is hereby excluded. _____________________ [signature(s)] [Note: All italicized text (including footnotes) is for use in preparing this form and shall be deleted from the final product.]

2 Insert the date twenty eight (28) days after the expected completion date as described in GC Clause 11.9.

The Employer should note that in the event of an extension of this date for completion of the Contract, the Employer would need to request an extension of this guarantee from the Guarantor. Such request must be in writing and must be made prior to the expiration date established in the guarantee. In preparing this guarantee, the Employer might consider adding the following text to the form, at the end of the penultimate paragraph: “The Guarantor agrees to a one-time extension of this guarantee for a period not to exceed [six months][one year], in response to the Beneficiary’s written request for such extension, such request to be presented to the Guarantor before the expiry of the guarantee.”



Option 2: Performance Bond By this Bond [insert name of Principal] as Principal (hereinafter called “the Contractor”) and [insert name of surety] as Surety (hereinafter called “the Surety”), are held and firmly bound unto Department of Transportation and Communications (DOTC) of the Republic of the Philippines as Obligee (hereinafter called “the Employer”) in the amount of [insert the amount in words and figures], for the payment of which sum well and truly to be made in the types and proportions of currencies in which the Contract Price is payable, the Contractor and the Surety bind themselves, their heirs, executors, administrators, successors and assigns, jointly and severally, firmly by these presents. WHEREAS the Contractor has entered into a written Agreement with the Employer dated the [insert date] day of [insert month], [insert year], for the Procurement of Trackwork, Electrical and Mechanical Systems and Integration with Existing Systems for LRT Line 2 – East (Masinag) Extension Project comprising Trackwork, Power Supply System, Overhead Catenary System, Signaling, Telecommunications System, Operations Control Center, and Automatic Fare Collection System (by Nominated Subcontractor); including all design, manufacture/test, delivery, storage, installation, site test, Systems Acceptance Test, carry out Interface/Integration of both LRT Line 2 Systems, commissioning, carry out all Systems Trial Operation and training of Employer’s operatives in accordance with the documents, plans, specifications, and amendments thereto, which to the extent herein provided for, are by reference made part hereof and are hereinafter referred to as the Contract. NOW, THEREFORE, the Condition of this Obligation is such that, if the Contractor shall promptly and faithfully perform the said Contract (including any amendments thereto), then this obligation shall be null and void; otherwise, it shall remain in full force and effect. Whenever the Contractor shall be, and declared by the Employer to be, in default under the Contract, the Employer having performed the Employer’s obligations thereunder, the Surety may promptly remedy the default, or shall promptly: (1) complete the Contract in accordance with its terms and conditions; or (2) obtain a Bid or Bids from qualified Bidders for submission to the Employer for completing the

Contract in accordance with its terms and conditions, and upon determination by the Employer and the Surety of the lowest responsive Bidder, arrange for a Contract between such Bidder and Employer and make available as work progresses (even though there should be a default or a succession of defaults under the Contract or Contracts of completion arranged under this paragraph) sufficient funds to pay the cost of completion less the Balance of the Contract Price; but not exceeding, including other costs and damages for which the Surety may be liable hereunder, the amount set forth in the first paragraph hereof. The term “Balance of the Contract Price,” as used in this paragraph, shall mean the total amount payable by Employer to Contractor under the Contract, less the amount properly paid by Employer to Contractor; or

(3) pay the Employer the amount required by Employer to complete the Contract in accordance

with its terms and conditions up to a total not exceeding the amount of this Bond. The Surety shall not be liable for a greater sum than the specified penalty of this Bond. Any suit under this Bond must be instituted before the expiration of one (1) year from the date of the issuing of the Taking-Over Certificate.



No right of action shall accrue on this Bond to or for the use of any person or corporation other than the Employer named herein or the heirs, executors, administrators, successors, and assigns of the Employer. In testimony whereof, the Contractor has hereunto set his hand and affixed his seal, and the Surety has caused these presents to be sealed with his corporate seal duly attested by the signature of his legal representative, this [insert day] day of [insert month], [insert year]. SIGNED ON on behalf of By in the capacity of In the presence of SIGNED ON on behalf of By in the capacity of In the presence of [Note: All italicized text (including footnotes) is for use in preparing this form and shall be deleted from the final product.]



Advance Payment Security

Demand Guarantee




Date: [Insert date of issue]

ADVANCE PAYMENT GUARANTEE No.: [Insert guarantee reference number]

Guarantor: [Insert name and address of place of issue, unless indicated in the letterhead]

We have been informed that [insert name of Contractor, which in the case of a joint venture shall be the name of the joint venture] (hereinafter called “the Applicant”) has entered into Contract No. [insert reference number of the contract] dated [insert date of the contract] with the Beneficiary, for the execution of the Procurement of Trackwork, Electrical and Mechanical Systems and Integration with Existing Systems for LRT Line 2 – East (Masinag) Extension Project comprising Trackwork, Power Supply System, Overhead Catenary System, Signaling, Telecommunications System, Operations Control Center, and Automatic Fare Collection System (by Nominated Subcontractor); including all design, manufacture/test, delivery, storage, installation, site test, Systems Acceptance Test, carry out Interface/Integration of both LRT Line 2 Systems, commissioning, carry out all Systems Trial Operation and training of Employer’s operatives (hereinafter called "the Contract").

Furthermore, we understand that, according to the conditions of the Contract, an advance payment in the sum [insert amount in figures] ([insert amount in words]) is to be made against an advance payment guarantee.

At the request of the Applicant, we as Guarantor, hereby irrevocably undertake to pay the Beneficiary any sum or sums not exceeding in total an amount of [insert amount in figures] ([insert amount in words])1 upon receipt by us of the Beneficiary’s complying demand supported by the Beneficiary’s statement, whether in the demand itself or in a separate signed document accompanying or identifying the demand, stating either that the Applicant:

(a) has used the advance payment for purposes other than the costs of mobilization in respect of the Works; or

1 The Guarantor shall insert an amount representing the amount of the advance payment and denominated

either in the currency(ies) of the advance payment as specified in the Contract, or in a freely convertible currency acceptable to the Employer.



(b) has failed to repay the advance payment in accordance with the Contract conditions, specifying the amount which the Applicant has failed to repay.

A demand under this guarantee may be presented as from the presentation to the Guarantor of a certificate from the Beneficiary’s bank stating that the advance payment referred to above has been credited to the Applicant on its account number [insert number] at [insert name and address of Applicant’s bank].

The maximum amount of this guarantee shall be progressively reduced by the amount of the advance payment repaid by the Applicant as specified in copies of interim statements or payment certificates which shall be presented to us. This guarantee shall expire, at the latest, upon our receipt of a copy of the interim payment certificate indicating that ninety percent (90%) of the Accepted Contract Amount, less provisional sums, has been certified for payment, or on the [insert day] day of [insert month], [insert year],2 whichever is earlier. Consequently, any demand for payment under this guarantee must be received by us at this office on or before that date.

This guarantee is subject to the Uniform Rules for Demand Guarantees (URDG) 2010 Revision, ICC Publication No. 758, except that the supporting statement under Article 15(a) is hereby excluded.

____________________ [signature(s)] [Note: All italicized text (including footnotes) is for use in preparing this form and shall be deleted from the final product.]

2 Insert the expected expiration date of the Time for Completion. The Employer should note that in the event

of an extension of the time for completion of the Contract, the Employer would need to request an extension of this guarantee from the Guarantor. Such request must be in writing and must be made prior to the expiration date established in the guarantee. In preparing this guarantee, the Employer might consider adding the following text to the form, at the end of the penultimate paragraph: “The Guarantor agrees to a one-time extension of this guarantee for a period not to exceed [six months][one year], in response to the Beneficiary’s written request for such extension, such request to be presented to the Guarantor before the expiry of the guarantee.”



Retention Money Security

Demand Guarantee




Date: [Insert date of issue]

RETENTION MONEY GUARANTEE No.: [Insert guarantee reference number]

Guarantor: [Insert name and address of place of issue, unless indicated in the letterhead]

We have been informed that [insert name of Contractor, which in the case of a joint venture shall be the name of the joint venture] (hereinafter called "the Applicant") has entered into Contract No. [insert reference number of the contract] dated [insert date] with the Beneficiary, for the execution of the Procurement of Trackwork, Electrical and Mechanical Systems and Integration with Existing Systems for LRT Line 2 – East (Masinag) Extension Project comprising Trackwork, Power Supply System, Overhead Catenary System, Signaling, Telecommunications System, Operations Control Center, and Automatic Fare Collection System (by Nominated Subcontractor); including all design, manufacture/test, delivery, storage, installation, site test, Systems Acceptance Test, carry out Interface/Integration of both LRT Line 2 Systems, commissioning, carry out all Systems Trial Operation and training of Employer’s operatives (hereinafter called "the Contract").

Furthermore, we understand that, according to the conditions of the Contract, the Beneficiary retains moneys up to the limit set forth in the Contract (“the Retention Money”), and that when the Taking-Over Certificate has been issued under the Contract and the first half of the Retention Money has been certified for payment, payment of [insert the second half of the Retention Money or if the amount guaranteed under the Performance Guarantee when the Taking-Over Certificate is issued is less than half of the Retention Money, the difference between half of the Retention Money and the amount guaranteed under the Performance Security] is to be made against a Retention Money guarantee.

At the request of the Applicant, we, as Guarantor, hereby irrevocably undertake to pay the Beneficiary any sum or sums not exceeding in total an amount of [insert amount in figures] ([insert amount in words])1 upon receipt by us of the Beneficiary’s complying demand supported by the Beneficiary’s

1 The Guarantor shall insert an amount representing the amount of the second half of the Retention Money or

if the amount guaranteed under the Performance Guarantee when the Taking-Over Certificate is issued is



statement, whether in the demand itself or in a separate signed document accompanying or identifying the demand, stating that the Applicant is in breach of its obligation(s) under the Contract, without the Beneficiary needing to prove or show grounds for its demand or the sum specified therein.

A demand under this guarantee may be presented as from the presentation to the Guarantor of a certificate from the Beneficiary’s bank stating that the second half of the Retention Money as referred to above has been credited to the Applicant on its account number [insert account’s number] at [insert name and address of Applicant’s bank].

This guarantee shall expire no later than the [insert day] day of [insert month], [insert year]2, and any demand for payment under it must be received by us at the office indicated above on or before that date.

This guarantee is subject to the Uniform Rules for Demand Guarantees (URDG) 2010 Revision, ICC Publication No. 758, except that the supporting statement under Article 15(a) is hereby excluded.

____________________ [signature(s)] [Note: All italicized text (including footnotes) is for use in preparing this form and shall be deleted from the final product.]

less than half of the Retention Money, the difference between half of the Retention Money and the amount guaranteed under the Performance Security and denominated either in the currency(ies) of the second half of the Retention Money as specified in the Contract, or in a freely convertible currency acceptable to the Beneficiary.

2 Insert the same expiry date as set forth in the Performance Security, representing the date twenty eight (28) days after the completion date described in GC Clause 11.9. The Employer should note that in the event of an extension of this date for completion of the Contract, the Employer would need to request an extension of this guarantee from the Guarantor. Such request must be in writing and must be made prior to the expiration date established in the guarantee. In preparing this guarantee, the Employer might consider adding the following text to the form, at the end of the penultimate paragraph: “The Guarantor agrees to a one-time extension of this guarantee for a period not to exceed [six months][one year], in response to the Beneficiary’s written request for such extension, such request to be presented to the Guarantor before the expiry of the guarantee.”

URL:http://www.jica.go.jp E-mail:[email protected].

Date post:	15-Mar-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	1 times