datacap - jobscope manufacturing software

DATACAP User’s Guide JOBSCOPE ®

DATACAP

JOBSCOPE Page 1

Contents

Contents ........................................................................................................................................................ 1

Introduction to DATACAP ............................................................................................................................. 5

Benefits of Using Automated Data Collection .......................................................................................... 5

General Overview ..................................................................................................................................... 6

General Terms ....................................................................................................................................... 6

Transactions .......................................................................................................................................... 7

Technical Overview ................................................................................................................................... 9

Transactions ............................................................................................................................................ 11

Database Updates ............................................................................................................................... 14

Breaks .................................................................................................................................................. 14

Overtime ............................................................................................................................................. 15

Holidays ............................................................................................................................................... 16

Rounding ............................................................................................................................................. 16

Download (Sync) Programs ................................................................................................................. 17

DATACAP Configuration .......................................................................................................................... 19

Database Options ................................................................................................................................ 20

Site Options ......................................................................................................................................... 20

User Interface (UI) Options ................................................................................................................. 22

Text Options ........................................................................................................................................ 23

Admin Options .................................................................................................................................... 23

DATACAP Data Synchronization .............................................................................................................. 24

Initial Setup ............................................................................................................................................. 26

Before opening Database Maintenance ............................................................................................. 26

Change Account References ............................................................................................................... 27

Change Overtime Schedules ............................................................................................................... 27

Change Break Schedules ..................................................................................................................... 27

Change Holiday Schedules .................................................................................................................. 27

Change Shifts ....................................................................................................................................... 27

Change Employees .............................................................................................................................. 27

Update System Configuration ............................................................................................................. 28

DATACAP

JOBSCOPE Page 2

Download Online Tasks ....................................................................................................................... 28

Database Maintenance ............................................................................................................................... 29

Sync ......................................................................................................................................................... 30

Schedules ................................................................................................................................................ 33

Account References ............................................................................................................................ 34

Overtime Schedules ............................................................................................................................ 36

Holiday Schedules ............................................................................................................................... 40

Break Schedules .................................................................................................................................. 42

Shifts.................................................................................................................................................... 45

Employees ............................................................................................................................................... 48

Employees ........................................................................................................................................... 49

Employee Groups ................................................................................................................................ 51

Supervisors .......................................................................................................................................... 54

Field Services ........................................................................................................................................... 55

Overhead Accounts ............................................................................................................................. 55

Labor ....................................................................................................................................................... 56

Labor Accounts .................................................................................................................................... 57

Scrap Codes ......................................................................................................................................... 59

Online Tasks ........................................................................................................................................ 60

Work Centers ...................................................................................................................................... 62

Automatic Time ....................................................................................................................................... 63

Holiday Attendance............................................................................................................................. 63

Salary Attendance ............................................................................................................................... 64

System ..................................................................................................................................................... 66

Configuration ...................................................................................................................................... 66

Clear Uploaded Transactions .............................................................................................................. 72

Clear Audit Log .................................................................................................................................... 72

Services ............................................................................................................................................... 74

Supervisor ................................................................................................................................................... 76

Online Approval ...................................................................................................................................... 76

Reports ........................................................................................................................................................ 79

Absentee Report ................................................................................................................................. 81

DATACAP

JOBSCOPE Page 3

Attendance Report .............................................................................................................................. 82

Employee Detail Report ...................................................................................................................... 83

Employee Status Report...................................................................................................................... 86

Employee Summary Report ................................................................................................................ 87

Employee Time Sheet (C) .................................................................................................................... 88

Employee With No Activity ................................................................................................................. 89

Exception Report Committed ............................................................................................................. 90

Exception Report ................................................................................................................................. 91

Idle Employees .................................................................................................................................... 92

Labor Audit Edit Log ............................................................................................................................ 93

Labor Audit no ATTN ........................................................................................................................... 94

Labor Audit Transaction Register (C) .................................................................................................. 95

Labor Detail (C) ................................................................................................................................... 96

Labor Detail Errors .............................................................................................................................. 97

Labor Summary ................................................................................................................................... 98

Online Tasks ........................................................................................................................................ 99

Overtime Report ............................................................................................................................... 100

Transaction Edit Log .......................................................................................................................... 101

Transaction Queue Register .............................................................................................................. 102

Unapproved Time (C) ........................................................................................................................ 103

Work In Process (WIP) ...................................................................................................................... 104

Upgrading .................................................................................................................................................. 105

Jobscope System Configuration ............................................................................................................ 106

Supervisors ............................................................................................................................................ 108

Routine Maintenance ............................................................................................................................... 111

DATACAP Server .................................................................................................................................... 111

Downloading Data ............................................................................................................................. 111

Host Systems ......................................................................................................................................... 111

Audit File ........................................................................................................................................... 111

Attendance File ................................................................................................................................. 111

Error Transactions ............................................................................................................................. 111

Hourly Transaction File ..................................................................................................................... 111

DATACAP

JOBSCOPE Page 4

Record Statuses ................................................................................................................................. 112

Start Host Processing ........................................................................................................................ 112

Stop Host Processing ......................................................................................................................... 112

AS/400 Specific.................................................................................................................................. 112

JOBSCOPE Enterprise Edition Specific ............................................................................................... 113

Appendix A - DATACAP Overtime Calculations ......................................................................................... 114

Overtime Scenario #1 ........................................................................................................................... 115

Overtime Scenario #2 ........................................................................................................................... 115

Appendix B - Parallel Operation Time Calculations .................................................................................. 117

Appendix C - DATACAP Troubleshooting Tips ........................................................................................... 118

DATACAP

JOBSCOPE Page 5

Introduction to DATACAP

DATACAP is an automated data collection system designed for Job Costing and Attendance tracking.

Employees use DATACAP by either typing or scanning bar-coded information. This data is sent over a

TCP/IP network to a Windows Server running DATACAP. DATACAP verifies and maintains the data,

determines the amount of time spent on jobs and indirect Labor Accounts, performs calculations, and

organizes the data into meaningful information. The process is completed when these records are

uploaded and posted to JOBSCOPE.

DATACAP Labor features automatic and/or manual application of break time, the ability to edit

transactions and a large degree of flexibility with regard to the calculation of overtime. Furthermore, the

client/server architecture allows for short-term independence from the JOBSCOPE host. This

independence results in faster processing while using less host resources, as well as the ability to

function when the host is down.

This section includes:

Benefits of using Automated Data Collection

General Overview

Technical Overview

Benefits of Using Automated Data Collection

Some of the advantages of utilizing an automated data collection system are:

Reduces data entry errors - Several studies have been conducted to compare manual data entry with an

automated data collection system that uses bar coding. Humans make mistakes; automated data

collection systems do not. With manually entered data, the expected error rate is 1 in 300 entries. With

an automated data collection system, the error rate is slashed to 1 in 3,000,000 entries. This is a

reduction in errors by a factor of 10,000. This represents significant savings in administering the data

collection system.

Verifies data online - Online verification of data by the automated data collection system ensures

proper charging of labor hours. Attempts to charge time against closed, secured, or restricted jobs, or

completed operations can be identified and prevented when an employee attempts to log-on.

Provides current availability of data - Unlike data collected manually, there is virtually no delay

between when an employee uses a barcode reader to enter the data into the system and when it is

available to management. Using such a system, information is current at all times.

Provides exact distribution of labor charges - Automated data collection permits very precise

assessment of cost data. This reduces or eliminates guesswork in determining time requirements for

production processes and provides a clear picture of labor utilization.

DATACAP

JOBSCOPE Page 6

General Overview

This section provides an overview of DATACAP Labor transactions and processing. When employees

arrive for work at the beginning of their shift, they Clock-In at a DATACAP session. If they know what

task they are going to be working on, they log directly onto it. If not, they log onto an indirect labor

account while they are waiting for their task assignments. Once they know the task they will be working

on, they log off of the account and log onto the new task. If they need to take a break during the day,

they can use the Suspend and Resume transactions to create a manual break or if an automatic break is

setup, it will be automatically calculated. If at any time they want to verify what their current Status on

the system is, they can. They will continue to log on and off of any tasks they work on during the day

until it is time to end their shift when they will Logoff and Clock-Out.

If an employee finds an item that has been previously reported as complete which needs to be

scrapped, they may enter a Scrap transaction at any time.

When supervisors need to verify what their employees have done, they can use the DATACAP Reports

from a web browser. Also, they may be able to edit transactions for their employees and create Absence

Entries for employees who are absent or working off site.

JOBSCOPE users may be able to view information in JOBSCOPE using reports or windows to determine

the status of operations. This information reflects the last processed DATACAP transactions. Depending

on the configuration, this could mean that a few minutes after an employee logs off of an operation, the

information about the cost and quantity of what they completed is available in JOBSCOPE to anyone

who needs (and has the authority) to know.

General Terms

Breaks and Idle Time - Methods of maintaining accurate records of the non-production expenses of an

organization. Any time for which the company pays not spent on production, either direct or indirect, is

normally separated into these two categories.

Database Maintenance - Used to define the System Configuration and Schedules that the commit

engine uses to make calculations.

DATACAP - The automated data collection system. This system currently automates the labor entry

procedures used in JOBSCOPE making the data collection and entry more accurate and less time

consuming.

Download (Sync) programs - Used to help DATACAP perform optimally by ensuring that the data from

JOBSCOPE, which will be used for transaction verification, is complete and accurate on the DATACAP

Server.

Edit Error Transactions - Allows correction of records that have not been successfully processed on

JOBSCOPE.

DATACAP

JOBSCOPE Page 7

Host Upload - Uploads the data in the DATACAP server to the JOBSCOPE host.

Task - Describes a specific item that employees are able to charge their time directly for cost collection.

These include Releases (Job Master in JOBSCOPE), Release-Work Order-Operations (Operations File in

JOBSCOPE) and direct or indirect Labor Accounts (Table 4004 in JOBSCOPE).

Transaction - Describes data records that are created by the DATACAP system to record what an

employee has done on the system. The types of transactions are described later in this chapter.

Transactions

Transactions describe data records that are created by the DATACAP system to record the employee’s

work. The following definitions pertain to transactions:

NOTE: For more information about transactions, see Technical Overview.

Clock-In - The process of an employee entering the DATACAP system to begin a day of work. Employees

will be prompted for their employee/badge number, which may be entered using either a keyboard or a

barcode scanner.

Clock-Out - The process of an employee exiting the DATACAP system to end a day of work. Employees

are prompted for their employee/badge number, which may be entered using either a keyboard or a

barcode scanner.

Logon - The process of an employee starting the application of costs to a particular task. Employees may

log onto a release or Release-Work Order-Operation (Release-Work-Order) by clicking or pressing the

[Logon Release] button or function key, or log onto an account by clicking or pressing the [Logon

Account] button or function key. They are then prompted for their employee/badge number, task

number, and work center, if logging onto a Release-Work-Order, they may be prompted to differentiate

between setup and run time. These values may be entered using either the keyboard or a barcode

scanner. Depending on the configuration, the work center may be presented to the employee for

confirmation or entered by the employee. DATACAP will automatically create a Clock-In transaction if an

employee is not clocked in before they Logon.

Logoff - The process of an employee stopping the application of costs to a particular task. Employees

may log-off of a release, Release-Work-Order, or account using either a keyboard or a barcode scanner.

They will be prompted for confirmation of each task to be logged-off of, and the quantity complete for

each operation.

Suspend - The process of an employee starting a manual break. Manual breaks are periods of time when

an employee temporarily stops working on the task(s) they are logged onto in order to go to lunch, get a

drink, etc. Employees may suspend their task charges using either a keyboard or a barcode scanner.

After a successful Suspend, their labor hours will be charged to their Manual Break Account until a

Resume is performed. If they do not have a Manual Break account assigned, these hours will be unpaid.

DATACAP

JOBSCOPE Page 8

Resume - The process of an employee stopping a manual break. Employees may resume their work

charges by using either a keyboard or a barcode scanner. After a successful Resume, the task(s) they are

logged onto will begin accumulating labor charges again.

Scrap - The process of an employee reporting completed material items as scrap when they are found

defective. Employees may create a scrap transaction. They are prompted for their employee/badge

number, the Release-Work-Order and work center where the scrap is found, which may be entered

using either a keyboard or a barcode scanner. They will also be required to enter a Scrap Code and

quantity. Scrap items are displayed in the JOBSCOPE In Process Scrap report.

Status - Describes the process of employees verifying what they are currently doing on the DATACAP

system. Employees may learn their status using either a keyboard or a barcode scanner. Their status,

and the task(s) they are logged onto, is displayed.

DATACAP

JOBSCOPE Page 9

Technical Overview

This section contains technical information on the terms, configurations and functions described in the

General Overview.

Account - Used to maintain specific types of costs related to the operation of an organization. These are

non-production costs.

Attendance accounts - Accounts used to track what employees are actually earning from the company in

the form of pay. Attendance is the time between clock in and clock out. They are found in the

Labor/Labor Accounts window and downloaded from JOBSCOPE.

Breaks - Time periods when an employee is not active on, but logged onto, a task. Breaks are utilized by

suspending task charges and ended by resuming task charges when the break is finished. The primary

purpose of breaks is to enable recognition of time spent in a non-productive status, which is actually

planned or authorized by management and taken by the employee. In areas where breaks are required,

this is a good method of creating an audit trail of proof of break utilization. Since the task charges are

suspended, the process of resuming the task, which was in process before the break started, is

simplified.

Commit Server - Reads the transactions from the Transaction Queue, sends the data to the appropriate

commit functions which make all of the calculations and store the calculated records in the Labor Audit

table. If data is not valid when it reaches the Commit Server (i.e. an employee was deleted before his

last transactions were committed), the Commit Server will not attempt to process any subsequent

transactions for the employee involved.

Database Maintenance - Used to establish DATACAP operating parameters, such as System

Configuration Options, References, Schedules, and Employees. If employees are not set up using

Database Maintenance, they are automatically assigned to shift ‘0’ when downloaded from JOBSCOPE.

In most cases it is more efficient to enter employees and assign them appropriate shifts and schedules

when they are entered in JOBSCOPE.

Holidays - Days when an employee is to be paid extra for working, even though the day would normally

fall on a regular business day. This is tracked to identify extra costs incurred during the performance of a

task.

Host Upload - Reads the data in the Labor Audit table, converts it into records that can be read by Host

Processing and writes these records to the audit table on JOBSCOPE.

Host Processing - Reads the data that has been uploaded from DATACAP and, after verifying that the

data is still valid, posts the data to the appropriate tables. Once the data has been posted, the labor

information can be retrieved in standard JOBSCOPE reports. These processes should remain active

perpetually but may need to be shutdown or restarted after backups on some machines.

DATACAP

JOBSCOPE Page 10

Idle Time - Any time which the employee earns pay without being authorized to charge that time to a

valid task. This time is normally tracked and controlled due to the fact that it is unplanned, unproductive

and potentially very costly.

Labor Audit Table - Contains records that have been processed by the Commit Server. It contains a status which indicates whether the record has been uploaded or not, and if an error occurred during the upload attempt. This is also where records are retained for a period of time as part of an audit trail.

Live Mode - Describes the configuration of the DATACAP applications that allows data to be available on JOBSCOPE reports as quickly as possible after a transaction is completed. In most cases, if supervisor approval is not required, Live Mode requires less than 15 minutes from the time employees log off or clock-out before the cost of their work is available in a JOBSCOPE report.

Overtime - Time for which an employee receives extra pay for working more hours than are normally required during a period of time. These costs are tracked to identify potentially unplanned costs for work required to fulfill task requirements.

Rates - The multipliers used to calculate the premium paid for abnormal working conditions such as the number of hours worked in a period of time, or holidays. The normal rate is 1.00 or 1 times the normal pay rate and double time is 2.00.

Release - A term that generally refers to a product or contract, which contains all of the items, and/or operations required to fulfill the product or contract’s terms. The release is used to manage and collect costs related to the product or contract.

Release-Work Order-Operation - The most specific level of product or contract reference. Normally this is a specific/basic step in the fulfillment of the contract or product’s completion, such as work required to complete a part, component, or assembly of the final product.

Schedules - Used to determine what calculations and manipulations of the data will be made in order to have the desired records created and processed. These may be as general as several shifts or as specific as a single employee.

Task - Any production-related direct Release/Release-Work Order-Operation or indirect account to which time is charged by an employee to track production- related costs.

Transactions - Contain the information that is used by the commit engine to make calculations and create records that will be uploaded and posted to JOBSCOPE. Typically, the commit engine will use two matching transactions from the Transaction Queue (Clock-In and Clock-Out) to create a single attendance, labor or scrap record in the Labor Audit table. However, in cases where automatic breaks or overtime apply, several records may be created from two transactions.

Transaction Queue - Contains transactions (raw data), which have passed the verification engine edits, but have not been processed by the Commit Server.

Verification Engine - Validates the data on the DATACAP server and, when applicable, the JOBSCOPE host. If invalid data is found, the verification engine sends a message back to the Intermec or WINCAP terminal so the employee can correct the invalid information that was entered. Once the data is validated, a message is sent back to the Intermec or WINCAP terminal to inform the employee that the transaction was successful. The transaction information is stored in the shared memory segment and in the Transaction Queue.

DATACAP

JOBSCOPE Page 11

Transactions

When an employee creates a Clock-In transaction, the verification engine will first try to validate the

employee/badge number in the DATACAP database. If the employee number is not found in the server

database, the employee will be notified that the number entered is not valid. Please note that badge

numbers are not known to the JOBSCOPE database so host verification of badge numbers will not work.

At the time the employee clocks in, the verification engine begins storing information that will later be

used to create attendance and labor records. The clock-in time stamp is the start time for the

Attendance Record. The employee will be considered idle before logging onto a task. All transactions will

be stored in the Transaction Queue to await processing by the Commit Server.

During processing by the commit engine, the shift tolerance values are compared against clock-in time.

If the clock-in is within the defined tolerances, the commit engine will adjust the start time for the

Attendance Record to the shift start time. Any labor records that occur during this period will be

adjusted to the shift start time also. If the clock-in is outside the shift tolerances, the start time will be

the actual time of the clock-in.

Additionally, if this is the first clock-in for the employee on this date, the daily hour accumulator for the

employee is reset to zero by the commit engine. The commit engine then checks sequential days to see

if the number of consecutive days should be incremented. This is relevant to overtime calculations,

among other things. If it is another sequential day, the Commit Server increments the sequential days

accumulator. If it is not another sequential day, the accumulator is reset. DATACAP then compares the

day of the week for the current clock-in and the last clock-in. If a new week has started (as defined in

System Configuration), the weekly hours accumulator is reset.

When an employee creates a Clock-Out transaction, the verification engine will try to validate the

employee/badge number in the DATACAP database. If the employee number is not found in the

database, the employee will be notified that the employee number they entered is not valid. Please

note that badge numbers are not known to the JOBSCOPE database so host verification of badge

numbers will not work.

During processing by the Commit Server, any shift or elapsed time rounding will occur when a clock-out

transaction is processed. If the clock-out occurs during the defined shift clock-out tolerances (if any), the

attendance hours are rounded to the shift end time. A labor record charged to the idle account (defined

in Account References) will be created for the adjustment (if any) made to the Attendance Record time.

For further information on this type of rounding, see Shift Rounding.

If the clock-out does not occur during the defined shift clock-out tolerances, but the elapsed time

rounding field is set to a value other than 00:00:00, elapsed time rounding will occur. Elapsed time

rounding will cause the employee’s attendance hours for the day to be rounded to the nearest multiple

of the time defined in the round elapsed time field. For example, if the value is set to 00:06:00, the

employee’s attendance hours will be rounded to the nearest six minutes or 0.1 hours. A labor record

DATACAP

JOBSCOPE Page 12

charged to the idle account will be created for the adjustment made to the Attendance Record time. For

further information on this type of rounding, see Rounding Elapsed Time.

After all rounding has taken place, an Attendance Record (charged to the Attendance Account defined in

Account References) will be created. The Attendance Record will contain the time stamps for the clock-

in and clock-out and the number of hours accumulated, after calculating the total time worked,

subtracting unpaid breaks and applying appropriate rounding calculations.

Host Upload will copy the Attendance Record to the JOBSCOPE host, where all dollar amounts are

calculated. (DATACAP calculates labor and attendance, including overtime for Job Costing purposes

using rate multipliers only).

When an employee creates a Logon transaction, depending on the configuration, the verification engine

will first attempt to locate the task that the employee is attempting to log onto in the DATACAP

database. If the task is not found locally, the verification engine will require the employee to enter the

work center. If the task is found, the work center may be included in the prompt for confirmation. Once

the work center is entered or confirmed, the verification engine will attempt to verify the

employee/badge number, task and work center using the same method as for Clock-In. After all of this

data is verified, if DATACAP is configured to handle setup, the employee is prompted to specify if this

logon is for setup time.

At the time the employee logs onto a task, the verification engine begins storing information that will

later be used to create labor records. If all information entered is correct, the user is notified that the

logon was successful.

The labor record types include: LBRA (Labor Account), LBRR (Labor Release), LBRS (Labor Setup), LBRO

(Overtime), and LBRW (Labor Release-Work-Order).

The commit engine compares the time between the last logoff and the new logon with the

Tolerance_Between_Tasks set in Database Maintenance. If the Tolerance_Between_Tasks is not

exceeded, the start time for the new task will be adjusted to the end time of the previous task. If the

employee exceeded the Tolerance_Between_Tasks, a labor record will be created charging the time

between tasks to the idle account defined in Account References.

When an employee creates a Logoff transaction the commit engine will calculate the hours worked for

the labor record as the difference between the start and end times with applicable breaks deducted. If

the employee is logged onto multiple Release-Work-Orders, the hours worked are divided evenly

between each of the operations. If breaks occurred during the logon, the breaks are either simply

deducted (unpaid) or deducted with a labor transaction created for the break (paid). If overtime is

enabled and applicable, the labor transaction is charged to the job and overtime accounts as

appropriate. This may result in multiple records for one transaction and is determined by the Account

Reference and Overtime Schedules, as well as DATACAP Configuration.

Suspend and Resume transactions are used to create a Manual Break (LBRA) record

DATACAP

JOBSCOPE Page 13

Scrap records (SCRP) are saved directly to the Labor Audit table so they are not affected by Edit Mode

configuration.

Status returns values about the current activities of an employee on the system.

DATACAP

JOBSCOPE Page 14

Database Updates

When a transaction is initially entered into Datacap, a record is written in the TRXQUE table in the local database. If the transaction is an employee clockin, a record is also written in the EMP_CLOCKIN table. This EMP_CLOCKIN record is deleted when the employee clocks out. If the transaction is an employee login (logging on to a task), then a record is written to the EMP_LOGON table. This record is deleted when the employee clocks off that task. When an employee logs off a task, or clocks off, another record is written in the TRXQUE table. Therefore, a logon and logoff to a task will result in two TRXQUE records. The TRXQUE table has a column called TRX_TYPE to tell the system what type of transaction the record represents. These TRX_QUE values are as follows:

Clockin – 1

Clockout – 2

Logon Account – 3

Logon Release – 4

Suspend – 5

Resume – 6

Logoff Release or Account - 7 The next process is called Commit Server. This process is controlled by a web process. The run interval

is controlled by a setting in the Services tab in the System menu. This process reads the TRXQUE records

and determines if the task is complete, meaning that a TRXQUE record exists for both logon and logoff.

If only the TRXQUE record for logon exists, meaning the employee is stilled logged on, then a record is

written in the WIP table. If both records exist, meaning the employee has logged off, then a record is

written in the LBR_AUDIT table.

In the LBR_AUDIT table, records can be edited by the supervisor. These records have a status value

(REC_STATUS). Values may be 0 or 1. 1 means uploaded, and 0 means not uploaded.

The next process is Host Upload. This process moves records from LBR_AUDIT to AUAUDIT in the jee

database. Again, the run interval is controlled by a setting in the Services tab in the System menu.

Finally, the Jobscope database updates are done by the Host Processing process, which runs as a service.

This service reads the AUAUDIT records and makes the database updates in Jobscope, such as job

costing, hourly transaction file records (PPHRTRX), and other updates. The AUAUDIT table has a field

called REC_STATUS. 000001 means ready to process, 000016 means processed, and 000256 means an

error has been detected.

Breaks

Break is the term describing the process by which an employee who is logged onto one or more tasks

may suspend charges to those tasks for a period of time. At the end of that period of time, they may

resume charges to tasks they were previously working on with minimal, or no, terminal activity.

DATACAP supports two types of breaks, manual and automatic. Breaks may be either paid or unpaid.

Manual breaks allow an employer to collect more accurate labor costs, but require employees to

perform suspend and resume transactions. Automatic breaks are not as accurate, since they

DATACAP

JOBSCOPE Page 15

automatically subtract the break time from on-going tasks, but they do not require the employee to

perform any transactions.

Manual Breaks allow employees to take random or unscheduled breaks of any length and return to the

previously active task with minimal terminal interaction. When an employee performs a [Suspend]

transaction, all tasks are suspended. When they perform a [Resume] transaction, their time will again be

charged to the tasks they were logged onto before the break. When an employee logs off or clocks out,

the length of their break(s) is automatically deducted from the hours worked in the labor and

attendance transactions as appropriate. If an account number is assigned in the Manual Break field of

the Account Reference in Database Maintenance, the suspended time is charged to this account number

and a labor record is created for the manual break. If the Manual Break field is left blank, no labor

record will be created and the break length will be deducted from the Attendance Record.

Upon returning from a break, the employee must resume the previous task before logging off, logging

onto a different task, or clocking out. See Suspend and Resume for more information on manual breaks.

Automatic Breaks allow an unlimited number of regularly scheduled breaks to be defined in a Break

Schedule, which is then assigned to a shift or employee. When an employee logs off, the length of any

applicable break(s) is automatically deducted from the hours worked in the labor transaction. If an

account number is assigned to a break in the Maintain Break Schedules window, the break time is

charged to that account number, and a labor record is created for the break. If the account field is left

blank, no labor record is created and the break length is deducted from the Attendance Record as well.

Overtime

The Overtime Schedules defined in the Maintain Overtime Schedules window in Database Maintenance

allow DATACAP to calculate overtime cost rates and fences. Five different overtime fences of three

types are available. There is one fence for consecutive days worked and two fences each for daily and

weekly hours worked. Each fence allows a different rate and results in a separate labor transaction for

the period when it is in effect. If overtime is to be calculated the same for all employees, only one

Overtime Schedule will be needed. If work on a holiday will be charged at a different rate, an Overtime

Schedule for holidays will be needed.

NOTE: If daily, weekly, and consecutive day overtime fences are all defined, then the consecutive day’s fence and rate takes precedence. The daily/weekly fence/rate precedence can be set in the Processing Priority section of the Maintain Overtime Schedules window.

Consecutive days are based on an employee’s clock-out dates. The date when employees clock out is

compared to the date of their last clock-out. If the current clock-out date is one day higher than the

previous clock-out date, and the employee worked the minimum number of hours, the consecutive day

count is incremented. If the date is the same as the previous clock-out, the consecutive day count

remains the same. In any other case, the consecutive day count is reset to 1. Therefore, employees

MUST clock-in and clock-out each day and work the minimum number of hours in order to generate

valid overtime results. If the consecutive days overtime fence is in effect, the employees’ transactions

DATACAP

JOBSCOPE Page 16

will have this rate applied before any other overtime calculations are performed. The consecutive days

count is reset at the beginning of the work week.

Weekly overtime is based on the accumulated hours worked during the current workweek. These

accumulated hours are stored in the Hours This Week field of the Employee Detail file. The method used

for accumulating these hours is determined by the WEEKLY_OVERTIME_BY_TOTAL_HOURS variable in

the System Configuration window in Database Maintenance. If the

WEEKLY_OVERTIME_BY_TOTAL_HOURS value is set to N, the daily overtime hours are excluded from

the accumulation. However, if the WEEKLY_OVERTIME_BY_TOTAL_HOURS value is set to Y, the daily

overtime hours are included in the accumulation.

Daily overtime is based on the accumulated hours worked on the current date. These accumulated

hours are stored in the Hours Worked Today field of the Employee Detail file.

NOTE: The date of the clock-in determines the date to which the hours worked are credited.

For additional information on overtime processing priorities, see Appendix C.

Holidays

Holidays are based on the date employees clock-in. If the date employees clock in is defined as a holiday

in their Holiday Schedule, all hours earned until they clock-out will be calculated using the holiday rates

defined in their Holiday Overtime Schedule, even if some portion of the hours do not fall on the holiday.

If employees clock-in on a date that is not defined as a holiday, the hours earned until they clock-out will

be calculated using the normal Overtime Schedule, even if some portion of the hours fall on a holiday. If

employees clock in on a date defined as a holiday, the hours worked until they clock-out will be

evaluated with their Holiday Schedule, even if some portion of the hours do not fall on the holiday.

Holiday records can also be created as a batch. See Holiday Attendance.

NOTE: For shifts that span midnight, a separate Holiday Schedule is necessary if they normally clock-in before midnight to begin a new business day.

Rounding

DATACAP provides two types of rounding for attendance hours: Shift Rounding and Elapsed Time

Rounding. Both types of rounding may be enabled at the same time. Both serve different purposes and

complement each other. In either case, the total of the hours worked from the labor records, including

rounding adjustments, will equal the hours in the Attendance Records.

Shift Rounding describes the method of adjusting employee Attendance Records to given shift start

and/or end times. This method is used to standardize the amount of time employees receive credit for

when they are in a queue during heavy use periods such as those experienced at shift start and end

times.

NOTE: When Clock-In and Logon are performed during the Clock-In tolerance period, the start time of both Attendance and Labor records are adjusted without additional records being created. When

DATACAP

JOBSCOPE Page 17

Clock-Out and Logoff transactions are performed during the Clock-Out tolerance period, the end time of the Attendance Record is adjusted and an adjusting Labor Record is created.

Round Elapsed Time describes the method of rounding the total hours worked to a set increment of

time, such as the nearest tenth, quarter, or half of an hour. This increment is set in the shift definition or

employee record in Database Maintenance.

For example, if the value defined in the employee’s record is 00:06:00 the Attendance Record will be

rounded to the nearest tenth of an hour. If the total time worked was 7 hours and 57 minutes; the

Attendance Record will be rounded to 8 hours. A labor record will be created charging the extra three

minutes to the employee’s idle account. (Note: If both clock-in and clock-out times are within the shift

tolerances, this rounding will not be used. That is, shift rounding takes precedence over elapsed time

rounding.)

NOTE: An employee must clock-out to initiate the rounding processes. DATACAP will always generate an adjusting Labor Record that will have a positive or negative value as needed.

Download (Sync) Programs

In order to provide faster verification, DATACAP provides several batch processes that download data

from JOBSCOPE to the DATACAP database:

• Security User

• Security User Group

• Security User Permission

• CSpec Job Cost Account

• Customer

• Customer Site

• WO Bill Of Material

• Part

• Location Code

• Material Cost Category

• WIP Code

• Material Master

• Bin Detail

• Lot Inventory

DATACAP

JOBSCOPE Page 18

• JEE Option

• Job

• Labor Account

• Scrap

• Employee

• Online Tasks

• Work Center

• Overtime Code

When an employee record is downloaded to the server database, the employee name, number,

department, shift, and supervisor id are downloaded. All other fields are set to default values. The

Database Maintenance process is used to update these defaults with correct data. It is also used to

define shifts, Account References, and Overtime, Break, and Holiday Schedules.

DATACAP

JOBSCOPE Page 19

DATACAP Configuration

After using either the DATACAP create or upgrade module, the settings for the new DATACAP database

are automatically loaded in the Database tab for the DATACAP page in the DC Server, DC Database, DC

User, and DC Password fields.

DATACAP

JOBSCOPE Page 20

Complete the remaining DATACAP configuration pages based on the following configuration item

descriptions

Database Options

DC Server

This is the SQL Server computer name that hosts the DATACAP database.

DC Database

This is the SQL Server database name for the DATACAP database.

DC User

A SQL account user name with access to the DATACAP database.

DC Password

This is the valid password for the SQL user defined above.

Host Type

This value will indicate the platform of the host JOBSCOPE system.

Host Server

This is the Windows Server computer name or IBM TCP address that hosts the JOBSCOPE

database.

Host DB Name

This is the database name for the JOBSCOPE database.

Host User

A SQL account user name with access to the host JOBSCOPE database.

Host Password

This is the valid password for the user defined above.

DL Job Interval (Minutes)

This is the number of minutes between each job download in the Job Controller.

UL Job Interval (Minutes)

This is the number of minutes between each job upload in the Job Controller.

Schedule Holiday Attendance

Enable or disable scheduled automatic holiday attendance processing.

Site Options

License File Path

Directory and file name of the location of the Jobscope license file. The format of this entry

DATACAP

JOBSCOPE Page 21

should be \\servername\folder\jeeflex_server.lic. The application pool identity user will need

read access to this file. If you need licensing set up for DATACAP, contact Theresa Campbell at

[email protected]

Log File Path

Local directory in which the DATACAP error and warning message logs should be saved. For the

installation in this document, the path would be E:\wwwroot\DATACAP\AppData\Logs. This

folder is not created during the initial install. It must be manually added. It must exist in the

web folder for the site. The application pool identity user will need full access to this folder.

Reports File Path

Local directory where the reports files are located. For the installation in this document, the

path would be E:\wwwroot\DATACAP\AppData\Reports.

Company

Enter the value of your customer number. Contact Jobscope Support to obtain this value (e.g.

J0001).

Site ID

Used to identify the DATACAP site in the upload labor process. Usually the first letter of your

customer number (Company) and a one digit number (e.g. J0).

Default Employee Number

Controls whether or not a default Employee Number will be displayed. Leave this field blank.

Min Quantity

Minimum number of units an employee may report to DATACAP as having completed

production before DATACAP will allow the employee to log off of the task. This setting creates a

warning message only.

Max Quantity

Maximum number of units an employee may report to DATACAP as having completed

production before DATACAP will allow the employee to log off of the task. This setting creates a

warning message only.

Scrap Min Quantity

Minimum number of units an employee may report to DATACAP as having been scrapped during

production. This setting creates a warning message only.

DATACAP

JOBSCOPE Page 22

Scrap Max Quantity

Maximum number of units an employee must report to DATACAP as having been scrapped

during production. This setting creates a warning message only.

Multimedia

This controls whether or not the Logon screen will check for multimedia files for the work order

or operation.

Days Ahead

This controls the value that defaults to the Days Ahead field in the Select RWO screen.

Restrict Days

This controls whether or not the Restrict Days Ahead function on the Select RWO screen can be

used.

Logoff Timeout

The amount of time that can lapse before DATACAP automatically logs off a user. This setting

will not logout an employee from a release or task.

User Interface (UI) Options

Enable Logon Task Button

This controls whether or not the Logon Task button will be accessible in DATACAP.

Enable Logoff All Button

This controls whether or not the Logoff All button will be accessible in DATACAP.

Enable Logoff Each Button

This controls whether or not the Log Off button will be accessible in DATACAP.

Enable Suspend/Resume Button

This controls whether or not the Suspend and Resume buttons will be accessible in DATACAP.

Enable Scrap Button

This controls whether or not the Scrap button will be accessible in DATACAP.

Enable Keypad

This controls whether or not the pop up keypad is available. The pop up keypad will be used

with devices that are stylus-driven without a true keyboard.

Enable Small Interface

This controls whether or not the DATACAP session is condensed for smaller displays.

DATACAP

JOBSCOPE Page 23

Text Options

Account

Changes the display name of Account.

Admin

Changes the display name of Admin.

Clock In

Changes the display name of Clock In.

Clock Out

Changes the display name of Clock Out.

Logon

Changes the display name of Logon.

Logoff

Changes the display name of Logoff.

Release

Changes the display name of Release.

Resume

Changes the display name of Resume.

Scrap

Changes the display name of Scrap.

Suspend

Changes the display name of Suspend.

Task

Changes the display name of Task.

Admin Options

Admin User

Changes the administrative user name.

Admin Password

Changes the administrative user password.

After setting all of the DATACAP settings, click the Save button at the bottom of the page to start

DATACAP.

DATACAP

JOBSCOPE Page 24

DATACAP Data Synchronization

After saving the DATACAP settings, DATACAP should load the login screen.

Click the Admin button at the top-left of the main screen. When the administrative login page loads,

provide the administrator username and password and click Login.

Unless you changed the default administrator username and password, the default username is ‘admin’

and the default password is ‘admin’.

On successful login, you will see the DATACAP Dashboard page.

DATACAP

JOBSCOPE Page 25

You should know that you can’t just go in and update the shifts and have the new values take effect

immediately. The old values are cached for quite a while. Even though the database shows the new

values, Datacap is still using the old ones. Eventually when the session times out it will load the new

ones but this will be at least 20 minutes with no activity. The Restart App tab will refresh everything.

When you click on it, it will take you back to the admin login and you will have to log in again.

The Reload Config Table tab reloads options configuration options in the Datacap database. You should

click on both Restart App and Reload Config Table anytime you make a change.

To update the database settings, click the Database (DB) Maintenance button in the menu at the top of

the page.

DATACAP

JOBSCOPE Page 26

In the Sync option of the Database Maintenance dropdown, download the data from the JEE database

specified during installation by checking the tables to download and clicking the Sync Checked button.

For the first data download, you should only check 2 or 3 boxes at a time to prevent the server from

timing out.

Before continuing with the setup, press the DB Maintenance button again to ensure that all of the

controls in the other Database Maintenance tabs are correctly bound to the DATACAP database. You

may need to periodically press the DB Maintenance after adding records like Overtime Schedules or

Account References to make sure that those values bind to controls that reference those tables in

DATACAP.

Initial Setup

The following sequence is recommended to enter valid data into the local server database. This

sequence is recommended because the first items must be created in order to be referenced by the

following items.

Before opening Database Maintenance

DATACAP

JOBSCOPE Page 27

These syncs need to be performed: Employees, Labor Accounts, Scrap Codes and Work Centers. This

copies the valid information on employees, Labor Accounts, Scrap Codes and work centers from the

Employee Master, Table 4004 (Labor Accounts), Table 4009 (Scrap Codes) and the Work Center Master

in JOBSCOPE to the server. This information is necessary for DATACAP to be able to operate.

Change Account References

The initial DEFAULT Account Reference contains empty account values. These must be changed to

accounts that are valid in the LBR_ACCT table, which may be selected from the list in the drop down list

boxes.

Change Overtime Schedules

The initial DEFAULT Overtime Schedule initially contains overtime fences that are set high enough to

prevent overtime from being charged. These fences should be changed to represent valid overtime

fences. If the Overtime Schedule to be used for holidays will not be the DEFAULT Overtime Schedule, a

new Overtime Schedule should be added for holidays.

Change Break Schedules

The DEFAULT Break Schedule initially contains a sample break. Valid breaks should be added along with

a break account valid in the LBR_ACCT table. Breaks that are to be paid must have an account while

unpaid breaks must not have an account assigned.

Change Holiday Schedules

The DEFAULT Holiday Schedule initially contains a sample Holiday Date. Valid dates should be entered

and the other fields should be reviewed.

Change Shifts

Shift 0 is the default shift. Any employee dynamically downloaded to the local database will be assigned

shift 0, so the fields need to be reviewed and updated with valid generic data. If only one shift is used,

then shift 0 should be that shift and should be valid in JOBSCOPE Table 4007. Otherwise, shift 0 should

be omitted from JOBSCOPE Table 4007 to provide a point at which transactions can be identified for

employee’s that are not properly set up.

Change Employees

Employees are added to the local database dynamically by being downloaded from the host the first

time the employee enters a transaction. The shift will default to 0 and other fields will have default

values. In many cases, these defaults will need to be changed to be useful. After going live with the

DATACAP system, it will be easier to manually add the employees to the local database when they are

DATACAP

JOBSCOPE Page 28

added to JOBSCOPE, instead of trying to identify and update employee records as they are dynamically

downloaded.

Update System Configuration

These parameters are used to set several system Configuration options. They need to be reviewed and

changed as appropriate.

Download Online Tasks

Download Tasks should be performed routinely to increase the efficiency of the task process. Once it is

finished initially, DATACAP should be ready to run.

DATACAP

JOBSCOPE Page 29

Database Maintenance

This section describes the different controls that are contained within the various tabs of the Database

Maintenance page. Database Maintenance is the administrative section where edits are performed.

Account References, Overtime, Break, Holiday and Shift Schedules are accessed through the Schedules

tab. Employees, Employee Groups, and Supervisors are accessed through the Employees tab.

TypeCharge and Overhead Accounts are accessed through the Field Services tab. Labor Accounts,

Online Tasks, Scrap Codes and Work Centers are accessed through the Labor tab. Automatic recording of

Holiday and Salary Attendance are accessed through the Automatic Time tab. System Configuration,

Clearing Labor Audit and Transaction Logs, and other DATACAP Services are accessed through the

System tab.

The purpose of this page is to make entries and updates to the DATACAP database. This includes the

parameters that control the operation of the DATACAP system. This section includes basic information

as well as instructions for performing routine maintenance of DATACAP. For information on the initial

setup procedures, see the previous section

From the DATACAP administrator login page, select Database (DB) Maintenance. The Database

Maintenance page displays. The Database Maintenance options can be accessed through the different

tabs on the page. These tabs are:

Sync

Schedules

Employees

Field Services

Labor

Automatic Time

System

Each window is explained in the following sections.

DATACAP

JOBSCOPE Page 30

Sync

This module allows the administrator to manually sync DATACAP’s tables with the corresponding tables

in JOBSCOPE, including:

Security User

Downloads data from the SPT9001 table on JOBSCOPE. Before downloading records from

JOBSCOPE, the existing records in this table on DATACAP are deleted.

Security User Group

Downloads data from the SecurityUserGroup table on JOBSCOPE. Before downloading records

from JOBSCOPE, the existing records in this table on DATACAP are deleted.

Security User Permission

Downloads data from the SecurityUserPermissions table on JOBSCOPE. Before downloading

records from JOBSCOPE, the existing records in this table on DATACAP are deleted.

CSpec Job Cost Account

Downloads data from the CSHEADER table on JOBSCOPE. Before downloading records from


Customer

Downloads data from the CustomerMaster table on JOBSCOPE. Before downloading records


Customer Site

Downloads data from the EPCUSTS table on JOBSCOPE. Before downloading records from


WO Bill Of Material

Downloads data from the DCWOBillOfMaterial table on JOBSCOPE. Before downloading records


Part

Downloads data from the DCPart table on JOBSCOPE. Before downloading records from


Location Code



Material Cost Category



WIP Code



Stock Inventory

Downloads data from the IPINVM table on JOBSCOPE. Before downloading records from


DATACAP

JOBSCOPE Page 31

Material Master

Downloads data from the LPMATRM table on JOBSCOPE. Before downloading records from


Bin Detail

Downloads data from the IPBINDT table on JOBSCOPE. Before downloading records from


Lot Inventory

Downloads data from the LPLOTIV table on JOBSCOPE. Before downloading records from


JEE Option

Downloads data from the SPTBLOP table on JOBSCOPE. Before downloading records from


Job

Downloads data from the DCJob table on JOBSCOPE. Before downloading records from


Labor Account

Starts the program, which downloads the indirect labor account records found in Table 4004

(Labor Collection Accounts) in the production control database of JOBSCOPE to the DATACAP

database. As with the Download Scrap Codes, Download Tasks and Download Work Center

programs, before any accounts are downloaded, all of the accounts currently in the DATACAP

database are deleted.

NOTE: A specific Labor Account must exist in the DATACAP database before an employee will be able to log onto it. Therefore Download Accounts needs to be run any time Labor Accounts are changed in JOBSCOPE.

Scrap

Starts the Download Scrap Codes program, which downloads the valid codes found in the Table

4009 (Production Scrap Codes) in the production control database of JOBSCOPE to the DATACAP

database. Download Scrap Codes deletes all of the Scrap Codes currently in the DATACAP

database before it downloads the Scrap Codes currently in JOBSCOPE.

NOTE: A specific Scrap Code must exist in the DATACAP database before an employee will be able to enter scrap transactions using that code. Therefore, download Scrap Codes needs to be run when Scrap Codes are changed in JOBSCOPE.

Employee

Starts the Download Employees program which downloads Employee information from the

Employee Master in the production control database of JOBSCOPE database to the DATACAP

database. If an employee number is already found in the DATACAP database, only the employee

name and the hourly/salary flag will be updated. If the EmployeeId field is not defined for an

employee, the EmployeeId field is filled in using the employee’s Employee Number, which will

generally only be true if upgrading from an older DATACAP installation. If an employee has been

DATACAP

JOBSCOPE Page 32

marked as terminated on the host that employee will be removed from the DATACAP database.

A filter for Location Code exists so that you can only download employees for your given

location.

NOTE: A specific employee’s record must exist in the DATACAP database to correctly process the transactions. The initial setup for an employee only includes his/her number, name and department, and assignment to shift 0 after a download. In order to reduce the number of error record corrections in JOBSCOPE and increase performance, it is recommended that employees be set up before they start to use DATACAP.

Online Tasks

Starts the Download Tasks program, which downloads Release and Release-Work-Order records

from the Job Master and Operations File tables in the production control database of JOBSCOPE

to the DATACAP database. Only Releases and the related Release-Work-Orders will be

downloaded. Normally, only Release-Work-Orders that have not been completed or secured will

be downloaded, but completed Release-Work-Orders for open Releases can be downloaded by

setting the ACCEPT_COMPLETED_TASKS parameter in the system configuration to ‘Y’. A filter for

Location Code exists so that you can only download tasks for your given location.

Before tasks are downloaded, the existing tasks in the ONLINE_TASKS table are deleted.

Work Center

Starts the Download Work Centers program, which downloads valid work centers from Work

Center Master in the production control database of JOBSCOPE to the DATACAP database.

Before the work centers are downloaded, the existing Work Centers are deleted from the WKCT

table. A filter for Location Code exists so that you can only download work centers for your

given location.

Overtime Code



DATACAP

JOBSCOPE Page 33

Schedules

Schedules are used in the employee records to assign Account References, Overtime, Holiday, Break and

Shift Schedules to be used when calculating transactions for an employee. To simplify maintenance

procedures, Account References, Overtime, Holiday and Break Schedules may be assigned to a shift that

will be assigned to an employee.

When a DATACAP engine needs a value from one of these schedules, it will first check the employee

record to see which schedule is associated with that employee. If the appropriate field is blank in the

employee record, the engine will check the employee’s shift. If the appropriate field is blank in the

assigned shift record, the engine will use the appropriate value that is assigned to Shift 0 (which must

always be defined). The options accessed from the Schedules menu are:

Accounts

Overtime

Holidays

Breaks

Shifts

Each option is explained in the following sections.

DATACAP

JOBSCOPE Page 34

Account References

Account References are used by DATACAP to determine which accounts employee costs will be charged

to. If an employee is active in the DATACAP system, the attendance account will be charged for this

time. Additionally the offsetting labor costs will be charged to the task the employee logged onto or one

of the other accounts in the Account Reference. The Maintain Account References window allows the

addition, maintenance and deletion of Account References.

1. From the Schedules tab, select Accounts to display the Maintain Account References window.

DATACAP

JOBSCOPE Page 35

2. Enter the following information. (Accounts must be valid in JOBSCOPE table 4004, Labor

Collection Accounts).

Account Reference - (10 alphanumeric characters) Enter a name or number to define a

new Account Reference or click one of the schedules listed in the list box at the left of

the window. This name or number will be used in the employee or shift record to assign

the Account Reference to be used for an employee. The Account Reference DEFAULT

may not be already defined in the database. It should be created/modified, but cannot

be deleted.

3. Select the following information from the drop-down list boxes.

Attendance - (28 alphanumeric characters) This is the attendance account for the

Account Reference. Each pair of clock-in and clock-out transactions will generate an

ATTN record that charges time to this account.

Manual Break - (28 alphanumeric characters) This is the manual break account for the

Account Reference. Each pair of suspend and resume transactions will generate an LBRA

record that charges time to this account. However, if this field is left blank, manual

breaks will be treated as unpaid breaks. No transaction will be generated, and the

length of the break will be subtracted from the hours worked in the Attendance Record

and the in-process labor records.

NOTE: Automatic Breaks are charged to an account defined in the Break Schedule.

Holiday - (28 alphanumeric characters) This is the holiday account associated with the

Account Reference. Every transaction that occurs during an attendance period that

begins on a defined holiday is processed as an LBRO record using this holiday account.

Idle - (28 alphanumeric characters) This is the idle account associated with the Account

Reference. This account will be used for LBRA records where an employee is not logged

onto a task and is not on a break. There is always at least one labor charge to this idle

account for each pair of clock-in and clock-out transactions.

NOTE: When Shift and Elapsed Time Rounding occur, this account will have both positive and negative time charges made to it.

Overtime - (28 alphanumeric characters) This is the overtime account associated with

the Account Reference. Employee overtime is charged to this account. If this field

contains CHARGE_TO_TASK, overtime will be charged to the current task instead of the

overtime labor account. The System Configuration ‘Overtime Premium to Overhead’ will

allow the overtime to be split between the task (the standard rate) and this account (the

premium rate). If ‘Overtime Premium to Overhead’ is set to ‘Y’ then this field should

have a valid overtime account, not CHARGE_TO_TASK.

4. Button Functions

New Clears the window and displays the initial values.

Delete Delete the current record from the local database.

Save Saves the current record.

DATACAP

JOBSCOPE Page 36

Overtime Schedules

Overtime Schedules are used by DATACAP to determine the fences and rates to be used for overtime

charges. The Overtime Schedule Maintenance function allows the addition, maintenance and deletion of

Overtime Schedule records.

NOTE: Overtime is for Job Costing purposes only. Overtime for Payroll purposes is determined by JOBSCOPE.

1. From the Schedules option, select Overtime to display the Maintain Overtime Schedules page.

2. Enter the following information.

DATACAP

JOBSCOPE Page 37

Overtime Schedule - (10 alphanumeric characters) Enter a name or number to define a

new Overtime Schedule or click on one of the schedules in the list at the left of the

window. This name or number will be used in the employee or shift record to assign the

Overtime Schedule to be used for an employee. The Overtime Schedule DEFAULT may

not be already defined in the database. It should be created/modified, but cannot be

deleted.

Consecutive Days Overtime Fence -(0-999) The number of consecutive days an employee

must work before becoming eligible for the Consecutive Days Special Rate. For example,

if the consecutive days fence were set to 6, the employee would be paid the regular rate

for six days and would be paid the consecutive days overtime rate on the seventh

consecutive working day. Any subsequent daily or weekly overtime transactions will be

calculated after the consecutive days fence rate is applied. The default is 365. This value

is reset at the beginning of the work week.

Consecutive Days Special Rate - (0 - 999) This is the multiplier for determining the rate

charged for consecutive days in excess of the Consecutive Days Fence. This rate will be

multiplied by the Base Rate from the employee or shift record to determine the actual

rate charged for overtime. The default is 1.0 (no overtime premium).

Day Length – Minimum number of hours an employee must be clocked in to qualify for

consecutive days count.

First Daily Overtime Fence - (0 - 24) The number of hours the employee must work per

day before becoming eligible for the First Daily Special Rate. The default is 24 (no

overtime charges).

NOTE: DATACAP provides for two overtime fences for both daily and weekly overtime. Hours in excess of the first fence but prior to the second fence will be subject to the first daily special rate. Hours in excess of the second overtime fence will be subject to the second daily special rate. For example, suppose the first daily overtime fence was set to 8 and the second daily overtime fence was set to 12. A 14-hour business day would be divided as follows. The first 8 hours would be subject to the normal rate. The next 4 hours would be subject to the first daily special rate. The final 2 hours would be subject to the second daily special rate. For more examples, see “Appendix C”.

First Daily Special Rate - (0 - 999) This is the multiplier for determining the rate charged

for daily hours in excess of the First Daily Overtime Fence, but less than the Second Daily

Overtime Fence. This rate will be multiplied by the Base Rate from the employee or shift

record, or the result of the Consecutive Days calculation to determine the actual rate

charged for overtime. The default is 1.0 (no overtime premium).

Second Daily Overtime Fence - (0 - 24) The number of hours the employee must work

per day before becoming eligible for the Second Daily Special Rate. The default is 24 (no

overtime charges).

Second Daily Special Rate - (0 - 999) This is the multiplier for determining the rate

charged for daily hours in excess of the Second Daily Overtime Fence. This rate will be

multiplied by the Base Rate from the employee or shift record, or the result of the

DATACAP

JOBSCOPE Page 38

Consecutive Days calculation to determine the actual rate charged for overtime. The

default is 1.0 (no overtime premium).

First Weekly Overtime Fence - (0 - 168) The number of hours the employee must work

per week before becoming eligible for the First Weekly Special Rate. The default is 168

(no overtime charges).

First Weekly Special Rate - (0 - 999) This is the multiplier for determining the rate

charged for daily hours in excess of the First Weekly Overtime Fence but less than the

Second Weekly Overtime Fence. This rate will be multiplied by the Base Rate from the

employee or shift record, or the result of the Consecutive Days calculation to determine

the actual rate charged for overtime. The default is 1.0 (no overtime premium).

Second Weekly Overtime Fence - (0 - 168) The number of hours the employee must work

per week before becoming eligible for the Second Weekly Overtime Rate. The default is

168 (no overtime charges).

Second Weekly Special Rate - (0 - 999) This is the multiplier for determining the rate

charged for weekly hours in excess of the Second Weekly Overtime Fence. This rate will

be multiplied by the Base Rate from the employee or shift record, or the result of the

Consecutive Days calculation to determine the actual rate charged for overtime. The

default is 1.0 (no overtime premium).

Processing Priority - This specifies the precedence of the daily and weekly special rates.

(Note: Consecutive Days is always calculated first.) Select one of the following choices

from the drop down list:

Daily first then Weekly - After the First Daily Overtime Fence becomes effective, the

Weekly Overtime Fences are no longer checked for that day. This option does not check

the Special Rates, so it is possible for a larger Weekly Special Rate to be replaced by a

smaller Daily Special Rate when a Daily Overtime Fence becomes effective.

Weekly first then Daily - After the First Weekly Overtime Fence becomes effective, the

Daily Overtime Fences are no longer checked for that week. This does not check the

Special Rates, so it is possible for a larger Daily Special Rate to be replaced by a smaller

Weekly Special Rate when a Weekly Overtime Fence becomes effective.

Maximum of Daily and Weekly - Each time an Overtime Fence becomes effective, its

Special Rate is compared to any other effective Special Rate, and the maximum of these

Special Rates will apply until another Overtime Fence becomes effective. (Note:

“Consecutive Days” is always calculated first.)

Overtime Code – This code will be written to the labor subledger record when it is

created in the Jobscope database.

NOTE: A single transaction may generate multiple labor records when overtime is processed depending on how many Overtime Fences are effective. A Special Rate is an hourly multiplier, not a dollar multiplier.

3. Button Functions


DATACAP

JOBSCOPE Page 39

Delete Deletes the current record from the local database.


DATACAP

JOBSCOPE Page 40

Holiday Schedules

Holiday Schedules are used by DATACAP to record the holiday dates for charges. The Holiday Schedule

Maintenance function allows the addition, maintenance and deletion of Holiday Schedule records.

1. From the Schedules option, select Holidays to display the Maintain Holiday Schedules page.


Holiday Schedule - (10 alphanumeric characters) Enter a name or number to define a

new Holiday Schedule or click on one of the schedules in the list at the bottom of the

window. This name or number will be used to assign the Holiday Schedule to be used for

an employee. The Holiday Schedule DEFAULT may not be already defined in the

database. It should be created/modified, but cannot be deleted.

Holiday Rate – (0-999) This is the multiplier for determining the rate charged for holiday

labor. This rate will be multiplied by the Base Rate from the employee or shift record to

determine the actual rate charged for labor. The default is 1.0.

DATACAP

JOBSCOPE Page 41

Holiday Code – (2 numeric characters) Enter a valid holiday code for the record.

Overtime Schedule – (10 alphanumeric characters) Select an Overtime Schedule to

assign the schedule to be used for the holiday.

Date- (MM/DD/YYYY) Enter a valid date or press the calendar icon to the right of the

date control to select a date from a calendar.

Automatic Hours – (0 - 24) Enter the number of hours of labor for the holiday.

3. Button Functions


Delete Deletes holiday schedule.

Save Saves the holiday schedule.

Add>> Adds the holiday to the holiday schedule

Remove Removes the holiday from the holiday schedule.

You can add holidays to the DEFAULT schedule by clicking on it in the bottom (Holiday Schedule) box.

When it displays, change the date field to the date of the holiday you want to add, and click on the Add

button. The system will display that date in the upper (Holidays) box. Change the date to the next

holiday you want to add and click on Add. Keep doing this until all the holidays you want on the holiday

schedule show in the Holidays box, and click on Save. This will write records to the Holidays table in the

database.

DATACAP

JOBSCOPE Page 42

Break Schedules

Break Schedules are used by DATACAP to determine when automatic breaks occur and how long they

are. If a break is paid, the schedules also determine to which account the break time is charged. When

an employee logs off, all applicable breaks will be deducted from the task(s) they are logging off of and,

if paid, a labor record will be created in the Labor Audit table for those breaks. If a break is unpaid, its

time will be deducted from the Attendance transaction hours.

The Maintain Break Schedules page allows the addition, maintenance and deletion of automatic break

records and schedules.

If you enter a valid account for a break, then the system assumes that the break is paid. If there is no

account, then the system assumes that the break is not paid.

One of the things you need to decide is whether you want the employees to clock out of the system

when they go on break. If you don’t want them to clock out, then simply enter the breaks and leave the

Early Clock Out and Late Clock In at zero and the system will do the breaks automatically.

If you want them to clock out and back in when taking a break, and you want the length of the break to

be based on their actual clock out/in times, and the break is unpaid, then you don’t need a break record

here.

If you want them to clock in and out, and the break is paid, then you need a record here. This is the

situation for which the Early Clock Out and Late Clock In values come into play. Take the case below for

the 10:00 break for 15 minutes. You may want to allow the employees some leeway in the clock out/in

times. If you set the Early Clock Out tolerance to 2 minutes, and the Late Clock In time to 3 minutes, the

an employee can clock out at 9:58 and clock in at 10:18, and still have the break recorded as 15 minutes.

If you want the break calculated as the actual clock out/in times, then leave the tolerances at zero.

You should know that the Start Time is the key to each break record so you can’t change that. If you do

change it and click on Save, the program will think you want to add a new one, and it will create a new

break record with the new Start Time and the same data as in the old record. When you do this, you will

need to delete the old record. This means that, if you want a new break record that is just like one of

the old ones except for the Start Time, you can change the time and click on Save, then decide whether

you want to delete the old one or not. Another way to do it is just to type in all the information for the

new record and click on Save.

DATACAP

JOBSCOPE Page 43

1. From the Schedules option, select Breaks to display the Maintain Break Schedules page.


Break Schedule - (10 alphanumeric characters) Enter a name or number to define a new

automatic Break Schedule or double-click one of the schedules in the Break Schedules list at

the bottom of the window. This name or number will be used in the employee or shift

record to assign the Break Schedule to be used for an employee. The Break Schedule

DEFAULT may not be defined in the database. It should be created / modified, but cannot be

deleted.

Start Time - (HH:MM:SS) This is the time of day at which the automatic break transaction

will start.

Length - (HH:MM:SS) This is the length of the automatic break.

Account - (28 alphanumeric characters) This is the account to which the automatic break will

be charged. Valid accounts are selected from the drop down list box. If this field is left blank,

labor transactions will not be created for the automatic breaks, and DATACAP will treat

them as unpaid breaks. That is, the break’s length will be automatically deducted from all in-

process labor transactions, as with any break, but the break will also be deducted from the

employee’s attendance transaction.

Early Clock Out – The number of minutes early the employee can clock out for the break but

be credited for time up to the beginning of the break. Zero means no tolerance.

DATACAP

JOBSCOPE Page 44

Late Clock In – The number of minutes late the employee can clock in for the break but be

credited for time back to the end of the break. Zero means no tolerance.

3. Button Functions

Save Adds the current break to the current schedule.


Delete Deletes the current break from the local database.

Edit Click on an existing break in the schedule.

Change the start time, length and/or account, and click Save to save the

changes.

DATACAP

JOBSCOPE Page 45

Shifts

Shifts are used by DATACAP to determine when an employee should begin and end work for the day as

well as to assign other schedules to groups of employees. The Maintain Shifts page allows the addition,

maintenance and deletion of Shift Schedules and records.

1. From the Schedules option, select Shifts to display the Maintain Shifts page.

DATACAP

JOBSCOPE Page 46

2. Enter the following.

Shift - (2 alphanumeric characters) Enter a number, letter or combination to define a new

shift or double-click one of the shifts in the list at the bottom of the window. This name or

number will be used in the employee record to assign the Shift Schedule to be used for an

employee. Shift 0 is pre-defined in the database. It should be modified but cannot be

deleted.

NOTE: The shift must be valid in JOBSCOPE table 4007 (Production Shift Codes).

Shift Start Time - (HH:MM:SS) Enter the time the shift is scheduled to start (Using a 24-hour

clock). The default is 00:00:00 (midnight).

Shift Length - (HH:MM:SS) Enter the length of the shift, including breaks. For example, a shift

that starts at 08:00:00 and ends at 17:00:00 with three breaks that total one hour would

have a length of 09:00:00. The default is 00:00:00.

Salary Hours – (HH:MM:SS) Enter the number of standard hours that a salary employee

should be credited with. This value is used by the Salary Attendance program to verify if any

salary hours should be created for the employee or if hours should be reversed for the given

day.

Account Reference - (10 alphanumeric characters) Assign the account reference for the shift

from the valid Account References in the drop-down list box. If this field is blank, the

account reference defined for shift 0 will be used. The default is DEFAULT. This field cannot

be blank for shift 0.

Overtime - (10 alphanumeric characters) Assign the Overtime Schedule for the shift from the

valid Overtime Schedules in the drop-down list box. The default is DEFAULT. If this field is

blank, the schedule defined for shift 0 will be used. This field cannot be blank for shift 0.

Holiday - (10 alphanumeric characters) Assign the Holiday Schedule for the shift from the

valid schedules in the drop-down list box. The default is DEFAULT. If this field is blank, the

schedule defined for shift 0 will be used. This field cannot be blank for shift 0.

Break - (10 alphanumeric characters) Assign the Break Schedule to use for the shift from the

valid schedules in a drop-down list box. The default is DEFAULT. If this field is blank, the

schedule defined for shift 0 will be used. This field cannot be blank for shift 0.

Early Clock-In - (0 - 120 minutes) When an employee clocks-in up to this long before the shift

starts, the clock-in is adjusted to the Shift Start Time by the shift rounding function. The

default is 0.

Late Clock-In - (0 - 120 minutes) When an employee clocks-in up to this long after the shift

starts, the clock-in is adjusted to the Shift Start Time by the shift rounding function. The

default is 0.

Early Clock-Out - (0 - 120 minutes) When an employee clocks-out up to this long before the

calculated end of shift, the clock-out is adjusted to the calculated end of the shift by the

shift rounding function. The default is 0.

DATACAP

JOBSCOPE Page 47

Late Clock-Out - (0 - 120 minutes) When an employee clocks-out up to this long after the

calculated end of shift, the clock-out is adjusted to the calculated end of shift by the shift

rounding function. The default is 0.

Tolerance Between Tasks - (HH:MM:SS) The grace period allowed between tasks without the

employee being logged onto an idle account. If an employee logs off one task and logs on to

another within the amount of time specified, the start time of the second task will be

adjusted to the end time of the first task. Otherwise an idle record will be created. The

default is 00:00:00.

Round Elapsed Time - (HH:MM:SS) Attendance Records will be rounded to this amount of

time if the other shift tolerances have not occurred. That is, if an employee clocks-in or out

outside of the Clock-Out tolerances, the total hours worked will be rounded up or down to

the amount of time set in this field. For example, if 00:06:00 is entered, the total time

worked will be rounded to the nearest tenth of an hour. If the total time worked was 8

hours and 2 minutes, the total time will be rounded to 8 hours. A labor record will be

created charging negative 2 minutes to the employee’s idle account. A rounding labor

record is always generated. The default is 00:00:00.

3. Button Functions


Save Saves the current shift record.

Edit Loads the selected shift into the corresponding controls.


DATACAP

JOBSCOPE Page 48

Employees

The options accessible from the Employees menu provide access to the DATACAP Employee table for

maintenance. DATACAP uses the Employee table to determine holiday and overtime charges, accounts

to use, and breaks to apply, among other things. From the Database Maintenance window, click on

Employees. The Employees tab displays. The options accessed from the Employees tab are:

Employees

Employee Groups

Supervisors

These options are explained in the following sections.

DATACAP

JOBSCOPE Page 49

Employees

The Maintain Employees window allows the addition, maintenance and deletion of employee table

records. These records may also be maintained in the Jobscope Employee Master.

1. From the Employees option, select Employees to display the Maintain Employees page.


Number - (8 alphanumeric characters) Enter or select (from the list at the bottom of the

window) the employee number.

NOTE: The employee number must be valid in the Employee Master of the JOBSCOPE database to pass the edits by the DATACAP Host Processing.

Badge ID - (8 alphanumeric characters) This field will default to the same value as Employee

Number. If you wish to allow users to clock by a number other than their employee number,

DATACAP

JOBSCOPE Page 50

supply the value in this field. The DATACAP functions will verify against the value in badge

number.

Vendor Number – (6 alphanumeric characters) This is the vendor number that the Field

Services program uses to reimburse the employee for expense reports. If you are not using

the expense report function in Field Services, then this should be blank. If you plan to use

the expense report function in Field Services, then a valid vendor number must exist here.

This value should be entered in the employee’s logon record in Jobscope security. The

synchronization program will get this value from the logon record and write it here. When

the vendor number is entered in the logon record, the program will check for a valid vendor

record, but, when the vendor number is entered here, the program will not validate the

vendor number. Therefore, you should first enter the vendor number in the logon record to

insure that it is entered in the logon record, and that the vendor number is valid.

Use Timecard – This flag will indicate whether the employee uses DATACAP or the Online

Timecard for entry of their time. Due to the nature of the time card, an employee should

not change method of entering time during a given week. If an employee needs to change

time entry method, it should be done at the beginning of a new week. Since Salary

Employees may use DATACAP and/or the Online Timecard this flag is used to indicate which

method Salary and Non-Exempt employees may use for job charges.

Name - (24 alphanumeric characters) Enter the name of the employee. If the employee

record is created by downloading from the host, the name is downloaded to this field.

Hourly/Salary/Non-Exempt – Pay Type value from the JOBSCOPE host. This helps determine

if an employee should have time charged through the Salary Attendance program and

whether or not the Cap Salary Time option will affect their time. Non-Exempt employees will

not have their time affected by the Salary Attendance program, including capping the time

but may use either DATACAP or the Online Timecard to collect time.

Shift - (2 numeric characters) Select a valid shift code for the employee from the drop-down

list. The default shift code is “0”.

Group ID - (4 alphanumeric characters) Select a valid primary group from the drop-down list

if one is desired. The default will be the first item shown in the box (or blank if there are no

available groups). The employee may be made a member of many groups using the

Employee Groups function. However, this field is meant to record the employee’s primary

group.

Department - (4 alphanumeric characters) Enter the employee’s department. This field is

optional.

Supervisor - (8 alphanumeric characters) Enter the employee’s supervisor. This field is

optional if there are not entries in the Supervisor’s table. If any entry exists in the

Supervisor’s table, this field becomes an edited drop down and must be supplied with a

valid Supervisor.

Overtime - (10 alphanumeric characters) Select the Overtime Schedule for this employee

from the valid Overtime Schedules in the drop-down list. If this field is blank, the Overtime

Schedule for the employee’s shift is used. The default is DEFAULT.

DATACAP

JOBSCOPE Page 51

Holiday - (10 alphanumeric characters) Select the Holiday Schedule for this employee from

the valid Holiday Schedules in the drop-down list. If this field is blank, the Holiday Schedule

for the employee’s shift is used. The default is DEFAULT.

Break - (10 alphanumeric characters) Select the Break Schedule for this employee from the

valid Break Schedules in the drop-down list. If this field is blank, the Break Schedule for the

employee’s shift is used. The default is DEFAULT.

Account Reference - (10 alphanumeric characters) Select the Account Reference for this

employee from the valid Account References in the drop-down list. If this field is blank, the

account reference for the employee’s shift is used. The default is DEFAULT.

Base Rate Multiplier - (integer). Enter the base rate multiplier for this employee. This is not

the hourly rate for the employee that is found in the Employee Master. Rather, this is just a

multiplier that DATACAP Host Processing uses to generate the hourly transaction entry

according to the following formula: (Base Rate × Hourly Rate × Hours Worked = Labor

Dollars.) This should usually be set to 1.0. Changes in the Hourly Rate should be made in

JOBSCOPE to avoid problems.

Tolerance Between Tasks - (HH:MM:SS) The amount of time allowed between tasks before

the employee is logged onto an idle account. If an employee logs off one task then logs on

to another within the amount of time specified, the start time of the second task is backed

up to the end time of the first task. Otherwise, an idle record will be created. The default is

blank. If this field is left blank, the task tolerance for the employee’s shift is used.

Round Elapsed Time - (HH:MM:SS) Clock-outs will be rounded to this amount of time if they

are outside the tolerances entered above. That is, if an employee clocks out outside of the

Clock-Out tolerances, the total hours worked will be rounded up or down to the amount of

time set in this field. For example, if 00:06:00 is entered, the total time worked will be

rounded to the nearest six minutes or tenth of an hour. If the total time worked was 6 hours

and 45 minutes, the total time will be rounded to 6.83333 hours. A labor record will be

created charging the extra five minutes to the employee’s idle account. A rounding labor

record is always generated. The default is blanks. If this field is left blank, the Round Elapsed

Time from the employee’s shift will be used. If that field is blank, the Round Elapsed Time

from shift 0 will be used.

3. Button Functions

Select Retrieves the employee data given the employee number or Badge ID.

Edit Retrieves the selected employee and loads their data into the controls.




Employee Groups

Employee Groups allow grouping employees at different levels than shifts for reports. Employees can be

included in any number of groups since this is only a reporting tool. The Maintain Employee Groups

page allows the creation of groups and the assignment of employees to those groups.

DATACAP

JOBSCOPE Page 52

1. From the Employees option, select the Employee Groups option. The Maintain Employee

Groups page displays.


Group ID - (4 alphanumeric characters) Enter or select a name or number to define a new

group. This name or number will be used in the Employee Maintenance Record or in the

Employee Groups window to assign the group(s) to be used for that employee. There are no

default groups.

Group Name - (20 alphanumeric characters) The description of the group.

3. Press Select Members and perform the following.

Employee Master List - This is a list of all employee numbers that are not assigned to the

current group.

Group Employee List - This is a list of all employee numbers assigned to the current group.

NOTE: Any updates in these groups will not be reflected in the employee record.

4. To return to the Group selection section, click on Select.

5. Button Functions

Add >> Adds the employee number(s) that are highlighted in the Employee

Master List to the Group Employee List.

<<Delete Deletes the employee number(s) that are highlighted in the Group

Employee

DATACAP

JOBSCOPE Page 53

List from the current group.

Edit Edits the Group ID.

Save Saves the Group ID.

New Creates a new Group ID.

Delete Deletes the current group.

Select Members Moves the focus to the list boxes for assigning employee numbers.

Done Completes the group employee list editing.

DATACAP

JOBSCOPE Page 54

Supervisors

Supervisors will allow you to create the valid entries for Supervisors. If any valid supervisors have been

entered in this table, it will activate the Supervisor Security throughout the system. Supervisor are

maintained in the Jobscope Employee Master, but you can see a list of them here. A user may only edit

transactions for a given employee if they are listed as that employee’s supervisor.

1. From the Employees group, select the Supervisors tab. The Maintain Supervisors page displays.


Supervisor ID - (8 alphanumeric characters) Enter a unique Supervisor ID. The Supervisor

field on the Employee screen will be edited against this value.

Supervisor Name – (24 alphanumeric characters) Enter the name of the current Supervisor.

3. Button Functions

Save Adds the supervisor that is shown.

New Clears the screen for a new transaction.

Edit Edits the selected supervisor.

Delete Deletes the current supervisor.

DATACAP

JOBSCOPE Page 55

Field Services

This section describes the different controls that are contained within the Field Services tab of the

Database Maintenance page.

Overhead Accounts

Overhead Accounts will allow you to create/edit the valid entries for Overhead Accounts. Note that any

edits or additions using this interface will only cause those changes in DATACAP and the changes will not

be reflected in the corresponding JOBSCOPE tables.

1. From the Field Services group, select the Overhead Accounts tab. The Maintain Overhead

Accounts page displays.


Account – (28 alphanumeric characters) Account identifier.

Description – (30 alphanumeric characters) Short description of the account.

3. Button Functions

Save Adds the record typed in the fields.

New Clears the screen for a new transaction.

Edit Edits the selected account.

Delete Deletes the current account.

DATACAP

JOBSCOPE Page 56

Labor

The Labor menu allows you to select options which provide access to the DATACAP labor tables for

maintenance. Any major changes to this data should be done at the host and downloaded to the server

in order to keep the databases synchronized.

Labor Accounts, Scrap Codes, Online Tasks, and Work Centers can all be downloaded from the host.

Before each type is downloaded, the records of that type in the DATACAP database will be erased.

From the Database Maintenance window, click on Labor. The Labor pull-down menu displays. The

options accessed from the Labor menu are:

Labor Accounts

Scrap Codes

Online Tasks

Work Centers

These options are explained in the following sections.

DATACAP

JOBSCOPE Page 57

Labor Accounts

Labor Accounts are used in various DATACAP records, such as attendance, indirect charges, overtime,

and breaks. The Maintain Labor Accounts window allows the addition, maintenance and deletion of

account numbers.

NOTE: These account numbers must be defined in table 4004 of JOBSCOPE and should be downloaded to the server database. However, to make minor changes (assigning work centers) to this table, use this window. Any changes that are not made in table 4004 may not pass edits at the host and will be lost when the next Download Accounts is performed.

1. From the Labor group, select Labor Accounts to display the Maintain Labor Accounts page.


Account Number - (28 alphanumeric characters) This is the unique identifier for the Labor

Account. There are no default accounts, but every account number must be valid in table

4004 in the production control database of JOBSCOPE.

Account Type - (1 alphanumeric characters) This is the account type. All valid types will

appear in a drop-down list. Select from these. The following types are valid: P (primary,

DATACAP

JOBSCOPE Page 58

attendance or direct charge), S (secondary, break or overtime), U (unreported or idle), V

(vacation), I (sick pay), H (holiday), J (jury duty), or O (personal time).

Work Center - (4 alphanumeric characters) This is the work center to be associated with the

account. There are no default work centers.

3. Button Functions

New Clears all fields in the window.


Delete Deletes the current record from the local server database.

Edit Edits the selected record.

DATACAP

JOBSCOPE Page 59

Scrap Codes

Scrap Codes are used when entering a scrap transaction. The Maintain Scrap Codes page allows the

addition, maintenance and deletion of Scrap Codes.

NOTE: These Scrap Codes must be defined in table 4009 of JOBSCOPE and should be downloaded to the server database. However, to make minor changes (Description) to this table, use this window. Any changes that are not made in table 4009 may not pass edits at the host.

1. From the Labor group, select Scrap Codes to display the Maintain Scrap Codes page.


Scrap Code - (2 alphanumeric characters) This is the unique identifier for the Scrap Code.

There are no default Scrap Codes, but the Scrap Code must be valid in table 4009 in the host

database.

Description - (30 alphanumeric characters) Enter the description of the Scrap Code.

DATACAP

JOBSCOPE Page 60

Online Tasks

Online Tasks are the releases or Release-Work Orders on which employees will be working and

therefore to which employees charge their time. The Maintain Online Tasks window allows the addition,

maintenance and deletion of releases and Release-Work Orders.

NOTE: This option has been provided for convenience and is intended for minor or temporary changes (work center, file associations). These tasks should be defined in JOBSCOPE and downloaded to the server database through either the download program or the DATACAP verification procedures. Refer to the “Overview” section for additional information.

1. From the Labor option, select the Online Tasks option. Depending on your selection of Task

Type, your window may look slightly different.


Task Type - Choose one of the following task types from the drop-down list box, enter the

task number and select OK. The appropriate window will display.

Release - A release can have up to 10 characters. A Release-Work Order can have up to 10

characters for the release and 4 characters for the work order. The preceding zeroes are

added to the work order and operation for the employee.

Operation - (4 numeric characters) Enter the desired operation number or select it from the

drop down list.

NOTE: If the JOBSCOPE version uses two character operations (HP 9.5 and 10), the DATACAP interface will automatically translate these 4-character operations into 2-character operations by eliminating the two preceding zeros during the upload.

Work Center - (4 alphanumeric characters) This is the work center associated with this task.

This field is not required but if it is blank, the employees logging onto this task at a terminal

will not be prompted with the default work center.

DATACAP

JOBSCOPE Page 61

Video File - (8 alphanumeric characters for the file name and 3 alphanumeric characters for

the extension) The name of the Video File that is associated with the operation. The file

name is downloaded from the Reference field, in the Operations File in the production

control database of JOBSCOPE. The extension is assigned to downloaded file names from

the System Configuration Options VIDEO_EXTENSION setting.

Drawing File - (8 alphanumeric characters for the file name and 3 alphanumeric characters

for the extension). The name of the Drawing File that is associated with the Work Order. The

file name is downloaded from the Drawing Number field, in the Work Order Master in the

production control database of JOBSCOPE. The extension is assigned to downloaded file

names from the System Configuration Options DRAWING_EXTENSION setting.

DATACAP

JOBSCOPE Page 62

Work Centers

Work centers are used by DATACAP to verify the location of transactions being performed. The Maintain

Work Centers page allows the addition, maintenance and deletion of work centers.

NOTE: This option has been provided for convenience and is intended for minor or temporary changes. Work centers should be defined in JOBSCOPE and downloaded to the server database through either the download program or the DATACAP verification procedures. Refer to the “Overview” section for additional information.

1. From the Labor group, select the Work Centers option. The Maintain Work Centers page

displays.


Work Center - (4 alphanumeric characters) Enter the work center.

Description – (40 alphanumeric characters) An optional field to describe the work center.

DATACAP

JOBSCOPE Page 63

Automatic Time

This section describes the different controls that are contained within the Automatic Time tab of the

Database Maintenance page.

Holiday Attendance

Allows the creation of a batch of generic records for a set number of hours for a given day. When this

option is run the user will be prompted for a date. DATACAP will then match the date entered to all

Holiday schedules, selecting the schedules that contain the date entered as a valid date. Then for each

employee in the EMPLOYEE table on the DATACAP server that has that Holiday Schedule, a transaction

for the automatic hours indicated on the Holiday Schedule will be created in LBR-AUDIT containing the

employee’s Holiday Account based on their Account Schedule. This transaction will be charged using the

Employee’s base rate. Holiday time automatically created may or may not count against overtime

fences. If the system generated Holiday time should not count toward overtime fences then manually

run the Holiday Attendance program the morning of the first working day after the holiday.

If the system generated holiday time should count toward the overtime fences then you can schedule

the process to run which will trigger this calculation. To schedule this process, check the Schedule

Holiday Attendance option in DATACAP’s Configuration. This will allow the download to run in batch

mode through the schedule.

NOTE: If an employee clocks in on a date that is a holiday for that employee, the transaction will be treated as overtime with a rate calculated as the Employee’s Base Rate times the Holiday Rate from their Holiday Schedule record. Any overtime fence that is valid will be applied with the proper overtime rates.

To properly use this option you must perform the following steps:

1. Create your valid Holiday Schedules. This includes setting up the Holiday Schedule with the valid

dates that should be processed as Holidays and then entering the valid Holiday Schedule on

each Employee or each shift.

DATACAP

JOBSCOPE Page 64

2. When the next scheduled Holiday arrives you may run the Create Holiday Attendance program

one of two ways:

Manual Process (Edit Mode)

Ensure that Commit Server has been run through the day preceding the Holiday. Through the

Automatic Time group, click on the Holiday Attendance tab. When the page appears, enter the

date of the Holiday, according to the supplied format. Click the button Go. This will create a

Holiday transaction for all employees that are linked to a Holiday Schedule that has the date

entered. The number of hours that are created is based on the Automatic Hours field of the

Holiday Schedule. Holiday time created this way will not count toward overtime fences.

Scheduled Process (Live Mode)

Check the Schedule Holiday Attendance option in DATACAP’s Configuration. This process will

start one minute after midnight on the date of the Holiday and create a Holiday transaction for

all employees that are linked to a Holiday Schedule that has the date entered. The number of

hours that are created is based on the Automatic Hours field of the Holiday Schedule. Holiday

time created this way will count toward overtime fences.

Salary Attendance

Allows the creation of a charge to an account for Salary employees. When this option is run the user will

be prompted for a date. DATACAP will then search the EMPLOYEE table on the DATACAP server for all

employees marked with a Pay Type of “S” and will generate a charge for that employee for the date

entered. The account used will be the Idle Account from the Employee’s Account Schedule. The number

of hours charged to the account will be calculated as (Salary Hours for the employee) minus (any

charges already in LBR-AUDIT for the date entered). If the System Configuration Option

CAP_SALARY_TIME is set to “Y” the hours charged for a given day will never total more than the

employee’s Salary Hours value. Any charges that causes more time than the Salary Hours will be

reversed. If the System Configuration Option CAP_SALARY_TIME is set to “N” the hours charged for the

a given day will be the total hours worked. Regardless of how the System Configuration is set, if the

salary employee’s clocked time is less than the Salary Hours value a charge to the employee’s Idle

Account will be created for the difference.

DATACAP

JOBSCOPE Page 65

To properly use this option you must perform the following steps:

1. Ensure that your employee’s Pay Type is correctly marked in JOBSCOPE. Run Download

Employees to populate this value on the DATACAP server.

2. Set the System Configuration Option CAP_SALARY_TIME to the appropriate value.

3. Create a Shift Schedule for salary employees with the proper Salary Hours. This Shift should

contain an Overtime Schedule that will generate no overtime.

4. Create an Account Schedule for salary employees with their proper account listed in all account

fields.

5. Update the salary employees with the proper Shift and Account Schedule.

6. Create any exception charges for salary employees for the previous day. If you use Transaction

Editor to create these charges, the previous day’s transactions must be processed by Commit

Sever before running the Salary Attendance program. If you use Absence Entry to create these

charges, you may run the Salary Attendance program at any time.

7. Through the Automatic Time group, select the tab called Salary Attendance. When the page

loads, enter the previous day’s date in the proper format. Click the GO button

DATACAP

JOBSCOPE Page 66

System

The System menu options provide access to the DATACAP system configuration and routine

maintenance programs. From the Database Maintenance window, click on System. The System group

displays. The options accessed from the System menu are:

Configuration

Clear Uploaded Transactions

Clear Audit Log

Configuration

The Configuration options allow viewing and editing of the parameters that control the DATACAP

system.

From the System group, select the Configuration tab. The System Configuration Option page displays.

Click the Edit button next to a parameter to move it to the edit fields. Press the Save button to save any

changes.

DATACAP

JOBSCOPE Page 67

Answer prompts on the following fields.

NOTE: These parameters are case sensitive. When setting an option to ‘Y’ or N, make sure to capitalize it. If the option is set to a number or letter that is not one of the choices (including a small ‘N’ or ‘Y’), DATACAP will use the default setting for that parameter.

WARNING: System configuration settings and their results can be complex. These options are

intended for use by DATACAP System Administrators only. Please review this section carefully before

making any changes to the system configuration.

The following parameters may be set using this window.

ACCEPT_COMPLETED_TASKS

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘Y’ allows labor to be

collected to completed operations within open jobs.

ACCEPT_UNVERIFIED_TASK

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). It has no effect if the RELEASE_VERIFICATION

option is set to ‘N’. Setting this option to ‘N’ ensures that employees are only able to log onto verifiable

tasks. Setting this option to ‘Y’ allows the employee to log onto an unverified task when the host

connection is lost. The verification engine will continue to verify with the host database when necessary

as long as the host connection is open. However, once the host connection is lost, the host database is

no longer considered available. The first employee to log onto a task requiring host verification will be

allowed to log onto that task before the host database is removed from the list of available databases.

Once the host database is removed from the list, unverified tasks will not be accepted.

NOTE: If DATACAP is operating as a stand-alone system, this setting has no effect.

ACCOUNT_NUMBER_LENGTH

This option indicates the number of significant digits DATACAP edits for charges to account. It must be a

number between 1 and 20.

ALLOW_MARK_OPERATION_COMPLETE If enabled, employees will be able to complete an operation without having to supply a quantity. The

supervisor may check or uncheck this box in the approval screen.

ALLOW_OVERRIDE_RWO_WORKCENTER If enabled, employees are able to overwrite the default work center that populates when logging onto a

release or account (this is how it has always been). If disabled, the employee no longer can make a

change to the work center when logging onto a task.

ALWAYS_RESPECT_TOLERANCES

This option should be set to either ‘Y’ or ‘N’ (Default = ‘Y’). It allows you to control when clock in and

clock out tolerances are used. Setting this option to ‘Y” will force the system to use the Clock Out

tolerances even if the employee missed the Clock In tolerances for the given day. Setting this option to

DATACAP

JOBSCOPE Page 68

‘N’ will cause the system to ignore the Clock Out tolerances if the employee missed the Clock In

tolerances for the given day.

BADGE_NUMBER_LENGTH

When logging into Datacap, the system will automatically increment to the next screen when the given

number of characters is supplied. This is in response to us increasing employee number length to 50 as

it used to only do this with 6 character badge numbers.

BUSINESS_DAY_START

This option should be set to a valid time (Default = 00:00:00, format HH:MM:SS). This defines the time of

day at which the accumulators used by the DATACAP verification and commit engines begin counting for

the new day. This option is typically set at a time when the shift that ends the business day is almost

over and before the shift that starts the next business day will start clocking in. Anyone clocking in after

this time will have all of their subsequent transactions (until the start of the next business day) applied

to the new business day.

For example, a site that has three shifts running twenty-four hours a day wants third shift to start the

new business day. Business Day Start is set to 10:00PM. An employee Clocking In on January 8 at

9:00PM will have his time counted on January 8 since he clocked in before Business Day Start. An

employee Clocking In on January 8 at 11:00PM will have his time counted on January 9 since he clocked

in after Business Day Start (even though it was before midnight). An employee Clocking In on January 9

at 1:00 AM will have his time counted on January 9 since it was after Business Day Start for January 9.

CAP_SALARY_TIME

As time is created by the Salary Attendance program, this option defines whether or not salary

employees should receive full credit for hours worked or if the hours should be limited to the Salary

Hours defined on the Shift Schedule. A value “Y” will cause the Salary Attendance program to reverse

any charges that go beyond the appropriate salary hours. A value of “N” will cause the system to credit

all hours worked to the salary employee.

DEFAULT_QTY_COMPLETE_TO_QTY_NEEDED

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). When set to ‘Y’, the Quantity Complete will

default to Quantity Needed. If set to ‘N’, then Quantity Complete will default to 0.

DISPLAY_JOB_TITLE

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). When set to ‘Y’, the Job Title of the Release

will display.

DISPLAY_SHIPTO_NAME

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). When set to ‘Y’, the Ship To Name of the

Release or the Description of the Account will display along with the value. Task fields will also now be

drop down boxes populated with valid entries.

DATACAP

JOBSCOPE Page 69

ENABLE_AUDIT_HRS_ROUNDING

This option should be set to either ‘Y’ or ‘N’. Setting this option to Y allows you to enable rounding of

hours for transactions to the nearest 2 decimals.

ENABLE_OVERTIME

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘Y’ will enable DATACAP

to process overtime. Setting this option to ‘N’ will disable overtime calculations.

HANDLE_SETUP

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘Y’ allows employees to

differentiate between setup time and run time for a Release Work Order. As each employee logs onto a

Release-Work Order, they will be asked if this transaction is setup time. If the employee answers Y, the

hours will be charged as setup time. After completing setup, the employee should logoff of and log back

onto the job as runtime by answering ‘N’ when prompted “Setup (Y/N)?”.

LOGOFF_MULTIPLE

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘Y’ will display the

Logoff Parallel grid when an employee is logged on to parallel tasks. This will allow the user to fill in log

off information in the grid then perform the Log Off function. Setting this option to ‘N’ will force the user

to step through logging off each task one at a time.

MANUALLY_APPROVE_ATTENDANCE

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘Y’ will require

supervisors to approve Attendance records along with charges to jobs and account. Setting this option

to ‘N’ will cause the system to create Attendance records already approved.

MASK_BADGE_NUMBER_ON_ENTRY

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘Y’ will cause the

employee/badge number characters to display as “*” when entered.

MINIMIZE_PROMPTS

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘Y’ will suppress some

of the messages that appear when employees are charging time. For example after performing a Clock

In the message “Clock In for employee was successful” will not appear.

NEW_WEEK_START

This option should be set to a value of 0-6 (0=Sunday, 1=Monday, etc.). (The default is 0.) This option

defines the day of the calendar week on which a new business week will start. The system will consider

any clock-in at or after the START_OF_BUSINESS_DAY on this day of the week to be starting a new

business week.

NO_HOST

This option will control whether Transaction Server will run in regular or No Host mode. A value of “N”

indicates regular mode while a value of “Y” will activate No Host mode for Transaction Server.

DATACAP

JOBSCOPE Page 70

ONLINE_APP_HOST_VERIFICATION

This option controls whether the Online Edit/Approval screen and Online Timecard will verify tasks

against the host database or not. If this option is set to “Y” then any task not found locally in the

DATACAP database will then be verified against the host database.

OVERTIME_ON_TIMECARD

This option will control whether or not an employee can mark an entry on the Online Timecard as

overtime. A value of “Y” will allow the Overtime field to be checked and a rate to be entered. A value of

“N” will disable the Overtime flag.

OVERTIME_PREMIUM_TO_OVERHEAD

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘N’ causes the system

to charge all overtime (i.e. the overtime premium plus the regular rate) to the overtime account

specified in the Account Reference. Setting this option to ‘Y’ causes the system to charge only the

overtime premium to the overtime account and the regular rate to the task. If this option is set to ‘Y’

then a valid account should be entered in the Overtime field of all Account Schedules.

Example: An employee works 5 hours on a job, 2 of which are overtime hours with a multiplier of 1.5. If

this option is set to ‘N’, 3 hours will be charged to the current task at the base rate and 2 hours will be

charged to the overtime account with a rate multiplier of 1.5. If this option is set to ‘Y’, 5 hours will be

charged to the current task at the base rate, and 2 hours will be charged to the overtime account with a

rate multiplier of .5.

PARALLEL_TASKS

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘N’ allows employees to

log onto more than one operation at the same time. The system will divide the hours worked equally

among the multiple operations. See Appendix C for more information.

PERFORM_SKILLS_CHECK

This option is used in conjunction with JOBSCOPE Enterprise Edition and should be set to either ‘Y’ or ‘N’

and is in effect when logging on to a Release/WO/Op. Setting this option to ‘Y’ will edit the employee’s

valid skills against the skills needed to perform the operation. If the employee has the skills necessary

they will be logged on. If the employee does not have the skills necessary, they will be stopped with a

message, “Invalid. Skills Requirement not met.” Setting this option to ‘N’ will perform no additional

edits.

PROMPT_FOR_QTY

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). Setting this option to ‘Y’ will cause the

system to prompt the user for a Quantity Complete when logging off a release, work order, and

operation task.

QUANTITY_TRACKING

This option should be set to either ‘Y’ or ‘N’. Setting this option to ‘Y’ allows DATACAP to download and

keep track of quantity required to complete operations.

DATACAP

JOBSCOPE Page 71

RELEASE_VERIFICATION

This option should be set to either ‘Y’ or ‘N’. (Default = ‘Y’) Setting this option to ‘Y’ causes the system to

verify releases and Release-Work Order before logons are processed. The system attempts to verify first

on the server, and then the host. Setting this option to ‘N’ will turn this verification off. After the data is

uploaded; however, the DATACAP Host Processing will still attempt to verify these transactions. If this

option is set to ‘N’, a drastic increase in the number of invalid transactions that are found on the host

after the data has been uploaded should be expected.

REQUIRE_OPERATION_FOR_RWO

This option will control whether or not an Operation is required to charge labor to a Release and Work

Order. Setting this option to “Y” will cause the system to require an Operation Number when a Work

Order is supplied. Setting this option to “Y” will allow the user to supply a Release and Work Order but

not require an Operation number.

REWORK_ON_TASKS

This option will indicate if the user can report ‘rework’ on tasks. Setting this option to “Y” will allow the

user to indicate if the labor is rework by checking a box when logging onto the task. The system will

allow the shop employee to log on to a completed task as long as the Rework box is checked. Setting

this option to “N” will now allow the user indicate the labor is rework and all normal edits will be

respected.

SETUP_QUANTITY

This option should be set to either Y or N (Default = N). This option has no effect if the HANDLE_SETUP

option is set to ‘N’. Setting this option to ‘Y’ will result in employees being prompted for the quantity

completed when they logoff of a setup transaction. This is useful when an employee may complete one

(or more) units during the setup process.

SUPERVISOR_APPROVAL

This option should be set to either Y or N (Default = N). This option controls whether or not labor

transactions collected through DATACAP must be approved from the Online Approval – Edit screen. If

this option is set to ‘N’ the DATACAP transactions can be committed by Commit Server and uploaded to

the host as usual. If this option is set to ‘Y’ then the transactions collected by DATACAP and committed

by Commit Server must be approved from the Online Approval – Edit screen before they will be eligible

for upload. All records from the Online Time Card must be approved from the Online Approval – Edit

screen as this is the only process for review that exists for those transactions.

SUSPEND_RESPECTS_BREAK_SCHEDULE

This option should be set to either Y or N (Default – N). This option controls whether the Suspend

functions still allows time to be diverted to scheduled breaks, paid or unpaid, or not. If this option is set

to ‘N’ the time the employee is suspended will be charged to the Manual Break account regardless of

scheduled breaks. If this option is set to ‘Y’ the time the employee is suspended will still have the

appropriate breaks taken out and charged to the appropriate account, if any.

DATACAP

JOBSCOPE Page 72

WEEKLY_OVERTIME_BY_TOTAL_HOURS

This option should be set to either ‘Y’ or ‘N’ (Default = ‘N’). When set to ‘N’, the weekly overtime

calculations for each employee are based only on the number of regular hours they have worked during

the week. Daily overtime hours are disregarded. Setting this option to ‘Y’ will result in each employee

having weekly overtime calculated using the total number of hours worked during the week whether or

not they have already had Daily overtime calculations applied to some of those hours. See Appendix C

for more information.

Clear Uploaded Transactions

When records are uploaded from the DATACAP server to the host, the records are not erased from the

server. Clear Uploaded Transactions erases all, or some (based on date), of these records from the

server Database. This should be done on a regular basis, depending on the number of transactions

generated and the free disk space on the server.

WARNING Do not run Clear Uploaded Transactions while Host Audit Copy is running. Make sure the

Host Audit Copy program is shut down before proceeding.

1. From the System group, select the Clear Uploaded Transactions tab. The following page will

prompt for a stop date. The program will delete all of the successfully uploaded records through

this date.

2. Enter the date and click OK.

When Clear Uploaded Transactions is completed, the message displays telling you the records were

deleted.

Clear Audit Log

DATACAP

JOBSCOPE Page 73

When changes are made from the Online Approval page, there is a record of the ‘before’ and ‘after’

transactions stored in an Audit Log table along with the date of the change and the ID of the user

making the change. Clear Audit Log erases all, or some (based on date), of these records from the server

Database. This should be done on a regular basis, depending on the number of transactions generated

and the free disk space on the server.

1. From the System group, select the Clear Audit Log tab. The following page will prompt for a

stop date. The program will delete all of the successfully uploaded records through this date.

2. Enter the date and click OK.

DATACAP

JOBSCOPE Page 74

Services

The Services tab allows you to access the various services available in DATACAP.

This section provides a description of what will happen when each item executed or modified in the

Services tab.

Commit Server

To change the Commit Server to “Live Mode”, change the Run Interval [seconds] to a value greater than

zero. This will execute the Commit Server at the provided interval. The Commit Server loads the commit

engine, which performs calculations on the transactions in TRXQUE. It then places the finished

attendance and labor records in the LBR-AUDIT table where they will be stored awaiting upload to the

host. Transactions cannot be edited using the Transaction Editor if the Commit Server is operated in Live

Mode because all records will be processed as they are created.

If you have the Commit Server Run Interval set to zero, you will need to run the Commit Server Run

Now process manually at regular intervals to process the edited transactions, along with all completed

transactions and write the resulting records to the LBR_AUDIT table in DATACAP. To run this process,

click the Go button next to the Commit Server - Run Now label. Only those records that have a Time

DATACAP

JOBSCOPE Page 75

Stamp date on or before the date entered will be processed. The ending time for transactions processed

will be the Business Start time of the date entered. If running DATACAP manually, this server must be

run on a regular basis (usually daily but at least weekly) to process transactions that have been

collected, possibly edited using the Transaction Editor, and verified.

Downloads – DATACAP Table Synchronization

To bulk synchronize all of the DATACAP tables with JOBSCOPE, press the Go button next to the

Download – Run Now label. The download process can also be scheduled to execute at a specific

interval by typing a time greater than zero in the Download – Run Interval [seconds] textbox. To

disable the automatic download of information from JOBSCOPE, set the Download – Run Interval to 0.

Uploads - Host Audit Copy

Host Audit Copy starts the processing of records in LBR_AUDIT with a Record Status of 0 and writes

them to the AUAUDIT table in the Jobscope host database (ZPAUDIT on the AS400). Host Audit Copy

can be executed manually by pressing the Go button next to the Upload – Run Now label or can be

scheduled to execute at specific intervals by typing a time greater than zero in the Upload – Run Interval

[seconds] textbox. To disable the automatic execution of the Host Audit Copy process, set the Upload –

Run Interval to 0.

NOTE: The Host Audit Copy process should be run regularly, at least once a week. It simply formats and copies the data in LBR_AUDIT to the host. To clear the successfully uploaded records, the Clear Uploaded Transactions page under the System tab must be used to clear the transaction log.

DATACAP

JOBSCOPE Page 76

Supervisor

This section describes the functions available in the Supervisor Terminal. The Supervisor Terminal is

accessible either by logging in with supervisor credentials or by logging in as an administrator and

clicking the Supervisor button in the administrator toolbar.

Online Approval

The purpose of this program is to allow the edit and approval of labor transactions that have been

collected from the Online Timesheet or have been collected through DATACAP but subsequently

committed. Once the System Configuration Option “Supervisor Approval” is set to “Y”, committed labor

transactions will not be uploaded to the Host until they have been approved through this screen. After

selecting Online Approval, the page will appear:

This is the approval screen.

Here’s a close-up view of the transaction to be approved.

DATACAP

JOBSCOPE Page 77

It should be noted that the transactions collected from DATACAP have already been committed so

changes from this screen will not affect overtime fences, etc. that Commit Server maintains. The records

for an employee’s given day or week will need to be formatted as needed before they are uploaded to

the host.

The records to be reviewed can now be selected by filling in:

Date– this will be the date for which time is to be reviewed

Show All Unapproved Transactions – this option will ignore the date criteria and show all

transactions that have not been previously approved

Shift – this will limit the selection to a particular shift or if left blank will select all shifts

Supervisors – this field will not display unless the supervisor has the Allow to Review All box

checked on the Supervisor screen.

Once the selection criteria have been supplied the supervisor clicks Select. A list of employees that are

eligible for edit will appear in the left hand display. Once the supervisor selects an employee, their labor

records for the given date will appear on the right hand display.

The supervisor may now edit, delete, or create transactions in this right hand display. To add a new

transaction click ADD and the Add Transaction window will appear. The supervisor will select the type of

transaction being added, fill in the appropriate information and then click OK. To delete an entry single

click the header column for the row in the grid and then click the DELETE button.

The Notes section of the screen will show any notes that have been created for the given transaction.

Since the data being reviewed from this screen has either come from the Online Timesheet or has been

committed as collected from DATACAP, any changes done on this screen will not affect the overtime

fences. The data will be passed to JOBSCOPE as it appears on this screen. The screen will maintain the

transactions as they appear on the screen.

Once the records are defined as desired the supervisor may now approve transactions as needed. If the

supervisor checks the Approve All box all transactions will be updated as approved and will be available

for upload to the Host. No task verification is done on an approval. It is assumed that the charge was

valid at the time of entry and that it should still be processed as it is.

Records created from the Online Timesheet must be reviewed and approved from this screen before

they will be eligible for upload to the host machine.

This is what the display looks like with data. Transactions are approved by checking the box on the left

and clicking on the Update Approvals and Values button.

DATACAP

JOBSCOPE Page 78

To add a new charge, click the Add New button at the bottom. When adding a new charge, select the

Trans Type for the charge. If you select Account, the Task/Acct will be the indirect labor account, and

the work center should default in. If you select Release, the Task/Acct field will be a job or release and

you must select a work center. If you select RWO, the Task/Acct will be a job/release, work order, and

operation. As you manually enter this value, you can use a period as a separator. You must enter a

work center but you can change it. Once the fields have been filled in, click SAVE. You can alter existing

charges but click the Update Approvals and Values button.

DATACAP

JOBSCOPE Page 79

Reports

The DATACAP Reports folder contains the following list of reports. Please note that if a report name is

followed by a “(C)” this indicates that the report shows only data that has been passed through the

Commit Server.

DATACAP

JOBSCOPE Page 80

Absentee Report

Attendance Detail (C)

Employee Detail

Employee Time Sheet (C)

Exception Report

Exception Report - Committed

Labor Detail (C)

Online Tasks

Overtime Report (C)

Labor Audit Transaction Register Report (C)

Transaction Edit Log Report

Transaction Queue Register Report

Work In Process

Unapproved Time (C)

Note: The Date Range selection criteria will always be the focus when the report prompt screen appears. Due to a limitation in Crystal Reports, the default Beginning and Ending date will be the current date. Please verify your dates before requesting your report.

DATACAP

JOBSCOPE Page 81

Absentee Report

The Absentee Report lists the employees that are absent for the day the report is run. You can select by

shift or by supervisor. The submit screen displays. Enter a shift and/or supervisor and click Execute.

The following information displays on the report:

Shift – The Shift that the subsequent employees are assigned to.

Employee/Badge Number - The current employee/badge number.

Employee Name – The name associated with the employee/badge number.

DATACAP

JOBSCOPE Page 82

Attendance Report

The Attendance Detail report lists attendance transactions that have been processed by the Commit

Server. You can select by Date Range, Employee or Badge Number, Shift, or Supervisor. You can also sort

by Employee/Badge or Date.


Date - The date for each Attendance Record.

Employee/Badge Number - The current employee/badge number.

Attendance Account - The account number to which the record is charged.

Hours - The attendance hours for the employee for the record.

Total for Employee # or Date (depending on the sorting method used) - Total hours by date or

employee.

Report Total – The total hours for all employees and dates specified.

DATACAP

JOBSCOPE Page 83

Employee Detail Report

The Employee Detail Reports list all of the information about the settings that are used by DATACAP to

make calculations. These settings are associated with an employee using the Maintain Employees and

Maintain Shifts windows of Database Maintenance. You can select by Employee or Badge, Group,

Department, Supervisor, or Shift. You can also sort by Employee/Badge, Group, Department, Shift, or

Supervisor.


Employee ID - The current employee’s number.

Employee Name - The name that is associated with the employee/badge number.

Group ID - The group that is associated with the employee.

Base Rate - The base rate multiplier that is associated with the employee.

Department - The department number that is associated with the employee.

Task Tolerance - The Between Task Tolerance that is associated with the employee, their shift or

shift 0.

Supervisor - The supervisor that is associated with the employee.

Clock-Out Round - The Round elapsed time that is associated with the employees, their shift or

shift 0.

Shift - The shift that is associated with the employee.

Shift Start - The time the shift is scheduled to begin.

Shift Length - The scheduled length of the shift.

Shift End - The calculated time the shift is scheduled to end.

DATACAP

JOBSCOPE Page 84

Early Clock-In Tolerance – The tolerance for early Clock-Ins that is associated with the shift.

Early Clock-Out Tolerance – The tolerance for early Clock-Outs that is associated with the shift.

Late Clock-In Tolerance- The tolerance for late Clock-Ins that is associated with the shift.

Late Clock-Out Tolerance- The tolerance for late Clock-Outs that is associated with the shift.

Account Reference - The Account Reference associated with the employee, their shift or shift 0.

The following fields are copied from the Account References record.

Overtime Account - The account assigned for use with the employee’s overtime transactions

(LBRO).

Holiday Account - The account assigned for use with the employee’s holiday overtime work

transactions (LBRO).

Attendance Account - The account assigned for use with the employee’s attendance

transactions (ATTN).

Idle Account - The account assigned for use with the employee’s idle time transactions (LBRA).

Suspend Account - The account assigned for use with the employee’s manual break transactions

(LBRA).

Overtime Schedule - The Overtime Schedule associated with the employee, their shift or shift 0.

The following fields are copied from the Overtime Schedule record.

Daily Hours 1 – The number of work hours in a business day before the first daily fence will

activate for the employee.

Daily Rate 1 – The rate multiplier the employee will have calculated while the first daily fence is

active.

Daily Hours 2 – The number of work hours in a business day before the second daily fence will


Daily Rate 2 – The rate multiplier the employee will have calculated while the second daily fence

is active.

Weekly Hours 1 – The number of work hours in a business week before the first weekly fence

will activate for the employee.

Weekly Rate 1 – The rate multiplier the employee will have calculated while the first weekly

fence is active.

Weekly Hours 2 – The number of hours in a business week before the second weekly fence will


Weekly Rate 2 – The rate multiplier the employee will have calculated while the second weekly

fence is active.

Sequential Days – The number of consecutive days the employee will have to work before the

Consecutive days fence will activate.

Sequential Days Rate – The rate multiplier the employee will have calculated while the

Consecutive days fence is active.

Processing Order - The processing priority for the overtime record.

Holiday Schedule - The Holiday Schedule associated with the employee, their shift or shift 0. The

following fields are copied from the Holiday Schedule record.

Holiday Rate - The holiday work hours rate multiplier for the employee.

DATACAP

JOBSCOPE Page 85

Holiday Dates - The dates of the holidays for the employee.

Holiday Overtime Schedule - The Overtime Schedule that is associated with the Holiday

Schedule. See the above description of the fields for the base Overtime Schedule as these fields

perform the same functions. On a holiday, the Overtime Schedule rate multipliers will be applied

after the holiday rate multiplier is applied. Often, an Overtime Schedule with no possible

overtime fences is desirable for this reason.

Break Schedule - The Break Schedule associated with the employee. The following fields are

copied from the Break Schedule record.

Start - The scheduled start time for each break.

Length - The scheduled length of the break.

Account - The account assigned for use when calculating the break.

DATACAP

JOBSCOPE Page 86

Employee Status Report

This report lists the status of the employees, whether clocked in or not clocked in.

The following information displays on the report.

Employee Number – The Employee’s number.


Employee Status – Whether the employee is clocked in or not clocked int

Task - If the employee is clocked in, it lists the task on which the employee is working.

DATACAP

JOBSCOPE Page 87

Employee Summary Report

This report lists data about the employee.


Employee – The employee number


Shift – the shift to which the employee is assigned.

Supervisor – The employee’s supervisor.

Acct_Ref – The account reference for the employee.

OT_Sched – The overtime schedule for the employee.

Brk_Sched – the break schedule for the employee.

DATACAP

JOBSCOPE Page 88

Employee Time Sheet (C)

The Employee Time Sheet reports list the labor transactions for a specified employee or shift in a time

sheet format. It only retrieves information that has been processed by the Commit Server. You can

select by Date Range, Employee or Badge, Supervisor, or Shift.



Employee/Badge Number - The employee/badge number entered when the report was run.

Date - The Clock-In date for the labor transactions.

Transaction - The transaction information (release, Release-Work-Order, or account number).

Start - The start time for the transaction.

Stop - The end time for the transaction.

Wkct - The work center associated with the transaction.

Rate - The rate multiplier for the transaction.

Qty - The quantity completed during the transaction.

Hours - The number of hours for the transaction.

Total Labor Hours - The total number of labor transaction hours for the employee on this date.

(This field should match Total Attendance Hours).

Total Attendance Hours - The total number of attendance transaction hours for the employee on

this date. (This field should match Total Labor Hours).

Employee Verification - This is provided so the employee can verify the report by signing or

initializing.

Supervisor Verification - This is provided so the supervisor can verify the report by signing or

initializing.

DATACAP

JOBSCOPE Page 89

Employee With No Activity

This report lists employees that are clocked in but not on a task.


Employee – The employee number


Shift – the shift to which the employee is assigned.

Supervisor – The employee’s supervisor.

DATACAP

JOBSCOPE Page 90

Exception Report Committed

The Exception Report Committed lists employees who have clocked in early or late, have clocked out

early or late, or haven’t clocked in or out for a given date. This report is based on data that has been

processed by Commit Server. You can select by Date Range, Supervisor, or Shift.


Employee - The number for the current employee.

Name – The name of the employee.

Type - The comments or explanation of the exception.

Time Stamp – The date and time of the transaction.

DATACAP

JOBSCOPE Page 91

Exception Report

The Exception Report lists employees who have clocked in early or late, or have clocked out early or late

on the current date. You can select by Date Range, Supervisor, or Shift.


Employee/Badge Number - The number for the current employee.

Name – The name of the employee.

Date - The date on which the exception occurred (current date).

Type - The comments or explanation of the exception.

Shift - The employee’s assigned shift.

DATACAP

JOBSCOPE Page 92

Idle Employees

This report lists employees who are clocked in, but not currently assigned to a task.


Employee – The Employee Number

Name – The Employee Name

Time Clocked In – The time the employee clocked in

Dept – The department to which the employee is assigned

Supervisor – The employee’s supervisor

DATACAP

JOBSCOPE Page 93

Labor Audit Edit Log

The Transaction Edit Log Report is a list of the transactions that have been changed through Transaction

Editor by a Supervisor. The report shows the information from before the change, the information after

the change, when the change was done, and by which Supervisor the change was made. You can select

by Date Range, Employee or Badge, or Supervisor. Please note that you must be using Supervisor

Security for this report to have useful information and this report does not load with the Supervisor’s

Terminal since it is an Administrative Audit report.

The following information is displayed on the report:

Employee/Badge Number - The employee/badge number displays.

Flag – The state of the current transaction when the logging was done. BEFORE indicates the

record before the change, AFTER indicates the record after the change, ADD indicates a record

created from scratch, and DELETE indicates a record was deleted.

Task - The task number for the transaction.

Work Center - The work center associated with the transaction displays.

Appv? – Y or N to indicate whether the transaction has been approved.

HRS Work – The time for the task.

Supervisor – The Supervisor that made the change.

Date of Change – The Date and Time that the change was made.

DATACAP

JOBSCOPE Page 94

Labor Audit no ATTN

This is a special purpose report that lists employees that are clocked on but have no attendance record,

which is a scenario that should not occur.

DATACAP

JOBSCOPE Page 95

Labor Audit Transaction Register (C)

The Transaction Register (Audit Table) lists the records that have and have not been uploaded to the

host. Records that have not yet been committed cannot be uploaded and thus are not relevant to this

report. You can select by Date Range, Shift, Employee or Badge, or Supervisor.


Employee - The current employee/badge number.

Serial Number - The serial number associated with the record.

Status - The upload status. (0 = upload not attempted yet, 1 = has been uploaded to the host

successfully, 1000 = the upload program encountered an error while trying to write the record

to the host).

Type - The type of record. (ATTN = attendance, LBRA = labor account, LBRO = labor overtime,

LBRR = labor release, LBRS = labor setup, LBRW = labor Release-Work-Order, SCRP = scrap)

Time Stamp – The time stamp of when the record was created.

Hrs Worked – The time for the task.

Quantity Complete – The quantity of pieces reported.

DATACAP

JOBSCOPE Page 96

Labor Detail (C)

The Labor Detail Report lists only transactions charged to releases, Release-Work-Orders, and Labor

Accounts. Totals are shown for each employee. This report only displays information that has been

committed by the Commit Server. You can select by Date Range, Task, Employee or Badge, Supervisor,

or Shift. You can also sort by Employee/Badge, Task, or Date.



Date - The date the labor transactions were performed.

Task - The associated number for the transaction.

Start Time – The start time for the task.

Stop time – The end time for the task.

SUBM? – A Y or N to indicate if the task has been submitted for approva.

APPV? – A Y or N to indicate if the task has been approved.

UPL? – A Y or N to indicate if the task has been uploaded.

Work Center - The work center where the labor was performed.

OT Code – The overtime code that may have been assigned to the transaction.

Quantity - The quantity completed during this transaction.

Hours - The number of hours worked during this transaction.

Total by Date - The total number of hours worked for the given date.

Report Total - Total number of hours worked for this report.

DATACAP

JOBSCOPE Page 97

Labor Detail Errors

The LBR_AUDIT.REC_STATUS field normally is 0 when a record has not been uploaded to Jobscope and is

changed to 1 when it has. However, if there is an error with the record (normally because the serial

number already exists in AUAUDIT) it will update the REC_STATUS to 1000. This report shows any

records with a REC_STATUS = 1000



Date - The date the labor transactions were performed.

Task - The associated number for the transaction.

Start Time – The start time for the task.

Stop time – The end time for the task.

Appv? – A Y or N to indicate if the task has been approved.


OT Code – The overtime code that may have been assigned to the transaction.

Quantity - The quantity completed during this transaction.

Hours - The number of hours worked during this transaction.

DATACAP

JOBSCOPE Page 98

Labor Summary

This is the Labor Detail report summarized by employee.

DATACAP

JOBSCOPE Page 99

Online Tasks

The Online Tasks report is a list of all valid releases and release-wo-ops in the DATACAP database. You

can select by Release or by all Releases.


Release-WO-Op - The associated number for the task.


Qty Required – The quantity required during this task.

Qty Complete - The quantity completed during this task.

Descriptioin – The description for the task.

DATACAP

JOBSCOPE Page 100

Overtime Report

The Overtime Detail Report lists all overtime transactions. Totals are shown for each employee. This

report only displays information that has been committed by the Commit Server. You can select by Date

Range, Employee or Badge, Shift, or Supervisor. You can also sort by Employee/Badge, Task, or Date.

The following information is displayed on the report:

Employee - The employee/badge number displays.

Uploaded – A Y or N to indicate if the task has been uploaded.

Date - The overtime date displays.

Overtime Account - The overtime account number displays. If this field displays,

“CHARGE_TO_TASK”, overtime has been charged to the task the employee was logged onto

during overtime.

Task – The task for the transaction.

Hours - The overtime hours earned displays.

OT Code – The overtime code entered for the transaction.

Report Total - The total number of hours for this report displays.

DATACAP

JOBSCOPE Page 101

Transaction Edit Log

This is an old report which looks at the AUDIT_LOG table which is no longer used.

DATACAP

JOBSCOPE Page 102

Transaction Queue Register

Normally TRXQUE is run on an interval but if you run it manually, this report will show a list of all

pending transactions in TRXQUE that will be processed. It also identifies if there are any records stuck

due to a data issue.


Employee - The employee number displays.

Type – The type of transaction (LBRA (Labor Account), LBRR (Labor Release), LBRS (Labor Setup),

LBRO (Overtime), and LBRW (Labor Release-Work-Order).

Task – The task for the transaction.

Date – The date for the transaction.

Time – The time for the transaction.

DATACAP

JOBSCOPE Page 103

Unapproved Time (C)

The Unapproved Time report prints an online display of committed labor that has not been approved by

the Supervisor Approval process, if used.


Employee - The employee number displays.

Supervisor – The supervisor for the employee.

Shift – The shift for the transaction.

Date/Time - The date and time of the transaction.

Task – The release, Release-Work-Order, or account number.

Start Time – The Start Time of the transaction.

Stop Time – The Stop Time of the transaction.


OT Code – The overtime code entered for the transaction.

Quantity – The quantity complete on the transaction.

Hours – The hours worked on the transaction.

DATACAP

JOBSCOPE Page 104

Work In Process (WIP)

The Work In Process report prints an online display of work in process for all employees that are

currently clocked in.


Employee/Name - The employee number/name displays.


Clock in Date/Time – The date time for the transaction clock in.

Task Type - The description of the task (Release, Release/WO/Op, Account, Overtime).

Task – The release, Release-Work-Order, or account number.

DATACAP

JOBSCOPE Page 105

Upgrading

Depending on what version you are upgrading from, the first difference will be that the Datacap database is now upgraded through Server Administration Utility just like the Jobscope database.

You will select the version you are upgrading to and will perform the upgrade in the same way you upgrade a Jobscope database.

Once the upgrade has completed, there will be some settings you will need to update.

DATACAP

JOBSCOPE Page 106

Jobscope System Configuration

In System Utilities, go to System Configuration – Shop Floor Control – Production. Check the box to Use Scheduling (if not already checked) and click Apply.

Next, go to Operations – Table Maintenance – Production Shift Codes. If you have not already set up your shifts in Jobscope, you must do so now. If you already have, be sure that the start and end times are set in 24 hour mode. You must enter a value in Calendar Duration and Hours Available but are not used by the Datacap system. If you are not using scheduling, you can just set these values to the length of the shift.

Once you have done this, you can disable scheduling but will need to turn it back on to make changes here. You can also choose to leave scheduling enabled and restrict access.

DATACAP

JOBSCOPE Page 107

Next, go to System Configuration – Shop Floor Control – Datacap. Enter the Datacap Server Name, Datacap Database Name and a valid SQL user/password in the grid at the bottom. Be sure the Active box is checked as well. You can leave the top section as is.

DATACAP

JOBSCOPE Page 108

Supervisors

Supervisors and Shifts are now set in Jobscope. They will download to Datacap whenever Sync is run. In Resources – Employees, you will check the option for supervisor on the employee record. If you do not see this check box, be sure you have enabled it in Security.

DATACAP

JOBSCOPE Page 109

Once you have enabled this check box, you can assign the supervisor to employees using the Supervisor Id dropdown:

Be sure that you also set the Normal Work Shift. This is the Production Shift Code table we set up earlier.

You can use the Grid Edit tool to assign these values to employees quicker.

DATACAP

JOBSCOPE Page 110

Once you have set up your supervisors in Jobscope, you need to assign them to a Jobscope User. In System Utilities – Security Users, assign the Employee to the Jobscope User from the dropdown. You may already have this set up.

When a supervisor goes to log into Datacap, they will use their Employee Number and Jobscope Password. If you use Windows authentication, they will use their Employee Number and their Windows Password.

DATACAP

JOBSCOPE Page 111

Routine Maintenance

DATACAP Server

Downloading Data

Employees, releases, tasks, etc. on the server must match the data present in the JOBSCOPE system

located on the host. To this end, the DATACAP Administrator should download new online tasks on a

daily or weekly basis, depending on the volatility of the data. Since work centers and employees change

less often, they can be downloaded less often. If the DATACAP Administrator doesn’t routinely

download data from the host, some transactions may be considered invalid by the server, even when

the data is valid on JOBSCOPE.

NOTE: Process time is dependent upon the size of the database, speed of the host, speed of the server, and the type of connections between the DATACAP server, the terminals and the host.

Host Systems

NOTE: The following information is common on all platforms; please refer to AS/400 Specifics or JEE Specifics for more information.

Audit File

Transactions sent to the host system are written to the Audit File. The size of this file must be monitored

and it should be cleared on a regular (monthly) basis using the Reset Audit option in the DATACAP

menu. Every record that is uploaded by the DATACAP server is written to the Audit File. However, the

host Reset Audit application deletes only those records that have been successfully processed.

Attendance File

Attendance Records that are sent to the JOBSCOPE host as part of successful transactions are recorded

in the Attendance file. The Attendance file is currently used only for verification of the accuracy of the

labor transactions uploaded from DATACAP. It should be monitored and cleared on a regular (monthly)

basis.

Error Transactions

Transactions that are not valid in JOBSCOPE at the time they are received and processed on the host are

retained in the AUDIT file with an error status. The Correct Error Transactions application on the host

will list the records with an error status and allow them to be corrected. It is essential that a DATACAP

Administrator investigates and edits the failed transactions on a daily basis, so that JOBSCOPE can

present a true job cost analysis.

Hourly Transaction File

Labor records that are processed by the JOBSCOPE host successfully are written to the Hourly

Transaction File. The Hourly Transaction File is currently used for all automated payroll interfaces due to

DATACAP

JOBSCOPE Page 112

the fact that correcting entries that are made in the Labor Entry window of JOBSCOPE are posted here.

It should be monitored and maintained in accordance with normal JOBSCOPE procedures.

Record Statuses

The following Record statuses are used to determine the processing status of records in the Audit File:

000001 New record ready to be read by the Router application.

000002 Routed record ready to be processed by the Reader application.

000004 Record is currently being processed by the Reader application.

000008 Record held due to host processing configuration (HP only).

000016 Record has been successfully processed.

000256 Record has failed the JOBSCOPE edits and must be corrected.

Start Host Processing

Host processing of DATACAP Transactions reads the records in the Audit File. It performs any

calculations that are required, formats and feeds the records to the labor process that posts entries

made through the JOBSCOPE Labor Entry window. Since these processes use minimal processor time

when no transactions are available to be processed, it is recommended that they be started once and

left running perpetually. One exception to this is when backups are performed that affect the processes

or the files they access.

Stop Host Processing

When this application is run, it posts an EXIT record to the Audit File for the Router and the Reader(s) to

process. This record will cause the Router and Readers to shutdown when they reach it. Therefore, if a

reader shuts down abnormally and the others are shutdown using the EXIT record, when the readers are

restarted, the reader that shutdown abnormally will still have an EXIT record that will cause that reader

to shutdown again.

AS/400 Specific

From the JOBSCOPE AS/400 main menu, select the Datacap hop code “DC”. The following menu

displays.

The DATACAP Administrator must make sure the subsystem QDCAPII exists. The following host

processing applications run within QDCAPII. If they are not found, they must be configured and/or

started in order for all of the DATACAP records to be successfully processed into JOBSCOPE:

DATACAPII

READLBR

READATTN

READSCRAP

DATACAP

JOBSCOPE Page 113

The following files are used:

Audit File: The ZPAUDIT file in the JBSOPDB library.

Attendance File: The ZPATTRX file in the JBSOPDB library.

Hourly Transaction File: The PPHRTRX file in the JOBSCOPEDB library.

Employee Master File: The PPEMPLM file in the JOBSCOPEDB library.

Job Master File: The PPJOBM file in the JOBSCOPEDB library.

Work Center Master File: The PPWKCTM file in the JOBSCOPEDB library.

Operations File: The PPOPERF file in the JOBSCOPEDB library.

Tables File: The TPTBLLS file in the JOBSCOPEDB library.

JOBSCOPE Enterprise Edition Specific

From the Accounting Module, the DATACAP Host Processes can be reached by navigating to

Production\Collect Labor\DATACAP.

The following files are used:

Audit File: The AUAUDIT table in the JBSDB database.

Attendance File: The AUATTEND table in the JBSDB database.

Hourly Transaction File: The PPHRTRX table in the JBSDB database.

Employee Master File: The PPEMPLM table in the JBSDB database.

Job Master File: The PPJOBM table in the JBSDB database.

Work Center Master File: The PPWKCTM table in the JBSDB database.

Operations File: The PPOPERF table in the JBSDB database.

Tables File: SPT4004 and SPT4009 tables in the JBSDB database.

DATACAP

JOBSCOPE Page 114

Appendix A - DATACAP Overtime Calculations

NOTE: Holiday transactions are not overtime transactions. Therefore, if overtime is disabled and a holiday is defined in the holiday schedule assigned to an employee, LBRO records will still be created and processed for any time worked on the holiday by that employee.

The DATACAP calculates overtime based on several factors:

1. OVERTIME_ENABLED option in the System Configuration Options must be set to ‘Y’ to allow

calculation of overtime.

2. The “WEEKLY_OVERTIME_BY_TOTAL_HOURS” option, in the System Configuration Options,

determines whether daily overtime is included in weekly fence calculations.

3. The “OVERTIME_PREMIUM_TO_OVERHEAD” option, in the System Configuration Options,

determines how overtime charges are calculated.

4. The Overtime Schedule for an employee determines where (overtime account or task) the costs

incurred during their overtime period will be charged.

Overtime is calculated when an employee logs off of a task. At this point, the system checks the

Overtime Schedule that is assigned either in the employee record, the shift or shift 0 in the server

database. The Overtime Schedule record contains two Daily Fences, two Weekly Fences, and a

Consecutive Days fence.

Once the assigned Overtime Schedule is found, the number of hours the employee worked is compared

with the hourly fences found there. Overtime is calculated using the processing order defined in the

Overtime Schedule. Consecutive Days always takes priority. After that, there are three processing

priority options: Daily first then Weekly, Weekly first then Daily, and Maximum of Daily and Weekly.

If the order is Daily first then Weekly, the hours accumulated each day are compared to the Overtime

Fences. Once the First daily Overtime Fence is exceeded, no further Weekly Overtime Fences will be

checked for that day. If a Weekly Overtime Fence is exceeded before the First daily Overtime Fence, the

Weekly Special Rate is applied until the First daily Overtime Fence takes effect.

If the order is Weekly first then Daily, the hours accumulated each day are compared to the Overtime

Fences. Once the First weekly Overtime Fence is exceeded, no further Daily Overtime Fences will be

checked for that week. If a Daily Overtime Fence is exceeded before the First weekly Overtime Fence,

The Daily Special Rate is applied until the First weekly Overtime Fence takes effect.

If the order is Maximum of Daily and Weekly, the hours accumulated each day compared to the

Overtime Fences. When an Overtime Fence is exceeded its Special Rate is compared to that of any other

applicable Overtime Fence. The higher Special Rate is applied until the next Overtime Fence is exceeded.

Examples of Overtime scenarios are described below.

DATACAP

JOBSCOPE Page 115

Overtime Scenario #1

Employees arrive at work on the first day of the business week. They Clock-In and wait for their

supervisor to assign their work for the day. Once they receive their assignment, they go to their work

area, log onto the first task for the day using a DATACAP terminal and begin their work. During the

course of the day, they Suspend and Resume for paid breaks and Clock-Out and back in for their unpaid

lunch. When they are finished for the day, they Logoff, clean up the work area and Clock-Out before

going home.

In this scenario, employees normally work 8 hours a day and 40 hours a week, but in order to meet a

scheduled shipment, they work 10 hours a day for the 5 business days. Their overtime rate is a standard

time-and-a-half (1.5). The options that effect the overtime calculations include:

WEEKLY_OVERTIME_BY_TOTAL_HOURS

Overtime Schedule Processing Priority

If the WEEKLY_OVERTIME_BY_TOTAL_HOURS option is set to ‘N’, the result will be a 2 hour daily

overtime record for the first 4 days and, depending on the priority, a 2 hour daily or weekly overtime

record for the final day. If this option is set to ‘Y’, the result will be a 2-hour daily overtime record for the

each of the first 4 days. However, since the employees would already have 40 hours for the week when

they clocked-in on the last day, they would have (depending on the processing priority) either, (1) a 10

hour weekly overtime record, or (2) an 8 hour weekly and a 2 hour daily overtime record for the last

day.

This chart might be helpful in comparing the results with the different settings:

Weekly Overtime Flag

Processing Priority

Overtime/Day Fence Day 1,2,3,4,5

Regular Hours Overtime Hours

N Daily 2D,2D,2D,2D,2D 40 10

N Weekly 2D,2D,2D,2D,2W 40 10

Y Daily 2D,2D,2D,2D,8W&2D 32 18

Y Weekly 2D,2D,2D,2D,10W 32 18

Overtime Scenario #2

A maintenance employee is scheduled to be “on call” for a given weekend. Maintenance employees

typically work a maximum of 10 days in a row and if they exceed the 10 days, they receive a 25%

premium until they have taken a day off. Additionally, since their hours depend on what is scheduled for

maintenance as well as what needs emergency repairs, they have different tiers to their daily and

weekly overtime compensation. If they work more than 8 hours on a given day, or more than 40 hours a

DATACAP

JOBSCOPE Page 116

week, they receive time-and-a-half (1.5). However, if they exceed 12 hours on a given day, they receive

double-time (2.0), and if they work more than 60 hours in a given week, they receive triple time (3.0).

The Overtime Schedule for this employee looks like this:

The employee works 8 hours a day Monday – Friday of the first week, answers calls on Saturday and

Sunday that require 13 hours on Saturday and 10 hours on Sunday and, because a co-worker is on

vacation, works 8 hours a day Monday-Friday of the second week. This results in a total of 12

consecutive days worked. Since the business week starts on Friday, they accumulated 40 hours the first

Thursday and 63 hours the second Thursday.

This table shows the number of hours that each fence is effective each day. The format indicates

whether WEEKLY_OVERTIME_BY_TOTAL_HOURS is set to ‘N’ or ‘Y.’

Day Cons. 1st Daily 2nd Daily 1st Weekly 2nd Weekly Regular Total

Mon-Fri (Day 1-5)

0 0 0 0 0 8 8

Sat (Day 6)

0 4 1 0 0 8 13

Sun (Day 7)

0 2 0 0 0 8 10

Mon (Day 8)

0 0 0 0 0 8 8

Tue (Day 9)

0 0 0 N=0 Y=7

0 8 8

Wed (Day 10)

0 0 0 N=8 Y=8

0 0 8

Thu (Day 11)

8 0 0 N=8 Y=5

N=0 Y=3

0 8

Fri (Day 12)

8 0 0 0 0 8 8

NOTE: The Consecutive Days Special Rate will be applied prior to the application of any other special rates. Therefore on day 11, the weekly overtime rate would be applied after the 1.25 multiplier from the Consecutive Days fence. This would result in the weekly special rates being multiplied by 1.25 (1.25 X 2 = 2.5 for 1st weekly and 1.25 X 3 = 3.75 for 2nd weekly).

DATACAP

JOBSCOPE Page 117

Appendix B - Parallel Operation Time Calculations

In order to charge time correctly for parallel operations, time must be calculated every time an

employee logs onto or off of a task. When logging onto an operation, the time will be calculated for all

operations already in process. After a logoff, time will be calculated for all operations currently in

process, including the operation being logged off of. Only Release-Work Order-Operations are allowed in

parallel; Releases and Accounts can only be logged onto one at a time. The example below explains how

time is calculated for parallel operations.

An employee clocks in and logs onto RELEASE.1.1. Because it is the first Release-Work Order-Operation

to be logged onto, no calculations will take place yet. After one hour, the employee logs onto

RELEASE.2.1. Time will then be calculated for RELEASE.1.1 because it is currently the only record for this

employee in the WIP (Work In Process) table. One hour has been accumulated for the first operation.

An hour later, the employee logs onto RELEASE.3.1. Calculations will take place for the time period since

the last calculation. RELEASE.1.1 and RELEASE.2.1 are the current operations in the WIP table, 1 hour

must be charged to these two operations. The total time will be divided equally between all operations

in the WIP table. Each operation will get 1/2 hour added to its total time. RELEASE.1.1 now has an

accumulated time of 1.5 hours and RELEASE.2.1 has 0.5 hours.

Three hours later, the employee logs off of RELEASE.1.1. There are three Release-Work Order-

Operations in the WIP table. The time is divided equally between them, and each operation will get one

hour added to its total. RELEASE.1.1 will now have 2.5 hours charged to it. RELEASE.2.1 now has an

accumulated time of 1.5 hours and RELEASE.3.1 has one hour.

One hour later, the employee logs off of RELEASE.2.1. There are two Release-Work Order-Operations in

the WIP table. After dividing the time equally between them, RELEASE.2.1 has a total time of 2 hours,

and RELEASE.3.1 has 1.5 hours. Finally, one hour later, the employee clocks out, logging off of

RELEASE.3.1 in the process. Because it is the only Release-Work Order-Operation in the WIP table, it gets

the full hour added to it.

The employee in the above example worked a total of 8 hours while charging to three operations in

parallel. Because the time was divided equally between the operations, the total time charged to all the

operations is 8 hours.

NOTE: Any fractions left over after dividing time between tasks is negligible since the time is calculated to the hour with 6 decimal places. This is the equivalent of .0036 seconds accuracy.

DATACAP

JOBSCOPE Page 118

Appendix C - DATACAP Troubleshooting Tips

Q: My WINCAP sessions will not connect. What do I do?

A: Restart IIS on the web server.

Q: What do the Record Status values indicate in the LBR_AUDIT file?

A: 0 means the record is ready for upload but has not been uploaded.

1 means the record has been uploaded to the host machine.

1000 means an error was encountered trying to upload the record. If this occurs the first thing to try is

to shutdown the Upload and restart it. If any error message appears, forward that to Jobscope Support.

Q: What do the Record Status values indicate on the Host?

A:

000001 means the record is ready for processing by Host Processing but has not been picked up yet.

00016 means the record has been picked up by Host Processing and successfully processed in the

JOBSCOPE costing system.

000256 means an error has occurred in Host Processing. Going to the DATACAP Host menu and running

the Correct Audit Errors screen can correct this. This usually means that an entry that was valid on the

DATACAP Server is not valid in JOBSCOPE.

January 29, 2019

datacap - jobscope manufacturing software

Documents