Introductionlinks.indracompany.com.ph/Procurement/ria/Portable Reader... · Web viewPortable Reader User Manual Toll Collection System (TCS) Migration of the Manila North Expressway

Portable Reader User Manual

Toll Collection System (TCS) Migration of the Manila NorthExpressway Project (MNEP)


Project: Toll Collection System (TCS) Migration of the Manila North Expressway Project (MNEP)

Contract Number: 120461

INDRA CUSTOMER

Name Signature Name Signature

Prepared byErwin SoletaOliver Ning

09/09/2015

Reviewed by

Approved by

Authorized by

This document has been prepared by Indra Philippines, Inc. and Egis Projects Philippines, Inc. within the framework of the Toll Collection System (TCS) Migration of the Manila North Expressway Project (MNEP), and cannot be used for a different purpose than that for which it was submitted, totally or partially reproduced, transmitted or reported to any person without Indra Philippines, Inc. and Egis Projects Philippines, Inc. and MNTC expressed authorization.

1.

Doc.Nº: 5052112046110MU00Edit./Rev.: 1/0Date: 09/09/2015



DOCUMENT VERSION CONTROL

This document contains the following pages, and the indicated editions and revisions

Page Edit./Rev. Page Edit./Rev. Page Edit./Rev. Page Edit./Rev.

All 1/0

DOCUMENT CHANGES CONTROL

Edit./Rev. Date Pages Changed Reason

1/0 09/09/2015 All First Version

ii of v Doc.Nr: 5052112046110MU00Edit./Rev.: 1/0

Date: 09/09/2015



INDEX

Chapter Description Page

1. INTRODUCTION............................................................................................................................. 6

2. PREVIOUS CONSIDERATIONS....................................................................................................7

3. REFERENCES................................................................................................................................ 8

4. ABBREVIATIONS AND TERMINOLOGY......................................................................................9

4.1. ABBREVIATIONS.......................................................................................................................................

4.2. TERMINOLOGY..........................................................................................................................................

5. INSTALLING THE APPLICATIONS AND SETTING OF CONFIGURATIONS............................10

5.1. PDA IMPORTER.......................................................................................................................................10

5.2. FARES, ROUTES, AND USERS FILES GENERATOR...........................................................................13

5.3. DATABASE CONFIGURATION...............................................................................................................15

6. GENERATION AND UPDATE OF USERS, FARES, AND ROUTES FILES................................21

6.1. GENERATION...........................................................................................................................................21

6.2. UPDATE.................................................................................................................................................... 22

7. PORTABLE READER UNIT HANDLING.....................................................................................24

8. PDA APPLICATION..................................................................................................................... 27

9. PDA IMPORTER........................................................................................................................... 34

10. CASH UP APPLICATION.............................................................................................................38

11. BACK OFFICE.............................................................................................................................. 39

11.1. COLLECTION DISCREPANCY................................................................................................................39

11.2. VIEW TRAVELS........................................................................................................................................39

12. REPORTS..................................................................................................................................... 41

13. FREQUENTLY ASKED QUESTIONS..........................................................................................42

A. APPENDIX F: PDA BIP-1300 4GB TECHNICAL SPECIFICATIONS..........................................47

Doc.Nr: 5052112046110MU00Edit./Rev.: 1/0Date: 09/09/2015

iii of v



FIGURES INDEX

Description Page

Figure 1 Windows Registry......................................................................................................................................10

Figure 2 ODBC Settings..........................................................................................................................................11

Figure 3 PDA Impoter Shortcut................................................................................................................................12

Figure 4 PDA Importer Login Screen.......................................................................................................................13

Figure 5 Database.properties XML Configuration...................................................................................................13

Figure 6 File Samples..............................................................................................................................................15

Figure 7 Portable Reader Windows Batch File........................................................................................................21

Figure 8 Loading of Configuration Files...................................................................................................................22

Figure 9 Loading Failure..........................................................................................................................................23

Figure 10 Multiple Parameter Files..........................................................................................................................23

Figure 11 Holding the portable reader (front and back)...........................................................................................24

Figure 12 Opening the receipt roll lid.......................................................................................................................24

Figure 13 Replacing the receipt roll.........................................................................................................................25

Figure 14 Tearing out the receipt out of the unit......................................................................................................25

Figure 15 Swiping the ticket.....................................................................................................................................26

Figure 16 PDA Login Screen...................................................................................................................................27

Figure 17 Plaza Selection........................................................................................................................................28

Figure 18 Classification Screen...............................................................................................................................28

Figure 19 Ticket Management.................................................................................................................................29

Figure 20 Plaza Origin Selection.............................................................................................................................30

Figure 21 Payment Processing................................................................................................................................30

Figure 22 Receipt Printing Error..............................................................................................................................31

Figure 23 PDA Receipt Sample...............................................................................................................................32

Figure 24 PDA Importer Login Screen.....................................................................................................................34

Figure 25 PDA Data Importer..................................................................................................................................34

Figure 26 Process - File Selection...........................................................................................................................35

Figure 27 Process Execution...................................................................................................................................36

Figure 28 Successful File Processing......................................................................................................................36

Figure 29 Failed File Processing.............................................................................................................................37

Figure 30 Cash Up................................................................................................................................................... 38

Figure 31 Collection Discrepancy............................................................................................................................39

iv of v Doc.Nr: 5052112046110MU00Edit./Rev.: 1/0

Date: 09/09/2015



Figure 32 View Travels............................................................................................................................................40

Figure 33 Daily Lane Traffic Per MOP.....................................................................................................................41

Figure 34 Revenue Per Lane POS..........................................................................................................................41

Figure 35 Error: destination folder to copy files does not exist................................................................................42

Figure 36 An error has occurred when processing the file (Database Exception)...................................................43

Figure 37 An error has occurred when processing the file......................................................................................43

Figure 38 Error loading file users. The application will close...................................................................................44

Figure 39 Impossible to print receipt. No paper.......................................................................................................45

Figure 40 Summary receipt can't be printed............................................................................................................45

Figure 41 Error moving shift file to SD card. Not found SD card.............................................................................46

TABLES INDEX

Description Page

Table 1 ID_PLACE Values.......................................................................................................................................11

Table 2 PDA_C_PLACES Configuration.................................................................................................................16

Table 3 Virtual PLACE_ID Values...........................................................................................................................16

Table 4 PDA Receipt Structure................................................................................................................................32

.


v of v



1. INTRODUCTION

This document details the end user guideline in the usage of the portable reader (PDA BIP-1300) as a

toll collection tool. The main objective of the portable reader is to serve as a virtual lane that can be

used to cater to cash transactions in the North Luzon Expressway.

It will be useful in managing peak seasons where traffic is high and counting of manual receipts is nor -

mally done. The PDA shifts will be available in Cash Up Application, while transits and revenue decla-

rations will be viewable in View Travels Module in the Back Office.

Along with the PDA unit, a corresponding plaza workstation application will be installed to import infor -

mation from the PDA.

6 of 47 Doc.Nr: 5052112046110MU00Edit./Rev.: 1/0

Date: 09/09/2015



2. PREVIOUS CONSIDERATIONS

The PDA being a device that will be used in different plazas, it needs to be ready to behave

dynamically, depending on the plaza selected by the user. This means the routes and fares of all the

plazas will be downloaded to each device, having all the devices with the exact same set routes and

fares. From the complete fare matrix, the PDA’s fares upon usage will take the fare table of the plaza

chosen.

As a security measure, the PDA plaza workstation application (PDA Importer) will only allow database

import of jobs corresponding to the plaza selected. This is a setting the plaza database and the

workstations registries.


7 of 47



3. REFERENCES

Ref. Document Name Document Number Version, Date

1. Portable Reader - Cash Payment - Write up - -

2. Portable Reader - Cash Payment 5052112046112DS10 04/08/2015


Date: 09/09/2015



4. ABBREVIATIONS AND TERMINOLOGY

4.1. ABBREVIATIONS

MNTC Manila North Tollways Corporation

MNEP Manila North Expressway Project

TCS Toll Collection System

WIR Work Inspection Request

PDA Portable Digital Assistant

4.2. TERMINOLOGY

Validation Process that assures the correct Product is developed, that is, that the Product complies with its intended use.

Verification Process that assures that the Product is developed accordingly to its predefined Requirements.

Synchronization Workstation (PDA Importer)

Interface equipment where the PDA will be connected to be updated with the data needed to operate in the toll system.


9 of 47



5. INSTALLING THE APPLICATIONS AND SETTING OF CONFIGURATIONS

5.1. PDA IMPORTER

1. Windows Registry

Figure 1 Windows Registry

a. Unpack the registry export provided.b. Set the PlaceID value to the ID_PLACE of the plaza where the workstation is located.

The list of values are as follows:

ID_PLACE Plaza Name16843008 Balintawak16843264 Mindanao16843520 Valenzuela NB16843776 Valenzuela SB16844032 Meycauayan NB16844288 Meycauayan SB16844544 Marilao NB16844800 Marilao SB16845056 Bocaue Barrier CS16849664 Bocaue Barrier OS16849152 Bocaue Interchange NB16845312 Bocaue Interchange SB16845568 Tabang16845824 Balagtas16846080 Sta Rita NB


Date: 09/09/2015



16846336 Sta Rita SB16846592 Pulilan NB16846848 Pulilan SB16847104 San Simon NB16847360 San Simon SB16847616 San Fernando NB16847872 San Fernando SB16848128 Mexico16848384 Angeles16848640 Dau CS16849408 Dau IC NB16849920 Dau IC SB16850176 Karuhatan OS

Table 1 ID_PLACE Values

2. ODBC Entriesa. Create the following ODBC in the workstation. These entries are needed to access

the database. If these are not created, file import cannot be completed. The SQL Server has to be configured to point to the database of the plaza where the worksta-tion is located.

Figure 2 ODBC Settings

3. PDA Importer GUIa. Copy the PDA Importer GUI folder to C:\Peaje


11 of 47



b. Create the following folders:i. C:\Peaje\PDA\files folder will contain the files to be inserted to the DBii. C:\Peaje\processed_error folder will contain the files that were not com-

pletely processediii. C:\Peaje\processed_ok folder will contain the files that were completely

processedc. Create a shortcut of the PDA Imported executable file and use the name of the reg-

istry as the shortcut parameter.

Figure 3 PDA Impoter Shortcut

4. Installation Validation.a. In order to validate that the application has been installed, open the application short-

cut and the application should open properly


Date: 09/09/2015



Figure 4 PDA Importer Login Screen

5.2. FARES, ROUTES, AND USERS FILES GENERATOR

1. Copy the given folder to C:\Peaje\BO\2. Create the following folders:

a. C:\Peaje\PDAFILES\FARESb. C:\Peaje\PDAFILES\FARES\ERRORc. C:\Peaje\PDAFILES\FARES\HISTORYd. C:\Peaje\PDAFILES\ROUTESe. C:\Peaje\PDAFILES\ROUTES\ERRORf. C:\Peaje\PDAFILES\ROUTES\HISTORYg. C:\Peaje\PDAFILES\USERh. C:\Peaje\PDAFILES\USER\ERRORi. C:\Peaje\PDAFILES\USER\HISTORY

3. Configure the database.properties file in order to point to the Back Office database where the information will be extracted.

Figure 5 Database.properties XML Configuration


13 of 47



4. Edit the applicationContext.xml file to set the folders where the files will be located after gener-ation. See highlighted snippets.

<bean id="userXmlGeneratorDAO" class="es.indra.peaje.batch.dao.user.impl.UserXmlGeneratorDAOImpl">

<property name="fileNameFormatUser" value="Users_{0,time,yyyyMMddHHmmss}.xml"/>

<property name="userFilePath" value="C:\\Peaje\\PDAFILES\\USER"/><property name="userFilePathOld" value="C:\\Peaje\\PDAFILES\\USER\\HISTORY"/><property name="userFilePathError" value="C:\\Peaje\\PDAFILES\\USER\\ERROR"/><property name="fileTypeUser" value="105"/>

</bean>

<bean id="fareXmlGeneratorDAO" class="es.indra.peaje.batch.dao.fare.impl.FareXmlGeneratorDAOImpl">

<property name="fileNameFormatFare" value="Fares_{0,time,yyyyMMddHHmmss}.xml"/><property name="faresFilePath" value="C:\\Peaje\\PDAFILES\\FARES"/><property name="faresFilePathOld" value="C:\\Peaje\\PDAFILES\\FARES\\HISTORY"/><property name="faresFilePathError" value="C:\\Peaje\\PDAFILES\\FARES\\ERROR"/><property name="fileTypeFares" value="106"/>

</bean>

<bean id="routeXmlGeneratorDAO" class="es.indra.peaje.batch.dao.route.impl.RouteXmlGenerator-DAOImpl">

<property name="fileNameFormatRoute" value="Routes_{0,time,yyyyMMddHHmmss}.xml"/><property name="routesFilePath" value="C:\\Peaje\\PDAFILES\\ROUTES"/><property name="routesFilePathOld" value="C:\\Peaje\\PDAFILES\\ROUTES\\HISTORY"/><property name="routesFilePathError" value="C:\\Peaje\\PDAFILES\\ROUTES\\ERROR"/>

<property name="fileTypeRoutes" value="107"/></bean>

5. Modify the following parameters inside the applicationContext.xml file to these recommended settings. See highlighted snippets.

a. File generation. The following lines will allow/disallow generation of fares, users, and routes files.

<property name="isGenerateFileX"><list>

<value>true</value> <value>true</value> 

<value>true</value> </list>

</property>b. Advance file generation. The following line if set to true, will allow files to be generated

even if there is no change in the version. If set to false, the files will not be generated if there is no update. See highlighted snippet.

<property name="ignoreMaintVersion" value="true"/>

6. Installation Validationa. In order to validate that the application has been installed, run the Windows Batch File

and check if the files are generated according to the settings used.


Date: 09/09/2015



Figure 6 File Samples

5.3. DATABASE CONFIGURATION

1. PDA_PLACES – This table contains the ID_PLACE of the virtual lanes that would represent the data from the PDA. It has to be configured properly per plaza in order to accept from all the PDA units the jobs only for that plaza. This table has to be updated every time there is a new PDA unit. Example:

ID_PDA PLAZA ID_PLACE_VIRTUAL00001 16843008 1684315800002 16843008 1684315800003 16843008 1684315800004 16843008 1684315800005 16843008 1684315800006 16843008 1684315800007 16843008 1684315800008 16843008 1684315800009 16843008 1684315800010 16843008 1684315800011 16843008 1684315800012 16843008 1684315800013 16843008 1684315800014 16843008 1684315800015 16843008 16843158


15 of 47



00016 16843008 1684315800017 16843008 1684315800018 16843008 1684315800019 16843008 1684315800020 16843008 16843158

Table 2 PDA_C_PLACES Configuration

The sample configuration above means that the plaza will accept jobs from the indicated PDA ID’s (ID_PDA) from Balintawak. PLAZA and ID_PLACE_VIRTUAL values are as follows

PLAZA ID_PLACE_VIRTUAL Plaza Name16843008 16843158 Balintawak16843264 16843414 Mindanao16843520 16843670 Valenzuela NB16843776 16843926 Valenzuela SB16844032 16844182 Meycauayan NB16844288 16844438 Meycauayan SB16844544 16844694 Marilao NB16844800 16844950 Marilao SB16845056 16845206 Bocaue Barrier CS16849664 16849814 Bocaue Barrier OS16849152 16849302 Bocaue Interchange NB16845312 16845462 Bocaue Interchange SB16845568 16845718 Tabang16845824 16845974 Balagtas16846080 16846230 Sta Rita NB16846336 16846486 Sta Rita SB16846592 16846742 Pulilan NB16846848 16846998 Pulilan SB16847104 16847254 San Simon NB16847360 16847510 San Simon SB16847616 16847766 San Fernando NB16847872 16848022 San Fernando SB16848128 16848278 Mexico16848384 16848534 Angeles16848640 16848790 Dau CS16849408 16849558 Dau IC NB16849920 16850070 Dau IC SB16850176 16850326 Karuhatan OS

Table 3 Virtual PLACE_ID Values


Date: 09/09/2015



2. Trigger – This trigger has to be updated every time a new plaza is added. This trigger trans-forms the PDA shift to a job that will be shown in the Cash Up application. The yellow high-lighted line must contain the virtual PLACE_ID value of that specific server.

ALTER TRIGGER [dbo].[TG_TSHIFTSBALANCE] ON [dbo].[L_D_TSHIFTSBALANCE]AFTER INSERT AS DECLARE @TURNO INT DECLARE @ID_LUGAR INT

DECLARE @NUM_VEHICULOS INT DECLARE @NUM_TICKETS INT

DECLARE @MPASO_NORMAL INT DECLARE @MPASO_VIOLACION INT DECLARE @MPASO_SIMULADO INT DECLARE @MPASO_FORZADO INT DECLARE @MPASO_ANULADO INT DECLARE @MPASO_COMITIVA INT DECLARE @MPASO_MARCHA_ATRAS INT DECLARE @MPASO_DESVIO INT DECLARE @MPASO_SIMULADO_TUTOR INT DECLARE @MPASO_INTERRUMPIDO_TUTOR INT DECLARE @MPASO_MODOPASO1 INT DECLARE @MPASO_MODOPASO2 INT

DECLARE @MPAGO_METALICO INT DECLARE @MPAGO_FRANQUICIA INT DECLARE @MPAGO_BONO INT DECLARE @MPAGO_CREDITO INT DECLARE @MPAGO_DIFERIDO INT DECLARE @MPAGO_TICKETS INT DECLARE @MPAGO_TAGS INT DECLARE @MPAGO_PREPAGO INT DECLARE @MPAGO_LIBRE INT DECLARE @MPAGO_MODOPAGO1 INT DECLARE @MPAGO_MODOPAGO2 INT

DECLARE @IMP_METALICO FLOAT DECLARE @IMP_FRANQUICIA FLOAT DECLARE @IMP_BONO FLOAT DECLARE @IMP_CREDITO FLOAT DECLARE @IMP_DIFERIDO FLOAT DECLARE @IMP_TICKETS FLOAT DECLARE @IMP_TAGS FLOAT DECLARE @IMP_PREPAGO FLOAT DECLARE @IMP_LIBRE FLOAT DECLARE @IMP_MODOPAGO1 FLOAT DECLARE @IMP_MODOPAGO2 FLOAT DECLARE @IMP_DOLARES FLOAT

DECLARE @IMP_METALICO_REMOTO FLOAT DECLARE @IMP_DOLARES_REMOTO FLOAT DECLARE @IMP_METALICO_PARC FLOAT DECLARE @IMP_RECARGAS FLOAT DECLARE @PENDING_VEH INT DECLARE @AMOUNT_CASH_VAL INT

DECLARE CursorTShiftBalance CURSOR FOR


17 of 47



SELECT NUM_SHIFT_ACCOUNTANT, ID_PLACE FROM Inserted BEGIN

OPEN CursorTShiftBalance

FETCH NEXT FROM CursorTShiftBalance INTO @TURNO, @ID_LUGAR

WHILE @@FETCH_STATUS = 0 BEGIN

SELECT @NUM_VEHICULOS = COUNT(*), @NUM_TICKETS = 0, @MPASO_NORMAL= ISNULL(SUM(CASE WHEN PAYMENT_MODE!=1 THEN 1 ELSE 0 END),0), @MPASO_VIOLACION= ISNULL(SUM(CASE WHEN (TYPE_VIOLATION_1 IS NOT NULL AND ID_VIOLATION_1 IS NOT NULL) THEN 1 ELSE 0 END),0), @MPASO_SIMULADO= ISNULL(SUM(CASE WHEN EXIT_MODE=0 THEN 1 ELSE 0 END),0), @MPASO_FORZADO= ISNULL(SUM(CASE WHEN ((LANE_MODE=6 OR LANE_MODE=7 AND LANE_MODE=11 AND LANE_MODE=14 AND LANE_MODE=16) AND TYPE_VIOLATION_1 IS NOT NULL AND ID_VIOLATION_1 IS NOT NULL) THEN 1 ELSE 0 END),0), @MPASO_ANULADO= 0, @MPASO_COMITIVA= ISNULL(SUM(CASE WHEN ID_CONVOY IS NOT NULL THEN 1 ELSE 0 END),0), @MPASO_MARCHA_ATRAS= ISNULL(SUM(CASE WHEN DIRECTION!=1 THEN 1 ELSE 0 END),0), @MPASO_DESVIO= 0, @MPASO_SIMULADO_TUTOR= 0, @MPASO_INTERRUMPIDO_TUTOR= 0, @MPASO_MODOPASO1= 0, @MPASO_MODOPASO2= 0,

@MPAGO_METALICO= ISNULL(SUM(CASE WHEN PAYMENT_MODE=2 THEN 1 ELSE 0 END),0), @MPAGO_FRANQUICIA= 0, @MPAGO_BONO= 0, @MPAGO_CREDITO= ISNULL(SUM(CASE WHEN PAYMENT_MODE=3 THEN 1 ELSE 0 END),0), @MPAGO_DIFERIDO= 0, @MPAGO_TICKETS= 0, @MPAGO_TAGS= ISNULL(SUM(CASE WHEN PAYMENT_MODE=5 THEN 1 ELSE 0 END),0), @MPAGO_PREPAGO= 0, @MPAGO_LIBRE= ISNULL(SUM(CASE WHEN PAYMENT_MODE=6 THEN 1 ELSE 0 END),0), @MPAGO_MODOPAGO1= 0, @MPAGO_MODOPAGO2=0,

@IMP_METALICO=ISNULL(SUM(CASE WHEN PAYMENT_MODE=2 THEN (CASE WHEN TYPE_CURRENCY=2 THEN -AMOUNT_RETURNED ELSE (CASE WHEN ID_CONVOY IS NOT NULL THEN CONVOY_AMOUNT+AMOUNT_TO_PAY ELSE AMOUNT_TO_PAY END)END) ELSE 0 END),0), @IMP_FRANQUICIA=0, @IMP_BONO= 0, @IMP_CREDITO= ISNULL(SUM(CASE WHEN PAYMENT_MODE=3 THEN (CASE WHEN ID_CONVOY IS NOT NULL THEN CONVOY_AMOUNT+AMOUNT_TO_PAY ELSE AMOUNT_TO_PAY END) ELSE 0 END),0), @IMP_DIFERIDO= 0, @IMP_TICKETS= 0, @IMP_TAGS= ISNULL(SUM(CASE WHEN PAYMENT_MODE=5 THEN AMOUNT_TO_PAY ELSE 0 END),0), @IMP_PREPAGO= 0, @IMP_LIBRE= ISNULL(SUM(CASE WHEN PAYMENT_MODE=6 THEN AMOUNT_TO_PAY ELSE 0 END),0), @IMP_MODOPAGO1 = 0, @IMP_MODOPAGO2 = 0, @IMP_DOLARES = ISNULL(SUM(CASE WHEN TYPE_CURRENCY=2 THEN CURRENCY_AMOUNT ELSE 0 END),0), @IMP_METALICO_PARC = ISNULL(SUM(CASE WHEN PAYMENT_MODE=4 AND TYPE_CURRENCY=1 THEN CURRENCY_AMOUNT ELSE 0 END),0) --FROM (SELECT * FROM TTRANSITOS UNION SELECT * FROM H_TTRANSITOS) AS TABLA_TRANSITOS FROM (SELECT * FROM L_D_TTRANSITS UNION SELECT * FROM L_H_TTRANSITS) AS TABLA_TRANSITOS WHERE TABLA_TRANSITOS.ID_SHIFT_ACCOUNTANT=@TURNO AND TABLA_TRANSITOS.ID_PLACE=@ID_LUGAR --EFECTIVO EN CASO DE PAGOS REMOTOS


Date: 09/09/2015

mailto:TABLA_TRANSITOS.ID_PLACE%3D@ID_LUGAR

mailto:TABLA_TRANSITOS.ID_SHIFT_ACCOUNTANT%3D@TURNO



SELECT @IMP_METALICO_REMOTO = ISNULL(SUM(CASE WHEN PAYMENT_MODE=2 THEN (CASE WHEN TYPE_CURRENCY=2 THEN AMOUNT_TO_PAY - CURRENCY_AMOUNT*CURRENCY_PRICE ELSE AMOUNT_TO_PAY END) ELSE 0 END),0), @IMP_DOLARES_REMOTO = ISNULL(SUM(CASE WHEN PAYMENT_MODE=2 AND TYPE_CURRENCY=2 THEN CURRENCY_AMOUNT ELSE 0 END),0) FROM (SELECT * FROM L_D_TTRANSITS_REMOTE UNION SELECT * FROM L_H_TTRANSITS_REMOTE) AS TABLA_TRANSITOS_REMOTOS WHERE TABLA_TRANSITOS_REMOTOS.ID_SHIFT_ACCOUNTANT_REMOTE=@TURNO AND TABLA_TRANSITOS_REMOTOS.ID_PLACE=@ID_LUGAR --EFECTIVO EN LAS RECARGAS SELECT @IMP_RECARGAS = ISNULL(SUM(RECHARGE_AMOUNT_RECEIVED),0) FROM (SELECT * FROM L_D_TRANSITS_AUX UNION SELECT * FROM L_H_TRANSITS_AUX) AS TABLA_AUX, (SELECT * FROM L_D_TTRANSITS UNION SELECT * FROM L_H_TTRANSITS) AS TABLA_TRANSITOS, (SELECT * FROM L_D_TRANSITS_RECHARGES UNION SELECT * FROM L_H_TRANSITS_RECHARGES) AS TABLA_RECHARGES WHERE TABLA_AUX.ID_PLACE = TABLA_TRANSITOS.ID_PLACE AND TABLA_AUX.ID_TRANSIT = TABLA_TRANSITOS.ID_TRANSIT AND TABLA_AUX.TYPE_TRANSIT = TABLA_TRANSITOS.TYPE_TRANSIT AND TABLA_TRANSITOS.ID_SHIFT_ACCOUNTANT=@TURNO AND TABLA_TRANSITOS.ID_PLACE=@ID_LUGAR AND TABLA_RECHARGES.ID_TRANSIT = TABLA_TRANSITOS.ID_TRANSIT AND TABLA_RECHARGES.ID_PLACE = TABLA_TRANSITOS.ID_PLACE AND TABLA_RECHARGES.TYPE_TRANSIT = TABLA_TRANSITOS.TYPE_TRANSIT --Actualizamos los totales con los pagos remotos y los parciales SET @IMP_METALICO = @IMP_METALICO + @IMP_METALICO_REMOTO + @IMP_METALICO_PARC + @IMP_RECARGAS SET @IMP_DOLARES = @IMP_DOLARES + @IMP_DOLARES_REMOTO -- El procedimiento solo estaría activo en Via, por lo tanto en numero de vehículos pendientes de validar es el mismo que el total SET @PENDING_VEH = @NUM_VEHICULOS -- El procedimiento solo estaría activo en Vía, por lo tanto la cantidad de validación es la de cash. SET @AMOUNT_CASH_VAL = @IMP_METALICO UPDATE L_D_TSHIFTSBALANCE SET N_VEHICLES=@NUM_VEHICULOS, N_TICKETS_ENTRY=@NUM_TICKETS, NORMAL=@MPASO_NORMAL, VIOLATIONS=@MPASO_VIOLACION, SIMULATED=@MPASO_SIMULADO, FORCED=@MPASO_FORZADO, ANULLED=@MPASO_ANULADO, CONVOY=@MPASO_COMITIVA, REVERSE=@MPASO_MARCHA_ATRAS, DEVIATION=@MPASO_DESVIO, SIMULATED_TUTOR=@MPASO_SIMULADO_TUTOR, INTERRUPTED_TUTOR=@MPASO_INTERRUMPIDO_TUTOR, PASSMODE1=@MPASO_MODOPASO1, PASSMODE2=@MPASO_MODOPASO2,

CASH=@MPAGO_METALICO, FRANCHISE=@MPAGO_FRANQUICIA, BOND=@MPAGO_BONO, CREDIT=@MPAGO_CREDITO, DEFERRED=@MPAGO_DIFERIDO, TICKETS=@MPAGO_TICKETS, TAGS=@MPAGO_TAGS, PREPAID=@MPAGO_PREPAGO, FREE=@MPAGO_LIBRE, PAYMENTMODE1=@MPAGO_MODOPAGO1, PAYMENTMODE2=@MPAGO_MODOPAGO2,

AMOUNT_CASH=@IMP_METALICO,


19 of 47

mailto:TABLA_TRANSITOS.ID_PLACE%3D@ID_LUGAR

mailto:TABLA_TRANSITOS.ID_SHIFT_ACCOUNTANT%3D@TURNO

mailto:TABLA_TRANSITOS_REMOTOS.ID_PLACE%3D@ID_LUGAR

mailto:TABLA_TRANSITOS_REMOTOS.ID_SHIFT_ACCOUNTANT_REMOTE%3D@TURNO



AMOUNT_FRANCHISE=@IMP_FRANQUICIA, AMOUNT_BOND=@IMP_BONO, AMOUNT_CREDIT=@IMP_CREDITO, AMOUNT_DEFERRED=@IMP_DIFERIDO, AMOUNT_TICKETS=@IMP_TICKETS, AMOUNT_TAGS=@IMP_TAGS, AMOUNT_PREPAID=@IMP_PREPAGO, AMOUNT_FREE=@IMP_LIBRE, AMOUNT_PAYMENTMODE1=@IMP_MODOPAGO1, AMOUNT_PAYMENTMODE2=@IMP_MODOPAGO2, AMOUNT_DOLLARS=@IMP_DOLARES, PENDING_VALIDATION_VEHICLES=@PENDING_VEH, AMOUNT_CASH_VALIDATION=@AMOUNT_CASH_VAL WHERE NUM_SHIFT_ACCOUNTANT=@TURNO AND ID_PLACE=@ID_LUGAR AND ID_PLACE in (16846230)

FETCH NEXT FROM CursorTShiftBalance INTO @TURNO, @ID_LUGAR END

CLOSE CursorTShiftBalance DEALLOCATE CursorTShiftBalance

END

GO


Date: 09/09/2015



6. GENERATION AND UPDATE OF USERS, FARES, AND ROUTES FILES

The users, fares, and routes files need to be generated and uploaded into the PDA for it to contain these updated parameters. The file can be generated from any FOE workstation application that has connection to the Back Office server where the application is properly installed.

6.1. GENERATION

1. Run the windows batch file

Figure 7 Portable Reader Windows Batch File

2. To validate the operation, the files should be generated in their respective locations depending on the settings made in the .jar file.


21 of 47



The filename format is as follows:Fares_20150416171501

Fares Parameter type20150416171501 Date and time of generation (YYYYMMDDhhminss, military time)

6.2. UPDATE

1. Connect the PDA to the workstation where the parameter files are generated.2. Copy the files to the SD card of the portable reader:

a. Fares \Hard Diskb. Routes \Hard Diskc. Users \Hard Disk

3. To validate that the update, the PDA application must be run. It will take time for the PDA to start after the update. If the update is successful, the application will continue to the login screen. Otherwise, an error will be shown.

Figure 8 Loading of Configuration Files

4. If there are multiple parameter files in the same folder, the application will use the one with the most recent generation date. A message will also be shown upon application start up, indicat-ing that there are multiple files for the same parameter.


Date: 09/09/2015



Figure 9 Loading Failure

Figure 10 Multiple Parameter Files


23 of 47



7. PORTABLE READER UNIT HANDLING

This section provides guidelines on how to handle the portable reader.

1. Holding the unit: In holding the portable reader, make sure to slide your hand in the strap at the back of the unit for better grip.

Figure 11 Holding the portable reader (front and back)

2. Replacing the receipt paper roll: a. Open the lid for the receipt roll by pressing the slider down.

Figure 12 Opening the receipt roll lid


Date: 09/09/2015



b. Take out the receipt roll core (if there is) and put in the new roll. Close the lid. There will be a clicking sound to indicate that the lid is properly closed.

Figure 13 Replacing the receipt roll

3. Tearing out the receipt: There is a manual cutter at the mouth of the printer. When tearing the receipt out of the unit, make sure to tear it towards the cutter.

Figure 14 Tearing out the receipt out of the unit


25 of 47



4. Ticket reading: In having a ticket read, make sure to swipe the ticket from one side all the way to the other side of the reader. The entire magnetic band of the ticket should be read by the magnetic reader head of the unit. Do not start nor stop from the middle of the reader.

Figure 15 Swiping the ticket


Date: 09/09/2015



8. PDA APPLICATION

1. Login to the PDA – only users with toll teller and toll supervisor profiles are allowed to log in. Toll supervisors and senior tellers in NLEX have the same profile setting in the Back Office so both will have access to the PDA application

Figure 16 PDA Login Screen

2. Plaza selection – The plaza where the PDA will be used must be chosen from the drop down list box. The radio buttons below the selection indicate whether the plaza selected is an Open System plaza or a Closed System plaza.


27 of 47



Figure 17 Plaza Selection

3. Classification Screen – This is the initial screen of each transaction, which also serves as the default screen of the application. In this screen, the user will be able to do the following:

a. Select class of the vehicle (1, 2a, 2b, 3).b. See the staff number of the user logged in.c. See the shift number the PDA is currently in.d. See the plaza selected as the PDA’s current plaza.e. See the name of the fare version applied in the PDA.

Figure 18 Classification Screen


Date: 09/09/2015



4. Ticket Selection – This screen is only applicable for when the plaza selected is a Closed Sys-tem plaza. If the plaza selected is an Open System plaza, this step is skipped.

Figure 19 Ticket Management

In this screen, the user will be able to do the following:

a. Swipe the ticket. The ticket line will be filled in automatically with the ticket numberb. Select No Ticket. The maximum fare will be automatically charged.c. Select Justified. The user will be transferred to the Origin Selection screen to choose

the justified origin for the motorist. This is to handle justified lost ticket cases. d. Select Damaged. The user will be transferred to the Origin Selection screen to choose

the justified origin for the motoriste. Select Not Justified. The maximum fare will be automatically charged. This is to han-

dle not justified lost ticket cases.


29 of 47



Figure 20 Plaza Origin Selection

5. Processing of payment – This screen shows the summary of the transaction that will be the basis for the payment.

Figure 21 Payment Processing

In this screen, the user will be able to do the following:


Date: 09/09/2015



a. See the class selected. Not editableb. See the origin. Not editablec. See the amount. This is the fare of the trip. Not editabled. Key in the amount received. e. See the change to be returned to the motorist. This is automatically computed while

the amount received is being keyed in.f. Press Cancel. Transaction will return to the default screen (classification screen)g. Press Back. Transaction will return to the ticket management screen if the plaza is a

Closed System plaza. Otherwise, the transaction will return to the default screen (classification screen).

h. Press Receipt. This confirms payment of the transaction.i. Transaction payment will not push through if the amount received is less than

the fare as the PDA only allows cash transactions.ii. If there is no receipt paper, or there is a problem with the receipt printer during

this stage, a prompt will be shown asking the user to save the transit

1. If the transit is saved, the transaction will be recorded, but the official receipt number will not be saved.

2. If the transit is not saved, the transaction will return to the default screen. This is the recommended option so the user can replace the receipt roll and just repeat the transaction.

Figure 22 Receipt Printing Error

6. PDA Receipt Structure


31 of 47



MANILA NORTH TOLLWAYS CORP.TIN: 004-984-856-000

Km 12 NLEX Compound, Balintawak, Caloocan City 1400OFFICIAL RECEIPT

MIN: 110225780Machine Serial Number 1234567891234567891234Accreditation No.: 1234567891234567891234Receipt No.: O1000020000001Date: 07/31/2014Time: 14:39:20Collector: 406464Lane: PDA02Class: 3Plaza: BALINTAWAK - OSEntry:

Toll: 121.43 PhpVAT: 14.57 PhpTotal: 136.00 PhpReceived: 150.00 PhpChange: 14.00 Php

Payment: Cash

Figure 23 PDA Receipt Sample

FIELD DESCRIPTIONMIN: Machine Identification Number provided by BIR. This is unique per PDA.Machine Serial Number Machine Serial Number of the printer. This is unique per PDA.Accreditation No.: Accreditation No. provided by BIR. This is the same for all PDA units.Receipt: System generated receipt number:Date: Date of the transactionTime: Date of the transactionCollector: Staff ID of the teller who processed the transactionLane: PDA IDClass: Class of the vehicle assigned by the toll tellerPlaza: Plaza where the vehicle paidEntry: Entry point of the vehicle (Plaza name)Toll: Base fare without VATVAT: Value Added Tax applied to the toll (12%)Total: Total fare for the tripReceived: Amount tenderedChange: Amount returned to the customerPayment: Means of payment

Table 4 PDA Receipt Structure

All Official Receipt numbers shall follow this format:


Date: 09/09/2015



OBPPPPPEEEEEEE

Where:

O – Official Receipt Identifier (For Official Receipt, this is “O”

B – Network Code (For NLEX, this is 1)

PPPPP – PDA unique identifier (5 digits padded with leading zeroes)

EEEEEEE– Sequential number associated with each PDA (7 digits padded with leading zeroes)


33 of 47



9. PDA IMPORTER

1. Log in to the application with the correct user credentials. Only toll supervisors and senior teller profiles will be allowed to log in. Make sure that the workstation has connection to the plaza server.

Figure 24 PDA Importer Login Screen

2. Upon successful log in, the user will see this default screen:

Figure 25 PDA Data Importer


Date: 09/09/2015



3. Copy files from the PDA to the workstationa. Make sure that the portable reader is plugged into the workstation.b. Access the SD card of the portable reader.c. Copy the files from the SD card to C:\Peaje\PDA\files

4. Process files – This process needs to be done in order to insert the job into the database. a. Select the file to be processed. Each file must be processed one by one. It should be

noted that the order of processing should be chronological. By default, only the jobs from plaza where the workstation located will be shown.

Figure 26 Process - File Selection

Note that the filenames follow this format:

PDAID_ Shift_Plaza ID_date.pda

PDA ID – PDA ID number

Shift – Shift number. This is continuous per PDA.

Plaza ID – This is the ID_PLACE of the plaza.

Date – This is the date and time of the shift (YYYYMMDDhhminss, military time)

Note: For Bocaue Barrier, Bocaue Interchange, and Dau, the ID_PLACE should be changed to “*”. After that, press enter and select the job to be processed.

b. Press Process to insert the job into the system.


35 of 47



Figure 27 Process Execution

5. Upon successful transfer of the files, the following message will be shown:

Figure 28 Successful File Processing

Type 1 Record: Begin of Job

Type 2 Record: Transactions

Type 3 Record: End of Job – If there was no end of job action and the application shut down or automatically restarted, the job will automatically be ended. There will be no Type 3 Record if this happens.


Date: 09/09/2015



6. If the file is not successfully transferred, the following message will be shown. If this message occurs, recheck the network connection and the configuration of the workstation and the server.

Figure 29 Failed File Processing


37 of 47



10. CASH UP APPLICATION

The jobs from the PDA will be available in the Cash Up Application if the file transfer is successful and the servers and workstations are properly configured.

Figure 30 Cash Up

Upon login to the Cash Up Application, the jobs will appear in the jobs pending liquidation. Note that the job number does not refer to the PDA job number. This refers to the order of the job that was transferred to the plaza from the PDA. This is because each PDA handles its own job sequence and for the job number to be continuous in the plaza, they have to be assigned the moment they are transferred to the plaza.

The revenue declaration process will be performed normally, following the same procedure for jobs from the toll lanes. The theoretical revenue will be computed from the transactions from the jobs that are selected, and if there are any other lane jobs that will be cashed up the same time with the PDA jobs, the total theoretical revenue will be cumulative of those jobs.


Date: 09/09/2015



11. BACK OFFICE

The jobs and transactions from the PDA will be viewable in the Back Office in the Collection Discrepancy and View Travels modules respectively.

11.1. COLLECTION DISCREPANCY

The revenue declaration will be viewable in the Collection Discrepancy module as soon as the job gets uploaded to the Back Office. There is no need to perform cash up release for jobs from the PDA.

Figure 31 Collection Discrepancy

11.2. VIEW TRAVELS

The transactions from the PDA will be viewable from the View Travels module as soon as the transactions get uploaded to the Back Office.


39 of 47



Figure 32 View Travels

Similar to the assignment of system job numbers, the transaction numbers are also assigned the moment the transaction gets transferred into the system. This is the rationale behind the recommendation of processing the jobs in a chronological order.

The lane name assigned for the PDA is VL. This stands for Virtual Lane. If multiple PDA units are used in the same plaza, they will all fall under the plaza’s VL where the transaction and job numbers will be assigned.

Although simulated, the transactions will not appear in the Manual Validation Application.


Date: 09/09/2015



12. REPORTS

Transactions from the PDA will be counted in the traffic and revenue reports as if they are transactions from normal toll lanes. The list of reports where the transactions will appear are as follows:

Here is an example of the traffic report where the PDA transactions are reflected:

Figure 33 Daily Lane Traffic Per MOP

Figure 34 Revenue Per Lane POS


41 of 47



13. FREQUENTLY ASKED QUESTIONS

This section includes the frequently asked questions regarding the usage of the portable reader and its accompanying applications

Q1. How do I know if a .pda file has been imported already?A1. Check the C:\Peaje\processed_ok folder of workstations where the PDA importer ap-

plication is installed because all PDA files that have been uploaded to the database successfully are moved to this folder.

Q2. The job I am trying to import is not in the C:\Peaje\processed_ok folder, and I am still not able to import it. What could be the reasons behind?

A1. Check the ID_PLACE of the job. A job can only be imported in the plaza selected upon opening the job.

A2. The job may have already been imported in another workstation in the same plaza.A3. There could be a problem in the connection between the workstation being used and

the plaza server.

Q3. Jobs are reflected in bother processed_error amd processed_ok folders. Why does this hap-pen?

A1. The job has already been imported (processed_ok) and it is being attempted to be im-ported again (processed_error). The software does not allow multiple import of the same job in the same plaza.

A2. An error may have been encountered (network error, configuration error) in the first at-tempt to import the job (processed_error). After the error is fixed, the job is imported again and is successful (processed_ok).

Q4. What are the possible error prompts in the data importer and what do they mean?A1. Error: destination folder to copy files does not exist - This is shown when the source

folder does not exist or the importer settings are not configured properly

Figure 35 Error: destination folder to copy files does not exist

A2. An error has occurred when processing the file (Database Exception) - This is shown when the database configuration to accept the PDA data is not configured properly, or when there is an issue in the strength of connection/network error (this is the case for Bocaue IC NB where the workstation’s connection).


Date: 09/09/2015



Figure 36 An error has occurred when processing the file (Database Exception)

A3. An error has occurred when processing the file - This shown for different events: 1. The user is trying to import a job that is already in the system. 2. The user is trying to import a job from a plaza different from the plaza the

workstation was set to work. 3. Problem in open system plaza importing – this will not happen anymore as

this fixed in ver 06/08/2015.

Figure 37 An error has occurred when processing the file

Q5. What are the possible error prompts in the portable reader application and what do they mean?

A1. "Error loading file user/routes/fare. The application will close". – The SD card contains User, Fare and the Route files needed to start the application. The application won’t run if the SD is not inserted properly. Return the portable reader to the system admin-istrator to load the parameter files.


43 of 47



Figure 38 Error loading file users. The application will close.

A2. Continuous dispensing of receipt – The portable reader application is not designed to run while the device is charging. The application (aside from the OS) is also monitor-ing the device’s battery level. In order to avoid this, make sure that the reader is not in use while it is charging.

A3. PDA device is not charging - Make sure the device is properly placed in the cradle and lights are on. You can also clean the charging terminal or the battery. If it still doesn’t work, it may be damaged. Note: To properly maintain the battery life, the PDA should have a full discharge and charge cycles.

A4. No “hard disk” reflected during exporting – In windows explorer, the “hard disk” folder represents the SD card inserted in the PDA device. Make sure that the SD card is connected or inserted properly.

A5. “Open card reader” error message - This happens when the SD card is not securely inserted or accidentally ejected from the device.

A6. Impossible to print receipt. No Paper – This happens when the transaction is about to finish and there is no receipt paper. There will be a prompt after this that will ask the user whether or not the transaction should be saved.

A7. Summary receipt can’t be printed – This is to inform the user that there will be no EOJ receipt.


Date: 09/09/2015



Figure 39 Impossible to print receipt. No paper.

Figure 40 Summary receipt can't be printed.

Q6. Why does the number of receipts do not match the number of total traffic sometimes? A1. The user still chose to save the transaction when the application prompted that the re-

ceipt cannot be printed.


45 of 47



Q7. I cannot find the job file in the SD card. What happened?A1. The jobs in the reader are initially stored in the internal memory. When the job is fin-

ished, that is the only time it is copied into the SD card. This is to avoid errors when the SD card is accidentally pulled out of the unit.

Figure below shows the error. Notice that the SD card is pulled out from the unit

Figure 41 Error moving shift file to SD card. Not found SD card

When this happens, the user must log in and log out of the application again with the SD card properly inserted.


Date: 09/09/2015



A. APPENDIX F: PDA BIP-1300 4GB TECHNICAL SPECIFICATIONS

This improvement implies the supply of 20 PDA model BIP-1300-M1M, which satisfied the following technical characteristics. For more information see the corresponding attached datasheet:

WLAN: 802.11 Scanner: SE-950 1D Laser RAM/ROM: 128MB/128MB Camera: 2.0 Megapixel Autofocus Keypad: Numeric OS: Windows Mobile 5.0 PAN: Bluetooth+IrDA Screen: 3.5” QVGA

Every PDA BIP-1300 shall entail its data card SD Kingston 4 Gb.


47 of 47

“The last page of the document”

Documents

Introductionlinks.indracompany.com.ph/Procurement/ria/Portable Reader... · Web viewPortable Reader User Manual Toll Collection System (TCS) Migration of the Manila North Expressway