CCTNS TN RFP Vol I Police NCRB

E-GOVERNANCE MISSION MODE PROJECT (MMP)
CRIME & CRIMINAL TRACKING NETWORK AND SYSTEMS

(CCTNS)
REQUEST FOR PROPOSAL FOR
SELECTION OF SYSTEM INTEGRATOR
FOR
IMPLEMENTATION OF CCTNS
IN
TAMIL NADU
VOLUME – I: TECHNO-FUNCTIONAL
REQUIREMENTS
RELEASED BY
TAMIL NADU POLICE
GOVERNMENT OF TAMIL NADU

E-Governance Mission Mode Project: Crime & Criminal Tracking Network and Systems
Table of Contents
1. Request for Proposal Datasheet ................................................................................... 8
2. Introduction ..................................................................................................................... 9
2.1 Project Background................................................................................................. 9
2.2 Background of Police Systems in India ................................................................ 9
2.2.1 Crime and Criminals Information System (CCIS) ........................................... 10
2.2.2 Crime Analysis and Automated Record Update System (CAARUS) ............ 10
2.2.3 Common Integrated Police Application (CIPA) .............................................. 11
2.2.4 Crime and Criminal Tracking Network System (CCTNS)............................... 12
2.3 CCTNS Implementation Framework .................................................................... 13
2.3.1 Goals of this Request for Proposal (RFP) ....................................................... 13
3. Project Overview ........................................................................................................... 15
3.1 Need for the Project............................................................................................... 15
3.2 Vision and Objectives of Project.......................................................................... 15
3.3 Stakeholders of Project ........................................................................................ 16
4. State Police Department............................................................................................... 19
4.1 Organization Structure .......................................................................................... 19
4.2 Existing Legacy Systems ..................................................................................... 23
4.3 Existing Data Center Infrastructure ..................................................................... 23
4.4 Existing WAN Infrastructure ................................................................................. 24
4.5 Existing Client Site Infrastructure........................................................................ 25
4.6 Existing Capacity Building Infrastructure (DTCs/ RTCs/ PTCs/ Police
Academies) ........................................................................................................................ 26
4.7 Core Application Software (CAS)......................................................................... 26
4.8 CAS (Center) .......................................................................................................... 27
4.9 CAS (State) ............................................................................................................. 28
4.10 Development of CCTNS Core Application Software (CAS) ........................... 31
4.11 Technology Stack for CAS (State) ................................................................... 31
5. Role of NIC in supporting CAS .................................................................................... 32
6. Scope of the Project ..................................................................................................... 35
6.1 Geographical Scope .............................................................................................. 35
6.2 Functional Scope ................................................................................................... 52
6.2.1 CCTNS Functional Modules ............................................................................. 53
6.2.2 Solution & Technology Architecture ............................................................... 59
6.3 Scope of Services during Implementation Phase .............................................. 62
6.3.1 Project Planning and Management .................................................................. 63
6.3.2 Configuration, Customization, and Extension (New Modules) of CAS (State)
…………………………………………………………… …………………………………………………………………..66
………………………
6.4 Infrastructure at the District Training Centers ................................................... 70

6.5 Site Preparation at Police Stations and Higher Offices ..................................... 71
6.6 Infrastructure at the Client Side Locations ......................................................... 71
6.7 Network Connectivity for PS & Higher Offices ................................................... 72
6.8 IT Infrastructure at the Data center and Disaster Recovery Center ................. 72
6.9 Data Digitization & Data Migration ....................................................................... 74
6.10 Migration of Data from CIPA and CCIS to CAS (State) .................................. 80
6.11 Capacity Building .............................................................................................. 80
6.12 Handholding Support ........................................................................................ 93
6.13 Requirement on Adherence to Standards....................................................... 93
6.14 Support to Acceptance Testing, Audit and Certification............................... 94
6.15 Scope of Services during Post-Implementation Phase ................................. 97
Government of Tamil Nadu Request for Proposal for Selection of System Integrator 2 of 302
6.16 Go-Live ............................................................................................................... 97

6.17 Handover and Exit Management ...................................................................... 97
7 Implementation and Roll-out Plan ........................................................................... 99
ANNEXURE I Governance Structure (State Level) ............................................... 105
ANNEXURE II Details of Technology Stacks - CAS (State) and CAS
(Center)……….………….......... ....................................................................................................... 110
ANNEXURE III Bill of Quantity – Client Site Locations ........................................ 113
ANNEXURE IV Bill of Quantity – Additional Locations ....................................... 142
ANNEXURE V Post Implementation Support Services........................................ 157
ANNEXURE VI Service Levels ................................................................................ 162
ANNEXURE VII Network Connectivity Solution ................................................... 182
ANNEXURE VIII Indicative Technical Specifications .......................................... 185
ANNEXURE IX Existing IT Infrastructure .............................................................. 222
ANNEXURE X Training Institutions Infrastructure ............................................... 226
ANNEXURE XI Geographical Coverage ................................................................ 228
ANNEXURE XII Functional Requirements Specifications................................... 276
ANNEXURE XIII Non-Functional Requirements Specifications ......................... 299
LIST OF ABBREVIATIONS
S. No Abbreviations Expanded
1 ACOP Additional Commissioner of Police
2 ACP Assistant Commissioner of Police
3 ADoC Anti Dowry Cell
4 ADC Additional Deputy Commissioner
5 ADGP Additional Director General of Police
6 ADSP Additional Superintendent of Police
7 AFIS Automatic Fingerprint Identification System
8 AP Armed Police
9 ARF Accident Record Form
10 AVS Anti Vice Squad
11 C&O Crime & Occurrences
12 CAARUS Crime Analysis and Automated Record Update System
13 CADB Crime Attributes Database
14 CAS Core Application Software
15 CB Crime Branch
16 CCIS Crime and Criminal Information System
17 CCIW Commercial Crime Investigation Wing
18 CCRB City Crime Record Bureau
19 CCTNS Crime and Criminal Tracking and Networking System
20 CID Criminal Investigation Department
21 CIPA Common Integrated Police Application
22 CMS Case Monitoring System
23 CSCID Civil Supplies Criminal Investigation Department
24 CSG Coastal Security Group
25 CSR Community Service Register
26 DC Deputy Commissioner of Police
27 DCB/CCB District Crime Branch
28 CCB City Crime Branch
29 DCRB District Crime Record Bureau
30 DGP Director General of Police
31 DIG Deputy Inspector General of Police
32 DIO District Informatics Officer
33 DMT District Mission Team
34 DSB District Special Branch
35 DSP Deputy Superintendent of Police
36 ELCOT Electronics Corporation of Tamilnadu
37 EOW Economic Offences Wing
38 FACTS Fingerprint Analysis and Crime Tracing System
39 FIR First Information Report
40 FOSS Free and Open Source Solution
41 GD General Diary
42 GIS Geographical Information System
43 GRP Government Railway Police
44 HG Home Guards
45 HIPS Host-based Intrusion Prevention System
46 ICT Information and Communication Technology
47 IGP Inspector General of Police
48 IO Investigating Officer
49 IPS Intrusion Prevention System
50 IRC Indian Road Congress
51 IVRS Integrated Voice Response System
52 JAPU Juvenile Aid Police Unit
53 JC Joint Commissioner of Police
54 LAN Local Area Network
55 MFD Multi Functional Device
56 MHA Ministry of Home Affairs
57 MOB Modus Operandi Bureau
58 MVCS Motor Vehicle Coordination System
59 NCR Non Cognizance Report
60 NCRB National Crime Record Bureau
61 NIC National Informatics Centre
62 NOC No Objection Certificate
63 OCIU Organized Crime and Intelligence Unit
64 PCCC Police Computer Communication Centre
65 PCR Protection of Civil Rights
66 PCW Police Computer Wing
67 PEW Prohibition and Enforcement Wing
68 PS Police Station
69 PSR Prisoner’s Search Register
70 PT Pending Trial
71 PTB Police Telecommunication Branch
72 PTC Police Training College
73 RADMS Road Accident Data Management System
74 RTO Regional Transport Office
75 SB Special Branch
76 SB CID Special Branch Criminal Investigation Department
77 SD CID Special Division Criminal Investigation Department
78 SDA State Designated Agency
79 SDD Software Design Document
80 SDFPB Single Digit Finger Print Bureau
81 SDM Sub Divisional Magistrate
82 SDPO Sub-Divisional Police Office
83 SHO Station House Officer
84 SI Sub Inspector
85 SI System Integrator
86 SIO State Informatics Officer
87 SJ & HR Social Justice and Human Rights
88 SLA Service Level Agreement
89 SMT State Mission Team
90 SP Superintendent of Police
91 SPMC State Programme Management Consultant
92 SPMU State Project Monitoring Unit
93 SRS Software Requirement Specification
94 STF Special Task Force
95 STPC State Traffic Planning Cell
96 SWAN State Wide Area Network
97 TEW Traffic Enforcement Wing
98 TIW Traffic Investigation Wing
99 TNCF Tamil Nadu Commando Force
100 TNFPB Tamilnadu Fingerprint Bureau
101 TNPA Tamilnadu Police Academy
102 TNPHC Tamilnadu Police Housing Corporation
103 TNSDC Tamil Nadu State Data Centre
104 TS Technical Services
105 UI Under Investigation
106 UT Union Territory
107 VPN Virtual Private Network
108 WAN Wide Area Network
1. Request for Proposal Datasheet
S. No Information Details
1. RFP reference No and Date C.No.

20/SCRB/CCTNS/2011
Dated 6th June 2011
2 EMD Rupees Three Crores Only
3. Date of pre-bid conference 17th June 2011 – Time to be

informed later
4. Last date for submission of written queries for 13th June 2011
clarification
5. Release of response to clarifications 21st June 2011
6. Last date (deadline) for receipt of 6th July 2011 - 3:00 PM

proposals in response to RFP notice
7. Place, Time and Date of opening of Technical 12th July 2011 – Time to be
informed later
proposals received in response to the RFP
notice
8. Place, Time and Date of opening of Financial 25th July 2011 – Time to be
informed later
proposals received in response to the RFP
notice
9. Contact Person for queries Additional Director General

of Police, State Crime
Records Bureau, Tamil
Nadu Police
10 Addressee and Address at which proposal in Additional Director General
of Police
response to RFP notice is to be submitted:
State Crime Records
Bureau (SCRB)
No. 95, Raja Annamalai
Puram
Chennai-600028
Tel: 044-24958585
Email: cctns@tn.gov.in
2. Introduction
2.1 Project Background
Availability of relevant and Timely information is of utmost necessity in conduct of business

by Police, particularly in investigation of crime and in tracking & detection of criminals. Police
organizations everywhere have been handling large amounts of information and huge volume
of records pertaining to crime and criminals. Information Technology (IT) can play a very vital
role in improving outcomes in the areas of Crime Investigation and Criminals Detection and
other functioning of the Police organizations, by facilitating easy recording, retrieval, analysis
and sharing of the pile of Information. Quick and timely information availability about different
facets of Police functions to the right functionaries can bring in a sea change both in Crime &
Criminals handling and related Operations, as well as administrative processes.
Creation and maintenance of databases on Crime & Criminals in digital form for sharing by all
the stakeholders in the system is therefore very essential in order to effectively meet the
challenges of Crime Control and maintenance of public order. In order to achieve this, all the
States should meet a common minimum threshold in the use of IT, especially for crime &
criminals related functions.
CCTNS will cover all the Police Stations in the States/UTs, and also the Sub-Divisions,
District headquarters, Range headquarters, Zonal IG offices and State headquarters.
Necessary Hardware will be provided at all these locations including data centers at State
and National headquarters. All these locations will be networked by providing appropriate
high-speed connectivity for data transfer and sharing of information amongst various
stakeholders.
Additional information can be found on NCRB website (http://ncrb.nic.in)
2.2 Background of Police Systems in India
Several initiatives have been introduced in the past to leverage IT in police functioning. Some
of these initiatives include centrally initiated programs such as the NCRB-led CCIS (Crime
and Criminals Information System) and CIPA (Common Integrated Police Application), and
several state-led initiatives such as CAARUS in Tamil Nadu.
Presently automation in the area of Civil Police is addressed mainly through the two GOI-led
initiatives – CCIS and CIPA – and in Tamil Nadu through State-led initiative, CAARUS.
This section explores the details of the two GOI-led initiatives and State Specific Application
CAARUS.
2.2.1 Crime and Criminals Information System (CCIS)
CCIS is an NCRB-driven program and has been launched in 1990. Since then, it has been
implemented in 35 states and union territories and spans over 700 locations. Most of the
state police headquarters and district headquarters are covered by CCIS and so are some of
the 14,000+ police stations in the country.
CCIS is primarily an initiative to create crime- and criminals-related database that can be
used for crime monitoring by monitoring agencies such as National Crime Records Bureau
(NCRB), State Crime Records Bureaus (SCRBx) and District Crime Records Bureaus
(DCRBx) and to facilitate statistical analysis of crime and criminals related information with
the States and monitoring agencies. In Tamil Nadu, CCIS and computers were provided to
SCRB and 37 DCRBx in 1996. The CCIS database of all state records is maintained at
present in SCRB.
CCIS data is used for publishing online reports such as Missing Persons report and is also
used as the basis for online query facilities that are available through the NCRB website. In
addition, it is also used by NCRB to publish an annual nation-wide Crime Report. CCIS
focuses exclusively in Crime and Criminals information and does not address the other
aspects of Police functioning.
CCIS was originally built on Unix OS and Ingres database, but has since been ported to
Windows platform and has released its last three versions on Windows (the last release
having taken place in September 2002).
2.2.2 Crime Analysis and Automated Record Update System (CAARUS)
This initiative was aimed at computerizing all manual police station records. It was developed
by the state police department and rolled out in 2006 and as part of this rollout all police
stations were provided with a computer. The various modules available in CAARUS
application are (I) Staff Management, (II) Case Registration, (III) Case Progress & Disposal
(IV) Station Data Bank and (V) Receipts.
Administrative data and data relating to crime in a police station were captured in CAARUS,
and periodicals and returns generated thereafter. Essentially, this was also a standalone
system which contained only data local to a police station with an additional feature to upload
data to Central server at SCRB at the end of a day.
CAARUS Stand-alone is built on client-server architecture on a Windows platform using

Visual Basic and MS Access database. The patch to upload data from stations to central
server at the end of day is developed in .NET
Benefits realized from CAARUS include the ability to enter registration (FIR) details into the
system and print out copies in format similar to manual records, instant generation of
abstracts and reviews and easier search of criminals using part strings, etc.
2.2.3 Common Integrated Police Application (CIPA)
A feature common to most of the early efforts has been a predominant focus on collection of
data as required by the monitoring agencies and on specific functions such as records
management, statistical analysis and office automation; rather than on police stations, which
are the primary sources of crime- and criminals-related data generation.
In order to provide an application that supports police station operations and the investigation
process, and that is common across all states and union territories, MHA had conceptualized
the Common Integrated Police Application (CIPA) in 2004. It has been initiated as part of the
“Modernization of State Police Forces (MPF)” scheme of the Ministry of Home Affairs. The
aim of CIPA is to bring about computerization and automation in the functioning at the police
station with a view to bringing in efficiency and transparency in various processes and
functions at the police station level and improve service delivery to the citizens. So far about
2,760 police stations, out of a total of 14,000+ police stations across the country, have been
covered under the Scheme. Specific to Tamil Nadu, Computers and software were provided
as part of CIPA to 137 Police Stations in the 6 Commissionerates in 2006.
CIPA is a stand-alone application developed to be installed in police stations and to support

the crime investigation and prosecution functions. CIPA is a centrally managed application:
an application core centrally developed and is installed in police station. Any state-specific
customizations are evaluated and made on a need basis.
The core focus of the CIPA application is the automation of police station operations. Its core
functionality includes the following modules: (i) Registration Module (ii) Investigation Module
(iii) Prosecution Module. There is also a Reporting module that addresses basic reporting
needs.
CIPA is built on client-server architecture on a NIC Linux platform using Java and
PostgreSQL database. NIC also worked on having a central repository of selected station
data in ELCOT data Centre.
Benefits realized from CIPA include the ability to enter registration (FIR) details into the
system and print out copies and the ability to create and manage police station registers on
the system, etc.
It was felt, however, that a standalone application couldn’t provide the enhanced outcomes in
the areas of Crime Investigation and Criminals Detection that are necessary. And for this
reason, MHA has decided to launch the Crime and Criminal Tracking Network System
(CCTNS) program.
2.2.4 Crime and Criminal Tracking Network System (CCTNS)
The Crime and Criminal Tracking Network Systems (CCTNS) was conceptualized by the
Ministry of Home Affairs in detailed consultation with all stakeholders and will be implemented
as a “Mission Mode Project (MMP)” and will adopt the guidelines of the National e-
Governance Plan (NeGP).
CCTNS aims at creating a comprehensive and integrated system for enhancing the efficiency
and effective policing at all levels and especially at the Police Station level through adoption
of principles of e-Governance, and creation of a nationwide networked infrastructure for
evolution of IT-enabled state of- the-art tracking system around “investigation of crime and
detection of criminals” in real time, which is a critical requirement in the context of the present
day internal security scenario.
The scope of CCTNS spans all 35 States and Union Territories and covers all Police Stations
(14,000+ in number) and all Higher Police Offices (6,000+ in number) in the country. The
CCTNS project includes vertical connectivity of police units (linking police units at various
levels within the States – police stations, district police offices, state headquarters, SCRB and
other police formations – and States, through state headquarters and SCRB, to NCRB at GOI
level) as well as horizontal connectivity, linking police functions at State and Central level to
external entities. CCTNS also provides for a citizen’s interface to provide basic services to
citizens.
There has been a strong feeling that the computer work is a burden which has to be done in
addition to normal course of work. Keeping this aspects in view, it was decided that there is a
need for expanding the functional applications, widening the territorial spread, and building in
networking capabilities in the system, both from the angle of Management Information
Systems (MIS) requirements and storage, collation, analysis and transmission/sharing of
crime and criminals related information at the police station, District, State and Central levels.
In this background, the Crime and Criminal Tracking Networking and Systems (CCTNS)
Scheme was conceived and incorporated in the Eleventh Five Year Plan.
2.3 CCTNS Implementation Framework
CCTNS would be implemented in a way where the States and UTs play a major role. CCTNS
would be implemented in alignment with the NeGP principle of “centralized planning and de-
centralized implementation”. MHA and NCRB would play a key role in planning the program
in collaboration with the Police leadership within States, in the development of a few core
components and in monitoring and reviewing the program. It is, however, the States and UTs
that would drive the planning and implementation at the State level.
The role of the Centre (MHA and NCRB) focuses primarily around planning, providing the
core application software (to be configured, customized, enhanced and deployed in States),
managing (from a high level) and monitoring the program. States would drive the
implementation at the state level and would continue to own the system after deployment.
With respect to the Core Application Software for the state, Tamil Nadu intends to position its
own software, CAARUS, as the Core Application Software (State). The state has got a
positive note from MHA to proceed with upgradation of CAARUS to a newer technological
platform. Up-scaled CAARUS would be the foundation on which configuration; customization
and state specific enhancements would be developed by the SI. Thus, in case of Tamil Nadu,
Core Application Software (State) and CAARUS would be synonymous.
The implementation of CCTNS would be taking an “integrated service delivery” approach

rather than that of procurement of hardware and software.
The central feature of CCTNS implementation at the State level is the “bundling of services”
concept. According to this, each States selects one (or a maximum of two) System
Integrators (SI) who would be the single point of contact for the State for all the components
of CCTNS. These components include the application (the changes made to the core
application provided by MHA), hardware, communications infrastructure, associated services
such as Capacity Building and Handholding, etc.
2.3.1 Goals of this Request for Proposal (RFP)
The primary goal of this RFP is to serve as a framework or a model for the RFP to be
released by States and UTs to select SI for their state through a competitive bidding process.
This volume of RFP intends to bring out all the details with respect to solution and other
requirements that are deemed necessary to share with the potential bidders. The goals of
RFP are further elaborated below:
 To seek proposals from potential bidders for providing the “bundle of services” in
implementing and managing the CCTNS solution in Tamil Nadu. The “bundle of
services” include the following:
 Configurationand deployment of CAS (State) at the state level
 Development and implementation of additional modules on top of CAS (State)
 Hardware (PCs, multi-functional devices, digital cameras, fingerprint scanners,
etc.)
 Communication infrastructure such as Network connectivity and Data Center
 Capacity Building and Handholding
 Digitization of historical records in CAARUS
 Change Management
 Provisioning of any specialized infrastructure identified by the state
 To understand from the bidders how they propose to meet the technical and
operational requirements of CCTNS.
 To ascertain how potential bidders propose to deliver the services and sustain
the demand and growth in the requirements.
 To ascertain from bidders on how they will ensure scalability and upgradeability
of the infrastructure and solution proposed to be deployed.
 To understand from the bidders as to how they intend to innovate further on this
service delivery model.
State of Tamil Nadu through CCTNS Apex Committee and Empowered Committee shall be
the final authority with respect to qualifying a bidder through this RFP. Their decision with
regard to the choice of the SI who qualifies through this RFP shall be final and the State
reserves the right to reject any or all the bids without assigning any reason. The State further
reserves the right to negotiate with the selected agency to enhance the value through this
project and to create a more amicable environment for the smooth execution of the project.
3. Project Overview
3.1 Need for the Project
The Ministry of Home Affairs has conceptualized the Crime & Criminals Tracking Network
and Systems (CCTNS) project as a Mission Mode Project under the National e-Governance
Plan (NeGP). This is an effort of the Government of India to modernize the police force
giving top priority to citizen services, information gathering, and its dissemination among
various police organizations and units across the country.
A need has been felt to adopt a holistic approach to address the requirements of the police,
mainly with relation to functions in the police station and traffic management. With a strong
focus on making police citizen friendly, there is an increasing need to strengthen the citizen
interface. Police functioning requires interaction with various departments to ensure a
process or service is brought to a conclusion. In light of this, interfaces need to be built with
external agencies such as courts, transport authorities, hospitals, and municipal authorities
etc to be able to share information between departments. Therefore, it becomes critical that
information and communication technologies are made an integral part of policing in order to
enhance the efficiency and effectiveness of the Police Department.
In order to realize the benefits of e-Governance fully, it is essential that a holistic approach is
adopted that includes re-engineering and standardizing key functions of the police and
creating a sustainable and secure mechanism for sharing critical crime information across all
Police Formations. The CCTNS has been conceptualized in response to the need for
establishing a comprehensive e-Governance system in police stations across the country.
3.2 Vision and Objectives of Project
Vision: To transform the police force into a knowledge-based force and improve the delivery
of citizen-centric services through enhancing the efficiency and effectiveness of the police
stations by creating a platform for sharing crime and criminal information across the police
stations in the country.
The overall objective of the MMP is based on enhancing the operational efficiency and
effectiveness of the police force in delivering the services.
The broad objectives of the project are as follows:

a)Improve Service Delivery to the Public
Citizens should be able to access police services through multiple, transparent, and
easily accessible channels in a citizen-friendly manner. The focus is not only to
improve the current modes of the service delivery but also provide alternate modes
such as internet/mobile for the public to communicate with the police.
b) Enhance Outcomes in Investigation
CCTNS is expected to provide the Investigating Officers with the tools, technologies
and information to facilitate faster and more accurate investigation of crime and
detection of criminals.
c)Provide Enhanced Tools for Law & Order Maintenance, Investigation, Crime
Prevention, & Traffic Management
Law & Order Maintenance, Investigation, Crime Prevention, and Traffic Management
are core components of policing work. Information technology can both enable and
improve the effectiveness and efficiency of the core activities of the police. Police
should be provided with data amenable for easier and faster analysis in order to
enable them to make better and informed decisions.
d) Increase Operational Efficiency
Police should spend more time on the public facing functions. Information technology
solutions should help in reducing the repetitive paperwork/records and making the
back-office functions more efficient.
e)Create a platform for sharing crime & criminal information across the country
There is a critical need to create a platform for sharing crime and criminal information
across police stations within and between the different states in order to increase the
effectiveness in dealing with criminals across the state borders. CCTNS is expected to
facilitate collection, storage, retrieval, analysis, transfer and sharing of data and
Information among Police Stations, Districts, State headquarters and other
organisations/agencies, including those at Government of India level.
f) Make the Police functioning citizen friendly, transparent, accountable, effective
and efficient by automating the processes and functions at the level of the
Police Stations and other police offices at various levels.
g) Improve the Police functioning in various other areas such as curbing
organised crimes, resource management, etc
h) Keep track of the progress of the crime and criminal investigation and
prosecution Cases, including progress of cases in the Courts.
3.3 Stakeholders of Project
The impact of the police subject being sensitive, a consultative and a bottom-up approach
has to be adopted in designing the MMP impacting the following stakeholders:
 Citizens/ Citizens groups

 MHA/NCRB/Others
 State Police department
 External Departments of the State
 Non-Government/Private sector organizations
The impact of the police subject being sensitive, a consultative and a bottom-up approach
has to be adopted in designing the MMP impacting the different stakeholders. An analysis of
key issues faced by different stakeholders and their expectations from the CCTNS project is
presented below.
Within the State Police Department, there are several stakeholders involved in this project. It
includes lower level officials at police stations for whom the key issues faced are reduced
operational efficiency due to duplicate entry of records in both software and in manual
registers. Also, IT support and maintenance of the computers is a major issue plaguing the
field level personnel. The higher level officials are more interested in knowing about status of
entry in software, receiving the abstracts and returns regularly. They are of the firm opinion
that the data entry consumes most of the time of the field level personnel which could
instead be used to do their core job more efficiently. The higher officials have expressed
interest in devices which would aid in police performing their core functions better.
The citizens expect the system to help reduce multiple visits to police premises to push their
application for further processing or for providing an easy option to know the status of their
complaints. The agencies/departments which regularly link up with police are more
interested in sharing data and assistance in tracking applications that cut across
departments. The MHA and NCRB as nodal agency are interested in sharing of intelligence
and data across states and ease of collecting nation wide crime data in a standardized
manner.
The following are the expected benefits envisaged from successful implementation of the
MMP by various stakeholders
Benefits to Citizens
i) Multiple channels to access services from police
ii) Simplified process for registering and tracking incidents, petitions and FIRs
iii) Simplified process for accessing general services such as requests for
certificates, verifications, and permissions
iv) Simplified process for registering grievances against police
v) Simplified process for tracking the progress of the case during trials
vi) Simplified access to view/report unclaimed/recovered vehicles and property
vii) Improved relationship management for victims and witnesses
viii) Ability to view and pay pending traffic challans from multiple access points
ix) Faster and assured response from police to any emergency calls for
assistance
Benefits to Police Department
i) Enhanced tools for investigation
ii) Centralized crime and criminal information repository along with the images
of the criminals and fingerprints with advanced search capabilities
iii) Enhanced ability to analyze crime patterns, modus operandi
iv) Enhanced ability to analyze accidents and other road incidents
v) Faster turnaround time for the analysis results (crime and traffic) to reach the
officers on the field
vi) Reduced workload of the police station back-office activities such as
preparation of regular and ad-hoc reports and station records management

vii) Enhanced tools to optimize resource allocation for patrols, emergency
response, petition enquiries, and other general duties
viii) A collaborative knowledge-oriented environment where knowledge is shared
across the different regions and units
ix) Better coordination and communication with external stakeholders through
implementation of electronic information exchange systems
x) Advanced tools for traffic regulation and enforcement
Benefits to Ministry of Home Affairs (NCRB)
i) Standardized means of capturing the crime and criminal data across the
police stations in the country
ii) Faster and easier access to crime and criminal information across the
country in a manner amenable for trend and pattern analysis
iii) Enhanced ability to detect crime patterns and modus operandi across the
states and communicate to the state police departments for aiding in crime
prevention
iv) The ability to respond faster and with greater accuracy to inquiries from the
parliament, citizens and citizens groups; and to RTI queries.
Benefit to External Departments (example: Jails, Courts, Passports Office, Transport
Department, and Hospitals)
i) Seamless integration with police systems for better citizen service delivery
and improved law enforcement
4. State Police Department
4.1 Organization Structure
The Tamil Nadu Police has strength of about a lakh plus and is headed by the Director
General of Police (DGP). There are 2 other officers of the rank of DGP, 15 officers of the
rank of Additional Director General of Police (ADGP), 41 officers of the rank of Inspector
General of Police (IGP), 20 officers of the rank of Deputy Inspector General of Police (DIG),
101 officers of the rank of Superintendent of Police (SP), 103 officers of the rank of
Additional Superintendent of Police (ADSP) and a very large number of other police officers.
For the purpose of providing efficient policing and better administration, the state has been
divided into 4 zones, 12 ranges, 31 districts and 7 commissionerates. There are police
stations providing different types of services stationed at each of these districts. The Police
Station is the basic operating unit while the District Police Office is the basic unit from the
viewpoint of administration.
There are 4 officials of the rank of Director General of Police, viz., DGP (Law & Order), DGP
(Fire & Rescue Services), DGP (Police Housing) and DGP (Vigilance & Anti-corruption).
DGP (Law & Order) is the head of the State Police Department and there are ADGPs of
different units reporting to the DGP as mentioned below:
 Economic Offences Wing (EOW): This unit deals with White collared offences with
respect to Non Banking Financial Corporations (NBFCs)
 Coastal Security Guard (CSG): This unit deals with protection of state’s coastal
borders
 State Transport Planning Cell (STPC): This unit is in charge of analyses of traffic
accidents and suggesting measures for improving road safety.
 Civil Supplies Criminal Investigation Department (CBCID): This unit handles crimes
done with respect to Essential Commodities act
 Armed Police (AP): This unit deals with the deployment and maintenance of armed
police force in the state
 Administration: This unit deals with the administrative affairs of the entire state police
department
Enforcement, Training, Crime Bureau and Criminal Investigation Department (CBCID),

Welfare, Uniform Services Recruitment Board (USRB) are some of the other functional
wings that are headed by ADGP in the state Police Headquarters.
In some cases the head of a unit may be the IGP. For instance, the Technical Section (TS)
is headed by the IGP.
The Law & Order unit caters to maintenance of law & order across the state and all 1452
police stations in the state report to the ADGP, Law & Order. There are IGPs reporting to
these unit ADGPs. In the Law & Order hierarchy, the state is separated further into zones
and then into districts and commissionerates.
Each zone is headed by an officer of the rank of IGP and each range by a DIG. There are a
number of districts in a range and each district is headed by the SP who is responsible for
regularly monitoring the performance of each police station in his/her district. The SPs have
Deputy Superintendent of Police (DSP) reporting to them. The DSPs are responsible for
monitoring a limited set of stations under their control frequently. The DSP sits out of the
sub-divisional office. Apart from cases which require DSP to act as the investigating officer,
this office works more as an administrative unit collating case progress details and station
administrative records. Each police station is headed by an inspector/sub-inspector. In case
a station is headed by a sub-inspector, it is attached to another station closer geographically
where inspector heads that station. This inspector headed station in such instances
becomes the circle office. This type of set-up is rare in the state at present with most of the
police stations being headed by an inspector.
There are also 7 commissionerates and 2 railway districts in addition to the 31 districts. The
law & order hierarchy is illustrated in the figure below:
Law & Order Hierarchy in Tamil Nadu Police
From the figure we see that there are units under the control of SP and commissioner at
district and commissionerate which deal with cases pertaining to specific areas such as
Protection of Civil Rights (PCR), Prohibition & Enforcement wing (PEW), etc. There
constitute the special units serving different purposes. The list of Special Units is mentioned
below:
 Intelligence Wing
 District Special Branch
 SB CID
 SD CID
 Q Branch CID
 Security Branch, Core Cell & OCIU
 Coastal Security Group (CSG)
 Crime Branch CID
 Crime (S.I.T)
 Economic Offences Wing (EOW)
 Commercial Crime Investigation Wing (CCIW)
 Idol Wing
 Tamil Nadu Police Academy (TNPA)
 Police Training College (PTC)
 Police Recruit School (PRS)
 In-service Training Centre (ISTC)
 Armed Police (AP)
 Prohibition Enforcement Wing (PEW)
 Home Guards
 Special Task Force (STF)
 State Traffic Planning Cell (STPC)
 TN Commando Force (TNCF)
 Government Railways
 Technical Services (TS)
 Social Justice & Human Rights (SJ & HR)
 State Crime Records Bureau (SCRB)
 Forensic Science Lab (FSL)
 DCRBx/CCRBx
 District/City - Crime Branch (DCB/CCB)
 Civil Supply CID (CSCID)
 Traffic Investigation Wing (TIW)
 Traffic Enforcement Wing (TEW)
 Juvenile Aid Police Unit (JAPU)
 Anti Vice Squad (AVS)
 Anti Dowry Cell (ADC)
Unit Offices of these Special units are usually located at the district HQ and
commissionerate are under the control of the district SP and commissioner respectively. At a
functional level, they report to their headquarters in the State Headquarters. For instance,
Security Branch Criminal Investigation Department (SBCID) branch at district helps the
district SP in giving intelligence on suspicious movements or on wanted suspects. At a
functional level, they report to the Intelligence & Internal Security unit in State Headquarters,
Chennai. The various functional units in Tamil Nadu Police are illustrated in the figure below:
Functional Units of Tamil Nadu Police
DGP, TN
L&O WELFARE
CB CID AP ADMIN HQRS
SCRB INT
OPERATION ENF
EOW CS CID
TS HG
CSG STF
STPC CRIME
COP/CN SJ/HR
DGP, Training DGP, TNUSRB DGP, Police Housing
In the commissionerate setup, the ultimate authority is the Commissioner. Under the
commissioner, there are additional commissioners, joint commissioners, deputy
commissioners, assistant commissioners, inspectors, sub-inspectors and constables who
make up the hierarchical set-up in the urban police setup. With respect to rural policing SP is
the ultimate authority and under him, there are DSPs responsible for the sub-division. Each
DSP has a number of inspectors managing different police stations reporting to him. The
general hierarchical set-up in Tamil Nadu Police is shown below:
Tamil Nadu Police: General Hierarchical Set-up
4.2 Existing Legacy Systems
The State is advanced in terms of usage of software for Police Stations. There is a
reasonably good penetration of IT in terms of hardware and awareness in the Police
Stations across the state. The State Application CAARUS has been aimed at automating
Case data entry and Station Records. As on date, more than 1100 Police Stations have
been provided with CAARUS and data entry in CAARUS is being monitored on a daily basis
by the department. State proposes to use CAARUS as the core engine software for the
state. The software would be upgraded to latest technology and compliant to NCRB/MHA
specifications and then used. The state has got a provisional approval from MHA/NCRB to
use CAARUS as Core Application.
Apart from CAARUS, the state already has a host of other IT applications in place, including
MOB Software and SWIFT. The application study was done as part of the Assessment
phase and the details of IT applications were gathered from client offices including SCRB,
Technical Section and Police Stations studied during field visits.
4.3 Existing Data Center Infrastructure
ELCOT is the implementing agency for Tamil Nadu State Data Centre (TNSDC). The
proposed Data Centre near ELCOT’s Office in Perungudi has been implemented and
inaugurated by government. The Disaster Recovery Centre attached to TNSDC, to be set up
in Madurai, is expected to take another year to complete. The specifications of TNSDC are
given below:
The TNSDC Data Center Operator (DCO) would be providing the following services to
facilitate application hosting at TNSDC:
 Physical Infrastructure for hosting the CCTNS Servers

 UPS and Power back-up
 Security – Physical Security and Common Firewall
 Monitoring & Management to the extent of informing the department in the event of
server or sub-system failure
 Power, cooling & other basic infrastructure requirement
The TNSDC DCO shall also make available the SAN Switch as part of Storage
infrastructure. SAN Hardware, Tape Library, Backup & Archival would be responsibility of
the System Integrator. The system integrator (SI) who shall be selected for implementation
of the project shall be responsible for sourcing, supplying and deploying server hardware
and solution specific software; developing and installing solution. SI shall provide a Bill of
Material/ Bill of Quantity that specifies all the hardware, software and any additional
networking components of solution, both for Primary Data Center and Disaster Recovery
Data Center, in detail so as to facilitate sizing of common Data Center infrastructure such as
Racks, Storage Solution, etc. among other components.
The indicative specifications for the IT infrastructure and detailed information pertaining to
Data Centre and Disaster Recovery Centre are described in Annexure VIII.
4.4 Existing WAN Infrastructure
Tamil Nadu Police is currently having a diverse set of networks to connect its locations
across the State. They are described as below.
Zonal Connectivity
Tamil Nadu State has been divided into 5 Zones- North, Greater Chennai, Western
(Coimbatore), South (Madurai) and Central (Trichy). Chief Office Server also acts as North
Chennai Server and is located at Chief Office. From the Chief Office the Microwave Links
are connected to each Zonal Office (ZO) as well as District Police Offices (DPO) as shown
below. Lease Line between these locations act as backups for the Microwave links. In each
ZO / DPO there are various user connected on the LAN.
The Microwave Link between the HQ and the ZO / DPO is of 2mbps capacity. The Zonal
connectivity is depicted in the illustration below:
Existing WAN Infrastructure - Zonal Connectivity
Police Station Connectivity

Police Stations in the state are provided with 256kbps Broadband Connectivity from BSNL.
Around 25 police stations do not have this broadband connectivity (as mentioned in
Annexure VII) because of feasibility issues and Department has asked the Service Provider
to explore options to provide this connectivity on a priority basis.
Department has a 4 Mbps Ethernet radio link between the SCRB premises and Chief Office.
Department also has a 2mbps Connectivity at Chief Office form BSNL and a VPN cum
Firewall setup. This Setup is used by the Police Stations across the state to connect to the
Server based at SCRB. The present connectivity at police stations is shown in the illustration
below:
Existing WAN Infrastructure – HQ, SCRB and Police Station connectivity
The VPN cum Firewall Box authenticates the users connecting from Police Stations, with a
login id and password and allows them to upload the daily transactions recorded in the
CAARUS desktop application at the Police Station.
The 2 Mbps link from BSNL currently limits the number of concurrent users to 25, but a
proposal has been sent by the Department to Government of Tamil Nadu for increasing this
to 34 Mbps as a short term measure till the CCTNS Connectivity for the state is rolled out.
4.5 Existing Client Site Infrastructure
Computers were provided as part of various schemes such as CCIS, CIPA and CAARUS to
the police stations and DCRBx/CCRBx. The CCIS computers were provided as part of
software roll out in 1996. The machines are obsolete and they are not even compatible with
the recent version of CCIS such as MLE01. Similarly, the machines provided as part of
CAARUS are also obsolete in configuration and is in bad shape. Computers were provided
as part of CIPA in 2006. These computers have been provided as part of CIPA roll out in
137 police stations spread across 6 commissionerates. The details of existing client site
infrastructure at these offices are described in Annexure IX.
4.6 Existing Capacity Building Infrastructure (DTCs/ RTCs/ PTCs/ Police

Academies)
Capacity building infrastructure has been developed at all districts and commissionerates to
train personnel of various ranks. The details of Centres established at different districts for
DTCs have been described in Annexure X. Funds have been earmarked for this capacity
building infrastructure development. The funds have also been utilized for upgrading the
Capacity Building Infrastructure at SCRB. The infrastructure that has been provided to these
institutions is described in Appendix XI.
4.7 Core Application Software (CAS)
The CCTNS application software will contain a “core” for the States/ UTs that is common
across all 35 States and UTs. The CCTNS Core Application Software (henceforth referred to
as CAS) will be developed at NCRB premises and provided to States and UTs for
deployment. There would be two parts of CAS with one part containing modules specific to
NCRB. These would be referred to as CAS (Centre). There would be state specific modules
included in other part. This would be referred to as CAS (State). Each State would
customize the CAS (State) according to their unique requirements and thereafter
commission the same. States and UTs also have an option to develop and deploy additional
applications over and above the customized CAS (State). The choice of such applications
lies exclusively with the State. In case of Tamil Nadu, the state has got the approval from
Centre for using its own legacy application software CAARUS for commissioning across the
state. CAARUS is at present being upgraded by NIC to comply with standards mandated by
MHA/NCRB such as 3-tier Services Oriented Architecture based with offline mode. The
upgraded application to be called as Common Integrated Police Record Update System
(CIPRUS) would be provided to the System Integrator who would build additional
applications and customizations on top of this CIPRUS application. Thus for Tamil Nadu,
CIPRUS would be CAS (State). Henceforth, CAS (State) and CIPRUS would be used
interchangeably. There would be a need to provide interfaces to enable reading and transfer
of data from/to CIPRUS to/from CAS (Centre) modules operating at NCRB.
CAS (State) (CIPRUS in case of Tamil Nadu), in the client-server architecture would be
ready by August 2011. Development of web-enabled services of consolidated CAS (State)
data and interactive web-enabled services would be made available in August, 2012. The
services would be implemented in a phased manner as and when services are being
developed by NIC.
This section provides the details of the CAS (State) and CAS (Center) that will be developed
by the Software Development Agency at the Center. The details provided here should be
read in conjunction with the RFP and the associated addendums issued by NCRB for the
selection of the Software Development Agency for the Design, Development and
Management of CCTNS Core Application Software (CAS).
The CCTNS application software can be conceptualized as comprising different services

that fall under two broad categories, CAS (Center) and CAS (State).
4.8 CAS (Center)
CAS (Centre) would reside at NCRB and would cater to the functionality that is required at
the GOI level (by MHA and NCRB). Like CAS (State), CAS (Centre) would also be
developed by NCRB. CAS (Centre) would enable NCRB to receive crime and criminals’
related data from States/UTs in order to organize it suitably to serve NCRB’s requirements
and to provide NCRB with the analysis and reporting abilities to meet their objective as the
central level crime and criminals’ data repository of the nation. This would address the
crime- and criminals-related information needs of MHA, NCRB, the Parliament, and central
government ministries and agencies, citizens and citizen groups. CAS (Centre) also
facilitates the flow if crime and criminals information across States/UTs on a need-basis.
CAS (Centre) will be developed and deployed at NCRB. Also, CAS (Centre) is expected to
interface with external agencies such as passports, transport authorities, etc.
Overview of Services for CAS (Center)

State-SCRB-NCRB Data Transfer and Management
The service shall enable the NCRB to receive, transform, and collate the crime, criminal,
and related data from States/UTs, to organize it suitably to serve NCRB requirements.
Crime and Criminal Reports
The service shall enable authorized personnel to generate the reports and perform analysis
on the central crime, criminals, and related data repository of the nation.
Crime and Criminal Records and Query Management
The service shall enable the authorized personnel to view various registers and perform
basic and advanced queries on the central crime, criminals, and related data repository of
the nation.
Talaash Service
The service will enable the user to search for missing persons across a central/ national
database.
Person of Interest
The service will enable the user to search for persons of interest such as persons wanted on
outstanding warrants, accused, charged habitual offenders, convicts, etc. across the
national database.
Registered Vehicle and Vehicle of Interest Service
The service will enable the user to search for registered vehicles and vehicles of interest
such as, missing / stolen vehicles, abandoned / unclaimed vehicles, and vehicles involved in
traffic incidents across the national database.
Publication Service
This functionality will help the NCRB to publish the periodic crime reviews to the NCRB
portal.
NCRB Citizen Interface
The service shall enable the citizens to access/ search the NCRB National Database on the
data (ex, Stolen Vehicles / Property, Missing Persons, etc.) that is approved to be made
accessible to public.
NCRB Interface for RTI
Due to the sensitivity of the information that pertains to national security and harmony, this
service shall enable a limited and restricted access to the authorized external stakeholders
to search the NCRB National Database, upon submission of any RTI requests.
4.9 CAS (State)
CAS (State) or CIPRUS in the case of Tamil Nadu covers functionality that is central to the
goals of CCTNS and is tailored to the state of Tamil Nadu while meeting the minimum
standards mandated by Centre. It would focus primarily on functionality at police station with
special emphasis on crime investigation and criminals’ detection. This part would be
developed by NIC and provided to the Tamil Nadu Police for Implementation and Roll out.
Tamil Nadu Police would determine the requirements for configuration, customization and
enhancements / extensions. The following are the main function blocks that would comprise
CAS (State):
 Registration
 Investigation
 Prosecution
 Records Management
 Search and Basic Reporting
CAS (State) will also include the functionality required at Higher Offices such as State Police
HQ, Range Offices, District HQ, Commissionerates, Sub-division Police Offices and SCRB.
It is envisioned that CAS (State), once operational, will significantly enhance

the outcomes in core police functions at Police Stations. It will do so primarily
through its role- and event-orientation, providing role based user access and controls
and an event driven interface that helps police personnel (playing different roles)
in more effectively performing their core functions and that relieves police personnel
from repetitive tasks that claim much of their time while returning low or no value.
In order for CAS (State) to achieve the above goals, it is envisaged to meet the following
requirements:
 It will lay special emphasis on the functions at police stations with focus on
usability and ease of use of the application
 It will be designed to provide clear and tangible value to key roles at the
Police Station: specifically the SHO (Station House Officer), the IO
(Investigation Officer) and the Station Writer.
 It will be event and role-driven. Access controls will be developed and role
based access will be provided in the application.
 It will be content/forms-based, with customized forms based on requirements
 It will be a flexible application, event and role-driven system where actions on a
case can be taken as required without rigid sequence / workflows
 It will eliminate the need for duplicate and redundant entry of data, and the
need for repetitive, manual report preparation – this freeing valuable time and
resources for the performance of core police functions
 It will be intelligent and help police perform their roles by providing alerts,
highlighting key action areas, etc.
 Ability to view and exchange information amongst Police Stations, between
Police Stations and other Police formations and with external entities including
citizens
 Reporting and data requirements of higher offices must be met at the State
Data Centre/SCRB level and not percolate to the police station level
 Central facilitation and coordination; but primarily driven and owned by
States/UTs where States/UTs can configure and customize the CAS
for their unique requirements without the intervention of the central entity
Services in CAS (State)

Citizens Portal Service
This service shall enable Citizens to request services from Police through online petitions
and track status of registered petitions and requests online. Citizens requests/services
include passport verification services, general service petitions such as No Objection
Certificate (NOC) for job, NOC for vehicle theft, NOC for lost cell phone/passport, Licenses
for arms, processions etc.
Petition Management Service
The service shall enable the police personnel to register and process the different kinds of
general service petitions and complaints.
Unclaimed/Abandon Property Register Service
The service shall enable the police personnel to record and maintain unclaimed/abandoned
property registers and match unclaimed/ abandoned property with property in lost/stolen
registers.
Complaint and FIR Management Service
The service shall enable the police personnel to register and process the complaints (FIR for
cognizable complaints, Non-Cognizable Report for non-cognizable, Complaint Report for
general complaints, etc.) reported by the public.
Investigation Management Service
The service shall enable the police personnel to process the complaints through capturing
the details collected during the investigation process that are required for the investigation
officer to prepare a final report.
Court and Jail Interface and Prosecution Management Service
The service shall enable the police personnel to interface with the courts and jails during the
investigation process (for producing evidence, producing arrested, remand etc) and during
the trial process.
Crime and Criminal Records and Query Management Service
The service shall enable the police personnel to view various registers and perform basic
and advanced queries on the crime and criminal information.
Police Email and Messaging Service
The service shall enable the police personnel to send / receive official as well as personal
correspondence. Integration with existing WAN email System would be done by NIC.
Periodic Crime, and Law & Order Reports and Review Dashboard Service
The service shall enable the police personnel to view relevant reports and dashboards and
to conduct periodic crime, and law & order reviews of the police station(s) under the officer’s
jurisdiction.
Notification of Alerts, Important Events, Reminders and Activity Calendar or
Tasks Service
The service shall capture / generate the required alerts, important events, reminders, activity
calendar and tasks.
State-SCRB-NCRB Data Transfer and Management Service
The service shall enable the Tamil Nadu Police to collate, transform and transfer the crime,
criminal, and other related data from state to NCRB.
State CAS Administration and Configuration Management Service
The service shall enable the Tamil Nadu Police to configure/ customize the application to
suit to their unique requirements.
User Help and Assistance Service
The service shall enable the end user to view the help manuals of the application and in
guiding the end user in using the application.
User Feedback Tracking and Resolution Service
The service shall enable the police personnel in logging the issues/defects occurred while
using the system.
Activity Log Tracking and Audit Service
The service shall capture the audit trail resulting from execution of a business process or
system function.
User Access and Authorization Management Service
The service shall enable the administrative user in setting the access privileges and will
provide authentication and authorization functionality.
4.10 Development of CCTNS Core Application Software (CAS)
CAS (Centre) will be developed at NCRB under the overall guidance and supervision of
MHA, and a dedicated team from NCRB. NCRB, on behalf of MHA, engaged a professional
software development agency (SDA) to design and develop CAS (Centre) and offer
associated services. The SDA would enhance and maintain CAS (Centre) until the end of
the engagement with NCRB and subsequent to that, CAS (Centre) would be managed by
NCRB under the guidance of NIC, DIT and MHA and CAS (State) would be managed by the
State under guidance of the State IT Department.
CAS (State) or CIPRUS would be developed by NIC at SCRB. CAS (State) would be built as
a platform to address the core requirements of the Police Station to provide a basic
framework to capture and process crime and criminal information at the police station while
providing the state the flexibility to build their state specific applications around it and in
addition to it. Post development, NIC would provide the application to the selected SI for
commissioning. The SI would add customization/ extensions to the application as desired by
the states without compromising on the sharing of data to be done with NCRB.
In order to achieve the above stated goals of simultaneously ensuring consistency and
standardization across States/UTs (where necessary and possible), and enabling
States/UTs to meet their unique requirements, CAS will be built as a highly configurable and
customizable application. CAS would therefore be a product-like application that could be
centrally managed and at the same time customized to meet the unique requirements of
the States/UTs and deployed in all States/UTs. The following sections provide details of the
configuration and customization requirements of CAS.
In order to achieve the key CCTNS goal of facilitating the availability of real time information
across police stations and between police stations and higher offices, CAS would be built
as a web application. However, given the connectivity challenges faced in a number of
police stations, especially rural police stations, the application must be built to provide off-
line availability in police stations with unreliable connectivity.

4.11 Technology Stack for CAS (State)
CIPRUS which is positioned as CAS (State) would be developed in Free and Open Source
Solution (FOSS) stack by the NIC at the State. The interface to enable transfer of data
between this application and CAS Centre would be done by the System Integrator (SI). The
SI is expected to bid with FOSS Stack in response to this RFP. SI shall procure all
necessary underlying solution components required to successfully implement CCTNS
solution for the Tamil Nadu Police meeting their requirements as per this RFP. The details of
the Technology Stack are provided in Annexure-II of this RFP.
5. Role of NIC in supporting CAS

NIC shall offer the Application Management Services for CAS (State). Also NIC will provide
Technical Program Management of Implementation of CAS (State) in Tamil Nadu.
Each of these activities is detailed out below.
Application Management Services for CAS (State)

NIC shall provide Application Management services to the CAS (State). The application
management services include the following:
 Provisionof bug fixes, minor changes, error resolutions and minor
enhancements.
 Minor enhancements (the usual run-of-the-mill enhancements and not the Ones
identified as part of Continuous Improvement).
 Change request management based on feedback from the users.
 Release Management; Version control of CAS (State) to be managed centrally,
with state-specific configuration incorporated.
 Routine functional changes without affecting the base structure.
 Any changes to CAS code that may be required because of patches to licensed
software being used (if any).
 Updating and maintenance of all project documents.
All planned changes to the application, especially major enhancements and changes in
functionality that are deviations from the signed-off FRS/SRS, shall be coordinated within
established Change control processes to ensure that:
 Appropriate communication on change required has taken place.

 Proper approvals have been received from CAS Core Group/CTT/CPMU.
NIC will define the Software Change Management and version control process and obtain
approval for the same from SCRB. For all proposed changes to the application, NIC will prepare
detailed documentation including proposed changes, impact on the system in terms of functional
outcomes/additional features added to the system, etc.
Technical Program Management of Implementation of CAS (State)

After successful 3rd party Security Audit certification, NIC will handover the certified CAS (State)
to SCRB. During the period of CAS Solution Design and Development and the Operations and
Maintenance Phase following that, NIC shall provide technical program management services in
implementing CAS in the State. Through the Technical Program Management, NIC shall extend
all the necessary support to the State SI and ensure that the SI successfully configures, and
deploys CAS (State) in the state. NIC’s Technical Program Management responsibilities include:
 Preparation of technical manuals to enable the SI to configure and deploy CAS in the
State; to be made available to SI online.
 Preparation of “CAS Implementation toolkits” that comprehensively covers details on all

the aspects of the CAS (State applications including technical details of CAS,
configuration, customization, and extension details, infrastructure sizing details,
installation, commissioning, maintenance, infrastructure environment turning, and
performance tuning details that are required for the SI to successfully commission the
CAS (State) application in the State, integrate CAS (State) with external agencies and
third party solutions in the State and integrate CAS (State) with CAS (Centre) to
seamlessly transfer the required data to NCRB. The implementation toolkit shall also
include the following:
o All completed and updated training and support material needed for configuring
and deploying CAS
o All completed and updated project documents including FRS, SRS, and Test
Plans would be provided to SI with requisite approval from SCRB
o Relevant software assets/artefacts (including configuration utilities / tools,
deployment scripts to state SI to deploy CAS (State) in the
State)
o Relevant standards and design guidelines to the SI for enhancements, and
integration of the application with external systems and third party components
that will be implemented by the SI at the State
 Conduct of direct knowledge transfer through regular contact sessions at SCRB with the
State SI during the contract period of the SI. During the contact sessions, the NIC shall
conduct need based structured training sessions on the CAS Implementation Toolkit
prepared by NIC.
 Dedicated State Points of Contact: Members of NIC’s team shall act as points of
contacts for the state level SI. The point of contact will be responsible for addressing
queries from an SI and in meeting SLA targets (in responding to the State’s needs).
 Helpdesk Support: NIC shall provide Helpdesk support to the State SI during
deployment and stabilization phases with 8 contact hours (during normal business hours
of 10 AM to 6 PM), 6 days (Monday through Saturday, both included).
 Deployment Scripts: NIC shall develop the necessary deployment scripts to deploy CAS
(State) in the State and provide the same to State SI.
 Data Migration Utility: NIC shall develop a Data Migration Utility/application with all the
formats and tools to load the data into the state databases. This will be provided to the
State which will enable the State SI to migrate data from legacy systems to the CAS
databases.
 Language Localization Support: Proving interface in local languages is a key
requirement of CAS (State). NIC shall build CAS (State) with interfaces in English and
Tamil.
 Supporting the SI to ensure that the CAS (State) that is configured and
o Successfully passes the User Acceptance Testing (UAT).
o Data Migration of CAS (State) related data from the legacy systems to CAS
(State)
o Infrastructure Sizing related to CAS (State)
o Commissioning and Deployment of CAS (State)

o Infrastructure Environment Performance Tuning related to CAS (State)
o Integration of CAS (State) with external agency solutions
o Integration of CAS (State) with additional solutions being integrated by the SI at
the State
o Seamless data transfer from CAS (State) to CAS (Centre)
 Troubleshooting, resolution and escalation with State SI; and ownership of end-to-end
data exchange between the CAS (State) and CAS (Centre) needs to ensure seamless
and real-time data exchange.
6. Scope of the Project
6.1 Geographical Scope
The scope of CCTNS in the State of Tamil Nadu spans across all the police stations and all higher
police unit offices including Sub-Divisional Offices, District Headquarters, Commissionerates, Range
Headquarters, Police Headquarter, State Crime Record Bureau, and other Special Police Units and
their corresponding Headquarters.
The CCTNS project involves connectivity of police units (linking police units at all levels within the
States). CCTNS also provides a citizens’ interface to provide Police services to citizens. Indicative
numbers of locations within the State to be covered for implementing CCTNS project are as follows:
The locations to be covered under this project include the following:

S.No. Client Site Locations Number of Offices
1 Non CIPA Police Stations 1345
2 CIPA Police Stations 137
3 AC Range Office/SDPO 258
4 Range/Zone 16
5 SCRB 1
6 TN Finger Print Bureau/ Forensic Science Lab 2
7 District Control Room 40
8 State Control Room 1
9 DPO 33
10 Commissionerate 7
11 ADC/DC/JC/ACOP Offices 53
12 ADSP Office 62
13 Police HQ Office 1
FIR Registering Special Unit Offices
14 Coastal Security Group 11
15 CBCID 43
16 Crime (SIT) 34
17 CCIW 31
18 EOW 16
19 PEW 94
20 DCB/CCB 38
21 CSCID 20
22 TIW 44
23 TEW 148
24 JAPU 9
Government of Tamil Nadu Request for Proposal for Selection of System Integrator Page 35 of 302

25 AVS 3
26 ADoC 2
Sub-total 493
FIR Registering Special Unit HQ 6
27 CSG 1
28 CBCID 3
29 Crime (SIT) 1
30 Idol Wing 1
Sub-total 6
Total 2441
Note: SCRB reserves the right to consider in part or omit all the requirements mentioned
The scope of project would also include the following additional locations:
S.No Additional Locations Number of Offices
1 Intelligence HQ 1
Intelligence Offices
2 Q-Branch 30
3 SBCID 42
4 Special Division 6
5 Security Branch & Core Cell 10
6 Organized Crime and Intelligence Unit 19
7 SIT 5
Sub-total 112
8 Outposts 69
9 Jails (includes sub-jails, Borstal school, district 129
jails, special sub-jails and central prisons)
10 District Level SDFPB and FSL 74
Other Special Unit Offices
11 Technical Services 114
12 District Special Branch 40
13 Armed Police 17
14 Social Justice & Human Rights 15
15 Special Task Force 2
Sub-total 179
Other Special Unit HQ
17 Armed Police 1
19 Home Guards (HG) 1
20 State Traffic Planning Cell 1
21 Tamil Nadu Commando Force 1
Sub-total 6
Total 570
The aforementioned locations would be covered for implementing CCTNS project including but not
limiting to, Site Preparation, procurement, deployment and commissioning of requisite Hardware,
Network connectivity, deployment and commissioning of CAS (State) and additional modules (with
proper integration) as per the requirement of Tamil Nadu Police, training & handholding support and
further provisioning of the all the services mentioned as per scope of work of this RFP.
The bill of materials for above client locations and additional offices is available in Annexure- III and
IV respectively.
Networking Connectivity required at each of these locations is described in Annexure VII of this RFP
The indicative state map with all the districts/ Commissionerates depicting the location of all Police
Units to be covered under the scope of CCTNS is attached as Annexure XI.
In the pilot phase, the following locations are planned to be covered
1 State Headquarters
2 SCRB
3 State FPB
4 State FSL
5 FIR Registering Special Unit Headquarters
6 Additional Other Special Unit Headquarters
7 Client site locations in Pilot Phase districts
8 Additional locations in Pilot Phase districts
The below table presents the list of client site locations and additional locations to be covered at the
headquarters:
S.No Pilot Phase at Headquarters Number of Offices
Client Site Locations

1 Police HQ 1
2 SCRB 1
3 State Fingerprint Bureau 1
4 State Forensic Science Lab 1
6 SCRB 1
7 FIR Registering Special Unit Headquarters 6
(CBCID – 3, EOW – 1, Idol Wing – 1, CSG – 1)
Additional Locations
8 Other Special Unit Headquarters (TS-1, Home 6
Guard -1, Armed Police -1, STPC -1, SJ & HR -
1, TN Commando Force - 1)
9 Intelligence Headquarters 1
Note: SCRB reserves the right to include in part or omit all the requirements put under this section
The below table presents the list of client site locations to be covered in the pilot districts:
S.No Districts in Zone Range DPO/ ADC/DC/ SDPO/ Control PS Justification

Roll Out Comm* JC/ACOP AC Room
Phase I Offices Range
Office
1 Sivagangai 1 1 1 5 1 39 A rural set-up with

good compliance in
filling CAARUS
entries, the feedback
would be helpful in
rolling out to other
rural districts.
Represents the
Southern Zone
2 Thanjavur 1 1 1 8 1 51 A semi-urban set-up
with good awareness
levels of state IT
applications, feedback
would be helpful in
rolling out to similar
districts. Represents
the Central Zone
3 Chennai 0 1 3 10 13 1 47 Commissionerate set-
Sub-urban up with large number
of Police Stations
4 Coimbatore 5 14 1 18 Commissionerate set-
City up with good record in
filling CAARUS entries
* - Would include DCRB/CCRB
The following additional offices are also expected to be covered in Pilot Phases:
S.No Districts in Intelligence TIW/ District FIR Other Total

Pilot Phase Unit Offices TEW FSL/ Registering Special
Units SDFPB Special Unit Unit
Offices Offices
1 Sivagangai 3 3 2 4 4 16
2 Thanjavur 2 5 3 8 7 25
3 Chennai 0 15 1 5 19 40
Sub-urban
4 Coimbatore 3 18 1 4 2 28
City
8 41 7 21 32 109
For the pilot phase, a tentative list of activities and timeline as part of the implementation plan is
mentioned below:
Unit Name Activity Timeline (

in Months)
State HQ (includes HQ, SCRB, Setting up Date Centre T+3

State Control Room, TNFPB and
Setting up DR Centre T+3
TNFSL)
Data Digitization/Migration for all state HQ T+12
higher offices
ICT Hardware and Site T1=T+4
Preparation at SHQ and SCRB
Pilot A - CAS (State) - Availability of Police T2=T1+4

Intranet
Pilot B - Crime Analysis Suite T3=T2+1
Pilot C - Knowledge Base Suite T4=T3+1
Pilot D - Communication Suite T5=T4+1
Pilot E - Constable Suite T6=T4+2
Pilot F - Law & Order Suite T7=T6+2
Pilot G - Traffic Suite (for SCRB) T8=T7+2
Police Stations Data Digitization/Migration for all Police T+12
Stations
ICT Hardware and Site Preparation T1=T+4
Pilot A - Installation of CAS (State) of NIC T2=T1+4
Pilot G - Traffic Suite T8=T7+2

in Months)
SDPO/AC Range Offices Data Digitization/Migration for all T+12

SDPO/AC Range Offices
ADC/DC/JC/ACOP Offices Data Digitization/Migration T+12
Intranet
Commissionerate Data Digitization/Migration for all T+12
commissionerates

Intranet
DPO Data Digitization/Migration for all DPOs T+12
ICT Hardware and Site T1=T+4
Preparation

Intranet

in Months)

Range Data Digitization/Migration for all ranges T+12

Intranet
Zone Data Digitization/Migration for all zones T+12
Intranet
District Control Room Data Digitization/Migration for all district T+12
control rooms
Intranet
FIR Registering Special Unit HQ ICT Hardware and Site Preparation T1=T+4
(CCIW, CSG, CBCID, Crime (SIT),
PEW, DCB, CBCID, EOW, Idol
Intranet
Wing)
Other Special Unit HQ (AP, Home ICT Hardware and Site Preparation T1=T+4
Guard, TS, SJ & HR, TNCF, STPC)
Intranet
Intelligence HQ Data Digitization/Migration for Intelligence T+12
Units

in Months)

Intranet
Other Special Unit Offices ICT Hardware and Site Preparation T1=T+4
FIR registering Special Unit Offices ICT Hardware and Site Preparation T1=T+4
Traffic Enforcement and ICT Hardware and Site Preparation T1=T+4
Investigation Wing
Pilot G – Traffic Suite T8=T2+9
Intelligence Unit Offices ICT Hardware and Site Preparation T1=T+4
District Training Centres Capacity Building to identified Personnel T+15
in each of the districts
Note: The Software module rollout would happen sequentially after CAS State core software is piloted. Following are the
milestones as denoted in the table above:
T=Date of signing the agreement between department and SI
T1= Time when ICT hardware and site preparation is complete
T2= Time when CAS State base roll out is complete
T3= Time when Pilot A roll out is complete
T4= Time when Pilot B roll out is complete
T5= Time when Pilot C roll out is complete
T6= Time when Pilot D roll out is complete
T7= Time when Pilot E roll out is complete
T8= Time when Pilot F roll out is complete
It is assumed that only when the all the pilots are rolled out and capacity building activities for the
district to cover all the functionalities are done and feedback is gathered. The above mentioned plan
is indicative and the SI is expected to interact with the department to arrive at the exact
implementation plan
CCTNS Roll-out Phase-I
During Roll out Phase-I of CCTNS, coastal and border districts and commissionerate set-up from
Police Stations till DPO/Commissionerate will be covered for the installation and commissioning of
hardware, connectivity and other infrastructure and the other services as mandated by MHA
guidelines. The details of client site locations are provided in the table below.
S.No Districts in Roll Zone Range DPO/ ADC/DC SDPO/ Control PS

Out Phase I Comm* /JC/ACOP AC Room
Offices Range
Office
1 Dharmapuri 1 1 5 3 1 26
S.No Districts in Roll Zone Range DPO/ ADC/DC SDPO/ Control PS

Out Phase I Comm* /JC/ACOP AC Room
Offices Range
Office
2 Cuddalore 1 1 8 7 1 50
3 Nagapattinam 0 1 4 1 30
4 Ramanathapuram 0 1 6 1 46
5 Theni 1 1 5 1 34
6 Vellore 1 1 8 1 63
7 Thoothukudi 1 1 8 1 54
8 Kanniyakumari 0 1 4 1 38
9 Tirunelveli 0 1 9 1 65
10 Coimbatore 1 1 5 1 35
11 Nilgiris 0 1 5 1 30
12 Tiruvallur 1 1 5 1 32
13 Krishnagiri 1 1 5 1 34
14 Villupuram 1 1 7 1 54
15 Kancheepuram 0 1 5 1 41
16 Tirunelveli City 1 8 8 1 7
17 Pudukottai 1 1 3 1 39
The details of additional locations to be covered are provided in the table below.
FIR Other Total

TIW/ District
Districts in Roll Intelligence Registering Special
S.No TEW FSL/
Out Phase I Unit Offices Special Unit Unit
Units SDFPB
Offices Offices
1 Dharmapuri 2 1 2 3 2 10
2 Cuddalore 3 3 2 7 2 17
3 Nagapattinam 3 4 2 9 3 21
4 Ramanathapuram 3 2 4 4 3 16
5 Theni 2 1 2 5 2 12
6 Vellore 2 2 3 7 5 19
7 Thoothukudi 3 1 2 8 3 17
8 Kanniyakumari 2 4 2 9 5 22
9 Tirunelveli 3 3 2 8 5 21
10 Coimbatore 4 3 3 8 5 23
11 Nilgiris 2 3 2 3 2 12
12 Tiruvallur 2 2 2 4 2 12
13 Krishnagiri 2 3 2 4 3 14
14 Villupuram 2 5 2 5 4 18
15 Kancheepuram 2 4 2 5 3 16
16 Tirunelveli City 1 7 1 2 3 14
17 Pudukottai 2 2 2 3 2 11
Total 40 50 37 93 52 282
For the rollout phase-I, a tentative list of activities and timeline as part of the implementation plan is
mentioned below:
in Months)
Police Stations ICT Hardware and Site Preparation D1=D+9

Installation of CAS (State) of NIC D2=D1+9
Knowledge Base Suite
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
SDPO/AC Range Offices ICT Hardware and Site Preparation D1=D+9
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
ADC/DC/JC/ACOP Offices ICT Hardware and Site Preparation D1=D+9
Availability of Police Intranet and Web- D2=D1+9
services based on Consolidated Data
Crime Analysis Suite
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
Commissionerate ICT Hardware and Site Preparation D1=D+9
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
DPO ICT Hardware and Site Preparation D1=D+9

in Months)

Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
Range ICT Hardware and Site Preparation D1=D+9
Communication Suite
Traffic Suite
Zone ICT Hardware and Site Preparation D1=D+9
Communication Suite
Traffic Suite
District Control Room ICT Hardware and Site Preparation D1=D+9
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
Other Special Unit Offices ICT Hardware and Site Preparation D1=D+9
FIR registering Special Unit Offices ICT Hardware and Site Preparation D1=D+9
Traffic Enforcement and ICT Hardware and Site Preparation D1=D+9
Investigation Wing
Traffic Suite
Intelligence Unit Offices ICT Hardware and Site Preparation D1=D+9

in Months)

District Training Centres Capacity Building to identified Personnel D+12
Note: Following are the milestones as denoted in the table above:
D=Date of beginning Rollout Phase-I, should be within 1 month of completion of Pilot Phase I
D1= Date of ICT hardware rollout completion
It is expected that the software and ICT hardware rollout would happen in a rolling manner and the SI is expected to interact
with the department to arrive at the priority list of districts from which the roll out for this phase will begin
The above mentioned plan is indicative and the SI is expected to interact with the department to arrive at
the exact implementation plan
CCTNS Roll Out Phase – II
During the roll-out Phase-II of the application, CCTNS hardware rollout would be complete with the roll
out happening to all other locations. Outposts, Jails and all ADSP Offices would be covered in this
Phase. Any further services the state wishes to provide to the citizen would be covered in this phase. In
this phase, the remaining identified personnel would also be trained in the concerned modules to bring
all the regions in the state to become ready for using the CCTNS application.
The details of client site locations and additional locations to be covered across the state are mentioned
below:
Client Site Locations

1 ADSP Offices 62
Additional Locations
2 Jails (including central jails, sub-jails and 129
Borstal Schools)
3 Outposts 69
4 Intelligence Unit Offices (OCIU and SIT) 24
The details of client site locations to be covered in this phase are mentioned below:
S.No Districts in Roll Out Zone Range DPO/ ADC/DC/ SDPO/ PS

Phase II Comm* JC/ACOP AC
Offices Range
Office
1 Tiruvannamalai 1 1 6 45
2 Namakkal 1 4 29
S.No Districts in Roll Out Zone Range DPO/ ADC/DC/ SDPO/ PS

Phase II Comm* JC/ACOP AC
Offices Range
Office
3 Salem 1 6 38
4 Erode 1 1 7 48
5 Tiruppur 1 6 30
6 Karur 1 1 3 18
7 Ariyalur 1 2 18
8 Perambalur 1 1 9
9 Trichy 1 5 32
10 Thiruvarur 1 4 28
11 Dindigul 1 7 42
12 Madurai 1 1 7 47
13 Virudhunagar 1 7 53
14 Railway Chennai 1 1 17
15 Railway Trichy 1 1 35
16 Salem City 1 5 8 14
17 Madurai City 1 5 9 20
18 Trichy City 1 5 8 16
19 Greater Chennai 1 15 29 110

The details of additional locations to be covered in this phase are mentioned below:
FIR Other
TIW/ District
Districts in Roll Out Intelligence Registering Special
S.No TEW FSL/ Total
Phase II Unit Offices Special Unit Unit
Units SDFPB
Offices Offices
1 Tiruvannamalai 2 2 2 4 1 11
2 Namakkal 1 3 2 4 3 13
3 Salem 2 3 2 8 4 19
4 Erode 2 3 2 6 6 19
5 Tiruppur 2 4 2 1 1 10
6 Karur 2 1 2 4 2 11
7 Ariyalur 1 0 2 1 2 6
8 Perambalur 2 0 2 3 2 9
9 Trichy 5 2 2 8 10 27
10 Thiruvarur 2 3 2 3 1 11
11 Dindigul 2 6 2 7 7 24
12 Madurai 5 4 2 9 6 26
13 Virudhunagar 2 6 2 6 4 20
14 Salem City 1 3 0 1 2 7
15 Madurai City 2 10 0 5 2 19
16 Trichy City 2 8 2 3 2 17
17 Greater Chennai 31 43 2 26 48 150
Total 66 101 30 99 103 399
For the roll out phase-II, a tentative list of activities and timeline as part of the implementation plan is
mentioned below:
in Months)
Police Stations ICT Hardware and Site Preparation E1=E+9

Installation of CAS (State) of NIC E2=E1+9
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
SDPO/AC Range Offices ICT Hardware and Site Preparation E1=E+9
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
ADC/DC/JC/ACOP Offices ICT Hardware and Site Preparation E1=E+9
Availability of Police Intranet and Web- E2=E1+9
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
Commissionerate ICT Hardware and Site Preparation E1=E+9
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
DPO ICT Hardware and Site Preparation E1=E+9

in Months)

Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
Range ICT Hardware and Site Preparation E1=E+9
Communication Suite
Traffic Suite
Zone ICT Hardware and Site Preparation E1=E+9
Communication Suite
Traffic Suite
District Control Room ICT Hardware and Site Preparation E1=E+9
Communication Suite
Constable Suite
Law & Order Suite
Traffic Suite
Other Special Unit Offices ICT Hardware and Site Preparation E1=E+9
FIR registering Special Unit Offices ICT Hardware and Site Preparation E1=E+9
Traffic Enforcement and ICT Hardware and Site Preparation E1=E+9
Investigation Wing
Traffic Suite
Intelligence Unit Offices ICT Hardware and Site Preparation E1=E+9

in Months)
Outposts ICT Hardware and Site Preparation E1=E+9

ADSP Offices ICT Hardware and Site Preparation E1=E+9
Communication Suite
Traffic Suite
Jails ICT Hardware E1=E+9
District Training Centres Capacity Building to identified Personnel E+12
Note: Following are the milestones as denoted in the table above:
E=Date of beginning Rollout Phase-II, should be within 2 month2 of completion of Rollout Phase I
E1= Date of ICT hardware rollout completion
It is expected that the software and ICT hardware rollout would happen in a rolling manner and the SI is expected to interact
with the department to arrive at the priority list of districts from which the roll out for this phase will begin
The above mentioned plan is indicative and the SI is expected to interact with the department to arrive at
the exact implementation plan
Operate & Maintain Phase

Operate and Maintain phase would commence in a rolling manner after the successful =implementation
of CCTNS in the specific districts belonging to a phase as per the scope of work mentioned in this RFP.
In addition to activities relating to operate and maintain of the comprehensive CCTNS solution, the
phase would also include the implementation of subsequent versions, upgrades, patches of CAS as
released by NCRB and the other initiatives of Tamil Nadu Police as part of MMP CCTNS.
6.2 Functional Scope
CCTNS intends to enable improving efficiency and effectiveness of police processes and also aid in
crime investigation through sharing of information pertaining to crime and criminal across police offices.
Apart from collating and maintaining data on crime and criminals, Police Officials and Personnel render a
variety of services in area of maintenance of law and order, crime investigation, major events monitoring
VIP bandobust, traffic enforcement and investigation, prosecution and witness trial management,
intelligence gathering and crime prevention, etc. Police stations also serves as front-end of the entire
police department in dealing with public complaints and requests, and at the same time they occupy a
pivotal place as the primary source of collection of information for the other functions/wings within the
department such as Intelligence. Thus, the functional scope of the application for CCTNS Tamil Nadu
would include:
a) Modules specific to Crime and Criminal data

b) Modules pertaining to state specific requirements
The list of functional modules is mentioned below:
6.2.1 CCTNS Functional Modules
The following table illustrates the services to be developed as part of Core Application Software (CAS)
State by NIC. This includes core services and support services as mentioned below:
S.No CCTNS Module/Service Description

Core Services mandated to be part of CAS (State)
1 Citizen Interface This would provide an interface for citizens to access
Police services online and know the status of their
complaint by keying in the Service Request Number. Also,
this would allow downloading copies of documents such as
FIR as .pdf format
2 Complaint & FIR This would enable capturing of FIR and complaint details in
Management Service the application and would also provide ability to store
images, voice and video pertaining to the case. The screen
would also be presented differently based upon the type of
complaint. Based upon approval by concerned superior
official, acknowledgment would be provided
3 Petition Management This would enable capturing of petition details in the
Service application and would also provide ability to store images,
voice and video pertaining to the case. The screen would
also be presented differently based upon the type of
petition. Based upon approval by concerned superior
official, acknowledgment or certificate would be provided
4 Investigation This provides facility to update case progress and store
Management Service images, voice and video pertaining to case investigation.
This would provide dashboard relating to cases under
investigation and facility to print arrest card
5 Unclaimed/Abandoned This provides ability to search database of abandoned and
Property Register unclaimed property across stations and also has a feature
Service to show an alert in case a newly registered case’s vehicle
number matches with the number already in database
6 Notification of Alerts, This module would assist the police personnel’s to get
Important Events, notification of alerts; important events, reminders and
Reminders and Activity activity calendar to help them get latest information about
Calendar or Tasks arrest, vehicles recovered, un-known dead bodies, Date of
Service VIP bandobust etc.

7 Police email and The Police Messaging system is role based
Messaging Service communication system to help the police personnel send
“Faster” and “Secure” official correspondence within /
across the multiple wings within / across the Police
departments. Integration with existing WAN Mail System
would be done by NIC
8 Periodic Crime & Law & This functionality will help the police personnel to view the
Order Reports and snapshot of the various statistics within and across police
Review Dashboard stations on petitions/ complaints, cases, NCR, FIR,
Service warrants, wanted offenders/suspects etc.,. This will also be
used by the higher officers at all levels/roles to conduct
periodic reviews of the police stations in their jurisdiction.
9 Court & Jail Interface System would provide an interface for entering the data on
and Prosecution People releasing from jail, people coming on bail and
Management Service parole. System would allow entry of case trial details to the
database.
10 Crime & Criminal This module will help the police personnel in searching
Records and Query (Quick & Advanced) any person of interest (missing
Management Service persons, arrested, released from jails, convicted,
acquitted), property of interest, complaint, crime, ,
abandoned / unclaimed property, stolen / lost property ,
pending warrants, pending summons and other
investigation-toolkit-data (Vehicle Registration, Driver
License, Cell Phone Numbers, Voter Details, Education
Data etc.). Search facility would be integrated with all the
modules proposed in this document. This module would
work as a one stop search facility for anything stored in the
information/ knowledge base of Tamil Nadu Police.
11 State SCRB- NCRB This functionality will enable the states to transfer the crime
Data Transfer and and criminal data from the state, organize it suitably to
Management Service serve the NCRB requirements.
Support Services mandated to be part of CAS (State)
12 State CAS This would be in-built in the CAS State application that is
Administration and being developed by NIC.
Configuration
Management Service
13 User Help and This would be in-built in the CAS State application that is
Assistance Service being developed by NIC.
14 User Feedback This functionality would be in-built in the CAS State
Tracking and Resolution Application that is being developed by NIC. This will help
Service the police personnel in logging the issues/defects occurred

while using the system on to Issue tracking system.
15 Activity Log Tracking This functionality would be in-built in the CAS State
and Audit Service Application that is being developed by NIC. This
functionality will maintain an unalterable Audit Trail, which
is a sequence of audit records, each of which contains
evidence directly pertaining to and resulting from execution
of a business process or system function.
16 User Access and The service shall enable the administrative user in setting the
Authorization access privileges and will provide authentication and
Management Service authorization functionality.
There would be enhancements and additional functionalities to be developed on top of CAS State
by the SI. The following table illustrates the additional functionalities to be developed on top of CAS
(State):
Additional Functionality to be developed on top of CAS (State)
1 Visual Representation The system would allow presentation of graphical analyses
of Data of data drawn from various databases
2 Geographic Information The system would allow plotting of details such as crime
System (GIS) Maps and accidents on GIS map. This would be useful to get an
accurate picture of which areas crime is more concentrated
in and suitable measures can be taken accordingly.
3 Missing persons and Missing persons and Unidentified Dead Bodies, Stolen and
Unidentified Dead Recovered Property - Collation and Feeding Data to CAS
Bodies - Collation and (Centre in prescribed database format), Development of
Feeding Data to CAS APIs for interfacing with CAS (Centre) functionality such as
(Centre in prescribed Talaash, MVCS, etc.
database format),
Development of APIs
for interfacing with CAS
(Centre) functionality
such as Talaash,
MVCS, etc.
4 Tagging fingerprint data The system would allow attaching fingerprints related to
to crime and criminal criminal and case to the already entered case details
data wherever available
5 Global Positioning This module would help in monitoring and locating the
System location of patrol cars and police officers using GPS
technology.

6 Media Monitoring System would make facilitate generation of reports from
Module media news releases based on defined keywords: The
system should facilitate capture of information from various
newspapers and other media release based on keywords
such as murder, dacoity from editions of various districts in
various newspapers and prepare a daily report based on
the same.
7 Police Intranet Website Development of a Police Intranet Website containing
department specific content including sharing of data on
missing persons, officials' transfers, etc. System would
facilitate development and maintenance of an intranet
website: This would facilitate uploading of important
documents including Police Standing Order, staff manuals,
important GOs, important transfers, details of sensitive
cases which would be scrolled on the web home page. The
home page would be reached on authentication of officers’
login. Depending on the rank of officer and location, the
items that would be displayed on the homepage would
differ. The locally important data would be flashed to a
district SP vis-à-vis an IG sitting in the headquarters.
Communication Suite
8 Social Networking Development of Interface between Police Website and
Social Networking for sharing of information such as
photos of traffic accidents, etc.
9 Mobile Interface and Development of mobile/SMS software for sending and
Services receiving information by and to citizens
Law & Order Suite
10 Mass Event Monitoring System would facilitate monitoring of resources during
mass deployment: The system would allow provision to
maintain the details of resources, their home base, vehicle
details, contact details including mobile number, place they
are deputized to work and so on. This would enable
tracking of the resources as and when needed.
11 CCTV Cameras Develop systems which will link up with CAS State
database for storing images captured in CCTV cameras
installed in critical places and images captured during
monitoring of large public gatherings
Traffic Suite
12 RTO Database Access Develop interface to access data maintained by RTO in

databases such as Vaahan and Sarathy. System would aid
traffic police personnel in crime prevention: The system
would support traffic personnel by providing a GPRS based
interface to access Transport Database(s)
13 Spot Fine Issue Ascertaining ownership of vehicle and issue spot fines for
traffic violations. There would be a facility to issue spot fine
receipts through a hand-held device which would also
enable GPRS based access to Transport database(s).
Constable Suite
14 Beats Management System would aid in noting down beat activities from spot:
System The System would allow transfer of beat tickets to
handheld terminals. An application would be residing on
the terminal on which completed beat activities can be
updated by police personnel and this data should be
synchronized with station database at the end of beat duty.
System would provide a mobile interface of functions such
as beat tickets so that it can be accessed by Police
Personnel from the field.
System would have ability to store data fields of voice,

video and images: The Handheld device would be used to
take in details in the form of audio, video or images. The
System’s database should be designed to have these fields
as part of the database structure.
15 Prisoner Escort Module This would present activities to be done by each escort
taking prisoner for court hearing including which route to
take and where to stay overnight if journey is long and so
on.
16 Explosives Check System would provide interface for entering and storing
details of explosives maintained at various shops in a sub-
district. This would be checked periodically by higher
officers.
17 Develop Interface to System would provide interface to access passport e-seva
access Passport e-seva module and automate the role of police department in
module police verification and report submission
Note: Detailed Functional Requirement Specifications are attached as Annexure XII to this RFP
SI will be required to customize the CAS (State) as received from NIC and shall also be responsible for
developing/ deploying other additional Modules meeting the functional requirements mentioned in the
Functional Requirement Specifications attached as Annexure-XII to this document and other integration
requirements.
SI will be required to develop the following suites modules and functionality in each suite as mentioned
above:
 Knowledge Base Suite
 Constable Suite
 Communication Suite
 Traffic Suite
 Law & Order Suite
The detailed functional requirements specifications of the above mentioned modules and
services are mentioned in Annexure XII.
6.2.2 Solution & Technology Architecture
National Crime Record Bureau, Ministry of Home Affairs, Government of India is the driving group
behind the development of Core Application Software at the Central level, therefore Solution and
Technology Architecture has been defined centrally by this group. However, a detailed TO BE state for
the ICT Hardware and solution & technology architecture has been developed for Tamil Nadu Police with
a focus on how the solution will enable the Tamil Nadu Police to provide a consolidated suite of
applications that can seamlessly interface with external sources such as other States, Centre, and other
external agencies.
CCTNS is deployed on a centralized architecture wherein application would be deployed at the State
Data Center and various offices of Police Department will connect to the system through MPLS VPN
Connectivity Option suggested centrally. The overall technology solution would be based upon most
relevant and suitable architecture standards including standards for Service Oriented Architecture
(SOA), XML services & necessary protocols for internet applications, Data Center standards etc.
Deployment Architecture
The proposed overall solution framework for the Department is presented in this section depicting the
overall ‘Big Picture’ of the key target areas of IT initiatives and their inter-relationships. This blue print
would be used as a communication tool that provides a snapshot of the overall goal/ direction to be
taken up for implementation of CCTNS project to which all the stakeholders could relate to, without
getting into the complex details of the internal workings of each of these initiatives. All the modules
depicted in the overall solution framework and explained in detail as part of the Functional Requirement
Specification – provides the overall goal of the Department, including the adoption of core applications
modeled under the CCTNS scheme. It is required that all the additional modules to be developed by SI
should be compliant to DIT, GoI standards and guidelines for open standards. This would enable ease of
interoperability and also be significantly more economical for the Tamil Nadu Police. It is recommended
that SI will opt for Service Oriented Architecture (SOA) for implementing CCTNS application modules.
The SI shall choose the technology such that:
 It can help businesses (Police functions) respond more quickly and cost-effectively to changing
market conditions.
 It shall promote reuse at the macro (service) level rather than micro (classes) level. It can also
simplify interconnection to - and usage of - existing IT (legacy) assets.
 It shall also support the principles of good design: Granularity, interoperability and modularity.
 The issues related to performance, manageability, and scalability shall be well addressed and
system shall provide a more manageable system and less contention for resources.
The overall Solution Blue-print of Tamil Nadu CCTNS is depicted in the figure below:
Users
The users of the application will cut across the hierarchy of the department and would also include
special unit offices. The type of communication shared between the basic unit, viz., police station and the
higher offices including DPO, Range Office and Zonal office would be periodic reviews and abstracts
depicting progress of cases and other activities at the specific police station. Similarly, such reports for
entire district would be prepared by the DCRBx/CCRBx and sent to SCRB or Headquarters for their
review. For special units such as Intelligence, CAARUS could be provided to the individual unit offices
and HQs. The software can be used to enter details of crime cases registered at Q-branch, updation of
case status, etc.
Core Function Business Application Layer
The application would have a core function business application layer which would include the basic
services and functions provided by the CAS (State) application.
Support Function Business Application Layer
The support function business application layer would include the user management and other
administrator level services.
BPR Component Business Layer
BPR component business layer would include the additional components that would be suggested as
part of process re-engineering which would be loaded in top of state specific CAARUS up-scaled
application.
Database
For the purpose of easier understanding the databases have further been divided into the important
databases. The databases including Missing Persons, Unclaimed Property, FIR/CSR, PCR Call and
Prosecution which would enable the department to provide the core and BPR services in a much more
efficient manner to the various stakeholders.
Security Components
CAS (State) is based on centralized architecture. The various users of the application will be given a role
based access. The users would be able to login to the application using the User ID and password
assigned to them. As this is a web based application the password would not be authenticated on the
users’ system but would be authenticated at the central location. This access would be governed by the
group policy as decided by the department. Therefore the users at a particular level of hierarchy would
get similar screens. The policy would be administered at the centralized location by the administrator of
the application. This role based access would give the users the screens based on their roles. The
application would maintain activity logs and audit trail of each user. The logs would enable senior officers
to find out unauthorized changes to the complaints/FIR. Senior Officer would also be able to see the
entries made by his/her juniors to guide them on the course to be taken for a particular investigation etc.
The functional architecture of the proposed system is illustrated in the figure below:
6.3 Scope of Services during Implementation Phase
The scope of the “bundled services” to be offered by the SI includes the following:
 Project planning and management

 Configuration, Rolling out of CAS (State) and Extension (New Modules) of CAS (State), Enable
Data Transfer to CAS (Centre). CAS (State) will be developed for Tamil Nadu in Free and Open
Source Solution (FOSS) Stack by National Informatics Centre (NIC) which would also provide
services to the state police department in a manner similar to that of Software Development
Agency (SDA) engaged by NCRB/MHA at the Centre. The SI is expected to bid with FOSS stack
in the response to this RFP. SI shall procure all the necessary underlying solution components
required to deploy the CAS (State) solution for the State.
 Site preparation at the Client site locations (Police Stations, AC Range Offices, Higher Offices of
Commissionerates (ADC,DC,JC,ACOP Offices), Commissionerates, District Police Offices,
ADSP Offices, Range offices, Zones, SCRB, SDPOs, State Forensic Science Lab, State
Fingerprint Bureau, State Police Control Room, District Police Control Room, District HQ and
State HQ) and Data Center.
 Site preparation at the Additional Client site locations (Special Unit Police Stations, Special Unit
Police Station HQ, Special Unit Non Police Station Offices, Special Unit Police Station HQ,
Outposts, Intelligence Unit Offices, Intelligence HQ, District Forensic Science Lab, District Single
Digit Fingerprint Bureau and Prisons).
 IT Infrastructure at the Client site locations (Police Stations, AC Range Offices, Higher Offices of
Commissionerates (ADC,DC,JC,ACOP Offices), Commissionerates, District Police Offices,
ADSP Offices, Range offices, Zones, SCRB, SDPOs, State Forensic Science Lab, State
Fingerprint Bureau, State Police Control Room, District Police Control Room, District HQ and
State HQ).
 IT Infrastructure at the Additional Client site locations (Special Unit Police Stations, Special Unit
Police Station HQ, Special Unit Non Police Station Offices, Special Unit Police Station HQ,
Outposts, Intelligence Unit Offices, Intelligence HQ, District Forensic Science Lab, District Single
Digit Fingerprint Bureau and Prisons).
 IT infrastructure at the Data Center and Disaster Recovery Center including the necessary
hardware, software and other networking components.
 Data migration and Digitization of Historical Data including digitization of data for Special Unit
Offices
 Migration of data from CIPA and CCIS to CAS (State)
 Capacity building
 Handholding Support
 Support to 3rd party acceptance testing, audit and certification
 National Service Delivery Gateway (NSDG)/ State Service Delivery Gateway (SSDG): The
System Integrator at the state level shall register as a Service Provider with the NSDG
Or SSDGs on behalf of the respective State Government and provide CCTNS based
services.Initially if NSDG/SSDG services are not available the CCTNS application shall
access servicesthrough the existing broadband networks and SDA shall develop APIs for
the required departments during CAS development to enable interoperability and
interconnectivity for its eventual integration with NSDG/SSDG. C‐DAC as Gateway
Service Provider of NSDG/SSDG shall provide connectors/Adapters and guidelines for
hosting services through NSDG/SSDG after the SI register as a Service Provider on behalf
of the Tamil Nadu Government.
In implementing the above, the SI shall strictly adhere to the standards set by the MHA, NCRB, and
State.
The project will be managed out of State Nodal Officer’s office in State HQ. At all points in the execution
of the project, key senior resources including the project manager must be based at State Nodal Officer’s
office in State HQ.
6.3.1 Project Planning and Management
This project is a geographically spread initiative involving multiple stakeholders. Its implementation is
complex and though its ultimate success depends on all the stakeholders; the role of SI is key and hence
SI is required to design and implement a comprehensive and effective project management methodology
together with efficient & reliable tools.
To have an effective project management system in place, it is necessary for the SI to use a Project
Management Information System (PMIS). The SI shall address at the minimum the following using
PMIS:
a. Create an organized set of activities for the project
b. Establish and measure resource assignments and responsibilities
c. Construct a project plan schedule including milestones
d. Measure project deadlines, budget figures, and performance objectives
e. Communicate the project plan to stakeholders with meaningful reports
f. Provide facility for detecting problems and inconsistencies in the plan
g. During the project implementation the SI shall report to the State Nodal Officer, on following
items:
(i) Results accomplished during the period;
(ii) Cumulative deviations to date from schedule of progress on milestones as specified in
this RFP read with the agreed and finalized Project Plan;
(iii) Corrective actions to be taken to return to planned schedule of progress;
(iv) Proposed revision to planned schedule provided such revision is necessitated by
reasons beyond the control of the SI;
(v) Other issues and outstanding problems, and actions proposed to be taken;
h. Progress reports on a fortnightly basis
i. Interventions which the SI expects to be made by the State Nodal Officer and/or actions to be
taken by the State Nodal Officer before the next reporting period;
j. Project quality assurance reports

k. As part of the project management activities, the SI shall also undertake:
i. Issue Management to identify and track the issues that need attention and resolution
from Tamil Nadu Police.
ii. Scope Management to manage the scope and changes through a formal management
and approval process
iii. Risk Management to identify and manage the risks that can hinder the project progress
The Project plan prepared by the SI would be reviewed by the Governance Structure in the State and
approved by the Committee on the advice of the State Mission Team and State Project Management
Unit.
The SI would update and maintain the Project Plan throughout the duration of the engagement. All
changes are to be reviewed and approved by the CAS Core Group.
Requirements Traceability Matrix

The SI would ensure that developed solution is fully compliant with the requirements and specifications
provided in the RFP such as functional, non-functional and technical requirements. For ensuring this, the
SI shall prepare a Requirements Traceability Matrix on the basis of Functional Requirements
Specifications (FRS), Non Functional Requirements Specification, and Technical Requirements provided
by State (updated, expanded and fine-tuned by the SI as necessary) and the System Requirements
Specifications (SRS) prepared by the SI. This matrix would keep track of the requirements and trace
their compliance through different stages of the project including software design, coding, unit testing
and acceptance testing. The Requirements Traceability Matrix would be a live document throughout the
project, with the SI team updating the matrix at every stage to reflect the meeting of each specification at
every stage.
Through the duration of the project, the State Mission Team will periodically review the Traceability
Matrix. State Governance Structure would provide the final approval on the advice of the State Mission
Team and SPMU once they are satisfied that all requirements are met.
Project Documentation
The SI shall create and maintain all project documents that would be passed on to State as deliverables
as per the agreed project timelines. The documents created by the SI will be reviewed and approved by
the Governance Structure Setup in the State. State Mission Team would also approve any changes
required to these documents during the course of the project. State will finally sign-off on the documents
on the recommendation of State Mission Team / SPMU.
Project documents include but are not limited to the following:

 Detailed Project Plan
 Updated/vetted FRS
 SRS document
 SDD document
o HLD documents (including but not limited to)

 Application architecture documents
 ER diagrams and other data modeling documents
 Logical and physical database design
 Data dictionary and data definitions
 Application component design including component deployment views, control
flows, etc.
o LLD documents (including but not limited to)
 Application flows and logic including pseudo code
 GUI design (screen design, navigation, etc.)
 All Test Plans
 Requirements Traceability Matrix
 Change Management and Capacity Building Plans
 SLA and Performance Monitoring Plan
 Training and Knowledge Transfer Plans
 Issue Logs
 Source Code document and Troubleshooting documents
The SI shall prepare the SDD Document in accordance with the ANSI/IEEE Std 1016-1987
Recommended Practice for Software Design Description.
The SI shall submit a list of deliverables that they would submit based on the methodology they propose.
The SI shall prepare the formats/templates for each of the deliverables upfront based upon industry
standards and the same will be approved by State prior to its use for deliverables.
All project documents are to be kept up-to-date during the course of the project. The SI shall maintain a
log of the internal review of all the deliverables submitted. The logs shall be submitted to State Nodal
Officer on request.
All project documentation shall conform to the highest standards of software engineering documentation.
Procure, Commission and maintain Project Management, Configuration Management and Issue Tracker
Tools at State HQ / SCRB
Project Management Tool: The SI shall keep the project plan and all related artefacts up-to-date during
the course of the project. In order to help with the project management, the SI shall use a suitable
standard, proven off-the-shelf project management tool (preferably with unrestricted redistribution
licenses). The SI shall install the project management software at State’s premises right at the beginning
of the project. The tool shall provide the dashboard view of the progress on project milestones by the
Nodal Officer and other Supervisory Officers of CCTNS.
Configuration Management Tool: The SI shall keep all project documents up-to-date during the course
of the project. In order to help with the version/configuration management for all documents (including
source code and all other project artefacts), the SI shall use a suitable standard, proven off-the-shelf
configuration management tool (preferably with unrestricted redistribution licenses). The SI shall install
the configuration management software at State’s premises right at the beginning of the project.
Issue Tracker: The SI shall employ a suitable and proven tool for tracking issues (preferably with
unrestricted redistribution licenses) through the execution of the project. The SI shall install the Issue
Tracking System at State’s premises to enable State’s users to access and use the same.
The SI shall procure and commission the required infrastructure (software, servers) for Project
Management Tool, Configuration Management Tool and Issue Tracker tool and maintain the same
through the duration of the project. These tools along with the servers on which they are deployed will
become property of the State and will be used by State even beyond the contract period.
The SI would setup an online repository on PMIS / Configuration Management Tool for providing
centralized access to all project documents including manuals and other materials. The online repository
would be maintained by the SI through the engagement period. The SI should ensure that the repository
is built on appropriate security features such as role- and necessity-based access to documents.
6.3.2 Configuration, Customization, and Extension (New Modules) of CAS (State)
System Study, Design, Application Development and Integration

The SI shall carry out a detailed systems study to refine the Functional Requirements Specifications
provided as Annexure to this RFP and formulate the System Requirements Specifications (SRS)
incorporating the standards and functional specifications provided by the NCRB and the state-specific
requirements. The SI shall also study CAS (State) and CAS (Center) being developed at NIC and NCRB
respectively during the system study phase. The SRS preparation shall take into account the BPR
recommendations suggested by the NCRB / State. The SI should also prepare a detailed document on
the implementation of CAS (State) with respect to configuration and rolling-out of CAS (State) and
extension of new modules as per the requirement of state.
1. Conduct of System Study at the locations earmarked for Pilot Phase. The locations are
mentioned in Implementation Plan in Annexure-XI.
2. Preparation of System Requirements Specifications (SRS) for additional functionalities and
different integration points with CAS (Center), CAS (State) and External agencies.
3. Preparation of CAS (State) implementation document with respect to Configuration, rolling
out and extension of new modules as per the requirement of state.
4. Preparation of the Solution Design
5. Solution Development and/or Configuration and/or Extension as required
6. Development of reports
7. Formulation of test plans and test cases for additional functionalities and different
integrations with external agencies including CAS (Center)
8. Testing of the configured solution (CAS) and additional functionalities.
Enhancements of functions / additions of new modules / services to CAS-State as per state specific
requirements / integration requirements to various interfaces / SSDGs shall also be incorporated in the
SRS and shall form the scope of work for the SI.
Creation of Test Plans: Once the SRS is approved and design is started, the SI would prepare all
necessary Test Plans (including test cases), i.e., plans for Unit Testing, Integration and System Testing
and User Acceptance Testing. Test cases for UAT would be developed in collaboration with domain
experts identified at state headquarters. The Test Plans also include planning for the testing any
integration with MOB Software, Case Monitoring System, 3rd party COTS solutions, CAS (Center), any
external agencies. The Test Plans should also specify any assistance required from State and should be
followed upon by the SI. The SI should have the Test Plans reviewed and approved by the State Mission
Team/SPMU. The State headquarters will sign off on the test plans on the advice of State Mission
Team/SPMU.
High Level Design (HLD): Once the SRS is approved, the SI would complete the HLD and all HLD
documents of the additional functionalities, integration with CAS Center and external agencies upon the
approved SRS. The SI would prepare the HLD and have it reviewed and approved by the State mission
team/SPMU. The State will sign off on the HLD documents on the advice of State Mission Team/ SPMU.
Detailed (Low Level) Design (LLD): The LLD would interpret the approved HLD to help application
development and would include detailed service descriptions and specifications, application logic
(including “pseudo code”) and UI design (screen design and navigation). The preparation of test cases
will also be completed during this stage. The SI would have the design documents reviewed and
approved by the State Mission Team/SPMU. State headquarters/Nodal officer will sign off on the LLD
documents upon the advice of State Mission Team/SPMU.
Application Development and Unit Testing: The SI would develop the application in accordance with
the approved requirements specifications and design specifications and according to the approved
Project Plan; and carry out the Unit Testing of the application in accordance with the approved test
plans. The SI shall utilize the local language support available in CAS (State) and prepare necessary
configuration files for both CAS and additional functionalities/modules developed as part of CAS.
The SI would also implement the changes proposed in the Change/Reference document to Core
Application Software and carry out a thorough regression testing including running some of the
previously executed scripts for the functionality from the traceability matrix provided by NCRB/State.
The SI shall also develop a Data Migration Utility/application for the additional functionalities with all the
formats and tools to load the data into the state databases. This will migrate data from legacy systems of
the new modules to the CAS databases. This would be in addition to Migration utility developed by NIC
for migration of data as mandated by MHA requirements.
The user acceptance testing and fine-tuning of the application would be at State Headquarters premises.
Also, the key senior resources would continue to be based onsite at State Headquarter premises.
Configuration of CAS (State): The SI shall configure CAS (State) to the requirements of the State that
include but not limited to:
1. Configuring users
2. Configuring Police Stations / Higher Offices
The collection and validation of the data required for the configuration of the CAS (State) shall be the
responsibility of the SI.
Setup of Technical Environment at State Headquarters: The SI shall procure, setup and maintain the
required software and the infrastructure for systems testing, functional testing and User Acceptance
Testing; and training activities within State Headquarter premises; and for any other activities that may
be carried out of State Headquarter premises such as issue management (Issue Tracker), document
repository (configuration management tool), etc.
Regression, Integration, System and Functional Testing: After successful unit testing of all
components, the SI would conduct full-fledged integration testing, system testing and functional testing in
accordance with the approved Test Plans for the configured/customized CAS (State), additional
functionalities and also integration with CAS (Center) and external agencies. This would include
exhaustive testing including functional testing, performance testing (including load and stress), scalability
testing and security testing. Functional testing will be led by the SI’s experts.
A thorough regression testing should be conducted for those functionalities identified in

Change/Reference document to provide a general assurance that no additional errors have cropped up
in the process of addressing the customizations and/or Extensions. Customized CAS (State) Integrations
with CAS (Center) and with any external agencies should be thoroughly tested.
Making all necessary arrangements for testing including the preparation of test data, scripts if necessary
and setup of test environment (across multiple platforms) shall be the responsibility of the SI.
The SI along with State Mission Team/ SPMU should take the responsibility in coordinating with NCRB
and other external agencies for a smooth integration.
Test Reports: The SI shall create test reports from testing activities and submit to State Mission
Team/SPMU for validation
Test Data Preparation: The SI shall prepare the required test data and get it vetted by State Mission
Team/SPMU. The test data shall be comprehensive and address all scenarios identified in the test
cases. The SI should also prepare the test data for all required integrations including CAS (Center) and
external agencies.
User Acceptance Testing (UAT): Test Plans for UAT would be prepared by the SI in collaboration with
the State Mission Team /SPMU domain experts. The SI will plan all aspects of UAT (including the
preparation of test data) and obtain required assistance from State Headquarters to ensure its success.
State Mission Team/SPMU will assemble representatives from different user groups based on inputs
from the SI and would facilitate UAT. The SI would make the necessary changes to the application to
ensure that CAS successfully goes through UAT.
It is mandatory for SI to incorporate/consider test cases as part of UAT test cases for those customized
and/or extensions and/or configured functionalities identified from traceability matrix provided by NCRB /
State.
6.4 Infrastructure at the District Training Centers
District Training Centres have been set up in each of the District Headquarters by SCRB through
provision of the necessary infrastructure required to provide training to the identified district personnel.
Similarly, training infrastructure has been provided at SCRB Training Centre and 15 other Training
institutions in the state including Police Recruit Schools, Police Computer Communications Centre,
Police Training Headquarters and Police Academy. The details of infrastructure that have been
provided in each of these training institutions are mentioned below:
Infrastructure at Training Institutions in Tamil Nadu

District Training Centre
Item Qty
Desktop PCs 11
MFP 1
UPS (5 kVA) 1
LCD Projector and Screen mounted 1
Site Preparation (LAN) 1
Air Conditioner 1
Computer Table 10
Computer Chair 11
White Board 1
1.5 Tonne Split Air conditioner 1
Broad band connectivity with 1 year rent (with rent free land line) without 1
static IP
Mike and amplifier with two speaker 1
Plastic Chair 15
Digicam (10 MP) 1
External hard disk 1
Vacuum Cleaner 1
SCRB Training Centre
Item Qty
Desktop PCs 10
Laptop 6
MFP 1
UPS (5 kVA) 1
LCD Projector and Screen mounted 1
Site Preparation (LAN) 1
Air Conditioner 1
Computer Table 10
Computer Table (Big) 1
Computer Chair 11
Book Shelves 1
White Board 1
LCD 50 inch TV 1
Other State Training Institutes
Item Qty
Desktop computers 20
Laptop 1
High end Server 1
External hard Disk (500 GB) 1
Multifunction Printer 1
UPS (5 KVA) 2
LCD Projector and screen mounted 1
Air Conditioner (Split 2 ton) 1
Computer Table 21
Computer Table (Big) 1
Computer Chair 21
Book Shelves 1
Electronic Clock 1
Biometric Device 1
White Board 1
Site preparation (LAN) 1
6.5 Site Preparation at Police Stations and Higher Offices
The SI is expected to prepare the client sites for setting up the necessary client site infrastructure. Site
preparation at Police Stations & Higher Offices will include but not limited to:
a) Provision of Local area network (LAN cables, LAN ports, etc.)
b) Provision of computer furniture for Police Stations
c) Ensure adequate power points in adequate numbers with proper electric-earthling
d) Earthing and electric cabling as required at the site
In addition to the above Supply and fixing of furniture like computer tables, chairs and other item shall
be carried out to ensure successful site preparation and installation of CCTNS at every access location.
Site Preparation shall cover all the activities necessary to enable the Police Station to setup the client
side infrastructure and operate on CCTNS. The SI would have to do site preparation for the client site
locations and additional locations, requirements of which are described in Annexure-XI
6.6 Infrastructure at the Client Side Locations
The premises for offices will be provided by the department at respective locations. The list of Police
Stations, Sub-divisions, and other locations where the infrastructure is required is provided under the
Geographical Scope Section. SI shall procure the CCTNS infrastructure required at the locations
statewide.
At each such location the following shall be carried out.
1. Supply of the hardware, software, networking equipments, UPS, inverter to the location
as per the requirements
2. Redundant Network Connectivity - Ensuring last mile connectivity and testing. (At some
locations SWAN may be available. SI shall ensure there is redundancy in the
connection)
3. Installation, Testing and Commissioning of UPS, Inverter
4. Physical Installation of Desktops, Printer, Scanner, MFD, Switch- Connecting
peripherals, devices, Plugging in
5. Operating System Installation and Configuration
6. Installation of Antivirus and other support software if any
7. Configuring the security at the desktops, switch and broadband connection routers
8. Network and browser Configuration
9. Test accessibility and functionality of CCTNS application from the desktops
10. Ensuring all the systems required are supplied, installed, configured, tested and
commissioned and declaring the site to be operational.
11. In addition to the above supply and fixing of furniture like computer tables, chairs
and other items shall be carried out to ensure successful site preparation and installation
of CCTNS at every location
CCTNS application will be accessed and used at various access locations across the state like
Police Stations, Sub Division office, District Office and other higher offices. The Bill of Materials for
client site locations and additional locations are described in Annexure-III and IV respectively.
6.7 Network Connectivity for PS & Higher Offices
The WAN connectivity for the CCTNS project will be provided by BSNL through MPLS VPN
connectivity at select offices till district headquarters level and VPN on Broadband for rest of the offices
beyond district. However, SI will be responsible for setting up and maintenance of LAN at the individual
offices.
The SI shall provide the connectivity to the Police Stations / Higher Offices in coordination with BSNL.
Guidelines on Network architecture and details provided by BSNL with respect to connectivity are
provided in Annexure-VII.
The scope of network connectivity and the technical bill of materials are provided in Annexure-VII and
VIII respectively.
6.8 IT Infrastructure at the Data center and Disaster Recovery Center
The SI shall provide system integration services to procure and commission the required software and
infrastructure at the State Data Centre and Disaster Recovery Centre, deploy the configured and
customized CAS (State), additional modules developed, and integrate with CAS (Centre) and any
External Agencies as provided in the functional scope.
The SI shall be completely responsible for the sourcing, installation, commissioning, testing and
certification of the necessary software licenses and infrastructure required to deploy the Solution at the
State Data Centre and at the Disaster Recovery Centre (DRC).
CAS (State) will be developed in FOSS stack by NIC. NIC is also expected to develop interface to
enable data transfer between CAS State and CAS Centre. SI shall procure all the necessary
underlying solution components required to deploy the CAS (State) solution for the State.
Tamil Nadu State Data Centre would be the premises for the Primary Data Centre (DC) which would
host the solution. The corresponding Disaster Recovery Centre (DRC) would be positioned at Kerala
SDC, Trivandrum. The SI would work with BSNL to provide connectivity between the DC and DRC and
also provide connectivity from DC to NCRB Data Centre. The SI is responsible for sizing the hardware to
support the scalability and performance requirements of the solution. The SI shall ensure that the
servers and storage are sized adequately and redundancy is built into the architecture that is required to
meet the service levels mentioned in the RFP.
The SI shall be responsible for the sizing of necessary hardware and determining the specifications of
the same in order to meet the requirements of State.
SI shall provide a Bill of Material that specifies all the hardware, software and any additional networking
components of solution for the State Data Centre and DRC, in detail so as to facilitate sizing of common
Data Centre and DRC infrastructure such as Racks, Power and Cooling, Bandwidth among other
components. The common DC and DRC infrastructure shall be provided by State.
SI shall ensure that effective Remote Management features exist in solution so that issues can be
addressed by the SI in a timely and effective manner; and frequent visits to Data Centre /DRC can be
avoided.
After commissioning and testing of the entire system at State Data Center / DRC, the SI shall support the
State in getting the system certified by a 3rd party agency identified by State.
The following common data Centre services will be available to the SI through the Data Centre Operator
/ Data Centre Service Provider (DCO):
1. Power and Cooling
2. UPS, Inverter Back-up
3. Common Firewall
4. Fire prevention
5. Physical security & Surveillance
6. Network Operation Centre
7. Data Centre Physical Maintenance and Support
The SI is responsible for the below at the Data Centre / DRC:

1. Racks
2. Servers (Web, Application, Database, Backup, Antivirus, EMS, etc.)
3. Enterprise Management System (EMS) Licenses
4. Licenses for Compliance Management, Web Access Management, Privileges Users
Management for Server Access Control
5. Antivirus Software
6. SAN Storage
7. Tape Library
8. Separate VPN for CCTNS Servers
9. All necessary software components including but not limited to Operating System, Backup
Software, and SAN Storage Management Software
10. IT Management of CCTNS Servers
SI shall procure licenses for the EMS tool that monitors / manages the entire enterprise wide application,
infrastructure and network related components. The SI shall also deploy a backup software to
periodically backup all data and software.
The indicative specifications for the Web Server, Application Server, Database Server and Networking
components are provided in Annexure-VII.
6.9 Data Digitization & Data Migration
Data Migration
Migrating the data from the other systems/manual operations to the new system will include identification
of data migration requirements, collection and migration of user data, collection and migration of master
data, closing or migration of open transactions, collection and migration of documentary information, and
migration of data from the legacy systems.
The SI shall perform the data digitization & migration from manual and/or the existing systems to
the new system. The Data digitization & migration to be performed by the SI shall be preceded by an
appropriate data migration need assessment including data quality assessment.
The Data migration strategy and methodology shall be prepared by SI and approved by State. In case
these have already been prepared by the SPMC, the SI can take the SPMC’s documents as inputs and
add / modify as necessary. Though State is required to provide formal approval for the Data Migration
Strategy, it is the ultimate responsibility of SI to ensure that all the data sets which are required for
operationalization of the agreed user requirements are digitized or migrated.
Any corrections identified by SCRB, Tamil Nadu, during Data Quality Assessment and Review, in the
data digitized/ migrated by SI, shall be addressed by SI at no additional cost to Tamil Nadu Police. So far
as the legacy data is concerned, they are either available as structured data in the IT systems that are
currently used by Tamil Nadu Police for related work or in the form of paper documents (Cases
Documents and Police Station Registers). Almost all of such data items relevant for a Police Station are
maintained at the same Police Station.
Data Migration Requirements
i. Since there could be structural differences in the data as stored currently from the new
system there should be a mapping done between the source and target data models
that should be approved by the Nodal Officer, CCTNS
ii. Carry out the migration of legacy electronic data
iii. Carry out the migration of the data available in the existing registers, reports, case
files, etc.(Physical Copies)
iv. Scan images and pictures within the case file in color and store them in the digital
format.
v. Provide checklists from the migrated data to State Nodal Officer for verification, including
number of records, validations (where possible), other controls / hash totals. Highlight
errors, abnormalities and deviations.
vi. Incorporate corrections for the errors discovered during verification process, as
proposed
vii. Get final sign off from State Nodal Officer/ Empowered Committee for migrated /
digitized data
viii. At the end of migration, all the data for old cases and registers must be available in the
new system
Scope of Data Migration: The state requirements for data migration can be classified into 2 types:
a. Migrate Legacy data from legacy State Specific Applications to CAS( State) database
using the Migration Tool to be provided by NIC
b. Transfer data from CAS (State) database to CAS (Centre) in the prescribed format using
the Migration Tool to be provided by NIC
Recommended Methodology of Data Migration: Data migration methodology will comprise the
following steps, explained as below. However this is just a guideline for data migration effort and the SI
will be required to devise his own detailed methodology and get it approved by State Nodal Officer.
1. Analysis
Analysis of the legacy data and its creation, conversion, migration and transfer to the proposed new
data base schema will be started during the scoping phase and shall take a parallel path during the
design and development phase of the application. It will cover the following steps:
a. Analyze the existing procedures, policies, formats of data in lieu of the new proposed
system to understand the amount of the data and the applicability in CCTNS
b. Write a specification to create, transfer and migrate the data set
c. Document all exceptions, complex scenarios of the data
d. This phase will generate the specification for Data Take–On routines
2. Transformation
Transformation phase can be commenced after integration testing phase. It will entail the following
steps:
a. Identify the fields, columns to be added/deleted from the existing system
b. Identify the default values to be populated for all ‘not null’ columns
c. Develop routines to create (Entry if any by data entry operators), migrate, convert the
data from hard copies, old database (if any), computer records to the new database
d. Develop test programs to check the migrated data from old database to the new
database
e. Test the migration programs using the snapshot of the production data
f. Tune the migration programs & iterate the Test cycle
g. Validate migrated data using the application by running all the test cases
h. Test the success of the data take-on by doing system test
3. Data Take–On
Take–On phase will be initiated when the proposed solution is ready to be deployed. It will entail the
following steps:
a. Schedule data transfer of the computerized data that has been newly created by the
data entry operators based on the hard copy records.
b. Schedule data transfer of the existing digital data in the proposed new format
c. Migrate the data from an old system (legacy) to the envisaged database
d. Test on the staging servers after the data take-on with testing routines
e. Migrate from staging servers to production servers
f. Deploy and rollout the system as per the project plan
Additional Guidelines for Data Migration
1. SI shall migrate/convert/digitize the data at the implementation sites of State.

2. SI shall formulate the “Data Migration Strategy document” which will also include internal
quality assurance mechanism. This will be reviewed and signed–off by State prior to
commencement of data migration.
3. SI shall incorporate all comments and suggestions of State in the Data Migration Strategy
and process documents before obtaining sign–off from State.
4. SI shall perform mock data migration tests to validate the conversion programs.
5. SI shall ensure complete data cleaning and validation for all data migrated from the
legacy systems to the new application.
6. SI shall validate the data before uploading the same to the production environment.
7. SI shall generate appropriate control reports before and after migration to ensure
accuracy and completeness of the data.
8. SI shall convey to State in advance all the mandatory data fields required for functioning
of the proposed solution and which are not available in the legacy systems and are
required to be obtained by State.
9. In the event State is unable to obtain all the mandatory fields as conveyed by SI, SI shall
suggest the most suitable workaround to State. SI shall document the suggested
workaround and sign-off will be obtained from State for the suggested workaround.
10. SI shall develop data entry programs / applications that may be required for the purpose
of data migration in order to capture data available with / obtained by State in non –
electronic format.
11. SI shall conduct the acceptance testing and verify the completeness and accuracy of the
data migrated from the legacy systems to the proposed solution.
12. State may, at its will, verify the test results provided by SI.
Data Digitization
In addition to the data migration SI would also digitize the historical data (covering the last 10 years).
The historical data to be digitized would include crime (case/incident) data, criminals’ data, the
data from the 7 IIFs and relevant historical information parameters/data used to generate registers
and reports. The unit of data digitization shall be one case file. Each case file shall consist of
information pertaining to all 7 IIFs, information parameters relevant to generate specific registers from
that case file and information parameters relevant to generate specific reports from that particular
case file.
Scope of Data Digitization: The state requirements for digitization can be classified into 2 types:
a. Digitization of Case Files: The following number of records pertaining to case files
maintained at Police Stations across the state should be digitized
S.No Registers/Form Name Number of Records

1 Number of Case Files(All types) 34,84,815
b.Digitization of Registers: The following registers maintained at different offices should be

digitized on a page basis. The mode of digitization could be data entry of scanning and the
SI would have to digitize the specific records in the specified mode. The list of registers to be
digitized across offices is mentioned below:
S.No Office Registers/Form Name Number of Type

Pages
1 DPO/CPO/Chief Sanctioned strength 10,000 Data Entry
Office/Special Permanent Estt. Register
Units Temporary Estt. Register
2 Post Sanction G.O.s 10,000 Scanning
3 Personnel Data 10,00,00 Data Entry
Service Book
4 M.T.Register 12,000 Data Entry
5 Vehicle Sanction G.O.s and 15,000 Scanning
allotment order
6 Personal files 2,50,000 Scanning
7 Line Hut, Land / Building 10,000 Data Entry
Registers
8 Land / Building - Sanction 10,000 Scanning
G.O.s

Pages
9 Govt. Property Register for 10,000 Data Entry
Furniture, Equipments, Arms
and Ammunitions
10 Long Rolls 25,00,000 Scanning
11 Recorded Disposals 25,00,000 Scanning
12 R.Dis / D.Dis only 10,000 Scanning
13 Police Stations FIR Index 9,00,000 Data Entry
14 Crime Abstract Data Entry
15 Part I 3,00,000 Data Entry
16 Part II 2,000 Scanning
17 Part III 1,05,000 Data Entry
18 Part IV 30,000 Data Entry
19 15,00,000 Scanning
20 Part V 45,000 Data Entry
21 13,50,000 Scanning
22 General Conviction Register 1,40,000 Scanning
23 Station Information Register 30,000 Scanning
24 Circle Office Circle Information Register 30,000 Scanning
25 Circle Map 300 Scanning
26 Government Property Register 600 Data Entry
27 SDO/Range Information Register 25,000 Scanning
28 Office Govt. Property Register 250 Data entry
29 GCR [Grave Crime Report] 25,000 Data entry
30 Explosive Register 416 Data entry
31 Cracker Shop Register 416 Data entry
32 P.R. Register 4,160 Data entry
33 SP Camp Office Correction Nos.1 to 4 to the Scanning
Records distribution list of officers using
the Civil Cipher System –
1981 Copy No.1457.
34 Cryptographic Regulations, Scanning
Part-IV-Miscellaneous Crypto
Systems Vol.-I –Civil Cipher.
Copy No.1739.
35 Consolidated General Scanning
instructions for the Civil Cipher
System (CCS) Part-I For all
sholders. Copy No.1641.
36 Rules and instructions for the Scanning
protection of the president
When in Delhi and on tour
1977 – Copy No.231.
37 State War Book (Tamil Nadu) Scanning
Revised in 1996 PREFACE
AND APPENDICES. Copy

Pages
No.70.
38 Guidelines for personal Scanning
security, Escort personnel and
drivers, driving vehicles of
persons with security Threats
and Check lists for the
Security arrangements for the
Prime Minister and Chief
Minister of Tamil Nadu. Copy
No.29.
39 Circular Memorandum in C.no. Scanning
SCA 1 No.8430 Dated:-
13.08.1999 for VVIP Security –
Booklet on Security
arrangements to VVIPs/VIPs.
Copy No.29.
40 Tamil Nadu Railway Protection Scanning
Scheme-2003. Copy No.40.
41 Social Justice CID, Chennai – Scanning
Manual for use in the Districts
– Copy No.000011.
42 Security Arrangements for Scanning
protection of individuals
(YELLOW BOOK) Copy
No.1327.
43 Rules and Instructions for the Scanning
Protection of the Prime
Minister When on Tour and
Travel. Copy No.459.
44 Circular Memorandum in C.no. Scanning
C1 No. 5500/X/2006/C Dated:-
29.03.2006, AND OVERVIEW
OF THE LEFT WING
EXTREMISM – 2005. Copy
No.58.
45 Distribution List of Officers Scanning
Using the Civil Cipher System
– 2004. Copy No.525
46 Government Mobile phone Scanning
Nokia – Model No.6610.
47 CIVIL CIPHER SYSTEM – Scanning
Introduction of Tamil Nadu
State Keyword No.1/2007 of
the Civil Cipher System from
1.6.2007.
48 CIVIL CIPHER SYSTEM – Scanning
Introduction of “Tamil Nadu
State Keyword No.1/2008 of
the Civil Cipher System from
01.06.2008.
49 The Tamil Nadu Political who’s Scanning
who – 2005.

Pages
50 New Southern Railway Strike Scanning
Scheme-2007 ( Copy No. 483)
51 DIN series documents No.2 & Scanning
3 of WAR WATCHING
STATIONS (COPY NO. 157 &
207)
52 A Study of security Scanning
arrangements for protection of
individuals. (Copy No.734
Note: SCRB reserves the right to consider in part or omit all the requirements mentioned under
additional locations to be covered
6.10 Migration of Data from CIPA and CCIS to CAS (State)
The SI is also responsible for migrating the Police Stations and Higher Offices currently
operational on CIPA and CCIS to CAS (State) as part of the CCTNS implementation in the State. SI
shall validate the data in the CIPA systems and migrate the data to CCTNS. In addition, the State may
also decide to cover other applications currently being used under this data migration and
integration effort if felt necessary.
Detailed list of Police Stations running CIPA along with the data to be migrated is enclosed as
Annexure-IX for the list of CIPA Police Stations
6.11 Capacity Building
The following steps are postulated for identifying trainers for providing capacity building to the identified
work force involving officials across all levels:
Identification of Trainers (Internal)

SCRB, Tamil Nadu shall identify qualified Trainers with relevant IT experience and training
competency within each District Mission Team and State Mission Team who will be directly
trained by the System Integrator and will be responsible for interfacing with the System Integrator for all
the Capacity Building Initiatives. These Trainers will be responsible for implementing the Capacity
Building interventions beyond the scope of the System Integrator.
Identification of Trainers (Police Training Colleges)

SCRB shall identify the Trainers within each of the Police Training Colleges in the State who will
be directly trained by the System Integrator. These trainers will be responsible for including training on
CCTNS within the training college curriculum and impart the training on CCTNS to the new recruits and
current personnel (refresher training) at the Police Training Colleges.
Identification of Trainees
Based on the nature of their responsibilities and their requirements from CCTNS, police staff can be
classified into the following categories for training purposes:
 Group I:
o Identify the key senior officers (ADGP, IG, DIG) responsible for Crime, Law and
Order, who are directly impacted by the CCTNS with respect to receiving/analyzing
the reports through CCTNS.
o Role-based training will be carried out for these officers at suitable location in the
State Headquarters by the System Integrator
 Group II:
o Identify the key officers (IG, DIG, SP, DCP, ACP) in charge of a
zone/range/district/sub-division who are directly impacted by the CCTNS with respect
to reviewing the police station performance through CCTNS, reviewing the
reports generated by the system, carrying out the required analysis using CCTNS
and providing the necessary guidance to the officers at the cutting edge.
o Role-based training will be carried out for these officers at suitable location in the
State Headquarters and respective Districts/Commissionerates by the System
Integrator
 Group III:
o Identify the key officers (SHO, SI) in the Police Stations and Higher Offices who
will use CCTNS for police station management, filing the necessary investigation
forms, and utilize the basic and advance search features of CCTNS to facilitate their
investigation process.
o In addition to the computer awareness training, role-based training will be carried out
for these officers at District Training Centers in the respective Districts/
Commissionerates by the System Integrator
o Refresher training can be carried out by the internal trainers subsequent to the
System Integrator trainings
 Group IV:
o Identify at least 2-3 key officers/constables (Station Writers, Court Duty, Head
Constables, Constables,) in each of the Police Stations and Higher Offices who will
use CCTNS for capturing the data/investigation forms, generating the reports and
utilize the basic and advance search features of CCTNS to service the general
service requests and aid in investigation process.
o Role-based training will be carried out for the identified officers at District Training
Centers in the respective Districts/Commissionerates by the System Integrator
o Refresher training, subsequent training to the remaining officers/constables in the
Police Station and Higher Offices can be carried out by the internal trainers
subsequent to the System Integrator trainings
 Group V:
o Identify 2 constables for each Sub-division/Circle Office that can provide the basic
computer operation support to the police stations within the Sub-division/Circle.
o Technical training will be carried out for the identified constables at District
Training Centers in the respective Districts/Commissionerates by the System
Integrator
The main challenges to be addressed effectively by the SI are the geographically dispersed
trainee base, wide variability in education and computer proficiency and minimal availability of time.
The SI holds the responsibility for creation of a detailed and effective training strategy, user groups and
classifications, training plan and guidelines, detailed training material, training program designed
their delivery to the target groups.
The SI holds the responsibility for creation of training material, designing the training programs and
their delivery to the target group. The State SI shall be responsible for the following activities as part of
the End User and Train the Trainer Training:
Develop Overall Training Plan

SI shall be responsible for finalizing a detailed Training Plan for the program in consultation with SCRB,
Tamil Nadu covering the training strategy, environment, training need analysis and role based training
curriculum. SI shall own the overall Training plan working closely with the SCRB, Tamil Nadu Training
team. SI shall coordinate overall training effort.
Develop District-Wise Training Schedule and Curriculum

SI shall develop and manage the District-Wise training schedule in consultation with SCRB, Tamil
Nadu, aligned with the overall implementation roadmap of the project and coordinate the same with
all parties involved. Training schedule shall be developed by solution and shall be optimized to reduce
business impact and effective utilization of Training infrastructure and capacities. The training
curriculum for the CCTNS training program should be organized by modules and these should be
used to develop the training materials. The training curriculum outlines the mode of delivery, module
structure and outline, duration and target audience. These sessions should be conducted such that the
users of the application/modules are trained by the time the application “goes-live” in the District with
possibly no more than a week’s gap between completion of training and going live of modules.
Continuous reporting (MIS) and assessment should be an integral function of training. SI shall also
identify the languages to be used by the end-user for entering data and ensuring multi-language
training to the end users as per requirement.
Develop Training Material

Based on their needs and the objectives of CCTNS, training programs could be organized under the
following themes:
1. Role-based training on the CCTNS application – Basic and Advanced. This training
should be in a role based, benchmarked and standardized format, multi-lingual and lead
to learning completion and assessment. It should also allow for self-learning and
retraining. Training would include mechanism for demonstration using
audio/video/simulated/demo practice exercises and evaluation of trainees.
2. “Train the Trainer” programs, where members of the police staff would be trained to
enable them to conduct further training programs, thus helping build up scalability in the
training program and also reducing the dependency on external vendors for training.
3. System Administrator training: a few members of the police staff with high aptitude
would be trained to act as system administrators and troubleshooters for CCTNS.
4. Customization of the Training Manuals, User Manuals, Operational and Maintenance

Manuals provided along with the CCTNS CAS Software
5. Design and development of the Training Manuals, User Manuals, Operational and
Maintenance Manuals for the modules developed at the State level.
In cases where the training material may be made available by MHA/NCRB, it is the SI’s
responsibility to ensure the relevance of the material to the State, customize if necessary and own up
the delivery and effectiveness.
SI shall ensure that the training content meets all the objectives of the training course. The
material shall be developed in English and Tamil. SI shall also develop the training material for delivery
through Computer Based Training, Instructor Led Training, Online User Material/Help Manuals and Job
Aids.
SI shall provide detailed training material providing step-by-step approach in soft and hard copies to all
police stations and offices for reference.
Deliver Training to End Users

SI shall deliver training to the end users utilizing the infrastructure at the District Training Centers. Role-
based training for the Senior Officers will be carried out for at suitable location in the State
Headquarters by the System Integrator.
SI shall also impart simulated training on the actual CAS (State) with some real life like database. The
SI should create case studies and simulation modules that would be as close to the real life scenario as
possible. The objective of conducting such trainings would be to give first had view of benefits of using
CAS system. Such specialized training should also be able to provide the participant a clear
comparison between the old way of crime and criminal investigation against the post CCTNS
scenario. This training needs to be conducted by the SI at the very end when all the other trainings
are successfully completed. This training may seem similar to role play training mentioned in the
section above however, in this simulated training, the SI would ensure that the IO’s are provided an
environment that would be exactly similar at a Police Station post CAS (State) implementation.
Most of the training would be an Instructor-Led Training (ILT) conducted by trained and qualified
instructors in a classroom setting. To maintain consistency across CCTNS trainings, standard
templates should be used for each component of a module.
An ILT course will have the following components:

 Course Presentation (PowerPoint)
 Instruction Demonstration (CAS - Application training environnent)
 Hands-on Exercices (CAS - Application training environnent)
 Application Simulations: Miniature version of CAS Application with dummy data providing
exposure to the IOs to a real life scenario post implementation of CAS
 Job Aids (if required)
 Course Evaluations (Inquisition)
In addition to the ILT, for the modules that may be more appropriate to be conducted through a
Computer Based Training (CBT), a CBT should be developed for them. CBT should involve training
delivered through computers with self instructions, screenshots, simulated process walk- through and
self assessment modules.
Select set of police staff with high aptitude group and/or relevant prior training, are to be imparted with
the training/skills to act as system administrators and also as troubleshooters with basic systems
maintenance tasks including hardware and network.
Deliver Training to Trainers (Internal and Trainers from the Training Colleges)
SI shall help SCRB, Tamil Nadu in assessing and selecting the internal trainers as well as the
trainers at training colleges who can conduct the end user training subsequent to the training by the SI.
SI shall coordinate the ‘Train the Trainer’ session for the identified trainers to ensure that they have the
capability to deliver efficient training.
In addition to the training delivered to the end-users, the trainers should also be trained on effectively
facilitate and deliver training to end users. Also, it is advisable to always run pilots for any training
program before deployment. This training will hence serve as the pilot and as a training session for
trainers as well. In addition the end-user training sessions, ToT training will consist of three segments:
1. The first segment will be set of workshops covering effective presentation skills and
coaching techniques and discussing the benefits and structure of the trainer model.
2. The second segment will be the formal CCTNS training which will consist of all modules of
CCTNS relevant for their role.
3. The third segment will be a teach-back session where trained trainers will present course
content and receive feedback regarding content, flow, and presentation techniques. This will
also include a feedback session where trainers can provide feedback on the training materials,
flow, comprehension level, and accuracy.
Training Effectiveness Evaluation

SI shall evaluate the effectiveness of all end users trainings using electronic or manual surveys. SI
shall be responsible for analyzing the feedback and arrange for conducting refresher training, wherever
needed.
State will periodically monitor the training effectiveness through the performance metrics and Service
levels and the SI shall comply with the same.
SI shall help the State with complete Change Management exercise needed to make this project a
success. In fact Change Management will have to subsume ‘training’ as a key enabler for change.
Following outlines the responsibilities of SI with respect to designing and implementation of change
management plan for the Project.
Change management
Stakeholder groups can be categorized into below categories, based on their influence and role in
managing the change and making it successful:
 Group I: Identify the key senior officers (ADGP, IG, DIG) responsible for Crime, Law
and Order, who are directly impacted by the CCTNS with respect to receiving/analyzing
the reports through CCTNS.
 Group II: Identify a few of the key officers (IG, DIG, DCP, ACP, SP) in charge of
a zone/range/district/sub-division who are directly impacted by the CCTNS with respect
to reviewing the police station performance through CCTNS, reviewing the reports
generated by the system, carrying out the required analysis using CCTNS and providing
the necessary guidance to the officers at the cutting edge.
 Group III: Identify a few of the key officers (SHO, SI,…) in the Police Stations and
Higher Offices who will use CCTNS for police station management, filing the necessary
investigation forms, and utilize the basic and advance search features of CCTNS
to facilitate their investigation process.
 Group IV: Identify a few of the key officers/constables (Station Writers, Court Duty,
Head Constables,etc.) in the Police Stations and Higher Offices who will use
CCTNS for capturing the data/investigation forms, generating the reports and utilize the
basic and advance search features of CCTNS to service the general service requests
and aid in investigation process.
Communication and Awareness

Communication & Awareness campaigns will be conducted throughout the duration of the
implementation of the CCTNS project across the State at Project, Program level as well as for
General awareness. SI shall work with the identified internal change agents (identified from the
District and State Mission Teams) for all the Communication and Awareness Programs. SI shall utilize
existing channels of communication and at the same time use innovative methods of communication
for effectiveness. SI should ensure that the communication messages are consistent, continuous and
easy to understand and wherever possible in Tamil using all available channels. SI shall align
communication content, timing and delivery to the deployment phases/plan of each solution.
S. Activities Details Frequency

No
1 Develop  SI shall prepare a detailed Once

detailed communication plan for the program
communication in line with the implementation timelines
plan of each solution
 SI shall ensure that all the
impacted audience is covered in
the communication plan and the
m ost appropriate mode of
communication is being used to deliver
the messages to the target audience
S. Activities Details Frequency

No
2 Develop  SI shall be responsible for developing the Recurring

Communication content for communication material in Activity
Content English and Tamil. over the
entire
 SI shall ensure that the communication is
duration of
simple, continuous and consistent.
the SI
3 Deliver  Prior to implementing the plan, the SI Recurring

Communication shall obtain the necessary sign-offs from Activity
Events State on the Communication Strategy & (once a
plan and make necessary changes as month)
recommended by State. over the
entire
 SI shall determine who needs to approve
duration of
communications prior to dissemination,
the SI
who is responsible for distributing the
message, and who is responsible for
ensuring that those accountable for
specific elements of the plan follow
through on their responsibilities.
 SI shall organize the communication
events or interventions for the target
audience.
• SI shall ensure consistency between
messages delivered via different
interventions, since the engagement of a
key individual stakeholder or stakeholder
group is an integrated effort, aiming at the
same objective.
Change Management Workshops

SI shall conduct Change Management workshops, build appreciation of change management and
develop change leadership across the stakeholder groups. SI shall design the necessary content
(reading material, presentations) in English and Tamil for the Change Management Workshops. SI
shall conduct at least three Change Management Workshops (minimum of one-day) in the State
Headquarters and at least one Change Management Workshop (minimum of one-day) all of the
Districts (at the District Headquarters) covering at least 3 officers/constables (SHO, SI/HC, and
Station Writer) from each police station in the district.
The SI is required to conduct the Change Management Workshops for all the identified Police
personnel in a phased manner in line with the overall implementation plan. These workshops
shall be conducted at the locations provided by the State. The workshop content & material shall be
designed with specific focus on the requirements of the personnel. SI shall conduct workshops for
each group of personnel in sync with the training plan and as part of the training module. SI is
required to provide the necessary material for the workshops including presentations, training material
etc in both soft and hard copy formats.
SI shall also associate and train the identified internal change agents (identified from the District and
State Mission Teams) during these workshops so that subsequent workshops can be conducted by
the internal change agents.
It is recommended that a change management team be formed to own, facilitate and execute change
management intervention. The change management structure will consist of a two-tier governance
structure, Viz., Top level governance structure – Steering committee and task force and Operational
Team
Change Management Organization
The Operational team would be entrusted with carrying our change management activities in the
districts. The team would comprise of change management experts, to be identified and deployed by
SI, District Mission Teams and Range DIG who would monitor the process and would be responsible
for the change management implementation in the concerned districts. There would be a Change
Management team of SI, one for each zone, which would be responsible for carrying out Change
management activities in all districts under the zone. The Operational team structure is shown in the
figure below:
Change Management Operational Team
Top Level Governance Committee: The top-level governance structure shall comprise the steering
committee and the task force:
Steering Committee
The strategic decision making will be carried out by the steering committee which will comprise the
Secretary of State Home Department and DGP.
Task Force
The task force would be responsible for monitoring the work of the operational team and taking
operational decisions as and when required.
Operational Structure: The operational level decision making as well as execution of the change
management initiative will be carried out by change management operational team which will comprise
the change management specialist as the head. The change management specialist will monitor the
committee and will supervise the work of communication lead and training lead.
Roles and responsibilities
The roles and responsibilities of the members with respect to Change Management interventions
implementation is described in the following table below:
Roles & Responsibilities (Change Management Strategy)
Committee Position name Role and Responsibilities

name
Change CM Steering  Take strategic decisions related to the project
Management Committee from change management standpoint
Steering Member  Take ownership of, manage, and implement the
committee vision for change management
 Clarify expectations from the various change
management phases. The expectations will
include matters related to scope, time and
deliverables
 Ensure that the project meets the goals and
expectations of the MHA by reviewing the project
milestones achieved on a periodic basis and
suggesting necessary modifications and course
corrections
 Influence and ensure that there is commitment
from the key stakeholders (such as Courts,
Passport Office) to the project
 Resolve any conflicts and issues that may arise
during the implementation of the change
management plan
 Identify the resources required for
implementation of various change management
interventions based on requests from the Task
Force and Operational Team.
Task Force Task force  Assist in execution of the vision for change
members management
 Regular monitoring of the progress of change
management implementation
deliverables
 Resolve any conflicts and issues that may arise

name
during the implementation of the change
management plan
 Report to Change Management Steering
Committee about progress made regarding
Change Management interventions
 Escalate those issues to Steering Committee
that may require strategic decision making
Change Change  Allocate resources to implement various
Management management change management interventions
Operational specialist1  The change management specialist would
Team identify the bottlenecks in the change
management roll out and identify the ways and
means to address the same
 Promote self-responsibility, agree on the
project scope, objectives and success criteria
with the change management team
deliverables
 Manage the operational risks arising during the
roll out of the change interventions.
 Undertake operational decisions related to the
project from change management standpoint
 Report to Range DIG and Task Force
periodically on progress made on change
management interventions
 Review the work with respect to the change
intervention, allocate responsibilities to the
change agents, review the progress on a day to
day basis
 Ensure that the facilitation and implementation
of the change interventions for each stakeholder
is carried out effectively within the planned time,
resources, budget as per the plan
 Coordinate with communication and training
leads to ensure dependencies across the
Services/ phases are identified and tasks are
1
Members would be part of the System Integrator

name
coordinated
 Prepare and send status progress reports to
the Range DIG periodically highlighting the
project progress, risks/ issues/ delays Implement
the decisions taken by the steering committee
and change management specialist
 Escalate difficulty in implementation of
interventions to Range DIG
Change Communication  Review the work programme with respect to the
management lead1 communication strategy and plan, allocate
committee responsibilities to the communication agents and
review the progress on a day to day basis
the change management specialist periodically
highlighting the project progress, risks/ issues/
delays
 Implement the decisions taken by the steering
committee and change management specialist in
coordination with district mission team
 Escalate difficulty in rolling out communication
plan and periodic status updates to Change
Management Specialist
Change Training lead1  Get buy in of all stakeholders to facilitate
management effective implementation of training plan
committee  Review the work project with respect to the
training interventions, allocate responsibilities to
the training agents and review the progress on a
day to day basis
 Ensure that the facilitation and implementation
of the training intervention for each stakeholder is
carried out effectively within the planned time,
resources, budget as per the plan
 Coordinate with communication and change
leads to ensure dependencies across the
Services/ phases are identified and tasks are
coordinated;
the change management specialist periodically
highlighting the project progress, risks/ issues/
delays and interventions required

name
 Implement the decisions taken by the steering
committee and change management specialist
 Escalate difficulty in rolling out training plan
and send periodic status updates to Change
Management Specialist
Change Training  Execute the assigned tasks and assist the
management agents1 training lead in ensuring successful
team implementation of the training related intervention
 Facilitating implementation of all the training
activities and reporting to the training lead
 Assist in development of training plan, training
schedule and training course content
 Responsible for creation of training material
either using in-house resources or outsourced
ones
 Assist in selection of vendor, trainers etc and
reviewing that the overall training related plan is
adhered to
 Facilitate conducting training program,
evaluating training effectiveness and creating
knowledge repository
 Responsible for facilitating training
interventions by working in collaboration with
change and communication agents
the training lead periodically
Change Communication  Execute the assigned tasks and assist the
management agents1 communication lead in ensuring successful
team implementation of the communication plan and
strategy
 Facilitate implementation of all the
communication interventions and reporting to the
communication lead
 Assist in preparation of communication content,
message design and other communication
related activity
 Responsible for creation of all communication
material either using in-house resources or
outsourced ones

name
 Assist in selection of vendor if required and
reviewing that the overall communication plan is
adhered to
 Facilitate communication interventions by
working in collaboration with training and change
agents
the communication lead periodically
6.12 Handholding Support
The System Integrator will provide one qualified and trained person per police station for a period of six
months to handhold the staff in the police station and ensure that the staffs in those police stations are
able to use CCTNS on their own by the end of the handholding period. SI must provide the project team
as per details and eligibility qualifications given in this RFP.
Handholding and project support would be required only after the successful commissioning of Core
Application (CAS) State and the necessary infrastructure and completion of capacity building and
change management initiatives in respective districts. Information of all Police locations regarding
engagement of handholding personnel has been provided in Geographical scope in this RFP.
Code of Conduct for Handholding personnel at Police Stations are as mentioned below:
 The person to be engaged by SI for Handholding support should work as six days per week.
 Handholding personnel should give 100% availability on all working days.
The qualification required for handholding personnel is described in Vol II, Section 5.11
The scheduling and requirement for handholding personnel would be in line with the implementation
phases of the project roll out as described in Section 6.1.1
6.13 Requirement on Adherence to Standards
CCTNS system must be designed following open standards, to the extent feasible and in line with
overall system requirements set out in this RFP, in order to provide for good inter-operability with
multiple platforms and avoid any technology or technology provider lock-in.
Compliance with Industry Standards

In addition to above, the proposed solution has to be based on and compliant with industry standards
(their latest versions as on date) wherever applicable. This will apply to all the aspects of solution
including but not limited to design, development, security, installation, and testing. There are many
standards that are indicated throughout this volume as well as summarized below. However the list
below is just for reference and is not to be treated as exhaustive.
Portal development W3C specifications
Information access/transfer SOAP, HTTP/HTTPS

protocols
Interoperability Web Services, Open standards
Photograph PNG (minimum resolution of 640 x 480

pixels)
Scanned documents TIFF (Resolution of 600 X 600 dpi)
Biometric framework BioAPI 2.0 (ISO/IEC 19784-1:2005)

specification
Finger print scanning IAFIS specifications
Digital signature RSA standards
Document encryption PKCS specifications
Information Security CCTNS system to be ISO 27001 certified
Operational integrity & security CCTNS system to be ISO 17799

management compliant
IT Infrastructure management ITIL / EITM specifications
Service Management ISO 20000 specifications
Project Documentation IEEE/ISO specifications for

documentation
The SI shall adhere to the standards published by the Department of Information Technology,
Government of India.
6.14 Support to Acceptance Testing, Audit and Certification
The primary goal of Acceptance Testing, Audit & Certification is to ensure that the system meets
requirements, standards, and specifications as set out in this RFP and as needed to achieve the desired
outcomes. The basic approach for this will be ensuring that the following are associated with clear and
quantifiable metrics for accountability:
1. Functional requirements
2. Test cases and Requirements Mapping
3. Infrastructure Compliance Review
4. Availability of Services in the defined locations
5. Performance and Scalability
6. Security / Digital Signatures
7. Manageability and Interoperability

8. SLA Reporting System
9. Project Documentation
10. Data Quality Review
As part of Acceptance testing, audit and certification, performed through a third party agency, State shall
review all aspects of project development and implementation covering software, hardware and
networking including the processes relating to the design of solution architecture, design of systems and
sub-systems, coding, testing, business process description, documentation, version control, change
management, security, service oriented architecture, performance in relation to defined requirements,
interoperability, scalability, availability and compliance with all the technical and functional
requirements of the RFP and the agreement. Here it is important to mention that there may be two
agencies selected by State, one for audit & certification of security and control aspect of the system and
the other for audit & certification of overall application software.
State will establish appropriate processes for notifying the SI of any deviations from defined
requirements at the earliest instance after noticing the same to enable the SI to take corrective action.
Such an involvement of the Acceptance Testing & Certification agencies, nominated by State, will not,
however, absolve the operator of the fundamental responsibility of designing, developing, installing,
testing and commissioning the various components of the project to deliver the services in perfect
conformity with the SLAs.
Following discusses the acceptance criteria to be adopted for system as mentioned above:
1. Functional Requirements Review

The system developed/customized by SI shall be reviewed and verified by the agency against the
Functional Requirements signed-off between State and SI. Any gaps, identified as a severe or critical
in nature, shall be addressed by SI immediately prior to Go-live of the system. One of the key inputs
for this testing shall be the traceability matrix to be developed by the SI from system. Apart from
Traceability Matrix, agency may develop its own testing plans for validation of compliance of system
against the defined requirements. The acceptance testing with respect to the functional requirements
shall be performed by both independent third party agency (external audit) as well as the select
internal department users (i.e. User Acceptance Testing).
2. Infrastructure Compliance Review

As mentioned above, an independent third party agency (external audit) shall perform the Infrastructure
Compliance Review to verify the conformity of the Infrastructure supplied by the SI against the
requirements and specifications provided in the RFP and/or as proposed in the proposal submitted by
SI. Compliance review shall not absolve SI from ensuring that proposed infrastructure meets the SLA
requirements. The SI would provide the specifications of the hardware supplied which would be checked
against the actual hardware supplied and hardware as described in the Bill of Materials in this volume of
RFP.
3. Security Review
The software developed/customized for system shall be audited by the agency from a security & controls
perspective. Such audit shall also include the IT infrastructure and network deployed for system.
Following are the broad activities to be performed by the Agency as part of Security Review. The
security review shall subject the system for the following activities:
a. Audit of Network, Server and Application security mechanisms
b. Assessment of authentication mechanism provided in the application
/components/ modules
c. Assessment of data encryption mechanisms implemented for the solution
d. Assessment of data access privileges, retention periods and archival
mechanisms
e. Server and Application security features incorporated etc
4. Performance
Performance is another key requirement for system and agency shall review the performance of the
deployed solution against certain key parameters defined in SLA described in this RFP and/or
agreement between State and SI. Such parameters include request-response time, workflow
processing time, concurrent sessions supported by the system, Time for recovery from failure,
Disaster Recovery drill etc. The performance review also includes verification of scalability provisioned in
the system for catering to the requirements of application volume growth in future.
5. Availability
The system should be designed to remove all single point failures. Appropriate redundancy shall be built
into all the critical components to provide the ability to recover from failures. The agency shall perform
various tests including network, server, security, DC/DR fail-over tests to verify the availability of the
services in case of component/location failures. The agency shall also verify the availability of services to
all the users in the defined locations.
6. Manageability Review
The agency shall verify the manageability of the system and its supporting infrastructure deployed using
the Enterprise Management System (EMS) Licenses procured by the SI. The manageability
requirements such as remote monitoring, administration, configuration, inventory management, fault
identification etc. shall have to be tested out.
7. SLA Reporting System

SI shall procure Licenses for the Enterprise Management System (EMS) deployed at Tamil Nadu State
Data Centre and shall develop any additional tools required to monitor the performance indicators listed
under SLA prescribed in this RFP. The Acceptance Testing & Certification agency shall verify the
accuracy and completeness of the information captured by the SLA monitoring system implemented by
the SI and shall certify the same. The EMS deployed for system, based on SLAs, shall be configured to
calculate the monthly transaction-based payout by State to SI.
8. Project Documentation
The Agency shall review the project documents developed by SI including requirements, design, source
code, installation, training and administration manuals, version control, etc. Any issues/gaps identified by
the Agency, in any of the above areas, shall be addressed to the complete satisfaction of State.
9. Data Quality
The Agency shall perform the Data Quality Assessment for the Data digitized/ migrated by SI to the
system. The errors/gaps identified during the Data Quality Assessment shall be addressed by SI before
moving the data into production environment, which is a key mile stone for Go-live of the solution.
6.15 Scope of Services during Post-Implementation Phase
The SI shall be responsible for the overall management of the system including the application and
entire related IT Infrastructure. The details of the post implementation support services are provided as
an Annexure V to this RFP. SI shall procure and deploy an EMS License that monitors / manages the
entire enterprise wide application, infrastructure and network related components.
SI shall provide the Operations and Maintenance Services for period of 5 years following the
deployment and “Go-Live” of the solution in the State. In case each District is declared as “Go-Live” at
different instances during the project roll-out, the Operations and Maintenance Services for the District
will start following the deployment and “Go-Live” of the solution in the District and SI shall continue
to provide the Operations and Maintenance Support for a period of 5 years following the deployment
and “Go-Live” of the solution in the last District.
6.16 Go-Live
Go-Live is defined as a milestone in the implementation plan which requires Completion and Acceptance of
the following activities in at least 85% of the Police Stations / Higher Offices in each of the Districts
targeted under the Phase
 Data Migration / Digitization

 Capacity Building Program covering the targeted personnel
 Change Management Initiatives covering the targeted personnel
 Site Preparation
 Delivery and Commissioning of Client Side Infrastructure
 Networking
 Commission of the Configured, Customized, and Extended CAS (State)
 The PS / HO have completely migrated to the new application and the police station and the
higher offices’ personnel are successfully conducting the intended functions through the
application
6.17 Handover and Exit Management
a) Exit management shall involve the complete handover of the CCTNS to the team identified by
the SCRB, Tamil Nadu, which would take care of CCTNS project after the tenure of the System
Integrator ends. Exit Plan has to be submitted by the System Integrator. Exit procedure needs to
be carried out as per approved Exit Plan. Exit Plan would include transfer of Intellectual property
rights, transfer of assets, knowledge transfer and smooth transition to new team selected by
SCRB, Tamil Nadu.
b) During the exit management period, the System Integrator shall use its best efforts to deliver the
services. Payments during the Exit Management period shall be made in accordance with the
Terms of Payment Schedule.
c) This Exit Management plan shall be furnished in writing to the SCRB, Tamil Nadu as part of the
Technical Proposal
d) SCRB, Tamil Nadu shall also provide all kind of technical support to designated agency while
transferring the project and hand hold the project for one month to enable designated agency
develop sufficient skills for smooth maintenance and operations of the project.
e) At the end of the contract period, the System Integrator shall transfer the ownership of all
equipments, Software etc in the Name of SCRB, Tamil Nadu and after transfer handover all the
equipments/software/Components supplied and installed under the project as per Purchase
order along with media, manuals, documentation to the SCRB, Tamil Nadu or its nominee in up
and running condition with a site wise Stock Registers.

7 Implementation and Roll-out Plan
Detailed Project Plan for Implementation and Roll-out is given below:

Detailed Project Plan
Phase Suggested Activities Responsibilities Time Line
(Month)
Pilot Phase - Setting up Data Centre
(T=Date of Installation and Testing of UPS SI T+3
Signing the Supply of the Hardware, Software, SI, NIC
Agreement) License & Networking equipments
Installation and Testing of Equipments SI, SPMU, SMT
Redundant Network Connectivity SI / BSNL
24*7 Support system in case of break SI
down
Setting up Disaster Recovery Centre T+3
Installation and Testing of UPS SI
Supply of the Hardware, Software, SI, NIC
License & Networking equipments
Installation and Testing of Equipments SI, SPMU, SMT
Redundant Network Connectivity SI / BSNL
24*7 Support system in case of break SI
down
Installation of CAS (State) of NIC SI, NIC T1=T+4
Customization of CAS (State) and CAS
(State) Integration with Identified
applications (T1 – Date of completion
of CAS State Rollout)
SRS preparation SI T1+1
Approval from SPMU & Department and SI, SPMU & T1+1
Change Incorporation in case of Department
suggestions Constituted
Committee
Development of Crime Analysis Suite SI & Department T2=T1+2
Constituted
Committee
Development of Knowledge Base Suite SI & Department T3=T2+2
Constituted
Committee
Development of Communication Suite SI & Department T4=T3+2
Constituted
Committee
Development of Constable Suite SI & Department T5=T4+1
Constituted
Committee
Development of Law & Order Suite SI & Department T6=T5+1
Constituted
Committee
Development of Traffic Suite SI & Department T7=T6+1
Constituted

(Month)
Committee
User Acceptance Testing SI, SPMU, SMT, T8=T7+2
DMT
Change Request SI, SMT, DMT
Final Implementation at 2 Pilot Districts, 2 SI, DMT, SMT T9=T8+1
Commissionerates, HQ and SCRB
Collection of feedback from users in Pilot SI, DMT T10=T9+1
Districts
Data Digitization/Data Migration
Analysis of Data to be digitized SI T+2
Collection & Consolidation of Data SI T+3
Data Digitization SI T+9
Data Validation & Re-entry SI T+10
Certification from Department about SI & Department T+11
authenticity of digitized data Assigned Official
Data Porting to the Servers (Centre and SI T+12
State)
ICT Hardware/Site Preparation
Site survey for the user level Hardware SI, DMT, SMT T+1
and Network installation
Preliminary inspection of Hardware and SMT, DMT, SPMU T+1
Network components
Network & Hardware Installation & SI,BSNL T+2
commissioning at Pilot Districts and other
Locations (Refer Section 6.1.1)
Acceptance tests for the network, SI, SPMU, BSNL, T+3
hardware and application SMT, DMT
Onsite inspection and verification of the SPMU, SMT, DMT T+3
inspection
Issue of final acceptance certificate for the SMT, DMT, SPMU T+4
network, application and hardware
Hardware and network installation SI, SPMU, SMT, T+4
completion report DMT
Capacity Building and Training
Creating Awareness and Sensitization SI, SMT, DMT T+3
through Seminars, Meetings and
Workshops
Preparation and approval of training SI, SMT T+4
material
Preparation and approval of training plan SI, SMT, SPMU T+5
Implementation of training plan at six pilot SI, DMT T+9
districts (Role-based Application Training,
Training of Trainers and Administrator
Training)
Incorporation of feedback from Pilot SI T+10
Training Completion report and sign offs SI, DMT, SMT,
SPMU

(Month)
Handholding & Helpdesk
Establishment
Starting of Handholding Support to PS for SI T1+6
six months & Establishment of Helpdesk
for PS & DC entire project period,
Providing Technical
Staff for DC
Roll-out Enhancement of CAS (State)
Phase I Evaluation of feedback and bugs by SI, Department D+1
(D=T+12) Department constituted
Committee, SPMU
Prioritisation of Changes required SI, SPMU, D+1
Department
Constituted
Committee
Incorporation of Change Requests and SI, NIC D+2
Customizations as per feedback
User Acceptance Testing SI, SPMU,DMT D+3
User Acceptance Testing Completion SI, SPMU, DMT D+4
Report
Installation and Configuration of Servers SI, NIC D+4
for Testing
Unit and Integration Testing SI D+5
Installation and Configuration of SI, NIC D+6
Production Servers
Beta version implementation report and SI, SMT, DMT, D+7
sign off SPMU
Launching the Beta Version SI D+8
Acceptance of the Beta Version Department D+9
Constituted
Committee
Go Live and Launch of the enhancements SI D+10
to the application in Roll out Phase I
locations on top of CAS (State) (Refer
Section 6.1.1)
ICT Hardware/Site Preparation
Site survey for the user level Hardware SI, DMT, SMT D+1
Preliminary inspection of Hardware and SMT, DMT, SPMU D+2
Network components
Network & Hardware Installation & SI,BSNL D+4
commissioning at Roll-out Phase I
Districts (Refer Section 6.1.1)
Acceptance tests for the network, SI, SPMU, BSNL, D+5
Onsite inspection and verification of the SPMU, SMT, DMT D+6
inspection
Issue of final acceptance certificate for the SMT, DMT, SPMU D+6

(Month)
Hardware and network installation SI, SPMU, SMT, D+7
Installation of CAS (State) SI, NIC D1=D+8
Creating Awareness and Sensitization SI, SMT, DMT D+1
Workshops
Preparation and approval of training SI, SMT D+2
material
Preparation and approval of training plan SI, SMT, SPMU D+5
Implementation of training plan at Roll-out SI, DMT D+9
Phase-I districts (Role-based Application
Training, Training of Trainers and
Administrator Training)
Incorporation of feedback SI D+10
Training Completion report and sign offs SI, DMT, SMT, D+11
SPMU
Establishment (D1 = Date at which
installation of network and hardware is
completed at all offices)
Starting of Handholding Support to PS for SI D1+6
Providing Technical
Staff for DC
Roll-out II ICT Hardware/Site Preparation
(E=D+12) Site survey for the user level Hardware SI, DMT, SMT E+1
Preliminary inspection of Hardware and SMT, DMT, SPMU E+2
Network components
Network & Hardware Installation & SI,BSNL E+4
commissioning at Roll-out Phase II
Districts (Refer Section 6.1.1)
Acceptance tests for the network, SI, SPMU, BSNL, E+5
Onsite inspection and verification of the SPMU, SMT, DMT E+6
inspection
Issue of final acceptance certificate for the SMT, DMT, SPMU E+6
Hardware and network installation SI, SPMU, SMT, E+7
Installation of CAS (State) of NIC SI, NIC E1=E+8
Creating Awareness and Sensitization SI, SMT, DMT E+1

(Month)
Workshops
Preparation and approval of training SI, SMT E+2
material
Preparation and approval of training plan SI, SMT, SPMU E+5
Implementation of training plan at Roll-out SI, DMT E+9
Phase-II districts (Role-based Application
Training, Training of Trainers and
Administrator Training)
Incorporation of feedback SI E+10
Training Completion report and sign offs SI, DMT, SMT, E+11
SPMU
Establishment
Starting of Handholding Support to PS for SI E1+6
Providing Technical
Staff for DC
The above implementation plan is tentative and the detailed implementation plan would be worked out
by the SI in coordination with the department. It has been suggested that the solution be piloted in all
offices in two districts and two commissionerates representing each of the 4 zones and the feedback
incorporated before rolling out across the State. The rollout plan shall be defined date-wise, location-
wise, module-wise and training completion and change management completion wise. A detailed
rollout checklist should be maintained for migrating application to production as well as for location
readiness.
SI shall prepare a detailed roll-out plan for each of the Districts in the Phase and get the same
approved by the department. SI is also responsible for conducting workshops for the key officers (State
Mission Team, District Mission Team, and District Core Team) of the Districts / State for presenting the
District-Wise roll-out plan and get the approval from the District Teams before getting the final approval
of the State Nodal Officer. The SI shall also provide the necessary assistance for the key officers (State
Mission Team, District Mission Team, and District Core Team) of the Districts / State during the roll-out
and implementation of CAS (State) in Tamil Nadu.
List of Indicative Deliverables:
1. Overall Project Plan

2. CAS Configuration / Roll-out / Extension of new modules
a. Requirements Traceability Matrix
b. Refined Functional Requirements Specification
c. Systems Requirement Specification
d. Design Document (High Level Design and Low Level Design)
e. Test Plans
f. CAS Configuration / roll-out/ Extension of new modules Document
3. Data Migration Strategy and Methodology including Detailed Data Migration Plan
4. Change Management and Capacity Building
a. Overall Change Management Plan
b. Content for Change Management including Awareness and Communications
Program
c. Overall Capacity Building Plan and District-wise Training Schedule and
Curriculum
d. Training Material
5. District-wise Roll-out / Implementation Plans
Service Levels
This section describes the service levels to be established for the Services offered by the SI to State.
The SI shall monitor and maintain the stated service levels to provide quality service to State. The
Service levels are provided in Annexure VI of this RFP.
ANNEXURE I Governance Structure (State Level)
As prescribed by DIT, the following committees formed at the state would continue to actively play a role
in implementation and monitoring of the project in various stages.
 State Apex Committee
 State Empowered Committee
 State Mission Team
 District Mission Team
The Overall Governance Structure for the project is illustrated below:

Overall Governance Structure for CCTNS Implementation
The structures of State Mission Team and District Mission Teams as mentioned in the MHA guidelines
are illustrated below:
State Mission Team Structure
District Mission Team Structure
The roles and responsibilities of each of the committees/teams are described in the table below:
Roles and Responsibilities of Committees/Teams
Committee/Team Roles and Responsibilities
State Apex Committee  Reviewing progress of the Project
 Overseeing utilization of funds
Frequency of Meeting:  Policy Directions and Guidance for successful
Quarterly execution of the Project
 Ensuring continuance of Mission Leader for sufficient
duration
 Creating a supporting environment for the success of
the project
State Empowered Committee  Disbursement of funds to Districts and other
units/agencies
Frequency of Meeting: Monthly  Approval of BPR proposals
 Sanction for various project components, as may be
specified, including the Hardware/Software
procurement as per the specifications from NIC
 Approval of various Project Components and
Functionalities to be covered in the Project
 Review progress of the Project
 Ensure proper Training arrangements
 Ensure deployment of appropriate handholding
personnel
 Other important policy and procedural issues
 Guidance to State/District Mission Teams
State Mission Team  Operational responsibility for the Project
 Formulating Project Proposals
Frequency of Meeting: Monthly  Getting sanction of GOI for various projects Hardware
rollout and operationalisation
 Co-ordination with various agencies
 Resolution of all software related issues, including
customization
 Resolution of all other issues hindering the Project
Progress
 Any other decision to ensure speedy implementation of
the project
 Assist the State Apex and Empowered Committees
District Mission Team  Prepare District Project Proposal
 Ensure proper Rollout of the Project in each selected
Frequency of Meeting: Monthly Police Station
Committee/Team Roles and Responsibilities

 Ensure hardware and software installation, and
operationalisation of the Project
 Training of all police personnel in the District
 Site preparation and availability of all utilities
 Ensure separate account keeping for the Project
The composition of committees/teams is described in the Tables below:

Composition of State Apex Committee
Sr. No Designation
1 Chief Secretary (Chair-Person)
2 Principal Home Secretary (Co-chair)
3 DGP
4 ADGP, SCRB (Convenor & Nodal Officer, CCTNS)
5 Secretary, Finance
6 IT Secretary
7 Representative from NIC
8 MHA Representative
9 MD, ELCOT
Composition of State Empowered Committee

Sr. No Designation
1 DGP (Chair-Person)
2 ADGP, SCRB (Co-chair)
3 Representative from NCRB
4 Special Secretary, Home Department
5 Special Secretary, Finance Department
6 MD, ELCOT
7 Representative from NIC
8 IGP, TNPHC, SDA
9 IGP, Training, PTC
Composition of State Mission Team

Sr. No Designation
1 ADGP, SCRB (Mission Leader)
2 IGP, TNPHC
3 SIO, NIC
4 Inspector, PCW
Composition of District Mission Team

Sr. No Designation
1 District SP (Chairperson)
2 Official from DCRB
3 DIO, District NIC
4 Official from PCW or official from other department with computer knowledge
5 DSP from one of the Law & Order Sub-division with sound domain knowledge
and computer awareness
6 Inspector from one of the Law & Order Sub-division with sound domain
knowledge and computer awareness
ANNEXURE II Details of Technology Stacks - CAS (State) and CAS (Center)
CAS (State) will be developed in FOSS stack by NIC.
The Technical Details for CAS (State) based on Free and Open Source Stack (FOSS), CAS (State)
Offline solution, CAS (Centre) Solution is provided in subsequent tables:
CAS (State) Online Solution
Description
The below Version (include
list is Proposed and Original major Support
indicative Solution by NIC Year of Supplier features/ Provided By
only Release services
only)
Webserver Apache 2.0 or above Apache HTTP Server Apache
Application HTTP
Tomcat 6.5 or above Apache Apache
Server Server
PostgreSQL
Database PostgreSQL 9.0 or above PostgreSQL ORDBMS
Community
Operating
Ce ntOS 2.0 or above Community OS Community
System
Others
Reporting Reporting
Jasper/PDF Reports 3.7 or above Jasper
Engine Services
Search:
Unstructured
data: using Open
CMS search
features
Search
Structured Data: N/a N/a N/a N/a
Engine
PostgreSQL DB
Search Engine &
Custom
application
interface
Description
The below Version (include
list is Proposed and Original major Support
indicative Solution by NIC Year of Supplier features/ Provided By
only Release services
only)
Portal Server FOSS stack NA Community HTTP Server Community
Workflow
FOSS Stack Com munity Community
Engine
Rules Engine Custom Built N/a N/a N/a N/a
Directory
FOSS 7.0 SUN LDAP SUN
Services
DMS/CMS Joomla/Drupal 7.5 or abov e
Email/Mess
Squirrel Mail
a ging
Physical
Security, Network
Security, DB
Encryption
Security (PostgreSQL), DB N/a N/a N/a N/a
Access Controls,
Role Based Access
Control (Custom
Developed), FOSS)
Identity
FOSS N/a N/a N/a Community
Management
Audit Custom Built N/a N/a N/a N/a
ETL +
Data Custom Built N/A N/a N/a Community
Quality
CAS (State) Offline Solution

The below Proposed Version Original Descriptio Support
list is Solution by and Supplier n (include Provided
Software Year of major By
indicative
only Development Release features/
Agency services
only)
Synchronizati Custom Built N/a N/a N/a N/a

on
Solution
Application Apache 6.0 Apache J2EE/PHP

Container Tomcat Foundati Application
on Container
Database PostgreSQL 9.0 Commu -- NIC

nity
ANNEXURE III Bill of Quantity – Client Site Locations
Scope of Hardware Supply, Installation, Commission, Testing and Maintenance

System integrator is responsible for supply, install, commission, testing and maintenance of Hardware
and other peripheral to all police stations and higher offices as mentioned below:
1 Non CIPA Police Stations 1345
2 CIPA Police Stations 137
3 AC Range Office/SDPO 258
4 Range/Zone 16
5 SCRB 1
6 TN Finger Print Bureau/ Forensic Science Lab 2
7 District Control Room 33
9 DPO 33
10 Commissionerate 7
11 ADC/DC/JC/ACOP Offices 53
12 ADSP Office 62
13 Police HQ Office 1
FIR Registering Special Unit Offices
14 Coastal Security Group 11
15 CBCID 43
16 Crime (SIT) 34
17 Commercial Crime Investigation Wing 31
18 Economic Offenses Wing 16
19 Prohibition Enforcement Wing 94
20 District Crime Branch /City Crime Branch 38
21 Civil Supplies CID 20
22 Traffic Investigation Wing 44
23 Traffic Enforcement Wing 148
24 Juvenile Aid Police Uunit 9
25 Anti Vice Squad 3
26 Anti Dowry Cell 2
Sub-total 493
FIR Registering Special Unit HQ 6
27 CSG 1
28 CBCID 3
29 Crime (SIT) 1
30 Idol Wing 1
Sub-total 6
Total 2441
Location wise distribution of hardware and peripherals is given below:
Police Station Hardware and Site Preparation Requirements (1345 Non CIPA PS, 137 CIPA PS
Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 1482
Police Stations:
PS Hardware and Site Preparation Requirements
Item Description Qty Make Model
Desktop Systems 4
HDD 160 GB 1
Duplex Laser Printer 1
Multi-function Laser
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
Network Switch 16 Ports 10/100 Un-
managed 1
Fingerprint Reader 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Adequate Furniture 1
Electrical Cabling 1
Earthing & Earth Pit 1
Wall Mountable Network Rack - 9 U 1
Patch Panel 12 Ports CAT 6 1
Information Outlet CAT 6 6
Cat 6 Cable with Cabling (In Meters) 120
Patch Cords 1 Mtr. CAT 6 6
Operational Expenses Each PS (In 5
Years)
Software
NIC Linux (to be provided by NIC) 4
LibreOffice 3.3 (to be provided by NIC) 4
Client Antivirus (5 Years) (Free to use) 4
Application Patch Management Software 4
(to be provided by NIC)
Asset Management Software (to be part 4
of EMS)
SDPO/ AC Range Office Hardware and Site Preparation Requirements (174 SDPO, 84 AC Range
Office Locations):
SDPO/ AC Range Offices:
SDPO/ AC Range Office Hardware and Site Preparation Requirements
Desktop Systems 3
Multi-function Laser (Print/Scan/Copy) 1
UPS 2 KVA 1
managed 1
Site Preparation
Operational Expenses Each Location (In 5
Years)
Software
Client Antivirus (5 Years) (Free to Use) 3
Asset Management Software (to be part of 3
EMS)
Range/Zone Office Hardware and Site Preparation Requirements (12 Range and 4 Zone Office
Locations):
Range/Zone Offices:
Range/Zone Office Hardware and Site Preparation Requirements
Desktop Systems 4
UPS 2 KVA 1
Network Switch 16 Ports 10/100 Un- 1
managed
Site Preparation
Range/Zone Office Hardware and Site Preparation Requirements

Years)
Software
UBUNTU LINUX 10.04 LTS or openSUSE 4
11.3 or FEDORA 13
LibreOffice 3.3 (to be available with the 4
above mentioned OS)
Client Antivirus (5 Years) (Free to Use) 4
EMS)
SCRB Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at SCRB:
SCRB Hardware and Site Preparation Requirements
Desktop Systems 4
UPS 5 KVA 1
Network Switch 16 Ports 10/100 Managed 1
Site Preparation
SCRB Hardware and Site Preparation Requirements

Years)
Software
11.3 or FEDORA 13
Libre Office 3.3 Office (to be available with 4
the above mentioned OS)
Client Antivirus for Linux OS (5 Years) 4
(Free to Use)
EMS)
State Fingerprint Bureau/State Forensic Science Lab Hardware and Site Preparation
Requirements (2 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at the state level Finger
Print Bureau (FPB) and Forensic Science Lab (FSL):
State FPB/FSL Hardware and Site Preparation Requirements
Desktop Systems 2
managed
Site Preparation
Years)
Software
11.3 or FEDORA 13
Client Antivirus for Linux OS (5 Years) (Free 2
to Use)
Application Patch Management Software (to 2
be provided by NIC)
EMS)
District Control Room Hardware and Site Preparation Requirements (33 Locations):
The set-up for control rooms would be established in each of the districts headquarters would consist of
the below items:
District Control Room Hardware and Site Preparation Requirements

Desktop Systems 3
managed
Site Preparation
Years)
Software
11.3 or FEDORA 13
to Use)
be provided by NIC)
EMS)
State Control Room Hardware and Site Preparation Requirements (1 Location):

The below mentioned items would be catering to Chennai Police Control Room which handles large
volume of traffic.
State Control Room Hardware and Site Preparation Requirements
Desktop Systems 5
managed
Site Preparation
Years)
Software
11.3 or FEDORA 13
to Use)
State Control Room Hardware and Site Preparation Requirements


be provided by NIC)
EMS)
District Police Office Hardware and Site Preparation Requirements (33 Locations):
District Police Offices:
District Police Office Hardware and Site Preparation Requirements
Desktop Systems 10
UPS 5 KVA 1
Site Preparation
Years)
Software
11.3 or FEDORA 13
to Use)
be provided by NIC)
EMS)
Commissionerate Hardware and Site Preparation Requirements (7 Locations):

Commissionerates:
Commissionerate Hardware and Site Preparation Requirements

Desktop Systems 25
UPS 5 KVA 3
Site Preparation
Years)
Software
11.3 or FEDORA 13
to Use)
be provided by NIC)
EMS)
ACOP/JC/DC/ADC Offices Hardware and Site Preparation Requirements (53 Locations):

SI has to supply, install, commission, testing of below hardware and peripherals at 53 offices of
Additional Commissioners, Joint Commissioners, Deputy Commissioners and Additional Deputy
Commissioners:
ACOP/JC/DC/ADC Offices Hardware and Site Preparation Requirements
Desktop Systems 3
UPS 2 KVA 1
Network Switch 16 Ports 10/100 un- 1
managed
Site Preparation
ACOP/JC/DC/ADC Offices Hardware and Site Preparation Requirements


Years)
Software
11.3 or FEDORA 13
to Use)
be provided by NIC)
EMS)
ADSP Offices Hardware and Site Preparation Requirements (62 Locations):

SI has to supply, install, commission, testing of below hardware and peripherals at 62 ADSP offices:
ADSP Offices Hardware and Site Preparation Requirements
Desktop Systems 2
UPS 2 KVA 1
Network Switch 16 Ports 10/100 un-managed 1
Site Preparation
Years)
ADSP Offices Hardware and Site Preparation Requirements

Software
11.3 or FEDORA 13
to Use)
be provided by NIC)
EMS)
Police Headquarters Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Police
Headquarters:
Police HQ Hardware and Site Preparation Requirements
Desktop Systems 50
UPS 5 KVA 4
Site Preparation
Years)
Software
11.3 or FEDORA 13
to Use)
be provided by NIC)
Police HQ Hardware and Site Preparation Requirements

EMS)
CSG Unit Office Hardware and Site Preparation Requirements (11 Locations):
Coastal Security Group Unit Offices:
CSG Unit Office Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Years)
Software
to Use)
be provided by NIC)
EMS)
CBCID Unit Offices Hardware and Site Preparation Requirements (44 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 44 CBCID
Unit Offices:
CBCID Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Years)
Software
to Use)
be provided by NIC)
EMS)
Crime (SIT) Unit Offices Hardware and Site Preparation Requirements (34 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 34 Crime
(SIT) Unit Offices:
Crime (SIT) Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Years)
Software
to Use)
be provided by NIC)
EMS)
CCIW Unit Offices Hardware and Site Preparation Requirements (31 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 31 CCIW
Unit Offices:
CCIW Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
CCIW Unit Offices Hardware and Site Preparation Requirements

(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Years)
Software
to Use)
be provided by NIC)
EMS)
EOW Unit Offices Hardware and Site Preparation Requirements (16 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 16 EOW
Unit Offices:
EOW Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
EOW Unit Offices Hardware and Site Preparation Requirements

UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Years)
Software
to Use)
be provided by NIC)
EMS)
PEW Unit Offices Hardware and Site Preparation Requirements (94 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 94 PEW
Unit Offices:
PEW Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
PEW Unit Offices Hardware and Site Preparation Requirements


managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Years)
Software
to Use)
be provided by NIC)
EMS)
DCB/CCB Unit Offices Hardware and Site Preparation Requirements (38 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 38 District
and City Crime Branch Unit Offices:
DCB/CCB Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
DCB/CCB Unit Offices Hardware and Site Preparation Requirements

Digital Camera 1
Electronic Pen 1
Site Preparation
Years)
Software
to Use)
be provided by NIC)
EMS)
CSCID Unit Offices Hardware and Site Preparation Requirements (20 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 20 Civil
Supplies Unit Offices:
CSCID Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
CSCID Unit Offices Hardware and Site Preparation Requirements

Years)
Software
to Use)
be provided by NIC)
EMS)
TIW Unit Offices Hardware and Site Preparation Requirements (43 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 43 Traffic
Investigation Wing Unit Offices:
TIW Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
TIW Unit Offices Hardware and Site Preparation Requirements


Years)
Software
to Use)
be provided by NIC)
EMS)
TEW Unit Offices Hardware and Site Preparation Requirements (178 Locations):
Traffic Enforcement Wing Unit Offices:
TEW Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
TEW Unit Offices Hardware and Site Preparation Requirements

Years)
Software
to Use)
be provided by NIC)
EMS)
JAPU Unit Offices Hardware and Site Preparation Requirements (9 Locations):

SI has to supply, install, commission, testing of below hardware and peripherals at each of the 9 Juvenile
Aid Police Unit Offices:
JAPU Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
JAPU Unit Offices Hardware and Site Preparation Requirements


Years)
Software
to Use)
be provided by NIC)
EMS)
AVS Unit Offices Hardware and Site Preparation Requirements (3 Locations):

SI has to supply, install, commission, testing of below hardware and peripherals at each of the 3 Anti
Vice Squad Unit Offices:
AVS Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Years)
Software
AVS Unit Offices Hardware and Site Preparation Requirements


to Use)
be provided by NIC)
EMS)
ADoC Unit Offices Hardware and Site Preparation Requirements (2 Locations):

SI has to supply, install, commission, testing of below hardware and peripherals at each of the 2 Anti
Dowry Cell Unit Offices:
ADoC Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Years)
Software
ADoC Unit Offices Hardware and Site Preparation Requirements

to Use)
be provided by NIC)
EMS)
CSG Headquarters Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Coastal Security
Group Headquarters:
CSG HQ Hardware and Site Preparation Requirements

Desktop Systems 10
UPS 5 KVA 1
Site Preparation
Years)
Software
11.3 or FEDORA
above mentioned OS)
to Use)
be provided by NIC)
EMS)
CBCID Headquarters Hardware and Site Preparation Requirements (3 Locations):

SI has to supply, install, commission, testing of below hardware and peripherals at the 3 CBCID
Headquarters:
CBCID HQ Hardware and Site Preparation Requirements

Desktop Systems 10
Multi-function Laser (Print/Scan/Copy 10
UPS 5 KVA 1
Site Preparation
Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
Idol Wing Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Idol Wing:
Idol Wing Hardware and Site Preparation Requirements

Desktop Systems 10
UPS 5 KVA 1
Site Preparation
Idol Wing Hardware and Site Preparation Requirements

Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
Crime (SIT) HQ Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Crime (SIT)
Headquarters:
Crime (SIT) HQ Hardware and Site Preparation Requirements

Desktop Systems 10
UPS 5 KVA 1
Site Preparation
Years)
Software
11.3 or FEDORA 13
Crime (SIT) HQ Hardware and Site Preparation Requirements


to Use)
be provided by NIC)
EMS)
Note:
The detailed specifications for hardware including desktops and furniture are described in Annexure
VIII.
Adequate Furniture: 2 Large Computer tables, 2 Small Computer Tables, 4 Chairs comprise a Set,
where Furniture is provisioned under this project. The exact requirement for each office should be
decided by the SI based on discussion with the department. Specifications for the furniture are provided
in the Annexure VIII
Operation expense: This includes free of cost replacement of toner cartridge for Laser and
Multifunction printer. The frequency of cartridge replacement shall be quarterly, i.e. every 3 months one
cartridge to be replaced in each printer. Free of cost replacement of Teflon paper of each laser &
multifunction printer on yearly basis is also a part of Operational expense. However cost of stationery
item is not included in this head. Consumption of cartridges may vary based on usage of individual
police locations, although SI shall strictly supply total number of cartridges as per quantity mentioned
above. Spare cartridges of any location may be used at other location on need basis. All the supplied
cartridges must be of the same original printer manufactures only and must follow standards of printer
manufacturer. Refilling of cartridges is not permitted.
Data Centre and Disaster Recovery Site Hardware and Software Requirements:
Data Centre Storage with SAN 1
Management Software, Backup
Software and SAN Switch
Disaster Recovery Centre Storage 1
with SAN Management Software,
Backup Software and SAN Switch
Data Centre Server Components
Application Server 2
Database Server 2
Web Server 2
Antivirus server 2
Mail & EMS Server 1
Load Balancer 1
Disaster Recovery Centre Server

Components

Database Server 2
Web Server 2
Anti-virus Server 2
Mail & EMS Server 1
Load Balancer 1
Automated Tape Library (ATL) for
Data Centre with backup Software 1
Fibre Cabling and Network Items
for Data Centre and Disaster
Recovery Centre
Internet Routers 2
Core switch L3 Gigabit 48 Port 2
Application Switches 2
UTM Firewall with VPN and IPS 2
Server racks 2
Open racks 2
8 port KVM switches 2
KVM over IP (Network Racks) 2
Host Intrusion Prevention System 18
(HIPS)
CAT 6 Cable (305 Mtr. Box) 3
Patch Cord 1 Mtr CAT 6 36
Data Centre and Disaster Recovery
Centre Software
Data Center Software (Server OS 18
with CAL, Server Management,
Intranet Portal, MIS & Reporting
Dashboard etc.)
Antivirus Software for Servers 4+14 CAL
Email Server Security Software 2
Enterprise Management System 18 CAL
(EMS)
TNSDC Compliance Management Unified
License to
cover large
number of
department
users
TNSDC Privileges Users 18 CAL
Management for Server Control
TNSDC Web Access Management 4 CAL
Out Sources manpower for 216
datacenters 2 nos. × 3 shifts for 4

Years (216 Man Months)
The minimum outsourced manpower details for datacenter are given below:
Technical Support and Project Team
Item Description Number of Persons

System and Network Administrator at Data Centre 3
Technical Support Staff at Data Centre 3
The overall Bill of material for above mentioned requirements at client and server side for client
site locations is listed as follows:
Client Side - Total Bill of Materials

Desktop Systems 9868
HDD 160 GB 2005
Multi-function Laser Printer ( Print/Scan/Copy) 2523
Network Switch 16 Ports 10/100 Un-managed 2430
Digital Camera 2005
Electronic Pen 2005
UPS 2 KVA 2394
UPS 5 KVA 65
3 KVA Inverter 2005
Server Side – Total Bill of Materials Required Qty

Data Centre Storage with SAN Management Software, 1
Backup Software and SAN Switch
Disaster Recovery Centre Storage with SAN Management 1
Software, Backup Software and SAN Switch
Data Centre Server Components
Database Server 2
Web Server 2
Antivirus server 2
Mail & EMS Server 1
Load Balancer 1
Disaster Recovery Centre Server Components

Server Side – Total Bill of Materials Required Qty

Database Server 2
Web Server 2
Anti-virus Server 2
Mail & EMS Server 1
Load Balancer 1
Automated Tape Library (ATL) for Data Centre with backup 1
Software
Fibre Cabling and Network Items for Data Centre and
Disaster Recovery Centre
Internet Routers 2
Core switch L3 Gigabit 48 Port 2
Application Switches 2
UTM Firewall with VPN and IPS 2
Server racks 2
Open racks 2
8 port KVM switches 2
KVM over IP (Network Racks) 2
Host Intrusion Prevention System (HIPS) 18
CAT 6 Cable (305 Mtr. Box) 3
Data Centre and Disaster Recovery Centre Software
Data Center Software (Server OS with CAL, Server 18
Management, Intranet Portal, MIS & Reporting Dashboard etc.)
Antivirus Software for Servers 4+14 CAL
Email Server Security Software 2
Enterprise Management System (EMS) 18 CAL
TNSDC Compliance Management Unified License to cover
large number of
department users
TNSDC Privileges Users Management for Server Control 18 CAL
TNSDC Web Access Management 4 CAL
Out Sources manpower for datacenters 2 nos. × 3 shifts for 216
4 Years (216 Man Months)
ANNEXURE IV Bill of Quantity – Additional Locations
Scope of Hardware Supply, Installation, Commission, Testing and Maintenance

System integrator is responsible for supply, install, commission, testing and maintenance of Hardware
and other peripherals to the additional special unit offices and higher offices as mentioned below:
S.No Additional Locations Number of Offices

1 Intelligence HQ 1
Intelligence Offices
2 Q-Branch 30
3 SBCID 42
4 Special Division 6
5 Security Branch & Core Cell 10
6 Organized Crime and Intelligence Unit 19
7 SIT 5
Sub-total 112
8 Outposts 69
9 Jails (includes sub-jails, Borstal school, district 129
jails, special sub-jails and central prisons)
10 District Level SDFPB and FSL 74
Other Special Unit Offices
12 District Special Branch 40
13 Armed Police 17
15 Special Task Force 2
Sub-total 179
Other Special Unit HQ
17 Armed Police 1
19 Home Guards (HG) 1
20 State Traffic Planning Cell 1
21 Tamil Nadu Commando Force 1
Sub-total 6
Total 570
Intelligence Headquarters Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Intelligence
Headquarters:
Intelligence HQ Hardware and Site Preparation Requirements

Desktop Systems 35
UPS 5 KVA 3
Handheld Device for data access and 7
communication
Site Preparation
Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
Intelligence Unit Offices Hardware and Site Preparation Requirements (112 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at the Intelligence Unit
Offices:
Intelligence Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 5
UPS 5 KVA 1
Intelligence Unit Offices Hardware and Site Preparation Requirements

Handheld Devices for data access and 1
communication
Site Preparation
Years)
Software
to Use)
be provided by NIC)
EMS)
Outposts Hardware and Site Preparation Requirements (69 Locations):

outposts:
Outposts Hardware and Site Preparation Requirements

Desktop Systems 4
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter
1
managed 1
Site Preparation
Outposts Hardware and Site Preparation Requirements


Years)
Software
to Use)
be provided by NIC)
EMS)
Jail Hardware Requirements (129 locations)

SI has to supply, install, commission, testing of computers at the jails including including sub-jails,
Borstal school, district jails, special sub-jails and central Prisons:
Jail Hardware and Site Preparation Requirements

Desktop Systems 1
Years)
Software
11.3 or FEDORA 13 with LibreOffice 3.3
above mentioned OS)
to Use)
be provided by NIC)
EMS)
District Forensic Science Lab /Single Digit Fingerprint Bureau Hardware and Site Preparation
Requirements (74 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at the state level Finger
Print Bureau (FPB) and Forensic Science Lab (FSL):
District FPB/FSL Hardware and Site Preparation Requirements
Desktop Systems 2
Site Preparation
Years)
Software
11.3 or FEDORA 13
LibreOffice 3.3 (to be available with the above 2
mentioned OS)
Client Antivirus for Linux OS (5 Years) (Free to 2
Use)
be provided by NIC)
EMS)
Technical Services Unit Offices Hardware and Site Preparation Requirements (114 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 114 Unit
Offices of Technical Services:
Technical Services Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Technical Services Unit Offices Hardware and Site Preparation Requirements

Site Preparation
Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
District Special Branch Unit Offices Hardware and Site Preparation Requirements (40 Locations):
SI has to supply, install, commission, testing of below hardware and peripherals at each of the 40 DSB
Unit Offices:
DSB Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
DSB Unit Offices Hardware and Site Preparation Requirements

Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
Armed Police Unit Offices Hardware and Site Preparation Requirements (17 Locations):
Offices of Armed Police:
Armed Police Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Armed Police Unit Offices Hardware and Site Preparation Requirements

Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
SJ & HR Unit Offices Hardware and Site Preparation Requirements (15 Locations):
Offices of Social Justice and Human Rights:
SJ & HR Unit Offices Hardware and Site Preparation Requirements

Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
SJ & HR Unit Offices Hardware and Site Preparation Requirements

Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
Special Task Force Unit Offices Hardware and Site Preparation Requirements (2 Locations):
Offices of Special Task Force:
Special Task Force Unit Offices Hardware and Site Preparation Requirements
Desktop Systems 4
HDD 160 GB 1
(Print/Scan/Copy) 1
UPS 2 KVA 1
3 KVA Inverter 1
managed 1
Digital Camera 1
Electronic Pen 1
Site Preparation
Special Task Force Unit Offices Hardware and Site Preparation Requirements
Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
Technical Services Headquarters Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Technical
Services Headquarters:
Technical Services HQ Hardware and Site Preparation Requirements

Desktop Systems 10
UPS 5 KVA 1
Site Preparation
Years)
Software
UBUNTU LINUX 10.04 LTS or openSUSE 11.3 10
or FEDORA 13
LibreOffice 3.3 (to be available with the above 10
mentioned OS)
Client Antivirus for Linux OS (5 Years) (Free to 10
Use)
Technical Services HQ Hardware and Site Preparation Requirements

Application Patch Management Software (to be 10

provided by NIC)
Asset Management Software (to be part of EMS) 10
Armed Police Headquarters Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Armed Police
Headquarters:
Armed Police HQ Hardware and Site Preparation Requirements

Desktop Systems 10
UPS 5 KVA 1
Site Preparation
Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
SJ & HR Headquarters Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Social Justice &
Human Rights Headquarters:
SJ & HR HQ Hardware and Site Preparation Requirements

Desktop Systems 10
UPS 5 KVA 1
Site Preparation
Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
Home Guards Headquarters Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Home Guards
Headquarters:
Home Guards HQ Hardware and Site Preparation Requirements

Desktop Systems 10
UPS 5 KVA 1
Site Preparation
Home Guards HQ Hardware and Site Preparation Requirements

Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
STPC Headquarters Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the State Transport
Planning Cell Headquarters:
STPC HQ Hardware and Site Preparation Requirements

Desktop Systems 10
UPS 5 KVA 1
Site Preparation
Years)
Software
STPC HQ Hardware and Site Preparation Requirements


11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
TNCF Headquarters Hardware and Site Preparation Requirements (1 Location):

SI has to supply, install, commission, testing of below hardware and peripherals at the Tamil Nadu
Commando Force Headquarters:
TNCF HQ Hardware and Site Preparation Requirements

Desktop Systems 10
UPS 5 KVA 10
Site Preparation
Years)
Software
11.3 or FEDORA 13
above mentioned OS)
to Use)
be provided by NIC)
EMS)
Note:
The detailed specifications for hardware including desktops and furniture are described in Annexure VIII.
Adequate Furniture: 2 Large Computer tables, 2 Small Computer Tables, 4 Chairs comprise a Set,
where Furniture is provisioned under this project. The exact requirement for each office should be
decided by the SI based on discussion with the department. Specifications for the furniture are provided
in the Annexure VIII.
Operation expense: This includes free of cost replacement of toner cartridge for Laser and Multifunction
printer. The frequency of cartridge replacement shall be quarterly, i.e. every 3 months one cartridge to be
replaced in each printer. Free of cost replacement of Teflon paper of each laser & multifunction printer
on yearly basis is also a part of Operational expense. However cost of stationery item is not included in
this head. Consumption of cartridges may vary based on usage of individual police locations, although SI
shall strictly supply total number of cartridges as per quantity mentioned above. Spare cartridges of any
location may be used at other location on need basis. All the supplied cartridges must be of the same
original printer manufactures only and must follow standards of printer manufacturer. Refilling of
cartridges is not permitted.
The overall Bill of material for above mentioned requirements at client side for additional
locations is listed as follows:
Client Side - Total Bill of Materials

Desktop Systems 1795
HDD 160 GB 179
Multi-function Laser Printer ( Print/Scan/Copy) 698
Digital Camera 179
Electronic Pen 179
UPS 2 KVA 248
UPS 5 KVA 121
3 KVA Inverter 179
Handheld Device for Data access and communication 119
ANNEXURE V Post Implementation Support Services
As part of the post implementation services, the SI shall provide support for the software, hardware,
and other infrastructure provided as part of this RFP. SI shall provide five (5) years of
comprehensive AMC that includes
1. Warranty support
2. Annual Technical Support (ATS)
3. Handholding Services
a. Operations and maintenance services for the server and related infrastructure supplied
and commissioned by the SI for the application at the Data Center and Disaster
Recovery Center.
b. Central Helpdesk from the State designated premises.
c. Support for the end users at each of the locations including deployment of one
competent person at each police station for a period of six months to handhold the staff
after the Core application and the necessary infrastructure are successfully
commissioned in the police stations.
d. Software maintenance and support services.
e. Application functional support services
The services shall be rendered onsite from the State designated premises. To provide the support for the
police stations, circle offices, sub‐divisional offices, district headquarters/ Commissionerates, ranges,
zones, State police headquarters and other locations across the State where the software, hardware,
and other infrastructure will be rolled out, SI is expected to provide experienced and skilled personnel at
each location. The SI will also ensure that there is a Service Center available or setup at each district or
a group of districts of the State, as per mutual understanding between State and the SI.
As part of the warranty services SI shall provide:
1. SI shall provide a comprehensive warranty and on-site free service warranty for 5 years from the
date of Go Live.
2. SI shall obtain the five year product warranty and five year onsite free service warranty on all
licensed software, computer hardware and peripherals, networking equipments and other
equipment.
3. SI shall provide the comprehensive manufacturer's warranty in respect of proper design,
quality and workmanship of all hardware, equipment, accessories etc. covered by the RFP. SI
must warrant all hardware, equipment, accessories, spare parts, software etc. procured and
implemented as per this RFP against any manufacturing defects during the warranty period.
4. SI shall provide the performance warranty in respect of performance of the installed hardware
and software to meet the performance requirements and service levels in the RFP.
5. SI is responsible for sizing and procuring the necessary hardware and software licenses as
per the performance requirements provided in the RFP. During the warranty period SI shall
replace or augment or procure higher-level new equipment or additional licenses at no
additional cost to the State in case the procured hardware or software is not adequate to meet
the service levels.

6. Mean Time between Failures (MTBF) If during contract period, any equipment has a
hardware failure on four or more occasions in a period of less than three months or six times in
a period of less than twelve months, it shall be replaced by equivalent or higher-level new
equipment by the SI at no cost to State. However, if the new equipment supplied is priced
lower than the price at which the original item was supplied, the differential cost should be
refunded to State. For any delay in making available the replacement and repaired equipments
for inspection, delivery of equipments or for commissioning of the systems or for acceptance
tests / checks on per site basis, State reserve the right to charge a penalty.
7. During the warranty period SI shall maintain the systems and repair / replace at the installed
site, at no charge to State, all defective components that are brought to the SI's notice.
8. The SI shall as far as possible repair the equipment at site.
9. In case any hard disk drive of any server, SAN, or client machine is replaced during warranty/
AMC the unserviceable HDD will be property of State and will not be returned to SI.
10. Warranty should not become void, if State buys, any other supplemental hardware from a third
party and installs it within these machines under intimation to the SI. However, the warranty will
not apply to such supplemental hardware items installed.
11. The SI shall carry out Preventive Maintenance (PM) once in a quarter, including cleaning
of interior and exterior, of all hardware and testing for virus, if any, and should maintain proper
records at each site for such PM. Failure to carry out such PM will be a breach of warranty and
the warranty period will be extended by the period of delay in PM.
12. SI shall monitor warranties to check adherence to preventive and repair maintenance terms and
conditions.
13. The SI shall ensure that the warranty complies with the agreed Technical Standards, Security
Requirements, Operating Procedures, and Recovery Procedures.
14. SI shall have to stock and provide adequate onsite and offsite spare parts and spare
component to ensure that the uptime commitment as per SLA is met.
15. Any component that is reported to be down on a given date should be either fully repaired or
replaced by temporary substitute (of equivalent configuration) within the time frame indicated in
the Service Level Agreement (SLA).
16. The SI shall develop and maintain an inventory database to include the registered hardware
warranties.
As a part of the ATS services SI shall provide:
1. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes,
replacements and maintenance.
2. If the Operating System or additional copies of Operating System are required to be installed /
reinstalled / de-installed, the same should be done as part of ATS.
3. SI should carry out any requisite adjustments / changes in the configuration for implementing
different versions of Application Software.
4. Updates/Upgrades/New releases/New versions: The SI shall provide from time to time the
Updates/Upgrades/New releases/New versions of the software and operating systems as
required. The SI should provide free upgrades, updates & patches of the software and tools to
State as and when released by OEM.

5. SI shall provide patches to the licensed software including the software, operating system,
databases and other applications.
6. Software License Management: The SI shall provide for software license management and
control. SI shall maintain data regarding entitlement for software upgrades, enhancements,
refreshes, replacements, and maintenance.
7. SI shall provide complete manufacturer’s technical support for all the licensed software problems
and/or questions, technical guidance, defect and non-defect related issues. SI shall provide a
single-point-of-contact for software support and provide licensed software support including but
not limited to problem tracking, problem source identification, problem impact (severity)
determination, bypass and recovery support, problem resolution, and management reporting.
8. The manufacturer’s technical support shall at a minimum include online technical support and
telephone support during the State’s business hours (Business hours in State will be from
0830 hours to 2030 hours on all days (Mon-Sun)) with access for State and SI to the
manufacturer’s technical support staff to provide a maximum of 4 hour response turnaround
time. There should not be any limits on the number of incidents reported to the manufacturer.
State shall have access to the online support and tools provided by the manufacturer. State shall
also have 24x7 access to a variety of technical resources including the manufacturer’s
knowledge base with complete collections of technical articles.
As a part of the Handholding services to provide Operations and maintenance support for the
server and related infrastructure supplied and commissioned by the SI for the application at the Data
Center and Disaster Recovery Center SI shall provide:
1. The scope of the services for overall IT infrastructure management as per ITIL framework
shall include 365x24x7 on site Monitoring, Maintenance and Management of the server and
related infrastructure supplied and commissioned by the SI for the application at the Data
Center and Disaster Recovery Center. The business hours in State will be from 0830 hours to
2030 hours on all days (Mon-Sun). SI will plan these services accordingly. The SI shall provide
the MIS reports for all the devices installed in the Data Center and Disaster Recovery Center in
format and media as mutually agreed with the State on a monthly basis. Whenever required by
State, SI should be able to provide additional reports in a pre-specified format. The indicative
services as part of this support are as below:
a) System Administration, Maintenance & Management Services
b) Application Monitoring Services
c) Network Management Services
d) Backend Services (Mail, messaging, etc)
e) Storage Administration and Management Services
f) IT Security Administration Services and Services for ISO 27001 and ISO 20000
compliance
g) Backup and Restore Services
As a part of the Handholding services to provide Centralized Helpdesk and Support for end users at
each location SI shall provide:
1. The service will be provided in the local language of the State, viz., Tamil.
2. The help desk service that will serve as a single point of contact for all ICT related incidents and
service requests. The service will provide a Single Point of Contact (SPOC) and also resolution
of incidents. State requires the SI to provide Help Desk services to track and route requests for
service and to assist end users in answering questions and resolving problems related to the
software application, network, Data Center, Disaster Recovery Center, Client side
infrastructure, and operating systems at all locations. It becomes the central collection point for
contact and control of the problem, change, and service management processes. This includes
both incident management and service request management.
3. SI shall provide a second level of support for application and technical support at police
stations, sub-divisional offices, district headquarters / Commissionerates, range offices, zonal
offices, State police headquarters and other locations across the State where the software,
hardware, and other infrastructure will be rolled out.
4. For all the services of State within the scope of this RFP, SI shall provide the following
integrated customer support and help.
5. Establish 16X6 Help Desk facility for reporting issues/ problems with the software, hardware and
other infrastructure.
6. SI shall maintain and support to all client side infrastructure including hardware, networking
components, and other peripherals.
7. SI shall provide maintenance of Hardware, including preventive, scheduled and predictive
Hardware support, as well as repair and / or replacement activity after a problem has
occurred.
8. SI shall track and report observed Mean Time Between Failures (MTBF) for Hardware.
9. SI shall provide functional support on the application components to the end users.
10. SI shall also provide system administration, maintenance and management services, LAN
management services, and IT security administration services.
As a part of the Handholding services to provide software maintenance and support services SI
shall provide:
1. The Software Maintenance and Support Services shall be provided for all software procured and
implemented by the SI. The SI shall render both on-site and off-site maintenance and support
services to State to all the designated locations. The Maintenance and Support Services will
cover, all product upgrades, modifications, and enhancements.
2. Updates/Upgrades/New releases/New versions: The SI will implement from time to time the
Updates/Upgrades/New releases/New versions of the software and operating systems as
required after necessary approvals from State about the same.
3. Tuning of application, databases, third party software’s and any other components provided as
part of the solution to optimize the performance.
4. The SI shall apply regular patches to the licensed software including the operating system
and databases as released by the OEMs.
5. Software Distribution: SI shall formulate a distribution plan prior to rollout and distribute/install
the configured and tested software as per the plan.
6. Software License Management: The SI shall provide for software license management and
control. SI shall maintain data regarding entitlement for software upgrades, enhancements,
refreshes, replacements, and maintenance. SI should perform periodic audits to measure license
compliance against the number of valid End User software licenses consistent with the terms
and conditions of site license agreements, volume purchase agreements, and other mutually
agreed upon licensed software terms and conditions and report to State on any exceptions to SI
terms and conditions, to the extent such exceptions are discovered.
7. The SI shall undertake regular preventive maintenance of the licensed software.
As part of the Handholding services to provide application functional support services SI shall provide:
1. The Application Functional Support Services shall be provided for all software procured and
implemented by the SI. The SI shall render both on-site maintenance and support services to
State from the development center in State.
2. Enhancements and defect fixes. SI shall incorporate technological changes, and provide
enhancements as per the requests made by State. SI shall perform minor changes, bug fixes,
error resolutions and minor enhancements that are incidental to proper and complete working of
the application.
3. Routine functional changes that include user and access management, creating new report
formats, and configuration of reports.
4. SI shall provide user support in case of technical difficulties in use of the software, answering
procedural questions, providing recovery and backup information, and any other requirement
that may be incidental/ancillary to the complete usage of the application.
5. The SI shall migrate all current functionality to the new / enhanced version at no additional
cost to State and any future upgrades, modifications or enhancements.
6. The SI shall perform user ID and group management services.
7. The SI shall maintain access controls to protect and limit access to the authorized End Users of
the State.
8. The services shall include administrative support for user registration, creating and
maintaining user profiles, granting user access and authorization, providing ongoing user
password support, announcing and providing networking services for users and providing
administrative support for print, file, directory and e-mail servers.
Exit Management and Transition – Capacity Building at State
After the exit of the SI, State shall take up the management of CAS (State). Therefore before the exit of
the SI, State must be strengthened and capacity must be developed for State to manage CAS. The SI
must plan the capacity building initiative to enable State manage CAS, and will collaborate with
State to implement the plan.
The SI shall create a detailed plan for Capacity Building (CB) required at State to manage CAS and a
Transition Plan (implemented over a minimum period of three months) to affect the handover to State;
and implement the same in collaboration with State before the completion of their engagement.
ANNEXURE VI Service Levels
1. This document describes the service levels to be established for the Services offered by the SI
to the State. The SI shall monitor and maintain the stated service levels to provide quality
service to the State.
2. Definitions.
a. “Scheduled Maintenance Time” shall mean the time that the System is not in service due
to a scheduled activity as defined in this SLA. The scheduled maintenance time would not
be during 16X6 timeframe. Further, scheduled maintenance time is planned downtime with
the prior permission of the State.
b. “Scheduled operation time” means the scheduled operating hours of the System for the
month. All scheduled maintenance time on the system would be deducted from the total
operation time for the month to give the scheduled operation time. The total operation time
for the systems and applications within the Primary DC, DRC and critical client site
infrastructure will be 24X7X365. The total operation time for the client site systems shall
be 18 hours.
c. “System or Application downtime” means accumulated time during which the System is
totally inoperable within the Scheduled Operation Time but outside the scheduled
maintenance time and measured from the time the State and/or its employees log a call
with the SI team of the failure or the failure is known to the SI from the availability
measurement tools to the time when the System is returned to proper operation.
d. “Availability” means the time for which the services and facilities are available for
conducting operations on the State system including application and associated
infrastructure. Availability is defined as:
{(Scheduled Operation Time – System Downtime) / (Scheduled Operation Time)} * 100%
e. “Helpdesk Support” shall mean the 16x6 basis support centre which shall handle Fault
reporting, Trouble Ticketing and related enquiries during this contract.
f. “Incident” refers to any event / abnormalities in the functioning of the Data Centre
Equipment / Services that may lead to disruption in normal operations of the Data Centre,
System or Application services.
g. “Incident” refers to any event / abnormalities in the functioning of the Data Centre
Equipment / Services that may lead to disruption in normal operations of the Data Centre,
System or Application services.
3. Interpretations.
a. The business hours are 8:30AM to 4:30PM on all working days (Mon-Sat) excluding Public
Holidays or any other Holidays observed by the State. The SI however recognizes the fact
that the State offices will require to work beyond the business hours on need basis.
b. "Non-Business Hours" shall mean hours excluding “Business Hours”.
c. 18X7 shall mean hours between 06:00AM -12.00 midnight on all days of the week.
d. If the operations at Primary DC are not switched to DRC within the stipulated
timeframe (Recovery Time Objective), it will be added to the system downtime.
e. The availability for a cluster will be the average of availability computed across all the
servers in a cluster, rather than on individual servers. However, non compliance with
performance parameters for infrastructure and system / service degradation will be
considered for downtime calculation.
f. The SLA parameters shall be monitored on a monthly basis as per the individual SLA
parameter requirements. However, if the performance of the system/services is degraded
significantly at any given point in time during the contract and if the immediate measures
are not implemented and issues are not rectified to the complete satisfaction of the
State or an agency designated by them, then the State will have the right to take
appropriate disciplinary actions including termination of the contract.
g. A Service Level violation will occur if the SI fails to meet Minimum Service Levels, as
measured on a half yearly basis, for a particular Service Level. Overall Availability and
Performance Measurements will be on a monthly basis for the purpose of Service
Level reporting. An “Availability and Performance Report” will be provided by the SI on
monthly basis in the State suggested format and a review shall be conducted based on
this report. A monthly Availability and Performance Report shall be provided to the State at
the end of every month containing the summary of all incidents reported and associated SI
performance measurement for that period. The monthly Availability and Performance
Report will be deemed to be accepted by the State upon review and signoff by both SI and
the State. Where required, some of the Service Levels will be assessed through audits or
reports e.g. utilization reports, measurements reports, etc., as appropriate to be provided
by the SI on a monthly basis, in the formats as required by the State The tools to perform
the audit will need to be provided by the SI. Audits will normally be done on regular basis
or as required by the State and will be performed by the State or the State appointed third
party agencies.
h. EMS system shall play a critical role in monitoring the SLA compliance and hence will
have to be customized accordingly. The 3rd party testing and audit of the system shall put
sufficient emphasis on ensuring the capability of EMS system to capture SLA compliance
correctly and as specified in this RFP. The selected System Integrator (SI) must deploy
EMS tool and develop additional scripts (if required) for capturing the required data for
SLA report generation in automated way. This tool should generate the SLA Monitoring
report in the end of every month which is to be shared with the State on a monthly basis.
The tool should also be capable of generating SLA reports for a half-year. The State will
audit the tool and the scripts on a regular basis.
i. The Post Implementation SLAs will prevail from the start of the Operations and
Maintenance Phase. However, SLAs will be subject to being redefined, to the extent
necessitated by field experience at the police stations / higher offices and the
developments of technology practices globally. The SLAs may be reviewed on an
annual/bi-annual basis as the State decides after taking the advice of the SI and other
agencies. All the changes would be made by the State in consultation with the SI.
j. The SI is expected to provide the following service levels. In case these service levels
cannot be achieved at service levels defined in the tables below, it shall result in a breach
of contract and invoke the penalty clause. Payments to the SI are linked to the compliance
with the SLA metrics laid down in the tables below. The penalties will be computed and
calculated as per the computation explained in this Annexure. During the contract period, it
is envisaged that there could be changes to the SLA, in terms of addition, alteration or
deletion of certain parameters, based on mutual consent of both the parties i.e. the State
and SI.
k. Following tables outlines the key service level requirements for the system, which needs
be ensured by the SI during the operations and maintenance period. These requirements
shall be strictly imposed and either the State or a third party audit/certification agency shall
be deployed for certifying the performance of the SI against the target performance
metrics as outlined in the tables below.
Implementation Phase SLAs
1. Capacity Building
Service Level Description Measurement
Capacity Building At least 80% of the trainees within the training program
should give a rating of satisfactory or above.
Severity of Violation: High
This service level will be monitored and measured on a

per District basis through feedback survey to be provided
to each attendee within the program.
If the training quality in the program falls below the

minimum service level, it will be treated as one (1)
violation.
The total number of violations for the payment period will

be the cumulative number of violations across all the
programs across all Districts in the payment period.
2. Data Migration / Digitization
Service Level Description Measurement
Data Migration Error rate in a batch should be less than 0.5%.
This service level will be measured on a monthly basis for

each Police Station / Higher Office.
If the data migration service level in a police station /

higher office falls below the minimum service level, it will
be treated as one (1) violation.

police stations / higher offices in the payment period.
Digitization Error rate in a batch during verification should be less
than 0.5%.

each Police Station / Higher Office.
If error rate is between 0.5% and 1%, it is considered as

lower performance and if error rate exceeds 1% it will be
treated as one (1) violation.

police stations / higher offices in the payment period.
Delivery Related Service Level Agreement (SLA) Criteria
Explanation: The deduction mentioned in this table shall be made from the next due payment to the vendor for services provided on Statewide
basis.
S. Service Metrics Baseline Lower Performance Violation of Service level Basis of Remarks
No. Parameters agreement Measurement
Metric Metric Deduction Metric Deduction
1 Delivery of As per the One week Rs. 10,000 >1 week after Rs. 20,000 for Dates for
the reports/ dates as after the due the due date every week of delivery of
deliverables due mentioned in date delay reports as
for this section the contract mentioned in
the contract
Delivery Related Service Level Agreement (SLA) Criteria
Explanation: The deduction mentioned in this table shall be made from the next due payment to the vendor for services provided on Statewide
basis.
S. Service Metrics Baseline Lower Performance Violation of Service Basis of Remarks

No. level agreement Measurement
Parameters
Metric Metric Deduction Metric Deduction
1. Supply, 3 months 3-4 months For non- > 4 months For non- Months after The deduction
installation and compliance at compliance at taking over of shall be made
Commissioning of each point of each point of the office site per site basis,
hardware at deployment: deployment: for project where criterion
offices Rs. 30,000 Rs. 45,000 is not satisfied
2. Supply, 6 months 6-7 months Rs. 100,000 More than 7 Rs.100,000 Months taken State / UT may
installation and from the date months for every after beginning conduct
Commissioning of of signing of month of of the independent
the Data Center contract delay assignment Audit to verify
Equipment that the data
center is as per
the
specifications.
3. Capacity building At least 80% Less than Rs. 15,000 / Less than Rs. Feedback The feedback of
of the training 80% and training 60% of the 25,000 per survey to be the attendees
audience more than session attendees training provided to must be taken
should give a 60% Find the session each attendee after every
rating of attendees training training session
satisfactory find the satisfactory and this
or above training feedback should
satisfactory be leveraged for
improving the
capacity building
program
4. Data Digitization Error rate in Error rate Rs. 5,000/ Error rate of Rs. 10,000 / Error rate in a Error rate
a batch between 5% batch and over 10%. batch and the batch during is measured by
during - 10% correction of entire batch to verification percentage
verification records be re-done of the records
should be with corrections
less than 5% marked by
designated
officials
5. Maintenance All the issues Resolution of Rs. 500 Resolution of Rs. 1000 for Time and date
phase reported issues within the issue every day of reporting of
regarding 2 working after 2 delay over the issue
hardware, days of working days and above
software etc. reporting beyond
should be
resolved
within 24
hours (within
1 working
day)
3. Violations and Associated Penalties
a) The primary intent of Penalties is to ensure that the system performs in

accordance with the defined service levels. Penalties are not meant to be punitive or,
conversely, a vehicle for additional fees.
b) Penalty Calculations. The framework for Penalties, as a result of not meeting the
Service Level Targets are as follows:
i. The performance will be measured for each of the defined service level metric
against the minimum / target service level requirements and the violations will
be calculated accordingly.
ii. The number of violations in the reporting period for each level of severity will
be totaled and used for the calculation of Penalties.
iii. Penalties applicable for each of the high severity violations are 0.1% of
respective payment-period payment to the SI.
iv. Penalties applicable for each of the medium severity violations are 0.05% of
respective payment-period payment to the SI.
Post Implementation Phase SLAs
1. Primary DC/DRC Site Infrastructure Systems and Application Availability and

Performance
a) Production CAS Systems. The failure or disruption has a direct impact on the state/
UT’s ability to service its police stations / higher offices, ability to perform critical back-
office functions or a direct impact on the organization. This includes but not limited to:-
i. Storage and related switches at Primary DC and DRC.
ii. Web, Application, Database, and Backup Servers at Primary DC and DRC.
iii. Primary DC to DRC connectivity.
iv. Primary DC and DRC network infrastructure
v. Primary DC and DRC security infrastructure.
b) Non-CAS Systems in Production and Non Production Systems (Development, QA, and
Training). The failure or disruption has no direct impact on the State’s ability to serve its
police stations / higher offices, or perform critical back-office functions.
i. Production Non CAS Servers
ii. Test, QA and Training Servers
iii. Helpdesk infrastructure & applications.
iv. EMS Infrastructure.
c) CAS Solution Components. The failure or disruption has a direct impact on the State’s
ability to service its police stations / higher offices, ability to perform critical back-office
functions or a direct impact on the organization.
d) Non ERP Solution Components. The failure or disruption has no direct impact on the
State’s ability to serve its police stations / higher offices, or perform critical back- office
functions.
e) These service levels will be monitored on a monthly basis.
f) The below tables gives details on the Service Levels the SI should maintain.
Service Level Measurement
Description
Infrastructure Availability of production CAS systems shall be at least 99%
Availability
Availability over the Violations for calculation of

six- month period penalty
< 99% & >= 98.5% 1
< 98.5% & >= 98% 2
< 98% 3
In addition to the above, if the service level in any month in the six-
month period falls below 98%, one (1) additional violation will be
added for each such month to the overall violations for this service
level.
Availability of non-CAS systems in production and non-production

systems shall be at least 97%.
Severity of Violation: Medium

< 97% & >= 96.5% 1
< 96.5% & >= 96% 2
< 96% 3
level.
RTO shall be less than or equal to six (6) hours.
Each instance of non-meeting this service level will be treated as one

(1) violation.
RPO (zero data loss in case of failure of Primary DC) should be zero
minutes

Infrastructure Sustained period of peak CPU utilization of any server crossing 70%
Performance (with the exception of batch processing) shall be less than or equal to
30 minutes.
Each occurrence where the peak CPU utilization of any server

crosses 70% (with the exception of batch processing) and stays
above 70% for time more than 30 minutes will be treated as one (1)
instance.

Description
Number of instances over the Violations for calculation of
six month period penalty
>0 & <=3 1
>3 2
In addition to the above, if the number of instances in any month in

the six-month period exceeds 3, one (1) additional violation will be
level.
Sustained period of peak I/O utilization of any server crossing 70%

(with the exception of batch processing) shall be less than or equal to
30 minutes.
Each occurrence where the peak I/O utilization of any server crosses
70% (with the exception of batch processing) and stays above 70%
for time more than 30 minutes will be treated as one (1) instance.
>0 & <=3 1

>3 2
level.
Infrastructure Sustained period of peak memory utilization of any server crossing
Availability 70% (with the exception of batch processing) shall be less than or
equal to 30 minutes.
Each occurrence where the peak memory utilization of any

server crosses 70% (with the exception of batch processing) and
stays above 70% for time more than 30 minutes will be treated as
one (1) instance.

>0 & <=3 1
>3 2

level.

Description
Application Availability of non-CAS solution components measured within the
Availability Data
Center shall be at least 97% Severity of Violation: Medium
This service level will be monitored on a monthly basis.

< 97% & >= 96% 1
< 96% 2
level.
Application Average application response time during peak usage hours as

Performance measured from a client terminal within the Data Center shall not
exceed 4 seconds.
The list of critical business functions and peak usage hours will be
identified by the State during the Supply and System Integration
Phase.
Average application response Violations for calculation of

time over the six- penalty
month period
> 4s & <= 5s 2
> 5s & <= 6s 4
> 6s 5
In addition to the above, if the average turnaround time in any month

in the six-month period goes beyond 6s, one (1) additional violation
will be added for each such month to the overall violations for this
service level.
2. Client Site Infrastructure Systems
a) Critical Client Site Systems. The failure or disruption results in inability of the police
station / higher offices to service its dependent offices or perform critical back-office
functions. Critical client site infrastructure means the IT infrastructure at client site
which are shared by multiple users i.e., Core Switch, Core Routers, etc.
b) This service level will be measured on a monthly basis for each implementation site.
The below tables gives details on the Service Levels the SI should maintain.

Description
Client Site Availability of the critical client site infrastructure components at all
Systems the implementation sites shall be at least 99%
Availability
This service level will be measured on a monthly basis for each

implementation site.
If the availability in a month for an implementation site falls below the

minimum service level, it will be treated as one (1) violation.
The total number of violations for the six-month period will be the
cumulative number of violations across all the months across all sites
in the six-month period.
3. Handholding Support: Client Site Support
a) Level 1 Incident. The incident has an immediate impact on the State’s ability to service
its police stations / higher offices, to perform critical back-office functions or has a direct
impact on the organization.
b) Level 2 Incidents. The incident has an impact on the State’s ability to service its police
stations / higher offices that while not immediate, can cause service to degrade if not
resolved within reasonable time frames
c) The severity of the individual incidents will be mutually determined by the State and SI.
d) The scheduled operation time for the client site systems shall be the business hours of
the State.
e) This service level will be measured on a monthly basis for each implementation site.
f) The tables below give details of the Service Levels the SI is required to maintain.

Description
Client Site 80% of the Level 1 Incidents at each site should be resolved within 2
Support business hours from the time call is received / logged which ever is
Performance earlier. The maximum resolution time for any incident of this nature
shall not exceed 8 business hours.
This service level will be measured on a monthly basis for each

implementation site.
If the performance in a month for an implementation site falls below

the minimum service level, it will be treated as one (1) instance. The
total number of instances for the six-month period will be the
cumulative number of instances across all the months across all sites
in the six- month period.
Average number of instances per month = (Total number of instances

for the six-month period) / 6
Average number of instances per Violations for calculation of

month penalty

Description
>0 & <=4 1
>4 & <=8 2
>8 & <=12 3
>12 4
80% of the Level 2 Incidents at each site should be resolved within 6

business hours from the time a call is received / logged which ever is
earlier. The maximum resolution time for any incident of this nature
shall not exceed 48 hours.

each implementation site.
If the performance in a month for an implementation site falls below

the minimum service level, it will be treated as one (1) instance. The
total number of instances for the six-month period will be the
cumulative number of instances across all the months across all sites
in the six- month period.
Average number of instances per month = (Total number of instances

for the six-month period) / 6
Average number of instances per Violations for calculation of
month penalty
>0 & <=4 1
>4 & <=8 2
>8 & <=12 3
>12 4
Replacement of hardware equipment shall be done within 7 days of

notification by the State. These equipments would have failed on four
or more occasions in a period of less than three months or six times
in a period of less than twelve months. (Mean Time Between Failure
Condition)

(1) violation.
4. Handholding Support: Application Support
a) Level 1 Defects. The failure to fix has an immediate impact on the State’s ability to
service its police stations / higher offices, inability to perform critical back-office
functions or a direct impact on the organization.
b) Level 2 Defects. The failure to fix has an impact on the State’s ability to service its
police stations / higher offices that while not immediate, can cause service to degrade if
not resolved within reasonable time frames.
c) Level 3 Defects. The failure to fix has no direct impact on the State’s ability to serve its
police stations / higher officers, or perform critical back-office functions.
d) The severity of the individual defects will be mutually determined by the State and SI.
e) This service level will be monitored on a monthly basis.
f) The below tables gives details on the Service Levels the SI should maintain.

Description
Application 95% of the Level 1 defects shall be resolved within 4 business hours
Support from the time of reporting full details.
Performance
Performance over the six- Violations for calculation of

month period penalty
< 95% & >= 90% 1
< 90% & >= 85% 2
< 85% 3
level.
95% of the Level 2 defects shall be resolved within 72 hours from the
time of reporting full details.

< 95% & >= 90% 1
< 90% & >= 85% 2
< 85% 3
level.
100% of the Level 3 defects shall be resolved within 120 hours from
the time of reporting full details.


Description
< 100% & >= 90% 1
< 90% & >= 80% 2
< 80% 3
level.
Up to date of the documentation of the design, modifications,
enhancements, and defect-fixes in the half-yearly period.
This service level will be measured on a half-yearly basis.

(1) violation.
5. Handholding Support: Helpdesk and Data Center Support
a) Level 1 Calls. The failure to fix has an immediate impact on the State’s ability to service
its police stations / higher offices, inability to perform critical back-office functions or a
direct impact on the organization.
b) Level 2 Calls. The failure to fix has an impact on the State’s ability to service its police
stations / higher offices that while not immediate, can cause service to degrade if not
resolved within reasonable time frames.
c) Level 3 Calls. The failure to fix has no direct impact on the State’s ability to serve its
police stations / higher offices, or perform critical back-office functions.
d) This service level will be monitored on a monthly basis.
e) The below tables gives details on the Service Levels the SI should maintain.

Description
Helpdesk 98% of the calls shall be answered within 45 seconds.
Performance

month period Penalty
< 98% & >= 90% 1
< 90% & >= 80% 2
< 80% 3

Description
level.
98% of the incidents within helpdesk resolution capacity shall
be resolved in a cycle time of 24 hours

< 98% & >= 90% 1
< 90% & >= 80% 2
< 80% 3
level.
98% of the non SI supported incidents shall be routed to the

appropriate service provider within 30 minutes.

< 98% & >= 90% 1
< 90% & >= 80% 2
< 80% 3
level.
80% of the Level 1 calls shall be resolved within 2 hours from call
received / logged which ever is earlier. The maximum resolution time
for any incident of this nature shall not exceed 8 business hours.
Performance over the Violations for calculation of

< 80% & >= 70% 1
< 70% & >= 60% 2

Description
< 60% 3
level.
80% of the Level 2 calls shall be resolved within 6 hours from call
received / logged which ever is earlier.
The maximum resolution time for any incident of this nature shall
not exceed 48 hours.

< 80% & >= 70% 1
< 70% & >= 60% 2
< 60% 3
level.
80% of the Level 3 calls shall be reported on status and action to be
communicated within 24 hours from call received / logged which ever
is earlier. The maximum resolution time for any incident of this
nature shall not exceed 72 hours.

< 80% & >= 70% 1
< 70% & >= 60% 2
< 60% 3
level.

Description
Datacenter Replacement of hardware equipment shall be done within 15 days of
Support notification by the State. These equipments would have failed on
Performance four or more occasions in a period of less than three months or six
times in a period of less than twelve months. (Mean Time Between
Failure Condition)
Each instance of non-meeting this service level will be treated as

one (1) violation.
Datacenter Up to date of the documentation of the design, modifications,
Support enhancements, and fixes.
Performance
This service level will be measured on a half-yearly basis.
Each instance of non-meeting this service level will be treated as

one (1) violation.
6. Reporting
a) The below table gives details on the Service Levels the SI should maintain for client site
systems availability.

Description
Availability and Provide monthly SLA compliance reports, monitoring and
Performance maintenance related MIS reports by the 5th of the following month.
Report
If the monthly SLA compliance report related to the service

level metrics is not provided in the given timeframe, it will be treated
as one (1) instance.
The total number of instances for the six-month period will be the
cumulative number of instances across all the months in the six-
month period.
Total number of instances Violations for calculation of

over the six month period penalty
>0 & <=3 1
>3 2
7. Credits for Successful Application Uptake
The below table gives details of the credits that can be gained by the SI for successful uptake
of the application in the State. The credits will not be calculated for the first reporting period.

Description
CCTNS Uptake The following metrics will be measured at the end of each reporting
period for each District that has been declared as “Go Live”:
1. Number of key transactions carried through internet (ex:

Transactional such as submitting an application for a no-
objection certificate and Informational such a requesting the status
of a case)
2. Number of active users profiles in State CAS
3. Number of read-write transactions on State CAS system
4. Number of Searches carried out on data in State CAS
5. Total number of FIRs prepared through State Cas
6. Total number of Crime Details Forms prepared through
State CAS
7. Total number of Key Investigation Forms prepared through
State CAS
8. Total number of Arrest Cards prepared through State CAS
9. Total number of Charge Sheets prepared through State CAS
10. Quality (recency and accuracy) of information available in
State CAS
11. Number of cases reported to be solved because of the
availability of State CAS
12. Number of ad-hoc requests successfully responded to using
State CAS
13. Turnaround Time for submitting the monthly and annual
crime/criminal information to NCRB from the State
A credit will be gained for each of the above parameters if the

uptake for that parameter shows significant improvement.
The following table applies for each of the above parameters:
% increase over the Credits

measurement in the last
reporting period
>5 & <=10% 2
>10 & <=15% 3
> 15% 4
8. Violations and Associated Penalties

a) The primary intent of Penalties is to ensure that the system performs in
accordance with the defined service levels. Penalties are not meant to be punitive or,
conversely, a vehicle for additional fees.
b) A six monthly performance evaluation will be conducted using the six monthly reporting
periods of that period.
c) Penalty Calculations.: The framework for Penalties, as a result of not meeting the
Service Level Targets is as follows:
i. The performance will be measured for each of the defined service level
metric against the minimum / target service level requirements and the
violations will be calculated accordingly.
ii. The number of violations in the reporting period for each level of severity
will be totaled and used for the calculation of Penalties.
iii. If the total number of credits gained by the SI is lower than the total
number of high severity violations in the reporting period, the total
number of credits will be subtracted from the total number of High
Severity Violations in the reporting period for the calculation of Penalties.
iv. If the total number of credits gained by the SI is higher than the total
number of high severity violations in the reporting period, the resultant total
number of high severity violations in the reporting period for calculation of
penalties will be considered as zero (0).
v. Penalties applicable for each of the high severity violations are two (2) % of
respective half yearly payment to the SI.
vi. A penalty applicable for each of the medium severity violations is one (1%)
of respective half yearly payment to the SI.
vii. Penalties applicable for each of the low severity violations is half
percentage (0.5%) of respective half yearly payment to the SI.
viii. Penalties applicable for not meeting a high (H) critical performance target
in two consecutive half years on same criteria shall result in additional
deduction of 5% of the respective half yearly payment to the SI
Penalty shall be applicable separately for each such high critical activity
ix. Penalties applicable for not meeting a medium (M) critical performance
target in two consecutive half yearly periods on same criteria shall result in
additional deduction of 3% of the respective half yearly payment to the SI.
Penalty shall be applicable separately for each such medium critical
activity
x. Penalties applicable for not meeting a low (L) critical performance target in
two consecutive half yearly periods on same criteria shall result in
additional deduction of 2% of the respective half yearly payment to the SI.
Penalty shall be applicable separately for each such medium critical
activity
xi. It is to be noted that if the overall penalty applicable for any of the review
period during the currency of the contract exceeds 25% or if the overall
penalty applicable for any of the successive half year periods during the
currency of the contract is above 15%; then the State shall have the right
to terminate the contract.
ANNEXURE VII Network Connectivity Solution
The Networking solution of CCTNS project shall be based on a Hybrid Model which will consist of
Tamil Nadu State Wide Area Network (TNSWAN) operated by ELCOT under SWAN scheme and
Data network operated by Bharat Sanchar Nigam Limited (BSNL) which consists of Point to point
leased lines, VPNoBB and MPLS technologies. BSNL shall be providing the Networking &
Connectivity services along with Operations & Maintenance for all the locations implemented by
BSNL in Tamil Nadu.
BSNL shall also provide connectivity on MPLS VPN network for aggregated bandwidth at the Tamil
Nadu State Data Center (TNSDC) for the locations connected on VPNoBB and also provide
connectivity for TNSDC at Chennai to the National Data Centre (NDC) of NCRB. Further BSNL
shall provide MPLS VPN network for connecting TNSDC and Disaster Recovery Centre (DRC) for
CCTNS Project to be positioned at State Data Centre, Kerala, located in Trivandrum.
Scope of work for BSNL: The details of scope of work of BSNL are as under:
a) Provisioning of 256 kbps/512 kbps VPNoBB connectivity to Police Stations

including the 25 remote and inaccessible Police Stations which presently do not
have broadband connection available. The list of these inaccessible locations is
as mentioned below:
S.No DISTRICT POLICE STATION
1. Vellore Panamadangai
2. Thiruvalam
3. Kavalur
4. Villupuram Thirupalaipandal
5. Cuddalore Thukkanampakkam
6. Maruthur
7. Coimbatore Pillur Dam
8. Tiruppur Tiruppur Rural
9. Erode Burgur
10. Kadambur
11. Salem Kariyakovil
12. Perambalur Venganur
13. Karur Balaviruthi
14. Pudukottai Udayallipatti
15. Theni Kurangani
16. Tirunelveli Vijanarayanapuram
17. Manjolai
18. Kuruvikulam
19. Sivanthipatti
20. Thirukkankudi
21. Sivalaperi
22. Thoothukudi Kadalkudi
23. SP, PTC, Perurani
24. Manimutharu TSP-X Battalian
25. TSP-XII Battalian
b) Provisioning of the Routers (at CCTNS site) and Modems for locations to be
connected directly with MPLS VPN and all other hardware and network
infrastructure provided for VPNoBB connectivity.
c) Provisioning of Aggregated bandwidth on MPLS VPN network at each
States/UTs SDC for the locations connected on VPNoBB network.

d) Provisioning of MPLS VPN connectivity between TNSDC and DRC.
e) Provisioning of MPLS VPN connectivity between NDC and TNSDC
f) Maintaining the network including hardware supplied for minimum period of 3
years.
SLA of 99% uptime would be provided for MPLS VPN connectivity. SLA for the sites
connected through VPN on Broadband will be 97%
Role of System Integrator: The SI shall coordinate with BSNL and the State/UT Police
Department for implementation of the Network and Connectivity solution of CCTNS
project.
The following are the key responsibilities of the SI with respect to Networking and
Connectivity.
i. Site preparation at all locations for establishment and installation of
networking and connectivity solution.
ii. Coordination with the State Police Department and nominated
officials of BSNL for Installation, Configuration, Testing and
Commissioning of BSNL’s 2Mbps MPLS VPN links and 256/512
kbps VPNoBB links.
iii. Coordination with BSNL for ensuring Operations and Maintenance of
networking hardware to ensure compliance to the SLAs as offered
by BSNL.
iv. The SI will also be coordinating with BSNL and State Police
Department for SLA Monitoring, Fault Reporting & Troubleshooting
of the links for meeting the Service levels and Master Service
Agreement.
v. SI shall also coordinate with State CCTNS Nodal Officer (ADGP,
SCRB) for finalizing Police stations lists for the connectivity options,
issuing commissioning report for demand note/payment clearance,
reporting SLA and providing for link status updates.
Note: The process of finalization for signing of contract with BSNL as Service provider for CCTNS
project is in progress and detailed guidelines on implementation of Networking and Connectivity will
be sent to all States/UTs.
ANNEXURE VIII Indicative Technical Specifications
Personal Computer for each of the police stations:
Personal Computers
Features Specifications
Processor Intel Core i5 2400 (3.10 Ghz, 6MB L3 Cache) 4 core processor
Chipset Intel Q67 Express Chipset
Motherboard OEM Motherboard
2 GB DDR3 PC3- 6400 (1066 Mhz) Non ECC RAM expandable up to 16
RAM
GB (4 DIMM Slots minimum)
250 - GB SATA 3.0 Gb/s Hard Drive (16 MB Cache, 7200 RPM, NCQ
Hard Disk Drive &
Smart -IV)
controller
Serial Advanced Technology Attachment (SATA) Super Multi Light
Optical Drive
Scribe DVD Writer Drive
Graphics Intel HD Graphics 2000 - Integrated
Audio Inel HD Audio - Integrated
Gigabit 10/100/1000 Network card with remote booting facility
Ethernet
External : 2 * 5.25" drive bays ; Internal : 2* 3.5" drive bays
Bays
Minimum 3 PCI / PCI express slots
Slots
Ports :6 * USB 2.0 (4 in front + 2 in rear), 1* VGA, 1* Line in , 1* Line
Ports out, 1* RJ 45
300-watt ATX Power Supply – PFC (Active Power Factor Correction

Power Supply
(PFC) power supply). Surge Tolerance of upto 2000V
Keyboard PS/2 104 keys keyboard (Same make as PC)
Monitor 18.5 ‘’ LCD monitor with TCO 5.0 Certification
Mouse PS/2 2 Button Optical Scroll Mouse(Same make as PC)
Operating System NIC Linux – To Be Provided by NIC
Office Productivity
LibreOffice 3.3 3 / Star Office / Libre Office
Application
Compliance And
As per industry standard for Monitor and PC
Certification
Drivers for different
Drivers should be supplied along with the PC
Operating systems
ISO 9001-14001, ISO 9001-2008, Greenpeace International, Should be
OEM Certifications in the in the list of top 5 desktop brands as per IDC report published for
India during year 2010.
Warranty 5 years comprehensive onsite replacement warranty.
Duplex Laser Printers

Feature Specification
Speed (min.) 20 PPM / 23PPM (A4)
Memory(min.) 32 MB / 64 MB
Resolution 1200x1200 dpi
Interface USB, Ethernet (UTP) with respective cables
Monthly Duty Cycle 10000 Pages
Language PCL6 / PS2 or higher
Print Mode Automatic Duplex Mode
Cartridge Full Cartridge- Starter Cartridge not acceptable
Drivers Windows 2000, Windows XP, Windows Vista, Windows 7, MAC OS
9.0, MAC OS X, Linux Kernel 2.6 or later
Multi - function Laser (Print/Scan/Copy)

Speed (min.) 20 PPM / 23PPM (A4)
Memory(min.) 32 MB / 64 MB
Resolution 1200x1200 dpi
Interface USB, Ethernet (UTP) with respective cables
Monthly Duty Cycle 10000 Pages
Language PCL6 / PS2 or higher
Accessories Copier, Scanner with ADF
Drivers Windows 2000, Windows XP, Windows Vista, Windows 7, MAC OS
Digital Pad & Pen

Pad Size 336mm (length) x 245mm (width)
Writing Area 210mm x 279mm
Notepad holder 210mm x 300mm
Built-in memory 32MB or more
Memory slot Secure Digital
Digital pen size 134mm x 11.3mm (diameter)
Digital page file DHW; DND
formats
OS Supported Windows 2000, Windows XP, Windows Vista, Windows 7, MAC OS
Interface USB 1.0 & 2.0
Finger print reader

Sensor Type Optoelectronic
Prism Architecture Dual Prism
Size of Window minimum 45mm x 45mm preferable up to 45mm x 48mm
Glass Thickness 25mm
Resolution 500 PPI or higher
Image grey scale 256 level Dynamic
Scanning time 0.01Sec.
Distortion rate 0.1%
Computer interface USB2.0, USB Powered
Operating 0-55 Degree C
temperature
Environmental Up to 90%
humidity
Optical/Film Coating Hygroscopic
Operating system Linux
Support
Compliant P. I. V
Digital Camera
Effective Megapixels 10 megapixels or Higher
Image sensor CMOS / CCD
Image sensor size 0.400 inches or larger
Image format JPEG /RAW
White balance Auto & Manual
Image Stabilization Hardware
Maximum Optical 4 X or Higher
Zoom
Maximum Wide Angle 28 mm
Minimum aperture 8
Maximum aperture 2
LCD screen size 3 inches or higher
Has live preview Yes
Maximum shutter 2500
speed
Minimum shutter 15
speed
ISO Low 100
ISO High 3200
Exposure settings Aperture Priority & Shutter Priority
Memory Capacity Minimum 2 GB
Memory type SD Memory Card / SDHC Memory Card / SDXC Memory Card
Flash characteristics Built-in Auto Flash
Flash Slow Sync / Red-Eye Reduction
Maximum video 1280 x 720 pixels
capture resolution
Maximum frame rate 30 Frames per Second
Video capture format MOV/AVI
Interface connection USB 1.0 & 2.0
Battery Type Lithium Ion/ AA Battery
Rechargeable Yes
Windows 2000, Windows XP, Windows Vista, Windows 7, MAC OS
160 GB External Hard Disk Drive

Capacity 160 GB
Type External
Interface USB 2.0 & USB 1.1
Spindle Speed 5400 RPM
Buffer Size 8 MB
Seek Time 12 ms
Transfer Rate 60 Mega Bytes /s
Form Factor 2.5"
OS Support Windows 2000, Windows XP, Windows Vista, Windows 7, MAC OS
16 Port Switch – Unmanaged

Standards IEEE 802.3 10BASE-T Ethernet
IEEE 802.3u 100BASE-TX Fast Ethernet
ANSI/IEEE 802.3 NWay auto negotiation
Protocol CSMA/CD
Data Transfer Rates Ethernet
10Mbps (half-duplex)
20Mbps (full-duplex)
Fast Ethernet:
100Mbps (half-duplex)
200Mbps (full-duplex)
Network Cables 10BASE-T: UTP Cat. 3, 4, 5 (100 m) EIA/TIA-586 100-ohm STP
(100 m)
100BASE-TX: UTP Cat. 5 (100 m) EIA/TIA-568 100-ohm STP (100m
max.)
Number of Ports 10/100Mbps port x 16
Twisted-pair Rx Auto-correction for each port
Reverse Polarity
MAC Address Automatic update
Learning
RAM Buffer 4MBits per device
Power Supply 100 - 240 VAC, 50/60 Hz 0.3A Internal power supply
16 Port Switch - Managed

Interface Ports 16 10/100/1000BASE-T Auto-negotiating, Auto-MDI/MDI-X ports
with 802.3x Flow Control
Performance 32Gbps
Switch Capacity
Packet Forwarding 23.8Mpps or above
Rate
MAC Address Table 8K
Size
MAC Address Update Up to 256 static MAC entries Enable/disable auto-learning of MAC
addresses
Packet Buffer 512KB
Power Input 100 to 240 VAC 50/60Hz Internal power supply
Port Standards and IEEE 802.3 10BASE-T Ethernet
Functions IEEE 802.3u 100BASE-TX Fast Ethernet
IEEE 802.3ab 1000BASE-T Gigabit Ethernet
IEEE 802.3z Gigabit Ethernet (fiber) ANSI/IEEE 802.3

IEEE 802.3x Flow Control
Auto-Negotiation
802.3af Power over Ethernet
LAYER 2 Features IGMP v1/2 Snooping: supports 64 multicast groups
802.1D Spanning Tree
Static Port Trunk (Link Aggregation): up to 6 groups per device, up
to 8 ports per group
VLAN 802.1Q VLAN (VLAN Tagging)
Up to 256 static VLAN groups
Management VLAN
Asymmetric VLAN
Quality of Service 802.1p Priority Queues
(QoS) Up to 4 queues per port
DSCP-based QoS
Security 802.1X Port-based Access Control
Broadcast Storm Control
Trusted Host
Cable Diagnostics function
Management Web-based GUI
SNMP v1 support
DHCP Client
Trap setting for destination IP, system events, fiber port events,
twisted-pair port events
Port Access Control
Web-based: Configuration backup/restoration
Web-based: Firmware backup/upload
System Reboot using web-based interface
UPS – 2 KVA online UPS (for each police station)

Power Rating 2 kVA/ 1.6 kW/ 0.8 PF with 60 min backup
Technology True On-Line Double Conversion Architecture
Nominal input 220/230/240 Vac
voltage (Vac)
Input voltage 160-288 VAC
Range
Operating 50/60 Hz auto sensing
Frequency
Nominal output 208/220/230/240 VAC
Voltage
Output voltage +/-3% online; +/-3% on battery mode
Regulation
Overload Up to 110 % for 2 minute, 111-150% for 30 sec
Capacity
Efficiency 85% (On-Line mode)
>93% (High efficiency mode)
Load Crest 3:1
Factor
LED 3 LEDs indicating UPS status
5 Alarm/Bar Graph indicators
Standard RS232
Communication
ports
Optional Slots SNMP, Multiserver card, relay card , Modbus card
Form Factor Dual Form Factor – Should be placed either as Rack mount or
Tower. Height Should not exceed 2U for rack mount purpose

Battery Type Sealed, lead-acid, maintenance-free
Battery Runtime The system must be capable of providing 60 minutes of battery
Back-up time.
(Minimum VAH= 2952 AH for 60 minutes back up)
Exide / Amaron / Luminous
Total number of batteries offered should be clearly mentioned.
Voltage of each battery offered should be clearly mentioned Ampere-
Hour rating of each battery offered should be clearly mentioned. Total
Volt-Ampere-Hour rating of the Battery Bank Offered should be clearly
mentioned.
Battery Modular, hot-swappable, user-replaceable
Replacement
Start-On-Battery Should allow startup of UPS without utility input
Operating 0°C - +40°C
Temperature
Storage Temp Recommended 0°C - +25°C
Altitude < 3000 M
Audible Noise <45 dB battery mode
RoHS Should be EU RoHS / WEEE Compliant
Compliance
Markings CE
Safety EN 50091-1 / equivalent
EMC EN 50091-2 /equivalent
Quality ISO 9001, ISO 14001
UPS – 5 KVA online UPS (for each District SP Office and Higher Offices)
Power Rating 5 kVA/ 4 kW/ 0.8 PF with 60 min backup
Technology True On-Line Double Conversion Architecture
Nominal input 220/230/240 Vac
voltage (Vac)
Input voltage 160-288 VAC
Range
Operating 50/60 Hz auto sensing
Frequency
Nominal output 208/220/230/240 VAC
Voltage
Output voltage +/-3% online; +/-3% on battery mode
Regulation
Overload Up to 110 % for 2 minute, 111-150% for 30 sec
Capacity
Efficiency 85% (On-Line mode)
>93% (High efficiency mode)
Load Crest 3:1
Factor
LED 3 LEDs indicating UPS status
5 Alarm/Bar Graph indicators
Standard RS232
communication
ports
Optional Slots SNMP, Multiserver card, relay card , Modbus card
Form Factor Dual Form Factor – Should be placed either as Rack mount or
Tower. Height Should not exceed 2U for rack mount purpose
Battery Type Sealed, lead-acid, maintenance-free
Battery Runtime The system must be capable of providing 60 minutes of battery

Back-up time.
(Minimum VAH= 7800 AH for 60 minutes back up)
Exide / Amaron / Luminous
Total number of batteries offered should be clearly mentioned.

Voltage of each battery offered should be clearly mentioned Ampere-
Hour rating of each battery offered should be clearly mentioned. Total
Volt-Ampere-Hour rating of the Battery Bank Offered should be clearly
mentioned.
Battery Modular, hot-swappable, user-replaceable
Replacement
Start-On-Battery Should allow startup of UPS without utility input
Operating 0°C - +40°C
Temperature
Storage Temp Recommended 0°C - +25°C
Altitude < 3000 M
Audible Noise <45 dB battery mode
RoHS Should be EU RoHS / WEEE Compliant
Compliance
Markings CE
Safety EN 50091-1 / equivalent
EMC EN 50091-2 /equivalent
Quality ISO 9001, ISO 14001
Specifications for Sine Inverter (3 KVA) (for each Police Station)

Under Voltage 100 +/- 10 V
INPUT
Over Voltage 285 +/- 10 V
Voltage (INVERTER Mode) 230 V Nominal
Voltage (Mains Mode) Same as Input
Frequency (INVERTER Mode) 50 Hz. +/- 2%
OUTPUT
Frequency (Mains Mode) Same as Input (45-55 Hz.)
Overload > 110 %
Transfer Time (typical a.s) 10 ms.
Type 12V/135 AH Tubular
Number 4 in series
BATTERY Typical Recharge Time 10-12 Hrs.
Battery Deep Discharge,
Protection Reverse Polarity, DC
Overvoltage
Inverter ON
Battery Low
Mains On
Battery Charged
Overload
LED DISPLAY No Load
Over Temperature
Short Circuit under Battery
Mode
MCB Trip or Short Circuit under
Mains Mode
Low Battery Pre-Alarm
Low Battery
ALARMS Overload
No Load Shut Down
Short Circuit
Operating Temperature 0-45o C (32-113 o F)
ENVIRONMENTAL Storage Temperature 0-45o C (32-113 o F)
Humidity 0-95 % RH non -condensing
Specifications for Tubular Battery (for each Police Station)

Nominal Capacity Electrolyte BOOST MODE TRICKLE
Voltage Volume in MODE
Litres Starting Finishing Min Max
(Minimum) Rate Rate
12 135AH 11.0 12.0 6.0 108 432
Specifications for Handheld Device for Data Access and Communication (for Intelligence Unit
Office and Intelligence Headquarters)
S.No Details Specification

1 System Software Win 6.5 or latest, Linux or Android (minimum 2.1)
2 CPU Arm 9 core 32 bit (500 MHz or Higher )OR Latest Intel PXA270
(520 MHz or higher)
3 Monitor Basic Screen parameter TFT, Color screen, 320*240 pix, 4:3
aspect ratio, 3.5 inch QVGA, high-definition capacitive touch
screen, At least 64K color (65,536 colors)
4 Full Radio GSM
Communication
GPRS
EDGE
3G/W-CDMA
Should work with 2.5G/3G data services being offered / to be
launched by various mobile service providers in India.
Bluetooth Class 2.0
Wi-Fi 802.11 b/g
Integrated GPS
5 Battery Rechargeable Li-ion / Li-Po
3.7V or higher upto 7.2V
1500mAH or higher with 230V AC Adaptor & Vehicle Cigarette
Lighter Charging Adaptor
Device should have Minimum 8 hrs Battery backup with GPRS
activated.
6 ROM/NAND Flash 256 MB Minimum 128 MB Minimum user space available,
7 RAM 256 MB Minimum configured scalable to 512 MB
8 SD card Slot SDIO support/SD Card Support
9 Input Full QWERTY with Stylus for Touch screen Input
10 Interface Data Cable Support, USB 2.0 Host & Client
11 Ruggedness IP 67
Should be able to withstand at least 4 feet drops on concrete
floors on all edges and on screen.
The TFT screen and device should be scratch resistant.
12 Java Java Support
13 Messaging SMS
MMS
E-Mail
Push E-Mail
14 GPS Channels:20,,Reqcquire:0.1sec avg.
Sensitivity:159DBm
Reqcquire:0.1sec avg.
Hot Start :1 Sec, average
Warm Start:38 Sec, average
Cold Start: 42 sec, average
15 Camera Camera 5 mega-pixel (Minimum)
Image Format - JPEG
Auto focus Lens
Facility to shoot video (24fps minimum)
Video Format – AVI/MP4/WMV
16 Finger Print Scanner 500 dpi or higher Optical Sensor
for Biometric Access
S.No Details Specification

Effective Area :14mm x 20
Minex compliant ISO templates
FAR:0.0001%
FRR:0.01%
UIDAI compliant
17 Signature Pad Integrated Pad & Stylus
18 Voice Recorder Standard Voice recorder facility
19 Additional Rugged carrying case with belt clip and with all required
Accessories connecting cable and vehicle charger.
An existing Screen protector along with an additional one.
20 Warranty 5 Years
21 Kill Option In case of a lost mobile, facility to destroy data from remote
location
22 Environmental Operating Temperature 0°C to 50°C
Parameter Storage Temp 0°C to 60°C
Operating Humidity 10-90% non-condensing
23 Certification ISO 9001
24 Agency Approvals FCC,ICS, CSA,IEC
25 Real time clock & Device should have real time clock so that time of device will not
Network Time change even if battery is removed.
Protocol (NTP) The device should also support time synchronization using NTP
support or SNTP.
26 Security Feature Facility to create guest account at device so that user will not be
able to do any unnecessary modifications
27 Diagnostic features Device should have network diagnostic features like PING,
TRACE ROUTE etc.
28 Antivirus protection Device should have licensed Antivirus Software.
b. Application Platform, Operating System and Server Hardware
S. No. Server description Hardware OS Application

1 Web Server internet users x86 family Ubuntu / PHP/J2EE
CentOS
2 Web server intranet users X86 family Ubuntu / Apache HTTP Server
CentOS
3 Directory Server Access X86 Ubuntu / Free Open Source
Manager with DNS & CentOS Solution (FOSS)
client authentication
license server
4 Application Server/Portal X86 Ubuntu / FOSS

CentOS
5 Data Base server X 86 Ubuntu/ PostgreSQL
CentOS
i. Technical Specification for Network Equipment:
Core Distribution switch:

 For Distribution Layer, two numbers of Distribution Multilayer switch proposal should come
with the standard architecture with Firewall service module with Active & standby units.
Should have at least 6 modules.
Switch Architecture  Distribution data switch consisting of One Management
module
 Core data switch consisting of One Management module
 All modules should be provided with distributed forwarding
capability.
 3x48 port 10/100/1000 module.
 2x24 Gigabit Fiber interfaces modules with support of
100BASE FX (Multi Mode) & 100BASE-BX (Single Mode)
 Redundant power source to meet the full power
requirements including the expanded load in future.
 The Core Data / Distribution Data Switch should have the
following features & requirements and Scalable with full
expansion capability, Number of Slots – Minimum of 6
slots.
Performance Specifications  Backplane Bandwidth should be minimum 600 Gbps in a
Single chassis.
 Layer 3 Forwarding Performance of up to 350 Mpps
 Redundant Management Modules with stateful failover.
Failure of one CPU should not affect the performance of
the switch. Redundant module of similar capacity.
 The Security features should support port filtering,
enabling of individual ports to access only selected nodes,
IP permit lists to prevent unauthorized access to the
switch, Access Control Lists (ACL) to secure networks
from unauthorized users, authentication and secure
communications over un -secure channels for access to
the network
Layer 2 Features  802.1Q, Centralized VLAN management and
configuration.
 Number of VLANS: - >=4000
 802.1 p/q - VLAN Tagging
 802.3x - Flow Control
 Support for features like Uni-Directional Link Detection. In
case of one of the Cores fiber cut, the switch should detect
uni -directional transmission and shut down the port to
avoid loops and help bring up the backup links.
 Ethernet IEEE 802.3, 10 Base T
 Fast Ethernet (IEEE802.3u, 10/100 Base-TX, 100 Base
FX, 1000 Base FX)
 Gigabit Ethernet-(IEEE 802.3z, 802.3ab)
 Support for 10 Gigabit Ethernet ( IEEE 802.3ae)
Layer 3 Features  Layer 3 or 4 switching and routing
 Port Mirroring
 L2, L3 and L4 access control filters. L3/L4 frame
classification
 VRRP or equivalent for High Availability
 Rapid Spanning Tree Protocol (RSTP)(802.1w)
 Rapid convergence Layer 3 protocols
 802.1s - Per-VLAN Group Spanning Tree Protocol
 Support for IP routing features for Static,RIPv1,
BGPv4,OSPFv2,IS-IS, IGMP v1,v2,v3
 IGMP v1,v2,v3
 Protocol-Independent Multicast (PIM)-SM
 RFC 1075 - DVMRP v3-07,
 PIM (Protocol Independent Multicast)
 IP Version 6 (IPv6) support in hardware.
Quality of Service Features  Enterprise wide QoS management: LAN to WAN
integration
 Traffic Classification: Physical Port, IP DA/SA, IP
DA/SA/L4 Port
 Admission Control: IP DA/SA, IP DA/SA L4, RSVP
 Traffic Marking: Diffserv, IEEE 802.1Q/P COS, IPv4 ToS,
via ACLs
 Congestion Avoidance: WRED, multiple Queue
Thresholds
 Scheduling IP precedence, 802.1p and ISL priority, three
transmit queues on a per port basis, WRR, Strict Priority
Queue TOS<->COS mapping
 Micro-Flow Policing (limits BW of specific user/application)
 Aggregate-Flow Policing (dedicated BW per customer
SLA)
 Excess-Rate Policing (permits traffic bursts, enables
granular priority Values/service-level)
 Strict-Priority Queue (protects mission-critical, delay-
sensitive traffic)
Security Features  Port based and policy based VLAN & Spanning tree
 Network ingress filtering - RFC 2267
 IP broadcast forwarding control
 Rate limiting using ACLs
 Uni cast Reverse Path Forwarding (RPF)
 SYN attack protection
 Session control
 RADIUS
 Support for Server load balancing with Layer 3 and Layer
4 protection
 No impact on packet forwarding performance
Wire rate Access Control Lists  Standard/Extended
 Reflexive (stateful)
 Dynamic (time of day)
 IP permit lists
 MAC address filtering based on Source and Destination
Address
 Bi-directional VACL per VLAN Community
 Traps and Syslog messages sent on security violations
 Private VLAN support
 802.1x Network Security and Authentication.
 Support for the 802.1x standard allows users to be
authenticated regardless of which LAN port they are
accessing, and provides unique benefits to customers who
have a large base of mobile (wireless) users accessing the
network.
 802.1x with VLAN assignment allows a dynamic VLAN
assignment a specific user regardless of where the user is
connected.
 802.1x with voice VLAN to permit an IP phone access to
the voice VLAN Irrespective of the authorized or
unauthorized state of the port.
 802.1x with port security for authenticating the port and
managing network access for all MAC addresses,
including that of the client.
 IP Access Lists to limit telnet and SNMP access.
 SSH, RADIUS, AAA for login authentication
 Support for Local Command Accounting and logging.
 DHCP and BOOTP relay
 Standard DNS support
 Per port broadcast, Unicast and Multicast storm control
 Dynamic trunking protocol for the automatic configuration
of required trunking Protocol on the ports, without
manually configuring it
Network Management features  Web based
 Telnet and TFTP access
 RMON - Remote Monitoring (RMON) with 4 RMON groups
(history, statistics, Alarms and events).
 SNMP agent – SNMPv1, SNMPv2c, SNMPv3, Port
snooping and connection steering
Layer 2 switch
General Features  The switch should have minimum 24 x 10/100/1000
Gigabit Ethernet Ports & 4 X dual –purpose Uplinks (four
SFP-based Gigabit Ethernet ports).
 Support for Redundant Power supply.
Performance  16 Gbps switching fabric
 Wire-speed forwarding rate - 6.5 Mpps
 Configurable up to 8000 MAC addresses
Layer-2 Features  IEEE 802.1Q VLAN encapsulation. Up to 255 VLANs
should be supported. Support for 4000 VLAN IDs.
 Support for Automatic Negotiation of Trunking Protocol, to
help minimize the configuration & errors.
 Support for Centralized VLAN Management.
 Spanning-tree Enhancements for fast convergence
 IEEE 802.1d, 802.1s, 802.1w, 802.3ad
 Spanning-tree feature to prevent other edge switches
becoming the root bridge.
 IGMP snooping v3, Support for upto 255 IGMP Groups.
IGMP filtering.
 Link Aggregation Protocol (LACP)
 Support for Detection of Unidirectional Links (in case of
fiber cut) and to disable them to avoid problems such as
spanning-tree loops.
 The Switch should be able to discover the neighboring
device of the same vendor giving the details about the
platform, IP Address, Link connected through etc, thus
helping in troubleshooting connectivity problems.
 Per-port broadcast, multicast, and storm control to prevent
faulty end stations from degrading overall systems
performance.
 Local Proxy Address Resolution Protocol (ARP) to work in
conjunction with Private
 VLAN Edge to minimize broadcasts and maximize
available bandwidth
Quality of Service (QoS) &  Standard 802.1p CoS and DSCP
Control  Control- and Data-plane QoS ACLs
 Four egress queues per port to enable differentiated
management of up to four traffic types across the stack.
 Weighted tail drop (WTD) to provide congestion avoidance
 Strict priority queuing mechanisms
 There should not be any performance penalty for highly
granular QoS functions.
 Rate Limiting function should guarantee bandwidth in
increments as small as 1Mbps.
Management  Superior manageability features.
 Command Line Interface (CLI) support for configuration &
troubleshooting purposes.
 For enhanced traffic management, monitoring, and
analysis, upto four RMON groups (History, statistics,
alarms, and events) must be supported.
 Layer 2 trace route to ease troubleshooting by identifying
the physical path that a packet takes from source to
destination.
 Domain Name System (DNS) support to provide IP
address resolution with user-defined device names.
 Trivial File Transfer Protocol (TFTP) to reduce the cost of
administering software upgrades by downloading from a
centralized location.
 Network Timing Protocol (NTP) to provide an accurate and
consistent timestamp to all intranet switches.
 SNMP v1, v2c, and v3 and Telnet interface support
delivers comprehensive in –band management, and a CLI-
based management console provides detailed out -of-band
management.
 RMON I and II standards
 SNMPv1, SNMPv2c, and SNMPv3
Core Router:
Architecture  Should be chassis based & modular architecture for
scalability and should be a single Box configuration for
ease of management.
 Architecture should be modular / distributed and should be
a single box configuration for ease of management.
 Multi Service Router (Data, Voice, Video)
 Should have power supply redundancy. A single power
supply should be able to support a fully loaded chassis.
 The offered platform should be able to support the
following interface types –
 Serial port with synchronous speed up to 2
Mbps with interface V.35/G.703,
Channelized E1 interfaces for provisioning
nx64Kbps connectivity
 E3 & DS3, STM1 for high speed interface
requirements, Channelized STM -1
Interfaces for aggregating multiple 2Mbps
interfaces onto a single Channelized
Interface.
 Ethernet Interfaces –GE (1000 Base X) as
per IEEE 802.3z and 802.3ab, FE as IEEE
802.3u,
 512 MB RAM and should be upgradeable to 1GB
 Should have 256 MB Flash
 Should have adequate memory to support all OS feature
 Should have IPSEC VPN (3DES/AES) Encryption
Features.
Interface Requirements  6 x V.35/G703 Serial Interfaces (along with necessary
cables) to Aggregate WAN links from Districts &
Aggregation Buildings.
 8X1 Channelized E1 Interfaces.
 4 x 1 Gigabit Ethernet Interfaces for LAN connectivity.
 Single channel wire speed shall be minimum of 15 Mpps
and router throughput should be minimum 10 GBPS.
 Should support performance services like NAT, GRE
tunneling, ACL (Standard & Extended) , all industry
standard routing protocol.
 Shall have MLPPP for link aggregation
 Shall have Voice traffic optimization
Performance  Shall support at least 150 Kpps forwarding performance
 Shall support variety of interfaces like
 V.35 Sync Serial, (2 Mbps), E1 G.703, Ch -E1
 GE as per IEEE 802.3z and 802.3ab, FE as per
IEEE 802.3u,
 ISDN BRI and PRI and Router should have auto
dial Backup capability for
 ISDN when primary Lease line is down.
 Shall support DSL connectivity using ADSL, G.SHDSL for
Horizontal office connectivity.
 Shall have support performance enhancement through
hardware based encryption
 Shall support other IP Services like ACLs.
 Shall support Voice traffic optimization with features like
LFI
High Availability  Router should have redundant CPU & Shall support
Redundant Power supply
 Shall support On-line insertion and removal for cards.
 Shall support Non-Stop forwarding for fast re-convergence
of routing protocols (BGP, OSPF, IS-IS)
 Should support VRRP.
 Shall support redundant connection to LAN
 Shall support VRRP or equivalent
Protocol Support  Shall support Routing protocols like RIP ver1 (RFC1058) &
2 (RFC 1722 and 1723), OSPF ver2 (RFC2328), BGP4
(RFC1771), IS-IS (RFC1195).
 Multicast routing protocols support: IGMPv1, v2 (RFC
2236), PIM -SM (RFC2362).
 Should have Dual Stack IPv4 & IPv6 protocols.
 Shall have IPv6 features
 Shall have RIPng and OSPFv3 for IPv6.
QoS Features  Classification and Marking: Policy based routing, IP
Precedence, DSCP.
 Congestion Management: WRED, Priority queuing,
 Traffic Conditioning: Committed Access Rate/Rate limiting
 Signaling: RSVP for Bandwidth reservation
 Link efficiency mechanisms: cRTP/LFI/DiffServ MLPPP
Security Features  Should have GRE Tunneling, NAT without any major
performance impact.
 Support for Firewall,
 MD-5 route authentication for RIP, OSPF, IS-IS and BGP
 SNMPv3 authentication
 AAA support using Radius
 PAP / CHAP authentication for P-to-P links
 Support for DoS prevention, DoS protection
 IP Access list to limit Telnet and SNMP access to router
 Shall support multi-level of access. Multiple privilege
authentications for Console and telnet access through local
database or through a separate AAA Server.
Debug, Alarms & Diagnostics  Support for monitoring of Traffic flows for Network planning
and Security Purposes.
 Display of input and output error statistics on all interfaces
 Display of Dynamic ARP table
 Trace-route, Ping and extended Ping for testing &
troubleshooting connectivity.
 Should have extensive support for SLA monitoring for
metrics like delay, latency, Jitter, packet loss,
Management  Shall have support for Web based management, C LI,
Telnet and SNMPv3
 Shall support Secure Shell for secure connectivity.
 Embedded RMON support for four groups – history,
statistics, alarms and events
Interface Requirements  2 * E1
 4 * Gigabit Ethernet Interfaces (1000 Base X) to connect to
the LAN. (That will be used for Broadband peer
connectivity)
 4 * V.35 / G703 Serial (2 Mbps) Interfaces (along with
necessary cables).
 1* console port.
 1* BRI for ISDN backup with auto Dial – backup
Performance  Shall support at least 150 Kbps forwarding performance
 Shall support variety of interfaces like
 V.35 Sync Serial, (2 Mbps), E1 G.703, Ch -E1
 GE as per IEEE 802.3z and 802.3ab, FE as per
IEEE 802.3u,
 ISDN BRI and PRI and Router should have auto
dial Backup capability for
 ISDN when primary Lease line is down.
 Shall support DSL connectivity using ADSL, G.SHDSL for
Horizontal office connectivity.
 Shall have support performance enhancement through
hardware based encryption
 Shall support other IP Services like ACLs.
 Shall support Voice traffic optimization with features like
LFI
Server Load Balancer

10/100/1000Mbps Ethernet Ports  minimum 2 ports upgradeable to 4 ports
Memory  Minimum 1 GB upgradeable to 8 GB
 Minimum of 2 Gbps throughput
 Minimum of 1 Gbps SSL throughput
Connections  Minimum of 4000 SSL connections scalable to 7500 SSL
connections
Server Load Balancing  Cyclic, Hash, Least numbers of users
Mechanism  Weighted Cyclic, Least Amount of Traffic
 NT Algorithm / Private Algorithm / Customizable Algorithm
/ Response Time
Redundancy Features  Supports Active-Active and Active-Standby Redundancy
 Segmentation / Virtualization support along with resource
allocation
Server Load Balancing Features  Server and Client process coexist
 UDP Stateless
 Service Failover
 Backup/Overflow
 Direct Server Return
 Client NAT
 Port Multiplexing-Virtual Ports to Real Ports Mapping
 DNS Load Balancing
Load Balancing Applications  Application/ Web Server, MMS, RTSP, Streaming Media
 DNS, FTP- ACTIVE & PASSIVE, REXEC, RSH,
 LDAP, RADIUS
SLB should support Management  Secure Web Based Management
options  SSH
 TELNET
 SNMP v1, 2, 3 Based GUI
 Command Line
ii. Specifications for Data Centre Infrastructure
Blade Chassis Specification

 Single blade chassis should accommodate minimum 6 (Quad core Processor) / 8
(Dual core Processor) or higher hot pluggable blades.
 Processor should be latest series/generation for the server model being quoted
 6U to 12U Rack-mountable
 Dual network connectivity for each blade server for redundancy should be
provided. Backplane should be completely passive device. If it is active, dual
backplane should be provided for redundancy
 Should accommodate Intel, AMD, RISC / EPIC Processor based Blade Servers for
future applications
 Should have the capability for installing industry standard flavours of Windows,
Linux, Unix, Solaris for x86 Operating Environments
 Single console for all blades in the enclosure or KVM Module DVD ROM can be
internal or external, which can be shared by all the blades allowing remote
installation of S/W and OS
 Minimum 2 external USB connections functionality
 Two hot-plug, redundant 1Gbps Ethernet module with minimum 10 ports
(cumulative), which enable connectivity to Ethernet via switch. Switch should be
(Internal/external) having Layer 3 functionality - routing, filtering, traffic queuing etc
 Two hot-plugs, redundant 4 Gbps Fiber Channel for connectivity to the external
 Fiber channel Switch and ultimately to the storage device.
 Power Supplies
o Hot Swap redundant power supplies to be provided
o Power supplies should have N+N. All Power Supplies modules should be
populated in the chassis
 Hot Swappable and redundant Cooling Unit
 Management
o Systems Management and deployment tools to aid in Blade Server
configuration and OS deployment,
o Remote management capabilities through internet browser
o It should provide Secure Sockets Layer (SSL) 128 bit encryption and
Secure Shell (SSH) Version 2 and support VPN for secure access over
internet.
o Ability to measure power historically for servers or group of servers for
optimum power usage
o Blade enclosure should have provision to connect to display console /
central console for local management like trouble shooting, configuration,
system status / health display
 Built in KVM switch or Virtual KVM feature over IP.
 Dedicated management network port should have separate path for management
Support heterogeneous environment: AMD, Xeon and RISC/EPIC CPU blades must be in same
chassis with scope to run Win2003/2008 Server, Red Hat Linux/ 64 Bit UNIX, Suse Linux / 64 Bit
UNIX / Solaris x86
Blade Server Hardware for Date Center location & Disaster recovery (Web, Portal,
Application)
Form Factor 6U to 12U Rack-mountable
Processor 2 Quad core @ 2.0 GHz or above with 4 MB shared L2 cache, 1066
MHz / 2000 MT/s FSB
Max CPU support Server should have 2 CPU at least.
RAM Std / Max Min 64 GB FBD RAM with min 8 Nos. free slots for future
expandability to 256 GB.
Drive controller SAS/SCSI
NIC 2 X (1000BASE-T) Tx Gigabit LAN ports with TCP / IP offload engine
support /dedicated chipset for network I/O on blade server
Hard Drive 4 X 146 GB SAS 10K RPM SAS or better Hot Plug Drives with RAID5
I/O expansion At least two expansion slots for FC or additional Gigabit cards
Slots
OS Certification Required
Operating system CentOS
The Operating System for all the servers should have the following
features: Unlimited virtualized guests. Multiple operating systems,
multiple versions, multiple performance and security settings, all
running on the same server.
Storage virtualization: Multiple guests, running on the same or

different servers, access and share logical storage volumes and file
systems.
High availability clustering and failover: Application and guest

operating system failover.
Management: Includes comprehensive management capabilities.

Support: Unlimited incident support on Telephone, Email & Web with
4 hours response time directly from OS vendor.
Upgrades: Free upgrade during support period

Apart from the above the authentication server shall have these
additional features:
 Centralizes management of people and their profiles, thus
reducing administrative costs;
 Should act as a central repository for user profiles and
preferences, enabling personalization;
 Should allows 4-way multi-master replication of data across
the enterprise, providing a centralized, consistent data source
available to enterprise applications
 Should enables single sign-on access with a partner solution
 Should be able to provide scalability for massive numbers of
users by containing the information control required for
developing extranet applications
OEM Certification ISO 9001-14001, ISO 9001-2008, Greenpeace International, Should
be in the in the list of top 5 desktop brands as per IDC report
published for India during year 2010.
Blade Server Hardware for Date Center location & Disaster recovery (Infrastructure Services
like EMS, Backup, DNS, Antivirus)
Processor 2 Quad core @ 2.0 GHz or above with 4 MB shared L2 cache, 1066
MHz / 2000 MT/s FSB
NIC 2 X (1000BASE-T) Tx Gigabit LAN ports with TCP / IP offload engine
support /dedicated chipset for network I/O on blade server
Slots

systems.



Blade Server Hardware for Date Center location & Disaster recovery (Database)
Processor Minimum 4x Quad core processor with 2.1GHz or above with
1066Mhz FSB / 2000 MT /s expandable to 4 physical processor with
min 4 MB L3 cache per processor
NIC At least 4 x 10/100/1000 Mbps Ethernet ports or more
Slots

systems.



iii. Cabling CAT6, Fiber MM/ SM Technical Specs
CAT-6 U/UTP Cable

 4 Pair Cable, 23 AWG Copper with integral cross -member pair separator for uniform
characteristic impedance.
 Standardization: ISO/IEC 11801 2nd Ed.; IEC 61156-5 2nd Ed.; EN 50173-1; EN 50288-6-
1; EIA/TIA 568B.2.1
 Cable overall diameter 6.3 mm.
 Cable jacket material : PVC
 Should have tensile strength of 100N.
 The cable should have 100ohm impedance and data transmission frequencies up to
250MHz.
 It should be certified by independent test labs like 3P/Delta to meet Cat -6 Standards.
 The cable should be supplied in 500m reel.
Mechanical Test
Ultimate Breaking Strength >400 N (90 lbf)
Minimum Bend Radius ≥35mm without load, ≥55mm with load
Electrical Test
DC Resistance ≤14.5Ω/100 m
DC Resistance Unbalance ≤2%
Mutual Capacitance 4.4pF/100m max.
Capacitance Unbalance ≤150pF/100m max.
Propagation Velocity 67%
Connection Module/Information Outlet

 RJ45 connection module of Category 6, for the establishing of transmission channels of
class E with up to 4 plugged connections, complies with Category 6 requirements of the
standards ISO/IEC 11801:2002, EN 50173-1: May 2007, DIN EN 50173-1: Dec. 2007 as
well as ANSI/TIA/EIA 568-B.2-1, de-embedded tested in acc. with IEC 60603-7-4,
interoperable and backwards compatible with Cat.5e and Cat.5.
 Suitable for 10GBase-T applications in acc. with IEEE 802.3an up to 500 MHz and 55 m.
 Parallel pair termination without crossover in acc. with EIA/TIA 568-A/B, gold-plated bronze
contacts for >1000 mating cycles, IDC contacts with single-wire strain relief and >20
insertion cycles, contact resistance <50 m Ohm, dielectric strength >1000 Veff..
 Maximum reliability through special contact design without internal transfer points.
 Should have integral dust cover and integrated bend-limiting strain -relief unit for cable
entry.
 Should have IDC to hold conductor without using any tool for termination of cable.
 Outlets should be of single metal piece design without any PCB to support the IDC /
Contacts.
 Should be reusable and tool less in design in terms of termination of solid wire installation
cable AWG22-24 as well as stranded cables AWG 22/7 – 26/7
 Should be made of halogen free material and should be certified by third party like 3P or
Delta or GHMT.
Patch Panel 24 port- Straight
 Patch panel with integrated cable tie shelf, 19" fastening kit, labeling field, accepting the
snap-in type color coding clips in 8 colors.
 Material: sub-rack made of sheet steel (DC01A) 1.5 mm, color blue achromatized, screen
made of plastic (ABS), halogen-free, color medium gray (NCS 2502-B)
 Complies with Category 6 requirements of the standards ISO/IEC 11801:2002, EN 50173-

1: May 2007, DIN-EN 50173-1: Dec. 2007 as well as ANSI/TIA/EIA 568-B.2-1, de-
embedded tested in acc. with IEC 60603-7-4, interoperable and backwards compatible with
Cat.5e and Cat.5.
 Suitable for 10GBase-T applications in acc. with IEEE 802.3an up to 500 MHz and 55 m in
case of unshielded.
 Each port should be individually terminated i.e. each Port should be individually
replaceable & provide consistent port-to-port performance.
 Each port should have an integral dust cover and integrated bend-limiting strain relief unit
for cable entry.
 Patch panels shall be modular in design and capable of supporting Cat 6 UTP/FTP and
S/FTP modules on same port. The same panel should have the capability of terminating
multimode and single mode fibers alongside the copper terminations.
Patch Cord UTP
 Standardization: Compliant with Cat.6, Class E (250 MHz) requirements: ISO/IEC 11801
2nd Edition Compliant with Cat.6 component standards IEC 60603-7-4 and 60603-7-5
 Patch Cords should have PVC jacket with conductor diameter copper strand AWG26.
 Patch cords to use IDC contact technology for all the conductor terminations for better
performance and not piercing type contact technology.
 Cat 6 patch cord plug to have metal screening & round cable holder and strain relief boot to
avoid bending.
 Plug to have two physically separated levels and all 8 wires need to be separated by
dielectrically.
 Should support optional locking mechanism for security purpose wherein the patch cords
can be locked on servers and all RJ45 ports and required Mechanical key to open patch
Cord.
 All the conductors should be IDC based termination at the RJ-45 plugs without directly
crimping the plug on cable.
iv. Networking & Server Rack
Feature Required specification

Feature 42U 800W X 800D Modular Structures made from aluminum extruded
profile, minimum extrusion wall thickness at all sides and corner- 2mm.
along with following items: Top and Base Cover with cable enter Black
Color
Front/Rear Front, Glass door, 800mm Wide, 42U, with Lock and hexagonal vent on
Door the trims for thermal Management/ air cooling. 42U , 800mm W, Rear
Steel Door, with 1/3 hexagonal vent at the base to allow proper air flow
and thermal control, with Lock
Mounting 19” Mounting Angles, 19” mounting angles powder coated along with “U”
Angles marking
SIDE PANELS 2 Nos. of Removable Side Panels along with slam latch. 4 nos. of
100mm W, Reducing Cable channels on the sides to allow better cable
management
Castors Castors - For providing mobility to the rack. Two with foot operated
brakes and Two without brakes, having a load carrying capacity of
100kg
Fan 230V AC 90CFM Fan (4 nos. for each Rack) with Fan Housing Unit
Cable Manager 19”, 1U, Horizontal Cable Manager, to allow proper cable routing
Cable Loops 24U to help route the cable vertically
Power Supply 10X 5 amps or 6 X 5 amps socket as per requirement
Castors Castors as needed
Cable Storage 2U cable storage shelf supported with 4 bobbins
Power Consumption Not more than 5 KVA
Redundancy Mechanical Devices such as Hard Disks, Fans and Power Units should
be completely Hot Swappable and Redundant to ensure High
Availability
Power Guaranteeing complete availability even on failure of any 2 power units
across the enclosure. Sufficient Power to run a fully loaded enclosure in
N+N redundant mode.
KVM/CD/USB/Floppy To be enabled Virtually over IP for Remote Access or Provided Locally.
Multi-platform Enclosure should support Xeon & RISC/EPIC blade on the
Support Same chassis. Enclosure should also support Unix, Linux and Windows
Operating environment
1. Enterprise Management and Monitoring Solution (EMS) Basic Requirements

 Solution should be inclusive with hardware, OS, patches, etc.
 Solution should provide for future scalability of the whole system without major
architectural changes.
 Should be SNMP v1, v2, v3 and MIB-II compliant.
 Filtering of events should be possible, with advance sort option based on
components, type of message, time etc.
 Should support Web / Administration Interface.
 Should provide compatibility to standard RDBMS.
 Solution should be open, distributed, and scalable and open to third party
integration.
 Should provide fault and performance management for multi-vendor TCP/IP
networks.
Security
 Should be able to provide secured windows based consoles / secured web- based
consoles for accessibility to EMS.
 Should have web browser interface with user name
and Password Authentication.
 Administrator/ Manager should have privilege to create/modify/delete user
Polling Cycle
 Support discriminated polling
 Should be able to update device configuration changes such as re-indexing of ports
 Fault Management
 Should be able to get fault information in real time and present the same in alarm
window with description, affected component, time stamp etc.
 Should be able to get fault information from heterogeneous devices — routers,
switches, servers etc.
 Event related to servers should go to a common enterprise event console where a

set of automated tasks can be defined based on the policy.
 Should have ability to correlate events across the entire infrastructure
components of DC/DR.
Discovery
 Should support automatic event correlation in order to reduce events occurring in
DC/DR.
 Should support advanced filtering to eliminate extraneous data / alarms in Web
browser and GUI.
 Should be configurable to suppress events for key systems/devices that are down
for routine maintenance or planned outage.
 Should be able to monitor on user-defined thresholds for warning/ critical states and
escalate events to event console of enterprise management system.
 Should provide out of the box root cause analysis with multiple root cause
algorithms inbuilt for root cause analysis.
 Should have self-certification capabilities so that it can easily add support for new
traps and automatically generate alarms.
 Should provide sufficient reports pertaining to asset and change management,
alarms and availability of critical network resources as well as network response
times for critical links.
 The tool shall integrate network, server and database performance information and
alarms in a single console and provide a unified reporting interface for network and
system components. The current performance state of the entire network and
system infrastructure shall be visible in an integrated console.
 Should provide an integrated performance view for all the managed systems and
networks along with the various threshold violations alarms in them. It should be
possible to drill-down into the performance view to execute context specific
reports
 Should provide the following reports for troubleshooting, diagnosis, analysis and
resolution purposes: Trend Reports, At-A-Glance Reports, & capacity prediction
reports
 Should provide accurate discovery of layer 3 and heterogeneous LAN and
Presentation
 Should be able to discover links with proper colour status propagation for
complete network visualization.
 Should support dynamic object collections and auto discovery. The topology of the
entire Network should be available in a single map.
 Should give user option to create his /or her map based on certain group of devices
or region.
Agents
 Should provide custom visual mapping of L2 and L3 devices connectivity and
relationships.
 Should monitor various operating system parameters such as processors, memory,

files, processes, file systems etc. where applicable using agents on the servers to
be monitored.
 Provide performance threshold configuration for all the agents to be done from a
central GUI based console that provide a common look and feel across various
platforms in the enterprise. These agents could then dynamically reconfigure them
to use these threshold profiles they receive.
System Monitoring
 Should be able to monitor/manage large heterogeneous systems environment
continuously.
 Windows
o Should monitor / manage following:
 Event log monitoring
 Virtual and physical memory statistics
 Paging and swap statistics
 Operating system
 Memory
 Logical disk
 Physical disk
 Process
 Processor
 Paging file
 IP statistics
 ICMP statistics
 Network interface traffic
 Cache
 Active Directory Services
o Should be capable of view/start/stop the services on windows servers
 Unix / Linux
o Should monitor with statistics :
 CPU Utilization, CPU Load Averages
 System virtual memory (includes swapping and paging)
 Disk Usage
 No. of Nodes in each file system
 Network interface traffic
 Critical System log integration
 Infrastructure Services
o IIS / Tomcat / Apache / Web server statistics
o HTTP service
o HTTPS service
o FTP server statistics
o POP/ SMTP Services
o ICMP services
o Database Services – Monitor various critical relational database management
system (RDBMS) parameters such as database tables / table spaces, logs

etc.
 Application Performance Management
o End to end Management of applications (J2EE/.NET based)
o Determination of the root cause of performance issues whether inside the
Java application in connected back-end systems or at the network layer.
o Automatic discovery and monitoring of the web application environment
o Ability to monitor applications with a dashboard.
o Ability to expose performance of individual SQL statements within
problem transactions
o Monitoring of third-party applications without any source code
change requirements.
o Proactive monitoring of all end user transactions; detecting failed
transactions; gathering evidence necessary for problem diagnose.
o Storage of historical data is for problem diagnosis, trend analysis etc.
o Monitoring of application performance based on transaction type
o Ability to identify the potential cause of memory leaks.
Reporting
 Should able to generate reports on predefined / customized hours.
o Should be able to present the reports through web and also generate “pdf” /
CSV/ reports of the same.
o Should provide user flexibility to create his /or her custom reports on the
basis of time duration, group of elements, custom elements etc.
o Should provide information regarding interface utilization and error statistics
for physical and logical links.
o Should create historical performance and trend analysis for capacity
planning.
o Should be capable to send the reports through e-mail to pre-defined user with
pre defined interval.
o Should have capability to exclude the planned-downtimes or downtime
outside SLA.
o Should be able to generate all sorts of SLA Reports.
o Should be able to generate web-based reports, historical data for the
systems and network devices and Near Real Time reports on the local
management console.
o Should be able to generate the reports for Server, Application, infrastructure
services and Network devices in DC/DR environment.
 Availability Reports
o Availability and Uptime – Daily, Weekly, Monthly and Yearly Basis
o Trend Report
o Custom report
o MTBF and MTTR reports
 Performance Reports
o Device Performance – CPU and Memory utilized
o Interface errors
o Server and Infrastructure service statistics
o Trend report based on Historical Information
o Custom report
o SLA Reporting
o Computation of SLA for entire DC/DR Infrastructure
o Automated Daily, Weekly, Monthly, Quarterly and Yearly SLA reports
 Data collection
o For reporting, required RDBMS to be provided with all licenses.
o Should have sufficient Storage capacity should to support all reporting data
for 5 Years of DC/DR operation.
 Integration
o Should be able to receive and process SNMP traps from infrastructure
components such as router, switch, servers etc.
o Should be able integrate with Helpdesk system for incidents.
o Should be able to send e-mail or Mobile –SMS to pre-defined users for pre-
defined faults.
o Should trigger automated actions based on incoming events / traps. These
actions can be automated scripts/batch files.
Network Management
 The Network Management function must monitor performance across heterogeneous
networks from one end of the enterprise to the other.
 It should proactively analyze problems to improve network performance.
 The Network Management function should create a graphical display of all
discovered resources.
 The Network Management function should have extensive reporting facility,
providing the ability to format and present data in a graphical and tabular display
 The Network Management function should collect and analyze the data. Once
collected, it should automatically store data gathered by the NMS system in a
database. This enterprise-wide data should be easily accessed from a central
location and used to help with capacity planning, reporting and analysis.
 The Network Management function should also provide information on
performance of Ethernet segments, including capacity utilization and error statistics
for the segment, WAN links and routers.
 Alerts should be shown on the Event Management map when thresholds are
exceeded and should subsequently be able to inform Network Operations Center
(NOC) and notify concerned authority using different methods such as pagers,
emails, etc.
 It should be able to automatically generate a notification in the event of a link failure
to ensure proper handling of link related issues.
 The Systems and Distributed Monitoring (Operating Systems) of EMS should be able
to monitor:
o Processors: Each processor in the system should be monitored for
CPU utilization. Current utilization should be compared against user-
specified warning and critical thresholds.

o File Systems: Each file system should be monitored for the amount of
file system space used, which is compared to user-defined warning and
critical thresholds.
o Log Files: Logs should be monitored to detect faults in the
operating system, the communication subsystem and in applications.
The function should also analyze the files residing on the host for
specified string patterns.
o System Processes: The System Management function should
provide real-time collection of data from all system processes. This
should identify whether or not an important process has stopped
unexpectedly. Critical processes should be automatically restarted
using the System Management function.
o Memory: The System Management function should monitor memory
utilization and available swap space.
o Event Log: User-defined events in the security, system, and
application event logs must be monitored.
SLA Monitoring
 The SLA Monitoring function of the EMS is by far the most important requirement
of the DC/DR Project. The SLA Monitoring component of EMS will have to
possess the following capabilities:
o EMS should integrate with the application software component of
portal software that measures performance of system against the
following SLA parameters:
 Response times of Portal;
 Uptime of data centre;
 Meantime for restoration of Data Centre etc;
Reporting
 The EMS should compile the performance statistics from all the IT systems
involved and compute the average of the parameters over a quarter, and
compare it with the SLA metrics laid down in the RFP.
 The EMS should compute the weighted average score of the SLA
metrics and arrive at the quarterly service charges payable to the Agency after
applying the system of penalties and rewards.
 The SLA monitoring component of the EMS should be under the control of the
authority that is nominated to the mutual agreement of Director, the partner so
as to ensure that it is in a trusted environment.
 The SLA monitoring component of the EMS should be subject to random third
party audit to vouchsafe its accuracy, reliability and integrity.
 The Reporting and Analysis tool should provide a ready-to-use view into
the wealth of data gathered by Management system and service management
tools. It should consolidate data from all the relevant modules and transform
it into easily accessible business-relevant information. This information, should
be presented in a variety of graphical formats can be viewed interactively
 The tool should allow customers to explore the real-time data in a variety
of methods and patterns and then produce reports to analyze the associated
business and service affecting issues.
 The presentation of reports should be in an easy to analyze graphical
form enabling the administrator to put up easily summarized reports
to the management for quick action (Customizable Reports). The software
should be capable of supporting the needs to custom make some of the reports
as per the needs of the organization.
 Provide Historical Data Analysis: The software should be able to provide a
time snapshot of the required information as well as the period analysis of the
same in order to help in projecting the demand for bandwidth in the future.
ITIL based Helpdesk System

 Helpdesk system would automatically generate the incident tickets and log the
call. Such calls are forwarded to the desired system support personnel deputed
by the Implementation Agency. These personnel would look into the problem,
diagnose and isolate such faults and resolve the issues timely. The helpdesk
system would be having necessary workflow for transparent, smoother and
cordial DC/DR support framework.
 The Helpdesk system should provide flexibility of logging incident manually via
windows GUI and web interface.
 The web interface console of the incident tracking system would allow viewing,
updating and closing of incident tickets.
 The trouble-ticket should be generated for each complaint and given to asset
owner immediately as well as part of email.
 Helpdesk system should allow detailed multiple levels/tiers of categorization on
the type of security incident being logged.
 It should provide classification to differentiate the criticality of the security incident
via the priority levels, severity levels and impact levels.
 It should allow SLA to be associated with a ticket based on priority, severity,
incident type, requestor, asset, location or group individually as well as
collectively.
 It should maintain the SLA for each item/service. The system should be able to
generate report on the SLA violation or regular SLA compliance levels.
 It should be possible to sort requests based on how close are the requests to
violate their defined SLA’s.
 It should support multiple time zones and work shifts for SLA & automatic ticket
assignment.
 It should allow the helpdesk administrator to define escalation policy, with
multiple levels & notification, through easy to use window GUI / console.
 System should provide a knowledge base to store history of useful incident
resolution.
 It should have an updateable knowledge base for technical analysis and further
help end-users to search solutions for previously solved issues.
 The web-based knowledge tool would allow users to access his / her knowledge
article for quick references.
 It should provide functionality to add / remove a knowledge base solution based
on prior approval from the concerned authorities
 Provide seamless integration to generate events/incident automatically from NMS
/ EMS.
 Each incident could be able to associate multiple activity logs entries manually or
automatically events / incidents from other security tools or EMS / NMS.
 Allow categorization on the type of incident being logged.
 Provide audit logs and reports to track the updating of each incident ticket.
 Proposed incident tracking system would be ITIL compliant.
 It should be possible to do any customizations or policy updates in flash with zero
or very minimal coding or down time.
 It should integrate with Enterprise Management System event management and
support automatic problem registration, based on predefined policies.
 It should be able to log and escalate user interactions and requests.
 It should support tracking of SLA (service level agreements) for call requests
within the help desk through service types.
 It should be capable of assigning call requests to technical staff manually as well
as automatically based on predefined rules, and should support notification and
escalation over email, web etc.
 It should provide status of registered calls to end-users over email and through
web.
 The solution should provide web based administration so that the same can be
performed from anywhere.
 It should have a customized Management Dashboard for senior executives with
live reports from helpdesk database.
NOTE: EMS tools deployed shall have the ability to manage the entire IT infrastructure proposed
by the SI
2. Compliance Management, Web Access Management & Privileges Users

Management for Server Access Control
Privileges Users Management for Server Access Control

Tamil Nadu State Data Centre currently has Privileged User Management Solution for Server Access
Control. SI needs to procure additional licenses of Privileges User Management Solution to secure
the critical infrastructure under the current project scope.
Web Access Management

Tamil Nadu State Data Centre currently has Access Manager as the Web Access Management and
Web Single Sign on Solution. SI needs to procure additional licenses to secure the critical
infrastructure under the current project scope.
Compliance Management
Tamil Nadu State Data Centre currently has Compliance Management Suite as the Role,
Compliance and Identity Management and Access Management Solution .SI needs to procure
additional licenses of Compliance Management Suite to secure the critical infrastructure under the
current project scope.
3. Storage and Backup Solution
SAN Switches – 2 nos.
 Minimum 16 Active ports (each with minimum port speed 4 GB) within same
switch upgradeable to 32 ports with minimum 2 Nos. of additional 10 Gbps FC
ports
 All cable of length of 10 meter each and accessories for connecting Servers
/Devices to SAN.
 Should have capability of ISL trunking of minimum 8 ports.
 Should support multiple OS.
 Non disruptive subsystem maintenance.
 Should have dual Fans and Hot plug power supplies switching and service
modules.
 Should have web based management software for administration and
configuration.
 Non disruptive microcode / firmware upgrades and hot code activation.
 Switch shall support in built diagnostics, power on self test, command level
diagnostics, online and offline diagnostics.
 Should support hardware ACL based Port security, Port Zoning and LUN Zoning
 Should support Secure Shell (SSH) encryption to provide additional security for
Telnet sessions to the switch.
 Should support multilevel security on console access prevent unauthorized users
from altering the switch configuration
 Should support Fibre Channel trace route and Fibre Channel Ping for ease
of troubleshooting and fault isolation
 Should support the following diagnostics:
o Online Diagnostics
o Internal Loopbacks
o FC Debug
o Syslog
o Online system health
o Power on self test (POST) diagnostics
 Should support Applications for device management and full fabric
management. The management software shall be able to perform following:
o Fabric View
o Summary View
o Physical View
o Discovery and Topology Mapping
o Network Diagnostics
o Monitoring and Alerts
Storage Area Network – 1 no.
Technical Specification for SAN
 The storage Box to be connected with the servers through SAN switches.
 Redundant SAN switches
 Separated Tape library.
 Intel based processor.
 SAN cabling with on direct OM3 Fiber patch cords.
 SAN controller
o Dual Active Active Controller
 Cache
o 8 GB Total Mirrored Cache for Disk IO Operations scalable to min 16 GB
 Host interface
o 4 host ports per controller, Fibre Channel (FC),4 Gbps per port
 Drive interface
o 4 drive ports per controller—Fibre Channel (FC) Switched or FC Arbitrated
Loop
 (FC-AL) standard per controller, 4 Gbps per port
 RAID levels Supported
o The Storage Box should have RAID Support of 0, 1, 3, 5 & 10 [Hardware
based (XOR) RAID engine].
 Fans and power supplies
o Dual redundant, hot-swappable
 SAN support
o Box should be compatible of SAN environment
 SAN specifications shall have the following
o The storage array shall be configured with at least 8 GB cache scalable to
min 16GB mirrored across two storage controllers for disk I/O operations.
o Storage subsystem shall support 146GB, 300GB 15K RPM disks and 1TB or
higher 10 K RPM Fiber channel drives & 750GB, 1TB SATA or higher SATA /
equivalent drives in the same device array
o Presently, the storage sub system shall be configured with 300 GB of
Performance drives and 1 TB or higher on SATA / equivalent for archiving
purpose.
o The storage Box should have 4 TB usable spaces after RAID-5
implementation, using 146/300 GB, 4Gbps 15K RPM FC disks.
o The storage system must provide upgrade path to larger or future array
controller and software technology while maintaining the existing investment.
o The storage array proposed should have an upgrade path from the
earlier generation product to the current generation product.
o All the necessary software to configure and manage the storage space, RAID
configuration, logical drives allocation, virtualization, snapshots (including
snap clones and snap mirrors) for entire capacity etc.
o Load balancing must be controlled by system management software tools.
o The multi-path software should not only support the supplied storage
and operating systems but should also support heterogeneous storage and
operating systems from different OEMs.
o The storage array must have complete cache protection mechanism either by
de- staging data or providing complete cache data protection with battery
backup for up to 72 hours or more.
o The storage array should support Operating System Platforms & Clustering
including: Windows Server 2003 (Enterprise Edition), Sun Solaris, HP-UX,
IBM- AIX, Linux / Solaris for x86.
o Storage should support non-disruptive online firmware upgrade for
both Controllers and disk drives.
o The storage array should support hardware based data replication at the
Block level across all models of the offered family.
o The storage should provide automatic rerouting of I/O traffic from the host in
case of primary path failure.
o Should provision for LUN masking, fiber zoning and SAN security (as disk
based encryption.
o Should support storage virtualization, i.e. Easy logical drive expansion.
o Should support hot-swappable physical drive raid array expansion with
the addition of extra hard disks
o Should be able to support clustered and individual servers at the same time.
o Should be able to take "snapshots" of the stored data to another logical drive
on a different Disk/RAID Group for backup purposes
o Should be configured with "snapshots and clone"
o Vendor should also offer storage performance monitoring and management
software.
o The vendor must provide the functionality of proactive monitoring of Disk
drive and Storage system for all possible hard or soft disk failure
Tape Library - 1
Tape drives
 Minimum 2 latest generation LTO drives. The State can size for more as per
their requirements.
Interface
 Fiber Channel Interface
Other Specifications
 Should have sufficient speed backup to Tape Library in High Availability
for backing up data from the SAN without any user intervention.
 Should be able to backup 50% of the entire production landscape in 8
hours window.
 Should support latest generation LTO drives or latest technology based
library with at least 2 latest generation LTO drives tape drives (>=4), rack
mountable with redundant power supplies.
 Cartridges should have physical capacity up to 1600 GB per
cartridge compressed; 800 GB native.
 At least 50 latest generation LTO drive Media Cartridges with 5
Cleaning Cartridges, Barcode labels shall also be provided
Backup Software
 The proposed Backup Solution should be available on various OS platforms
such as Windows and UNIX platforms and be capable of supporting SAN

based backup / restore from various platforms including UNIX, Linux, and
Windows etc.
 Centralized, web-based administration with a single view of all back up servers
within the enterprise. Single console must be able to manage de-duplicated
and traditional backups.
 The proposed backup solution should allow creating tape clone facility after the
backup process.
 The proposed Backup Solution has in-built frequency and calendar based
scheduling system.
 The proposed backup Solution supports the capability to write multiple data
streams to a single tape device or multiple tape devices in parallel from multiple
clients to leverage the throughput of the Drives using Multiplexing technology.
 The proposed backup solution support de-multiplexing of data cartridge to
another set of cartridge for selective set of data for faster restores operation to
client/servers
 The proposed backup solution should be capable of taking back up of SAN
environment as well as LAN based backup.
 The proposed backup solution shall be offered with 4 Nos. UNIX based
licenses, 26 Nos. Windows based licenses and the rest 20 Nos. LINUX based
licenses for both SAN based backup and the LAN based backup.
 The proposed solution also supports advanced Disk staging.
 The proposed Backup Solution has in-built media management and supports
cross platform Device & Media sharing in SAN environment. It provides a
centralized scratched pool thus ensuring backups never fail for media.
 Backup Software is able to rebuild the Backup Database/Catalog from tapes in
the event of catalog loss/corruption.
 The proposed Backup Software should offer online backup for all the Operating
Systems i.e. UNIX, Windows & Linux etc
 The proposed Backup Solution has online backup solution for different type of
Databases such as Oracle, MS SQL, and Sybase / DB2 etc. on various OS.
 The Proposed backup solution shall provide granularity of single file restore.
 The Proposed backup solution shall be designed in such a fashion so that
every client / server in a SAN can share the robotic tape library.
 Backup Solution shall be able to copy data across firewall.
 The backup software must also be capable of reorganizing the data onto tapes
within the library by migrating data from one set of tapes into another, so that
the space available is utilized to the maximum. The software must be capable
of setting this utilization threshold for tapes
 The backup software should be able to support versioning and should
be applicable to individual backed up object’s
 Should have the ability to retroactively update changes to data management
policies that will then be applied to the data that is already being backed up or
archived
 All software licenses should be in the name of ……… and should be a
perpetual license, i.e. the software license should not expire after the contract
period. The software Licenses should be comprehensive and no further
licenses should be required for DC/DR operations. The software installed
should necessarily be the latest version at the time of actual implementation.
 FC-IP Router – 2 nos.
 Fibre Channel Ports
o min 4 FC ports
 FC Port Speed
o Autosensing 1/2/4 Gb/s
 iSCSI (Ethernet) Ports
o min 8 Ethernet ports
 iSCSI (Ethernet) Port Speed
o 1 Gigabit Ethernet
 Aggregate Bandwidth
o min 125 MB/s
 Protocol Support
o FCP
o iSCSI
 High-Availability Features
o Two-way active/active clustering with failover and failback
capabilities
o Multiple iSCSI connections provide multipathing support from a
single gateway to as many as 100 servers.
 Management Features
o CLI (by Telnet, SSH, or console)
 iSCSI Gateway Manager
o SNMP
 Allows for monitoring traffic statistics on each storage
and network interface, fan and temperature and iSCSI
session details.
4. Furniture Specifications
1) Specs of Computer Table 1 (Large):
Size L1200mm x W600mm x H745mm

Top & Understructure 18mm to 28mm thick top of PLB (Prelaminated Board). Edges
sealed with PVC beading. Understructure of MS (Metal Steel) duly
powder coated with 35 microns minimum. Comprising of plastic
KBPT (Keyboard Pull out Tray) fitted under the table top
Load Bearing Capacity 40 KG for the Table Top & 15 KG for the shelf
Hardware Comprising of Glide screws & self-tapping screws
2) Specs of Computer Table 2 (Small):

Size L900mm x W440mm x H745mm
Top & Understructure 18mm to 28mm thick top of PLB (Prelaminated Board). Edges
sealed with PVC beading. Understructure of MS (Metal Steel) duly
powder coated with 35 microns minimum. Comprising of plastic
KBPT (Keyboard Pull out Tray) fitted under the table top
Load Bearing Capacity 40 KG for the Table Top & 15 KG for the shelf
Hardware Comprising of Glide screws & self-tapping screws
3) Specs of Computer Chair:
OVERALL SIZE  Width: at least 70cm
 Depth: at least 70cm
 Height: 84 – 96.5cm
 Seat height: 46.6 – 59cm
SEAT/BACK ASSEMBLY The seat and back should be made up of at least
1.2cm thick hot pressed plywood, upholstered
with fabric and moulded Polyurethane foam with
PVC (Poly Vinyl Chloride) lipping all around.
Back Size – W 49cm x H 47cm
Seat Size – W 49cm x D 44cm
FOAM The polyurethane foam should have density and
hardness suitable for heavy usage (at least 80
Kgs load)
ARMRESTS The chair should have robust armrests
CENTRE PIVOT MECHANISM The centre pivot mechanism should have the
following features:
 360 degree revolving type.
 17-20 degree maximum tilt on pivot at
centre.
 Tilt tension adjustment.
 Upright locking.
PNEUMATIC HEIGHT ADJUSTMENT The pneumatic height adjustment facility should
be there.
TELESCOPIC BELLOW ASSEMBLY The bellow should be of 3 piece telescopic type
and injection moulded in black Polypropylene
PEDESTAL ASSEMBLY The pedestal should be fabricated from at least
0.2cm thick CR (Cold Rolled) Steel and powder
coated. Twin wheel castors (castors with
diameter 5.0cm) are required
ANNEXURE IX Existing IT Infrastructure
# City Police Station Client Duplex Multifuncti 16 - Modem/Fa Addition DVD UPS
PC Laser on product port x cards al HDD Writer/D 2KVA
Printer (print/scan/ unman (additional 160 GB VD Rom online
copy) aged item) drive
switch
1 Salem City Ammapet 3 1 1 1 2 2 2 1
2 Annadanapatty 4 1 1 1 2 2 2 1
3 Fairlands 4 1 1 1 2 2 2 1
4 Govt.HQRS Hospital 3 1 1 1 2 2 2 1
5 Hasthampatty 4 1 1 1 2 2 2 1
6 Kannankurichi 3 1 1 1 2 2 2 1
7 Kitchipalayam 4 1 1 1 2 2 2 1
8 Pallapatty 4 1 1 1 2 2 2 1
9 Salem Town Crime 4 1 1 1 2 2 2 1
10 Shevapet 4 1 1 1 2 2 2 1
11 Sooramangalam 4 1 1 1 2 2 2 1
12 Coimbatore Bazaar 5 1 1 1 2 2 2 1
City
13 Kattur 5 1 1 1 2 2 2 1
14 Peelamedu 4 1 1 1 2 2 2 1
15 Race course 4 1 1 1 2 2 2 1
16 R s puram 4 1 1 1 2 2 2 1
17 Ramanathapuram 4 1 1 1 2 2 2 1
18 Singanallur 4 1 1 1 2 2 2 1
19 Selvapuram 3 1 1 1 2 2 2 1
20 Saibaba colony 4 1 1 1 2 2 2 1
21 Saravanapatti 4 1 1 1 2 2 2 1
22 Ukkadam 4 1 1 1 2 2 2 1
23 Variety hall road 4 1 1 1 2 2 2 1
24 Chennai City Koyambedu 5 1 1 1 2 2 2 1
25 Adayar 5 1 1 1 2 2 2 1
26 Aminjikarai 5 1 1 1 2 2 2 1
27 Annanagar 5 1 1 1 2 2 2 1
28 Ayyanavaram 5 1 1 1 2 2 2 1
29 Chintadripet 5 1 1 1 2 2 2 1
30 Egmore 5 1 1 1 2 2 2 1
31 Elephant gate 5 1 1 1 2 2 2 1
32 Esplanade 5 1 1 1 2 2 2 1
33 Flower bazaar 5 1 1 1 2 2 2 1
34 Fort st george 5 1 1 1 2 2 2 1
35 General section 4 1 1 1 2 2 2 1
switch
36 Harbour 5 1 1 1 2 2 2 1
37 Ice house 5 1 1 1 2 2 2 1
38 Guindy 5 1 1 1 2 2 2 1
39 Zam bazar 5 1 1 1 2 2 2 1
40 Kasimedu 5 1 1 1 2 2 2 1
41 Kodambakkam 5 1 1 1 2 2 2 1
42 Korukkupet 5 1 1 1 2 2 2 1
43 Kothavalchavadi 5 1 1 1 2 2 2 1
44 Mambalam 5 1 1 1 2 2 2 1
45 Anna salai/mount road 5 1 1 1 2 2 2 1
46 Muthialpet 5 1 1 1 2 2 2 1
47 Mylapore 5 1 1 1 2 2 2 1
48 Ashok nagar 5 1 1 1 2 2 2 1
49 New washermanpet 5 1 1 1 2 2 2 1
50 North beach 5 1 1 1 2 2 2 1
51 Numgambakkam 5 1 1 1 2 2 2 1
52 Otteri 5 1 1 1 2 2 2 1
53 Periamet 5 1 1 1 2 2 2 1
54 Pulianthoppu 5 1 1 1 2 2 2 1
55 Royapettah 5 1 1 1 2 2 2 1
56 Royapuram 5 1 1 1 2 2 2 1
57 Saidapet 5 1 1 1 2 2 2 1
58 Sembiam 5 1 1 1 2 2 2 1
59 Seven wells 5 1 1 1 2 2 2 1
60 Teynampet 5 1 1 1 2 2 2 1
61 Tondiarpet 5 1 1 1 2 2 2 1
62 Triplicane 5 1 1 1 2 2 2 1
63 Vepery 5 1 1 1 2 2 2 1
64 Vyasarpadi 5 1 1 1 2 2 2 1
65 Washermanpet 5 1 1 1 2 2 2 1
66 Basin bridge 5 1 1 1 2 2 2 1
67 Thousand lights 5 1 1 1 2 2 2 1
68 Anna square 5 1 1 1 2 2 2 1
69 Govt. General hospital 5 1 1 1 2 2 2 1
70 Abiramapuram 5 1 1 1 2 2 2 1
71 Choolaimedu 5 1 1 1 2 2 2 1
72 I.C.F. Colony 5 1 1 1 2 2 2 1
73 Chetpet 5 1 1 1 2 2 2 1
switch
74 Kotturpuram 5 1 1 1 2 2 2 1
75 T.p.chatram 5 1 1 1 2 2 2 1
76 Secretariat colony 5 1 1 1 2 2 2 1
77 Sastri nagar 5 1 1 1 2 2 2 1
78 Foreshore estate 5 1 1 1 2 2 2 1
79 Arumbakkam 4 1 1 1 2 2 2 1
80 Kumaran nagar 4 1 1 1 2 2 2 1
81 Peravalur 4 1 1 1 2 2 2 1
82 Govt. Estate 4 1 1 1 2 2 2 1
83 Dr. R. Krishnan nagar 5 1 1 1 2 2 2 1
84 M.k.b. Nagar 4 1 1 1 2 2 2 1
85 Marina 5 1 1 1 2 2 2 1
86 Pondy bazaar 5 1 1 1 2 2 2 1
87 Kilpauk mental hospital 5 1 1 1 2 2 2 1
88 Fishing harbour 4 1 1 1 2 2 2 1
89 K.k. Nagar 4 1 1 1 2 2 2 1
90 Thiruvanmiyur 4 1 1 1 2 2 2 1
91 Velacheri 4 1 1 1 2 2 2 1
92 Villivakkam 4 1 1 1 2 2 2 1
93 Virugambakkam 4 1 1 1 2 2 2 1
94 Govt. Rsrm hospital 3 1 1 1 2 2 2 1
95 High court 5 1 1 1 2 2 2 1
96 J.j. Nagar 5 1 1 1 2 2 2 1
97 Kodungaiyur 5 1 1 1 2 2 2 1
98 Kolathur 5 1 1 1 2 2 2 1
99 Rajamangalam 5 1 1 1 2 2 2 1
100 Thirumangalam 5 1 1 1 2 2 2 1
101 Thiruvotriyur 5 1 1 1 2 2 2 1
102 Thiru vika nagar 5 1 1 1 2 2 2 1
103 Madurai City Sri meenakshi amman 3 1 1 1 2 2 2 1
104 Mathichayam 4 1 1 1 2 2 2 1
105 Madurai town east 4 1 1 1 2 2 2 1
106 Madurai town north 4 1 1 1 2 2 2 1
107 Madurai town south 4 1 1 1 2 2 2 1
108 Jaihindpuram 4 1 1 1 2 2 2 1
109 Keeraithurai 4 1 1 1 2 2 2 1
110 Sellur 4 1 1 1 2 2 2 1
switch
111 Somasundaram colony 4 1 1 1 2 2 2 1
112 Subramaniapuram 4 1 1 1 2 2 2 1
113 Thideernagar 4 1 1 1 2 2 2 1
114 K. Pudur 4 1 1 1 2 2 2 1
115 Thallakulam traffic 5 1 1 1 2 2 2 1
116 Town traffic ii 4 1 1 1 2 2 2 1
117 Karimedu traffic iii 4 1 1 1 2 2 2 1
118 Annanagar traffic vi 5 1 1 1 2 2 2 1
119 Tiruchirapalli Woraiyur 4 1 1 1 2 2 2 1
120 Tirunelveli Melapalayam 4 1 1 1 2 2 2 1

City
121 Palayamkottai 5 1 1 1 2 2 2 1
122 Perumlpuram 4 1 1 1 2 2 2 1
123 Pettai 3 1 1 1 2 2 2 1
124 Thatchanallur 3 1 1 1 2 2 2 1
125 Tirunelveli junction 5 1 1 1 2 2 2 1
126 Tirunelveli town 3 1 1 1 2 2 2 1
127 Tiruchirapalli Airport 3 1 1 1 2 2 2 1

City
128 Ariyamangalam 3 1 1 1 2 2 2 1
129 Contonment 4 1 1 1 2 2 2 1
130 Edamalaipattipudur 3 1 1 1 2 2 2 1
131 Fort 4 1 1 1 2 2 2 1
132 Gandhi market 4 1 1 1 2 2 2 1
133 Golden rock 3 1 1 1 2 2 2 1
134 K.k.nagar 4 1 1 1 2 2 2 1
135 Palakkarai 4 1 1 1 2 2 2 1
136 Srirangam 4 1 1 1 2 2 2 1
137 Thillai nagar 3 1 1 1 2 2 2 1
Total 606 137 137 137 274 274 274 137
ANNEXURE X Training Institutions Infrastructure
The following locations were identified at various districts and commissionerates and the District
Training Centres were established. The locations of District Training Centres, Police Recruit
School, Police Academy is mentioned below:
S.No City / District Place Area
1 CHENNAI CITY 2nd Floor, C5-Kothavalchavadi PS, Chennai 480 Sq.Ft.
2 CHENNAI CITY C-Class Room, Ground Floor, Old Building, 500 Sq.Ft.
PCCC, R.A.Puram, Chennai-28
3 CHENNAI SUB-URBAN Chennai Sub-Urban Commissionerate Complex, 504 Sq.Ft.
St. Thomas Mount
4 CUDDALORE Unused Elementary School, AR, Cuddalore. 450 Sq.Ft.
5 KANCHEEPURAM In-Service Training Centre, DPO, Kanchipuram 448 Sq.Ft.
6 THIRUVALLUR Training Hall, DPO, Thiruvallur, 518 Sq.Ft.
7 THIRUVANNAMALAI Conference Hall, Armed-HQ, Tiruvannamalai 608 Sq.Ft.
8 VELLORE A Hall, DPO, Vellore 800 Sq.Ft.
9 VILLUPURAM 1st Floor, In-service Centre, DPO, Villupuram 520 Sq.Ft.
10 ARIYALUR CCTNS Training Centre, Ragavan Complex, 550 Sq. Ft.
Trichy Main Rd, Ariyalur
11 KARUR Training Hall, New DPO, Karur. 530 Sq.Ft.

12 NAGAPATTINAM DPO, 2nd Floor, Nagapattinam 470 Sq.Ft.
13 PERAMBALUR 2nd Floor, DPO, Perambalur 458 Sq.Ft.
14 PUDUKKOTTAI Conference Hall, Pudukottai 600 Sq.Ft.
15 THANJAVUR Control Room, Tanjavur. 570 Sq.Ft.
16 TIRUVARUR AR Campus, Tiruvarur. 416 Sq.Ft.
17 TRICHY Training Hall, 2nd Floor, DPO, Trichy 375 Sq.Ft.
18 TRICHY CITY Old Control Room, Contonment PS Campus 608 Sq.Ft.
19 DINDIGUL Women's Waiting Hall, AR, Dindigul 390 Sq.Ft.
20 KANYAKUMARI DPO, Kanniyakumari 675 Sq.Ft.
21 MADURAI 1st Floor, Conference Hall, Ty. PRS, AR, 783 Sq.Ft.
Madurai
22 MADURAI CITY Tallakulam PS Campus, Madurai City. 620 Sq.Ft.
23 RAMANATHAPURAM Women Police Rest Room, A.R campus, 416 Sq.Ft.
Ramnad
24 SIVAGANGAI Community Hall, 2nd Floor, DPO, Sivagangai 768 Sq.Ft.
25 THENI Training Hall, DPO, Theni 928 Sq.Ft.
26 THIRUNELVELI Conference Hall, DPO, Tirunelveli 979 Sq.Ft.
27 THOOTHUKUDI Nearby DPO, Thoothukudi 854 Sq.Ft.
28 TIRUNELVELI CITY PRS Admin Building, AR, Tirunelveli City. 900 Sq.Ft.
29 VIRUDHUNAGAR 1st Floor, In-service Centre, DPO, Villupuram 600 Sq.Ft.
30 COIMBATORE Campus of Mahalingapuram PS, Pollachi S.D. 1100 Sq.Ft.
31 COIMBATORE CITY AIMS Building hall, Coimbatore city 800 Sq.Ft.

32 DHARMAPURI AR old Kalyanamandapam, Dharmapuri 1250 Sq.Ft.
S.No City / District Place Area

33 ERODE AR Complex, Erode 1000 Sq.Ft.
34 KRISHNAGIRI New DPO, Krishnagiri 858 Sq.Ft.
35 NAMAKKAL Training Hall, AR Complex, Namakkal 999 Sq.Ft.
36 NILGIRIS TN Home Guards & Civil Defence Trg. Centre, 595 Sq.Ft.
The Nilgirish
37 SALEM New DPO, Salem. 1110 Sq. Ft.

38 SALEM CITY Control Room, Salem City. 810 Sq.Ft.
39 TIRUPUR District Police Office, Tiruppur functioning at 2/69 600 Sq.Ft.
Angeripalayam road, Tiruppur – 641602.
40 CHENNAI RAILWAY Back side of RPO,Meeting Hall, 8- varatharajulu 400 Sq. Ft.
street, egmore, chennai
41 SCRB 95, Santhome High Road, R.A.Puram, Chennai- 550 Sq. Ft.
28
42 TAMILNADU POLICE Technology Block,Tamilnadu Police Acadamy, 500 Sq. Ft.
ACADEMY,OONAMAN Oonamanchery, Chennai-48
CHERY
43 POLICE TRAINING Cyber Hall, Police Training Head quarter, 6, 500 Sq. Ft.
COLLEGE,ASHOK Natesan Salai, Ashok Nagar, Chennai - 600 083.
NAGAR, CHENNAI
44 POLICE COMPUTER Police Computer Communication Center, 500 Sq. Ft.
COMMUNICATION R.A.Puram, Santhome High Road, Chennai - 28
CENTRE, R.A.PURAM,
CHENNAI
45 DGP's OFFICE, Hall No-310 (Half portion) second floor, DGP 1212 Sq. Ft.
CHENNAI office, Mylapore , Chennai - 4
46 PRS - VELLORE Law Class Room, Police Recruit School, Vellore 500 Sq. Ft.
Fort, Vellore, Tamil Nadu. Ph:- 0416-2220065.
47 PRS – TRICHY Class Room - 'A' , Police Training School, 500 Sq. Ft.
Batallion Ground, Trichy I Batallion, Tamil Nadu.
Ph:- 0431-2472695.
48 PRS - COIMBATORE First Floor of the Library Hall, Police Recruit 440 Sq. Ft.
School, Papanayakanpalayam, Coimbatore
49 PRS - THOOTHUKUDI LCD Projector Room, Police Training School, 712 Sq. Ft.
Perurani, Thoothukudi, Tamil Nadu. Ph:- 04162-
271070.
ANNEXURE XI Geographical Coverage
This presents the geographic coverage for the CCTNS Project in Tamil Nadu. The districts and
commissionerates are represented in the Tamil Nadu map as shown below:
The project would be rolled out in the following higher offices in the state headquarters:
 Tamil Nadu Police Headquarters
 State Crime Records Bureau
These offices would be covered in Pilot Phase of Implementation. Along with these, the districts
and offices in each district to be covered in different phases are described below. The geographical
coverage described in the tables below reflecting the phases of implementation as mentioned in
Section 6.1.1
Zone/ DPO/CPO ACOP/JC/DC/AD ADSP Office SDPO/AC Range Police Stations Outposts*
Range Or City C Offices Offices
Pilot Phase
South/ Sivagangai NA Sivagangai Aravayal Alagappapuram

Ramanathapur
Manamadurai AWPS Devakottai Mithravayal
am
Karaikudi AWPS Manamadurai Velayuthapattina
m
Devakottai. AWPS-Karaikudi
Thiruppathur AWPS-Sivagangai
AWPS-Thiruppathur
Chettinadu
Devakottai Taluk
Devakottai Town
Elayangudi
Kalaiyarkoil
Kallal
Kandavarayanpatti
Karaikudi North
Karaikudi South
Keelasevalpatti
Kundrakudi
Madagupatti
Manamadurai
Nachiyapuram
Nerkuppai
Palayanur
Pallathur
Poolamguruchi
Poovanthi
Pulithipatty
S.S.Kottai
S.V.Mangalam
Sakkottai
Salaigramam
Singampunari
SIPCOT
Sivagangai Taluk
Sivagangai Town
Somanathapuram
Thiruppachethi
Thiruppathur Town
Thiruppuvanam
Thiruvegampet
Thiukostiyur
Ulagampatti
Central/ Thanjavur NA Thanjavur Town Adiramapattinam

Thanjavur
Vallam Ammapet
Thiruvaiyaru AWPS papanasam
Thanjavur Rural AWPS pattukottai
Kumbakonam AWPS Thiruvaiyaru
Thiruvidaimarudur AWPS-kumbakonam
Pattukottai AWPS- Thanjavur
Orathanadu Ayyampet
Budalur
Hariduvaramangalam
Kabisthalam
Kallaperambur
Kumbakonam North
Kumbakonam South
Kumbakonam Taluk
Madukkur
Maruvoor
Melathur
Nachiyarkoil
Nadukaveri
Orathanadu
Pandanallur
Papanadu
Papanasam
Patteswaram
Pattukottai
Peravorani
Sengipatty
Sethubavachathiram
Swamimalai
Thanjavur Med.Col
Thanjavur Taluk
Thanjavur Tamil Univ
Thanjavur Town East
Thanjavur Town South
Thanjavur Town West
Thiruchitrambalam
Thirukattupalli
Thiruneelakudi
Thiruppanandal
Thiruvaiyaru
Thiruvidaimarudur
Thiruvonam
Thogur
Valangaiman
Vallam
Vattathikottai
Chennai Sub- St. Thomas Mount DCP, St. Thomas Ambattur Adambakkam
urban Mount
DCP, Ambattur Avadi Airport
DCP, Ennore Ambattur

Madhavaram
Madavaram Ambattur Estate
Madipakkam Avadi
Maduravoyal AWPS - Ambattur
Meenambakkam AWPS - Avadi
Pattabiram AWPS - Ennore
Poonamallee AWPS - Madhavaram
Puzhal AWPS - Madipakkam
Selaiyur AWPS - Poonamallee
St. Thomas Mount AWPS - St Thomas

Mount
Tambaram AWPS - Tambaram
Chitlapakkam
Chrompet
Ennore
Korattur
Kunrathur
Madhavaram
Madipakkam
Maduravoyal
Manali
Manali New Town
Mangadu
Meenambakkam
Milk Colony
Muthapudupet
Nandampakkam
Nasaratpet
Palavanthangal
Pallavaram
Pallikaranai
Pattabiram
Peerkankaranai
Poonamallee
Puzhal
Redhills
Sankar Nagar
Sathangadu
Selaiyur
SRMC
St. Thomas Mount
Tambaram
Tank Factory
Thirumullaivoyal
Thirunindravur
Thiruverkadu
Coimbatore Coimbatore City DCP, L & O, City Coimbatore West AWPS Central
City Police Office
DCP, Crime & Coimbatore East Bazaar

Traffic, City Police
Office
DCP, Coimbatore Coimbatore

Central
Headquarters,
City Police Office
DCP, Armed Coimbatore South Kattur

Reserve, PRS,
Coimbatore
ADC, PEW, City Kuniamuthur

Police Office
Peelamedu
Poddanur
R S Puram
Race Course
Ramanathapuram
Rathinapuri
Saibaba Colony
Saravanapatti
Selvapuram
Singanallur
Ukkadam
Variety Hall Road
Roll-out Phase I
West/Salem Dharmapuri Dharmapuri A.Pallipatti
Harur Adiyamankottai
Pennagaram AWPS Harur
AWPS Pennagaram
AWPS Dharmapuri
Bommidi
Dharmapuri
Eriyur
Harur
Hogenakkal
Indur
Kadathur
Kambainallur
Karimangalam
Kottapatti
Krishnapuram
Mahendramangalam
Marandahalli
Mathikonpalayam
Morappur
Palacode
Paparapatti
Pappireddipatti
Pennagaram
Pouchenpalli
Thoppur
North/ Cuddalore Cuddalore Annamalainagar

Villupuram
Panruti Avinankudi
Chidambaram AWPS - Neyveli
Sethiyathope AWPS - Panruti
Neyveli AWPS Sethiyathope
Virudhachalam AWPS Vridhachalam
Thittakudi AWPS-Chidambaram
AWPS- Cuddalore
Bhuvanagiri
Chidambaram Taluk
Chidambaram Town
Cuddalore NT
Cuddalore OT
Cuddalore port
Devanampattinam
Kadampuliyur
Kammapuram
Karuveppilankurichi
Kattumannarkoil
Killai
Kullanchavadi
Kumaratchi
Kurinjipadi
Mandharakuppam
Mangalampet
Maruthur
Muthandikuppam
Naduveerapattu
Nellikuppam
Neyveli Township
Neyveli Thermal
Oomangalam
Orathur
Panruti
Pennadam
Porto novo
Puduchatram
Pudupettai
Puthur
Ramanatham
Reddichavadi
Sethiyathope
Sirupakkam
Sozhatharam
Srimushnam
Thiruppapuliyur
Thookkanampakkam
Titakudi
Vadalur
Veppur
Virudhachalam
Central/ Nagapattinam Nagapattinam Anaikaranchatram Vettaikaranirrup

Thanjavur pu
Vedaranyam AWPS - Sirkali
Mayiladuthurai AWPS - Vedaranyam
Sirkali AWPS -Mayiladuthurai
AWPS -Nagapattinam
Kariyapattinam
Keelaiyur
Keevalur
Kuthalam
Manalmedu
Mayiladuthurai
Nagapattinam
Nagoor
Palaiyur
Perambur
Poompuhar
Poraiyar
Pudupattinam
Sembanarkoil
Sirkali
Thalainayar
Thirukuvalai
Thiruvenkadu
Thittachery
Vaitheswaran Koil
Valivalam
Vedaranyam
Velankanni
Velipalayam
Voimedu
South/Ramana Ramanathapuram Kamuthi Abiramam Jetty

thapuram
Keelakarai AWPS - Keelakarai
Paramakudi AWPS - Paramakudi
AWPS - Rameswaram
AWPS - Thiruvadanai
AWPS- Kamuthi
AWPS -
Ramanathapuram
Chatrakudi
Devipattinam
Elanjambur
Emaneswaram
Eravadi Dharga
Kadaladi
Kamuthi
Keelakarai
Keelaselvanoor
Keelathooval
Kenikkarai
Kovilangulam
Mandala Manickam
Mandapam
Mudukulathur
Nainarkoil
Pamban
Paramakudi Taluk
Paramakudi Town
Parthibanoor
Peraiyur
Perunali
R.S.Mangalam
Ramanathapuram
Bazaar
Ramanathapuram
Town
Rameswaram Temple
Rameswaram Town
S.P.Pattinam
Sayalkudi
Sikkal
Thangachimadam
Thanushkodi
Theriruveli
Thirupalaikudi
Thirupullani
Thiruvadanai
Thondi
Uchipuli
Uthirakosamangai
Valinokkam
South/Dindigul Theni Theni Allinagaram Vaigai
Periyakulam Andipatti Ethakovil
Andipatti AWPS Andipatti Kanniyapillaipatti
Bodinayakanur AWPS Bodi
Uthamapalayam AWPS
Uthamapalayam
AWPS- Theni
Bodinayakkanur rural
Bodinayakkanur Town
Chinnamanur
Cumbum North
Cumbum South
Devadanapatti
Gandamanur
Gandamanur Vilakku
Gudalur North
Gudalur South
Highways
Jayamangalam
Kadamalaikundu
Kombai
Kumuli
Kurangani
Mayiladumparai
Odaipatti
Palanichettypatti
Periyakulam
Rajathanai
Rayappanpatti
Theni
Thenkarai
Thevaram
Uthamapalayam
Varasanadu
Veerapandi
North/Vellore Vellore Vellore Alangayam Avalur
Katpadi Ambalur Thimmampet
Ranipet Ambur Taluk
Arakkonam Ambur Town
Gudiyatham Anaicut
Ambur Arakonam Taluk
Vaniyambadi Arakonam Town
Thiruppathur Arcot Taluk
Arcot Town
AWPS - Ambur Town
AWPS Gudiyatham
AWPS- Ranipet
AWPS - Vaniyambadi
AWPS - Vellore North
AWPS- Arakonam
AWPS- Thirupathur
AWPS- Vellore
Bagayam
Banavaram
Ealagiri
Gudiyatham Taluk
Gudiyatham Town
Jolarpet
K.V.Kuppam
Kalavai
Kandili
Katpadi
Kavalur
Kaveripakkam
Kondampalayam
Kurisilapet
Latheri
Melpadi
Melpatti
Natrampalli
Nemili
Omerabad
Pallikonda
Panamadangi
Paradarami
Pernampet
Ponnai
Ranipet
Ranipet SIPCOT
Sathuvacheri
Sholinghur
Thakkolam
Thirupathur Taluk
Thirupathur Town
Thiruvalam
Timiri
Valapandal
Vaniyambadi Taluk
Vaniyambadi Town
Vellore North
Vellore South
Vellore Taluk
Veppankuppam
Virinchipuram
Virudampet
Walajapet
South/ Thoothukudi Thoothukudi Alwarthirunagiri Serakulam

Town
Tirunelveli
Thoothukudi Arumuganeri Sankaralingapur
Rural am
Maniyachi Authoor
Kovilpatti AWPS Srivaikundam
Vilathikulam AWPS Srivaikundam
Srivaikundam AWPS Thiruchendur
Thiruchendur AWPS Vilathikulam
Sattankulam AWPS-Kadambur
AWPS-Kovilpatti
AWPS-Pudukottai
AWPS-Tuticorin
Eppodumvendran
Eral
Ettayapuram
Kadalkudi
Kadambur
Kalugumalai
Kayathar
Koppampatti
Kovilpatti East
Kovilpatti West
Kulasekarapattinam
Kulathur
Kurumbur
Maniyachi
Masarpatti
Meignanapuram
Murappanad
Muthiahpuram
Nalatinpudur
Naraikinaru
Nazareth
Ottapidaram
Pasuvanthanai
Pudukkottai
Pudur
Puliyampatti
Puthiam Puthur
Sattankulam
Sayarpuram
Seidunganallur
SIPCOT
Soorankudi
Srivaikundam
Thalamuthunagar
Tharuvaikulam
Thattaparai
Thattarmadam
Thermalnagar
Thiruchendur
Tiruchendur Temple
Tuticorin Central
Tuticorin North
Tuticorin South
Vilathikulam
South/Tirunelv Kanniyakumari Nagercoil Anju gramam Lower kothaiyar

eli
Kanniyakumari Aralvoimozhi Upper kothaiyar
Thuckkalai Arugani
Colachel Arumanai
Asaripallam
AWPS Colachel
AWPS Kanniyakumari
AWPS Kuzhithurai
AWPS- Nagercoil
Boothapandy
Colachel
Eraniel
Ethamozhi
Kadaiyalumoodu
Kaliyakkavilai
Kanya Kumari
Karungal
Keeriparai
Kollancode
Kottar
Kottiyode
Kulasekaram
Kuzhithurai
Manavalakurichi
Mandaikadu
Nesamani Nagar
Nithiravilai
Pazhugal
Pechiparai
Puthukadai
Rajakkamangalam
South Thamaraikulam
Suchindram
Thiruvattar
Thuckkalai
Vadaseri
Vellichanthai
South/Tirunelv Tirunelveli Tirunelveli rural Achanpudur Servalar

eli
Ambasamudram Alankulam Lower dam
Cheranmahadevi Alwarkurichi Manimuthar
Alangulam Ambasamudram Seethaparpanall

ur
Tenkasi AWPS - Alankulam Ayyapuram
Sankarankoil AWPS -
Ambasamudram
Puliyangudi AWPS - Nanguneri
Valliyoor AWPS -Sankarankoil
Nanguneri AWPS - Tirunelveli

Rural
AWPS - Valliyoor
AWPS- Tenkasi
Ayikudi
Cheranmahadevi
Chinnakoilankulam
Courtallam
Devarkulam
Eruvadi
Gangaikondan
Kadayam
Kadayanallur
Kalakkad
Kallidaikurichi
Karivalamvanthanallur
Koodankulam
Kuruvikulam
Manjolai
Manur
Moolaikaraipatty
Moontradaippu
Mukkudal
Munneerpallam
Nanguneri
Ovari
Palavoor
Panagudi
Panavadalichatram
Pappakudi
Pathamadai
Pavoorchatram
Puliangudi
Puliarai
Radhapuram
Sambavarvadakarai
Sankarankoil Taluk
Sankarankoil Town
Seevalaperi
Senthamaram
Shenkottai
Sivagiri
Sivanthipatti
Surandai
Suthamalli
Thalaiyuthu
Thenkasi
Thirukkurungudi
Thiruvengadam
Thisayanvilai
Tirunelveli Taluk
Uthumalai
Valliyoor
Vasudevanallur
Veerakeralampudur
Veeravanallur
Vickramasingapuram
Vijayanarayanam
West/ Coimbatore Pollachi Alandurai Aliyar

Coimbatore
Valparai Anamalai Kadambarai
Water Falls
Periyanaicken Annur Sheikalmudis
Palayam
Perur AWPS - Perur
AWPS - Thudiyalur
AWPS - Pollachi
Chettipalayam
Gomangalam
K.G. Chavadi
Kadambarai
Karamadai
Karumathampatty
Karunyanagar
Kinathukadavu
Koilapalayam
Kottur
Madukkarai
Mahalingapuram
Mettupalayam
Mudis
Negamam
Periyanaickenpalayam
Perur
Pillurdam
Pollachi Bazaar
Pollachi Taluk
Pollachi Town
Sirumugai
Sulur
Thondamuthur
Thudialur
Vadavalli
Valparai
Vedakkipalayam
West/ Nilgiris Udhagamandalam Ambalamoola

Town
Coimbatore
Udhagamandalam Aruvankadu
Rural
Coonur AWPS - Coonur
Gudalur AWPS - Devala
Devala AWPS - Gudalur
AWPS -
Udhagamandalam
AWPS -
Udhagamandalam
Rural
Cherambadi
Coonoor Town
Denaducombai
Devala
Devarsholai
Emerald
Erumad
Gudalur
Ketti
Kolacombai
Kothagiri
Manjur
Masinagudi
Naduvattam
Nellakottah
Newhope
Pudumand
Sholurmattam
Udhagamandalam
Rural
Udmlm Town Central
Udmlm Town West
Uppercoonoor
Wellington
West/Salem Krishnagiri Krishnagiri Anchetty
Bargur AWPS - Bargur(Dpi)
Uthangarai AWPS -
Denkalaikottai(Dpi)
Hosur AWPS - Hosur(Dpi)
Denkanikottai AWPS -
Krishnagiri(Dpi)
Bagalur
Bargur
Barur
Berigai
Denkanikottai
Gurubarapalli
Hosur
Hudco
Kallavi
Kandhikuppam
Kaveripattinam
Kelamangalam
Krishnagiri Taluk
Krishnagiri Town
Krp Dam
Maharajakadai
Mathigiri
Mathur
Nagarasampatti
Pochampalli
Rayakottai
Samalpatti(Dpi)
Shoolagiri
Singarapettai
SIPCOT
Thally
Uthanapalli
Uthangarai
Veppanapalli
North/Villupura Villupuram Gingee Anandapuram

m
Kallakurichi Arakandanallur
Kottakuppam Auroville
Tindivanam Avalurpet
Thirukoilur AWPS - Gingee
Ulundurpet AWPS - Kallakurichi
Viluppuram AWPS Kottakuppam
AWPS Tindivanam
AWPS-Thirukoilur
AWPS-Villupuram
Brammadesam
Chinnasalem
Elavanasurkottai
Gingee
Kachirapalayam
Kallakurichi
Kandachipuram
Kandamangalam
Kanjanur
Kanni
Kariyalur
Kedar
Kikuppam
Kiliyanoor
Kottakuppam
Mailam
Manalurpet
Marakanam
Moongi Thuraipattu
Nallan Pillai Petral
Olakkur
Pagandaikuttusalai
Periyathatchur
Rishivandiam
Roshanai
Sankarapuram
Sathiyamangalam
Thirukoilur
Thirunavalur
Thirupalapandal
Thiyagadurgam
Tindivanam
Tiruvennainallur
Ulundur Pet
Vadaponparappi
Valathy
Valavanur
Vanur
Varanjaram
Vellimedupettai
Vikravandi
Villupuram Taluk
Villupuram Town
Villupuram West
North/ Thiruvallur Thiruvallur Arambakkam Periyakuppam

Kancheepura
Uthukottai Arani
m
Thiruthani AWPS Ponneri
Ponneri AWPS Thiruvallur
Gummidipoondi AWPS Uthukottai
AWPS-Thiruthani
Gummudipoondi
Kadambathur
Kanakamma Chatram
Kattur
Kavarapettai
Manavala Nagar
Mappedu
Minjur
Pallipet
Pathirivedu
Pennalurpet
Periyapalayam
Ponneri
Pothattur Pet
R.K.Pet
Sevvapet
Sholavaram
Sipcot
Thirupalaivanam
Thiruthani
Thiruvalangadu
Thiruvallur Taluk
Thiruvallur Town
Uthukottai
Vellavedu
Vengal
North/Kanchee Kancheepuram Chengalpattu Achirapakkam Anaicut

puram
Kancheepuram AWPS Chengalpattu
Maduranthagam AWPS Mahabalipuram
Mamallapuram AWPS Melmaruvathur
Sriperumbudur AWPS Sriperumbudur
AWPS-Kancheepuram
Baluchettychatram
Chengalapattu Tn
Chengalpattu Taluk
Cheyyur
Chittamur
Chunambedu
Guduvancheri
Kalpakkam
Kanchi Taluk
Kelampakkam
Koovathur
Maduranthakam
Magaral
Mamallapuram
Manampathi
Manimangalam
Maraimalai Nagar
Melmaruvathur
Oragadam
Orathi
Otteri
Padalam
Palur
Sadras
Salavakkam (G5)
Sivakanchi
Somangalam
Sriperumbudur
Sunguvarchatram
Thalambur
Thirukalukundram
Thiruporur
Uthiramerur
Vishnukanchi
Walajabad (K3)
Central/ Trichy Pudukottai Pudukottai Alangudy Malaiyur
Alangudi Annavasal Vellanoor
Aranthangi Aranthangi
Kottaipattinam Arimalam
Keeranur Athanakottai
Ponnamaravathy Avudaiyarkoil
AWPS - Alangudi
AWPS - Keeranur
AWPS -
Ponnamaravathy
AWPS -Aranthangi
AWPS - Pudukottai
AWPS - Thirumayam
Embal
Gandharvakottai
Ganeshnagar
Illupur
Jagadapattinam
K.Pudupatty
Karaiyur
Karambakudy
Karur
Keeramangalam
Keeranur
Kottaipattinam
Manamelgudy
Mandaiyur
Mathur
Mimisal
Nagudy
Namana Samudram
Panayappatty
Ponnamaravathy
Pudukottai Town
Regunathapuram
Sampathuvidthi
Thirugokarnam
Thirumayam
Thiruppunavasal
Udayalipatti
Vadakadu
Viralimalai
Tirunelveli City Tirunelveli City DCP, L & O, Tirunelveli Town AWPS - Tirunelveli
Junction
Kokirakulam,
Tirunelveli City
DCP, Crime & Palayamkottai AWPS -Palayamkottai

Traffic ,
Kokirakulam,
Tirunelveli City
ADC, PEW, Melapalayam

Tirunelveli City
Palayamkottai
Perumalpuram
Pettai
Thatchanallur
Tirunelveli Junction
Tirunelveli Town
Roll-out Phase-II
North/Vellore Tiruvannamalai Arni Annakkvur
Chengam Arni Taluk
Cheyyar Arni Town
Polur AWPS Chengam
Tiruvannamalai AWPS Cheyyar

Town
Tiruvannamalai AWPS Polur
Rural
Vandavasi AWPS Vandavasi
AWPS-Arni
AWPS-Tiruvannamalai
Brammadesam
Chengam
Chetpet
Cheyyar
Desur
Dusi
Jamuna Marudur
Kadaladi
Kalambur
Kalasapakkam
Kannamangalam
Kilcodungalore
Kilpennathur
Mangalam
Melchengam
Moranam
Pachalf
Pernamallur
Polur
Ponnur
Pudupalayam
Santhavasal
Sathanurdam
Thachampet
Thandrampet
Thanipadi
Thellar
Thiruvannamalai East
Thiruvannamalai Taluk
Thiruvannamalai Town
Thiruvannamalai Town
Crime
Vadavanakkambadi
Vanapuram
Vandavasi North
Vandavasi South
Veraiyur
Vettavalam
West/Salem Namakkal Namakkal AWPS Rasipuram
Tiruchengode AWPS - Tiruchengode
Rasipuram AWPS Velur
Vellur AWPS-Namakkal
Ayilpatty
Belukurichi
Elachipalayam
Erumapatty
Jedarpalayam
Komarapalayam
Mallasamudram
Mangalapuram
Mohanur
Molasai
Nallipalayam
Nallur
Namagiripet
Namakkal
Pallipalayam
Paramathi
Puduchatram
Rasipuram
Sendamangalam
Thiruchengodu Rural
Thiruchengodu Town
Valavandhinadu
Velagoundanpatti
Velur
Vennandur
West/Salem Salem Salem Rural Attaiyanpatti
Sankari Attur
Mettur AWPS Athur
Omalur AWPS Mettur
Athur AWPS Omalur
Valappady AWPS Salem Rural
AWPS Sankari
Deevattipatti
Edapady
Ethappur
Gangavalli
Jalakandapuram
Karipatty
Kariyakoil
Karumalaikoodal
Karumandurai
Kolathur
Kondalampatti
Macdonalds Choultry
Malliyakarai
Mallur
Mechery
Mettur
Nangavalli
Omalur
Panamarathupatty
Poolampatti
Sankari
Steel Plant
Thalaivasal
Thammampatty
Tharamangalam
Thevoor
Tholasampatty
Valapady
Veeraganur
Veeranam
Yercaud
West/Coimbat Tiruppur Tirupur Alangiyam

ore
Avinashi Anupparpalayam
Palladam Avinashi
Udumalpet Avinashipalayam
Kangeyam AWPS Avinashi
Dharapuram AWPS Dharmapuram
AWPS Kangeyam
AWPS Palladam
AWPS Tiruupur
AWPS Udumalpet
Cheyur
Dhally
Dharapuram
Gudimangalam
Kamachinaickenpalaya
m
Kangeyam
Komaralingam
Kundadam
Kunnathur
Madathukulam
Mahalingapuram
Mangalam
Mulanur
Palladam
Perumanallur
Tiruppur Rural
Trippur North
Trippur South
Udumalpet
Uthiyur
Uthukuli
Vellakoil
West/Coimbat Erode Erode Town Ammapet Govt. Hospital,

Erode
ore
Perunthurai Andhiyur
Bhavani Appakoodal
Gobichettipalaya Arachalur
m
Sathyamangalam AWPS Bhavani
AWPS
Gobochettipalayam
AWPS
Sathyamangalam
AWPS-Erode
Bangalapudur
Bargur Hills
Bhavani
Bhavanisagar
Chennimalai
Chithode
Erode North
Erode South
Erode Taluk
Erode Town
Gobichettipalayam
Hassanur Hills
J.R.S.Puram/Kadambu
r
Kadathur
Kanjikoil
Karungalpalayam
Kavandapadi
Kodumudi
Malayampalayam
Modakuruchi
Nambiyur
Perundurai
Puliampatti
Sathyamangalam
Siruvalur
Sivagiri
Thalavadi
Thingalur
Varappalayam
Vellitiruppur
Vellode
Central/Trichy Karur Karur Town Aravakurichi
Karur Rural AWPS Kulithalai
Kulithalai AWPS-Karur
Chinnadharapuram
Chinnathamanipatty
K.Paramathi
Karur
Kulithalai
Lalpettai
Mayanoor
Palaviduthi
Pasupathipalayam
Thennilai
Thogamalai
Velayuthanpalayam
Velliyanai
Vengal
Vengamedu
Central/Trichy Ariyalur Ariyalur Andimadam
Jeyankondam Ariyalur
AWPS Ariyalur
AWPS Jeyankondam
Bikkiramangalam
Irunbulikurichi
Jeyankondam
Kairalabad
Keelapalur
Kuvagam
Meensurity
Sendurai
T. Palur
Thalovai
Thirumanur
Thoothur
Udayarpalayam
Venganur
Central/Trichy Perambalur Arumbavur Arumbavoor
Mangalamedu AWPS-Perambalur
Kaikalathur
Kunnam
Mangalamedu
Maruvathur
Padalur
Perambalur
V.Kalathur
Central/Trichy Trichy Thiruverumbur AWPS Lalgudi
Jeeyapuram AWPS Manaparai
Lalgudi AWPS Musiri
Musiri AWPS Thiruverambur
Manapparai Bhel
Inamkulathur
Jeeyapuram
Kallakudi
Kattuputhur
Kollidam
Lalgudi
Manachanallur
Manapparai
Manikandan
Musiri
Navalpattu
Pulivalam
Puthanatham
Ramji Nagar
Samayapuram
Siruganur
Somarasampet
Thathaiyangar Pet
Thiruverambur
Thottiyam
Thuraiyur
Thuvagudi
Thuvarankurichi
Uppiliyapuram
Vaiyampatty
Valanadu
Vathalai
Central/ Thiruvarur Thiruvarur Alivalam

Thanjavur
Thiruturaipoondi AWPS Nannilam
Nannilam AWPS
Thiruthuraipoondi
Mannargudi AWPS-Mannargudi
Muthupet AWPS-Tiruvarur
Edaiyur
Eravanchery
Kalappal
Kodavasal
Koothanallur
Koradachery
Kottur
Mannargudi
Mannargudi Taluk
Muthupettai
Nannilam
Needamangalam
Pamani
Paravakottai
Peralam
Perugavalanthan
Thalayamangalam
Thirukkalar
Thirumakottai
Thiruthuraipoondi
Tiruvarur Taluk
Tiruvarur Town
Vadapathimangalam
Vaduvoor
Vaipur
South/ Dindigul Dindigul Town Ambadurai

Dindigul
Dindigul Rural Ambilikkai
Vedasandur Ammayanaickanur
Palani AWPS Kodaikanal
Oddanchatram AWPS Nilakottai
Nilakottai AWPS Ottanchatram
Kodaikanal AWPS Vadamadurai
AWPS-Dindigul
AWPS-Palani
Ayakudi
Batlagundu
Chatrapatti
Chinnalapatti
Dindigul Taluk
Dindigul Town North
Dindigul Town South
Dindigul Town West
Edayakottai
Eriodu
Guzilamparai
Kallimandayam
Kannivadi
Keeranur
Kodaikkanal
Koombur
Natham
Nilakottai
Oddanchatram
Palani Adivaram
Palani Taluk
Palani Town
Pattiveeranpatti
Reddiyarchatram
Sempatti
Shanarpatti
Swaminathapuram
Thadicombu
Thandikudi
Vadamadurai
Vedasandur
Vilampatti
Viruveedu
South/Madurai Madurai Melur Alanganallur
Samayanallur Appanthirupathy
Usilampatti Avaniyapuram
Thirumangalam AWPS Melur
Peraiyur AWPS- Samayanallur
Thirupparankundr AWPS-
am Thirumangalam
Oomachikulam AWPS Usilampatti
AWPS-Thirupparankun
Balamedu
Chatrapatti
Checkanurani
Elumalai
Kadupatty
Kallikudi
Karuppayoorani
Keelavalavu
Koodakovil
Koodal Pudur
Kottampatti
M.Kallupatti
Melavalavu
Melur
Nagaiahpuram
Nagamalaipudukottai
Oomachikulam
Othakadai
Peraiyur
Perungudi
Samayanallur
Saptur L2
Sedapatty
Sholavandan
Silaiman
Sindupatty H3
T.Kallupatti
T.Ramanathapuram
Thirumangalam Taluk
Thirumangalam Town
Thirunagar
Thirupparangundram
Usilampatty Taluk
Usilampatty Town
Uthappanaickanur
Vadipatty
Valandur
Vikkaramangalam
Villoor
South/Madurai Virudhunagar Virudhunagar A.Mukkulam
Sattur Alankulam
Sivakasi Amathur
Rajapalayam Ammapatti
Srivilliputhur Appanaickkanpatty
Aruppukottai Aruppukottai Taluk
Thiruchuli Aruppukottai Town
Aviyur
AWPS Aruppukottai
AWPS Sathur
AWPS Sivakasi
AWPS Srivilliputhur
AWPS-Rajapalayam
AWPS-Virudhunagar
Elayirampannai
Irukkangudi
Kariappatti
Kathanoor
Keelaparalachi
Keelarajakularaman
Koomapatty
Krishnan Kovil
M.Pudupatti
M.Reddiapatti
Mallan Kinaru
Malli
Mamsapuram
Maraneri
Narikudi
Nathampatti
Pandalkudi
Rajapalayam North
Rajapalayam South
Sattur
Sattur Taluk
Seithur
Seithur Rural
Sivakasi East
Sivakasi Town
Soolagarai
Srivilliputhur Taluk
Srivilliputhur Town
Thalavaipuram
Thiruchuli
Thiruthangal
Vachakarapatti
Vanniyampatti Vilakku
Veeracholan
Vembakkottai
Virudhunagar Bazaar
Virudhunagar East
Virudhunagar Rural
Virudhunagar West
Watrap
Madurai City Madurai City DCP, L & O, Anna Nagar Annanagar

Madurai City
DCP, Crime, Madurai Town AWPS Madurai

North(Thilagar Thidal)
Madurai City
DCP, Traffic, Thilagar Thidal AWPS Madurai Town

Madurai City
DCP, Thallakulam AWPS-Madurai South

Headquarters,
Madurai City
DCP, Armed Govt. Rajaji Hospita

Reserve, Madurai
City
ADC, PEW, Jaihindpuram

Madurai City
K.Pudur
Karaimedu
Keeraithurai
Madurai Town Ctrl

(Vilakhuthoon)
Madurai Town East
(Theppakulam)
Madurai Town North

(Thilagar Thidal)
Madurai Town South
(South Gate)
Mathichayam
Sellur
Somasundaram
Colony
Sri Meenakshi Amman
Subramaniapuram
Thallakulam
Thideernagar
Trichy City Trichy City DCP, L & O, Cantonment Airport

Trichy
DCP, Crime & Golden Rock Ariyamangalam

Traffic, Trichy
ADC, PEW, Fort AWPS Cantonment

Trichy
Srirangam AWPS Fort Range
AWPS Golden Rock
AWPS-Srirangam
Contonment
Edamalaipattipudur
Fort
Gandhi Market
Golden Rock
K.K.Nagar
Palakkarai
Srirangam
Thillai Nagar
Uraiyur
Salem City Salem City DCP, L & O, ACP, West, Ammapet

Sooramangalam
Hanging Garden,
Salem
ACP, West- Annadanapatty

Crime, Fairlands
ACP, South – AWPS Ammapet
Salem Town
ACP, South Crime AWPS
- Annathapatti Sooramangalam
AWPS-Salem
Fairlands
Govt.Hqrs Hospital
Hasthampatty
Kannankuruchi
Kitchipalayam
Pallapatty
Salem Town
Shevapet
Sooramangalam
Chennai City Chennai City Adyar Abiramapuram Akkarai Check

Post
Anna Nagar Adyar CMBT -
Koyambedu
Ashok Nagar Aminjikarai Karampakkam
Check Post
Ayanavaram Anna Nagar KMC Hospital -
Kilpauk
Egmore Anna Salai Komaleswaranp
et - Pudupet
Flower Bazaar Anna Square Koyambedu
Check Post
Guindy Arumbakkam Luz Corner
Harbour Ashok Nagar Market -

Koyambedu
High Court AWPS Adyar Naathamuni
Check Post
Kilpauk AWPS Anna Nagar New Secretariat
MKB Nagar AWPS Ashok Nagar Retteri Check

Post
Mylapore AWPS Ayanavaram RSRM Hospital -
Royapuram
Nungambakkam AWPS Egmore Thevar Statue -
Tenyampet
Port Marina AWPS Flower Bazar Thiruvanmiyur
Check Post
Pulianthope AWPS Guindy Velachery Check
Post
Royapettah AWPS Harbour
Royapuram AWPS High Court
Saidapet AWPS Kilpauk
Sembium AWPS Mambalam
T.Nagar AWPS Mkb Nagar
Teynampet AWPS Mylapore
Thirumangalam AWPS Peravallore
Thiruvotriyur AWPS Pulianthope
Thuraipakkam AWPS Royapettah
Triplicane AWPS Royapuram
Vadapalani AWPS Saidapet
Vepery AWPS Teynampet
Villivakkam AWPS Thirumangalam
Washermenpet AWPS Thiruvottiyur
AWPS Thousand
Lights
AWPS Triplicane
AWPS Vadapalani
AWPS Vepery
AWPS Villivakkam
AWPS Washermenpet
Ayyanavaram
Basin Bridge
Chetpet
Chintadripet
Choolaimedu
Dr. R.K. Nagar
Egmore
Elephant Gate
Esplanade
Fishing Harbour
Flower Bazar
Foreshore Estate
Fort St. George
Govt. Estate
Govt. Hospital
Govt. KG Hospital
Govt. Royapettah
Hospital
Govt. RSRM Hospital
Govt. Women &

Children Hospital
Guindy
Harbour
High Court
I.C.F Colony
Ice House
J.J Nagar
K.K. Nagar
Kasimedu
Kilpauk
Kilpauk Medical
College Hospital
Kodambakkam
Kodungaiyur
Kolathur
Korukkupet
Kothavalchavadi
Kotturpuram
Koyambedu
Kumaran Nagar
M.K.B. Nagar
Mambalam
Marina
MGR Nagar
Museum
Muthialpet
Mylapore
Neelankarai
New Washermenpet
Nolambur
North Beach
Nungapakkam
Otteri
Peravalur
Peripheral
Periyamet
Pondy Bazar
Port Marine
Pulianthoppu
Rajamangalam
Royapettah
Royapuram
RSRM
Saidapet
Sastri Nagar
Secretariat Colony
Semanchery
Sembium
Seven Wells
Stanley Hospital
T.P. Chatram
Teynampet
Thiru Vi Ka Nagar
Thiruvanmiyur
Thiruvottiyur
Thousand Lights
3 Thuraipakkam
Tirumangalam
Tondiarpet
Triplicane
Vadapalani
Valasaravakkam
Velachery
Vepery
Villivakkam
Virugambakkam
Vyasarpadi
Washermenpet
Zam Bazar
GRP Chennai GRP Chennai Chennai Central Arakkonam Basin Bridge
Chennai Egmore Avadi Tiruvallur
Coimbatore Chengalpattu Tondaiarpet
Chennai Central Rayapuram
Coimbatore Walajah
Coonur Vellore
Dharmapuri Thirupathur
Egmore Morappur
Erode Hosur
Jolarpet Mettupalayam
Katpadi Pollachi
Korrukkupettai Coonoor
Mettupalayam
Perambur
Podhanur
Pollachi
Royapuram
Salem
Salt Coatur
Tambaram
Thiruvallur
Tirupathur
Tirupur
Tondiarpet
Udhagamandalam
Vellore
Walajah
GRP Trichy GRP Trichy Trichy Junction Ariyalur Cuddalore
Madurai Junction Bodi Ariyalur
Chidambaram Ponmalai
Cuddalore Karur
Dindigul Pudukottai
Golden Rock Kumbakonam
Karaikudi Nagapattinam
Karur Putukottai
Kodai Road Bodi
Kumbakonam Kodairoad
Madurai Manamadurai
Manamadurai Thenkasi
Maniyachi Maniyatchi
Mayiladuthurai Srivillipudur
Nagapattinam
Nagercoil
Palani
Pattukottai
Pudukottai
Rameswaram
Srivilliputhur
Tenkasi
Thanjavur
Tiruchirapalli
Tirunelveli
Tiruvarur
Tuticorin
Villupuram
Virudhachalam
Virudhunagar
*- SCRB has the full right to implement in part or omit all requirements put under this head
The implementation would also cover special units in each of the districts along with their
headquarters. These locations by districts are described in the table below for each district Phase
wise. This should be seen together with the implementation plan described in Section 6.1.1.
District Q- CSG CBCID Crime CCIW EOW Idol PEW DCB CSCID TIW TEW JAPU AVS ADoC
Branch (SIT) Wing
Pilot Phase
Special Unit HQ 1 3 1 0 0 1 0 0 0 0 9 3 2
Sivagangai 2 1 1 1 1 3
Thanjavur 1 4 1 1 1 1 2 3
Chennai Sub- 0 4 1 3 12
urban
Coimbatore City 1 2 1 1 3 15
Sub-total 4 5 7 7 2 0 1 14 4 1 8 33 9 3 2
Roll-out Phase-I
Dharmapuri 1 1 1 1 1
Cuddalore 1 1 1 1 1 1 1 1 3
Nagapattinam 1 4 1 1 1 1 1 1 3
Ramanathapuram 1 1 1 1 1 2
Theni 1 1 1 1 1 1 1
Vellore 1 2 1 1 1 1 1 1
District Q- CSG CBCID Crime CCIW EOW Idol PEW DCB CSCID TIW TEW JAPU AVS ADoC
Branch (SIT) Wing
Thoothukudi 1 3 1 1 1 1 1 1
Kanniyakumari 1 3 1 1 1 1 1 1 1 3
Tirunelveli 1 2 2 1 1 1 1 1 3
Coimbatore 1 2 2 1 1 1 1 3
Nilgiris 1 1 1 1 3
Tiruvallur 1 1 1 1 1 2
Krishnagiri 1 1 1 1 1 1 2
Villupuram 1 1 1 1 1 1 5
Kancheepuram 1 1 1 1 1 1 4
Tirunelveli City 1 1 1 6
Pudukottai 1 1 1 1 2
Sub-total 15 13 18 14 16 7 0 35 17 10 9 41 0 0 0
Roll-out Phase-II
Tiruvannamalai 1 1 1 1 1 2
Namakkal 1 1 1 1 3
Salem 1 2 2 1 1 1 1 3
Erode 1 1 1 1 1 2 3
Tiruppur 1 4
Karur 1 1 1 1 1 1
Ariyalur 1
Perambalur 1 1 1 1
Trichy 1 2 2 1 1 1 1 2
Thiruvarur 1 1 1 1 3
Dindigul 1 1 2 1 1 1 1 6
Madurai 1 2 3 1 1 1 1 2 2
Virudhunagar 1 1 1 1 1 1 1 6
Salem City 1 1 2
Madurai City 1 2 1 1 1 3 7
Trichy City 1 1 1 2 6
Greater Chennai 5 2 1 1 1 1 1 13 30
Sub-total 11 0 22 14 13 9 1 45 17 9 26 74
Total 30 18 47 35 31 16 1 94 38 20 43 148 9 3 2
*- SCRB has the full right to implement in part or omit all requirements put under this table
District SBCID OCIU SIT SB & SDCID DS TS AP SJ & HG STF STPC TNCF Jails District
Core B HR FSL/FP
Cell B
Intelligence Unit Offices Special Unit Non PS Offices
Pilot Phase
Special Unit Non 1 1 1 1 1 1
PS HQ
Sivagangai 1 1 3 3 2
Thanjavur 1 1 5 1 6 3
Chennai Sub- 1 1 9 9 1
urban
Coimbatore City 1 1 1 1 7 1
Sub-total 3 2 0 4 19 9 2 1 0 1 1 16 7
Roll-out Phase-I
Dharmapuri 1 1 1 2 2
Cuddalore 1 1 1 1 6 2
Nagapattinam 1 1 1 1 1 5 2
Ramanathapuram 1 1 1 1 1 2 4
Theni 1 1 1 3 2
Vellore 1 1 1 3 1 10 3
Thoothukudi 1 1 1 2 4 2
Kanniyakumari 1 1 4 4 2
Tirunelveli 1 1 1 2 1 1 5 2
Coimbatore 1 1 1 1 2 1 1 7 3
Nilgiris 1 1 1 2 2
Tiruvallur 1 1 1 1 2
Krishnagiri 1 1 1 1 2 2
Villupuram 1 1 1 1 1 6 2
Kancheepuram 1 1 1 1 2 2
Tirunelveli City 1 1 1 1 1
Pudukottai 1 1 1 5 2
Sub-total 17 5 3 17 25 3 9 0 0 0 0 66 37
Roll-out Phase-II
Tiruvannamalai 1 1 3 2
Namakkal 1 1 2 4 2
Salem 1 1 2 1 5 2
Erode 1 1 3 2 6 2
Tiruppur 2 1 3 2
Karur 1 1 1 3 2
Ariyalur 1 1 1 1 2
Perambalur 1 1 1 1 2
Trichy 2 1 1 2 4 3 1 7 2
Thiruvarur 1 1 2 2
Dindigul 1 1 4 1 1 5 2
Madurai 2 1 1 1 3 1 1 5 2
Virudhunagar 1 1 2 1 2 2
Salem City 1 1 1
Madurai City 1 1 1
Trichy City 1 1 1 1 1
Greater Chennai 3 19 5 1 2 45 1 1
Sub-total 22 19 5 3 3 19 71 6 5 0 2 0 0 47 30
Total 42 19 5 10 6 40 115 18 1 1 2 1 1 129 74
ANNEXURE XII Functional Requirements Specifications

S.No. Functional Requirements
Knowledge Base
1 Media Monitoring – At present, the information from print media and visual media
are manually gathered and maintained as links in excel sheet at each district. These
information are analyzed, grouped under specific keywords and sent to higher
officers on request from district level. It is intended to install a media monitoring
functionality tool which would be able to collate, analyse and prepare dossiers on
specific keywords such as religious extremism from various print and visual media
sources which can help higher offices make useful analyses.
Intended Users: Officials from District SP and above could get dossiers on topics
pertaining to their jurisdiction
FR01 Should facilitate automatic aggregation of related information based on conceptual
understanding by retrieving them from varied sources such as newspapers,
magazines, emails and other physical media and electronic media including news
channel videos, phone calls, e-newspapers and other multimedia available in
English and Tamil from various districts centrally in SCRB
FR02 Should facilitate automatic extraction of meaning, analyze the data and hyperlink
related fields and events present across multiple media sources
FR03 Should enable integration with other unstructured data available in the department
FR04 Should facilitate contextual data search of the integrated database
FR05 Should be able to facilitate querying unstructured data

FR06 Should be able to prepare reports based on automatic meaning extraction and
analyses to pre-defined set of officials who may be interested in the specific topic
FR07 Should be able to mail the results of query and contextual search to the official
concerned
FR08 Should be able to alert through emails/SMS, investigators and agencies to breaking
news which may still not have reached the department before the press
FR09 Should facilitate analyzing scenes and recognize faces and vehicle number plates
in areas where videos captured through CCTV Cameras are available.
2 Police Intranet – There is no department specific web enabled repository of
knowledge at the moment. It is proposed to develop an intranet website which
would also have a log-in feature for personnel. The portal would hold details on
Police Acts, Rules, Helpline/Checklist for case registration, Investigation,
prosecution for various types of cases, official promotions and transfers and so on.
Intended Users: Personnel from Constabulary till DGP

FR10 The existing TN Police Intranet should be upgraded to a website based on suitable
content management system
FR11 The Intranet System should support role based content creation and distribution
FR12 The Intranet System should support automatic email alerts based on roles assigned
in the system
FR13 The Intranet System should have PSO, circulars, conduct rules, Acts, etc. for easy
reference
FR14 The Intranet System should allow role based updation of PSO, circulars, conduct
rules, Acts etc
FR15 The Intranet System should allow users to login to the HRMS provided by NIC for
updation and retrieval of records
FR16 The Intranet System should allow police personnel to register their grievances
FR17 The Intranet System should provide with online help manual to assist in using the
Intranet System, CAS (State) and other modules developed.
FR18 The Intranet System should provide search facility to access specific information
from the databases e.g area specific information, crime & criminal information,
victim details, lost / found property, unidentified dead bodies etc.
Traffic Suite
3 Patrol and Police Control Room Call Interface – The Complaints are also
registered through the Central Police Control Room at the State Headquarters that
is accessible to the public through Emergency Contact number (100) and Women
and Child Helplines.
Intended Users: Police Control Room Operators at Districts and

Commissionerates, Police Station Users such as SHO, Highway Patrol Vehicles
FR19 The system should display all the unanswered calls and the call/caller details to the
user. In case some calls are unanswered due to unavailability of personnel, the
head of the PCR would get the details of the unanswered calls. It would also allow
them to call back the number to ascertain the details of the calls.
FR20 System should arrange the incoming calls in the order that come in. The system
would arrange the calls on FIFO (First-In-First-Out) basis and the calls would be
allotted to the first available personnel.
FR21 The system should allow the user to answer /respond to the call through the user
interface. The user interface would be designed in such a manner that the PCR
personnel need to use only the interface to respond to calls.
FR22 The system should allow the user to record the call along with timestamp and
capture it in the system,
FR23 In case the call(s) comes in for an already registered complaint, the system should
allow the user to link the call(s) to the registered complaint.
FR24 System should provide an interface to the Police Control Room (PCR) to capture
the details of the complaint and the caller / complainant through a “quick capture
complaint form” relevant for a complaint that is reported in through a phone call,
email, walk-ins in emergency or a non-emergency situation.
FR25 In case the caller reports a complaint that is within the jurisdiction of the Police
Control Room (either State HQ or District), the system should allow the user to
identify the appropriate police station or available patrol vehicle and transfer the call
to the same for response.

FR26 In case the caller reports a complaint that is outside the jurisdiction of the PCR
(either State HQ or District HQ), the system should allow the user to transfer the
calls to the appropriate police control room that has the jurisdiction.
FR27 The system should allow the user to record the details of complaint assignment and
the action taken by the responder on the complaint.
FR28 Should provide the reports and search capabilities on the call registered/logged
FR29 Should allow facility to pass on information/complaint lodged/provided by citizen to
the concerned Police Station so that IO can follow up accordingly for enquiry.
FR30 Should allow facility to receive SMS from citizens sent and respond to their queries
with respect to status of case or permission request, etc.
FR31 Should store details of calls logged and action taken in the Police Control Room
Call database server located at each Police Control Room
FR32 Should allow separate interface for storing details of calls logged regarding VIP
movements, law & order situation in the Police Control Room Call database
FR33 Should allow listening to feed from the highway patrol devices, for converting the
feed into readable format for control room and for generating various reports.
FR34 Should allow display of complete fleet information of vehicles on Highway Patrol in
one screen for each District Control Room
FR35 Should allow capture details of the following in the form of a Report from each
Highway Patrol vehicle through a handheld device and store the data in the Control
Room Call Database:
 Distance Traveled Report
 Vehicle Productivity Report
 Customized distance report – provides information on time periods defined
by the user between any dates
 Night Drive Report
 Entry and Exit Report at pre-mapped locations
 Route Deviation Report
FR36 Should present route map for each of the highway patrol vehicle for its assigned
route in the handheld device
FR37 Should program the boundary for each of the highway patrol vehicle in the
handheld device and in case of any deviation from the fencing, it should be
communicated to the District Control Room
FR38 Should be able to maintain log of Movement (including direction) and/or Halt of
patrol vehicles communicated automatically form handheld device in the application
in the District Control Room
FR39 Should be able to send alerts automatically from handheld device to the District
Control Room in case of violations relating to Speed monitoring, halt duration
monitoring, route deviation and emergency. These should be captured in the
application in District Control Room
FR40 Should be able to send Trip Sheet details to District Control Room using handheld
device in the patrol vehicle
FR41 Should allow all reports to be downloadable to Excel

FR42 Should have the capability to extract victim /accused details from CAS (State)
database and transmit the same to Patrol Vehicle device on request
4 RC Book/DL Verification, Spot Fine – There is no instant access to checking
driver/vehicle credentials by traffic policemen. It is proposed to empower field level
traffic policemen to enable them to check credentials on the spot and issue spot
fines.
Intended Users: Additional Commissioner, Traffic and DCP in cities and SPs in
district under whose jurisdiction Traffic enforcement and Traffic investigation
falls.SCRB will access the resources for the purpose of statistics
FR43 The System should facilitate knowing about the status of vehicle – whether it is
stolen or involved in crime or otherwise.
FR44 The System should provide information on the previous history of involvement of
vehicle or driver in accident(s)
FR45 The Handheld Device/Mobile Data Terminal should facilitate search on the basis of
a variety of parameters including vehicle number/chassis number/engine number
and name of driver.
FR46 The System should facilitate automatic transfer of data (E.g., Printed Challans of
traffic violation) from the Hand-Held Device/ Mobile Data Terminal to the Back-end
Server Database; The System should also provide the team managing the traffic
management challans with the necessary reports, statistics and aid in the
monitoring and control of money collection and reconciliation of payments against
the challans issued. The System should also ensure expansion history of past
offences of a particular person.
5 Fingerprint – At present, there is no automation of linking the crime data captured

in FIR to previous fingerprint data. Also, fingerprint database enters criminal data
again along with entry already done for FIR. It is proposed to tag fingerprint to crime
and criminal data wherever available and also facilitate capturing of fingerprint
images and tag it to crime data for new criminals so that it will be integrated as one
database:
Intended Users: Beat Constables, TNFPB

FR47 The Handheld Device/ Mobile Data Terminal should be capable of retrieving
relevant data relating to the Public violators, Bad characters & Ex-Convicts from the
database of the Tamil Nadu Police Department located at State Fingerprint Bureau.
FR48 The Handheld Device/ Mobile Data Terminal should allow Beat Officers to perform
a quick verification of an individual against an ID card or Database or Finger Print
Verification
FR49 The Handheld Device/ Mobile Data Terminal should facilitate Police personnel to
identify unconscious victims against the database Tamil Nadu Police Department
located at State Fingerprint Bureau and also compare with the UID Database (as
and when it is made available)
FR50 The Handheld Device/ Mobile Data Terminal should facilitate search on the basis of
the finger print identification of the suspect/culprit
FR51 The Handheld Device/ Mobile Data Terminal should be able to capture and store
finger print of violators, register new suspects etc
6 Business Intelligence - The system would allow presentation of graphical
analyses of data drawn from various databases.
Separate dashboards would be presented to higher officials based on their

jurisdiction ranging from SP till Headquarter level higher officials
Separate dashboards would be presented to field level staff for their jurisdiction for
different type of crimes ranging from station level officer to sub-divisional/range
officer
Separate Dashboards should be made available at functional level for different level
of officers specific to the special units.
FR52 The system should allow the user to create visual presentations like pie charts,
graphs and thematic maps.
FR53 The system should allow user to select the data fields from the data base of State
CAS.
FR54 The system should allow user to select different geographical entities like Police
Stations, Districts, and Ranges etc. and generate thematic maps based on the data
sets selected.
FR55 The system should generate thematic maps based on different colour codes to
differentiate between different entities selected for display
FR56 The system should have the capability to drill down to the lower levels from the
generated graphs to see the individual values of the data set.
FR57 The system should have the facility to generate adhoc, dynamic and regular reports
from the State CAS
Communication Suite
1 Social Networking – There is a need to harness the power of social networking for
efficient information sharing between citizens and department. It is proposed to
establish a link between the Police Intranet website and the Tamil Nadu/Chennai
Community home page in Social networking sites such as Facebook, Orkut and
Twitter through which important notifications can be issued to the public such as
traffic diversions, election duty announcements. Also, citizens may be able to post
messages or photos on hit and run cases, thefts on this portal which would be
checked at SCRB for suggesting suitable course of action
Intender Users: Citizens and all department personnel from constable to DGP
FR58 A dedicated page should be created on one of the popular Social Networking
websites for TN Police.
FR59 The choice of the website should be in consultation with TN Police
FR60 The dedicated page should display the important contact numbers of each district
control room and SP Offices in the state.
FR61 The dedicated page should have the facility to for the citizens to upload
photographs of traffic incidents / violations
FR62 The dedicated page should provide the choice of displaying / hiding the name of
uploader of photograph and this choice should be made available to the citizen who
is uploading the photograph.
FR63 The dedicated page should also provide the update and the action taken by TN
Police on the photographs of traffic incidents / violations
FR64 The dedicated page should mention clearly on the landing page that fraudulent /
mischieveous uploading of photographs would amount to misusing of the facilty and
liable for action by TN Police
FR65 The dedicated page should be able to store the IP address of the uploader and the
same should be mentioned clearly on the landing page so that fraudulent /
mischieveous use of this facility would be reduced.
2 Mobile Interface – There is a need to facilitate instant communication between
officials to ensure quick action on situations such as additional reinforcement during
bandobust. It is proposed to set-up an SMS server through which pre-defined
messages may be communicated to enable swift action to be taken.
Intended Users: Citizens, Officers from SHO to Zonal IG, DCP, Police Control
Room
FR66 The System should be able to communicate the details of a traffic violator to the
concerned Police Control room over SMS so that they would inform the next Police
men on that route over phone so that the offender can be tracked, stopped and
apprehended
FR67 The System should provide Position verification of resources during bandobust to
the coordinator. There should be a facility to send SMS from a bandobust sub-
group member to concerned DC asking for more reinforcements to handle a Law &
Order Situation
FR68 The System should provide a fully customizable module wherein a superior officer
can register his mobile numbers and those of his sub-ordinate officers. The SMS
Server will send reminder SMS 2 days before due date for sending MIS reports
such as status reports and abstracts pertaining to CAS Functionalities to both the
Police Station personnel and the higher official who has to review these reports to
enable timely submission and approval of these report.
FR69 The System should provide facility to know status of the complaint/FIR by keying in
the acknowledgement number
FR70 The System should provide facility to send bulk SMS from Police Control Room to
public on matters of public interest such as helpline numbers during emergency and
special alerts in case of events such as elections
Law & Order Suite
1 Mass Event Monitoring – There are events happening around the year for which
the department has to design bandobust schemes, identify places for positioning
resources, identify resources, acquire the resources, deploy and monitor them.
System would facilitate developing schemes of bandobust and specify

corresponding resource requirement for positions defined on the scheme. The
System would allow looking for resources for plotting by contacting various district
SPs, armed police units and home guard offices. The resource assigned would be
monitored during mass deployment using GIS and/or CCTV Cameras set up in
temporary control rooms in the event spot as maybe the case. The system would
allow provision to maintain the details of resources, their home base, vehicle
details, contact details including mobile number, place they are deputized to work
and so on. This would enable tracking of the resources as and when needed.
Intended Users: DC,SP, Special Units such as Armed Police, Armed Reserve and
Commando Force, Security Forces and L & O Constables, Special Battalions,
Home Guards
FR71 Should provide a calendar of events for the year which would be used to mobilize
resources for event monitoring
FR72 System would facilitate developing schemes of bandobust for the event, e.g, cricket
match bandobust and specify corresponding resource requirement for positions
defined on the scheme.
FR73 Should allow planning for bandobust activities and help identify resources from
across districts for deployment. For identified resources, system should allow
sending emails to concerned district SP for permission
FR74 Should allow positioning resource in a specific area in a bandobust and monitor the
position of the resource using messages transmitted through the handheld device
which would be sent to the SP Office where the application should analyse the
position and send back message in case resource is not in his designated area
FR75 Should allow maintaining the details of resources, their home base, vehicle details,
contact details including mobile number, place they are deputized to work and so
on. This would enable tracking of the resources as and when needed.
2 Prisoner Escort - This would present activities to be done by each escort during
handling prisoners in the movement of prisoners from
1) Police Station to Court
2) Jail/Home to Court
3) Court to Jail/Home
4) Jail to Jail
5) Court to Police Station in case of police custody
Intended Users: Armed Reserve Constables.act as escorts, DC (AR),

Commandants send escorts
FR76 The system would be based on Beats Management System above.
FR77 The system should allow the head of the police station to feed in the details of
prisoner, location of pickup, location of destination (court, hospital, transit stay in
another jail, transfer to another prison etc) , shortest route to be undertaken,
estimated time of pickup and estimated time of arrival at destination.
FR78 The system should update the location of the escort party on a predetermined
interval to the server.
FR79 The system should generate alerts in case the escorting party deviates from the pre
assigned route.
FR80 The system should have the facility fo the escorting party to initiate the journey at
the time of pickup and close the journey after arriving at the destination.
FR81 The system should generate alerts in case there is no initiation of journey details by
the escorting party. A slack can be allocated for delays during travel.
FR82 The system should generate alerts in case there is no closure of journey by the
escorting party. A slack can be allocated for delays during travel.
FR83 The system should generate these alerts in the form of popups in the State CAS
Application at the source and destination police stations.
FR84 The system should maintain logs of each journey performed for a minimum period
of Six Months.
FR85 The police team escorting the prisoners should be intimated to the control room
before hand. The System should allow entry of details of team members, their
name, rank, phone number and unit where belongs which should be made available
to the Control room before escort takes place.
FR86 There would be facility to intimate concerned control room on departure of escort
over SMS with details so that traffic police on that route would be staying alert.
FR87 In case of any halts in between, the system should facilitate corresponding
message communication to the concerned control room over SMS.
FR88 The system should have the capability to inform the users in form of reminders for
the upcoming Prisoner Escort for atleast 2 days in advance.
3 CCTV Solution – It is proposed to develop systems which will link up with CAS
State database for storing images captured in CCTV cameras installed in critical
places and images captured during monitoring of large public gatherings and main
traffic points in the city
Intended Users: From Commissioners till Jurisdiction/ Bandobust In-charge Officers
in Commissionerates, From SP till Jurisdiction Officer in Districts
FR89 The system should be deployed at al the important traffic junctions in the 7
commissionerates of the State.
FR90 The system should have the capacity to store the images received from each
camera at the Monitoring Unit located at the Police Control Room of each
commissionerate.
FR91 The system should deploy Pan-Tilt-Zoom (PTZ) platform for each of the cameras
FR92 The (PTZ) platform for each camera should be controlled from the Monitoring Unit
FR93 The system should use Automatic Number Plate Reading(ANPR) Cameras to allow
users to record the number plate of the traffic violators
FR94 The ANPR Cameras provided in the system should have the capability of local
storage.
FR95 The system should have wireless connectivity between the cameras at the traffic
junctions and the Monitoring Unit.
FR96 The system should have a one way audio transmission capability from the
Monitoring Unit to the Traffic Junction for important announcements.
FR97 The system should have capability to search thru the archived recording based on
time of the day and name of location.
Constable Suite
1 Beats Management – This is a regular activity at the police station performed by
the constables in their designated area, viz. beat and broadly covers the following
activities:
1) Service of Process
2) Enquiry of BC/KD/DC/HO/Ex convict
3) Enquiry about strangers, suspects, receivers of stolen property, criminals,
antisocial elements, fundamentalists
4) Enquiry about Contraband, gambling, prostitution, illegal money collection,
lottery tickets, drug trafficking, idol thefts, sand quarry, etc.
5) Enquiry about group clashes w.r.to Caste, communal and religious conflicts
6) Enquiry about SB Activities
7) Enquiry about Explosive Stocking
8) Inspection of Vital Installations
9) Monitor Fairs and Festivals
10) Locked Houses’ Check
11) Check Wanted Criminals
12) Check Spread of Communicable Diseases and Effects of Natural
Calamities
Intended Users: From Beat Constables to SP/DSP/DC. Higher Officers review the
beat activities done
FR98 The Handheld Device/ Mobile Data Terminal should facilitate recording the action
taken by the Beat officer at the spot which should be entered/submitted to the
database along with all details and action taken, including arrest of suspect,
impounding of vehicle, etc.
FR99 The Handheld Device/ Mobile Data Terminal should be able to capture photographs
of crimes/ evidences to be forwarded to the court for certain category of offences.
FR100 The Handheld Device/ Mobile Data Terminal should be enabled with GPS system
for capturing the Geographical locations of spots visited and checked during a Beat.
FR101 The Handheld Device/ Mobile Data Terminal should have layers of Beat and Police
Station along with vital installation, bad characters, important landmarks, etc.
embedded on the GPS map. The layers may be added on top of the maps at the
GIS server at the database end and this could be read by the Handheld Device/
Mobile Data Terminal. The System should also provide facility to create beats and
modify set beats
FR102 The System (Refers to the Core Application Software) should cover and register all
details pertaining to the respective Police Station and allow modification of the
same. This enhancement is expected to be done by System Integrator
FR103 The System (Refers to the Core Application Software) should enable the user to
add any activity; for ex. Passport verification, Bad Character verification, Summon
issuance, etc. This enhancement is expected to be done by System Integrator.
FR104 The System (Refers to the Core Application Software) should enable
Synchronization of data in the desktop, server application and the handheld
application through a separate module developed for this purpose. This
enhancement is expected to be done by System Integrator
FR105 The Beat System (Refers to the Handheld Device, application and the backend
database pertaining to beats) should facilitate performance of surveillance and
monitoring of the locations and public assets maintained in the Part IV (Village
Database) of the respective Police Station.
FR106 The Beat System (Refers to the Handheld Device and the backend application
pertaining to beats) should facilitate creation of Beat & Allocation of Beat Duties as
per the specified roster of the respective Police Stations after taking into account
availability of personnel after accounting for leaves, pre-decided bandobust duty,
etc. Any modifications in the roster such as transfer of personnel or non-availability
of personnel due to an emergency should be reflected in the beat system
automatically.
FR107 The Handheld Device/ Mobile Data Terminal should be able to access from the
main database Server and display upon request, details such as Pop-up
tables/codes, vehicle and license details, all types of offences, fines, offence types,
incident details etc., in order to minimize the amount of data to be inserted by the
Beat Police Officer.
FR108 The System (Refers to the Handheld Device, application and the back-end
Database Server pertaining to traffic data) should provide features wherein when a
criminal’s name is entered the database server should be able to send all the
details relating to the criminal including previous offence history.
2 Explosives Checking – This would be done by Station Officers to check whether
permissible levels of explosives are maintained
Intended Users: Station House Officers

FR109 Should provide a facility to enter details of name and license number of shops,
quantity of explosives, past history in explosive related violations for shops in each
Sub-division jurisdiction and store it in the database
FR110 Should allow setting safe limits of explosives for shops and should alert whenever
quantity entered exceeds this limit to District SP and DSP
FR111 Should allow preparation of monthly reports on explosives checks done and
statistics related to explosive shops for each of the sub-division which can be
aggregated at District level, Range Level, Zonal Level and State Level
3 Passport Verification - Application comes from RPO to IS. From IS, it is sent to IS
constables in Police Station. After verification, the report is sent to Passport
Inspector at Commissionerate. Passport Inspector through DC, IS sends the
verified application to RPO.
In districts, it goes to DCRB. From DCRB, the application is sent to SB constable at
local police station. The police station sends report after verification to DCRB who
sends it back to RPO through Collector/SP.
It is intended to receive applications online from RPO through passport e-seva. The
verified application and report are intended to be sent back online to Passport
Office. The interface for receiving and sending the verification is expected to be
developed by SI.
Intended Users: SB/IS Constables, SP, DC(IS), Passport Inspector

FR112 The system should interface with the Passport Seva System which is currently
undergoing Pilot Testing in Bengaluru and Pune.
FR113 The system should take the Personal Particulars form from the Passport Application
and forward it to the respective Police Station.
FR114 The system should allow user to take a printout of the Personal Particulars form.
FR115 After the physical verification of the Passport Applicant, the system should allow the
police station user to fill in the required details and comments if any.
FR116 The verification form should automatically fill in the required details from the
Personal Particulars form received.
FR117 The system should maintain records of all passport verification request received
/verified / rejected.
FR118 The system should forward the verification form back to the Regional Passport
Office from where the Personal Particulars Form was originally received.
The envisaged To-be scenarios for the following functionalities are illustrated below:
 Knowledge Base
o Media Monitoring
o Intranet Portal
 Traffic Suite
o Patrol and Police Control Room Interface
o RC Book/ DL Verification, Spot Fine
 Crime Analysis Suite
o Fingerprint
o Business Intelligence
 Communication Suite
o Social Networking
o Mobile Interface
 Law & Order Suite
o Mass event Monitoring
o Prisoners Escort
 Constable Suite
o Beats Management
o Explosive checking
o Passport Verification
It is expected that this would give the SI a fair idea of the process envisaged with the inclusion of
these new functionalities
Patrol and Control Room Module

Process Description
Law & Order and Police
Department Service Requestor Citizen, Police Personnel
Control Room
Stakeholder Involved Citizens, Police Department, Government
Details of the caller and
Complaint Management
Input their complaint and Output
and effective action
Crime Scene details
Objective The Objective is to effectively manage the PCR Complaints and Patrolling Activities
Main Scenario
Sr.No Activity Steps Actor
PCR receives call from Citizen or Police Personnel and will capture the
1 details of caller and complaint. System checks the PCR Call Interface Police Control Room
database for similar complaint
If the system could find similar complaint, it will give the option to link the
1a Police Control Room
call to the previously registered complaint.
If it is new complaint, then the Control Room Personnel will find out the
1b required details and enquires if it need to send the Patrolling unit to the Police Control Room
crime scene and informs accordingly.
Nearest Patrolling Unit will go to the crime scene and informs the details of
2 Patrolling Unit
the crime scene to PCR along with backup requirement.
PCR captures the details given by the onsite Patrolling Unit and will refer
3 the Complaint to the Police Station under whose jurisdiction the Crime has Police Control Room
occurred.
Police Station receives the complaint and will proceeds for registration/
4 Police Station
investigation
Highway Patrol vehicles send reports of distance and area covered and
5 Highway Patrol Vehicle
specific accident related information, if any to the District control room
Police Control Room receives report and in event of any route deviation
6 Control Room
alerts highway patrol vehicle accordingly to retrace to correct path
The process overview of the Patrol and PCR Call Interface System is illustrated below:
Patrol and Police Control Room Module Process Overview
Media Monitoring
Process Description
Inspectors till DSP, SP
and Above, Other
Department Police Department Service Requestor
Department, Assembly
and RTI
Stakeholder Involved Police Department, Government
Inputs relating to fetching Generation of information
Input Output
and searching in a report format
The Objective is to have an effective search mechanism of unstructured data
Objective including media sources for effective usage of Police Department data especially in
the investigation process
Main Scenario
Information sought from various stakeholders (keyword specific search,
1 MO specific search, name specific search or area specific search) is Police Personnel
received at SCRB
SCRB searches the repository of media monitoring dossiers, crime data
residing on central server, CCTV footage using the media monitoring
2 SCRB
application front end to generate report on possible leads, statistics or
investigation aids
System provides the information in the report format through mail and
3 SCRB
SMS to concerned user who had raised the request
Report is used to answer assembly questions or prepare for monthly DSP and Above,
4
review meeting and so on Assembly
The process overview of the Media Monitoring Functionality is illustrated below:
Media Monitoring Process Overview
RC Book/DL Verification, Spot Fine and Finger Print

Process Description
Department Traffic Police Service Requestor Traffic Police
Stakeholder Involved Citizens, Police Department, Government
Input Offence committed by Output Issue of Challans,
any driver, details are Verification of
captured by Traffic Antecedence using
Police Fingerprint
Objective The Objective is to verify RC Book/ DL Verification and issue spot fine to the traffic
Violator
Main Scenario
1 Violates traffic rule / General verification Traffic Police
2 Traffic policeman verifies the RC Book/ DL and finger print( if necessary) Traffic Police
with the help of Handheld device
3a If the vehicle is not stolen and verifies deviates/ traffic violation, the traffic Traffic Police
police will issue Challan
3b If the vehicle is stolen, the system will alert the Police Control Room, Other Agencies
nearest Police Station and nearest Patrolling Unit
4 The appropriate action is taken is to catch the accused Other Agencies
5 Informs the on-field officer about the action taken Traffic Police
6 Traffic Policeman deposits fine with details of fines handed out in the Traffic Police
Commissioner/SP Office at end of his daily duty hours
7 SP Office/Commissioner Traffic Section stores details of fines collected by SP
each policeman in the application Office/Commissionerate
The process overview of RC Book/DL Verification and Spot Fine Issuance is illustrated below:
RC Book/DL Verification, Spot Fine and Finger Print Process Details
Mass Event Monitoring

Process Description
SP, DC, L & O
Constables, Special
Units such as Home
Guard, Armed Police
Scheme development,
Creation of mass event Resource deployment for
Input and entering the details Output scheme and Event
of mass event activities Monitoring, alerting and
generation of report
The Objective is to monitor the Mass events which takes place in the state for
Objective
smooth flow of the event and public safety
Main Scenario
SP Office will take stock of bandobusts, create schemes and identify
1 SP/DC Office
resources for deployment.
2 The approved orders is sent to all the involved Police Personnel SP/DC Office
If any changes are needed to be incorporated, change request is raised for
3 SP/DC Office
modifications
4 Identified resources are called on board after obtaining requisite approvals SP/DC Office
Stores the details of personnel, mobile number, home base, vehicle
5 SP/DC Office
number and other inventory details
Positions of resources in scheme and any troublesome situation is sent via
6 On field personnel
handheld device
7 SP/DC orders for backup or asks for repositioning to right location SP/DC Office
The process overview of the Mass Event Monitoring Functionality is illustrated below:
Mass Event Monitoring Process Overview
Prisoners Escort
Process Description
Armed Police, DC (AR),
AR Constables,
Commandants and
Escorts
Inputs regarding the
prisoners escort for
following situations:
1) Police
Station to
Court
2) Jail/Home to
Court
Generation of report and
Input 3) Court to Output
alerting services
Jail/Home
4) Jail to Jail
5) Court to
Police
Station in
case of
police
custody
Objective The Objective is to successfully transfer the prisoners from one location to other
Main Scenario
Head of the Police Station will enter the details of Prisoners Escort which
1 includes, prisoners detail, police personnel escorting, source, destination, Police Station
travelling route, inventories etc
System should be able to track the vehicle constantly checking with the
2
travelling route, and will inform in case of any discrepancies
If there is any discrepancy, alert the PCR, nearest Police Station and
3 Other Units
nearest Patrolling Unit.
4 Enter the details of discrepancy Police Station
5 After the completion of the activity, report is generated.
The process overview of the Prisoners Escort Functionality is illustrated below:
Prisoners Escort Module Process Overview
Beats Management
Process Description
Department Police Department Service Requestor Police Personnel
Inputs of the activities
alerting services,
Input performed, action taken, Output
Updation of KD/DC
Part IV Village Database
Check Register
The Objective is to enter the action taken by the On-field officer at any crime/ illegal
Objective
activity place.
Main Scenario
On-field Officer enters the details of any crime scene he come across
1 On-field Officer
during patrolling/ other duties
If there is any backup requirement or major criminal activity is going on,
2 Other Units
the system will send alert to other units
Sends the review report to the superiors regarding the usage of system,
3 Other Units
most similar search etc
4 The appropriate action is taken is to catch the accused Other Agencies
5 Informs the on-field officer about the action taken On-field Officer
6 Update the situation with the action taken On-field Officer
7 Report is generated on the activity
The process overview of the Beats Management Functionality is illustrated below:
Beats Management Process Details
Explosive Checking
Process Description
Inputs of the license
Input shops, quantities of Output
alerting services
explosives etc
The Objective is to effective checking of explosive shops and transaction in
Objective
explosives
Main Scenario
Police Station registers the new explosive shops, quantities of explosives,
1 Police Station
its transactions etc
2 If the quantities of explosives cross the safe limit, it will alert the SP/DSP
3 Update the system with the action taken, upload any permissions etc SP/DSP
The process overview of the Explosives Checking Functionality is illustrated below:
Explosive Checking Process Overview
Passport Verification
Process Description
Inputs of verification
Input Output Generation of report
details
The Objective is to verify the passport applications and inform the same to Passport
Objective
department
Main Scenario
SP Office will receives the request of passport verification from RPO and
1 SP Office
on request the system will direct it to respective Police Station
The field-officer updates the verification details and sends it for approval to
2 Police Station
SP Office
3 SP Office approves it and send it to Passport Department SP Office
Details of Police Verifications and its status is saved in the station
4 Police Station
database using the application developed
Details of successful verifications done at each district would be passed on
5 SP Office
as feed to Passport e-seva application
The process overview of the Passport Verification Functionality is illustrated below:
Passport Verification Process Overview
Ministry of Home Affairs RFP for Tamil Nadu 298 of 302

ANNEXURE XIII Non-Functional Requirements Specifications
S. No. Non-functional Requirements

I. Technical Solution Architecture Requirements
NFR 1 The System Solution needs to be architected using robust and proven software and
hardware technologies like Service-Oriented Architecture (SOA) and open standards.
The solution architecture should be built on sound architectural principles enabling
fault-tolerance, high-performance, and scalability both on the software and hardware
levels. The proposed solution should support a drag and drop GUI based process
modeler for constructing business flows.
It is desired to have a service bus for message broking between various applications.
NFR 2 The proposed products should be certified to run on Linux 2.6.
The proposed system should comply to open standards that is published and adopted
by the worldwide vendors & industry forums.
The underlying operating system should have inherent (without any add-on or plug-in
software) capability to resist from virus attacks
All software products proposed for middleware and database must run in Active-Active
(High availability) configuration mode.
II. Software Architecture Requirements
NFR 3 Software architecture must support web services standards including XML, SOAP,
UDDI and WSDL etc.
NFR 4 Software architecture must support flexibility in adding functionalities or applications.
NFR 5 Software architecture components should utilize the high availability, clustering, and
load balancing features available in the proposed hardware architecture to increase
system performance and scalability features.
NFR 6 Software architecture must support trace logging, error notification and resolution and
exception handling and auto roll back during batch failures. Software architecture
should also notify the technical users of the application on the memory utilization by
providing the auto alert mechanism.
III. Hardware Architecture Requirements
NFR 7 Hardware architecture must provide redundancy and high availability capabilities at the
hardware level; this includes servers, network components, and storage system.
NFR 8 All servers and systems must be configured with no single point of failure.
NFR 9 Hardware architecture should be capable of consolidating several applications /
workloads in a number of servers as required.
NFR 10 Hardware architecture servers must be placed within proper network locations to

satisfy the security requirements of the Solution.

NFR 11 Hardware architecture must include Storage Area Network (SAN) and backup solution
to support all portal hardware and software components.
NFR 12 SI is required to deliver sound and complete technical solution architecture for System
Solution with high performance, redundancy and scalability. SIs are required protect
critical information architecture and cater to technical perspective, business
perspective, law enforcement prospective and national security perspective.
IV. Development, Testing, Staging, and Production Requirements
NFR 13 SI is required to provide appropriate development, test, and staging hardware
environments and explain how they are related to production environment. SI is
required to explain how the development, test, and staging environment support the
implementation activities of System Solution. Development, test and staging
environment will be different from Production environment. At the end of the term these
environment will belong to the department.
NFR 14 Development and test environment should include configuration management
capabilities and tools for system configuration, versioning scheme, documentation,
change control processes and procedures to manage deployment of solution
deployment.
NFR 15 The test, development and staging environment should include required workstations,
desktops and tools appropriate to support development, testing, staging and
deployment.
NFR 16 The development, test and staging environments must include similar operating
systems, software components, products, and tools to those of production
environment.
NFR 17 The development, test, and staging environments should be independent logically and
physically from the production environment and of each other.
NFR 18 The development environment should be used for development and should be
configured to allow access for developers’ workstations.
NFR 19 The staging environment should be used for functional and user acceptance testing,
stress testing, and performance benchmarking.
NFR 20 The test environment should be used as a testing environment of System Solution and
its software components and products.
V. Security Requirements
NFR 21 It should have a secure solution at the hardware infrastructure level, software level,
and access level.
NFR 22 Authentication, Authorization & Access Control
It is required to implement necessary security mechanisms to enable secure login and
authorized access to portal information and services.
NFR 23 Encryption: It is required to ensure confidentiality of sensitive information and data of

users and portal information.

NFR 24 It is required to implement mechanisms, protocols, and algorithms necessary to protect
sensitive and confirmation data and information both during communication and
storage. Virtual Directory should be used for single sign on, as meta directory or
synchronization between directories creates un necessary duplication of user
information.
Must provide password management capabilities like, password resets, password

synchronization: The tool must also allow users to reset their passwords on those
applications that they have accounts on without the intervention of the administrators /
helpdesk. This will improve efficiency at the same time reduce the workload of the
administrator / help desk groups. Ability to generate audit reports without all of the
target resources being available. Historical data should be readily available – no
customization should be required. Diagnosing the cause of the problem, and resolve it
with minimal to no down time.
VI. Monitoring and Management Requirements
NFR 25 The Central System Solution should provide monitoring and management of the entire
Solution including all software components and application.
VII. Performance and Scalability Requirements
NFR 26 SI is required to design the overall System Central Solution with high performance and
scalability to handle increasing number of users.
NFR 27 SI is required to deliver System Solution that provides measurable and acceptable
performance requirements for various user groups, channels and bandwidths.
VIII. General Non Functional Requirements
NFR 28 The System should provide User ID and Password for facilitating entry.
NFR 29 The System would facilitate access to the system only through user ID and password
NFR 30 The System (Refers to the Core Application Software) should facilitate logging in
through web and generating desired MIS reports.
NFR 31 The System (Refers to the Core Application Software) should facilitate provision of
varied information to the higher officials on a regular basis and also on a need basis.
NFR 32 The System (Refers to the Core Application Software) should provide the facility to
generate various statutory reports, reviews and abstracts for the smooth functioning of
the Department.
NFR 33 The Handheld Device/Mobile Data Terminal should have a software application
connecting to the database server.
NFR 34 The System (Refers to the System involving the Handheld Device and Server
accessed by the device) should have uninterrupted network connectivity with the
Central Database server which should be established by the System Integrator through
GPRS/GSM.
NFR 35 The Handheld Device/Mobile Data Terminal should facilitate finger print verification of

the user based on proper authentication. There could be multiple departmental users
intending to use the device
NFR 36 The Handheld Device/Mobile Data Terminal should have sufficient memory to
effectively handle the processes in an off-line mode in the event of a GPRS/GSM
connectivity failure It should push the data to database as and when the GPRS
connectivity/ Wire connectivity to the system is restored.
NFR 37 The Software System (Refers to the System involving the Handheld Device and Server
accessed by the device) should work in Client-Server architecture where in the
Handheld Device/Mobile Data Terminal shall serve as a client.
NFR 38 The Software (Refers to Software for Handheld Device/Mobile Data Terminal) should
be intuitive and should facilitate usage with minimal training.
provide comprehensive data back-up and restoration capability.
be device independent.
NFR 41 The System (Refers to the Core Application Software) should have an audit trail facility
maintained at the server end. Trails of users currently logged in and inactive users at a
time as well as user history should be maintained.
NFR 42 The System (Refers to the Core Application Software) should have a firewall, access
control system, password policies, audit trail etc. from the security point of view.
NFR 43 The Handheld Device/ Mobile Data Terminal should have GPRS/GSM based software
connected to the database server. The client should be provided with a facility to
search on the basis of Criminal Name, Nature of Offence, etc.
NFR 44 The Software (Refers to the Core Application Software) should also be able to
generate dynamic reports based on any of the fields as per the user's requirement as
well as standardized MIS Reports, Statistical reports.
NFR 45 The software (Refers to Software for Handheld Device/Mobile Data Terminal) should
be customized as per user requirement.
NFR 46 The System (Refers to the Core Application Software) should enable selecting options
using dropdown menu and the administrator should be able to modify the master
tables as and when required.
NFR 47 The System should allow upgradation of software versions (Refers to the Core
Application Software and Handheld Device Software) from time to time as per
available technology.
NFR 48 The Software (Refers to the Core Application Software and Handheld Device
Software) should provide menu based help to the user.

CCTNS TN RFP Vol I Police NCRB

Transféré par

Informations du document

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

CCTNS TN RFP Vol I Police NCRB

Transféré par

Droits d'auteur :

Formats disponibles

E-GOVERNANCE MISSION MODE PROJECT (MMP)

CRIME & CRIMINAL TRACKING NETWORK AND SYSTEMS

GOVERNMENT OF TAMIL NADU

6.4 Infrastructure at the District Training Centers ................................................... 70

6.16 Go-Live ............................................................................................................... 97

1. Request for Proposal Datasheet

1. RFP reference No and Date C.No.

3. Date of pre-bid conference 17th June 2011 – Time to be

5. Release of response to clarifications 21st June 2011

6. Last date (deadline) for receipt of 6th July 2011 - 3:00 PM

9. Contact Person for queries Additional Director General

2.1 Project Background

Availability of relevant and Timely information is of utmost necessity in conduct of business

Additional information can be found on NCRB website (http://ncrb.nic.in)

2.2 Background of Police Systems in India

2.2.1 Crime and Criminals Information System (CCIS)

2.2.2 Crime Analysis and Automated Record Update System (CAARUS)

data to Central server at SCRB at the end of a day.

CAARUS Stand-alone is built on client-server architecture on a Windows platform using

2.2.3 Common Integrated Police Application (CIPA)

CIPA is a stand-alone application developed to be installed in police stations and to support

data in ELCOT data Centre.

2.2.4 Crime and Criminal Tracking Network System (CCTNS)

2.3 CCTNS Implementation Framework

The implementation of CCTNS would be taking an “integrated service delivery” approach

2.3.1 Goals of this Request for Proposal (RFP)

3.1 Need for the Project

3.2 Vision and Objectives of Project

The broad objectives of the project are as follows:

3.3 Stakeholders of Project

 Citizens/ Citizens groups

preparation of regular and ad-hoc reports and station records management

4. State Police Department

4.1 Organization Structure

Enforcement, Training, Crime Bureau and Criminal Investigation Department (CBCID),

Functional Units of Tamil Nadu Police

DGP, Training DGP, TNUSRB DGP, Police Housing

Tamil Nadu Police: General Hierarchical Set-up

4.2 Existing Legacy Systems

4.3 Existing Data Center Infrastructure

 Physical Infrastructure for hosting the CCTNS Servers

4.4 Existing WAN Infrastructure

Existing WAN Infrastructure - Zonal Connectivity

Police Station Connectivity

Existing WAN Infrastructure – HQ, SCRB and Police Station connectivity

4.5 Existing Client Site Infrastructure

4.6 Existing Capacity Building Infrastructure (DTCs/ RTCs/ PTCs/ Police

4.7 Core Application Software (CAS)

The CCTNS application software can be conceptualized as comprising different services

4.8 CAS (Center)

Overview of Services for CAS (Center)

4.9 CAS (State)

It is envisioned that CAS (State), once operational, will significantly enhance

Services in CAS (State)

4.10 Development of CCTNS Core Application Software (CAS)

5. Role of NIC in supporting CAS

Each of these activities is detailed out below.

Application Management Services for CAS (State)

 Appropriate communication on change required has taken place.

Technical Program Management of Implementation of CAS (State)

 Preparation of “CAS Implementation toolkits” that comprehensively covers details on all

o Commissioning and Deployment of CAS (State)

6. Scope of the Project

6.1 Geographical Scope