1-866-PRESYNCT
YOUR FORMS, OUR SOFTWARE®
|
|
YOUR FORMS, OUR SOFTWARE® |
|
|
|
|
|
|
|
|
 |
|
|
||
|
|
|
FAQs
Is Presynct the right police/incident report writing system for
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 1. How is your current incident report filing system indexed? | |
|
|
| 2. How do you handle agency reporting requirements, such as management or UCR/NIBRS reporting? (i.e. state/fed crime summary)? | |
|
|
| 3. How long does it take officers to complete an incident report? | |
|
|
| 4. How do you handle/track incident report attachments in your current filing system? | |
|
|
| 5. How does your current approval process work? Work flow? | |
|
Have you ever calculated out what it costs to process a hand-written incident report? Consider the following example provided by Commander David Rossetto, Division Commander, Milpitas Police Department (Note: This example uses salaries based on a national average according to the US Department of Labor):
Officer Time |
25 mins x $31/hour |
$12.91 |
Sergeant’s Time |
5 mins x $43/hour |
$3.58 |
Records Clerk Time |
10 mins x $25/hour |
$4.17 |
 |
||
|
|
|
|
||
TOTAL PER REPORT |
40 minutes |
$20.66 |
Now, how many reports do you process a month or each year?
500 reports/ month = $10,330 |
6,000 reports/ year = $123,960 |
1,000 reports/ month = $20,660 |
12,000 reports/ year = $247,920 |
Plug in your own department’s salaries - how much is it really costing you? And then, tally up your hard costs for paper, envelopes, postage, re-sends, copier supplies and maintenance, etc.
Using the same example above, it takes about 40 minutes to process a report by hand. Now let’s break that down using the Presynct Report Network:
Officer Time |
20 mins x $31/ hour |
$10.33 |
*The auto-populate feature in Presynct will save time since officers do not have to retype redundant data |
||
|
|
|
Sergeant’s Time |
5 mins x $43/hour |
$3.58 |
|
|
|
Records Clerk Time |
$0.00 |
|
|
||
|
|
|
|
||
TOTAL PER REPORT |
25 minutes |
$13.91 |
Now, how many extra officer hours does that extra 15 minutes add up to?
500 reports/ month = 125 hours |
6,000 reports/ year = 1,500 hours |
1,000 reports/ month = 250 hours |
12,000 reports/ year = 3,000 hours |
What sets Presynct Technologies, Inc. apart from the competition is the close relationship that we strive for with each of our customers. There are no empty promises, we’ll be there when you need us… and we back that up with a money-back guarantee to prove it!
The Presynct Report Network is an entry-level system. It’s easy to use, affordable and designed and built to grow with you as your department’s needs grow.
Presynct does not require the huge financial and time commitment involved with the installation of a RMS.
Presynct interfaces easily with existing systems – it was specifically designed that way. The Presynct software is based on open-standards technology.
Presynct builds and completes most of the testing of each system in our own facilities. The onsite installation can be as short as one day for a basic configuration that requires little, if any, integration with other systems. We also offer onsite training, so your department can be up and running on the Presynct Report Network in only a few days, not a few months or years!
Average training time is only a few hours. Since Presynct leverages the format of your department’s existing forms and processes, the system requires minimal training. Officers instantly feel at home completing the same forms on the computer that they used to handwrite.
Yes, depending on your existing police report software technology. We can make a definitive determination after we’ve had a chance to review your existing report software and systems.
MDC and laptop requirements are:
PCs:
Server requirements are:
1. |
Easy to use |
No system is worth the cost if nobody uses it! |
|
|
|
2. |
Open architecture |
Will the system integrate with the current systems you have in place? Will the system integrate with any systems you plan to purchase in the future? You don’t want to have to purchase a new system in 3 years because you invested in a system that can’t be used with any other vendor’s products. Flexibility is important. |
|
|
|
3. |
Cost effective |
Is the investment worth it for your department? Budgets are tight, how do you justify the cost? What immediate benefit will your agency feel? What long-term problems does the purchase solve? |
|
|
|
4. |
System fits YOUR needs |
Find a system that works for you, not the other way around. No one system works for every department, if your needs are not the great – don’t buy a system with a lot of bells & whistles. |
|
|
|
5. |
Current environment |
Only you really know your agency and officers – will they use the system you choose? |
|
|
|
6. |
Look to the future |
NIBRS, GJXML, add on systems, where will your department be in 3 or 5 years? |
|
|
|
7. |
Company integrity |
Who are you partnering with? Will they stay with you through the entire process? |
|
|
|
8. |
Installation |
How much time are you going to be offline? The length of time depends on what you’re doing – the initial installation of a new system will be relatively quick, while interfacing with an existing system could take a little longer. |
|
|
|
9. |
Maintenance |
What does it involve? Who handles it? Do you have an IT Dept.? |
|
|
|
10. |
What do you want the |
Complete reports, electronic distribution, external distribution or internal distribution, store information, retrieve information, print copies of reports as they look today, create crime analysis, State or Federal reporting. |
According to the Federal Bureau of Investigations, UCR is a city, county, and state law enforcement program which provides a nationwide view of crime based on the submission of statistics by law enforcement agencies throughout the country. The Uniform Crime Reporting Program was conceived in 1929 by the International Association of Chiefs of Police to meet a need for reliable, uniform crime statistics for the nation.
The crime data are submitted either through a state UCR Program or directly to the national UCR Program, which is administered by the FBI. Since the 1930s, the data have been used in law enforcement administration, operation, and management, as well as to indicate the levels and nature of crime in the United States.
According to the Federal Bureau of Investigations, NIBRS is an incident-based reporting system through which data are collected on each single crime occurrence. NIBRS data are designed to be generated as a by-product of local, state, and federal automated records systems. Thus, an agency can build a system to suit its own needs, including any collection/storage of information required for administrative and operational purposes, in addition to reporting data required by NIBRS to the national UCR Program. NIBRS collects data on each single incident and arrest within 22 offense categories made up of 46 specific crimes called Group A offenses. For each of the offenses coming to the attention of law enforcement, specified types of facts about each crime are collected. In addition to the Group A offenses, there are 11 Group B offense categories for which only arrest data are reported. (UCR Handbook, NIBRS Edition, pp. 1-2)
The Global Justice XML Data Model (Global JXDM) is intended to be a data reference model for the exchange of information within the justice and public safety communities. In a nutshell, the Global JXDM is a technology standard for sharing data between and among disparate electronic systems.
According to the US Department of Justice – Office of Justice Programs, Global JXDM is an XML standard designed specifically for criminal justice information exchanges, providing law enforcement, public safety agencies, prosecutors, public defenders, and the judicial branch with a tool to effectively share data and information in a timely manner. The Global JXDM removes the burden from agencies to independently create exchange standards, and because of its extensibility, there is more flexibility to deal with unique agency requirements and changes. Through the use of a common vocabulary that is understood system to system, Global JXDM enables access from multiple sources and reuse in multiple
applications.
|
|
|
|
