One one of my factory tours, they did say that the VIN is assigned right at the start of body assembly.
I think that some of the early Sigs have had VINs preassigned, so that we don't get some random number.
yep. That's my understanding too. I'd love to see another tweet from Elon of MXs on the body line #2 or the vehicle final assembly line. This market needs to know that some production has begun on the signature series MXs
The timing is about right to be starting Signature production if Tesla wants to get all of the US models delivered before the end of the year as they keep saying they want to.
I wonder what they will do with the VINs of people who cancelled. They could fill them in with people from the waitlist or skip them entirely. In any case, the VIN doesn't necessarily indicate production order so there wouldn't be a major advantage either way.
I would doubt if they preassigned VINs based on Orders (Signature or Production). VINs are encoded with what is actually installed on the car. [TH="width: 13%"]Position[/TH] [TH="width: 30%"]Description[/TH] [TH="width: 57%"]Value[/TH] 1-3 Manufacturer 5YJ = Tesla Motors, Inc. 4 Make S = Model S 5 Body Type A = 5 Door Hatchback LHD (Left Hand Drive) 6 Restraint System 1 = Manual Type 2 Seat Belts (Front, Rear*3) With Front Airbags, PODS, Side Inflatable Restraints, Knee Airbags (Front) 7 Battery Type E = Lithium Ion Battery - Electric 8 Motor/Drive Unit 4 = Performance Dual Motor - Three Phase A/C Induction 9 Check Character 1 10 Model Year F = 2015 11 Location of Manufacture F = Fremont, CA, USA 12 Serial #, 100,000s digit 1 13-17 Serial Number Digits 56789 There is a configuration part of the VIN of what features are installed. So to assign a VIN for an non-configured order is not feasible (the VIN also has the Vehicle SN and Model Year). Once an order is confirmed and Tesla starts production of what will be built, the VIN can be assigned. I would imagine Tesla assigns the VIN at beginning of Production, as part of Work-In-Process accounting to keep track of assets moved from inventory to the vehicle, then finally to Finished Goods Inventory and ultimately to Delivery. The good news seems to be that VINs assigned to some signature orders (not reservations) indicated Tesla is actually placed those Model X's in production. We just don't know the build numbers and timing. Hopefully ModelXtracker will help gauge the timing.
So you have a beautiful VIN. Do you have a delivery date? Or an indication which month that delivery will be in? Or, heck, which year?
When my status changes, i'll let everyone know. (meaning, I love all you guys, but the numerous pm's hoping for more info just are making me a little nuts. I got nuthin'.)
a) in my defense, at least I didn't send a PM b) that sounds like a great idea c) maybe you should just post an update at a reasonable frequency. How does every 4 hours sound?
Neither did I. Having too much fun enjoying the 7.0 software in Model S Signature. The new upgrade provides training to learn to love the new interface before the delivery of Model X.
All we need is an API boolean didBonnieGetHerX(); Or a more elaborate version perhaps int whereIsBonniesX(); go crazy defining an enum with the int values. #Xobsessed [emoji16]
Sorry, but that's a terrible API definition. Hey, forum geeks, can we please get some serious bike-shedding going here? The simplistic idea would of course be bool didBonnieReceiveADeliveryDate() but that's a little redundant because a better approach would be struct tm *getBonniesDelieverDate() and then return a NULL pointer if you don't have a delivery date yet... See how much easier this is with good API design?
I actually went complete nerdo on my first "draft" and then toned it down 3 times.. I have underestimated the nerdom and technical prowess on this forum! High5 for the proper font too !!
Thanks for the spelling check. Problem fixed. Getting back to enjoying the software update was on my mind instead of double checking the post.