A Conceptual Design for a Mobile Application to Support Infield Inventory Activities

Abstract

This paper introduces an inventory assistant being developed at Oak Ridge National Laboratory (ORNL) that we believe will empower users to perform inventory activities at nuclear facilities more accurately, reliably, and quickly. Inventory activities at nuclear facilities are often conducted using pen and paper, which can be time-consuming, tedious, and susceptible to reading or transcription errors. The proposed inventory assistant would replace the paper-based process used by International Atomic Energy Agency (IAEA) inspectors, nuclear facility operators, or verification monitors to complete an inventory of nuclear and non-nuclear items. In general, the inventory assistant would ingest an inventory list, distribute assigned items from the inventory list to one or more mobile devices, enable inventory teams to record their observations in the field, and then enable an inventory lead to integrate and reconcile the observations to produce a final report. The assistant consists of two software components—one for the inventory teams to record observations in the field (In-Field Observations App [IFOA]) and one for the inventory lead to reconcile the inventory list with observations (Distribution, Integration, and Reconciliation Application [DIRA]). This paper introduces the overall workflow of the inventory assistant and describes the IFOA user experience in more detail. To demonstrate the concept, the authors present a use case of IAEA inspectors conducting item counting and tag checking activities of UF6 cylinders at a gas centrifuge enrichment plant with a large number of UF6 cylinders (e.g., thousands). These activities can currently require 30–40 person-days of inspection to complete. Based on experiences during an exercised performed at the IAEA by the ORNL team in 2016, we believe an inventory assistant could allow the IAEA to complete item counting and tag checking using the global identifier or the operator’s barcode in 8–10 person-days of inspection. We would expect other users (e.g., facility operators or verification monitors) to also benefit from significant time savings.