EAP is indicated on the window sticker and it's been 12 days since it was ordered. I asked the delivery center to ensure it's installed on the car before I picked it up.
If they would have told me EAP wasn't installed on the car before picking it up, I would have left it there until it was. It would probably be done by now.
Engineering has nothing to do with contracts. When I called Tesla they said it's just a software update and I don't have to go back to the delivery center to get EAP. Of all the people I've spoken to at Tesla, nobody has stated why it's taking so long but was told to just be "patient." They can't even tell me when it's going to be installed in my car. That's the frustrating part.
This isn't a repair or something that requires troubleshooting where you don't know how long it's going to take. It's a fixed timeframe. They should know how long it will be.
Coming from a software engineer's perspective, it isn't always as simple as click-and-you-get-it. Judging by how Tesla's infrastructure has been slowing down with the Model 3 ramp up, my educated guess would be this:
1. Not too many people order EAP after the fact of vehicle purchase. With this being the case and EAP not loaded into the vehicle upon initial build, that means a completely separate system would be in place to deliver this software update.
2. Since this isn't a situation that happens often as just mentioned, my bet would be that the internal software team doesn't have a completely automated system for this setup. When you're talking about software automation and large corporations such as Tesla, it always comes down to dollars and cents. I'd be willing to bet that pushing the update to you can't be done without a software engineer actually doing it. Probably isn't an interface created for a non-engineer to do it because financially it may have not made sense to automate this.
That may sound ridiculous given how long EAP has been out, but non-critical business software gets pushed to the bottom of the barrel all the time, in any industry.
3. Pushing software updates across a cellular network to thousands of people isn't a simple task. It's actually quite a monumental effort. You don't just broadcast an update to everyone. There are so many factors that come into play in regards to this; model of vehicle, configuration of vehicle, location of vehicle, connectivity, size of the update, queueing, etc.
None of this info probably assuages any of your irritation, but I thought it would be helpful to get a little insight (albeit a guess).
