Loading...
HomeMy WebLinkAboutCAG2001-0525 - Supplement - KC Fire District 40 - Sunpro Message Switch (SMS) Interface Transfer of Support - 07/12/2001 City of Kent, Washington Valley Communications SMS Interface Agreement Valley Communications SMS Interface Agreement City of Kent, Washington Valley Communications SMS Interface Agreement 1 INTRODUCTION..................................................................................................................................................... 1 1 1 SMS INTERFACE BACKGROUND 1 12 OBJECTIVES 1 13 SMS INTERFACE INFORMATION 1 2. ROLES AND RESPONSIBILITIES......................................................................................................................3 2 1 CITY OF KENT 3 2 1 1 Backup and Recovery 3 2 1 2 Missed Messages 3 213 Version Control 3 214 SMS Maintenance 3 2 1 5 Disclaimer of Liability and Limitation of Remedies 4 2 2 VALLEY COMMUNICATIONS 4 221 PR to SMS Interfacc 4 222 SMS to FireRMS5 0 5 223 Missed Messages 5 224 Disclaimer of Liability and Limitation of Remedies 5 2 3 PARTICIPATING AGENCY 6 2 31 FireRMS5 0 Licensing 6 232 SMSLicensing 6 233 Network Security 6 234 Version Coordination 6 3. COST......................................................................................... ...............................................................................7 4. PARTICIPATING AGENCY AGREEMENT...........................................................................................................8 Index i City of Kent, Washington Palley Communications SMS Interface Agreement 1. Introduction The purpose of this document is to outline the participation requirements for using the Sunpro Message Switch (SMS) Interface located at Valley Communications The information addressed in this section includes ♦ SMS Interface Background ♦ Objectives ♦ SMS Interface Information 1.1. SMS Interface Background The SMS was developed by Sunpro to provide an automatic mechanism by which computer-aided dispatch (CAD) information could be entered into Sunpro's FireRMS5 0 information system. The City of Kent (City) purchased the SMS software and hardware in September 1999 While the SMS software provided the mechanism to enter information into FireRMS5 0, there was no interface available between the PRC CAD system employed by Valley Communications and SMS At the City's request, Valley Communications contracted with PRC to design and implement an interface to the SMS Work began on this interface in September 1999 and was completed in May 2000 The City and Fire District 40 participated in testing the SMS interface from May 2000 through September 2000. The City began using the SMS interface in a production environment in October 2000 1.2. Objectives This agreement's primary objective is to make the SMS interface available to Valley Communications dispatched agencies using Sunpro FireRMS5 0 1.3. SMS Interface Information The PRC/SMS interface does not provide access to all CAD data nor does it provide all data necessary to complete an incident report in FireRMS5 0 The information that is provided includes. ♦ Incident Summary Data — This includes overall incident dates and times as taken from CAD with the incident type translated from the CAD incident type to an NFIRS incident type The incident type is not complete in order to force an incident review prior to completing an incident ♦ Address Data — The address or other location data given to CAD is transferred to SMS and an attempt is made to parse the data into the various fields that make up the FireRMS5 0 incident address The address data is not verified against any local tables in either SMS or FireRMS5 0 The address as it came from CAD appears in the Directions field on the incident Location tab ♦ Apparatus Data — The CAD dispatched apparatus information is transmitted to FireRMS5 0 via SMS This includes the apparatus identifier, dates and times, and apparatus personnel. In order to receive any apparatus data, the member agency must have defined the apparatus for which the data is being transmitted in their system If SMS does not find an apparatus id in the agency's system matching the apparatus id transmitted from CAD, no apparatus information will be entered for that incident Apparatus personnel can be obtained from CAD, but as with the apparatus id, the personnel ids received Introduction I City of Kent, Washington Valley Communications SMS Interface Agreement from CAD must match the personnel identifiers defined in the agency's FireRMS5.0 system FireRMS5 0 uses the roster data to populate incident apparatus by default ♦ Narrative Data — The CAD narrative information is currently being transmitted from CAD to SMS however, the current SMS version only captures and transmits the first 254 characters to FireRMS5 0 ♦ Persons Involved — SMS populates this tab from the person information transmitted from CAD Currently, CAD only transmits one name and address. An attempt is made to parse the address similar to the incident address This is the basic information currently populated in FireRMS5 0 from SMS Other information is available and some additional information can be translated to populate other fields in FireRMS5 0. However, this has implications for all participating agencies and must be coordinated through the City All incident information transferred from CAD to SMS is subject to error from the crews on the apparatus, the dispatch operator, and network communications. It is therefore imperative that each agency review the incident information prior to marking the incident complete Introduction 2 City of Kent, Washington Valley Communications SMS Interface Agreement 2. Roles and Responsibilities This section outlines the roles and responsibilities of all parties associated with the SMS Interface The parties include ♦ The City of Kent ♦ Valley Communications ♦ Participating Agencies 2.1. City of Kent The City took primary responsibility in the SMS Interface's development and implementation The City anticipates maintaining the leadership role and fulfilling the technical duties relating to the SMS maintenance 2.1.1. Backup and Recovery The City will be responsible for the SMS backup and recovery This backup and recovery includes restoring the SMS software to the version that was operating prior to the need for recovery and restoring the configuration files Any messages that had been transmitted to a member agency or were in the process of being transmitted will not be restored Any lost messages can be retransmitted by Valley Communications. 2.1.2. Missed Messages The City is not responsible for any messages missed by a participating agency for any reason 2.1.3. Version Control The SMS uses FireRMS5 0 in conjunction with SMS software to distribute CAD dispatches New FireRMS5 0 releases require updates on the SMS as well as all personal computers that have FireRMS5.0 software and the FireRMS5 0 database server The City will establish the timeframes for updating the SMS and FireRMS5.0 releases. These updates will occur no more than once per quarter This will effectively limit the new FireRMS5 0 releases that participating agencies can implement This is necessary because all participating agencies must use the same version of FireRMS5 0 or risk losing incidents transmitted from CAD. 2.1.4. SMS Maintenance The City will provide periodic SMS maintenance This maintenance includes ♦ Clearing the activity log ♦ Clearing the incident history ♦ Updating participating agency configurations ♦ Updating software on the SMS It may be necessary to stop SMS transmission during any maintenance activities, however, participating agencies will be notified prior to a scheduled outage Roles and Responsibilities 3 City of Kent Washington Valley Communications SMS Interface Agreement 2.1.5. Disclaimer of Liability and Limitation of Remedies 2.1.5.1. Results Not Warranted The City has no control over the condition under which participating agencies use the SMS interface and does not and cannot warrant the results obtained by such use 2.1.5.2. Limitation on Warranty The City is not responsible for problems caused by changes in or modification to the operating characteristics of any computer hardware or operating system to which the SMS interface connects Nor is the City responsible for problems that occur as a result of the use of software or hardware that is incompatible with the SMS interface 2.1.5.3. Exclusion of Implied Warranty ANY IMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, ARE EXPRESSLY EXCLUDED. 2.1.5.4. Damages Limitation The City disclaims any and all liability for special, incidental, or consequential damages (including loss of profit) arising out of this agreement or with respect to the installation, use, operation, or support of the SMS interface or any update to the SMS interface even if the City has been apprised of the possibility of such damages 2.1.5.5. Limitation of Any Recovery The participating agency specifically agrees that any liability on the part of the City arising from breach of warranty, breach of contract, negligence, strict liability in tort, or any other legal theory shall not exceed amounts paid by the participating agency in fees for the use and maintenance of the SMS interface. 2.2. Valley Communications This subsection details Valley Communications' responsibilities regarding SMS operation 2.2.1. PRC to SMS Interface Valley Communications' responsibilities regarding the PRC to SMS interface include: ♦ Ensuring the PRC to SMS interface is properly transferring closed incidents to SMS ♦ Coordinating with PRC to correct problems with CAD regarding the incident transmission to SMS ♦ Coordinating with PRC for any enhancements to the interface. ♦ Starting and stopping the PRC CAD side of the interface ♦ Re-transmitting any incidents requested by member agencies. Roles and Responsibilities 4 City of Kent, Washington Palley Communications SMS Interface Agreement 2.2.2. SMS to FireRMS5.0 Valley Communications' responsibilities regarding the SMS to FireRMSS 0 transmission include ♦ Ensuring the SMS computer is operating and connected to Valley Communications' network ♦ Ensuring the SMS computer is able to establish a connection through Valley Communications' firewall to each participating agency's FireRMS5 0 system All network connections and firewall penetrations will be consistent with Valley Communications' network security policy and must be approved by Valley Communications prior to any implementation 2.2.3. Missed Messages Valley Communications is not responsible for any messages missed by a participating agency for any reason 2.2.4. Disclaimer of Liability and Limitation of Remedies 2.2.4.1. Results Not Warranted Valley Communications has no control over the condition under which participating agencies use the SMS interface and does not and cannot warrant the results obtained by such use 2.2.4.2. Limitation on Warranty Valley Communications is not responsible for problems caused by changes in or modification to the operating characteristics of any computer hardware or operating system to which the SMS interface connects Nor is Valley Communications responsible for problems that occur as a result of the use of software or hardware that is incompatible with the SMS interface 2.2.4.3. Exclusion of Implied Warranty ANY IMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, ARE EXPRESSLY EXCLUDED 2.2.4.4. Damages Limitation Valley Communications disclaims any and all liability for special, incidental, or consequential damages (including loss of profit) arising out of this agreement or with respect to the installation, use, operation, or support of the SMS interface or any update to the SMS interface even if Valley Communications has been apprised of the possibility of such damages 2.2.4.5. Limitation of Any Recovery The participating agency specifically agrees that any liability on the part of Valley Communications arising from breach of warranty, breach of contract, negligence, strict liability in tort, or any other legal theory shall not exceed amounts paid by the participating agency in fees for the use and maintenance of the SMS interface Roles and Responsibilities 5 City of Kent, Washington Valley Communications SMS Interface Agreemenf 2.3. Participating Agency The Participating Agency's responsibilities are outlined in this subsection 2.3.1. FireRMS5.0 Licensing Each participating agency is responsible for payment of all licensing, maintenance, and support fees relating to the agency's installation of FireRMSS 0 to Sunpro 2.3.2. SMS Licensing Each participating agency is responsible for payment of all licensing, maintenance, and support fees relating to SMS based on Sunpro's licensing requirements for said agency. 2.3.3. Network Security Each participating agency is responsible for their network security In order to use the SMS interface, the participating agency must coordinate with Valley Communications to establish a network connection which will allow the SMS transmission to pass through the participating agency's security measures and establish a connection to the agency's FireRMSS 0 server 2.3.4. Version Coordination Each participating agency must coordinate with the City regarding the currently supported FireRMS5.0 version Once the City decides to upgrade to a new SMS or FireRMSS 0 version, the participating agency must upgrade their FireRMSS 0 installation to the new version within 4 hours of the time set by the City. Failure to perform this upgrade may result in the participating agency not receiving CAD information transmitted from SMS to the particular agency These upgrades will occur no more than once per quarter 2.3.4.1. Remote Queue Processing If Sunpro modifies the SMS application to incorporate remote queue processing, we will examine the ramifications to our operations and make a determination at that time about incorporating a setup of that nature into the SMS processing environment Roles and Responsibilities 6 City of Kent, Washington Valley Communications SMS Interface Agreement 3. Cow The costs associated with participating in the Valley Communication SMS Interface are those incurred by the City in developing and implementing the interface Table 1, below, details these implementation costs and the amount each agency must pay to participate Table 1 SMS Interface Implementation Costs Description Amount SMS Interface Development Cost $68,400 Hardware and Operating System Cost $2,500 Total SMS Interface Development Costs $70,900 Membership Cost $7,090 The cost is based on participation by 10 agencies This is a one-time cost payable to the City of Kent Cost 7 City of Kent, Washington Valley Communications SMSInterface Agreement 1. Participating Agency Agreement I, Chief Paul Witt, as the authorized representative of King County Fire District 40 certify that I have reviewed the Valley Communications SMS Interface Agreement and agree to abide by the terms and conditions set forth herein including payment of the $ 7,090 fee King Con ty Fire District 40 Signed Date Title zl,� City of Kent Signed ® 9j Date 7 Title Valley Communications Signed Date —/ -O Title D�rec folr C4- 1 Participating Agency Agreement 8