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."

567 comments

  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 Anonymous Coward · · Score: 1, Insightful

      Case Sensitive?...smoke much crack? Have you ever tried to read a 25 year old rusty-arse VIN?

    3. Re:Extend the character set? by Anonymous Coward · · Score: 0

      although it might make the codes harder to verbalize

      Have *you* ever tried to read the post you're replying to?

    4. Re:Extend the character set? by DAldredge · · Score: 1

      How does your 'solution' stop the need to reprogram every system that uses VINs?

    5. 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.

    6. Re:Extend the character set? by AndroidCat · · Score: 2, Insightful
      vin varchar(17) null,

      Might work. I doubt if any of the code tries to manipulate it as a number. (Unless there's a checksum built into it.)

      --
      One line blog. I hear that they're called Twitters now.
    7. Re:Extend the character set? by _14k4 · · Score: 1

      Except for all the code that polishes user input with the "upper()" function... :/

    8. Re:Extend the character set? by Devil+in+Building+9 · · Score: 1

      the need to reprogram every system

      What on earth is the big deal about changing some validation routines? In Y2K we did that on millions of systems and software, you didn't object to that did you?

      This is a piece of cake compared to Y2K.

    9. Re:Extend the character set? by AndroidCat · · Score: 1

      Bah! It's not a vehicle indentification number and it's 17 characters, not digits! (Of course I remembered that after my previous post.) Stupid bad terminology.

      --
      One line blog. I hear that they're called Twitters now.
    10. Re:Extend the character set? by AuMatar · · Score: 1

      One major mistake- you're assuming SQL. I rather doubt that everything that uses VINs uses SQL. In fact, I'd be surprised if its a fraction of that. Don't forget that the old databases from when the systems started predate SQL, and that the data will appear in records and programs that don't involve databases.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    11. 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.
    12. Re:Extend the character set? by Anonymous Coward · · Score: 0


      Well, you can't have a solution with ZERO effort. Y2K was a big rewrite of alot of stuff.

    13. Re:Extend the character set? by DAldredge · · Score: 0, Troll

      When you get in the real world you will begin to understand that such a change would cost a lost of money and there are other ways to increase the amount of usable numbers.

    14. Re:Extend the character set? by AndroidCat · · Score: 1

      Oh, I think I'm safe in saying that at least one major auto company uses SQL. Really really old SQL. That line didn't come from one of their tables, of course.

      --
      One line blog. I hear that they're called Twitters now.
    15. Re:Extend the character set? by Mick+Ohrberg · · Score: 5, Funny

      How about a VINv6?

      --

      Quidquid latine dictum sit, altum sonatur.

    16. Re:Extend the character set? by LaCosaNostradamus · · Score: 3, Interesting

      You must be talking about an escape sequence, which will allow a much larger space of definition, although those definitions will be more fluidly defined due to the very nature of extension.

      For instance, a bit can be taken from the existing set, which if 1, indicates "an extended code follows". Then you can add as much as you want, since it's just a freakin' data stream.

      Realistically, anything that causes a car company to alter its design, specifically to redesign to accomodate a change in standards, is something they'll complain about. However, if they can leverage the change into something "featuriffic" for the customer -- like being able to design your own watchpoints in the car's codespace and other stuff like that -- then they can merrily design it up and just as merrily make it into a good-paying option.

      --
      [You have a stable society when some nut guns down a schoolyard and the law doesn't change.]
    17. 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)
    18. Re:Extend the character set? by Audacious · · Score: 1

      I'm surprised they aren't using a barcode of some sort. Then all letters are usable including the extended ASCII character set.

      But to tell the truth - the extended character set is really hard to read sometimes. After all, how would you tell if the vertical line were on the left, middle, or right? What's a square mean?

      I'm also surprised that they only allocated one digit for the year. Didn't we learn anything from Y2K? Why not use two letters and have 1024 years? By the time the numbers rolled over the original cars would be nothing but piles of rust.

      --
      Someone put a black hole in my pocket and now I'm broke. :-)
    19. Re:Extend the character set? by AuMatar · · Score: 1

      THats not the point. You don't have to fix just 1 piece of software, you have to fix EVERY piece of software that EVERYONE uses. That goes from insurance to manufacturers to government. Unless they manage a hack to keep 17 digits, it will not be a simple fix.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    20. Re:Extend the character set? by drinkypoo · · Score: 2, Informative
      Unicode symbols take two bytes to represent. Well, in the interesting form of Unicode. Automotive VINs basically come in two flavors. The earlier and simpler flavor is just a short serial number. The form used today is a string of a specific length which may only be made up of alpha characters, and some of those characters actually have specific meaning to others, and many of them have specific meaning to automakers. For instance, by reading the VIN on my (now stolen) '86 IROC I was able to find out that the reason the paint was coming off is that it was painted in Van Nuys, CA. Kind of amusing in a car which was from TX...

      The reason this is such a major issue is because you cannot do precisely what you suggest. Most of the states are probably still using heavily antiquated systems to run their licensing operation. This is particularly true in California, whose Department of Motor Vehicles spent some absurd amount of money on what ended up being an already-ancient system to replace their old system. Like most state agencies, they've got shiny new PCs on their desks with flat panel displays, and they're using a terminal emulator (probably 3270) to interface to the systems in which they do all their work.

      Given certain apparent truths about bureaucracies, this is probably true to some extent in most of the world. Many systems worldwide would need to upgraded in order to implement a substantial change in VIN encoding, including licensing authorities, car insurance software, law enforcement databases, and others.

      I guess there is an up side, though... you COBOL programmers have some more work coming.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    21. Re:Extend the character set? by Devil+in+Building+9 · · Score: 0, Troll

      When you get your head out of your ass you will realize that (a) some things worth doing cost money and take effort, and (b) you don't have all the answers.

      there are other ways to increase the amount of usable numbers

      I honestly am not trolling here, but waiting for your suggestions... I mean the Society of Automotive Engineers is brainstorming to figure this problem out, and here you are with all the answers. Please contact them, or RTFA and shut up.

    22. 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.

    23. 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.

    24. Re:Extend the character set? by aiabx · · Score: 1

      Yes, there is a checksum built in. I think it's the 11th or 12th digit.
      -aiabx

      --
      Just this guy, you know?
    25. Re:Extend the character set? by Xoder · · Score: 2, Informative

      Many manufacturers do use barcodes (Code 39, in fact, which only supports the uppercase characters, the numbers, and about six punctuation characters), in addition to the standard metal-punching method. However, they do need to keep that method, for the "rusty VIN" reason stated above, metal is more robust than stickers.

      I worked for a barcode reader manufacturer for a while and we got calls from people wanting to use our scanners in just that way, because ours use Bluetooth, and you don't want to deal with wires when you're leaning over a car.

      And, in reference to my parenthetical above, not all symbologies support the full ASCII set, in fact, very few do. Barcode Island has some nice low-level specs about specific symbologies.

      --
      The previous sig has been removed due to /. protecting your best interests
    26. Re:Extend the character set? by MagicDude · · Score: 1

      Does the phrase "suck it up" mean anything? It's tough now, but in the end it's really the only permanent solution. Plus, how does this problem dwarf the Y2K problem? Maybe I'm missing something, but how much needs to be changed? You'll need to update the manufacturer's computers, law enforcement computers, insurance computers, and maybe a few others. Now, that's a lot less than Y2K where you had to update, ummm, (echo) EVERYTHING IN THE KNOWN UNIVERSE (/echo). It sounds like it's just the company complaining about how they have to finally pay for upgrades. Understandable, but they need to deal with it.

    27. Re:Extend the character set? by shaitand · · Score: 1

      Y2k was a phantom for every system reprogrammed, rechiped, patched, etc there were hundreds or even thousands that were not and have not been.

      The problem wasn't really a problem ;) Any good programmer told you that prior to the year 2000.

    28. Re:Extend the character set? by tomhudson · · Score: 1
      Damn, something ate my "1=", in 1="Made in USA"

      Sorry :-(

    29. Re:Extend the character set? by tjic · · Score: 1

      What Unicode plane contains the-artist-formerly-known-as-Prince 's name? That would be a *great* thing to embed in a VIN.

    30. Re:Extend the character set? by Anonymous Coward · · Score: 0

      How bout using IPV6 technology.
      Short, sweet, simple fix.

    31. Re:Extend the character set? by Short+Circuit · · Score: 2, Informative

      It sure was a problem. But on systems where it mattered, it was fixed. A manufacturing firm's toxic-materials(read: paint) usage tracking computer can't afford to have flawed data points (the fines are tremendous), but most home PCs don't have any such responsibilities or consequences.

      The problem here is that nearly all the systems affected matter, from ownership registries to insurance calculations.

    32. 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...

    33. Re:Extend the character set? by jekewa · · Score: 1

      Perhaps just using letters in more places, or even just use all of the letters. The article broke out the, uh, breakdown of the VIN string; seems that there are some unused letters in the year code, for example. And if the serial number isn't strictly a number, but more of a code, they'd go from 10^6 to 36^6 just by allowing 000000 to ZZZZZZ.

      --
      End the FUD
    34. Re:Extend the character set? by FictionPimp · · Score: 1

      That all seems short sighted. It also doesn't seem to take into account new car companys that may popup in the future. The fact is they are just prolonging the real solution, and at some point, they will have to do something. And the longer they wait, the more money it is going to cost. Old systems will loose source code and documentation, lack of qualified programmers for outdated languages etc.

    35. Re:Extend the character set? by DAldredge · · Score: 1, Troll

      No, it will not cost more in the long run if done correctly. You write a standard and say in 10 - 20 years the new standard will take effect. When new systems are bought/written design them so they can use the old style and the new style vins. When the 10 - 20 years is up you switch.

      That isn't nearly as disruptive.

    36. 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
    37. Re:Extend the character set? by kannibal_klown · · Score: 1

      Depends how you "word it."

      It was a problem, and COULD have been serious had people not been working on it. I say serious only in situations where a more-legacy system was running something very volitle (maybe some nuke silos, waste disposal centers, etc). But it was HIGHLY overrated.

      For 99.99999% of the systems out there, it was no big deal if the systems did go down, and most didn't

      Hell, I was still working as a cashier back then, and our store's computer system went down (we were running off an old 386 system). It handled all of the registers.

      I said "Fuck it" and went home. There was no way in hell I was going to look through a book of barcodes to find the prices of all of the items people were buying (I wasn't really supposed to work that day anyway). I talked to some friends later, and they said it sucked, because people were buying shit left and right because they thought Armaggedon was still possible.

      I laughed, and quit shortly thereafter.

    38. Re:Extend the character set? by Nefarious+Wheel · · Score: 1

      How about another code to show how many times the VIN has been ground down and re-stamped?

      --
      Do not mock my vision of impractical footwear
    39. Re:Extend the character set? by Anonymous Coward · · Score: 1, Funny
      Y2K turned out just fine, though it did take quite a bit of work to make it so...
      That's crazy talk!

      I know because Billy-Jim-Bob two pages up said Y2K was no big deal, and everyone knows 15-year old Slashdot posters are the most knowledgable geeks in the known universe.
    40. Re:Extend the character set? by WushuJim · · Score: 1

      Case sensitive might not even be necessary. If there are 36 possible characters (A-Z,0-9) with 17 digits, allowing just one more character such as a # increases the amount of possible VIN's by 60%. Two additional characters increases the possibilities by 150%. Characters such as # and & can easily be distinguished between numbers and letters. It may be a temporary fix, but it certainly could work.

    41. Re:Extend the character set? by dfenstrate · · Score: 2, Insightful

      Considering every year they build and rearrange whole assembly lines to crank out thousands of vehicles no one has ever seen before, I'd say retooling is rather a minor issue here.

      On the other hand, with the myriad of computers involved in DMV systems, parts management, etc, I can see how the programming part of the matter would be very difficult.

      --
      Alcohol, Tobacco and Firearms should be the name of a store, not a government agency.
    42. Re:Extend the character set? by PiercedSoul · · Score: 1

      Why not something simple, like 2004Corvette1, 2004Corvette2, etc? Wouldn't that make sense?

    43. Re:Extend the character set? by gewalker · · Score: 1

      I for one look forward to this. I've spent most of the last 2 years interfacing EDI systems for quite a few automotive systems. Just think of the additional billable hours.

    44. 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.

    45. Re:Extend the character set? by StarOwl · · Score: 2, Interesting

      The check digit is position nine.

      Of course, one way to expand the VIN number set would be to alter the check-digit algorithm to create a second, parallel numbering space.

      For example, if model year 2005, use the old algorithm and increment by one position for the new checksum, and recycle the SAE codeset.

      Wash, rinse, and repeat to expand VIN space 30-ishfold.

      Yes, it'd break systems that have the check-digit algorithm hardcoded, but VIN verification systems have to be updated regularly anyway to deal with new SAE codes, the recycling of the year digit, etc.

      Or, we could just have Wal-Mart tell the auto industry to start relying on RFID tags and their numberset to uniquely identify vehicles, and eliminate the problem until we run out of RFID identifiers. :)

    46. Re:Extend the character set? by tomhudson · · Score: 1
      PiercedSoul wrote:
      Why not something simple, like 2004Corvette1, 2004Corvette2, etc? Wouldn't that make sense?
      ... which is why we'll never see it :-)

      Unfortunately, manufacturers cram all sorts of other information into the vin - but its' not done on a consistent basis between manufacturers. The first 3 digits (WMI), the 9th (check digit), 10th (model year), 11th through 17th (sequential number) are standardized - the rest ... well, they're "somewhat standardized". If you've had to write code to determine make, model, year and equipment from the vin, it's REALLY ugly.

    47. 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.)

    48. Re:Extend the character set? by tomhudson · · Score: 1
      DAldredge wrote:
      How does your 'solution' stop the need to reprogram every system that uses VINs?
      It doesn't, but it makes it much less likely to introduce bugs, requires the least amount of modifications to existing tables and code, and is a fix that any coder can understand easily enough to implement. .
    49. 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.

    50. Re:Extend the character set? by Anonymous Coward · · Score: 1, Insightful

      Well, actually the Dingbats are part of Unicode already...

    51. Re:Extend the character set? by tomhudson · · Score: 1
      WushuJim wrote:
      If there are 36 possible characters (A-Z,0-9)
      ... um, there aren't. For model years, the set is [A..H, J..N, P, R..T, V..Y, 0..9]. No I, O, Q, U or Z. see here

      For the rest of the VIN, I, O and Q are not allowed, as they are to easily confused with zero and one.

      The 9th (checksum) digit has further restrictions.

      As you point out, they could add other characters to extend the set. Imagine saying your Ford's serial number is !F$CK*NG$#!POS&23 :-)

    52. Re:Extend the character set? by EvanED · · Score: 1

      Again, every piece of software that uses VINs would have to have at least moderate revision in order to be able to use the extra field. Furthermore, you make the assumption that at least most of the software that uses it is just a series of SQL statements, but I should not at all be surprised if a very substantial number of these applications use home-brewed databases, or other forms of storage.

      In other words, it's not just going in and adding a column to the database and making a couple tweaks to the code; there would need to be substantial revisions. Not overwhelming revisions of course, but enough that it's far more than a trivial task.

    53. Re:Extend the character set? by EvilTwinSkippy · · Score: 1
      It's that whole hard-codedness that makes it hard to just tack on more digits in the first place.

      /whack head with frying pan

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    54. Re:Extend the character set? by LSD-25 · · Score: 1

      I had to deal with the same shit when I worked at a supermarket. However, it wasn't Y2000. Twice, the computer that ran the cash registers had a hardware failure. So the management used the brilliant tactic of handing out markers to the customers so they could write the price on the barcoded items. Then people would naturally forget, so we'd have to run endless price checks.

    55. Re:Extend the character set? by LSD-25 · · Score: 1

      They don't want to use the letters I, O, and Z because they are too easy to confuse with the numerals 1, 0 and 2.

    56. Re:Extend the character set? by John+Starks · · Score: 1

      Haha, brilliant scheme. "Let's see. You've got 10 pounds of filet mignon, 99 cents a pound, 8 lobsters at 50 cents each, and 30 bottles of wine at 79 cents each. Ok, Mr. Johnson, have a nice day."

    57. Re:Extend the character set? by Jorkapp · · Score: 1

      What would the first VINv6 ID be?
      0000:0000:0000:0000:0000:0000:0000:0001 ?

      --
      Frink: Nice try floyd, but you were designed for scrubbing, and scrubbing is what you shall do.
    58. Re:Extend the character set? by PiercedSoul · · Score: 1

      Actually, its easier to just look at the car to determine its characteristics....lol...seriously though, the 2004Corvette1 could be linked to a database of details if it needed to be checked, and the physical VIN tags are not secure at all, making them just about useless.

    59. Re:Extend the character set? by Bush+Pig · · Score: 1

      Just allow the last 6 digits (the serial number) to be hex instead of decimal.

      --
      What a long, strange trip it's been.
    60. Re:Extend the character set? by Bush+Pig · · Score: 1

      The VIN is put on the vehicle at several points including (where I work) being stamped directly into the cowl (part of the body). It's a bit hard to grind-and-restamp sheet steel in an undetectable fashion.

      --
      What a long, strange trip it's been.
    61. Re:Extend the character set? by Anonymous Coward · · Score: 0

      well, actually, the current systems *don't* handle these nonstandard VINs. they simply force the user to exit the system and handle them socially, ie: by calling the salvage rep on the telephone and explaining that you have a wrecked 1960 volkswagen with a 7-digit numeric VIN, not a stolen Bobcat with a 7-digit alphanumeric VIN. takes a lot of poking around and leaves you with non-standard records.

    62. Re:Extend the character set? by GMwrench · · Score: 1

      It's more than that the 4th and 5th are model designators. The 8th is for engine and 11th is for manifacture plant. The article skips the real problem the year A-Zwere used in the 80s and 90s. and 1-0 now ending with the 2010 model year. There were no complaints when it went to 17 digits in 1981. I say bite the bullet and go to a two digit year and add any more for new information and expantion. It would be probably be cheeper in the long run.

    63. Re:Extend the character set? by Anonymous Coward · · Score: 0

      Huh?

    64. Re:Extend the character set? by PiercedSoul · · Score: 1

      Grinding is easy, then there's no VIN, right? My main point is that holding so much info. in the VIN is pointless.

    65. Re:Extend the character set? by Anonymous Coward · · Score: 0

      What's best is that the characters are actually given names. "Yes, that's three heavy teardrop-spoked asterisk outlined greek cross heavy sparkle X lower blade scissors medium flattened left paranthesis ornament twelve dingbat negative cirled sans-serif digit two open-outlined rightwards arrow envelope tapedrive".

    66. Re:Extend the character set? by Anonymous Coward · · Score: 0

      Yup, everything Auto Insurance will have to be overhauled. Not only does VIN = Valid, but it signifies year, make, model...etc. An extension of the current VIN scheme would require a fair amount of coding effort for every company out there that does anything based on VIN #'s. Not just insurance companies, but also body shops, auto makers, and any other company that uses a vehicle's VIN as part of their system's data.

      Not a small effort, but considering how often dates are used in data I'm not sure that this change will even approach the universal scope that Y2K did. I lived thru Y2K as a programmer, and it was rare that a system that's been in use for a decent amount of time wasn't affected. This really only has impacts for those companies who deal with vehicles. Damn near everything somehow needs a date reference, very little needs a VIN reference in comparison.

    67. Re:Extend the character set? by DAldredge · · Score: 1

      The damn article goes over several different methods that can be used to provide more VINs that require NO REPROGRAMMING.

      It's not that hard to read, is it?

    68. Re:Extend the character set? by tomhudson · · Score: 1
      The license bureaus handle the non-standard vins no problem ... ask anyone who deals in used heavy equipment ... these things last decades.

      I once owned a road grader that had a 5-digit VIN.

    69. Re:Extend the character set? by tomhudson · · Score: 2, Informative
      We'll still need to alter all software that validates vins and automatically computes the year from the 10th digit in 17-digit vins by 2009. This can NOT be handled without altering the programs involved.

      Also, the article makes a serious error:

      and each one needs a unique VIN in the same way a newborn is given a Social Security number.
      SSNs are not necessarily unique. There was a series of letters exchanged on this very subject in The C User's Journal a decade ago. This is just something that the general population asumes without questioning it.
    70. Re:Extend the character set? by Dwonis · · Score: 1
      Yes, but you could shorten that to ::1.

      Wait, doesn't that mean localcar?

    71. Re:Extend the character set? by Wolfrider · · Score: 1

      Buggrit! ;-) You'd have to call in some wizards from the Counterweight Continent for that!

      --
      .
      == WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??
    72. Re:Extend the character set? by Bzap · · Score: 1

      That all seems short sighted. It also doesn't seem to take into account new car companys that may popup in the future. The fact is they are just prolonging the real solution, and at some point, they will have to do something.

      And at some point, cars and VINs will be obsolete. 30 years? Our personal teleporters should be ready by then.

    73. Re:Extend the character set? by jbarr · · Score: 1

      There's a huge difference between "re-tooling" and "re-using" tools. What they are talking about is adding functionality to existing tools. They would have to incur a huge cost to either purchase new tools or retrofit existing tools on existing lines (Obviously, new lines would be treated differently, but we're talking about existing lines here.) The real cost savings is the ability to re-use standardized tools from line to line, year to year.

      --
      My mom always said, "Jim, you're 1 in a million." Given the current population, there are 7000 of me. God help us all!
    74. Re:Extend the character set? by jekewa · · Score: 1
      That is true, but in the example set forth in the article, speaking only of the model year, there is neither an O or a 0. I can see confusion between O and Q, too, especially on that grubby tag in the junk yard.

      To further agree, even if you removed I, O, Q, and Z, that's 6^32 instead of 6^10 for just the serial number.

      --
      End the FUD
    75. Re:Extend the character set? by DAldredge · · Score: 1

      It doesn't say that SSN's are unique and never reused. It stats that each child is given a unique SSN, and when the system works correctly, they are. It isn't unheard of for cars to have duplicate VINs.

    76. Re:Extend the character set? by dspyder · · Score: 1

      That was my initial thought too... start using !@#$%^&*()... of course, that has a few major potential flaws: A lot of computer systems might have a validation critera. Also, not everybody's keyboard goes like that ( keyboards I believe also have the ' up there somewhere too)...

      OCR systems that scan various forms might also need to be retrained.

      Nothing insermountable, and certainly nowhere near the scope of the Y2k problem, but an interesting situation none the less...

      When do we start running out of license plate numbers in California??

      --D

    77. Re:Extend the character set? by Anonymous Coward · · Score: 0

      nobody cares about that busted-ass car in your front yard..

    78. Re:Extend the character set? by bar-agent · · Score: 1

      Have you learned nothing from Y2K? Nothing obsolete goes away.

      --
      i'd hit it so hard, if you pulled me out you'd be the king of britain [bash.org]
    79. Re:Extend the character set? by Anonymous Coward · · Score: 0

      How about getting rid of the VIN system all together. It is pointless to have an ID number for every car.

    80. Re:Extend the character set? by Grayswan · · Score: 1

      Why not something simple, like 2004Corvette1, 2004Corvette2, etc? Wouldn't that make sense?

      Better yet, lets go full XML. DTD included of course!

      --
      If you open your mind too wide, people will throw trash in it.
  2. Slashdotters response: by JesseL · · Score: 5, Funny

    Just use NAT.

    --
    "Prefiero morir de pie que vivir siempre arrodillado!"
    1. Re:Slashdotters response: by Anonymous Coward · · Score: 0

      Just use NAT.

      New Automotive Tag?
      Nifty ASCII Ticket?
      National Acronym Target?

      / 'Nother Annoying Techie

    2. Re:Slashdotters response: by jhylkema · · Score: 1, Funny

      Offtopic, but I've got karma to burn, so fuggit.

      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."

      Meals Refusing to Exit?

      Meals Rejected by Ethiopians?

    3. Re:Slashdotters response: by djtack · · Score: 1

      Just use NAT

      Actually, I think the IP equivalent of fixing the allocation problem is CIDR (Classless Inter-Domain Routing).

    4. Re:Slashdotters response: by fred911 · · Score: 1, Funny

      Meals regurgitated by elephants

      --
      09 F9 11 02 9D 74 E3 5B - D8 41 56 C5 63 56 88 C0 45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    5. Re:Slashdotters response: by Anonymous Coward · · Score: 0

      Microsoft Refuses Education
      Microsoft's security Revamp easily Eluded
      Monkeydance Really Emotional
      Microsoft's Reign Ends

    6. Re:Slashdotters response: by Anonymous Coward · · Score: 0

      Not just use NAT, be sure to setup a Beowulf cluster on the NAT LAN too.

      That solves everything!

    7. Re:Slashdotters response: by theonetruekeebler · · Score: 1
      "Meal, Ready to Eat."

      Three lies for the price of one.

      --
      This is not my sandwich.
    8. Re:Slashdotters response: by Dun+Malg · · Score: 1
      Golly, if it's that serious maybe I should start stocking up on MREs...

      Meals Refusing to Exit?

      Meals Rejected by Ethiopians?

      You know, I used to hear those (or variations on those*) back when I and several thousand friends were camping out in the Saudi Arabian desert. I understood the taste complaints (we got stuck with all the ham dishes so our saudi friends could have the not-ham), but the constipation issue drove me up the wall! The guy I worked with every day for weeks used to complain endlessly about MRE constipation, but he'd eat one and drink MAYBE a half canteen of water. I kept telling him, "those MREs are salty; you gotta drink more water". But would he listen? No, he'd eat his 3600 salt-laden calories a day and drink maybe a quart of water total for all three meals. I ate the same damn crap he did (ham slice...the horror...the horror), but I chugged down at LEAST a canteen full of water after every one, and not ONCE did any of my meals "refuse to exit".

      Sorry. Ranting a bit. I got really tired of hearing about Specialist Barlow's constipation so the subject tends to set me off... :)

      * Marines Refuse to Eat 'em, Meals Refused by Everyone, More Repulsive Eats...

      --
      If a job's not worth doing, it's not worth doing right.
    9. Re:Slashdotters response: by John+Harrison · · Score: 1

      As long as we're off topic, did you know that the federally mandated drinking drinking age of 21 was signed into law by Ronald Reagan in the 1980's, rather than during prohibition as you seem to think it was?

  3. Uh-oh by ash*embers · · Score: 1
    "Y2K all over again?"

    There goes our defense system again...

    1. 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.

    2. Re:Uh-oh by ash*embers · · Score: 1
      I must remember to put a smiley or something in posts like that, as it is quite clear that automobile ID tags have everything to do with national security.

      (This is not a troll, I just had to laugh when someone thought I was being serious!)

    3. Re:Uh-oh by Anonymous Coward · · Score: 0

      What a load of bull.

  4. Argh... by Anonymous Coward · · Score: 0, Funny

    Does reading "userfriendly" make anyone else around here want to strangle someone?

    1. Re:Argh... by kfg · · Score: 2, Funny

      Not strangle, no. It irks a bit I suppose, nonetheless words of common phrases often end up linked into a singleword over time.

      Some body starts hyphenating the words, then, eventually, overtime, the hyphen is removed. Email irks too. It starts out as an acronym, then changes into a word. It's a total bastardization of the language, yet, thereitis.

      And thereisntanythingyoucandoaboutit.

      KFG

    2. Re:Argh... by Anonymous Coward · · Score: 0

      I was talking about the comic.

    3. Re:Argh... by kfg · · Score: 1

      I was talking about violins in the streets.

      KFG

  5. If I were them by jkauzlar · · Score: 2, Insightful

    I would start using alphanumeric characters in the serial number field (last 6 digits), giving them 36^6=2,176,782,336 possibilities instead of 10^6=1 million. Actually maybe they already do? If so, then start using the !@#$#$%^%^&*)(*& symbols!

    1. Re:If I were them by th1ckasabr1ck · · Score: 1
      Actually maybe they already do? If so, then start using the !@#$#$%^%^&*)(*& symbols!

      What if they already are using those too?

    2. Re:If I were them by jkauzlar · · Score: 1

      Then they're just screwed

    3. 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.
    4. Re:If I were them by Anonymous Coward · · Score: 0

      Motherfucking symbols aren't the solution to your problem. How about we just convert everything to 128-bit binary and be done with it?

    5. Re:If I were them by Senjutsu · · Score: 1

      Then we're all screwed. Removing the duplicates from the parent's punctuation suggestions and adding in the alphanumeric set gives a 48 character set. 48^6 = 12,230,590,464. If they're already using punctuation, this would mean that there'd be more cars than people by the end of the decade.

      I, for one, welcome our new automotive overlords.

    6. Re:If I were them by Enigma_Man · · Score: 1

      Hehe, I read this as "start using the [swearword] symbols!" But... I suppose it's the same meaning either way.

      -Jesse

      --
      Nothing says "unprofessional job" like wrinkles in your duct tape.
  6. CRY! by Anonymous Coward · · Score: 0

    Any bets they will get massive government subsidies to take care of this "bigger then y2k" problem?

    If anything, coders should be working on fixing that upcoming unix bug... when is it, 2012?

    1. Re:CRY! by Anonymous Coward · · Score: 0

      bigger than!!

      then references time.

    2. 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.
    3. Re:CRY! by Anonymous Coward · · Score: 2, Informative

      Lithuania is already a member of the EU, since May 1 2004.

    4. Re:CRY! by Anonymous Coward · · Score: 1, Informative

      But not to the Euro which is the common currency for the EU.

    5. Re:CRY! by ShavenYak · · Score: 1

      2006-12-31 Sun - HP3000, End Of Life.

      May it rest in peace. Best f'in minicomputer ever.

      --

      Hey kids, there's only 5 days left 'til Yak Shaving Day!
  7. Duh! by Anonymous Coward · · Score: 0

    Detroit never heard of NAT? Routers could ID multiple vehicles using a single public VIN.

  8. 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*

    1. Re:Carmageddon by dr_dank · · Score: 1

      I'm more worried about the assembly robots revolting and attacking the population!

      It's ok as long as you keep old people's medicine out of their reach.

      --
      Where does the school board find them and why do they keep sending them to ME?
    2. Re:Carmageddon by Anonymous Coward · · Score: 0

      Do you have any stairs in your house?

    3. Re:Carmageddon by shigelojoe · · Score: 1

      When they grab you with those metal claws, you can't break free, because they're made of metal and robots are strong.

    4. Re:Carmageddon by NarrMaster · · Score: 0

      Its a friendly robot.... this time. What about next time?

      --
      That's right. All your base.
    5. Re:Carmageddon by Anonymous Coward · · Score: 0

      Grandma must go down the stairs.

  9. This is awful by Anonymous Coward · · Score: 0

    How will my Studebaker collect its hard earned social security?

  10. from the articles picture (the vin number) by Anonymous Coward · · Score: 2, Informative

    The vin is from this vehicle:

    VIN: 3P3ES47Y8XT528059
    Year/Make/Model: 1999 PLYMOUTH NEON HIGHLINE/EXPRESSO
    Body Style: Pillard Hardtop 4 Dr
    Engine Type: 2.0L L4 SMPI DOHC 16V
    Manufactured In: MEXICO

    1. Re:from the articles picture (the vin number) by p51d007 · · Score: 2, Interesting

      Are you running the NICB decoder for that one? I have a copy of that program (since I work for law enforcement), comes in handy for what we do to verify the check digit etc.....dips**t's always try to mess with the VIN, but forget to code it correctly...

    2. Re:from the articles picture (the vin number) by Staos · · Score: 0

      They say you can steal cars using the VIN number.

      --
      In Soviet russia, only old Koreans profit from pictures of Natalie Portman stored on Beowulf Clusters.
    3. Re:from the articles picture (the vin number) by Anonymous Coward · · Score: 1, Insightful

      Y'all love the word 'dipshit' don't ya?

    4. Re:from the articles picture (the vin number) by Anonymous Coward · · Score: 0

      Brilliant! This clearly follows the Slashdot "News for Nerds, Stuff that Matters" philosophy!

      What can we do with this important data? Is this the reporter's car? Mwahahaha! We know what kind of engine he has! Next stop: world domination!

      Or has this person simply proved to us what we already knew--he has way too much time on his hands to prove his '1337ness' by looking up the VIN number, but posting it anonymously!

    5. Re:from the articles picture (the vin number) by Anonymous Coward · · Score: 0

      Actually that is from carfax

    6. Re:from the articles picture (the vin number) by david_reese · · Score: 3, Interesting
      Are you running the NICB decoder for that one?

      No need. Carfax has a free service where the basic details come up before you pay for your report on the VIN. Also, people with a subscription can get details on any number of cars for the sub period. Since I just bought a car for my sister, I have a sub... here's a snippet of what carfax says about this VIN:

      Accident Report
      Date: Source:
      06/29/1999 Michigan Police Report

      Detail:
      Accident Reported
      in Oakland County
      Involving a rear impact
      with another motor vehicle
      Moderate/Severe damage reported
      Airbag deployed
  11. I for welcome our new VIN invaders by stecoop · · Score: 1, Insightful

    The Society of Automotive Engineers, which established the existing VIN system in 1981 and expected it to last 30 years, has formed a committee to address the impending shortage.

    Good thing we survived the 80's so we can always point at mistakes on how not to build things to last. I really hate to see someone that points out that "It'll Last for X years" and it never does. Like IPv4, now we have IPv6 - which I can almost say for certain it will outlast most of us (IIRC it has more digits than atoms in the universe). 640k anyone, the list goes on and on. All of you as engineers have to think a little harder; did we really really save that much money when we used 2 digit dates verses 4 digits. Even into the 90's now the 00's how many use 04 are their checks - what if the Declaration of Independence just had 2-digit year? Its not like were running cat7 in the walls but now maybe there is a list long enough where we can start saying why don't we add a few spare digits for buffering.

    1. Re:I for welcome our new VIN invaders by TwistedSquare · · Score: 1
      1981 and expected it to last 30 years

      I really hate to see someone that points out that "It'll Last for X years" and it never does.

      In this case it did last for X years, if it will be used up by the end of the decade.

    2. 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.

    3. Re:I for welcome our new VIN invaders by Mr.+Bad+Example · · Score: 1

      > did we really really save that much money when we used 2 digit dates verses 4 digits

      Considering that a lot of Y2K-vulnerable applications were written in a time when tiny amounts of storage sold for thousands of dollars, I'd say yes.

    4. Re:I for welcome our new VIN invaders by Anonymous Coward · · Score: 0

      IPv6 addresses have much fewer digits than atoms in the universe. Perhaps you meant more unique addresses? Even so, that's still not the case.

      -- Pedantic Asshole

    5. Re:I for welcome our new VIN invaders by haystor · · Score: 1

      I've nearly always used two digits to express the date and I've never been confused about which century I'm in.

      Although I did show up 100 years late for a meeting once...

      If you really want to be a stickler, I suggest you start counting years from the very first one.

      --
      t
    6. Re:I for welcome our new VIN invaders by arieswind · · Score: 1

      I really hate to see someone that points out that "It'll Last for X years" and it never does.

      If it was made in 1981 and it was given a 30 year lifetime, it should run out in 2011, 1 year after the time they predict they will have run out by, the end of this decade (2010 for the calendarically uninclined)

    7. Re:I for welcome our new VIN invaders by Blackeagle_Falcon · · Score: 1
      The Society of Automotive Engineers, which established the existing VIN system in 1981 and expected it to last 30 years, has formed a committee to address the impending shortage.

      I really hate to see someone that points out that "It'll Last for X years" and it never does.

      The article says unused nubmers will be exhausted by the end of the decade, which is almost right on the 30 year prediction made back in 1981. I'd say the did a pretty good job estimating auto demand.

    8. Re:I for welcome our new VIN invaders by eofpi · · Score: 1

      I'd hardly say the VIN system is coming up short. The CNet article said manufacturers may run out by the end of the decade, which would only be a year short of the original estimate. We never see that kind of accuracy in predictions in the computer world (Moore's law generally accepted), because the automobile industry is a much more mature industry.

      Extending the VIN length makes the most sense to me, since there doesn't seem to be a way around this without having to reprogram all the systems anyways. Some people have suggested expanding the characters available for part or all of it, but the characters in use were selected because they're the easiest to tell apart when the VIN plate is encrusted with layers of rust. That's not something most of us are used to thinking about (who gets rusty computer parts?), but is absolutely vital for cars, as long as they're still made with steel or iron anywhere in them.

      --
      Y'know, you blow up one sun and suddenly everyone expects you to walk on water.
    9. Re:I for welcome our new VIN invaders by taped2thedesk · · Score: 1
      Like IPv4, now we have IPv6 - which I can almost say for certain it will outlast most of us (IIRC it has more digits than atoms in the universe).
      Sure it will, until they decide to assign IPs to quarks.
    10. Re:I for welcome our new VIN invaders by p3d0 · · Score: 1
      I have a better idea:

      #define VIN_LENGTH (17)

      Then, when you run out of digits, change the 17 to an 18 and recompile.

      Seriously. It is not cost-effective in general to t foresee or predict or allow for all conceivable futures. What we can and should do it make our software flexible enough to adapt. You don't need the benefit of foresight to do this. People like David Parnas have shown us how to write modular software for three decades now and we just don't listen.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    11. 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.
    12. Re:I for welcome our new VIN invaders by Keighvin · · Score: 1

      I work as a programming manager for a major online closeout retailer, combining a number of both core and partner items which are tracked via similar in-house-assigned SKU (stock keeping unit). The standard has been a 6 digit SKU for the 5 year life of the company, which has recently caused us some significant troubles - especially as some blocks have been reserved so that some applications could differentiate particular classes of product by that reserved prefix.

      We almost ran out, and in fact were about a week and a half away from exhausting our usable space when we off-loaded a significant portion to a 7 digit space. The idea is to go to 8, but that's all we could guarantee would work with those particular products given the nature of legacy applications; others might not handle it at all. Which bought us some time, but we still have a lot of work to do to get the legacy systems stabalized.

      --
      Any spoon would be too big.
    13. Re:I for welcome our new VIN invaders by the_mad_poster · · Score: 2, Interesting

      Your clear, concise understanding of technology issues is only undermined by the minor fact that you screwed up all of the examples that you gave. 1) The "640k" quip is a misunderstood urban legend. 2) There's nothing wrong with IPv4 which is why there is no rush to switch it out. 3) The fact that pretty much everything kept running on 1/1/00 even though most of it was never touched for an "update" suggests that maybe it wasn't a big deal after all.

      On the subject of IP, the only inherent problem in IPv4 was that nobody expected us to try hooking everything including the kitchen sink - literally - to the Internet.

      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    14. Re:I for welcome our new VIN invaders by molotov303 · · Score: 1

      In all fairness, the article says that the current system will last for the rest of the decade.

      2010 - 1980 = 30 years

    15. Re:I for welcome our new VIN invaders by cdrudge · · Score: 3, Funny
      If you really want to be a stickler, I suggest you start counting years from the very first one.
      I'd like to do this, but I'm not real sure where to start. What year is this just so I know for future reference. And did you start counting when the big bang happened, or when god said let there be light?
    16. Re:I for welcome our new VIN invaders by Trifthen · · Score: 1

      You don't know the half of it. In the VIN code system, only one character from 0-9 and any letter except for I, O, Q, or U, is used for the year. Oddly enough, it cycles (1980 = A, 1990 = L, 2001=1, ..., 2010 = A) so it's already a flawed system. Theoretically, you could have the same VIN for a 1980 vehicle as a 2010 vehicle. Nice design!

      --
      Read: Rabbit Rue - Free serial nove
    17. Re:I for welcome our new VIN invaders by stecoop · · Score: 1

      Who made the decision to only make it last 30 years? Programmers, Vendors, the Government? What is the incentive of an Engineer to build something that will fail in time (other than money). Wouldn't it be easier to make something that can handle change? If I was ask to build this and I was on a committee and read the report that the VIN would only last 30 years, I would have said what cost, financial, productivity impact would it have if we made it last longer for I would have known that cars would last longer than 30 years. Even today, I expect cars to last longer than 30 years.

    18. Re:I for welcome our new VIN invaders by Jeff+DeMaagd · · Score: 1

      On the subject of IP, the only inherent problem in IPv4 was that nobody expected us to try hooking everything including the kitchen sink - literally - to the Internet.

      Doesn't IP have four million digits? Give one to each person alive and you are past exhausted. I suspect that half of them don't care or have far more pressing needs such as clean food, water and shelter. Even the IP problem is something about distribution if MIT has a class A, and HP has two (one for HP, one from Compaq), and I doubt they use a fraction of them.

      But, one thing to remember is that, why should a refrigerator get internet access by a specific IP? I don't want outsiders to be able initiate connections, do I? Even with a firewall, I think that's asking for trouble.

    19. Re:I for welcome our new VIN invaders by platipusrc · · Score: 1

      starting from the beginning of 1981 and going til the end of 2010 is 30 years. They weren't off if that's when they started.

      --
      And the muscular cyborg German dudes dance with sexy French Canadians
    20. Re:I for welcome our new VIN invaders by Planesdragon · · Score: 1

      2) There's nothing wrong with IPv4 which is why there is no rush to switch it out.

      there's plenty wrong with IPv4. The reason we're not switched to IPv6 (which could be done in about a month of concerted effort) is that NAT--an ugly hack to make IPv4 work--is such an effective hack.

      3) The fact that pretty much everything kept running on 1/1/00 even though most of it was never touched for an "update" suggests that maybe it wasn't a big deal after all.

      It was a big deal. And a LOT got touched. 1/1/2000 was such a non-event because I.T. did its job, not because the threat wasn't there.

      On the subject of IP, the only inherent problem in IPv4 was that nobody expected us to try hooking everything including the kitchen sink - literally - to the Internet.

      4,228,250,625

      If we were to limit each person to one address, and require each address to have one owner, we'd still run out of IP addresses shortly after half the planet was online.

      (Actually, quite a bit soooner--the number above doesn't allow for the 16,581,375 reserved addresses.)

    21. Re:I for welcome our new VIN invaders by Cyn · · Score: 1

      actually, 1981 would be the first year - so 2010 would be the 30th year. It will have lasted the predicted 30 years, and run out right at its lifetime. One could easily argue that it technically runs out during some month of 2011, but car manufacturers release a next years models (which would need the VINs) at least half a year early anyway

      --
      cyn, free software and *nix operating systems enthusiast.
    22. Re:I for welcome our new VIN invaders by poot_rootbeer · · Score: 1

      did we really really save that much money when we used 2 digit dates verses 4 digits

      The answer to that is easy to come up with now, when RAM is $0.25/megabyte and hard disk space is $0.80/gigabyte.

      Just 20 years ago (nevermind 30-35 years ago, when the roots of the Y2K problem ACTUALLY began) RAM cost $35,000/MB and hard drives were $170,000/GB -- as if there were any hardware with that much capacity. Go to your project manager in 1980 and tell him that you want to store dates in a way that will still work when his newborn son is in college, but it'll double the memory footprint of the product -- think he'll agree to it?

      We're spoiled by our modern hardware that sits idle 99.9% of the time -- in the olden days, every tiny scrap of performance mattered.

    23. Re:I for welcome our new VIN invaders by YankeeInExile · · Score: 2, Funny

      Excellent idea except for the problem that make universe takes a really long time to compile.

      --
      How does the Slashdot Effect happen given that no slashdotters ever RTFA?
    24. Re:I for welcome our new VIN invaders by jobbegea · · Score: 1

      They used a single character for encoding the year (the 10th character). That is why it will end in 30 years

      --

      Net sa best, mar it koe minder
    25. Re:I for welcome our new VIN invaders by cbreaker · · Score: 1

      It's funny that you mentioned the idle thing, because it's so true.

      I see a lot of admins making a big deal out of a machine that's running at 80% CPU all the time (a busy web server.) I say, GOOD, use the processing power, *that's what it's there for*. Only until you reach 100% does it begin to be a problem.

      Now, I know there's always stipulations, and I'm assuming that said busy web server is caching most of the data into RAM here and/or the disk I/O is not a huge bottleneck.

      --
      - It's not the Macs I hate. It's Digg users. -
    26. Re:I for welcome our new VIN invaders by Incoherent07 · · Score: 2, Insightful

      20/20 hindsight brigade reporting for duty, I see. Besides, making your hardware (read: VIN stamper) modular is a bit harder.

      --
      This is my sig. There are many others like it, but this one is mine.
    27. Re:I for welcome our new VIN invaders by Anonymous Coward · · Score: 0
      Minor correction to your sig:

      Slashdot needs a (+1, Nitpick) option.

    28. Re:I for welcome our new VIN invaders by Rosonowski · · Score: 1

      Except that it's pretty easy to tell the difference between the two on casual inspection.

      --
      01101001 01100001 01101101 01101110 01101111 01110100 01100001 01101100 01100001 01110111 01111001 01100101 01110010
    29. Re:I for welcome our new VIN invaders by VertigoAce · · Score: 1

      It has very little to do with predicting demand. The year of release is encoded as a single digit in the VIN. They gave this digit 30 possible values, so it lasts for 30 years. If they had used two digits, they could have made it last 900 years (using the other 15 digits efficiently would give you more VIN's than the number of cars you could produce in 900 years).

    30. Re:I for welcome our new VIN invaders by Trifthen · · Score: 1

      Tell that to all the automated systems that only see the number. ^_^

      --
      Read: Rabbit Rue - Free serial nove
    31. Re:I for welcome our new VIN invaders by Rosonowski · · Score: 1

      True, but for most of the applications involving humans, it won't be too bad. I understand the problem, though.

      --
      01101001 01100001 01101101 01101110 01101111 01110100 01100001 01101100 01100001 01110111 01111001 01100101 01110010
    32. Re:I for welcome our new VIN invaders by Anonymous Coward · · Score: 0
      Your program seems to be missing a bit of code. In fact, I've compiled the given macro, and the updated version, and observed no change whatsoever in the systems of the world that actually use VINs, rather than just mentioning them in a macro that's never referenced.

      Perhaps once you've rewritten all of that software and hardware, as a single source tree using this as a header (and of course extended gcc to recompile hardware from this source), you can market your solution to the car companies.

      Oh, and of course you'll need a utility that detects the change during its own recompilation, and updates all the records engraved on existing cars in the database*.

      *world

      ...or hey, maybe pretending VINs have always been 18 characters, as a recompile would do, isn't the best solution? But I'm sure you know what you're doing.

    33. Re:I for welcome our new VIN invaders by Anonymous Coward · · Score: 0

      I hear make world has been working fine so far.

    34. Re:I for welcome our new VIN invaders by aardvarkjoe · · Score: 2, Insightful
      Doesn't IP have four million digits?

      Not to nitpick or anything -- but no. IPv4 allows for 4 billion (and change) possible addresses: 2^32, minus a bit for addresses which aren't usable for various reasons. "Digit" is not a synonym for a possible address.


      OK, yeah, that was nitpicking, but since I've seen at least two people make the same mistake in this thread, I wanted to point it out :)

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    35. Re:I for welcome our new VIN invaders by stecoop · · Score: 1

      Alright so lets calculate the cost of storing 2 bytes vs. 4 bytes using your 1 gigabyte in 1980 dollars.

      For 10^9 of storage containing 16 byte fixed length entries will store 62,500,000 records. At a cost of 0.00017 for 2 byte length dates would total $10,625. At 0.00034 dollars per 4 byte length entries would cost $21,250. Double yes but only 6.25% savings over the 170k. A not too bad return actually after calculating it. But the big question is the total cost. Like why did ls return 19100 date in the year 2000? I sort of agree that cost were huge back in the 50's and into the 80's but when the 90's rolled around, simple functions shouldn't have self imposed legacy restraints.

    36. Re:I for welcome our new VIN invaders by qwertyphobia · · Score: 1
      I have a better idea:

      #define VIN_LENGTH (17)

      Then, when you run out of digits, change the 17 to an 18 and recompile.

      Except, if you look at how a VIN code is made up, it isn't simply a 17 digit number. It's a 17 character code with specific fields within it and some of these fields are reaching capacity. To extend the VIN requires redefining the fields and changing all the software that parses those fields.

      As has already been mentioned, the 30 year lifetime prediction is accurate because the code has a single character to identify the year and there's 30 possible values for it. Nothing to do with unusually astute sales analysts.

    37. Re:I for welcome our new VIN invaders by stecoop · · Score: 1

      http://en.wikipedia.org/wiki/Ipv6

      IPv6 is version 6 of the Internet Protocol. IPv6 is intended to replace the previous standard, IPv4, which only supports up to about 4 billion (4 × 109) addresses, whereas IPv6 supports up to about 3.4 × 1038 addresses. This is the equivalent of 4.3 × 1020 (430,000,000,000,000,000,000 which is more than the number of seconds that have past since the big bang) unique addresses per square inch of the Earth's surface.

      IPv6 is the second version of the Internet Protocol to be widely deployed, and is expected (as of 2001) to form the basis for future expansion of the Internet. In 2003, Nihon Keizai Shimbun (as cited in CNET Asia Staff, 2003) reported that Japan, China, and South Korea claimed to have made themselves determined to become the leading nations in internet technology, which would partially take the form of jointly developing IPv6, and completely adopting IPv6 starting in 2005.

    38. Re:I for welcome our new VIN invaders by Anonymous Coward · · Score: 0

      Probably believed the hype that we'd be out of fuel by now and it wouldn't matter any more...

    39. Re:I for welcome our new VIN invaders by p3d0 · · Score: 1
      Yes, yes, so it would be more than a 1-liner. I was being facetious. What I'm talking about is information hiding in general. There's no reason that knowledge of the format of a VIN number should be smeared throughout your code. If you can't replace the VIN number logic in your software with a reasonable amount of effort, or if you think the kind of design I'm talking about requires superhuman foresight, then you have no business calling yourself a software engineer.

      The principle of information hiding has been known since long before VIN numbers were invented.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    40. Re:I for welcome our new VIN invaders by p3d0 · · Score: 1
      20/20 hindsight brigade reporting for duty, I see.
      Really? If you think writing software to allow for changes in the VIN format requires superhuman foresight, I hope you're not in the business of writing software.

      Besides, making your hardware (read: VIN stamper) modular is a bit harder.
      I don't understand this assertion. Do you think I'm proposing that the VIN stamper should be constructed to allow for any possible number of digits without modification? If so, you missed my point.
      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    41. Re:I for welcome our new VIN invaders by Anonymous Coward · · Score: 0

      but consider this.

      perhaps they began developing this system in 1980, at which time it would have really lasted thirty years. it may not have been accepted or become "the established norm" for a few months; perhaps enough to make it next year.

      if an engineer says "if we did it this way would last us thirty years," consider the legalese: lasting 30 years is what it would do if it was how they were doing it right then.

      it does not imply that it would last for thirty years from its actual implementation date. project leaders and managers often miss this subtle distinction, and could well have reworded what they were told, or anybody else could have done that, being confident that they were 100% correct.

  12. Switch to IPV6 by Anonymous Coward · · Score: 0

    Time for the automotive industry to recognize the limitions of VIN, ditch it, and switch to IPV6.

    Seriously, I wonder why they can't switch to some type of barcode system, so the cops don't have to key in a really huge long number.

    1. Re:Switch to IPV6 by greechneb · · Score: 1

      A lot of cars do have a bar code next to the vin, although it probably is just for the manufacturer/dealer supply chain

  13. Good by Anonymous Coward · · Score: 2, Interesting

    Why does the government feel that it needs to know the "ID" of my vehicle? What business is it of theirs? This is no different than other government-mandated identity programs such as Social Security numbers. Not to get tin-foil-hatty, 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.

    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?

    1. Re:Good by TopShelf · · Score: 2, Funny

      Right on, man! Next thing you know they'll want to put unique ID's on all network interface devices.

      Fight the power!

      --
      Stop by my site where I write about ERP systems & more
    2. Re:Good by _14k4 · · Score: 1

      Because when I run grandma over and sell my car for parts.. they can put it back together again; finding the dented quarter panel.

      Or, they can find my car after it's been stolen and scrapped on the street for parts.

    3. Re:Good by Crazy+Man+on+Fire · · Score: 3, Insightful

      Why? Cars have to be registered and insured. Typically, things that are registered (cars, guns, people, etc) have to be uniquely identifiable. Without a VIN or some similar system of identification, such registration would not be possible.

    4. Re:Good by The_Real_Nire · · Score: 2, Insightful

      Lets see, for warranty verification, theft protection, automobile history tracking (for accidents), recall tracking (so your car doesnt explode, hopefully).

      How many more reasons do you need?

      I think it ges without saying that most, if not all Pentiums did not have these sorts of problems.

    5. Re:Good by JesseL · · Score: 1

      First, because we can all see the need for unique serial numbers for vehicles. Second, because there is no way for just anybody to query the VIN from your vehicle and use it to track your doings.

      --
      "Prefiero morir de pie que vivir siempre arrodillado!"
    6. Re:Good by _14k4 · · Score: 1

      ...well, except for exploding. MMX anybody? :)

    7. Re:Good by Anonymous Coward · · Score: 0

      Because if there is an automovitve recall and you wish to participate that vin is important for getting the free repair.

      If you choose not to participate that number is important if you get an accident so insurance and the auto manufacturer can duke it out.

      If you are the first to get in an accident that is the fault of the auto maker that vin will tell you when and where it was made so similar cars can avoid your fate.

      If your car gets stolen it is a unique identifier for the police to track.

      That's just what I can think of off the top of my head. I swear to god one day I am going to read on slashdot "I don't think doctors should have access to my medical records, why should they be able to invade my privacy like that?"

      I mean, jebus, get a friggin grip.

    8. Re:Good by slartibart · · Score: 1
      How else do you tell otherwise identical cars apart?

      It's just like a serial number on any other type of product.

      As far as the government knowing the VIN, how else can the government register cars? If there's a dispute over whose car it is, how else can you identify the car? License plates are too easily switched.

      I'm all for small government too, but there are too many government constructs that are useless and invade privacy to worry about this one - that has a use and doesn't really invade privacy.

      With the CPU ID, we were more worried about losing our anonymity online, which we should have every right to. You don't have the right to be anonymous on public roads. If you want to drive your car on your own roads, you don't need to register it, IIRC. Then no one will know your VIN.

    9. Re:Good by kidgenius · · Score: 1

      Well, when your car gets in a wreck, stolen, or parted out, and you want it back, have fun trying to do it w/o a VIN number. In this case, it FOR YOUR GOOD as well.

    10. Re:Good by Anonymous Coward · · Score: 0

      that *was* the excuse. Now they need VINs so that they can put them in your tires and read them as you roll by guardrails.

      God forbid a terrorist is speeding away in a burning bus that he just blew up with the bomb strapped to his chest!

    11. Re:Good by Aaul · · Score: 1

      The VIN system is useful for checking the history of a used car you might be buying. To verify that you're not buying a car that was used in some criminal act, for example. It's also pretty important for law enforcement in finding and returning stolen vehicles. Without a VIN, you'd have to pretty much describe every last detail of your car so the police can make sure the car they just found is really yours.

    12. Re:Good by Punboy · · Score: 1

      You're right! Now lets stop shipping people with unique ID's, its not the government's business who i am!

      --
      If you like what I've said here, and want to read more, go to http://www.krillrblog.com
    13. 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.

    14. Re:Good by J'raxis · · Score: 2, Informative
      MAC addresses--
      • Aren't necessarily unique, as some NICs are programmable;
      • Aren't government-mandated;
      • Aren't illegal to change;
      • Aren't illegal to hide or otherwise obfuscate.
      Your comparison really fell on its face. Care to try again?
    15. Re:Good by Pieroxy · · Score: 1

      You are funny.

    16. Re:Good by ceswiedler · · Score: 1

      I'd like to see you run a LAN where MAC addresses aren't unique.

      Likewise, try to license vehicle ownership in any way without a unique number to identify the vehicle. If you think vehicle licensing ISN'T necessary, well then, your car is mine, buddy--prove that it ain't.

    17. Re:Good by wfberg · · Score: 1

      Why? Cars have to be registered and insured. Typically, things that are registered (cars, guns, people, etc) have to be uniquely identifiable. Without a VIN or some similar system of identification, such registration would not be possible.

      Typically, insured things need to get damaged before you can claim insurance.

      "Yeah, sure, that was the Ford with VIN 123456789 that I was paying insurance on, unlike my other 2 identical cars which have different VINs - but the VIN appears to have been destroyed in the accident".

      --
      SCO employee? Check out the bounty
    18. Re:Good by geirhe · · Score: 1

      Why does the government feel that it needs to know the "ID" of my vehicle?

      Someone pinches your license plates. You need a new set. How do you know that the *stard who stole your license plates doesn't put them on his own car, which incidentally looks like yours. You would end up with all his tickets. VINs make it possible to actually find out if this has happened for the police - is this the car which should have these license plates?

      If someone pinches your car and sends it somewhere else, it will be possible for you to reclaim your car if someone ever catches the guys who did it. Without VINs, a car without a license plate is up for grabs.

      The company which makes your car also has issues that makes it necessary to identify individual cars. Say that one engine assembly line is faulty, and this problem surfaces two years down the line when engines start keeling over. Would you rather have a spectacular engine failure, or a letter from your friendly automaker telling you they need to provide you with a new engine? Please feel free to abstract this to brake systems failures, if you want.

      This is why you want VINs.

    19. Re:Good by dankow · · Score: 1

      ...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...

      Sometimes I wonder if some Slashdot readers take 1984 a little too seriously. This confirms my suspicion. Fiction, dude, fiction. Take a deep breath.

      --
      I am the hub of Jack's digital lifestyle.
    20. Re:Good by Feanturi · · Score: 1

      Why does the government feel that it needs to know the "ID" of my vehicle?

      Because people steal cars. A lot. Remember that the government is made of people, and is *for* people. Some of the things they try to protect us from are just stupid, and other things, like vehicle registries, help us out. I don't see a VIN as a privacy issue at all. A unique ID in my CPU on the other hand, that's entirely different.

    21. Re:Good by SydShamino · · Score: 1

      >>>>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.

      Now, if the government mandated that VINs be implanted in RFID chips, and then the government started installing readers on roadsides to record where I traveled, -then- I would be worried.

      Databases that require a human to connect point A to point B (i.e. that car with me) don't bother me that much, because most humans have better things to do and the data isn't necessarily stored for all of time.

      --
      It doesn't hurt to be nice.
    22. Re:Good by elegie · · Score: 1

      The issue of VINs running short was bound to happen eventually, assuming that a number is not reused when the corresponding vehicle is destroyed or scrapped. Using numbers that were intended for other countries (they would have to be officially reassigned) could be easier than extending the number of digits if those other countries did not produce any vehicles. Of course, the fact that a country does not produce vehicles could change quicker than expected...

      The following is somewhat off-topic...

      Speaking of SSNs, those will eventually run out (currently SSNs of deceased individuals are not reused and not all combinations are valid.) Unlike VINs, the SSN was originally only intended for the Social Security program. The SSN was later used for more and more things, and the more rapid consumption of the available numbers is not the only problem that resulted. An SSN in the wrong hands can potentially lead to very significant problems (i.e. identity fraud) as compared to knowledge of a VIN. Knowing a VIN could result in being able to track down the owner of a vehicle.

      It sometimes is possible to "rebel against" SSNs. When a private party asks for an SSN, it is useful to ask why if it is for purposes not related to income taxes. An SSN should not be used as a password! Many educational institutions will now assign an alternate ID number (instead of using an SSN as an ID number); the procedure for obtaining such a number may not always be clearly documented or mentioned in the usual places.

    23. Re:Good by glitch23 · · Score: 1

      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)

      Just for clarification, not all states in the US have inspections (Ohio being one of them). It's usually easy to spot the states that don't once you see some cars from that state, and the people who drive them.

      --
      this nation, under God, shall have a new birth of freedom. -- Lincoln, Gettysburg Address
    24. Re:Good by tanguyr · · Score: 1

      Hi - i came here via metamod (of the parent poster) and i think everybody here is being a bit harsh: his question wasn't "why does my car need an ID number" but "why does the government feel that it needs to know the ID of my vehicle" - and i think he has a point. Sure, i can accept that the manufacturer needs a way to track its cars, and the insurance company needs to know these things as well. If and when the police need to know - you tell them. After all, if your laptop gets stolen you don't expect them to look up the serial number in the national coputer equipment database, do you?

      So... yeah, why does the government need to know the VIN?

      --
      #!/usr/bin/english
    25. Re:Good by Anonymous Coward · · Score: 0

      sorry, meant grandparent

  14. 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 i.r.id10t · · Score: 1

      What kind of car is it? My '65 Porsche 356 has a 6 digit number...

      --
      Don't blame me, I voted for Kodos
    2. 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.

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

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

    4. 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:Probably some truth to that. by tgd · · Score: 1

      Gray market european 1968 911L

    6. Re:Probably some truth to that. by jon787 · · Score: 3, Funny
      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.

      So multiplying by 0.62 didn't occur to them?
      --
      X(7): A program for managing terminal windows. See also screen(1).
    7. Re:Probably some truth to that. by shawn99452 · · Score: 2, Interesting

      Yes, my car also (1964 Dodge) has a VIN of less than 10 digits, all numbers. And it's on the inside door jam, since it was made 2 years before they were required to be visible outside the car. I had trouble getting it insured, and eventually the lady just put X's for the remaining digits, and the computer was okay with that. I would think though, that just adding another field, like VIN2 or something, would be an easy cheap fix. Or fixing VIN altogether, by using the first character or 2 as a length designator, so we don't have to worry about this nonsense again.

    8. Re:Probably some truth to that. by deacon · · Score: 2, Interesting
      Could you please share with us what "training" you did at the RMV

      (a chair? horsewhip? cattle-prod? Brain-implant?)

      to get them to input the number correctly?

      I went thru that once a looong time ago, with a 6 digit vin on a motorcycle, and I was never able to get those @$$#0!&$ to budge off their asses. Finally had the local police department make up a vin#, with the 6 digets in the middle of it, and they took that.

      Can you tell my blood pressure still Chernobyls at the memory of that whole farce?

    9. Re:Probably some truth to that. by fred911 · · Score: 1

      That's why the title has miles at TMU. Any vehicle without an odo that displays miles is marked True Mileage Unknown, unless the odo is replaced by a certified station and and proper docs are provided for the conversion.

      ps.. we call 911's not made for US delivery ROW (rest of world).

      --
      09 F9 11 02 9D 74 E3 5B - D8 41 56 C5 63 56 88 C0 45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    10. Re:Probably some truth to that. by tgd · · Score: 1

      I'm quite aware that people refer to the non US cars ROW, but a) Slashdot isn't all people in the US, b) not everyone here knows that and c) most 911 enthusiasts don't realize there was ROW 911L's, because most historical documentation says the L was created and sold in the US because of the inability of the S that year to meet emissions standards.

    11. Re:Probably some truth to that. by ultramk · · Score: 1

      Obviously it's not a ford.

      Actually, it is... Ford Prefect, to be exact.

      (how far it is to Betelgeuse, anyway?)

      m-

      --
      You catch enchiladas by picking them up behind the head and holding them underwater until they don't kick anymore -VeGas
    12. Re:Probably some truth to that. by Lanoitarus · · Score: 0

      > Shit, drive a couple more blocks and its brand new again! ...I wonder if the new car smell comes back?

    13. Re:Probably some truth to that. by theonetruekeebler · · Score: 1
      I'm not surprised by either. The VIN system was not adopted until 1981; before then, vehicle manufacturers used whatever internal serialization scheme they cared for. In Colorado, we were expected to left-fill the number with either X or 0, I forget which.

      As for odometers, most states write "0" in the "odometer" field of the title for vehicles over N years old (where N in (10 15 20)). The asumption is that odometers are used to determine wear-and-tear on a vehicle; after N years, simple deterioration becomes a sufficiently important factor. I know a BMW motorcycle rider whose bike had just under 300,000 documented miles on it. When he retitled it, the odometer statement read "0". He was pissed.

      --
      This is not my sandwich.
    14. Re:Probably some truth to that. by Random832 · · Score: 1

      The Massachusetts RMV had no idea what to do with an odometer in kilometers

      if they ask just say "Some weird european thing... five eighths of a mile"

      4.971 eighths, to be more precise, but it's probably easier for them to work with whole numbers, and it's not fraud (though IANAL) since the error falls against you rather than in your favor.

      --
      We've secretly replaced Slashdot with new Folgers Crystals - let's see if it notices.
  15. Alternate Slashdotter's response: by Grayden · · Score: 4, Funny

    Perhaps this will speed the transition to VINv6...

    1. Re:Alternate Slashdotter's response: by Anonymous Coward · · Score: 0

      There's no place like 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0...

    2. Re:Alternate Slashdotter's response: by k12linux · · Score: 1

      Don't you mean there's no place like 0010111101101000011011110110110101100101 ?

    3. Re:Alternate Slashdotter's response: by combcox · · Score: 1

      Anyone thought of a project to proxy VIN.

  16. Y2K by dr_dank · · Score: 1

    By that logic, the next car that rolls off the assembly line when the numbers are exhausted will be a Baker Electric.

    --
    Where does the school board find them and why do they keep sending them to ME?
  17. 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
    2. Re:Use More of the alphabet by Ralph+Wiggam · · Score: 2, Insightful

      That's the first thing I thought of, too.

      How inefficient do you have to be to blow through a 17 character (which is not the same as a digit, Mr. Author) alphanumeric code in 30 years? They did have the good sense to throw out I,O,Q,U,and Z, something I wish other alphanumeric codes would do, and used a check digit. If used to it's full efficiency, the VIN system could identify 121 trillion vehicles for every human being on the planet.

      The article is stupid. It talks about this is a big problem, compares it to Y2K, and then mentions that Armenia and Zimbabwe were assigned huge blocks that are going unused. As long as everyone is told that the system is changing and my garage doesn't try to order parts from Zimbabwe, we'll be fine.

      -B

    3. Re:Use More of the alphabet by Danse · · Score: 1

      Why, oh why can't they have designed something more scalable to begin with?

      From my experience in software design, it's because nobody wants to put in any effort in planning for the future. They want something that is good enough right now. By the time the bad design decisions become apparent to the average person, it's somebody else's problem.

      --
      It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
    4. Re:Use More of the alphabet by Azi+Dahaka · · Score: 2, Informative

      They do this already. They mostly stick to their primary character, but sometimes are assigned a different one.

      Ford has F, N, and Z.
      Chrysler has C.
      Honda has H, 7, and S.
      Toyota has T, and N. (Shared with Ford.)
      Volkswagen has V and B.

    5. Re:Use More of the alphabet by Bob+Uhl · · Score: 1

      I understand I (looks like the numeral one) and O (looks like the numeral zero), and can even see Z (could look like a 2 if handwritten), but why eliminate Q and U?

    6. Re:Use More of the alphabet by Ralph+Wiggam · · Score: 1

      On a dirty metal VIN tag, O, Q, and U can look identical.

      -B

  18. 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 SolidiusRock · · Score: 1

      Bah.. you beat me to it.

      To back this point, as well as the point about two vins, the problem isn't that complex. By recycling vins from cars removed from general circulation, you can open up many new ones that otherwise wouldn't have, as well as implementing a supplemental vin for the newer cars should extend the identification even longer, maybe three just to circumvent it in the future.. :D

    2. 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...

    3. Re:VIN numbers as SSNs? by sunspot42 · · Score: 1

      Is the SSN just a serial number, though? I thought the first 3 digits indicated which state the SSN was issued in. Or has that been changed?

    4. Re:VIN numbers as SSNs? by Anonymous Coward · · Score: 0

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

      This idea would work fine as long as there was a scrap vechicle registry, which I thinh there should be anyway. Common knowlege says There is a brisk trade in buying smashed vechicles and then using the VIN on a stolen car. There are now more cross checks with other bodyparts and of course the engine serial #, electronic components and controllers with locic and memory circuits, but it still occurs.

    5. Re:VIN numbers as SSNs? by Anonymous Coward · · Score: 1, Funny

      recycle it's VIN number

      recycle it is vehicle identification number number?

    6. Re:VIN numbers as SSNs? by josea · · Score: 0

      Not as easy as it sounds. The fourth through eight digits in the VIN are specific to the body style and other options (so a Crew Cab truck has different digits than a Super Cab). So if your old 77 Chevy Nova dies, the number may not be reusable on any current model. Also, if your car dies after only a couple of years and is then used on a vehicle it could cause havoc with DMVs, Insurance, and law enforcement. Finally, remember that the VIN is not only written onto the little badge on your dash or the car door, it is also on the engine, transmission, the frame of pickup trucks, etc. So your vehicle may die, but it's VIN could live on in a junkyard.

      --
      I blog, they blog, do you
    7. Re:VIN numbers as SSNs? by The+Meshback · · Score: 1

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

      A good idea, but how do they decide when a car officially 'dies'? A few years ago I bought a 1966 VW Bug that had been sitting in a barn for 15+ years. I rebuilt/restored the entire car and still used the original engine. Granted, I only hit 70mph when I was on the highway, going downhill. But the engine ran fine with a little work and a tune-up.

      How would they determine when a car was officially dead? My VW was probably ready for the junkyard, except that the body only had minimal fender damage and I paid $500 for it because the family just wanted it off their property. There are always hobbyists who see that POS as a revamped conversation piece. How do you propose we get around the restoration of an old beater?

    8. Re:VIN numbers as SSNs? by Anonymous Coward · · Score: 0

      Car thieves already do this, just go to another state and find a similar car and then write down the vin and sell your list to some sucker.

    9. Re:VIN numbers as SSNs? by Anonymous Coward · · Score: 0

      the vehicle is assigned a salvage title, and in some cases can be determined "not repairable", as in "not safely repairable", which is different from the insurance standard of "not economically repairable"

  19. Two by fmarano · · Score: 1

    Just give every new car two VIN numbers - Problem solved

    1. Re:Two by Anonymous Coward · · Score: 0

      Yes, using VIN numbers twice as fast will really help.

  20. Uh... by Anonymous Coward · · Score: 0

    And a VIN shortage is "News for Nerds," how?

    1. Re:Uh... by jrl87 · · Score: 1

      it isn't, but how much stuff on here really is?

      This was just posted by some sneaky guy in the automotive IDing business so we will do his work for him ... no matter how inefficient and redundant the final product turns out to be ....

  21. all too common issue by XMichael · · Score: 2, Interesting

    This is a fairly common issue in other industries as well... In the food packaging industry they use what is called a DSS number; in addition to the generic serial number we've all known to grown and hate. This DSS number is sort of an industry number which allows the manufactures to more accurately tracking where the product what packed / shipped to, etc. The system is at it's witts ends, as these DSS numbers are appended depending on the number of destinations... Turns out when they designed the system food was only being shipped to many 3 or 4 places at the most --- now it's common for food to be shipped to upwards of a dozen places BEFORE it is even shipped to the grocery store.

    all in all, same story, boo hoo, it'll cost them a bunch of money to upgrade

    CCTV Systems

  22. 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?

    1. Re:I'm not sure... by CableModemSniper · · Score: 1

      Um, since they designed the current VIN system in '81 according to the article, your '60s Chevy probably didn't have a VIN in the sense they are speaking of.

      --
      Why not fork?
    2. Re:I'm not sure... by f.money · · Score: 1

      Um, since they designed the current VIN system in '81 according to the article, your '60s Chevy probably didn't have a VIN in the sense they are speaking of.
      Oh cool, so there's not even a problem. All those devices already have a way to enter a non-standard (not 17 char) VIN into them for all the older cars on the road. This sounds like a lot of talk about nothing . . .

    3. Re:I'm not sure... by drinkypoo · · Score: 1

      ISO 3779 (VINs) came about in 1977 and was last revised in 1983. The VIN had the same major purpose, which is to say identifying a vehicle, but it was basically a serial number. I don't know how they were handed out. However, they are NOT the serial number, at least not for all manufacturers, because many vehicles (like my dad's '63 chevy) have both a short VIN and a serial number.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  23. 2005 must = ... 5 by Grrr · · Score: 1

    The "how to read a VIN" sidebar from USAToday has an error in it. I feel all fuzzy inside now.

    <grrr>

  24. 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.

    1. Re:Umm.... that will be $250,000 in modifications by Kutsal · · Score: 1

      If only things were that simple..

      What about the <input name="vin" size="17"> fields in your html pages, or if (vin.length() != 17) lines in your Java/JSP codes?...

      Yay for consultants..

      --
      Karma: Bad (but who really cares anyway?)
    2. Re:Umm.... that will be $250,000 in modifications by irokitt · · Score: 1

      Yeah, but you actually have to do it in COBOL, which makes it harder;)

      --
      If my answers frighten you, stop asking scary questions.
    3. Re:Umm.... that will be $250,000 in modifications by jfengel · · Score: 3, Insightful

      You have to run it on every database. And you have to deal with every program that operates on it and allocates exactly 17 characters for the space. That means scanning the source code, which is wildly expensive (assuming you even still have the source code).

      Every program which parses the VIN will be confused by a change in the format. Again, more code scanning.

      When any two databases pass VINs to one another, they both have to use the same standard.

      Once the code is fixed, you have to install it on every computer. You have to synchronize the database update and the code install, and every set of databases that hook up with each other. You can make things compatible enough to be prepared to communicate with non-upgraded databases, but that means more code, and more testing.

      You have to test the bejeezus out of it, too, because some of these systems can't afford to crash.

      So the change is going to be a lot more expensive than one SQL query.

    4. Re:Umm.... that will be $250,000 in modifications by p3d0 · · Score: 1

      It has more to do with the user-interface software that inputs and verifies these numbers, rather than the databases that store them. The trouble is that the modification should be as simple as you say, but brain-damaged software "engineers" have made it harder than it should be.

      --
      Patrick Doyle
      I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
    5. Re:Umm.... that will be $250,000 in modifications by cdrudge · · Score: 1

      Or all those lines written in some since extinct programming language because your state's [DB]MV hasn't upgraded their computer systems since 1981 when the system was put into place.

    6. Re:Umm.... that will be $250,000 in modifications by Anonymous Coward · · Score: 0

      I don't think most slashdotters will understand why this is a big deal. I assume the average slashdotter either can't afford a car or is too young to drive.

      "VIN? What's a VIN?"

    7. Re:Umm.... that will be $250,000 in modifications by 3ryon · · Score: 1

      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);


      But don't you understand? Haven't you been paying attention? Actually reading the data will crash the database.

    8. Re:Umm.... that will be $250,000 in modifications by poot_rootbeer · · Score: 1

      alter table VEHICLES modify column VIN varchar(50);

      Oops! The database crashed and we have to rebuild the tables from the original create scripts and restore data from back up.

      Hey... how come every INSERT statement for data originating after a certain date is causing an error now?

      The data layer supporting larger VIN strings doesn't do any good if the validation routines in the business layer and the form fields in the presentation layer aren't reviewed and possibly rewritten, anyway.

    9. Re:Umm.... that will be $250,000 in modifications by Anonymous Coward · · Score: 0

      Thanks.. you just saved a bunch of work...

      (although our table is named vehicle and the vin is already 30 chars long)

    10. Re:Umm.... that will be $250,000 in modifications by KevinKnSC · · Score: 1

      And that's just the software side of it. You also have to replace/upgrade the machine that stamps the VIN at the factory, you have to upgrade the proprietary VIN barcode scanner at the mechanic, etc.

    11. Re:Umm.... that will be $250,000 in modifications by Anonymous Coward · · Score: 0

      "The data layer supporting larger VIN strings doesn't do any good if the validation routines in the business layer ... aren't reviewed and possibly rewritten, anyway."

      I'd make a point about the folly moving business rules/constraints from the DBMS to the application but I think you just made it for me.

    12. Re:Umm.... that will be $250,000 in modifications by Fweeky · · Score: 1

      Then you're fired for making a serious application full of magic numbers. DRY.

    13. Re:Umm.... that will be $250,000 in modifications by leviramsey · · Score: 1
      [DB]MV

      Make that [DBR]MV

    14. Re:Umm.... that will be $250,000 in modifications by geirhe · · Score: 1

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

      Brilliant.

      On one side, we have the pessimists blowing this issue out of proportion.

      On the other side, we have people who don't know the first thing about the practicalities of actually changing a system that is deployed on hundreds of boxen telling us that it is really a one-liner, no really!

      Or are you possibly a troll, sir?

    15. Re:Umm.... that will be $250,000 in modifications by khallow · · Score: 1

      It's not a problem here. He's not reading the data, he's altering it. That's quite safe.

    16. Re:Umm.... that will be $250,000 in modifications by mikelieman · · Score: 1

      Not so clear... We've got a legacy application and adding a char or two to the VIN field means dumping the table to a text file, making the change to the table structure, and then reloading it.

      Oh, 20 locations in NY * 250,000 records... NOT something I want to do...

      --
      Technology -- No Place For Wimps! Grateful Dead and Jerry Garcia Chatroom -- http://www.wemissjerry.org
    17. Re:Umm.... that will be $250,000 in modifications by cr@ckwhore · · Score: 1

      Yep, that's exactly it! I know this first hand because I wrote software for motor vehicle registration which is used by several municipalities within the state of Maine. Due to state regulations, the software relies on the VIN as a UNIQUE value to represent each vehicle record. So, when VINs are no longer unique, the software will need to be fixed. If VINs are extended, the software will need to be fixed. Either way, something as seemingly simpls as a VIN number could make an impact on the economy.

      --
      Skiers and Riders -- http://www.snowjournal.com
    18. Re:Umm.... that will be $250,000 in modifications by jbolden · · Score: 1

      You have never worked with legacy systems.

      1) The data isn't being stored relationally but in ISAM formats

      2) The datastructures are column 1 and possibly null padded

      3) The code uses all kinds of interesting approaches based on the exact format of the VIN. For example if digits 3-8 by position mean XYZ to do calculations ABC, you might have code like
      Let X = VIN mod 100000

      IF X > A and X B and X = C ...
      where A,B,C are modifications to the 3-8 digits...

      Oh yeah and this ain't in ASCII either. I'm happy this could be tons of wonderful consulting work.

    19. Re:Umm.... that will be $250,000 in modifications by sploxx · · Score: 1

      Yes...
      And it's even doubtful

      - if the database uses SQL as it's query language
      - is relational
      - can handle the load without crashing

    20. Re:Umm.... that will be $250,000 in modifications by lachlan76 · · Score: 1

      Well ideally somewhere in your code (C/C++) you'd have
      #define VIM_LENGTH 17
      Don't know about Java though, I haven't used that in years, and can't remember if it'd all work that way.

    21. Re:Umm.... that will be $250,000 in modifications by leerpm · · Score: 1

      I know you are joking, but I would like to to point out the VIN is probably a primary key in many databases. And you don't just go changing the length of your primary key that easily, because all the other tables that reference it, have to update their foreign key columns. Then all your indexes have to be updated, plus any db tier procedural code that declares the length of the field.

      And that's just the database. Then you have to go and modify all the application layer code to handle the longer field length. I pity those developers who hardcoded the VIN field as char[17]. Then you have to update your UI code to make sure the screen output and fields can handle input that long.

      That's just the software side. Then you have to worry about all that hardware used for printing/stamping out the VINs.

  25. 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
    1. Re:Let me clarify... by drinkypoo · · Score: 1

      Other countries do have their own unique portions of the VIN but they still follow the standard to some degree, and they ALL use the unique manufacturer identifier.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Let me clarify... by Gorffy · · Score: 1

      Yes, Canada uses the VIN system as the main ID too.

    3. Re:Let me clarify... by sport_160 · · Score: 0

      I tihnk that you will find that VIN is an international standard applied to any car built in the world, wether it is sold in the US or not. sport_160.

    4. Re:Let me clarify... by erichill · · Score: 1
      I don't know if you've looked at a Japanese VIN lately, but when I look at a Honda or a Toyota the VINs seem to fit the same pattern as for any American brand.

      Something that strikes me about this is how the states are even going to approve the budget for the change in time, let alone implement it?

      I can just imagine the mess at the DMV, let alone the lines.

      --
      Credo sim. - I think I am.
    5. Re:Let me clarify... by rk · · Score: 1
      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.

      It's also interesting that they think this dwarfs Y2K. Do they really think that VIN is used more than dates?

      I would like to reassure the Society of Automotive Engineers that after a careful and exhaustive audit, the database that I manage containing data pertaining to Mars Global Surveyor and Mars Odyssey is ready for any VIN changes they might need to make.

  26. Simple by Anonymous Coward · · Score: 0

    Use The Global Numbering Automobile Authenitcation (G.N.A.A.) system developped by Gary Niger Corporation back in 1970. It is capable of 17 trillion googol googalplexes worth of combinations.

    More information here

  27. Barcodes already in place by nurb432 · · Score: 1

    I dont know about you, but my VIN already has a barcode printed on the tag, and its a couple of years old...

    It doesnt address the issue of running out of numbers of course...

    --
    ---- Booth was a patriot ----
  28. It wasn't an engineer ... by auburnate · · Score: 2, Insightful

    Whoever came up with the the VIN system as it stands needs to be drawn and quartered. I assure you that had any engineer worth his salt been given the plan of VIN back in 1981, he wouldn't have allowed there to be the imminent shortage we face now. By simply giving the right data fields (specifically the last six) more than enough space, we would have never faced this crisis ... and I hesitate to call this a crisis ...

    1. Re:It wasn't an engineer ... by BigBir3d · · Score: 1

      SAE

      society of
      automotive
      engineers

      implemented in 1981.

      supposed to last 30 years (2011 for the math impaired).

      RTFA.

    2. Re:It wasn't an engineer ... by Zak3056 · · Score: 1

      Whoever came up with the the VIN system as it stands needs to be drawn and quartered. I assure you that had any engineer worth his salt been given the plan of VIN back in 1981, he wouldn't have allowed there to be the imminent shortage we face now.

      It was designed in 1981 to last 30 years. If we run out at the end of this decade, it will have lasted 30 years.

      I fail to see why this is poor engineering. You could argue that it was stupid to design for ONLY a 30 year lifespan, but that would hardly be the fault of the guy that implemented it.

      --
      What part of "shall not be infringed" is so hard to understand?
    3. Re:It wasn't an engineer ... by Trifthen · · Score: 1

      The problem with designing it to only last 30 years, is that means there would have to be a migration path long before the 30 years were up. Now we get to re-engineer the entire VIN system in place all over the country for insurance, government, personal, decoding, and tracking purposes in about 4 years. If they used 2 characters for the year instead of 1, for an 18 character VIN, it could have lasted 961 - and that's only *one* change that could have made the number much more scalable.

      Nice job, guys!

      --
      Read: Rabbit Rue - Free serial nove
  29. 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.'
  30. This is dumb... by jwthompson2 · · Score: 2, Interesting

    We have a system that is potentially going to cause companies to have to upgrade their systems in order to handle a new ID scheme. I understand that companies want to save money, but eventually these things will run out and upgrades will need to be done. Would a smart move not be to bite the bullet and just produce a new numbering scheme with more longevity?

    --
    Even if I knew that tomorrow the world would go to pieces, I would still plant my apple tree. -Martin Luther
  31. 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.

    1. Re:Wait, what part of this should be surprising? by stratjakt · · Score: 1

      36 years..

      As I understand it, the year of manufacture is encoded in one digit. So it goes 0-9, A-Z... 36 years, then it goes back to 0.

      I mean, a 17 digit alphanumeric string gives you 17^36-1 combinations. (1.9777034430598898484014560205854e+44) combinations says windows' calculator. That's a lot. More than IPv6 or MAC.

      It's the year thing that's the "problem", but like you said, they've always known about this problem. And there are many different solutions, they'll pick one (they have about a decade to do so), and life will move on. It's certainly nothing to panic about.

      I'm sure a few little VIN-parsing apps will need to be updated here and there, no big deal.

      --
      I don't need no instructions to know how to rock!!!!
    2. Re:Wait, what part of this should be surprising? by PPGMD · · Score: 1
      I'm sure a few little VIN-parsing apps will need to be updated here and there, no big deal.

      No big deal my ass, headline writer is correct that it's going to cast at least $250,000 per a company (unless it's a newer system). DMVs, car manufacturers, insurance companies, police stations, lenders and anyone else using the VIN number as vehicle identification (whether primary or secondary).

      The governement transition alone will probably cost a couple of million.

    3. Re:Wait, what part of this should be surprising? by Ann+Elk · · Score: 2, Funny

      Sounds like everything's going according to plan.

      It's too bad the plan sucks.

    4. Re:Wait, what part of this should be surprising? by Anonymous Coward · · Score: 0

      I'm sure a few little VIN-parsing apps will need to be updated here and there, no big deal.

      Heh, I work in the auto industry, and you are nuts. The systems are disparate, there is no single system that deals with every aspect of VINs, even in one company. There are systems in the plants, systems in storage lots, systems at ports, systems in accounting, at dealerships, etc, etc, etc. Auto companies and suppliers have an amazing blend of high tech and old tech that has worked forever. It would simply be a nightmare to have to change everything.

      That doesn't even take into account insurance company systems, DMVs, law enforcement vehicle look-ups, etc.

      This really isn't a few little apps here and there.

    5. Re:Wait, what part of this should be surprising? by EvanED · · Score: 1

      It's 31 though; O and Q aren't used because they are too easily confused with 0, I is too easily confused with 1, U isn't used, Z isn't used. In addition, 1980 is given A, and the first year it was in use was '81.

      description

    6. Re:Wait, what part of this should be surprising? by spectasaurus · · Score: 2, Funny

      Really, I was going to post the same thing. Seems kind of like the way things were supposed to work. Makes you wonder what they were thinking in 1981.

      "Hmm, this new VIN thing is good for 30 years."

      "Then what'll we do?"

      "I don't know, I'll be retired."

      "Oh yeah, me too"

      "Let them figure it out."

      "Yeah, at least we'll get to 2000 OK, let's see those banks and nuclear reactors do that."

    7. Re:Wait, what part of this should be surprising? by Random832 · · Score: 1

      The governement transition alone will probably cost a couple of million.

      You misspelled billion... (though i'm told there are numbering systems where 'million' indicates 10^9... if so, then i'm mistaken)

      --
      We've secretly replaced Slashdot with new Folgers Crystals - let's see if it notices.
    8. Re:Wait, what part of this should be surprising? by PPGMD · · Score: 1
      I was think per an agency.

      Jesus the costs of a revamp for the entire country will be unfathomable. Oh well it's a cost of doing business when you don't plan for an expandable system.

  32. VIN Number sparse field by jfmiller · · Score: 2, Informative

    Actually with a 17 digit number ther would be 100,000,000,000,000,000 different VIN number and that doesn account for the fact that the 17 digits are alphanumeric. the problem is that there is information encoded in many of the digits. For example, the first charicter will idintify the country the engine and body were joined (where the care was "manufactured") others idintify the manufacturer, modle year, etc...

    The problem will most likely be solved by assigning each country a secont third or fourth(for us and Japan) identifying digit opening up the rest of the namespace anew.

    --
    Strive to make your client happy, not necessarly give them what they ask for
    1. Re:VIN Number sparse field by Anonymous Coward · · Score: 0

      too many spelling errors... let me be the first to say... "YOU SUCK"

  33. 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 EboMike · · Score: 1

      The VIN is not a random number. Many of the characters indicate something, like make, model, origin, etc.

      This is similar to IPv4 - it's a 32bit number, but you cannot say that "we now have 4 billion unique IDs that may be randomly assigned".

      Just for example, if the first character being an 'A' indicated "DeLorean", it means that 1/26 of ALL possible VINs are reserved for DeLoreans, regardless whether they only make 0.000001% of all cars ever produced.

    2. Re:So many cars in the world... by kidgenius · · Score: 1
      The problem arises because the numbers aren't just arbitrary. They specifically mean something. So, when a manufacturer is limited to 1 letter in one of those spaces, you start to reduce how many numbers you have. Also, there are certain characters that aren't used b/c of their similarity to other letters, but you would know ALL of this if you had simply RTFA.

      Wait, this is /., what was I thinking?

    3. Re:So many cars in the world... by drinkypoo · · Score: 1

      This annoying page which resizes your browser unnecessarily will help you understand why that is not accurate. So will ISO 3779, but you have to pay to get standards apparently...

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    4. 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.
    5. Re:So many cars in the world... by apt · · Score: 1

      If you read the article, you would see that the way that the information is encoded into the VIN doesn't allow them to reach the optimal number of combinations without bending the rules they created when VINs were established.

    6. Re:So many cars in the world... by passion · · Score: 3, Informative

      26?!

      Umm, let's talk about 26 letters (A-Z) - I'm assuming these systems are case insensitive... plus 10 numbers (0-9), I'd say that would make it 36.

      Perhaps they could dramatically increase their potential name-space by making the VINs case-sensitive. That would allow 62 possible characters per place.

      --
      - passion
    7. Re:So many cars in the world... by OverlordQ · · Score: 1

      Ever see a rusted VIN tag? Pain in the ass to even tell what letter it is, now adding even more possibilities . . .

      --
      Your hair look like poop, Bob! - Wanker.
    8. Re:So many cars in the world... by taped2thedesk · · Score: 1
      Perhaps they could dramatically increase their potential name-space by making the VINs case-sensitive.
      they'd still have to change the computer systems to be case-sensitive, in addition to making it really easy to screw something up...
  34. IDEA!!! by WwWonka · · Score: 3, Funny

    ...vehicle ID numbering system (VIN) will soon run out of unique numbers

    Ewww, ewwww...quick, rename it VINv6, adopt the change, talk about it for years on end, scare folks with the apocolyptic visions of a VINv4 disaster, implement sparingly, even have some Finish dude incorporate it into his own car line he started from scratch(obviously stolen from Ford ideas) and have absolutely NO ONE use it due to their legacy cars!

  35. SSNs by j1m+5n0w · · Score: 1
    Automakers build 60 million cars and trucks every year and each one needs a unique VIN in the same way a newborn is given a Social Security number.

    How long until we run out of SSNs? 9 digits == 1 billion unique combinations. Are they efficiently allocated?

    -jim

    1. Re:SSNs by Rura+Penthe · · Score: 1

      They reuse SSNs actually, so they're in no danger of running out. They're not nearly as unique as VIN.

    2. Re:SSNs by LaCosaNostradamus · · Score: 1

      Check my logic.

      If SSNs began to be issued in the 1930s, that means that about 1 Human lifetime has passed. If about 150 million lived in America then, and about 300 million today, then about 150 million were issued for births. Since the variance due to immigration should have folded into the 150 million existing extra people, then that sounds like a firm estimate of how many SSNs have been used. So, about 15% of the "available" set.

      --
      [You have a stable society when some nut guns down a schoolyard and the law doesn't change.]
    3. Re:SSNs by j1m+5n0w · · Score: 1
      Check my logic.

      If the 150 million that lived in America then are distinct from the 300 million today (which is probably mostly true), that's at least 450 million used SSNs, or about 45%. But as an earlier reply stated, they recycle SSNs, so its more like 30% are in use.

      -jim

  36. They do, sometimes.... by Otto · · Score: 3, Informative

    If they produce more than a million units of any particular car in a year, they use letters in here. Sometimes they use letters anyway, to denote different car types and such. The last six characters can be essentially anything 0-Z, it leaves it up to the manufacturer.

    The problem is not that duplicates will occur, it's that the year number will repeat starting in 2011. The 7th character (from the right) denotes the year, and anybody can see, this means that it loops over every 36 years. Not particularly good planning, methinks.

    One simple solution is to recommend both use of all 36 chars in the serial number and to denote the first character of that number to be a character never used there before by most manufacting companies. In most cases, car companies rarely use anything above A or B for the first character of the serial, so for some this will be easy to work around. For others, it may be more difficult as they'll have to change their own internal coding scheme for the serial.

    Most probable change is that the characters for countries (first character) will be stolen, like happened with 4 and 5 for US cars.

    --
    - 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.
    1. Re:They do, sometimes.... by Anonymous Coward · · Score: 0

      What car sells a million units? Matchbox or Hot Wheels?

    2. Re:They do, sometimes.... by Anonymous Coward · · Score: 0

      What do you mean, "Not good planning"? In 1980, everyone knew that we'd have flying cars by 2011. Clearly the manufacturing of flying cars would require a new identification numbering system (why, I don't know). It's not shortsighted, we just dropped the ball on making flying cars!

    3. Re:They do, sometimes.... by Anonymous Coward · · Score: 0

      In 1980, everyone knew that we'd have flying cars by 2011.
      And we would have had them, too, if it wasn't for all the time and effort sunk into the Chrysler payroll system. Damn you Kent Beck!

    4. Re:They do, sometimes.... by A+Bugg · · Score: 1

      Actually the year is the 10th character.

    5. Re:They do, sometimes.... by tomhudson · · Score: 2, Insightful
      Otto wrote: it's that the year number will repeat starting in 2011 ... it loops over every 36 years No, it starts repeating in 2009 (uses 'A"), for the 2010 model year, and repeats every 30 years, because the letters I, O, Q, U, Z and the number Zero are not used to denote years:

      Here's the complete table 1980 to 2039.

      A 1980, 2010 I not used.. Q not used.. Y 2000, 2030 6 2006, 2036
      B 1981, 2011 J 1988, 2018 R 1994, 2024 Z not used.. 7 2007, 2037
      C 1982, 2012 K 1989, 2019 S 1995, 2025 0 not used.. 8 2008, 2038
      D 1983, 2013 L 1990, 2020 T 1996, 2026 1 2001, 2031 9 2009, 2039
      E 1984, 2014 M 1991, 2021 U not used.. 2 2002, 2032
      F 1985, 2015 N 1992, 2022 V 1997, 2027 3 2003, 2033
      G 1986, 2016 O not used.. W 1998, 2028 4 2004, 2034
      H 1987, 2017 P 1993, 2023 X 1999, 2029 5 2005, 2035
    6. Re:They do, sometimes.... by tomhudson · · Score: 2, Informative

      Darn formatting. Here it is corrected. Sorry, my fault :-(

      Otto wrote:

      it's that the year number will repeat starting in 2011 ... it loops over every 36 years
      No, it starts repeating in 2009, not 2011 (for the 2010 model year), and repeats every 30 years, because the letters I, O, Q, U, Z and the number Zero are not used to denote years:
      A 1980, 2010 I not used.. Q not used.. Y 2000, 2030 6 2006, 2036
      B 1981, 2011 J 1988, 2018 R 1994, 2024 Z not used.. 7 2007, 2037
      C 1982, 2012 K 1989, 2019 S 1995, 2025 0 not used.. 8 2008, 2038
      D 1983, 2013 L 1990, 2020 T 1996, 2026 1 2001, 2031 9 2009, 2039
      E 1984, 2014 M 1991, 2021 U not used.. 2 2002, 2032
      F 1985, 2015 N 1992, 2022 V 1997, 2027 3 2003, 2033
      G 1986, 2016 O not used.. W 1998, 2028 4 2004, 2034
      H 1987, 2017 P 1993, 2023 X 1999, 2029 5 2005, 2035
    7. Re:They do, sometimes.... by gnuman99 · · Score: 1
      The problem is not that duplicates will occur, it's that the year number will repeat starting in 2011. The 7th character (from the right) denotes the year, and anybody can see, this means that it loops over every 36 years. Not particularly good planning, methinks.

      And how is this a problem? Will people confuse cars from 1981 with cars from 2010?

    8. Re:They do, sometimes.... by innocent_white_lamb · · Score: 1

      And how is this a problem? Will people confuse cars from 1981 with cars from 2010?

      Yes, when ordering parts from a junkyard (er, automotive parts recycling depot). When you tell Joe to just run over there and fetch the whozit you want to be sure that it fits the frammitz and isn't too tall to go under the stiplarch.

      See?

      --
      If you're a zombie and you know it, bite your friend!
  37. There is a technical solution by Anonymous Coward · · Score: 3, Funny

    Virtual Private Vehicles. It's sort of a blend between a public mass-transit system and your own private vehicle.

    Your car would not have its own VIN while traveling. To get to your destination, you "tunnel" your vehicle into the back of a flatbed truck. Your vehicle would be packaged into the flatbed truck along with other vehicles. Once your vehicle arrives, it would be unloaded and you would take it alone to finish the local part of the trip.

    1. Re:There is a technical solution by Kiryat+Malachi · · Score: 1

      I know you meant this to be funny, but seriously - long distance driving SUCKS, and I would be all kinds of into a system like this.

      Small vehicles (maybe, say, electric-powered?) that can only do 40-60 miles on a charge, and a who-cares-how-its-powered system those small vehicles can piggyback onto that does long hauls.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    2. Re:There is a technical solution by Anonymous Coward · · Score: 0

      There is already a solution available for this... Its called AmTrak.

    3. Re:There is a technical solution by Kiryat+Malachi · · Score: 1

      Amtrak doesn't leave me with a vehicle at the other end.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
  38. First three characters by ad0gg · · Score: 1
    To overcome the shortage, SAE is taking a close look at the first three digits of a VIN -- known separately as the World Manufacturer Identifier. It consists of numbers and letters -- excluding I, O, Q, U and Z because they can be mistaken for numbers or another letter.

    Which number can you confuse U with? And you must be pretty stupid to confuse Z with 5 or S.

    --

    Have you ever been to a turkish prison?

    1. Re:First three characters by rimclean · · Score: 1

      VIN's are stamped on metal. It is easy to confuse a Z with a 2. Not a 5 or S.

    2. Re:First three characters by sartin · · Score: 1

      numbers or another letter.

      Which number can you confuse U with? And you must be pretty stupid to confuse Z with 5 or S.

      You may have noticed, escpecially in some bad fonts or when it is crudely stamped out on metal (as a VIN is), that "U" somewhat resembles the letter "V". When you are reading old, rusty VIN plates stamped into metal 15 years ago on a a production line, it's not that hard to confuse "Z" with "2".

    3. Re:First three characters by Anonymous Coward · · Score: 0

      Z = 2
      U = 0 (well with the top part covered by an old parking garage stub)

    4. Re:First three characters by theGreater · · Score: 1

      How about 'U' and 'V'? 'O and 0' or 'Z' and '2' or '6' and 'G' or '1' and 'I'? Of course, in most fonts they're fairly simple to tell apart, but then most fonts aren't under the hood of your car for 10 years and covered in dirt and grime.

      -theGreater Mechanic.

    5. Re:First three characters by Anonymous Coward · · Score: 0

      V and U perhaps? 2 and Z also?

    6. Re:First three characters by Anonymous Coward · · Score: 0

      And you must be pretty stupid to confuse Z with 5 or S.

      True, but the number 2 isn't all that far off.

    7. Re:First three characters by Trifthen · · Score: 1

      U can look like a V, and Z may look like a 2. It's not just numbers, but any confusing or possibly misleading combination that is restricted.

      --
      Read: Rabbit Rue - Free serial nove
    8. Re:First three characters by Anonymous Coward · · Score: 0

      These numbers are mechanically stamped
      into little metal plates. They don't
      always come out so clear.

      U == 11?
      U == LI?
      U == I1?

      And

      Z == 2?
      Z == 7?

    9. Re:First three characters by CountBrass · · Score: 1

      Are you a moron? You quote "becase they can be mistaken for numbers or another letter" and then ask which number U can be confused with? Well duh U and V (V being a letter) and Z and 2.

      Fuckwit.

      --
      Bad analogies are like waxing a monkey with a rainbow.
    10. Re:First three characters by LaCosaNostradamus · · Score: 1

      I don't know about "U" (forgive the pun), but mixing O, I, 0 and 1 (oh, eye, zero and one) in strings of identifying digits is a bad idea, particularly in real-world situations where the string will have to be read off a dirty tag in poor lighting. Font selection is also often poorly done for printing and punching such things. Which is why (in part) the MICR font is used on checks ... to reduce transcription error.

      As far as I'm concerned, no ID string should use I, O and S since they can be easily confused for 0, 1 and 5 in adverse conditions (i.e. most real-world situations). And while you're doing that, if you can spare the digit-width, get rid of other things that a dirt-smudge can threaten ... which may be why the "U" is omitted.

      --
      [You have a stable society when some nut guns down a schoolyard and the law doesn't change.]
  39. Cars: the new ipv4! by Buran · · Score: 1

    Maybe we just need to go to 64-bit VINs!

  40. Good. by buht · · Score: 1

    Good, these problems promote jobs for those of us that program for a living.

    --

    -- The box said Windows 2000 or better... so I installed Linux
  41. Why not retire.. by MisanthropicProgram · · Score: 2, Interesting

    and reuse the VINs from junked cars? Someone somewhere, especially in the insurance industry, must be tracking them.

  42. Article text (Slashdotted...Feh) by Anonymous Coward · · Score: 0

    Too many cars, too few digits

    U.S. will run out of vehicle ID numbers. Solution? Recycle or buy from Botswana

    By Eric Mayne / The Detroit News
    Image

    Comment on this story
    Send this story to a friend
    Get Home Delivery

    The auto industry's number is almost up.

    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.

    And like an odometer that returns to zero and starts over again, a Vehicle Identification Number -- or VIN -- could be duplicated.

    Experts say duplicated VINs would cause havoc for repair shops, state license offices, insurance agencies, law enforcement and other groups that use VINs to legally rob people by fining them for "parking violations."

    "We've been brainwashing law enforcement and the insurance community and virtually everybody that a VIN is like DNA -- there's one for any one vehicle--and boy are these people easy to brainwash!" said Ed Sparkman, spokesman for the Chicago-based National Insurance Crime Bureau.

    At the root of the impending shortage is the explosion of vehicle production in recent decades. Automakers build 60 million cars and trucks every year and each one needs a unique VIN in the same way a newborn is injected with a Social Security chip. And that doesn't count heavy trucks, motorcycles, bicycles, and other vehicles that require VINs.

    The Society of Automotive Engineers, which established the existing VIN system in 1981 and expected it to last 30 years, has doomed the problem to a committee to address the impending shortage.

    One potential fix: Poach VINs assigned to smaller countries such as Botswana, which don't mass produce vehicles or donate money to US politicians.

    Unlike telephone companies, which simply created new area codes to cope with a surge in households, cell phones and fax machines, the committee, typical to most committees, is not recommending longer VINs -- even though 18- or 19-character codes would not repeat for 100 years.

    Longer codes would require a major overhaul of computer systems that would dwarf the challenges and expenses spawned by the Y2K computer dilemma, said Dave Proefke, chairman of the committee.

    "The scope of the logistical changes and the monetary impact are just gastronomical," said Proefke, a technical engineer for vehicle security at General Motors Corp.

    At smaller manufacturers, the change would cost tens of millions of dollars, Proefke said.

    "For GM, it would mean a significant change for every assembly center we have, all our engineering centers, all our processing centers," he said.

    To overcome the shortage, SAE is taking a close look at the first three digits of a VIN -- known separately as the World Manufacturer Identifier. It consists of numbers and letters -- excluding I, O, Q, U and Z -- because they can be mistaken for numbers or another letter by overweight, nearsighted police officers.

    By international agreement, a WMI is assigned according to region. Initially, the United States had all WMI codes that started with the number 1.

    "We were assuming we were always going to be 1, originally," Proefke said. "Now we're 1, 4 and 5. And we don't have that many left of 5."

    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

  43. 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.

    1. Re:Ooooooooh well. by Trifthen · · Score: 1

      Backwards compatible is right. But that's easy. Whatever the new system is, it'll be larger than 17 digits. Detection code should be able to tell 17 digits from > 17 digits, and handle the VIN accordingly. The main problem is locating the breathtakingly large amount of software that uses VINs in some way, and retrofitting them.

      Yuck.

      --
      Read: Rabbit Rue - Free serial nove
    2. Re:Ooooooooh well. by rice_burners_suck · · Score: 1
      It'll be flippin' hysterical when this happens to the Social Security system. Nine digits can only handle one billion folks. Plus, the numbering system is set up to detect certain combinations as counterfeit, so quite a few thousands of numbers cannot be used. Start this system in the '30's, and with about 300 million folks in the U.S. right now, and about 60 million back then, say in four or five generations (which will be up by 20 or 30 years from now), the Social Security system will run out of numbers and will have to be changed. Try to track down the obscure systems everywhere--in colleges and universities, all medical clinics and hospitals, all banks and financial institutions, all credit card and loan companies, all employers... basically all software that uses that retarded number to identify people... What a mess that will be.

      It serves 'em right, though. I'm against the whole idea of using that number as an ID number for people. It's an account number as far as I'm concerned. There shouldn't be any kind of national ID in this country...

    3. Re:Ooooooooh well. by MenTaLguY · · Score: 1

      As I recall, they're already recycling SSNs.

      --

      DNA just wants to be free...
    4. Re:Ooooooooh well. by yoshi_mon · · Score: 0

      As I recall, they're already recycling SSNs.

      And this is nothing new really. I can remember one of my economics profs telling me this back in collage which was ~10 years ago now.

      In addition to this the American population growth is pretty low. And if we keep nukeing the middle class I can forsee it getting even lower.

      --

      Really, I know what I'm doing...Ohhhh, look at the shiny buttons!
    5. Re:Ooooooooh well. by EtherMonkey · · Score: 1

      OMG! Quick: run to Home Depot and buy a generator before they all sell out!

      Drats, they ran out of generator serial numbers too, and no more can be sold until a new system is introduced. Switch to Plan B: off to the battery aisle!

      --
      --- A man with a briefcase can steal more money, than any man with a gun. [Don Henley]
    6. Re:Ooooooooh well. by ixmo · · Score: 1

      On the other hand, the VIN problem will affect a larger number of computers than the Y2K problem.
      That's a very interesting statement, but I don't get it:
      What do atomic power plant computers or airplane cockpit equipment have to do with automotive VINs?

      ix

    7. Re:Ooooooooh well. by Secrity · · Score: 1

      The vast majority of the computers that use software dealing with VINs (insurance, auto repair, dealers, parts, etc.) use off-the-shelf software. This means that in the vast majority of cases, changing the number of characters in the VIN field would just mean installing a software upgrade and the installer program would take care of the database changes. I suspect that even the more on-off situations use software that is much easier to change than the older banking software.

  44. Why don't they just use more WMI's? by daveo0331 · · Score: 1

    If you RTFA (yeah right), WMI is the first three digits of the VIN and identifies the manufacturer. Apparently US manufactureres can only use about a thousand of these, even though there should be 31^3 = 29,791 total possibilities. A lot of those combinations are probably going unused; why not use them first before doing things like adding digits that will require major changes to the system?

    The article talks about taking WMIs from countries that aren't using them, but doesn't really say if there's WMIs out there that aren't really assigned to anyone.

    --
    Remember the days when Republicans were the party of fiscal responsibility?
    1. Re:Why don't they just use more WMI's? by tomhudson · · Score: 1
      The first character is reserved for country of manufacture, so that changes from 31^3 to 31^2 right there.

      In actual fact, with the way vehicle manufacturing is international, we really don't need this artifact from an older way of doing things.

    2. Re:Why don't they just use more WMI's? by Dyolf+Knip · · Score: 1

      I thought that too! How the hell can they be running out of namespace when by my calculations there should be 31^17 total available codes? That's like 2.2x10^25; at 60 million new ones every year it ought to last 7 million times longer than the current age of the universe. If they're running out, it's due to atrociously lousy allocation of subsets, not inherent problems with the length of the VIN.

      --
      Dyolf Knip
  45. create a whole new protocol by Anonymous Coward · · Score: 0

    call it ipv6, and integrate expanded vins, authentication, various forms of security, and then, when it's ready to go live, we'll have everyone change thier IP's, I mean VINs, at the same time, causing a massive backup at the DMV, taking years, maybe even decades to recover.

    Awe yeah, payback for all those hours I've spent renewing my license.

  46. This will last 30 years, no problem... by Otto · · Score: 2, Informative

    The VIN includes a year code (10th character from the left) that denotes the year the car was made. However, this loops after 30 years (they left out potentially confusing chars in the yearcode, like I, O, U, Q, Z, and zero).

    But in 2011, the year loops. That's the only problem, really.

    --
    - 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.
  47. 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?
    1. Re:Good for speeders! by Anonymous Coward · · Score: 1, Funny

      let me get this straight:

      you traded a '68 Mustang for a '92 Prizm?!

    2. Re:Good for speeders! by Just+Some+Guy · · Score: 1
      Spoken like someone who's never owned an old Mustang. I loved that thing, don't get me wrong (gloss black paint, aluminum rims, kickin' stereo, all in excellent condition), but it was a mechanical nightmare.

      I am a geek, as evidenced by the fact that we're having this conversation on Slashdot, but I could still change the head gasket without referring to my dog-eared Chilton's manual. I will probably never change drum brake pads again, but have the experience to do a good job of it. On the plus side, it was a good hacker's car because a motivated person could learn their way around the the entire mechanical and electrical system. On the minus side, you had to.

      I was stationed in Chicago and awaiting transfer to San Diego when I traded cars. Yeah, I can think of worse things than tooling around in southern California in a classic muscle car, but I can't think of many things worse than blowing a clutch in the middle of New Mexico during the non-air-conditioned drive out there.

      --
      Dewey, what part of this looks like authorities should be involved?
    3. Re:Good for speeders! by Anonymous Coward · · Score: 0

      Obviously, you are not a geek(or at least, not a car geek) if you don't enjoy pointlessly maintaining an old muscle car. That's part of the joy of cars. It's no fun if the thing practically maintains itself.

    4. Re:Good for speeders! by Just+Some+Guy · · Score: 1

      I was a 20-year-old geek with big responsibilities, an unsympathetic employer, and no reliable alternate means of transportation. A muscle car is a blast to tinker with as long it being undriveable doesn't mean that you get sent to jail for being late to work. I fully plan to have another one someday that I can take out on sunny weekends, but it won't be my main driver.

      --
      Dewey, what part of this looks like authorities should be involved?
    5. Re:Good for speeders! by red+floyd · · Score: 1

      My dad dropped a transmission ('75 Fiat) in the middle of the New Mexico desert.

      He had to wait for 2 weeks in a motel in Santa Rosa (?) for a new one to come in.

      --
      The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
    6. Re:Good for speeders! by alexburke · · Score: 1

      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.

      I have modpoints, but merely modding this as +1 Funny simply doesn't do it justice.

      That line is an absolute gem! Consider it stolen. :)

      Keep up the good work, and buy one of these while you're at it, just in case the next patrolman bothers to look up while writing the ticket and notices you're not in an Edsel. They're worth every cent. Don't settle for ANYTHING less.

    7. Re:Good for speeders! by cowlum · · Score: 1

      I couldnt just sit this one out..

      I understand exactly where 'Just_Some_Guy' is coming from. When I got a classic for my first car but had to give it up for a reliable everyday driver. About 5 years later i couldnt stand the 'every day bore' and have started building a hybrid. Its a 1974 BMW 2002 that im installing a BMW m3 fi engine into. Not easy not cheap. But when its done in another few years ill have the best of both worlds.

    8. Re:Good for speeders! by Just+Some+Guy · · Score: 1
      That line is an absolute gem! Consider it stolen. :)

      Thanks, man. That's what makes it all worthwhile. :)

      --
      Dewey, what part of this looks like authorities should be involved?
  48. Know who the culprit is? by Anonymous Coward · · Score: 0

    MIT.

    They were allocated a huge block of VINs when they once were considering getting into the automobile business. I think it's about time they started sharing.

  49. Multiple checkdigits by jfabermit · · Score: 1

    Isn't a really, REALLY easy solution to add in a different checkdigit scheme? If the checkdigit matches the old pattern, use the old system. If it's one more than the old pattern, use a new system. That way, we can make better use of the trillion or so available numbers. That wasn't so hard now, was it?

    1. Re:Multiple checkdigits by bstone · · Score: 1

      The problem with all of these suggested schemes is that they will require an update of all the code that uses VINs. As long as the code needs to be updated anyway, why not just fix it to do things right.

      Also, there's NO WAY that there can be the same amount of code that uses VINs as there is that uses dates, and by definition, that code is at most 25 years old.

      The problem with Y2K legacy code was that some of it dated back 40 years, with the source code missing. Back in the mid 60's, the disk drives of the time could hold about 30 Megs and cost about $600,000 in today's dollars. With the number of dates present in customer/employee records, sometimes cutting from 4 to 2 digit dates could cut almost 10% off your data storage costs. At the time, before people realized that the IBM 360 "family" of computers would really allow code to last, code was assumed to need complete re-writes every few years. Bad assumptions, stupid to allow the source code to get lost, sure, but NOT NEARLY AS BAD as DESIGNING a system to last a max of thirty years and suddenly "finding out" that you have made no accommodations for doing anything about it when the time is almost up.

  50. Stocking up by sjonke · · Score: 2, Funny

    "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."

    No, it's time to stock up on VINs. Anyone want to buy the rights to 4S6RN38F94L296406 ?

    --
    --- What?
    1. Re:Stocking up by Jedi+Holocron · · Score: 1

      How long till the numbers are auctioned off on eBay?

    2. Re:Stocking up by Just+Some+Guy · · Score: 1

      Depends. Is it for the downloadable version, or does the buyer also get the media?

      --
      Dewey, what part of this looks like authorities should be involved?
    3. Re:Stocking up by theonetruekeebler · · Score: 1

      You drive a 2004 Honda manufactured in the US.

      --
      This is not my sandwich.
  51. Why not just put the YEAR in there? by Banner · · Score: 1

    Then you could recycle the tags all you wanted to. I mean really now, how hard could this be? A date tag with a serial number would allow you to reroll the serial number every year if you wanted to (or hell, every day if you use 8 digits!).

    This just sounds like such a non-issue due to the extreme short-sightedness of whatever idiots came up with this scheme.

    1. Re:Why not just put the YEAR in there? by Trurl's+Machine · · Score: 1

      Then you could recycle the tags all you wanted to. I mean really now, how hard could this be? A date tag with a serial number would allow you to reroll the serial number every year if you wanted to (or hell, every day if you use 8 digits!)

      Not that easy. VIN is used to encode lots of information. The first character describes the country of origin, second the manufacturer, then you have places reserved for car type, model year, assembly plant etc. You can't recycle it without actually throwing the whole system away.

    2. Re:Why not just put the YEAR in there? by Banner · · Score: 1

      I mean that after you've inserted a real year field (ie more than one digit, say four), you can recycle the serial number portion of the VIN number. That's the part that is giving them the issue, because it combined with the year and other options is leading to repeats.

    3. Re:Why not just put the YEAR in there? by Kiryat+Malachi · · Score: 1

      No, the year digit is the sole issue here, since we're due for a rollover at the end of the decade.

      Technically speaking, if we used a 4 digit year field, we'd still get a rollover, it would just be roughly 8000 years away.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
  52. IPv6 by isolvesystems · · Score: 0, Redundant

    Suggest they use IPv6 methodology. It basically has unlimited IDs...

    --
    http://www.isolvesystems.com - Technology Marketplace
  53. Bad by EboMike · · Score: 2

    This tinfoil crap is slowly getting on my nerves. Doesn't anyone see the purpose of a VIN?

    Whenever I buy a car, the first thing I get is the VIN so I can check the car's background. This is invaluable. A central registry about cars has many advantages.

    1. Re:Bad by Anonymous Coward · · Score: 0

      A central registry of people would have many advantages too. Just imagine: you're about to ask this hot chick out on a date, and as a mere formality, you scan her ID code tattoo on the back of her neck. Then use this key in a database to bring up her dating history, STD diagnosis and treatment history, and reviews from previous guys that dated her. One of them says, "Higher maintenance than first expected," and another says, "I think I got herpes from this chick." You make an excuse and disappear, having "forgotten" her phone number.

    2. Re:Bad by beebware · · Score: 1



      Yep - sounds a good idea to me - so does a central database of people. Your future partner/employer/employee would be able to look up your backround. /devils advocate)

      If you think about it, VINs are actually quite "unique" in the way they work - I can't think of a single other system in large scale active use which allows you to track a _single_ unit (rules at barcodes) across international borders. VINs are good, but people aren't cars ;)

  54. If I remember correctly... by Anonym1ty · · Score: 2, Informative

    If I remember correctly the left 11 digits are used for make, model, production location, model year etc.... ---the 8th digit from the right is the model year alpha-numeric 1-9 + A-Z they skip 0, I, O and Q (L = 1990 and S=1995)

    They could become case sensitive with the year, or use mor characters in the ASCII table.

    I thought the last 6 digits were supposed to be unique, except it doesn't make sense since I have never seen letters there (maybe there are) and that would have broke after 1 Million cars.

    They could just reassign the letter used for the manufacturer and start over with the year code. This doesn't sound like it has to be that big of a problem for them. Do all GM's have to start with 1G and all Fords with 1F and all toyotas with 1T?????

  55. Aren't we overreacting a bit?? by bckrispi · · Score: 1
    'Longer codes would require a major overhaul of computer systems that would dwarf the challenges and expenses spawned by the Y2K computer dilemma.'

    Let's put this into perspective. Y2K affected virtually every computer system built between the 1960's and the mid 80's. Auto manufacturers can hardly make this claim... What systems read VIN numbers outside of the auto manufacturing industry??? Police, State MVD's and insurance companies are the only ones I can think of. Yeah, it's going to be a PITA, but to claim it's going to be an effort on par with Y2K seems a bit ludicrious.

    --
    Xenon, where's my money? -Borno
  56. We don't need no stinking subject by Anonymous Coward · · Score: 0


    So just use letters in the last six digits as well as numbers.

  57. better planning by t_allardyce · · Score: 1

    Seems like this shouldnt have been a problem - the engineers predicted it would last 30 years when they designed it in 1981 and its still predicted to run out around 2010, id call that spot on and if no-one bothered to design the systems to be easily upgradable then its their fault. All serial numbering systems should have a basic plan for extension even if its not expected to be needed for decades, and all applications that use the numbers should be designed with that in mind!

    --
    This comment does not represent the views or opinions of the user.
  58. VINs not such a big deal in this external system by eltoyoboyo · · Score: 1

    A verylarge fleet services company, with whose verylarge Oracle database I work, uses the VIN as a variable chararacter field. It is not a key field but is indexed. The point being that the VIN was a secondary means of identifying a vehicle outside of Fleet and Unit number. I say: blow 'er wide open.

    --
    Have you Meta Moderated t
  59. ALL YOUR VIN by Anonymous Coward · · Score: 0

    R BELONG TO US

  60. why is this a crisis? by fermion · · Score: 2, Interesting
    will be exhausted by the end of the decade

    The Society of Automotive Engineers, which established the existing VIN system in 1981 and expected it to last 30 years, has formed a committee to address the impending shortage.

    Perhaps I am daft, or perhaps the reporting was inaccurate, but I do not see the crisis. The second quote indicates the system was established in 1981 and was expect to last 30 years, which is 2011. The first quote indicates that the numbers will run out around 2009. Does this mean that the auto industry is in crisis because of a 10% error in their estimation? It really sounds like the numbers running out was expected, and the meeting to discuss the future should just be routine.

    Unlike the Y2K thing, in which everyone assumed that computers would be replaced regularly, there was certainly no doubt that we would still be making cars in 2010, and if we depended on a VIN, those cars would need one.

    From a programming point of view, I am sure many database designers used the VIN as the primary key, and this is why it will cost so much to revamp. After all, we were all assured that the number will always unique. Common sense, however, tells us not to trust anything we don't have total control over, and not to make design decisions based on the assumption that outside forces will never change their minds. Therefore, it might make sense for an auto manufacturer to use the VIN as a primary key. However, I wonder why it made sense for everyone else to do the same, assuming that this is the case.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    1. Re:why is this a crisis? by The+Snowman · · Score: 1

      From a programming point of view, I am sure many database designers used the VIN as the primary key, and this is why it will cost so much to revamp.

      I think the real issue is that millions of systems out there assume a 16 digit VIN with letters and numbers in specific locations with specific meanings. Changing that involves changing databases to allow longer strings, changing validation routines and input boxes to allow longer (and possibly different) strings, and application logic to parse and understand the new, longer strings. The Y2K fiasco involved changing to a four digit string, which is how some systems viewed it anyway, and if nothing else, systems at least displayed it that way. They just assumed the wrong century. With VINs we make assumptions because we as humans defined the VIN. Years have meaning without computers, VINs have no meaning without vehicles.

      I think the best thing to do is add a few more digits to VINs to accomodate future requirements that we do not know about yet. Who knows what we will need? This is the same mentality behind API calls with reserved arguments. Maybe it will need more functionality in the future, so add an extra argument so the signature does not change. That makes it a lot easier to update old applications. Sounds like a solution to a familiar problem, does it not?

      --
      24 beers in a case, 24 hours in a day. Coincidence? I think not!
  61. Take a page from DB normalization... by stienman · · Score: 1

    A serial number should be exactly that - a number which denotes no more information than the sequential number of the item that came off the production line.

    A VIN is sort of a zombie half dead half alive number. It contains information about the item it is attached to, as well as the serial number.

    The real problem is not that it's limited - it had a life span, it's lived that span of time - it's that people developing systems and processes to deal with cars made the assumption that the VIN is not limited in its life span.

    The VIN is useful, no doubt, but the reality is that each car should have a VIN that doesn't contain the serial number and a seperate serial number. If you want to keep both in one number then you can form it yourself by putting the VIN before the serial number.

    They should have designed it to scale 30 years ago.

    But the reality now is that we're due for an upgrade. Now the VIN will be expanded and stored on an RFID chip (or barcoded at minimum).

    -Adam

  62. OT but what about credit card numbers? by tetranz · · Score: 2, Interesting

    I'm surprised we haven't heard something similar about CC numbers. Debit and credit cards, prepaid etc AFAIK all share the same numbering world wide. Does anyone know?

    1. Re:OT but what about credit card numbers? by confused+one · · Score: 1

      ummm, where were you when they went from 12 digits to 16?

    2. Re:OT but what about credit card numbers? by gabbarbhai · · Score: 1

      Out of the usual 16 digits, first 6 determine the bank, card type etc (for Visa, IIRC: 4 for the bank and sometimes digits 5,6 for the card type). So you still have about five times the world population many cards available for each bank including the checksums etc. Also, cars are everywhere, credit cards have not proliferated that much yet, dispite what you might think here in the US. With one-time usage cards, though, there could be a potential problem but IIRC they have expiry dates there. Someone pl. correct me on the last one.

    3. Re:OT but what about credit card numbers? by rabtech · · Score: 1

      VIN numbers are subdivided, sorta like MAC addresses. This means that some people have huge allocations they aren't using while others are running out of space.

      If VINs were just flat alphanumeric numbers (base-36 numbers) then we'd have way more than necessary.

      Most of a credit card number is just that - a serial number, meaning there are plenty of them. (Only the first two and the last digit are "special" - the inbetween digits are the serial part).

      --
      Natural != (nontoxic || beneficial)
    4. Re:OT but what about credit card numbers? by evilviper · · Score: 1
      I'm surprised we haven't heard something similar about CC numbers.

      Why are you surprised at that?

      It's a 16-digit number... Which means you have over 1 TRILLION combinations. Okay, they'll skip "1111 1111 1111 1111" and similar numbers, but that still gives you a load of numbers.

      Now, assuming they remove an incredibly large portion (50%) of those combinations, you've still got 500 BILLION possibly card numbers. That means each person on the planet (that includes 1-year-olds, and 130-year-olds) has to have 83 credit cards each. That has to be all at once, not over their lifetime, because each number expires about every 4 years, then you get a new one, and your old one can be used elsewhere.

      If that wasn't enough, there's also the issue that your credit card number is tied to your name, and issue date (month/year), so using one number on dozens of different cards would be possible, and not likely to result in it being easy to guess card numbers, because you have to guess a vaild NAME, MONTH, and YEAR. Not to mention that most places also verify your address.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    5. Re:OT but what about credit card numbers? by lachlan76 · · Score: 1

      The way that the CC#s are verified, only one in ten numbers is valid, IIRC.

    6. Re:OT but what about credit card numbers? by omahajim · · Score: 1

      Well, for Visa for example, they use 16 digits, each using all of the characters 0-9. Straight factorial math means there are 20,922,789,888,000 combinations. Will that be enough for VISA for awhile? Other than the fact that VISAs typically start with 4 I think, then that makes it 15!=1,307,674,368,000 But I could be wrong.

    7. Re:OT but what about credit card numbers? by omahajim · · Score: 1
      Maybe my math was wrong.

      http://www.seifried.org/security/cryptography/2001 1009-storing-cc.html

      http://www.totse.com/en/bad_ideas/scams_and_rip_of fs/credit1.html

    8. Re:OT but what about credit card numbers? by Ignorant+Aardvark · · Score: 1

      Yeah, your math is wrong, it's not 16!, it's 10^16.

  63. Misspelled Title by kb0pin · · Score: 1

    You misspelled the title. It should say Auto Manufacturers Running Out Of Unique Ideas.

  64. Since VIN numbers are used by police insurance etc by Anonymous Coward · · Score: 0

    And databases are never current even in the best of situations and given my experience with recycled phone numbers when the previous owner was a deadbeat, you would come to regret a owning a vehicle with a recycled VIN that had ever been listed as stolen or on criminal records.

  65. LBA Mode needed then by Anonymous Coward · · Score: 0

    Sounds like they need to come up with an LBA mode for VINs..

  66. 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!!

    1. Re:BSD by happyfrogcow · · Score: 1

      See! BSD is dying!!

      i can't wait for the /. article next year! oh happy days!

  67. A call to arms.... by snax · · Score: 1

    Most probable change is that the characters for countries (first character) will be stolen, like happened with 4 and 5 for US cars.

    So it's really just the US that's having problems, right? So now we'll be taking over countries for their VIN prefixes....
    1. Re:A call to arms.... by StalinsNotDead · · Score: 2, Funny

      So it's really just the US that's having problems, right? So now we'll be taking over countries for their VIN prefixes....

      Yeah. Those conspiracy-lovers think it was all about oil. But in reality it was the unused VIN prefixes in Afghanistan and Iraq.

      --
      Thanks to the internet, we can now all die alone together! -SomeWoman
  68. we thought we would run out of ip's too... by tr0p · · Score: 1
    This is a simple problem to fix when you understand how we solved the problem of running out of ip's:

    1) Begin design and manufacture of the "automobile router" that can delegate and manage hundreds private VIN's per single real VIN.

    2) ???

    3) Profit!

    --

    My only regret... is that I have... bonitis..

  69. Auto Manufacturers Running Out Of Unique IDeas by Anonymous Coward · · Score: 1, Funny

    ...would be an even better headline.

  70. VIN Format by dopaz · · Score: 2, Informative

    Lets take a look at a VIN. First you can only use capital letters and numbers, except for the letters I, O and Q. If you can't tell if its a letter or a number then its a number. WVW EE83A2 SE219476 The first three characters are the WMI, world manufacturer identifier. With the above VIN its pretty obvious who made this car (volkswagen). I can't speak for other manufacturers, but with volkswagen the first character is the country of manufacture. This Passat was built in Germany. The next six characters are the VDS, vehicle descriptor section. Manufacturers use this to describe the vehicle traits, and if you google for "volkswagen vin decoder" (or whatever manufacturer you're looking for) you can probably find out what the codes represent. The last digit in this section is a check digit. The final 8 characters are the VIS, vehicle identifier section. At least, the last 5 digits must be numbers and it is the production number of the car (serial number). The first character in this section is the year of manufacture. With VW, the second character in this section is representative of the plant that built the car. The remaining digits are the production number. If you look at the year of manufacture it rolls over every 30 years anyways. With a little common sense it shouldn't matter if two cars have the same VIN... there would be an age difference of 30 years.

  71. Note to self by yet+another+coward · · Score: 1

    If I find myself in charge of inventing a numbering system, estimate the range necessary and then double the number of bits used.

  72. Chicken Little by __aanhjr1420 · · Score: 2, Funny

    "[...]would dwarf the challenges and expenses spawned by the Y2K computer dilemma."

    So, in this engineer's opinion, we've got more systems using VINs than dates?

  73. They can't tell a 1981 Buick from a 2011 Buick? by Secrity · · Score: 2, Informative

    And I thought that the Y2k issue was sort of shortsighted. These people have NO excuse for this fiasco. In 1981, the people who invented these VIN's thought that 31 years was sufficient? They didn't know that there were cars around that were more than 31 years old then? They thought so little of the cars made at that time to think that none of them would last for 31 years? To think, our tax money will help the DMV fix this problem, no matter how they fix it.

  74. Bad analogy in article by gotr00t · · Score: 2, Informative
    In the article, it keeps mentioning how a "VIN is to a vehice as DNA is to a human," however, this comparison is flawed in many ways.

    First of all, you use the VIN to seach for details about a vehicle in a database, its not there to build a vehicle out of, which is the essential purpose of DNA for humans.

    Secondly, you can't use a DNA sequence to seach for information about a person by simply typing it into a form somewhere on the net.

    And then there exists the fact that there exist humans with the exact same DNA. Identical twins, for example, have the same genetic code.

    They should say something like "a VIN is to a vehicle as an SSN is to a person." Even though the SSN is only in the US, its still a better analogy in comparison.

  75. Easily Handled by sogoodsofarsowhat · · Score: 1

    Just upgrade Vins to IPV6 and the problem is solved :)

    --
    . I love the sound of burning women and screaming rubber....
  76. The real solution ..... by Anonymous Coward · · Score: 0

    how about people just stop buying cars? I mean, get real, it's so much cheaper to keep an old car running than to build a new one.

    1. Re:The real solution ..... by EvanED · · Score: 1

      Only to a certain point.

      You also miss benefits of newer cars; increased gas mileage, better safety features, etc.

    2. Re:The real solution ..... by Anonymous Coward · · Score: 0

      I'll put my '84 Chevy Caprice against your '04 Civic ANY DAY! :)

  77. 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
  78. Wow by Fuzzums · · Score: 1

    So they're going to make 64-bit cars now?

    --
    Privacy is terrorism.
  79. Re:Carmageddon, iROBOT! by Matey-O · · Score: 1

    Don't worry...the badguy robots all turn on this red E.T. heart light thingy.

    --
    "Draco dormiens nunquam titillandus."
  80. Change from numbers to AlphaNumeric by PetoskeyGuy · · Score: 1

    There is a rule that the last 8 characters of a VIN are used to ID the car. The previous ones the make/model/manufacturer. Strike the last 4 numeric rule and you've suddenly got a shitload more unique codes.

    That would be a much simpler solution then extending the field length because the expensive dinosaur systems that run car dealerships right now probably wouldn't handle a change in the length of the field.

    The rules say numbers and capital letters only, no I, O or Q. Can some bored CS major out there tell use how many new cars would be added by changing from 4Alphanumberic+4Numeric to 8Alphanumeric?

    1. Re:Change from numbers to AlphaNumeric by J'raxis · · Score: 1

      Considering that this thing is mandates as numeric, how much software out there is storing this portion of the VIN as an integer?

      [Software used by insurance agencies or law enforcement probably treat the whole VIN as one long unique ID, but I'm thinking of software used by individual manufacturers: since the first segments of the VIN would always be the same, within this context, this information probably isn't duplicated in each individual record.]

  81. You're wrong by Anonymous Coward · · Score: 1, Funny

    I speak from experience

    1. Re:You're wrong by multiplexo · · Score: 3, Funny
      I speak from experience


      Is this the perfect /. post or what? Someone posting as AC, saying that another poster is wrong, claiming experience and then not providing any further information. It's as if this is the Jungian archetype of a /. post, the Platonic ideal, the ne plus ultra.

      --
      cheap labor conservatives - they want to keep you hungry enough to be thankful for minimum wage.
  82. Could be... by SuperKendall · · Score: 3, Funny

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

    Obviously it's not a ford.


    Well, it could be - probably right after the purchase he had to roll it backwards a few feet to get it up on the blocks.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  83. Yawn by nuggz · · Score: 1

    Why not allocate letters to the country of manufacture?
    VIN2 can start with a Z.

  84. This was done deliberately... by James+Turpin · · Score: 0

    It was designed to last only 30 years. Obviously if they allocated the number more efficiently you wouldn't run out, but the guys who designed it don't care because now they have to be hired out of retirement as consultants (or at the very least that was their intention). They are comparing this to Y2K not because it is that bad, but because the people who orchestrated the crisis want to prep their potential customers, to get them used to the idea of paying outrageous fees for an overhaul, regardless of how dificult (or, rather, easy) the fix turns out to be.

    --
    Mathematics is not a crime.
  85. Chaos envy by Doc+Ruby · · Score: 1

    The car biz envies the computer biz. Their own equity languished in comparison to dotcom stocks, so they used the Al Qaeda planebombings to justify financing billions in SUV debt. Now they want the budgets spent on Y2K for their own IT. Nowhere in the article does it explain how the 17 digit VIN, containing several letters (therefore a capacity of at least millions of billions, if not trillions of trillions, of unique IDs) are actually "running out". Or why this is a surprise, when the 1981 system, planned to last 30 years, is possibly approaching a limit after 25 - 85% of the way into its lifetime. Who knows exactly where this story comes from - most likely, the media obsession with fear of threats to the status quo.

    --

    --
    make install -not war

  86. Common Sense by Analise · · Score: 1

    Duplication could still occur, but the difference between a 30-year-old vehicle and a new one should help avoid any confusion, experts say.

    "It's common sense," said Val Vitols, executive director of Michigan's Automotive Theft Prevention Authority.


    But not many people have/use common sense. They tend to freak out when something new/confusing drops into their path and messes up their routine.

    --
    >insert witty sig file here
  87. No Problem by jpatters · · Score: 1

    That's OK, I'll just set my VCR to 1972 again.

    --
    "Remember, there never were pineapple-almond cookies here."
  88. If they can't sove this they're stupid... by Anonymous Coward · · Score: 0

    Hell, this has happened previously in Spain. Madrid used to have M-XXXX-L (where X is a number and L a letter). When they finished they went for M-XXXX-LL. Valladolid did the same, the same for most of the spanish cities. If this could be done in Spain - which is far from being as avanced in computing as the eeuu is - I'd laught if this can't be done in the states...

  89. Red Tape by H0NGK0NGPH00EY · · Score: 1

    Sounds like a problem with red tape, rather than a problem with the actual amount of available numbers. They just need to figure out a better way to use the space they have. A 17 digit code, where each digit is either a letter or a number (36 possibities for each digit) has 286,511,799,958,070,431,838,109,696 possible combinations!

    Somehow I doubt even a tiny fraction of 286 septillion cars have been produced, or will ever be produced.

    --
    Do not read this sig.
    1. Re:Red Tape by pclminion · · Score: 2, Informative
      The VIN isn't just an ID, though, it encodes all sorts of relevant information. Each car manufacturer follows the same basic scheme, but the details of how the data are encoded varies between car makers.

      For example, the VIN can encode the make, model, year, original color, original interior type, factory accessories, the manufacturing line it came off of, etc. It is true that this information could be compressed to some degree, but one of the key features of the VIN is that it is human readable (at least by people who are experienced with it), and doing "clever" things to compress the data into fewer digits will break that.

      For example, consider what would happen if we applied your advice to the Y2K problem and tried to find a clever encoding to make "better use" of the available digits.

      It was common to encode a date using 6 digits: 2 for the day, 2 for the month, and 2 for the year. Suppose we continue to use 6 digits, but instead of encoding the date as MM-DD-YY, simply write the number of days it has been since January 1, 1970. Using this encoding, it is possible to represent dates for (approximately) the next 2700 years, without making the date field wider than 6 digits.

      It should be obvious, though, that such an encoding would be extremely frustrating since it doesn't map to our normal concept of months and days. Quick, what month does day number 516672 fall in? This is exactly why the right choice for Y2K was to simply expand the fields to use the entire year. And the same argument applies to VINs.

    2. Re:Red Tape by Anonymous Coward · · Score: 0

      Quick, what month does day number 516672 fall in?

      June.

    3. Re:Red Tape by MCZapf · · Score: 1
      The VIN isn't just an ID, though, it encodes all sorts of relevant information.

      More like all sorts of irrelevant information. They put in too much. I don't need to be able to determine how many cupholders the car has by looking at the VIN. I can just look at the cupholders! Why didn't they encode the optimum gasoline octane rating for the engine into the VIN too? Because it's in the manual, that's why. There are some things you'll just have to look up separately.

  90. GUIDs -- let's just bite the bullet by msew · · Score: 1

    GUIDs -- let's just bite the bullet and never run out of IDs again.

    Sure you use more space in the DB but the cost of that compared to haveing to rearchitect and update all of the hardware and scanners and such is negligible.

  91. extend alphas Re:Extend the character set? by swschrad · · Score: 2, Insightful

    allow letters in the serial number portion, overlay models onto the "old" model designations, revisit closed plant IDs for that section of the VIN... lots of possibilities out there. it's pretty simple to fix any code that demands that the last 6 characters be numeric, for instance, and the hardest part is for folks to accept that if you set too small an address space, you have to hack it later and fool up your pretty rules.

    this is not rocket science, and civilization will not die.

    --
    if this is supposed to be a new economy, how come they still want my old fashioned money?
    1. Re:extend alphas Re:Extend the character set? by tomhudson · · Score: 1

      Exactly. It used to be that the last 7 digits were expected to be numeric. There's no reason not to allow alphas in the last 6 digits.

  92. maybe it's time for by ShadowRage · · Score: 1

    VINv6?

  93. 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.

  94. Re:They could mix up the alphanumeric rules a litt by confused+one · · Score: 1

    unless you're converting the numbers to uint to conserve space...

  95. names. . . by Rogue+Leader · · Score: 1

    Luckily, auto manufacturers haven't run out of really stupid names for their cars; Toureg, Aztec, Nubira, etc. Were these spit out by the same computer that gave us Viagra?

    --

    worst sig ever. . .

  96. No, not good by blincoln · · Score: 1

    VINs are a very handy feature.

    Last year I started looking for a car. At the time I was really interested in a Subaru SVX, since they're kind of like relics of the 80s future that never was.

    Anyhow, I was very close to buying one from a guy that seemed reputable, but just to be on the safe side I ran the VIN through Carfax.

    It turned out that that particular VIN had been issued a "dismantled" title, meaning the car had been damaged so heavily that it was no longer possible to repair it and re-title it. It was actually illegal to drive on the road.

    I figured there were two possibilities - either the dealer had bought the wrecked car and fixed it up using substandard parts, or he'd done a Gone in 60 Seconds (the original version) on it and swapped the VIN tags from the wrecked car with those from a stolen one. Either way, it wasn't something I wanted to pay $5000 for.

    --
    "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
  97. A Fortune to be Had by zangdesign · · Score: 1

    1. License the right to build cars in countries with no existing car industry
    2. Snap up all those unused VINs
    3. ...
    4. Profit!

    --
    To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
  98. Well what about... by swaic · · Score: 1


    What happens when you buy a car at auction. I believe the original VIN is removed and replaced with a new one. For example, a car sold at auction in New York will get a new VIN with something like NY12345.

    So they could just start using a hex VIN starting at zero and have old cars come in for re-vin'ing if a duplicate arises. Good thing they don't hire me to decide those things...

    1. Re:Well what about... by satterth · · Score: 1
      I believe the original VIN is removed and replaced with a new one. For example, a car sold at auction in New York will get a new VIN with something like NY12345.
      I think That only happens at Fat Tony's Chop Shop.
      --
      Being called a dork on Slashdot must be like being called the retard in special ed.
  99. Well, most of them, in fact.. by Otto · · Score: 1

    I misphrased that. By "particular car" I meant like "Ford" or "Chrysler" or "Toyota". While a manufacturer than use the 3rd digit to denote the specific car type (like "Impala" or "Taurus" or "WhateverPieceOfShitToyotaMakes"), few do that. Most use a letter in the serial number instead.

    --
    - 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.
  100. Confirmed kills? by Lord+Bitman · · Score: 1

    Dont they keep track of cars which can be confirmed to have been destroyed? Why not re-use numbers?

    --
    -- 'The' Lord and Master Bitman On High, Master Of All
    1. Re:Confirmed kills? by bstone · · Score: 1

      Sure, let someone else use the VIN of my brand new "fix-er upper" that I got cheap at the junkyard. Does that mean he gets my tickets, too (assuming I can actually get the thing to go past the speed limit).

    2. Re:Confirmed kills? by Lord+Bitman · · Score: 1

      maybe you dont quite understand "confirmed to have been destroyed".. I'll phrase it differently:
      "confirmed to have been destroyed"

      oh wait, that's the same way of putting it. I guess there's no way to be clearer than that.

      --
      -- 'The' Lord and Master Bitman On High, Master Of All
  101. Outsource it! by lesv · · Score: 2, Insightful
    It's just time to bite the bullet, and rewrite all that code. I'm sure that Detroit, the Gov., and all others concerned don't mind relying on India, China, and Russia for their core applications. After all, they supported laying off local software developers. :)

    You'll never work in this town again! ... Unless, of course we need you.

  102. Fine With Me by CyborgWarrior · · Score: 2, Funny

    I ground the VIN numbers off my car everytime I ermm....get.....a new one :-D

    --
    If you can't say something nice, make sure you have something heavy to throw.
  103. Pretty much, yes... by Otto · · Score: 1

    The problem is that there's a lot of countries that we don't import vehicles from that have country codes assigned. They don't really need them. Take the whole range of F* codes:

    FA-FE Ghana
    FF-FK Nigeria
    FF-FK Madagascar
    FL-F0 not assigned
    GA-G0 not assigned
    HA-H0 not assigned

    While there's the G and H codes to steal from essentially nobody, the F codes are pretty useless to those countries too, as they don't make cars for the US. See, the codes only really apply to cars here in the US, other countries can do whatever the hell it is that they want to do. So we could gank the whole F series without much problem.

    --
    - 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.
  104. Don't forget the dealerships by taped2thedesk · · Score: 1

    It will be a lot more expensive to upgrade all of the individual dealerships and repair shops. Tons of old mainframe-based code that is hardcoded to accept 17 digits. In addition, many of the preprinted forms actually have seventeen separate spaces for the VIN digits, rather than one big box. There are all sorts of little things like this that will need to be taken care of.

  105. I doubt it is so difficult.... by whoever57 · · Score: 1
    There are many cars on the road that don't have a VIN in the current format. Insurance companies, DMV's etc. all have to track these. For example, my 40+ year old car is titled against the engine number and it is nowhere near 17 digits. Apparently this was quite common at the time the car was originally registered -- at least for that manufacturer.

    The local DMV, insurance company does not seem to have a problem with my car's less than 17 digit VIN.

    So the systems in place must already be more flexible than is suggested by the article.

    --
    The real "Libtards" are the Libertarians!
    1. Re:I doubt it is so difficult.... by EvanED · · Score: 1

      I don't see anywhere in the article that it says all VINs are exactly 17 digits, just that expanding it to 18 or 19 would require a huge overhaul. Which it would, of course, considering that a, say, 13 digit VIN will easily fit in 17 spaces, but 18 wouldn't.

  106. Bull by Anonymous Coward · · Score: 1, Funny

    Finally - a slashdot comment that is both insightful and a load of bull!

  107. Easy solution by hal9000 · · Score: 1

    STOP MAKING AUTOMOBILES! :-p

    --
    Look out honey, 'cause I'm using technology; Ain't got time to make no apology
  108. Easiest solution...well, would have been anyway... by ScrappyLaptop · · Score: 1

    Isn't the simplest way to eliminate unique-number obsolescence just to incorporate the YYYY (or YYYYMM or YYYMMDD if you must) into the first x digits of the unique number? That way if you won't run out in a single year, you will never run out. Well, not until the year 9999, anyway...

  109. Convert to AMD64 by Nom+du+Keyboard · · Score: 1

    Just convert VINs to run on 64-bit processors. I'm assured this solves all addressing problems into the foressable future.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  110. just use duplicate numbers by timts · · Score: 1

    I dont think anybody would mistake some 20 year old car as new one.

  111. no need by krokodil · · Score: 1

    no need to make numbers longer - just extend
    alphabet with additional characters.

    Arguably, this would be easier upgrade for existing
    systems.

  112. This is a horrible hack, but... by devphaeton · · Score: 1

    The thing that i have yet to see anyone mention is this:

    Most of the car models in the lowest registers of the VIN numbers are no longer in production, and haven't been for 20-some years. We *could* re-use some of those numbers.

    Secondly, I don't know if you've noticed or not, but there are much fewer car companies than there used to be, *and* each company is making much fewer models.

    It won't be long before SUVs are no longer `cool', and gasoline will be rare and prohibitively expensive. More folks will be buying cars that run on fuel cells or electricity.

    Thenagain, car makers should just STFU, bite the bullet, and understand that shit like this happens. If it were thought through a little more 30 years ago, we wouldn't have to do it yet.

    The key is designing a system that doesn't expire until after you've died

    --


    do() || do_not(); // try();
  113. Hello? by CaptDeuce · · Score: 3, Funny

    Unlike telephone companies, which simply created new area codes to cope with a surge in households, cell phones and fax machines, ...

    Simply? Donchya just love it when a complex problem can be dismissed with that simp... er, ... single word? We're running out of area codes too.

    Then there's large metro areas that have switched to 10 or even 11 digit dialing. Say you move to such a place and you take your phone with with you -- you know, the one with all your those numbers programmed into it by your wife -- and you need to add the area codes to all of them. Going the other way, some (many? most?) areas that only use 7 digit dialing and you gotta remove the area codes.

    No big deal you say? Chances are it's her phone and she lost the manual. Or maybe it just seems to always happen that way.

    Then there's area code splits. I'd hate to be responsible for any sizable contact database when that happens.

    Good thing that phone numbers can be dealt with so simply.

    :^j

    OK, show of hands: how many of you know two or more VINs? Good. Now all you smart asses put your hands down. Ah. I see one hand up in ... I think that's Montana ... and there's three in North Carolina. OK, hands down.

    Now, how many of you know three or more phone numbers?

    [earth's orbit shifts slightly]

    Thank you.

    --
    "Where's my other sock?" - A. Einstein
    1. Re:Hello? by theonetruekeebler · · Score: 1
      Until the early 1990s all U.S. area codes had either 0 or 1 as their second digit. Furthermore, no exchange had 0 or 1 as its second digit. There was a substantial amount of reprogramming to do at phone companies and elsewhere to recognize the newly-allowed numbers as valid; it was not a trivial problem.

      You want to know what would relieve area code pressure? Tax reform. I'm not kidding. The area code system was designed so that area codes never crossed state boundaries. In-state calls and interstate calls are subject to different taxes, see, so you have entire area codes wasted on places like Alaska and Wyoming, each with a population under a million.

      Where I live, I have six area codes that are local calls, but I don't care anymore, because I don't use my home phone for anything anymore---from my cell phone, all calls are local and an 11th digit would be a trivial addition.

      --
      This is not my sandwich.
    2. Re:Hello? by BCW2 · · Score: 1

      It would have been simpler to create new cell only area codes and leave the land lines alone.

      --
      Professional Politicians are not the solution, they ARE the problem.
    3. Re:Hello? by aisnh · · Score: 1
      Yes, it's sad, but I know my VIN by heart. I got into an accident once, and when I went around to get estimates at body shops the conversation usually went like this:
      Estimator: Can I see your registration?
      Me: It's JH4DA9356NS033641

      Apparently, in 30 years in the business, he had never run into anyone who had memorized their VIN before. He had me tell it to everyone in the shop.
      Heh.

      (And yes, for all of you who are going to look it up, it's a 1992 Acura Integra)
    4. Re:Hello? by CaptDeuce · · Score: 1

      Apparently, in 30 years in the business, he had never run into anyone who had memorized their VIN before. He had me tell it to everyone in the shop.
      Heh.

      Ah. You must be one of the gentlemen in North Carolina.

      :-D

      --
      "Where's my other sock?" - A. Einstein
  114. What happens to the credit cards? by bigsimes · · Score: 1

    Their numbering must eventually end and what will happen then?

    For VINs 'doppelgangers' might be a solution, using some other marker to identify in conjunction with the VIN, like the area those VINS were issued in.

    Remembered a link here to credit card numbering logic, interesting read.

  115. Offtopic: SSN mandatory by Anonymous Coward · · Score: 0

    Well.. you techincaly don't.. I THINK. If you never ever earn an income then you don't need a tax id because you never fill a tax return. (or does the gov mandate that eveyone file a tax return, even if you only live in a state park and eat wild berries?)

    And if you don't participate in (i.e, plan to draw benifits from) the U.S. dept of health's social security program, you don't need an SSN..

    I'm probably wrong though....

    1. Re:Offtopic: SSN mandatory by Anonymous Coward · · Score: 0

      You're right. You don't need a SSN if you don't work, because you'll never contribute to or withdraw from the Social Security fund, and because you'll never file taxes. But if you don't have a SSN, you won't be able to get a driver's license, open a bank account of any kind, attend a college or university, get a credit card, get a Blockbuster card, and so on.

    2. Re:Offtopic: SSN mandatory by Kiryat+Malachi · · Score: 1

      Banks, universities, and credit card companies might not let you get away with it, but Blockbuster will absolutely not require it if you complain. Since most video stores require your account to be credit-card backed anyway, there's no reason for them to ask for your SSN, and no reason for you to give it to them.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
  116. the answer to everything by Enrico+Pulatzo · · Score: 1

    use ipv6, of course.

    It's not like cars won't eventually get their own ip anyway, so let's do it now.

  117. Unicode, baby by Atario · · Score: 2, Funny

    "It's 1 Z D R J (aleph) (delta) (omicron) (one quarter vulgar fraction) (ordinal indicator, masculine) (cyrillic capital letter KJE) (surjection, z notation finite). Oh shoot, I forgot the (german penny sign). Lemme start all over..."

    --
    "A great democracy must be progressive or it will soon cease to be a great democracy." --Theodore Roosevelt
  118. just add wingdings? by wardk · · Score: 1

    add Windings, I want my vin to have happy faces.

  119. Bullshit! by Anonymous Coward · · Score: 0

    17 positions, each with 36 possible characters, yeilds 286,511,799,958,070,431,838,109,696 different possible VINs!!! I refuse to beleive they have used up all possible combinations! They don't need more digits or more posible characters for each digit, they just need to relax the encoding rules a bit!

  120. this is not a new problem to the auto industry by HappyDrgn · · Score: 1

    This has happened before. Take a look at a VIN for a car made prior to 1970. As a side, I sold a 1967 VW bug to someone out of state 5 years ago (I am in California, I believe they where in Nevada). Their DMV requirement was a notarized memo w/ VIN and title photocopy "proving" ownership in my state. I went to my bank at the time, Washington Mutual, who was unable to process it because a requirement was putting the VIN in their system. As it turns out their validation system would not accept my VIN because it was too short. I ended up having to get it done at another bank.

  121. Non-unique VINs by AndyChrist · · Score: 1

    Add some digits which would identify them as post 200x. Systems which are not upgraded to accept these digits but which can have two vehicles per number should still have operators intelligent enough to figure out which of (come on, seriously, at MOST two) vehicles they are looking for.

  122. Morons!!!! by Pedrito · · Score: 1

    From the article:The Society of Automotive Engineers, which established the existing VIN system in 1981 and expected it to last 30 years, has formed a committee to address the impending shortage.

    Well hell, 30 years? That was pretty friggin' short-sighted. Can you say, "Digging your own grave." How about, "Making your own bed?"

    And how can you come up with a 17 digit code that only lasts 30 years.

    I guess the degree of automotive engineer didn't require much math in the 70s and 80s.

    1. Re:Morons!!!! by the+eric+conspiracy · · Score: 1

      That was pretty friggin' short-sighted.

      Not really. You are some 40 year old SAE guy in a room thinking 30 years? Great! I'll be retired by the time the shit hits the fan. After that, who gives a rats ass.

    2. Re:Morons!!!! by Pedrito · · Score: 2, Funny

      Not really. You are some 40 year old SAE guy in a room thinking 30 years? Great! I'll be retired by the time the shit hits the fan. After that, who gives a rats ass.

      Yeah, but it's not like cars hadn't been around a lot more than 30 years by the 70s already. Did they really think we'd all be flying helicopters in 30 years? Come on.

  123. It's the Hardware Stupid! by zachlipton · · Score: 1

    A lot of people are saying that this shouldn't be any big deal, and even that it would be trivial to use alphanumeric VIN's, leaving a huge number of possibilities. However, the problem with this is that there is a huge amount of hardware around that relies on the existing VIN format, such as the machines the parking-ticket people use or eqipment at the vehicle factory. While it is usually (unless you lost the source code, but that's another story) possible to update software to handle the larger numbers, it's a completely different story when the code is etched in hardware. Furthermore, these hardware devices are very light-weight, meaning that memory is at a premium and the designers would have been unlikely to build their systems in a way that would easily handle the extra digits.

    As for those who are saying that alphanumeric VIN's should be used, it's a pretty big deal to add alphanumeric keyboards to all the machines with only numeric keyboards.

  124. how about ipv6? by agwis · · Score: 1

    I understand that with ipv6 there is supposed to be approximately 340,282,366,920,938,463,463,374,607,431,770,000,00 0 ip addresses available. As more and more vehicles are using technology like onstar and becoming more computerized it's only a matter of time before you will be able to access your vehicle (statistics, upgrades, etc) through a web interface. At that point, you will need an ip number for it and it could double as the vin number.

  125. You sir, by geekoid · · Score: 0, Flamebait

    are scum.
    First, you were driving at a high rate of speed.
    Second, you got caught
    Third, the patrolman decided you seemed decent enough, and beside you serve the country, and cut you a break writung you a ticket for 5 miles over the limet.

    Then you though it all back at him using some cheesy mistake.

    You are no different then a billion dollar company moving money around to avoid taxes.

    As a vetran, I find what you have done not only an insult to police force, but a disgrace to the uniform.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    1. Re:You sir, by Just+Some+Guy · · Score: 1
      First, I was on an all-but-abandoned four-lane highway in a sports car designed to take it.

      Second, you're right: I didn't resist.

      Third, the summons wanted my signature to attest to the fact that all of the information was correct, and it wasn't. In that state a factually incorrect ticket is grounds for automatic dismissal. In other words, the law gave me a choice between lying (that the ticket was correct) and being fined, or telling the truth (that the ticket was not correct) and being found not guilty. I did not ask for or receive any special favors.

      What would you have done in my case? If your answer is "perjured myself and paid the fine", then you're lying. BTW, you're willing to write me off as scum because I legally and ethically avoided paying a speeding ticket nearly 15 years ago? I admit that you have higher standards than most.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:You sir, by Y2K+is+bogus · · Score: 1

      Dude, I'd arrest you for reckless driving if I saw you flying down the freeway in a Geo prizm.

      That car had a 1 in 3 chance of serious injury, to the driver, and nearly a 50/50
      chance of serious injury to the passenger, in frontal crash tests.

      Irrespective of the 4 wheel disc and 130HP engine, that car is a cheapo tin can death trap.

    3. Re:You sir, by fred911 · · Score: 1

      "Third, the summons wanted my signature to attest to the fact that all of the information was correct"

      Did not. All the summons did was allow your release of arrest, with your promise to appear to the hearing.

      If you don't sign a ticket you can be held until a hearing is compleated.

      --
      09 F9 11 02 9D 74 E3 5B - D8 41 56 C5 63 56 88 C0 45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  126. Yea right.. major overhaul... by miketang16 · · Score: 1

    They're just saying that because they don't want to do it. They'd rather make a big deal about it so that when they finally have to do it, they'll get paid more for it.

    --
    -------
    "In times of universal deceit, telling the truth becomes a revolutionary act."
    -- George Orwell
  127. don't forget the handwriting by Tangurena · · Score: 3, Interesting
    Almost all of the warranty forms used by GM Ford and Chrysler (used for fixing radios or other electronics in the vehicle) have one stage where human handwriting is used. Uppercase and lower case can be really hard for even humans to distinguish. Along with some idiot leaving off 1 digit from the VIN can make the warranty processing situation more challenging.

    Dealing with handwriting is why certain characters were eliminated. Think of error correcting/preventing codes. The check digit really only existed to prevent the casual abuser from falsifying warranty claims and VIN tags.

  128. I can almost hear it echoing... by localman · · Score: 1

    One of the designers is worried about not having enough numbers and suggests they use a larger numberspace or an easily extensible system and some other clever guy says, "Heh! It'll be a great day when we have that problem!"

    I can't counthow many times I've heard that. But nobody ever ends up happy when that day comes.

    Cheers.

  129. why? by geekoid · · Score: 1

    I mean all your variable are defined in one place, right? There all clearly labeled, right? plus you can just go to the documentation...

    OTOH, the IT community could use a job boost, so with any luck all thre systems are hard code and have variable names like asd34fd. oh, and no comment or documentation.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  130. A solution for all IDs for all time by Un+pobre+guey · · Score: 2, Funny
    varchar2(1152921504606846976)

  131. The world's going to end by cardshark2001 · · Score: 1
    Because the manufacturers won't be able to fix this problem, and they'll stop making cars. Really!

    Anybody else got a feeling that they're just complaining about it so they can charge more for their cars without invoking the Sherman acts?

    "We sold so many cars we're running out of numbers for them all."

    Boo-hoo. I need a tissue.

    --
    WWJD? JWRTFA!
  132. 64 bit integers by rjshields · · Score: 1

    'Longer codes would require a major overhaul of computer systems...'

    The developer should have considered using a long instead of an int.

    --
    In this world nothing is certain but death, taxes and flawed car analogies.
  133. 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.
  134. What is the big deal? by be951 · · Score: 1
    Some tidbits from the article:

    The first and second positions are the country and manufacturer, respectively. The U.S. has three digits for the country code, and 31 possibilities for the manufacturer (ten numeric digits, plus 26 letters minus I, O, Q, U, and Z since they could be mistaken for numbers or another letter). So do we have over 90 manufacturers? I'm thinking it is around 3 (separate divisions such a Chevrolet and Pontiac are represented by the next position). And speaking of that, each company can have 30 or so divisions or vehicle types or classes. Positions 4-8 are for vehicle features like body style or engine type. Plenty of room there. Ninth position is a check digit. Not clear if this could be a sticking point. Probably not. Next digit represents the year. This rolls over every 30 years, but that should not be much of an issue. The next position is for the manufacturing plant of origin. Again, 31 possibilities for each division of each company. The remaining six digits are the serial number, which could allow up to a million cars per plant per year, unless a company/division assigns more than one code to a given plant. Now, how many millions identical (remember, different engine, transmission, etc... differentiates the VIN) units does even a flagship brand like Ford produce in a year? I think it is safe to say that it is less than 30 million. Especially given that "Automakers build 60 million cars and trucks every year...."

    I also found this amusing: "Of 1,056 WMI [first three positions of the VIN] codes available to U.S. manufacturers, 594 remain, according to SAE. " Oh, no! That's less than half! Wait, no it isn't.

  135. I fail to see the problem. by Raptor+CK · · Score: 1

    Aside from the idiocy of a system limited to a wraparound in the year 2011, If we're risking an overlap beyond that, then we have proven our idiocy as a consumer culture.

    31 countries.
    31 Manufacturers.
    31 Vehicle types.
    31^5 Body style/Engine type/series/etc combinations per vehicle type.
    In one of 31 potential plants. Each with a run "limited" to 31^6 of this specific combination.

    If one plant is spewing out over 800 million of a specific SUV each year, there's clearly a level of mental retardation in our society that should have left us all resembling monkeys who have barely discovered fire.

    Admittedly, some reallocation is in order here. The addressing system is slightly out of whack relative to the actual production output of any given plant. However, I have a solution if that can't be done:

    Hey, manufacturers! Listen up! STOP MAKING SO MANY GODDAMNED CARS.

    (That said, the problem is said to hit at the end of the decade, which is right on schedule, as many posters have noted.)

    --
    Raptor
    "Procrastination is great. It gives me a lot more time to do things that I'm never going to do."
  136. Cry me a river by Mr+Z · · Score: 1

    They mention in the article that the current system, put in place in 1981, was designed to last 30 years. That's 2011. Now they say they'll run out by the end of the decade. That's 2010. Wow, a whole year short of plan?

    Also, it sounds like with very minor tweaks, they could get another 30 years out of the system. Beautiful!

    If car makers could step back from their ego slightly, and use more than one "division" character for each division, you'd get even more encoding space. The "division" is basically a subcategory of manufacturer, and is encoded in the 3rd digit. For US VINs, a 'G' in the second position is GM. A '2' in the third position means 'Pontiac'. What if they used more characters there to also mean Pontiac? Ditto for GMs other divisions? Heck, what if we used multiple 'make' designations for GM? Why only "G"?

    So what's the issue again?

    --Joe
  137. Hahahahahah! by Otto · · Score: 1

    Are you serious? The guy who wrote the original application quit *ages* ago. If everybody got fired for making "magic numbers" in the applications, there'd be no freakin' applications! There'd be no programmers, no software, nothing.

    You show me an application without magic numbers, and I'll show you a coder who's out of work and bored and coding something without a deadline. I'll also show you a program that few, if any, people actually use.

    Welcome to the real world, friend.

    --
    - 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.
    1. Re:Hahahahahah! by Fweeky · · Score: 1

      Er, sorry, but it's not a lot of work to define a constant and use it where you would have put a number. Not even if you're in a hurry.

      Remind me not to hire you to maintain our 100,000 user web application.

    2. Re:Hahahahahah! by WNight · · Score: 1

      That's the problem. People assume it'd take too long to do things right. Hell, Extreme Programming preaches doing nothing except the absolute minimum required to make it work right now - future changes can incorporate the cost of modifying the staticly coded program.

      But, once you've been programming for a few years, usually, you realize that it's just as fast to put 'PI = 3.141592;' at the top of the program than it is to use it everywhere, and less error prone. It's also easier to do this with database field widths and everything. When you code for variable widths you're always thinking about the idea of making the data fit, not just blindly accepting. You avoid whole classes of bugs like buffer overflows because you're thinking about the data.

      Really, doing it right has a much lower cost in the end, for any non-trivial application.

    3. Re:Hahahahahah! by Otto · · Score: 1

      I think you missed my point...

      I agree that using constants, even if it's just #define's, is a good thing. But the whole concept of firing somebody because they didn't is silly. That sort of stuff rarely gets noticed. Much more critical bugs often go by unchecked, and you're expecting people to not only notice but fire people over something like not using constants? Come on, pull the other one, it's got bells on.

      --
      - 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.
    4. Re:Hahahahahah! by Fweeky · · Score: 1

      The concept is silly because it was largely a joke. At least the thread subject got it ;)

  138. Just like book numbers by Aidtopia · · Score: 1

    ISBN numbers, which are intended to uniquely identify books, are also running out. This is due in part to the boom in self-publishing. Like VINs, some digits are reserved to identify the company (publisher), others are a serial number doled out by the publisher, and there's a simple check digit to catch typos, transpositions, etc.

    The ISBN format was a little more flexible, though. The publisher identifer could be a variable number of digits. Big publishers got short codes, and thus more digits for the serial number. Small houses got long codes and just a few digits for the serial number. Thus a lot more of the identity space can be used.

    But the internet self-publishing (or print-on-demand) companies (e.g., iUniverse, FirstBooks, etc.) were late to the game, so they didn't get the short publisher codes like other prolific houses. In the end it works out, as you can assign multiple publisher codes to a publisher that prints more titles than originally allowed for.

    The self-publishing companies are cranking out hundreds of titles a year. Unlike a traditional publisher, there's no drawback to setting up a title that may never sell since the author pays these costs. This is rapidly accelerating the depletion of code numbers. And since self-publishing companies never take books "out-of-print," they can't recycle serial numbers in their space. (I'm not certain recycling is allowed in the system, but you could imagine doing so for books that are long out-of-print.

    Obviously, there are advantages to having meaning built into the number rather than using a strictly serial number. Auto insurers can get most of what they need to know about the car out of the VIN (manufacturer, model year, body type, etc.). Book sellers can figure out which publisher's catalog to check by looking up the beginning of an ISBN. But the trade-off is severely limiting flexibility for when the identity space is depleted (as with VIN and ISBN), or the assumptions change radically (as with ISBN in a self-publishing world).

  139. That's awful shortsighted of you. by raehl · · Score: 1

    How long should the VIN have been?

    Would making the VIN longer for the past 30 years so we didn't have to update it now have been worth the increased costs of data storage, longer VIN printing, data entry, etc, over the past 30 years? Keep in mind that data storage was at a premium in 1980 - every bit counted. Not spending money on that storage in 1980 was probably worth the hassle of expanding the VINs now.

    We could make VINs 1,000 digits long, and we'd still be able to use them on starships, but it'd be pretty stupid to do so.

  140. From an ex-auto manufacturer IT guy by rebill · · Score: 1

    The major problem with using lower case letters is a physical one - the VIN plate on your vehicle is a piece of stamped metal of a a specified-by-law size and shape, with a specified-by-law font that ensures that Mr. County Sherriff can clearly read what that thing says without making mistakes.

    The mechanics of stamping a piece of metal precludes fancy fonts - and lower case letters will tend to end up smears, rather than clear text.

    Besides, a lot of the software will helpfully uppercase the letters for you (since it cannot be lower case, yet most keyboards these days are multicase), so you're still right back to the "expensive to update all the software" problem.

    There is a A *MUCH* simpler solution.

    Those 17 positions include a lot of detail about the type of vehicle/engine, et cetera. Even *one* difference is enough to change that position and the checksum characters, which will make the VINs unique. So, any auto manufacturer at risk of overlapping VINs,

    1. Gets the list of VINs that were used on the last cycle
    2. Compares their current vehicle line to see if they would have any "oops, they match" situations
    3. If they find any, they shuffle the vehicles around, until there are no more matches.

    Everything hinges on the 5 characters in positions 4 through 8 (body style, Engine type, model, series) along with the checksum in position 9. The manufacturer has positions 12 through 17 to play with, and 31 possible values to put into each position, or 31^7 possible serial numbers that they can use in a year.

    In other words, for a guaranteed overlap, that manufacturer would have to build 27 billion identical cars in a single year to exhaust the entire serial number space.

    That's what, 4 cars for every human on the planet?

    They will scream because the vehicle that they want to be serial number "A00001" has to be shunted to serial number "A00003", but in the grand scheme of things, it can be dealt with by creative assignment of the serial number range.

    --

    Chivalry is not dead, it's just frequently misspelt. - M. Langley

  141. Why a 30 yr limit? Did they work for Tyrell Corp? by vdo2000 · · Score: 1

    Or did the engineers want to make sure they had a job in 30 years for the redesign?

  142. VINs are NOT necessarily unique... by ayahner · · Score: 1

    A few years back, according to Discovery Channel's FBI Files or New Detectives (i forget which exactly), there was a Canadian car dealer who would steal high-end cars in canada, and replace their VIN tags with those from the same make/model in a junk yard.

    Eventually, he needed more VINs and sent a few scouts to US car lots to record VINs from US cars right off the lot.

    They finally prosecuted him, but they estimate that there are ~$7 million worth of high end cars that they apparently can't (or are too lazy) to locate.

    It's obvious that there is no central VIN tracking system, or the FBI would have used to to search for duplicates between the US and Canadian registries.

  143. What's the big deal? by TommydCat · · Score: 1
    "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."

    That would be.... 2010?

    "The Society of Automotive Engineers, which established the existing VIN system in 1981 and expected it to last 30 years, has formed a committee to address the impending shortage." At least until 2011? Did someone forget to update their timeline?

    --
    This comment does not necessarily represent the views and opinions of the author.
  144. Easy solution... by rulethirty · · Score: 1

    Call in the IPv6 guys to fix everything up.

  145. When they ran out of telephone country codes... by rfc1394 · · Score: 1
    The telephone network divides the world into 9 regious. 1 is North America above Mexico, 2 is Africa, 3 and 4 are Europe, 5 is Mexico and South America, etc. When there were too many countries being issued country codes in the Public Switched Telephone Network (PSTN) in certain regions than there were available codes, they just borrowed some from the underused regions (e.g. Africa.) This is why Greenland, whose country code should start with a 3 or 4, has the number 299.

    Since the obvious solution is much cheaper than any other choice (cost essentially zero vs. billions of dollars), the automobile industry will obviously do the same thing the telephone industry did, borrow numbers from where they aren't being used.

    The newspaper article gave the example of what they can (and almost certainly will) do to fix the shortage of numbers: borrow manufacturer codes from countries that do not now and probably won't ever have automobile manufacturers, like Botswana.

    --
    The lessons of history teach us - if they teach us anything - that nobody learns the lessons that history teaches us.
  146. I vote for recycling by MrLint · · Score: 1

    Im not a terribly big fan of cob jobs, but im thinking about why this may not a problem. What would stop them from reusing old VIN numbers in the serialized portion of the code? If the rest of the code is still accurate there should be no full code dupes. And if for some reason there was. The state of license and the plate number would handle the possibility of dupes.

    The only thing left over would be destroyed, disassembled or un-IDed cars, im wondering if this is a large enough number to be concerned about.

  147. not just VINs car makers are running low on... by Anonymous Coward · · Score: 0
    while running out of VINs in the near future may be problematic, I think the fact that we're running out of oil is perhaps a bigger problem.

    Then again, though I guess solar-powered cars will need VINs, too...

  148. different mindset different results by perlchild · · Score: 1

    anyone notice some numbering systems aren't very resillient, and some others are?

    When are we expected to run out of MAC addresses?

  149. Metric? by Anonymous Coward · · Score: 0

    OT. If they have to go through that much trouble anyway, why not seize the opportunity and convert to Metric, too!? Only half ;-) Once the manufacturers start, the rest of the country will follow...

  150. What problem? by Anonymous Coward · · Score: 0

    This can not be a problem. A 17 digit code with each digit 0-Z allows 17^36 or 10^44.3 Each person on earth can own more cars than there are grains of beachsand on earth! Or buy one car each microsecond until the end of the SUN!

    This is true even if half a dusin of the positions are limited to be a number.

    (I am guessing 1000 grains of beachsand fills a ml, and that all beaches on earth contains 40 million cubic kilometer of beachsand, and that the Sun will burn for 5 trillennia)

    1. Re:What problem? by Russellkhan · · Score: 1

      It's not quite that simple. A good number of the positions are pre-determined to indicate manufacturer, country of origin, production year, etc. Also, the letters I, O and Q are not used, for the sake of clarity.

      All in all, I believe the last 8 digits are the ones that are changed without predetermined meaning - and of those, the last 4 are always numeric.

      I'm not about to do the math to figure out how many numbers are available, but am interested enough to appreciate it if someone else cares to figure it out and post it.

      Hmm, just thought of something, since manufacturer and model year are part of the VIN, this would seem to indicate that manufacturers are producing too many cars per year (for the VIN system) - though I believe there's some overlap - IIRC, only one digit is used for model year, so I guess eventually the same numbers gets re-used for the year digit.

      --
      Information doesn't want to be anthropomorphized anymore.
  151. patent opportunity by martinflack · · Score: 2, Funny

    Quick, someone patent VIN's with one more digit....

  152. Dwarf Y2k? by Juggle · · Score: 1

    Ok, I know there are a lot of systems that would have to be updated to deal with any kind of change to VIN codes.

    But dwarf Y2K? Come on. Seriously.

    You mean we're ment to believe there are more software applications that deal with VIN codes than there are which deal with dates?

    The issues in finding a single solution to the VIN code itself may be a far more complex issue than the issue of 2 digit vs. 4 digit dates.

    But once a solution has been agreed on fixing it will be MUCH easier (as big of a job as it will be) as there aren't nearly as many systems that will have to be updated.

    --
    --- Juggle juggle@hitesman.com
  153. 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.
  154. We have to rewrite before 2009 anyway ... by tomhudson · · Score: 2, Informative
    We've already got a problem with "recycling" the 10th digit (the year code). In the 2010 model year (2009), vehicles will have the same year code ("A") as vehicles made in 1980. All software that automatically fills in the date based on the 10th digit is going to fail in 2009 - 5 years from now..

    Remember - you heard it here first (PS - I already solved this problem for one piece of software by having a drop-down select box that lets you choose the year range - pre-1980, 1980 to 2008, 2009 and up. User selects the range, and the proper year is calculated. reject vin if <> 17 chars && > 1979. Handles pre-1980 already :-)

    As for the rest, you might want to go here for more information on decoding VINs.

    1. Re:We have to rewrite before 2009 anyway ... by swv3752 · · Score: 1

      You need to patent that. :-P

      Ya think I'm kiddin'.

      --
      Just a Tuna in the Sea of Life
    2. Re:We have to rewrite before 2009 anyway ... by r0gue_ · · Score: 1

      heh :)

    3. Re:We have to rewrite before 2009 anyway ... by tomhudson · · Score: 1
      Darn ... didn't think of that. Anyway, I have 1 year in which to apply, and I've established publicly that I've already done it.

      Anyone out there want to buy the rights?

    4. Re:We have to rewrite before 2009 anyway ... by Anonymous Coward · · Score: 0

      Actually that now makes it public domain, and therefore unpatentable ...

      Thanks!!! :-)

    5. Re:We have to rewrite before 2009 anyway ... by tomhudson · · Score: 0, Redundant

      No, it doesn't. Both the USPTO and WIPO rules allow for 1 year :-)

  155. The VIN designers watch Jetsons too much by rollingcalf · · Score: 1

    They expected the 17-digit VIN system to last 30 years. Only 30 years. So what the hell did they think we would be using for transportation in year 31 -- hovercraft or jetpacks?

    --
    ---------
    There is inferior bacteria on the interior of your posterior.
    1. Re:The VIN designers watch Jetsons too much by DirkDaring · · Score: 1

      Teleportation. Hovercraft and jetpacks would still require a VIN.

  156. Telephone Numbers by Detritus · · Score: 1

    Some people have already had software problems due to the changes in the allowable digits for area codes and telephone numbers. Area codes used to always have 0 or 1 for the second digit. I've seen "clever" code that stored an area code in an 8-bit byte by swapping the first two digits and converting it to an integer.

    --
    Mea navis aericumbens anguillis abundat
  157. Possible solution by Tjp($)pjT · · Score: 1

    Tack the year when they run out onto the end of the VINs, then start back at the beginning of the valid sequences. The concept late model then has semantic context. Then the systems only need to be modified to allow multiple matches for the same VIN, since you'd only store the 17 characters. When a car is reported stolen, the VIN is easy to reconstruct since the last four digits would be one of a few years. And you could determine which of those is the most likely in database lookups pretty easily, and you could always know the correct entry when you know the model year of the vehicle.

    No muss no fuss.

    Then require that by say 2030 all VIN storing systems needed to be replaced with a compliant system for 21 character or larger VINs. Make the VINs with the wrap years as the last four digits (of 21 character VINs) be skipped on new VINs once the new system is online.

    Of course just like Y2K and phone number portability, they'll wait until 2029 to decide to actually implement and petition for more time saying 26 years wasn't long enough...

    --
    - Tjp

    I am in wallow with my inner money grubbing capitalistic pig. ... Oink!

  158. Easy solution - IPv6 by Anonymous Coward · · Score: 0

    Just do the easy solution and give every new car an IPv6 address, using that in place of the VIN.

    Would also make wireless into cars easier.

  159. Worse than Y2K? Hah! by xihr · · Score: 1
    Saying that it dwarfs Y2K is rather funny, since Y2K was ridiculously overhyped as a major disaster and it turned out to be less than a small hiccup. Granted, some of that amelioration was due to people noticing the problem and getting worried about it, thereby actively trying to fix it before it got serious, but still ...

    So here's another MAJOR DISASTER waiting to happen, right? How many people think that this is seriously going to become a major issue in car manufacturing, resulting in a situation that is very difficult and expensive to fix? There are plenty of short-term solutions (many of which we've seen here) that can easily make the problem a non-issue until longer VIN codes are approved and make their way through the system (including database entries as well as the physical machines which stamp the codes).

    Another overhyped non-issue ...

  160. Hmmmfff by HermanAB · · Score: 1

    How the hell can one 'run out of numbers'? It carries on till infinity and anyway, why can't you start reusing numbers after 100 years?

    --
    Oh well, what the hell...
  161. Seems to me they are already screwed by NotQuiteReal · · Score: 1
    Sorry - I peeked at the article.

    In it they explain how the current VIN number is layed out.

    It says the 1st character is the country of origin - with 1,4,5 = USA, 2=Canada, 3=Mexico, etc.

    So, that leaves only 31 other countries? [A-Z,0,6-9]

    I know "J" cars are from Japan, I don't know about German, English, French, Swedish, Italian, Korean, etc. I am pretty sure they make cars in Ireland and Brazil too. I don't know how many places do make cars.

    What happens if a 32nd country wants to make cars?

    Aren't there something like 200 +/- countries in the world [and more all the time!]

    --
    This issue is a bit more complicated than you think.
  162. you're storing your phone numbers wrong by Anonymous Coward · · Score: 1, Insightful

    Have you considered storing your phone numbers in international format(AKA SMS format)? To contact a local number here you would use an example like this:
    +16045551212
    (+=internationl dialing prefix),(1= country code), (604=area code), (5551212=local number).
    Regardless of where on the planet that number is dialled, the tower will determine if it's a local or international call and have it correctly forwarded and billed. The same numbering format used for sending international SMS text messages can also be used for placing phone calls. The 604 area code switched to 10 number dialing a few years back. I had no problems with the transistion.

  163. Retards! by Anonymous Coward · · Score: 0

    You retards who think it's ust a question of changing the metal stamping machines.... We're talking about millions of COMPUTERs worldwide, such as at your local Pep Boys, repair places, tire stores, hardware stores that sell auto parts, EVERYWHERE!! All these would need software upgrades.

  164. Here's the optimal solution: by Anonymous Coward · · Score: 0

    Let's just stop making cars.

  165. What's the issue here? by sunderland56 · · Score: 1

    The article says, "Of 1,056 WMI codes available to U.S. manufacturers, 594 remain, according to SAE.". So the sum total of cars made in the USA to date has consumed LESS THAN HALF the available codes. How about this: all non-gasoline vehicles get a new VIN scheme. Gasoline will run out in 20 years, so that leaves more than enough numbers for current dinosaur-based technology.

  166. From someone who works for GM by Scud · · Score: 0

    And on the equipment that does two out of the three "stampings".

    I work in the Vehicle Systems building at one of GM's assembly plants, and in our building we do the VIN number that you see under the windshield and the stamping on the frame in a "secret" location (right there under the seats).

    The VIN tag that gets riveted to the dash is etched using a special machine made in Germany. Every GM plant in America (and probably every GM plant in the world) has, or will have, two of these machines each.

    The laser etcher shuttles an individual tag into a fixture where it gets etched, and then shuttles it out to a box where they are picked up and brought down to the line. It's all automatic other than the loading and the unloading of the tags.

    IIRC, the guy on the line who attaches these has the extra responsibility of making sure that:

    a) No tags are lost.
    b) Tags are attached in the proper sequence.
    c) No rivets are lost.
    d) Etched side up. :)

    Any missing tags or rivets will bring about the Feds. It's a big deal. Any tags that are mis-etched or damaged are collected and destroyed. Trust me, it's a big deal.

    BTW, the rivets are a special one-of-a-kind design that you can't buy. I suppose the Chinese will counterfeit them any day now...

    The laser etcher gets its sequence from our computers in the sky, very simple. So simple in fact that the addition of a couple extra digits is trivial.

    Will the VIN etcher handle the extra digits? Most likely. We would have had to be dumbasses to buy something that wouldn't.

    As a GM employe (not two e's at the end, which is another story) I put our chances at 50-50.

    As for the VIN on the body, it gets there by way of the pin stamper. The pin stamper has a number of pins that are driven via air pressure and they stamp the crossbrace just behind the seats. This isn't *as* trivial as the VIN etcher, but it really isn't that bad. Basically a wider fixture with a couple of extra pins (and these might not even be necessary).

    As for the engine, I can't speak with any authority on that, I don't even know where it's stamped at. But I imagine that at the most it would require a larger pad to accept the stamping (and no, I don't believe we are going to change our fonts anytime soon so there's no hope for scrunching it down).

    Keep in mind that we make engineering changes all of the time , this really isn't much more than that.

    So from a hardware standpoint (as one of the guys who works on these things) I really don't understand where Mr. Proefke is coming from.

    Okay, so now you know.

    --
    I dream in binary.
    1. Re:From someone who works for GM by BCW2 · · Score: 1

      The engine block is stamped on the right front (speaking from the drivers seat) of GM V8s (the old small block and big block). The block has a pad cast as part of the block that is machined when the surface is done. When the cylinder head is bolted on the pad sticks out below it. When rebuilding an engine you can change the number, just let DMV know about it. I put my own numbers on engines I built for racing in the 70's and 80's.

      The problem will be re-writing all the programs that only allow X number of characters for the VIN. It's not that big a deal to change a line or two in each program, but collectively it's a pain. I doubt if any two states use the same program. I don't think it's as big a problem as the article says.

      --
      Professional Politicians are not the solution, they ARE the problem.
    2. Re:From someone who works for GM by Scud · · Score: 0
      The problem will be re-writing all the programs that only allow X number of characters for the VIN. It's not that big a deal to change a line or two in each program, but collectively it's a pain. I doubt if any two states use the same program. I don't think it's as big a problem as the article says.


      Well... I suppose to a certain degree. We have some (PLC) programs that rely on the VIN number (usually read into the PLC by way of a scanner), but I'm pretty sure that we use our own internal sequence number for almost everything since there is no guarantee that the VIN numbers will be in sequence.

      I didn't know about changing the block number. Interesting :)

      --
      I dream in binary.
    3. Re:From someone who works for GM by Scud · · Score: 0
      The problem will be re-writing all the programs that only allow X number of characters for the VIN. It's not that big a deal to change a line or two in each program, but collectively it's a pain. I doubt if any two states use the same program. I don't think it's as big a problem as the article says.


      Oh, duh!

      You mean after it leaves the plant.

      How silly of me :)

      --
      I dream in binary.
    4. Re:From someone who works for GM by BCW2 · · Score: 1

      The programs for the state DMV's, the insurance companies, and the dealers (new and Used), business that have company vehicles. Did I miss anyone?

      --
      Professional Politicians are not the solution, they ARE the problem.
  167. I cry bullshit by harkabeeparolyn · · Score: 1
    Why do I get the feeling that these are the same sad sacks who can't retrieve data out of a database without crashing the systems and irretrievably losing data?

    I cry bullshit. The only problem here is that no one wants to pay to have this work done. They can't figure out a way to farm it out to India, or make it someone else's problem so now the suits are fretting. The tinny sound you hear is the smallest set of bagpipes in the world playing a dirge for the lost souls in insurance and law enforcement who are learning that hey, maybe we need to keep some IT people stateside after all.

  168. MACs only have to be unique on the same segment. by Ayanami+Rei · · Score: 2, Insightful

    VINs, on the other hand, need to be unique globally.

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  169. Get Your Cars Now! by SEWilco · · Score: 1
    Golly, if it's that serious maybe I should start stocking up on MREs and ammunition

    But please don't stock up on cars.

  170. 17 digits? by mwm158 · · Score: 2, Informative

    If this thing is 17 digits, that leaves 10^17 possible VIN numbers. How many cars are being made?!? 100,000,000,000,000,000 Vin numbers. I think they have adminstration issues in how they distribute these numbers, not a lack of them.

    1. Re:17 digits? by MrRee · · Score: 2, Informative

      Working for one of the major auto manufacturers I feel impelled to respond.

      For us, the 17 digit vin is broken into a number of different fields. The last six numbers are the actual serial number field of the car. There are other fields for year, production facility, model, etc. So in any given year, for any given model, there are 999,999 possible serial numbers that can be produced. The next year, the field containing the year code changes so we have all 999,999 combinations available for use again.

      The problem: We don't really use all 999,999 combinations. Instead, we subgroup them out. 200000 is Ford, 600000 is mercury--you get the point. The solution is make all 999,999 combinations of the last six digits available.

  171. So what? They re-use "keys" all the time. by Anonymous Coward · · Score: 0

    So they run out of "VINs" the state in which the vechile is in, can provide a sticker to relate to the car.

    They have been making the same keys for cars for over 20 years. I have actually opened the wrong car (looked like mine) and started it before actually finding out it wasn't mine because the seat was too far back (and they had kid toys in the back).

    A VIN is important but it can be easily solved. Add more numbers.....weee!

  172. And the PHB response ... by Anonymous Coward · · Score: 1, Funny

    Database geek: "We're running out of VIN's."
    PHB: "Okay, where can we get some more VIN's?"
    Database geek: "Mmmm, Botswana, Zambia, ..."
    PHB: "Works for me! Close the plant and move all the production to Botswana."

  173. I fail to see the importance of this... by CptSkippy · · Score: 2, Informative

    considering that the VIN system is not reliable prior to 1986. Validating a VIN works something like this...

    If VIN is post 1985 then Validate else accept it for what it is.

    Just tweak this code to say...

    If VIN is post 1985 and pre 2005 then Validate else if post 2004 validate with new 2005 algorithm.

    problem f***ing solved. This is just another Y2k scare. VIN information is so botched this won't even register on the radar. I work for an Auto insurance company and I can tell you that atleast 20% of the VINs on our policies are a Hash missing the serial number, plant of manufacter and a couple other useless tidbits. The Insurance Industry only uses the VIN to ensure a valid rate.

  174. Why not just reverse the VIN? by SiliconJesus101 · · Score: 1
    Simply flipping the VIN and starting over with the numbers backwards shouldn't require any real changes. There would just have to be a stipulation that any vehicles built after 20xx have ther VIN's read backwards.

    So, my car (JS23N0B163XXX), if manufactured after 20xx would become (XXX361B0N32SJ).

    Yeah, I know...1970 Challenger R/T VIN....you'll just have to assume the newer 17 digit VIN codes for the newer cars. It would also be quite obvious if you saw a series of numbers only (sequential build) at the beginning of the VIN that it was indeed a flipped VIN.

    --

    "The strong will do what they want, the weak will do what they must."
    -Thucydides

  175. No, silly by A+nonymous+Coward · · Score: 1

    0000:0000:0000:0000:0000:0000:0000:0000

    Maybe you're a Pascal programmer? PL/SQL?

    1. Re:No, silly by leerpm · · Score: 1

      No ::0 means no address, and ::1 is the local loopbac, so you can't start with either of those. You'd have to start with 0000:0000:0000:0000:0000:0000:0000:0002 :)

  176. Recycle them by $exyNerdie · · Score: 1

    Recycle the VIN numbers for the cars that have been destroyed... cars don last for ever...

  177. The answer is simple by SuperBigGulp · · Score: 1

    Stop making cars.

    --
    Someday a Slashdot ID of 177180 will mean something.
  178. barcoding scheme by boisepunk · · Score: 1

    Since many entities that deal with cars use (when availible) the barcode that sometimes accompanies a VIN. We run into the same problem (expanding the spectrum of numerical values) when we make VINs "case-sensitive."
    It's a good idea, and it shows some genious, but the idea wont work. Keep thinking, you just might come up with an idea that will work. That's how lightbulbs too off.

    --
    main(0)
  179. Gremlins & Pacers by codewritinfool · · Score: 1

    Why not re-use codes from Gremlins and Pacers? Those cars were so horrible, those codes deserve another chance.

  180. Actually.... by Anonymous Coward · · Score: 0

    the Geo Prism is nothing more than a rebadged Toyota Corolla. Maybe you think the same of the Corolla, but most people seem to think pretty highly of them. Are you thinking of the Metro maybe?

    Incidentally, the Metro was just a rebadged Suzuki Swift. The Storm, Isuzu Impulse.

  181. Not until 2011 by jgoemat · · Score: 1

    So one of the identifiers is a year. Are we making more and more cars every year so that the other fields fill up? If not, the current system should be good until after 2011, when it would wrap around to 1981 again.

  182. Dwarf Y2k? LOL by jgoemat · · Score: 2, Informative
    Longer codes would require a major overhaul of computer systems that would dwarf the challenges and expenses spawned by the Y2K computer dilemma, said Dave Proefke, chairman of the committee.
    Dwarf the challenges of Y2K? Give me a break... What percentage of computer systems use only 17 characters for a VIN and cannot be changed with an 'alter table' command? Any of them would probably also be the same systems that would have been affected by Y2K. I guarantee dates are used in many more places than VIN numbers are.

    Besides, there are all kinds of ideas in the article itself for getting around it, including many small countries that don't even produce vehicles that use VINs that are taking up a lot of the numbers. Cars build before 1981 didn't even have a standard, each company made up their own VIN numbers. The systems still have to account for those, so we could always go back to the old system. Many cars are out there now with duplicate VINs.

  183. There is LOADS of redundancy by Andy_R · · Score: 2, Interesting

    Characters 4-8 are for body style, engine type, model and series.
    Character 10 is the model year.
    The last 6 characters are the serial number.

    Unless a manufacturer makes more than 999,999 each of about 33^4 different models per year, I don't see the problem.

    --
    A pizza of radius z and thickness a has a volume of pi z z a
  184. Bad management by areve · · Score: 1

    they appear to have a 17 digit alpha numeric id containg a-z 0-9 thats 36^17 id's possible so they could have 286,511,799,958,070,431,838,109,696 cars... Surely with better management they could label every atom in every car with a uniq id!

  185. Big fuss.... by nmg196 · · Score: 1

    In the UK we've changed our license plate (VIN) scheme several times in the last 20 years. It hasn't really been a major problem and each time it happens, it barely makes the news. I'm not really sure what all the fuss is about. Has the US used the same system for a very long time or something?

    As for all the silly suggestions above about using case sensitive characters - in the UK at least, license plates need to be computer readable over CCTV and adding more characters makes this harder. They also need to be memorable to people as well. I can hardly see how a license plate that has strange symbols or mixed case letters is going to be memorable...

    The best bet would to simply use ONLY alphabetical characters and exclude. The problem with numbers is that there are only 10 of them.

  186. Do like the phone company... by Timbo55 · · Score: 1

    ...and just add a "9"

  187. Re: don't forget the handwriting ... redundancy? by pbhj · · Score: 1

    Why not then, in the VinXP (when it comes out) have some sort of redundancy so that errors (such as 1 vs I vs l) could be corrected for?

  188. 2007-01-01 Mon Lithuania joins the Euro(?) by Anonymous Coward · · Score: 0

    YEAAAH. That makes us Critical and Significant, doesn't it? And I thought all we could do was sharpen our teeth and club out Mel Gibson's brains out with golf clubs on every occasion we got.

    --Coder

  189. Easy solution by BeCre8iv · · Score: 1

    Give each new vehicle 2 numbers and 2 linked entrys in the VIN database - thatway you get more combinations without a major overhall of the sys.

    Maybe one number could be stored electronicly so the system cannot just be hacked with an anglegrinder.

    --
    This perpetual motion machine Lisa made is a joke, it just keeps getting faster and faster. - Homer
  190. Its really not that hard! by Anonymous Coward · · Score: 0

    Just build another system from scratch ;-)
    Dont we just loooooove that idea!

  191. Shortsighted Morons! by windowpain · · Score: 1

    "The Society of Automotive Engineers, which established the existing VIN system in 1981 and expected it to last 30 years, has formed a committee to address the impending shortage."

    So they only allowed for enough to last until 2011 anyway! What was going to happen then? What were they thinking? If they had used numbers in the form AA1-AA1-AA1 they'd have had more then 300 trillion freaking VINs. Sure it wouldn't have been as easily decoded by humans but jeez man, these guys didn't even try.

    --
    Insert witty sig here.
  192. The problem is assigning meanings to codes by krislyn · · Score: 1

    This doesn't help solve the problem, but:

    The reason the problem occurred in the first place is because an elementary rule was broken: Never Assign Intrinsic Meanings To Codes.

    Once you start with "this column means this, that column means that", you're bound for trouble. Better just assigning sequential numbers and putting the actual description of the vehicle which was given that number in a database row.

  193. How to cross reference? by TheConfusedOne · · Score: 1

    I would imagine that most VIN handling DB's use the VIN as the unique code right now. So, either you're going to have to introduce a new unique key or something to support the lookup/reference to the overflow table and entry.

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
  194. Proof of ownership. by Anonymous Coward · · Score: 0

    If you think vehicle licensing ISN'T necessary, well then, your car is mine, buddy--prove that it ain't.

    Possesion of the ominous "Manufacturer's Statement of Origin" or "Manufacturer's Certificate of Origin," both aka "senior claim" or "senior title" or "fee simple" or "allodial title" and...

    Sealed contract; lawful (voluntary) transmittal or transfer from previous owner and...

    Charisma to enforce your senior claim based on these two lawful merits.

    It's unscrupulous, dishonerable people like you "ceswiedler" that compel honorable people and citizenry to incorporate marks of another's creation such as VIN or SSN or Driver's License or Marriage License et al. It is unlawfuly to force anyone to use anyone else's registry to "identify" any object within another's records; it is always just a form of extending jurisdiction and thereby a populous to tax for recurring uneffectual services; incurred in scope of a principality and sovereign.

    Like I said, you are dishonerable: a peice of shit that can't be trusted to hold someone else's purse or prized possesions responsibily, or your own God-given virginity.

    Perhaps you should be asking yourself whether you can prove that you are not a slave to anyone or are a freeman? Because you advocate another's services, implying you are irresponsible to your actions and implicating adversly slander and libel unto your fellow that desire not benefice from another's registry service or record.