Spreadsheet: 189e7500-2c3c-451b-8252-51033e8fccb9
Sheet: Interfaces

Spokane County Request for Proposals #P8705
Public Safety Information Systems Replacement Project
CAD, Mobile, RMS/AFR Interface Requirements
 | Master List | Description
 |  | PSAP\911 phone call delivery vendor
 |  | Washington State and Federal  index of criminal justice information
 |  | Law and Fire\EMS analysis and mapping solution
 |  | Business Intelligence Software
 |  | Photo Management (home grown)
 |  | Computerized voice dispatch and fire station alerting
 |  | Emergency medical determinant code software
 |  | Unit update interface from Fire CAD to AMR (Ambulance contracted provider)
 |  | Alphanumeric and cell phone paging for Verizon, AT&T, Sprint and Nextel
 |  | Scheduling
 |  | Fire EMS Records Management System
 |  | Regional RMS
 |  | Regional RMS
 |  | Image warehouse of an approved incident report
 |  | Jail Management System
 |  | Ticket/Crash Reporting
 |  | Regional Gang database
 |  | Property management system
 |  | State Offender [NAME] to import and export registered offender information
 |  | County Warrant system
 |  | Custom Extraction Methods
 |  | Pawn property records
 |  | Spokane County Employee Tracking System
 |  | Jail Employee Deployment Information
 |  | The County would like the ability for criminal justice IT staff to access the RMS database for real time access to data, for use in other application.  In addition, these outside apps (such as CaseMan and PreTrial Services) need the ability to import criminal/arrest history associated to a name, and import images pertaining to criminal/arrest history.  In addition, these outside apps need the ability to import details associated to an incident number, and to import images pertaining to an incident number.  [NAME] detention needs the ability to import incident images involving juvenile subjects and arrestees.
REQUIRED INTERFACES
Item # | Interfaces | Comply ( C) | Not Comply (N) | Alternative\Conversion (A) | Modification (M) | Third Party Add-On (T) | Comments
1 | [NAME]
 | Ability to provide a one-way interface from the Cassidian E9-1-1 system to the CAD application.
 | Ability to import 911 data into the CAD system to pre-fill the CAD incident mask.
 | Ability to transfer ANI/ALI data, including caller X/Y coordinates and cell tower coordinates into the CAD incident mask.
 | Ability to automatically translate X/Y coordinates into an address point on the CAD incident mask.
 | Ability to transfer ANI/ALI data, including caller Lat/Long coordinates and cell tower coordinates into the CAD incident mask.
 | Ability to automatically translate Lat/Long coordinates into an address point on the CAD incident mask.
 | Ability to transfer the cellular service provider name into the CAD incident mask.
 | Ability to parse address information when transferring data from the E9-1-1 system to the CAD system.
 | Ability to transfer 9-1-1 call receipt time to CAD call history.
 | Ability to append TTY conversation to CAD incident.
 | Ability to plot incoming 9-1-1 calls on the CAD application map.
 | Ability to transfer information captured in the E-911 system and link it to incidents.
14 | Notifications to Primary Voice and Data Carriers (txt)
15 | WACIC/NCIC
16 | CAD Functionality
 | Ability to support a bi-directional interface between the CAD/Mobile and WACIC/NCIC.
 | Ability to limit access to WACIC/NCIC interface by security group or user.
 | Ability for users to attach query returns to CAD incident record.
 | Ability to run queries automatically upon execution of selected commands (e.g., run plates and registered owner upon entering a traffic stop).
 | Ability to conduct WACIC/NCIC queries (e.g., wanted person, missing person, protection order, etc.) via a standard query screen.
 | Ability for WACIC/NCIC queries to automatically query the multiple databases at the same time, as defined by each agency (e.g., Police RMS, Fire RMS, COPLINK, etc.)
 | Ability to allow dispatchers to monitor field personnel WACIC/NCIC queries.
 | Ability to disable feature allowing dispatchers to monitor field personnel WACIC/NCIC queries.
 | Ability to notify dispatchers when field personnel receive a hit on a WACIC/NCIC query run from the Mobile.
 | Ability to display photos, images or other multimedia content from WACIC/NCIC.
 | RMS Functionality
 | Ability to support a bi-directional interface between the RMS  and WACIC/NCIC.
 | Ability to perform the following WACIC/NCIC transactions from within the RMS:
 | Query record
 | Add record
 | Modify record
 | Supplement record
 | Clear record
 | Cancel record
 | Ability to update the RMS (add or modify records) with information returned from a WACIC/NCIC query.
 | Ability to support automated NCIC validation letter.
 | Ability for NCIC validation letters to incorporate agency-defined data fields (e.g., automatically enters subject's address, property, etc.)
 | Ability to automatically populate the WACIC/NCIC mask from within a record (e.g. from information contained in that record).
 | Ability, when required by WACIC/NCIC, to create a logically associated record to submit multiple entries related to the identical incident.
 | Ability to auto-truncate records information based upon WACIC/NCIC limitation.
 | Ability to run WACIC/NCIC queries from within the RMS (e.g. upon entering a name, property, vehicle, etc.).
 | Omega CrimeView and\or FireView
 | Ability to transfer CFS data from the CAD application to Omega Crime View and\or FireView.
 | Ability for transfer of data to occur:
 | In Real-time
 | Via a County-defined batch updating schedule
 | QLIKView
 | Ability to transfer CFS data from the CAD application to QLIKView.
 | Ability for transfer of data to occur:
 | In Real-time
 | Via a County-defined batch updating schedule
 | SPRS
 | Ability for users on the CAD and Mobile applications to query the SPRS photo database based on:
 | Name
 | CID number
 | Ability to hyperlink photos from SPRS with master name files.
 | Ability to import photos from SPRS and have that photo associated with a master name file.
 | Ability to query SPRS using the SPRS associated number from the RMS.
 | COPLINK
 | Ability to upload information to the COPLINK database from the RMS.
 | Ability for County to determine what incident information is exported.
 | Ability for County to determine the frequency of data transfer (e.g., real-time, hourly, daily, etc.)
 | LInX
 | Ability to upload information to the LInX database from the RMS.
 | Ability for County to determine what incident information is exported.
 | Ability for County to determine the frequency of data transfer (e.g., real-time, hourly, daily, etc.)
 | OnBase
 | Ability to interface with OnBase scanning to export a .TIF of all law enforcement reports upon completion.
 | GTL - Offender Management System
 | Ability to support an interface between the RMS and GTL OMS
 | Ability to query the GTL OMS from the RMS.
 | Ability to query the RMS from GTL OMS
 | Ability for modifications related to an individual (e.g., appearance, scars/marks/tattoos, address, etc.) to update the RMS master files.
 | Ability to return a soundex ordered list of names from RMS to OMS
 | Ability to add and/or manage RMS names and CID numbers on behalf of OMS requests
 | Ability to add and/or manage other data stored in RMS on behalf of OMS (including jail status, charge information, etc.)
 | Ability to transfer agency-identified fields from the RMS to GTL (e.g., CCID)
 | Ability to transfer agency-identified fields from GTL to the RMS (e.g., address, personal identifiers)
 | Ability to transfer information from the field reporting system to GTL.
 | SECTOR
 | Ability to interface with Washington State Statewide Electronic Collision and Ticket Online Records (SECTOR) so that all information captured within the SECTOR application is transferrable to the RMS.  If these needs can be partially met, indicate the discrepancies within the "comments" section.  For more information on SECTOR, see http://trafficrecords.wa.gov/eTRIP/SECTOR/SECTOR_Default.aspx
 | Ability to interface with SECTOR so that agency-defined information captured within the field report from the AFR is available for transfer into the SECTOR.
 | Ability to interface with the SECTOR so that agency-defined information captured within the SECTOR is available for transfer to the field report.
 | PathFinder
 | GangNet
 | Ability to interface with GangNet to export incident information.
 | Ability to interface with GangNet to import agency-defined information.
 | Ability for County to determine what incident information is exported.
 | Ability for County to determine the frequency of data transfer (e.g., real-time, hourly, daily, etc.)
 | The BEAST
 | Ability to support a two-way interface with The BEAST and the RMS.
 | Ability for officers to enter property and evidence information into the field reporting system and have it transferred to the BEAST.
 | Ability to receive an export from the BEAST into the RMS regarding property information (all applicable data fields)
 | Ability to query The BEAST from within the RMS.
 | State Offender [NAME]
 | Ability to export information from the Registered Offenders database in the RMS to the State Offender Watch Database
 | Ability to import information from the State Offender Watch database to the Registered Offenders database in the RMS.
 | OnBase
 | County Warrant System
 | Ability to interface with the County Warrant System to import Warrant data to the RMS.
144 | CRASH - SECTOR
 | Ability to export accident report data to the CRASH system.
 | DATA EXCHANGE
 | Ability to upload data into RMS using a DATA EXCHANGE
 | Ability to extract data from RMS to use in other systems using a DATA EXCHANGE.
 | PAWN
 | Ability to import the following data fields from pawn property information:
 | Pawner information:
 | Name
 | Race
 | Sex
 | DOB
 | Address
 | Transaction information:
 | Date
 | Time
 | Location of Pawn Shop
 | Item Description:
 | Make
 | Model
 | Color
 | Description
 | SETS application
 | Ability to import the following training records information:
 | Class details
 | Course Topics
 | Student Information
 | JEDI application
 | Ability to import the following training records information:
 | Class details
 | Course Topics
 | Student Information
 | Other Applications
 | Ability to provide County access to the RMS database for real time access to data for use in other applications.
OPTIONAL INTERFACES
 | Locution Fire Station Alerting
 | Ability to support an interface with the Locution fire station alerting system.
 | Ability for CAD application, upon entry of agency-defined criteria, to activate fire station alerting system.
 | Ability for CAD application to recognize fill-in units and activate the fire station alerting system for where that unit has redeployed.
64 | Medical Priority Paramount
 | Ability to integrate ProQA into the call taking/dispatching process.
 | Ability for all interactions with ProQA (e.g., questions posed, answers received) to be automatically attached to the CFS record.
 | Ability for the County to determine which questions and responses become attached to the CFS record.
 | Ability for ProQA to automatically launch dependent on county-defined call types.
 | AMR CAD-to-CAD
 | Ability to provide a two-way interface with AMR ambulance company (TriTech CAD system).
 | Ability to generate requests for service from AMR.
 | Ability to send requests for service to AMR.
 | Ability to monitor availability of AMR units and special equipment.
 | Ability to log interagency communications in CAD audit files.
 | Ability to take into account the unit status of AMR apparatuses when recommending appropriate units for dispatch.
 | Ability to take into account unit location of AMR apparatuses when recommending appropriate units for dispatch.
 | Ability to send messages to AMR.
 | Ability to integrate AVL data from AMR the CAD map.
 | Telestaff
 | Ability to import multiple Telestaff instance roster information from Telestaff into CAD
 | Ability for transfer of data to occur:
 | In Real-time
 | Via a County-defined batch updating schedule
 | Fire RMS
 | Ability to export active and closed calls information to FDM and FireHouse Fire RMS Systems
 | SafetyPad ePCR
 | Ability to export active and closed calls information to SafetyPad ePCR application
84 | Paging
 | Ability to support paging interfaces from the CAD/Mobile system to the paging systems. |  |  |  |  |  | The Zetron Model 25 handles 5/6 toning, and the Zetron Model 2200 handles the digital paging.
 | Ability to support the development of paging groups within the CAD system.
 | Ability to select a paging group within the CAD/Mobile system and trigger pages to individuals within the paging group.
 | Ability to select units within the CAD/Mobile system and trigger pages to those units.
 | Ability to generate pages based on units recommended for a response.
 | Ability to send a dispatch to a unit via a paging device.
 | Ability to send the following information in a page:
 | Call type
 | Incident number
 | Incident location
95 | Customer Definable Data Elements
 | Ability to automatically generate pages to agency-defined paging groups based on agency-defined parameters (e.g., incident type, call priority, location).
 | Ability to support VOIP paging.