Yes, it's called "wiring" a contract. When I worked at a company that sold specialized processors to the government we ran into that all the time. Usually it was something defensible on its face, at least, like software compatibility with a previous piece of hardware.

But sometimes we would see unimaginative stuff like a specification of the LED layout on the front panel or very specific weight restrictions that happened to fall between our hardware and the preferred vendor.

In the government's defense, though, the system is set up to combat this tendency, at least for smaller contracts. When I was on the other side (having left the vendor to work for our civil service customer) we would routinely get pointed questions from the purchasing people regarding this or that line of the RFP - was it really required, or were we trying to wire the contract?

That's common I think in just about every government procurement deal. In higher ed we would choose the service or software we wanted to buy. then write the procurement request to fit that product. And in many cases the vendors that deal with Higher ed and government contracts, provide guidance with writing the request.

It's common in telecoms too. We get RFPs that are pretty much lifted from the spec page of a competitors (incumbent) product.