request for p s ystem i - ncrb.gov.inncrb.gov.in/bureaudivisions/cctnsnew/data/all state...

Crime & Criminals Tracking Network and Systems Project Haryana Police

Government of Haryana Corrigendum to RFP for Selection of System Integrator of 72

E-GOVERNANCE MISSION MODE PROJECT (MMP)

CRIME & CRIMINAL TRACKING NETWORK AND SYSTEMS

(CCTNS)

REQUEST FOR PROPOSAL FOR

SELECTION OF SYSTEM INTEGRATOR

FOR

IMPLEMENTING, COMMISSIONING AND

MAINTAINING CCTNS

IN

HARYANA POLICE

CORRIGENDUM - II

RELEASED BY:

HARYANA POLICE

GOVERNMENT OF HARYANA



TABLE OF CONTENTS

1 REQUEST FOR PROPOSAL REVISED DATASHEET ................................................................. 3

2 RFP VOLUME I ................................................................................................................................... 4

A. 5.3 SCOPE OF WORK SUMMARY AND TIMELINES ............................................................................ 4

B. 5.4 SCOPE OF SERVICES – DURING IMPLEMENTATION ..................................................................... 9

C. ANNEXURE V .................................................................................................................................17

3 RFP VOLUME II ................................................................................................................................52

A. SECTION 7, FORMAT FOR BID RESPONSE – COMMERCIAL BID........................................................52

B. ANNEXURE – OTHER FORMATS ......................................................................................................58

4 ANNEXURE: INDICATIVE LIST OF LOCATIONS AND ADDRESSES ..................................59



11 RREEQQUUEESSTT FFOORR PPRROOPPOOSSAALL RREEVVIISSEEDD DDAATTAASSHHEEEETT

S. No Information Details

1 Last date, Time (deadline) and Venue for

receipt of proposals in response to RFP

notice

21st March 2011 till 2:00 p.m. at the Office

of IGP Telecommunication, Haryana Police

Headquarter, Sector-6, Panchkula

2 Date, Time and Venue of opening of

Technical proposals received in response

to the RFP notice

21st March 2011, 3:00 p.m. at Gazetted

Officers Mess. Police Complex, Moginand,

Panchkula

3 Place, Time and Date of Technical

Presentations by the bidders

To be intimated Later

4 Place, Time and Date of opening of

Financial proposals received in response

to the RFP notice

To be intimated Later

5 Contact Person for queries Sh. Jagdish Chand

DSP/IT, Haryana Police Headquarters,

Sector -6, Panchkula

[email protected]

Ph: 0172 2587900 to 906, Extn. 199 or 151

6 Addressee and Address at which

proposal in response to RFP notice is to

be submitted:

Director General of Police, Haryana

Haryana Police Headquarters,

Sector-6, Panchkula

Table 1: RFP Datasheet

mailto:[email protected]



22 RRFFPP VVOOLLUUMMEE II

A. 5.3 Scope of Work Summary and Timelines

1. Revised Scope of Work Summary and Timelines also reflected is as follows:

S. No. Project Activity Deliverables Timelines (T - from date of signing of contract)

1. Project planning

i. Detailed Project Plan and Management Methodology for effective implementation of the Project

ii. Project Progress Report every fortnightly iii. Risk Management and Mitigation Plan iv. Manpower Deployment Plan v. Periodic reports from PMIS, Configuration Management

and Issue Tracker Tools

T

Study and Design

2.

System Study – study the legislation, business processes and organization design of Haryana Police along with relevant reports such as PIM

vi. A comprehensive System Study document vii. Updated/ vetted FRS report including list of additional

features that would result in further improvement in the overall application performance for consideration of the department

viii. A comparative report on the extent of functionality currently available in the vendor‘s application (CAS provided by Centre) other applications/ COTS products and with the FRS for CRP

ix. Detailed integration and interfacing model x. Change/Reference document including all the changes

or deviations from the base version of the CAS(State)/ FRS of other modules

T + 8 Weeks

3. Detailed assessment of functional requirements and MIS requirements

4. Finalization/ Vetting of FRS

5. Preparation of System Requirement Specification report and Software Requirement Specification report

xi. System Requirement Specification Report and Software Requirement Specification reports meeting all the Business, Functional and technical requirement of Haryana Police and incorporating all the functional




specifications, standards provided by the NCRB, Haryana Police specific requirements and different integration points with CAS (Centre), external agencies and other applications of Haryana Police

xii. List of additional features proposed in complete CCTNS Application

xiii. CAS (State) Implementation document w.r.t. Configuration, Customization, Extension and Integration as per Haryana Police‘s requirements

6. Procurement of IT infrastructure at Data Centre and DR

T + 8 Weeks

7. Preparation of Solution Design documents

A detailed Design document including: xiv. Technical Architecture Document (Application, Network,

and Security) xv. High Level Design (including but not limited to)

a. Application architecture documents b. ER diagrams and other data modelling

documents c. Logical and physical database design d. Data dictionary and data definitions e. Application component design including

component deployment views, control flows, etc.

xvi. Low Level Design (including but not limited to) a. Application flows and logic including pseudo

code b. GUI design (screen design, navigation, etc.) c. Database architecture, including defining data

structure, data dictionary as per standards laid-down by GoI/ GoH

xvii. CCTNS Application Test Plans and Test Cases

T + 10 Weeks

8. Site Survey xviii. A site survey report detailing the current status of each

site and the enhancements to be made at each site (s) based on the State‘s requirement and the guidelines of

T + 10 Weeks




MHA, NCRB

9. IT infrastructure sizing

xix. Final BoM with Technical specifications for the IT Hardware, Network and other IT Infrastructure Requirements

xx. Strategy for Data Centre and DR Site xxi. Report on the reusability of existing infrastructure xxii. Hardware procurement & Deployment plan

T + 11 Weeks

10. Others xxiii. Data Migration Strategy and Methodology T+11 Weeks

11. Commissioning and operationalization of IT infrastructure at Data Centre and DR

T + 11 Weeks

Implement (This shall only begin after CAS (State)1 has been received from NCRB, MHA) – T1

12.

Study and analyze the CAS (State) system as received from NCRB against the requirements of Haryana Police and conduct Conference Room Pilot (CRP) based on the requirement specifications

xxiv. Feedback Report based on CRP I and CRP II

T1 + 4 Weeks

13. Finalization of requirement specifications xxv. Final FRS, SyRS, SRS and other requirements with all

the Solution Design documents T1 + 6 Weeks

14. Configuration & Customization of CAS (State) and development of additional modules

T1 + 14 Weeks

15. Integration with CAS (Centre) T1+ 14 Weeks

16. Data migration and digitization of historical data

T1 + 14 Weeks

17. Migration of CIPA and CCIS Police Stations/ non-CIPA and CCIS Police Stations/ Higher Offices to CCTNS

T1 + 15 Weeks

18. Testing of configured & deployed solution (CAS) and additional functionalities

T1 + 16 Weeks

19. Site preparation at Pilot Phase Client site T1 + 18 Weeks

1 As per the guidelines of CCTNS MMP, Core Application Software (State) would be provided by NCRB.




locations

20. Procurement, Commissioning and Operationalizing the IT infrastructure at Pilot phase Police locations

T1 + 20 Weeks

21. User Acceptance and Testing of Pilot Phase implementation

xxvi. Detailed Testing Plans and Test Cases xxvii. Detailed User Operation Manual

T1 + 20 Weeks

22. User Training on Pilot Phase CCTNS Solution xxviii. Detailed Training Plan, Training Manuals, Training

Content, Training Examination Question Bank, etc. T1 + 22 Weeks

23. Pilot rollout in two districts xxix. Report on amendments / enhancements / modifications

made based on inputs of Haryana Police T1 + 22 Weeks

24. Go-Live of Pilot xxx. Pilot phase Acceptance from Haryana Police xxxi. Pilot phase Go-Live Report including

a. Site Preparation and Infrastructure Deployment / Commissioning Report for Pilot Sites, Data Centre and DR Site

b. Data Migration report for Pilot phase c. Performance and Load Testing Report for Pilot

phase

T1 + 24Weeks

25. Improvement of application according to the experience of Phase I

T1 + 24 Weeks

26. CCTNS Solution customization for Phase II and integrating with external agencies

T1 + 32 Weeks

27. Site preparation at Phase II Client locations T1 + 42 Weeks

28. Procurement, Commissioning and Operationalizing of IT infrastructure at Phase II Client locations

T1 + 42 Weeks

29. Capacity Building and Change Management xxxii. Detailed Change Management, Capacity Building and

Communication Strategy. T1+ 44 Weeks

30. User Training on complete CCTNS Solution xxxiii. Detailed User Operation Manual xxxiv. Detailed Training Plan, Training Manuals, Training

Content, Training Examination Question Bank, etc.

T1 + 44 Weeks

31. State wide rollout of Phase II xxxv. Report on amendments / enhancements / modifications

made based on inputs of Haryana Police / Third Party‘s Acceptance Testing for State-wide Roll-Out

T1 + 45 Weeks

32. 3rd

party Acceptance testing, audit and xxxvi. Third Party Acceptance Testing Certificate T1 + 48 Weeks




certification of complete CCTNS Solution

33. SLA and Performance Monitoring Plan xxxvii. Detailed plan for monitoring of SLAs and performance of

the overall system Before ―Go-Live‖

34. Go-Live for complete CCTNS Solution

xxxviii. Go-Live Acceptance from Haryana Police xxxix. Report on roll-out across State including

a. Site Preparation and Infrastructure Deployment Report across State

b. Manpower Deployment Report c. Data Migration Report including Test Plans and

Test Results for Data Migration d. Training Delivery Report e. Overall Test Report

T1 + 50 Weeks

Post Implementation - Operation and Maintenance

5 Years since the “Go-Live” of Complete CCTNS Solution

1. Handholding support xl. Detailed User Operation Manual xli. Detailed Training Plan, Training Manuals, Training

Content, Training Examination Question Bank, etc.

For next 1 year from ―Go-Live of each of the phases - Pilot and complete CCTNS solution respectively‖

2. Project Operation and Maintenance

xlii. Fortnightly Progress Report on Project including SLA Monitoring Report and Exception Report

xliii. Project Quality Assurance report xliv. Details on all the issues logged

5 Years from the date of “Go-Live” of Complete CCTNS Solution



B. 5.4 Scope of Services – During Implementation

1. 5.4.3.6 Formulation of Test Plans, Para (2),

The Test Plans ….. test cases on the advice of SPMC/ State Mission Team/ SPMU. The selected

System Integrator would create a testing & development environment for the CCTNS integrated

solution to be implemented in Haryana. This would be maintained by the vendor and transferred

to the Department at the end of the contract at no additional cost.

Stands amended as

The Test Plans ….. test cases on the advice of SPMC/ State Mission Team/ SPMU. The selected

System Integrator would create a testing & development environment for the CCTNS integrated

solution to be implemented in Haryana. SI will be responsible for creating and maintaining a

separate Test environment (hardware and software) to enable testing for change requests. The

Development and Testing environments would be created and maintained by the vendor in

District Panchkula at the Haryana Police premises and would be transferred to the Department at

the end of the contract at no additional cost.

2. 5.4.3.7 Application Development and Unit Testing, Footnote (22),

SI shall implement all the suggestions/ changes proposed by Haryana Police without considering

it as part of the Change Control till the completion of one year of Handholding support by SI.

Stands amended as

SI shall implement all the suggestions/ changes proposed by Haryana Police without considering

it as part of the Change Control till the completion of one year of Handholding support by SI.

Haryana Police will not pay any additional amount for changes during the aforementioned period.

However, SI will be required to follow the process of maintaining and tracking all the change

requests received.

3. 5.4.3.7 Application Development and Unit Testing, 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 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

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

Stands amended as



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 Haryana CCTNS

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

4. 5.4.6 Network Connectivity for PS and Higher Offices

Stands amended as

The connectivity2 for the CCTNS project at majority of the Higher Offices will be on Haryana

SWAN and connectivity at all the Police Stations and other Units will be either on SWAN or VPN

over Broadband with 512 Kbps bandwidth. SI will be required to provide VPN over Broadband

connectivity from service providers for the Police Stations or other Units till SWAN is stabilized in

the State; However at some of the Police Stations or Other Units, Haryana Police may also use3

the existing SWAN connectivity, and finally connecting the Police Stations or Other Units (both

VPN over broadband and SWAN) to the State Data Centre where CCTNS solution will be hosted.

SI will ensure termination of the aggregated bandwidth (on Ethernet port) from service provider of

all the VPN over broadband sites directly at SDC. SI will also be responsible for setting up and

maintenance of LAN at the individual offices, wherever required. SI will seek 2 Mbps secure

internet bandwidth (through SDC‘s IPS and Firewall) from SDC to enable access to Citizens

Portal. This Internet bandwidth will also be used for Haryana CCTNS network as an Internet

gateway for enabling internet access if required. SI will also need to coordinate with SDC

operator for implementation of other security policies as and when required.

In addition to the above, SI will be responsible for the last mile connectivity for CCTNS project,

which includes, but not limited to provisioning and maintenance of new connectivity from the

bandwidth providers and liaisoning with the existing SWAN System Integrators. SI shall ensure

connectivity uptime as per SLA from SDC to the Police Stations and Higher Offices. SI shall be

required to provide all the necessary hardware/ software for implementing the aforementioned

network solution for CCTNS project in Haryana Police. SI shall prepare comprehensive network

architecture for connecting all the Police Stations / Higher Offices to the State DC. SI will be

required to liaison and coordinate with existing Haryana SWAN System Integrators as well as the

2 MHA/NCRB centrally are in discussion with BSNL for the provisioning of CCTNS Network

Connectivity and Bandwidth. BSNL will be extending the horizontal connectivity from existing Haryana

SWAN PoPs. Therefore bidders are advised not to enter into a long term contract with service provider for

VPN over Broadband connectivity. 3 Usage of existing SWAN connectivity at Police Station would be decided by Haryana Police as per the

Site survey report prepared by SI.



existing service providers for ensuring seamless connectivity at all locations to meet the SLA. It is

imperative to mention that selected SI would be responsible for successful network connectivity

across the State and SDC.

The connectivity between the State Data Center and Disaster Recovery Center shall be provided

by the State, however SI will be required to commission CCTNS solution and shall maintain all

the hardware/ software provided at SDC and DR Site as part of this project.

State may decide to migrate from VPN over broadband connectivity at Police Stations to SWAN

network whenever Haryana SWAN stabilizes at the said offices, hence SI will be required to carry

out the migration exercise which includes but not limiting to liaisoning with the SWAN SI/ Service

provider and thereafter support for maintenance of the sites migrating from VPN over broadband

to SWAN network.

SI shall be responsible for creating and implementing the required IP scheme for VPN over

broadband network to be established for Police Stations.

5. 5.4.7 IT Infrastructure at the State Data Centre and Disaster Recovery Centre, Para (1),

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

Stands amended as

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.

6. Corrigendum, 5.4.7 IT Infrastructure at the State Data Centre and Disaster Recovery

Centre, Amended Para,

State will provide the premises for hosting the solution in State Data Centre (SDC) at New

Haryana Secretariat, Sector -17, Chandigarh before the commencement of this project. State is



also in the process of finalizing the site for setting up the Disaster Recovery Centre (DRC) for

SDC with Government of India. 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 meet

the service levels mentioned in the RFP. It is important to mention that solution will be hosted

only at SDC, however its backup would be taken at DRC. SI will be required to carry out Data

Backups of all master and transaction data on this project at the DR Site. Desired RPO <60

minutes for the project. Incremental backups should be taken periodically and sent across to the

Disaster Recovery Site.

Stands amended as

State will provide the premises for hosting the solution in State Data Centre (SDC) at New

Haryana Secretariat, Sector -17, Chandigarh before the commencement of this project. State is

also in the process of finalizing the site for setting up the Disaster Recovery Centre (DRC) for

SDC with Government of India. 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 meet

the service levels mentioned in the RFP. It is important to mention that solution will be hosted

only at SDC, however its backup would be taken at DRC. SI will be required to carry out Data

Replication and Backups of all master and transaction data on this project at the DR Site. Desired

RPO <60 minutes for the project. Incremental backups of the data would be taken periodically

from Databases to External Tape drives, which shall be stored in a safe custody of Haryana

Police. Incremental data backups would also be taken at Disaster Recovery Centre as well in the

same method as adopted for State Data Centre.

7. Corrigendum, Indicative Bill of Material also reflected in Section 6, Vol.II and Annexure

E: Bill of Material, Vol.III of this RFP, is revised as

S. No. Hardware Requirements

A Police Stations - 270 in number Indicative

Quantity # (units)

1 Desktops at Police Stations

i Desktops with pre-loaded latest version of Microsoft Windows 7

Professional or higher OS– 4 at each location

1080



2 Desktop Virtualization Mode4l at Police Stations

i 1 Set each comprising of 4 TFT Screens, four keyboards, four

optical mouse, and one CPU with additional one more CPU as

backup and associated h/w & s/w for desktop virtualization with

pre-loaded latest version of Microsoft Windows 7 Professional or

higher OS

270

3 Other Hardware

i. Desktops with pre-loaded latest version of Microsoft Windows 7

Professional or higher OS

656

ii. HDD 320 GB or higher 270

iii. Multi-Function Laser (Print/Scan/Copy) 376

iv. SNMP based 3KVA UPS for 120min backup 376

v. 2KVA/ 5KVA Generator Set 270

vi. Router for SWAN termination

vii. 16-Port L2 Switch

5 130

viii. Digital Camera 270

ix. Electronic Pen 270

x. Duplex Laser Printer (Black/ White) 310

xi. 600 VA UPS with 60 Min backup 332

B Hardware for State Data Center

3. Servers at SDC (Minimum server required, bidder may propose

more servers as per the solution)

Web Servers 2

Application Servers 2

Database Servers 2

Mail Server 1

Backup Server 1 Identity Access Management Server 1

11

4 Haryana Police reserves the right to adopt either model of Desktops deployment at Police Stations.

5 Specifications of 24 Port Switch is to be considered here.



Antivirus Server/ Management Server 1

EMS Server 1

4. FCIP Router 1

5. SAN Storage 1

6. SAN Management Software As required

7. SAN Switch 2

8. Tape Library 1

9. Backup Software 1

10. KVM Switches 2

11. Server Load Balancer 2

12. RDBMS Licenses (full use and perpetual licenses for 2 Database

servers)

Number to be

proposed based on

the technology

stack adopted

13. CAL License of Enterprise Management System (EMS) for

Police Department equipments considering the expansion of

atleast 20-25% in near future

Total number of

network based

component as per

model (Desktop or

Virtualization

model)

14. Server Operating Systems 11

15. Appliance based Hardware Security Module (HSM) for PKI

Security and Encryption.

2

16. 24 Port L3 Switch to connect the IT Infrastructure of Haryana

Police inside the SDC

2

C Hardware for Disaster Recovery Site

1. Servers at DR Site (Minimum server required, bidder may

propose more servers as per the solution)

Backup Server 1

1

2. FCIP Router 1



3. SAN Storage 1

4. SAN Management Software As required

5. SAN Switch 2

6. Tape Library 1

7. Backup Software 1

D Civil Works No. of Locations

1. Flooring 270

2. Wall Finishing and Painting 270

3. Roller Blinds 270

4. Ceiling Mounted Light fixtures 270

5. 4 mm thick Glass for door renovation 270

6. Split Type AC 270

7. Workstations with allied furniture 270

8. Cabinets (48 Sq. Ft. Approx of 1.8 ft. depth) 270

E Creation of LAN (structured cabling with creation of LAN

nodes, laying CAT-6 UTP cables, patch panels, cable

crimping, installing RJ-45, etc.)

No. of Locations

1. Police Stations (approx. no. of nodes 6 per location) 100

2. Sub-Division Offices (approx. no. of nodes 6 per location) 60

3. District Head Offices (approx. no. of nodes 12 per location) 10

4. Commissionerates (approx. no. of nodes 25 per location) 2

5. Range Headquarters (approx. no. of nodes 5 per location) 4

6. SCRB (approx. no. of nodes 5 per location) 1

7. Police Headquarters (approx. no. of nodes 50 per location) 1

Note:



These are only indicative numbers of material desired for the implementation of this

project. Department reserves the right to increase or decrease the quantity of material at

any time during the currency of the project to any extent and department shall make

payments for each component on actual number provided by SI.

SI shall be responsible for proposing other hardware/ software components as part of

their Bill of Material for the successful implementation of this project

8. 5.4.8 Data Digitization & Data Migration,

In order to bring in more clarity in the scope of SI for Data Digitization & Data Migration,

interested bidders are invited to attend meeting on 8th

March 2011 at 11:00 am in the GO Mess,

Police Complex, Moginand, Panchkula. For any queries related to the aforementioned meeting,

interested bidders may contact the Contact Person as mentioned in RFP Datasheet enclosed

with this corrigendum.

9. 5.4.13 Support to User Acceptance Testing, Audit and Certification, Para (3),

Haryana Police assisted by SPMC/ SPMU will formally notify the SI in writing of any deviations

from defined requirements at the earliest instance after noticing the same during acceptance

testing or at any time during the currency of the project, to enable the SI to take corrective action

and meet the desired Service Levels. Such an involvement of the Acceptance Testing &

Certification agencies, nominated by Haryana Police, 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. SI

shall be completely responsible for providing all the required support for successfully completing

this exercise, which may also require support for final certification from the concerned agency.

Following details added to the clause

Further, in addition to the above mentioned support, SI shall also be responsible for getting

security audit clearance from the Government of India empanelled agencies such as CERT-IN

and quality certification of the complete CCTNS solution from STQC before its deployment at the

Haryana State Data Centre. It is important to mention that all the expenses incurred in User

Acceptance Testing, Audit and Certification of the complete CCTNS solution will be borne by

selected SI.



C. Annexure V

1. Title:

Annexure V: Indicative Technical Specifications

Stands amended as

Annexure V: Minimum Technical Specifications

2. Revised Minimum Technical Specifications also reflected in Annexure E: Bill of

Material, Vol.III of this RFP, are as follows:

A. Minimum Technical Specifications Requirement at State Data Center & Disaster

Recovery Site

1. Revised specifications for Enterprise Management and Monitoring Solution (EMS)

Haryana State has procured and is currently running a comprehensive Enterprise Management

Solution for its SDC and at its State NOC respectively, which addresses the following areas:

Network management comprising of Fault and root cause analysis solutions

Performance monitoring for network and Servers

Application Performance & Traffic Monitoring

Host level security for servers

Trouble ticketing system

As part of implementing the monitoring tool for this project, SI is required to procure full use CAL

licenses of the existing EMS with Haryana State for this project from the OEM. SI shall be

responsible for configuring and integrating the Haryana Police sites on the existing EMS. EMS

software at SWAN\ SDC comprise of CA Spectrum, CA eHealth, CA NSM , CA Database

Performance, CA Access Control, CA Service Desk ,CA Wily APM. Management Servers are

provisioned for all above modules .However bidder should provide necessary additional licenses

as well as supporting hardware if required as per design for any of above components to meet

the project requirements. It is important to mention that Consoles will be extended from existing

EMS\NMS components and will be provided to CCTNS SI. Operator will work with existing

SWAN/ SDC SI managing EMS to discover network, establish agent integrations to report to

existing manager servers. SI will be required to procure supportive hardware to use the CA

Service Desk solution as part of their Central Helpdesk, which would be set up in District

Panchkula in Haryana Police premises

SI shall be required to provide all the necessary hardware/ software to meet the below mentioned

indicative requirements from EMS.

Basic Requirements

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

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

1. Support discriminated polling

2. Should be able to update device configuration changes such as re-indexing of ports

Fault Management

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

inbuilt 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

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

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



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

1. Should be able to monitor/manage large heterogeneous systems environment

continuously.

2. Windows OS

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

Should be capable of view/start/stop the services on windows servers

3. Unix / Linux

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

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

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

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

defined 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

11. Availability and Uptime – Daily, Weekly, Monthly and Yearly Basis

12. Trend Report

13. Custom report

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

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

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

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

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. o EMS should integrate with the application software component of portal

software that measures performance of system against the following SLA

parameters:

Response times of Portal;

Uptime of data centre;

Meantime for restoration of Data Centre etc;

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

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.

ITIL based Helpdesk System

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

NOTE: EMS tools deployed shall have the ability to manage the entire IT infrastructure proposed

by the SI

2. Identity and Access Management

EMS should provide well designed identity and access management system to meet below

requirements:

Proposed Identity & Access Management solution must be extension of existing EMS & from

EMS OEM for seamless integration. The Identity & Access Management should integrate with the

existing server access control solution currently deployed at the SDC to provide holistic end to

end user, application & server level security & auditing. The Identity Management should provide

a services-oriented, software-based identity management service, which allows to easily

automate the management (i.e., creation, modification, suspension and deletion) of the accounts

needed on a variety of disparate systems and physical resources, ensuring that employees,

outsourced agencies should have access to the right systems at the right level of privilege.

Proposed solution must be designed for all internal users. The proposed Identity & Access

Management solution must consist of the following core modules:

Host-based Server Access Control System

Haryana SDC is currently hosting CA Technologies Host based Server Access Control System.

Bidder to provide additional licenses to secure critical servers under scope of the project to meet

below requirements:

Host based security solution must allow controlling of access to system resources

including data files, devices, processes/daemons and audit files.

The solution should Self-protect itself – Must be able to prevent hackers with root access

from circumventing or shutting down the security engine. Must use a self-protected

database for storing all security information.

The solution should provide Rights Delegation - Must provide the ability to designate

specific users as Administrators, Auditors, and Password Managers etc with appropriate

rights. Must also provide the ability to designate specific users as Subordinate or Group

Administrators, to manage users and file permissions for their Group



The solution must provide Stack Overflow Protection (STOP) – Must be able to prevent

stack overflow exploits on UNIX systems, to ensure that arbitrary commands cannot be

executed in order to break into systems.

The solution should support cross platform Management – Must support management

and policy distribution across Windows, Linux and Unix platforms from a central

management console. It must support the deployment of the same policies across

multiple servers ensuring consistency of security policies across machines in the

enterprise.

The solution must provide capability to allow access to sensitive resources only through

approved programs.

Identity and Access Management

Bidder to provide extended IAM above existing host based access control to provide additional

security layer at user & application level.

Must provide centralized administration of user-ids and password management.

Must have APIs to enable additional user management operations on UNIX, NT over and

above the default operating system account set-up.

Must have LDAP interface to enable queries/updates by authorized third-party customer

tools.

Must support enforcement of a centrally-defined security policy, e.g. for access rights,

password lengths

Role-based Administration. Role Based & Rule Based User Provisioning.

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.

Must provide access to only those applications/resources that the user/customer has

authority to.

Should provide capabilities to have Corporate Directory as well as Provisioning Directory.

Web access management system should support single sign-on across security

domains.



If a user is authenticated at a low level of security (e.g., password), then they should be

forced to re-authenticate when they attempt to access a more sensitive resource (e.g.,

one protected by a token card).

The priority of these authentication methods should be Administrator specified .It should

not be hard-wired into the product, and Administrator should be able to control the priority

of each Authentication method. 1000 levels of priority should be supported.

Solution should support directory chaining.

Solution should provide protection from cross-site scripting

Administrator should be able to integrate dynamic/external data (at run-time) in the

enforcement of my policies via a Web service.

Administrator should be able to create policies that perform comparative tests on each

user‘s directory profile information.

Solution should support controlled ―impersonation‖ of users allowing certain users to

temporarily use the entitlements of other users without sharing of passwords.

Solution should support automatic failover and Failover between clusters

Solution should support 4 & 8-way SMP servers.

Administrator should be bale specify that a certain directory be used for user

authentication, but a different directory be used for user authorization. It should also allow

multiple directories to be configured. For example: Customers can be managed in one

directory, employees in another, partners in another, etc.

3. Web Server (Container to execute the presentation logic)

1. The web server should be capable of supporting clustering.

2. All components of the web server should be based on standards and selected such as

to provide ease of management and to avoid compatibility issues

3. All web server components must be maintainable with an ease such that corrective and

preventive maintenance can be performed on the system without affecting the entire

working of system.

4. All the web server components must be capable of being managed from a remote

management station and provide information on performance parameters

4. Application Server

1. Application Server should be fully standards compliant providing support for Web

Services, SOAP, WSDL, UDDI, LDAP v3, SSL v3, XML 1.0 and equivalent standards



2. Provide comprehensive XML support compliant with the W3C XML standards and

contain the basic building blocks to XML-enable applications -including reading,

manipulating, transforming and viewing XML documents

3. Support developing, publishing and consuming web services

4. Support wireless enabled web sites and portals

5. The application server should be capable of supporting clustering.

6. All components of the application server should be based on standards and selected

such as to provide ease of management and to avoid compatibility issues

7. All application server components must be maintainable with an ease such that

corrective and preventive maintenance can be performed on the system without

affecting the entire working of system.

8. All the application server components must be capable of being managed from a

remote management station and provide information on performance parameters

5. Revised Specifications for Database

The database should address all the structured and un-structured data storage

requirements of the proposed system

The RDBMS database should have a high tolerance of failure

The underlying database should support 24x7 high availability

The database should provide horizontal scalability, by adding additional servers for the

same database without any downtime

The data scalability and manageability should be integral part functionality of the

database.

The database should provide enterprise class web management tools for management

and maintenance of databases even from remote places

The database should support native automated disaster recovery capability without any

third party support using cost effective option of automatically synchronizing the

transaction logs to disaster site, which in case of fail over the other node provides the

availability of all data. This flexibility of log synchronization should be supported from

Enterprise to Entry Level server edition of the database

The database should be capable to support plug and play data transfer across platforms

or operating systems

The database should be able to support various types of content like Texts, Images,



Multi-media, Spatial and XML content natively

The database should ensure data synchronization between database servers on near

real-time basis by capturing messages at the source database, stage messages in a

queue, propagate messages from one queue at the source to another queue at the target

and consuming messages

The database should support both way data synchronization across database servers in

one-to-many and many-to-one situations and automatically detect data conflicts and

resolve the same as per predefined conflict resolution algorithms

The database should support data synchronization across database servers in

heterogeneous platforms

The database should be capable to deploy fine-grained access control, separation and

segregation of duties and native encryption capabilities. The database should also

prevent access to sensitive application data by highly privileged users.

The database should control access to the applications, databases and data with flexible

security controls.

The solution should provide options or utility to encrypt/decrypt sensitive data

The solution should support data export and import facility to variety of databases and

other software packages

The solution should provide backup (hot & cold) and recovery facility

The solution should be able to schedule a backup/restore task

The solution should be compatible with 3rd party system monitoring package.

The solution should support selective encryption of the stored data

The database should support a single unified data model hosted on a single database.

The database design & architecture should be in line with the functional and non-

functional requirements of the proposed system

The database should be highly available with every processing node providing full view

of data. This means, in case of failure of one server, each remaining server in the cluster

should provide full access to all data at any point in time

It should support clustering exploiting rapidly emerging disk storage and interconnect

technologies

It should provide automated disaster recovery solution to maintain transaction

consistency, providing an option of zero data loss where required

It should provide restrictive data access that enables different types of users to have

secure, direct access to mission-critical data sharing

It should control data access down to the row-level (row-level security) so that multiple

communities of users with varying access privileges can share data within the same



database

It should provide encryption capabilities while transferring data over networks

It should possess ability to encrypt data stored in the database at the column level

It should provide Public Key Infrastructure (PKI) support

It should provide support for comprehensive auditing for ‗inserts‘, ‗deletes‘, ‗updates‘ and

‗selects‘, and quickly spot and respond to security breaches

It should store XML content native to database

It should have the ability to index, search, and analyze text and documents stored in

database

It should support different partitioning schemes to split large volumes of data into

separate pieces or 'partitions' which can be managed independently

A centrally Monitored Based GUI Administration Tool should be available with the

RDBMS to Create, Delete & Manipulate different Database Objects and also Schedule

Queries priorities centrally.

Server Configuration Tools be available to automatically configure clients, network etc.

Database should preferably have received the security certification (EAL) such as

International Common Criteria for Information Technology Security Evaluation or

equivalent.

Database should support industry standard TPC benchmark or Equivalent.

The database software should provide the following capabilities:

a. Advanced Web Based Reporting Services

b. Data warehousing and Analysis Services

c. Business Intelligence

d. Complete ETL functionality

e. Performance Management Tools

f. Clustering Tools

g. Tuning and Diagnostics Tools

h. Spatial Database Capabilities

i. Database Compression and Encryption Tools

j. Replication Technologies for Failover to Remote Sites.

All the above functionalities should support scalable and high available functionality.

DBMS ETL Tool Capabilities:

a. ETL Should support Import and Export Wizard and supporting connections, source

and destination adapters, and tasks

b. ETL Should support performing persistent lookups, Data Profiling; Should support

fuzzy lookups and fuzzy search

c. The ETL tool should provide for integrating data from various relational or non-



relational sources. The tool should provide native access interface to the following PC

Files – Spreadsheets, Flat Files, DBF, etc..

d. The ETL tool should be rich in the set of in-built transformations and functions. The

tool should provide at least 50 in-built transformation functions.

e. Should support Central Management of Replications, Fine grained scheduling of data

replication, Scale out of replication architecture, Capability for both Push and Pull

Replications

DBMS Reporting capabilities like :

a. Should provide facilities to Create, Design, Generate & manage the reports.

b. Should support Visualization tools such as maps, gauges, and charts

c. Should support for remote and non-relational data sources

d. Should have centralized reporting functionality that gives users a single place for

locating the latest reports, spreadsheets, or key performance indicators.

e. Should Provide Reporting which can be published through a variety of mediums like

web application, client application, mail, ftp folder, mobile handhelds etc. Should support

multiple formats like html, PDF, XML, CSV, etc. and other custom formats as out of the

box.

f. Should provide customization features for reporting where user can filter on various

parameters to be reported on the screen.

g. Should allow administrators to create reporting boundaries (without programming)

using which adhoc reporting can be done by end users.

h. Should allow Creation of filters to control data displayed on a report. And allow

Parameters passing to the reports at run- time.

i. Should provide Offline viewing of previously created Reporting results.

6. Server Load Balancer

10/100/1000Mbps Ethernet Ports – minimum 4 ports

Memory: Minimum 4 GB

Minimum of 2 Gbps throughput

Minimum of 1 Gbps SSL throughput

Minimum of 10000 SSL connections

Server Load Balancing Mechanism

o Cyclic, Hash, Least numbers of users

o Weighted Cyclic, Least Amount of Traffic

o NT Algorithm / Private Algorithm / Customizable Algorithm / Response

Time

Redundancy Features

o Supports Active-Active and Active-Standby Redundancy

o Segmentation / Virtualization support along with resource allocation

Server Load Balancing Features

o Server and Client process coexist

o UDP Stateless



o Service Failover

o Backup/Overflow

o Direct Server Return

o Client NAT

o Port Multiplexing-Virtual Ports to Real Ports Mapping

o DNS Load Balancing

Load Balancing Applications

o Application/ Web Server, MMS, RTSP, Streaming Media

o DNS, FTP- ACTIVE & PASSIVE, REXEC, RSH,

o LDAP, RADIUS

Content Intelligent SLB

SLB should provide protection against DoS/DDoS attack

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

7. Link Load Balancer (may be proposed if State/UT has to build own DC in case SDC‟s

are not operational)

10/100/1000Mbps Ethernet Ports – minimum 4 ports

Memory: Minimum 2 GB

Minimum of 2 Gbps throughput

Link Load Balancing Algorithim

o round robin, wigthed round robin, response time, shortest response etc…

o

Link Load Balancer should support below Management options

o Secure Web Based Management

o SSH

o TELNET

o SNMP v1, 2, 3 Based GUI

o Command Line

8. Production CAS (State) Application Services related servers (Web, Portal, Application,

Database, Directory, etc…)

Blade Chassis Specification



Single blade chassis should accommodate minimum 6 or higher hot pluggable

blades.

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 1 USB port

Two hot-plug/hot-swap, redundant 1Gbps Ethernet module with minimum 8 ports

(cumulative), having Layer 2/3 functionality.

Two hot-plugs/hot-swap redundant 4 Gbps Fiber Channel for connectivity to the

external Fiber channel Switch and ultimately to the storage device.

Power Supplies

o Hot plug/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 pluggable/hot-swappable redundant Cooling Unit

Management

o Systems Management and deployment tools to aid in Blade Server

configuration and OS deployment,

o Remote management capabilities through internet browser

o It should provide Secure Sockets Layer (SSL) 128 bit encryption and

Secure Shell (SSH) Version 2 and support VPN for secure access over

internet.

o Ability to measure power historically for servers or group of servers for

optimum power usage

o Blade enclosure should have provision to connect to display console /

central console for local management like trouble shooting, configuration,

system status / health display

Built in KVM switch or Virtual KVM feature over IP.

Dedicated management network port should have separate path for

management

Support heterogeneous environment: AMD, Xeon and RISC/EPIC CPU blades

must be in same chassis with scope to run Win2003/2008 Server, Red Hat Linux

/ 64 Bit UNIX, Suse Linux / 64 Bit UNIX / Solaris x86



Blade Servers (Web, Portal, Application, Directory, etc…)

Blade can be half / full height with I/O connectivity to backplane

2 Quad core @ 2.0 GHz or above with 4 MB shared L2 cache, 1066 MHz / 2000

MT/s FSB

Processor should be latest series/generation for the server model being quoted

Min 32 GB DDR3RAM with min 8 Nos. free slots for future expandability.

Minimum Memory: 32 GB scalable to 128 GB per blade

2 X (1000BASE-T) Tx Gigabit LAN ports with TCP / IP offload engine support /

dedicated chipset for network I/O on blade server

2 X 300 GB HDD or more hot swappable system disk with mirroring using

integrated RAID 0,1 on internal disks, or min.16 GB compact flash card to be

provided. It should be possible to hot swap the drives without shutting down the

server.

VGA / Graphics Port / Controller

Should support heterogeneous OS platforms

Blade Servers for Infrastructure Services (EMS, Backup, DNS, Antivirus, etc…)

Blade can be half / full height with I/O connectivity to backplane

2 Quad core @ 2.0 GHz or above with 4 MB shared L2 cache, 1066 MHz / 2000

MT/s FSB


Min 16 GB DDR3RAM with min 8 Nos. free slots for future expandability.

Minimum Memory: 16 GB scalable to 128 GB per blade

2 X (1000BASE-T) Tx Gigabit LAN ports with TCP / IP offload engine support /

dedicated chipset for network I/O on blade server

2 X 300 GB HDD or more hot swappable system disk with mirroring using

integrated RAID 0,1 on internal disks, or min.16 GB compact flash card to be

provided. It should be possible to hot swap the drives without shutting down the

server.

VGA / Graphics Port / Controller

Should support heterogeneous OS platforms

Database Server

Minimum 4x hex-core processor with 2GHz or above with 1066Mhz FSB / 2000

MT /s expandable to 8 physical processor with min 6 MB L3 cache per processor


OS support: Microsoft® Windows Server 2003 / 2008, Enterprise Edition / Red

Hat® Enterprise Linux 5 & 4 AP / SUSE® Linux Enterprise Server 9 / Solaris for

x86



Memory (DDR3 RAM): Min. 64 GB scalable upto1TB

RAID controller with RAID 0/1/5 with 512 MB cache

HDD hot pluggable: 4 x 300GB 2.5‖ 10 K RPM HDD or more

Disk bays: Support for min 8 small form factor hot plug SAS / SCSI hard drives in

disk drive carriers

At least 4 x 10/100/1000 Mbps Ethernet ports or more

2 x 4 Gbps Fiber Channel Ports

Ports Rear: Two USB ports (Ver 2.0); RJ-45 Ethernet; keyboard and mouse;

no parallel port; Front port: One USB (Ver 2.0)

Graphics controller: SVGA / PCI bus / ATI® ES 1000 / min 16MB SDRAM

std/max / 1280x1024 at 16M colors

Optical / diskette: 8X / 24X slim-line DVD ROM drive shared across chassis

Power supplies: Hot pluggable/hot swapable redundant AC power supply

Management feature to identify failed components even when server is switched

off.

Rack Mountable

It should provide Secure Sockets Layer (SSL) 128 bit

Encryption and Secure Shell (SSH) Version 2 and support VPN for secure

access over internet.

Should be able to manage systems through a web-browser.

9. Revised Specifications for Storage and Backup Solution

SAN Switches

Minimum 16 Active ports (each with minimum port speed 4 Gbps) within same switch

upgradeable to 24ports

All cable of length of 10 meter each and accessories for connecting Servers /Devices to

SAN.

Should have capability of ISL trunking of minimum 8 ports.

Should support multiple OS.

Non disruptive subsystem maintenance.

Should have dual hot plugfans and hot plug power supplies switching and service

modules.

Should have web based management software for administration and configuration.

Non disruptive microcode / firmware upgrades and hot code activation.

Switch shall support in built diagnostics, power on self test, command level diagnostics,

online and offline diagnostics.

Should support hardware ACL based Port security, Port Zoning and LUN Zoning



Should support Secure Shell (SSH) encryption to provide additional security for Telnet

sessions to the switch.

Should support multilevel security on console access prevent unauthorized users from

altering the switch configuration

Should support Fibre Channel trace route and Fibre Channel Ping for ease of

troubleshooting and fault isolation

Should support the following diagnostics:

o Online Diagnostics

o Internal Loopbacks

o FC Debug

o Syslog

o Online system health

o Power on self test (POST) diagnostics

Should support Applications for device management and full fabric management. The

management software shall be able to perform following:

o Fabric View

o Summary View

o Physical View

o Discovery and Topology Mapping

o Network Diagnostics

o Monitoring and Alerts

Storage Area Network

SAN controller

Dual Active Active Controller

Cache

8 GB Total Mirrored Cache for Disk IO Operations scalable to min 16 GB

Host interface

4 host ports per controller, Fibre Channel (FC),4 Gbps per port

Drive interface

4 drive ports per controller—Fibre Channel (FC) Switched or FC Arbitrated Loop

(FC-AL) standard per controller, 4 Gbps per port

RAID levels Supported

0, 1, 5 / 6

Fans and power supplies

Dual redundant, hot-swappable

SAN support

Box should be compatible of SAN environment



SAN specifications shall have the following

The storage array shall be configured with at least 8 GB cache scalable to min 16

GB mirrored across two storage controllers for disk I/O operations.

Storage subsystem shall support 300GB 15K RPM disks and 400GB or higher

10 K RPM Fiber channel drives & 750GB, 1TB SATA or higher SATA / equivalent

drives in the same device array

Presently, the storage sub system shall be configured with 300 GB FC drives for

performance purpose and 750 GB or higher on SATA / equivalent for archiving

purpose.

The storage system must provide upgrade path to larger or future array controller

and software technology while maintaining the existing investment.

The storage array proposed should have an upgrade path from the earlier

generation product to the current generation product.

All the necessary software to configure and manage the storage space, RAID

configuration, logical drives allocation, virtualization, snapshots (including snap

clones and snap mirrors) for entire capacity etc.

Redundant power supplies, batteries and cooling fans and data path and storage

controller.

Load balancing must be controlled by system management software tools.

The multi-path software should not only support the supplied storage and

operating systems but should also support heterogeneous storage and operating

systems from different OEMs.

The storage array must have complete cache protection mechanism either by de-

staging data or providing complete cache data protection with battery backup for

up to 72 hours or more.

The storage system should have minimum 10 TB and scalable upto 50 TB of raw

capacity using 40% on Fiber Channel drives and 60% on SATA / equivalent

drives using the same configuration as quoted in this tender‖.

The storage array must have the capability to do array based remote replication

using FCIP or IP technology.

The storage array should support block level Synchronous and Asynchronous

replication across heterogeneous storage arrays from different OEMs.

The storage array should support Operating System Platforms & Clustering

including: Windows Server 2003 (Enterprise Edition), Sun Solaris, HP-UX, IBM-

AIX, Linux / Solaris for x86.

Storage should support non-disruptive online firmware upgrade for both

Controllers and disk drives.

The storage array should support hardware based data replication at the Block

level across all models of the offered family.

The storage should provide automatic rerouting of I/O traffic from the host in case

of primary path failure.

Should provision for LUN masking, fiber zoning and SAN security.



Should support storage virtualization, i.e. Easy logical drive expansion.

Should support hot-swappable physical drive raid array expansion with the

addition of extra hard disks

Should be able to support clustered and individual servers at the same time.

Should be able to take "snapshots" of the stored data to another logical drive on

a different Disk/RAID Group for backup purposes

Should be configured with "snapshots and clone"

Vendor should also offer storage performance monitoring and management

software.

The vendor must provide the functionality of proactive monitoring of Disk drive

and Storage system for all possible hard or soft disk failure

Tape Library

Tape drives

Minimum 2 latest generation LTO drives. The SI can size for more as per their

requirements.

Interface

Fiber Channel Interface

Other Specifications

Should have sufficient speed backup to Tape Library in High Availability for

backing up data from the SAN without any user intervention.

Should be able to backup 50% of the entire production landscape in 8 hours

window.

Should support latest generation LTO drives or latest technology based library

with at least 2 latest generation LTO drives tape drives (>=4), rack mountable

with redundant power supplies.

Cartridges should have native capacity of 800 GB or more per cartridge.

At least 50 latest generation LTO drive Media Cartridges with 5 Cleaning

Cartridges, Barcode labels shall also be provided

Backup Software

The proposed Backup Solution should be available on various OS platforms such

as Windows and UNIX platforms and be capable of supporting SAN based

backup / restore from various platforms including UNIX, Linux, and Windows etc.

Centralized, web-based administration with a single view of all back up servers

within the enterprise. Single console must be able to manage de-duplicated and

traditional backups.

The proposed backup solution should allow creating tape clone facility after the

backup process.

The proposed Backup Solution has in-built frequency and calendar based

scheduling system.



The proposed backup Solution supports the capability to write multiple data

streams to a single tape device or multiple tape devices in parallel from multiple

clients to leverage the throughput of the Drives using Multiplexing technology.

The proposed backup solution support de-multiplexing of data cartridge to

another set of cartridge for selective set of data for faster restores operation to

client/servers

The proposed backup solution should be capable of taking back up of SAN

environment as well as LAN based backup.

Bidder must quote the Online SAN based backup functionality on all proposed

database servers with LAN based backup on rest of the application/web/portal

servers..

The proposed solution also supports advanced Disk staging.

The proposed Backup Solution has in-built media management and supports

cross platform Device & Media sharing in SAN environment. It provides a

centralized scratched pool thus ensuring backups never fail for media.

Backup Software is able to rebuild the Backup Database/Catalog from tapes in

the event of catalog loss/corruption.

The proposed Backup Software should offer online backup for all the Operating

Systems i.e. UNIX, Windows, Linux, etc.

The proposed Backup Solution has online backup solution for different type of

Databases such as Oracle, MS SQL, MySQLand Sybase / DB2 etc. on various

OS.

The Proposed backup solution shall provide granularity of single file restore.

The Proposed backup solution shall be designed in such a fashion so that every

client / server in a SAN can share the robotic tape library.

Backup Solution shall be able to copy data across firewall.

The backup software must also be capable of reorganizing the data onto tapes

within the library by migrating data from one set of tapes into another, so that the

space available is utilized to the maximum. The software must be capable of

setting this utilization threshold for tapes

The backup software should be able to support versioning and should be

applicable to individual backed up object‘s

Should have the ability to retroactively update changes to data management

policies that will then be applied to the data that is already being backed up or

archived

All software licenses should be in the name of Haryana Police and should be full

use perpetual license, i.e. the software license should not expire after the

contract period. The software Licenses should be comprehensive and no further

licenses should be required for DC/DR operations. The software installed should

necessarily be the latest version at the time of actual implementation.

FC-IP Router



Fibre Channel Ports

min 4 FC ports

FC Port Speed

Autosensing 1/2/4 Gb/s

iSCSI (Ethernet) Ports

min 8 Ethernet ports

iSCSI (Ethernet) Port Speed

1 Gigabit Ethernet

Aggregate Bandwidth

min 125 MB/s

Protocol Support

FCP

iSCSI

High-Availability Features

Two-way active/active clustering with failover and failback capabilities

Multiple iSCSI connections provide multipathing support from a single

gateway to as many as 100 servers.

Management Features

CLI (by Telnet, SSH, or console)

iSCSI Gateway Manager

SNMP

Allows for monitoring traffic statistics on each storage and network

interface, fan and temperature and iSCSI session details.

10. Appliance based HSM for PKI Security and Encryption

S. No Feature / Specifications Required

1 Should support Windows 2000,2003,2008,Linux,Solaris,HP-UX 11i,VMWARE,AIX 5.3

2 Should comply to standards like FIPS 140-2 Level-3, CC EAL4+,ROHS,FCC part 15

Class B

3 Key Exchange Mechanism: DES / TripleDES, AES Algorithm Symmetric Algorithm :

AES, MD5, SHA 1, SHA 2, SHA-256 , DES, TripleDES

4 Support for various cryptographic algorithms: Asymmetric Key with Diffie-Hellman

(1024-4096 bit), RSA (512-4096 bit) and (PKCS#1 v1.5, OAEP PKCS#1

5 Signing speed : 5000 S/S

6 Remote PED Support for Authentication



7 Onboard key generation, Digital Signing & Verification process to be done inside the

HSM only for better performance and security

8 HSM should be integrated with the applications running inside the Data Center

9 Complete hardware based storage of key material for entire Life cycle

10 24/7 telephonic/email support infrastructure based out of India

11. KVM Switch

Keyboard, Video Display Unit and Mouse Unit (KVM) and/or other Control Devices/PCs may be

used for the IT Infrastructure Management for which the necessary consoles/devices shall be

placed by MPSEDC in the location earmarked. The KVM unit should provide the following

functionalities:

a. It should be rack-mountable.

b. It should have a minimum of 8 ports scalable upto 24 ports.

c. It should support local user port for rack access.

d. It should support both USB and PS/2 connections.

e. It should be capable of storing username and profiles.

f. It should support high resolution of minimum 1280 x 1024

g. It should be capable to auto scan servers

h. It should work on CAT 6 / CAT 7 cables.

i. Rack Mountable LCD Monitor with In-built Keyboard & Mouse

i. 1 U Rack Mount

ii. Display size: 17 inches diagonal

iii. Contrast Ratio: 700:1

iv. Display colors: 16 million

v. Resolution: SXGA 1280 x 1024

vi. Brightness: 300 nit

vii. Compatible to both PS/2 and USB based inputs

12. L3 Switch at Data Center:

(i) Layer 3 stackable switch

(ii) 24 nos. of dedicated 10/100/1000 Base-T ports

(iii) 4 Nos. of dedicated 1000 Base X

(iv) support to enable dedicated 64Gbps Stacking and 2* 10G ports (or more) by

seamless addition of hardware resources

(v) Nonblocking architecture

(vi) (vi) 160 Gbps switching fabric and 65.5 Mpps forwarding rate

(vii) Support IGMP Snooping with Broadcast Control IGMP v3.

(viii) Support for minimum 20000 MAC addresses.



(ix) Ethernet, Fast Ethernet, Gigabit, 10Gigabit support

(x) Spanning tree/Rapid Spanning Tree support

(xi) Per VLAN Spanning Tree

(xii) Support for IEEE 802.1Q tagging - 1K VLANS & 4K VLAN ID's

(xiii) Dynamic Trunking Protocol or Link Aggragtion Control Protocol or equivalent.

(xiv) VLAN Trunking Protocol or centralized VLAN management or equivalent

(xv) Traffic classification should be based on user-definable application types: TOS,

DSCP, Port based, Mac address, IP address, TCP/UDP port number

(xvi) Multicast filtering per port should be supported

(xvii) Support SNMP upto ver.3

(xviii) Prioritization support

(xix) Minimum 500 VLANS

(xx) SNMP and Telnet support

(xxi) Web-based and CLI management

(xxii) Four RMON groups (1,2,3&9)

(xxiii) Out of Band Management Ethernet RJ45 Port

(xxiv) Additional features: Advanced QoS, Rate limiting

(xxv) L3 Features : Static routes, RIPv1/v2 & RIPng

(xxvi) Security : Time based L2/L3/L4 Access Control Lists, 802.1x, IPFIX, and AAA

Radius support

(xxvii) Mounting: 19‖ Rack mountable

(xxviii) Source power supply: 230 V AC Single phase 50Hz to internal hot swappable PSU,

slot for Internal RPSU

B. Minimum Technical Specifications Requirement at Police Units

1. Revised Specifications for Desktops

Client Systems - all Police Units/ Offices

Minimum Technical Specifications for Desktop PC

Processor: Intel Core i5-650processor (3.20 GHz) with Q57 Chipset or higher

Cache: 6 MB

Memory Type: 4 GB DDR-III @ 1066 MHZ or higher

Memory Slot: 4 DIMM Slots

Internal Hard Disk/Speed: 320 GB SATA (7200 RPM) or higher

Optical Drive: SATA SuperMultiLightScribe DVD Writer Drive

Display size: 18.5 inch (measured diagonally)

Graphics Controller: Intel latest Graphics Media Accelerator integrated graphics

Form Factor: Convertible Minitower

External I/O ports: Rear: 6 USB 2.0, 1 standard serial port, 1 optional serial port, 1

optional parallel port, 2 PS/2, 1 RJ-45, 1 VGA, 1 Display Port, audio in/out; Front: 2 USB

2.0, headphone and microphone



Expansion slots: 3 full-height PCI, 1 full-height PCI Express x1, 2 full-height PCI

Express x16

Network interface: Integrated Intel 82567LM Gigabit Network Connection

Power requirements: Input voltage 90 – 264 / 100 – 240 VAC, 50/60 Hz, 47 – 63 Hz,

active PFC (85% High Efficiency)

Management: Desktop Management Tool

Bilingual Keyboard (Hindi and English): PS/2 or USB Standard Keyboard

Pointing device: USB 2-Button Optical Scroll Mouse

Security management: TPM 1.2 TPM Security Chip (except for Russia), TPM Pre-Boot

Authentication (via BIOS), Smartcard Pre-boot Authentication (via BIOS), Stringent

Security (via BIOS), SATA port disablement (via BIOS), HP ProtectTools Embedded

Security Software, Serial, Parallel, USB Enable/Disable (via BIOS), Removable Media

Write/Boot Control, Power-On Password (via BIOS), Setup Password (via BIOS)

Warranty: 3 Years Part, 3 Years Labour, 3 Years On-Site

2. Router

a) General Architecture:

(i) High speed CPU

(ii) Rack mountable configuration

(iii) Health LED for all modules to indicate status

b) Router Port Requirements:

(i) 10/100 Mbps Ethernet- 2 Nos

(ii) WAN Ports E1- 2 Nos

(iii) Packet Forwarding Speed- Minimum 60 Kpps

c) Router Features:

(i) Support for router redundancy protocol

(ii) Router software must have on line reconfiguration facilities

(iii) High MTBF

(iv) Capable of booting from a remote system where router image is present

(v) Support for standard routing protocols like OSPF, RIP & BGP

(vi) Flash min 128 MB

(vii) Minimum of 256 MB RAM

(viii) Configurationally changes should be done without rebooting the router or modules

(ix) Stateful firewall functionality and IDS.

d) Software features:

Following standard IP routing protocols:

(i) Static

(ii) RIP, OSPF



(iii) OSPF Over Demand Circuits

(iv) Policy Routing

(v) IP Version 6 Support

(vi) Support for IPSec& 3DES through a simple software upgrade as and when required.

Following WAN protocols:

(i) PPP

(ii) Multilink PPP

(iii) Compression-Payload and TCP/IP Header

Following Multicasting and Quality of Service (QoS):

(i) Resource Reservation Protocol (RSVP) as per RFP 2205 and Internet Group

Management Protocol Version 2 (IGMPv2) as per RFC 2236.

(ii) Support for IP Precedence, Committed Access Rate (CAR),

(iii) DiffServQoS

(iv) The router shall support Application recognition and it should be possible to frame

policies based on the applications.

e) Security Features:

(i) Support DES / 3 DES / AES

(ii) PPP PAP or CHAP support.

(iii) VPN support

(iv) Time based Access Lists

(v) Multiple Privilege Levels.

(vi) Support for RADIUS or AAA.

f) Power: 230 V AC, 50 Hz

3. Revised specifications of Multi-Function Laser (Print/ Scan/ Copy)

Multifunction Laser Printer LAN 3 in 1 Printer (Black & White)

Minimum Technical Specifications for Multi-Function Laser Printer

Printer

High-speed printing, Black-and-white: up to 27 ppm, Duty Cycle: up to 15,000 pages per

month

Automatic two-sided printing, 250-sheet input tray, Print, scan and copy unattended with

the Automatic Document feeder, enhanced print permanence,

Capable of installation, configuring, monitoring and troubleshooting in the network, from

anywhere on the network

Scanner

Flatbed with automatic document feed, upto 4800 dpi; Enhanced upto 19200 dpi; Scan

size atleast (flatbed): 8.5 x 14 inches (216 x 356 mm), front panel scan (scan to

application.

Copier

Black-white colour-Upto 1200x600 dpi, Copy speed (black, draft quality, A4):Up to 35

cpm, Copy resolution (black graphics): Up to 1200 x 600 dpi, Copier resize: 25 to 400%,

Maximum number of copies: Up to 99, Copier smart software features: Up to 99 multiple



copies, reduce/enlarge from 25 to 400%, 2-up or 4-up allowing 2 or 4 pages to be

copied onto 1 page, contrast (lighter/darker), resolution (copy quality), tray select,

collate, margin, shift

4. Revised specifications of SNMP based 3KVA UPS

SNMP Based UPS - all Police Units/ Offices

Minimum Technical Specifications for UPS

1. ISO 9001 certified brand

2. True On Line Type

3. Backup period should be atleast2Hrs with minimum 7200VAH for 3 KVA

4. IGBT with High Frequency PWM (Pulse with Modulation) Technology

5. Output wave form should be Sine wave

6. Compatible with local Electricity Power Generator.

7. Total Harmonic Distortion should be less than 3%.

8. Support input voltage range of 160 V to 270 V.

9. Output Voltage should be 230 Volt AC (+/- 1%)

10. Output frequency should be 50 Hz +/- 0.05 Hz (Crystal Controlled)

11. Closed housing for batteries with suitable stand.

12. Inherent protection should be provided for over loading, low battery, over temperature, short circuits, over and under input voltage.

13. LED indicators should be provided for at least load indication, load on battery, low battery, overload, Mains ON.

14. Galvanic Isolation to be provided either through external isolation transformer at input or through inbuilt isolation transformer at output

15. Audible indicator should be provided for at least load on battery, low battery, Mains failure, Overload

5. Revised specifications for 2 KVA or 5 KVA Generator Set

2KVA/ 5KVA Generator Set - all Police Units/ Offices

Minimum Technical Specifications for DG Set

1. The proposed DG set should be able to support the Police Unit equipments along with AC, in absence of primary power source. Engine shall be vertical multi cylinder 4 stroke type in accordance with IS 10002-1981 with latest amendments.

Type Multi cylinder Method of starting Electric start 12 V DC Type of cooling Water cooled /Air cooled Type of governor Mechanical/Electronic Type of fuel High speed diesel Rating Continuous Output Suitable HP rated to match the alternator

Rated speed 1500 RPM Over load capacity 10% overload – minimum 1 hour

50% overload – minimum 1 minute

2. Accessories



Flywheel to suitable diameter and fuel injection equipment Air cleaner Lubricating oil cooler Electric motor starting equipment like motor, battery, charging generator with

voltage regulator etc. Heavy duty radiator with fan Residential type silencer with exhaust piping with vibration isolator Fuel tank suitable for 8 Hrs of continuous running with necessary piping and fuel

gauge, drain valve, inlet and outlet connections. Anti vibration mounting pads (Dunlop) Speed controlling governor Suitable coupling system to the Alternator Tachometer Lubricating oil pressure gauge Hour meter to indicate number of Hrs of operation Auto trip on low oil pressure Over speed alarm with trip Thermal insulation for exhaust line with glass wool, Aluminium sheet, chicken mesh,

Diesel line 12 mm dia including beads flangeretc Battery 12 V with lead and terminal Battery charger. Protection: Protection against low lubricating oil pressure, high water

temperature and over speed shall be provided for engine with alarm and fuel shut off.

3. Compliance Shall compliance with the latest CPCB emission & noise norms (less than 75db at 1

meter distance)

6. Revised Specifications for L2 Switch at PS/HO

(i) Layer 2 switch (ii) 24 No 10/100 ports (iii) 2 Nos. 10/100/1000 (iv) Non-blocking architecture (v) min 8.8 Gbps switching fabric and 6.5 Mpps forwarding rate (vi) Support IGMP Snooping with Broadcast Control IGMP v3. (vii) Support for minimum 8000 MAC addresses. (viii) Ethernet, Fast Ethernet support (ix) Spanning tree/Rapid Spanning Tree support (x) Per VLAN Spanning Tree (xi) Support for dynamic VLAN Registration (xii) Dynamic Trunking Protocol or equivalent. (xiii) VLAN Trunking Protocol or Centralized VLAN management or equivalent (xiv) Traffic classification should be based on user-definable application types: TOS,

DSCP, Port based, Mac address, IP address, TCP/UDP port number (xv) Multicast filtering per port should be supported (xvi) Support SNMP upto ver.3 (xvii) Prioritization support (xviii) Minimum 250 vlans (xix) SNMP and Telnet support (xx) Web-based and CLI management (xxi) Four RMON groups (1,2,3&9)

Should support Policy based Switching and traffic Redirection One to one and One to Many mirroring



SCP and SFTP for secure Management Private Vlan support

(xxii) Additional features: Advanced QoS, Rate limiting (xxiii) Time based L2/L3/L4 Access Control Lists, 802.1x and AAA Radius support (xxiv) Mounting: 19‖ Rack mountable (xxv) Source power supply: 230 V AC Single phase 50Hz

7. Revised specifications of 600VA UPS with 60 minutes backup

Specifications

Certifications ISO 9001 certified / ISO 14001

Technology PWM Technology employing MOSFETS for switching

Efficiency >=75%

Input Voltage & Range 140-280 V

Input Frequency Range 47 to 53 Hz

Output Voltage 200 to 255V

Frequency 50 Hz +/- 5%

Output Power Factor 0.6 lag

Waveform Quasi Sine Wave

Battery Backup 60 minutes

Battery Type Sealed Lead Maintenance Free VRLA type (Lead Calcium SMF batteries NOT acceptable)

Battery Capacity Minimum 336 VAH

Transfer Time <5 msec

Battary Brands Reputed &Reliable brands

Temperature Range 0 to 45 Degree C

Noise level <55 dB @ 1 Meter

Alarms & Indications All necessary alarms & indications essential for performance monitoring of UPS like mains fail, low battery & fault detection

Communication Interface

RS232/DB9

8. Digital Pen

Digital Pen- all Police Stations

Minimum Technical Specifications for Digital Pen

Average battery life

Min. 2.5 hours continuous writing use

Average usage life

150,000 hours

Approximate battery recharge time

2 hours



Battery type Lithium-ion polymer rechargeable battery

Standard connectivity

USB 1.1 (also called High Speed USB 2.0)

Humidity non-operating

0 to 95% RH (excluding rain, non-operating)

Humidity range 0 to 95% RH (excluding rain)

Humiditiy recommended operating range

0 to 90% RH (non-condensing, operating)

Operating temperature maximum

104°F

Operating temperature recommended range

32 to 104°F

Storage temperature range

-4 to 104°F

Storage life Up to 5 years

Image compression

Pattern images to X, Y coordinate samples with relative time of capture

Image processing rate

75 Hz

Image resolution

Atleast 500 dpi

Image scaling Perspective, rotation, tilt, and error correction

Languages supported

English and Hindi

Internal fixed memory

Atleast 10 MB (1.3 MB available for user strokes)

9. Revised specifications of Digital Camera

Digital Camera - all Police Stations

Minimum Technical Specifications for Digital Camera

Features Atleast 14 Mega Pixels Sensor Type 1/2.3 Super HAD CCD or equivalent Optical Zoom: 4x Lens: Carl Zeiss Vario-Tessar or equivalent F Number 2.7 – 6.5 Auto Focus Range (W: Approx. 4cm to Infinity, T: Approx. 60cm to



Infinity) Compatible Recording media- Built in memory , SD Memory card ,

SDHC Memory Card , SDXC Memory Card, etc. LCD: 2.7 (6.9 cm) (230K pixels), Clear Photo LCD Battery Life: 240 shots or 120mins Battery System: Lithium ION Battery USB 2.0 Hi-Speed Photo Mode Intelligent Auto, Easy Shooting, Program Auto, Steady

Shot Scene Selection Twilight / Twilight Portrait / Landscape / Soft Snap /

Snow / Beach / High Sensitivity / Underwater / Gourmet / Pet Still Image Size 14M 4,320 x 3,240 Still Image Size 16:9 Mode 11M(4,320 x 2,432) / 2M(1,920 x 1,080) Movie Recording Mode (QVGA) 320 x 240, 29.97fps Movie Recording Mode (VGA) 640 x 480, 29.97fps Movie Recording Time Up to 2GB per shoot Recording Format Motion JPEG / AVI Still Image Recording Mode Normal (JPEG) / Burst (JPEG) ISO Sensitivity Setting Auto / 80 / 100 / 200 / 400 / 800 / 1600 Image Stabilizer Auto Focus Mode Intelligent Exposure Compensation Plus / Minus 2.0EV, 1 / 3EV step White Balance Auto / Daylight / Cloudy / Fluorescent / Incandescent /

Flash Flash Mode Auto, Flash On, Flash Off, Pre-flash Auto Daylight Dynamic Range Optimiser Standard / Off / Plus Face Detection Red-eye Reduction

User Interface

Self-Timer Auto Review Index Playback Playback Moving Image Mode (QVGA / VGA) Slide Show Playback (SD) Image Rotation / Divide (MPEG) / Cue & Review Hand Shake Alert LCD Brightness Setting Speaker Volume Control Internal Memory Full Data Copy (to Memory Stick) Multi-use Terminal USB Connecting Auto / Mass Storage



33 RRFFPP VVOOLLUUMMEE IIII

A. Section 7, Format for Bid Response – Commercial Bid

1. Form 2: Detailed Component-Wise Pricing stands amended as

S.

No. Category

Component No of Components /

Units of Service (X)

Rate (per unit)

(Y)

Total Cost ( =

X*Y)

A. Hardware Related Costs with the AMC6 for the period of 5 years from the Go-Live of the project

1. Infrastructure /

Hardware

Set of Virtualized

Desktops with

preloaded OS

Desktops with

preloaded OS

Printers

…

DG Set7 2 KVA 270

DG Set 5 KVA 270

Others

2.

Infrastructure

Installation and

Testing /

Miscellaneous

Charges

…..

Others

Total A:

B (i). Networking (LAN) Related Costs

1. Network Related

Infrastructure

Routers

Switch

….

Structured

Cabling

Others

2. Network Testing /

6 Rates quoted for AMC of hardware shall also be applicable for AMC of existing hardware with Haryana

Police. 7 Although rates of DG Sets of 2 KVA and 5 KVA category have been asked, however only one category

of DG Sets would finally be procured and which shall be decided at the time of negotiations



S.

No. Category



Rate (per unit)

(Y)

Total Cost ( =

X*Y)

Bandwidth/

Miscellaneous

Charges

….

Others

Sub Total B(i):

B (ii): Networking – VPN over Broadband

S. No Connectivity

Annual Charges

for 512 Kbps

bandwidth at

each location (a)

No. of Locations (b) No. of Years

(c)

Total Cost ( =

a*b*c)

VPN Over

Broadband 1000 1

….

Others

Sub Total B (ii):

Total B: Sub Total B(i) + Sub Total B(ii):

C (i) . Application Development & Audit, Testing and Certification with Database Creation Cost

S.

No. Category

Name of the

module No of licenses (X)

Rate (per unit)

(Y)

Total Cost ( =

X*Y)

1.

For COTS

products: Module

wise licensing and

deployment cost

Module 1

Module 2

……

Module n

2.

CCTNS

application: Total

cost of

Customization,

integration,

development and

deployment of the

CCTNS solution as

per requirements

mentioned in the

RFP

Name of the

Module of CAS

(State)

Man Months (a) Man Month

Rates (b)

Total Cost

(=a*b)

Module 1

…..

Module n

3. For Be-Spoke

development

Name of the

Module

Man Months (a) Man Month

Rates (b)

Total Cost

(=a*b)



S.

No. Category



Rate (per unit)

(Y)

Total Cost ( =

X*Y)

Module 1

…..

Module n

Sub Total C (i):

S.

No. Category Annual Charges (a) No. of Years (b)

Total Cost

(a*b)

4. Annual Maintenance Charges for

complete CCTNS Application 5

8

5. …..

6. Others

Sub Total C (ii):

S.

No. Category Total Cost

7. Application Testing

8. Application Audit incl. security audit and clearance from GoI agencies

9. Application Certification incl. Quality Certification from STQC

10. …..

11. Others

Sub Total C (iii):

Total C: Sub Total C(i) + Sub Total C(ii) + Sub Total C(iii):

D. Site Preparation and Civil Works

1.

Site Preparation

and Civil Works at

MHC room in each

Police Station

Flooring

2 Wall finishing and

Painting

3 Computer

Workstations

4 Cabinets

5 Renovation of

main entry door

6 Windows Roller

8 AMC charges are applicable only after the Go-Live of Complete CCTNS system in the State.



S.

No. Category



Rate (per unit)

(Y)

Total Cost ( =

X*Y)

Blinds…

… ….

n Others

E. Operations and Maintenance Costs (Half yearly Expenses for 5 years of contract after „”Go-Live”) –

as detailed in RFP Volume 1

1.

Application

Maintenance &

Operational

Expense including

upgradation,

deployment of

patches, fixes etc.

2.

Infrastructure

Maintenance

Expense (Helpdesk,

deployed hardware

& network

infrastructure etc.)

3. ….

4. Others

Total E:

F: Support Manpower

1. Programmer

2. System Analyst

3. Data Entry Operator

4. Trainer

5. …..

6. Any Other

G. Data Digitization

1.

Cost of digitization of data (data entry of

the Master data and minimum historical

transactional data entry)

2 persons for 3

months (6)

2. Cost of scanning of existing files for the

Integrated Workflow and Document

1 person for 6

months (6)



S.

No. Category



Rate (per unit)

(Y)

Total Cost ( =

X*Y)

Management System

…..

Others

Total G:

H. Data Cleansing & Data Migration

1. Cost of Data Cleansing and Migrating Data from existing system to new system

2. Testing of migrated data

….

Others

Total H:

I. Training (considering batch size of 20-30 participants)

S.No. Training Cost Per Person for Qty Rate (per unit) Total Cost

1. Change Management Trainings 5000 trainees L 5000*L

2. Trainings on the Application modules 10000 trainees M 10000*M

….

Others

Total I:

J. Data Centre Related Costs with the AMC for the period of 5 years from the Go-Live of

the project:

S.

No. Category Component

Qty / Units

of Service

(X)

Rate (per unit) (Y) Total Cost (= X*Y)

1.

Deployment of

requisite

infrastructure

for Data centre

Servers

2. Networking

equipments

3.

Storage

equipments (SAN

etc.)

4. Back up

equipments



S.

No. Category Component

Qty / Units

of Service

(X)

Rate (per unit) (Y) Total Cost (= X*Y)

5. Server OS license

6. Database license

7. Anti-virus

8. EMS CAL

Licenses

9. Identity & Access

Management

10. HMS

11. ….

12. Installation &

testing charges

13. Others

Total J:

K: O&M of Data Center

1

All the O&M

cost for

managing the

data center

services

Site preparation

2. Manpower

3.

Maintenance of

the H/w & system

software

4.

Maintenance &

updation of Anti-

virus

5. …..

6. Others

Total K:



B. Annexure – Other Formats

2. V. Undertaking on Provision of Work Environment at the Nodal Agency

Stands amended as

(Company letterhead)

[Date]

To

<<Address to be added>>

Sub: Undertaking on Provision of Work Environment at premises of Nodal Agency

Sir,

1. I/We as System Integrator do hereby understand that the onsite team of System

Integrator operating out of Haryana Police premises will be provided only with seating

space. Any other requirements such as desktops, software will be System Integrator‘s

responsibility.

Yours faithfully,

Authorized Signatory

Designation



44 AANNNNEEXXUURREE:: IINNDDIICCAATTIIVVEE LLIISSTT OOFF LLOOCCAATTIIOONNSS AANNDD

AADDDDRREESSSSEESS

Table of Police Ranges, Police Commissionerates, Police Districts, Sub-Divisions, Police

Stations and Police Posts in the state for assessing the network connectivity feasibility

Name of Range

Name of District

Name of Sub-Divisions against the District

Name of Police Stations against the Sub-Divisions

Name of police Posts against the Police Station

Special Cell

Ambala Range

Panchkula

Panchkula Sub Division

Sector-5 1.

Sector-2 Sector-6 Sector-7 Sector-10 Sector-21

CIA Staff Crime against women cell Detective Staff GIS Cell

2. Sector-14 Sector-15 Sector-16

Chandimandir

Balwala Ramgarh Morni Sector 25

Sector-20

Sector-19

Raipur Rani Mauli

Mansa Devi Complex

MDC

Kalka Sub-Division

Kalka

City Kalka

Pinjore

HMT Matewala Surajpur

Traffic Surajpur

Ambala Ambala Sub- Division

Ambala City 1.

PP No-1 PP No-2 PP No-3 PP No-4 PP No-5

CIA Staff CAW Cell Special women Protection Cell Security Branch Detective Staff Baldev

Nagar 2.

Baldev Nagar Model Town Sector-7 U.E

Ambala Sdr PP Sector-9

Ambala Cantt

Regiment Bazar Topkhana



H.B.colony

Parao

Lal Kurti Mohra

Mahesh Ngr

Patvi

Panjokhra

Naraingarh Naraingarh

Shehzadpur

Brara Brara

Mullana

Indl.Area Saha

Yamuna -nagar

Yamuna -nagar

.Farakpur

Gandhi Nagar Women Cell IT Cell CIA Staff Cyber Cell Special Cell Maoist Cell

Sadhaura

Bilaspur

Chappar Ranjit Pur

City YNR

Hamida Rampura

Sadar YNR Kalanaur

Radaur

Kheri Lakha Singh

Jathlana

Traffic

Jagadhari Sub-Division

Sadar Jagadhari

City Jagadhari

1. Buria Gate

2. Sec-17 U.E.

3. Arjun Nagar

Chhachrauli

Khizrabad

Buria Panchtirthi

Kurukhetra Thanesar City Thanesar

City Thanesar Subhash Mandi Sector-7 HUDA

CIA Staff Detective Staff P.O. Staff AEC Staff Excise Staff Women Cell No-1 Women Cell-2 Women & Child Welfare Staff Squad to prevent

Sadar Thanesar Jyotisar 3

rd Gate

Kurukshetra

Ladwa



Babain Eve-teasing Prosecution cell Senior citizen spl staff Unidentified dead bodies and Blind murder cell

Shahbad

HUDA Shahbad City Shahbad

Jhansa

Traffic

Pehowa Pehowa

City Pehowa Gumthla Garba

Ismailabad

Kaithal Kaithal City Kaithal

HUDA Anaz-mandi

CIA Women Cell

Sadar Kaithal

Sangatpura Titram

Kalayat

Rajound Kithana

Dhand City Pundri

Pundri

Traffic

Gulha

1. Guhla 1. Mehmudpur

2. Ramthali Azimgarh

CIA Women Cell

1. Cheeka 2.

1. Bhagal Arnoli

Siwan S Siwan

Rohtak Rohtak Rohtak 1.

1. Sadar RTK

1. Titoli 2. Ghilor

CIA CAW Cell EOW Cell CIA Women Cell

Sampla 1. Kharawar Kansala

2. City RTK 1.

Old Sabzi-Mandi Indira Colony Sukhpura Chowk Gau Karan

3. Civil Line 4.

Gandhi camp Model Town Arya Nagar New Sabzi- Mandi

2. Shivaji colony



3. U.Estate

1. PGIMs 2. Sector-

2,3,4 3. Sector-1 4. New Bus

Stand Sector-14

Meham Kalanaur

5.

2. Meham

City Meham

3. Lakhan Majra

Jhajjar Jhajjar

Jhajjar

1. Dujana 2. City JJR Dulina Kulana

1. Beri

Chhuchakwas Diggal City Beri

Sahl Sahlawas

Sasrauli

Bahadurgarh

City B.garh

1. Sector-6 2. Sector-9 3. MIF

Sdr B.garh

1. Assauda 2. Mandothi 3. Badli

Line Par B.garh

Sonipat Sonepat

City Sonipat

1. Gohana Road

2. Gita Bhawan

3. Sector-23 Old City

CIA, CAW EOW SIT Senior citizen cell

Civil Line

1. Silkas colony

2. Sector-14 Sector-15

Sadar Sonipat

1. Sector-3

PS Women

Kharkhauda

Jharaul Saidpur

Kundli Barota

Rai

Bahalgarh Garhmirkpur

Mohana

Khanpur Kalan



Ganaur Ganaur

Khubru Rajlugarhi

Murthal Mimarpur

Traffic

Gohana City Gohana Samta Chowk Mudlana

. Sadar Gohana Butana

Baroda

Women

Panipat

Panipat

Model Town

8-Marla Model town Assandh Road

CIA Economic Cell Anti Vehicle Cell RTI Cell Samoksha Cell Women Cell

City Panipat

Bus stand Quilla Tehsil Camp Sec-7 HUDA

Chandni Bagh Sec-11-12 HUDA Sec-29 HUDA Baljit Ngr Kishan Pura

Bhapoli

Traffic Smalkha Panipat

Sadar PPT Sanauli

Samalkha

Smalkha

City Smalkha

Israna

Matlauda

Urlana Thermal Bohli

Karnal Karnal Sadar KNL

Jundla Rambha

CIA Women Cell Detective Staff Senior Citizen Staff Civil Line

Sec-13 Sec-6 Sec-9 Model Town

Madhuban

Kunjpura

City KNL

Ram Nagar Sadar Bazar Bus Stand Sec-4

Butana Nigdu

Tarauri

Highway Traffic



Assandh Assandh

1. Jalmana

2. Ballah 3. Salwan

Nissing Sitamai

Gharunda Munak

Indri

Indri Biana

South Range

Mewat Nuh

Nuh Akera Chowk CIA Women Cell Detective Staff Senior Citizen Staff

.Tauru Khori

Jhirkha FP.Jhirkha

Nagina FP.Jhirkha

Punhana Bichore Piningwan

Nagina

Palwal Palwal

City Palwal

Bus Stand Bhawan Kund Hathin Gate

CIA Women Cell Detective Staff Senior Citizen Staff Sadar Palwal

Gadpuri Dhatir

Chandhaut

Amarpur Bagpur

Camp colony

Hodal

Hassaanpur

Hodal Mundkati

Hathin

Hathin

Uttawar Mindkola

Traffic Hodal



Rewari Rewari

City

Rewari

Gokal Gate

Kanod Gate

.Bharawas Gate

Bus stand

Hospital

CIA , CAW, EOW

Sadar Rewari

Model Town

Sec-3

Court

Complex

Rampura

Bharawas-VIII

Bawal City Bawal

Kosola

Dharuhera

Traffic

Kosli Kosli

Nahar

Dahina

Jatusana

Khol Kund

Rohrai

Mohinder-

garh

Mohinder-

garh

.M.garh

City M.garh

Akoda

CIA Women Cell

Detective Staff

Senior Citizen Staff

Kanina Kanina

Dongra Ahir

Satnali Madhogarh

Narnaul City NNL

Mahavir Chowk

Govt. Hospital

Sadar NNL

Faizabad

Gaheli

Ateli City Ateli

Nangal

Chowdhary

Nizampur

Traffic



Hisar Hisar

Hisar

City Hisar

HTM HSR

Dogran Mohalla

Parao

Multani-chowk

Surya Ngr

12 Qurter

Bus Stand

Anaz Mandi

Spl cell

AVT staff

Senior citizen cell,

missing children cell,

CAW, Cyber Crime

Cell, EOW, CIA,

Slum Cell

Civil Line

U.Estate-II

Court-Complex

PLA HSR

HAU HSR

Sadar Hisar

Balsmand

Azad Nagar

Cantt HSR

Mangli

Barwala

Adampur

Agroha

Uklana

Traffic Chikenwas

TAP Sorkhi (SD

Hansi)

Baas

Hansi

Narnaund Kheri chowk

City Hansi Anaz Mandi

Sadar Hansi

Jind Jind

City Jind

Civil lines

Rohtak Rd

Patiala Chowk

Govt. Hospital

Bus stand

CIA Staff, PO Staff,

Excise Staff

Prosecution Staff,

CAW, Vehicle Theft

Act Cell, Maoist cell,

Sr. Citizen cell,

EOW, Women/Child

Protection Cell

Sadar Jind

Julana

Alewa

Traffic Jind



Safidon

Safidon Safidon Mandi

Pilukhera Nagina

Narwana City Narwana

Garhi

Pipaltha

Data Singh -

Wala.

Dhamtan

Sadar Narwana Dhanoda

Uchana Uchana Mandi

Fatehabad Fatehabad

City FTB

Guru-

Nanakpura

Bus stand

CIA Staff, PO Staff,

Excise Staff

Prosecution Staff,

CAW, Vehicle Theft

Act Cell, Maoist cell,

Sr. Citizen cell,

EOW, Women/Child

Protection Cell

Sadar FTB

Badopal

Dariyapur

Hanspur

Bhuna

Bhattu Kalan

Traffic FTB

Tohana

City Tohana Chd Road

Sadar Tohana Kulan

Jakhal Meyond

Ratia

Ratia Ratia

Mehamira

Nagpur

Bamanwala

Sirsa Sirsa

Rori

Bara Gudha

City SRS

Khairpur

JJ Colony

Sabzi Mandi

HUDA colony

Kirti nagar

Bus Stand

Sadar SRS Malekan

Ding



Traffic

Dabwali City Dabwali Gol Bazar

Sadar Dabwali

Chautala

Ghoriwal

Odhan Zandhwala

Kalanwali Singhpura

Ellenabad

Ellenaband

Rania

Kari wala

Jiwan Ngr

Nihal Singh

Chaupta

Jamal

Bhiwani

Bhiwani

City BWN

Dinod Gate

Jain chowk

BTM BWN

Anaj Mandi

Genl. Hospital

CIA, Detective, Anti

Theft staff, PO staff,

SPL cell, CAW,

EOW, Women &

Child Protection cell,

Civil Line

Sec-13

Sabzi Mandi

Bus stand

Sadar BWN

Mundhal Kalan

Kharak kalan

Gujarni Mor

Juhi

Traffic

Dadri

City Dadri

Sadar Dadri

Adampur

Dadi

Badhra

Bond Kalan Achina Tal

Loharu

Loharu

Behal Chehar Kalan

Siwani

Siwani Jhupa

Tosham Kairu

Bhwani Khera



Commissi

onerate

GGN

West

Gurgaon

City

Gurgaon

City GGN

Khandsa Road

Pataudi chowk

Arjun Nagar

Sec-14

New Colony

CIA West, CIA East,

CIA-III, Women cell

Security Br.

RTI Cell

Summon staff

EOW cell

Police Lines

1stTraffic- Hero

Honda

2nd

Bilaspur

Traffic I/C West

4 Traffic I/C East

Traffic I/C Highways

CIA-I Sec:46

CIA-II Sec:17

Special Staff

Anti Snatching

Sec:10

Anti Burglary Staff

Anti Bangla Deshi

Staff

Anti Car Hijacking

and Anti Vehicle

Theft Staff

Anti Auto Theft east

wing

Escort Guard Lines

Sector-10 Sec-9

Civil line

Udyog

Vihar

Old Sec-5 Sec-4/7

Rajinder Park

Udyog Vihar

Palam vihar

Sec-17, 18

East

Gurgaon

Sadar

Gurgaon

Sadar Gurgaon

Sec-40

Sec-56

DLF

Gurgaon

Sushant Lok

DLF-I

DLF-II PP DLF-III

Sec-29

South

Gurgaon

Bhondsi

Gurgaon

Sohna

City Sohna

Nimoth

Bhondsi

Badshahpur

Kherki Daula

Pataudi

PS Pataudi

1.City Pataudi

2.Heli Mandi

Farukh Nagar

Bilaspur

Manesar

Commissi

onerate,

FBD

Faridabad

Faridabad

PS Sarai Khawaja Palla

Detective,

Anti Theft staff,

PO staff,

SPL cell,

Crime against,

Economic Offences

Wing, Railways,

PS Sector 31 Sector 28

PS Central

Sector 14

Sector 15

Sector 15A

Sector 16



Sector 17 Tele-com.

Traffic

StateWomen &

Child Protection cell,

CIA Cell

Women Cell

Traffic Cell

SRM Guard

Patrolling Staff

Bhupani Kheri Pul

Old Faridabad

RG Chowk

Sector 19

Mujesar Sanjay Colony

Sector 55

Dhoj

Pali

Sikrona

Saron

Dabua Colony

Parvatiya

Colony

Kotwali PP No.2

NIT

PP No.5

PP No.21A

PP No,21D

SGM Nagar

PP No.3 Sainik

Colony

Suraj Kund

Ankhir

Monger. Sector

46

Badkhal

Ballabgarh

Sector 7

Sector 3 Sector

11

Sector 8

Sector 7

City Ballabgarh

Adarsh Nagar

Bus Stand

Chawla-Colony

Aggarwal-

Chowk

Sadar Ballabgarh

PS Tigaon



PS Chhainsa

Governme

nt Railway

Police

ACP Traffic I

ACP Traffic

II

ACP HQs

DSP Ambala

Railway Sub

Division

DSP

Faridabad

Railway Sub

Division

DSP Hissar

Railway Sub

Division

1. CIA Badarpur

2. CIA Naveen

Nagar

3. CIA DLF

4. CIA Bhupani

5. CIA Ballabgrh

6. CIA Faridabad

7. CIA Mujesar

8. ATS Ballabgarh

9. Homicide Cell

PS Traffic

1. PS Kalka

2. PS Chandigarh

3. PS Ambala

Cantt.

4. PS Jagadhri

5. PS Kurukshetra

6. PS Karnal

7. PS Panipat

8. PS Sonipat

1. PS Faridabad

2. PS Rewari

3. PS Gurgaon

PS. Bahadurgarh

1. PS Hissar

2. PS Sirsa

Chandpur

Ambala City



3. PS Rohtak

4. PS Jind

Kaithal

Samalkha

Ganaur

Palwal

1. M.garh

2. Narnaul

3. Dadri

4. Loharu

Pataudi Rd.

1. Jakhal

2. Bhiwani

1. Dabwali

2. Ellanabad

Narwana

FRS No. Business / Functional Requirement

1.1 Portal providing Police to Citizen(P2C) Services (CODE- PR)

1.1.1 Should allow user (citizens) to access portal via the internet to register complaints online.

1.1.2 Should allow users (citizens/petitioners) to search for their request on the basis of Service Request number or petitioner

details.

1.1.3 Should display petition/service request details and status on the screen based on the user search

1.1.4 Should allow users to save the status as a PDF file and/or print the status

1.1.5 Should allow the users to provide comments and feedback on online services

1.1.6 System should allow the user

1. To download all applicable forms as e-forms and submit the same

System should provide the user to download forms for following services through the online portal

1. Complaint Registration

2. Tenant Verification

3. Servant Verification

4. Permission Request for Processions and Rallies

5. Application for Character Certificate

Submit e-form once the user has connectivity

1.1.7 System should provide the user with an Online Help facility

1. Frequently Asked Questions on workflow of applications

2. User Manual on procedures to avail police services

3. Relevant police documents (library)

4. Address / contact nos. of police offices

1.1.8 System should provide the user with the following Transaction Services through the online portal

1. Complaint Registration




5. Passport Verification Status

6. Arm License Verification Status


System should provide the user with the following representative Information Services through the online portal

1. Missing Persons Listing (with Photographs)

2. Proclaimed Offenders Listing

3. Stolen/ Recovered Vehicles Listing

4. Unidentified Dead bodies (with photographs) Listing

5. Abandoned / Unclaimed/recovered Properties Listing

6. Most Wanted Criminals Listing (with photographs)

CAS - STATE FUNCTIONAL REQUIREMENTS

Annexure: CAS (State) Functional Requirement Specifications as released by NCRB/MHA


1.1.9 System should allow the user to input the following details for complaint registration on the online portal (at least 2 should be

mandatory)

1. Mobile Phone Number

2. Address

3. Identifications

3.1 Ration Card Number

3.2 Passport Number

3.3 Bank Account Number

3.4 Voter ID Card Number

3.5 PAN Number

3.6 Unique ID Number

3.7 Electricity Bill Number

3.8 Landline Telephone Number

3.9 Email ID

1.1.10 System should allow the user to view the time taken to process the service request (to monitor service delivery time)

(Technically: system should keep a log of the start time of the registration of the complaint / general service request till such

time that the status of the application is closed; system should diaplay the user at the end of the service fulfillment, the total

time taken to complete the service delivery)

1.1.11 System should provide an acknowledgement to the complainant (once the application has been submitted online) through

1. Mobile Phone (SMS)

2. Email

3. On Screen

1.1.12 System should generate a complaint reference number for retrieval of complaint status information (such as the use of

CAPTCHA feature)

1.1.13 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 forward the complaint to the relevant PS or appropriate authority based on address of the complainant (in

case the PS is not known)

1.1.14 System should allow the user to lodge an anonymous information (in case the user does not want to disclose personal details)

1. User should be able to select from 'Tip'

1.1.15 System should be able to record the IP address of user

1.1.16 System should allow the user to submit C-form to register foreigners

1. Provide for notices to foreigners (leave India notices)

2. Alerts to Interpol

3. Overstay checks and alerts

4. Alerts to immigration database (interface once created)

1.1.17 Should allow user (citizens) to view menu of services available

1.1.18 Should allow automatic carbon copying of generated reports on services to stakeholders.


1.1.19 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"

1.2 Petition/Verification/Request Management Service (CODE-VR)

1.2.1 Should allow the user (police staff) to capture the general service petitions of the citizens based on their request. The general

service requests can be any of the following No Objection Certificates, verification of passport, service, tenant, servant, Lost

cell phone , arms license, permissions for procession,rallies,mikes,etc.

1. Employee Verification




5. Passport Verification Status

6. Arm License Verification Status


1.2.2 Should allow uploading of any relevant documents such as scanned documents/images

1.2.3 Should present different templates/forms for different kinds of petitions/service/verification requests

1.2.4 Should allow the user to assign the petition to police personnel for preliminary enquiry and also forward it to other offices

1.2.5 Should allow the user based on the role to record notes/remarks to the petition.

1.2.6 Should allow the user to search the existing repository of previous cases/petitions/requests before responding to the petitioner.

1.2.7 Should allow for approval by the concerned officer before issuing the certificate.

1.2.8 Should provide the user to entrust / re-entrust the petition and close the petition

1.2.9 Should allow the user to generate the certificate or report or permission or the response to the petitioner

1.2.10 Should allow the user to link / de-link petitions

1.2.11 Should allow the user to merge petitions in case of duplicate petitions/requests

1.2.12 Should provide the reports and search capabilities on the petitions/requests

1.2.13 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

1.2.14 System should allow the user to view the antecedents of the person belonging to other states (in case a verification report has

been prepared for a stranger)

1.2.15 System should forward a request for verification of a stranger (in case the permanent and present address are different) to the

relevant police station

(be it in a different state)


1.2.16 System should allow the user to receive online service request applications from other agencies (such as RPO)

1.2.17 System should dispatch the response of a petition / service request via

1. Email and/or

2. Post

3. SMS

And update the status of the application in the system

1.2.18 System should generate an alert if no action is taken on a petition within 24 hrs (for complaint and FIR) and 7 days for general

verifications, and sent to higher officers.

If 24 hrs / 7 days time limit has been breached a non-compliance report should be generated automatically to all higher offices

1.2.19 System should allow mutilple agencies to carry out verification concurrently such as passport verification by PS and by CID /

district police office should be concurrent

1.2.20 System should allow to capture request for Foreigner

- Registration Certificate

- Registration Permit

1.2.21 System should allow user to generate RC & RP

1.2.22 Should allow the user to view timeline within which to resolve the issue (process step)

1.2.23 This page on the site should carry warning to the user he is liable to be prosecuted for malicious complaint or content in

accordance with the law in force.

1.3 Unclaimed / Abandoned Property Register Service (CODE-UP)

1.3.1 Should allow the user to capture the unclaimed/abandoned property details.

1.3.2 Should allow uploading of any relevant documents such as scanned documents/images and maintenance of online photo

gallery/list of stolen/lost and abandoned property

1.3.3 Should present different templates/forms for different kinds of property (vehicles, cultural, fire arms, cell phones etc.,)

1.3.4 Should allow user to search the lost/stolen property in different case or different police station within the repository.

1.3.5 In case a match is found the system should link the unclaimed/abandoned property with the case

1.3.6 In case if the property wasn’t claimed for more than 6 months then the system should prompt & record the auction details after

requisite approvals.

1.3.7 Should provide the reports and search capabilities on the unclaimed/abandoned property

1.3.8 System should allow the user to search for stolen / abandoned property (based on access rights)

1.3.9 System should generate an alert for the concerned IO if the property seized is already involved in a crime


1.3.10 This page on the site should carry warning to the user that he is liable to be prosecuted for false claim of stolen or unclaimed

properties in accordance with the law in force.

1.3.11 Should allow the user to view the details of the sale proceeds deposited in Govt treasury once the property is auctioned off

after requisite approvals

(SHO and higher officers)

1.4 Complaint and FIR Management Service (CODE-FIR)

1.4.1 System should allow the user to log the complaint details. The complaints would be of different nature (Cognizable and Non-

Cognizable, Missing

Person, Stolen Property, Unidentified dead body,etc)

1.4.2 Should allow uploading of any relevant documents such as scanned documents/images in various formats

1.4.3 Should present different templates/forms for different kinds of complaints

1.4.4 Should allow the user to assign the complaint to police personnel for preliminary enquiry

1.4.5 Should allow the user to record notes/remarks on the complaint.

1.4.6 Should allow the user to search the existing repository of previous complaints before acting on the complaint.

1.4.7 Should allow for approval by the concerned officer before issuing the FIR/NCR.

1.4.8 Should provide the police personal to create the FIR / NCR (Non-Cognizable report) / complaint report for other cases or a

report for juvenile case

1.4.9 Should allow the user to transfer an FIR falling in other jurisdiction(zero FIR)

1.4.10 System should facilitate the closing of a complaint for those complaints which do not proceed for investigation.

1.4.11 System should allow the user to link / de-link complaints

1.4.12 System should allow the user to merge complaints in case of duplicate complaints or cross case

1.4.13 Should allow for complaints to be registered through the PCR Call Interface and Management Service.

1.4.14 Should present the station writer a dashboard with the report summary table consisting of new cases, court disposal, cases

pending arrest, etc.

1.4.15 Should provide the reports and search capabilities on the complaints registered.

1.4.16 System should also allow the user to view crime and criminal data (as per the state specified formats)

1.4.17 System should display the name of the police station / higher office where the compliant was originally registered

1.4.18 System should allow the user to edit the Act and Section for a registered FIR (an alert should be sent to higher office and

judiciary) (only with alteration memo / amended FIR)


1.4.19 System should allow the user to link Unidentified Dead Bodies with Missing Persons

1.4.20 System should allow the user to view a GIS map of the crime location (as soon as case is registered, with details of additional

crimes committed in the same area)

1.4.21 System should provide for automatic dispatch of notifications to Airports & Seaports (ports of entry and exit) on criminal

movements

1.4.22 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)

1.4.23 System should allow the user to send copies of the FIR to a distribution list through email

1.4.24 System should allow the user to create and forward special reports to DIG / IG Range, CID and DGP (in cases of heinous

crime)

1.4.25 System should allow the user to link FIRs with MLCs / Missing Persons / Unnatural Deaths (since they can be converted into

FIRs)

1.4.26 System should provide the following local heads (in addition to others) for FIR

1. Bag / purse lifting

2. Theft by opening bag/purse

3. Theft by snatching bag/purse

4. Unlawful Assembly

1.4.27 System should provide for the following statuses for FIR

1. Pending Investigation

2. FR Submitted

3. Chargesheet Submitted

with an alert sent to District Police Office / Range DIG / Zonal IG / CID (CB) (in some category crimes)

1.4.28 System should allow the user to capture the 'Alias' of complainant, accused, witnesses etc. in the FIR

1.4.29 System should allow the user to capture Finger Print and Retina Scan for accused in FIR

1.4.30 System should generate an email to National Human Rights Commission within 24 hrs in case there is a custodial death and

police encounter deaths

1.4.31 System should allow the user to have information on

1. Hartals

2. All types of Agitations

The investigation of such cases also to be viewed / reported to DySP / Assistant Commissioner and Narcotic Cell

1.4.32 System should allow the user to register cases of wild life crime, and send the report to CBCID HQ and to SIU XI Branch of

CBI and Wild Life Bureau


1.4.33 System should provision for registration of cases under video piracy and a monthly report to be sent to AIG and DySP Crime

Detachment on

1. Number of raids conducted in the District included in the raids conducted in Police Station limits

2. Cases registered with particulars of films, persons arrested

Report to be sent before the 10th of every month

An alert on pending actions to be generated by the system

1.4.34 System should allow for auto transfer of cases registered as a crime againt SC / ST or POC Act to SP (will in turn allign

DySP for investigation)

1.4.35 System should allow the user to capture details on relatives of the Unknown Dead / Injured Person (when traced) under

1. Name

2. Address

3. Contact Details

4. Statement

1.4.36 This page on the site should carry warning to the user that he is liable to be prosecuted for false or malicious reporting of crime

in accordance with the law in force.

1.4.37 Should allow the user to see a complete list of templates of broad heads of crimes to file his compliant.

1.4.38 The page should clearly inform the user

"This is an electronic mode of complaint for immediate response to crime scene attendance or crime prevention

and does not exclude the complainant to visit the police station to deliver a signed copy of the FIR and make his

preliminary statement to the

O.C"

1.4.39 The page should inform the user that after the FIR has been launched, all his subsequent information on line will not be termed

2nd FIR, 3rd FIR and so on.

1.4.40 Should allow the user to see the list of police stations with jurisdictional areas to file complaint in appropriate PS

1.4.41 Should allow the user to view the details in case his FIR or information has been routed to the PS having jurisdiction over his

matter through an Inbox facility

1.4.42 The complaint passed from PCR can be acted upon by PS staff by registering compliant on suo moto basis depending upon

the nature of the compliant otherwise PCR is not the FIR receiving window

1.4.43 Such information may be on display on dash boards of every officer in the PS and higher officers and not only on the

dashboards of PS station writer

1.4.44 Provision to be made for juvenile cases (as per the JJ Act)

1.4.45 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


1.4.46 System should provide for capture of cases for Juvenilles

1. Accused (sent to Juvenile Justice Board)

2. Victim (Childrens Court)

3. Witness (Childrens Court, Regular court - as appropriate)

1.4.47 Provision may be given to make FIR number to five digits

1.4.48 Provision may be given to show the wings / units like Vigilance and Anti Corruption Bureau / CBCID in the FIR

- to be taken in context of entering data pertaining to an agency where the case is being transferred

1.4.49 Missing person registration should be handled as in ZIPNET

- (Comment from NCRB) missing persons registration should incorporate inputs from ZIPNET application as well

1.5 PCR Call Interface and Management Service (CODE-PCR)

1.5.1 The system should display all the unanswered calls and the call/caller details to the user.

1.5.2 System should arrange the incoming calls in the order that come in.

1.5.3 The system should allow the user to answer /respond to the call through the user interface.

1.5.4 The system should allow the user to record the call.

1.5.5 In case the call(s) comes in for an already registered complaint, the system should allow the user to link the call(s) to the

registered complaint.

1.5.6 System should provide an interface to the Police Control Room (PCR) and Police Station users to capture the details of the

complaint and the caller / complainant through a “quick capture complaint form” relevant for a complaint that is reported in

through a phone call, email, walk-ins in emergency or a non-emergency situation. The system should also have the provision

for recording the call along with the timestamp and capture in the system.

1.5.7 In case the caller reports a complaint that is within the jurisdiction of the PCR (either State HQ or District), the system should

allow the user to identify the appropriate police station or available patrol vehicle and transfer the call to the same for response.

1.5.8 In case the caller reports a complaint that is outside the jurisdiction of the PCR (either State HQ or District HQ), the system

should allow the user to transfer the calls to the appropriate police control room that has the jurisdiction.

1.5.9 The system should allow the user to record the details of complaint assignment and the action taken by the responder on the

complaint.

1.5.10 Should provide the reports and search capabilities on the call registered/logged

1.5.11 1. System should provide for generation of status reports and action taken on police calls

2. System should generate reports twice a day and forward the same to higher offices at the district level

1.5.12 System should allow the users to transfer PCR calls to relevant police station

1.6 Investigation Management Service (CODE-IN)


1.6.1 In case of NCR (Non Cognizable Report), the system should allow user to capture the investigation details relevant to a non-

cognizable offence and the approval from the court and prepare a final report for closure of the NCR

1.6.2 System should allow the user to generate an alteration memo and subsequently modify the acts and section details of the

complaint.

1.6.3 Should allow uploading of any relevant documents such as scanned documents/images

1.6.4 System should allow the user to record and transfer a case that does not fall under jurisdiction of the present police station

1.6.5 Should present customized templates/forms for the type of complaint under investigation.

1.6.6 Should allow the user to assign the FIR to other police personnel.

1.6.7 Should allow the user to record notes/remarks on the complaint.

1.6.8 System should change the case status depending on the progress of the investigation.

1.6.9 System should allow the user to record the remarks on the status/case progress.

1.6.10 System should associate pre-defined tasks / activities that are required during the investigation to the case. The tasks /

activities should be customizable by the administrator to the type of the case under investigation. The user should be able to

add / modify tasks / activities to the predefined 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.

1.6.11 Should allow the user to capture the details of the investigation relevant to the type of the complaint. Indicative details captured

during investigation are given below.

• Crime scene details

• Victims Details

• Accused Details

• Witness Details

• Property Details (stolen/seized)

• Evidence details

• Forensics details

• Medico Legal Case Details

• Other details in the crime details form

1.6.12 System should allow preview and printing of all the required forms (7 IIF’s, forms required for preparing the case diary and

other forms necessary for

submission to the external entities such as courts)

1.6.13 In case of death, system should allow the user to capture results conducted for inquest (whether person was hurt, details of

clothing etc.,) and generate an inquest report.

1.6.14 System should capture the inquest report generated by the magistrate incase of death in police or judicial custody or death of

lady within 7 years of marriage.

1.6.15 System should allow the user to prepare, preview, print requests/forms that are sent to external agencies (FSL, FPB, hospitals,

RTA etc.,) for expert opinion. The request/forms should be made available to the user as templates that are managed

(created/edited) through administration functionality.


1.6.16 System should provide the feature to capture the response in the form of parameterized data and scanned documents

received from different external agencies.

1.6.17 System should allow the user to prepare, preview and print arrest card

1.6.18 System should allow user to capture the court surrender details

1.6.19 Should allow the user to capture the interrogation details as summary and parameterized data.

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

1.6.21 System should allow the user to view the detailed and summary views of the case

1.6.22 System should allow the user to prepare the final report (charge sheet/ challan, undetected, untraced, mistake of fact, civil

nature). System should prompt the user with the list of documents required for filing a charge sheet.

1.6.23 System should allow the case to be re-opened and reassigned to a different investigating officer. In case of re-opening, the

case history should be maintained.

1.6.24 System should also track the remarks/suggestions posted by higher officers /circle officers during investigation.

1.6.25 System should present to the IO , dashboard of under trials, under investigation, re-opened cases, etc and to other users

based on their roles(IO) and their jurisdiction.

1.6.26 System should provide the dashboards to higher officials about the case progress and metrics about PT cases etc.,

1.6.27 System should allow the SSP & Senior Officers to view the summary of cases based type of case and cases falling in their

jurisdiction

1.6.28 System should present the SHO & Senior officials about the details of the cases based on the status like open, closed, re-

open, disposed, unresolved and case pending for trial.

1.6.29 Should provide the reports and search capabilities on the case progress.

1.6.30 System should allow the user to capture the finger print of an arrested person (through scanned image)

1.6.31 System should allow supervisory Officers to provide their instruction/remark mandatorily on progress report of Special Case

Report (Heinous Crime)

& voluntarily for Non-Heinous Crimes

1.6.32 System should allow the user to record details of the property released during investigation

1.6.33 System should allow the user to record details of partial recovery of properties during investigation

1.6.34 System should allow the user to prepare a dossier of the criminal (as per procedures, where ever required)

1.6.35 System should allow the user to enter data received from Forensic Science Labs on a case during investigation


1.6.36 System should allow the user to update the status of case property as

1. Released

2. Transferred

3. Sent to Police Station

4. Sent to Forensic Lab / Forensic Medicine Department

5. Sent to Court (as evidence)

1.6.37 System should allow the user to capture victim information under

1. Number of persons deceased

2. Number of persons seriously hurt

3. Number of persons with simple hurt

4. Number of non-injured persons

5. Gender

6. Age

7. SC / ST

8. Economic Strata

9. Educational Qualification

10. Nationality

11. Religion

12. Identity

13. Address

14. Contact Details (Telephone / Mobile / Email)

1.6.38 System should provide the user (investigating officer) with

1. Crime and criminal information

2. Address tracking of mobile users

3. Help book on investigating procedures through his / her mobile phone

1.6.39 System should allow the user to record and print witness statements

1.6.40 System should allow the user to record and print Motor Vehicle Inspection Reports

1.6.41 System should allow the user to capture the case diary details (in a parameterized format)

1.6.42 System should provide for an alert to the user in cases where accused identity is not known, but

1. Similar case has been registered, where accused identity is found to be near description

2. Similar case is registered with same modus operandi

3. An arrest has been made in an another case with similar accused description

1.6.43 System should allow the user to take out print outs of witness statements at the time of charge sheet


1.6.44 System should send alerts in the below cases, to concerned District SPs and SP CID

1. Murder Cases where no significant progress is made even after 72 hours of investigation

2. In all murder cases in which the accused are not identified in FIR

3. Explosions in which more than one person is killed.

4. All cases of seizure of spirit in which the seized quantity exceeds 5000 litres.

5. All cases of seizure of Narcotic and Psychotropic Substances other than Ganja, except those where the quantity of the

substance seized does not exceed the prescribed "minimum for personal consumption or small quantity".

6. Cases of theft of Government Arms and Ammunitions and theft or loss of Government property over Rs. 10 lakhs.

7. All Women Trafficking Cases having interstate linkages.

8. Cases of Cheating or fraud by private financial institutions where the total transactions involved or the deposits collected by

the accused exceed

Rs. 2 Crores in that particular case or other cases of a similar nature involving the same accused.

9. Cases other than traffic accident cases in which Police Officers of and above the rank of CI figure as accused except

petitions endorsed by Courts under Sec. 156(3) CrPC.

1.6.45 System should prompt the police user with the list of documents and list if witnesses required for filing a charge sheet.

1.6.46 System should also track the action taken by the investigation officers on the remarks/suggestions posted by higher officers

during investigation

1.6.47 The concerned police officer as user of the system only should be allowed to capture the details of investigation

1.6.48 Finger print should also be allowed to upload through an electronic reader and a photograph through a web cam

1.6.49 Provision for 'Dying Declaration' under 32 Indian Evidence Act to be made

1.6.50 Property Seizure Form

1. Linkage of confession statement with items confessed

2. Facility to add GD number against un-linked property under the same FIR number

3. Tool-tip for confession statement during property linkage

1.6.51 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 characterstics should be displayed (based on NCRB code

)

1.6.52 System should provide for digitization of

Bad Characters Roll A - SHO of the PS will be required to enter the details of a bad character under survellience (in case

the person is in the same district)

Bad Characters Roll B - SHO fills in the roll B in case the person moves out of the district

1.6.53 Investigation - Disclosure of the Accused person may reveal Co-accused For this purpose Section 82 and Section 83 of the

CrPC may be referred System should provide for

- capture of details for co-accused

- Attachment of assets of the co-accused (absconder) under Section 83 CrPC

1.6.54 System should provide to add multiple entries under MLC report


1.6.55 System should provide to add multiple entries for 'Victims eligible for compensation'

- would need to be flagged individually

1.7 Court and Jail Interface & Prosecution Management Service (CODE-CJP)

1.7.1 System should allow the user to capture the charge sheet acknowledgement details (interim and final) received from the court

after the submission of the Charge Sheet.

1.7.2 System should allow the user to capture the summons/warrants issued by court.

1.7.3 System should allow the user to assign the summons/warrants to police personnel.

1.7.4 System should allow the user to record the status of execution on the summons/warrants.

1.7.5 In case accused applied for bail, system should allow the user to record the bail details

1.7.6 System should allow the user to capture the Trial update / Court disposal form. Indicative details captured during trial day of

the case are given below

• Court Disposal Details

• Next hearing date

• Trial Status of the persons involved (Attendance, Examination, Bail Plea, Required for Next Hearing,etc)

• Bail

• Accused Status

• Court Order

1.7.7 System should allow the user to capture details if the convicted appeals in the higher court.

1.7.8 System should allow the user to capture the status (granted re-trial, appeal denied) of the appeal

1.7.9 System should allow the user to capture jail / remand related information (release from jail, sent on judicial remand, sent to

police custody …).

1.7.10 System should allow the user to manage and handle the split cases.

1.7.11 System should allow the user to proceed for re-investigation if ordered by the court.

1.7.12 The solution should provide the IO to view the tasks that he/she had set in calendar, the court appointments,

summon/warrants and Administrative related tasks.

1.7.13 The system should allow the prisoner / suspect / arrested / convict / acquitted movements into and out of jails.

1.7.14 System should present court constable with dashboard including court appointment schedule, summary of charge sheets,

case disposed by court, summons and warrants,etc

1.7.15 System should allow the user to capture remarks of the Public Prosecutor before the finalization of the Charge Sheet

1.7.16 System should allow the user to capture details of

1. Witnesses

2. Witness statements

3. Next Trial date

4. Trial Outcomes / Results


1.7.17 System should allow the user to capture details of the receipt of FIR from court

1.7.18 System should provide for preparation of calendar (daily, weekly, fortnightly) for cases scheduled for hearing

1.7.19 System should allow the user to generate report on disposal of cases in the prescribed format (state wise)

1.7.20 System should provide an alert to the SHO and IO on cases of 'impending expiry of remand period'

1.7.21 System should allow the user to capture details of accused who have escaped from custody and match the same with

1. Arrests made

2. Unidentified dead bodies

1.7.22 System should allow the user to know the status and monitor of summons / warrants issued to police stations outside their

jurisdiction

1.7.23 System should allow for generation of alerts on unexecuted warrants

1.7.24 System should allow the user to capture details of attempts made for summon warrant execution

1.7.25 The movement of each UTP from and into the jail be properly accounted for.

1.7.26 In Tamil Nadi different numbers given when a case is transferred to other courts - (the following data fields are additionally

captured)

1. Court Case No

2. Preliminary Registration no.

3. SC no.

4. Multiple court case numbers

5. Date of sending case to sessions and other courts

1.7.27 System should provide for

- Joint Trial

in court disposal form and in trial form

1.7.28 During court trial; in cases where

- Some of the charges under some specific sections are not proved there should be an option to capture the sections which

are proved and which are not proved (against a partcular accused)

1.7.29 Special Warrants - 'Type of Warrants' (for National / International Criminals)- DW Warrant (Distress Warrant)

- BW Warrant (Bailable Warrant)

- Notices

- Red Corner Notice

- Blue Corner Notice

- Yellow Corner Notice

- Others

1.7.30 Trial details can be flexible & target can be set, which could mean that a Superior Court or High Court may fix a deadline to

complete the trial, in which case, it should be reflected in the screens during the trial so as to keep reminding the concerned

officer.


1.7.31 System should provide for Case Split

1. Under 'Trial Details' - capture data 'hearing date' wise

1.a Hyperlink dates

1.b Radio button to select split on a given hearing date

1.c Ability to select an accused to continue with parent case and others to continue with additional CC number

1.7.32 System should provide for 'Tracking of Appeal Cases '

1.7.33 System should provide for 'Change of IO '

1. In most of the cases IO can be changed

1.8 Crime and Criminal Records and Query Management Service(CODE-QR)

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

1.8.2 Should provide the user a quick search for given case ID

1.8.3 System should also provide an advanced search capability and allow user filter the search to a greater detail like crime details,

suspect details, victim details, modus operandi, property, victim, arrested, suspect, witness, guarantor/surety, habitual offender

details,etc

1.8.4 The system should allow the user to configure / build a query on the searchable data through query builders.

1.8.5 System should provide the ability to store, load and delete custom queries to each user for easy retrieval.

1.8.6 System should allow the user to organize the search results sort by clicking on table header

1.8.7 System should organize the search results in paged manner. It should also provide user the flexibility to navigate to the

required page.

1.8.8 System should provide standard formats for the data from external sources (Vehicle Registration, Driver License, Phone (cell

and land line from multiple providers) Numbers, Voter Details, Educational / Academic Certification Data) and a utility to

capture the data into the investigation toolkit- data repository.

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

1.8.10 System should maintain the history of data in case of modifications (ex, vehicle transferred to a new owner, an old cell phone

number acquired by a

new user,…)

1.8.11 System should provide the user with an ability to search (full and partial strings) the investigation-toolkit-data 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.

1.8.12 In case the searched entity has a history of ownership, the same should be presented in the search results.

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


1.8.14 If a user requests access to, or searches for, a case which he does not have the right to access, the System must provide one

of the following responses (selectable at configuration time):

display title and metadata;

display the existence of a case but not its title or other metadata;

Do not display any case information or indicate its existence in any way.

These options are presented in order of increasing security. Note that the requirement in the third option (i.e. the most

stringent) implies that the System must not include such cases in any count of search results; this level of security is normally

appropriate for cases dealing with matters such as national security.

1.8.15 If a user performs a quick or advanced search, the System must never include in the search result list any record which the

user does not have the right to access.

1.8.16 System should provide the user with search hints / tips on data fields such as

1. Names

2. Locations

3. Objects

1.8.17 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)

1.8.18 System should allow the user to conduct an advanced search based on sub parameters on a major data field

1.8.19 System should provide for similar features to a Soundex function for searches on

1. Names

2. Places

3. Objects

1.8.20 System should provide for the following additional options in the MLC register

1. Hit by train

2. Crossing the Line

3. By Crushing

1.8.21 System should allow the user to enter age of a new born child in 'Days'

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

1.8.23 The linkages should be provided in the system with the transport department, the office of the Dy Commissioner , courts,

educational institutions and university and other stake holders .

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

1.8.25 The system should assist the IO and higher officers with court’s judgments to guide them in investigation


1.8.26 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

1.9 Police Email and Messaging Service (CODE-EM)

1.9.1 Should allow the user to create or import the organizational hierarchy and the users of the police department.

1.9.2 Should allow the user to select the user list from the organization hierarchy

1.9.3 Should allow the user to create personal address book, groups

1.9.4 Should allow the user to send messages to groups.

1.9.5 Should allow the user to create & select templates for message standardization

1.9.6 Should allow the user to choose the option for read receipt

1.9.7 Should allow the user to search the messages from the archive based on message subject and between two dates

1.9.8 System should allow the user to choose the option of encrypting the message

1.9.9 System should allow the user to print the message in printer friendly format

1.9.10 System should allow the user to subscribe to alerts on cell phone in case of receiving a new email in the inbox.

1.9.11 System should show the usage statistics at all levels and departments.

1.10 Periodic Crime and Law & Order Reports and Review Dashboard Service (CODE-R)

1.10.1 System should present customized dashboards and reports to the users based on their role -Duty Constable, Court Constable,

Station Writer, IO, SHO, Circle Inspector, ACP, DCP, Sub-Divisional Officer, CP,SP, DIG,IG,DG, other higher officers in

Administration

1.10.2 System should present various statistics such as summarized information, current progress, monthly numbers, comparative

statements, trends with charting capability, exception reports, crime maps indicating the hot spots.

1.10.3 System should allow the user to view on alerts/events/reminders

1.10.4 System should present the user with statistics of all petitions

1.10.5 System should present the user with statistics on “Newly Registered complaints”

1.10.6 System should present the user with statistics on NCR’s (Non Cognizable cases).

1.10.7 System should present the user with statistics on FIRs with different statuses such as New/Under Investigation/ Pending Trial/

Re-opened

1.10.8 System should present the user with statistics on Warrants & Summons


1.10.9 System should present the user with court calendar which includes details on court appointment schedule, information on the

cases under trial

1.10.10 System should present the user with activity calendar

1.10.11 System should present the user with statistics and list of “high priority FIR” (Grave /Heinous Crime Details)

1.10.12 System should present the user with list of Pending Arrests & Wanted Offenders/Suspects

1.10.13 System should present the user with statistics of charge sheets & Court Disposal

1.10.14 System should present the user with list of latest happenings across police stations such as missing persons & unidentified

dead bodies

1.10.15 System should present the user with prisoner movement updates

1.10.16 System should present the user with Major and Minor head wise statistics

1.10.17 System should present the application usage statistics that provide indicators on the application uptake and usage by the

police personnel

1.10.18 System should allow the user to drill down to a granular level to a complaint or suspect from the information presented in the

dashboard.

1.10.19 System should provide the user an interface to enable the senior officers to conduct periodic reviews of the police station

(citizen services, law &

order, crime,etc)

1.10.20 System should allow the user to generate comparative statements of the above said statistics during monthly crime reviews.

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

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

1.10.23 System should consolidate and generate statistics based on the role and jurisdiction

1.10.24 System should allow the user to view a list of Active Criminals on the dashboard

1.10.25 System should allow the user to generate reports on

1. Number of arrests made (as a data field in Special Report, Heinous Crime Cases)

1.10.26 System should allow the user to generate Daily/ Morning Situation Report

1.10.27 System should allow the user to generate report on

1. Number of criminals arrested during a day

1.10.28 System should allow the user to generate a crime chart with

1. Details on Cyber Crimes

2. Financial Frauds


1.10.29 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

1.10.30 System should allow the user to generate report on cases pending (with prosecution action awaited)

1.10.31 System should allow the user to create a 360 Degree profile for dangerous and most wanted criminals (dossier)

1.10.32 System should generate an alert in case the Case Diary is not handed over within 10 days of transfer

1. The act of the officer will be deemed to be an act of obstruction to further investigation and as an act of suppression of

relevant evidentiary material

SPs concerned may initiate action for such delinquency after evaluating the circumstances of each individual case of non-

compliance

1.10.33 Haryana:

We have proposed a List of Monitored Cases which will have only selected cases for close monitoring (to be decided by the

SHOs/Supervisory officers).

Remaining cases will be monitored only from the point of view of service of summons, execution of warrants etc.

1.11 Notification of Alerts, Important Events, Reminders and Activity Calendar or Tasks Service (CODE-AR)

1.11.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 (attention diversion gangs) registered in a police station, in case a general petition for a procession or

road work has been approved, an alert on the same well in advance to the affected police station(s), alerts in case an activity is

pending for more than a week or an advance alert in case the stipulated time is about to expire (ex, police remand about to

expire and the IO has to file for remand extension), a case coming up for trial where the IO has to be present as a witness, ….)

1.11.2 System should automatically generate reminders of any pending or overdue actions on the cases that are pending registration

/ investigation / trail.

1.11.3 System should allow the user to create and send user alerts / events / reminders to identified group / subscribed users / police

stations.

1.11.4 System should allow the user to schedule the activities and maintain the calendar with reminders.

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

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


1.11.7 System should allow the user to generate alerts for SHO and IO in cases where a witness is used 'as a witness' in multiple

cases (stock witnesses)

1.11.8 System should allow the user to generate alerts for IG / DIG / SSP / SP / SHOs officers where an FIR is registered against

Naxal / Maoist / Terrorist / Insurgent Activities

1.11.9 System should generate an alert in case an Act and Section has been modified in for an FIR, and send it to

1. DIG / SP / SDPO / DCP / ACP / CO

1.11.10 System should generate an alert for SHO, IO, SP every fortnight (after the arrest and judicial remand till chargesheeted) and '

everyday for the last 7 days ', where a chargesheet needs to be filed for an accused who is in jail

1.11.11 System should allow the user to generate alerts for

1. Periodic progress of special report cases

2. Date of chargesheet of special report cases

1.11.12 System should generate an alert for an IO '3 days in advance' before bail hearing date

1.11.13 System should provide generation and transmission of SMS (to SP / DSP) on

1. Conviction Details

2. Summons / Warrants Details (if not served within the prescribed time limit / 3 days before the court date)

1.11.14 System should provide for generation and transmission of SMS (to all SHOs) on details of criminals released from Jail

- and for important criminal / offendors in sensational cases to SPs

1.11.15 System should generate alerts on

1. Court Case Hearing Date (to orginal PS (SHO) and concerned IO)

2. Charge Sheet Submission

3. Release and Parole Date

4. Bank Robberies, Dacoity (in other districts states) (to SPs)

5. Accused / Arrested (in other police stations as well)

6. Heinous Crime Case Details

7. Special Report (juvenile, sc st, old age, etc)

8. Express FIR cases

9. Missing Persons

10. Stolen Vehicles

11. Unidentified Dead Bodies

12. Interstate Gang Operations

13. Firearms Stolen

15. Hue and Cry Notices

16. Terror Offences

17. State CID Instructions

18. Political Agitations

19 Filing Revision / Appeal / SLPs

20. Visit of VVIPs


1.11.16 System should generate an alert wherein a professional criminal is released from Jail and send the same to

1. Police Station of the resident area

2. Police Station of the area, where he / she has committed crime in the past

3. All police stations, where similar modus operandi has been reported in the state

1.11.17 System should have a Dictionary of common names and each time a new name is entered the master data for names should

be updated. Also there should be a system generated alert when the user tries to enter a new name which is not there in the

list of suggested names.

Example: when the user has entered Raje, system should show the various suggestions like Rajeev, Rajesh etc. and incase a

user enters RajeevX, system should show an alert saying that "please correct the name if the entered name is incorrect"

1.11.18 System should allow the IO to select an appropriate distribution list from a master list of email to send any alert

1.12 State-SCRB-NCRB Data Transfer and Management Service (CODE-DT)

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

1.12.2 The data extracted from States/UTs must be transformed into standard formats required by NCRB.

1.12.3 The data should be run through a quality process to identify any possible duplicates or wrong data before sending to NCRB

1.12.4 Transformed and cleansed data must be uploaded on to NCRB databases

1.12.5 The system should provide the flexibility to cleanse and transform data

1.12.6 The system should support automatic extraction of data

1.12.7 System should provide an option to monitor and manage data extraction, Transformation and loading process

1.12.8 System should allow the user to kick start the load process manually in the absence of load failure

1.12.9 System should allow reconciling those records which failed during the load process.

1.13 State CAS Administration and Configuration Management Service (CODE-CR)

1.13.1 The solution should provide the user to customize the application without affecting the core.

1.13.2 System should allow the user to change the look and feel like font, skins, images of the application

1.13.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, Ranges, Zones and police stations.

1.13.4 System should allow the user to define the organization all its units (police stations, districts, range, zone) and user hierarchy


1.13.5 System should present the data elements based on major and minor heads selected by user.

1.13.6 System should generate reports based on roles defined.

1.13.7 System should allow the user to add/modify/delete/modify-order of acts, sections and local laws.

1.13.8 System should provide the user to add/modify/delete/modify-order of property-type/castes/tribes details.

1.13.9 System should not allow the user to delete/modify/modify-order of the master data provided by the centre.

1.13.10 System should allow the user to maintain different templates as per the directive of local governments or standard guidelines,

circulars, standing orders.

1.13.11 System should allow the user to maintain case specific service levels/time limits/measurable indicators for each step in the

case progress from registration to investigation to trial.

1.13.12 A change in service levels/standards/benchmarks should be maintained/tracked by the system with start and end dates

1.13.13 A change in role/designation should be maintained/tracked with start and end dates

1.14 User Help and Assistance Service (CODE-UH)

1.14.1 The solution should provide detailed context-sensitive help material for all the possible actions and scenarios on all user

interfaces in the application.

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

1.14.3 The solution should have comprehensive help facility wherein the users can obtain system specific technical / functional help

on line

1.14.4 The help should be accessible to the users both in the offline and online mode

1.14.5 The system should maintain and make available to user a database of frequently asked Questions

1.15 User Feedback Tracking and Resolution Service CODE-UFT)

1.15.1 The solution should provide an interface for the user to log any defects or enhancement requests on the application and track

thereafter.

1.15.2 The solution should send alerts (e.g., email, SMS) to the user if the user chooses to whenever any action has been taken on

the alert

1.15.3 The solution should enable the user to track the submitted defect or enhancement request.

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

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


1.16 Activity Log Tracking and Audit Service(CODE-LA)

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

• All the actions (create/read/update/delete) that are taken upon the critical entities (case, suspect, property,…) in the system

• The user initiating and or carrying out the action;

• The date and time of the event.

• Administrative parameters

The word “unalterable” is to mean that the audit trail data cannot be modified in any way or deleted by any user; it may be

subject to re-department

and copying to removable media if required, so long as its contents remain unchanged.

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

1.16.3 The System must maintain the audit trail for as long as required, which will be at least for the life of the case to which it refers.

1.16.4 The System must ensure that audit trail data is available for inspection on request, so that a specific event can be identified

and all related data made accessible, and that this can be achieved by authorized external personnel who have little or no

familiarity with the system.

1.16.5 The System must be able to export audit trails for specified cases (without affecting the audit trail stored by the System). This

functionality can be used by external auditors, who wish to examine or analyze system activity.

1.16.6 The System must be able to capture, store and report violations (i.e. A user’s attempts to access a case to which he is denied

access), and (where

violations can validly be attempted) attempted violations, of access control mechanisms.

1.16.7 The System must at a minimum be able to provide reports for actions on cases organized:

• By case;

• By user;

• In chronological sequence.

1.16.8 Any access to cases and all other activities involving the cases and related documents or data should also need to be stored in

the audit trail to ensure legal admissibility and to assist in data recovery.

1.17 User Access and Authorization Management Service (CODE-AA)

1.17.1 The system must allow the user to create / update / delete user and user profile.

1.17.2 The System must allow the user to limit access to cases to specified users or user groups.

1.17.3 The system should provide for role-based control for the functionality within the system.

1.17.4 The System must allow a user to be a member of more than one group.

1.17.5 The System must allow only admin-users to set up user profiles and allocate users to groups.


1.17.6 The System should allow a user to stipulate which other users or groups can access cases.

1.17.7 The System must allow changes to security attributes for groups or users (such as access rights, security level, privileges,

password allocation and management) to be made only by super-user.

1.17.8 System should allow the user to those functionalities that he/she is authorized to access.

1.17.9 System should allow a maximum of three attempts to login.

1.17.10 System should allow the user to regenerate a lost password/reset password with set of hint questions

1.17.11 System should encrypt the user passwords

1.17.12 System should allow creation of new users, transfer of postings for existing users and any other actions that affect their

authentication and authorization settings.

1.17.13 System should allow changes in roles/ authorization with the transfer / promotions of staff

request for p s ystem i - ncrb.gov.inncrb.gov.in/bureaudivisions/cctnsnew/data/all state...

Documents