SCTEP - Performance Test Procedure Rev6 - Clarifications

transcript

8/2/2019 SCTEP - Performance Test Procedure Rev6 - Clarifications

1/20

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 PROCEDUREREVISION: 6 DATE : 22 Feb 2009 PURPOSE: PERFORMANCE TEST

Toll Collection System Contractor:Fujitsu Philippines Inc.2nd Floor, United Life Building,A. Arnaiz Avenue (Pasay Road),Legaspi Village, Makati City 1229,Philippines.Tel: +632-812-4001Fax: +632-817-7576

Main Contractor:KOJM Joint VentureNo. 175 ManibaugPasig, PoracPampanga 2008, PhilippinesTel: +6345-329-3191Fax: +6345-329-3200

Concessionaire:Bases Conversion and Development Authority2nd Floor, Bonifacio Technology Center31st St., Crescent Park WestBonifacio Global City, Taguig CityPhilippinesTel: +632-816-6666Fax: +632-816-0996


2/20

Subic-Clark-Tarlac Expressway ProjectPerformance Test Procedure

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

COMPILED BY: Fujitsu Philippines Inc.All rights reserved. Consistent with our policy of continuing product and solution development, specifications and solutions shown inthis document are subject to change without notice.

1. TABLE OF APPROVAL/ACCEPTANCE

Responsibility Company Designation Signature Date

Prepared by Fujitsu PhilippinesInc. TCS Contractor

Compiled by Fujitsu PhilippinesInc. TCS Contractor

Submitted by KOJM Joint Venture Main Contractor

Approved by PCI-KEI-NK JointVenture Consultant

Accepted byBases Conversionand Development

AuthorityConcessionaire


3/20


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


2. DISTRIBUTION LIST

Copy No. Company Designation Copy

MASTER Fujitsu PhilippinesInc. TCS Contractor 1

1 KOJM Joint Venture Main Contractor 1

2 PCI-KEI-NK JointVenture Consultant 1

3Bases Conversionand Development

AuthorityConcessionaire 1


4/20


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


3. REVISION GRID

RevisionNo. Date Revision Remarks

0 22/4/2008 First Release Performance TestProcedure

1 22/5/2008 Second ReleaseMore detailed update onsystem performancetesting as per comment

2 4/6/2008 Third Release Updated TMC applicationperformance

3 16/6/2008 Fourth Release Added system generatedreports

4 1/7/2008 Fifth Release Modified added systemgenerated reports

5 12/7/2008 Sixth ReleaseIncluded additionalprocedures as per JVCcomments

6 22/02/2009 Seventh Release Updated based on BCDAcomments


5/20


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


4. TABLE OF CONTENTS

1. TABLE OF APPROVAL/ACCEPTANCE ............................................................................................... 2

2. DISTRIBUTION LIST ............................................................................................................................... 3

3. REVISION GRID ....................................................................................................................................... 4

4. TABLE OF CONTENTS ........................................................................................................................... 5

5. INTRODUCTION ....................................................................................................................................... 6

6. VEHICLE CLASS CATEGORY .............................................................................................................. 6

7. SCOPE ....................................................................................................................................................... 6

8. 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


6/20


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


5. INTRODUCTION

This document describes the procedure and guidelines in carrying out the siteperformance test during live system operation.

6. VEHICLE CLASS CATEGORY

No of Axles Height < or = 2.13m Height > 2.13m2 Class 1 Class 23 Class 2 Class 3

4 or more Class 3 Class 3

7. SCOPE

The scope of this document is to provide a report on the Performance Test results forthe entire SCTEX manual toll collection system. The results compiled in this documentare presented in as it is monitored basis. It is not the intention of this report to addressthe system design, interfaces, fraud, human intervention, and operation and

maintenance procedures.


7/20


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


8. PERFORMANCE TESTING

The performance test is a functional evaluation of the system wherein emphasis is onthe final measurable performance characteristics rather than on detailed material orcomponent specifications. Even though this test is based mainly on the evaluation ofthe AVC system which has a significant impact on the proper collection of toll fee basedon the correctness of vehicle classification and thus directly translating into the entiresystem performance, performances of both system applications and other peripheralsare essential as well. The subsequent tables can be used as checklists to verify andrecord corresponding data that will be acquired from actual observation during theconduct 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 generatedreports.

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 ofthe items enumerated on Table 8.1.1 below on any one complete random transactionselected.

8.1.1 Lane Application Performance (Entry)

Item System Function Average Remarks1 TC login 1 second2 OTL change to Red or Green 1 second3 Entry of class type and acceptance 1 second4 Time to process smartcard and display

data for TC2 seconds From SC issuance (TIE)

until data is displayed atVDU

5 LTL change to Green after card is issued 1 second6 LTL change to Red or vice versa 1 second7 Lane transaction [depends on TC

performance]Up to 450

transactionsper hour

From pressing the vehicleclass button until SC ishanded to the motorist

8 Vehicle counting after vehicle leaves VDDdetection zone (0 40 kph) 2 seconds

9 Data synchronization between Lane andPCS [depends on network performance] 5 seconds

Upon vehicle exit from VDDzone until transaction isreflected in the job listing


8/20


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


10 Minimum number of operation days that alldata related to jobs, transactions andalarms could be stored in the lanecontroller if there is a network failure

30 days

Likewise, the functionality of each component listed on Table 8.1.2 shall also beobserved and noted for one complete random transaction selected.

8.1.2 Lane Peripherals (Entry)

Item Lane Peripheral Remarks1 Lane Controller2 Visual Display Unit3 Keyboard with ISO Card Reader4 Ticket Issuance Equipment5 Emergency Foot Switch6 IP Phone7 Uninterruptible Power Supply8 Transient Voltage Surge Suppressor9 Media Converter

10 Overhead Traffic Light11 Vehicle Departure Detector12 Lane Traffic Light13 Amber Security Beacon14 Loop Coil

Performance test for the exit lane shall be conducted by observing and taking note ofthe items enumerated on Table 8.1.3 for one complete random transaction selected.

8.1.3 Lane Application Performance (Exit)

Item System Function Average Remarks1 TC login 1 second2 OTL change to Red or Green 1 second3 Entry of class type and acceptance

1 secondAfter pressing the Acceptbutton until system hasreflected class acceptance

4 CRS to indicate vehicle classification 1 second5 Time to process smart card and display

data for TC and motorist3 seconds After pressing the Acceptbutton and TFI has

displayed the fare amount6 LTL change from Red to Green after

payment is received and accepted 1 second

7 TFI to show fare amount and Thank Youmessage after Accept is registered 1 second8 Time to print a receipt and journal for cash 6 seconds After pressing the Accept


9/20


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


transaction (cash) button until end ofreceipt/journal printing

9 Time to print a voucher and journal for anon-cash transaction 6 seconds

After pressing the non-cash

button until vehicle has leftAVC zone and voucher/ journal printing has ended.

10 Lane transaction [depends on TCperformance]

Up to 240transactions

per hour

Upon SC insertion into theTVE until receipt is handedto the motorist

11 AVC output upon vehicle entry at AVCdetection zone (0 40 kph) 2 seconds

Upon vehicle exit from AVCzone until system returns toclassification menu

12 Automatic Lane Barrier opening time 1 second After pressing the Acceptbutton until ALB opens13 Automatic Lane Barrier closing time

1 secondOnce AVC has returned theclass to the lane systemuntil ALB closes down

14 Data synchronization between Lane andPCS [depends on network performance] 5 seconds

Upon vehicle exit from AVCzone until transaction isreflected in the job listing

15 Minimum number of operation days that alldata related to jobs, transactions andalarms could be stored in the lanecontroller if there is a network failure

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 Lane Peripherals (Exit)

Item Lane Peripheral Remarks1 Lane Controller2 Visual Display Unit3 Keyboard with ISO Card Reader4 Ticket Validation Equipment5 Emergency Foot Switch6 Receipt Printer

7 IP Phone8 Uninterruptible Power Supply9 Transient Voltage Surge Suppressor

10 Media Converter11 Overhead Traffic Light12 Automatic Vehicle Classification System13 Automatic Lane Barrier14 Lane Traffic Light15 Toll Fare Indicator16 Amber Security Beacon

17 Classification Repeater Sign18 Loop Coil


10/20


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


Performance test for the toll monitoring console shall be conducted by observing andtaking note of the items enumerated on Table 8.1.5 for one complete randomtransaction or incident selected.

8.1.5 Toll Monitoring Console (TMC) Application Performance

Item System Function Average Remarks1 Time to display all equipment status i.e.,

OTL, LTL, TFI, ALB and LC door 1 3 seconds

Equipment statuses aresent within 3 seconds.From then until status isreflected on RTMC.

2 Time to display user login status 1 second3 Time to display MBC status [if MBC is

down for 60 seconds]1 3 seconds

MBC status is sent within 3seconds after MBC communication failed message is displayed at thelane. From then until statusis reflected on RTMC.

4 Time to display AVC status [if AVC is downfor 60 seconds]

1 3 seconds

AVC status is sent within 3seconds after AVC communication failed message is displayed at thelane. From then until statusis reflected on RTMC.

5 Time to display printer status3 5 seconds

Printer status is sent within5 seconds. From then untilstatus is reflected onRTMC.

6 Time to display ALB remote control status(close, open or release) 1 second

Upon changing of ALBstatus in remote controlmode until its status changeis reflected on Incident field

7 Time to display alert for emergency (EFS) 1 3 seconds After pressing the EFS untilsignal is shown in RTMC

8

Time to display alert for class discrepancy

1 3 seconds

After class discrepancy hasoccurred at the lane (uponvehicle exit from AVC zone)

until it is reflected onIncident field9 Remote login 1 3 seconds

10 Time to update status of icons afterincidents 2 7 seconds

Equipment status after anincident is sent within 7seconds. From then untilstatus is reflected onRTMC.

Accuracy of reports listed on Table 8.1.6 as generated at each selected plaza shall beverified by an audit team composed of nominated representatives.


11/20


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


8.1.6 Plaza Generated Reports

Item Report Remarks1 Cash Up Summary Report2 Float Summary Report3 Money Bag Listing4 Revenue Banking Period Summary5 Bank Deposit Batch Reconciliation Report6 Job Summary Report7 Plaza Activity Summary Report8 Logs of Equipment Alarms Report

Performance test for the plaza application shall be conducted by observing and takingnote of the items enumerated on Table 8.1.7 for each random incident or activityselected.

8.1.7 Plaza Application Performance

Item System Function Average Remarks1 Updating of incident at PCS

10 secondsFrom the time an incident istriggered at the lane until itis reflected on Incident field

2 Incident acknowledgment by TS

3 seconds

Upon clicking of

Acknowledge button untilincident is updated3 Processing of report printout function

[depends on criteria selected]3 10

seconds4 Daily and monthly traffic revenue report

generation 3 seconds

5 Uploading of parameters from PCS25 seconds

From the time parametersare changed at TOCCSuntil download at PCS iscompleted

6 Time to display inquiry screen 3 seconds

CPU loading when working on:a) the system program during normaloperationb) processing of on-demand display andprintout function

7

c) uploading and validation process

60%

8 Time delay between operator action andscreen display 5 seconds

After clicking each of theoptions in the menu untilscreen displays the details

9 Time delay between operator action andprintout 15 seconds

10 Time delay between operator action andscreen display for exceptionally largedatabase table (e.g. Cash/individual detail

10 secondsAfter clicking each of theoptions in the menu untilscreen displays the details


12/20


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


transaction)11 Time delay between operator action and

printout for exceptionally large databasetable (e.g. Cash/individual detailtransaction)

20 - 120seconds

After Print button is clickeduntil the report is generated

12 Time to upload data to PCS using externalmedium i.e., thumb drive for one completeday of data from the lane if network failed

5 minutesAfter clicking Upload buttonuntil data transfer iscompleted

The functionality of each component listed on Table 8.1.8 shall also be observed andnoted for one complete random incident or activity selected.

8.1.8 Maxi Booth Equipment

Item Equipment Remarks1 Plaza Computer System Server2 PCS Server Monitor3 PCS Server Keyboard4 PCS Server Mouse5 Real-Time Monitoring Console6 RTMC Monitor7 RTMC Keyboard8 RTMC Mouse9 Toll Supervisor Terminal

10 TST Monitor11 TST Keyboard12 TST Mouse13 Tour-of-Duty Terminal14 TOD Monitor15 TOD Keyboard16 TOD Mouse17 TOD Printer (Laser)18 Operations Printer (Laser)19 Maintenance Printer (Dot Matrix)20 ISO Card Reader 121 ISO Card Reader 222 ISO Card Reader 323 IP Phone 124 IP Phone 225 Router26 Network Switch27 Uninterruptible Power Supply28 Transient Voltage Surge Suppressor Stage 129 Transient Voltage Surge Suppressor Stage 230 Transient Voltage Surge Suppressor Stage 3


13/20


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


Performance test for the toll operations center application shall be conducted byobserving and taking note of the items enumerated on Table 8.1.9 for one randomactivity selected.

8.1.9 Toll Operations Center ( TOC) Application Performance

Item System Function Average Remarks1 Time to buildup new data entry [depends

on extent of data information]1 5 seconds

After Submit button isclicked (when transactioninfo has been entered onthe field) until systemreflects it

2 Time to generate summary reports (dailyand monthly)

3 20seconds

3 CPU loading when working on:a) the system program during normaloperationb) processing of on-demand display andprintout functionc) uploading and validation process

60%



5 Time delay between operator action andprintout 15 seconds

6 Time delay between operator action andscreen display for exceptionally largedatabase table (e.g. all summary reports).

5 15seconds


7 Time delay between operator action andprintout for exceptionally large databasetable (e.g. all summary reports)

20 - 120seconds

After Print button is clickeduntil the report is generated

8 Time to upload PCS parameters fromTOCCS using external medium i.e., thumbdrive if network failed

1 - 5 minutesAfter clicking Upload buttonuntil data transfer iscompleted

Accuracy of reports listed on Table 8.1.10 as generated at the toll operations centershall be verified by an audit team composed of nominated representatives.

8.1.10 TOC Generated Reports

Item Report Remarks1 Comprehensive Report2 Daily Cash Revenue3 Daily Traffic Revenue by User (Cash)4 Daily Traffic Revenue by User (Service)5 Daily Traffic Volume by User (All MOP)6 Daily Traffic Volume by User (Cash)7 Daily Traffic Volume by User (Exempt)


14/20


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


8 Daily Traffic Volume by User (HPMC)9 Daily Traffic Volume by User (Service)

10 Daily Traffic Volume by User (Violations)

Accuracy of the Concessionaire reports listed on Table 8.1.11 as generated at the tolloperations center shall be verified by an audit team from the Concessionaire.

8.1.11 Concessionaire Reports

Item Report Remarks1 Toll Operations Report (All Plazas)2 Toll Operations Report [per plaza] 3 Traffic Volume by Toll Plaza (All Plazas)4 Traffic Volume by Vehicle Classification (All

Plazas)5 Traffic Revenue by Toll Plaza (All Plazas)6 Traffic Revenue by Vehicle Classification

(All Plazas)7 Toll Revenue and Traffic Volume (All

Plazas)8 Toll Traffic Volume by Plaza (All Plazas)9 Total Cash Revenue by Plaza (All Plazas)

10 Traffic Volume by Vehicle Classification[per plaza]

11 Daily Traffic Volume by User (Cash) [per

plaza] 12 Daily Traffic Volume by User (Service) [per

plaza] 13 Daily Traffic Volume by User (Exempt) [per

plaza] 14 Daily Traffic Volume by User (Violations)

[per plaza] 15 Daily Traffic Volume by User (All MOP)

[per plaza] 16 Traffic Revenue by Vehicle Classification

[per plaza] 17 Daily Traffic Revenue by User (Cash) [per

plaza] 18 Daily Traffic Revenue by User (Service)

[per plaza] 19 Daily Traffic Revenue by User (Exempt)

[per plaza] 20 Daily Cash Revenue [per plaza] 21 Toll Revenue and Traffic Volume [per

plaza]

Performance test for the smart card batch processing application shall be conducted byobserving and taking note of the items enumerated on Table 8.1.12. Recommendedsampling size is 200 pieces.


15/20


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


8.1.12 Smartcard Batch Processing Application Performance

Item System Function Average Remarks1 Time to initialize a new card

5 seconds

Upon clicking of Startbutton to encodeinformation onto the carduntil the card is dropped offby the machine.

2 Time to create a pre-issued card

5 seconds

Upon clicking of Startbutton to encodeinformation onto the carduntil the card is dropped offby the machine.


After clicking each of theoptions in the menu until

screen displays the details 4 Time to access data from TOCCS

1 - 3 seconds

After login ID and passwordhave been entered for theBPM to authenticate themwith the TOCCS databaseuntil being logged in andable to access the system.

The functionality of each component listed on Table 8.1.13 shall also be observed andnoted for one random activity selected.

8.1.13 TOC Computer Room Equipment

Item Equipment Remarks1 TOC Computer System Server2 TOCCS Server Monitor3 TOCCS Server Keyboard4 TOCCS Server Mouse5 Network Monitoring System Server6 NMS Server Monitor7 NMS Server Keyboard

8 NMS Server Mouse9 TOC Computer System Workstation 1

10 TOCCS Workstation 1 Monitor11 TOCCS Workstation 1 Keyboard12 TOCCS Workstation 1 Mouse13 TOC Computer System Workstation 214 TOCCS Workstation 2 Monitor15 TOCCS Workstation 2 Keyboard16 TOCCS Workstation 2 Mouse17 Operations & Tour-of-Duty Printer 1

18 Operations & Tour-of-Duty Printer 219 Smart Card Batch Processing Machine


16/20


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


20 ISO Card Encoder21 ISO Card Reader 1

22 ISO Card Reader 223 IP Phone 124 IP Phone 225 IP Phone 326 Router27 Network Switch28 Uninterruptible Power Supply29 Transient Voltage Surge Suppressor Stage 130 Transient Voltage Surge Suppressor Stage 2


17/20


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


8.2 AVC SYSTEM PERFORMANCE

The accuracy of the Automatic Vehicle Classification (AVC) system shall be 1 error inevery 1000 vehicles based on the following assumptions:

1. The traffic sampling used for measurement shall be the statistical representativeof actual vehicles for the accuracy required on the lane.

2. This guarantee applies only to the correct determination of the classificationbased on the AVC criteria above.

3. The results compiled are presented in as it is monitored basis. It is not theintention 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 todetermine 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 andverified against the actual vehicle classification noted down on the AVCSampling Record by the designated arbiter (recommended personnel will befrom the Consultant).

3. The samples recorded on the AVC Sampling Record will be used to analyze thediscrepancies reported during the performance testing period.

During the performance test, it is recommended that there should be nomalfunction of the AVC equipment and that all peripherals interfaced to the AVCsystem are in good working condition to obtain precise test results. Otherwise,the said malfunction needs to be repaired first prior to conducting theperformance test.

4. The total number of discrepancies recorded shall be analyzed to determine theactual number of discrepancies that can be attributed to the AVC system.Discrepancies caused by exceptional cases shall not be considered as AVCerrors.


18/20


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


8.2.1 SAMPLE AVC SAMPLING RECORD FORMAT

AVC STATISTICAL SAMPLING RECORD PLAZA ______________ LANE ___ DATE ____________

MVC AVC MVC AVCNO1 2 3 1 2 3

REMARKS NO1 2 3 1 2 3

REMARKS

1 512 523 534 545 556 567 578 589 59

10 60

11 6112 6213 6314 6415 6516 6617 6718 6819 6920 7021 7122 72

23 7324 7425 7526 7627 7728 7829 7930 8031 8132 8233 8334 8435 8536 8637 8738 8839 8940 9041 9142 9243 9344 9445 9546 9647 97

48 9849 9950 100


19/20


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


8.2.2 SAMPLE AVC TEST RESULT SUMMARY

PLAZA :

LANE :DATE :

As Recorded

Total Sampling Recorded A = 1000

Correct Classification B = 996

Incorrect Classification C = 1

Unable to Classify D = 1

Accounted Error (not due to AVC System) E = 2

Classification Rate X1

= (A - D) / A x 100%

AVC Error X2 = (C / A) x 100%

AVC Accuracy X3 = 100% - X2


20/20


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

COMPILED BY: Fujitsu Philippines Inc.All rights reserved Consistent with our policy of continuing product and solution development specifications and solutions shown in

8.3 SAMPLE CONCLUSION REPORT

1. The Performance Test has been successfully carried out in Subic-Clark-TarlacExpressway (SCTEX) at selected lanes, from __(date) ___ to __(date) ___ inaccordance 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 datawere based on actual observations without taking into consideration any possiblefraud, equipment failure, human intervention and the like.

4. A summary of the Performance Test results is shown below:

Clark North ALane 1 2 3 4 5Total Vehicle PassageCorrect ClassificationIncorrect ClassificationUnable to ClassifyAccounted ErrorAVC 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 tabulatedTest Result Summaries as supporting documents.

6. Examples of errors that shall be considered as accounted error in certain casesare as follows: bumper to bumper crossing, bulldozers, human crossing, overloadedvehicles, modified vehicles such as the ones with low profiles, with attached anti-static 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 passthrough. The situation can be improved by replacing the identified failing padsensors. It was also noted that Lanes 2 and 4 have greater vibrations as comparedto other lanes when a heavily loaded trailer passes through. This is another factorthat shall be considered as indirectly contributing to intermittent detection of thebeam while some incorrect classifications recorded from other lanes are mainlycaused by an additional pulse.

SCTEP - Performance Test Procedure Rev6 - Clarifications

Documents