Technical Proposal

Technical Proposal
PARKING MANAGEMENT AND GUIDANCE SYSTEM
Prepared for:
Mysore Mall Parking

Submitted by:
Metro Infrasys Private Limited
B-92, Mayapuri Industrial Area
Phase-1, New Delhi-110064
Parking Management System

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
2 of 65
Contents
PREPARED FOR: .............................................................................................................................. 1
1.
DOCUMENT INFORMATION ................................................................................................. 5

1.1
1.2
1.3
2.
INTRODUCTION ....................................................................................................................... 8
2.1
3.
3.2.1
3.2.2
3.2.3
3.2.4
Entry Lane..................................................................................................................................... 11
Exit Lane ....................................................................................................................................... 11
Control Room ................................................................................................................................ 12
Online Services.............................................................................................................................. 12
HARDWARE REQUIRED AT PARKING ENTRY..........................................................................14

HARDWARE REQUIRED AT PARKING EXIT .............................................................................14
EXIT PAYMENT STATION ......................................................................................................14
HARDWARE REQUIRED AT CONTROL CENTRE .......................................................................15
SOFTWARE DESCRIPTION ...................................................................................................16

5.1
5.2
5.3
5.3.1
5.3.2
5.3.3
5.3.4
6.
SYSTEM ARCHITECTURE .......................................................................................................10

FUNCTIONAL OVERVIEW.......................................................................................................11
PROPOSED HARDWARE........................................................................................................13
4.1
4.2
4.3
4.4
5.
ROLES AND RESPONSIBILITIES ............................................................................................... 9
PROPOSED SOLUTION ..........................................................................................................10

3.1
3.2
4.
DOCUMENT PURPOSE AND CONTENT ..................................................................................... 5

LIST OF ABBREVIATIONS........................................................................................................ 6
DEFINITIONS .......................................................................................................................... 7
MONITORING ........................................................................................................................16
CENTRAL CONTROL SYSTEM ................................................................................................17
LEVELS DESCRIPTION ............................................................................................................20
Lane level ...................................................................................................................................... 20
Admin level ................................................................................................................................... 23
Point Of Sale Module .................................................................................................................... 30
Cashup Module.............................................................................................................................. 31
PARKING MANAGEMENT.....................................................................................................33
6.1
6.2
PARKING ENTRY FRONT -END...............................................................................................33

PARKING EXIT FRONT END .................................................................................................34
Confidential: Unauthorized disclosure, copying and distribution are prohibited

Page 2 of 65
Metro Infrasys Pvt. Ltd.

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
3 of 65
7.
SYSTEM AUDIBALITY AND REPORTS ...............................................................................35

7.1
7.2
SYSTEM MONITORING...........................................................................................................35
SYSTEM REPORTING .............................................................................................................36
7.2.1
7.2.2
7.2.3
7.2.4
7.2.5
7.2.6
Hourly transaction report ............................................................................................................... 37

Pending Vehicle Transaction Report .............................................................................................. 38
Pass Transaction Report ................................................................................................................. 39
Search Vehicle Detail Report ......................................................................................................... 40
Summaries Transaction Report....................................................................................................... 42
Detailed Revenue Report ............................................................................................................... 43
8. PROJECT MANAGEMENT & EXECUTION METHODOLOGY ...... ERROR! BOOKMARK

NOT DEFINED.
8.1
8.2
BUSINESS EXCELLENCE MODEL ...................................... ERROR! BOOKMARK NOT DEFINED.

GOVERNANCE FRAMEWORK ........................................... ERROR! BOOKMARK NOT DEFINED.
8.2.1
8.2.2
8.2.3
8.2.4
8.2.5
8.2.6
9.
Steering Committee ..........................................................................Error! Bookmark not defined.

Project Management Office (PMO) ...................................................Error! Bookmark not defined.
Project Delivery Structure .................................................................Error! Bookmark not defined.
Escalation Management ....................................................................Error! Bookmark not defined.
Change Management ........................................................................Error! Bookmark not defined.
Delivery Governance ........................................................................Error! Bookmark not defined.
PROJECT SUPPORT AND MAINTENANCE ........................................................................45

9.1
9.2
9.3
9.4
9.5
9.6
9.7
9.8
9.9
9.10
10.
PREVENTIVE MAINTENANCE .................................................................................................45

CORRECTIVE MAINTENANCE ................................................................................................45
DAILY INSPECTION FORMS ....................................................................................................46
FAULT NOTIFICATIONS .........................................................................................................46
WARRANTY SPARES .............................................................................................................47
ACCIDENT DAMAGE..............................................................................................................47
LOGGING OF FAULTS ............................................................................................................48
WEEKLY REPORT ..................................................................................................................48
MONTHLY REPORT ...............................................................................................................48
OFFICE SPACE .......................................................................................................................48
TECHNICAL SPECIFICATIONS ........................................................................................49
10.1
SERVER ................................................................................................................................49
10.1.1
10.1.2
10.2
10.3
Server Racks ............................................................................................................................. 50

Server UPS ................................................................................................................................ 50
TICKET DISPENSER ...............................................................................................................51

SMART CARD READER ..........................................................................................................52

Page 3 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
4 of 65
10.3.1
10.3.2
10.3.3
10.3.4
10.3.5
10.3.6
10.3.7
10.3.8
10.4
BAR CODE READER ..............................................................................................................54
10.4.1
10.4.2
10.4.3
10.4.4
10.4.5
10.4.6
10.5
Function .................................................................................................................................... 54
Specification ............................................................................................................................. 54
Electrical Connections ............................................................................................................... 55
MTBF ....................................................................................................................................... 55
Environmental Factors ............................................................................................................... 55
Environmental Protection .......................................................................................................... 55
BOOM BARRIER ....................................................................................................................56
10.5.1
10.5.2
10.5.3
10.5.4
10.5.5
10.5.6
10.5.7
10.6
10.7
10.8
Function .................................................................................................................................... 52
Specification ............................................................................................................................. 52
Data Connection ........................................................................................................................ 53
Mounting................................................................................................................................... 53
Signage ..................................................................................................................................... 53
Function .................................................................................................................................... 56
Boom Specification ................................................................................................................... 56
Data Connection ........................................................................................................................ 56
Mounting................................................................................................................................... 56
HANDHELD DEVICE ..............................................................................................................59

KEYBOARD ...........................................................................................................................61
THERMAL RECEIPT PRINTER .................................................................................................62
10.8.1
10.8.2
10.8.3
10.8.4
10.8.5
10.8.6
10.8.7
10.8.8
Function .................................................................................................................................... 62
Specification ............................................................................................................................. 62
Data Connection ........................................................................................................................ 62
Mounting................................................................................................................................... 62
Operational Requirements.......................................................................................................... 63
Header Information ................................................................................................................... 64

Page 4 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
5 of 65
1.
DOCUMENT INFORMATION
1.1 Document Purpose and Content
This document is submitted by Metro Infrasys Pvt. Ltd., in response to the technical documents
supplied as a reference for the project Supply, Installation and Maintenance of Parking Management
System.
The purpose of this document is to present a detailed description of Parking Management System
(PMS)
Please note that this is a confidential document and that it is submitted in the understanding that it
will not be disclosed in whole or in part to any party other than the directors, employees and agents
of the committee who have a need to know; and that it will only be used for the purpose of Tender
Assessment. This document is intended for both the stakeholders and the developers of the system.

Page 5 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
6 of 65
1.2 List of Abbreviations

Abbreviation
Comment
CCU
Central Control Unit
CPU
Central Processing Unit
FAQ
Frequently Asked Questions
MIS
Management Information System
PMS
Parking Management system
RFID
Radio Frequency Identification
RFP
Request for Proposal
UPS
Uninterruptible Power Supply

Table 1- List of Abbreviations

Page 6 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
7 of 65
1.3 Definitions
Terms
Central Computer
Definitions
A computer system that is connected to all other computers under the PMS
through the communication network. The Network control software runs at the
Central Computer.
Central Control Room
Control Centre is the place where servers are kept for storing the data & for
administration purpose.
Communication Network
A wired or wireless facility used to send and receive data between the Entry
device and Control Room
Entry Point
Entry Point is the point where ticket will be issued to the user who wants to park
the vehicle.
Exit Point
Exit point is the point where the ticket will be validated and payment process
done
Pay Station
POS
Ticket Dispenser
Place where the parking fare will be collected from the user.
Point Of Sale A station where recharge can be done.
A device from where ticket can be generated
Table 2- Definitions

Page 7 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
8 of 65
2.
INTRODUCTION
Based in New Delhi, Metro Infrasys formerly known as Metro Infrasys (www.metroinfrasys.com)
is one of the leading players in the field of Intelligent Transportation Systems and has an impressive
track record of collaboration with the top construction companies in India and is driven by the
philosophy of dynamic engineering based on reliability.
Drawing on comprehensive research and contact with international companies abroad, Metro
Infrasys offers the best of what is available for Traffic Management Solutions, adapted using local
knowledge and expertise to suit Indian conditions and operational environments.
It is emerging as a Leading Indian company in the field of Intelligent Transportation Systems by

having made foray in the following fields of ITS:
- Toll Collection Systems
- Parking Management Systems
- Weigh in Motion systems
- Service Centre and Assembly and Testing unit - The Company is having in house Engineering
Development & Software Development Center Manesar Industrial Area on NH-8 in Gurgaon,
where a state-of-the-art service and maintenance centre has been constructed, complete with a
fully equipped mock toll lane and 24x7 support environment.
Metro Infrasys has set a Service, Integration and Development centre as per the international
standards based at IMT Manesar, Gurgaon (Haryana). Here the company has made a state-of-art
Mock Lane through which it demonstrates various technologies for Tolling, Traffic Management
and Parking and is used for Simulation, Testing, Innovation and Trainings.

Page 8 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
9 of 65
2.1 Roles and Responsibilities
1. Responsibilities of METRO
a. Program Management
b. Solution Design Validation
c. Quality Assurance & Validation
d. Coordination with Client
2. Responsibilities of Metro
a. Solution Design
b. Installation and commissioning of all equipment
c. Coordinate for technical assistance
d. Control Room Construction
e. Installation of all equipment at Entry and Exit Lanes

Page 9 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
10 of 65
3.
PROPOSED SOLUTION
This proposal deals with the General Technical Solution for the Parking Management and
Guidance System. The Systems Consists of Entry and Exit Lanes controlled by control
centre for the parking.
3.1 System Architecture
Figure 1- System Architecture

Page 10 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
11 of 65
3.2 Functional Overview

The application will have below nodes or point of operations stated as follows:
3.2.1
Entry Lane
1. Vehicle user sees the available parking slot at outdoor LED display and enters at parking
area.
2. After this, User press the ticket dispenser machine PUSH button and ticket will be issuing
to the vehicle user by ticket dispenser machine.
3. Issued Ticket shows date and time at which ticket was issued.
4. As parking slot is assigned to a vehicle, the parking display will automatically reduce one
slot at the particular parking level.
5. As vehicle comes at Entry Loop, barrier get up and User will Park the vehicle at the
assigned slot at parking ticket.
3.2.2
Exit Lane
Payment Station (Manual POS)
1. Manned POS deploys at service kiosks or at the car park exit.
2. At time of Exit, user gives his ticket to the cashier at payment centre (POS).
3. Cashier at Payment centre scan the ticket by scanner.
4. Vehicle User pays the parking charges as per vehicle stay in parking area.

Page 11 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
12 of 65
3.2.3
Control Room
1. All the real time information will update at Central Server.
2. Vehicle image at entry and parking details will store at server.
3.2.4
Online Services
1. We can do multiple parking Lots Monitoring
2. We have Central Reporting System on a single server from Central Office.
3. We can provide facility of Remote Monitoring view of entire parking facility in all locations
from a single location.

Page 12 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
13 of 65
4.
PROPOSED HARDWARE
Entry Point
Entry Point is the point where ticket will be issue to the user who wants to park the
vehicle. Each entry lane will be equipped with one Automatic Entry Device/Ticket
Dispenser. As Vehicle detects at the lane by the presence loop, Vehicle User press the
Ticket Issue/ Push button, a barcode ticket will be issue.
Barrier at Entrance & at Exit

As ticket issued by the ticket dispenser, barrier, at entrance will get up and the user
park the vehicle. At the time of exit, barrier at exit will get up as after ticket
verification from payment station.
Exit Point/ Payment Station

Exit point is at the area where the ticket will be validated and payment process done
and henceforth user will be allowed to exit the parking area.
Control Centre
Control Centre is the place where servers are kept for storing the data & for
administration purpose.The data of the entire parking area for movement of all entries
and exits are automatically stored and controlled at the Server, replicated to the
backup server. The Server ensures that each card or generated ticket follows a
complete cycle of entry and exit, and that the operator does not steal any money from
the cash drawer, it offers security.

Page 13 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
14 of 65
4.1 Hardware Required at Parking Entry

Entry Lanes
Entry Lanes will be equipped with listed equipments:
1. Presence/ Entry Loop
2. Ticket Dispenser Machine
3. Automatic Parking Barriers at Entrance
4. Parking Information Display
4.2 Hardware Required at Parking Exit

Exit Lanes will be equipped with listed equipments:
1. Presence/Entry Loop
2. Automatic Parking Barrier at Exit
3. Parking Information Display
4. Handheld Device
5. Thermal Printer
4.3 Exit Payment Station

Payment Station will be equipped with listed equipments:
1.
Smart Card Reader
2.
Barcode Scanner
3.
Workstation
4.
Monitor
5.
Thermal Receipt Printer
6.
Keyboard

Page 14 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
15 of 65
4.4 Hardware Required at Control Centre

Control Centre
Control Centre will be equipped with listed equipments:
1. Central Database Server
2. Workstation ( POS, Audit)
PMS
Server
POS
WorkStation
Audit
WorkStation
CONTROL
CENTRE
Central Control Room

Page 15 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
16 of 65
5.
SOFTWARE DESCRIPTION
The proposed Parking Fee Collection System supports the cash payment, Electronic
payment. The equipments are capable of accepting, validating and recording Parking Fee
Transactions under any one of the following methods of payment (MOP):
Cash Payment
Electronic Payment
Hence the proposed system will provide the capability to handle all the above transaction
modes, or as many as possible.
5.1 Monitoring
The Parking Fee Collection System has extensive monitoring mechanisms for keeping
track of all the operations at the Lane PC Level.
The system shows the standard view of all the lanes from the central plaza controller. Fully
functioning systems are shown in green, while systems that are either not operational are
shown in the status as online or off line.
This system allows centralized control and maintenance of the entire Parking Fee Collection
System from a central location with minimum effort.

Page 16 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
17 of 65
5.2
Central Control System

The Control Center is required to configure the system as followed:
Create Login
To create the login to any of the users which has to be assigned in any of the lanes it
consists of the following fields:
Login ID
Password
Confirm password
Description
Create Operator
The Operator has to be defined for the shift with to & from date and shift name &
Operator ID. The Operator has unique ID which has to assign for particular lane and the
same can be set on any day and the particular date.

Page 17 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
18 of 65
Create plaza
It is required to create a new plaza if the parking is connecting with another parking
with its entry and exit lanes and the main plaza is controlling all parkings
simultaneously. This is also used for having the combined report at the center.
Create Shift
This screen is used to define the shift, the timing of the shift for the whole day.
This screen has the following input:

Shift name given for the shift
Shift Description
Starting time and End time of the shift

Page 18 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
19 of 65
Create User
This screen is used to create the user for all this functions:
Create card/ Ticket issuing

It is required to create card/ Ticket issuing and it has to be configured.
The lane will have the following entries:
Receipt
Vehicle Number
Date & Time
Parking Fare

Page 19 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
20 of 65
5.3 Levels description

5.3.1
Lane level
To allow for the manual collection of money, enabling the Parking cashier to receive
and handle money.
To provide online feedback to the system administrator in order to continuously
report, the status of the various lane devices and the current operational status,
including shift information.
Lane Module
Lane module is located in the lane which provides the GUI for the operator. All the
hardware modules are integrated & connected to this interface. The business logic is
controlled & operated using this module.
Lane computer system operates independently in case of server or network

communications error.

Page 20 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
21 of 65
Monitor
Keyboard
Industrial
Motherboard
I/O Card
Inductive
Loops
UFD
Boom Barrier
Though the architecture designed for the solution is client server configuration but
Lane module has capability to act as completely independent system. The master
tables are updated on a specified time interval whereas transactional data is
replicated into main database.
Access to the lane application is controlled via username & password. All the
transaction data will be saved in encrypted form of data packets and then replicated
in the Main Admin database from the local database. The Reporting module will use
this collected data for generating the reports.

Page 21 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
22 of 65
All Transactions are sent to the Admin Server database. Backup utility will take
back process to protect the sensitive data.
The GUI developed for the application is comprehensive simple yet secured so as to
assure that no tampering is possible.
The following hardware will be attached to the lane application:

1.
2.
3.
4.
5.
Entry Loop Detector

Industrial Lane Controller
Keyboard
Automatic Boom Barrier
Network cabling to connect all Entry/Exit Lanes & Admin
System architecture is so designed to trace the possibility of any faults in advance.

Health status check up is done at the equipment interface level and updating the
same in database as well as at the monitoring units. Specially designed interfaces are
available in the solution to pick up the real time status for fault detection &
rectification in least possible time to improve the overall system uptime.

Page 22 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
23 of 65
5.3.2
Admin level
The Admin level is the set of software and hardware used to gather information from the
entry point/Lane, and to monitor their functioning. The purpose of the Admin level is to
consolidate the information collected by the lanes, and to provide overall monitoring and
control for the lane equipment. Other functions such as shift conciliation and real time data
handling are also responsibility of the admin level.
This level fulfils with all requirements established for the Access Control System (ACS),
this is among others receiving all information transmitted by the Entry points/lanes and
verifying transactions, providing Entry point controller/operator control and performance
facilities, and includes a host of management tools and reports for the effective
administration of each Entry point. The Admin level also assists in auditing the Entry
lane/point operation. It is conceived as different modules that performs independently the
different levels of the Entry point operation.
Admin level architecture

The typical Admin level contains:
A server PC that receives and stores all the data from the Entry lanes.
One or more network printers for reports, shift conciliation documents, etc.

Page 23 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
24 of 65
Admin Server
The Admin Server is the main component of the Admin level. All other clients connect to
it during their normal operation, including the corresponding lanes.
The main functions of the Admin server are as follows:
To handle messages coming from the lanes

To manage the delivery of commands and messages to the lanes
To control shifts and sub-shifts
To keep the lane states updated
To automatically generate files to update the lanes
To generate a back up file of the communication with the lanes
Admin Module
Also known as Configuration utility, this module is present at the Admin level. A
dedicated workstation can be provided which will have access controlled login activity.
The purpose of Admin Application is to provide the feature to set all Masters which we
are utilized in proposed solution.
Admin Module includes:
To Create Systems Users
Assign User Name and password for Login into system
Assigning their roles and rights for every module
Configure Lane Details
Set Vehicles Details

Page 24 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
25 of 65
System User Detail

Admin Server
System User Detail
Violation Type
Dash Board
Incident Type
Admin Application
Cash Up
Ticket/Smart Card
holder Details
POS
Ticket/Smart Card
holder Details
Lane Description
Lane
Description
Ticket/Smart Card
holder Details
Incident
Type
Fare Detail
System
User Detail
Violation
Type
Exemption Details
Lane Application
Figure 2 Typical Dataflow Diagram for Admin Module
The Application is designed on 3-Tier Layers:

a. Presentation Layer
b. Data Access Layer
c. Business Logic Layer
Page 25 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
26 of 65
Admin login

Page 26 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
27 of 65
Manage Masters

Page 27 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
28 of 65
Login settings

Page 28 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
29 of 65
Reports

Page 29 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
30 of 65
5.3.3
Point Of Sale Module

The purpose of POS Application is to provide a facility through which Smart
Card/New Account can be issued. It should be located at Admin level/or at Exit lane
according to the requirements. It is through this module itself where in accounts for
various passes can be opened or recharged.
User will manage the all pass transaction like issuing the monthly, daily passes and
visitor passes maintaining the accounts of Employees, Visitors Drivers etc., the
system caters of the following:
1. Show the all account holder detail
2. Show the status of the passes like Cardholder and card expiry date etc.
3. Show the all black listed passes.
4. Reissue the passage and cards.
Following is the functional flow diagram which signifies POS operation.
POS Layout
Passes can be in form any media compatible to the application either be it Smart Card or
Bar-coded card prints. Passes are issued after entering the complete personal & commercial
vehicle details in the system. These details are stored in the memory media.

Page 30 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
31 of 65
5.3.4
Cash up Module
Also know as Reconciliation Module. The purpose of Cash UP Application is to
provide a platform wherein declaration of the cash amount collected can be done by
lane or PoS operator. This module keeps the records of all cashed up shifts for
further use and allow user to check the revenue declared by him and system
generated revenue.
Cash up Module is a software component in charge of contrasting the collection
declared by the cashiers with the one detected by the system through the transactions
informed by the lanes. Its main functions are:
Conciliation of closed shifts

Rendering of closed shift money to the external collection companies
Enabling shifts to be re-conciliated
Generating conciliation reports
It will handle the total concept of Revenue Declaration.

The post shift revenue declaration by the operator is done without knowing the
system registered amount. The whole concept of cash up is build to keep a micro
level check on the revenue collection. Following is the screen shot which signifies
the declaration of collected revenue.

Page 31 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
32 of 65
Cashup application generated report acts as the principle proof of collection done by the
user. To further strengthen the agreement hard copy of the report is signed by operator &
shift supervisor.

Page 32 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
33 of 65
6.
PARKING MANAGEMENT
The System allows the administration to control the parking lots, including the control of
barriers and traffic lights. The system provides the possibility to limit the number of
vehicles inside a parking lot so that a balancing is possible, and the traffic lights are
controlled accordingly. This network-enabled configuration opens up many possibilities for
Smart Card and ETC-based access control systems.
6.1 Parking Entry Front -End

Page 33 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
34 of 65
6.2 Parking Exit Front End
Car Entry Exit Image Verification: It is a standard feature provided in the software
for taking photos, scanning or importing car images from the parking database, such that
stored cars image can be displayed automatically during Exit on the workstation during
access monitoring or for photo verification purposes.
The operation at exit gates can be done manually as well as automatically. As soon as Car
reaches at Exit point the Smart Card Reader verifies the access for car, but still it is upto on
the operator that he lets the car go. The operator check the live image taken by the camera
to the previous/Entry time photo from the database if both matches then only he opens the
door.

Page 34 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
35 of 65
7.
SYSTEM AUDIBALITY AND REPORTS

The Parking Fee Collection System is extremely sophisticated software, and performs an
incredible range of functionality to support every aspect of Parking collection, management
and control. One of the most powerful features of this system is the extensive set of reports
to be able to view practically every aspect of the operation of this complex system. The
entire set of system management, audit ability, and reports is discussed in this section of this
document.
7.1 System Monitoring
The Parking Fee Collection System provides a system monitoring console to be able to
view and manage practically every aspect of the hardware and system at each Parking booth
within the plaza. The console can be used in one of two modes:
1. To get an overview, i.e. to monitor the hardware of all the lanes to verify that
all equipment is in working order. Any lane that is not fully functional is shown
highlighted. The administrator can then click on that lane icon to drill down and
get more detailed information about all the equipment for that lane.
2. To view the drill down information about one particular lane to see every
equipment and their status within that lane. SNMP in order to interface with each of
this equipment, and to report on their status. Any equipment that is not functioning is
show highlighted in this drill down diagram.

Page 35 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
36 of 65
7.2 System Reporting

Page 36 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
37 of 65
7.2.1
Hourly transaction report

This report is use to print Hourly based traffic of vehicle. It prints Number of vehicles
entered in parking area and all vehicle exits from the parking area in specific hour .
a) Select Date From and To date
b) Select report type i.e. if you want print either all entry vehicle detail only or
all exit vehicle detail only or both
c) Select Mode Type daily report or monthly report
Hourly Transaction Report

Page 37 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
38 of 65
7.2.2
Pending Vehicle Transaction Report

This report is used to print all vehicles which are currently parked into parking area.
Pending Vehicle Transaction Report

Page 38 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
39 of 65
7.2.3
Pass Transaction Report

This report is used to generate all pass transaction done in between given date and
time.
Pass Transaction Report

Page 39 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
40 of 65
7.2.4
Search Vehicle Detail Report

This report use to print the detail of the any vehicle entered into the parking area like
Account holder name, entry time and exit time of vehicle etc.

Page 40 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
41 of 65
Search Vehicle Detail Report

Page 41 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
42 of 65
7.2.5
Summaries Transaction Report
Summaries Transaction Report

Page 42 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
43 of 65
7.2.6
Detailed Revenue Report
Detailed Revenue Report

Page 43 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
44 of 65

Page 44 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
45 of 65
8.
PROJECT SUPPORT AND MAINTENANCE

We ensure that sufficient suitably trained staff are on site for the warranty period maintenance of 6
year and shall ensure at all times.
The following aspects of the maintenance for the warranty period shall be defined.
We will provide a comprehensive maintenance manual at the time of submission of the tender
documents, the manual will be complete and in line with the equipment being provided.
8.1 Preventive Maintenance
Preventive Maintenance is defined as any works carried out in the lane area, plaza area, Junction area
that is continuous and planned in nature.
We will at the beginning of each month, no later than the 3rd working day, provide a Preventive
Maintenance Schedule to the designated officer, a copy will be sent to the reporting officer. The
schedule shall be required to be signed as the maintenance activities are executed by the Maintenance
Engineer and the designated officer.
Completed reports will be sent to the higher Authority on a monthly basis.
8.2 Corrective Maintenance
Corrective Maintenance is defined as works carried out at the highways and Junction area that aims to
rectify/repair a fault or problem that may be causing the equipment to function in a manner that creates
operational problems.
This may be done at any time. The categories of corrective maintenance are provided below with
response times to repair the fault.

Page 45 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
46 of 65
Time to Respond
Time to
Repair
Total Time
< 4 Hour
< 8 Hours
< 8 Hours
< 8 Hours
< 18 Hours
24 Hours from Notification
< 24 Hours
< 48 Hours
72 Hours from Notification
Category
8.3 Daily inspection Forms

Ours maintenance engineer will on a daily basis inspect ALL the equipment at and will be required
to log all inspections on the Daily Inspection Report (Equipment).
8.4 Fault Notifications

The fault notifications will be logged in a bound register, the register will be located in the control
room. We will provide the necessary fault notification registers; this shall include the following
items:
Study Bound Register
Each Page Sequentially Numbered
Junction Name
Original Plus 3 Copies (Self Carbonising Paper)
Original White Paper
Ours Copy (Yellow)
Technical Manager Copy (Pink)
Fields Required (this can be discussed with the Engineer)
Date of Fault
Time of Fault
Equipment - ID

Page 46 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
47 of 65
Equipment Faulty
Description of Fault
Officer Signature
Date and Time Fault Logged
Date and Time of Engineer Arrival at Site
Fault Found
Spare Used
8.5 Warranty Spares
We will provide a comprehensive warranty on all items which have been supplied in the Equipment
Supply Tender; under no circumstances shall the warranty of any equipment be compromised by the
installation of an interface card into any of the equipment supplied. ALL the equipment shall be fully
covered by the warranty period provided by us. All items shall be fully covered for any type of failure
that takes place.
The spare parts ordered in the Supply Tender will be used for the replacement of items that have
become faulty during the warranty period. The spares used will be replaced by us as per contract and
defined SLAs.
We ensure that all spares as supplied above are fully functional, (except those written off or scrapped
during this period) at the end of the warranty period when handover of the equipment takes place.
8.6 Accident Damage
The customer will be required to provide the items that have become damaged due to vehicle impact
and or fair wear and tear.

Page 47 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
48 of 65
8.7 Logging of Faults

We ensure that a fault register is provided with details to be recorded in the event of the equipment
not working. The register will be provided by us and will be finalised in consultation with the
Engineer.
8.8 Weekly Report

We will provide a weekly report which fully covers all the following points,
Consolidated Daily activities
Daily fault log
Repairs completed
Repairs outstanding
8.9 Monthly Report

We will provide a monthly report by the 3rd working day of the month the report will include the
following,
Faults for the Month, including historic graphs
MTBF Reports, per equipment per lane, including historic graphs
Equipment Availability Reports, per equipment per lane, including historic graphs
Completed Maintenance for Previous Month
Software problems, fixes proposed
These reports will be discussed in detail in the Monthly Maintenance meeting.
8.10 Office Space

We will be provided with a limited amount of office space and workshop/store in which he can work
during the hours of duty.

Page 48 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
49 of 65
9.
TECHNICAL SPECIFICATIONS
Data Sheets for following has been enclosed separately in below section.
9.1 Server
We are providing servers for the project. The server specification together with the planned
network layout will be provided. We also provide the rate for supply, installation and
configuration of the servers together with all Operating System licenses this will include but not
be limited to,
PMS Application and Configuration,
Dual Data Stream Application and data reconciliation with PMS,
Network Configuration including

Firewall Configuration,
Database replication at head office
Database Configuration
User Account Management
All Vital Tables
All Tariff Tables
All Discount Tables
Installation and Configuration of the Anti Virus Software
Plaza Level
Lane Level
Install any other software that may be required for PMS

Page 49 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
50 of 65
9.1.1
Server Racks
We provide a suitable 42U rack with all equipment fitted, this will include but not be
limited to cooling fans, power distribution doors and locks, all doors and side panels shall
be removable for ease of access. All doors shall be fitted with good quality locks, all keyed
alike. The server rack shall be big enough to be able to accommodate the servers and have
sufficient space for cooling.
9.1.2
Server UPS
We provide a 6 KVa dedicated UPS for the server, with sufficient battery backup for 30
minutes.

Page 50 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
51 of 65
9.2 Ticket Dispenser
Main Unit :
Side Frame supporting cutter and thermal printer modules.
Fan folded pack or reel form handling.
Single or dual way dispenser configuration
Easy BarCode scanner module replacement
Ticket validation capability
Bottom ticket capture device
Contactless card management based on Mifare standard
ISO/IEC- 14443A & B + ISO-15693
Communication by means of RS 232/RS 485 Serial Interface or USB.
Technical Specification:
Thermal Printer:
Printing Method: Thermal
Print Width: 48 mm
Dot per Line: 384
Abrasion Life: 50 Km min
Environmental:
Operating Temperature: From 0 to 50C
Storage Temperature: From -20 to + 60C
Relative Humidity : From 20 to 80%

Page 51 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
52 of 65
9.3 Smart Card Reader

9.3.1
Function
The unit will be used to read Smart Cards as well as be used for the log-on and log-off of the
Parking Collectors and other staff authorised to access the toll lane system, be this for the
purpose of collection of revenue, report checking or technical requirement.
9.3.2Specification
The T&G contact-less smart card reader will conform to the following specifications,
Card Interface
Operating Frequency
13.56 MHz
Full ISO 14443 -1 to 4 compliant, embedded T=CL
protocol
Read/write the following Smart Cards:
Compliance
- ISO 14443 A, B, T=CL cards

- Mifare cards (including DESFire)
- SR176, SRIX512 and SRIX4K chip based cards
9.3.3
Baud rate
106 Kbps, 424 Kbps or 848 Kbps
Reading distance
up to 10 cm
Electrical Connections
We will ensure that any power supplies required for the successful operation of the Smart
Card Reader is fully enclosed and incorporated into the equipment enclosure, no external
power supply units shall be allowed in the lane environment.
Proper electrical earthing as required and recommended will be strictly adhered to at all
times.

Page 52 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
53 of 65
9.3.4
Data Connection
The integration of the Smart Card Reader into the parking lane computer will be required to
ensure the quickest read/write time available is required.
9.3.5
Mounting
The unit shall be mounted on the outside of the toll booth in a position which will allow for
easy use by the motorists, the mounting shall be done using a suitable mounting plate and the
reader shall be mounted in a position so as not to have a negative impact on the read/write
distance. We will provide a suitable stainless steel mounting bracket onto which the
contactless smart card reader shall be mounted. The brackets shall have a clearly visible
operation pictogram pasted onto the bracket ,we shall provide this for approval before
manufacture.
9.3.6
Environmental Factors
The CSC will conform to the following specifications

Operating temperature range
-20 C to +70 C (-4 F to +158 F)
Humidity
9.3.7
0 % to 93 % non condensing
Environmental Protection
The CSC reader will conform to the following IP ratings

Index of Protection
9.3.8
IP67
Signage
The signage shall conform to the Universal Contactless Smart Card Reader Symbol. We shall
paste a suitable sticker on all external readers provided.
Figure 3 Smart Card Sign

Page 53 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
54 of 65
9.4 Bar Code Reader

9.4.1
Function
A Bar Code Reader (BCR) will be used to read daily passes (up/down trip) and the bar code
encoded on the rear of the Smart Cards that are issued for monthly, exempt and regular users.
9.4.2Specification
The bar code reader will conform to the following specifications,
Width of Window
74 mm
Light Source
660 nm visible red LED
Ambient Light
Up to 80000 Lux
PCS
30% or more
Resolution
0.1mm (4mils) - Code 39,PCS=45 %, on contact
Scan Speed
200 scans/sec
Maximum scanning distance
0-10 inches
Scanning angle
Front: 60 Rear: 60 Yaw: 75
Interface
Keyboard, RS232 , USB Interface
Codes Read
UPC/EAN/JAN & Addon 2/5, Code 39, Code 39, Code 39 Full
ASCII, Code 11, Interleave 25, Industrial 25, Matrix 25,China
Postage, Code 128, Codeabar/NW7, Code 93, MSI/PLESSEY, Code
32, BC 412 and All Standard Linear Codes
2D Codes: PDF147, Code 16K
Operating temperature
0-40C.
Environment
5% to 90% relative humidity, non-condensing
Options
Stand for continuous read mode
Shocks
1.5m drop onto concrete

Page 54 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
55 of 65
9.4.3
We ensure that any power supplies required for the successful operation of the bar code
reader is fully enclosed and incorporated into the equipment enclosure, no external power
supply units shall be allowed in the lane environment.
9.4.4MTBF
The BCR will be able to read at least 2,500,000 transactions before being replaced.
9.4.5Environmental Factors
The BCR will conform to the following specifications
Operating temperature
range
-20 C to +70 C (-4 F to +158 F)
Humidity
0 % to 93 % non condensing
9.4.6Environmental Protection
The BCR reader will conform to the following IP ratings,
Index of Protection
IP 64

Page 55 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
56 of 65
9.5 Boom Barrier
9.5.1
Function
The function of the lane barrier is to control the passage of vehicles through the lane after
payment of the required toll fee.
Each lane shall be fitted with a lane exit barrier, the exact location of the lane exit barrier shall be
provided by us at the time of tender.
9.5.2
Boom Specification
The lane exit barrier shall conform to the following specification,
Open time
0.9 sec
Close Time
0.9 sec
The boom arms shall be fitted to a swing away mechanism to prevent damage to the lane exit
barrier mechanical parts in the event the lane exit boom arm is struck by a vehicle in the lane.
9.5.3
The lane exit barrier shall be connected to the UPS supply. All connections and wiring shall be
neatly installed and the earthing of the lane exit boom enclosure shall be done in strict
accordance with the guidelines/specifications.
A single 40mm conduit shall be provided in the island for the electrical cable.
9.5.4
Data Connection
The lane exit barrier receives a signal from the Loops to open and close.
A single 40mm conduit shall be provided in the island for this purpose.
9.5.5
Mounting
The lane exit barrier shall be mounted on the island at the location indicated by the equipment
contractor for the lane exit barrier pedestal. The civil contractor shall cast the cage bolts into the
island, it should be noted that we will provide these cage bolts within 28 days of award of letter
of award. The cage bolts shall be galvanised and supplied with at least 4 sets of templates to
ensure alignment of bolts is correct. We shall ensure that an engineer is on site during this

Page 56 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
57 of 65
process to ensure alignment and location is perfect. Failing to provide the cage bolts shall result
in mounting the barrier with an alternative method.
We shall provide all details of civil work required for the installation of the lane exit barrier. The
location of the lane exit barrier in relation to the Antenna shall be such that the driver of
the vehicle does not have to slow down at all, the opening time of the lanes fitted with
readers and configured as dynamic lanes shall be no less than 0.9 seconds. We shall be
required to prove that a queue of at least 25 vehicles fitted with the TAG is sent through the lane
to ensure compliance. We will be required to prove this at the SAT and shall ensure that under
no circumstances the performance of the lane is reduced in any manner by the lane exit barrier
not being located in the correct location for fast and efficient operation of the non stop lanes.
The lane exit boom shall not be mounted closer than 350mm from the island edge.
9.5.6
Environmental Factors
The lane exit boom will be installed with only marginal protection from the rain and heat.
We ensure that the boom is mounted on a suitable plinth no less than 25mm high and no higher
than 35mm. We will be responsible to cast this pedestal on top of the island. The conduits for the
tunnel or manhole shall be raised a further <50mm above the pedestal to ensure water ingress
into the conduit is not possible.
Lane
Exit
Barrier
Pedestal
Island
Figure 4- Pedestal for Lane Exit Barrier

Page 57 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
58 of 65
Conduits
Pedestal
Island
Figure 5 -PVC Conduits <50mm above Pedestal Top
9.5.7
The barrier shall be powder coated RAL 2000 colour. The enclosure shall be equipped with a
lock to remove panels. The top cover shall be easily removable for maintenance purposes. All
cage bolts, washers and nuts used to mount the barrier shall be galvanised.

Page 58 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
59 of 65
9.6 Handheld Device
Features
Performance
Specification
Description
Processor
Operating System
TIAM3715 or TIDM3730 @ 1GHz ARM Cortex A8
Memory , Flash
LPDRAM: 256MB/512MB, NAND Flash:256MB/512MB
Display Resolution
3.5 inch 240 x 320 Pixels / 262,000 Color, Touch Screen, Sun
Readable optional
Interface
1 USB (OTG t ype) , 1 USB (Host)
Expansion Slot
Mini SD Card Slot
Audio & Vibration
Speaker (mono) x 2, Microphone x 1
Microsoft Window CE 6.0 R3 or Windows CE 7.0
Key Specification
Alpha & numeric Keys, Navigation Key (Total 20 Hardware Keys )
PCI
PCI 3.0 Online/ Offline Certification
Smart Card
EMV L1&L2 Certified Smart Card Reader, 2 SAMs slot
Magnetic Card
Reader
Printer
Printer Paper
OPTION
ISO7811 Triple Track (track 1, 2, & 3)

2 inches High Speed, High resolution, thermal printer
Diameter=25mm, width=48mm
Camera
3.1 M Pixel CMOS with LED Flash Light
Barcode Scanner
RFID
Biometric interface
GPS
WALN
1D (2D optional)
Mifare A/B Type
FingerPrint Interface
SiRFstarIII GSC3e/LP
802.11 b/g
Bluetooth
BT Class2.0EDR supports OBEX, SPP, PAN profiles
Power
2000mAh Liion Removable / Rechargeable Battery
Communication
Interface
(builtin)
GSM/GPRS/EDGE /CDMA/3G Modem, 1 USIM slot.
Physical
Dimension (mm)
205 (L) x 86.5(W) x 56(H) mm

Page 59 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
60 of 65
Specification
Accessories
Secure
Performance
Specification
Weight
500g
Operating
Temperature
20C to 50C
Default
User's Manual, USB Cable, Stylus Pen,
Other
AC adapter, EarMic phone (Mono), Cradle (option)
Processor
Operating System
Memory , Flash
Display Resolution
Interface
MAXQ1850
VOS
Share Flash
Share
UART

Page 60 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
61 of 65
9.7 Keyboard
The classification buttons provided shall be located in an easy to use location on the TCT. The
Classification buttons shall be double width buttons and shall be colour coded making them easier to
see. Each class shall have a different colour as agreed with the engineer. A sample is provided
below.
Figure 6- KeyBoard

Page 61 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
62 of 65
9.8 Thermal Receipt Printer

9.8.1
Function
The Lane Printer will be used to print the receipt of the transaction as well as provide balance of
accounts for the pre-paid motorists.
The receipts will be printed on demand normally or automatically if the settings on the lane INI
file indicate that they should be printed on demand. This setting may be modified by the plaza
manager via a menu option.
9.8.2
Specification
The Printer will be of compact size and use readily available thermal paper rolls of a standard
size with marker stripe to indicate the end of the roll. If dot matrix printers are used, the printer
shall use a readily available inexpensive ribbon, preferably in nylon and be contained in a plastic
cassette. The print rate should be sufficiently fast to print the details of receipt or of a transaction
in less than 2 seconds.
9.8.3
The Electrical Connection to the printer will be done by using a suitably rated socket and
plug/cable provided in the Unit, the removal of the power socket from the rear of the printer shall
not be possible without using a suitable tool to remove the plug/power cable.
9.8.4
Data Connection
The Data Connection for the printer will be from the Unit. The data cable will be secured to the
printer using standard industry connectors with suitable screws that cannot be removed without
the use of a suitable tool. Sufficient slack will be provided to ensure easy access for maintenance
purposes. The printer will not be able to print when the paper and or mechanism covers are
removed.
9.8.5
Mounting
The Lane Receipt Printer will be located in the tollbooth and mounted in a position that will
allow the operator to easily reach a receipt and local mode EOS documents printed on the printer.
The design of the tollbooth will be designed to ensure the maximum ergonomic design is
achieved. The power and data cables shall be secured and covered to look neat and professional.
The printer will not be able to move around on the worktop and a suitable arrangement will be
provided to secure/hold the printer to the worktop.

Page 62 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
63 of 65
9.8.6
Operational Requirements
The following operational requirements will be provided but not limited to the printer that is
supplied with the toll collection equipment.
The printer will be able to generate a paper low warning but is not a requirement and shall be
able to generate a paper out message. This message will be sent to the Unit and it will
display this message on the toll collectors screen.
The Unit will ensure that
communications between the printer and unit are monitored and that in the event of a
communications failure or if the printer is offline that a warning message is displayed on the
screen. These incidents will be logged in the PMS.
The printer will be able to print Hindi Character set including the rupee symbol.
The printer provided will be have the following minimum specifications,
Minimum Printer Specifications

Print Speed - 200mm/sec
Line Spacing - 3 or 4mm (default)
Resolution - 203 dpi
No. of Columns - 48 (default), Maximum 71
Barcodes - UPC-A/E, JAN/EAN8/13, Code 39/93/128, Codabar (NW7)
Paper Specs - Thermal roll paper Width 80mm default, 58mm adjustable
Roll Diameter - Maximum 90mm
Paper Loading - Drop-in
Paper Sensors - Near End, Paper Out, Cover Open
Reliability - Printer Cutter 60 million lines MCBF (CRT) 1500,000 Cuts
Operating Temperature - 5 to 45C
Operating Humidity - 5% to 90% RH (w/o condensation)
Interface - Serial (RS232C), Parallel, USB
Data Buffer - 8K bytes (or better)
Logo Store - 2M bit
Emulation - Star line mode & ESC/POS mode

Page 63 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
64 of 65
Drivers - Windows 9x/NT/2000/Vista/Windows 7/XP, OPOS, JavaPOS, Linux, Star

Raster Graphics & Mac OSX
9.8.7
The printer will be mounted in the booth and will be required to be work in an environment that
has dust and fumes entering the booth. The printer will be able to withstand the rigours of this
type of operating environment.
9.8.8
Header Information
We will ensure that the Header Information to be printed on each receipt will conform to the
following minimum specification. The header information will be printed on every receipt,
transaction record or any other printout in the lane.
A header will consist but not limited to 2 lines of expanded font double height letters
with a total of 24 characters per line.
A further eight line of single space characters with an average of 30 characters per line.
The total length of the printed receipt is estimated at about 85mm.
The header and other publicity message details shall be printed in advance for each
transaction.
The header information is provided below,
Company Name
Plaza Name and Contact Details
Tax Information
Toll Collector ID
Lane Number
We will ensure that the header information is correct in every respect before COD. All spaces,
line spacing, formatting and information shall be required to be approved and accepted at the
time of SAT.

Page 64 of 65

(PMS)
Document Name
Version
Issue Date
Page
PMS
V 1.0
01st July2015
65 of 65
END OF
DOCUMENT

Page 65 of 65

Technical Proposal - Parking - Mysore Mall

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Technical Proposal - Parking - Mysore Mall

Transféré par

Droits d'auteur :

Formats disponibles

PARKING MANAGEMENT AND GUIDANCE SYSTEM

Mysore Mall Parking

Parking Management System

DOCUMENT INFORMATION ................................................................................................. 5

HARDWARE REQUIRED AT PARKING ENTRY..........................................................................14

SOFTWARE DESCRIPTION ...................................................................................................16

SYSTEM ARCHITECTURE .......................................................................................................10

ROLES AND RESPONSIBILITIES ............................................................................................... 9

PROPOSED SOLUTION ..........................................................................................................10

DOCUMENT PURPOSE AND CONTENT ..................................................................................... 5

PARKING ENTRY FRONT -END...............................................................................................33

Confidential: Unauthorized disclosure, copying and distribution are prohibited

Metro Infrasys Pvt. Ltd.

Parking Management System

SYSTEM AUDIBALITY AND REPORTS ...............................................................................35

Hourly transaction report ............................................................................................................... 37

8. PROJECT MANAGEMENT & EXECUTION METHODOLOGY ...... ERROR! BOOKMARK

BUSINESS EXCELLENCE MODEL ...................................... ERROR! BOOKMARK NOT DEFINED.

Steering Committee ..........................................................................Error! Bookmark not defined.

PROJECT SUPPORT AND MAINTENANCE ........................................................................45

PREVENTIVE MAINTENANCE .................................................................................................45

Server Racks ............................................................................................................................. 50

TICKET DISPENSER ...............................................................................................................51

Confidential: Unauthorized disclosure, copying and distribution are prohibited

Metro Infrasys Pvt. Ltd.

Parking Management System

BAR CODE READER ..............................................................................................................54

BOOM BARRIER ....................................................................................................................56

HANDHELD DEVICE ..............................................................................................................59

Confidential: Unauthorized disclosure, copying and distribution are prohibited

Metro Infrasys Pvt. Ltd.

Parking Management System

1.1 Document Purpose and Content

Confidential: Unauthorized disclosure, copying and distribution are prohibited

Metro Infrasys Pvt. Ltd.

Parking Management System

1.2 List of Abbreviations

Central Control Unit

Central Processing Unit

Frequently Asked Questions

Management Information System

Parking Management system

Radio Frequency Identification

Request for Proposal

Uninterruptible Power Supply

Confidential: Unauthorized disclosure, copying and distribution are prohibited

Metro Infrasys Pvt. Ltd.

Parking Management System

Central Control Room

Confidential: Unauthorized disclosure, copying and distribution are prohibited

Metro Infrasys Pvt. Ltd.

Parking Management System

It is emerging as a Leading Indian company in the field of Intelligent Transportation Systems by

Confidential: Unauthorized disclosure, copying and distribution are prohibited

Metro Infrasys Pvt. Ltd.

Parking Management System

2.1 Roles and Responsibilities

Confidential: Unauthorized disclosure, copying and distribution are prohibited

Metro Infrasys Pvt. Ltd.

Parking Management System

3.1 System Architecture

Figure 1- System Architecture