Clocking-In

Operators come to the shop floor and log on to the system. They open POD and choose the Clock-In/Out button to clock in. Each operator enters user ID and password and chooses the Clock In/Out button in the plug-in. The system displays the logon screen. The user types in the password and chooses OK.

Operator Julia came in time and clocked in at 8:05. The system successfully clocked her in and started tracking her labor time against the IDLE_A LCC, which is a default LCC of her cost center.

Supervisor Maria opens the On Premises Report. She enters the EA into the Cost Center field and chooses Search. The system presents the report which indicates that user Julia is clocked in and user John is not. His status remains Clocked Out.

Operator John arrived late and did not clock in at 8:10. The system did not clock him in as it is set up to only allow the user clock in within the clock-in interval.

John comes to his supervisor Maria and explains the problem and reason of the late arrival. Maria opens the Supervisor Clock-In/Out activity, enters the John’s user ID, updates the actual time of arrival, and enters the reason of the late arrival into the Comments field. Maria chooses the Clock-In/Out button and the system clocks John in. John’s time is also tracked against the IDLE_A LCC, which is a default LCC of his cost center.

Supervisor Maria retrieves the On Premises Report for the cost center EA again. Now all the employees of this cost center are clocked in.

Laboring On/Off and Collecting Distributed Times

Operators select the operation Assembly_A, the DEFAULT resource, and SFC number of the Engine_A material. They choose the Start button. The system starts the selected SFC number and labors the users on to it. The user labor and the SFC labor are being tracked against the PRODUCTION_A LCC which is assigned to shop order of the started SFC number.

When the users finish working on the SFC number at an operation, they choose the Complete button. The system completes the selected SFC numbers at the Assembly_A operation and displays the Collect Work Time plug-in. Here the users can see how much time they spent on processing the SFC numbers and can distribute the time among the activities Preparation, Assembling, and Check.

Julia spent 7 minutes on processing this SFC number. She indicates that she worked 1 minute on preparation, 5 minutes on assembling, and 2 minutes on checking, and chooses the OK button. The system compares the total time indicated for the distributed activities against the time spent on overall SFC number processing. Total distributed times is 8 minutes which exceeds the overall time spent on the SFC number processing, thus the system displays an error message. Julia changes the time spent on assembly to 4 minutes, and chooses OK again. The updated values pass the check, and the system saves the entries and labors Julia off from the SFC number. Her labor time is being tracked against their default LCC IDLE_A again.

John has also spent 7 minutes on processing his SFC number. But he does not distribute this time among the activities and just chooses OK in the plug-in. The system labors him off from his SFC number and continues tracking his labor time against his default LCC IDLE_A. John will be able to distribute the time spent on processing this SFC number tomorrow in his time sheet.

After having worked for some time on assembling Engine A, Julia is asked to assemble Engine B to substitute a missing operator. She enters the operation Assembly_B and the resource DEFAULT in the POD, selects the SFC number of the Engine_B material and chooses the Start button. The system starts the selected SFC number and labors her on to it. The user labor and the SFC labor are being tracked against the PRODUCTION_B LCC which is assigned to the shop order of the started SFC number. This time will be charged to the EB cost center.

When Julia finishes working on the SFC number at the operation, she chooses the Complete button. The system completes the selected SFC numbers at the Assembly_B operation and labors her off from the SFC number. The Collect Work Time plug-in is not displayed as no standard value key is assigned to this routing operation and material.

Monitoring SFC Labor in Real Time

During the working day, Maria monitors labor time spent by operators on shop orders processing. She may do this by specific order or LCC. Today she needs to know how much time is spent on shop orders with the Production_A LCC and how much time is spent on the shop order for Engine_B which is processed by Julia.

To do this, Maria opens the LCC Summary report, enters PRODUCTION_A into the Labor Charge Code field, Today into the Date Range field and chooses Search. The system displays all shop orders with this LCC that have been processed today along with the time spent on each of them.

Then she clears the screen, enters the shop order number for ENGINE_B that Julia worked on today and chooses Search. The system displays time logged for this shop order and labor charge codes this time is charged to.

Changing User LCC

John needs to restock goods. To indicate this, he chooses the Change User LCC button in the POD. The system displays the Change User LCC plug-in. John chooses the Show LCC button in the plug-in, enters password, and chooses OK. The system displays IDLE_A as his current LCC. Johns enters RESTOCKING_A into the New LCC field and chooses the Change LCC button in the plug-in. The system starts tracking his labor time against this LCC. This time will be charged to the EA cost center as indirect labor.

Similarly, when in the afternoon John and Julia participate in an internal employee training, they need to change their user LCC to TRAINING_INT. The time spent on training will be charged to the TRAINING cost center. However, John has forgotten to do this and will have to add this information in his time sheet the next day.

Clocking Out and Rolling Up Labor Records

At the shift end, users open the Clock In/Out plug-in in the POD to clock-out. Julia forgets to do this and the system will clock her out automatically when running the scheduled labor rollup script. Her clock-out time will be visible in the system as 17:00, which is her shift end time.

Labor rollup automatically runs at 00:05. No user interaction is required.

Viewing User Timesheet

Next day, after labor rollup has run, the users can review their time sheet to verify everything is correct. Julia opens the User Timesheet activity, selects Yesterday in the Labor Date Range field and submits Retrieve. The system displays one row with the status New for yesterday’s date. The clock-out time is 5:00, which equals the shift end time.

Julia chooses the Details icon. The system displays the table with 4 rows; each row represents time logged for the particular LCC:

The PRODUCTION_A and PRODUCTION_B LCCs represent the direct labor spent on processing SFC number, so there are shop order numbers in the corresponding rows. Julia selects the Details icon for the PRODUCTION_A record and reviews the content. She can see the labor time distributed between the activities. Everything looks fine and Julia accepts the record. To do this, she selects the record in the User Labor Time Summary screen and chooses  More Accept Selected . She repeats this action for each time record or selects the whole day record on the initial User Timesheet screen and chooses  More Accept Selected . The status of the selected records changes to Accepted.

John opens the User Timesheet activity, selects Yesterday in the Labor Date Range field, and chooses Retrieve. The system displays one row with the New status for yesterday’s date. The warning status for the record contains SPRV Clock-In/Out, which means that John was clocked out by his supervisor. John chooses the Details icon. The system displays the table with his time records for yesterday. The table contains the following records:

The time he spent on training has not been recorded for TRAINING and was logged against RESTOCKING, as he forgot to change his user LCC. Now he needs to correct this manually.

First, he selects the details of the RESTOCKING_A record, decreases the Labor Time value, enters comment (for example, Decreased labor time, as time spent on internal training was logged here by mistake) and chooses Apply. The system saves the changes and the warning User Labor Edit is now displayed against this time record on the initial screen.

Then, on the User Labor Time Summary screen, John chooses  Actions Insert Indirect Labor Record . He enters TRAINING on the Labor Charge Code screen, enters training duration time into the Labor Time field, changes the Labor Date and the Record Start Time values so that they contain the training start and end time. Then he enters the comment (for example, Forgot to change my LCC for training) into the User's Comments field and chooses Apply.

The system adds a new record and the warning User Labor Edit is now displayed against this time record on the initial screen.

John selects all his records and accepts them.

Timesheet Review by Supervisor

Maria opens the Supervisor Time Edit and Approval activity and retrieves the records for the cost center EA and yesterday’s date. She reviews the timesheets and approves the status of the accepted records. For this, she selects the record and chooses  Actions Approve Selected . The status of the record is changed to Approved.

The supervisor can also unapprove the accepted record, if it is incorrect or misses the required information. For example, when reviewing John’s records, Maria notices that his PRODUCTION_A record misses the distributed labor times. She indicates this in the Supervisor’s Comments field and chooses Apply. Then she selects the record on the User Labor Time Summary screen and changes its status to Unapproved by choosing  Actions Unapprove Selected .

Now John needs to open this record in the User Time Edit activity, enter the values for distributed labor time and change the status back to Accepted. Then, Maria reviews his record again and changes its status to Approved.