JK Policecrimebranchjkpolice.nic.in/docs/JK_RFP_Vol-I.pdf · Page | 7 . VOLUME – I: FUNCTIONAL...

CRIME & CRIMINAL TRACKING NETWORK AND SYSTEMS (CCTNS)

Page | 1

VOLUME – I: FUNCTIONAL AND TECHNICAL SPECIFICATIONS

E – GOVERNANCE

MISSION MODE PROJECT (MMP)

CRIME & CRIMINAL TRACKING

NETWORK AND SYSTEMS (CCTNS)

RFP FOR SELECTION OF SYSTEM INTEGRATOR

Government of Jammu & Kashmir

VOLUME-I: FUNCTIONAL AND TECHNICAL SPECIFICATIONS

Released By:

JK Police


Page | 2


TABLE OF CONTENTS ACRONYMS ................................................................................................................................................................................. 5

1 INTRODUCTION ................................................................................................................................................................... 7

1.1 Project Background .................................................................................................................................................... 7

1.2 Background of Police Systems in INDIA ....................................................................................................................... 7

1.2.1 Crime and Criminals Information System (CCIS) ...................................................................................................... 8

1.2.2 Common Integrated Police Application (CIPA) ........................................................................................................ 8

1.3 Crime & Criminals Tracking Network and Systems (CCTNS) ......................................................................................... 9

1.4 CCTNS Implementation Framework .......................................................................................................................... 12

1.5 Goals of this RFP ....................................................................................................................................................... 12

2 PROJECT OVERVIEW .......................................................................................................................................................... 14

2.1 Need for the Project ................................................................................................................................................. 14

2.2 Vision and Objectives of Project ................................................................................................................................ 15

2.3 Stakeholders of the Project ....................................................................................................................................... 16

2.4 Desired Outcomes from Various Stakeholders .......................................................................................................... 17

3 STATE POLICE DEPARTMENT .............................................................................................................................................. 19

3.1 Organization Structure ............................................................................................................................................. 19

3.2 Existing Legacy Applications ..................................................................................................................................... 25

3.3 Existing Data Center Infrastructure ........................................................................................................................... 28

3.4 Existing JK SWAN Infrastructure ................................................................................................................................ 28

3.5 Existing Client Site Infrastructure .............................................................................................................................. 29

3.6 Existing Capacity Building Infrastructure (District Training Centers and Police Training Colleges) ............................... 30

4 CORE APPLICATION SOFTWARE ......................................................................................................................................... 32

4.1 CAS (Center) ............................................................................................................................................................. 33

4.2 CAS (State) ............................................................................................................................................................... 33

4.3 Development of CCTNS Core Application Software (CAS) .......................................................................................... 36

4.4 Overview of Services for CAS (State) ......................................................................................................................... 37

4.5 Overview of Services for CAS (Center) ....................................................................................................................... 38

4.6 Technology Stack for CAS (State) .............................................................................................................................. 39


Page | 3


4.7 Role of Software Development Agency (SDA) in supporting CAS ................................................................................ 39

5 SCOPE OF THE PROJECT ..................................................................................................................................................... 43

5.1 Geographical Scope .................................................................................................................................................. 43

5.2 Functional Scope ...................................................................................................................................................... 46

5.2.1 Functional Modules .............................................................................................................................................. 46

5.2.2 Solution and Technical Architecture ..................................................................................................................... 56

5.2.3 State Specific Requirements ................................................................................................................................. 60

5.2.4 Integration and Interfacing requirements: ............................................................................................................ 63

6 SCOPE OF SERVICE ............................................................................................................................................................. 66

6.1 Project Planning and Management ........................................................................................................................... 67

6.2 System Study, Design, Application Development and Integration .............................................................................. 71

6.2.1 Preparation of System and Software Requirements Specifications (SyRS and SRS) ................................................. 73

6.2.2 Preparation of CAS Implementation document ..................................................................................................... 73

6.2.3 Preparation of Solution Design ............................................................................................................................. 74

6.2.4 Configuration, Customization, Extension (New modules) of CAS (State) and Integration with CAS (Center) and External agencies ............................................................................................................................................................... 78

6.3 Infrastructure at the District Training Centers ........................................................................................................... 83

6.4 ........................................................................................................................................................................................ 83

6.5 Site Preparation at Police Stations and Higher Offices ............................................................................................... 84

6.6 Infrastructure at the Client Site Locations ................................................................................................................. 85

6.7 Network Connectivity for Police Stations, Higher Offices and District Training Centers .............................................. 86

6.8 Scope of Work of System Integrator with respect to Network Connectivity ............................................................... 87

6.9 IT Infrastructure at the Data Center and Disaster Recovery Center ............................................................................ 89

6.10 Data Migration and Data Digitization ........................................................................................................................ 91

6.11 Migration of CIPA and CCIS Police Stations/ Higher Offices to CCTNS ......................................................................... 95

6.12 Change Management ............................................................................................................................................... 96

6.13 Capacity Building .....................................................................................................................................................105

6.14 Handholding Support ..............................................................................................................................................110

6.15 Requirement on Adherence to Standards ................................................................................................................110


Page | 4


6.16 Support to 3rd Party Acceptance Testing, Audit and Certification .............................................................................111

7 SCOPE OF SERVICES DURING POST IMPLEMENTATION PHASE ...........................................................................................114

8 IMPLEMENTATION AND ROLL-OUT PLAN ..........................................................................................................................115

8.1 Implementation and Project Roll-Out Plan ...............................................................................................................117

9 SERVICE LEVELS ................................................................................................................................................................123

10 ANNEXURE ..................................................................................................................................................................124

ANNEXURE I CONTACT DETAILS ............................................................................................................................................124

ANNEXURE II LIST OF 23 CIPA POLICE STATIONS AND EXISTING LEGACY SYSTEMS .................................................................127

ANNEXURE III PROPOSED DC FOR THE POLICE DEPARTMENT ................................................................................................133

ANNEXURE IV HARDWARE DETAILS OF POLICE DEPARTMENT ...............................................................................................135

ANNEXURE V TOTAL NUMBER OF POLICE OFFICES ................................................................................................................136

ANNEXURE VI EXISTING LEGACY SYSTEMS ............................................................................................................................137

ANNEXURE VII POWER SUPPLY .............................................................................................................................................142

ANNEXURE VIII: CAS STACK TECHNOLOGY ...........................................................................................................................148

ANNEXURE IX: POST IMPLEMENTATION SUPPORT SERVICES .................................................................................................152

ANNEXURE X: SERVICE LEVELS ..............................................................................................................................................157

ANNEXURE XI: FUNCTIONAL REQUIREMENT SPECFICATIONS ................................................................................................176

ANNEXURE XII: INDICATIVE TECHNICAL SPECFICATIONS ........................................................................................................205

ANNEXURE XIII: INDICATIVE HARDWARE BILL OF MATERIAL .................................................................................................247

ANNEXURE XIV: E GOVERNANCE STRUCTURE .......................................................................................................................252

ANNEXURE XV: Status of JKSWAN (List of Identified POPs) ....................................................................................................255

ANNEXURE XVI: TECHNICAL ARCHITECTURE .........................................................................................................................260

ANNEXURE XVII – NETWORK CONNECTIVITY FOR P/S & HIGHER OFFICES. .............................................................................263

ANNEXURE XVIII – LIST OF CIPA P/S, NON-CIPA P/S AND OTHER HIGHER OFFICES. ................................................................264

ANNEXURE XIX – CURRENT STATUS OF CAPACITY BIULDING IN J&K ......................................................................................275


Page | 5


ACRONYMS ACP : Assistant Commissioner of Police. ADGP : Additional Director General of Police AMC : Annual Maintenance Cost. BPR : Business Process Reengineering. CBI : Central Bureau of Investigation. CBT : Computer Based Training. CCIS : Crime & Criminal Information System. CCTNS : Crime & Criminal Tracking Network and System. CDMA : Code Division Multiple Access CFC : Citizen Facilitation Counter. CI : Circle Inspector. CID : Crime Investigation Department. CIPA : Common Integrated Police Application. CRPC : Criminal Procedure Code. CSC : Common Service Center. DCRB : District Crime Record Bureau. DDO : District Development Officer. DGP : Director General of Police. DIGP : Deputy Inspector General of Police. DIT : Department of Information Technology DM : District magistrate. DPO : District Police office. DSP : Deputy Superintendent of Police. FB : Fingerprint Bureau. FIR : First Information Report G2B : Government to Business. G2C : Government to Citizen. G2G : Government to Government. GoI : Government of India. HQ : Head Quarter. ICT : Information & Communication Technology. IGP : Inspector General of Police. IIC : Inspector In charge. IO : Investigating Officer. IPC : Indian Penal Code. IT : Information Technology. LAN : Local Area network. MHA : Ministry Of Home Affairs. MIS : Management of Information System. MMP : Mission Mode Project. NCRB : National Crime Record Bureau. NeGP : National e-Governance Plan NIC : National Informatics center. SPMU : State Project Management Unit. PoP : Point of presence.


Page | 6


PS : Police Station. PTS : Police Training School. RFP : Request For proposal. RPC : Ranbir Penal Code SCRB : State Crime Record Bureau. SDC : State Data Center. SDPO : Sub Divisional Police Office. SFSL : State Forensic Science Laboratory. SLA : Service Level Agreement SMMP : State Mission Mode Project. SP : Superintendent of Police. UAT : User Acceptance test UPS : Uninterruptible Power Supply. VIP : Very Important Person. VSAT : Very Small Aperture Terminal. MPLS : Multiprotocol label Switching VPN : Virtual private Network. BB : Broadband. VSAT : Very Small Aperture terminal. CDMA : Code Division Multiple Access.

SWAN : State Wide Area network


Page | 7


1 INTRODUCTION

1.1 Project Background

CCTNS is a Mission Mode Project under the National e-Governance Plan of Govt. of India.

CCTNS aims at creating a comprehensive and integrated system for enhancing the efficiency

and effectiveness of Policing through adopting of principle 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'. Crime and Criminal Tracking

Network & Systems (CCTNS) is a plan scheme conceived in the light of experience of a non-plan

scheme namely - Common Integrated Police Application (CIPA). Police organizations

everywhere have been handling large amounts of information and huge volume of records

pertaining to crime and criminals.

Information Technology (IT) can play a very vital role in improving outcomes in the areas

of Crime Investigation and Criminals Detection and other functioning of the Police

organizations, by facilitating easy recording, retrieval, analysis and sharing of the pile of

Information. Availability of relevant and Timely information is of utmost necessity in conduct of

business by Police, particularly in investigation of crime and in tracking & detection of criminals.

Quick and timely information availability about different facets of Police functions to the right

functionaries can bring in a sea change both in Crime & Criminals handling and related

Operations, as well as administrative processes.

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.


Page | 8


1.2.1 Crime and Criminals Information System (CCIS)

CCIS is an NCRB-driven program and has been launched in 1990. Since then, it has

been implemented in 35 states and union territories and spans over 700 locations. Most

of the state police headquarters and district headquarters are covered by CCIS and so are

some of the 14,000+ police stations in the country.

CCIS is primarily an initiative to create crime- and criminals-related database that

can be used for crime monitoring by monitoring agencies such as National Crime Records

Bureau (NCRB), State Crime Records Bureaus (SCRBx) and District Crime Records Bureaus

(DCRBx) and to facilitate statistical analysis of crime and criminals related information

with the States and monitoring agencies.

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 inefficiency and

transparency in various processes and functions at the Police Station level and improve


Page | 9


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.

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

support the crime investigation and prosecution functions. CIPA is a centrally managed

application: an application core centrally developed and is installed in police station. Any

state-specific customizations are evaluated and made on a need basis.

The core focus of the CIPA application is the automation of police station operations.

Its core functionality includes the following modules: (i) Registration Module (ii)

Investigation Module (iii) Prosecution Module. There is also a Reporting module that

addresses basic reporting needs.

CIPA is built on client-server architecture on a NIC Linux platform using Java and

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 & Criminals Tracking Network and Systems (CCTNS)

Ministry of Home Affairs (MHA) has conceptualized CCTNS as a Mission Mode Project

towards enhancing outcomes in areas of Crime Investigation, Criminals detection; and

enhancing effectiveness and efficiency of policing through creation of a nationwide, networked

infrastructure for evolution of IT-enabled state-of-the-art system. National Crime Records

Bureau (NCRB) is the central JK police that would manage the implementation of CCTNS under

the overall supervision and guidance of MHA.

The Project CCTNS is related to automations of Police functions, sharing of crime and

criminal information amongst various formations of Police and other stake holders in the

system and public service delivery therefore there will be no yield from the project in financial


Page | 10


terms. This will increase the efficiency of Police, policy planners and criminal justice system as a

whole and improve the quality and service levels of the public services being offered by the

Police to public. The project will improve the services and service levels within the Police

department, criminal justice system and those to be offered to public which cannot be

translated into financial terms nevertheless it will substantially reduce the expenditure on the

stationery, special messengers for carrying messages, man-efforts, dak and postage.

The Hardware maintenance, Software development and maintenance is covered in its

cost during the plan period. The State of Jammu and Kashmir would bear all expenses with

regard to Crime and Criminal Tracking Network and Systems (CCTNS) project beyond the XI

Five-Year Plan period.

The overall objective of the Project is based on enhancing the operational efficiency and

effectiveness of the Police force in delivering the services. The broad objectives of the project

are as follows:

• 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.

• Improving delivery of citizen centric services through effective usage of Information & Communication Technology (ICT).

• Provide the Investigating Officers with the tools, technologies and information to facilitate faster and more accurate investigation of crime and detection of criminals.

• Improve the Police functioning in various other areas such as Law & Order, Traffic Management, curbing organized crimes, resource management etc.

• Facilitate collection, storage, retrieval, analysis, transfer and sharing of data and Information among Police Stations, Districts, State headquarters and other organizations/ agencies, including those at Government of India level.

• Enabling and assisting the senior Police Officers in better management of Police Force.

• Keep track of the progress of the crime and criminal investigation and prosecution Cases, including progress of cases in the Courts.

• Reduction in manual and redundant Record keeping.

• Provide easy and alternate access to the service users in interacting with the department/ Agency.

• Reduce the response time of the Police to the service users by automating its workflows for approvals and sanctions.

• Empower the Citizen/service users with required information on various activities of the Police and the various assistances available for different categories of beneficiaries.


Page | 11


• Provide accurate and reliable status information on all the requests made by the beneficiaries.

• Provide accurate and reliable information on the various schemes.

• Strengthening the internal system.

• Facilitating Interaction and sharing of Information among Police Stations, Districts, States etc. and other Police Agencies.


Page | 12


1.4 CCTNS Implementation Framework

As an integral part of the Implementation frame works, the State Government will play

the significant role in the implementation of the project. MHA and NCRB would play a key role

in planning the program in collaboration with the Police leadership within the State of Jammu &

Kashmir, in the development of a few core components and in monitoring and reviewing the

program. It is, however, the State that would drive the planning and Implementation of the

project at the State level. MHA and NCRB focuses primarily around planning, providing the core

application software (CAS) which is to be configured, customized, enhanced and deployed for

the Jammu and Kashmir Police department. The State 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. According to this, each

States selects 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,

associated services such as Capacity Building and Handholding, etc.

1.5 Goals of this RFP

This volume of RFP intends to bring out all the details with respect to solution and other

requirements that are deemed necessary to share with the potential bidders.

The goals of RFP are further elaborated below:

• To seek proposals from potential bidders for providing the “bundle of services” in implementing and managing the CCTNS solution in States.

• 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.


Page | 13


The State reserves the right to reject any or all the bids without assigning any reason. The

State further reserves the right to negotiate with the selected agency to enhance the quality

and quantity of this project and to create a more amicable environment for the smooth

execution of the Project adhering to State Government rules and regulations.

Email:

Address for Communication for the purpose of this RFP:

Deputy Inspector General of Police, J&K (Crime) Old PHQ Complex, CPO Chowk Panjtirthi, Jammu – Jammu and Kashmir - 180001

Ph: 0191-2561694 [email protected]; [email protected]

(i) Old PHQ complex (Nov - April)

State CCTNS Project Nodal Officer:

Inspector General of Police, J&K (Crime)

Panjtirthi, Jammu - Jammu and Kashmir Ph: 0191-2564210 Fax: 0191-2564210

(ii) Royal Apartments (May -Oct) Near Rajbagh Police Station Srinagar - Jammu and Kashmir Ph: 0194-2310912 Email: [email protected]

mailto:[email protected]�




Page | 14


2 PROJECT OVERVIEW

2.1 Need for the Project

As the MHA has taken CCTNS a Mission Mode Project under 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.

The CCTNS project covers all 35 States and union territories. CCTNS will cover all the

Police Stations in the States, and also the Sub-Divisions, District headquarters, Range

headquarters, Zonal IG offices and State headquarters. Necessary Hardware will be provided at

all these locations including data centers at State and National headquarters. All these locations

will be networked by providing appropriate high speed connectivity for data transfer and

sharing of information amongst various stakeholders.

To facilitate standardization across States/ UT’s NCRB would develop Core Application

Software (CAS) centrally through a Software Development Agency (SDA). CAS has two

components viz CAS (Centre) and CAS (State) which would then be customized and

implemented at the State level by the System Integrator (SI).

Each State/ UT is required to implement State level Core Application Software CAS (State).

CAS (State) would include selected functionalities of the Police Department at the State level,

with emphasis on the Police Station functionality. CAS (State) needs to be designed and

implemented as per the unique requirements of each State. At the same time, CAS (State) is

also required to integrate with CAS (Centre), with full Synchronization of data across the sub

level and main database.


Page | 15


2.2 Vision and Objectives of Project

Vision: To transform the police force into a knowledge-based force and improve the

delivery of citizen-centric services through enhancing the efficiency and effectiveness of the

police stations by creating a platform for sharing crime and criminal information across the

police stations in the country.

The overall objective of the MMP is based on enhancing the operational efficiency and

effectiveness of the police force in delivering the services.

The broad objectives of the project are as follows:

a) Improve Service Delivery to the Public

Citizens should be able to access police services through multiple, transparent, and easily

accessible channels in a citizen-friendly manner. The focus is not only to improve the

current modes of the service delivery but also provide alternate modes such as internet for

the public to communicate with the police.

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.

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.


Page | 16


2.3 Stakeholders of the Project

The impact of the police being very subjective, consultative and bottom up approach is to

be adopted in designing the CCTNS Project impacting the various stakeholders.

• Citizens

• MHA/ NCRB/ SCRB

• State Police Department/ Police Officials

• Courts

• DM Office

• Regional Passport Office

• Regional Transport Office

• Civil Defense/ Disaster Management/ Flooding

• PMF/ SF

• FSL/ State Vigilance Organization

• Non – Government / Private Sectors


Page | 17


2.4 Desired Outcomes from Various Stakeholders

The following are the expected benefits from the various stakeholders.

• Multiple channels to access services from Police

Benefits to citizens:

• 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 against Police

• Simplified process for tracking the progress of the case during trials

• Tracking of different type of verifications/ NoC (service verifications, NGO verifications, character Certificates, etc.)

• 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

• Ability to view and pay pending traffic challans from multiple access points

• Faster and assured response from police to any emergency calls for Assistance

• Enhanced tools for investigation

Benefits to Police Department:

• Centralized crime and criminal information repository along with the criminal images and fingerprints with advanced search capabilities

• Enhanced ability to analyze crime patterns, modus operandi

• Enhanced ability to analyze accidents and other road incidents

• Faster turnaround time for the analysis results (crime & traffic) to reach the officers on the field

• Reduced workload of the police station back-office activities such as preparation of regular and adhoc 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 different regions and units

• Better coordination and communication with external stakeholders through implementation of electronic information exchange systems

• Advanced tools for traffic regulation and enforcement/ Online verification of RCs and DLCs


Page | 18


• Faster and easier access to crime and criminal information across the country in a manner amenable for trend and pattern analysis

Benefits to Police Personals:

• Enhanced ability to detect crime patterns and modus operandi across the States and communicate to the State Police Departments for aiding in crime prevention

• Reduction of paper work

• Reduction of workload

• Proper monitoring system for the higher offices

• Balanced performance evaluation metrics and framework

• Simplified process for registering grievances within the department

• Seamless integration with Police systems for better citizen service delivery and improved law enforcement.

Benefits to External Departments:


Page | 19


3 STATE POLICE DEPARTMENT

Jammu and Kashmir Police was established in 1873 and highly decorated force. The JK Police

is scripting a saga of valour. It has met various challenges successfully, especially in the fight against

terrorism and has upheld the honor of the organization and maintained the public trust. The JK

Police has emerged as one of the best forces in the country and is proud to have been recognized

as a symbol of bravery by the central and the State Governments.

Though its mission is to restore lasting peace and complete normalcy in the State, but to deal

with the day-to-day crime and law and order situations is its basic duty. The J& K Police have to

continue its fight against terror with full might and determination and at the same time serve the

people of the State with a renewed zeal to make Jammu & Kashmir a most peaceful State in the

country.

The command and control of the JK Police vests with the Director General of Police, J&K,

(DGP) who is in-charge of the entire gamut of Police Administration viz recruitment, discipline, law

enforcement, internal economy and administration in the State of J&K. Besides being the head of

the Police Department, the DGP, J&K is responsible for advising the Government on all matters

connected with it.

3.1 Organization Structure

The Jammu and Kashmir has two State Police Headquarters one in Srinagar and the other

in Jammu. The Director General of Police is headquartered in Srinagar during the summer

months and in winter the office of Director General of Police moves to Jammu the winter

capital along with Darbar Move.

The State is divided in two Executive Police Zones as follows:

a. Jammu Zone

b. Kashmir Zone

Further, each Zone is headed by a Zonal Inspector General of Police (IGP) who is overall In-

charge of law and order situation in the respective Zone; the two zones are further sub-divided

into Ranges, each headed by an officer of the rank of a Dy. Inspector General of Police (DIG).

Presently, there are seven Ranges, four in Jammu Zone and three in Kashmir Zone. The Range

DIG supervises the Police administration in the Districts, each of which is headed by an officer


Page | 20


of the rank of Superintendent of Police (SsP)/ Sr. Superintendent of Police (SSsP). The District

SsP/ SSsP are assisted by one or more Additional Superintendents of Police/ Chief Prosecuting

Officers, Asst. Dy. Superintendents of Police, Sr. Prosecuting Officers in the discharge of their

duties. To bring the Police administration nearer to the people, Districts have further been

divided into Sub divisions, Police Stations and Police Posts/ Divisions. The Sub-Divisions are

headed by officers of the rank of Assistant / Deputy Superintendent of Police. Presently, J&K

have a total of 190 Police Stations (including two Women Police Stations one each at Srinagar

and Jammu) and 259 Police Posts/ Divisions in the State of J&K manned by Police personnel of

the rank of Inspectors, Sub-Inspectors, Asst. Sub-Inspectors, Head Constables.


Page | 21


Police Headquarters has following officers to assist Director General of Police in the

administration of Police organization:

• Addl. DGP (Headquarters) • IGP (Headquarters) • IGP (Personnel/ Trainings) • IGP (Modernization) • IGP (Tech) • Director of Prosecution.

In addition to this various branches like:

• Establishment Section • Personnel Section • Provision Section • Welfare Section • Building Section • Trainings Section • Human Rights Section • Prosecution Section • Arms and Ammunition Section • Confidential Section • Crime Intelligence Vigilance Section • Motor & Transport Section • APR Section • Deployment Section

Estates Section also assists the Director General of Police in his administration.

The following offices also move along with Darbar Move which has provincial offices at

Srinagar/ Jammu working round the year:-

1. CID Headquarters, headed by Additional Director General of Police 2. Crime Headquarters, headed by Inspector General of Police 3. Railways Headquarters, headed by Inspector General of Police 4. Security Headquarters, headed by Inspector General of Police 5. Armed Police headed by Additional Director General of Police 6. HG/ CD headed by Addl. Director General of Police 7. Police Housing headed by Inspector General of Police as MD 8. Traffic headed by Inspector General of Police


Page | 22


JK POLICE HEADQUARTERS

The Police Headquarters is headed by the Director General of Police who is assisted by

ADG and Inspector General of Police (Hqrs.), Inspector General of Police (Personal & Training),

Inspector General of Police (Modernization), Inspector General of Police (Technical), Dy.

Inspector General of Police (Administration), Director Prosecution, and Asst. Inspector General

of Police (Personnel), Asst. Inspector General of Police (CIV), Asst. Inspector General of Police

(Provisioning & Transport) Asst. Inspector General of Police( Welfare),Dy. Director Prosecution,

Dy. Director Buildings/ Planning & Statistics, Chief Accounts Officer, who in turn are assisted by

CPO, Sr. PO’s, Dy. SsP, Prosecuting Officers (PRO), Section Officers & Dealing Assistants to deal

with various facets of administration, law enforcement, logistics, establishment and policy

planning like:

ARMED POLICE WING

The Armed Police is headed by an officer of the rank of ADG and assisted by Inspector

General of Police (IGP) in both the zones. For effective supervision, the IGP Armed is assisted by

two (02) DIsG, one in Jammu and the other in Kashmir, & one Dy. Director Prosecution, One

CPO & one Sr. PO. The two DIsG exercise superintendence over Armed/ IRP Battalions, each

headed by a Commandant of the rank of SSP/ SP and deployed in every nook and corner of J&K

State. There are at present 11 Armed and 20 IR in the State. The Armed Police is not deployed

for routine duties but instead used as a specialized force to deal with the maintenance of law

and order and to combat militancy.

SECURITY WING

The Security wing is supervised by an officer of the rank of Inspector General of Police

(IGP Security) who in turn is assisted by a DIG Security, Staff Officer & a Chief Prosecuting

Officer. The Security wing has the charter of providing security to protected persons, vital

installations and to secure venues during sensitive & important events.

TRAFFIC POLICE WING

The Traffic wing is headed by an officer of the rank of Inspector General of Police (IGP)

who is assisted by one S.O, Dy. Director Prosecution, and CPO& Sr. PO. The IGP supervises two

traffic Range DIG’s and Zonal traffic SsP who are charged with ensuring the smooth flow of

traffic at Jammu, Srinagar and the National Highway respectively. This wing is primarily engaged

in regulating traffic and enforcement of traffic laws.


Page | 23


CRIME WING

This wing is headed by an officer of the rank of Inspector General of Police (IGP) who is

assisted by a DIG, Staff Officer, DDP, CPO’s & Sr. PO’s, and SSsP each at Jammu and Srinagar, in

the discharge of his duties which include investigating cases of public importance, collection

and consolidation of crime data, supervision of State Crime Records Bureau (SCRB), Crime

Photograph Cell and maintenance of Dog Squad. Two (02) Police Stations, one at Srinagar and

other at Jammu, the Crime Branch, have powers of investigation vested with them vide J&K

Government Home Dept. Order SRO 202.

RAILWAYS WING

The Railway Wing is headed by an officer of the rank of IGP who is assisted by one DIG at

Hqrs. and SSsP Railways Jammu & SSsP Railways Kashmir. The Railway Police deals with criminal

cases at Railway Platforms and tracks besides protection of Railway property.

PROSECUTION WING

This cadre is headed by an officer designated as Director Prosecution posted in the Police

HQRS, who in turn is assisted by Dy. Director Prosecution (SsP), Chief Prosecuting Officer, Sr.

Prosecuting Officers (Dy. SsP) and Prosecuting Officers (Insps). All the department al litigations

viz Writs, appeals, civil suits, claim petitions, SLP’s, contempt’s, criminal prosecution etc are

conducted/ dealt with and supervised by this wing. The officers of this wing being police

officers are also posted in the field for various law and order duties besides act as law

instructors& legal advisors of the department.

FSL WING

An officer of the rank of IGP designated as IGP (Tech) exercises control over the Forensic

Science Laboratory (FSL) which in turn is headed by Director FSL who works under the overall

super vision of IGP (Tech) who operates from PHQ. There are two (02) Forensic Science

Laboratories at Jammu and Srinagar along with ten (10) Field Mobile FSL units. The FSL has

various sections like Chemistry and Toxicology, Biology and Serology, documents, finger print

and foot print, physics, Ballistic, Polygraph and Explosive section. The FSL provided scientific

aids in the investigations and thus play an important role in the administration of criminal

justice system.


Page | 24


HOME GUARD/ CIVIL DEFENCE/ AUXILIARY POLICE WING

This wing is headed by the DGP J&K who is ex-officio Commandant General and assisted

by Joint Commandant General of the rank of ADGP designated as ADG/ HG/ CD/ Auxiliary

Police. The IGP is further assisted by a DIG, who exercises command and control over Civil

Defense/ Home guards and two Auxiliary Police Battalions one each at Jammu and Srinagar

which are headed by officers of the rank of SsP/ SSsP. The Auxiliary Police discharges

multifarious duties such as assisting the civil Police in traffic control/ regulation, maintenance of

law and order and protection of life and property. The Auxiliary Police Battalions also organizes

training of Civil Defense and Home Guard Volunteers to meet any eventuality and extend a

helping hand during emergencies like natural disasters.

POLICE COMMUNICATION WING

This wing is headed by an officer of the rank of IGP (Tech) who is further assisted by an

officer of rank of DIG, designated as Director, Police Telecommunication and assisted by

technical personnel. The Director is responsible for installation, functioning and maintenance of

Police Telecommunication grid in the State linking Police Stations, Control Rooms, District

Headquarters and other Police wings.

POLICE HOUSING CORPORATION (PHC)

There is an independent Housing Corporation called the Police Housing Corporation (PHC)

to execute construction works of JK Police. The PHC is headed by Managing Director of the Rank

of IG and one Superintending Engineer, Executive Engineers, one each for Jammu and Kashmir

Divisions, Assistant Executive Engineers and Jr. Engineers. The Engineering staff of PHC is on

deputation to the Corporation.

The list of addresses designations and contact details of the officials are provided as an Annexure to this

RFP.


Page | 25


3.2 Existing Legacy Applications

The existing system in the State of Jammu and Kashmir is not well organized yet. CCIS is a

project developed by NCRB on the basis of seven integrated forms. Crime Criminal information

system (CCIS) was introduced in the J&K State vide SRO No. 47 of 2003 dated 19th Feb. 2003.

Further a project called CIPA (Common Integrated Police Application) which is a multilingual

application to automate the processes (workflow) at primary sources of data itself was

implemented in 23 police stations out of 190 across the state of J&K. But still majority of the

work is being done manually and then the date is being stored at DPO level, which is

subsequently forwarded to SCRB, Jammu in the form of Compact Disc (CD) which in turn is

being stored in standalone Server’s for storage purpose. The below listed table show the

current deployed applications which are being used at DPO level.

The below table shows current applications that are deployed in JK police S. N. Application

Name Description of Services provided by Application

Application architecture (Centralized/ Decentralized)

Development Platform – Web Enabled or not

Database/ Operating System

Developed By Location (HO/ DO/ ZO/ MO/ Any other level) Centralized/ Decentralized

1 Crime Criminal Information System

CCIS Decentralized Local application

Windows Server 2000

NCRB DO

2 Motor Vehicle Coordination System

MVCS Decentralized Local application

Windows Server 2000

NCRB HO

3 Payroll Payroll Decentralized Local application

Windows Server 2000

Local level development

DO level

4 Organized Crime Information system

OCIS Decentralized Local application

Windows Server 2000

NCRB SCRB/HO

5 FACTs FACT Decentralized Local application

Windows Server 2000

Private Party SCRB/HO

6 CIPA CIPA Decentralized Local application

Linux (OS), Postgres (RDBMS).

NIC/NCRB P/S

7 PIF PIF Decentralized Local application

Windows XP, VB/ Access

Local level development

DO


Page | 26


Crime and Criminal information system (CCIS): CCIS is a project developed by NCRB on

the basis of seven integrated forms. CCIS was installed and implemented in all the States in the

year 1996. Crime Criminal information system (CCIS) was introduced in the J&K State vide SRO

No. 47 of 2003 dated 19th Feb. 2003. So far the State has entered 390074 records/ Forms in the

database.

Motor Vehicle Coordination System: MVCS is designed for coordination of stolen and

recovered motor vehicles as well as inquiries relating to these. This service has been made web-

enabled which will facilitate the Police Department. MVCS is based on SQL, which is used to

track the stolen/ recovery vehicles. So far the State has entered 750731 records in the

database. All concerned DPO’s are sending the data to SCRB where it is manually entered into

MVCS application.

Payroll: Generation of the Pay bill schedules of Pay & Bank Statements. The accounts

officer of every department has to generate Pay bill for every month for the serving employees.

The manual generation requires a lot of labor for generation of pay bills. The Computerization

of pay reduced the manual labor and generates the pay bill without any flaws.

Organized Crime Information system (OCIS): OCIS aims to create a comprehensive

database in respect of terrorists/ underworld elements and organized criminals for effective

coordination of activities and sharing of data and preparation of background files on such

organized criminals/ gangs. The OCIS has been started on pilot basis in 8 States for crimes of

‘automobile thefts’ and ‘trafficking in women and children for prostitution and maid services’.

Fingerprint analysis and Criminal Tracing System (FACTS): FACTS are an advanced

automatic fingerprint identification system, with state-of-the-art digital image processing,

neural networks and pattern recognition techniques. It automatically extracts fingerprint

features for matching, using high-speed and high-accuracy unified matcher algorithm (UMA).

Common Integrated Police Application (CIPA): The Common Integrated Police Application

(CIPA) is developed by NIC under the guidelines of NCRB and MHA. CIPA phase first is

implemented in 23 police stations of Jammu and Kashmir State. CIPA is a multilingual

application to automate the processes at Police Station and to build a crime & criminal

Information system based on CrPC. It provides an efficient way of organizing crime records for

generating queries/ reports and crime analysis for decision support.


Page | 27


Personal Information System: The Personnel Information system is a Computer based

system for maintenance of the Service Registers of individuals in an organization. The details

pertaining to personnel, postings, qualifications, departmental tests passed, training attended,

family details etc are stored in this system. Retrieval of information is possible based on any

individuals or on collective information grouped by certain categories namely designation,

retirement, length of service, place of working etc.

The List of the 23 Police Stations and the details pertaining to the technology platform, Network

connectivity, availability of the hardware/ other facilities, services offered and Existing Legacy System is given in

detail as an Annexure to this RFP.


Page | 28


3.3 Existing Data Center Infrastructure

The State Data Center of Jammu and Kashmir is not yet in place; however the process of

selecting the vendor is completed and M/S Trimax Pvt.Ltd has been awarded the letter of

Intent. The site for hosting SDC has been decided to be the IT enclave in Jammu Secretariat.

If the SDC will not be ready till the timelines of CCTNS Implementation, SCRB may be

temporarily utilized for installation of the Police DC equipment’s. After the completion of SDC,

all the Police Data Center equipment shall be moved to SDC. The location for the proposed

Police Data Centre is decided to be SCRB, Jammu, whereas the location of the Disaster Recovery

Site is proposed to be NCRB, New Delhi.

The details pertaining to the proposed DC for the Police Department is given as an Annexure to this RFP.

3.4 Existing JK SWAN Infrastructure

The SWAN is not yet in place in the State of Jammu and Kashmir. The Detailed Project

Report (DPR) has been prepared by Consultants from Software Technology Park of India (STPI)

and the same has been approved by DIT, Government of India. The Request for Proposal (RFP)

has also been prepared and currently bid process phase of the project has been initiated.

JKSWAN is to provide connectivity to all the government departments. The identification of

POPs is in process and till now, 174 have been identified. JKSWAN is considered to be the

secondary back up for the CCTNS Project.

Details of JKSWAN POPs identified across the State are attached as an Annexure to this RFP.

Currently, none of the Police Stations is interconnected to their District Police offices. The

District Police offices have been provided the connectivity of 2Mbps bandwidth. All District

Polices across Jammu and Kashmir are connected to SCRB Jammu with the leased line of 2

Mbps bandwidth for transmission of data, however none of the District Police offices are

sending the data across the leased line. Data from respective CIPA enabled Police Stations as

well as from District Police offices are copied over to the compact disks and are physically sent

to SCRB Jammu for storage purpose.


Page | 29


3.5 Existing Client Site Infrastructure

In the State of Jammu and Kashmir majority of the Police Stations are housed in the

Government. During our survey we found some basic facilities missing in some of the remote

areas, and they are not having appropriate power supply due to curtailment and offices below

DPO level need to be renovated, as majority of them are lacking necessary flooring and

furnishings.

Further offices above DPO level are lacking proper communication. Even DPO, Range

offices, Zone Office & PHQ is lacking behind in communication. The table below is showing a list

of 23 Police Stations out of 190 where basic computerization needs have been fulfilled.

The below table shows current Hardware that has been deployed in JK police, under CIPA Project DISTRICTS POLICE

STATION

Clie

nt C

ompu

ter

Mak

e &

Mod

el

Ope

ratin

g Sy

stem

Mem

ory

Mul

ti-Fu

nctio

nal

Prin

ter

(Prin

t/Sc

an/C

opy)

16 P

ort S

witc

h

Mod

em/

Fax

Card

s (A

dditi

onal

Item

)

HDD

120

GB

Addi

tiona

l Ite

m)

DVD

Writ

er I/

O

DVD

RO

M D

rive

UPS

2KV

A O

nlin

e

Anantnag Anantnag 05 Acer Linux 512 01 01 Nil Nil 02 01 Baramulla Baramulla 05 Acer Linux 512 01 0 Nil Nil Nil 01 Budgam Budgam 05 Acer Linux 512 01 01 Nil Nil 02 01 Doda Doda 05 Acer Linux 512 01 01 02 02 02 01 Jammu City 04 Acer Linux 512 01 01 Nil Nil 02 01 Jammu Gandhi Nagar 05 Acer Linux 512 01 01 Nil Nil 02 01 Kargil Kargil 03 Acer Linux 512 01 01 Nil Nil 02 01 Kathua Kathua 05 Acer Linux 512 01 01 02 02 02 01 Kupwara Kupwara 05 Acer Linux 512 01 01 Nil Nil Nil 01 Leh Leh 04 Acer Linux 512 01 01 02 02 02 01 Poonch Poonch 05 Acer Linux 512 01 01 Nil Nil Nil 01 Pulwama Pulwama 04 Acer Linux 512 01 01 Nil Nil Nil 01 Rajouri Rajouri 05 Acer Linux 512 01 01 02 02 02 01 Srinagar Karan Nagar 04 Acer Linux 512 01 01 Nil Nil 04 01 Srinagar Kothibagh 05 Acer Linux 512 01 01 Nil Nil 05 01 Udhampur Udhampur 05 Acer Linux 512 01 01 02 02 02 01 Samba Vijaypur 04 Acer Linux 512 01 01 02 02 02 01 Ganderbal Ganderbal 05 Acer Linux 512 01 01 Nil Nil 02 01 Kulgam Kulgam 04 Acer Linux 512 01 01 Nil Nil 02 01 Awantipora Awantipora 05 Acer Linux 512 01 01 Nil Nil Nil 01 Ramban Ramban 04 Acer Linux 512 01 0 Nil Nil Nil 01 Reasi Reasi 05 Acer Linux 512 01 01 02 02 02 01 Handwara Handwara 05 Acer Linux 512 01 01 Nil Nil Nil 01

Total 105 23 21 14 14 37 23


Page | 30


3.6 Existing Capacity Building Infrastructure (District Training Centers and Police Training

Colleges)

In the State of Jammu and Kashmir there are a total number of 6 Training centers/

Colleges under further augmentation, one State Crime Record Bureau (SCRB) and 25 District

Training Centers. Each lab is equipped with a minimum of 6 computers, one Multi-Function

Printer, one Projector with Screen, one 16 Port Switch and 5KV online UPS for backup purpose.

Each of the labs is well furnished and fully functional out of which one or two sites still need

renovation. Below are some pictures that have been taken from District Training Centers –

Srinagar.


Page | 31


The below table shows current Hardware that has been deployed in District Training

Centers and Police Training Colleges

S. No DISTRICT Computers- HP-8000 Model- Intel Core Duo

UPS- 5.0 KV Elnova

Printer- HP-1522 Printer/ Scanner/

Copy/ Fax

Projector DLP Multimedia NEC NP 210-G with Screen

1 SRINAGAR 15 01 01 01 2 BUDGAM 10 01 01 01 3 GANDERBAL 10 01 01 01 4 BARAMULLA 15 01 01 01 5 BANDIPORA 10 01 01 01 6 KUPWARA 10 01 01 01 7 PULWAMA 08 01 01 01 8 SHOPIAN 08 01 01 01 9 KULGAM 08 01 01 01 10 ANANTNAG 15 01 01 01 11 LEH 10 01 01 01 12 KARGIL 10 01 01 01 13 JAMMU 15 01 01 01 14 SAMBA 10 01 01 01 15 KATHUA 10 01 01 01 16 DODA 10 01 01 01 17 KISHTWAR 10 01 01 01 18 RAMBAN 10 01 01 01 19 UDHAMPUR 10 01 01 01 20 REASI 10 01 01 01 21 RAJOURI 15 01 01 01 22 POONCH 10 01 01 01 23 PD SOPORE 06 01 01 01 24 PD AWANTIPORA 08 01 01 01 25 PD HANDWARA 08 01 01 01 26 SKPA UDHAMPUR 08 01 01 01 27 PTTI VIJAYPUR 07 01 01 01 28 SPS PTS KATHUA 07 01 01 01 29 STC TALWARA 06 01 01 01 30 STC SHEERI 06 01 01 01 31 PTS MANIGAM 06 01 01 01 32 SCRB JAMMU 05 01 01 01

Total 300 31 31 31


Page | 32


4 CORE APPLICATION SOFTWARE

CCTNS Core Application Software (CAS) would be built as a platform to provide the basic

framework to capture crime and criminal information, mainly at the Police Station, while

providing the States with the flexibility to build their State specific applications around it and in

addition to it.

On behalf of MHA, NCRB would provide to the State Jammu and Kashmir with a CCTNS

Core Application Software (CAS), which would be configured, customized, enhanced and

deployed by the State of Jammu and Kashmir. NCRB has engaged the services of professional

software development agency (SDA) to develop CAS that would be provided to the State. The

State level Systems Integrators (SI) would configure, customize and enhance CAS according to

the unique requirements of the State before deploying it.

The SDA is designing and developing CAS based on the functional requirements specified

by NCRB, and would also manage CAS. NCRB has selected SDA through a competitive bidding

process. The center through the SDA will be responsible for supporting the State Level System

Integrator(s) for the final implementation of the developed Core Application Software. States

also will have an option to develop and deploy the 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 tentatively by <March 2012>

This section provides the details of CAS (State) and CAS (Center) that will be developed by

the Software Development Agency (SDA) at the Center. The details provided in subsequent

sections will be read in conjunction with the RFP and the associated addendums issued by the

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

(Center) is provided in detail in the RFP issued by NCRB for the selection of the SDA. The CCTNS

application software can be conceptualized as comprising different services that fall under two

broad categories, CAS (Center) and CAS (State).

The Core Application Software for the State will provide the limited but core functionality

that is required at the Police Station. The remaining functionality will be developed by the State

Level System Integrator(s) on top of the Core Application Software.


Page | 33


The Core Application Software for the State will provide the limited but core functionality

that is required at the Police Station. The remaining functionality will be developed by the State

Level System Integrator(s) on top of the Core Application Software.

4.1 CAS (Center)

This component is an application at the Central (GOI/ NCRB) level that accepts/ gathers/

collects data from States and processes/ organizes the same. CAS (Centre) would be deployed

at NCRB. Relevant input, output and report formats and processing requirements would be

included as per the requirements of GOI/ GOI Agencies. The center’s SDA would be required to

design, develop, test, enhance and maintain CAS. The SDA would also be required to create all

required documentation including operations manuals, technical manuals and user manuals.

The SDA would be responsible for providing training content, user/ technical support, and

deployment support to NCRB for central deployment. CAS (Centre) would comprise the services

that would address the requirements of NCRB, and would be deployed and used at NCRB. CAS

(Centre) would enable NCRB to receive crime and criminals’ related data from States, 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 criminal’s data

repository of the nation.

4.2 CAS (State)

CAS would be provided to the State by NCRB, on behalf of MHA. The Systems Integrators

(SI) selected by the State would configure, customize, extend and deploy the State CAS as per

the unique requirements of the State. The SDA would be required to design, develop, test,

enhance and maintain CAS. The SDA would also be required to create all required

documentation including operations manuals, technical manuals and user manuals. The SDA

would be responsible for providing training content, user technical support, and deployment

support to the System Integrators at State Level for configuration and customization of the

application. CAS (State) would be a collection of services that would be deployed in the State. It

would focus primarily on functionality at Police Station with special emphasis on crime

investigation and criminals’ detection.


Page | 34


CAS (State) covers functionality that is central to the goals of CCTNS. The following are the

main function blocks that would comprise CAS (State):

• Registration • Investigation • Prosecution • Records Management • Search and Basic Reporting

The CAS application would be designed as per the requirements of the Police department

keeping in view the daily functionality of the Police Station. The application would be rich in

different functional modules with the easy access to the application. Each personal of the police

department would be provided with the unique user id and password with proper

authentication and security access. The modules of the CAS application are based on the roles

and responsibilities of the police department who will be accessing the application. Whenever

the police personal logs on the application with the valid User ID and Password, the application

will redirect the personal to the functions, attributes that are assigned to them, with daily

updated information pertaining to the police personal who is logging on to the application.

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.

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, event and role-driven system where actions on a case can be taken as required without rigid sequence/ workflows

• It will eliminate the need for duplicate and redundant entry of data, and the need for repetitive, manual report preparation – this freeing valuable time and resources for the performance of core police functions


Page | 35


• It will be intelligent and help police perform their roles by providing alerts, highlighting key action areas, etc.

• Ability to view and exchange information amongst Police Stations, between Police Stations and other Police formations and with external entities including citizens

• Reporting and data requirements of higher offices must be met at the State Data Centre/ SCRB level and not percolate to the police station level.

• Central facilitation and coordination; but primarily driven and owned by States/UTs where States/UTs can configure and customize the CAS for their unique requirements without the intervention of the central entity.


Page | 36


4.3 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. NCRB, on behalf of MHA, 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, 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/ UTs with the flexibility to build their State specific applications around it

and in addition to it. CAS (State) will be provided to States and UTs for deployment. Each State/

UT would customize the CAS according to their unique requirements and thereafter

commission the same. A bulk of the functionality would be added at State discretion and would

be added as extensions to the CAS (State) by the System Integrators (SI) chosen by the State.

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/ UTs and deployed in all

States/ UTs. The following sections provide details of the configuration and customization

requirements of CAS.

In order to achieve the key CCTNS goal of facilitating the availability of real time

information across police stations and between police stations and higher offices, CAS would be

built as a web application. However, given the connectivity challenges faced in a number of

police stations, especially rural police stations, the application must be built to work in police

stations with low and/ or unreliable connectivity.


Page | 37


4.4 Overview of Services for CAS (State)

1. 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.

2. Petition Management Service: The service shall enable the police personnel to register and process the different kinds of general service petitions and complaints.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

8. 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.

9. Police Email and Messaging Service: The service shall enable the police personnel to send/ receive official as well as personal correspondence.

10. Periodic Crime, and Law & Order Reports and Review Dashboard Service: The service shall enable the police personnel to view relevant reports and dashboards and to conduct periodic crime, and law & order reviews of the police station(s) under the officer’s jurisdiction.

11. Notification of Alerts, Important Events, Reminders and Activity Calendar or Tasks Service: The service shall capture/ generate the required alerts, important events, reminders, activity calendar and tasks.

12. 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.

13. State CAS Administration and Configuration Management Service: The service shall enable the individual State/UT to configure/ customize the application to suit to their unique requirements.

14. 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.


Page | 38


15. User Feedback Tracking and Resolution Service: The service shall enable the police personnel in logging the issues/defects occurred while using the system.

16. Activity Log Tracking and Audit Service: The service shall capture the audit trail resulting from execution of a business process or system function.

17. User Access and Authorization Management Service: The service shall enable the administrative user in setting the access privileges and will provide authentication and authorization functionality.

4.5 Overview of Services for CAS (Center)

1. 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, to organize it suitably to serve NCRB requirements.

2. 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.

3. 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.

4. Talaash Service: The service will enable the user to search for missing persons across a central national database.

5. 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, and convicts across the national database.

6. Registered Vehicle and Vehicle of Interest Service: The service will enable the user to search for registered vehicles and vehicles of interest such as, missing/ stolen vehicles, abandoned/ unclaimed vehicles, and vehicles involved in traffic incidents across the national database.

7. Publication Service: This functionality will help the NCRB to publish the periodic crime reviews to the NCRB portal.

8. 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.

9. 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.


Page | 39


4.6 Technology Stack for CAS (State)

CAS (State) will be developed in two distinct technology stacks by the Software

Development Agency at the Center. 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 successfully implement CCTNS solution for the Jammu & Kashmir Police meeting their

requirements as per this RFP.

The details of the Technology Stacks are provided as an Annexure to this RFP.

4.7 Role of Software Development 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 (Center) and CAS (State).

• 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 (Center): The SDA shall provide Application Management services to the CAS (State) and CAS

(Center). 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 Jammu & Kashmir Police.


Page | 40


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 and

UTs 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/ UTs; 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 turning, and performance tuning details that are required for the SI to

successfully commission the CAS (State) application in the State, integrate CAS (State)

with external agencies and third party solutions in the State and integrate CAS (State)

with CAS (Centre) to seamless transfer the required data to NCRB The implementation

toolkit shall also include the following:


Page | 41


• All completed and updated training and support material needed for customizing and deploying CAS.

• All completed and updated project documents including FRS, SRS, HLD, LLD and Test Plans.

• Relevant software assets (including configuration utilities/ tools, deployment scripts to State SIs to deploy CAS (State) in States).

• 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 State 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 State’s 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 will 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 System Integrator’s.

• 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 will enable the State SIs to migrate data from legacy/ paper based systems to the CAS databases. The data migration tool will be an extension of the one provided by the SDA. In case the Data Migration Tool developed by the SDA does not incorporate support for any State specific formats etc, the Data Migration Tool developed by the SI will have to support these.

• 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 State SIs. It is the responsibility of the SI to customize CAS (State) for development of local language interfaces. However the SDA shall assist the State SIs where ever required only to support the development of such interfaces. In addition, the SDA shall assist the State SIs in customizing CAS (State) to support local language interface and ensure the development of interface in local languages.


Page | 42


• National Service Delivery Gateway (NSDG)/ State Service Delivery Gateway (SSDG):

The System Integrator at the state level shall register as a Service Provider with the NSDG or SSDGs on behalf of the respective State Government and provide CCTNS based services. Initially if NSDG/ SSDG services are not available the CCTNS application shall access services through the existing broadband networks and SDA shall develop APIs for the required departments during CAS development to enable interoperability and interconnectivity for its eventual integration with NSDG/ SSDG. C-DAC as Gateway Service Provider of NSDG/ SSDG shall provide connectors/ adapters and guidelines for hosting services through NSDG/ SSDG after the SI registers as a Service Provider on behalf of the State/ UT Governments.

• 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.

• Configuration of CAS (State)

• Customization of CAS (State)

• Data Migration of CAS (State) related data from the legacy systems and/ or manual records to CAS (State)

• Infrastructure Sizing related to CAS (State)

• Commissioning and Deployment of CAS (State)

• Infrastructure Environment Performance Turning related to CAS (State)

• Maintenance of CAS (State)

• Integration of CAS (State) with external agency solutions

• 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.


Page | 43


5 SCOPE OF THE PROJECT

5.1 Geographical Scope

The scope of CCTNS in the State of Jammu & Kashmir spans across all the police stations

and all higher police Offices including Sub-Divisional Offices, District Headquarters, Range

Headquarters, Police Headquarter, State Crime Record Bureau, and other Police Units.

The CCTNS project involves connectivity of police units (linking police units at all levels within

the State). CCTNS also provides a citizens’ interface to provide Police services to citizens.

Indicative numbers of locations within the State to be covered for implementing CCTNS project

are as follows:

S. No. Police Units Indicative Number

1. Police stations 190

2. Sub Divisional Police Office/ ASP’s 67

3. District Police Offices (DPO’s) 25

4. Range PHQ 7

5. Zone ZPHQ 2

6. SCRB 1

7. Police Head Quarter’s 2

The above mentioned locations would be covered for implementing CCTNS project

including but not limiting to, Site Preparation, procurement, deployment and commissioning of

requisite Hardware, Network connectivity, deployment and commissioning of CAS (State) and

additional modules (with proper integration) as per the requirement of Jammu & Kashmir

Police, training &handholding support and further provisioning of the all the services

mentioned as per scope of work of this RFP. The following required details for these offices are

as follows:

• The indicative State map with all the districts depicting the location of all Police Units to be covered under the scope of CCTNS will be made available on request to the shortlisted bidder.


Page | 44


• Each Police Station comprises of one Station House Officer (SHO), One MHC, and One Officer on duty, One Investigation officer and one to two Computer Operators. A typical Jammu and Kashmir Police Station comprise of one room each for SHO, MHC, Duty Officer, Investigation Officer and Computer Operators.

CCTNS PHASE 1:

The first phase of the CCTNS or the Pilot phase would be rolled out in 4 districts of the

State of Jammu and Kashmir and all the higher offices of concerned districts as well as State

level offices such as Police Headquarters, State Crime Record Bureau. The pilot roll out would

include site preparation, complete deployment of CCTNS solution including all the application

modules of customized CAS, additionally developed modules, integration of application

modules to form a comprehensive CCNTS Suite for JK Police, Installation, Commissioning and

Operationalization of hardware, network connectivity, other infrastructure and associated

services (such as capacity building, handholding, etc.) and integration with CAS (Centre).

Successful Go-Live of Pilot phase would be based on the overall implementation of CCTNS in the

respective districts. The choice of the districts where the first phase would be rolled out is

provided below:

S. No Districts in Phase1 Number of Police Stations Rationale for Choosing

1 Jammu 25 Jammu is the winter capital of the

State J&K. It is larger in size and

covers both rural and urban areas.

2 Udhampur 10 Udhampur is the next major

District of Jammu Province. It has

plain as well as hilly areas.

3 Srinagar 25 Srinagar is the summer capital of

J&K State. It is larger in size and

covers both rural and urban areas.

4 Baramulla 14 Baramulla District is one of the

largest Rural Police districts in J&K.

It comprises a range It has good no.

of Police Stations and has both

plain and hilly areas.


Page | 45


CCTNS PHASE2:

During Phase-II of CCTNS, the remaining police stations, other Police Units across the

State that would be covered for Site preparation, complete deployment of CCTNS solution/

suite, installation, commissioning and Operationalization of hardware, network connectivity,

other infrastructure and associated services (such as capacity building, handholding, etc.) to

meet the overall objectives of CCTNS and the requirements of JK Police. External interfacing

and integration of CCTNS suite/ solution with external agencies would be performed in this

phase. Successful Go-Live of CCTNS implementation would be based on the overall

implementation of CCTNS in the State and henceforth, O&M phase would get started.

Operate & Maintain Phase: Operate and maintain phase would be initiated after the successful implementation of

CCTNS as per the scope of work mentioned in this RFP. In addition to activities relating to

operate and maintain of the comprehensive CCTNS solution, the phase would also include the

implementation of subsequent versions, upgrades, patches of CAS as released by NCRB and the

other initiatives of Jammu & Kashmir Police as part of MMP CCTNS.


Page | 46


5.2 Functional Scope

Police Officers at Police Station provides a variety of services in area of maintenance of

law and order, crime investigation, protection of state assets, VIP protection, traffic control,

prosecution and witness trial management, intelligence gathering and crime prevention, etc.

Police stations also serves as front-end of the entire police department in dealing with public

complaints and requests, and at the same time they occupy a pivotal place as the primary

information collecting agent for the other functions/ wings within the department.

5.2.1 Functional Modules

CCTNS functionality is designed to focus on delivering value to IOs, records room

staff and citizens within the broad crime investigation area. The CAS application should

provide the basic platform for capturing the crime and its prevention.

• The CAS application is embedded with different modules based on the designation and rank of the police men.

• The CAS application is specific with respect to police department. It will be easily accessible by IO, SHO, head constables, SP/ SSP etc, with their respective unique user id and passwords.

• The CAS application will be embedded with different functional modules like Registration, Investigation, Prosecution, Search, Help, and Reporting etc.

• The CAS application would be maintained by the administrator’s for full administration of the application.

• The non functional requirements would be the qualitative approach for user friendliness and the performance of the system.

• The CAS application would be designed as per the requirements of the police departments keeping in view the daily functionality of the police station. The application would be rich in different functional modules with the easy access to the application. Each personal of the police department would be provided with the unique user id and password with proper authentication and security access. The modules of the CAS application are based on the roles and responsibilities of the police department who will be accessing the application. Whenever the police personal logs on the application with the valid user and password, the application will redirect the personal to the functions, attributes that are assigned to them, with daily updated information pertaining to the police personal.

• The application will be embedded with the functional modules like registration of cases, investigation for the cases, prosecution, trails reporting etc. The application would be daily monitored and administrated, daily backups of the data would be taken so there is no loss of data. The application would be more user friendly with easy access with full security.


Page | 47


SI will be required to customize the CAS (State) as received from NCRB and shall also

be responsible for developing/ deploying other additional Modules meeting the functional

requirements mentioned in the Functional Requirement Specifications attached as an

Annexure to this RFP and other integration requirements.

The State of Jammu and Kashmir police department will be having 6 additional

modules to the CAS application. The additional modules need to be customized and

should be added to the CAS. The 6 additional State specific modules are as:

• GIS Module

• Terrorism Module

• Human Trafficking Module

• Antidrug smuggling and production Module

• Crime mapping Module

• Protection of wildlife Module

Geographic Information System (GIS) Module:

Geographic Information System captures, stores, analyzes, manages, and presents

data linked to location or geography. GIS applications are tools that allow users to create

interactive queries (user-created searches), analyze spatial information, edit data, maps

and present the results in user friendly manner.

GIS has been applied to varied domains from Natural Resource Management, Urban

Mapping, Transportation, Economic development, Public safety and Homeland security.

GIS is an essential tool for effective crime and law enforcement mapping as it provides a

way to visualize crime data, make informed decisions, and evaluate law enforcement

programs. GIS enables law enforcing agencies address tactical, strategic, or administrative

issues efficiently by integrating legacy law enforcement data with spatial information and

demographics for actionable intelligence and decision support.

It is extremely essential for the State Police dept in each of the Police Stations, DPO’s

and PHQ to be able to view the Crime Records, Traffic Records, Jail Records, Terrorism/

Militancy details in Spatial as well as Non Spatial format. A SHO must be able to view all

relevant data pertaining to his beat on a Map and if necessary cross check it with the data

from another Police Station. The mapping for a particular State can be done on different


Page | 48


scales for rural/ urban areas and also possibly keeping the density of population. These

maps will have to be customized to include the relevant details required to be

incorporated by the Police for specific Police Stations. As part of CCTNS it will require GIS

servers with the main server at the Police HQ, Servers at DPO’s and thin client

workstations at the respective Police Stations.

GIS once applied for CCTNS application can generate reports for the following

modules for JK Police and also for the modules that will be provided by CAS viz

Registration, Prosecution, and Investigation:-

• Crime analysis

• Registration, Prosecution and Investigation of Crime

• Terrorism/ Insurgency

• Restricted Area permit

• Drug Bootlegging/ Smuggling

• Protection of Wildlife, Flora & Fauna

Crime Mapping Module:

Since most of the crime has location reference, all types of incidence data like

accidents, Murders, Thefts, etc can be linked with data on offenders, suspects, police

jurisdiction, casualties, victims, etc. GIS analysis tools will help determine spatial patterns

and hotspots for various types of crimes. One of the main concerns for effective policing

is Resource availability and deployment. GIS based crime pattern analysis will help

effective resource deployment for crime analysis and prevention and also to track the

effectiveness of law enforcement programs. Thus it is important that JK Police must get an

additional module pertaining to Crime Mapping.

Features:

a. Pin Mapping: Allow users to dynamically create color coded pin maps based upon database attributes such as incident Date, Time, Location and Incident type.

b. Incident Count Mapping: Count the number of incidents in a particular area on the map. (E.g. mapping a town for theft cases for a particular month). Reports can be generated for all or for different categories like Robbery, murder, thefts, riot, attack etc.

c. Hot Spot Mapping: Provides both a simple and an advanced command for automatically extracting hot spots from a plot of incidents, helping police direct patrols where they are needed most.


Page | 49


d. Temporal Reporting: Allows users to create incident/ time-of-day histograms, giving them the latest information on trends and patterns in their locality. (E.g. Road accidents occurring “between” 0300 – 0600). Report of thefts/ robberies during the weekdays.

These functionalities can be achieved through Thematic mapping tool.

Thematic Mapping:

It allows creation of spatial patterns within data by creating themes. Users can

create, edit, or apply themes based on their requirements. Authorized users will also be

able to specify color schemes, symbols and manage, view and delete themes, create

simple themes or render maps based on unique values or class breaks. This tool will help

the police to spatially render crime information like Crime Count, Crime Frequency, etc

police station or Beat wise.

OGC thematic mapping tool will allow JK Police to perform thematic mapping of OGC

standard data formats. It also allows segregation of features available to the

administrators and the general users.

Benefits:

Crime mapping software will benefit the Police department in the following ways:-

a. Mapping crime can help police protect citizens more effectively. Simple maps that

display the locations where crimes or concentrations of crimes have occurred can be

used to help direct patrols to places they are most needed.

b. Maps offer crime analysts graphic representations of crime-related issues. An

understanding of where and why crimes occur can improve attempts to fight crime.

c. Policy makers in police departments might use more complex maps to observe trends

in criminal activity, and maps may prove invaluable in solving criminal cases.

d. GIS allows police personnel to plan effectively for emergency response, determine

mitigation priorities, analyze historical events, and predict future events.

e. GIS helps identify potential suspects to increase investigators suspect base when no

leads are evident.

f. GIS can also be used to get critical information to emergency responders upon

dispatch or while en route to an incident to assist in tactical planning and response.


Page | 50


Terrorism Module:

Jammu and Kashmir is one of the States with a long running problem of insurgency

and terrorism which surfaced in a big way from the early 90s. A number of hard line

groups like JKLF, HM, LASHKAR and others are still active in different parts of the State. In

addition J&K has boundaries with Pakistan and China. It is very well known that these

Countries have serious law and order problems and are affected by militancy as well as

terrorism.

Keeping the above factors in mind JK Police cannot afford to ignore the aspect of

terrorism/ militancy, wherein some of these groups have fair sized small pockets of

influence and have the potential to stir up trouble which cannot be ignored. Potential

terrorism related threats to J&K can be broadly classified as under:-

a. Influence of the major groups like JKLF, LASHKAR and their capability to trigger major

terror attacks.

b. Pakistan based militant groups who pass through LOC to J&K or take temporary

shelter in the State. In addition they have also been fermenting trouble and violence in

J&K.

c. Major effort by intelligence agencies of any of the neighboring countries in fermenting

trouble in J&K.

Terrorism/Militancy is an aspect which the Police of any State especially J&K can ill

afford to ignore. Therefore it is essential that JK Police must get an additional module

pertaining to Terrorism developed as part of the State CCTNS.

Features

The module will encompass the following features:-

a. Terrorist Details: Details of Killed, Arrested and Surrendered terrorist that operate in

the State. Personality profile of top leaders of each outfit.

b. Major Attacks: - Details of major strikes like Bomb blast, IED, Firing, Ambush, and

Suicide Bombers, details of casualties (Citizen/ Police personnel’s), damage to

property, loss of weapons, types of arms and ammunition recovered.


Page | 51


c. Terrorist Groups: - Details of major terrorist organizations. Their organizational profile,

known areas of influence, known modus operandi and tactics of each group, details of

supporters, over ground workers and front organizations, training bases (In India and

neighboring countries), assessed strength, holding of weapons and war like stores.

d. Intelligence: - Details of intelligence like Radio/ Mobile/ Internet/ Satellite/ Intercepts,

human intelligence inputs and code words.

e. Supporting forces: - Details of State Police nominated for counter terrorist operations

to include its organization, contact details, special equipment holding, State of

training, training infrastructure, details of past operations, and important case studies

with lessons learnt.

Benefits

The module will help in getting complete information about terrorist groups, their

outfits, training bases in India and neighboring country, Inter organizational linkages and

recovered arms and ammunition.

GIS Reports generated for:-

a. Location of major terrorist strikes in the State: - Will have incident details like Nearby

PS, Dist, date, time, type of attack - IED, firing, ambush etc. with details of casualties,

damage to property and loss of property due to terrorist actions.

b. Likely routes of infiltration.

c. Location based reports generated for killed, injured or arrested terrorists.

d. Record of wireless and telephonic intercepts of terrorist cadres or supporters.

e. Record of recoveries of weapons, explosives and war like stores/ material in counter

terrorist operations.

Protection of Wildlife, Flora & Fauna Module:

State Forest Department came into existence in the State of Jammu and Kashmir in

1881 when J. C. Mc. Donald was appointed the first ever Conservator of Forests of the

State. He started the process of consolidation and demarcation of forests. In 1923, H. L.

Wright was appointed as the first Chief Conservator of Forests. Scientific forest


Page | 52


management and reorganization of Forest Department took place during this period and

all forests of the State were brought under the purview of working plans.

Contribution:

Prime contribution of natural forests is towards maintenance of ecological balance,

conservation of bio-diversity, regulation of hydrological regime, promotion of soil and

water conservation, climate regulation, carbon sequestration and nutrient recycling.

Forests of the State are renowned the world over for their scenic charm and aesthetics.

These also contribute directly or indirectly for sustaining agriculture, horticulture, animal

and sheep husbandry, fisheries, water supply, power generation, industry, herbal

medicines and tourism.

Forest Area: Forest area of the State is 20,230 sq km which is about 10% of its geographical area.

If Ladakh region is excluded which does not have significant expanse of natural forests,

the proportion of natural forests in the State area increases to 47%. Per capita forests and

tree cover in the State is about 0.15 ha which almost double the national average of 0.07

ha. About 40% of the forest area is either dense or very dense and rest falls in the

category of open forest and 60% of the total forest area falls in Jammu region and balance

in Kashmir.

Timber and Firewood consumption:

Every year, about 50 % of timber and fuel wood requirements especially in rural

areas are met by supplies from forests. Total timber and fuel wood consumption in the

State are estimated at about 25 lakh cft and 400 lakh quintals respectively every year.

People's Participation:

Jammu and Kashmir State is giving highest priority for enrolling the participation of

village communities in protection and management of forests. All important activities of

Forest Department including execution of major State and Central Government schemes

are being implemented through a participatory approach centering on Joint Forest

management Committees (JFMCs).


Page | 53


Militancy Related Losses in Forest Sector:

79 forest officials including one Conservator of Forests lost their lives while on duty.

135 forest buildings were gutted. 47 lakh cft of timber worth Rs. 41 crores was gutted.

Interior forest areas suffered damages for being remained unattended.

Features:

Some of the functionalities proposed for this sub module are:

a. Details of Offenders/ Groups (Name, Sex, DOB, Address, Local address in J&K, Contact

phone number, Type of poaching, the potential clients, conduits etc)

b. Details of Victimized Species( Type, Geographical Area species present in, Victim in

which type of poaching)

c. Details of different types of endangered and protected wildlife species, flora and

fauna – their locations in different parts of the State.

d. The resources available to tackle these crimes, locations of the nearest Police Stations,

the type of equipment and training to name a few.

e. Historical records of such crimes for analysis and arriving at the potential threats.

Benefits:

a. Will keep track of illegal poaching agents involved

b. Will be able to track records of Victims.

c. Will have details/ history of poaching.

d. Generate reports for poaching (month/ year wise)

e. Preventive measures can be planned for such kind of activities

Human Trafficking Module:

Human Trafficking is a crime against humanity. It involves an act of recruiting,

transporting, transferring, harboring or receiving a person through a use of force, coercion

or other means, for the purpose of exploiting them. Every year, thousands of men,

women and children fall into the hands of traffickers, in their own countries and abroad.


Page | 54


Elements of human trafficking - On the basis of the definition given in the Trafficking

in Persons Protocol, it is evident that trafficking in persons has three constituent

elements:

• The Act (What is done) - Recruitment, transportation, transfer, harboring or receipt of persons

• The Means (How it is done) - Threat or use of force, coercion, abduction, fraud, deception, abuse of power or vulnerability, or giving payments or benefits to a person in control of the victim

• The Purpose (Why it is done) - For the purpose of exploitation, which includes exploiting the prostitution of others, sexual exploitation, forced labour, slavery or similar practices and the removal of organs.

In addition to the criminalization of trafficking, the Trafficking in Persons Protocol

requires criminalization also of:

• Attempts to commit a trafficking offence,

• Participation as an accomplice in such an offence,

• Organizing or directing others to commit trafficking.

Features:

Some of the functionalities proposed for this sub module are:

a. Details of Offenders/ Groups (Name, Sex, DOB, Address, Local address in J&K, Contact

phone number, Type of human trafficking involved)

b. Details of Victims( Name, Address, Nationality, address in J&K, Victim in which type of

human trafficking)

Benefits:

a. Will keep track of human trafficking illegal agents and foreigners involved

b. Will be able to track records of Victims (generally from which part of India/ abroad).

c. Will have details/ history of human trafficking.

d. Generate reports for human trafficking (month/ year wise)

e. Preventive measures can be planned for such kind of activities


Page | 55


Anti-Drug Smuggling and Production Module:

A number of Incidents of smuggling are reported every year in the State. While BSF

is responsible for border management, it is the responsibility of the State Police to

identify and catch known smugglers, confiscate illegal goods and initiate legal action

against these offenders. The module must be able to tabulate the details of the known

offenders, their activities, acts of smuggling; recoveries, etc present them in different

formats for viewing, analysis and sharing. The main functionalities proposed under this

sub module are:

• Type of smuggling activity and goods involved. • Know routes/ areas of activity. • Name, Sex, DOB, Address, ID etc of smugglers and accomplices. • Organizational profiling of smuggling gangs including key persons. • Inputs related to drugs and narcotics smuggling to be created as separate fields. • Details on apprehensions, recoveries, FIRs, ongoing court cases, sentencing, offenders out

on bail etc.

Multi-lingual Support:

While the CAS being provided by NCRB will support English and Hindi languages, it is

extremely essential for JK Police to have multilingual support in Urdu language. It is

proposed to develop the same at the State level as part of the CCTNS project. This feature

shall make it possible for FIRs and other reports typed in Urdu to be able to read in

English/ Hindi. This essential interface will make the CCTNS at the State level practical and

user friendly otherwise it will not find takers at the Police Station level who will tend to

avoid using the CCTNS application if the local language support is not there. It is also

proposed to train our staff on these applications before they actually start using it.


Page | 56


5.2.2 Solution and Technical Architecture

National Crime Record Bureau, Ministry of Home Affairs, Government of India is the

driving group behind the development of Core Application Software at the Central level,

therefore Solution and Technology Architecture have been defined at that very level.

CCTNS is deployed on a centralized architecture wherein application would be

deployed at the Data Center and various offices of Police Department will connect to the

system through BSNL leased line. The overall technology solution would be based upon

most relevant and suitable architecture standards including standards for Service

Oriented Architecture (SOA), XML services & necessary protocols for internet applications,

Data Center standards etc.

Technical architecture is provided as an Annexure to this RFP.


Page | 57


Deployment Architecture:

JK Police Data

Centre

Workflow

Engine

Multi-L

ingual Support Police Station SDPO District Offices ASP Offices Range Offices Zone Offices PHQ SCRB

BSNL NETWORK (Leased Line, VPNoBB and VSAT)

Security Layer

User L

ayer D

ata Layer

Application Layer

Service Delivery

Call for Service Status Update License Application Verification App Report & Record - RTI

Portal and Gateway Interface

Portal (Internet/ Intranet) Citizen Service Centers Mobile/ SMS Call Centre/ Helpdesk

Information System Master Information

Crime Information

Telephone No. Info

Case Information

Forensic Information

Foreigners Information

Financial Information

Complaint Information

HR Information

Criminal Information

Property Information

Vehicle Information

Inventory Information

Mission Person Info

CCTNS Core Application Modules Petition Mgmt

Complaint/ FIR Mgmt

PCR Call Interface

Registration

Investigation

Prosecution

Citizen/ Portal

Activity Log

Records & Query

Email

Crime/ Law & Order

Data Transfer &Mgmt

Notification & Alerts

CAS Admin &Config

User Feedback

User Help & Assistance

Monitoring

Traffic e-Challenging

Foreigners Reg.

GIS Module

Human Trafficking

Anti Drug Smuggling & Production Module

Organized Crime Module

Protection of Wildlife


Page | 58


The ‘User’ Layer: This layer forms the internal departmental users accessing the

applications over Internet or through the available network. Role based access would be

defined for the internal users for having accessibility to the respective application

modules, such as HRMS, which would be accessed by all the Police Officers but higher

Police authorities would essentially be accessing reporting modules which would help

them in decision making and monitoring the overall Policing at various levels. Integrated

database structure would ensure a one point stop search available to all the police units.

The ‘Data’ Layer: The overall solution would be based on a hybrid architecture

comprising of centrally located databases at Police Data Centre as central repository and

locally deployed databases at other police units (mainly Police Stations). All the proposed

applications would be able to function in an offline mode and on availability of

connectivity, data would automatically replicate with the central repository in Police Data

Centre. This approach would cater to the functionalities of all the key processes and

functions performed at Police Station level and would also allow the users to have an

access to the central repository for comprehensive information as and when required. The

Police Data Centre would securely host the aforementioned information databases on

servers specifically for Police Department. It is recommended that the Data Center (DC)

should be the preferred to Third Party Data Centre option mainly on account of the

following:

• The specialized skills needed to manage a data-centre (such as security access management through multiple delivery channels, data encryption, storage management, database administration, etc.) are already being provided for at the DC. To replicate, maintain and continuously upgrade these skills at a Department level would be extremely difficult, time consuming and waste of effort and resources.

• Easier to integrate with overall e-Governance initiatives in the State (i.e. integration and interoperability with applications and databases being developed and maintained by other departments at the DC) in the future, if and when required

• Cost effective option as the IT infrastructure investments would be required only for enhancing the capacity of DC (e.g. additional servers, Storage capacity, upgraded connectivity, etc.).

Networking: The overall networking solution would be based on a combination of

Leased line, VPN over Broadband and VSAT ensuring optimum uptime at all the desired

locations. The option of networking and connectivity with BSNL is under discussion and

will be finalized by MHA.


Page | 59


The ‘Application’ Layer represents three categories of modules, i.e. modules

proposed by the CAS (State), existing modules of the State department which would

either be integrated as it is or may require certain customization to integrate with CAS

and lastly, the additional modules proposed by the department which would be either

developed afresh or would be deployed after customizing a commercially available

software. These modules will communicate with each other by sharing of data with one

another, or by coordinating an activity between two or more services.

Users can easily access solution components (CCTNS modules) having a single sign-

on facility either through internet. All the modules would be supported with Business

Intelligence/ Data Mining tools coupled with Bi-lingual support, e-payment gateway and

workflow engine.

The ‘Service Delivery’ Layer represents the different modes/ media of service

delivery, which would be used for availing/ accessing the services of Police. Services would

be primarily provided through Dial 100, over internet, Mobile, SMS and through Khidmat

centers.


Page | 60


5.2.3 State Specific Requirements

Selected System Integrator would be completely responsible for successful

implementation of end to end CCTNS solution in Jammu & Kashmir State as per the

requirement of JK Police and on the lines of NCRB, MHA guidelines. It is imperative for

System Integrator to understand two basic aspects of this project, i.e. CCTNS Solution as

provided by Centre and secondly the specific requirements of the J&K State, for the

success of this project.

An indicative list of specific requirements is detailed below; however, final specific

requirements would emerge from the Detailed System Study to be conducted by System

Integrator.

Application Specific Requirements: The functional requirement specifications have been defined in the attached

Annexure. However, JK Police have also customized some of these functional

requirements to meet the desired objectives of the department through this project.

SI would be required to customize the CAS (State) which may include, but not

limiting to modifications in User Interface, addition/ modification/ renaming of the Tabs/

Sub-tabs as per JK Police requirements, etc. Final navigation scheme of CAS (State) across

all the screens and modules shall have to get approved by JK Police.

Key Configuration Requirements:

Multi-lingual Support: System Integrator would be required to configure the

complete CCTNS with multilingual support (English, Hindi and Urdu) for User Interface,

Font, Data Entry, Search, Report Generation and all types of data transactions, etc.

Data Entry: System Integrator would be required to configure the CCTNS solution in

such a manner that it ensures complete data entry in the system by Police officials in such

a way that system should generate reports on data entry Police Unit wise, IO wise, by

taking a cutoff date and generate the desired reports. In addition to this Integrated

Investigation Forms would require the mandatory entry of the data for generation of

Police Report to be submitted in the Court. Though it has been proposed that the CAS

(State), to be provided by NCRB should be equipped with Dictionary of Common Names of

Persons, Places for proper addressing, but in case it does not come equipped with the


Page | 61


same, selected SI would be required to prepare such a dictionary of names of persons and

places before initiating the exercise of Data Digitization and Data Migration. The idea is to

ensure lesser mistakes during data entry in the names, addresses.

Record Management: Automation of all the Police Station registers and system

generated reports supported by Business Intelligence &Data Mining tools to empower

Police Officers is what CCTNS can offer.SI would be required configure the CCTNS

application with Business Intelligence & Data Mining support for Crime Analysis and Crime

Pattern analysis as per the requirements of the department.

Case information recording: Investigating Officer has always been over loaded with

case investigations, and therefore consumes a good amount of time to re-align his

investigations details at the day end. Hence we foresee a need for storing every case in

CCTNS application where IO may store all the case related data, such as Case Diaries,

Photographs, scanned documents, audio/ visual recordings, miscellaneous

correspondence, etc. at one location for his ready reckoning and anywhere retrieval. SI

would be required configure the CCTNS application with this kind of concept for the

successful implementation.

Local Database: The local databases should be maintained at each Police Station to

record and register complaints, during no connectivity or in case of network failure. The

Systems should be able perform in Offline mode and all the activities performed should be

recorded. As the offline mode switches back to the online mode, data recorded in local

database at Police Station would synchronize with central data repositories and

henceforth, both the repositories local and central would be in sync.

Additional Application development:

The SI would be required to develop, implement, and integrate the additional

modules with the CAS (State). The modules are:

• GIS Module

• Terrorism Module

• Human Trafficking Module

• Antidrug smuggling and production Module

• Crime mapping Module


Page | 62


• Protection of wildlife Module

Although the detailed functional requirement specification of the above mentioned

modules would emerge out from the Detailed System Study to be conducted by System

Integrator. SI would follow all the standard norms of Software Engineering to document

(the functional specification and design documents), design, implement and commission

the application and finally maintaining them. Since all the application modules would get

integrated with the CCTNS Core Application Software and all the integrated application

modules would be treated as one solution, therefore testing and maintenance will have to

be conducted for entire solution as per the project plan.


Page | 63


5.2.4 Integration and Interfacing requirements:

In addition to the Configuration, Customization and Extension (New Modules) of CAS

(State), it is necessary for the entire solution to get integrated with the CAS (Center) and

External Agencies. System Integrator will be required to integrate the complete set of

solution with CAS (Center) and create interfaces for further integration with External

Agencies (in phase II of project implementation). The detailed integration and interfacing

model would emerge out of the detailed study of System Integrator.

The interfaces to be developed within CAS (State) should provide proper information

and data sharing with external agencies, but not limiting to Jails, Courts, Hospitals, Mobile

Service Providers, etc. External Interfacing shall also be provided State Common Service

Centre (CSC), e-forms applications (of State portals and Service Delivery Gateway), State

Universities, Cyber Cafes of the State, other external government departments etc. to

facilitate electronic exchange of information. System Integrator would be required to

study the interfacing requirements with CAS (Centre), external agencies and other State

departments for seamless integration and information exchange, as part of Detailed

System Study.

It is necessary for the System Integrator to conduct a detailed study for deriving the

Integration and Interfacing requirements of CAS (State). At the outset, System Integrator

would also be required to study the National Level initiatives or projects for interfacing

and integration requirements with CAS (State), such as but not limiting to, initiatives by

Department of IT, GoI, Ministry of External Affairs, GoI, AFIS project, Age progression,

Mobile Number Portability, etc.

Indicative types of data/ information exchange with external agency, with which

interfacing of CCTNS solution will be required are as follows, further more integration

requirements are mentioned in the Functional Requirement Specification attached as

Annexure to this RFP document.


Page | 64


S.No Name of Agency Data/ Information Remarks 1 State Transport Authority • Data of Driving License (as

required by Motor Vehicle Act) • Data of Vehicle Registration

Certificate (as required by Motor Vehicle Act)

• Data of Stolen Vehicle from JK Police

SI will be required to develop functionality by customizing CAS (State) to import data from State Transport Authority and use the same with various modules of CAS

2 State Jails • Bail order details • Data of prisoners/ jail inmates • Data regarding movement of

prisoner/ under trial/ convict. • Data regarding discharge of

under-trial/ convict who are accused in cases figuring on the list of monitored cases.

SI will be required to develop functionality by customizing CAS (State) to capture such data from State Jails/ Prisons and use the same with various modules of CAS

3 State Courts • Charge Sheet acknowledgement • Data of Case Trials, etc. • Data of summons/ warrants

issued by court, next date of hearing, status of accused(whether on bail or in custody)

• Court permissions, judgments, sentences, etc. against cases.

SI will be required to develop functionality by customizing CAS (State) to capture such data from State Courts and use the same with various modules of CAS

4 State Government Hospitals

• Medico Legal Reports (MLRs) • Postmortem reports (PMRs) • Other forms/ requests made by

Police for expert opinions.

SI will be required to develop functionality by customizing CAS (State) to capture such data from State Govt. Hospitals and use the same with various modules of CAS

5 Mobile Service Providers • All the Data associated with mobile subscribers.

• Call detail records of individual subscribers.

SI will be required to develop functionality by customizing CAS (State) to capture such data from Mobile Service providers and use the same with various modules of CAS

6 Service Verification • Character Antecedent Certificate for employment

• Verification request for rented persons

• Verification request of drivers/ home servant

• Verification request of private

SI will be required to develop functionality by customizing CAS (State) to capture such data


Page | 65


security personnel • NOC for Permanent Resident

Certificate • NOC for theft vehicle to claim

insurance 7 Passport Verification • Seamless integration with Police

systems for better citizen service delivery and improved law enforcement

• Timely Police verification and online submission

• Online status tracking of police verification of Passport

SI will be required to develop functionality by customizing CAS (State) to capture such data


Page | 66


6 SCOPE OF SERVICE

The scope of the “bundled services” to be offered by the SI includes the following:

• Project planning and management. • System study and design • Core Application Software (State) Deployment as provided by NCRB, MHA. • Procurement, deployment and Commissioning of IT infrastructure at the Police Data Center

and disaster Recovery Center including the necessary hardware, software and other networking components Data migration and Digitization of Historical Data.

• Customization of CAS as per requirement of State, including but not limiting to its configuration and Extension (New Modules) of CAS (State)

• Integration of CAS (State) with CAS (Centre) and External Agencies and their external applications

• Development and deployment of JK Police specific Application modules. • Site preparation at the Client site locations (Police Stations, Range offices, Zones, SCRB,

SDPOs, District HQ, and State HQ • Procurement, Deployment and Commissioning of IT Infrastructure at the Police Unit

locations (Police Stations, Range offices, SCRB, SDPOs, District HQ, and State HQ). • Network connectivity with Creation of LAN at Police locations • Infrastructure at the District Training Centers including computers, networking

components, projectors and UPS. • Site preparation at the Client site locations (police stations, circle offices, Range offices,

Zones, SCRB, SDPOs, District HQ and State HQ), Training Centers and Data Center. • IT Infrastructure at the Client site locations (police stations, circle offices, Range offices,

Zones, SCRB, SDPOs, District HQ and State HQ). • Network connectivity. • IT infrastructure at the Data Center and Disaster Recovery Center including the necessary

hardware, software and other networking components. • Data migration and Digitization of Historical Data. • Migration of CIPA and CCIS Police Stations / Higher Offices to CCTNS. • Change Management. • Capacity building. • Handholding Support. • Support to 3rd party acceptance testing, audit and certification.

In implementing the above, the SI shall strictly adhere to the standards set by the MHA,

NCRB, and State of Jammu and Kashmir.

The project will be managed by State IGP Crime of Jammu and Kashmir police department.

At all points in the execution of the project, key senior resources including the project manager

must be based at State IGP Crime’s office in Jammu and Kashmir.


Page | 67


6.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,

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:

• Create an organized set of activities for the project • Effective Coordination with various stakeholders including the police department, SPMC,

SPMU, CPMU, NCRB and SDA. • Establish and measure resource assignments and responsibilities • Construct a project plan schedule including milestones • Measure project deadlines, budget figures, and performance objectives • Communicate the project plan to stakeholders with meaningful reports • Provide facility for detecting problems and inconsistencies in the plan. • During the project implementation the SI shall report to the State IGP Crime of Jammu and

Kashmir, on following items:

• Results accomplished during the period; • Cumulative deviations to date from schedule of progress on milestones as specified in

this RFP read 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;

• Progress reports on a fortnightly basis • Interventions which the SI expects to be made by the State IGP Crime and/ or actions to be

taken by the State IGP Crime before the next reporting period; • Project quality assurance reports • Change control mechanism. • As part of the project management activities, the SI shall also undertake:

• Issue Management to identify and track the issues that need attention and resolution from the STATE.

• Scope Management to manage the scope and changes through a formal management and approval process.

• Risk Management to identify and manage the risks that can hinder the project progress.


Page | 68


The Project plan prepared by the SI at the initial stage of the project would be reviewed

by the Governance Structure in the State and approved by the Apex/ Empowered Committee

on the advice of the State Mission Team and SPMC/ SPMU.

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 JK police department or

appointed representative.

Requirements Traceability Matrix The SI would ensure that developed solution is fully compliant with the requirements and

specifications provided in the RFP such as functional, non-functional and technical

requirements. For ensuring this, the SI shall prepare a Requirements Traceability Matrix on the

basis of Functional Requirements Specifications (FRS), Non Functional Requirements

Specification, and Technical Requirements provided by State (updated, expanded and fine-

tuned by the SI as necessary) and the System Requirements Specifications (SRS) prepared by

the SI. This matrix would keep track of the requirements and trace their compliance through

different stages of the project including software design, coding, unit testing and acceptance

testing. The Requirements Traceability Matrix would be a live document throughout the

project, with the SI team updating the matrix at every stage to reflect the meeting of each

specification at every stage.

Through the duration of the project, the State Mission Team will periodically review the

Traceability Matrix. State Governance Structure would provide the final approval on the advice

of the State Mission Team and SPMU once they are satisfied that all requirements are met.

Project Documentation The SI shall create and maintain all project documents that would be passed on to State as

deliverables as per the agreed project timelines. The documents created by the SI will be

reviewed and approved by the Governance Structure Setup in the State. State Mission Team

would also approve any changes required to these documents during the course of the project.

State will finally sign-off on the documents on the recommendation of State Mission Team /

SPMU.


Page | 69


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 modeling documents • Logical and physical database design • Data dictionary and data definitions • Application component design including component deployment views, control flows,

etc. • Documents (including but not limited to)

• Application flows and logic including pseudo code • GUI design (screen design, navigation, etc.)

• All Test Plans • Requirements Traceability Matrix • Change Management and Capacity Building Plans • SLA and Performance Monitoring Plan • Training and Knowledge Transfer Plans • Issue Logs

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 IGP Crime on request. All project documentation shall conform to the

highest standards of software engineering documentation.

Procure, Commission and maintain Project Management, Configuration Management and

Issue Tracker Tools at State HQ/ SCRB.

Project Management Tool: The SI shall keep the project plan and all related artifacts up-

to-date during the course of the project. In order to help with the project management, the SI

shall use a suitable standard, proven off-the-shelf project management tool (preferably with

unrestricted redistribution licenses). The SI shall install the project management software at

State’s premises right at the beginning of the project. The tool shall provide the dashboard view

of the progress on project milestones by the IGP Crime and other Supervisory Officers of

CCTNS.


Page | 70


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 artifacts), the SI shall use a

suitable standard, proven off-the-shelf configuration management tool (preferably with

unrestricted redistribution licenses). The SI shall install the configuration management software

at State’s premises right at the beginning of the project.

Issue Tracker: The SI shall employ a suitable and proven tool for tracking issues

(preferably with unrestricted redistribution licenses) through the execution of the project. The

SI shall install the Issue Tracking System at State’s premises to enable State’s users to access

and use the same.

The SI shall procure and commission the required infrastructure (software, servers) for

Project Management Tool, Configuration Management Tool and Issue Tracker tool and

maintain the same through the duration of the project. These tools along with the servers on

which they are deployed will become property of the State and will be used by State even

beyond the contract period.

The SI would setup an online repository on PMIS/ Configuration Management Tool for

providing centralized access to all project documents including manuals and other materials.

The online repository would be maintained by the SI through the engagement period. The SI

should ensure that the repository is built on appropriate security features such as role- and

necessity-based access to documents.


Page | 71


6.2 System Study, Design, Application Development and Integration

The System Integrator will carry out a detailed systems study to refine the Functional

Requirements Specifications provided as Annexure to this RFP and formulate the System

Requirements Specifications (SRS) incorporating the functional specifications and standards

provided by the NCRB and the State-specific requirements. The System Integrator shall also

study CAS-State and CAS-Center that is being developed at NCRB and already running

application in the State of Jammu and Kashmir for the system study phase. The System

Integrator shall study should the different integration points of CAS State with external

agencies as per the requirements of the State of Jammu and Kashmir. The preparation of SRS

prepared by System Integrator shall take into account the BPR recommendations suggested by

the NCRB/ State. The System Integrator should also prepare a detailed document on the

implementation of CAS (State) with respect to configuration, customization and extension as

per the requirement of 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 artifacts/ documents provided by NCRB/ State. As part of the System Study, the

selected System Integrator shall be responsible to:

• Prepare a comprehensive System Study document by studying the legislation, business processes and organization design of the Department of Police, Government of Jammu & Kashmir. The Project Implementation and Monitoring (PIM) report prepared by State Project Management Consultant (SPMC) along with the supporting Annexure(s) will be made available to the successful bidder.

• The selected Bidder shall perform the detailed assessment of the functional requirements and MIS requirements listed in Annexure of Volume I of this RFP and prepare a new FRS report, as part of the System Study document incorporating list of additional features that would result in further improvement in the overall application performance for consideration of the Department.

• Preparation of the Solution Design.

• Solution Development and/ Customization and Configuration and Extension as required.

• Development of reports.

• Formulation of test plans and test cases for additional functionalities and different integrations with external agencies including CAS (Center).

• Change/ Reference document include all the changes or deviations from the base version of the CAS (State).

• Testing of the configured solution (CAS) and additional functionalities.

• Change Management and Capacity Building Plans


Page | 72


• SLA and Performance Monitoring Plan

• Training and Knowledge Transfer Plans

• 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 JK Police or its nominated

representatives 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 IGP Crime on request. All project documentation shall conform to the highest

standards of software engineering documentation.


Page | 73


6.2.1 Preparation of System and Software Requirements Specifications (SyRS and SRS) The selected SI shall be responsible for preparing and submitting detailed

requirement specification documents as per IEEE or equivalent standards which meets all

the Business, Functional and Technical requirements of the police department. The SI

would prepare the Requirement Specification document reviewed and approved by the JK

Police or its nominated agencies. The JK Police will sign off on the requirement

specification documents on the advice of State Mission Team or nominated

representatives of JK Police.

Note: The vendor is required to update the FRS/ SRS as and when any enhancements/ modifications

are made to CAS (State) application till the currency of project.

6.2.2 Preparation of CAS Implementation document A comprehensive CAS implementation and deployment document shall be prepared

by the System integrator in consultation with JK Police to prepare for the ultimate change-

over day from existing CIPA/ CCIS based system to the new CCTNS system. The

implementation document would also comprise of Trainings to be provided to the Police

officials at different stages of the project, procurement, deployment and commissioning

of required hardware and software, provisioning of network connectivity, site

preparation, etc. Further, SI will also prepare detailed Work Plan and estimate the

timelines and resources required for Configuration, Customization, Extension, Integration,

and Commissioning of the CAS (State) software as per State requirements. All the

documents prepared by the system Integrator will seek approvals from the JK police

department or appointed agencies.


Page | 74


6.2.3 Preparation of Solution Design Detailed Design document would include:

• Technical Architecture Document (Application, Network, and Security)

• (High Level and Low Level Design

• Database architecture, including defining data structure, data dictionary as per standards laid down by Government of India/ Government of J&K (In case such standards are not defined, the same will have to be approved by Govt. of J&K)

Technical Architecture A centralized architecture (servers and processing at single and central location) has

been proposed for the J&K CCTNS project. All requests from internal and external users

will be sent to the systems, located in a central place for processing. All users will access

the application through local or remote terminals using a browser (through internet for

external users and through intranet or VPN for internal Departmental users).

Bidders should clearly understand that the desire of the department is not to create

a mere IT Solution but an information infrastructure that will expand, integrate and

enhance the functional needs of the department, citizens and other stakeholders. It is in

this spirit that the core design and functional requirements are elaborated below:

a) Service Fulfillment: The objective of the System is to deliver the service from initiation

to completion through electronic channels, as far as possible. Processes have been

reengineered so that a stakeholder is able to access the system, perform the required

tasks which may involve single or multiple back-end application interactions and fulfill

the service requests through the complete solution.

b) Single-Sign On: The Solution should enable single-sign-on so that any user once

authenticated and authorized by system is not required to be re-authorized for

completing any of the services in the same session. For employees of the JK Police, the

browser based application accessed on the intranet, through single-sign-on

mechanism, will provide access to all the core services (based on their roles and

responsibilities), Help module, Basic and advanced Reporting etc. Similarly, for

external users (Citizens, Hotels, Cyber Cafes, Hospitals, Jails, Transport Department

etc), based on their profile and registration, the system shall enable single-sign on

facility to apply for various services, make payments, submit queries/ complaints and

check status of their applications.


Page | 75


c) Support for PKI based Authentication and Authorization: The solution shall support

PKI based Authentication and Authorization, in accordance with IT Act 2000, using the

Digital Certificates issued by the Registration Authorities (RA). In particular, PKI based

authentication and authorization shall be implemented by the selected Bidder for

officials/ employees involved in processing key G2B and G2C services, including

issuance of notices, receipts and approvals.

To ensure integrity and confidentiality, the data collected (both online and

offline) at the police location should be digitally signed and encrypted before it is sent

from one location to other/ central data center. Hardware Security module should be

integrated with the applications in Data Centre in high availability mode and should be

able to endure the security and integrity of the signing key, key management and

multifactor authentication to access the key and most significantly it should be able to

enhance the performance of the complete system by offloading the complete

cryptography process to a dedicated appliance. All data interchanged among various

police offices and between the users of an application interface, Core application,

Police agencies and CCTNS databases should be digitally signed and encrypted using

the PKI infrastructure.

d) Interoperability Standards: Keeping in view the evolving needs of interoperability,

especially the possibility that the solution would become the focal point of delivery of

services, and may also involve cross-functionality with the e-Government projects of

other departments/ businesses in future, the solution should be built on Open

Standards.

e) Scalability: One of the fundamental requirements of the proposed solution is its

scalability. The architecture should be proven to be scalable (cater to increasing load

of internal and external users and their transactions) and capable of delivering high

performance for at-least five years from the date of deployment. In this context, it is

required that the application and deployment architecture should provide for Scale-

Up and Scale out on the Application and Web Servers, Database Servers and all other

solution components.

f) Security: The Systems implemented for Project should be highly secure, considering

that it is intended to handle sensitive data relating to Crime and Criminals. The

overarching security considerations are described below. The security services used to


Page | 76


protect the Solution shall include: Identification, Authentication, Access Control,

Administration and Audit and support for industry standard protocols.

The solution shall support advanced user authentication mechanisms including

Digital Certificates and biometric authentication. Security design should provide for a well-

designed identity management system, security of physical and digital assets, data and

network security, backup and recovery and disaster recovery system. The solution should

provide for maintaining an audit trail of all the transactions without impacting the overall

performance of the system. The overarching requirement is the need to comply with ISO

27001 standards of security.

The detailed quality of service requirements is given in the Service Levels attached as an Annexure

to the RFP.

Application Architecture It has been proposed that the Applications designed and developed for the

department must follow some best practice and industry standards. In order to achieve

the high level of stability and robustness of the application, the system development life

cycle must be carried out using the industry standard best practices and adopting the

security constraints for access and control rights. The various modules/ application should

have a common Exception Manager to handle any kind of exception arising due to

internal/ external factors. This will help ease of application maintenance and

enhancements. Similarly the modules/ application are to be supported by the Session and

Transaction Manager for the completeness of the request and response of the client

request. The system should have a module exclusively to record the activities/ create the

log of activities happening within the system/ application to avoid any kind of

irregularities within the system by any User/ Application.

Proposed Application Architecture The 3-tier architecture (also referred to as multi-tier or N-tier architecture) has been

proposed for the Application Solution.

The entire processing should take place in three layers:

• Front-end software (client tier) -responsible for the presentation of information. • Middleware (application server tier) - responsible for all the business rules • Server Software (database server tier) - responsible for the manipulation and storage

of data. Data ranges from text to numerical, to video on demand.


Page | 77


High Level Design (HLD) Once the SyRS and SRS are approved, the SI would complete the High Level

Designing and all HLD documents of all the functionalities, integration with CAS Center

and external agencies. The SI would prepare the HLD and have it reviewed and approved

by the JK Police or nominated representatives/ agencies. The JK Police will sign off on the

HLD documents based on the advice of State Mission Team/ SPMC or nominated

representatives/ agencies.

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 JK Police or its nominated representatives/ agencies. JK

Police will sign off on the LLD documents based on the advice of State Mission Team/

SPMC or JK Police nominated representatives/ agencies.


Page | 78


6.2.4 Configuration, Customization, Extension (New modules) of CAS (State) and Integration with CAS (Center) and External agencies CAS would cover those police functions that are central to the goals of the CCTNS

project and are common across States/ UTs. This includes core functions in the areas of

Complaints/ Case Management, Police Station Efficiency and Analysis & Reporting. The

CAS is being developed at Centre is a product-like application that could be centrally

managed and at the same time customized to meet the unique requirements of the

States/ UTs and deployed in all States/ UTs. SI would be responsible for configuring,

customizing and developing additional modules based on CAS Implementation document

over as per the Functional Requirement of the State.

CAS (State) contains functionality that is common across all States/ UTs. CAS (State)

would be configured, customized, extended by the SI based on the unique requirements

of the State and deployed at the State Data Centre. In order to ensure consistency

between States/ UTs and facilitate the exchange of crime and criminals related

information between States/ UTs and the Centre and between States/ UTs, NCRB would

develop, own and maintain the CAS.

Briefly describing the tasks to be carried out by SI as part of CAS (State)

configuration, customization, extension and integration basis requirements of the State:

1) Deployment of Core Application Software (State) as provide by NCRB, MHA 2) Conduct Conference Room Pilot 3) Customization of CAS as per requirement of State, including but not limiting to its

configuration and Extension (New Modules) of CAS (State) 4) Development and deployment of JK Police specific Application modules 5) Integration of CAS (State) with CAS (Centre) and External Agencies and their external

applications 6) Development of reports 7) Formulation of test plans and test cases for additional functionalities and different

integrations with external agencies including CAS (Center) 8) Change/ Reference document 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 shall also be incorporated in the SRS and shall form the scope of work for the SI

10) Provision of Local laws and Acts (RPC).


Page | 79


Deployment of CAS (State)

As the initial step, the selected SI will be responsible for deployment of CAS (State)

application as such provided by NCRB, MHA in the development environment for further

studying the exact requirements of the State in consultation with JK Police or its

nominated agencies and further customizing the deployed CAS to meet the requirements

of JK Police. Such a deployment exercise will be completely different from the deployment

exercise to be carried out by the SI at the time of Pilot Roll-out and Go-Live in Jammu and

Kashmir; however deployment at these stages would mean deployment of customized

CAS (State) for the application to be accessed by respective concerned Police Units and

other stakeholders.

As part of deployment of CAS application, 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.

Creation of Test Plans The System Integrator will prepare SRS document and once the SRS is approved and

design is started, 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 by System integrator in collaboration with domain experts identified at State

headquarters. The Test Plans also include planning for the testing any integration with

third party COTS solutions, CAS (Center), any external agencies. The Test Plans should also

specify any assistance required from State and should be followed upon by the SI. The SI

should have the Test Plans reviewed and approved by the State Mission Team/ SPMU. The

State headquarters will sign off on the test plans on the advice of State Mission Team/

SPMU.


Page | 80


High Level Design (HLD) The System Integrator shall complete the HLD, once the SRS is approved. All the HLD

documents of additional functionalities, integration with CAS Center and external

agencies upon the approved SRS. The SI would prepare the HLD and have it reviewed and

approved by the State mission team/ SPMU. The State will sign off on the HLD documents

on the advice of State Mission Team/ SPMU.

Detailed (Low Level) Design (LLD) The LLD would interpret the approved HLD to help application development and

would include detailed service descriptions and specifications, application logic (including

“pseudo code”) and UI design (screen design and navigation). The preparation of test

cases will also be completed during this stage. The SI would have the design documents

reviewed and approved by the State Mission Team/ SPMU. IGP Crime of Jammu and

Kashmir will sign off on the LLD documents upon the advice of State Mission Team/

SPMU.

Application Development and Unit Testing The System Integrator will start developing 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 CAS and additional functionalities/ modules developed as

part of CAS. The SI would also implement the changes proposed in the Change/ Reference

document to Core Application Software and carry out a thorough regression testing

including running some of the previously executed scripts for the functionality from the

traceability matrix provided by NCRB/ State. The SI shall also develop a Data Migration

Utility/ application for the additional functionalities with all the formats and tools to

load the data into the State databases. This will migrate data from legacy/ paper based

systems of the new modules to the CAS databases. The user acceptance testing and fine-

tuning of the application would be at State Headquarters premises. Also, the key senior

resources would continue to be based onsite at State Headquarter premises.


Page | 81


Configuration of CAS (State) The SI shall configure CAS (State) to the requirements of the State of Jammu and

Kashmir 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 State Headquarters The SI shall procure, setup and maintain the required software and the

infrastructure for systems testing, functional testing and User Acceptance Testing; and

training activities within State Headquarter premises; and for any other activities that may

be carried out of State Headquarter premises such as issue management (Issue Tracker),

document repository (configuration management tool), etc.

Regression, Integration, System and Functional Testing After successful unit testing of all components, the SI would conduct full-fledged

integration testing, system testing and functional testing in accordance with the approved

Test Plans for the configured/ customized CAS (State), additional functionalities and

also integration with CAS (Center) and external agencies. This would include exhaustive

testing including functional testing, performance testing (including load and stress),

scalability testing and security testing. A thorough regression testing should be conducted

for those functionalities identified in Change/ Reference document to provide a general

assurance that no additional errors have cropped up in the process of addressing the

customizations and/ or Extensions. Customized CAS (State) Integrations with CAS (Center)

and with any external agencies should be thoroughly tested. Making all necessary

arrangements for testing including the preparation of test data, scripts if necessary and

setup of test environment (across multiple platforms) shall be the responsibility of the SI.

The SI along with State Mission Team/ SPMU should take the responsibility in

coordinating with NCRB and other external agencies for a smooth integration.


Page | 82


Test Reports The SI shall create test reports from testing activities and submit to State Mission

Team/ SPMU for validation

Test Data Preparation The SI shall prepare the required test data and get it vetted by State Mission Team/

SPMU. The test data shall be comprehensive and address all scenarios identified in the

test cases. The SI should also prepare the test data for all required integrations including

CAS (Center) and external agencies.

User Acceptance Testing (UAT) Test Plans for UAT would be prepared by the SI in collaboration with the State

Mission Team/ SPMU domain experts. The SI will plan all aspects of UAT (including the

preparation of test data) and obtain required assistance from State Headquarters to

ensure its success. State Mission Team/ SPMU will assemble representatives from

different user groups based on inputs from the SI and would facilitate UAT. The SI would

make the necessary changes to the application to ensure that CAS successfully goes

through UAT. It’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.


Page | 83


6.3 Infrastructure at the District Training Centers

The SI is expected to setup the district training centers at each District Headquarters. The

premises will be provided by the Jammu and Kashmir police department and all infrastructures

such as projectors, computers, networking components, UPS required to run the training lab

shall be provided by the SI. The training labs for CCTNS project in Jammu and Kashmir has been

set up in all districts and training for the police personal has been started. The labs have been

set up in all districts including 1 training lab in SCRB Jammu, where the police personal are

getting trained. All necessary hardware has been provided.

6.4


Page | 84


6.5 Site Preparation at Police Stations and Higher Offices

The Jammu and Kashmir Police shall provide the necessary minimum constructed rooms/

space permanent construction to the SI. The SI would be responsible for conducting a site

survey to identify the exact situation of the sites for CCTNS infrastructure and commissioning.

The SI would prepare a site survey report detailing the current status of each site and the

enhancements to be made at each site (s) based on the State’s requirement and the guidelines

of MHA. SI would be responsible to prepare the client sites for setting up the necessary client

site infrastructure (The space cannot be used for any purpose other than for delivering the said

CCTNS services). State Government shall arrange for necessary clearances which shall enable

the SI to undertake civil, electrical, and mechanical works including but not limiting to

installation of electrical equipments, cable laying etc. at the respective sites.

Site preparation at Police Stations & Higher Offices will include:

• Ensure adequate power points with proper Earthing and electric cabling as required at the site. • Providing adequate furniture i.e. 4 computer tables with suitable space for printers, MFP,

fingerprint reader, digital camera and 4 no of moving chairs. • Adequate flooring needs to be done at all Police Stations. • Provision of Local area network (8 No of LAN Ports), Laying UTP cables, Structured Cabling,

Installation of Patch Panels, Installation of Wall Mountable Network Rack, Information Outlet CAT 6 and Patch Cords.)


Page | 85


6.6 Infrastructure at the Client Site Locations

The location for setting up the CCTNS offices will be provided by the department of JK

Police at respective locations. The list of Police Stations, Circle offices, and other locations

where the infrastructure is required is provided under the Geographical Scope Section. System

integrator would procure the CCTNS infrastructure required at the locations Statewide.

The following activities are to be carried out at each client location.

• The System Integrator will Supply the hardware, software, networking equipment’s, UPS, DG set to the each locations as per the requirements.

• The System Integrator will check redundant Network Connectivity -Ensuring last mile connectivity and testing of each location.

• The System Integrator will ensure the Installation, Testing and Commissioning of UPS, DG-Set at each location and proper functioning of these equipment’s.

• The System Integrator will ensure the Physical Installation of Desktops, Printer, Scanner/ MFD, Switch- Connecting peripherals, devices, etc.

• The system Integrator will check the Operating System Installation and Configuration of CCTNS Software and other application are in place as per the requirements.

• The System integrator will ensure the Installation of Antivirus and other support software. • The System Integrator will ensure the security at the desktops, switch and broadband

connection routers and network and browser Configuration as each location. • The System Integrator will ensure functionality of CCTNS and testing of the application

from the desktops • The System Integrator will ensure all the systems required are supplied, installed,

configured, tested and commissioned and declaring the site to be operational. • Ensure adequate number of power points with proper electric-earthing. • Supply and fixing of furniture like computer tables, chairs and other items shall be carried

out to ensure successful site preparation and installation of CCTNS at every location

CCTNS application will be accessed and used at various access locations across the State

like Police Stations, Circle Office, Sub Division office, District Office and other higher offices.

The total number and specifications for client systems, printers, UPS, network components and other

peripherals for all Police Stations and higher offices will be provide as an annexure to this RFP.


Page | 86


6.7 Network Connectivity for Police Stations, Higher Offices and District Training Centers

The System integrator is expected to provide the Network connectivity to all Police

Stations, Higher offices, district training centers wherever the connectivity is required for the

smooth functioning of the CCTNS Project. The System integrator shall procure the connectivity

from BSNL and is expected to set up the last mile connectivity to the all sites of Jammu and

Kashmir Police department. The System integrator will prepare comprehensive network

architecture for connecting all the Police Stations, Higher Offices to the State DC and DRC and

also the connectivity from the State DC/ DRC to the DC/ DRC at the Center hosting the CAS

(Center). The connectivity between the Data Center/ Disaster Recovery Center and the NCRB

data center that hosts CAS (Center) will be provided by BSNL.

The System integrator shall study the current network infrastructure of the JK Police

department. All district offices and higher offices of JK Police department will be covered by the

leased line with a speed of 2 Mbps or higher. The Police Stations will be covered by VPNOBB

connectivity of 512 Mbps speed and the remaining remote Police Stations will be covered

under VSAT. The remote locations are identified and the SI will study the network feasibility for

the remote locations as well.


Page | 87


6.8 Scope of Work of System Integrator with respect to Network Connectivity

The Networking solution of CCTNS project shall be based on a Hybrid Model which will

consist of State Wide Area Network (SWAN) operated by State under SWAN scheme and Data

network operated by Bharat Sanchar Nigam Limited (BSNL) which consists of Point to point

leased lines, VPNoBB, WiMax, VSAT and MPLS technologies. BSNL shall be providing the

Networking & Connectivity services along with Operations & Maintenance for all the locations

implemented by BSNL in that State.

BSNL shall also provide connectivity on MPLS VPN network for aggregated bandwidth at

each State SDC (State Data Center) for the locations connected on VPNoBB, WiMax and VSAT

network and also provide connectivity for SDC (State Data Centre) at State Headquarters (SHQs)

to the National Data Centre (NDC) of NCRB. Further BSNL shall provide MPLS VPN network for

connecting SDC and Disaster Recovery Centre (DRC) of the State. The DRC location need to be

finalized by the State and the SDC of other State may be mutually considered as DRC of each

other.

Scope of work for BSNL: The details of scope of work of BSNL are as under:

a) Provisioning of 2Mbps Point to Point Lease Line (P2PLL) for locations to be connected with

the nearest SWAN POP.

b) Provisioning of WAN connectivity on VPNoBB/ WiMax/ VSAT for locations which are not

feasible to be connected directly with the SWAN on P2PLL.

c) Provisioning of the Routers (at CCTNS site) and Modems for locations to be connected

directly with SWAN and all other hardware and network infrastructure provided for

VPNoBB/ WiMax/ VSAT connectivity.

d) Provisioning of Aggregated bandwidth on MPLS network at the State SDC for the locations

connected on VPNoBB, WiMax and VSAT network.

e) Provisioning of MPLS connectivity between State SDC and DRC.

f) Provisioning of MPLS connectivity between NDC and State SDC.

g) Maintaining the network including hardware supplied for minimum period of 3 years.


Page | 88


Role of System Integrator: The SI shall coordinate with BSNL and the JK State Police

Department for implementation of the Network and Connectivity solution of CCTNS project.

The following are the key responsibilities of the SI with respect to Networking and Connectivity. 1) Site preparation at all locations for establishment and installation of networking and

connectivity solution. 2) Coordination with the State Police Department and nominated officials of BSNL for

Installation, Configuration, Testing and Commissioning of BSNL’s2Mbps Point to Point Leased Lines for connecting with SWAN, VPNoBB, WiMax, VSAT and MPLS links.

3) Coordination with BSNL for ensuring Operations and Maintenance of networking hardware to ensure compliance to the SLAs as offered by BSNL.

4) The SI will also be coordinating with BSNL and State Police Department for SLA Monitoring, Fault Reporting & Troubleshooting of the links for meeting the Service levels and Master Service Agreement.

5) The Police Stations and Higher Offices which are within the proximity of SWAN PoP (Point of Presence) will be connecting on LAN directly from SWAN PoP. The SI shall also coordinate with SWAN operator (Appointed under SWAN project) for Installation, Configuration, Testing and Commissioning of LAN connectivity for sites co-located within the SWAN PoP and LAN connectivity from SWAN NOC (Network Operation Centre) to the SDC. The SI shall be coordinating with SWAN operator for SLA Monitoring, Fault Reporting& Troubleshooting of the LAN links as per SWAN SLA.

SI shall also coordinate with State CCTNS Nodal Officer (State Police Department) for

finalizing Police stations lists for the connectivity options, issuing commissioning report for

demand note/payment clearance, reporting SLA and providing for link status updates.

Network Connectivity for PS & Higher Offices is provided as an annexure to this RFP


Page | 89


6.9 IT Infrastructure at the Data Center and Disaster Recovery Center

The System Integrator would provide system integration services to procure and

commission the required software and infrastructure at the Data Centre and Disaster Recovery

Centre. The System integrator would deploy the configured and customized CAS (State),

additional modules and integrate with CAS (Centre)

The System Integrator will be completely responsible for the sourcing, installation,

commissioning, testing and certification of the necessary software licenses and infrastructure

required to deploy at the Data Centre and at the Disaster Recovery Centre (DRC).

CAS (State) will be developed in two distinct technology stacks by the SDA at the Center.

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.

The State data center in Jammu and Kashmir State is not in place yet. The Jammu and

Kashmir Police department would provide the premises for Primary Data Centre (DC) in SCRB

Jammu for hosting the solution and the Disaster Recovery Centre (DRC) in NCRB New Delhi. The

SI is responsible for sizing the hardware to support the scalability and performance

requirements of the solution.

The SI shall ensure that the servers and storage are sized adequately and redundancy is

built into the architecture that is required to meet the service levels mentioned in the RFP.

The SI shall be responsible for the sizing of necessary hardware and determining the

specifications of the same in order to meet the requirements of State.

SI shall provide a Bill of Material that specifies all the hardware, software and any

additional networking components of solution for the State Data Centre and DRC, in detail so as

to facilitate sizing of common Data Centre and DRC infrastructure such as Racks, Power and

Cooling, Bandwidth among other components. The common DC and DRC infrastructure shall be

provided by State.

SI shall ensure that effective Remote Management features exist in solution so that issues

can be addressed by the SI in a timely and effective manner and frequent visits to Data Centre/

DRC can be avoided.


Page | 90


After commissioning and testing of the entire system at Data Center/ DRC, the SI shall

support the State in getting the system certified by a 3rd party agency identified by State.

The following common data Centre services shall be provided by the SI for the data center:

• RACK • Power and Cooling • UPS, DG set power backup • Bandwidth and Connectivity • LAN • VPN • Firewall • Intrusion Protection System • Fire prevention • Physical security surveillance • Network Operation Centre • Common Data Centre facility Maintenance and Support

The SI is responsible for the below at the Data Centre/ DRC:

• Servers (Web, Application, Database, Backup, Antivirus, EMS, etc.) • Enterprise Management System (EMS) • Antivirus Software • SAN Storage • SAN Switches • Tape Library • All necessary software components including but not limited to Operating System, Backup

Software, and SAN Storage Management Software.

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, Database Server and Networking components shall be provided as Annexure to this RFP.


Page | 91


6.10 Data Migration and Data Digitization

Data Migration: Data migration is the process of making an exact copy of an organization’s current data

from one device to another device—preferably without disrupting or disabling active

applications—and then redirecting all input/output (I/O) activity to the new device. Migrating

the data from the other systems/ manual operations to the new system will include

identification of data migration requirements, collection and migration of user data, collection

and migration of master data, closing or migration of open transactions, collection and

migration of documentary information, and migration of data from the legacy systems.

The SI shall perform the data digitization & migration from manual and/ or the existing

systems to the new system. The Data digitization & migration to be performed by the SI shall be

preceded by an appropriate data migration need assessment including data quality assessment.

The Data migration strategy and methodology shall be prepared by SI and approved by police

Department. It 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 department for related work or in the form of paper

documents (Cases Documents and Police Station Registers). Almost all of such data items

relevant for a Police Station are maintained at the same Police Station.

Data Migration Requirements: 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 JK Police

or its nominated agencies.

Though JK Police will 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.


Page | 92


Any corrections identified by JK Police or any of its appointed agencies, during Data

Quality Assessment and Review, in the data digitized/ migrated by SI; it shall be addressed by SI

at no additional cost to JK Police.

1. 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

2. Carry out the migration of legacy electronic data 3. Carry out the migration of the data available in the existing registers, reports, case files, …

(Physical Copies) 4. Scan images and pictures within the case file in color and store them in the digital format. 5. Provide checklists from the migrated data to IGP Crime of Jammu and Kashmir for

verification, including number of records, validations (where possible), other controls / hash totals. Highlight errors, abnormalities and deviations.

6. Incorporate corrections as proposed 7. Get final sign off from IGP Crime of Jammu and Kashmir for translated/ migrated/ digitized

data 8. At the end of migration, all the data for old cases and registers must be available in the new

system.

Scope of Data Migration: The Total Data of Jammu and Kashmir police department is 248310. And the data which

has been digitized for last 10 years is 145453.

The pilot phase of the project will be run in 4 districts of Jammu and Kashmir State.

1. The historic data for Jammu, Udhampur, Srinagar, and Baramulla is 155512, out of which74204 has been feeded into CCIS application. The details of data are provided an annexure.

2. Sources of such data (Any legacy systems, Police Stations/ Higher Offices/ DCRB/ CCRB/ SCRB/ any other Crime/ Criminal Information Repositories such as Central Crime Station…) will be provided an annexure.

3. Data Migration Plan with respect to the process to be adopted for data migration, validations to be carried out, the responsibilities of the Police Department and System Integration during the Data Migration, and the phasing of data migration.

The data reconciliation and de-duplication is a major activity to be carried out as part of

the data migration.


Page | 93


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 IGP Crime of Jammu and Kashmir.

1. Analysis Analysis of the legacy data and its creation, conversion, migration and transfer to the

proposed new data base schema will be started during the scoping phase and shall take a

parallel path during the design and development phase of the application. It will cover the

following steps:

• Analyze the existing procedures, policies, formats of data in lieu of the new proposed system to understand the amount of the data and the applicability in CCTNS

• 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

2. 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

3. Data Take–On Take–On phase will be initiated when the proposed solution is ready to be deployed. It

will entail the following steps:

• 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


Page | 94


• Migrate from staging servers to production servers • Deploy and rollout the system as per the project plan

Additional Guidelines for Data Migration • SI shall convert/ migrate/ 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 department.

• In the event department is unable to obtain all the mandatory fields as conveyed by SI, SI shall suggest the most suitable work around. 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.


Page | 95


6.11 Migration of CIPA and CCIS Police Stations/ Higher Offices to CCTNS

The System integrator is responsible for migrating the Police Stations and Higher Offices

currently operational on CIPA and CCIS to CCTNS as part of the CCTNS implementation in the

State. SI shall validate the data in the CIPA systems and migrate the data to CCTNS.

CCIS (District Level) CIPA(police Stations)

Jammu Jammu city

Udhmapur Gandhi Nagar

Reasi Reasi

Samba Kathua

Kathua Vijaypur

Poonch Rajouri

Rajouri Poonch

Ramban Udhampur

Doda Ramban

Kistawar Doda

Srinagar Karan Nagar

Anantnag Kothibagh

Awantipora Ganderbal

Budgam Budgam

Ganderbal Leh

Bandipora Kargil

Pulwama Baramulla

Baramulla Kupwara

Handwara Handwara

Kupwara Anantnag

Leh Pulwama

Kargil Awantipora

Shopian Kulgam

All data which is currently present on CCIS and CIPA application will be migrated to the

CAS application.


Page | 96


6.12 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. It is to be noted that State has

adopted a holistic approach for implementation of Project to ensure that planned objectives

are met. 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 JK Police 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 stake holders who have an

interest in the issues with which the CCTNS project is concerned. The stake holder 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 and State Mission

Teams.


Page | 97


Stakeholder groups can be categorized into below categories, based on their influence

and role in managing the change and making it successful:

• Group I: Identify the key senior officers (ADGP, IG, DIG) responsible for Crime, Law and Order, who are directly impacted by the CCTNS with respect to receiving/analyzing the reports through CCTNS.

• Group II: Identify a few of the key officers (IG, DIG, DCP, ACP, SP) in charge of a zone/range/district/sub-division who are directly impacted by the CCTNS with respect to reviewing the police station performance through CCTNS, reviewing the reports generated by the system, carrying out the required analysis using CCTNS and providing the necessary guidance to the officers at the cutting edge.

• Group III: Identify a few of the key officers (SHO, SI, 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. It is to be noted that 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 stake

holder and the influence that they can exercise on their respective areas of control, for making

CCTNS successful. System Integrator (SI) shall ensure that all the 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


Page | 98


and to develop and deliver effective stakeholder interventions to individual stakeholders and

stake holder groups.

The stakeholders are distributed across the State/ UT 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

Stakeholder Analysis SI shall be responsible for interviewing stakeholders, analyzing data and recommending action plan to address concerns related to the CCTNS project. Finalize questions to understand stakeholder concerns, what success means for them, influence on project, what is the impact of the program on the stakeholder etc SI shall be responsible for refreshing the stakeholder engagement plan in consultation with the JK Police, whenever the project scope or the program implementation timelines undergo a change.

One time activity

Given the number of stakeholders, SI will use innovative ways to interview/interact with Stakeholders including, Phone/VC/Face to face/Focused Group etc so as to reduce costs of interaction.

Develop Stakeholder Engagement Content

SI shall develop content – discussion scripts, presentations or videos to explain the objectives of the program, what is in it for them and their people, what the benefits are.

Recurring activity over the entire duration of the SI

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


Page | 99


• 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/UT, 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 forth coming

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 (This may change as

per the size of the target police personnel).

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/ UT police department’s acceptance to change, potentially on

the job.


Page | 100


S. No Activities Details Frequency

Develop Change Readiness Survey Approach

• SI shall be responsible for developing the objectives, scope, and process for change measurement • SI shall also finalize the target audience, timelines, method of change measurement

One time activity

Develop and Configure Change Measurement Survey/ Instrument

• SI shall develop or configure an appropriate change measurement instrument that is convenient for audience and easy to assimilate for CM Team • SI shall configure the change measurement instrument based on the requirements of the project

Recurring Activity (at least four times in two years)

Select Sample Audience and Administer the survey

• SI shall select the sample for the survey and should ensure that the targeted audience is a fair mix representing all State Offices, solutions and all levels of the organization. • SI shall be responsible for administering the survey- paper based or electronic, as the case maybe.

One time activity followed by review of sample audience for each subsequent cycle

Analyze reports and Devise corrective action plan

• Analyze the result of the survey and generate survey reports (Higher Office-wise, State Headquarters -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

Once for each survey

Share the result with the leadership and refresh change management plan

• SI shall share the results of each survey with audience identified by JK Police and validate the corrective action plan with their inputs. • SI shall refresh the Change Management Plan with new interventions in consultation with JK Police Change Management Plan

Once for each survey


Page | 101


Other Requirements: • Change Readiness Survey should be deployed at significant milestone along the project

implementation timelines but not limited to four in number, considering different go-lives in the project implementation plan

• SI should conduct at least four change readiness surveys- First survey shall be a baseline survey and should be deployed at the beginning of Track-2.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 after the CAS (State) go-live.

• 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 JK Police 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.


Page | 102


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/ UT’s 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/ UT at Project, Program level as well as

for General awareness.

S. No Activities Details Frequency

Develop and Validate Detailed communication plan

• SI shall facilitate an exploration of specific objectives; i.e., who must understand what, by when, and why 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.

Once

Develop Communication Content

• SI shall be responsible for developing the content for communication material in English, Hindi and vernacular language. • SI shall ensure that the communication is simple, continuous and consistent.

Recurring Activity over the entire duration of the SI

Deliver Communication

• Prior to implementing the plan, the SI shall obtain the necessary sign-offs from State on

Recurring Activity (once a month) over


Page | 103


Events the 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.

the entire duration of the SI

Measure Effectiveness Of Communication and Update Change Management Plan

• After implementing the communications program, SI shall seek feedback on and measure the impact of the communications 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 JK Police 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.

Once in Six Months


Page | 104


Other Requirements: • SI shall work with the identified internal change agents (identified from the District and

State Mission Teams) for all the Communication and Awareness Programs

• SI shall utilize existing channels of communication and at the same time use innovative methods of communication for effectiveness

• SI should ensure that the communication messages are consistent, continuous and easy to understand and wherever possible in 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 Head quarters 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.


Page | 105


6.13 Capacity Building

The JK Police shall identify at least four qualified Trainers with relevant IT experience and

training competency within each District Mission Team and State Mission Team who will be

directly trained by the System Integrator and will be responsible for interfacing with the System

Integrator for all the Capacity Building Initiatives. These Trainers will be responsible for

implementing the Capacity Building interventions beyond the scope of the System Integrator.

The JK Police shall identify the Trainers within each of the Police Training Colleges in the

State who will be directly trained by the System Integrator. These trainers will be responsible

for including training on CCTNS within the training college curriculum and impart the training on

CCTNS to the new recruits and current personnel (refresher training) at the Police Training

Colleges.

Identification of Trainees: Based on the nature of their responsibilities and their

requirements from CCTNS, Police staff can be classified into the following categories for training

purposes:

• Group I: Identify the key senior officers (ADGP, IG, DIG) responsible for Crime, Law and Order, who are directly impacted by the CCTNS with respect to receiving/analyzing the reports through CCTNS.

• Role-based training will be carried out for these officers at suitable location in the State Headquarters by the System Integrator

• Group II: Identify the key officers (IG, DIG, 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.

• Role-based training will be carried out for these officers at suitable location in the State Headquarters and respective Districts by the System Integrator

• Group III: Identify 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.

• In addition to the computer awareness training, role-based training will be carried out for these officers at District Training Centers in the respective Districts by the System Integrators Refresher training can be carried out by the internal trainers subsequent to the System Integrator trainings


Page | 106


• Group IV: Identify at least 3-4 key officers/ constables (Station Writers, Court Duty, Head Constables, Constables) in each of the Police Stations and Higher Offices who will use CCTNS for capturing the data/ investigation forms, generating the reports and utilize the basic and advance search features of CCTNS to service the general service requests and aid in investigation process.

• In addition to the computer awareness training, role-based training will be carried out for the identified officers at District Training Centers in the respective Districts by the System Integrator

• Refresher training, subsequent training to the remaining officers/ constables in the Police Station and Higher Offices can be carried out by the internal trainers subsequent to the System Integrator trainings

• Group V: Identify 2 constables for each Circle Office that can provide the basic computer operation support to the police stations within the Circle.

Technical training will be carried out for the identified constables at District Training

Centers in the respective Districts by the System Integrator

The main challenges to be addressed effectively by the SI are the geographically dispersed

trainee base, wide variability in education and computer proficiency and minimal availability of

time. The SI holds the responsibility for creation of a detailed and effective training strategy,

user groups and classifications, training plan and guidelines, detailed training material, training

program designed their delivery to the target groups.

The SI holds the responsibility for creation of training material, designing the training

programs and their delivery to the target group. The State SI shall be responsible for the

following activities as part of the End User and Train the Trainer Training.

Develop Overall Training Plan SI shall be responsible for finalizing a detailed Training Plan for the program in

consultation with State’s JK Police covering the training strategy, environment, training need

analysis and role based training curriculum. SI shall own the overall Training plan working

closely with the JK Police Training team. SI shall coordinate overall training effort.

Develop District-Wise Training Schedule and Curriculum SI shall develop and manage the District-Wise training schedule in consultation with JK

Police 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


Page | 107


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.

Learning Management System and Training Portal Developing a Learning Management System and Training Portal for providing access to all

training content online including documents, demo, audio, video, simulation and practice,

assessment, self-learning and context sensitive help and monitoring, support and reporting

Develop Training Material Based on their needs and the objectives of CCTNS, training programs could be organized

under the following themes:

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 troubleshooters for CCTNS.

5. Customization of the Training Manuals, User Manuals, Operational and Maintenance Manuals provided along with the CCTNS CAS Software6. Design and development of the Training Manuals, User Manuals, Operational and Maintenance Manuals for the modules developed at the State level.

In cases where the training material may be made available by MHA/ NCRB, it is the SI’s

responsibility to ensure the relevance of the material to the State, customize if necessary and

own up the delivery and effectiveness.SI shall ensure that the training content meets all the

objectives of the training course. The material shall be developed in English, Hindi and


Page | 108


vernacular 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 District Training

Centers. Role-based training for the Senior Officers will be carried out for at suitable location in

the State Headquarters by the System Integrator.SI shall also impart simulated training on the

actual CAS (State) with some real lifelike 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, simulated

process walk-through and self assessment modules.


Page | 109


Select set of police staff with high aptitude group and/or relevant prior training, are to be

imparted with the training/skills to act as system administrators and also as troubleshooters

with basic systems maintenance tasks including hardware and network.

Deliver Training to Trainers (Internal and Trainers from the Training Colleges) SI shall help JK Police in assessing and selecting the internal trainers as well as the trainers

at training colleges who can conduct the end user training subsequent to the training by the SI.

SI shall coordinate the ‘Train the Trainer’ session for the identified trainers to ensure that they

have the capability to deliver efficient training.

In addition to the training delivered to the end-users, the trainers should also be trained

on effectively facilitate and deliver training to end users. Also, it is advisable to always run pilots

for any training program before deployment. This training will hence serve as the pilot and as a

training session for trainers as well. In addition the end-user training sessions, ToT training will

consist of three segments:

1. The first segment will be set of workshops covering effective presentation skills and coaching techniques and discussing the benefits and structure of the trainer model.

2. The second segment will be the formal CCTNS training which will consist of all modules of CCTNS relevant for their role.

3. The third segment will be a teach-back session where trained trainers will present course content and receive feedback regarding content, flow, and presentation techniques. This will also include a feedback session where trainers can provide feedback on the training materials, flow, comprehension level, and accuracy.

Training Effectiveness Evaluation SI shall evaluate the effectiveness of all end users trainings using electronic or manual

surveys. SI shall be responsible for analyzing the feedback and arrange for conducting refresher

training, wherever needed.

State will periodically monitor the training effectiveness through the performance metrics

and Service levels and the SI shall comply with the same.


Page | 110


6.14 Handholding Support

The System Integrator will provide one qualified and trained person per Police Station/

higher office for a period of 6 months or one qualified and trained person per two police

stations for a period of 1 year 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.

6.15 Requirement on Adherence to Standards

CCTNS system must be designed following open standards, to the extent feasible and in

line with overall system requirements set out in this RFP, in order to provide for good inter-

operability with multiple platforms and avoid any technology or technology provider lock-in.

Compliance with Industry Standards In addition to above, the proposed solution has to be based on and compliant with

industry standards (their latest versions as on date) wherever applicable. This will apply to all

the aspects of solution including but not limited to design, development, security, installation,

and testing. There are many standards that are indicated throughout this volume as well as

summarized below. However the list below is just for reference and is not to be treated as

exhaustive.

Portal development W3C specifications Information access/transfer protocols SOAP, HTTP/HTTPS Interoperability Web Services, Open standards Photograph JPEG (minimum resolution of 640 x 480pixels) Scanned documents TIFF (Resolution of 600 X 600 dpi) Biometric framework Bio API 2.0 (ISO/IEC 19784-1:200Specification 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 Management CCTNS system to be ISO 17799 compliant IT Infrastructure management ITIL / EITM specifications Service Management ISO 20000 specifications Project Documentation IEEE/ ISO specifications for documentation

The SI shall adhere to the standards published by the Department of Information

Technology, Government of India.


Page | 111


6.16 Support to 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. Test cases and Requirements Mapping 3. Infrastructure Compliance Review 4. Availability of Services in the defined locations 5. Performance and Scalability 6. Security/ Digital Signatures 7. Manageability and Interoperability 8. SLA Reporting System 9. Project Documentation 10. Data Quality Review

As part of Acceptance testing, audit and certification, performed through a third party

agency, STATE shall review all aspects of project development and implementation covering

software, hardware and networking including the processes relating to the design of solution

architecture, design of systems and sub-systems, coding, testing, business process description,

documentation, version control, change management, security, service oriented architecture,

performance in relation to defined requirements, interoperability, scalability, availability and

compliance with all the technical and functional requirements of the RFP and the agreement.

Here it is important to mention that there may be two agencies selected by STATE, one for

audit & certification of security and control aspect of the system and the other for audit &

certification of overall application S/W.

STATE will establish appropriate processes for notifying the SI of any deviations from

defined requirements at the earliest instance after noticing the same to enable the SI to take

corrective action. Such an involvement of the Acceptance Testing &Certification agencies,

nominated by STATE, will not, however, absolve the operator of the fundamental responsibility

of designing, developing, installing, testing and commissioning the various components of the

project to deliver the services in perfect conformity with the SLAs.

Following discusses the acceptance criteria to be adopted for system as mentioned above:


Page | 112


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 independent third party agency

(external audit) as well as the select internal department users (i.e. User Acceptance Testing).

2. Infrastructure Compliance Review 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.


Page | 113


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) proposed 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 payout by STATE to SI.

8. Project Documentation The Agency shall review the project documents developed by SI including requirements,

design, source code, installation, training and administration manuals, version control etc. Any

issues/ gaps identified by the Agency, in any of the above areas, shall be addressed to the

complete satisfaction of STATE.

9. Data Quality The Agency shall perform the Data Quality Assessment for the Data digitized/ migrated by

SI to the system. The errors/ gaps identified during the Data Quality Assessment shall be

addressed by SI before moving the data into production environment, which is a key mile stone

for Go-live of the solution.


Page | 114


7 SCOPE OF SERVICES DURING POST IMPLEMENTATION PHASE

The SI shall be responsible for the overall management of the system including the

application and entire related IT Infrastructure. The details of the post implementation support

services are provided as an Annexure to this RFP. SI shall develop/ procure and deploy an EMS tool

that monitors/ manages the entire enterprise wide application, infrastructure and network related

components.

SI shall provide the Operations and Maintenance Services for a period of 3 years following the

deployment and “Go-Live” of the solution in the State. In case each District is declared as “Go-Live”

at different instances during the project roll-out, the Operations and Maintenance Services for the

District will start following the deployment and “Go-Live” of the solution in the District and SI shall

continue to provide the Operations and Maintenance Support for a period of 3years following the

deployment and “Go-Live” of the solution in the last District.


Page | 115


8 IMPLEMENTATION AND ROLL-OUT PLAN

It is suggested that the solution be piloted in a few Police Stations in four Districts and the

feedback incorporated before rolling out across the STATE. The rollout plan shall be defined date-

wise, location-wise, module-wise and training completion and change management completion

wise. A detailed rollout checklist should be maintained for migrating application to production as

well as for location readiness.

SI shall prepare a detailed roll-out plan for each of the Districts in the Phase and get the

same approved by the State. SI is also responsible for conducting workshops for the key officers

(State Mission Team, District Mission Team, District Core Team) of the Districts/ State for

presenting the District-Wise roll-out plan and get the approval from the District Teams before

getting the final approval of the IGP Crime of Jammu and Kashmir, all also provide the

necessary assistance for the key officers (State Mission Team, District Mission Team, District

Core Team) of the Districts/ State during the design and implementation of CCTNS in the State.

One of the important factors that would determine the success of the CCTNS implementation in

the State is the continuous availability of domain experts to the implementation team.


Page | 116


SI shall put together a team of at least five (5) domain experts with a minimum of 10 years

of experience in the State Police Department who will work on this project on a full time basis

during the entire duration of the project.

List of Indicative Deliverables:

1) Overall Project Plan 2) CAS Configuration/ Customization/ Extension

a) Requirements Traceability Matrix b) Refined Functional Requirements Specification c) Systems Requirement Specification d) Design Document (High Level Design and Low Level Design) e) Test Plans f) CAS Configuration/ Customization/ Extension Document g) Change/ Reference Document documenting changes to the base version of CAS (State)

3) Network Connectivity a) Network Architecture b) Network diagrams (LAN and WAN) for PS/ HO to State DC/ DRC c) Network diagrams for connectivity between State DC/ DRC to NCRB DC/ DRC 4) Data Migration Strategy and Methodology including Detailed ration Plan

5) Change Management and Capacity Building a) Overall Change Management Plan b) Content for Change Management including Awareness and c) Communications Program d) Overall Capacity Building Plan and District-wise Training Schedule and Curriculum e) Training Material

6) District-wise Roll-out/ Implementation Plans.


Page | 117


8.1 Implementation and Project Roll-Out Plan

T = Date of Signing of Agreement with System Integrator (SI)

Detailed Project Plan

Phase Suggested Activities Responsibility

Timelines in

Months Phase – I (T= Signing Date of Agreement)

Setting up of Data Center Providing the Premises for Server Room & Disaster Recovery JK Police

T+1

Preparation of Bill of Quantity (Hardware, Software, Connectivity)

SI

Preparation of layout SI

Sizing document for Common Server Room Infrastructure (Server Racks, Power arrangement, Cooling etc.)

SI

Approval from Respective authorities SI/ SPMU/ JK Police

Preparation of Site SI

T+3

Wiring (Electrical, WAN Connectivity etc.) JK Police

Cooling Arrangements JK Police

Procurement of Hardware, Software, Licenses SI

24*7 Power backup Support Provision JK Police

Installation and Testing of UPS, DG-Set SI

T+4 Supply of the Hardware, Software, License & Networking equipments

SI


Page | 118


Installation and Testing of Equipments SI

Redundant Network Connectivity SI/ JK Police

24*7 Support system in case of break down SI

Testing and Up-gradation SI T+5 Inspection and Suggestions SPMU/ JK

Police Approval From Department JK Police

T+6 Operation Support SI

Customization of CAS (State) SRS preparation SI T+1

Approval from SPMU & Department and Change Incorporation in case of suggestions

SI/ SPMU/ JK Police T+2

Customization, Configuration and Development of Application SI T+4 User Acceptance Testing SI

T+5 Change Request SI

Final Implementation at all Police Stations SI T+6

CAS Integration with Identified applications SRS preparation SI T+2

Approval from SPMU & Department SI/ SPMU/ JK Police T+3

Customization, Configuration and Integration SI T+8 User Acceptance Testing SI

T+10 Change Request SI

Roll out at all Police Stations SI

CCTNS Site Preparation (Police Stations)


Page | 119


Site handover/ Approval for CCTNS JK Police T+1 Electrical & Local Area Networking Work SI

T+3 Procurement of Hardware, Software, Licenses SI

Supply of the Furniture & Fixtures SI T+4

Supply and Installation of Desktops/ PCs, Printers, Scanners, UPS

SI T+5

WAN Testing and VPN configuration SI

T+5 Arrangements of Power Backup (DG Set/ UPS) SI

Testing of Connectivity with Data Center (WAN) SI

Testing of CCTNS system at Police Station from User perspective

SI

Inspection and Suggestions SPMU/ JK Police T+6

CAS Operational at all Police Stations SI T+6

Approval from Department JK Police

Data Migration

Analysis of Data to be Migrated SI T+3

Collection & Consolidation of Data SI

Data Migration SI

T+6 Data Security SI

Certification from Department about authenticity of Migrated data

SI

Data Digitization Analysis of Data to be Digitized SI T+3 Collection & Consolidation of Data SI T+5


Page | 120


Data Digitization SI T+15

Data Validation & Re entry SI T+17 Certification from Department about authenticity of Digitized data

SI T+18

Capacity Building

Creating awareness and Sensitization (Through seminars, meetings, workshops)

SI/ JK Police T+2

Training of Master Trainers for CCTNS Application SI T+3

Up-gradation & Revision of Basic Computer Training SI

T+6 Training of Core Application Software (CAS) SI

System administration and Maintenance Training SI

Handholding & Helpdesk Establishment Starting of Handholding Support to PS for six months & Establishment of Helpdesk for PS & DC entire project period, Providing Technical Staff for DC

SI T+6

CCTNS Site Preparation (PHQ, PCR, FBP, FSL, Zone, Range, Districts) Phase –II (D = T+6) Site Handover/ Approval for CCTNS JK Police D+1

Electrical & Local Area Networking Work SI D+3

Procurement of Hardware, Software, Licenses SI

Supply of the Furniture & Fixtures SI D+4 Supply and Installation of Desktops/ PCs, Printers, Scanners, UPS

SI D+5


D+6 Arrangements of Power Backup (DG Set/ UPS) SI

Connectivity with DC SI

Testing of CCTNS system from User Perspective SI

Inspection and Suggestions SPMU/ JK


Page | 121


Police


Capacity Building (Phase II) Creating awareness and Sensitization (Through seminars, meetings, workshops)

SI D+2

Training of Master Trainers for CCTNS Application SI

D+6 Up-gradation & Revision of Basic Computer Training SI

Training of Core Application Software SI

System Administration and Maintenance Training SI

Helpdesk & Technical Support Starting Helpdesk and Technical Support for phase II locations for entire project period

SI D+6

Phase –III (C = D+6) CCTNS Site Preparation (all other locations and DR site) Site Handover/ Approval for CCTNS JK Police C+1 Electrical & Local Area Networking Work SI

C+3 Procurement of Hardware, Software, Licenses SI

Supply of the Furniture & Fixtures SI C+4 Supply and Installation of Servers, Desktops/PCs, Printers, Scanners, UPS

SI C+5


C+6

Arrangements of Power Backup (DG Set/ UPS) SI

Connectivity with DC SI

Testing of CCTNS system from User Perspective SI

Inspection and Suggestions SPMU/ JK Police



Page | 122


Capacity Building (Phase III) Creating awareness and Sensitization (Through seminars, meetings, workshops)

SI/ JK Police C+2

Training of Master Trainers for CCTNS Application SI

C+6 Up-gradation & Revision of Basic Computer Training SI

Training of Core Application Software SI

System administration and Maintenance Training SI

Helpdesk & Technical Support Starting Helpdesk and Technical Support for phase II locations for entire project period

SI C+6

Go-Live of CCTNS Project in entire State SI C+6 Operation and Maintenance Support

Support after Implementation Phases after Go-Live Operations and Maintenance support SI

Go live + 36

Warranty and AMC services SI

Continuations of Helpdesk for Providing Support to all Locations

SI

Regular supervision, monitoring and extending support to department for smooth functioning of project.

SI/ SPMU

Note: The Operation and Maintenance Support Period may be extended for further 12 or 24 Months.


Page | 123


9 SERVICE LEVELS

This section describes the service levels to be established for the Services offered by the SI to

department. The SI shall monitor and maintain the stated service levels to provide quality service

to department.

The SLA are provided as an Annexure to this RFP


Page | 124


10 ANNEXURE

ANNEXURE I CONTACT DETAILS

The list of addresses designations and contact details of the officials

S. No. Name Designation Address Telephone Number

Director General of Police (DGP)

1. Sh. Kuldeep Khoda (IPS) DG Police J&K

Director General of Police Police Headquarters (Summer Office) Peer Bagh, Srinagar Jammu & Kashmir, India - 190001

Gulshan Ground, Jammu (Winter Office) Jammu & Kashmir, India 180001

0194-2443010 (Off) Summer [May - October] 0194-2443011 (Off) Summer [May - October] 0194-2443012 (Fax) Summer [May - October]

0191-2430834 (Fax) Winter [November - April] 0191-2430871 (Off) Winter [November - April] 0191-2430841 (Off) Winter [November - April]

Inspector General of Police (IGP)

1. Smt. D. R. Doley (IPS) IGP Headquarters

Inspector General of Police Police Headquarters (Winter Office) Gulshan Ground, Jammu

Peer Bagh, Srinagar (Summer Office) Jammu & Kashmir, India - 190001

0191-2454064 (Off) Winter [November - April] 0191-2452351 (Fax) Winter [November - April]

0194-2443014 (Off) Summer [May - October] 0194-2443015 (Fax) Summer [May - October]

2. Sh. Raja Aijaz Ali (IPS) IGP Crime

Inspector General of Police Royal Apartments, Near Rajbagh Police Station, Srinagar - 190001

Old PHQ Complex, CPO Chowk, Panjtirthi Jammu - 180001

0194-2310912 (O) Summer [May - October] 0194-2310912 (O) Summer [May - October]

0191-2540496 (O) Winter [November - April]

Deputy Inspector General of Police (DIG)

1. Shri Yoginder kaul (I.P.S)

DIG Crime

Deputy Inspector General of Police Royal Apartments, Near Rajbagh Police Station, Srinagar -190001

Old PHQ Complex, CPO Chowk, Panjtirthi Jammu - 180001

0194-2310940(O) Summer [May - October]

0191-2561694 (O) Winter [November - April]


Page | 125


Senior Superintendent of Police (SSP)

1. Mr. Surinder Gupta (I.P.S) Senior Superintendent of Police D.P.O Udhampur 01992-270210

2. Mr. Haseeb Mughal Senior Superintendent of Police D.P.O Baramulla 01952-234217

3. Mr. Israr khan Senior Superintendent of Police D.P.O Samba 01923-246100

4. Mr. J.L Sharma Senior Superintendent of Police D.P.O Kathua 01922-234010

5. Mr. S. Anand Jain Senior Superintendent of Police D.P.O Rajouri 01962-262244

6. Mr. Ashkoor Ahmed Wani Senior Superintendent of Police D.P.O Poonch 01965-220408

7. Mr. Mohd Irshad Senior Superintendent of Police D.P.O Awantipora 01933-247202

8. Mohd. Aslam Senior Superintendent of Police D.P.O Handwara 01955-262600

9. Mumtaz Ahmed Senior Superintendent of Police D.P.O Shopian 01933-261890

10. Ashiq Hussain Bukhari Senior Superintendent of Police D.P.O Srinagar 01942- 455047

11. Uttam Chand Senior Superintendent of Police D.P.O Budgam 01951-255240

12. Amit Kumar Senior Superintendent of Police D.P.O Pulwama 01933-241237

13. Bashir Ahmed Khan Senior Superintendent of Police D.P.O Bandipora 01957-225870

14. Mubashir Latifi Senior Superintendent of Police D.P.O Kulgam 01931-260253

15. Ramesh Kumar Jha Senior Superintendent of Police D.P.O Anantnag 01932-222836

16. Beem Sin Tuti Senior Superintendent of Police D.P.O Kishtiwar 01995-259353

17. Keshav Ram Chaurisia Senior Superintendent of Police D.P.O Doda 01996-233396


Page | 126


18. Keshav Ram Chaurisia Senior Superintendent of Police D.P.O Reasi 01991-244663

19. Anil Kumar Magotra Senior Superintendent of Police D.P.O Ramban 01998-266648

20. Vivek Gupta Senior Superintendent of Police D.P.O Leh 01982-250200

21. Altaf Khan Superintendent of Police D.P.O Sopore 01954-222260

22. Imtiyaz Hussain Mir Senior Superintendent of Police D.P.O Ganderbal 01942-416443

23. V. K Birdi Senior Superintendent of Police D.P.O Kupwara 01955-252450

24. Javaid Iqbal Matoo Senior Superintendent of Police D.P.O Kargil 01985-232645

25. Basant Rath Senior Superintendent of Police D.P.O Jammu 0191-2561578

Deputy Superintendent of Police

1. Sh. Abdul Hakeem Munshi (KPS)

Dy SP SCRB

Deputy Superintendent of Police State Crime Record Bureau (SCRB) Gulshan Ground Jammu, India – 180001

0191 – 2433110


Page | 127


ANNEXURE II LIST OF 23 CIPA POLICE STATIONS AND EXISTING LEGACY SYSTEMS

The below list details out the number of Police Stations where CIPA has been implemented DISTRICTS POLICE

STATION Client

Computer Make

& Model

Operating System

Connectivity Status

Services being offered under CIPA

Operational Date Availability of Power Supply

Backup facility

Anantnag Anantnag 05 Acer Linux Nil Logging FIR, Investigation. 29.10.07 1-2 Hrs UPS Battery Exhausted

Baramulla Baramulla 05 Acer Linux Nil Logging FIR, Investigation. 01.01.08 8-9 Hrs Non- Functional Budgam Budgam 05 Acer Linux Nil Logging FIR, Daily Diary. 01.01.08 2-3 Hrs Non- Functional Doda Doda 05 Acer Linux Nil Logging FIR, Investigation. 08.10.07 5 Hrs UPS Battery

Exhausted Jammu City 04 Acer Linux Nil Logging FIR, Missing person

report, Investigation, Daily Diary. 01.01.08 8 Hrs UPS Functional,

UPS Battery Exhausted

Jammu Gandhi Nagar

05 Acer Linux Nil Logging FIR, Investigation, Missing person report, Daily Diary.

01.01.08 7-8 Hrs UPS Functional, UPS Battery Exhausted

Kargil Kargil 03 Acer Linux Nil Logging FIR, Daily Diary. 2-3 Hrs UPS Battery Exhausted

Kathua Kathua 05 Acer Linux Nil Logging FIR, Investigation, Missing person report.

01.01.08 12 Hrs UPS Battery Exhausted

Kupwara Kupwara 05 Acer Linux Nil Logging FIR. 01.01.08 Essential UPS Battery Exhausted

Leh Leh 04 Acer Linux Nil Logging FIR. 22.09.08 2-3 Hrs UPS Battery Exhausted

Poonch Poonch 05 Acer Linux Nil Logging FIR, Investigation, Daily Diary.

01.01.08 6-7 Hrs Functional

Pulwama Pulwama 04 Acer Linux Nil Logging FIR, Investigation, Missing person report, Daily Diary.


Rajouri Rajouri 05 Acer Linux Nil Logging FIR, Investigation, Daily Diary.


Srinagar Karan Nagar 04 Acer Linux Nil Logging FIR, Investigation, Missing person report.

01.01.08 5-8 Hrs Functional

Srinagar Kothibagh 05 Acer Linux Nil Logging FIR, Investigation. 01.11.07 5-8 Hrs Functional Udhampur Udhampur 05 Acer Linux Nil Logging FIR, Investigation, 01.01.07 5 Hrs UPS Functional,


Page | 128


Missing person report, Daily Diary.

UPS Battery Exhausted

Samba Vijaypur 04 Acer Linux Nil Logging FIR, Investigation, Missing person report, Daily Diary.

01.01.08 4 Hrs UPS Functional, UPS Battery Exhausted

Ganderbal Ganderbal 05 Acer Linux Nil Logging FIR, Investigation, Missing person report.

01.01.08 Essential UPS Battery Exhausted

Kulgam Kulgam 04 Acer Linux Nil Logging FIR. 01.01.08 3-4 Hrs UPS Battery Exhausted

Awantipora Awantipora 05 Acer Linux Nil Logging FIR, Investigation, Daily Diary.


Ramban Ramban 04 Acer Linux Nil Logging FIR, Investigation, Daily Diary.

01.01.08 24 Hrs Functional

Reasi Reasi 05 Acer Linux Nil Logging FIR, Investigation, Missing person report, Daily Diary.

01.01.08 6-7 Hrs UPS Battery Exhausted

Handwara Handwara 05 Acer Linux Nil Logging FIR, Investigation, Missing person report.



Page | 129


Currently there are 5 legacy systems that are operational in Jammu and Kashmir department. The application named as CCIS is operational at district level, whereas CIPA is operational in 23 police stations. Apart from these applications, there are 3 standalone applications that are currently operational and are maintained at SCRB Jammu

1. Common Integrated Police Application (CIPA)

S. No Application Name Nature

Common Integrated Police Application Registration 1 Description The application is used at national level

• Record Case Registration Details • Record Case Investigation • Record Prosecution Details • Record Other Crime & criminal related

details • Generate various Registers (Arrest register,

Missing register etc) • Generate various Reports (Crime Cases

reports, Missing Persons reports, • Unnatural death etc). • Maintain daily station diary (Only at 23

police stations)

2 Technology Used • Java as front end • Postgres SQL as backend • Linux as operating system Deployment

3 Deployment • Installed at 23 police stations. 4 GAPS • Only FIR Registration module is used

• Local language not supported • Operating System LINUX – not very user

friendly • Standalone application No

Interconnectivity across different police stations

• Very few reports & registers have been generated at police stations from the CIPA

5 Recommendations • All existing data on FIR Registration from CIPA should be migrated to CCTNS application.

• The data needs to be migrated to “Complaint and FIR Management Service” module of CCTNS.

• Continue after CCTNS. and should be discontinued after CCTNS implementation


Page | 130


2. Crime and Criminal Information System (CCIS)


Crime and Criminal Information system Registration 1 Description The Application is used for tracking the number of FIR’s

, complaints etc and has almost all the functionalities of CCIS

2 Technology Used • VB. Net as front end • MS-SQL Server 2000 as backend

3 Deployment Installed at district police offices 4 GAPS • Data not updated regularly-data entry is not

complete • Data is feeded manually as received from

district office. • Quality of entered Data is questionable • Recommendations

5 Recommendations • All existing data from CCIS need to be migrated to CCTNS

• (Assumption is that that even though CIPA is newer version of

• CCIS – data migration has not been done from CCIS to CIPA)

• . The data needs to be migrated to “Complaint and FIR Management Service” module of CCTNS. And discontinued after CCTNS implementation


Page | 131


3. Motor Vehicle Coordination System (MVCS)


Motor vehicle coordination System Motor vehicle 1 Description The application is developed by NCRB & is used to :

• Record information regarding lost/stolen and recovered vehicles.

• Recovery status of stolen and unclaimed vehicles.

• Generate certificates for the vehicle (whether involved in crime or not) and various other reports like monthly/yearly reports etc

2 Technology Used • Visual Basic (version 6.0) as front-end • MS-SQL 2005 server as backend

3 Deployment • Installed at SCRB 4 GAPS • Application is a standalone and not

integrated with other Systems • Information is not correct. • No advance search options

5 Recommendations • CCTNS CAS application would come with the module of Vehicle Registration.

4. Automated Fingerprint Identification System (AFIS)


Automated fingerprint identification system Finger print Analysis

1 Description The application is used for capturing, encoding, storing and matching fingerprints using the image processing and pattern recognition technique.

2 Technology Used • Java as Front end • Oracle at backend


integrated with other Systems • Scanning of fingerprints of criminals is not

done. • Application is not currently in use

5 Recommendations • All existing data need to be migrated to the CCTNS application.

• An analysis of existing functionality of the application should be done and enhanced accordingly.


Page | 132


5. Organized Crime Intelligence System (OCIS)


Organized Crime Intelligence system Organized crime 1 Description • The application is used for capturing the

profiles of different militancy organizations. • The application is used for capturing the

profiles of different fake currency gangs. • The application is used for capturing the

profiles of different narcotics and crime mafia gangs

2 Technology Used • Java as Front end • Oracle at backend


integrated with other Systems. • Search option is limited. • No option to modify or edit

5 Recommendations • All existing data need to be migrated to the CCTNS application.



Page | 133


ANNEXURE III PROPOSED DC FOR THE POLICE DEPARTMENT

The details pertaining to the proposed DC for the Police Department

Items Qty Make Model Network Server Racks 42 U 2 Application Server (Rack Server) 2 Test & Development Server (Rack Server) 1 Database Server (Rack Server) 2 Web Server (Blade Server) 2 Portal Server (Blade Server) 2 Backup Server (Blade Server) 1 Directory & Access Server 2 Communication & Mail Server 2 Blade Chassis 2 Storage Box (SAN) 2 Storage Area Switch 2 SAN Storage Management Software 1 Automated Tape Library 2 DR Recovery Storage 1 Back-up Software 1 HSM for PKI Security and Encryption (2No at DC and 1 at DR)

3

Router 2 FC – IP Router 2 Load Balancer 2 Link load Balancer 2 Core Switch L3 Gigabit 48 Port 2 KVM Switch 2 Patch Panel 24 Ports CAT 6 2 CAT 6 Cable (305 Mtr. Box) 3 Information Outlet CAT 6 36 Patch Cord 2 Mtr CAT 6 36 UTM Firewall with VPN and IPS 2 Data Center Software (Server OS with CAL, Server Management, Intranet Portal, MIS & Reporting Dashboard etc.)

18

Database Software (Processor Based for unlimited users)

6

Antivirus Software for Servers 18


Page | 134


Email Security Software Required features; Anti-spam Anti-virus Anti-spoofing Anti-phishing Anti-spyware (Attachments) Denial of Service Data Leak Prevention

2

Enterprise Management System (EMS) 1 Out Sourced manpower for datacenter 2 nos. × 3 shifts for 5 Years

-

ATS for three (3) years -


Page | 135


ANNEXURE IV HARDWARE DETAILS OF POLICE DEPARTMENT

The details of hardware for the Police Department

Office PC Including OS, MS-Office & Antivirus

UPS MFP Switch Other

OS, MS Office & Antivirus

Police Station

Non-CIPA (167) 668 167 167 167 0

Police Station

CIPA (23) 0 23 23 23 92

SDPO/ ASP

(67) 201 67 67 67 0

District police

(25) 250 25 25 25 0

Range

(7) 28 7 7 7 0

Zone

(2) 8 2 2 2 0

SCRB

(1) 10 1 1 1 0

PHQ

(2) 60 2 2 2 0


Page | 136


ANNEXURE V TOTAL NUMBER OF POLICE OFFICES

The total number of Police Stations and Higher offices

Police Stations 190 Districts 25 SDPO/ ASP 67 Ranges 7 Zones 2 PHQ Medium 2 SCRB 1

0

20

40

60

80

100

120

140

160

180

200

Police Stations

Districts SDPO/ ASP Ranges Office

Zones PHQ SCRB

Police Stations -190

Districts - 25

SDPO/ASP - 67

Range Office - 7

Zone Office - 2

PHQ - 2

SCRB - 1


Page | 137


ANNEXURE VI EXISTING LEGACY SYSTEMS

Currently there are 5 legacy systems that are operational in Jammu and Kashmir

department. The application named as CCIS is operational at district level, where as CIPA is

operational in 23 police stations. Apart from these applications, there are 3 standalone

applications that are currently operational and are maintained at SCRB Jammu.

S.No:1 Application Name Nature

Common Integrated Police Application Registration

1.Description The application is used at national level

• Record Case Registration Details • Record Case Investigation • Record Prosecution Details • Record Other Crime & criminal

related details • Generate various Registers (Arrest

register, Missing register etc) • Generate various Reports (Crime

Cases reports, Missing Persons reports,

• Unnatural death etc). • Maintain daily station diary (Only at

23 police stations)

2.Technology Used • Java as front end • Postgres SQL as backend • Linux as operating system

Deployment

3.Deployment • Installed at 23 police stations.

4.GAPS • Only FIR Registration module is used

• Local language not supported • Operating System LINUX – not very

user friendly • Standalone application No

Interconnectivity across different police stations

• Very few reports & registers have been generated at police stations


Page | 138


from the CIPA

5.Recommendations • All existing data on FIR Registration from CIPA should be migrated to CCTNS application.

• The data needs to be migrated to “Complaint and FIR Management Service” module of CCTNS.

• Continue after CCTNS. and should be discontinued after CCTNS implementation

S.No:2 Application Name Nature Crime and Criminal Information system Registration

1.Description The Application is used for tracking the number of FIR’s , complaints etc and has almost all the functionalities of CCIS

2.Technology Used • VB. Net as front end

• MS-SQL Server 2000 as backend

3.Deployment Installed at district police offices

4.GAPS • Data not updated regularly-data entry is not complete

• Data is feeded manually as received from district office.

• Quality of entered Data is questionable

• Recommendations

5.Recommendations • All existing data from CCIS need to be migrated to CCTNS

• (Assumption is that that even though CIPA is newer version of

• CCIS – data migration has not been done from CCIS to CIPA)

• . The data needs to be migrated to “Complaint and FIR Management Service” module of CCTNS. And discontinued after CCTNS implementation


Page | 139



Motor vehicle coordination System Motor vehicle

1.Description The application is developed by NCRB & is used to :

• Record information regarding lost/stolen and recovered vehicles.

• Recovery status of stolen and unclaimed vehicles.

• Generate certificates for the vehicle (whether involved in crime or not) and various other reports like monthly/yearly reports etc

2.Technology Used • Visual Basic (version 6.0) as front-end

• MS-SQL 2005 server as backend

3.Deployment • Installed at SCRB

4.GAPS • Application is a standalone and not integrated with other Systems

• Information is not correct.

• No advance search options

5.Recommendations • CCTNS CAS application would come with the module of Vehicle Registration.


Page | 140



Automated fingerprint identification system

Finger print Analysis

1.Description The application is used for capturing, encoding, storing and matching fingerprints using the image processing and pattern recognition technique.

2.Technology Used • Java as Front end

• Oracle at backend


4.GAPS • Application is a standalone and not integrated with other Systems

• Scanning of fingerprints of criminals is not done.

• Application is not currently in use

5.Recommendations • All existing data need to be migrated to the CCTNS application.



Page | 141



Organized Crime Intelligence system Organized crime

1.Description • The application is used for capturing the profiles of different militancy organizations.

• The application is used for capturing the profiles of different fake currency gangs.

• The application is used for capturing the profiles of different narcotics and crime mafia gangs

2.Technology Used • Java as Front end

• Oracle at backend


4.GAPS • Application is a standalone and not integrated with other Systems.

• Search option is limited.

• No option to modify or edit

5.Recommendations • All existing data need to be migrated to the CCTNS application.



Page | 142


ANNEXURE VII POWER SUPPLY

The availability of power supply to the police stations/ higher offices

List of Remote/ Inaccessible Police Establishments/ Police Stations of district Srinagar having long power shortage or no

power.

S.No. Zone Police Station Power Supply.

1. City South zone P/S Sadder Power Curtailment

P/S Raj Bagh

P/S Sherghari 24 Hours Supply

P/S Kara nagar

P/S Shaheed Gunj

P/S Batamaloo

P/S Women

2. City West Zone P/S Pantha chowk Long Power Shortage

P/S Nowgam

P/S Parimpora

3. City East Zone P/S Maisuma Power Curtailment

P/S Kral Khud

P/S Kothi Bagh

P/S R.M Bagh

P/S Nishat Interrupted Power Supply

P/S Harwan

4. City North Zone P/S Khanyar Interrupted power Supply

P/S Rainawari Power Shortage

P/S Nowhatta

P/S M.R. Gunj

P/S Safakadal

5. City Hazratbal Zone P/S Soura 24 Hrs. power supply line


Page | 143


P/S Lal Bazar leads to Air Tel tower near Police Stations.

P/S Nigeen Long Power Shortage

P/S Zakoora

P/S Zadibal

List of Remote/ Inaccessible Police Establishments/ Police Stations of Kashmir Zone (except district Srinagar) having long

power shortage or no power.

S.No. Name of the District

Police Station Description

1. Ganderbal I. P/S Ganderbal II. P/S Kangan III. P/S Kheerbhawani

Long power shortage.

2. Kargil I. P/S Drass II. P/S Zanaskar

Do

3. Baramulla I. P/S Baramulla II. P/S Sheeri III. P/S Tangmarg IV. P/S Chandoosa V. P/S Bijhama VI. P/S Kunzer VII. P/S Pattan VIII. P/S Kreeri IX. P/S Uri

Do

4. Kupwara I. P/S Karnah II. P/S Trehgam III. P/S Lalpora IV. P/S Sogam V. P/S Keran

Long power shortage from ‘I to IV’ while as no power supply in ‘V’ i.e.

P/S Keran

5. Handwara I. P/S Villgam Long power Shortage.

6. Bandipora I. P/S Gurez Do

7. Sopore I. P/S Dangiwacha II. P/S Panzalla

Long power shortage

8. Anantnag I. P/S Kokernag II. P/S Achabal III. P/S Dooru IV. P/S Ashmuquam V. P/S Srigufara VI. P/S Mattan

Do

9. Kulgam I. P/S Kulgam II. P/S Qazigund III. P/S Damhal Hanjipora

Do

10. Shopian I. P/S Zainapora II. P/S Kellar

Long power shortage


Page | 144


Status of Historic data for 4 districts for last 10 years:

S.No District Total Data Data digitized

1 Jammu 54136 31541 2 Udhampur 18068 13762 3 Srinagar 55098 20632 4 Baramulla 28210 8269 5 Total 155512 74204

Fingerprint Data for the year 2010 (January to November:

District Cases

Registered

Conviction

Taken place

Search slips

Received

Conviction slips

Received

Chance Finger

Print Received.

Jammu 3971 1344 54 05 0

Udhampur 1031 381 845 155 0

Baramulla 1028 89 276 97 0

Srinagar 2676 266 80 0 0

Fingerprint Data for the year 2009 (January to December:

District Cases

Registered

Conviction

Taken place

Search slips

Received

Conviction slips

Received

Chance Finger

Print Received.

Jammu 4011 1087 321 0 0

Udhampur 1026 386 779 246 05

Baramulla 1713 213 551 135 0

Srinagar 3401 435 157 0 0


District Cases

Registered

Conviction

Taken place

Search slips

Received

Conviction slips

Received

Chance Finger

Print Received.

Jammu 4056 709 383 02 0

Udhampur 902 304 693 302 0

Baramulla 1538 18 574 142 0

Srinagar 2939 527 177 0 43


Page | 145



District Cases

Registered

Conviction

Taken place

Search slips

Received

Conviction slips

Received

Chance Finger

Print Received.

Jammu 3516 1051 385 62 0

Udhampur 1015 400 677 226 0

Baramulla 1771 233 944 45 0

Srinagar 3105 305 40 0 0


District Cases

Registered

Conviction

Taken place

Search slips

Received

Conviction slips

Received

Chance Finger

Print Received.

Jammu 3436 1454 159 21 0

Udhampur 1062 397 389 05 0

Baramulla 2002 215 72 0 0

Srinagar 3255 415 50 0 0

Note: - Out of total data received at SCRB up to year 2006 all data from the 4 districts were feeded into the FACTS

System and afterward FACTS had exhausted its capacity and no feeding of data had taken place. Data Pending for feeding into

the FACTS System is as under:-

District Search slips

Received

Conviction slips

Received

Chance Finger

Print Received.

Total

Jammu 1143 69 0 1212

Udhampur 2994 929 05 3928

Baramulla 2345 419 0 2764

Srinagar 454 0 43 497

Total 6936 1417 48 8401


Page | 146


Data for MVCS for last ten years

Year Jammu Srinagar Baramulla Udhampur

Stolen Recovered Stolen Recovered Stolen Recovered Stolen Recovered

2001 141 32 151 34 12 2 12 4

2002 94 59 316 86 18 9 6 4

2003 67 17 74 45 13 7 7 0

2004 89 60 142 143 9 21 5 15

2005 157 54 128 121 5 7 3 2

2006 79 54 120 85 6 1 0 1

2007 123 71 104 99 12 0 5 2

2008 226 52 113 47 12 2 9 9

2009 183 92 162 47 8 0 8 7

2010 249 110 321 83 18 3 4 22

Data present in CIPA Application

S.No District Police Station Registration Investigation Prosecution Information General Dairy

1 Jammu Gandhi- Nagar 954 50 0 50 12050

2 Jammu City Jammu 288 133 - 32 29700

3 Kathua Kathua 986 47 0 48 -

4 Samba Vijaypur 505 202 - 283 33229

5 Poonch Poonch 552 35 - - 12,453

6 Rajouri Rajouri 1199 15 - - 31651

7 Doda Doda 793 42 0 72 474

8 Ramban Ramban 479 12 0 18 694

9 Reasi Reasi 712 287 - 73 17506

10 Udhampur Udhampur 1140 4 - 690 19960

11 Srinagar Kothibagh 407 07 - - -

12 Srinagar Kara nagar 392 176 - 398 -

13 Budgam Budgam UPS at Police station Budgam

is non functional due


Page | 147


to which the working of data feeding of CIPA

is stopped.

14 Baramulla Baramulla UPS at Police station

Baramulla is non functional due to which

the working of data feeding of CIPA is stopped. Also one server

is non functional

15 Kupwara Kupwara 376 - - -

16 Handwara Handwara 664 361 - 65 -

17 Anantnag Anantnag 1296 70 - - -

18 Pulwama Pulwama 1069 788 - 6 35725

19 Kulgam Kulgam 794 - - - -

20 Ganderbal Ganderbal 579 55 - 18 Version

conflict

21 Awantipora Awantipora 540 02 - - 858

22 Leh Leh 1458 - - - -

23 Kargil Kargil 166 - - - 25080


Page | 148


ANNEXURE VIII: CAS STACK TECHNOLOGY

DETAILS OF THE TECHNOLOGY STACKS FOR CAS (STATE) AND CAS (CENTER), CAS (State) will be developed in two distinct technology stacks by the SDA at the Center.

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 Solution by Software Development Agency

Version And Year of Release

Original Supplier

Description (include Major features/ Services only)

Support Provided By

Web Server Sun Java System Web Server 7.0

7.0 SUN HTTP Server SUN

Application Server Glassfish Application Server

3.0

SUN J2EE Application Server

SUN

Database MySQL 5.1 SUN DB Store SUN

Operating System

Solaris 10 SUN Operating System

SUN

Others Reporting Engine

Jasper Reports 3.7 Jasper Reporting Services

Email/ Messaging Q-Mail

1.4

Qmail Community E-Mail Solution

Search Engine

Search: Unstructured data: using open CMS search features Structured Data

N/a N/a N/a N/a

Mysql & Custom application interface

Portal Server

Glassfish Application Server

3.0 SUN J2EE Application Server

SUN

Workflow Engine

jBPM 4.0 JBoss Workflow Engine

Rules Engine

Custom Built N/a N/a N/a N/a

Directory Services

Sun Directory Services

7.0 SUN LDAP SUN

DMS/CMS Open CMS 7.5.1 Open CMS Content Management System

Security Physical Security, Network Security, DB Encryption (MySQL), DB Access Controls,

N/a N/a N/a N/a


Page | 149


Role Based Access Control (Custom Developed), LDAP (Sun Directory Services),

Identity Management

Open SSO 7.0 SUN LDAP SUN

Audit

log4j, Custom Built application 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

Proposed Solution by Software Development Agency


Original Supplier

Description (include major features/ services only)

Support Provided By

Web Server IIS 6 Microsoft Web and Application Server

Microsoft

Application Server IIS 6 Microsoft Web and Application Server

Microsoft

Database SQL Server 2008 2008 Microsoft DB Store Microsoft Operating System

Windows Server 2008 2008 Microsoft Operating System Microsoft


SQL Server reporting Services

2008 Microsoft Reporting Services

Microsoft

Email/ Messaging Q-Mail 1.4 Qmail community Email- Solution Search Engine Search:

Unstructured data Using open CMS Search features Structured data SQL DB-Search Engine &custom Application interface

N/a N/a N/a N/a

Portal Server IIS 6 Microsoft Webb and Application Server

Microsoft

Workflow Engine Windows workflow foundation

n/a n/a n/a n/a

Rules Engine Custom built n/a n/a n/a n/a Directory Services

Microsoft Active directory 2008 Microsoft LDAP Microsoft

DMS/ CMS Windows SharePoint Services

n/a n/a n/a Microsoft

Security Physical security, Network Security DB encryption (MYSQL),DB

n/a n/a n/a n/a


Page | 150


Acess Controls Role based Access Control(custom developed),LDAP(sun Directory Services)

Identity Management

Microsoft Active directory 2008 Microsoft LDAP Microsoft

Audit

IIS log, Custom built n/a n/a n/a Microsoft

ETL SQL Server ETL 2008 Microsoft ETL Microsoft

CAS (State) Offline Solution Proposed Solution

by Software Development Agency


Original Supplier


Support Provided By

Synchronization solution

Custom built n/a n/a n/a n/a

Application Container

Apache Tomcat 6.0 Apache foundation J2EE Application Container

Database MYSQL/ SQl Express

5.1/2008 Sun/Microsoft DB store Sun/Microsoft


Page | 151


CAS (Center) Solution Proposed Solution

by Software Development Agency


Original Supplier


Support Provided By

Web server

Sun Java System Web Server 7.0


Application Server Glassfish Application Server

3.0

SUN J2EE Application Server

SUN

Database MySQL 5.1 SUN DB Store SUN

Operating System

Solaris 10 SUN Operating System

SUN


Jasper Reports 3.7 Jasper Reporting Services

Email/ Messaging n/a

Search Engine

Search: Unstructured data: using Alfresco search features Structured Data Sybase DB search Engine & Custom Application Interface

N/a N/a N/a N/a

Portal Server

Glassfish Application Server


Workflow Engine

jBPM 4.0 jBoss Workflow engine

Rules Engine

Custom built n/a n/a n/a n/a

Directory Services

Sun Directory Services 7.0 SUN LDAP SUN

DMS/CMS Alfresco

Security Physical Security, Network Security, DB Encryption(MySQL), DBAccess Controls, Role Based Access Control (Custom Developed), LDAP(Sun Directory Services)

n/a n/a n/a n/a

Identity Management

Open SSO 7.0 SUN LDAP SUN

Audit

Log4j, Custom built n/a n/a n/a n/a

ETL +data quality Sybase Etl 15.1 Sybase ETL Sybase


Page | 152


ANNEXURE IX: 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 3 years of

comprehensive ATS support to the hardware at no additional cost.

1. Warranty support 2. Annual Technical Support (3yrs ATS support) 3. Handholding Services

a) Operations and maintenance services for the server and related infrastructure supplied and commissioned by the SI for the application at the Data Center and Disaster Recovery Center.

b) Central Helpdesk from the STATE designated premises. c) Software maintenance and support services. d) Application functional support services

The services shall be rendered onsite from the State designated premises. To provide the

support for the police stations, circle offices, sub-divisional offices, district headquarters,

ranges, zones, State police headquarters and other locations across the STATE where the

software, hardware, and other infrastructure will be rolled out, SI is expected to provide

experienced and skilled personnel at each location. The SI will also ensure that there is a Service

Center available or setup at each district or a group of districts of the State, as per mutual

understanding between State and the SI. 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:

1. SI shall provide a comprehensive warranty and on-site free service warranty for 3years from the date of Go Live.

2. SI shall obtain the three year product warranty and three year onsite free service warranty on all licensed software, computer hardware and peripherals, networking equipments and other equipment.

3. SI shall provide the comprehensive manufacturer's warranty in respect of proper design, quality and workmanship of all hardware, equipment, accessories etc. covered by the RFP. SI must warrant all hardware, equipment, accessories, spare parts, software etc. procured and implemented as per this RFP against any manufacturing defects during the warranty period.

4. SI shall provide the performance warranty in respect of performance of the installed hardware and software to meet the performance requirements and service levels in the RFP.

5. SI is responsible for sizing and procuring the necessary hardware and software licenses as per the performance requirements provided in the RFP. During the warranty period SI shall replace or augment or procure higher-level new equipment or additional licenses at no


Page | 153


additional cost to the State in case the procured hardware or software is not adequate to meet the service levels.

6. Mean Time between Failures (MTBF) If during contract period, any equipment has a hardware failure on four or more occasions in a period of less than three months or six times in a period of less than twelve months, it shall be replaced by equivalent or higher-level new equipment by the SI at no cost to STATE. However, if the new equipment supplied is priced lower than the price at which the original item was supplied, the differential cost should be refunded to STATE. For any delay in making available the replacement and repaired equipments for inspection, delivery of equipments or for commissioning of the systems or for acceptance tests/ checks on per site basis, STATE reserves the right to charge a penalty.

7. During the warranty period SI shall maintain the systems and repair/ replace at the installed site, at no charge to STATE, all defective components that are brought to the SI's notice.

8. The SI shall as far as possible repair the equipment at site. 9. In case any hard disk drive of any server, SAN, or client machine is replaced during

warranty/ ATS the unserviceable HDD will be property of STATE and will not be returned to SI.

10. Warranty should not become void, if STATE buys, any other supplemental hardware from a third party and installs it within these machines under intimation to the SI. However, the warranty will not apply to such supplemental hardware items installed.

11. The SI shall carry out Preventive Maintenance (PM), including cleaning of interior and exterior, of all hardware and testing for virus, if any, and should maintain proper records at each site for such PM. Failure to carry out such PM will be a breach of warranty and the warranty period will be extended by the period of delay in PM.

12. SI shall monitor warranties to check adherence to preventive and repair maintenance terms and conditions.

13. The SI shall ensure that the warranty complies with the agreed Technical Standards, Security Requirements, Operating Procedures, and Recovery Procedures.

14. SI shall have to stock and provide adequate onsite and offsite spare parts and spare component to ensure that the uptime commitment as per SLA is met.

15. Any component that is reported to be down on a given date should be either fully repaired or replaced by temporary substitute (of equivalent configuration) within the time frame indicated in the Service Level Agreement (SLA).

16. The SI shall develop and maintain an inventory database to include the registered hardware warranties.

As part of the ATS services SI shall provide:

1. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes, replacements and maintenance.

2. If the Operating System or additional copies of Operating System are required to be installed/ reinstalled/ de-installed, the same should be done as part of ATS.

3. SI should carry out any requisite adjustments/ changes in the configuration for implementing different versions of Application Software.

4. Updates/ Upgrades/ new releases/ new versions. The SI shall provide from time to time the Updates/ Upgrades/ new releases/ new versions of the software and operating systems as required. The SI should provide free upgrades, updates &patches of the software and tools to STATE as and when released by OEM.


Page | 154


5. SI shall provide patches to the licensed software including the software, operating system, databases and other applications.

6. Software License Management. The SI shall provide for software license management and control. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes, replacements, and maintenance.

7. SI shall provide complete manufacturer’s technical support for all the licensed software problems and/or questions, technical guidance, defect and non-defect related issues. SI shall provide a single-point-of-contact for software support and provide licensed software support including but not limited to problem tracking, problem source identification, problem impact (severity) determination, bypass and recovery support, problem resolution, and management reporting.

8. The manufacturer’s technical support shall at a minimum include online technical support and telephone support during the STATE’s business hours (Business hours in STATE will be from 0830 hours to 2030 hours on all days (Mon-Sun))with access for STATE and SI to the manufacturer’s technical support staff to provide a maximum of 4 hour response turnaround time. There should not be any limits on the number of incidents reported to the manufacturer. STATE shall have access to the online support and tools provided by the manufacturer. STATE shall also have 24x7 access to a variety of technical resources including the manufacturer’s knowledge base with complete collections of technical articles.

As part of the Handholding services to provide Operations and maintenance support for

the server and related infrastructure supplied and commissioned by the SI for the application at

the Data Center and Disaster Recovery Center SI shall provide:

1. The scope of the services for overall IT infrastructure management as per ITIL framework shall include 365x24x7 on site Monitoring, Maintenance and Management of the server and related infrastructure supplied and commissioned by the SI for the application at the Data Center and Disaster Recovery Center.

The business hours in STATE will be from 0830 hours to 2030 hours on all days (Mon-Sun).

SI will plan these services accordingly. The SI shall provide the MIS reports for all the devices

installed in the Data Center and Disaster Recovery Center in format and media as mutually

agreed with the STATE on a monthly basis. Whenever required by STATE, SI should be able to

provide additional reports in a pre-specified format. The indicative services as part of this

support are as below:

(a) System Administration, Maintenance & Management Services (b) Application Monitoring Services (c) Network Management Services (d) Backend Services (Mail, messaging, etc) (e) Storage Administration and Management Services (f) IT Security Administration Services and Services for ISO 27001 and ISO 20000 compliance (g) Backup and Restore Services


Page | 155


As part of the Handholding services to provide Centralized Helpdesk and Support for end

users at each location SI shall provide:

1. The service will be provided in the local language of the STATE.

2. The help desk service that will serve as a single point of contact for all ICT related incidents and service requests. The service will provide a Single Point of Contact (SPOC) and also resolution of incidents. STATE requires the SI to provide Help Desk services to track and route requests for service and to assist end users in answering questions and resolving problems related to the software application, network, Data Center, Disaster Recovery Center, Client site infrastructure, and operating systems at all locations. It becomes the central collection point for contact and control of the problem, change, and service management processes. This includes both incident management and service request management.

3. SI shall provide a second level of support for application and technical support at police stations, 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.

4. For all the services of STATE within the scope of this RFP, SI shall provide the following integrated customer support and help.

5. Establish 16X6 Help Desk facilities for reporting issues/ problems with the software, hardware and other infrastructure.

6. SI shall maintain and support to all client side infrastructure including hardware, networking components, and other peripherals.

7. SI shall provide maintenance of Hardware, including preventive, scheduled and predictive Hardware support, as well as repair and/ or replacement activity after a problem has occurred.

8. SI shall track and report observed Mean Time between Failures (MTBF) for Hardware.

9. SI shall provide functional support on the application components to the end users.

10. SI shall also provide system administration, maintenance and management services, LAN management services, and IT security administration services.

As part of the Handholding services to provide software maintenance and support

services SI shall provide:

1. The Software Maintenance and Support Services shall be provided for all software procured and implemented by the SI. The SI shall render both on-site and 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.

2. Updates/Upgrades/New releases/New versions. The SI will implement from time to time the Updates/Upgrades/New releases/New versions of the software and operating systems as required after necessary approvals from STATE about the same.


Page | 156


3. Tuning of application, databases, third party software’s and any other components provided as part of the solution to optimize the performance.

4. The SI shall apply regular patches to the licensed software including the operating system and databases as released by the OEMs.

5. Software Distribution. SI shall formulate a distribution plan prior to rollout and distribute/install the configured and tested software as per the plan.

6. Software License Management. The SI shall provide for software license management and control. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes, replacements, and maintenance.SI should perform periodic audits to measure license compliance against the number of valid End User software licenses consistent with the terms and conditions of site license agreements, volume purchase agreements, and other mutually agreed upon licensed software terms and conditions and report to STATE on any exceptions to SI terms and conditions, to the extent such exceptions are discovered.

7. The SI shall undertake regular preventive maintenance of the licensed software. As part of the Handholding services to provide application functional support services SI shall provide:

a) The Application Functional Support Services shall be provided for all software procured and implemented by the SI. The SI shall render both on-site maintenance and support services to STATE from the development center in STATE.

b) 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.

c) Routine functional changes that include user and access management, creating new report formats, and configuration of reports.

8. 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.

9. 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.

10. The SI shall perform user ID and group management services.

11. The SI shall maintain access controls to protect and limit access to the authorized End Users of the STATE.

12. The services shall include administrative support for user registration, creating and maintaining user profiles, granting user access and authorization, providing ongoing user password support, announcing and providing networking services for users and providing administrative support for print, file, directory and e-mail servers.


Page | 157


ANNEXURE X: SERVICE LEVELS

This document describes the service levels to be established for the Services offered by

the SI to the Jammu and Kashmir State. The SI shall monitor and maintain the stated service

levels to provide quality service to the JK Police.

1. Definitions. a) “Scheduled Maintenance Time” shall mean the time that the System is not in service

due to a scheduled activity as defined in this SLA. The scheduled maintenance time would not be during 16X6 timeframe. Further, scheduled maintenance time is planned downtime with the prior permission of the Jammu and Kashmir State.

b) “Scheduled operation time” means the scheduled operating hours of the System for the month. All scheduled maintenance time on the system would be deducted from the total operation time for the month to give the scheduled operation time. The total operation time for the systems and applications within the Primary DC, DRC and critical client site infrastructure will be 24X7X365. The total operation time for the client site systems shall be 18 hours.

c) “System or Application downtime” means accumulated time during which the System is totally inoperable within the Scheduled Operation Time but outside the scheduled maintenance time and measured from the time the State and/ or its employees log a call with the SI team of the failure or the failure is known to the SI from the availability measurement tools to the time when the System is returned to proper operation.

d) “Availability” means the time for which the services and facilities are available for conducting operations on the State/ UT system including application and associated infrastructure. Availability is defined as:

e) {(Scheduled Operation Time – System Downtime)/ (Scheduled Operation Time)} * 100%

f) “Helpdesk Support” shall mean the 16x6 basis support centre which shall handle Fault reporting, Trouble Ticketing and related enquiries during this contract.

g) “Incident” refers to any event/ abnormalities in the functioning of the Data Centre Equipment/ Services that may lead to disruption in normal operations of the Data Centre, System or Application services.

2. Interpretations. a) The business hours are 8:30AM to 4:30PM on all working days (Mon-Sat) excluding

Public Holidays or any other Holidays observed by the State. The SI however recognizes the fact that the State/ UT offices will require to work beyond the business hours on need basis.

b) "Non-Business Hours" shall mean hours excluding “Business Hours”.

c) 18X7 shall mean hours between 06:00AM -12.00 midnight on all days of the week.

d) If the operations at Primary DC are not switched to DRC within the stipulated timeframe (Recovery Time Objective), it will be added to the system downtime.

e) The availability for a cluster will be the average of availability computed across all the servers in a cluster, rather than on individual servers. However, non compliance with


Page | 158


performance parameters for infrastructure and system /service degradation will be considered for downtime calculation.

f) The SLA parameters shall be monitored on a monthly basis as per the individual SLA parameter requirements. However, if the performance of the system/services is degraded significantly at any given point in time during the contract and if the immediate measures are not implemented and issues are not rectified to the complete satisfaction of the State or an agency designated by them, then the State will have the right to take appropriate disciplinary actions including termination of the contract.

g) A Service Level violation will occur if the SI fails to meet Minimum Service Levels, as measured on a half yearly basis, for a particular Service Level. Overall Availability and Performance Measurements will be on a monthly basis for the purpose of Service Level reporting. An “Availability and Performance Report” will be provided by the SI on monthly basis in the JK Police suggested format and a review shall be conducted based on this report. A monthly availability and Performance Report shall be provided to the State at the end of every month containing the summary of all incidents reported and associated SI performance measurement for that period. The monthly Availability and Performance Report will be deemed to be accepted by the State upon review and signoff by both SI and the State. Where required, some of the Service Levels will be assessed through audits or reports e.g. utilization reports, measurements reports, etc. as appropriate to be provided by the SI on a monthly basis, in the formats as required by the State. The tools to perform the audit will need to be provided by the SI. Audits will normally be done on regular basis or as required by the State and will be performed by the State appointed third party agencies.

h) EMS system as specified in this RFP shall play a critical role in monitoring the SLA compliance and hence will have to be customized accordingly. The 3rdparty testing and audit of the system shall put sufficient emphasis on ensuring the capability of EMS system to capture SLA compliance correctly and as specified in this RFP. The selected System Integrator (SI) must deploy EMS too land develop additional scripts (if required) for capturing the required data for SLA report generation in automated way. This tool should generate the SLA Monitoring report in the end of every month which is to be shared with the State/ UT on a monthly basis. The tool should also be capable of generating SLA reports for a half-year. The State will audit the tool and the scripts on a regular basis.

i) The Post Implementation SLAs will prevail from the start of the Operations and Maintenance Phase. However, SLAs will be subject to being redefined, to the extent necessitated by field experience at the police stations/ higher offices and the developments of technology practices globally. The SLAs may be reviewed on an annual/bi-annual basis as the State decides after taking the advice of the SI and other agencies. All the changes would be made by the State in consultation with the SI.

j) The SI shall provide the following service levels. In case these service levels cannot be achieved at service levels defined in the tables below, it shall result in a breach of contract and invoke the penalty clause. Payments to the SI are linked to the compliance with the SLA metrics laid down in the tables below. The penalties will be computed and calculated as per the computation explained in this Annexure. During the contract period, it is envisaged that there could be changes to the SLA, in terms of addition,


Page | 159


alteration or deletion of certain parameters, based on mutual consent of both the parties i.e. the state and SI.

k) Following tables outlines the key service level requirements for the system, which needs be ensured by the SI during the operations and maintenance period. These requirements shall be strictly imposed and either the state or a third party audit/certification agency shall be deployed for certifying the performance of the SI against the target performance metrics as outlined in the tables below.

IMPLEMENTATION PHASE SLAS:

1. Capacity Building Service Level Description Measurement

Capacity Building At least 80% of the trainees within the training program should give a rating of satisfactory or above. Severity of Violation: High This service level will be monitored and measured on a per District basis through feedback survey to be provided to each attendee within the program. If the training quality in the program falls below the minimum service level, it will be treated as one (1) violation. The total number of violations for the payment period will bathe cumulative number of violations across all the programs across all Districts in the payment period.

2. Data Migration/ Digitization Service Level Description Measurement

Data Migration Error rate in a batch should be less than 0.5%

Errors having “High” impact would amount from mistakes in section of offence/ FIR details/ Name of accused or complainant/ particulars of accused such as address, contact details, Ids (DL No., passport No. etc.). High impacting errors shall have direct implications to penalties.

Errors having “Low” impact would amount from other mistakes. 3 or less low impacting errors per case file will not be subjected for penalties, however mistakes would be corrected by SI at the time of such incident is reported. Severity of Violation: High

This service level will be measured on a monthly basis for each Police Station/ Higher Office.

If the data migration/ digitization service level in a Police Station/ higher office falls below the minimum service level, it will be treated as one (1) violation.

The total number of violations for the payment period will be the cumulative number of violations across all the Police Station/ higher offices in the payment period.


Page | 160


3. Service Level Agreement (SLA) Criteria

Delivery Related Service Level Agreement (SLA) Criteria Explanation: The deduction mentioned in this table shall be made from the next due payment to the vendor for services provided on Statewide basis.

S. No. Service Metrics Parameters

Baseline Lower Performance Violation of Service level agreement

Basis of Measurement

Remarks

Metric Metric Deduction Metric Deduction 1. Delivery of the

reports/deliverables due for this section

As per the dates as mentioned in the contract

One week after the due date

`. 10,000/- Per Week

>1 week after the due date

`. 20,000 for every week of delay

Dates for delivery of reports as mentioned in the contract

2. Customization of CAS (State)/ Integration with existing application/ migrations of existing data

6 months from date of signing of contract

6-8 months `. 100,000/- > 8 months `. 1,00,000 per month of delay

Months taken after beginning of the Assignment and test the application at the Data center by the Operator, not including the software audit by TPA

The application should be tested for desired functionalities, security, and completeness as well as compliance with SLA, within the period

3. Supply, installation and Commissioning of hardware at offices

3 months 4-6 months For non-compliance At each point of deployment: `. 30,000

> 6 months For non-compliance At each point of deployment `. 45,000/ month

Months after taking over of the office site for project

The deduction shall be made per site basis, where criterion is not satisfied

4. Supply, installation and Commissioning

6 months from the

6-7 months `. 100,000/- > 7 months `. 100,000 for every

Months taken after beginning

JK Police may conduct


Page | 161


of the Datacenter Equipment

date of signing of contract

month of delay

of the assignment independent audit to verify that the data center is as per the Specifications

5. Capacity building All the trainees should pass the training

Less than 80% and more than 60% marks

` 500/- Per Trainee

Less than 60% marks

`1000/- per trainee

Results from Examination test, post training course

The feedback of the attendees must be taken after every training session/ program and this feedback should be leveraged for improving the capacity building program

6. Data Digitization Zero tolerance for High Impacting errors and less than 3 low impacting errors per case file

Lower Performance if the error rate is “between” 0.5% to 1%.

` 50/- error

Above 1% ` 100/- error and entire case to be redone

Error per case file during verification

Error rate is measured by percentage of the records with corrections marked by designated officials


Page | 162


Error rate in a batch during verification should be less than 0.5% - baseline metric

7. Maintenance Phase

All the issues reported regarding hardware, software etc. should be resolved within 24 hours(within 1 working day)

Resolution of issues within 2 working days of reporting

`. 250/- per instance

Resolution of the issue after 2 Working days

`.500/- for every day delay over and above beyond

Time and date of reporting of the issue

Note: Based on the requirement, above service levels can be change at the time of project execution.


Page | 163


4. Violations and Associated Penalties a) The primary intent of Penalties is to ensure that the system performs in accordance

with the defined service levels. Penalties are not meant to be punitive or, conversely, a vehicle for additional fees.

b) Penalty Calculations. The framework for Penalties, as a result of not meeting the Service Level Targets are as follows:

I. The performance will be measured for each of the defined service level metric against the minimum/ target service level requirements and the violations will be calculated accordingly.

II. The number of violations in the reporting period for each level of severity will be totaled and used for the calculation of Penalties.

III. Penalties applicable for each of the high severity violations are 0.1% of respective payment-period payment to the SI.

IV. Penalties applicable for each of the medium severity violations are 0.05% of respective payment-period payment to the SI.

Post Implementation Phase SLAs

1. Primary DC/ DRC Site Infrastructure Systems, Application Availability & Performance a) Production CAS Systems. The failure or disruption has a direct impact on the ability

to service its police stations/ higher offices, ability to perform critical back-office functions or a direct impact on the organization.

This includes but not limited to:- I. Storage and related switches at Primary DC and DRC.

II. Web, Application, Database, and Backup Servers at Primary DC and DRC. III. Primary DC to DRC connectivity. IV. Primary DC and DRC network infrastructure. V. Primary DC and DRC security infrastructure.

b) Non-CAS Systems in Production and Non Production Systems (Development, QA, and Training). The failure or disruption has no direct impact on the Jammu and Kashmir state ability to serve its police stations/ higher offices, or perform critical back-office functions.

I. Production Non CAS Servers. II. Test, QA and Training Servers.

III. Helpdesk infrastructure & applications. IV. EMS Infrastructure.

c) CAS Solution Components. The failure or disruption has a direct impact on the state / UT’s ability to service its police stations/ higher offices, ability to perform critical back-office functions or a direct impact on the organization.

d) Non ERP Solution Components. The failure or disruption has no direct impact on the state/ UT’s ability to serve its police stations/ higher offices, or perform critical back-office functions.

e) These service levels will be monitored on a monthly basis.

f) The below tables gives details on the Service Levels the SI should maintain.


Page | 164


Service Level Description Measurement

Infrastructure Availability Availability of production CAS systems shall be at least 99% Severity of Violation: High

Availability over the six month period

Violations for calculation of penalty

< 99% &>= 98.5% 1 < 98.5% &>= 98% 2

< 98% 3 In addition to the above, if the service level in any month in the six-month period falls below 98%, one (1) additional violation will be added for each such month to the overall violations for this service level.

Infrastructure Availability Availability of non-CAS systems in production and nonproduction systems shall be at least 97%. Severity of Violation: Medium



< 97% &>= 96.5% 1 < 96.5% &>= 96% 2


Infrastructure Availability RTO shall be less than or equal to six (6) hours. Severity of Violation: High Each instance of non-meeting this service level will be treated as one (1) violation.

Infrastructure Availability RPO (zero data loss in case of failure of Primary DC) should not be greater than one hour. Severity of Violation: High Each instance of non-meeting this service level will be treated as two (2) violations.

Infrastructure Performance Sustained period of peak CPU utilization of any server crossing70% (with the exception of batch processing) shall be less than or equal to 30 minutes. Severity of Violation: High Each occurrence where the peak CPU utilization of any server crosses 70% (with the exception of batch processing) and stays above 70% for time more than 30 minutes will be treated as one (1) instance.

Number of instances over the six month period


>0 &<=3 1 > 3 2

In addition to the above, if the number of instances in any month in the six-month period exceeds 3, one (1) additional violation will be added for each such month to


Page | 165


the overall violations for this service level. Infrastructure Performance Sustained period of peak I/O utilization of any server

crossing70% (with the exception of batch processing) shall be less than or equal to 30 minutes. Severity of Violation: High Each occurrence where the peak I/O utilization of any server crosses 70% (with the exception of batch processing) and stays above 70% for time more than 30 minutes will be treated as one (1) instance.



>0 &<=3 1 > 3 2

In addition to the above, if the number of instances in any month in the six-month period exceeds 3, one (1) additional violation will be added for each such month to the overall violations for this service level.

Infrastructure Performance Sustained period of peak memory utilization of any server crossing 70% (with the exception of batch processing) shall be less than or equal to 30 minutes. Severity of Violation: High Each occurrence where the peak memory utilization of any server crosses 70% (with the exception of batch processing)and stays above 70% for time more than 30 minutes will be treated as one (1) instance.



>0 &<=3 1 > 3 2

In addition to the above, if the number of instances in any month in the six-month period exceeds 3, one (1) additional violation will be added for each such month to the overall violations for this service level.

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



< 99.9% &>= 99.5% 1 < 99.5% &>= 99% 2


Application Availability Availability of non-CAS solution components measured within the Data Center shall be at least 97%


Page | 166


Severity of Violation: Medium This service level will be monitored on a monthly basis.



< 97% &>= 96% 1 < 96% 2

In addition to the above, if the service level in any month in the six-month period falls below 96%, one (1) additional violation will be added for each such month to the overall violations for this service level.

Application Performance Average application response time during peak usage hours as measured from a client terminal within the Data Center shall not exceed 4 seconds. Severity of Violation: High The list of critical business functions and peak usage hours will be identified by the state/ UT during the Supply and System Integration Phase. This service level will be monitored on a monthly basis.

Average application response time over the six-month period


> 4s &<= 5s 2 > 5s &<= 6s 4

> 6s 5 In addition to the above, if the average runaround time in any month in the six-month period goes beyond 6s, one (1) additional violation will be added for each such month to the overall violations for this service level.

2. Client Site Infrastructure Systems a) Critical Client Site Systems. The failure or disruption results in inability of the police

Station/ Higher offices to service its dependent offices or perform critical back-office functions. Critical client site infrastructure means the IT infrastructure at client site which are shared by multiple users i.e., Core Switch, Core Routers, etc.

b) This service level will be measured on a monthly basis for each implementation site.

c) The below tables gives details on the Service Levels the SI should maintain.

Service Level Description Measurement

Client Site Systems Availability Availability of the critical client site infrastructure components at all the implementation sites shall be at least 99% Severity of Violation: High This service level will be measured on a monthly basis for each implementation site. If the availability in a month for an implementation site falls below the minimum service level, it will be treated as one (1) violation. The total number of violations for the six-month period will be the cumulative number of violations across all the months across all sites in the six-month period.


Page | 167


3. Handholding Support: Client Site Support a) Level 1 Incident. The incident has an immediate impact on the state/UT’s ability to

service its police stations/ higher offices, to perform critical back-office functions or has a direct impact on the organization.

b) Level 2 Incidents. The incident has an impact on the state/ UT’s ability to service its police stations/ higher offices that while not immediate, can cause service to degrade if not resolved within reasonable time frames

c) The severity of the individual incidents will be mutually determined by the state/ UT and SI.

d) The scheduled operation time for the client site systems shall be the business hours of the state/ UT.

e) This service level will be measured on a monthly basis for each implementation site.

f) The tables on the following page give details of the Service Levels the SI is required to maintain.

Service Level Description Measurement Client Site Support Performance

80% of the Level 1 Incidents at each site should be resolved within 2 business hours from the time call is received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 8 business hours. Severity of Violation: Medium This service level will be measured on a monthly basis for each implementation site. If the performance in a month for an implementation site falls below the minimum service level, it will be treated as one (1) instance. The total number of instances for the six-month period will be the cumulative number of instances across all the months across all sites in the six-month period. Average number of instances per month = (Total number of instances for the six-month period) / 6

Average number of instances per month

Violations for calculation of Penalty

>0 &<=4 1 >4 &<=8 2

>8 &<=12 3 >12 4


Page | 168


Client Site Support Performance 80% of the Level 2 Incidents at each site should be resolved within 6 business hours from the time a call is received /logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 48 hours. Severity of Violation: Medium This service level will be measured on a monthly basis for each implementation site. If the performance in a month for an implementation site falls below the minimum service level, it will be treated as one (1) instance. The total number of instances for the six-month period will be the cumulative number of instances across all the months across all sites in the six-month period. Average number of instances per month = (Total number of instances for the six-month period) / 6

Average number of instances per month

Violations for calculation of Penalty

>0 &<=4 1 >4 &<=8 2

>8 &<=12 3 >12 4

Client Site Support Performance Replacement of hardware equipment shall be done within 7days of notification by the state / UT. These equipments would have failed on four or more occasions in a period of less than three months or six times in a period of less than twelvemonths. (Mean Time Between Failure Condition) Severity of Violation: High Each instance of non-meeting this service level will be treated as one (1) violation.

4. Handholding Support: Application Support a. Level 1 Defect. The failure to fix has an immediate impact on the State/ UT’s ability

to service its police stations/ higher offices, inability to perform critical back-office functions or a direct impact on the organization.

b. Level 2 Defects. The failure to fix has an impact on the State/ UT’s ability to service its police stations/ higher offices that while not immediate, can cause service to degrade if not resolved within reasonable time frames.

c. Level 3 Defects. The failure to fix has no direct impact on the State/UT’s ability to serve its police stations/ higher officers, or perform critical back office functions.

d. The severity of the individual defects will be mutually determined by the State/ UT and SI.

e. This service level will be monitored on a monthly basis. f. The below tables gives details on the Service Levels the SI should maintain.

Service Level Description Measurement Application Support Performance 95% of the Level 1 defects shall be resolved within 4

business hours from the time of reporting full details. Severity of Violation: High


Page | 169


This service level will be monitored on a monthly basis. Performance over the six month period


< 95% &>= 90% 1 < 90% &>= 85% 2 < 85% 3


Application Support Performance

95% of the Level 2 defects shall be resolved within 72 hours from the time of reporting full details. Severity of Violation: High This service level will be monitored on a monthly basis.

Performance over the six month period


< 95% &>= 90% 1 < 90% &>= 85% 2 < 85% 3


Performance over the six month period


< 100% &>= 90% 1 < 90% &>= 80% 2 < 80% 3


Application Support Performance

Up to date of the documentation of the design, modifications, enhancements, and defect-fixes in the half-yearly period. Severity of Violation: Medium This service level will be measured on a half-yearly basis. Each instance of non-meeting this service level will be treated as one (1) violation.


Page | 170


5. Network Uptime: Severity of Violation: High

This service level will be monitored on a monthly basis.

The below tables gives details on the Service Levels the SI should maintain.

Service Level Description

Measurement

Network Uptime

Availability of the network and all related components at all the implementation sites shall be at least 99% Severity of Violation: High This service level will be measured on a monthly basis for each implementation site. If the network availability in a month falls below the minimum service level, it will be treated as one (1) violation. The total number of violations for the six-month period will be the cumulative number of violations across all the months across all sites in the six-month period.

6. Handholding Support: Helpdesk and Data Center Support a) Level 1 Call. The failure to fix has an immediate impact on the state /UT’s ability to

service its police stations / higher offices, inability to perform critical back-office functions or a direct impact on the organization.

b) Level 2 Calls. The failure to fix has an impact on the state / UT’s ability to service its police stations / higher offices that while not immediate, can cause service to degrade if not resolved within reasonable time frames.

c) Level 3 Calls. The failure to fix has no direct impact on the state / UT’s ability to serve its police stations / higher offices, or perform critical back-office functions.

d) This service level will be monitored on a monthly basis. e) The below tables gives details on the Service Levels the SI should maintain.

Service Level Description Measurement Helpdesk Performance 98% of the calls shall be answered within 45

seconds. Severity of Violation: High This service level will be monitored on a monthly basis.

Performance over the six-month period


< 98% &>= 90% 1 < 90% &>= 80% 2 < 80% 3



Page | 171


Helpdesk Performance 98% of the incidents within helpdesk resolution capacity shall be resolved in a cycle time of 24 hours Severity of Violation: High This service level will be monitored on a monthly basis.



< 98% &>= 90% 1 < 90% &>= 80% 2 < 80% 3


Helpdesk Performance 98% of the non SI supported incidents shall be routed to the appropriate service provider within 30 minutes. Severity of Violation: Medium This service level will be monitored on a monthly basis.



< 98% &>= 90% 1 < 90% &>= 80% 2 < 80% 3


Helpdesk Performance 80% of the Level 1 calls shall be resolved within 2 hours from call received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed8 business hours. Severity of Violation: High This service level will be monitored on a monthly basis.



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

In addition to the above, if the service level in any month in the six-month period falls below 60%, one (1) additional violation will be added for each


Page | 172


such month to the overall violations for this service level.

Helpdesk Performance 80% of the Level 2 calls shall be resolved within 6 hours from call received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 48 hours. Severity of Violation: High This service level will be monitored on a monthly basis.



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


Helpdesk Performance 80% of the Level 3 calls shall be reported on status and action to be communicated within 24 hours from call received /logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 72 hours. Severity of Violation: High This service level will be monitored on a monthly basis.



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


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

Datacenter Support Performance Up to date of the documentation of the design, modifications, enhancements, and fixes. Severity of Violation: Medium


Page | 173


This service level will be measured on a half-yearly basis. Each instance of non-meeting this service level will be treated as one (1) violation.

7. Reporting a) The below tables gives details on the Service Levels the SI should maintain for client

site systems availability.

Service Level Description Measurement Availability and Performance Report Provide monthly SLA compliance reports,

monitoring and maintenance related MIS reports by the 5th of the following month. Severity of Violation: Medium This service level will be monitored on a monthly basis. If the monthly SLA compliance report related to the service level metrics is not provided in the given timeframe, it will be treated as one (1) instance. The total number of instances for the six-month period will be the cumulative number of instances across all the months in the six-month period.

Total number of instances over the six month period


>0 &<=3 1 > 3 2

8. Credits for Successful Application Uptake The below tables gives details of the credits that can be gained by the SI for successful uptake of the application in the State, the credits will not be calculated for the first reporting period.

Service Level Description Measurement CCTNS Uptake The following metrics will be measured at the end of

each reporting period for each District that has been declared as “Go Live”: 1. Number of key transactions carried through internet(ex: Transactional such as submitting an application for a no-objection certificate and Informational such a requesting the status of a case) 2. Number of active users profiles in CCTNS 3. Number of read-write transactions on CCTNS system 4. Number of Searches carried out on data in CCTNS 5. Total number of FIRs prepared through CCTNS 6. Total number of Crime Details Forms prepared through CCTNS 7. Total number of Key Investigation Forms prepared through CCTNS


Page | 174


8. Total number of Arrest Cards prepared through CCTNS 9. Total number of Charge Sheets prepared through CCTNS 10.Quality (recency and accuracy) of information available in CCTNS 11. Number of cases reported to be solved because of the availability of CCTNS 12. Number of ad-hoc requests successfully responded to using CCTNS 13. Turnaround Time for submitting the monthly and annual crime/criminal information to NCRB from the State A credit will be gained for each of the above parameters if the uptake for that parameter shows significant improvement. The following table applies for each of the above parameters:

% increase over the measurement in the last reporting period

Credits

>5 &<=10% 2 >10 &<=15% 3 > 15% 4

9. Violations and Associated Penalties a) The primary intent of Penalties is to ensure that the system performs in accordance

with the defined service levels. Penalties are not meant to be punitive or, conversely, a vehicle for additional fees.

b) A six monthly performance evaluation will be conducted using the six monthly reporting periods of that period.

c) Penalty Calculations. The framework for Penalties, as a result of not meeting the Service Level Targets are as follows:

I. The performance will be measured for each of the defined service level metric

against the minimum / target service level requirements and the violations will be calculated accordingly.

II. The number of violations in the reporting period for each level of severity will be totaled and used for the calculation of Penalties.

a. If the total number of credits gained by the SI is lower than the total number of high severity violations in the reporting period, the total number of credits will be subtracted from the total number of High Severity Violations in the reporting period for the calculation of Penalties.

b. If the total number of credits gained by the SI is higher than the total number of high severity violations in the reporting period, the resultant total number of high severity violations in the reporting period for calculation of penalties will be considered as zero (0).

III. Penalties applicable for each of the high severity violations are two (2) % of respective half yearly payment to the SI.


Page | 175


IV. Penalties applicable for each of the medium severity violations are one (1%) of respective half yearly payment to the SI.

V. Penalties applicable for each of the low severity violations is half percentage (0.5%) of respective half yearly payment to the SI.

VI. Penalties applicable for not meeting a high (H) critical performance target in two consecutive half years on same criteria shall result in additional deduction of 5% of the respective half yearly payment to the SI. Penalty shall be applicable separately for each such high critical activity

VII. Penalties applicable for not meeting a medium (M) critical performance target in two consecutive half yearly periods on same criteria shall result in additional deduction of 3% of the respective half yearly payment to the SI. Penalty shall be applicable separately for each such medium critical activity

VIII. Penalties applicable for not meeting a low (L) critical performance target in two consecutive half yearly periods on same criteria shall result in additional deduction of 2% of the respective half yearly payment to the SI. Penalty shall be applicable separately for each such medium critical activity

IX. It is to be noted that if the overall penalty applicable for any of the review period during the currency of the contract exceeds 25% or if the overall penalty applicable for any of the successive half year periods during the currency of the contract is above 15%; then the state / UT shall have the right to terminate the contract.


Page | 176


ANNEXURE XI: FUNCTIONAL REQUIREMENT SPECFICATIONS

S.No FUNCTIONALITY Compliance (Yes/No/partial) Citizen Interface/Portal 1. Should allow user (citizens) to access portal via the internet to register

complaints online.

2 Should allow users (citizens/petitioners) to search for their request on the basis of Service Request number or petitioner details.

3 Should display petition/service request details and status on the screen based on the user search

4 Should allow users to save the status as a PDF file and/or print the status 5 Should allow the users to provide comments and feedback on online services 6 System should allow the user

1. To download all applicable forms as e-forms and submit the same System should provide the user to download forms for following services through the online portal 1. Complaint Registration 2. Tenant Verification 3. Servant Verification 4. Permission Request for Processions and Rallies 5. Application for Character Certificate Submit e-form once the user has connectivity

7 System should provide the user with an Online Help facility 1. Frequently Asked Questions on workflow of applications 2. User Manual on procedures to avail police services 3. Relevant police documents (library) 4. Address / contact nos. of police offices

8 System should provide the user with the following Transaction Services through the online portal 1. Complaint Registration 2. Tenant Verification 3. Servant Verification 4. Permission Request for Processions and Rallies 5. Passport Verification Status 6. Arm License Verification Status 7. Application for Character Certificate System should provide the user with the following representative Information Services through the online portal 1. Missing Persons Listing (with Photographs) 2. Proclaimed Offenders Listing 3. Stolen/ Recovered Vehicles Listing 4. Unidentified Dead bodies (with photographs) Listing 5. Abandoned / Unclaimed/recovered Properties Listing 6. Most Wanted Criminals Listing (with photographs)

9 System should allow the user to input the following details for complaint registration on the online portal (at least 2 should be mandatory) 1. Mobile Phone Number 2. Address 3. Identifications 3.1 Ration Card Number 3.2 Passport Number 3.3 Bank Account Number 3.4 Voter ID Card Number 3.5 PAN Number 3.6 Unique ID Number 3.7 Electricity Bill Number


Page | 177


3.8 Landline Telephone Number 3.9 Email ID

10 Should allow uploading of any relevant documents such as scanned documents/images

11 System should allow the user to view the time taken to process the service request (to monitor service delivery time) (Technically: system should keep a log of the start time of the registration of the complaint / general service request till such time that the status of the application is closed; system should display the user at the end of the service fulfillment, the total time taken to complete the service delivery)

12 System should provide an acknowledgement to the complainant (once the application has been submitted online) through 1. Mobile Phone (SMS) 2. Email 3. On Screen

13 System should allow the user to select their relevant (as per jurisdiction) police station from a list (in case the PS is known) System should forward the complaint to the relevant PS or appropriate authority based on address of the complainant (in case the PS is not known)

14 System should be able to record the IP address of user 15 System should change the case status depending on the progress of the

investigation.

16 System should allow the user to submit C-form to register foreigners 1. Provide for notices to foreigners (leave India notices) 2. Alerts to Interpol 3. Overstay checks and alerts 4. Alerts to immigration database (interface once created)

17 Should allow user (citizens) to view menu of services available 18 This page on the site should carry warning to the user

"User will be liable to be prosecuted for malicious complaint or content in accordance with the law in force"

Petition/Verification/Request Management Service 19 Should allow the user (police staff) to capture the general service petitions of

the citizens based on their request. The general service requests can be any of the following No Objection Certificates, verification of passport, service, tenant, servant, Lost cell phone, arms license, permissions for procession, rallies, mikes, etc. 1. Employee Verification 2. Tenant Verification 3. Servant Verification 4. Permission Request for Processions and Rallies 5. Passport Verification Status 6. Arm License Verification Status 7. Application for Character Certificate


21 Should present different templates/forms for different kinds of petitions/service/verification requests

22 Should allow the user to assign the petition to police personnel for preliminary enquiry and also forward it to other offices

23 Should allow the user based on the role to record notes/remarks to the petition.

24 Should allow the user to search the existing repository of previous cases/petitions/requests before responding to the petitioner.


Page | 178


25 Should allow for approval by the concerned officer before issuing the certificate.

26 Should provide the user to entrust / re-entrust the petition and close the petition

27 Should allow the user to generate the certificate or report or permission or the response to the petitioner

28 Should provide the reports and search capabilities on the petitions/requests 29 System should allow the user to search for cases and / or case details

registered in other police stations of same state and other states based on access rights

30 System should allow the user to view the antecedents of the person belonging to other states (in case a verification report has been prepared for a stranger)

31 System should forward a request for verification of a stranger (in case the permanent and present address are different) to the relevant police station (be it in a different state)

32 System should allow the user to receive online service request applications from other agencies (such as RPO) Passport Branch

33 System should dispatch the response of a petition / service request via 1. Email and/or 2. Post 3. SMS And update the status of the application in the system

34 System should generate an alert if no action is taken on a petition within 24 hrs (for complaint and FIR) and 7 days for general verifications, and sent to higher officers. If 24 hrs / 7 days time limit has been breached a non-compliance report should be generated automatically to all higher offices

35 System should allow multiple agencies to carry out verification concurrently such as passport verification by PS and by CID / district police office should be concurrent

36 System should allow to capture request for Foreigner - Registration Certificate - Registration Permit

37 Should allow the user to view timeline within which to resolve the issue (process step)

38 This page on the site should carry warning to the user he is liable to be prosecuted for malicious complaint or content in accordance with the law in force

Unclaimed/Abandoned property register service

39 Should allow the user to capture the unclaimed/abandoned property details. 40 Should allow uploading of any relevant documents such as scanned

documents/images and maintenance of online photo gallery/list of stolen/lost and abandoned property

41 Should present different templates/forms for different kinds of property (vehicles, cultural, fire arms, cell phones etc.,)

42 Should allow user to search the lost/stolen property in different case or different police station within the repository.

43 In case a match is found the system should link the unclaimed/abandoned property with the case

44 In case if the property wasn’t claimed for more than 6 months then the system should prompt & record the auction details after requisite approvals.

45 Should provide the reports and search capabilities on the unclaimed/abandoned property

46 System should enable users to view the photos and the details of auctioned


Page | 179


property

47 System should enable users to bid the auctioned property that is seized by police.

48 System should display the details of the arms and ammunitions recovered during the search operation

49 System should generate an alert for the concerned IO if the property seized is already involved in a crime

50 Should allow the user to view the details of the sale proceeds deposited in Govt. treasury once the property is auctioned off after requisite approvals (SHO and higher officers)

51 This page on the site should carry warning to the user that he is liable to be prosecuted for false claim of stolen or unclaimed properties in accordance with the law in force.

Complaint and FIR Management Service 52 System should allow the user to log the complaint details. The complaints

would be of different nature (Cognizable and Non-Cognizable, Missing Person, Stolen Property, Unidentified dead body, etc)

53 Should allow uploading of any relevant documents such as scanned documents/images in various formats

54 Should present different templates/forms for different kinds of complaints 55 Should allow the user to assign the complaint to police personnel for

preliminary enquiry

56 Should allow the user to record notes/remarks on the complaint. 57 Should allow the user to search the existing repository of previous complaints

before acting on the complaint.

58 Should allow for approval by the concerned officer before issuing the FIR. 59 Should provide the police personal to create the FIR/ NCR (Non-Cognizable

report)/ complaint report for other cases.

60 Should allow the user to transfer an FIR falling in other jurisdiction(zero FIR) 61 System should facilitate the closing of a complaint for those complaints which

do not proceed for investigation

62 System should allow the user to link/ de-link complaints 63 System should allow the user to merge complaints in case of duplicate

complaints or cross case

64 Should allow for complaints to be registered through the PCR Call Interface and Management Service.

65 Should present the station writer a dashboard with the report summary table consisting of new cases, court disposal, cases pending arrest, etc.

66 Should provide the reports and search capabilities on the complaints registered.

67 System should also allow the user to view crime and criminal data (as per the state specified formats)

68 System should display the name of the police station/ higher office where the compliant was originally registered

69 System should allow the user to edit the Act and Section for a registered FIR (an alert should be sent to higher office and judiciary) (only with alteration memo/ amended FIR)

70 System should allow the user to link Unidentified Dead Bodies with Missing Persons

71 System should allow the user to view a GIS map of the crime location (as soon as case is registered, with details of additional crimes committed in the same


Page | 180


area) 72 System should provide for automatic dispatch of notifications to Airports &

Seaports (ports of entry and exit) on criminal movements

73 System should allow the user to capture 1. Signature of the complainant (using a digital pen or paper scanner) 2. Thumb impression of the complainant (using a paper scanner) 3. Signature of the approving authority (using digital pen and paper scanner)

74 System should allow the user to send copies of the FIR to a distribution list through email

75 System should allow the user to create and forward special reports to DIG / IG Range, CID and DGP (in cases of heinous crime)

76 System should allow the user to link FIRs with MLCs/ Missing Persons/ Unnatural Deaths (since they can be converted into FIRs)

77 System should provide the following local heads (in addition to others) for FIR 1. Bag/ purse lifting 2. Theft by opening bag/purse 3. Theft by snatching bag/purse 4. Unlawful Assembly

78 System should provide for the following statuses for FIR 1. Pending Investigation 2. FR Submitted 3. Charge sheet Submitted with an alert sent to District Police Office/ Range DIG/ Zonal IG/ CID (CB) (in some category crimes)

79 System should allow the user to capture the 'Alias' of complainant, accused, witnesses etc. in the FIR

80 System should allow the user to capture Finger Print and Retina Scan for accused in FIR

81 System should generate an email to National Human Rights Commission within 24 hrs in case there is a custodial

82 System should allow the user to have information on 1. Hartals 2. All types of Agitations The investigation of such cases also to be viewed/ reported to DySP/ Assistant Commissioner and Narcotic Cell

83 System should allow the user to register cases of wild life crime, and send the report to CBCID HQ and to SIU XI Branch of CBI and Wild Life Bureau

84 System should provision for registration of cases under video piracy and a monthly report to be sent to AIG and DySP Crime Detachment on 1. Number of raids conducted in the District included in the raids conducted in Police Station limits 2. Cases registered with particulars of films, persons arrested Report to be sent before the 10th of every month .An alert on pending actions to be generated by the system

85 System should allow for auto transfer of cases registered as a crime against SC/ ST or POC Act to SP (will in turn align DySP for investigation)

86 System should allow the user to capture details on relatives of the Unknown Dead/ Injured Person (when traced) under 1. Name 2. Address 3. Contact Details 4. Statement

87 Should allow the user to see a complete list of templates of broad heads of crimes to file his compliant.

88 The page should clearly inform the user "This is an electronic mode of complaint for immediate response to crime


Page | 181


scene attendance or crime prevention and does not exclude the complainant to visit the police station to deliver a signed copy of the FIR and make his preliminary statement to the O.C"

89 The page should inform the user that after the FIR has been launched; all his subsequent information on line will not be termed 2nd FIR, 3rd FIR and so on.

90 Should allow the user to see the list of police stations with jurisdictional areas to file complaint in appropriate PS

91 Should allow the user to view the details in case his FIR or information has been routed to the PS having jurisdiction over his matter through an Inbox facility

92 The complaint passed from PCR can be acted upon by PS staff by registering compliant on suomoto basis depending upon the nature of the compliant otherwise PCR is not the FIR receiving window. Such information may be on display on dash boards of every officer in the PS and higher officers and not only on the dashboards of PS station writer

93 Provision to correct the 'spellings' of names needs to be updated after FIR. Since FIR once freezon these details cannot be changed, there should be a provision of correcting or updating the spellings in the subsequent forms

94 System should provide for capture of cases for Juveniles 1. Accused (sent to Juvenile Justice Board) 2. Victim (Children’s Court) 3. Witness (Children’s Court, Regular court - as appropriate)

95 Provision may be given to show the wings / units like Vigilance and Anti Corruption Bureau / CBCID in the FIR ,to be taken in context of entering data pertaining to an agency where the case is being transferred

PCR Call Interface and Management Service 96 System should allow users to register their complaints on IVR, based on the

nature of the complaint.

97 IVR should support multi languages. (English, Hindi, Urdu, kashmiri, Dogri).

98 System should generate the survey form with each call via email, SMS

99 System should arrange calls to be picked up in FIFO order

100 System should record all calls for internal audit and training purpose

101 System should generate an alert if the number already exists in the database as suspicious number.

102 System should generate unique identification number for each call and same should be maintained in the database for future reference

103 System should allow the user to answer /respond to the call through the user interface.

104 System should provide an interface to the Police Control Room (PCR) and Police Station users to capture the details of the complaint and the caller / complainant through a “quick capture complaint form” relevant for a complaint that is reported in through a phone call, email, walk-ins in emergency or a non-emergency situation. The system should also have the provision for recording the call along with the timestamp and capture in the system.


Page | 182


105 In case the caller reports a complaint that is within the jurisdiction of the PCR (either State HQ or District), the system should allow the user to identify the appropriate police station or available patrol vehicle and transfer the call to the same for response.

106 In case the caller reports a complaint that is outside the jurisdiction of the PCR (either State HQ or District HQ), the system should allow the user to transfer the calls to the appropriate police control room that has the jurisdiction.

107 The system should allow the user to record the details of complaint assignment and the action taken by the responder on the complaint.

108 System should allow the users to transfer PCR calls to relevant police station

Investigation Management Service 109 In case of NCR (Non Cognizable Report), the system should allow user to

capture the investigation details relevant to a non- cognizable offence and the approval from the court and prepare a final report for closure of the NCR

110 System should allow the user to generate an alteration memo and subsequently modify the acts and section details of the complaint.


112 System should allow the user to record and transfer a case that does not fall under jurisdiction of the present police station

113 Should present customized templates/forms for the type of complaint under investigation.

114 Should allow the user to assign the FIR to other police personnel.

115 Should allow the user to record notes/remarks on the complaint.

116 System should change the case status depending on the progress of the investigation.

117 System should allow the user to record the remarks on the status/case progress.

118 System should associate pre-defined tasks/ activities that are required during the investigation to the case. The tasks/ activities should be customizable by the administrator to the type of the case under investigation. The user should be able to add/ modify tasks/ activities to the pre-defined list associated with the case. The administrator should be able to add/ modify the super-set of tasks/ activities defined in the system and make them default to a type of the case.

119 Should allow the user to capture the details of the investigation relevant to the type of the complaint.


Page | 183


Indicative details captured during investigation are given below.

• Crime scene details

• Victims Details

• Accused Details

• Witness Details

• Property Details (stolen/seized)

• Evidence details

• Forensics details

• Medico Legal Case Details

• Other details in the crime details form

120 System should allow preview and printing of all the required forms (7 IIF’s, forms required for preparing the case diary and other forms necessary for submission to the external entities such as courts)

121 In case of death, system should allow the user to capture results conducted for inquest (whether person was hurt, details of clothing etc.,) and generate an inquest report.

122 System should capture the inquest report generated by the magistrate in case of death in police or judicial custody or death of lady within 7 years of marriage.

123 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.

124 System should provide the feature to capture the response in the form of parameterized data and scanned documents received from different external agencies.

125 System should allow the user to prepare, preview and print arrest card

126 System should allow user to capture the court surrender details

127 Should allow the user to capture the interrogation details as summary and parameterized data.

128 System should allow the user to capture the custody/remand details related to the decision of the court on the arrested that are produced before the court.

129 System should allow the user to view the detailed and summary views of the case


Page | 184


130 System should allow the user to prepare the final report (charge sheet/ challans, undetected, untraced, mistake of fact, civil nature). System should prompt the user with the list of documents required for filing a charge sheet.

131 System should allow the case to be re-opened and reassigned to a different investigating officer. In case of re-opening, the case history should be maintained.

132 System should also track the remarks/suggestions posted by higher officers /circle officers during investigation.

133 System should present to the IO, dashboard of under trials, under investigation, re-opened cases, etc and to other users based on their roles (IO) and their jurisdiction.

134 System should provide the dashboards to higher officials about the case progress and metrics about PT cases etc

135 System should allow the SSP & Senior Officers to view the summary of cases based type of case and cases falling in their jurisdiction

136 System should present the SHO & Senior officials about the details of the cases based on the status like open, closed, re-open, disposed, unresolved and case pending for trial.

137 Should provide the reports and search capabilities on the case progress.

138 System should allow the user to capture the finger print of an arrested person (through scanned image)

139 System should allow supervisory Officers to provide their instruction/remark mandatorily on progress report of Special Case Report (Heinous Crime) & voluntarily for Non-Heinous Crimes

140 System should allow the user to record details of the property released during investigation

141 System should allow the user to record details of partial recovery of properties during investigation

142 System should allow the user to record details of partial recovery of properties during investigation

143 System should allow the user to update the status of case property as

1. Released

2. Transferred

3. Sent to Police Station

4. Sent to Forensic Lab / Forensic Medicine Department


Page | 185


5. Sent to Court (as evidence)

144 System should allow the user to capture victim information under

1. Number of persons deceased

2. Number of persons seriously hurt

3. Number of persons with simple hurt

4. Number of non-injured persons

5. Gender

6. Age

7. SC / ST

8. Economic Strata

9. Educational Qualification

10. Nationality

11. Religion

12. Identity

13. Address

14. Contact Details (Telephone / Mobile / Email)

145 System should provide the user (investigating officer) with

1. Crime and criminal information 2. Address tracking of mobile users 3. Help book on investigating procedures through his/ her mobile phone

146 System should allow the user to record and print witness statements

147 System should allow the user to record and print Motor Vehicle Inspection Reports

148 System should allow the user to capture the case diary details (in a parameterized format)

149 System should provide for an alert to the user in cases where accused identity is not known, but

1. Similar case has been registered, where accused identity is found to be near description

2. Similar case is registered with same modus operandi

3. An arrest has been made in an another case with similar accused description


Page | 186


150 System should allow the user to take out print outs of witness statements at the time of charge sheet

151 System should send alerts in the below cases, to concerned District SPs and SP CID

1. Murder Cases where no significant progress is made even after 72 hours of investigation

2. In all murder cases in which the accused are not identified in FIR

3. Explosions in which more than one person is killed.

4. All cases of seizure of spirit in which the seized quantity exceeds 5000 liters.

5. All cases of seizure of Narcotic and Psychotropic Substances other than Ganja, except those where the quantity of the substance seized does not exceed the prescribed "minimum for personal consumption or small quantity".

6. Cases of theft of Government Arms and Ammunitions and theft or loss of Government property over `. 10 lakh.

7. All Women Trafficking Cases having interstate linkages.

8. Cases of Cheating or fraud by private financial institutions where the total transactions involved or the deposits collected by the accused exceed `. 2 Crores in that particular case or other cases of a similar nature involving the same accused.

9. Cases other than traffic accident cases in which Police Officers of and above the rank of CI figure as accused except petitions endorsed by Courts under Sec. 156(3) CrPC.

10. All counterfeit currency cases as per practice followed now in respect of such cases

152 System should prompt the police user with the list of documents and list if witnesses required for filing a charge sheet.

153 System should also track the action taken by the investigation officers on the remarks/suggestions posted by higher officers during investigation

154 The concerned police officer as user of the system only should be allowed to capture the details of investigation

155 Finger print should also be allowed to upload through an electronic reader and a photograph through a web cam

156 System should provide for the following during capture of physical features for a person

1. Pictorial diagram of a human should be displayed

2. Based on the mouse click on the picture various body parts and


Page | 187


characteristics should be displayed (based on NCRB code)

157 System should provide for digitization of Bad Characters Roll A - SHO of the PS will be required to enter the details of a bad character under surveillance (in case the person is in the same district) Bad Characters Roll B - SHO fills in the roll B in case the person moves out of the district

158 Investigation - Disclosure of the Accused person may reveal Co-accused For this purpose Section 82 and Section 83 of the CrPC may be referred System should provide for

- capture of details for co-accused

- Attachment of assets of the co-accused (absconder)

159 System should provide to add multiple entries under MLC report

160 System should provide to add multiple entries for 'Victims eligible for compensation' -would need to be flagged individually

Court and Jail interface & prosecution Management Service 161 System should allow the user to capture the charge sheet acknowledgement

details (interim and final) received from the court after the submission of the Charge Sheet.

162 System should allow the user to capture the summons/warrants issued by court.

163 System should allow the user to assign the summons/warrants to police personnel.

164 System should allow the user to record the status of execution on the summons/warrants.

165 In case accused applied for bail, system should allow the user to record the bail details

166 System should allow the user to capture the Trial update / Court disposal form. Indicative details captured during trial day of the case are given below

• Court Disposal Details

• Next hearing date

• Trial Status of the persons involved (Attendance, Examination, Bail Plea, Required for Next Hearing, etc)

• Bail

• Accused Status

• Court Order

167 System should allow the user to capture details if the convicted appeals in the


Page | 188


higher court.

168 System should allow the user to capture the status (granted re-trial, appeal denied) of the appeal

169 System should allow the user to capture jail / remand related information (release from jail, sent on judicial remand, sent to police custody …).

170 System should allow the user to manage and handle the split cases.

171 System should allow the user to proceed for re-investigation if ordered by the court.

172 The solution should provide the IO to view the tasks that he/she had set in calendar, the court appointments,

173 The system should allow the prisoner / suspect / arrested / convict / acquitted movements into and out of jails

174 System should present court constable with dashboard including court appointment schedule, summary of charge sheets, case disposed by court, summons and warrants, etc

175 System should allow the user to capture remarks of the Public Prosecutor before the finalization of the Charge Sheet

176 System should allow the user to capture details of

1. Witnesses

2. Witness statements

3. Next Trial date

4. Trial Outcomes/ Results

177 System should allow the user to capture details of the receipt of FIR from court

178 System should provide for preparation of calendar (daily, weekly, fortnightly) for cases scheduled for hearing

179 System should allow the user to generate report on disposal of cases in the prescribed format (state wise)

180 System should provide an alert to the SHO and IO on cases of 'impending expiry of remand period'

181 System should allow the user to capture details of accused who have escaped from custody and match the same with

1. Arrests made

2. Unidentified dead bodies


Page | 189


182 System should allow the user to know the status and monitor of summons / warrants issued to police stations outside their jurisdiction

183 System should allow for generation of alerts on unexecuted warrants

184 System should allow the user to capture details of attempts made for summon warrant execution

185 System should provide for

- Joint Trial

in court disposal form and in trial form

189 During court trial; in cases where

- Some of the charges under some specific sections are not proved there should be an option to capture the sections which are proved and which are not proved (against a particular accused)

190 Special Warrants - 'Type of Warrants' (for National / International Criminals)

- DW Warrant (Distress Warrant)

- BW Warrant (Bailable Warrant)

- Notices

- Red Corner Notice

- Blue Corner Notice

- Yellow Corner Notice

- Others

191 Trial details can be flexible & target can be set, which could mean that a Superior Court or High Court may fix a deadline to complete the trial, in which case, it should be reflected in the screens during the trial so as to keep reminding the concerned officer.

192 System should provide for Case Split

1. Under 'Trial Details' - capture data 'hearing date' wise

1.a Hyperlink dates

1.b Radio button to select split on a given hearing date

1.c Ability to select an accused to continue with parent case and others to continue with additional CC number

193 System should provide for 'Tracking of Appeal Cases'


Page | 190


194 System should provide for 'Change of IO'

1. In most of the cases IO can be changed or transferred

Crime and Criminal Records and Query Management Service 195 Should provide the user to search the repository based on FIR No, Beat area,

case category, date range and year/month/week. It should also provide the user to select multiple values for a single field.

196 Should provide the user a quick search for given case ID

197 System should also provide an advanced search capability and allow user filter the search to a greater detail like crime details, suspect details, victim details, modus operandi, property, victim, arrested, suspect, witness, guarantor/surety, habitual offender details, etc

198 The system should allow the user to configure/ build a query on the searchable data through query builders.

199 System should provide the ability to store, load and delete custom queries to each user for easy retrieval.

200 System should allow the user to organize the search results sort by clicking on table header

201 System should organize the search results in paged manner. It should also provide user the flexibility to navigate to the required page.

202 System should provide standard formats for the data from external sources (Vehicle Registration, Driver License, Phone (cell and land line from multiple providers) Numbers, Voter Details, Educational / Academic Certification Data) and a utility to capture the data into the investigation toolkit-data repository.

203 System should provide for capturing the updates or a complete feed of the external data and capture only the updates since the last feed in case of a complete data set is re-fed into the system.

204 System should maintain the history of data in case of modifications (ex, vehicle transferred to a new owner, an old cell phone number acquired by a new user,…)

206 In case the searched entity has a history of ownership, the same should be presented in the search results.

207 System should provide the user to export the search results in the format selected by the user like doc, pdf, xls, and spreadsheet in printer friendly format with page numbers printed on every page

208 If a user requests access to, or searches for, a case which he does not have the right to access, the System must provide one of the following responses (selectable at configuration time): display title and metadata; display the existence of a case but not its title or other metadata; Do not display any case


Page | 191


information or indicate its existence in any way. These options are presented in order of increasing security. Note that the requirement in the third option (i.e. the most stringent) implies that the System must not include such cases in any count of search results; this level of security is normally appropriate for cases dealing with matters such as national security.

209 If a user performs a quick or advanced search, the System must never include in the search result list any record which the user does not have the right to access.

210 System should provide the user with search hints / tips on data fields such as

1. Names

2. Locations

3. Objects

211 System should allow the user to match criminal records on the basis of

1. Finger Prints (to be done by FPBs)

2. Date of Birth (by IO)

3. Parentage (IO)

4. Modus Operandi (IO)

5. DNA (by Forensic Labs)

212 System should allow the user to conduct an advanced search based on sub parameters on a major data field

213 System should provide for similar features to a Soundex function for searches on

1. Names

2. Places

3. Objects

214 System should provide for the following additional options in the MLC register

1. Hit by train or Car

2. Crossing the road

3. By Crushing

215 System should allow the user to enter age of a new born child in 'Days'

216 The system should also enable to do advanced search on basis of the location parameter for which the names of places in the district under PS may be


Page | 192


located in the directory of locations.

217 The linkages should be provided in the system with the transport department, the office of the Dy Commissioner

218 The system should assist the IO with the modalities of investigation of specific crimes with reference to set procedures as per the CrPC and Special Acts.

219 The system should assist the IO and higher officers with court’s judgments to guide them in investigation

220 System should provide facility for automated correlation of 'missing / found / dead persons'

- will forward the correlated items to the queue of the officer who has registered the case

Police Email and Messaging Service 221 Should allow the user to create or import the organizational hierarchy and the

users of the police department.

222 Should allow the user to create or import the organizational hierarchy and the users of the police department.

223 Should allow the user to create or import the organizational hierarchy and the users of the police department.

224 Should allow the user to send messages to groups.

225 Should allow the user to send messages to groups.

226 Should allow the user to choose the option for read receipt

227 Should allow the user to search the messages from the archive based on message subject and between two dates

228 System should allow the user to choose the option of encrypting the message

229 System should allow the user to print the message in printer friendly format

230 System should allow the user to subscribe to alerts on cell phone in case of receiving a new email in the inbox.

231 System should show the usage statistics at all levels and departments.

232 System should enable users to send the signals(wireless messages) over internet

233 System should enable to use the messenger facilities within or across various police stations and Higher offices.

Periodic Crime and law & order reports and review Dashboards 234 System should present customized dashboards and reports to the users based


Page | 193


on their role -Duty Constable, Court Constable, Station Writer, IO, SHO, Circle Inspector, ACP, DCP, Sub-Divisional Officer, CP,SP, DIG,IG,DG, other higher officers in Administration

235 System should present various statistics such as summarized information, current progress, monthly numbers, comparative statements, trends with charting capability, exception reports, crime maps indicating the hot spots.

236 System should allow the user to view on alerts/events/reminders

237 System should present the user with statistics of all petitions

238 System should present the user with statistics on “Newly Registered complaints”

239 System should present the user with statistics on NCR’s (Non Cognizable cases)

240 System should present the user with statistics on FIRs with different statuses such as New/Under Investigation/ Pending Trial/ Re-opened

241 System should present the user with statistics on Warrants & Summons

242 System should present the user with court calendar which includes details on court appointment schedule, information on the cases under trial

243 System should present the user with activity calendar

244 System should present the user with statistics and list of “high priority FIR” (Grave /Heinous Crime Details)

245 System should present the user with list of Pending Arrests & Wanted Offenders/Suspects

246 System should present the user with statistics of charge sheets & Court Disposal

247 System should present the user with list of latest happenings across police stations such as missing persons & unidentified dead bodies

248 System should present the user with prisoner movement updates

249 System should present the user with Major and Minor head wise statistics

250 System should present the application usage statistics that provide indicators on the application uptake and usage by the police personnel

251 System should allow the user to drill down to a granular level to a complaint or suspect from the information presented in the dashboard.

252 System should provide the user an interface to enable the senior officers to conduct periodic reviews of the police station (citizen services, law & order, crime, etc)


Page | 194


253 System should allow the user to generate comparative statements of the above said statistics during monthly crime reviews.

254 System should allow the user to review the pending or overdue actions such as “filing a charge sheet within a defined time limit from the time of registering the case”, arrest of known accused etc.,

255 System should allow the user to create additional tasks / alerts / reminders on the actions items for investigating officers and track its progress in next monthly review.

256 System should consolidate and generate statistics based on the role and jurisdiction

257 System should allow the user to view a list of Active Criminals on the dashboard

258 System should allow the user to generate Daily/ Morning Situation Report

259 System should allow the user to generate report on

Number of criminals arrested during a day

260 System should allow the user to generate a crime chart with

1. Details on Cyber Crimes

2. Financial Frauds

261 System should allow the user to generate report (PS / IO / District wise) on

1. Number of pending cases

2. Number of cases where recovery happened

3. Number of cases where accused is identified and arrested

4. Number of cases where accused is identified and not arrested

5. Number of cases where charge sheet is pending

6. Number of cases pending due to response of external agencies like cases pending due to want of forensic report

262 System should allow the user to generate report on cases pending (with prosecution action awaited)

263 System should generate an alert in case the Case Diary is not handed over within 10 days of transfer

1. The act of the officer will be deemed to be an act of obstruction to further investigation and as an act of suppression of relevant evidentiary material SPs concerned may initiate action for such delinquency after evaluating the


Page | 195


circumstances of each individual case of non-compliance

Notification of Alerts, Important Events, Reminders and Activity Calendar or Tasks Service 264 System should automatically generate alerts (suspect in one case person or

wanted either because of pending warrants / summons apprehended / arrested in a different case, vehicle reported lost in one case is either recovered or found abandoned, dead body details captured in the system matches the details for a missing person reported in a different case, suspect in one case / person wanted either because of pending warrants / summons sent on remand or released in a different case, complaint of certain kind (attention diversion gangs) registered in a police station, in case a general petition for a procession or road work has been approved, an alert on the same well in advance to the affected police station(s), alerts in case an activity is pending for more than a week or an advance alert in case the stipulated time is about to expire (ex, police remand about to expire and the IO has to file for remand extension), a case coming up for trial where the IO has to be present as a witness, ….)

265 System should automatically generate reminders of any pending or overdue actions on the cases that are pending registration / investigation / trail.

266 System should allow the user to create and send user alerts / events / reminders to identified group / subscribed users / police stations.

267 System should allow the user to schedule the activities and maintain the calendar with reminders.

268 The alerts / events / reminders are either sent to the respective IO / SHO handling the case or in charge of the police station with the jurisdiction of the case.

269 The alerts / events / reminders should be available to be sent in the form of an email, or SMS to the registered phone or as an alert in the application once the user logs into the system or all available modes.

270 System should allow the user to generate alerts for SHO and IO in cases where a witness is used 'as a witness' in multiple cases (stock witnesses)

271 System should allow the user to generate alerts for IG / DIG / SSP / SP / SHOs officers where an FIR is registered against Naxal / Maoist / Terrorist / Insurgent Activities

272 System should generate an alert in case an Act and Section has been modified in for an FIR, and send it to DIG / SP / SDPO / DCP / ACP / CO

273 System should generate an alert for SHO, IO, SP every fortnight (after the arrest and judicial remand till charge sheet) and ' everyday for the last 7 days ', where a charge sheet needs to be filed for an accused who is in jail

274 System should allow the user to generate alerts for

1. Periodic progress of special report cases


Page | 196


2. Date of charge sheet of special report cases

275 System should generate an alert for an IO '3 days in advance' before bail hearing date

276 System should provide generation and transmission of SMS (to SP / DSP) on

1. Conviction Details

2. Summons / Warrants Details (if not served within the prescribed time limit / 3 days before the court date)

277 System should provide for generation and transmission of SMS (to all SHOs) on details of criminals released from Jail and for important criminal / offenders in sensational cases to SPs

278 System should generate alerts on

1. Court Case Hearing Date (to original PS (SHO) and concerned IO)

2. Charge Sheet Submission

3. Release and Parole Date

4. Bank Robberies, Dacoity (in other districts states) (to SPs)

5. Accused / Arrested (in other police stations as well)

6. Heinous Crime Case Details

7. Special Report (juvenile, scst, old age, etc)

8. Express FIR cases

9. Missing Persons

10. Stolen Vehicles

11. Unidentified Dead Bodies

12. Interstate Gang Operations

13. Firearms Stolen

15. Hue and Cry Notices

16. Terror Offences

17. State CID Instructions

18. Political Agitations

19 Filing Revision / Appeal / SLPs

20. Visit of VVIPs


Page | 197


279 System should generate an alert wherein a professional criminal is released from Jail and send the same to

1. Police Station of the resident area

2. Police Station of the area, where he / she has committed crime in the past

3. All police stations, where similar modus operandi has been reported in the state

280 System should have a Dictionary of common names and each time a new name is entered the master data for names should be updated. Also there should be a system generated alert when the user tries to enter a new name which is not there in the list of suggested names.

281 System should allow the IO to select an appropriate distribution list from a master list of email to send any alert

State-SCRB-NCRB Data Transfer and Management Service 282 Should extract the crime, criminals, and other related data or updates from the

previous extraction from States and UTs database at regular and pre-specified periods. The periodicity might differ from data group to data group.

283 The data extracted from J&K State must be transformed into standard formats required by NCRB.

284 The data should be run through a quality process to identify any possible duplicates or wrong data before sending to NCRB

285 Transformed and cleansed data must be uploaded on to NCRB databases

286 The system should provide the flexibility to cleanse and transform data

287 The system should support automatic extraction of data

288 System should provide an option to monitor and manage data extraction, Transformation and loading process

289 System should allow the user to kick start the load process manually in the absence of load failure

290 System should allow reconciling those records which failed during the load process.

State CAS Administration and Configuration Management Service 291 The solution should provide the user to customize the application without

affecting the core.

292 System should allow the user to change the look and feel like font, skins, images of the application

293 System should provide the flexibility in creating/modifying and deleting the user Hierarchy and should allow the admin to assign roles as proposed by


Page | 198


Districts, Ranges, Zones and police stations.

294 System should allow the user to define the organization all its units (police stations, districts, range, zone) and user hierarchy

295 System should present the data elements based on major and minor heads selected by user.

296 System should generate reports based on roles defined.

297 System should allow the user to add/modify/delete/modify-order of acts, sections and local laws.

298 System should provide the user to add/modify/delete/modify-order of property-type/castes/tribes details.

299 System should not allow the user to delete/modify/modify-order of the master data provided by the centre.

300 System should allow the user to maintain different templates as per the directive of local governments or standard guidelines, circulars, standing orders.

301 System should allow the user to maintain case specific service levels/time limits/measurable indicators for each step in the case progress from registration to investigation to trial.

302 A change in service levels/standards/benchmarks should be maintained/tracked by the system with start and end dates

303 A change in role/designation should be maintained/tracked with start and end dates

User Help and Assistance Service 304 The solution should provide detailed context-sensitive help material for all the

possible actions and scenarios on all user interfaces in the application.

305 The solution should provide context based help facilities and also on-line help at functions, screen and field level that can be customized by the State.

306 he solution should have comprehensive help facility wherein the users can obtain system specific technical / functional help online

307 The help should be accessible to the users both in the offline and online mode

308 The system should maintain and make available to user a database of frequently asked Questions

User Feedback Tracking and Resolution Service 309 The solution should provide an interface for the user to log any defects or

enhancement requests on the application and track thereafter.

310 The solution should send alerts (e.g., email, SMS) to the user if the user


Page | 199


chooses to whenever any action has been taken on the alert

311 The solution should enable the user to track the submitted defect or enhancement request.

312 The solution should enable the help-desk user to view the reports on the submitted defects or enhancement requests category-wise, status-wise, and age-wise

313 The support solution should be accessible to the users both from within the application and also outside the application through a different interface (ex, in case the CAS application is down).

Activity Log Tracking and Audit Service 314 An audit trail is a record of actions taken by either the user or the system

triggers. This includes actions taken by users or Administrators, or actions initiated automatically by the system as a result of system parameters. The System must keep an unalterable audit trail capable of automatically capturing and storing information about:

• All the actions (create/read/update/delete) that are taken upon the critical entities (case, suspect, property)

in the system

• The user initiating and or carrying out the action;

• The date and time of the event.

• Administrative parameters

The word “unalterable” is to mean that the audit trail data cannot be modified in any way or deleted by any user; it may be subject to re-department and copying to removable media if required, so long as its contents remain unchanged.

315 Once the audit trail functionality has been activated, the System must track events without manual intervention, and store in the audit trail information about them.

316 The System must maintain the audit trail for as long as required, which will be at least for the life of the case to which it refers.

317 The System must ensure that audit trail data is available for inspection on request, so that a specific event can be identified and all related data made accessible, and that this can be achieved by authorized external personnel who have little or no familiarity with the system.

318 The System must be able to export audit trails for specified cases (without affecting the audit trail stored by the System). This functionality can be used by external auditors, who wish to examine or analyze system activity.

319 The System must be able to capture, store and report violations (i.e. A user’s


Page | 200


attempts to access a case to which he is denied access), and (where violations can validly be attempted) attempted violations, of access control mechanisms.

320 The System must at a minimum be able to provide reports for actions on cases organized:

• By case;

• By user;

• In chronological sequence.

321 Any access to cases and all other activities involving the cases and related documents or data should also need to be stored in the audit trail to ensure legal admissibility and to assist in data recovery

User Access and Authorization Management Service 322 System should allow users to have specified access (read, write and execute)

323 System should allow user/Admin to modify the user profile’s (designations in case the officer is promoted to next level)

324 System should allow users to create new folders on the network with right access (read, write )

325 System should allow users to access network folders with valid user id and password.

326 The system must allow the user to create / update / delete user and user profile.

327 The System must allow the user to limit access to cases to specified users or user groups.

328 The system should provide for role-based control for the functionality within the system.

329 The System must allow a user to be a member of more than one group.

330 The System must allow changes to security attributes for groups or users (such as access rights, security level, privileges, password allocation and management) to be made only by super-user.

331 The System should allow a user to stipulate which other users or groups can access cases.

332 System should allow a maximum of three attempts to login.

333 System should allow the user to regenerate a lost password/reset password with set of hint questions

334 System should encrypt the user passwords


Page | 201


335 System should allow creation of new users, transfer of postings for existing users and any other actions that affect their authentication and authorization settings.

336 System should allow changes in roles/ authorization with the transfer / promotions of staff


Page | 202


S.No Functionality

Registration

Login

Login

General Petition

General Petition Services

Submit General Service Petition

Prepare Response for Service Petition


Maintain (Enter/Update/Delete) Unclaimed/Abandoned Property Information

Basic Complaints

Register Complaint

Complete Registration

Close complaint

Investigation

Crime Related

Capture Crime Details Form

Capture Chance Finger Prints

Capture Investigation Details

Prepare Remand Report or Judicial Custody Report

Prepare Arrest Card

Prepare Property Seizure Form

External Agencies Related

Prepare FPB/FSL/PME/MLC request form

Capture FPB/FSL/PME/MLC response reports

Prepare Inquest Report

Inquest Report Received from Magistrate

Transfer case to different PS or Agency

Reports

Prepare Final Report or Charge Sheet

External Agencies Related

IO Alerts for finishing a particular activity before the stipulated time

Alerts & MIS for senior officers

Reports

Prepare Final Report or Charge Sheet

Investigation

Help for IO


Page | 203


Help: View information on the support agencies

Help: View checklist related for a type of case

Support Services

Document Management

Generate Reports

Secure Access

Support Service

Prosecution

Court Interface

Submit Trial-Day Update

Split case in case of trial at different courts

Order for reinvestigation/investigation

Reports

Alerts & MIS for senior officers

Support Services

Document Management

Generate Reports

Secure Access

Support Service

Citizen Interface

Complaint Based Registration

Register Complaint and Receive Acknowledge

Query Based Interfacing

Conduct a Query


Apply for a NOC from the police

Status check on a NOC application

Provide general feedback/comments to the Police

Navigation

Case View

Multiple Case View

Home Pages

IO Home Page

SHO Home Page

Duty Officer’s Home Page

Court Constable’s Home Page

Station Writer’s Home Page


Page | 204


SSP & Senior Officer’s Home Page

Search

Quick Search

Advanced Search

Application Configuration

Admin Functions

Configure acts/sections

Configure additional data elements specific to the state acts/sections

Configure MO/Property-Types/Castes/Tribes

Configure Police Organization Structure (Districts, Ranges, Police Stations...)

Configure Courts/FSL/FPB

Configure Templates

Configure Case-specific Service Levels

Configure Users

Note: The Above mentioned modules in this RFP are indicative and SI is required to study the complete system, while

preparing the SRS document


Page | 205


ANNEXURE XII: INDICATIVE TECHNICAL SPECFICATIONS

Minimum Technical Specifications for Data Center and Recovery Center:

1) Enterprise Management System

SI shall procure and install EMS in the data centre for monitoring of the network.

• The EMS solution should monitor fault, availability and performance of network devices

across Management.

• Performance monitoring of network and server.

• Trouble ticketing systems

• EMS components should be from same OEM for out of the box seamless integration

capabilities

• EMS should be from ISO 27001 certified OEM. Bidder should provide necessary OEM

certificate.

Network Fault Management

The Network Fault Management consoles must provide web based topology map view

from a single central console. The system should provide discovery & inventory of

heterogeneous physical SNMP enabled network devices like Hubs (Layer 1), wireless (WAP)

devices, 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.

• Network Fault Management GUI should be Web-based providing views for Navigation,

Contents & Components Detail. Navigation view should provide views for Users, Locator

and Explorer search. Contents view should provide views for Alarm, Topology, List,

events. Components detail should provide Impact, Root cause, Host Configuration,

Interfaces & Alarms history information.

• The discovery should be able to identify and model router redundancy using vendor-

specific protocols (like VRRP and HSRP support for Cisco devices) so that alarms

generated from these virtual addresses are automatically excluded.

• The fault management should be able to discover MPLS links between MPLS routers for

isolating problems of link failure due to provider backbone failure or CE MPLS router

failure.


Page | 206


• The system must support multiple types of discovery like IP range discovery - including

built-in support for IPv6 ,Import data - from pre-formatted files (IPs, ranges, strings or

ports),Seed router based discovery - Using route tables and SNMP MIBs, Trap-Based

Discovery - whenever new devices are added with capability to exclude specific devices

based on IP addresses/ IP Address range

• The solution must use advanced root-cause analysis techniques. The system must

deduces the root cause of the problem and in topology it should visually pinpoint single

impacting device (in red color), as well as other impacted devices (in green color).

• The tool should provide sufficient reports pertaining to EMS. The tool should generate

necessary set of reports pertaining to Network Device Asset Inventory, alarms &

availability reports as well as a detailed network asset reports.

• The fault management web based console must provide tabs like topology, alarm,

interfaces, root cause tab in single GUI. It should provide explorer & search tabs as well

as configuration management as integral part of fault manager.

• The Fault management must provide Spotlight views for Router Redundancy, VLAN list

and VPN list. When clicked on a particular VLAN from VLAN List, participating devices

only for that particular VLAN gets highlighted in the topology map.

• The fault management should display connecting link between two devices and port

labels in same web GUI once clicked on a particular link. If there are multiple links

between two devices all the multiple links between two devices and their connected

port labels must be visible in same web GUI.

• Synchronized Discovery is required in order to reduce effort to discover devices again in

performance management engine. Devices once discovered in groups in Fault

Management should be imported directly into groups inside performance management

engine without a need to run separate discovery in performance management engine.

• The proposed NMS should provide unified workflow between the fault and performance

management systems including bi-directional and context-sensitive navigation, such as

o Navigate from the Topology View to At-a-Glance or Trend Reports for any asset

o Navigate from the Alarm View to At-a-Glance, Trend or Alarm Detail

• The system should provide capability to measure & report on response time for

common TCP/ IP applications using test on routers:


Page | 207


o HTTP, HTTPS, DNS, FTP, SMTP, SNMP, POP3, ICMP, Jitter

• The system should support secure device configuration capture and upload and thereby

detect inconsistent “running” and “startup” configurations.

• The proposed system should be able to administer configuration changes to network

elements by providing toolkits to automate the following administrative tasks of

effecting configuration changes to network elements like Capture running & startup

configuration, Upload configuration , Upload firmware , Write startup configuration.

• The proposed tool should display configuration changes differences in GUI showing

modified, remove, masked lined from last captured network configurations for routers

and switches. Also this should be able to identify which user has made changes or

modifications to device configurations through Fault Management Tool.

• 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 behaviors.

• The proposed service management system should provide a detailed business 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 system should 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.

• The system must be capable of managing IT resources in terms of the business services

they support, specify and monitor service obligations, and associate users/

Departments/ Organizations with the services they rely on and related Service/

Operational Level Agreements.


Page | 208


Secure Network Configuration Management

• The system should provide both window and web based consoles for accessing the EMS.

• The system should have web based interface with user id and password authentication.

• A user attempting to modify a device configuration from Network Operation Console

should be forced to choose from a list of users that have the “configuration change

approval” privilege to obtain approval from. The approver should be notified of the

request through email.

• The approver should be able to view the proposed configuration change and choose to

approve or deny from links within the email. The requester should be then notified by

email of the approval or denial.

Performance Management System

System should provide comprehensive end-to-end Network performance management

across key parts of the network infrastructure. The proposed Network Performance

Management System must provide the following features:

• The performance management should integrate with fault management to forward

performance alarms by defining notified rules and associated alarms shall be visible

against monitored device in fault manager console

• The system shall identify over-and under-utilized links and assist in maximizing the

utilization of current resources. The proposed system shall provide Performance of

Network devices like CPU, memory & buffers etc, LAN and WAN interfaces and

network segments.

• The proposed system must have a cognos based report authoring tool built-in which

will enable complete customization flexibility of performance reports for network

devices and monitored servers.

The tool should provide a live trend diagram displaying the various resource utilization

levels of various critical devices and links in the managed infrastructure.

The tool should provide a live exceptions list displaying the various health and threshold

exceptions that are occurring in the managed infrastructure.

The proposed system should use intelligent alarm de-duplication algorithms to learn the

behaviour of the network infrastructure components over a period of time.


Page | 209


The proposed system should be able to auto-calculate resource utilization baselines for

the entire managed systems and networks and allow user to set corresponding upper and

lower threshold limits.

Baseline setting should be as follows out-of-the-box:

• For a daily Health report, the baseline should be 6 weeks (42 days) by default.

• For a weekly Health report, the baseline should be 13 weeks by default (for a weekly

my Health report, it should be 6 weeks).

• For a monthly Health report, the baseline should be 12 months by default. The

Proposed Performance Management must provide following charts for all kinds of

Health Reports:

• Availability Chart ,Availability Chart (CIO Summary Report) Average Health Index

Chart ,Average Network Volume and Call Volume Charts, Avg. Response Chart

Bandwidth Utilization Chart, Element Variable Report Element Volume vs. Baseline

Chart, Exceptions Detail Report ,Exceptions Detail Table ,Exceptions Summary

Report, Failed Attempts Chart ,Health Index Change Leaders Chart ,Health Index

Leaders Chart , Jitter Chart ,Latency Chart , Network Interface Utilization Chart

Network Volume Chart, Paging Rate Chart ,Partition Utilization Chart etc.

• Performance Management mapping should match elements such as routers and

switches to corresponding models in Fault Management so that Fault Manager can

provide performance reporting options for the models in Network Operation

Console. Further element to model mapping should allow performance alarms to be

visible for the respective model in fault management Network Operation Console.

• Proposed performance management should be integrated with proposed fault

management using in built single sign on mechanism which should allow fault

manager users to access performance management user interface without a need to

re-login. SSO Users can be imported from LDAP directory or can be defined inside

SSO component.

Traffic analysis system should be deployable for optimum performance.

The solution should be of the type passive monitoring without a need to install any

probe or collector for data collection. The solution must provide the following flow based


Page | 210


metrics: Rate utilization, Byte count, Flow count, IP hosts with automatic DNS resolution, IP

conversation pairs with automatic DNS resolution, Router/ Interface with automatic DNS

SNMP name resolution, protocol breakdown by host, link, TOS or conversation, Utilization

by bit pattern, matching of the TCP ToS field, AS number, BGP next hop address, IPv6

address.

The network traffic analysis system must be from same OEM providing Network Fault &

Performance Management System for seamless integration.

The proposed traffic analysis system should provide visibility into new and unknown

traffic patterns which is critical for ensuring the performance of networked applications, as

well as identifying security risks. It should provide real-time analysis of traffic behaviour for

every client and server in infrastructure to help ensure network delivers application services

reliably and securely.

Traffic Analysis System must provide Search for any traffic using a specific configurable

destination port, or port range, autonomous system (AS) number, BGP next hop IP address,

ToS bit, clients or servers that are experiencing more than a specified number of TCP resets

per hour, IPv4 or IPv6 conversation bad IP Header, unreachable destination, TTL expired,

trace route requests, MAC addresses, TCP flags, VLAN.

The proposed solution must keep and report on unique hosts and conversations per day

for each monitored interface

The proposed tool must provide availability and performance for server nodes and

deliver scalable, real-time management of critical systems.

The proposed tool should be able to monitor various operating system parameters such

as processors, memory, files, processes, file systems, log files ,daemons etc. It should be

possible to configure and define thresholds for warning/critical states and escalate events

to event console of enterprise management system.

The proposed tool should integrate with network performance management system and

support operating system monitoring for various platforms including Windows, LINUX/

UNIX, and LINUX/ LINUX/ UNIX.

Proposed solution should provide light weight monitoring agents reporting to network

performance server.


Page | 211


Application Performance Management

System should determine if the root cause of performance issues could be inside the

monitored application, in connected back-end systems or give indications about problems

at the network layer from a single console view.

System should monitor .NET/ Java based applications.

System should proactively monitor 100% of real user transactions 24x7 identifying the

user name and IP address; detect failed transactions; gather evidence necessary for triage

and diagnosis of problems that affect user experiences and prevent completion of critical

business processes.

System must have ability to monitor transactions that include XML, SOAP and other

identifiable protocols over HTTP/S.

System must be able to monitor complex web pages comprised of multiple components

like frames, Java-script, images, and other HTTP components.

System must be able to combine multiple transactions into a logical business process.

System should monitor end-to-end, REAL user transactions

System should not allow end users to install/upload software on to their desktops.

System should provide for self-monitoring of internal health with reports pages and

alerts on errors or issues.

System should have provision for automatic transaction discovery, for example by

setting up some bounding parameters to describe transactions like the web site, the

language, and parameters (such as post, query, and cookies).

System must support monitoring on:

• Transactional level

• Business Process level

• User and User group level

System shall be capable of real-time detection of errors and performance problems that

affect the ability of customers to execute successful transactions, thus able to proactively

identify errors and problems customers are experiencing and enable trouble shooting to

begin before an increasing number of customers are impacted and call for support.

The management reports from the solution allows viewing the details for each defect

and aggregate like defects into an incident, and also provides the ability to quickly see


Page | 212


commonality across defects while still providing the ability to drill down to view the metrics

for a specific defect.

System should be able to see exactly what request was sent by the end users' browser

sent and the response by the application, when a defect occurs.

System must be able to provide root-cause probability graphs for performance

problems showing the most probable root-cause area within application infrastructure.

System must quickly create a baseline for performance over a period of time from the

live production application.

System must have ability to automatically generate and distribute PDF formatted

reports via email on a daily, weekly, or monthly basis.

System must be able to provide the ability to create user groups based on location/

geographic area.

System must have ability to create user groups based on URL string, cookie value, XML

attribute, IP Addresses or HTTP header

System must be able to extract data from Http request header and body to assist in

identifying transactions or extract user, session and other parameters.

Solution should generate a graphical map of the complex transactions showing the path

of the transaction across multiple application components. Map view should also highlight

any triage to enable quick identification of the problem.

System must provide ability to monitor performance of applications going up to the

method level of execution (Java/ .Net method) 24x7 in production environments with

negligible impact on monitored application (minimum overhead).

All application stakeholders (i.e. DBA, Operations, and Application developers) must get

performance data pertaining to their specific areas from single Java/ .NET Application Agent

within the application server and be able to display them on dashboards.


Page | 213


Helpdesk Management

The proposed ITIL-based Helpdesk Management System must provide the following

features:

• The proposed helpdesk solution must provide flexibility of logging, viewing,

updating and closing incident manually via web interface. The web interface

console would also offer power-users tips.

• The proposed helpdesk solution must support all ITILv3 processes like request

management, problem management, configuration management and change order

management with out-of-the-box templates for various ITIL service support

processes. Bidder should provide ITIL v3 certification letter on all processes.

• Each incident must be able to associate multiple activity logs entries via manual

update or automatic update from other enterprise management tools.

• The proposed helpdesk solution must be able to provide flexibility of incident

assignment based on the workload, category, location etc.

• Each escalation policy must allow easy definition on multiple escalation levels and

notification to different personnel via window GUI/ console with no or minimum

programming.

• The proposed helpdesk knowledge tools solution must provide grouping access on

different security knowledge articles for different group of users.

• The proposed helpdesk solution must have an updateable knowledge base for

technical analysis and further help end-users to search solutions for previously

solved issues.

• The proposed helpdesk solution must support tracking of SLA (service level

agreements) for call requests within the help desk through service types.

• The proposed helpdesk solution must be capable of assigning call requests to techal

staff manually as well as automatically based on predefined rules, and should

support notification and escalation over email, web etc.

• The proposed helpdesk solution must integrate tightly with the Knowledge tools

and CMDB and should be accessible from the same login window.

• The proposed helpdesk solution must have a built-in workflow engine. The

proposed helpdesk solution must support Non-linear workflows with decision


Page | 214


based branching and the ability to perform parallel processing. It should also have a

graphical workflow designer with drag & drop feature for workflow creation and

updates.

• It should support remote management for end-user & allow analysts to do the

desktop sharing for any system located anywhere, just connected to internet.

• Web based remote desktop management feature should be supported as part of

helpdesk troubleshooting

• It should allow IT team to create solution & make them available on the end – user

login window for the most common requests.

EMS integration with Helpdesk:

When certain user tries to make any change on network device through fault

management console a helpdesk ticket should be generated automatically. The Service Desk

operator must have the ability to view the proposed configuration change once the ticket is

approved the user is automatically notified and is able to proceed with the change.

The proposed Fault Management Solution must support integration with proposed help

desk or trouble ticketing system such that integration should Associates alarms with Service

Desk tickets in the following ways:

• Manually creates tickets when requested by Fault Management GUI operators

• Automatically creates tickets based on alarm type

• Provides a link to directly launch a Service Desk view of a particular ticket created by

alarm from within the Network Operation console.

• Maintains the consistency of the following information that is shared between alarm

and its associated Service Desk ticket including status of alarms and associated

tickets and current assignee assigned to tickets.

Helpdesk ticket number created for associated alarm should be visible inside Network

Operation Console .It should be integrated in a way that Helpdesk incident can be launched

once clicked on ticket number for associated alarm from within Network Operation Console.

The proposed network fault management system should integrate with the helpdesk

system by updating the Asset with CI information to support viewing history or open issues

in helpdesk on the particular managed asset and associate an SLA to the ticket in the


Page | 215


helpdesk. The proposed network fault management system should 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.NMS console must show

associated helpdesk ticket number for the alarms that generated those tickets.

SLA’s violation on monitored end user response time must open a helpdesk incident out

of the box.

Proposed performance management system and traffic analysis system must integrate

through common network performance portal depicting drill down performance views on

performance utilization and type of traffic flowing through monitored interface.

Identity & Access Management

Requirements for the Identity and Access Management System

The Identity and Access Management Solution consisting of Identity Management,

Provisioning, Password Management, Web Access Management, Web SSO, and Single Sign-

On for thick client applications and Server Access Control must be from a single OEM to

enable smooth and easy out-of-the-box integration among the various sub components.

The bidder shall provide undertaking by OEM of Identity and Access Management

Solution whose software products have been offered for associating Project Manager

during the project execution period.

The proposed Server Access Control Solution should be able to protect critical server

infrastructure and minimize security risks by regulating access to confidential data and

mission critical services. The solution should provide policy-based control of who can access

specific systems, what they can do within them, and when they are allowed access.

Specifically, it should proactively secure access to data and applications located on Linux,

UNIX and Windows system servers throughout the infrastructure.


Page | 216


Server Access Control

The Host Access Control should be able to protect business critical infrastructure and

minimizes security risks by regulating access to confidential business data and mission

critical services. The solution should provide policy-based control of who can access specific

systems, what they can do within them, and when they are allowed access.

Host based security solution must allow controlling of access to system resources

including data files, devices, processes/daemons and audit files.

• The solution should Self-protect itself – Must be able to prevent hackers with root

access from circumventing or shutting down the security engine. Must use a self-

protected database for storing all security information.

• The solution should provide Rights Delegation - Must provide the ability to designate

specific users as Administrators, Auditors, and Password Managers etc with

appropriate rights. Must also provide the ability to designate specific users as

Subordinate or Group Administrators, to manage users and file permissions for their

Group

• The solution should support cross platform Management – Must support

management and policy distribution across Windows, Linux and UNIX platforms

from a central management console. It must support the deployment of the same

policies across multiple servers ensuring consistency of security policies across

machines in the enterprise.

• The solution must provide capability to allow access to sensitive resources only

through approved programs.

• Administrators must be able to define critical files that are not supposed to change.

If these files are modified, the process that checks the sensitive files must find that

the files have changed and write an audit record.

• The solution should allow protection of files on even non-NTFS file systems like FAT

and CDFS.

• The solution must provide support for IPv6 and FIPS140-2 and must provide Services

and Registry Values Protection on Windows

• The solution must provide administrative password checkout function. It should

provide workflow for requesting and checking out a system-generated. The solution


Page | 217


should provide the functionality to force the user to check the password in once

their task is completed, or PUPM should provide the capability to be configured to

automatically check the password in after a specific time period; and it can be a

manually forced check in as well.

• The privilege user password management (PUPM) must provide a fully functional

and customizable workflow that provides common out-of-the-box use cases for

PUPM. The solution must provide a break glass feature. A break glass scenario

occurs when a privileged user needs immediate access to an account that they are

not authorized to manage. Break glass accounts are privileged accounts that are not

assigned to the user according to their role. However, the user can obtain the

account password immediately, without approval, if the need arises. This eliminates

the possibility of a delay for an admin to approve the request. All transactions

related to the break glass scenario must securely be logged for audit purposes.

• The solution should provide a feature to eliminate passwords from scripts. Via

PUPM, it should be possible to replace hard-coded passwords in scripts with

privileged account passwords that are generated by PUPM only when needed.

• The solution should provide a unified web based console which consolidates all

aspects of privileged user management under a single console — host access control

and privileged user management across physical and virtual systems, devices and

applications.

• The PUPM must support a wide range of virtualization platforms including but not

limited to: VMware ESX, Solaris 10 Zones, LDOMs, Microsoft Hyper-v, IBM VIO, AIX

LPAR, HP-UX VPAR, Linux Xen and Mainframe x/VM, providing for more consistent

security management of access control risks across these virtual partitions, in

addition to physical platforms.

Web Access Management and Web Single Sign-On

The Web Access Management solution should provide a secure access to business

content, applications, and information across its organization, while allowing management

of multiple user communities across the organization.

The proposed web access security management solution:


Page | 218


• Must include out-of-the-box support for specified relevant third-party technologies -

Authentication, PKI, and smart cards.

• Must provide access to only those applications/ resources that the user/ customer

has authority to.

• Must not have an agent installed on application, database or directory servers

where users need to be provisioned.

• Must be able to integrate with user administration product

• Web access management system itself should use 128-bit RC4encryption between

its distributed components.

• Solution must support all following authentication method: Passwords, Two factor

tokens, X.509 certificates, Passwords over SSL, Smart cards ,Combination of methods

,Forms-based ,Custom methods ,Full CRL & OCSP support

• Web access management system should support off-line generation and

management of encryption keys using N cipher with the strength (size of encryption

key) of the encryption algorithms of 128-bit RC4

• Strong authentication (such as the use of a smart card) should be required to access

certain administrator functions

• Web access management system should support single sign-on across security

domains.

• If a user is authenticated at a low level of security (e.g., password), then they should

be forced to re-authenticate when they attempt to access a more sensitive resource

(e.g., one protected by a token card).

• The priority of these authentication methods should be Administrator specified .It

should not be hard-wired into the product, and Administrator should be able to

control the priority of each Authentication method. 1000 levels of priority should be

supported.

• Solution should support both session and idle timeouts on a per-resource basis.

• Administrator should be able to specify rules for generating and rolling over

encryption keys (e.g., periodically, or upon command).

• Authentication management system should be capable of supporting automated

fallback to alternative authentication systems.


Page | 219


• Solution should support directory chaining.

• Solution should provide protection from cross-site scripting & SQL Injection attacks.

• Solution should support time or location-based policies.

• Administrator should be able to create a policy for any user, any group (including

dynamic groups), any role, or even any ad-hoc set of users who share certain

attributes.

• Administrator should be able to integrate dynamic/ external data (at run-time) in

the enforcement of my policies via a Web service.

• Solution should support controlled “impersonation” of users allowing certain users

to temporarily use the entitlements of other users without sharing of passwords.

• Solution should support fine-grained control of access to file, page, or objects.

• Solution should support full replication of all components.

• Solution should support automatic failover and Failover between clusters

• Solution should support 4 & 8-way SMP servers.

• Solution should do dynamic load balancing across all servers.

• Solution should also load balance across directories.

• Solution should provide “2nd-level caching”, so that recently used policies are

separated out into a separate cache. And these caches should be tunable for each

environment; also the caches should be either flushed or refreshed on administrator

command.

• Solution should work with existing user directory.

• API should support workflow capabilities.

• There should be an API to allow custom directories to be used for user storage.

• Must log users into any resource requiring a sign-on which includes client server

applications, email, databases applications and Web enabled applications. The

solution must provide capabilities to manage all environments from access

management perspective.

• Integration between Web SSO and enterprise SSO should be out of the box.


Page | 220


Role, Compliance and Identity Management

• The proposed solution should allow efficiently sort through extremely large volumes of

user and privilege information to quickly discover potential roles.

• The proposed solution should provide a clean set of user entitlement data to support

role management efforts.

• The proposed solution should periodically validate that users, roles or resources have

appropriate access rights to meet compliance requirements.

• The proposed solution should provide role custodians or resource owners to view the

current entitlements of their respective entities, then certify that they are appropriate

or identify privileges that should be removed.

• The proposed solution should provide a centralized engine that establish and enforce a

consistent set of identity compliance policies to minimize security risk.

• The proposed solution should prevent Identity vulnerabilities using consistent identity

compliance policy enforcement.

• The Solution should have built-in reputed reporting engine such as Business Objects,

etc.

• Must provide centralized administration of user-ids and password management.

• Must provide a central directory of users, their real-world business information, their

accounts, and their access rights across the enterprise without requiring changes to end-

systems.

• Must allow accounts on end-systems to be discovered, and linked to users within the

administration utility, which can be subsequently used as the single point of

administration.

• Cross Platform/ Application - Must provide easy and cost-efficient administration of

users and resources across enterprise security systems and directories like NT, UNIX,

Microsoft Exchange and others specified.

• Scalable - Must be scalable, open, extensible, and built around standards-based LDAP/

X.500 technology.

• Audit - Must provide a consolidated audit trail of administrative operations.

• Other Requirements


Page | 221


• Must have APIs to enable additional user management operations on UNIX, NT over and

above the default operating system account set-up.

• Must have LDAP interface to enable queries/ updates by authorized third-party

customer tools.

• Must support enforcement of a centrally-defined security policy, e.g. for access rights,

user names, password lengths

• Role-based Administration

• Role Based & Rule Based User Provisioning.

• Must provide access rights based on job function to support implementation of role-

based administration.

• Must have a web-interface for simplified user administration that can be used by HR,

business managers to introduce and delete users, and assign them to job functions

• Should be able to integrate with HR application, CRM application so as to enable

creation of user ids based on data fed to CRM and HR applications.

• Must allow users to access critical data through a single, secure login, while reducing

security/ password administration.

• Should have an embedded work flow which would help in automating routine tedious

tasks like approval processes.

• Must provide advanced Web support, to allow for smooth access and personalization of

the user interface for each user. Once a user has been authenticated to the sign on

system, access to all authorized Web applications and resources must be handled by this

system.

• Must be easy to deploy and maintain.

• Must work across specified platforms, databases, and applications.

• Must include out-of-the-box support for specified relevant third-party technologies -

Authentication, PKI, and smart cards.

• Must have a highly scalable architecture.

• Must allow incremental implementations.

• Must provide access to only those applications/ resources that the user/ customer has

authority to.

• Must be able to integrate with user administration product.


Page | 222


• Provide capabilities to perform recertification of identities across the Enterprise.

• Perform Identity Auditing for entitlement violations and validations.

• Out-of-Box integration with Web Services.

• Should provide capabilities to have Corporate Directory as well as Provisioning

Directory.

Security Log Record Collection & Management

• The system shall provide a graphical user interface/ wizard to rules for normalizing

custom log sources or modifying existing integrations

• The system shall provide automated update mechanism for Content (product

integrations and reports). This process shall occur seamlessly and transparently without

any customer intervention as part of the subscription update process.

• "The system shall support the following methods for log collection :

• Windows Management Instrumentation, Syslog, Open Database Connectivity (ODBC),

Text Log (flat file), Open Platform for Security (OPSEC)"

• The system shall provide a mechanism to monitor the current status and relative health

of the logging infrastructure.

• The system shall have the capability to drag and drop building of custom queries &

reports

• The system shall have the capability for updates delivered and applied via an update

service provided by the vendor to keep the system up-to-date. This includes the agents

and it should be pushed centrally without having to reinstall the agents.

• The system shall have a secure and preferably embedded log repository to store logs

that does not require separate database expertise to administer and manage.


Page | 223


Data Loss Protection

• The solution should protect against all relevant user activity including use of a Web

browser, e mail, launching applications or installers, printing documents and copying

files to removable media such as a USB thumb drive. The solution should use

application and device names along with full content inspection to leverage identity,

context and concepts to accurately evaluate user activity while reducing unwanted

alerts.

• The solution should perform an unlimited number of tasks, each with its own set of

defined local or remote scanning locations. Tasks can be executed on-demand or during

scheduled times. The solution should deploy entirely within the file server, repository or

collaboration server, or deploy as a remote scanning server. The highly scalable and

distributed architecture allows data to be scanned at rates exceeding 500GB per hour.

Once sensitive information is discovered, it can be deleted, copied or moved to another

location. Source files can even be replaced with a stub file of the same name containing

an informational message. Also, source document properties can be set to specific

values for use in downstream analysis and control.

• The solution should exclude known application program files which are positively

identified from the National Software Reference Library (NSRL) maintained by the US

National Institute of Science and Technology (NIST). The solution should provide deep

content inspection with the ability to leverage identity, context and concepts within

detection methods, reduce the possibility of tagging a document incorrectly and ensures

that all potential threats are controlled.

• The solution should protect and control messages that are sent within the organization

and accessed by Web e-mail applications and mobile devices such as Blackberry and

Treo. The solution should provide direct Exchange and Lotus integration and not just

scanning of logs and libraries. E-mail integration provides superior filtering of e-mails

and reduces internal e-mail information risks.

• The solution should take the right action once a violation is found. The message can be

blocked, quarantined, encrypted or ingested for monitoring and review. Additionally the

user should be warned or informed that the message they are about to send is in


Page | 224


violation of policies. The solution should prevent users from inadvertently sending

personally identifiable information via OWA or iNotes

Web Server: • Web Server (Container to execute the presentation logic)

• The web server should be capable of supporting clustering.

• All components of the web server should be based on standards and selected such as to

provide ease of management and to avoid compatibility issues.

• All web server components must be maintainable with an ease such that corrective and

preventive maintenance can be performed on the system without affecting the entire

working of system.

• All the web server components must be capable of being managed from a remote

management station and provide information on performance parameters

Application Server: • Application Server should be fully standards compliant providing support for Web

Services, SOAP, WSDL, UDDI, LDAP v3, SSL v3, XML 1.0 and equivalent standards.

• Provide comprehensive XML support compliant with the W3C XML standards and

contain the basic building blocks to XML-enable applications –including reading,

manipulating, transforming and viewing XML documents.

• Support developing, publishing and consuming web services • Support wireless enabled web sites and portals • The application server should be capable of supporting clustering. • All components of the application server should be based on standards and selected

such as to provide ease of management and to avoid compatibility issues • All application server components must be maintainable with an ease such that

corrective and preventive maintenance can be performed on the system without affecting the entire working of system.

• All the application server components must be capable of being managed from a remote management station and provide information on performance parameters.

Database • The database should address all the structured and un-structured data storage

requirements of the proposed system • The RDBMS database should have a high tolerance of failure • The underlying database should support 24x7 high availability • The database should provide horizontal scalability, by adding additional servers for the

same database without any downtime • The data scalability and manageability should be integral part functionality of the

database.


Page | 225


• The database should provide enterprise class web management tools for management and maintenance of databases even from remote places

• The database should support native automated disaster recovery capability without any third party support using cost effective option of automatically synchronizing the transaction logs to disaster site, which in case of fail over the other node provides the availability of all data. This flexibility of log synchronization should be supported from Enterprise to Entry Level server edition of the database

• The database should be capable to support plug and play data transfer across platforms or operating systems

• The database should be able to support various types of content like Texts, Images, Multi-media, Spatial and XML content natively

• The database should ensure data synchronization between database servers on near real-time basis by capturing messages at the source database, stage messages in a queue, propagate messages from one queue at the source to another queue at the target and consuming messages

• The database should support both way data synchronization across database servers in one-to-many and many-to-one situations and automatically detect data conflicts and resolve the same as per predefined conflict resolution algorithms

• The database should support data synchronization across database servers in heterogeneous platforms

• The database should be capable to deploy fine-grained access control, separation and segregation of duties and native encryption capabilities. The database should also prevent access to sensitive application data by highly privileged users.

• The database should control access to the applications, databases and data with flexible security controls.

• The solution should provide options or utility to encrypt/decrypt sensitive data • The solution should support data export and import facility to variety of databases and

other software packages • The solution should provide backup (hot & cold) and recovery facility • The solution should be able to schedule a backup/restore task • The solution should be compatible with 3rd party system monitoring package. • The solution should support selective encryption of the stored data • The database should support a single unified data model hosted on a single database. • The database design & architecture should be in line with the functional and

nonfunctional requirements of the proposed system • The database should be highly available with every processing node providing full view

of data. This means, in case of failure of one server, each remaining server in the cluster should provide full access to all data at any point in time

• It should support clustering exploiting rapidly emerging disk storage and interconnect technologies

• It should provide automated disaster recovery solution to maintain transaction consistency, providing an option of zero data loss where required

• It should provide restrictive data access that enables different types of users to have secure, direct access to mission-critical data sharing


Page | 226


• It should control data access down to the row-level (row-level security) so that multiple communities of users with varying access privileges can share data within the same database

• It should provide encryption capabilities while transferring data over networks • It should possess ability to encrypt data stored in the database at the column level • It should provide Public Key Infrastructure (PKI) support • It should provide support for comprehensive auditing for ‘inserts’, ‘deletes’, ‘updates’

and ‘selects’, and quickly spot and respond to security breaches • It should store XML content native to database • It should have the ability to index, search, and analyze text and documents stored in

database • It should support different partitioning schemes to split large volumes of data into

separate pieces or 'partitions' which can be managed independently • A centrally Monitored Based GUI Administration Tool should be available with the

RDBMS to Create, Delete & Manipulate different Database Objects and also Schedule Queries priorities centrally.

• Server Configuration Tools be available to automatically configure clients, network etc. • Database should have received the security certification (EAL) such as International • Database should support industry standard TPC benchmark or Equivalent. • The database software should provide the following capabilities: • Advanced Web Based Reporting Services • Data warehousing and Analysis Services • Business Intelligence • Complete ETL functionality • Performance Management Tools • Clustering Tools • Tuning and Diagnostics Tools • Spatial Database Capabilities • Database Compression and Encryption Tools • Replication Technologies for Failover to Remote Sites. • All the above functionalities should support scalable and high available functionality. DBMS ETL Tool Capabilities: • ETL Should support Import and Export Wizard and supporting connections, source and

destination adapters, and tasks • ETL Should support performing persistent lookups, Data Profiling; Should support fuzzy

lookups and fuzzy search • The ETL tool should provide for integrating data from various relational or non relational

sources. The tool should provide native access interface to the following PC Files – Spreadsheets, Flat Files, DBF, etc.

• The ETL tool should be rich in the set of in-built transformations and functions. • The tool should provide at least 50 in-built transformation functions. • Should support Central Management of Replications, Fine grained scheduling of data

replication, Scale out of replication architecture, Capability for both Push and Pull Replications


Page | 227


DBMS reporting capabilities: • Should provide facilities to Create, Design, Generate & manage the reports. • Should support Visualization tools such as maps, gauges, and charts • Should support for remote and non-relational data sources • Should have centralized reporting functionality that gives users a single place for

locating the latest reports, spreadsheets, or key performance indicators. • Should Provide Reporting which can be published through a variety of mediums like web

application, client application, mail, ftp folder, mobile handhelds etc. • Should support multiple formats like html, PDF, XML, CSV, etc. and other custom

formats as out of the box. • Should provide customization features for reporting where user can filter on various

parameters to be reported on the screen. • Should allow administrators to create reporting boundaries (without programming)

using which adhoc reporting can be done by end users. • Should allow Creation of filters to control data displayed on a report. And allow

Parameters passing to the reports at run- time. • Should provide Offline viewing of previously created Reporting results.

2) Server Load Balancer

• 10/ 100/ 1000Mbps Ethernet Ports – minimum 2 ports upgradeable to 4 ports • Memory: Minimum 4 GB • Minimum of 2 Gbps throughput • Minimum of 1 Gbps SSL throughput • Minimum of 4000 SSL connections scalable to 7500 SSL connections • Server Load Balancing Mechanism

o Cyclic, Hash, Least numbers of users o Weighted Cyclic, Least Amount of Traffic o NT Algorithm/ Private Algorithm/ Customizable Algorithm/ Response Time

• Redundancy Features o Supports Active-Active and Active-Standby Redundancy o Segmentation/ Virtualization support along with resource allocation

• Server Load Balancing Features o Server and Client process coexist o UDP Stateless o Service Failover o Backup/ Overflow o Direct Server Return o Client NAT o Port Multiplexing-Virtual Ports to Real Ports Mapping o DNS Load Balancing

• Load Balancing Applications o Application/ Web Server, MMS, RTSP, Streaming Media o DNS, FTP- ACTIVE & PASSIVE, REXEC, RSH, o LDAP, RADIUS

• Content Intelligent SLB • SLB should provide protection against DoS/ DDoS attack


Page | 228


• HTTP Header Super Farm • URL-Based SLB • SLB should support below Management options

o Secure Web Based Management o SSH o TELNET o SNMP v1, 2, 3 Based GUI

• Command Line

3) Link Load Balancer (may be proposed if State has to build own DC in case SDC’s is not

operational)

• 10/100/1000Mbps Ethernet Ports – minimum 2 ports upgradeable to 4 ports • Memory: Minimum 2 GB • Minimum of 2 Gbps throughput • Link Load Balancing Algorithm

o Round robin, weighted round robin, response time, shortest response etc. • Link Load Balancer should support below Management options

o Secure Web Based Management o SSH o TELNET o SNMP v1, 2, 3 Based GUI

• Command Line

4) Production CAS (State) Application Services related servers (Web, Portal, Application,

Database, Directory, etc…)

Blade Chassis Specification

• Single blade chassis should accommodate minimum 9 (Quad core Processor)/ 18 (Dual core Processor) or higher hot pluggable blades.

• Processor should be latest series/ generation for the server model being quoted (Xeon processor Preferred)

• 6U to 12U Rack-mountable • Dual network connectivity for each blade server for redundancy should be provided.

Backplane should be completely passive device. If it is active, dual backplane should be provided for redundancy.

• Should accommodate latest high speed processor in compatible with the OEM’s of blade servers.

• Should have the capability for installing industry standard flavors of Windows, Linux and Unix Operating environments.

• Single console for all blades in the enclosure or KVM Module. • DVD ROM can be internal or external, which can be shared by all the blades allowing

remote installation of S/W and OS. • Should provide external USB port. • Two hot-plug, redundant Ethernet modules with minimum (8 – 10) x 1Gbps Ethernet

ports (cumulative) having L2/ L3 functionality.


Page | 229


• Two hot-plugs/ hot Swap redundant 4 Gbps Fiber Channel for connectivity to the external Fiber channel Switch and ultimately to the storage device.

• Power Supplies o Hot Swap/ hot plug redundant power supplies to be provided. o Power supplies should have N+N. All Power Supplies modules should be populated

in the chassis. • Hot Swappable/ hot pluggable and redundant Cooling Unit. • Management

o Systems Management and deployment tools to aid in Blade Server configuration and OS deployment.

o Remote management capabilities through internet browser. o It should provide Secure Sockets Layer (SSL) 128 bit encryption and Secure Shell

(SSH) Version 2 and support VPN for secure access over internet. o Ability to measure power historically for servers or group of servers for optimum

power usage. o Blade enclosure should have provision to connect to display console/central console

for local management like trouble shooting, configuration, system status/ health display.

• Built in KVM switch or Virtual KVM feature over IP. • Dedicated management network port should have separate path for management. • Support heterogeneous environment: AMD, Xeon and RISC/ EPIC CPU blades must be in

same chassis with scope to run Win2003/ 2008 Server, Red Hat Linux/ 64 Bit UNIX, SUSE Linux /64 Bit UNIX /Solaris x86.

Blade Servers (Web, Portal, Application, Directory, etc…)

• Blade can be half/ full height with I/O connectivity to backplane. • 2 Quad core @ 2.0 GHz or above with 4 MB shared L2 cache, 1066 MHz / 2000MT/s FSB • Processor should be latest series/ generation for the server model being quoted (Xeon

processor Preferred) • Min 32 GB FBD/ DDR3 RAM with minimum 8 no. free slots for future expandability. • Minimum Memory: 32 GB scalable to 128 GB per blade • The Blade should have redundant 4 Gbps Fiber Channel HBA (only for database server) • Min 2 X (1000BASE-T) Tx Gigabit/ equivalent or better LAN ports with TCP/ IP offload

engine support/ dedicated chipset for network I/O on blade server. • 2 x 146GB HDD or more hot plug/ hot swap system disk with mirroring using integrated

raid 0,1 on internal disks or min 16 GB compact flash card to be provided. It should be possible to hot swap the drives without shutting down the server.

• VGA/ Graphics Port/ Controller. • Should support heterogeneous OS platforms.

Blade Servers for Infrastructure Services (EMS, Backup, DNS, Antivirus, etc…)

• Blade can be half/ full height with I/O connectivity to backplane. • 2 Quad core @ 2.0 GHz or above with 4 MB shared L2 cache, 1066 MHz/ 2000MT/s FSB • Processor should be latest series/ generation for the server model being quoted (Xeon

processor Preferred)


Page | 230


• Min 16 GB FBD/ DDR3 RAM with min 8 Nos. free slots for future expandability. • Minimum Memory: 16 GB scalable to 128 GB per blade. • The Blade should have redundant 4 Gbps Fiber Channel HBA • Min 2 X (1000BASE-T) Tx Gigabit/ equivalent or better LAN ports with TCP/ IP offload

engine support/ dedicated chipset for network I/O on blade server. • 2 x 146GB HDD or more hot plug/ hot swap system disk with mirroring using integrated

raid 0,1 on internal disks or min 16 GB compact flash card to be provided. It should be possible to hot swap the drives without shutting down the server.

• VGA/ Graphics Port/ Controller • Should support heterogeneous OS platforms

Database Server

• Minimum 4x Quad core processor with 2.1 GHz or above with 1066 MHz FSB/ 2000MT/s is scalable up to 8 processors 8 physical processor with minimum 4 MB L3 cache per processor.

• Processor should be latest series/ generation for the server model being quoted (Xeon processor Preferred)

• OS support: Microsoft® Windows Server 2003/ 2008, Enterprise Edition/ Red Hat® Enterprise Linux 5 & 4 AP/ SUSE® Linux Enterprise Server 9/ Solaris for x86.

• Memory (RAM): Min 64 GB scalable to 256 GB. • RAID controller with RAID 0, 1, 5, 6 with 256 MB cache. • HDD hot pluggable: 4 x 146 GB 2.5” 10K RPM HDD or more. • Disk bays: Support for min 8 small form factor hot plug SAS/ SCSI hard drives in disk

drive carriers. • At least 4 x 10/ 100/ 1000 Mbps Ethernet ports or more. • 2 x 4 Gbps Fiber Channel Ports. • Ports Rear: Two USB ports (Ver 2.0); RJ-45 Ethernet; keyboard and mouse;

Front: One USB (Ver 2.0) • Graphics controller: SVGA/ PCI bus/ ATI® ES 1000/ min 16MB SDRAM std/max/

1280x1024 at 16M colors • Optical/ diskette: 8X/ 24X slim-line DVD ROM drive shared across chassis • Security: Power-on password/ boot without keyboard. • Power supplies: Hot Plug/ Swap redundant power supply to be provided • Management feature to identify failed components even when server is switched off. • Rack Mountable • It should provide Secure Sockets Layer (SSL) 128 bit. • Encryption and Secure Shell (SSH) Version 2 and support VPN for secure access over

internet. • Should be able to manage systems through a web-browser.


Page | 231


5) Storage and Backup Solution

SAN Switches • Min 16 Active Ports (each with minimum port speed 4 GB) within same switch

upgradeable to 24 port with minimum 2 Nos. of additional 10/ 8 GBBS FC ports. • All cable of length of 10 meter each and accessories for connecting Servers/ Devices to

SAN. • Should have capability of ISL trunking of minimum 8 ports. • Should support multiple OS. • Non disruptive subsystem maintenance. • Should have dual Hot plug/ hot swap Fans and Hot plug/ hot swap power supplies

switching and service modules • Should have web based management software for administration and configuration. • Non disruptive microcode/ firmware upgrades and hot code activation. • Switch shall support in built diagnostics, power on self test, command level diagnostics,

online and offline diagnostics. • Should support hardware ACL based Port security, Port Zoning and LUN Zoning. • Should support Secure Shell (SSH) encryption to provide additional security for Telnet

sessions to the switch. • Should support multilevel security on console access prevent unauthorized users from

altering the switch configuration • Should support Fiber Channel trace route and Fiber Channel Ping for ease of

troubleshooting and fault isolation • Should support the following diagnostics:

o Online Diagnostics o Internal Loopbacks o FC Debug o Syslog o Online system health o Power on self test (POST) diagnostics

• Should support Applications for device management and full fabric management. The management software shall be able to perform following: o Fabric View o Summary View o Physical View o Discovery and Topology Mapping o Network Diagnostics o Monitoring and Alert

Storage Area Network

• SAN controller o Dual Active Controller

• Cache o 8 GB Total Mirrored Cache for Disk IO Operations scalable to min 16 GB

• Host interface


Page | 232


o 4 host ports per controller, Fibre Channel (FC), 4 Gbps per port • Drive interface

o 4 drive ports per controller—Fibre Channel (FC) Switched or FC Arbitrated Loop (FC-AL) standard per controller, 4 Gbps per port

• RAID levels Supported 0, 1, 5, 6 • Fans and power supplies

o Dual redundant, hot-swappable/ hot pluggable • SAN support

o Box should be compatible of SAN environment • SAN specifications shall have the following

o The storage array shall be configured with at least 8 GB cache scalable to min 16GB mirrored across two storage controllers for disk I/O operations.

o Storage subsystem shall support 300 GB/ 450/ 600 or higher FC/SAS 10K RPM disks. 750 GB / 1TB or higher SATA/ FATA/ equivalent 7200 RPM drives in the same storage array.

o Presently, the storage sub system shall be configured with 300 GB of Performance drives and 750 GB or higher on SATA / equivalent for archiving purpose.

o The storage system must provide upgrade path to larger or future array controller and software technology by controller upgrade or data migration.

o The storage array proposed should have an upgrade path from the earlier generation product to the current generation product. Hence the bidder should provide the solution data migration from existing array to new array or upgrade the array.

o All the necessary software to configure and manage the storage space, RAID configuration, logical drives allocation, virtualization, snapshots (including snap clones and snap mirrors) for entire capacity etc.

o Redundant power supplies, batteries and cooling fans and data path and storage controller.

o Load balancing must be controlled by system management software tools. o The Multi-path software should support supplied or heterogeneous storage and

operating. o The storage array must have complete cache protection mechanism either by de-

staging data or providing complete cache data protection with battery backup for up to 72 hours or more.

o The Storage should have at least 2ports of 4 Gbps Frontend ports and 2 no’s of back end ports of 4Gbps”

o The storage array must have the capability to do array based remote replication using FCIP or IP technology.

o The storage array should support block level Synchronous and Asynchronous replication on homogenous or heterogeneous storage arrays.

o The storage array should support Operating System Platforms & Clustering including: Windows Server 2003 (Enterprise Edition), Sun Solaris, HP-UX, IBMAIX, Linux / Solaris for x86. Any software or license required to enable connectivity to all these OS should be included.

o Storage should support non-disruptive online firmware upgrade for both Controllers and disk drives.


Page | 233


o The storage array should support hardware based data replication at the Block level across all models of the offered family.

o The storage should provide automatic rerouting of I/O traffic from the host in case of primary path failure.

o Should provision for LUN masking, fiber zoning and SAN security. o Should support storage virtualization, i.e. easy logical drive expansion & automated

load leveling across new drives to minimize performance bottleneck. o Should support hot-swappable physical drive raid array expansion with the addition

of extra hard disks o The storage system should be scalable from 20TB to 60TB of raw capacity using 40%

on Fiber Channel drives and 60% on SATA/ equivalent drives using the same configuration

o Should be able to support clustered and individual servers at the same time. o Should be able to take "snapshots" of the stored data to another logical drive on a

different Disk/ RAID Group for backup purposes o Should be configured with "snapshots and clone (local and remote)", licenses for the

storage & clone features should support resync. o Vendor should also offer storage performance monitoring and management

software. o The vendor must provide the functionality of proactive monitoring of Disk drive and

Storage system for all possible hard or soft disk failure.

Tape Library

• Tape drives o Minimum 2 latest generation LTO drives. The State can size for more as per their

requirements. • Interface

o Fiber Channel Interface

Other Specifications • Should have sufficient speed backup to Tape Library in High Availability for backing up

data from the SAN without any user intervention. • Should be able to backup 50% of the entire production landscape in 8 hours window. • Should support latest generation LTO drives or latest technology based library with at

least 2 latest generation LTO drives tape drives (>=4), rack mountable with redundant power supplies.

• Cartridges should have physical capacity up to 1600 GB per cartridges compressed; 800 GB native.

• At least 50 latest generation LTO drive Media Cartridges with 5 Cleaning Cartridges, Barcode labels shall also be provided.

Backup Software • The proposed Backup Solution should be available on various OS platforms such as

Windows and UNIX platforms and be capable of supporting SAN based backup / restore from various platforms including UNIX, Linux, and Windows etc.


Page | 234


• Centralized, web-based administration with a single view of all back up servers within the enterprise. Single console must be able to manage de-duplicated and traditional backups.

• The proposed backup solution should allow creating tape clone facility after the backup process.

• The proposed Backup Solution has in-built frequency and calendar based scheduling system.

• The proposed backup Solution supports the capability to write multiple data streams to a single tape device or multiple tape devices in parallel from multiple clients to leverage the throughput of the Drives using Multiplexing technology.

• The proposed backup solution support de-multiplexing of data cartridge to another set of cartridge for selective set of data for faster restores operation to client/ servers

• The proposed backup solution should be capable of taking back up of SAN environment as well as LAN based backup.

• The proposed backup solution shall be offered with 4 Nos. UNIX based licenses, 26 Nos. Windows based licenses and the rest 20 Nos. LINUX based licenses for both SAN based backup and the LAN based backup.

• The proposed solution also supports advanced Disk staging. • The proposed Backup Solution has in-built media management and supports cross

platform Device & Media sharing in SAN environment. It provides a centralized scratched pool thus ensuring backups never fail for media.

• Backup Software is able to rebuild the Backup Database/ Catalog from tapes in the event of catalog loss/ corruption.

• The proposed Backup Software should offer online backup for all the Operating Systems i.e. UNIX, Windows & Linux etc

• The proposed Backup Solution has online backup solution for different type of Databases such as Oracle, MS SQL, and Sybase/ DB2 etc. on various OS.

• The Proposed backup solution shall provide granularity of single file restore. • The Proposed backup solution shall be designed in such a fashion so that every client/

server in a SAN can share the robotic tape library. • Backup Solution shall be able to copy data across firewall. • The backup software must also be capable of reorganizing the data onto tapes within

the library by migrating data from one set of tapes into another, so that the space available is utilized to the maximum. The software must be capable of setting this utilization threshold for tapes

• The backup software should be able to support versioning and should be applicable to individual backed up objects.

• 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.


Page | 235


FC – IP Router

• Fibre Channel Ports o Min 4 FC ports

• FC Port Speed o Autosensing 1/ 2/ 4 Gb/s

• iSCSI (Ethernet) Ports o Min 8 Ethernet ports

• iSCSI (Ethernet) Ports speed o 1 Gigabit Ethernet

• Aggregate Bandwidth o Min 125 MB/s

• Protocol Support o FC o iSCSI

• High Availability Features o Two way active/ clustering with failover and failback capabilities o Multiple iSCSI connections provide multi-pathing support from a single gateway to

as many as 100 servers • Management Features

o CLI (by Telnet, SSH or console) • iSCSI Gateway Manager

o SNMP o Allow for monitoring traffic statics on each storage and network interface, fan and

temperature and iSCSI session details.


Page | 236


6) Appliance based HSM for PKI Security and Encryption

S. No Specification 1 Should support windows 2000/ 2003/ 2008, Linux, Solaris, HP-UX 11i, VMWARE, AIX

5.3 2 Should comply to standards like FIPS 140-2 Level-3, CC EAL4+, ROHS, FCC part 15

Class B 3 Key Exchange Mechanism: DES/ Triple DES, AES Algorithm 4 Hash/ HMAC algorithm: MD5, SHA 1, SHA 2, SHA 256 5 Symmetric Algorithm : AES, MD5, SHA 1, SHA 2, SHA-256 , DES, Triple DES 6 Support for various cryptographic algorithms: Asymmetric Key with Diffie-Hellman

(1024-4096 bit), RSA (512-4096 bit) and (PKCS#1 v1.5, OAEP PKCS#1 v2.0), Digital Signing via RSA (1024-4096-bit), DSA (512-1024-bit), EC Brain pool Curves (named and user-defined), Suite B Algorithm Support and ARIA support.

7 Published API for various above functionalities for integrating with the Application software.

8 Signing speed: 5000 S/S 9 Remote PED Support for Authentication

10 Onboard key generation, Digital Signing & Verification process to be done inside the HSM only for better performance and security

11 HSM should be integrated with the applications running inside the Data Center 12 Complete hardware based storage of key material for entire Life cycle 13 24/ 7 telephonic/ email support infrastructure based out of India 14 TCP/ IP Network based appliance 15 Key Length Supported (1024 to 4096) 16 Public Key Algorithm RSA encrypt/ decrypt, RSA sign/ verify, ECC (Electric Curve

cryptography) 17 Keys are always in Hardware and never stored in Software in any form 18 Compatibility: PKCS#11 , CAPI, Open SSL, JCE/ JCA 19 Scalable Up to more than 15 unique partitions 20 Private key generation and import: Archival and duplication mechanism to be

specified. Give the procedure for key transportation from one HSM card to other HSM card.

21 Contents can be securely stored on Backup Tokens to simplify backup, cloning, and disaster recovery.

22 Onboard key generation, Digital Signing & Verification process to be done inside the HSM only for better performance and security.

23 Additional/ specific software’s if any, required supporting multiple HSM appliances to be provided.


Page | 237


7) KVM Switch

Keyboard, Video Display Unit and Mouse Unit (KVM) and/ or other Control Devices/ PCs may be used for the IT Infrastructure Management for which the necessary consoles/ devices shall be placed by MPSEDC in the location earmarked. The KVM unit should provide the following functionalities:

• Rack-mountable.

• Minimum 8 ports scalable up to 24 ports.

• Should support local user port for rack access.

• Support for USB and PS/2 connections.

• Capability of storing username and profiles.

• Should support high resolution of minimum 1280 x 1024

• Capability to auto scan servers

• Should work on CAT 6/ CAT 7 cables.

• Rack Mountable LCD Monitor with In-built Keyboard & Mouse

o 1 U Rack Mount.

o Display size: 17 inches diagonal.

o Contrast Ratio: 700:1

o Display colors: 16 million.

o Resolution: SXGA 1280 x 1024.

o Brightness: 300 nit.

o Compatible to both PS/2 and USB based inputs


Page | 238


8) Networking Equipments (SDC/ DR/ all other Police Locations)

Router

a) General Architecture:

• High speed CPU • Rack mountable configuration • Health LED for all modules to indicate status

b) Router Port Requirements:

• 10/ 100 Mbps Ethernet - 2 Nos • WAN Ports E1 - 2 Nos • Packet Forwarding Speed - Minimum 160 Kpps

c) Router Features:

• Support for router redundancy protocol • Router software must have on line reconfiguration facilities • High MTBF • Capable of booting from a remote system where router image is present • Support for standard routing protocols like OSPF, RIP & BGP • Should have adequate memory and flash for proper functioning of all features with

no performance degradation. • Minimum of 256 MB RAM • Configurationally changes should be done without rebooting the router or modules

Stateful firewall functionality.

d) Software features:

• Following standard IP routing protocols:

o Static o RIP, OSPF o OSPF Over Demand Circuits o Policy Routing o IP Version 6 Support o Support for IPSec& 3DES through a simple software upgrade as and when required.

• Following WAN protocols:

o PPP o Multilink PPP o Compression-Payload and TCP/IP Header

• Following Multicasting and Quality of Service (QoS):

o Resource Reservation Protocol (RSVP) as per RFP 2205 and Internet Group Management Protocol Version 2 (IGMPv2) as per RFC 2236.

o Support for IP Precedence, Committed Access Rate (CAR), o DiffServQoS


Page | 239


o The router shall support Application recognition and it should be possible to frame policies based on the applications or equivalent functionality.

e) Security Features:

• Support DES/ 3 DES/ AES • PPP PAP or CHAP support. • VPN support • Time based Access Lists • Multiple Privilege Levels. • Support for RADIUS or AAA.

f) Power: 230 V AC, 50 Hz


Page | 240


Switches:

a) 16 Port Switch:

• 16 x 10/ 100BASE-TX, auto-negotiation ports • Interface: RJ-45 10BASE-T, 100BASE-TX • LED indicators: Power, Link/ Act • Transfer Method: Store and Forward • MAC Address Learning: Automatically learning, automatically Update • Power Supply: 100 – 240 VAC, 50/60Hz • 16-Port 10/100 Switch • Safety & Emission: FCC, CE • Rack mount Kit • IEEE 802.3 10Base-T Ethernet, IEEE 802.3u 100Base-TX Fast Ethernet, IEEE 802.3

Nway Auto-negotiation, IEEE 802.3x Flow Control, IEEE 802.1p Qos Prioritization

b) 48 port Layer 3 Switch:

• Layer 3 stackable switch • 48 x 10/ 100/ 1000 ports, auto-negotiating • 4 No SFP-based Gigabit Ethernet ports • Non-blocking architecture • 32 Gbps switching fabric capacity and 38 mpps forwarding rate • Support IGMP Snooping with Broadcast Control IGMP v3. • Support for minimum 8000 MAC addresses. • Ethernet, Fast Ethernet support • Spanning tree/ Rapid Spanning Tree support • Per VLAN Spanning Tree • Support for dynamic VLAN Registration • Dynamic Trunking Protocol or equivalent. • VLAN Trunking Protocol or equivalent • Traffic classification should be based on user-definable application types: TOS, DSCP,

Port based, Mac address, IP address, TCP/ UDP port number • Multicast filtering per port should be supported • Support SNMP upto ver.3 • Prioritization support • Minimum 250 vlans • SNMP and Telnet support • Web-based and CLI management • Four RMON groups (1,2,3&9) • Additional features: Advanced QoS, Rate limiting • L3 Features : Static routes & RIP • Mounting: 19” Rack mountable • Source power supply: 230 V AC Single phase 50Hz


Page | 241


Perimeter Firewall

a) Physical Attributes • Rack Mountable • Modular Chassis • Redundant Power Supply

b) Interfaces • 4xGE Upgradable to 8 • 1xConsole Port

c) Performance • Firewall Throughput: Min 2 Gbps • Concurrent Connections: Min 500K • Simultaneous VPN tunnels: Min 2K

d) Routing Protocols • Static Routes • RIP v1, RIP v2 • OSPF v2 & v3

e) Protocols • TCP/IP,PPTP • RTP, L2TP • IPSec / GRE, DES/ 3DES/ AES • PPPoE, EAP-TLS, RTP • FTP, HTTP, HTTPS • SNMP, SMTP • DHCP, DNS • Support of IPv6

f) Other Support g) 802.1Q, NAT, PAT, IP Multicast Support, Remote Access VPN, Time based ACls, URL

filtering, Support VLAN, Layer 2 Firewall, Virtual Firewall, RADIUS/ TACACS h) Management i) Console, Telnet, SSHv2, Browser based configuration j) SNMP v1, SNMP v2


Page | 242


9) Minimum Technical Specifications Requirement at Police Units: Minimum Technical specifications for Desktops at Police Stations

Desktop Configuration

1 Processor: Intel Core2Duo or higher 2 Motherboard: OEM Motherboard 3 Memory: Minimum 4 GB DDRII or higher 4 Cache: Minimum 4 MB or higher 5 Internal Hard Disk: 320 GB SATA (7200 RPM) or higher 6 Optical Drive: DVD Writer Drive 7 Display size: 18.5 inch (measured diagonally) 8 Graphics Controller: Integrated graphic Controller 9 Form Factor: Convertible Minitower

10 External I/O ports:

Stereo in, stereo out (back) & stereo out (front), Headphone and microphone; Expansion slots: 1 full-height PCI, 2 full-height PCI Express x1, 1 full-height PCI Express x16

11 Rear: 6 USB 2.0, 1 serial port (optional), 1 parallel port (optional), 1 PS/2 (Keyboard), 1 PS/2 (Mouse), 1 RJ-45, 1 VGA, audio in/out.

12 Front: 2 USB 13 Network interface: Integrated 10/100 Mbps Ethernet Adapter (RJ-45), 14 Management: Desktop Management Tool 15 Bilingual Keyboard: PS/2 or USB Standard Keyboard 16 Pointing device: USB 2-Button Optical Scroll Mouse 17 Security management:

(Optional) TPM 1.2 TPM Security Chip (except for Russia), TPM Pre-Boot

18 Authentication: (Optional)

Smartcard Pre-boot Authentication (via BIOS), Stringent

19 Software Including: Preloaded Windows 7 Business/ Professional Edition or higher Preloaded MS-Office Preloaded Antivirus

20 Software Security Security Software, Serial, Parallel, USB Enable/ Disable (via BIOS), Write/ Boot Control, Power-On and Setup Password (via BIOS)

21 Warranty (ATS): 3 Years Part, 3 Years Labor, 3 Years On-Site

Minimum Technical Specifications for Multi-Function Laser Printer

Multi-Function Laser (Print/ Scan/ Copy) 1 Printer High-speed printing, Black-and-white: up to 35ppm (draft); up to 15ppm, Duty

Cycle: Upto 15,000 pages per month. Automatic two-sided printing, 250-sheet input tray, Print, scan and copy unattended with the Automatic Document feeder, monitoring and troubleshooting in the network, from anywhere on the network

2 Scanner Flatbed with automatic document feed, upto 4800 dpi; Enhanced upto 19200 dpi; Scan size max (flatbed): 215.9 x 297 mm (8.5” x11.7”), front panel scan

3 Copier Black-white color-Upto 1200x600 dpi, Copy speed (black, draft quality, A4):Up to 35 cpm, Copy resolution (black graphics): Up to 1200 x 600 dpi, Copier resize: 25 to 400%, Maximum number of copies: Up to 99, Copier smart software features: Up to 99 multiple copies, reduce/ enlarge from 25 to 400%, 2-up or 4-up allowing 2 or 4 pages to be copied onto 1 page, contrast (lighter/ darker), resolution (copy quality), tray select, collate, margin, shift.


Page | 243


Minimum Technical Specifications for Duplex Laser Printer

Duplex Laser Printer – all Police Units/ Offices 1 Laser Printer Speed:

• 28 PPM (A4) or higher Processor:

• 400 Mhz or higher Resolution:

• Min. 1200 x 1200 dpi Duty Cycle:

• Min. 50,000 page/month Memory:

• 64 MB or higher Interface:

• USB 2.0 (High Speed) with USB Cable Duplex:

• Automatic Paper support:

• A4, Legal Compatibility:

• Windows XP/Windows Vista/Windows 7/ Linux

Minimum Technical Specifications for UPS SNMP Based 2kVA UPS - all Police Units/ Offices

1 SNMP • ISO 9001 certified brand • True On Line Type • Backup period should be at least 2 Hr with minimum 7200VAH for 3

kVA • IGBT with High Frequency PWM (Pulse with Modulation) Technology • Output wave form should be Sine wave • Compatible with local Electricity Power Generator. • Total Harmonic Distortion should be less than 3%. • Support input voltage range of 160 V to 270 V. • Output Voltage should be 230 Volt AC (+/- 1%) • Output frequency should be 50 Hz +/- 0.05 Hz (Crystal Controlled) • Closed housing for batteries with suitable stand. • Inherent protection should be provided for over loading, low battery,

over temperature, short circuits, over and under input voltage. • LED indicators should be provided for at least load indication, load on

battery, low battery, overload, Mains ON. • Audible indicator should be provided for at least load on battery, low

battery, Mains failure, Overload. • Galvanic Isolation to be provided through inbuilt double wound

transformer at output.


Page | 244


Minimum Technical Specifications for DG Set 2.5 KV DG Set - all Police Units/ Offices

1 The proposed DG set should be able to support the Police Unit equipments, in absence of primary power source. Engine shall be vertical multi cylinder 4 stroke type in accordance with IS 10002-1981 with latest amendments. Type: Multi cylinder Method of starting: Electric start 12 V DC Type of cooling: Water cooled / Air cooled Type of governor: Mechanical/ Electronic Type of fuel: High speed diesel Rating: Continuous Output: Suitable HP rated to match the alternator Rated speed: 1500/ 3000 RPM Over load capacity: 10% overload – minimum 1 hour 50% overload – minimum 1 minute

• Flywheel to suitable diameter and fuel injection equipment • Air cleaner • Lubricating oil cooler • Electric motor starting equipment like motor, battery, charging

generator with voltage regulator etc. • Heavy duty radiator with fan • Residential type silencer with exhaust piping with vibration isolator • Fuel tank suitable for 8 Hrs of continuous running with necessary piping

and fuel gauge, drain valve, inlet and outlet connections. • Anti vibration mounting pads (Dunlop) • Speed controlling governor • Suitable coupling system to the Alternator • Tachometer • Lubricating oil pressure gauge • 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, Aluminum sheet,

chicken mesh, Diesel line 12 mm dia including beads flanger etc • Battery 12 V with lead and terminal • Battery charger. • Protection: Protection against low lubricating oil pressure, high water

temperature and over speed shall be provided for engine with alarm and fuel shut off.


Page | 245


Minimum Technical Specifications for Finger Print Reader Finger Print Reader - all Police Stations

1 Fingerprint Sensor: • Scanner: Optical sensor • Resolution: 500 dpi at 256-bit (416 X 416 pixels) • Platen Area: 0.83 in x 0.83 in (45.7 mm x 45.7 mm) PIV System included • Distortion: <1%

Biometric Matching: • Authentication: <1 second (including detection, encoding and

matching) • Identification: <2 seconds in 1:3000 mode (including detection,

encoding and matching) • False Acceptance Ratio (FAR): 1 in 10,000 or better, configurable • based on security specifications

Interfaces: • Standard USB

Environment: • Temperature: 0° C to 50° C • ESD Protection: 15 KV

Format Supported: • AANSI/ INCITS 378, • ISO 19794-2

Minimum Technical Specifications for Digital Pen Digital Pen- all Police Stations

1 Average battery life: • Min. 2.5 hours continuous writing use

Average usage life: • 3 – 4 years

Approximate battery recharge time: • 2 hours

Battery type: • Lithium-ion polymer rechargeable battery:

Standard Connectivity: • USB 1.1 (also called High Speed USB 2.0)

Humidity non operating: • 0 to 95% RH (excluding rain, non-operating)

Humidity range: • 0 to 95% RH (excluding rain)

Operating range: • 0 to 90% RH (non-condensing, operating)

Operating temperature maximum: • 104°F

Operating temperature recommended range: • 32 to 104°F

Storage temperature range: • -4 to 104°F

Storage life:


Page | 246


• 3 – 4 years Image compression:

• Pattern images to X, Y coordinate samples with relative time of capture Image processing rate:

• 75 Hz Image resolution:

• At least 500 dpi Image scaling:

• Perspective, rotation, tilt, and error correction Internal fixed memory:

• At least 10 MB (1.3 MB available for user strokes)

Minimum Technical Specifications for Digital Camera Digital Camera - all Police Stations

1 • At least 14 Mega Pixels • Sensor size: 1/2.3-inch • Sensor type: CCD • Optical Zoom: 4x • Precision Digital Zoom: Yes, needed • Lens: Carl Zeiss or equivalent • Min aperture wide f3.1 - 3.5 • Min aperture tele f5.8 - 8.0 • Auto Focus Range (W: Approx. 4cm to Infinity, T: Approx. 60cm to

Infinity) • Compatible Recording Media Memory Stick Duo/ Memory Stick PRO • Duo/ Memory Stick PRO Duo (High Speed)/ Memory Stick PRO-HG • Duo/ SD Memory Card/ SDHC Memory Card • LCD: 2.7 (6.9 cm) (230K pixels), Clear Photo LCD • Battery Life: 240 shots or 120mins • Battery System: Lithium ION Battery • USB 2.0 Hi-Speed


Page | 247


ANNEXURE XIII: INDICATIVE HARDWARE BILL OF MATERIAL

Hardware Distribution at Non-CIPA, CIPA and all other Higher Office’s: Description Indicative

Quantity at Non-CIPA P/S

(167)

Indicative Quantity at CIPA

P/S

(23)

Indicative Quantity at SDPO/ ASP

(67)

Indicative Quantity at DPO

(25)

Indicative Quantity at

Range Office

(7)

Indicative Quantity at Zone

Office

(2)

Indicative Quantity at PHQ

(2)

Indicative Quantity at

SCRB

(1)

TOTAL

Desktops

Desktop with pre-loaded OS, MS-Office & Antivirus

668 - 201 250 28 8 60 10 1225

Other Hardware

Printer (Duplex Laser) 167 - - - - - - - 167

Multi Function Printer

(Print/ Scan/ Copy) 167 - 67 25 7 2 2 1 271

UPS (2.5KV) 167 - 67 75 7 2 16 3 337

Generator (2KV) 167 23 - - - - - - 190

16 Port Switch 167 23 67 25 7 2 2 1 294

HDD 160 GB (External) 167 23 - - - - - - 190

Digital Camera 167 23 - - - - - - 190

Electronic Pen 167 23 - - - - - - 190

Fingerprint Reader 167 23 - - - - - - 190

Site Preparation1 167 23 67 25 7 2 2 1 294

Other Software


Page | 248


Operating System (Win 7) 0 92 0 0 0 0 0 0 92

Microsoft Office Suit 0 92 0 0 0 0 0 0 92

Antivirus Software 0 92 0 0 0 0 0 0 92

Operational Expenses

for 3 Years 167 23 67 25 7 2 2 1 294

Site Preparation1: Include Adequate Furniture, Electric Cabling with suitable Earthing & Earth Pit, Cat 6 Cable with Cabling (In Meters), Patch Cords 2 Mtr. CAT 6 & Information Outlet CAT 6

Note: Quoted price should include Licensed OS, MS-Office Suite and Antivirus Quoted price should include 3 Years ATS i.e. 3 Years Part, 3 Years Labour, 3 Years On-Site warranty


Page | 249


Hardware Distribution at Data Centre and Disaster Recovery Site:

The details pertaining to the proposed DC and DR the Police Department

Items Qty Make Model Network Server Racks 42 U 2

Application Server (Rack Server) 2

Test & Development Server (Rack Server) 1

Database Server (Rack Server) 2

Web Server (Blade Server) 2

Portal Server (Blade Server) 2

Backup Server (Blade Server) 1

Directory & Access Server 2

Communication & Mail Server 2

Blade Chassis 2

Storage Box (SAN) 2

Storage Area Switch 2

SAN Storage Management Software 1

Automated Tape Library 2

DR Recovery Storage 1

Back-up Software 1

HSM for PKI Security and Encryption (2No at DC and 1 at DR) 3

Router 2

FC – IP Router 2

Load Balancer 2

Link load Balancer 2

Core Switch L3 Gigabit 48 Port 2

KVM Switch 2

Patch Panel 24 Ports CAT 6 2

CAT 6 Cable (305 Mtr. Box) 3


Page | 250


Information Outlet CAT 6 36

Patch Cord 2 Mtr CAT 6 36

UTM Firewall with VPN and IPS 2

Data Center Software (Server OS with CAL, Server Management, Intranet Portal, MIS & Reporting Dashboard etc.)

18

Database Software (Processor Based for unlimited users) 6

Antivirus Software for Servers 18

Email Security Software Required features; Anti-spam Anti-virus Anti-spoofing Anti-phishing Anti-spyware (Attachments) Denial of Service Data Leak Prevention

2

Enterprise Management System (EMS) 1

Out Sourced manpower for datacenter 2 nos. × 3 shifts for 5 Years -

ATS for three (3) years -

Note: System Integrator shall provide necessary service support and assistance to JK Police for taking the bandwidth for WAN connectivity from BSNL and/ or SWAN and also provide and subsequent, required and related maintenance/ support services.


Page | 251


Handholding Support:

S. No. Items No. of Police Station For the period of 6 Months 1. Handholding Support 190

Data Digitization:

S. No. Items No. Of Case Files to be Digitized (For last 10 Years) 1. Digitization 102857

Capacity Building:

Expenditure Head No. Of Units SCRBX Infrastructure 1

District Training Centre ,Site preparation 25

District Training Centre 25

RTC/ PTC/ Academy 6

Training for Police Personal 42441


Page | 252


ANNEXURE XIV: E GOVERNANCE STRUCTURE

This section will provide the governance structure that will be created at the

State level to monitor the implementation of the CCTNS project. 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

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

Committee

• Disbursement of funds to Districts and other units/

agencies

• Approval of BPR proposals

• Sanction for various project components, as may be

specified, including the Hardware/ Software,

procurement as per the specifications from NIC

• Approval of various Project Components and

Functionalities to be covered in the Project

• Review progress of the Project

• Ensure proper Training arrangements

• Ensure deployment of appropriate handholding

personnel

• Other important policy and procedural issues

State Mission Team • Operational responsibility for the Project

• Formulating Project Proposals

• Getting sanction of GOI for various projects

• Hardware rollout and Operationalization


Page | 253


• Co-ordination with various agencies

• Resolution of all software related issues, including

customization

• Resolution of all other issues hindering the Project

Progress

• Any other decision to ensure speedy implementation of

the project

• Assist the State Apex and Empowered Committees

District Mission Team • Prepare District Project Proposal

• Ensure proper Rollout of the Project in each selected

Police Station

• 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

State Apex Committee

Members Composition Suggested

Member 1 (Chairman) Chief Secretary

Member 2 (Vice Chairman) Financial Commissioner (Home)

Member 3 Director General of Police, J&K

Member 4 Principal Secretary (IT)

Member 5 Commissioner/ Secretary (Finance)

Member 6 Special Secretary (Home)

Member 7 Head of SCRB

Member 8 (Convener) Representative of GOI, MHA

Member 9 IGP Crime (CCTNS Project)

Member 10 Representative of NIC

Member 11 Any other member co-opted from the field of IT,

Telecom


Page | 254


State Empowered Committee


Member 1 (Chair Person) DGP, J&K

Member 2 IGP (HQRs) PHQ, J&K

Member 3 IGP (Personnel) PHQ, J&K

Member 4 IGP Crime, J&K

Member 5 MD, PHC, J&K

Member 6 DIG Crime, J&K

Member 7 DIG (Admin) PHQ, J&K

Member 8 Director Police Telecommunication, J&K

Member 9 AIG (CIV) PHQ J&K

Member 10 AIG (Provision) PHQ, J&K

Member 11 State Informatics Officer

State Mission Team


Member 1 (Mission Leader) IGP Crime J&K

Member 2 DIG Crime, J&K

Member 3 DIG (Admin) PHQ, J&K

Member 4 State Informatics Officer

District Mission Team


Member 1 (Chair Person) District SSP/SP

Member 2 (Convener) DYSP (HQRS)

Member 3 Distt. Information Officer of NIC

Member 4 I/C District Crime Records Bureau.


Page | 255


ANNEXURE XV: Status of JKSWAN (List of Identified POPs)

S. No Name of the District Name of the Block Total 1 Jammu 1.Khour 2.Akhnoor 3.Marh 4.Dansal 5.Bishnah 6.R.S.Pura 7.Satwari 8.Bhalwal Total 8 2 Samba 1.Purmandal 2.Vijaypur 3.Samba 4.Ghagwal Total 4 3 Kathua 1.Hiranagar 2.Barnoti 3.Kathua 4.Billawar 5.Bani 6.Basohli 7.Lohai-Malhar 8.Duggan(New) Total 8 4 Udhampur 1.Udhampur 2.Majalta 3.Ramnagar 4.Ghordi 5.Dudu-Basantgarh 6.Chenani 7.Panchari 8.Kud Total 8 5 Reasi 1.Reasi 2.Pouni 3.Arnas 4.Mahore 5.Katra Total 5 6 Doda 1.Ghat 2.Assar 3.Thathri 4.Bhellassa


Page | 256


5.Bhagwah 6.Bhaderwah 7.Marmat(New) 8.Gundana (New) Total 8 7 Ramban 1.Ramban 2.Banihal 3.Ramsoo 4.Gool 5. Ukharhal Total 5 8 Kishtwar 1.Marwah 2.Warwan 3.Inderwal 4.Kishtwar 5.Padder 6.Drabshalla(New) 7.Nagseni (New) 8.Dachhan(New) Total 8 9 Rajouri 1.Rajouri 2.Sunderbani 3.Kalakote 4.Nowshera 5.Manjakote 6.Budhal 7.Darhal 8.Thanamandi (New) 9. Doongi Total 9

10 Poonch 1.Poonch 2.Mendhar 3.Mandi 4.Surankote 5.Balakote 6.Buffliaz(New) Total 6 Total Blocks In Jammu Division 69


Page | 257


BLOCKS/TEHSIL POPS IN KASHMIR DIVISION

S.No District Blocks Total 1 Srinagar Srinagar Total 1

2 Ganderbal Ganderbal Lar Kangan Wakura Sonmarg Total 5

3 Budgam Budgam B.K.Pora Beerwah Chadoora Khansahib Khag Nagam Narbal Total 8

4 Pulwama Pampore Kakapora Pulwama Tral Keller (Partly) Total 5

5 Shopian Shopian Keller (Partly) (Counted Above) Total 1

6 Anantnag Achabal Breng Dachnipora Khoveripora Shangus Shahabad Qazigund (Partly) Bijbehara Phalgam Quimoh (Partly) Total 10

7 Kulgam D.H.Pora Devsar Kulgam Pahloo Quimoh (Partly)(Counted Above) Qazigund (Partly)(Counted Above)


Page | 258


Total 4 8 Baramulla Uri Boniyar Baramula Rohama Rafiabad Sopore Zaingeer Wagoora Pattan Singhpora Gulmarg Kunzer Tangmarg Total 13

9 Bandipora Tulail Gurez Bandipora Hajin Sumbal Sonawari Total 6

10 Kupwara Sogam Wavoora Kalaroos Kupwara Trehgam Rajwar Langate Ramhal Kralpora Tangdhar Teetwal Handwara Total 13

11 Kargil Kargil G.M.Pore(Trespone) Sankoo Shaker Chiktan Shargole Taisura Drass Zanskar Lungnuk Total 9


Page | 259


12 Leh Leh Chuchot Khaltsi Suspol Nobra Panamic Nyoma Durkot Kahru Total 9 Total In Kashmir Division 83

TOTAL BLOCKS IN J&K = 69 + 83 = 152

Hence the total number of POP’s works out to be: 152+20+2 = 174


Page | 260


ANNEXURE XVI: TECHNICAL ARCHITECTURE

Deployment Architecture:


Page | 261


The ‘User’ Layer: This layer forms the internal departmental users accessing the

applications over Internet or through the available network. Role based access would be

defined for the internal users for having accessibility to the respective application modules,

such as HRMS, which would be accessed by all the Police Officers but higher Police authorities

would essentially be accessing reporting modules which would help them in decision making

and monitoring the overall Policing at various levels. Integrated database structure would

ensure a one point stop search available to all the police units.

The ‘Data’ Layer: The overall solution would be based on a hybrid architecture comprising

of centrally located databases at Police Data Centre as central repository and locally deployed

databases at other police units (mainly Police Stations). All the proposed applications would be

able to function in an offline mode and on availability of connectivity, data would automatically

replicate with the central repository in Police Data Centre. This approach would cater to the

functionalities of all the key processes and functions performed at Police Station level and

would also allow the users to have an access to the central repository for comprehensive

information as and when required. The Police Data Centre would securely host the

aforementioned information databases on servers specifically for Police Department. It is

recommended that the Data Center (DC) should be the preferred to Third Party Data Centre

option mainly on account of the following:

• The specialized skills needed to manage a data-centre (such as security access management

through multiple delivery channels, data encryption, storage management, database

administration, etc.) are already being provided for at the DC. To replicate, maintain and

continuously upgrade these skills at a Department level would be extremely difficult, time

consuming and waste of effort and resources.

• Easier to integrate with overall e-Governance initiatives in the State (i.e. integration and

interoperability with applications and databases being developed and maintained by other

departments at the DC) in the future, if and when required

• Cost effective option as the IT infrastructure investments would be required only for

enhancing the capacity of DC (e.g. additional servers, Storage capacity, upgraded

connectivity, etc.).


Page | 262


Networking: The overall networking solution would be based on a combination of Leased

line, VPN over Broadband and VSAT ensuring optimum uptime at all the desired locations. The

option of networking and connectivity with BSNL is under discussion and will be finalized by

MHA.

The ‘Application’ Layer represents three categories of modules, i.e. modules proposed by

the CAS (State), existing modules of the State department which would either be integrated as

it is or may require certain customization to integrate with CAS and lastly, the additional

modules proposed by the department which would be either developed afresh or would be

deployed after customizing a commercially available software. These modules will

communicate with each other by sharing of data with one another, or by coordinating an

activity between two or more services.

Users can easily access solution components (CCTNS modules) having a single sign-on

facility either through internet. All the modules would be supported with Business Intelligence/

Data Mining tools coupled with Bi-lingual support, e-payment gateway and workflow engine.

The ‘Service Delivery’ Layer represents the different modes/ media of service delivery,

which would be used for availing/ accessing the services of Police. Services would be primarily

provided through Dial 100 system accessed over internet, Mobile, SMS and through Khidmat

centers.


Page | 263


ANNEXURE XVII – NETWORK CONNECTIVITY FOR P/S & HIGHER OFFICES.


Page | 264


ANNEXURE XVIII – LIST OF CIPA P/S, NON-CIPA P/S AND OTHER HIGHER OFFICES.

List of Non-CIPA and CIPS Police Stations

S. No ZONE RANGE DISTRICT POLICE STATION CIPA/ Non-CIPA P/S 1 JAMMU ZONE JAMMU-KATHUA JAMMU JAMMUCITY CIPA

2 PACCA DANGA Non-CIPA

3 NAWABAD Non-CIPA

4 BAKSHI NAGAR Non-CIPA

5 GANDHI NAGAR CIPA

6 SATWARI Non-CIPA

7 AKHNOOR Non-CIPA

8 KANACHAK Non-CIPA

9 KHOUR Non-CIPA

10 DOMANA Non-CIPA

11 NAGROTA Non-CIPA

12 JAJJHAR KOTLI Non-CIPA

13 BISHNAH Non-CIPA

14 BAGH-E-BAHU Non-CIPA

15 PIR MITHA Non-CIPA

16 BUS STAND JAMMU Non-CIPA

17 JANIPUR Non-CIPA

18 BAHU FORT Non-CIPA

19 CHANNI HIMAT Non-CIPA

20 GANGYAL Non-CIPA

21 AMB GHAROTA Non-CIPA

22 MIRAN SAHIB Non-CIPA

23 ARNIA Non-CIPA

24 RS PURA Non-CIPA

25 WOMEN P/S Non-CIPA

26 KATHUA KATHUA CIPA


Page | 265


27 LAKHANPUR Non-CIPA

28 HIRANAGAR Non-CIPA

29 RAJBAGH Non-CIPA

30 BASOHLI Non-CIPA

31 BILLAWAR Non-CIPA

32 BANI Non-CIPA

33 MALHAR Non-CIPA

34 SAMBA SAMBA Non-CIPA

35 VIJAYPUR CIPA

36 RAMGARH Non-CIPA

37 BARIBRAHMANA Non-CIPA

38 PURMANDAL Non-CIPA

39 GHAGWAL Non-CIPA

40 JAMMU ZONE DODA – RAMBAN – KISHTWAR RAMBAN RAMBAN CIPA

41 BANIHAL Non-CIPA

42 CHANDERKOTE Non-CIPA

43 BATOTE Non-CIPA

44 GOOL Non-CIPA

45 DODA DODA CIPA

46 DEESA Non-CIPA

47 ASSAR Non-CIPA

48 BADHERWAH Non-CIPA

49 THATRI Non-CIPA

50 GANDOH Non-CIPA

51 KISHTWAR KISHTWAR Non-CIPA

52 ATHOLI Non-CIPA

53 CHATROO Non-CIPA

54 MARWAH Non-CIPA

55 POONCH RAJOURI RAJOURI RAJOURI CIPA


Page | 266


56 MANJAKOTE Non-CIPA

57 THANNAMANDI Non-CIPA

58 DARHAL Non-CIPA

59 BUDHAL Non-CIPA

60 KANDI Non-CIPA

61 NOWSHERA Non-CIPA

62 KALAKOTE Non-CIPA

63 SUNDERBANI Non-CIPA

64 DHARAMSAL Non-CIPA

65 POONCH POONCH CIPA

66 SURANKOTE Non-CIPA

67 MENDHAR Non-CIPA

68 GURSAI Non-CIPA

69 MANDI Non-CIPA

70 LORAN Non-CIPA

71 UDHAMPUR – REASI REASI BHAWAN Non-CIPA

72 *KATRA Non-CIPA

73 REASI CIPA

74 JYOTIPURAM Non-CIPA

75 TALWARA Non-CIPA

76 MAHORE Non-CIPA

77 UDHAMPUR UDHAMPUR CIPA

78 RAMNAGAR Non-CIPA

79 MAJALTA Non-CIPA

80 BASANTGARH Non-CIPA

81 CHENANI Non-CIPA

82 PANCHARI Non-CIPA

83 REHBAL Non-CIPA

84 KUD Non-CIPA


Page | 267


85 LATTI Non-CIPA

86 WOMEN CELL UDHAMPUR Non-CIPA

87 RAILWAYS - JAMMU GRP JAMMU Non-CIPA

88 GRP KATHUA Non-CIPA

89 GRP MANWAL Non-CIPA

90 GRP UDHAMPUR Non-CIPA

91 GRP KATRA* Non-CIPA

92 CB JAMMU CRIME BRANCH JAMMU Non-CIPA

93 P/S CI - JAMMU CID - JAMMU Non-CIPA

94 KASHMIR ZONE CENTRAL KASHMIR RANGE SRINAGAR MR GANJ Non-CIPA

95 KHANYAR Non-CIPA

96 NOWHATA Non-CIPA

97 PARIMPORA Non-CIPA

98 SAFAKADAL Non-CIPA

99 RAINAWARI Non-CIPA

100 KARANNAGAR CIPA

101 BATAMALOO Non-CIPA

102 SHAHEED GANJ Non-CIPA

103 SHERGARI Non-CIPA

104 RAJBAGH Non-CIPA

105 SADDAR Non-CIPA

106 NOWGAM Non-CIPA

107 KRALKHUD Non-CIPA

108 MAISUMA Non-CIPA

109 KOTHIBAGH CIPA

110 RM BAGH Non-CIPA

111 PANTHA CHOWK Non-CIPA

112 NISHAT Non-CIPA

113 HARWAN Non-CIPA


Page | 268


114 SOURA Non-CIPA

115 LAL BAZAR Non-CIPA

116 ZADIBAL Non-CIPA

117 NAGEEN Non-CIPA

118 ZAKURA Non-CIPA

119 WOME P/S RAMBAGH Non-CIPA

120 GANDERBAL Ganderbal CIPA

121 Kangan Non-CIPA

122 Kheerbhawani Non-CIPA

123 BUDGAM Budgam CIPA

124 Chadoora Non-CIPA

125 Charar-i-Sharief Non-CIPA

126 Magam Non-CIPA

127 Beerwah Non-CIPA

128 Khag Non-CIPA

129 LEH Leh CIPA

130 Nobra Non-CIPA

131 Nyoma Non-CIPA

132 KARGIL Kargil CIPA

133 Drass Non-CIPA

134 Zanaiskar Non-CIPA

135 NORTH KASHMIR RANGE BARAMULLA Baramulla CIPA

136 Uri Non-CIPA

137 Bijhama Non-CIPA

138 Panzula Non-CIPA

139 Pattan Non-CIPA

140 Tangmarg Non-CIPA

141 Sopore Non-CIPA

142 Sheeri Non-CIPA


Page | 269


143 Boniyar Non-CIPA

144 Gulmarg Non-CIPA

145 Kunzar Non-CIPA

146 Kreeri Non-CIPA

147 Dangiwacha Non-CIPA

148 Chandoosa Non-CIPA

149 KUPWARA Kupwara CIPA

150 Lalpora Non-CIPA

151 Karnah Non-CIPA

152 Trehgam Non-CIPA

153 Keran Non-CIPA

154 Sogam Non-CIPA

155 HANDWARA Handwara CIPA

156 Vilgam Non-CIPA

157 Karalgund Non-CIPA

158 BANDIPORA Bandipora Non-CIPA

159 Sumbal Non-CIPA

160 Gurez Non-CIPA

161 SOUTH KASHMIR RANGE ANANTNAG Anantnag CIPA

162 Dooru Non-CIPA

163 Pahalgam Non-CIPA

164 Sarigufara Non-CIPA

165 Mattan Non-CIPA

166 Bijbhera Non-CIPA

167 Kukernag Non-CIPA

168 Achabal Non-CIPA

169 Ashmuqam Non-CIPA

170 PULWAMA Pulwama CIPA

171 Rajpora Non-CIPA


Page | 270


172 SHOPIAN Shopian Non-CIPA

173 Zainpora Non-CIPA

174 Keller Non-CIPA

175 AWANTIPORA Awantipora CIPA

176 Tral Non-CIPA

177 Pampore Non-CIPA

178 KULGAM Kulgam CIPA

179 Qazigund Non-CIPA

180 DamhalHanjipora Non-CIPA

181 Yaripora Non-CIPA

182 CRIME BRANCH

KASHMIR Crime Branch Kashmir Non-CIPA

183 RAILWAYS KASHMIR Qazigund Non-CIPA

184 Anantnag Non-CIPA

185 Srinagar Non-CIPA

186 Awantipora Non-CIPA

187 Nowgam Non-CIPA

188 Hamrey Non-CIPA

189 Baramulla Non-CIPA

190 P/S CI KASHMIR CID - KASHMIR Non-CIPA


Page | 271


LIST OF SDPO / ASP OFFICES (JAMMU) S. No ZONE RANGE DISTRICT SDPO/ ASP

1. JAMMU ZONE Jammu-Kathua Jammu SDPO CITY NORTH 2. SDPO GANDHI NAGAR 3. SDPO CITY EAST 4. SDPO BAKSHI NAGAR 5. SDPO RS PURA

6. SDPO AKHNOOR 7. SDPO DOMANA 8. SDPO NAGROTA 9. ASP SOUTH 10. ASP NORTH 11. ASP RURAL 12. ASP (HQS) 13. Kathua DySP HQRS. KATHUA 14. SDPO BASHOLI 15. SDPO CHADWAL 16. ASP KATHUA 17. Samba DySP HQRs 18. SDPO VIJAYPUR 19. SDPO BARIBRAHMANA 20. ASP SAMBA 21. Ramban-Doda-Kishtwar Ramban DySP HQRs RAMBAN 22. SDPO BANIHAL 23. SDPO GOOL 24. Doda DySP HQRS DODA 25. SDPO BHADERWAH 26. SDPO GANDOH 27. ASP BHADERWAH 28. Kishtwar SDPO KISHTWAR 29. SDPO ATHOLI 30. ASP KISHTWAR 31. Roonch-Rajouri Rajouri DySP HQRs RAJOURI 32. SDPO NOWSHERA 33. SDPO THANNAMANDI 34. ASP RAJOURI 35. ASP NOWSHERA 36. Poonch DySP HQRS POONCH 37. SDPO MENDHAR 38. SDPO SURONKOTE 39. Reasi-Udhampur Udhampur DySP HQRs 40. SDPO RAMNAGAR 41. ASP UDHAMPUR 42. ASP City UDHAMPUR 43. Reasi SDPO REASI


Page | 272


44. SDPO KATRA 45. SDPO MAHORE 46. SDPO BHAWAN 47. ASP KATRA 48. ASP REASI 49. RAILWAYS

Railways

Jammu SDPO RLYS. JAMMU

50. SDPO RLYS VIJAYPUR 51. SDPO RlysUDHAMPUR 52. SDPO RLYS KATRA

LIST OF SDPO / ASP OFFICES (KASHMIR)

S. No ZONE RANGE DISTRICT SDPO/ ASP 1 KASHMIR

ZONE Central Kashmir Range Srinagar DySP HQRs

2 SDPO SADDAR 3 SDPO SAHEEDGANJ 4 SDPO KOTHIBAGH 5 SDPO NEHRUPARK 6 SDPO KHANYAR 7 SDPO MR GANJ 8 SDPO HAZRAT BAL 9 ASP SOUTH

10 ASP EAST 11 ASP NORTH 12 ASP HAZRATBAL 13 Ganderbal DySP HQRs GANDERBAL 14 SDPO KANGAN 15 Budgam DySP HQRs 16 SDPO CHARARIE-SHARIEF 17 SDPO MAGAM 18 SDPO KHANSAHAB 19 Leh DySP HQRs LEH 20 SDPO NOBRA 21 Kargil DySP HQRS KARGIL 22 South Kashmir Range Anantnag DySP HQRs 23 SDPO BIJBHERA 24 Kulgam SDPO KULGAM 25 Pulwama DySP HQRs PULWAMA 26 Awantipora SDPO AWANTIPORA 27 Shopian SDPO SHOPIAN 28 North Kashmir Range Baramulla DySP HQRs BARAMULLA 29 SDPO URI 30 SDPO TANGMARG 31 SDPO PATTAN 32 Sopore ASP SOPORE


Page | 273


33 Handwara DySP HQRs HANDWARA 34 Kupwara DySP HQRs KUPWARA 35 Bandipora DySP HQRS BANDIPORA 36 SDPO SUMBAL 37 Railways SP Railways Kashmir SDPO SRINAGAR (RLY) 38 SDPO ANANTNAG (RLY) 39 SDPO BARAMULLA (RLY)

LIST OF DPO OFFICES S. No. ZONE RANGE DISTRICT POLICE OFFICE

1 JAMMU Jammu - Kathua JAMMU 2 KATHUA 3 SAMBA 4 Rajouri - Poonch RAJOURI 5 POONCH 6 Udhampur - Reasi UDHAMPUR 7 REASI 8 Doda - Ramban RAMBAN 9 DODA 10 KISHTWAR 11 KASHMIR Central Kashmir Range SRINAGAR 12 BUDGAM 13 GANDERBAL 14 LEH 15 KARGIL 16 South Kashmir Range ANANTNAG 17 PULWAMA 18 KULGAM 19 SHOPIAN 20 AWANTIPORA 21 North Kashmir Range BARAMULLA 22 KUPWARA 23 HANDWARA 24 BANDIPORA 25 SOPORE


Page | 274


LIST OF RANGE OFFICES S. No. ZONE RANGE

1 KASHMIR ZONE CENTRAL KASHMIR RANGE

2 SOUTH KASHMIR RANGE

3 NORTH KASHMIR RANGE

4 JAMMU ZONE JAMMU KATHUA RANGE

5 UDHAMPUR REASI RANGE

6 POONCH RAJOURI RANGE

7 DODA RAMBAN RANGE

LIST OF ZONE OFFICES S. No. ZONE

1 KASHMIR ZONE

2 JAMMU ZONE

LIST OF PHQ S. No. ZONE

1 KASHMIR ZONE (PHQ)

2 JAMMU ZONE (PHQ)

LIST OF SCRB S. No. SCRB

1 SCRB JAMMU


Page | 275


ANNEXURE XIX – CURRENT STATUS OF CAPACITY BIULDING IN J&K

Name of the Zone Summary of the Total Manpower Trained under CCTNS Project in J&K State Total

Details of Jammu Zone As on 15-03-2011

SSP SP ASP CPO DYSP/SPO INSPR/PO SI ASI HC`s SGCT`s CT`s FOLL`s/SPO`s R/CT`s 3 10 0 2 40 76 192 474 1402 1756 3808 102 229 8094

Details of Kashmir Zone Upto 28-02-2011

0 0 3 2 11 29 72 228 684 730 1401 3 213 3376

Grand Total 3 10 3 4 51 105 264 702 2086 2486 5209 105 442 11470

JK Policecrimebranchjkpolice.nic.in/docs/JK_RFP_Vol-I.pdf · Page | 7 . VOLUME – I: FUNCTIONAL...

Documents

Transcript of JK Policecrimebranchjkpolice.nic.in/docs/JK_RFP_Vol-I.pdf · Page | 7 . VOLUME – I: FUNCTIONAL...