Alstom is using its own software and hardware on future ETCS electrostar retrofits, so expect Alstom software on future Derby products.But the questions are, does Alstom use a robust, well written code base, including the reuse of reliable code in its own products, unlike the former Bombardier’s and since the takeover by Alstom, given that it evidently doesn’t work, how much chance is there of Alstom pulling the plug on this worthless outsourcing experiment and replacing the software on the Aventras or any new build stock based on something of it’s own that works?
Most manufacturers have had software issues, the 700s and FLIRTs weren't issue-free but they got pretty quickly resolved while Bombardier took over a year on the 710s suggesting the problems were far deeper.
If your software is laid out well into modules then it's very easy to reuse code, it's very difficult to reuse code and maintain code when it isn't laid out well.I’ve been told that the Desiros still run on Windows 3.1, so would the Siemens attitude to reusing well written code that works be very different?
Moving OS depends on what technologies they've used but often isn't that difficult if the underlying technologies can be compiled for different OSes. Bombardier moved to Linux for the 379s (not 387s AFAIK) and early Aventras (initial 345 code).
Keeping it on early Windows (very common for TMS, Alstom did the same) is minimal work but can cause issues with hardware obsolescence and support from Microsoft ending as well as licensing from Microsoft.