NTBI VIN2 Specification - Revision history

imported>NelsonJenkins: /* NTBI VIN2 2012 */

2012-09-16T00:40:02Z

‎NTBI VIN2 2012

imported>NelsonJenkins: /* Sequential Vehicle Identifier */

2012-09-16T00:33:53Z

‎Sequential Vehicle Identifier

imported>NelsonJenkins: /* NTBI VIN1 2011 */

2012-09-16T00:29:11Z

‎NTBI VIN1 2011

imported>NelsonJenkins at 00:27, 16 September 2012

2012-09-16T00:27:01Z

Show changes

imported>WillSzymborska: Created page with "Since 2011, NTBI products have used the VIN1 and newer VIN2 vehicle numbering systems to identity each specific vehicle within Second Life mostly for role-play reference. It i..."

2012-09-15T20:12:48Z

Created page with "Since 2011, NTBI products have used the VIN1 and newer VIN2 vehicle numbering systems to identity each specific vehicle within Second Life mostly for role-play reference. It i..."

New page

Since 2011, NTBI products have used the VIN1 and newer VIN2 vehicle numbering systems to identity each specific vehicle within Second Life mostly for role-play reference. It is also to simplify customer service by giving an exact model code which can be provided to explain to the manufacturer, vehicles brand, model name, encrypted date stamp (to figure out when this product was rezzed in-world and determine if it is outdated), version number and version style.

==Usage==
Vehicles built by SZYM Motors MFG include the following format:

SZ (MFG code for SZYM), ENT (3 characters for model name),_, AG (version type),14 (internal version number which does not necessarily reflect a date of manufacture or model year),_,(6 characters for date stamp).

(Example: SZENT_AG14_0051OH)

For version numbers of SZYM vehicles, 01 would designate version 1. However this is not to be confused with vehicles produced by Lusch Motors. On Lusch vehicles this would be displayed as "1.0" using a decimal point and having a minor version number marking in the tenths place.

@@ Line 14: / Line 14: @@
 As a result, VIN2 was reworked from the ground up, and a web interface was added for customer support purposes which could "look up" VIN2 codes to decode the make, model, version number, package, and a timestamp when it was rezzed. The numbering specification was also changed to be easier to read without a decoder, since the color and wheel information could be stored on the server so other information could be added.
-An updated VIN3 standard was considered to expand on the numbering scheme and bring the system more in line with the [http://en.wikipedia.org/wiki/Vehicle_Identification_Number ISO 3779 (VIN)] standard as originally intended, but was scrapped in lieu of a small VIN2 bugfix update, as there was no real need to change the system. However, VIN2's web interface will be eventually reworked so [[BluComm]] could potentially use its database to look up VIN2 numbers.
+An updated VIN3 standard was considered to expand on the numbering scheme and bring the system more in line with the [http://en.wikipedia.org/wiki/Vehicle_Identification_Number ISO 3779 (VIN)] standard as originally intended, but was scrapped in lieu of a small VIN2 bugfix update, as there was no real need to change the system.
 ===Lusch Motors Variant===

@@ Line 187: / Line 187: @@
 ===Sequential Vehicle Identifier===
-The Sequential Vehicle Identifier is a 6-digit alphanumeric code that spans across the entire VIN2 system (5-digit for VIN1), and every rezzed vehicle has its own unique SVI. Each SVI can be "tracked" to an originating point where it was rezzed, and at what time. This allows NTBI to collect anonymous usage data, which was previously going to be used to display a gridwide map of rez locations of all NTBI vehicles, but currenly only powers a rez counter, seen in the Prototype mall and various locations in the Celaeno complex. (It should be noted that vehicles aren't "tracked", their rez locations and times are only recorded once to allow for anonymous usage statistics and copybotted vehicle investigations.)
+The Sequential Vehicle Identifier is a 6-digit alphanumeric code that spans across the entire VIN2 system (5-digit for VIN1), and every rezzed vehicle has its own unique SVI. Each SVI can be pinpointed to an originating time when it was rezzed. This allows NTBI to collect anonymous usage data, which powers a rez counter seen in the Prototype mall and various locations in the Celaeno complex. (It should be noted that vehicles aren't "tracked", their rez times are only recorded once to allow for anonymous usage statistics and copybotted vehicle investigations.)
 The SVI is also used to generate the license plate number on first rez.

@@ Line 7: / Line 7: @@
 The VIN1 specification, originally called VOID (Vehicle/Object IDentifier) as it was designed to be used with more than just vehicles and then renamed to VID internally, was first designed in Q2 2011 and was structured around the actual [http://en.wikipedia.org/wiki/Vehicle_Identification_Number Vehicle Identification Number] standards, going so far as to propose an unused country code solely for NTBI. This method also had the added benefit of providing a set of attributes which could be transferred between vehicles to copy general configurations from one car to another. However, it was rejected by [[ac14 Hutson]], who viewed it as too complicated and difficult to implement.
-Revised proposals were submitted by both [[Nelson Jenkins]] and [[ac14 Hutson]], both of whom eventually collaborated on the final specification, which was used mainly as an identification system to track the source of copybotted vehicles (hence using color and wheel codes to verify the integrity of the number).
+Revised proposals were submitted by both [[Nelson Jenkins]] and [[ac14 Hutson]], both of whom eventually collaborated on the final specification, which was used mainly as an identification system to pinpoint the source of copybotted vehicles (hence using color and wheel codes to verify the integrity of the number).
 ===NTBI VIN2 2012===