Slashdot Mirror


Auto Manufacturers Running Out Of Unique IDs

wakebrdr writes "Y2K all over again? A story in today's Detroit News explains how the vehicle ID numbering system (VIN) will soon run out of unique numbers. According to the article, a member of the Society of Automotive Engineers says, 'Longer codes would require a major overhaul of computer systems that would dwarf the challenges and expenses spawned by the Y2K computer dilemma.' Golly, if it's that serious maybe I should start stocking up on MREs and ammunition in preparation for the day the assembly lines come to a screeching halt."

44 of 567 comments (clear)

  1. Extend the character set? by SIGALRM · · Score: 5, Interesting

    The 17-digit codes that identify the origin, make, model and attributes of cars, trucks, buses -- even trailers -- worldwide will be exhausted by the end of the decade.

    How about extending the allowable characters in a VIN to include certain ASCII or Unicode symbols? Perhaps make them case-sensitive? That would preserve uniqueness--at least for awhile longer--although it might make the codes harder to verbalize (i.e. to an insurance agent).

    --
    Sigs cause cancer.
    1. Re:Extend the character set? by LittleGuy · · Score: 5, Funny

      How about extending the allowable characters in a VIN to include certain ASCII or Unicode symbols? Perhaps make them case-sensitive? That would preserve uniqueness--at least for awhile longer--although it might make the codes harder to verbalize (i.e. to an insurance agent).

      I *knew* we'd find a use for Dingbats Font someday!

      --
      Mod Karma -1: I sed bad wurds. If I cep my mouf shut, I wud be at riyses.
    2. Re:Extend the character set? by Kallahar · · Score: 5, Informative

      reprogramming every device that read's VIN's to accept case sensitivity would be just as hard as adding an extra few digits.

    3. Re:Extend the character set? by Rob+the+Bold · · Score: 5, Funny

      Yes, Mr. Insurance agent, I've got my VIN right here. It's A-1-D-1-squiggle-smiley face-squiggle-1-2-W-musical notes-e with two dots over it-female symbol-B-5-open paren-heart.

      --
      I am not a crackpot.
    4. Re:Extend the character set? by Mick+Ohrberg · · Score: 5, Funny

      How about a VINv6?

      --

      Quidquid latine dictum sit, altum sonatur.

    5. Re:Extend the character set? by matguy · · Score: 5, Informative

      Right, the big thing here is the tooling to punch the codes in to sheet metal or solid metal parts. The tooling is set up to punch certain length codes, just adding another number isn't as simple as just putting another punch on the rack, the whole mechanism would need to be changed in most situations.

      --

      matguy(.com)
    6. Re:Extend the character set? by tomhudson · · Score: 5, Interesting
      Even 10-year-old VINs are sometimes hard to read - (hello, Toyota Tercel, GM and Ford pickups...)
      'Longer codes would require a major overhaul of computer systems that would dwarf the challenges and expenses spawned by the Y2K computer dilemma.'
      No it wouldn't. We've been through this before, in the '70s - when each manufacturer made their VIN any way they wanted to - and most were 13 digits, some less.

      Computer systems today still handle VINs of less than 17 digits with no problems, provided they've been designed correctly.

      So just expand the VIN field by adding a second field of, say, 6 more digits. Vehicles with a VIN of 17 digits or less don't have anything in the second field, those with more than 17 digits do.

      The overflow field doesn't even have to be in the same table - just a lookup to see if there's an entry there for the VIN.

      Or make the first character of the VIN an arbitrary value - say 'O' (the letter 'o', not the number zero, which means "Made in USA", 2="Made in Canada", 3="Made in Mexico", J="Made in Japan, K="Made in Korea", etc... The letters 'I, O, and Q' are forbidden in the current VIN scheme, as they are too easy to confuse with zero and one. Tell the software that anything beginning with an 'O' should be searched for using the new, longer VIN.

      Heck, you could even use a zero, since nobody uses it as the country origin code.

      As I said, it's not that big a deal, as we've been there before.

    7. Re:Extend the character set? by DAldredge · · Score: 5, Interesting

      I did read the article, you did not. If you have you would have learned to following.

      Of 1,056 WMI codes available to U.S. manufacturers, 594 remain, according to SAE.

      One solution that will be considered when the committee votes on a final recommendation in September or October is to reclaim WMI codes that are going unused in other regions.

      More than two dozen countries, from Armenia to Zimbabwe, have up to 288 WMI codes each. All are dormant.

      The group may also reclaim WMI codes from U.S. trailer, motorcycle and other manufacturers no longer in business. SAE doesn't have a precise count, but such defunct companies could be the source of enough WMI codes to supplement another 30 years of use, said Steve Ezar, manager of government and industry standardization at SAE.

      Another possible solution: the WMI code could be revamped so that the third digit, which now indicates brand, will be freed up to denote different information.

      For example, a VIN beginning with 5G1 now describes a Chevrolet built in the United States, while 5G2 identifies a Pontiac.

      But in the future, 5G1 could be used to cover all GM products, freeing 5G2 for -- perhaps -- another manufacturer.

    8. Re:Extend the character set? by EvanED · · Score: 4, Insightful

      This would still result in having to rewrite a lot of software to take the extra field into account. Especially because you could say the exact same argument for Y2K: "So just expand the year field by adding a second field of 2 more digits. Years in the 20th century don't have anything in the second field, those outside do."

      That said, who knows how much of a problem this is; Y2K turned out just fine, though it did take quite a bit of work to make it so...

    9. Re:Extend the character set? by geekoid · · Score: 4, Funny

      the automotive industry has used dingbats for years!

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    10. Re:Extend the character set? by tomhudson · · Score: 4, Insightful
      I specifically stated NOT extending the field, which would mean restructuring each table - rather I stated that an extra field or separate lookup table could be added.

      The concept is not new - I stole it from "Database System Concepts, 2nd Ed. (c) 1991, Korth and Silberschatz", though they used the concept of "overflow blocks" for storing values that clash in a hash, and I'm using it for looking up the extended version of a vin (if it exists).

      This way, since the original tables are not altered, existing queries that do not deal with the extended vin are not affected, and there's a lot less debugging to do - and a lot fewer areas where bugs can creep in.

      The sql statements that do lookups of vins are the only ones that would have to be modified. Not a complex task, since the vin itself (in a properly-normalized database) is not the primary key, but rather gives you back an oid (object id).

      Same problem with SINs, which are also not unique in every case.

    11. Re:Extend the character set? by walt-sjc · · Score: 4, Insightful

      This completey misses the point. It's not just the database: it's the software, forms, etc. for insurance companies, law enforcement, DMV, etc. for all cities, states, provinces, countries, etc everywhere in the world. Each of these systems probably validates what is a real VIN so any changes to the current scheme will cause massive problems. Any addition of a new field will be almost as hard.

      This is obviosly why they are looking at this issue now, so in 10 - 20 years when the current numbers are gone, software can be ready for any new scheme (cause that's about how long it will take.) Hopefully BECAUSE of all the code rewrites for Y2K, this task will be much easier (many old systems were completely replaced in modern languages with modern coding techniques.)

    12. Re:Extend the character set? by tomhudson · · Score: 4, Informative
      As I point out elsewhere, the problem begins in 2009 (for the 2010 model year) when any software that calculates the model year based on the 10th digit is f$cked. That's 5 years from now - not 10 to 20.

      The society should contact people who work on a day-to-day basis writing code to handle the non-standard vins (pre-1980). In my case, I've already put in handlers for post-2008.

      Now, since all current systems ALREADY handle vins that are not exactly 17 characters long (pre-1980) by relaxing the validation schemes and enabling extra user input options, not pre-determining the model year, etc., there's not as much work as you would seem to think.

  2. Slashdotters response: by JesseL · · Score: 5, Funny

    Just use NAT.

    --
    "Prefiero morir de pie que vivir siempre arrodillado!"
  3. Carmageddon by Anonymous Coward · · Score: 5, Funny

    I'm not worried about the assembly lines coming to a screeching halt... I'm more worried about the assembly robots revolting and attacking the population!

    *Duck and cover*

  4. Probably some truth to that. by tgd · · Score: 4, Funny

    My car has a seven digit number as a VIN.

    I had a lot of issues getting it registered and insured, although in most cases it was just a training issue -- the people I was dealing with didn't know how to enter it correctly.

    The Massachusetts RMV had no idea what to do with an odometer in kilometers though, so my title says 9,999,999 miles on it.

    1. Re:Probably some truth to that. by wo1verin3 · · Score: 5, Funny

      >> do with an odometer in kilometers though, so my title says 9,999,999 miles on it.

      Obviously it's not a ford.

    2. Re:Probably some truth to that. by michaelhood · · Score: 4, Funny

      7-digit VIN and 4-digit UID. You ARE oldschool.

    3. Re:Probably some truth to that. by LaCosaNostradamus · · Score: 4, Funny

      my title says 9,999,999 miles on it

      I hope you changed the oil.

      --
      [You have a stable society when some nut guns down a schoolyard and the law doesn't change.]
  5. Re:If I were them by LittleGuy · · Score: 5, Funny

    Actually maybe they already do? If so, then start using the !@#$#$%^%^&*)(*& symbols!

    Those symbols are usually reserved for use *after* the accident with the uninsured driver.

    --
    Mod Karma -1: I sed bad wurds. If I cep my mouf shut, I wud be at riyses.
  6. Alternate Slashdotter's response: by Grayden · · Score: 4, Funny

    Perhaps this will speed the transition to VINv6...

  7. Use More of the alphabet by arieswind · · Score: 5, Insightful

    The second character signifies the manufacturer (General Motors is G, Ford is F, Chrysler is C)

    Why not just give GM, Ford, and Chrysler another letter? GM can have G and H, Ford E and F, and Chrysler B and C

    Surely every manufacturer doesn't produce as many cars as the top few

    1. Re:Use More of the alphabet by Trifthen · · Score: 4, Interesting

      We run an automotive listing and search system. We've been building and maintaining a list of manufacturers for every type of vehicle that started with over 50 manufacturers of regular road vehicles. Personally, I'm surprised they came up with this stupid system at all. One character for country? After removing I, O, Q, U and Z, that leaves 31. Now count how many countries there are in the world - I'll wait until you're done. Why, oh why can't they have designed something more scalable to begin with?

      --
      Read: Rabbit Rue - Free serial nove
  8. VIN numbers as SSNs? by Michael+Pigott · · Score: 5, Interesting

    Maybe one could use VIN numbers as SSNs: when a car "dies" recycle it's VIN number.

    1. Re:VIN numbers as SSNs? by jridley · · Score: 4, Informative

      No, because the VIN isn't just a serial number. It incorporates the year, manufacturer, and a lot of other info. A given VIN is only usable on another car of the same make, model, year, body style, and place of manufacture.

      You could recycle numbers within one year; if a 2005 car got killed in the first year of its life, they could make another 2005 car with the same VIN, but that's probably not going to help much...

  9. I'm not sure... by jbardell · · Score: 4, Interesting

    I'm not sure if the issue is that the VIN's can't get any longer than they already are, but I know that the VIN on an older vehicle (ie. the '60 Chevy pickup I had) is a few characters shorter than a VIN of today. I would think that lengths in between these two would be useable without any major overhaul, but what do I know?

  10. Umm.... that will be $250,000 in modifications by HighOrbit · · Score: 5, Funny

    Let's see... how many manhours can a consultant charge the PHB to run the following SQL query

    alter table VEHICLES modify column VIN varchar(50);

    Yup.. that took countless manhours.

  11. Let me clarify... by GillBates0 · · Score: 4, Informative
    One potential fix: Poach VINs assigned to smaller countries such as Botswana, which don't mass produce vehicles.

    Since the article wasn't clear on this, and a comparison with Y2K was made.

    The current VIN system is local to the US (and probably Canada, not sure). Other countries do not share the VIN system/database/namespace. Sure, the manufacturers are located all over the world, and there's a unique ID for country of manufacture, but the VIN numbering is only mandatory for vehicles in the US.

    Other countries have their own numbering system (usually a chassis/SL No.), and their databases are built around their unique identifiers.

    So yes, their proposed solution is feasible, because right now, there are Country codes assigned to countries which will most likely not export vehicles to the US in the near future. But the comparison with Y2K is off because of the fact that this problem is local to the US.

    --
    An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
  12. Re:CRY! by OverlordQ · · Score: 4, Interesting

    no:
    2004-07-17 Sat - GPS Receiver Almanac Rollover, 256 weeks after GPS 1024-week rollover.
    2004-12-31 Fri - 2004/366 - cf. 1996-366.
    2005-??-?? ??? - "Some *really* old versions of UNIX (e.g. 16-bit BSD) die in 2005.".
    2005-11-29 Tue - 04:53:20 UTC : 212 Gs from JD 0.0.
    2006-03-29 Wed - Solar Eclipse, Brazil - Africa - Turkey - Asia.
    2006-12-31 Sun - HP3000, End Of Life.
    2007-01-01 Mon - Lithuania joins the Euro?
    2007-01-01 Mon - "USA FAA computers fail, 32 years from 1975". TZ? 2006?
    2007-08-09 Thu - CMJD 54321.
    2008-01-19 Sat - 30 years before 2038-01-19 - mortgage look-ahead?
    2008-03-23 Sun - Easter Sunday is unusually early this year (previously this day in 1913 & next in 2160; earliest, March 22, 1818 & 2285).
    2009-01-01 Sun - NOAA: Termination of satellite processing of distress signals from 121.5/243 MHz emergency beacons. Use 406 MHz.
    2009-02-13 Fri - 23:31:30 GMT is UNIX time_t 1234567890.
    2009-09-09 Wed - 090909 is another possible valid nonsense or marker date; as with, of course, other 0x0x0x & 1x1x1x dates, or anything with YY small.
    2???-??-?? ??? - Introduction of the Euro in the UK ???
    2010-01-01 Fri - Y2.01K. There will be some who have coded only for Years 200#.
    2010-01-01 Fri - Sorting YYMMDD decade-reversed covers 1990-2009 only.
    2010-01-01 Fri - Reported ANSI C library overflow. Very dubious. RSVP if you can explain it.
    2010-12-25 Sat - CMJD 55555.
    2011-09-14 Wed - @01:46:39 UTC less leap seconds, GPS 999999999 seconds.
    2011-11-11 Fri - Seen as a "marker" date - cf. 1999-09-09. Contains 11/11/11 11:11:11.


    taken from: Critical and Significant Dates

    --
    Your hair look like poop, Bob! - Wanker.
  13. They could mix up the alphanumeric rules a little by beef+curtains · · Score: 5, Insightful

    As a software developer for a gargantuan insurance company, let me assure you that I would be rather grumpy (to say the least) if I came into work one day and was told we have to overhaul our VIN-handling code. That would suck. Royally.

    However, automakers could start mixing some alphas into the numeric vehicle-identifier portions of VINs...this could provide a few million (at least...too lazy to do math) more string combinations, and wouldn't affect the parts that IT people care about.
    --
    Just once I'd like someone to call me 'Sir' without adding 'You're making a scene.'
  14. Wait, what part of this should be surprising? by Mongoose+Disciple · · Score: 4, Informative

    Let's think about this:

    They designed the system in 1981.

    They expected it to last 30 years.

    So that's... until 2011?

    And now they're saying it'll run out around the end of this decade. That'd be about 2010-2011ish, no?

    Sounds like everything's going according to plan.

  15. Re:I for welcome our new VIN invaders by Crazy+Man+on+Fire · · Score: 4, Insightful

    Um, actually, if they expected it to last 30 years and they expect to run out of unique VINs at the end of the current decade, it will have lasted 30 years.

  16. So many cars in the world... by eamacnaghten · · Score: 4, Interesting
    Hmm - let me see - a 17 digit alphanumeric field - that is 286,511,799,958,070,431,838,109,696 different combinations.

    I know they had made a lot of cars, but that many?

    --

    Web Sig: Eddy Currents

    1. Re:So many cars in the world... by OverlordQ · · Score: 4, Informative

      Your math doesn't hold up. Just because there are 26^17 combo's doesn't mean they all can/could be used.

      EG: characters 4-8 are body style/features/engine/type/etc and 10 is the year.

      I'm sure a car from 2004 will have any of the similar features of a car from the 80's, so there goes 1 whole factor, down to 26^16, I'm sure if you went through the other characteristics it would narrow it down even further.

      --
      Your hair look like poop, Bob! - Wanker.
  17. Ooooooooh well. by rice_burners_suck · · Score: 4, Interesting
    Well, this is a pretty serious situation, but slightly different than the Y2K problem. First of all, most of the software affected by Y2K was written in COBOL and ran on all kinds of mainframes. These were the kind of computers that had been programmed and debugged at one point in the past, and were eventually made to work flawlessly. They ran so well that the companies using them almost forgot they existed. When Y2K started approaching, it was suddenly necessary to dig up a bunch of really old systems, for many of which the documentation, or even the source code, was missing. Imagine having to re-create programming that had existed for years, just to keep date records correct. This was a huge expense for many organizations. The Y2K problem, however, only affected the kind of software that used 2 characters to store the date. Most programming done since the 80's, or even a bit earlier than that, uses integers to keep track of the date, and there are different dates that these things will roll over. So they are not affected by Y2K per se, but by a similar problem that will affect various systems from time to time.

    On the other hand, the VIN problem will affect a larger number of computers than the Y2K problem. There are, of course, the few big manufacturers, who keep track of parts and whatnot. There are thousands of dealers, and perhaps tens of thousands of auto repair facilities. Then, of course, there are all the governments around the world that keep track of auto registration. All of these locations use VIN numbers in various ways, be it for record keeping, tracing design decisions and parts, locating parts for repairs, etc. Now imagine that all of these locations, some very big, and some very small, need new programming because of a change to the VIN system. And this change will affect all of these locations at the same time, not from time to time as with date rollover problems. Further, most auto repair facilities use computers and programming that they obtained years ago, and who knows if the software vendor is even around anymore. The source code is probably long gone for many of these applications.

    The problem is that the VIN numbers are being used up as new vehicles are being manufactured. When the last VIN is gone, all of these systems will have to be up to date for the change, and that means a lot of money spent on new computers, new programming, and whatever trouble it takes to convert old records to the new system, which will have to be backwardly compatible with the old VIN numbering system.

    Let this be a lesson: Whenever a unique number is needed, let's use about 40 digits in a base 36 system, consisting of letters and numbers. That'll cover us for a while.

  18. Good for speeders! by Just+Some+Guy · · Score: 5, Interesting
    I got clocked once at a pretty decent rate on an interstate highway. I was in the military at the time and in uniform, and the nice highway patrolman wrote the ticket for 5 mph over the limit (which was significantly under my real speed, unless you're my insurance agent, in which case I was framed, darn it, framed!).

    I had recently upgraded my car and my home state lets you move your license plates to your new car as long as you sell your old one at the same time. Fortunately for me, the state hadn't gotten around to turning my '68 Mustang into a '92 Prizm and the patrolman copied the information straight from the computer to the ticket.

    When I received a summons in the mail, I disputed it with the cause being that I was in a '92 Prizm and did not even own a '68 Mustang, and the complaint was completely dropped.

    The moral of the story: if I find out that I share a VIN with an Edsel on blocks in some farmer's pasture, then the police will have to use a spectrometer to measure my speed. I'll be driving my "get out of jail free" car until the sonic booms shake it apart.

    --
    Dewey, what part of this looks like authorities should be involved?
  19. Re:Uh-oh by AKAImBatman · · Score: 5, Insightful

    I wouldn't worry too much about it. Every industry eventually hits this dilemma and every industry deals with it in their own way. Just a few years ago (actually prior to Y2K), some of the companies in the business of Livestock Genetics were worried they'd run out of Bull numbers. (I think the standard was something like AC0023 where the first two digits identified the company and the last four were the bull's number.)

    The various companies formed an IT standards committee and came to an agreement on extending the numbers. It took a year or two, but the systems got converted and life went on. It really wasn't that big of a deal. As a bonus, a real standard for data processing showed up. The previous number scheme was designed for paper and allowed for certain variations which gave computer systems a fit. e.g. Sometimes the number might be written as AC23 or simply 23. This made it difficult for a computer to decide if the code was the domestic code or the international code.

  20. Re:I for welcome our new VIN invaders by killmenow · · Score: 5, Insightful
    Ok, so what we have here is:
    1. a claim that the VIN system was created in 1981, and expected to last 30 years
    2. a claim that the numbers could run out by the end of the decade
    So, they expected it to last 30 years, and now somebody says it'll probably only last 29 years and you say, "I really hate to see somone that points out that 'It'll Last for X years' and it never does.'

    I don't know about anybody else, but if 23 years ago, someobdy engineered a system that was expected to last 30 years...and they were only off by one year...I'd cut them some slack.

    Granted, they should've thought about what would happen after thirty years, but they probably did. In fact, they probably thought long and hard about it and decided either:

    (a) we'll all be teleporting everywhere by then and cars won't matter anymore; or,
    (b) we'll all be retired by then so who gives a rat's ass.
  21. BSD by Anonymous Coward · · Score: 4, Funny

    >2005-??-?? ??? - "Some *really* old versions of UNIX (e.g. 16-bit BSD) die in 2005.".

    See! BSD is dying!!

  22. Re:Good by no+reason+to+be+here · · Score: 5, Interesting

    Why does the government feel that it needs to know the "ID" of my vehicle? What business is it of theirs?
    Because they have an interest in making sure that that vehicle is safe to drive (safety inspections). Also, it makes it a little more likely that your car could be recovered if it were ever stolen. Also, I believe (not certain) that VINs are global, voluntarily created by automotive manufacturers; therfore, they wouldn't be just a US thing. Furthermore, the gov't provides all the roads on which you would be driving. The gov't identifies your car by its license plate. You give your VIN when you register your car so that there is something else to match it against other than the plates if it is stolen, in an accident, etc.

    This is no different than other government-mandated identity programs such as Social Security numbers.
    Yes it is. One has to have an SSN in the US, no matter what. One doesn't have to own a car (well, in some instances one DOES have to own a car, but people in a large enough metropolitan area don't have to).

    Not to get tin-foil-hatty,
    too late

    but if you've read books like 1984 or studied leaders like Hitler, you will know that programs like this (even if they start with the best of intentions) end up going way down the slippery slope, usually with disastrous results.
    A VIN isn't going to lead the SS to your door step. No one knows the VIN on a particular automobile unless they are standing right next to it and looking right at where it is printed. Now if you smash your car into a bus load of orphans, and you flee the scene on foot, then maybe the cops could check the VIN to see to whom the car is registered, and then come arrest you later. Of course, they could just as easily check the license plate.

    Slashdotters were (rightfully) up in arms a few years back when Intel planned on embedding unique IDs into their Pentium III chips. Yet we blindly accept VINs and other intrusions into our privacy without question. Why?
    Maybe, just maybe, /.ers see VINs as just a serial number on a car, not some sort of gov't tracking system devised by the Illuminati. I think most /.ers don't like SSNs (to use your other example), but they are way, WAY too entrenched to just rebel against. Pick your battles, as they say.

  23. No way! by SuperKendall · · Score: 4, Funny

    Impossible! How would they reach us, why they'd need a million cars to... oh. Crap!

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  24. The answer is obvious - VIN portability. by djh101010 · · Score: 4, Funny

    Now, we just need some clueless politician and/or judge to decree that we need to be able to keep the same VIN when we switch cars. After all, it's just as personal as a phone number or an IP address, right?

    Who cares if it completely neuters the data model, is hard if not impossible to implement, and results in massive confusuion and overhead nightmares, it's the in thing to do, making all these pesky numbers portable.

    Come to think of it, my VIN already is portable, I put a few hundred miles on it a month.

  25. Actually, it's two characters for country... by Otto · · Score: 4, Informative

    It's just that countries get a range of those two characters. While the US has 1*, 4*, and 5*, and Canada has 2*, Mexico has 3A-3W and Costa Rica has 3X-37.

    The whole first three characters (known as the WMI) get assigned by the SAE, according to whatever-the-hell-system they feel like using. They just happen to assign it certain ways.

    Google for "VIN Country Codes" for the complete list.

    --
    - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
  26. DMV Training by ArsSineArtificio · · Score: 4, Funny
    Could you please share with us what "training" you did at the RMV

    It puts the numbers in the correct boxes, or else it gets the hose again.

    --
    All employees must wash hands before seeking equitable relief.