ANNEXURE 6: RESUME OF THE PROPOSED ADJUDICATOR Atal Indore City Transport Services Limited (AICTSL) ANNEXURE 6
ANNEXURE 7: INTERFACE DOCUMENT OF THE EXISTING ON-BOARD PIS DISPLAY UNIT Atal Indore City Transport Services Limited (AICTSL) ANNEXURE 7
INTEGRATED BUS DISPLAY CONTROLLER (IBDC) Document Title: Interfacing Document Document Number: VM/RD/IBDC Rev. 1.0 Prepared By Reviewed By Approved By Signature Signature Signature Name: Name: Name: Chemito Technologies Pvt Ltd. 8, Mohatta Bhavan, Off Dr. Moses Road, Worli, Mumbai 400 018, Maharashtra, India www.chemito.net
Revision Record Version Date of Release Details Version 1.0 23/11/2012 Original Document IBDC Interfacing Manual Page: 2
Table of Contents TABLE OF CONTENTS... 3 1. GENERAL... 4 2. TELEGRAM FORMAT... 4 2.1 HEADER FIELD... 4 2.2 INFORMATION FIELD... 5 2.2.1 Baud Rate Setting... 6 2.2.2 GPS Data Configuration... 7 2.2.3 Configuring Emergency Messages... 8 2.2.4 Configuring Predefined IBDC keys for Emergency... 9 2.2.5 Request for GPS RMC data... 10 2.2.6 Command to Display Emergency messages on Inside display... 11 2.2.7 Command to Set Route on all Destination Display Boards... 12 2.2.8 Request for Bus Current Route... 13 2.3 CHECKSUM FIELD... 14 2.4 THE FOOTER FIELD... 14 3. APPENDIX I... 15 IBDC Interfacing Manual Page: 3
1. General This document describes format of the telegram between IBDC and different types of On Board Computers on Bus. Detailed encoding of the telegram format is described in following sections. 2. Telegram Format The Telegram format is generalized. The telegram is broadly split into 6 distinct Data fields as shown below: Field Number Relative Within the Telegram 1 SOT 1 0 Start of Telegram 2 Packet Number 2 1 Range : < 00 99 > 3 Message Type 2 3 Range : < 00 99 > 4 Field N 5 Dependent upon Message 5 Checksum 2 N+5 equivalent of Binary checksum of entire Telegram except SOT 6 EOT 1 N+7 End of Transmission Table 1: Generalized Structure of Field IBDC to On Board Computer Telegram The total length of telegram will be N + 9 bytes, Where N = Number of bytes required for a particular message. 2.1 Header Field The Header field acts as preamble to the Field. It contains Packet number, Message Type as shown in Table below: Length of the Field : 5 bytes from Start of the Telegram : 0 IBDC Interfacing Manual Page: 4
Byte Represents Data Value & Range Number Decimal equivalent 0 SOT Character 1 01H 1 MSD of Packet < 0 9 > < 30H 39H > 2 LSD of Packet < 0 9 > < 30H 39H > 3 MSD of Message type < 0 9 > < 30H 39H > 4 LSD of Message type < 0 9 > < 30H 39H > Table 2: Header Data Message type table shown below Description Encoding Used in the Telegram 1 IBDC Baud Rate Setting 30H, 31H 2 GPS Data Configuration 30H, 32H 3 Emergency Message for Inside Display Configuration 30H, 33H 4 Configuration of Predefined Keys for Driver Emergency Messages 30H, 34H 5 Request for GPS data 30H, 35H 6 Command to Display Emergency messages on Inside Display 30H, 36H 7 Command to Set Bus Route on all Destination Displays 30H, 37H 8 Request for Current Bus Route Details 30H, 38H Table 3: Message Type 2.2 Field The information field will be of different length and will carry different data depending upon the type of On Board Computers on Bus. The information field always starts at an offset of 7 from Start of the Telegram. First byte of the information field is always STX character and the last character is always ETX character. IBDC Interfacing Manual Page: 5
2.2.1 Baud Rate Setting IBDC Serial interface port parameters are 1. Baud Rate: 115200 bps. 2. Data Bits: 8 Bit 3. Stop Bit: 1 Bit 4. Parity: None. However, IBDC can be configured by remote communication for 4800, 9600, 19200, 115200 (default as 115200) baud rates. Baud rate configuration details are given below. equivalent 2 Baud rate 6 Rage 4800, 9600, <30H-39H> 19200, 115200 3 ETX 1 End of Text 03H IBDC Serial Port Pin Configurations DB9 Female Pin Signal Description Remark 1 2 TXD IBDC Output 2 3 RXD IBDC Input 3 5 GND Common However, IBDC can set Baud rate after receiving the data. IBDC Interfacing Manual Page: 6
2.2.2 GPS Data Configuration This section describe GPS data configuration. GPS data configuration details given below equivalent GPS Data 0 = Query one time 2 1 <30H-31H> Mode 1 = Set Rate 3 Rate 2 Rage 01 10 sec <30H-39H> 4 ETX 1 End of Text 03H However, IBDC reply to On Board Computers. Details are given below equivalent GPS Data 0 = Query one time 2 1 <30H-31H> Mode 1 = Set Rate 3 Rate 2 Rage 01 10 sec <30H-39H> 4 ETX 1 End of Text 03H IBDC Interfacing Manual Page: 7
2.2.3 Configuring Emergency Messages This section describe configuration of Emergency messages for Inside display. equivalent 2 3 4 MSD of Message ID LSD of Message ID MSG LENGTH 1 Range : < 0 9 > <30H-39H> 1 Range : < 0 9 > <30H-39H> 3 Range: < 001 300 > <30H,30H,31H- 33H,30H.30H> 5 Message Max 300 Byte Dependent upon Message Characters 6 ETX 1 End of Text 03H However, IBDC reply the Acknowledgement to On Board Computers. Details are given below. equivalent 2 ACK 3 ACK <41H, 43H, 4BH> 3 ETX 1 End of Text 03H IBDC Interfacing Manual Page: 8
2.2.4 Configuring Predefined IBDC keys for Emergency This section describe configuration of predefined IBDC keys for Emergency equivalent 2 Key 1 Range : < 0 9 > <30H-39H> 3 MSG LENGTH 3 Range : < 01 30 > <30H,31H- 33H,30H> 4 Message Max 30 Byte Dependent upon Characters Message 5 ETX 1 End of Text 03H However, IBDC reply the Acknowledgement to On Board Computers. Details are given below. equivalent 2 ACK 3 ACK <41H, 43H, 4BH> 3 ETX 1 End of Text 03H IBDC Interfacing Manual Page: 9
2.2.5 Request for GPS RMC data GPS RMC data Request details are given below; equivalent 2 RMC Data 1 G 47H 3 ETX 1 End of Text 03H However, IBDC reply the data to On Board Computers. Details are given below. equivalent 2 RMC (NMEA) String Depends on NMEA protocol Depends on NMEA protocol String 3 ETX 1 End of Text 03H IBDC Interfacing Manual Page: 10
2.2.6 Command to Display Emergency messages on Inside display This section describe configuration of Commands to display Emergency messages on Inside display equivalent 2 3 MSD of Message ID LSD of Message ID 1 Range : < 0 9 > <30H-39H> 1 Range : < 0 9 > <30H-39H> 4 ETX 1 End of Text 03H However, IBDC reply to On Board Computers. Details are given below equivalent 2 3 MSD of Message ID LSD of Message ID 1 Range : < 0 9 > <30H-39H> 1 Range : < 0 9 > <30H-39H> 4 ETX 1 End of Text 03H IBDC Interfacing Manual Page: 11
2.2.7 Command to Set Route on all Destination Display Boards This section describe configuration of Commands to set route on all Destination Display Boards equivalent 2 No 4 Range : < 0001 9999 > <30H, 30H, 30H, 31H- 39H, 39H, 39H, 39H > 3 ETX 1 End of Text 03H However, IBDC reply to On Board Computers. Details are given below equivalent 2 No 4 Range : < 0001 9999 > <30H, 30H, 30H, 31H- 39H, 39H, 39H, 39H > 3 ETX 1 End of Text 03H IBDC Interfacing Manual Page: 12
2.2.8 Request for Bus Current Route Bus Current Route Request details are given below; equivalent 2 Route 1 R 52H 3 ETX 1 End of Text 03H However, IBDC reply the data to On Board Computers. Details are given below. equivalent 2 No 4 Range : < 0001 9999 > 3 Route 4 Alpha Numeric 4 Destination Depend upon Message Depend upon Message <30H, 30H, 30H, 31H- 39H, 39H, 39H, 39H > Characters Characters 3 ETX 1 End of Text 03H IBDC Interfacing Manual Page: 13
2.3 Checksum Field The checksum field contains 8-bit, modulo-256 sum of all the data bytes in the telegram except first byte (SOT). The 8-bit checksum is again coded in. Byte Number Represents Data Value & Range HEX equivalent 0 Upper Nibble of Checksum < 0 F > < 30H 39H >, < 41H- 46H > 1 Lower Nibble of Checksum < 0 - F > < 30H 39H >, < 41H- 46H > Table 4: checksum data 2.4 The Footer Field The Footer field comprises of one byte, viz. EOT character to signify end of Telegram. Byte Represents Data Value & Range Number Decimal equivalent 0 EOT Character 1 04H IBDC Interfacing Manual Page: 14
3. Appendix I Telegram Examples 1. To Set Baud Rate ( in ) 3 01 30H, 31H 01 6 Baud Rate 9600 30H, 30H, 39H,36H, 009600 30H, 30H, 12 ETX 03H End of Text 13 Checksum 39H, 37H Checksum-97 15 EOT 04H End of Telegram 2. Telegram for GPS data Configuration. ( in ) 3 02 30H, 32H 02 6 1 31H Set Rate 7 01 30H, 31H 1 See Rate 9 ETX 03H End of Text 10 Checksum 35H, 42H Checksum-5B 12 EOT 04H End of Telegram IBDC reply to On Board Computers ( in ) 3 02 30H, 32H 02 6 1 31H Set Rate 7 01 30H, 31H 1 See Rate 9 ETX 03H End of Text 10 Checksum 35H, 42H Checksum-5B 12 EOT 04H End of Telegram IBDC Interfacing Manual Page: 15
3. Telegram for configuration of Emergency messages for Inside display ( in ) 3 03 30H, 33H 03 6 10 31H, 30H Message ID 10 8 014 30H, 31H, 34H Message length = 14 11 Message 42H, 55H, 53H, 20H, 54H, 45H, 52H, Message= BUS TERMINATED 4DH, 49H, 4EH, 41H, 54H, 45H, 44H 25 ETX 03H End of Text 26 Checksum 42H, 37H Checksum-B7 28 EOT 04H End of Telegram IBDC reply the Acknowledgement to On Board Computers ( in ) 3 03 30H, 33H 03 6 ACK 41H, 43H, 4BH Acknowledgement = ACK 9 ETX 03H End of Text 10 Checksum 39H, 39H Checksum-99 12 EOT 04H End of Telegram 4. Telegram for Configuration of predefined IBDC keys for Emergency ( in ) 3 04 30H, 34H 04 6 5 35H Key 5 7 11 31H, 31H Message length = 11 11 Message 46H, 49H, 52H, 45H, 20H, 49H, 4EH, Message= FIRE IN BUS 20H, 42H,55H, 53H 20 ETX 03H End of Text 21 Checksum 34H, 39H Checksum-49 23 EOT 04H End of Telegram IBDC Interfacing Manual Page: 16
IBDC reply the Acknowledgement to On Board Computers ( in ) 3 04 30H, 34H 04 6 ACK 41H, 43H, 4BH Acknowledgement = ACK 9 ETX 03H End of Text 10 Checksum 39H, 41H Checksum-9A 12 EOT 04H End of Telegram 5. Telegram for GPS RMC data Request ( in ) 3 05 30H, 35H 05 6 G 47H GPS Data Request 7 ETX 03H End of Text 8 Checksum 31H, 33H Checksum-13 10 EOT 04H End of Telegram IBDC reply to On Board Computers ( in ) 3 05 30H, 35H 05 6 $GPRMC,094330.00 0,A,3113.3156,N,121 21.2686,E,0.51,193.93 RMC String RMC String,171210,,,A*68 76 ETX 03H End of Text 77 Checksum 46H, 45H Checksum-FE 79 EOT 04H End of Telegram IBDC Interfacing Manual Page: 17
6. Telegram for configuration of Commands to display Emergency messages on Inside display ( in ) 3 06 30H, 36H 06 6 50 35H, 30H Message ID 8 ETX 03H End of Text 9 Checksum 33H, 32H Checksum-32 11 EOT 04H End of Telegram IBDC reply to On Board Computers ( in ) 3 06 30H, 36H 06 6 50 35H, 30H Message ID 8 ETX 03H End of Text 9 Checksum 33H, 32H Checksum-32 11 EOT 04H End of Telegram 7. Telegram for configuration of Commands to set route on all Destination Display Boards ( in ) 3 07 30H, 37H 07 6 0101 30H, 31H, 30H, 31H, Route Serial Number = 0101 10 ETX 03H End of Text 11 Checksum 39H, 30H Checksum-90 13 EOT 04H End of Telegram IBDC Interfacing Manual Page: 18
IBDC reply to On Board Computers ( in ) 3 07 30H, 37H 07 6 0101 30H, 31H, 30H, 31H, Route Serial Number = 0101 10 ETX 03H End of Text 11 Checksum 39H, 30H Checksum-90 13 EOT 04H End of Telegram 8. Telegram for Bus Current Route Request ( in ) 3 08 30H, 38H 08 6 R 52H Request for Route 7 ETX 03H End of Text 8 Checksum 32H, 31H Checksum-21 10 EOT 04H End of Telegram IBDC reply to On Board Computers ( in ) 3 08 30H, 38H 08 6 0101 30H, 31H, 30H, 31H Route Serial Number = 0101 10 151A 31H, 35H, 31H, 41H Route No = 151A 14 Destination 56H, 41H, 53H, 48H, Destination = VASHI 49H 19 ETX 03H End of Text 20 Checksum 45H, 34H Checksum-E4 22 EOT 04H End of Telegram IBDC Interfacing Manual Page: 19
ANNEXURE 8: STANDARD FORM FOR DECLARATION REGARDING CUSTOMS/ EXCISE DUTY EXEMPTION Atal Indore City Transport Services Limited (AICTSL) ANNEXURE 8
Declaration regarding customs/ excise duty exemption for equipment/ goods bought for the work Name of the Project: Design, Supply, Install, Integrate, Commission, Test, Operate and Maintain the Intelligent Transportation System components for AICTSL in Indore, Madhya Pradesh, India From: (Bidder s Name and Address) To: Atal Indore City Transport Services Limited (AICTSL), Plot 30- Residency Area, A.B. Road, Opp. M.G.M. Medical College, Indore, Madhya Pradesh 452001 Dear Sir: Regarding: [Name of Work] Certificate for Import/Procurement of Equipment/ Goods 1. We confirm that we are solely responsible for obtaining customs/excise duty waivers which we have considered in our bid and in case of failure to receive such waivers for reasons whatsoever, the Employer will not compensate us. 2. We are furnishing below the information required by the Employer for issue of the necessary certificates in terms of the Government of India Central Excise Notification 108/95 and Customs Notification 85/99. 3. The goods/construction equipment for which certificates are required are as under: Items Make/ Brand Name Quantity Value Goods/ Equipment (From System Inventory Table) (a) Equipment 1 (b) Equipment 2 (c) (d) State whether it will be procured locally or imported (if so from which country) regarding justification for the quantity and their usage in works 4. We agree that no modification to the above list is permitted after bids are opened. 5. We agree that the certificate will be issued only to the extent considered reasonable by the Employer for the work, based on the Bill of Quantities and the equipment installation programme and methodology as furnished by us along with the bid. 6. We confirm that the above goods will be exclusively used for the above work and the equipment will not be sold or otherwise disposed of in any manner for the period of five years from the date of acquisition. Date: Place: (Signature) (Printed Name) (Designation) (Common Seal) Page 1 of 1