I've been involved in all sides of the issue. Competitive procurement is vital to keeping smaller businesses operating in our communities when there is a large, homogeneous system. Anyone who has been in this profession for several decades has seen the local two-way shop go away once a regionalized radio system makes its way into the communities the shop once served, if that shop was independent or sold a competitive brand to the "big" system. Then, only the manufacturer-favored shop survives and all competition in all markets seems to evaporate, except maybe for items that are blister-packed and can be immediately set up and shipped without the need for continued support. What ends up happening is that these "mom and pop two-way shops" close. Large centralized depots will fly out support specialists, and maybe a regional satellite office will supply a "warm body" to fulfill a contractual response time.
Standards-based systems are also vital. That means that there needs to be a lot of representation around the table in the standards-making process so that a dominant player does not sway or bully proprietary embellishments into the standard. For example, there would be minimal compatibility to insure interoperability, and then there would be upper-level performance offered as a high order set of features that precludes any such interoperablity.
This last thing is big in the grants community, particularly in urban areas: the NIFTY FACTOR. I hate to term it this way, but some of the folks making procurement decisions are 60-somethings whose mommys never bought them the Howdy Doody cowboy suit, the big clunky red or blue bicycle with the streamers coming off the handlebars, the X-Ray glasses with the spiral lenses, or that Captain Video set of walkie-talkies they dreamed about in the back of the comic books. They have purchasing authority now, and they certainly can compensate for that lacking childhood - with grant money! I know my analog seems kinda whacked, but... think about it... seriously.
The operative issue needs to be practicality and service within the given environment. Someone cited NXDN as being indefensible. I can somewhat defend that, because a 4 kHz wide system can be shoe-horned into operation in areas where anything wider cannot be accommodated. What I'm getting at is knowing your functional environment and any restrictions that come with it. I suppose the bottom line is knowing what you need to do the job you need to do and specifying the equipment that will allow you to do that. Analyses of needs is something one usually does not see in the industry or the public sector (most like to take something that already exists and seems to work somewhere else, then plagiarize it to their own organization and environment).