Spreadsheet: 189e7500-2c3c-451b-8252-51033e8fccb9
Sheet: RMS Field Reporting

Spokane County Request for Proposals #P8705
Public Safety Information Systems Replacement Project
Field Reporting Requirements
 | 'Field Reporting'!B17
 | 'Field Reporting'!B31
 | 'Field Reporting'!B48
 | 'Field Reporting'!B189
 | 'Field Reporting'!B247
 | 'Field Reporting'!B255
 | 'Field Reporting'!B265
 | 'Field Reporting'!B275
Item # | Field Reporting Functional Requirements | Comply ( C) | Not Comply (N) | Alternative\Conversion (A) | Modification (M) | Third Party Add-On (T) | Comments
1 | General Field Reporting Requirements
 | Ability to enter incident reports either:
 | In the desktop environment
 | In a mobile environment
 | Ability to attach an MO to an incident.
 | Ability to attach an MO to a person.
 | Ability to link case report to a related call for service record.
 | Ability to associate event class with a CAD incident number.
 | Ability to handle multiple case reports (e.g., originals, supplementals) per CAD incident.
 | Ability to link all associated reports and forms to a common report number (e.g. citations, tow reports, arrest reports, criminal complaint,  etc.).
 | Ability to provide a day/night mode.
 | Ability to initiate queries into one or more databases from within the field reporting application.
 | Ability to accommodate a multi-jurisdictional environment and allow users to indicate with which jurisdiction they are entering the report.
 | Ability for an agency to take a report outside of its jurisdiction and not have that report affect statistics or be fully imported into the RMS (i.e., [NAME])
 | Application Integration
 | Mobile Integration
 | Ability to automatically logon to the field reporting application upon logon to the Mobile application.
 | Ability to toggle between the field reporting and Mobile client (including mobile mapping) applications.
 | Ability to receive dispatch alerts and/or indicators while field reporting application is in use.
 | Ability to incorporate coordinates from mobile mapping into field report.
 | RMS Integration
 | Ability to provide external system query functionality and features available in the RMS in the field reporting software.
 | Ability for all fields in the field reporting module to have corresponding data elements in the RMS application.
 | Ability to update data in the RMS application as soon as the report approval process is completed.
 | CAD Integration
 | Ability to initiate a field report for the primary officer upon entry in the CAD application of a disposition code for a call type requiring a report.
 | Ability for CAD incident data to automatically populate a report.
 | Ability for CAD call comments to automatically populate a report.
 | Ability for agency to define which CAD data populates a report.
 | Ability to automatically transfer the incident number from CAD to the AFR.
 | Ability for CAD system to assign report to the appropriate agency based upon incident location.
 | Report Writing
 | Report Workload Management
 | Ability to work on multiple reports and multiple incidents simultaneously and toggle among them at the user's discretion.
 | Ability to save reports in progress.
 | Ability to notify user upon exiting the reporting application of reports not yet completed based upon report type.
 | Ability for multiple personnel to work on the same incident simultaneously.
 | Ability to resume work on a saved report at the exact location in report completion process with no loss of data.
 | Ability to automatically save incomplete reports at the network level so that a user can access the report at a later time from a computer other than the one used to start the original report.
 | Ability to save reports locally.
 | Ability to automatically save incomplete reports locally (e.g., auto-save).
 | Ability to clearly indicate as to where the report is being saved (i.e., locally or on the network level).
 | Ability to enter data when offline.
 | Ability to upload reports automatically upon re-establishing wireless connectivity.
 | Ability to enter, in the field, data required for any report (e.g., case report, traffic, DUI, etc.).
 | Ability to begin to write a report prior to entering a call disposition.
 | Ability to track the status of reports (e.g., unwritten, incomplete, awaiting approval, approved, etc.) at logon to the Mobile application.
 | Ability to display the following field reporting information upon logon to the Mobile system:
 | Rejected reports
 | Reports awaiting approval
 | Reports awaiting follow up investigation
 | Recently approved reports
 | Reports incomplete
 | Ability for supervisors to see which reports have not been completed at the end of the shift.
 | Ability to reconcile reports and display those reports still outstanding.
 | Report Initiation
 | Ability for each agency to define call types that require an incident report to be written.
 | Ability to generate a CAD incident number from the field reporting application.
 | Data Entry
 | Ability to provide dedicated fields to capture all information required for NIBRS reporting.
 | Ability to accommodate NIBRS-defined business logic.
 | Ability to maintain compliance with NIBRS requirements (both field values and business logic).
 | Ability to provide dedicated fields to capture all information required for CLERY reporting.
 | Ability for each agency to modify business logic.
 | Ability to enter data in a non-conventional manner (e.g., not require personnel to enter data in a prescribed sequence).
 | Ability to provide dedicated fields to capture name information for:
 | Suspects
 | Arrested Individuals
 | Victim Business
 | Witnesses
 | Victims
 | Complainants
 | Other persons
 | Ability to provide dedicated fields to capture offense information for multiple offenses.
 | Ability to provide dedicated fields to capture location information for:
 | Involved persons
 | Involved incident locations
 | Ability to accommodate foreign addresses.
 | Ability to provide dedicated fields to capture property information:
 | Type/Category
 | Quantity
 | Descriptors
 | Value
 | Make
 | Model
 | Brand
 | Recovered Date
 | Recovered Location
 | Agency-defined fields
 | Ability to capture all property data fields in the field that are captured within the RMS property module.
 | Ability to provide a report summary field.
 | Ability for multiple officers to provide input to a single incident once it is created and report number assigned.
 | Ability to support input via:
 | Bar code readers
 | Card swipe device
 | [NAME]
 | Touch screen
 | [NAME]
 | RFID-types
 | Voice Command
 | Ability to provide basic word processing capabilities on narrative and comment fields, including, but not limited to:
 | Text wrap
 | Paragraph formatting
 | Use of bullets and numbering
 | [NAME] check
 | [NAME]
 | Copy and paste
 | Ability to incorporate drag and drop functionality.
 | Ability to modify the spell check dictionary (e.g., add agency-specific acronym exceptions).
 | Ability to accelerate routine data entry tasks (i.e., workflow functionality) with the following:
 | Code-driven drop-down menus
 | Type ahead based on dropdown menus
 | Shortcut keys (e.g., BR = Brown)
 | Default menus
 | Ability to override auto-population capability.
 | Ability to support auto-population of data fields based upon master name files from the RMS.
 | Ability for any auto-populated data fields to require user validation (e.g., when auto-populating address, system prompts user to validate current data)
 | Ability for each agency to configure the auto-population validation capability.
 | Ability to restrict user's ability to use master files when entering data based upon:
 | Officer
 | Agency
 | Ability to enter an unlimited number of:
 | Persons
 | Property
 | Vehicles
 | Offenses
 | Ability to automatically translate standard text (e.g., offense type, property type, location type, descriptors, etc.) entries into NIBRS and NCIC codes.
 | Ability to associate text entries to appropriate code tables.
 | Ability to accommodate reports for non-criminal activity (e.g., informational).
 | Ability to include codes for non-criminal activity in offense code table (e.g., for incidents that do not involve criminal activity but which the County would like to track - domestic disputes, for example).
 | Ability to populate incident report with information already in the system (e.g. incident information, name information, etc.).
 | Ability to populate incident report with query returns.
 | Ability to provide user entering a name with a list of potential existing master name records based on a variety of criteria, including:
 | Exact spelling
 | Partial name
 | Sound-alike searching
 | Phonetic replacement
 | Diminutive first names
 | Ability for each agency to create a dictionary of standard language templates for reports that officers input frequently (e.g., auto-narratives).
 | Ability to prompt user to complete any mandatory fields not completed.
 | Ability to capture electronic signatures.
 | Ability to scan and attach signatures.
 | Ability to provide an online tool to draw crime scene diagrams.
 | Ability to define mandatory fields.
 | Ability to prevent appearance on a data entry screen of a field for which a value should not be entered.
 | Ability to identify mandatory fields based on crime type.
 | Ability to identify all required forms based on crime type.
 | Ability to limit available values in subsequent code tables based on an entered crime type.
 | Ability to distinguish between mandatory and optional fields.
 | Ability to validate data entry to ensure all required fields have been completed.
 | Ability to validate data at submission.
 | Ability to validate data to ensure that only valid codes have been used.
 | Ability to validate any data field that requires master index data against master indices.
 | Ability to validate any address information entered into the report against the CAD geofile.
 | Ability to override geovalidation errors.
 | Ability to suggest a remedy for errors.
 | Additional Report Forms
 | Ability to identify all required forms based on the offense type.
 | Ability to override required forms.
 | Ability to populate data across report forms to eliminate redundant data entry.
 | Ability to populate data across reports for multiple incidents.
 | Ability to complete a single report form that is applicable to multiple incidents (e.g., electronic duplicate).
 | Ability for corrected data in a field to auto populate across related report forms.
 | Ability for County to design reports and forms.
 | Create Supplemental Report
 | Ability to create supplemental reports associated with a submitted and approved initial case report.
 | Ability to permit users to complete supplemental reports in the Field Reporting system before the original report is submitted to RMS.
 | Ability for multiple personnel to simultaneously create and add supplemental reports regarding the same incident.
 | Ability for investigators to create supplemental reports to document follow-up investigations.
 | Ability for supplemental reports to be processed through a report approval process.
 | Ability to link supplemental reports to the original case report.
 | Ability to pre-fill supplemental reports with information already in system.
 | Report Submission
 | Ability to support the wireless access of a report by the report author.
 | Ability to support wireless approval of the same report by a field supervisor (i.e., not require a user to log onto a wired terminal)
 | Ability to automatically resend lost data packets until automated field reporting send is successful.
 | Ability to send confirmation indicating automated field reporting upload was completed successfully.
 | Ability to save a copy of an active report locally until the user receives confirmation of receipt of data from the RMS.
 | Ability upon receipt of report into the RMS, for the report to be locally removed from the AFR application.
 | Ability to support multiple reports simultaneously.
 | Ability to automatically maintain a log of automated field reporting transactions, including, but not limited to the following information:
 | Date and time of transmission
 | Workstation ID
 | Report ID
 | User ID/name
 | Ability to conduct a data verification and validation process prior to submitting a report for review.
 | Ability to ensure that reports are compliant with NIBRS reporting requirements prior to submission.
 | Ability to ensure that reports are compliant with CLERY reporting requirements prior to submission.
 | Ability to prevent submission of a report with data entry errors.
 | Ability to prompt officer as to which fields require correction.
 | Ability to describe the nature of the correction required.
 | Report Approval
 | Ability to configure the automated field reporting system to support agency-specific processes/workflow.
 | Ability for each agency to determine which type of reports require approval (e.g., arrest/incident vs. field interview).
 | Ability for any edits made to a report to undergo a re-validation process.
 | Ability to indicate approving supervisor on any additional supplements (e.g., additional narrative) entered into a previously approved report.
 | Ability for officers to submit reports electronically to their supervisors for review and approval.
 | Ability for officers to submit a report to a supervisor "group" rather than an individual supervisor.
 | Ability for officers to indicate that a report requires immediate supervisor attention.
 | Ability for  supervisors to receive, review and approve incident reports online.
 | Ability for supervisors to edit submitted reports.
 | Ability for each agency to identify what data elements may be edited by a supervisor (e.g., only edit the location field but restrict edits from being made within the narrative).
 | Ability for any edits made to a submitted report to be logged within an audit trail, identifying data changed and individual making edits.
 | Ability to provide the supervisor the option of approving the report or returning the report to an officer for corrections.
 | Ability for supervisors to attach electronic to notes to a report to indicate to the officer areas that need to be corrected.
 | Ability to track status of errors/corrections notifications by the following:
 | Author
 | Case number
 | Offense code
 | Reviewer/supervisor
 | Date
 | Ability to automatically notify appropriate supervisor when their subordinate has a returned report.
 | Ability to delete corrective messages after a report has been approved by a supervisor.
 | Ability to track the status of reports (e.g. unwritten, incomplete, awaiting approval, approved, etc.).
 | Ability to generate a report identifying status of reports (e.g., shows reports outstanding, incomplete, awaiting approval).
 | Ability for supervisors to know that they have outstanding reports to review.
 | Ability to send recurring notifications to officers regarding reports needing corrections.
 | Ability to reconcile field reports with CAD calls to identify incomplete or missing reports.
 | Ability when a report is being reviewed to prevent other users from reviewing the same report (e.g., prevent multiple users from simultaneously reviewing a report for approval).
 | Ability to provide a function that returns the report to the approval queue if not approved within an agency-defined time frame (e.g., supervisor has 2 hours to review an open report).
 | Ability to return reports to the report approval queue.
 | Ability to automatically route reports to appropriate users based on agency-defined business logic (e.g. to investigators based on crime-type).
 | Ability for Records staff to complete an accuracy review for reporting requirement compliance prior to adding report to the RMS database.
 | Report Access
 | Ability to access all reports from the field.
 | Ability to restrict access to report (permission based, e.g., internal investigators only).
 | Ability to indicate reports that have not been approved, yet are available for viewing.
 | Ability to create and maintain distribution lists based on user-defined criteria.
 | Ability to access and update submitted automated field reports from the field prior to report approval.
 | Ability to query information in an incomplete or unapproved report.
 | Field Contacts
 | Ability to electronically link field contact record to master indices.
 | Ability to automatically update master indices upon creating a new field contact record.
 | Ability to document multiple people on one field contact record.
 | Ability to document multiple vehicles on one field contact record.
 | Ability to auto-populate the field contact fields with any information captured within CAD.
 | Ability to track and associate a field contact record with an incident/case number.
 | Ability to hyperlink a field contact record to the related CAD incident.
 | Arrest/Incident Reporting
 | Ability to enter individual arrest information.
 | Ability to enter mass arrest information.
 | Ability to link information entered in the arrest database to all other applicable modules to eliminate the potential for duplicate data entry.
 | Ability to populate an arrest report with information already entered into a case report.
 | Ability to provide drop down menus as appropriate for data entry (e.g., offense, statute, NIBRS codes, etc.).
 | Ability to automatically populate relevant fields of the arrest module with data already in the Master Name Index (MNI).
 | Ability to attach an MO to an incident as opposed to a person.
 | Ability to document incident and arrest information, as required by NIBRS.
 | Ability to clear multiple incidents with one arrest.
 | Towed Vehicles
 | Ability to provide a towed vehicle form that captures all information as described in the RMS.
 | Ability to populate the towed vehicle form with:
 | Incident data transferred from CAD
 | Person data entered into associated reports (e.g., citations, crash reports, incident reports, etc.).
 | Vehicle data entered into associated reports (e.g., citations, crash reports, incident reports, etc.).
 | Location data entered into associated reports (e.g., citations, crash reports, incident reports, etc.).
 | Ability to email towing form.
 | Ability to print the towing form.
 | Ability to capture electronic signatures.
 | Pre-Booking Requirements
 | Ability to enter individual arrest information.
 | Ability to enter mass arrest information.
 | Ability to link information entered in the arrest database to all other applicable modules to eliminate the potential for duplicate data entry.
 | Ability to populate an arrest report with information already entered into a case report.
 | Ability to link an arrest report number with an incident report number.
 | Ability to provide drop down menus as appropriate for data entry (e.g., offense, statute, NIBRS codes, etc.).
 | Ability to automatically populate relevant fields of the arrest module with data already in the Master Name Index (MNI).
 | Ability to provide dedicated fields to capture all data fields as required by the Spokane County Jail.  These forms and/or specific data fields may be made available upon request.
 | Ability for the County to add data elements to the pre-booking form.
 | Ability for the County to remove data elements from the pre-booking form.