Notes:
If you don't know how to achieve something, then new tools won't cure that. (On the other hand: if they had known what a standard system would look like based on their existing technology then using OO might have made it easier to achieve.)
Reuse is HARD, can only follow use, and needs to be addressed by specific efforts – it isn't an automatic consequence of OO.
Java isn't "platform independent" it is a platform – this has caused issues on some projects targeting devices whose support for Java is poor.
Developing customer project sets goals and priorities that conflict with developing a standard system. This adds cost to the development process, and invariably fails to meet both sets of objectives.
Note:
They had also decided that much of the previously established development process wasn't OO and rejected it. However, no real effort was made to establish a new process.