Release Notes for RescueNet FireRMS version 4.15 July, 2014 Introduction These release notes accompany the release of FireRMS version 4.15. This document is not meant to comprise complete documentation of the software. For detailed information about using the software, refer to the user documentation listed below available on the FireRMS Installation CD. The following documents are available and recommended: FireRMS Administrator s Guide (contained in the Documentation directory on the Distribution CD-ROM). FireRMS User s Guide (contained in the Documentation directory on the Distribution CD-ROM). FireRMS SQL Utilities Guide (contained in the Documentation directory on the Distribution CD-ROM). FireRMS Installation Guides and Technical Support Bulletins (available from ZOLL Sales and Support departments). Other documents may also be included on the CD-Rom. For the latest version of this document, and other support notes about this product, please check our Customer Support Website at http://www.myzolldata.com/ Important Notices If you are upgrading from a version of FireRMS earlier than 4.9, you are strongly encouraged to uninstall your current version of FireRMS before
installing FireRMS version 4.15. Failing to uninstall the earlier version will result in duplicate FireRMS icons displayed on your desktop and in the list of programs displayed in the Windows Control Panel. If you are using the Add-on Program Supplies and Inventory and you will be using SQL Server version 2012, you must upgrade to a new version of Supplies and Inventory version 2.0.119. There are no changes in this new version of S&I except to provide support for SQL Server 2012. Before upgrading your software, if you have any work-in-progress User Defined Tabs, you must run the Update UDTab and Reset Permissions in the SQL Utilities program. If you do not reset permissions, an error will occur during the upgrade. When upgrading the FireRMS client on a machine where SMS is running as a Service, Stop the SMS Service before attempting to upgrade the FireRMS client. Once the upgrade has completed, start the FireRMS client one time before restarting the SMS Service. If you install FireRMS in a directory other than c:\firerms5sql, and you use SMS, you must open the SMS configuration and register the FireRMS executable in its new location. ZOLL Customer Support is available to assist with any SMS configuration questions.
FireRMS version 4.15 New Features This section lists new features in FireRMS version 4.15. Unless otherwise specified, each update listed is available on both the USA and Canadian versions of the FireRMS program. Administrative/General New Support for SQL Server 2012. FireRMS 4.15 has been certified to work with Microsoft SQL Server 2012. FireRMS will also continue to work with SQL Server 2005, 2008 & 2008 R2. The FireRMS core & mobile programs will now attempt to reconnect to SQL Server if the network connection is lost and later reconnected. In all previous releases of FireRMS, if the network connection between the FireRMS client and SQL Server was lost, users would have to restart the application in order to reestablish the connection, potentially losing any work in progress such as Incident Narrative reports. New mapping fields to store NFIRS code values have been added for Stations and Apparatus records. NFIRS allows no more than 3 characters for Stations and no more than 5 characters for Apparatus/Unit IDs. FireRMS has long allowed users to enter up to 4 characters for Stations and up to 8 characters for Unit IDs, but this required excluding Apparatus records when exporting to NFIRS, and Station IDs would be truncated when they exceeded the NFIRS maximum limit. If you use more than 3 characters for stations or 5 characters for Unit IDs in FireRMS, you may now enter unique Extract values for these identifiers so these records may be included in your NFIRS Incident export. There is no need to enter a value in these new fields if your IDs are 3 characters or less for Stations, or 5 characters or less for Units. All comment and note fields have been updated to support copy and paste via a right click from a mouse. In previous releases of FireRMS, copy and paste in these field types could only be completed via the keyboard shortcuts Ctrl/C and Ctrl/V. A new type of User Defined Tab One to Many Date is now available for creation in the following modules: Hydrant, Personnel, Occupancy, and Vehicles & Equipment. Similar to the previously available One to Many tab type, this tab allows users to enter multiple records on each single tab by clicking an Add button and providing a Date & Time value to be stored in a list box. Data entered in all other fields on the tab will be linked to the each specified date/time entry. When working with the Personnel Explorer, if the view is set to Roster, the Rank as set in the Roster will be displayed and used to populate the field Position for
each person selected. If the view is set to Personnel or Alphabetical, the Rank as set in the Personnel module will be displayed and used. DayBook Address and Comments will now display with Occupancy activity listings in the Details column of the Daybook To Do Items List. Incidents Incident Type 611E is now available for selection from the Incident Type code list on systems setup to use Basic or Advanced EMS. 611E is an NFIRS Plus One code typically used for EMS Cancelled En Route calls. (USA Only) The EMS field Pulse on Transfer, which was previously displayed as a checkbox, has been updated to be a selection field allowing the user to specifically select Yes or No. This change should help to prevent confusion regarding the usage of that field. The field Initial Dispatch Code has been updated to two fields: Initial and Final Dispatch code. On systems where this field is populated by a CAD, if the CAD system sends multiple values for this field over the course of an incident, the Initial and Final codes will both be saved and displayed. (USA Only) When entering a Canadian Postal Code on the location tab, users may no longer enter multiple spaces or other invalid characters. When data exists on the Fire or Structure Tab, users will no longer be able to change the incident type from 01 or 02 to any other incident type, nor will they be able to delete the incident type field. Only after all data has been deleted from the Fire and Structure tabs will users be able to change the incident type code. (Ontario Province only) A new button labeled Import will now display on the location tab when working on an Exposure report. When selected, the address from the initial Fire Report will be imported into the new Exposure record. This change should help cut down redundant data entry when working on exposure reports (USA Only) Incidents imported from the epcr product will now be marked complete when the Provider Impression = 16, but no data was included for the optional field Pre- Arrival Arrest Details. The Pre-Arrival details field is not required by NFIRS, so has been removed from the validation routine used to mark epcr records complete. On systems where Incidents are created by a CAD system, and then later updated from an epcr system, the Personnel records will no longer be imported from the Roster if they were posted to the Incident by the CAD Vendor.
Occupancies The Occupancy Inspection Report available for use on FireRMS Mobile clients has been updated to allow an inspection report to be marked complete with No Findings. A new Finding code No Violations has been added to the list of Findings for the Occupancy module. This code may be selected when Inspection Reports are completed with No Violations found. Your local Administrator may update the Code, Short & Long Description of this new Finding type, and even associate Standards or IFC/NFPA codes with it, if desired, and the text values they enter will be displayed on your Inspection Reports. The Found Date displayed with Findings on the Mobile Inspection report will now display the date entered in that field on the FireRMS Occupancy activities form, rather than displaying the date the record was actually created. A new System Option Req Valid Address has been added under Tools, System, More Settings. When selected, users will be unable to create new Occupancy records, or update the address of any Occupancy, unless the Address may be validated. Please see the FireRMS Administrators Guide for more information on setting up Cities, Streets and Blocks to use for the Address Validation Routine. A new option is now available to Retire Finding Codes. When the checkbox Retire Finding is selected for any single Finding code, that code will no longer be available for new entries in the Occupancy module or the Mobile Inspection report. A new security option has been added for the Occupancy Module. When the security object Occupancy, Activities, Findings, Req Action is set to 1 No Access, users will be unable to Add Findings unless the View is set to Associated List and an Activity is selected. This change ensures that those users are unable to create Findings unless those findings are directly associated with an Activity. This security object is set to level 3 Full Access, by default, allowing pre-existing behavior to continue to work for all users. The Apex Draw properties sheet has been updated so that.jpg files will always now be created by default. Users may clear the checkbox for.jpg files if creating them is not desired. This change ensures that as updates are made to an Apex file, any associated.jpg files will also now be updated. Enforcements added to a CUPA Inspection will now be flagged as Batch records when they were created using the Batch process. This change provides a visual reminder to users that making changes to enforcement for one violation will update all enforcements for all violations created under the same batch.
Training Objectives and Skills may now be retired. When an objective or skill or an entire category of Objectives or Skills is set to retired, they may no longer be added to newly created Training Classes. If a retired objective or skill had previously been added to a class under the Customize Training options, it will no longer display for that class the next time the class is scheduled in the Training module. Retired objectives and skills will continue to display in classes where they had been added if those classes were scheduled before the objective or skill was retired. If, after retiring an entire category of objectives or skills, the Administrator wishes to un-retire the group, each objective or skill must be unretired individually. Vehicles and Equipment The Vehicle fields Bore (located on the Drive Train tab) and all Weight Distribution fields (located on the Chassis tab) now accept up to 3 characters after a decimal place. This change allows users to more accurately record data for these vehicle attributes. FireRMS version 4.15 Problems Solved This section lists issues resolved in FireRMS version 4.15. Hydrants Location information is now displayed for all Hydrants imported via the Upsize process. The Upsize process will no longer truncate latitude and longitude information for Hydrants after the first two decimal places. Up to 6 digits after the decimal will now be properly processed during the upsize import routine. Incidents The Incident Completeness report will no longer display invalid results when run against a group of Incidents that include 131 or 142 type incidents. Values entered in the fields Story of Origin, At or Above Grade, Main Floor Area, all located on the Structure tab, may now be deleted. Occupancies
Personnel Location information is now displayed for all Occupancies imported via the Upsize process or created via the Create History process. Printing any single Occupancy will no longer return an error when sections such as Prevention Info are cleared in the Selection list. Users with Read Only access to the Occupancy contact page will now be able to use the selection field for Other Numbers to review the contact s cell, fax or other number. Users may now select Findings in Occupancy History records. Tabbing through the Activity Completion date field and then back up to it will no longer cause any updates to be made on associated findings. The Security Objects for Personnel have been updated as follows: Form, Personnel Info, All, Non-Restricted, Form, Personnel Info, All, Restricted & Form, Personnel Info, All, Scheduling now apply to all personnel records except for the record for the currently logged on user. The Security Objects Form, Personnel Info, You, Non-Restricted, Form, Personnel Info, You, Restricted & Form, Personnel Info, You, Scheduling now apply to the currently logged on user. The FireRMS Administrator Guide, Appendix A properly describes how each of these security objects function. Scheduling & Tracking Training Errors will no longer display when attempting to print Activities for Equipment or Occupancy records when those records include both single and double quote characters. The Customize Training Form has been updated to ensure Administrators may add Objectives & Skills, and set default hours, while creating multiple training classes during a single session. FireRMS version 4.15 Known Problems This section lists problems that have not been resolved in FireRMS version 4.15. Mobile Incident Reporting
The Patient Disclosure Form, available with Advanced EMS and NEMSIS reporting forms, does not currently work on Windows 8.1.
FireRMS version 4.15 System Minimum Software & Hardware Requirements Client Computers and Workstations Processor RAM Disk Space External drive Monitor Supported Platforms Pentium IV 1GHz 512MB (minimum) 1 GB (minimum) CD ROM or DVD Super VGA (800x600) or higher resolution Keyboard and mouse Windows Vista, Windows 7, Windows 8.1(*), Windows 2003, Windows 2008, Windows 2008 (R2), Windows 2012 The Operating Systems should have the latest Service Packs and other Windows updates installed. (*) To automatically setup the ODBC connection on a new Windows 8.1 system, after installing the FireRMS Client, you must right click on the Desktop icon one time and select Run As an Administrator. Alternately, the ODBC connection may be manually configured for your database. Mobile Client* Processor Intel Centrino TM Mobile Technology (recommended) RAM 1GB (minimum) Disk Space 4 GB (recommended) External drive CD ROM or DVD Monitor Super VGA (800x600) or higher resolution Keyboard and mouse Supported Platforms Windows 7, Windows 8.1(*) Client DB The Operating Systems should have the latest Service Packs and other Windows updates installed. (*) To automatically setup the ODBC connection on a new Windows 8.1 system, after installing the FireRMS Mobile Client, you must right click on the Desktop icon one time and select Run As an Administrator. Alternately, the ODBC connection may be manually configured for your database. SQL Server 2005 Express Edition (SP2/SP3) if running Microsoft SQL Server 2005 on the server. SQL Server 2008 Express Edition or SQL Server 2008 Express R2 Edition if running Microsoft SQL Server 2008
or SQL Server 2008 R2 on the server. SQL Server 2012 Express Edition if running Microsoft SQL Server 2012 on the server. Additional Software Requirement To use Mobile Inspection Reports, Adobe Reader must be installed on the mobile computer. You can obtain the latest version of the reader from: http://www.adobe.com/ Click on downloads to select the appropriate version of the reader program for your operating system. NOTE: When running FireRMS Mobile Dashboard on Windows 8.1 you may need to also install Crystal Reports 11 SP4.5 in order to launch Crystal Reports from the Dashboard program. CR11 SP4.5 is available on the Mobile CD-Rom in the CR11 folder, or contact ZOLL Customer Support to obtain this service pack. * Handwriting recognition is supported on Tablet PCs equipped with a digitizer pen. Other devices may not support handwriting recognition in all fields. Database Server - Microsoft SQL Server 2005 or 2008* Processor RAM Disk Space Dual Processor Pentium IV 1GHz (minimum) or 4 Processor Pentium IV 2GHz (minimum) for multiple mobile installations 4GB (minimum) or 8GB (minimum)** 40 GB (minimum) External drive Supported Platforms CD ROM or DVD Windows 2003, Windows 2008, Windows 2008 (R2), Windows 2012 The above Operating Systems should have the latest Service Packs and other Windows updates installed. Monitor VGA or higher resolution: pixel resolution 1,024x768 * Check the Microsoft Web site for additional requirements. ** A minimum of 8GB is required if you are using SQL Utilities Auditing or the FireRMS Mobile product. A minimum of 16GB may be required for mobile installations with greater than 75 mobiles, or if you are hosting more than one database on the single server. Contact ZOLL Systems Customer Support or Sales for more information. Sunpro Message Server (SMS) Processor Pentium IV 1GHz or greater RAM 512 MB (minimum) / per SMS instance Disk Space 10GB (minimum) Network TCP/IP connectivity
External drive Supported Platforms CD ROM or DVD, backup storage device Windows 2003 Server, Windows 2008 Server, Windows 2008 Server (R2), Windows 2012 Server, Windows 7, Windows 8.1(*) The above Operating Systems should have the latest Service Packs and other Windows updates installed. (*) When installing SMS on Windows 8.1, you must right click on the program executable file sms.exe - one time and select Run as an Administrator in order to register with the FireRMS Database and/or to create SMS Services. Central Web Reporting Option (Web Server Required) Web Server Requirements Supported Platforms Windows Server Internet Information Services (IIS) with ASP.Net Refer to Microsoft for IIS installation and minimum requirements Windows 2003 Server, Windows 2008 Server, Windows 2008 Server (R2), Windows 2012 Server All the above Operating Systems should have the latest Service Packs and other Windows updates installed. Installing FireRMS 4.15 These installation procedures describe how to install FireRMS software on the client and the server. Verifying SQL Server Settings SQL Server 2005 (SP2- SP3), SQL Server 2008 (SP1 or later), SQL Server 2008 R2, or SQL Server 2012 (SP1 or later) is required to use FireRMS version 4.15. Before installing either SQL Server, or SQL Express, check the Microsoft web site and review all requirements. After installing either SQL Server or SQL Express, you must use the Surface Configuration Management Utility to verify the following settings so that FireRMS successfully runs with SQL Server: Under SQL Server Network Configuration, Protocols make sure that Named Pipes and TCP/IP are both Enabled. Under SQL Native Client Configuration, Client Protocols, make sure that Named Pipes and TCP/IP are both Enabled.
Under SQL Server Services, make sure the SQL Server Agent is Running, and that the Start Mode is set to Automatic. Refer to the next sections for information on installing the FireRMS software. Installing FireRMS Client Software This section describes the procedure you follow to install the FireRMS client software. In addition to the client software, FireRMS requires certain third party utilities for normal operations. All utilities except for the Microsoft Windows operating systems and services packs can be found on the FireRMS CD. Refer to the System Requirements section in this document for the correct version numbers of the software. The installation of FireRMS Client installs FireRMS Client software and Crystal Reports run-time. Important Note: The FireRMS Mobile client has separate/unique installation instructions in the Installing FireRMS Mobile Client and FireRMS Mobile Configuration section below. Refer to this section if you are installing software on a FireRMS Mobile Client. The following must be installed on the FireRMS Client before installing FireRMS client software: Supported Windows Operating System To install the client software: Insert the FireRMS installation CD in the client CD drive. After a pause, the CD options screen appears. (If the CD options screen does not start automatically, in Windows Explorer open the FireRMS installation CD directory and double-click Launch.exe.) Click Install Products in the list of options. Click FireRMS Client. A Welcome screen is displayed. Click Next. A Customer Information screen is displayed with User Name and Company Name fields. We recommend selecting the default option to install the application for anyone who uses this computer. This allows any computer user to run this application on the client. Enter this information and click next. The Destination Location screen will display. We recommend using the default directory (typically c:\firerms5sql). Click next, or click Browse to install to a different directory. A Setup Type screen will display. You may choose Complete or Custom install, and then click next. (If you select a Custom install, you can deselect FireRMS Core application or Crystal Reports 11 Runtime.) A File Copy screen will display with Setup information. Click Next. A Setup Status screen will display and the software is installed.
When the installation has completed, click Finish. The main screen will display. OPTIONAL: Click 3rd Party Utilities or Add on Apps if you wish to install any of the third party utilities or add on applications on your system. Click Exit twice to close the FireRMS install program. Restart your computer. The first time you launch the FireRMS client, a configuration screen will display. This will occur one time only. Installing FireRMS SQL Utilities Software This section describes the procedure you follow to install software on the server. To install software on the server: Insert the FireRMS installation CD in the client CD drive. After a pause, the CD options screen appears. (If the CD options screen does not start automatically, in Windows Explorer open the FireRMS installation CD directory and double-click Launch.exe.) In the list of options, click SQL Utilities. If this is an SQL Utilities upgrade only a message box will display prompting you to upgrade SQL Utilities. Click Yes if you want to proceed. A Welcome screen will be displayed. Click Next. A Customer Information screen is displayed with User Name and Company Name fields. Enter this information and click next. The Destination Location screen will display. We recommend using the default directory, (typically c:\firerms5sql). Click next, or click Browse to install to a different directory. A Setup Status screen will display and the software will be installed. After completing the install, click Finish. The first time you launch the SQL Utils program, a configuration screen will display. This will occur one time only. Updating your FireRMS Database Double-click the SQL Utilities icon on the desktop. If the SQL Server agent is not running, you will be prompted to enter the SQL Server name and logon credentials. If the service is running, SQL Utilities automatically detects this information. If you have defined an SA password you will be prompted to enter it to complete the logon. Then, Do one of the following:
Update the FireRMS database(s) if you are upgrading your software. Verify that no clients are connected to the database(s). In the Your Databases list of the SQL Utilities for FireRMS dialog, locate and highlight the FireRMS database that you are updating. Click the Lock Database check box. Click the Update button to update a single database or the Update button to update all the databases. Uncheck the Lock Database check box to unlock the FireRMS databases. Create a new database if you are performing a new install. Click the Create button. The Create Database dialog box displays. Enter the database name in the Database Name text box. Click OK. Close the SQL Utilities application. Start FireRMS on a client machine. Click the Help menu, and then click Help About. In the About dialog, click the Details button. In the Details dialog, verify the application version number is correct. Note: If you are using FireRMS Mobile, you will need to delete all subscribers and disable the publisher before running this upgrade. After the upgrade has completed, you may re-enable the publisher and re-add the mobile subscribers Installing FireRMS Mobile Client and FireRMS Mobile Configuration This section describes the procedure you follow to install software on the server. NOTE: If you are using FireRMS Mobile version 4.1 or earlier, contact ZOLL Systems Customer Support for additional information before beginning the upgrade. MOBILE SETUP OPTIONS: After installing FireRMS Mobile on each mobile client, the System Administrator must complete the mobile configuration as described in Chapter 7 of the SQL Utilities Guide. Or in the FireRMS Mobile Release Notes. Also, refer to FireRMS User s Guide and the Online Help for details about the FireRMS features created for use on a mobile device: a laptop or Tablet PC. Note: Be sure to install the proper version of SQL Express to match your server based SQL Program. To install FireRMS Mobile Client:
Insert the FireRMS Mobile installation CD in the client CD drive. After a pause, the CD options screen appears. (If the CD options screen does not start automatically, in Windows Explorer open the FireRMS Mobile installation CD directory and double-click Launch.exe.) Click the Install FireRMS Mobile button. The Welcome Wizard screen will display. Click Next. The Customer Information screen will display. Enter a User Name and Company and click next. The Choose Destination Location screen displays with a destination of C:\FireRMS5SQL\. Click Next. A Setup Type screen displays. Choose Complete or Custom and click next. If you select Custom, you can deselect the following: FireRMS Core Application, Crystal Reports 11 Runtime, or Occupancy Inspection. Click Next. The File Copy screen displays with your selections. Click Next. The Setup Status screen will display. After completing the install, click Finish. The install continues with Crystal Reports 11 Runtime. (The Welcome screen may take a few minutes to display.) When the Welcome screen displays, click next. The Customer Info screen will display. Enter a User Name and Company and click next. Crystal Reports 11 Runtime will be installed. After completing the install, click Finish. The main screen will display. Click Exit twice to close the FireRMS Mobile install program. Restart your mobile client computer. NOTE: If the Crystal Reports runtime does not automatically install with the mobile client software, you may run the installer separately from the CD-Rom. After installing the software on each mobile client, you must complete the mobile configuration on the server. Please refer to the SQL Utilities Guide for information on configuring the FireRMS DB servers, databases, and utilities for the mobile clients for proper database synchronization. Note: If an administrator uses design mode to create local configuration options, the mobile users should run the SQLUtilsMobile program to reset permissions before running the FireRMS mobile again. This ensures all changes to the local version of the program are set properly. Setting Security on Mobile Devices After installing FireRMS Mobile Client software, you must set the security on each mobile device to enable users who are not OS Administrators, to enter data on the mobile devices:
Open Windows Explorer and right-click on the FireRMS5SQL folder. Select Properties from the menu to display the Properties dialog. Click the Security tab. Select the Group Users. In the Permissions for Administrators list box, select the Full Control check box and click OK. Disabling User Account Control on mobile devices In order to use the many integrated components of FireRMS and FireRMS Mobile clients, you may need to disable User Account Control on your system. Please refer to the appropriate Microsoft Help file for your operating system to learn how to disable UAC. Database Synchronization for FireRMS Mobile on a system with a Firewall When you install Vista or Windows 7, the firewall is turned on by default. Database synchronization will not work with the default firewall settings. You may either turn off the firewall or update the firewall settings to allow SQL server connections to pass through the firewall. Information on how to setup firewall exceptions is provided on the Microsoft Web site or in the online help for your operating system. Disclaimer of Warranty ZOLL Inc. makes no representations or warranties, either expressed or implied, by or with respect to anything in this document, and shall not be liable for any implied warranties of merchantability or fitness for a particular purpose or for any indirect, special or consequential damages. Copyright 2013, ZOLL Inc., All rights reserved. Printed in the United States.