Axcess e/OLS User Manual - Manual (Page 11)

O N L I N E S U P E R V I S O R U S E R ’ S M A N U A L
©AXCESS INTERNATIONAL, Inc
750.015.001 R00
8 5/4/2007
and stored into a relational database, and then posted to the Live -Event viewer. We
are now in a position to investigate different types of RFID events. We will be able to
view events in near real time, or use the stored events’ information via the relational
database. Below in figure 2.9 is the Live-Event gauge with its controls and two events.
Figure 2.9 Live-Event Gauge, with two RFID events.
Looking at the top line of information and controls in the gauge from left to right, we
see the time of the User’s client machine, and that OLS is connected to the LogServer
and DCFR. Next we see Live-Event’s controls. Checking the “Pause checkbox” will
cause the Live-Event screen to stop updating with new RFID events. Checking the
“Beep checkbox” allows OLS to issue an audible sound whenever a new RFID event
“arrives” to the Live-Event viewer (Note that the client machine must be properly
equipped to produce sound). Next is the “Event filter dropdown box” at its default
position, which is to allow the Live-Event gauge to display all possible RFID events.
The “Display” button is used in accordance with the “Event filter dropdown box”,
and will be discussed later. The “Popup dropdown box” refers to the type of
information that will be displayed when the popup , to the left of an RFID event, is
double clicked. Lastly, there is a control to increase or decrease the font size of the
RFID events in the Live-Event gauge.
Let’s look at an RFID event and dissect the information it yields. As mentioned
earlier, red messages in OLS usually require attention so we’ll look at figure 2.10, and
discuss the information from left to right
Figure 2.10 Information in a RFID event
First is the popup. Second is the “yyyy/mm/dd hh:mm:ss” time stamp of the event.
Next is the event’s individual identification number, here it’s “
10991364 ”. This number
distinguishes this event from all other events in the database. Also, notice that the
“
EVT: ” prefix stands for “Event”, as in an RFID event. The next piece of
information is, “ TAG: 12300116 ”. Recalling figure 0, each Axcess Tag has its own
individual identification number programmed into it. The rest of the information in
event
EVT: 10991364 were derived from the tag identification number associated with
information previously configured in the relational database by an administrator.
Continuing from left to right, “
PID:0014 ”stands for “Personal IDentification number
0014”. “- PANIC- ”, is the event type. Event types will be discussed in more detail soon.
“ Nursing Manager ” is the description of what tag 12300116 is attached to. In this
case, tag 12300116 is with a Nursing Manager who has triggered their Axcess Panic
Tag. Recall that red in OLS Live-Event usually requires a response. Finally, we see the
last piece of information of event “
EVT:10991364 ” in the Live-Event gauge as,
“ @1stFloorNorthEast FirstFloorNorthEastReader5 ”. The symbol “@” is read as