1. Item Unique Identification (IUID) 101
DASN (A&LM)'s IUID Education and Training Series
Item Unique Identification (IUID) 101
IUID Center Representative
NSWC Corona, IUID Center
29 March 2012

2. Housekeeping Please mute your telephone
Please use the chat box for questions which are critical to the understanding of the presentation
Please submit any question not requiring immediate attention to
Questions will be answered as time permits

3. The World of Unique Identification (UID)
DUID
IUID
APUID
RPUID
SYSUID
EDIPI
OUID
Points to be made:
This brief only considers the unique identification of items.
Notes:
IUID is frequently interchanged with the acronym UID, stemming from the initial release of policy (a few of the early policy memos call for UID). However, it was quickly realized that unique identification covered more than just items. As such, several initiatives were assembled under the UID umbrella, including the re-branding of UID of items into IUID. The other example UID initiatives listed in the slide (note the list is not exhaustive), are:
DUID: Demand Unique Identification
IUID: Item Unique Identification
APUID: Acquisition Program Unique Identification
RPUID: Real Property Unique Identification
SYSUID: System Unique Identification
EDIPI: Electronic Data Interchange Personal Identifier (CAC)
OUID: Organization Unique Identification
This brief only considers the subject of IUID.

4. Item Unique Identification (IUID)
IUID is a system of marking items with globally unique Unique Item Identifiers (UIIs) that distinguish them from all other like and unlike items
UID/IUID is mandated within the DoD for all new item acquisitions, items the government already owns (legacy items), and government furnished property (GFP) meeting specific criteria
Points to be made:
IUID policy is mandated by DoD and NATO
The scope of IUID is across all components of the DoD
The barcodes are affixed to items
Notes:
NATO’s unique identification efforts are active, and additional countries are implementing their own policies, so it’s important to check for updates to the NATO portion of this slide.
IUID within the DoD applies to legacy, GFP, and new acquisition items, including FMS.
NATO
Policy Active STANAG 2290
APUID-1
Netherlands Policy active
Canada Clause Implemented

5. Where is the Requirement?
OUSD (AT&L) Policy Memoranda
IUID Requirement for New Acquisitions, 29 Jul 03
IUID Requirement for Legacy and GFP, 23 Dec 04
IUID Policy Refinement for Secondary Items in Use or in Inventory, 30 Dec 10
DoD Directive
UID Standards for a Net-Centric DoD
DoD Instructions
Serialized Item Management for Materiel Maintenance
Operation of the Defense Acquisition System
Accountability and Management of DoD-Owned Equipment and Other Accountable Property
IUID Standards for Tangible Personal Property
DFARS Prescription and Clauses
Item Identification and Valuation
Reporting of Government-Furnished Equipment in the DoD Item Unique Identification (IUID) Registry
Item Identification and Valuation Requirements
SECNAV Instruction
Implementation of Item Unique Identification within the
Department of the Navy
Points to be made:
IUID policy exists as a stand alone policy and is integrated in policies for various business processes throughout the DoD (e.g., property accountability)
Notes:
Updates to policies are continuous, make sure to check for the latest version. (As of Sep 2011, there are a number of them known to be in the queue for update/revision.)
This list of policies is not exhaustive.

6. What is the Policy for DoD?No
DoD Serially Managed? No
Item Cost ≥ $5,000?
Start
Embedded Item?
Yes
Yes
Yes No
Controlled Inventory?
DoD Serially Managed?
Yes
Yes No No
Mission Essential?
Yes
No IUID Required
Points to be made:
This flow chart can be used to determine which items require IUID compliance.
For new acquisitions, the requiring activity (i.e. the government) must identify and list in the contract those items that require IUID compliance for reasons other than the $5,000 threshold (i.e., DoD serially managed, controlled inventory, mission essential, permanent identification required for other reason(s)).
Notes:
Additional information on this flowchart can be found in the DoD Guide to Uniquely Identifying Items (check for the latest version). No
Permanent Identification Needed? No
Yes
IUID Required

7. What is the Policy for Secondary Items in Inventory or Use?
Unique item-level traceability: the requirement to trace lifecycle management events related to acquisition, property accountability, storage, operation, maintenance, safety, physical security, retirement, and disposal by each individual item.
Secondary item: an item that is not defined as a principle item and includes reparable components, subsystems, and assemblies, consumable repair parts, bulk items and material, subsistence, and expendable end items, including clothing and other personal gear.
Unique item-level traceability requirement at any point in the lifecycle?
DoD IUID Compliance Required
YES
Start
Points to be made:
For legacy secondary items the only criteria for determining IUID compliance requirements is whether there is any requirement for unique traceability at the item level (e.g., do I care that I have this specific wrench and not just this type of wrench).
Notes:
This slide is an outcome of the policy refinement memo issued in December 2010, which extended the date for IUID compliance of legacy secondary items to December 2015.
DRAFT No
No DoD IUID required

8. Automatic Identification Technology (AIT)
1-D Barcodes
Passive RFID Tags
Contact Memory Buttons
2-D Barcodes
EPC RFID Tag
Points to be made:
Suite of AIT includes many technologies, but the only one that meets IUID requirements is the Data Matrix
Notes:
29 July 2003 – DoD Policy requiring IUID (new acquisition, legacy and GFP required by 23 Dec 2004 policy)
2 October 2003 – DoD Policy requiring RFID
Even if items are marked with a linear (i.e. traditional 1-D barcode), they must be marked with a data matrix to be IUID compliant.
Why the data matrix? For a few reasons:
Greater data capacity (over 2,000 characters)
Data recovery capability (can theoretically damage up to 50% of the barcode and still extract the data from the barcode [though in practice the amount of damage allowing for data recovery varies, largely due to the location of the damage, the outer perimeter of the barcode contains no error correction])
Optically read, allowing for a variety of marking methods and materials
Can be read omni-directionally (direction of the mark is irrelevant to scanning)
Data Matrix
PDF417
QR Code
Active RFID Tags
Aztec
MaxiCode
Bullseye

9. Scope of the UII A UII is… A UII is not… a data element
a unique identifier for an item
globally unique
permanent
created by concatenating specific data elements
an enabler for business intelligence
a device for communicating data, such as Radio Frequency Identification (RFID) tags or contact memory buttons
a replacement for the National Stock Number (NSN)
intelligent data that yields information about the item
transferable from one item to another
Points to be made:
The UII is the unique data string that identifies the item (it is derived from what is encoded in the IUID mark, but is not the encoded data verbatim).
The UII is what is required to be permanent and unique per policy.
Notes:
The UII is similar to a social security number for an item. It does not give any specific information about the item, only uniquely identifies the item so information can be identified/associated/gathered from information systems.
Just as your social security number is yours forever, the UII is that item’s forever.
The UII is not intended to replace any existing item information, it should be consider a new data element.

10. Why IUID? IUID provides…
the “data key” to item lifecycle traceability in business processes and information systems
reliable and accurate data for financial, accountability, and asset management purposes
IUID enables…
the discovery and correlation of item information
globally accessible and secure enterprise data
joint paperless management
Points to be made:
IUID provides the key to enable data for a single item to be linked across business process (e.g., financial, logistics, maintenance) to provide a more complete and accurate lifecycle picture.
Notes:
The incorporation of AIT also provides an opportunity to re-engineer business processes, potentially streamlining them and realizing savings of cost and/or time while increasing data accuracy and reliability.

11. An IUID is always a data matrix A data matrix is not always an IUID
Can You Spot the IUID?
Points to be made:
A data matrix is not automatically an IUID. In order to be an IUID, the data matrix must be encoded with the required information in an approved format (discussed in upcoming slides).
Notes:
It is becoming quite common to see data matrices in your daily life, they are used in a variety of industries. You might have seen them on the outside of mail received from the post office, on an ice cream container, on vitamins, on financial statements, among other items you encounter as you go through your day. These are not IUIDs, they are data matrices.
Need to be aware that just because you seen a data matrix on an item does not necessarily mean the item is IUID compliant. It is important to check that the barcode is IUID compliant, unless you have previous knowledge of its compliance.
Each one is a data matrix, but only one is an IUID
An IUID is always a data matrix
A data matrix is not always an IUID

12. A Tale of Two Constructs
What’s an EID? Identifies the organization ensuring the uniqueness of the UII
Construct #1: Serialized within the enterprise identifier (EID) Contains the EID and the serial number (no part number)
Construct #2: Serialized within the part number Contains the EID, part number, and serial number
Points to be made:
There are two constructs approved for use for IUID. As long as the business rules are followed, both of them will result in unique UIIs.
In addition to the construct, the data must be encoded into the data matrix in accordance with one of the three permitted format codes.
The EID identifies the organization ensuring the uniqueness of the UII. For legacy items, it is common for this to be a government DODAAC, not the CAGE of the manufacturer.
Notes:
These are the pieces that transform a data matrix into an IUID.
The three permitted format codes are: 05 (Application Identifiers), 06 (Data Identifiers), and 12 (Text Element Identifiers). Formats 05 and 06 are described and detailed in ISO and format 12 is described and detailed in the Air Transport Association (ATA) Common Support Data Dictionary (CSDD).
There are also a handful of DoD accepted IUID equivalents (e.g., VIN), see the DoD Guide to Uniquely Identifying Items for more information.
An example is provided on the next slide.
Note: The discussion on constructs can derail the discussion quickly and for a long period of time. Be aware of this potential and be prepared tto move the discussion forward.
There are three permitted format codes for either construct
The format code determines the semantics of the encoded string

13. Turning a Data Matrix into an IUID
The right information encoded into the right
kind of mark
Syntax
[)>R/S06G/S7LN41164G/S1PT123G/SS531R/SEOT
Format Code:
Enterprise Identifier:
Data Identifiers:
Serial Number:
Part Number:
Points to be made:
This is one example of an IUID-compliant data matrix. There are many other ways (around 50) to assemble IUID-compliant data matrices.
Notes:
R/S refers to the “Record Separator” character in the ASCII character set. It is a non-printable character with an ASCII value of 30.
G/S refers to the “Group Separator” character in the ASCII character set. It is a non-printable character with an ASCII value of 29.
EOT refers to the “End of Transmission” character in the ASCII character set. It is a non-printable character with an ASCII value of 4.
Common mistake: typing in “R/S” (or any of the other non-printable characters) instead of using the ASCII value. This mistake will cause the data matrix to be not be an IUID.
You do not want to be creating IUID-compliant data matrices by hand. This is only to show you what goes into making an IUID-compliant data matrix. These should be created by an application, program, or information system.
Additional information can be encoded into the data matrix, after the IUID string. We tend to discourage this for a couple of reasons:
The more data you put in the barcode, the bigger the barcode. Scanners have an optimum size for reading the barcode easily (½” x ½” is ideal, but up to 1” x 1” works).
If the additional data entered in the barcode is not permanent data (i.e., it is data that at any point in the lifecycle may change) you are creating a situation where the barcode is going to have to be replaced with an updated barcode and you risk outdated or inaccurate information being used before the barcode can be updated.
Better to have the additional information separate from the IUID-compliant barcode.
Unique Item Identifier (UII) : LDN41164T123531

14. IUID Data Constraints
Must be encoded into an ECC200 Data Matrix barcode
Must include syntax from ISO/IEC 15434
Must include appropriate semantics
Must adhere to data element length requirements
Must use only A through Z, 0 through 9, /, and –
No lower case letters, periods, asterisks, commas, …
UII ≤ 50 characters
UII must be unique across the globe
UII must be “permanent”… forever
Points to be made:
Additional IUID data constraints that are required for IUID compliance.
Notes:
The character constraints are most frequently problematic when it comes to part numbers. If this is a problem for a particular program often suggest using either construct #1 (just avoid the situation entirely) or define a business process for handling the illegal characters (consistent use).
The UII is permanently assigned to the item, meaning it never changes. It stays with the item through modifications, part number rolls, retirement, destruction, and/or death, never to be assigned to another item.

15. Vocabulary Recap – Part I
Unique Identification (UID) is a system of identifying entities to distinguish them from each other. Item Unique Identification (IUID) is a system of marking items with globally unique, Unique Item Identifiers (UIIs) that distinguish them from all other like and unlike items. Unique Item Identifier (UII) is a string of characters which is globally unique. Exactly one UII is assigned to exactly one item.
Points to be made:
Vocabulary refresher
Notes:
Some words and phrases have a particular meaning within the context of IUID.

16. Vocabulary Recap – Part II
Data Matrix is a two-dimensional matrix barcode made up of square modules arranged within a perimeter finder pattern IUID Compliant Data Matrix is an ECC200 Data Matrix encoded in accordance with the semantics of ISO or ATA CSDD, syntax of ISO 15434, and all required data IUID Compliant Data Matrix Encoded String [)>R/S06G/S7LN41164G/S1PT123G/SS531R/SEOT
Points to be made:
Vocabulary refresher
Notes:
Some words and phrases have a particular meaning within the context of IUID.

17. Tips for IUID Specifications in Contracts
Can specify…
…mark shall be read in full sunlight
…mark shall be read by a {fill in name of barcode scanner here}
…mark shall be placed {fill in somewhere convenient to read here}
…mark shall be readable after rubbing the mark with a hydraulic-
fluid-dipped thumb
…mark shall be readable after {fill in some overhaul procedure here}
Cannot specify…
…what data to put into the mark
…what semantics to use
…what construct to use
Points to be made:
Cannot tell the contractor what do, but can give performance requirements/specifications (and advised to).
Notes:
Stories of contractors applying the mark in inconvenient locations (e.g. on the back of rack-mounted equipment); can avoid this with performance specifications (e.g., mark must be readable when the item is in use or installed).
If people state they specify the construct in the contract, they should consider themselves lucky if the contractor is complying because they don’t have to.
DFARS states the contractor has sole discretion on the creation of the contents of the mark.

18. The IUID Registry Program Registry Database Limited to the Program
UNCLASSIFIED
Contains all the data/information the Program needs
Location
Condition
Program
Database
Registry
Points to be made:
IUID information is required to be submitted to the IUID Registry (the specific information required depends on whether the item is new, legacy, or GFP).
The IUID Registry is not a replacement for a program’s database or information system.
Notes:
The IUID Registry is an unclassified system, therefore it does not contain location information or condition information (among other data fields).
The IUID Registry ensures UII uniqueness (once a UII has been registered it rejects any subsequent attempts to register the same UII).
Items must be registered when initially associated to a UII and be updated when certain lifecycle events occur (e.g., part number change, custodianship change).
Custodianship is tracked within the IUID Registry, but only down to the service level on the government side (e.g., Navy, Army) and to the company on the contractor side.
Items can be loaded into the IUID Registry via submission of an XML or flat-file that is compliant to a proscribed schema, or hand entered (this method is highly discouraged).
If assistance is needed with creating an XML file or submitting the file to the registry assistance can be found by contacting the IUID Gateway at NSWC Corona
The IUID Registry allows public access (specific item information must be provided and limited information is returned) and controlled access (more options, including queries).
Limited to the Program
Feeds the IUID Registry
Spans all DoD
Ensures uniqueness
UNCLASSIFIED

19. Business Rules Supported by Barcode Scanning
Points to be made:
This is an example scenario of improving inventory/warehousing practices by utilizing IUID implementation.
The following slides are a small sample of ideas where IUID could be utilized to gain benefits. They may not be applicable to your program, but encourage you to consider your situation, area, program and think about where improvements could be made. Where is your pain? Is there a way IUID can help?
Notes:
This is the first slide of the next few which provide examples of how IUID can be utilized to improve business processes.
This slide uses the example of a warehouse of items where the shelves have also been barcoded. IUID can benefit in several sample scenarios:
Scan when items placed on shelf (updates Automated Information System (AIS))
- Can scan the item’s location and update the AIS with accurate info (don’t need to remember what shelf it was supposed to go on or what shelf it was put on). Lost items must be re-procured, found, or done without.
- Can track weight capacities of the shelf and it’s current capacity, alerting the worker when a shelf’s weight capacity is exceeded.
- Alerts worker when items cannot co-mingle (e.g. code A and non-code A NWRM; chemical incompatibilities; fire safety regs.)
2) Taking inventory shelf by shelf
- catches items that should be out of inventory
- catches items that need processing (forced recall for instance)
- ensures AIS and ground truth are in sync.

20. You Don’t Know What You’ve Got ‘Til It’s Gone
Keeping Track of 4860 Items in a Warehouse Mezzanine
Without Scanning…
Full inventory never completed
Sample data estimates 32.4 hours to complete inventory with 2% error rate
With IUID Scanning…
Full inventory completed in 6 hours
Experience with scanning decreases inventory time to 55 minutes with 100% accuracy
Points to be made:
This is a real example taken from the warehouse at the Naval Surface Warfare Center in Corona (NSWC Corona).
Notes:
At the Measurement Science Technology Laboratory within the Naval Surface Warfare Center Corona, IUID implementation has reduced the time to take inventory and improved its accuracy. Initial time savings of 81.4% were immediately realized when the time dropped from 32.4 hours to 6 hours. Experience with the scanning operation further reduced the time to 55 minutes, a 97% reduction in labor from the original task. IUID and scanning improved accuracy as well, eliminating the 2% transcription errors found in a sample analysis.
Sample data had to be used for inventory without scanning because an inventory without scanning could never be completed due to workload demand (i.e., equipment was always required before an inventory could be completed).
The numbers are actually a little conservative because we couldn't factor in time wasted by transcription errors, breaks, interruptions, etc. in a defensible, rigorous way.
Details: 
The mezzanine is made up of 83 racks, that are roughly 6ft tall, with 5 shelves on average to each rack. There are a total of 4860 boxes containing navy gages distributed throughout the racks and shelves. The shelf contents are organized by gage drawing number where possible. The gage drawing and serial numbers are written on the exterior of each box with permanent marker or painted on using a stencil. IUID labels are placed on three faces of each box to accommodate any orientation of the box on a shelf. A rack containing 50 gages was chosen to calculate the average time it takes to manually write down the box drawing number and serial number along with the shelf location. This information would then be taken to a computer for input into the gage tracking system (GTS) database. A junior warehouseman wrote down the gage drawing numbers, serial numbers for 50 items in 10 minutes. He then traveled from the mezzanine to a computer terminal. Travel time was 2.5 min. Once the GTS was opened to the appropriate change gage location screen he took 10 minutes to input the data. The GTS reported an error stating that 1 record of the 50 gages was "not found in database". The jr. warehouseman then traveled back to the mezzanine to verify the gage drawing and serial number, roundtrip was 5 min. The jr. warehouseman found he wrote down 101 instead of 181 for the serial number pertaining to drawing
Helpful to note that since the boxes are organized on the shelves by drawing number where possible, the jr. warehouseman performing the data entry portion of the task is able to copy and paste the like drawing numbers down the column which increases data entry speed and accuracy. Travel time, interruptions, breaks, etc... were not added into the total time to execute manual inventory for 4860 items.

21. Many of the Benefits are Universal
IUID in Maintenance
You could scan the IUID mark on each test instrument (TI)
36 months
32 months
41 months
6 months
5 months
35 months
You could keep track of an individual TI’s calibration data
Identify poor performers
Lots
Manufacturers
Procedures
Calibrators
Calculate calibration intervals for each specific TI
Look up the model number super fast!
Then pull the calibration procedure as usual.
And calibrate…as usual.
And ship…as usual.
Points to be made:
This is an example of how IUID could be utilized in determining maintenance requirements.
Notes:
This example is taken from the world of calibration equipment. If the focus of the IUID implementation efforts is only on compliance, once items are marked you can look up the model really fast and continue the other processes as usual.
However, if one considers how to gain benefit from IUID implementation, a number of improvements are possible:
Track the calibration data of each test instrument allowing for the identification of poor performers (e.g., lots, manufacturers, processes, calibrators)
Customize the maintenance requirements for each test instrument, potentially reducing maintenance efforts (for items that are still in calibration) and potentially catching equipment out of calibration prior to the maintenance period.
Scanning the standard can check if the standard is in calibration
Scanning the standard can identify the equipment used to calibrate that test instrument and the equipment that test instrument has calibrated (especially useful if a bad standard is identified after the fact).
Although this example is specific to the calibration world, consider how it could be tweaked to your program.
You could scan each standard used to calibrate the TI
Ensure standard(s) in cal cycle
Identify equipment calibrated by bad standards
OR...
Many of the Benefits are Universal

22. Good Data, Good Analysis
Test data analysis found a problem with gyro-scopes used in STANDARD Missiles
Crystallized Deposits
Configuration data identified affected missiles and targeted specific units for testing
Points to be made:
This is another real example from the Naval Surface Warfare Center in Corona (NSWC Corona).
Notes:
The database for STANDARD Missile utilizes a database key, very similar to IUID (it has the same purpose of the IUID, it just isn’t formatted correctly). During test data analysis, there was a problem identified with gyro-scopes used in STANDARD Missiles (seen in the picture on the left). Through further analysis, it was noticed that the problematic gyro-scopes were closely serialized together, that is from the same lot. Configuration data enabled the analysts to identify the missiles affected by the problematic gyro-scopes so a Naval message could be sent downgrading the condition of affected missiles. Location data identified a unit already at the depot to test. Upon testing, the unit failed as expected, and the gyro-scope was removed for further investigation (middle picture). Upon further examination, it was found that the damping fluid used in the gyro-scopes had been oversaturated, and thus had crystallized, preventing the gyro-scopes from functioning properly.
Because the data was accurate and available, the issue was resolved without suffering any damage or casualties, and minimal cost. The problem was able to be scoped and the best solution for the program was executed. All of the affected missiles were downgraded identified for rework upon regular maintenance return. Sections already in the queue for maintenance were identified and the issue resolved.
Collateral Damage = None
Casualties = 0
Misfires = 0
Location data found a convenient unit to test

23. Lessons Learned
IUID is about more than marking and registering concatenated UIIs and their data elements
IUID should be considered in the global context
Not just a DoD initiative
International benefits across government agencies, industry, coalition partners
Identify and involve all stakeholder groups in planning efforts
Groups involved in implementing IUID
Groups that can and will benefit from IUID
Consider existing marking item management practices first
How are items marked today?
Is there available room to add IUID marking on existing data plates and labels?
Ensure serialized item management practices are integrated with IUID
IUID must be the data key for SIM to enable true lifecycle data association

24. Lessons Learned
DoD is responsible for determining which items require IUID in solicitations
Contractors may go beyond IUID requirements
Government must communicate requirements clearly
Contract structure (e.g. use of line items, attachments, exhibits)
Provision of technical authority and documentation when required
For items used in multiple programs, if one requires IUID, all should require IUID
Ensure IUID is integrated into Quality Assurance processes
Quality must be introduced at the front end
Readability and accuracy are crucial throughout the lifecycle
IUID can serve as a forcing function to standardize
Mergers and acquisitions have created complexity in property management
Manufacturers can benefit from lifecycle data as well as government

25. IUID Resources OSD UID Policy Office Website www.uniqueid.org
Trusted site for policy, updates, FAQs, and IUID newsletter
DoN IUID Website
MIL-STD 130 (current version is N as of Mar 2012)
Marking standards and requirements
DoD Guide to Uniquely Identifying Items (currently v2.0 as of Mar 2012)
Business rules, additional guidance for legacy items
IUID Toolkit
Role based roadmaps for IUID implementation
Defense Acquisition University (DAU)
Continuous Learning Courses (CLM200, CLE 040) to increase IUID knowledge
IUID Helpdesk
Valuable resources – check for the most current version of MIL-STD 130 and the DoD Guide to Uniquely Identifying Items (as of Sept 2011 both were in the process of being revised).

26. QUESTIONS & ANSWERS

27. “Hello World!” is encoded into this ECC200 Data Matrix 2-D Barcode
Quiet Zone
Data
(viz. “Hello World!”)
Error Correction
Clocking Pattern
Finder Pattern
Points to be made:
This slide shows the decomposition of a data matrix (note it is not IUID-compliant)
Notes:
The Clocking Pattern provides row and column count information to the reader.
The Finder Pattern provides orientation information to the reader.
The data is always in the upper left diagonal portion of the barcode.
The error correction makes up the remainder of the barcode.
The symbols are optically read so any marking methodology capable of leaving a visible mark will work.
Suitability is dependent on environmental, material and process constraints.
“Hello World!” is encoded into this ECC200 Data Matrix 2-D Barcode

28. ECC 200 Data Matrix Map Hello World! Hello World! ASCII → “e”
= 102
ASCII → “e”
Hello World!
Hello World!
Points to be made:
Each size of data matrix has it’s own similar map, this is only for a 16 x 16.
Notes:
Error Correction is done through Reed-Solomon algorithms.
With 12 EC bytes within the symbol at most 12 blocks with errors can be corrected.
That can be 12 single bit errors in each block or 12 multiple bit errors in each block.
The number of data bytes and error-correcting bytes depends on the size of the data matrix.
A 16 x 16 Data Matrix holds 12 bytes with the data & 12 error-correcting bytes

29. Reading vs. Verifying Marks
The vocabulary of IUID distinguishes “reading,” “verifying,” and “validating”
Reading the mark decodes the text in the mark.
Verifying the mark ensures the quality of the mark meets the standards for contrast, squareness, straight edges, etc.
Validating the mark makes sure all of the correct ASCII characters that ought to be in the mark are in the mark. It makes sure that all the illegal characters that shouldn’t be in the mark aren’t. It makes sure that all other IUID business rules are followed with respect to the mark’s content.
Points to be made:
These words, while often interchangeable normally, have very particular meaning in the context of IUID.
Notes:
Reading is the result of scanning the mark (it extracts the content of the barcode).
Verifying is process that examines the physical characteristics of the mark using a special piece of equipment, called a verifier.
Validating is a process the examines the contents of the mark to ensure all of the rules and standards have been met. Some verifiers do this, as do some applications that have been programmed appropriately (e.g., QCTS)

30. Verification
Verification grades (“A”–“F”) eight characteristics of the mark
Grades of “B” or higher are required to pass the mark
Axial Non-uniformity
Grid Non-uniformity
Unused Error Correction
Fixed Pattern Damage
Points to be made:
Verification examines the quality of specific characteristics of the mark, examples shown on this slide.
Notes:
Verification requires a verifier (about $10,000)
Scanning a barcode is not the same as verifying
Quality requirements are found in MIL-STD 130
Three standards exist for verification per MIL-STD-130N:
ISO/IEC (used for printed labels) 3.0/05/660 (grade of 3.0 or better, with a .005” aperture, with 660 nanometer (red) light)
AS9132 (used for direct part marking)
AIM/DPM (used for both) 2.0/7.5-25/640/(45Q/30Q/90/30T/30S)
where 2.0 grade or better, X-dimension of the application ” ” using 640 nanometer light +/- 20 nm
with illumination 45Q = medium angle four side illumination
30Q = medium angle four side illumination
90 = diffuse perpendicular
30T = low angle two side illumination
30S = low angle one side illumination
Modulation
Over-print
Under-print
Contrast

31. A Readable, Failing Mark
UNDER PRINT
OVER PRINT
CLOCKING PATTERN
DAMAGE
Points to be made:
This is a real label magnified many times.
Though this label scans (i.e. can be read) it fails verification.
Notes:
Why care? Marks can only reasonably be expected to degrade over time. If we want to be to get the most out of the marking effort, we should start with a high quality mark.
FINDER PATTERN
DAMAGE

32. Readability of the Mark
Hard Read
Easy Read
Expensive Readers
Cheap Readers
Contrast
Shape
Cell Size
Reflectance
Points to be made:
There are a variety of methods and materials available to mark items, some of them require more sophisticated technology to read them.
Notes:
It is more difficult to read (i.e. better lighting and/or lenses are required) marks that have low contrast, on a curved surface, with small cell size, or are reflective.
Inexpensive readers can more easily read high contrast marks, marks on flat surfaces, with large cell size, or no reflectance.
This is just some of the factors to consider when selecting a marking method and/or material (other factors to consider include (but not all inclusive): the item’s environment, space available for marking, the marking location).

33. When a Marine Needs to Turn in M118… They Turn in M118
Marines reserialize gages to pass inspection
Accountability is lost
Errors enter the information system
Points to be made:
This is another real example from the Naval Surface Warfare Center in Corona (NSWC Corona).
Notes:
Ground Marines receive infantry weapon gages that are accounted for by serial number. Over time, some of the gages would get switched or mixed. During inspection, some Marines would remove the provided serial number and reserialize their gage(s) to match the serial number they were assigned, so as to meet inspection (an example can be seen in the picture on the left). This practice makes accountability nearly impossible, enters errors into the information system, and often destroys the gage, resulting in unnecessary re-procurement.
In an attempt to curb this practice, IUIDs were laser etched into the gages. Once the initial batch of marked gages (approximately 3,000 out of 35,000) were sent to the field, the practice immediately ceased, even by those who had not received the IUID marked gages.
With IUID Reserialization is No Longer a Problem