Remote Attendance Welfare System


This document is a broad outline of RAWS processing, detailing how the various processes relate to one another, as well as how daily shift details find their way into the RAWS universe.

Getting There:

[ SC ] –> Modules / Module Options


RAWS comprises a number of stages

  1. Configure your system
  2. Train your employees
  3. Manage the time & attendace using RAWS

Configure your system

Train your employees


Manage the Time & Attendance, Welfare using RAWS

Operational Points

  1. A shift edited in the Scheduling Workbench will be automatically updated to the RAWS Queue when the Shift Commencement time is in advance of the current system time and the Shift Date is the same as the current system date
  2. Shifts will not appear until they are due to appear on the Queue. This is defined by the time of the shift and the settings on the Queue Configuration window. In addition, control over the appearance of Welfare checks are specified in the Company/Client/Shift configurations and the Queue configuration control
  3. If a Welfare Check is missed or late, the next due time will be calculated from the last welfare check received time, This may mean one or more regulated times may be stepped over to bring the next due time inline with the current system time.
  4. Welfare Checks stop when either the Shift Finish time precedes the next welfare due time or the next welfare due time exceeds the limits of welfare check times – as defined in the Company/Client/Shift configurations
  5. All IVR/SMS logs are processed, regardless of there completeness or correctness of data. That being, a log received without an event will default to a Sign On,  a log received without a RAWS Site ID will not update any shifts, however will still be moved to the IVR_LOG_HIST table with the time and date of processing
  6. All RAWS events processed are logged against the Time and Attendance activity table contained against each shift.
  7. All RAWS events are processed to the Shift Audit Tab of the individual shift.
  8. RAWS Queue Resets – the RAWS work queue is built/rebuilt each time a queue is started and at 00:01 each new day. This way is to keep the number of rows in the processing work table to a minimum to aid performance of the Queue Monitor window.
  9. The appearance of shifts in other timezones will be adjusted by the time in the current timezone, meaning a time lag may appear in the display, but the time is relevant to the location of the shift.

Top of Page

See Also

RAWS - Add Client

RAWS - Configuration

RAWS - Launch Process

RAWS - Monitor Queues

RAWS - Overview

Top of Page