Bear with me, while I sort this.
Things we know for sure (facts):
Rumours/assumptions:
Theory:
Assuming that everything was planned to deliver the first OTA capable car from VW, everything fits with a simple testing procedure of the OTA system. What do you need for a test of OTA: access to lots of cars, that you can check and verify the delivery of the update.
So, you need to build a large number of cars, stockpile them with a beta version of the software. They all need to be connected (smart at that point). Then send the updated software OTA. But you still need a confirmation of the test, so send an engineer to every car to verify the update.
But the OEM still has an issue with the testing, meaning that is has only delivered in a highly controlled environment. So, one more test is needed, where you release the cars with v1 of the software in Sep. At a later date, v2 is released which delivers on the missing functions. But these are things that the customers can easily verify and report in case of problems. This has the benefit of demonstration of OTA to the customer (shortly after delivery) and obvious benefits to the manufacturer.
Things we know for sure (facts):
- new car software with capability for OTA updates (new to VAG);
- Stockpiling of cars (not unique, seems to have happened with other OEMs);
- All 1st Edition cars to be delivered at the same time in early Sep'20;
Rumours/assumptions:
- stockpiling seems to have been planned in advance;
- software issues (rumours with very limited details about specifics). VW officially announced some missing software features at release of 1st Ed, which to me at least sound irrelevant (speed display and smartphone connectivity).
- My assumption is that the cars are being delivered on time from the original VW announcements of "summer 2020";
Theory:
Assuming that everything was planned to deliver the first OTA capable car from VW, everything fits with a simple testing procedure of the OTA system. What do you need for a test of OTA: access to lots of cars, that you can check and verify the delivery of the update.
So, you need to build a large number of cars, stockpile them with a beta version of the software. They all need to be connected (smart at that point). Then send the updated software OTA. But you still need a confirmation of the test, so send an engineer to every car to verify the update.
But the OEM still has an issue with the testing, meaning that is has only delivered in a highly controlled environment. So, one more test is needed, where you release the cars with v1 of the software in Sep. At a later date, v2 is released which delivers on the missing functions. But these are things that the customers can easily verify and report in case of problems. This has the benefit of demonstration of OTA to the customer (shortly after delivery) and obvious benefits to the manufacturer.