Laserfiche WebLink
APPENDIX A <br />PARIS PATROL STAFFING MODEL <br />This model is a simple time needed model which uses historical data gathered from <br />existing departmental and city sources and computes the time necessary to accomplish <br />the required tasks and divides that time by the average work time available per officer. <br />With twelve hour shifts - alternating as they do - the model will tell you the number of <br />officers needed on each of the day shifts and each of the night shifts. If you enter 365 in <br />line 11, it will tell you how many officers you need to split between the two shifts. Data <br />entry items are discussed below. <br />Definitions <br />Data Entry Items <br />Number of Work Days in Period (line 11) <br />Days in period under study. Model can be used for less than one year but all <br />data must be gathered for just that period. Since the 12 hour shifts altemate regularly, each day <br />shift will have 182.5 work days in a year. <br />Shift Length in Hours (line 12) <br />Self-explanatory. <br />Average Citizen Generated Calls for Service on Shift per day (line 13) <br />This is an average of the count of Citizen Generated calls only. Officer initiated calls and arrests <br />are conducted during the Proactive/Preventive Time designated for officers (line 37). Most CAD <br />applications can produce the total number of calls per shift in any time period. This information can <br />be divided evenly between the two day or two nigh shifts as calls occur randomly. <br />Total Citizen Generated CFS per shift per Year (line 14) <br />This number is automatically generated by multiplying line 11 and line 12. <br />Percentage of Citizen CFS Requiring Multiple Unit Dispatch (line 15) <br />This percentage is derived from dividing the number of actual two unit dispatches by the total <br />number of Citizen CFS received. It usually will not change significantly from year to year unless <br />policy decisions change the types of multi-unit dispatch criteria. If CAD system is able to produce <br />this more accurately, use the more accurate figures. If the CAD is able to track total time on call for <br />all units combined either per call or in total for a specific time period, that data should be entered <br />manually and not computed by this model. Average Time on Call (line 16) <br />Average time on call is obtained from accurate CAD data. Absent reliable data from the CAD <br />system, use between .66 and .75. Most agency's actual data ranges between 40 and 45 minutes <br />per call on average. <br />Total Time Required for all Citizen Generated Activity (line 17) <br />This number is generated by adding the total number of Citizen Calls and the number of multiple <br />unit dispatches, which are second officers on the calls, and multiplying by the average time on call. <br />Page 51 <br />