Army Serial Number Tracker ARSNT 3 Jun 09 Mike Waraksa

2. LOGSA has seven Serial Number systems contained in LIW. Until ARSNT, no SN cross-referencing between systems was being accomplished. ARSNT was designed as a tool that would perform a behind the scenes SN cross-reference between all of LOGSA�s systems contained in LIW WEBLIDB. To date ARSNT includes PBUSE SN records, WEBUIT, and RIDB. LMP and AOAP will be additional enhancements to ARSNT to capture SN reporting for those initiatives. Input screens for WEBUIT and TEDB data functions will be developed as ongoing initiatives for ARSNT as well. LOGSA has seven Serial Number systems contained in LIW. Until ARSNT, no SN cross-referencing between systems was being accomplished. ARSNT was designed as a tool that would perform a behind the scenes SN cross-reference between all of LOGSA�s systems contained in LIW WEBLIDB. To date ARSNT includes PBUSE SN records, WEBUIT, and RIDB. LMP and AOAP will be additional enhancements to ARSNT to capture SN reporting for those initiatives. Input screens for WEBUIT and TEDB data functions will be developed as ongoing initiatives for ARSNT as well.

3. ARSNT is a LOGSA initiative that began about three (3) years ago. The intent of ARSNT is to consolidate and integrate all LOGSA serial number data. Consolidate: Give users one place to access serial number data. Integrate: Show movement between the serial number reporting systems. This is especially applicable to UIT (Unique Item Tracking: small arms, CCI (controlled cryptographic items), RATTS (Radioactive Tracking and Testing System)). Before ARSNT, if an item was shipped from the warehouse to a PBUSE unit, that shipment would stay open in WebUIT -- PBUSE and WebUIT did not �talk� to each other. Since ARSNT has been released, if ARSNT finds a match (SN+NIIN) between PBUSE and WebUIT, the open shipment in WebUIT will be closed. PBUSE, RIDB, UIT, TEDB: These systems feed ARSNT. ARSNT will show exactly what these feeder systems show. For example, if a PBUSE unit is reporting with an invalid UIC or incorrect serial number format, ARSNT will show the data exactly as it appears on the property book. The property book is considered the accountable source. However, ARSNT will �flag� the record so the user is aware of the data discrepancies. (See Reporting Conditions GUI) ARSNT is a LOGSA initiative that began about three (3) years ago. The intent of ARSNT is to consolidate and integrate all LOGSA serial number data. Consolidate: Give users one place to access serial number data. Integrate: Show movement between the serial number reporting systems. This is especially applicable to UIT (Unique Item Tracking: small arms, CCI (controlled cryptographic items), RATTS (Radioactive Tracking and Testing System)). Before ARSNT, if an item was shipped from the warehouse to a PBUSE unit, that shipment would stay open in WebUIT -- PBUSE and WebUIT did not �talk� to each other. Since ARSNT has been released, if ARSNT finds a match (SN+NIIN) between PBUSE and WebUIT, the open shipment in WebUIT will be closed. PBUSE, RIDB, UIT, TEDB: These systems feed ARSNT. ARSNT will show exactly what these feeder systems show. For example, if a PBUSE unit is reporting with an invalid UIC or incorrect serial number format, ARSNT will show the data exactly as it appears on the property book. The property book is considered the accountable source. However, ARSNT will �flag� the record so the user is aware of the data discrepancies. (See Reporting Conditions GUI)

4. ARSNT Phase I was released January 2006. Because of the complexity of the RATTS items (two serial numbers (cell and detector)), LOGSA decided to release separately. There were data integrity issues with TEDB (duplicate serial numbers, etc.) that prevented integration with ARSNT, so LOGSA decided to cleanse the TEDB data first. TEDB data and RATTS data will be integrated into ARSNT as soon as possible. ARSNT Phase I was released January 2006. Because of the complexity of the RATTS items (two serial numbers (cell and detector)), LOGSA decided to release separately. There were data integrity issues with TEDB (duplicate serial numbers, etc.) that prevented integration with ARSNT, so LOGSA decided to cleanse the TEDB data first. TEDB data and RATTS data will be integrated into ARSNT as soon as possible.

5. ARSNT Full Capability ARSNT integrates multiple stovepipe systems. Provides single tool to query serial numbers. ARSNT is the bridge to Enterprise Resource Planning (ERP) Solution which will be the link between all the systems such as wholesale to retail, contractor to depot, retailer to SARSS, etc. Future enhancements include TEDB (Vehicles), and Item Unique Identification (IUID) which is a system of identification that will give eligible items unique marking via electronic readers (bar code) or 2D matrix identifier. ARSNT integrates multiple stovepipe systems. Provides single tool to query serial numbers. ARSNT is the bridge to Enterprise Resource Planning (ERP) Solution which will be the link between all the systems such as wholesale to retail, contractor to depot, retailer to SARSS, etc. Future enhancements include TEDB (Vehicles), and Item Unique Identification (IUID) which is a system of identification that will give eligible items unique marking via electronic readers (bar code) or 2D matrix identifier.

6. Things to Remember NOTE: Annual Wipe Test are no longer required. However, Still needed when doing Maintenance or Shipping.NOTE: Annual Wipe Test are no longer required. However, Still needed when doing Maintenance or Shipping.

7. LOGSA ARSNT/UIT POCs

10. The next series of charts shows some of the query capabilities of ARSNT. ARSNT will show exactly what these feeder systems show. For example, if a PBUSE unit is reporting with an invalid UIC or incorrect serial number format, ARSNT will show the data exactly as it appears on the property book. The property book is considered the accountable source. However, ARSNT will �flag� the record so the user is aware of the data discrepancies. I will be showing you the below Queries�.and will also be showing you some Reporting Conditions where you can retrieve serial/registration number data with discrepancies. The next series of charts shows some of the query capabilities of ARSNT. ARSNT will show exactly what these feeder systems show. For example, if a PBUSE unit is reporting with an invalid UIC or incorrect serial number format, ARSNT will show the data exactly as it appears on the property book. The property book is considered the accountable source. However, ARSNT will �flag� the record so the user is aware of the data discrepancies. I will be showing you the below Queries�.and will also be showing you some Reporting Conditions where you can retrieve serial/registration number data with discrepancies.

11. This chart shows where the user can find ARSNT in WebLIDB The serial number simple query screen is used to perform simple queries on exact matches of the serial/registration number data. You can search by a number of data fields.This chart shows where the user can find ARSNT in WebLIDB The serial number simple query screen is used to perform simple queries on exact matches of the serial/registration number data. You can search by a number of data fields.

12. As shown in the chart, the purpose of the Simple Query is to provide a quick response to the user. No wild card capability. No History records. STUDENTS FOLLOW ALONG WITH PE #1. (We are going to do research on a 5.51mm M249 Machine Gun) SERIAL NUMBER: 114571 Note: If you want to see all Serial/Reg numbers (if there are any reg numbers) you can input only the OWNER UIC in the force value As shown in the chart, the purpose of the Simple Query is to provide a quick response to the user. No wild card capability. No History records. STUDENTS FOLLOW ALONG WITH PE #1. (We are going to do research on a 5.51mm M249 Machine Gun) SERIAL NUMBER: 114571 Note: If you want to see all Serial/Reg numbers (if there are any reg numbers) you can input only the OWNER UIC in the force value

13. This is the Simple Query output. Note the ERROR CODES column. If a serial number record has an error associated with it, there would be a YES in the ERROR CODES column. The user would click on YES and the error code details would be provided�.explain this to class Also do a drill down a NIIN and a drill down on a UIC. Be careful what you query! There are approximately 11M serial number records in ARSNT. For example, the ARSNT GUIs will not allow you to query just a NIIN.This is the Simple Query output. Note the ERROR CODES column. If a serial number record has an error associated with it, there would be a YES in the ERROR CODES column. The user would click on YES and the error code details would be provided�.explain this to class Also do a drill down a NIIN and a drill down on a UIC. Be careful what you query! There are approximately 11M serial number records in ARSNT. For example, the ARSNT GUIs will not allow you to query just a NIIN.

14. This is used for complex queries. The ARSNT Enhanced Query provides more options, such as the LIDB Force Tab and LIDB Item Tab. Also, the user can do a similar match (wildcard) on serial number or registration number. The user can also select a Serial Number System Code to help narrow search. This code groups like items together, such a Small Arms (S), TEDB (T), etc. Current records only with the enhanced serial number query. STUDENTS CAN FOLLOW ALONG USING PE #2 ----CRITERIA----- SERVICE TYPE: ARMY SN SYS CODE: USE �S� for small arms or USE �C� for CCI items�.then click on �>� to move it over to Selected Codes. SERIAL / REGISTRATION NUMBER SEARCH: ALL (or your choice depending on query) SEARCH Matching Strategy: EXACT MATCH (explain similar) ----FORCE-------- TREE AND UNIT TYPE: Unit Selection OWNER UIC: WP50AA (or whatever your using) ------ITEM TREE---- TREE AND UNIT TYPE: All Items This is used for complex queries. The ARSNT Enhanced Query provides more options, such as the LIDB Force Tab and LIDB Item Tab. Also, the user can do a similar match (wildcard) on serial number or registration number. The user can also select a Serial Number System Code to help narrow search. This code groups like items together, such a Small Arms (S), TEDB (T), etc. Current records only with the enhanced serial number query. STUDENTS CAN FOLLOW ALONG USING PE #2 ----CRITERIA----- SERVICE TYPE: ARMY SN SYS CODE: USE �S� for small arms or USE �C� for CCI items�.then click on �>� to move it over to Selected Codes. SERIAL / REGISTRATION NUMBER SEARCH: ALL (or your choice depending on query) SEARCH Matching Strategy: EXACT MATCH (explain similar) ----FORCE-------- TREE AND UNIT TYPE: Unit Selection OWNER UIC: WP50AA (or whatever your using) ------ITEM TREE---- TREE AND UNIT TYPE: All Items

15. This is the ARSNT Enhanced Query output. These are the CCI items you have reflected for UIC WP50AA Note: demonstrate some of the drilldown capabilities Note: In this case there is not�but If there was a �YES� in the ERROR CODE column right click on it and explain the error. This is the ARSNT Enhanced Query output. These are the CCI items you have reflected for UIC WP50AA Note: demonstrate some of the drilldown capabilities Note: In this case there is not�but If there was a �YES� in the ERROR CODE column right click on it and explain the error.

16. The ARSNT Serial Number History Query provides the same functionality as the WebUIT Serial Number History Report. However, all serial numbered items in ARSNT will be shown, to include PBUSE history. STUDENTS CAN FOLLOW ALONG USING PE #3 SERIAL/REGISTRATION NUMBER: Serial Number INPUT 046652 and 046689 OPTIONAL CRITERIA SELECTIONS: 013931973 SN SYS CODE: �C� Note: You can also show them a Small Arms example�SN 7113007 with NIIN 011289936 (shows UIT and PBUSE Hist)The ARSNT Serial Number History Query provides the same functionality as the WebUIT Serial Number History Report. However, all serial numbered items in ARSNT will be shown, to include PBUSE history. STUDENTS CAN FOLLOW ALONG USING PE #3 SERIAL/REGISTRATION NUMBER: Serial Number INPUT 046652 and 046689 OPTIONAL CRITERIA SELECTIONS: 013931973 SN SYS CODE: �C� Note: You can also show them a Small Arms example�SN 7113007 with NIIN 011289936 (shows UIT and PBUSE Hist)

17. This is the results of the Serial Number History Query that provides the same functionality as the WebUIT Serial Number History Report. However, all serial numbered items in ARSNT will be shown, to include PBUSE history.This is the results of the Serial Number History Query that provides the same functionality as the WebUIT Serial Number History Report. However, all serial numbered items in ARSNT will be shown, to include PBUSE history.

18. The Serial Number Simple Query works the same as the Non-RATTS query�but includes RATTS items STUDENTS CAN FOLLOW ALONG USING PE #4 Click Radio Button for CELL SERIAL NUMBER UIC WP50AAThe Serial Number Simple Query works the same as the Non-RATTS query�but includes RATTS items STUDENTS CAN FOLLOW ALONG USING PE #4 Click Radio Button for CELL SERIAL NUMBER UIC WP50AA

19. You have pulled all RATTS Items for that particular UIC. Note: Show ERROR CODES �YES� and explain You have pulled all RATTS Items for that particular UIC. Note: Show ERROR CODES �YES� and explain

20. INTRUCTOR: SME Asked us not to show SERIAL NUMBER AD HOC QUERY: THEY ARE WORKING ON IT>>>SOMETHING IS WRONG WITH IT. The Ad Hoc Query allows users to customize output format. The user could then save in Favorite Reports and run whenever data needs to be refreshed. The AD HOC QUERY REPORT includes the same capability as the enhanced query with the added ability to customize output format and query by document number. The report also displays serial number records with discrepancies/ data anomalies that are flagged by a with an error code upon loading. Again�any corrections must be made at the source. INTRUCTOR: SME Asked us not to show SERIAL NUMBER AD HOC QUERY: THEY ARE WORKING ON IT>>>SOMETHING IS WRONG WITH IT. The Ad Hoc Query allows users to customize output format. The user could then save in Favorite Reports and run whenever data needs to be refreshed. The AD HOC QUERY REPORT includes the same capability as the enhanced query with the added ability to customize output format and query by document number. The report also displays serial number records with discrepancies/ data anomalies that are flagged by a with an error code upon loading. Again�any corrections must be made at the source.

21. Serial Number Reporting Conditions Non-RATTS Now REPORTING CONDITIONS SERIAL NUMBER REPORTING CONDITIONS � NON-RATTS This report identifies serial number/registration number records with discrepancies and data anomalies Any corrections must be made at the source�ie PBUSE�UIT..etcNow REPORTING CONDITIONS SERIAL NUMBER REPORTING CONDITIONS � NON-RATTS This report identifies serial number/registration number records with discrepancies and data anomalies Any corrections must be made at the source�ie PBUSE�UIT..etc

22. Serial Number Tracker Reporting Conditions Criteria Serial Number Reporting Conditions � This report identified serial/registration number records with discrepancies/data anomalies. These records are flagged with an error code upon loading. You can select one or more reporting conditions, and organize the output by various criteria. Any corrections must be made at the source, i.e., property book. STUDENTS CAN FOLLOW USING PE #5 (See PE)Serial Number Reporting Conditions � This report identified serial/registration number records with discrepancies/data anomalies. These records are flagged with an error code upon loading. You can select one or more reporting conditions, and organize the output by various criteria. Any corrections must be made at the source, i.e., property book. STUDENTS CAN FOLLOW USING PE #5 (See PE)

23. Serial Number Tracker ReportingConditions Report Left click on error codes and explain each one.Left click on error codes and explain each one.

24. PBUSE Duplicate Records Explain difference in these two reports�.HOWEVER, SME has asked us to show the PBUSE DUPLICATE RECORDS rather then the Serial Number Mulit-Claimant report�.. PBUSE duplicate records report identifies duplicate serial number records and duplicate registration number records in PBUSE only�it does not check UIT. PBUSE DUPLICATE RECORDS only pulls records from the PBUSE serial number table, GCSSA_HR_ASSETS. This report identifies exact serial number+NSN duplicates AND modified duplicates+NSN in PBUSE only!! Modified duplicates are serial numbers that contain DUP or special characters, and match an "unmodified" serial number record (without DUP or special characters). For example, 1234DUP and 1234; or 1234 and (1234). This report will return any serial number containing 'DUP', even if there is not a match. This report also identifies duplicate and modified REGISTRATION_NUMBERS in PBUSE. Also explain Serial Number Multi Claimants how it matches between UIT and PBUSE�. SERIAL NUMBER MULTI-CLAIMANTS identifies exact serial number matches between UIT/UIT, UIT/PBUSE, and PBUSE/PBUSE. This report does not identify modified serial number matches or registration number matches. Explain difference in these two reports�.HOWEVER, SME has asked us to show the PBUSE DUPLICATE RECORDS rather then the Serial Number Mulit-Claimant report�.. PBUSE duplicate records report identifies duplicate serial number records and duplicate registration number records in PBUSE only�it does not check UIT. PBUSE DUPLICATE RECORDS only pulls records from the PBUSE serial number table, GCSSA_HR_ASSETS. This report identifies exact serial number+NSN duplicates AND modified duplicates+NSN in PBUSE only!! Modified duplicates are serial numbers that contain DUP or special characters, and match an "unmodified" serial number record (without DUP or special characters). For example, 1234DUP and 1234; or 1234 and (1234). This report will return any serial number containing 'DUP', even if there is not a match. This report also identifies duplicate and modified REGISTRATION_NUMBERS in PBUSE. Also explain Serial Number Multi Claimants how it matches between UIT and PBUSE�. SERIAL NUMBER MULTI-CLAIMANTS identifies exact serial number matches between UIT/UIT, UIT/PBUSE, and PBUSE/PBUSE. This report does not identify modified serial number matches or registration number matches.

25. Duplicate Criteria TO FIND PBUSE DUPLICATE RECORDS : STUDENTS CAN FOLLOW ALONG USING PE #6 -----CRITERIA TAB------ REPORT TYPE: ALL SN SYS CD = >> -----FORCE TREE------- TREE and UNIT TYPE: Unit Selection ENTER UNIT SELECT UIC from Dropdown and type: W8AM and click Add ----ITEM TREE TAB--- ALL ITEMSTO FIND PBUSE DUPLICATE RECORDS : STUDENTS CAN FOLLOW ALONG USING PE #6 -----CRITERIA TAB------ REPORT TYPE: ALL SN SYS CD = >> -----FORCE TREE------- TREE and UNIT TYPE: Unit Selection ENTER UNIT SELECT UIC from Dropdown and type: W8AM and click Add ----ITEM TREE TAB--- ALL ITEMS

26. PBUSE Duplicates This report contains the PBUSE duplicates. LEFT CLICK ON THE UIC TO GET THE PBUSE POC INFO This report contains the PBUSE duplicates. LEFT CLICK ON THE UIC TO GET THE PBUSE POC INFO

27. Multi-Claimants SME has asked us to show the PBUSE DUPLICATE RECORDS rather then the Serial Number Mulit-Claimant report�.. THIS PAGE IS HIDDEN FOR THIS BRIEF: WILL NORMALLY SHOW SERIAL NUMBER MULTI CLAIMENT� SME has asked us to show the PBUSE DUPLICATE RECORDS rather then the Serial Number Mulit-Claimant report�.. THIS PAGE IS HIDDEN FOR THIS BRIEF: WILL NORMALLY SHOW SERIAL NUMBER MULTI CLAIMENT�

28. SN in UIT, but not in PBUSE after Conversion UIC Converted to PBUSE � Serial Number in UIT but not in PBUSE. This report identifies PBUSE UICs which have serial numbers in UIT but these serial numbers are not being reported in PBUSEUIC Converted to PBUSE � Serial Number in UIT but not in PBUSE. This report identifies PBUSE UICs which have serial numbers in UIT but these serial numbers are not being reported in PBUSE

29. This query will show you a discrepancy report between a UIC in PBUSE and UIT. It will show that you have PBUSE UICs with Serial numbers being reported in UIT and not being reported in PBUSE. STUDENTS CAN FOLLOW ALONG USING PE #7 CRITERIA TAB � MAKE SURE �EXCLUDES TRAK S� IS CHECKED FORCE TAB: UNIT SELECTION: UIC = �WSS0� or WSS0AA� (can explain this to students) This query will show you a discrepancy report between a UIC in PBUSE and UIT. It will show that you have PBUSE UICs with Serial numbers being reported in UIT and not being reported in PBUSE. STUDENTS CAN FOLLOW ALONG USING PE #7 CRITERIA TAB � MAKE SURE �EXCLUDES TRAK S� IS CHECKED FORCE TAB: UNIT SELECTION: UIC = �WSS0� or WSS0AA� (can explain this to students)

30. This is the output query report � These items are being reported via UIT (See DATA SRC)�however, they are being reported on a UIC that has already been converted to PBUSE. Needs to be corrected.This is the output query report � These items are being reported via UIT (See DATA SRC)�however, they are being reported on a UIC that has already been converted to PBUSE. Needs to be corrected.

32. LOGSA ARSNT/UIT POCs