tender no.: 75/cctns/scrb/wb date: 7th july, 2011...

Tender Document for Selection of System Integrator (SI) Under CCTNS Project

Tender No.: 75/CCTNS/SCRB/WB

Date: 7th July, 2011

Crime & Criminal Tracking Network and Systems

(CCTNS)

Implementation of CCTNS

In

West Bengal

Annexure to the Volume I of the RFP

Issued By

State Crime Records Bureau, West Bengal

2 Annexure to the Volume I of the RFP for selection of system integrator for CCTNS, West Bengal

Implementation of CCTNS (Crime & Criminal Tracking Network and System) in West Bengal

Table of Contents Annexure: Project Governance Structure ..................................................................................................... 3

Annexure: Details of the Existing Legacy Systems ........................................................................................ 5

Annexure: SWAN Overview for West Bengal ............................................................................................. 12

Annexure: AS – IS ICT Infrastructure Details ............................................................................................... 23

Annexure: Infrastructure at Police Computer Training Institutes .............................................................. 26

Annexure: List of Police Computer Training Institutes in West Bengal ...................................................... 27

Annexure: Scope of Services ....................................................................................................................... 29

Functional Requirements Specifications for CAS (State) ........................................................................ 29

Additional State Specific Application Functionalities ............................................................................. 48

Sample Traffic Police Reports ................................................................................................................. 53

Non Functional and Technical Requirements ......................................................................................... 55

General Considerations and Constraints ................................................................................................ 65

Annexure: Details of the Technology Stacks for CAS (State) and CAS (Center) .......................................... 68

Annexure: District Maps ............................................................................................................................. 75

Annexure: Unit Details .............................................................................................................................. 115

Annexure: Police Stations with Power/Connectivity Issues ..................................................................... 171

Annexure: Indicative Physical Layout of a Police Station ......................................................................... 172

Annexure: Detailed Process flows for Functions Performed in Police Stations ....................................... 173

Annexure: Indicative Hardware Bill of Material ....................................................................................... 189

Annexure: Indicative Technical Specifications for CCTNS Solution Components ..................................... 196

Annexure: Indicative Network Architecture Details ................................................................................. 225

Annexure: CIPA Data Volume ................................................................................................................... 232

Annexure: List of Locations where CCIS is Installed .................................................................................. 235

Annexure: Post Implementation Support Services ................................................................................... 236

Annexure: CCTNS Implementation Plan ................................................................................................... 241

Annexure: CCTNS Rollout Plan .................................................................................................................. 253

Annexure: Service Levels for CCTNS Solution ........................................................................................... 254

Annexure: Indicative Project Organization Structure of the selected bidder ........................................... 277

Annexure: Sample Registers ..................................................................................................................... 278

Annexure: Physical paper base data conversion Strategy ........................................................................ 281



Annexure: IIF Forms .................................................................................................................................. 285

Annexure: Project Governance Structure The CCTNS project envisages transforming the data capturing and the reporting into a simple,

transparent, orderly and humane process. Implementing such a program that would impact citizens in a

direct manner and has linkages with a wide-ranging set of stakeholders is likely to encounter various

challenges. Following bodies/committees are suggested for the governance and monitoring of the entire

project

State Apex Committee

The broad functions of the State Apex Committee include the following:

1. Reviewing progress of the project

2. Overseeing utilization of the funds

3. Policy Directions and Guidance for successful execution of the project

4. Ensuring continuance of Mission Leader for sufficient duration

5. Creating a supporting environment for the success of the project

The composition of State Apex Committee is as following:

Member Designation

Chief Secretary

Principal Home Secretary

DGP, WBP

Commissioner of Police, KP

Nodal Officer (CCTNS Project)

Any other member co‐opted from the field of IT, Telecom, etc.

State Empowered Committee

The broad functions of the State Empowered Committee include the following:

1. Disbursement of funds to districts and other units/agencies

2. Approval of BPR proposals

3. Sanction for various project components, as may be specified, including the hardware/software

procurement as per the specifications from NIC.

4. Approval of various project components and functionalities to be covered in the project.

5. Review progress of the project

6. Ensure proper training arrangements



7. Ensure deployment of appropriate handholding personnel. With continuous feedback of the

trainee officers and the SPMU, the State Empowered Committee shall ensure that handholding is

effective enough to meet the requirements of successful project execution

8. Other important policy and procedural issues

9. Guidance to State/District Mission teams or other delegated officers

10. Presiding over regular meetings with State/District Mission teams (bi - weekly meetings towards

the starting phases of the project and monthly towards the closing phases of the project.)

11. Ensure ownership with regards to the CCTNS Project by:

a. Overseeing the result of examination / evaluation of trained personnel on site

b. Publicly acknowledging the top 100 data entry personnel through a monthly report that

may be sent to every PS.

The composition of the state empowered committee is as following:

Member Designation

DGP, WBP

ADG, Welfare, WBP

ADG, Housing, WBP

ADG, Training, WBP

JCP (Admin), KP

Joint Secretary, Home

Joint Secretary, IT

Joint Secretary, Finance

DGP, SCRB


Senior Technical Director NIC, WB

State Core Committee

The composition of the core committee is as following:

Member Designation

ADG, Welfare, WBP

JCP (Admin), KP

DGP, SCRB


Special Guest (Mr. Sanjay Singh)

Annexure: Details of the Existing Legacy Systems

Sl No.

Application Name

Description of Services provided

by Application

Application architecture

(Centralized / Decentralized

)

Development Platform –

Web Enabled or not

Operating

System

Database Developed by

Location (HO/DO/ZO/

MO/Any other level)‐ Centralized / Decentralized

Comments

1 Talash Info System

1. Database for missing and kidnapped persons, unidentified dead bodies

2. Generation of fixed format reports

3. Matching of missing persons with unidentified dead bodies

4. Total Data Volume in Talash includes 85452 records (since 2004)

Decentralized Not Web Enabled

Windows Server 2003/2000

SQL Server 2000

NCRB Decentralized Visual Basic front end.

2 MVCS 1. Database for the details


Windows Based

SQL Server




Sl No.

Application Name


by Application



)


Web Enabled or not

Operating

System


Location (HO/DO/ZO/


Comments

of stolen/recovery of the stolen vehicles

2. Verification on enquiry about used vehicles and generation of NoC

3. Reporting and MIS generation

4. Total Data Volume in MVCS comprises of 16654 cases for the period 2000 – 2009

2000

3 Stolen & Recovered Fire Arms

1. Data entry for stolen and recovered fire arms, ammunition


Windows Based

MS ACCESS




Sl No.

Application Name


by Application



)


Web Enabled or not

Operating

System


Location (HO/DO/ZO/


Comments

s etc. 2. Generation

of fixed format reports

3. Total Data Volume comprises of 14636 cases for the period 2000 – 2009

5 Crime in India

1. Database for all types of crimes under IPC, local and special laws

2. Publishing of results in web through PDF files.

3. Generation of operational reports


MS-DOS MS-DOS file system

MHA Decentralized



Sl No.

Application Name


by Application



)


Web Enabled or not

Operating

System


Location (HO/DO/ZO/


Comments

6 TCTS 1. Thana Criminal Tracking System (TCTS) was a Thana level initiative undertaken 4/5 years ago.

2. The objectives for this initiative were similar to that of CCTNS. It was supposed to roll up to DCTS (District Level) and finally to SCTS (State Level).

3. It was in the middle of



Sl No.

Application Name


by Application



)


Web Enabled or not

Operating

System


Location (HO/DO/ZO/


Comments

TCTS initiative that CIPA was conceived. Subsequently, the rollout of TCTS was stalled.

4. From a Data Base perspective it was decided that TCTS Data Base would be converted into CIPA Database.

5. Bridge software was developed by Webel to facilitate the process of converting



Sl No.

Application Name


by Application



)


Web Enabled or not

Operating

System


Location (HO/DO/ZO/


Comments

TCTS DB into CIPA DB.

6. However, the effort turned out to be unsuccessful and TCTS initiative was scrapped altogether.

7 FICN 1. The Fake Indian Currency Notes System involved Data entry for the details of fake notes such as denomination, no., series etc.

2. Fixed format

report


Windows Based

MS-Excel SCRB Decentralized



Sl No.

Application Name


by Application



)


Web Enabled or not

Operating

System


Location (HO/DO/ZO/


Comments

generation.

3. For the

period 2006

- 2009, the

following

data is

stored in

FICN: 679

Reported

Cases of

Fake note

seizure,

122630

Pieces of

Seized

Currency

amounting

to a total

value of Rs.

5,12,5,4974

Annexure: SWAN Overview for West Bengal

1. WB SWAN Overview



2. WB SWAN: Horizontal Connectivity

3. Present list of SWAN POPs at State

Summary of district wise POPs for WBSWAN:

Sl. No. District No. of POPs

1. Kolkata - State Switching Centre ( Writers' Buildings ) 1

2. Darjeeling 14

3. Hooghly 18

4. Howrah 15

5. Jalpaiguri 15

6. Malda 16

7. Murshidabad 27

8. Nadia 20

9. 24 P (North) 23

10. Paschim Medinipur 30

11. Purba Medinipur 28

12. South 24 Parganas 30

13. Uttar Dinajpur 10

14. Dakshin Dinajpur 8

15. Coochbehar 15

16. Purulia 20

17. Bankura 23

18. Birbhum 21

TOTAL 334

The above list excludes 34 POPs in Bardhaman district which were connected previously during

WBSWAN expansion in Pilot district Bardhaman.

Detailed list of POPs for WBSWAN:

Sl. No. District Location Coverage

1. Coochbehar Coochbehar DHQ

2. Coochbehar Coochbehar Sadar SDHQ

3. Coochbehar Coochbehar-II BHQ

4. Coochbehar Dinhata SDHQ

5. Coochbehar Dinhata-II BHQ

6. Coochbehar Sitai BHQ

7. Coochbehar Mathabhanga SDHQ

8. Coochbehar Mathabhanga-I BHQ

9. Coochbehar Mathabhanga-II BHQ

10. Coochbehar Sitalkuchi BHQ

11. Coochbehar Mekhligunj SDHQ

12. Coochbehar Mekhligunj (Changrabanda) BHQ

13. Coochbehar Haldibari BHQ

14. Coochbehar Tufangunj SDHQ

15. Coochbehar Tufangunj-II BHQ




16. Jalpaiguri Jalpaiguri DHQ

17. Jalpaiguri Moynaguri BHQ

18. Jalpaiguri Dhupguri BHQ

19. Jalpaiguri Rajgunj BHQ

20. Jalpaiguri Mal SDHQ

21. Jalpaiguri Mal BHQ

22. Jalpaiguri Metiali BHQ

23. Jalpaiguri Nagrakata BHQ

24. Jalpaiguri Alipurduar SDHQ

25. Jalpaiguri Alipurduar-I BHQ

26. Jalpaiguri Alipurduar-II BHQ

27. Jalpaiguri Madarihat-Birpara BHQ

28. Jalpaiguri Falakata BHQ

29. Jalpaiguri Kalchini BHQ

30. Jalpaiguri Kumargram BHQ

31. Darjeeling Darjeeling DHQ

32. Darjeeling Darjeeling-Pulbazar BHQ

33. Darjeeling Jorebunglow-Sukhia Pokhari BHQ

34. Darjeeling Rongli-Rongliot BHQ

35. Darjeeling Kalimpong SDHQ

36. Darjeeling Kalimpong-II BHQ

37. Darjeeling Garubathan BHQ

38. Darjeeling Kurseong SDHQ

39. Darjeeling Mirik BHQ

40. Darjeeling Siliguri SDHQ

41. Darjeeling Kharibari BHQ

42. Darjeeling Matigara BHQ

43. Darjeeling Naxalbari BHQ

44. Darjeeling Phansidewa BHQ

45. Uttar Dinajpur Uttar Dinajpur DHQ

46. Uttar Dinajpur Raigunj BHQ

47. Uttar Dinajpur Itahar BHQ

48. Uttar Dinajpur Kaliaganj BHQ

49. Uttar Dinajpur Hemtabad BHQ

50. Uttar Dinajpur Islampur SDHQ

51. Uttar Dinajpur Goalpokhor–I BHQ

52. Uttar Dinajpur Goalpokhor–II BHQ

53. Uttar Dinajpur Chopra BHQ

54. Uttar Dinajpur Karandighi BHQ

55. Dakshin Dinajpur Dakshin Dinajpur DHQ

56. Dakshin Dinajpur Gangarampur SDHQ

57. Dakshin Dinajpur Gangarampur BHQ

58. Dakshin Dinajpur Harirampur BHQ

59. Dakshin Dinajpur Hili BHQ

60. Dakshin Dinajpur Kumarganj BHQ




61. Dakshin Dinajpur Kushmandi BHQ

62. Dakshin Dinajpur Tapan BHQ

63. Malda Malda DHQ

64. Malda Englishbazar BHQ

65. Malda Gazole BHQ

66. Malda Habibpur BHQ

67. Malda Kaliachak-I BHQ

68. Malda Kaliachak-II BHQ

69. Malda Kaliachak-III BHQ

70. Malda Manikchak BHQ

71. Malda Old Malda BHQ

72. Malda Bamongola BHQ

73. Malda Chanchol SDHQ

74. Malda Chanchol-I BHQ

75. Malda Chanchol-II BHQ

76. Malda Ratua-I BHQ

77. Malda Ratua-II BHQ

78. Malda Harishchandrapur-I BHQ

79. Murshidabad Murshidabad DHQ

80. Murshidabad Berhampore BHQ

81. Murshidabad Beldanga-I BHQ

82. Murshidabad Beldanga-II BHQ

83. Murshidabad Hariharpara BHQ

84. Murshidabad Naoda BHQ

85. Murshidabad Domkol SDHQ

86. Murshidabad Raninagar-I BHQ

87. Murshidabad Raninagar-I BHQ

88. Murshidabad Jalangi BHQ

89. Murshidabad Lalbagh SDHQ

90. Murshidabad Bhagawangola-I BHQ

91. Murshidabad Bhagawangola-II BHQ

92. Murshidabad Lalgola BHQ

93. Murshidabad Nabagram BHQ

94. Murshidabad Kandi SDHQ

95. Murshidabad Khargram BHQ

96. Murshidabad Burwan BHQ

97. Murshidabad Bharatpur-I BHQ

98. Murshidabad Bharatpur- II BHQ

99. Murshidabad Jangipur SDHQ

100. Murshidabad Raghunathganj-II BHQ

101. Murshidabad Suti-I BHQ

102. Murshidabad Suti-II BHQ

103. Murshidabad Samserganj BHQ

104. Murshidabad Sagardighi BHQ

105. Murshidabad Farakka BHQ




106. Nadia Nadia DHQ

107. Nadia Krishnagar-I BHQ

108. Nadia Krishnagar-II BHQ

109. Nadia Kaliganj BHQ

110. Nadia Nakashipara BHQ

111. Nadia Chapra BHQ

112. Nadia Nabadwip BHQ

113. Nadia Krishnaganj BHQ

114. Nadia Kalyani SDHQ

115. Nadia Chakdaha BHQ

116. Nadia Haringhata BHQ

117. Nadia Ranaghat SDHQ

118. Nadia Ranaghat-I BHQ

119. Nadia Ranaghat-II BHQ

120. Nadia Hanskhali BHQ

121. Nadia Shantipur BHQ

122. Nadia Tehatta SDHQ

123. Nadia Tehatta-II BHQ

124. Nadia Karimpur-I BHQ

125. Nadia Karimpur-II BHQ

126. Birbhum Birbhum DHQ

127. Birbhum Suri I BHQ

128. Birbhum Suri II BHQ

129. Birbhum Saithia BHQ

130. Birbhum Dubrajpur BHQ

131. Birbhum Khayrashol BHQ

132. Birbhum Rajnagar BHQ

133. Birbhum Mohamed-Bazar BHQ

134. Birbhum Bolpur SDHQ

135. Birbhum Bolpur-Sriniketan BHQ

136. Birbhum Ilambazar BHQ

137. Birbhum Labhpur BHQ

138. Birbhum Nanur BHQ

139. Birbhum Rampurhat SDHQ

140. Birbhum Rampurhat-II BHQ

141. Birbhum Mayureswar-I BHQ

142. Birbhum Mayureswar-II BHQ

143. Birbhum Murarai-I BHQ

144. Birbhum Murarai-II BHQ

145. Birbhum Nalhati-I BHQ

146. Birbhum Nalhati-II BHQ

147. Bankura Bankura DHQ

148. Bankura Bankura I BHQ

149. Bankura Bankura II BHQ

150. Bankura Barjora BHQ




151. Bankura Chhatna BHQ

152. Bankura Gangajalghati BHQ

153. Bankura Mejia BHQ

154. Bankura Onda BHQ

155. Bankura Shaltora BHQ

156. Bankura Khatra SDHQ

157. Bankura Indpur BHQ

158. Bankura Hirbandh BHQ

159. Bankura Raipur BHQ

160. Bankura Sarenga BHQ

161. Bankura Ranibandh BHQ

162. Bankura Simlapal BHQ

163. Bankura Taldangra BHQ

164. Bankura Bishnupur SDHQ

165. Bankura Indas BHQ

166. Bankura Joypur BHQ

167. Bankura Patrasayar BHQ

168. Bankura Kotulpur BHQ

169. Bankura Sonamukhi BHQ

170. Purulia Purulia DHQ

171. Purulia Manbazar-I BHQ

172. Purulia Manbazar-II BHQ

173. Purulia Puncha BHQ

174. Purulia Bandwan BHQ

175. Purulia Hura BHQ

176. Purulia Arsha BHQ

177. Purulia Baghmundi BHQ

178. Purulia Balarampur BHQ

179. Purulia Burrabazar BHQ

180. Purulia Joypur BHQ

181. Purulia Jhalda-I BHQ

182. Purulia Jhalda-II BHQ

183. Purulia Raghunathpur SDHQ

184. Purulia Raghunathpur-I BHQ

185. Purulia Raghunathpur-II BHQ

186. Purulia Kashipur BHQ

187. Purulia Neturia BHQ

188. Purulia Para BHQ

189. Purulia Santuri BHQ

190. Paschim Medinipur Paschim Medinipur DHQ

191. Paschim Medinipur Garbeta-I BHQ

192. Paschim Medinipur Garbeta-II BHQ

193. Paschim Medinipur Garhbeta-III BHQ

194. Paschim Medinipur Keshpur BHQ

195. Paschim Medinipur Shalboni BHQ




196. Paschim Medinipur Kharagpur SDHQ

197. Paschim Medinipur Kharagpur-I BHQ

198. Paschim Medinipur Kharagpur-II BHQ

199. Paschim Medinipur Dantan-I BHQ

200. Paschim Medinipur Dantan-II BHQ

201. Paschim Medinipur Pingla BHQ

202. Paschim Medinipur Sabang BHQ

203. Paschim Medinipur Mohanpur BHQ

204. Paschim Medinipur Narayangarh BHQ

205. Paschim Medinipur Keshiari BHQ

206. Paschim Medinipur Debra BHQ

207. Paschim Medinipur Ghatal SDHQ

208. Paschim Medinipur Chandrakona-I BHQ

209. Paschim Medinipur Chandrakona-II BHQ

210. Paschim Medinipur Daspur-I BHQ

211. Paschim Medinipur Daspur-II BHQ

212. Paschim Medinipur Jhargram SDHQ

213. Paschim Medinipur Binpur-I BHQ

214. Paschim Medinipur Binpur-II BHQ

215. Paschim Medinipur Jamboni BHQ

216. Paschim Medinipur Gopiballavpur-I BHQ

217. Paschim Medinipur Gopiballavpur-II BHQ

218. Paschim Medinipur Nayagram BHQ

219. Paschim Medinipur Sankrail BHQ

220. Purba Medinipur Purba Medinipur DHQ

221. Purba Medinipur Tamluk BHQ

222. Purba Medinipur Nandakumar BHQ

223. Purba Medinipur Moyna BHQ

224. Purba Medinipur Shahid Matangini BHQ

225. Purba Medinipur Panskura-I BHQ

226. Purba Medinipur Kolaghat BHQ

227. Purba Medinipur Chandipur BHQ

228. Purba Medinipur Haldia SDHQ

229. Purba Medinipur Haldia BHQ

230. Purba Medinipur Mahishadal BHQ

231. Purba Medinipur Nandigram-I BHQ

232. Purba Medinipur Nandigram-II BHQ

233. Purba Medinipur Sutahata BHQ

234. Purba Medinipur Egra SDHQ

235. Purba Medinipur Egra-I BHQ

236. Purba Medinipur Egra-II BHQ

237. Purba Medinipur Bhagawanpur-I BHQ

238. Purba Medinipur Pataspur-I BHQ

239. Purba Medinipur Pataspur-II BHQ

240. Purba Medinipur Contai SDHQ




241. Purba Medinipur Kanthi-II BHQ

242. Purba Medinipur Kanthi-III BHQ

243. Purba Medinipur Khejuri-I BHQ

244. Purba Medinipur Khejuri-II BHQ

245. Purba Medinipur Ramnagar-I BHQ

246. Purba Medinipur Ramnagar-II BHQ

247. Purba Medinipur Bhagawanpur-II BHQ

248. Hooghly Hooghly DHQ

249. Hooghly Balagarh BHQ

250. Hooghly Chinsurah-Mogra BHQ

251. Hooghly Dhaniakhali BHQ

252. Hooghly Pandua BHQ

253. Hooghly Polba-Dadpur BHQ

254. Hooghly Chandannagar SDHQ

255. Hooghly Haripal BHQ

256. Hooghly Singur BHQ

257. Hooghly Tarakeshwar BHQ

258. Hooghly Srirampur SDHQ

259. Hooghly Chanditala-I BHQ

260. Hooghly Chanditala-II BHQ

261. Hooghly Jangipara BHQ

262. Hooghly Arambagh SDHQ

263. Hooghly Khanakul-I BHQ

264. Hooghly Goghat-I BHQ

265. Hooghly Pursurah BHQ

266. Howrah Howrah DHQ

267. Howrah Bally Jagachha BHQ

268. Howrah Domjur BHQ

269. Howrah Jagatballabhpur BHQ

270. Howrah Panchla BHQ

271. Howrah Sankrail BHQ

272. Howrah Uluberia SDHQ

273. Howrah Uluberia II BHQ

274. Howrah Amta-I BHQ

275. Howrah Amta-II BHQ

276. Howrah Bagnan-I BHQ

277. Howrah Bagnan-II BHQ

278. Howrah Shyampur-I BHQ

279. Howrah Shyampur-II BHQ

280. Howrah Udaynarayanpur BHQ

281. North 24 Parganas North 24 Parganas DHQ

282. North 24 Parganas Barasat-II BHQ

283. North 24 Parganas Amdanga BHQ

284. North 24 Parganas Deganga BHQ

285. North 24 Parganas Habra-I BHQ




286. North 24 Parganas Habra-II BHQ

287. North 24 Parganas Rajarhat BHQ

288. North 24 Parganas Bidhan Nagar SDHQ

289. North 24 Parganas Barrackpore SDHQ

290. North 24 Parganas Barrackpore-I BHQ

291. North 24 Parganas Barrackpore-II BHQ

292. North 24 Parganas Bongaon SDHQ

293. North 24 Parganas Bagda BHQ

294. North 24 Parganas Gaighata BHQ

295. North 24 Parganas Bashirhat SDHQ

296. North 24 Parganas Basirhat-II BHQ

297. North 24 Parganas Baduria BHQ

298. North 24 Parganas Haroa BHQ

299. North 24 Parganas Hasnabad BHQ

300. North 24 Parganas Hingalganj BHQ

301. North 24 Parganas Minakhan BHQ

302. North 24 Parganas Sandeshkhali-I BHQ

303. North 24 Parganas Sandeshkhali-II BHQ

304. North 24 Parganas Swarupnagar BHQ

305. South 24 Parganas South 24 Parganas DHQ

306. South 24 Parganas Bishnupur-I BHQ

307. South 24 Parganas Bishnupur-II BHQ

308. South 24 Parganas Budge Budge-I BHQ

309. South 24 Parganas Budge Budge-II BHQ

310. South 24 Parganas Thakurpukur Maheshtala BHQ

311. South 24 Parganas Baruipur SDHQ

312. South 24 Parganas Bhangore-I BHQ

313. South 24 Parganas Jaynagar-I BHQ

314. South 24 Parganas Jaynagar-II BHQ

315. South 24 Parganas Kultali BHQ

316. South 24 Parganas Sonarpur BHQ

317. South 24 Parganas Canning SDHQ

318. South 24 Parganas Canning-I BHQ

319. South 24 Parganas Canning-II BHQ

320. South 24 Parganas Basanti BHQ

321. South 24 Parganas Gosaba BHQ

322. South 24 Parganas Diamond Harbour SDHQ

323. South 24 Parganas Diamond Harbour-II BHQ

324. South 24 Parganas Falta BHQ

325. South 24 Parganas Kulpi BHQ

326. South 24 Parganas Magrahat-I BHQ

327. South 24 Parganas Magrahat-II BHQ

328. South 24 Parganas Mandirbazar BHQ

329. South 24 Parganas Mathurapur-I BHQ

330. South 24 Parganas Mathurapur-II BHQ




331. South 24 Parganas Kakdwip SDHQ

332. South 24 Parganas Namkhana BHQ

333. South 24 Parganas Patharpratima BHQ

334. South 24 Parganas Sagar BHQ

Index: Explanation of the acronyms used above

Acronym Explanation

DHQ District Head Quarter

SDHQ Sub Division Head Quarter

BHQ Block Head Quarter



Annexure: AS – IS ICT Infrastructure Details

The existing IT Infrastructure at the various Police Stations across several districts in Bengal was put in place during the CIPA initiative. It was rolled out in two phases, Phase 1 and Phase 2. The following table presents an overview of the Two Phases:

Phase Duration No. of PS Covered

WB Police Kolkata Police

1 06/04/2005 to 13/12/2006 47 0

2 28/06/2006 to present day 66 24

Phase 1 Detail: District wise breaks up of Supplied Hardware under the Phase-I PSs are given below:-

District Computer Printer UPS 16 Port Switch

HOWRAH 39 20 10 10

N – 24 PGS 63 26 13 13

HOOGHLY 34 20 10 10

S – 24 PGS 59 28 14 14

TOTAL 195 94 47 47

Phase 2 Details:

District wise break up of Supplied Hardware under the Phase-II PSs are given below:- West Bengal Police

SL No.

District Computer Printer M/F Printer

16 Port

Switch

Modem/Fax Card

Addl. HDD

120GB

DVDR/DVD R/W

UPS 2

KVA

1 Bankura 7 2 2 2 4 4 4 2

2 Birbhum 9 2 2 2 4 4 4 2

3 Burdwan 33 8 8 8 16 16 16 8



SL No.

District Computer Printer M/F Printer

16 Port

Switch

Modem/Fax Card

Addl. HDD

120GB

DVDR/DVD R/W

UPS 2

KVA

4 Coochbehar 11 3 3 3 6 6 6 3

5 Darjeeling 20 5 5 5 10 10 10 5

6 D/Dinajpur 8 2 2 2 4 4 4 2

7 Howrah 14 3 3 3 6 6 6 3

8 Howrah GRP 8 2 2 2 4 4 4 2

9 Jalpaiguri 17 4 4 4 8 8 8 4

10 Kharagpur GRP

8 2 2 2 4 4 4 2

11 Murshidabad 24 6 6 6 12 12 12 6

12 Purba Medinipur

8 2 2 2 4 4 4 2

13 Paschim Medinipur

12 3 3 3 6 6 6 3

14 Malda 9 2 2 2 4 4 4 2

15 Nadia 17 4 4 4 8 8 8 4

16 N 24 Pgs 24 5 5 5 10 10 10 5

17 Purulia 7 2 2 2 4 4 4 2

18 Sealdah GRP 6 2 2 2 4 4 4 2

19 S-24 Pgs 12 3 3 3 6 6 6 3

20 U/Dinajpur 6 2 2 2 4 4 4 2

Total 266 66 66 66 132 132 132 66

Kolkata Police:

DISTRICT COMPUTER PRINTER UPS 16 PORT SWITCH

24 POLICE STATION UNDER KOLKATA POLICE

110 48 24 24

List of Police Stations where installation of CIPA could not be done in Phase 2:



Sl No. DISTRICT No. of PS STATUS

1 Howrah GRP [Total – 2] 1 Site not ready

2 Kharagpur GRP [Total – 2] 2 Site not ready

3 Malda [Total – 2] 2 Site not ready

4 North 24 PGS [Total – 5] 1 Site not ready

5 Paschim MDP [Total – 3] 3 Site not ready

TOTAL NO OF POLICE STATIONS 09

Detailed Configuration of the Hardware Installed:

Sl. No. COMPONENT NAME

CONFIGURATION

1. CPU HCL LX INFINITI PRO BL 1200 MONITOR: 17’’ HCL (HCM780M) KEY BOARD: HCL 5107 OPT/USB BOUSE: HCL M-UV96 MOTHER BOARD: ASUS P5GD2-TVM/S RAM: HYNIX (2*256 MB DDR, 400 MHz) LAN: (10/100/1000) RTL8110S-32 HDD: SEAGATE 120 GB SATA, 7200 RPM FDD: MITSUMI D359M3D (1.44 MB) DVD-W: PIONEER DVR-110D or DVD-R: TOSHIBA/SAMSUNG SH-D162 SPMS: 250W ATX INTERNAL MODEM/FAX CARD

2. Duplex Printer HP 1320 DUPLEX LASERJET PRINTER

3. MPF HP 3020 LASERJET PRINTER MPF

4. Switch D- LINK 16 PORT UNMANAGED SWITCH

5. UPS 2 KVA ONLINE UPS



Annexure: Infrastructure at Police Computer Training Institutes

Sl. No. Name Numbers Sanctioned

1 Client System (PC) 20

2 External HDD 1

3 Multifunction Point (Print/Scan/Copy/ Laser) 1

4 Duplex Network Laser Printer 1

5 24 port switch 1

6 UPS for 120 mins back up 6

7 Slide Projector 1

8 Laptop 1

9 Site Preparation 1

10 Software/ Biometric/ Contingency 1

Note: Training Units (includes PTS and District Training Center) to be used for Capacity Building



Annexure: List of Police Computer Training Institutes in West Bengal

Existing List of Police Computer Training Institutes:

Sl. No. Name of the Training Center

1. Police Training College, Barrackpore

2. Police Training School, Kolkata Police

3. STC SAP 1st BN Barrackpore

4. STC SAP 2nd BN Barrackpore

5. STC SAP 4th BN Raigung, Uttar Dinajpur

6. STC SAP 9th BN Krishnagar, Nadia

7. STC SAP 12th BN Dubgram, Jalpaiguri

List of existing District Computer Training Centers:

Sl. No. Name of the Training

Center

1. SP Bankura

2. SP Birbhum

3. SP Burdwan

4. SP Purba Medinipore

5. SP Paschim Medinipore

6. SP Hooghly

7. SP Purulia

8. SP North 24-PGS

9. SP South 24-PGS

10. SP Howrah

11. SP Nadia

12. SP Murshidabad

13. SP Dakshin Dinajpur

14. SP Uttar Dinajpur

15. SP Jalpaiguri

16. SP Malda

17. SP Cooch Behar

18. SP Darjeeling

19. SRP Sealdah

20. SRP Siliguri

21. SRP Howrah

22. SRP Kharagpur



List of additional STCs for which funds have been requested vide Memo No: 313/CCTNS/SCRB/WB,

dated: 16/09/2010

Sl. No. Name of the Training Center

1. STC SAP 3rd BN Barrackpore

2. STC SAP 6th BN Barrackpore

3. STC SAP 8th BN Barrackpore

4. STC EFR 1st BN Salua, Paschim Medinipur

5. STC 1st IR BN Durgapur

6. STC Paschim Medinipur

7. STC Bankura

List of additional DPCTCs for which funds have been requested vide Memo No:

363/63/CCTNS/SCRB/WB, dated: 21/10/2010

Sl. No. Names of the KP Division for which DPCTCs have been proposed

1. Central Division

2. Eastern Suburban Division

3. North Division

4. Port Division

5. South Division



Annexure: Scope of Services

Functional Requirements Specifications for CAS (State)

No. Business / Functional Requirement

CAS - STATE FUNCTIONAL REQUIREMENTS

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 6. 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 2. Tenant Verification 3. Servant Verification 4. Permission Request for Processions and Rallies 5. Passport Verification Status 6. Arm License Verification Status 7. Application for Character Certificate System should provide the user with the following representative Information Services through the online portal 1. Missing Persons Listing (with Photographs) 2. Proclaimed Offenders Listing 3. Stolen/ Recovered Vehicles Listing 4. Unidentified Dead bodies (with photographs) Listing 5. Abandoned / Unclaimed/recovered Properties Listing 6. Most Wanted Criminals Listing (with photographs)




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 display 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 2. Tenant Verification 3. Servant Verification 4. Permission Request for Processions and Rallies 5. Passport Verification Status 6. Arm License Verification Status 7. Application for Character Certificate

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 multiple 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). Application should be compatible for future integration with GIS application.

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 (Application should recognize retina scanner) 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 limits2. 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 against SC / ST or POC Act to SP (will in turn align 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 frozen on 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 Juveniles 1. Accused (sent to Juvenile Justice Board) 2. Victim (Children’s Court) 3. Witness (Children’s 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 pre-defined list associated with the case. The administrator should be able to add / modify the super-set of tasks / activities defined in the system and make them default




to a type of the case.

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 in case 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 person 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 characteristics 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 surveillance (in case the person is in the same district)Bad Characters Roll B - SHO fills in the roll B in case the person moves out of the district

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 that 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 Nadu, 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 particular 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 Split1. 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 stakeholders.

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.9.12 Number of users expected to be 83358 and 99% uptime required for mail solution at DC/DR.

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 to1. 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 ' every day 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) on1. 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 / offenders in sensational cases to SPs

1.11.15 System should generate alerts on 1. Court Case Hearing Date (to original PS (SHO) and concerned IO) 2. Charge Sheet Submission 3. Release and Parole Date 4. Bank Robberies, Dacoity (in other districts states) (to SPs) 5. Accused / Arrested (in other police stations as well) 6. Heinous Crime Case Details 7. Special Report (juvenile, 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 14. Hue and Cry Notices 15. Terror Offences 16. State CID Instructions 17. Political Agitations 18. Filing Revision / Appeal / SLPs20. 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 in case 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

Additional State Specific Application Functionalities

System Integrator is responsible for developing the Additional State Specific Functionalities. The application modules and functionalities covered during the Phase I of CCTNS implementation are listed in the table below:

Modules Additional Functionalities Complied

(Y/N)

Registration Module

Counterfeit Advisory and Theft Reporting

System should provide an option to register Theft cases under GRP

Petitioner to be able to download/print the certificate /report /permission or response to request

System should have provision for registering cases against unknown culprits

System should capture details needed for traffic Police requirements (Challan file is available and the system integrator is expected to digitize the same)

Investigation Module

System should provide a provision for initial investigation for information received through PCR, phone etc. wherein a complainant is first established and a letter of complaint generated / a suo motto case registered before an FIR is lodged.

System should allow the provision of multiple Officers (with no upper limit) to be assigned to a particular Case

System should generate the Memo of Evidence that needs to be submitted with the charge sheet for approval by the concerned higher authority

For Arms Seized, Memo of Evidence is not necessary; PP opinion through SP is mandated in these cases. So, system should capture PP’s opinion.

System should allow for the creation of a Special Report




(Y/N)

after review and rejection of initial charge sheet

System should allow for comments of the user on the Special Report

System should allow different users to assign different categories of cases to be SR Case

Prosecution Module Provision has to be kept for entering arrested person details.

Basic and Advanced Search Module

System should allow the creation of different sets of roles for same hierarchy

System should allow for parameterized search of defect log status

Basic (regular) reporting and MIS

Indicative reports include the following:

Charge sheet details (PS & Date wise)

FRT

FIR & Non FIR pending/under investigation & final form received (PS wise)

Case Trial (GR/NGR) and summary report on the same

Case Disposal (Head wise)

Warrant details

Property Register

Reports for Traffic Police (For details, please refer ‘Annexure: Sample Traffic Reports’)

In WBP, the case alerts may be send to an OC, IC or CI while in KP, these may be sent to the OC or AC

The System must able to provide reports for actions on cases organized: By Status (Unresolved/In - progress/Resolved)



The application modules and functionalities covered during the Phase II of CCTNS implementation are

listed in the table below:

Modules Additional Functionalities Complied (Y/N)

Collaboration Solutions (police messaging, email)

The Nodal Officer assigned to a patrol party will need to interact directly with the system over wireless/communication device

System should provide alerts to superior officers whenever a transferred officer joins under them

System should generate an alert whenever a new user is stipulated the work by the older user

Citizen Interface Petitioner to be able to download/print the certificate/report/permission or response to request

Services such as request for conducting ceremonies and functions (pujas, marriages etc.)

Services for NoC generation by employers

Services for applying for gun licensing

Advanced analysis and Reporting

System needs to have the provision of reports to be taken multiple times during each day

System should allow for the creation of a Special Report after review and rejection of initial chargesheet


Automated Fingerprint Recognition System

No state specific changes are envisaged (System Integrator is expected to integrate the fingerprint recognition system for investigation module)

The application modules and functionalities covered during the Phase III of CCTNS implementation are listed in the table below:


(Y/N)

External Interfaces (such as Courts, Prisons, Hospitals, Cell phone service providers, Vehicle

System should help identify and trace hoax callers (PCR will identify the hoax caller and application is expected to aid the PCR)

System should allow a caller to register a case from any place (even from outside the jurisdiction) if the incidence being reported took place within the jurisdiction of the PCR

System should enable a caller response time within 5 minutes




(Y/N)

information, etc.)

There should be enough flexibility to attend to intra state scenarios (even beyond the PCR’s jurisdiction) subject to the criticality of the event and availability of resources nearby for quick deployment. System should allow the user to identify the appropriate police station and transfer the call.

The Nodal Officer assigned to a patrol party will need to interact directly with the PCR system over wireless/communication device (Application should be accessible from mobile/wireless devices)

Crime Prevention (Beat Management, etc.) and other modules decided to be provided to all states

State specific changes as required to be done by the SI

Separate Module Relating to Trafficking of Women & Children

Trafficking of women and children is a major problem in the state. It is seen that largest number of sex-workers in any Red Light areas in major metropolitan cities in India are from West Bengal.

A separate State-specific module which would generate require data, reports and capture information relating to trafficking of women & children should be included as a separate module in the CAS(State).

Separate Law & Order Related Manpower Deployment & Resources Module

The CCTNS Project implementation plan includes the state level Control Rooms of both Kolkata Police & West Bengal Police would be a part of the CCTNS network.

It is felt that to increase the usability of this software & obtain maximum benefit from the CCTNS network there should be required details relating to manpower available for Law& Order duty deployment captured in real time basis in the system at all levels of the network. This would help in improving response time for tackling emergent Law & Order situations.

Further the CCTNS System should be able to capture details regarding resources/equipment needed for Law & Order duties. These include vehicles, security equipment like munitions, dhal, protective gear, etc.

The system should also be able to generate basic arrangement/Bandobast for Law & Order duties




(Y/N)

which are specific to the state.

In view of this, it is felt that a separate Law& Order related Manpower Deployment & Resources Module be made a part of the CAS (State).

Note: Further state specific FRS which would form part of CAS(State) to be developed by SI, shall be

shared with all the bidders in due course of time.



Sample Traffic Police Reports

I. Details of Road Accidents on Different types of cause Type of Accidents

Total

Fatal Grevious Injury Minor Injury Non-Injury

Type of Cause

No. of Accident

s

No. of persons

killed

No. of Accidents

No. of persons

greviously Injured

No. of Acciden

ts

No. of persons minor

Injured

No. of Accident

s

(1) (2) (3) (4) (5) (6) (7)

(1+3+5+7)

1 Fault of driver

2

Fault of Passenger other than Driver

3 Bad Road

4 Bad Weather

5 Mechanical fault in Vehicle

6 Fault of Pedestrian

7 Others

Total

II. Details of Road Accidents on Different types of vehicles Type of Accidents

Type of vehicle

Fatal Grevious Injury Minor Injury Non-Injury

Total No. of Accident

s

No. of persons

killed

No. of Accidents

No. of persons

greviously Injured

No. of Acciden

ts

No. of persons minor

Injured

No. of Accident

s

(1) (2) (3) (4) (5) (6) (7)

(1+3+5+7

)



1 Truck

2 Buses

3 Mini Buses

4 Car/Jeep/Taxi

5 Three Wheeler

6 Two Wheeler

7

Other Heavy Vehicle

8

Vehicle not Known

9 Other

Total



Non Functional and Technical Requirements This section of Requirement Specifications focuses on the different functionalities of the overall solution

from a maintenance and administration perspective. All such requirements have been organized in this

section in various modules as following:

Security Management

1.1 Authentication

1.1.1 The system should support LDAP based authentication

1.1.2 The system should support ASP.NET, JDBC and open standards options.

1.1.3 The solution should ensure data safety and integrity in the event of

communication channels operation failures.

1.1.4 The solution should support multi -tier authentication where required.

1.1.5 The solution should not store authentication credentials on client computers

after a session terminates.

1.2 Authorization

1.2.1 The user should be able to invoke an action according to permission granted to

him and according to business logic/rules.

1.2.2 The system should provide flexibilities for managing the authentication and

authorization with respect to the ability to interface to external solutions.

1.3 Access Management

This module should have the following facilities and functionalities:

1.3.1 The access levels to be provided to the different internal roles / stakeholders

will be managed centrally. The system should have the flexibility to change

the role based access as and when required.

1.3.2 System should ensure that the user gets to access only that data for which he is

authorized.

1.3.3 There should be ability to support & implement session timeout

1.3.4 Ability to define access to specific menus by user groups

1.3.5 Allow customized ID-password policies to be implemented

1.3.6 Password will be account specific for both internal and external users.

1.3.7 The solution should employ a common user access and authentication service to

ensure Single-Sign on for the end-user

1.3.8 Application will provide option to allow admin/super -admin to add/edit/delete

to users

1.3.9 Credential remaining same, this will allow the same roles to access more than

one modules as well.



1.3.10 Provision for password expiry and management:

1.3.10.1 A question / answer along with the password reset before

activating the reset password

1.3.10.2 Force change of password on first time login, first time login

post reset

1.3.10.3 The user can change his/her passwords at the maximum of 4

times in a day.

1.3.10.4 The system should have the ability to store last five passwords

in the password history and the user should be restricted to use the last

five passwords whenever he/she tries to change the password.

1.3.10.5 Password should be changed in a frequency of 45 days. System

should alert that the password needs to be changed when the password

change date is approaching near. If the password is not changed, the

user id will be locked

1.3.10.6 Force new user to change password after first log in

1.3.11 The system should provide easy access to define new user groups and create

custom roles.

1.3.12 The solution should ensure that data deletion is controlled centrally as per

the defined policy or the person having right to do so.

1.3.13 Maintain administrative IDs for the purpose of system administration

1.3.14 Lock the session after a specified number of authentication failures.

1.3.15 Ability to track and audit the following

1.3.15.1 Successful login

1.3.15.2 Un-successful login

1.3.15.3 Last login date/time

1.3.15.4 Updating of user contact details

1.4 Secure Communication Channel

1.4.1 The system should Support SSL/ https between the web browser & web server

front end. (Internet & Intranet) and also from web server to the database.

1.5 Single Sign on

1.5.1 The system should have integration with LDAP server for advanced security and

should provide single sign on feature. It should provide a standard set of

interfaces to integrate with an LDAP server.

1.6 Encryption

1.6.1 Ability to support & implement digital signatures (Per unit(e.g. PS, Higher

offices, other police offices as mentioned in RFP) one digital signature is

required)



1.6.2 Proper key management techniques should be used to support the

cryptographic techniques

1.6.3 Support encryption between web browser & web server front end (Internet &

Intranet)



Application and Systems Management

1.7 Logging

1.7.1 The system should maintain logs of various transactions like failed logins, failed

and successful attempts to access critical data, database

1.7.2 A separate interface should be provided to define the different event that can

be logged and the business rules for logging such events

1.7.3 Generate error log for each batch containing the records which failed to be

processed in the batch report and the reason for failure

1.7.4 All the exceptions will store at DB end and pass the same at state/centre label

for further escalation

1.7.5 Application will maintain audit log for important data transactions like updation

and deletion

1.7.6 All the credentials and sensitive data always will store at Database end

1.7.7 The system should have a provision to store the logs in the following locations:

1.7.7.1 System event logs in the application servers

1.7.7.2 As an e-mail message

1.7.7.3 Database servers for database related logs

1.7.7.4 Message Queue

1.7.7.5 Text files in the application servers

1.7.7.6 WMI events

1.7.7.7 Custom locations such as a file server.

1.7.7.8 Local logs should be stored locally at the individual user desktops.

1.8 Exception Handling and Notifications

1.8.1 Capability to provide summary reports of the various events logs

1.8.2 The system should be able to provide configurable error messages and monitor

the occurrence of the same. The error messages should be categorizable as:

1.8.2.1 Errors

1.8.2.2 Alerts

1.8.2.3 Messages etc

1.8.3 Monitoring Reports for various types of Error messages should be available

1.8.4 The system should have the ability to monitor the quality of stored data and its

integrity during changes to the stored data in real-time and batch

1.9 Monitoring

This section covers the functionalities of EMS (Enterprise Management System) which are applicable for this solution.

1.9.1 Ability to monitor application parameters and behavior

1.9.1.1 Database connection pools

1.9.1.2 Thread pools

1.9.2 Ability to monitor the application for the following parameters:



1.9.2.1 Health monitoring

1.9.2.2 Error Monitoring

1.9.2.3 Performance Monitoring

1.9.2.4 Configuration Monitoring

1.9.2.5 Security Monitoring

1.9.3 Provision for periodic activity reports covering security event and application

usage.

1.9.4 Ability to record metrics for completed and failed procedures

1.9.5 Ability to monitor the performance of batch jobs based on the user load at the

time and allow for analysis of the optimum time and load to run the batch.

Should there be any requirement for batch processing, performance

monitoring for the same should be in place. All solution components to be

tested before deployment.

1.9.6 Ability to monitor the system in remote sessions.

1.9.7 The system should have a strong management framework allowing the

administrators to monitor, reconfigure, manage, update, and control all

platforms, hardware and software, of the portal site and associated services.

The management framework should also allow administrators to monitor

operations, report faults, alert administrators of failures, analyze access,

usage, load, etc. to take appropriate actions whenever needed.

1.10 Release and Patch Management

1.10.1 The system upgrades should be possible without affecting the present

configuration and settings. System upgrade should include different

components like

1.10.1.1 Application components

1.10.1.2 Antivirus

1.10.1.3 Database and operating system.

1.10.1.4 Others (MS-Office Components, Web Browsers etc)

1.11 Audit Trail

1.11.1 The system should support for comprehensive audit trail features such as:

1.11.1.1 Daily activities log are merged into the history log files

1.11.1.2 Date, time and user-stamped transaction checklist are on-line

generated for different transactions

1.11.1.3 Daily activity reports are provided to highlight all the

transactions being processed during the day

1.11.1.4 Unsuccessful attempts to log-in to the system should be

recorded

1.11.1.5 All attempts to access/change system data should be system

driven



1.11.1.6 The system should trigger a audit trail / report to concerned

user if a part of a scheduled set of activities (say certain programs/

activities) did not run on schedule

1.12 Replication Management

1.12.1 The system should have flexibility to regenerate the programs and features

without starting the development process from very beginning. The system

should have an user interface to support the same so that the entire

development activity can be replicated to a new set up without much of

problems

1.13 Server Statistics Analysis

1.13.1 Availability of an UI to monitor the server statistics like CPU usage; RAM

utilized and load distribution on the different servers.

1.13.2 Capability to monitor for the peak user / average user / transaction per

second loads

1.13.3 Notify the system administrator whenever there is a suspicious increase in

system activity or the system usage crosses a preset threshold value.

1.14 Data Migration and Integration

The system should have the following capabilities with respect to data integration

1.14.1 The system should have the ability to integrate data using enterprise data

model as part of the interfaces between applications to ensure loose

coupling

1.14.2 An integral management tool with Graphical job sequencer and nesting of

sessions

1.14.3 Ability to capture data from different data sources irrespective of their

platforms.

1.14.4 Support for concurrent processing of multiple data streams without writing

procedural code.

1.14.5 Support management & scheduling tools for data loads.

1.14.6 The system should have configurable tools for:

1.14.6.1 data mapping

1.14.6.2 extracting

1.14.6.3 filtering

1.14.6.4 transforming/cleansing and enhancement

1.14.6.5 loading

1.14.6.6 Incremental loading

1.14.6.7 Refresh with ability to change refreshment frequency

1.14.7 Data Quality and Integrity must be ensured across systems particularly, at

data capture stage and managing stored data



1.14.8 The system should perform a virus check on all the uploaded files before

uploading the files onto the server

1.14.9 Allow users to perform detailed and complex data transformations when

deriving data fields

1.14.10 Capability to automatically download and upload feeds from various sources

such as Web services, RSS feeds, flat files - csv, xls, txt etc.

1.15 SLA Management

1.15.1 The system should provide monitoring and management features for

tracking SLAs

1.16 Application Integration

1.16.1 Ability to integrate with third party applications over LAN, WAN and internet.

1.16.2 Capable of interfacing with backend business applications existing within the

Police Organization.



Requirement Specifications – Others

1.17 Flexibility

1.17.1 Modular structure providing the flexibility to deploy selected modules-

products- lines of business combination as per the convenience of CCTNS

users

1.17.2 The solution will be configurable architecture as per state requirements and

customization as well.

1.17.3 The solution should provide application architectures that are highly granular

and loosely coupled.

1.17.4 The solution architecture should allow infrastructure simplicity and

standardization.

1.17.5 The system should be designed in manner that operational data will never be

lost until a manual intervention/hardware failure.

1.17.6 Data model should be flexible to add more data fields as per changing

business needs

1.18 Usability Requirements

1.18.1 The system should have the following flexibilities and functionalities in terms

of usability: Comprehensive sitemap details in an easy to browse format.

1.18.2 The system should ensure that Same screen appears each time it is launched

1.18.3 Consistent and logical navigation flow

1.18.4 The solution should maintain a database of frequently asked questions

(FAQ).

1.18.5 The solution will provide data dictionary for mandatory fields.

1.18.6 The solution should be based on shared and reusable architectures, that is,

applications, systems and infrastructure are characterized as service

oriented, component-based and reusable.

1.18.7 Usage of standard GUI features (e.g., pull-down menus, dialog boxes, toolbar

buttons)

1.18.8 All error messages produced by the System must be meaningful,

1.18.9 Consistent look and feel

1.18.10 The application windows colors must respond correctly to user changing of

color settings (i.e., must change with the colors, or all must stay fixed).

1.18.11 Data formats are consistent throughout application windows

1.18.12 The menu options in the pages can be accessed via keyboard commands

and/or arrow keys, following Microsoft conventions. Mouse-only access to

options should be avoided.

1.18.13 The system should ensure that controls on page must respond properly to

Tab order and hot-keys (alt-keys). In Microsoft Windows, a user should be

able to use the Tab key to move from one control to the next. This should

work in a logical manner such as from left to right and top to bottom.



1.18.14 Provision for tool tips at each field and also online Help at the field level

1.18.15 The system should prevent the users from errors and allow error recovery

1.18.16 System should be user friendly so that submission guidelines for each form

are easily understandable by the user. For example a pop up screen or drop

down list be provided wherever possible. For example pop up for date should

be “dd-mm-yyyy” and drop down list for “fund code”, “return code” etc.

1.18.17 The system should comply with the following usability standards:

1.18.17.1 ISO 9241: Ergonomic requirements for office work with visual

display terminals

1.18.17.2 ISO/IEC 10741-1: Dialogue interaction - Cursor control for text

editing

1.18.17.3 ISO/IEC 11581: Icon symbols and functions

1.18.17.4 ISO 13406: Ergonomic requirements for work with visual

displays based on flat panels

1.18.17.5 ISO 18789: Ergonomic requirements and measurement

techniques for electronic visual displays

1.19 Performance

1.19.1 The system should provide fast and steady response times (Quality of

Service). The maximum user response time should be less than 2 seconds

and average response time should be less than 1 second for the next screen

to appear or the existing screen to refresh for submission of data. The speed

and efficiency of the system should not be affected with growing volumes,

especially during search operations, data warehousing, reporting, MIS, online

processes and batch processes. WBSWAN is the primary connectivity and

performance measures are expected on WBSWAN.

1.19.2 Will provide log shipping to continue the operations

1.19.3 The system should be designed to have minimum satisfactory performance

even in Police Stations connected on low-bandwidth (28 kpbs).

1.19.4 System will show quick response in simple search and will take little bit more

time for advance search and this will vary based on input conditions.

1.20 Availability

1.20.1 Application will up and running (at least 99% if no other disturbance i.e.

power failure, LAN problem and any other infra - structure issues).

1.21 Scalability Requirements

The system should meet the following scalability requirements:

http://www.usabilitynet.org/tools/r_international.htm#9241x

http://www.usabilitynet.org/tools/r_international.htm#10741






1.21.1 Support multi- tier architecture (The Application should at least have the

following within its architecture) for all modules within the application with

well - defined interfaces between the layers

1.21.1.1 Presentation Layer

1.21.1.2 Business Logic Tier

1.21.1.3 Data Tier

1.21.2 Ability to scale horizontally without redesign

1.21.2.1 Multiple similar hardware and mix of multiple hardware in a

horizontal setup

1.21.2.2 Scalability for external components (External components

should not restrict scalability) - Provide performance

benchmarks for similar functions required in SCRB for Solution

scalability

1.21.3 Ability to scale vertically without redesign

1.21.3.1 Addition of CPU, Memory, Hard disk capacity without causing

downtime

1.21.4 Support the deployment of additional modules at a later point in time with

minimal downtime and loss of productivity.

1.21.5 Support message patterns and protocols supported - e.g. publish/subscribe,

synchronous/asynchronous, push/pull/pool, topics/queues.

1.21.6 The system should support payment and collection processes relate to via

RTGS or NEFT standards. (Future Requirement)

1.21.7 The solution should facilitate centralized deployment of the application.

1.22 User Interface Requirements

1.22.1 The user should be able to create and design customized screens with ability

to select and add fields, drag and drop the fields at the required position,

apply rules on the fields (such as length, type of data, mandatory/non-

mandatory, help function, dependency on other fields and its values etc.),

multi-branding with colour, design, logos etc. of multiple parties including

those of third party service providers.

1.22.2 System should support multilingual interface.

1.22.3 System should support multilingual labels.

1.22.4 The interfaces will customizable or user-configurable to the extent possible

(look and feel, logos).



1.22.5 The System user interface must be suitable for users with special needs; that

is, compatible with specialist software that may be used and with

appropriate interface guidelines

1.23 Data Entry/Capture, Data Quality and Integrity Methodology

The system should support the following data entry methodologies to minimize data entry errors and improve data integrity. One should be able to choose the data entry option for each type of transaction and change the same as and when required.

1.23.1 Maker / Authoriser – One person should enter data and another should

authorize the entered data. If the authoriser notices errors in data entry, the

task should be returned back to the data entry operator. Typically all master

table data entry should follow the maker / author route. However one should

be able to choose between all the three available options for data entry.

1.23.2 Single Data Entry – The data is entered only once and it progresses in the

value chain. Such data entry screens typically have large number of

validations to prevent data entry errors.

1.23.3 Double Data Entry – The same transaction data is entered by two different

persons. Only selected fields are data entered by two different persons. The

system should then match the data entered by two persons (character by

character), and if the data matches then it progresses further in the process

value chain. If the data entered by two users does not match, then the

transaction is referred to a third person who verifies the data from the

source and accepts the correctly entered data or rectifies the data if both

persons have wrongly entered the data.

1.23.4 All data entry/capture should be managed through the option of defining

data quality and integrity tools to perform data validity and correctness

checks with supporting data quality and integrity tools at the time of data

capture/entry. The captured data stored in systems should be managed and

monitored regularly through appropriate data quality and integrity tools in

place to ensure that the quality of the data is protected and managed

effectively.

General Considerations and Constraints

1.1 The implementation partner should size for adequate hardware based on the volumes for

the applications in the entire solution & database and all other applications relevant for DC

and DRC.

1.2 At police station will able to work on offline env and post that data will synchronization at

state label when internet connectivity will available.



1.3 Application code should not contain invalid references to network resources (Pathnames,

URLs etc).

1.4 The hardware sized for all the applications should be redundant and scalable. All the

components within the server should be hot swappable and should incur no downtime due

to component failure.

1.5 All the servers suggested should have dual power supplies. The power input to the power

supplies will be from separate Uninterrupted Power Supplies which will be fed from two

different power sources. In case of failure of one power supply, the second power supply

should be able to take the full load without causing any interruption in services.

1.6 All servers should have at a minimum of dual 1000 Mbps network interface cards (NIC)

installed on different slots. Each NIC will be cabled from a different module on the switch

using gigabit speed cabling.

1.7 The system should be platform independent and should be deployable on multiple

platforms such as HP UNIX, IBM AIX, IBM i, Sun Solaris, Microsoft Windows, Linux etc., but

should also allow integration with other software deployed across heterogeneous operating

system platforms. Since the bidder needs to choose either of the two technology stacks, as

mentioned in the RFP, CAS (State) application should have hardware platform independence

and interoperability with other applications to the extent possible.

1.8 The system should use Service Oriented Architecture best practices and should use industry

standards for integration to achieve universal use.

1.9 The solution should result in low architectural diversity.

1.10 Solution should follow NIC website development guidelines and standard guidelines too.

1.11 Ability to be browser independent. The system should be compatible with the following

browsers

1.11.1.1 Internet Explorer 6.0 or higher;

1.11.1.2 Mozilla Firefox 3.0.7 or higher;

1.11.1.3 Safari, Netscape, etc.

1.12 All Operating system, database and other software licenses for DC and DR shall be

genuine, perpetual, full use and should provide patches, bug fixes, security patches and

updates directly from the respective developer / manufacturer for the contract period.

1.13 OS should support for all peripherals required under CCTNS Project i.e. Finger Print

Scanner, Electronic Pen, MFP, Laser Printer etc.

1.14 The proposed Operating System must not be “End of Life” product.

1.15 Manufacturer should provide time to time Updates / patches / security patches / bug

fixes for the operating systems.

1.16 The proposed system software indemnification and indemnification must cover patent

claims, copy right claims, legal fees and damages claim. System integrator and / or the

developer / manufacturer must protect the department from all such legal cost that may

arise out of any claim by a third party alleging intellectual property infringement i.e. related

to the software.



1.17 There should be 24*7 access to a variety of technical resources including the OEM

Support Portal, manufacturer’s knowledge base with complete collections of technical

articles.



Annexure: Details of the Technology Stacks for CAS (State) and CAS

(Center) CAS (State) will be developed in two distinct technology stacks by the SDA at the Center. The Technical Details for CAS (State) Solution Stack 1 and Stack2, CAS (State) Offline solution, CAS (Centre) Solution are provided in subsequent tables: CAS (State) Solution - Stack 1

Particulars

Proposed

Solution by

Software

Development

Agency

Version and

Year of

Release

Original

Supplier

Description

(include major

features/

services only)

Support

Provided By

Webserver Sun Java System Web Server 7.0

7.0 SUN HTTP Server SUN

Application Server

Glassfish Application

Server

3.0 SUN J2EE Application Server

SUN

Database MySQL 5.1 SUN DB Store SUN

Operating System

Solaris 10 SUN Operating System

SUN

Others

Reporting Engine

Jasper Reports 3.7 Jasper Reporting Services

Email/Mess Aging

Q-Mail 1.4 Qmail Community

E-Mail Solution

Search Engine

Search: Unstructured data: using open CMS search features Structured Data Mysql & Custom application

interface

N/a N/a N/a N/a

Portal Server

Glassfish Application

3.0 SUN J2EE Application

SUN



Particulars

Proposed

Solution by

Software

Development

Agency

Version and

Year of

Release

Original

Supplier

Description

(include major

features/

services only)

Support

Provided By

Server Server

Workflow Engine

jBPM 4.0 JBoss Workflow Engine

Rules Engine

Custom Built N/a N/a N/a N/a

Directory Services

Sun Directory Services

7.0 SUN LDAP SUN

DMS/CMS Open CMS 7.5.1 Open C MS

Content Management System

Security Physical Security, Network Sercurity, DB Encryption (MySQL), DB Access Controls, Role Based Access Control (Custom Developed), LDAP (Sun Directory Services),

N/a N/a N/a N/a

Identity Management

OpenSSO (Other open source SSO application providing similar or enhanced functionality is acceptable)

7.0 SUN LDAP SUN

Audit log4j, Custom Built application audit

N/a N/a N/a N/a

ETL Custom Built N/a N/a N/a N/a



CAS (State) Solution - Stack 2

Particulars

Proposed

Solution by

Software

Development

Agency

Version And

Year of

Release

Original Supplier

Description

(include major

features/

services only)

Support

Provided By

Webserver IIS 6 Microsoft Web & App Server

Microsoft

Application Server

IIS 6 Microsoft Web & App Server

Microsoft

Database SQL Server

2008

2008 Microsoft DB Store Microsoft

Operating System

Windows Server 2008

2008 Microsoft Operating System

Microsoft

Others Microsoft

Reporting Engine

SQL Server Reporting

Services

2008 Microsoft Reporting Services

Microsoft

Email/ Messaging

Q-Mail 1.4 Qmail Community

E-Mail Solution

Search Engine

Search: Unstructured data: Using openCMS search features Structured Data: SQL DB Search Engine & Custom application

N/a N/a N/a N/a



Particulars

Proposed

Solution by

Software

Development

Agency

Version And

Year of

Release

Original Supplier

Description

(include major

features/

services only)

Support

Provided By

interface

Portal Server IIS 6 Microsoft Microsoft Web & App Server

Microsoft

Workflow Engine

Windows Workflow Foundation

N/a N/a N/a N/a

Rules Engine Custom Built N/a N/a N/a N/a

Directory Services

Microsoft Active Directory

2008 Microsoft LDAP Microsoft

DMS/CMS Windows Sharepoint

Services

n/a n/a n/a Microsoft

Security Physical Security, Network Security, DB Encryption (MySQL), DB Access Controls, Role Based Access Control (Custom Developed), LDAP (Sun Directory Services),

N/a N/a N/a N/a

Identity Management

Microsoft Active

2008 Microsoft LDAP Microsoft



Particulars

Proposed

Solution by

Software

Development

Agency

Version And

Year of

Release

Original Supplier

Description

(include major

features/

services only)

Support

Provided By

Directory

Audit IIS Log, Custom Built

N/a N/a N/a N/a

ETL SQL Server

ETL

2008 Microsoft ETL Microsoft

CAS (State) Offline Solution

The below list is indicative only

Proposed

Solution by

Software

Development

Agency

Version and

Year of

Release

Original Supplier

Description (include major

features/ services

only)

Support

Provided By

Synchronization Solution


Application Container

Apache Tomcat

6.0 Apache Foundation

J2EE Application Container

Database MySQL / SQL Express

5.1/2008 SUN / Microsoft

DB Store SUN / Microsoft

CAS (Center) Solution

The below list is

indicative only

Proposed

Solution by

Software

Development

Agency

Version and

Year of

Release

Original Supplier


features/ services

only)

Support

Provided By

Webserver Sun Java System Web Server 7.0




The below list is

indicative only

Proposed

Solution by

Software

Development

Agency

Version and

Year of

Release

Original Supplier


features/ services

only)

Support

Provided By

Application Server

Glassfish Application Server

3.0 SUN J2EE Application Server

SUN

Database Sybase IQ Enterprise

15.1 Sybase ETL Sybase

Operating System

Solaris

Others

Reporting Engine

Jasper Reports 3.7 Jasper Reporting Services

Search Engine

Search: Unstructure data: using Alfresco search features Structured Data: Sybase DB Search Engine & Custom application interface

N/a N/a N/a N/a

Portal Server

Glassfish Application Server


Workflow Engine

jBPM 4.0 JBoss Workflow Engine

Rules Engine


Directory Services

Sun Directory Services

7.0 SUN LDAP SUN

DMS/CMS Alfresco

Email/Mess aging

N/A

Security Physical Security, Network

N/a N/a N/a N/a



The below list is

indicative only

Proposed

Solution by

Software

Development

Agency

Version and

Year of

Release

Original Supplier


features/ services

only)

Support

Provided By

Sercurity, DB Encryption (MySQL), DB Access Controls, Role Based Access Control (Custom Developed), LDAP (Sun Directory Services),

Identity Management

Open SSO 7.0 SUN LDAP SUN

Audit log4j, Custom Built

N/a N/a N/a N/a

ETL + Data Quality

Sybase ETL 15.1 Sybase ETL Sybase



Annexure: District Maps Kolkata Police: Central Division



Kolkata Police: South Division



Kolkata Police: South East Division

Kolkata Police: South East Division



Kolkata Police: East Suburban Division



Kolkata Police: Port Division



WB Police: Uttar Dinajpur District



WB Police: Nadia District



WB Police: Murshidabad District



WB Police: Bankura District



WB Police: Howrah District



WB Police: Jalpaiguri District



WB Police: Coochbehar District



WB Police: Hooghly District



WB Police: Dakshin Dinajpur District



WB Police: South 24 Parganas District



WB Police: Purulia District



WB Police: Bardhaman District



WB Police: Paschim Medinipur District



WB Police: North 24 Parganas District



WB Police: Jhargram Police District



WB Police: Maldah District



WB Police: Purba Medinipur District



WB Police: Birbhum District



WB Police: Darjeeling



District



WB Police: Kharagpur GRP District



WB Police: Siliguri GRP District



WB Police: Sealdah GRP District



WB Police: Howrah GRP District



Annexure: Unit Details

Police Stations and Higher Offices:

CIPA Details

HQ Zone Range District SP Addl SP SDPO Circle/ IRP Police Station CCTNS Phase

Phase

Installation

date

No of PC

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP KALIMPONG

CI GARUBATHAN

O/C GARUBATHAN

Phase II

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP KALIMPONG

CI GARUBATHAN O/C JALDHAKA

Phase II

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP KALIMPONG

I/C KALIMPONG

Phase II

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP SADAR DSP SADAR CI SADAR

O/C JORABANGLOW

Phase II

WBP

North Beng

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP SADAR DSP SADAR CI SADAR O/C PALBAZAR

Phase II



CIPA Details


Phase

Installation

date

No of PC

al Zone

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP SADAR DSP SADAR CI SADAR O/C RANGALI

Phase II

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP SADAR DSP SADAR I/C DARJEELING

Phase II

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP SADAR DSP SADAR I/C LODHAMA

Phase II

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP SILIGURI DSP TOWN

CI BAGDOGRA O/C KHARIBARI

Phase II

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING


CI BAGDOGRA

O/C BAGDOGRA

Phase II

WBP

North Beng

Darjeeling Range

Darjeeling

SP DARJEELING


CI BAGDOGRA O/C MATIGARA

Phase II Phase II

3/11/2009

3



CIPA Details


Phase

Installation

date

No of PC

al Zone

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING


CI BAGDOGRA

O/C NAKSALBARI

Phase II Phase II

3/11/2009

4

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING


CI BAGDOGRA

O/C PHASHIDEWA

Phase II Phase II

4/11/2009

3

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP SILIGURI

I/C PRADHAN NAGAR PS SILIGURI

Phase II Phase II

26/11/2009

4

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

ADDL SP SILIGURI I/C SILIGURI

Phase II Phase II

16/02/2009

3

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

SDPO KURSEONG CI MIRIK O/C MIRIK

Phase II

WBP

North Beng

Darjeeling Range

Darjeeling

SP DARJEELING

SDPO KURSEONG CI MIRIK

O/C SUKHIAPOKHRI

Phase II



CIPA Details


Phase

Installation

date

No of PC

al Zone

WBP

North Bengal Zone

Darjeeling Range

Darjeeling

SP DARJEELING

SDPO KURSEONG I/C KURSEONG

Phase II

WBP

North Bengal Zone

Darjeeling Range

Uttar Dinajpur

SP UTTAR DINAJPUR

ADDL SP SADAR DSP SADAR

I/C KARAMDIGHI

Phase II

WBP

North Bengal Zone

Darjeeling Range

Uttar Dinajpur

SP UTTAR DINAJPUR

ADDL SP SADAR DSP SADAR I/C RAIGANJ

Phase II Phase II

23/10/2009

3

WBP

North Bengal Zone

Darjeeling Range

Uttar Dinajpur

SP UTTAR DINAJPUR

ADDL SP SADAR

SDPO ISLAMPUR

CI GOLPUKUR O/C CHAKULIA

Phase II

WBP

North Bengal Zone

Darjeeling Range

Uttar Dinajpur

SP UTTAR DINAJPUR

ADDL SP SADAR

SDPO ISLAMPUR

CI GOLPUKUR O/C GOLPUKUR

Phase II

WBP

North Beng

Darjeeling Range

Uttar Dinajpur

SP UTTAR DINAJPUR

ADDL SP SADAR

SDPO ISLAMPUR CI ITAHAR

O/C HEMTABAD

Phase II



CIPA Details


Phase

Installation

date

No of PC

al Zone

WBP

North Bengal Zone

Darjeeling Range

Uttar Dinajpur

SP UTTAR DINAJPUR

ADDL SP SADAR

SDPO ISLAMPUR CI ITAHAR O/C ITAHAR

Phase II

WBP

North Bengal Zone

Darjeeling Range

Uttar Dinajpur

SP UTTAR DINAJPUR

ADDL SP SADAR

SDPO ISLAMPUR I/C CHOPRA PS

Phase II

WBP

North Bengal Zone

Darjeeling Range

Uttar Dinajpur

SP UTTAR DINAJPUR

ADDL SP SADAR

SDPO ISLAMPUR I/C ISLAMPUR

Phase II Phase II

25/11/2009

3

WBP

North Bengal Zone

Darjeeling Range

Uttar Dinajpur

SP UTTAR DINAJPUR

ADDL SP SADAR

SDPO ISLAMPUR I/C KALIAGANJ

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR DSP SADAR I/C KOTWALI PS

Phase II Phase II

25/7/2009

5

WBP

North Beng

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR

SDPO (MATHABHANGA & CI DINHATA

O/C DINHATA PS

Phase II Phase II

25/7/2009

3



CIPA Details


Phase

Installation

date

No of PC

al Zone

MEKHLIGANJ)

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR

SDPO (MATHABHANGA & MEKHLIGANJ) CI DINHATA O/C SITAI PS

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR

SDPO (MATHABHANGA & MEKHLIGANJ)

CI MATHABHANGA

O/C GHOKSHADANGA PS

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR


CI MATHABHANGA

O/C MATHABHANGA PS

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR


CI MATHABHANGA

O/C SITALKUCHI

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR


CI MEKHLIGANJ

O/C KUCHLIBARI

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR


CI MEKHLIGANJ

O/C MEKHLIGANJ

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR


CI SADAR (TUFANGANJ)

O/C BAXIRHAT PS

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR


CI SADAR (TUFANGANJ)

O/C TUFANGANJ PS

Phase II Phase II

24/7/2009

3

WBP

North Bengal Zone

Jalpaiguri range

Cooch Bihar

SP COOCHBEHAR

ADDL SP SADAR

SDPO (MATHABHANGA & MEKHLIGANJ) I/C HALDIBARI

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR DSP SADAR CI SADAR

O/C BHAKTINAGAR PS

Phase II Phase II

1/4/2009

3

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR DSP SADAR CI SADAR

O/C RAYGANJ PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR

SDPO ALIPURDUAR CI BIRPARA

O/C BIRPARA PS

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR

SDPO ALIPURDUAR CI BIRPARA

O/C MADARIHAT

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR

SDPO ALIPURDUAR CI KALCHINI O/C JAYGAN PS

Phase II Phase II

2/4/2009

3

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR

SDPO ALIPURDUAR CI KALCHINI

O/C KALCHINI PS

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR

SDPO ALIPURDUAR CI KALCHINI

O/C SAMUKTALA PS

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR

SDPO ALIPURDUAR

I/C ALIPURDUAR

Phase II Phase II

30/3/2009

4



CIPA Details


Phase

Installation

date

No of PC

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR

SDPO ALIPURDUAR I/C FALAKATA

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP ALIPURDUAR

SDPO ALIPURDUAR

I/C KUMARGANJ

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP SADAR DSP CRIME I/C BANARHAT

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP SADAR DSP CRIME I/C DHUPGURI

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP SADAR DSP CRIME

I/C MOYNAGURI

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP SADAR DSP SADAR I/C KOTWALI PS

Phase II Phase II

31/3/2009

4



CIPA Details


Phase

Installation

date

No of PC

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP SADAR

SDPO MALBAZAR CI MAL O/C MAL PS

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP SADAR

SDPO MALBAZAR CI MAL O/C MATELI PS

Phase II

WBP

North Bengal Zone

Jalpaiguri range

Jalpaiguri

SP JALPAIGURI

ADDL SP SADAR

SDPO MALBAZAR CI MAL

O/C NAGRAKATA PS

Phase II

WBP

North Bengal Zone

Malda Range

Dakshin Dinjapur

SP DAKSHIN DINAJPUR


CI BALURGHAT O/C HILI

Phase II

WBP

North Bengal Zone

Malda Range

Dakshin Dinjapur

SP DAKSHIN DINAJPUR


CI BALURGHAT

O/C KUMARGANJ

Phase II

WBP

North Bengal Zone

Malda Range

Dakshin Dinjapur

SP DAKSHIN DINAJPUR


CI BALURGHAT O/C TAPAN

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

North Bengal Zone

Malda Range

Dakshin Dinjapur

SP DAKSHIN DINAJPUR

ADDL SP SADAR DSP SADAR I/C BALURGHAT

Phase II Phase II

29/7/2009

3

WBP

North Bengal Zone

Malda Range

Dakshin Dinjapur

SP DAKSHIN DINAJPUR

ADDL SP SADAR

SDPO GANGARAMPUR I/C BANSIHARI

Phase II

WBP

North Bengal Zone

Malda Range

Dakshin Dinjapur

SP DAKSHIN DINAJPUR

ADDL SP SADAR

SDPO GANGARAMPUR

I/C GANGARAMPUR

Phase II Phase II

30/7/2009

3

WBP

North Bengal Zone

Malda Range

Dakshin Dinjapur

SP DAKSHIN DINAJPUR

ADDL SP SADAR

SDPO GANGARAMPUR

I/C HARIRAMPUR

Phase II

WBP

North Bengal Zone

Malda Range

Dakshin Dinjapur

SP DAKSHIN DINAJPUR

ADDL SP SADAR

SDPO GANGARAMPUR

I/C KUSHMANDI

Phase II

WBP

North Bengal Zone

Malda Range Malda SP MALDA

ADDL SP SADAR DSP D&T

I/C BAISNAB NAGAR

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

North Bengal Zone



I/C ENGLISH BAZAR

Phase II

WBP

North Bengal Zone


ADDL SP SADAR DSP D&T I/C KALIACHAK

Phase II

WBP

North Bengal Zone



I/C MANIKCHAK

Phase II

WBP

North Bengal Zone


ADDL SP SADAR DSP SADAR CI GAZOLE

O/C BAMONGOLA

Phase II

WBP

North Bengal Zone


ADDL SP SADAR DSP SADAR CI GAZOLE O/C GAZOLE

Phase II

WBP

North Bengal Zone


ADDL SP SADAR DSP SADAR I/C HABIBPUR

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

North Bengal Zone


ADDL SP SADAR DSP SADAR I/C MALDA

Phase II

WBP

North Bengal Zone


ADDL SP SADAR

SDPO CHANCHOL CI RATUA

MANIKPUR (HARISHCHANDRAPUR)

Phase II

WBP

North Bengal Zone


ADDL SP SADAR

SDPO CHANCHOL CI RATUA RATUA

Phase II

WBP

North Bengal Zone


ADDL SP SADAR

SDPO CHANCHOL I/C CHANCHOL

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO DOMKOL CI DOMKOL ISLAMPUR

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO DOMKOL CI DOMKOL JALANGI

Phase II

WBP

South Beng

Murshidabad

Mushidabad

SP MURSHID

ADDL SP LALBAG

SDPO DOMKOL CI DOMKOL RANINAGAR

Phase II



CIPA Details


Phase

Installation

date

No of PC

al Zone

Range ABAD

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO DOMKOL I/C DOMKAL

Phase II Phase II

15/10/2009

4

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO JANGIPUR

CI JANGIPUR SAGARDIGHI

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO JANGIPUR

CI JANGIPUR SAMSERGANJ

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO JANGIPUR

CI JANGIPUR SUTI

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO JANGIPUR

I/C FARAKKABARAGE

Phase II Phase II

16/10/2009

3

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO JANGIPUR

I/C RAGHUNATHGANJ

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO LALBAG CI LALBAG

BHAGABANGOLA

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO LALBAG CI LALBAG JIYAGANJ

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO LALBAG CI LALBAG LALGOLA

Phase II Phase II

11/9/2009

4

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO LALBAG CI LALBAG NABAGRAM

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO LALBAG CI LALBAG RANITALA

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP LALBAG

SDPO LALBAG

I/C MURSHIDABAD

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP SADAR DSP CRIME CI SADAR O/C BELDANGA

Phase II Phase II

10/10/2009

4

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP SADAR DSP CRIME CI SADAR O/C REJINAGAR

Phase II

WBP

South Beng

Murshidabad

Mushidabad

SP MURSHID

ADDL SP SADAR DSP D&T CI SADAR

O/C DOULATABAD

Phase II



CIPA Details


Phase

Installation

date

No of PC

al Zone

Range ABAD

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD


O/C HARIHARPARA

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP SADAR DSP D&T CI SADAR O/C NOWDA

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD


I/C BAHARAMPUR

Phase II Phase II

14/10/2009

5

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP SADAR

SDPO KANDI CI KANDI BHARATPUR

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP SADAR

SDPO KANDI CI KANDI BURWAN

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP SADAR

SDPO KANDI CI KANDI KHARGRAM

Phase II

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP SADAR

SDPO KANDI CI KANDI SALAR

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone

Murshidabad Range

Mushidabad

SP MURSHIDABAD

ADDL SP SADAR

SDPO KANDI I/C KANDI

Phase II Phase II

12/10/2009

4

WBP

South Bengal Zone

Murshidabad Range Nadia SP NADIA


CI NAKASHIPARA O/C DHUBULIA

Phase II

WBP

South Bengal Zone



CI NAKASHIPARA O/C KALIGANJ

Phase II

WBP

South Bengal Zone



CI NAKASHIPARA

O/C NAKASHIPARA

Phase II

WBP

South Bengal Zone


ADDL SP SADAR DSP D&T I/C NABADWIP

Phase II

WBP

South Bengal Zone



CI KRISHNAGANJ

O/C CHAPRA (CHAKLA)

Phase II

WBP

South Bengal Zone



CI KRISHNAGANJ

O/C KRISHNAGANJ

Phase II

WBP

South Beng

Murshidabad Nadia SP NADIA


I/C KOTWALI (KRISHNAGAR)

Phase II Phase II

28/02/2008

4



CIPA Details


Phase

Installation

date

No of PC

al Zone

Range

WBP

South Bengal Zone


ADDL SP SADAR

SDPO KALYANI I/C CHAKDA

Phase II Phase II

29/02/2008

4

WBP

South Bengal Zone


ADDL SP SADAR

SDPO KALYANI

I/C HARINGHATA

Phase II

WBP

South Bengal Zone


ADDL SP SADAR

SDPO KALYANI I/C KALYANI

Phase II Phase II

29/02/2008

4

WBP

South Bengal Zone


ADDL SP SADAR

SDPO RANAGHAT

CI SANTIPUR O/C DHANTALA

Phase II

WBP

South Bengal Zone


ADDL SP SADAR

SDPO RANAGHAT

CI SANTIPUR

O/C GANGNAPUR

Phase II

WBP

South Bengal Zone


ADDL SP SADAR

SDPO RANAGHAT

CI SANTIPUR

O/C HANSKHALI

Phase II

WBP

South Bengal Zone


ADDL SP SADAR

SDPO RANAGHAT

CI SANTIPUR O/C SANTIPUR

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone


ADDL SP SADAR

SDPO RANAGHAT

CI SANTIPUR O/C TAHERPUR

Phase II

WBP

South Bengal Zone


ADDL SP SADAR

SDPO RANAGHAT I/C RANAGHAT

Phase II Phase II

29/02/2008

4

WBP

South Bengal Zone


ADDL SP SADAR

SDPO TEHATTA

CI KARIMPUR

O/C HAGOLBERIA

Phase II

WBP

South Bengal Zone


ADDL SP SADAR

SDPO TEHATTA

CI KARIMPUR O/C KARIMPUR

Phase II

WBP

South Bengal Zone


ADDL SP SADAR

SDPO TEHATTA

CI KARIMPUR O/C MURUTIA

Phase II

WBP

South Bengal Zone


ADDL SP SADAR

SDPO TEHATTA

CI KARIMPUR

O/C THANARPARA

Phase II

WBP

South Bengal Zone


ADDL SP SADAR

SDPO TEHATTA I/C TEHATTA

Phase II

WBP

South Beng

Presidency Range Howrah

SP HOWRAH

ADDL SP RURAL DSP D&T

CI MUNSHIRH J B PUR PS

Phase II Phas

e I 31/10/2006

3



CIPA Details


Phase

Installation

date

No of PC

al Zone

AT

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL DSP D&T I/C DOMJUR PS

Phase II Phas

e I 2/11/2

006 4

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL DSP SADAR

CI SANKRAIL PANCHLA PS

Phase II

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL DSP SADAR

CI SANKRAIL SANKRAIL PS

Phase II Phas

e I 31/10/2006

4

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL

SDPO ULUBERIA CI AMTA AMTA PS

Phase II Phase II

13/7/2009

4

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL

SDPO ULUBERIA CI AMTA JOYPUR PS

Phase II

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL

SDPO ULUBERIA

CI Garchumuk BOURIA PS

Phase II

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL

SDPO ULUBERIA

CI Garchumuk SHYAMPUR PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL

SDPO ULUBERIA

CI MUNSHIRHAT U N PUR PS

Phase II

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL

SDPO ULUBERIA I/C BAGNAN PS

Phase II Phase II

14/7/2009

5

WBP

South Bengal Zone


SP HOWRAH

ADDL SP RURAL

SDPO ULUBERIA

I/C ULUBERIA PS

Phase II Phase II

15/7/2009

5

WBP

South Bengal Zone


SP HOWRAH

ADDL SP TOWN DSP (T/N) I/C BALLY PS

Phase II Phas

e I 26/10/2006

4

WBP

South Bengal Zone


SP HOWRAH

ADDL SP TOWN DSP (T/N)

I/C GOLABARI PS

Phase II Phas

e I 19/10/2006

5

WBP

South Bengal Zone


SP HOWRAH

ADDL SP TOWN DSP (T/N) I/C LILUAH PS

Phase II Phas

e I 20/10/2006

3

WBP

South Bengal Zone


SP HOWRAH

ADDL SP TOWN DSP (T/N)

I/C MP GHORA PS

Phase II

WBP

South Beng


SP HOWRAH

ADDL SP TOWN DSP (T/S)

I/C HOWRAH PS

Phase II Phas

e I 16/10/2006

5



CIPA Details


Phase

Installation

date

No of PC

al Zone

WBP

South Bengal Zone


SP HOWRAH

ADDL SP TOWN DSP (T/S) I/C BANTRA PS

Phase II Phas

e I 27/10/2006

4

WBP

South Bengal Zone


SP HOWRAH

ADDL SP TOWN DSP (T/S) I/C JAGACHA PS

Phase II Phas

e I 30/10/2006

3

WBP

South Bengal Zone


SP HOWRAH

ADDL SP TOWN DSP (T/S) I/C SHIBPUR PS

Phase II Phas

e I 17/10/2006

4

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BARRACKPORE I/C BIZPUR PS

Phase II Phase II

2/12/2009

4

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BARRACKPORE

I/C JAGADDAL PS

Phase II Phas

e I 17/11/2006

5

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BARRACKPORE I/C NAIHATI PS

Phase II Phas

e I 16/11/2006

5

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BARRACKPORE

I/C NOAPARA PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BARRACKPORE

I/C TITAGARH PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BELGHORIA I/C AIRPORT PS

Phase II Phas

e I 7/11/2

006 5

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BELGHORIA

I/C BARANAGAR PS

Phase II Phas

e I 10/11/2006

4

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BELGHORIA

I/C BELGHORIA PS

Phase II Phas

e I 13/11/2006

5

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BELGHORIA

I/C DUM DUM PS

Phase II Phas

e I 8/11/2

006 5

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BELGHORIA I/C GHOLA PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BELGHORIA

I/C KHARDAH PS

Phase II Phas

e I 20/12/2006

5

WBP

South Beng

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACK

SDPO BELGHORIA I/C NIMTA PS

Phase II Phas

e I 9/11/2

006 5



CIPA Details


Phase

Installation

date

No of PC

al Zone

PORE

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BARRACKPORE

SDPO BELGHORIA

I/C NSCBI AIRPORT PS

Phase II Phas

e I 6/11/2

006 5

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BIDHANNAGAR

SDPO BIDHANNAGAR

ELECTORNIC COMPLEX PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BIDHANNAGAR

SDPO BIDHANNAGAR

I/C BIDHANNAGAR EAST PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BIDHANNAGAR

SDPO BIDHANNAGAR

I/C BIDHANNAGAR NORTH PS

Phase II Phas

e I 14/11/2006

5

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BIDHANNAGAR

SDPO BIDHANNAGAR

I/C BIDHANNAGAR SOUTH PS

Phase II Phase II

20/07/2009

4

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP BIDHANNAGAR

SDPO BIDHANNAGAR

I/C LAKETOWN PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BONGAON

I/C BONGAON PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT CI HABRA AMDANGA PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT CI HABRA

ASHOKE NAGAR PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT CI HAROA DEGANGA PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT CI HAROA HAROA PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT CI HAROA MINAKHA PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT BAGUIHATI PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT I/C BARASAT PS

Phase II Phas

e I 20/11/2006

5

WBP

South Beng

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT I/C HABRA PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

al Zone

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT

I/C RAJARHAT PS

Phase II Phas

e I 21/11/2006

5

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARASAT NEW TOWN PS

Phase II Phase II

23/12/2009

4

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BARRACKPORE

I/C BARRACKPORE PS

Phase II Phas

e I 15/11/2006

4

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BASIRHAT

CI HASNABAD HASNABAD PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BASIRHAT

CI HASNABAD

HINGALGANJ PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BASIRHAT

CI HASNABAD

SANDESH KHALI PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BASIRHAT

CI SWARUPNAGAR BADURIA PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BASIRHAT

CI SWARUPNAGAR

SWARUPNAGAR PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BASIRHAT

I/C BASIRHAT PS

Phase II Phase II

7/9/2009

4

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BONGAON

CI GAIGHATA BAGDAH PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BONGAON

CI GAIGHATA GAIGHATA PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS.

ADDL SP NORTH

SDPO BONGAON

CI GAIGHATA

GOPALNAGAR PS

Phase II

WBP

South Bengal Zone

Presidency Range

North 24 Pgs

SP NORTH 24-PGS. HEMNAGAR PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL DSP CRIME I/C KASBA PS

Phase II Phas

e I 4/12/2

006 5

WBP

South Beng

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRI DSP CRIME

I/C PURBA JADAVPUR PS

Phase II Phase II

3/12/2009

4



CIPA Details


Phase

Installation

date

No of PC

al Zone

AL

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL DSP CRIME I/C TILJALA PS

Phase II Phas

e I 5/12/2

006 5

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL DSP D&T

I/C BISHNUPUR PS

Phase II Phas

e I 2/12/2

006 5

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL DSP D&T

I/C NODAKHALI PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL

DSP INDUSTRIAL

I/C BUDGE BUDGE PS

Phase II Phas

e I 7/12/2

006 5

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL

DSP INDUSTRIAL

I/C MAHESHTALA PS

Phase II Phas

e I 6/12/2

006 5

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL

DSP INDUSTRIAL

I/C METIABRUZ PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL

DSP INDUSTRIAL I/C NADIAL PS

Phase II Phas

e I 19/12/2006

3



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL

DSP INDUSTRIAL

I/C RABINDRANAGAR PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL DSP TOWN I/C BEHALA PS

Phase II Phas

e I 28/11/2006

5

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP INDUSTRIAL DSP TOWN

I/C JADAVPUR PS

Phase II Phas

e I 27/11/2006

5

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.


I/C REGENT PARK PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.


I/C THAKURPUKUR PS

Phase II Phas

e I 30/11/2006

5

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO BARUIPUR

CI BHANGORE BHANGORE PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO BARUIPUR

CI BHANGORE JOYNAGAR PS

Phase II Phas

e I 15/12/2006

4

WBP

South Beng

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO BARUIPUR

CI BHANGORE KASHIPUR PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

al Zone

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO BARUIPUR

CI BHANGORE

KOLKATA LEATHER COMPLEX PS (KLC)

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO BARUIPUR

CI BHANGORE KULTALI PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO BARUIPUR

CI BHANGORE

MAIPITH COASTAL PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO BARUIPUR

I/C BARUIPUR PS

Phase II Phas

e I 8/12/2

006 5

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO BARUIPUR

I/C SONARPUR PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO CANNING

CI CANNING BASANTI PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO CANNING

CI CANNING CANNING PS

Phase II Phas

e I 11/12/2006

3



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO CANNING

CI CANNING GOSABA PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO CANNING

CI CANNING JIBANTALA PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO CANNING

CI CANNING

SUNDARBAN COASTAL / KISHORIMOHANPORE PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO DIAMOND HARBOUR

CI MAGRAHAT MAGRAHAT PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL


CI MAGRAHAT USTHI PS

Phase II Phas

e I 12/12/2006

3

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL


CI MANDIRBAZAR KULPI PS

Phase II Phase II

9/9/2009

3

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL


CI MANDIRBAZAR

MANDIR BAZAR PS

Phase II

WBP

South Beng

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO DIAMOND

CI MANDIRBA

MATHURAPUR PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

al Zone

HARBOUR ZAR

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL


CI MANDIRBAZAR RAIDIGHI PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL


I/C DIAMOND HARBOUR PS

Phase II Phas

e I 13/12/2006

3

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO DIAMOND HARBOUR I/C FALTA PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL


I/C RAMNAGAR PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO KAKDWIP CI KAKDWIP DHOLAHAT PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO KAKDWIP CI KAKDWIP FREZERGANJ PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO KAKDWIP CI KAKDWIP KAKDWIP PS

Phase II Phase II

8/9/2009

4



CIPA Details


Phase

Installation

date

No of PC

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO KAKDWIP CI KAKDWIP NAMKHANA PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO KAKDWIP CI KAKDWIP

PATHAR PRATIMA PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

ADDL SP RURAL

SDPO KAKDWIP CI KAKDWIP SAGAR PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS.

HALDIBARI COASTAL PS

Phase II

WBP

South Bengal Zone

Presidency Range

South 24 Pgs

SP SOUTH 24-PGS. SARSUNA PS

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM


CI (A) SADAR O/C MD BAZAR

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM


CI (A) SADAR O/C SADAIPUR

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM


CI (A) SADAR O/C SAINTHIA

Phase II

W West Burdwan BIRBHU SP ADDL SP DSP SADAR CI (B) O/C Phase II



CIPA Details


Phase

Installation

date

No of PC

BP ern Zone

range M BIRBHUM SADAR DUBRAJPUR

DUBRAJPUR

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM


CI (B) DUBRAJPUR

O/C KANKARTALA

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM


CI (B) DUBRAJPUR

O/C KHAIRASOLE

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM


CI (B) DUBRAJPUR O/C RAJNAGAR

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR DSP SADAR I/C SURI

Phase II Phase II

8/10/2010

4

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR

SDPO RAMPURHAT

CI MURARAI O/C MURARAI

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR

SDPO RAMPURHAT

CI MURARAI O/C NALHATI

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR

SDPO RAMPURHAT

CI RAMPURHAT O/C MARGRAM

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR

SDPO RAMPURHAT

CI RAMPURHAT

O/C MAYURESWAR

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR

SDPO RAMPURHAT

I/C RAMPURHAT

Phase II

W West Burdwan BIRBHU SP ADDL SP SDPO CI BOLEPUR O/C Phase II



CIPA Details


Phase

Installation

date

No of PC

BP ern Zone

range M BIRBHUM SADAR BOLEPUR ILAMBAZAR

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR

SDPO BOLEPUR CI BOLEPUR O/C PANRUI

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR

SDPO BOLEPUR CI NANOOR O/C LAVPUR

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR

SDPO BOLEPUR CI NANOOR O/C NANOOR

Phase II

WBP

Western Zone

Burdwan range

BIRBHUM

SP BIRBHUM

ADDL SP SADAR

SDPO BOLEPUR I/C BOLEPUR

Phase II Phase II

9/10/2009

5

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP ASANSOL DSP SADAR CI ASANSOL

O/C ASANSOL(N)

Phase I Phase II

2/9/2009

4

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP ASANSOL DSP SADAR CI ASANSOL

O/C ASANSOL(S)

Phase I Phase II

2/9/2009

4

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP ASANSOL DSP SADAR

CI RANIGANJ O/C JAMURIA

Phase I Phase II

3/9/2009

3

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP ASANSOL DSP SADAR

CI RANIGANJ O/C RANIGANJ

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP ASANSOL DSP SR CI HIRAPUR O/C BARABONI

Phase I

W West Burdwan Burdwa SP ADDL SP DSP SR CI HIRAPUR O/C HIRAPUR Phase I



CIPA Details


Phase

Installation

date

No of PC

BP ern Zone

range n BURDWAN

ASANSOL

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP ASANSOL DSP SR

I/C CHITTARANJAN

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP ASANSOL DSP SR I/C KULTI

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP ASANSOL DSP SR I/C SALANPUR

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP DURGAPUR

SDPO DURGAPUR

CI (A) DURGAPUR

O/C COKE OVEN

Phase I Phase II

3/9/2009

4

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP DURGAPUR

SDPO DURGAPUR

CI (A) DURGAPUR

O/C DURGAPUR

Phase I Phase II

4/9/2009

4

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP DURGAPUR

SDPO DURGAPUR

CI (A) DURGAPUR

O/C NEW TOWNSHIP

Phase I Phase II

3/9/2009

4

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP DURGAPUR

SDPO DURGAPUR

CI (B) DURGAPUR O/C ANDAL

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP DURGAPUR

SDPO DURGAPUR

CI (B) DURGAPUR O/C BUD BUD

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP DURGAPUR

SDPO DURGAPUR

CI (B) DURGAPUR O/C FARIDPUR

Phase I

W West Burdwan Burdwa SP ADDL SP SDPO CI (B) O/C KANKSA Phase I



CIPA Details


Phase

Installation

date

No of PC

BP ern Zone

range n BURDWAN

DURGAPUR

DURGAPUR DURGAPUR

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP DURGAPUR

SDPO DURGAPUR

CI (B) DURGAPUR O/C LAUDA

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP DURGAPUR

SDPO DURGAPUR

CI (B) DURGAPUR

O/C PANDABESWAR

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN


CI (B) SADAR O/C JAMALPUR

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN


CI (B) SADAR O/C MEMARI

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN


CI (C) SADAR

O/C KHANDAGHOSH

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN


CI (C) SADAR

O/C MADHABDIHI

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN


CI (C) SADAR O/C RAINA

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN


CI (A) SADAR O/C BHATAR

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN


CI (A) SADAR O/C GALSI

Phase I Phase II

22/7/2009

3

W West Burdwan Burdwa SP ADDL SP DSP SADAR I/C AUSGRAM Phase I



CIPA Details


Phase

Installation

date

No of PC

BP ern Zone

range n BURDWAN

SADAR

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN


I/C BURDWAN (SADAR)

Phase I Phase II

21/7/2009

4

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP SADAR

SDPO KALNA CI KAlNA O/C KANLA

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP SADAR

SDPO KALNA CI KAlNA

O/C MONGALKOTE

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP SADAR

SDPO KALNA CI KAlNA

O/C MONTESWAR

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP SADAR

SDPO KALNA

I/C PURBASHTALI

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP SADAR

SDPO KATWA CI KATWA O/C KATWA

Phase I

WBP

Western Zone

Burdwan range

Burdwan

SP BURDWAN

ADDL SP SADAR

SDPO KATWA I/C KETUGRAM

Phase I

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


CI (B) MOGRA

O/C BALAGARH PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


CI (B) MOGRA O/C MOGRA PS

Phase II Phas

e I 25/09/2006

3

W West Burdwan HOOGH SP ADDL SP DSP D&T CI (B) O/C PANDUA Phase II Phas 26/09/ 3



CIPA Details


Phase

Installation

date

No of PC

BP ern Zone

range LY HOOGHLY SADAR MOGRA PS e I 2006

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


I/C CHINSURAH PS

Phase II Phas

e I 19/09/2006

4

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


CI (A) SADAR

O/C DADPUR PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


CI (A) SADAR

O/C DHANIAKHALI PS

Phase II Phas

e I 13/10/2006

3

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


CI (A) SADAR O/C GURAP PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


CI (A) SADAR O/C POLBA PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY

ADDL SP SADAR

SDPO ARAMBAG

CI ARAMBAG

O/C GOGHAT PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY

ADDL SP SADAR

SDPO ARAMBAG

CI ARAMBAG

O/C KHANAKUL PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY

ADDL SP SADAR

SDPO ARAMBAG

CI ARAMBAG

O/C PURSURAH PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY

ADDL SP SADAR

SDPO ARAMBAG

I/C ARAMBAG PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY

ADDL SP (INDUSTRIAL), SERAMPORE

SDPO CHANDANNAGAR

CI CHANDANNAGAR

O/C BHADRESWAR PS

Phase II Phas

e I 15/09/2006

4

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO CHANDANNAGAR

CI CHANDANNAGAR

O/C CHANDANNAGAR PS

Phase II Phas

e I 15/09/2006

4

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO CHANDANNAGAR

CI TARAKESWAR

O/C HARIPAL PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO CHANDANNAGAR

CI TARAKESWAR O/C SINGUR PS

Phase II Phas

e I 10/10/2006

3

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO CHANDANNAGAR

CI TARAKESWAR

O/C TARAKESWAR PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO SERAMPORE

CI UTTARAPARA

O/C CHANDITALA PS

Phase II Phas

e I 12/10/2006

3



CIPA Details


Phase

Installation

date

No of PC

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO SERAMPORE

CI UTTARAPARA

O/C DANKUNI PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO SERAMPORE

CI UTTARAPARA

O/C JANGIPARA PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO SERAMPORE

CI UTTARAPARA O/C RISHRA PS

Phase II

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO SERAMPORE

I/C SERAMPORE PS

Phase II Phas

e I 20/09/2006

4

WBP

Western Zone

Burdwan range

HOOGHLY

SP HOOGHLY


SDPO SERAMPORE

I/C UTTARAPARA PS

Phase II Phas

e I 11/10/2006

3

WBP

Western Zone

Midnapur Range Bankura

SP BANKURA

ADDL SP SADAR DSP D&T I/C RAIPUR

Phase II

WBP

Western


SP BANKURA

ADDL SP SADAR DSP D&T I/C RANIBANDH

Phase II



CIPA Details


Phase

Installation

date

No of PC

Zone

WBP

Western Zone


SP BANKURA

ADDL SP SADAR DSP D&T I/C SARENGA

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR DSP D&T I/C SIMLAPAL

Phase II

WBP

Western Zone


SP BANKURA


CI GANGAJALGHATI

GANGAJALGHATI

Phase II

WBP

Western Zone


SP BANKURA


CI GANGAJALGHATI MEJHIA

Phase II

WBP

Western Zone


SP BANKURA


CI GANGAJALGHATI SALTORA

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR DSP Sadar CI SADAR CHHATNA

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR DSP SADAR CI SADAR ONDA

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR DSP SADAR CI SADAR TALDANGA

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR DSP SADAR CI SADAR BELIATORE

Phase II

WBP

Western


SP BANKURA

ADDL SP SADAR DSP SADAR I/C BANKURA

Phase II



CIPA Details


Phase

Installation

date

No of PC

Zone

WBP

Western Zone


SP BANKURA

ADDL SP SADAR DSP SADAR I/C BARJORA

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR

SDPO KHATRA CI INDPUR BARIKUL

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR

SDPO KHATRA CI INDPUR HIRABANDH

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR

SDPO KHATRA CI INDPUR INDPUR

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR

SDPO KHATRA I/C KHATRA

Phase II Phase II

19/11/2009

3

WBP

Western Zone


SP BANKURA

ADDL SP SADAR

SDPO VISHNUPUR

CI KOTULPUR JOYPUR

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR

SDPO VISHNUPUR

CI KOTULPUR KOTULPUR

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR

SDPO VISHNUPUR

CI SONAMUKHI INDUS

Phase II

WBP

Western Zone


SP BANKURA

ADDL SP SADAR

SDPO VISHNUPUR

CI SONAMUKHI PATRASAYER

Phase II

WBP

Western


SP BANKURA

ADDL SP SADAR

SDPO VISHNUPUR

CI SONAMUK SONAMUKHI

Phase II Phase II

18/11/2009

4



CIPA Details


Phase

Installation

date

No of PC

Zone HI

WBP

Western Zone


SP BANKURA

ADDL SP SADAR

SDPO VISHNUPUR I/C VISHNUPUR

Phase II

WBP

Western Zone

Midnapur Range

Jhargram Police District

SP JHARGRAM POLICE DISTRICT

ADDL SP OPERATION

SDPO JHARGRAM

CI GOPIBALLAVPUR O/C BELIABERA

Phase II

WBP

Western Zone

Midnapur Range



ADDL SP OPERATION

SDPO JHARGRAM

CI GOPIBALLAVPUR O/C SANKRAIL

Phase II

WBP

Western Zone

Midnapur Range



ADDL SP OPERATION

SDPO JHARGRAM I/C BELPAHARI

Phase II

WBP

Western Zone

Midnapur Range



ADDL SP OPERATION

SDPO JHARGRAM I/C BINPUR

Phase II

WBP

Western Zone

Midnapur Range



ADDL SP OPERATION

SDPO JHARGRAM

I/C GOPIBLLAVPUR

Phase II

WBP

Western Zone

Midnapur Range



ADDL SP OPERATION

SDPO JHARGRAM I/C JAMBONI

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

Western Zone

Midnapur Range



ADDL SP OPERATION

SDPO JHARGRAM I/C JHARGRAM

Phase II

WBP

Western Zone

Midnapur Range



ADDL SP OPERATION

SDPO JHARGRAM I/C NAYAGRAM

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP SADAR DSP ADMIN I/C KOTWALI PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP SADAR DSP CRIME CI GHATAL DASPUR PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP SADAR DSP CRIME CI GHATAL GHATAL PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP SADAR DSP CRIME CI SADAR

CHANDRAKONA PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP SADAR DSP CRIME CI SADAR GORBETA PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP SADAR

DSP OPERATION CI KESHPUR

ANANDAPUR PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP SADAR

DSP OPERATION CI KESHPUR KESHPUR PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP SADAR

DSP OPERATION CI KESHPUR SALBONI PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP SADAR

DSP OPERATION

I/C GOALTOR PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR CI BELDA BELDAH PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR CI BELDA KESHARI PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR CI DEBRA DEBRA PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR CI DEBRA PINGLA PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR CI DEBRA SABANG PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR CI KGP

KHARAGPUR LOCAL PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR CI KGP

NARAYANGARH PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR I/C DATAN PS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR

I/C KHARAGPUR TOWN PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR

SDPO KHARAGPUR

I/C MOHANPUR PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR Gurguripal PS

Phase II

WBP

Western Zone

Midnapur Range

Pachim Medinipur

SP PAS. MEDINIPORE

ADDL SP KHARAGPUR I/C LALGARH

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI

SDPO CONTAI

CI BHUPATINAGAR

O/C BHUPATINAGAR

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI

SDPO CONTAI

CI BHUPATINAGAR

O/C DIGHA MOHANA COSTAL PS

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI

SDPO CONTAI

CI BHUPATINAGAR O/C KHEJURI

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI

SDPO CONTAI

CI BHUPATINAGAR O/C MARIZDA

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI

SDPO CONTAI

CI BHUPATINAGAR

O/C TALPATTIGHAT PS

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI

SDPO CONTAI CI CONTAI O/C DIGHA

Phase II Phase II

27/11/2009

4



CIPA Details


Phase

Installation

date

No of PC

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI

SDPO CONTAI CI CONTAI

O/C RAMNAGAR

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI

SDPO CONTAI I/C CONTAI

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI SDPO EGRA CI EGRA

O/C BHAGABANPUR

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI SDPO EGRA CI EGRA O/C EGRA

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP CONTAI SDPO EGRA CI EGRA

O/C PATASHPUR

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP HALDIA

SDPO HALDIA

CI MAHISADAL O/C BHANIPUR

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP HALDIA

SDPO HALDIA

CI MAHISADAL

O/C DURGACHAK

Phase II Phase II

15/12/2009

4

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP HALDIA

SDPO HALDIA

CI MAHISADAL

O/C MAHISADAL

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP HALDIA

SDPO HALDIA

CI MAHISADAL

O/C NANDIGRAM

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP HALDIA

SDPO HALDIA

CI MAHISADAL O/C SUTAHATA

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP HALDIA

SDPO HALDIA I/C HALDIA

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP SADAR

SDPO TAMLUK

CI NANDAKUMAR

O/C CHANDIPUR

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP SADAR

SDPO TAMLUK

CI NANDAKUMAR O/C MAYNA

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP SADAR

SDPO TAMLUK

CI NANDAKUMAR

O/C NADAKUMAR

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP SADAR

SDPO TAMLUK CI TAMLUK O/C KOLAGHAT

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP SADAR

SDPO TAMLUK CI TAMLUK O/C PANSKURA

Phase II

WBP

Western Zone

Midnapur Range

Purba Medinipur

SP PURBA MEDINIPUR

ADDL SP SADAR

SDPO TAMLUK CI TAMLUK O/C TAMLUK

Phase II

WBP

Western Zone

Midnapur Range Purulia

SP PURULIA

ADDL SP SADAR DSP D&T CI SADAR ARSHA PS

Phase I

WBP

Western Zone


SP PURULIA

ADDL SP SADAR DSP D&T CI SADAR KOTSHILA PS

Phase I

WBP

Western Zone


SP PURULIA


PURULIA MAFARSHAL PS

Phase I



CIPA Details


Phase

Installation

date

No of PC

WBP

Western Zone


SP PURULIA


PURULIA TOWN PS

Phase I Phase II

12/2/2009

3

WBP

Western Zone


SP PURULIA

ADDL SP SADAR DSP D&T I/C JALDAH PS

Phase I

WBP

Western Zone


SP PURULIA

ADDL SP SADAR DSP D&T I/C JOYPUR PS

Phase I

WBP

Western Zone


SP PURULIA

ADDL SP SADAR DSP DEB

CI MANBAZAR HURA PS

Phase I

WBP

Western Zone


SP PURULIA


CI MANBAZAR KENDA PS

Phase I

WBP

Western Zone


SP PURULIA


CI MANBAZAR MANBAZAR PS

Phase I

WBP

Western Zone


SP PURULIA


CI MANBAZAR PUNCHA PS

Phase I

WBP

Western Zone


SP PURULIA


CI BALARAMPUR BAGMUNDI PS

Phase I

WBP

Western Zone


SP PURULIA


CI BALARAMPUR

BALARAMPUR PS

Phase I

WBP

Western Zone


SP PURULIA


CI BALARAMPUR BANDOAN PS

Phase I



CIPA Details


Phase

Installation

date

No of PC

WBP

Western Zone


SP PURULIA


CI BALARAMPUR BARABAZAR PS

Phase I

WBP

Western Zone


SP PURULIA


CI BALARAMPUR BORO PS

Phase I

WBP

Western Zone


SP PURULIA

ADDL SP SADAR

SDPO RAGHUNATHPUR

CI KASHIPUR KASHIPUR PS

Phase I

WBP

Western Zone


SP PURULIA

ADDL SP SADAR

SDPO RAGHUNATHPUR

CI KASHIPUR PARA PS

Phase I

WBP

Western Zone


SP PURULIA

ADDL SP SADAR

SDPO RAGHUNATHPUR

CI RAGHUNATHPUR NATURIA PS

Phase I

WBP

Western Zone


SP PURULIA

ADDL SP SADAR

SDPO RAGHUNATHPUR

CI RAGHUNATHPUR

RAGHUNATHPUR PS

Phase I Phase II

12/2/2009

4

WBP

Western Zone


SP PURULIA

ADDL SP SADAR

SDPO RAGHUNATHPUR

CI RAGHUNATHPUR SATURI PS

Phase I

WBP

Western Zone


SP PURULIA

ADDL SP SADAR

SDPO RAGHUNATHPUR

I/C SANTALDIHI PS

Phase I

WBP

Howrah GRP

SRP HOWRAH

DSRP (CORD) IRP KATWA

O/C AJIMGANJ GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH


O/C BELUR GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH


O/C KALNA GRPS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

Howrah GRP

SRP HOWRAH


O/C KATWA GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH

DSRP ASSANSOL IRP ANDAL

O/C ANDAL GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH

DSRP ASSANSOL IRP ANDAL

O/C SAITHIA GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH

DSRP ASSANSOL IRP ANDAL O/C SURI GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH

DSRP ASSANSOL

I/C ASANSOL GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH

DSRP SADAR IRP BANDEL

O/C BANDEL GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH


O/C BURDWAN GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH


O/C KAMERKUNDU GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH


O/C SHEORAPHULY GRPS

Phase II

WBP

Howrah GRP

SRP HOWRAH

DSRP SADAR

I/C HOWRAH GRPS

Phase II Phase II

4/12/2009

4

WBP

Kharagpur GRP

SRP KHARAGPUR

DSRP KHARAGPUR

IRP (ADRA) GRP ADRA GRPS

Phase II

WBP

Kharagpur GRP

SRP KHARAGPUR

DSRP KHARAGPUR

IRP (ADRA) GRP BANKURA GRPS

Phase II

WBP

Kharagpur GRP

SRP KHARAGP

DSRP KHARAGPU

IRP (ADRA) GRP PURULIA GRPS

Phase II



CIPA Details


Phase

Installation

date

No of PC

UR R

WBP

Kharagpur GRP

SRP KHARAGPUR

DSRP KHARAGPUR

IRP (HQ) KGP GRP SALIMAR GRPS

Phase II

WBP

Kharagpur GRP

SRP KHARAGPUR

DSRP KHARAGPUR

IRP KHARAGPUR GRP HALDIA GRPS

Phase II

WBP

Kharagpur GRP

SRP KHARAGPUR

DSRP KHARAGPUR

IRP KHARAGPUR GRP

JHARGRAM GRPS

Phase II

WBP

Kharagpur GRP

SRP KHARAGPUR

DSRP KHARAGPUR

IRP KHARAGPUR GRP

KHARAGPUR GRPS

Phase II

WBP

Kharagpur GRP

SRP KHARAGPUR

DSRP KHARAGPUR

IRP KHARAGPUR GRP PANSKURA GRP

Phase II

WBP

Sealdah GRP

SRP SEALDAH

DSRP (CORD)

IRP BARASAT

O/C BARASAT GRPS

Phase II

WBP

Sealdah GRP

SRP SEALDAH

DSRP (CORD)

IRP BARASAT

O/C BONGAON GRPS

Phase II

WBP

Sealdah GRP

SRP SEALDAH

DSRP (CORD)

I/C NAIHATI GRPS

Phase II

WBP

Sealdah GRP

SRP SEALDAH DSRP DEB

IRP SONARPUR

O/C BARUIPUR GRPS

Phase II

WBP

Sealdah GRP


IRP SONARPUR

O/C DIAMONDHARBOUR GRPS

Phase II

WBP

Sealdah GRP


IRP SONARPUR

O/C JADAVPUR GRPS

Phase II



CIPA Details


Phase

Installation

date

No of PC

WBP

Sealdah GRP


IRP SONARPUR

O/C SONARPUR GRPS

Phase II

WBP

Sealdah GRP

SRP SEALDAH

DSRP RANAGHAT

IRP KRISHNAGAR

O/C BERHAMPUR GRPS

Phase II

WBP

Sealdah GRP

SRP SEALDAH

DSRP RANAGHAT

IRP KRISHNAGAR

O/C KRISHNAGAR GRPS

Phase II

WBP

Sealdah GRP

SRP SEALDAH

DSRP RANAGHAT

I/C RANAGHAT GRPS

Phase II

WBP

Sealdah GRP

SRP SEALDAH

DSRP SADAR IC (CR)

O/C BALIGUNJ GRPS

Phase II

WBP

Sealdah GRP

SRP SEALDAH

DSRP SADAR IC (CR)

O/C DUM DUM GRPS

Phase II Phase II

30/12/2008

3

WBP

Sealdah GRP

SRP SEALDAH

DSRP SADAR

I/C SEALDAH GRPS

Phase II Phase II

30/12/2008

3

WBP

Siliguri GRP

SRP SILIGURI

DSRP SILIGURI GRP

IRP ALIPURDWAR GRP

O/C ALIPURDWAR JUNCTION GRPS

Phase II

WBP

Siliguri GRP

SRP SILIGURI

DSRP SILIGURI GRP

IRP ALIPURDWAR GRP

O/C NEW COOCHBEHAR GRPS

Phase II

WBP

Siliguri GRP

SRP SILIGURI

DSRP SILIGURI GRP

IRP ALIPURDWAR GRP

O/C NEW MAINAGURI GRPS

Phase II

WBP

Siliguri GRP

SRP SILIGURI

DSRP SILIGURI GRP

IRP SILIGURI GRP

O/C BALURGHAT GRPS

Phase II

W Siliguri SRP DSRP IRP O/C DALKOLA Phase II



CIPA Details


Phase

Installation

date

No of PC

BP GRP SILIGURI SILIGURI GRP

SILIGURI GRP

GRPS

WBP

Siliguri GRP

SRP SILIGURI

DSRP SILIGURI GRP

IRP SILIGURI GRP

O/C NEW MAL JUNCTION GRPS

Phase II

WBP

Siliguri GRP

SRP SILIGURI

DSRP SILIGURI GRP

IRP SILIGURI GRP

O/C SILIGURI (T) JUNCTION GRPS

Phase II

WBP

Siliguri GRP

SRP SILIGURI

DSRP SILIGURI GRP

I/C MALDA TOWN GRPS

Phase II Phase II

24/11/2009

3

WBP

Siliguri GRP

SRP SILIGURI

DSRP SILIGURI GRP

I/C NEW JALPAIGURI GRPS

Phase II Phase II

27/11/2009

3



List of Other Police Offices and Other Agencies in West Bengal:

Other Police Offices and Other Agencies Number of Units

Finger Print Bureau, CID, WB 1

Forensic Scientific Lab (FSL), Government of WB 1

Police Control room, WBP 1

Police Control room, KP 1

Total 4



Annexure: Police Stations with Power/Connectivity Issues

80 PS in West Bengal will have Solar Power backup. The Solar power system will be provided by the

Government of India. Providing solar power system is not part of the Scope of Work of this assignment.

In these 80 PS, SI doesn’t require to supply Generator. List of these 80 PS will be provided in due course

of time.



Annexure: Indicative Physical Layout of a Police Station

Index:

Item Code Item Name

T2 Duplex Laser Printer

T3 PC with Table

T4 Multi Function Laser

T5 16 Port Switch

T6 Fingerprint Reader

T7 Digital Camera

T8 Electronic Pen

2KVA

Generator

T3 T3 T3

T2

20 feet

25 feet

UPS T5

T4

T6

T7

T8



Annexure: Detailed Process flows for Functions Performed in Police

Stations

Overall Process Flow Diagram From the list of above functions, the AS IS data capture processes for the key activities like Case Investigation, Charge Sheet filing etc. has been provided below which is general and common to the different kinds of specific services performed at the police station level.



Activity Name Process Flow Process Output

Case Investigation

Case Diary with preliminary investigation information

Scenario 1 Scenario 2 Chargesheet/FRT

IO has the authority to access

the Case Diary at any time

Petition from Court

(Magistrate) to SP (‘Court

Complaint Case’ under 156(3)

SP Assigns the case to the

OC

Need to track the state of case

movement after assignment to the PS

In special cases

e.g. narcotics,

DSP acts as IO

CID cases go through PS.

Exception is CBI,

considered a PS under

Special Establishment Act

PS sends all FIR copies

(1 each to SP Office, CI

Office and Court)




Charge sheet filing

Special Report if filing is rejected

Rejected by

SP

Recorded in Special

Report with comment

SP Directs IO to

file charge sheet IO Resumes

Investigation

Suspect

Acquitted




Assignment & Handling of Special Report Cases (SR-Case)

Special Report Cases (SR-Case)

Criteria for classifying a case as SR-

Case varies across districts; even a

petty case may be treated as SR-

Case based on sensitivity of issue

The Crime Staff in SP’s

office holds the designation

of ‘Reader to SP’

There is always a provision

to Re-Open an SR-Case at

anytime

May ask to file a Charge sheet or

to collect more evidence after

this




Crime Conference

Mobilization to solve critical issues/cases

Direction for the law enforcement team going forward

Conducted at SDPO/SP Office,

this conference involves an

oversight of both Cognizable and

Non Cognizable Offences



Process Flow Diagrams for specific services The process flow diagrams for the specific services are provided below as:

Complaints

Received at the

Police Station

Y

N

Y

The details are

entered in the

General Diary

Whether Cognizable

offence or not?FIR is lodged

Actionable case or not

Further Enquiry

Non FIR

Generation

Issuance of GD

receipt

Complainant goes

to court

Issuance of court

order

N

Investigation

Process

Process Flow: Complaints/ information to the concerned Police Station

Receipt of Court

Order at PS

An officer is

assigned for

Enquiry Process

Enquiry Process

and Preparation of

Enquiry Report

The detailed

enquiry report is

sent to court



Enquiry about the

status of the

complaint

Details are provided

by the I/O to the

complainant

I/O provides the

copy of FIR to the

complainant

If charge sheet is

filed, charge sheet /

final report no., date,

section is provided to

the complainant

verbally

A letter is issued to

the complainant

informing the fate of

the case

Process Flow: Status of the complaint or case registered at Police Station



Request/letter for

the copy of the

post mortem

report to the S.P in

T.R Form

Approval by the S.P

and sent to the

police station

One copy of the P.M

report attested by the

O/C or I/O is sent to

the concerned party

Process Flow: Copies of FIRs, post‐mortem reports and other permissible documents etc

Request/letter for

the copy of the

FIR

A copy of FIR report

is given to the

concerned party

free of cost

Request/letter for

the copy of the GD

A receipt of GD with

GD No. (GD copy

cannot be provided

to the concerned

party

Concerned party

requests to

P.S(O.C) for

conducting

event(s)

Details are

forwarded to S.D.O

through CI

Permission if

granted post

approval by S.D.O

Process Flow: Submission of requests for issue of clearances for events and functions

The SDO can

further forward and

delegate the power

of approval to

SDPO



Details of the

missing person is

entered in the G.D

Details of the

missing person is

updated in missing

person register

I/O provides the form

in which the details of

the missing person

along with photograph

to the complainant

Is it a case of kidnap FIR is lodgedInvestigation

Process

The details of the

person is sent to the

different districts

(DCRBs)

DCRB further sends

this information to

the respective PS

under the district

The concerned party

advertises the details

of the missing

person in media

If the missing person

is recovered/found

the GD is updated

The entry for the

missing person is

cancelled in the

missing person

register

N

Y

The informant

redirected to the

CID’s missing

persons squad and

Lalbazar missing

persons squad

Process Flow: Details of missing/ kidnapped persons

If a girl below 15 years is missing, the

specific case is to be registered under

section 366 (A)



Details of the

unidentified dead

body is entered in

the G.D

Details of the

unidentified dead body is

entered in UD case

register

A copy of Surat Hal

and UD case

challan is sent to

Hospital for P.M

report

Issuance of P.M

report by hospital

and sent back to

P.S

Preparation of case

diary and detailed

investigation process

If the case ends in

final report, it goes to

zonal DSP for it’s

approval

I/O prepares Surat Hal

report and UD case

challan and

investigates the case

One copy of details

of the UD register

and complaint is sent

to SDO Court

The relevant documents

are attached with the

specific case of the case

diary

The details are sent to

the court for trial processIs it a cognizable offence

Process Flow: Unidentified Deadbodies

If the case is charge

sheeted it would

follow the same

investigation process

as mentioned earlier

A case to be

registered and FIR to

be lodged (if injuries

are marked on the

body, FIR is to be

lodged immediately)



Details of the

stolen vehicle are

entered in the G.D

Details of the stolen

vehicle are entered

in the FIR

Investigation

Process

Preparation of case

diary

If recovered, all the

details are entered in

seizure list, general

diary, Case Diary

and property register

Seizure list is sent to

the court for further

actions

A petition to the

court is lodged by

the complainant for

release of the

vehicle

I/O reports regarding

the petition of the

petitioner

Issuance of court

order for the release

of the vehicle with a

Jimma bond to the

concerned party

Issuance of receipt

voucher of the I/O.

Release of the

vehicle to the

concerned party

Details of the release

is entered into the

property register and

GD, CD

Process Flow: Missing or Stolen Vehicles

A message is drafted and sent

providing all the numbers

specific to the vehicle such as

(chassis no, license no. etc.) to

SCRB, CID, Lalbazar and all

bordering police stations

Vehicle is recovered or

not?

Y

If not recovered, the

case ends in

preparation of final

report

N

The case may get reopened

if further information is

obtained regarding the

matter and the investigation

process starts



Details are

entered in the G.D

Details are entered

in the FIR

Details of the arms

recovered entered

in Malkhana

register

Examination of Arms

Expert and

preparation of the

examination report

A letter in form of a

prayer for sanction

order is prepared

The sanctioned

order is sent to the

district magistrate for

approval of the

charge sheet

Post approval of the

charge sheet, a

charge sheet is

generated

After receipt of the

exam report and

other artifacts, PP

opinion of the

concerned court is

taken

Process Flow: Details of Arms

Stolen / recovered

Recovered

Message to be sent with all

details such as particulars of

the stolen arms and the

numbers to SCRB, CID, DD,

Lalbazar and all other

concerned units

Stolen

Gun license of the

owner is seized

Investigation

Process as

msnetoiednearlier



Details are

entered in the G.D

Petition to the

District Magistrate

for gun license in a

specified format

District Magistrate

sends the details

to SP

SP further forwards

this information to

the concerned police

station

A report is prepared

by the S.I based on

the findings and

sends it to S.P

The S.P sends it to

the DM for approval

of the award of

license

Approval/rejection of

license by the DM

An S.I is appointed

for enquiry of the

case

Process Flow: Submission of requests for issue of Gun Licenses



Concerned party

issues a letter to

S.P requesting for

NOC

The same

information

forwarded to O.C

Enquiry about the

person on whose name

NOC needs to be

issued by an SI

Final report / NOC to

the concerned party

Process Flow: Submission of requests for issue of character certificates and NOC



Petition raised by

citizen to the

Passport Office

Request routed to

ASP

Petition routed to

DIB

DIO is endorsed

DIO Investigates

Report sent to DIB

Routed to ASP

Decision

forwarded to

Passport Office

Process Flow: Passport Verification



Citizen approach police for

Servant Verification

Police Approaches the employing

agency for servant’s background

Gathers information and records

details in the ‘Servant Register’

along with photographs of the

servant

Reports the outcome to the

enquiring party

Process Flow: Servant Verification



Annexure: Indicative Hardware Bill of Material

Number of PCs required for PS

Particulars Number of PS Number of PCs/ Unit Number of PC’s to be installed

No. of NON CIPA PS 349 4 1396

Number of PS covered under CIPA Phase I

47 4 188

Number of PCs required for higher offices

Higher Office Name No. of Units Number of PCs/ Unit Number of PC’s to be installed

(a) (b) (a)*(b)

Circles/IRPs 97 3 291

Sub Divisions 54 3 162

Ranges 7 4 28

Zones 3 4 12

SCRB 1 4 4

Commissionerates 0 25 0

Districts 29 10 290

Police Head Quarters 2 50 100

Number of PCs required for Other Police Offices

Particulars Number of PS Number of PCs/ Unit Number of PC’s to be installed

Number of Other Police Offices/ Other Agencies

4 2 8



Hardware Required for Non CIPA PS:

Component Name PS No. of Units / PS Total No. of Units

(a) (b) (a)*(b)

HDD 160GB 349 1 349

Duplex Laser Printer 349 1 349

Multi‐Function Laser (Print /Scan /Copy)

349 1 349

UPS for 120 min backup 349 1 349

24‐Port Managed Switch 349 1 349

Fingerprint Reader 349 1 349

Digital Camera 349 1 349

Electronic Pen 349 1 349

Hardware Required for PS covered under CIPA Phase I:


(a) (b) (a)*(b)

HDD 160GB 47 1 47

Duplex Laser Printer 47

1 47


47

1

47

UPS for 120 min backup 47

1 47


Fingerprint Reader 47

1 47





Hardware Required PS covered under CIPA Phase- II:


(a) (b) (a)*(b)

HDD 160GB 90 1 90



1 90



2KVA Generator Set

** Generator Set not required for 80 PS where Solar Power back up system to be provided by Government of India. So number of Generator Set to be procured is 406.



Hardware Requirement at Higher Offices:

Circles / IRPs Sub – Division Range Zone

Component Name

Circles / IRPs

No. of Units / Circle

Total No. of Units

Sub - Division

No. of Units / Sub -

Division

Total No. of Units

Range No. of Units / Range

Total No. of Units

Zone No. of Units / Zone

Total No. of Units

(a) (b) (a)*(b) ( c) (d) ( c)*(d) (e) (f) (e)*(f) (g) (h) (g)*(h)

HDD 160GB 97 0 0 54 0 0 7 0 0 3 0 0

Duplex Laser Printer

97 0 0 54 0 0 7 0 0 3 0 0

Multi‐Function Laser (Print /Scan / Copy)

97 1 97 54 1 54 7 1 7 3 1 3

UPS for 120 min backup

97 1 97 54 1 54 7 1 7 3 1 3

2KVA Generator Set

97 0 0 54 0 0 7 0 0 3 0 0

24‐Port Managed Switch

97 1 97 54 1 54 7 1 7 3 1 3

Fingerprint Reader

97 0 0 54 0 0 7 0 0 3 0 0

Digital Camera 97 0 0 54 0 0 7 0 0 3 0 0

Electronic Pen 97 0 0 54 0 0 7 0 0 3 0 0



SCRB Commissionerates Districts Police Head Quarters

Component Name

SCRB

No. of

Units /

SCRB

Total No. of

Units

Commissionerates

No. of Units / Commissionerat

e

Total No. of

Units

Districts

No. of Units / Distric

t

Total No. of Units

Police Head

Quarters

No. of

Units / HQ

Total No. of Units

(i) (j) (i)*(j

) (k) (l)

(k)*(l)

(m) (n) (m)*(n

) (o) (p)

(o)*(p)

HDD 160GB 1 0 0 0 0 0 29 0 0 2 0

Duplex Laser Printer

1 0 0 0 0 0 29 0 0 2 0

Multi‐Function Laser (Print /Scan / Copy)

1 1 1 0 25 0 29 10 290 2 50 100

UPS for 120 min backup

1 1 1 0 0 0 29 4 116 2 20 40

2KVA Generator Set

1 0 0 0 0 0 29 0 0 2 0 0

24‐Port Managed Switch

1 1 1 0 0 0 29 2 58 2 5 10

Fingerprint Reader

1 0 0 0 0 0 29 0 0 2 0 0

Digital Camera

1 0 0 0 0 0 29 0 0 2 0 0

Electronic Pen 1 0 0 0 0 0 29 0 0 2 0 0



Hardware Requirement at Other Police Offices/ Other Agencies:

Component Name Number of Other Police Office No. of Units / PS Total No. of Units

(a) (b) (a)*(b)

HDD 160GB 4 0 0

Duplex Laser Printer 4

0 0


4

1 4

UPS for 120 min backup 4

1 4

2KVA Generator Set 4 0 0



0 0



Hardware for DC and DR

Specifications

Locations

DC DR

Database Server 2 1

Application Server for BI 2 1

Application Server for Portal 2 1

Application Server for Document Management System 2 1

* Web Server

* Directory & Access Server

Communication & Mail Server 2 1

SAN Storage 1 1

SAN Switch 1 1

Tape Library 1 Back Up Software at DC 1 Core Router 1 1

Core Switch 1 1

Server Load Balancer 1

* Bidders can propose virtualization for Infrastructure servers (e.g. Web Server, Directory & Access

Server, Antivirus, Backup, DNS etc.), keeping minimum 2 numbers of physical servers in DC and

minimum 1 number in DR.

Networking Hardware Details: In addition to the Networking Hardware as mentioned above; racks for

switches need to be supplied for all of the following units:

Type of unit Number of Unit

PS 486

Other Police Offices/ Other Agencies 4

Circles / IRPs 97

Sub – Division 54

Range 7

Zone 3

SCRB 1

District 29

HQ 2

DC & DR 2



Annexure: Indicative Technical Specifications for CCTNS Solution

Components

Minimum Technical Specifications Requirement at State Data Center & Disaster Recovery Site 1. Enterprise Management and Monitoring Solution (EMS) Basic Requirements

Solution should be inclusive with hardware, OS, patches, etc.

Solution should provide for future scalability of the whole system without major architectural changes.

Should be SNMP v1, v2, v3 and MIB-II compliant.

Filtering of events should be possible, with advance sort option based on components, type of message, time etc.

Should support Web / Administration Interface.

Should provide compatibility to standard RDBMS.

Solution should be open, distributed, and scalable and open to third party integration.

Should provide fault and performance management for multi-vendor TCP/IP networks.

Security

Should be able to provide secured windows based consoles / secured web - based consoles for accessibility to EMS.

Should have web browser interface with user name and Password Authentication

Administrator/ Manager should have privilege to create/modify/delete user.

Polling Cycle

Support discriminated polling

Should be able to update device configuration changes such as re-indexing of ports Fault Management

Should be able to get fault information in real time and present the same in alarm window with description, affected component, time stamp etc.

Should be able to get fault information from heterogeneous devices — routers, switches, servers etc.

Event related to servers should go to a common enterprise event console where a set of automated tasks can be defined based on the policy.

Should have ability to correlate events across the entire infrastructure components of DC/DR

Should support automatic event correlation in order to reduce events occurring in DC/DR

Should support advanced filtering to eliminate extraneous data / alarms in Web browser and GUI



Should be configurable to suppress events for key systems/devices that are down for routine maintenance or planned outage.

Should be able to monitor on user-defined thresholds for warning/ critical states and escalate events to event console of enterprise management system.

Should provide out of the box root cause analysis with multiple root cause algorithms inbuilt for root cause analysis

Should have self-certification capabilities so that it can easily add support for new traps and automatically generate alarms

Should provide sufficient reports pertaining to asset and change management, alarms and availability of critical network resources as well as network response times for critical links.

The tool shall integrate network, server and database performance information and alarms in a single console and provide a unified reporting interface for network and system components. The current performance state of the entire network and system infrastructure shall be visible in an integrated console.

Should provide an integrated performance view for all the managed systems and networks along with the various threshold violations alarms in them. It should be possible to drill-down into the performance view to execute context specific reports

Should provide the following reports for troubleshooting, diagnosis, analysis and resolution purposes: Trend Reports, At-A-Glance Reports, & capacity prediction reports

Should be able to auto-calculate resource utilization baselines for the entire managed systems and networks and allow user to set corresponding upper and lower threshold limits

Discovery

Should provide accurate discovery of layer 3 and heterogeneous layer 2 switched networks for Ethernet, LAN and Servers etc.

Manual discovery can be done for identified network segment, single or multiple devices.

Presentation

Should be able to discover links with proper colour status propagation for complete network visualization

Should support dynamic object collections and auto discovery. The topology of the entire Network should be available in a single map.

Should give user option to create his /or her map based on certain group of devices or region.

Should provide custom visual mapping of L2 and L3 devices connectivity and relationships. Agents

Should monitor various operating system parameters such as processors, memory, files, processes, file systems etc. where applicable using agents on the servers to be monitored.

Provide performance threshold configuration for all the agents to be done from a central GUI based console that provide a common look and feel across various platforms in the enterprise. These agents could then dynamically reconfigure them to use these threshold profiles they receive.

System Monitoring



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

Windows OS

o Should monitor / manage following:

Event log monitoring Virtual and physical memory statistics Paging and swap statistics Operating system Memory Logical disk Physical disk Process Processor Paging file IP statistics ICMP statistics Network interface traffic Cache Active Directory Services

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

o Unix / Linux

o Should monitor with statistics :

CPU Utilization, CPU Load Averages System virtual memory (includes swapping and paging) Disk Usage No. of Nodes in each file system Network interface traffic Critical System log integration

Infrastructure Services

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

End to end Management of applications (J2EE/.NET based)



Determination of the root cause of performance issues whether inside the Java application in connected back-end systems or at the network layer.

Automatic discovery and monitoring of the web application environment

Ability to monitor applications with a dashboard

Ability to expose performance of individual SQL statements within problem transactions

Monitoring of third-party applications without any source code change requirements

Proactive monitoring of all end user transactions; detecting failed transactions; gathering evidence necessary for problem diagnose.

Storage of historical data is for problem diagnosis, trend analysis etc.

Monitoring of application performance based on transaction type

Ability to identify the potential cause of memory leaks. Reporting

Should able to generate reports on predefined / customized hours

Should be able to present the reports through web and also generate “pdf” / CSV / reports of the same.

Should provide user flexibility to create his /or her custom reports on the basis of time duration, group of elements, custom elements etc.

Should provide information regarding interface utilization and error statistics for physical and logical links

Should create historical performance and trend analysis for capacity planning

Should be capable to send the reports through e-mail to pre-defined user with pre-defined interval

Should have capability to exclude the planned-downtimes or downtime outside SLA

Should be able to generate all sorts of SLA Reports.

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.

Should be able to generate the reports for Server, Application, infrastructure services and Network devices in DC/DR environment.

Availability Reports

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

Trend Report

Custom report

MTBF and MTTR reports Performance Reports

Device Performance – CPU and Memory utilized

Interface errors

Server and Infrastructure service statistics

Trend report based on Historical Information

Custom report

SLA Reporting

Computation of SLA for entire DC/DR Infrastructure

Automated Daily, Weekly, Monthly, Quarterly and Yearly SLA reports



Data collection

For reporting, required RDBMS to be provided with all licenses

Should have sufficient Storage capacity should to support all reporting data for 5 Years of DC/DR operation.

Integration

Should be able to receive and process SNMP traps from infrastructure components such as router, switch, servers etc.

Should be able integrate with Helpdesk system for incidents.

Should be able to send e-mail or Mobile –SMS to pre-defined users for predefined faults

Should trigger automated actions based on incoming events / traps. These actions can be automated scripts/batch files.

Network Management

The Network Management function must monitor performance across heterogeneous networks from one end of the enterprise to the other.

It should proactively analyze problems to improve network performance.

The Network Management function should create a graphical display of all discovered resources.

The Network Management function should have extensive reporting facility, providing the ability to format and present data in a graphical and tabular display

The Network Management function should collect and analyze the data. Once collected, it should automatically store data gathered by the NMS system in a database. This enterprise-wide data should be easily accessed from a central location and used to help with capacity planning, reporting and analysis.

The Network Management function should also provide information on performance of Ethernet segments, including capacity utilization and error statistics for the segment, WAN links and routers.

Alerts should be shown on the Event Management map when thresholds are exceeded and should subsequently be able to inform Network Operations Center (NOC) and notify concerned authority using different methods such as pagers, emails, etc.

It should be able to automatically generate a notification in the event of a link failure to ensure proper handling of link related issues.

The Systems and Distributed Monitoring (Operating Systems) of EMS should be able to monitor: o Processors: Each processor in the system should be monitored for CPU utilization.

Current utilization should be compared against user-specified warning and critical thresholds.

o File Systems: Each file system should be monitored for the amount of file system space used, which is compared to user-defined warning and critical thresholds.

o Log Files: Logs should be monitored to detect faults in the operating system, the communication subsystem and in applications. The function should also analyze the files residing on the host for specified string patterns.

o System Processes: The System Management function should provide real-time collection of data from all system processes. This should identify whether or not an important process has stopped unexpectedly. Critical processes should be automatically restarted using the System Management function.



o Memory: The System Management function should monitor memory utilization and available swap space.

o Event Log: User-defined events in the security, system, and application event logs must be monitored.

SLA Monitoring

The SLA Monitoring function of the EMS is by far the most important requirement of the DC/DR Project. The SLA Monitoring component of EMS will have to possess the following capabilities:

o EMS should integrate with the application software component of portal software that measures performance of system against the following SLA parameters:

Response times of Portal;

Uptime of data center;

Meantime for restoration of Data Centre etc.;

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.

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.

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.

o The SLA monitoring component of the EMS should be subject to random third party audit to vouchsafe its accuracy, reliability and integrity.

Reporting

The Reporting and Analysis tool should provide a ready-to-use view into the wealth of data gathered by Management system and service management tools. It should consolidate data from all the relevant modules and transform it into easily accessible business-relevant information. This information, should be presented in a variety of graphical formats can be viewed interactively

The tool should allow customers to explore the real-time data in a variety of methods and patterns and then produce reports to analyze the associated business and service affecting issues.

The presentation of reports should be in an easy to analyze graphical form enabling the administrator to put up easily summarized reports to the management for quick action (Customizable Reports). The software should be capable of supporting the needs to custom make some of the reports as per the needs of the organization.

Provide Historical Data Analysis: The software should be able to provide a time snapshot of the required information as well as the period analysis of the same in order to help in projecting the demand for bandwidth in the future.

ITIL based Helpdesk System

Helpdesk system would automatically generate the incident tickets and log the call. Such calls are forwarded to the desired system support personnel deputed by the Implementation Agency. These personnel would look into the problem, diagnose and isolate such faults and resolve the



issues timely. The helpdesk system would be having necessary workflow for transparent, smoother and cordial DC/DR support framework.

The Helpdesk system should provide flexibility of logging incident manually via windows GUI and web interface.

The web interface console of the incident tracking system would allow viewing, updating and closing of incident tickets.

The trouble-ticket should be generated for each complaint and given to asset owner immediately as well as part of email.

Helpdesk system should allow detailed multiple levels/tiers of categorization on the type of security incident being logged.

It should provide classification to differentiate the criticality of the security incident via the priority levels, severity levels and impact levels.

It should allow SLA to be associated with a ticket based on priority, severity, incident type, requestor, asset, location or group individually as well as collectively.

It should maintain the SLA for each item/service. The system should be able to generate report on the SLA violation or regular SLA compliance levels.

It should be possible to sort requests based on how close are the requests to violate their defined SLA’s.

It should support multiple time zones and work shifts for SLA & automatic ticket assignment.

It should allow the helpdesk administrator to define escalation policy, with multiple levels & notification, through easy to use window GUI / console.

System should provide a knowledge base to store history of useful incident resolution.

It should have an updateable knowledge base for technical analysis and further help end-users to search solutions for previously solved issues.

The web-based knowledge tool would allow users to access his / her knowledge article for quick references.

It should provide functionality to add / remove a knowledge base solution based on prior approval from the concerned authorities

Provide seamless integration to generate events/incident automatically from NMS / EMS.

Each incident could be able to associate multiple activity logs entries manually or automatically events / incidents from other security tools or EMS / NMS.

Allow categorization on the type of incident being logged.

Provide audit logs and reports to track the updating of each incident ticket.

Proposed incident tracking system would be ITIL compliant.

It should be possible to do any customizations or policy updates in flash with zero or very minimal coding or down time.

It should integrate with Enterprise Management System event management and support automatic problem registration, based on predefined policies.

It should be able to log and escalate user interactions and requests.

It should support tracking of SLA (service level agreements) for call requests within the help desk through service types.

It should be capable of assigning call requests to technical staff manually as well as automatically based on predefined rules, and should support notification and escalation over email, web etc.

It should provide status of registered calls to end-users over email and through web.



The solution should provide web based administration so that the same can be performed from anywhere.

It should have a customized Management Dashboard for senior executives with live reports from helpdesk database.

There should be a documented escalation management mechanism.

Online technical support and telephone support should be available during working hours.

There should be a maximum of 4 hours response turnaround time on complaints.

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

2. Server Load Balancer

10/100/1000Mbps Ethernet Ports – minimum 4 ports upgradeable to 6 ports

Memory: Minimum 4 GB upgradeable to 8 GB

Minimum of 2 Gbps throughput scalable to 4 Gbps

Minimum of 1 Gbps SSL throughput

Minimum of 4000 SSL connections scalable to 10000 SSL connections

Security features should be as per standard practice.

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

Input Global Load Balancing

HTTP Header Super Farm



URL-Based SLB

SLB should support below Management options o Secure Web Based Management o SSH o TELNET o SNMP v1, 2, 3 Based GUI o Command Line

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

Directory, etc…) Blade Enclosure

Blade Chassis:

o Solution to house the required number of blade servers in smallest number of enclosures,

occupying a max of 10U rack height per enclosure

o Same enclosure should support Intel Xeon, AMD Opteron and RISC/EPIC blades. Enclosure

should also support UNIX, Linux and Windows Operating environment.

o Should have Hot Pluggable & Redundant Management Modules.

o Should provide a highly reliable and high performance redundant active mid-plane or

passive back-plane design in the blade enclosure. Should provide detailed technical

information.

o Should be able to accommodate the blade servers mentioned in the sections below in the

proposed blade enclosures.

o Support simultaneous remote access for different servers in the enclosure.

LAN Interconnect

o Two or Four network ports from each of the servers in the enclosure should be available on

1 Gigabit LAN switch / Link Aggregation Module / Pass-through to connect to external

network devices.

Fibre Channel Interconnects

o Redundant minimum 4Gbps Fibre Channel Pass thru Interconnect modules to direct HBA

cards to SAN Switch/Storage.

MAC Address & WWN Management:

o Blade Enclosure should preferably support management & deployment of MAC Addresses of

NIC Adapters and WWN No of FC adapters at the chassis level so that replacement of a

server blade does not involve Network & SAN configuration effort at the blade level

Power Supply:

o The enclosure should be populated fully with power supplies of the highest capacity &

energy efficiency available with the vendor. Power supplies should support N+N as well as

N+1 redundancy configuration, where N is greater than 1. Guaranteeing complete

availability even on failure of any 2 power supplies across the enclosure

Cooling:



o Each blade enclosure should have a cooling subsystem consisting of redundant hot

pluggable fans or blowers enabled with technologies for improved power consumption and

acoustics

System Software

o Management/controlling software have to be from the same OEM

Remote Management

o Must provide a remote management functionality to operate the server in both in-band and

out-of-band. Must be part of the server without the need to install any additional hardware

or software

o Must have Real-time Virtual KVM functionality and be able to perform a remote Power

sequence. Must provide both Java & Java-free browsing options.

Power Management:

o Must be able to show the actual power usage and actual thermal measurement data of the

servers.

Database Server

Processor: Latest Generation x86-64 Bit Minimum 2*8- Core Processor with Minimum 1.86Ghz Clock Speed and 12MB Cache or higher

Number of Processors: Offered Server should be scalable to 4 (Four) Processors

Memory: 64 GB DDR3 Memory Per Server

Memory Scalability: Memory Should be Scalable up to 256 GB

Network Interface Ports: Minimum 2 * 10 GbE Ports

FC-HBA Ports: 2 * 4 Gb/s FC-HBA Ports

Internal RAID: Internal RAID Controller should be able to do RAID 1,0

Internal HDD: Minimum 4 * 50GB Internal SSD/ Minimum 2 *300GB Internal SAS SFF Hot Plug HDD

OS & Virtualization Infrastructure Support: MS Windows, RHEL, SLES, Oracle Solaris, VMware Sphere & Microsoft Hyper

Form Factor: Blade

Application Server

Processor: Latest Generation x86-64 Bit Minimum 2*8-Core Processor with Minimum 1.86Ghz Clock Speed and 12MB Cache or higher



Memory capability: Memory Should be Scalable up to 256GB


FC-HBA Ports: 2 * 4Gb/s FC-HBA Ports


Internal HDD: Minimum 4 * 50GB Internal SSD/ Minimum 2 *300GB Internal SAS SFF Hot Plug HDD

Pre-Failure Warranty: Critical Components like CPU, Memory & HDD should be covered under Pre-Failure Warranty



OS & Virtualization Infrastructure Support: MS Windows, RHEL, SLES, Oracle Solaris, VMware Sphere & Microsoft HyperV /CentOS 5

Form Factor: Blade

Mail Server

Processor: Latest Generation x86-64 Bit Minimum 2*4CoreProcessor with Minimum 2.53 GHz Clock Speed and 12MB Cache or higher



Memory Scalability: Memory Should be Scalable up to 128 GB

PCI-Express Slots: Server Should Have Minimum 2 * PCI Express Slots


FC-HBA Ports: Minimum 2 * 4Gb/s FC-HBA Ports


Internal HDD: Minimum 2 * 300GB Internal SAS SFF Hot Plug HDD

Pre-Failure Warranty: Critical Components like CPU, Memory & HDD should be covered under Pre-Failure Warranty

OS & Virtualization Infrastructure Support: MS Windows, RHEL, SLES, Oracle Solaris, VMware Sphere & Microsoft Hyper

Form Factor: Blade

Infrastructure Servers (Backup, DNS, Antivirus, etc…)

Processor: Latest Generation x86-64 Bit Minimum 4-Core Processor with Minimum 1.86Ghz Clock Speed and 18MB Cache or higher

Number of Processors: Offered Server should be configured/ populated with 8 (Eight) Processors

Memory: Minimum 128 GB DDR3 Memory Per Server

Memory Scalability: Memory Should be Scalable Minimum up to 2 Terabytes within the existing enclosure

PCI-Express Slots: Server Should Have Minimum 12 * PCI Express Slots

Network Interface Ports: Minimum 12 * 1GbE Ethernet Ports per Server. Minimum 1 * 10/100 Mb/s Port for Server Management

FC-HBA Ports: Minimum 6 * 8Gb/s FC HBA Ports / Server

Internal RAID: Internal RAID Controller with minimum 512MB battery Backed Write Cache

Internal HDD: Minimum 8 * 300GB Internal SAS SFF Hot Plug HDD Per Server

DVD: Internal DVD-RW

Power Supplies: Redundant Hot-Swappable Power Supplies Configured in N+N Mode

Fans: Redundant Hot Swappable Fans (optional)

Pre-Failure Warranty: Critical Components like CPU, Memory and HDD should be covered under Pre-Failure Warranty

OS & Virtualization Infrastructure Support: MS Windows, RHEL, SLES, Oracle Solaris, VMware VSphere & Microsoft HyperV

Form Factor: Rack-Mount

4. Storage and Backup Solution



SAN Switches – 2 nos.

Minimum 16 Active ports (each with minimum port speed 8 Gbps) within same switch upgradeable to 32 ports or higher with fiber channel connectivity.

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

Should have capability of ISL trunking of minimum 8 ports.

Should support multiple OS.

Non-disruptive subsystem maintenance.

Should have dual Fans and Hot plug power supplies switching

Should have web based management software for administration and configuration.

Non-disruptive microcode / firmware upgrades and hot code activation.

Switch shall support in built diagnostics, power on self test, command level diagnostics, online and offline diagnostics.

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

Should support Secure Shell (SSH) encryption to provide additional security for Telnet sessions to the switch.

Should support multilevel security on console access prevent unauthorized users from altering the switch configuration

Should support Fiber Channel trace route and Fiber Channel Ping for ease of troubleshooting and fault isolation

Should support the following diagnostics: o Online Diagnostics o Internal Loopbacks o FC Debug (Optional) 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

Note: Fiber channel connectivity to be considered wherever FC port has been mentioned. Storage Area Network – 1 no

Controllers: The proposed SAN array shall be configured with dual Active-Active controllers for redundancy with dedicated cache mirroring interface between controllers

Front-End & Back- End Ports: The proposed SAN array shall be configured with Minimum speed of 4 Gbps for both 8 number of frontend ports and 8 number of backend ports spread across dual controllers.



Cache & Cache backup: The proposed SAN array shall be configured with at least 8 GB scalable to 16 GB, across dual controllers. Cache shall be mirrored between the controllers. Entire cache should be available for a single LUN.

Offered Capacity: The proposed SAN array shall be configured with minimum 10 TB post RAID, using 450 GB 15k rpm dual ported FC drives in RAID 5.

Maximum Usable Capacity: The storage system should be scalable up to minimum 30 TB of usable capacity using fibre channel disk drives. The maximum capacity is considered using maximum 30 spindles per device (back end) port in the same ratio of disks as currently proposed

Disk IOPS: o The array should be capable to deliver at least 10000 disk IOPS. o Bidder should enclose OEM certification for the given performance for proposed

configuration and public document for the required performance scalability

RAID Levels: The Proposed SAN Array should support RAID Levels 1 or 10, 5 and 6

Replication Solution: The Storage Solution should be provided for a 2- Site DR Architecture where Primary & DR should Replicate Asynchronously. All necessary hardware and software licenses to be provided by SI.

Snapshots & Volume Clones: Offered Storage must include snapshots &volume clones licenses Note: For estimating data size the System Integrator should make use of the following information:

Number of cases in WB in last 10 years

Number of Police stations

IIF forms provided with this document

Database size of existing applications

Tape Library - 1

Drive Type: LTO5

Minimum No of Drives: 4

Drive Scalability: Up to 16 drives

No of Slots: Minimum 100

Slot Scalability: Up to 400 slots

Power Supplies: Redundant Power Supplies

User Interface: Touch Screen Graphical Interface

Cartridges: 100 LTO5 barcode labeled cartridges & 10 cleaning cartridges from the tape library OEM

Note: Backup/ Restore operation is not required to be performed at DR site when DC is operational. Backup Software

The proposed Backup Solution should be available on various OS platforms such as Windows and UNIX platforms and be capable of supporting SAN based backup / restore from various platforms including UNIX, Linux, and Windows etc.

Centralized, web-based administration with a single view of all back up servers within the enterprise. Single console must be able to manage de-duplicated and traditional backups.

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

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



The proposed backup Solution supports the capability to write multiple data streams to a single tape device or multiple tape devices in parallel from multiple clients to leverage the throughput of the Drives using Multiplexing technology.

The proposed backup solution support de-multiplexing of data cartridge to another set of cartridge for selective set of data for faster restores operation to client/servers

The proposed backup solution should be capable of taking back up of SAN environment as well as LAN based backup.

The proposed backup solution shall be offered with required numbers of UNIX based licenses, Windows based licenses and LINUX based licenses for both SAN based backup and the LAN based backup as per the specification provided for 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, and Sybase / DB2 etc. on various OS.

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

The Proposed backup solution shall be designed in such a fashion so that every client / server in a SAN can share the robotic tape library.

Backup Solution shall be able to copy data across firewall.

The backup software must also be capable of reorganizing the data onto tapes within the library by migrating data from one set of tapes into another, so that the space available is utilized to the maximum. The software must be capable of setting this utilization threshold for tapes

The backup software should be able to support versioning and should be applicable to individual backed up object’s

Should have the ability to retroactively update changes to data management policies that will then be applied to the data that is already being backed up or archived

Note: All software licenses should be in favor of the SCRB, WB and should be a perpetual license, i.e. the software license should not expire after the contract period. The software Licenses should be comprehensive and no further licenses should be required for DC/DR operations. The software installed should necessarily be the latest version at the time of actual implementation. FC-IP Router

2 nos. FC-IP router could be separate or can be an integrated module in SAN switch

Fiber Channel Ports o min 2 FC ports scalable to 4 FC ports

FC Port Speed

o Autosensing 1/2/4 Gb/s



iSCSI (Ethernet) Ports o min 2 Ethernet ports, scalable to 4 Ethernet ports

iSCSI (Ethernet) Port Speed

o 1 Gigabit Ethernet

Aggregate Bandwidth o min 125 MB/s

Protocol Support

o FCP o iSCSI

High-Availability Features

o Two-way active/active clustering with failover and failback capabilities o Multiple iSCSI connections provide multi-pathing support from a single gateway to as

many as 100 servers. Management Features

o CLI (by Telnet, SSH, or console) iSCSI Gateway Manager

o SNMP o Allows for monitoring traffic statistics on each storage and network interface, fan and

temperature and iSCSI session details. 5. Desktops

Processor: Intel Core i5-650 / i5-750 processor Or AMD Phenom X4 950 (3.20 GHz) Processor with Q57/785G Chipset or higher , RAM 4 GB

Motherboard & Chipset: OEM Motherboard

Video: Integrated Graphic controller

Network: Integrated 10/100/1000 Gigabit Ethernet controller

Ports: 1x fast serial port, 4x USB 2.0 ports (2 ports on front ), 1xKeyboard port, 1xMouse port

HDD Controller: Integrated dual port SATA-II controller

Memory: 4GB DDR III or higher

Storage: 250GB sata II HDD 7200 RPM

Optical Drive: 22X DVD writer or higher

Monitor: 18.5” TFT or more (4:3 aspect ratio) LCD Monitor 1280 x 1024 resolution with 5 ms or lower response time, TCO 05 certified

Keyboard: English 107 or more Keys mechanical Keyboard which should also have layout and support for Bengali.

Mouse: USB Optical Scroll Mouse with antistatic mouse pad resolution of Optical 1000 cpi, Complying to CE and FCC norms

Out Of Band Management: System should support out-of-band management

Power Management & DMI: System with Power management features & Desktop Management Interface implementation



System Chassis: Small Form Factor System chassis with suitable power supply having active power factor correction feature to sustain full load. Small dimension and low power consumption as per current standard while considering the heat dissipation into account.

OS Support & Certification: Windows XP/7 / Linux /Centos 5.5

Preloaded Software: Above configuration preloaded with OS (Latest Version) with Office Suite as per the course contents recommended by NCRB, Antivirus with all necessary Plug-ins/ utilities and driver software including bundled in DVD Media

6. 160 GB External Hard Disk

Capacity: Minimum 160 GB

Connectivity: Hi-speed USB2.0

Operating System Supported: Windows XP/Windows Vista /Windows7/ /Linux Red hat /Ubuntu

Accessories: Drive should be supplied with cables, necessary driver and software, Base stand and attachable feet.

7. Laser Jet Network Printer (Duplex)

Print speed, black - Up to 26 ppm

Print resolution, black - Up to 600 x 600 x 2 dpi

Print technology - Laser

Monthly duty cycle - Up to 8000 pages

Memory, standard - 32 MB

Print languages, standard - Host-based printing, PCL 5e

Duplex printing (printing on both sides of paper) - Automatic (standard)

Media sizes, standard - Letter, legal, executive, postcards, envelopes (No. 10, Monarch)

Media sizes, custom - 250-sheet input tray: 5.8 x 8.27 to 8.5 x 14 in; priority feed slot: 3 x 5 to 8.5 x 14 in

Media types - Paper (laser, plain, photo, rough, vellum), envelopes, labels, cardstock, transparencies, postcards

Accessories included - USB cable, Driver CD, Utility software, Cat5/6 UTP patch cable

Network ready - Standard (built-in Ethernet)

Power consumption - <=450 watts

Power Consumption (Standby) - <=8 watts

Operating temperature range - 63.5 to 77º F

ENERGY STAR® Qualified - Yes

8. Laser Multifunction Device (Print, Copy, Scan)

Print speed, black - Up to 18 ppm

Print resolution, black - Up to 600 x 600 dpi

Print technology - Laser

Monthly duty cycle - Up to 8000 pages

Memory, standard - 64 MB

Print languages, standard - Host-based printing, PCL 5e

Duplex printing (printing on both sides of paper) - Manual (driver support)



Media sizes, standard - Letter, legal, executive, postcards, envelopes (No. 10, Monarch)

Media sizes, custom – Minimum 150-sheet input tray: 5.8 x 8.27 to 8.5 x 14 in; priority feed slot: 3 x 5 to 8.5 x 14 in

Media types - Paper (laser, plain, photo, rough, vellum), envelopes, labels, cardstock, transparencies, postcards

Scanner type - Flatbed, ADF

Scan resolution, optical - Up to 1200 dpi

Scan size - 8.5 x 11.7 in

Scan speed - Up to 6ppm

Supported file formats - PDF; TIF; BMP; GIF; JPG

Copy resolution - Up to 600x 400 dpi

Maximum number of copies - Up to 99 copies

Accessories included - USB cable , Driver CD ,Utility software , UTP patch cable & One printing cartridge

Connectivity - Hi-Speed USB 2.0 port; 10/100Base-T Ethernet network port

Network ready - Standard (built-in Ethernet)

Power consumption - <=450 watts

Power Consumption (Standby) - <=2.2 watts

Operating temperature: 50 to 90F

ENERGY STAR® Qualified: Yes

9. On-Line Ups (2KVA) Single Phase Input & Single Phase Output

Capacity: 2KVA

Battery Backup: Minimum 120minutes

General o Inverter Technology: Pulse Width Modulation (PWM) using IGBTs, double conversion o Switching frequency: 20 KHz or higher o Total Harmonic Distortion (THD) Voltage: < 2% for 100% linear load < 3% for 100% non-

linear load o Noise level: Less than 55 dB o Operating Temperature: 0º- 50º C o Output Wave Form: Pure sine wave o Cooling: Air Cooled

Input o Voltage Range: 160 V AC to 280 V AC o Frequency range: 50 ± 6% Hz o D/G set comp ability: Required o Input Power Factor: 0.9 or better at full output load leading to Unity with power factor

correction (PFC)

Output o Voltage: 230V AC +1 %, single phase o Regulation: Less than + 1% in the following conditions



a. No load to full load/Full load to no load b. 0.6 lag to Unity PF c. During Entire Backup time. d. Complete Input Voltage Range

o Frequency: 50 Hz + 0.5 %

Efficiency o Overall Efficiency: 80 % or better on rated full load of 0.8 PF & 230V, 50Hz AC output o Inverter Efficiency: 90% or better on rated full load of 0.8 PF & 230V, 50Hz AC output

Overload Capacity: 110% for 2 min. & 125% overload for 30sec.

Load Power Factor: 0.8 lagging

Protection Required for: Short Circuits / Over Loading/ Over Temperature / Input low/ high voltage control/DC low/high voltage trip

Battery Make: Complying with JIS C 8702 test. Battery recharge time (after complete discharge to 100% charge) & charge rating: Battery recharge time should not exceed 8 hours and charger should be capable to charge battery on C10 rating.

Battery Capacity: o Capacity of UPS: 2KVA o D.C.Bus Voltage: <192 V o Battery Bank for Back-up Time: 120minutes o UPS & Battery Housing: Powder coated UPS & battery cabinet with caster wheel should be

of minimum 1mm thick good quality material and should be free from sharp edge, scratches, nicks, & burs etc. Enclosure should conform to protection requirement of IP2L1 to IS13947 (Part 1)/1993 (reaffirmed 2004).

L.C.D. meter: To measure and monitor input voltage, output voltage, output current, DC current, DC voltage, input / output frequency

Indications: Mains on/ Load on Battery/Inverter/ Battery level/ Load level/ Inverter over load

Audible Alarm: Over Temperature / Main failure/Battery low/ Inverter Overload

Switches: Main ON/OFF MCB/ Battery ON/OFF MCB/ Inverter push button with reset.

Output Connection: O/P Terminals of standard quality should be provided. 03 Nos. of 5/15A/230V female ISI/ IEC Mark socket and all 3 sockets should

Isolation Transformer: Galvanic Isolation through Transformer Note -More than two battery banks should not be used in Parallel in the configuration. 10. Generators 2 KVA



CAPACITY: 2KVA

ENGINE: o COOLING SYSTEM REQD.: Air cooled, Water/Coolant cooled o Rated Current: AC 3.0 A/ AC 7.1A o Ignition system: Transistor Controlled Ignition (TCI) o Fuel Tank Capacity (Diesel/kerosene run): minimum 2.7 L o Fuel Tank Capacity (Petrol starting): minimum 0.25 L o Continuous running hours: 4 Hours o Frequency (Hz): 50 Hz o Rated Output (VA): 350 VA o Maximum Output (VA): 450 VA o Silent type: Yes

11. Fingerprint scanner

Sensor Type: Optoelectronic

Prism Architecture: Dual Prism

Size of window: 18mm x 22mm minimum

Glass thickness: 25mm

Resolution: 512 PPI upgradable

Image grey scale: 256 level Dynamic

Scanning time: 0.01Sec.

Distortion rate: 0.1%

Computer interface: USB2.0, USB Powered

Operating temperature: 0 – 55 Degree C

Environmental humidity: Up to 90%

Optical /Film Coating: Hygroscopic

Operating system Support: Window XP / Vista / 7 / Linux 12. Digital Camera

Pixels (Min.): 12 megapixels or higher

Display Size: 2.7 inches or higher

Recording Media: SD memory card/ SDHC memory Card/SDXC memory card/ Multimedia Card

Recording Format: JPEG & RAW

Optical Zoom: 3X or higher

ISO Sensitivity Setting: Auto 80 – 1600 (Minimum)

Auto Focus Range: Approx (W)=3 cm to infinity, Approx (T)= 80 cm to infinity

White Balance: Auto / Daylight / Cloudy / Fluorescent / Incandescent / Flash

Flash Function: Auto/ Red Eye Reduction/Off

USB Connectivity: Yes (Hi- Speed) )/USB 2.0 or higher

Battery Backup: Atleast 120 Min / 200 shots or above

Operating system Support: Window XP / Vista / 7/ Linux

13. Electronic Pen



Data communication: USB 1.1 standard (also supports USB 2.G standard), Bluetooth 1.2 standard

Built-in battery: Rechargeable battery

Continuous writing time: 2 hours or longer Standby time:1 hours (min.) without a cap

Charging time: Approx. 2 hours (from 0 to100% charge)

Charging method: Dox cradle or USB adapter

Operating system Support: Window XP / Vista / 7/ Linux

Digital Pad Size: (Approx) 336mm * (Approx) 245 mm

Pad Writing Area: Minimum A4 size

Notepad Holder: (Approx) 210mm* (Approx) 300 mm

Built-in Memory: 32 MB or more

Memory Slot: Secure Digital

Pen Size: Minimum 125mm * 10 mm (diameter)

Digital Page File: DHW, DND 14. Computer Tables Computer Table Size: L 910 x W 610 x H 728 mm

Top: Size 910 x 610 mm made of 18 mm thick pre laminated medium density fiber (MDF) board ISI Marked (IS: 14587-1998). The top shall be firmly screwed on 25x25x1 mm square tube frame.

Upper side of laminated board shall be in natural teak shade while the bottom side shall be white/cream shade.

Sliding key Board tray: A Sliding key Board tray shall be made of 18mm pre laminated medium density fiber board of size 725x450 mm. The gap between top and tray shall be 100mm.

Sufficient top and bottom racks space to accommodate CPU, UPS and Printers o Table top should have one wire manager for wires control. Table top, keyboard and

storage shelf should be made of 19 mm pre-laminated MDF Board of premium brands.

All furniture must be branded and of good quality from reputed manufacturers with ISI marking.

15. Computer Chairs Computer Chair with Handle

Seat size shall be 430x430 mm on 10 mm thick molded comm. ply with 60 mm thick 40 density molded PU foam Back rest size shall be 400x300 mm on 10 mm thick molded comm. ply with 40 mm thick 32 density molded PU foam covered with tapestry.

The height of back rest shall be 900x500 mm for top and bottom edges respectively. The black rest shall be provided with lifting arrangement on flat iron & helical spring.

Two nos. suitable PU handles shall be provided.

The base stand should be made up of 5 prongs duly pressed welded together centrally with apedestal bush with good quality twin wheel castors. The stand and other metal parts excluding central spindle shall be powder coated. Complete steel structure shall be pretreated and powder coated with minimum thickness of 60 microns coating.



A central spindle of 25mm dia rod without threads shall be provided with revolving arrangements. The adjustable height of chair shall be from 530 to 570 mm. A good quality tapestry cloth shall be provided on seat & back in attractive colour/ shade.

All furniture must be branded and of good quality from reputed manufacturers with ISI marking. 16. Electrical Cabling

Scope: Supply, install, testing, commissioning and maintenance of electrical cabling for supplying power to run installed devices.

Skilled Manpower: Electrical Cabling shall be laid by skilled and experienced workmen using adequate equipment to minimize stretching of the cable.

Cable Terminations: All terminations should be carried out according to the manufacturer‘s instructions and guidelines and standards of generic cabling systems. When terminating outlets, care must be taken for safety.

Testing & Documentation: Testing of each node should be done as per manufacturer standards and the final report should be submitted.

Specifications: Total 8 Electrical Points Including 3 Switches & 3 Sockets in Each Point, (2 No. 5-Amps and 1 No. 15 Amps.) - Point wiring using ISI approved PVC Conduit / Casing Capping, 1.1 KV grade 2.5 Square meter FRLS Cu flexible wire including supply of wire, switch, socket and GI Box. Including all necessary hardware & accessories complete, material and labor as per requirement of the MP Police. For point wiring having Average Point length is12 to 18 Meters.

UPS & Generator Set Cabling: Electrical Cabling for Network Rack, Four Computer Points, separate cabling for Two Printers from main input and Generator set to UPS Including change-over, MCB and all other accessories as per requirement.

17. Pit Earth Earth resistance measured must be less than 2 Ohm.

G.I. Pipe of 60 mm diameter with a sole plate to be laid vertically down inside the ground to depth of 3.5 meter. To the G.I. Pipe four copper plates are fitted at the bottom inside the earth. The Copper plate is of One-meter Square. G.I. Pipe is fitted to Copper plates by means of brass bolts & nuts of 9.4 mm X 50 mm and with spring Washers & Plate washer. The trench is fitted with fine ash to a height of One meter, then Salt to a height of One meter, followed by Saw Dust to a height of One meter.

Thus the G.I. Pipe is buried inside, to a depth of three meters & only 0.5 meter is kept above ground level. From this portion connection is made to equipment Earth Strip as desired.

Copper plate .5-meter square 3 mm thick, sole plate 60 Sq. mm, 6 mm thick GI wire-to-wire earthing system connection should be made with compression connectors or otherwise weld connection.

Copper Plate Earthing

300mm x 300mm x 4mm Thick Copper Plate (Not less than 95% copper purity): 15 Kg (1 in No)



25mm x 3mm Thick Copper Strip (Not less than 95% copper purity): 12 ft./ 6 Kg

Charcoal: 200 Kg

Salt: 40 Kg

(150 x 100 x 6mm Thick Terminal Plate Copper: 2 Nos (0.900 Kg) each

Sundries such as Brass, Nut bolts, Porcelain, Insulator, Thimbles, I/Tape etc.: As per requirement

40mm Dia B-Class GI Pipe for watering & Strip protection.: 10 ft.

Supply of Soft Soil (Optional): 4 Cu.Mts. 18. Wall Mounted Network 9U Rack

Size: 19” Wall mount ,9 U height

Body: Minimum Powder quoted steel Body with front door of glass. Completely covered & have security locks.

Accessories: Proper ventilated with One Fan, One Cable Manager, Power Distribution Unit of 6 No. (5 and 5 Amp) Sockets with surge protection, Mounting Accessories,

Earthing: Fitted with Copper Strip for earthing the Equipment 19. Cat-6 Patch Panel

Type: 24 port patch panel as per requirement, Unshielded Twisted Pair, Category 6, ANSI/TIA/EIA 568- B.2.1

Circuit identification Scheme: Port Labeling for port identification on each of 24-ports

Port Identification: Labels on each of 24/48-ports (to be included in supply),

Height: 1U

Category: Category 6

Modular Jack: 750 mating cycles 20. Core Router

A. Architecture

The architecture should be based on high performance CPU with convergence of routing, switching, voice and security.

The Router should be a single box configuration and should be modular, so that there is flexibility to use the appropriate choice of interfaces as and when required.

Should have at least 6 slots. Each WAN card slot should support a variety of interfaces like V.35 Syc Serial (2 Mbps), E1, Channelized E1 , ISDN BRI/PRI, E3, Channelized E3, STM-1 etc.

Should support Voice Interfaces like FXO, FXS (Internal/ external)

Should have either support for Voice Modules (internal/ external), and High Performance VPN Encryption modules

Forwarding capability should be at least 1400 Kbps using 64-byte packet size with QOS enabled.

Should have USB 2.0 ports for storing OS images

The Router shall have at least 1GB DRAM and 256 MB Flash

Router should have at least 150 Mbps of encryption throughput and support for 1500 tunnels from Day-1.



Router should support on-line software reconfiguration to implement changes without rebooting.

Router should have internal Redundant Power Supply for High availability.

B. Interface Requirements

3 x Gigabit Ethernet Interface

1 nos. of Channelized STM-1 interface (Bidders may consider adding a Gigabit interface instead of Channelized STM-1 interface)

8x V.35 interface

C. Software

The router shall support following WAN protocols: PPP as per RFC 1661, Multilink PPP, ISDN, Frame Relay etc.

The Router shall support following IP routing protocols: RIP Version 1 & 2, Triggered RIP support as per RFC 2091 to support demand circuit, OSPF Version 2 as per RFC 1583, BGP 4, and IS-IS. Multicast Routing support through PIM.

Support for NAT as per RFC 1631, Port Address Translation support.

IEEE 802.1Q based VLAN tagging

D. Security

Access lists based on Network Address, Mask, Protocol Type and Socket Type;

MD 5 Route Authentication as RFC 1321, Controlled SNMP Access through the use of SNMP V.2 with MD5 Authentication.

Multiple Privilege levels to provide different level of access.

Remote Authentication Dial in user service (RADIUS) as per RFC 2138

VPN Support - To Support IP Security (IPSec), AES], 3DES, DES and MPLS

VPN Encryption - Equipped for Hardware Accelerated Encryption with 280 Mbps performance.

Support for Web VPN (SSL VPN) on the router internal or external

Router shall support Network Management through: SNMP, RMON support, Software Upgrade through FTP or TFTP; TELNET. The Router should also have integrated Web Interface (GUI) for ease of configuration.

E. Protocols

The Router should be MPLS (Multiprotocol Label Switching) Ready with the following MPLS Features:

MPLS Diff-Serv-Aware Traffic Engineering (DSTE)

MPLS Label Distribution Protocol (LDP/RSVP)

MPLS QoS - DiffServ Tunnel Mode Support,

MPLS Traffic Engineering (TE) – Automatic bandwidth adjustment for TE tunnels

The Router should be IPv6 (IP version 6) Ready from day 1.

Secure Services Management - To Support SSHv2 and SNMPv3 protocols to encrypt the management session.



F. High Availability

Power Redundancy - Equipped with internal Redundant Power Supply.

USB Flash Memory - To Support USB Flash memory for ease of image recovery

Online insertion and removal - Should support online insertion and removal

G. Multimedia and QoS support

A class-based scheduling/queuing mechanism that provides configurable minimum bandwidth allocation to each class

Should support Congestion Management mechanisms such as Priority Queuing, Custom Queuing, Weighted Fair Queuing etc.

Should support Congestion Avoidance mechanisms such as RED / WRED

RSVP: Resource Reservation Protocol (RSVP) as per RFC 2205

Should support Policy-based Routing

IGMPv2, v3: Internet Group Management Protocol Version 2 & 3

Multicast routing support such as Protocol Independent Multicast (PIM) - Sparse Mode and Dense Mode.

Integrated Web-based device-management tool embedded in the router; and should be accessed remotely for faster and easier deployment of routers for both WAN access and security features.

21. CAT 6 Cable Lying

Cable Laying: All the cabling shall run through PVC conduit / Casing Capping of suitable size of ISI standard.

Skilled Manpower: Cables shall be laid by skilled and experienced workmen using adequate equipment to minimize stretching of the cable.

Cable Terminations: All terminations should be carried out according to the manufacturer‘s instructions and guidelines and standards of generic cabling systems. When terminating outlets, care must be taken to avoid damaging the copper cores when stripping back the outer sheathing.

Testing & Documentation: Testing of each node should be done as per manufacturer standards and the final report should be submitted.

UTP COMPONENTS: The system should Meet or exceed TIA/EIA 568 B-2 specifications of Category-6 as a system. All performance parameters -Attenuation, Pair -to-Pair and power sum NEXT, Pair And Power sum ELFEXT, Return Loss and Delay skew should be tested for 100m Channel as well as 90m permanent Link. It should be a single OEM solution and should ensure optimum system performance. There should not be any Impedance mismatch problems among components of the cabling system. The complete system should be tested up to 600 MHz for all the test parameters to ensure the end-to-end system performance.

22. CAT 6 Patch Cord (1 Meter / 2 Meters)

Length: 1Meter /3 Meter

Conductor: 24 AWG 7 / 32, stranded copper

Cable Type: UTP CAT 6 ANSI/TIA/EIA 568-B.2.1



Plug Protection: Matching colour boot to maintain bend radius

Category: Category 6

Terminals: Phosphor Bronze with gold plating

Jacket: PVC 23. Global Positioning System The Global Positioning System (GPS) is a space-based global navigation satellite system that provides reliable location and time information in all weather and at all times and anywhere on or near the Earth, when and where there is an unobstructed line of sight to four or more GPS satellites. It is freely accessible by anyone with a GPS receiver. The GPS generally consists of three segments: the space segment, the control segment, and the user segment:

The Space Segment consists of a nominal constellation of 24 operating satellites that transmit one-way signals that give the current GPS satellite position and time.

The Control Segment consists of worldwide monitor and control stations that maintain the satellites in their proper orbits through occasional command maneuvers, and adjust the satellite clocks. It tracks the GPS satellites, uploads updated navigational data, and maintains health and status of the satellite constellation.

The User Segment consists of the GPS receiver equipment, which receives the signals from the GPS satellites and uses the transmitted information to calculate the user’s three dimensional position and time./ No/

Partial) Functional Features

The GPS should monitor the location of patrol cars and police officers using GPS. This is particularly helpful when sending help to officers in need of assistance.

The GPS should be able to help track and recover stolen cars. Rather than giving chase, such a stolen vehicle should be tracked by law enforcement officials over a long distance so that apprehension of the thief can be made once the car reaches its destination.

The GPS should allow police officers to know their own location by utilizing its video map directories, inside patrol cars and other law enforcement vehicles. This can help decrease response times to emergencies.

The GPS should be able to quickly transmit via satellite the fingerprints, license numbers and images of wanted individuals.

The GPS should have the feature of placing GPS bracelets on paroled criminals to monitor their movements.

It should be possible to equip vehicles with GPS along with other equipments as bait in law enforcement operations. The GPS should be installable in the construction machinery and even computers to aid in sting operations.

Functional Specifications (GPS Tracking)

The GPS should monitor the location of patrol cars and police officers using GPS. This is particularly helpful when sending help to officers in need of assistance.



Instant Update: The GPS should allow seeing where a moving vehicle is at any time (location, speed and heading)

Tracking: The GPS should track each short" stop and go – that is each time the vehicle stops moving for three or more minutes (e.g. parked with engine running) as well as the next time it continues driving. With respect to Tracking another important feature the GPS should have is to know when a vehicle stops and the engine is turned off and for how long as well as the distance and driving time between stops including information about location (street address)date and time, etc.”

Trip Routes: The GPS should be able to view the path a vehicle is driving (or drove) from one place to another.

Street Addressing: The GPS should be able to receive reports from vehicles regarding their approximate street address, in addition to precise longitude and latitude.

Landmarks: The GPS should be able to see vehicle positions with reference to Landmarks as it is useful for knowing where vehicles are (or have been) in relation to locations, such as police stations, criminal and/or unauthorized areas.

Get directions for drivers: The GPS should be able to guide a lost driver in the right direction.

Google Maps: When viewing vehicles' current location or historical activity, the GPS should allow choosing between four high-quality map views: Standard, Satellite, Hybrid and Terrain.

Quick Zoom: The GPS should instantly zoom-in to a vehicle's location while keeping sight of your others vehicles.

Speeding Alert: The GPS should be able to report a speeding alert to Vehicles when they exceed a certain speed limit (which should be changeable).

Tow Alert: The GPS should be able to report when a Vehicle moves while the ignition is off (possible theft by tow truck).

Excessive Idling: The vehicle should be able report the GPS when it idles for too long.

Instant Notify: The GPS should have the feature to get up-to-the minute updates on whatever vehicle activity that is important. With instant notification, you can choose to be automatically notified via email or text message when certain activity occurs— for example, if and when a vehicle is operated off-hours, leaves a job site, speeds excessively, or idles too much.

Instant Messaging: The GPS should have the feature to send information— such as addresses, work orders, driving directions— quickly and easily from the web to the driver's cell phone. The driver should also be able to reply to that message from the GPS.

Functional Specifications (GPS Bracelet)

The GPS should support GPRS/SMS communication

The GPS should be able to perform standard real time tracking by: Unit ID, location, speed, direction, time, alarm status.

The GPS should be able to automatically generate timely reports or reports upon command.

The GPS should be able to perform voice monitoring.

The GPS should have an SOS button to send out the exact location for immediate rescue/action.

If the wrist tracker exists in the GPS, then it should be able to report the position under ordered-frequency and work in interval-based saving power mode.

The GPS should have a Geo-fence alarm, and should be able to setup geo-fence areas in case of lost.

The GPS should have a speed limit alarm

The GPS should support mobile phone tracking & web based GPRS tracking solutions.



24. UTM Firewall with VPN & IPS

The firewall should be an hardware appliance based unit

UTM Firewall with Unrestricted users

The unit should have minimum 1 GB or higher memory

Firewall stateful throughput should be more than 5 GBPS

Gateway Antivirus throughput should be more than 1 GBPS

IPS throughput should be more than 2 GBPS

VPN throughput should be more than 2 GBPS

Unified Threat Management throughput should be more than 1 GBPS

UTM should support minimum 20000 new Connections per second

UTM should support more than 1500 site-to-site VPN Tunnels and more than 5000 VPN Client, Should be supplied with minimum 2000 bundled VPN Clients

UTM Should support Active/Passive with State Synch and Active/Active UTM in HA Mode

The UTM should have 8 Copper Gigabit Network Interface Ports, 1 Console Interface, 2 USB ports

Should have LED’s indicating Status (Power, Test, Alarm) LAN (Link, Activity) WAN (Link, Activity) DMZ (Link, Activity)

Unit should have minimum 16 Core Processor with specialized security processing

It should not consist of any failure devices such as Hard Disk

Should have additional Cryptographic Accelerator Processor offloading VPN computation from Main Processor

Should have a Multi-Layered Protection Technology

Should have upgradeable Firmware

Should Have a Re-Assembly Free Deep Packet Inspection or equivalent feature

Should have a stateful throughput of 1 Gbps or higher Bi-directional for Firewall

Gateway Antivirus should be able to scan the 50+ Protocols including HTTP, FTP,SMTP, POP3 and IMAP,

Should support the following and Standard protocols TCP/IP, UDP, ICMP, HTTP, HTTPS, IPSec, ISAKMP/IKE, SNMP, DHCP, PPPoE, L2TP, PPTP, RADIUS

Should have an integrated Intrusion Prevention System

Should be able to Scan encrypted traffic and payload for any virus threats

Should be able to provide Content Filtering services without the use of other software with more than 8 million site categorized

Should support routing functionality like RIP and OSFP

Should be able to add policy based routes on the appliance

Should have no file size limitation for GAV/IPS scanning

Should support Site-to-Site Auto Provisioning VPN

Should support IKEv2 Secondary Gateway, IKEv2 Dynamic Client Support

Should have Application Firewall for application Bandwidth Control, Access Control, Regulation of web traffic, email, email attachments and file transfers, scanning of files and documents for keywords and specified content, creation of custom IDS/IPS signatures

Should support Single Sign-On for user authentication



Should Inbound Load Balancing for redundancy or load balancing for multiple server applications or devices

Should support HTTPS Content Filtering

Should support SSL Control for policies to control the establishment of SSL connections

Should support Services Dashboard for global and local statistics of blocked network threats

Should support Packet Capture to capture and examine the contents of individual data packets that traverse the firewall appliance for troubleshooting, diagnostics and general network activity, decreasing the time it take to investigate potential issues

Should support Hardware Failover with State sync

Should support Network Address Translation (NAT) over Virtual Private Network (VPN)

Should support Clean Virtual Private Network (VPN) technology

Should support 25000+ signature in the Gateway Antivirus (GAV)

Should support Network Antivirus (NAV) from the hardware appliance

Should support Address Resolution Protocol (ARP) binding functionality

Should support Zone Security

Should support object Based Management

Should support SPAM blocking

Should support VOIP protocol both SIP and H.323

Should support policy based Network Address Translation (NAT)

Should support WAN to WAN failover

Should support Internet Service Provider (ISP) failover

Should support Load Balancing in Round Robin and in accordance with Bandwidth & percentage

Should support Hardware Failover / High Availability

Should have Console based and Browser based management facility.

The data transfer between the Management station and Firewall appliance should be encrypted.

The appliance would be IPv6 Ready

Should support firewall modes like Nat mode, Bridge mode and transparent mode

Should be able to log any traffic and activity on the unit

Should be able to divert Logs on to log server and third party software integration should be possible.

Should be able to generate reports with statistic such as User login, IP address, Intrusion, URL, Virus attacks etc.

25. RJ-45 RJ-45 : 10BASE-T, 100BASE-TX, AND 1000BASE-T

26. 24 Port 10/100/1000 and 2 Fibre Uplinks Managed Switch

OEM Make - Top 5 in IDC /Gartner reports (quarter ending December ’10 or March ‘11) in terms of market share of units sold

24 10/100/1000 Base-TX Ethernet ports and extra 2 nos 1000Base-SX/LX (shared or combo) All ports can auto-negotiate between 10Mbps /100Mbps/ 1000Mbps, half-duplex or full duplex

and flow control for half-duplex ports. Support 8K MAC address. 32 Gbps or more switching fabric capacity



Packet Forwarding Rate should be 35.0 Mpps The switch must support Port Mirroring, Port Trunking and 802.3ad LACP Link Aggregation port

trunks to allow creation of Ethernet channeling with other devices Support IEEE 802.3x flow control for full-duplex mode ports. Support 802.1D Spanning Tree Protocol (STP), 802.1S, 802.1w, Rate Limiting, 802.1Q VLAN

encapsulation, Up to 255 VLANs per switch and up to 4000 VLAN Ids Support IGMP v1, v2 and v3 snooping 802.1p Priority Queues, port mirroring, DiffServ Support based on 802.1p priority bits with at least 8 queues DHCP support & DHCP snooping /relay/optional 82/server support

Shaped Round Robin (SRR) or WRR scheduling support

Support for Strict priority queuing Support for IPv6 ready features with dual stack

Access control

Support port security Support 802.1x (Port based network access control). Support for MAC filtering. Should support TACACS+ and RADIUS authentication

VLAN

Support 802.1Q Tagged VLAN and port based VLANs and Private VLAN The switch must support dynamic VLAN Registration or equivalent

Protocol and Traffic

Network Time Protocol or equivalent Simple Network Time Protocol support Switch should support traffic segmentation Traffic classification should be based on user-definable application types: TOS, DSCP, Port based,

TCP/UDP port number Management

Switch needs to have RS-232 console port for management via a console terminal or PC Must have support SNMP v1, v2 and v3. Should support 4 Groups of RMON Should have accessibility using Telnet, SSH, Console access, easier software upgrade through

network using TFTP etc. Configuration management through CLI, GUI based software utility and using web interface

Annexure: Indicative Network Architecture Details

The Networking solution of CCTNS project shall be based on a Hybrid Model which will consist of State

Wide Area Network (SWAN) operated by State under SWAN scheme and Data network operated by

Bharat Sanchar Nigam Limited (BSNL) which consists of Point to point leased lines, VPNoBB, WiMax,

VSAT and MPLS technologies. BSNL shall be providing the Networking & Connectivity services along with

Operations & Maintenance for all the locations implemented by BSNL in the State of West Bengal. BSNL

shall also provide connectivity on MPLS VPN network for aggregated bandwidth at the SDC (State Data

Center) for the locations connected on VPNoBB, WiMax and VSAT network and also provide connectivity

for SDCs (State Data Centre) at Police Headquarters (PHQs) to the National Data Centre (NDC) of NCRB.

Further BSNL shall provide MPLS VPN network for connecting SDC and Disaster Recovery Centre (DRC)

for the State of West Bengal. The DRC location need to be finalized by the States and the SDCs of other

States/UTs may be mutually considered as DRCs of each other.

Proposed Network Architecture by Department of IT

Connectivity Modes for Implementation of CCTNS in West Bengal

CCTNS system evolves about transporting the data collected at Police Stations and various

field offices spread across the state to the Central server system to be located at the West

Bengal Government State Data Centre in Kolkata. After processing and archiving, the criminal

data Base will be accessed by the various Police establishment in the state as well as by the

NCRB.

The Data connectivity is hence, one of the primary components for the project. Following are the

different connectivity modes which may be deployed for implementation of CCTNS system:

MODE I

WBSWAN (West Bengal State Wide Area Network), the State Government’s networking

backbone which currently connects all District, Sub division and Block Head Quarters in the

state is proposed to be the primary connectivity vehicle. Individual Police Stations and the

various offices of the Police establishments are going to be connected to the nearest POP of

WBSWAN so that Data can be transported to the WBSDC via the WBSWAN State HQ POP

located in Kolkata over the secure terrestrial Leased Circuits of WBSWAN.

The local connectivity between the Police Establishment and respective WBSWAN is proposed

to be over WAN, implemented over BSNL Leased circuits. Depending on the geographic terrain,

distance and availability, the alternate mode of connectivity like wireless connectivity may also

be used. Establishments located proximal to the WBSWAN POPs, LAN connectivity may be

used.

MODE II

In certain locations where WBSWAN connectivity is not feasible, the connectivity is planned

over VPN over broadband. In this mode individual remote Police establishment would be

connected over Internet broadband feed. The data would be sent over the Internet cloud. The

WBSDC will be provided with a fixed IP Internet connectivity. For adequate Data Security, the

data movement between the remote location and the WBSDC located server/ Storage systems

is planned over a secure VPN connection. Adequate security scheme like encryption, antivirus

etc as well as other steps against various internet related threats should be planned with

deployment of devices like UTM or equivalent.

MODE III

The connectivity scheme must have to fall back on BSNL MPLS backbone or VSAT

connectivity, in the event either of the options described above is not feasible. The MPLS

backbone of BSNL may be employed for connectivity to NCRB in New Delhi. If MPLS

Page | 228


connectivity is desired, a local lead drop will have to be provided to the WBSDC with

appropriate terminal equipment.

MODE IV

In some remote Police Station connectivity via VSAT may have to be resorted to. As the number

of VSAT station is expected to be limited it is suggested that the common facility like the Earth

station etc offered by VSAT service provider like BSNL etc may be utilized. In such a scenario a

suitable backhaul connection from the service provider Earth station need to be arranged up to

the WBSDC. If VSAT facility is used, suitable security features at either end need to be

established.

If all the above options for connectivity are to be employed to realize the Composite Hybrid

Network, the SI will have to provide a suitable terminal networking arrangement at the WBSDC

end. This should employ the necessary Security infrastructure also. For the nodes connected

using the WBSWAN backbone, the connectivity up to the WBSDC may be realized using the

inherent infrastructure already built at the WBSWAN SHQ POP and WBSDC. Only individual

connectivity needs to be implemented.

Summarizing, the above four solutions:

Mode I – WBSWAN connectivity is the most recommended solution wherever the distance from

WBSWAN POP is within feasible range. As it is the captive network for the Government of West

Bengal implemented over dedicated terrestrial leased circuits, end to end data security is

assured. Connection to WBSDC already exists at the SHQ (State Head Quarter) of WBSWAN.

With a marginal cost voice and video facilities may also be extended over this network.

Mode II – VPN over broadband: this is a cost effective solution using internet as the connectivity

vehicle. However, additional security has to be built in to the solution at both the remote as well

as at the central .to ensure data privacy and security.

Mode III – It is BSNL’s network, to be used for redundancy .NCRB at Delhi may be connected

over this backbone.

Mode IV- Connectivity option using VSAT may be required where the terrestrial leased circuits

as well as broadband are not feasible. Here also the security features are to be taken into

consideration.

Page | 229


Connectivity criteria for terminating into WBSDC

The proposed connectivity will be treated as the dedicated service for CCTNS in which only the

Power, cooling and BMS facility will be extended from WBSDC. Hence all required terminal

equipment for creating independent NOC like firewall, router, switches etc are to be provided to

WBSDC.

Guideline for lateral connected nodes to ride on WBSWAN

Physical Layer

All connectivity will normally be terminated on the serial port of the WBSWAN router

However for connectivity using medium other than terrestrial leased circuit ( e.g. Wimax / Wifi/ VSAT ) as a special case may be terminated on the managed switch

As different class of routers are provided at individual class of POPs, the serial port interface requirements are different. Bidders are to study the following table and provide for the required equipment Suitable and matching Networking equipment to be designed for the Police station and corresponding local BSNL exchange end:

Class of

POP

Type of

Router

Interface for lateral

connections

Interface Equipment required at

WBSWAN POP end ( to be

provided by end user)

A State HQ Cisco 7609 STM1 interface

directly to Router

The 2Mbps incomers are

multiplexed at the local BSNL

exchange and fed into the STM1’s

composite channel. Hence no

interface equipment is additionally

required at the SHQ end. SI to

coordinate with BSNL and

WBSWAN team for suitable channel

allocation

B District HQ Cisco 7206 STM1/ CP8/ CP16

interface is provided

through suitable CPE

by BSNL. Channels

are De Multiplexed

and fed with

individual G.703

interface to the serial

cards of the DHQ

router

The 2Mbps incomers are

multiplexed at the local BSNL

exchange and subsequently demux-

ed at DHQ end. Hence no interface

equipment is additionally required

at the DHQ end. SI to coordinate

with BSNL and WBSWAN team for

suitable channel allocation

C Sub Cisco 3845 Interface provided on

the router is V.35

In 30 out of 44 SDHQ BSNL has

provided G.703 interface If the links

Page | 230


All interface equipment along with necessary cables required at the POP will have to be provided and maintained by the end customer or his nominated SI. WBSWAN operator/ implementing agency will be responsible only for the interface port configuration and its continued functioning.

Power supply for the interface equipment like modem, radio etc may be provided from the conditioned power supply of the WBSWAN POP. However a prior approval will have to be obtained to ensure that the interface equipment to be used are adequately protected so that the WBSWAN equipment are not damaged due these – e.g for wireless outdoor equipment, supply must be adequately protected with proper earthing and surge suppressors/ protectors

Modem / Interface Converters supplied should meet the following spec

1. All interfaces of the modems used should have valid TEC GR approval

2. The modem should have built in surge protection compliant to ITU-T, K-20/K-21 Standards

3. The Modem/ converter manufacturer should have valid ISO 9000 : 2008

4. Complies with EMI/EMC specification CISPR 22 ( 1993) for Class B equipment (for Modems only)

The SI will be required to liaison with BSNL for line provisioning and testing whenever needed (During initial commissioning as well as day to day running) .Similarly SI will have to arrange for manpower for testing during installation and breakdown maintenance.

In the event the Police station and other offices, to be integrated through WBSWAN, are with in distance feasible for LAN connectivity (through Cat6/ OFC/ Wireless Links) the

Division HQ serial port are to be terminated on such SDHQ

the bidder need to provide G.703

to V.35 Interface Converters at

SDHQ end

In balance 14 SDHQ the connection

is through conventional Leased

Circuit .The bidder has to provide 1

pair of V.35/G.703 Leased line

modem

(Detailed list will be provided during

integration)

D Block HQ Cisco 2811 Interface provided on

the router is V.35

serial port

In BHQ the connection is through

conventional Leased Circuit .The

bidder has to provide 1 pair of

V.35/G.703 Leased line modem to

be placed in the WBSWAN POP

and corresponding BSNL

exchange

Page | 231


interface will be terminated on the Managed Switch and suitable VPN will be created by the WBSWAN operator.

The SI for the end user will have to arrange for all necessary permission to erect pole / mast /tower etc for wireless connectivity. Also necessary permission will have to be arranged by the end user for laying the cables within and outside the office premises

Networking and other issues

To adhere to the interface requirement of WBSWAN the SI need to design the end equipment to follow the WBSWAN IP scheme. For each station a pool of 8 IPs would be provided from the WBSWAN IP pool. Out of the 8 usable IPs provided the SI should use 2 IPs (a /30 IP block) for point to point connectivity to be established (DHQ/SDHQ/BHQs) . Balance 6 IPs ( /29 IP block) should be used for. End user LAN

In the event more than 6 IPs are needed for the end customer LAN the end customer will have to device his own mechanism like Proxy server etc and use one of the WBSWAN IPs as gateway

SI would be advised to get in touch with DIT, GoWB prior to quoting for ensuring compatibility of the proposed equipment with the existing WBSWAN system. WBSWAN backbone runs on EIGRP protocol.

All nodes connected to WBSWAN should have adequate antivirus protection

As a policy guidelines, internet feed is not to be provided to the end user equipment connected to WBSWAN

Page | 232


Annexure: CIPA Data Volume

The following tables present the module wise Data Volume in CIPA. This data may used for migration to

CCTNS. However, Data Quality has to be ensured before any such migration exercise.

CIPA Phase – I:

No of cases entered in Hooghly

Registration Investigation Prosecution Information General Diary FIR UD Missing MLC NCR

4049 1518 1386 9 114 74 0 0 2245

No of cases entered in Howrah

Registration Investigation Prosecution Information General

Diary FIR UD Missing MLC NCR

3065 1408 1591 68 3148 578 146 0 4751

NO OF CASES ENTERED in North 24 Parganas

REGISTER Investigation Prosecution Information General

Diary FIR UD MISSING MLC NCR

8183 2183 3537 9 798 122 0 32 49526

No of cases entered in South 24 Parganas



4776 2050 1783 0 163 100 1 0 2641

Page | 233


CIPA Phase – II:

No of cases entered in Kolkata Police



6038 198 483 49 0 0 0 0 5423

No of cases entered in Burdwan



855 440 193 0 0 0 0 0 0

No of cases entered in D – Dinajpur



280 73 60 0 0 0 0 0 269

No of cases entered in Birbhum



56 26 11 0 0 0 0 0 160

No of cases entered in Murshidabad



Page | 234


874 191 108 0 0 0 0 0 108

No of cases entered in Howrah



396 136 183 0 0 0 0 0 93

No of cases entered in Sealdah GRP



123 247 4 0 0 0 0 0 0

No of cases entered in Nadia



629 148 230 0 0 0 0 0 0

Page | 235


Annexure: List of Locations where CCIS is Installed

List of Districts where CCIS is installed:

Sl. No. District Place of Installation

1. North 24 Parganas HQ – Barasat

2. South 24 Parganas HQ – Alipur

3. Howrah HQ – Howrah

4. Hooghly HQ – Chinsurah

5. Midnapore HQ – Midnapore

6. Purulia HQ – Purulia

7. Bankura HQ – Bankura

8. Nadia HQ - Krishnagar

9. Murshidabad HQ – Berhampur

10. Malda HQ – Malda

11. Burdwan HQ – Burdwan

12. Birbhum HQ – Suri

13. Uttar Dinajpore HQ – Raiganj

14. Dakshin Dinajpore HQ – Balurghat

15. Jalpaiguri HQ – Jalpaiguri

16. Darjeeling HQ – Darjeeling

17. Cooch - Behar HQ – Cooch – Behar

18. Howrah – GRP HQ – Howrah

19. Sealdah – GRP HQ – 20, Dum Dum Rd. Calcutta – 30

20. Siliguri – GRP HQ – Siliguri

Page | 236


Annexure: Post Implementation Support Services As part of the post implementation services, the SI shall provide support for the software, hardware, and other infrastructure provided as part of this RFP. SI shall provide five (5) years of comprehensive AMC that includes 1. Warranty support 2. Supply of consumables as following:

a. Printer toner/ cartridge and paper for Printer and Multi Function Laser Unit (Print/ Scan/ Copy): On average each unit (e.g. Police Station, Higher Offices, Other offices) will require to print around 100 pages per day.

Above numbers are indicative and actual consumption may vary from the above. Bidder is advised to quote the unit price for each of the above items along with total cost for these items. The actual payment to SI for the consumables would be based on the actual consumption and the unit price quoted.

Note: Fuel for generators not to be provided by SI. The pricing for fuel should not be included in the costing.

3. Annual Technical Support (ATS) 4. Handholding Services

a. Operations and maintenance services for the server and related infrastructure supplied (inclusive of preventive maintenance) and commissioned by the SI for the application at the Data Center and Disaster Recovery Center.

b. Central Helpdesk from the STATE designated premises. c. Support for the end users at each of the locations including deployment of one competent

person at each police station for a period of six months to handhold the staff after the Core application and the necessary infrastructure are successfully commissioned in the police stations.

d. Software maintenance and support services. e. Application functional support services

Note: The services shall be rendered onsite from the State designated premises. To provide the support for the police stations, circle offices, sub-divisional offices, district headquarters, ranges, zones, Police headquarters and other locations across the State where the software, hardware, and other infrastructure will be rolled out, SI is expected to provide experienced and skilled personnel at each location. The SI will also ensure that there is a Service Center available or setup at each district or a group of districts of the State, as per mutual understanding between State and the SI. The SI shall develop a work plan for the knowledge sharing as per scope defined in this RFP for use in future phases of the project. As part of the warranty services SI shall provide: 1. SI shall provide a comprehensive warranty and on-site free service warranty for 5 years from the

date of Go Live.

Page | 237


2. SI shall obtain the five year product warranty and five year onsite free service warranty on all licensed software, computer hardware and peripherals, networking equipments and other equipment.

3. SI shall provide the comprehensive manufacturer's warranty in respect of proper design, quality and workmanship of all hardware, equipment, accessories etc. covered by the RFP. SI must warrant all hardware, equipment, accessories, spare parts, software etc. procured and implemented as per this RFP against any manufacturing defects during the warranty period.

4. SI shall provide the performance warranty in respect of performance of the installed hardware and software to meet the performance requirements and service levels in the RFP.

5. SI is responsible for sizing and procuring the necessary hardware and software licenses as per the performance requirements provided in the RFP. During the warranty period SI shall replace or augment or procure higher-level new equipment or additional licenses at no additional cost to the State in case the procured hardware or software is not adequate to meet the service levels.

6. Mean Time Between Failures (MTBF) If during contract period, any equipment has a hardware failure on four or more occasions in a period of less than three months or six times in a period of less than twelve months, it shall be replaced by equivalent or higher-level new equipment by the SI at no cost to STATE. However, if the new equipment supplied is priced lower than the price at which the original item was supplied, the differential cost should be refunded to STATE. For any delay in making available the replacement and repaired equipments for inspection, delivery of equipments or for commissioning of the systems or for acceptance tests / checks on per site basis, STATE reserves the right to charge a penalty.

7. During the warranty period SI shall maintain the systems and repair / replace at the installed site, at no charge to STATE, all defective components that are brought to the SI's notice.

8. The SI shall as far as possible repair the equipment at site. 9. In case any hard disk drive of any server, SAN, or client machine is replaced during warranty / AMC

the unserviceable HDD will be property of STATE and will not be returned to SI. 10. Warranty should not become void, if STATE buys, any other supplemental hardware from a third

party and installs it within these machines under intimation to the SI. However, the warranty will not apply to such supplemental hardware items installed.

11. The SI shall carry out Preventive Maintenance (PM), including cleaning of interior and exterior, of all hardware and testing for virus, if any, and should maintain proper records at each site for such PM. Failure to carry out such PM will be a breach of warranty and the warranty period will be extended by the period of delay in PM.

12. SI shall monitor warranties to check adherence to preventive and repair maintenance terms and conditions.

13. The SI shall ensure that the warranty complies with the agreed Technical Standards, Security Requirements, Operating Procedures, and Recovery Procedures.

14. SI shall have to stock and provide adequate onsite and offsite spare parts and spare component to ensure that the uptime commitment as per SLA is met.

15. Any component that is reported to be down on a given date should be either fully repaired or replaced by temporary substitute (of equivalent configuration) within the time frame indicated in the Service Level Agreement (SLA).

16. The SI shall develop and maintain an inventory database to include the registered hardware warranties.

As part of the ATS services SI shall provide: 1. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes,

replacements and maintenance.

Page | 238


2. If the Operating System or additional copies of Operating System are required to be installed / reinstalled / de-installed, the same should be done as part of ATS.

3. SI should carry out any requisite adjustments / changes in the configuration for implementing different versions of Application Software.

4. Updates/Upgrades/New releases/New versions. The SI shall provide from time to time the Updates/Upgrades/New releases/New versions of the software and operating systems as required. The SI should provide free upgrades, updates & patches of the software and tools to STATE as and when released by OEM. This clause is applicable for all server side as well as client side applications.

5. SI shall provide patches to the licensed software including the software, operating system, databases and other applications.

6. Software License Management. The SI shall provide for software license management and control. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes, replacements, and maintenance.

7. SI shall provide complete manufacturer’s technical support for all the licensed software problems and/or questions, technical guidance, defect and non-defect related issues. SI shall provide a single-point-of-contact for software support and provide licensed software support including but not limited to problem tracking, problem source identification, problem impact (severity) determination, bypass and recovery support, problem resolution, and management reporting.

8. The manufacturer’s technical support shall at a minimum include online technical support and telephone support during the STATE’s business hours (Business hours in STATE will be from 0830 hours to 2030 hours on all days (Mon-Sun)) with access for STATE and SI to the manufacturer’s technical support staff to provide a maximum of 4 hour response turnaround time. There should not be any limits on the number of incidents reported to the manufacturer. STATE shall have access to the online support and tools provided by the manufacturer. STATE shall also have 24x7 access to a variety of technical resources including the manufacturer’s knowledge base with complete collections of technical articles.

As part of the Handholding services to provide Operations and maintenance support for the server and related infrastructure supplied and commissioned by the SI for the application at the Data Center and Disaster Recovery Center SI shall provide: 1. The scope of the services for overall IT infrastructure management as per ITIL framework shall

include 365x24x7 on site Monitoring, Maintenance and Management of the server and related infrastructure supplied and commissioned by the SI for the application at the Data Center and Disaster Recovery Center. The business hours in STATE will be from 0830 hours to 2030 hours on all days (Mon-Sun). SI will plan these services accordingly. The SI shall provide the MIS reports for all the devices installed in the Data Center and Disaster Recovery Center in format and media as mutually agreed with the STATE on a monthly basis. Whenever required by STATE, SI should be able to provide additional reports in a pre-specified format. The indicative services as part of this support are as below:

(a) System Administration, Maintenance & Management Services

(b) Application Monitoring Services

(c) Network Management Services

(d) Backend Services (Mail, messaging, etc)

(e) Storage Administration and Management Services

(f) IT Security Administration Services and Services for ISO 27001 and ISO 20000 compliance

Page | 239


(g) Backup and Restore Services

As part of the Handholding services to provide Centralized Helpdesk and Support for end users at each location SI shall provide: 1. The service will be provided in the local language (i.e. Bengali) of the STATE. 2. The help desk service that will serve as a single point of contact for all ICT related incidents and

service requests. The service will provide a Single Point of Contact (SPOC) and also resolution of incidents. STATE requires the SI to provide Help Desk services to track and route requests for service and to assist end users in answering questions and resolving problems related to the software application, network, Data Center, Disaster Recovery Center, Client side infrastructure, and operating systems at all locations. It becomes the central collection point for contact and control of the problem, change, and service management processes. This includes both incident management and service request management.

3. SI shall provide a second level of support for application and technical support at police stations, circle offices, sub-divisional offices, district headquarters, range offices, zonal offices, state police headquarters and other locations across the STATE where the software, hardware, and other infrastructure will be rolled out.

4. For all the services of STATE within the scope of this RFP, SI shall provide the following integrated customer support and help.

5. Establish 16X6 (6:00 AM to 10:00 PM from Monday to Saturday) Help Desk facility for reporting issues/ problems with the software, hardware and other infrastructure.

6. SI shall maintain and support to all client side infrastructure including hardware, networking components, and other peripherals.

7. SI shall provide maintenance of Hardware, including preventive, scheduled and predictive Hardware support, as well as repair and / or replacement activity after a problem has occurred.

8. SI shall track and report observed Mean Time Between Failures (MTBF) for Hardware. 9. SI shall provide functional support on the application components to the end users. 10. SI shall also provide system administration, maintenance and management services, LAN

management services, and IT security administration services. As part of the Handholding services to provide software maintenance and support services SI shall provide: 1. The Software Maintenance and Support Services shall be provided for all software procured and

implemented by the SI. The SI shall render both on-site and offsite maintenance and support services to STATE to all the designated locations. The Maintenance and Support Services will cover, all product upgrades, modifications, and enhancements.

2. Updates/Upgrades/New releases/New versions. The SI will implement from time to time the Updates/Upgrades/New releases/New versions of the software and operating systems as required after necessary approvals from STATE about the same.

3. Tuning of application, databases, third party software’s and any other components provided as part of the solution to optimize the performance.

4. The SI shall apply regular patches to the licensed software including the operating system and databases as released by the OEMs.

5. Software Distribution. SI shall formulate a distribution plan prior to rollout and distribute/install the configured and tested software as per the plan.

6. Software License Management. The SI shall provide for software license management and control. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes,

Page | 240


replacements, and maintenance. SI should perform periodic audits to measure license compliance against the number of valid End User software licenses consistent with the terms and conditions of site license agreements, volume purchase agreements, and other mutually agreed upon licensed software terms and conditions and report to STATE on any exceptions to SI terms and conditions, to the extent such exceptions are discovered.

7. The SI shall undertake regular preventive maintenance of the licensed software. As part of the Handholding services to provide application functional support services SI shall provide: 1. The Application Functional Support Services shall be provided for all software procured and

implemented by the SI. The SI shall render both on-site maintenance and support services to STATE from the development center in STATE.

2. Enhancements and defect fixes. SI shall incorporate technological changes, and provide enhancements as per the requests made by STATE. SI shall perform minor changes, bug fixes, error resolutions and minor enhancements that are incidental to proper and complete working of the application.

3. Routine functional changes that include user and access management, creating new report formats, and configuration of reports.

4. SI shall provide user support in case of technical difficulties in use of the software, answering procedural questions, providing recovery and backup information, and any other requirement that may be incidental/ancillary to the complete usage of the application.

5. The SI shall migrate all current functionality to the new / enhanced version at no additional cost to STATE and any future upgrades, modifications or enhancements.

6. The SI shall perform user ID and group management services. 7. The SI shall maintain access controls to protect and limit access to the authorized End Users of the

STATE. 8. The services shall include administrative support for user registration, creating and maintaining user

profiles, granting user access and authorization, providing ongoing user password support, announcing and providing networking services for users and providing administrative support for print, file, directory and e-mail servers.

Exit Management and Transition – Capacity Building at State After the exit of the SI, State shall take up the management of CAS (State). Therefore before the exit of the SDA, State must be strengthened and capacity must be developed for State to manage CAS. The SI must plan the capacity building initiative to enable State manage CAS, and will collaborate with State to implement the plan. The SI shall create a detailed plan for Capacity Building (CB) required at State to manage CAS and a Transition Plan (implemented over a minimum period of three months) to affect the handover to State; and implement the same in collaboration with State before the completion of their engagement.

Page | 241


Annexure: CCTNS Implementation Plan

It is proposed to roll out CCTNS in three phases. Deployment of hardware, connectivity and other

infrastructure across all police stations, higher offices and other police units would take place in the first

two phases. CAS (Core Application Software) would be rolled out in three phases. The core focus of each

of the three phases is delineated below:

CCTNS Phase I

Geographical Coverage

During the first phase of the application, CCTNS would be rolled out in 1‐2 districts (amounting to

approximately 10% of the total police stations across the state) and all higher offices associated with

these districts. The roll out would include installation and commissioning of hardware, connectivity,

other infrastructure and associated services (such as handholding). The choice of the districts where the

first phase would be rolled out is provided below. The police stations chosen for the first phase should

be a mix and match of both developed and undeveloped districts and geographically separated districts.

Sl. No. Districts in Phase I Number of Police

Stations

Rationale for choosing them

1 Burdwan 32 High ICT maturity of the police stations and

the offices in the district

Urban Centers have better basic amenities and

typically lead technology acceptance. Hence,

only urban PSs have been chosen in Phase – I

2 Purulia 21 Lower maturity in terms of ICT requirements

and also geographically separated from the

other district chosen.

In addition to the above, Higher offices (District, SDPO and Circles) of Purulia and Burdwan have been

covered in Phase I, along with 1 Zone and 2 Ranges. Also 2 PHQs and SCRB have been covered in Phase I.

Page | 242


Service Coverage

During the first phase, the following services and service levels will be achieved

Service Coverage

S.

No. Services Service Level

1 Petition Management Service

May vary as per the type

of services required.

2 Unclaimed/Abandon Property Register Service

3 Complaint and FIR Management Service

4 Investigation Management Service

5

Crime and Criminal Records and Query Management Service

(Such as stolen vehicle, missing persons/children, unidentified

dead bodies etc.)

6

Periodic Crime, and Law & Order Reports and Review Dashboard

Service

7 User Access and Authorization Management Service

Digitization of Historical Data

In addition to the functionality identified above, Phase‐I would also include the digitization of historical

data (covering the last 10 years). This would involve digitizing 832,163 case records.

Digitization of historical data would help the police department maximize benefits from features such as

Search and Reporting and is would significantly enhance outcomes in the areas of Crime Investigation,

Criminals Tracking, servicing the requests of citizens and other groups, etc. The digitization exercise

would be carried out by the state‐level SI. Please note that apart from the data that is to be digitized

using the registers mentioned above, Data from Talash has to be migrated. The following table presents

the year wise volume of data to be migrated from Talash:

Year 2004 2005 2006 2007 2008 2009 Grand Total

Talash Data 3589 11484 15061 15548 18746 21024 85452

Page | 243


Application Functionalities

The application modules and functionalities covered during the Phase I of CCTNS implementation are



Modules Additional Functionalities

Registration

Module

Counterfeit Advisory and Theft Reporting

System should provide an option to register Theft cases under GRP

Petitioner to be able to download/print the certificate /report /permission

or response to request

System should have provision for registering cases against unknown culprits

Investigation

Module

System should provide a provision for initial investigation for information

received through PCR, phone etc. wherein a complainant is first established

and a letter of complaint generated / a suo motto case registered before an

FIR is lodged.

System should allow the provision of multiple Officers (with no upper limit)

to be assigned to a particular Case

System should generate the Memo of Evidence that needs to be submitted

with the charge sheet for approval by the concerned higher authority

For Arms Seized, Memo of Evidence is not necessary; PP opinion through SP

is mandated in these cases. So, system should capture PP’s opinion.

System should allow for the creation of a Special Report after review and

rejection of initial charge sheet


System should allow different users to assign different categories of cases to

be SR Case

Prosecution

Module Provision has to be kept for entering arrested person details.

Basic and

Advanced Search

Module

System should allow the creation of different sets of roles for same

hierarchy

System should allow for parameterized search of defect log status

Page | 244




Basic (regular)

reporting and MIS

Indicative reports include the following:

Charge sheet details (PS & Date wise)

FRT

FIR & Non FIR pending/under investigation & final form received (PS wise)

Case Trial (GR/NGR) and summary report on the same

Case Disposal (Head wise)

Warrant details

Property Register

In WBP, the case alerts may be send to an OC, IC or CI while in KP, these may

be sent to the OC or AC

The System must able to provide reports for actions on cases organized:

By Status (Unresolved/In - progress/Resolved)

Page | 245


Capacity Building Initiatives

The no. of personnel in each group that would be trained on the four training themes during Phase I is

provided in the table below:

Estimated for number of Personnel for Direct Training

Training Program

Group

A

Group

B

Group

C

Total

Awareness and sensitization of benefits of IT 215 967 638 1,820

Basic Computer Awareness & Role based training for application

users 215 15,478 25,518 41,211

Trainers Training 0 19 159 179

System Administration & Support Training 0 0 1914 1,914

Total 430 16,464 28,230 45,124

Outcomes

Phase Activities Outcomes Challenges

CCTNS

Phase – I

Site Preparation in

Selected Districts.

Civil construction, if needed

to support the ICT

infrastructure completed.

No major challenges are envisaged.

Installation of

Hardware.

Hardware and Network

infrastructure installed

Delay in the infrastructure

(hardware, software, networking

devices etc) procurement.

Instability of the network causing

application downtime

Train the officials Officers well versed with

Basic IT skills and knowledge

of CCTNS Application

Absence of upward communication

channel may lead to lack of feedback

on training. This may adversely

impact training quality.

Commissioning of

the Application.

CCTNS application rolled out

successfully.

Unavailability of the experienced

team members with the proper

technology knowledge used in the

Page | 246



project.

Testing: Sufficient coverage of

business scenarios in the Unit and

Integration tests; and issues raised

there upon.

Data Migration Data in CIPA systems and

other from hard copy

registers migrated to CCTNS

Failure to treat data migration as a

project unto itself

Underestimating the time and cost

of data migration

Lack of end-state data quality

Failure to support the organizational

support:

Lack of appreciation for the

complexities of data mapping

Hand holding Initial support provided to

effectively handle CCTNS

based activities


team members with the project

domain knowledge.


team members with the proper

technology knowledge used in the

project.

Insufficient amount of time allotted

for this activity.

Page | 247


CCTNS Phase II


During Phase‐II of CCTNS, the remaining police stations and the other agencies as mentioned in the

Annexure: Unit Details will be covered for the installation and commissioning of hardware, connectivity

and other infrastructure and associated services. The districts where the second phase would be rolled

out are provided below.


S. No. Districts in Phase I Number of Police Stations

1 North 24 Pgs 40

2 South 24 Pgs 44

3 Howrah 19

4 Mushidabad 26

5 Nadia 21

6 Hooghly 23

7 Birbhum 18

8 Purba Medinipur 22

9 Pachim Medinipur 21

10 Bankura 23

11 Jhargram Police District 8

12 Darjeeling 18

13 Uttar Dinajpur 9

14 Cooch Bihar 10

15 Jalpaiguri 17

16 Malda 11

17 Dakshin Dinjapur 8

18 Sealdah GRP 13

19 Howrah GRP 13

20 Kharagpur GRP 8

21 Siliguri GRP 9

22 KP – North 8

23 KP – Central 9

24 KP – Eastern 7

25 KP - SOUTH & SOUTH SUBARBAN 11

26 KP - Port Division 7

Page | 248



S. No. Districts in Phase I Number of Police Stations

27 KP - South East 6

Service Coverage

During the second phase, the following services and service levels will be achieved

Service Coverage

S. No. Services Service Level

1 Citizen’s Portal Services

May vary as per the type

of services required

2 State-SCRB-NCRB Data Transfer and Management Service

3 State CAS Administration and Configuration Management Service

4 User Help and Assistance Service

5 User Feedback Tracking and Resolution Service

6 Activity Log Tracking and Audit Service

7

Notification of Alerts, Important Events, Reminders and Activity

Calendar or Tasks Service






Collaboration

Solutions (police

messaging, email)

The Patrolling Officer assigned to a patrol party will need to interact directly

with the system over wireless/communication device

System should provide alerts to superior officers whenever a transferred

officer joins under them

System should generate an alert whenever a new user is stipulated the work

by the older user

Citizen Interface Petitioner to be able to download/print the certificate/report/permission or

response to request

Services such as request for conducting ceremonies and functions (pujas,

marriages etc.)

Services for NoC generation by employers

Services for applying for gun licensing

Page | 249


Advanced analysis

and Reporting

System needs to have the provision of reports to be taken multiple times

during each day

System should allow for the creaion of a Special Report after review and

rejection of initial chargesheet


Automated

Fingerprint

Recognition

System

No state specific changes are envisaged



Training Program

Group

A

Group

B

Group

C

Tota

l

Awareness and sensitization of benefits of IT 0 0 60 60


users 0 0 2380

238

0


System Administration & Support Training 0 0 179 179

Total 0 0 2633 263

3

Outcomes


CCTNS

Phase – II

Site Preparation in

Selected Districts.

Civil construction, if

needed to support

the ICT infrastructure

completed.

No major challenges are envisaged.

Establish Solar Power

Connectivity in

identified districts.

Persistent Power

failure ceases to be a

challenge to the

CCTNS

implementation.

Delay in installation may lead to rollout

of CCTNS in these Police Stations with

power issues.

Installation of

Hardware.

Hardware and

Network

infrastructure

installed

Delay in the infrastructure (hardware,

software, networking devices etc)

procurement.

Instability of the network causing

application downtime

Page | 250



Training Officials Officers well versed

with Basic IT skills

and knowledge of

CCTNS Application



on training. This may adversely impact

training quality.

Commissioning of the

Application.

CCTNS application

rolled out

successfully.

Unavailability of the experienced team

members with the proper technology

knowledge used in the project.

Testing: Sufficient coverage of business

scenarios in the Unit and Integration

tests; and issues raised there upon.

Data Migration Data in CIPA systems

and other from hard

copy registers

migrated to CCTNS

Failure to treat data migration as a

project unto itself

Underestimating the time and cost of

data migration

Lack of end-state data quality

Failure to support the organizational

support:

Lack of appreciation for the

complexities of data mapping

Hand holding Initial support

provided to

effectively handle

CCTNS based

activities


members with the project domain

knowledge.


members with the proper technology

knowledge used in the project.

Insufficient amount of time allotted for

this activity.

CCTNS Phase III


All police units in West Bengal would have been covered for the installation and commissioning of

hardware, connectivity and other infrastructure by the end of Phase‐II. CCTNS Phase‐III is planned

around the release of subsequent versions of CAS and the large enhancements initiated at the state

level.

Service Coverage

Service Coverage

S. No. Services Service Level

Page | 251


1 PCR Call Interface and Management Service May vary as per the type

of services required

2 Court and Jail Interface and Prosecution Management Service

3 Police Email and Messaging Service






External Interfaces (such as Courts, Prisons,

Hospitals, Cell phone service providers,

Vehicle information, etc.)

System should help identify and trace hoax callers

System should allow a caller to register a case from any

place (even from outside the jurisdiction) if the

incidence being reported took place within the

jurisdiction of the PCR

System should enable a caller response time within 5

minutes

There should be enough flexibility to attend to intra

state scenarios (even beyond the PCR’s jurisdiction)

subject to the criticality of the event and availability of

resources nearby for quick deployment.

The Nodal Officer assigned to a patrol party will need to

interact directly with the PCR system over

wireless/communication device

Crime Prevention (Beat Management, etc.)

and

other modules decided to be provided to all

states

No state specific changes are envisaged



Training Program Group

A

Group

B

Group

C Total

Awareness and sensitization of benefits of IT 0 0 68 68


users 0 0 2720 2720


Page | 252


System Administration & Support Training 0 0 204 204

Total 0 0 3,009 3,00

9

Outcomes


Phase III Training Officials Officers well versed

with Basic IT skills and

knowledge of CCTNS

Application



on training. This may adversely impact

training quality.

External Interfacing Application Integration

with external

applications

Dissimilarity in data structures or

technical specifications between CCTNS

and the external solution can lead to

further complexities in integrating the

external interfaces.

Page | 253


Annexure: CCTNS Rollout Plan Following is the overall timeline for major activities:

Major Activity Year

1

Year

2

Year

3

Year

4

Year

5

Year

6

Project planning and management

System study, design, application development and

integration of the CCTNS Application Software based on

Core Application Software (CAS) provided by NCRB

Configuration Customization and Extension (New Modules)

of CAS (State) and Integration with CAS (Center) and

External Agencies

Site preparation at the Client site locations

IT Infrastructure at the Client site locations

Network connectivity (LAN etc.) internal to Police Stations

/ Higher Offices and Other Units

IT infrastructure at the Data Center and Disaster Recovery

Center

Data migration and Digitization of Historical Data

Migration of CIPA data for Police Stations / Higher Offices

to CCTNS

Capacity building

Handholding Support

Support to 3rd party acceptance testing, audit and

certification: SI will be responsible for the support to 3rd

party acceptance testing, audit and certifications

Post Go Live Support

Bidders need to submit a detailed Project Plan based on their approach.

Page | 254


Annexure: Service Levels for CCTNS Solution 1. This document describes the service levels to be established for the Services offered by the SI to the

State. The SI shall monitor and maintain the stated service levels to provide quality service to the State.

2. Definitions.

a. “Scheduled Maintenance Time” shall mean the time that the System is not in service due to a scheduled activity as defined in this SLA. The scheduled maintenance time would not be during 16X6 timeframe. Further, scheduled maintenance time is planned downtime with the prior permission of the State.

b. “Scheduled operation time” means the scheduled operating hours of the System for the month. All scheduled maintenance time on the system would be deducted from the total operation time for the month to give the scheduled operation time. The total operation time for the systems and applications within the Primary DC, DRC and critical client site infrastructure will be 24X7X365. The total operation time for the client site systems shall be 18 hours.

c. “System or Application downtime” means accumulated time during which the System is totally

inoperable within the Scheduled Operation Time but outside the scheduled maintenance time and measured from the time the State and/or its employees log a call with the SI team of the failure or the failure is known to the SI from the availability measurement tools to the time when the System is returned to proper operation.

d. “Availability” means the time for which the services and facilities are available for conducting

operations on the State system including application and associated infrastructure. Availability is defined as: {(Scheduled Operation Time – System Downtime) / (Scheduled Operation Time)} * 100%

e. “Helpdesk Support” shall mean the 16x6 basis support center which shall handle Fault reporting, Trouble Ticketing and related enquiries during this contract.

f. “Incident” refers to any event / abnormalities in the functioning of the Data Centre Equipment / Services that may lead to disruption in normal operations of the Data Centre, System or Application services.

3. Interpretations.

a. The business hours are 8:30AM to 4:30PM on all working days (Mon-Sat) excluding Public Holidays or any other Holidays observed by the State. The SI however recognizes the fact that the State offices will require to work beyond the business hours on need basis.

b. "Non-Business Hours" shall mean hours excluding “Business Hours”.

c. 18X7 shall mean hours between 06:00AM -12.00 midnight on all days of the week.

Page | 255


d. If the operations at Primary DC are not switched to DRC within the stipulated timeframe (Recovery Time Objective), it will be added to the system downtime.

e. The availability for a cluster will be the average of availability computed across all the servers in

a cluster, rather than on individual servers. However, non - compliance with performance parameters for infrastructure and system / service degradation will be considered for downtime calculation.

f. The SLA parameters shall be monitored on a monthly basis as per the individual SLA parameter requirements. However, if the performance of the system/services is degraded significantly at any given point in time during the contract and if the immediate measures are not implemented and issues are not rectified to the complete satisfaction of the State or an agency designated by them, then the State will have the right to take appropriate disciplinary actions including termination of the contract.

g. A Service Level violation will occur if the SI fails to meet Minimum Service Levels, as measured on a half yearly basis, for a particular Service Level. Overall Availability and Performance Measurements will be on a monthly basis for the purpose of Service Level reporting. An “Availability and Performance Report” will be provided by the SI on monthly basis in the State suggested format and a review shall be conducted based on this report. A monthly Availability and Performance Report shall be provided to the State at the end of every month containing the summary of all incidents reported and associated SI performance measurement for that period. The monthly Availability and Performance Report will be deemed to be accepted by the State upon review and signoff by SI and the State. Where required, some of the Service Levels will be assessed through audits or reports e.g. utilization reports, measurements reports, etc., as appropriate to be provided by the SI on a monthly basis, in the formats as required by the State The tools to perform the audit will need to be provided by the SI. Audits will normally be done on regular basis or as required by the State and will be performed by the State or the State appointed third party agencies.

h. EMS system as specified in this RFP shall play a critical role in monitoring the SLA compliance and hence will have to be customized accordingly. The 3rd party testing and audit of the system shall put sufficient emphasis on ensuring the capability of EMS system to capture SLA compliance correctly and as specified in this RFP. The selected System Integrator (SI) must deploy EMS tool and develop additional scripts (if required) for capturing the required data for SLA report generation in automated way. This tool should generate the SLA Monitoring report in the end of every month which is to be shared with the State on a monthly basis. The tool should also be capable of generating SLA reports for a half-year. The State will audit the tool and the scripts on a regular basis.

i. The Post Implementation SLAs will prevail from the start of the Operations and Maintenance Phase. However, SLAs will be subject to being redefined, to the extent necessitated by field experience at the police stations / higher offices and the developments of technology practices globally. The SLAs may be reviewed on an annual/bi-annual basis as the State decides after taking the advice of the SI and other agencies. All the changes would be made by the State in consultation with the SI.

j. The SI is expected to provide the following service levels. In case these service levels cannot be achieved at service levels defined in the tables below, it shall result in a breach of contract and

Page | 256


invoke the penalty clause. Payments to the SI are linked to the compliance with the SLA metrics laid down in the tables below. The penalties will be computed and calculated as per the computation explained in this Annexure. During the contract period, it is envisaged that there could be changes to the SLA, in terms of addition, alteration or deletion of certain parameters, based on mutual consent of both the parties i.e. the State and SI.

k. Following tables outlines the key service level requirements for the system, which needs be ensured by the SI during the operations and maintenance period. These requirements shall be strictly imposed and either the State or a third party audit/certification agency shall be deployed for certifying the performance of the SI against the target performance metrics as outlined in the tables below.

Implementation Phase SLAs

1. Capacity Building

Service Level Description

Measurement

Capacity Building

At least 80% of the trainees for each officer group i.e. Group A/B/C within the training program should give a rating of satisfactory or above. Severity of Violation: High This service level will be monitored and measured on a per District basis through feedback survey to be provided to each attendee within the program. If the training quality in the program falls below the minimum service level, it will be treated as one (1) violation. The total number of violations for the payment period will be the cumulative number of violations across all the programs across all Districts in the payment period.

Capacity Building

At least 80% of the intended trainees for each officer group i.e. Group A/B/C should be trained at the end of each phase of the Implementation. Severity of Violation: High This service level will be monitored and measured on a per District basis through feedback survey to be provided to each attendee within the program. If the training quality in the program falls below the minimum service level, it will be treated as one (1) violation. The total number of violations for the payment period will be the cumulative number of violations across all the programs across all Districts in the payment period.

Page | 257


2. Data Migration/Digitization


Measurement

Data Migration

/Digitization

Error rate (All standard Data Migration/Digitization errors) in a batch should be less than 0.5%. Severity of Violation: High This service level will be measured on a monthly basis for each Police Station / Higher Office covered under that phase of the implementation. If the data migration service level in a police station / higher office falls below the minimum service level, it will be treated as one (1) violation. The total number of violations for the payment period will be the cumulative number of violations across all the police stations / higher offices in the payment period.

Delivery Related Service Level Agreement (SLA) Criteria

Explanation: The deduction mentioned in this table shall be made from the next due payment to the vendor for services provided on Statewide basis.

S. No.

Service Metrics Parameters

Baseline Lower Performance

Violation of Service level agreement

Basis of Measurement

Remarks

Metric Metric Deduction

Metric Deduction

1. Delivery of the Reports / deliverables due as per milestones in the contract

As per the dates as mentioned in the contract

One week after the due date

Rs. 10,000

>1 week after the due date

Rs. 20,000 for every week of delay

Dates for delivery of reports as mentioned in the contract

2. Development, deployment and testing of CAS (State) application

5.0 months from date of signing of contract

5-7 months

100,000 Rupees

More than 7 months

Rs. 1,00,000 per month of delay

Months taken after beginning of the assignment to develop and test the application at the Data center by the Operator, not including the

The centralized application should be tested for desired functionalities, security, and completeness as

Page | 258




S. No.





Remarks


Metric Deduction

time taken for software audit by the SPMU or any other agency nominated by the Empowered Committee, CCTNS Project, West Bengal

well as compliance with SLA, within the period

3. Supply, installation and Commissioning of all ICT hardware at Police Stations, Higher offices and other Agencies relevant for CCTNS Project, West Bengal

3 months

3-4 months

For noncompliance at each point of deployment: Rs. 30,000

> 4 months

For noncompliance At each point of deployment: Rs. 45,000

Months after taking over of the office site for project

The deduction shall be made per site basis, where criterion is not satisfied

4. Supply, installation and Commissioning of the Data Center Equipment and associated Hardware

6 months from the date of signing of contract

6-7 months

Rs. 100,000

More than 7 months

Rs. 100,000 for every month of delay

Months taken after beginning of the assignment

State may conduct Independent audit to verify that the data center is as per the specifications.

5. Capacity At least Less Rs. Less Rs. 25,000 Feedback The

Page | 259




S. No.





Remarks


Metric Deduction

building 80% of the training audience for each group of officers i.e. Group A/B/C should give a rating of satisfactory or above

than 80% and more than 60% attendees find the training satisfactory

15,000 / training session

than 60% of the attendees find the training satisfactory

per training session

survey to be provided to each attendee

feedback of the attendees must be taken after every training session and this feedback should be leveraged for improving the capacity building program

6. Data Digitization

Error rate in a batch during verification should be less than 0.5%

Error rate between 0.5% - 1.0%

Rs. 5,000 / batch and correction of records

Error rate of over 1.0%.

Rs. 10,000 / batch and the entire batch to be re-done

Error rate in a batch during verification

Error rate is measured by percentage of the records with corrections marked by Designated officials

7. Maintenance phase

All the issues reported regarding hardware, softwar

Resolution of issues within 2 working days of reporti

Rs. 500 Resolution of the issue after 2 working days

Rs. 1000 for every day delay over and above beyond

Time and date of reporting of the issue

Page | 260




S. No.





Remarks


Metric Deduction

e etc. at all units and the Data Center for CCTNS Project, West Bengal should be resolved within 24 hours (within 1 working day)

ng

3. Violations and Associated Penalties a. The primary intent of Penalties is to ensure that the system performs in accordance with the defined

service levels. Penalties are not meant to be punitive or, conversely, a vehicle for additional fees.

b. Penalty Calculations. The framework for Penalties, as a result of not meeting the Service Level Targets is as follows:

i. The performance will be measured for each of the defined service level metric against the

minimum / target service level requirements and the violations will be calculated accordingly.

ii. The number of violations in the reporting period for each level of severity will be totaled and used for the calculation of Penalties.

iii. Penalties applicable for each of the high severity violations are 0.1% of respective payment-

period payment to the SI.

Page | 261


iv. Penalties applicable for each of the medium severity violations are 0.05% of respective payment-period payment to the SI.

Post Implementation Phase SLAs 1. Primary DC/DRC Site Infrastructure Systems and Application Availability and Performance

a. Production CAS Systems. The failure or disruption has a direct impact on the State’s ability to

service its police stations / higher offices, ability to perform critical back-office functions or a direct impact on the organization.

This includes but not limited to:-

i. Storage and related switches at Primary DC and DRC. ii. Web, Application, Database, and Backup Servers at Primary DC and DRC.

iii. Primary DC to DRC connectivity. iv. Primary DC and DRC network infrastructure. v. Primary DC and DRC security infrastructure.

b. Non-CAS Systems in Production and Non Production Systems (Development, QA, and

Training). The failure or disruption has no direct impact on the State’s ability to serve its police stations / higher offices, or perform critical back-office functions.

i. Production Non CAS Servers. ii. Test, QA and Training Servers.

iii. Helpdesk infrastructure & applications. iv. EMS Infrastructure.

c. CAS Solution Components. The failure or disruption has a direct impact on the State’s ability to

service its police stations / higher offices, ability to perform critical back-office functions or a direct impact on the organization.

d. Non ERP Solution Components. The failure or disruption has no direct impact on the State’s ability to serve its police stations / higher offices, or perform critical back-office functions.

e. These service levels will be monitored on a monthly basis.

f. The below tables gives details on the Service Levels the SI should maintain.


Measurement

Infrastructure Availability

Availability of production CAS systems shall be at least 99% on a 24*7 basis leaving scheduled downtime (if any)

Severity of Violation: High

Availability over the six month period

Violations for calculation of penalty

Page | 262



Measurement

< 99% & >= 98.5% 1

< 98.5% & >= 98% 2

< 98% 3

In addition to the above, if the service level in any month in the six-month period falls below 98%, one (1) additional violation will be added for each such month to the overall violations for this service level.


Availability of non-CAS systems in production expected to be on a 24*7 basis leaving scheduled downtime (if any) and nonproduction systems during the working hours as per the contract shall be at least 97% in each. Severity of Violation: Medium



< 97% & >= 96.5% 1

< 96.5% & >= 96% 2

< 96% 3



RTO shall be less than or equal to six (6) hours. Severity of Violation: High Each instance of non-meeting this service level will be treated as one (1) violation.


RPO (zero data loss in case of failure of Primary DC) should be zero minutes. However, bidder to propose best possible solution considering the 2 site (DC and DR) architecture for CCTNS project, WB. Severity of Violation: High Each instance of non-meeting this service level will be treated as two (2) violations.

Infrastructure Performance

Sustained period of peak CPU utilization of any server crossing 70% (with the exception of batch processing) shall be less than or equal to 30 minutes. Severity of Violation: High Each occurrence where the peak CPU utilization of any server crosses 70% (with the exception of batch processing) and stays above 70% for time more than 30 minutes will be treated as one (1) instance.

Page | 263



Measurement

Number of instances over the six month period


>0 & <=3 1

> 3 2

In addition to the above, if the number of instances in any month in the six-month period exceeds 3, one (1) additional violation will be added for each such month to the overall violations for this service level.


Sustained period of peak I/O utilization of any server crossing 70% (with the exception of batch processing) shall be less than or equal to 30 minutes. Severity of Violation: High Each occurrence where the peak I/O utilization of any server crosses 70% (with the exception of batch processing) and stays above 70% for time more than 30 minutes will be treated as one (1) instance.



>0 & <=3 1

> 3 2



Sustained period of peak memory utilization of any server crossing 70% (with the exception of batch processing) shall be less than or equal to 30 minutes. Severity of Violation: High Each occurrence where the peak memory utilization of any server crosses 70% (with the exception of batch processing) and stays above 70% for time more than 30 minutes will be treated as one (1) instance.



>0 & <=3 1

> 3 2


Page | 264



Measurement

Application Availability

Availability of CAS solution components measured within the Data Center shall be at least 99.9% Severity of Violation: High This service level will be monitored on a monthly basis.



< 99.9% & >= 99.5% 1

< 99.5% & >= 99% 2

< 99% 3


Application Availability

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



< 97% & >= 96% 1

< 96% 2


Application Performance

Average application response time during peak usage hours as measured from a client terminal within the Data Center shall not exceed 4 seconds. Severity of Violation: High The list of critical business functions and peak usage hours will be identified by the State during the Supply and System Integration Phase. This service level will be monitored on a monthly basis.

Average application response time over the six-month period


> 4s & <= 5s 1

> 5s & <= 6s 2

> 6s 3

Page | 265



Measurement

In addition to the above, if the average turnaround time in any month in the six-month period goes beyond 6s, one (1) additional violation will be added for each such month to the overall violations for this service level.

2. Client Site Infrastructure Systems

a. Critical Client Site Systems. The failure or disruption results in inability of the police station / higher

offices to service its dependent offices or perform critical back-office functions. Critical client site infrastructure means the IT infrastructure at client site which are shared by multiple users i.e., Core Switch, Core Routers, etc.

b. This service level will be measured on a monthly basis for each implementation site. c. The below tables gives details on the Service Levels the SI should maintain.

Service Level Description Measurement

Client Site Systems Availability

Availability of the critical client site ICT infrastructure components at all the implementation sites i.e. Police Stations, Higher Offices and Other Agencies where CCTNS is to be rolled out shall be at least 99% Severity of Violation: High This service level will be measured on a monthly basis for each implementation site. If the availability in a month for an implementation site falls below the minimum service level, it will be treated as one (1) violation. The total number of violations for the six-month period will be the cumulative number of violations across all the months across all sites in the six-month period.

Page | 266


3. Handholding Support: Client Site Support

a. Level 1 Incident. The incident has an immediate impact on the state’s ability to service its police stations/higher office, to perform critical back-office functions or has a direct impact on the organization.

b. Level 2 Incidents. The incident has an impact on the state’s ability to service its police stations/higher offices that while not immediate, can cause service to degrade if not resolved within reasonable time frames

c. The severity of the individual incidents will be mutually determined by the state and SI.

d. The scheduled operation time for the client site systems shall be the business hours of the state.

e. This service level will be measured on a monthly basis for each implementation site.

f. The tables on the following page give details of the Service Levels the SI is required to maintain.


Client Site Support Performance

80% of the Level 1 Incidents at each Police Station/higher office where such incidents are reported should be resolved within 2 business hours from the time call is received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 8 business hours. Severity of Violation: Medium This service level will be measured on a monthly basis for each implementation site. If the performance in a month for a Police Station/higher office falls below the minimum service level, it will be treated as one (1) instance. The total number of instances for the six-month period will be the cumulative number of instances across all the months across all Police Stations/higher offices in the six-month period. Average number of instances per month = (Total number of instances for the six-month period) / 6

Average number of instances per month

Violations for calculation of Penalty

>0 & <=4 1

>4 & <=8 2

>8 & <=12 3

Page | 267



>12 4


80% of the Level 2 Incidents at each Police Station/higher offices where such incidents are reported should be resolved within 6 business hours from the time a call is received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 48 hours. Severity of Violation: Medium This service level will be measured on a monthly basis for each Police Station/higher office. If the performance in a month for a Police Station/higher office falls below the minimum service level, it will be treated as one (1) instance. The total number of instances for the six-month period will be the cumulative number of instances across all the months across all Police Stations/higher offices in the six-month period. Average number of instances per month = (Total number of instances for the six-month period) / 6

Average number of instances per month

Violations for calculation of Penalty

>0 & <=4 1

>4 & <=8 2

>8 & <=12 3

>12 4


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

Handholding Support: Application Support

a. Level 1 Defects. The failure to fix has an immediate impact on the State’s ability to service its police stations / higher offices, inability to perform critical back-office functions or a direct impact on the organization.

Page | 268


b. Level 2 Defects. The failure to fix has an impact on the State’s ability to service its police stations / higher offices that while not immediate, can cause service to degrade if not resolved within reasonable time frames.

c. Level 3 Defects. The failure to fix has no direct impact on the State’s ability to serve its police stations / higher officers, or perform critical back office functions.

d. The severity of the individual defects will be mutually determined by the State and SI.

e. This service level will be monitored on a monthly basis.

f. The below tables gives details on the Service Levels the SI should maintain.


Application Support Performance

95% of the Level 1 defects shall be resolved within 4 business hours from the time of reporting full details. Severity of Violation: High This service level will be monitored on a monthly basis.

Performance over the six month period


< 95% & >= 90% 1

< 90% & >= 85% 2

< 85% 3



95% of the Level 2 defects shall be resolved within 72 hours from the time of reporting full details. Severity of Violation: High This service level will be monitored on a monthly basis.



< 95% & >= 90% 1

< 90% & >= 85% 2

< 85% 3


Application Support 100% of the Level 3 defects shall be resolved within 120 hours from the

Page | 269



Performance time of reporting full details. Severity of Violation: High This service level will be monitored on a monthly basis.



< 100% & >= 90% 1

< 90% & >= 80% 2

< 80% 3



Up to date of the documentation of the design, modifications, enhancements, and defect-fixes in the half-yearly period. Severity of Violation: Medium This service level will be measured on a half-yearly basis. Each instance of non-meeting this service level will be treated as one (1) violation.

4. Network Uptime: Severity of Violation: High This service level will be monitored on a monthly basis.

The below tables gives details on the Service Levels the SI should maintain.


Network Uptime Availability of the network and all related components at all the implementation sites (including Police Stations, Higher Offices and Other Agencies under CCTNS Project, West Bengal) shall be at least 99% Severity of Violation: High This service level will be measured on a monthly basis for each implementation site. If the network availability in a month falls below the minimum service level,

Page | 270



it will be treated as one (1) violation. The total number of violations for the six-month period will be the cumulative number of violations across all the months across all sites in the six-month period.

5. Handholding Support: Helpdesk and Data Center Support

a. Level 1 Calls. The failure to fix has an immediate impact on the State’s ability to service its police stations / higher offices, inability to perform critical back-office functions or a direct impact on the organization.

b. Level 2 Calls. The failure to fix has an impact on the State’s ability to service its police stations / higher offices that while not immediate, can cause service to degrade if not resolved within reasonable time frames.

c. Level 3 Calls. The failure to fix has no direct impact on the State’s ability to serve its police stations / higher offices, or perform critical back-office functions.

d. This service level will be monitored on a monthly basis.

e. The below tables gives details on the Service Levels the SI should maintain.


Measurement

Helpdesk Performance

98% of the calls shall be answered within 45 seconds. Severity of Violation: High

This service level will be monitored on a monthly basis.

Performance over the six-

month period

Violations for calculation of

penalty

< 98% & >= 90% 1

< 90% & >= 80% 2

< 80% 3



98% of the incidents within helpdesk resolution capacity shall be resolved in a cycle time of 24 hours Severity of Violation: High

Page | 271



Measurement

This service level will be monitored on a monthly basis.


month period


penalty

< 98% & >= 90% 1

< 90% & >= 80% 2

< 80% 3



98% of the non SI supported incidents shall be routed to the appropriate service provider within 30 minutes. Severity of Violation: Medium This service level will be monitored on a monthly basis.


month period


penalty

< 98% & >= 90% 1

< 90% & >= 80% 2

< 80% 3



80% of the Level 1 calls shall be resolved within 2 hours from call received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 8 business hours. Severity of Violation: High This service level will be monitored on a monthly basis.


month period


penalty

< 80% & >= 70% 1

< 70% & >= 60% 2

< 60% 3

In addition to the above, if the service level in any month in the six-month

Page | 272



Measurement

period falls below 60%, one (1) additional violation will be added for each such month to the overall violations for this service level.


80% of the Level 2 calls shall be resolved within 6 hours from call received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 48 hours. Severity of Violation: High This service level will be monitored on a monthly basis.


month period


penalty

< 80% & >= 70% 1

< 70% & >= 60% 2

< 60% 3



80% of the Level 3 calls shall be reported on status and action to be communicated within 24 hours from call received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 72 hours. Severity of Violation: High This service level will be monitored on a monthly basis.


month period


penalty

< 80% & >= 70% 1

< 70% & >= 60% 2

< 60% 3


Datacenter Support Performance

Replacement of hardware equipment shall be done within 15 days of notification by the State. These equipments would have failed on four or more occasions in a period of less than three months or six times in a period of less than twelvemonths. (Mean Time Between Failure Condition) Severity of Violation: High

Page | 273



Measurement

Each instance of non-meeting this service level will be treated as one (1) violation.

Datacenter Support Performance

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

6. Reporting

a. The below tables gives details on the Service Levels the SI should maintain for client site systems availability.


Availability and Performance Report

Provide monthly SLA compliance reports, monitoring and maintenance related MIS reports for all relevant implementation components covering ICT hardware, applications, training etc. across all units under CCTNS Project, West Bengal by the 5th of the following month. Severity of Violation: Medium This service level will be monitored on a monthly basis. If the monthly SLA compliance report related to the service level metrics is not provided in the given timeframe, it will be treated as one (1) instance. The total number of instances for the six-month period will be the cumulative number of instances across all the months in the six-month period.

Total number of instances over

the six month period


>0 & <=3 1

> 3 2

Page | 274


7. Credits for Successful Application Uptake The tables below give details of the credits that can be gained by the SI for successful uptake of the application in the State. The credits will not be calculated for the first reporting period.


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

such as submitting an application for a no-objection certificate and Informational such a requesting the status of a case)

2. Number of active users profiles in CCTNS 3. Number of read-write transactions on CCTNS system 4. Number of Searches carried out on data in CCTNS 5. Total number of FIRs prepared through CCTNS 6. Total number of Crime Details Forms prepared through CCTNS 7. Total number of Key Investigation Forms prepared through CCTNS 8. Total number of Arrest Cards prepared through CCTNS 9. Total number of ChargeSheets prepared through CCTNS 10. Quality (recency and accuracy) of information available in CCTNS 11. Number of cases reported to be solved because of the availability of

CCTNS 12. Number of ad-hoc requests successfully responded to using CCTNS 13. Turnaround Time for submitting the monthly and annual crime/criminal

information to NCRB from the State A credit will be gained for each of the above parameters if the uptake for that parameter shows significant improvement. The following table applies for each of the above parameters:

% increase over the measurement in the last reporting period

Credits

>5 & <=10% 2

>10 & <=15% 3

> 15% 4

8. Violations and Associated Penalties

a. The primary intent of Penalties is to ensure that the system performs in accordance with the defined service levels. Penalties are not meant to be punitive or, conversely, a vehicle for additional fees.

b. A six monthly performance evaluation will be conducted using the six monthly reporting periods of that period.

Page | 275


c. Only one SLA will be considered for each type of violation in order to avoid paying of penalties at different level caused by a single violation

Page | 276


d. Penalty Calculations. The framework for Penalties, as a result of not meeting the Service Level Targets are as follows:

(a) The performance will be measured for each of the defined service level metric against the minimum / target service level requirements and the violations will be calculated accordingly.

(b) The number of violations in the reporting period for each level of severity will be totaled and used for the calculation of Penalties.

i. If the total number of credits gained by the SI is lower than the total number of high severity

violations in the reporting period, the total number of credits will be subtracted from the total number of High Severity Violations in the reporting period for the calculation of Penalties.

ii. If the total number of credits gained by the SI is higher than the total number of high severity violations in the reporting period, the resultant total number of high severity violations in the reporting period for calculation of penalties will be considered as zero (0).

(c) Penalties applicable for each of the high severity violations is two (2) % of respective half yearly payment to the SI

(d) Penalties applicable for each of the medium severity violations is one (1%) of respective half yearly payment to the SI

(e) Penalties applicable for each of the low severity violations is half percentage (0.5%) of respective half yearly payment to the SI

(f) Penalties applicable for not meeting a high (H) critical performance target in two consecutive half years on same criteria shall result in additional deduction of 5% of the respective half yearly payment to the SI. Penalty shall be applicable separately for each such high critical activity

(g) Penalties applicable for not meeting a medium (M) critical performance target in two consecutive half yearly periods on same criteria shall result in additional deduction of 3% of the respective half yearly payment to the SI. Penalty shall be applicable separately for each such medium critical activity

(h) Penalties applicable for not meeting a low (L) critical performance target in two consecutive half yearly periods on same criteria shall result in additional deduction of 2% of the respective half yearly payment to the SI. Penalty shall be applicable separately for each such medium critical activity

(i) It is to be noted that if the overall penalty applicable for any of the review period during the currency of the contract exceeds 25% or if the overall penalty applicable for any of the successive half year periods during the currency of the contract is above 15%; then the State shall have the right to terminate the contract.

Page | 277


Annexure: Indicative Project Organization Structure of the selected bidder

SI Project Director

Program Manager

Technology SMEs

Project Manager

Domain SMEs

Data Digitization /

Migration Team

Application

Development Team

Leads

Business Analysts

Infrastructure Team

Change

Management &

Capacity Building

Leads

Application

Development Team

QA & Testing Team

Change Management &

Capacity Building Team

AMC Team

Networking Team

Page | 278


Annexure: Sample Registers

Illustrative

Page | 279


Illustrative

Page | 280


Illustrative

Page | 281


Annexure: Physical paper base data conversion Strategy In the context of CCTNS Project, WB, all the data from the hardcopy registers can be converted into

electronic formats using the following techniques:

Manual data entry – The SI would be employing data entry operators who will on a regular basis for

a certain time period in the implementation schedule will manually enter data using the hardcopy

and the physical files in the Police Stations and Higher Offices in a format prescribed during the

design stage.

Data Digitization and scanning – Digitization is a method of converting analog form of data to digital

and electronic formats using advanced tools and technologies without the need of manual

intervention. The SI may use Scanning to convert physical formats of data into electronic formats

like images and PDFs etc. Following steps may be followed by the SI for data digitization:

o Identification of the items for the collection – The SI in consultation with the State will identify which data are needed to be converted into digital formats.

o Choice of formats – The SI in consultation with the State will decide upon the formats to which these data is going to be converted. For example, *.doc, *.html, *.rtf etc.

o Choice of hardware – The SI in consultation with the State will finalize and procure all relevant hardware infrastructure needed to convert this data to electronic format without any additional cost to the State. For example, scanners, OCRs (Optical Character Readers), computers etc.

o Choice of software – The SI in consultation with the State will finalize the selection of software supporting digitization such as OCR and ICR.

o Storage and archiving – The SI will have to calculate the storage space required for the digitized data.

o Management – The SI will have to manage the activities so as to ensure optimal results. The SI will have to take into consideration several factors for getting the desired quality for digitization such as conditions and coloring of the source documents, font types, persons handling the activities etc. along with unknown factors. All these have to be managed by the SI while managing the entire activity of digitization

However, the SI can also propose any other technique as deemed suitable/fit for the conversion of physical data into electronic format.

Recommended Methodology of Data Verification Effective data verification is the most important step in the digitization of data. Selected SI will support the state police department in carrying out the data verification in a time bound manner and evolve a mechanism for data validation at various levels. An illustrative mechanism is given below:

The manually processed Integrated Investigation Forms (1 to 7)/ other registers for a particular case would be given to the SI and will be checked for data completeness and consistency (lack of blank fields, correct data type per field, etc.) by the SI .

Once the data is entered, digitized IIF forms (1 to 7)/ other registers will then be checked/ verified from the System for the particular case and shall be compared with the manually processed Case File, whereas In case of migrated data, IIF forms will be checked against the

Page | 282


report generated from CIPA system for any particular case. Errors detected at this stage will be corrected by SI at no cost to the department.

Corrected System generated Case File and its data will then be matched for verification against the existing manual records/ digitized records in CIPA application in Police Station. Further, system generated Case File will go through various levels of verification, starting from the Police Station to District level, District to Range and State level. A suggested scheme for the number of record verification is given below:

Sl.

No.

Verification

Check

Stage Responsibility

for checking

Responsibility

for correction

Remarks

1. Data consistency

check for manually

processed data

from different

registers

Before

entering

data into

the system

SI in consultation

with Police Station

staff

Selected bidder e.g. empty

fields, spelling

mistakes,

wrong/

improper data

2.

System generated

Information from

data captured from

registers

After data

entry into

new system

Police Station

IC /OC or a sub

inspector made

responsible by the

IC / OC and SPMU

Selected bidder 100% records

checking of

respective

Police Stations

3. District DSP

supported by SPMU

Selected bidder 30% records of

each Police

Station under

his jurisdiction

4. District SP

supported by SPMU

Selected bidder 15% records of

each Police

Station under

his jurisdiction

5. State CCTNS Nodal

Officer supported by

Selected bidder 1% all records

Page | 283


SPMU

This type of data verification by the concerned officials of the state police department will be done through Data Verification Workshops where the records are brought, verification done and the issues are flagged within a definite time frame. SI shall be responsible for conducting workshops and shall formally inform project nodal officer in writing well in advance for data verification workshop. SI shall also be responsible for incorporating and implementing changes proposed in these workshops at no additional cost to the department. These workshops shall work as User Acceptance Testing for Data Digitization. However overall System Acceptance testing shall be different from this testing and SI shall provide all the support required for ensuring quality of data entry / data digitization, wherever required. There should also be a mechanism to incorporate those Police transactions that have taken place during the digitization of data phase. Correction facilities available in the software should be monitored to detect and discourage its misuse. Once this process is complete, the corrected data will be re-entered in the system and the records for which disputes have not been resolved will be flagged in the system so that this will not be bottleneck in the system going live. However, SI shall seek approval for flagging such data and point out the same during workshops. In case approval is not provided by state police department on the unresolved data entry, the same shall be counted for penalty calculations. Beyond this exercise, SI should be responsible for correcting the data entry found erroneous by the Department or its designated representatives at no additional cost to the Department. State police department may at its discretion levy penalties for erroneous data entry as per penalty terms defined in the Service Level Agreement.

Page | 284


Following diagram is an indicative representation of the workflow of the manual data conversion

activities to be carried out in CCTNS Project, WB. Bidders can propose their own framework as deemed

to be fit for the project.

Start

Physical Documents

submitted by insurers

and others are

accumulated for

digitalization and

scanning

Identification of

batches

Data manually

entered/

digitalized/

scanned

High Level error

after scanning/

digitizing/manual

enrt

Whether the data is

properly captured as per

desired results?

Medium Level

error after

scanning/

digitizing/manual

entry

Low Level or

minor errors after

scanning/

digitizing/ manual

entry

Re- scanning/

digitizing/entry of

data for better

accuracy

Thorough

cleansing and

Editing of data

Minor Cleansing

and editing of data

to increase

accuracy

Archive the document

Whether the

document is

scanned digitized/

entered?

Digitized data gets

stored in the

databases

Back-up of

database is taken.

Back-up End

End

Scanned

Digitized/ Entered

Creation of

metadata

Error Free

With Errors

CCTNS Project, WB Data

Digitization Workflow

Page | 285


Annexure: IIF Forms

Following is the details of IIF forms.

Sl No. IIF Number Form

1 IIF – I First Information Report

Attachment to Item 7 of First Information Report

2 IIF – II Crime Details Form

Attachment to Item 7 of Crime Details Form or Item 10 of Property Search & Seizure Form.

3 IIF – III Arrest/Court Surrender Form

4 IIF – IV Property Search & Seizure Form

Attachment to Item 10 of Property Search & Seizure Form.

5 IIF – V Final Form/Report

6 IIF – VI Court Disposal Form

7 IIF – VII Result of Appeal Form

8 - COMBINED INPUT FORM FOR

WANTED/MISSING/KIDNAPPED/DESERTER FROM ARMED

FORCES ETC/ESCAPEE/UNIDENTIFIED PERSON/DEAD BODY

9 - MISCELLANEOUS DETAILS FORM

10 - ADDITIONAL TERRORIST DETAILS

Forms are attached in following pages.

I.I.F.-I/�� I��

��FIRST INFORMATION REPORT

�� (Under Section 154 Cr.P.C.)

�� !��"�� !��"�� !��"�� !��"��#$%�#$%�#$%�#$%��& �'(�) ��& �'(�) ��& �'(�) ��& �'(�) �****

1. District(+�,�)...……..........……………..P.S.(��)..…....………............Year(-. )………..//..FIR No.(�/��/��/� ).……..……Date(��)........./…………..…

2. (i) Act('0"0��)...……..................................…………. Sections("��)./////////////////////////////////…………..///////////////////………..………….

(ii) Act('0"0��)...........…………….................................Sections("��)...............................................................….………..……………………

(iii) Act('0"0��)..........................................……………..Sections("��)................................................................…………..……………………

(v) Other Acts & Sections('(��'0"0��- �"��)/////////////////////////////..........................................…………….……………………………..

3. (a)(�) Occurrence of offence:(1��*�Day��*.........……………….. Date from��&*…………..….Date to��*......…….../////…..

� � �� Time Period��!�*...………..........////////Time from�2�&��&*....……..............….////////////. Time to�2�&��*///....................…//////……………

(b)�3* Information received at P.S.��&��4��*: Date��*............................... Time��*...........///////……………………………

(c)�)* General Diary Reference�� 5 *: Entry No.��6-67�� /*.........................…….. Time��*..…////////………………………………

� � � � �4. Type of Information��8 �&��4�!9:* : Written/Oral�0,+3�/�;+3�* : � �5. Place of Occurrence : 1��<�,��=�;�� (a)��* Direction and distance from P.S.��&��&��>��- ��?*//// ……………………………………………

………………………………………………………………………………Beat No.�2@�� /*//////////////////////…………………..//………………………..

(b)�3* Address��*./.............................................................................................................……………….........…………..////……………………….

...........................................................................................................……………….....................................................///………………………..

(c )�)* In case, outside the limit of this Police Station, then ��A��&��@��&�2�!��!�B��2�C�*�:

Name of P.S/��&��*...................................…… …………….……….District� +�,�* ……………………………………………………

6. Complainant / Informant : �0>�� /�A6D,��&�&�-�,�*:

(a)��*�� Name��*/////........................................................................................................................….…////////…………….//………………………..

(b)�3* Father's/Husband's Name�6��/�0��*.....................................................................................…///////…………/…………………………

(c)�)* Date/Year of Birth��(�0�0�/-. *.………………………..........…..//�d)�1*� Nationality��E@��*.......................…..…….///////……………/…

(e)�FG* Passport No/�� /*///…………………………………………………………..///…………………………………………………………../.

Date of Issue��?��&��0�0�*..…………………….//////Place of Issue��?��&��<��*//……………..……………………………….

(f)�* Occupation�H�-��*................................................................................................................................……///…………………………………

(g)�I* Address��*....................................................................................................................................///////…………………………………………

7. Details of known/suspected/unknown accused with full particulars��J��/� ��K"/'J��'05�9LM��N �6--�N *�:�(Attach separate sheet, if necessary)

��O-P��!�B��',)��Q��R�@��S*

(1) ....................................................................................................................................................................…///……………………..////…………………

(2) ................................................................................................................................................……………………........................./////////………………..

(3) ................................................................................................................………………………...................................................…//////////………………

��####/2 -

I.I.F.-I/�� I

8. Reasons for delay in reporting by the complainant / informant �0>��/A6D,��&�&�-�,&�T��B��&�&��S��&�?��N*

.............................................................................................................................................................................../////////………………………………………..

.............................................................................................................................................................................../////////…………………………………………

� //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////…………………

9. Particulars of properties stolen��?�!9:��U�6D��6--�N) / �Attach separate sheet, if necessary ) ��O-P��!�B��',)��Q��R�@��S*

.............................................................................................................................................................................../////////…………………………………………

.............................................................................................................................................................................../////////……………………………………..

.............................................................................................................................................................................../////////……………………………………..

10. Total value of property stolen (��?�!9:��U�6D��9 ,��V�) .........................................………………………./////……………………………………………..

�11. Inquest Report(��R�9��@W�� ) / U.D. case No. ('�� 0��R�9��,�� /) / if any ��:�!��* / ……..///////…………………………….//////�12. F/I/R contents��/��/��/��6-.��-<�9* (Attach separate sheet, if required ): ��O-P��!�B��',)��Q��R�@��S*

13. Action taken��):�� -�:��):�� -�:��):�� -�:��):�� -�:*�*�*�*�/Since the above information reveals commission of offence(s) u/s as mentioned at Item No. 2. :

��CL��T��B�� /�X��C+V,+3��"��Y ��& �'(�) ��'��"�!��&��,��!Z:

(1) Registered the case and took up the investigation or ��,�� @�� [��O�U5��):��*��

(2) Directed Sh./Smt./Km.(Name of I.O.)/\@/\@�0�/�9 / (��'0"��?��* .///////////////////////////////////////////Rank(��*.//////////////////……………….

No.�� /*…/// ////////////////////to take up the�Investigation or ��O�U5��&��& �0��]>��&�)��*

(3) Refused investigation due to� �+�� NM� �&� �� &� �&� A(�� )�� *…//////////////////////////////……………………………��

/////////////////////////////////////////////////////////////////////////////////………………………………////////////////////////////////////////////////////……./ Or��*

(4) Transferred to P.S. ��,��<��(��)��B��&��*//////////////////////////////////////////////////////////////District�+�,�*///// ...….…… on

point of jurisdiction�W&^�0"��_67��&*/

F.I.R. read over to the complainant / informant, admitted to be correctly recorded and a copy given to the complainant /informant, free of cost.

��/��/��/�0>�� /A6D,��&�&�-�,&��`��9��:�):B�+��&��!?�,&3��967��[��0>�� /A6D,��&�&�-�,&��0��0�:>9V��

��): |*

R.O.A.C.��`��9��[��!?��)��`��9��[��!?��)��`��9��[��!?��)��`��9��[��!?��)�� |��****

Signature of Officer in charge, Police Station

� � � � � � � �� 5��?��& �!<��W��5��?��& �!<��W��5��?��& �!<��W��5��?��& �!<��W�****��

��14. Signature / Thumb impression�� Name (��****//////////////////////////////////////////////////////////////////////////////////of the complainant / informant.

�0>�� /A6D,��&�&�-�,&��&

!<��W�/' )�a& ��0�>��*�� Rank.��****.......................….....……. No.�� b�� b�� b�� b��****.................////////////////////////…………

� � � � � � � ��#5. Date and time of despatch to the court ��(��,��5&��&��0�0��[��*///////////////////////////////////////////////////…………///////////////////////

- 2/2 -

Attachment to item 7 of First Information Report

�� b�� b�� b�� b��c�c�c�c�� ,K�� ,K�� ,K�� ,K��

Physical features, deformities and other details of the suspect/accused : ( If known / seen )

� ��K"�/�'05�9L��>��?��2��-�B�6-�� 0��'(��6--�N��J��!M/��&3&�)��!M*

Sl.

No.

�/�

/

Sex

0, )

Date/Year

of Birth

�(�0�0�/

-.

Build

>��?��

2��-�

Height

(cms.)

��

��&/�@/��S*

Complexion

� )

Identification Mark(s)

�!��& �0(!

1 2 3 4 5 6 7

Deformities/

Peculiarities

6-�� 0��/6-0>67��

Teeth

��

Hair

2�,

Eyes

O3S

Habit(s)

O��S

Dress Habit(s)

�!��-�

8 9 10 11 12 13

Language/

Dialect

5�.�/2�,@

PLACE OF

>�?��& ��!<�&��B�0�U�0,+3��0(!��;��!Z�?

Burn Mark

�,&�!9��

Leucoderma

"-,��)

Mole

�<��

Scar

1�-

Tattoo

)9�&�!9��

14 15 16 17 18 19

These fields will be entered only if complainant/informant gives any one or more particulars about the suspect/accused.

A��M��S��6-67��5@��)@��0>�� /A6D,��&�&�-�,��H�6LB�� K"/'05�9L��& �2��&��S��&�'0"��6--�N��&��!8�|

�

I.I.F.-II/�� II

CRIME DETAILS FORM

'��"�6--�N�� '��"�6--�N�� '��"�6--�N�� '��"�6--�N��

1. District(+�,�)////////////...……..............P.S.(��)..…...///////.............Year(-. )……..//..FIR No.(�/��/��/� ).……..……Date(��)........./………….………..

�2. Acts and Sections�'0"0��- �"��*//////////////////////////////////////////////////////....................................................................................................………

� �3. Place of occurrence shown by:�1��<�,��3��&�-�,&��*:�

Name��*..............................................Father's/Husband's Name�6��/�0��*//////////////////////////////////////////////////////.................................…./

Address� ��*..............................................................................................................................................................///////////////////////////////////////////////////

4. Type of crime : �'��"��*:

(i) Major Head ��9b��>@. * ........................................…….(ii) Minor Head��,19�>@. *//////////////////////.....................................................……..

(iii) Method(s) � (1) ////////////////////////////////////////.......................................................................................................................

� � -��&��

��?��?�& *� (2) ................................................./////////////////////////////////////////....................................................................

(3) .................................................................................................../////////////////////////////////////////....................

(iv) Conveyance(s) used��)��)��-�!�*�/////////////////////////////////////////////////..................................................................................….

(v) Character assumed�"��N��)��d�* //////////////////////////////////////////////////...........................................................................................

(vi) Language / Dialect used��)��):�5�.�/2�,@*////////////////////////////////////////////////////�..........................................................................…

(vii) Special feature –1��6->&.�,WN�#*�///////////////////////////////////////////////////................................................................................................…...

Special feature –2��6->&.�,WN�X*�///////////////////////////////////////////////........................................................................................................…

Special feature –3�6->&.�,WN�e*�///////////////////////////////////////////////.....................................................................................................……

(viii) Type of place of occurrence��1��<�,��*�////////////////////////////////////////////////////..................................................................……

� �(ix) Type of property stolen[4 types](Major head of the property to be filled):��?��)�@��U�6D��[%��]��U�6D��& ��9b��>@. �5��&�!&�9*

1) ...............................................................//////////////////////////.. 2) ...///////////////////........................................................

3) ////////////////////////.//................................................................ 4) ///////////////////...........................................................

5. Particulars of the victim(s) (Attach separate sheet, if required):��@�F�M��6--�N ��O-P��!�B��',)��Q��R�@��S*�:��

Sl.

No.

�/� /

Name

��

Father's/

Husband's

Name

6��/�0��

��

Date/

Year

of Birth

�(�

0�0�/-.

Sex

0, )

Nationality

��E@��

Religion

�"�

Whether

SC/ ST/

OBC

f��'�9G

��0�/'�9G

��0�

'(��6�IF&�

-) ��&�!Z�?

Occupation

H�-��

Address

��

Injury

(Grievous/

Simple)

��) 5@�/

��(�*

Means of

causing

injury

!0��B�

+��&��

�!9�:�):

1 2 3 4 5 6 7 8 9 10 11 12

��####/2 ��

I.I.F.-II/�� II

6. Motive of crime �'��"��Cg&P�*/////…….......................................................................................................................................////////�7. Details of properties stolen/involved (Use appropriate prescribed form(s) and attach).�

��?�!9:/� 0,4��U�6D��6--�N��C��9L�� )��R�@��S*� �

8. Date and time of visit to the place of occurrence:��1��<�,��& �0��?WN��0�0��- ��*:

Date��*///////////////////////////////////////// ……………… Time ��*�/////////////////////////////…….......................

� � � � �

9. Description of the place of occurrence�1��<�,��-N �*:

10. Description of physical evidence from the scene of crime for the property recovered/seized for the purpose of investigation.

� ��& �Cg&P��&�1��<�,��&�2��/�=��):��U�6D��& �5;0��N��-N ��:-

(i) Witness�Name�)-�!��*////..////////////////...............................................................…………………………………………………….

Address��*/////////////////////////////////////////////////…..................................................................…………………………………………

(ii) Witness�Name�)-�!��*�//////////////////…………////……………………………………..................................................................

� �Address��*�////////////////////////////////////////////////////.....................................................……………………………………………………

11. Sketch/ Map of the place of occurrence (Attach sketch/ map with legends separately, if needed. If to scale, indicate so. May be certified and

signed by witnesses, if required).

1��<�,��&3�0^/�f>��O-P��!�B��&3�0^/�f>�B�� & �M��!��',)��&��R�@��S |��8��&��& �'�9��!�B��

CV,&3��S�|��O-P��!��)-�!M�T��R��6��- �!<��W��-��*� Whether the Sketch/Map prepared by draftsman? Yes/No

� f��&3�0^/�f>�B��d��T��8��)��?�!�/�!?

Signature of Investigating Officer

��'0"��?��& ��'0"��?��& ��'0"��?��& ��'0"��?��& �!<��W�!<��W�!<��W�!<��W��

��Name��*////*////*////*////........................................��

Place�<��* ..................... Rank��*/////*/////*/////*/////.............……. No./�� /*/*/*/*� Date :�0�0�* …………….

�

- 2/2 -

Att

ach

men

t to

Ite

m 7

of

Cri

me

Det

ail

s F

orm

or

Item

10 o

f P

rop

ert

y S

earc

h &

Seiz

ure

Form

.

'��

�"�6--

�N��

��

��

� b��

'��

�"�6--

�N��

��

��

� b��

'��

�"�6--

�N��

��

��

� b��

'��

�"�6--

�N��

��

��

� b��c� c�c�c�

'�-��

U�6D��

��,�>

@��-

��=�

@��

��

� b��

'�-��

U�6D��

��,�>

@��-

��=�

@��

��

� b��

'�-��

U�6D��

��,�>

@��-

��=�

@��

��

� b��

'�-��

U�6D��

��,�>

@��-

��=�

@��

��

� b��#G

�#G

�#G

�#G

�� ,K�

�� ,K�

�� ,K�

�� ,K�

�

Det

ail

s of

iden

tifi

ab

le n

um

ber

ed o

r u

nn

um

ber

ed p

rop

erty

in

clu

din

g f

ire-

arm

s se

ized

/ re

cover

ed/

stole

n/

involv

ed:

OK�

&��h

MO

K�&��h

MO

K�&��h

MO

K�&��h

M� ��!��

!��

�K�

��!��

!��

�K�

��!��

!��

�K�

��!��

!��

�K�B� B�B�B�� b��

��'

�-��'

� b��

��

=�� b��

��'

�-��'

� b��

��

=�� b��

��'

�-��'

� b��

��

=�� b��

��'

�-��'

� b��

��

=�/2��

2��

�2�

��

2��

�/��?

��?

��?

��?/�

0,4��

U�6D��

��6--�

N� 0,

4��

U�6D��

��6--�

N� 0,

4��

U�6D��

��6--�

N� 0,

4��

U�6D��

��6--�

N:

Dis

tric

t(+�

,�).

..…

…..

....

....

……

……

……

....

P.S

.(��).

.….…

……

……

…..

....

....

....

Yea

r(-.

)……

..//.

.FIR

No.(�/��/��/� ).…

…..

……

Dat

e(��

)...

....

../…

……

….

Wit

nes

s-1

)-�!�#

Sig

natu

re o

f In

vest

igati

ng O

ffic

er

��'

0"��?��&�!

<��W

�

Sig

nat

ure

!<��W

�N

am

e� ��

��

��

��

* *** …

……

……

……

……

……

……

……

..

� ��

Wit

nes

s-2

Ran

k� ��

��

��* ***

……

……

……

.. N

o.� ��

�

�

� /* /*/*/*

……

….…

……

…

)-�!�X

��

��

��

��

��

��

��

Sig

nat

ure

!<��W

�

Sl.

No.

�/�

/

Type

of

pro

per

ty

�U�

6D��

��

��

Est

imat

ed

val

ue

(in R

s.)

'�9��0�

��

��V�

��d/�S*

Quan

tity

��^�

Mak

e

�&�

Model

/

Bore

��,

/

2��

Num

ber

� b��

Spec

ial

mar

ks

of

iden

tifi

cati

on

�!��

&�6->&.�

0(!

Countr

y

of

ori

gin

�&>��

!��

0�0�

��

! 9:

Sei

zed/

Rec

over

ed/

Sto

len/

Involv

ed

�=�

/2��/

��?/�

0,4

Bel

ongin

g t

o v

icti

m/

accu

sed o

r

aban

doned

�@�F�

/'05

�9L��

&�

� 2 0"��'

�-��

��R�L

Insu

rance

cert

ific

ate

No.

2@��

�N�^

�

� /

Nam

e of

Insu

rance

com

pan

y

2@��U�

�@��

1

2

3

4

5

6

7

8

9

10

11

12

13

Att

ach

men

t to

Ite

m 7

of

Cri

me

Det

ail

s F

orm

or

Item

10 o

f P

rop

ert

y S

earc

h &

Seiz

ure

Form

.

'��

�"�6--

�N��

��

��

� b��

'��

�"�6--

�N��

��

��

� b��

'��

�"�6--

�N��

��

��

� b��

'��

�"�6--

�N��

��

��

� b��c� c�c�c�

'�-��

U�6D��

��,�>

@��-

��=�

@��

��

� b��

'�-��

U�6D��

��,�>

@��-

��=�

@��

��

� b��

'�-��

U�6D��

��,�>

@��-

��=�

@��

��

� b��

'�-��

U�6D��

��,�>

@��-

��=�

@��

��

� b��#G

�#G

�#G

�#G

�� ,K�

�� ,K�

�� ,K�

�� ,K�

�

Det

ail

s of

Cu

ltu

ral

prop

ert

y s

eized

/rec

over

ed/s

tole

n:

�=�

�=�

�=�

�=�

/2��

2��

�2�

��

2��

�/��?

��?

��?

��?!

9:��

� <��0��

U�6D��

��6--

! 9:��

� <��0��

U�6D��

��6--

! 9:��

� <��0��

U�6D��

��6--

! 9:��

� <��0��

U�6D��

��6--�N �N�N�N

:

Dis

tric

t(+�

,�).

..…

……

……

……

…..

....

....

....

..P

.S.(��).

.….…

……

……

…..

....

....

....

Yea

r(-.

)……

..//

..F

IR N

o.(�/��/��/� ).…

…..

……

Dat

e(��

)...

....

../…

……

…..

Sl.

No.

�.�

� /

Type

�� <��0��

�U�

6D��

��

��

Mat

eria

l

u

sed

"��9�

+��&�

0�0�

�

Nom

en-

clat

ure

��T

0�

Hei

ght

i�:

Bre

adth

;F�:

Dep

th

)!�

�:

Wei

ght

-j�

Age

�AD

/BC*

O�9�

�://:

/��- *

Est

imat

ed

Val

ue

(in R

s.)

'�9��0�

��

��V�

�

�d/�

S/*

Sp

ecia

l fe

atu

res

6->&.�

,WN

6->&.�

,WN

6->&.�

,WN

6->&.�

,WN

Sei

zed/

Rec

over

ed/

Sto

len

�=�

/2��/

��?

Photo

gra

ph

coll

ecte

d

Yes

/No

��,@�):�

'�-��

!?

AS

I

cert

ific

ate

No.

�/��

/O:/�

��N

�^��

/

Insu

rance

cer

tifi

cate

No.

and n

ame

of

the

com

pan

y

2@��

�N�^

�� /�

[��2@��U�

�@�

��

cm-

mm

�&/�

@/-

0�/�

@/

cm-

mm

�&/�

@/-

0�/�

@/

cm-

mm

�&/�

@/-

0�/�

@/

kg.-

gm

.

��/k

��

k��

-1

-2

-3

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

Wit

nes

s-1

)-�!�#

Sig

natu

re o

f In

vest

igati

ng O

ffic

er

��'

0"��?��&�!

<��W

�S

ignat

ure

!<��W

�N

am

e� ��

��

��

��

* *** …

……

……

……

……

……

……

……

..

� ��

Wit

nes

s-2

Ran

k� ��

��

��* ***

……

……

……

.. N

o.� ��

�

�

� /* /*/*/*

……

….…

……

)-�!-�

Sig

nat

ure

!<��W

�

Att

ach

men

t to

Ite

m 7

of

Cri

me

Det

ail

s F

orm

or

Item

10 o

f P

rop

ert

y S

earc

h &

Seiz

ure

form

.

'��

�"�6--

�N��

��

��

� b��

'��

�"�6--

�N��

��

��

� b��

'��

�"�6--

�N��

��

��

� b��

'��

�"�6--

�N��

��

��

� b��c� c�c�c�

'�-��

U�6D��

��,�>

@��-

��=�

@'�-��

U�6D��

��,�>

@��-

��=�

@'�-��

U�6D��

��,�>

@��-

��=�

@'�-��

U�6D��

��,�>

@��-

��=�

@��

��

� b��

��

��

� b��

��

��

� b��

��

��

� b��#G

�#G

�#G

�#G

�� ,K�

�� ,K�

�� ,K�

�� ,K�

�

Det

ail

s of

Au

tom

ob

ile

seiz

ed/r

eco

ver

ed

/sto

len

/in

volv

ed

�=�

�=�

�=�

�=�

/2��

2��

�2�

��

2��

�/��?

��?

��?

��?/�

0,4�-

�!�M��6--�

N� 0,

4�-

�!�M��6--�

N� 0,

4�-

�!�M��6--�

N� 0,

4�-

�!�M��6--�

N:

Dis

tric

t(+�

,�).

..…

…////////////.

....

...//

....

..P

.S.(��).

.…..

.///////////..

....

....

...Y

ear(-.

)……

..//.

.FIR

No.(�/��/��/� ).…

…..

……

Dat

e(��

)...

....

../…

……/////

Sl.

No.

�/

� /

Type

of

auto

mobil

e

-�!�

��

��

Est

imat

ed v

alue

(in R

s.)

'�9��0�

��

��V�

��d/�S*

Mak

e

�&�

Colo

ur

� )

Model

(Yea

r)

��,

�-. *

Reg

n.

No.

� �@�

�N��

/

Chas

sis

No.

&0�

��

/

Engin

e N

o.

A +��

/

Sei

zed/

Rec

over

ed/

Sto

len/

Involv

ed

�=�

/2��/

��?/�

0,4

Bel

ongin

g t

o v

icti

m/

accu

sed o

r

aban

doned

�@�F�

/'05

�9L��

&�

� 2 0"��'

�-��

��R�L

Insu

rance

cert

ific

ate

No.

2@��

��N

�^��

/

Nam

e of

Insu

rance

com

pan

y

2@��U�

�@��

��

1

2

3

4

5

6

7

8

9

10

11

12

13

Wit

nes

s-1

)-�!�#

Sig

natu

re o

f In

vest

igati

ng O

ffic

er

��'

0"��?��&�!

<��W

�S

ignat

ure

!<��W

�

Wit

nes

s-2

Nam

e …

……

……

……

……

……

……

……

..

)-�!�X� ��

��

��

��

��

� ��

Sig

nat

ure

!<��W

�!<

��W

�!<

��W

�!<

��W

�R

an

k …

……

……

…..

No.

……

….…

……

…

��

��

��

��

��

��

��

�� /

�

I.I.F.-III/�� III

ARREST/ COURT SURRENDER FORM

0)�l��?0)�l��?0)�l��?0)�l��?/(��,��S�OR�(��,��S�OR�(��,��S�OR�(��,��S�OR� �� N�� N�� N�� N�� (Separate form for each accused)

��R�&��'05�9L��& �0,��',)�� R�&��'05�9L��& �0,��',)�� R�&��'05�9L��& �0,��',)�� R�&��'05�9L��& �0,��',)�� ****

�. District(+�,�*.……………..............P.S.(��*..…….................Year(-. *……..//..FIR No.(�/��/��/� *.……..……Date(��*........./……..

Alphanumeric code of the accused............... (Write A1 to A9 for the first 9 persons, B1 for 10th person & so on)

'05�9L��-N �� b��R�� !,&�m�H�6L�M��& �0,��#��&��m��B��-S�H�6L��& �0,��2@�#��A�@��!��&�'(��H�6L�M��& �0,�*

2. Date, Time and Place of arrest/surrender: Date��* .......………//////Time��*..........……G.D.No.�� /*……….//////

0)�l��?/OR� �� N��0�0��- ��:�

Place of arrest:�0)�l��?��<��* : P.S.��*///////////////………………..District�+�,�* ……………………………………………

�3. Name of the court (if surrendered): �(��,��OR�� N��!�**//.................................................................... �4. Acts and Sections�:�('0"0��- �"��)�:� //////////////////////////////////////////......................................................................... �5. Arrested and forwarded/ Arrested and released on bail or PR bond/ Arrested but released on anticipatory bail/ Arrested and remanded to

police custody/ Surrendered in court and bailed out/ Surrendered in court and sent to judicial custody/ Surrendered in court and remanded to

police custody.

(tick ' � ' applicable portion).

0)�l��&6.��/0)�l��[��9,�& ��!� ��/0)�l�� (�9�'0k��!��/

0)�l��[��90,��!��S�5&��/(��,��S�OR�� N�[��!�/(��,��S�OR�� N�[��(��0��

�!��S�5&��/(��,��S�OR�� N�[��90,��!��S�5&��|

�,�)��!<�&��‘ � ‘ ��0(!�,)��*�6. Particulars of the arrested person:�0)�l��H�6L��6--�N* :

(i) Name��*..........................................................................................................................................…////////////////////////////////

(ii) Father's / Husband's Name�6��/�0��*..../////////////////////////////////////////////////.....................////////////////////////////////

(iii) First Alias ��C��*.............................////////////.(iv) Second Alias��T�@��C��*...........................……../////////////////

(v) Nationality��E@��*..........................//////////////////.....(vi) (a) ��* Voter Id. card No.��!��^�� /*///……...////////

(b)�3* Passport No. ...................……………..//////////(c)�)* Date of issue ......////////////(d)�1* Place of issue../////..............

� � �� /� � � ��?��&��0�0��?��&��<��

(vii) Religion("� )......./////////////// ................................./////. (viii) Caste/Tribe(��0�/��0�).........................……///////////////////

(ix) SC/ST/OBC('�9B��0�/'�9/��0�/'(��6�IF&�-) )……………………………………………...///////////////////////////////////

(x) Occupation(H�-��).....................………………………………………………………………………..//////////////////////////////� � ��(xi) Permanent Address(<��:��*...........................////...…Distt�+�,�*.......///////////////.…… P.S��*......//////////////.........……

� �(xii) Present Address �-� ��*............................///..///Distt �+�,�*......///////////////..……P.S.��*...........……////////////////

� �7. Injuries, cause of injuries and physical condition of the arrested person (Indicate if medically examined) :

� 0)�l��H�6L��>��?��>�/��:��,)@�!��C��& ��N/��NM��6--�N:

� ��f��?��):�!��CV,&3��S*:

..................................................................................................................................................................................

.................................................................................................................................................................................

��1/3 -


8. The arrested person, after being informed of the grounds of arrest and his legal rights, was duly taken into custody�on…...........//////////////�

(date) at …///////////////….........(hours) at …..//////////////.......... (place). The following article(s) was/were found on physical search, conducted

on the person of the arrested person and was/were taken into possession, for which a receipt was given to the arrested person. If no article

found, `NIL’ may be indicated.

0)�l�� H�6L� �� C�� 0)�l��?� �� N� [�� C��& � ��@� '0"��M� �� 2��&� !9��

��//////////////////////////////��/////////////////////////////////<��//////////////……………��!��S�0,��)�� | 0)�l��H�6L��

��,�>@�,&�&��0�U�0,+3��)��+��&��=�&��S�,&��@��?�):�| ��9 I�5@��!? �� )��!��

‘�9 I��!? �9 I��!? �9 I��!? �9 I��!? ’��0,3��|

(1) .............................................................…… (2) ..............................................................……..

(Attach separate sheet, if required).�(��O-P��!�B��',)��7��R�@��S*

Necessary wearing apparels were left on the arrested person for the sake of human dignity and body protection.

� ��-@��)��>��?��2�-�!&�9�O-P��F&�0)�l��H�6L��& �>�?��!�&��)��|

The arrested person was cautioned to keep himself/ herself covered for purpose of identification.

0>��b��!&�9�'��&�O��`��3�&��& �0,��0)�l��H�6L��&��)��|

Intimation given to Shri/Smt. .....................................(relation) …........./////////////on (date)………………at (hrs.)………………

� \@/\@��@/�9 ��?� /////////////////////////////////////……..�� 2 "*///////////////////////…��*�////////��*/////……/��?�):|

9. Physical features, deformities and other details of the arrested person:

� 0)�l��H�6L��>��?��2��-�B�6-�� 0��- �'(��6--�N:-

Sex

0, )

Date/Year of

Birth

�(�0�0�/-.

Build

>��?��2��-�

Height

(cms.)

��&/�@/*

Complexion

� )

Identification Marks(s)

�!��& �0(!

1 2 3 4 5 6

Deformities/

Peculiarities

6-�� 0��/

6-0>67��

Teeth

��

Hair

2�,

Eyes

O3S

Habit (s)

O��S

Dress

Habit(s)

�!��-�

Language/

Dialect

5�.�/2�,@

PLACE OF

>�?��& ��!<�&��B�0�U�0,+3��0(!�

�;��!Z�?

Burn

mark

�,&�

!9��

��

Leuco-

derma

"-,�

��)

Mole

�<��

Scar

1�-

Tattoo

)9�&�!9��

��

7 8 9 10 11 12 13 14 15 16 17 18

� Other features, if any �'(��,WNB��:�!��*�//////////////////......................................................................................................….

�10.� Whether finger-prints taken :��')90,�M��& �0�>��0,��)�*� � Yes/No�!�/�!? *

�

11. Socio-economic profile of the arrested person :�0)�l��H�6L��+��- �O0� ��+<�0�*:

(a) Living Status: Living alone / Living with family / with associate in pucca house / hotel / hostel / katcha house / thatched house / slum /

homeless / harbourer.

��*��@-� <��:� '�& ,�/��-��!�/�!��)@��!��f�& �1��S/!��,/I�^�-��/�n��1�/Io��/p9K)@�pM�F?/2&1�/O0\� |�

- 2/3 -


(b)�3* Educational qualification(s) �>8+W��K��*..................................….(c) �)* Occupation �H�-��*/////............................../////////

�d)�1*��Income Group:�O��-) *�:

� �(i) Economically weaker section (Annual income below Rs. 25,000/-)

O0� ��_67��&��-) ��-�6. ��O��d/�X$BGGG/-��&��)

(ii) Lower income (Rs.25,001/- to Rs.50,000/-)

��0�U��O��d/�X$BGG#/-��&�d/�$GBGGG/-��*

(iii) Lower middle income (Rs. 50,001/- to Rs. 1,00,000/-)

��0�U��q��O��d/�$GBGG#/-��&�d/�#BGGBGGG/-��*(iv) Middle income (Rs.1,00,001/- to Rs.2,00,000/-)

��q��O��d/�#BGGBGG1/-��&�d/�XBGGBGGG/- ��*

(v) Upper middle income(Rs.2,00,001/- to Rs.3,00,000/-)

��Cn��q��O��d/�XBGGBGG#/-��&�d/�eBGGBGGG/-��*(vi) Upper income (Above Rs.3,00,000/-)

��Cn�O��d/�eBGGBGGG/-��&�'0"�)

12. Whether the arrested person, as per observation and known police records:

� ��F��,��- �J��90,�� & �O"��B�f��0)�l��H�6L :

(a)��* Is dangerous:� Yes/No (b)�3*� Previously jumped any bail Yes/No

3��!8�?� � � !�/�!? � ��- ��S��@��2�0��,��!8?�� !�/�!?

(c)�)* Is generally armed � Yes/No (d)�1*� Operates with accomplices Yes/No

� O��;��>h��3��!8?� � !�/�!? � ��!��0)�M�� !��>@,�!8? !�/�!?

(e)��o* Is known/listed criminal Yes/No (f)�*� Is recidivist Yes/No

� J��/��@2T�'��"@�!8? !�/�!? � ��'��"�H��@�!8?� � � ��!�/�!?

(g)�I* Is likely to jump bail � Yes/No (h)��* � If released on bail, likely to commit crime

� ��& ��;��2�0��,�&� � !�/�!? ��or threaten victims/witnesses. � Yes/No

� �� 5�-��!8?� � � � ��!��!��&��& �2��'��" ��&�� !�/�!?

� � � � � � ��@�F�M/)-�!M��"��&��U5�-��!8?

(i)(p* Is wanted in any other case ��@�'(��'��"��S�-� 0I��!8?* � Yes/No�!�/�!? *

( If Yes against item (b), (e) or (i), give case reference/Sections. Attach separate sheet, if required)

� � (��3BF�'�-��p��CD��!��!ZB��,�� 5 /"��Y ��CV,&3��S | ��O-P��!�B��

� � ',)��7��R�@��S )

13. Name and address of the witnesses ( At least one witness is necessary ) )-�!M��[��:��&��)-�!�'0�-�� !8

�1* Signature

!<��W�!<��W�!<��W�!<��W�

�2* Signature

� � � � � !<��W��

14. Signature or LTI of arrested person�0)�l��H�6L��& �!<��W��2��&�' )�a& ��0�>��*

Signature of Investigating Officer

��'0"��?��& �!<��W�Name .............................…………….……

r��Rank .....................................No. ..............

Place/<�� .........……........� � � � � �� /�

Date / ��..........…….......

��eeee/3��

I.I.F.-IV/�� IV

PROPERTY SEARCH & SEIZURE FORM

�U�6D��,�>@��- ��=�@�� U�6D��,�>@��- ��=�@�� U�6D��,�>@��- ��=�@�� U�6D��,�>@��- ��=�@�� (Search/Production/Recovery u/s 51/102/165 Cr.P.C……….. etc.)

�� !��"�� !��"�� !��"�� !��"��$#$#$#$#/102/165////////////////AR��& �'(�AR��& �'(�AR��& �'(�AR��& �'(�) ��,�>@) ��,�>@) ��,�>@) ��,�>@/�&>@�&>@�&>@�&>@/2��)@2��)@2��)@2��)@****

�. District(+�,�*...……...........PS(��*..….............Year(-. *……..//..FIR/GD No.(�/��/��//�� /*.……..…Date(��*..//......./…

2. Acts and Sections �'0"0��- �"��*B/////////////////…………………………………………………………………………………////�3. Nature of property Seized : Stolen/Unclaimed/Unlawful possession/Involved/Intestate.

� �=��U�6D��:��?/,�-��/'-8"��=��/� 0,4/0�- �@��

4. Property seized/ recovered: ��U�6D��=�/2��&��*(a)��* Date��*………………(b)�3*Time��*///…………….…////� �

(c) �)* Place�<��*//////////////////////////////////………………………………………………………………………//…………………….

(d) �1* Description of the place�<��6--�N*//////////////////////////////////………………………………………./…………………...

5. Person from whom seized /recovered �H�6L�+��&��=�/2��):*�:

Name��*/////////////////////……………………Father’s/Husband’s name�6��/�0��*/////////////////// ………………..//////////

Sex�0, )*///////////////////////////// ……………. /Age�O�9* .………….////////////./ //////Occupation�H�-��*//……………………...///

Address��*/////////////////////////////////////////………………………………………………………………….………………………..

��

Professional receiver of stolen property.�9��:�!9:��U�6D��H�-��0��4�� !8?* Yes/No�!�/�!? *� � �6. Witnesses()-�!)�:

(i) Name(��)……………….. ………………………Father’s/Husband’s name(6��/�0��)…………. ………………//……….

Age(O�9) …………………………….…………..Occupation (H�-��) …………………Address(��)….. ……………//…………

……………………………………………………………………………………………………………………………………/…….

………………………………………………………….……………………………………………………………………………….

(ii) Name(��)……………………………………….Father’s/Husband’s Name(6��/�0��)……..…………//////////…………

Age(O�9)……………………..……. …………..Occupation(H�-��)…. ……………………Address(��)…..…………………..

…………………………………………………………………………………………….……………………………………………

…………………………………………………………………………………………………………………………………………

7. Action taken/recommended for disposal of perishable property………………………….……………………………………………

� >@s��7�!��&�-�,@�-<�9��& �0�<��N�!&�9��):�� -�:/0��>

8. Action taken/recommended for keeping of valuable property ……………………….………………………………………………..

� ��V�-��U�6D��9�+W��3�&�!&�9��):�� -�:/0��>

9. Identification required.��f��0>��b��O-P��!8?* Yes/No��!�/�!? *� � � � � �

10. Details of properties seized/ recovered ( Use appropriate prescribed form(s) and attach).

� �=�/2��):��U�6D��6--�N��C��9L�0�"� �� )��R�@��S*

(1) …………………….………………………………………………………………………………………

(2) …………………….……………………………………………………………………………………….

(Attach separate sheet, if required)��O-P��!�B��',)��Q��R�@��S*

- 1/2 -

I.I.F.-IV/�� IV

11. Circumstances/grounds for seizure��=��&��+<�0��/O"��*:

12. The above mentioned properties were seized in accordance with the provisions of law in the presence of the above said witnesses/* and a copy

of the seizure form was given to the person/ the occupant of the place from whom seized.

C��9 L��U�6DB�i��>� ��)��)-�!M/*��C�+<�0��S��@��-"��M��& �'�9��=��):��=�@�� 0��

C��H�6L/<��& �0�-��@��?�):�+��&��U�6D��=��):�!8 |

13 The following properties were packed and/or sealed and the signature of the above said witnesses obtained thereon or on the body of the

property.

0�U�0,+3��-<�9Y ��)-�!M��C�+<�0��S��8��- /'�-��@,��)��8��M��'�-��U�6D��C��9 L�)-�!M��& �

!<��W��0,��)�|

Sl.

No.

�/� /

Property

�U�6DIndicate whether signature obtained on the packet or on the body of

the property

CV,&3��S��!<��W��8�& ��'�-��U�6D��4��)�|

1 2 3

��Specimen of the seal is given below

�@,��@&��!8�@,��@&��!8�@,��@&��!8�@,��@&��!8 | Signature of the person from whom seized (if present)

+��H�6L��&��U�6D��=��):B�C��& �!<��W� (��C�+<��!�*

Witness-1

)-�!�#

Signature ��……………………………………………...

!<��W� �� Signature of Investigating officer

� ��'0"��?��& �!<��W�

Witness-2 Name��* ………………………………………

)-�!�X� � �

Rank��* ………………….…No/�� /*.………...

� �� /�

Place�<��*…………………. Date��*//.. Signature� � � � � � �!<��W�

* In case the property is seized from such a place that no receipt is required to be given to anybody, this portion of the sentence should be struck off.

t��U�6D�u�&�<��&��=��):�!��!��@��&�&��O-P��!�B�-!��A��5�)��S�|

- 2/2 -

Att

ach

men

t to

Ite

m 1

0 o

f P

rop

erty

Sea

rch

& S

eizu

re F

orm

.

�U�

6D��

��,�>

@��-

��=�

@��

��

� b��

�U�

6D��

��,�>

@��-

��=�

@��

��

� b��

�U�

6D��

��,�>

@��-

��=�

@��

��

� b��

�U�

6D��

��,�>

@��-

��=�

@��

��

� b��#G

�#G

�#G

�#G

�� ,K�

�� ,K�

�� ,K�

�� ,K�

�

Det

ail

s of

Cou

nte

rfei

t C

urre

ncy

reco

ver

ed

/sei

zed

:

2��

�2�

��

2��

�2�

��/�=�

�=�

�=�

�=�

��):�

��,

@��9v��

��6--�

N��

��):�

��,

@��9v��

��6--�

N��

��):�

��,

@��9v��

��6--�

N��

��):�

��,

@��9v��

��6--�

N:

Dis

tric

t�+�

,�*

……

……

……

……

……

……

……

.P.S

. ��

��*

……

……

……

……

……

…. Y

ear�-.

*……

….…

.. F

IR N

o.��/��/��

/� /*

……

……

……

.Dat

e��

*……

……

……

...

Sl.

No.

�/�

/

Num

ber

of

pie

ces

��M��0�

f�M�� b��

Ser

ies

\� 3,��

��@�?�

*

Ser

ial

Num

ber

��

b��

Type

of

curr

ency

�9v��

��

��D

enom

inat

ion

' ��

��

�V�V

isib

le c

ounte

rfei

ting m

ark(s

)

�R�W��

�,@�0

(!

1

2

3

4

5

6

7

Wit

nes

s-1

)-�!�#

Sig

nat

ure

�

��

��

……

……

……

……

……

……

……

……

…..

. //////

!<��W

�

�

��

��

� S

ignat

ure

of

Inves

tigat

ing o

ffic

er

��

��

��'

0"��?��&�!

<��W

�

Wit

nes

s-2

��

��

�N

ame��

��*

……

……

……

……

……

……//

……

…

)-�!�X�

��

�

��

��

�R

ank��

�* …

……

……

……

.……

..N

o.�� /*

……

…..

.

��

Sig

nat

ure

!<��W

�

Att

ach

men

t to

It

em 1

0 o

f P

rop

erty

Sea

rch

& S

eizu

re F

orm

.

�U�

6D��

��,�>

@��-

��=�

@��

��

� b��

�U�

6D��

��,�>

@��-

��=�

@��

��

� b��

�U�

6D��

��,�>

@��-

��=�

@��

��

� b��

�U�

6D��

��,�>

@��-

��=�

@��

��

� b��#G

�#G

�#G

�#G

�� ,K�

�� ,K�

�� ,K�

�� ,K�

�

Det

ail

s of

Narc

oti

c d

ru

gs

recover

ed/s

eized

:

2��

�2�

��

2��

�2�

��/�=�

��):�

��[

.0"�M��6--�

N�=�

��):�

��[

.0"�M��6--�

N�=�

��):�

��[

.0"�M��6--�

N�=�

��):�

��[

.0"�M��6--�

N:

Dis

tric

t�+�

,�*

……

……

……

……

……

……

……

.P.S

. ��

��*

……

……

……

……

……

…. Y

ear�-.

*……

….…

.. F

IR N

o.��/��/��

/� /*

……

……

……

.Dat

e��

*……

……

……

...

Sl.

No.

�/�

/

Nam

e of

dru

g

<-��[

.0"��

��

No.

of

pac

ket

s

�8��M��

�� b��

Wei

ght

(K/g/�

gm

s.)

-j�

��

/k�/�k��*

Des

crip

tion o

f th

e pac

kin

g a

nd m

arkin

g,

if a

ny

�8�� )

/��

w)��

��6--�

NB��

�:�!

��

Met

hod o

f co

nce

alm

ent

0I��&��

��?��

Est

imat

ed v

alue

(in R

s.)

'�9��0�

��

�V��d/�S*

1

2

3

4

5

6

7

Whet

her

the

noti

ce u

nder

Sec

tion 5

0 o

f N

DP

S A

ct s

erved

on t

he

per

son ?

�

��

Yes

/No

f��H�

6L��

��

/�?/�

@/��/�'0"

0��

��"��$G

��&�' �) ��

��

��?��

��)��

?��

�!�/�!?

Whet

her

the

Lab

ora

tory

anal

ysi

s fo

rm f

ille

d o

n t

he

spot

?

�

�Y

es/N

o

f��;�&��

��)>�,��6-x&.N

�� 5

��)

��

?��

��

��

!�/�!?

Sig

natu

re o

f M

agis

trate

(w

hen

pre

sen

t) /

Gazett

ed

Off

icer

� ��

Sig

natu

re o

f I

nvest

igati

ng O

ffic

er

Wit

ness

-1� ��

� ��

� ��

��

��

��

��

��

��(�

��"@>

�(�

��"@>

�(�

��"@>

�(�

��"@>

�� 2�

C�+<��!

M�2�

C�+<��!

M�2�

C�+<��!

M�2�

C�+<��!

M* ***/��

�6^�

�'0"

��?��&�!

<��W

��6^�

�'0"

��?��&�!

<��W

��6^�

�'0"

��?��&�!

<��W

��6^�

�'0"

��?��&�!

<��W

��

� ��

��'

0"��?��&�!

<��W

��'

0"��?��&�!

<��W

��'

0"��?��&�!

<��W

��'

0"��?��&�!

<��W

�

)-�!

)-�!

)-�!

)-�!� ��

# ###

Nam

e��*

……

……

……

……

……

……

…..

N

ame��*

……

……

.……

……

……

……

...

��

��

��

��

��

��

��

��

�S

ignat

ure

!<��W

�!<

��W

�!<

��W

�!<

��W

�

Court�(��,�*/

……

……

……

……

……

…..

R

ank ��

*……

……

……

...

No.�� /*

……

….

Wit

ness

-2

)-�!

)-�!

)-�!

)-�!� ��

X XXX

Sig

nat

ure

!<��W

�!<

��W

�!<

��W

�!<

��W

�

� � � � � I.I.F.-V/�� V

FINAL FORM/ REPORT

' 0��' 0��' 0��' 0�� /�� (Under Section 173 Cr.P.C.)

�� !��"�� !��"�� !��"�� !��"��####ce�ce�ce�ce��& �'(�) ��& �'(�) ��& �'(�) ��& �'(�) �****

IN THE COURT OF ..................................................................................

� /////////////////////////////////////////////�& �(��,��S� � ��

1. District�+�,�* ......................……P.S.��* .............………Year�-. *.………….FIR No.��/��/��/� /*.......... Date��* ……….//�2. Final Report / Charge Sheet No/��' 0�� /O��^�� b��.*/.................................................…3. Date��*//……///////////� � � � � � � �4. (i) Act�'0"0��*.............................................................…………. Sections�"��*/// ........................................................... � �

(ii) Act�'0"0��* .........................................................….…………Sections�"��*/// .......................................................…

(iii) Act�'0"0��* ............................................................…………. Sections�"��*// ........................................................…

(iv) Other Acts & Sections�'(��'0"0��- �"��*....................................................................................…//////////////////////////////� �5. Type of Final Form/Report: Charge Sheet / Not charge sheeted for want of evidence / FR True, Undetected / FR True, Untraced / FR True,

offence abated / FR Unoccurred .


' 0�� /�� :-�O��^��+3,��/��y��'5�-��& ��N�O��^��+3,��!? ��/' 0�� !?-��!? �

,)�/' 0�� !?�0�,��!? ��!?/' 0�� !?�'��"��)��/' 0�� '1��

� �,�)��!<�&��‘�’ ��0(!�,)��*

6. If FR Unoccurred: False/Mistake of Fact/Mistake of law/Non cognisable /Civil nature.


� ��' 0�� '1��:�p�az/�{�M�� 9̂��/��@� 9̂��/'� J&�/�?-��@

� �,�)��!<�&��‘�’ ��0(!�,)��*

7. If Charge sheet : � Original / Supplementary.


� ��O��^��+3,�� :� ��,/'�9��

� �,�)��!<�&��‘�’ ��0(!�,)��*

8. Name of I/O/ ��'0"��?��*. ...............................…………Rank��* ....................................……No.�� /* ..............…..

(at the time of charge sheet) �O��^��+3,��&��*

9. (a)��* Name of complainant / informant �0>�� /A6D,��&�&�-�,&��* ....................................................................….

� �(b)�3* Father's / Husband's name�6��/�0��*.................................................................................…..////////////////////////

� �10. Details of Properties/Articles/Documents recovered/seized during investigation and relied upon (separate list can be attached, if necessary).

��& ��;��2��/�=��U�6D/-<�9/�<��-&��6--�N�+�(!S�O"��2��)��!�B��O-P��'�9��',)��@�� ,K��S*:-

Sl.

No.

� /� /

Property description

�U�6D��6--�N

Estimated value

(in Rs.)

'�9��0��V��

�d/�S*

P.S. Property Register

No.

��U�6D��+�<��

� /

From whom/ where

recovered or seized

�!�/��&��=��'�-��

2��):�|

Disposal

0��N

1 2 3 4 5 6

- 1/4 -

I.I.F.-V/�� V

11. Particulars of accused persons charge-sheeted: (Use separate sheet for each accused)

� O��^��+3,�'05�9LM��6--�N�:��R�&��'05�9L��& �0,��',)��Q��R�@��S*

Sl. No./�� b��////////// …….

(i) Name��* ............................................///.Whether verified (f��R��6��!8?)..................................…/////////////////////////////////////� � � � � � � �(ii) Father's/Husband's name�6��/�0��* ....//////////////.....................……(iii) Date/ Year of birth ��(�0�0�/-. *...…………////////

(iv) Sex �0, )* ....………..///////////// (v) Nationality ��6E��*................//////////(vi) Passport No.�� b��/////////////////…………./

Date of Issue��?��&��0�0�* ……………/////// Place of Issue ��?��&��<��.......//////////////.……………………………//

(vii) Religion�"� * .........// (viii) Whether SC/ST/OBC�'�9/��0�/'�9/��0�/'(��6�IF&�-) *.……..///………………………………….

(ix) Occupation�H�-��*…..………………………………………………………………………………………………………………………

� � � � �� (x) Address��*////////////////////////////////////////.................................................................................………………………………………//

.................................................................///////////////////////////////////////.Whether verified�f��R��6��!Z?*//.................................…./

(xi) Provisional criminal No.�'�+(��'��"@�� b��*//////.............................……………………………………………………..////////////�

(xii) Regular Criminal No. (if known)�0��0��'��"@�� b��J��!�*.............……………………………………………………….

(xiii) Date of arrest�0)�l��?��0�0�* /….../////……………………………………………………………………………………………….

� � � � ��(xiv) Date of release on bail��!�:��0�0�* ............../////////////////////////////////////////////////////////////////////////////////////////////////�

(xv) � Date on which forwarded to court((��,��5&��&��0�0�)//////////////////////////////////////////////////////////////////////////////////////////////� � � � � ��(xvi) Under Acts & Sections�'0"0��- �"��* :///////////......………………………………………/////////////////////////////////////////////////////

(xvii) Details of bailers / sureties: ��0��M��=�;��*:

Name��* ……………………………..//////�Father’s/Husband’s name�6��/�0��* ………////……………………………/////� � � � � �

Occupation�H�-��* .................................... Address��*///////////////////////// .................................................................................……

� Identification��!��* …………/////////////////////////////////………………………………………………………………………………..

� �(xviii) Previous convictions with case references��,&��& �� 5 ��!�B��!,&�!9:��j��6--�N*.......................................................…...…

� � � �.........................................................................................................................................................….….…/////////////////////////////////////

.....................................................................................................................................................…........…../////////////////////////////////////

(xix) Status of the accused:

Forwarded / Bailed by police / Bailed by court / Judicial custody / Absconding / Proclaimed offender


� '05�9L��+<�0� :

� �&>��)��/�90,��T��j��/(��,��T��/(��0��!��S/��/1�6.��'��"@

� �,�)��!<�&��‘�’��0(!�,)��*

��XXXX/%�%�%�%��

I.I.F.-V/�� V

12. Particulars of accused persons - not charge sheeted (suspect) : (Use separate sheet for each suspect)

� O��^��+3,��)�� K"*�'05�9LM��6--�N��R�&�� K"��& �0,��',)��Q��R�@��S*

Sl. No.�� b��*///// ……

(i) Name��* ..........................................................…………Whether verified(f��R��6��!8?).........................…………

� � � � � � �(ii) Father's/Husband's Name(6��/�0��) .............................(iii) Date/Year of birth(�(�0�0�/-. ) .….......................…

� �

(iv) Sex(0, )* .............. (v) Nationality��E@��* ............................ (vi) Passport No.�� /*..........................……..//� � � � ��

Date of Issue��?��&��0�0�*……///…………………...////// Place of Issue��?��&��<��*.............................. � � � � � �

(vii) Religion�"� * ....///////////////////(viii) Whether SC/ST/OBC�'�9/��0�/'�9/��0�/'(��6�IF&�-) ......…//////////////////////

(ix) Occupation�H�-��* .......//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////� � � � � � ��

(x) Address��*//////////////................................................................................................………………////////////////////////////

………………………………///////////////Whether verified�f��R��6��!8?*…………/////////////////////……………….///

(xi) Provisional criminal No.�'�+(��'��"@�� b�� *.......................……………..//////////////////////////////////////////////////////

(xii) Suspicion approved :�� &!�'�9��* � Yes/No�!�/�!? *� � �(xiii) Status of the accused (suspect): �'05�9L�� K"*��+<�0�*:

Bailed by police/Bailed by court/ Judicial custody/Not arrested


� � �90,��T��/(��,��T��/(��0��!��S/0)�l��!? ��

� � �,�)��!<�&��‘�’��0(!�,)��*

(xiv) Under Acts & Sections�'0"0��- �"��*.................................................................………………//////////////////////

(xv) Any Special remarks including reasons for not charge sheeting ..................................................……/////////////////////////////

� � O��^��+3,��&��& ��N��!��:�6->&.�'|�96L�:

............................................................................................................................................................../////////////////////////

..............................................................................................................................................................////////////////////////

..............................................................................................................................................................///////////////////////

�� 3/4 -

I/ ///I/ ///

F.-

V/��

��

��

��

��

��

��

��

��

��

��

�� V

13.

Par

ticu

lars

of

wit

nes

ses

to b

e ex

amin

ed:��I

��I

��

��&�-

�,&�)

-�!M��

��6--�

N*:

� Sl.

No.

�/�

/

Nam

e

��

Fat

her

's/H

usb

and's

nam

e

6��/�

0��

��

Dat

e/Y

ear

of

bir

th

�(�

0�0�

/-.

Occ

upat

ion

H�-�

��

Addre

ss

��

Type

of

evid

ence

to b

e te

nder

ed

�<�9��

��&�-

�,&��

�y��

��

��

1

2

3

4

5

6

7

14.

If F/R

. is

fal

se,

indic

ate

acti

on t

aken

or

pro

pose

d t

o b

e ta

ken

u/s

182/2

11 I

.P.C

...

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

......

..…

….

��'

+(��

�� p

�az�!8��

��5�/�

/� /��"��

182/2

11��

&�'(�

) ��

��):�

'�-��

<��6-

��

�� -�:��

��6--�

N�:

15.

Res

ult

of

Lab

ora

tory

an

alysi

s ��

��)>�,��S��

)��

6-x&.N

��N

��*:

...

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

..

� 16.

Bri

ef

fact

s of

the

case

(A

dd s

epar

ate

shee

t, i

f nec

essa

ry)

....

....

....

....

....

....

....

....

....

....

......

....

....

....

...…

……

……

……

……

……

……

……

……

……

……

……

……

……

……///

��,&��

&�� 2 0"��

+W4��

{�:��

��O

-P��!

�B��',)��

�Q��R�

@��S*

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

….

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

.…..

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

...…

17.

Ref

er N

oti

ce s

erved

:��?��

��

�*

�Y

es/N

o�!�/�

!? *

Dat

e��

*...

....

....

....

......

....

.

(Ack

now

ledgem

ent

to b

e pla

ced)

��

�-�@��R�

@��S*��

��

��

18.

Des

pat

ched

on��

&.N��

��0�0�

* ..

....

....

....

....

....

....

....

……

….//////

�19.

No.

of

encl

osu

res:��

,K�

�M�� b��*

: …

……

……

……

……

20.

Lis

t of

encl

osu

res

: A

s an

nex

ed�� ,K�

�M��@*

:

��

��

��

Forw

arded

by O

ffic

er i

n c

har

ge

S

ignat

ure

of

Inves

tigat

ing O

ffic

er

��

��

�5��?�'0"

��?�T��'

k&6.�

��

subm

itti

ng f

inal

rep

ort

/char

ge

shee

t��

��

��

'

0��

�� /O

��

�^��

��

&�-�,&

��'

0"��?��&�!

<��W

��

��

��

Nam

e��*

....

....

......

....

....

....

....

....

....

....

....

N

ame��*

....

....

....

......

....

....

....

....

....

..…

....

..

��

��

��

Ran

k��

�* .

....

....

....

....

...N

o.�� /*

...

....

....

....

R

ank��

�* .

....

....

....

....

......

....

No.�� /*

...

..…

..

� �� % %%%/%� %�%�%�

� ��

��

I.I.

F.-

VI/��

��

��

��

��

��

��

��

��

��

��

��

�� V

I

CO

UR

T D

ISP

OS

AL

FO

RM

(��,

��0�<�

��N��

��

(��,

��0�<�

��N��

��

(��,

��0�<�

��N��

��

(��,

��0�<�

��N��

��

IN T

HE

CO

UR

T O

F .

......

....

....

....

....

....

....

....

....

....

....

....

......

....

..

��

��

��

�///////////////////////////////////////////////////////////�&�(

��,��

S

1.

Dis

tric

t(+�

,�*

....

...…

…/////

P.S

.��*/////////////////////

Yea

r�-.

* ….///////F

IR /

Pro

ceed

ing N

o.��/��/��

//�� -�:�� /*

.....…

……

..D

ate��

*......…

…..2. C

har

ge

shee

t No.�O

��^

�� /*

.......... D

ate(��

*..…

…///

� 3.

Ju

dic

ial

file

/Court

cas

e N

o.��(

��0�

��

�:,

/��

&��

/* .

....

....

....

....

....

.……

……

…

4.

Act

s &

Sec

tions

of

Law

��

&�'0"

0��

- �"��*

…..

....

....

....

......

....

....

....

....

....

....

.///////////////////////////////

..

��

��

��

5.

Dat

e of

fram

ing c

har

ge

in c

ourt

...

....

....

....

....

....

....

....

./////////////////////////////////////////…

6.

Type

of

case

……

…./////////////////////////////////.7

. D

ate

of

judgem

ent

./////////////////////////////////////////.

....

....

....

....

.//

�(�

��,��

S�O��

��6-�

��

�}&��

��&*��0�0�

��

��

&��

��

��

��

��(

��,��T

��

)��

0�N ��

��0�0�

8.

N

ame(

s) o

f t

he

pro

secu

tor�'0"

-L��*�

...

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

.////////////////////////////////////////////////////////////////////////////////////////////////////

� 9.

Det

ails

of

court

dis

posa

l in

res

pec

t of

the

adult

acc

use

d p

erso

ns

:

�-�

<��'

05�9LM��&��

2 "��

S�(��,��0�<�

��N��

��6--�

N:

Sl.

No.

�/

� G

Nam

e of

the

accu

sed

'05

�9L��

��

Pro

vis

ional

crim

inal

num

ber

'�+(��

'��

�"@�� b��

Reg

ula

r

crim

inal

num

ber

0��0�

��

'��

�"@�� b��

Type

of

dis

posa

l

0�<�

��N��

��

��

Act

s &

Sec

tions

of

law

under

whic

h c

onvic

ted

��

&�'0"

0��

- �

"��+��&�'

(�) ��

0�~��.�

��62

�

Type

of

punis

hm

ent

�9��:�)

:��j�

Per

iod

of

punis

hm

ent

�j��

'-0"

Am

ount

of

Fin

e

(in R

s.)

�9�� &��

��

��0>

��d/�S*

Per

iod o

f

Bond

�9,�&��

��

'-0"

Am

ount

of

Bond

(in R

s.)

�9,�&��

��

��0>

�d/�

S*

Fin

ger

pri

nts

tak

en

Yes

/No

i ),@�0

(!�

0,��

)��

!�/�!?

1

2

3

4

5

6

7

8

9

10

11

12

-

� �� 1/2� ��

��

��

��

��

��

��

��

��

��

��

��

��

-��

10.

Det

ail

s of

Cou

rt d

isp

osa

l in

res

pec

t of

Ju

ven

iles

:

��>��'

��0"

�M��&��

2 "��

S�'�@,��

&��N

��

��6--�

N

Sl.

No.

�/�

/

Nam

e of

the

Acc

use

d

'05

�9L��

��

Pro

vis

ional

crim

inal

num

ber

'�+(��

'��

�"@�

� b��

Reg

ula

r

crim

inal

num

ber

0��0�

��

'��

�"@�

� b��

Type

of

dis

posa

l

0�<�

��N�

��

��

Act

s &

Sec

tions

of

law

under

whic

h c

onvic

ted

��

&�'0"

0��

�- �"

��+��&�

'(�

) ��0�T�

�.�

��62

�

Type

of

punis

h-

men

t

�9��:�)

:�

�j�

Per

iod o

f

det

enti

on/

care

r��2

�?/

�&3�&3

��

'-0"

Am

ount

of

fine

(in R

s.)

�9�� &��

��

��0>

�

�d/�

S*

Nam

e &

Addre

ss o

f th

e S

pec

ial

hom

e/

Juven

ile

hom

e/ O

bse

rvat

ion h

ouse

to w

hic

h

sent

+��6->

&.�)�!/��

>��)

�!/� �&W

N�)

�!��S�

5&��)��C�

��-

��

Fin

ger

pri

nts

taken

Yes

/No

i),@�

0(!

�

0,�&�)

��

!�/�!?

1

2

3

4

5

6

7

8

9

10

11

11.

Rea

sons

of

Acq

uit

tal��.�

96L��

��N*

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

.///////////////////////////////////////////////////////////////////////////////////////////////

12.

Oth

er c

om

men

ts /

str

ictu

res

pas

sed b

y t

he

court�(��,��T

��?�'(�

��o

�N@/O

,��*

13.

Appea

l pre

ferr

ed('

�@,��

��

@!)

Yes

/ N

o�!�/�

!? *

-

By S

tate

/ B

y a

ccu

sed /

By c

om

pla

inan

t��

�T��/'

05�9L�T

��/0>�� T��*

��

��

��

��

��

Sig

nat

ure

of

the

P.P

./A

.P.P

. pre

par

ing t

he

form

��

8��

��&�-

�,&��

@/�@//�/�@/�@/�

�&�!

<��W

�

�N

ame(��*/////////////////////…

……

……

..…

�D

ate��

* ..

....

....

....

......

....

....

……

…////…

- 2/2

-

�

I.I.

F.-

VII

/��

��

��

��

��

��

��

��

��

��

��

�� V

II

RE

SU

LT

OF

AP

PE

AL

FO

RM

'�@,��

��'�@,��

��'�@,��

��'�@,��

��N

��

��

��N

��

��

��N

��

��

��N

��

��

�IN

TH

E C

OU

RT

OF

...

....

....

....

....

....

....

....

....

....

....

....

....

....

....

....

..

��

��

��////////////////////////////////////////////////////////////�&�(�

��,��

S

1.

Dis

tric

t�+�

,�*///////////////////////..

......

....

....

....

....

.P.S

.��*///////// .

……

……

…..

Yea

r�-.

*///

...

....

....

.…..

FIR

/ P

roce

edin

g

No.��/��/��

//�� -�:��

/* .

....

....

....

..///////

.Dat

e��

*//////////////////////.

....

......

....

….

2.

Char

ge

shee

t N

o.�O

��

�^��

b��*

..

....

....

....

....

....

....

....

. …

……

……

……

……

..D

ate��

*//////////////////////////////////////////////////////////////////////////////////////////

…

……

……

....

....

....

....

....

....

...…

……

……

3.

Jud

icia

l f

ile/

Court

cas

e N

o.�(�

�0��

�:,

/��

&��

/*..

....

....

....

....

....

....

....

....

....

....

....

....

....

....

...…

……

……

……

……

……

……

……

.……

./////////////////////////////////////////////////////////////////////////////////////

�

4.

Appel

lant

par

ty /�'

�@,��'

�@,��

��&�-

�,�*

��

Sta

te /

Acc

use

d /

Com

pla

inan

t ��

/'05

�9L

/0>�� *

5.

Appea

l N

o.�'�@,��

/* .

……

…////…

……

....

....

....

....

....

....

....

....

....

..…

……

…./////

.6.

Dat

e of

appea

l�'�@,��

��0�0�

*////////////////////////////////////////////////////////////////////////////////////////////////////…

……

//�

��

��

��

��

7.

Dat

e of

judgem

ent�(�

��,��T

��

)��

0�N ��

��0�0�

*�..

....

....

....

....

....

....

....

......

....

....

....

....

....

....

....

....

....

....

....

……

……

……

……

……

……

……///////////////////////////////////////////////////////////////////////////

� 8.

Part

icu

lars

of

the r

esu

lts

of

ap

pea

l in

res

pec

t of

the a

du

lt a

ccu

sed

pers

on

s :

�-�

<��'

05�9LM��&��

2 "��

S�'�@,��

&��N

��

��6--�

N-�

<��'

05�9LM��&��

2 "��

S�'�@,��

&��N

��

��6--�

N-�

<��'

05�9LM��&��

2 "��

S�'�@,��

&��N

��

��6--�

N-�

<��'

05�9LM��&��

2 "��

S�'�@,��

&��N

��

��6--�

N:

Sl.

No.

�/�

/

Nam

e of

the

accu

sed

'05

�9L��

��

Pro

vis

ional

crim

inal

num

ber

'�+(��

'��

�"@�� b��

Reg

ula

r cr

imin

al

num

ber

0��0�

��'

��"@�

� b��

Act

s &

Sec

tions

of

law

under

whic

h c

onvic

ted

��

&�'0"

0��

- �"��

+��&�'

(�) ��0�~��.�

��62

�

Res

ult

of

appea

l

'�@,��

��

��N

��

Type

of

punis

hm

ent

�9��:�)

:�

�j�

Per

iod o

f

punis

hm

ent

�j��'-0"

Am

ount

of

fine

(in R

s.)

�9�� &��

��0>

�

�d/�

S*

Per

iod o

f

bond

�9,�&��

��

'-0"

Am

ount

of

bond

(in R

s.)

�9,�&��

��0>

�

�d/�

S*

1

2

3

4

5

6

7

8

9

10

11

The

colu

mns

show

ing "

Act

s &

Sec

tions

of

Law

" onw

ard s

hould

be

fill

ed u

p o

nly

in c

ase

ther

e is

chan

ge

in p

unis

hm

ent

in c

ase

of

convic

tion o

r w

hen

acq

uit

tal

is s

et a

side,

both

in r

espec

t of

adult

s an

d j

uven

iles

.

-�<�

�[��

>��'

��0"

�M��&�2

��&��

SB�‘�

��

&�'0"

0��

- �"��+��&�'

(�) ��0�~��.�

��62

��

&�'0"

0��

- �"��+��&�'

(�) ��0�~��.�

��62

��

&�'0"

0��

- �"��+��&�'

(�) ��0�~��.�

��62

��

&�'0"

0��

- �"��+��&�'

(�) ��0�~��.�

��62

�’� ��&�O

)&�-

�,&��

�,�M��SB��5@�5�?��

��

2��.0��T��j�*��

S��-�

��!

��'�-��

2�

��.�

9L��!

�:*��T

��?�)

:�!��|

- 1/2

-

� ��

I.I.

F.-

VII

/��

��

��

��

��

��

��

��

��

��

��

�� V

II

9.

Part

icu

lars

of

the r

esu

lts

of

ap

pea

l in

res

pec

t of

Ju

ven

iles

:

��>��'

��0"

�M��&��

2 "��

S�'�@,��

&��N

��

��6--�

N��

>��'

��0"

�M��&��

2 "��

S�'�@,��

&��N

��

��6--�

N��

>��'

��0"

�M��&��

2 "��

S�'�@,��

&��N

��

��6--�

N��

>��'

��0"

�M��&��

2 "��

S�'�@,��

&��N

��

��6--�

N:

Sl.

No.

�/�

/

Nam

e of

the

accu

sed

'05

�9L��

��

Pro

vis

ional

crim

inal

num

ber

'�+(��

'��

�"@�� b��

Reg

ula

r

crim

inal

num

ber

0��0�

��

'��

�"@�

� b��

Act

s &

Sec

tions

of

law

under

whic

h c

onvic

ted

��

&�'0"

0��

- �

"��+��&�'

(�) ��

0�~��.�

��62

�

Res

ult

of

appea

l

'�@,��

��

��N

��

Type

of

punis

hm

ent

�9��:�)

:�

�j�

Per

iod o

f

det

enti

on/

care

�j�2

�?/

�&3�&3

��

'-0"

Am

ount

of

fine

(in R

s.)

�9�� &��

��0>

�

�d/�

S*

Nam

e &

addre

ss o

f th

e S

pec

ial

hom

e/Ju

ven

ile

hom

e/O

bse

rvat

ion h

ouse

to

whic

h s

ent

+��6->

&.�)�!/��

>��)

�!/� �&W

N�)

�!��S�

5&��)��C�

��-

��

1

2

3

4

5

6

7

8

9

10

10.

Any n

ota

ble

obse

rvat

ions

of

the

Appel

late

court

on t

he

Inves

tigat

ion /

Pro

secu

tion /

Low

er c

ourt

s ��

�/'

05��

�/0�

,&�(

��,��

��'�@,@�(�

��,��T

��:�C

V,&3�@��'

|�96L

* :

: 11.

Oth

er c

om

men

ts /

str

ictu

res

pas

sed b

y t

he

court

�(�

��,��T

��):�

'(�

��o

�N@/O

,��*�:

12.

Rem

arks,

par

ticu

larl

y i

n r

egar

d t

o f

urt

her

appea

l, i

f an

y �3��;��

��9�

:��):�

'�@,��

&�2��&��S�'

|�96L

B��

�:�!

��*�:

Sig

nat

ure

of

the

P.P

./A

.P.P

. pre

par

ing t

he

form

��

8��

��&�-�,&��@/�

@//�/�@/�@/�

&�!<�

�W�

��N

ame��

�* …

……

……

……

……

……

…..

��D

ate��

*//.

....

....

....

....

....

.……

……

…..

�

- 2/2

-

COMBINED INPUT FORM FOR WANTED/MISSING/KIDNAPPED/DESERTER FROM

ARMED FORCES ETC/ESCAPEE/UNIDENTIFIED PERSON/DEAD BODY

'�&+W�'�&+W�'�&+W�'�&+W��3��!9O3��!9O3��!9O3��!9O��'�!��'�!��'�!��'�!��'05R��'05R��'05R��'05R��'J��H�6L'J��H�6L'J��H�6L'J��H�6L��H��H��H��H�6L6L6L6L��>-��& �0,�&�0�,��9,�� >-��& �0,�&�0�,��9,�� >-��& �0,�&�0�,��9,�� >-��& �0,�&�0�,��9,��

1. TYPE OF PERSON : (Circle one)�H�6L��*:�)�,��*

Missing/Kidnapped/Deserter�3��!9O��'05R��*

Wanted/Escapee/Arrested�'�&+W��0)�l��*

Un-Id. Person/Un-Id Body�'J��H�6L�'J��>-*

2. District�+�,�*………………………/////P.S.(��)……………….……FIR./G.D.No.(�/��/��/�� -�:�� /*///////…………�Date�� *…….….…/////

3. ACTS & SECTIONS�'0"0��[��"��*:

(i) Act�'0"0��*......................................…….///////////// Sections�"��*//////////////////////////////////////////////////////////////////////////////////////

(ii) Act�'0"0��*////////////................................................Sections�"��*////////////////////................................................................….//////////

(iii) Act�'0"0��*.///////////..........................................…..Sections�"��*///////////////////.................................................................…//////////

4. @ Name��* :///……/////////////////////////////////………………………………………………………………………………………………../

5. @ Alias(s)�C��* ://///////////////////////////////…/………………………………………………………………………………………………/

6. @ Father’s/Husband’s Name�6��0��* ://///////////////////////////////……………………………………………………………….///

7. Sex�0, )*: (M/F)��!,��9d.* :…………………………/////////////////////////�8. Year of Birth��(��0�0�* ://///////////…………………../////////////

9. Height�i�:*/////////// ……..:……///////Cms��&/0�/*� 10. Build�2��-�* :…////////////////…/////////…………..�11. Complextion�� )*:/………….

12. Colour of eyes�O 3�� ) ):�……………////////////////////………………….�13. Colour of Hair(2�,�� )) :…………….…………………/…

14. Deformity type(6-�� 0��)�……………………………………………………Location(<��) :/……….……….…………………………….

15. Identification marks(�!��0�):…………………..…………………………/�……Location(<��) :………….…………………………….//////////

16. @ Address(��) :……………….…………………………………………………………………………………………………..……………

Locality(<��)://……………………………………..………………………………..City(>!�) :/……………………………………………………

Distt(+�,�):…………………………….………………………………………………P.S.(��) :…………………………………………………...

______________________________________________________________________________________________________________________________

(FOR MISSING/KIDNAPPED/DESERTER/ESCAPEE/UN-ID PERSON/DEAD BODY ONLY)

�3��!9O�'�!��'05R��'J��>-�0�,��& �0,�&*

17. Clothes worn(�!�&��&) :…………………………….………………………………………………………………………………………………/

18. Date : Missing/Kidnapped/U. Dead Body Found/Escaped/Deserted :……………………………..…………………………………………………..

� �� :�3��!9O�'�!��'J��>-�0�,��'05R��

@ NOT APPLICABLE FOR UN-IDENTIFIED PERSON/DEAD BODY.

@�'J��H�6L��>-��& �0,�&�,�)��!?

MISCELLANEOUS DETAILS FORM��6-6-"�6--�N�� 6-6-"�6--�N�� 6-6-"�6--�N�� 6-6-"�6--�N��

(DETAILS OF ASSOCIATE OF TERRORIST)��O� �-��?�� 2 "��& �6--�NO� �-��?�� 2 "��& �6--�NO� �-��?�� 2 "��& �6--�NO� �-��?�� 2 "��& �6--�N****

1. Distt�+�,�*//….………//////////////PS/��* ….……////////////////Year�-. * ..……//////////FIR No/��/��/��/� /* …..…////� Date��* …….…………..

Alphanumeric code of the Accused�'05��)@��-N ��* ……………………………�As per the Arrest Memo)��0)�l��?��&��& �'�9��*////////� � � � � � � � �2. Name��*//////////////////////////////////////////////………………………………………………………..…………………….………………………………..

3. Father’s/Husband’s Name�6��0��* ////////////////////////////////////////////…………………………………………………………………………/

4. Sex�0, )* ……////////////////////////////////////////////////////////////………………………////////5. �Date of Birth��(��0�0�*/////………………………….. /

6. Date Bail jumped��&��?*…………………………………………………….…….……. ……………////////////////////////////////////////////////////

7. Actual date of release�0��9 L��&��-�<�6-��0�0�*……///////////////////////////////////////////……………………………………………………………

8. Associate Details�� 2 0"��& �6--�N*:

1. (i) Name��*/////////////////////////////////………………..……………………………………..………………………………………..

(ii) Father’s/Husband’s Name�6��0��* ……………………..……….. ……..…………………/////////////////////////////////

(iii) Type of association�� 2 "��* ………………… (Relative, Friend, Partner etc.)��P�&��B0�^B5�)@��BAR��*/////////////� � � � � � � � � �� (iv) Address��*// ………………………………//////////// Locality�<��*/////////// ……….……….………….……………………

� � � City�>!�* ………………………………………//////////Distt �+�,�*…….………….…/…P/S/��* //…………….…………

2. (i) Name��*………………………………………………………………………………………………. //////////////////////////////

(ii) Father’s/Husband’s Name�6��0��*////////////////////////////// …………………………………………………………

(iii) Type of association�� 2 "�� *……………….. (Relative, Friend, Partner etc.)��P�&��B0�^B5�)@��BAR��*//////////� � � � � � � � � �� (iv) Address��* ………………………………////////////// Locality �<��*////////……….……….………….……………………

� City ��*////////……………………………………… Distt �+�,�*…….………….…////P/S/��* …………….…………

�

NOTE: Please use additional sheets in case of more associates.��o�N@:-�'0"�� 2 "M��& �0,��'0��L��Q��R�@��S�

Signature of the Investigation Officer:

'�9� "�� '0"��?��& �!<��W�

Name��*: ……………………………

Rank��* : …………………………

Number, if any ………………………...

� b��B��:

Place�<��*: ………………………….. � Date��* …………………………..

ADDITIONAL TERRORIST DETAILS��'0��L�O� �-��?�6--�N�� '0��L�O� �-��?�6--�N�� '0��L�O� �-��?�6--�N�� '0��L�O� �-��?�6--�N��

1. Distt/�+�,�*……………….…///�P/S/��* ……………………/Year�-. *………….... FIR No/��/��/��/� /* ………… Date��* …………..…….

Alphanumeric code of the Accused�'05��)@��-N ��*…………………….….. (As per the Arrest Memo)��0)�l��?��&��& �'�9��*//////////� � � � � � � � �2. Name��*//////////////////////////////////////////………………………………………………………………………………………..……………..………..

3. Father’s/Husband’s Name�6��0��* …………………………..………………………………………………////////////////////////////////////////

4. State Dossier No/��+�� /* ………………………………………………///////5. NCRB Dossier No/��/'/��/=��+�� /…/////………

� � � � � � � ��6. Country where trained�+��&>��S��0>+W��)�* ……………..…………………7. Category of Terrorist�O� �-��?��\&N@ *……….………/� � � � � ��8. Explosive used��)��)��6-<��* ……………………………………………9. Weapon used��)��)��!0��*…………..……...

� � � � � ��10. Target(s) of terrorist �O� �-��?��,y�*� (i) ………………………………………. (ii) .……….……///………………………………………….

� � � � �11. Area(s) of operation (districts)�� -�!?�W&^��+�,�*

�i) ……….………………………….…………………….. (ii) …………………………………………………………////////////////////////////…

(iii) …….…………………………………………………. (iv)////////////////////////////………………….………………………………………..

(v)……..….……………………………………………….

12. Affiliations and Associations��-�� 2 "�[��'(��+�� 2 "*

(i) ………….……..…………………..………………/. (ii) …………………////////////////////////////////…. …./////////////////////////////////////

13. Hideouts�I9 ��&��<��* (i) ………..……..……………………/�ii) ………///////////////////////////////…………………………….……………….….

�14. Harbourer Details�>�N��&�&�-�,&��6--�N*:

1. (i) Name ��*///////////////////////////////……………………………..………………………………………………………….…. /

(ii) Father’s/Husband’s Name�6��0��*////////////////////////////// ……………….………………………………………/

(iii) Address��*…/////////////……………………………. Locality�<��*////////////////………...…………………………………

� � � City�>!�*/……………………………….///////////////. Distt/�+�,�*………………/////// P/S/��*/////……….…………..

2. (i) Name��*/////////////////////////////………………………………………………………………………………………………

(ii) Father’s/Husband’s Name�6��0��*//////////////////////////// ………………………………………………………//

(iii) Address��*……………………………….////////////// Locality�<��*………...…………………………………/////////////

� � � City�>!�*/………………………………..///////////////// Distt/�+�,�*………………/////// P/S/��*////……….…………..

NOTE: Please use additional sheets in case of more associates.

��o�N@:-�[��'0"��!��0)�M��& �0,�� ',)��Q��R�@��S�

Signature of the Investigation Officer:

� � � � � � � � � '�9� "��'0"��?��& �!<��W�

Name��*: /………////////////////////…………………

Rank��* : ……………………////////////////////…

Number, if any ……………………….../////////////////

� � � � � � � � � � b��B��:

Date�� ………………………….. � � � � � �� Place�<��*:////……………………….. ////////////////