1. COMFISCS Item Unique Identification (IUID) April 22, 2009

2. 1 But a UPC doesn’t tell me which Coke I have. An IUID mark is a lot like a UPC.

3. 2 Each IUID mark is Globally Unique. Think SSN

4. 3 Sample of IUID Benefits Provides machine readable data entry ► Reduces human error ► Eliminate data transposition errors ► Increases data accuracy A data matrix won’t scan incorrectly Offers DoD a single identification method ► Ability for disparate systems, that track items differently, to handle the same item and know it’s the same item Enables cradle to grave tracking

5. 4 Back to the Future? “I think the industry has sold itself on a program that offers so little return that it simply won’t be worth the trouble and expense” discussing the potential of the barcode in 1975* *“Scanning Hits a Snag,” Progressive Grocer, December 1975, p. 47

6. 5 Item Unique Identification (IUID) I'm not IUID compliant. What data is in the Data Matrix? [)> 06 25SLDN64267STDMSL33454 Is it IUID compliant?YES What are the different pieces of data within the IUID? [)> 06 25S LDN64267STDMSL33454 What is the UII?LDN64267STDMSL33454 Is the UII registered?NO; How do we know it is unique?

7. 6 The Need Standard, repeatable, reusable processes and tools were needed to address the IUID mandate ► Compliance checking ► IUID marking ► AIS capability updates ► Etc.

8. 7 COMFISCS Tools Quick Compliance Tool Suite (QCTS) Electronic IUID Dashboard (eID) Non-intrusive Front End (NiFE)

9. 8 Quick Compliance Tool Suite (QCTS) Simplifies and expedites IUID marking efforts Enforces IUID standards ► Includes capabilities for 54+ different IUID formats Government owned Web based

10. 9 QCTS (Phase I) Series of marking tools designed to address discrete needs

11. 10 QCTS Features UII registry lookup ► QCTS checks the IUID registry to determine if an item has been registered or not. If an item has been registered, the user is notified. Duplicate registrations are prevented. IUID data extraction ► QCTS parses scanned IUID labels and extracts the information in them. IUID image data extraction ► QCTS can parse and extract IUID information from uploaded photographs and scanned images of IUID labels. IUID raw data string compliance validation ► All IUID labels that are parsed are subjected to numerous validation checks to ensure they comply with the IUID specification.

12. 11 QCTS Features (cont.) UII compliance validation ► All UIIs (as opposed to raw IUID data extracted from marks) are also checked to ensure they comply with the IUID specification. IUID mark generation ► QCTS is capable of generating IUID marks as downloadable images. Item registration ► QCTS is capable of registering items with the IUID registry once they have been marked. IUID Registry XML file validation ► QCTS is capable of validating the format and contents of uploaded XML IUID Registry files. These files contain information about IUID-enabled items that should be registered.

13. 12 QCTS (Phase II) Process framework combines QCTS tools with management functions, enabling organizations to administer IUID marking projects efficiently

14. 13 QCTS Features (cont.) Marking task management ► QCTS allows a large marking effort to be split into manageable chunks which it can automatically assign to marking personnel. Manager overview (Dashboard) ► QCTS enables site managers to see all marking effort progress at their site including marking tasks, label quantities and status, and the progress of individual marking personnel. Wizard Interface for managers ► QCTS relies heavily on Wizard-based interaction with the system to ease use and reduce the need for extensive training. Label management ► QCTS provides support for label management including onsite label printing with IUID capable printers, centralized label ordering and tracking, and template management to simplify label creation.

15. 14 QCTS Features (cont.) Multiple site management ► QCTS is not limited to a single site, but rather can be used across multiple sites simultaneously. Data integration via simple file upload ► Introducing legacy inventory to be marked into QCTS is performed as a simple Excel file upload. Existing inventory systems do not need to permit QCTS to connect to them.

16. 15 QCTS Screenshots

17. 16 QCTS Screenshots

18. 17 QCTS Screenshots

19. 18 QCTS Screenshots

20. 19 QCTS Screenshots

21. 20 QCTS Screenshots

22. 21 Electronic IUID Dashboard (eID) Tool for monitoring legacy IUID marking over an entire organization or command

23. 22 eID Features Command level marking progress overview (Dashboard) ► eID monitors legacy IUID marking over an entire organization or command. The progress each unit has made in their individual marking effort is clearly visible and metrics are easily downloadable. Drill down to any unit below you in the command structure ► Organizations are stored in eID as a customizable organization chart. Metrics can be pulled from any level in the chart. Individual units may also be viewed and reported on, providing any level of detail desired. Simple data entry by file upload ► Unmarked items are introduced to the system as a simple Excel file upload from an existing inventory management system.

24. 23 eID Features (cont.) Fully integrated with QCTS ► Items marked with QCTS are automatically updated in eID No requirement to use QCTS ► While combining eID with QCTS provides a very smooth and efficient marking process, eID in no way requires QCTS to track and update marking data. Marked items may be updated via the same Excel file upload used to initially load them in the system. eID may be used with any IUID marking solution.

25. 24 eID Screenshot

26. 25 Non-intrusive Front End (NiFE) Most legacy systems are not IUID capable IUID could provide some immediate benefit if legacy systems were 2D data matrix aware Modifying legacy systems is expensive, dangerous and usually forbidden Non-intrusive Front End (NiFE) ► Independent software module ► Sits between legacy system and user ► Supports 2D data matrix and scanners ► Translates UII into legacy key data ► Requires no modification of Legacy System ► No software changes ► No Database changes

27. 26 Current Efforts LCS IUID implementation ILO IUID marking opportunity at FISCN IUID marking for SSP during TRAP process BIC marking opportunity WAWF receipt and acceptance with OSD

28. 27 LCS IUID Implementation Initiate and standardize IUID efforts for LCS ► Seaframe ► Mission Modules Leverage QCTS capabilities ► Compliance checking for new items ► IUID marking for previously unmarked items ► Track status with eID Evaluate use of NiFE for existing AISs ► Begin using the UII Serve as a model for IUID implementation for other ship platforms.

29. 28 ILO Marking Opportunity IUID marking during Integrated Logistics Offload (ILO) at FISCN ► Opportunistic marking ► Mark items as part of normal business process Leveraging QCTS capabilities Establish automated metrics Participants include FISCN, MFOM, SSP, PEO SUBS and Core IUID Team ► One Comprehensive Pilot provides shared benefit Processes for SSP TRAP and Marine Corp at BIC appear very similar.

30. 29 OSD – Receipt and Acceptance Integration of automatic data capture for Receipt and Acceptance of IUID required items ► Incorporates QCTS tools ► Handheld computer operating in connected or disconnected mode ► Laptop computer with tethered scanner ► Interfaces with WAWF and IUID Registry All current efforts have common requirements.