Liberty Fire Department Saves Time, Leverages More Data

ESO Staff

Fire agencies are always pushing for improvement. Whether it’s tweaking operational procedures or adding new training opportunities, more efficient firehouses mean safer communities and teams. But how can an agency know where improvements can be made – and if changes are making a positive impact – without setting an original benchmark?

The answer is data, and lots of it. For every agency, there is a wealth of helpful information just waiting to paint a picture of what currently is – and is not – working.

Most agencies are aware of this available information, and already work with it to some extent. After all, regular reporting is required for many purposes, like state and city funding, grants, and organizations like NFIRS. However, many agencies are using tools that are holding them back, not empowering them. That was the same boat the Liberty Fire Department in Missouri found itself in.

About the Liberty Fire Department

With around 4,400 calls per year and three stations in a 29-square mile service area, Liberty Fire Department was in need of better ways to input and extract data that would better serve its personnel and community. Its current software was unwieldy, and the team struggled with not only accurately entering the data but with accessing it later for reports and snapshots of performance and operations.

Liberty Fire Chief Mike Snider turned to neighboring agencies to see what software they were using, and learn about the pros and cons of each. When he saw the software tools from ESO in action, the ease-of-use for personnel made a key impression, because Snider knew that if the tools were easier to use, the team would be more likely to enter required data more consistently and accurately.

Additionally, the reporting functions and processing of data from across the agency – like personnel information, training, incident reports, and more – was especially attractive for Snider, who often needed to provide status reports and updates to the public, government, and industry agencies.

Test Driving New Software

Exploring the ESO’s ePCR and fire incidents tools proved extremely simple for Liberty FD, with the ESO team creating a virtual “sandbox” environment that offered an idea of what the setup for its agency would be. This real-world, hands-on setting allowed Chief Snider to let his team play with dummy data and explore the various features and functions of the tools.

His team needed minimal training to start understanding and using the intuitive functions and tools, building his confidence that everyday use would make accurate data input more efficient and consistent. When Liberty FD decided to move forward with the ESO tools, the ESO implementation team made the switch over as seamless as possible, working on a tight timeline and addressing any issues that arose during the process.

Better Data for the Fire Department

Today Liberty FD is reaping the results of the new, more powerful tools on a daily basis. The agency can now easily record data on a regular basis, with personnel easily helping input the required data on calls and incidents. Team information, like training hours and even immunization records, are easily maintained and can be modified to send notifications as needed to ensure certifications are met.

Progress on quality improvement projects or new training and process initiatives can be easily tracked, and station metrics can be compared to other agencies across the nation. Finally, reports and statistics can be easily pulled at a moment’s notice, making it easier for the agency to communicate with the public as needed, or check progress of various projects or stats.

Liberty FD looked to its peers for what was working best, and was not disappointed. Taking the time to switch to a new software tool improves efficiencies every day and helps the team focus more on firefighting and less on number-crunching.

To learn more, read the full Liberty FD success story.

Leave a comment

Leave a Reply

Your email address will not be published. Required fields are marked *