Document Sample
CAPTAIN Retreat Powered By Docstoc
         A Service Management Update
                  Capitol Region Council of Governments

Agency Administrators
August 17, 2004
Wethersfield Police Department

   CAPTAIN System Direction
   CJIS Application Summary Update
   Wireless Service Update
   CAPTAIN Improvements/Changes
   Requests for New Features/Functions
              Mobile Data System
 Originally designed as a statewide pilot mobile data
 Operating for almost six years in the field
 Principal purpose was four fold:
    –   Field COLLECT access
    –   Paperless incident reporting including crash
    –   Regional data sharing
    –   Field messaging service
   Piloted in 39 towns as part of the Capitol Region
    Chief of Police Association
   Commercial carrier technology
               Usage Status
• Statewide Standard; mobile data system of choice for
  CT law enforcement agencies
• 85 law enforcement agencies use some part of the
  system in their police cars
• Currently managed by Capitol Region Council of
  Governments through its Public safety Council with a
  single technical committee.
• No full time employees
• 1180+ laptop, palmtop, devices
• 1500+ LAN based devices
       CAPTAIN Components
   Messaging (chat)
   Inquiry
   CAD Interface
   Interface to Local Records Management
   Incident Reporting
     Crime (NIBRS)
     Crash
 Interface to DOT Server
 Traffic Stops (Racial Profiling)
             Next Steps
 Implement New Wireless Technology
 Add Functionality and New Users
 Migrate Application to Browser
         CAPTAIN Next Steps
    Implement New Wireless Technology
   Specify new broader band wireless service with
    ruggedized devices and GPS capability
   Procure through competitive bid
   Test and evaluate
   Affirm network security and reliability
   Initiate conversion of selected elements of connection
   Provide new “modems” for each user
   Dispose of CDPD equipment
   Roll out complete by December 2004
          CAPTAIN Next Steps
           Add Functionality and Users
   Identify application changes and improvements through several
    JAD sessions
   Revise application to include new COLLECT functionality
   Support field use of OBTS and PRAWN
   Consider alternatives to data sharing and reporting model
   Specify and acquire Homeland Security and Emergency
    Management applications for CREPC towns
   Specify and acquire AVL and critical resource map services
   Add Fire and EMS CAD interfaces
   Add Fire and EMS to Messaging Service with added security
   Legacy interfaces will continue to be maintained for a
    considerable time
   Would like to implement electronic citations
         CAPTAIN Next Steps
               Migration to Browser

   Contract with a vendor for selected project
    management services; including specification
   Technical Committee will continue to manage project
   Re-visit DOIT application hosting
   Legacy interfaces will continue to be maintained for a
    considerable time
         Reporting Model
Three approaches to incident and crash
  – National standard (NIBRS, NFIRS, MMUCC)
  – Common report form for all users (IOWA
    National Model)
  – XML based interfaces for all CAPTAIN
    reporting to meet state and national
        End User Perceptions
 Police officers are becoming the first line in data
 Police officers are the most expensive data entry staff
  in the justice and traffic records systems
 Mobile applications have to first work for those who
  work in the field
 Research must be done without collecting all of the
  data all of the time
 There needs to be a dividend from the efficiencies
  brought from task to transfer to police officers in the
           James P. Donnelly
              Project Manager
CAPTAIN Mobile Data Communications Systems
               860 826-3087

Shared By: