Today, we introduce the latest update for our beta test version of Ops Force Deploy. Many improvements to the interface have been made as well as many bugs fixed based on the feedback you have given us.
There are some changes to this version that we expect you will notice:
1. A Calculation Bug:
In the previous beta release, there was a bug that could cause the “Fit” in Scheduler to change when the workflow was closed and re-opened. We have addressed this issue and the fit number should now be consistent, but it will be different than the number you had seen in the last release. This is explained also by #2 and #3 below.
2. An Improvement to the Mathematics
When we first started developing Deploy, we based our calculations on an established queuing model. Over time, we have found ways to improve its accuracy based on our experience in applying this model to real police operations. One of the limitations we found with the model is that it did not consider “Response Speed” when calculating “Probability of All Units Busy”. “Response Time” has always correctly included the “Response Speed”.
When setting Operational Goals or allocating units based on “Probability All Units Busy”, the resulting probability was not influenced by this speed. The reason this is important to consider is that when units are en-route to an event, they are unable to respond to other events (unless pre-empted by a dispatcher). In simple terms, if they are responding more slowly, it is more likely that all units will be busy.
I am happy to announce that we have enhanced the equations so that “Response Speed” will now directly affect this statistic. Because of this change, you will likely see an increase in the number of units required to meet this Operational Goal. Also, your “Fit” in Scheduler will change. Please do not be alarmed by these changes.
3. “Lost Time” and Fit
If you have any “lost time” set in your schedule profile for the beginning or ending of shift, the reduction of this time was not affecting your Fit. We have addressed this issue so that the reduction of staff during their lost time will now be reflected in the Fit number. The result of this is that your Fit is likely to go *down* vs before. Since the lost time usually happens during shift overlaps where your schedule is overstaffed, reducing units based on this lost time now helps offset this over-staffing and results in a better fit to your workload.
We know there are still some pending feature requests from our customers and bugs that remain but we hope that you will log in and kindly let us know of any problems you may encounter so we can continue to work towards our next official release.
-Dan Harris, CTO