Normal
0
false
false
false
MicrosoftInternetExplorer4
st1\:*{behavior:url(#ieooui) }
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-format:other;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
@font-face
{font-family:Utah;
panose-1:2 11 6 3 2 2 2 3 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
mso-hyphenate:none;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";
mso-fareast-language:AR-SA;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
{margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan no-line-numbers;
mso-hyphenate:none;
tab-stops:center 3.45in right 6.9in;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";
mso-fareast-language:AR-SA;}
p.MsoMessageHeader, li.MsoMessageHeader, div.MsoMessageHeader
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.75in;
margin-bottom:.0001pt;
text-indent:-.75in;
mso-pagination:widow-orphan;
mso-hyphenate:none;
background:#CCCCCC;
border:none;
mso-border-alt:solid black .5pt;
padding:0in;
mso-padding-alt:1.0pt 1.0pt 1.0pt 1.0pt;
font-size:12.0pt;
font-family:Arial;
mso-fareast-font-family:"Times New Roman";
mso-fareast-language:AR-SA;}
@page Section1
{size:8.5in 11.0in;
margin:.8in .8in 82.6pt .8in;
mso-header-margin:.5in;
mso-footer-margin:.8in;
mso-paper-source:0;}
div.Section1
{page:Section1;
mso-footnote-position:beneath-text;}
/* List Definitions */
@list l0
{mso-list-id:1;
mso-list-type:simple;
mso-list-template-ids:1;
mso-list-name:WW8Num1;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.75in;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
mso-ascii-font-family:Symbol;
mso-hansi-font-family:Symbol;}
@list l1
{mso-list-id:2;
mso-list-type:simple;
mso-list-template-ids:2;
mso-list-name:WW8Num2;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.75in;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
mso-ascii-font-family:Symbol;
mso-hansi-font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
Normal
0
false
false
false
MicrosoftInternetExplorer4
st1\:*{behavior:url(#ieooui) }
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
h2
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
mso-outline-level:2;
font-size:18.0pt;
font-family:"Times New Roman";}
p.MsoMessageHeader, li.MsoMessageHeader, div.MsoMessageHeader
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
The direction of senate Bill 2463 will
without question save taxpayers millions while creating safer roads. One area overlooked
is officer safety. Another are is in house development or hiring an outside
firm. We know of few successfully developed and implemented in house systems.
Beyond this obstacle we have major challenges in the area of officer safety,
and the need for electronic crash reporting is a factor.
Mobile computers, smart
devices such as handhelds are a valuable addition to law enforcement personnel.
These devices provide critical information about potential suspects or
violators. At the same time in car computers have also created additional
challenges by significantly increasing the number of accidents or ‘near misses’
out on the road. Also, technology can create distractions resulting in loss of
life. Many documented cases can be found showing minor distraction have resulted
in criminals getting an upper hand on a distracted officer. Any agency
that has experienced an accident or death involving a patrol vehicle knows the
serious financial and legal impact that it can have.
Any good ticket system
must deal with this important challenge. With safety technology installed
on a mobile computer, an officer can have the ability to enter a license plate
into any existing mobile software and never have to look at the computer
screen. This type of software will provide clear verbal response to the
officer of the critical components included in the files returned from NCIC,
State and Local Databases – and shared data from other departments. Critical
information such as expired tags, suspended driver licenses, stolen vehicles,
warrant hits, etc. This is a text-to-speech engine that will not read
everything in the files. It will only verbally respond the critical
information (specified by each police department) so as an officer approaches a
suspect vehicle they will already know the information needed to handle the
situation appropriately. The software should be customized to add
key words and meet the needs of any law enforcement agency. Safety systems
should also fully capable of appending key department policy statements with
key words. In short when “stolen vehicle” appears and is read back to the
officer verbally, applicable policy statements can also be voiced back. In the
case of a stolen vehicle departments may want officers alerted with “Call
Backup Immediately” instructions to comply with department policy.
The feedback that officers have
received from agencies utilizing this type of software showed, on average, the
following results:
· The number of accidents is significantly reduced
· An increase in the number of safe traffic stops due to
advanced notification of critical information
· Officers ran approximately 50% more mobile queries per
shift resulting in:
· A 70% increase in citations issued or ‘problems’
identified => leading to
· A 40% increase in the number of arrests overall
In general, these agencies have found that if they were
able to avoid accidents overall (including loss of vehicle, insurance premiums,
legal fees) the software had essentially justified every return on investment
theory, and that did not even take into consideration the additional
benefits/ROI of increased traffic tickets and revenue.
Overall, SafetyFirst has provided safer working
conditions for law enforcement officers by providing them with critical
information in real time. It allows them to maintain focus and attention
on a vehicle in front of them, rather than on a laptop computer screen.
As mentioned above, the
mobile computers allow officers to run NCIC, State, and Local checks on
individuals and their vehicles. With the addition of Safety First, the
information led to greater efficiencies for officers who started to run a
higher volume of queries, which in turn contributed to writing an increased
number of citations by officers. Officers realize that the majority
of information that is necessary to complete a ticket, is the same information
that has been already returned in the files contained in a query. In order to
simplify the process, we are able to capture the appropriate information from a
mobile query and auto-populate traffic tickets that are used by officers on
patrol. IyeTek can create an electronic version of a handwritten ticket
used by a department.
The iyeTek electronic ticket
system enables law enforcement agencies to meet ever-growing data collection
and reporting requirements without compromising safety, accuracy, or
effectiveness. Electronic tickets essentially replace conventional
tickets with thermal in car printers, and mobile computers. The software
is intuitive for the officers making it very simple and efficient for them to
complete the information. Citations can be completed and printed with
only a few keyboard strokes and in less than 30 seconds. The
resulting ticket is accurate, and completely legible. Tickets with
enhanced legibility will eliminate much of the discrepancies that can lead to
contested tickets being waived or overturned. In Miami-Dade County, a
judge estimated that approximately 20-30% of all citations were thrown out due
to errors, legibility, and incomplete information leading to millions of
dollars in lost revenue for the county.
Table #1 – Savings
related to implementation of iyeTek solutions (Avg. of sample departments)
|
Traffic Stop
Savings
Back End Savings
|
|
Ave.Time Saved: 8 Minutes per
stop
Total Citations:
20,000
|
|
Stops per Day:
10
20%
Error:
4,000
|
|
Days per Year:
300
Fine Per Citation: $75
|
|
# of
Officers:
10
Lost Income: $300,000
|
|
Time
Saved:
240,000 Minutes
|
|
4,000 Hours IyeTek Data
|
The final component of a
completely integrated electronic forms system takes the data captured by an
officer and electronically transfers it to any data collection system.
Reports can then be generated from the data gathered by these systems and
evaluated. The two benefits of electronic data capture is the elimination of
data re-entry and the associated errors and the real-time access to the
information. From the officer perspective, it does not require them to
gather or process any additional information out in the field.
Once a ticket or crash
report is printed or saved, iyeTek has the ability to send the necessary
information to any Database Management System utilizing iyeTek data.
iyeTek Data captures the data entered on a ticket and coverts it to a file
format for the receiving database. The iyeTek software eliminates the
need for duplicate data entry and provides for a 100% accurate and reliable
method of moving data from tickets directly into other court and law
enforcement record systems. IyeTek Data also integrates with TicketScan when
violator signature capture is a local requirement.
The total savings
realized by implementing iyeTek Data is dependant on a variety of factors
including: the volume of forms being processed, the time required
to input and process each form, the wages and benefits paid to clerical workers
whose sole job is data entry and processing. Most agencies find that
these employees performing data entry can be utilized in areas that are more
strategic to the department.
Overall, electronic forms
systems can effectively assist an Hawaii
in reducing its costs through greater efficiencies – and this does not even
take into consideration the revenue increases from submitting completely
accurate forms.
iyeTek's next generation technologies to ensure Hawaii agencies are
provided with the most up to date innovations. Our officers and technical
staff are continuously improving our applications and doing R & D on the
newest technology available. Chris Hood 888.949.3835 Ext 703