ANNEXURE-1

Specification for Hand Held Device (Simputer), to be used for Field Transactions by the
Traffic Police Officers, for challans and other services related with Smart Card based
Driving License and Vehicle Registration Certificate (RC).
1. CPU Minimum speed 200 MHz or higher
2. RAM Minimum 32 MB or higher
3. Permanent Storage Minimum 32 MB (Flash or otherwise)
4. General Features Real Time Clock, Power Management/Power save option.
5. Display 240x320 Monochrome LCD based tough screen, Contrast level should b
such that the text is visible in broad day light.
Note: - Cost of TFT LCD display in lieu of Monochrome should be additional
quoted.
6. Input Device Tough Panel Overlay on LCD display used with plastic stylus (pen).
7. Smart Card Readers Two in-built, PC/SC and ISO-7816 compliant Smart Card Readers. Mu
support 3 V contact chip card with T=0 and T=1 protocol.
8. Printer Support Impact Printer must be supported by the device through the serial port.
Note: - Thermal Printer must be quoted as add-on in lieu of Impact Printer
9. USB Version 1.1. interfaces
USB Slave for PC connection, USB Master for other connectivity.
10. Power on/off Switch and automated sleep mode in case of inactivity.
11. Battery pack Rechargeable, Removable batteries with 8 hours on time and 7 days stand b
time on sleep mode.
12. Connectivity Following connectivity features must be supported along with appropriat
API’s and quoted separately as add-on for the device:
GPRS, GPS, GSM, CDMA, PSTN (External Dial-up modem on serial port
TCP/IP, Infrared/Blue Tooth.
13. Operating System Device must be operated through Open Source Operating System
Linux (Kernel version 2.6.x or above) with appropriate GUI/Graphica
Toolkit/X-Windows GUI environment support on the above describe
LCD display)
14. Development Platform
Java (J2ME) run time, C++ and all necessary API’s and Libraries fo
Support application development alongwith necessary API’s/libraries for all add o
integration.
15. Smart Card Reader
PC/SC API or similar (Like PC/SC Lite from MUSCLE)
Programming Interface
16. Bio-Metric/Finger Device
Print must support Finger Print capture and verification system as add
Verification alongwith appropriate API’s Devices for capture of raw image, Registratio
and Verification of Finger Prints and 1:1 matching.
Note: - However, this system should be quoted as add-on.
17. Warranty On site 36 months, from the date of successful installation/commissioning,
all respect.
 ANNEXURE-2

DELHI TRAFFIC POLICE

Software specifications
For
Prosecution (all types of Challans) and
Accident Reporting

The purpose of the proposed application software based on simputers is to provide the Traffic
Police the ability to do the following:
1. Collection of information by the field staff
2. Collection of information at all the traffic circle office
3. Collection of information of 3 Notice branches
4. Collection of information about all accidents in prescribed format
5. Integrate the collected information in centralized database
6. Access & retrieve information under various categories and access levels
7. Generation of statistical, analysis and comparison reports

Background

There are two enforcement Agencies in Delhi for Regulation, Monitoring and Enforcing of
provisions of Motor Vehicle Act and Rules framed there under.

1. Enforcement wing of Transport Department.

2. Traffic Police under the Delhi Police.

The process has been described only with regards to Delhi Traffic Police. Challaning is the
process of prosecution by enforcement agencies for and under Motor Vehicle Act.

Challan is a document prepared by the enforcement agency for prosecution of an offence under
Motor Vehicle Act.

Impounding of vehicle is to retain by the enforcement agencies for an offence committed under
Motor Vehicle Act. Impound vehicle is released after the payment of challan fees.

Compounding of challans under M.V.Act means settlement between the enforcement agencies
and the offender by which challan is disposed of through depositing of notified fee by the
offender.
Enforcement agencies deploy its team for regulating, monitoring, enforcing the Motor Vehicle
Act.

A violator may be stopped by one of these teams and may asked to produce the following
documents in original.

1. Driving licence
2. Registration book of vehicle
3. Insurance certificate
4. Pollution under control certificate
5. Permits ( for commercial vehicles only)
6. Certificate of fitness ( for commercial vehicles only)
7. Road Tax Receipt (for commercial vehicles only)

If the violator is not carrying the above documents or found violating any of the Traffic
Rules/Regulations, the violator may by challaned.

The violator’s document and even vehicle may also be impounded depending on the violation
under rules of MV Act 1988, CMVR 1999 and DMV Rule 1993.

Functioning

Delhi Traffic Police issues challans for people who violate the traffic rules. The violators
have the choice of either compound their challans by paying the prescribed fine on the spot
or go to the court at the prescribed date and time.

In both the case the procedure is mentioned below:

1. Compounded challans – Prescribed fine amount as per law is paid at the spot
against a receipt (only certain offences can be compounded as per law)
2. Court challans – For disposal in the court the violator has to appear in the court on
the date and place mentioned the challan. The case is heard by the court depending
upon whether he pleads guilty of not.
If he/she pleads guilty, the court may impose penalty on the facts and circumstances
of the case. If he does not plead guilty he may be asked by the court to submit the
ground/documents on the basis of which he does not plead guilty. After hearing the
violator and the challaning officer, the court will decide the case. All the documents
are released from the court after disposition of the case.

Many violators are also booked through the Notices for violations sent by Post Office by the
Notice branch. Notices can be filled by all Ranks including Gazetted officers of Delhi Police
even if they are posted in Units other than Traffic Unit. The Traffic Police has a
comprehensive system of data collection and computerization in relation to the back office
work related to the Notice generation system.

There is automatic Notice generation from the slips filled in by all ranks in the field for which
the Standing Operating Procedures in 3 parts have been mentioned below.

B SOP - 01
1. Violation Slips are received from TI Circles in the computer section.
 1.1 Violation Slips from GOs and Complaints Cards are received by Notice Branch.
Entries are made in Register and are forwarded to the Computer Section for data
entry.
1.2 E-mail and SMS (for TSR) are received by Computer Section.
2. After receiving the above documents, these are scrutinized based on the
following criteria:
a) Violation is correct or not,
b) Registration No.
c) Time of violation
3. Incorrect violation slips are returned to the TI circles.
OK slips are scanned & edited using ‘TeleForm’ and text file is generated.
Notice No. is generated in the form of : X/NB(T), dt. DD/MM/YYYY, where ‘X’ is
the running number given by the software. The same is noted down in a ‘Control
Register” for reference.
4. The text file is uploaded to the server using FTP and ownership details are linked
for each vehicle from the vehicle ownership database residing in the server.
5. A master file namely ‘V_mast’ is used to generate offence details, section of law
and compounding amount.
6. Process the print file of the notices.
7. Print the notices for violation (Duplicate copies) as per the print file on pre-printed
stationery through a line printer.
7.1 The instructions for the violator are pre-printed on the back side of the notices
stationery.
8. Send the notices to the notice Branch where carbon copy of the computer
printout is separated.
9. The original copy is put in an envelope and duplicate copy is removed and
retained for record in the notice branch.
10. Send the original copy of notices along with the envelopes and their summary
through a Road Certificate to the post office for dispatch.
11. Acknowledgement given by the post office is kept in the Notice Branch for record
purposes.
C SOP - 02

1. If the Traffic rules violators are willing to pay the compounding amount, they or their
representative come to the compounding amount collection center(s) mentioned on the
backside of the Notice.
1.1 The amount can be either paid in cash at the designated counters or by cheque/draft
through Cheque Depository Machines.
2.1 For deposition by Cash, the information about the driver of the vehicle at the time of
violation is given by the person who has come for deposition of the compounding
amount.
2.2 Based on this information the compounding challan is prepared in the name of violator
by the counter clerk and signature of violator is taken on the challan. Copy of the
challan along with receipt of the compounding amount is given to the violator.
3. For deposition by Cheque/draft, the menu driven touch screen kiosk helps the user to
deposit the cheque or draft against individual violation slips. The transaction through
Cheques/drafts is subject to their realization.
4. The data from each center is uploaded to the server using FTP.
5. The cash as well as cheques/drafts from respective centers are sent to the Accounts
Branch along with their statements on a daily basis.
6. Account Branch deposits the cheque(s) along with the summary to the State Bank of
India in the PHQ.
7. Bounced/returned cheques are given back to the Notice Branch by the Accounts Branch.
7.1 Notice Branch writes to the traffic violator advising him/her to pay a valid cheque or pay
cash.

D SOP - 03

1. Court notice is issued in case either the violator does not report to Notice Branch for any
discrepancy in his/her notice or fails to deposit the compounding amount within 5 months
of issue of notice.
2. Such cases are called pending cases for which the following proceedings are
undertaken on a regular basis at least once in a week.
3. A Court Notice is prepared for each pending case and the same is printed in duplicate
on pre-printed stationery through a line printer.
4. Each of these Court Notices has a running number given by the software. The same is
noted down in a ‘Control Register” for reference.
5. Send the notices to the notice Branch where carbon copy of the computer printout is
separated.
6. The original copy of the Court Notice is separated and the corresponding office copy of
the notice U/S 133 Motor Vehicles Act, sent earlier to the violator is attached with it.
7. Send these papers to any of the traffic courts according to the jurisdiction as per place of
violation through the post office.
8. The data corresponding to these Court Notices is also sent electronically (in floppy)
regularly on a fortnight basis to the selected Traffic courts which have the facility of
computers.

For the clarity of operation the administrative hierarchy and existing as well as proposed
workflow is given below:

Administrative setup

1. In the administrative set-up there is one Joint CP, 1 Addl CP, 5 DCsP, 15 AcsP and
other ranks.
2. For the purpose of prosecution and other similar activities the Setup includes 3 Ranges
each headed by a DCP, 9 districts each headed by an ACP (3 ACsP under 1 DCP), 38
Circles each headed by a Traffic Inspector (3-6 TI s under each ACP)
3. There are 12-15 ZOs in each circle. ZOs are the SI or ASI
4. Only ZOs or above ranking officers can issue a compounding or a court challan else
notices are generated from the information collected from the field.
5. Teen Murti Office under ACP/Computer has backend systems responsible for compiling
statistical reports of Prosecution data after obtaining the inputs from the circles.
Besides, accident data is also compiled at the Computer Center.

Requirement of the software

Various components which are required to be considered for giving the various interfaces for
all the users are as follows:
 1. Compounded (Cash) Challans (Format is given at Annexure-A)
2. Court Challans(Format is given at Annexure-B)
3. Notices u/s 133 MVA(Format is given at Annexure-C)
4. Accident Input Forms (Format is given at Annexure-D)
5. Statistical reports, analysis and comparison reports
6. Permanent records

The various databases maintained at the backend will include:

a. Database on violations.
b. Database on vehicle ownership.
c. Database on code files (vehicle type, offence, colour, make, location, area of
jurisdiction).
d. Database on Driver Licences.
e. Databases on Stage Carriage Permits, Bus queue shelters and Stage Carriage
routes.

1. Compounded (Cash) Challans

At present manual entries are made in duplicate at the spot as per the proforma
attached at Annexure-A. One copy is given to the violator which act as a receipt for the
compounding amount taken in cash at the spot.

2. Court Challans
At present manual entries are made in triplicate at the spot as per the proforma attached
at Annexure-B. One copy is given to the violator, one sent to the court along with
document seized and retained in the office

3. Various registers are maintained in each circle as well as ACP office based on the
information of Cash and Court Challans.
1. Existing workflow for Court and Cash Challan at Site:

Spotting & stopping the offending vehicle

Checking the license, Regn No. and other papers of the vehicle

Noting down the report of the vehicle and the offences manually

Compounding Court challan in Send the report to Circle

challan at the spot certain offences or on daily basis
when the violator
does not pay at the
spot
Data analysis
The court decides
and the violator
complies with the
orders
Summary report

Figure 1.0 Existing workflow for cash/court challans

2. Issuing Challan Notice from the Notice Branch (If the vehicle cannot be stopped):

Spot the offending vehicle

Collecting the report of the vehicle and the offence in a Coded

Format from the field in the form of data sheets

Sending the data sheets to Notice Branch on daily basis

Data feeding in computer according to the report coming

from site + Manual Check

Sort Notices mentioning the amount and date of fine

Taking the printout of the notice

Sending the notice to the vehicle owner

If the violator
Fine paid at stipulated locationhas failed top pay fine
within a particular time period

Sending copies of the notices to court & to vehicle owner

Figure
Court 2.0 Existing
decides and thework flow complies
violator for Noticewith
generations
the orders
Note:-

1. All shaded/coloured boxes relate to Simputer based work items.

Essential features of the software: - Application software for following Applications:-

1. Compounding Challans
2. Court Challans
3. Notice U/S 133 MV Act, when defaulting vehicle could not be stopped ( Constables to
Gazetted Officers)
4. Road Accident Reporting and input Forms
5. Capture of Fingerprint for major offences like Drunken Driving, Dangerous Driving and
Unidentified Victims of road traffic accidents.
6. Direct download/upload of data to/from the Server at Circle Office.
7. All the data exchange one at circle and another from circle to the central database at
Teen Murti Traffic Office.
8. There should be scalability for on-line payments by Credit Cards.
9. Verification of Smart Card based Driving License and Registration Card and retrieval of
MRZ data for from these cards for display on the monitor.
10. Performing the operations as described in points 1, 2 and 3 above on Smart Card based
Driving License and RC Card.
11. Software for Smart Card reader/writer for Driving license and Registration Certificate
(RC) of the vehicle will be provided by the NIC, which needs to be integrated with the
software being developed by the vendor.

It should be Based on/ supported by open source.

The Applications as mentioned from 1 to 8 above shall be developed by the successful
vendor based on the specification /Functional requirements approved by the department
(Delhi Traffic Police).

The Applications mentioned in 9 to 11 above shall be developed in collaboration with
NIC, Delhi Traffic Police, for which vendor shall depute expert developers for three man
months at NIC Smart Card Lab, apart from providing all technical inputs/training for
Application Development on the device.

All the source codes and IPR of these software shall be the property of Delhi Police and
NIC.

Cost should be inclusive of all necessary accessories viz. Cables, Connectors, Batteries,
Charges, Stationary, Ribbons etc. etc.

Vendor should also quote the costs of all consumables required subsequently in long
run.
 PROFORMA FOR PRICE SCHEDULE
(To be enclosed with commercial bid)

Tender No. _________General-II(Traffic), dated _____________

Date of opening __________ Time__________/hours

We___________________________________________________________________
__ hereby certify that we are established manufacturers/authorized representatives of
M/S__________________ ___________________________________________________ with
factories at______________________ which are fitted with modern equipment and where
production methods, quality control and testing of all materials manufactured or used by us are
open to inspection by the representative of the purchaser. We hereby offer to supply the
following items at the prices indicated below :

Description Qty.of Unit Price

Sl. No. Extended
in Sales
Price Tax
Other
in Govt.
Incidental Total Price FOR
work/item Indian in India Rupees
Indian levies, if anycharges,
(To ifDestination
any in
Rupees Rupees be specified) (To Indian
be Rupees
specified)
b d E f g h I
1.Simputer

Application
Software

It is hereby certified that we have understood all the terms & conditions specified in the
tender document and are thoroughly aware of the nature of job required to be done and
stores/items to be sullied. We agree to abide by all the tender terms and conditions.

We hereby offer to carry out the job and (or) duly the store/items detailed above or such
portion(s) thereof as you specify in the notification of award.

Signature and seal of Bidder

Dated:-
 BIDDER’S PARTICULARS

1. NAME OF THE FIRM :__________________________________

2. CORRESPONDANCE ADDRESS
WITH TELEPONE & FAX NO. : _____________________________

3. LOCAL ADDRESS WITH TELEPHONE :_______________________________

4. NAME & ADDRESS OF THE MANUFACTURER_________________________

5. WHETHER REGISTERED WITH NSIC/

DGS&D, IF YES ATTACH COPY : _______________________________

6. EXCISE/CUSTOM DUTY CERTIFICATE:_____________________________

7. VAT REGISTRATION PROOFWITH TIN NO. __________________________

8. LATEST SALES TAX CLEARANCE CERTIFICATE ____________________

9. ISO 9000 YEAR 2000 CERTIFICATE _______________________________

10. WHETHER AGREED TO ORGANISE DEMO OF THE EQUIPMENT_________

11. COPY OF AUTHORISED DISTRIBUTOR/

DEALERSHIP CERTIFICATE : _______________________________

12. TECHNICAL SPECIFICATIONS OF THE

SYSTEM ALONGWITH LITERATURE/BROCHURE _____________________

13. PROOF OF PAST PERFORMANCE,IF ANY __________________________

14. APPLICATION FEE : __________________________________

15. BID SECURITY/EMD MONEY DETAIL : _______________________________

16. COPY OF INSTRUCTIONS AND

CONDITIONS DULY SIGNED : __________________________________

17. ANY CONDITION OF THE BIDDER ________________________________

SIGNATURES OF THE TENDERER WITH STAMP

 CHECK LIST

(TO BE ATTACHED WITH THE TECHNICAL BID)

1. NAME OF THE FIRM

2. CORRESPONDENCE ADDRESS WITH TELEPHONE

AND FAX NO.

3. LOCAL ADDRESS WITH TELEPHONE AND FAX NO.

4. WEHTHER REGISTERED WITH NSIC, IF YES,

ATTACH COPY

6. EARNEST MONEY Rs. 50,000/- IN FORM OF BANK

DRAFT

7. SALES TAX /VAT REGISTRATION CERTIFICATE

8. CURRENT/LATEST SALES TAX CLEARANCE

CERTIFICATE.
9. EXCISE DUTY CERTIFICATE

10. LIST OF OWNERS/PARTNERS

11. WHETHER MANUFACTURER, IF YES,

ATTACH COPY
13. WHETHER YOU AGREE TO SUBMIT ADVANCE
SAMPLE OF MAIN SUPPLY WITHIN 15 DAYS AFTER
OPENING OF THE COMMERCIAL/ PRICE BID.
14. A CERTIFICATE TO THE EFFECT THAT THEY HAVE
NOT BEEN BLACK LISTED BY ANY DEPARTMENT
AND THAT NO CRIMINAL CASE/COMPLAINT IS
PENDING AGAINST THEM.
15. HAS THE QUOTED THE RATES AS PER TENDERED
TECHNICAL SPECIFICATIONS.
16. PROOF OF PAST PERFORMANCE (IF ANY)

17. COPY OF TERMS AND CONDITION DULY SIGNED

18. ANY OTHER CONDITION, SPECIFY WITH DETAILS

SIGNATURE OF THE TENDERER WITH STAMP