[Reproduced with
permission from Vicor Inc. 2004]
Time Clock Report Help
General Description:
This screen allows reporting of time clock activity information for given
dates, users, pods, and shifts.
The report screen is divided into four (4) main sections:
Terms:
Activities are divided into the following categories:
-
Online - Activities that can be tracked by the RIDS system, such
as Extraction, Keying, and Scanning
-
(Scheduled) Idle - Idle time explicitly clocked into by a user via
the Time Clock screen, or the implicit idle time between selecting an online
application (via the RIDS blue button screen)
-
Workfile (or Unscheduled) Idle - Idle time between activities that
can be determined within the RIDS system, such as time between processing
workfiles. (For the case of Extraction, the time between lockboxes considered
to be part of productive Extraction.)
-
Offline - All activities that aren't Online activities or some form
of Idle. E.g., Mailroom, Break, etc.
Report Selection Criteria:
The user may specify criteria by which resulting rows are qualified
for reporting.
Criteria Interpretation (Inclusive versus Exclusive)
Note that some criteria exclusively qualify a row, whereas others
inclusively
qualify it. Here is how the criteria are interpreted in trying to qualify
a row for display. A row must include:
Date(s) of Interest
AND
Home Pod(s) OR Work Pod(s) of interest
AND
Home Shift(s) OR Work Shift(s)
of interest
AND
User Name(s) AND/OR User Id(s)
AND
Required Online OR
Required Offline activities OR
ANY ROW if Include 0% activity
rows is checked
The results may be filtered by:
-
Date(s) of Interest - Start of Day (SOD) work date(s).
One or more dates can be specified by clicking on the date(s) of interest.
The default is the most recent known date for which Time Clock data are
available. (The select all or clear all buttons can be used
to select or clear all items in this list. Clearing all dates will cause
zero rows to be displayed in the results.)
-
Home Pod(s) of Interest - User home pod(s)
The home pod(s) of interest, where home pod refers to the pod to which
a user is assigned. (This value is set for a given user via the User Admin
functions.) The default is any home pod. (The select all or clear
all buttons can be used to select or clear all items in this list.)
-
Work Pod(s) of Interest - Work pod(s)
The pod(s) of interest, where work pod refers to any pod for which
a user performed work. This can include the user's home pod. The
default is none of the work pods. (The select all or clear all
buttons can be used to select or clear all items in this list.)
-
Home Shift(s) of Interest - User home shift(s)
The home shift(s) of interest, where home shift refers to the shift
to which a user is assigned. (This value is set for a given user via the
User Admin functions.) The default is the any home shift. (The select
all or clear all buttons can be used to select or clear all
items in this list.)
-
Work Shift(s) of Interest - Work shift(s)
The work shifts of interest, where work shift refers to the shift for
which a user performed work. This can include the user's home shift. The
default is none of the work shifts. (The select all or clear
all buttons can be used to select or clear all items in this list.)
-
Include rows with 0% activity (checkbox)
If checked (selected) rows will be qualified even if the only activity
for that row was NotAtWork or any type of online idle. The default
for this is unchecked.
-
User Name Matches - A name or pattern matching one or more users'
names (as set in the User Admin functions).
The names matching is case-insensitive. A star (*) is a wildcard
match for any set characters. A question mark (?) is a wildcard
match for any single character. For example,
?ith*
will match both Withers and Tithers, but not Whithers
(because ? only matches one character and won't match Wh).
-
User Id Matches - A user ID or pattern matching one or more users'
ID (as set in the User Admin functions).
The user ID matching is case-insensitive. A star (*) is a wildcard
match for any set characters. A question mark (?) is a wildcard match for
any single character. For example,
*3?666*
will match both pp3666, 1346667 and 11346667, but
not 3p46667 (because ? only matches one character
and not p4).
Except for User Names and User IDs, all categories
are considered mutually exclusive. That is, a row must satisfy all
criteria to pass.
For example, if one selects pods a and b, and Night
shift, then each qualifying row must be from either pod a or b,
and
be for a user whose home shift is the Night shift.
Except for User Names and User IDs, one may use the AND/OR selector
to specify whether both or either matches are required to qualify a row.
For example, for user Mike Smith with user ID 123456,
the criteria:
name: *smith* OR
id: 2*
would qualify, since *smith* matches the user's name. However,
name: *smith* AND
id: 2*
would not qualify, since 2* doesn't match the user's ID.
Lastly, one may specify the number of output rows for each page of the
report. The default is currently 20 rows per page. Multi-page reports have
page links at the beginning and end of each page, allowing one to skip
to a given page, or previous or next page of the report.
Description
of Report Output Row Details:
Each row shows one day's work timeline for a given user. The report is
sortable via mouse clicks on a given column heading.
The columns headings are:
-
User ID - Id for this user
-
User Name - Name for this user
-
Home Pod - Pod that this user is normally assigned to
-
Work Pod(s) - Pod(s) that this user did work for
-
Home Shift - Shift that this user normally works during
-
Work Shift(s) - Shift(s) that this user did work for
-
Shift Start Time - Time of first known activity for this user for
this work date
-
Shift Duration - Total time this user worked for this work date
-
Productivity Times and Rates
(tables) - Two tables showing online and offline times and productivity rates for activities this user performed.
These tables have the following columns:
-
Key - A color legend key for the timeline and bargraph images. Online
activities may have two colors: One for the activity, and one for the Workfile
Idle time associated with that activity. The latter is denoted by '(Idle)'
in the key.
-
Activity - Online activity name
-
Count - Total number of items processed for this activity
-
Workfile Time - Amount of actual work time spent in processing (i.e.,
not including Workfile Idle time) for this activity
-
Session Time - Total session time spent on this activity
-
Workfile Rate - Count divided by Workfile Time for this activity
-
Session Rate - Count divided by Session Time for this activity
-
Efficiency - Workfile Time divided by Session Time
-
Activities (bar chart) - A histogram showing percentage time spent
in each activity. The activities are color coded and named, and hence
can be used as a key for reading the Timeline
. The assignment of colors to activities is configurable via the
Activity Editor, accessible either from the Site Spec Editor or the Time
Clock Menu (both under the ops Main Menu).
Activities are also grouped by Online, Offline and Idle times. Each
labeled activity shows percentage of total activity time it represents.
Online activities can also have a known Workfile Idle time. Hence the
graph shows the activity along with it's respective Workfile Idle time.
The two numbers represent the percentage of total shift time, and percentage
of session time, respectively for that activity. For example:
Sup Scan (26.3%, 40.1%)
Shows that a user spent 26.3% of his/her total day's time doing actual
real Supplemental Scanning work (i.e., not between workfiles). And that
time as a percentage of the total Supplemental Scanning session time is
40.1%. Hence the percentage of the time spent in this activity overall,
including inter-workfile idle time is just 26.3%/40.1%, or 65.6%. This
then, is the total relative height of the composite bar for this activity.
The last grouping shows total Scheduled Idle as a single bar, and total
Workfile Idle bar showing each flavor of Workfile Idle in a single
composit bar.
-
Timeline
(graph) - A color-coded (chronological) timeline showing what the user
did though out the given work day.
The timeline is into separate but parallel Online, Idle, and Offline
bars (see Terms above). Any apparent overlap of activities
is due solely to the coarse granularity of the report.
Below the activity bars is the actual wall clock timeline with tics
of duration denoted by the note Incr = .... This timeline is overlaid
with color coded shift information, each shift represented by a different
color, described by a key below. A color coded shift bar that has an additional
green line running through its length, indicates that this is the user's
home shift.
Description of Report
Output Summary:
At the bottom of the last page of the report are two tables of totals,
one each for Online and Offline activities respectively. These are the
totals for all detail rows, for all pages in the report.
The column headings for the Online Aggregate Totals table are the same
as for the Productivity Times and Rates
described above,
with the addition of a column for the number of users associated with
each activity. In addition a Total Online row is included for grand
totals under each column where appropriate.
The column headings for the Offline Aggregate Totals table are simply
Activity, Number of users, and Total Time for that activity.
Data File Download Section
At the bottom of the each page of the report is an identical Download Section,
consisting of links to data files containing both raw data and aggregated
(or cooked) data for each full day's work. Note that these files
contain data for all users for that day, not just the possibly filtered
detail results specified in the selection criteria in the report above.
Raw Data Files
The links names and file names for the raw data are of the form: YYYYMMDD.csv
Each line represents one activity for a given user. The file is sorted
by user, by time.
Each data line is in the following piple-separated (|) field format:
-
Date/Time - YYYYMMDDhhmmss timestamp. Start time of this activity
-
User ID - System user ID
-
Activity Shift - Shift during which activity occurred
-
Activity Pod - Pod for which activity was performed (Null if not
applicable)
-
Activity Name - Mnemonic name for the activity
-
Count - Number of items processed for this activity (0 if not applicable)
-
User Name - Full RIDS name for the given user
-
Home Shift - User's home shift
-
Home Pod - User's home pod
-
Problem Text - Any descriptive text if this is a special Problem
activity
For example:
20021027090200|nba00017|Weekend|d|SupKeying|722|"Loren Smith"|Day|d|
Definitions for Activities and Shifts can be viewed in the site
spec menu.
Cooked Data Files
The links names and file names for the cooked data are of the form: YYYYMMDD_STATS.csv.
The purpose of these statistics is to provide some condensed and more
usable form of the raw data. These may be downloaded into, say, an Excel
spreadsheet. This allows for custom reporting for different time periods
and criteria than the on-screen report may allow.
Each line represents the time for a given user spent in a given activity,
for a given pod, for a given shift. For example, if an extractor did only
extraction for a day, but did so for three pods and two shifts, that person
would be represented by six Extraction (6) lines in the cooked statistics.
The file has a single header row, giving abbreviated column headings.
The remaining rows are data rows.
Each data line is in the following comma-separated (,) field format:
-
UserID - System User ID
-
HmPod - User's home pod
-
HmShift - User's home shift
-
WrkPod - Pod for which activity was performed
-
WrkShift - Shift during which activity was performed
-
Activity - Mnemonic name for the activity
-
Count - Number of items processed for this activity (including saves,
0 if not applicable)
-
Saves - Number keystroke saves for this activity (0 if not applicable)
-
TotTime - Total (i.e., session) time spent performing this activity
(for this user, pod, shift). This includes Workfile Idle time.
-
ProdTime - Total (i.e., Workfile) time spent performing this activity
(for this user, pod, shift). This does not include Workfile Idle
time
For example:
UserID,UserName,HmPod,HmShift,WrkPod,WrkShift,Activity,Count,Saves,TotTime,ProdTime
...
nba00017,Loren Brock,d,Day,d,Weekend,SupKeying,95006,17545,29723,11522
nba00017,Loren Brock,d,Day,d,Day,SupKeying,132797,51346,36692,13280
Definitions for Activities and Shifts can be viewed in the site spec menu.