It's not universally done, though. It depends on how the program office(s) involved decide to run things.
EDIT: To expand. Look at space systems. The ground stations are not tied to specific space systems (though some space systems develop their own ground networks), that is a separate program from the satellites and SOCs. There is no one "space program". And even for a particular satellite system the SOC may be under a separate contract vehicle than the satellite itself.
NASA did this with the commercial crew program, awarding to both SpaceX and NASA to reduce risk.
Though you also have that done for aircraft. The F-35 was selected among several aircraft that were being developed by various contractors as the one to move forward as the JSF. This is where the lifecycle of a program comes into play. In the R&D stages you'll see multiple options quite commonly because they want to compete different vendors. Eventually it whittles down to one for things like aircraft to move forward. Though, using the JSF as an example, maybe they should select multiple. LM were the geniuses that thought you could increase software productivity by hiring more programmers and having them work in shifts.