My Fire Rules Version Available:

My Fire Rules Alert

Zoll Alert

EFR Alert

My ePCR Metrics Alert


Date:7/11/2015
My Fire Rules Version: 4.0.2
FireRMS Version: Applies to all versions
Level: Changes from 3.8.27 to 4.0.2



My Fire Rules - Security improvements:

  • "SQL Server Connections" renamed "SQL Connection & Security" along with renamed tabs and buttons to improve clarity and usability.
  • MFR_Reporter & MFR_Billing Login passwords are now User controlled
  • MFR_Billing database User is not created (can be removed from current databases) if not using Billing Rules (Login remains, but can be Deleted in "Non-Hosted" installation
  • Uncheck_User (specialized Login) can now be re-named
  • Changes were made to incorporate updated ZOLL Security (in v5.0)
  • Updated FTP Credentials used in the program to be more secure

Metrics Pivot Table Data

  • Updated Metrics Inc_Casualties script, Per_AllDaybookTQ & LQ scripts and Per_Otheractivities script to fix bugs

My Validator (MV ver. 4.0.1)

  • "V-Button" (in conjunction with FireRMS 5.0) will ALLOW for Validation of more than ONE Year from the "Authority Tab" as the IncidentKey is now being used rather than "IncidentNumber" for Validation. This is particularly of use to those customers that "re-use Incident Numbers year over year".
  • Other minor bug fixes made to the Scan tool

"Response Report" improvements (MT ver. 4.0.1)

  • Clarifications were made to enumerate why records were "initially excluded" from the records used in the calculations. A new field (Excluded_Reason) was added making it easier to understand by using the Pivot table why records were excluded from the calculations. This is extremely useful when using data that was not totally validated.
  • Improvements were also made in the Excel OLE-DB connection for 64-bit Excel and in the Naming of the Workbook so that multiple Report Workbooks can be utilized without the user needing to rename the file.

Date:4/18/2015
My Fire Rules Version: 3.8.27
FireRMS Version: Applies to all versions
Level: Changes from 3.8.7 to 3.8.27



My Validator improvements (MV ver. 3.8.11)

  • Selections on Startup allows for User to define download options
    • This allows for quicker refresh of display
  • Filter by Month/Year option added Incidents/Training/Other Entries
  • "SCAN" has been improved yet again
    • When the "Scan of Completed Incidents" encounters any Fatal Errors you are now allowed to "Un-Complete" those incidents and "Require Validation" again. This will also uncheck the "Reviewed" and "Release To Public" Flags for those incidents.
      • The ONE requirement for this item to function is that you have a SQL User that has the rights to change those fields in the Incident Table; The Rules Guys has created a SQL Script available that will assist your DBA in creating such a SQL Login/User for this purpose and this purpose alone (so you do not need to give "sa" access).

"Occupancy Billing Toolkit" numerous improvements (BT ver. 1.4.11)

  • You can now Store Permits as a PDF to the FireRMS Letters TAB (as you have been able to do with Invoices)
    • Also available from the "Manage Permits" (and "Manage Invoices" , for Invoices) area.
  • The SQL Job may now be set to run as often as every 10 minutes. This, in conjunction with the "Quick-Pay" option allows for Permits to be Issued, Paid for, and Printed in as little as 15-20 minutes.
  • Quick-Pay option allows a Billable Request to be processed in rapid succession for those Invoices that are typically quick items such as Burn Permits.
  • Billing for Actions may now be done either at time of Completion OR the time of Assignment.
  • "Automatic Fee Increases for Actions" (in addition to Units and SqFt) have been added for:
    • Hours (with a minimum dollar amount and selective rounding)
    • Heads (associated with the Occupancy above a number)
    • Devices (associated with the Occupancy above a number)
  • Allow for Send to Collections of Delinquent Invoices
  • Deposit By Fund option for accounting for Deposits
  • Returns can now be added in Billing Toolkit for NSF or other needs,
    • In Returns section of Payments TAB (directly affects the Invoice)
  • Improved PDF quality and performance
  • Past Due and Delinquencies TABS now disabled if a "No Payments Recorded" agency
  • Improved Search and Filter for searching for Invoices/Permits
    • more to follow

Data Warehouse Processing has improved

  • When the Data Warehouse Processing completes, the MyFireRulesDB Log file is now reduced in size – this saves a substantial amount of wasted space due to bloat.

Incident Validation fully supports 10 Digit Incident Number format throughout all areas

MFR QuickSupport

  • Updated to Team Viewer 10 in all Modules and on Website for improved security and functionality

Date:12/13/2014
My Fire Rules Version: 3.8
FireRMS Version: Applies to all versions
Level: Changes from 3.7.15 to 3.8



"Vehicles & Equipment Validation" is now available

  • A fourth My Fire Rules Validation module is now available. This Validation module functions similar to the Occupancy Validation (since there is not a "Complete" checkbox).

"Tab-Level Validation" implemented for Occupancy and Hydrants as well as the new Vehicles & Equipment Validation.

  • When the Rules are "Loaded" for these Modules, you have an option to allow Validation of the Total Record (how it has been), or for Validation for the specific TAB that is showing when the "V" Button is Clicked.
    • Also available from the "Manage Permits" (and "Manage Invoices" , for Invoices) area.
      • If "Tab-Level Validation" is enabled during "Load Rules" , then when called with the "V" Button, the user can choose their Tab Option (All, Info, Activities)
      • This is of particular benefit for Validation of the "Actions" and "Findings" Tabs (Activities) without having to review the rest of the Occupancy/Hydrant/V&E Record.

For EF Recovery Billing refinements were made to improve control

  • "Reviewed" is now an option (in place of "Completed" ) for more control in determining when an Incident Record’s data would be transferred to the EF Recovery website.
  • Special XML Characters (<, >, &, ", ') are now replaced with the appropriate words for the Text Fields in the "EFR Info" TAB when submitted to EF Recovery.

"SCAN" in My Validator has been expanded to include ALL Modules

  • In addition to "Completed Incident Records", "Completed Training Records" and "Completed Other Activities Records" may now be Scanned for Fatal Errors within the "Filtered List".
  • Occupancy, Hydrant, and Vehicle & Equipment Records may now be Scanned for Fatal Errors within the "Filtered List".

Occupancy Billing enhanced

  • "Review Fee Increases" Button added to allow for auditing of when Fees have been increased.
  • Added ability to "Store" (to occ_letters in FireRMS) and "Re-Printing" a Permit that has been paid for and issued.
  • Added an "every 10 to 99 minutes" option for how often to run the "Billing Job" to allow for quicker turn-around for creating Invoices and Permits. A delay is still needed to allow for complete entry of an activity record

"Data Warehouse" FIX for "AllFires" Table (Incident Metrics Toolkits)

  • It came to our attention that (starting with version 3.7.10) "AllFires" table records were not correctly being removed from the Data Warehouse when ZOLL had removed the "fire" table record if the incident Mutual Aid Code field had been changed from "None or Received" to "Given" ; this caused an inflated number of FIREs when compared to the "All Incidents" count of "our fires. Those records are now correctly being removed.

Date:6/9/2014
My Fire Rules Version: 3.7.15
FireRMS Version: Applies to all versions
Level: Changes from 3.7.10 to 3.7.15



"Data Warehouse" FIX for Training "Does and Does NOT Have" Table (Training Metrics Toolkits)"

  • It came to our attention that in the 3.7.10 update we inadvertently had created a situation that caused the data in the "RMS5SQL_TRNG_DoesAndDoesNotHave" Table in the MyFireRulesDB Database to not be replace which grew that Table by duplicating the data that it held every night. That error has been corrected in 3.7.15.

"Apparatus Pivot Table" Clarification

  • There is a DIFFERENCE in the Data that is contained in the 2 Pivot Tables for Apparatus Response
    • "AppByStation" contains ALL Apparatus Dispatch Records for EACH Apparatus (including those Cancelled Enroute)
    • "AppRespTimes" now ONLY Contains Records where there is a VALID "Enroute To Scene" Time (scenedate) for that apparatus AND a VALID "Arrival at Scene" (arrivaldate) for that apparatus. Since the absence of either of these times will NOT Allow for the calculation of a Response Time those units are excluded so as not to calculate times with errors in the calculations.

Occupancy Pivot Table Fields added

  • The Occupancy Load data has been added to the following 3 Occupancy Pivot Table
  • "Occupancies" , "Inspections" and "SysHazOther"
    • There is a "Load_Has_Occ_Load" [Yes/No] field to indicate if the Occupancy has Occ_Load data, a "Load_Combined_Occ_Load" field with the Total Occupancy Load # for the whole Occupancy, as well as the other Occ_Load fields for each "Occ_Load" record.

Date:4/12/2014
My Fire Rules Version: 3.7.12
FireRMS Version: Applies to all versions
Level: Mandatory for all 64 Bit Excel users



Even MORE Speed and size improvements

    made to "Data Warehouse for Trusted Analytics (Metrics Toolkits)"
  • The time needed to update the MyFireRulesDB Data Warehouse used by the Metrics Pivot Tables has been REDUCED by 50% in this release. After "Initial Creation" , we now have improved the "update algorithm" that reduces update time by about 50% over previous versions!
  • Typical updates now focus on the last 2 year’s data. If you need the rebuild to include data earlier than 2 Years ago the "individual rebuild option" (from the DW Table listing) is available.

MyValidator has been improved

  • MyValidator now has a "SCAN" Button. Scan will run "Validation" on the Completed Incidents that are within the "Filtered Records" for Incidents that have somehow "fallen through the cracks" and been completed BUT have one or more "Fatal Errors". This can occur one of two way
    • NEW Fatal Rules have been applied
    • Somehow the Incident was "completed" , then changed in a way that would have created a "Fatal Error" but did not create a "Red" field that would have "Un-Completed " the incident If Scan finds any records with Fatal Errors it will produce a List of those Incidents with the # of Fatal Errors and the name of the Member Making Report. Administrators can then un-complete the report and inform the Member Making Report

Metrics Toolkit improvements

  • Pivot Tables are now completely compatible with 64-bit Excel 2010 and 64-bit Excel 2013, without needing any user or IT intervention.
  • Pivot Tables now have a "Date Option" that allows each user to limit the records that are returned when the Pivot Table is "refreshed".
  • The "Other" TAB has a "Redefine Connection Properties" Button. This allows users that have:
    • Pivot Tables that are used external to the "Pivot Table Launcher"
    • Changed the SQL Server that their databases are on. In this case, those Pivot Tables will become "unusable" if the "connection" is not edited

Recovery Toolkit improvements

  • Recovery Toolkit now sends the DispatchDate and ClearDate in the XML data to EF Recovery for easier verification of the "Time" element.

Date:9/1/2013
My Fire Rules Version: 3.7.0
FireRMS Version: Applies to all versions
Level: Recommended update for all Metrics users



It is very important that you keep your My Fire Rules programs “up to date”!

  • This update significantly improves the Metrics SQL Job that typically runs every night to refresh your data warehouse that is then used by your Metrics Pivot Tables. The job is now faster and uses less disk space. After installing the update, be sure to reload your Metrics Job.

Date:3/16/2013
My Fire Rules Version: 3.6.3
FireRMS Version: Applies to all versions
Level: Recommended update for all users



It is very important that you keep your My Fire Rules programs “up to date”!

  • Along with a few other fixes & enhancements, this update provides an option to use a secure login rather than the FireRMS5Reporter provided by ZOLL.

Date:12/6/2012
My Fire Rules Version: 3.5.38
FireRMS Version: Applies to FireRMS 4.11 and up
Level: Mandatory Upgrade for FireRMS Version 4.11 and up users



It is very important that you keep your My Fire Rules programs “up to date”!

  • The release of ZOLL RescueNet FireRMS v 4.11 required a change to the “Enhanced Validation for FireRMS Version 4.7 and above” in order to recognize the correct Version Number. In My Fire Rules 3.5.38 we have corrected the FireRMS Version Number recognition problem.
  • It is very important that our users Update to Version 3.5.38 of My Fire Rules as soon as possible. This will require the end user to update the "MyValidator.exe" file that is in ALL "firerms5sql" FireRMS Client program Folders and installing the latest " MyValidator.msi" (ver. 3.6.2). My Validator allows you to monitor your " Incomplete Incidents " and validate them from outside the FireRMS Client program. My Validator now allows for filtering by "First Arriving Unit".
  • Starting with FireRMS Version 4.7 a new system setting was added to the program. This setting inhibits marking the incident complete if the user has not clicked the "Validate Button". The end user is provided with a message indicating that the incident requires validation prior to marking it complete.
  • We recommend that you use the “My Fire Rules -> Enhanced Validation & Replication” BUTTON (located next to the “Close” Button) to enable “Enhanced Validation”.
  • If you change the setting using the "Inc Require Validate" feature under "More Settings " in ZOLL () there is one step that does not get completed. In order to complete the missing step you must "Load the Rules” to ensure proper set up.
  • Occupancy Validation now includes Hydrant Validation, and Training Validation now includes Other Entries Validation in Release 3.5.

Date:6/20/2012
My Fire Rules Version: 3.5.38
FireRMS Version: 4.9 and up
Level: N/A



It is very important that you keep your My Fire Rules programs “up to date”!

  • Now available in Incident Metrics!
    • New "Response Report" has been added to Incident Metrics
      • Allows Definition of "User Standards" to Report against
      • Allows User Defined Creation of "Geo-Areas" using 10 NFIRS Location Fields
    • Allows User Defined "Full 1st Alarm response"
      • by # of Personnel
      • by # and Type of Apparatus
    • Includes Formatted Report AND Pivot Table to examine the underlying DATA
      • Meets Washington State RCW 52.33 Reporting
        • Flexible enough for use in Re-Rate Data Requests
    • Quick Report Generation
    • Allows you to Examine and fix any erroneous data, and Run the Report again
    • All licensed users of Incident Metrics will receive the "New RESPONSE REPORT" automatically

Date:5/1/2011
My Fire Rules Version: 3.0.4
FireRMS Version: Applies to FireRMS 4.7 and up
Level: Mandatory Upgrade for FireRMS Version 4.7 and up users



It is very important that you keep your My Fire Rules programs “up to date”!

  • With Release 2.6 we removed the "Transaction Roll Back" message we had used to inform the user that the Incident is "NOT Complete" because, IF users were "Non-Compliant " and did NOT uncheck the box as directed, there were "undesirable consequences".
  • With ZOLL RescueNet FireRMS v 4.7 a "Message" replacement fix has been implemented allowing a tightly integrated experience for the user; paired with Release 3.0 of Incident Validation.
  • It is VERY IMPORTANT that our users Update to Version 3 of My Fire Rules as SOON as possible, Including updating the "MyValidator.exe" file that is in ALL "firerms5sql" FireRMS Client program Folders as well as Installing the latest "MyValidator.msi" (ver 3.0.2) which allows you to monitor your "Incomplete" Incidents and Validate them external from the FireRMS Client program.
  • We highly encourage the use of the ZOLL 4.7 "Inc Require Validate" feature under "More Settings" (or by enabling our "Enhanced Enforcement") which inhibits Marking the Incident COMPLETE if the user has NOT Clicked the Validate Button – with a Message to the User.
  • Training & Occupancy Validation is also now possible with Release 3.0.

Date: 6/30/2010
My Fire Rules Version: 2.6
FireRMS Version: Applies to FireRMS 4.3.X and up
Level: Mandatory Upgrade for My Fire Rules 2.5 and lower



It is very important that you keep your My Fire Rules programs “up to date”!

  • With Release 2.6 we have removed the "Transaction Roll Back" message we had used to inform the user that the Incident is "NOT Complete".
  • We had been using a "Transaction Roll Back" message that told the user that they "MUST UNCHECK COMPLETE BOX NOW", however IF users were "Non-Compliant" and did NOT uncheck the box as directed, there were "undesirable consequences". Therefore we have removed the "Roll Back" and no longer NOTIFY the USER that the "Report has been Marked UNCOMPLETED" ; but it is still "Marked UNCOMPLETED".
  • Using the "MyValidator" program allows you to monitor those "Incomplete" Incidents. We are exploring "Message" replacement fixes.
  • Additionally, we now "require that the Validate BUTTON be used" (at least once) if there are only Warnings present; We do this by Marking the Incident UNCOMPLETED if the user has NOT Clicked the Validate Button.