They do understand, that is the reason for standards that you could enforce as a mayor customer, if not on all your operations, in your primary ones. It cost a lot of money to depend on just only one company that knows you can't change to their competence(monopoly cost), too.
I'm not saying the incumbent should always win. Far from it. We've bult a business on disrupting that exact scenario, but you'll find that your customer relationships are short lived if you treat vendors as universally interchangeable cogs. You have to listen carefully to the vendors and the stakeholders inside the purchasing organization, and make sure you hold the challenger accountable for their promises.
It could be that when writing a RFQ that there is a similar method: one decides first what product/team you want, then write the RFQ to match that product/team. Not that that excuses the gov't just that it's a standard way to game the system.
I work part-time with the department of interior, and they've tried writing job specs like this, and the person they wanted to hire has never made it through OPM.
> It could be that when writing a RFQ that there is a similar method: one decides first what product/team you want, then write the RFQ to match that product/team.
This is done all the time in private industry as well. "Politics" isn't limited just to governments.
Indeed. But is it good for the US government (or any other IT user) to lock themselves in to one supplier? Probably not.
I have a certain amount of sympathy for the government employees in these situations. Imagine you have a staff full of people with a specific skill set -- a bunch of MCSEs, for example -- yet the law says you must write your specifications in such a way that any vendor can answer the RFP. What are you supposed to do with your team? There is often, but not always, a change management factor applied to bidders where significant changes are required, but managers don't always accept these facts. They don't understand, for example, why the guy who was trained to fix John Deer tractors can't readily switch to servicing a fleet of Kubota tractors without taking technical courses on the new product and changing out some tooling. These things cost money that may not be made up by a short term savings on capital expenditure. The problem is, "that's the next guy's problem".
I just hope that the result of this lawsuit is what's good for the US Government, not just what's good for Google.