Viewing and editing Shop Floor records in Workforce Management

After a transaction has been recorded in Factory Track, it is sent to Workforce Management where it is displayed on an employee’s timesheet. Note that because Factory Track allows employees to work on multiple jobs concurrently, Workforce Management stores these transactions on the timesheet as work premium records.

Only completed transactions originating from Factory Track are recorded in Workforce Management. A completed transaction refers to work performed against a specific operation, setup performed against a specific operation, or indirect tasks not charged to any operation.

All completed work segments originating in Factory Track are posted in Workforce Management as Work Premium Time overrides on an employee's timesheet. Each premium includes the start and end times for the activity and the duration of time for which the activity was performed. In addition, for worked performed against a specific operation, the premium includes the relevant work order and operation, the number of items completed, the number of items scrapped (bad quantity), and the reason for the scrapped quantities, if applicable.

Note: By default, the Bad Quantity and Reason premium fields are hidden in the Daily Timesheet. To view the fields, you must configure the Field UI localization setting of the PREM_WRKD_BAD_QUANTITY and the PREM_RSNCD_NAME fields in config mode. See "Using config mode" in the Infor Workforce Management Time and Attendance Implementation and Administration Guide.

Example: Viewing Shop Floor information in Workforce Management

In this timesheet, an employee recorded both setup time (SETUP) and operation time (OP). The employee also recorded indirect task time for training (TRN). Both the setup and operation time contain information about the work order and operation. The indirect task is not charged to any work order or operation.


Start Time	End Time	Hours	Time Code	Work order	Operation	Completed Qty	Scrap Qty	Scrap Reason
07:30	08:00	0:30	SETUP	PROJ A	OP101
0:800	16:00	5:30	OP	PROJ A	OP101	40	12	Error
13:30	15:30	2:00	TRN	0	0

Note that the duration of time worked on an operation does not need to equal the interval of time between the specified start and end time of the activity. In this example, 5.5 hours of work was performed against the OP101 operation over an eight-hour interval, which also included two hours of training.

During the execution of the OP101 operation, 40 items were completed and 12 items were scrapped (with a reason code of Error).