Storeroom Event Viewer
The Storeroom Event Viewer (SEV) is an advanced RFID Inventory Management application that enables a user to rapidly check-out (aka Issue) RFID tagged parts and associate a Work Order to each part during the checkout process. Conversely, it enables parts that have been issued to be returned and put back into Storeroom Inventory. The SEV feeds the TagNet Outbound queue to send those transactions to SAP or whatever the customer system of record is for enterprise inventory, Work Order data is accessed by a direct ODBC link to a corporate Maximo WO database.
This SEV application utilizes RFID and other technologies to streamline the human element to maintain accurate inventory as well as SOX compliance. Previous checkout workflow comprised of manual input to a excel spreadsheet that was then batched daily (more manual input) into SAP screens.
Shown below is architecture:
Integration with TagNet & Customer data
The below workflow steps are visualized in Appendix A.
1.This is where a RFID issue event takes place. The Worker enters the portal and any parts being carried (or pushed on cart) are read and visualized on the Event Viewer.
1a) This is where the tags scanned at the issue read point (portal) are captured by the SRC and posted as XML documents in the local SRC ‘Queue’ sub-folder.
1b) This where the SEV App polls the Queue folder and parses the XML document for each read event cycle. An example of this XML can be seen in Appendix B.
1c) This where the SEV App resolves the tags to their details by calling VERIFYTAGINFO URI. Note: this is exact same behavior as done with TagNet Mobile when it reads tags on one thread and resolves on another. Once the tags have been resolved they are populated in the Carousel Control in the UI.
1d) This where the SEV App accesses the local WO Database to present WO data as done in the mockup. Note: this data will be synchronized to a MySQL or SQL Lite DB by a separate Customer synchronization process.
1e) This is where the worker submits the update (Done button) and those W/O’s associated with each tag are updated in the TagNet repository. The MOVE ITEM URI will be used passing the list of tags including the [Work_Order] UDA value. Note: This creates inventory transactions that moves the material in TagNet to an ISSUE state and updates the tag with UDA association.
2.Presentation Layer. The behavior will mimic that done in the mockup, in this case we are using live data.
2a) This is where resolved tag read events populate the Carousel Control in the UI. Note: there will be a dwell period setting incorporated that will clear the tag list cache if no activity is taken within a selected time period (e.g. 60 seconds).
2b) This is where WO data is displayed in the main list based on the Parent Sub-unit selection in the header ‘swipe’ control. Selecting a list-entry will highlight that row and populate the current Tag Card that is currently set focus.
2c) This is where the worker submits the update and those W/O’s associated with each tag are updated in the TagNet repository. Normal validation rules need to be put in place ensuring that all tags have a WO association before allowing update.During this interchange with the SEV display, the user is prompted to perform certain actions (see table below) by means of Audio based TTS (Text-to-Speech). This TTS is driven by an event driven workflow engine that can be easily mastered by an internal administrator. Additionally, this workflow events can talk to LED strips that provide an additional welcoming and confirmation experience.
How does it work?
The SEV is deployed to a Windows 10 touchscreen computer that is mounted within a specialized RFID Portal structure as shown below.
This is a browser based application that works best with Chrome as well as Firefox. It does not work with IE currently.
The workflow logic
Copyright © 2023 Stratum Global, Inc.