Cctns Si RFP JH Vol I f1

Request for Proposal
Implementation of Crime and Criminal Tracking

Network and System in Jharkhand State
VOLUME–I: FUNCTIONAL AND TECHNICAL SPECIFICATIONS,

Version 2.0
DEPARTMENT OF POLICE,
GOVERNMENT OF JHARKHAND
Last date of Submission
12:00 Hrs, 11th June, 2011

RFP Volume-I for State System Integrator for Implementation of CCTNS in Jharkhand
Table of Contents
1 INTRODUCTION.....................................................................................................................................................10
1.1 PROJECT BACKGROUND ..........................................................................................................................10
1.2 BACKGROUND OF POLICE SYSTEMS IN INDIA...............................................................................11
1.2.1 CRIME AND CRIMINAL INFORMATION SYSTEM (CCIS) ...................................................11
1.2.2 COMMON INTEGRATED POLICE APPLICATION (CIPA) ....................................................12
1.3 CRIME AND CRIMINALS TRACKING NETWORK AND SYSTEMS (CCTNS) ..........................13
1.4 CCTNS IMPLEMENTATION FRAMEWORK .......................................................................................13
2 STRUCTURE OF RFP ............................................................................................................................................16
2.1 GOALS OF THIS RFP ...................................................................................................................................16
3 EXECUTIVE SUMMARY .......................................................................................................................................18
4 SCOPE OF WORK FOR IMPLEMENTING AGENCY ...................................................................................19
4.1 OVERVIEW OF SCOPE ...............................................................................................................................19
4.2 DETAILED SCOPE OF WORK ..................................................................................................................21
4.2.1 GEOGRAPHICAL SCOPE ..................................................................................................................21
4.2.2 FUNCTIONAL SCOPE ........................................................................................................................21
4.3 DETAILED SCOPE OF SERVICES DURING IMPLEMENTATION PHASE.................................24
4.3.1 PROJECT PLANNING AND MANAGEMENT .............................................................................25
4.3.2 CONFIGURATION, CUSTOMIZATION AND EXTENSION (NEW MODULES) OF CAS
(STATE) AND INTEGRATION WITH CAS (CENTRE) AND EXTERNAL AGENCIES .....................28
4.3.3 IT INFRASTRUCTURE AT THE DISTRICTS TRAINING CENTRES ..................................32
4.3.4 SITE PREPARATION AT POLICE STATIONS AND HIGHER OFFICES ............................32
4.3.5 INFRASTRUCTURE AT THE CLIENT SITE LOCATIONS .....................................................33
4.3.6 NETWORK CONNECTIVITY FOR POLICE LOCATIONS .......................................................37
4.3.7 INFRASTRUCTURE AT THE DATA CENTRE & DISASTER RECOVERY CENTRE ......39
4.3.8 DATA MIGRATION AND DATA DIGITIZATION......................................................................42
4.3.9 CHANGE MANAGEMENT ................................................................................................................46
4.3.10 OBTAINING ISO27001 CERTIFICATION FOR CCTNS SYSTEM .......................................47
4.3.11 HANDHOLDING SUPPORT .............................................................................................................47
4.3.12 REQUIREMENT ON ADHERENCE TO STANDARDS .............................................................47
4.3.13 3RD PARTY ACCEPTANCE TESTING, AUDIT AND CERTIFICATION ..........................48
4.4 SCOPE OF SERVICES DURING POST IMPLEMENTATION PHASE ...........................................51
4.5 ROLL OUT PLAN ..........................................................................................................................................59
Confidential Page 2
5 PROJECT CHARTER ..............................................................................................................................................66

5.1 VISION AND OBJECTIVES OF PROJECT ..............................................................................................66
5.1.1 VISION ....................................................................................................................................................66
5.1.2 NEED FOR THE PROJECT ...............................................................................................................66
5.1.3 OBJECTIVES OF THE PROJECT .....................................................................................................66
5.2 DESIRED OUTCOMES OF THE PROJECT ............................................................................................68
6 ROLE AND RESPONSIBILITY OF STAKEHOLDERS .................................................................................70
6.1 PRIMARY STAKEHOLDERS OF THE PROJECT ................................................................................70
6.2 OTHER STAKEHOLDERS OF THE PROJECT .....................................................................................70
6.3 ROLES AND RESPONSIBILITIES OF STAKEHOLDERS OF THE PROJECT.............................70
6.3.1 DEPARTMENT OF POLICE .............................................................................................................71
6.3.2 SOFTWARE DEVELOPMENT AGENCY (SDA) .........................................................................72
6.3.3 STATE PROJECT MANAGEMENT UNIT (SPMU)....................................................................73
6.3.4 SYSTEM INTEGRATOR (SI) ............................................................................................................75
6.4 PROJECT GOVERNANCE STRUCTURE ................................................................................................76
7 GEOGRAPHICAL COVERAGE ............................................................................................................................81
7.1 Organisation structure ..............................................................................................................................81
8 PROPOSED SOLUTION ........................................................................................................................................85
8.1 TO BE PROCESS FLOW ..............................................................................................................................86
8.1.1 CORE APPLICATION SOFTWARE ................................................................................................86
9 OVERALL ARCHITECTURE................................................................................................................................96
9.1 FUNCTIONAL REQUIREMENTS .............................................................................................................96
9.2 NON FUNCTIONAL REQUIREMENTS ............................................................................................... 125
10 CHANGE MANAGEMENT AND CAPACITY BUILDING .................................................................... 135
10.1 OBJECTIVE OF CHANGE MANAGEMENT........................................................................................ 135
10.2 SCOPE OF CHANGE MANAGEMENT ................................................................................................. 135
10.3 CAPACITY BUILDING .............................................................................................................................. 145
10.4 INFRASTRUCTURE AVAILBLE FOR CAPACITY BUILDING ..................................................... 145
10.5 OVERALL TRAINING PLAN .................................................................................................................. 146
11 ANNEXURE ...................................................................................................................................................... 151
11.1 Annexure 1 – Contact Details of Key Officials............................................................................... 151
11.2 Annexure 2 – List of all Police locations & Network Connectivity Requirement ........... 152
11.3 Annexure 3 – Technical Architecture and Standards ................................................................ 167
11.4 Annexure 4 - Implementation Plan................................................................................................... 181
11.5 Annexure 5 – Information on Existing Systems .......................................................................... 191
Confidential Page 3
11.6 Annexure 6 - Network Connectivity Details.................................................................................. 194

11.6.1 Connectivity Status at PHQ, Jharkhand ................................................................................. 194
11.6.2 Connectivity Status at Police Stations & Other Units ....................................................... 194
11.7 Annexure 7 - Jharkhand Police State Wide Area Network ...................................................... 196
11.8 Annexure 8 – Technical Specifications (Indicative)................................................................... 204
11.8.1 Desktop System ............................................................................................................................... 204
11.8.2 Technical Specifications 250GB External USB Hard disk............................................... 207
11.8.3 Technical Specifications Laser Jet Network Printer (Duplex) ..................................... 208
11.8.4 Technical Specifications Laser Jet Multifunction Printer (Print, Copy, Scan) ....... 210
11.8.5 TECHNICAL SPECIFICATIONS FOR ON-LINE UPS (2KVA) SINGLE PHASE INPUT &
SINGLE PHASE OUTPUT.................................................................................................................................. 213
11.8.6 TECHNICAL SPECIFICATIONS FOR DIESEL GENERATORS 5KVA.............................. 216
11.8.7 Technical Specifications 16 Port Unmanaged Switch...................................................... 221
11.8.8 Technical Specifications Finger Print Reader ..................................................................... 222
11.8.9 Technical Specifications Digital Camera ............................................................................... 223
11.8.10 Technical Specifications Electronic Pen ........................................................................... 225
11.8.11 Technical Specifications Computer Tables ..................................................................... 226
11.8.12 Technical Specifications Computer Chairs ...................................................................... 227
11.8.13 Technical Specifications Electrical Cabling ..................................................................... 228
11.8.14 SPECIFICATION FOR PIT EARTH ........................................................................................ 229
11.8.15 Technical Specifications Wall Mounted Network 9U Rack....................................... 232
11.8.16 Technical Specifications Cat-6 Patch Panel..................................................................... 232
11.8.17 Technical Specifications Information Outlet (Cat6-Single Port) ............................ 233
11.8.18 Technical Specifications CAT 6 Cable Lying ................................................................... 234
11.8.19 Technical Specifications CAT 6 Patch Cord (1 Meter / 2 Meters) ......................... 234
11.8.20 Technical Specification of Routers for Police Stations ............................................... 235
11.8.21 Video Conferencing Equipment for AMC ......................................................................... 239
11.8.22 Large Format Video Display for AMC ................................................................................ 242
11.8.23 Rack Servers for AMC............................................................................................................... 243
11.8.24 Technical Specification 24 Port managed L2 Switch for AMC................................. 243
11.8.25 Desktop Systems for AMC ...................................................................................................... 245
11.8.26 ON-LINE UPS (3KVA) SINGLE PHASE INPUT & SINGLE PHASE OUTPUT for AMC
246
11.8.27 Specifications of Ku band VSAT & the architecture ..................................................... 250
11.8.28 MPLS VPN Router Specification ........................................................................................... 255
Confidential Page 4
11.8.29 Technical Specification for Database Servers ................................................................ 261

11.8.30 Technical Specification for Application Servers ........................................................... 262
11.8.31 Technical Specification for Mail Servers .......................................................................... 264
11.8.32 Technical Specification for Infrastructure Servers ...................................................... 265
11.8.33 Technical Specification for Blade Enclosure .................................................................. 267
11.8.34 Technical Specification for SAN Storage (1 at DC, 1 at NR and 1 at DR) ............. 269
11.8.35 Technical Specification for SAN Switch (1 at DC, 1 at NR and 1 at DR) ............... 270
11.8.36 Technical Specification for Tape Library ......................................................................... 271
11.8.37 Technical Specification for Backup Software ................................................................. 272
11.8.38 TECHNICAL SPECIFICATIONS FOR ON-LINE MUDULAR UPS DATA CENTER (20
KW IN N+1 CONFIGURATION) ..................................................................................................................... 274
11.8.39 TECHNICAL SPECIFICATIONS FOR DIESEL GENERATORS 50KVA (3Phase)... 279
11.8.40 TECHNICAL SPECIFICATIONS CORE ROUTER AT DC ................................................ 284
11.8.41 Specification of Core Switch at Datacentre ..................................................................... 289
11.8.42 TECHNICAL SPECIFICATIONS SERVER FARM ACCESS SWITCH AT DC ............. 290
11.8.43 TECHNICAL SPECIFICATIONS INTERNET ROUTER.................................................... 294
11.8.44 TECHNICAL SPECIFICATIONS CORE ROUTER AT NR SITE ..................................... 297
11.8.45 TECHNICAL SPECIFICATIONS SERVER FARM ACCESS SWITCH AT NR ............. 302
11.8.46 TECHNICAL SPECIFICATIONS IP Based KVM Switch ................................................. 305
11.8.47 Technical Specification for Management Console........................................................ 307
11.8.48 Digitization Requirements ..................................................................................................... 307
11.8.49 Handholding and Technical support (including Helpdesk) Requirements ....... 310
11.8.50 Capacity Building Requirements ......................................................................................... 315
11.8.51 Data Centre Operational Manpower/Requirements .................................................. 317
11.8.52 Project Planning and Management Requirements ...................................................... 318
11.8.53 Certification Requirements ................................................................................................... 320
11.8.54 Technical Specification—5 KVA Stabilizer ...................................................................... 321
11.8.55 Technical Specification—42U Rack.................................................................................... 322
11.8.56 A Technical Specification—Intrusion Prevention System ........................................ 323
11.8.57 Technical Specification—Firewall ...................................................................................... 325
11.8.58 Technical Specification—Load Balancer.......................................................................... 332
11.8.59 Technical Specification—Antivirus Software ................................................................ 339
11.9 Annexure 9 - Post Implementation Support Services ............................................................... 342
11.10 Annexure 10 - SERVICE LEVELS ................................................................................................... 349
11.11 Annexure 11 – Technology Stacks for CAS (State) and CAS (Centre) ............................ 354
Confidential Page 5
11.12 Annexure 12 – Bills of Material (Department at its discretion may negotiate with SI
to alter/ substitute the quantity in the BOM proposed without having any impact in the
financials)................................................................................................................................................................... 360
11.13 Annexure 11 – The Registers and reports presently in Use within the Department
360
11.14 Formats of Registers and reports presently in Use within the Department (refer
Volume-1-A).............................................................................................................................................................. 362
List of Figures
FIGURE 1 - ORGANIZATION STRUCTURE JHARKHAND POLICE ....................................................................................... 82

FIGURE 2: NON-FIELD ORGANIZATION STRUCTURE JHARKHAND POLICETHE LIST OF 26 POLICE DISTRICTS IS AS FOLLOWS:
..................................................................................................................................................................... 83
FIGURE 3: CCTNS SOLUTION OVERVIEW................................................................................................................... 86
FIGURE 4: NETWORK CONNECTIVITY REQUIREMENTS............................................................................................... 152
FIGURE 5: SERVICE ORIENTED ARCHITECTURE......................................................................................................... 168
FIGURE 6: PORTAL ARCHITECTURE ......................................................................................................................... 169
FIGURE 7: PORTAL LIFE CYCLE MANAGEMENT ......................................................................................................... 170
FIGURE 8: PORTAL FRAMEWORK ............................................................................................................................ 171
FIGURE 9: LOGICAL DEPLOYMENT ARCHITECTURE .................................................................................................... 172
FIGURE 10: NETWORK ARCHITECTURE ................................................................................................................... 175
FIGURE 11: PROPOSED CCTNS WAN ..................................................................................................................... 177
FIGURE 12: DR CENTRE ARCHITECTURE ................................................................................................................. 179
FIGURE 13: DC /NDR/ DR CENTRE ARCHITECTURE ............................................................................................... 180
FIGURE 14 - JHARKHAND POLICE SWAN................................................................................................................. 196
List of Tables
TABLE 1: PHASE-I ROLLOUT PLAN............................................................................................................................ 60

TABLE 2: GOVERNANCE STRUCTURE ......................................................................................................................... 77
TABLE 3: COMPOSITION OF STATE APEX COMMITTEE ................................................................................................. 78
TABLE 4: COMPOSITION OF STATE EMPOWERED COMMITTEE...................................................................................... 79
TABLE 5: COMPOSITION OF STATE MISSION TEAM ..................................................................................................... 79
TABLE 6: COMPOSITION OF DISTRICT MISSION TEAM ................................................................................................. 80
TABLE 7: LIST OF POLICE LOCATIONS........................................................................................................................ 81
TABLE 8: CCTNS JHARKHAND APPLICATION MODULES .............................................................................................. 96
TABLE 9: FUNCTIONALITIES SPECIFICATIONS FOR STATE SPECIFIC CUSTOMIZATION REQUIREMENTS.............................. 99
TABLE 10: FUNCTIONAL REQUIREMENTS OF SP OFFICE MODULE .............................................................................. 112
TABLE 11: PROGRAM SPECIFIC TRAINEE ESTIMATES ................................................................................................. 144
TABLE 12: ESTIMATED TRAINING REQUIREMENTS ................................................................................................... 145
TABLE 13: INDICATIVE TRAINING CONTENT ............................................................................................................ 147
TABLE 14: POLICE STATION WISE CONNECTIVITY & ELECTRIC POWER AVAILABILITY STATUS ...................................... 153
TABLE 15: USER AND BANDWIDTH SIZING .............................................................................................................. 178
TABLE 16: DIGITIZED DATA UNDER CIPA ................................................................................................................ 183
TABLE 17: APPLICATION MODULES TO BE COVERED DURING PHASE-I ........................................................................ 183
Confidential Page 6
TABLE 18: TRAINING TO BE COVERED IN PHASE-I .................................................................................................... 184

TABLE 19: EXPECTED OUTCOMES DURING PHASE-I ................................................................................................... 184
TABLE 20: DISTRICT WISE POLICE STATION TO BE COVERED IN PHASE-II ................................................................... 185
TABLE 21: SERVICE COVERAGE DURING PHASE-II ..................................................................................................... 186
TABLE 22: SERVICE COVERAGE DURING PHASE-II ..................................................................................................... 186
TABLE 23: TRAINING PLANNED FOR PHASE-II .......................................................................................................... 187
TABLE 24: EXPECTED OUTCOMES DURING PHASE-II.................................................................................................. 187
TABLE 25: SERVICE COVERAGE PLANNED FOR PHASE-III .......................................................................................... 188
TABLE 26: APPLICATION MODULES TO BE COVERED DURING PHASE-III ...................................................................... 189
TABLE 27: TRAINING PLANNED FOR PHASE-III ........................................................................................................ 189
TABLE 28: EXPECTED OUTCOMES DURING PHASE-III ................................................................................................ 190
TABLE 29: LEGACY SYSTEMS/APPLICATIONS ........................................................................................................... 191
TABLE 30 - CONNECTIVITY STATUS AT PHQ ............................................................................................................ 194
TABLE 31 - CONNECTIVITY STATUS AT POLICE STATIONS & OTHER UNITS .................................................................. 194
TABLE 32: CURRENT HARDWARE INFRASTRUCTURE ASSESSMENT SUMMARY ............................................................. 197
TABLE 33: PHQ IT INFRASTRUCTURE ASSESSMENT SUMMARY ................................................................................. 197
TABLE 34: DISTRICT WISE IT INFRASTRUCTURE ASSESSMENT SUMMARY ................................................................... 199
TABLE 35: TRAINING CENTRE & CAPACITY ............................................................................................................. 202
TABLE 36: LIST OF VARIOUS REGISTERS AND FORMS OF THE DEPARTMENT ................................................................ 360
Confidential Page 7
List of Abbreviations
TERM DEFINITION
ADGP Additional Director General of Police
AIG Assistant Inspector General of Police
ASI Assistant Sub Inspector
ASP Assistant Superintendent of Police
CI Circle Inspector
CID Crime Investigation Department
CIPA Common Integrated Police Application
CRO Crime Record Office
CSP City Superintendent of Police
DC Deputy Commissioner
DCRB District Crime Records Bureau
DGP Director General of Police
DIG Deputy inspector General of Police
DSB District Special Branch
DSP Deputy Superintendent of Police
GRP Government Railway Police
IGP Inspector General of Police
JAP Jharkhand Armed Police
NCRB National Crime Records Bureau
NIC National Informatics Centre
PHQ Police Headquarter
PP Public Prosecutor
RI Reserve Inspector
RTO Regional Transport Office
Confidential Page 8
TERM DEFINITION
SB Special Branch
SCRB State Crime Records Bureau
SDA State Designated Agency
SDPO Sub Divisional Police Officer
OC Officer-In-Charge
SI Sub Inspector
SP Superintendent of Police
STF Special Task Force
SWAN State Wide Area Network
Confidential Page 9
1 INTRODUCTION
1.1 PROJECT BACKGROUND
Availability of relevant and timely information is of utmost importance 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 Information. Quick and timely information availability about different facets of Police
functions to the right functionaries can bring in 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.
Common Integrated Police Application (CIPA) started in the year 2004 after a detailed study
thereof by a Subgroup of domain and technical experts. The pilot project was launched in Delhi
in 2005. Computer hardware, software and technical assistance were provided to police
stations. 10% police stations in Jharkhand (38 Police Stations only) have been covered under
CIPA wherein, at present, FIRs are being registered digitally and some events relating to
investigations are also being captured. Over a period of time, at one level, it was felt that, at this
pace, it would take many years before all police stations could be covered and, at another level,
that a stand-alone system of this nature would have very limited utility. Keeping these 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.
CCTNS aims at creating a comprehensive and integrated system for enhancing the efficiency and
effectiveness of policing through adoption of principles of e-Governance and creation of a
nationwide networking infrastructure for evolution of IT-enabled-state-of-the-art tracking
system around ‘investigation of crime and detection of criminals’. It aims to create
infrastructure and mechanism to provide the basis for evolution of an IT enabled state-of-the-art
workflow (Processes) automation system in a planned manner from Police Station level
upwards and also provide public service delivery systems. It will not only automate police
functions at police station and higher levels but will also create facilities and mechanism to
provide public services like registration of online complaints, ascertaining the status of case
registered at the police station, verification of persons etc.
Confidential Page 10
CCTNS will cover all the Police Stations in the States, and also the Sub-Divisions (including
Circles under inspectors), District headquarters, Range headquarters, Zonal IG offices and State
headquarters. Necessary Hardware will be provided at all these locations including Data Centres
at State Headquarters. All these locations will be networked by providing appropriate high-
speed connectivity for data transfer and sharing of information amongst various stakeholders.
The Crime and Criminal Tracking Network and Systems (CCTNS) project is to be implemented in
a manner where the major role would lie with the State Governments in order to bring in the
requisite stakes, ownership and commitment, and only certain core components would be in the
hands of the Central Government, apart from the required review and monitoring of project
implementation on a continuing basis.
With the launching of CCTNS, the erstwhile Common Integrated Police Application (CIPA)
programme would be subsumed into it in a manner that the work already done there under is
not disrupted. So far, 2,760 police stations, out of a total of around 14,000 police stations across
the country, have been covered under the Scheme.
The broad objectives of the CCTNS project are streamlining investigation and prosecution
processes, strengthening of intelligence gathering machinery, improved public delivery system
and citizen-friendly interface, nationwide sharing of information across on crime and criminals
and improving efficiency and effectiveness of police functioning. It will also:
1. Facilitate collection, storage, retrieval, analysis, transfer and sharing of data and
information among Police Stations, District, State Headquarters and other
organization/agencies, including those at Government of India level.
2. Help in enabling and assisting the senior Police Officers in better management
of Police Force.
3. Help in Keeping track of the progress of the crime and criminal investigation
and prosecution Cases, including progress of cases in the court.
4. Help in reducing the manual and redundant record keeping.
Additional information can be found on NCRB website (http://ncrb.nic.in)
1.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 State-led
initiatives such as e-COPS (in Andhra Pradesh), Police IT (in Karnataka), Thana Tracking System
(in West Bengal), CAARUS (in Tamil Nadu) and HD IITS (in Gujarat). Presently automation in the
area of Civil Police is addressed mainly through the two GoI-led initiatives – CCIS and CIPA – and
in some states such as Andhra Pradesh, Karnataka and Gujarat, through State-led initiatives.
1.2.1 CRIME AND CRIMINAL 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 (SCRB) and District Crime Records Bureaus (DCRB) and to facilitate
statistical analysis of crime and criminals related information with the states and monitoring
agencies.
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).
1.2.2 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.
As per the guidelines by MHA CIPA was implemented in 2004 in old Ranchi district of Jharkhand
State. A total of 38 police stations were upgraded to the standard of CIPA in respective districts.
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 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 Linux platform using Java and Postgre SQL
database. 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.
1.3 CRIME AND CRIMINALS TRACKING NETWORK AND SYSTEMS (CCTNS)

The Crime and Criminal Tracking Network and Systems (CCTNS) is a Mission Mode Project
conceptualized and sponsored by the Ministry of Home Affairs (MHA) in detailed consultation
with all stakeholders and adopt the guidelines of the National E-governance Plan (NeGP).
The CCTNS project aims at creating a comprehensive and integrated system for enhancing the
efficiency and effectiveness of policing 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 the real time. This 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 will have citizen’s interface to provide basic services to citizens.
The project would facilitate collection, storage, retrieval, analysis, transfer and sharing of data
and information among police stations, district, state headquarters and other organization and
/or agencies, including those at Government of India level wherein thousands of police stations
in India are to be linked through a tracking network in a bid to boost connectivity between
stations and enhance crime-fighting capabilities.
1.4 CCTNS IMPLEMENTATION FRAMEWORK

CCTNS would be implemented in a way where the State will 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. However, the State would drive the
planning and implementation of the project at the State level.
The role of the Centre (MHA and NCRB) focuses primarily around planning, providing the core
application software (CAS) which is to be configured, customized, enhanced and deployed in
States, managing and monitoring the program at a higher level. States would drive the
implementation at the State level and would continue to own the system after deployment. 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. Accordingly Jharkhand will select one System Integrator (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 and associated services such as operation and maintenance,
Capacity Building and Handholding, etc.
2 STRUCTURE OF RFP
The content of this RFP has been documented as a set of three volumes as explained below:
Volume I: Functional and Technical Requirements
Volume I of RFP intends to bring out all the details with respect to solution and other
requirements that Department deems necessary to share with the potential bidders. The
information set out in this volume has been broadly categorized as the scope of work,
Functional, Technical, and Operational covering multiple aspects of the requirements.
Volume II: Commercial and Bidding Terms
Volume II of RFP purports to detail out all that may be needed by the potential bidders to
understand project implementation approach, commercial terms and bidding process details.
Volume III: Contractual and Legal specifications
Volume III of RFP is essentially devoted to explain the contractual terms that the Department
wishes to specify at this stage. It basically consists of a draft of Master Services Agreement
(MSA) that needs to be signed between the Department and the successful bidder (SI). This MSA
includes a separate schedule on Service Level Agreement (SLA).
This is the Volume I of the SI RFP that comprises Scope of work, Technical and Functional
Requirements for the implementation of CCTNS project.
2.1 GOALS OF THIS RFP

The primary goal of this RFP is solicit proposals from the interested bidders to be selected as the
System Integrator (SI) for the State through a competitive bidding process. This volume of RFP
intends to bring out all the details with respect to the 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 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.
The Department of Police, Jharkhand shall be the final authority with respect to qualifying a
bidder through this RFP. The decision with regard to the choice of the System Integrator (SI)
who qualifies through this RFP shall be final and the department reserves the right to reject any
or all the bids without assigning any reason. The department 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 EXECUTIVE SUMMARY
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 enhancing outcomes in the areas of Crime Investigation and Criminals Detection, in
information gathering, and its dissemination among various Police organizations and units
across the country, and in enhancing Citizen Services.
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.
Jharkhand Home Dept. through Jharkhand Police is one of the front runners to initiate CCTNS
implementation in the state. Jharkhand Police dept. will establish SPMU to provide the required
operational support during the implementation phases of CCTNS.
The purpose of this RFP is to identify and select the System Integrator who will undertake the
CCTNS Project which includes integration, configuration, customization and extension of CCTNS
Core Application Software, establishment of network connectivity, deployment of hardware, Site
preparation, data migration and digitization of historical data, Change management & Capacity
Building, Handholding support and Operation & maintenance for Police Stations, SDOPs and
other Higher offices to achieve the defined objectives of CCTNS project.
4 SCOPE OF WORK FOR IMPLEMENTING AGENCY
4.1 OVERVIEW OF SCOPE
Considering the wide geographical scope and operational complexity, scope of the project is to
Customize, Develop, Test, Deploy, Operate and Maintain the proposed Crime and Criminal
Tracking and Networking System (CCTNS) and the Jharkhand Police Department’s functional
areas in BMT (Build, Maintain & Transfer) Model.
The System Integrator is not just the supplier of Hardware and Software but will be the System
Integrator of all the Department Functional Areas as detailed below; integrated with CCTNS CAS
(Centre) & CAS (State) as a component to the department portal.
The following outlines the broad areas of scope of work for the System Integrator, and the later
sections highlight the detailed scope of work for IA in each of the following areas.
“As a broad scope the SI will perform the following primary tasks.
(i) Procurement, Installation & Commissioning of Hardware, System Software &
Networking Infrastructure at all Department office locations of the department;
(ii) System study, SRS on all additional functionalities of CAS (State) and State Specific
Application as identified in the detailed Scope of Work;
(iii) Application Development of the all additional functionalities of CAS (State) as identified
and integration with CAS (State), existing department Website and other web services
with Role Based Access Control;
(iv) Customized Application software development and Application deployment at
Jharkhand Police Data Centre, DRC, PHQ, and all the Police Locations as specified under
detailed Scope of Work;
(v) Operation & Maintenance support to existing application post integration of the
Department, Department Website, Web applications, as detailed given in Annexure of
RFP Vol-I;
(vi) Data Digitization, Migration of past 10 year’s legacy data of all Police locations, PHQ and
data consolidation at Central Data Centre for Dash Board view;
(vii) Setup of Data Centre, Near Disaster Recovery and Disaster Recovery Centre at a location
identified by the Department, presently; it is planned to be provisioned at Jharkhand
Police Data Centre and DRC at NICSI data Centre, New Delhi;
(viii) Application Integration with any other department specific services;
(ix) Help Desk provisioning by providing a Helpline/ Call Centre function centrally in 3 shifts
(x) Training, Capacity Building & Change Management required for the project, covering
Jharkhand Police Department and all the stake holders involved in CCTNS Project;
(xi) Operation & Maintenance of the Overall System Solution (Hardware, System Software,
Application Software and other Infrastructure) for 5 Years from completion of Phase-
III*;
(xii) Provisioning of Application Software, for integration of any new Police location with the
CCTNS System during Operation and Maintenance Phase;
(xiii) Provisioning of Application Software, Hardware, networking etc. for integration of any
Police Location, already within the project being relocated during Operation and
Maintenance Phase;
(xiv) Obtaining ISO (27001, 20000) certifications for the CCTNS system
(xv) Compliance with the SLAs as defined in Schedule of MSA.
(xvi) The SI shall implement the CCTNS system and then run it successfully for a period of six
(6) months (Pilot Phase) in order to be eligible for grant of the requisite certification in
terms of the Agreement.
(xvii) A detailed description of the scope of work is given in Volume I of the RFP. The time
frame, within which the various activities and tasks relating to the scope of work have to
be executed, is given in Schedule of the MSA in RFP Vol-III. The IA shall strictly adhere to
the schedule for implementation of the Project”
*Phased Implementation Approach:

Phase-I:
• The system will be Piloted covering Police Data Centre, DRC, Police Head Quarter, all
higher offices (Range/Zone/SP/SDPO/Circles)all the Police Stations of Districts Ranchi
and Khunti and 1 Police Station at rest of the 24 Police districts engaged in Policing with
available modules of CCTNS CAS (State)
• This phase will also cover customisation, additional functionality and state specific
Application deployment at above mentioned geographic location with 6 months.
• In this phase, network connectivity as applicable, state-wide data digitization activity
and capacity building will have to be carried out.
Go-Live: The system shall “go-Live” with successful completion of Phase-I. Envisaged timeline for
completion of Phase-I is 6 months.
Phase-II:
• Deployment of CCTNS application with Phase-I modules and additional modules
as made available by SDA at all police location of the State.
• Deferred state-specific application development (duly approved) and leftover
data digitization if any.
• Capacity building as per Phase-II plan.
• Network Connectivity, as applicable
• Envisaged timeline for completion of Phase-II is 3 months
Phase-III: All police locations in the State would have been covered for the installation and
commissioning of hardware, connectivity and other infrastructure by the end of Phase-II. CCTNS
Phase-III is planned around the release of subsequent versions of CAS and the enhancements
initiated at the central level within 6 months from “Go-Live”. Envisaged timeline for completion
of Phase-II is 3 months.
Envisaged timeline for completion of first three phases as listed above is 1 year. O&M phase
shall commence only after successful completion of Phase-III as listed above.
4.2 DETAILED SCOPE OF WORK

The SI shall be responsible for meeting of all the functional and non-functional requirements as
listed in the RFP Vol- I. The detailed scope of work is as given below:
4.2.1 GEOGRAPHICAL SCOPE

CCTNS will cover all the Police locations in the Jharkhand State including State Police Head
Quarters, Zone IG offices, Range headquarters, and District headquarters, Sub-Divisions Offices,
District Police Stations, District Special Branches, Special Intelligence Branches, District Crime
Branches and Training Centres.
The list of all Police locations and details of these police locations is attached as an annexure to
this document. The annexure also includes the list of police locations where power
availability/connectivity is difficult.
Following table lists an outline of Geographical scope to be covered under CCTNS project.
Sl. Offices No.
1 Number of Police Stations 478
2 Number of SDPO/Circles 132
3 Number of Districts 26
4 Number of Ranges 7
5 Number of Zones 4
7 No. of Control Room 28
8 No. of Jails 26
9 No. of Forensic labs 1
10 No. of Finger Print Bureau 1
11 PHQ 1
Total Number of Police locations 704
Note: SI will have an access to 24 District Training Centre, 5 Police Training Centres and 1
SCRB training centre for capacity building activities.
4.2.2 FUNCTIONAL SCOPE

The functional scope of the project addresses the key functional areas of the Department of
Police. The SI is required to study the key process requirements, the functional requirements
and develop the required solution w.r.t the functional requirements. SI would configure and
customize CAS-Centre, CAS-State specific to the Jharkhand State and provide required interfaces
that need to be developed on existing legacy systems to be interfaced with CAS and develop any
additional CAS-State Extension modules. Additionally SI should provide solution for integration
requirements of the CAS with other MMP applications and external interfaces such as CSC, Jail,
Court, e-kosh, state portal etc. if any. The following table lists down the Applications/services
that would be part of CCTNS Jharkhand.
Sl. Module Name Application /Service Type of Additional

Services/ functionalities for
Application CAS State
(Yes/No/NA)
1. Registration Complaint and FIR CAS-State Yes

Module Management Service
2. Investigation Investigation CAS-State Yes

Unclaimed/Abandon CAS-State No
Property Register Service
Crime Investigation CAS-State No

Reports
3. Prosecution Custody, Trial & CAS-State Yes

Module Prosecution, Court and
Jail Interface &
Prosecution Management
Services
4. Search Module Crime & Criminal Records CAS-State Yes

and Query Management
Service
5. Configuration State CAS Administration CAS-State Yes

Module and Configuration
Management Service
6. Citizen Citizen Portal Service CAS-State No

Interface
Portal Employee Portal Service CAS-State *SRS to be carried
Extension out by System
Integrator
7. Traffic Module Challan Management CAS-State *SRS to be carried

Traffic Management Integrator
Reports and MIS

(Yes/No/NA)
8. Crime PCR Call Interface and CAS-State Yes

Prevention Management Service
Duty Allocation, CAS-State *SRS to be carried

Nakabandi, Patrolling, Extension out by System
VIP Security/Prisoner Integrator
Petition Management CAS-State Yes

Service
e-Mail/Message CAS-State No
Notification of Alerts, CAS–State Yes

Important Events,
Reminders and Activity
Calendar or Tasks Service
9. Analysis, Periodic, Crime and Law CAS–State Yes

Business & Order Reports and
Intelligence & Review Dashboard
MIS Module Service
10. Data Transfer State SCRB-NCRB Data CAS–State No

Module Transfer and
Management Service
11. User User help and Assistance CAS–State No

Assistance Service
Module
User feedback tracking CAS–State No
and resolution Service
12. Security User Access and CAS–State No

Module Authorization
Management Service
Activity Log Tracking and CAS–State No

Audit Services
13. Naxal CAS-State *SRS to be carried

Maintain database of
Information Extension out by System
Naxal
System Integrator
Updating on Naxal
activities in the state

(Yes/No/NA)
Sharing of data among

the Naxal-affected states
14. SP office CAS-State *SRS to be carried
HRM systems including
module Extension out by System
force statement, force
Integrator
return, command and
duty distribution,
inventory management,
fleet management,
workflow, accounts
management, file tracking
etc.
15. Crime Records CAS-State *SRS to be carried
All crime records
Module Extension out by System
including CD Part-I, II, III,
Integrator
and all connected
registers
* Functional Requirements specified for reference detailed under Functional

Requirement Specification of this volume.
4.3 DETAILED SCOPE OF SERVICES DURING IMPLEMENTATION PHASE

The scope of the “bundled services” to be offered by the SI as detailed under Scope of Work
includes the following:
• Project planning and management.

• Configuration, Customization and Extension (development of New Modules) of CAS
(State) and Integration with CAS (Centre) and External Agencies. CAS (State) will be
developed in two distinct technology stacks by the SDA at the Centre. The SI is expected
to bid with one of the technology stacks 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, Circle Inspector Office,
Range offices, Zones, SCRB, SDPOs, District HQ and State HQ), Training Centres and Data
Centre.
• IT Infrastructure procurement/ deployment/ maintenance at the Client site locations
(Police stations, Circle offices, Range offices, Zones, SCRB, SDPOs, District HQ and State
HQ).
• Provisioning of Network connectivity with the help of Network Service Provider
(engaged centrally by MHA/NCRB) and by SI where ever applicable.
• IT infrastructure procurement/ deployment/ maintenance at the Data Centre, Near

Disaster Recovery and Disaster Recovery Centre including the necessary hardware,
software and other networking components.
• Data migration and Digitization of Historical Data of last 10 years.
• Migration of CIPA Police Stations / Higher Offices to CCTNS.
• Change Management.
• Capacity Building.
• Handholding Support.
• User acceptance testing for the application.
• Ensuring acceptance testing, audit and certification through 3rd party Agency like
STQC/CERT-IN.
In implementing the above, the SI shall strictly adhere to the standards set by the MHA, NCRB,
and State Administration.
For SI, the Intellectual Property Rights (IPR) for the project would be limited to the customized
code and the product license fee and its annual fee for maintenance, version upgrades etc.
should be paid by SI.
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.
4.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:
• Results accomplished during the period;
• Cumulative deviations to date from schedule of progress on milestones as

specified in this RFP and with the agreed and finalized Project Plan;
• Corrective actions to be taken to return to planned schedule of progress;
• Proposed revision to planned schedule provided such revision is necessitated by

reasons beyond the control of the SI;
• 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 the Administration of state of Jharkhand.
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 team in the State and
approved by the Empowered Committee on the advice of the 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 Empowered Committee will periodically review
the Traceability Matrix. Nodal Officer would provide the final approval on the advice of the State
Empowered Committee 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 the 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 Empowered
Committee would also approve any changes required to these documents during the course of
the project. State Administration will finally sign-off on the documents on the recommendation
of SPMU.
Project documents include but are not limited to the following:
Detailed Project Plan
Updated/vetted FRS
SRS document
HLD documents (including but not limited to):
• Application architecture documents
• ER diagrams and other data modelling documents
• Logical and physical database design
• Data dictionary and data definitions
• Application component design including component deployment views, control flows,

etc.
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
User Manuals
Issue Logs
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.
The SI will also be required to procure commission and maintain Project Management,
Configuration management and Issue tracker tools at the State Headquarters during the course
of project implementation. The requirements are listed below:
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 (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
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.
4.3.2 CONFIGURATION, CUSTOMIZATION AND EXTENSION (NEW MODULES) OF CAS

(STATE) AND INTEGRATION WITH CAS (CENTRE) AND EXTERNAL AGENCIES
System Study, Design, Application Development and Integration
The SI shall carry out a detailed systems study to refine the Functional Requirements
Specifications provided in this volume of the RFP and formulate the System Requirements
Specifications (SRS) incorporating the functional specifications and standards provided by the
NCRB and the state-specific requirements. The SI shall also study CAS-State and CAS-Centre
being developed at NCRB and / or already running application in the State during the system
study phase. The study should also include different integration points of CAS state with
external agencies as per state requirement. 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, customization
and extension as per the requirement of the State. The SI would also prepare a change/reference
document based on changes or deviations from the base version of the CAS (State) with
appropriate references to all the artefacts /documents provided by NCRB / State.
The SI will also be responsible for:
1. Conducting System Study at the following locations on sample basis:

a. CIPA District
b. Circle Office
c. SP Office
d. SDPOs
e. IG Range Office
f. District Police Station
g. Other offices as mentioned RFP
2. Preparation of System Requirements Specifications (SRS) for additional functionalities
and different integration points with CAS (Centre) and External Agencies.
3. Preparation of CAS (State) implementation document with respect to Configuration,
Customization and extensions as per the requirement of the state.
4. Preparation of the Solution Design.
5. Solution Development and/or Customization 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 (Centre)
8. Preparation of Change/Reference document which will include all the changes or
deviations from the base version of the CAS (State)
9. 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 / SSDG (as and when
they happen) 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 Police Headquarters. The Test Plans also include planning for the
testing any integration with 3rd party COTS solutions, CAS (Centre), any external agencies. The
Test Plans should also specify any assistance required from Police Department and should be
followed upon by the SI. The SI should have the Test Plans reviewed and approved by the State
Empowered Committee /SPMU. The State will sign off on the test plans on the advice of State
Empowered Committee /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 (Centre) and external agencies upon the
approved SRS. The SI would prepare the HLD and have it reviewed and approved by the State
Empowered Committee /SPMU. The State will sign off on the HLD documents on the advice of
State Empowered Committee / 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
Empowered Committee /SPMU. State headquarters/Nodal officer will sign off on the LLD
documents upon the advice of State Empowered Committee /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
consider the local language support 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 Utility will migrate
the data from legacy based systems of the new modules to the CAS databases.
The user acceptance testing and fine-tuning of the application would be at the State
Headquarters premises. Also, the key senior resources would continue to be based onsite at the
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:
• Developing Local Language Interfaces and Support
• Configuring users
• Configuring Police Stations / Higher Offices
• Configuration of the UI as required by the State
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 the 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
(Centre) 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 (Centre) and with any external agencies should be thoroughly
tested by the SI.
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 Empowered Committee / 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 Empowered
Committee /SPMU for validation
Test Data Preparation
The SI shall prepare the required test data and get it vetted by State Empowered Committee
/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
(Centre) and external agencies.
User Acceptance Testing (UAT)
Test Plans for UAT would be prepared by the SI in collaboration with the State Empowered
Committee /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
Empowered Committee /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’s 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.
4.3.3 IT INFRASTRUCTURE AT THE DISTRICTS TRAINING CENTRES
There are 26 District Training Centres proposed under CCTNS; one each at District
Headquarters. The premises for the training centre have been identified by the Police
Department. The Department will provide the basic infrastructure like furniture, projectors,
computers, UPS required to run the training lab. SI is expected to provide the networking
components and connectivity to all District Training Centres through liasioning with the
centrally selected network service provider (BSNL).
Location details of all District Training Centres have been provided in Annexure of RFP Vol-I.
4.3.4 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:
Provision of Local area network (LAN cables, LAN ports)
Provision of computer furniture for Police Stations
Ensure adequate power points in adequate numbers with proper electric earthing.
Electric Wiring and providing power points for Computers, Printers and earthing from
main line and Generator line with accessories
In addition to the above supply and fixing of furniture of good quality like Computer
tables Computer Chairs (Cushion with arm), and other items shall be carried out to
ensure successful site preparation and installation of CCTNS at every access location.
As per the procurement process of the department, the SI shall need to supply all
materials to the Central Store located at Hotwar, Ranchi. Central Stores will issue
materials to all police locations, and the SI will have the responsibility of delivery,
installation, handover of the same to the Officer-In-Charge of that particular location.
Acceptance certificate and goods receipt note will need to be signed by the Officer-In-
Charge and countersigned by the concerned SP/superior officer as the case may be. The
acceptance certificate and goods receipt note will need to be submitted to the Central
Store by the SI in order to be eligible for payment.
Site Preparation shall cover all the activities necessary to enable the Department of Police to
setup the client side infrastructure and operate on CCTNS. Site Preparation will not include the
construction of buildings and major civil work.
Following is the total number of sites across the Jharkhand State which need site preparation.
Sl. Offices No.
5 Number of Zones 4
8 No. of Jails 26
11 PHQ 1
4.3.5 INFRASTRUCTURE AT THE CLIENT SITE LOCATIONS
The premises for offices will be provided by the Department at respective locations. The list of
Police Stations, SDOP, District offices, 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 in the State wide.
At each such location the following shall be carried out.
• Supply of the hardware, software, networking equipment, UPS, DG set to the location as
per the requirements
• Provisioning of redundant Network connectivity with the help of Network Service

Provider (engaged centrally by MHA/NCRB) and Provisioning of 400 VSAT connectivity
(demand based)
• Installation, Testing and Commissioning of UPS, DG-Set
• Physical Installation of Desktops, Printer, Scanner, /MFD, Switch- Connecting

peripherals, devices, Plugging in etc.
• Operating System Installation and Configuration.
• Installation of Antivirus and other support software if any.
• Configuring the security at the desktops, switch, routers and broadband connection/
networks.
• Network and browser Configuration.
• Test accessibility and functionality of CCTNS application from the desktops.
• Ensuring all the systems required are supplied, installed, configured, tested and
commissioned and declaring the site to be operational.
CCTNS application will be accessed and used at various access locations across the State like
Police Stations, Circle Office, Sub Division office, District Office and other higher offices.
The detailed list of ICT infrastructure at the proposed locations is as given below:
• PHQ – Ranchi
• Police Stations (including Control Room)
• SP’s Office / Other Office of Districts.
• SDOP’s / Circle/ other Offices.
• Range & Zone Offices
• Any other location as finalised from time to time during the project period
The list of ICT infrastructure requirements at the 478 Police Stations are:
Items No.
Client Systems (Desktops) 3
Laptop 1
HDD 250GB 1
Duplex Laser Printer 1
Multi-Function Laser (Print/Scan/Copy 1
UPS with 30 min backup 4
5KVA Generator Set (demand based) 1
Items No.
5KVA Voltage Stabiliser 1
16-Port Switch 1
Fingerprint Reader 1
Digital Camera 1
Electronic Pen 1
Detailed Specifications for above is given in Annexure. The list of ICT infrastructure
requirements at Higher Offices:
No of PC (Each MFP (Each Switch (Each UPS (Each

Sl Items
offices office) office) office) office)
1 PHQ 1 50 50 1 50
2 SCRB 1 4 1 1 4
Ranges/
3 11 4 1 1 4
Zones
SP
4 26 10 10 1 10
(Districts)
SDPO/
5 132 3 1 1 3
Circle
6 Others 56 1 1 1 1
Note: 56 other offices (PCR, CID, Jail, FSL, FPB)
Detailed Specifications for above is given in Annexure
SI shall refer the Bill of Material provided in this RFP. SI shall also assess the infrastructure
requirements (including Servers, Storage, Networking and Security) for operationalization of
the CCTNS system and to provide the functionalities to all the stakeholders, in full conformance
with the SLAs.
The bidders have to perform an independent assessment of the Infrastructure requirements for
CCTNS system and provide a detailed BOM with necessary supplementary items as per the BOM
provided in RFP Vol-I for the proposed infrastructure which will meet the SLA requirements as
specified in the RFP.
Important: All system software licenses would have to be taken in the name of the Department.
For any COTS (Commercially Available off the Shelf) products it is necessary for bidders to
obtain certification from the respective software vendors that proposed infrastructure is
sufficient to meet the performance and scalability requirements of the project. Addressing any
performance issues/degradation during O & M phase shall be the responsibility of SI at no
additional cost other than what is specified in the commercial proposal.
Procurement of IT Infrastructure
The SI shall procure & supply the IT Infrastructure for CCTNS system as proposed by them in
their technical proposal. The SI shall ensure that all the equipment supplied to the Department
is brand new and is free from any defect of any sort.
a. Bidder is expected to liaise with the network solution provider (BSNL) for provision of the
network connecting the above locations including DC / DRC for Intranet and Internet
services. This is in addition to all the Police locations.
b. It is required to connect all the above locations through MPLS based connectivity with the
Data Centre and Disaster Recovery sites. The Bidder is expected to size the network and
bandwidth requirement in line with assessment made available in this RFP with reasonable
spare capacity such that the network can serve additional applications in future and meet
the required SLAs as mentioned in the RFP.
c. Bidder shall ensure configuration of both MPLS and Internet connectivity through the
configuration of Quality of Service (QoS).
d. For DR connectivity, the Bidder shall provision MPLS connectivity at a point defined by
NICSI in Delhi through network service provider. The network service provider shall
provision for router or any other devices etc. required for the termination purposes at the
termination point.
e. Bidder need to provide the detailed items, specifications and qty. for all hardware including
network components in the BOM format provided.
IT Infrastructure Installation
The SI shall be responsible for operationalization of the CCTNS system from end to end, which
includes installation of IT Infrastructure and connecting the department database to all
Databases. The SI shall deploy the application software at the DC and shall ensure that the
application software services are made accessible to the CCTNS system users.
Connecting all locations on the CCTNS system network

The SI shall connect all the locations on CCTNS system network to the Data Centre in line with
the architecture and specifications and shall ensure that the access to Department portal is
provided to all the users.
Warranty
The SI shall provide comprehensive warranty & Maintenance support for a period of 5 years
from completion of Phase-III for all components supplied for the CCTNS system as per the
contract.
The SI shall replace any parts/components of the IT Infrastructure supplied for this project if
the components are defective and during the entire warranty period SI shall apply all the latest
patches/updates for all the software components after appropriate testing.
Documentation
The SI shall undertake preparation of documents including that of Infrastructure solution design
& architecture, configuration files of the Infrastructure, user manuals, Standard Operating
Procedures, Information Security Management procedures as per acceptable standards.
The SI shall take sign-off on the documents, including design documents, Standard Operating
Procedures, Security Policy & Procedures from Nodal Officer, CCTNS Project and shall make
necessary changes as recommended before submitting the final version of the documents.
4.3.6 NETWORK CONNECTIVITY FOR POLICE LOCATIONS
The SI shall use the last mile connectivity(provided by BSNL) and VSAT connectivity as offered
by him with Provision of Local area network (LAN cables, LAN ports, etc.) to the Police Stations,
Higher Offices, District Training Centres, PHQ, SCRB and other such places wherever required. SI
shall use any ISP/ SWAN for the connectivity redundancy as and when it is made operational / is
available. SI shall prepare comprehensive network architecture for connecting all the Police
Stations / Higher Offices to the Police DC and DRC (at NICSI) and also the connectivity from the
Police DC / DRC to the DC / DRC at the Centre hosting the CAS (Centre).
The connectivity between the Data Centre / Disaster Recovery Centre and the NCRB data centre
that hosts CAS (Centre) will be provided by the SI through Network Service Provider selected
centrally.
The VSAT connectivity proposed in the BOM is within the scope of SI to supplement overall
connectivity requirement of the department to ensure Project “Go-Live” within the timeline.
Networking Infrastructure (Indicative-to be provided by BSNL and SI)
The table below provides a detailed break up of Networking Connectivity & Infrastructure
required at Police Stations, Higher Office & other offices level.
The following items to be provided by centrally selected network service provider (BSNL)
Location-wise Connectivity of Network Infrastructure
Category-1 Category-2
Districts + DGP + CID/ Crime

Police Stations+ Circle Branch/Special Branches + Inter State
Connectivity +Sub Divisions+ Police Wireless Centre + PCR+Forensic
Ranges+ Zones Science Labs + Finger Print Bureau +
SCRB + Others
Broadband 495 62
VSAT 119
Leased Line
(including router, 7 27
modem & switch)
The following items to be provided by the SI:
VSAT to be 400
provisioned by SI
(Demand based)
Internet Router
(demand based) 400
MPLS VPN Router 3 nos.
MPLS VPN 4 Mbps

pooled bandwidth 3 years
MPLS VPN 4 Mbps

bandwidth from
police data centre to
VSAT service
provider hub
(committed
bandwidth 100% 3 years
MPLS VPN 4 Mbps

bandwidth from DR
site to VSAT service
provider hub
(committed
bandwidth 100% 3 years
Detailed Breakup of offices for network connectivity is provided in Annexure
4.3.7 INFRASTRUCTURE AT THE DATA CENTRE & DISASTER RECOVERY CENTRE
The SI shall provide system integration services to procure and commission the required
software and infrastructure at the State Police Data Centre and Disaster Recovery Centre, deploy
the configured and customized CAS (State), additional modules developed (for details on
specific / additional modules needed please refer the FRS requirements in Annexure), 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 Police Data Centre and at the Disaster Recovery Centre (DRC).
CAS (State) will be developed in two distinct technology stacks by the SDA at the Centre.
The SI is expected to bid with one of the technology stacks 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.
Department will provide the premises for Data Centre (DC) and NDR (Near Disaster Recovery
Centre) for hosting the solution. The premises for Disaster Recovery Centre (DRC) would be at
NICSI Data Centre in New Delhi.
The project will be hosted on Police Data Centre (DC), NDR and Disaster Recovery Centre where
necessary IT infrastructure will be provisioned by the SI.
SI is expected to prepare a proper plan including BOM and specifications for Hardware, Software
and necessary infrastructure (like Servers, Storage and Networking) for hosting the CCTNS
system at DC/NDR/DRC based on the assessment made and provided in this RFP.
Considering the future growth projection in CCTNS applications it is important that SI should
plan for the DC/NDR/DRC in a manner which will facilitate future expansions in the no. of users
(subject to limits defined beyond which a new location may have to be opened). Scalability for
each Stakeholder of CCTNS has to be planned.
1. SI will be allowed to provision it’s Manpower (Physical access) at DC/NDR/DRC for
installation, Configuration and maintenance of H/W & System Software including OS
during the project period, specifically during Development, testing, user Acceptance
testing stage. Such permission would be granted only with due authorisation of the
Department and/ or its SPMU. Additionally, VPN access for remote administration will
be provided for the project.
2. The following infrastructure at the DC/NDR/DR (NICSI) will be available to the SI:
a. RACK space
b. Power and Cooling
c. UPS, DG set power backup
d. Bandwidth and Connectivity
e. LAN
f. VPN
g. Firewall
h. Intrusion Protection System
i. Fire prevention
j. Physical security surveillance
k. Network Operation Centre
l. Common Data Centre facility Maintenance and Support
3. As a practice NICSI would not charge additionally VPN Connectivity for remote
administration for the DR site.
4. NICSI has Enterprise Management Solution (EMS) to maintain the service levels of its
Data Centre infrastructure and would provide all the necessary alerts to maintain the
Service Level in case of DR being functional. No penalty would be imposed on
Implementing Agency due to failure at NICSI end. SI should provision industry standard
EMS for the Application Performance monitoring ( based on real time end user
transactions & application performance measurement), Server & Database Performance
Monitoring (Availability & Performance) and for all the services of the project.
5. The project anticipates high volume of transactions and requires high availability of
bandwidth. Termination of MPLS cloud, including termination equipment as required (of
BSNL) that SI will get for the project will be done at Police Data Centre/ NDR/ NICSI Data
Centre. Jharkhand Police Department in consultation with SI will finalize the bandwidth
requirement at Police Data Centre & DR Centre at NICSI and network plan and decision
about location of its termination at NICNET will be taken after due approvals from NIC
Hq.
6. Following product and services shall be provided at DC and DR sites:
a. At State Police data Centre:
i. Hosting space for DC
ii. Shared firewall
iii. The power and network will be made available as part of the DC services
iv. The VPN access will be provided for remote administration of server
b. At DR Sites: NICSI data centre would provide Rack Space as per the rate
applicable for IT infrastructures that need to be provisioned by SI for the project.
For each Rack Space one LAN Switch and one SAN switch would be provided, as
a package”
i. Hosting space for DR
ii. Shared SAN storage and tape library back-up from NICSI as per the sizing
requirement by SI
iii. Core Switch, Load Balancer, SAN Switch
iv. Shared firewall and IPS

v. The power and network will be made available as part of the DR services
vi. The VPN access will be provided for remote administration of server
vii. 24x7 Help Desk support to the Jharkhand Police Department and its
representatives
viii. Connectivity between DC and DR In the event of any collocated hardware
related incident, the NICSI help desk will inform the personnel identified as
Administrator.
7. For DR connectivity, the Bidder shall ensure provisioning the termination of MPLS
connectivity at a point defined by NICSI in Delhi, through BSNL. Bidder shall make
provision for router or any other devices etc. required for the termination purposes at
the termination point.
8. Bidder is also expected to provision Multi-Protocol Label Switching (MPLS) based
back up connectivity to Data Centre on the similar lines as the primary connectivity for
all the Police Locations.
9. The bidder should make provision the storage infrastructure and accessories as
required for the Overall application of CCTNS at DC, NDR and DR site (to be placed at
NICSI data centres). The storage solution for CCTNS will constitute ZERO data loss
solution, through NDR with Recovery Point Objective (RPO) shall be limited to data
those are in-transit for replication at the time of occurrence of any disaster and
Recovery Time Objective (RTO) =< 2 hours for the critical application on storage.
10. For other non-critical applications and processes, the RTO shall not exceed 12 hours and
the RPO shall be limited to data those are in-transit for replication at the time of
occurrence of any disaster.
11. Bandwidth sizing requirement has been specified in this RFP. Bidder shall also suggest
the required bandwidth between the DC and DR centres to meet the RPO & RTO
specified as above, for both critical as well as non-critical Applications.
12. The mode of replication between the DC & NDR shall be synchronous and DC and DR site
shall be asynchronous SAN replication. It shall be the responsibility of SI.
13. Bidder shall include all the components (other than mentioned above) that are required
to make the solution complete.
14. Bidder shall design a suitable replication strategy and an effective model for replication
of the databases on the SAN storage.
Expectation from Bidder for DC and DR Sites
a. Provision of IT infrastructure as required but not limited to:
a) Servers (Web Server, Directory Server + Access Manager, Application Server/Portal,

Database Server, Mail Messaging Server etc.)
b) Enterprise Management System (EMS)
c) Antivirus Software
d) Capacity upgrade of SAN Storage at DC
e) SAN Switches
f) Load Balancer
g) Intrusion Protection System
h) Tape Library
i) All necessary software components including but not limited to Operating System,
Backup Software, and SAN Storage Management Software
b. The installation, configuration and maintenance of system software’s and application will be
the responsibility of the Bidder.
c. The maintenance of Bidder’s / Purchaser’s hardware collocated at DC & DR at NICSI will

remain Bidder’s responsibility.
d. SI needs to get security audit of the Application before moving the application to production
environment. The application can be audited by the list of companies for the said purpose at
CERT-in website with prior approval from Jharkhand Police Department.
e. SI needs to ensure OS hardening, Vulnerability Assessment and Penetration Testing prior to

provisioning the same at DC/DR.
SI shall develop / procure and deploy an 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, Directory Server, Database
Server, Mail Messaging Server and Networking components are provided in Annexure.
4.3.8 DATA MIGRATION AND DATA DIGITIZATION
Migration of 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
Department of Police, Jharkhand. Though Department 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 Department or any appointed agency, during Data
Quality Assessment and Review, in the data digitized/ migrated by SI, shall be addressed by SI at
no additional cost to Department. So far as the legacy data is concerned, they are either available
as structured data in the IT systems that are currently used by CIPA Districts or CCIS District
Headquarters for related work or in the form of paper documents (Cases Documents and Police
Station Registers).
Data Migration Requirements
• 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 Project Director
• Carry out the migration of legacy electronic data. In case electronic data is found to be
unviable for migration, it will be required to create digitized data from manual records.
• Carry out the digitization of the data available in the existing registers, reports, case files,
(Physical Copies)
• Scan images and pictures within the case file in colour and store them in the digital
format
• 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.
• Incorporate corrections as proposed
• Get final sign off from State Nodal Officer for migrated / digitized data
• At the end of migration, all the data for old cases and registers must be available in the
new system
Scope of Data digitization and Data migration
The Data for last 10 years would be Digitized/ Migrated to the new CCTNS application.
Following data represents the last 10 years historical data would be digitized/ Migrated to the
new CCTNS application , that include crime (case/incident) data, criminals’ data, the data from
the police stations records rooms (form police registers).
Records for Digitization

Base
S No Record Type
Year
Records for Data Entry (Cases)
1. FIR 2000 299,156
2. Charge sheet 2000 299,156
3. Seizure Memo 2000 299,156
4. Conviction Memo 2000 194,452
5. Arrest Memo 2000 897,468

Base
S No Record Type
Year
Records for Data Entry (Cases)
6. Final Report 2000 194,452
7. Wanted/ Missing- 2000

Person/Property 89,747
Total 2,273,587
Data Migration of records
A one-time effort to migrate the CCIS & CIPA data of last ten years across the police stations into
the system is required. Currently the data digitization process is in its infancy stage and
following table provides the indicative estimate of number of records to be migrated from CCIS
& CIPA out of total number of records. The following records are considered but not limited to
as a single ‘CASE’.
Data Migration
Sl. CIPA
Registers/Form Name Number of Records (from Any other
2006)
1 FIR 19,000 NA
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.
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:
Analyse 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
Write a specification to create, transfer and migrate the data set
Document all exceptions, complex scenarios of the data
This phase will generate the specification for Data Take–On routines
Transformation
Transformation phase can be commenced after integration testing phase. It will entail the
following steps:
Identify the fields, columns to be added/deleted from the existing system
Identify the default values to be populated for all ‘not null’ columns
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
Develop test programs to check the migrated data from old database to the new
database
Test the migration programs using the snapshot of the production data
Tune the migration programs & iterate the Test cycle
Validate migrated data using the application by running all the test cases
Test the success of the data take-on by doing system test
Data Take-on
Take–On phase will be initiated when the proposed solution is ready to be deployed. It will
entail the following steps:
Schedule data transfer of the computerized data that has been newly created by the data
entry operators based on the hard copy records.
Schedule data transfer of the existing digital data in the proposed new format
Migrate the data from an old system (legacy) to the envisaged database
Test on the staging servers after the data take-on with testing routines
Migrate from staging servers to production servers
Deploy and rollout the system as per the project plan
Additional Guidelines for Data Migration
SI shall migrate/convert/digitize the data at the implementation sites of Department.
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.
SI shall incorporate all comments and suggestions of Department in the Data Migration
Strategy and process documents before obtaining sign–off from Department.
SI shall perform mock data migration tests to validate the conversion programs.
SI shall ensure complete data cleaning and validation for all data migrated from the
legacy systems to the new application.
SI shall validate the data before uploading the same to the production environment.
SI shall generate appropriate control reports before and after migration to ensure
accuracy and completeness of the data.
SI shall convey to Department 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.
In the event Department is unable to obtain all the mandatory fields as conveyed by SI,
SI shall suggest the most suitable workaround to Department. SI shall document the
suggested workaround and sign-off will be obtained from Department for the suggested
workaround.
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 Department in
non – electronic format.
SI shall conduct the acceptance testing and verify the completeness and accuracy of the
data migrated from the legacy systems to the proposed solution.
Department may, at its will, verify the test results provided by SI.
4.3.9 CHANGE MANAGEMENT
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 initiative, to be designed & implemented by SI, shall focus on addressing
key aspects of Project including building awareness in Police personnel on benefits of new
system, changes (if any) to their current roles & responsibilities, addressing the employee’s
concerns & apprehensions w.r.t. implementation of new system and benefits that are planned
for the employees.
It is required that if SI doesn’t operate in the Change Management, Communication and Training
domain then he collaborates with/ hires services of a specialist agency who will be responsible
for complete Change Management, Awareness and Communication implementation and
monitoring, on the lines suggested below:
The State Nodal Agency shall form various stakeholder groups to address the Change
Management Initiative. Stakeholders are all those who need to be considered in achieving
project goals and whose participation and support are crucial to its success. A key individual
stakeholder or stakeholder group is a person or group of people with significant involvement
and/or interest in the success of the project.
Stakeholder analysis identifies all primary and secondary stakeholders who have an interest in
the issues with which the CCTNS project is concerned. The stakeholder groups will be the set of
core users (Change Agents) who will directly participate in the awareness and communication
initiatives, workshops, and provide feedback to the District Mission Teams and State
Empowered Committee.
Details on Change management has been provided in RFP Vol-I.
4.3.10 OBTAINING ISO27001 CERTIFICATION FOR CCTNS SYSTEM

SI is required to obtain ‘ISO27001’ and ‘ISO20000’ certifications for the CCTNS system by the
end of first six months of O & M phase. SI shall include all the efforts and cost required to obtain
the above certifications in the commercial proposal submitted by them in response to this RFP.
4.3.11 HANDHOLDING SUPPORT
The System Integrator will provide a maximum of 240 qualified and trained persons for the
entire project period who shall be utilized to handhold the staff in the police station / higher
office and ensure that the staffs in that police station / higher offices are able to use CCTNS on
their own by the end of the handholding period. Handholding support would be required only
after the successful commissioning of Core application and the necessary infrastructure and
completion of capacity building and change management initiatives in respective police stations
/ Higher Offices.
The SI is required to submit manpower deployment plan for handholding support.
Item No of Police Locations Period
Full project
period,
710 estimated
Handholding man months
Support* 5730
*Resources provided must be DC/ PGDCA qualified and should undergo 2 weeks training on
computer hardware and networking before reporting at Police Stations/higher offices.
4.3.12 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.
Particulars Required Standards to be adhered to

Portal development W3C specifications
Information access/transfer protocols SOAP, HTTP/HTTPS
Interoperability Web Services, Open standards
Photograph JPEG (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:200 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 compliant
Management
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.
4.3.13 3RD PARTY 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. Infrastructure Compliance Review
3. Availability of Services in the defined locations
4. Performance and Scalability
5. Security / Digital Signatures
6. Manageability and Interoperability
7. SLA Reporting System
8. Project Documentation
9. Data Quality Review
As part of Acceptance testing, audit and certification, performed through a designated agency,
i.e.; STQC/ CERT-IN, department 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 the department, one for audit & certification of security and control aspect of the system and
the other for audit & certification of overall Application software.
Department 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 the department, 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 w.r.t. the
functional requirements shall be performed by both designated agency STQC/CERT-IN (external
audit) as well as the select internal department users (i.e. User Acceptance Testing).
2. Infrastructure Compliance Review
Designated third party agency 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.
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, work-
flow 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) deployed 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 design, implement/customize the Enterprise Management System (EMS) 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 pay-out 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.
4.4 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. SI shall develop / procure and deploy an EMS tool that
monitors / manages the entire enterprise wide application, infrastructure and network related
components. The post implementation phase services shall include Application, IT
infrastructure and enabling infrastructure maintenance services/ facility management services
at all client locations for ensuring adherence of SLAs as per the guidelines mentioned in the SI
RFP template.
Infrastructure maintenance services for CIPA police stations shall also be part of the scope of
services during post-implementation phase.
SI shall provide the Operations and Maintenance Services for a period of 5 years following
completion of Phase-III in the State
The SI shall be required to provide operational and maintenance services for CCTNS system
including, all the software and hardware components. This section discusses the Operations &
Maintenance services to be provided by SI with respect to Application Software & supporting IT
Infrastructure Management.
Warranty Services
As part of the warranty services SI shall provide:
• SI shall provide a comprehensive warranty and on-site free service warranty for 5 years
from the date of completion of Phase-III
• SI shall obtain the five year product warranty and five year onsite free service warranty
on all licensed software, computer hardware and peripherals, networking equipment
and other equipment.
• 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.
• 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.
• 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.
• 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 equipment for inspection, delivery of equipment or for
commissioning of the systems or for acceptance tests / checks on per site basis, State
reserves the right to charge a penalty.
• 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.
• The SI shall as far as possible repair the equipment at site.
• 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.
• 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.
• The SI shall carry out Preventive Maintenance (PM), 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.
• SI shall monitor warranties to check adherence to preventive and repair maintenance

terms and conditions.
• The SI shall ensure that the warranty complies with the agreed Technical Standards,
Security Requirements, Operating Procedures, and Recovery Procedures.
• 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.
• 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).
• The SI shall develop and maintain an inventory database to include the registered
hardware warranties.
ATS (Annual Technical Support) Services

As part of ATS services SI shall provide:
• SI shall maintain data regarding entitlement for software upgrades, enhancements,

refreshes, replacements and maintenance.
• 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.
• SI should carry out any requisite adjustments / changes in the configuration for
implementing different versions of Application Software.
• 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.
• SI shall provide patches to the licensed software including the software, operating system,
databases and other applications.
• 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 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.
• 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 08:30 hours to 20:30 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 hours 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.
• Implementation of SLA Monitoring & Measurement System (SLA-MMS)
SI shall procure/ design and implement a SLA Monitoring & Measurement System tool (SLA-
MMS) to measure performance against each of the indicators listed under the service levels
specified in Schedule VIII of the MSA in Volume III of the RFP, in consultation with SPMU.
The SLA-MMS implemented by SI shall be reviewed by an independent organization for
certification.
SI shall ensure that proposed SLA-MMS addresses all the SLA measurement requirements and
enables calculation of eligible compensation to the SI on a quarterly basis, including penalties as
specified in the SLA.
SI shall design the CCTNS system to provide an independent and real-time access to the SLA-
MMS to the SPMU established by the Department.
In addition, SI shall send a weekly log of the output of the SLA-MMS to the SPMU.
Operations & Maintenance of Application Software
Maintenance includes, but is not limited to production monitoring, troubleshooting &
addressing the functionality, availability & performance issues and implementing the system
change requests.
The SI shall keep the application software in good working order; meeting the requirements
defined by the Department, perform changes and upgrades to applications as requested by the
Department, within the overall scope of the quality and quantity of functionalities to be
delivered under this RFP.
As part of this support, SI shall define and implement the Information Systems Security Policy
(ISSP) in consultation with the Department/SPMU.
Based on the ISSP, SI is also required to develop detailed Standard Operating Procedures, in
compliance with ISO 27001, for managing the security of the CCTNS System.
The following is the broad scope for maintenance and support functions with regard to the
software:
i. Compliance to the Functional Requirements specified in Volume I of the RFP
ii. Compliance to Service Levels specified in Schedule VIII of the MSA in Volume III of the
RFP.
The SI shall ensure compliance to uptime and performance requirements of CCTNS system as
indicated in the SLA in RFP Vol-III and any updates/major changes to the software shall be
accordingly planned by SI for ensuring adherence to the SLA requirements.
iii. Application Software Maintenance
The SI shall rectify all the errors/bugs/gaps/ modification on account of rule/acts/policy
change of Government in the functionality offered by CCTNS system (vis-à-vis the FRS & SRS
signed off by Nodal Officer) at no additional cost during the operations & maintenance period.
For performing any functional changes to system, which are deviating from the signed-off
Functional Requirements/System Requirements, a separate Change Control Note (CCN) shall be
prepared by SI and shall be mutually agreed between SI and the Department. No additional cost
is permissible for implementation of such CCN during the project period unless otherwise
agreed upon.
iv. Problem identification and Resolution
Identification and resolution of application problems (e.g. system malfunctions, performance
problems and data corruption etc.) shall be part of SI’s responsibility. The SI shall also be
responsible to rectify the defects pointed out by the SPMU to be set up by the Department and
carry out the enhancements suggested by the SPMU, as a result of the Field Assessments carried
out by the SPMU, during the O&M period. NISG will take up the SPMU role for this project. This
shall be at no additional cost to the Department, in so far as the enhancements relate to items of
work falling within the purview of the defined Scope of Work (SOW) for SI. Items outside the
SOW shall be handled through the mechanism of Change Control, defined in the Volume III of
RFP.
v. Software Change & Version Control
All planned changes to application systems shall be coordinated within established Change
Control processes to ensure that:
a. Appropriate communication on change required has taken place
b. Proper approvals have been received
c. Schedules have been adjusted to minimize impact on the production environment
The SI shall define the Software Change Management & Version control process and obtain
approval for the same from the Department. For any changes to the software, SI has to prepare
detailed documentation including proposed changes, impact to the system in terms of functional
outcomes/additional features added to the system. SI is required to obtain approval from the
Department for all the proposed changes before implementation of the same into production
environment and such documentation is subject to review at the end of each quarter of
operations & maintenance support.
vi. Maintain configuration information
Maintain version control and configuration information for application software and any system
documentation
vii. Maintain System documentation
Maintain and update documentation of the software system. Ensure that:
a. Source code is documented
b. Functional specifications are documented
c. Application documentation is updated to reflect on-going maintenance and enhancements
including FRS and SRS
d. User & training manuals are updated to reflect on-going changes/enhancements
e. Standard practices are adopted and followed for version control and management.
viii. IT Infrastructure Maintenance & Operations
a. Installation & Configuration for SLA-MMS for monitoring and management of CCTNS
infrastructure installed at all the Department locations.
b. Overall monitoring and management of the systems implemented for CCTNS system in the
data Centre, which includes administration of Data Centre Infrastructure
(Web/application servers, database server, and storage), Network and all other services
ancillary to these facilities to ensure performance and availability requirements of the
Project.
c. Ensuring compliance to the uptime and performance requirements, including data backup
& business continuity, for CCTNS system as indicated in the RFP.
d. Implementation of a comprehensive security policy conforming to ISO27001.
e. Perform the patch management, testing and installation of software updates issued by the
OEM/vendors from time to time. These patches/updates before being applied on the live
infrastructure of the data Centre shall be adequately tested. Any downtime caused due to
updates & patches shall be to the account of the SI and it shall not be considered as ‘Agreed
Service Down-Time’.
f. Ensure overall security of the solution including installation and management of Antivirus
solution for protection of all the servers and systems implemented for the project,
application of updates/patches etc. The antivirus patches have to be updated and applied
from time to time, after appropriate testing of the patches in the staging area.
g. Develop the Standard Operating Procedures (SOPs), in accordance with the ITIL/ISO
27001 standards, for CCTNS Infrastructure management. These SOPs shall cover all the
aspects including Infrastructure installation, monitoring, management, data backup &
restoration, security policy, business continuity & disaster recovery, operational
procedures. The SI shall obtain sign-offs on the SOPs from Department and shall make
necessary changes, as and when required, to the fullest satisfaction of Department.
h. Preventive maintenance, carrying out the necessary repairs and replacement of parts
wherever needed to keep the performance levels of the hardware and equipment in tune
with the requirements of the SLA. Such preventive maintenance shall not be attended
during working hours of CCTNS system, unless inevitable and approved by Department.
i. Reactive maintenance that is intended to troubleshoot the system with sufficient teams.
j. Continuous Performance tuning of the system as may be needed to comply with SLA
requirements.
k. Continuous monitoring & management of network during the working hours & restoration
of breakdown within prescribed time limits.
l. Monitoring security and intrusions into the system, which include taking necessary
preventive and corrective actions.
m. Monitor and record, server & network performance and take corrective actions to ensure
performance optimization on a daily basis.
n. Escalation and coordination with other vendors for problem resolution wherever
required.
o. System administration tasks such as managing access control system, creating & managing
users, taking backups etc.
p. Ensure that daily back-up copies of the data are created and maintained safely.
q. Produce and maintain system audit logs on the system for a period agreed with the
Department. On expiry of the period the audit logs should be archived and stored off-site.
r. Regular review the audit logs for relevant security lapses.
s. Review security advisories (such as bulletins available in the industry) on a regular basis
to determine vulnerabilities relevant to information assets and take necessary preventive
steps.
t. Supply consumables required for day-to-day operations of the data Centre, Disaster
Recovery site and other locations covered under the project. These consumables include,
but not limited to, storage media, Printer cartridges, CD/DVDs, data cables, UPS batteries
etc. During the warranty/operations/management period, SI shall not charge any
additional cost to the Department for replacement of these consumables. The cost quoted
for Operations & maintenance shall include the consumables cost also.
ix. Technical Support Services
As 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 Centre and Disaster Recovery Centre SI shall provide:
• 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 Centre and Disaster Recovery Centre.
The business hours in State will be from 08:30 hours to 20:30 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 Centre and Disaster Recovery Centre 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:
• System Administration, Maintenance & Management Services
• Application Monitoring Services
• Network Management Services
• Backend Services (Mail, messaging, etc.)
• Storage Administration and Management Services
• IT Security Administration Services and Services for ISO 27001 and ISO 20000
compliance
• Backup and Restore Services
As part of the Handholding services to provide Centralized Helpdesk and Support for
end users at each location SI shall provide:
• The service will be provided in the local language of the State.
• 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. Department 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 Centre, Disaster Recovery Centre, 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.
• SI shall provide a second level of support for application and technical support at
police stations, circle offices, sub-divisional offices, district headquarters, range
offices, Zonal offices, state police headquarters and other locations across the State
where the software, hardware, and other infrastructure will be rolled out.
• For all the services of State within the scope of this RFP, SI shall provide the
following integrated customer support and help.
• Establish 16X7 Help Desk facilities for reporting issues/ problems with the software,
hardware and other infrastructure.
• SI shall maintain and support to all client side infrastructure including hardware,
networking components, and other peripherals.
• 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.
• SI shall track and report observed Mean Time between Failures (MTBF) for
Hardware.
• SI shall provide functional support on the application components to the end users.
• SI shall also provide system administration, maintenance and management services,

LAN management services, and IT security administration services.
As part of the Handholding services to provide software maintenance and support

services SI shall provide:
• 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 offsite
maintenance and support services to State to all the designated locations. The
Maintenance and Support Services will cover, all product upgrades, modifications,
and enhancements.
• 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.
• Tuning of application, databases, third party software’s and any other components
provided as part of the solution to optimize the performance.
• The SI shall apply regular patches to the licensed software including the operating
system and databases as released by the OEMs.
• Software Distribution. SI shall formulate a distribution plan prior to rollout and

distribute/install the configured and tested software as per the plan.
• 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.
• 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:
• 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 centre in State.
• 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.
• Routine functional changes that include user and access management, creating new
report formats, and configuration of reports.
• 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.
• 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.
• The SI shall perform user ID and group management services.
• The SI shall maintain access controls to protect and limit access to the authorized
end users of the State.
The services shall include administrative support for user registration, creating and maintaining
user profiles, granting user access and authorization, providing on-going user password
support, announcing and providing networking services for users and providing administrative
support for print, file, directory and e-mail servers.
4.5 ROLL OUT PLAN
It is proposed to roll out CCTNS in three phases. Deployment of hardware, connectivity and
other infrastructure across all police stations, higher offices and other police units would take
place in the first two phases. CAS (Core Application Software) would be rolled out in three
phases. The core focus of each of the three phases is delineated below:
CCTNS Implementation Pilot Phase
Geographical Coverage
During the first phase of implementation, CCTNS would be rolled out in covering 1 Police district
– Old Ranchi (Presently Ranchi and Khunti district; amounting to approximately 10% of the total
police locations across the state), one Police Station of each of 24 Police districts and all higher
offices. The roll out would include installation and commissioning of hardware, connectivity,
other infrastructure and associated services (such as handholding). The choice of the districts
where the first phase would be rolled out is provided below.
Table 1: Phase-I Rollout Plan
Number
of
Sl. Districts in Phase I Rationale for choosing them
Police
Stations
- Large populated district

- IT savvy departments in these
districts
1 Ranchi 41 - Proximity to the headquarters
- CIPA District
- All these police stations were
covered under CIPA
2 Khunti 8 - Do -
3. 1 Police Station each of 24 Police districts 24 - Do -
Total 73
*Phased Implementation Approach:

Phase-I:
• The system will be Piloted covering Police Data Centre, DRC, Police Head Quarter, all
higher offices (Range/Zone/SP/SDPO/Circles)all the Police Stations of Districts Ranchi
and Khunti and 1 Police Station at rest of the 24 Police districts engaged in Policing with
available modules of CCTNS CAS (State)
• This phase will also cover customisation, additional functionality and state specific
Application deployment at above mentioned geographic location with 6 months.
• In this phase, network connectivity as applicable, state-wide data digitization activity
and capacity building will have to be carried out.
Go-Live: The system shall “go-Live” with successful completion of Phase-I. Envisaged timeline for
completion of Phase-I is 6 months.
Phase-II:
• Deployment of CCTNS application with Phase-I modules and additional modules
as made available by SDA at all police location of the State.

• Deferred state-specific application development (duly approved) and leftover
data digitization if any.
• Capacity building as per Phase-II plan.
• Network Connectivity, as applicable
• Envisaged timeline for completion of Phase-II is 3 months
Phase-III: All police locations in the State would have been covered for the installation and
commissioning of hardware, connectivity and other infrastructure by the end of Phase-II. CCTNS
Phase-III is planned around the release of subsequent versions of CAS and the enhancements
initiated at the central level within 6 months from “Go-Live”. Envisaged timeline for completion
of Phase-II is 3 months.
Envisaged timeline for completion of first three phases as listed above is 1 year. O&M phase
shall commence only after successful completion of Phase-III as listed above.
SI is required to adhere to the prescribed implementation and roll out plan (The plan may be
revised depending on the availability of the CAS (State) from NCRB). The broad level
implementation and roll out plan is shown below:
Detailed Project plan
Schedule
Sl. Phase Activity period in
Months
1 Phase Contract Finalization and Award 0
(Pre)
2 Phase-I Opening of Site Office for the Project 0
3 Phase-I Submission of Project Plan for approval 0
4 Phase-I Project Management Information System (PMIS) 0.5
5 Phase-I Implementation of Project Management, Configuration 1
management and Issue tracker tools
6 Phase-I Data Migration Strategy Document 1
7 Phase-I Procurement, deployment and commissioning of 2
required equipment at State Data Centre +DRC
8 Phase-I Procurement, installation and commissioning of 2
hardware (including PCs, peripherals, etc.),
communication infrastructure (routers, switches, VSAT
wherever applicable etc.) at police stations and higher
offices including site preparation (for Ranchi, Khunti
districts and 1 Police station at all other 24 Districts)
Schedule
Months
9 Phase-I Implementation of CCTNS Core Application Software 2
provided by NCRB on a pilot basis and review of Pilot
implementation by District Mission Team & Core Team
The SI shall configure CAS (State) to the requirements
of the State that include but not limited to:
• Developing Local Language Interfaces and Support
• Configuring users
• Configuring Police Stations / Higher Offices
• Configuration of the UI as required by the State
The collection and validation of the data required for
the configuration of the CAS (State) shall be the
responsibility of the SI.
10 Phase-I Commencement of Study of CAS (State) and for SRS on 2

Additional Functionality and State specific Application
11 Phase-I Data migration and Digitization of historical data for 2
Ranchi & Khunti Districts
12 Phase-I Submission of HLD for review and approval by 2
Department
13 Phase-I Submission of LLD for review and approval by 2
Department
14 Phase-I Capacity building for police personnel for Phase-I 3
15 Phase-I Need analysis and SRS for Customization of CCTNS 3
Core Application Software provided by NCRB.
16 Phase-I Submission of SRS on Additional Functionality and 3
State specific Application
17 Phase-I Sign-off on the documents, including design 3
documents, Standard Operating Procedures, Security
Policy & Procedures from Nodal Officer, CCTNS Project
and shall make necessary changes as recommended
before submitting the final version of the documents.
18 Phase-I Customization of CCTNS Core Application Software 4.5
provided by NCRB at pilot location for acceptance
19 Phase-I Development and deployment of additional 5
functionality that is scoped under CCTNS on a pilot
basis
20 Phase-I Preparation of CAS (State) implementation document 5
with respect to Configuration, Customization and
extensions as per the requirement of the state.
21 Phase-I Preparation of the Solution Design. 5
22 Phase-I Solution Development and/or Customization and/or 5
Configuration and/or Extension as required.
23 Phase-I Development of reports. 5
24 Phase-I Formulation of test plans and test cases for additional 5
functionalities and different integrations with external
agencies including CAS (Centre)
Schedule
Months
25 Phase-I Preparation of Change/Reference document which will 5
include all the changes or deviations from the base
version of the CAS (State)
26 Phase-I Testing of the configured solution (CAS) and additional 5
functionalities.
27 Phase-I Provisioning and maintenance of the required software 5
and the infrastructure for systems testing, functional
testing and User Acceptance Testing
28 Phase-I Security audit of the Application before moving the 6
application to production environment. (The
application can be audited by the list of companies for
the said purpose at CERT-in website with prior
approval from Jharkhand Police Department)
29 Phase-I OS hardening , Vulnerability Assessment and 6
Penetration Testing prior to provisioning the same at
DR.
30 Phase-I Deployment of Handholding Support Manpower for 6
applicable police locations
31 Phase-I Third Party Audit & Certification to ensure that the 6
system meets requirements, standards, and
specifications as set out in this RFP and as needed to
achieve the desired outcomes
32 Phase-I Deployment of senior resources including the project
manager in State HQ
33 Phase-II Data migration and Digitization of historical data for all 6
other Districts
34 Phase-II Procurement, installation and commissioning of 8
hardware (including PCs, peripherals, etc.),
communication infrastructure (routers, switches,
VSATs wherever applicable etc.) at police stations and
higher offices including site preparation (for all
districts)
35 Phase-II Development and deployment of additional 8
functionality that is scoped under CCTNS to be
completed in Phase-II
36 Phase-II Capacity building for police personnel for Phase-II 9
37 Phase-III Development of additional functionality that is scoped 11
under CCTNS to be completed in Phase-III
38 Phase-III Deployment of full version of CAS scoped under CCTNS 12
post UAT
39 Phase-III Capacity building for police personnel for Phase-III 12
40 Post SI is required to obtain the ISO 27001 certification for 18
Phases the CCTNS system by the end of first six months of O &
O&M M phase.
Schedule
Months
41 Post Comprehensive warranty and on-site free service 5 Years post
Phases warranty for 5 years from the date of completion of completion of
O&M Phase-III. Phase-III
42 Post SI to carry out rectification of the defects pointed out
Phases and / or enhancements suggested by the SPMU during
O&M the O&M period.
43 Post Issue of Change Control note (CCN) for enhancement
Phases suggested by SPMU falling beyond the agreed Scope of
O&M Work to commence at the start of O& M Phase
44 Post To prepare detailed documentation including proposed
Phases changes, impact to the system in terms of functional
O&M outcomes/additional features added to the system at
the end of each Quarter of O& M Phase.
O&M the O&M period.
48 Post Product license fee and its annual fee for maintenance,
Phases version upgrades etc.
O&M
49 Post Preventive Maintenance (PM), including cleaning of
Phases interior and exterior, of all hardware and testing for
O&M virus, if any, and should maintain proper records at
each site for such PM
O&M the O&M period.
O&M the O&M period.
Schedule
Months
O&M the O&M period.
O&M the O&M period.
O&M the O&M period.
5 PROJECT CHARTER
5.1 VISION AND OBJECTIVES OF PROJECT
5.1.1 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 in real time across the police stations in the state and
country”
5.1.2 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. There is also a
need to strengthen the citizen interfaces with the police. Interfaces need to be built with
external agencies like 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 state and country.
5.1.3 OBJECTIVES OF THE PROJECT
The overall objective of this Mission Mode Project is 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
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 through effective usage of Information & Communication Technology (ICT).
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 for the public to
communicate with the police. This will result in;
o Access to Police services in a Citizen-friendly manner

o Provide alternate modes of service delivery such as internet (for general requests such
as NOC, for following up on status of NOC application at Ministry of External Affairs,
Road Transport etc.)
b) 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.
c) 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 like Traffic Management, Emergency Response, Human Resource Management,
Store Management, Finance Management etc., thus resulting in;
o Reducing the necessity to manually perform monotonous and repetitive tasks

o Improving the communication e.g. Police messaging, email systems, etc.
o Automating back-office functions, and thereby releasing Police staff for greater focus on
core Police functions
d) 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. This would enable easy sharing of real-time
information across Police Stations and Districts at the State level and across States at the
National level resulting in:
o Improved investigation and crime prevention
o Better tracking of criminals, suspects, accused, repeat offenders, etc.
5.2 DESIRED OUTCOMES OF THE PROJECT

The following are the expected benefits envisaged from successful implementation of the MMP:
Benefits to Citizens
• Multiple channels to access services from police like, Web, Call centre and Police dept.
Office to access the some services they need. This would save them a lot of time and
effort and would ensure convenience to citizen.
• Simplified process for registering and tracking petitions and FIRs.
• Simplified process for accessing general services such as requests for certificates,
verifications, and permissions.
• Simplified process for registering grievances.
• Simplified process for tracking the progress of the case under trial.
• Simplified access to view/report unclaimed/recovered vehicles and property.
• Improved relationship management for victims and witnesses.
• Greater access to traffic police for registering traffic complaints.
• Faster and assured response from police to any emergency calls for assistance.
• Flexibility w.r.t. obtaining status of their applications / service request immediately on

request.
• Faster and efficient processes.
Benefits to Department of Police, Jharkhand
• Enhanced tools for investigation.
• Centralized crime and criminal information repository along with the criminal images
and fingerprints with advanced search capabilities.
• Enhanced ability to analyse crime patterns, modus operandi.
• Enhanced ability to analyse accidents and other road incidents.
• Faster turnaround time for the analysis results (crime and traffic) to reach the officers
on the field.
• Reduced workload of the police station back-office activities such as preparation of

regular and ad-hoc reports and station records management.
• Enhanced tools to optimize resource allocation for patrols, emergency response, petition
enquiries, and other general duties.
• A collaborative knowledge-oriented environment where knowledge is shared across the

regions and units.
• Better coordination and communication with external stakeholders through

implementation of electronic information exchange systems.
• Advanced tools for traffic regulation and enforcement.
• Automated system to save the efforts of the officials in various day to day tasks.
• Automation of Search of Documents will facilitate convenience for the Police officials
• Speedy recovery of data and impounding will be possible due to instant access to data.
• Timely Report generation with all desired fields would be possible through the
automated system. This will help the decision makers of the Department in prompt
decision making & progress tracking.
Police Personnel, Dept. of Police, Jharkhand
• Balanced performance evaluation metrics and framework.
• Simplified process for registering grievances within the Department.
• Simplified process for personnel’s administrative services such as leave, pay-roll, loans,
and bill claims.
• Integrated view of the service record that presents the performance feedback and
training needs.
Ministry of Home Affairs (MHA) and National Crime Records Bureau (NCRB)
• Standardized means of capturing the crime and criminal data across the police stations
in the country.
• Faster and easier access to crime and criminal information across the country in a
manner amenable for trend and pattern analysis.
• Enhanced ability to detect crime patterns and modus operandi across the State and
communicate to the State police department for aiding in crime prevention.
• The ability to respond faster and with greater accuracy to inquiries from the parliament,
citizens and citizens groups; and to RTI queries.
External Departments (ex: Courts, Prosecution office, Jail, Passports Office, District
Administration, and Transport Department etc.)
• Seamless integration with police systems for better citizen service delivery and
improved law enforcement.
6 ROLE AND RESPONSIBILITY OF STAKEHOLDERS
6.1 PRIMARY STAKEHOLDERS OF THE 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:
• Ministry of Home Affairs (MHA) is the sponsoring Ministry for the CCTNS project at
the National Level.
• National Crime Records Bureau (NCRB) is the Central Nodal Agency that would
manage the implementation of CCTNS at the Central Level.
• Software Development Agency (SDA) is responsible for the development of Core

Application Software (CAS), CAS – Centre and CAS - State. CAS – State would be provided
to all States/UT in India for Configuration, Customization and Extension.
• Department of Police, Jharkhand, is responsible implementing the CCTNS in

Jharkhand State with the ultimate objective of providing all CCTNS-related services to
the citizens, Government and the other “Stakeholders” in an efficient, convenient and
transparent manner.
• State Project Monitoring Unit (SPMU) would work as the extended arm of Police
Department to implement the project. It would be primarily responsible for supporting
Government in supervising, monitoring and evaluating the development and
implementation of the project at the State level.
• System Integrator (SI) would undertake the CCTNS Project in Jharkhand State which
includes integration, configuration, customization and extension of CCTNS Core
Application Software, establishment of network connectivity, deployment of hardware,
Site preparation, data migration and digitization of historical data, Change management
& Capacity Building, Handholding support and Operation & maintenance for Police
Stations, SDPOs and other Higher offices to achieve the defined objectives.
6.2 OTHER STAKEHOLDERS OF THE PROJECT

There are many stakeholders who are directly or indirectly related to the system. The following
is a list of key stakeholders:
• Citizens and Citizen groups
• Non-Government/ Private Sector organization
• External Departments such as Jail & Jurisdiction, District Administration, Passports

Office, Transport Department, Hospitals, Department of Medical Education and Research
etc.
6.3 ROLES AND RESPONSIBILITIES OF STAKEHOLDERS OF THE PROJECT
A clear definition of the roles and responsibilities of all the stakeholders in a project establishes
transparency, accountability, manageability and efficiency in the project. All the stakeholders
are responsible for pursuing the following objectives besides there specific responsibilities.
S No. Responsibilities
1 Providing all support to other stakeholders as and when requested
2 Taking the lead in resolving any project issues
3 Active participation in all the phases of the project by dedicating time & resources
4 Duly considering the project requirements before making any changes in the internal
operations with respect to processes, services, technology, legal & human resource
areas
5 Strict adherence to the timelines and service level agreements
6.3.1 DEPARTMENT OF POLICE
As owner of the Project, the role of Police Department in the successful implementation of
CCTNS includes discharging the following responsibilities:
Sl. Responsibilities
Facilitator
1 Selection of System Integrator for Overall Project development and roll out
2 Ensure that all the components of CCTNS are developed and commissioned as per the
scheduled project timelines.
3 Will enter into an agreement with NICSI for Disaster Recovery Centre space for the
Department and make it available to SI for creation, operationalization and
maintenance of DRC for the project
4 Managing the third party security audit for the application & infrastructure.
5 Ensuring that the all the stake holder participating in the project, are responsive to
the needs of the citizens and putting in place appropriate grievance lodging and
redressal mechanisms for this purpose
Contract / Institutionalization Responsibility
6 Enter into agreement with the SI for creating framework for:
a) Design, development, deployment and implementation of the project
b) Project terms and conditions
7 Setting up of State Project Management Unit (SPMU) for
a) Strategic and Technical guidance and direction
b) Monitoring and Evaluation of the project
Guidance, Monitoring and Evaluation Responsibility
8 Guidance and direction to the project team through SPMU
9 Monitoring of the project progress through SPMU
Sl. Responsibilities
10 Evaluation of the deliverables by System Integrator through SPMU
Change Management Responsibility
11 Relevant co-ordination with NCRB and MHA required for development and
implementation of the project
12 Any changes required to the processes because of process re-engineering
13 Increasing the Awareness about the CCTNS Application among Department and
Citizens.
Support Responsibility
14 Full cooperation and support to SPMU and System Integrator, whenever required
15 Identification / finalization of Data Centre / Disaster Recovery Centre
16 Ensure timely sign-off on the deliverables submitted by SI, wherever required
17 Creation of suitable procedures to ensure timely payment to SI for the work done
18 Creation of proper mechanism for dispute resolution that may arise between
stakeholders
6.3.1.1.1
6.3.2 SOFTWARE DEVELOPMENT AGENCY (SDA)
The Software Development Agency would build the Core Application Software (CAS) at Centre.
CAS-Centre and CAS State would be developed at Centre and sent to Jharkhand State for
customization, configuration and extension in CAS-State.
Sl Roles and Responsibilities
Development and Implementation
1 Development of CCTNS Application Core Application Software (CAS) for Jharkhand

state
• Design and Development of CAS-Centre and CAS-State Modules.
• System Study and Business Process Re-engineering of all modules.
• Preparation of System Requirements Specifications
• Preparation of high level design and standards
• Design & Development of application modules for the portal.
• Testing and acceptance
• Implementation of portal modules
2 • Supporting the SI to ensure that the CAS (State) that is configured and
customized by the SI in the State successfully passes the User Acceptance
Testing (UAT) milestone.
Documentation, Maintenance and Support
3 Ensure complete documentation related to design development of CAS and send it to

Jharkhand state for reference.
4 Ensure to transfer documents related to any upgrade in the system
5 The SDA will define the Software Change Management and version control process and
obtain approval for the same from NCRB. For all proposed changes to the application,
the SDA will prepare detailed documentation including proposed changes, impact on
the system in terms of functional outcomes/additional features added to the system,
etc.
6.3.3 STATE PROJECT MANAGEMENT UNIT (SPMU)
The State Project Management Unit (SPMU) would work as the extended arm of Department to
implement the project. It would be primarily responsible for supporting Department in
supervising, managing the System Integrator, monitoring and evaluating the development and
implementation of the proposed project.
Sl Roles and Responsibility

Monitoring Application Development and Implementation
1 Advising Department on adequacy of internal controls and audit systems in
operations by bench marking with best practices
2 Providing inputs to Department on processes, business rule formulations etc., during
the application development phase.
3 Monitoring Implementation of IT system during all phases
4 Advising Department on IT and business architecture developed by the SI, its
suitability to the needs/requirements
5 Vetting quality and suitability of all deliverables of application development
submitted by SI, supporting Department in sign-off on various deliverables
6 Supporting Department in conducting user acceptance testing and quality audits and
other associated activities
Monitoring IT infrastructure & Services delivery performance
7 Development of necessary templates for monitoring SLAs and expected performance
requirements of the Application, platform and Network
8 Monitoring operations and service delivery, analysis of service delivery data and IT
infrastructure performance
9 Advising Department on matters relating to compliance with SLA parameters and
expected performance requirements
10 Escalation of SLA reports and associated issues, resolution methods to designated
officials of Department
Key Stakeholder Management

11 Planning key stakeholder feedback surveys to understand effectiveness of service
delivery.
12 Design of stakeholder feedback forms and conducting surveys to capture response on
services, service levels, availability of infrastructure and grievance redressal status
etc.
13 Conducting key Stakeholder feedback surveys at various locations and on a sample
basis as required by Department
14 Assessing changes required in applications, service delivery frequency etc., and
subsequent change initiation.
Training and Knowledge management
15 Preparation & Implementation of a detailed training plan
16 Monitoring of effectiveness of training delivered to Department and key stakeholders
Contract and relationship management
17 Assist the department in bid management for selection of SI
18 Interacting with vendor(s) on an on-going basis
19 Preparation of change control proceedings, analysis of options, implications of
changes required in proposed system, preparation of implementation schedules
20 Support Department in all discussions with SI by preparing
• Progress/ performance Reports;
• Consideration of matters arising out of the Change Control procedures;
• Issues escalated in accordance with the escalation procedures as agreed;
• Matters to be brought to notice in accordance with the agreement;
• Highlights of the past month’s performance statistics, concentrating on major
or technical issues reported in service delivery;
• Explanations of matters outstanding from previous periods and in particular
issues, which have been or are about to be escalated;
• Stakeholder satisfaction issues;
• Review of progress to approved changes and status of implementation;
• Suggestions for improvements in service delivery;
• Issues with contract management, billing/ invoicing and other financial
matters.
Other support activities of SPMU
21 Monitoring and reviewing exit management plans provided by vendor, assessing
impact of exit procedures suggested by SI on key stakeholders of proposed system
22 Supporting Department in conducting quality audits of proposed system and review
of audit reports in enabling Department to provide sign-off to SI
23 Reporting to Department on various aspects of proposed system, visits to office
locations of SI on a regular basis for assessment of ground situation and reporting to
Department

24 Analysis and tracking of issues, collection of statistics and data, documentation and
presentation
25 Review and benchmark operations against set standards as decided from time to
time.
26 Risk Management and Risk Mitigation plan and Department accordingly
Finance and reconciliation issues:
27 Advise Department on payments to SI
6.3.4 SYSTEM INTEGRATOR (SI)
System Integrator(SI) is responsible implementing the CCTNS Project in Jharkhand State which
includes integration, configuration, customization and extension of CCTNS Core Application
Software, establishment of network connectivity, deployment of hardware, Site preparation,
data migration and digitization of historical data, Change management & Capacity Building,
Handholding support and Operation & maintenance for Police Stations, SDPOs and other Higher
offices to achieve the defined objectives
Development and Implementation
1 Implementation of CCTNS Application Core Application Software (CAS) for Jharkhand

state
• Configuration, Customization and Extension of CAS-State Modules.
• System Study and Business Process Re-engineering of all modules.
• Preparation of System Requirements Specifications
• Preparation of high level design and standards
• Design & Development of application modules for the portal.
• Testing and acceptance
• Implementation of portal modules
2 Installation and commissioning of hardware required

Establishing IT and non-IT Infrastructure
• Installation and commissioning of hardware required at Data Centre, NDR and
DRC at NICSI space provided for the Department through an agreement
• Installation and commissioning of hardware required at all Police Stations and
Higher Police Offices
• Carry out necessary Site Preparation and provide all required non-IT
Infrastructure at Police locations for implementing CCTNS project
3 Providing the necessary components for Network Connectivity

• Providing VSAT network connectivity and bandwidth among assigned police

locations
• Providing Network connectivity and bandwidth charges for connectivity among
Police Locations in case it not assigned to BSNL exclusively.
• Providing Network connectivity and bandwidth charges for connectivity
between DC and DRC in case it not assigned to BSNL exclusively.
• Providing Network connectivity and bandwidth charges for connectivity
between SCRB and NCRB in case it not assigned to BSNL exclusively.
4 Data Digitization and Migration of CIPA data for CIPA police stations and Data
Digitization and Migration of data for last 10 years
5 Carry out Capacity Building and Training for Police Personnel on CCTNS Application
and basic IT awareness
Documentation, Maintenance and Support
6 Handholding support to Department at each police location wherever required during

the project period
7 Maintenance for a period of 5 years of CCTNS application
8 Ensure complete documentation related to design, development and implementation

work is done and submitted to Department
9 Ensure all milestones are completed within the agreed timeline
10 Ensure meeting of all agreed SLAs
11 Ensure quality of deliverables as agreed during the agreement
12 Cooperation with Department, SPMU and other Stakeholders
13 Periodic progress reports (monthly, quarterly and annually) submission to SPMU
14 Cooperation with Department appointed Quality Audit Agency during audits
6.4 PROJECT GOVERNANCE STRUCTURE

The following governance committees, recommended by DIT shall review progress,
implementation, and rollout, shall monitor utilization of funds and issue Policy
Directions/Guidelines for CCTNS project at the State level.
• State Apex Committee
• State Empowered Committee
• State Mission Team
• District Mission Team
The table below provides the committees /teams that form part of the governance structure and
their roles and responsibilities as defined in the CCTNS implementation guidelines provided by
MHA.
Table 2: Governance Structure
Committee / Team Roles & Responsibilities
State Apex Committee

• Reviewing progress of the Project,
• Overseeing utilization of funds,
• Policy Directions and Guidance for successful execution of the
Project,
• Ensuring continuance of Mission Leader for sufficient duration,
and
• Creating a supporting environment for the success of the
project
State Empowered
• Disbursement of funds to Districts and other units/agencies
Committee
• Approval of BPR proposals
• Sanction for various project components, as may be specified,
including the Hardware/Software procurement as per the
specifications
• 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
• Getting sanction of GOI for various aspects of the project
• Hardware rollout and operationalization
• Co-ordination with various agencies
• Resolution of all software related issues, including
customization
• Resolution of all other issues hindering the Project Progress
Committee / Team Roles & Responsibilities
• 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 Police
Station and subsequently all the police locations within the
district
• Ensure hardware and software installation, and
operationalization 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 State Apex Committee is as following:
Table 3: Composition of State Apex Committee
Members Composition
Chairman Chief Secretary, Jharkhand
Co- Chairman Principal Secretary, Home Dept. Jharkhand
Member Principal Secretary, Finance Dept. Jharkhand
Member Secretary, Dept. of IT, Jharkhand
Member Director General of Police, Jharkhand
Member Representative from NIC, Jharkhand
Member Nodal Officer, CCTNS, Jharkhand

Secretary
Member Representative of MHA, GOI, Jharkhand
Member Head of SCRB, Jharkhand
Member Inspector General of Police ( Provisions), Jharkhand
Member Any other Member from the field of IT/Telecom, nominated by

Chief Secretary
Frequency of meeting: Once a Quarter
The composition of State Empowered Committee is as following:
Table 4: Composition of State Empowered Committee
Members Composition
Chairman Director General of Police, Jharkhand
Co- Chairman Head of SCRB, Jharkhand
Member Representative of NCRB
Member Representative of Home Dept., Jharkhand
Member Representative of Finance Dept., Jharkhand
Member Representative of Dept. of IT, Jharkhand
Member Representative from NIC, Jharkhand at state level
Member Secretary Inspector General of Police ( Provisions), Jharkhand
Member Additional Director General of Police (CID)/(SB)
Member Special Invitee
Frequency of meeting: Once a month
The composition of State Mission Team will have the following members:
Table 5: Composition of State Mission Team
Members Composition
Mission Nodal Officer, CCTNS, Jharkhand
Lead/Member *
Member/Mission Head of SCRB, Jharkhand

Lead*
Member Responsible representative from NIC at state level
Member State Informatics Officer(SIO), NIC
The composition of District Mission Team will have the following members:
Table 6: Composition of District Mission Team
Members Composition
Chairperson
Superintendent of Police of the District
Convener
One Officer of DCRB
Member District Informatics Officer of the NIC District
Member One officer from district police having computer knowledge as

appointed by District SSP/SP
Core Team: The Core Team instituted by the Department will review each every aspect of
the project and provide insight to the Project for taking decision by the Nodal Officer,
CCTNS Project. Frequency of meeting once in a month
7 GEOGRAPHICAL COVERAGE
In line with the mandate of Govt. of India, the geographical coverage has been considered for all
over state boundaries of Jharkhand. In terms of the locational entities of the offices covered is
placed in following table
Table 7: List of Police Locations
Sl. Offices No.
5 Number of Zones 4
8 No. of Jails 26
11 PHQ 1
12 No. of Police Personnel Approx.

60,000**
7.1 Organisation structure

The Jharkhand State Police is headed by the Director General of Police (DGP). The DGP is fully
responsible for the maintenance of discipline and for efficient discharge of duties by all ranks in
the department.
The Jharkhand Police Head Quarter is based at Ranchi and functions through different wings.
Each wing is headed by Additional Director General of Police (ADGP) or notified senior officer.
The different wings are given as under:
1. Crime Investigation Department (CID)

2. Special Branch
3. Wireless
4. Training
5. Operations
6. Special Forces (JAP, IRB, JJ, SAP)
The Jharkhand Police field establishment is divided into 4 Zones. Each Zone is headed by an
Inspector General of Police (IGP). Similarly the field establishment is divided into 7 Ranges. Each
Range is headed by Deputy Inspector General of Police (DIG). Each Range DIG reports to his
respective Zonal IG. The Jharkhand state has 26 Police districts and each District Police is
headed by a Superintendent of Police (SP) and falls under a particular Range office.
Figure 1 - Organization Structure Jharkhand Police
Figure 2: Non-Field Organization Structure Jharkhand Police
The list of 26 Police Districts is as follows:
Bokaro West Singhbhum Chatra

Gumla Garhwa Giridih
Hazaribagh Deoghar Godda
Khunti Pakur Saraikella-Kharswan
Latehar Lohardaga Simdega
Palamu Ranchi Sahebganj
Ramgarh Dhanbad East Singhbhum
Jamtara Koderma Dumka
Rail Dhanbad Rail Jamshedpur
Please visit the www.jharkhandpolice.gov.in site for more details.
8 PROPOSED SOLUTION
A Core Application Software (CAS) has been envisaged for catering the functions of police
department. Overall process flow, police departments and organization structure have been
discussed below followed by overview of proposed CAS solution.
CCTNS is deployed on a centralized architecture wherein various offices of Police Department

connect to the system through Data Centre. The entire solution architecture is based on
following 4 pillars:
• Users/Stakeholders
• Delivery Channels
• Services / Modules
• Resources
Figure below shows the overview and depicts CCTNS services accessed by different users
through various channels and resources that integrate and interoperate to deliver these
services.
Figure 3: CCTNS Solution Overview
8.1 TO BE PROCESS FLOW

In broad the envisaged solution includes development of CAS, providing required IT
infrastructure and network infrastructure for CCTNS. CAS has been discussed below while IT &
Networking Infrastructure and other requirements are mentioned as Annexure.
8.1.1 CORE APPLICATION SOFTWARE
The CCTNS application software will contain a “core” for the States 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. Each State would
customize the CAS 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. The choice of such applications lies exclusively with the State.
The Core application Software (CAS) is expected to be ready by October 2011.
This section provides the details of the CAS (State) and CAS (Centre) that will be developed by
the Software Development Agency (SDA) at the Centre. 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 functional requirements and the technical architecture of the CAS (State) and CAS (Centre)
is provided in detail in the RFP issued by NCRB for the selection of the SDA. The relevant
sections of the SDA-RFP are provided in Annexure of this RFP. (Please visit
http://ncrb.gov.in/cctns.htm for more details on CAS)
The CCTNS application software can be conceptualized as comprising different services that fall
under two broad categories, CAS (Centre) and CAS (State).
CAS (Centre)
CAS (Centre) would cater to the functionality that is required at the GoI level (by MHA and
NCRB). CAS (Centre) would enable NCRB to receive crime and criminals’ related data from
States 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 is needed 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 (Centre)

i) 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.
ii) 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.
iii) 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.
iv) Talaash Service
The service will enable the user to search for missing persons across a central/ national
database.
v) 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.
vi) Registered Vehicle and Vehicle of Interest Service
Overview of Services for CAS (Centre)

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.
vii) Publication Service
This functionality will help the NCRB to publish the periodic crime reviews to the NCRB portal.
viii) 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.
ix) 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.
CAS (State)
CAS (State) covers functionality that is central to the goals of CCTNS and is common to all States
and UTs. It would focus primarily on functionality at police station with special emphasis on
crime investigation and criminals’ detection. This part would be developed at NCRB and
provided to the States and UTs for configuration, customization and enhancements / extensions.
The State 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 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, 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.
• It will be content/forms-based, with customized forms based on requirements.
• It will be a flexible application 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, thus 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.
• It will provide the ability to view and exchange information amongst Police Stations,
between Police Stations and other Police formations and with external entities including
citizens.
• It will ensure that relevant 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.
• It will ensure central facilitation and coordination; however CAS (State) will be primarily
driven and owned by States where States can configure and customize the CAS for their
unique requirements without the intervention of the central entity
Overview of Services in CAS (STATE)

i. 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.
ii. Petition Management Service
The service shall enable the police personnel to register and process the different kinds of
general service petitions and complaints.

iii. 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.
iv. 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 genera
complaints, etc.) reported by the public.
v. PCR Call Interface and Management Service
The service shall enable the police personnel to register and process the complaints as received
through the Police Control Room through the Dial 100 emergency contact number.
vi. 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.
vii. 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.
viii. 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.
ix. Police Email and Messaging Service
The service shall enable the police personnel to send / receive official as well as personal
correspondence.
x. Periodic Crime, Law and 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.
xi. Notification of Alerts, Important Events, Reminders and Activity Calendar or Task
Services
The service shall capture / generate the required alerts, important events, reminders, activity

calendar and tasks.
xii. State-SCRB-NCRB Data Transfer and Management Service
The service shall enable the States to collate, transform and transfer the crime, criminal, and
other related data from state to NCRB.
xiii. State CAS Administration and Configuration Management Service
The service shall enable the individual State to configure/ customize the application to suit to
their unique requirements.
xiv. 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.
xv. User Feedback Tracking and Resolution Service
The service shall enable the police personnel in logging the issues/defects occurred while using
the system.
xvi. Activity Log Tracking and Audit Service
The service shall capture the audit trail resulting from execution of a business process or system
function.
xvii. 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
DEVELOPMENT OF CCTNS CORE APPLICATION SOFTWARE (CAS)
CAS (Centre) and CAS (State) will be developed at NCRB under the overall guidance and
supervision of MHA, and a dedicated team from NCRB under the supervision of National
Informatics Centre (NIC). NCRB, on behalf of MHA, has engaged a professional software
development agency (SDA) to design and develop CAS (Centre) and CAS (State) and offer
associated services. The SDA would enhance and maintain CAS (Centre) and CAS (State) until
the end of the engagement with NCRB and subsequent to that, CAS (Centre) and CAS (State)
would be managed by NCRB under the guidance of NIC, DIT and MHA.
CAS (State) would be built as a platform at NCRB addressing 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 States with the flexibility to build their state specific
applications around it and in addition to it. CAS (State) will be provided to States for
deployment. Each State would customize the CAS according to their unique requirements and
thereafter commission the same. A bulk of the functionality would be added at States’ discretion
and would be added as extensions to the CAS (State) by the System Integrators (SI) chosen by
the States.
In order to achieve the above stated goals of simultaneously ensuring consistency and
standardization across States (where necessary and possible), and enabling States 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 and deployed in all States.
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 work in police stations
with low and/or unreliable connectivity.
TECHNOLOGY STACK FOR CAS (STATE) AND CAS (CENTRECENTRE)
CAS (State) will be developed in two distinct technology stacks by the Software Development
Agency at the Centre. The details of the Technology Stacks are provided as an Annexure to this
RFP. The SI is expected to bid with one of the technology stacks in response to this RFP. SI shall
procure all necessary underlying solution components required to deploy CAS (State) solution
for the State.
ROLE OF SOFTWARE DEVELOPING AGENCY (SDA) IN SUPPORTING CAS
The SDA will provide Services for CAS (State) for a period of three (3) years followed by two
optional one-year periods from the date of successful completion of the CAS (State) Certification.
The decision on the two optional one-year periods will be taken in entirety by NCRB. During the
contract period, the SDA shall offer the following services:
• Application Management Services for CAS (State) and CAS (Centre)
• Technical Program Management of Implementation of CAS (State) for all 35 States/UTs

throughout the duration of the engagement with NCRB/MHA.
Each of these activities is detailed out below:
Application Management Services for CAS (State) and CAS (Centre)
The SDA shall provide Application Management services to the CAS (State) and CAS (Centre).
The application management services include the following:
• Provision of 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.
• 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.
• SI shall be responsible for application management services and maintenance support

for additional applications, customizations and extensions at the State.
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.
• Cost and effort estimate shall be mutually agreed upon between SDA and NCRB
The SDA will define the Software Change Management and version control process and obtain
approval for the same from NCRB. For all proposed changes to the application, the SDA 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 certification, the SDA will hand over the certified CAS (State) to States through
NCRB. While NCRB will facilitate the transfer, the successful transfer of CAS to States on time is
SDA’s responsibility. During the period of CAS Solution Design and Development and the
Operations and Maintenance phase following that, the SDA shall provide technical program
management services in implementing CAS in States. Through the Technical Program
Management, the SDA shall extend all the necessary support to the State SI and ensure that the
SI successfully configures, customizes and deploys CAS (State) in States. The SDA’s Technical
Program Management responsibilities include but are not limited to:
• Preparation of technical manuals to enable the SI to configure, customize, enhance and

deploy CAS in States; to be made available to SIs through the CAS online repository
managed by the SDA.
• Preparation of “CAS Implementation toolkits” that comprehensively covers details on all

the aspects of the CAS (State) and CAS (Centre) applications including but not limited to
technical details of CAS, configuration, customization, and extension details,
infrastructure sizing details, installation, commissioning, maintenance, infrastructure
environment tuning, 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 seamless 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 customizing
and deploying CAS
o All completed and updated project documents including FRS, SRS, HLD, LLD and
Test Plans
o Relevant software assets/artefact (including configuration utilities / tools,

deployment scripts to SIs to deploy CAS (State) in States)
o Relevant standards and design guidelines to the SI for customization, further

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 monthly contact sessions at NCRB

covering all State SIs during the contract period. During the contact sessions, the SDA
shall conduct structured training sessions on the CAS Implementation Toolkit prepared
by the SDA.
• Dedicated Points of Contact: Members of the SDA’s team shall act as points of contacts
for the State level SIs. The number of States serviced by each SDA contact person shall be
determined in consultation between the CAS Core Group and the SDA. The point of
contact will be responsible for addressing queries from an SI and in meeting SLA targets
(in responding to States’ needs).
• Helpdesk Support: SDA shall provide Helpdesk support to the State SIs during
customization, 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).
The SDA shall deploy a team of at least 5 qualified and certified resources in NCRB to
address the questions from the SIs.
• Deployment Scripts: The SDA shall develop the necessary deployment scripts to deploy
CAS (State) in States and provide the same to State SIs.
• Data Migration Utility: The SDA 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 States and will enable the SIs to migrate data from legacy/paper based systems to the
CAS databases.
• Language Localization Support: Proving interface in local languages is a key

requirement of CAS (State). The SDA shall build CAS (State) with interfaces in English
and Hindi; and also build CAS (State) in such a way that it can be configured for
interfaces in other local languages at the State level by the SIs. In addition, the SDA shall
assist the SIs in customizing CAS (State) to support local language interface and ensure
the development of interface in local languages.
• Supporting the SI to ensure that the CAS (State) that is configured and customized by
the SI in the State successfully passes the User Acceptance Testing (UAT) milestone.
o Configuration of CAS (State)
o Customization of CAS (State)
o Data Migration of CAS (State) related data from the legacy systems and / or
manual records 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 Maintenance of 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.
• Seamless data exchange from CAS (State) to CAS (Centre)
• Troubleshooting, resolution and escalation with State SIs; and ownership of end-to-end
data exchange between the CAS (State) and CAS (Centre) needs to ensure seamless and
real-time data exchange.
9 OVERALL ARCHITECTURE
9.1 FUNCTIONAL REQUIREMENTS

The section of the FRS specifies the functional requirements of the CCTNS-Jharkhand
Automation System in terms of Modules and their associated Process flow. The Modules are
primarily organized in terms of the Actors (users) that interact and benefit from the Modules.
Functionality for Users (Citizens, Stakeholders and Jharkhand Police officials)

CCTNS-Jharkhand will comprise of 17 Services/ Applications and will be developed under two
categories; CAS-State and CAS- State Extension. Services/Applications for CAS-State will be
developed by NCRB appointed Software Development Agency (SDA) at centre and will be called
as CAS-State. These Applications will be further customized while adding additional
functionalities by State-SI (if any). CAS-State Extension will be set of Services/ Applications and
will be completely developed by State–SI. Following are different Modules and Applications
which will be part of the CCTNS-Jharkhand
Table 8: CCTNS Jharkhand Application Modules
Additional
Type of
functionalities for
Sl. Module Name Application /Service Services/
CAS State
Application
(Yes/No/NA)
1. Registration Complaint and FIR CAS-State Yes

2. Investigation Investigation CAS-State Yes

Unclaimed/Abandon CAS-State No
Property Register Service
Crime Investigation CAS-State No

Reports
3. Prosecution Custody, Trial & CAS-State Yes

Module Prosecution, Court and
Jail Interface &
Prosecution Management
Services
4. Search Module Crime & Criminal Records CAS-State Yes

and Query Management
Service
Additional
Type of
functionalities for
CAS State
Application
(Yes/No/NA)
5. Configuration State CAS Administration CAS-State Yes

Module and Configuration
Management Service
6. Citizen Citizen Portal Service CAS-State No

Interface
Portal Employee Portal Service CAS-State *SRS to be carried
Integrator
7. Traffic Module Challan Management CAS-State *SRS to be carried

Traffic Management Integrator
Reports and MIS
8. Crime PCR Call Interface and CAS-State Yes

Prevention Management Service
Duty Allocation, CAS-State *SRS to be carried

Nakabandi, Patrolling, Extension out by System
VIP Security/Prisoner Integrator
Petition Management CAS-State Yes

Service
e-Mail/Message CAS-State No
Notification of Alerts, CAS–State Yes

Important Events,
Reminders and Activity
Calendar or Tasks Service
9. Analysis, Periodic, Crime and Law CAS–State Yes

Business & Order Reports and
Intelligence & Review Dashboard
MIS Module Service
10. Data Transfer State SCRB-NCRB Data CAS–State No

Module Transfer and
Management Service
11. User User help and Assistance CAS–State No

Assistance Service
Additional
Type of
functionalities for
CAS State
Application
(Yes/No/NA)
Module User feedback tracking CAS–State No

and resolution Service
12. Security User Access and CAS–State No

Module Authorization
Management Service
Activity Log Tracking and CAS–State No

Audit Services
13. Naxal CAS-State *SRS to be carried

Maintain database of
Information Extension out by System
Naxal
System Integrator
Updating on Naxal
activities in the state
Sharing of data among
the Naxal-affected states
14. SP office CAS-State *SRS to be carried
HRM systems including
module Extension out by System
force statement, force
Integrator
return, command and
duty distribution,
inventory management,
fleet management,
workflow, accounts
management, file tracking
etc.
15. Crime Records CAS-State *SRS to be carried
All crime records
Module Extension out by System
including CD Part-I, II, III,
Integrator
and all connected
registers
*Functional requirements specified in the next section
The additional functional specifications of all the modules are listed below:
Table 9: Functionalities Specifications for State Specific Customization Requirements
Registration Module
FIR Crime Registration module should provide all the functionalities
Registration mentioned in CCTNS FRS by NCRB. Following are additional
and Complaint functionalities to be developed by SI for Crime Registration module of
Lodging Jharkhand CCTNS:
• The police personnel should be able to assign/add/delete acts,
sections, and local Acts while recording the complaint/FIR
• System should update all concern register if there is any change in
any register involve in Crime registration Process
• System should send alert to all concerned Cell/dept./branch (like
CID, SB, and SIB) regarding new complaint/FIR.
• Biometric device should be integrated with the system for capturing
fingerprints and storing the details in the database
• System should provide functionalities of common component for all
Crime Registration processes:
o Information Provisioning
o Form Availability
o Status Tracking
• System should provide functionalities of common component for all
Registration of complaint/Grievance processes:
o Application Receipt
• System should be able to identify the section of cases according to
the crime
• Un Natural death cases should be correlated with missing person
cases by the system while registering.
• Citizen should able to check the FIR/Complaint status online
MIS and
• The Reports (MIS) should be generated from System
Escalation
• The Escalation alert should be generated from System
Investigation Module
Investigation Crime Investigation module should provide all the functionalities
& mentioned in CCTNS FRS by NCRB. Following are additional
Interrogation functionalities to be developed by SI for Crime Investigation module of
Jharkhand CCTNS:
• System should display all possible Investigating Officer (IO) and no
of cases/type of cases currently being handled by them. System
should suggest the best IO based on experience and success ratio of
IO
• System should send request for involvement of external agencies
through SMS/Email.
• System should allow the user to prepare, preview, print
requests/forms that are sent to external agencies (FSL, FPB,
hospitals, RTA etc.,) for expert opinion. The request/forms should
be made available to the user as templates that are managed
(created/edited) through administration functionality
• The audio video file should be prepared and maintained in System
• System should generate the template of possible evidences to be
collected based on sections of Crime.
• System should maintain all evidence record like amount and date
etc.
• System should allow the external agencies like Forensic lab to
submit their report and update the same in system
• System should maintain documentary proof copy in scanned and
other format
• System, should categorize all evidence etc. and stored with some
parameter & summary to facilitate its search
• System should support to identify accused from Proclaimed
Offender list if crime pattern seems to identical to any earlier case
• System should generated search/arrest warrant request
• System should send the arrest detail to senior Officers
• System should send alert for wanted criminal
• System should maintain the list of Absconder
• System should generate request for police remand
• System should facilitate in preparation of consolidated list /
Summary of evidences/statement for interrogation.
• System should allow updating of Case Diary based on report and
updating on interrogation
• System should allow to attach the audio/video file of interrogation
• The Charge sheet should be prepared through System and System
should display all statement, evidences and interrogation detail etc.
which can be consolidated for charge sheet. The review of charge
sheet with PP should be through System with proper track change

etc.
• System should send the missing person detail sent to control room
and SP office. The detail should include:
o Name
o Address
o Photo
o Identification mark
o Parents/Spouse Name
o ID/UID No
o Physical Appearance
o Mental Status
o Last spotted location
o Phone no. of the contact person
• At the end of one month duration the missing person/unidentified
body information should automatically updated to DCRB, SCRB &
NCRB (Talaash)
• In case of Person found to be dead the System should generate
Inquest/PM report request
• The updating in status of Missing person system should add or
remove person details in Crime gazette/Talaash.
any register involve in Crime Investigation Processes
• System there should have provision of changing the sections.
Whenever a section is changed by Investigating Officer an alert
should go to all higher offices and relevant court
• System should also update all the relevant register if any change is
made in the section by the investigating officer during investigation
• If due to any reason charge sheet is not prepared then system
Should generate an alert before two days of the deadline filling
charge sheet
• Should have facility to capture status whether person is sent for
judicial remand or police remand after arrest/surrender
• Should have facility to capture finger print of arrested person
• System should be able to send supervision note by the supervisor of
the case to the higher and concern officer

• System should be able to send progress report by supervisor of the

case to the concern higher officer.
• System should allow SP to issue Report 1, Report2 and subsequent
Report after receiving the supervision note and progress report.
• System should also allow senior officer to pass an order if required
during the investigation to the concern officer.
• Modus Operandi of various previous crime should be available in
the application
• System should have the capability to search & match the missing
person with the unidentified dead bodies and victims reported in
different cases
• Status of case property whether released/transferred to other PS/
Lab testing produced to court etc. should be available along with
details
• Criminal dossier of all the criminals across India should be available
for search
• Should have help features /FAQs hat can help IO undertake
investigation for various types of cases
Reports and
Escalation
• System should be able to generate following reports to be available
to Higher officer :
o pending cases
o PS wise
o IO wise
o city wise
o district
o Number of cases where recovery happened
o Number of cases where accused is identified and arrested
o Number of cases where accused is identified and not
arrested
o Number of cases where charge sheet is pending
o Number of cases pending due to response of external
agencies like cases pending due to want of forensic report
Crime
• System should be able to share all records of crime reported in the

Investigation State for crime cell with other departments.
Department
• System should allow to transfer cases from District Police to CID
Crime Cell
• System should generate comparative figures and alerts for Crime
Cell
• Generate alerts on long time pending cases
• System should share the case diary with higher officers online
• Crime registered under IT Act should be shared with Cyber Crime
cell.
• System should provide facility to investigation team to exchange
information with Cyber Crime Cell
• System should keep profile of history sheet who conducted crime
against Wildlife and forest and sharing of information on case
registered.
• System should keep records of citizen complaint received and their
status.
• System should generate automatic alerts on pending complaints.
• System should provide facility to communicate with district SP.
• System should maintain narcotics offence, fake currency offence in
the state and shall send a compiled report of all districts to NCRB.
• System should provide facility to match the finger prints with the
existing database
• System should provide facility to share disputed document between
SP and QD experts.
• System should information on crimes occurring against schedule
caste and schedule tribes in the state
• System should maintain the records & status of Vidhansabha
Questions and automatic alerts on pending records from concern
Department.
Prosecution Module
Prosecution Prosecution module should provide all the functionalities mentioned
in CCTNS FRS by NCRB. Following are additional functionalities to be
developed by SI for Prosecution & Conviction module of Jharkhand
CCTNS:
• System should display in monitor/LCD screen of Control Room the

Prosecution Module
list of accused in Police Remand.
• System should allow information exchange with DPO and IO
through Emails/SMS.
• System should allow the Summon Office to updates all summons
detail regularly.
• Concerned department should inform IO through System about
availability for the case.
• IO should be able to update the bail detail in system.
• System should send alerts to the concerned department, witness &
external agency about hearing date through SMS/Email.
any register involve in Prosecution & Conviction Processes.
• System should allow for alerts/SMS to all police stations as soon as
criminal is released from jail.
• System should allow for status of court case, conviction details,
summons /warrants, remand details, judicial custody details to be
received by SMS.
Reports and
Escalation
Search Module
Search & Search Module should Provide all the functionalities mentioned in
Explore CCTNS FRS by NCRB. Following are the additional functionalities to be
developed by SI
• System should also provide an advanced search capability and
allow user to filter the search to a greater detail like crime details,
suspect details, victim details, modus operandi and property
• System should provide for configuring / building a query on the
searchable data through query builders
• System should enable the user to store, load and delete custom
queries for easy retrieval
Configuration Module
Configuration Following are the additional functionalities to be developed by SI for
of Application easy configuration of CCTNS application
• System should allow the user to define the organization with all its

units (police stations, districts, range, zone) and user hierarchy
• System should present the data elements based on major and minor
heads selected by user
• System should allow the user to add/modify/delete order of acts,
sections and local laws
• System should provide the user to add/modify/delete order of
MO/property-type/castes/tribes details
• System should not allow the user to delete/modify/modify-order of
the master data provided by the centre.
• System should allow the maintenance of different templates as per
the directive of local governments or standard guidelines
Citizen Interface Module

Portal Portal should provide all the functionalities mentioned in CCTNS FRS
by NCRB. Following are additional functionalities to be developed by
SI for Portal of Jharkhand CCTNS.
• The system should have On-Line complaints receiving complaints,
forwarding to the concerned district and Police Station, tracking its
status through a unique number.
• The system should have On-Line incident information – giving
information to various police authorities about fire breaking, crime
commission, criminal’s presence etc.
• The system should have On-line queries facility – Queries under RTI
Act or general queries.
• The portal will have 2 interfaces; one for the employees (Internal) &
another for external stake holders.
• SI should Re-design and manage Jharkhand Police website which is
under construction. Department currently has only a basic under
construction website with detail of Jharkhand Police in English. SI
has to redesign the website in 2 languages English and Hindi. Portal
should be the external interface for the CCTNS portal.
• System should provide an interface for all applications relevant for
each type of users such as “Registration”, “Investigation” etc.
• System should enable user to reorder, pages, remove content, and
modify page layout to organize content in their personal
workspaces.
• System should provide comprehensive search facility to locate all
types of content within the set confines of security.

Citizen Interface Module
• Website will be the face of Jharkhand Police to people in general as

well as stakeholders as an organization. SI should ensure regular
updating of website with relevant data (minimum 4 updates a
month is expected).
• System should allow online registration of Foreigners – Registration
at Police Station with details of place of stay, duration & purpose
etc.
• System should allow to register complaints On-line and forwarding
it to concerned district and Police Station. System should track the
status of complaint through unique number.
• System should allow to query online under RTI Act
• System should allow online incident information giving information
to various police authorities about fire breaking, crime commission,
criminals’ presence etc.
• MIS on Portal Usage, Up time etc.
Traffic Management Module

e-challan
Following State specific functionalities to be developed by SI for
Jharkhand CCTNS
• System should have capability to enter challan details into the
system
• System should be able to generate challan report
• System should allow to update and maintain the bank receipts
records
• Hand held device to be provided to the police officer will enable to
generate the challan details in the system directly and also
authenticate the documents held by the motor driver.
• Should have the feature of finding the details of previous challan(s)
if any on the vehicle/ driving license/ driver/ any other individual
and take necessary action (if required)
• Should have the facility of finding the information on the vehicle
and/ or the driving license on the basis of its Registration number/
Driving License no. / Name and Fathers Name/ Date of Birth.
• Should have the functionality of challaning, money collection from
the offender, updating of challan information and compounding of
challan at the scene of offence
• Should support Handheld devices for – issuing challan, accessing


databases, reporting violation, acknowledging receipt of documents
obtained from the offender, Compounding of challan on the spot,
etc.
• Should have the facility to give the system generated copy of the
Challan, receipt for documents or payment receipt to the offender
(optional)
• Should have the facility of automatic update of Challan information
in the Traffic Violation Database.
• Should have provision of accessing the database of crime and
criminals and lost and stolen vehicles using the hand held device at
the scene of offense
• Should have the facility of online payment of challan using the
internet portal.
• Should have the facility to pay the challan money at the kiosks at the
Traffic Police Office.
• The Offender would have the facility to take the services of a courier
service hired by Police to return his Registration Copy/ driving
license/ Pan card etc. seized during the Challaning. (The Offender
can also visit the traffic police office and collect his documents)
• The money from the Kiosks at the Traffic Police office would be
collected in cash and the system would be updated
• Should have the information on the status of Challan payment by
the offender(s)
• System should allow capturing of information relating to violations
compounded by the court (in case of offenders who prefer going to
court).
• System should show pendency of challan in courts (more than 1
year, 6 months, 3 months, 2 months etc.) and generate reports
• Should have provision of recording the offence against driver/
owner and maintaining the record for suspension/ cancellation of
licenses
• Should create automatic alerts for offenders who have not paid
their Challan fees for more than a month when they are caught next
time
• Should have the facility of updating the database once the
documents of the offender have been sent to court
• Should have interface with Police for criminal database, Transport
for vehicle and drivers data, SCRB for stolen vehicles

• Should allow violations/ challaning database to be shared with

Transport department to allow them to cancel the driving license.
Traffic
• The system should be able to display all the road network and
Management
routes in a digitized maps based system.
• The system should be able to record the information on the traffic
flow in a particular crossing during different hours of the day.
• The system should allow the traffic police to plan for the traffic
diversion in a specific route due to event/construction/security
measures.
• The system should be able to generate report on the traffic
management
City
• The system should able to monitor the traffic condition in a
Surveillance
particular traffic intersection through CCTV. The system should be
able keep record of the traffic flow in the intersection.
• The system should allow the officer to record the traffic violation at
the intersection and keep record the vehicle number.
• The system should allow the officer to send alert to the next traffic
intersection and capture the offender.
Reports and
• The Traffic Status should be generated for the location should be
Escalation
based on historical data
• In case of changes made in the register regarding Traffic Offence
Booking process, the system should update all relevant registers
• The special event/security/Civil construction alert for traffic
diversion/management should be generated by System
• The System should provide Traffic Management plan for detail of
team and duty hour
• The System should provide functionality on preparing report on
Traffic Management
• System should update all concerned register if there is any change
in any register involved in Traffic Management Process. The
Reports (MIS) should be generated from System which would be
consolidated for all the districts and sent to Police Head Quarters.
Crime Prevention Module

Emergency
• Single Automated number i.e. ‘100’ should be used for any
Response


emergency – Call taking & call dispatch, interface with fire office,
hospital & other district control rooms
• System should enable real time Fleet Management – GPS enabled
M.T. fleet with navigation system for quick response
• System should allow real time surveillance – Surveillance of
important intersections, vital installations etc.
• Citizen location should be automatically displayed if call is from
Landline number
• The Call detail should be recorded
• The Caller & Call detail should be fed on System
• The GPS should be used to identify the closest ‘PCR’ & Patrolling
Vehicle to the caller/incident location. The Updated Map should be
used for location identification.
• The Call detail should be send to the ‘PCR’, Patrolling Vehicle, Police
Station, Other agencies like Blood Bank, Disaster Management team,
Hospitals, Fire Station near to the Emergency location nearest to the
Caller/incident location through SMS/Message Alert.
• System should have details of Police personnel/equipment etc.
required to be deployed for tackling emergency
• The Police team should update the Status/action through
SMS/Message using PDA.
• The Police team should submit report on System
Nakabandi/
• The Concerned PS/Nakabandi team should receive the detail about
Patrolling/ VIP
Vehicle/Individual as alert in form of message/SMS
Security/
• The PS/Nakabandi team should be able to send the detail of
confiscated Vehicle/Individual/ Property with photograph to the
concerned PS/Police Offices who raised the alert
• The detail of Nakabandi team/patrol team/PCR should be captured
in Database under General Diary register
• System should allow to identify the Patrolling requirement in the
area of Jurisdiction based on data available
• System should inform the deployment plan to Patrol/PCR team
member through message/SMS alert
• The position of Patrol team/PCR should be available to control
room through GPS
• The Patrol team should be able to inform PS/Control room for
additional support for incident through PDA in form of


message/SMS alert
• The team should be able to send additional support requirement as
normal/emergency
• External agencies/Department should be able send the Security
requirement through System
• System should provide details of available Police
personnel/equipment etc.
• System should allow to send request to the concerned Office for
providing additional Police personnel/equipment
• System should allow to reply for the request regarding Police
personnel/equipment detail to concerned Police Office /external
agencies
• System should send the Security Plan detail to all the Offices from
where the Police personnel/equipment has to be deployed
• System should send alert in form of message/SMS 12 & 6 Hrs.
before the schedule deployment
• System should allow to prepare report & submit on the Security to
the Offices where it is required
• System should allow Department/External agencies to raise the
Surveillance request
• System should allow Department/External agencies should be able
to share detail like name, any ID, photograph, finger print of
suspects
• System should allow to raise the alert about movement of suspect
from one PS jurisdiction to another
Naxal Information Management

Application in Jharkhand Police is using in-house developed System having the
Use following features. SI is expected to integrate the application in to
CCTNS System in compliance to CCTNS standards:
Admin Functions
• Quick view option
• User Login
• Organisation
• Category
• Naxal Status
• Case Status
Input type
• State


• District
• Police Station
• Village
• Zone
• Informant with information details with date & time
segregated in administration higherarcy.
• Users
Organisation functions
• Organisation details /Crime list /List of Naxal
• Naxal Crime Functions
• Investigation details
• Other details
• Naxal Lists
• Attachments
• Naxal Profiles
• Advance Search
Reports
• Accused Naxal Crime
• Police Station – Input
• Description – Input
Application development platform
• OS – Window 2003
• Web Server – Apache 2.0
• Scripting : PHP
• Framework: CakePHP
• Database: MySQL
Extremist
• The system should be able to capture information related to the
Database
suspected extremist group. The system should be able to record the
name of the group, location they are operating from, team leader’s
name, address of team leader, number of members of the group,
record the name of the member and their address, details of the
next of kins. The system should be able to capture the details of the
financer, sympathiser, harbourer, frontal organisation.
Search Module
• Extremist Management involves identification of the suspected
individual who belong to the region, migrated from other region
and other cases so extensive search operation is carried out by the
Para-Military force to identify the suspected person. The system
should be able to search the details of the suspected person. The
system should be able to link with the RTO, Voter ID, and telecom
operator’s database to verify the identity of the person. The system
should be interlinked with the agencies like IB, SSB, Defence
Intelligence, Revenue Intelligence, real-time data sharing with
Telecom Service providers, call Interception and Intelligence of
other state police. Interface with state and central security agencies
should be provided for sharing of information


Force
• The system should be able to keep record of the details of the
Movement
movement of the force. The system should assist the force to get the
geographical details of the location to be visited for the search,
combing and other operation. The system should be able to map the
location of the nearest police station and location of the post of the
force. The system should allow the officer to keep track of different
inspection post and force at the post. The system should allow the
officer to keep track of the movement of the vehicle through the GPS
based system to identify the location of force in different location.
SP Office Module
SI is required to develop this State Specific Application in compliance to the CCTNS standards
and in integrate the same to CCTNS System.
Table 10: Functional Requirements of SP Office Module
HR Management Module
Application The System is developed in VB.net, Web based solution now is being used by
in use 50+ users
Backend: Oracle 10g

OS: Windows 2003 Server
With following functionality:
The system must capture the details relating to the following aspects and
generate reports relating to :
• Rank wise personnel data

• Rank wise list of people who are on suspension
• Rank wise list of people who are scheduled to retire on June of each
year.
• Rank wise vacancy list
• List of people recruited on compassionate grounds.
• The above list is used for recruitment process for each unit of Police.
There is already a master form in the configuration module to capture the basic
details of police personnel. The same form may be customized for capturing

these data and re-used in the HRMS module. The other details are as follows:
•
Employee
• Photograph attached
Master Data
• Property Statements
• Health profile
• Name of Spouse and children with full details
• Name of dependant parents
• Date of Retirement
• Gratuity and pension details
• Caste category- Gen/SC/ST/OBC/EBC (Extreme Backward Class)
Recruitment System must capture the following details for recording the hiring process:
Process:
• Name
• Fathers Name
• Caste
• Religion
• Address
• Date of Birth
• Educational Qualifications
• The recruitment process is based on the reports generated in the point
number one.
Training The system must include the information with regard to:
Basic Training – this must capture information relating to a person. Thus

system must associate the user id based information with all the trainings done
by the person.
Extra Training –this will capture details to group of users within a police unit.
Hence the roles of users must be mapped to various police units like CID, BMP,
Special Branch, SCRB, etc.
Postings Every police personnel with an ID in the system must also capture information
and relating to the past postings served.
Transfers
System will also have provision to record the details of transfers that is pending.
System will give admin role based rights for making changes to the transfers.
Annual Annual confidential Report: Based on all feedback entered about a personnel
Confidential from time to time. The system will generate a report. There will be provision in

Report system based on role, whereby a certain role of users will be able to fill up and
perform self-assessment. While for others, the assessment data entered by user
will move in workflow to a senior officer.
Increments, There will be provision in system to record the details of the pay structure of
Leave etc. personnel. There will be ways to download pay slips as well.
The salary structure must be viewable in the usual format like:
Rs. 10,000-100-15,000-300-20,000
Earned Leave
There must be provision in system to calculate the total leaves, including half
earned leave. There must be a mechanism in the system to define such leaves
and associate the leave structure based on the role/rank of a user in the system.
The system must have provision to reflect the following information in a

tabular/easy view format for a year:
Total Leaves
Leaves Spent
Leave Balance
Carry Forward Leaves from last year.
Encashment of Leaves
Maternity Leave Balance
Paternity Leave Balance
Grievance System should allow dealing hand to create a request for Grievance
Redressal
System should provide dealing hand with an option to choose amongst the
officer whom to mark the request
System should allow dealing hand to add remarks to the service request
System should provide the SP with an option to retrieve the details of Grievance
System should allow SP to add remarks to the Grievance request.
Payroll, Payroll
Arrear etc.
The system should be able to calculate the salary details of the all the police
personnel based on their salary structure.
The system should be able to link with the leaves sub module for the monthly

salary processing in case of deduction in the salary.
The system should be able to link the payroll system currently functioning
under the police department.
Arrear Generation
System should provide clerk with an option to enter the revised basic pay of the
employee.
System should allow the clerk to generate the arrear of an employee from a
selected date based upon revised basic pay.
System should allow clerk to generate & print bills for selected employees with
selected details
System should be able to update the revised salary details into the Employees‟
account.
Bandobast The system should allow the officer for the planning of the Bandobast duties of
Duties the police officials. The system should record the date of allocation of work,
number of police personnel, location of the Bandobast duties and other details.
The system should record the details of the official who will be allocated for the
Bandobast duties.
The system should allow the police officer to report the personnel available on
the day of Bandobast duty.
Other in-house development of Application need to be integrated with CCTNS system or

to be developed a fresh based on the availability of source code, design document etc.
shall be the responsibility of SI. Following are the other applications in use within the
department.
Application Details
in Use
Web Portal Ready to be deployed under public domain
CMS: Drupal Ver. 6
Web Server: Apache
Scripting: PHP
Database: MySQL

Application Details
in Use
Visitors’ Platform used:

Information
System VB6
Database: MySQL
Asset Create/ Modify/ Delete

Management
Stock-in / Stock-out
Maintenance Module to be developed
Vehicle Management Module to be developed
Fuel Consumption / Allotment
Inventory Management Module
Vendor Management module
Analysis, Business Intelligence & MIS Module

Data Capture
This is an additional functionality to CAS state that SI need to develop:
\Application
• System should have the capability to connect with multiple data sources and
types. System should provide access support for all major structured data
sources, including but not limited to relational databases, flat files, and
mark-up languages. System should be able to migrate, synchronize and
replicate data across different operational systems and data sources
• System should support reading and writing of data from message queues as
well as sending and receiving data to and from Web services
• System should ensure cleansing of data before storage. Cleansing should be
applied to legacy data as well as for real time transactional data
• System should monitor data quality in real time to discover when quality
falls below the acceptable limits. System should issue alerts when there is a
need to take corrective action
• System should help in creation of data-marts and data streams
• System should build a library of reusable rules for data migration and
replication or synchronization
Analytics
• System should be able to use data-marts and data-streams prepared using
Application
the Data Capture Module

Analysis, Business Intelligence & MIS Module
• System should support interactive “slice & dice”, pivot table analysis,
visualization
• System should perform trend analysis, forecasting or predictive modelling
and pattern recognition and report via OLAP techniques
• Data will be picked up from multiple application databases to create data
marts and used for analytics
• System should perform at-least the following analytics
o Benchmarking studies
o Risk Analytics
o Risk model development
o Damage and loss estimation
Dashboard &
• System should load, organize, view and save reports based on OLAP cubes
Reporting
and/or relational data from one or more data sources
Application
• System should implement Dashboard for Management Information System.
Dashboard should present key and updated metrics defined by department
in an easy to understand format.
• All users should configure key metrics viewed by them and customize the
data available on their personalized dashboard.
• Dashboard should be customizable and access restricted for the intended
group. The data elements/ reports accessible to an employee should be
viewable to all the employees higher up on the hierarchy.
• System should provide multidimensional & relational data exploration: drill,
rotate, filter, reorganize, sort, toggle totals, export to various target formats
etc.
• System should print reports to PDF or export formatted tables and graphs,
or simply data, to Excel
• System should send selected reports to KM system
• The dashboard should be a visual representation of important metrics as
defined by the department during the system requirements specification
stage.
• Metrics will be tracked and represented in tabular and visual form (charts,
bar graphs, pie charts etc.). The data range would be modifiable by the user
and the changes would reflect on the charts / diagrams.
Common Component and Work flow Module


Common
• System should allow user to fetch requisite information regarding G2C
Component
Services
• System should provide information like:
o Centres for collecting application forms
o Procedural information related to service
o Service fee
o Service levels for the delivery of service
o Process to validate authenticity of the certificate
o Escalation matrix
• System should allow user to upload and update content on information
pertaining to G2C services
• System should automatically publish information on the Jharkhand
Police/CCTNS Portal once uploaded
• System should keep track of contents which have not been updated for a
given period.
• System should communication with the Alerts & Notification component
and alert the users for updating content which have not been updated for a
given period
• System should allow users to fetch requisite Application Forms for all G2C
Services
• System should allow user to upload and update standardized application
forms pertaining to G2C services
• System should automatically publish application forms Jharkhand
Police/CCTNS Portal once uploaded
• System should keep track of application forms which have not been updated
for a given period.
• System should communication with the Alerts & Notification component
and alert the users for updating application forms which have not been
updated for a given period
• System should allow users to register applications in the System by selecting
relevant e-forms
• System should communicate with the Data validation component for
validating entered data
• System should allow users to scan and upload supporting documents for an
application

• System should generate Acknowledgement Identification number once the

application data has been validated and submitted for registration. This
should act as a proof of submission of documents & act as a Reference
number for all further processing / enquiries / escalations.
• System should generate an Acknowledgement receipt and allow user to
print it so that it can be given to the applicant. This receipt should contain
following details
o Acknowledgement Identification Number (AIN)
o Applicant details
o Service Type
o Date of Issue
o Expected date of delivery
• System should detect status updates whenever status of application is
updated
• System should communicate with the Alerts & Notifications component and
alert the user whenever there is a status update against an application
• System should check if applicant’s mobile no. has been registered and will
communicate with the SMS gateway to send status updates directly to the
applicant’s mobile no.
• System should allow user to check status of an application by with the help
of AIN. i.e. will fetch the status of the application based on the AIN
• System should allow citizens to register grievances through Help Desks, PS,
Portal
• System should generate a grievance tracking number just like the AIN. This
number should act as the reference no. for tracking the status of grievance
registered
• System should allow user to track the progress of the grievance registered
by entering the grievance no.
• System should communicate with the grievance redressal module for
further routing the grievance to appropriate authority
• System should communicate with the status tracking component to alert on
status updates regarding the progress of grievances
• System should allow searching in databases for Verification
• System should allow to generate alert to concerned officials for Physical
verification
• System should allow to upload/prepare and submit verification report

• System should allow user to update and submit acceptance reason

• System should allow to update status against AIN
• System should generate alert for acceptance
• System should allow to print acceptance report
• System should allow user to update and submit rejection reason
• System should allow to update status against AIN
• System should generate alert for rejection
• System should allow to print rejection report
• System should alert delivery officer after acceptance
• System should alert citizen to collect certificate/document
• System should allow to generate certificate with digital signature and print
the same
• System should allow movement of file/request on various parameters
• System should provide facility to mark the application to pre-defined
hierarchy
• System should allow FIFO principle for taking action on application
• System should alert for delay in action
• System should provide facility to mark the application to other officer
• System should provide facility track File Movement & Receipt/ Dispatch of
Government orders, Circulars & Notifications.
Collaboration Module
Knowledge
• System should allow user to submit learning documents to the knowledge
Management
management system; digital versions of archived documents should be
incorporated into the system
• System should allow user to define tags for the submitted resource
• System should interface with Business Intelligence and Data Mining
Application for archiving the Data Mining reports
• System should allow user to view data in logical sections in the KM related
to tagging
• System should interface with Grievance Management System & capture
feedbacks of citizens
• System should allow user to search documents using multiple search

criteria
• System should present results in order of relevance
• System should allow storing of document (Image & Metadata)
• System should support for viewing a large number of file formats without
the need of having the parent application. The system should support all
commonly used file formats as MS Office, Acrobat, TIF, JPEG, GIF, BMP, etc.
• System should provision to edit the document Metadata
• System should provide versioning of the document
• System should provision for marking comments
• System should provision for archival of data on pre-defined parameters
• System should allow role based access to the documents
• System should allow users to view and participate in forums
e-mail/
• System should allow users to display a specified number of messages in the
Message
mini-view
• System should extend the E-Mail facility to SB/SIB/CID/Training and all
other section of Police
• System should allow users to display current email messages from Inbox
• System should allow users to delete, reply, forward and compose email
• System should allow users to compose new email and retrieve to, cc and bcc
addresses from the directory
• System should allow users to read email messages
• System should allow users to check the server for new messages
• System should allow users to save email drafts
• System should allow users to save a copy of emails that have been sent
• System should allow users to attach and download email attachments
• System should allow users to create and delete folders
• System should allow users to move, copy or rename folders
• System should allow users to move messages between folders
• System should allow users to search for messages
• System should allow users to specify the number of messages to display on
each page
• System should allow users to add email sender address to personal address
book

Alerts &
• System should allow users to view tasks
Notification
• System should allow users to filter between all, not complete or complete
tasks
• System should allow users to search tasks by keyword
• System should allow users to add a new task
• System should allow users to mark a task as complete
• System should allow users to add, edit or delete tasks
• System should allow users to specify the number of tasks to display on the
mini-view
• System should allow users to specify the number of tasks to display on each
page
• System should allow users to view a day, week, month or year view of
appointments
• System should allow users to specify the default mini-view (day, week or
month)
• System should allow users to add appointments with repeating options
• System should allow users to set appointment importance (normal, low,
high)
• System should allow users to create meeting requests
• System should allow users to edit or delete appointments
• System should allow users to search appointment by keyword (subject
and/or description)
System should allow users to display upcoming or past appointments
Call Centre Module

Call Centre
• All Citizen & Employee Call should land on specific number (PRI)
Management
provisioned by Department
Module -
Complaint • IVR should be playing the Language Choice Menu and Type of Caller
Management (Citizen/Department Employee) and the Call would be routed to the
for Citizen & respective agents based on the mutually agreed and documented call Flow.
IT Help Desk • The hold music and the hold announcements should be played if lines are
for Police busy provided.
Personnel
• The Caller would input all detail and System Should generate unique
Acknowledgement Identification Number (AIN)

Call Centre Module
• The status of Complaint/Grievance should be updated to caller whenever

AIN is provided
• The System should send the SMS/e-Mail for feedback and same should be
stored
• Real time monitoring should be available on the Call
• Sample % of the Voice Calls should be recorded for quality test & training.
• The Performance measurement of calling agent and devices like call drop,
average time of answering, customer satisfaction should be generated
• All the recorded calls will be retained online for particular time as agreed by
department.
Data Transfer Module

State SCRB- • Data Transfer Module shall provide all the functionalities mentioned in
NCRB Data CCTNS FRS by NCRB. There are no state specific additional functionalities
Transfer and envisaged.
Management
Service
User Assistance Module

User help and • User Assistance Module shall provide all the functionalities mentioned in
Assistance CCTNS FRS by NCRB. There are no state specific additional functionalities
Service envisaged.
User
feedback
tracking and
resolution
Service
Security Module
User Access • Security Module shall provide all the functionalities mentioned in CCTNS
and FRS by NCRB. There are no state specific additional functionalities
Authorization envisaged.
Management

Security Module
Service
Activity Log
Tracking and
Audit
Services

9.2 NON FUNCTIONAL REQUIREMENTS

The non-functional requirements relating to performance, availability, deployment,
implementation, operations and others are listed in the subsequent subsection. Based on the
assessment of the requirements listed below:
Sl. 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 modeller 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 multiple operating systems.
SI should submit list of operating systems with which products are certified to
run.
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 software based load balancing for scalability
and performance
NFR 5 Software architecture must support flexibility in adding functionalities or

applications.
NFR 6 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 7 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 8 Hardware architecture must provide redundancy and high availability capabilities
at the hardware level; this includes servers, network components, and storage
system.
NFR 9 All servers and systems must be configured with no single point of failure.
NFR 10 Hardware architecture should be capable of consolidating several applications /

workloads in a number of servers as required.
NFR 11 Hardware architecture servers must be placed within proper network locations
to satisfy the security requirements of the Solution.
NFR 12 Hardware architecture must include Storage Area Network (SAN) and backup
solution to support all portal hardware and software components.
NFR 13 SIs 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 14 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 15 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 16 The test, development and staging environment should include required


workstations, desktops and tools appropriate to support development, testing,
staging and deployment.
NFR 17 The development, test and staging environments must include similar operating
systems, software components, products, and tools to those of production
environment.
NFR 18 The development, test, and staging environments should be independent logically
and physically from the production environment and of each other.
NFR 19 The development environment should be used for development and should be
configured to allow access for developers’ workstations.
NFR 20 The staging environment should be used for functional and user acceptance
testing, stress testing, and performance benchmarking.
NFR 21 The test environment should be used as a testing environment of System Solution
and its software components and products.
V. Security Requirements
NFR 22 It should have a secure solution at the hardware infrastructure level, software
level, and access level.
NFR 23 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 24 Encryption: It is required to ensure confidentiality of sensitive information and

data of users and portal information.
NFR 25 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. The proposed


solution should have SSO capabilities for web based applications.
VI. Monitoring and Management Requirements
NFR 26 The Central System Solution should provide monitoring and management of the
entire Solution including all software components ,application and IT assets
NFR 27 The monitoring and management should monitor health of software and
hardware infrastructure running System Solution covering operating system,
database, software components, applications, servers, network components, and
other related software and hardware components. It should provide proactive
monitoring, alerting and reporting. The management tool for managing database,
application server & custom application developed should be unified & should
have capabilities like provisioning & patching
a) SI shall design an appropriate policy and architecture for implementation of
the EMS solution.
b) SI shall provision industry standard EMS for the Application Performance
monitoring ( based on real time end user transactions & application
performance measurement), Server & Database Performance Monitoring
(Availability & Performance), Network Fault Monitoring and for all the
services of the project.
c) SI shall develop a plan for implementation of EMS at Police locations and data
centre sites.
d) It is expected that SI will draw knowledge from industry leading practices and
his experiences to implement the EMS solution that is best suited for CCTNS
Project. SI shall come up with the blueprint for an EMS policy and cohesive
EMS architecture and obtain approval from the department prior to actual
implementation.
e) SI shall undertake installation, configuration and implementation of all the
components of the EMS.
f) SI shall be responsible for designing and implementing the workflow required
for the IT helpdesk. The requirement analysis shall be approved by Police
Department prior to commencement of implementation.
g) SI shall ensure that the EMS solution is properly installed and configured in all
the servers / desktops and the assets are properly tracked and controlled.
h) SI shall design and implement monitoring and alert mechanisms for all the
equipment and components in the datacentre.
i) SI shall design appropriate backup and archival strategies / policies in
accordance with CCTNS security policy for managing data related to EMS.
j) There shall be provision for SLA management tool either integrated with the


EMS or separately.
k) SLA management tool shall be able to monitor all the service levels including
that related to network, systems, database and application defined in the
service level agreement
i. SLA management tool shall automatically document problems,
interruptions and consolidated violations of the SLA
ii. SLA management tool shall enable authorized users to have a
unified view of the entire EMS system SLA at single console along
with integrated performance and reports for troubleshooting,
diagnosis, analysis and resolution purposes such as:
• Trend Reports
• Top N Utilization reports
• What-if capacity prediction reports
Application Performance Management System

• The solution must determine if the root cause of performance issues is inside
the monitored application, in connected back-end systems or at the network
layer from a single console view
• The solution must proactively monitor 100% of real user transactions; detect
failed transactions; gather evidence necessary for triage and diagnosis of
problems that affect user experiences and prevent completion of critical
business processes
• The solution must be able to provide root-cause probability graphs for
performance problems showing the most probable root-cause area within
application infrastructure.
• The solution must allow monitoring granularity of no more than 15 seconds
for all transactions.
• The solution must identify any changes to application configuration files (.xml,
properties etc.), File system or application code and be able to correlate
changes to application performance dynamically in production environments.
Integrated Performance Management System for Network, Systems and

Databases:
The Network Performance Management consoles must provide a consistent
report generation interface from a single central console. This central console will
also provide all required network performance reports (including latency,
threshold violations, packet errors, availability, bandwidth utilization etc.) for the


network infrastructure.
• At-A-Glance Reports to present a single page report on vital device statistics
like Backplane Statistics, Buffer Statistics, and CPU Utilization etc.
• Top N Reports to present a list of elements that exceed / fall below a
particular threshold value.
• What-If Reports to perform capacity planning by observing the effect of
changes in capacity & demand
• The system must have a report authoring and custom option built-in which
will enable complete customization flexibility of performance reports for
network devices and monitored servers.
• The system should provide a live trend diagram that continuously charts
critical statistical performance variables as they are collected and displaying
the resource utilization levels of various critical devices and links in the
managed infrastructure.
• The system should provide a live exceptions list displaying the various health
and threshold exceptions that are occurring in the managed infrastructure.
• The traffic monitoring system must be able to track 100% of all flow traffic on
the network and identify malicious behaviour with all IP conversations
• The user must be able to generate reports from the long term database based
on specific thresholds defined by the user where the threshold can be
compared to rate, utilization or volume of every monitored interface as a filter
for inclusion in the report.
• The solution should support monitoring of servers including monitoring and
reporting for following parameters:
• Processors, File Systems, Log Files, System Processes, Memory, CPU,
NT Processes, Page Files
• The database performance management system shall integrate network and
server performance management systems and provide the unified view of the
performance state in a single console. It should be able to automate
monitoring, data collection and analysis of performance from single point.
Network Fault Management System:

• The system should provide topology, discovery & inventory of heterogeneous
physical network devices like Layer-2 & Layer-3 switches, Routers and other
IP devices and do mapping of LAN & WAN connectivity with granular visibility
up to individual ports level.
• The proposed solution must provide a detailed asset report, When a report is


run the administrator should have an option of specifying the number of
consecutive days the port may be “unused” in order for it to be considered
“available”.
• The system must use advanced root-cause analysis techniques for
comprehensive analysis of network faults.
• The system should be able to clearly identify configuration changes as root
cause of network problems. The solution must able to perform “load & merge”
configuration changes to multiple network devices
• The system should have the ability to monitor and visualize a virtualized
system infrastructure by discovering and monitoring virtual machines and
providing ability to depict the logical relationships between virtual servers
and virtual machines.
• The System should be able to detect virtual server and virtual machine
configuration changes and automatically update topology.
• The System should be able to monitor Quality of Service (QoS) parameters
configured to provide traffic classification and prioritization for reliable traffic
transport.
• The solution should be able to discover and model configured QoS classes,
policies and behaviours.
• The solution should be able to map and manage MPLS – VPNs by automating
the provider connection resolution and monitoring the service health with an
option to auto-provision service assurance tests to proactively calculate the
availability of remote sites
The service management system should be able to provide a detailed service
dashboard view indicating the health of each of the departments / offices in the
organization and the health of the services they rely on as well as the SLAs. The
Service Dashboard should provide a high level view for officers and other users of
the system. The system should also provide an outage summary that gives a high
level health indication for each service as well as the details and root cause of any
outage.
Integrated System
• The console and associated management system should be deployable in a
separate physical web-server to reduce the load on the primary management
server. The security must be able to permit or restrict operator access to
different areas of information based on user security rights assigned by the
administrator.
• The Network Management System should provide unified workflow between
the fault and performance management systems including bi-directional and
context-sensitive navigation, such as;

• Navigate from the Topology View to At-a-Glance or Trend Reports for

any asset
• Navigate from the Alarm View to At-a-Glance, Trend or Alarm Detail
Reports
• The fault management system should be able to attach an asset identifier
when submitting a helpdesk ticket. In case the asset is not found in the
helpdesk database, it should be automatically created prior to submitting the
ticket.
• The performance management system shall integrate network & system
performance information and alarms in a single console and provide a unified
reporting interface for network components. The current performance state
of the entire network & system infrastructure must be visible in a central
integrated console.
• The Fault Management Solution must integrate with Server Monitoring
Solution to provide Consolidated Alarm view from Single console. Monitored
Server should be discovered as server model and configured from proposed
fault management console itself in order to monitor metrics like memory, CPU
etc.
The Application Performance Solution should be able to integrate with Fault
Monitoring Solution to forward Application Performance Threshold violation
alarms in the proposed Fault Management Console as well as Server Monitoring
Event Management console.
VII. Performance and Scalability Requirements
NFR 28 SI is required to design the overall System Central Solution with high
performance and scalability to handle increasing number of users.
NFR 29 SI is required to deliver System Solution that provides measurable and acceptable
performance requirements for various user groups, channels and bandwidths.
NFR 30 SI is required to provide optimal and high performance Portal Solution satisfying
response time for slow Internet connections and different browsers.
The average page view time is estimated to 1.0 Sec. The maximum acceptable
response time is estimated at 2.0 Secs.
The average size of session per user basis may be estimated at 20.0 mins
SI is expected to use their experience and follow industry averages to estimate
the maximum CPU utilization during peak load hours
The Portal platform should provide support for portal standards such as JSR 168,
WSRP 2.0 and JSR-170, JSR227


The solution should support all widely used browsers and OS as per industry
standards. There should be no tie-in to any particular OS or browser.
The Portal platform should support deployment on Linux, Unix and Windows.
Ability to provide single information view of the data coming from multiple
sources such as web service, XML, SQL source, Web Pages and Spread sheets. This
would need ability to connect to multiple sources, defining rules and filtering
conditions, applying visualization and then publishing in portal
Portal architecture should support both .NET and Java platform
Portal search should support both content, keywords, Full text & people search
The portal platform should have the ability to surface data managed by packaged
and custom applications like ERPs through portlets.
The portal platform should provide support for Digital certificates and Secure
Interface for confidential transactions as required.
Portal should support bilingual (Hindi & English)
Business User Administrations – The portal solution should provide browser-
based tools that would let business-level portal managers intelligently assemble,
configure, and manage enterprise portals. The administration tools should
provide granular control and delegation of administration tasks for custom role-
based management.
The portal solution should have analytics console for accessing portal metrics.
The analytics console should be available as an integrated application so that the
product is easy to learn and easy to deploy.
The portal solution should provide secure and controlled access to the analytics
console. Only portal administrators should be able to access the console without
exposing data that might be sensitive or private.
Portal offering should be in the leader quadrant of Gartner Analyst report.
Personalization of home page using drag & drop functionality.


10 CHANGE MANAGEMENT AND CAPACITY BUILDING
10.1 OBJECTIVE OF CHANGE MANAGEMENT

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 initiative, to be designed & implemented by SI, shall focus on addressing
key aspects of Project including building awareness in Police personnel on benefits of new
system, changes (if any) to their current roles & responsibilities, addressing the employee’s
concerns & apprehensions w.r.t. implementation of new system and benefits that are planned
for the employees.
It is required that if SI doesn’t operate in the Change Management, Communication and Training
domain then he collaborates with/ hires services of a specialist agency who will be responsible
for complete Change Management, Awareness and Communication implementation and
monitoring, on the lines suggested below:
10.2 SCOPE OF CHANGE MANAGEMENT

The State Nodal Agency shall form various stakeholder groups to address the Change
Management Initiative. Stakeholders are all those who need to be considered in achieving
project goals and whose participation and support are crucial to its success. A key individual
stakeholder or stakeholder group is a person or group of people with significant involvement
and/or interest in the success of the project.
Stakeholder analysis identifies all primary and secondary stakeholders who have an interest in
the issues with which the CCTNS project is concerned. The stakeholder groups will be the set of
core users (Change Agents) who will directly participate in the awareness and communication
initiatives, workshops, and provide feedback to the District Mission Teams and State
Empowered Committee.
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, and DIG) responsible for Crime, Law
and Order etc. who are directly impacted by the CCTNS with respect to
receiving/analysing 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, ASI,…) 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,…) 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.
SI is required to incorporate the cost of all resources required for design, execution and
management of Change Management Plan for project, in its overall project cost.
Stakeholder Analysis / Impact Assessment
The SI shall perform the impact assessment, in light of new system, to identify the changes to the
current functioning, organization structure, roles & responsibilities, current capacities (training
to the existing resources or deployment of additional resources) etc. In this context, the SI is
required to perform a baseline assessment of the communication requirements of various
stakeholders to understand what stakeholders currently know about the initiative; what they
need and want to know; how they prefer to receive information about the project. The SI shall
steer the communication efforts, for both internal & external stakeholders, for the project and
State will provide necessary support and guidance to SI for the same.
A detailed study needs to be carried out to understand the impact on each of the stakeholder
and the influence that they can exercise on their respective areas of control, for making CCTNS
successful. System Integrator (SI) shall ensure that the all stakeholders are aligned to the
program and their concerns are documented and addressed. This activity would ensure that the
Communications and Awareness Plan is in sync with the overall project's deployment schedule
and to develop and deliver effective stakeholder interventions to individual stakeholders and
stakeholder groups.
The stakeholders are distributed across the State and the SI should ensure that innovative and
effective methods are used to conduct the Stakeholder Management activity which should cover
the following but is not limited to points mentioned in the table below.
The SI would be responsible for the following activities:
S.No Requirements Details Frequency

1 Stakeholder Analysis • SI shall be responsible for One time activity
interviewing stakeholders, analysing Given the number of
data and recommending action plan stakeholders, SI will
to address concerns related to the use innovative ways
CCTNS project. to interview/interact
with Stakeholders
• Finalize questions to understand including,
stakeholder concerns, what success Phone/VC/Face to
means for them, influence on face/Focused Group
project, what is the impact of the etc. so as to reduce


program on the stakeholder etc. costs of interaction.
• SI shall be responsible for refreshing

the stakeholder engagement plan in
consultation with the State’s Nodal
Agency, whenever the project scope
or the program implementation
timelines undergo a change.
2 Develop Stakeholder SI shall develop content – discussion Recurring activity

Engagement scripts, presentations or videos to over the entire
Content explain the objectives of the program, duration of the SI
what is in it for them and their
people, what the benefits are.
Other Requirements:
• SI shall cover all the identified stakeholders and stakeholder groups identified in all the
higher offices, State Headquarters, District Headquarters, SCRB, DCRB and Police
Stations.
• SI will recommend additional Stakeholder or Stakeholder Groups – Internal and External

who need to be covered under this activity.
• SI shall also cover the extended teams and should not limit to the direct identified
stakeholders.
• SI shall come up with innovative ways of stakeholder engagement in addition to the

video conferencing, one-on-one meeting and teleconference.
• SI shall ensure that the stakeholder engagement activity is a continuous activity and
buy-in and commitment of the stakeholders are key drivers for the success of this
project.
• SI shall make recommendations to best manage this process.
• SI shall also develop Job Aids, an important component of sustaining the change by
ensuring that there is enough support material available to maintain the performance of
the transformed workforce. A job aid is a repository for information, processes, or
perspectives that is external to the individual and that supports work and activity by
directing, guiding, and enlightening performance. Since job aids are external to the
individual and would be applicable to those set of activities which are complex and
difficult to memorize. For example, in the beginning stage, searching of records in the
CAS might require a Job Aid. However, as the time progresses and user becomes more
thorough and comfortable with the new system Job Aids for such activities may no

longer be required. Also, for more complex activities such as generating a MIS report
from the system might require a Job Aid for a much longer duration. These Job Aids must
be revised on periodic basis.
Assess change readiness
The SI shall perform an assessment, based on the Impact Assessment, to identify to what extent
the State is currently equipped for the change, what are the key potential blockers and enablers
within the structure, processes and staff for implementing the changes.
The Change Readiness Assessment should be used to determine the changes, requirements,
concerns, type and level of resistance and expectations emerging as a result of the CCTNS
program. The analysis should be performed for the whole state for each of the identified
stakeholders impacted by CCTNS.
Assessing change readiness will help the change team to:
• Pinpoint where risks are likely to occur
• Clarify issues associated with CCTNS
• Identify potential responses to change
• Identify and target where change activities are most needed
Change Readiness Survey shall involve collecting information about affected groups within the
organization to determine how ready they are to accept and assimilate forthcoming changes. At
least four Change Readiness Surveys are recommended during the project to measure if the
project is on track and is aligned to the intended end state objectives.
SI shall conduct 4 Cycles of Change Readiness Survey:
• 1st Cycle shall measure readiness to change
• 2nd & 3rd Cycle shall measure progress of change
• 4th Cycle shall measure the State Police Department’s acceptance to change, potentially
on the job.

1 Develop Change • SI shall be responsible for developing
Readiness Survey the objectives, scope, and process for
approach change measurement
• SI shall also finalize the target

audience, timelines, methods of
change measurement One time activity


2 Develop and • SI shall develop or configure an
Configure appropriate change measurement
Change Recurring Activity (At
instrument that is convenient for
Measurement audience and easy to assimilate for least 4 times in 2 years)
Survey/ CM Team
Instrument
• SI shall configure the change
measurement instrument based on
the requirements of the project
3 Select Sample • SI shall select the sample for the One time activity
Audience and survey and should ensure that the followed by review of
Administer the targeted audience is a fair mix sample audience for
survey representing all State Offices, each subsequent cycle.
solutions and all levels of the
organization.
• SI shall be responsible for

administering the survey- paper
based or electronic, as the case may
be.
4 Analyse reports • Analyse the result of the survey and Once for each survey
and generate survey reports (Higher
devise corrective Office-wise, State Headquarters -
action plan wise, District Headquarters - wise
and Police Station-wise) to be shared
with respective leadership team.
• Identify the key patterns that emerge

out of the survey for all groups of
stakeholders
5 Share the result • SI shall share the results of each Once for each survey
with survey with audience identified by
the leadership State’s Nodal Agency and validate
and refresh the corrective action plan with their
change inputs.
management plan • SI shall refresh the Change
Management Plan with new
interventions in consultation with
State’s Nodal Agency’s Change
Management Plan

Other Requirements:
• Change Readiness Survey should be deployed at significant milestone along the project
implementation timelines but not limited to four in number.
• SI should conduct at least four change readiness surveys- First survey shall be a baseline
survey and should be deployed at the beginning of Phase-I. Second survey should be
conducted after 3-4 months of the first survey. Third survey should be completed at
least a month before the go-live. Fourth survey should be conducted at the beginning of
Phase-II.
• Proper mechanism for survey validation and verification should be devised. The survey
result shall not be considered as valid if the participant audience is less than 60% of the
target audience.
• SI should ensure that the sample selected for the change readiness survey is a fair mix
representing all solutions, State Offices and levels of the Organization. SI shall utilize
both computer based and paper based method of survey deployment
• SI should ensure that the change measurement report gives insight to the leadership
team if the change is on track or off-track and the corrective action plan for desired
result. Report should bring forth results for higher offices, State Headquarters, District
Headquarters, SCRB, DCRB and Police Stations.
• Change management plan should be revisited and revised based on the survey results
and corresponding corrective actions in consultation with State’s Nodal Agency’s
Change Management Team.
Develop the change management plan
The SI shall design a road map to achieve/implement all the change management initiatives,
which are essential for success of the project. The plan shall be more than an implementation
plan; and shall contain change milestones based on the change vision, benefits milestones,
benefits tracking mechanisms, actions to build commitment and actions to ensure business
continuity. The plan shall also define change governance – including appropriate decision
making and review structures.
Implementation of Change Management Plan
SI shall take lead in assisting State in implementing the change and State in turn shall provide all
the necessary support for successful implementation of the change management plan developed
by the SI. The SI shall be responsible for all the costs involved in design and implementation of
the change management plan for Project. The SI shall proactively work with State to address the
project needs and gain buy-in and involvement of all the stakeholders in achieving the change.
During the whole exercise, stakeholders’ awareness, understanding and commitment to new
ways of working should be raised. Stakeholders should also be encouraged, where appropriate,
to contribute to or participate in the project to engender a joint sense of ownership.
Communication and Awareness

Communication and Awareness aims at engaging officers of the police force in two way
interactive communications about the changes so that all individuals in the State police
department understand the target vision and strategy for moving forward. The purpose of
communication plan is to educate and involve all audience groups to build understanding and
ownership of the CCTNS Project. The communication plan also ensures that the CCTNS project
provides relevant, accurate, consistent and timely project information to relevant stakeholders
to promote and gain support for CCTNS Project. This plan provides a framework to manage and
coordinate the wide variety of communications that take place during the project covering who
will receive the communications, how the communications will be delivered, what information
will be communicated, who communicates, and the frequency of the communications.
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.
Sl Requirements Details Frequency

1 Develop and • SI shall facilitate an exploration of Once
Validate detailed specific objectives; i.e., who must
communication understand what, by when, and why
plan with respect to the project, to
ensure successful uptake of the
project.
• SI shall prepare a detailed

communication plan for the
program in line with the
implementation timelines of each
solution.
• SI shall ensure that all the impacted

audience is covered in the
communication plan and the most
appropriate mode of
communication is being used to
deliver the messages to the target
audience.
• These key audiences are not the

only ones who will receive
information, but their
demographics will shape the
strategy in terms of message and
vehicle selection.


2 Develop • SI shall be responsible for Recurring Activity over
Communication developing the content for the entire duration of
Content communication material in English, the SI
Hindi language.
• SI shall ensure that the

communication is simple,
continuous and consistent.
3 Deliver • Prior to implementing the plan, the Recurring Activity

Communication SI shall obtain the necessary sign- (once a month) over the
Events offs from State on the entire duration of the SI
Communication Strategy & plan and
make necessary changes as
recommended by State.
• SI shall determine who needs to

approve communications prior to
dissemination, 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.


4 Measure • After implementing the Once in six months
Effectiveness communications program, SI shall
of Communication seek feedback on and measure the
and Update Change impact of the communications
Management Plan program.
• SI shall evaluate the effectiveness of

the communication by electronic or
paper based survey or focused
group discussion and develop an
action plan to improve the
effectiveness of communication.
• SI shall refresh the Change

Management Plan in consultation
with State’s Nodal Agency’s Change
Management Plan.
• Through feedback, SI shall assess

which messages have been
delivered most clearly; which
vehicles are most effective; and
whether the appropriate target
audiences have been identified.
Based on such assessment, SI shall
update the communication strategy
& plan and
shall ensure that objectives of
communication program are
ensured, which further should lead
to successful uptake of system.
Other Requirements:
• SI shall work with the identified internal change agents (identified from the District
Mission Teams and State Empowered Committee) 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 vernacular medium using all available
channels

• The SI shall conduct Communications & Awareness Campaigns for each Technology
Solution offered in CAS (State) being implemented through various means – Print,
Electronic, Face to Face, Audio/Visual etc.
• SI shall align communication content, timing and delivery to the deployment

phases/plan of each solution.
Change Management Workshops
SI shall conduct Change Management workshops build appreciation of change management and
develop change leadership across the stakeholder groups. SI shall define the requirements
based on the detailed analysis and design the necessary content (reading material,
presentations) in English, Hindi, and Local Language (if different) 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/ASI/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.
Following is the indicative list of the training programs that needs to be administered to the
group of officials as identified above. The overall responsibility of administering the training
program lies with the SI.
1. Awareness and sensitization of benefits of IT
2. Basic Computer Awareness & Role based training for application users
3. Trainers Training
4. System Administration & Support Training
Table 11: Program specific trainee estimates
Sl. Training Program No. of Police Personnel
1 Awareness and sensitization of benefits of IT 6,596
2 Basic Computer Awareness 11,777

Sl. Training Program No. of Police Personnel
3 Role based training for application users 23,777
4 Training of Trainers 130
5 System Administration & Support Training 146
Total 42,426
The SI shall be responsible for the all the training activities as part of the End User and Train the
Trainer Training.
10.3 CAPACITY BUILDING

Capacity Building is a highly critical component of CCTNS. The objective of CCTNS Capacity
Building (CB) initiatives is to empower the direct users and other stakeholders of CCTNS to
optimally use CCTNS and enhance outcomes in crime investigation, criminals tracking and other
core police functions; and also ensure a smooth functioning of CCTNS.
The System Integrator would render CB services in both areas, as per the “bundling” approach
adopted for CCTNS. The SI holds the responsibility for creation of training material, designing
the training programs and their delivery to the target group.
Building capacities at various levels is critical to the successful implementation of the

recommended IT initiatives. Also, the training programs would cover at minimum general/basic
computer awareness programs in addition to CCTNS-specific programs in order to ensure
adoption of the system at the police station level.
The break-up of the police force for providing training in the Jharkhand is provided below:
10.4 INFRASTRUCTURE AVAILBLE FOR CAPACITY BUILDING
Table 12: Estimated Training requirements
Group Officers No. of Police Personnel
A Covers all senior officers including IG, SP, ASP & CoP 65
B Covers all Police Inspectors, SIs and ASIs 6,531
C Covers all Head Constables, Constables and clerks 23,777
Total 30,373
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 will have 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 will have the responsibility for creation of training material, designing the training
programs and their delivery to the target group.
The SI will have an access to 24 District Training Centres (DTC) located in SP office of
each district along with 5 Police Training Centres & 1 training centres at SCRB.
10.5 OVERALL TRAINING PLAN

SI shall be responsible for finalizing a detailed Training Plan for the program in consultation
with State Nodal Agency covering the training strategy, environment, training need analysis and
role based training curriculum. SI shall own the overall Training plan working closely with the
State Nodal Agency’s Training team. SI shall coordinate overall training effort.
Develop District-Wise Training Schedule and Curriculum
System Integrator shall develop and manage the District-Wise training schedule in consultation
with State’s Nodal Agency, 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 the specific needs and the objectives of CCTNS, training programs should be organized
by the SI.
Following is the indicative list of the training programs that needs to be administered to the
group of officials as identified above. The overall responsibility of administering the training
program lies with the SI.
1. Basic IT skills and use of computers to creating awareness about the benefits of ICT and
basic computer skills
2. 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.

3. “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.
4. System Administrator training: a few members of the police staff with high aptitude would
be trained to act as system administrators and trouble-shooters for CCTNS.
5. Customization of the Training Manuals, User Manuals, Operational and Maintenance

Manuals provided along with the CCTNS CAS Software
6. Design and development of the Training Manuals, User Manuals, Operational and
Maintenance Manuals for the modules developed at the State level.
The indicative training content for the training programs under capacity building is listed below:
Table 13: Indicative Training Content
Training Type of Training Training Content Number of

No. Days
1 Awareness and This module shall cover Principles of e- 2
sensitization of governance, NeGP & CCTNS. It shall also
benefits of ICT cover the advantages of use of ICT in Police
Department.
It shall briefly cover the technology trends

and how it can be put to use by use of live
examples of ICT use across the world
2 Basic computer This module shall cover the fundamental 9
awareness concepts of Computer, Internet, Peripherals,
System software and Application software
It shall also cover the use of MS Office suite

in detail (Word, Excel, PPT, Database)
email/ internet searching
It can also touch upon use of office tools
such as printers, fax machine, copiers and
scanners as well as basics in use of
computers (checking network connections,
etc.).
Role based system This module is required to train the 12
training on CCTNS Constables, Head Constables and officers till
Application SHO rank at various levels in operating the
Software CCTNS application. The training is to be
provided to the police staff depending upon
their role and responsibilities in the service
workflow. Training would include
mechanism for demonstration, practical
exercises and evaluation of trainees. During
this training, the trainees could also be
asked to carry out the routine functions
using the software.

Training Type of Training Training Content Number of

No. Days
3 Trainer's training This training is provided to a select audience 14
across groups who can act as Master
trainers and those who can train their
colleagues
4 Network Skills in Troubleshooting vis-à-vis 7
Administration application, standard software and
support and networking (for those with the aptitude
Trouble Shooting and/or prior training)
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 Hindi and English language. 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 designated District
Headquarter Training Centres. Role-based training for the Senior Officers will be carried out for
a suitable location in the State Police 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)

• Instructor Demonstrations (CAS - Application training environment)
• Hands-on Exercises (CAS - Application training environment)
• 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, and 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 trouble-shooters
with basic systems maintenance tasks including hardware and network.
Deliver Training to Trainers (Internal and Trainers from the Training Colleges)
SI shall help State’s Nodal Agency 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,
Training of Trainers 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 analysing 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.
HANDHOLDING SUPPORT
The System Integrator will provide a maximum of 240 qualified and trained persons for the
entire project period who shall be utilized to handhold the staff in the police station / higher
office and ensure that the staffs in that police station / higher offices are able to use CCTNS on
their own by the end of the handholding period. Handholding support would be required only
after the successful commissioning of Core application and the necessary infrastructure and
completion of capacity building and change management initiatives in respective police stations
/ Higher Offices.
The SI is required to submit manpower deployment plan for handholding support commencing
post Go-Live.
Item No of Police Locations Period
Full project
period,
710 estimated
Handholding man months
Support* 5,730
*Resources provided must be DC/ PGDCA qualified and should undergo 2 weeks training on
computer hardware and networking before reporting at Police Stations/higher offices.

11 ANNEXURE
11.1 Annexure 1 – Contact Details of Key Officials
Name Designation Contact

Mr. B.B. Pradhan, IPS IG, Provision Jharkhand Police Headquarter
Campus, Ranchi Pin 834004
Mr. S.N. Pradhan, IPS Nodal Officer CCTNS Project Special Branch Building,
and IG, Special Branch Jharkhand Police Headquarter
Campus, Ranchi Pin 834004 e-
Mail Id: cctnsjknd@nisg.org

11.2 Annexure 2 – List of all Police locations & Network Connectivity Requirement
Figure 4: Network Connectivity Requirements
• It has been decided that connectivity for all the police stations and higher offices will be
provided by BSNL.
• SI will have to provision demand based VSAT connectivity limited to max. of 400
connections to Police Locations
• MPLS network to connect 37 higher offices, 119 through V-SAT and the remaining 557
sites to be connected through VPN on Broadband.
• SWAN will be the backup network wherever available
• The network will ultimately graduate to MPLS for all sites with SWAN (JHARNET) as
backup
• SLA of 99% uptime would be provided for MPLS connectivity. SLA for the sites
connected through VPN on Broadband will be 97%

Table 14: Police Station wise Connectivity & Electric Power availability status
Type of Primary
Power
BSNL's GSM connectivity
Name of Police availa
S.No. Name of District Connectivity Proposed by
Station bility
available BSNL(MPLS,VPN,VPB
(Hrs.)
NoBB,CDMA,VSAT)
1 Bokaro Balidih Yes VPNoBB 4 -5

2 Bokaro Bermo Yes VPNoBB 4 -5
Bokaro Thermal
Bokaro Yes VPNoBB
3 PS 4 -5
4 Bokaro BSCity Yes VPNoBB 7- 8
CHANDANKIYA
Bokaro Yes VPNoBB
5 RI 4 -5
6 Bokaro Chandrapura Yes VPNoBB 4 -5
7 Bokaro CHAS Yes VPNoBB 7- 8
CHAS
Bokaro Yes VSAT
8 (MUFFASIL) 4 -5
9 Bokaro Chatrochatti Yes VSAT 4 -5
10 Bokaro Dugdha Yes VPNoBB 4 -5
11 Bokaro Gandhinagar Yes VPNoBB 4 -5
12 Bokaro Gomiyo Yes VPNoBB 4 -5
13 Bokaro Harla Yes VPNoBB 4 -5
14 Bokaro IEL Yes VPNoBB 4 -5
15 Bokaro Jageswarbihar Yes VSAT 4 -5
JARIDIH(JAINA
Bokaro Yes VPNoBB
16 MORE) 4 -5
17 Bokaro KASMAR Yes VPNoBB 4 -5
18 Bokaro Lalpania Yes VPNoBB 4 -5
19 Bokaro Mahila Thana Yes VPNoBB 7- 8
20 Bokaro Mahuwatarnd Yes VSAT 4 -5
21 Bokaro Marafari Yes VPNoBB 4 -5
22 Bokaro Nawadih Yes VPNoBB 4 -5
Penknarayanpu
Bokaro Yes VPNoBB
23 r 4 -5
24 Bokaro PETERWAR Yes VPNoBB 4 -5
25 Bokaro PINDRAJORA Yes VSAT 4 -5
26 Bokaro SC/ST Thana Yes VPNoBB 7- 8
27 Bokaro Sector –IV Yes VPNoBB 4 -5
28 Bokaro SIYALJORI Yes VSAT 4 -5
29 Chatra Bashishtnagar Yes VPNoBB 4 -5
30 Chatra Ghorighat Yes VSAT 4 -5
31 Chatra Gidhour Yes VPNoBB 4 -5
32 Chatra Hantarganj Yes VPNoBB 4 -5
33 Chatra Itkhori Yes VPNoBB 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
34 Chatra Kanhachatti Yes VSAT 4 -5

35 Chatra Kunda Nil VPNoBB 4 -5
36 Chatra Lawalong Yes VPNoBB 4 -5
37 Chatra Mahila Yes VPNoBB 7- 8
38 Chatra Mayurhand Yes WIMAX 4 -5
39 Chatra Pandeypura Yes VSAT 4 -5
40 Chatra Pathalgadda Yes VPNoBB 4 -5
41 Chatra Piparwar Yes VSAT 4 -5
42 Chatra Pratappur Yes VPNoBB 4 -5
43 Chatra Rajpur Yes VSAT 4 -5
44 Chatra Sadar Yes VPNoBB 7- 8
45 Chatra SC/ST Yes VPNoBB 7- 8
46 Chatra Shila 4 -5
47 Chatra Simaria Yes VPNoBB 4 -5
48 Chatra Tandwa Yes VPNoBB 4 -5
Baba
Deoghar Vaidyanath Yes VPNoBB
49 Mandir 4 -5
50 Deoghar Chittra Yes VPNoBB 4 -5
51 Deoghar Debipur Yes CDMA 4 -5
52 Deoghar Deoghar Town Yes VPNoBB 7- 8
53 Deoghar Jasidih Yes VPNoBB 4 -5
54 Deoghar Karo Yes VPNoBB 4 -5
55 Deoghar Kunda Yes CDMA 4 -5
56 Deoghar Madhupur Yes VPNoBB 4 -5
57 Deoghar Mahila 7- 8
58 Deoghar Margomunda 4 -5
59 Deoghar Mohanpur Yes VPNoBB 4 -5
60 Deoghar Palajori Yes VPNoBB 4 -5
61 Deoghar Sarath Yes VPNoBB 4 -5
62 Deoghar Sarwan Yes VPNoBB 4 -5
63 Deoghar SC/ST 7- 8
64 Deoghar Sonaraithadhi Yes VPNoBB 4 -5
65 Dhanbad Baghmara Yes VPNoBB 4 -5
66 Dhanbad Baliapur Yes VPNoBB 4 -5
Bankmore
Dhanbad Yes VPNoBB
67 Thana 4 -5
68 Dhanbad Barora Yes VPNoBB 4 -5
69 Dhanbad Barwadda Yes VPNoBB 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
70 Dhanbad Chirkunda Yes VPNoBB 4 -5

71 Dhanbad Dhanbad Town Yes VPNoBB 7- 8
72 Dhanbad Dhansar Yes VPNoBB 4 -5
73 Dhanbad East Tundi Yes VPNoBB 4 -5
74 Dhanbad Govindpur Yes VPNoBB 4 -5
75 Dhanbad Hariharpur Yes VPNoBB 4 -5
76 Dhanbad Jharia Yes VPNoBB 4 -5
77 Dhanbad Jogta Yes VPNoBB 4 -5
78 Dhanbad Jorapokhar Yes VPNoBB 4 -5
79 Dhanbad Katras Yes VPNoBB 4 -5
80 Dhanbad Kenduwadih Yes VPNoBB 4 -5
81 Dhanbad Loyabad Yes VPNoBB 4 -5
82 Dhanbad Madhuwan Yes VPNoBB 4 -5
83 Dhanbad Mahila Yes VPNoBB 7- 8
84 Dhanbad Mahuda Yes VPNoBB 4 -5
85 Dhanbad Maithan Yes VPNoBB 4 -5
86 Dhanbad Nirsa Yes VPNoBB 4 -5
87 Dhanbad Patherdih Yes VPNoBB 4 -5
88 Dhanbad Putki Yes VPNoBB 4 -5
89 Dhanbad Rajganj Yes VPNoBB 4 -5
90 Dhanbad Saraidhela Yes VPNoBB 4 -5
91 Dhanbad SC /ST Yes VPNoBB 7- 8
92 Dhanbad Sindri Yes VPNoBB 4 -5
93 Dhanbad Sudamdih Yes VPNoBB 4 -5
94 Dhanbad Tetulmari Yes VSAT 4 -5
95 Dhanbad Tisra Yes VPNoBB 4 -5
96 Dhanbad Topchanchi Yes VPNoBB 4 -5
97 Dhanbad Tundi Yes VPNoBB 4 -5
98 Dumka Dumka Town Yes VPNoBB 7- 8
99 Dumka Gopikandar Yes VPNoBB 4 -5
100 Dumka Hansdiha Yes VPNoBB 4 -5
101 Dumka Jama Yes VPNoBB 4 -5
102 Dumka Jarmundi Yes VPNoBB 4 -5
103 Dumka Kathikund Yes VPNoBB 4 -5
104 Dumka Mahila Yes VPNoBB 7- 8
105 Dumka Masaliya Yes VPNoBB 4 -5
106 Dumka Muffasil Yes VPNoBB 4 -5
107 Dumka Ramgarh Yes VPNoBB 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
108 Dumka Raneshwar Yes VPNoBB 4 -5

109 Dumka Saraiyahat Yes VPNoBB 4 -5
110 Dumka SC/ST Yes VPNoBB 7- 8
111 Dumka Sikaripara Yes VPNoBB 4 -5
112 Dumka Taljhari Yes VPNoBB 4 -5
113 Dumka Tongra Yes VPNoBB 4 -5
114 East Singhbhum Azadnagar Available VPNoBB 4 -5
115 East Singhbhum Bagbeda Available VPNoBB 4 -5
116 East Singhbhum Bahragora Available VPNoBB 4 -5
117 East Singhbhum Barmamines Available VPNoBB 4 -5
118 East Singhbhum Barsol Available VPNoBB 4 -5
119 East Singhbhum Birsanagar Available VPNoBB 4 -5
120 East Singhbhum Bistupur Available VPNoBB 4 -5
121 East Singhbhum Bodam NO V-SAT 4 -5
122 East Singhbhum Chakulia Available VPNoBB 4 -5
123 East Singhbhum Dhalbhumgarh Available VPNoBB 7- 8
124 East Singhbhum Dumaria Available VPNoBB 4 -5
125 East Singhbhum Galudih Available VPNoBB 4 -5
126 East Singhbhum Ghatshila Available VPNoBB 4 -5
127 East Singhbhum Golmuri Available VPNoBB 7- 8
128 East Singhbhum Govindpur Available VPNoBB 4 -5
129 East Singhbhum Gudabanda NO V-SAT 4 -5
130 East Singhbhum Jadugora Available VPNoBB 4 -5
131 East Singhbhum Jugsalai Available VPNoBB 4 -5
132 East Singhbhum Kadma Available VPNoBB 4 -5
133 East Singhbhum Kamalpur Available VPNoBB 4 -5
134 East Singhbhum Kawali Available V-SAT 4 -5
135 East Singhbhum Mahila Available VPNoBB 7- 8
136 East Singhbhum Mango Available VPNoBB 4 -5
137 East Singhbhum MGM Available VPNoBB 4 -5
138 East Singhbhum Musabani Available VPNoBB 4 -5
139 East Singhbhum Parsudih Available VPNoBB 4 -5
140 East Singhbhum Patamda Available VPNoBB 4 -5
141 East Singhbhum Potka Available VPNoBB 4 -5
142 East Singhbhum Sakchi Available VPNoBB 4 -5
143 East Singhbhum SC/ST Available VPNoBB 7- 8
Shyamsundarpu
East Singhbhum Available V-SAT
144 r 4 -5
145 East Singhbhum Sidgora Available VPNoBB 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
146 East Singhbhum Sitaramdera Available VPNoBB 4 -5

147 East Singhbhum Sonari Available VPNoBB 4 -5
148 East Singhbhum Sundarnagar Available VPNoBB 4 -5
149 East Singhbhum Telco Available VPNoBB 7- 8
150 Garhwa Bardiha Yes VSAT 4 -5
151 Garhwa Bhandariya Yes VPNoBB 4 -5
152 Garhwa Bhwanathpur Yes VPNoBB 4 -5
153 Garhwa Chiniya Yes VPNoBB 4 -5
154 Garhwa Dandai Yes VSAT 4 -5
155 Garhwa Dando Yes VSAT 4 -5
156 Garhwa Dhudki Yes VPNoBB 4 -5
157 Garhwa Garhwa Town Yes VPNoBB 7- 8
158 Garhwa Kandi Yes VPNoBB 4 -5
159 Garhwa Ketar Yes VSAT 4 -5
160 Garhwa Kharodhi Yes VSAT 4 -5
161 Garhwa Mahila Yes VPNoBB 7- 8
162 Garhwa Majhiyon Yes VPNoBB 4 -5
163 Garhwa Meral Yes VPNoBB 4 -5
164 Garhwa Nagar Untari Yes VPNoBB 4 -5
165 Garhwa Ramkanda Yes VPNoBB 4 -5
166 Garhwa Ramna Yes VPNoBB 4 -5
167 Garhwa Ranka Yes VPNoBB 4 -5
168 Garhwa SC/ST No VPNoBB 7- 8
169 Garhwa Vishnupura Yes VSAT 4 -5
170 Giridih Ahilyapur Yes VSAT 4 -5
171 Giridih Bagodar Yes VPNoBB 4 -5
172 Giridih Bengabad Yes VPNoBB 4 -5
173 Giridih Bhelwaghati Yes VSAT 4 -5
174 Giridih Birni Yes VPNoBB 4 -5
175 Giridih Deori Yes VPNoBB 4 -5
176 Giridih Dhanwar Yes VPNoBB 4 -5
177 Giridih Dumri Yes VPNoBB 4 -5
178 Giridih Gandey Yes VPNoBB 4 -5
179 Giridih Gawan Yes VPNoBB 4 -5
180 Giridih Giridih Town Yes VPNoBB 7- 8
181 Giridih Hirodih Yes VPNoBB 4 -5
182 Giridih Jamua Yes VPNoBB 4 -5
183 Giridih Khukhra Yes VSAT 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
Lokai
Giridih
184 Narayanpur 4 -5
185 Giridih Mahila Yes VPNoBB 7- 8
186 Giridih Muffasil Yes VPNoBB 4 -5
187 Giridih Nimiyaghat Yes VSAT 4 -5
188 Giridih Pirtand Yes VPNoBB 4 -5
189 Giridih Sariya Yes VPNoBB 4 -5
190 Giridih SC/ST Yes VPNoBB 7- 8
191 Giridih Taratand Yes VPNoBB 4 -5
192 Giridih Tisri Yes VPNoBB 4 -5
193 Godda Belbadda 4 -5
194 Godda Boarijor 4 -5
195 Godda Deodand 4 -5
196 Godda Godda Muffasil Yes VPNoBB 4 -5
197 Godda Godda Town Yes VPNoBB 7- 8
198 Godda Hanwara 4 -5
199 Godda Lalmatiya 4 -5
200 Godda Mahagama 4 -5
201 Godda Mahila Yes VPNoBB 7- 8
202 Godda Meherma 4 -5
203 Godda Pathargama 4 -5
204 Godda Poreyahat Yes VPNoBB 4 -5
205 Godda SC/ST Yes VPNoBB 7- 8
206 Godda Sunderpahari Yes VPNoBB 4 -5
207 Godda Thakhurgangti Yes VPNoBB 4 -5
Albert Akka
Gumla No VSAT
208 (Jari) 4 -5
209 Gumla Basia yes VPNoBB 4 -5
210 Gumla Bharno Yes VPNoBB 4 -5
211 Gumla Bishunpur Yes VPNoBB 4 -5
212 Gumla Chainpur Yes VPNoBB 4 -5
213 Gumla Dumri Yes VPNoBB 4 -5
214 Gumla Ghaghra Yes VPNoBB 4 -5
215 Gumla Gumla Town Yes VPNoBB 7- 8
Gurdari
Gumla Yes VSAT
216 (Vishunpur) 4 -5
217 Gumla Kamdara yes VPNoBB 4 -5
Kurumgarh
Gumla VSAT
218 (Chainpur) 4 -5
219 Gumla Mahila Yes VPNoBB 7- 8

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
220 Gumla Palkot Yes VPNoBB 4 -5

221 Gumla Raidih Yes VPNoBB 4 -5
222 Gumla SC/ST Yes VPNoBB 7- 8
223 Gumla Sisai Yes VPNoBB 4 -5
Sursang
Gumla Yes VSAT
224 (Raidih) 4 -5
225 Gumla Toto VPNoBB 4 -5
226 Hazaribagh Ango Yes VSAT 4 -5
227 Hazaribagh Barhi Yes VPNoBB 4 -5
228 Hazaribagh Barkagaon Yes VPNoBB 4 -5
229 Hazaribagh Barkatha Yes VPNoBB 4 -5
230 Hazaribagh Bishnugarh Yes VPNoBB 4 -5
231 Hazaribagh Chalkusha Yes VSAT 4 -5
232 Hazaribagh Charhi Yes VPNoBB 4 -5
233 Hazaribagh Chauparan Yes VPNoBB 4 -5
234 Hazaribagh Churchu Yes VPNoBB 4 -5
235 Hazaribagh Dandi Yes VPNoBB 4 -5
236 Hazaribagh Daru Yes VPNoBB 4 -5
237 Hazaribagh Giddi Yes VPNoBB 4 -5
238 Hazaribagh Gorhar Yes VSAT 4 -5
239 Hazaribagh Ichak Yes VPNoBB 4 -5
240 Hazaribagh Katkamdag Yes VSAT 4 -5
241 Hazaribagh Katkamsandi Yes VPNoBB 4 -5
242 Hazaribagh Keredari Yes VPNoBB 4 -5
243 Hazaribagh Mahila Yes VPNoBB 7- 8
244 Hazaribagh Muffasil Yes VPNoBB 4 -5
245 Hazaribagh Sadar Yes VPNoBB 7- 8
246 Hazaribagh SC/ST Yes VPNoBB 7- 8
247 Hazaribagh Tati Jhariya Yes VPNoBB 4 -5
248 Jamtara Bagdehri Yes Wimax 4 -5
249 Jamtara Bindapathar Yes VSAT 4 -5
250 Jamtara Fatehpur Yes VPNoBB 4 -5
251 Jamtara Jamtara Yes VPNoBB 7- 8
252 Jamtara Karmatand Yes VPNoBB 4 -5
253 Jamtara Kundhit Yes VPNoBB 4 -5
254 Jamtara Mahila Yes VSAT 7- 8
255 Jamtara Mihijam Yes VPNoBB 4 -5
256 Jamtara Nala Yes VPNoBB 4 -5
257 Jamtara Narayanpur Yes VPNoBB 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
258 Jamtara SC/ST Yes VPNoBB 7- 8

259 Khunti Arki Yes VPNoBB 4 -5
260 Khunti Karra Yes VPNoBB 4 -5
261 Khunti Khunti Town Yes VPNoBB 7- 8
262 Khunti Mahila Yes VPNoBB 7- 8
263 Khunti Murhu Yes VPNoBB 4 -5
264 Khunti Raniya Yes VPNoBB 4 -5
265 Khunti SC/ST Yes VPNoBB 7- 8
266 Khunti Torpa Yes VPNoBB 4 -5
267 Koderma Chandwara Yes VPNoBB 4 -5
268 Koderma Dhab 4 -5
269 Koderma Domchanch Yes VPNoBB 4 -5
270 Koderma Jainagar Yes VPNoBB 4 -5
271 Koderma Kodarma Town Yes VPNoBB 7- 8
272 Koderma Mahila Yes VPNoBB 7- 8
273 Koderma Markacho Yes VPNoBB 4 -5
274 Koderma Nawalshahi 4 -5
275 Koderma Satgawa Yes VPNoBB 4 -5
276 Koderma SC/ST Yes VPNoBB 7- 8
277 Koderma Telaiya Yes VPNoBB 4 -5
278 Latehar Balumath Yes VPNoBB 4 -5
279 Latehar Baresadh No VSAT 4 -5
280 Latehar Barwadih Yes VPNoBB 4 -5
281 Latehar Chandwa Yes VPNoBB 4 -5
282 Latehar Chhipadohar Yes VPNoBB 4 -5
283 Latehar Garu Yes VPNoBB 4 -5
284 Latehar Herhanj 4 -5
285 Latehar Latehar Town Yes VPNoBB 7- 8
286 Latehar Mahila Yes VPNoBB 7- 8
287 Latehar Mahuadand Yes VPNoBB 4 -5
288 Latehar Manika Yes VPNoBB 4 -5
289 Latehar Netarhat 4 -5
290 Latehar SC/ST Yes VPNoBB 7- 8
291 Lohardaga Bagdu Yes VSAT 4 -5
292 Lohardaga Bhandra Yes VPNoBB 4 -5
293 Lohardaga Jobang Yes VSAT 4 -5
294 Lohardaga Kairo Yes VSAT 4 -5
295 Lohardaga Kisko Yes VPNoBB 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
296 Lohardaga Kudu Yes VPNoBB 4 -5

Lohardaga
Lohardaga Yes VPNoBB
297 Town 7- 8
298 Lohardaga Mahila Yes VPNoBB 7- 8
299 Lohardaga SC/ST Yes VPNoBB 7- 8
300 Lohardaga Senha Yes VPNoBB 4 -5
301 Lohardaga Serendag Yes VSAT 4 -5
302 PAKUR Amlapara Yes VPNoBB 4 -5
303 PAKUR Hiranpur Yes VPNoBB 4 -5
304 PAKUR Littipara Yes VPNoBB 4 -5
305 PAKUR Maheshpur Yes VPNoBB 4 -5
306 PAKUR Mahila Yes VPNoBB 7- 8
307 PAKUR Pakur Mufsil Yes VPNoBB 4 -5
308 PAKUR Pakur Town Yes VPNoBB 7- 8
309 PAKUR Pakuria Yes VPNoBB 4 -5
310 PAKUR SC/ ST Yes VPNoBB 7- 8
311 Palamu Bishrampur 4 -5
312 Palamu Chainpur Yes VPNoBB 4 -5
313 Palamu Chhatarpur Yes VPNoBB 4 -5
Daltonganj
Palamu Yes VPNoBB
314 Town 7- 8
315 Palamu Haidernagar Yes VPNoBB 4 -5
316 Palamu Hariharganj Yes VPNoBB 4 -5
317 Palamu Hussainabad Yes VPNoBB 4 -5
318 Palamu Lesliganj Yes VPNoBB 4 -5
319 Palamu Mahila 7- 8
320 Palamu Manatu Yes CDMA 4 -5
321 Palamu Mohammadganj Yes VPNoBB 4 -5
322 Palamu Nawa Bazar yes VSAT 4 -5
323 Palamu Nawajaipur yes VSAT 4 -5
324 Palamu Noudiha Bazar yes VSAT 4 -5
325 Palamu Pandu yes 4 -5
326 Palamu Pandwa yes VPNoBB 4 -5
327 Palamu Panki Yes VPNoBB 4 -5
328 Palamu Patan Yes VPNoBB 4 -5
329 Palamu Pipra yes VSAT 4 -5
330 Palamu Pipratand 4 -5
331 Palamu Ramgarh 4 -5
332 Palamu Rehla 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
333 Palamu Sadar Bairia Yes VPNoBB 4 -5

334 Palamu SC/ST 7- 8
335 Palamu Tarhansi yes VSAT 4 -5
336 Palamu Utari Road yes 4 -5
Rail District
Barharwa
337 Dhanbad 4 -5
Rail District Barkakana Rail
Yes VPNoBB
338 Dhanbad Ps 7- 8
Rail District
BOJUDIH Yes VPNoBB
339 Dhanbad 7- 8
Rail District
Chandrapura Yes VPNoBB
340 Dhanbad 7- 8
Rail District Daltonganj (Rail
341 Dhanbad PS) 7- 8
Rail District
Dhanbad Rail PS Yes VPNoBB
342 Dhanbad 7- 8
Rail District
Gomiyo Yes VPNoBB
343 Dhanbad 7- 8
Rail District
Gomo Rail PS Yes VPNoBB
344 Dhanbad 7- 8
Rail District
Jasidih Rail PS Yes VPNoBB
345 Dhanbad 7- 8
Rail District Katrasgarh(Rail
Yes VPNoBB
Rail District
Kodarma Rail Ps Yes VPNoBB
347 Dhanbad 7- 8
Rail District Kusunda (Rail
Yes VPNoBB
Rail District Madhupur Rail
Yes VPNoBB
349 Dhanbad PS 7- 8
Rail District Patherdih Rail
Yes VPNoBB
350 Dhanbad PS 7- 8
Rail District Sahibganj Rail
Yes VPNoBB
351 Dhanbad PS 7- 8
Rail District East BOKARO (Rail
Yes VPNoBB
352 Singbhum PS) 7- 8
Rail District East Chakradharpur
Available VPNoBB
353 Singbhum (Rail PS) 7- 8
Rail District East Chandil (Rail
Available VPNoBB
Rail District East Dogwaposi (Rail
Available VPNoBB

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
Rail District East

Hatia (Rail PS)
356 Singbhum 7- 8
Rail District East
Muri (Rail PS)
357 Singbhum 7- 8
Rail District East
Ranchi (Rail PS)
358 Singbhum 7- 8
Rail District East Tatanagar (Rail
Available VPNoBB
360 Ramgarh Barlanga Yes VSAT 4 -5
361 Ramgarh Basal Yes VPNoBB 4 -5
362 Ramgarh Gola Yes VPNoBB 4 -5
363 Ramgarh Mahila Yes VPNoBB 7- 8
364 Ramgarh Mandu Yes VPNoBB 4 -5
365 Ramgarh Patratu Yes VPNoBB 4 -5
366 Ramgarh Rajrappa Yes VPNoBB 4 -5
367 Ramgarh Ramgarh Town Yes VPNoBB 7- 8
368 Ramgarh SC/ST Yes VPNoBB 7- 8
369 Ranchi Angara Yes VPNoBB 4 -5
370 Ranchi Argora Yes VPNoBB 4 -5
371 Ranchi Bariyatu Yes VPNoBB 4 -5
372 Ranchi Bedo Yes VPNoBB 4 -5
373 Ranchi Budmu Yes VPNoBB 4 -5
374 Ranchi Bundu Yes VPNoBB 4 -5
375 Ranchi Chanho Yes VPNoBB 4 -5
376 Ranchi Chutia Yes VPNoBB 4 -5
377 Ranchi Daily Market Yes VPNoBB 4 -5
378 Ranchi Dasham Fall Yes VSAT 4 -5
379 Ranchi Dhurwa Yes VPNoBB 7- 8
380 Ranchi Doranda Yes VPNoBB 4 -5
381 Ranchi Gonda Yes VPNoBB 4 -5
382 Ranchi Hindpiri Yes VPNoBB 4 -5
383 Ranchi Itki Yes VPNoBB 4 -5
384 Ranchi Jagarnathpur Yes VPNoBB 4 -5
385 Ranchi Kanke Yes VPNoBB 4 -5
386 Ranchi Khelari Yes VPNoBB 4 -5
387 Ranchi Kotwali Yes VPNoBB 7- 8
388 Ranchi Lalpur Yes VPNoBB 4 -5
389 Ranchi Lapung Yes VPNoBB 4 -5
390 Ranchi Lowar Bazar Yes VPNoBB 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
391 Ranchi Mackluskiganj Yes VPNoBB 4 -5

392 Ranchi Mahila yes VPNoBB 7- 8
393 Ranchi Mandar Yes VPNoBB 4 -5
394 Ranchi Nagri Yes VPNoBB 4 -5
395 Ranchi Namkum yes VPNoBB 4 -5
396 Ranchi Narkopi Yes VSAT 4 -5
397 Ranchi Ormanjhi Yes VPNoBB 4 -5
398 Ranchi Pithoria Yes VPNoBB 4 -5
399 Ranchi Ratu yes VPNoBB 4 -5
400 Ranchi Sadar Yes VPNoBB 7- 8
401 Ranchi SC/ST Yes VPNoBB 7- 8
402 Ranchi Sikidiri Yes VPNoBB 4 -5
403 Ranchi Silli yes VPNoBB 4 -5
404 Ranchi Sonahatu Yes VPNoBB 4 -5
405 Ranchi Sukhdeonagar Yes VPNoBB 4 -5
406 Ranchi Tamar Yes VPNoBB 4 -5
407 Ranchi Tatisilway Yes VPNoBB 4 -5
408 Ranchi Thakurgaon Yes VPNoBB 4 -5
409 Ranchi Traffic Yes VPNoBB 4 -5
410 Sahebgunj Barhait Yes VPNoBB 4 -5
411 Sahebgunj Barharwa Yes VPNoBB 4 -5
412 Sahebgunj Boriyo Yes VPNoBB 4 -5
413 Sahebgunj Kotalpokhar No VPNoBB 4 -5
414 Sahebgunj Mahila Yes VPNoBB 7- 8
415 Sahebgunj Mirzachouki Yes VPNoBB 4 -5
416 Sahebgunj Muffasil Yes VPNoBB 4 -5
417 Sahebgunj Radhanagar Yes VPNoBB 4 -5
418 Sahebgunj Rajmahal Yes VPNoBB 4 -5
419 Sahebgunj Ranga Yes VSAT 4 -5
420 Sahebgunj Sahibganj Town Yes VPNoBB 7- 8
421 Sahebgunj SC/ ST Yes VPNoBB 7- 8
422 Sahebgunj Taljhari Yes VPNoBB 4 -5
Seraikella-
Adityapur Available VPNoBB
423 Kharswan 7- 8
Seraikella-
Chandil Available VPNoBB
424 Kharswan 4 -5
Seraikella-
Chouka Available VPNoBB
425 Kharswan 4 -5
Seraikella-
Gamhariya Available VPNoBB
426 Kharswan 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
Seraikella-
Ichagarh Available V-SAT
427 Kharswan 4 -5
Seraikella-
Kandra Available VPNoBB
428 Kharswan 4 -5
Seraikella-
Kharshawan Available VPNoBB
429 Kharswan 4 -5
Seraikella-
Kuchai Available VPNoBB
430 Kharswan 4 -5
Seraikella-
Kukdu Available VPNoBB
431 Kharswan 4 -5
Seraikella-
Mahila Available VPNoBB
432 Kharswan 7- 8
Seraikella-
Nimdih Available VPNoBB
433 Kharswan 4 -5
Seraikella-
Rajnagar Available VPNoBB
434 Kharswan 4 -5
Seraikella-
RIT Available VPNoBB
435 Kharswan 7- 8
Seraikella-
SC/ST Available VPNoBB
436 Kharswan 7- 8
Seraikella-
Tiruldih Available V-SAT
437 Kharswan 4 -5
Seraikella-
Town Available VPNoBB
438 Kharswan 7- 8
439 Simdega Bano yes VPNoBB 4 -5
440 Simdega Bolba yes VPNoBB 4 -5
441 Simdega Jaldega yes VPNoBB 4 -5
442 Simdega Kersai yes VSAT 4 -5
443 Simdega Kolebira yes VPNoBB 4 -5
444 Simdega Kurdega yes VPNoBB 4 -5
445 Simdega Mahabuang yes VSAT 4 -5
446 Simdega Mahila yes VPNoBB 7- 8
447 Simdega Muffasil yes VPNoBB 4 -5
448 Simdega Pakartand yes VSAT 4 -5
449 Simdega Rengadih 4 -5
450 Simdega SC/ST yes VPNoBB 7- 8
451 Simdega Simdega Town yes VPNoBB 7- 8
452 Simdega T.Tangar yes VPNoBB 4 -5
453 West Singhbhum Anandpur Available V-SAT 4 -5
454 West Singhbhum Bandgaon Available VPNoBB 4 -5
455 West Singhbhum Chakradharpur Available VPNoBB 4 -5
456 West Singhbhum Chhotanagra Available V-SAT 4 -5

Type of Primary
Power
Station bility
(Hrs.)
NoBB,CDMA,VSAT)
457 West Singhbhum Goilkera Available CDMA 4 -5

458 West Singhbhum Gua Available VPNoBB 4 -5
459 West Singhbhum Hatgamharia Available VPNoBB 4 -5
460 West Singhbhum Jagarnathpur Available VPNoBB 4 -5
461 West Singhbhum Jaraikela Available CDMA 4 -5
462 West Singhbhum Jetaya Available V-SAT 4 -5
463 West Singhbhum Jhikpani Available VPNoBB 4 -5
464 West Singhbhum Karaikela Available VPNoBB 4 -5
465 West Singhbhum Kiriburu Available VPNoBB 4 -5
466 West Singhbhum Kumardungi Available VPNoBB 4 -5
467 West Singhbhum Mahila Available VPNoBB 7- 8
468 West Singhbhum Majhgaon Available VPNoBB 4 -5
469 West Singhbhum Manjhari Available VPNoBB 4 -5
470 West Singhbhum Manoharpur Available WIMAX 4 -5
471 West Singhbhum Muffasil Available VPNoBB 4 -5
472 West Singhbhum Nowamundi Available VPNoBB 4 -5
473 West Singhbhum Sadar Available VPNoBB 7- 8
474 West Singhbhum SC/ST Available VPNoBB 7- 8
475 West Singhbhum Sonua Available WIMAX 4 -5
476 West Singhbhum Tebo Available V-SAT 4 -5
477 West Singhbhum Toklo Available V-SAT 4 -5
478 West Singhbhum Tonto Available V-SAT 4 -5

11.3 Annexure 3 – Technical Architecture and Standards

The Proposed CCTNS solution is designed using the industry’s best practices and is based on n-
tier service oriented architecture.
• The users should get authenticated before the access to the application is made
available. The users are to post the request for service and deliver services interfacing
with the applications hosted or connected through the CCTNS deployment environment.
• CCTNS application shall be built under the Centralized Architecture specification. It shall
be built on High Availability solution at the web server, application server and database
server level to overcome complete failures of services delivered through CCTNS
application. High - Availability solution works under Active - Active modes.
• In Active-Active Configuration, in normal circumstances, both the nodes are configured

in a cluster to provide the services to users continuously, so both the nodes are utilized
in online enquiries, transactions, etc. while running the same application. When one
node goes down, the entire load of the application shall switch over to the second node.
Solution Summary
• Based on n-tier Service Oriented Architecture
• DC at PDC, NDR at SDC
• DR at NIC/ Other adjoining state
• Network and Security will be taken care by SI at DC (Police Data Centre) for DR placed at
NICSI security will be the responsibility of NICSI
• Police Station – 3 desktops and 1 laptop with webcam, finger print device and 2 printers
SOA Architecture
Service Oriented Architecture (SOA) is a computer systems architectural style for creating and
using business processes, packaged as services, throughout their lifecycle. SOA also defines and
provisions the IT infrastructure to allow different applications to exchange data and participate
in business processes. These functions are loosely coupled with the operating systems and
programming languages underlying the applications. SOA separates functions into distinct units
(services), which can be distributed over a network and can be combined and reused to create
business applications. These services communicate with each other by passing data from one
service to another, or by coordinating an activity between two or more services. SOA concepts

are often seen as built upon and evolving from older concepts of distributed computing and
modular programming.
The CCTNS project will be architected using robust and proven software and hardware
technologies like Service-Oriented Architecture (SOA) and open standards. The solution
architecture shall be built on sound architectural principles enabling fault-tolerance, high-
performance and scalability both on the software and hardware levels.
SOA is a framework that enables
1. Business flexibility – to keep up with fast changing requirement of customers and

partners
2. Easy integration –using Enterprise Service Bus (ESB)
- through web service invocation
- secure FTP
- digitally signed email attachment
3. Better business process
4. Reuse of assets – turnout time is reduced
5. Reduction of risks – as with SOA, simplicity & flexibility to mitigate risk
Figure 5: Service Oriented Architecture
Portal Architecture

Portal Server is the key to an SOA approach because it provides a common framework and
interface to integrate information, people and business processes.
Essentially a portal is a series of different applications and services - some of which come with
the portal itself (e.g. content management, search, document management etc.) other
applications are then combined and assembled (together with any relevant business processes)
at the “front-end” via portlets, thus making Portal into what is essentially a giant “composite”
application.
Figure 6: Portal Architecture
In addition to the common interface, application and content integration framework provided
by Portal, it should also support the following:
• Different access modes to applications and services
• Roles and processes based access which can be used to verify and dynamically assign
what applications and services a user can see.
• The ability for business users to create and extend portal applications without the need
for any programming.
• Application templates that allow business users to easily assemble and customize linked
applications and processes into composite applications.

Figure 7: Portal Life Cycle Management
The proposed architecture can be broken into several main components. Firstly, there are the
main actors in the system comprised of citizens, SCRB users, Police Station users and other
agencies, Local IB, etc. Secondly, there are the main business services that the architecture
offers. Thirdly, the data exchange service between State server & Police station and State server
to Central NCRB Server. Finally, there is the portal framework itself which provides a pre-
packaged prescriptive architecture based on tried and true architectural approaches – SOA, pre-
integrated products, industry standards, and a shared knowledge base of experience.

Figure 8: Portal Framework
Deployment Architecture (Centralized)
The centralized deployment architecture proposed for CCTNS Project is presented below:

Figure 9: Logical Deployment architecture
This will have the following nodes:
• Load balancing – The load balancer provides horizontal scalability to the web servers
by dispatching Hyper Text Transfer Protocol (HTTP) requests among several identically
configured security gateway i.e. web servers. This node enhances system availability,
capacity, and performance. As the CCTNS Portal system grows, the ability for the system
grows and balances load and continue to maintain the designed service levels. Also, the
ability to stay up and running at all times with appropriate failover is accomplished
through cluster and load balance servers.
• Web Server node – The web server node or HTTP server is typically designed for access
by HTTP clients and to host static content for presentation. The web server also provides
services for serving other protocols like FTP, RTSP, etc. User requests for dynamic
content are forwarded by the web server to the application server for processing.
• Portal Server node– The portal server nodes provide the user presentation services.
The portal server provides the services to dynamically define a standardized enterprise
look and feel for the web applications. The portal server provides the user with the
ability to personalize web applications based on the user preferences and business rules
defined within the portal. Portals can be designed to be presented particular ways based

on roles, as well. This node enables functionality for pervasive devices, including
intelligent notification.
• Web Content Management Node– It is proposed to collaborate for content creation,

approvals, management, retention, and publishing across internet, intranet and extranet
assets. It is a power and sophisticated web content management product designed to
accelerate development of portal contents. The web content manager for portable
document manager is used for web content management for production server and
facilitates storage and rendering of web contents from Portable Document Manager.
• Business Process Manager/Workflow Management System Node– This node

manages the business workflow processes that involve business functions and human
interaction. It ensures that the business processes are executed in the proper order by
the proper people and systems. There will be business process associated with the Govt.
Department services for processing the user service request. Depending on the nature
of those workflows, a workflow system within closely connected content management
system might be needed, or a broader-based workflow engine might be needed.
• Electronic Forms Server Node– This node would work on top of J2EE application
server and provide API for processing & integrating forms with CCTNS Portal processes.
These would have capabilities to attach the supporting documents, digital signatures etc.
along with the form.
• Content Manager Nodes – This node provides for both structured data in the form of a
relational database management system (RDBMS) and unstructured content. The
content manager functionality includes integration of all forms of information, from
XML, text, images, documents, biometric data and more. The CCTNS Portal System will
have to handle a lot of various types of data and information. The ability to store
different types of information, group that information into cases and query on it, makes
Content Management node very important. This node also provides the basic document
workflow to model the business processes as part of CCTNS Portal Business Process.
• Web Application Server node – This node provides the infrastructure for component
based application logic. The web application server(s) provide the underlying J2EE
services for running servlets, JSPs (Java Server Pages) and EJB (Enterprise Java Bean)
objects, as well as interacting with other components (JMS, JDBC, etc.). Web application
servers also provide transaction management capabilities and can be configured to
provide a highly scalable and available network for running web based applications. The
web application server also provides a runtime environment for hosting and accessing

web services. For the proposed system, web application server will be the central
runtime environment for applications i.e. grievance management, Helpdesk applications,
Portal and Dashboards and MIS.
• Data Management Node- This node provides for both structured data in the form of a
relational database management system (RDBMS). This node is being used for managing
the master data, transaction data, relationship data, and other operational data entities
of various application modules products. There is a need to have a Data Quality Engine
to filter out quality data from the existing such databases with the various applications
of the department.
• Identity Solution Node – This node discovers individual’s identity i.e. “Who is who?” It
does resolves inconsistent, ambiguous identity and attributes information into a single
resolved entity across multiple data sets, despite deliberate attempts to confuse or
misrepresent individual identity. This node exposes the web services which have been
consumed by business process engine for fulfilling the business requirements.
• Enterprise Systems Management node – This node offers a full range of functionality
for monitoring and managing an enterprise-level system for quality of services levels,
system performance, potential outages, efficient use of system resources and more. The
robust capability of managing not only system components but system services is
possible with the proposed CCTNS Portal System that follows an SOA Framework thus
lowering costs through efficient utilization of system resources and pro-active system
upkeep.

Network Architecture
Figure 10: Network Architecture

It is proposed that the DC at PHQ shall be used as a Primary DC and NIC DC shall be considered
as Secondary DC i.e. DR.
Complete Network and Security will be of DC/NIC. The Severs with SSL encryption and Server
Load Balancer along with the storage shall have to be used.
The CCTNS database at the Data Centre will be mirrored at Disaster Recovery on a routine basis
with desired RPO (Recovery Point Objective) and RTO (Recovery Time Objective). This Disaster
recovery shall serve as a redundant link in case of failure in accessing the application from the
State Data Centre.
Information Security Measures
CCTNS application security initiatives should include, DMZ Policy, encryption, authentication,
authorization and digital signature. It should take the appropriate measures for the data
privacy, confidentiality and access control.
CCTNS’s complete security is assured by implementing the security at the following levels,
• Component level (Operating system, routers, switches etc.) security (ISO 15408)
• Application level (Basic application for access control, authentication and audit trail etc.)
security
• System level (Physical security, communication and operation management, business

continuity management etc.) security (ISO 27001)
Integration with JHARNET
Core Infrastructure - JHARNET
JHARNET is used to connect distributed network sites in a Government via private or

public telecommunication lines. It typically serves as a customized communication
"backbone" interconnecting all the Government local networks with communications
trunks that are appropriate based on anticipated communication rates and volumes
between nodes. The network would be able to support Voice, Data and Video services. It
would form the backbone on which all departmental and core applications reside. The
JHARNET will connect the CCTNS headquarters, zones, Districts and police stations. This
robust connectivity backbone right from the state headquarter to the lowest hierarchies
will make it possible to have better service standards and lesser Turnaround Time for all
the stakeholders of the department.
State Data Centre
The State Data Centre, for the department, Police Data Centre (PDC) located at Police
Head Quarter, Dhurwa, Ranchi, would function as a centralized location to host all the IT
initiatives of the Department. It would act as a mediator and convergence point between
the open unsecured public domain and sensitive government environment. The PDC
enables the department to host their services/applications on a common infrastructure
leading to ease of integration and efficient management, ensuring that computing
resources and the support connectivity infrastructure (JHARNET) is adequately and
optimally used. The PDC would need to be equipped with state of the art Data Security,
System Security, Internet Security, Redundant Power supply, Access Control System, Air-
conditioning and other infrastructure. The PDC would host the CCTNS Core State
Application and the Department Applications.
Figure 11: Proposed CCTNS WAN

User and Bandwidth Sizing
Table 15: User and Bandwidth Sizing
Transaction
Number Bandwidth
Area under Number Number of volume
of users / Requirement
consideration of offices users (KB) per
office (MB)
user
Zone 2 4 8
Range 2 7 14
Districts 5 26 130
Police stations (3
desktop and 1 laptop) 4 478 1912
PHQ 30 1 30
Sub Division office 1 55 55
Labs(forensic,
cybercrime) 3 2 6
Training Labs - Districts 10 24 240
Training Lab (Police

Academy, Police
College) 20 5 100
Total System Users 602 2,495
Concurrent (30%) 748.5 35 26.19
Estimated citizens in
Jharkhand 3.90 Cr.
%age estimated for

CCTNS
users in Jharkhand 5
Total Portal users 17.50Lacs

Disaster Recovery
Disaster recovery is the process, policies and procedures related to preparing for recovery or
continuation of technology infrastructure critical to an organization after a natural or human-
induced disaster. Disaster recovery is a subset of business continuity. While business continuity
involves planning for keeping all aspects of a business functioning in the midst of disruptive
events, disaster recovery focuses on the IT or technology systems that support business
functions.
Figure 12: DR Centre Architecture
DR facilitates management and utilization of CAS Application resources through virtualization

concepts.
• Achieves high availability of critical data by optimal usage of the existing infrastructure
thus reducing the financial, operational and business impact in the event of any natural,
manmade or technical disasters
• Enables seamless growth of CAS during the entire lifecycle by removing dependencies
on specific hardware configurations
• Manages Trigger like loss of site events effectively
The separate DR capability supports an entirely flexible development, test and staging
environment. The result was a visibly increased performance and far greater utilization
capability. The Figure above shows the overview of Disaster Recovery, LAN & WAN integration.
All the critical services are required to be replicated in disaster recovery, so only one broadcast

domain will be created. Because of the above reason, two sets of switches and one WAN router
are shown in the figure above.
1. The bidder should make provision the storage infrastructure and accessories as
required for the Overall application of CCTNS at DC and DR site (to be placed at NICSI
data centres). The storage solution for CCTNS will constitute near ZERO data loss
solution with Recovery Point Objective (RPO) shall be limited to data those are in-
transit for replication at the time of occurrence of any disaster and Recovery Time
Objective (RTO) =< 2 hours for the critical application on storage.
2. For other non-critical applications and processes, the RTO shall not exceed 12 hours and
the RPO shall be limited to data those are in-transit for replication at the time of
occurrence of any disaster.
3. Bandwidth sizing requirement has been specified in this RFP. Bidder shall also suggest
the required bandwidth between the DC and DR centres to meet the RPO & RTO
specified as above, for both critical as well as non-critical Applications. Proposed
Architecutre is shown in the Fig. below.
Figure 13: DC /NDR/ DR Centre Architecture

11.4 Annexure 4 - Implementation Plan

Implementation Model
It is proposed to roll out CCTNS in three phases. Deployment of hardware, connectivity and
other infrastructure across all police stations, higher offices and other police units would take
place in the first two phases. CAS (Core Application Software) would be rolled out in three
phases. The core focus of each of the three phases is delineated below:
CCTNS Implementation Phase-I
During the first phase of the application, CCTNS would be rolled out in covering 1 Police district
– Old Ranchi (Presently Ranchi and Khunti district; amounting to approximately 10% of the
total police locations across the state) one Police Station of each of 24 Police district Head
Quarter and all higher offices. The roll out would include installation and commissioning of
hardware, network connectivity as applicable, , other infrastructure and associated services
(such as handholding). The choice of the districts where the first phase would be rolled out is
provided below.
Geographical coverage during phase-I
Number
Sl. Districts in Phase I of Police Rationale for choosing them
Stations
- Large populated district

- IT savvy departments in these districts
1 Ranchi 41 - Proximity to the headquarters

- CIPA District
- All these police stations were covered
under CIPA
2 Khunti 8 - Do -
3 1 Police Station of 24Police districts 24 - Do -

Total 73
Service Coverage
During the first phase, the following services and service levels will be achieved.

Service coverage during phase-I
Sl. Services Service levels

1 FIR - 1 hr. from
General Diary
- Lodging of FIR
- 1 hr. from lodging
- Issuance of FIR
2 Complaints
- Complaints to the concerned Police Station - 1 hr. from arrival
- Receipt of complaint/case to the concerned - 1 day

Police Station /Cell / Wing
- Action taken on the registered complaint
- 7 days
3 Details of stolen items
- Details of stolen/ recovered vehicles, arms and 1 day from request

other properties
4 Details of missing persons
- Details of missing/ kidnapped persons and their 1 day from request

matching with arrested, unidentified persons and
dead bodies
Digitization of Historical Data:
In addition to the functionality identified above, Phase-I would also include the digitization of
historical data (covering the last 10 years record). The historical data to be digitized would
include crime (case/incident) data, criminals’ data, the data from the 7 IIF and data from the
police stations records rooms (from Police Registers).
The Digitization of Historical data would be done on the basis of per ‘Case’. A ‘Case’ contains the
following documents which will have to be digitized.
Number of records for Data Digitization during phase-I
S No. Registers/Form Name Number of Records
1 FIR Approximately 240 cases per police
2 Charge Sheet stations for last 10 Years

S No. Registers/Form Name Number of Records
3 Seizure Memo
4 Conviction Memo
5 Arrest Memo
6 Final Report
7 Missing/ Unclaimed- Person/ Property
Digitization of historical data would help the police department maximize benefits from features
such as Search and Reporting and is would significantly enhance outcomes in the areas of Crime
Investigation, Criminals Tracking, servicing the requests of citizens and other groups, etc.
The digitization exercise would be carried out by the state-level SI.
Data Digitized under CIPA:
Table 16: Digitized data under CIPA
Data Migration
Sl. CIPA
Registers/Form Name
Number of Records
1 FIR 19,000
Application Functionalities
The application modules and functionalities to be covered during the Phase I of CCTNS
implementation are listed in the table below:
Table 17: Application modules to be covered during phase-I
Modules Additional Functionalities Covered

Registration module The details of the additional functionalities
of these modules are given under
Investigation module Functional Requirements Chapter.
Prosecution module


Basic and Advanced Search functionality
Basic (regular) reporting and MIS
Capacity Building Initiatives
The no. of personnel in each group that would be trained on the four training themes during
Phase-I is provided in the table below:
Table 18: Training to be covered in Phase-I
Training Program Group A Group B Group C

Awareness and sensitization on benefits of IT 30 2,000 -
Basic Computer Awareness 4,000
Role based training for application users 0
System Administration & Support training 0
Training of Trainers 0
Outcomes
Table 19: Expected outcomes during phase-I
Phase Activities Outcomes Challenges

CCTNS Rollout in Ranchi & Khunti Implementation of CCTNS
- Resistance to change
Phase-I districts of Jharkhand in 2 districts
- Agreement on the
Establishment of service Accountability of services service levels for the
levels pertaining to above provided by the services provided
mentioned services department
- Historical data is
Digitization of historical The historical data can be incomplete/ missing
data of the last 10 years retrieved from the system - Required personnel
through the Search feature not available for
training
Training imparted to the 6030 people would have


personnel of Group A, B & undergone the training
C program
CCTNS Implementation Phase-II
During Phase-II of CCTNS Implementation, the remaining police stations will be covered for the
installation and commissioning of hardware, network connectivity as applicable and other
infrastructure and associated services.
The districts where the second phase would be rolled out are provided below.
Table 20: District wise Police station to be covered in Phase-II
Sl. Districts in Phase II Number of Police Stations

1 Bokaro 27
2 Chatra 19
3 Deoghar 15
4 Dhanbad 32
5 Dumka 15
6 East Singhbhum 35
7 Garhwa 19
8 Giridih 22
9 Godda 14
10 Gumla 17
11 Hazaribagh 21
12 Jamtara 10
13 Koderma 10
14 Latehar 12
15 Lohardaga 10

Sl. Districts in Phase II Number of Police Stations

16 Pakur 8
17 Palamu 25
18 Ramgarh 8
19 Sahebganj 12
20 Saraikella-Kharswan 15
21 Simdega 13
22 West Singhbhum 25
23 Railway East Singhbhum 7
24 Railway Dhanbad 14
Total 405
Service Coverage
During the second phase, the following services and service levels will be achieved in addition to
the services rolled out in Phase-I.
Table 21: Service coverage during phase-II

Portal Information
1 4 hrs.
- Updation of information or status on the portal
The application modules and functionalities covered during the Phase II of CCTNS
Table 22: Service coverage during phase-II

Collaboration Solutions (police The details of the additional functionalities of
messaging, email) these modules are given under Functional
Requirement Chapter.
Citizen Interface


Advanced analysis, Business Intelligence
and MIS
Common component & workflow
Crime Prevention (Beat Management,

etc.)
Phase II is provided in the table below:
Table 23: Training planned for phase-II

Awareness and sensitization of
35 2,000
benefits of IT
Role based training for application

12,000
users
Training of Trainers 60 70
System Administration & Support

70 76
training
Outcomes
Table 24: Expected outcomes during phase-II

CCTNS Rollout in remaining Implementation of CCTNS
- Resistance to change
Phase-II districts of Jharkhand in 24 districts
- Agreement on the
levels pertaining for the provided by the services provided
above mentioned services department
- Required personnel


Training imparted to the Approximately 18,000 not available for
personnel of Group A, B & people would have training
C undergone the training
program
CCTNS Implementation Phase-III
All police units in the State would have been covered for the installation and commissioning of
hardware, connectivity and other infrastructure by the end of Phase-II. CCTNS Phase-III is
planned around the release of subsequent versions of CAS and the large enhancements initiated
at the state level.
Service Coverage
During the third phase, the following additional services and service levels will be achieved.
Table 25: Service coverage planned for Phase-III

1 Registration of Vehicles
1. 1 day
1. Issue of NOC for used vehicles
2 Arms License
1. 15 days
1. Verification for new arms license 2. 7 days
2. Verification for renewal of arms license 3. 2 days after receiving
3. Verification of arms license of the application
3 Foreigner Registration
1. Registration of foreigners 1. 2 Hours

2. Issue of NOC for foreigners 2. 1 day
4 Verification Requests
1. 10 days
1. Servants 2. 10 days
2. Employment 3. 15 days
3. Passport 4. 10 days
4. Character 5. 10 days


5. Tenant
5 Security to VIP/Event
1. Provide security 1. 2 days from request

6 Surveillance
1. Provide surveillance to suspect 1. 6 hrs. from request
The application modules and functionalities covered during the Phase III of CCTNS
Table 26: Application modules to be covered during Phase-III

Traffic Module The details of the additional
functionalities of these modules are
Call Centre given under Functional Requirement
Specifications.
SP Office Module
Naxal Information System
Phase III is provided in the table below:
Table 27: Training planned for Phase-III

Awareness and sensitization on benefits of IT 2,531
Role based training for application users 11,777
Outcomes

Table 28: Expected outcomes during Phase-III

CCTNS Upgrade to newer version
Latest version of CAS - Resistance to change
Phase-III of CAS and enhancements
- Agreement on the
levels pertaining for the provided by the services provided
above mentioned services department
- Required personnel
Training imparted to the Remaining people would not available for
personnel of Group A, B & have undergone the training
C training program

11.5 Annexure 5 – Information on Existing Systems

A. EXISTING LEGACY SYSTEMS (Applications) in Jharkhand Police
Table 29: Legacy Systems/Applications
Areas of police
Application Date of
Sl. functioning Present status
Software Name commissioning
covered
1. Web Portal of the Ready to be deployed
Department under public domain
CMS: Drupal Ver. 6
Web Server: Apache
Scripting: PHP
Database: MySQL
2. Open Text Overall Office 2009 Installed at PHQ,

(Document Documentation Ranchi
Management
System)
3. CIPA Reducing of manual 2007 38 Police Stations

records, elimination (Old Ranchi District
of duplicate and only (Presently
inconsistent record Ranchi & Khunti
keeping, Districts))
maintenance of
details of criminals,
introducing
transparency in the
working of police,
facilitating
supervision by the
senior officers and
faster response to
the public.
4. Personnel Personnel Records – 2010 Web Based

Information Entire Police Force Application hosted at
System by NIC SDC, JAP-IT, and
Dhurwa.
The System is
developed in VB.net,
Web based solution
now is being used by

Areas of police
Application Date of
Sl. functioning Present status
Software Name commissioning
covered
50+ users
Backend: Oracle 10g

OS: Windows 2003
Server
5. CCMS (Court Case Maintain & monitor

Monitoring court cases pending
System) – NIC in different courts
(e.g. Supreme Court,
High Court, District
Court, Labour Court,
Consumer Court,
etc.)
6. Inventory & Asset Provides basic Web based solution

Management information about under development
System the inventory and
assets.
7. Motor Vehicle & Provides basic Web based solution

Fleet information about under development
Management the motor vehicle
System and fleet.
8. Naxal Information Application

System development
platform
• OS – Window
2003
• Web Server –
Apache 2.0
• Scripting : PHP
• Framework:
CakePHP
Database: MySQL
9. Visitors’
Platform used:
Information
System VB6
Database: MySQL

B. EXISTING DATA CENTRECENTRE INFRASTRUCTURE
The department is having its own operationalized Data Centre, hereinafter named as Police Data
Centre. It is located at Police Head Quarter, Dhurwa Ranchi. This functions as a centralized
location to host all the IT initiatives of the Department. It acts as a mediator and convergence
point between the open unsecured public domain and sensitive government environment. The
present IT infrastructure in place is detailed here under.
Sl. Item Specifications Qty.
1. Application Server OS-Windows 2003 Server, 4GB 01

Ram, AMD 2220 x 2, HDD-146GB
x2
2. Router Cisco 2821 01
3. Core Switch (Layer 3) D-Link 7206 02

With NMS Model
4. Edge Switches D-Link DGS 3426P – 24 ports 16
5. Firewall ASA 5510 02
6. Server Rack HCL – 42 U 04
7. UPS - Online Emerson- 10KVA & 20 KVA 02

11.6 Annexure 6 - Network Connectivity Details
11.6.1 Connectivity Status at PHQ, Jharkhand
Table 30 - Connectivity status at PHQ
Brief Specification
Sl. Particular Remarks
Provided Installed
1 No. of nodes 300 150
2 Access points 40 20
3 Connectivity 8Mbps 8 Mbps
4 Server RAM (for 4GB 2GB

interconnectivity)
5 Mailing Server NIC Mail Server

(for E-Mail)
6 E-mail IDs Issued to all

concerned
7 Internet security ASA 5510 Firewall + Anti-

Cisco Virus
11.6.2 Connectivity Status at Police Stations & Other Units
Table 31 - Connectivity status at Police Stations & other units
Sl. Location Connectivity Description
1 Police Stations (456) N/A
2 Zonal offices (4)/ Range offices N/A

(7)
3 District HQ- SP office/ Connected (Jharnet /NIC)

Residence (24)
4 PHQ (1) 8mbps Leased Line BSNL

The PDC would need to be equipped with state of the art Data Security, System Security, Internet
Security, Redundant Power supply, Access Control System. The PDC would host the CCTNS Core
State Application and the Department Applications.
C. EXISTING WAN INFRASTRUCTURE
Jharkhand SWAN is a very ambitious project to provide the State with a basic information
technology backbone which will be utilized for carrying voice, data and voice traffic facilitating
interdepartmental communication and data sharing within the State. SWAN will be a safe, fast,
reliable and cost effective network connecting all the blocks of the State through a hybrid
network consisting of Wimax, leased line and other network technologies on a Public-Private
Partnership mode and operating on a Build-Operate-Transfer (BOT) model. The project enables
instant online interaction among government departments / agencies resulting in obtaining
reports on a real time, improving the workflow processes and the pace of decision-making.

11.7 Annexure 7 - Jharkhand Police State Wide Area Network
Figure 14 - Jharkhand Police SWAN

D. EXISTING CLIENT SITE INFRASTRUCTURE
CIPA has been implemented in the 38 police Stations at Ranchi:
Table 32: Current Hardware Infrastructure Assessment Summary
Sl Device / Components Unit No. of Components

1 Desktops 4 144
2 Laser printers 1 38
3 Multi-function Device (printer / scan / copy) 1 38
4 Switch (16 Port) 1 38
5 Modem fax card 1 38
6 HDD Ext. 2 76
7 DVD writer i/o DVD ROM drive 2 76
8 UPS 1 38
Details of IT Infrastructure at PHQ, Jharkhand
Table 33: PHQ IT Infrastructure Assessment Summary

Sl. Item Specifications Qty.

1. Application Server OS-Windows 2003 Server, 4GB Ram, AMD 2220 x 2, HDD- 01
146GB x 2
2. Desktop Computers Intel Pentium D 33
3. Desktop Computers Intel Core2 Duo 20
4. Desktop Computers Intel Pentium IV 15
5. Desktop Computers Intel Xeon 01
6. Laser Printer – B &W HP LaserJet 26
7. Laser Printer – Colour HP LaserJet 02
8. Laser Printer – Colour Konica Minolta 05
9. Scanner HP Scanjet 05
10. Router Cisco 2821 01
11. Core Switch (Layer 3) With NMS Model D-Link 7206 02
12. Edge Switches D-Link DGS 3426P – 24 ports 16
13. Wireless Access Points 802.11g (108 Mbps) D-Link 3500AP 40
14. KVM Switch D-Link 16 Port 01
15. Firewall ASA 5510 02
16. CAT 5 Cable D-Link 305 Mtr. 30 rolls
17. Info Outlet Box UTP Angular Dual Port 350
18. CAT 5 Patch Cord D-Link 1 Mtr. 600
19. Server Rack HCL – 42 U 04
20. CAT-6 patch panel UTP Keystone-24 Port 16

21. UPS -1 KVA Emerson 40

22. UPS Uniline 14
23. SAN Storage SUN Make. Model No. Storagetek – 6100 13 TB, Raid 5 1
24. SAN Switch CISCO make MDS 9134 – 32 Port 2
25. Tape Library SUN Make, Storagetek SL500 1
The below table represents the status of IT infrastructure made available under Police modernization in Districts.
Table 34: District wise IT Infrastructure Assessment Summary
CD-
ROM /,
District S.P
Sl. Computers Printers Scanner DVD UPS Laptop Misc.
Office
writer
etc.
1. Bokaro 15 13 1 15 6 1 -
2. Chaibasa 14 14 3 19 12 1 -
3. Chatra 15 15 1 15 13 1 -
4. Deoghar 10 7 1 10 7 1 D-Link 16
Port Switch
5. Dhanbad 17 11 - 17 10 - -

CD-
ROM /,
District S.P
Office
writer
etc.
6. Dumka 20 15 2 20 11 - -
7. Garhwa 12 10 1 12 11 - -
8. Giridih 12 10 1 12 12 1 a) Online
UPS
b) 8 Port Hub
9. Godda 12 4 1 10 10 1 -
10. Gumla 11 8 1 11 5 - -
11. Hazaribagh 11 11 1 11 10 1 HP DAT Drive
12. Jamshedpur 15 12 2 15 6 - a) 3
Batteries
(Rocket)
b) Over
Voltage Cut
off Device
13. Jamtara 10 6 1 10 9 - D-Link 24

Port Switch

CD-
ROM /,
District S.P
Office
writer
etc.
14. Khunti 4 4 - 4 3 -
15. Koderma 7 9 1 7 7 - -
16. Latehar 9 9 - 9 9 - -
17. Lohardaga 11 13 1 11 10 - a) Over Cut

Voltage
Device –
2Nos.
b) 24 Port D-
link Switch –
2Nos.
c) Automatic
Double Phase
Device – 1 No.
18. Pakur 13 13 1 11 9 - -
19. Palamu 7 6 1 7 3 - -
20. Ramgarh 8 5 - 8 - - -
21. Ranchi 18 17 2 18 14 - -
22. Sahebganj 13 6 1 13 6 - a) Xerox

Machine – 1

CD-
ROM /,
District S.P
Office
writer
etc.
No.
b) Microsoft
Mouse – 1No.
c) B/W
Monitor – 1
No.
23. Saraikella- 12 7 - 12 8 - -
Kharswan
24. Simdega 12 7 1 12 7 1 -
Note: Most of the IT infrastructure available has been commissioned between 2002 and 2006 have become obsolete and needs to be replaced.
E. EXISTING CAPACITY BUILDING INFRASTRUCTURE
Following training institutes are running in Jharkhand Police Department. These institutes will be equipped with necessary infrastructure for CCTNS
project.
Table 35: Training Centre & Capacity
Name of the Training

Location Training Capacity
Institution

Name of the Training

Location Training Capacity
Institution
Hazaribagh
Police Training School @ 20 per batch
Hazaribagh
Police Training college @ 50 per batch
Jharkhand Armed Police Padma

@ 20 per batch
training Centre ( other forces
are also trained here),
Netarhat
@ 40 per batch
School of Jungle Warfare (SJW),
Ranchi
PHQ @ 20 per batch
SCRB Ranchi @ 20 per batch
DTC Each district HQ (SP @ 10 per batch

office)

11.8 Annexure 8 – Technical Specifications (Indicative)
Hardware & Networking Component for DC / NDR/ DR (IT Hardware should be of any OEM whose market share as per IDC Report is more
than 6.5%)
11.8.1 Desktop System
S. Item Complete Description

No
1 Processor Two Core , 64bit x86 Processor @ 3GHz ,4MB L3 cache, Memory support DDR3
2 Motherboard & OEM Motherboard

Chipset
3 Video Integrated Graphic controller
4 Network Integrated 10/100/1000 Gigabit Ethernet controller
5 Ports 1x fast serial port, 4x USB 2.0 ports (2 ports on front ), 1xKeyboard port, 1xMouse port
6 HDD Controller Integrated dual port SATA-II controller
7 Memory 2GB DDR III 1333MHz or higher

expandable up to 8 GB or more
8 Storage 250GB sata II HDD 7200 RPM
9 Optical Drive 22X DVD writer or higher


No
10 Monitor 18.5” TFT or more (4:3 aspect ratio) LCD Monitor 1280 x 1024 resolution with 5 ms or
better response time, TCO 05 certified
11 Keyboard 107 or more Keys mechanical Keyboard
12 Mouse USB Optical Scroll Mouse with anti-static mouse pad resolution of Optical 1000 cpi,
Complying to CE and FCC norms
13 Out Of Band System should support out-of-band management

Management
14 Power System with Power management features & Desktop Management Interface
implementation
Management &
DMI
15 System Chassis Small Form Factor System chassis with suitable power supply having active power factor
correction feature to sustain full load.
16 OS Support & Windows 7 / Linux /Centos 5.5 /Ubuntu

Certification
17 Preloaded Above configuration preloaded with OS (Latest Version) with Hindi Language packs,
Software Office Suite with Hindi Unicode fonts , ClamAV Antivirus with all necessary Plugins/
utilities and driver software including bundled in DVD Media
Laptop Specification


No
1 Operating System Windows 7 & Linux Redhat 5 /Centos 5.5 /Ubuntu
support &
certification
2 Processor & X86 processor with dual core 2 Ghz or above with 1 MB L2 cache
Chipset
3 Memory 2GB DDR3 1066 SDRAM
4 Storage 250GB SATA hard drive, 5400RPM
5 Video
14" 1366 x 768 pixel resolution, high-brightness LED-backlit TFT LCD, supporting
simultaneous multi-window viewing
6 Audio
One built-in speaker
High-definition audio support
Built-in microphone
Linux /windows compatible
7 Interface Ports
Three USB 2.0 ports HDMI™ port with HDCP support
External display (VGA) port, Headphone/speaker/line-out jack Microphone-in jack,
Ethernet (RJ-45) port
DC-in jack for AC adapter


No
8 Card Slot 2-in-1 card reader (SD, MMC,)
9 Communications Network connection supporting 802.11b/g/n wireless LAN, WI-FI ,Bluetooth wireless
PAN ,Gigabit LAN, Wake-on-LAN ready ,
10 Preloaded Above configuration preloaded with OS (Latest Version) with Hindi Language packs,
Software Office Suite with Hindi Unicode fonts , ClamAV Antivirus with all necessary Plugins/
utilities and driver software including bundled in DVD Media
12 Weight Approx. 2.6kg
13 Power Approx 65watt AC adapter , Six-cell lithium ion battery
14 Carry case Executive carry bag
15 Compliance ACPI 3.0,DMI 2.0 ,Energy Star, Mobile PC2002 ,

Wi-Fi CERTIFIED
16 Webcam Built in webcam
17 Battery backup Minimum 4 hrs backup on full work load
18 Others One USB External mechanical Key board and one Optical mouse
11.8.2 Technical Specifications 250GB External USB Hard disk
SL Parameters Specifications

1 Capacity 250GB
2 Connectivity Hi-speed USB2.0
3 Operating Windows Xp
System
Supported /Windows Vista /Windows7/
/Linux Red hat /Ubuntu
4 Accessories: Drive should be supplied with cables, necessary driver and software, Base stand and
attachable feet.
11.8.3 Technical Specifications Laser Jet Network Printer (Duplex)
1 Print speed, black Up to 26 ppm
2 Print resolution, Up to 600 x 600 x 2 dpi

black
3 Print technology Laser
4 Monthly duty Up to 8000 pages

cycle

5 Memory, standard 32 MB
6 Print languages, Host-based printing, PCL 5e

standard
7 Duplex printing Automatic (standard)

(printing on both
sides of paper)
8 Media sizes, Letter, legal, executive, postcards, envelopes (No. 10, Monarch)
standard
9 Media sizes, 250-sheet input tray: 5.8 x 8.27 to 8.5 x 14 in; priority feed slot: 3 x 5 to 8.5 x 14 in
custom
10 Media types Paper (laser, plain, photo, rough, vellum), envelopes, labels, cardstock, transparencies,
postcards
11 Accessories USB cable , Driver CD ,Utility software ,Cat5/6 UTP patch cable & One printing cartridge
included
12 Network ready Standard (built-in Ethernet)
13 Power <=450 watts

consumption
14 Power <=2.2 watts

Consumption
(Standby)

15 Operating 63.5 to 77º F

temperature
range
16 ENERGY STAR® Yes

Qualified
11.8.4 Technical Specifications Laser Jet Multifunction Printer (Print, Copy, Scan)
1. Print speed, Up to 18 ppm

black
2. Print Up to 600 x 600 dpi

resolution,
black
3. Print Laser
technology
4. Monthly duty Up to 8000 pages

cycle
5. Memory, 64 MB
standard

6. Print Host-based printing, PCL 5e

languages,
standard
7. Duplex printing Manual (driver support)

(printing on
both sides of
paper)
8. Media sizes, Letter, legal, executive, postcards, envelopes (No. 10, Monarch)
standard
9. Media sizes, 250-sheet input tray: 5.8 x 8.27 to 8.5 x 14 in; priority feed slot: 3 x 5 to 8.5 x 14 in
custom
10. Media types Paper (laser, plain, photo, rough, vellum), envelopes, labels, cardstock, transparencies,
postcards
11. Scanner type Flatbed, ADF
12. Scan resolution, Up to 1200 dpi

optical
13. Scan size 8.5 x 11.7 in
14. Scan speed Up to 6ppm
15. Supported file PDF; TIF; BMP; GIF; JPG

formats

16. Copy resolution Up to 600x 400 dpi
17. Maximum Up to 99 copies

number of
copies
18. Accessories USB cable , Driver CD ,Utility software , UTP patch cable & One printing cartridge
included
19. Connectivity Hi-Speed USB 2.0 port; 10/100Base-T Ethernet network port
20. Network ready Standard (built-in Ethernet)
21. Power <=450 watts

consumption
22. Power <=2.2 watts

Consumption
(Standby)
23. Operating 50 to 90F

temperature
range
24. ENERGY Yes

STAR®
Qualified

11.8.5 TECHNICAL SPECIFICATIONS FOR ON-LINE UPS (2KVA) SINGLE PHASE INPUT & SINGLE PHASE OUTPUT
1 Capacity 2KVA
Battery Backup 120minutes
2 General
Inverter Technology Pulse Width Modulation (PWM) using IGBTs, double conversion
Switching frequency 20 KHz or higher
Total Harmonic < 2% for 100% linear load

Distortion (THD)
< 3% for 100% non-linear load
Voltage
Noise level Less than 55 dB
Operating 0º- 50º C

Temperature
Output Wave Form Pure sine wave
Cooling Air Cooled
3 Input
Voltage Range 160 V AC to 280 V AC

Frequency range 50 ± 6% Hz
D/G set comp ability Required
Input Power Factor 0.9 or better at full output load leading to Unity with power factor correction (PFC)
4 Output
Voltage 230V AC +1 %, single phase
Regulation Less than + 1% in the following conditions

1. No load to full load/Full load to no load
2. 0.6 lag to Unity PF
3. During Entire Backup time.
4. Complete Input Voltage Range
Frequency 50 Hz + 0.5 %
5 Efficiency
Overall Efficiency 80 % or better on rated full load of 0.8 PF & 230V, 50Hz AC output
Inverter Efficiency 90% or better on rated full load of 0.8 PF & 230V, 50Hz AC output
6 Overload Capacity 110% for 2 min. & 125% overload for 30sec.

7 Load Power Factor 0.8 lagging
8 Protection Required for : Short Circuits / Over Loading/ Over Temperature / Input low/ high
voltage control/ DC low/high voltage trip
9 Battery Make Complying with JIS C 8702 test.
Battery recharge Battery recharge time should not exceed 8 hours and charger should be capable to
time charge battery on C10 rating.
(after complete
discharge to 100%
charge) & charge
rating
11 Battery Capacity
Capacity D.C.Bus Battery Bank for Back-up Time

of UPS
Voltage
2KVA <192 V 120 minutes
UPS & Battery Powder coated UPS & battery cabinet with caster wheel should be of minimum 1mm
Housing thick good quality material and should be free from sharp edge, scratches, nicks, &
burs etc. Enclosure should conform to protection requirement of IP2L1 to IS13947
(Part 1)/1993 (reaffirmed 2004).
12 L.C.D. meter To measure and monitor input voltage, output voltage, output current, DC current, DC
voltage, input / output frequency
13 Indications Mains on/ Load on Battery/ Inverter/ Battery level/ Load level/ Inverter over load

14 Audible Alarm Over Temperature / Main failure/ Battery low/ Inverter Overload
15 Switches Main ON/OFF MCB/ Battery ON/OFF MCB/ Inverter push button with reset.
16 Output Connection O/P Terminals of standard quality should be provided. 03 Nos. of 5/15A/230V female
ISI/ IEC Mark socket and all 3 sockets should
17 Isolation Galvanic Isolation through Transformer

Transformer
Note -More than two battery banks should not be used in parallel in the configuration.
11.8.6 TECHNICAL SPECIFICATIONS FOR DIESEL GENERATORS 5KVA
S.No Parameter Required Specifications
1 CAPACITY 5KVA
2 ENGINE:
COOLING SYSTEM Air cooled, Water/Coolant cooled

REQD.
WATER LEVEL The Water/Coolant cooled system of the engine should be equipped with in built
MAINTENANCE expansion tank so that frequent topping up of water/daily check of water level is not
needed. Only a top up at 250 hours should suffice. Engine should have high quality and
finish to make it a zero leakage system. Similarly the water system should have seals


etc. to ensure no water leakage from the water pump.
OUTPUT The ENGINE continuous duty rated should be capable of developing sufficient output
HP under site temperature conditions of 45 degree C to ensure full output from 5 kVA
alternator.
MINIMUM HP Not less than 10 B.H.P continuous rated.
SPEED 3000 rpm
FUEL PUMP The pump should be of MONOBLOCK design of MICO or equivalent make to ensure
better governing and easy repair in the field.
GOVERNOR Mechanical / electronic
NO. OF CYLINDERS Single / Multi cylinder, in accordance with is 10001-1981 with latest amendments.
FLYWHEEL Of suitable diameter and weight (indicate the diameter and the weight).
OVERLOAD Engine should be capable of providing 10% overload for 1 hour for every 11hour
CAPACITY continuous running at full load
ENGINE Naturally Aspirated

ASPIRATION
STANDARD THAT IS/BS (IS 10000/BS: 5514/BS: 649).

THE ENGINE
SHOULD MEET
RADIATOR Heavy duty with fan (provide technical details).

SILENCER Residential type with exhaust piping with vibration isolators (provide technical
details).
STARTING Equipment like electric motor, battery, charging alternator etc. for electric start
ACCESSORIES Fuel injection equipment, air cleaner, voltage regulator, anti-vibration mounting pads,
speed controlling governor, suitable coupling system to the alternator, tachometer,
lubricating oil temperature and pressure gauge, rpm indicator and hour meter to
indicate number of hrs. Of operation, auto trip on low oil pressure, over speed alarm
with trip, thermal insulation for exhaust line with glass wool, aluminium sheet,
chicken mesh, diesel line of suitable diameter.
PROTECTION Against low lubricating oil pressure, high water temperature shall be provided for
engine with alarm and fuel shut off.
3 ACOUSTIC The enclosure supplied should ensure not more than 5-7 degree C temperature rise
ENCLOSURE then the outside temperature with natural air circulation. The noise level should not
be more than 75 dB at 1 meter distance. Enclosure should be duly type approved by
CPCB authorized lab. The enclosure must be fitted with sheet steel of 1.2/1.6 mm
thickness, seven tank pre-treated and powder coated with pure polyester powder to
enable outdoor installation.
4 FUEL TANK Fuel tank with capacity of 12 hours continuous running at full load with necessary
piping, fuel gauge, drain valve, inlet and outlet connectors complete in all respect.
5 ENVIRONMENTAL Shall meet requirement of rules1986 as laid down by Ministry of Environment &
CONDITIONS Forest read with GSR No. 371 (E) dated: 17.05.2002, GSR 520 (E) dated: 01.07.2003
and GSR 448 (E) dated: 12.07.2004 in respect to emission norms for the engine and in
respect of noise level for the DG sets.

6 ALTERNATOR Self-excited and self-regulated alternator should be of brushless type with VG-I grade
of voltage regulation giving an output of 5 KVA, single phase 230/240 Volts, 50 Hz, 0.8
(lag) power factor, 2 wire close coupled to the Engine. Class of insulation should be
Class "H". Alternator should meet IS 13364 (part-I):1992/2003. Alternator should be
capable of 10% overload for
one hour and 50% overload for 15 seconds in 12 hours. Permissible voltage variation
- +/-1.5% of rated voltage.
PROTECTION Screen protected drip proof with IP 21 degree of protection as per IS: 4691/85.
7 AUTO MAINS The AMF control panel shall have the following instruments and accessories:
FAILURE (AMF) (a) Microprocessor based genset controller with composite meter for digital display
of:
CONTROL
i) Output voltage/AC Mains voltage.
PANEL
ii) Output Current.
iii) Power Factor
iv) Frequency.
v) kWh
vi) Three attempts engine start/engine cranking relay.
vii) On-delay timer for load change over.
viii) On-delay timer for engine shut off.
(b) Mode selector switch for setting the panel on any one position such as
OFF/auto/manual/test.
(c) Engine ON-OFF switch (Push button type)


(d) MCCB of suitable rating shall be provided.
(e) Rectangular aluminium bus bars (one number for each phase, neutral and earthing
terminal) of adequate ratings duly colour coded with heat shrinkable PVC sleeves.
(f) Two contactors of suitable rating (one for DG set & one for AC mains) with over
load relay.
g) Under-voltage relay for mains.
(h) Battery charger complete with voltage regulator, float or booster selector switch,
ON-OFF switch, voltmeter and ammeter for charging the battery from mains. This will
be in addition to the battery charging alternator fitted on the engine.
(i) Instrument & Control Fuses.
(j) Five number indicating lamps to indicate 'mains ON', 'load on mains', 'set running',
'and load on set ‘and’ battery charger on'.
(K) Audio visual alarm for 'Low lubricating oil pressure', 'High cylinder head
temperature’, ‘Start failure' and 'DG over load'.
(l) Any other switch, instrument, relay or contactor etc. essential for smooth and
trouble free functioning of DG set with AMF panel is to be specified by the tenderers in
their offer with complete detail of the item.
The panel should be within the D G set acoustic enclosure.
The system should have an inbuilt By PASS Change Over switch to ensure that in case
of AMF / D G Set failure the mains can get directly connected to the load.
Make of Contactors: Should be specified
Make of Microprocessor: Should be specified
8 BATTERY Battery of very low maintenance - 85 AH or higher lead acid type Make : Should be
specified

SIZE AND WEIGHT Should be minimum (provide details).
9 INSTALLATION 10. Earthing connection to terminate the existing earthing

DETAILS
11. RCC / PCC Foundation of size as per DG set and having a height above ground
of at least 9 inches.
12. Length of input/output cables up to a length of 20 mts.
13. 4x10 Sq. mm armoured aluminium cable
14. Cable laying - wall supported/open
15. Cable laying - under ground
16. End termination of Cable - 4 terminations
17. Exhaust piping with aluminium cladding (where needed)
18. Testing of the DG set at the site for 1 hour and handover
11.8.7 Technical Specifications 16 Port Unmanaged Switch
Parameters Specifications
1 Network Ports The switch should have minimum 16 x 10/100 Ports
UTP RJ-45 ports
2 Protocol CSMA/CD

Parameters Specifications
3 Standards IEEE 802.3 10 Base-T Ethernet

Compliance
IEEE 802.3u 100BASE-TX Fast Ethernet
IEEE/ANSI 802.3 Auto Negotiation
IEEE 802.3x Full duplex Flow Control
4 Data Transfer Rates Ethernet 10 Mbps(Half-duplex ,20 Mbps Full duplex)
Fast Ethernet 100 Mbps(Half Duplex), 200 Mbps(Full-Duplex)
5 Performance Bandwidth: 3.2 Gbps or above

Specifications
Mac Address Database 4k
6 Power Supply 100V-240VAC
11.8.8 Technical Specifications Finger Print Reader
1 Sensor Type Optoelectronic
2 Prism Architecture Dual Prism
3 Size of window 18mm x 22mm minimum

4 Glass thickness 25mm
5 Resolution 512 PPI upgradable
6 Image grey scale 256 level Dynamic
7 Scanning time 0.01Sec.
8 Distortion rate 0.1%
9 Computer interface USB2.0 , USB Powered
10 Operating 0 – 55 Degree C
temperature
11 Environmental Up to 90%
humidity
12 Optical /Film Hygroscopic

Coating
13 Operating system Window XP / Vista / 7 / Linux

Support
11.8.9 Technical Specifications Digital Camera

1 Pixels (Min.) 8 megapixels or higher
2 LCD Monitor Type TFT
3 Display Size 2.7 inches or higher
4 Recording Media SD memory card/ SDHC memory Card/SDXC memory card/ Multimedia Card
5 Recording Format JPEG
6 Zoom 3X or higher
7 ISO Sensitivity Auto / 80 / 100 / 200 / 400 / 800 / 1600 / High

Setting
8 Optical Zoom Yes

During Movie
Recording
9 Auto Focus Range Approx.: (W)=3 cm to infinity, (T)= 80 cm to infinity
10 Shooting Modes Auto, Portrait, Landscape, Night Snapshot, Indoor, Face self-timer, Low Light, Beach,
Underwater, Foliage, Snow, Fireworks, Long Shutter, Movie, Documents
11 White Balance Auto / Daylight / Cloudy / Fluorescent / Incandescent / Flash
12 Flash Function Auto/ Red Eye Reduction/Off/Face detection/noise reduction
13 USB Connectivity Yes (Hi- Speed)

14 Battery Backup 120 Min / 200 shots or above
15 Operating system Window XP / Vista / 7/ Linux

Support
11.8.10 Technical Specifications Electronic Pen
1 Data communication USB 1.1 standard (also supports USB 2.G standard), Bluetooth 1.2 standard
2 Built-in battery Rechargeable battery
3 Continuous writing 2 hours or longer Standby time:1 hours (min.) without a cap
time
4 Charging time Approx. 2 hours (from 0 to100% charge)
5 Charging method Dox cradle or USB adapter
6 Operating system Window XP / Vista / 7/ Linux

Support
7 Digital Pad Size 336mm * 245 mm
8 Pad Writing Area 210mm * 279 mm
9 Notepad Holder 210mm* 300 mm

10 Built-in Memory 32 mb or more
11 Memory Slot Secure Digital
12 Pen Size 134mm * 11.3 mm (diameter)
13 Digital Page File DHW, DND
11.8.11 Technical Specifications Computer Tables
1 Computer Table • Top: Size 910 x 610 mm made of 18 mm thick pre laminated medium density
Size: L 910 x W 610 x fibre (MDF) board ISI Marked (IS: 14587-1998). The top shall be firmly
screwed on 25x25x1 mm square tube frame.
H 728 mm
• Upper side of laminated board shall be in natural teak shade while the bottom
side shall be white/cream shade.
• Sliding key Board tray: A Sliding key Board tray shall be made of 18mm pre
laminated medium density fibre board of size 725x450 mm. The gap between
top and tray shall be 100mm.
• Sufficient top and bottom racks space to accommodate CPU, UPS and Printers
Table top should have one wire manager for wires control. Table top, keyboard
and storage shelf should be made of 19 mm pre-laminated MDF Board of
premium brands.

11.8.12 Technical Specifications Computer Chairs
1 Computer Chair with • Seat size shall be 430x430 mm on 10 mm thick moulded comm. ply with 60
Handle mm thick 40 density moulded PU foam
• Back rest size shall be 400x300 mm on 10 mm thick moulded comm. ply with
40 mm thick 32 density moulded PU foam covered with tapestry.
• The height of back rest shall be 900x500 mm for top and bottom edges
respectively. The black rest shall be provided with lifting arrangement on flat
iron & helical spring.
• Two nos. suitable PU handles shall be provided.
• The base stand should be made up of 5 prongs duly pressed welded together
centrally with a pedestal bush with good quality twin wheel castors. The stand
and other metal parts excluding central spindle shall be powder coated.
Complete steel structure shall be pre-treated and powder coated with
minimum thickness of 60 microns coating.
• A central spindle of 25mm dia rod without threads shall be provided with
revolving arrangements. The adjustable height of chair shall be from 530 to
570 mm.
A good quality tapestry cloth shall be provided on seat & back in attractive
colour/ shade.

11.8.13 Technical Specifications Electrical Cabling
1 Scope Supply, install, testing, commissioning and maintenance of electrical cabling for
supplying power to run installed devices.
2 Skilled Manpower Electrical Cabling shall be laid by skilled and experienced workmen using
adequate equipment to minimize stretching of the cable.
3 Cable Terminations All terminations should be carried out according to the manufacturer‘s
instructions and guidelines
and standards of generic cabling systems. When terminating outlets, care must be
taken for safety.
4 Testing & Testing of each node should be done as per manufacturer standards and the final
Documentation report should be submitted.
5 Specifications Total 8 Electrical Points Including 3 Switches & 3 Sockets in Each Point, (2 No. 5-
Amps and 1 No.
15 Amps.) - Point wiring using ISI approved PVC Conduit / Casing Capping, 1.1 KV
grade 2.5
Square meter FRLS Cu flexible wire including supply of wire, switch, socket and GI
Box. Including
all necessary hardware & accessories complete, material and labour as per
requirement of the MP
Police. For point wiring having Average Point length is12 to 18 Meters.
6 UPS & Generator Set Electrical Cabling for Network Rack, Four Computer Points,
Cabling
separate cabling for Two Printers from main input and Generator set to UPS

Including change-over,
MCB and all other accessories as per requirement.
11.8.14 SPECIFICATION FOR PIT EARTH
S no. Materials QTY.
General
Earth resistance measured must be less than 2 Ohm.

G.I. Pipe of 60 mm diameter with a sole plate to be laid vertically down inside the ground to depth of 3.5
meter. To the G.I. Pipe four copper plates are fitted at the bottom inside the earth. The Copper plate is of One-
meter Square. G.I. Pipe is fitted to Copper plates by means of brass bolts & nuts of 9.4 mm X 50 mm and with
spring Washers & Plate washer. The trench is fitted with fine ash to a height of One meter, then Salt to a height
of One meter, followed by Saw Dust to a height of One meter.
Thus the G.I. Pipe is buried inside, to a depth of three meters & only 0.5 meter Is kept above ground level.
From this portion connection is made to equipment Earth Strip as desired.
Copper plate .5-meter square 3 mm thick, sole plate 60 Sq. mm, 6 mm thick GI wire-to-wire earthing system
connection should be made with compression connectors or otherwise weld connection.
Copper Plate Earthing
1. 300mm x 300mm x 4mm Thick Copper Plate (Not less than 95% copper purity) 15 Kg (1 in No)
2. 25mm x 3mm Thick Copper Strip (Not less than 95% copper purity) 12 ft./ 6 Kg

3. Charcoal 200 Kg
4. Salt 40 Kg
5. (150 x 100 x 6mm Thick Terminal Plate Copper 2 Nos (0.900 Kg) each
6. Sundries such as Brass, Nut bolts, Porcelain, Insulator, Thimbles, I/Tape etc. As per requirement
7. 40mm Dia B-Class GI Pipe for watering & Strip protection. 10 ft.
8. Supply of Soft Soil (Optional) 4 Cu.Mts.
Suggestive Earthing Diagram


11.8.15 Technical Specifications Wall Mounted Network 9U Rack
1 Size 19” Wall mount ,9 U height
2 Body Minimum Powder quoted steel Body with front door of glass. Completely covered & have
security locks.
4 Accessories: Proper ventilated with One Fan, One Cable Manager, Power Distribution Unit of 6 No. (5
and 5 Amp) Sockets with surge protection, Mounting Accessories,
5 Earthing Fitted with Copper Strip for earthing the equipment
11.8.16 Technical Specifications Cat-6 Patch Panel
1 Type 24 port patch panel as per requirement, Unshielded Twisted Pair, Category 6,
ANSI/TIA/EIA 568- B.2.1
2 Circuit Port Labelling for port identification on each of 24-ports

identification
Scheme
4 Port Labels on each of 24/48-ports (to be included in supply),

Identification
5 Height 1U
6 Category Category 6
7 Modular Jack 750 mating cycles
11.8.17 Technical Specifications Information Outlet (Cat6-Single Port)
1 Type 1-port, Shuttered, White, with surface box for surface mount applications, Category
6,TIA/EIA 568-b Category
2 Material ABS/Polycarbonate
3 No. of ports One
4 Protection Shutters
5 Identification To be supplied with label for port identification

11.8.18 Technical Specifications CAT 6 Cable Lying
1 Cable Laying All the cabling shall run through PVC conduit / Casing Capping of suitable size of ISI
standard.
2 Skilled Cables shall be laid by skilled and experienced workmen using adequate equipment to
Manpower minimize stretching of the cable.
3 Cable All terminations should be carried out according to the manufacturer‘s instructions and
Terminations guidelines and standards of generic cabling systems. When terminating outlets, care must
be taken to avoid damaging the copper cores when stripping back the outer sheathing.
4 Testing & Testing of each node should be done as per manufacturer standards and the final report
Documentation should be submitted.
5 UTP The system should Meet or exceed TIA/EIA 568 B-2 specifications of Category-6 as a
OMPONENTS system. All performance parameters -Attenuation, Pair -to-Pair and power sum NEXT, Pair
And Power sum ELFEXT, Return Loss and Delay skew should be tested for 100m Channel
as well as 90m permanent Link. It should be a single OEM solution and should ensure
optimum system performance. There should not be any Impedance mismatch problems
among components of the cabling system. The complete system should be tested up to
600 MHz for all the test parameters to ensure the end-to-end system performance.
11.8.19 Technical Specifications CAT 6 Patch Cord (1 Meter / 2 Meters)

1 Length 1Meter /3 Meter
2 Conductor 24 AWG 7 / 32, stranded copper
3 Cable Type UTP CAT 6 ANSI/TIA/EIA 568-B.2.1
4 Plug Protection Matching colour boot to maintain bend radius
5 Category Category 6
6 Terminals Phosphor Bronze with gold plating
7 Jacket PVC
11.8.20 Technical Specification of Routers for Police Stations
Sl. No. Specifications
A. Architecture
1 Should be chassis based & modular architecture for scalability and should be a single box configuration for
ease of management.
2 Should have support for hardware based IPSEC VPN.
3 Should have minimum of 256MB of RAM and 32 MB of Flash Memory
B. Interface Requirements

1 2 x 10/100 Mbps Base Ethernet interface
2 1 x 2 Mbps V.35 serial interfaces
3 1 free slot for future use (3G/ISDN/ADSL/ or others)
C. Performance
1 Should support high performance traffic forwarding with concurrent features like Security, Voice enabled
2 Should support variety of interfaces like V.35 Sync Serial (2 Mbps), E1, ADSL, ISDN-BRI, FXO/FXS for remote
office aggregation
3 Should support 3G module for connectivity and also should support external popular 3G modem via USB port
4 Should hardware based encryption / compression with IPSEC and minimum 150 VPN tunnels.
5 Should have at least 150Kpps forwarding performance
6 Support for high density Ethernet switch cards 4 ports for remote offices to avoid additional switches.
7 Should have USB 2.0 ports for storing OS images
D. High Availability
1 Should support redundant connection to LAN
2 Should support Non-Stop forwarding for fast re-convergence of routing protocols
3 Should support boot options like booting from TFTP server, Network node

4 Should support VRRP or equivalent
E. Protocols
1 Should support Routing protocols like RIP ver1 (RFC1058) &2 (RFC 1722 and 1723), OSPF ver2 (RFC2328),
BGP4 (RFC1771), IS-IS (RFC1195).
2 Multicast routing protocols support : IGMPv1,v2 (RFC 2236), PIM-SM (RFC2362) and PIM-DM, M-BGP
3 Should have full IPv6 features.
4 Should have RIPng and OSPFv3 for IPv6.
5 Should have MPLS Features: MPLS VPN (L2 & L3), MPLS TE, DiffServ-Aware TE
F. QoS Features:
1 Classification and Marking: Policy based routing, IEEE 802.1p
2 Congestion Management: WRED, Priority queuing, Class based queuing
3 Traffic Conditioning: Committed Access Rate/Rate limiting
4 Signalling: RSVP
5 Link efficiency mechanisms: cRTP, LFI, MLPPP
6 Per VLAN QoS. Time Based Shaping and Policing for QoS
G. Security Features:

1 Support for GRE Tunnelling, NAT, L2TP/IPSECS tunnelling
2 Support for MD-5 route authentication for RIP, OSPF and BGP
3 Shall support multi-level of access
4 Support for SNMPv3 authentication, SSHv2
5 AAA support using Radius and/or TACACS
6 Support for PAP and CHAP authentication for P-to-P links
7 Multiple privilege level authentications for console and telnet access through Local database or through an
external AAA Server.
8 Time based & Dynamic ACLs for controlled forwarding based on time of day for offices
9 IEEE 802.1x support for MAC address authentication
H. Management
1 Shall have support for Web based management, CLI, Telnet and SNMPv3
2 Shall support Secure Shell for secure connectivity.
3 Shall support Out of band management through Console and external modem for remote management

11.8.21 Video Conferencing Equipment for AMC
Video Conferencing Equipment, Make: Tandberg, Model: Edge95MXP
SL Specification
1. Conference room equipment
The system should support Video standards -H.261,H.263, H.263 ++,H.264
H.264 should be possible when sending or receiving two live video sources e.g. Presenter and Presentation.
The system should support H.323 and SIP simultaneously
The system should support H.239 in both H.323 and SIP calls
It must be possible to enable or disable H.239 while in the Video call
Should be HD compatible and must support HD Resolutions: 720P
The system should support 16:9 and 4:3 aspect ratio
The system should support frame rate -15 fps up to 200 Kbps, 30 fps --200 Kbps and above.
The system Should support H.239 protocol for data sharing
The system should support the following Video Input

1 x 9 PinDSUB: HD Main Camera
1 x MiniDin, S-video: auxiliary/document camera
1 x RCA/Phono, composite: document camera/aux
1 x RCA/Phono, composite: VCR
1 x DVI-I: PC.

SL Specification
The system should have inbuilt capability for audio from PC /laptop during H.239 Video call
The system should support following Video Output

1 x MiniDin, S-video: main monitor
1 x RCA/Phono, composite: main monitor or VCR
1 x RCA/Phono, composite: dual monitor or VCR
1xDVI-1/XGA: main or second monitor
XGA Output
The system should support G.711, G.722, G.722.1, G.728, 20KHz audio or better and VCR Ducking
AUDIO INPUTS (4 INPUTS)

2 x microphone, 24V phantom powered, XLR connector
1 x RCA/Phono, Line Level: auxiliary (or VCR Stereo L)
1 x RCA/Phono, Line Level: VCR/DVD (Stereo R)
AUDIO OUTPUTS (2 OUTPUTS)

1 x RCA/Phono, S/PDIF (mono/stereo) or Analogue
Line Level: main audio or Analogue Stereo L
1 x RCA/Phono, Line Level: VCR or Analogue Stereo R
Bandwidth on IP H.323 : 1Mbps for point to point HD resolution
The system should be upgradable to support ISDN in future on the same endpoint
The system should support H.323 features:

IP precedence (QOS), DiffServe.
Resource reservation protocol-RSVP

SL Specification
IP Type of Service-TOS
Standards based- Packet Loss Recovery feature on H.323 call
The system should have the capability to get upgraded to multiconferencing capability in future to connect
1+3 video sites plus at least 1 audio sites in the following mode--4 party Continuous presence, Voice switched
and Chair control , Audio & video transcoding, rate matching, H.264 & H.239 in multipoint call. It should be
possible to add multipoint calls on the fly without having to disconnect calls
When hosting a multipoint call, the system should not typically stop showing content when the fourth
participant joins the call.
The IP and 3x BRI ports and data sharing should be on backplane on the codec
Meetings both point and point and multipoint , should be password protected and the same should be
possible for H.323 and SIP networks
H.233, H.234, H.235. 'AES' encryption of IP and ISDN calls. Call should be encrypted end to end even in a
multiconferencing.
Should be 1/3" CMOS camera
Should have 7X zoom or better. Camera and Codec should be from same OEM
42° vertical field of view
72° total vertical field of view

SL Specification
250° total horizontal field of view
Should have 70 degrees horizontal Field Of View
IPV6 and IPV4 dual standard
The PC Presentation Port, ISDN Ports and IP Interface should be on the back plane of the Codec
11.8.22 Large Format Video Display for AMC
Large Format Video Display , Make: SAMSUNG, Model: 4000MX2

Specification
40” LCD Display with HD capable with wall mounting kit

Specifications :Panel : 40" Diagonal Size, Professional series panel, 1920 x 1080 (16:9 aspect ratio)
resolution, 450 cd/m2 brightness, 4000:1 contrast ratio, 178/178 viewing
angle (H/V) , 8ms response time (G-to-G) Connectivity : VGA, DVI-D, Composite, HDMI video input, RCA
(L/R), Stereo mini jack audio input, RCA (L/R) audio output, RS232c (in/out) external control Features : Anti
image retention, temperature sensor,
lamp error detection, built-in fan, built-in speakers (10W+10W), RS232 CMDC, Video wall feature, pivot
display, button lock Certification : UL, FCC, Energy star 5.0

11.8.23 Rack Servers for AMC
Rack Servers, Make:HCL, Model: Infinity Global Line 2700hc
Specifications
Intel Xeon Quad Core E5620 or higher
Intel 5520 Chipset
4 GB DDR3 Registered Expandable up to 186 GB
6 Port SATA On board Controller
Dual Gigabit Ethernet Port
1 * PCI Slot, 1 *PCI X8 Slot, PCI X16 Slot
2* 500 SATA II Hot Swap Hard Disk
DVD Writer
Hot Swap Redundant Power Supply
11.8.24 Technical Specification 24 Port managed L2 Switch for AMC
24 Port managed L2 Switch, Make: DAX, Model: Dx5024GS

Specifications


Specifications
L2 Stackable Managed Switch having 24x10/100/1000BaseT ports with 4xcombo SFP slots
Switching Capacity should be at least 68Gbps
Packet Forwarding Rate should be at least 50.60 Mpps for 64-byte packet size
The Switch should have following L2 features from Day-1
1. MAC Address Table size: At least 8000
2. Jumbo Frame Support
3. IGMPv1 v2 with at least 256 IGMP snooping groups, MLD Snooping v1 v2,
4. IEEE802.1D STP, 802.1w RSTP, 802.1s MSTP
5. IEEE 802.3ad Link Aggregation
6. Port mirroring for TX/Rx/Both. One-to-One mode, Many-to-one mode
7. IEEE 802.1Q VLAN, at least 256 Static VLANs, 256 Dynamic VLANs Groups, GVRP, Voice-VLAN
The switch should have 802.1p support with 4 queues per port


Specifications
The Switch should have following Management features from day-1: Web-based GUI, CLI, console port,
Telnet Server, Telnet client, TFTP Client, SNMPv1v2cv3, DHCP Client, DHCP Relay, Multiple Image,
SNTP
11.8.25 Desktop Systems for AMC
Desktop Systems, Make:HCL Model: Infinity Orbital e075pro

Sl No. Item Complete Description
1 Processor Intel Dual Core E5500 / AMD Athlon X2 215

2 Motherboard & Intel G 41 /NVidia GeForce 7 Series or better chipset
Chipset based motherboard with minimum one PCIe & one
PCI/PCIx slots. Motherboard should be of Small Form Factor (SFF)/ Micro ATX form factor
supporting 1066 MHz FSB.
3 Video Integrated Graphic controller
4 Network Integrated Gigabit Ethernet controller
5 Ports 1x fast serial port, 4x USB 2.0 ports (2 ports on front ), 1xKeyboard port, 1xMouse port
6 HDD Controller Integrated dual port SATA-II controller
7 Memory 2GB DDRII /DDR III 800MHz or higher
expandable up to 8 GB
8 Storage 250GB sata II HDD 7200 RPM
Optical Drive DVD writer
Monitor 18" TFT or more (4:3 aspect ratio) LCD Flat Monitor 1280 x 1024 resolution with 5 ms or
better response time, TCO 03 certified

Desktop Systems, Make:HCL Model: Infinity Orbital e075pro

Sl No. Item Complete Description
Power System with Power management features & Desktop Management Interface implementation
Management &
DMI
System Chassis Small Form Factor System chassis of volume not more than 14 litre with suitable power
supply having active power factor correction feature to sustain full load including possible
future up gradations and with minimum one free internal peripheral bay (3.5”)
OS Support & Linux (XP & VISTA) & Linux
Certification
11.8.26 ON-LINE UPS (3KVA) SINGLE PHASE INPUT & SINGLE PHASE OUTPUT for AMC
ON-LINE UPS (3KVA)SINGLE PHASE INPUT & SINGLE PHASE OUTPUT, Make: Uniline Model: Maxi power
1 Capacity 3KVA
Battery Backup 60minutes
2 General
Inverter Technology Pulse Width Modulation (PWM) using IGBTs, double Conversion
Switching frequency 20 KHz or higher
Total Harmonic Distortion < 2% for 100% linear load

(THD) Voltage
< 3% for 100% non-linear load

1 Capacity 3KVA
Operating Temperature 0º- 50º C
Output Wave Form Pure sine wave
Cooling Air Cooled
3 Input
Frequency range 50 ± 6% Hz
D/G set comp ability Required
Input Power Factor 0.9 or better at full output load leading to Unity with power factor correction
(PFC)
4 Output
Voltage 230V AC +1 %, single phase

2. 0.6 lag to Unity PF

1 Capacity 3KVA
Frequency 50 Hz + 0.5 %
5 Efficiency
Overall Efficiency 80 % or better on rated full load of 0.8 PF & 230V, 50Hz AC output
Inverter Efficiency 90% or better on rated full load of 0.8 PF & 230V, 50Hz AC Output
6 Overload Capacity 110% for 2 min. & 125% overload for 30sec.
7 Load Power Factor 0.8 lagging
8 Protection Required for :

Short Circuits
Over Loading
Over Temperature
Input low/ high voltage control
DC low/high voltage trip
9 Battery Make CSB / Panasonic / Global Yuasa / Exide / Orchid / Okaya /Amar Raja make
complying with JIS C 8702 test.
Battery recharge time (after Battery recharge time should not exceed 8 hours and charger should be
complete discharge to 100% capable to charge battery on C10 rating.
charge) & charge rating

1 Capacity 3KVA
11 Battery Capacity
Capacity of D.C.Bus Battery Bank for Back-up Time

UPS
Voltage
3KVA <192 V 60minutes
UPS & Battery Housing Powder coated UPS & battery cabinet with caster wheel should of minimum
1mm thick good quality material and should be free from sharp edge,
scratches, nicks, & burs etc.
Enclosure should conform to protection requirement of IP2L1 to IS13947
(Part 1)/1993 (reaffirmed 2004).
12 L.C.D. meter To measure and monitor input voltage, output voltage, output current, DC
current, DC voltage, input / output frequency
13 Indications Mains on /Load on Battery/ Inverter/ Battery level/ Load level/ Inverter
over load
14 Audible Alarm Over Temperature/ Main failure/ Battery low/ Inverter Overload
15 Switches Main ON/OFF MCB / Battery ON/OFF MCB/ Inverter push button with reset.
16 Output Connection O/P Terminals of standard quality should be provided.

03 Nos. of 5/15A/230V female ISI/ IEC Mark socket
17 Isolation Transformer Galvanic Isolation through Transformer

11.8.27 Specifications of Ku band VSAT & the architecture
1 VSAT Network Details
Technology The VSAT network shall provide Star connectivity using the latest technology
using TDM/TDMA/FTDMA/ MFTDMA or better technology for connectivity.
Outbound Data rate One aggregate outbound with size software configurable from 2 Mbps to 81 Mbps
from the hub without any hardware changes.
Inbound Data Rate The proposed system should support multiple inbounds of 128/256/512/1024
ksps as minimum and upgradeable up to 1.6 Mbps using the same IDU and having
M: N redundancy, where M is total number of operational demodulators and N is
the number of standby demodulators.
2 Network Management A complete Network Management System (NMS) for monitoring all the circuits,
remote terminals is required
Configuration Management The NMS should support monitoring, control and configuration of the entire
network by means of user friendly Graphical User Interfaces. NMS should be
capable of software upload to all VSAT’s within the network.
Accounting Management The NMS should have necessary BW management features. NMS should be able to
switch off the operation of any VSAT if required.
Security Management The NMS should have necessary security features for management, administration
and operation. NMS should have different levels of password protection for
system administration, management and operation etc.

Performance Management The NMS should be SNMP compliant and reports regarding BW usage, UP time etc.
can be generated. The NMS should be able to manage the entire enterprise wide
network from a single point i.e. the service provider HUB.
Fault Management The NMS should have inbuilt features of Fault management system to guarantee
maximum uptime.
3 VSAT Terminal
Configuration
Compatibility with the The VSAT IDU should support TCP/IP without the need of an external router. The
latest Network/IP Protocols IDU should support important IP protocols and functionalities, without any
and Acceleration features external device like –
TCP Acceleration
QOS definitions for different IP traffic applications
Access Mechanisms like dedicated access, Bandwidth on Demand, Slotted Aloha

depending upon the IP applications
Protocol support - IPv4, Unicast, Multicast, IGMP, Routing (RIP v1 & v2), Telnet,
ARP, ICMP, FTP
Internal Processor & The IDU should have a processor with speed of min 300Mhz with internal
memory memory of 64MB.The IDU should have dual memory banks each for storing the
software and the firmware to provide added robustness. In case the software or
firmware in the respective primary banks crashes or is changed, the terminal shall
be able to use the backup bank to come up.

Flash Updates The terminals should be able to take the software and firmware downloads from
the hub over the air, without any disturbance to the online user traffic while in
operation on per terminal (Unicast), per group (Multicast) or entire network
(Broadcast) basis
4 Out Door Unit
Power Output 2W
Transmit Frequency 13.00GHz to 14.5GHz
Input Frequency Range 107.42MHz to 113.28MHz
DC power requirement <=19V @ 1.7A (2W)
5 LNB
Receive Frequency 10.95 – 12.75GHz
Input VSWR 3.5 :1 (Max) @ room temperature
Noise Temp 70K typical
Output Frequency 950 –1700MHz
Conversion Gain 50 – 60 dB
Conversion Gain Variation +/- 3 dB
Temperature Range -400C to +550C

6 Indoor Unit
Transmit
In route Data Rate up to 1.6 Mbps
Symbol Rate 128, 256, 512, 1024 Ksps
Modulation QPSK/BPSK/GMSK / OQPSK or better
In route access TDMA/FTDMA/MFTDMA
Bit Error Rate 10-7 or better
FEC Coding ½ ,Turbo code ½, 2/3 and 4/5 to 7/8
Receive
Out route Data Rate Up to 121 Mbps
Symbol Rate 1 – 45 Msps (in 1 Msps steps)
Modulation QPSK/ 8PSK /GMSK or better
Bit Error Rate 10-10 or better
Frequency Range Ku band / Ka-band
Physical Interface
No. of Ethernet ports 1

Ports Interface One 10/100BaseT Ethernet LAN RJ45 port
Port Speeds 10/100 Mbps
Data transport protocol TCP/IP, UDP
IP protocol support ARP, ICMP, IGMP
Access schemes on Inbound TDMA/FTDMA/MFTDMA
Access to terminal console Internet Browser and through Telnet
Management from NOC Remote terminal management via the Network Management System.
Configuration, status monitoring, and commissioning via the NOC

11.8.28 MPLS VPN Router Specification

1 Architecture
The router should be a modular platform with two integrated serial interface (with
required cables) and at least one additional slot to provide connectivity. The
additional slot should support all sorts of combinations for future upgrades
including V.35 Serial Links, 3G Wireless, ISDN, etc. The router should be able to take
total 8 Serial links.
The router should be powered by processor to support growing demands of branch-

office networks by supporting high-throughput WAN requirements.
It should support embedded hardware encryption acceleration enhancement to

provide higher scalability, which should support WAN link security and VPN services
(both IPsec and SSL acceleration).
On Board LAN 10/100/1000 Ports – At least two
Memory (DRAM) – At least 512 MB--
Flash – At least 256 MB
Console Port – 1
Auxiliary Port – 1
Should support PoE (not required from Day 1)
USB Port – At least one high-speed USB 2.0 port. The USB port can be used to enable
another mechanism for secure token capabilities and storage.

2 Performance
Shall support high performance traffic forwarding - at least 1000 Kpps with 64 byte
packet size.
Shall support other IP Services like GRE tunnelling, ACLs, IPSEC VPNs, Firewalling,
NAT services, Zone based Firewall, IPS and content filtering from Day1
Shall support Voice traffic optimization with features like QoS, Class-Based Weighted
Fair Queuing (CBWFQ), Weighted Random Early Detection (WRED), Hierarchical
QoS, Policy-Based Routing (PBR), Performance Routing (PfR), and Advanced Routing
Support for intelligent power management
3 High Availability
Shall support redundant Gigabit Ethernet connection to LAN
Shall support fast reboot for minimum network downtime
Shall support boot options like booting from TFTP server, Network node and Flash
Memory
Shall support multiple storage of multiple images and configurations
Shall support link aggregation using LACP as per IEEE 802.3ad
Shall support VRRP or equivalent
4 Protocol Availability

Should support Routing protocols like IS-IS, RIP v1 & RIP v2, OSPF ver2, BGP4
Should support Multicast routing protocols IGMPv3, PIM-SM, PIM-SSM or equivalent
Should support IPv6 QoS, RIPng, OSPFv3
Shall support MPLS
Support for Load balancing Protocol.
Configuration Roll Back to recover the mis-configured router to last good

configuration
5 Encapsulation Support
Should support Encapsulation like Ethernet, 802.1q, PPP, MLPPP, FR, MLFR, HDLC,
V.35, PPPoE
6 Security Features
Support Standard ACL, Extended ACL, ACL that can match arbitrary bits of packet
bits of a packet at an arbitrary depth in the packet header and payload
Should have features for IPSEC Site-to-Site and Remote Access VPNs. Any Office to
Any other office, dynamic establishment of VPNs so that the configuration &
management of IPSEC VPNs becomes easier and SSL VPN
Support Content filtering
MD-5 route authentication for RIP, OSPF and BGP

Shall support multi-level of access
SNMPv3 authentication, SSHv2
AAA support using Radius.
CHAP authentication
IP Access list to limit Telnet and SNMP access to router
Multiple privilege level authentications for console and telnet access through Local
database or through an external AAA Server.
Time based ACLs for controlled forwarding based on time of day for offices
7 Debug, alarms &

Diagnostics
Support for monitoring of Traffic flows for Network planning and Security purposes
Trace-route, Ping and extended Ping
Shall support functionality that enables automation of many network management

tasks and directs the operation of router OS to increase availability, collect
information, and notify external systems or personnel about critical events
8 Accounting
The router should have following accounting features:

Packet & Byte Counts
Start Time Stamp & End Time Stamps.
Network Time Protocol
Input & Output interface ports.
Type of service, TCP Flags & Protocol
Source & Destination IP addresses
Source & Destination TCP/UDP ports
9 Management
Shall have support for Web, GUI based management, CLI, Telnet and SNMP
Embedded RMON support for four groups – history, statistics, alarms and events
Should have to support Out of band management through Console and an external
modem for remote management.
Event and System logging: Event and system history logging functions shall be
available. The Router shall generate system alarms on events. Facility to put selective
logging of events onto a separate hardware here the analysis of log shall be available.
Pre-planned scheduled Reboot Facility: The Router shall support the preplanned
timed reboot to upgrade their hardware to a new software feature and plan the
rebooting as an off-peak time

10 Interface
Requirements
4 x 2Mb WAN Interfaces with V.35 connection
4 x Gigabit Ethernet Interfaces
11.8.29 Technical Specification for Database Servers
S. Parameter Complete Description

No
1 Processor Latest Generation x86-64 Bit Minimum Hexa-Core Processor with Minimum 1.86Ghz Clock
Speed and 12MB Cache with QPI Technology
2 Number of Offered Server should be configured with 4 (Four) Processors

Processors
3 Memory 64 GB DDR3 Memory Per Server
4 Memory Memory Should be Scalable up to 256 GB

Scalability
5 PCI-Express Slots Server Should Have Minimum 4 * PCI Express Slots
6 Network Minimum 4 * 10GbE NIC Ports

Interface Ports
The NIC Ports should support FCoE & iSCSI

S. Parameter Complete Description

No
7 FC-HBA Ports 2 * 8 Gb/s FC-HBA Ports
8 Internal RAID Internal RAID Controller should be able to do RAID 1,0
9 Internal HDD Minimum 4 * 50GB Internal SSD/ Minimum 2 * 300GB Internal SAS SFF Hot Plug HDD
10 Pre-Failure Critical Components like CPU, Memory, SSD & PCI Slots should be covered under Pre-
Warranty Failure Warranty
11 OS & MS Windows, RHEL, SLES, OEL, Oracle Solaris, VMware Sphere & Microsoft Hyper
Virtualization
Infrastructure
Support
12 I/O & Power Server Should have redundant power supply (Connector) and redundant I/O Connector.
Supply(Connecto
r) Redundancy
13 Form Factor Blade
11.8.30 Technical Specification for Application Servers
Sl Parameter Complete Description
1 Processor Latest Generation x86-64 Bit Minimum Hexa-Core Processor with Minimum 1.86Ghz Clock

2 Number of Offered Server should be configured with 4 (Four) Processors

Processors
4 Memory Memory Should be Scalable up to 256GB

calability
6 Network Minimum 4 * 10GbE NIC Ports

Interface Ports
The NIC Ports should support FCoE & iSCSI
7 FC-HBA Ports 2 * 8Gb/s FC-HBA Ports
9 Internal HDD Minimum 4 * 50GB Internal SSD/ Minimum 2 * 300GB Internal SAS SFF Hot Plug HDD
10 Pre-Failure Critical Components like CPU, Memory, SSD & PCI Slots should be covered under Pre-
11 OS & MS Windows, RHEL, SLES, OEL, Oracle Solaris, VMware Sphere & Microsoft HyperV
Virtualization /CentOS 5
Infrastructure
Support

Supply
(Connector)
Redundancy
11.8.31 Technical Specification for Mail Servers
1 Processor Latest Generation x86-64 Bit Minimum Six Core Processor with Minimum 2.53 Ghz Clock
2 Number of Offered Server should be configured with 2(Two) Processors

Processors
4 Memory Memory Should be Scalable up to 128 GB

Scalability
6 Network Minimum 2 * 1GbE Ports

Interface Ports

7 FC-HBA Ports Minimum 2 * 8Gb/s FC-HBA Ports
9 Internal HDD Minimum 2 * 300GB Internal SAS SFF Hot Plug HDD
10 Pre-Failure Critical Components like CPU, Memory, HDD & PCI Slots should be covered under Pre-
11 OS & MS Windows, RHEL, SLES, OEL, Oracle Solaris, VMware Sphere & Microsoft Hyper
Virtualization
Infrastructure
Support
Supply(Connecto
r) Redundancy
11.8.32 Technical Specification for Infrastructure Servers
1 Processor Latest Generation x86-64 Bit Minimum 6-Core Processor with Minimum 1.86Ghz Clock
Speed and 18MB Cache
2 Number of Offered Server should be configured with 8 (Eight) Processors


Processors
3 Memory Minimum 128 GB DDR3 Memory Per Server
4 Memory Memory Should be Scalable Minimum up to 2 Terabytes within the existing enclosure
Scalability
6 Network Minimum 12 * 1GbE Ethernet Ports Per Server

Interface Ports
Minimum 1 * 10/100 Mb/s Port for Server Management
7 FC-HBA Ports Minimum 6 * 8Gb/s FC HBA Ports / Server
8 Internal RAID Internal RAID Controller with minimum 512MB battery Backed Write Cache
9 Internal HDD Minimum 8 * 300GB Internal SAS SFF Hot Plug HDD Per Server
10 DVD Internal DVD-RW
11 Power Supplies Redundant Hot-Swappable Power Supplies Configured in N+N Mode
12 Fans Redundant Hot Swappable Fans
13 Pre-Failure Critical Components like CPU, Memory, HDD and PCI Slots should be covered under Pre-
14 OS & MS Windows, RHEL, SLES, OEL, Oracle Solaris, VMware VSphere & Microsoft HyperV
Virtualization
Infrastructure


Support
15 Form Factor Rack-Mount
11.8.33 Technical Specification for Blade Enclosure
1 Blade Chassis Solution to house the required number of blade servers in smallest number of enclosures,
occupying a maximum of 10U rack height per enclosure
Same enclosure should support Intel Xeon, AMD Opteron and RISC/EPIC blades. Enclosure
should also support Unix, Linux and Windows Operating environment.
Should have Hot Pluggable & Redundant Management Modules.
Should provide a highly reliable and high performance redundant mid-plane/back-plane

design in the blade enclosure. Should provide detailed technical information.
Should be able to accommodate the blade servers mentioned in the sections below in the
proposed blade enclosures.
Support simultaneous remote access for different servers in the enclosure.
2 LAN Interconnect Two or Four network ports from each of the servers in the enclosure should be available
on 10 Gigabit LAN switch / Link Aggregation Module / Pass-through to connect to external
network devices...

3 Fibre Channel Redundant 8GB Fibre Channel Pass thru Interconnect modules to direct HBA cards to SAN
Interconnects Switch/Storage.
4 MAC Address & Blade Enclosure should preferably support management & deployment of MAC Addresses
WWN of NIC Adapters and WWN No of FC adapters at the chassis level so that replacement of a
Management server blade does not involve Network & SAN configuration effort at the blade level
5 Power Supply The enclosure should be populated fully with power supplies of the highest capacity &
energy efficiency available with the vendor. Power supplies should support N+N as well as
N+1 redundancy configuration, where N is greater than 1. Guaranteeing complete
availability even on failure of any 2 power supplies across the enclosure
6 Cooling Each blade enclosure should have a cooling subsystem consisting of redundant hot
pluggable fans or blowers enabled with technologies for improved power consumption and
acoustics
7 Redundancy The Midplane/Backplane, all interconnect switches the power bus running across the
chassis should be in redundant configuration
8 System Software Management/controlling software have to be from the same OEM
9 Remote Must provide a remote management functionality to operate the server in both in-band and
Management out-of-band. Must be part of the server without the need to install any additional hardware
or software
Must have Real-time Virtual KVM functionality and be able to perform a remote Power
sequence. Must provide both Java & Java-free browsing options.
Power Must be able to show the actual power usage and actual thermal measurement data of the
Management servers.

11.8.34 Technical Specification for SAN Storage (1 at DC, 1 at NR and 1 at DR)
Parameter Specification
Controllers The proposed SAN array shall be configured with dual Active-Active controllers for
redundancy with dedicated cache mirroring interface between controllers
Front-End & The proposed SAN array shall be configured with minimum 8x8 Gb/s FC front end host
Back-End Ports ports, & 8 x 4Gb/s FC Back end ports spread across dual controllers.
Cache & Cache The proposed SAN array shall be configured with at least 16 GB total usable cache for data,
backup across dual controllers. Cache shall be mirrored between the controllers. Entire cache
should be available for a single LUN.
Offered Capacity The proposed SAN array shall be configured with minimum 12 TB using 450 GB 15k rpm
dual ported FC drives in RAID 5.
Maximum Usable The storage system should be scalable up to minimum 150TB of usable capacity using fibre
Capacity channel disk drives. The maximum capacity is considered using maximum 30 spindles per
device (back end) port in the same ratio of disks as currently proposed
Disk IOPS The array should be configured to deliver at least 10000 disk IOPS at less than 10
milliseconds response.
Bidder should enclose OEM certification for the given performance for proposed
configuration and public document for the required performance scalability
RAID Levels The Proposed SAN Array should support RAID Levels 1 or 10, 5 and 6

Replication The Storage Solution should be provided for a 3-Site DR Architecture where Primary
Solution & Near Recovery Sites should replicate Synchronously and Simultaneously Primary
& DR or NR to DR should Replicate Asynchronously.
The offered Replication Solution should preferably be Array based, however, in case
Array Based 3-Site replication is not available with the offered storage, an Operating
System & Database independent third party proven 3-Site replication solution has to
be offered. All the necessary hardware & software required for 3-Site replication
should be offered along with the solution
Snapshots & Offered Storage must include snapshots & volume clones licenses
Volume Clones
11.8.35 Technical Specification for SAN Switch (1 at DC, 1 at NR and 1 at DR)
Architecture Switch Should have Completely Non-Blocking Architecture
Fabric Bandwidth Switch Should have minimum 680 Gb/s Fabric Bandwidth
Port Speed Ports should be configured with at least 8 Gb/s FC SFPs and should auto-negotiate to 2/4
Gbps speeds
QoS Switch Should support Quality of Services
ISL Trunking Switch Should include ISL Trunking / link aggregation up to minimum 64Gb/s

Power Supply Switch Should be Configured with redundant Power Supplies and Fans
and Fans
Number of Ports 24 ports
Form Factor Rack Mount
11.8.36 Technical Specification for Tape Library
Drive Type LTO5
Minimum No of 4
Drives
Drive Scalability Up to 8 drives
No of Slots Minimum 100
Slot Scalability Up to 400 slots
Power Supplies Redundant Power Supplies
User Interface Touch Screen Graphical Interface
Cartridges 100 LTO5 barcode labelled cartridges & 10 cleaning cartridges from the tape library


OEM
11.8.37 Technical Specification for Backup Software
Support of SAN Proposed backup solution should provide Online SAN based backup agent on all database
Based Backup servers with LAN based (open file support) on all app/web servers
Linux Compatible The proposed Backup Solution Software has inbuilt Java / Web based GUI for centralized
Software management of backup domain and Linux supported Backup server
Disk Staging Software must have integrated true Disk Staging feature, wherein the backup continues to
Feature take place even when the disk space allocated is full. The backup software must be
intelligent enough to flush out the data from the disk and migrate the same to the tape
automatically based on the user defined threshold & will not affect the backup operations.
Bidder must quote the licenses for disk based backup
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
Incremental The software should support for ever incremental backup & there should not be a need to
Backup do a Full back up again
Entire Server The software should have capability to back up the entire configuration of the server and
Backup restore it from scratch the entire system including configuration when in a scenario of
hardware failure

Backup Software is able to rebuild the Backup Database/Catalogue from tapes in the event
of catalogue loss/corruption.
Database support The proposed Backup Solution has certified real time backup solution for different type of
Databases such as Oracle, MySQL, Postgres etc.
The proposed solution should have Bare Metal Recovery agent on database servers
Individual File The Proposed backup solution shall provide granularity of single file restore
Restore
The Proposed backup solution shall be designed in such a fashion so that every
client/server in a SAN can share the robotic
Backup Solution shall be able to copy data across firewall
Backup Solution shall support automatic skipping of backup during holidays
Should support backup Polices to be defined centrally & should be applied to Data, not
restricted to tape media’s. This is to optimally reuse the tape media.
The software should have capability to retrieve selectively based on search criteria
The Backup Software shall provide restart-able restore in case of any failure during a
Restore operation
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 have the capability to reclaim the media back in to the new
backup process even if the 50% of the data had expired in the backed up media. The
reclamation threshold should be user configurable
The Backup software must have an integrated RDBMS as the catalogue and must not use
Flat file system to store the backup data.
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
11.8.38 TECHNICAL SPECIFICATIONS FOR ON-LINE MODULAR UPS FOR DATA CENTRE (20 KW IN N+1 CONFIGURATION)
Sl PARAMETERS SPECIFICATIONS
1 Capacity 20 KW using Hot pluggable modular UPS
Battery Backup 30 Minutes at full load of 20 KW
Supported Should equip to utilize the UPS modules in N+1, N+X and N+N configuration.

Configurations
2 General
Technology Pulse Width Modulation (PWM) using IGBTs in inverter & Rectifier section, Online double
conversion
Switching Free running Frequency

frequency
Operating 0º- 40º C

Temperature
Crest Factor N o t less than 3:1 on full non-linear load
Humidity Up to 95% non-condensing
Output Wave Pure Sine wave

Form
Cold Start facility Required
Cooling Air cooled
Isolation UPS should be equipped with suitable capacity of isolation transformer in input side
3 Input Three Phase AC

Frequency Range Always better than 0.9 at non-linear load of above 25% to 100% under any input conditions
defined above.
Input Power Less than 5% on Full load and not more than 10% at 25% load
Factor
D/G set Required

Compatibility
4 Output
Voltage 415V AC +1 %
2. 0.6 lag to Unity PF load 35
Frequency (a) 50 Hz + 0.5 %
5 Efficiency
Overall Efficiency 85 % or better on rated full load of 0.8 PF
90% or better on rated full load of 0.8 PF
6 Overload 125% for 10 min. & 150% overload for 60sec.

Capacity
7 Load Power 0.6 lagging to unity

Factor
8 Transient For 100% load change, output must remain within ±5% and recovery within 20 ms.
Response
Time
9 Protection Should be equipped with protection for Short Circuits, Over Loading, Over Temperature,
Input low/ high voltage control and DC low voltage trip.
10 Battery Bank
Details
Battery Type Sealed Maintenance Free (VRLA)
Battery Make Any good National or International brand complying with JIS C 8702.
Battery recharge Battery recharge time should not exceed 8 hours and charger should be capable to charge
time (after battery on C10 rating.
complete
discharge to
100% charge) &
charger rating
Battery Cut off Not less than 1.75V/cell

voltage during
backup

11 Battery Capacity
Capacity of UPS Battery Bank for Back-up Time of 30 minutes
20KW > 18000VAH
UPS & Battery Single UPS Rack suitable to house above asked Hot pluggable rack mountable modular
Housing UPS. The cabinet should be of good quality material; powder coated and should be free
from sharp edge, scratches, nicks, & burs etc. UPS rack should preferably have option to
house batteries inside for 30 minutes battery backup. Rack should conform to all protection
requirements.
LED Indications/ Mains on, Load on Battery, Inverter, Battery level, Load level Inverter over load
Mimic Diagram
LCD Panel Required (For measuring input & output parameters)
Audible Alarm Over Temperature, Main failure, Battery low, Inverter Overload
Switches / Main ON/OFF

Isolators
Output ON/OFF
Battery ON/OFF
Manual Bypass
Inverter push button with reset.
Output Built in/external Managed power distribution unit to power source server racks.
Connection to
server rack

SNMP Support & Required

Static Bypass
Paralleling UPS Should have desired electronic circuitry to use UPS in parallel up to 4 to make total
capacity of 80 KW and using in configuration of N+1, N+X & N+N
11.8.39 TECHNICAL SPECIFICATIONS FOR DIESEL GENERATORS 50KVA (3Phase)
Sl Component Name Required Specifications
1 CAPACITY 50KVA
2 ENGINE:
COOLING SYSTEM Air cooled, Water/Coolant cooled

REQD.

WATER LEVEL The Water/Coolant cooled system of the engine should be equipped with in built
MAINTENANCE expansion tank so that frequent topping up of water/daily check of water level is not
needed. Only a top up at 250 hours should suffice. Engine should have high quality and
finish to make it a zero leakage system. Similarly the water system should have seals etc.
to ensure no water leakage from the water pump.
OUTPUT The ENGINE continuous duty rated should be capable of developing sufficient output HP
under site temperature conditions of 45 degree C to ensure full output from 50 kVA
Alternator.
MINIMUM HP Not less than 10 B.H.P continuous rated.
SPEED 3000 rpm
FUEL PUMP The pump should be of MONOBLOCK design of MICO or equivalent make to ensure
better governing and easy repair in the field.
GOVERNOR Mechanical / electronic
NO. OF CYLINDERS Single/Multi cylinder, in accordance with is 10001-1981 with latest amendments.
FLYWHEEL Of suitable diameter and weight (indicate the diameter and the weight).
OVERLOAD Engine should be capable of providing 10% overload for 1 hour for every 11hour
CAPACITY continuous running at full load
ENGINE Naturally Aspirated

ASPIRATION
STANDARD THAT IS/BS (IS 10000/BS: 5514/BS: 649).

THE ENGINE


SHOULD MEET
RADIATOR Heavy duty with fan (provide technical details).
SILENCER Residential type with exhaust piping with vibration isolators (provide technical details).
STARTING Equipment like electric motor, battery, charging alternator etc. for electric start
ACCESSORIES Fuel injection equipment, air cleaner, voltage regulator, anti-vibration mounting pads,
speed controlling governor, suitable coupling system to the alternator, tachometer,
lubricating oil temperature and pressure gauge, rpm indicator and hour meter to
indicate number of hrs. Of operation, auto trip on low oil pressure, over speed alarm
with trip, thermal insulation for exhaust line with glass wool, aluminium sheet, chicken
mesh, diesel line of suitable diameter.
PROTECTION Against low lubricating oil pressure, high water temperature shall be provided for
engine with alarm and fuel shut off.
3 ACOUSTIC The enclosure supplied should ensure not more than 5-7 degree C temperature rise then
the outside temperature with natural air circulation. The noise level should not be more
ENCLOSURE
than 75 dB at 1 meter distance. Enclosure should be duly type approved by CPCB
authorized lab. The enclosure must be fitted with sheet steel of 1.2/1.6 mm thickness,
seven tanks retreated and powder coated with pure polyester powder to enable outdoor
installation.
4 FUEL TANK Fuel tank with capacity of 12 hours continuous running at full load with necessary
piping, fuel gauge, drain valve, inlet and outlet connectors complete in all respect.
5 ENVIRONMENTAL Shall meet requirement of rules1986 as laid down by Ministry of Environment & Forest
CONDITIONS read with GSR No. 371 (E) dated: 17.05.2002, GSR 520 (E) dated: 01.07.2003 and GSR
448 (E) dated: 12.07.2004 in respect to emission norms for the engine and in respect of


noise level for the DG sets.
6 ALTERNATOR Self-excited and self-regulated alternator should be of brushless type with VG-I grade of
voltage regulation giving an output of 50 KVA, three phase 230/240 Volts, 50 Hz, 0.8
(lag) power factors, 2 wire close coupled to the Engine. Class of insulation should be
Class "H". Alternator should meet IS 13364 (part-I):1992/2003. Alternator should be
capable of 10% overload for one hour and 50% overload for 15 seconds in 12 hours.
Permissible voltage variation - +/-1.5% of rated voltage.
PROTECTION Screen protected drip proof with IP 21 degree of protection as per IS: 4691/85.
7 AUTO MAINS The AMF control panel shall have the following instruments and accessories:
FAILURE (AMF) a) Microprocessor based genset controller with composite meter for digital display
Of:
CONTROL
i) Output voltage/AC Mains voltage.
PANEL
ii) Output Current.
iii) Power Factor
iv) Frequency.
v) kWh
vi) Three attempts engine start/engine cranking relay.
vii) On-delay timer for load changes over.
viii) On-delay timer for engine shut off.
b) Mode selector switch for setting the panel on any one position such as OFF /auto
/ manual l/ test.
c) Engine ON-OFF switch (Push button type)


d) MCCB of suitable rating shall be provided.
e) Rectangular aluminium bus bars (one number for each phase, neutral and
earthing terminal) of adequate ratings duly colour coded with heat shrinkable
PVC sleeves.
f) Two contactors of suitable rating (one for DG set & one for AC mains) with over
load relay.
g) Under-voltage relay for mains.
h) Battery charger complete with voltage regulator, float or booster selector switch,
ON-OFF switch, voltmeter and ammeter for charging the battery from mains.
This will be in addition to the battery charging alternator fitted on the engine.
(i) Instrument & Control Fuses.
(ii) Five number indicating lamps to indicate 'mains ON', 'load on mains', 'set
running', 'and load on set ‘and’ battery charger on'.
(iii) Audio visual alarm for 'Low lubricating oil pressure', 'High cylinder head
temperature', 'Start failure' and 'DG over load'.
(iv) Any other switch, instrument, relay or contactor etc. essential for smooth
and trouble free functioning of DG set with AMF panel is to be specified in
the offer with complete detail of the item.
The panel should be within the D G set acoustic enclosure.
The system should have an inbuilt By PASS Change Over switch to ensure that in case of
AMF / D G Set failure the mains can get directly connected to the load.
Make of Contactors: Should be specified
Make of Microprocessor: Should be specified
8 BATTERY Battery of very low maintenance - 85 AH or higher lead acid type, Make: Should be


specified
SIZE AND WEIGHT Should be minimum (provide details).
9 INSTALLATION • Earthing connection to terminate the existing earthing

DETAILS
• RCC / PCC Foundation of size as per DG set and having a height above ground of
at least 9 inches.
• Length of input/output cables up to a length of 20 mts.
• 4x10 Sq. mm armoured aluminium cable
• Cable laying - wall supported/open
• Cable laying - under ground
• End termination of Cable - 4 terminations
• Exhaust piping with aluminium cladding (where needed)
• Testing of the DG set at the site for 1 hour and handover
11.8.40 TECHNICAL SPECIFICATIONS CORE ROUTER AT DC
Sl Specifications
A. Architecture
1 The architecture should be based on high performance CPU with convergence of routing,
switching, voice and security.

Sl Specifications
2 The Router should be a single box configuration and should be modular, so that there is
flexibility to use the appropriate choice of interfaces as and when required.
3 Should have at least 6 slots. Each WAN card slot should support a variety of interfaces like
V.35 Syc Serial (2 Mbps), E1, Channelized E1 , ISDN BRI/PRI, E3, Channelized E3, STM-1 etc.
4 Should support Voice Interfaces like FXO, FXS
6 Should have either support for Voice Modules, and High Performance VPN Encryption
Modules
7 Forwarding capability should be at least 1,100 Kpps using 64-byte packet size with QOS
enabled.
9 The Router shall have at least 1GB DRAM and 256 MB Flash
10 Router should have at least 150 Mbps of encryption throughput and support for 1500
tunnels from Day-1.
12 Router should support on-line software reconfiguration to implement changes without

rebooting.
13 Router should have internal Redundant Power Supply for High availability.
B. Interface
Requirements
1 3 x Gigabit Ethernet Interface

Sl Specifications
2 1 nos. of Channelized STM-1 interface
3 8x V.35 interface
C. Software
1 The router shall support following WAN protocols: PPP as per RFC 1661, Multilink PPP,
ISDN, Frame Relay etc.
2 The Router shall support following IP routing protocols: RIP Version 1 & 2, Triggered RIP
support as per RFC 2091 to support demand circuit, OSPF Version 2 as per RFC 1583, BGP 4,
and IS-IS. Multicast Routing support through PIM.
3 Support for NAT as per RFC 1631, Port Address Translation support.
4 IEEE 802.1Q based VLAN tagging
D. Security
1 Access lists based on Network Address, Mask, Protocol Type and Socket Type;
2 MD 5 Route Authentication as RFC 1321, Controlled SNMP Access through the use of SNMP
V.2 with MD5 Authentication.
3 Multiple Privilege levels to provide different level of access.
4 Remote Authentication Dial in user service (RADIUS) as per RFC 2138
5 VPN Support - To Support IP Security (IPsec), AES], 3DES, DES and MPLS

Sl Specifications
6 VPN Encryption - Equipped for Hardware Accelerated Encryption with 280 Mbps
performance.
8 Support for Web VPN (SSL VPN) on the router internal or external
10 Router shall support Network Management through: SNMP, RMON support, Software
Upgrade through FTP or TFTP; TELNET. The Router should also have integrated Web
Interface (GUI) for ease of configuration.
E. Protocols
1 The Router should be MPLS (Multiprotocol Label Switching) Ready with the following MPLS
Features:
2 MPLS Diff-Serv-Aware Traffic Engineering (DS-TE)
3 MPLS Label Distribution Protocol (LDP/RSVP)
4 MPLS QoS - DiffServ Tunnel Mode Support,
5 MPLS Traffic Engineering (TE) - Automatic bandwidth adjustment for TE tunnels
6 The Router should be IPv6 (IP version 6) Ready from day 1.
7 Secure Services Management - To Support SSHv2 and SNMPv3 protocols to encrypt the
management session.
F. High
Availability

Sl Specifications
1 Power Redundancy - Equipped with internal Redundant Power Supply.
2 USB Flash Memory - To Support USB Flash memory for ease of image recovery
3 Online insertion and removal - Should support online insertion and removal
G. Multimedia
and QoS
support
1 A class-based scheduling/queuing mechanism that provides configurable minimum

bandwidth allocation to each class
2 Should support Congestion Management mechanisms such as Priority Queuing, Custom

Queuing, Weighted Fair Queuing etc.
3 Should support Congestion Avoidance mechanisms such as RED / WRED
6 RSVP: Resource Reservation Protocol (RSVP) as per RFC 2205
7 Should support Policy-based Routing
8 IGMPv2, v3: Internet Group Management Protocol Version 2 & 3
9 Multicast routing support such as Protocol Independent Multicast (PIM) - Sparse Mode and
Dense Mode.
11 Integrated Web-based device-management tool embedded in the router; and should be

accessed remotely for faster and easier deployment of routers for both WAN access and
security features.

11.8.41 Specification of Core Switch at Datacentre
Sl Specification
1 Chassis based Architecture, with minimum 5 payload slots for switching and one slot should be free for future
expansion.
2 Should have 500 Gbps switch fabric.
3 Packet forwarding rate for 64-byte packets required at least 210 million packets per second forwarding rate
at Layer 2, 3
4 The Switch should have the following interfaces from Day 1:

48 x 10/100/1000 BaseTx interfaces
12 x 10Gbps interfaces SFP ports
5 There should not be any service degradation due to failure of power supply or CPU.
6 Redundant power supplies, fan and CPU from day 1. The Switch should be able to take redundant switching
fabric/CPU with similar feature and Capacity.
7 Hot swappable chassis Components such as power supply and interface modules
8 Support for 2000 Active VLANs.
9 Layer 3 features, VRRP or equivalent to create redundant, Static IP routing, RIPv1&2, OSPF.
10 Standard and extended ACLs on all ports. Should support integrated firewall module
11 Should support 802.1x user authentication

Sl Specification
12 Should have support for Ipv6
13 CoS: Should support port-based COS assignment and CoS trust
Queue per port: Should have minimum 8 hardware queues per port
14 Mac address table size of 50,000 entries and Routing entries capacity of 256,000 on the CPU.
11.8.42 TECHNICAL SPECIFICATIONS SERVER FARM ACCESS SWITCH AT DC
Sl Parameter Specification
Architecture
● The Switch should have 24x10/100/1000Mbps Copper Ethernet ports with 2x10Gbps
SFP+ Based Fibre Uplinks port and 4 x1Gbps SFP Port
● Dual redundant, modular power supplies and fans
● Media Access Control Security (MACsec) hardware-based encryption
Performance
Switching Fabric should be 160 Gbps Capacity
The switch throughput should be 65Mpps

Memory: DRAM 256 MB, Flash 128MB
Total VLANs 1000
● Dynamic Host Configuration Protocol (DHCP) auto configuration of multiple switches

through a boot server
● Automatic QoS (AutoQoS) configuration
● Auto negotiation on all ports should automatically select half- or full-duplex transmission
mode
● Should facilitate dynamic trunk configuration across all switch ports.
● Link Aggregation Control Protocol (LACP)
● Automatic media-dependent interface crossover (MDIX)
● Should support feature to allow unidirectional links caused by incorrect fibre-optic wiring
or port faults to be detected and disabled on fibre-optic interfaces.
● Local Proxy Address Resolution Protocol (ARP)
● Internet Group Management Protocol (IGMP) Snooping for IPv4 and IPv6 MLD v1 and v2
Snooping to provide fast client joins and leaves of multicast streams and limit bandwidth-
intensive video traffic to only the requestors.
● Multicast VLAN Registration (MVR)
● Per-port broadcast, multicast, and unicast storm control

● Remote Switch Port Analyser (RSPAN)
● Layer 2 trace route
● Network Timing Protocol (NTP)
Security
Features
● Port Security
● DHCP Snooping
● Dynamic ARP Inspection (DAI)
● IP source guard
● 802.1X Supplicant
● Private VLANs
● Unicast Reverse Path Forwarding (RPF)
● Security VLAN ACLs
● Port-based ACLs
● Secure Shell (SSH) Protocol, Kerberos, and Simple Network Management Protocol Version
3

● TACACS+ and RADIUS authentication
● MAC Address Notification
● Bridge protocol data unit (BPDU) Guard
● Spanning Tree Root Guard (STRG)
● Dynamic VLAN assignment
IP Routing
Features
● IP unicast routing protocols (Static, Routing Information Protocol Version 1 [RIPv1], and
RIPv2, RIPng)
● Equal-cost routing facilitates Layer 3 load balancing and redundancy
● VRRP or HSRP
Management
CLI
SNMP
Web GUI

11.8.43 TECHNICAL SPECIFICATIONS INTERNET ROUTER
Sl Parameter Specifications
A. Architecture
1 Should be chassis based & modular architecture for scalability and should be a single box
configuration for ease of management.
2 Should support at least 6 interface slots to accommodate the current requirement as well as
for the future expansion
3 Should have support for hardware based IPSEC VPN.
4 Should have minimum of 256MB of RAM and 128 MB of Flash Memory
B. Interface
Requirements
1 3 x 10/100/1000 Base T interface.
2 2 x 2 Mbps V.35 interfaces
C. Performance
1 Should support high performance traffic forwarding with concurrent features like Security,
Voice enabled
2 Should support variety of interfaces like V.35 Sync Serial (2 Mbps), E1, Channelised-E1,
ISDN-BRI/PRI, FXO/FXS for remote office aggregation
3 Should hardware based encryption / compression with IPSEC throughput of 150 Mbps and

minimum 1000 VPN tunnels.
4 Should have at least 800 Kpps forwarding performance
5 Support for high density Ethernet switch cards (8 ports / 16 ports) for remote offices to
avoid additional switches.
D. High
Availability
1 Should support redundant connection to LAN
2 Should support Non-Stop forwarding for fast re-convergence of routing protocols
3 Should support boot options like booting from TFTP server, Network node
4 Should support multiple storage of multiple images and configurations
5 Should support link aggregation using LACP as per IEEE 802.3ad
6 Should support VRRP or equivalent
E. Protocols
1 Should support Routing protocols like RIP ver1 (RFC1058) &2 (RFC 1722 and 1723), OSPF
ver2 (RFC2328), BGP4 (RFC1771), IS-IS (RFC1195).
2 Multicast routing protocols support : IGMPv1,v2 (RFC 2236), PIM-SM (RFC2362) and PIM-

DM, M-BGP
3 Should have full IPv6 features from day 1.
4 Should have RIPng and OSPFv3 for IPv6.
5 Should have MPLS Features: MPLS VPN, MPLS TE, DiffServ-Aware TE
F. QoS Features:
1 Classification and Marking: Policy based routing, IP Precedence, DSCP
2 Congestion Management: WRED, Priority queuing, Class based queuing
3 Traffic Conditioning: Committed Access Rate/Rate limiting
4 Signalling: RSVP
5 Link efficiency mechanisms: cRTP, LFI, MLPPP
6 Per VLAN QoS. Time Based Shaping and Policing for QoS
G. Security
Features:
1 Support for GRE Tunnelling, NAT, L2TP/IPSECS tunnelling
2 Support for MD-5 route authentication for RIP, OSPF, IS-IS and BGP
3 Shall support multi-level of access

4 Support for SNMPv3 authentication, SSHv2
5 AAA support using Radius and/or TACACS
6 Support for PAP and CHAP authentication for P-to-P links
7 Multiple privilege level authentications for console and telnet access through Local database
or through an external AAA Server.
8 Time based & Dynamic ACLs for controlled forwarding based on time of day for offices
9 IEEE 802.1x support for MAC address authentication
H. Management
1 Shall have support for Web based management, CLI, Telnet and SNMPv3
2 Shall support Secure Shell for secure connectivity.
3 Shall support Out of band management through Console and external modem for remote
management
11.8.44 TECHNICAL SPECIFICATIONS CORE ROUTER AT NDR SITE
A. Architecture

1 The architecture should be based on high performance CPU with convergence of routing,
switching, voice and security.
2 The Router should be a single box configuration and should be modular, so that there is
flexibility to use the appropriate choice of interfaces as and when required.
3 Should have at least 2 slots. Each WAN card slot should support a variety of interfaces like
V.35 Sync Serial (2 Mbps), E1, Channelized E1 , ISDN BRI/PRI, E3, Channelized E3, STM-1 etc.
4 Should support Voice Interfaces like FXO, FXS
6 Should have either support for Voice Modules, and High Performance VPN Encryption
Modules
7 Forwarding capability should be at least 400 Kpps using 64-byte packet size with QOS
enabled.
9 The Router shall have at least 1GB DRAM and 256 MB Flash
10 Router should have at least 50 Mbps of encryption throughput and support for 500 tunnels
from Day-1.
12 Router should support on-line software reconfiguration to implement changes without

rebooting.
13 Router should have internal Redundant Power Supply for High availability.
B. Interface

Requirements
1 3 x Gigabit Ethernet Interface
2 4x V.35 interface with Cable
C. Software
1 The router shall support following WAN protocols: PPP as per RFC 1661, Multilink PPP,
ISDN, Frame Relay etc.
2 The Router shall support following IP routing protocols: RIP Version 1 & 2, Triggered RIP
support as per RFC 2091 to support demand circuit, OSPF Version 2 as per RFC 1583, BGP 4,
IS-IS. Multicast Routing support through PIM.
3 Support for NAT as per RFC 1631, Port Address Translation support.
4 IEEE 802.1Q based VLAN tagging
D. Security
1 Access lists based on Network Address, Mask, Protocol Type and Socket Type;
2 MD 5 Route Authentication as RFC 1321, Controlled SNMP Access through the use of SNMP
V.2 with MD5 Authentication.
3 Multiple Privilege levels to provide different level of access.
4 Remote Authentication Dial in user service (RADIUS) as per RFC 2138
5 VPN Support - To Support IP Security (IPsec), AES], 3DES, DES and MPLS

6 VPN Encryption - Equipped for Hardware Accelerated Encryption with 250 Mbps
performance.
8 Support for Web VPN (SSL VPN) on the router internal or external
10 Router shall support Network Management through: SNMP, RMON support, Software
Upgrade through FTP or TFTP; TELNET. The Router should also have integrated Web
Interface (GUI) for ease of configuration.
E. Protocols
1 The Router should be MPLS (Multiprotocol Label Switching) Ready with the following MPLS
Features:
2 MPLS Diff-Serv-Aware Traffic Engineering (DS-TE)
3 MPLS Label Distribution Protocol (LDP/RSVP)
4 MPLS QoS - DiffServ Tunnel Mode Support,
5 MPLS Traffic Engineering (TE) - Automatic bandwidth adjustment for TE tunnels
6 The Router should be IPv6 (IP version 6) Ready from day 1.
7 Secure Services Management - To Support SSHv2 and SNMPv3 protocols to encrypt the
management session.
F. High
Availability

1 Power Redundancy - Equipped with internal Redundant Power Supply.
2 USB Flash Memory - To Support USB Flash memory for ease of image recovery
3 Online insertion and removal - Should support online insertion and removal
G. Multimedia
and QoS
support
1 A class-based scheduling/queuing mechanism that provides configurable minimum

bandwidth allocation to each class
2 Should support Congestion Management mechanisms such as Priority Queuing, Custom

Queuing, Weighted Fair Queuing etc.
3 Should support Congestion Avoidance mechanisms such as RED / WRED
6 RSVP: Resource Reservation Protocol (RSVP) as per RFC 2205
7 Should support Policy-based Routing
8 IGMPv2, v3: Internet Group Management Protocol Version 2 & 3
9 Multicast routing support such as Protocol Independent Multicast (PIM) - Sparse Mode and
Dense Mode.
11 Integrated Web-based device-management tool embedded in the router; and should be

accessed remotely for faster and easier deployment of routers for both WAN access and
security features.

11.8.45 TECHNICAL SPECIFICATIONS SERVER FARM ACCESS SWITCH AT NDR
Architecture
● The Switch should have 24x10/100/1000Mbps Copper Ethernet ports with 2x10Gbps
SFP+ Based Fibre Uplinks
● Optional four Gigabit Ethernet (GbE) SFP or two 10GbE SFP+ uplink network modules
● Dual redundant, modular power supplies and fans
● Media Access Control Security (MACsec) hardware-based encryption
Performance
Switching Fabric should be 160 Gbps Capacity
The switch throughput should be 65Mpps
Memory: DRAM 256 MB, Flash 128MB
Total VLANs 1000
● Dynamic Host Configuration Protocol (DHCP) auto configuration of multiple switches

through a boot server
● Automatic QoS (AutoQoS) configuration

● Auto negotiation on all ports should automatically select half- or full-duplex transmission
mode
● Should facilitate dynamic trunk configuration across all switch ports.
● Link Aggregation Control Protocol (LACP)
● Automatic media-dependent interface crossover (MDIX)
● Should support feature to allow unidirectional links caused by incorrect fibre-optic wiring
or port faults to be detected and disabled on fibre-optic interfaces.
● Local Proxy Address Resolution Protocol (ARP)
● Internet Group Management Protocol (IGMP) Snooping for IPv4 and IPv6 MLD v1 and v2
Snooping to provide fast client joins and leaves of multicast streams and limit bandwidth-
intensive video traffic to only the requestors.
● Multicast VLAN Registration (MVR)
● Per-port broadcast, multicast, and unicast storm control
● Remote Switch Port Analyser (RSPAN)
● Layer 2 trace route
● Network Timing Protocol (NTP)
Security
Features

● Port Security
● DHCP Snooping
● Dynamic ARP Inspection (DAI)
● IP source guard
● 802.1X Supplicant
● Private VLANs
● Unicast Reverse Path Forwarding (RPF)
● Security VLAN ACLs
● Port-based ACLs
● Secure Shell (SSH) Protocol, Kerberos, and Simple Network Management Protocol Version
3
● TACACS+ and RADIUS authentication
● MAC Address Notification
● Bridge protocol data unit (BPDU) Guard
● Spanning Tree Root Guard (STRG)
● Dynamic VLAN assignment

IP Routing
Features
● IP unicast routing protocols (Static, Routing Information Protocol Version 1 [RIPv1], and
RIPv2, RIPng)
● Equal-cost routing facilitates Layer 3 load balancing and redundancy
● VRRP or HSRP
Management
CLI
SNMP
Web GUI
11.8.46 TECHNICAL SPECIFICATIONS IP Based KVM Switch
1 Supported It should have a minimum of 16 ports scalable and upgradeable

Ports
2 Maximum It should support 2 remote users and 1 user at the rack

User at a time

3 Functionalities It should support 2 remote users and 1 user at the rack
It should support 2 remote users and 1 user at the rack
It should be able to integrate with power strips, so as to be able to reset power of the
remote device at port level
Remote access of both servers and serial devices such as routers (through same or different
appliances)
It should have facility to integrate with secure management
Gigabit Ethernet ports
Virtual Media Support of multiple media including 'ISO image' files
19 inch rack mountable design
KVM access over IP
Browser based management available at both remote and local (supported browser =
Internet Explorer for MS Window, Firefox for MS Window and Linux)
Support for resolution of 1600*1200 or above
Single window access to all equipment
Logging should be centralized in one syslog server
Equipment access logs and event history and send email alerts based on log details as
triggers
Absolute mouse synchronization

11.8.47 Technical Specification for Management Console
Sl Specification
40” LCD Display with HD capable with wall mounting kit

Specifications :Panel : 40" Diagonal Size, Professional series panel, 1920 x 1080 (16:9 aspect ratio)
resolution, 450 cd/m2 brightness, 4000:1 contrast ratio, 178/178 viewing
angle (H/V) , 8ms response time (G-to-G) Connectivity : VGA, DVI-D, Composite, HDMI video input, RCA
(L/R), Stereo mini jack audio input, RCA (L/R) audio output, RS232c (in/out) external control Features :
Anti image retention, temperature sensor,
lamp error detection, built-in fan, built-in speakers (10W+10W), RS232 CMDC, Video wall feature, pivot
display, button lock Certification : UL, FCC, Energy star 5.0
11.8.48 Digitization Requirements
Sl No. Parameter Specification
1 Qualification Resource planned for deployment for digitization work should have essential
qualification of 10+2 in any discipline. Graduates will be preferred. They should have
typing speed of 20WPM minimum in Hindi.
One Functional Co-Ordinator to be deployed centrally should have essential

qualification of Graduate in Engineering with 2-3 Years’ experience in the functional

area. Graduate in Engineering with MBA is preferred.
2 Computer Resource should be well conversant with the working of the computers and should
Knowledge necessarily have knowledge of LAN function, MS Word, MS Excel and MS Power Point
packages /Open Office suite. For the project adequate training to be imparted prior to
deployment at site
3 Selection & The department may at its discretion interview the candidates and the following
Document documents verification of the of the digitization support manpower before SI putting
Verification them in work.
a) List of persons deployed:

b) Bio-Data and relevant certificates of the persons:
c) Valid photo identity proof.
4 Target The SI will have to do the Data migration and Digitization of Historical Data of last 10
years in estimated to be completed in 1900 unit months, unit consisting of M/C,
resource, checklist printout for error free entry and necessary supervision to ensure
compliance to requirement.

Base
Record Type
Year Records for Data Entry
(Cases)
FIR 2000 299,156
Charge sheet 2000 299,156
Seizure Memo 2000 299,156
Conviction 2000 194,452

Memo
Arrest Memo 2000 897,468
Final Report 2000 194,452
Wanted/ 2000
Missing-
Person/Propert
y 89,747
Total 2,273,587
5 Cost of
Digitization
It is required by SI to comply with all Statutory requirements i.e. Remuneration of

resources being engaged including Employers’ contribution of PF, ESIC and other
statutory payments etc. as applicable. The cost estimate must also include agency
(maximum 15%) charges, supervision cost, checklist printout cost, Machine
deployment cost, one centrally deployed functional co-ordinator / team leader etc.
Department recommended 1,924 man months and minimum remuneration
(inclusive of Employee’s PF etc.) of the resources are as under:
1. Rs. 7,000/- pm for Digitization Staff
2. Rs. 20,000/- pm for Functional Co-Ordinator
6 Monthly Report The SI need submit the monthly attendance report , performance report , unit months
Submission left status and uploading of data on to central project management system

Place of Police station or Circle Inspector office or department will provide a suitable place for
Digitization digitization work .
7 Others
A In case, the person employed by the SI commits any act omission/commission that
amounts to misconduct/indiscipline/incompetence, the SI will be liable to take
appropriate disciplinary action against such persons, including their removal from the
site of work required by the department.
B The SI shall replace immediately any of its personnel who is found unacceptable to
the department because of security risks, incompetence, conflict of interest, improper
conduct etc. upon receiving a notice from this department
C The SI shall immediately provide a substitute in the event of any person leaving the
job due to his/her personal reasons.
D The SI shall be solely responsible for the redressal of grievances/resolution of
disputes relating to person deployed. The Department shall, in no way be responsible
for settlement of such issues whatsoever.
11.8.49 Handholding and Technical support (including Helpdesk) Requirements
Handholding and Technical support ( including Helpdesk) Requirements
Helpdesk Management System
Bidder should provide a centralized Enterprise Management solution for all the IT assets spread across various offices
throughout the State. The offered solution should be from a single vendor/product family so as to ensure the integration and
high level of data exchange between various layers and based on an Internationally recognized industry standard Enterprise

Management Software (EMS) and shall be required to have full capabilities to provide unified Fault, Performance and
Service level management and reporting. The proposed solution is expected to have following functionality:
• The Solution has modular architecture.
• Based on applications that are then proposed to be deployed, it would be possible to add modules on to base
module providing the desired Management functionality.
• The Solution is expected to be based on SNMP and TCP/IP standards permitting Network layer level Management
of alarm and event s on the same platform.
• The Solution is scalable customizable module wise to suit the growing or changing needs.
• The Solution is capable of managing Network Resources deployed over a heterogeneous mix of media.
• The Solution will be able to share the same database and the data between the different functional modules of the
system i.e. would have a common object repository for all modules.
• It would be possible to use the Policies and Tasks defined at the Base for all the functional modules running on top
of the base. MS features an object-oriented architecture that is open, distributed, highly scalable, and multi-
platform.
• Solution is able to delegate authority: It would be possible to provide the means to define multiple administrators,
each with their own level of authority suitable to their responsibility and experience level. Using role based
administration; it would be possible to control administrator access to appropriate function and /or other
resources. The solution can be divided into Policy Region s (a logical collection of resources) based on organization
or geography.
• HELPDESK MANAGEMENT
• It should provide web-based support interface to end-users and helpdesk staff to open service requests, track
problems, search for solutions.
• It should support automatic problem registration with respect to EMS event management, based on predefined
policies.
• It should be able to log and escalate user interactions and requests.

• It should provide status of registered calls to end -users over email and through web.
• It should have an updateable knowledge base for technical analysis and further help end-users to search solutions
for previously solved issues.
• It should have the ability to track work history of calls to facilitate troubleshooting.
• It should support tracking of SLA (service level agreements) for call requests within the helpdesk through service
types.
• It should support request management and change order management.
• 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 be able to provide basic reports.
• The service desk should be from the same product family/suite/OEM as the EMS and should be compliant with ITIL
standards.
• It should be able to facilitate establishment of relationships between Calls logged like parent / child.
• It should provide provision for customer surveys to assess their service experience.
• It should allow incidents to attach multiple documents.
• It should provide for automatic population of assets like server, routers, switches etc. in its database using
integration with Asset management or Network management software where these assets are already discovered/
available.
• Provisioning of Help Desk facility by providing help line/ Call centre facility in 2 shifts.
Resource Deployment requirements
1 Qualification
Resources to be provided must be DC/ PGDCA qualified and should undergo 2 weeks

training on computer hardware and networking before reporting at Police Stations /

higher offices.
The Functional Co-Ordinator to be deployed centrally should have essential qualification of
Graduate in Engineering with 3-4 Years’ experience in the functional area. Additionally,
MBA qualification is preferred.
2 Skill The SI will ensure the candidate is well conversant with the WindowsXP / Linux and
/Knowledge should necessarily have knowledge of LAN /WAN, Linux, Windows XP/7 MS Word, MS
Excel and MS Power Point packages /Open Office suite and having good exposure to Linux
and Open Office.
3 Verification The antecedents of the candidates should have got verified by the SI from the local police
authorities.
Document documents verification of the of the digitization support manpower before SI putting them
Verification in work.

b) Bio-Data with relevant certificates of the persons:
c) Valid photo-id proof.
5 Responsibility Handholding and technical assistance/guidance/training at police locations. Provisioning
of Help Desk facility by providing help line/ Call centre facility in 2 shifts. Please refer
section 11.8.48 for detailed requirements and for EMS Specification requirements specified
under Non-functional Requirements, Chapter 9.2.
6 Man months SI is responsible for properly using the handholding Technical assistants to support the
project for required period post Go-Live .The SI will have to carefully utilize 4,860 Man
months for hand holding, help desk support.
7 Payment It is required by SI to comply with all Statutory requirements i.e. Remuneration of
resources being engaged including Employers’ contribution of PF, ESIC and other statutory

Terms payments etc. as applicable. The cost estimate must also include agency (maximum
15%) charges, supervision cost, one centrally deployed functional co-ordinator /
team leader etc.
Department recommended minimum remuneration (inclusive of employee’s PF etc.)
of the resources are as under:
1. Rs. 10,000/- pm for Handholding resource
8 Monthly The SI will submit the monthly attendance report, performance report, Salary paid report
report and other reports if asked for time to time to the department.
submission
9 Others
amounts to misconduct/indiscipline/incompetence, the SI will be liable to take appropriate
disciplinary action against such persons, including their removal from the site of work
required by the department.
B The SI shall replace immediately any of its personnel who is found unacceptable to the
department because of security risks, incompetence, conflict of interest, improper conduct
etc. upon receiving a notice from this department
C The SI shall immediately provide a substitute in the event of any person leaving the job due
to his/her personal reasons.
D The SI shall be solely responsible for the redressal of grievances/resolution of disputes
relating to person deployed. The Department shall, in no way be responsible for settlement
of such issues whatsoever.

11.8.50 Capacity Building Requirements
1 Qualification
The SI will deploy the capacity building support manpower having essential
resources to qualification of BCA /BSC(IT)/ Graduate with PGDCA and two years experience in
be deployed training/support or MCA /BE with one year experience in training / support from
recognized University.
The Functional Co-Ordinator to be deployed centrally should have essential qualification
of MBA in HR with 3-4 Years’ experience in the functional area.
2 Skill / The SI will ensure the candidate is well conversant with the WindowsXP / Linux and
Knowledge should necessarily have knowledge of LAN /WAN, Linux, Windows XP/7, MS Word, MS
Excel and MS Power Point packages /Open Office suite and having good exposure to Linux
and Open Office.
Document documents verification of the of the digitization support manpower before SI putting them
Verification in work.

b) Bio-Data and relevant certificates of the persons:
4 Responsibilit Si will ensure training to the police personnel as specified in capacity building
y requirements chapter in RFP Vol-I.
5 Man months SI is responsible for properly using capacity building support manpower to carry out the
training programme .The SI will have to carefully utilize approximately 2196 man
months, including re-training ( at the rate of 20 trainees per batch and 24 working days in
a month)
6 Overall cost / It is required by SI to comply with all Statutory requirements i.e. Remuneration of
Payment resources being engaged including Employer’s contribution of PF, ESIC and other

Terms charges required for design, execution and management of Change Management &
Capacity Building plan, one centrally deployed functional co-ordinator / team
leader etc.
Department recommended 2,196 man months and minimum remuneration
1. Rs. 12,000/- pm for Training Staff
Report with the number. Of persons trained and other reports as asked for; from time to time to
Submission the department.
8 Others
appropriate disciplinary action against such persons, including their removal from the site
of work required by the department.
C The SI shall immediately provide a substitute in the event of any person leaving the job
due to his/her personal reasons.
relating to person deployed. The Department shall, in no way be responsible for
settlement of such issues whatsoever.
E The overall scope shall also include meeting all requirements on Change Management and
Capacity building activity specified under Chapter 10 of RFP Vol-I

11.8.51 Data Centre Operational Manpower/Requirements
1 Qualification/ The SI will deploy the data centre support manpower having following essential
Experience qualification and experience.
• Network Administrator: B.E / MCA or equivalent with CCNA / CCNP certification
with 3 years of experience or BCA / Graduate with CCNP certification and
experience of 5 years in managing 50 leased line connections.
• Database Administrator: B.E / MCA or equivalent with 3 years of experience or
BCA with 5 years of experience in managing Oracle / MySQL / Postgres database at
data centre with OCA/OCP/MySQL DBA certificate.
• System cum Security Manager: B.E /MCA or equivalent with 3 years of
experience or BCA with 5 years of experience in managing systems of Linux /
Solaris at data centre. RHCE certification is preferable.
2 Skill SI will deploy certified Network, Database & System admin Datacentre management
/Knowledge expertise persons to manage the CCTNS data centre.
3 Selection & The department may at its discretion interview and the following documents verification
Document of the of the digitization support manpower before SI putting them in work.
Verification
b) Bio-Data of the persons:
4 Responsibilit Si will ensure the proper data centre operational management by using these staffs.
y
5 Man months 3 resources, 2 shifts, 5 years from establishment of data centre infrastructure
6 Payment It is required by SI to comply with all Statutory requirements i.e. Remuneration of

Terms resources being engaged including Employers’ contribution of PF, ESIC and other
(maximum 15%) charges, supervision cost, etc.

Department recommended 360 man months and minimum remuneration

1. Rs. 35,000/- pm for Database Administrator/ System Administrator/ Network
Administrator.
Report and other reports is asked for; from time to time to the department.
Submission
9 Others
11.8.52 Project Planning and Management Requirements
Sr. Parameter Specification

No.

1 Qualification / The SI will deploy the manpower having following essential qualification and experience.
Experience .
Team Leader: Essential Requirements: Graduation in Engineering with a
degree/diploma in Business Administration with a minimum of 5-7 years project
management experience .Project management experience should preferably be for long
term projects in the Government sector.PMI certification is required.
2 Skill Project Management and respective functional area management skills, preferably in
/Knowledge police domain
Tools Required Project Management Information System (PMIS). Detailed requirements for the same have
been elucidated in Section 4.3.1 of this RFP Vol-I.
3 Selection & The department may at its discretion interview and the following documents verification
Document of the of the support manpower before SI putting them in work.
Verification
b) Bio-Data of the persons:
4 Responsibility Si will ensure the proper project management by using these staffs.
5 Man months Team Leader for entire project duration, functional areas as per requirement
6 Payment Terms It is required by SI to comply with all Statutory requirements i.e. Remuneration of
resources being engaged including Employers’ contribution of PF, ESIC and other
(Maximum 15%) charges, supervision cost, etc.
Department recommended 66 man months and minimum remuneration (inclusive
of Employee’s PF etc.) of the resources are as under:
1. Rs. 40,000/- pm for Team Leader

7 Monthly Report The SI will submit the monthly attendance report, performance report, Salary paid report
Submission and other reports as asked for from time to time by the department.
8 Others
11.8.53 Certification Requirements
Details
• Ensure acceptance testing, audit and certification through 3rd party Agency like STQC/CERT-IN as specified
in Section 4.3.13.
• SI is required to obtain ‘ISO27001’ and ‘ISO20000’ certifications for the CCTNS system by the end of first six
months of O & M phase.
• SI shall include all the efforts and cost required to obtain the above certifications in the commercial
proposal submitted by them in response to this RFP.

11.8.54 Technical Specification—5 KVA Stabilizer
1 Input voltage 90-280 Volt
2 Output voltage 220 volt. 10%
3 Frequency 50 Hz
4 Insulation Greater than 6 M Ohms
5 Mode Of Automatic
Operation
6 Response Time 30 seconds
7 Duty Cycle Automatic
8 Type Of Cooling Air Cooled
9 Efficiency Better than 98%
10 Operating 0 degree C to 55 deg. C Unbalance supply and load, suitable for single phase
temperature unbalanced/balanced load & for all power factor
11 Transformer All copper wound on CRGO laminations, as per ISO specification for high efficiency
and low loss

12 Salient Input/output voltage shown by voltmeter on front panel

Features
11.8.55 Technical Specification—42U Rack
1 Feature 42U 800W X 800D Modular Structures made from aluminium extruded profile, minimum
extrusion wall thickness at all sides and corner- 2mm. along with following items: Top and
Base Cover with cable enter Black Colour
2 Front/Rear Door Front, Glass door, 800mm Wide, 42U, with Lock and hexagonal vent on 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
3 Mounting Angles 19” Mounting Angles, 19” mounting angles powder coated along with “U” marking
4 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
5 Castors Castors - For providing mobility to the rack. Two with foot operated brakes and Two without
brakes, having a load carrying capacity of 100kg
6 Fan 230V AC 90CFM Fan (4 nos. for each Rack) with Fan Housing Unit
7 Cable Manager 19”, 1U, Horizontal Cable Manager, to allow proper cable routing

8 Cable Loops 24U to help route the cable vertically
9 Power Supply 10X 5 amps or 6 X 5 amps socket as per requirement
10 Castors Castors as needed
11 Cable Storage 2U cable storage shelf supported with 4 bobbins
11.8.56 A Technical Specification—Intrusion Prevention System
Sl Specification
1 The IPS should have performance of at least 1 Gbps
2 IPS should have redundant power supply.
3 4*10/100/1000 interfaces.
4 It should provide protocol decoding and validation for network traffic
5 It should be able to monitor all major TCP/IP protocols, including but not limited to IP, Internet Control
Message Protocol (ICMP), TCP, and User Datagram Protocol (UDP).
6 It should also provide stateful decoding of application-layer protocols such as FTP, Simple Mail Transfer
Protocol (SMTP), HTTP, SMB, Domain Name System (DNS), remote procedure call (RPC), NetBIOS,
Network News Transfer Protocol (NNTP), generic routing encapsulation (GRE), and Telnet.

Sl Specification
7 It should also provide anomaly identification for attacks that may cover multiple sessions and
connections, using techniques based on identifying changes in normal network traffic patterns (i.e. ICMP
flood with a predefined number of ICMP packets within a certain amount of time).
It should also identify attacks based on observed deviations in the normal RFC behaviour of a protocol or
service (i.e. HTTP response without an HTTP request).
It should also Identify Layer 2 Address Resolution Protocol (ARP) attacks and man-in-the-middle attacks,
which are prevalent in switched environments.
It should also provide deep analysis and control of a broad set of applications, including:
• Peer-to-peer
• Instant messaging
• Tunnelled applications over Port 80
• Allows the user to make policy decisions about various traffic types and Multipurpose Internet Mail
Extensions types to help ensure that malicious traffic is disallowed from traversing the network.
It should also have a support for Anti-IPS Evasion Techniques
• Traffic normalization
• IP defragmentation
• TCP stream reassembly
• De-obfuscation

Sl Specification
It should provide unparalleled contextual analysis of data to determine its threat and eliminate false
positives.
It should have support for some threat rating feature which can provide a single view of the threat
environment of the network. Threat Rating can minimize alarms and events through the ability to
customize the viewer to only show events with a high Threat Rating value.
It should support IPv6. It should have visibility into IPv6 traffic to identify malicious traffic.
It should support virtual sensors (at least 3) within the appliance. A virtual sensor can monitor multiple
segments and different policies or configurations can be applied for each virtual sensor within a single
physical sensor. Different policies can also be defined per monitored segment under analysis.
11.8.57 Technical Specification—Firewall
1 HARDWARE FEATURES
The Firewalls should be Hardware based, Reliable, purpose-built security appliance with
hardened operating system that eliminates the security risks associated with general-purpose
operating systems with 8 Nos. of 10/100/1000 Base TX interfaces, 4 Nos of SFP in terfaces and
1 Fast Ethernet interface.
The Appliance should be Full-featured, high-performance firewall, and IP Security/Secure

Sockets Layer (IPsec/SSL) VPN technologies deliver robust application security, user- and
application-based access control, and remote user/site connectivity.

Should be redundant supporting Active/Active or Active/Standby Firewall for High Availability

& Scalability
Firewall Throughput of Up to 1.2 Gbps
VPN Throughput of Up to 425 Mbps
Concurrent Sessions of at least 650,000
IPsec VPN Peers of up to 5000
WebVPN Peers of up to 2500
Support for Virtual Firewalls of up to 50 logical firewalls so that the Central site can have an
individual firewalling for every remote site in future.
Virtual Interfaces (VLANs) support for at least 250 VLANs for forming Secure server Farms and
DMZs
Scalability through VPN clustering and load balancing
2 Software Features
Application Security Services
The Firewall should have Integrated specialized inspection engines for protocols like HTTP,
FTP, ESMTP, DNS, SNMP, ICMP, SQL*Net, NFS, H.323 Versions 1-4, SIP, MGCP, RTSP, TAPI and
JTAPI over CTIQBE protocol, GTP, LDAP, ILS, RPC and many more
The Firewall should provide advanced inspection services to detect and optionally block
instant messaging, peer-to-peer file sharing, and other applications tunnelling through Web

application ports
It should block popular instant messaging applications such as AOL Instant Messenger,
Microsoft Messenger, and Yahoo Messenger
Should stop peer-to-peer file sharing applications such as KaZaA and Gnutella. Should thwart
tunnelling applications such as GoToMyPC
Support for SNMP version filtering for all SNMP traffic attempting to flow through security
appliance, supporting filtering of SNMP versions 1, 2, 2c, and 3
For Sun RPC and Network Information Service Plus (NIS+) Security Services
Support for port-hopping UNIX applications through stateful inspection and NAT services for
Sun RPC and NIS+ sessions transactions that use Portmapper v2 or RPCBind v3 or v4
Advanced H.323 inspection services that support versions 1-4 of the protocol along with Direct
Call Signalling (DCS) and Gatekeeper Router Control Signalling (GKRCS) to provide flexible
security integration in a variety of H.323-driven voice-over-IP (VoIP) environments
NAT and PAT support for H.323 services, including advanced features such as fax over IP
(FoIP) using the T.38 protocol, an ITU standard that defines how to transmit FoIP in real time
Fortified SIP inspection engine that secures both, UDP and TCP based SIP environments
NAT- and PAT-based address translation support for SIP-based IP phones and applications
such as Microsoft Windows Messenger, while delivering advanced services such as call
forwarding, call transfers, and more
Secure integration of IP telephony services while successfully connecting calls over

multiprotocol VoIP environments across NAT and PAT boundaries

Rich MGCP security services and NAT- and PAT-based address translation services for MGCP-
based connections between media gateways and call agents or media gateway controllers
NAT-based address translation services for RTSP media streams for improved support in real-
time networking environments
Support for inspection of various TAPI- and JTAPI-based applications that use CTIQBE
Inspection of H.323, SIP based voice and multimedia streams that have been fragmented or
segmented
Support for foundational capabilities to assist in detecting protocol and application layer
attacks
To provide TCP stream reassembly and analysis services to help detect attacks that are spread
across a series of packets
Should offer TCP traffic normalization services for additional techniques to detect attacks,
including advanced flag and option checking, TCP packet checksum verification, detection of
data tampering in retransmitted packets, and more
3 Network Containment and Control Services
Robust stateful inspection firewall services that track the state of all network communications
Inbound and outbound access control lists (ACLs) for interfaces, time-based ACLs, and per-
user or -group policies for improved control over network and application usage
Greater control over resource usage by defining time-based ACLs, when certain ACL entries are
active, with custom time ranges applied to selected ACLs

Convenient troubleshooting tool that allows administrators to test and fine-tune ACLs without
the need to remove and replace ACL entries
Creation of security policies based on interface name instead of IP address, a feature that is
especially useful in broadband environments where the external interface is typically assigned
a dynamic IP address
Powerful reporting and troubleshooting capabilities that help enable collection of detailed
statistics on which ACL entries are triggered by network traffic attempting to traverse a
security appliance
Dynamic downloading and enforcement of ACLs on a per-user basis, upon user authentication
with the firewall
Grouping of network objects (such as devices, networks, and services) into logical groups to
greatly simplify access control rule definition and maintenance
Rich dynamic, static, and policy-based NAT and PAT services
4 Secure Connectivity Services
IPsec remote-access VPN concentrator services for up to hundreds of simultaneous remote

software- or hardware-based VPN clients
Should be able to Push VPN policy dynamically to Easy VPN Remote-enabled solutions upon
connection, eliminating the need to manage each client separately and therefore helping
ensure enforcement of the latest corporate VPN security policies
Perform VPN client security posture checks when a VPN connection attempt is received,
including enforcing usage of authorized host-based security products

Support for automatic software updates to VPN clients with the ability to trigger updates when
VPN connections are established, or on demand for currently connected VPN clients
Extend VPN reach into environments using NAT or PAT, through support for the IETF UDP
wrapper mechanism for safe traversal through NAT and PAT boundaries as well as TCP and
UDP NAT traversal methods
Support for Lempel-Ziv Standard (LZS) compression for optimizing performance over low-
bandwidth connections
Should include unlimited user support for the VPN Client. Should be available on wide range of
platforms, including Microsoft Windows 98, ME, NT, 2000, and XP; Sun Solaris; Intel-based
Linux distributions; and Apple Macintosh OS X
Should provide many innovative features, including dynamic security policy downloading from
VPN Server, automatic failover to back up VPN Servers, administrator customizable
distributions, and more
Should support SSL VPN-based remote-access connectivity from almost any Internet-enabled
location, using only a Web browser and its native SSL encryption
Supporting hundreds of simultaneous SSL VPN connections
Provide CIFS (Microsoft Windows) file share access through an easy-to-use Web interface
Enforce granular, group-based access control, limiting users to specific network resources
Provide access to TCP-based applications, such as Telnet and Windows Terminal Services, with
the SSL-VPN Port Forwarding Java applet (on systems running Sun Java Runtime Environment
[JRE] 1.4 or later)

Support for improved IPsec and WebVPN remote-access scalability and reliability through
integrated VPN clustering and load-balancing services
Should provide convenient method for authenticating VPN users through native integration
with popular authentication services, including Microsoft Active Directory, Microsoft Windows
Domains, Kerberos, LDAP, and RSA SecurID (without requiring a separate RADIUS server to act
as an intermediary)
Support for Internet Key Exchange (IKE) and IPsec VPN standards with hub-and-spoke or
meshed VPN configurations
improved network reliability and performance through support of OSPF dynamic routing and
reverse-route injection over site-to-site VPN tunnels
Support for Simple Certificate Enrolment Protocol (SCEP)-based enrolment and manual
enrolment with leading X.509 solutions from Baltimore, Entrust, iPlanet/Netscape, Microsoft,
RSA, and VeriSign
Interoperability with large-scale PKI deployments through n-tiered certificate hierarchy

support
Ability to manually enrol into X.509 certificate authorities through support for Public Key
Cryptography Standard (PKCS) #10 formatted certificate requests
Support for manual importing of certificates using PKCS #7, and importing certificates with
private keys using PKCS #12
Support for a variety of RSA (Rivest, Shamir, Adelman) key sizes ranging up to 4096 bits
Support for DSA (Digital Signature Algorithm)-based X.509 certificates with key sizes ranging

up to 1024 bits
5 High-Availability Services
Support for Active/Active & Active/Standby failover.
Support for bidirectional state sharing between Active/Active failover pair members for
support of advanced network environments with asymmetric routing topologies, allowing
flows to enter through one Firewall appliance and exit through the other, if required
Maximizing VPN connection uptime with Active/Standby stateful failover for VPN connections
Support for Synchronizing all security association state information and session key material
between failover pair members, providing a highly resilient VPN solution
Enable geographic separation of Security appliances in a failover pair by allowing failover

information to be shared over a dedicated LAN connection between failover pair members
Support to perform software maintenance release upgrades on the Firewall appliance failover
pairs without affecting network uptime or connections
11.8.58 Technical Specification—Load Balancer
1 Architecture

Should be a multi-processor based appliance
Should have min 4 x 10/100/1000 Base T
Should have minimum 4 Gb RAM & Upgradeable to 8 Gb
Should support minimum 1 Million L4 concurrent connections
Should support minimum 100,000 L4 connections per second
Should support minimum 32,000 L7 connections per second
Should support minimum 1 Gbps L7 throughput form day one & should be upgradeable in future
to support 4 Gbps via software license without any change in Hardware or adding any memory
Should support SSL offloading & HTTP acceleration from day one in same unit without adding
another hardware to save rack space, power & cooling requirements
Should support SSL bps Max 1 Gbps
Should support 1000 SSL TPS from day one and upgradable to minimum 6000 SSL TPS through
license upgrade
Should support 100,000 SSL concurrent connections
Should support 4000 logical interfaces
Should have Flash Drive support
Should support Port Mirroring

Should support following deployments
Routing Mode : where client-side and server-side VLANs are on different subnets
Bridge Mode: where client-side and server-side VLANs are on the same subnets.
Direct Server Response: where SLB load balance an initial request from the client to a real server;
however, the server directly responds to the client bypassing the SLB.
2 Load Balancing Features
Should support minimum 100 Servers & Maximum 4000 Servers for load balancing
Should support minimum 100 Virtual Servers & Maximum 750 Virtual servers
Should support following load balancing algorithms
Cyclic - Round Robin
Weighted Cyclic
Least Connections
Least Bandwidth
Least Response time
Server load balancing based on SNMP parameter like CPU load, Memory utilization etc.
Should support Client NAT & Server NAT

In case of Server / Application failure device should detect it in not more than 30 seconds
In case of Server failure traffic should be diverted to another Server automatically
Should support following content based Load balancing features
HTTP Header based redirection
URL-Based Redirection
Browser Type Based Redirection
Preferential Treatment (Cookie-Based)
Should support End-to-End SSL Encryption (Backend Encryption)
Should support SSL initiation ( SSL between SLB & Servers)
4 Server Management Features
Should support Graceful shutdown of Servers
Should support Graceful Activation of Servers
Should able to redirect traffic based on Source IP, Destination IP & TCP PORT
5 Segmentation/Virtualization
The Load Balancer should support virtualization or segmentation where it should be possible to
create virtual partitions from day one. Each of this Partition should be completely isolated from

each other w.r.t. dedicated access control and resource allocation
Should support Min & Max resource allocation per virtual Partition
Should support resource sharing between virtual Partitions so in case if resource is available
with another virtual partition it can be borrowed automatically
Should keep configuration files separately for each virtual partition or segment
6 Health Monitoring
Should provide individual health checks for real servers & farms
Should allow to monitor protocol like HTTP, SMTP, POP, FTP etc.
Should allow to configure Customize health probes based on TCP & UDP parameters
Should provide GUI to configure Health Monitoring
Should provide flexible Script based support for complex environments & advance health
monitoring
7 Redundancy
Should support Redundancy for High Availability
Should support transparent failover between 2 devices
Should support transparent failover between 2 Virtual Instances configured on 2 different units
Should Supports active-standby and active-active redundancy topologies with automatic

configuration synchronization
The failover should be transparent to other networking devices
8 Security
Should support minimum 1000 Access list
Should support HTTP deep packet inspection (HTTP header, URL, and payload)
Should support bidirectional Network Address Translation (NAT) and Port Address Translation
(PAT)
Should support TCP Normalization & TCP connection state tracking
Should support ICMP flood guard
Should support Virtual connection state for UDP
Should support Sequence number randomization
Should support TCP header validation
Should support TCP window size checking
Should able to detect & drop same Source port & destination port traffic
Should able to detect & drop L4 port 0 traffic
9 Application Acceleration

Should Support SSL Offloading & Acceleration on same hardware to reduce number of equipment
in Data centre & save power / cooling requirement
Should support 1500 SSL certificates
Should support HTTP Compression technologies like GZIP & DEFLATE using dedicated hardware
chips
Should support 500Mbps hardware based compression from day one & upgradeable in future to
2 Gbps via software / license upgrade
Should use dedicated Hardware Card / Module for compression & not software based
compression
Should support dynamic caching technologies
Should store cached content in RAM for faster content delivery
Should provide 1 GB dedicated storage capacity in RAM
Should support image optimization
Should support transparent TCP Multiplexing (TCP Offloading)
9 Management
Should support following Management Applications , Telnet/ SSH/ HTTPS/ Console/ SNMP
Should support GUI for configuration & monitoring

Should support access control per virtual unit so each virtual unit can be managed by different
group without able to see config in other virtual unit
10 Quality of Service
Should have the capability to set the type of service (ToS)
Should have the capability to set the Differentiated Services Code Point (DSCP)
Should support QoS per client request on a Layer 4 or 7 match
11.8.59 Technical Specification—Antivirus Software
License The antivirus software to protect 600 desktops windows /Linux and 10 servers
1 Features
Shall have automated virus cleaning and repairing capabilities.
Shall provide for Web-based centralized management.
Shall provide Domain based central management – and is able to organize and manage
computers in logical domains.

Shall provide TCP/IP and HTTP support with latest Web technologies – ActiveX, ASP, PHP, CGI,
HTML.
Shall be able to scan through minimum of 20 types of compression formats.
Shall support pattern file roll-back – shall be able to return to past pattern file if there is any
problem with the new pattern file.
Shall be able to remotely deploy the Client software using the following mechanisms: Web- based
installation
Provide for central management console to centrally control desktop configurations, including
scanning and cleaning options
Shall monitor all desktops for virus activity in real time and maintain a log to provide a complete
picture and activity of virus protection in a corporate environment.
Shall provide one-stop Web-based console to ease the client software deployment, update and
upgrade in real time
Shall allow domain based management for simultaneous client configuration to implement and
enforce desktop antivirus policy.
Real-time lock down of client configuration – allow or prevent users from changing setting or
unloading / uninstalling the software.
Shall be able to remotely un-install the software.
Shall provide continuous Virus protection and able to perform updates regardless of whether the
client is connected to the management server or not.

Shall be able to support automated attack-specific policy recommendations before a new pattern
file is available.
Shall be able to support remote deployment and execution of damage clean-up tools (Damage
Clean-up Services)
Shall support multiple Windows platform - Windows XP/vista/Windows 7/Windows

2003/Windows 2008 server
Shall provide protection for server based Linux Redhat platform
Includes POP3 scanning by providing real-time scan for Outlook Express, Eudora, and Netscape
mail
Shall not require reboot of the client after deployment
Shall not require reboot after update or upgrade.
Able to perform different scan Actions based on the virus type (Trojan/ Worm, Joke, Hoax, Virus,
other)
Shall be able to scan only those file types which are potential virus carriers (based on true file
type)
Shall include Vulnerability Assessment tool to identify AV clients on a network
Shall support Quarantine Manager

11.9 Annexure 9 - 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:
• Warranty support
• Annual Technical Support (ATS)
• Handholding Services
o Operations and maintenance services for the server and related infrastructure supplied and commissioned by the SI for the
application at the Data Centre and Disaster Recovery Centre.
o Central Helpdesk from the State designated premises.
o Software maintenance and support services.
o Application functional support services
The services shall be rendered onsite from the State designated premises. To provide the support for the police stations, sub-divisional offices,
district headquarters, 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 shall develop a work plan for the
knowledge sharing as per scope defined in this RFP for use in future phases of the project.
As part of the warranty services SI shall provide:
• SI shall provide a comprehensive warranty and on-site free service warranty for 5 years from the date of completion of Phase-III.
• SI shall obtain the five year product warranty and five year onsite free service warranty on all licensed software, computer hardware and
peripherals, networking equipment and other equipment.

• 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.
• 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.
• 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.
• 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 equipment for
inspection, delivery of equipment or for commissioning of the systems or for acceptance tests / checks on per site basis, State reserves the
right to charge a penalty.
• 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.
• The SI shall as far as possible repair the equipment at site.
• 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.
• 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.
• The SI shall carry out Preventive Maintenance (PM), 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.

• SI shall monitor warranties to check adherence to preventive and repair maintenance terms and conditions.
• The SI shall ensure that the warranty complies with the agreed Technical Standards, Security Requirements, Operating Procedures, and
Recovery Procedures.
• 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.
• 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).
• The SI shall develop and maintain an inventory database to include the registered hardware warranties.
As part of the ATS services SI shall provide:
• SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes, replacements and maintenance.
• 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.
• SI should carry out any requisite adjustments / changes in the configuration for implementing different versions of Application Software.
• 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.
• SI shall provide patches to the licensed software including the software, operating system, databases and other applications.
• 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 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.
• 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 08:30 hours to 20:30 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 accesses to a variety of technical resources including the manufacturer’s knowledge base with complete collections
of technical articles.
As 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 Centre and Disaster Recovery Centre SI shall provide:
• 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
Centre and Disaster Recovery Centre.
The business hours in State will be from 08:30 hours to 20:30 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 Centre and Disaster Recovery Centre 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:
• System Administration, Maintenance & Management Services
• Application Monitoring Services
• Network Management Services
• Backend Services (Mail, messaging, etc.)
• Storage Administration and Management Services

• IT Security Administration Services and Services for ISO 27001 and ISO 20000 compliance
• Backup and Restore Services
As part of the Handholding services to provide Centralized Helpdesk and Support for end users at each location SI shall provide:
• The service will be provided in the local language of the State.
• 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 Centre,
Disaster Recovery Centre, 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.
• SI shall provide a second level of support for application and technical support at police stations, circle offices, sub-divisional offices, district
headquarters, range offices, Zonal offices, state police headquarters and other locations across the State where the software, hardware, and
other infrastructure will be rolled out.
• For all the services of State within the scope of this RFP, SI shall provide the following integrated customer support and help.
• Establish 16X6 Help Desk facilities for reporting issues/ problems with the software, hardware and other infrastructure.
• SI shall maintain and support to all client side infrastructure including hardware, networking components, and other peripherals.
• 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.
• SI shall track and report observed Mean Time between Failures (MTBF) for Hardware.
• SI shall provide functional support on the application components to the end users.

• SI shall also provide system administration, maintenance and management services, LAN management services, and IT security
administration services.
As part of the Handholding services to provide software maintenance and support services SI shall provide:
• 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 offsite maintenance and support services to State to all the designated locations. The Maintenance and Support Services will
cover, all product upgrades, modifications, and enhancements.
• 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.
• Tuning of application, databases, third party software’s and any other components provided as part of the solution to optimize the
performance.
• The SI shall apply regular patches to the licensed software including the operating system and databases as released by the OEMs.
• Software Distribution. SI shall formulate a distribution plan prior to rollout and distribute/install the configured and tested software as per
the plan.
• 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.
• 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:
• 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 Centre in State.

• 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.
• Routine functional changes that include user and access management, creating new report formats, and configuration of reports.
• 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.
• 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.
• The SI shall perform user ID and group management services.
• The SI shall maintain access controls to protect and limit access to the authorized end users of the State.
• The services shall include administrative support for user registration, creating and maintaining user profiles, granting user access and
authorization, providing on-going user password support, announcing and providing networking services for users and providing
administrative support for print, file, directory and e-mail servers.

11.10Annexure 10 - SERVICE LEVELS

E-Service is defined as the core services that are delivered by the Police department / Police institution to Government, Police or Citizen through use
of technology. Some of these e-services are already being provided by the police department of the state. However some of them will be covered
under CCTNS. Service levels refer to the parameters that can be used in measuring the efficiency, transparency & reliability of the core services in
terms of –
• Service Quality
• Service Quantity
• Service delivery time
• Cost of service
The table below captures services, service levels and transaction details for each service.
Service Levels Improvements in Service

No. of Transactions
S No Services
/month
Existing Envisaged Quantity Quality
Citizens
1 Complaints
Complaints/Information to the concerned

Not Defined 1 hr. from arrival N Y
Police Station


No. of Transactions
S No Services
/month
Receipt of complaint/case to the

Not Defined 1 day N Y
concerned Police Station/Cell/Wing
Action taken on the registered complaint Not Defined 7 days Y Y
2 FIR
1 hr. from General

Lodging of FIR Not Defined Y Y
Diary
Issuance of FIR Not Defined Immediate Y Y
3 Registration of Vehicles
Verification for registration of vehicles Not Defined 5 days N N
Issue of NOC for vehicles 5 days 1 day Y Y
4 Arms License
Verification for new arms license 20 days 15 days N Y


No. of Transactions
S No Services
/month
Verification for renewal of arms license 7 days 7 days N N
2 days after
Issue of arms license Not Defined N Y
verification
5 Details of stolen items
Details of stolen/ recovered vehicles,

Not Defined 1 day from request N Y
arms and other properties
6 Foreigner Registration
Registration of foreigners Not Defined 2 hours N Y
Issue of NOC for foreigners Not Defined 1 day N Y
7 Verification requests
Servants 30 days 10 days Y Y
Employment 10 days 10 days N N
Passport 20 days 15 days Y Y
Character 10 days 10 days N N
Tenant 30 days 10 days Y Y


No. of Transactions
S No Services
/month
8 Portal Information
Updation of information or status on the

Not Defined 4 hours N Y
portal
9 Security to VIP/Event
Provide security to VIP/Event Not Defined 2 days from request N Y
10 Surveillance
Provide surveillance of suspect Not Defined 6 hours from request N Y
Details of missing/ kidnapped persons

and their matching with arrested, Not Defined 1 day from request N Y
unidentified persons and dead bodies
Government/Police
1 Details of criminals


No. of Transactions
S No Services
/month
Details of arrested persons/ wanted

Not Defined 1 day from request N Y
criminals and their illegal activities
Details of missing/ kidnapped persons

and their matching with arrested, Not Defined 1 day from request N Y
unidentified persons and dead bodies
The SI shall monitor and maintain the stated service levels to provide quality service to State. The SLAs (Service Level Agreements) are provided in
Vol-III to this RFP.

11.11Annexure 11 – Technology Stacks for CAS (State) and CAS (Centre)

CAS (State) will be developed in two distinct technology stacks by the SDA at the Centre.
The Technical Details for CAS (State) Solution Stack 1 and Stack2, CAS (State) Offline solution,
CAS (Centre) Solution are provided in subsequent tables:
CAS (State) Solution - Stack 1
Proposed Description
Version
The Below list Solution by (include Support
and Original
is indicative Software major Provide
Year of Supplier
only Development features/ d by
Release
Agency services only)
Sun Java System
Web server Web Server 7.0 7.0 SUN HTTP Server SUN
Glassfish J2EE
Application Application Application
Server Server 3.0 SUN Server SUN
Database MySQL 5.1 SUN DB Store SUN
Operating Operating
System Solaris 10 SUN System SUN
Others
Reporting
Reporting engine Jasper Reports 3.7 Jasper Services
Email/Messagin Qmail
g Q-Mail 1.4 Community E-Mail Solution
Search:
Unstructured
data: using
openCMS search
features
Structured Data
MySQL &
Custom
application
Search Engine interface N/A N/A N/A N/A
Glassfish J2EE
Application Application
Portal Server Server 3.0 SUN Server SUN
Workflow Workflow
Engine jBPM 4.0 JBoss Engine
Rules Engine Custom built N/A N/A N/A N/A

Version
and Original
Year of Supplier
Release
Directory Sun Directory
Services Services 7.0 SUN LDAP SUN
Content
Management
DMS/CMS OpenCMS 7.5.1 OpenCMS System
Physical
Security,
Network
Security,
DB Encryption
(MySQL), DB
Access Controls,
Role Based
Access Control
(Custom
Developed),
LDAP (Sun
Directory
Security Services), N/A N/A N/A N/A
Identity
Management OpenSSO 7.0 SUN LDAP SUN
log4j, Custom
Built
application
Audit audit N/A N/A N/A N/A
ETL Custom built N/A N/A N/A N/A

CAS (State) Solution - Stack 2
Version
and Original
is indicative Software major Provided
Year of Supplier
only Development features/ by
Release
Web and
Application
Web server IIS 6 Microsoft Server Microsoft
Web and
Application Application
Server IIS 6 Microsoft Server Microsoft
SQL Server
Database 2008 2008 Microsoft DB Store Microsoft
Operating Windows Operating

System Server 2008 2008 Microsoft System Microsoft
Others
SQL Server
Reporting Reporting
Reporting engine Services 2008 Microsoft Services Microsoft
Qmail
Email/Messaging Q-Mail 1.4 Community E-Mail Solution
Search:
Unstructured
data: using
openCMS search
features
Structured Data
SQL DB Search
Engine &
Custom
application
Web and
Application
Portal Server IIS 6 Microsoft Server Microsoft
Windows
Workflow Workflow
Engine Foundation N/A N/A N/A N/A
2008 Microsoft LDAP Microsoft

Directory Microsoft Active

Version
and Original
is indicative Software major Provided
Year of Supplier
only Development features/ by
Release
Services Directory
Windows
SharePoint
DMS/CMS Services N/A N/A N/A Microsoft
Physical
Security,
Network
Security,
DB Encryption
(MySQL), DB
Access Controls,
Role Based
Access Control
(Custom
Developed),
LDAP (Sun
Directory
Identity Microsoft Active

Management Directory 2008 Microsoft LDAP Microsoft
IIS Log, Custom

Audit built N/A N/A N/A N/A
ETL SQL Server ETL 2008 Microsoft ETL Microsoft
CAS (State) Offline Solution
Version
The below list Solution by (include Support
and Original
Year of Supplier
Release
Synchronizatio
n
Solution Custom Built N/A N/A N/A N/A
J2EE
Application Apache Application
Container Apache Tomcat 6.0 Foundation container

Version
and Original
Year of Supplier
Release
MySQL / SQL 5.1/200 SUM / SUN /

Database Express 8 Microsoft DB Store Microsoft
CAS (Centre) Solution
Version
and Original
Year of Supplier
Release
Sun Java System

Web server Web Server 7.0 7.0 SUN HTTP Server SUN
Glassfish J2EE
Application Application Application
Server Server 3.0 SUN Server SUN
Sybase IQ
Database Enterprise 15.1 Sybase ETL Sybase
Operating
System Solaris
Others
Reporting Reporting
engine Jasper Reports 3.7 Jasper Services
Search:
Unstructured
data: using
Alfresco search
features
Structured Data:
Sybase DB
Search
Engine &
Custom
application
Glassfish
Application
Portal Server Server 7.0 SUN HTTP Server SUN

Version
and Original
Year of Supplier
Release
Workflow Workflow
Engine jBPM 4.0 JBoss Engine
Directory SUN Directory

Services Services 7.0 SUN LDAP SUN
DMS/CMS Alfresco
Email/Messagi
ng NA
Physical
Security,
Network
Security,
DB Encryption
(MySQL), DB
Access Controls,
Role Based
Access Control
(Custom
Developed),
LDAP (Sun
Directory
Identity
Management OpenSSO 7.0 SUN LDAP SUN
log4j, Custom
Audit Built N/A N/A N/A N/A
ETL+Data
Quality Sybase ETL 15.1 Sybase ETL Sybase

11.12Annexure 12 – Bills of Material (Department at its discretion may negotiate with SI

to alter/ substitute the quantity in the BOM proposed without having any
substantial impact in the financials)
Detailed BOM has been provided in Volume-2 of this RFP.
11.13Annexure 11 – The Registers and reports presently in Use within the Department
The Registers and reports specific to the state in Hindi and English as practiced within the
department are placed here under. This should not be construed as exhaustive. It is made
available here for reference purpose only. SI will have the responsibility to finalise required
reports and registers based on the CAS (State) made available by NCRB with due concurrence
from the department.
Table 36: List of Various Registers and Forms of the department
Sl. Registers / Reports/ Forms
1. Application for Auction

2. Application for entry in Absconder Roll
3. Application for opening dossier
4. Bail Bond
5. Dead Body Challan
6. Case Diary
7. Station Diary
8. Application form
9. Final Form
10. Form for prisoner Food
11. Lab Performa
12. MLC Form
13. MLC Requisition Form
14. Passport Verification Form
15. Police Remand Request
16. Preventive Action Form
17. Road Receipt
18. Verification Form
19. Search List

20. Seizure list

21. Arrest Memo
22. Body search Memo
23. Physical examination Memo
24. Property Seizure Memo
25. Search Memo
26. Court Order
27. Court/Govt./Higher official Order
28. SDM Order
29. Absconder Register
30. Alphabetical Register
31. Arms Register
32. Arrest Register
33. CD II
34. Character Verification Register
35. Complaint Register /Public Petition Register
36. Conviction Register
37. Correspondence Register (Receipt / Dispatch)
38. FIR Register
39. Foreigner Registration
40. Index Register
41. Inquest Form
42. Khatian 1 ( Thana )
43. Khatiyan
44. Malkhana Register
45. Missing Cattle Register
46. Missing Person Register
47. MLC Register
48. Non-FIR Register
49. Passport Register
50. Petty Case Register
51. Running Register
52. Terrorist Register (Optional)
53. Warrant Register
54. Correction Slip
55. OD (On Duty) Slip
56. Receipt of seized property list from Court

57. Supervision note

58. Enquiry Report
59. Final Report
60. FIR Format
61. Forensic Lab report
62. Medical Report
63. MLC Report
64. Post-mortem Report
65. Summon/ Warrant Report
66. Valuation Report
67. Verification Report
11.14Formats of Registers and reports presently in Use within the Department (refer
Volume-1-A)
End of Document
***

Cctns Si RFP JH Vol I f1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cctns Si RFP JH Vol I f1

Uploaded by

Copyright:

Available Formats

Request for Proposal

Implementation of Crime and Criminal Tracking

VOLUME–I: FUNCTIONAL AND TECHNICAL SPECIFICATIONS,

Last date of Submission

12:00 Hrs, 11th June, 2011

5 PROJECT CHARTER ..............................................................................................................................................66

11.6 Annexure 6 - Network Connectivity Details.................................................................................. 194

11.8.29 Technical Specification for Database Servers ................................................................ 261

FIGURE 1 - ORGANIZATION STRUCTURE JHARKHAND POLICE ....................................................................................... 82

TABLE 1: PHASE-I ROLLOUT PLAN............................................................................................................................ 60

TABLE 18: TRAINING TO BE COVERED IN PHASE-I .................................................................................................... 184

ADGP Additional Director General of Police

AIG Assistant Inspector General of Police

ASI Assistant Sub Inspector

ASP Assistant Superintendent of Police

CID Crime Investigation Department

CIPA Common Integrated Police Application

CRO Crime Record Office

CSP City Superintendent of Police

DCRB District Crime Records Bureau

DGP Director General of Police

DIG Deputy inspector General of Police

DSB District Special Branch

DSP Deputy Superintendent of Police

GRP Government Railway Police

IGP Inspector General of Police

JAP Jharkhand Armed Police

NCRB National Crime Records Bureau

NIC National Informatics Centre

PHQ Police Headquarter

RTO Regional Transport Office

SCRB State Crime Records Bureau

SDA State Designated Agency

SDPO Sub Divisional Police Officer

STF Special Task Force

SWAN State Wide Area Network

4. Help in reducing the manual and redundant record keeping.

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

1.2 BACKGROUND OF POLICE SYSTEMS IN INDIA

1.2.1 CRIME AND CRIMINAL INFORMATION SYSTEM (CCIS)

1.2.2 COMMON INTEGRATED POLICE APPLICATION (CIPA)

1.3 CRIME AND CRIMINALS TRACKING NETWORK AND SYSTEMS (CCTNS)

1.4 CCTNS IMPLEMENTATION FRAMEWORK

2.1 GOALS OF THIS RFP

4 SCOPE OF WORK FOR IMPLEMENTING AGENCY

4.1 OVERVIEW OF SCOPE

*Phased Implementation Approach:

4.2 DETAILED SCOPE OF WORK

4.2.1 GEOGRAPHICAL SCOPE

Sl. Offices No.

1 Number of Police Stations 478

2 Number of SDPO/Circles 132

7 No. of Control Room 28

9 No. of Forensic labs 1

10 No. of Finger Print Bureau 1

Total Number of Police locations 704

4.2.2 FUNCTIONAL SCOPE

Sl. Module Name Application /Service Type of Additional

1. Registration Complaint and FIR CAS-State Yes

2. Investigation Investigation CAS-State Yes

Crime Investigation CAS-State No

3. Prosecution Custody, Trial & CAS-State Yes

4. Search Module Crime & Criminal Records CAS-State Yes