We've been able to utilize C3 to compare many different deployment strategies over the years when, for example, we've been looking at new station placement, temporary station placement (during a major road closure), and many "what if" possibilities that ultimately didn't go anywhere (which can be valuable in itself!)

The ability to run multiple possible deployment plans with the same underlying dataset and get detailed performance comparisons in a VERY short time is stellar. On top of that, if more granular detail is needed, it's easy to get to. Being able to see not only which model is better in different situations, but also by how much, empowers the end user to make better cost/benefit comparisons.

I genuinely don't know that I like anything "least". If I had to choose something, maybe it's that it can be intimidating because there are so many ways to look at the data results that it can be overwhelming. BUT, you don't have to make use of all of them, and can get a vast amounts of useful info upfront, then learn how to get more complex info on your own schedule.

We used to have to attempt scenario modeling with various BI tools and Arc GIS. While that worked, it was laborious and still felt a little like guessing. With Code 3 we can model complex and layered scenarios in just a few hours.

What I like the most about Code 3 is that it is flexible enough to allow creativity in modeling deployment changes. The different scenarios I have been able to model are far beyond what I thought was possible when originally purchasing the software

The user interface and general flow of the software is not the most intuitive. Fortunately, the documentation is great and walks you through each feature in detail.

We have always had to find our 90th percentile numbers manually using excel and data from our current RMS system. With Code3 Strategist, we now have the capability to automate that system and pull our numbers with just a few clicks.

The most impactful feature for us the the ability to look at 90th percentile numbers along with the maps of our city. The system gets easier to use the more often that you use it.

The learning curve of using the system was the only "difficult" part of it. The implementation was great and we had a wonderful trainer come to our department and teach us how to navigate the system and build what we needed.

We've had a great experience with the software and continue to be impressed with the continued evolution of the capabilities and reporting options.

Code 3 has been a great tool for maintaining accreditation performance reporting. Additionally, it has played a key role in determining future demand impact and deployment related decisions.

This is a great software. The main limitation is that it requires the user to spend adequate time learning the software.

The visualization of real data to partner agencies and showing what "could be" rather than just "what is".

This software gives the end user the ability to do predictive quantitative response modeling based on prior incidents.

The build out features to program in each resource and capabilities can be time consuming.