Loading...
HomeMy WebLinkAboutCORRESPONDENCE - RFP - P847 COMPUTER AIDED DISPATCHA CompuDyne Company Tiburon, Inc. 11211 Taylor Draper Lane, Suite 300 Austin, Texas 78759 Tel: 512/345-8613 Fax: 512/345-8615 www.tiburoninc.com Tiburonâ August 28, 2003 Correspondence: P1263-01-gr Larry Vail Fort Collins Public Safety Project P.O. Box 580 Fort Collins, CO 80522-0580 Subject: Proposal and Commitment to Resolve Functional Issues Reference: The System Implementation Agreement between the City of Fort Collins and Larimer County and Tiburon, Inc. for Computer Aided Dispatch, Records Management System, Field Automation System, Civil Process, and Corrections Management System dated June 30, 2003. Mr. Vail: This letter is to document our response to the product related issues deemed “high priority” by the Fort Collins – Larimer County. These issues are items identified during the recently completed 30-day Product Validation exercise. The format of this response is as follows: A General Position Statement Furnished by Fort Collins-Larimer County Section I – CAD/MDS Specific Issues Priority Issue # - <title> Position Statement from Fort Collins-Larimer County Reference Material submitted by Fort Collins-Larimer County Tiburon Address of the Issue Tiburon Commitment regarding this Issue There are four sections, one for each of the Tiburon Products. A GENERAL POSITION STATEMENT FURNISHED BY FORT COLLINS-LARIMER COUNTY It is expected that all priority issues will be addressed as a part of the implementation of the Tiburon products. If not addressed as a part of the 7.3.3 product, then all priority issues must be addressed by the completion of task 21 of the Statement of Work (system upgrade), that will occur within six months of the completion of Task 20 of the Statement of Work. Tiburon must reply to these issues with a clear action plan that states the proposed solution and that sets a fixed timeline for issue resolution. Priority issues must be addressed to the satisfaction of the CRISP project manager before the project can move forward. Mr. Larry Vail Page 2 Subject: Proposal and Commitment to Resolve Functional Issues 4/17/2023 SECTION I – CAD/MDS SPECIFIC ISSUES Priority Issue 1 – Phase II Wireless Position Statement from Fort Collins-Larimer County Phase II wireless functionality - Tiburon estimates approximately six weeks of work to get phase II to work as specified by CRISP. Debate going on internally at Tiburon as to if this will be a base line fix. This is seen by CRISP as a part of addressing all X-Y issues. Reference Material submitted by Fort Collins-Larimer County 2-5.3 (1) - ****CRITICAL FUNCTIONALITY**** The proposed application shall be APCO phase II wireless compliant (i.e., Should follow FCC standards for Phase II wireless and Qwest ANI/ALI format 30W) as provided to Tiburon. 3-7.1 (3) - The proposed application shall have the ability to receive and accept geographic coordinates from a cellular telephone carrier and display the location of a cellular caller on a map (phase 2 wireless). X-Y Coordinates - At minimum the ability to enter the X-Y coordinates for any location stored in the system. Ideally the ability to move a mouse pointer over a map (with a continuous, running x-y display next to the pointer) with the ability to click to initiate an incident by the displayed X-Y and/or populate an existing incident or other location with the displayed X-Y. Tiburon Address of this Issue Below is Tiburon’s plan for Wireless E9-1-1 development. 1. AVE will be required to obtain Phase II 911 wireless capabilities Polygonal (RD) data will exist in AVE and will be accessible via an assigned name or coordinate (X/Y or lat/long) 2. The Tiburon E911 interface module will be changed to parse for the wireless latitude/longitude coordinates 3. The incoming latitude/longitude coordinates will be converted to an address, based on the following:  2 configurable parameters will be available, minimum and maximum distance  If the coordinate is within “minimum distance” of the nearest premise address, common place address, or intersection, then that address will be used as the geo-verified location.  If the coordinate exceeds the “maximum distance” of the nearest premise address, common place address, or intersection, then the RD record name will be used as the geo-verified location.  If the coordinate is between the “minimum distance” and the “maximum distance” of the nearest premise address, common place address, or intersection, then that address will be used as the geo-verified location. The location description will contain a descriptive statement providing a direction and distance of the caller relative to the location returned. Mr. Larry Vail Page 3 Subject: Proposal and Commitment to Resolve Functional Issues 4/17/2023 4. The lat/long and X/Y will be stored in the call history. It will be prominently displayed in the dispatch and recall windows, Query Incident History outputs, and dispatch messages. 5. The Calls-for-Service call history will be changed to accept the lat/long and X/Y from the transfer and store it in the database. Note: Existing history addresses will not be converted to a lat/long. 6. CARS will be changed to accept and store the lat/long. 7. If mapping is provided, the map will be zoomed on receipt of the call information at the workstation from the Tiburon E911 interface module, instead of when the event is entered or the address verified. The map will reflect the position (coordinates) of the caller as reported in the 911 data. Indications reflecting the accuracy of the reported location will be provided on the map, when available from the 911 vendors. 8. Based on lat/long coordinates for cursor position on a map, the user will have the ability to initiate call entry from cursor position on the map. (Only Maverick mapping has this capability. This is a mapping vendor limitation.) 9. User will have the ability to enter lat/long or X/Y coordinates as a location when entering a call. The location will be verified based on the above described scenarios. 10. Client has asked for the ability to show X/Y on the map when moving the cursor. Both map vendors (Maverick & Plant) put that information on the bottom right portion of the screen as when you stop the cursor the location is displayed on the map next to it. Tiburon Commitment Regarding This Issue Design and development of the functionality described in the previous section will be part of the UNIX CAD/2000 system being purchased by Fort Collins. It is anticipated that this enhancement will be made generally available to the Fort Collins project by July 2004 or earlier. SECTION 2 – RMS/ARS SPECIFIC ISSUES Priority Issue 1 – ARS Supplemental Report Transfer Position Statement from Fort Collins-Larimer County Names, property, charges, or vehicles entered into ARS as part of a supplement DO NOT transfer to RMS. This information has to be entered again into RMS. This is of significant concern since this would cause the CRISP agencies to do duplicate entry in order to keep the databases in-sync. This is an issue at NIBRS sites. Tiburon says they will fix this but the fix is indeterminate. RMS fails to pass SAR because of this issue. Reference Material submitted by Fort Collins-Larimer County 4-4.1 (7) - The proposed mobile field reporting application shall require data be entered only once and use that data in all other needed forms and reports. Tiburon Address of the Issue Mr. Larry Vail Page 4 Subject: Proposal and Commitment to Resolve Functional Issues 4/17/2023 The proposed solution is an attempt to minimize the duplicate entry that is now required while transferring supplements, although some review by the operator importing the supplement will still be required. The following process rules are applied: 1. Automatic property updates are limited to recovery data. 2. Automatic person updates are limited to the addition of new persons. 3. The current tickler/e-mail notification will be expanded to include more data. 4. Person/property/vehicle records will be transferred into a holding queue to be reviewed and processed by the IBRS administrator/clerks. 5. A new browser query will be created to retrieve these records from the temporary holding file. It will be possible to query these records by Case Number or Incident Date range. 6. Each of the records from the holding file will have three actions to choose from (Update, New, Remove). 7. The UPDATE button will modify the existing record in the database. Any information in the holding record will replace the information in the RMS Incident NIBRS record. This would be used for recovery of property or vehicle information. Any other updates will need to be handled manually because of the complications with figuring out which fields need to be updated and linked. 8. If the NEW action is selected then the record will be added into the RMS Incident NIBRS database. Since there are many complicated factors for modifying already existing person records, NEW would be the only option for supplemental person records. Any updates would need to be handled manually. 9. If the REMOVE action is selected, the record will be removed from the holding queue and no action will be taken. Any updates to the RMS Incident NIBRS database will need to be handled manually. Tiburon Commitment Regarding This Issue Design and development of the functionality described in the previous section will be part of the UNIX RMS/2000 system being purchased by Fort Collins. It is anticipated that this enhancement will be made generally available to the Fort Collins project by July 2004 or earlier. SECTION III – CMS SPECIFIC ISSUES Priority Issue 1 – Name Search Functionality Position Statement from Fort Collins-Larimer County The system reviewed lacks the ability to look up by name within the application itself - outside of the browser alpha search. A search is provided for jail ID and booking number and by inmates in custody. These criterion, while necessary and effective, should be available in addition to basic name search functionality and not in place of it. Although this issue has been discussed many times before, it is being restated to ensure Tiburon is clear that this issue must be addressed. Mr. Larry Vail Page 5 Subject: Proposal and Commitment to Resolve Functional Issues 4/17/2023 Reference Material submitted by Fort Collins-Larimer County (SIA exhibit 8 - Fort Collins ~ Larimer - Functionality Enhancement Document) Name Lookup and Entry - It is required that all CMS functions be capable of being driven by name rather than booking number, and that all data entry and modification processes are initiated and manipulated from a single application/client (including mugshot display). Tiburon has indicated that this functionality is planned for an upcoming release of the product. By accepting this document Tiburon Incorporated is required to provide this functionality to the CRISP agencies. A timeline for delivery must be disclosed and honored. Tiburon Address of the Issue Tiburon recognizes the need for efficient, intuitive and comprehensive database queries into the Corrections system. By gathering input from our client base and setting goals and priorities with our steering committee we now offer the following name search functionality within CMS: 1. All CMS bookings can now be initiated through the GUI name search that is located within the CMS transaction menu. The same name search is also built into the Browser menu allowing the CMS application to be launched from the Browser as well as through the traditional GUI menu. Starting the booking process through the name search allows the booking officer greater flexibility in identifying an inmate and maintains database integrity in building a history of bookings using the same unique combination of JID and MNI instead of assigning multiple identifiers across individual bookings. 2. At the request of our CMS steering committee a name search is being added to the CMS Incident Disciplinary Module to allow easier access to all of inmates disciplinary records. 3. At the request of our CMS steering committee a name search function is being added to the CMS Programs Module allowing for quick access to a complete list of all an inmates scheduled and historical programs/classes. 4. The current in-custody name search has been enhanced to return the current booking data and all historical bookings. The current booking data is always returned first. 5. The existing CMS in-custody name search will be enhanced to allow for non- custody names to be searched for historical bookings. 6. The general system name search will be enhanced with the ability to launch the CMS application when a name is returned that has a valid CMS jail identification number (JID). This is additional functionality from what is described in item number 1. 7. The Victim Witness Module will be enhanced with a name search function to allow access to the Victim Witness database by either inmate name or victim name. Tiburon Commitment regarding this Issue Design and development of the functionality described in the previous section will be part of the UNIX CMS/2000 system being purchased by Fort Collins. It is anticipated Mr. Larry Vail Page 6 Subject: Proposal and Commitment to Resolve Functional Issues 4/17/2023 that this enhancement will be made generally available to the Fort Collins project by July 2004 or earlier. SECTION IV – Civil (CPS) SPECIFIC ISSUES Priority Issue 1 – Overall Functionality Position Statement from Fort Collins-Larimer County Replacing the current Civil System used by the Sheriff’s Office with the Tiburon Civil module will represent a significant loss in functionality. While some issues can be addressed to a certain degree using Crystal reports this will not solve the majority of the problems. The Civil module as it currently exists will not provide the functionality needed by the CRISP agencies. Tiburon is instructed not to proceed with the Civil BPR at this time. All monies for the Civil module to be held in abeyance pending an acceptable solution from Tiburon. If no solution is found the Civil module and all payments will be eliminated from the project. Reference Material submitted by Fort Collins-Larimer County (None Supplied) Tiburon Address of the Issue The functionality of the release 7.3.3 of the Civil product as reviewed during the Fort Collins-Larimer County Product Validation is not substantially changed in the initial release of version 7.40. At this time, release 7.40 is not expected to address Fort Collins-Larimer County acceptance issues related to this application module. The concept of a significant upgrade of this product has been in discussion for some time. The functionality of the text-based version of the product as it is currently operating in the Greeley Colorado system has been held up as a starting point for additional functionality to be added to the GUI version. In addition, some effort has been made to move forward with a version of the product developed from the common requirements of our Colorado customers. However, we are in the requirements gathering phase of this initiative and there is as yet no consensus among the User Community as to what the required functionality might be. Tiburon Commitment regarding this Issue Tiburon recommends that Fort Collins-Larimer County suspend implementation of the current version 7.3.3 and version 7.40 of the CPS product. If there is significant movement on incorporating significant new functionality in a follow-on release of this product, or there is significant progress toward definition and delivery of a Colorado specific offering of this project and the timetable for general availability is July 2004, at that point Fort Collins-Larimer can review their decision whether or not to include this module as part of this project. Mr. Larry Vail Page 7 Subject: Proposal and Commitment to Resolve Functional Issues 4/17/2023 We remain committed to moving this project forward in a mutually beneficial manner. If you have any questions, please feel free to contact me. Sincerely, Gerry Rymes, Central Region Operations Manager cc: Ken Peters, Sales Executive, National Accounts Rod Brown, Vice President, Central Region file: P1263-01-v6rm.doc