1. Hospital Asset Tracking
Use Case Description
Hospital Asset Tracking

2. Introduction Slide Introduce the scenario Category of Application
This scenario prototypes tracking valuable assets leaving the hospital building.
Category of Application
Asset Tracking
Optional Information
AWID 2010, closed circuit video system (Honeywell 32 Channel Omni)
The goal of this slide is to introduce the scenario that we are building. 2

3. Use Case Assumptions Assets are tagged with predefined tag IDs.
When tagging the assets, the system will enable the user to enter an asset name or ID into the system, so that the tag is associated with the asset.
LAN connectivity between Rifidi Box and AWID readers (10 readers installed).
AWID readers trigger video cameras when tags are read
This Slide lists some of the assumptions that are made in addition to the items that are tagged 3

4. Use Case Assumptions (cont.)
Readers and Video cameras are installed at each exit door that needs to be monitored.
Only valuable assets that may not leave the building are tagged.
When an asset is passing through an exit door (any direction) the asset is logged together with door ID and time stamp.
This Slide lists some of the assumptions that are made in addition to the items that are tagged 4

5. Asset Tracking Process Steps
Asset is tagged.
Web interface is displayed that allows and requires the user to enter a name or ID for the asset. If the tag is already associated with an asset, the new asset is overwriting the existing association.
Asset arrives at a door‏
Reader installed at each door
This is the actual workflow steps for the process. 5

6. Hospital Process Rules
If asset is read at door, log asset with timestamp
These are the unique business rules for this application. 6

7. Hospital Process Visual
When asset is read at door, the reader triggers the video camera to record.
More business rules but this time for a visual application that is the front end. 7

8. Associating Tags with Asset
(Inventory)‏
Asset ID
(RFID)‏
Tag #
Insert / Update
This is a UI mockup for what the front end application that displays the outcome of this process. Note that some processes might strictly feed upstream and hence will not have a UI. In this case lay out the integration points and xml schemas if possible. 8