LANMAS Annual Users Training Meeting

1. D O C U M E N T A T I O N & I N F O R M A T I O N S E R V I C E S LANMAS Annual Users Training Meeting May 18, 2010 Renaissance Las Vegas Hotel SRNS-MS-2010-00086

2. Agenda Fay Armstrong • Welcome • LANMAS User Training • Implementation at LANL • Overview of LANMAS v3.3 • Future Enhancements/Corrections • Summary

3. LANMAS User Training Fay Armstrong • MCA-214 LANMAS Basic User Training • Scheduled 6/14-6/16 – Host Site SRS • MCA-114 LANMAS Admin Training • Scheduled 6/17-6/18 – Host Site SRS • Training Needs in FY11 • Dates & Host Site

4. Implementation at LANL Benny Martinez

5. Overview of v3.3 Len Bowers • v3.2c released June 17, 2009 • Laundry list of items addressed: • D-23 changes incorporated (Version 2 of XML) • Scrap Code requirement removed • Report classification added • Recommendations of Reports Sub-Committee • Added MBA Intransit, Receipt Measurement & Approve/Decline • 5 Software Error Notifications • 740 Dataset without Obligation activity • Ending Balance problems on MBR (removal of scrap codes) • Approve/Decline (Container Only) • Negative Levels of Review • Receipt Measurement Involving Containers

6. Overview of v3.3 (cont.) Len Bowers • v3.3 • ~60 Issues/Enhancements To Be Addressed • Admin • Limit Checking Maintenance (Limit Type Refresh) • Location Maintenance (Start/End Dates) • Copying Security Permissions (& Resize) • LSAuto • Prevent moves without valid location for account • LANMAS • Recommendations from the Receipt Measurement Sub-Committee • Global Parameter for radio buttons in Adjustments/Mix/Split/Transfer/Rec. Meas. • Expand source document number to 40 characters • Remove TID on Receipt without deleting • Date suppression for DP740 dataset and 741 report

7. Overview of v3.3 (cont.) Len Bowers • VB.NET Phase I • Re-write Admin • No database changes

8. Future Enhancements/Corrections Group Discussion – Led by Fay Armstrong • Receipt & Receipt Measurement Workflow • Item Level Reporting • Others

9. Future Enhancements/Corrections (cont.) Receipt

10. Future Enhancements/Corrections (cont.) ReceiptMeasurement

11. Future Enhancements/Corrections (cont.) Item Level Reporting • Item Definition Suggested Using the NMIA Item definition as Item definition: Item Identifier (ITEM_ID) The Item Identifier is used to link together records associated with the same physical item. A physical item is a single piece or container consisting of one or more nuclear materials (and hence more than 1 inventory record) that satisfy all of the following criteria:* the presence can be visually verified;* there is a unique identification, and cannot be readily divided; and* there is a recorded nuclear material mass.For example, all records associated with a single pit or CSA would have the same ITEM_ID. The ITEM_ID should remain unchanged from one assessment to the next if the item is unchanged

12. Future Enhancements/Corrections (cont.) Item Level Reporting (cont.) Suggested change: Item Identifier (ITEM_ID) The Item Identifier is used to link together records associated with the same physical item. Aphysical item is a single piece or container consisting of one or more nuclear materials (and hence more than 1 inventory record) that satisfy all of the following criteria:* when used in conjunction with piece count, it identifies a group of pieces that is accounted for as a single unit * the presence can be visually verified;* there is a unique identification, and cannot be readily divided (remove this phrase); and* there is a recorded nuclear material mass.For example, all records associated with a single pit or CSA would have the same ITEM_ID. TheITEM_ID should remain unchanged from one assessment to the next if the item is unchanged

13. Future Enhancements/Corrections (cont.) • Offsite Shipments / Receipts and Inventory • Item ID added to Batch Name • LANMAS Implementation • Use Material Records as Item for NMMSS Reporting • Use MatlID as batch name • Other Needs? • Reports • Retain Summary Reporting capability

14. Summary Fay Armstrong