It was identified by Mr. Randy Reed of NAVSISA during the 31 Aug ? 1 Sep 2010 DPAS CCB that IUID numbers created in the IUID Registry and copied over to DPAS could not be printed by DPAS, as insufficient information is captured between DPAS and the IUID Registry. That only the following situations would enable DPAS to print the IUID 2-D data matrix: 1. Previously scanned IUID labels that were associated to an Asset ID in the scanner and uploaded into DPAS. 2. DPAS-generated UID1 UII based on NAVSISA DODAAC and Asset ID (e.g. N0367MDA1000001). Scenario: The Missile Defense Agency (MDA) currently has over 6,000 IUID numbers assigned in DPAS that were generated in the IUID Registry and copied over to DPAS using the DPAS UII Query tool. As a result of the above criteria, none of the assigned UII (UID1, UID2, VIN, or ESN) can be printed by DPAS. Recommended solution: Can a determination be made to see if the relevant key data points can be extracted from the IUID Registry (DODAAC/CAGE/DUNS/etc., Part Number, and Serial Number) to facilitate DPAS being able to print the UII label from non-DPAS generated sources? Customer priority: 2