Works History: Shopfloor Work Operation Data Collection

Contents

Shopfloor Work Operation Data Collection

Reference Contents > Works History > Shopfloor Work Operation Data Collection

This window enables you to record when Work Order Operations have been completed on the Shopfloor. Within it you can record the completion, or partial completion, of Operations processing the Work Order assembly.

When the window opens, you select a Work Order using the Select Work Order window that will be presented.

When you locate a Work Order two lists of Operation data are built. The upper list shows the current Process Route for the assembly. This list includes a total of received and scrapped quantity so far logged against each Operation. The lower list shows all history records so far created for the Operations.

The window does not provide any facility to change history that has already been recorded. You are restricted in recording a new completion only.

Having selected an order, by default you are provided with the next Operation to record. If the last history record is for a partial completion, you will be presented with the next Operation with a quantity consistent with the previous partial completion. If you want to record a second sub-batch of a previous Operation, click on the Operation in the upper list.

You can enter a Good in batch quantity and a Scrapped quantity. The sum of the two can not exceed a quantity that accumulates with any previous sub-batch receipt for the Operation such that it exceeds the Quantity Ordered.

In the File — System Manager — Company Details function you may have set a WO + Receiving variance limit. In which case the permissible total quantity may be in excess of the Quantity Ordered.

TIP: The Work Order Receiving Variance limit can be usefully used when you build a level of scrap into the Bill of Materials. If you then get a better than expected yield from the production process, you can record it correctly.

Having entered the quantities, you may optionally identify the employee who processed the Operation. This may be useful as Work History reports can be sorted and selected by employee code. The employee must be pre-defined in the File — System Manager — Employees function.

If you enter a scrap quantity, you will be expected to enter a Scrap Reason code. This is not mandatory but you will be reminded if you forget. Scrap Reason codes must be pre-defined in the Master — Quality Assurance — Scrap and Test Codes function.

You can now enter the Setup and Run times actually taken in processing the quantity through this Operation. If you Process Entries and save the quantity before you do this, you can always re-enter the times, and employee, using the Log WO Performance function. You have two methods of entering the times. Either enter them directly in decimal hours, or use the HMSP syntax here (see below), or construct the hours by entering the days, working time in the day, start time, end time and break time, where all times are in hours and minutes, or use the sliders.

TIP: Times must be entered using the 24 hour clock (known as military time in the US) and can be typed in using almost any character as a delimiter between hours and minutes. For example, ’10 16′, ‘10.16’, ‘10,16’ will all yield ’10:16′.

When you are satisfied with the times, confirm by clicking on the Process Entries button. You will then automatically be presented with the next appropriate Operation to record against. If this is inappropriate, change the Work Order or close the window.

TIP: In some circumstances it may be permissible to record operations out of sequence. You can do this with the optWOShopOpOutSeq option in Settings Maintenance at a system level. If the value is 1 users will be able to record operations out of sequence.

TIP: You can use the optWOShopReceive option in Settings Maintenance at any level to have the system automatically open the appropriate Receive Work Order Assemblies from Production or Backflush Work Order window automatically pre-loaded when you record the completion of a quantity on the final operation.

TIP: Normally, after selecting a Work Order, or an operation line in the operation list, the Good in batch is set to the available receipt quantity. However, there is a user-level option that can force the default quantity to zero. The option optWOShopDefaultZero should be set to 1.

TIP: Normally Work History Operation Comments are not recorded. However, there is an option, optWOHistOpCom, that permits the recording of comments when work operation history is recorded. When the option is set to 1, the Work Operation History Comments window is made available for each Shopfloor or Log WO Performance entry. If set to 2, it additionally opens for Receive WO and Backflush WO. With this option set to 1 or 2 you can use the option optWOHistOpComText for default comment text.

Field	Description
Work Order Number	Work Orders. Work order number. {WKOFILE.WKOWONO char 6}
Ordered Quantity	Work Orders. Quantity ordered. {WKOFILE.WKOOQTY number 3dp}
Planned Completion Date	Work Orders. Date of planned completion. {WKOFILE.WKOCDAT date date1980}
Assembly Part Number	Work Orders. Part number (parent assembly). {WKOFILE.WKOPTNO char 18}
Description	Parts Master. Part description. {PTMFILE.PTMDESC char 30}
Stock UoM	Parts Master. Standard stock unit of measure. {PTMFILE.PTMSTUM char 6}
Process Route List	A listing of the process route operations for the assembly being processed by the selected WO.
Total Route Hours	The total hour planned for the WO quantity, based on process route times.
Operation Number	Work History. Operation number of process route. {WOHFILE.WOHOPNO integer}
Quantity in Batch	Work History. Quantity completed. {WOHFILE.WOHQTY number 3dp}
Quantity Scrapped	Work History. Assembly scrap quantity. {WOHFILE.WOHSCRA number 3dp}
Employee Code	Work History. Employee code. {WOHFILE.WOHEMPL char 4}
Employee Name	Employees. Employee name. {EMPFILE.EMPNAME char 50}
Scrapped Reason Code	Work History. Scrap reason code (relation: IDXID = con(‘7’,WOHSCRE). {WOHFILE.WOHSCRE char 4}
Scrapped Reason	Index and Other Codes. Index code, scrap reason or QA test description (must have at least 1 character). {IDXFILE.IDXDESC char 255}
Show	Click to show a list of available scrap reason codes.
Reason Code List	List of available scrap codes. Double-click to assign.
Setup Hours	You can use HMSP syntax here (see below). Work History. Setup time for operation batch in hours. {WOHFILE.WOHSTIM number 2dpShortnum}
Setup Days	Whole days included in the operation setup for the batch.
Setup Time Per Day	The time in hrs:mins that each of a whole day represents.
Setup Breaks	The setup break time in hrs:mins.
Setup Start Time	The setup start time in the day.
Setup End Time	The setup end time in the day.
Setup Slider	Use the slider to increase or decrease the setup duration.
Runtime Hours	You can use HMSP syntax here (see below). Work History. Runtime for operation batch in hours. {WOHFILE.WOHRTIM number 4dp}
Runtime Days	Whole days included in the operation runtime for the batch.
Runtime Time Per Day	The time in hrs:mins that each of a whole day represents.
Runtime Breaks	The runtime break time in hrs:mins.
Runtime Start Time	The runtime start time in the day.
Runtime End Time	The runtime end time in the day.
Runtime Slider	Use the slider to increase or decrease the runtime duration.
Production Logged List	A list of the operation batches logged so far. The times can be edited in the Log Performance function.
Total Logged Hours	The total time so far logged to the WO.
Avoid queries	Check this option to suppress normal warning and confirmation messages.

Button	Action
Select Work Order	To select a specific Work Order. It opens the Select Work Order window.
Revert to Saved	To cancel any entries and revert to the original state.
Process Entries	To confirm and process the entries you have made.

Entering Time Values using HMSP Syntax

The system stores and uses times in decimal hours. 1.5000 hours rather than 1hr 30min. However, you can enter time in a number of different ways that will automatically convert to the equivalent decimal hours when you leave the field.

Units	Syntax	Example which Converts to
Hours	h or H	1h30m = 1.5000
Minutes	m or M	20m = 0.3333
Seconds	s or S	3.6s = 0.0010
Hours:Mins	: or ;	1:30 = 1.5000
Combined	All	1:30m36s = 1.5100
Pieces per hour	p or P	100p = 0.0100

Was this article helpful?

Yes No

Shopfloor Work Operation Data Collection

Entering Time Values using HMSP Syntax

Was this article helpful?

Related Articles

Leave a Comment Cancel