Important to understand about Rescuenet is that it is NOT designed to be pulled out of the box and put on the truck. It is a massively customizable program that is designed to be "built" to the end user's specifications. This however, takes time and expertise. If the system using the software is not willing to put this into it, the it will be a disaster.
Every time you add or take away a closed call rule, intervention, facility, ect it changes how various parts of the program interact. These changes then have to be tested, and programming possibly rewritten.
Another failure point is the server, if the user is not willing to pony up for servers powerful enough to handle the demand placed upon them, again, it will be a disaster.
Time from purchase to implementation at our service was 6 months. In this time the team putting together the software was spending 40-50 hours a week on it. Our launch was not problem free, but it went a lit more smoothly than other launches I've been through.
We have options that are relevant to our system (for instance no "bazooka", although it IS still in Texas trauma registry), the reports come from the server promptly and are correct and the average time to do a very thorough, complete report on an average call takes around 20 minutes to do. A more complicated report takes longer, but creates one of the most legally defensible reports I've ever seen. In summary, it's the best chart, paper or electronic I've ever used.
What it sounds like is your managers are not taking the time to hash the program out first. Which is a shame, because it really is a heck of a chart once the bugs are worked out.