11–14 of 14 posts
Won't the MPGe values be higher for these vehicles because they are being driven exclusively during summer months so far, when batteries are less efficient in the winter months?
If the efficiency gains vary by production year, that implies it's hardware improvements, as opposed to software tweaks (which would be rolled out fleet-wide regardless of year). I wonder what goes into that experience curve effect?
Tesla doesn’t change hardware by build year. They make hardware changes every day/week/month.
How are they sourcing parts and integrating them into the manufacturing process "every day"? This seems like an SV understanding of manufacturing; Tesla may be more agile than the average auto OEM, but there is still a complex procurement prcoess that requires lead time, as well as spare parts for fleet repair and maintenance.
Do you have an example of a piece of hardware they are swapping every day, week or month? Maybe this is why they have a hard time servicing their cars.
Earlier quoted context omitted.
Tesla doesn’t change hardware by build year. They make hardware changes every day/week/month.
> They make hardware changes every day/week/month. How are they sourcing parts and integrating them into the manufacturing process "every day"? This seems like an SV understanding of manufacturing; Tesla may be more agile than the average auto OEM, but there is still a complex procurement prcoess that requires lead time, as well as spare parts for fleet repair and maintenance. Do you have an example of a piece of har…
They know by VIN exactly what parts go in what car.
That said, the coding equivalent is that they make interfaces - and swap out interfaces. You can make a LOT of changes at the implementation level, that do not change an interface.
> Do you have an example of a piece of hardware they are swapping every day, week or month?
Sure, they are swapping the entire body caste machine from ~20 parts down to 1..
https://www.foundrymag.com/molds-cores/media-gallery/2193204...
went live this week I believe, while they are actively cranking out thousands of model Ys per day.
Another example - the octovalve - a very special decide that lets heat and cold get shared 8 ways as needed between motors / battery / and cabin is a huge part of the model Y. According to a teardown
https://www.thestreet.com/tesla/news/munro-tesla-model-y-oct...
the valve has had 13 changes in the 6 months the car has been in production. 13! In a single part that is the size of a small backpack.
> Maybe this is why they have a hard time servicing their cars.
This has not been my experience at all. I think QC is a little low on brand new cars during rush season, but service has been top notch. Make sure you aren't relying on stories from 2016.
Earlier quoted context omitted.
Tesla doesn’t change hardware by build year. They make hardware changes every day/week/month.
Really? How do they support all those hardware configurations? Is there a policy framework they use to manage software development do it works well with all those configurations?
Same way you can easily refactor code.
For an example see https://www.thestreet.com/tesla/news/munro-tesla-model-y-oct...