Example: tourism industry

Standard Functional Specifications for Law Enforcement ...

Bureau of Justice Assistance Office of Justice Programs Department of Justice NIJ National Institute of Justice The Research, Development, and Evaluation Agency of the Department of Justice Standard Functional Specifications for Law Enforcement Records management Systems (RMS). Developed by the Law Enforcement Information Technology standards Council (LEITSC). Standard Functional Specifications for Law Enforcement Records management Systems (RMS). Developed by the Law Enforcement Information Technology standards Council (LEITSC). Standard Functional Specifications for Law Enforcement Records management Systems (RMS) . This document was prepared with the guidance, leadership, and funding of the Bureau of Justice Assistance, Office of Justice Programs, Department of Justice, in collaboration with the Law Enforcement Information Technology standards Council.

enforcement Records Management Systems (RMS), it is vital to recognize and consider the Law Enforcement Information Sharing Program (LEISP) developed by the U.S. Department of Justice (DOJ). The LEISP is designed to promote information sharing among all levels of the law enforcement community and to guide the investment of

Tags:

  System, Management, Standards, Specification, Enforcement, Record, Investment, Functional, Standard functional specifications for, Enforcement records management systems

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Transcription of Standard Functional Specifications for Law Enforcement ...

1 Bureau of Justice Assistance Office of Justice Programs Department of Justice NIJ National Institute of Justice The Research, Development, and Evaluation Agency of the Department of Justice Standard Functional Specifications for Law Enforcement Records management Systems (RMS). Developed by the Law Enforcement Information Technology standards Council (LEITSC). Standard Functional Specifications for Law Enforcement Records management Systems (RMS). Developed by the Law Enforcement Information Technology standards Council (LEITSC). Standard Functional Specifications for Law Enforcement Records management Systems (RMS) . This document was prepared with the guidance, leadership, and funding of the Bureau of Justice Assistance, Office of Justice Programs, Department of Justice, in collaboration with the Law Enforcement Information Technology standards Council.

2 This project was supported by Grant No. 2003-MU-BX-0068, awarded by the Bureau of Justice Assistance. ii Standard Functional Specifications for Law Enforcement Records management Systems (RMS). Acknowledgements LEITSC Governance LEITSC Functional standards Committee Larry Boyd, Chairman Joe Cassa Chief of Police Bureau Commander Irving (TX) Police Department Wheat Ridge (CO) Police Department Police Executive Research Forum (PERF). Mitchell Ray Davis, III. Joe Akers Chief of Police LEITSC Staff Liaison Dixmoor (IL) Police Department National Organization of Black Law Enforcement Executives (NOBLE) Debbie Fox Information Technology Administrator Terry Chowanec Louisville (KY) Metro Police Department LEITSC Staff Liaison PERF Michael Haslip Chief of Police Ted Kamatchus, Vice Chair City of Blaine (WA) Police Department Sheriff Marshall County (IA) Sheriff's Office Linda Hill National Sheriffs' Association (NSA) Consultant IJIS Institute Mark Marshall Chief of Police J.

3 B. Hopkins Smithfield (VA) Police Department Division Commander/Jail Administrator International Association of Chiefs of Police (IACP) Story County (IA) Sheriff's Office Morris Roberson Dina Jones Postal Service (Retired) CAD Manager NOBLE Story County (IA) Sheriff's Office Heather Ruzbasan Bruce Kelling LEITSC Project Manager Bask Enterprises, LLC. Managing Principal G. Matthew Snyder LEITSC Staff Liaison Daniel Murray IACP IT management Section Commander Arlington County (VA) Police Department Fred Wilson LEITSC Staff Liaison NSA. Standard Functional Specifications for Law Enforcement Records management Systems (RMS) iii Beverly Muse J.

4 Patrick McCreary Technology Manager Associate Deputy Director City of Chattanooga (TN) Bureau of Justice Assistance Office of Justice Programs Morris Roberson Department of Justice Postal Inspector (Retired). Postal Service Harlin McEwen Chief of Police (Retired). Jim Slater Ithaca (NY) Police Department Chief Information Officer Massachusetts Executive Office of Public Safety David Mulholland Lieutenant Mark Steigemeier Park Police Vice President IACP. Motorola Jennifer Zeunik Darrell True Former LEITSC Project Manager (2002 2005). IT Administrator IACP. Wrentham (MA) Police Department Gary Vest Project Manager Chief of Police Heather Ruzbasan Powell (OH) Police Department LEITSC.

5 International Association of Chiefs of Police Paul Wormeli 515 North Washington Street Executive Director Alexandria, VA 22314. IJIS Institute (703) 836-6767, ext. 275. Advisors and Other Program Contacts William Cade, Jr. Director, 911 Services and Communications Operations Special Thanks to Our Partners Center Association of Public Safety Communications Officials Joe Estey Chief of Police Hartford (VT) Police Department Former LEITSC Governance Member IJIS Institute IACP Joe Heaps Communications Technology Portfolio Manager National Institute of Justice This document is the result of an extraordinary Office of Justice Programs collaboration between many justice practitioners and Department of Justice industry experts.

6 Thank you all for your commitment, time, energy, and patience. Dustin Koonce Policy Advisor Bureau of Justice Assistance Office of Justice Programs Department of Justice iv Standard Functional Specifications for Law Enforcement Records management Systems (RMS). Table of Contents iii Table of v Executive Summary: Records management ix Business Function: General 1. Business Function: Master 3. Use Case 3. Use Case: Master Name 3. Use Case: Master Vehicle 5. Use Case: Master Property 5. Use Case: Master Location 5. Use Case: Master Organization 5. Business Function: Calls for 7. Use Case 8. Use Case: Transfer CFS Data to 8. Business Function: Incident 9.

7 Use Case 9. Use Case: Prepare Initial Incident 9. Use Case: Create Supplemental 10. Use Case: Report 11. Business Function: Investigative Case 13. Use Case 13. Use Case: Assign 13. Use Case: Case 14. Use Case: Conduct 14. Use Case: 14. Use Case: Case 15. Business Function: Property and Evidence 17. Use Case 18. Use Case: Collect Property and 18. Use Case: Vehicle 18. Use Case: Property and Evidence 19. Use Case: Property and Evidence 19. Standard Functional Specifications for Law Enforcement Records management Systems (RMS) . Business Function: 21. Use Case 21. Use Case: Receive and Process 21. Use Case: Verify 21. Use Case: Warrant 22.

8 Use Case: Cancel 22. Business Function: 23. Use Case 23. Use Case: Arrest 23. Use Case: Arrest Warrant 24. Use Case: DUI 24. Business Function: 25. Use Case 25. Use Case: Process 25. Use Case: Verify 26. Use Case: 26. Business Function: Juvenile 27. Use Case 27. Use Case: Juvenile 27. Use Case: Juvenile 28. Use Case: Juvenile 28. Business Function: Traffic Accident 29. Use Case 29. Use Case: Accident 29. Business Function: 31. Use Case 31. Use Case: Issue 31. Business Function: Field 33. Use Case 33. Use Case: Document Field 33. Business Function: 35. Use Case 35. Use Case: Receive and Process Pawn 35. Use Case: Seize Pawn 35. Use Case: Analysis of Pawn 36.

9 Use Case: Regional and State Pawn 36. Business Function: Civil 37. Use Case 37. Use Case: Serve 37. Use Case: Seized 37. Use Case: 38. Business Function: Protection Orders and 39. Use Case 39. Use Case: Protection Order and Restraint 39. Business Function: Permits and 41. Use Case 41. Use Case: Application 41. Use Case: 41. Use Case: Background 41. Use Case: 42. vi Standard Functional Specifications for Law Enforcement Records management Systems (RMS). Business Function: Equipment and Asset 43. Use Case 43. Use Case: Equipment 43. Use Case: Equipment 43. Use Case: Equipment 43. Use Case: Equipment 44. Use Case: Physical 44. Use Case: Equipment 44.

10 Use Case: Equipment 44. Business Function: Fleet 45. Use Case Diagram .. 45. Use Case: Fleet 45. Use Case: Fleet 45. Use Case: Fuel 45. Use Case: Fleet 46. Use Case: Damage 46. Use Case: Fleet 46. Business Function: 47. Use Case 47. Use Case: Operational 47. Use Case: Personnel 47. Use Case: Scheduling and 48. Use Case: 48. Use Case: Duty 48. Use Case: Training and 48. Business Function: Internal 51. Use Case 51. Use Case: Conduct IA 51. Business Function: Analytical Support (Crime Analysis).. 53. Use Case 54. Use Case: Tactical 54. Use Case: Strategic 54. Use Case: Forecasting 54. Use Case: Administrative 54. Business Function: RMS 57.