e-governance mission mode project (mmp) rfp for si/cctns si rfp... · 2011-06-08 · the cctns...

SI RFP (Vol-I) for Implementation of CCTNS in Puducherry

RFP for Selection of System Integrator (SI) for

Implementation of

Crime & Criminal Tracking Network and Systems (CCTNS) Project

in

UT of Puducherry

VOLUME–I: Techno – Functional Requirements

Puducherry Police

Government of Puducherry

E-Governance Mission Mode Project (MMP)


Confidential Puducherry Police Page - 2-

Request for Proposal Datasheet:

S No. Information Details

1 RFP reference No and Date 08th June 2011

2 Non Refundable Tender Cost Rs. 5000/-

3 Sale of RFP Document 08th June 2011

4 Earnest Money Deposit (EMD) Rs. 20,00,000/-

5 Last date for submission of written

queries for clarifications

24th June 2011

6 Date, Time & Venue of pre-proposal

conference

04th July 2011 at 11:00 AM at IGP

Conference Hall, Police Headquarters,

Puducherry

7 Release of response to clarifications on 11th July 2011

8 Last date (deadline) for receipt of

proposals in response to RFP notice

11th July 2011 till 12:00 PM at the Office

of IGP, Police Headquarters, Puducherry

9 Place, Time and Date of opening of

Technical proposals received in

response to the RFP notice

11th July 2011 till 3:00 PM at the Office

of IGP, Police Headquarters, Puducherry

10 Place, Time and Date of Technical

Presentation by the bidders

To be intimated later

11 Place, Time and Date of opening of

Financial proposals received in

response to the RFP notice

To be intimated later

12 Contact Person for queries Shri. Atul Katiyar, IPS

Deputy Inspector General of Police,

Office of the SSP (L&O), Puducherry

[email protected]

Ph. 0413-2205303/04

13 Addressee and Address at which

proposal in response to RFP notice is

to be submitted:

The Inspector General of Police,

Police Headquarters

Puducherry

mailto:[email protected]



List of Abbreviations

S No Abbreviation Description

1. ASI Assistant Sub Inspector

2. AWPS All Woman Police Station

3. CAS Core Application Software

4. CB Capacity Building

5. CCIS Crime and Criminals Information System

6. CCTNS Crime & Criminal Tracking Network System

7. CI Circle Inspector

8. CID Crime Investigation Department

9. CIPA Common Integrated Police Application

10. CPMU Central Project Monitoring Unit

11. CRB Crime Record Bureau

12. CRO Crime Record Office

13. DC Data Centre

14. DCRB District Crime Record Bureau

15. DGP Director General of Police

16. DIG Deputy Inspector General

17. DNS Domain Name System

18. DRC Disaster Recovery Centre

19. DSB District Special Branch

20. EMS Enterprise Management System

21. FIR First Information Report

22. FPB Finger Print Bureau

23. FRRO Foreigners Regional Registration office

24. FRS Functional Requirement Specifications

25. G2G Government to Government

26. GoI Government of India

27. GUI Graphical User Interface

28. HC Head Constable

29. HQ Head Quarters

30. HR Human Resource

31. ICT Information and Communication Technologies

32. IG Inspector General

33. IO Investigating Officer

34. IT Information Technology

35. IIF Integrated Investigation Form

36. LAN Local Area Network

37. LLD Low Level Design

38. MHA Ministry of Home Affairs

39. MMP Mission Mode Project

40. MTW Motor Transport Workshop

41. NCRB National Crime Record Bureau

42. NeGP National E-Governance Programme



43. NIC National Informatics Centre

44. NOC No Objection Certificate

45. OS Operating System

46. PC Police Constable

47. PCR Cell Protection of Civil Rights Cell

48. PHQ Police Headquarter

49. PP Puducherry Police

50. PSWAN Pondicherry State Wide Area Network

51. RFP Request for Proposal

52. RTI Right to Information

53. RTO Regional Transport Officer

54. SAN Storage Area Network

55. SB Special Branch

56. SDA Software Developing Agency

57. SDC State Data Centre

58. SDPO Sub Divisional Police Office

59. SHO Station House Officer

60. SI System Integrator

61. SI Sub Inspector

62. SIGMA Specialized Intelligence Gathering Machinery

63. SLA Service Level Agreement

64. SP Superintendent of Police

65. SPMC State Program Management Consultant

66. SPMU State Project Monitoring Unit

67. SQL Structured Query Language

68. SRS System Requirement Specifications

69. SSDG State E-Governance Services Delivery Gateway

70. SSP Senior Superintendent of Police

71. UAT User Acceptance Testing

72. UDR Unidentified Dead Bodies Report

73. UPS Uninterrupted Power Supply

74. UT Union Territory

75. VAC Vigilance & Anti-Corruption Unit

76. VPN Virtual Private Network

77. VRK Vulnerable Record Keeping

78. WAN Wide Area Network

79. WHC Woman Head Constable

80. WSI Woman Sub Inspector



Table of Contents

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

1.1 Project Background --------------------------------------------------------------------------------- 7

1.2 Background of Police Systems in India ---------------------------------------------------------- 8

1.2.1 Crime and Criminal Information System (CCIS) ------------------------------------------ 8

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

1.2.3 Crime and Criminals Tracking Network and Systems (CCTNS) ---------------------- 10

1.3 CCTNS Implementation Framework ------------------------------------------------------------ 12

1.4 Structure of RFP------------------------------------------------------------------------------------- 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 ----------------------------------------------------------------- 14

2.2.1 Vision-------------------------------------------------------------------------------------------- 14

2.2.2 Objectives of the Project --------------------------------------------------------------------- 14

2.3 Stakeholders of the Project ----------------------------------------------------------------------- 15

2.4 Desired Outcome from Various Stakeholders ------------------------------------------------- 15

3. PUDUCHERRY POLICE (OVERVIEW) ------------------------------------------------------------------ 18

3.1 Organization Structure ---------------------------------------------------------------------------- 18

3.2 Existing legacy Systems---------------------------------------------------------------------------- 22

3.3 Existing Data Center Infrastructure ------------------------------------------------------------- 25

3.4 Existing WAN Infrastructure --------------------------------------------------------------------- 26

3.5 Existing Police Stations (CIPA) Infrastructure ------------------------------------------------ 28

3.6 Existing Training Center --------------------------------------------------------------------------- 28

4. Core Application Software (CAS) ---------------------------------------------------------------------- 32

4.1 Volume – I Scope of Services ---------------------------------------------------------------------- 32

4.2 CAS (Center) ----------------------------------------------------------------------------------------- 32

4.3 CAS (UT) ---------------------------------------------------------------------------------------------- 33

4.4 Development of CCTNS Core Application Software (CAS) ---------------------------------- 37

4.5 Technology Stack for CAS (UT) ------------------------------------------------------------------- 37

4.6 Role of Software Developing Agency (SDA) in Supporting CAS ---------------------------- 37

5. SCOPE OF THE PROJECT -------------------------------------------------------------------------------- 41

5.1 Geographical Scope --------------------------------------------------------------------------------- 41

5.2 Functional Scope ------------------------------------------------------------------------------------ 41

5.3 Scope of Services during Implementation Phase --------------------------------------------- 58



5.3.1 Project Planning and Management -------------------------------------------------------- 59

5.3.2 Configuration, Customization and Extension (New Modules) Of CAS (UT) and

Integration with CAS (Center) and External Agencies --------------------------------------------- 62

5.4 Site Preparation at Police Stations and Higher Offices --------------------------------------- 66

5.5 Infrastructure at the Implementation Locations ---------------------------------------------- 68

5.6 Network Connectivity for Police Locations ---------------------------------------------------- 70

5.7 Infrastructure at the Data Center & Disaster Recovery Centre ----------------------------- 72

5.8 Other Requirements -------------------------------------------------------------------------------- 74

5.9 Data Migration and Data Digitization ----------------------------------------------------------- 81

5.10 Capacity Building ----------------------------------------------------------------------------------- 85

5.11 Handholding Support ------------------------------------------------------------------------------ 93

5.12 Requirement on adherence to Standards ------------------------------------------------------ 95

5.13 Support to 3rd Party Acceptance Testing, Audit and Certification ------------------------- 96

5.14 Insurance ------------------------------------------------------------------------------------------- 102

5.15 Scope of Services during Post Implementation Phase ------------------------------------- 102

6. IMPLEMENTATION AND ROLL-OUT PLAN -------------------------------------------------------- 103

7. SERVICE LEVELS ---------------------------------------------------------------------------------------- 105

8. ANNEXURE ----------------------------------------------------------------------------------------------- 106

Annexure 1 – List of all Implementation locations -------------------------------------------------- 106

Annexure 2 – Implementation Location Maps ------------------------------------------------------- 110

Annexure 3 – Locations Details for Network connectivity ----------------------------------------- 112

Annexure 4- Region wise Police Strength for Capacity Building ---------------------------------- 113

Annexure 5 - Case Files for Data Digitization --------------------------------------------------------- 114

Annexure 6- Implementation Plan & Roll out Plan -------------------------------------------------- 117

Annexure 7- Government Structure for Implementation Monitoring --------------------------- 124

Annexure 8 - Post Implementation Support Services ----------------------------------------------- 128

Annexure 9- Functional Requirement Specifications ----------------------------------------------- 133

Annexure 10 – Technology Stacks for CAS (State/UT) and CAS (Center) ----------------------- 168

Annexure 11 – Bills of Material for DC, DR and other locations ----------------------------------- 172

Annexure 12 – Network Connectivity Solution ------------------------------------------------------ 175

Annexure 13 – Technical Specifications (Indicative) ----------------------------------------------- 187

Annexure 14 – Technical Specification of Software for DC and DR ------------------------------- 217

Annexure 15 – Service Levels --------------------------------------------------------------------------- 234

Annexure 16 – PSWAN Connectivity ------------------------------------------------------------------- 252

Annexure 17 – Networking details of Police Station and Other Officers ------------------------ 253



1. INTRODUCTION

1.1 Project Background

Availability of relevant and timely information is of utmost importance in conduct of business

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

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

records pertaining to crime and criminals. Information Technology (IT) can play a very vital role

in improving outcomes in the areas of Crime Investigation and Criminals Detection and other

functioning of the Police organizations, by facilitating easy recording, retrieval, analysis and

sharing of the pile of Information. Quick and timely information availability about different

facets of Police functions to the right functionaries can bring in a sea change both in Crime &

Criminals handling and related Operations, as well as administrative processes.

Creation and maintenance of databases on Crime & Criminals in digital form for sharing by all

the stakeholders in the system is therefore very essential in order to effectively meet the

challenges of Crime Control and maintenance of public order. In order to achieve this, all the

State/UTs should meet a common minimum threshold in the use of IT, especially for crime &

criminals related functions.

The CCTNS project is to be implemented in a manner where the major role would lie with the

Puducherry Governments in order to bring in the requisite stakes, ownership and commitment,

and only certain core components would be in the hands of the Central Government, apart from

the required review and monitoring of project implementation on a continuing basis.

With the launching of CCTNS, the erstwhile Common Integrated Police Application (CIPA)

programme would be subsumed into it in a manner that the work already done there under is

not disrupted. So far, 2,760 police stations, out of a total of around 14,000 police stations across

the country, have been covered under the Scheme.

The broad objectives of the CCTNS project are streamlining investigation and prosecution

processes, strengthening of intelligence gathering machinery, improved public delivery system

and citizen-friendly interface, nationwide sharing of information across on crime and criminals

and improving efficiency and effectiveness of police functioning. It will also:

1. Facilitate collection, storage, retrieval, analysis, transfer and sharing of data and

information among Police Stations, District, State/UT Headquarters and other

organization/agencies, including those at Government of India level.

2. Help in enabling and assisting the senior Police Officers in better management

of Police Force.

3. Help in Keeping track of the progress of the crime and criminal investigation

and prosecution Cases, including progress of cases in the court.

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



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

1.2 Background of Police Systems in India

Several initiatives have been introduced in the past to leverage IT in police functioning. Some of

these initiatives include centrally initiated programs such as the NCRB-led CCIS (Crime and

Criminals Information System) and CIPA (Common Integrated Police Application), and

State/UT-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 State’s such as Andhra Pradesh, Karnataka and

Gujarat, through State -led initiatives.

1.2.1 Crime and Criminal Information System (CCIS)

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

implemented in 35 State/UTs and Union Territories and spans over 700 locations. Most of the

State/UT 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/UT Crime Records Bureaus (SCRB) and District Crime Records Bureaus (DCRB) and to

facilitate statistical analysis of crime and criminals related information with the State/UTs 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 State 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/UT Police Forces (MPF)” scheme of the Ministry of Home Affairs. The

aim of CIPA is to bring about computerization and automation in the functioning at the police



station with a view to bringing in efficiency and transparency in various processes and functions

at the police station level and improve service delivery to the citizens. So far about 2,760 police

stations, out of a total of 14,000+ police stations across the country, have been covered under

the scheme.

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

crime investigation and prosecution functions. CIPA is a centrally managed application: an

application core centrally developed and installed in police station. Any State/UT-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.

MIS on CIPA Implementation:

A Management Information System on CIPA is developed for the entire UT to monitor the CIPA

implementation. On every day basis, the STA or the CIPA personnel will enter the CIPA issue for

a police station. If the issue could be resolved by the STA, the details are entered. The details like

number of FIR entered software issue if any, functional problems, and hardware complaints of a

Police station and call attended details like M/s. Acer are fed into the system.

The issues are categorized as

1. Hardware Problems

2. Software Problems

3. Backup Problems

4. Font Problems

5. Miscellaneous

6. Details of Police Officials trained

Customization of CIPA:

In CIPA, the core software for all the basic modules are designed and developed by NIC, Delhi.

This software has functional modules common to the entire country. But, there are some

additional reports, fields and queries which are state specific. For Puducherry, the CIPA

implementation committee had forwarded several such bugs in the software, additional

modules and enhancements in the software time-to-time. To start with, the CIPA V12B was

introduced to all police stations. As on 01/01/2010, The CIPA V17C is the version used in all the

police stations in UT. Some of the local requirements which are incorporated in the latest

release of CIPA are:



1. Missing Acts and Sections

2. Printing options of CD

3. Missing Police Stations

4. Printing of Witness Statement

5. Few reports related to MLCs

6. Additional character widths for few fields

The issues are time to time taken care during CIPA implementation and the new release of CIPA

which carries out such amendments is installed in all the police stations. A portal URL

http://eitsm.nic.in/cipa is made available by CIPA development team for uploading the issues

and suggestions as part of the local customization. If bugs are reported, they are amended in the

revised versions. Similarly, all suggestions and customization requirements are amended with

the consultation of NCRB.

Data Replication for Data Integration:

It is desired by the CIPA implementation committee to integrate all the CIPA data with one

server for building a MIS on CIPA data. For this purpose, NIC, Puducherry developed an

integration model for all Police stations using Data Replication technology. The advantages of

such integration of all Police stations data are:

1. Instant information of all Crime Occurrences for a day for the entire UT

2. Search the details of the accused/complainant across all the Police stations

3. Quick retrieval of the details of the case

4. Auto generation of all statutory reports of the Police Stations for CRB

5. Cross tab reports for comparison of crime rates

6. Comprehensive search mechanism on Acts/Section, Police stations, date of

occurrence, modus operandi etc.

7. Search on stolen vehicles based on type of vehicles, vehicle registration number,

Chassis/engine number also connectivity to RTO database

8. Crime Analysis for a particular police station

9. Retrieval of details of seized property

1.2.3 Crime and Criminals Tracking Network and Systems (CCTNS)

The Crime and Criminal Tracking Network and Systems (CCTNS) is a Mission Mode Project

conceptualized and sponsored by the Ministry of Home Affairs (MHA) in detailed consultation

with all stakeholders and adopt the guidelines of the National E-governance Plan (NeGP).

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

efficiency and effectiveness of policing at the Police Station level through adoption of principles

of e-Governance, and creation of a nationwide networked infrastructure for evolution of IT-

enabled State -of-the-art tracking system around “investigation of crime and detection of

criminals” in the real time. This is a critical requirement in the context of the present day

internal security scenario.

http://eitsm.nic.in/cipa



The scope of CCTNS1 spans all 35 State/UTs and Union Territories and covers all Police Stations

(14,000+ in number) and all Higher Police Offices (6,000+ in number) in the country. The

CCTNS project includes vertical connectivity of police units (linking police units at various levels

within the UT – Police Stations, District Police offices, Police headquarters, CRB and other police

formations – and UT, through Police headquarters and CRB, to NCRB at GOI level) as well as

horizontal connectivity, linking police functions at State/UT and Central level to external

entities. CCTNS also provides for a citizen’s interface to provide basic services to citizens.

The Project would facilitate collection, storage, retrieval, analysis, transfer and sharing of data

and information among police stations, district, and Police headquarters and other organization

or agencies, including those at Government of India level wherein thousands of police stations in

India are to be linked through a tracking network in a bid to boost connectivity between

stations and enhance crime-fighting capabilities.

The following figure is a simplistic representation of the ‘Change’ in policing system envisaged

under the CCTNS project. In the existing system, most of the police function and systems are

manual and paper based. The interaction of citizen with department and also of various offices

within the department is either through physical presence of individuals or through the post –

commonly known as ‘Dak System”.

In the CCTNS scenario, certain services of police department for citizens would become online

and could be accessed / requested through web. Also, the associated workflow of police

processes would become automated. Connectivity would be provided till police station level and

all higher offices would be connected either through State Data Centre or Police Data Centre (in

case State Data Centre is not ready). The department would further be connected centrally with

other police offices in all the States / U.Ts and centre as well as with NCRB and MHA at the



central level. This envisaged scenario would lead to integrated policing system across the

country.

1.3 CCTNS Implementation Framework

CCTNS would be implemented in a way where the State/UT plays a major role. CCTNS would be

implemented in alignment with the NeGP principle of “centralized planning and de-centralized

implementation”. MHA and NCRB would play a key role in planning the program in

collaboration with the Police leadership within State/UT, in the development of a few core

components and in monitoring and reviewing the program. It is, however, the State/UT that

would drive the planning and implementation at the State/UT level.

The role of the Centre (MHA and NCRB) focuses primarily around planning, providing the core

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

State/UTs, managing and monitoring the program at a higher level. State/UTs would drive the

implementation at the State/UT 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/UT level is the “bundling of services”

concept. According to this, each State/UT selects one System Integrator (SI) who would be the

single point of contact for the State/UT 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.4 Structure of RFP

The RFP document consists of three volumes:

RFP Volume I: Technical and Functional Requirements

RFP Volume II: Commercial and Bidding Terms

RFP Volume III: Contractual and Legal Specifications

This is the Volume I of the SI RFP that comprises Techno-functional Requirements for the

implementation of CCTNS project.

1.5 Goals of this RFP

The primary goal of this RFP is solicit proposals from the interested bidders to be selected as

the System Integrator (SI) for the UT of Puducherry through a competitive bidding process. This

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

requirements that are deemed necessary to share with the potential bidders. The goals of RFP

are further elaborated below:



To seek proposals from potential bidders for providing the “bundle of services” in

implementing and managing the CCTNS solution in the UT of Puducherry.

To understand from the bidders how they propose to meet the technical and operational

requirements of CCTNS.

To ascertain how potential bidders propose to deliver the services and sustain the

demand and growth in the requirements.

To ascertain from bidders on how they will ensure scalability and upgradeability of the

infrastructure and solution proposed to be deployed.

To understand from the bidders as to how they intend to innovate further on this

service delivery model.

The Puducherry Police, (through CCTNS Apex Committee and Empowered Committee) shall be

the final authority with respect to qualifying a bidder through this RFP. Their decision with

regard to the choice of the System Integrator (SI) who qualifies through this RFP shall be final

and the Puducherry Police reserves the right to reject any or all the bids without assigning any

reason. The Puducherry Police further reserves the right to negotiate with the selected agency

to enhance the value through this project and to create a more amicable environment for the

smooth execution of the project.



2. PROJECT OVERVIEW

2.1 Need for the Project

The Ministry of Home Affairs has conceptualized the Crime & Criminals Tracking Network and

Systems (CCTNS) project as a Mission Mode Project under the National e-Governance Plan

(NeGP). This is an effort of the Government of India to modernize the police force giving top

priority to citizen services, information gathering, and its dissemination among various police

organizations and units across the country.

A need has been felt to adopt a holistic approach to address the requirements of the police,

mainly with relation to functions in the police station and traffic management. There is also a

need to strengthen the citizen interfaces with the police. Interfaces need to be built with

external agencies like courts, transport authorities, hospitals, and municipal authorities etc to

be able to share information between departments. Therefore, it becomes critical that

information and communication technologies are made an integral part of policing in order to

enhance the efficiency and effectiveness of the Police Department.

In order to realize the benefits of e-Governance fully, it is essential that a holistic approach is

adopted that includes re-engineering and standardizing key functions of the police and creating

a sustainable and secure mechanism for sharing critical crime information across all police

formations. The CCTNS has been conceptualized in response to the need for establishing a

comprehensive e-Governance system in police stations across the country.

2.2 Vision and Objectives of Project

2.2.1 Vision

2.2.2 Objectives of the Project

The overall objective of the CCTNS 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:

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.

“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”



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 UT in order to increase the effectiveness in

dealing with criminals across the UT borders.

2.3 Stakeholders of the Project

The impact of the police subject being sensitive, a consultative and a bottom-up approach has to

be adopted in designing the MMP impacting the following stakeholders:

Citizens and Citizen groups

Puducherry Police

Ministry of Home Affairs (MHA) and National Crime Records Bureau (NCRB)

External Departments such as Jail & Jurisdiction, Passports Office, Transport

Department, and Hospitals, District Administration, Department of Medical Education

and Research

Non-Government/ Private Sector organization

2.4 Desired Outcome from Various Stakeholders

The following are the expected benefits envisaged from successful implementation of the MMP:

S. No Stakeholder Benefits

1. Citizens Multiple channels to access services from police like, Web,

Call centre and Police dept Office to access the some

services they need. This would save them a lot of time and

effort and would ensure convenience to each citizen.

Simplified process for registering and tracking petitions

and FIRs

Simplified process for accessing general services such as



requests for certificates, verifications, and permissions

Simplified process for registering grievances against police

Simplified process for tracking the progress of the case

during trials

Simplified access to view/report unclaimed/recovered

vehicles and property

Improved relationship management for victims and

witnesses

Faster and assured response from police to any emergency

calls for assistance

The Citizen would get the benefit as the processes will

become quick and efficient. It has been envisaged that the

citizens would be provided with quick and easy access to

the desired services

Citizens would be having the flexibility of obtaining status

of its application/service request immediately on request.

Citizens would also get the advantage of various payment

options and channels through various payment interfaces

2. Police

Department

Enhanced tools for investigation

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 and

traffic) to reach the officers on the field

Reduced workload of the police station back-office

activities such as preparation of regular and ad-hoc reports

and station records management

Enhanced tools to optimize resource allocation for patrols,

emergency response, petition enquiries, and other general

duties

A collaborative knowledge-oriented environment where

knowledge is shared across the 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

Automated system would save the efforts of the officials in

various day to day tasks.

Automation of Search of Documents will facilitate

convenience for the Police officials

Speedy recovery of data and impounding will be possible

due to instant access to data.



Timely Report generation with all desired fields would be

possible through the automated system. This will help the

decision makers of the Department in prompt decision

making & progress tracking.

Multiple access channels for the citizens would lead to

reduce rush and chaos at various offices across the UTs.

3. Police

personnel

Balanced performance evaluation metrics and framework

Simplified process for registering grievances within the

department

4. Police officials Balanced performance evaluation metrics and framework

Simplified process for registering grievance within

department

Simplified process for personnel’s administrative services

such as leave, pay-roll, loans, and bill claims

Integrated view of the service record that presents the

performance feedback and training needs

5. External

Departments

Seamless integration with police systems for better citizen

service delivery and improved law enforcement

6. Ministry of

Home Affairs &

NCRB

Standardized means of capturing the crime and criminal

data across the police stations in the country

Faster and easier access to crime and criminal information

across the country in a manner amenable for trend and

pattern analysis

Enhanced ability to detect crime patterns and modus

operandi across the UTs and communicate to the UTs police

departments for aiding in crime prevention



3. PUDUCHERRY POLICE (OVERVIEW)

3.1 Organization Structure

Puducherry Police holds a strong force more than 3000 personnel and with 48 Police Stations

(41 - CIPA Police Stations + 7 – Non-CIPA Police Stations) across the Union Territory. It plays an

important role in prevention and detection of crime, maintenance of law and order across the

UT and in bringing offenders to justice. The department has a high Government-to-Citizen

(G2C) interaction.

The UT of Puducherry consist areas of Puducherry, Karaikal, Mahe and Yanam.

The Inspector General of Police (IGP) is the head of the Puducherry Police and fully responsible

for the maintenance of discipline and for efficient discharge of duties by all ranks in the

department.

The Inspector General of Police for the Union Territory of Puducherry consists of 6 regions

namely, Puducherry (North), Puducherry (South), Puducherry (Rural), Karaikal, Mahe and

Yanam. Inspector General of Police holds the administrative control of Puducherry Police

assisted by Deputy Inspector General of Police. The organization is divided into two segments: I)

Law and Order and ii) Crime and Intelligence. Each unit and sub-divisions are under

Superintendent of Police. The disciplinary and administrative control is under the Inspector

General of Police, Puducherry.

SP (PCR)

SSP (C&I)

SP (MT)

SP (SB)

SP - Sig - I nt

SP (CID)

SP (Wireless)

IGP

SSP(HQ) - cum - CMT IRBn

DIG

Dy CMT (IRBn)

SSP (KKL)

SP (KKL)

SSP (L&O)

SP (North)

SP (Rural)

SP (Traffic)

SP (Mahe)

CI (Yanam)

SP (South)

SP (HQ)

SP (POP)

SP (HG)

SP(PTS)

CMT (PAP)

SP - Sig - Sec



Law and Order

The Law and Order wing consisting of six regions (sub-division), each under the control of one

Superintendent of Police, except Yanam region is under the control of Circle Inspector of Police.

The Puducherry & Karaikal Districts are under the control of Senior Superintendent of Police.

Armed Police under the control of SP (PAP) is divided into 5 company’s each headed by the

officer in the rank of Inspector of Police. The Armed Police has been assigned Detachment Duty

at other regions of U.T. of Puducherry.

The Senior Superintendent of Police (SSP) exercises supervision and coordinates the work of

the superintendents of police of Puducherry and Karaikal. The SSP exercises the same powers

and responsibilities of a District superintendent of Police within the UT.

Crime and Intelligence

The Crime and Intelligence Wing functions are under the overall supervision of the Senior

Superintendent of Police (Crime and Intelligence). There are eight units in this wing e.g. Special

Branch, CID, SIGMA (Security) etc. Each unit is headed by the officer in the rank of

Superintendent of Police.

The Superintendent of Police (SP) is in-charge of the area for which the SP is appointed for

supervising investigation of crimes and maintaining law and order. The SP also exercises a

control over the work of Circle Inspectors and Station House Officers. All communications

between magistrates and police force must be conveyed through the SP.

The Circle Inspector (CI) is in-charge of a police circle. The CI is primarily responsible for

maintenance of law and order in the respective circle and for supervising the work of

investigation, detection and prevention of crime.

The following diagram depicts the organizational hierarchy at the Senior Superintendent of

Police office level in Puducherry



SSP

SP

Circle

Inspector

Inspector

At the Senior Superintendent of Police office level the SSP heads the office, and staffed by

Superintendent of Police (SP), Circle Inspector (CI), Inspector.

The following diagram depicts the organizational hierarchy at the Superintendent of Police

office level in Puducherry

SP

Circle

Inspector

Inspector

Sub -

Inspector



At the Superintendent of Police office level the SP heads the office, and staffed by Circle

Inspector (CI), Inspector and Sub-Inspector.

The following diagram depicts the organizational hierarchy at the Police Station level in

Puducherry

SHO/SI

ASI

Head

Constable

Police

Constable

At the Police Station level the SHO/SI heads the station, and staffed by Asst. Sub –Inspector

(ASI), Head Constable (HC) and Police Constable (PC).

The Nodal officer appointed for the CCTNS Project / Bid Management:

Contact Person Shri. Atul Katiyar, IPS

Deputy Inspector General of Police

Contact Details Office of SSP (L&O), Puducherry

Ph – 0413 2205303/04

e-mail – ssplo.pon.nic.in

Please refer Annexure-1 for details of Implementation locations (Organizational Units)

considered under CCTNS Project.



3.2 Existing legacy Systems

Existing Applications in Puducherry Police

Crime and Criminal Information System CCIS

1 Name and description of the Legacy

System

Application manages

information about crime and

criminal by digitizing 7 IIFs

used for a case; of all the Police

stations across the state

Create crime and criminals

related database and provide

information

2 Whether this application will be

migrated or continue to run and

needs to be integrated with the new

solution to be developed as part of

this RFP

Needs to be migrated with the New

Solution developed

3 System Functionality Stand alone / non web based

System

OS-Unix/Windows

Database- Ingress

4 Current No of users NA

5 Details on the architecture,

technology platform of the system

Decentralized (Client-Server

Architecture)

6 Deployment details – Geographical

reach, Number of Police Stations

covered

NA

7 Current data available in the system

and whether the data can be used

during data migration

Data is not available in the system. All

the data if given to NCRB and no

backup of data is available in

Puducherry

8 Issues and challenges relating to the

functioning and usage of legacy

system

CCIS‘s data is incompetent and unreliable due to lack of interest of police officials while filling the data into the system.



Common Integrated Police Application CIPA


System

FIR registration CIPA was considered as a major

step towards computerization of police stations and developed to provide automated working on crime registration, Investigation, Prosecution, management of police station register‘s records. It provides customized reports on specific needs of Police stations.





this RFP


Solution developed

3 System Functionality Stand alone / non web based

System

OS- Linux

Database- PostgreSQL

4 Current No of users Approx. 76 (38*2)



Decentralized (Client-Server

Architecture)



covered

CIPA is available in 38 Police Stations




Data is available in the system and it

should be migrated



system

It‘s a decentralized application; each police station manages their data separately. All the desired (State specific) reports were not achieved in it. Instantaneous access on particular record of any location is not available for higher level. Limited facilities for PS.



Payroll System Payroll


System

Pay roll System is for police and IRBN





this RFP


Solution developed

3 System Functionality Web Based System

OS- Windows

Frontend – Dot Net

Backend – SQL

4 Current No of users 3000 users for Police Personnel

approx.

1000 users for Home guards approx.

1000 users for IRBN approx.



NA



covered

NA




NA



system

NA



DCR Online DCR (MHA)


System

Data are fed using this software in the MHA on regular basis





this RFP


Solution developed

3 System Functionality Web Based System

4 Current No of users NA



NA



covered

NA




NA



system

NA

3.3 Existing Data Center Infrastructure

The work on preparation of State Data Centre (SDC) is underway. The SDC is located at Kalapet,

Puducherry region and functioning as a centralized location to host all the IT initiatives in the

UT. It would act as a mediator and convergence point between the open unsecured public

domain and sensitive Government environment. The SDC enables various government

departments to host their services/applications on a common infrastructure leading to ease of

integration and efficient management, ensuring that computing resources and it supports

connectivity infrastructure under (PSWAN) Puducherry State Wide Area Network. It is

adequately and optimally used. The SDC is equipped with state of the art Data Security, System

Security, and Internet Security, Redundant Power supply, Access Control System, Air-

conditioning and other infrastructure. The Data Center in the SDC would host the CCTNS Core

Application for UT if hardware requirements are supplied to it as a Co-located Model.



The Existing infrastructure available at Data Center as follows:

Item Item Description (Make/Model)

Unit of measurement

Quantity (Units)

Web Server HS 22 NA 1 Database Server P 550 NA 1

Antivirus Server HS 22 NA 1

Application Server Blade HS 22 NA 1

Tape Library TS 3310 NA 1

Rack Cyberack 420 (Black) NA 1

3.4 Existing WAN Infrastructure

All Police stations in Puducherry are having individual BSNL Broadband connectivity for e-mail

and other uses. The Headquaters of the four regions have PSWAN connectivity. The Puducherry

police may consider alternate ISP to meet contigency is required as secondary connectivty to all

the Police Stations and Higher offices. Currently implementation of PSWAN is in progress and is

used by few other departmental headquarters equipped with necessary networking

infrastructure. Full implementation of PSWAN connecting upto blocks level, is expected in the

future and will become a strong backbone in Puducherry.

Please refer Annexure-16 for detailed PSAWAN Connectivity in Puducherry

PSWAN is a very ambitious project to provide the UT with a basic information technology

backbone which will be utilized for carrying voice, data and voice traffic facilitating

interdepartmental communication and data sharing within the UT. PSWAN will be a safe, fast,

reliable and cost effective network connecting all the blocks of the UT through a hybrid network

consisting of WiMax, leased line and other network technologies on a Public-Private

Partnership mode and operating on a Build-Operate-Transfer (BOT) model. The project enables

instant online interaction among government departments / agencies resulting in obtaining

reports on a real time, improving the workflow processes and the pace of decision-making.



The above diagram is showing the layered Architecture of Wide Area Network connectivity.

Here the last mile or horizontal connectivity to be extended towards nearest POP of SWAN.

From the police stations or locations 512 Kbps lease circuit is suggested as the secondary

connectivity. All the Police Stations & Higher offices have broadband connectivity which will be

considered as Primary connectivity. Only few offices will have 2 Mbps primary and 2 Mbps

secondary leased line connectivity in the same manner.

The Disaster recovery center will be connected by 2 Mbps lease circuit primary and

secondary from SWAN State HQ, hence during any failure of State Data Center, the traffic will

be diverted towards Disaster Recovery without any single point of failure. There should be one

separate 2 Mbps primary Lease circuit and 2 Mbps secondary Lease circuit directly

connected to State Data Center for active replication of Disaster Recovery Center in a same

redundancy manner from service provider prospective.

The CCTNS, CAS application to be replicated with Delhi Central server as per NCRB guidelines.

For this purpose there should be one 2 Mbps primary lease circuit from BSNL and 2 Mbps

lease circuit backup from other service provider or from a different BSNL exchange to be

connected with CCTNS core router and that will be placed at State Data Center.



3.5 Existing Police Stations (CIPA) Infrastructure

The below table represents the status of IT infrastructure made available under Police

modernization and CCIS in Districts

Existing Infrastructure for CIPA

3.6 Existing Training Center

There is only one dedicated Training center for Puducherry Police i.e. Police Training School

(PTS) located at Police Complex, Puducherry. There is no basic infrastructure for Computer

training.

Total 274 Police Personnel’s has been training under Level I (Basic Computer training)

Course

Puducherry 72

Karaikal 100

Mahe 39

Yanam 63

Total 274

Status of the Computer Training for Police Personnel (Level-I) conducted in the four

regions of U.T. of Puducherry as on 05-04-2011

CIPA Infrastructure Information

S. No Device / Components Location Utility Configuration No. of Components

1 Desktops 41 PS CIPA Linux Based 164

2 Laser printers 41 PS CIPA HP 41

3 Multi function printer (printer /scan /copy)

41 PS CIPA HP 41

4 8 Port Switch 41 PS CIPA - 41

5 UPS 41 PS CIPA 3 KVA 41


S. No

Region No of batches conducted

Total officials trained

Cadre wise split-up Remarks

SSP SP Inspector S.I /A.S.I

H.C P.C Total

1 Puducherry 5 72 0 3 4 11 12 42 72 Each batch consists of 20 candidates, In Yanam, we have completed Level-I, Karaikal one more batch to be conducted and Mahe two more batches to be conducted. We have to concentrate in Puducherry Region

2 Karaikal 6 100 0 0 0 6 2 83 100

3 Mahe 2 39 0 1 1 6 2 27 39

4 Yanam 3 63 1 5 3 54 63

Total 16 274 0 4 6 28 19 206 274

Status of the Computer Training for Police Personnel (Level-I) conducted in Puducherry as on 05-04-2011

S.No Region Batch Total officials trained

Cadre wise split-up Date of Commencement

Date of Exam

Remarks

SSP SP Inspector S.I /A.S.I H.C P.C Total

1 Puducherry I 13 1 1 10 13 14-06-2010 15-07-2010 Out of 20 per batch only 13 were attended

II 16 1 1 1 4 9 16 14-06-2010 15-07-2010 Out of 20 per batch only 16 were attended

III 8 1 2 2 3 8 29-10-2010 1/11/2010 Commenced two batches, Batch-II only 8 were attended, No one is attended in Batch-IV

IV 19 1 1 4 2 11 19 14-02-2011 14-03-2011 One officer was not attended out of 20 officers

V 16 1 1 3 2 9 16 14-02-2011 14-03-2011 One officer was not attended out of 20 officers

Total 5 72 0 3 4 11 12 42 72


Status of the Computer Training for Police Personnel (Level-I) conducted in Karaikal as on 05-04-2011


Cadre wise spilit-up Date of Commencement

Date of Exam Remarks

SSP SP Inspector S.I /A.S.I H.C P.C Total

1 Karaikal I 20 4 1 15 20 27-09-2010 29-10-2010 Morning 7.00 AM to 10.00 AM

II 19 2 17 19 Evening 6.00 PM to 9.00 PM

III 17 17 17 8/11/2010 8/12/2010 Morning 7.00 AM to 10.00 AM

IV 18 1 1 16 18 Evening 6.00 PM to 9.00 PM

V & VI

26 2 6 18 26 28-01-2011 8/3/2011

Total 5 100 0 3 4 11 12 42 100

Status of the Computer Training for Police Personnel (Level-I) conducted in Mahe as on 05-04-2011


Cadre wise spilit-up Date of Commencement

Date of Exam Remarks


H.C P.C Total

1 Mahe I 20 1 1 2 4 12 20 28-02-2011 29-03-2011

II 19 4 15 19 One Officer not attended the training

Total 39 0 1 1 6 2 27 39



Status of the Computer Training for Police Personnel (Level-I) conducted in Yanam as on 05-04-2011

S. No

Region Batch Total officials trained

Cadre wise split-up Date of Commencement

Date of Exam


H.C P.C Total

1 Yanam I, II & III

63 1 5 3 54 63 26-02-2011 To be conducted in the 3rd week of April 2011, due to General Elections Exam is

postponed

Total 1 5 3 54 63


4. Core Application Software (CAS)

The CCTNS application software will contain a “core” for the State/UTs that are common across

all 35 State/UTs. The CCTNS Core Application Software (henceforth referred to as CAS) will be

developed at NCRB premises and provided to State/UTs for deployment. Each State/UT would

customize the CAS according to their unique requirements and thereafter commission the same.

States and UTs also have an option to bridge the other applications they develop and deploy as

additional applications over and above the customized CAS. The choice of such applications lies

exclusively with the State/UT.

The Core application Software (CAS) is expected to be ready by July 2011.

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

by the Software Development Agency (SDA) at the Center. The details provided here should be

read in conjunction with the RFP and the associated addendums issued by NCRB for the

selection of the Software Development Agency for the Design, Development and Management of

CCTNS Core Application Software (CAS).

4.1 Volume – I Scope of Services

a) Annexure-10 - Functional Requirements

b) Annexure-10 - Functional Requirements - Wire Frames

c) Annexure-- Non Functional Requirements

d) Annexure-11 - Technical Requirements

The functional requirements and the technical architecture of the CAS (State/UT) 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/UT).

4.2 CAS (Center)

CAS (Centre) would cater to the functionality that is required at the GoI level (by MHA and

NCRB). CAS (Centre) would enable NCRB to receive crime and criminals’ related data from

State/UTs in order to organize it suitably to serve NCRB’s requirements and to provide NCRB

with the analysis and reporting abilities to meet their objective as the central level crime and

criminals’ data repository of the nation. This would address the crime and criminals related

information needs of MHA, NCRB, the Parliament, and central government ministries and

agencies, citizens and citizen groups. CAS (Centre) also facilitates the flow if crime and criminals

information across State/UTs is needed on a need-basis. CAS (Centre) will be developed and

deployed at NCRB. Also, CAS (Centre) is expected to interface with external agencies such as

passports, transport authorities, etc.



Overview of Services for CAS (Center)

i) UT-CRB-NCRB Data Transfer and Management

The service shall enable the NCRB to receive, transform, and collate the crime, criminal, and

related data from UTs, to organize it suitably to serve NCRB requirements.

ii) Crime and Criminal Reports

The service shall enable authorized personnel to generate the reports and perform analysis

on the central crime, criminals, and related data repository of the nation.

iii) Crime and Criminal Records and Query Management

The service shall enable the authorized personnel to view various registers and perform basic

and advanced queries on the central crime, criminals, and related data repository of the

nation.

iv) Talaash Service

The service will enable the user to search for missing persons across a central/ national

database.

v) Person of Interest

The service will enable the user to search for persons of interest such as persons wanted on

outstanding warrants, accused, charged habitual offenders, convicts, etc. across the national

database.

vi) Registered Vehicle and Vehicle of Interest Service

The service will enable the user to search for registered vehicles and vehicles of interest such

as, missing / stolen vehicles, abandoned / unclaimed vehicles, and vehicles involved in traffic

incidents across the national database.

vii) Publication Service

This functionality will help the NCRB to publish the periodic crime reviews to the NCRB

portal.

viii) NCRB Citizen Interface

The service shall enable the citizens to access/ search the NCRB National Database on the

data (ex, Stolen Vehicles / Property, Missing Persons, etc.) that is approved to be made

accessible to public.

ix) NCRB Interface for RTI

Due to the sensitivity of the information that pertains to national security and harmony, this

service shall enable a limited and restricted access to the authorized external stakeholders to

search the NCRB National Database, upon submission of any RTI requests.

4.3 CAS (UT)

CAS (State/UT) covers functionality that is central to the goals of CCTNS and is common to all

State/UTs. It would focus primarily on functionality at police station with special emphasis on

crime investigation, criminal’s detection and sharing and dissemination of information. This

part would be developed at NCRB and provided to the State and UTs for configuration,

customization and enhancements / extensions. The UT would determine the requirements for

configuration, customization and enhancements/ extensions. The following are the main

function blocks that would comprise CAS (UT):



Registration

Investigation

Prosecution

Records Management

Search and Basic Reporting

CAS (State/UT) will also include the functionality required at Higher Offices such as UT Police

HQ, District HQ (2), Regional HQ(6) and CRB.

It is envisioned that CAS (State/UT), once operational, will significantly enhance the outcomes

in core police functions at Police Stations. It will do so primarily through its role and event-

orientation, providing role based user access and controls and an event driven interface that

helps police personnel (playing different roles) in more effectively performing their core

functions and that relieves police personnel from repetitive tasks that claim much of their time

while returning low or no value.

In order for CAS (State/UT) to achieve the above goals, it is envisaged to meet the following

requirements:

It will lay special emphasis on the functions at police stations with focus on usability and

ease of use of the application.

It will be designed to provide clear and tangible value to key roles at the Police Station:

specifically the SHO (Station House Officer), the IO (Investigation Officer) and the

Station Writer.

It will be event and role-driven. Access controls will be developed and role based access

will be provided in the application.

It will be content/forms-based, with customized forms based on requirements.

It will be a flexible application system where actions on a case can be taken as required

without rigid sequence / workflows.

It will eliminate the need for duplicate and redundant entry of data, and the need for

repetitive, manual report preparation , thus freeing valuable time and resources for the

performance of core police functions

It will be intelligent and help police perform their roles by providing alerts, highlighting

key action areas, etc.

It will provide the ability to view and exchange information amongst Police Stations,

between Police Stations and other Police formations and with external entities including

citizens.

Relevant reporting and data requirements of higher offices must be met at the State Data

Centre/CRB level and not percolate to the police station level.

Central facilitation and coordination; however CAS (State/UT) will be primarily driven

and owned by UT where UT can configure and customize the CAS for their unique

requirements without the intervention of the central entity



Overview of Services in CAS (UT)

i. Citizens Portal Service

This service shall enable Citizens to request services from Police through online

petitions and track status of registered petitions. Citizen’s 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, Foreigners Regional Registration Status etc.

ii. Petition Management Service

The service shall enable the police personnel to register and process the different kinds

of general service petitions and complaints.

iii. Unclaimed / Abandon Property Register Service

The service shall enable the police personnel to record and maintain

unclaimed/abandoned property registers and match unclaimed/ abandoned property

with property in lost/stolen registers.

iv. Complaint and FIR Management Service

The service shall enable the police personnel to register and process the complaints (FIR

for cognizable complaints, Non-Cognizable Report for non-cognizable, Complaint Report

for genera complaints, etc.) reported by the public.

v. PCR Call Interface and Management Service

The service shall enable the police personnel to register and process the complaints as

received through the Police Control Room through the Dial 100 emergency contact

number.

vi. Investigation Management Service

The service shall enable the police personnel to process the complaints through

capturing the details collected during the investigation process that are required for the

investigation officer to prepare a final report.

vii. Court and Jail Interface and Prosecution Management Service

The service shall enable the police personnel to interface with the courts and jails during

the investigation process (for producing evidence, producing arrested, remand etc) and

during the trial process.

viii. Crime and Criminal Records and Query Management Service

The service shall enable the police personnel to view various registers and perform

basic and advanced queries on the crime and criminal information.



ix. Police Email, Messaging Service, IP tracking and SMS tracking, Call Analysis tracking

The service shall enable the police personnel to send / receive official as well as

personal correspondence.

x. Periodic Crime, Law and Order Reports and Review Dashboard Service

The service shall enable the police personnel to view relevant reports and dashboards

and to conduct periodic crime, and law & order reviews of the police station(s) under

the officer’s jurisdiction.

xi. Notification of Alerts, Important Events, Reminders and Activity Calendar or Task

Services

The service shall capture / generate the required alerts, important events, reminders,

activity calendar and tasks.

xii. UT CRB-NCRB Data Transfer and Management Service

The service shall enable the State/UTs to collate, transform and transfer the crime,

criminal, and other related data from UT to NCRB.

xiii. UT CAS Administration and Configuration Management Service

The service shall enable the individual UT to configure/ customize the application to suit

to their unique requirements.

xiv. User Help and Assistance Service

The service shall enable the end user to view the help manuals of the application and in

guiding the end user in using the application.

xv. User Feedback Tracking and Resolution Service

The service shall enable the police personnel in logging the issues/defects occurred

while using the system.

xvi. Activity Log Tracking and Audit Service

The service shall capture the audit trail resulting from execution of a business process or

system function.

xvii. User Access and Authorization Management Service

The service shall enable the administrative user in setting the access privileges and will

provide authentication and authorization functionality



4.4 Development of CCTNS Core Application Software (CAS)

CAS (Centre) and CAS (State/UT) will be developed at NCRB under the overall guidance and

supervision of MHA, and a dedicated team from NCRB under the supervision of National

Informatics Centre (NIC). NCRB, on behalf of MHA, will engage a professional software

development agency (SDA) to design and develop CAS (Centre) and CAS (State/UT) and offer

associated services. The SDA would enhance and maintain CAS (Centre) and CAS (State/UT)

until the end of the engagement with NCRB and subsequent to that, CAS (Centre) and CAS

(State/UT) would be managed by NCRB under the guidance of NIC, DIT and MHA and CAS

(State/UT) would be managed by the State under guidance of the State IT Department.

CAS (State/UT) 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 State/UTs with the flexibility to build their

UT specific applications around it and in addition to it. CAS (State/UT) will be provided to 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 UTs’ discretion and would be added as extensions to the CAS (State/UT) by the System

Integrators (SI) chosen by the UT without comprising on the simplicity and performance of the

system.

In order to achieve the above UTs goals of simultaneously ensuring consistency and

standardization across UT (where necessary and possible), and enabling UTs to meet their

unique requirements, CAS will be built as a highly configurable and customizable application.

CAS would therefore be a product-like application that could be centrally managed and at the

same time customized to meet the unique requirements of the UTs and deployed in all UTs.

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.

4.5 Technology Stack for CAS (UT)

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

Agency at the Center. The details of the Technology Stacks are provided as an Annexure to this

RFP. The SI is expected to bid with one of the technology stacks in response to this RFP. SI shall

procure all necessary underlying solution components required to deploy CAS (State/UT)

solution for the UT. Details of Technology stack is provided in Annexure-10

4.6 Role of Software Developing Agency (SDA) in Supporting CAS

The SDA will provide Services for CAS (UT) for a period of three (3) years followed by two

optional one-year periods from the date of successful completion of the CAS (UT) 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 (UT) and CAS (Center)

Technical Program Management of Implementation of CAS (UT) for all 35 State/UTs

throughout the duration of the engagement with NCRB/MHA.

Each of these activities is detailed out below:

Application Management Services for CAS (UT) and CAS (Center)

The SDA shall provide Application Management services to the CAS (UT) 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 (UT) to be managed centrally, with

State/UT-specific configuration incorporated.

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

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 (UT)

After successful certification, the SDA will hand over the certified CAS (UT) to State/UTs

through NCRB. While NCRB will facilitate the transfer, the successful transfer of CAS to

State/UTs 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 State/UTs. Through the

Technical Program Management, the SDA shall extend all the necessary support to the State/UT

SI and ensure that the SI successfully configures, customizes and deploys CAS (UT) in State/UTs.

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 State/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 (UT) 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 (UT) application in the UT, integrate CAS (UT) with

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

(Centre) to seamless transfer the required data to NCRB. The implementation toolkit

shall also include the following:

o All completed and updated training and support material needed for

customizing and deploying CAS

o All completed and updated project documents including FRS, SRS, HLD, LLD and

Test Plans

o Relevant software assets/artifact (including configuration utilities / tools,

deployment scripts to SIs to deploy CAS (UT) in UT)

o Relevant standards and design guidelines to the SI for customization, further

enhancements, and integration of the application with external systems and

third party components that will be implemented by the SI at the UT.

Conduct of direct knowledge transfer through monthly contact sessions at NCRB

covering all UT SIs during the contract period. During the contact sessions, the SDA shall

conduct structured training sessions on the CAS Implementation Toolkit prepared by

the SDA

Dedicated Points of Contact: Members of the SDA’s team shall act as points of contacts for

the UT level SIs. The number of UTs 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 UTs’ needs).

Helpdesk Support: SDA shall provide Helpdesk support to the UT SIs during

customization, deployment and stabilization phases with 8 contact hours (during

normal business hours of 10 AM to 6 PM), 6 days (Monday through Saturday, both

included). The SDA shall deploy a team of at least 5 qualified and certified

resources in NCRB to address the questions from the SIs.

Deployment Scripts: The SDA shall develop the necessary deployment scripts to deploy

CAS (UT) in UT and provide the same to State/UT SI.

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/UT databases. This will be

provided to UTs and will enable the 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/UT). The SDA shall build CAS (State/UT) with interfaces in English and

Hindi; and also build CAS (State/UT) in such a way that it can be configured for

interfaces in other local languages at the UT level by the 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.

Supporting the SI to ensure that the CAS (UT) that is configured and customized by the

SI in the UT successfully passes the User Acceptance Testing (UAT) milestone.

o Configuration of CAS (UT)

o Customization of CAS (UT)

o Data Migration of CAS (UT) related data from the legacy systems and / or

manual records to CAS (UT)

o Infrastructure Sizing related to CAS (UT)

o Commissioning and Deployment of CAS (UT)

o Infrastructure Environment Performance Turning related to CAS (UT)

o Maintenance of CAS (UT)

o Integration of CAS (UT) with external agency solutions

o Integration of CAS (UT) with additional solutions being integrated by the SI at

the UT.

Seamless data exchange from CAS (UT) to CAS (Centre)

Troubleshooting, resolution and escalation with UT SI; and ownership of end-to-end

data exchange between the CAS (UT) and CAS (Centre) needs to ensure seamless and

real-time data exchange.



5. SCOPE OF THE PROJECT

5.1 Geographical Scope

CCTNS will cover all Police locations in the UT of Puducherry including Police Head Quarters, SP

offices, and District headquarters, Sub-Divisions Offices, Police Stations, Other Police Stations,

Special Branches, Jail, Finger Print Bureau, Police Control Rooms, Crime Records Bureau, and

Training Centres. These are the locations across which the application and the bundle of

services shall be rolled out.

The list of all Police locations and details of the same is attached as an annexure to this

document. Location Maps & Locations details are available at Annexure-1 & 2

Following table lists an outline of Geographical scope to be covered under CCTNS project.

Above are the locations across which the application and the bundle of services shall be

rolled out.

5.2 Functional Scope

The functional scope of the project addresses the key functional areas of the Puducherry Police.

The SI is required to study the key process requirements, the functional requirements and

develop the required solution w.r.t the functional requirements. SI would configure and

customize CAS-Centre, CAS-State/UT specific to the UT of Puducherry and provide required

interfaces that need to be developed on existing legacy systems to be interfaced CAS and

develop any additional CAS-State/UT Extension modules. Additionally SI should provide

solution for integration requirements of the CAS with other Mission Mode Projects (MMP)

applications of Government of India (GoI) and inclusive of the other existing applications of

S No Office Qty (no.)

1 Police Station (Non CIPA) 7

2 Police Station (CIPA) 41

3 Sub Divisions 6

4 SP offices 7

5 Circles 15

6 District (SSP-L&O, SSP-KKR) 2

7 SSP (C&I) 1

8 PHQ 1

9 Finger Print Bureau 1

10 Crime Records Bureau 1

11 Proposed Training Centre 1

12 Police Control Rooms 4

Total 87



Puducherry Police and Personnel Information System etc to be developed by SI and applications

external interfaces such as CSC, Jail, Court, e-kosh, UT portal etc if any. The following table lists

down the Applications/services that would be part of CCTNS Puducherry.

S. No. Module Name Application /Service Type of

Services/

Application

Additional

functionalities for

CAS State/UT

(Yes/No/NA)

1. Registration

Module

Complaint and FIR

Management Service

CAS-State/UT Yes

2.

Investigation

Module

Investigation Management

Service

CAS-State/UT Yes

3. Prosecution

Module

Custody, Trial & Prosecution,

Court and Jail Interface &

Prosecution Management

Services

CAS-State/UT Yes

4. Search Module Crime & Criminal Records and

Query Management Service

CAS-State/UT Yes

5. Configuration

Module

UT CAS Administration and

Configuration Management

Service

CAS-State/UT Yes

6. Citizen

Interface

Portal

Citizen Portal Service CAS-State/UT Yes

7. Crime

Prevention

PCR Call Interface and

Management Service

CAS-State/UT Yes

Petition Management Service CAS-State/UT Yes

8. Collaboration

Module

Police Email, Messaging

services, IP tracking and SMS

tracking, Call Analysis

tracking

CAS-State/UT Yes

Notification of Alerts,

Important Events, Reminders

and Activity Calendar or

Tasks Service

CAS–State/UT Yes

9. Analysis,

Business

Intelligence &

MIS

(Reporting)

Periodic, Crime and Law &

Order Reports and Review

Dashboard Service

CAS–State/UT Yes




Services/

Application

Additional

functionalities for

CAS State/UT

(Yes/No/NA)

Module

10. Data Transfer

Module

UT SCRB-NCRB Data Transfer

and Management Service

CAS–State/UT Yes

11. User

Assistance

Module

User help and Assistance

Service

CAS–State/UT Yes

User feedback tracking and

resolution Service

CAS–State/UT Yes

12. Security

Module

User Access and

Authorization Management

Service

CAS–State/UT Yes

Activity Log Tracking and

Audit Services

CAS–State/UT Yes

State Specific Modules

13. Visitor

Information

System

I. Hotel Should provide the functionality to the Hotel owners of registering their Hotel details - Name of the Hotel -Owner/ Manager valid identification details - Staff identification details - Staff Verification details - City - District - Nearest Police Station -PAN Number -Tax Identification Number or any other Registration Number

1. Foreigners:

i. Allow the Foreigners

to submit Arrival Report

ii. Apply for Registration Certificate, Registration permit with respective REO

iii. Allow the hotel staff to upload the

CAS-State/UT

Extension

Yes




Services/

Application

Additional

functionalities for

CAS State/UT

(Yes/No/NA)

personal particulars of the foreigners

iv. Alerts on over stay

2. Indian Citizens:

i. Allow the hotel staffs

to submit the arrival /

check –in report in the

prescribed format

with mandatory fields

II. Cyber Cafe

Should provide the functionality to the Cyber café owners of registering their cyber café details - Name of the Centre - Name of the Owner -Owner valid identification details - City - District - Nearest Police Station -PAN Number -Tax Identification Number or any other Registration Number - Mobile / Phone Number Should allow periodic registering the information of the users at cyber café: - Customers Name and Identification Proof - Address - Mobile / Phone Number - Nationality (for non-Indian nationals Passport Number is mandatory) - Date and Time of Internet usage of each user System should be able to




Services/

Application

Additional

functionalities for

CAS State/UT

(Yes/No/NA)

auto-populate the information of café users based on previous entries, if any

14. Human

Resource

Management

System

1. Employee Information

2. Service Book

3. Payroll Generation

4. Transfer

5. Promotions

6. Vacancies

7. Annual Confidential Report

(ACR) generation

8. Leave management

9. Training details

10. Departmental Enquiry

11. Post Retirement Benefits

CAS-State/UT

Extension

Yes

15. Logistics

Management

System

This module should maintain

movement of materials

owned by the Police

department of the UT.

(Government properties

include Arms and

Ammunitions, IT Store,

Communication equipments,

Vehicles etc.)

CAS-State/UT

Extension

Yes

16. General

Verification

This Module include Passport

verification, Job verification ,

Tenant verification, Servant

verification, Government

Servant verification, Vehicle

parking verification, Private

Security verification, Business

verification

CAS-State/UT

Extension

Yes

17. Vehicle

Tracking

System

This Module should access the

database containing Vehicle

particulars and owner details

from the Regional transport

offices and bridging the

CAS-State/UT

Extension

Yes




Services/

Application

Additional

functionalities for

CAS State/UT

(Yes/No/NA)

Puducherry RTO database

thro’ online

Additional CAS (UT)

S. No CCTNS Modules

Additional Requirements for Customization of Main Functional blocks

1 Registration Module

It is proposed to Customize the registration module for UT of Puducherry and therefore the following functionalities shall be extended for the benefit of the user:

i. Registration of Missing Persons ii. Registration of Un-Natural / Suspect / Custody death

iii. Registration of Unclaimed / Abandoned / Suspected stolen Property

iv. Registration of Security Proceedings against the defaulters / habitual offenders

v. Registration of Preventive arrests Further this module would enable assignment of a unique number for better monitoring / report generation.

2 Investigation Module

The Investigation Module shall be integrated with the following tools for aiding the Investigation Officer:

i. Audio/ Visual Tools for taking witness / accused statements ii. Tools for guiding the Investigation Officer in heinous crimes

like Murder, Rape, Dacoity, Robbery etc. and the system would also generate checklists for the above heinous crimes

iii. Help Menu for Investigation toolkits 3 Records

Management This module would help the user to manage the information

relating to functionalities added in the Registration Module. Manage Un-Identified Dead bodies and Missing Persons

record Manage Stolen / Abandoned / Unclaimed Property Recent Release from jails Convicted / acquitted record Criminal case appeal record In addition, the system should manage Pending Investigation

cases, warrants and summons 4 Search and

Basic Reporting

This module would help the user to search the information relating to functionalities added in the Registration module and should generate reports accordingly. Added, the system should generate report for Pending Investigation cases, warrants and summons.



Overview of additional services in CAS (UT)

S. No CCTNS Modules Additional Requirements for Customization of Services in CAS (State/UT)

1 Citizen Portal System

Citizens requests / services include services for: i. Demonstration

ii. Public Meeting / Specified Indoor Meeting iii. Loud speaker permission iv. Non Conviction Certificate (NCC)

It shall also provide services for:

i. Un-Identified Dead bodies ii. Missing Persons

iii. Proclaimed Offenders iv. Stolen Vehicles

Visitors Information System:

3. Foreigners: v. Allow the Foreigners to submit the Form C /

Arrival Report vi. Apply for Registration Certificate, Registration

permit vii. Allow the hotel staff to upload the personal

particulars of the foreigners 4. Indian Citizens:

i. Allow the hotel staff to submit the arrival / check –in report in the prescribed format with mandatory fields

2 Complaint and FIR Management Service

This Module should enable the Police Personnel to register and process the complaints on Missing Persons, Un-Natural death etc.

3 Crime and criminal Records and Query Management Service

This module would help the user to search the information relating to functionalities added in the Registration Module.

Search Un-Identified Dead bodies and Missing Persons record

Search Stolen / Abandoned / Unclaimed Property Recent Release from jails Convicted / acquitted record Criminal case appeal record In addition, the system should search Pending

Investigation cases, warrants and summons 4 Notification of

Alerts, Imp. Events, Reminders & Activity Calendar or Tasks Service.

This module would assist the police personnel’s to get notification of alerts; important events, reminders and activity calendar to help them get latest information about registration of heinous crimes, un-identified dead bodies, VVIP Visit, arrest, vehicles recovered, etc.

The suggested technical architecture and standards are provided as an Annexure to this RFP. The functional requirements for the solution are provided as an Annexure-9 to this RFP.



Architectural Requirements 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 Architecture has been identified at that very level. However, a detailed TO BE state for the ICT Hardware and architecture has been developed for Puducherry Police with focus on how the solution will enable the Puducherry Police to provide a consolidated suite of applications that can seamlessly interface with external sources such as other States, Centre, and other external agencies. CCTNS is deployed on a centralized architecture wherein application would be deployed at the State Data Centre at Puducherry and various offices of Police Department will connect to the system through WAN. 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 Centre standards etc. A brief understanding of the Proposed Deployment Architecture, Solution Architecture, Technical Architecture and Application Architecture is provided below: Deployment Architecture The proposed overall solution framework for the Department is presented in this section depicting the overall ‘Big Picture’ of the key target areas of IT initiatives and their inter-relationships. This blue print would be used as a communication tool that provides a snapshot of the overall goal/ direction to be taken up for implementation of CCTNS project to which all the stakeholders could relate to, without getting into the complex details of the internal workings of each of these initiatives. All the modules depicted in the overall solution framework and explained in detail as part of the Functional Requirement Specification – provides the overall goal of the Department, including the adoption of core applications modeled under the CCTNS scheme. It is required that all the additional modules to be developed by SI should be complying with DIT, GoI standards and guidelines for open standards. This would enable ease of interoperability and also be significantly more economical for the Puducherry Police. It is recommended that SI will opt for Service Oriented Architecture (SOA) for implementing CCTNS application modules6. The SI shall choose the technology such that:

It can help businesses (Police functions) respond more quickly and cost-effectively to changing market conditions.

It shall promote reuse at the macro (service) level rather than micro (classes) level. It can also simplify interconnection to - and usage of - existing IT (legacy) assets.

It shall also support the principles of good design: Granularity, interoperability modularity.

The issues related to performance, manageability, and scalability shall be well addressed and system shall provide a more manageable system and less contention for resources.

Note:

This is an indicative Solution & Technology Architecture. SI will carry out detailed study to develop the exact Solution & Technology Architecture for Puducherry CCTNS solution considering NCRB guidelines.



CCTNS application modules or CCTNS suite would mean customized CAS (State), additionally developed modules, integrated modules, interfaces, web portal, and other application modules under scope of this project.

Solution architecture In this section, the major components of the Solution Architecture that are the building blocks of the entire information technology system, have been defined and elaborated in the context of how these information blocks will add up to deliver the envisioned services will be discussed. The overall Solution Blue-print of the Puducherry CCTNS is depicted in the figure below:

User Layer

PSWAN

Police stations District OfficesState

Headquaters

Other Police

Units

Security Layer

Data Layer

State Data Center

Information Databases

Master

Information

Forensic

Information

Inventory

Information

Financial

Information

Property

Information

HR

Information

Crime

Information

Case

Information

Missing

Person

Information

Complainant

Information

Foreigners

Information

Vehicle

Information

Application Portfolio

CCTNS Application Modules

Registration

Investigation

Prosecution

Complaint/

FIR Mgmt

Petition Mgmt

PCR Call

Interface

Abandon

Property

Records and

Query

Email &

Messaging

Data Transfer

& Mgmt

User

Feedback

Notifications &

Alerts

Crime and Law

& Order

Reporting

User Help &

Assistance

CAS Admin &

ConfigurationCitizen

Interface &

Portal

Visitor

Information

System

Human

Resource

Management

System

Logistics

Management

System

General

Verification

Vehicle Tracking

System

Workflow Engine

Payment Gateway

Service Delivery

ChannelsPortal and Gateway Interface

Portal (Internet/

Intranet)

Citizen Service

Center

Mobile / SMS Dial 100Verification

Application

Call Center /

Helpdesk

Reports and

Records - RTI

Standards and PoliciesIT Policies and

ComponentsQuality Standards

IT Security

Policies

IT Procurement

Policies

Modules proposed in CAS (State)

Additional Modules proposed by State to be developed



The ‘User’ Layer: This layer forms the internal departmental users accessing the applications over Internet or through the Puducherry State Wide Area 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 State 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 State 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 State Data Centre would securely host the aforementioned information databases on servers specifically for Puducherry Police Department. It is recommended that the State Data Center (SDC) 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 SDC. 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 SDC) in the future, if and when required

Cost effective option as the IT infrastructure investments would be required only for enhancing the capacity of SDC (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 Puducherry SWAN (i.e. the State Wide Area Network established by the State Government) ensuring optimum uptime at all the desired locations. The ‘Application’ Layer: The 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 or through SWAN. 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



Technical Architecture A centralized architecture (servers and processing at single and central location) has been proposed for the Puducherry 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 Puducherry 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.

(c) Support for PKI based Authentication and Authorization – The solution shall support PKI based Authentication and Authorization, in accordance with IT Act 2000 (amended till date), 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.

(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 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 are given in the Service Levels attached as Annexure 15 to this Volume of 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. State Specific Requirements Selected System Integrator would be completely responsible for successful implementation of end to end CCTNS solution in Puducherry UT as per the requirement of Puducherry 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 Puducherry UT, for the success of this project. An indicative list of specific requirements is detailed above; however, final specific requirements would emerge from the Detailed System Study to be conducted by System Integrator.



Application Specific Requirements 1. Key Customization Requirements: The functional requirement specifications of each of the modules mentioned above in the functional scope have been defined in the attached Annexure 9. The functionalities which are coming through the original application has not been tampered and the customization requirements is primarily to be focused on to the configuration that is required in terms of the department’s organizational/hierarchical structure, roles and rights of police personnel at various levels, reports and registers that are maintained at the different levels of the organization covering police stations and higher offices, etc. In addition to the configuration requirements, some enhancements are done into the existing modules as required by the UT. The details of the enhancements are provided in the functional requirement specifications as given in the annexure. Apart from these enhancements, the modules to be added such as Foreigner Registration Module, HRMS Module, Inventory Module, Issue of Certificate Module, Cyber Crime and Mobile Crime Module and Integration Module etc are also provided in the FRS attached as annexure. 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 as 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 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 less mistakes during data entry in the names, addresses. Selected SI is also required to configure the system in such a manner that system should send alerts in case data entry is not being performed appropriately in the modules. For example, data entry in the DDR is a continuous activity, hence in case no data is entered in DDR for 12 hours or more, system should send alerts to concerned DSP and in case no data entry for more than 24 hours, the matter should be escalated and alerts should be sent to concerned SP. Similarly for arrest forms, in case no data is entered in next 48 hours after the registration of FIR, the system should send alerts to concerned SHO. Record Management: Institutionalizing various ICT tools and technology have a common agenda of eliminating drudgery from the existing system. 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 a Case Basket for 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: It would be a false assumption to anticipate seamless connectivity at all Police Stations. Therefore, local databases at Police Station to record and register complaints, has been proposed during no connectivity. As the offline mode switches back to the online mode, data recorded in local database at Police Station would automatically synchronize with central data repositories and information stored locally would be sent to the central repository. Weeding out of Records: SI would be required to configure the CCTNS system, to enforce Puducherry Police specific requirements for weeding out of records. Note: These are only key customization recommendations, however detailed customization requirements to be done as per the FRS regarding each module. 2. Integration and Interfacing Requirements CCTNS is deployed on a centralized architecture wherein various offices of Police Department connect to the system through SWAN and BSNL from State Data Centre. The interfaces to be developed within CAS (State) should provide proper information and data sharing with external agencies, but not limiting to, Transport Authority, Jails, Courts, Hospitals, Mobile Service Providers, etc. External Interfacing shall also be State Common Service Centers (CSC), e-forms applications (project in progress) (of State portals and Service Delivery Gateway), State Universities, Cyber Cafes of the State, and Hotels of the State and 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, LIMS project, Age progression, Mobile Number Portability, etc. CCTNS and other Mission Mode Projects:

The National e-Governance Plan (NeGP) of the Govt. of India aims to cooperate, collaborate and

Integrate information across different departments in the Centre, States and Local Government.

Government systems are characterized by islands of legacy systems using heterogeneous

platforms and technologies and spread across diverse geographical locations, in varying state of



Automation, make this task very challenging.

The NSDG (National e-Governance Service Delivery Gateway) is an integrated MMP under the

National e-Governance Plan (NeGP), can simplify the above task by acting as a standards-based

messaging switch and providing seamless interoperability and exchange of data across the

departments. NSDG acting as a nerve center, would handle large number of transactions, and

would help in tracking and time stamping all transactions of the Government. The Gateway

would provide major benefits to the departments such as Multiple Delivery Channels, Better

Audit Management & Time Stamping, Web enabling of Legacy Applications, Interoperability,

Departmental Workflow, Seamless availability of information, Centralized Management, Shared

services.

Crime and Criminal Tracking Network and Systems (CCTNS) is a Mission Mode Project (MMP)

conceptualized and sponsored by the Ministry of Home Affairs (MHA), Govt. of India (GoI)

towards enhancing outcomes in Crime Investigation and Criminals Tracking; and in enhancing

the efficiency and effectiveness of Police departments in all States. It is proposed to achieve this

through the adoption of the principles of e-Governance and creating a nationwide, networked

infrastructure for supporting an ICT (Information and Communication Technologies) enabled

state-of-the-art policing system. CCTNS aims at creating a comprehensive and integrated system

for enhancing the efficiency and effectiveness of policing at all levels and especially at the Police

Station level through adoption of principles of e-Governance, and creation of a nationwide

networked infrastructure for evolution of IT-enabled state-of-the-art tracking system around

―investigation of crime and detection of criminals in the real time, which is a critical

requirement in the context of the present day internal security scenario. For increasing the

efficacy of CCTNS it needs to be integrated with few other e-governance mission mode projects

i.e. SWAN & SDC. SWAN may provide the basic network connectivity for CCTNS whereas State

Data Center would be the heart of CCTNS where all information would get stored.

The following are the list of Mission Mode Projects (MMP) in UT of Puducherry:

S. No Mission Mode Projects (MMP)

1 Agriculture

2 Commercial Taxes

3 e-District

4 Employment Exchange

5 Land Records

6 Municipalities

7 Gram Panchayats

8 Road Transport

9 Treasuries



Brief Description of Police Station Process

The police station is a hub of several activities. Maintenance of law and order, crime

investigation, protection of state assets, VIP protection, traffic control, service of summons,

production of witnesses in courts, intelligence gathering, bandobust duties, crime prevention are

some of multifarious functions that the police station and its officers have to discharge. Police

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

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

information collection agent for the other functions/wings within the department. In order to

achieve the end-objective of bringing in efficiency and effectiveness in the police station, it is

crucial to understand the different responsibilities of the police station and identify the key

services that need to be addressed in this study.

The first step in identifying the key functions is to segment them under core and supporting,

where the core includes services like crime prevention, petition handling and the supporting

include the employee related personnel and pay functions, store management etc. The efficiency

gains are achieved through addressing the supporting services where the police station is

provided with tools to perform the tasks faster with fewer resources, and the effectiveness gains

are achieved by addressing the core services where the police station can improve the quality of

the services.



Police Station FunctionsE

mp

loye

e

Re

late

d

Em

plo

ye

e

Re

late

dB

ack O

ffic

eB

ack O

ffic

eL

aw

& O

rde

rL

aw

& O

rde

rC

all R

esp

on

se

Ca

ll R

esp

on

se

Crim

e

Pre

ve

ntio

n

Crim

e

Pre

ve

ntio

nD

ete

ctio

n &

Inve

stig

atio

n

De

tectio

n &

Inve

stig

atio

nC

ou

rt &

Pro

se

cu

tio

n

Co

urt

&

Pro

se

cu

tio

nP

ub

lic F

acin

gP

ub

lic F

acin

g

Handling Petitions General Services Traffic Regulations

Emergency

Response

No Emergency

Response

Crime analysis Beats & PatrolsCommunity

Policing

Village Area

InformationCampaigns Cash Escort

Repeat Offender

Checking

Evidence

Management

Prisoners

Management

Custody

ManagementInvestigation

Receiving

informants

information

Execution of

Summons

Victim/Witness

Relationship

Management

Disposal of

Recovered GoodsTrail Management

Enforcement of

various legislationsBandobast duties

Store

Management

Records

Management

Management

Reports

AccountsDuty & AllocationHR AdministrationGrievance

Redressal



5.3 Scope of Services during Implementation Phase

The scope of the “bundled services” to be offered by the SI includes the following:

a) Project planning and management.

b) System study, design, application development and integration of the CCTNS Application

Software based on Core Application Software (CAS) provided by NCRB

c) Configuration, Customization and Extension (New Modules) of CAS (UT) and Integration

with CAS (Center) and External Agencies. CAS (UT) 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 (UT) solution for the UT.

d) Development & Integration of state specific modules mentioned in the above table to the

CAS State.

e) Site preparation at the Client site locations (Police stations, Circle offices, SP offices, CRB,

SDPOs, District HQ, Training Centers and Police HQ) and Data Center.

f) IT Infrastructure at the Client site locations (Police stations, Circle offices, SP offices,

CRB, SDPOs, District HQ, Jail, Finger Print Bureau, Police Control Rooms, Training

Centers and Police HQ).

g) Network connectivity at all locations

h) IT infrastructure at the Data Center and Disaster Recovery Center including the

necessary hardware, software and other networking components.

i) Data Digitization of Historical data and Migration of CIPA and CCIS Police Stations /

Higher Offices data to CCTNS.

j) Capacity Building of the identified police personnel

k) Handholding Support.

l) Support to 3rd party acceptance testing, audit and certification of the Application

developed by SI.

m) Post Go-Live operation and maintenance support/services (Please refer Annexure – 8)

In implementing the above, the SI shall strictly adhere to the standards set by the MHA, NCRB,

and UT of Puducherry Administration.

SI is also wholly responsible for third party vendor applications. In case of any

problems/issues related to the applications while implementing, Puducherry Police will

seek clarifications with SI only not to third party vendors.

The project will be managed out of the office of UT Nodal Officer in UT HQ. At all points in the

execution of the project, key senior resources including the project manager must be based at

UT Nodal Officer’s office in UT HQ.

The item (m) above refers only to the mandatory support to be provided by SI during the

execution of the activity.

The item (a) above refers to Project planning and management functions from the side of SI

which should align with the overall Project planning and management functions of the UT

executed through UT Nodal officer with the support of SPMU.



5.3.1 Project Planning and Management

This project is a geographically spread initiative involving multiple stakeholders. Its

implementation is complex and though its ultimate success depends on all the stakeholders; the

role of SI is key and hence SI is required to design and implement a comprehensive and effective

project management methodology together with efficient & reliable tools.

To have an effective project management system in place, it is necessary for the SI to use a

Project Management Information System (PMIS). The SI shall address at the minimum the

following using PMIS:

a) Create an organized set of activities for the project

b) Coordinate and collaborate with various stakeholders including the Police departments,

SPMU, CPMU and SDA

c) Establish and measure resource assignments and responsibilities

d) Construct a project plan schedule including milestones

e) Measure project deadlines, budget figures, and performance objectives

f) Communicate the project plan to stakeholders with meaningful reports

g) Provide facility for detecting problems and inconsistencies in the plan

h) During the project implementation the SI shall report to the UT Nodal Officer, on

following items:

i) Results accomplished during the period

ii) Cumulative deviations to date from schedule of progress on milestones as

specified in this RFP read with the agreed and finalized Project Plan

iii) Corrective actions to be taken to return to planned schedule of progress

iv) Proposed revision to planned schedule provided such revision is

necessitated by reasons beyond the control of the SI

v) Other issues and outstanding problems, and actions proposed to be taken;

vi) Interventions which the SI expects to be made by the Project Director and

/or actions to be taken by the Project Director before the next reporting

period

i) Progress reports on a fortnightly basis

j) Interventions which the SI expects to be made by the UT Nodal Officer and/or actions to

be taken by the UT Nodal Officer before the next reporting period;

k) Project quality assurance reports

l) Change Control Mechanism

m) 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 UT.

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

The Project plan prepared by the SI would be reviewed by the Governance Structure (Please

refer to Annexure- 7 on details on Governance Structure to be setup in the State) in the UT and



approved by the Apex / Empowered Committee on the advice of the State Mission Team & State

Project Management Unit.

The SI would update and maintain the Project Plan throughout the duration of the engagement.

All changes are to be reviewed and approved by the CAS Core Group.

Requirements Traceability Matrix

The SI would ensure that developed solution is fully compliant with the requirements and

specifications provided in the RFP such as functional, non-functional and technical

requirements. For ensuring this, the SI shall prepare a Requirements Traceability Matrix on the

basis of Functional Requirements Specifications (FRS), Non Functional Requirements

Specification, and Technical Requirements provided by UT (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 the UT 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 UT. (Please refer to Annexure-

7 for details on Governing Structure to be set up in the State). State Mission Team would also

approve any changes required to these documents during the course of the project. UT will

finally sign-off on the documents on the recommendation of State Mission Team/SPMU/State

Empowered Committee.

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.

LLD documents (including but not limited to):

Application flows and logic including pseudo code

GUI design (screen design, navigation, etc.)



All Test Plans

Requirements Traceability Matrix

Change Management and Capacity Building Plans

SLA and Performance Monitoring Plan

Training and Knowledge Transfer Plans

Issue Logs

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 UT 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 UT Nodal Officer on request.

All project documentation shall conform to the highest standards of software engineering

documentation.

Procure, Commission and maintain Project Management, Configuration Management and

Issue Tracker Tools at State HQ / SCRB.

Project Management Tool: The SI shall keep the project plan and all related 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

UT’s premises right at the beginning of the project. The tool shall provide the dashboard view of

the progress on project milestones by the Nodal Officer and other Supervisory Officers of

CCTNS.

Configuration Management Tool: The SI shall keep all project documents up-to date during

the course of the project. In order to help with the version/configuration management for all

documents (including source code and all other project 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 UT

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 UT’s premises to enable UT’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 UT and will be used by UT 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.

5.3.2 Configuration, Customization and Extension (New Modules) Of CAS (UT) and

Integration with CAS (Center) and External Agencies

System Study, Design, Application Development and Integration

In terms of functionality, CAS would cover those police functions that are central to the goals of

the CCTNS project and are common across UTs. This includes core functions in the areas of

Complaints/ Case Management, Police Station Efficiency and Analysis & Reporting. It is

estimated that of the possible police functions that could potentially be part of the CCTNS

application at the UT level, the functionality covered by CAS is a relatively small part. Therefore,

CAS is being developed as a product-like application that could be centrally managed and at the

same time customized to meet the unique requirements of the UTs and deployed in all

States/UTs. SI would be responsible for adding the functionality over and above the CAS (State)

as provided in the Annexure-9.

CAS (State/UT) contains functionality that is common across all States/UTs. CAS (State/UT)

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

services that will be provided by the Software Development Agency (SDA) for the CAS (State)

are articulated in Annexure-7.

For the additional functionality that the UT wants to be added to CAS (State/UT), the SI shall

carry out a detailed systems study to refine the Functional Requirements Specifications

provided as Annexure-9 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 SRS preparation shall take into account the BPR

recommendations suggested by the NCRB.

The SI shall carry out a detailed systems study to refine the Functional Requirements

Specifications provided as Annexure to this RFP and formulate the System Requirements

Specifications (SRS) incorporating the functional specifications and standards provided by the

NCRB and the UT-specific requirements. The SI shall also study CAS-State/UT and CAS-Center

being developed at NCRB and / or already running application in the UT during the system

study phase. The study should also include different integration points of CAS State/UT with

external agencies as per UT requirement. The SRS preparation shall take into account the BPR

recommendations suggested by the NCRB / State/UT. The SI should also prepare a detailed

document on the implementation of CAS (State/UT) with respect to configuration,

customization and extension as per the requirement of the UT. The SI would also prepare a

change/reference document based on changes or deviations from the base version of the CAS

(State/UT) with appropriate references to all the artifacts /documents provided by NCRB / UT.



The SI will also be responsible for:

1. Conducting System Study at selected at the following locations:

a. CIPA Police Stations

b. Non-CIPA Police Stations

c. Police Headquarter

d. District Offices (SSP)

e. SSP (C&I)

f. SP Office

g. SDOPs

h. Crime Records Bureau (CRB)

i. Circle Offices

j. Finger Print Bureau

k. Police Control Rooms

2. Preparation of System Requirements Specifications (SRS) for additional functionalities

and different integration points with CAS (Center) and External Agencies.

3. Preparation of CAS (State/UT) implementation document with respect to Configuration,

Customization and extensions as per the requirement of the UT of Puducherry.

4. Preparation of the Solution Design.

5. Solution Development and/or Customization and/or Configuration and/or Extension as

required.

6. Development of reports.

7. Formulation of test plans and test cases for additional functionalities and different

integrations with external agencies including CAS (Center)

8. Preparation of Change/Reference document which will include all the changes or

deviations from the base version of the CAS (State/UT)

9. Testing of the configured solution (CAS) and additional functionalities.

Enhancements of functions / additions of new modules / services to CAS (State/UT) as per UT

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.

Creation of Test Plans

Once the SRS is approved and design is started, the SI would prepare all necessary Test Plans

(including test cases), i.e., plans for Unit Testing, Integration and System Testing and User

Acceptance Testing. Test cases for UAT would be developed in collaboration with domain

experts identified at UT Police Headquarters. The Test Plans also include planning for the

testing any integration with 3rd party COTS solutions, CAS (Center), any external agencies. The

Test Plans should also specify any assistance required from Police Department and should be

followed upon by the SI. The SI should have the Test Plans reviewed and approved by the State

Mission Team /SPMU. The UT will sign off on the test plans on the advice of State Mission Team

/SPMU.

High Level Design (HLD)

Once the SRS is approved, the SI would complete the HLD and all HLD documents of the

additional functionalities, integration with CAS (Center) and external agencies upon the

approved SRS. The SI would prepare the HLD and have it reviewed and approved by the State



Mission Team /SPMU. The UT 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. UT headquarters/Nodal officer will sign off on the LLD documents upon

the advice of State Mission Team /SPMU.

Application Development and Unit Testing

The SI would develop the application in accordance with the approved requirements

specifications and design specifications and according to the approved Project Plan; and carry

out the Unit Testing of the application in accordance with the approved test plans. The SI shall

consider the local language support and prepare necessary configuration files for both CAS and

additional functionalities/modules developed as part of CAS.

The SI would also implement the changes proposed in the Change/Reference document to Core

Application Software and carry out a thorough regression testing including running some of the

previously executed scripts for the functionality from the traceability matrix provided by NCRB/

UT.

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 UT databases. This Utility will migrate the

data from legacy based systems of the new modules to the CAS databases.

The user acceptance testing and fine-tuning of the application would be at the UT Headquarters

premises. Also, the key senior resources would continue to be based onsite at the UT

Headquarter premises.

Configuration of CAS (State/UT)

The SI shall configure CAS (State/UT) to the requirements of the UT that include but not limited

to:

1. Developing Local Language Interfaces and Support

2. Configuring users

3. Configuring Police Stations / Higher Offices

4. Configuration of the UI as required by the UT

The collection and validation of the data required for the configuration of the CAS (State/UT)

shall be the responsibility of the SI.

Setup of Technical Environment at the UT 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

UT Headquarter premises; and for any other activities that may be carried out of UT



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/UT), additional functionalities and also integration with CAS

(Center) and external agencies. This would include exhaustive testing including functional

testing, performance testing (including load and stress), scalability testing and security testing.

Functional testing will be led by the SI’s experts.

A thorough regression testing should be conducted for those functionalities identified in

Change/Reference document to provide a general assurance that no additional errors have

cropped up in the process of addressing the customizations and/or Extensions. Customized CAS

(State/UT) Integrations with CAS (Center) and with any external agencies should be thoroughly

tested.

Making all necessary arrangements for testing including the preparation of test data, scripts if

necessary and setup of test environment (across multiple platforms) shall be the responsibility

of the SI.

The SI along with State Mission Team / SPMU should take the responsibility in coordinating

with NCRB and other external agencies for a smooth integration.

Test Reports

The SI shall create test reports from testing activities and submit to State Empowered

Committee / State Mission Team /SPMU for validation

Test Data Preparation

The SI shall prepare the required test data and get it vetted by SPMC/ State Mission

Team/SPMU or a Third Party Agency. The test data shall get generated from the data entry/

data migration exercise by SI and should 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. SI shall prepare all the reports required for Puducherry

CCTNS solution to undergo quality assessment and certifications such as STQC, etc.

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



The SI must offer an Enterprise Management Solution that provides end-to-end, comprehensive,

modular and integrated management of IT infrastructure components to maximize the

availability of CCTNS IT services and SLA performance. The management system needs to

aggregate events and performance information from the domain managers and tie them to

service definitions. The proposed set of tools should automatically document problems and

interruptions for various IT services offered and integrate with the service level management

system for reporting on service level agreements (SLAs).The proposed solution be unified and

must also generate a comprehensive view of a service with real-time visibility into service

status and identify the root cause of various infrastructure problems as well as prioritize

resources based on impact.

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

5.4 Site Preparation at Police Stations and Higher Offices

The SI is expected to prepare the client sites for setting up the necessary client site

infrastructure. Site preparation at Police Stations & Higher Offices will include but not limited

to:

i) Provision of Local area network (LAN cables, LAN ports)

ii) Provision of computer furniture for Police Stations

iii) Ensure adequate power points in adequate numbers with proper electric earthing.

iv) Electric Wiring and providing power points for Computers, Printers and earthing

from main line and Generator line with accessories

v) In addition to the above supply and fixing of furniture of good quality like Computer

tables Computer Chairs (Cushion with arm), and other items shall be carried out to

ensure successful site preparation and installation of CCTNS at every access location.

Site Preparation shall cover all the activities necessary to enable the Police Stations to setup the

client side infrastructure and operate on CCTNS. Site Preparation will not include the

construction of buildings and major civil work.

Following is the total number of sites across the UT of Puducherry, which need site

preparation.

S. No Office Offices/Locations

1 Police Stations Police Stations 48

2

Higher Offices Police Head Quarters 1

Circle Offices 15

District HQ 2

SDPO & SP offices 14

Crime Records Bureau 1

Total 81



1. Site Preparation at Client Site Location

Item Quantity required in

each location

Total Quantity required

1.1. Non CIPA Police Station: (7 nos.)

Computer table 4 28

Chair 4 28

Printer Table 1 7

Electrical Cabling 1 7

Earthing and Earth Pit 1 7

Wall Mountable Network Rack- 9U 1 7

Patch Panel 24 ports CAT 6 1 7

Information outlet CAT 6 6 42

CAT 6 Cable with cabling (In Meters) 120 840

Patch Cords 1 Mtr. CAT 6 6 42


Any Other

1.2. CIPA Location Police Stations: (41 nos.)


Patch Panel 24 ports CAT 6 1 41


Any Others

1.3. SCRB (1 no.)

Computer Table 4 4

Chair 4 4


Patch Panel 24 port CAT 6 1 1

Information Outlet CAT 6 6 6

CAT 6 Cable with Cabling (in meters) 120 120

Patch Cord 1 mtr. CAT 6 1 1


Any Others

1.4. SDPO Office: (6 nos.)

Computer Table 3 18

Chair 3 18

Earthing and Earth PIT 1 6



Patch Panel 24 Port CAT 6 1 6







Any Others

1.5. SP (District) Office: (7 nos.)

Computer Table 10 70

Chairs 10 70


Earthing and Earth Pit 1 7


Patch Panel 24 Ports CAT 6 1 7


CAT 6 Cable with Cabling (In Meters) 220 1540

Patch Cords 1 meter CAT 6 15 105

Patch Cords 2 meter CAT 6 15 105

Any Others

1.6. Police Head Quarter

Computer Table 15 15

Chair 15 15

Wall Mountable Network Rack – 9U 2 2

Patch Panel 24 Port CAT 6 2 2



Patch Cords 1 mtr. CAT 6 20 20

Patch Cords 2 mtr. CAT 6 20 20

Any Others

Note: Quantity may differ (less or higher) depending upon the implementation

locations. Payments will be made on actual.

5.5 Infrastructure at the Implementation Locations

The premises for offices will be provided by the Department at respective locations. The list of

Police Stations, Circle offices SDOP, District offices, and other locations where the infrastructure

is required is provided under the Geographical Scope Section. SI shall procure the CCTNS

infrastructure required at the locations in the UT.

At each such location the following shall be carried out.

1. Supply of the hardware, software, networking equipments, UPS, DG set to the location as

per the requirements

2. Ensure adequate numbers of Power points with proper electric wiring

3. Redundant Network Connectivity - Ensuring last mile connectivity and testing.

4. Installation, Testing and Commissioning of UPS, DG-Set

5. Physical Installation of Desktops, Printer, Scanner, /MFD, Switch- Connecting

peripherals, devices, Plugging in etc.

6. Operating System Installation and Configuration.

7. Installation of Antivirus and other support software if any.



8. Configuring the security at the desktops, switch, routers and broadband connection/

networks.

9. Network and browser Configuration.

10. Test accessibility and functionality of CCTNS application from the desktops.

11. Ensuring all the systems required are supplied, installed, configured, tested and

commissioned and declaring the site to be operational.

12. In addition to the above supply and fixing of furniture like computer tables, chairs and

other items shall be carried out to ensure successful site preparation and installation of

CCTNS at every location

13. The SI must propose a management system that manages the end-to-end performance

and availability of CCTNS service delivery. The system must provide management for

Datacenter and Network Infrastructure

CCTNS application will be accessed and used at various access locations across the UT of

Puducherry like Police Stations, Circle Office, Sub Division office, District Office and other higher

offices.

The detailed list of ICT infrastructure at the proposed locations is as given below:

PHQ – Puducherry

Police Stations

Districts offices

SDOP’s /SP’s Office

SSP (C&I)

Circle offices

Crime Records Bureau

Police Control Rooms

The list of ICT infrastructure requirements at the following 7 Non CIPA Police Stations are:

S No. Items No.

1 TFT Desktops with Pre-loaded latest version of Microsoft Windows 7 Professional or higher OS including Anti-virus and Office Suite as per the technology stack adopted – 4 for each Police Station

4

2 HDD 320GB or higher 1

3 Duplex Laser Printer 1

4 Multi-Function Laser (Print/Scan/Copy) 1

5 UPS for 120min backup 1

6 2KVA Generator Set 1

7 16-Port Switch 1

8 Fingerprint Reader 1

9 Digital Camera 1

10 Electronic Pen 1

11 OPE (Paper/toner) 3 yrs



The list of ICT infrastructure requirements at the following 41 CIPA Police Stations are:

S No. Items No.

1 TFT Desktops with Pre-loaded latest version of Microsoft Windows 7 Professional or higher OS including Anti-virus and Office Suite as per the technology stack adopted – 4 for each Police Station

4

2 HDD 320GB or higher 1

3 2KVA Generator Set 1

4 16-Port Switch 1

5 Fingerprint Reader 1

6 Digital Camera 1

7 Electronic Pen 1

Detailed Specifications for above is given in Annexure-14. The list of ICT infrastructure

requirements at Higher Offices:

S.

No

Locations No of

offices

PC (Each

office)

MFP

(Each

office)

Switch

(Each

office)

UPS

(Each

office)

OPE Paper/toner

1 PHQ 1 15 15 0 15 3ys

2 CRB 1 4 1 1 1 3ys

3 Circles 15 3 1 1 1 3ys

4 Districts (SSP

Off) 2 10 10 0 10 3ys

5 SDOP 6 3 1 1 1 3ys

6 SP Offices 7 3 1 1 1 3ys

7 SSP (C&I) 1 3 1 1 1 3ys

9 FPB 1 1 0 0 0 3ys

10 Police Control rooms

4 3 0 1 0 3ys

Detailed Specifications for above is given in Annexure-14

5.6 Network Connectivity for Police Locations

All Police Stations and Higher Offices connected with Broadband through BSNL ISP, while

PSWAN in its Stage- I extended connectivity to office of the Departmental head region wise and

connectivity to Municipality & Commercial Panchayats. Proposal for connectivity through

PSWAN up to PS level is suggested for feasibility through IT & NIC for consideration in Stage I

and Stage II to be initiated in the near future. Alternate connectivity by ISP other than BSNL is

under negotiation at NCRB, MHA.



Networking Connectivity required

All the Police stations & Higher offices have Broadband connectivity; however some locations

have no internet connectivity. In this regard few offices have been recommended Broadband

connectivity through BSNL. As per guidelines 10% locations has been considered for MPLS

connectivity.

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 each States/UTs SDC for

the locations connected on VPNoBB, WiMax and VSAT network.

e) Provisioning of MPLS connectivity between State/UT SDCs and DRC.

f) Provisioning of MPLS connectivity between NDC and State/UT SDCs

g) Maintaining the network including hardware supplied for minimum period of 3

years.

Role of System Integrator: The SI shall coordinate with BSNL and the UT Police Department

for implementation of the Network and Connectivity solution of CCTNS project. The following

are the key responsibilities of the SI with respect to Networking and Connectivity.

i. Site preparation at all locations for establishment and installation of networking and

connectivity solution.

ii. Coordination with the UT Police Department and nominated officials of BSNL for

Installation, Configuration, Testing and Commissioning of BSNL’s 2Mbps Point to

Point Leased Lines for connecting with SWAN, VPNoBB, WiMax, VSAT and MPLS

links.

iii. Coordination with BSNL for ensuring Operations and Maintenance of networking

hardware to ensure compliance to the SLAs as offered by BSNL.

iv. The SI will also be coordinating with BSNL and UT Police Department for SLA

Monitoring, Fault Reporting & Troubleshooting of the links for meeting the Service

levels and Master Service Agreement.

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

vi. SI shall also coordinate with State CCTNS Nodal Officer (UT 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.

Detailed Break-up of offices for network connectivity is provided in Annexure-3

5.7 Infrastructure at the Data Center & Disaster Recovery Centre

The SI shall provide system integration services to procure and commission the required

software and infrastructure at the State Data Centre and Disaster Recovery Centre, deploy the

complete CCTNS applications suite (configured and customized CAS (State), additional modules

developed, and integrate with CAS (Centre) and any External Agencies as provided in the

functional scope). Although SI will not be required to undertake any electrical and civil work in

the SDC and DRC premises, however, if required then within the Rack, electrical work will be the

responsibility of the System Integrator.

.

The SI shall be completely responsible for the sourcing, installation, commissioning, testing and

certification of the necessary software licenses and infrastructure required to deploy the

Solution at the State Data Centre and at the Disaster Recovery Centre (DRC).

SI shall ensure that support and maintenance, performance and up-time levels are compliant

with SLAs. SI shall coordinate with SDC in isolating the issues between solution stack and

common infrastructure provided by SDC; and in ensuring that they are reported to concerned

parties so that they are resolved in timely manner.

To ensure redundancy requirements are met, SI shall ensure that infrastructure procured by the

SI has redundancy built in. SI shall also provide descriptive ‘Deployment Model, Diagrams and

Details’ so that redundancy requirements for the common Data Center infrastructure can be

addressed.

CAS (State/UT) 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/UT) solution for the UT.

UT will provide the premises for Primary Data Centre (DC) for hosting the solution as well as

the Disaster Recovery Centre (DRC). 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 UT.

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 Data Centre and Disaster Recovery Site infrastructure

such as Racks, Power and Cooling, Bandwidth among other components. The common

DC and DRC infrastructure shall be provided by UT.

SI shall ensure that effective Remote Management features exist in solution so that

issues can be addressed by the SI in a timely and effective manner; and frequent visits to

Data Centre / DRC can be avoided.

After commissioning and testing of the entire system at State Data Center / DRC, the SI

shall support the UT in getting the system certified by a 3rd party agency identified by

the UT.

UT will provide the premises for Primary Data Centre (DC) and Disaster Recovery

Centre (DRC) for hosting the solution. The solution shall be hosted in a collocation

model in the State Data Centers.

The following infrastructure at the Data Centre will be available to the SI through the Data

Centre Operator / Data Centre Service Provider (DCO):

1. RACK

2. Power and Cooling

3. UPS, DG set power backup

4. Bandwidth and Connectivity

5. LAN

6. VPN

7. Firewall

8. Intrusion Protection System

9. Fire prevention

10. Physical security surveillance

11. Network Operation Centre

12. Common Data Centre facility Maintenance and Support

The SI is responsible for the below at the Data Centre / Disaster Recovery Centre:

1. Servers (Application Server, Intra Web Server, Directory Server + Access

Manager, Database Server, Mail Messaging Server etc.)

2. Enterprise Management System (EMS)

3. Antivirus Software

4. SAN Storage

5. SAN Switches

6. Tape Library



7. All necessary software components including but not limited to Operating

System, Backup Software, and SAN Storage Management Software

8. The SI must propose a management system that manages the end-to-end

performance and availability of CCTNS service delivery. The system must

provide management for Datacenter and Network Infrastructure

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-14 to this RFP.

SI shall provide Bill of Materials for all the hardware, infrastructure items and other

items which are part of the scope.

Given below is an indicative format for Technical Bill of Materials:

Data Center in Puducherry

S No. Item Original Equipment

Manufacturer

Item\ Desc. (Model/Make)

Unit of measurement

Quantity # (units)

Please insert details as required

Bill of materials for DC & DR is provided in Annexure-12.

5.8 Other Requirements

Performance Management System

i) Integrated Performance Management System for Monitoring Networks, Systems & Databases:

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

The tool should provide an integrated performance view for all the managed systems and networks along with the various threshold violations alarms in them. It should be possible to drill-down into the performance view to execute context specific reports:

i. At-A-Glance Reports to present a single page report on vital device statistics like Backplane Statistics, Buffer Statistics, CPU Utilization, Fan Status, Memory Statistics, Power Status, Temperature Status, Packets Statistics



ii. Top N Reports to present a list of elements that exceed / fall below a particular threshold value. This would help network operators to identify elements that share specific performance characteristics.

iii. Trend Reports to present a single graph of a single variable (e.g. CPU utilization) for multiple devices across time. This would help network operators & IT managers plan or capacity and identify long drawn problems

iv. What-If Reports to perform capacity planning by observing the effect of changes in capacity & demand (for example, the report should indicate what the bandwidth utilization would be if the demand was double the historical value)

The system must provide capability to measure & generate detailed performance reports for the following common TCP/IP applications:

DHCP: Measure the round trip latency required to obtain an IP address. DNS: Measure the DNS lookup time including Latency and Packet Loss FTP : Measure the time it takes to connect and transfer a file including

Latency and Packet Loss ICMP Ping : Measure round trip source to destination including Latency and

Packet Loss Latency and Packet Loss for POP3, SMTP, TCP, UDP Echo Test etc.

The proposed system must have a report building and customization option built-in which will enable complete customization flexibility of performance reports for network devices and monitored servers.

The proposed performance management system tool should provide an integrated performance view for all the managed systems and networks along with the various threshold violations alarms in them. It should be possible to drill-down into the performance view to execute context specific reports

The tool should have the capability to configure different polling speeds for different devices in the managed infrastructure with capability to poll critical devices using 30 second poll periods.

ii) System and Database Performance Monitoring Requirements

o The proposed server performance management system shall integrate network

performance management systems and provide the unified performance state

view in a single console. The current performance state of the entire network

and server infrastructure shall be visible in an integrated console.

o The proposed tool must provide lightweight server agents to ensure availability

and performance for target server nodes and deliver scalable, real-time

management of critical systems.

o The proposed tool should be able to monitor various operating system

parameters such as processors, memory, files, processes, file systems, etc. where

applicable, using agents on the servers to be monitored. It should be possible to

configure the operating system monitoring agents to monitor based on user-

defined thresholds for warning/critical states and escalate events to the central

console of the enterprise management system.

o The proposed tool should integrate with network performance management

system and support operating system monitoring for various platforms

including Windows, UNIX and Linux.

o The proposed solution should support management following parameters:



Processors: Each processor in the system should be monitored for CPU

utilization. It should compare Current utilization against user specified warning

and critical thresholds.

File Systems: Each file system should be monitored for the amount of file

system space used, which should be compared to user-defined warning and

critical thresholds.

Log Files: Logs should be monitored to detect faults in the operating system, the

communication subsystem, and in applications. System agents should also

analyze log files residing on the host for specified string patterns.

System Processes: System agents should provide real-time collection of data

from all system processes. Using this it should help identify whether or not an

important process has stopped unexpectedly.

Memory: System agents should monitor memory utilization and available swap

space and should raise an alarm in event of threshold violation.

The proposed database performance management system shall integrate

network and server performance management systems and provide the unified

view of the performance state in a single console. It should be able to automate

monitoring, data collection and analysis of performance from single point.

It should also provide the ability to set thresholds and send notifications when

an event occurs, enabling database administrators (DBAs) to quickly trace and

resolve performance-related bottlenecks. The proposed management system

must send alerts for an array of server conditions, including inadequate free

space, runaway processes, high CPU utilization and inadequate swap space.

iii) Application Performance Management System & End-User Monitoring System Web based Applications and Portals

The proposed solution must determine if the root cause of performance issues is

inside the monitored application, in connected back-end systems or at the

network layer from a single console view

The proposed solution must proactively monitor 100%of real user transactions;

detect failed transactions; gather evidence necessary for triage and diagnosis of

problems that affect user experiences and prevent completion of critical

business processes

The proposed solution must provide deeper end-to-end transaction visibility by

monitoring at a transactional level and without deploying any software at end

user desktop. The solution must provide a single view that shows entire end-to-

end real user transaction and breaks down times spent within the application

components, SQL statements, backend systems and external 3rd party systems.

The proposed solution must be able to provide root-cause probability graphs for

performance problems showing the most probable root-cause area within

application infrastructure.

The proposed solution must be able to detect production Memory Leaks from

mishandled Java Collections and isolate exact component creating leaking

Collection.

The proposed solution must allow monitoring granularity of no more than 15

seconds for all transactions.



The proposed solution must provide real-time monitoring of resource utilization

like JVM memory usage, Servlets, EJB pools, DB connection pools and Threads.

The proposed solution must tie SQL statements to components involved, i.e. SQL

queries should be able to get correlated to the Java components calling them.

This should be clearly visible by showing the transaction call stack ("Blame

stack").

The proposed solution must identify any changes to application configuration

files (.xml, properties etc), File system or application code and be able to

correlate changes to application performance dynamically in production

environments.

The proposed solution must proactively identify any thread usage problems

within applications and identify stalled (stuck) threads. The proposed solution

must also monitor web services across multiple processes (cross JVM tracing)

The proposed solution should allow access to performance data both using a

Graphical user interface (GUI) and over the web (web based access) and provide

ability to monitor performance of applications up to the method level of

execution (Java/.Net method) 24x7 in production environments with negligible

impact on monitored application.

The proposed solution must provide for dynamic instrumentation of application

code, i.e. enhance be able out of the box monitoring with extra monitoring

definitions without having to restart application.

The proposed solution should measure the end users' experiences based on

transactions without necessitating installation of client agents / probes on end-

user desktops.

The proposed system must be able to detect user impacting defects and

anomalies and reports them in real-time. The proposed system must also be able

to provide user usage analysis and show how user's success rate, average time

and transaction count has changed over a specific period of time such as current

week versus previous week.

The proposed system must be able to pro-actively determine exactly which real

users were impacted by transaction defects, their location and status.

The proposed system must be able to provide the ability to detect and alert

when users experience HTTP error codes such as 404 errors or errors coming

from the web application.

Helpdesk Solution

i) The SI shall proposed an Integrated ITILV3- V2 complaint Helpdesk Solution for end-to-end service support using best practices for Incident, Problem, Change and Configuration Management.

o The proposed helpdesk solution must be ITIL V3-V2 complaint and provide

built-in support for various ITIL v3-v2 processes.

o The proposed helpdesk solution must be certified from external agencies (like

Pink verify Certificate)

o The proposed helpdesk solution must provide flexibility of logging, viewing,

updating and closing incident manually via web interface.



o The proposed helpdesk solution must provide seamless integration to log

incident automatically via system and network management.

o The proposed helpdesk solution must be able to provide flexibility of incident

assignment based on the workload, category, location etc. The system must have

an escalation policy that will allow flexibility of associating with different criteria

like device/asset/system, category of incident, priority level, organization and

contact.

o The proposed helpdesk solution must provide classification to differentiate the

incident via multiple levels/tiers of categorization, priority levels, severity levels

and impact levels.

o The proposed helpdesk solution must provide web-based knowledge database

to store useful history incident resolution.

o The proposed helpdesk solution must contain built-in workflow management

engine and a knowledge tools system that can provide grouping access on

different security knowledge articles for different group of users.

o The proposed helpdesk solution must have a strong reporting module built in it

to generate various KPI / KQI related metrics and reports for the service support

processes including Incident Management, Problem Management etc. .

o The proposed helpdesk solution must be able to log and escalate user

interactions and requests.

o The proposed helpdesk solution must have the ability to track work history of

calls to facilitate troubleshooting.

o The proposed helpdesk solution must support tracking of SLA (service level

agreements) for call requests within the help desk through service types.

o The proposed helpdesk solution must support request management, problem

management, configuration management and change order management.

o The proposed helpdesk solution must be capable of assigning call requests to

technical staff manually as well as automatically based on predefined rules, and

should support notification and escalation over email, web etc.

o The proposed helpdesk solution must have an integrated CMDB for better

configuration management & change management process. CMDB must provide

built-in support for CI families, CI Classes and CI Relationship Types out of the

box.

o The proposed helpdesk solution must have a top management dashboard for

viewing the helpdesk KPI in graph & chart formats.

o The proposed helpdesk solution must support remote management for end-user

& allow analysts to do the desktop sharing for any system located anywhere

connected to internet. Remote desktop sharing in helpdesk tool should be out-

of-the-box, agent-less & all activities must be automatically logged into the

helpdesk ticket.

ii) The SI must deploy specific management solutions to carry out Asset Management, Software Delivery & Remote Control System for Desktops, Servers and Laptops at client side locations and central data center:

The proposed desktop management system should provide single integrated agent

for asset management, remote software delivery and remote desktop control.



The proposed Asset Management solution must provide inventory of hardware and

software applications on end-user desktops including information on processor,

memory, operating system, mouse, key board of desktops etc. through agents

installed on them.

The proposed Asset Management solution must have reporting capabilities; provide

predefined reports and the possibility to create customized reports on data in the

inventory database. Report results could be displayed as lists or graphs. The

proposed must have the capability to export the reports to CSV, HTML and XML

format.

The proposed Asset Management solution must provide the facility for user defined

templates to collect custom information from desktops. The proposed solution must

also provide facility to recognize custom applications on desktops including ability

to collect WBEM information.

The proposed Asset Management solution must support administrators to register a

new application to the detectable application list using certain identification

criteria’s (Like executable, Date/time stamp etc.). The new application must be

detected automatically from next time the inventory is scanned.

The proposed Software Deployment System must support delivery, installation, and

un-installation of software (ex. Patches of Anti-virus solution etc.) installed on end-

user desktops by software delivery remotely through agents installed on them. It

must allow pre- and post-installation steps to be specified if required & support

rollback in the event of failure in installing software to end-user desktops.

The proposed Software Deployment System should support both push and pull

software distribution modes. A catalog/advertisement option of the existing

software delivery packages must be provided for end-user to download and install

software of his / her choice.

The proposed Remote Desktop Control Management System should allow remote

control of end-user desktop for facilitating resolution of desktop issues without the

need to go to the end-user desktop, through agents installed on them.

The proposed Remote Desktop Control Management System must support Seamless

integration with management applications such as helpdesk, asset management and

Software delivery.

The proposed Remote Desktop Control Management System must support remote

Reboot & Chat functions between nodes and including capability to encrypt the

authentication traffic.

Security Management System

i) Host-based Server Access Control System

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.

Host based security solution must allow controlling of access to all system resources

including data files, devices, processes/daemons and audit files.



The solution should provide fined grained User Control. The proposed solution must

allow controlling actions and access to resources of all users including privileged

accounts such as root / administrator. The solution must track the "real user" even

in case of surrogates.

The solution should provide Rights Delegation. The proposed solution must provide

the ability to designate specific users as Administrators, Auditors, and Password

Managers etc with appropriate rights. The proposed solution 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. The proposed solution

must support management and policy distribution across various 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.

Solution must intercept and verify every request to change user identity and

maintain a reliable audit trail.

The solution should support operating systems such as IBM-AIX, Digital Unix, HP-UX,

Sun Solaris, and Windows 2000/2003.

The solution must provide support for IPv6 and FIPS140-2

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

iii) Identity and Access Management

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 have APIs to enable additional user management operations on UNIX, NT over

and above the default operating system account set-up.

Must support enforcement of a centrally-defined security policy, e.g. for access

rights, password lengths

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 include out-of-the-box support for specified relevant third-party technologies -

Authentication, PKI, and smart cards.

Provide capabilities to perform recertification of identities across the Enterprise.

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 provide protection from cross-site scripting

The solution should provide a seamless universal single sign-on across web and

client server applications. Both client server single sign-on and web single sign-on

solutions should integrate out of the box.

Solution should support SAML (the standard for exchanging authentication and

authorization information between security management systems) without coding,

including both SAML Consumer & SAML Producer modes of operation. .

SAML Consumer capability should support both one-to-one user mapping as well as

many-to-one user mapping.

Solution should support 4 & 8-way SMP servers.

5.9 Data Migration and Data Digitization

Migration of the data from the other systems/manual operations to the new system will include

identification of data migration requirements, collection and migration of user data, collection

and migration of master data, closing or migration of open transactions, collection and

migration of documentary information, and migration of data from the legacy systems.

The SI shall perform the data digitization & migration from manual and/or the existing systems

to the new system. The Data digitization & migration to be performed by the SI shall be

preceded by an appropriate data migration need assessment including data quality assessment.

The Data migration strategy and methodology shall be prepared by SI and approved by

Puducherry Police. Though Department is required to provide formal approval for the Data



Migration Strategy, it is the ultimate responsibility of SI to ensure that all the data sets which are

required for operationalization of the agreed user requirements are digitized or migrated.

Any corrections identified by UT 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

UT. So far as the legacy data is concerned, they are either available as structured data in the IT

systems that are currently used by UT 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

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 by using data migration utility

3. Carry out the digitization 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 UT Nodal Officer for verification, including

number of records, validations (where possible), other controls / hash totals. Highlight

errors, abnormalities and deviations.

6. Incorporate corrections for the errors discovered during verification process, as

proposed

7. Get final sign off from UT Nodal Officer/Empowered Committee for 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

Data Migration of records

A one‐time effort to migrate the CCIS & CIPA data of last ten years across the police stations into

the system is required. Currently the data digitization process is in its infancy stage and

following table provides the indicative estimate of number of records to be migrated from CCIS

& CIPA out of total number of records. The following records are considered but not limited to

as a single ‘CASE’.

S. No. Data Migration

Name of the records CCIS Number of Records

(last 20 years)

CIPA Number of Records

(from 2006)

1. FIR & Other Documents 54,828

50,054

Total 54,828 50,054



Total (CCIS+CIPA) = 1, 04,882

Note: Now CCIS is not functional in UT of Puducherry & all the data have been submitted to

NCRB & no back-up is available with UT of Puducherry.

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 UT Nodal Officer.

1. Analysis

Analysis of the legacy data and its creation, conversion, migration and transfer to the proposed

new data base schema will be started during the scoping phase and shall take a parallel path

during the design and development phase of the application. It will cover the following steps:

a) Analyze the existing procedures, policies, formats of data in lieu of the new proposed

system to understand the amount of the data and the applicability in CCTNS

b) Write a specification to create, transfer and migrate the data set

c) Document all exceptions, complex scenarios of the data

d) This phase will generate the specification for Data Take–On routines

2. Transformation

Transformation phase can be commenced after integration testing phase. It will entail the

following steps:

a) Identify the fields, columns to be added/deleted from the existing system

b) Identify the default values to be populated for all ‘not null’ columns

c) Develop routines to create (Entry if any by data entry operators), migrate, convert the

data from hard copies, old database (if any), computer records to the new database

d) Develop test programs to check the migrated data from old database to the new

database

e) Test the migration programs using the snapshot of the production data

f) Tune the migration programs & iterate the Test cycle

g) Validate migrated data using the application by running all the test cases

h) Test the success of the data take-on by doing system test

3. Data Take-on

Take–On phase will be initiated when the proposed solution is ready to be deployed. It will

entail the following steps:

a) Schedule data transfer of the computerized data that has been newly created by the data

entry operators based on the hard copy records.

b) Schedule data transfer of the existing digital data in the proposed new format

c) Migrate the data from an old system (legacy) to the envisaged database

d) Test on the staging servers after the data take-on with testing routines



e) Migrate from staging servers to production servers

f) Deploy and rollout the system as per the project plan

Additional Guidelines for Data Migration

1. SI shall migrate/convert/digitize the data at the implementation sites of UT.

2. SI shall formulate the “Data Migration Strategy document” which will also include

internal quality assurance mechanism. This will be reviewed and signed–off by UT prior

to commencement of data migration.

3. SI shall incorporate all comments and suggestions of UT in the Data Migration Strategy

and process documents before obtaining sign–off from UT.

4. SI shall perform mock data migration tests to validate the conversion programs.

5. SI shall ensure complete data cleaning and validation for all data migrated from the

legacy systems to the new application.

6. SI shall validate the data before uploading the same to the production environment.

7. SI shall generate appropriate control reports before and after migration to ensure

accuracy and completeness of the data.

8. SI shall convey to UT 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 UT.

9. In the event UT is unable to obtain all the mandatory fields as conveyed by SI, SI shall

suggest the most suitable workaround to UT. SI shall document the suggested

workaround and sign-off will be obtained from UT for the suggested workaround.

10. SI shall develop data entry programs / applications that may be required for the

purpose of data migration in order to capture data available with / obtained by UT in

non – electronic format.

11. SI shall conduct the acceptance testing and verify the completeness and accuracy of the

data migrated from the legacy systems to the proposed solution.

12. UT may, at its will, verify the test results provided by SI.

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

The SI is also 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 UT. SI shall

validate the data in the CIPA systems and also migrate the data to CCTNS. In addition, the UT

may also decide to cover other applications currently being used under this data migration and

integration effort if felt necessary.

List of CIPA Police Stations are provided in Annexure-1

Data Digitization

In addition to the data migration SI would also digitize the historical data (covering the last 10

years). The historical data to be digitized would include crime (case/incident) data, criminals’

data, the data from the 7 IIF and relevant historical information parameters/data used to

generate registers and reports. The unit of data digitization shall be one case file. Each case file

shall consist of information pertaining to all 7 IIFs, information parameters relevant to generate

specific registers from that case file and information parameters relevant to generate specific

reports from that particular case file.



S. No.

Details of Data Digitization Requirement

Name of the Records Number of Records/Cases

To be Digitized

1 Case Files (IIF 1 to 7) Around 85,500 Criminal cases are registered in all Police Stations in the UT in the last 10 years i.e. since 1/1/2001 up to Feb 2011. These case files needs to be digitized and migrated. As scheduled, CAS application would be live in the UT in the mid of 2012. Therefore, data from March 2011 to till the assumed period in the year 2012 also needs to be digitized/migrated and this may be 20,000 additional Case Files approximately. A total of 85,500+10,000 = 95,500

Total 95,500

List of Case Files for Data Digitization is provided in Annexure-5

5.10 Capacity Building

Capacity Building is a highly critical component of CCTNS. The objective of CCTNS Capacity

Building (CB) initiatives is to empower the direct users and other stakeholders of CCTNS to

optimally use CCTNS and enhance outcomes in crime investigation, criminals tracking and other

core police functions; and also ensure a smooth functioning of CCTNS.

The System Integrator would render CB services in both areas, as per the “bundling” approach

adopted for CCTNS. The SI holds the responsibility for creation of training material, designing

the training programs and their delivery to the target group.

Building capacities at various levels is critical to the successful implementation of the

recommended IT initiatives. Also, the training programs would cover at minimum general/basic

computer awareness programs in addition to CCTNS-specific programs in order to ensure

adoption of the system at the police station level.

The break-up of the police force in the UT of Puducherry identified for CB under CCTNS Project

is provided below:

Group Officers No. of Police Personnel

A Covers all senior officers including IGP, DIG, SSP & SPs 25

B Covers all Police Inspectors, SIs and ASIs 270

C Covers all Head Constables, Constables and clerks 1546

Total 1841

Total Strength rounded to 2000

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.

Following is the indicative list of the training programs that needs to be administered to the

group of officials as identified above. The overall responsibility of administering the training

program lies with the SI.

Sl No. Levels Training Program No. of

traine

es

Remarks

1. Level-I Basic Computer Awareness

2500

Presently this training is being provided by Puducherry Cooperative Institute

2. Level-II 1. Database Management

1000

Puducherry Cooperative Institute will provide this training to identified police personnel

2. Role based training for

CCTNS application users

3. Awareness and sensitization

of benefits of IT System

SI would be responsible for this training

3 Level-II 4. Network & System

Administrator Training

15 SI would be responsible for this training

Following infrastructure will be required to build a state of the art training center at existing

Police Training School.

S. No

Infrastructure needed PTS

1 Desktop (OS Preloaded) 50

2 Multi Function Printer 5

3 LCD Projector 1

4 Screen 1

5 White Board 1

6 UPS cum inverter (120 minutes backup) 1

7 Inverter (fans & Tube lights) 1

8 Finger Print Reader 10

90 Digital Camera 2

10 Web Camera 50



Note:

Under Capacity Building two level of training scheduled as cited below and approved by

Puducherry Government as a move towards e-Governance in accordance to the availability status.

1. Level-I Training is for imparting Basic Computer Training Skills for all police personnel

and it is being conducted by Puducherry Cooperative Institute avoiding working hours

with no loss of Manpower of routine duties.

2. Level-II training is for CCTNS Application and Database Management for selected persons

of the department to work in CCTNS Application especially System Administrator, Writers,

SHO, CI, SI, ASI and Head Constable who are working in Police Stations, while

Administrative Awareness & sensitization training will be provided to other senior officials.

If any other is proposed for training with the approval of the Empowered Committee’s time

to time will also be accommodate in Level-II training.

3. Government of Puducherry has already approved cost for Level-I & Level-II training

courses for each candidate.

4. Since all the necessary infrastructure facilities and training on Database Management will

be provided by Cooperative Institute, the System Integrator will impart rest of the

trainings in Level-II such as (Role based training for CCTNS Application, Awareness &

Sensitization training & Network & System Administrator Training) at the provided

infrastructure.

5. System Integrator will get the payment from the Puducherry cooperative institute

for all Level-II trainings.

6. The Trainer to be provided by the System Integrator for CCTNS Application training, which

will be synchronized with the Puducherry Government Co-Operative Computer Training

Institute with whom the training was already entrusted.

The UT 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 UT’s Nodal Agency covering the training strategy, environment, training need analysis and

role based training curriculum. SI shall own the overall Training plan working closely with the

UT’s Nodal Agency’s Training team. SI shall coordinate overall training effort.

11 Electronic Pen 2

12 Operational Expenses 1

13 Site Preparation 1



Develop District-Wise Training Schedule and Curriculum

SI shall develop and manage the District-Wise training schedule in consultation with UT’s Nodal

Agency, aligned with the overall implementation roadmap of the project and coordinate the

same with all parties involved. Training schedule shall be developed by solution and shall be

optimized to reduce business impact and effective utilization of Training infrastructure and

capacities. The training curriculum for the CCTNS training program should be organized by

modules and these should be used to develop the training materials. The training curriculum

outlines the mode of delivery, module structure and outline, duration and target audience.

These sessions should be conducted such that the users of the application/modules are trained

by the time the application “goes-live” in the District with possibly no more than a week’s gap

between completion of training and going live of modules. Continuous reporting (MIS) and

assessment should be an integral function of training. SI shall also identify the languages to be

used by the end-user for entering data and ensuring multi-language training to the end users as

per requirement.

Develop Training Material

Based on their needs and the objectives of CCTNS, training programs could be organized under the following themes:

1. Role-based training on the CCTNS application – Basic and Advanced. This training should

be in a role based, benchmarked and standardized format, multi-lingual and lead to

learning completion and assessment. It should also allow for self-learning and retraining.

Training would include mechanism for demonstration us in

audio/video/simulated/demo practice exercises and evaluation of trainees.

2. “Train the Trainer” programs, where members of the police staff would be trained ton

enable them to conduct further training programs, thus helping build up scalability in the

training program and also reducing the dependency on external vendors for training.

3. System Administrator training: a few members of the police staff with high aptitude

would be trained to act as system administrators and troubleshooters for CCTNS.

4. Customization of the Training Manuals, User Manuals, Operational and Maintenance

Manuals provided along with the CCTNS CAS Software.

5. Design and development of the Training Manuals, User Manuals, Operational and

Maintenance Manuals for the modules developed at the UT 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 UT, 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 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 UT Headquarters by the System Integrator.

SI shall also impart simulated training on the actual CAS (State/UT) with some real life like

database. The SI should create case studies and simulation modules that would be as close to

the real life scenario as possible. The objective of conducting such trainings would be to give

first had view of benefits of using CAS system. Such specialized training should also be able to

provide the participant a clear comparison between the old way of crime and criminal

investigation against the post CCTNS scenario. This training needs to be conducted by the SI at

the very end when all the other trainings are successfully completed. This training may seem

similar to role play training mentioned in the section above however, in this simulated training,

the SI would ensure that the IO’s are provided an environment that would be exactly similar at a

Police Station post CAS (State/UT) implementation.

Most of the training would be an Instructor-Led Training (ILT) conducted by trained and

qualified instructors in a classroom setting. To maintain consistency across CCTNS trainings,

standard templates should be used for each component of a module.

An ILT course will have the following components:

Course Presentation (PowerPoint)

Instruction 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

walkthrough and self assessment modules.

Select set of police staff with high aptitude group and/or relevant prior training, are to be

imparted with the training/skills to act as system administrators and also as troubleshooters

with basic systems maintenance tasks including hardware and network.

Deliver Training to Trainers (Internal and Trainers from the Training Colleges)

SI shall help UT’s Nodal Agency in assessing and selecting the internal trainers as well as the

trainers at training colleges who can conduct the end user training subsequent to the training by

the SI. SI shall coordinate the ‘Train the Trainer’ session for the identified trainers to ensure that

they have the capability to deliver efficient training.

In addition to the training delivered to the end-users, the trainers should also be trained on

effectively facilitate and deliver training to end users. Also, it is advisable to always run pilots



for any training program before deployment. This training will hence serve as the pilot and as a

training session for trainers as well. In addition the end-user training sessions, 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.

UT will periodically monitor the training effectiveness through the performance metrics and

Service levels and the SI shall comply with the same.

SI shall help the UT with complete Change Management exercise needed to make this project a

success. In fact Change Management will have to subsume ‘training’ as a key enabler for change.

Following outlines the responsibilities of SI with respect to designing and implementation of

change management plan for the Project.

Change Management

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 UT Nodal Agency shall form various stakeholder groups to address the Change Management

Initiative. Stakeholders are all those who need to be considered in achieving project goals and

whose participation and support are crucial to its success. A key individual stakeholder or

stakeholder group is a person or group of people with significant involvement and/or interest in

the success of the project.

Stakeholder analysis identifies all primary and secondary stakeholders who have an interest in the

issues with which the CCTNS project is concerned. The stakeholder groups will be the set of core

users (Change Agents) who will directly participate in the awareness and communication



initiatives, workshops, and provide feedback to the District Mission Teams and State Empowered

Committee.

Stakeholder groups can be categorized into below categories, based on their influence and role

in managing the change and making it successful:

Group I: Identify the key senior officers (ADGP, IG, and DIG) responsible for Crime, Law

and Order etc who are directly impacted by the CCTNS with respect to

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

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.

Communication and Awareness

Communication & Awareness campaigns will be conducted throughout the duration of the

implementation of the CCTNS project across the UT at Project, Program level as well as for

General awareness. SI shall work with the identified internal change agents (identified from the

District and State Mission Teams) for all the Communication and Awareness Programs. SI shall

utilize existing channels of communication and at the same time use innovative methods of

communication for effectiveness. SI should ensure that the communication messages are

consistent, continuous and easy to understand and wherever possible in vernacular medium

using all available channels. SI shall align communication content, timing and delivery to the

deployment phases/plan of each solution.



S. No Activities Details Frequency

1 Develop detailed communication plan

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

Once

2 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

3. Deliver Communication Events

Prior to implementing the plan, the SI shall obtain the necessary sign-offs from UT on the Communication Strategy & plan and make necessary changes as recommended by UT.

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.

Recurring Activity (once a month) over the entire duration of the SI

Change Management Workshops

SI shall conduct Change Management workshops build appreciation of change management and

develop change leadership across the stakeholder groups. SI shall design the necessary content

(reading material, presentations) in English, 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 UT Headquarters and at least one Change Management

Workshop (minimum of one-day) all of the Districts (at the District Headquarters) covering at



least 3 officers/constables (SHO, SI/ASI/HC, and Station Writer) from each police station in the

district.

The SI is required to conduct the Change Management Workshops for all the identified Police

personnel in a phased manner in line with the overall implementation plan. These workshops

shall be conducted at the locations provided by the UT. 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.

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

Qualification Eligibility for Project Team: Handholding staff for police station:

Handholding Staff

Desired qualification/Experience M.Sc. (IT/CS)/ PGDCA / BCA

Overall experience of 1-2 year of Application Software/LAN/WAN/PC

troubleshooting, Data Entry on Computer Applications, Working

Proficiency on office suite. Full computer literacy and excellent

fluency in Hindi language

Location Police Station

Minimum Manpower

Service window



Other Project Team 1. Project Manager:

Project Manager

Desired Qualification / Experience

Post-Graduate Level of education in related fields of social sciences, environmental engineering, economics and/or planning (education and/or experience on sustainable development/ platform is an asset)

Minimum 5 years of proven professional experience as Project Manager/Project Leader in the management of state level government/ corporate projects in similar fields

Experience in project administration, coordinating, planning, execution, monitoring and reporting

Good understanding of Project Life Cycle & Management Full computer literacy and excellent fluency in English language

Location HQ

Minimum Manpower 1

Service window 9*6

2. System & Network Administrator:

System & Network Administrator


B. Tech or BE (CS) / MCA / M.Sc.

(IT/CS)

OEM Certified

Overall experience of 2-3 year of

systems and network administration in

large projects

Expert in Network Administration -

LAN, MAN & WAN.

Full computer literacy

Fluency in English & Hindi language

Location DC

Minimum Manpower 2

Service window 24*7



3. Database Administrator

Database Administrator


B. Tech or BE (CS) / MCA / M.Sc.

(IT/CS)

OEM Certified

Overall experience of 2-3 year of

Database administration in

large projects

Expert in Database Administration



Location DC

Minimum Manpower 2

Service window 24*7

4. Technical Field Staff:

Technical Field Staff


BE (CS) / MCA / M.Sc. (IT/CS)

Overall experience of 2-3 year of LAN/

WAN/ Servers / Storage/ DC & DR

Software / Hardware support



Location Police Stations

Minimum Manpower 48

Service window 24*7

5.12 Requirement on adherence to Standards

CCTNS system must be designed following open standards, to the extent feasible and in line

with overall system requirements set out in this RFP, in order to provide for good inter-

operability with multiple platforms and avoid any technology or technology provider lock-in.

Compliance with Industry Standards

In addition to above, the proposed solution has to be based on and compliant with industry

standards (their latest versions as on date) wherever applicable. This will apply to all the

aspects of solution including but not limited to design, development, security, installation, and

testing. There are many standards that are indicated throughout this volume as well as

summarized below. However the list below is just for reference and is not to be treated as

exhaustive.



Particulars Required Standards to be adhered to

Portal development W3C specifications, GIGW specifications

Information access/transfer protocols SOAP, HTTP/HTTPS

Interoperability Web Services, Open standards

Photograph JPEG (minimum resolution of 640 x 480 pixels)

Scanned documents TIFF (Resolution of 600 X 600 dpi)

Biometric framework BioAPI 2.0 (ISO/IEC 19784-1:200 Specification

Finger print scanning IAFIS specifications

Digital signature RSA standards, Inter operability guidelines

issued under IT Act

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.

5.13 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,

UT 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 UT, one for audit &

certification of security and control aspect of the system and the other for audit & certification

of overall application software.

UT 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

UT, will not, however, absolve the operator of the fundamental responsibility of designing,

developing, installing, testing and commissioning the various components of the project to

deliver the services in perfect conformity with the SLAs.

Following discusses the acceptance criteria to be adopted for system as mentioned above:

1. Functional Requirements Review

The system developed/customized by SI shall be reviewed and verified by the agency against

the Functional Requirements signed-off between UT 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.

2. Test cases and Requirements Mapping

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

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

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

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

i) The SI must provide System and Database Performance System for all servers in the

Datacenter (referenced in DC IT Infrastructure requirements)

ii) The SI must provision for End-User response time monitoring and transaction based

deep-dive analysis for Web based applications. (referenced in DC IT Infrastructure

requirements)

iii) The SI must provision for Integrated Performance Management System for

Monitoring Networks, Systems & Databases: (referenced in Reporting requirements

above)

iv) The SI must provide a Traffic Analysis and Reporting System for deep-dive

diagnostics (referenced in Reporting requirements above)

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

i) Infrastructure Fault Management System for the following functions:

a) Infrastructure Fault Analysis

a. The proposed solution must automatically discover manageable elements

connected to the network and map the connectivity between them. The

Network Fault Management consoles must provide the topology map view

from a single central console.

b. The proposed system must support multiple types of discovery including IP

range discovery, Seed router based discovery & Trap-Based Discovery

c. The system should provide discovery & inventory of heterogeneous physical

network devices like Layer-2 & Layer-3 switches, Routers and other IP

devices and do mapping of LAN & WAN connectivity with granular visibility

up to individual ports level.

d. The system must be able to support mapping and modeling of the

infrastructure grouped by network connectivity, physical location of

equipment and user groups or departments



e. The system should support maps grouped by network topology, geographic

locations of the equipments and user group/departments. These should help

in understanding physical Network, virtual Network services and the

relationships between them.

f. The system must provide visualization tools to display network topology and

device to device connectivity. The system must also be able to document

connectivity changes that were discovered since the last update.

g. The proposed solution must provide a detailed asset report, organized by

vendor name and device, listing all ports for all devices. When a report is run

the administrator must have an option of specifying the number of

consecutive days the port must be “unused” in order for it to be considered

“available”.

h. The proposed solution should provide out of the box root cause analysis with

multiple root cause algorithms inbuilt for root cause analysis.

i. It should have a strong event correlation engine which can correlate the

events on the basis of event pairing, event sequencing etc.

j. The system must be able to ‘filter-out’ symptom alarms and deduce the root

cause of failure in the network automatically

k. The proposed solution must support a an architecture that can be extended

to support multiple virtualization platforms and technologies

b) Configuration Management for Critical Network Devices

a. The system should be able to clearly identify configuration changes as root

cause of network problems

b. The proposed fault management solution must able to perform real-time or

scheduled capture of device configurations

c. The proposed fault management solution must able to store historical device

configurations captured in the database and thereby enable comparison of

current device configuration against a previously captured configuration as

well as compare the current configuration against any user-defined standard

baseline configuration policy.

c) Advanced IP Services Management for technologies like QoS and Multicast

a. The proposed solution should be able to support response time agents to

perform network performance tests to help identify network performance

bottlenecks.

b. The proposed solution should be able to monitor QoS parameters configured

to provide traffic classification and prioritization for reliable VoIP transport.

The proposed solution should discover and model configured QoS classes,

policies and behaviors.

c. The proposed solution should provide the ability to discover, map & monitor

multicast sources & participating routers wherein the system should be able

visualize the distribution tree in the topology map.

d) Infrastructure-based SLA Management and Integration Requirements

a. The proposed service management system should provide a detailed service

dashboard view indicating the health of each of the departments / offices in



the organization and the health of the services they rely on as well as the

SLAs.

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

c. Root cause analysis of infrastructure alarms must be applied to the managed

Business Services in determining service outages. SLA violation alarms must

be generated to notify whenever an agreement is violated or is in danger of

being violated.

d. The system must provide the capability to designate planned maintenance

periods for services and take into consideration maintenance periods

defined at the IT resources level. In addition the capability to exempt any

service outage from impacting an SLA must be available.

e. The proposed NMS should provide unified workflow between the fault and

performance management systems including bi-directional and context-

sensitive navigation

f. The system must support seamless bi-directional integration to helpdesk or

trouble ticketing system

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

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

8. 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 UT to SI.

i) End to End Service Level Management System for the Datacenter and Network

Infrastructure

Provide end-to-end, comprehensive, modular and integrated management of IT

infrastructure components to maximize the availability of IT services and SLA

performance.

The management system needs to aggregate events and performance information

from the domain managers and tie them to service definitions. This capability is



critical for the administrators to have a complete view of the performance and

availability of various application services being managed.

The proposed tools should automatically document problems and interruptions for

various IT services offered and integrate with the service level management system

for reporting on service level agreements (SLAs).

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.

Provide a detailed service dashboard view indicating the health of each of the

departments / offices in the organization and the health of the services they rely on

as well as the SLAs.

Provide a high level view for executives and other users of the system using a real

time business services Dashboard.

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.

Support for a User Definition Facility to define person(s) or organization(s) that uses

the business Services or is a party to a service level agreement contract with a

service provider or both. The facility must enable the association of Users with

Services and SLAs.

The Service Level Agreements (SLAs) definition facility must support defining a set

of one or more service Guarantees that specify the Service obligations stipulated in

an SLA contract for a particular time period (weekly, monthly, and so on).

Guarantees supported must include one that monitors service availability (including

Mean Time to Repair (MTTR), Mean Time between Failure (MTBF), and Maximum

Outage Time thresholds) and the other that monitors service transaction response

time.

SLA violation alarms must be generated to notify whenever an agreement is violated

or is in danger of being violated.

Provide the capability to designate planned maintenance periods for services and

take into consideration maintenance periods defined at the IT resources level. In

addition the capability to exempt any service outage from impacting an SLA must be

available.

A historical reporting facility that will allow for the generation of on-demand and

scheduled reports of Business Service related metrics with capabilities for

customization of the report presentation.

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



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

SI shall only provide requisite support and coordinate with the UT Department for Audit,

User acceptance and Certification.

5.14 Insurance

The successful bidder shall insure the entire hardware infrastructure procured, supplied and

commissioned at all the locations till Go-Live of Complete CCTNS Solution against theft,

vandalism, fire and lightening. In case of any such event, the vendor will be required to take

remedial actions within the timelines defined in the SLAs in this RFP.

5.15 Scope of Services during Post Implementation Phase

The SI shall be responsible for the overall management of the system including the application

and entire related IT Infrastructure. The details of the post implementation support services are

provided as an Annexure-8 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 5 years following

the deployment and “Go-Live” of the solution in the UT In case each District is declared as

“Go-Live” at different instances during the project roll-out, the Operations and Maintenance

Services for the District will start following the deployment and “Go-Live” of the solution in

the District and SI shall continue to provide the Operations and Maintenance Support for a

period of 5 years following the deployment and “Go- Live” of the solution in the last District.

<< The post implementation phase services shall include Application, IT infrastructure and

enabling infrastructure maintenance services/ facility management services at all client

locations for ensuring adherence of SLAs as per the guidelines mentioned in the SI RFP

template>>.

<< Infrastructure maintenance services for CIPA police stations shall also be part of the

scope of services during post implementation phase>>

The details of the post implementation support services are provided in Annexure-8



6. IMPLEMENTATION AND ROLL-OUT PLAN

It is proposed to roll out CCTNS in three phases. Deployment of hardware, connectivity and

other infrastructure across all police stations, higher offices and other police units would take

place in the first two phases. CAS (Core Application Software) would be rolled out in three

phases. The core focus of each of the three phases is delineated below:

Implementation of CCTNS in Union Territories of Puducherry covers 95 locations including 48 –

PS, 15 – Circles, 6-SDPOs, 7-SPs, 2-Districts (SSP), 1–SSP (C&I), 1-SHQ, 4-Jail, 1- Finger Print

Bureau, 5- New Training Centres, 4- Police Control Rooms and 1 CRB. Some of the

implementation locations are positioned in the same office / building hence, effectively reducing

the number of geographical location.

CCTNS Implementation Pilot Phase (Phase-I)

As per NCRB’s recommendation, we suggest that North & South zone police stations in

Puducherry region should be taken up as the Pilot Police stations for Data digitization and

CCTNS application software implementation. The benefits of this approach is that the learnings

of this pilot can be quickly adopted and any unforseen bottle necks can be overcome while

implementing in other areas.

Geographical Coverage

Offices No. of units Locations

Police Stations 14 All Police Stations of North & South Zones

SDPO 2 North & South

Districts 1 SSP (L&O)

Circles 6 3-North, 3-South

Office Numbers

Police Station (Non CIPA) 7

Police Station (CIPA) 41

Sub Divisions 6

SP offices 7

Circles 15

District (SSP-L&O, SSP-KKL) 2

SSP (C&I) 1

SHQ 1

Finger Print Bureau 1

Crime Records Bureau 1

Proposed Training Centres 1

Police Control Rooms 4

Total 87



SHQ 1 Puducherry HQ

Crime Records Bureau 1 Puducherry HQ

SSP office 1 SSP (C&I)

SP 4 SB, SIGMA, CID, PTS

Control Rooms 1 Puducherry HQ

Finger Print Bureau 1 Puducherry HQ

Total 32

SI is required to strictly adhere to the prescribed implementation and roll out plan. The broad

level implementation and roll out plan is shown below:

SI shall prepare a detailed roll-out plan for each of the Districts in the Phase and get the same

approved by the UT. SI is also responsible for conducting workshops for the key officers (State

Mission Team, District Mission Team, and District Core Team) of the Districts / State for

presenting the District-Wise roll-out plan and get the approval from the District Teams before

getting the final approval of the State Nodal Officer. The SI shall also provide the necessary

assistance for the key officers (State Mission Team, District Mission Team, and District Core

Team) of the Districts / State during the design and implementation of CCTNS in the State / UT.

One of the important factors that would determine the success of the CCTNS implementation in

the UT is the continuous availability of domain experts to the implementation team. SI shall put

together a team of domain experts with a minimum of 10 years of experience in the UT 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 Data Migration Plan

5. Change Management and Capacity Building

a) Overall Change Management Plan

b) Content for Change Management including Awareness and Communications

Program



c) Overall Capacity Building Plan and District-wise Training Schedule and

Curriculum Training Material

6. District-wise Roll-out / Implementation Plans

Please refer Annexure-6 for detailed plan of Phase wise implementation and roll out

7. SERVICE LEVELS

This section describes the service levels to be established for the Services offered by the SI to

UT. The SI shall monitor and maintain the stated service levels to provide quality service to UT.

The Service levels are provided in Annexure-15 of this RFP.

A List of SLAs that needs to be measured using the proposed monitoring tools is given below.

These SLAs must be represented using appropriate customizable reports to ensure overall

service delivery.



8. ANNEXURE

Annexure 1 – List of all Implementation locations

Offices No. of units

Police Stations 48

SDPO 6

Districts (SSP off) 2

Circles 15

SHQ 1

CRB 1

SSP office (C&I) 1

Training Centers 1

Finger Print Bureau 1

SP Offices 7

Control Rooms 4

Total 87

1. List of Police Stations:

S No. DISTRICTS/REGION POLICE STATIONS Address

Non CIPA Police Stations

1.

PUDUCHERRY

VAC MG road, Muthialpet, Puducherry

2. FOOD CELL Villianur Road, Reddiyarpalayam, Puducherry

3. EXCISE Thattanchavady Industrial Estate, Thattanchavady, Puducherry

4. KARAIKAL

EXCISE Bharathiyar Street, Karaikal –

5. FOOD CELL Bharathiyar Street, Karaikal

6. MAHE EXCISE Mahe

7. YANAM EXCISE Yanam

CIPA Police Stations

8.

PUDUCHERRY

GRAND BAZZAR J.N. Street, Puducherry

9. MUTHIALPET M.G. Road, Muthialpet, Puducherry

10. LAWSPET Main Road, Lawspet,Puducherry

11. KALAPET East Coast road, Kalapet, Puducherry

12. ORLEANPET Maraimalai Adigal Salai, Orleanpet, Puducherry-

13. ODIENSALAI Bussy Street, Puducherry

14. MUDALIARPET Cuddalore Main road, Mudaliarpet, Puducherry




15. REDDIYARPALAYAM Villupuram Main road, Reddiarpalayam, Puducherry

16. D’ NAGAR Kamaraj Salai, Gorimedu, Puducherry

17. METTUPALAYAM Vazhudavur Main Road, Mettupalayam, Puducherry.

18. VILLIANUR South Car Street, Villianur, Puducherry-

19. MANGALAM PS Uruvaiaru main road Mangalam, Villianur.

20. AWPS (Pondy) J.N. Street, Puducherry

21. AWPS (Villianur) South Car St., Villianur, Puducherry

22. TRAFFIC (Pondy) J.N. Street, Puducherry

23. TRAFFIC (Villianur) South Car St., Villianur, Puducherry

24. ARIYANKUPAM Cuddalore main road, Tollgate, Ariyankuppam, Puducherry

25. THAVALAKUPPAM Thavalakuppam, Puducherry

26. BAHOUR North Car St., Bahour, Puducherry

27. KIRUMAMPAKKAM Cuddalore Main road, Kirumampakkam, Puducherry

28. NETTAPAKKAM Main road, Nettapakkam, Puducherry.

29. THIRUBUVANAI Main Road, Thirubuvanai, Puducherry

30. THIRUKKANUR Thiruvannamalai Road, Thirukkanur, Puducherry

31. KATTERIKUPPAM Katterikuppam, Puducherry

32. SEDARAPET PS Mailam Main road,Sedarapet.

33. PCR CELL (Pondy) Iyyanar Koil Street, Orleanpet, Puducherry

34. CID (Pondy) No. 1, Rue Dumas, CID Complex Puducherry

35.

KARAIKAL

TOWN Bharathiyar Street, Karaikal

36. KOTTUCHERRY Karaikal Main road, Kottucherry, Karaikal

37. AWPS Duplex St., Karaikal

38. TRAFFIC Bharathiyar Street, Karaikal

39. PCR CELL Mari Amman Koil St., SSP Quadrangle, Karaikal

40. TR PATTINAM Nagore Main road,T.R. Pattinam, Karaikal

41. NERAVY Neravy Salai, Neravy,Karaikal

42. THIRUNALLAR North Car Street, Thirunallar, Karaikal

43. NEDUNGADU Kamaraj Salai, Nedungadu, Karaikal




44. COASTAL Beach Road, Fatima Nagar, Karaikal

45. MAHE

MAHE Tellecherry Road, Mahe

46. PALLORE Palloor, Mahe

47. YANAM

YANAM Yanam

48. PCR CELL Yanam

2. List of Districts, SDPOs, Circles & SP Offices

DISTRICTS/REGION SDPO CIRCLES SP Offices

PUDUCHERRY (DISTRICT SSP OFFICE)

NORTH

GRAND BAZAR SPECIAL BRANCH

SIGMA

LAWSPET VIGILANCE & ANTI-CORRUPTION CELL FOOD CELL

ORLEANPET PROTECTION OF CIVIL RIGHTS CELL

TRAFFIC

CRIME INVESTIGATION

BUREAU

SOUTH

MUDALIARPET

D’ NAGAR

VILLIANUR

RURAL

ARIYANKUPAM

BAHOUR

NETTAPAKKAM

THIRUKKANUR

KARAIKAL (DISTRICT SSP OFFICE)

KARAIKAL

TOWN KKL

TR PATTINAM

THIRUNALLAR

MAHE (REGION) MAHE MAHE

YANAM (REGION) YANAM YANAM

2 6 15 7



3. List of other offices

Districts/Region Offices Address

PUDUCHERRY

Police Head quarters (PHQ) NO.4, Dumas Street,

Puducherry

Crime Records Bureau Rue Dumas, CID Complex

Puducherry

SSP (Crime & Investigation) NO.4, Dumas Street,

Puducherry

Finger Print Bureau Rue Dumas, CID Complex

Puducherry

Police Control Room NO.4, Dumas Street,

Puducherry

Police Training School (Existing) Gorimedu, Puducherry

KARAIKAL

Police Control Room SSP (Karaikal) office

MAHE Police Control Room Mahe

Yanam Police Control Room Yanam



Annexure 2 – Implementation Location Maps Puducherry & Karaikal Districts



Mahe & Yanam Region



Annexure 3 – Locations Details for Network connectivity

Leased line required at following locations:

S No. Leased Line Locations Bandwidth requirement

1 IGP Office (SHQ) NO.4, Dumas Street, Puducherry

2 CID Complex, Puducherry

3 SSP (HQ), Puducherry

4 SSP (KKL) office, Mari Amman Koil St., SSP Quadrangle, Karaikal

5 SP (North) , Puducherry

Broadband Connectivity required at following locations:

S No. Broadband Locations Bandwidth requirement

1 SP Offices Mahe

2 Administrative block, Puducherry

3 Police Control Room, Mahe

4 Police Control Room, Yanam

Note: Bandwidth requirement will be determined after proper study from the BSNL in

consultation of Puducherry Police.



Annexure 4- Region wise Police Strength for Capacity Building

Following numbers of Police Personnel identified for Capacity Building under CCTNS

Project.

Designation/Post Puducherry Karaikal Yanam Mahe Total

IGP 1 1

DIGP 1 1

SSP 3 1 4

SP 17 1 1 19

Group A 25

Inspector 56 6 1 2 65

Sub Inspector 122 14 3 7 146

Assistant Sub Inspector 44 4 2 9 59

Group B 270

Head Constable 234 44 4 12 294

Police Constable 976 157 50 69 1252

Group C 1546

Total Police Strength 1841

Total Police strength rounded to 2000


Annexure 5 - Case Files for Data Digitization

TOTAL NUMBER OF FIRs REGISTERED FOR THE LAST TEN YEARS IN THE U.T. OF PUDUCHERRY BY STATION WISE

Sl. No.

Police Station 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 (UPTO FEB)

1 Grand Bazaar 346 435 535 518 480 535 636 657 550 351 61

2 Muthialpet 291 262 284 295 322 338 327 289 378 273 34

3 Lawspet 206 292 324 300 408 488 262 256 236 240 33

4 Kalapet 100 101 113 136 154 126 134 130 145 100 19

5 Orleanpet 320 297 276 390 451 400 513 563 583 514 101

6 Odiansalai 283 259 308 316 338 303 355 306 557 465 56

7 D'Nagar 360 265 285 298 284 325 421 434 412 435 52

8 Mettupalayam 133 114 125 195 222 214 236 231 213 211 29

9 Mudaliarpet 348 283 325 377 321 265 409 344 371 396 30

10 Reddiarpalayam 354 280 273 280 304 263 310 259 222 272 26

11 Villianur 532 479 578 692 454 424 437 415 441 521 71

12 Ariankuppam 203 228 256 360 279 241 284 271 267 231 51

13 Thavalakuppam 179 160 169 216 222 209 218 235 181 151 29

14 Bahour 233 203 206 264 237 216 220 241 184 188 36

15 Kirumampakkam 181 174 198 268 233 271 248 328 257 199 38

16 Nettapakkam 137 183 200 147 212 180 135 227 165 132 18

17 Thirubuvanai 181 197 200 232 227 213 190 181 140 138 19



18 Thirukkanur 145 141 298 202 240 214 203 184 187 130 21

19 Katterikuppam 111 108 200 189 173 189 178 178 151 124 12

20 Karaikal (Town) 395 289 360 412 368 435 414 417 347 388 81

21 Kottucherry 200 145 126 206 174 200 171 170 127 141 23

22 T.R.Pattinam 212 148 151 187 200 205 246 230 199 150 35

23 Neravy 117 133 124 171 132 151 148 133 171 151 21

24 Thirunallar 216 191 181 159 187 247 265 275 192 180 22

25 Nedungadu 145 118 114 125 130 120 145 133 121 129 12

26 Mahe 66 125 157 158 200 160 111 104 169 114 17

27 Palloor 105 120 150 126 226 151 103 100 195 95 13

28 Yanam 147 93 121 107 94 305 236 199 141 159 29

29 Traffic, Pdy 782 873 947 990 1059 999 1140 1117 934 703 79

30 Traffic,Villianur - - - - 371 304 321 271 312 283 50

31 Traffic, KKL 140 191 147 187 198 158 118 130 138 143 23

32 Food Cell, Pdy 11 19 32 19 27 18 29 50 56 30 8

33 Food Cell, KKL 3 3 5 5 5 4 5 3 14 8 -

34 PCR Cell, Pdy 8 15 18 17 9 5 19 21 24 26 3

35 PCR Cell, KKL 4 2 - 2 4 5 5 5 3 2 -

36 PCR Cell, Yanam 1 1 - 1 2 4 1 3 2 - -

37 CID 16 21 22 33 18 8 21 21 28 15 4

38 AWPS, Pdy 21 55 55 71 74 27 33 27 18 27 2

39 AWPS, Villianur - - - - 35 17 25 12 5 18 3

40 AWPS, Karaikal - - - - - 3 28 31 11 12 3

SUB-TOTAL 7232 7003 7863 8651 9074 8940 9300 9181 8847 7845 1164

TOTAL 85100



41 VAC

42 Excise

GRAND TOTAL 85100+400


Annexure 6- Implementation Plan & Roll out Plan

North & South zone police stations in Puducherry region will be taken up as the Pilot Police

stations for Data digitization and CCTNS application software implementation. The benefits of

this approach is that the learnings of this pilot can be quickly adopted and any unforseen bottle

necks can be overcome while implementing in other areas.

CCTNS application will be implemented in three Phases including,

Phase Activities Timelines (Month)

Date of Signing of Agreement with the successful bidder T

Phase I (North & South Region police stations and Some Higher office of Puducherry as Pilot implementation)

Installation and Commissioning of necessary hardware and networking infrastructure at the desired location. Site Preparation at the selected location

T+6

Application Modules and Functionalities

Customization of CAS (State) and roll out in pilot stations

Digitization of historical data of the last 10 years

Training imparted to the selected personnel of Group A, B & C (No of persons to be identified in consultation with UT at the time of training)

Phase II (police stations & Higher offices of Karaikal & Rural region of Puducherry will be covered)

Installation and Commissioning of necessary hardware and networking infrastructure at all locations in the Puducherry

T+9

Revision of the knowledge gained through training

Training imparted to the personnel of Group A, B & C (No of persons to be identified in consultation with UT at the time of training)

Phase III (remaining Police Stations & Higher offices of Mahe & Yanam will be covered)


T+12


Training imparted to the personnel of Group A, B & C (No of persons to be identified in consultation with UT at the time of training)

Go-Live of CCTNS Project in entire State

Post Implementation

Operations and Maintenance support

Go Live + 5 Warranty and AMC services



Support Services

Continuations of Helpdesk for Providing Support to all Locations

years

Regular supervision, monitoring and extending support to department for smooth functioning of project.

CCTNS Phase-I (6 Months)


During the first phase of the application, CCTNS would be rolled out in North & South Zone

police stations and Some Higher office of Puducherry as Pilot implementation. This phase would

include installation and commissioning of hardware, Network connectivity, and other

infrastructure and associated services (such as Handholding) in the Puducherry District

including SHQ, SDPO, Circles CRB, Training centers etc. The CCTNS application will be rolled out

in the following locations in Phase-I. The Pilot Implementation will be done in 6th Months

duration.


Police Stations 14 All Police Stations of North & South Zones

SDPO 2 North & South

Districts 1 SSP (L&O)

Circles 6 3-North, 3-South

Police Head Quarters 1 Puducherry HQ

CRB 1 Puducherry HQ

SSP office 1 SSP (C&I)

SP 4 SB, SIGMA, CID, PTS

Control Rooms 1 Puducherry HQ

Finger Print Bureau 1 Puducherry HQ

Total 32

Digitization of Historical Data: In addition to the functionality identified above, Phase-I would

also include the digitization of historical data (covering the last 10 years). The historical data to

be digitized would include crime (case/incident) data, criminals’ data, the data from the police

stations records rooms (form police registers) and administrative, employee and asset related

data.

Digitization of historical data would help the police department maximize benefits from features

such as Search and Reporting and is would significantly enhance outcomes in the areas of Crime

Investigation, Criminals Tracking, servicing the requests of citizens and other groups, etc.

During this activity the SI should also strategize and perform data migration from the CIPA

database to the CCTNS database. The digitization exercise would be carried out by the System

Integrator.



SN. Registers/Form Name Number of Records/Cases (Approximate)

1 Case Files (IIF 1 to 7) 85,500+10,000

Total 95,500

Application Functionalities

All the application modules and functionalities identified would be covered during the Phase I

of CCTNS implementation

Modules

Registration module

The details of the additional functionalities

of these modules are given in Annexure-4

Investigation module

Prosecution module

Basic and Advanced Search functionality

Search Module

Analysis & Intelligence Module & MIS

Module

Configuration Module

Citizen Portal Module

Crime Prevention Module

Collaboration Module

Component & Work flow Module

Module Master Requirement Module

General Requirement (Data Transfer)

Module

User Assistance Module

Security Module

UT Specific Module :

Visitor Information System Module

Human Resource Management System

(HRMS) Module

Logistics Management System Module

General Verification Module

Vehicle Tracking System Module



Capacity Building Initiatives

The no. of personnel in each group that would be trained on the four training themes during Phase-I are provided in the table below:

Sl No. Levels Training Program No. of trainees

1. Level-I Basic Computer Awareness 2500

2. Level-II 1. Database Management

1000 2. Role based training for CCTNS

application users

3. Awareness and sensitization of

benefits of IT System

3 Level-II 4. Network & System Administrator

Training

15

Outcome

Phase Activities Outcomes Challenges

CCTNS Phase-I

Installation and Commissioning of necessary hardware and networking infrastructure at the desired location. Site Preparation at the selected location

Provision of proper infrastructure for implementation of the CCTNS project in the selected districts

- Challenges in ensuring

connectivity

considering the

geographical locations

of the Police Stations

and other Police

Offices

- Resistance to change

- Incomplete or missing

historical data

- Required personnel

not available for

training

-

Customization of CAS

(State) and roll out in pilot

stations

Implementation of CCTNS

in pilot police stations

Digitization of historical

data of the last 10 years

The historical data can be

retrieved from the system

through the Search

feature

Training imparted to the

selected personnel of

Group A, B & C

Selected people would

have undergone the

training program

CCTNS Phase-II (3 Months)


During Phase-II of CCTNS, the police stations & Higher offices of Karaikal & Puducherry will be

covered for the installation and commissioning of hardware, connectivity and other

infrastructure and associated services. The Phase-II Implementation will be done in 3 Months

duration.




Police Stations 30 All police Stations of Rural (Puducherry), Karaikal, PCR Cell, CID & traffic, VAC, Food Cells, Excise

SDPO 3 Rural (Puducherry), Karaikal & Traffic

District 1 SSP Karaikal

Circles 7 4-Rural (Puducherry), 3-Karaikal

SP 3 VAC, FOOD Cell & PCR Cell

Control Rooms 1 Karaikal HQ

Total 45


The no. of personnel in each group that would be trained on the four training themes during

Phase II is provided in the table below.

Outcomes


CCTNS Phase-II


Provision of proper infrastructure for implementation of the CCTNS project

- Delay in Installation,

commissioning of

hardware and

networking

equipments

- Availability of

bandwidth in terms of

connectivity



not available for

training


Refresher Training for the selected personnel

Training imparted to the personnel of Group A, B & C

Selected personnel would have undergone the training program

Training Program Group A Group B Group C

Awareness and sensitization of benefits of IT 0 0 0

Basic Computer Awareness (Level-I) 0 100 550

Role based training for application users (Level-

II)

0 100 550

Trainers training 0 15 10

Network Administration Support &

Troubleshooting

0 0 30



The above recommended implementation model would streamline implementation of CCTNS project in the Union Territory and reduce the effort and time for implementation.

CCTNS Phase-III (3 Months)


During Phase-II of CCTNS, the remaining Police Stations & Higher offices of Mahe & Yanam will

be covered for the installation and commissioning of hardware, connectivity and other

infrastructure and associated services. The rationale for selection of Mahe & Yanam for

implementation under Phase-III is that both these locations are wide apart from Puducherry

District and have connectivity issue. The Phase-III Implementation will be done in 3 Months

duration.

offices No. of units

Locations

Police Stations 4 Mahe & Yanam

SDPO 1 Mahe

Circles 2 Mahe & Yanam

Control Rooms 1 Mahe

Control Rooms 1 Yanam

Total 8


The no. of personnel in each group that would be trained on the four training themes during

Phase II is provided in the table below:

Training Program Group A Group B Group C

Awareness and sensitization of benefits of IT 0 0 0

Basic Computer Awareness (Level-I) 0 0 578

Role based training for application users (Level-

II) 0 0 578

Trainers training 0 0 0

Network Administration Support &

Troubleshooting 0 0 37



Outcomes


CCTNS Phase-III


Provision of proper infrastructure for implementation of the CCTNS project

- Delay in Installation,

commissioning of

hardware and

networking

equipments

- Availability of

bandwidth in terms of

connectivity



not available for

training


Refresher Training for the selected personnel

Training imparted to the personnel of Group A, B & C

Selected personnel would have undergone the training program

The above recommended implementation model would streamline implementation of

CCTNS project in the Union Territory and reduce the effort and time for implementation.



Annexure 7- Government Structure for Implementation Monitoring

This section will provide the governance structure that will be created at the UT of Puducherry

level to monitor the implementation of the CCTNS project.

As per the Guidelines issued by the Ministry of Home Affairs, Government of India, UT of

Puducherry Police Department shall constitute appropriate governance and operations

structures, and in alignment with the structures recommended by DIT, GOI under NeGP

guidelines. The following governance committees shall form the institutional framework for

implementation, monitoring and evaluation of CCTNS project.

1. State Empowered Committee

2. District Mission Team

State Empowered Committee

The CCTNS project in Puducherry has a Steering Committee headed by the Chief Secretary. The

Committee is the absolute decision making body in implementation, policy matters, vendor

evaluation and selection and project review. The Committee also plays a major role in drawing

out the I.T. requirement of Puducherry Police and evaluating funding opportunities for the

same. The composition is as follows:

Sl No Designation Role

1 Chief Secretary Chairperson

2 Principal Secretary / Secretary (Finance) Member

3 Inspector General of Police Convener

4 Representative of NIC, Puducherry Member

5 Director/ Deputy Secretary (SR), MHA Member

6 Any other members to be co-opted as necessary Member

This Committee will be responsible for following:

Allocation of funds

Approval of BPR (Business Process Reengineering) proposals.

Sanction for various project components, as may be specified, including the

Hardware/Software procurement.

Approval of various functionalities to be covered in the Project.

Review progress of the Project.

Ensure proper Training arrangements

Ensure deployment of appropriate handholding personnel.

Other important policy and procedural issues.

Guidance to UT of Puducherry District Mission Teams.



District Mission Team

For taking up CCTNS rollout in entire union territory it would require a full time dedicated

Project implementation Team at the UT. This team would oversee project execution and would

manage implementation and deal with technology, process & change management related

issues. This team would typically consist of core people at the UT level and have a well balanced

mix of domain expertise about the department processes & functions and technical expertise

(i.e. technology, process re-engineering, change management, project management).

In case of the Puducherry the State Mission Team and District Mission Team has been rolled into

one. Its composition follows.


1 Inspector General of Police Chairperson

2 Senior Superintendent of Police(L&O) Convener

3 Senior Superintendent of Police(Karaikal) Member

4 Senior Superintendent of Police( Crime and Intelligence) Member

5 Senior Superintendent of Police( HQ) Member

6 Representative of NIC, Puducherry Member

7 Representative of NCRB, New Delhi Member

8 Director, CRB. Puducherry Member

9 Superintendent of Police(HQ) Member

10 Superintendent of Police(PTS) Member

11 Superintendent of Police (North) Member

12 Superintendent of Police (South) Member

13 Superintendent of Police (Rural) Member

The District Mission Team will be responsible for following:

Operational responsibility for the Project.

Formulating Project Proposals.

Getting sanction of GOI for various projects.

Hardware rollout and commissioning

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 Union Territory Apex and Empowered Committees

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.

Appointment and proper utilization of handholding personnel.

UT Core Team (Operational Team)


1 Deputy IGP Chairperson

2 Senior Superintendent of Police(C&I) Member

3 Senior Superintendent of Police(L&O)/ Senior

Superintendent of Police(Karaikal)

Convener

4 Director (CRB) Member

5 Superintendent of Police (HQ) Member

6 Superintendent of Police (PTS) Member

7 Superintendent of Police (North) Member

8 Superintendent of Police (South) Member

9 Superintendent of Police (Rural) Member

10 Superintendent of Police (PCR Cell) Member

11 Superintendent of Police (Food Cell) Member

12 Superintendent of Police (VAC) Member

13 Superintendent of Police (Traffic) Member


To Provide Operational support to the State Mission Team

To liaise with the District Core Team to provide implementation support and collate

regular feedback from the end users

Shall carry out the monitoring and evaluation of the scheme at regular intervals to asses

the uptake of the solution and provide recommendation to the State Mission Team and

the System integrator for continuous improvement of the implemented solution and

services

District Core Team (Puducherry, Mahe and Yanam)


1 Senior Superintendent of Police(L&O) Chairperson

2 Superintendent of Police(North) Convener

3 Circle Inspector Member

4 Sub Inspector Member



5 Head Constable Member

6 Police Constable Member

7 Superintendent of Police (Mahe) Member

8 Superintendent of Police (Traffic) Member

9 Superintendent of Police (Karaikal) Member


To Provide the end user support at the cutting edge in the Police Stations

To provide operational support of the District Mission team

Shall carry out the monitoring and evaluation of the scheme at regular intervals to asses

the uptake of the solution and provide recommendation to the State Mission Team and

the System integrator for continuous improvement of the implemented solution and

services

UT of Puducherry Training Team

In order to ensure the effectiveness of computer training program under the CCTNS project, the

following team has been formed specifically to monitor the training program on a regular basis.


1 Senior Superintendent of Police(L&O) Nodal Officer, CCTNS

2 Senior Superintendent of Police(Karaikal) Member

3 Superintendent of Police(CRB) Member

4 Superintendent of Police(PTS) Member

5 Inspector (CRB) Member

6 Inspector - Web officer Member

7 Head Constable Member



Annexure 8 - Post Implementation Support Services

As part of the post implementation services, the SI shall provide support for the software,

hardware, and other infrastructure provided as part of this RFP. SI shall provide Five (5) years

of comprehensive AMC that includes:

Warranty support

Annual Technical Support (ATS)

Handholding Services

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) Support for the end users at each of the locations including deployment of one

competent person at each police station for a period of six months to handhold

the staff after the Core application and the necessary infrastructure are

successfully commissioned in the police stations.

c) Central Helpdesk from the UT designated premises.

d) Software maintenance and support services.

e) Application functional support services

The services shall be rendered onsite from the UT designated premises. To provide the support for the police stations, circle offices, sub-divisional offices, district headquarters, ranges, zones, UT police headquarters and other locations across the UT where the software, hardware, and other infrastructure will be rolled out, SI is expected to provide experienced and skilled personnel at each location. The SI will also ensure that there is a Service Center available or setup at each district or a group of districts of the State, as per mutual understanding between State and the SI.

As part of the warranty services SI shall provide:

1. SI shall provide a comprehensive warranty and on-site free service warranty for 5 years

from the date of Go Live.

2. SI shall obtain the five year product warranty and five year onsite free service warranty

on all licensed software, computer hardware and peripherals, networking equipments

and other equipment.

3. SI shall provide the comprehensive manufacturer's warranty in respect of proper

design, quality and workmanship of all hardware, equipment, accessories etc. covered

by the RFP. SI must warrant all hardware, equipment, accessories, spare parts, software

etc. procured and implemented as per this RFP against any manufacturing defects

during the warranty period.

4. SI shall provide the performance warranty in respect of performance of the installed

hardware and software to meet the performance requirements and service levels in the

RFP.

5. SI is responsible for sizing and procuring the necessary hardware and software licenses

as per the performance requirements provided in the RFP. During the warranty period

SI shall replace or augment or procure higher-level new equipment or additional



licenses at no additional cost to the UT 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 UT. 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 UT. 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, UT 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 UT, all defective components that are brought to the SI's

notice.

8. The SI shall as far as possible repair the equipment at site.

9. In case any hard disk drive of any server, SAN, or client machine is replaced during

warranty / AMC the unserviceable HDD will be property of Puducherry Police and may

be returned to SI on only after wiping it clean at the physical level with a pre-decided

hex value. In case wiping is not possible, HDD shall not be returned to Sis.

10. Warranty should not become void, if UT 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 UT as and when released by OEM.

5. SI shall provide patches to the licensed software including the software, operating

system, databases and other applications.

6. Software License Management. The SI shall provide for software license management

and control. SI shall maintain data regarding entitlement for software upgrades,

enhancements, refreshes, replacements, and maintenance.

7. SI shall provide complete manufacturer’s technical support for all the licensed software

problems and/or questions, technical guidance, defect and non-defect related issues. SI

shall provide a single-point-of-contact for software support and provide licensed

software support including but not limited to problem tracking, problem source

identification, problem impact (severity) determination, bypass and recovery support,

problem resolution, and management reporting.

8. The manufacturer’s technical support shall at a minimum include online technical

support and telephone support during the UT’s business hours (Business hours in UT

will be from 0830 hours to 2030 hours on all days (Mon-Sun)) with access for UT 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. SI shall have access to the online support and tools provided by the

manufacturer. SI shall also have 24x7 accesses to a variety of technical resources

including the manufacturer’s knowledge base with complete collections of technical

articles.

As part of the Handholding services to provide Operations and maintenance support for the

server and related infrastructure supplied and commissioned by the SI for the application at the

Data 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 UT

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

UT on a monthly basis. Whenever required by UT, SI should be able to provide

additional reports in a pre-specified format. The indicative services as part of this

support are as below:

a) System Administration, Maintenance & Management Services

b) Application Monitoring Services

c) Network Management Services

d) Backend Services (Mail, messaging, etc)

e) Storage Administration and Management Services

f) IT Security Administration Services and Services for ISO 27001 and ISO 20000

compliance

g) Backup and Restore Services



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

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. UT requires the SI to provide Help Desk services to

track and route requests for service and to assist end users in answering questions and

resolving problems related to the software application, network, Data Center, Disaster

Recovery Center, Client side infrastructure, and operating systems at all locations. It

becomes the central collection point for contact and control of the problem, change, and

service management processes. This includes both incident management and service

request management.

3. SI shall provide a second level of support for application and technical support at police

stations, circle offices, sub-divisional offices, district headquarters, range offices, zonal

offices, UT police headquarters and other locations across the UT where the software,

hardware, and other infrastructure will be rolled out.

4. For all the services of UT 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 UT 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 UT about the same.

3. Tuning of application, databases, third party software’s and any other components

provided as part of the solution to optimize the performance.

4. The SI shall apply regular patches to the licensed software including the operating

system and databases as released by the OEMs.

5. Software Distribution. SI shall formulate a distribution plan prior to rollout and

distribute/install the configured and tested software as per the plan.



6. Software License Management. The SI shall provide for software license management

and control. SI shall maintain data regarding entitlement for software upgrades,

enhancements, refreshes, replacements, and maintenance. SI should perform periodic

audits to measure license compliance against the number of valid End User software

licenses consistent with the terms and conditions of site license agreements, volume

purchase agreements, and other mutually agreed upon licensed software terms and

conditions and report to UT 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:

2. 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 UT from the development center in UT.

3. Enhancements and defect fixes. SI shall incorporate technological changes, and provide

enhancements as per the requests made by UT. SI shall perform minor changes, bug

fixes, error resolutions and minor enhancements that are incidental to proper and

complete working of the application.

4. Routine functional changes that include user and access management, creating new

report formats, and configuration of reports.

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

6. The SI shall migrate all current functionality to the new / enhanced version at no

additional cost to UT and any future upgrades, modifications or enhancements.

7. The SI shall perform user ID and group management services.

8. The SI shall maintain access controls to protect and limit access to the authorized end

users of the UT.

9. The services shall include administrative support for user registration, creating and maintaining user profiles, granting user access and authorization, providing ongoing user password support, announcing and providing networking services for users and providing administrative support for print, file, directory and e-mail servers.

Exit Management and Transition – Capacity Building at UT

After the exit of the SI, UT shall take up the management of CAS (State/UT). Therefore before the exit of the SDA, UT must be strengthened and capacity must be developed for UT to manage CAS. The SI must plan the capacity building initiative to enable UT manage CAS, and will collaborate with UT to implement the plan. The SI shall create a detailed plan for Capacity Building (CB) required at UT to manage CAS and a Transition Plan (implemented over a minimum period of three months) to affect the handover to UT; and implement the same in collaboration with UT before the completion of their engagement.



Annexure 9- Functional Requirement Specifications

Registration Module

S. No Functionality Compliance

(Yes/No/Partial)

1 System should provide a facility to Operator to log the information details. The information could be of different nature (Cognizable, Non-Cognizable Offense, Missing Persons, Unnatural / Suspect / Custody death, Unidentified Dead Body, Lost Property, Unclaimed/ Abandoned /Suspected / Stolen Property, Security proceedings against the defaulters / habitual offenders, Preventive arrests using this module.)

2 Should allow uploading of any relevant documents such as Scanned documents of the complaint/images.

3 Should present different templates/forms for different kinds of complaints. For example, the system should provide different forms for (Cognizable, Non-Cognizable Offense, Missing Persons, Unnatural / Suspect / Custody death, Unidentified Dead Body, Lost Property, Unclaimed/ Abandoned /Suspected / Stolen Property, Security proceedings against the defaulters / habitual offenders, Preventive arrests)

4 System should support the facility of Digital Signatures for the registration of Complaint/ Petition. Note: It should not be a mandatory mechanism for Complaint/ Petition registration

5 Should allow the Operator to assign the investigation/enquiry to an Investigating Officer (IO) in case of FIR and Inquiry Officer in case of report of (Cognizable, Non-Cognizable Offense, Missing Persons, Unnatural / Suspect / Custody death, Unidentified Dead Body, Lost Property, Unclaimed/ Abandoned /Suspected / Stolen Property, Security proceedings against the defaulters / habitual offenders, Preventive arrests)etc (to be designated by the SHO)

6 Should allow the Operator to record notes/remarks on the complaint/Information.

7 Should assist the Operator by providing “Data Validation Controls” during the registration process.

8 Should allow the Operator to search the existing repository of previous FIRs/complaints/Information before deciding the course of action on same subject.

9 Should allow for approval (formal/ informal) by the SHO/ Senior Most Officer in PS before issuing the FIR and any other report stated above.

10 Should provide facility to the Investigating Officer to create the FIR or any other report stated above or a report for juvenile case at the crime scene through a Handheld device.



11 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)

12 Should allow the Operator to transfer an FIR or any other report stated above falling in other Police Station jurisdiction

13 System should facilitate closing of a case which is not taken up for investigation (u/s 157 CrPC).

14 System to also have closure reports for other registration reports (Cognizable, Non-Cognizable Offense, Missing Persons, Unnatural / Suspect / Custody death, Unidentified Dead Body, Lost Property, Unclaimed/ Abandoned /Suspected / Stolen Property, Security proceedings against the defaulters / habitual offenders, Preventive arrests etc.) which the approval of SP/DSP of that area.

15 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

16 System should allow the user to view the antecedents of a person belonging to other state

17 System should forward a request for verification of a stranger (in case the permanent and present addresses are different) to the relevant police station (be it in a different state). System should allow the user to update progress on a call for service from time to time. System should generate a report of all pending calls for service alleging cognizable offences for >24 hours and all other calls for service pending for more than certain number of days (to be decided by the supervisory officer in each unit/district) to facilitate scrutiny by supervisory ranks.

18 Should allow the user to view timeline within which to resolve the issue (process step)

19 System should allow the user to link / de-link complaints.

20 System should allow the user to merge complaints in case of duplicate complaint or cross case

21 Should present the station writer a dashboard with the report summary table consists of new cases, court disposal, cases pending arrest etc

22 Should have a list of Special Report Cases.

23 Should provide the reports and search capabilities on the complaints registered.

24 System should also allow the user to view crime and criminal data (as per the state specified formats), subject to the access being role based.

25 System should display the name of the police station / higher office where the compliant was originally registered

26 System should not allow the user to edit the FIR once registered/frozen.



27 System should allow the user to link Unidentified Dead Bodies with Missing Persons

28 System should provide for automatic dispatch of notifications to Airports & Seaports (ports of entry and exit) on criminal Movements

29 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)

30 System should allow the user to send copies of the FIR to a distribution list through EMAIL

31 System should allow the user to create and forward special reports to IGP, DIGP, SSP (L&O) (in cases of heinous crime)

32 System should allow the user to link FIRs with MLCs / Missing Persons / Unnatural Deaths (since they can be converted into FIRs)

33 System should provide for the following statuses for FIR 1. Pending Investigation 2. Charge sheet Submitted to Court with date 3. Untraced report submitted to supervisory ranks (SP) with date 4. Untraced report submitted to Court (with date) 5. Cancellation report submitted to supervisory ranks (SP) with date 6. Cancellation report submitted to Court (with date)

34 System should allow the user to capture the 'Alias' of complainant, accused, witnesses etc. in the FIR

35 System should allow the user to capture Finger Print and Retina Scan for accused in FIR

36 System should generate an email to National Human Rights Commission within 24 hrs in case there is a custodial death and police encounter deaths

37 System should allow the user to have information on major events, namely, Hartals, All types of Agitations, fairs, religious gatherings, elections, rally, etc.

38 System should allow the user to register cases of wild life crime, and send the report to Wild Life Bureau

39 System should allow for auto transfer of cases registered as a crime against SC / ST or POC Act to SP for investigation

40 System should allow the user to capture identity details of the Unknown Dead / Injured Person (when traced).

41 Should allow the user to see the list of police stations with jurisdictional areas to file complaint in appropriate PS and also to locate the area PS particulars based on address or prominent landmark nearby.

42 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

43 System to have provision 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

44 Cognizable, Non-Cognizable Offense, Missing Persons, Unnatural / Suspect / Custody death, Unidentified Dead Body, Lost Property, Unclaimed/ Abandoned /Suspected / Stolen Property, Security proceedings against the defaulters / habitual offenders, Preventive arrests registration shall be done just like the FIR. The format of a new IIF will be decided in consultation with that Puducherry Police.

Investigation Module


(Yes/No/Partial)

1 In case of NCR (Non Cognizable Report), the system should allow user to capture the relevant complaint details in the General Diary and take a printout for the complainant or the IO to approach the court for permission to investigate.

2 Should allow uploading of any relevant documents such as scanned documents/images linked to the case under investigation/ inquiry

3 System should allow the user to record and transfer a case that does not fall under jurisdiction of the present police station after proper registration

4 Should present customized templates/integrated investigation forms for the type of crime under investigation

5 Should allow user to search the lost/stolen property in different cases or different police station within the repository

6 In case a match is found the system should link the unclaimed/abandoned property with the case

7 The system should generate a list of an unclaimed/abandoned property which isn’t claimed within the period allowed, to initiate the process of auction & record the auction details after requisite approvals/auction

8 System should generate an alert for the concerned IO if the property seized is already involved in a crime

9 System should have the facility to change the case status depending on the progress of the investigation. By default after registration of FIR, status should be under investigation - Under Investigation (default) - Status could be based on nature of Police Report (Under Trial/ Closure) - Court Acceptance on the basis of 173 reports/ other than case of Charge Sheet -Status Should be editable



10 System should allow the SHO/IOEO or any other senior officer as per section 36 CrPC to record remarks on the status/case progress and issue guidelines/pointers. (SP should be able to updates through Initial Special Report and Continuous Special Report by accessing the Case Basket (containing CDs, 161 statements, audio video recording, scene of crime photographs, PMR, MLR, Inquest Reports, Crime Scene Map, Memos, etc.)

11 System should assist the user in the generation of Initial Special Report (ISR)

12 System to have functionality to upload the ISR

13 System should support the facility of Digital Signatures for signing CDs, statements etc by the IO/ SHO/ SO. Note: It should not be a mandatory mechanism for FIR Registration

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

15 System should be able to add/ modify status of accused during Investigation/ Prosecution - In Police Custody - In Judicial Custody - On Bail - Bail Jumper - Proclaimed Offender

16 Should allow the user to capture the details of the investigation/enquiry relevant to the type of the case.

17 Multiple Charge sheets should be able to be submitted in a single FIR. In a single case supplementary charge sheet may also be prepared and submitted (even during trial)

18 Indicative details captured during investigation of criminal cases in IIF forms or otherwise are given below. i. Crime scene details ii. Victims Details with as many personal identification numbers iii. Accused Details iv. Witness Details v. Property Details (stolen/seized) vi. Evidence details (Oral, Documentary, Physical, Audio video, ) vii. Forensic details viii. Medico Legal Details ix. Other details as per the crime details form

19 System should allow preview and printing of all the required forms (7IIF’s, forms required for preparing the case file and other forms necessary for submission to the external entities such as courts).



20 In case of unnatural death, system should allow the user to capture data relating to inquest (nature of injuries, details of clothing etc.) and generate an inquest report.

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

22 System should allow the user to enter data received from Forensic Science Labs on a case during investigation

23 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/dockets should be made available to the user as templates that are managed (created/edited) through administration functionality.

24 System should provide the feature to capture the response in the form of parameterized data and scanned documents received from different external agencies.

25 System should allow the user to prepare, preview and print arrest card and seizure/recovery/receipt memo/ user defined templates.

26 System should allow user to capture the arrest/ court surrender details

27 Should allow the user to capture the interrogation details as summary and parameterized data.

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

29 System should allow the user to enter/ capture the unique identification details of the convicts like IRIS, Fingerprints and Facial patterns.

30 System should allow the user to view the detailed and summary views of the case

31 System should allow supervisory Officers to provide their instruction/remarks on initial special report (ISR) in Special Report cases.

32 System should allow the user to record details of the property released during investigation

33 System should allow the user to prepare the final police report u/s173 CrPC (charge sheet, closure, untraced, cancellation, civil nature)

34 System should not allow the Computer Operator/ Investigating Officer to get the system generated copy of the Charge Sheet until he has filled the other IIF forms (No. 2, 3 and 4)

35 System should be able to generate the information on the criminal (his previous convictions) at the time of generation of Charge sheet.

36 Systems should assist the IO in filling the forms by incorporating various Data Control Points within the online forms



37 System should prompt the user with the list of documents required for filing a charge sheet.

38 System should allow the case to be reopened and reassigned to a different investigating officer. In case of reopening, the case history should be maintained.

39 System should keep record of the remarks/suggestions by higher officers during investigation.

40 System should present the IO dashboard of under trials, under investigation, re-opened cases, Put to court cases to users based on their roles and their jurisdiction.

41 System should provide the dashboards to higher officials about the case progress and metrics about U/I cases etc.,

42 System should allow the SP & Senior Officers to view the summary of Cases based type of case and cases falling in their jurisdiction also have an access to the Case Basket

43 System should present the SHO & Senior officials about the details of the cases based on the status like open, closed, reopen, disposed, unresolved and case pending for trial.

44 The system should have the provision to capture the details of History Sheets dangerous/ habitual offenders.

45 System should be able to create a 360 degree profile of all such criminals using dossier data through the data entry. The reports would get generated in the module “Periodic Crime and Law & Order Reports and Review Dashboard Service”

46 System should have an interface with Age Progression Technology software for getting updated pictures of missing persons/ fugitives/ POs,

47 System to provide facility to IO to be able to uploaded information such as any person of interest/ any vehicle of interest/ mobile phone (IMEA) of interest/ any other property of interest. Details of the concerned IOs investigation and what action is required to be taken.

48 Should support business intelligence tools for crime mapping and analysis in order to generate clues to assist in investigation.

49 Should provide the reports and search capabilities on the case progress

50 Should support Real-time exact and relaxed matches of fingerprints from the master database using live scan fingerprints or the latest prints collected from the scene of crime.

51 Should support identification of criminals by the latent prints collected from crime scenes and facility

52 Should prompt identification of persons detained in the course of investigatory actions by police, including identification of absconders at the Police Station of from the mobile PCR Vans.

53 Should support identification of incapable persons unable to provide information about themselves due to a mental illness, accidents etc.

54 Should support identification of unidentified deceased persons, including victims of accidents and natural disasters



55 System should be able to record the following details of the person, as proposed by the Planning Commission, Government of India : - Finger Prints - IRIS - Facial Maps (Facial Recognition System)

56 System should allow the user to update the status of case property as 1. Deposited in PS 2. Released 3. Transferred to another case/PS 4. Sent to Forensic Lab / Forensic Medicine Department/any other agency 5. Sent to Court (as evidence)

57 System should allow the user to capture victim information as under 1. Particulars of victims deceased/ seriously hurt/hurt/unhurt, namely:- i. Gender ii. Age iii. SC / ST/OBC iv. Economic Strata v. Educational Qualification vi. Nationality vii. Religion

viii. Identity marks ix. Address x. Contact Details (Telephone / Mobile / Email) xi. Whether eligible for compensation.

58 System should provide the user with 1. Crime and criminal information 2. Address tracking of mobile users 3. Access to Knowledge Base through his / her mobile phone

59 System should allow the user to record and print witness statements

60 System should provide for 'Change of IO' 1. In most of the cases IO can be changed

61 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 another case with similar accused description

62 System should allow the user to take out print outs of witness statements at the time of charge sheet

63 System should prompt the police user with the list of documents and list if witnesses required for filing a charge sheet.

64 Finger print should also be allowed to upload through an electronic reader and a photograph through a web cam



65 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 characteristics should be displayed (based on NCRB code)

66 –System should allow the user to capture details of Proclaimed offender, - Attachment/auction of his assets under Section 83/84 CrPC

Prosecution Module


(Yes/No/Partial)

1 System should allow the user to capture the charge sheet acknowledgement details received from the court after the submission of the Charge Sheet.

2 System should have facility create a list of critical cases to be monitored very closely and also to put a particular case on the list of monitored cases. There would be two/ three different types of the screens of these types of cases

3 System should allow the user to capture the summons/warrants issued by court, next date of hearing, status of accused (whether on bail or in custody with name of jail, PO, bail jumper etc). System should provide for preparation of calendar (daily, weekly, fortnightly) for cases scheduled for hearing

4 System should allow the user to assign the summons/warrants to police personnel. In case of police personnel, System should serve the summon on him directly with a copy to his Unit in charge through SWAN; in case of non police government servants, copy of the summon may go to the nearest police station for service

5 System should allow the user to record the status of service/execution on the summons/warrants respectively.

6 In case if accused applied for bail, system should allow the user to record the bail details including particulars of sureties, identifiers and raise alerts in case of stock surety/identifier

7 System should allow the user to capture the Trial update / Court disposal form

8 System should provide for monitoring of progress of selected cases figuring on the “List of Monitored Cases” through a court diary to be filled in the prescribed format by the Public Prosecutor/ Court

9 Indicative details captured during trial day of the Monitored cases are given below i. Stage of Trials ii. Court Disposal Details iii. Next hearing date iv. Witnesses who deposed - Fully Supported



- Partially Supported - Hostile v. Any change in Accused Status (got bail, in custody, where, declared PO, jumped bail etc) vi. Any special requirement for the next date, any additional accused summon, etc. vii. Interim Court Orders, General Remarks, etc.

10 System should allow the user to capture details if the convicted accused appeals in the higher court - IIF 7 Status (granted retrial, appeal denied) of the appeal.

11 System should allow the user to capture jail / remand related information (release from jail, sent on judicial remand, sent to police custody).

12 System should allow the user to manage and handle the split cases.

13 System should allow the user to proceed for further investigation if ordered by the court.

14 The solution should provide the IO to view the tasks that he/she had set in calendar, the court appointments, and Administrative related tasks.

15 The system should allow capturing the movement of the prisoner / under trial / convict movements into and out of jails.

16 System should present Court (court constable) dashboard including court hearing schedule, summary of charge sheets, case disposed by court, summons and warrants/ other processes issued and status of service/ execution

17 System should allow to send alerts to local police station in case of discharge of under-trial/convict who are accused in cases figuring on the list of monitored cases or who are listed as dangerous prisoners from Jail on furlough/parole etc

18 System should maintain a list of dangerous prisoners. User should be able to update it periodically. The list would specifically assist the Police Escorts in charge to obtain: (a) Court permission for handcuffing Note: This list would also help decide Parole applications

19 System should allow the user to capture challan checking memo (remarks of the Public Prosecutor before the finalization of the Charge Sheet)

20 System should allow the user to generate report on disposal of cases in the prescribed format (state wise)

21 System should allow the user to capture details of wanted accused and match the same with any other person of interest already existing in the system (complainants/witnesses/accused/arrested/missing persons/unidentified dead bodies/unnatural deaths etc.)

22 System should allow for generation of report on unexecuted warrants

23 System should allow the user to capture report of summon service and warrant execution



24 The movement of each UTP from and into the jail be properly accounted for

25 System should provide for - Joint Trial in court disposal form and in trial form

26 System should provide facility to split case into more than one court cases and allot fresh CC no.

27 System should provide for Tracking of Appeal outcome

Search Module


(Yes/No/Partial)

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

2 Should provide the user a quick search for given case ID

3 System should support search by speech samples/ picture gallery

4 System should have an interface with AFIS

5 Search to have the Soundex support for finding the relaxed and exact matches

6 System should also provide an advanced search capability and allow user to filter the search to a greater detail like crime details, suspect details, victim details, modus operandi and property using drill down functionality

7 System to provide the option with “Do you mean this ?” with relaxed matches of searched category/ parameter

8 The system should allow the user to configure / build a query on the searchable data through query builders and make any possible search in the databases.

9 System should provide the ability to store, load and delete custom queries to each user for easy retrieval

10 System should allow the user to organize the search results sort by clicking on table header

11 System should organize the search results in paged manner. It should also provide user the flexibility to navigate to the required page

12 System should provide standard formats for the data from external sources (Vehicle Registration Numbers) and a utility to capture the data into the investigation toolkit-data repository



13 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

14 System should maintain the history of data in case of modifications (ex, vehicle transferred to a new owner)

15 System should provide the user with an ability to search (full and partial strings) the knowledge repository. This search interface should be made available both as a separate interface and as well as an integrated interface, integrated with the crime and criminal search interface.

16 In case the searched entity has a history of ownership, the same should be presented in the search results

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

18 System should provide the user with search hints / tips on data fields such as 1. Names 2. Locations 3. Objects

19 System to have a search optimizing engine to provide with the results that exactly matches the searched parameter

20 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)

21 System should allow the user to conduct an advanced search based on sub parameters on a major data field

22 System should provide for similar features to a Soundex function for searches on 1. Names 2. Places 3. Objects

23 System should allow the user to enter age of a new born child in 'Days'

24 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 located in the directory of locations.

25 The linkages should be provided in the system with the transport department

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

27 The system should assist the IO and higher officers with court’s judgments to guide them in investigation



28 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

Configuration Module


(Yes/No/Partial)

1 The solution should provide the user to customize the application without affecting the core.

2 System should allow the user to change the look and feel like font, skins, images of the application

3 System should provide the flexibility in creating/modifying and deleting the user Hierarchy and should allow the admin to assign roles as proposed by Districts, Regions and police stations.

4 System should allow the user to define the organization, all its units (police stations, districts, regions) and user hierarchy

5 Decision on Major & Minor head of a crime should be based on the business rules defined in the system to judge the type of head to be selected against the incident reported

6 System should generate reports based on roles defined/ System to also generate the Dashboard based on the Roles defined

7 System should be able to customize and lock contents of the dashboard based on the roles defined and its usage

8 User should also be able to monitor the performance of units/officers relating to data entry (between any two cutoff dates)

9 System should allow the user to add/modify/delete/modify-order of acts, sections and local laws

Citizen Portal Module


(Yes/No/Partial)

1 Should allow user citizens to access Citizens’ Services portal via the internet

2 Should provide users (citizens) with an interface to connect to “Call for Service” Module for making police service requests in the following areas: 1. General Service Petitions 2. Passport verification requests 3. Tenant Verification



4. Servant Verification 5. Permission Request for Processions and Rallies 6. NOC (No Objection Certificates) 7. NOC for purchase second hand vehicle, 8. Lost Cell Phone Certificate, Arms License, 9. Driving License etc. 10. Report incidents (including incident of Cognizable crimes, Non-Cognizable Crimes, Incident of Missing Persons, Unnatural deaths, Unidentified Dead Bodies, Lost Property, Unclaimed/ Abandoned Property etc.)

3 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

4 Should provide facility to the citizens to search (using relevant search parameters) and view the information regarding incidents– such as 1. Unidentified Dead Bodies 2. Most Wanted Criminals, 3. Missing Persons, 4. Stolen Vehicles (search by color/ brand/ model of vehicle, date of stolen), 5. Unclaimed/ Abandoned Property 6. Criminals/ sex offenders/ most wanted criminals (search by area wise, crime head wise or both)

5 1. System should allow the user to select their relevant (as per jurisdiction) police station from a list (in case the PS is known) 2. System should provide the user particulars of the PS based on the address, PIN code or prominent landmark near their location. 3. 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)

6 System should provide the facility to citizens to keep their identity anonymous at the time of reporting of incident or providing secret information regarding crime and criminals. For eg. System may mask the email id of the citizen reporting incident, whereas in cases where email is not been used for reporting of incident, system to provide an interface with a normal text box which can be used by citizens for reporting incident. This service would be titled as “cyber tips”

7 System should be able to record the IP address of user

8 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

9 Should allow automatic carbon copying of generated reports on services to stakeholders.



10 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"

11 Should have the facility to keep list of the Community Liaison group. Portal should provide the facility to citizens to know their liaison group, contact details of group members, information regarding group meetings, schedule and agenda of next meetings, various public announcements, pictures, etc.

12 Should display CFS/ FIR details on the screen, based on the user search through Call for Service ID. Basic Status: Case Registered/ Investigation Denied under 157 section, Under Investigation/ Under Inquiry/Police report sent to Court/Nature of Police Report, Copy of FIR/ Complaint Registered

13 Should provide citizens with a help sub module to educate them on the police services, police rules, safety tips, modus operandi and FAQs.

14 System should host a “Sex Offender Registry” to allow citizens to know about sex offenders in their locality/ village/ town

15 Should have space for publicity of commendable work done by citizens in assisting the police

16 Should provide up to date location/ contact information on area Police Station/ Other Police Offices on the basis of Landmark or address

17 Should have an interface with social networking sites like Face book and twitter to record traffic and crime information into the citizen interface/ portal module

18 Should provide for cataloguing of Calls for Service on the basis of police office, demographical traits of citizens like age, gender, ethnicity, rural/urban background, religion/caste etc.

19 Should allow Police Officers to access the portal via the Internet/ Intranet

20 Facility of Single Sign-on and allowing the Police Officers to log in to the departmental modules through Portal

21 Should allow the officers to choose the language preference for the use of portal, i.e. portal shall support both Hindi and English interface for police officers

22 Should provide role based access to the various modules and sub modules of the proposed CAS (State) and other additionally proposed modules to all the Police Officials

23 Should provide the Police Officials with the help module to assist them in using the Portal/ CAS (State) and other additionally proposed modules

24 Should provide the Police Officials with comprehensive Search capability to access any type of information which is desirable for e.g.) e-learning course material, area specific information, crime & criminal information, etc. Search would run on the knowledge base using business intelligence methods

Generic Requirements for Portal



25 Support the management of content from multiple repositories (Knowledge base), content should get sync/ RSS feed/ updated with the knowledge base with mobiles

26 Should have Content creation tools

27 Should have Content workflow management tools

28 Should have Workflow support for management of creation and publishing process with # Publishing stages # Complex business rule support # Balancing of tasks across a workgroup of users

29 Should support In-place editing of content

30 Ability to manage content metadata via portal

31 Mass import/export tools

32 Content versioning support

33 Access control tied to portal access control

34 Integration with personalization engine to provide personalized content

35 Integration with search engine

Infrastructure Support

36 Should support industry wide operating systems.

37 Should support industry wide web servers.

38 Should support industry wide web browsers.

39 Should support industry wide database management systems.

40 Should support industry wide directory servers.

41 Should provide a mechanism for balancing the user and/or request load across several logical and/or physical servers

42 Ability to scale vertically (take advantage of servers with multiple CPUs)

43 Ability to scale horizontally (spread load across several physical servers with fail-over support)

44 Provide a mechanism for fail-over of logical and physical servers



45 Provide role-based access control to portal resources, including support for automatic propagation and inheritance of privileges throughout the portal taxonomy

46 Provide SSL support for HTTPS (web-based front-end) & LDAP (directory server)

47 Provide front-end protocol switching support (e.g. HTTP to HTTPS)

48 Support distributed caching of static content, such as style sheets, images and scripts, that can be served by an architectural component other than the portal, such as the web server

49 Support security data caching, such as user attributes and group memberships

50 Provide a mechanism for balancing the user and/or request load across several logical and/or physical servers

51 Log of access from various IP addresses

52 Visitor Counters of the website and web-pages separate

Administration

53 Provide a web-based administration tool

54 Ability to manage users and group memberships

55 Ability to manage user/group access control to portal resources, such as pages and portlets

56 Portal platform’s administration tool must support the ability to create/update/delete portal resources, such as pages and portlets

57 Support the delegation of the administration of portions of the portal to users

58 Should have a Policy based Administration Model where # Policy should be part of the programming model # Admin interface should have provision for setting system wide “policy sets”

Personalization

59 Ability to provide personalized content based on sophisticated business rules (rules engine) and user profiles

60 Provide a recommendation engine that drives personalization by related users based on their profile and past behavior

61 Provide integration between the personalization engine and a content management platform

62 Provide integration between the personalization engine and the search engine

63 Log personalization engine events and results



64 Log recommendation engine events and results

65 Provision for Administrators can apply “Personalization rules” to both portlets and portal pages i.e. Use of Business logic to provide “dynamic” experience. Example: Show HR Benefits Page during enrollment period

66 Provision for Personalization rules dialog to be accessed in context

Search

67 Ability to search structured information repositories, such as Databases For example details of passport verification requests, NOC (No Objection Certificates), NOC for purchase second hand vehicle, Lost Cell Phone Certificate, Arms License, Driving License etc. , Complaints (including Non-Cognizable Criminal Incident, Missing Person, Un-natural death, Unidentified Dead Body, Lost Property, Unclaimed/ Abandoned Property etc.)

68 Ability to search unstructured information repositories, such as documents, images, audio and video

69 Support free text searches

70 Support structured searches driven by metadata

71 Perform federated searches across multiple indexes

72 Search engine must provide preemptive access control of search results; content the user cannot access does not appear in the search results

73 Support crawling of sites to build content indexes

74 Ability to start/stop crawling manually

75 Ability to schedule periodic crawling

76 Support filtered crawling

77 Support browsing of indexed content

78 Support integration of search results with the personalization engine

79 Support relevance-based sorting of search results

80 Ability to edit indexed content metadata

81 Provide out-of-the-box portlets for searching and browsing



82 Administrative must be able to customize pages and portlets with their own settings

83 Administrative must be able to customize the page layout

84 Administrator must be able to create new private-pages

85 User must be able to change the look-and-feel of the portal

86 Ability to have workgroup-level customization by a super-user

87 Ability to lock down one or more pages preventing customization

Police Email and Messaging Service


(Yes/No/Partial)

1 Should allow the user to create or import the organizational hierarchy and the users of the police department along with their Email ID to populate contact list/ address book

2 Should allow the user to select the user list from the organization hierarchy

3 Should allow the user to create personal address book, groups

4 Should allow the user to send messages to groups.

5 User should be able to create folders with rule based redirection of incoming emails (example yahoo mail)

6 System should provide a way through which the user is able to sort emails by clicking on any attribute header (example yahoo mail)

7 System should allow a facility through which all emails with common subject line is seen/ shown together in a common thread (example Gmail)

8 Should allow the user to create & select templates for message Standardization

9 Should allow the user to choose the option for read/ receipt Notification

10 System should allow configuring the automatic acknowledge and read receipt for a particular user or a category of users. For rest of users system should allow them to choose the option for read/ receipt notification

11 System should be able to evaluate the regularity of a user in terms of using email service by calculating average time between two consecutive logins and number of mails read/ written/ replied between the respective consecutive logins



12 System should categorize users based on their frequency of using email service as Regular, Irregular and Rare User

13 Should allow the user to search the messages from the archive based on message subject or between any two dates – Search to be powerful like Gmail

14 System should allow the user to choose the option of encrypting the message or digitally sign them

15 System should allow the user to print the message in printer friendly format

16 System should allow the user to use all the functionalities of email facility (such as checking mails, sending emails, receiving alerts of emails, deleting emails, etc.) on cell phone in case of receiving a new email in the inbox

17 System should show the usage statistics at all levels and departments

18 System should allow the user to search for email address of any other member of the service on the basis of personal particulars (Name, Rank, Posting place etc.)

19 Email address scheme to be specified in consultation with Puducherry Police

20 Admin should be able to block any particular email id/ mailbox

21 System to have a powerful Spam mails filters such as Gmail and Yahoo mail

Periodic Crime and Law & Order Reports and Review Dashboard Service


(Yes/No/Partial)

1 System should present customized dashboards to the users based on their role (Duty Constable, HC, IO, SHO, CI, SP and higher officers in the District/Region/ Head Quarters

2 System should present various statistics such as summarized information, current progress, monthly numbers, comparative statements, trends with charting capability, exception reports, and crime maps indicating the hot spots

3 Administrator should be able to customize and lock the contents of the dashboard for each office/ officer

4 Dashboard should be available to the user unit wise/ officer wise

5 System should allow the user to view alerts/events/reminders

6 System should present the user with statistics of all CFSs, those pending for >24 hrs, >48 hrs with the contact details of the citizen



7 System should present the user with statistics on “Newly Registered Cases”

8 System should present the user with statistics on registration (FIRs, Missing Person Reports, Unnatural Death Reports, Unidentified Dead Body Reports, Lost & Found Reports), status of investigation/ enquiry, final disposal etc.

9 System should present the user with statistics on FIRs with different status such as New/Under Investigation/ Pending Trial/ Re-opened

10 System should present the user with statistics on Summons, Warrants & Notices

11 System should present the user with court calendar which includes details namely; cause list, information on the cases under trial (next date of hearing, witnesses to be examined, summons issued/ served, witnesses already examined, stage of trial etc.)

12 System should present the user with activity calendar

13 System should present the user with statistics and progress of “high priority FIR” (List of Monitored Cases)

14 System should have the functionality to create a 360 degree profile of the dangerous, most wanted criminals – a dossier form to get generated from system Profile to include: 1. Personal particulars including name, DOB, photograph, language spoken, ID marks, peculiarities etc (as per prescribed format) 2. Sighting Report 3. Harbourers helping the criminals 4. Defense Lawyers Sureties, identifiers 5. Speech recording of criminal and Video Footage 6. Finger Prints etc. 7. Mug shots (in square pixels format) 8. Family members, associates, receivers of stolen property 9. Vehicle Used 10. Cell Phone Used/ Number Used 11. Any CDR associated with the Mobile Number

15 System should present the user with list of Pending Arrests & Wanted Offenders/Suspects

16 System should present the user with list of latest happenings across police stations such as missing persons & unidentified dead bodies

17 System should present the user with prisoner movement updates

18 System should present the user with Major and Minor head wise statistics

19 System should present the application usage statistics that provide indicators on the application uptake and usage by the police personnel

20 System should allow the user to drill down to a granular level to a complaint or suspect from the information presented in the dashboard



21 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)

22 System should allow the user to generate comparative statements of the above said statistics during monthly crime reviews

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

24 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

25 System should consolidate and generate statistics based on the role and jurisdiction

26 System should allow the user to view a list of Most Wanted Criminals on the dashboard

27 System should allow the user to generate reports on 1. Number of arrests made (as a data field in Special Report, Heinous Crime Cases)

28 System should allow the user to generate Daily/ Morning Situation Report

29 System should allow the user to generate report on 1. Number of criminals arrested during a day

30 System should allow the user to generate a crime chart with 1. Details on Cyber Crimes 2. Financial Frauds

31 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

32 System should allow the user to generate report on cases pending (with prosecution sanction awaited)

33 System should generate an alert in case the Case Diary is not handed over within 10 days of transfer



Notification of Alerts, Important events, Reminders and Activity Calendar or Task

Services


(Yes/No/Partial)

1 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 registered in a police station , in case a general petition/ call for service 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) using business intelligence and data mining tools. The tools would query the information stored in the Knowledge base.

2 System should automatically generate reminders of any pending or overdue actions on the cases that are pending registration / investigation / trail

3 System should allow the user to create and send user alerts / events /reminders to identified group / subscribed users / police stations

4 System should allow the user to schedule the activities and maintain the calendar with reminders

5 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

6 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

7 System should generate an alert for SHO, IO, before expiry of judicial remand till charge sheeted and where a charge sheet needs to be filed for an accused who is in jail

8 System should allow the user to generate alerts for Periodic progress of special report cases

9 System should generate an alert for an IO before bail hearing date

10 System should provide for generation and transmission of alert to all SHOs/DSPs/SP on release of important criminal / offenders from jail in sensational cases

11 System should generate alerts on 1. Court Case Hearing Date (to orginal PS (SHO) and concerned



IO) 2. Release and Parole information 3. Bank Robberies, Dacoity (in other districts states) (to SPs) 4. Accused Arrested (in the same police station) 5. Heinous Crime Case Details 6. FIR cases 7. Missing Persons 8. Stolen Vehicles 9. Unidentified Dead Bodies 10. Firearms Stolen

12 System should have a Dictionary of common names and each time a new name is entered the master data for names should be updated, subject to the approval of Administrator at the State level. 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. Example: when the user has entered Gane, system should show the various suggestions like Ganesh, Gaurav etc. and incase a user enters GaneshX, system should show an alert saying that "please correct the name if the entered name is incorrect"

13 System should allow the IO to select an appropriate distribution list from a master list of email to send any alert

UT CRB-NCRB Data Transfer and Management Service


(Yes/No/Partial)

1 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

2 The data extracted from States/UTs must be transformed into standard formats required by NCRB

3 The data should be run through a quality process to identify any possible duplicates or wrong data before sending to NCRB

4 Transformed and cleansed data must be uploaded on to NCRB databases

5 The system should provide the flexibility to cleanse and transform data

6 The system should support automatic extraction of data

7 System should provide an option to monitor and manage data Extraction, Transformation and Loading process

8 System should allow the user to kick start the load process manually in the absence of load failure

9 System should allow reconciling those records which failed during the load process



User Help and Assistance Services


(Yes/No/Partial)

1 The solution should provide detailed context-sensitive help material for all the possible actions and scenarios on all user interfaces in the application

2 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

3 The solution should have comprehensive help facility wherein the users can obtain system specific technical / functional help on line

4 The help should be accessible to the users both in the offline and online mode

5 The system should maintain and make available to user a database of frequently asked Questions

User Feedback Tracking and Resolution service


(Yes/No/Partial)

1 The solution should provide an interface for the user to log any defects or enhancement requests on the application and track thereafter

2 The solution should send alerts (e.g., email, SMS, knowledge management updates, etc.) to the user if the user chooses to, whenever any action has been taken on the alert

3 The solution should enable the user to track the submitted defect or enhancement request

4 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

5 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


(Yes/No/Partial)

1 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: (a) All the actions (create/read/update/delete) that are taken upon the critical entities (case, suspect, property,…) in the system (b) The user initiating and or carrying out the action; (c) The date and time of the event. (d) Administrative parameters The word “unalterable” is to mean that the audit trail data cannot be modified in any way or deleted by users, but the authorized users would have the provision to delete them; it may be subject to redepartment and copying to removable media if required, so long as its contents remain unchanged. 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

2 The System must maintain the audit trail for as long as required. Log/ audit trail of Investigation activities namely all Daily Diary entry, FIR Registration and entries of arrest should be logged only for a period of one month and shall be automatically deleted

3 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

4 The System must be able to capture and store violations (i.e. A user’s attempts to access/ tampering with information of a case/ crime & criminal database to which he is denied access), and (where violations can validly be attempted) attempted violations, of access control mechanisms

5 The System must at a minimum be able to provide reports for actions on violations with appropriate mechanism to escalate such cases

State Specific Modules

Visitor Information System Module


(Yes/No/Partial)

Hotel:

1 Should provide the functionality to the Hotel owners of registering their Hotel details - Name of the Hotel -Owner/ Manager valid identification details - Staff identification details - Staff Verification details - City - District - Nearest Police Station -PAN Number -Tax Identification Number or any other Registration Number



2 Foreigners:

3 Ability to allow the Foreigners to submit the Arrival Report

4 Ability to apply for Registration Certificate, Registration permit to concerned REO

5 Ability to allow the hotel staff to upload the personal particulars of the foreigners

6 Ability to provide alerts on over stay

Indian Citizens:

7 Ability to allow the hotel staffs to submit the arrival / check –

in report in the prescribed format with mandatory fields

Cyber Café:

8 Should provide the functionality to the Cyber café owners of registering their cyber café details - Name of the Centre - Name of the Owner -Owner valid identification details - City - District - Nearest Police Station -PAN Number -Tax Identification Number or any other Registration Number - Mobile / Phone Number

9 Should allow periodic registering the information of the users at cyber café: - Customers Name and Identification Proof - Address - Mobile / Phone Number - Nationality (for non-Indian nationals Passport Number is mandatory) - Date and Time of Internet usage of each user System should be able to auto-populate the information of café users based on previous entries, if any

Human Resource Management System (HRMS) Module


(Yes/No/Partial)

Employee Information



1 System should allow entering employee information like Employee ID No., Name of the employee, Date of Birth, height, weight, Permanent Address, Name of the district, Caste, Education Details, Details of the family (Spouse, Children), Date of Joining, Due Retirement Date, any departmental enquiry ,Character verification, joined as what designation, Service record of the employee, present deputation etc.

Service Book

2 System should maintain the service book of employee online with details of Employee, Promotions, Transfers, Departmental Enquiry

Payroll Generation

3 System should be able to link payroll to the online Treasury

Payroll

4 System should be able to integrate the employee salary detail

into the employee account

5 System should be able to generate the gross salary of

employee based upon basic pay

6 System should provide bill clerk with an option to print salary

details of selected employees

7 System should provide the bill clerk with option to retrieve old

salary details of any employee

8 System should provide employee with an option to view his/

her salary details for any selected month

Transfer / Promotions

9 System should allow clerk to create a case for

Promotion/Transfers

10 System should move the case file as per the process flow

11 System should provide with an option to approve the case or

to add remarks or to add remarks & send it to concerned

authority

12 System should provide the users with a dropdown list to select

& mark the various authorities as required

13 System should allow clerk to add remarks & mark to

concerned person

14 System should be able to update the accounts of the promoted

employees



15 System should generate a unique ID for every case created

Vacancies

16 System should be able to generate list of vacant positions

17 System should be able to generate Recruitment Calendar for

various districts

Annual confidential report (ACR)

18 System should allow dealing hand to scan & attach the ACR

with the employees’ account

19 System should allow dealing hand to add any remarks along

with the ACR

20 System should allow to retrieve & view the attached ACR

21 System should allow to add remarks to the attached ACR

22 System should allow marking the ACR to higher officials for

their review purpose

23 System should provide dropdown options to choose the

desired officer to mark the ACR to

24 System should allow the other officers to retrieve the ACR

marked to him

25 System should allow the concerned officer to add remarks to

the ACR

26 System should allow the officer to mark the ACR to desired

officer/ dealing hand

27 System should update the final remarks of the concerned

authority against the ACR & should update the ACR into the

employees’ account

28 System should allow the concerned officer/ dealing hand to

retrieve the previous ACR of an employee

Leave

29 System should allow employee to submit a leave request by

logging into his/her account

30 System should be able to manage the leave status of the

employee under various categories



31 System should be able to route the leave request to concerned

officer as per the process flow

32 System should allow OSI to create a leave request on the

behalf of employee account

33 System should allow the concerned authority to retrieve the

leave as well as employee details upon receiving the request

34 System should provide the concerned authority with an option

to approve or reject the service request

35 System should be able to update the employees’ account after

the leaves are approved

Training details

36 System should allow dealing hand to create a case for training

37 System should allow dealing hand to scan & attach documents

to case

38 System should allow dealing hand to mark the case to

concerned authority from a drop down list

39 System should create an alert to the concerned authority

about the creation of the case

40 System should maintain log of the case file

41 System should retrieve the case details as requested by

authority/ dealing hand

42 System should allow viewing person to print a portion of the

case file

43 System should allow the concerned authority to add remarks

to the case file

44 System should allow concerned authority to mark the case to

dealing hand or other person from a list

45 System should allow concerned authority to approve/ reject

the case

46 System should create an alert & intimate the dealing hand

about updated case file

47 System should update training certificate to CRC file of

employee once approved by concerned authority



Departmental enquiry

48 System should allow to raise a new case for Departmental

Enquiry

49 System should allow officials to view, update Departmental

Enquiry

Post Retirement Benefits

50 System should maintain the post retirement benefits like

pension, PF, GPF, EPF details for employee

51 System should maintain the PF amount withdrawn by

employee

52 System should allow requesting for withdrawal of post

retirement benefits for employee

Logistics Management System Module


(Yes/No/Partial)

1

Should have the inventory status ( Receipt/ Issue/ Store

Holding) of all type of assets including vehicles, arms and

ammunitions, land & buildings, radio and IT equipments, other

movable items, consumables etc. (Head wise and Sub Head

wise)

2

Should allocate unique asset no to every asset based on their

category like computer system, laptop, car, arms etc. The

unique number should be meaningful and indicate head,

subhead, year of purchase etc.)

3

The system should have facilities for maintaining a

comprehensive fixed assets register, including:

a) Asset Serial number

b) Asset Description

c) Asset category (Major Head & Minor Head)

d) Custodian Branch / Unit / Individual

e) Purchase Date

f) Warranty period/AMC start date and end date (if



any)

g) Original cost

h) Asset Useful life in years

i) Condemnation date

j) Auction date

k) Disposal date

4

Should provide a detailed maintenance management service –

date, time, permit no, asset no, bill no, cost of maintenance etc

of assets sent for maintenance

5

Should maintain inventory records of (location, department,

person, asset no., etc.):

a) Vehicles

b) Arms & Ammunitions

c) Furniture

d) Hardware

e) IT

f) Radio equipment

g) Consumables

6 Receive requirements of office inventory from authorized

personnel

7 Should have the option to check the availability of an

inventory in the organization

8 Should allow allocation of the office inventory to departments

/ projects on the basis of requirements.

9

Should allow monitoring of inventory issued to individual

members of the service (especially Gazetted Officers) with the

due date. Should also generate annually the list of inventory

with each official for his information and acknowledgement.

10 Should allow to generate letter for purchase/ permission

approval of new office inventory

11 Should be possible to maintain the approval process hierarchy

for these letters



12

The system should have the provision to monitor the condition

of assets/equipment and components and in case of motor

vehicles assist in periodic vehicle maintenance.

13

System should capture POL details calculating running

expenses per km, maintenance cost/ km, year on year, month

on month comparison and comparison between drivers

14 Should allow creating preventive maintenance schedules for

assets.

15 Should enable the storing of preventive and reactive

maintenance records for each asset as asset history

16 Should generate reminders for warranty expiry and AMC

renewal

17 Should be able to store and provide details of vendors for

AMC/warranty and Rate Contracts

18 Should be able to generate reminders for statutory bill

payments at pre-defined time

19 System should provide actual status of asset holdings with

each officer or a class of officers for seeking acknowledgement

20

System should be able to generate No Dues certificate at the

time of superannuation of officer, once the asset holdings have

been submitted in the Store

21 System should capture details of insurance/ warrantee/ AMC

of each asset for periodic checks and necessary action

22 System should generate alerts for periodic maintenance/

insurance renewal/ AMC renewal, etc. for each asset

23

System should be able to capture the Purchase Terms &

Conditions of each asset, which should be available for

reference of Police Units

24

In case of purchase of assets, system should capture details of

its receipt in store and further issuance or delivery to a

specific location.

25

Once the asset has been received by an individual or by a

Police Unit, system should be able to capture the

acknowledgement from the concerned and generate receipt



General Verification Module


(Yes/No/Partial)

1

Should have the interface with the other department Regional Passport Office and SDM Office for Police Verification for issuance of Passport, and issuance of Arms Licenses (in districts only) respectively. SDM office will also have an interface to request police services for carrying out the knowledge tests in the case of Driving Licenses

2 Should be linked with payment gateway for receiving fees against providing service verification

3 Should have provision of generating dynamic user id and password for an authorized users of other Government departments Password to be sent in email as a message

4 Should provide acknowledgement to the requester office post receiving request for verification

5 Should have provision for searching all databases with the name and other details provided as part of primary verification

6 Should have provision to help assign a verification request to a Verifying Officer

7 System should allow the Verifying Officer, if required to fix verification date and time

8

System to have functionality of a checklist which can be filled during physical visit and take witnesses (witness at verification location)signatures, pictures or thumb prints (as required)

9 System should allow the Verifying Officer to prepare reports using standard templates from anywhere, based on the data entered using handheld device

10 Should help Police in providing their recommendations with remarks on the verification

11 Should allow for approval by the concerned officer (Police Station SHO), SP Office before providing the recommendations on the request

12 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

13 Should be able to provide updated status on the verification exercise on a real time basis



Vehicle Tracking System Module


(Yes/No/Partial)

1

The system should accept the information from the database maintained from the Regional Transport Office (RTO) Puducherry and bridging the Puducherry RTO database thro’ online.

2

The system should search the vehicle on the basis: i. Registration Number

ii. Chasis Number iii. Engine Number and also provide particulars of

vehicles and owner details

3 The system should also maintain a separate database for Puducherry Police with updation facility

4 The system should search the vehicle details from motor vehicle, SCRB and NCRB database to track stolen vehicle based on Registration No, Chasis No, Engine No.

Note: Application Software for State specific modules has to be tested and certified for its security

vulnerability by anyone of the vendors empanelled by MCIT.



Annexure 10 – Technology Stacks for CAS (State/UT) and CAS (Center)

CAS (State/UT) will be developed in two distinct technology stacks by the SDA at the

Center.

The Technical Details for CAS (State/UT) Solution Stack 1 and Stack2, CAS (State/UT) Offline

solution, CAS (Centre) Solution are provided in subsequent tables:

CAS (State/UT) Solution - Stack 1

The Below list is indicative only

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 openCMS search features Structured Data MySQL & Custom application interface

N/A N/A N/A N/A

Portal Server Glassfish 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 OpenCMS 7.5.1 OpenCMS Content Management System



Security Physical Security, Network Security, DB Encryption (MySQL), DB Access Controls, Role Based Access Control (Custom Developed), LDAP (Sun Directory Services),

N/A N/A N/A N/A

Identity Management

OpenSSO 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/UT) Solution - Stack 2

The Below list id indicative only



Original Supplier


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

Others

Reporting engine SQL Server Reporting Services

2008 Microsoft Reporting Services

Microsoft

Email/Messaging Q-Mail 1.4 Qmail Community

E-Mail Solution

Search Engine Search: Unstructured data: using openCMS search features Structured Data SQL DB Search Engine & Custom application interface

N/A N/A N/A N/A



Portal Server IIS 6 Microsoft Web and Application Server

Microsoft

Workflow Engine Windows Workflow Foundation

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


N/A N/A N/A N/A

Identity Management

Microsoft Active Directory

2008 Microsoft LDAP Microsoft

Audit IIS Log, Custom built

N/A N/A N/A N/A

ETL SQL Server ETL 2008 Microsoft ETL Microsoft

CAS (State/UT) Offline Solution

The below list is indicative only



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 SUM / Microsoft DB Store SUN / Microsoft



CAS (Center) Solution

The below list is indicative only



Original Supplier


Support Provided by

Web server Sun Java System Web Server 7.0


Application Server Glassfish Application Server


SUN

Database Sybase IQ Enterprise 15.1 Sybase ETL Sybase

Operating System Solaris

Others

Reporting engine Jasper Reports 3.7 Jasper Reporting Services

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


Directory Services SUN Directory Services

7.0 SUN LDAP SUN

DMS/CMS Alfresco

Email/Messaging NA


N/A N/A N/A N/A

Identity Management

OpenSSO 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



Annexure 11 – Bills of Material for DC, DR and other locations

Bill of Quantity here are only indicative desired for the implementation of this project.

Department reserves the right to increase or decrease the quantity of material at any time

during the implementation of the project to any extent and department shall make payments for

each component on actual number provided by SI.

SI is requested to put due diligence while responding to this RFP and shall be responsible for

proposing other hardware/ software components as part of their Bill of Material for the

successful implementation of this project

Sl

No. Equipment Qty

1 Data Center Storage

SAN Storage 1

SAN Switch 2

2 Disaster Recovery (DR) Storage

SAN Storage 1

SAN Switch 2

3 Data Center Server cost

Database Server 2

Blade Chasis 1

Blade Server 13

4 Disaster Recovery (DR) Server

50% of DC

5 Automated Tape Library for Data Center 1

6 Security items for DC & DR Centers

Data Center



Sl

No. Equipment Qty

UTM and HSM 2

DR Center

50% of DC

7 Software for Data Center & DR Center

Data Center

Data Base- SQL server 2008 Enterprise/ My SQL 2

Web Server – IIS 7.0 / Glassfish 4

E mail Messaging Software (Free with Linux) 1

Antivirus Software 1

Proxy with web filtering 1

Helpdesk management system 1

Operating System for Server Bundled with server

DR Center

50% of DC

Detailed Breakup of the Blade server for DC & DR

Bill of Material for CCTNS Project

Sl No. Equipment Location Qty

Server Hardware

1. Database Server Data Center 2

2. Application Server Data Center 2

3. Intranet Web Server Data Center 2

4. Mail Messaging Server Data Center 2

5 Directory Server Data Center 1

6 DMS and Workflow Data Center 2



7 Proxy n Antivirus Server Data Center 2

8 EMS Server Data Center 1

9 42 u Rack Data Center 2

Detailed Breakup of System Software required for DC & DR

System Software for CCTNS Project

Sl No. Equipment Qty

Data Center

1 Data Base- SQL server 2008 Enterprise (Microsoft)/ My SQL(Open Source) 2

2 Web Server – IIS 7.0 / Apache + Glassfish 4

3 Application and Portal- Microsoft / Sun Portal Server + Glassfish AS 2

4 Directory Server - Microsoft Active Directory/ Open SSO + SUN Directory 2

5 E mail Messaging Software (Open Source RHEL/ SUSE Linux) 1

6 Antivirus Software 1

7 DMS and Workflow 1

8 Helpdesk management system 1

9 Licenses for Tivoli software for Managing of all servers ( we want to use

existing EMS of SDC)

Note:

1. For Automated Tape library for Data center – Only tapes compatible with SDC Tape

Library system IBM/TS 3010 is required

2. All Cabling within the racks, need to be provided by SI (LAN cabling completed up to

rack level at PYSDC)

3. The software for DC should have compatibility and needs to be discussed with DCO,

PYSDC before Procurement.

4. The existing Back –up Software in DC can be utilized by the SI with consultation with

PYSDC.

5. Exact Server sizing would be done by the SI for server hardware for DC with

consultation with PYSDC.

6. The system software for DC should have compatibility and needs to be discussed with

DCO, PYSDC before Procurement.



7. PYSDC has already some antivirus client licenses, it may contemplate if we can use

those licenses or SI to buy additional licenses for the purpose with consultation with

PYSDC.

8. The SI concerned has to sign a MOU with PPEGS for the Co-location at PYSDC.

9. The operation and Maintenance (O & M) charges amounting to 2% of total cost of

hardware proposed to be deployed at PYSDC, needs to be paid on a quarterly basis to

DCO, PYSDC. This O&M cost does not include AMC cost.

10. The Power consumption per rack shall not exceed 5 KV.

Note: Bill of Materials (Infrastructure) shall be supplied after the identification of

Disaster Recovery (DR) site in consultation with UT.

Annexure 12 – Network Connectivity Solution

CCTNS is deployed on a centralized architecture wherein various offices of Puducherry Police

connect to the system through State Data Centre. The entire solution architecture is based on

following 4 pillars:

Users/Stakeholders

Delivery Channels

Services / Modules

Resources

Figure below shows the overview and depicts CCTNS services accessed by different users

through various channels and resources that integrate and interoperate to deliver these

services.



Solution Summary

Based on based on n-tier Service Oriented Architecture (SOA)

DC at SDC (during transition phase)

DR at NIC/ Other adjoining State

Network and Security will be taken care by SDC/NIC/PSWAN

Police Station – (4 desktops) with webcam+ finger print device + 2 printer

Portal Architecture

Portal Server is a key to a SOA approach because it provides a common framework and interface

to integrate information, people and business processes.

Essentially a portal is a series of different applications and services - some of which come with

the portal itself (e.g. content management, search, document management etc.) other

applications are then combined and assembled (together with any relevant business processes)

at the “front-end” via portlets, thus making Portal into what is essentially a giant “composite”

application.

In addition to the common interface and application and content integration framework

provided by Portal, it should also support

Different access modes to applications and services

Roles and processes based access which can be used to vary what applications and services a user can see.

The ability for business users to create and extend portal applications without the need for any programming.

Application templates that allow business users to easily assemble and customize linked applications and processes into composite applications.



The proposed architecture can be broken into several main components. First there are the

main actors in the system comprised of citizens, CRB users, Police Station users and other

agencies, Local IB, etc. Secondly there are the main business services that the architecture

offers. Thirdly the data exchange service between UT server & Police station and UT server to

Central NCRB Server. Finally there is the portal framework itself which provides a pre-packaged

prescriptive architecture based on tried and true architectural approaches – SOA, pre-

integrated products, industry standards, and a shared knowledge base of experience.



Deployment Architecture (Centralized)

This will have the following nodes:

Load balancing – The load balancer provides horizontal scalability to the web servers

by dispatching Hyper Text Transfer Protocol (HTTP) requests among several identically

configured security gateway i.e. web servers. This node enhances system availability,

capacity, and performance. As the Mission Convergence Portal system grows, the ability

for the system grows and balance load while remaining its service level agreements will

be extremely important. Also, the ability to stay up and running at all times with

appropriate failover is accomplished through the ability to cluster and load balance

servers.

Web Server (UI) node – The web server node or HTTP server is typically designed for

access by HTTP clients and to host static content for presentation. The web server also

provides services for serving other protocols like FTP, RTSP, etc. User requests for

dynamic content are forwarded by the web server to the application server for

processing.

Portal Server node– The portal server nodes provide the user presentation services.

The portal server provides the services to dynamically define a standardized enterprise

look and feel for the web applications. The portal server provides the user with the

ability to personalize web applications based on the user preferences and business rules

defined within the portal. Portals can be designed to be presented particular ways based

on roles, as well. This node enables functionality for pervasive devices, including

intelligent notification.

Web Content Management Node– It is proposed to collaborate for content creation,

approvals, management, retention, and publishing across internet, intranet and extranet



assets. It is a power and sophisticated web content management product designed to

accelerate development of portal contents. The web content manager for portable

document manager is used for web content management for production server and

facilitates storage and rendering of web contents from Portable Document Manager.

Business Process Manager/Workflow Management System Node– This node

manages the business workflow processes that involve business functions and human

interaction. It ensures that the business processes are executed in the proper order by

the proper people and systems. There will be business process associated with the Govt.

Department services for processing the user service request. Depending on the nature

of those workflows, a workflow system within closely connected to a content

management system might be needed, or a broader-based workflow engine.

Electronic Forms Server Node– This node would work on top of J2EE application

server and provides API for processing & integrating forms with Mission Convergence

Portal processes. These would have capabilities to attach the supporting documents,

digital signatures etc. along with the form.

Content Manager Nodes – This node provides for both structured data in the form of a

relational database management system (RDBMS) and unstructured content. The

content manager functionality includes integration of all forms of information, from

XML, text, images, documents, biometric data and more. The Mission Convergence Portal

System will have to handle a lot of various types of data and information. The ability to

store different types of information, group that information into cases and query on it,

making a Content Management node very important. This node also provides the basic

document workflow to model the business processes as part of Mission Convergence

Portal Business Process.

Web Application Server node – This node provides the infrastructure for component

based application logic. The web application server(s) provide the underlying J2EE

services for running servlets, JSPs (Java Server Pages) and EJB (Enterprise Java Bean)

objects, as well as interacting with other components (JMS, JDBC, etc). Web application

servers also provide transaction management capabilities and can be configured to

provide a highly scalable and available network for running web based applications.

The web application server also provides a runtime environment for hosting and

accessing web services. For the proposed system, web application server will be the

central runtime environment for applications i.e. grievance management, Helpdesk

applications, Portal and Dashboards and MIS.

Data Management Node- This node provides for both structured data in the form of a

relational database management system (RDBMS). This node is being used for managing

the master data, transaction data, relationship data, and other operational data entities

of various application modules products. There is a need to have a Data Quality Engine

to filter out quality data from the existing such databases with the various departments.

Identity Solution Node – This node discovers individual’s identity i.e. “Who is Who?” It

does resolves inconsistent, ambiguous identity and attributes information into a single

resolved entity across multiple data sets, despite deliberate attempts to confuse or



misrepresent individual identity. This node exposes the web services which have been

consumed by business process engine for fulfilling the business requirements.

Enterprise Systems Management node – This node offers a full range of functionality

for monitoring and managing an enterprise-level system for quality of services levels,

system performance, potentially outages, efficient use of system resources, and more.

The more robust capability of managing not only system components, but system

services, is possible with a Mission Convergence Portal System that follows an SOA

Framework, thus lowering costs from more efficient utilization of system resources and

pro-active system upkeep.

Network Architecture

InternetMPLS Cloud

Database

ServerApplication

Server

Mail ServerWeb ServerAnti Virus Server

Domain Controller

Server LAN

EMS Server

Database

Server

DNS Server

Core Switch

WAN Router

Ethernet

Connectivity

with Server LANServer

farm

firewall

firewall

Storage SAN

Server

Farm

Proposed Components at

State Data Center

WAN Router

Higher Offices

Police Stations

CCTNS

Application

CAS (Center)

WAN Router

National Data

Center

PHQ

Training Centers

VPN Over B

B

It is proposed that SDC shall be used as Primary DC. Servers and Networking equipments

should be provided by System Integrator. Bidder will propose the Severs with SSL encryption

and Server Load Balancer along with the storage.

The CCTNS database at the State Data Center will be mirrored at Disaster Recovery on a

routine basis. This Disaster recovery shall serve as a redundant link in case of failure in

accessing the application from the State Data Center.

Information Security Measures

CCTNS application security initiatives should include, DMZ Policy, encryption, authentication,

authorization and digital signature. It should take the appropriate measures for the data

privacy, confidentiality and access control.



CCTNS’s complete security is assured by implementing the security at the following levels,

Component level (Operating system, routers, switches etc.) security (ISO 15408)

Application level (Basic application for access control, authentication and audit trail etc.)

security

System level (Physical security, communication and operation management, business

continuity management etc.) security (ISO 27001)

Integration with WAN

Core Infrastructure – ISP & PSWAN

ISP will provide the broadband connectivity with over 48 Police points as the primary

connectivity in the UT. The Data & Voice connectivity can be used as primary connectivity with

its existing network. PSWAN is also used to connect distributed network sites in a Government

via private or public telecommunication lines. It typically serves as a customized

communication "backbone" interconnecting all the Government local networks with

communications trunks that are appropriate based on anticipated communication rates and

volumes between nodes. The network would be able to support Voice, Data and Video services.

It would form the backbone on which all departmental and core applications reside. The WAN

will connect the CCTNS headquarters, zones, Districts and police stations. This robust

connectivity backbone right from the UT headquarters to the lowest hierarchies will make it

possible to have better service standards and lesser Turnaround Time for all the stakeholders of

the department.



State Data Centre

The State Data Centre would be located at Puducherry, and would function as a centralized

location to host all the IT initiatives in the UT. It would act as a mediator and convergence point

between the open unsecured public domain and sensitive government environment. The SDC

enables various government departments to host their services/applications on a common

infrastructure leading to ease of integration and efficient management, ensuring that computing

resources and the support connectivity infrastructure (PSWAN) is adequately and optimally

used. The SDC would need to be equipped with UT of the art Data Security, System Security,

Internet Security, Redundant Power supply, Access Control System, Air-conditioning and other

infrastructure. The Data Center in the SDC would host the CCTNS Core UT Application and the

Department Applications.

Data Center Optimization with Scalability and Redundancy:

The major components of Data Centre that need to be considered are listed in the table below

and detailed BOM for DC has been provided in annexure:

Data Center Setup Requirements

Space Requirement: As least 500 sq feet space is required to accommodate Network

infrastructure, Server infrastructure and security infrastructure.

False ceiling: To reduce the heat conductivity false ceiling is required for all standard data

center design. Ceiling should be done by the heat and electrical resistance.

False Flooring: Providing and fixing Access flooring system (False floor) M-floor laminated

HPL panel with edge support rigid grid understructure system. Access floor system to be

installed shall provide a maximum finished floor height of 1'from the existing floor level. The

system shall provide for suitable Floor tiles, pedestals and stringers designed to withstand

various static loads and rolling loads. The entire Access floor system shall be made from steel

cementations in filled. Access Floor tiles shall provide for adequate fire properties, acoustic

barrier and air leakage resistance. The system shall be able to accept an approved laminated

floor covering i.e. Anti-static High pressure laminate with PVC beading on the edges of the

tiles.

Electrical System And Installation: Supply (including Main DC Panel, Power Cables, TPN, UPS

Power Distribution Board, PAC and Lightning Distribution Board, Point Wiring, Light Fixture,

Cable Trays, Emergency Lamp, Copper Plate Earthing, Earthing Strips, Static Switch etc),

Electrical System-Install

Fire and Security: Fire and Security System (Including Analog Addressable Fire Alarm System,

Analog Addressable Microprocessor based multi cooperative type, photo thermal multi

criteria detector, Laser type photoelectrical smoke detector, manual call point with mini

monitor module, electronic sounders, Fault isolator, FM 200 Fire Suppression System, Access

Control System, Building Management System, Rodent Repellent System, Fire Extinguisher

System etc)

Water Leak Detection System: Water Leak Detection (including 4 Zone WLD panel, WLD cable,

Relay Module, 2 Core 1.5 Sq mm shielded armored cable for Signal etc.)

Passive Cabling Services: As the structure cabling is the main key area of standardization of a

Data Center, so patch panel for UTP cabling and LIU for Fiber cabling needs to be implemented

inside the server and NW rack. Cable should be laid under the false floor and run inside proper

PVC cable tray. The same should be applicable for the optical fiber cable also.

AC Supply: In the current scenario and considering the current location of the Data Center



precision AC to be prescribed with redundant PAC unit. As per the total heat count calculation

to be done on BTU (British thermal unit) per Hr basis.

Structure Cabling: As per the current scenario Police Department does not have the cabling

infrastructure, so for entire IT roll out Data Center, District HQ, Police stations and Disaster

recovery will be proposed with total structural cabling design.

Component wise service redundancy is the major and key component of DC design. Data Flow is

assumed to hit Distribution layer and then directly flow into core Layer for traffic segregation

for intranet and internet.

For the redundancy purpose, two numbers of Distribution switch are required to be introduced

with active and standby unit. Redundant multi mode fibers to be connected for the uplinks

towards Core layer switches. All the Core access layer switches are to be connected with Multi

mode fiber up links from each distribution switch for VLAN and physical redundancy.

As mentioned before Core switches are required for Data traffic segregation from Distribution

and end computing towards WAN. For the redundancy purpose units of Core switches to be

introduced and WAN components will be terminated to the core switches by the Layer 2

switches which will be trunked to the core switches by multi mode fiber connectivity. Therefore

it is required that two units of layer two switches should be introduced for WAN router

connectivity and transit to the Core layer for LAN integration. Distribution Core switches will

configure with VRRP for VLAN and L2 connectivity redundancy, and core switches will be

configured with VRRP for traffic flow redundancy for wide area network.

The Data Center design has been proposed to reach redundancy and scalability. As per the

above diagram three layered architecture has been followed for LAN equipment, security

infrastructure and Wide area Network. DMZ has been created for online services of the

applications and other online services from the organization prospective. The layer has been

mentioned in the diagram as Access Layer Core Switches, Distribution Layer modular switch,

Core Layer modular switch. Dual Intranet routers, dual firewalling system, IPS/IDS and dual

internet switches.

Disaster Recovery

Disaster recovery is the process, policies and procedures related to preparing for recovery or

continuation of technology infrastructure critical to an organization after a natural or human-

induced disaster. Disaster recovery is a subset of business continuity. While business continuity

involves planning for keeping all aspects of a business functioning in the midst of disruptive

events, disaster recovery focuses on the IT or technology systems that support business

functions.



Facilitates management and utilization of CAS Application resources through virtualization

concepts

Achieves high availability of critical data by optimal usage of the existing infrastructure

thus reducing the financial, operational and business impact in the event of any natural,

manmade or technical disasters

Enables seamless growth of CAS during the entire lifecycle by removing dependencies

on specific hardware configurations

Manages Trigger like loss of site events very effectively

The separate DR capability supports an entirely flexible development, test and staging

environment. The result was a visibly increased performance and far greater utilization

capability. The above diagram shows the overview of Disaster Recovery LAN & WAN

integration. All the critical services are required to be replicated in disaster recovery, so only

one broadcast domain will be created. Because of the above reason, two sets of switches and

one WAN router are mentioned in diagram.



Network Diagram for DC and DR Site:



Annexure 13 – Technical Specifications (Indicative)

Minimum Technical Specifications Requirement at State Data Center & Disaster Recovery

Site

1. Enterprise Management and Monitoring Solution (EMS)

The basic requirements for EMS are given below

SI shall be required to provide all the necessary hardware/ software to meet the below

mentioned indicative requirements from EMS.

Basic Requirements Compliance (Y/N)

1 Solution should be inclusive with hardware, OS,

patches, etc.

2 Solution should provide for future scalability of the

whole system without major architectural changes.

3 Should be SNMP v1, v2, v3 and MIB-II compliant.

4 Filtering of events should be possible, with advance

sort option based on components, type of message,

time etc.

5 Should support Web / Administration Interface.

6 Should provide compatibility to standard RDBMS.

7 Solution should be open, distributed, and scalable and

open to third party integration.

8 Should provide fault and performance management for

multi-vendor TCP/IP networks.

Security Compliance (Y/N)

1 Should be able to provide secured windows based

consoles / secured web-based consoles for accessibility

to EMS.

2 Should have web browser interface with user name

and Password Authentication.

3 Administrator/ Manager should have privilege to

create/modify/delete user.

Polling Cycle Compliance (Y/N)




1 Support discriminated polling

2 Should be able to update device configuration changes

such as re-indexing of ports

Fault Management Compliance (Y/N)

1 Should be able to get fault information in real time and

present the same in alarm window with description,

affected component, time stamp etc.

2 Should be able to get fault information from

heterogeneous devices — routers, switches, servers etc.

3 Event related to servers should go to a common

enterprise event console where a set of automated tasks

can be defined based on the policy.

4 Should have ability to correlate events across the entire

infrastructure components of DC/DR

5 Should support automatic event correlation in order to

reduce events occurring in DC/DR.

6 Should support advanced filtering to eliminate

extraneous data / alarms in Web browser and GUI.

7 Should be configurable to suppress events for key

systems/devices that are down for routine

maintenance or planned outage.

8 Should be able to monitor on user-defined thresholds

for warning/ critical states and escalate events to event

console of enterprise management system.

9 Should provide out of the box root cause analysis with

multiple root cause algorithms in built for root cause

analysis.

10 Should have self-certification capabilities so that it can

easily add support for new traps and automatically

generate alarms.

11 Should provide sufficient reports pertaining to asset

and change management, alarms and availability of

critical network resources as well as network response




times for critical links.

12 The tool shall integrate network, server and database

performance information and alarms in a single

console and provide a unified reporting interface for

network and system components. The current

performance state of the entire network and system

infrastructure shall be visible in an integrated console.

13 Should provide an integrated performance view for all

the managed systems and networks along with the

various threshold violations alarms in them. It should

be possible to drill-down into the performance view to

execute context specific reports

14 Should provide the following reports for

troubleshooting, diagnosis, analysis and resolution

purposes: Trend Reports, At-A-Glance Reports, &

capacity prediction reports

15 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

Discovery Compliance (Y/N)

1 Should provide accurate discovery of layer 3 and

heterogeneous layer 2 switched networks for Ethernet

2 Manual discovery can be done for identified network

segment

Presentation Compliance (Y/N)

1 Should be able to discover links with proper colour

status propagation for complete network visualization.

2 Should support dynamic object collections and auto

discovery. The topology of the entire Network should

be available in a single map.

3 Should give user option to create his /or her map

based on certain group of devices or region.

4 Should provide custom visual mapping of L2 and L3




devices connectivity and relationships

Agents Compliance (Y/N)

1 Should monitor various operating system parameters

such as processors, memory, files, processes, file

systems etc. where applicable using agents on the

servers to be monitored.

2 Provide performance threshold configuration for all the

agents to be done from a central GUI based console

that provide a common look and feel across various

platforms in the enterprise. These agents could then

dynamically reconfigure them to use these threshold

profiles they receive.

System Monitoring Compliance (Y/N)

1 Should be able to monitor/manage large

heterogeneous systems environment continuously.

2 Windows OS o Should monitor / manage following:

Event log monitoring Virtual and physical memory

statistics Paging and swap statistics Operating system Memory Logical disk Physical disk Process Processor Paging file IP statistics ICMP statistics Network interface traffic Cache Active Directory Services

o Should be capable of view/start/stop the services on windows servers

3 Unix / Linux o Should monitor with statistics :

CPU Utilization, CPU Load Averages

System virtual memory (includes swapping and paging)

Disk Usage No. of Inodes in each file system




Network interface traffic Critical System log integration

Infrastructure Services Compliance (Y/N)

4 IIS / Tomcat / Apache / Web server statistics HTTP service HTTPS service FTP server statistics POP/ SMTP Services ICMP services Database Services – Monitor various critical

relational database management system (RDBMS) parameters such as database tables / table spaces, logs etc.

Application Performance Management Compliance (Y/N)

1 End to end Management of applications (J2EE/.NET

based)

2 Determination of the root cause of performance issues

whether inside the Java application in connected back-

end systems or at the network layer.

3 Automatic discovery and monitoring of the web

application environment

4 Ability to monitor applications with a dashboard.

5 Ability to expose performance of individual SQL

statements within problem transactions

6 Monitoring of third-party applications without any

source code change requirements.

7 Proactive monitoring of all end user transactions;

detecting failed transactions; gathering evidence

necessary for problem diagnose.

8 Storage of historical data is for problem diagnosis,

trend analysis etc.

9 Monitoring of application performance based on

transaction type

10 Ability to identify the potential cause of memory leaks.

Reporting Compliance (Y/N)




1 Should able to generate reports on predefined /

customized hours.

2 Should be able to present the reports through web and

also generate ―pdf‖ / CSV /reports of the same.

3 Should provide user flexibility to create his /or her

custom reports on the basis of time duration, group of

elements, custom elements etc.

4 Should provide information regarding interface

utilization and error statistics for physical and logical

links.

5 Should create historical performance and trend

analysis for capacity planning.

6 Should be capable to send the reports through e-mail to

pre-defined user with predefined interval.

7 Should have capability to exclude the planned-

downtimes or downtime outside SLA.

8 Should be able to generate all sorts of SLA Reports.

9 Should be able to generate web-based reports,

historical data for the systems and network devices and

Near Real Time reports on the local management

console.

10 Should be able to generate the reports for Server,

Application, infrastructure services and Network

devices in DC/DR environment.

Availability Reports Compliance (Y/N)

1 Availability and Uptime – Daily, Weekly, Monthly and

Yearly Basis

2 Trend Report

3 Custom report

4 MTBF and MTTR reports

Performance Reports




1 Device Performance – CPU and Memory utilized

2 Interface errors

3 Server and Infrastructure service statistics

4 Trend report based on Historical Information

5 Custom report

6 SLA Reporting

7 Computation of SLA for entire DC/DR Infrastructure

8 Automated Daily, Weekly, Monthly, Quarterly and

Yearly SLA reports

Data Collection Compliance (Y/N)

1 For reporting, required RDBMS to be provided with all

licenses.

2 Should have sufficient Storage capacity should to

support all reporting data for 5 Years of DC/DR

operation.

Integration Compliance (Y/N)

1 Should be able to receive and process SNMP traps from

infrastructure components such as router, switch,

servers etc.

2 Should be able integrate with Helpdesk system for

incidents.

3 Should be able to send e-mail or Mobile –SMS to pre-

defined users for pre-defined faults.

4 Should trigger automated actions based on incoming

events / traps. These actions can be automated

scripts/batch files.

Network Management Compliance (Y/N)

1 The Network Management function must monitor

performance across heterogeneous networks from one

end of the enterprise to the other.




2 It should proactively analyze problems to improve

network performance.

3 The Network Management function should create a

graphical display of all discovered resources.

4 The Network Management function should have

extensive reporting facility, providing the ability to

format and present data in a graphical and tabular

display

5 The Network Management function should collect and

analyze the data. Once collected, it should

automatically store data gathered by the NMS system

in a database. This enterprise-wide data should be

easily accessed from a central location and used to help

with capacity planning, reporting and analysis.

6 The Network Management function should also

provide information on performance of Ethernet

segments, including capacity utilization and error

statistics for the segment, WAN links and routers.

7 Alerts should be shown on the Event Management

map when thresholds are exceeded and should

subsequently be able to inform Network Operations

Center (NOC) and notify concerned authority using

different methods such as pagers, emails, etc.

8 It should be able to automatically generate a

notification in the event of a link failure to ensure

proper handling of link related issues.

9 The Systems and Distributed Monitoring (Operating

Systems) of EMS should be able to monitor:

Processors: Each processor in the system should be monitored for CPU utilization. Current utilization should be compared against user-specified warning and critical thresholds.

File Systems: Each file system should be monitored for the amount of file system space used, which is compared to user-defined warning and critical thresholds.

Log Files: Logs should be monitored to detect faults in the operating system, the




communication subsystem and in applications. The function should also analyze the files residing on the host for specified string patterns.

System Processes: The System Management function should provide real-time collection of data from all system processes. This should identify whether or not an important process has stopped unexpectedly. Critical processes should be automatically restarted using the System Management function.

Memory: The System Management function should monitor memory utilization and available swap space.

Event Log: User-defined events in the security, system, and application event logs must be monitored.

SLA Monitoring Compliance (Y/N)

1 The SLA Monitoring function of the EMS is by far the

most important requirement of the DC/DR Project. The

SLA Monitoring component of EMS will have to

possess the following capabilities

2 EMS should integrate with the application software

component of portal software that measures

performance of system against the following SLA

parameters:

Response times of Portal; Uptime of data centre; Meantime for restoration of Data Centre etc;

3 EMS should compile the performance statistics from all

the IT systems involved and compute the average of

the parameters over a quarter, and compare it with the

SLA metrics laid down in the RFP.

4 The EMS should compute the weighted average score

of the SLA metrics and arrive at the quarterly service

charges payable to the Agency after applying the

system of penalties and rewards.

5 The SLA monitoring component of the EMS should be

under the control of the authority that is nominated to

the mutual agreement of Director, the partner so as to

ensure that it is in a trusted environment.




Reporting Compliance (Y/N)

1 The Reporting and Analysis tool should provide a

ready-to-use view into the wealth of data gathered by

Management system and service management tools. It

should consolidate data from all the relevant modules

and transform it into easily accessible business-relevant

information. This information, should be presented in a

variety of graphical formats can be viewed

interactively

2 The tool should allow customers to explore the real-

time data in a variety of methods and patterns and then

produce reports to analyze the associated business and

service affecting issues.

3 The presentation of reports should be in an easy to

analyze graphical form enabling the administrator to

put up easily summarized reports to the management

for quick action (Customizable Reports). The software

should be capable of supporting the needs to custom

make some of the reports as per the needs of the

organization.

4 Provide Historical Data Analysis: The software should

be able to provide a time snapshot of the required

information as well as the period analysis of the same

in order to help in projecting the demand for

bandwidth in the future.

ITILv3 based Helpdesk Compliance (Y/N)

1 Helpdesk system would automatically generate the

incident tickets and log the call. Such calls are

forwarded to the desired system support personnel

deputed by the Implementation Agency. These

personnel would look into the problem, diagnose and

isolate such faults and resolve the issues timely. The

helpdesk system would be having necessary workflow

for transparent, smoother and cordial DC/DR support

framework.

2 The Helpdesk system should provide flexibility of

logging incident manually via windows GUI and web




interface.

3 The web interface console of the incident tracking

system would allow viewing, updating and closing of

incident tickets.

4 The trouble-ticket should be generated for each

complaint and given to asset owner immediately as

well as part of email.

5 Helpdesk system should allow detailed multiple

levels/tiers of categorization on the type of security

incident being logged.

6 It should provide classification to differentiate the

criticality of the security incident via the priority levels,

severity levels and impact levels.

7 It should allow SLA to be associated with a ticket based

on priority, severity, incident type, requestor, asset,

location or group individually as well as collectively.

8 It should maintain the SLA for each item/service. The

system should be able to generate report on the SLA

violation or regular SLA compliance levels.

9 It should be possible to sort requests based on how

close are the requests to violate their defined SLA‗s.

10 It should support multiple time zones and work shifts

for SLA & automatic ticket assignment.

11 It should allow the helpdesk administrator to define

escalation policy, with multiple levels & notification,

through easy to use window GUI / console.

12 System should provide a knowledge base to store

history of useful incident resolution.

13 It should have an updateable knowledge base for

technical analysis and further help end-users to search

solutions for previously solved issues.

14 The web-based knowledge tool would allow users to

access his / her knowledge article for quick references.




15 It should provide functionality to add / remove a

knowledge base solution based on prior approval from

the concerned authorities

16 Provide seamless integration to generate

events/incident automatically from NMS /EMS.

17 Each incident could be able to associate multiple

activity logs entries manually or automatically events /

incidents from other security tools or EMS / NMS.

18 Allow categorization on the type of incident being

logged.

19 Provide audit logs and reports to track the updating of

each incident ticket.

20 Proposed incident tracking system would be ITILv3

compliant.

21 It should be possible to do any customizations or

policy updates in flash with zero or very minimal

coding or down time.

22 It should integrate with Enterprise Management

System event management and support automatic

problem registration, based on predefined policies.

23 It should be able to log and escalate user interactions

and requests.

24 It should support tracking of SLA (service level

agreements) for call requests within the help desk

through service types.

25 It should be capable of assigning call requests to

technical staff manually as well as automatically based

on predefined rules, and should support notification

and escalation over email, web etc.

26 It should provide status of registered calls to end-users

over email and through web.

27 The solution should provide web based administration

so that the same can be performed from anywhere.




28 It should have a customized Management Dashboard

for senior executives with live reports from helpdesk

database.

Desktop Management Compliance (Y/N)

1 The proposed desktop management system should

provide single integrated agent for asset management,

remote software delivery and remote desktop control.

Asset Management System Compliance (Y/N)

2 The proposed Asset Management solution must

provide inventory of hardware and software

applications on end-user desktops including

information on processor, memory, operating system,

mouse, key board of desktops etc. through agents

installed on them.

3 The proposed Asset Management solution must have

reporting capabilities; provide predefined reports and

the possibility to create customized reports on data in

the inventory database. Report results could be

displayed as lists or graphs.


the capability to export the reports to CSV, HTML and

XML format.


provide the facility for user defined templates to collect

custom information from desktops.


provide facility to recognize custom applications on

desktops.


support administrators to register a new application to

the detectable application list using certain

identification criteria‘s (Like executable, Date/time

stamp etc.). The new application must be detected

automatically from next time the inventory is scanned.


provide facility for queries and automated policies to




be set up and permit scheduling of collecting engines

to pick up the data at defined intervals.

9 The proposed Asset Management solution must be able



integrate with the helpdesk solution and allow ticket

creation automatically on an event defined in asset

management solution. It should also allow manual

ticket creation also.


support Software metering to audit and control

software usage where launching of an application can

be prevented based on centrally configured number of

licenses for an application.






installed on them.







the capability to export the reports to CSV, HTML and

XML format.


provide the facility for user defined templates to collect

custom information from desktops.


provide facility to recognize custom applications on

desktops.


support administrators to register a new application to




the detectable application list using certain

identification criteria‘s (Like executable, Date/time

stamp etc.). The new application must be detected

automatically from next time the inventory is scanned.


provide facility for queries and automated policies to

be set up and permit scheduling of collecting engines

to pick up the data at defined intervals.

19 The proposed Asset Management solution must be able



integrate with the helpdesk solution and allow ticket

creation automatically on an event defined in asset

management solution. It should also allow manual

ticket creation also.


support Software metering to audit and control

software usage where launching of an application can

be prevented based on centrally configured number of

licenses for an application.






installed on them.






NOTE: EMS tools deployed shall have the ability to manage the entire IT infrastructure proposed

by the SI



2. Production CAS (State) Application Services related servers (Web, Portal, Application,

Database, Directory, etc…)

Blade Chassis Specification

Single blade chassis should accommodate minimum 6 (Quad core Processor) / 8 (Dual

core Processor) or higher hot pluggable blades.

Processor should be latest series/generation for the server model being quoted

6U to 12U Rack-mountable

Dual network connectivity for each blade server for redundancy should be provided.

Backplane should be completely passive device. If it is active, dual backplane should be

provided for redundancy

Should accommodate Intel, AMD, RISC / EPIC Processor based Blade Servers for future

applications

Should have the capability for installing industry standard flavours of Windows, Linux,

Unix, Solaris for x86 Operating Environments

Single console for all blades in the enclosure or KVM Module

DVD ROM can be internal or external, which can be shared by all the blades allowing

remote installation of S/W and OS

Minimum 2 external USB connections functionality

Two hot-plug, redundant 1Gbps Ethernet module with minimum 10 ports (cumulative),

which enable connectivity to Ethernet via switch. Switch should be (Internal/external)

having Layer 3 functionality - routing, filtering, traffic queuing etc

Two hot-plugs, redundant 4 Gbps Fiber Channel for connectivity to the external Fiber

channel Switch and ultimately to the storage device.

Power Supplies

o Hot Swap redundant power supplies to be provided

o Power supplies should have N+N. All Power Supplies modules should be

populated in the chassis

Hot Swappable and redundant Cooling Unit

Management

o Systems Management and deployment tools to aid in Blade Server configuration

and OS deployment,

o Remote management capabilities through internet browser

o It should provide Secure Sockets Layer (SSL) 128 bit encryption and Secure Shell

(SSH) Version 2 and support VPN for secure access over internet.

o Ability to measure power historically for servers or group of servers for

optimum power usage

o Blade enclosure should have provision to connect to display console / central

console for local management like trouble shooting, configuration, system status

/ health display

Built in KVM switch or Virtual KVM feature over IP.

Dedicated management network port should have separate path for management



Support heterogeneous environment: AMD, Xeon and RISC/EPIC CPU blades must be in

same chassis with scope to run Win2003/2008 Server, Red Hat Linux / 64 Bit UNIX,

Suse Linux / 64 Bit UNIX / Solaris x86

1. Technical Specifications of servers for Data Center & Disaster Recovery Center

Specification of Blades Enclosure

Feature Specifications Compliance (Y/N)

Form Factor

Up-to 10 U Form factor per chassis with all

redundancy features (Hard Drives, Power, and

Cable Management). The requisite number of

Enclosures to be configured to populate the

Servers and Storage/Expansion Units

Blade Bays Blade Chassis to accommodate minimum of 8 hot

pluggable blade servers with SAS HDDs.

Chassis Feature 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 have the capability for installing

industry standard flavors of Windows,

Linux, Unix, Solaris for x86 Operating

Environments

Single console for all blades in the

enclosure or KVM Module

DVD ROM can be internal or external,

which can be shared by all the blades

allowing remote installation of S/W and

OS

Minimum 2 external USB connections

functionality

Ethernet Switch

Modules

Two hot-plug, redundant 1Gbps Ethernet module

which enable connectivity to Ethernet via switch.

Switch should be Internal/external. The number

of Ethernet ports should be sufficient to connect

fully populated chassis being offered to network.

SAN Connectivity Two hot-plugs, redundant 4 Gbps Fiber Channel

for connectivity to the external Fiber channel

Switch and ultimately to the storage device.

Redundancy Mechanical Devices such as Hard Disks, Fans and

Power Units should be completely Hot Swappable



and Redundant to ensure High Availability

Blade

Management

Systems Management and deployment

tools to aid in Blade Server configuration

and OS deployment,

Remote management capabilities through

internet browser

It should provide Secure Sockets Layer

(SSL) 128 bit encryption and Secure Shell

(SSH) Version 2 and support VPN for

secure access over internet.

Ability to measure power historically for

servers or group of servers for optimum

power usage

Blade enclosure should have provision to

connect to display console / central

console for local management like trouble

shooting, configuration, system status /

health display

Power Hot Swap redundant power supplies to be

provided

Power supplies should have N+N. All

Power Supplies modules should be

populated in the chassis

KVM To be enabled Virtually over IP for Remote Access

or Provided Locally.

Specifications for Database Servers

Features Specifications Required Compliance (Y/N)

CPU X86 based Processor, Minimum 2.6 GHz.

Processor, should be latest series/generation,, 2

CPU socket fully loaded

Chipset Suitable Processor OEM motherboard/chipset

Form factor Half/Full Height Blade with I/O connectivity to

backplane

Memory 64GB DDR3 scalable to 128 GB

Clustering Should have Cluster support for high availability

NIC Dual 10/100/1000 NIC in failover mode

SCSI Controllers Dual Port Serial Attached SCSI controller on board




with RAID 0 & 1 capability

Bays Dual 2.5” SAS Hard Disk bays

Hard Disk Drives 300 GB 2.5” SAS Hard Disk Drive hot swappable

system disk with mirroring using integrated RAID

0,1 on internal disks

Ethernet Adapter Dual Port 1000BASE-T Gigabit Ethernet Adapter

SAN Connectivity The Blade should have redundant 4 Gbps Fiber

Channel HBA (For Application, Directory and Mail

Messaging)

I/O Expansions I/O expansion slot for up gradation of Ethernet

Adapter

Power Supply Redundant Power supply

System

Management and

Diagnostics

LED lights indicating failing component and on-

board diagnostics (via on-board system

management processor)

Software Server Management software with the device

drivers

OS Compatibility MS Windows Server 2008 (Enterprise and Std.

Ed.), Solaris for x86 Latest Edition, Red hat

Enterprise Linux Latest Edition

Back Up Device Should be able to connect with SAN Storage over

4/8 Gbps Fiber channel.

Security The server should have fips certified card based

hardware security module to perform

cryptography operations.



Specifications for Other Servers


CPU X86 based Processor. The Frequency should be

minimum 2.5 GHz or more. Processor should be

latest series/generation for the server model

being quoted

Chipset Suitable Processor OEM motherboard/chipset

Form factor Half/Full Height Blade with I/O connectivity to

backplane

Memory 64GB DDR3 scalable to 128 GB

SCSI Controllers Dual Port Serial Attached SCSI controller on board

with RAID 0 & 1 capability

Bays Dual 2.5” SAS Hard Disk bays

Hard Disk Drives Two 146 GB 2.5” SAS Hard Disk Drive hot

swappable system disk with mirroring using

integrated RAID 0,1 on internal disks

Ethernet Adapter Dual Port 1000BASE-T Gigabit Ethernet Adapter

SAN Connectivity The Blade should have redundant 4 Gbps Fiber

Channel HBA (For Application, Directory and Mail

Messaging)

I/O Expansions I/O expansion slot for up gradation of Ethernet

Adapter

Power Supply From the Blade Chassis

System

Management and

Diagnostics

LED lights indicating failing component and on-

board diagnostics (via on-board system

management processor)

Software Server Management software with the device

drivers

OS Compatibility MS Windows Server 2008 (Enterprise and Std.

Ed.), Solaris for x86 Latest Edition, Red hat

Enterprise Linux Latest Edition



2. Specification of Storage Area Network for DC and DR

Specification of SAN Storage Box

Sr. No. Storage

Parameter

Functionality Compliance (Y/N)

1 Operating System

& Clustering

Support

The storage array should support

industry-leading Operating System

platforms including: Windows Server

2003, 2008, Vmware, Sun Solaris, HP-

UX, IBM-AIX and Linux

Offered Storage Shall support all above

operating systems in Clustering.

2 Capacity &

Scalability

The Storage Array shall be offered with

10 TB Usable space after Raid

Implementation

Storage shall be scalable to 25 TB after

Raid Implementation

3 Processing Power Offered controllers shall be based on latest

PCI-e technology to ensure that there is no

bottleneck for IO communication.

4 Architecture &

Processing Power

The storage array should support dual,

redundant, hot-pluggable, active-active

array controllers

Storage Array shall have Switched

Architecture for Disk drive connectivity.

Controllers shall be true active-active so

that a single Logical unit can be shared

by both controllers at the same time.

5 No Single point of

Failure

Offered Storage Array shall be

configurable in a No Single Point of

configuration including Array Controller

card, Cache memory, FAN, Power supply

etc. It should have Redundant power

supplies, batteries and cooling fans and

data path and storage controller.

6 Disk Drive

Support

Offered Storage Array shall support 4Gbps

dual-ported 146/ 300 / 400 / 450GB /

600GB hot-pluggable Enterprise SAS hard

drives



Sr. No. Storage

Parameter


7 Cache Offered Storage Array shall be given

with Minimum of 4GB cache

Cache shall be mirrored using dedicated

PCI-express bus and shall not use Disk

data path

Cache shall be dynamically managed for

Read and Write operations

Shall have dynamic management of

Cache block size

Cache shall not have any overhead for

the operating system.

8 Raid Support Offered Storage Subsystem shall

support Raid 0, 1, 1+0, 5 and Raid 6

Offered Storage subsystem controllers

shall have capability to create a single

volume of more than 24TB

9 Data Protection The storage array must have complete

cache protection mechanism either by

destaging data or providing complete

cache data protection with battery

backup for up to 72 hours or more.

10 Host Ports &

Back-end Ports

Offered Storage shall have minimum of 4

host ports for connectivity to servers &

minimum of 2 device ports for Disk shelf

connectivity

11 Ports Bandwidth Offered storage shall be end to end 4Gbps

where each drive and drive shelf shall be

connected through dual active-active

paths.

12 Global Hot Spare Offered Storage Array shall support

distributed Global hot Spare for offered

Disk drives

At least 2 Global hot spare drives shall

be configured for every 50 drives.

13 Performance Offered Storage subsystem shall

support more than 1,00,000 IOPS

Shall have capability to use more than

30 drives per array group or raid group

for better performance

Shall support more than 800MB/sec

sequential throughput.



Sr. No. Storage

Parameter


14 Load Balancing &

Multi-path

Multi-path and load balancing software

shall be provided,

15 Maintenance Offered storage shall support online non-

disruptive firmware upgrade for both

Controller and disk drives.

16 Re-build time For better re-build times in case of disk

failure, offered storage rebuild operations

shall not depends upon the number of

drives in the raid group.

17 Business Copy Shall support Snapshot,

18 Storage Array

Configuration &

Management

Software

Vendor shall provide Storage Array

configuration and Management

software

Software shall be able to manage more

than one array of same family

19 Performance

Management

Vendor shall also offer the performance

management software for Storage Array

20 Remote

Replication

Storage shall support both Synchronous

and Asynchronous replication at

controller level

Shall support replication across all

models of the offered family



Specification of SAN Switch

Sr.

No.

SAN Switch

Parameter


1 Capacity SAN switch shall be configured with

minimum of 16 Ports .

2 Throughput Should deliver 8 Gbit/Sec Non-

blocking architecture with 1:1

performance for up to 24 ports

3 Auto sensing

Should protect existing device

investments with auto-sensing 1, 2,

4, and 8 Gbit/sec capabilities

4 Form Factor The switch should be rack

mountable

5 Upgrade Non disruptive Microcode/

firmware Upgrades

6 Bandwidth The switch shall provide Aggregate

bandwidth of 192 Gbit/sec: 24 ports

× 8 Gbit/sec (data rate) end to end.

7 Management Switch shall have support for web

based management and should also

support CLI.

8 Interface The switch should have USB port for

firmware download, support save,

and configuration

upload/download.

i. Server Load Balancer

10/100/1000Mbps Ethernet Ports – minimum 2 ports upgradeable to 4 ports

Memory: Minimum 1 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

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 o Command Line

3. Specification of Automated Tape Library

Sr. No. Tape Library

Parameter


1 Capacity Shall support Native data capacity

of 36TB (uncompressed)

expandable to 72TB

(2:1compressed)

Shall be offered with 24 Cartridge

slots.

2 Tape Drive

Architecture

Offered LTO5 drive in the Library

shall conform to the Continuous and

Data rate matching technique for

higher reliability.

3 Speed Offered LTO5 drive shall support

140MB/sec in Native mode and



Unified Threat Management Device

UTM security appliances should offer unified threat management solutions to secure the

network, including security protections, updates and management and hardware warranty. It

should have Integrated UTM management & the ability to centrally manage multiple Devices

from a single console.

The proposed UTM solution should be able to provide the following functionalities:

Firewall

IPSEC VPN

Identity Awareness

IPS

URL Filtering

Antivirus & Anti-Malware

Anti-Spam & Email Security

Web Security

UTM device should meet the following specification:

Ports Minimum of 4* 10/100/1000

Firewall Throughput Minimum 4.5 GBPs

VPN Throughput Minimum 300 Mbps

280MB/sec in 2:1 Compressed mode

4 Scalability Tape Library shall support scalability

for more than 4 Number of LTO-5 and

120 slots either within the same

frame or by cascading another frame

6 Connectivity Offered Tape Library shall provide

8Gbps native FC connectivity to SAN

switches.

7 Management Tape Library shall provide web based

remote management.

8 Barcode Reader

and Mail slots

Tape library shall support Barcode

reader and mail slot.

9 Other Features Tape Library shall have GUI Panel

Shall be rack mountable

Minimum 10 cartridges to be

provided with barcode labels.

http://www.checkpoint.com/products/identity-awareness-software-blade/

http://www.checkpoint.com/products/softwareblades/intrusion-prevention-system.html

http://www.checkpoint.com/products/softwareblades/url-filtering.html

http://www.checkpoint.com/products/softwareblades/antivirus-anti-malware.html

http://www.checkpoint.com/products/softwareblades/anti-spam-email-security.html

http://www.checkpoint.com/products/softwareblades/web-security.html



Concurrent Sessions Minimum 500,000

IPS Throughput Minimum 500mbps

Licensed Users Unlimited

VLANs Minimum 1024

Storage Minimum 60 GB

Enclosure 1U

Specification of Layer 2 switch

Features Specifications

No of Switch Ports 16

MAC Address Table Size 8K

SwitchFabric 32Gbps Forwarding Capacity

Transmission Method Store-and-Forward

Diagnostic LEDs Per Unit: Power

Per Port: Activity/Link, Speed

Packet Buffer Memory 340KBytes Buffer Memory per Device

QoS 802.1p (4 Queues)

Interface Options

RJ-45 10BASE-T, 100BASE-TX, AND 1000BASE-T

Network Protocols and Standards

IEEE 802.3 Ethernet, 802.3u Fast Ethernet, 802.3x Flow

Control, 802.3ab Gigabit Ethernet, 802.1p QoS, 802.1w,

802.1D, 802.1as, 802.1x,

TECHNICAL SPECIFICATIONS OF HSM FOR PKI SECURITY AND ENCRYPTION

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 applications at Data Center 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 Crime & Criminals Tracking

Network and Systems Significantly. It should be able to enhance the performance of the complete



system by offloading the complete cryptography process to a dedicated appliance. Digital Certificates

in addition to the HSM appliance may be used for further enhancing the security and integrity of the

information.

Should support Windows 2000,2003,2008,Linux,Solaris,HP-UX 11i,VMWARE,AIX 5.3

Should comply to standards like FIPS 140-2 Level-3, CC EAL4+,ROHS,FCC part 15 Class B

Signing speed : 5000 S/S

Remote PED Support for Authentication

Onboard key generation, Digital Signing & Verification process to be done inside the HSM

only for better performance and security

HSM should be integrated with the applications running inside the Data Center

Complete hardware based storage of key material for entire Life cycle

TECHNICAL SPECIFICATIONS of Passive Networking Components

CAT-6 U/UTP Cable

4 Pair Cable, 23 AWG Copper with integral cross -member pair separator for uniform

characteristic impedance.

Standardization: ISO/IEC 11801 2nd Ed.; IEC 61156-5 2nd Ed.; EN 50173-1; EN 50288-

6-1; EIA/TIA 568B.2.1

Cable overall diameter 6.3 mm.

Cable jacket material : PVC

Should have tensile strength of 100N.

The cable should have 100ohm impedance and data transmission frequencies up to

250MHz.

It should be certified by independent test labs like 3P/Delta to meet Cat -6 Standards.

The cable should be supplied in 500m reel.

Mechanical Test

Ultimate Breaking Strength >400 N (90 lbf)

Minimum Bend Radius ≥35mm without load, ≥55mm with load

Electrical Test

DC Resistance ≤14.5Ω/100 m



DC Resistance Unbalance ≤2%

Mutual Capacitance 4.4pF/100m max.

Capacitance Unbalance ≤150pF/100m max.

Propagation Velocity 67%

Connection Module/Information Outlet

RJ45 connection module of Category 6, for the establishing of transmission channels of

class E with up to 4 plugged connections, complies with Category 6 requirements of the

standards ISO/IEC 11801:2002, EN 50173-1: May 2007, DIN EN 50173-1: Dec. 2007 as

well as ANSI/TIA/EIA 568-B.2-1, de-embedded tested in acc. with IEC 60603-7-4,

interoperable and backwards compatible with Cat.5e and Cat.5.

Suitable for 10GBase-T applications in acc. with IEEE 802.3an up to 500 MHz and 55 m.

Parallel pair termination without crossover in acc. with EIA/TIA 568-A/B, gold-plated

bronze contacts for >1000 mating cycles, IDC contacts with single-wire strain relief and

>20 insertion cycles, contact resistance <50 m Ohm, dielectric strength >1000 Veff..

Maximum reliability through special contact design without internal transfer points.

Should have integral dust cover and integrated bend-limiting strain -relief unit for cable

entry.

Should have IDC to hold conductor without using any tool for termination of cable.

Outlets should be of single metal piece design without any PCB to support the IDC /

Contacts.

Should be reusable and tool less in design in terms of termination of solid wire

installation cable AWG22-24 as well as stranded cables AWG 22/7 – 26/7

Should be made of halogen free material and should be certified by third party like 3P or

Delta or GHMT.

Patch Panel 24 port- Straight

Patch panel with integrated cable tie shelf, 19" fastening kit, labeling field, accepting the

snap-in type color coding clips in 8 colors.

Material: sub-rack made of sheet steel (DC01A) 1.5 mm, color blue chromatized, screen

made of plastic (ABS), halogen-free, color medium gray (NCS 2502-B)

Complies with Category 6 requirements of the standards ISO/IEC 11801:2002, EN

50173-1: May 2007, DIN-EN 50173-1: Dec. 2007 as well as ANSI/TIA/EIA 568-B.2-1, de-

embedded tested in acc. with IEC 60603-7-4, interoperable and backwards compatible

with Cat.5e and Cat.5.



Suitable for 10GBase-T applications in acc. with IEEE 802.3an up to 500 MHz and 55 m

in case of unshielded.

Each port should be individually terminated i.e. each Port should be individually

replaceable & provide consistent port-to-port performance.

Each port should have an integral dust cover and integrated bend-limiting strain relief

unit for cable entry.

Patch panels shall be modular in design and capable of supporting Cat 6 UTP/FTP and

S/FTP modules on same port. The same panel should have the capability of terminating

multimode and single mode fibers alongside the copper terminations.

Patch Cord UTP

Standardization: Compliant with Cat.6, Class E (250 MHz) requirements: ISO/IEC

11801 2nd Edition Compliant with Cat.6 component standards IEC 60603-7-4 and

60603-7-5

Patch Cords should have PVC jacket with conductor diameter copper strand AWG26.

Patch cords to use IDC contact technology for all the conductor terminations for better

performance and not piercing type contact technology.

Cat 6 patch cord plug to have metal screening & round cable holder and strain relief boot

to avoid bending.

Plug to have two physically separated levels and all 8 wires need to be separated by

dielectrically.

Should support optional locking mechanism for security purpose wherein the patch

cords can be locked on servers and all RJ45 ports and required Mechanical key to open

patch Cord.

All the conductors should be IDC based termination at the RJ-45 plugs without directly

crimping the plug on cable.



Annexure 14 – Technical Specification of Software for DC and DR

Specification of EMS Software

Bidder should provide a centralized Enterprise Management solution for all the IT

assets spread across various units.

The offered solution should be from a single vendor/product family so as to ensure

the integration and high level of data exchange between various layers and based

on an Internationally recognized industry standard Enterprise Management

Software (EMS) and shall be required to have full capabilities to provide unified

Fault, Performance and Service level management and reporting.

The Solution is expected to be based on SNMP and TCP/IP standards permitting

Network layer level Management of alarm and event s on the same platform.

Fault Management

Should be able to get fault information in real time and present the same in alarm

window with description, affected component, time stamp etc.

Should be able to get fault information from heterogeneous devices — routers,

switches, servers etc.

Event related to servers should go to a common enterprise event console where a

set of automated tasks can be defined based on the policy.

Should have ability to correlate events across the entire infrastructure components

of DC/DR.

Should support automatic event correlation in order to reduce events occurring in

DC/DR.

Should support advanced filtering to eliminate extraneous data / alarms in Web

browser and GUI.

Should be configurable to suppress events for key systems/devices that are down

for routine maintenance or planned outage.

Should be able to monitor on user-defined thresholds for warning/ critical states

and escalate events to event console of enterprise management system.

Should provide out of the box root cause analysis with multiple root cause

algorithms inbuilt for root cause analysis.

Should have self-certification capabilities so that it can easily add support for new

traps and automatically generate alarms.

Should provide sufficient reports pertaining to availability of critical network

resources as well as network response times for critical links.



Should provide the following reports for troubleshooting, diagnosis, analysis and

resolution purposes: Trend Reports, At-A-Glance Reports, & capacity prediction

reports

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

Discovery

Should provide accurate discovery of layer 3 and heterogeneous layer 2 switched

networks for Ethernet, LAN and Servers etc.

HELPDESK MANAGEMENT

It should be integrated with Fault Management Solution.

It should support automatic problem registration with respect to EMS event

management, based on predefined policies.

It should be able to log and escalate user interactions and requests.

It should provide status of registered calls to end -users over email and through

web.

It should have an updateable knowledge base for technical analysis and further

help end-users to search solutions for previously solved issues.

It should have the ability to track work history of calls to facilitate troubleshooting.

It should support tracking of SLA (service level agreements) for call requests

within the helpdesk through service types.

It should support request management and change order management.

It should be capable of assigning call requests to technical staff manually as well as

automatically.

It should be able to provide reports.

The service desk should be from the same product family/suite/OEM as the EMS

and should be compliant with ITIL standards.



3. Personal Computer for each of the police stations:

Features Specifications Compliance (Y/N)

Processor Intel Core i3 or i5 – 650 processor (3.20

GHz) with Q57 Chipset or higher

Motherboard OEM mother board

Bus Architecture

Integrated Graphics, Integrated (on board)

High Definition Audio controller with

internal speaker, 2 PCI slats

Bays 2x Internal 3.5” bays, 2xExternal 5.25”

bays & 2xExternal 3.5” bays

Memory 3 GB DDR3 SDRAM Expandable to 4 GB

Hard Drive 320 GB SATA-II.

Removable drive DVD ROM drive

Network Integrated 10/100 Mbps Ethernet Adapter

(RJ-45), PXE support

Key board Standard USB keyboard

Mouse 2 button optical wheel mouse

Monitor 19” TFT Color Monitor

Interface

1 serial, 1 Parallel, 6 USB (Minimum 2 in

front), 1 PS/2 Keyboard, 1 PS/2 Mouse,

VGA, audio ports for Microphone &

headphones in front.

OS Certification Microsoft Windows

OS Preloaded Windows 7 Business Edition

Antivirus Preloaded Standard Symantec/Macafee

Desktop version with three year update

Warranty 3 years onsite comprehensive warranty support.

Desktop

Certification

FCC and UL certification mandatory, Energy star, TCO, WIN Logo. OEM must possess ISO 9001 and ISO 14001. Need to produce valid FCC part 15 and UL certificate for the particular model/configuration

Security for

Desktop

Removable Media boot control, Serial, Parallel and USB interface control, Power On password, Setup password, FIPS and CC certified hard drive encryption software



with pre-boot authentication

4. Specification for Anti-Virus Solution:

Specifications Compliance (Y/N)

Unified protection - from viruses, spyware, and other

current integrated through one client agent

Simplified administration - through central management

to protect the infrastructure with greater efficiency

Visibility and control - through insightful, prioritized

security reports and a summary dashboard view,

which enable administrator for visibility and control over

malware threats

Infrastructure Integration Capabilities

All Data must be stored Centrally in proposed

Database Server and Reporting should be

Provided

Malware Filtering Capabilities

Should support Integrated anti-

virus/antispyware agent delivering real-time

protection

Should support Static analysis and code

emulation for addressing threats

Should support Event Flood Protection

Should support Integrated and Single foot

printed State Assessment Scans to detect

Vulnerabilities

Should support In-depth scanning of unknown

malware by Dynamic Translation

Manageability

The Solution Should support Centralized

Monitoring of the integrated anti-malware

engine, security state assessment technologies and

policies alerts, and reports

Should support in-built Reporting for Below

Items :

Deployment Status: Number of machines up to

date or not up to date with the latest



signatures

Top issues and issue history: Information about

the top issues in their environment

categorized by type along with the history of issues over

time

Top Threats and threat history: List of top

threats, their severity and number of machines

impacted. Should provide info on current status

and trends

Top vulnerabilities and vulnerability history:

Through security state assessment checks, admin

should be able to see the top vulnerabilities as

well as history of vulnerabilities over time. The

admin should also be alert to measure the

security risk profile based on security best

practices

Top alerts and alert history: Should support

Information about the key alerts impacting

their environment (with the ability to drill down into

more information), along with the history of alerts over

time

It should be capable of providing customized

alerts based on incidents and assets

5. Laser Jet Printer


Print speed Up to 14 ppm A4 &letter

Resolution upto 600 x 600 dpi

Printing Features Manual duplex printing

N-up printing,

Economic mode for toner

savings

Memory 2 MB RAM

Paper Handling Tray 150-sheet adjustable main

input tray,

100-sheet output bin,

manual two-sided printing

Paper Size A4,

A5,



A6,

B5,

letter,

legal,

postcards,

envelopes

Interfaces Hi-Speed USB 2.0 port,

operating systems support

Required

Windows, Linux

6. Printer, Scanner, Copier all in one Device


Print speed Up to 27 ppm letter

Resolution Printing: upto 1200 x 1200 dpi

Copying: up to 600 x 600 dpi

Scanning: up to 1200 x 1200

dpi

Printing Features Manual duplex and booklet

printing

Collation,

Watermarks,

Copying Features 1 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

Scanning Features Flatbed scanner up to letter, A4

size;

supported file types: JPEG,

TIFF, PDF, GIF, and BMP

Should be able to scan Legal

Documents

Control panel 2-line LCD text display,

Asian character support,

16-character display,

Memory 32 MB RAM

Paper Handling Tray 10-sheet priority input tray,

250-sheet multipurpose input

tray,

125-sheet output bin,

manual two-sided printing

Paper Size 76 x 127 mm (3 x 5 inches) to

216 x 356 mm (8.5 x 14

inches);

letter,

legal,



index cards,

postcards;

A4,

A5

Interfaces Hi-Speed USB 2.0 port,

Ethernet port

operating systems support

Required

Windows, Linux

7. Specification of Layer 2 switch


No of Switch Ports 16

MAC Address Table Size 8K

SwitchFabric 32Gbps Forwarding Capacity

Transmission Method Store-and-Forward

Diagnostic LEDs Per Unit: Power

Per Port: Activity/Link, Speed

Packet Buffer Memory 340KBytes Buffer Memory per Device

QoS 802.1p (4 Queues)

Interface Options

RJ-45 10BASE-T, 100BASE-TX, AND

1000BASE-T

Network Protocols and Standards

IEEE 802.3 Ethernet, 802.3u Fast Ethernet,

802.3x Flow Control, 802.3ab Gigabit

Ethernet, 802.1p QoS, 802.1w, 802.1D,

802.1as, 802.1x,

Specification for Router at Site

Should be modular architecture for scalability and should be a single box configuration

for ease of management with AC power support.

Should have minimum of 128 MB of RAM and 32 MB of Flash Memory and scalable.

Should support high speed WAN deployment requirement performance support up to

160kpps or higher



Interfaces: 2 integrated 10/100 Ethernet ports on board, 1-Port Serial WAN Interface

Card along with V.35 serial DTE cable., 1-Port ISDN WAN Interface Card (dial and leased

line) for backup,

Should be modular architecture for scalability and should be a single box configuration

for ease of management with AC power support.

Should support Voice, Video, Security, Data services concurrently

Should support SNMP v1/v2/v3.

It should support device and system management feature that helps to customize

behavior based on network events as they happen & execute scripts if required

RMON, Syslog and Netflow or equivalent

Should support online diagnostics on hardware components

Should support IPv4 and IPv6 routing protocols and dual stack

Static routes, RIPng

Open Shortest Path First (OSPFv2/v3), ISIS

Border Gateway Protocol (BGPv4), MPLS VPN

Multicast Internet Group Management Protocol (IGMPv3), PIM SM/DM, MLD

8. Digital Pad & Pen


Digital Pad Size 336mm (length) x 245mm (width)

Writing area 210mm x 279mm

Notepad holder 210mm x 300mm

Built-in memory 32MB or more

Memory Slot Secure Digital

Interface USB 1.0/ 2.0

Digital Pen size 13mm x 11.3 mm (diameter)

Digital Page file

format

DHW; DND

OS supported Windows 200/ XP/ Vista

Data

Communication

USB 1.1 standard (also supports USB 2.G

standard), Bluetooth 1.2 standard

Built in battery Rechargeable battery




Continuous

Writing Time

2 hours or longer

Standby time:1 hours (min.) without a gap

Charging Time Approx 2 hours ( from 0% to 100 percent

charge)

Charging

Method

Doc cradle or USB Adapter

Operating

System support

Compatible with Windows XP/ Vista / 7/

Linux/ Sun Solaris

9. Finger print reader


Sensor Type Optoelectronic

Prism Architecture Dual Prism

Size of window 18mm X 22 mm minimum

Glass Thickness 25 mm

Resolution 512 PPI upgrade

Image Grey Scale 256 level Dynamic

Scanning Time 0.01 sec

Distortion Rate 0.1 %

Computer

Interface

USB 2.0, USB powered

Operating

Temperature

0 - 55 O C

Environmental

Humidity

Up to 90%

Optical / Film

Coating

Hygroscopic

Operating System

Support

Compatible with Window XP / Vista / 7

/ Linux/ others

Others Should be of Forensic Grade




Should be PIV (Personal Identification

and Verification) standards compliant

10. Digital Camera


Pixels (min) 12 Megapixel or higher

LCD Monitor

Type TFT

Display Size 2.7 ― or higher

Recording

Format

JPEG

Optical Zoom 4 X or higher

Digital Zoom 8 X or higher

ISO Sensitivity

Setting

Auto / 80 / 100 / 200 / 400 / 800 / 1600 /

High

Recording

Media

SD memory card, SDHC memory card,

SDXC memory card, Multimedia Card

Optical Zoom

During Movie

Recording

Yes

Auto Focus

Range

Approx: (W)=3 cm to infinity, (T)= 80 cm to

infinity

Self Timer Yes

Shooting Modes Auto, Portrait, Landscape, Night Snapshot,

Indoor, Face self-timer, Low Light, Beach,

Underwater, Foliage, Snow, Fireworks,

Long Shutter, Movie, Documents

White Balance Auto / Daylight / Cloudy / Fluorescent/

Incandescent/ Flash

Flash Function Auto/ Red Eye Reduction/Off/Face

detection/noise reduction

USB

Connectivity

Yes (Hi- Speed)




Battery Backup 120 min

Operating

System Support

Compatible with Windows XP/ Vista / 7/

Linux/ Sun Solaris

11. UPS – 2 KVA online UPS (for each police station)

Feature Specification Compliance (Y/N)

Power Rating 2 KVA/ 1.6 kW with 120 min backup

Technology True On-Line Double Conversion

Architecture in rack mount Design

Nominal input voltage

(Vac)

220/230/240 VAC

Input voltage range 160-288 VAC

Operating frequency 50/60 Hz auto sensing

Nominal output voltage 208/220/230/240 VAC

Output voltage

regulation

+/-3% online; +/-3% on battery

mode

Overload capacity Up to 110 % for 2 minute, 111-150%

for 30 sec

Efficiency 85% (On-Line mode) >93% (High

efficiency mode)

Load Crest Factor 3 : 1

LED 3 LEDs indicating UPS status

5 Alarm/Bar Graph indicators

Standard

communication ports

RS232

Optional Slots SNMP, Multiserver card, relay card ,

Modbus card

Form Factor Dual Form Factor – Should be placed

either as Rack mount or Tower.

Height Should not exceed 2U for rack

mount purpose

Battery Type Sealed, lead-acid, maintenance-free



Battery Runtime The system must be capable of

providing 120 minutes of battery

Back-up time.

(Minimum VAH = 1300 VAH for 30

minutes back -up)

Total number of batteries offered

should be clearly mentioned.

Voltage of each battery offered

should be clearly mentioned

Ampere-Hour rating of each battery

offered should be clearly mentioned.

Total Volt-Ampere-Hour rating of the

Battery Bank Offered should be

clearly mentioned.

Battery Replacement Modular, hot-swappable, user-

replaceable

Start-On-Battery Should allow startup of UPS without

utility input

Operating Temperature 0°C - +40°C

Storage Temp Recommended 0°C - +25°C

Altitude < 3000 M

Audible Noise <45 dB battery mode

RoHS Compliance Should be EU RoHS / WEEE

Compliant

Markings CE

Safety EN 50091-1 / equivalent

EMC EN 50091-2 /equivalent

Quality ISO 9001, ISO 14001

12. Generators – 2 KVA Generators

Feature Specification Compliance

(Y/N)

Maximum Output 2400 VA

Rated Output 2100 VA




(Y/N)

Starting System Electric Starter with Built in Battery and charger

Fuel Petrol Start and Kerosene run / LPG

Fuel tank Capacity Kerosene - 15 L, Petrol - 0.75 (for kerosene fuel).

For LPG- depends on size of LPG cylinder used by

customer

Continuous

Running Hours

8 Hours

Features Pilot Lamp and Fuel Gauge

Necessary safety certification from reputed

certifying authority shall be furnished

Silent Type Yes

13. Computer Table:


(Y/N)

Size L 910 x W 610 x H 728 mm

Top Side Size 910 x 610 mm made of 18 mm thick pre

laminated medium density fiber (MDF) board ISI

Marked (IS: 14587-1998). The top shall be firmly

screwed on 25x25x1 mm square tube frame as

shown in figure.

Upper side of laminated board shall be in natural

teak shade while the bottom side shall be

white/cream shade.

Sliding Key Board

Tray

A Sliding key Board tray shall be made of 18mm

pre laminated medium density fiber board of size

725x450 mm. The gap between top and tray shall

be 100mm.

Key board tray shall slide smoothly on sliding

channel duly powder coated having nylon roller

arrangement.




(Y/N)

Storage Shelves for

CVT

A storage shelve made of 18 mm particle board

shall be provided along with the length of the

table at bottom about 100 mm above from the

ground level. Shelves shall be screwed on frame

work of 25x25x1 mm square tube. The shelve shall

be covered from back side with 18mm pre

laminated medium density fiber board as shown

in drawing.

Steel Structure The rigid steel structure shall consist of two nos.

rectangular base tubes of size 50x25x1.25 mm

about 520 mm length placed along the width on

vertical tubes of size 25x25x1 mm shall be welded

for fixing up of side panels. A supporting frame of

25x25x1 mm square tube shall be welded on the

top of the tubes for the side panels as shown for

supporting the top of the table.

The base tube shall be provided with adjustable

shoes 2 nos. on each side.

Painting Complete frame of tubes shall be powder coated.

14. Chair:

Specification Compliance (Y/N)

Seat size shall be 430x430 mm on 10 mm. thick molded comm. ply with 60 mm thick 40 density molded PU foam

Back rest size shall be 400x300 mm on 10 mm thick molded comm. ply with 40 mm thick 32 density molded PU foam covered with tapestry.

The height of back rest shall be 900x500 mm for top and bottom edges respectively. The black rest shall be provided with lifting arrangement on flat iron & helical spring.

Two nos. suitable PU handles shall be provided.

The base stand should be made up of 5 prongs duly pressed welded

together centrally with a pedestal bush with good quality twin wheel

castors. The stand and other metal parts excluding central spindle

shall be powder coated. Complete steel structure shall be pretreated

and powder coated with minimum thickness of 60 microns coating.



Specification Compliance (Y/N)

A central spindle of 25mm dia rod without threads shall be provided

with revolving arrangements. The adjustable height of chair shall be

from 530 to 570 mm.

A good quality tapestry cloth shall be provided on seat & back in

attractive color/ shade.

15. Electric Cabling:

Scope: Scope of Electrical cabling, is to provide power supply for devices installed. System Integrator is responsible for supply, install, testing, commissioning and maintenance of electrical cabling for supplying power to run installed devices at police locations. Specification:

i) Total 5 Electrical Points Including 3 Switches & 3 Sockets in Each Point, (2 No. 5-Amps and 1 No. 15 Amps.) - Point wiring using ISI approved PVC Conduit / Casing Capping, 1.1 KV grade 2.5 square meter FRLS Cu flexible wire including supply of wire, switch, socket and GI Box. Including all necessary hardware & accessories complete, material and labor as per requirement of the A&N Police. For point wiring having Average Point length is12 to 18 Meters.

ii) UPS & Generator Set Cabling: Electrical Cabling for Network Rack, Four Computer

Points, separate cabling for Two Printers from main input and Generator set to UPS Including change-over, MCB and all other accessories as per requirement.

16. Earthing and Earthing Pit

Adequate earthing through underground earth pit should be prepared that prevent causes generated from improper power supply. Separate Copper Plate Earthing (With Plate Size 300X300X3 MM), The Earth resistance should not exceed 2.5 Ohms, and Ground to earth Voltage should not be more than 3 volts. 17. Wall Mounted Network Rack- 9U

Specification Compliance

(Y/N)

19‖ Wall mount, 9 U Height

Minimum Powder quoted steel Body with front door of glass.

Completely covered & have security locks.

Proper ventilated with One Fan, One Cable Manager, Power Distribution

Unit of 6 No. (5 and 5 Amp) Sockets with surge protection, Mounting

Accessories,



Specification Compliance

(Y/N)

Fitted with Copper Strip for earthing the equipments

18. 42 U Rack

Parameter Specification Compliance

(Y/N)

Feature

42U 800W X 800D Modular Structures made from aluminum extruded profile, minimum extrusion wall thickness at all sides and corner- 2mm. along with following items: Top and Base Cover with cable enter Black Colour

Front/Rear Door

Front, Glass door, 800mm Wide, 42U, with Lock and hexagonal vent on the trims for thermal Management/ air cooling. 42U , 800mm W, Rear Steel Door, with 1/3 hexagonal vent at the base to allow proper air flow and thermal control, with Lock

Mounting Angles

19” Mounting Angles, 19” mounting angles powder coated along with “U” marking

SIDE PANELS

2 Nos. of Removable Side Panels along with slam latch. 4 nos. of 100mm W, Reducing Cable channels on the sides to allow better cable management

Castors

Castors - For providing mobility to the rack. Two with foot operated brakes and Two without brakes, having a load carrying capacity of 100kg

Fan

230V AC 90CFM Fan (4 nos. for each Rack) with Fan Housing Unit

Cable Manager

19”, 1U, Horizontal Cable Manager, to allow proper cable routing

Cable Loops

24U to help route the cable vertically

Power Supply

10X 5 amps or 6 X 5 amps socket as per requirement

Castors

Castors as needed

Cable Storage

2U cable storage shelf supported with 4 bobbins



19. CAT 6 Patch Panel


(Y/N)

Type 24 or 12 port patch panel as per requirement, Unshielded Twisted Pair, Category 6, ANSI/TIA/EIA 568- B.2.1

Category Category 6

Circuit

Identification

Scheme

Port Labeling for port identification on each of 24-

ports

Port Identification Labels on each of 24/48-ports (to be included in

supply)

Height 1 U (1.75 inches)

Modular Jack 750 mating cycles

Note: BOM and other necessary applications should comply with IPv6 technology.



Annexure 15 – Service Levels

Indicative Draft of the Service levels is given below. Puducherry, UT Police may add more

service levels / modify the service levels as per actual requirements.

This annexure describes the service levels to be established for the Services offered by the SI to

the UT. The SI shall monitor and maintain the UT service levels to provide quality service to the

UT.

Definitions:

(a) “Availability” means the time for which the services and facilities are available for

conducting operations on the UT system including application and associated infrastructure.

Availability is defined as:

{(Scheduled Operation Time – System Downtime) / (Scheduled Operation Time)} * 100%

(b) “Helpdesk Support” shall mean the 16x6 basis support centre which shall handle Fault

reporting, Trouble Ticketing and related enquiries during this contract.

(c) “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.

(d) “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 UT.

(e) “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.

(f) “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 UT 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.

1. Interpretations.

(a) The business hours are 7:00AM to 11:00PM on all working days (Mon-Sat) excluding Public

Holidays or any other Holidays observed by the UT. The SI however recognizes the fact that the

UT offices will require to work beyond the business hours on need basis.

(b) "Non-Business Hours" shall mean hours excluding “Business Hours”.

(c) 16X7 shall mean hours between 07:00AM -11.00PM midnight on all days of the week.



(d) If the operations at Primary DC are not switched to DRC within the stipulated timeframe

(Recovery Time Objective), it will be added to the system downtime.

(e) The availability for a cluster will be the average of availability computed across all the

servers in a cluster, rather than on individual servers. However, non compliance with

performance parameters for infrastructure and system / service degradation will be considered

for downtime calculation.

(f) The SLA parameters shall be monitored on a monthly basis as per the individual SLA

parameter requirements. However, if the performance of the system/services is degraded

significantly at any given point in time during the contract and if the immediate measures are

not implemented and issues are not rectified to the complete satisfaction of the UT or an agency

designated by them, then the UT 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 UT suggested format and a review shall be conducted based on this report. A monthly

Availability and Performance Report shall be provided to the UT 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 UT upon review and signoff by SPMU and the UT 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 UT. 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 UT and will be performed by the UT or the UT

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 3rd party testing and audit of

the system shall put sufficient emphasis on ensuring the capability of EMS system to capture

SLA compliance correctly and as specified in this RFP. The selected System Integrator (SI) must

deploy EMS tool and develop additional scripts (if required) for capturing the required data for

SLA report generation in automated way. This tool should generate the SLA Monitoring report

in the end of every month which is to be shared with the UT on a monthly basis. The tool should

also be capable of generating SLA reports for a half-year. The UT will audit the tool and the

scripts on a regular basis.

(j) 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 UT decides after taking

the advice of the SI and other agencies. All the changes would be made by the UT in consultation

with the SI.

(k) The SI is expected to provide the following service levels. In case these service levels cannot

be achieved at service levels defined in the tables below, it shall result in a breach of contract



and invoke the penalty clause. Payments to the SI are linked to the compliance with the SLA

metrics laid down in the tables below. The penalties will be computed and calculated as per the

computation explained in this Annexure. During the contract period, it is envisaged that there

could be changes to the SLA, in terms of addition, alteration or deletion of certain parameters,

based on mutual consent of both the parties i.e. the UT and SI.

Following tables outline 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 UT 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

Capacity Building

Service Level Description Measurement

Capacity Building At least 80% of the trainees within the training program should give a rating of satisfactory or above. Severity of Violation: High This service level will be monitored and measured on a per District basis through feedback survey to be provided to each attendee within the program. If the training quality in the program falls below the minimum service level, it will be treated as one (1) violation. The total number of violations for the payment period will be the cumulative number of violations across all the programs across all Districts in the payment period.

Data Migration / Digitization


Data Migration Error rate in a batch should be less than 0.5%. 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 stations / higher offices in the payment period.



Violations and Associated Penalties

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.

Penalty Calculations - The framework for Penalties, as a result of not meeting the Service Level

Targets is as follows:

(i) The performance will be measured for each of the defined service level metric against the

minimum / target service level requirements and the violations will be calculated accordingly.

(ii) The number of violations in the reporting period for each level of severity will be totaled and

used for the calculation of Penalties.

(iii) 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 SLA:

Primary DC/DRC Site Infrastructure Systems and Application Availability and Performance

Production CAS Systems. - The failure or disruption has a direct impact on the UT’s ability to

service its police stations / higher offices, ability to perform critical back-office functions or a

direct impact on the organization.

This includes but not limited to:-

Storage and related switches at Primary DC and DRC.

Web, Application, Database, and Backup Servers at Primary DC and DRC.

Primary DC to DRC connectivity.

Primary DC and DRC network infrastructure.

Primary DC and DRC security infrastructure.

Non-CAS Systems in Production and Non Production Systems (Development, QA, and

Training)

The failure or disruption has no direct impact on the UT’s ability to serve its police stations /

higher offices, or perform critical back-office functions.

This includes but not limited to:

Production Non CAS Servers.

Test, QA and Training Servers.

Helpdesk infrastructure & applications.

EMS Infrastructure.



CAS Solution Components

The failure or disruption has a direct impact on the UT’s ability to service its police stations /

higher offices, ability to perform critical back-office functions or a direct impact on the

organization.

Non ERP Solution Components

The failure or disruption has no direct impact on the UT’s ability to serve its police stations /

higher offices, or perform critical back-office functions.

These service levels will be monitored on a monthly basis.

The below tables gives details on the Service Levels the SI should maintain.


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% and >=98.5% 1

<98.5% and >=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% and >=96.5% 1

<96.5% and >=96% 2

<96% 3


Infrastructure Availability RPO should be < 60 mins Severity of Violation: High Each instance of non-meeting this service level will be treated as two (2) violations.

Infrastructure Availability RPO (zero data loss in case of failure of primary DC) should be zero

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

Violations for calculation of penalty

>0 and <=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.


Sustained period of peak I/O utilization of any server crossing 70% (with the exception of batch processing) shall be less than or equal to 30 minutes. 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.



>0 and <=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.


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



>0 and <=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 The service shall be monitored on a monthly basis


<99.9% & >=99.5% 1

<99.5% & >99% 2

<99% 3


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


<97% & >=96% 1

<96% 3


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 UT during the Supply and System Integration Phase. The service shall 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 turnaround time in any month in the six-month period falls goes beyond 6s, one (1) additional violation will be added for each such month to the overall violations for this service level.



Client Site Infrastructure Systems

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.

This service level will be measured on a monthly basis for each implementation site.

The below tables gives details on the Service Levels the SI should maintain:


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.

Handholding Support: Client Site Support

Level 1 Incidents - The incident has an immediate impact on the UT’s ability to service its

police stations / higher offices, to perform critical back-office functions or has a direct impact on

the organization.

Level 2 Incidents - The incident has an impact on the 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

The severity of the individual incidents will be mutually determined by the UT and SI.

The scheduled operation time for the client site systems shall be the business hours of the UT.

This service level will be measured on a monthly basis for each implementation site.

The tables on the following page give details of the Service Levels the SI is required to maintain:


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


80% of the Level 2 Incidents at each site should be resolved within 6 business hours from the time call is received / logged which ever is earlier. The maximum resolution time for any incident of this nature shall not exceed 48 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


Replacement of hardware equipment shall be done within 7 days of notification by the 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.



Handholding Support: Application Support

Level 1 Defects - The failure to fix has an immediate impact on the UT’s ability to service its

police stations / higher offices, inability to perform critical back-office functions or a direct

impact on the organization.

Level 2 Defects. The failure to fix has an impact on the 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.

Level 3 Defects. The failure to fix has no direct impact on the UT’s ability to serve its police

stations / higher officers, or perform critical back-office functions.

The severity of the individual defects will be mutually determined by the UT and SI.

This service level will be monitored on a monthly basis.



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 This service level will be monitored on a monthly basis.

Performance over the six month period Violations for calculation of penalty

<95% & >=90% 1

<90% & >=85% 2

<85% 3



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.


<95% & >=90% 1

<90% & >=85% 2

<85% 3





100% of the Level 3 defects shall be resolved within 120 hours from the time of reporting full details. Severity of Violation: High This service level will be monitored on a monthly basis.


<100% & >=90% 1

<90% & >=80% 2

<80% 3



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.

2. Network Uptime:




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.



Handholding Support: Helpdesk and Data Center Support

Level 1 Calls - The failure to fix has an immediate impact on the UT’s ability to service its police

stations / higher offices, inability to perform critical back-office functions or a direct impact on

the organization.

Level 2 Calls. The failure to fix has an impact on the 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.

Level 3 Calls. The failure to fix has no direct impact on the UT’s ability to serve its police

stations / higher offices, or perform critical back-office functions.


The below tables gives details on the Service Levels the SI should maintain.


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



Performance over the six month period Violations for

calculation of penalty

<98% & >=90% 1

<90% & >=80% 2

<80% 3

In addition to the above, if the service level in any month in

the six-month period falls below 80%, one (1) additional

violation will be added for each such month to the overall

violations for this service level.

Helpdesk Performance 98% of the incidents within helpdesk resolution capacity shall be resolved

in a cycle time of 24 hours.





<98% & >=90% 1

<90% & >=80% 2

<80% 3





Helpdesk Performance 98% of the non SI supported incidents shall be routed to the appropriate

service provider within 30 minute



Severity of Violation: Medium




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

8 business hours.





<80% & >=70% 1

<70% & >=60% 2

<60% 3





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.





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







<80% & >=70% 1

<70% & >=60% 2

<60% 3





Datacenter Support Performance

Replacement of hardware equipment shall be done within 15

days of notification by the 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)


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

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.

Reporting



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



Credits for Successful Application Uptake

The below tables gives details of the credits that can gained by the SI for successful uptake of the

application in the UT. The credits will not be calculated for the first reporting period.


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


>5 & <=10% 2

>10 & <=15% 3

>15% 4



Service Level Category: Network Infrastructure

a) Network Specific SLAs

a. Uptime SLA

b. MTBF (Mean Time Between Failures) & MTTR (Mean Time to Repair)

c. Latency & Response Time (DNS / DHCP / SMTP etc)

d. Traffic-based SLAs

Service Level Category: Data Center IT Infrastructure

b) System Specific SLAs

a. System Availability

b. System Response Time

c. Utilization based SLAs (CPU / Memory etc.)

c) Application Specific SLAs

a. End-User Based SLAs

i. End-to-End Response Time for End-User Web Pages to Load

ii. Avg. Response Time, Errors Per Interval, Response per Interval

iii. SLAs from Critical Processes (e.g. Submit Button Click, Upload Action in

Portal)

b. Transaction Based SLAs

i. SLAs for Business Process involving with multiple steps / pages

ii. Completion Time SLA for Critical Business Processes

c. Application Deep-Dive SLAs

i. Application Component-Wise SLA within the DC

1. SLA for DB Query to Complete

2. Web Services Call etc.

ii. 3rd Party interaction SLAs between Applications



Service Level Category: End-to-End Service Delivery

d) End-to-End Service Based SLAs

Sample SLA Report for Network / System Availability & Response Time Testing:

Element Name Total

Availability

(%)

Deviation

from Goal

Outage

Start

Outage

End

Duration Remarks

DEL_JAIPUR_LI

NK

98.80 1.1 29/11/20

09

13.30

29/11/200

9

13.37

00.07.00 BSNL

Outage

09/12/20

09

04.10

09/12/200

9

04.14

00.04.00 Router

Down

Some Sample SLA Definitions are given below:

Service SLA Method of

Measurement

Computation

Cycle Penalty

Overall Network

Availability 99% NMS Tool Quarterly

End-to-End Network

Response Time from

remote location

5ms NMS Tool Quarterly

DNS / DHCP / File

Server/ AD etc 99% NMS Tool Yearly



Bandwidth Utilization

(Peak) 80% NMS Tool Yearly

End-User Page Loading

Time for Portal (in EAs

/ CCs)

3s APM Tool Quarterly

Average Response

Time for any

transaction

5s APM Tool Quarterly



Annexure 16 – PSWAN Connectivity

PSWAN NOC

Puducherry

Karaikal

DHQ

Mahe

DHQ

Yanam

DHQ

SSP Office

1Mbps

SP Office

512 Kbps

SP Office

512 Kbps

DGP Office

Dumas ST

2 Mbps

CID Complex

Dumas ST

1 Mbps

Traffic Complex

Nehru Street

512 Kbps

SP South

Pillaithottam

512 Kbps


Annexure 17 – Networking details of Police Station and Other Officers



Note: Softcopy of the Networking details of Police Station and Other Officers will be provided on request

~~~~~~~~~~~~~~~~~~~~~~~~End of the Document~~~~~~~~~~~~~~~~~~~~~~~~~~~~