| Product: |
|
|
|
|
|
| Economics: |
|
|
|
|
|
cost?
|
|
|
|
|
|
cost savings?
|
|
|
|
|
|
total cost of
ownership (operating expenses, maintenance, etc).
|
|
|
|
|
|
funding sources
|
|
|
|
|
|
would it qualify
for DHS funding?
|
|
|
|
|
|
could it reduce
manpower needs?
|
|
|
|
|
|
could it automate
manual processes?
|
|
|
|
|
|
| Public perception: |
|
|
|
|
|
would it make
people feel safer
|
|
|
|
|
|
would it make
people feel civil liberties were at risk?
|
|
|
|
|
|
would it make
people feel it encouraged discrimination?
|
|
|
|
|
|
would it make
people feel there was less risk of lethal consequences?
|
|
|
|
|
|
is the technology
available to the general public?
|
|
|
|
|
|
| Police perception |
|
|
|
|
|
would police feel
it made them safer?
|
|
|
|
|
|
would police feel
it was easy to use?
|
|
|
|
|
|
would police feel
intimidated by training it required?
|
|
|
|
|
|
would police feel
it complicated their jobs?
|
|
|
|
|
|
would policefeel
it endangered them?
|
|
|
|
|
|
| Would it increase potential liability? |
|
|
|
|
|
| (For
electronic technologies) is it based on Open Standards, and does
that make it both cheaper and more robust than competitors based
on proprietary systems? |
|
|
|
|
|
| Is
it too cutting-edge to be reliable at this point? |
|
|
|
|
|
| Operations: |
|
|
|
|
|
would it speed up an
existing process and make it a more effective tool?
|
|
|
|
|
|
would life-cycle
costs be too high?
|
|
|
|
|
|
will it foster
"digital convergence " by interconnect well with other
technologies?
|
|
|
|
|
|
would it require
significant disruption to daily routines?
|
|
|
|
|
|
would it allow
us to do things we can't today?
|
|
|
|
|
|
would it facilitate
collaboration with other jurisdictions and agencies?
|
|
|
|
|
|
| Is it approved by the CIJ? |
|
|
|
|
|
| would it interface easily with legacy technology? |
|
|
|
|
|
| is it likely to become obsolete rapidly? |
|
|
|
|
|
44.493 Issues
in Criminal Justice Technology & Security