Electronic Data Interchange (EDI) Protocol

Toll Plaza 1

Port 1

NHAI Data Centre / Central Server

Port 2

Toll Plaza 2

Port 3 Port N

Toll Plaza 3

Toll Plaza n.

May 2015 Highway Automation and Management (HAM) /Electronics Division, NHAI Page | 1

Document Control Status

Document Amendment Record Change No Original

Date 02/04/2014

Prepared By HAM Division

2

28/05/2014

HAM Division

Brief Record of Change Electronic Data Interchange (EDI) protocol for collection of real time data from toll plaza prescribed for data transfer initially from 14 toll plazas under revenue sharing projects. Annexure-B to EDI Protocol incorporating Provision for Security of Data transmission Plaza ID and XML File Nomenclature for 14 toll plazas under six revenue sharing projects initially identified for EDI integration, which was later revised to 20 toll plazas under ten revenue sharing projects.

3

05/08/2014

HAM Division

4

04/12/2014

5

23/12/2014

6

29/05/2015

HAM Division HAM Division HAM Division

Mode of Payment (MOP) Master Vehicle Class Master List Frequently Asked Questions (FAQ) added to EDI Protocol for common understanding of all stakeholders. Addendum 1 to FAQ All Instructions Consolidated into a self speaking booklet for easy reference. Additional plazas added at Sr No 21 and 22 under Plaza ID and XML File Nomenclature list

Page | 2

Contents 1

Electronic Data Interchange (EDI) Protocol ......................................................................... 4 1.1

Online Real time data interchange from Toll Plaza to Central Server at NHAI............. 4

1.2

Key Constituents of EDI:.............................................................................................. 5

1.3

Features will be available to the Concessionaires ......................................................... 5

1.4 Shortlisted Data Attributes to be provided by Concessionaire from Plaza server/database ..................................................................................................................... 6 1.4.1

Lane Transaction Detail Table (LANE_TXN) .................................................... 6

1.4.2

POS Smart Card Transaction Detail Table (POS_SC_TXN) ............................. 7

1.4.3

POS ETC TAG Transaction Detail Table (POS_TAG_TXN) .............................. 8

1.4.4

Illustrative .xml format for above shortlisted data attributes ........................... 9

2

Schematic Diagram ............................................................................................................11

3

File Name Nomenclature ...................................................................................................12

4

3.1

Nomenclature for .xml file with plaza ID ....................................................................12

3.2

Mode of Payment (MOP) Master ................................................................................13

3.3

Vehicle Class Master List ............................................................................................14

Frequently Asked Questions (FAQ): ..................................................................................15

Page | 3

1

Electronic Data Interchange (EDI) Protocol 1.1

Online Real time data interchange from Toll Plaza to Central Server at NHAI Provisions contained in the Articles 19.5, 22.1 and 22.4, mandate the Concessionaire to submit periodic statements of the fee collected, No. of vehicles using the Project Highway (Traffic Census), No. of vehicles carrying load in excess of permissible limits, etc, in the forms set forth in Schedule “M” & “N”. Further, Article 23.3.1 prescribes that for determining the actual traffic on the Project Highway, the Authority shall be entitled to inspect the relevant records of the Concessionaire. In addition, Article 26.5.1 prescribes that in order to satisfy itself that the Concessionaire is reporting its Realisable Fee honestly and faithfully, the Authority may undertake such other measures and actions as it may deem necessary, to ascertain the actual Fee Revenues. The Article 22.4 mandates the Concessionaire to install, operate and maintain a computer system with round-the-clock connections to the networks of the Authority and other related entities for exchange of data and information useful or necessary for efficient and transparent regulation and management of traffic. For this purpose, the Concessionaire is required to follow such protocol for Electronic Data Interchange (the “EDI”) as the Authority may specify. In order to implement the above provisions of the Concession Agreement and to satisfy itself that the Concessionaire is reporting its Realisable Fee honestly and faithfully, NHAI has setup a Central Server at Millennium Telecom Limited (MTL) Data Centre so as to collect the relevant data online on real-time basis from the Computer Systems operated & maintained by the Concessionaire at its respective Toll Plazas. For exchange of data between the Computer Systems operated & maintained by the Concessionaire at Toll Plazas and the Central Server of NHAI, necessary EDI protocol has been specified with details elucidated below. The Concessionaire is, therefore, required to arrange the round-the-clock connections between the Computer Systems operated & maintained by the Concessionaire at Toll Plazas and the above mentioned Central Server of NHAI using Virtual Private Network (VPN) connectivity in accordance with the provisions contained in the Article 22.4 of Concession Agreement. For any technical clarification / assistance, the Concessionaire may contact GM(Elect)/ DGM(Elect) at NHAI, HQ (Ph011-25074100 Extn. 1406) e-mail- [email protected]/ [email protected].

Page | 4

a) b) c)

d) e) f)

1.2 Key Constituents of EDI: Medium: VPN Connectivity, at least 2 MBPS from Toll Plaza to Central Server/Data Center NHAI What to Send: Stream of Data Attributes against each transaction to be sent to central server (listed below) How to Send: Format of Data interchange to be .xml/flat file format, configured for data packet every 5 minutes1 or as specified by NHAI from time to time. (Illustrative .xml format to carry defined data packet may be seen in subsequent section). The data to be sent through FTP. Where to Send: IP address and port number for respective plazas to be separately prescribed by NHAI on case to case basis. Responsibility of data Completeness, Integrity and Accuracy: Sole responsibility of the Concessionaire. Security of Data transmission: The data transmission shall be secured through following: a. Unique IP Address (Static and Public) for Plaza server (Main Server / Standby of DR2). b. Unique Port Number / Folder on Central Server for each toll plaza to upload data and download Log File. c. MAC ID of the Plaza Server (Main Server / Standby of DR). d. User ID and Password allocated by NHAI for each location.

1.3 Features will be available to the Concessionaires a) Log of XML files containing details of the File Name, Size of file, Source IP Address, Date Time Stamp of Central Server receipt, Number of data rows in each XML file will be stored for two calendar days in plane text file on the respective Concessionaire’s shared space on NHAI’s Central server. In case the Concessionaire chooses to check the data integrity they may choose to download such files for verification / reconciliation at their end. b) If required, at the end of file transmission, Concessionaire will call a function via services running on Server, which will provide the confirmation of file transfer with “File Name”, “File Size” and few more critical attributes which will be used in future as reference. c) Handheld Devices/Ticketing machines: Concessionaire shall notify NHAI, in case any other method of toll collection such as handheld ticketing machine etc., is in use at the plaza. Concessionaire shall provide the complete data structure/architecture and the procedure followed to capture the transaction details in the plaza server. The transaction details/data of such transactions will also be required to be sent to NHAI Central server in the format to be prescribed by NHAI, on case to case basis.

1 2

Maximum time limit. Disaster Recovery

Page | 5

d) NHAI reserves the right to modify any requirement or format from time to time. 1.4

S. No. 1

2 3 4 5 6 7 8 9

10 11 12

13 14 15

Shortlisted Data Attributes to be provided by Concessionaire from Plaza server/database 1.4.1 Lane Transaction Detail Table (LANE_TXN) Attribute Remarks TP_Name

Toll Plaza Name as per the gazette notification. (Kindly specify in case plaza name is different in plaza server database etc.) TP_ID Toll Plaza ID To be provided by NHAI, concessionaire may ask NHAI while configuring EDI Lane_ID Lane number/name, as in concessionaire’s database Session_ID Toll Collector (TC) login session id, as generated in the database Shift_ID Shift: A, B or C viz. A: 00:00:00 to 07:59:59, B: 08:00:00 to 15:59:59 & C: 16:00:00 to 23:59:59 User_ID Toll Collector user id Date_Time Date and time stamp of the Transaction Txn_No Transaction number as generated in the database Veh_Class Vehicle class to be mapped as prescribed in the concession o TC_Class agreement. Concessionaire may ask NHAI for the master data while o AVC_Class configuring EDI o Sup_Class TC_Class: Vehicle class as entered by the Toll Collector in lane AVC_Class: Vehicle class as classified by the Automatic Vehicle Classifier (AVC) Sup_Class: Vehicle class as entered by the Supervisor/Auditor/Validator PCU_Factor As applicable for the audited vehicle class, as prescribed in the concession agreement Veh_Reg_No Vehicle registration number as entered/captured during the transaction in lane MOP_Type MOP: Mode of Payment, as mentioned in Schedule M (Cash, card, tag, monthly pass, local monthly pass, daily pass, return journey, exempt, revoke, violation etc.) To be mapped with the list provided in the concession agreement. Concessionaire may ask NHAI for the master data while configuring EDI SC_ID Smart Card ID, as stored in the database/ generated during issuing new smart card TAG_ID TAG ID, as stored in the database/ generated during issuing new TAG Dailypass_ID Daily pass/Barcode ID, as stored in the database/ generated Page | 6

16 17 18 19

Applicable_Fee Perm_wt Act_wt_wim Act_wt_wb

20 21 22

Add_Fee_Over Amt_Paid Exemp_Cat

23

Sup_Remark 1.4.2

during issuing new daily pass Fee payable as per applicable fee schedule Permissible weight Actual weight as recorded by the SSWIM installed in lane Actual weight as recorded by the Static weight bridge installed at plaza Additional fee paid for overloading Amount paid by the commuter Exemption category: To be mapped with the list provided in the concession agreement. Concessionaire may ask NHAI for the master data while configuring EDI Supervisor/Auditor/Validator remarks as entered by him in the system during audit/validation/authorization of the transaction

POS Smart Card Transaction Detail Table (POS_SC_TXN)

S.No. Attribute 1 TP_Name 2

TP_ID

3 4 5

POS_ID Session_ID Shift_ID

6 7 8 9 10

User_ID Date_Time POS_Txn_No Cust_ID SC_ID Veh_Reg_No

11

Veh_Class

12 13 14 15 16 17

SC_Iss_dt SC_Exp_dt SC_Status SC_Rechg_dt SC_Rechg_Amt SC_Type

Remarks Toll Plaza Name as per the gazette notification. (Kindly specify in case plaza name is different in plaza server database etc.) Toll Plaza Id. To be provided by NHAI, concessionaire may ask NHAI while configuring EDI POS number, as in concessionaire’s database POS executive login session id, as generated in the database Shift: A, B or C viz. A: 00:00:00 to 07:59:59, B: 08:00:00 to 15:59:59 & C: 16:00:00 to 23:59:59 POS executive user id Date and time stamp of the transaction POS Transaction number as generated in the database Customer ID, as generated in the database Smart Card ID, as generated in the database during issuing new smart card Vehicle registration number entered/captured during the transaction in POS Vehicle class to be mapped as prescribed in the concession agreement. Concessionaire may ask NHAI for the master data while configuring EDI Date of issue of Smart card Date of expiry of Smart card Smart Card Status before recharge: Active/deactive/blacklisted Date of recharge of Smart Card Smart card recharge Amount Monthly/Discounted local (all applicable categories)/Exempt/VIP etc.

Page | 7

1.4.3

POS ETC TAG Transaction Detail Table (POS_TAG_TXN)

S.No. Attribute 1 TP_Name

2

TP_ID

3 4 5

POS_ID Session_ID Shift_ID

6 7 8 9 10 11

User_ID Date_Time POS_Txn_No Cust_ID TAG_ID Veh_Reg_No

12

Veh_Class

13 14 15 16 17 18

TAG_Iss_dt TAG_Exp_dt TAG_Status TAG_Rechg_dt TAG_Rechg_Amt TAG_Type

Remarks Toll Plaza Name as per the gazette notification. (Kindly specify in case plaza name is different in plaza server database etc.) Toll Plaza Id. To be provided by NHAI, concessionaire may ask NHAI while configuring EDI POS id/number, as in concessionaire’s database POS executive login session id, as generated in the database Shift: A, B or C viz. a: 00:00:00 to 07:59:59, B: 08:00:00 to 15:59:59 & C: 16:00:00 to 23:59:59 POS executive user id Date and time stamp of the transaction POS Transaction number as generated in the database Customer ID, as generated in the database TAG ID, as generated in the database during issuing new smart card Vehicle registration number entered/captured during the transaction in POS Vehicle class to be mapped as prescribed in the concession agreement. Concessionaire may ask NHAI for the master data while configuring EDI Date of issue of TAG Date of expiry of TAG TAG Status before recharge: Active/deactive/blacklisted Date of recharge of TAG Amount for which TAG recharged at POS Monthly/Discounted local (all applicable categories)/Exempt/VIP etc.

Page | 8

1.4.4

Illustrative .xml format for above shortlisted data attributes

DELHI 01 11 000123 Page | 9

1 S1585 2014-04-01T00:00:00+05:30 31101102581277 04 04 04 4.5 RT HR47B0105 CASH SM_23534 01325346 2VCDY423734VSD 666 666 23546 54645 34546 1000 11 TC CORRECT

Page | 10

2

Schematic Diagram Collection of Real Time Data from Toll Plaza under BOT (Toll) Projects

Approx. 3 GB Data / Month Real time per transaction basis through VPN (at least 2 Mbps)

NHAI Data Centre / Central Server

Toll Plaza 1 Port 1 Port 2 Approx. 3 GB Data / Month Real time per transaction basis through VPN (at least 2 Mbps)

Port 3

Toll Plaza 2 Port n 2 Mbps VPN Connection Approx. 3 GB Data / Month Real time per transaction basis through VPN (at least 2 Mbps)

Toll Plaza 3

. . . . . . .

Approx. 3 GB Data / Month Real time per transaction basis through VPN connectivity (at least 2 Mbps)

NHAI Hq

Toll Plaza n.

Web Based Application Fetches data from Central Server: 1. Prepares reports 2. Takes Backup & 3. Monitor / Manage Web Space utilization at Central Server.

Requirements At Toll Plaza 1. VPN Connection (at least 2 Mbps) from each plaza to NHAI Central Server. 2. EDI Protocol to transfer toll transaction data per transaction basis via .XML file through FTP to NHAI Data Center

Page | 11

3

File Name Nomenclature NHAI has prescribed standard nomenclature for .xml files to be sent to the Central Server from respective toll plaza. Each plaza shall be assigned or unique code (Plaza ID) at the time of establishing real time data transfer. In addition, Mode of Payment (MoP) as well as Vehicle Class Master has also been standardized. 3.1

Sr. NH No.

1

2

2

8

3

8

4

8

5

8

6

1

7

1

8

1

9

8

10

8

11

8

12

5

13

7

14

7

15

3

Stretch

Badarpur Elevated Highway

Chalthan Dahisar

Panipat Jalandhar

Gurgaon Kotputli Jaipur

Nomenclature for .xml file with plaza ID State

Organisati on

Toll Plaza Name

Toll Plaz a ID

Haryana

Badarpur Faridabad Elevated Tollways Ltd.

Badarpur

001

Boriach

002

Bhagwada

003

Charoti

004

Khanewade

005

Nilokheri (Karnal)

006

Sambhu

007

Ladowal

008

IRB Surat Gujarat & Dahisar Maharashtra Tollways Pvt. Ltd.

Haryana & Punjab

Haryana & Rajasthan

Soma Isolux NH One Tollways Pvt.Ltd.

Shahjahanpur 009 Pink city Expressways Manoharpur 010 Pvt. Ltd. Daulatpura 011

L&T Chennai Tamil Nadu Tada Nallur 012 Tollways Ltd. L&T Vaniyambadi 013 Krishnagiri Krishnagiri Tamil Nadu Walajahpet Walajahpet Tollways Pallikonda 014 Ltd. SEW KhalgatNavayuga Madhya MP/Maharas Barwani Sendhwa 015 Pradesh htra Border Tollways Pvt. Ltd. Chennai Tada

16

Panthangi

17

9

HyderabadAndhra Vijayawada Pradesh Section

18

19

3

20

67

21

8

22

8

PimpalgaonNashikMaharashtra Gonde Trichy to Karur – BOT Tamilnadu (Toll) Project

KishangarhRajasthan Ajmer-Beawar

GMR Hyderabad Vijayawada Chillakallu Expressways Pvt. Ltd. Korlaphadu

016

017

018

XML File 1 name (Cash)

XML file 2 name (Smart card POS)

XML file 3 name (ETC)

XML file 4 name (Audit)

00101_YYYYM 00102_YYYYMMD 00103_YYYYMMDD A00101_YYYYMMDDHH MDDHHMMSS DHHMMSS HHMMSS MMSS 00201_YYYYM 00202_YYYYMMD 00203_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS 00301_YYYYM 00302_YYYYMMD 00303_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS 00401_YYYYM 00402_YYYYMMD 00403_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS 00501_YYYYM 00502_YYYYMMD 00503_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS 00601_YYYYM 00602_YYYYMMD 00603_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS 00701_YYYYM 00702_YYYYMMD 00703_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS 00801_YYYYM 00802_YYYYMMD 00803_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS 00901_YYYYM 00902_YYYYMMD 00903_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS 01001_YYYYM 01002_YYYYMMD 01003_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS 01101_YYYYM 01102_YYYYMMD 01103_YYYYMMDD MDDHHMMSS DHHMMSS HHMMSS

A00201_YYYYMMDDHH MMSS A00301_YYYYMMDDHH MMSS A00401_YYYYMMDDHH MMSS A00501_YYYYMMDDHH MMSS A00601_YYYYMMDDHH MMSS A00701_YYYYMMDDHH MMSS A00801_YYYYMMDDHH MMSS A00901_YYYYMMDDHH MMSS A01001_YYYYMMDDHH MMSS A01101_YYYYMMDDHH MMSS

01201_YYYYM 01202_YYYYMMD 01203_YYYYMMDD A01201_YYYYMMDDHH MDDHHMMSS DHHMMSS HHMMSS MMSS 01301_YYYYM 01302_YYYYMMD 01303_YYYYMMDD A01301_YYYYMMDDHH MDDHHMMSS DHHMMSS HHMMSS MMSS 01401_YYYYM 01402_YYYYMMD 01403_YYYYMMDD A01401_YYYYMMDDHH MDDHHMMSS DHHMMSS HHMMSS MMSS 01501_YYYYM 01502_YYYYMMD 01503_YYYYMMDD A01501_YYYYMMDDHH MDDHHMMS DHHMMSS HHMMSS MMSS S 01601_YYYYM MDDHHMMS S 01701_YYYYM MDDHHMMS S 01801_YYYYM MDDHHMMS S 01901_YYYYM MDDHHMMS S

01602_YYYYMMD 01603_YYYYMMDD A01601_YYYYMMDDHH DHHMMSS HHMMSS MMSS 01702_YYYYMMD 01703_YYYYMMDD A01701_YYYYMMDDHH DHHMMSS HHMMSS MMSS 01802_YYYYMMD 01803_YYYYMMDD A01801_YYYYMMDDHH DHHMMSS HHMMSS MMSS

PNG Pimpalgaon Tollway Ltd.

019

M/s. TK Toll Manavasi Road Pvt. Ltd.

020

02001_YYYYMM02002_YYYYMMDD 02003_YYYYMMDDHA02001_YYYYMMDDHH DDHHMMSS HHMMSS HMMSS MMSS

21

02101_YYYYMM02102_YYYYMMDD 02103_YYYYMMDDHA02101_YYYYMMDDHH DDHHMMSS HHMMSS HMMSS MMSS

22

02201_YYYYMM02202_YYYYMMDD 02203_YYYYMMDDHA02201_YYYYMMDDHH DDHHMMSS HHMMSS HMMSS MMSS

Soma Isolux KishangarhGegal Ajmer-Beawar Tollways Pvt.Ltd. Piplaz .

01902_YYYYMMD 01903_YYYYMMDD A01901_YYYYMMDDHH DHHMMSS HHMMSS MMSS

There are four folders on FTP Server namely CASH, POS, ETC & Audit. All .xml files should reach the destination / concerned folder which is automatically created date-wise on FTP server.

Page 12 of 22

3.2

Mode of Payment (MOP) Master

The Central server will store the data as per following codes for Mode of Payment. The Concessionaire will provide the details in the following table as applicable at the respective Toll Plaza MOP Mapping Details – Column 3 & 4 to be filled by Concessionaire and Returned to NHAI NHAI Central Concessionaire NHAI Central DB Concessionaire DB MOP type MOP type MOP type Description MOP type Code code Description (1) (2) (3) (4) Cash 1 Daily Pass Issued for 2 onward passage Daily Pass Return 3 passage Local Journey Pass 4 Monthly Pass 5 Monthly Pass Local 1 6 Monthly Pass Local 2 7 Monthly Pass School 8 Bus Monthly Pass Exempt 9 Exempt 10 Revoke 11 Violation 12 System Error 13 Manual 14 15 ETC Tag

Page 13 of 22

3.3

Vehicle Class Master List

The Central server will store the data as per following codes for Vehicle Class. The Concessionaire will provide the details in the following table as applicable at the respective Toll Plaza/ Concession Agreement: Vehicle Class Mapping Details – Column 3 & 4 to be filled by Concessionaire and Returned to NHAI NHAI Central Concessionaire Concessionaire NHAI Central DB DB Vehicle Vehicle Class Vehicle Class Vehicle Class Class Description Code Description (1) (2) (3) (4) Two wheeler 1 Three - Wheeler 2 Passenger Three - wheeler Freight 3 Car / Jeep / Van 4 Light Commercial Vehicle 5 2-axle Light Commercial Vehicle 6 3-axle Bus 2-axle 7 Bus 3-axle 8 Mini-Bus / Light 9 passenger Vehicle Truck 2 - axle 10 Truck 3 - axle 11 Truck 4 - axle 12 Truck 5 - axle 13 Truck 6 - axle 14 Truck Multi axle ( 7 and 15 above) Earth Moving Machinery 16 Heavy Construction 17 machinery Tractor 18 Tractor with trailer 19 Tata Ace and Similar mini Light Commercial 20 Vehicle

Page 14 of 22

4

Frequently Asked Questions (FAQ):

Sl. Question Answer/ Clarification No. 1 For data completeness, Concessionaire’s responsibility: integrity and security, 1) VPN Connectivity with at least 2 MBPS from what provisions are to be Toll Plaza Server (physical location) to Central maintained/ ensured? Server/Data Center NHAI 2) Unique IP Address (Static and Public) for Plaza server (Main Server / Standby of DR3). 3) MAC ID of the Plaza Server (Main Server / Standby of DR). 4) Audit logs including System Administrator activities logs are maintained and audit logging (both at the application and OS level) are enabled on all the servers and all the toll booth machines. Under no circumstances the audit log be disabled NHAI’s Responsibility: 5) Unique Port Number / Folder on Central Server for each toll plaza to upload data and download Log File. 6) User ID and Password for each toll location after one-to-one mapping the Public IP of Plaza with Central Server of NHAI. 2 What are the key 1. Data completeness, integrity and accuracy of the constituents to be ensured data sent on central server to be the sole by concessionaires for data responsibility of the Concessionaire. exchange from plaza 2. Stream of Data Attributes against each server to NHAI’s Central transaction to be sent to Central Server has been Server? prescribed under EDI protocol. 3. Format of data interchange to be .xml/flat file format, configured to accommodate data packet of all transactions within a duration not exceeding 5 minutes or as specified by NHAI from time to time. 4. The data to be sent through FTP. 5. IP address of the Central server and Port Number for respective plaza to have been prescribed by NHAI.

3

Disaster Recovery

Page 15 of 22

Sl. Question No. 3 What should be the frequency of data transfer?

4

As the data is subjected to auditing / validation, whether it should be transferred to NHAI after data auditing / validation? Whether any different .xml file naming convention for audited/ validated data is to be followed.

5

6

Answer/ Clarification Normally, the data should be transferred on real-time basis i.e. as soon as a transaction takes place at the toll plaza. However, depending on traffic volume, data size of each transaction and the bandwidth available at the Toll Plaza the time-span for real time data transfer should not exceed 5 minutes in any case. a) The data is to be transferred as soon as it is generated on the Plaza server. b) The date should be sent from Toll Plaza Server, i.e., as transacted not from the HO of Concessionaire or Processed data. c) In case the data is validated / modified for any reason afterwards, the same shall be re-sent immediately every time after such validation / modification for which the EDI protocol prescribes for capturing comments of supervisor / auditors, which is self-explanatory. d) The modified / validated data shall also conform to prescribed naming convention as per EDI protocol, with revised date and time stamp, whereas the unique transaction ID shall remain the same. Each toll plaza has been assigned a unique plaza code and a standard naming convention for the .XML files containing data to be transferred to the Central Server. This should be strictly adhered to.

What is the file naming convention while transferring the data from Plaza? OR How the names of XML files would be defined? Can concessionaire use the The attributes under XML files are standardized. No different Attributes names change in naming conventions as well as sequencing of under XML file. attributes under XML data file is permissible under any circumstances. In addition, once data types of attributes related to real time data transfer shared by Concessionaire with NHAI for mapping, the data type of any attribute should not be changed by the Concessionaire.

Page 16 of 22

7

8

9

10

4

Can concessionaire use Concessionaire is not required to change anything in MoP4 prescribed by NHAI their TMS database for the sake of data transfer to under EDI protocol? NHAI. The Central server will store the data as per code(s) for Mode of Payment prescribed under EDI. For the purpose of mapping, the Concessionaire will provide the requisite details to NHAI in the table prescribed under para 3.2 as per applicable MoP at their respective Toll Plaza (One time exercise). Can concessionaire use As already said, the Concessionaire is not required to Vehicle Class Master change anything in TMS database for the sack of data (VCM) prescribed by transfer to NHAI. NHAI in the EDI The Central server will store the data as per codes for protocol? VCM prescribed under para 3.3 above. For the purpose of mapping, the Concessionaire will provide the requisite details to NHAI in the table prescribed under para 3.3 above as per applicable VCM at their respective Toll Plaza (One time exercise). How the transactions EDI protocol prescribed by NHAI has no provision to against manual tolling be accept/ incorporate data against manual tolling incorporated in the data transactions. files being exchanged In case under special circumstances the Concessionaire resorts to manual tolling for a limited duration, the from plaza server. same shall be sent separately, immediately after the end-of-shift in .XLS file, by email, to [email protected] for which the requisite format shall remain same i.e. each data attribute should be in one column in the same sequence (left to right) as that in .xml file format and every transaction should be recorded in one row. In case of any breakdown Concessionaire shall notify NHAI, in case any other on any toll lane OR method of toll collection such as handheld ticketing to overcome the problem machine (GPRS enabled) etc. is in use at the toll plaza. of long queues of vehicles Concessionaire shall provide the complete data during peak hours on toll structure/ architecture and the procedure followed to booths, if the capture the transaction details in the plaza server. concessionaires resorts to The transaction details/data of such transactions will collecting toll fee using also be required to be sent to NHAI Central server in hand held / electronic the format to be prescribed by NHAI, on case to case devices, in such case, what basis. will be the procedure / protocol to send such data.

Mode of Payment

Page 17 of 22

11

In case of server goes down or data link failures, how the data be sent to NHAI server.

12

With reference to file format prescribed above data types of few columns mismatch w.r.t. TMS application. Data Type is not mentioned for POS_SC_TXN and POS_TAG_TXN structure thus needs to confirm about it. (Reference POS ETC TAG Transaction Detail Table) Max allowed length for the attributes and its mandatory/non mandatory requirement is not mentioned in Transaction Detail Is it required to upload file in specific folder? Central server folder structure is not given. How to communicate MAC ID of plaza server? Is it required to provide during initial configuration at central side or required to include with each transmitted file?

13

14

15

16

The concessionaire(s) has to ensure the XML data files are generated and stored locally on tolling server, and same is to be synchronized with NHAI server which will also maintain log of XML files received to facilitate the concessionaire’s system to identify the gap(s) (if any) and accordingly the concessionaire’s system shall send the backlog data, as soon as connectivity is reestablished. To clear the backlog of pending data, the concessionaires will have to ensure that the XML file is sent in cluster of transactions of maximum 5 minutes as per the naming convention mentioned in EDI Protocol. The date and time of such data shall be the original transaction date and time when it was generated and be sent to Central server as it is. Concessionaire to use Data type as per their TMS Application and inform NHAI about the same in advance. Data type once decided needs to be adhered strictly by the Concessionaire. Concessionaire to use Data type as per their TMS Application and inform NHAI about the same in advance. Data type once decided needs to be adhered strictly by the Concessionaire.

Concessionaire to use Data type as per their TMS Application and inform NHAI about the same in advance. Data type once decided needs to be adhered strictly by the Concessionaire.

Every toll plaza has been assigned access to a specific folder using the FTP user id / password. The files are to be uploaded on root folder for which access has been provided by NHAI. Ones MAC ID of Plaza Server is communicated to NHAI, it is not required to be included in transmitted file.

Page 18 of 22

17

What will be exact name of the log folder?

Following four folders are available to every toll plaza on central server;  Cash  POS  ETC  Audcash

18

What will be the structure of Log file which will be generating at central side against uploaded data?

Log file is in .txt format having same name of XML file received on Central server. Sample Log file is given below :

19

What will be the log writing methodology, will it be only one file against one uploaded file or it will be day wise file and going to keep upending latest logs in same file.

One log file shall be generated by the system against every uploaded file.

20

It is mentioned that reconciliation log file will be available for 2 calendar days on central server, but what will happen if files are uploaded from plaza server to central server and while downloading its log file from central server (for reconciliation at plaza server) connection disconnected and continue in same state for next 6 or 7 days?

The concessionaire to report NHAI EDI team well in advance (i.e. before expiry of 2 calendar days) which will ensure that the log files are not removed from the server and are accessible as and when server/connection is restored.

Page 19 of 22

21

22

23

Date time is included in the name of generated file, but is this date time should be file creation time stamp or it should be slot wise time stamp? (As per deployed functionality, consider a date 23 Sep 2014 first file creates at 00:05:01 hrs and it fetches transaction in between 00:00:01 hrs to 00:05:00 hrs and generated file having name as 00401_20140923000000) Files are generating at 5 min of interval but if transactions are not happened during particular interval then is it required to upload files which are having Zero record? This case can in general happen for POS type of Transactions If we keep incrementing record retrieval timestamp by 5 min. and any lane get disconnected from network then the transactions of that lane will post on server after some time, then in this case old time stamp transaction will appear in current file stamp. What exact mechanism needs to implement for uploading of transactions in such scenario?

Please see answer to FAQ Sl.No 3 & 4 which is self explanatory.

As per EDI protocol normally a transaction file is required to be generated as soon as a transaction happens and in no case the delay should be exceed 5 minutes. Please also see answer to FAQ Sl.No 3 & 4.

Please see answer to FAQ Sl. No 11 which is selfexplanatory.

Page 20 of 22

24

25

26

As per TMS functionality Auditor can audit Lane transaction multiple times till the declaration of Lane booth and then in this scenario same audited lane transaction will get uploaded multiple times to the Central server. What should be the exact mechanism needs to implement for uploading of transactions in such scenario. If lane transaction is scrapped / canceled then its related flag is nowhere mentioned in structure LANE_TXN, Is it not required to mention such transactions? At any Stretch CCH functionality is implemented, under this functionality initially all the lane transactions are performing under Single Journey, on uploading of these transaction to the CCH server, after completion of day file is receiving with exact MOP w.r.t. transaction performed on Lane. CCH is responsible for reconciliation of the records and if there is any deviation in image of vehicle and registered class then CCH can take two or more days for its verification and then only they are confirming MOP of the vehicle. What should be the procedure for uploading of these transactions?

Please see answer to FAQ Sl. No 4.

For all scrapped/ cancelled transactions, there should be an MOP type defined in the TMS. The same shall be informed to NHAI and data in .xml format shall be sent using that MoP type.

Please see answer to FAQ Sl. No 4.

Page 21 of 22

For Any Queries Please Contact: Shri Deepak Saxena Dy. General Manager (Elect.) G-5&6, Sector – 10, Dwarka New Delhi – 110 075 Phone: 25074100/200, Extn. 1410 Mob.: 9810902815 Phone: 25074100/200, Extn. 1406

Page 22 of 22