SCTEP - Performance Test Procedure Rev6 - Clarifications

SUBIC CLARK TARLAC EXPRESSWAY PROJECT
THE DESIGN, MANUFACTURING, PROCUREMENT OF EQUIPMENT, WORKMANSHIP, SHIPPING TO SITE, INSTALLATION, CONSTRUCTION, TESTING, SETTING TO WORK, COMMISSIONING, DOCUMENTATION AND WARRANTY OF THE TOLL COLLECTION EQUIPMENT AND SYSTEM TITLE: PERFORMANCE TEST PROCEDURE
REVISION: 6 DATE : 22 Feb 2009 PURPOSE: PERFORMANCE TEST
Toll Collection System Contractor: Fujitsu Philippines Inc. nd 2 Floor, United Life Building, A. Arnaiz Avenue (Pasay Road), Legaspi Village, Makati City 1229, Philippines. Tel: +632-812-4001 Fax: +632-817-7576 Main Contractor: KOJM Joint Venture No. 175 Manibaug Pasig, Porac Pampanga 2008, Philippines Tel: +6345-329-3191 Fax: +6345-329-3200 Concessionaire: Bases Conversion and Development Authority 2nd Floor, Bonifacio Technology Center 31st St., Crescent Park West Bonifacio Global City, Taguig City Philippines Tel: +632-816-6666 Fax: +632-816-0996
Subic-Clark-Tarlac Expressway Project Performance Test Procedure
Page : 2 / 20 Rev : 6 Date : 22 Feb 2009
1. TABLE OF APPROVAL/ACCEPTANCE
Responsibility Prepared by Company Fujitsu Philippines Inc. Fujitsu Philippines Inc. Designation TCS Contractor Signature Date
Compiled by
TCS Contractor
Submitted by
KOJM Joint Venture
Main Contractor
Approved by
PCI-KEI-NK Joint Venture Bases Conversion and Development Authority
Consultant
Accepted by
Concessionaire
COMPILED BY: Fujitsu Philippines Inc. All rights reserved. Consistent with our policy of continuing product and solution development, specifications and solutions shown in this document are subject to change without notice.
Page : 3 / 20 Rev : 6 Date : 22 Feb 2009
2. DISTRIBUTION LIST
Copy No. Company Fujitsu Philippines Inc. Designation Copy
MASTER
TCS Contractor
KOJM Joint Venture
Main Contractor
PCI-KEI-NK Joint Venture Bases Conversion and Development Authority
Consultant
Concessionaire
Page : 4 / 20 Rev : 6 Date : 22 Feb 2009
3. REVISION GRID
Revision No. 0 1 2 3 4 5 6
Date 22/4/2008 22/5/2008 4/6/2008 16/6/2008 1/7/2008 12/7/2008 22/02/2009
Revision First Release Second Release Third Release Fourth Release Fifth Release Sixth Release Seventh Release
Remarks Performance Test Procedure More detailed update on system performance testing as per comment Updated TMC application performance Added system generated reports Modified added system generated reports Included additional procedures as per JVC comments Updated based on BCDA comments
Page : 5 / 20 Rev : 6 Date : 22 Feb 2009
4. TABLE OF CONTENTS
1. 2. 3. 4. 5. 6. 7. 8. TABLE OF APPROVAL/ACCEPTANCE............................................................................................... 2 DISTRIBUTION LIST ............................................................................................................................... 3 REVISION GRID ....................................................................................................................................... 4 TABLE OF CONTENTS........................................................................................................................... 5 INTRODUCTION....................................................................................................................................... 6 VEHICLE CLASS CATEGORY .............................................................................................................. 6 SCOPE ....................................................................................................................................................... 6 PERFORMANCE TESTING.................................................................................................................... 7 8.1 SYSTEM APPLICATIONS AND PERIPHERALS............................................................................. 7 8.1.1 Lane Application Performance (Entry)........................................................................................ 7 8.1.2 Lane Peripherals (Entry) ............................................................................................................. 8 8.1.3 Lane Application Performance (Exit) .......................................................................................... 8 8.1.4 Lane Peripherals (Exit)................................................................................................................ 9 8.1.5 Toll Monitoring Console (TMC) Application Performance ....................................................... 10 8.1.6 Plaza Generated Reports ........................................................................................................... 11 8.1.7 Plaza Application Performance ................................................................................................. 11 8.1.8 Maxi Booth Equipment .............................................................................................................. 12 8.1.9 Toll Operations Center (TOC) Application Performance .......................................................... 13 8.1.10 TOC Generated Reports............................................................................................................. 13 8.1.11 Concessionaire Reports ............................................................................................................. 14 8.1.12 Smartcard Batch Processing Application Performance............................................................. 15 8.1.13 TOC Computer Room Equipment .............................................................................................. 15 8.2 AVC SYSTEM PERFORMANCE..................................................................................................... 17 8.2.1 SAMPLE AVC SAMPLING RECORD FORMAT....................................................................... 18 8.2.2 SAMPLE AVC TEST RESULT SUMMARY ................................................................................ 19 8.3 SAMPLE CONCLUSION REPORT ................................................................................................. 20
Page : 6 / 20 Rev : 6 Date : 22 Feb 2009
5. INTRODUCTION
This document describes the procedure and guidelines in carrying out the site performance test during live system operation.
6. VEHICLE CLASS CATEGORY

No of Axles 2 3 4 or more Height < or = 2.13m Class 1 Class 2 Class 3 Height > 2.13m Class 2 Class 3 Class 3
7. SCOPE
The scope of this document is to provide a report on the Performance Test results for the entire SCTEX manual toll collection system. The results compiled in this document are presented in as it is monitored basis. It is not the intention of this report to address the system design, interfaces, fraud, human intervention, and operation and maintenance procedures.
Page : 7 / 20 Rev : 6 Date : 22 Feb 2009
8. PERFORMANCE TESTING
The performance test is a functional evaluation of the system wherein emphasis is on the final measurable performance characteristics rather than on detailed material or component specifications. Even though this test is based mainly on the evaluation of the AVC system which has a significant impact on the proper collection of toll fee based on the correctness of vehicle classification and thus directly translating into the entire system performance, performances of both system applications and other peripherals are essential as well. The subsequent tables can be used as checklists to verify and record corresponding data that will be acquired from actual observation during the conduct of the test.
8.1
SYSTEM APPLICATIONS AND PERIPHERALS
The overall system performance involves the performance of the lane application, TMC (toll monitoring console) application, plaza application, TOC (toll operations center) application, the smartcard batch processing application and the accuracy of generated reports. Baseline data are included as well for reference to benchmark the systems optimum performance. Performance test for the entry lane shall be conducted by observing and taking note of the items enumerated on Table 8.1.1 below on any one complete random transaction selected. 8.1.1
Item
Lane Application Performance (Entry)

Average 1 second 1 second 1 second 2 seconds 1 second 1 second Up to 450 transactions per hour 2 seconds 5 seconds
Upon vehicle exit from VDD zone until transaction is reflected in the job listing
1 2 3 4 5 6 7
8 9
System Function TC login OTL change to Red or Green Entry of class type and acceptance Time to process smartcard and display data for TC LTL change to Green after card is issued LTL change to Red or vice versa Lane transaction [depends on TC performance] Vehicle counting after vehicle leaves VDD detection zone (0 40 kph) Data synchronization between Lane and PCS [depends on network performance]
Remarks
From SC issuance (TIE) until data is displayed at VDU
From pressing the vehicle class button until SC is handed to the motorist
Page : 8 / 20 Rev : 6 Date : 22 Feb 2009
10
Minimum number of operation days that all data related to jobs, transactions and alarms could be stored in the lane controller if there is a network failure
30 days
Likewise, the functionality of each component listed on Table 8.1.2 shall also be observed and noted for one complete random transaction selected. 8.1.2
Item 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Lane Peripherals (Entry)

Remarks
Lane Peripheral Lane Controller Visual Display Unit Keyboard with ISO Card Reader Ticket Issuance Equipment Emergency Foot Switch IP Phone Uninterruptible Power Supply Transient Voltage Surge Suppressor Media Converter Overhead Traffic Light Vehicle Departure Detector Lane Traffic Light Amber Security Beacon Loop Coil
Performance test for the exit lane shall be conducted by observing and taking note of the items enumerated on Table 8.1.3 for one complete random transaction selected. 8.1.3
Item 1 2 3 4
Lane Application Performance (Exit)

Average 1 second 1 second 1 second Remarks
System Function TC login OTL change to Red or Green Entry of class type and acceptance CRS to indicate vehicle classification Time to process smart card and display data for TC and motorist LTL change from Red to Green after payment is received and accepted TFI to show fare amount and Thank You message after Accept is registered Time to print a receipt and journal for cash
After pressing the Accept button until system has reflected class acceptance After pressing the Accept button and TFI has displayed the fare amount
1 second 3 seconds 1 second 1 second 6 seconds

After pressing the Accept
5 6 7
8
Page : 9 / 20 Rev : 6 Date : 22 Feb 2009
transaction 9 Time to print a voucher and journal for a non-cash transaction Lane transaction [depends on TC performance] AVC output upon vehicle entry at AVC detection zone (0 40 kph) Automatic Lane Barrier opening time Automatic Lane Barrier closing time 1 second 14 15 Data synchronization between Lane and PCS [depends on network performance] Minimum number of operation days that all data related to jobs, transactions and alarms could be stored in the lane controller if there is a network failure 5 seconds
6 seconds Up to 240 transactions per hour 2 seconds 1 second
10
(cash) button until end of receipt/journal printing After pressing the non-cash button until vehicle has left AVC zone and voucher/ journal printing has ended. Upon SC insertion into the TVE until receipt is handed to the motorist Upon vehicle exit from AVC zone until system returns to classification menu After pressing the Accept button until ALB opens Once AVC has returned the class to the lane system until ALB closes down Upon vehicle exit from AVC zone until transaction is reflected in the job listing
11 12 13
30 days
Likewise, the functionality of each component listed on Table 8.1.4 shall also be observed and noted for one complete random transaction selected. 8.1.4
Item 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Lane Peripherals (Exit)

Remarks
Lane Peripheral Lane Controller Visual Display Unit Keyboard with ISO Card Reader Ticket Validation Equipment Emergency Foot Switch Receipt Printer IP Phone Uninterruptible Power Supply Transient Voltage Surge Suppressor Media Converter Overhead Traffic Light Automatic Vehicle Classification System Automatic Lane Barrier Lane Traffic Light Toll Fare Indicator Amber Security Beacon Classification Repeater Sign Loop Coil
Page : 10 / 20 Rev : 6 Date : 22 Feb 2009
Performance test for the toll monitoring console shall be conducted by observing and taking note of the items enumerated on Table 8.1.5 for one complete random transaction or incident selected. 8.1.5
Item 1
Toll Monitoring Console (TMC) Application Performance

Average 1 3 seconds 1 second
MBC status is sent within 3 seconds after MBC communication failed message is displayed at the lane. From then until status is reflected on RTMC. AVC status is sent within 3 seconds after AVC communication failed message is displayed at the lane. From then until status is reflected on RTMC. Printer status is sent within 5 seconds. From then until status is reflected on RTMC. Upon changing of ALB status in remote control mode until its status change is reflected on Incident field After pressing the EFS until signal is shown in RTMC After class discrepancy has occurred at the lane (upon vehicle exit from AVC zone) until it is reflected on Incident field Equipment status after an incident is sent within 7 seconds. From then until status is reflected on RTMC.
System Function Time to display all equipment status i.e., OTL, LTL, TFI, ALB and LC door Time to display user login status Time to display MBC status [if MBC is down for 60 seconds]
Remarks
Equipment statuses are sent within 3 seconds. From then until status is reflected on RTMC.
2 3
1 3 seconds
Time to display AVC status [if AVC is down for 60 seconds] 1 3 seconds
Time to display printer status 3 5 seconds
Time to display ALB remote control status (close, open or release) Time to display alert for emergency (EFS) Time to display alert for class discrepancy
1 second 1 3 seconds
8 9 10 Remote login Time to update status of icons after incidents
1 3 seconds 1 3 seconds 2 7 seconds
Accuracy of reports listed on Table 8.1.6 as generated at each selected plaza shall be verified by an audit team composed of nominated representatives.
Page : 11 / 20 Rev : 6 Date : 22 Feb 2009
8.1.6
Item 1 2 3 4 5 6 7 8
Plaza Generated Reports

Remarks
Report Cash Up Summary Report Float Summary Report Money Bag Listing Revenue Banking Period Summary Bank Deposit Batch Reconciliation Report Job Summary Report Plaza Activity Summary Report Logs of Equipment Alarms Report
Performance test for the plaza application shall be conducted by observing and taking note of the items enumerated on Table 8.1.7 for each random incident or activity selected. 8.1.7
Item 1 2 3 4 5
Plaza Application Performance

Average 10 seconds Remarks
From the time an incident is triggered at the lane until it is reflected on Incident field Upon clicking of Acknowledge button until incident is updated
System Function Updating of incident at PCS Incident acknowledgment by TS
3 seconds Processing of report printout function [depends on criteria selected] Daily and monthly traffic revenue report generation Uploading of parameters from PCS 3 10 seconds 3 seconds 25 seconds 6 7 Time to display inquiry screen CPU loading when working on: a) the system program during normal operation b) processing of on-demand display and printout function c) uploading and validation process Time delay between operator action and screen display Time delay between operator action and printout Time delay between operator action and screen display for exceptionally large database table (e.g. Cash/individual detail 3 seconds
From the time parameters are changed at TOCCS until download at PCS is completed
60%
8 9 10
5 seconds 15 seconds 10 seconds
After clicking each of the options in the menu until screen displays the details
Page : 12 / 20 Rev : 6 Date : 22 Feb 2009
11
12
transaction) Time delay between operator action and printout for exceptionally large database table (e.g. Cash/individual detail transaction) Time to upload data to PCS using external medium i.e., thumb drive for one complete day of data from the lane if network failed
20 - 120 seconds
After Print button is clicked until the report is generated
5 minutes
After clicking Upload button until data transfer is completed
The functionality of each component listed on Table 8.1.8 shall also be observed and noted for one complete random incident or activity selected. 8.1.8
Item 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
Maxi Booth Equipment

Remarks
Equipment Plaza Computer System Server PCS Server Monitor PCS Server Keyboard PCS Server Mouse Real-Time Monitoring Console RTMC Monitor RTMC Keyboard RTMC Mouse Toll Supervisor Terminal TST Monitor TST Keyboard TST Mouse Tour-of-Duty Terminal TOD Monitor TOD Keyboard TOD Mouse TOD Printer (Laser) Operations Printer (Laser) Maintenance Printer (Dot Matrix) ISO Card Reader 1 ISO Card Reader 2 ISO Card Reader 3 IP Phone 1 IP Phone 2 Router Network Switch Uninterruptible Power Supply Transient Voltage Surge Suppressor Stage 1 Transient Voltage Surge Suppressor Stage 2 Transient Voltage Surge Suppressor Stage 3
Page : 13 / 20 Rev : 6 Date : 22 Feb 2009
Performance test for the toll operations center application shall be conducted by observing and taking note of the items enumerated on Table 8.1.9 for one random activity selected. 8.1.9
Item 1
Toll Operations Center (TOC) Application Performance

Average 1 5 seconds 3 20 seconds Remarks
After Submit button is clicked (when transaction info has been entered on the field) until system reflects it
System Function Time to buildup new data entry [depends on extent of data information]
2 3
4 5 6
Time to generate summary reports (daily and monthly) CPU loading when working on: a) the system program during normal operation b) processing of on-demand display and printout function c) uploading and validation process Time delay between operator action and screen display Time delay between operator action and printout Time delay between operator action and screen display for exceptionally large database table (e.g. all summary reports). Time delay between operator action and printout for exceptionally large database table (e.g. all summary reports) Time to upload PCS parameters from TOCCS using external medium i.e., thumb drive if network failed
60%
5 seconds 15 seconds 5 15 seconds 20 - 120 seconds 1 - 5 minutes
After clicking each of the options in the menu until screen displays the details After Print button is clicked until the report is generated After clicking Upload button until data transfer is completed
Accuracy of reports listed on Table 8.1.10 as generated at the toll operations center shall be verified by an audit team composed of nominated representatives. 8.1.10
Item 1 2 3 4 5 6 7
TOC Generated Reports

Remarks
Report Comprehensive Report Daily Cash Revenue Daily Traffic Revenue by User (Cash) Daily Traffic Revenue by User (Service) Daily Traffic Volume by User (All MOP) Daily Traffic Volume by User (Cash) Daily Traffic Volume by User (Exempt)
Page : 14 / 20 Rev : 6 Date : 22 Feb 2009
8 9 10
Daily Traffic Volume by User (HPMC) Daily Traffic Volume by User (Service) Daily Traffic Volume by User (Violations)
Accuracy of the Concessionaire reports listed on Table 8.1.11 as generated at the toll operations center shall be verified by an audit team from the Concessionaire. 8.1.11
Item 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Concessionaire Reports
Remarks
Report Toll Operations Report (All Plazas) Toll Operations Report [per plaza] Traffic Volume by Toll Plaza (All Plazas) Traffic Volume by Vehicle Classification (All Plazas) Traffic Revenue by Toll Plaza (All Plazas) Traffic Revenue by Vehicle Classification (All Plazas) Toll Revenue and Traffic Volume (All Plazas) Toll Traffic Volume by Plaza (All Plazas) Total Cash Revenue by Plaza (All Plazas) Traffic Volume by Vehicle Classification [per plaza] Daily Traffic Volume by User (Cash) [per plaza] Daily Traffic Volume by User (Service) [per plaza] Daily Traffic Volume by User (Exempt) [per plaza] Daily Traffic Volume by User (Violations) [per plaza] Daily Traffic Volume by User (All MOP) [per plaza] Traffic Revenue by Vehicle Classification [per plaza] Daily Traffic Revenue by User (Cash) [per plaza] Daily Traffic Revenue by User (Service) [per plaza] Daily Traffic Revenue by User (Exempt) [per plaza] Daily Cash Revenue [per plaza] Toll Revenue and Traffic Volume [per plaza]
Performance test for the smart card batch processing application shall be conducted by observing and taking note of the items enumerated on Table 8.1.12. Recommended sampling size is 200 pieces.
Page : 15 / 20 Rev : 6 Date : 22 Feb 2009
8.1.12
Item 1
Smartcard Batch Processing Application Performance

Average 5 seconds Remarks
Upon clicking of Start button to encode information onto the card until the card is dropped off by the machine. Upon clicking of Start button to encode information onto the card until the card is dropped off by the machine. After clicking each of the options in the menu until screen displays the details After login ID and password have been entered for the BPM to authenticate them with the TOCCS database until being logged in and able to access the system.
System Function Time to initialize a new card
Time to create a pre-issued card 5 seconds
3 4
Time delay between operator action and screen display Time to access data from TOCCS
2 seconds
1 - 3 seconds
The functionality of each component listed on Table 8.1.13 shall also be observed and noted for one random activity selected. 8.1.13
Item 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
TOC Computer Room Equipment

Remarks
Equipment TOC Computer System Server TOCCS Server Monitor TOCCS Server Keyboard TOCCS Server Mouse Network Monitoring System Server NMS Server Monitor NMS Server Keyboard NMS Server Mouse TOC Computer System Workstation 1 TOCCS Workstation 1 Monitor TOCCS Workstation 1 Keyboard TOCCS Workstation 1 Mouse TOC Computer System Workstation 2 TOCCS Workstation 2 Monitor TOCCS Workstation 2 Keyboard TOCCS Workstation 2 Mouse Operations & Tour-of-Duty Printer 1 Operations & Tour-of-Duty Printer 2 Smart Card Batch Processing Machine
Page : 16 / 20 Rev : 6 Date : 22 Feb 2009
20 21 22 23 24 25 26 27 28 29 30
ISO Card Encoder ISO Card Reader 1 ISO Card Reader 2 IP Phone 1 IP Phone 2 IP Phone 3 Router Network Switch Uninterruptible Power Supply Transient Voltage Surge Suppressor Stage 1 Transient Voltage Surge Suppressor Stage 2
Page : 17 / 20 Rev : 6 Date : 22 Feb 2009
8.2
AVC SYSTEM PERFORMANCE
The accuracy of the Automatic Vehicle Classification (AVC) system shall be 1 error in every 1000 vehicles based on the following assumptions: 1. The traffic sampling used for measurement shall be the statistical representative of actual vehicles for the accuracy required on the lane. 2. This guarantee applies only to the correct determination of the classification based on the AVC criteria above. 3. The results compiled are presented in as it is monitored basis. It is not the intention of this procedure to address the system design, interfaces, fraud, human intervention and other operational and maintenance procedures. Following are the steps that shall be carried out for the AVC performance testing to determine its accuracy: 1. The AVC performance is to be monitored for 1 hour or for the first 100 vehicles, whichever comes first, for each AVC lane or randomly selected AVC lane (minimum is one wide lane and one 3-meter lane) at each toll plaza. 2. Every discrepancy identified during the monitoring period will be recorded and verified against the actual vehicle classification noted down on the AVC Sampling Record by the designated arbiter (recommended personnel will be from the Consultant). 3. The samples recorded on the AVC Sampling Record will be used to analyze the discrepancies reported during the performance testing period. During the performance test, it is recommended that there should be no malfunction of the AVC equipment and that all peripherals interfaced to the AVC system are in good working condition to obtain precise test results. Otherwise, the said malfunction needs to be repaired first prior to conducting the performance test. 4. The total number of discrepancies recorded shall be analyzed to determine the actual number of discrepancies that can be attributed to the AVC system. Discrepancies caused by exceptional cases shall not be considered as AVC errors.
Page : 18 / 20 Rev : 6 Date : 22 Feb 2009
8.2.1
SAMPLE AVC SAMPLING RECORD FORMAT

PLAZA ______________ LANE ___ DATE ____________
NO 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 1 MVC 2 3 1 AVC 2 3 REMARKS
AVC STATISTICAL SAMPLING RECORD

NO 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 1 MVC 2 3 1 2 AVC 3 REMARKS
Page : 19 / 20 Rev : 6 Date : 22 Feb 2009
8.2.2 PLAZA :
SAMPLE AVC TEST RESULT SUMMARY
DATE : LANE :
As Recorded Total Sampling Recorded Correct Classification Incorrect Classification Unable to Classify Accounted Error (not due to AVC System) Classification Rate AVC Error AVC Accuracy A= 1000 B= 996 C= 1 D= 1 E= 2 X1= (A - D) / A x 100% X2= (C / A) x 100% X3= 100% - X2
Page : 20 / 20 Rev : 6 Date : 22 Feb 2009
8.3
SAMPLE CONCLUSION REPORT
1. The Performance Test has been successfully carried out in Subic-Clark-Tarlac Expressway (SCTEX) at selected lanes, from __(date)___ to __(date)___ in accordance with the Performance Test requirements (SPL 1500.3.7.3). 2. During the Performance Test, no malfunction of AVC equipment has been reported. All peripherals interfaced to the AVC system are in good working condition. 3. All recorded results have been presented on as it is monitored basis. The data were based on actual observations without taking into consideration any possible fraud, equipment failure, human intervention and the like. 4. A summary of the Performance Test results is shown below: Clark North A 3
Lane Total Vehicle Passage Correct Classification Incorrect Classification Unable to Classify Accounted Error AVC Accuracy (%)
5. This report shall conclude the MTCS system performance as installed in SCTEX. Attached with this report are the AVC Statistical Sampling Records and tabulated Test Result Summaries as supporting documents. 6. Examples of errors that shall be considered as accounted error in certain cases are as follows: bumper to bumper crossing, bulldozers, human crossing, overloaded vehicles, modified vehicles such as the ones with low profiles, with attached antistatic chain, etc. These are some of the error factors that would affect accuracy. However, low accuracy in Lanes 1 and 3 was generally caused by hardware defects. There were a number of inconsistent detection feedbacks when some vehicles pass through. The situation can be improved by replacing the identified failing pad sensors. It was also noted that Lanes 2 and 4 have greater vibrations as compared to other lanes when a heavily loaded trailer passes through. This is another factor that shall be considered as indirectly contributing to intermittent detection of the beam while some incorrect classifications recorded from other lanes are mainly caused by an additional pulse.

SCTEP - Performance Test Procedure Rev6 - Clarifications

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SCTEP - Performance Test Procedure Rev6 - Clarifications

Hochgeladen von

Copyright:

Verfügbare Formate

SUBIC CLARK TARLAC EXPRESSWAY PROJECT

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 2 / 20 Rev : 6 Date : 22 Feb 2009

KOJM Joint Venture

PCI-KEI-NK Joint Venture Bases Conversion and Development Authority

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 3 / 20 Rev : 6 Date : 22 Feb 2009

KOJM Joint Venture

PCI-KEI-NK Joint Venture Bases Conversion and Development Authority

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 4 / 20 Rev : 6 Date : 22 Feb 2009

Date 22/4/2008 22/5/2008 4/6/2008 16/6/2008 1/7/2008 12/7/2008 22/02/2009

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 5 / 20 Rev : 6 Date : 22 Feb 2009

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 6 / 20 Rev : 6 Date : 22 Feb 2009

6. VEHICLE CLASS CATEGORY

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 7 / 20 Rev : 6 Date : 22 Feb 2009

SYSTEM APPLICATIONS AND PERIPHERALS

Lane Application Performance (Entry)

From SC issuance (TIE) until data is displayed at VDU

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 8 / 20 Rev : 6 Date : 22 Feb 2009

Lane Peripherals (Entry)

Lane Application Performance (Exit)

1 second 3 seconds 1 second 1 second 6 seconds

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 9 / 20 Rev : 6 Date : 22 Feb 2009

6 seconds Up to 240 transactions per hour 2 seconds 1 second

Lane Peripherals (Exit)

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 10 / 20 Rev : 6 Date : 22 Feb 2009

Toll Monitoring Console (TMC) Application Performance

Time to display printer status 3 5 seconds

8 9 10 Remote login Time to update status of icons after incidents

1 3 seconds 1 3 seconds 2 7 seconds

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 11 / 20 Rev : 6 Date : 22 Feb 2009

Plaza Generated Reports

Plaza Application Performance

System Function Updating of incident at PCS Incident acknowledgment by TS

5 seconds 15 seconds 10 seconds

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 12 / 20 Rev : 6 Date : 22 Feb 2009

After Print button is clicked until the report is generated

After clicking Upload button until data transfer is completed

Maxi Booth Equipment

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 13 / 20 Rev : 6 Date : 22 Feb 2009

Toll Operations Center (TOC) Application Performance

5 seconds 15 seconds 5 15 seconds 20 - 120 seconds 1 - 5 minutes

TOC Generated Reports

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 14 / 20 Rev : 6 Date : 22 Feb 2009

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 15 / 20 Rev : 6 Date : 22 Feb 2009

Smartcard Batch Processing Application Performance

System Function Time to initialize a new card

Time to create a pre-issued card 5 seconds

TOC Computer Room Equipment

Subic-Clark-Tarlac Expressway Project Performance Test Procedure

Page : 16 / 20 Rev : 6 Date : 22 Feb 2009