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

Spokane County Request for Proposals #P8705
Public Safety Information Systems Replacement Project
Mobile Functional Requirements
 | General__Mobile_Data_Computing_Features
 | Mobile_Application_User_Interface
 | Function_Keys_Commands
 | Emergency_Key_Functionality
 | Mobile_Security
 | Mobile_Application_Integration
 | Mobile_Mobile_Mapping
 | Status Views
 | Mobile_Dispatch_Operations
 | Queries
Item # | Mobile Data Computing Functional Requirements | Comply ( C) | Not Comply (N) | Alternative\Conversion (A) | Modification (M) | Third Party Add-On (T) | Comments
1 | General  Mobile Data Computing Features
 | Ability to operate in a Windows environment to support concurrent processing.
 | Ability for Mobile software to operate in a desktop environment.
 | Ability to provide a visual alert if Mobile is receiving negative response from CAD system (no connection to CAD).
 | Ability to continuously attempt to reconnect to CAD system in the event connectivity is lost.
 | Ability to provide screen display formats that are consistent across the application.
 | Ability to prevent other applications from automatically overlaying the Mobile application.
 | Ability to support multiple on-screen configurations based upon agency as opposed to agency type (e.g., SVFD would have a different configuration than SFD)
 | Ability for Mobile system to automatically connect to the backup environment when the primary is unavailable.
 | Mobile Application User Interface
 | Ability for user to toggle among applications on the Mobiles.
 | Ability for user to toggle among windows.
 | Ability for user to minimize or expand any window.
 | Ability to support voice commands.
 | Ability to support touch-screen functionality.
 | Ability for users to select a touch screen configuration that accommodates protective hand gear (e.g., big buttons, touch screen works with gloves on).
 | Ability to accept input from:
 | 3D barcode reader (e.g., driver's license, registration)
 | Card swipe device
 | Keyboard
 | Point-and-click devices (i.e., [NAME], trackball, touch pad)
 | Ability to provide agency system default configurations.
 | Ability for users to configure the display of their Mobiles, including:
 | Font color
 | Font size
 | Window size
 | Window location
 | Day/Night mode
 | Ability for each agency to configure the display of their Mobiles, including:
 | Font color
 | Font size
 | Window size
 | Window location
 | Ability to configure a default for the following application settings:
 | Audible message
 | Audible tones
 | Color
 | Reverse video (e.g., day/night mode)
 | Ability to store a user profile for mobile display configuration for auto-configuration upon log on.
 | Ability to allow users to return to application default settings.
 | Ability for users to select a configuration scheme that accommodates color-blindness.
 | Ability to support multiple on-screen button configurations (e.g., left side, right side, top or bottom).
 | Ability to provide visible differentiation (e.g., color) between active applications.
 | Ability to copy and paste from one application or window to another.
 | Ability to display the following information on the screen during normal operations:
 | Availability of wireless connectivity
 | Call status
 | Current unit status
 | Status of all units within the agency
 | Current system date and time
 | Incident number
 | Message alert
 | Radio talk group (if assigned)
 | Unit ID
 | Vehicle location
 | Ability for screen information to automatically refresh when information changes.
 | Ability to view multiple calls simultaneously (e.g., in different windows).
 | Ability for each agency to require any combination (including none) of the following when a user logs onto the Mobile application:
 | Name
 | User ID
 | Password
 | Personnel Number (unlimited)
 | Car number
 | Cell phone number (10-digit, including dashes)
 | Personnel in vehicle
 | Equipment
 | Special Skill
 | Mileage
 | Miscellaneous field
 | Ability to update the Mobile unit log-in information without logging on and off.
 | Ability to transfer an MDC to another apparatus.
 | [NAME]
 | Ability to support single keystroke commands.
 | Ability for each agency to define keystroke shortcuts for:
 | Common tasks
 | Status updates
 | Ability to configure a Mobile button (tool bar or function key) to launch any third-party program (e.g., Adobe, CAMEO, etc.).
 | Emergency Key Functionality
 | Ability to initiate an emergency message transmission from a touch screen button or hot key.
 | Ability to automatically transmit the following information in an emergency situation:
 | Last known location
 | Current location (with AVL)
 | Reference to incident
 | User ID
 | User name
 | Ability to configure emergency key to capture agency defined combination of above information.
 | Ability to provide a delay between emergency key activation and notification (to allow users to cancel emergency if button was hit accidentally).  Indicate within the "comments" section how this is configured (e.g., configured by agency, standard time, etc.)
 | Ability to have a visible and audible indication that emergency key has been activated (in all units).
 | Ability for dispatch to select which consoles receive visible/audible alerts of emergency key activation.
 | Ability to link emergency key functionality to PTT radio activation.
 | Ability to send to all Mobile and CAD users (except the sender) an emergency notification with unit ID and location (if known) when the emergency key is activated.
 | Ability for each agency to configure which Mobile users receive the emergency key activation notice (e.g., only PD receives PD emergency key activation, only identical agency receives notification, etc.)
 | Ability to prevent emergency notification from appearing on the sender's screen.
 | Ability for the Mobile screen to revert to its prior view after the user dismisses an emergency message.
 | Ability to automatically send location coordinates and unit ID upon triggering an emergency key.
 | Security
 | Ability to logon multiple individuals per unit.
 | Ability to assign an individual to a unit at any time from within the mobile application.
 | Ability to remove an individual from a unit at any time from within the mobile application.
 | Ability, when there are multiple users logged onto one Mobile to allow one user to logoff the system while allowing another to remain logged on.
 | Ability for a resource to be logged on but not available for service.
 | Ability for a unit logged on to automatically default to "available" status.
 | Ability to logoff personnel without logging off the associated apparatus (e.g., firefighters changing shift).
 | Ability to logoff a Mobile and remain logged into CAD system.
 | Ability for a user to logoff the system and save information on the Mobile including:
 | In-progress reports
 | Messages
 | Notes
 | Query returns
 | Ability to store the following until manually deleted by the user:
 | In-progress reports
 | Messages
 | Notes
 | Query returns
 | Ability to support a user-initiated download of software/files at logon without interfering with operational performance.
 | Ability to support an automatic download of software/files at logon without interfering with operational performance.
 | Ability to separate Mobile logoff from designating status as off-shift.
 | Application Integration
 | Ability to view all incident information available in CAD on the Mobile.
 | Ability for mobile status updates to be reflected in CAD.
 | Ability to run multiple applications (e.g., mobile, automated field reporting) on the Mobile at the same time, with CAD operations having precedence over reporting operations.
 | Ability to receive dispatch alerts and/or indicators without losing current work.
 | Ability for alerts created in CAD or RMS or FRMS to be made available to users in the Mobile environment.
 | Ability to access reports within the RMS when responding to a location (e.g., hyperlink)
 | Ability to access reports within the FRMS when responding to a location (e.g., hyperlink)
 | [NAME]
 | Ability for map to function without wireless connectivity.
 | Ability to support AVL functionality.
 | Ability to cache map layers to minimize the amount of data transmitted wirelessly.
 | Ability to update unit and incident locations on map without resetting the entire map.
 | Ability to display compass direction between two user selected points.
 | Ability to select map layers for display.
 | Ability to center map display on:
 | Current vehicle location (with AVL)
 | Midpoint between vehicle location and dispatch location
 | Dispatch location
 | Vehicle activating emergency activation key
 | Specified geographic area (e.g., entering an address via text entry)
 | Incident location
 | Ability for user to access apartment complex maps upon clicking on the location for a complex (assuming user-created map layer containing site maps).
 | Ability to accept temporary overlays (e.g., crime analysis hot spot map)
 | Ability to display any premise and hazardous information alerts on the map.
 | Ability to "drill down" within the map to provide additional information related to that location.
 | Ability to display other field units on mobile map (assuming AVL and sufficient bandwidth) as defined by each agency.
 | Ability to make temporary "marks" on map (e.g., to note locations of a law enforcement perimeter or the locations of fire apparatus at a large scene).
 | Ability to display active incidents and unit statuses on the map.
 | Ability to click on a unit or incident in the incident queue or unit status bar and have it displayed on the map.
 | Ability to click on a unit in the map display and have the corresponding incident information displayed.
 | Ability for mapping client to load automatically upon system boot.
 | Ability to filter display by applicable fields, including but not limited to:
 | Agency
 | Unit type
 | Unit status
 | Incident type
 | Incident priority
 | Officer name
 | Vehicle type (e.g., Fire apparatus only)
 | Incident number
 | Response area
 | Routing
 | Ability to provide audible routing information.
 | Ability to provide text-based routing information.
 | Ability to automatically calculate directions from user's current location (on Mobile using AVL) to dispatched location.
 | Ability to support quickest-time routing for all dispatches.
 | Ability to support shortest route for all dispatches.
 | Ability to provide estimated travel time.
 | Ability to highlight on the map the recommended route from current location to a dispatched incident site.
 | Ability to recalculate directions to incident/specified location on the fly.
 | Ability to take into account the following when calculating routing directions:
 | Street speed limits
 | Closed streets
 | School zones
 | Hazards by time of day (e.g., school opening/closing)
 | Dispatch entered obstacles
 | Mobile user entered obstacles
 | Distance between vehicle and incident location
 | Height limitations on overpasses
 | Weight limitations
 | Train crossings
 | Ability for Mobile user to turn recommended route ability on/off.
 | Ability to clearly display potential obstacles along route.
 | Ability to record all routing displays within CAD (e.g., map displays, travel time, travel time estimation, etc.) for analysis to improve routing logarithms.
 | Ability to automatically rotate map so that unit is automatically displayed moving up on the display.
 | Status  Views
 | Ability to view pending calls.
 | Ability for a field user to assign themselves to a call without the use of a command (e.g., double-click via mouse, touch screen, etc.)
 | Ability to view active calls.
 | Ability to  view unit status by:
 | Response area (e.g., beat, sector, fire district, etc.)
 | City
 | Individual unit/apparatus
 | Squad/company
 | Ability to open any active incident to view dispatch data, units and incident notes.
 | Ability to view personnel on each apparatus in real-time.
 | Mobile Dispatch Operations
 | [NAME]
 | Ability to receive dispatches on the Mobile.
 | Ability for dispatches to open automatically on mobile computers.
 | Ability to alert mobile users that a new dispatch has arrived:
 | Audible alert
 | Visual alert
 | Ability for all personnel dispatched to an incident to receive notification when other personnel are en route.
 | Ability for all personnel dispatched to a call to receive notification of status and location changes of other personnel dispatched to the call.
 | Ability to access and read all call comments associated with a call regardless of whether assigned to the call.
 | Ability to display the following information in distinct fields or tabs (as opposed to in the call narrative) upon receipt of dispatch:
 | Assisting unit(s)
 | Comments/narrative (unlimited)
 | Date and time incident entered
 | Driver registration information
 | HAZMAT code and instructions
 | HAZMAT status
 | Incident location with cross streets
 | Incident priority
 | Incident type
 | Incident talk group
 | Number of previous calls at a location
 | Hyperlinks to previous calls
 | Pre-plan information
 | Suspect information:
 | Name
 | Description
 | Location
 | Associates
 | Phone number at incident location (if different)
 | Vehicle information
 | Premise and prior information flag
 | Premise information
 | Recommended route
 | System generated incident number
 | Weapons involved
 | Associated Hazards/BOLOs
 | Agency-defined (i.e., differing between Fire and Police)
 | Ability for all agencies to see incident information sent to other agencies dispatched to the same incident.
 | Incident Updates
 | Ability to display most current incident data at the top of the screen.
 | Ability to receive supplemental incident information (e.g., location, suspect, vehicle information, etc.) without interrupting or overlaying current screen.
 | Ability for incident data to be updated in real-time without user intervention (e.g., incidents, unit statuses, call comments, etc.).
 | Ability for supplemental information to be visually distinct from information previously received by Mobile user (e.g., separate font color, highlighted, etc.).
 | Ability to have different types of information on different screens (e.g., tabs - one for current incident, one for related premise history, etc.) such that users can easily filter or access information. [indicate the number of tabs/screens that can be supported within the comments section]
 | Ability to transmit status information to the CAD system in real time.
 | Premise and Hazard Information
 | Ability to alert user of availability of information associated with a location (gate codes, hazards, premise history, pre-plans, etc.).
 | Ability to indicate type of information that is attached to a call (e.g., gate code, hazard, etc.).
 | Ability for field units to have the option of pulling up or not pulling up  information attached to the call.
 | Ability to drill down in premise history to find links to incidents, persons, vehicles, etc.
 | Ability for each agency to configure icons to indicate type of hazard.
 | Ability to drill down into icon to determine associated hazard information.
 | Ability to retrieve fire pre-plan information in the mobile environment.
 | Ability to pull up a previous call in a premise history file and show any hazards that were valid at the time of the call.
 | Field Initiated Calls for Service
 | Ability to initiate a call for service from the Mobile, including:
 | Call for service
 | Traffic stop
 | Administrative activity (e.g. training, field inspections, etc.)
 | Other Agency defined call types.
 | Ability to initiate a call for service with a function-key.
 | Ability, with appropriate supporting mapping/AVL technology, to indicate unit/incident location when initiating an incident from the field.
 | Perimeters
 | Ability to automatically generate a perimeter upon entry of a location and perimeter distance (e.g., set a 3 block perimeter around 300 Main St.).
 | Ability to receive suggested perimeter positions from dispatch.
 | Ability for suggested perimeter positions to appear on the mobile map upon receipt.
 | Call Disposition
 | Ability to clear calls from the Mobile.
 | Ability to require a call clearance code in order to clear a call from the Mobile.
 | Ability for each agency to have their own unique disposition codes and not be presented with disposition codes used by other agencies (e.g., fire only sees fire disposition codes).
 | Ability to select disposition code from a drop-down list.
 | Ability to provide a text field for disposition comments.
 | Ability to reject a disposition if unsuitable for the incident type.
 | Ability to change the final call type and disposition from the Mobile environment based upon agency.
 | Queries
 | General Queries
 | Ability to automatically notify user when query information has been queried within an agency-defined time frame "delayed inquiry hit"(e.g., querying a license that has been queried in the past hour by another user) from the following systems:
 | CAD
 | Law Enforcement RMS (with permission)
 | Fire RMS (with permission)
 | WACIC/NCIC
 | COPLINK
 | Any databases interfaced to CAD
 | Ability to search and query all appropriate databases without impacting dispatching performance.
 | Ability to query all linked databases via a single query.
 | Ability to query and retrieve premise information for an address not associated with a call for service.
 | Ability to initiate queries with a single key stroke.
 | Ability to use predefined data entry forms/screens (masks).
 | Ability to provide pre-defined data entry/query forms, including, but not limited to:
 | Articles
 | Accident Investigation
 | Driver license query
 | Incident status
 | Location
 | License plate query
 | Logon/logoff
 | Missing person information
 | Name query
 | SSN #
 | Premise information query
 | Previous events
 | Vehicles
 | Ability to access query forms by:
 | Command line entry
 | Drop down menus
 | Dedicated function keys
 | Unit History Queries
 | Ability to query unit history detail by:
 | Date and time range (i.e., start and end dates or times)
 | Agency
 | Apparatus ID
 | Officer name
 | Personnel ID
 | Time on call
 | Unit ID
 | Incident Queries
 | Ability to query and retrieve incident records by one or more of the following factors:
 | Any operator ID associated with the incident
 | Any unit ID assigned to the incident
 | Agency
 | Apparatus ID
 | Caller number
 | Case number
 | Cross streets
 | Date and time range (e.g., start and end data and time parameters)
 | Disposition codes
 | Unit ID
 | Officer name
 | Personnel ID
 | Geographic area (e.g., area, beat, sector, grid etc.)
 | Incident number
 | Incident priority
 | Incident type
 | License plate
 | Location or partial location
 | Name (suspect, reporting party, witness, victim)
 | Ability to query incidents geographically (e.g., draw on the map).
 | License Plate Queries
 | Ability for authorized users to enter vehicle stops on the command line or entry form and automatically run the license plate against all available relevant databases.
 | Ability for authorized users to conduct multiple license plate searches simultaneously.
 | Ability to save all previous license plate searches until user clears data.
 | Ability for authorized users to automatically run the registered owner of the vehicle in a license plate query return.
 | Ability to automatically populate a query mask and query driver's license information upon scan of a driver's license.
 | Ability to automatically populate the vehicle mask and query the vehicle when scanning the registration.
 | [NAME]
 | Ability to save all query returns until user clears data.
 | Ability to save all stored query returns after logoff (e.g., returns are still there the next time user logs onto the system).
 | Ability to attach any database query return to incident records.
 | Ability to drill down into query returns regarding a potentially hazardous subject, vehicle, and/or location to find the details of that hazard.
 | Ability to sort query results on any returned field.