DASN (ELM)'s IUID Education and Training Series

IUID Registry Data Submission Details

1

IUID Center Representative NSWC Corona, IUID Center

30 MAY 2013

Housekeeping

2

• 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 iuid.helpdesk@dla.mil

• Questions will be answered as time permits

Today’s Topics

3

• What is the IUID Registry

• Obtaining and Understanding the Requirements

• XML file structure

• Flat file structure

• Loading Information into the Registry

• Common Pitfalls

• Additional Resources

• Questions

What is the IUID Registry?

4

According to DFARS 252.211-7007 Reporting of Government-Furnished Property.

Registry Snapshot - Statistics

5

Data Requirements

• It depends…

6

LEGACY or NEW?

Contractor or Government

System?

Updating?

End Product (Parent)

or Embedded (Child)?

Adding?

Construct 1 Construct 2 w/ PN Construct 2 w/ Lot

IUID Equivalent

Custody Change Custodian Change Ownership Change

Lifecycle Event Mark Set Change

Part Number Change Type Designation

Change Configuration Change

Government Furnished Property?

From WAWF?

Data Requirements

7

Data Elements

Name*

Organization*

Phone*

Email

Contact

All files need these basic elements

Administrator DODAAC*

System Name*

System Version*

System Identifier

Administrator DODAAC*

DITPR Number*

SystemName

SystemVersion

System Identifier

ContractorIdentifier* a CAGE Code or a DUNS Code

System Name*

System Version*

System Identifier

Government System w/ DITPR #

Government System w/o DITPR #

Contractor System

* means the data is required

All files will have one of these three:

Data Requirements

8

ContractNumber*

ContractNumberType*

PrimeContractorIdentifier*

AcceptanceCode*

AcceptanceDate*

AcquisitionCost*

ClinSlinElin*

Description*

ForeignCurrencyCode*

ShipToCode*

UnitOfMeasure*

UII*

UidType*

ContractOrderNumber

BatchLot

CurrentPartNumber

CurrentPartNumberEffectiveDate

EnterpriseIdentifier

IssuingAgencyCode

ManufacturerCode

ManufacturerIdentifier

OriginalPartNumber

SerialNumber

Warranty

Pedigree Information

ConditionCodeType

ConditionCode

ConditionCodeEffectiveDate

Either DoDEntity or FederalEntity*

EffectiveDate*

BaggedOrTaggedCode*

Contents*

EffectiveDate*

AddedOrRemovedCode* (in this case, "A")

MarkerCode*

MarkerIdentifier*

MediumCode*

Set*

Value* (optional if CONTENTS = "UID")

TypeDesignationMethod

TypeDesignationValue

EffectiveDate

ConditionCode

Item Owner

Mark

TypeDesignation

* means the data is required

Multiple data elements enclosed

by a thick bordered box means the

data elements in the box must all

be provided if any of them are provided.

Legend

Adding “New”, “End Product”,

“Construct 1” items, no GFP.

SpecialToolingOrTestEquipmentStatus*

EffectiveDate*Special Tooling

Data Requirements

9

ConditionCodeType

ConditionCode

ConditionCodeEffectiveDate

Either DoDEntity or FederalEntity*

EffectiveDate*

BaggedOrTaggedCode*

Contents*

EffectiveDate*

AddedOrRemovedCode* (in this case, "A")

MarkerCode*

MarkerIdentifier*

MediumCode*

Set*

Value* (optional if CONTENTS = "UID")

TypeDesignationMethod

TypeDesignationValue

EffectiveDate

ConditionCode

Item Owner

Mark

TypeDesignation

* means the data is required

Multiple data elements enclosed

by a thick bordered box means the

data elements in the box must all

be provided if any of them are provided.

Legend

Adding “Legacy”, “End Product”,

“Construct 1” items, no GFP.

SpecialToolingOrTestEquipmentStatus*

EffectiveDate*Special Tooling

Description*

UII*

UidType*

ContractNumber

ContractNumberType

ContractOrderNumber

PrimeContractorIdentifier

AcceptanceCode

AcceptanceDate

AcquisitionCost

ClinSlinElin

ForeignCurrencyCode

ShipToCode

UnitOfMeasure

BatchLot

CurrentPartNumber

CurrentPartNumberEffectiveDate

EnterpriseIdentifier

IssuingAgencyCode

ManufacturerCode

ManufacturerIdentifier

OriginalPartNumber

SerialNumber

Warranty

Pedigree Information

End Goal Examples

10

See the document:

“OSD_UID_5.0_IUID_Flat_File_Specification.pdf”

See the document:

“UID_Elements_structure_V5.0.2.xlsx”

Deciphering The Requirements

11

See the document:

“OSD_UID_5.0_IUID_Flat_File_Specification.pdf”

See the document:

“UID_Elements_structure_V5.0.2.xlsx”

XML File Structure

12

See the document:

“OSD_UID_5.0_IUID_Flat_File_Specification.pdf”

See the document:

“UID_Elements_structure_V5.0.2.xlsx”

Flat File Structure

13

See the document:

“OSD_UID_5.0_IUID_Flat_File_Specification.pdf”

See the document:

“UID_Elements_structure_V5.0.2.xlsx”

Generic File Structure

^ is used to separate fields

Flat File Structure

14

See the document:

“OSD_UID_5.0_IUID_Flat_File_Specification.pdf”

See the document:

“UID_Elements_structure_V5.0.2.xlsx”

Generic File Structure

Mandatory

Optional

Not used for IUID

Conditional

Alpha (letters)

Numeric (Digits)

Alpha-Numeric (Letters or Digits)

^ is used to separate fields

Making Your File

15

Commercial Software (DADMS ID = 84569)

Excel

Access

Notepad

Filename.xml

Filename.txt

Loading IUID Information into the Registry

16

one-way transfer

Secure File Transfer Protocol

(SFTP)

used to add UII records

to the IUID Registry and

to update existing records

Two way data transfer over the internet

HyperText Transfer Protocol Secure (HTTPS)

used to add IUID records, update existing records

and correct information in the Registry up to 60

days after initial entry. (Non-WAWF, non-updated

(https://iuid.logisticsinformationservice.dla.mil )

Many other DoD systems communicate

through the Global Exchange Service (GEX)

the Wide Area WorkFlow

is one of them.

New Procurements

Legacy

Legacy New Procurements

&

New Procurements

&

Wide Area Work Flow (WAWF) (Screenshot)

17

GEX Options

1. Establish your own account: Set up a GEX account to submit the files by SFTP or HTTPS.

The entry point to this process is to send an email to the helpdesk at iuid.helpdesk@dla.mil requesting assistance setting up a GEX account.

The process takes several weeks to complete so allow for this in your planning.

2. Email “proper & valid” xml files to CRNA_IUID-gateway@navy.mil - Funding issues may compromise this option

- Funding issues have already limited the scope and services.

- File checking can no longer be provided

- Help with finding and resolving data issues within a file can no longer be provided

18

Common Pitfalls

• The information in the file is interdependent and this needs to match.

19

We know

1) This UII is a construct 2

2) The issuing agency code is “UN”

3) The enterprise ID is “512346789”

4) The original PN is “XYX”

5) The serial number is “123”

6) The UII is “DN1234XYX123”

This will fail because if we build the UII

based on 1 through 5 we get:

“UN512346789XYX123”

and this doesn’t match the UII in 6:

“DN1234XYX123”

1

2 3

4 5

6

Mark Sets

20

12-B-3876002Y3 CATALOG NUMBER

3 mark sets

11 marks

10 reportable marks

Mark Sets

21

12-B-3876002Y3 CATALOG NUMBER

3 mark sets

SE

T 1

S

ET

2

SE

T 3

Mark Sets

22

12-B-3876002Y3 CATALOG NUMBER

11 marks

Mark Sets

23

12-B-3876002Y3 CATALOG NUMBER

10 reportable marks

CONTRACT NUMBER

DATE OF MANUFACTURE

FAA CERTIFICATION

HULL NUMBER

INTERNAL ASSET NUMBER

ITEM NOMENCLATURE

LOT NUMBER

MANUFACTURER CAGE

MANUFACTURER NAME

NATIONAL STOCK NUMBER

PART NUMBER

PROPERTY CONTROL NUMBER

SERIAL NUMBER

SERVICE/AGENCY/COMMAND

SUPPLIER NAME

TAIL NUMBER

TYPE DESIGNATION

UID

USA NUMBER

USAF NUMBER

USN NUMBERTh

e o

nly

types o

f m

ark

s w

hic

h a

re r

eport

able

Mark Sets (only the UID is required)

24

12-B-3876002Y3 CATALOG NUMBER

<Mark>

<BaggedOrTaggedCode>N</BaggedOrTaggedCode>

<Contents>TYPE DESIGNATION</Contents>

<EffectiveDate>2009-05-02</EffectiveDate>

<AddedOrRemovedCode>A</AddedOrRemovedCode>

<MarkerCode>D</MarkerCode>

<MarkerIdentifier>1U2R7</MarkerIdentifier>

<MediumCode>HUMAN READABLE</MediumCode>

<Set>SET 1</Set>

<Value>AN/MAK-3</Value>

</Mark>

<Mark>

<BaggedOrTaggedCode>N</BaggedOrTaggedCode>

<Contents>UID</Contents>

<EffectiveDate>2013-05-13</EffectiveDate>

<AddedOrRemovedCode>A</AddedOrRemovedCode>

<MarkerCode>D</MarkerCode>

<MarkerIdentifier>3H234</MarkerIdentifier>

<MediumCode>2D COMPLIANT</MediumCode>

<Set>SET 2</Set>

<Value>D1U2R7F100200300400APMH80312</Value>

</Mark>

<Mark>

<BaggedOrTaggedCode>N</BaggedOrTaggedCode>

<Contents>PART NUMBER</Contents>

<EffectiveDate>2013-05-13</EffectiveDate>

<AddedOrRemovedCode>A</AddedOrRemovedCode>

<MarkerCode>D</MarkerCode>

<MarkerIdentifier>3H234</MarkerIdentifier>

<MediumCode>BARCODE</MediumCode>

<Set>SET 2</Set>

<Value>F100200300400AP</Value>

</Mark>

Registry Helpdesk Contact Information

25

• For help with Registry functionality, special queries or reports please contact: – iuid.helpdesk@dla.mil or 269-961-4745

• For help with your Account please contact: – iuid.accounts@dla.mil or 269-961-4400

• To register for an IUID Registry website account: https://iuid.logisticsinformationservice.dla.mil/brs

• Russell Zinke, Deputy System Manager

Russell.Zinke@dla.mil

• Will Whittington, System Manager

William.Whittington@dla.mil

IUID Resources

26

OSD UID Policy Office Website www.uniqueid.org Trusted site for policy, updates, FAQs, and IUID newsletter

DoN IUID Website https://acquisition.navy.mil/rda/home/acquisition_one_source/item_unique_identification_iuid

MIL-STD 130 (current version is N, Change 1 as of Nov 2012) Marking standards and requirements

DoD Guide to Uniquely Identifying Items (currently v2.5 as of Sep 2012) Business rules, additional guidance for legacy items

Defense Acquisition University (DAU) www.dau.mil Continuous Learning Courses (CLM200, CLE 040) to increase IUID knowledge

IUID Helpdesk iuid.helpdesk@dla.mil

QUESTIONS

&

ANSWERS

27