Home

Remote Attendance Welfare System

Overview

This document details the RAWS hierarchy in a visual format so that the logic surrounding RAWS is easier to comprehend..

Getting There:

[ N/A ]

Introduction

As noted in the RAWS logic item, the fact that RAWS can be configured at many levels gives rise to a sophisticated logic flow. This document demonstrates how to correctly configure RAWS.

The Top Level (Company Level)

The company control is the place where you define whether you make RAWS functionality available at all (for a company by company basis).

raws company

The above is telling us the following:

Time & Attendance Processing Active - indicates that RAWS is active for sign-on & sign-off in this company.

Welfare Checking Active - indicates that welfare checking is active in the RAWS processing. If this check box was not ticked at all, then irrespective of your ticking any welfare checkbox at a lower level, no welfare checking will happen. The lack of any data within the triumvirate Welfare Check inputs (Check Time & Check Interval) is telling RAWS to look for the welfare parameters at the client or shift level.

Top of Page

The Middle Level (Client)

The next level down from the company level is the client (rostering location) where you intend to manage the shifts. The Time n Attendance tab on the Client Details screen containts the configuration parameters for RAWS. (This is the default setting for the examples that follow below).

client level

In the image above, the Overide TNA settings checkbox is selected, which tells RAWS that "we're taking control of all parameters" at this level. However, in this instance nothing else if checked and therefore nothing will happen in RAWS if the checking gets to the client level (refer RAWSQlogic for explanation).

Top of Page

The Middle Level (Client) Configured

The following image details how you may want to correctly configure a client site for T&A monitoring.

raws monitoring

In the image above, we're over-riding the RAWS controls to the details noted.

TNA is active for this client / site, with basic sign-on and sign-off. Welfare checking is enabled, and the triumvirate of times are set, therefore we can expect RAWS to manage the welfare checking as noted between the hours of 10.00pm and 05.00 am the next day. Welfare checks will be raised (monitored) every 2.00 hours.

Top of Page

The Client Work Schedules

Whilst in the Client Details screen, if you select the Services tab you get the client work schedules as defined for the site.

work schedules

We'll now take a look at the RAWS definitions behind the shifts.

Top of Page

Client Work Schedules

Similar to each of the previous images we've seen, the Time and Attendance tab on work schedules has the exact same parameters. This allows you to control every aspect of T&A management through RAWS at the very lowest level. This images is indicating that we want this shift (when it becomes part of a standard schedule) to be loaded to the RAWS Monitor Queue for management.

The Raws Options indicates "Use Default Settings", which in this instance means - follow the path upwards through the Client Site Time & Attendance definition to find over-riding parameters, and if you find none there, take the parameters are they are set up at the Company Control level.

This work schedule will manage sign-on and sign-off only.

Top of Page

Explanation - overide TNA Settings

In this example (above), Overide TNA settings is checked but nothing else including TNA Active - this has effectively turned off any system default processing, because the selection indicated "Overide TNA Settings" and the setting are all empty.

Top of Page

Explanation - activate Sign On

In this example (similar to the previous), we have selected TNA Active - which indicates that we require sign-on and sign-off only.

Top of Page

Explanation - Welfare Checking only

This example demonstrates all aspects of T&A monitoring to be switched on, and then the Raws Options are used to over ride and turn off sign-on monitoring, whilst maintaining Welfare checking. Welfare checking will happen because the triumvirate time settings have values.

Top of Page

Explanation - Sign on and Welfare Checking

This example demonstrates all T&A settings including valid Welfare values, therefore sign-on and welfare checking will be actioned on these shifts.

See Also

RAWS - Add Client

RAWS - Configuration

RAWS - Launch Process

RAWS - Monitor Queues

RAWS - Monitor Queue Logic

RAWS - Overview

Top of Page