2.0 Release Notes

A Maps sub-tab has been added to the Incidents and Hydrants tabs, letting you view the physical locations of incidents and hydrants, respectively. The locations of incidents or hydrants are indicated by light gray circles on the map.

Information on using the maps is available in the FH Analytics Analytics User's Guide, under Use incident and hydrant maps.

The Incidents, EMS, Occupancies, Staffing, and Hydrants tabs now include a Details sub-tab, on which you can view the raw data as it exists in the FH database.

Note: For best performance, at the top of the interface, select the year you want to see the raw data for.

On the Admin tab,there are now two methods of authentication available when accessing an FH SQL database. If you click the new SQL Integrated button, fields for logging into the database using Windows NT authentication appear. If you click the new SQL DB button, fields for logging into the database using SQL Server authentication appear.

On the Admin tab, for each type of unit in your FH database, you can now have the same unit type accept more than one type code. A second column has been added to Std of Coverage Unit Type, and if you enter a second type code in the additional column, FH Analytics creates a logical OR between the two type codes.

As a result, on the Compliance → Standard of Cover tab, in the lower left corner of the interface, under Minimum Unit Type Counts, the name of the unit type is a combination of the two type codes, and you can enter a total number of units for all your vehicles of those type codes.

On the Admin tab, under Scramble Patient, you can now choose whether or not to conceal (scramble) the names of patients displayed in FH Analytics.

The results of your setting appears on the EMS → Patients tab, in the Patient Information by information pane, when you select the Patient Data data view.

On the Admin tab, under Use Dispatch Time, you can now choose whether or not to start the response timer from the time of the received 911 call, or to start the response timer from the alarm time.

You can now choose to filter data by either the calendar year, or by a fiscal year. On the Admin tab, under Fiscal Year Start, you can enter a 0 to use a normal calendar year, or you can enter the number of the month the fiscal year starts in to use a fiscal year.

The calendar interface on the other tabs in FH Analytics starts with the month you specify, instead of with January, and the labels in the calendar interface update accordingly.

If you have a large database with records going back a number of years, but you only want to analyze records from the last few years, you can now improve FH Analytics' performance by only loading the data from the last few years. On the Admin tab, under Min Data Year, you can specify the oldest year you to want use when analyzing data from the FH database, and only the data from that year to the present is loaded.

Example: Your FH database contains records from 1995 to the present, but you only need to analyze the data from 2007 to the present. If you enter 2007 for vMinDataYear, only the records from the 2007 to the present are loaded and analyzed in FH Analytics.

Note: By default, 2010 is the minimum data year. If you want to analyze records pre-dating 2010, you need to change this value.

On the Compliance → Incident Compliance tab, in the lower right corner of the interface, under 90% Goals, you can now view feedback about the number of incidents that meet your 90% criteria for call processing, call turnout, and travel time.

On the Compliance → Standard of Cover tab, in the center of the interface, under 90% Goals, you can now view feedback about the number of incidents that meet your 90% criteria for cutoff times.

On the Compliance → Incident Compliance tab, in the lower left corner of the interface, new filters are availble to let you exclude calls that are outside your normal driving area (example, rural locations), and that would skew your data. This keeps unusual calls out of the calculations.

The following names have changed on the interface, but the data and functionality for the respective features have removed the same.

• On the Compliance → Incident Compliance tab, the First Turnout Time Compliance bar graphics are now named First Unit Response Time Compliance, and the Reflex Time (Minutes) – First Unit and Reflex Time (Minutes) – Last Unit are now named Total Response Time (Minutes) – First Unit and Total Response Time (Minutes) – First Unit, respectively.
• On the Admin tab, Incident_Unit_Type is now named Unit Type Available.