<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Works History Archives - Caliach</title>
	<atom:link href="https://caliach.com/article-categories/works-history/feed/" rel="self" type="application/rss+xml" />
	<link>https://caliach.com/article-categories/works-history/</link>
	<description>Manufacturing Software Solutions</description>
	<lastBuildDate>Tue, 26 Jul 2022 12:41:09 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://caliach.com/wp-content/uploads/2022/11/fav-150x150.png</url>
	<title>Works History Archives - Caliach</title>
	<link>https://caliach.com/article-categories/works-history/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Work History: Shopfloor Work Operation Data Collection</title>
		<link>https://caliach.com/knowledge-base/wwohshop/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Tue, 26 Jul 2022 12:41:09 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/?post_type=ht_kb&#038;p=4456</guid>

					<description><![CDATA[<p>OVERVIEW 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 [&#8230;]</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohshop/">Work History: Shopfloor Work Operation Data Collection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">OVERVIEW	</h2>



<p>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. </p>



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



<p>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. </p>



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



<p>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. </p>



<p>You can enter a Good in batch quantity and a Scrapped quantity. The sum of the two cannot exceed a quantity that accumulates with any previous sub-batch receipt for the operation such that it exceeds the Quantity Ordered. </p>



<p>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 more than the Quantity Ordered. </p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">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.</p>



<p>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. </p>



<p>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. </p>



<p>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. </p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">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′</p>



<p>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. </p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">Tip: In some circumstances it may be permissible to record operations out of sequence. You can do this with the <strong>optWOShopOpOutSeq</strong> option in Settings Maintenance at a system level. If the value is 1, users will be able to record operations out of sequence.</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">Tip: You can use the <strong>optWOShopReceive</strong> 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.</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">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<strong> optWOShopDefaultZero</strong> should be set to 1.</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">Tip: Normally Work History Operation Comments are not recorded. However, there is an option, <strong>optWOHistOpCom</strong>, 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 <strong>optWOHistOpComText</strong> for default comment text.</p>



<h2 class="wp-block-heading">File Path</h2>



<h3 class="wp-block-heading">Process &gt; Shopfloor &gt; Shopfloor Data…</h3>



<p>This file path takes you to the Shopfloor Work Operation Data Collection window. </p>



<figure class="wp-block-image"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/4_table-description-automatically-generated.png" alt="Table

Description automatically generated" class="wp-image-4457"/></figure>



<h3 class="wp-block-heading">Work Order</h3>



<p>This is the work order number </p>



<h3 class="wp-block-heading">Link icon</h3>



<p>Click to view any linked external files.  Hold the shift key down and click to create a new file link for the record. </p>



<h3 class="wp-block-heading">Select WO button</h3>



<p>To select a specific Work Order. This opens the Select Work Order window.</p>



<h3 class="wp-block-heading">Kitted field</h3>



<p>This is the date the works order was kitted. </p>



<h3 class="wp-block-heading">Ordered</h3>



<p>The quantity ordered is displayed here. </p>



<h3 class="wp-block-heading">Planned Completion</h3>



<p>Date of planned completion. </p>



<h3 class="wp-block-heading">Assembly</h3>



<p>Part number (parent assembly).</p>



<h3 class="wp-block-heading">Assembly description</h3>



<p>Part description.</p>



<h3 class="wp-block-heading">UoM</h3>



<p>Standard stock unit of measure.</p>



<h3 class="wp-block-heading">Process Route field</h3>



<p>A listing of the process route operations for the assembly being processed by the selected WO.</p>



<h3 class="wp-block-heading">Total route hours for quantity ordered</h3>



<p>The total hour planned for the WO quantity, based on process route times.</p>



<h3 class="wp-block-heading">Record Batch Operation Completion</h3>



<h3 class="wp-block-heading">Operation</h3>



<p>Operation number of process route.</p>



<h3 class="wp-block-heading">Goods in batch</h3>



<p>Quantity completed.</p>



<h3 class="wp-block-heading">Scrapped</h3>



<p>Assembly scrap quantity.</p>



<h3 class="wp-block-heading">Show button</h3>



<p>List of available scrap reason codes </p>



<h3 class="wp-block-heading">Scrap reason</h3>



<p>Index code, scrap reason or QA test description </p>



<h3 class="wp-block-heading">Employee</h3>



<p>Employee code and name. </p>



<h3 class="wp-block-heading">Set up hours	</h3>



<p>You can use HMSP syntax here (see below). Setup time for operation batch in hours. </p>



<h3 class="wp-block-heading">Setup Days</h3>



<p>Whole days included in the operation setup for the batch.</p>



<h3 class="wp-block-heading">Setup Time Per Day</h3>



<p>The time in hrs:mins that each of a whole day represents.</p>



<h3 class="wp-block-heading">Setup Breaks</h3>



<p>The setup break time in hrs:mins.</p>



<h3 class="wp-block-heading">Setup Start Time</h3>



<p>The setup start time in the day.</p>



<h3 class="wp-block-heading">Setup End Time</h3>



<p>The setup end time in the day.</p>



<h3 class="wp-block-heading">Setup Slider</h3>



<p>Use the slider to increase or decrease the setup duration. </p>



<h3 class="wp-block-heading">Run hours</h3>



<p>You can use HMSP syntax here (see below). Runtime for operation batch in hours.</p>



<h3 class="wp-block-heading">Run Days</h3>



<p>Whole days included in the operation runtime for the batch.</p>



<h3 class="wp-block-heading">Run Time Per Day</h3>



<p>The time in hrs:mins that each of a whole day represents.</p>



<h3 class="wp-block-heading">Run Breaks</h3>



<p>The runtime break time in hrs:mins.</p>



<h3 class="wp-block-heading">Run Start Time</h3>



<p>The runtime start time in the day.</p>



<h3 class="wp-block-heading">Run End Time</h3>



<p>The runtime end time in the day.</p>



<h3 class="wp-block-heading">Run Slider</h3>



<p>Use the slider to increase or decrease the runtime duration. </p>



<h3 class="wp-block-heading">Production Logged field</h3>



<p>A list of the operation batches logged so far. The times can be edited in the Log Performance function.</p>



<h3 class="wp-block-heading">Total hours logged so far</h3>



<p>The total time so far logged to the WO.</p>



<h3 class="wp-block-heading">Avoid queries tick box</h3>



<p>Check this option to suppress normal warning and confirmation messages.</p>



<h3 class="wp-block-heading">Revert button</h3>



<p>To cancel any entries and revert to the original state.</p>



<h3 class="wp-block-heading">Process Button</h3>



<p>To confirm and process the entries you have made.</p>



<h2 class="wp-block-heading"><strong>Entering Time Values using HMSP Syntax</strong>
</h2>



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



<figure class="wp-block-table is-style-regular"><table><tbody><tr><td><p><strong>Units</strong>
</p></td><td><p><strong>Syntax</strong>
</p></td><td><p><strong>Example which Converts to</strong>
</p></td></tr><tr><td><p>
  Hours
</p></td><td><p>
  H or H
</p></td><td><p>
  1h30m = 1.5000
</p></td></tr><tr><td><p>
  Minutes
</p></td><td><p>
  M or M
</p></td><td><p>
  20m = 0.3333
</p></td></tr><tr><td><p>
  Seconds
</p></td><td><p>
  S or S
</p></td><td><p>
  3.6s = 0.0010
</p></td></tr><tr><td><p>
  Hours:Mins
</p></td><td><p>
  : or ;
</p></td><td><p>
  1:30 = 1.5000
</p></td></tr><tr><td><p>
  Combined
</p></td><td><p>
  All
</p></td><td><p>
  1:30m36s = 1.5100
</p></td></tr><tr><td><p>
  Pieces per hour
</p></td><td><p>
  P or P
</p></td><td><p>
  100p = 0.0100
</p></td></tr></tbody></table></figure>



<figure class="wp-block-table is-style-regular"><table><tbody><tr><td><p><strong>See Also:</strong>
</p></td><td><ul>
  <li>
    Select Work Order
  </li>
</ul></td></tr></tbody></table></figure>



<p>
  Compiled in Program Version 6.00.  Help date last modified on 26 July 2022.
</p>



<p>Class wWohShop last modified 25 May 2022 FP: Process > Shopfloor > Shopfloor Data&#8230; </p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohshop/">Work History: Shopfloor Work Operation Data Collection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Works History: Work Operation Tracking</title>
		<link>https://caliach.com/knowledge-base/wwtkinput-2/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Thu, 14 Jul 2022 08:52:24 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/?post_type=ht_kb&#038;p=4449</guid>

					<description><![CDATA[<p>OVERVIEW This window is the primary data entry window for the Work Tracking system. You can manually enter data, however it is primarily designed to be used with wedge barcode readers. Two sets of data are needed for real time work tracking. The first set is activity data, which is: Work Order number, e.g. 000001 [&#8230;]</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwtkinput-2/">Works History: Work Operation Tracking</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">OVERVIEW	</h2>



<p>This window is the primary data entry window for the Work Tracking system. You can manually enter data, however it is primarily designed to be used with wedge barcode readers. </p>



<p>Two sets of data are needed for real time work tracking. </p>



<p>The first set is activity data, which is: </p>



<p>Work Order number, e.g. 000001 or a Special Tracking Order such as CLEAN </p>



<p>Operation number, e.g. 010 or, in the case of Special Tracking Orders, 000 </p>



<p>Whether the work is Setup or Runtime indicated by a 0 or 1. </p>



<p>These are linked together with dashes to make a single data entry string, for example 000001-010-0, indicating setup on operation 10 of work order 000001. </p>



<p>This data can be printed as a barcode on Work Orders, two for each operation of the route. One for Setup and one for Runtime. The user can then just swipe one or other to record this activity data. </p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon is-style-alert">NOTE: The barcode reader must be configured so that the terminator character appended by the reader is an Enter. The program will then automatically move to the next set of data and wait for entry.</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon is-style-info">CUSTOM CAPABILITY: The default barcode fonts used in the program are C39 AIAG B-3 24pt LJ3 for Windows and C39 High 36pt LJ4 for Macintosh. These can be changed with a custom #WIRFONTS or #MARFONTS system classes.</p>



<p>When you need to log to Special Tracking Orders it is best to use a sheet of barcodes or labels. These can be printed from the Special Tracking Orders function. There are no setup or runtime alternatives, as any activity on a Special Tracking Order has zero operation number and is considered setup. </p>



<p>The second set of data is employee data, which is: </p>



<p>Employee code, e.g. 5200 </p>



<p>Action of either starting or finishing (logging on or off a work activity) indicated by a 0 or 1 </p>



<p>These are concatenated together with a dash to make a single data entry string, for example 5200-0, indicating employee 5200 is starting a work activity. </p>



<p>This data can be typically part of an employee badge and can be printed as barcode label (standard Avery L7163) from File — System Manager — Employees. </p>



<p><strong>Data Entry</strong>
</p>



<p>When you operate the Work Tracking Input function, the window opens with no data. The list area will show only entries made since you open the window. Note that, unlike other program windows, the Cancel button clears the data entry fields ready for a new input data set and does not close the window or cancel the edit process. </p>



<p>The status bar at the bottom of the window will show any error, warning, or status messages. </p>



<p>The system has the capability of automatically recording the completion of Work Order operations as though you were doing so in the Shopfloor Data function. To record completion, check the Record Quantities checkbox and two additional entry fields become exposed. This additional data needs to be entered through the keyboard. If you enter a scrapped quantity, you may also provide a scrap reason code (optionally selected from the Show list). </p>



<p>To make a data entry, first swipe the Work Order operation barcode, or Special Tracking Work Order barcode, then the employee label start barcode. Those two swipes, if correct, will cause the data to be recorded and added to the list. The window status returns automatically to be ready for another data set entry. </p>



<p>When you record the end of an operation, the start record previously made will be located and the finish time recorded on it. That tracking record will then have been completed. A default time of 12 hours is allowed between starting and finishing before a separate finishing-only tracking record is created. This is necessary to resolve the problem of an employee not recording the finish of an operation before he leaves in the afternoon. </p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon is-style-alert">Note: The option<strong> optWorkTrackingLateHrs</strong> is available to change the time permitted for a finish event to be recorded after which a new tracking record is created. The default is 12 hours unless you enter a numeric value against <strong>optWorkTrackingLateHrs</strong>.</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon is-style-alert">Note: The system option <strong>optWorkTrackingOpSeq</strong> is available to force operations to be entered in sequence. If this is not set, operations can be recorded in any order.</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">Tip: You can use the <strong>optWOShopReceive </strong>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.</p>



<p>The listing shows results for the session. The list shows the key information of employee code, work order, operation number and setup (S) or runtime (R), plus the Log status of whether the record is currently open (On) or has been finished (Off), then the start and finish date and times, and finally a comment. </p>



<p>To enter a comment, simply double-click on the line. The Work Tracking Comment window will open where you can enter your comment text. </p>



<p>Work Tracking records can be amended and analysed in the Work Tracking Analysis window. </p>



<h2 class="wp-block-heading">File Path</h2>



<h3 class="wp-block-heading">Process &gt; Shopfloor &gt; Work Tracking Input…</h3>



<p>This file path takes you to the Work Operation Tracking window. </p>



<figure class="wp-block-image"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/1_a-picture-containing-graphical-user-interface-des.png" alt="A picture containing graphical user interface

Description automatically generated" class="wp-image-4450"/></figure>



<h3 class="wp-block-heading">WO – Op.No. – Set/Run</h3>



<p>Tracking event operation input in the form Work Order – Op No – Set or Run entry, normally by barcode scan. </p>



<h3 class="wp-block-heading">Work Order</h3>



<p>Work order number </p>



<h3 class="wp-block-heading">Link icon</h3>



<p>Click to view any linked external files.  Hold the shift key down and click to create a new file link for the record. </p>



<h3 class="wp-block-heading">Operation</h3>



<p>Operation number </p>



<h3 class="wp-block-heading">Employee – Login/off</h3>



<p>Employee input in the form Employee code – Start or End entry, normally by barcode scan. </p>



<h3 class="wp-block-heading">Part number</h3>



<p>Unique part number. </p>



<h3 class="wp-block-heading">Remaining qty</h3>



<p>Remaining quantity that has not been recorded in the Work Order history. </p>



<h3 class="wp-block-heading">Record Quantities</h3>



<p>Check this option if you wish to record assembly operation completion. </p>



<h3 class="wp-block-heading">Cancel button</h3>



<p>Aborts the process currently in session. The keyboard equivalent is the Esc key for Windows computers and Command-.(full stop or period) for the Mac.</p>



<h3 class="wp-block-heading">OK button</h3>



<p>The OK button updates the data you have entered or confirms the selection and/or processes the function you have called.</p>



<h3 class="wp-block-heading">Quantity received</h3>



<p>Quantity of the assembly completed. </p>



<h3 class="wp-block-heading">Quantity Scrapped</h3>



<p>Quantity of the assembly scrapped. </p>



<h3 class="wp-block-heading">Scrapped reason code</h3>



<p>Scrap reason code entry is only possible when a scrap quantity has been entered. </p>



<h3 class="wp-block-heading">Scrapped reason</h3>



<p>Reason for scrap. </p>



<h3 class="wp-block-heading">Show button</h3>



<p>Click to show a list of available scrap reason codes. </p>



<h3 class="wp-block-heading">Scrap reason pop up list</h3>



<p>List of available scrap codes. Double-click to assign.</p>



<h3 class="wp-block-heading">Information field</h3>



<p>List of events recorded so far this session. Enter or change a comment in the list or by double-clicking.</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">Tip: To edit cells in the list, select the line and click in the cell and hover the mouse over the cell. I.E. click once and pause with no mouse movement. The cell will then expand into an editable box in which you can enter different data. On leaving the box with any action like a tab or click elsewhere, the data is verified and the list returns to normal with the new data shown in the cell.</p>



<p>
  Compiled in Program Version 6.00. Help data last modified 12 July 2022 
</p>



<p>
  Class wWtkInput last modified 25 May 2022
</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwtkinput-2/">Works History: Work Operation Tracking</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Works History: Work Tracking Analysis</title>
		<link>https://caliach.com/knowledge-base/wwtkanal/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Mon, 27 Jun 2022 13:25:25 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/?post_type=ht_kb&#038;p=4425</guid>

					<description><![CDATA[<p>OVERVIEW Work Tracking and Shopfloor Time and Attendance The program supports an employee work tracking system. Employees can log on and off work order operations in real time, usually with the aid of barcode readers. Powerful costing and analysis functions are available and there is a system of special work orders that can cover non-productive [&#8230;]</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwtkanal/">Works History: Work Tracking Analysis</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h1 class="wp-block-heading" id="wwtkanal-">OVERVIEW </h1>



<p>Work Tracking and Shopfloor Time and Attendance </p>



<p>The program supports an employee work tracking system. Employees can log on and off work order operations in real time, usually with the aid of barcode readers. Powerful costing and analysis functions are available and there is a system of special work orders that can cover non-productive activity and attendance. Each employee can have 6 pay rates which can be used in costing shopfloor activity and attendance. </p>



<p>To use the system fully you need to invest in barcode reader hardware and maintain terminals in strategic locations in the production area. Each terminal would run Caliach Vision and be equipped with barcode reading hardware. Such hardware is known as a &#8220;wedge&#8221; barcode reader as it acts as a substitute to keyboard entry and wedges between the keyboard and computer. </p>



<p>All work tracking functions are available from the Process &#8212; Shopfloor menu. After selection of a menu line the Shopfloor menu is installed on the menu bar. </p>



<p>To setup the system you may wish to create some Special Tracking Orders first and enter Employee pay rates. </p>



<p>The Process &#8212; Shopfloor &#8212; Work Tracking Input function opens the Work Operation Tracking window. You can manually enter data, however, it is primarily designed to be used with wedge barcode readers. </p>



<p>The Process &#8212; Shopfloor &#8212; Work Tracking Analysis function opens this window (see later). </p>



<p>The Process &#8212; Shopfloor &#8212; Special Tracking Orders function opens the Special Tracking Work Order Maintenance window which enables you to setup attendance and other pseudo orders that work can be logged against. </p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">TIP: There are two Posted Flags on work tracking records. One is the CostPosted which identifies whether the record has had costs calculated from the employee rates. The second is the Work OrderPosted flag which is always set for non-WO records and identifies whether the record has been included in posting costs to a Work Order. Both flags are controlled in the Analysis function.</p>



<h2 class="wp-block-heading">File Path</h2>



<h3 class="wp-block-heading">Process &gt; Shopfloor &gt; Work Tracking Analysis…</h3>



<p>This file path takes you to the Work Tracking Analysis window. </p>



<figure class="wp-block-image"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/graphical-user-interface-application-table-exce.png" alt="Graphical user interface, application, table, Excel

Description automatically generated" class="wp-image-4426"/></figure>



<h3 class="wp-block-heading">Event list</h3>



<p>List of events recorded so far this session. You can enter or change a comment within the list.</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">TIP: To edit cells in the list, select the line and click in the cell and hover the mouse over the cell. I.E. click once and pause with no mouse movement. The cell will then expand into an editable box in which you can enter different data. On leaving the box with any action like a tab or click elsewhere, the data is verified and the list returns to normal with the new data shown in the cell</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon">TIP: Double clicking a line in the Order column open the &#8216;Log Work Order Operational Performance&#8217; window with the line pre-selected.</p>



<h3 class="wp-block-heading">Totals – Hr:Mins</h3>



<p>Total time in Hrs:Mins for working operations listed.</p>



<h3 class="wp-block-heading">Totals &#8211; Labour</h3>



<p>Total labour cost for working operations listed.</p>



<p class="wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon is-style-danger">WARNING: If times are changed, the cost is re-calculated using the base cost rate for the employee. After changes, you must ultimately use the Analyse button to apply the rates. This is because complex rates apply across the entire set of tracking events and not necessarily to an individual event.</p>



<h3 class="wp-block-heading">Totals &#8211; Overhead</h3>



<p>Total overhead cost for working operations listed. </p>



<h3 class="wp-block-heading">Select History button</h3>



<p>Click to select a set of work tracking history. It opens the Work Tracking History Selection window.</p>



<h3 class="wp-block-heading">Add Event button</h3>



<p>Click to add an event to the tracking file. It opens the Work Tracking Event Addition window.</p>



<h3 class="wp-block-heading">Delete Selected button</h3>



<p>Click to delete selected lines from the tracking file.</p>



<h3 class="wp-block-heading">Set Rates button</h3>



<p>Click to view and amend the labour rate schedule. It opens the Work Tracking Labour Rate Schedule window.</p>



<h3 class="wp-block-heading">Print List button</h3>



<p>Click to print a listing of the records in the list in the sort order selected. Right-click to select a report destination.</p>



<h3 class="wp-block-heading">Analysis button</h3>



<p>Click to choose an analysis option or report. It opens the Work Tracking Analysis Options window. </p>



<figure class="wp-block-table is-style-regular"><table><tbody><tr><td><p>
  See also:
</p></td><td><ul>
  <li>
    Work Tracking History Selection
  </li>
  <li>
    Work Tracking Event Addition
  </li>
  <li>
    Work Tracking Labour Rate Schedule
  </li>
  <li>
    Work Tracking Analysis Option
  </li>
</ul></td></tr></tbody></table></figure>



<p>
  Compiled in Program Version 6.00. Help data last modified 27 June 2022 
</p>



<p>   Class wWtkAnal last modified 25 May 2022</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwtkanal/">Works History: Work Tracking Analysis</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Work History: Work Tracking Labour Rate Schedule</title>
		<link>https://caliach.com/knowledge-base/wwtkrates/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Mon, 27 Jun 2022 11:54:23 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/?post_type=ht_kb&#038;p=4420</guid>

					<description><![CDATA[<p>OVERVIEW This window opens when you click on the Set Rates button on the Work Tracking Analysis window. The working hours are the hours from starting in the morning and not the hours at that rate. So if you have normal hours for Monday through Friday of 8 hours, you would indicate that for your [&#8230;]</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwtkrates/">Work History: Work Tracking Labour Rate Schedule</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">OVERVIEW	</h2>



<p>This window opens when you click on the Set Rates button on the Work Tracking Analysis window. </p>



<p>The working hours are the hours from starting in the morning and not the hours at that rate. So if you have normal hours for Monday through Friday of 8 hours, you would indicate that for your Base Rate. Overtime up to a further 8 hours should be shown as Rate 1 with 16:00 as the extent of working hours at that rate. </p>



<h2 class="wp-block-heading">File Path</h2>



<h3 class="wp-block-heading">Process &gt; Shopfloor &gt; Work Tracking Analysis &gt; Set Rates Button </h3>



<p>This file path takes you to the Work Tracking Labour Rate Schedule window. </p>



<figure class="wp-block-image"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/table-description-automatically-generated-1.png" alt="Table

Description automatically generated" class="wp-image-4421"/></figure>



<h3 class="wp-block-heading">RATE SCHEDULE FIELD</h3>



<h3 class="wp-block-heading">Monday through Sunday</h3>



<p>Check the days for which the time relates to for each Rate in the schedule.</p>



<h3 class="wp-block-heading">Base Rate through Rate 5</h3>



<p>Select which rate is applicable on each day by selecting the tick box </p>



<h3 class="wp-block-heading">Working Time</h3>



<p>Enter the time into the working day up to which this rate applies on the checked days.</p>



<h3 class="wp-block-heading">Cancel button</h3>



<p>Aborts the process currently in session. The keyboard equivalent is the Esc key for Windows computers and Command-.(full stop or period) for the Mac.</p>



<h3 class="wp-block-heading">Ok button</h3>



<p>The OK button updates the data you have entered or confirms the selection and/or processes the function you have called.</p>



<figure class="wp-block-table is-style-regular"><table><tbody><tr><td><p>
  See Also
</p></td><td><ul>
  <li>
    Work Tracking Analysis
  </li>
  <li>
    Employee Maintenance
  </li>
</ul></td></tr></tbody></table></figure>



<p>
  Compiled in Program Version 6.00. Help data last modified 27 June 2022. 
</p>



<p>   Class wWtkRates last modified 25 May 2022</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwtkrates/">Work History: Work Tracking Labour Rate Schedule</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Works History: Work History Listing</title>
		<link>https://caliach.com/knowledge-base/wwohlist-2/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Thu, 23 Jun 2022 11:28:04 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/?post_type=ht_kb&#038;p=4402</guid>

					<description><![CDATA[<p>OVERVIEW This window opens when you operate the Process — Shopfloor — Review History for Part menu function. It enables you to view the costed operational batch history for all work orders for an assembly. File Path Process &#62; Shopfloor &#62; Review History for Part This file path takes you to the Work History Listing [&#8230;]</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohlist-2/">Works History: Work History Listing</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">OVERVIEW	</h2>



<p>This window opens when you operate the Process — Shopfloor — Review History for Part menu function. It enables you to view the costed operational batch history for all work orders for an assembly. </p>



<h2 class="wp-block-heading">File Path</h2>



<h3 class="wp-block-heading">Process &gt; Shopfloor &gt; Review History for Part</h3>



<p>This file path takes you to the Work History Listing window </p>



<figure class="wp-block-image"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/3_graphical-user-interface-application-description-6.png" alt="Graphical user interface, application

Description automatically generated" class="wp-image-4403"/></figure>



<h3 class="wp-block-heading">Part Number</h3>



<p>Part number unique identifier. {PTMFILE.PTMPTNO char 18}</p>



<h3 class="wp-block-heading">Up and Down Arrows</h3>



<p>Use these arrows to move through the part numbers. </p>



<h3 class="wp-block-heading">Description</h3>



<p>Part description. {PTMFILE.PTMDESC char 30}</p>



<h3 class="wp-block-heading">Stock UoM</h3>



<p>Standard stock unit of measure. {PTMFILE.PTMSTUM char 6}</p>



<h3 class="wp-block-heading">History List	</h3>



<p>Lists of work history records.</p>



<h3 class="wp-block-heading">Total Net Quantity</h3>



<p>The net received quantity of the assembly listed.</p>



<h3 class="wp-block-heading">Average Unit Assembly Cost</h3>



<p>The average unit assembly cost. </p>



<h3 class="wp-block-heading">Average Planned Work Centre Cost</h3>



<p>The average unit planned work centre cost based on route times.</p>



<h3 class="wp-block-heading">Average Actual Work Centre Cost</h3>



<p>The average unit actual work centre cost based on actual times. </p>



<p></p>



<p>Compiled in Program Version 6.00. Help data last modified 23 June 2022.  </p>



<p>Class wWohList last modified 25 May 2022. </p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohlist-2/">Works History: Work History Listing</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Works History Topic Contents</title>
		<link>https://caliach.com/knowledge-base/index-46/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 17:02:39 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/index-46/</guid>

					<description><![CDATA[<p>Works History Topic Contents</p>
<p>The post <a href="https://caliach.com/knowledge-base/index-46/">Works History Topic Contents</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Works History Topic Contents</h2>
<p id="navline"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a></p>
<p>Most topics are related directly to functional windows, menus or toolbars. Click on the topic to view details.</p>
<ul>
<li><a href="mwohhistory">&#8211; Shopfloor Menu</a></li>
<li><a href="wwohperform">Log Work Order Operational Performance</a></li>
<li><a href="wwohshop">Shopfloor Work Operation Data Collection</a></li>
<li><a href="wwspmaint">Special Tracking Work Order Maintenance</a></li>
<li><a href="wwohlist">Work History Listing</a></li>
<li><a href="wwohcomment">Work History Operation Comment</a></li>
<li><a href="wwowohselect">Work History WO Selection</a></li>
<li><a href="wwtkinput">Work Operation Tracking</a></li>
<li><a href="wwohprint">Work Order History Report Selection</a></li>
<li><a href="wwohselect">Work Order History Selection</a></li>
<li><a href="wwtkanal">Work Tracking Analysis</a></li>
<li><a href="wwtkoptions">Work Tracking Analysis Options</a></li>
<li><a href="wwtkcomm">Work Tracking Comment</a></li>
<li><a href="wwtkadd">Work Tracking Event Addition</a></li>
<li><a href="wwtkrecords">Work Tracking History Selection</a></li>
<li><a href="wwtkrates">Work Tracking Labour Rate Schedule</a></li>
<li><a href="wwtkselect">Work Tracking Selection</a></li>
</ul>
<p id="navline"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a></p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/index-46/">Works History Topic Contents</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Works History: &#8211; Shopfloor Menu</title>
		<link>https://caliach.com/knowledge-base/mwohhistory/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 17:02:39 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/mwohhistory/</guid>

					<description><![CDATA[<p>Works History: - Shopfloor Menu</p>
<p>The post <a href="https://caliach.com/knowledge-base/mwohhistory/">Works History: &#8211; Shopfloor Menu</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>&#8211; Shopfloor Menu</h2>
<p id="navline"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Works History</a> &gt; &#8211; Shopfloor Menu</p>
<p><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/mwohhistory.jpg" width="200" height="207" alt="Shopfloor Menu"/></p>
<p>This menu covers Shopfloor activities and covers conventional work operation history and work tracking.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Line</p>
</th>
<th valign="top">
<p align="left">Function</p>
</th>
<th valign="top">
<p align="left">Keys</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Shopfloor Data</p>
</td>
<td valign="top">
<p align="left">To record the completion of individual WO operations and the performance of production. This function opens the <a href="wwohshop">Shopfloor Work Operation Data Collection</a> window.</p>
</td>
<td valign="top">
<p align="left"> </p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Log WO Performance</p>
</td>
<td valign="top">
<p align="left">To log the time performance of operations carried out on a Work Order. This function opens the <a href="wwohperform">Log Work Order Operational Performance</a> window.</p>
</td>
<td valign="top">
<p align="left"> </p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Work Tracking Input</p>
</td>
<td valign="top">
<p align="left">Enables manual or bar-code entry of work tracking events. This function opens the <a href="wwtkinput">Work Operation Tracking</a> window.</p>
</td>
<td valign="top">
<p align="left"> </p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Work Tracking Analysis</p>
</td>
<td valign="top">
<p align="left">Analysis of work tracking and attendance events. This function opens the <a href="wwtkanal">Work Tracking Analysis</a> window.</p>
</td>
<td valign="top">
<p align="left"> </p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Special Tracking Orders</p>
</td>
<td valign="top">
<p align="left">To create or maintain special work orders used for work tracking. This function opens the <a href="wwspmaint">Special Tracking Work Order Maintenance</a> window.</p>
</td>
<td valign="top">
<p align="left"> </p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Review History for Part</p>
</td>
<td valign="top">
<p align="left">To view a list of work history records for a part. This function opens the <a href="wwohlist">Work History Listing</a> window.</p>
</td>
<td valign="top">
<p align="left"> </p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Print Work History Reports</p>
</td>
<td valign="top">
<p align="left">Provides selective reports on works history and factory operational performance. This function opens the <a href="wwohprint">Work Order History Report Selection</a> window containing the <a href="wwohselect">Work Order History Selection</a> subwindow.</p>
</td>
<td valign="top">
<p align="left"> </p>
</td>
</tr>
</table>
<h4>Work History Data</h4>
<p>Work Order history doubles for shop floor performance history. For each Work Order batch received into stock a record is created for each Operation listed on the Process Route for the produced Assembly. You can also record each Operation completion individually in Shopfloor Data. If no Process Route exists a single record is created with blank entries for the Route data. The production performance actual times and employee can be added and edited later within the Log WO Performance function.</p>
<p>The following fields are maintained in each Work History record:</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">WO Number</p>
</td>
<td valign="top">
<p align="left">The Work Order number.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Reference</p>
</td>
<td valign="top">
<p align="left">The Reference that was entered on the Work Order. This can be used for report selection.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Assembly</p>
</td>
<td valign="top">
<p align="left">The part number of the manufactured assembly the Work Order was subject to.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Part Issue</p>
</td>
<td valign="top">
<p align="left">The assembly part Issue Reference confirmed on the Work Order.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Operation Number</p>
</td>
<td valign="top">
<p align="left">The Operation sequence number in the Process Route at the time of receipt of the batch or the Operation completion. Changing the Process Route may mean that the Operation Number recorded in history is not the same as the current Process Route.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Work Centre</p>
</td>
<td valign="top">
<p align="left">Work Centre code within which the Operation was carried out.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Completion Quantity</p>
</td>
<td valign="top">
<p align="left">The quantity of the produced assembly completed in this batch or sub-batch. It is possible to record multiple receipts of a Work Order and different multiple completions for the same Operation. The times recorded against the record relate to the production of this quantity plus any scrap.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Scrapped Quantity</p>
</td>
<td valign="top">
<p align="left">The quantity of the final assembly that was scrapped during production. This is not scrapped material or parts as this is accounted for through the issue of extra items. This is the number of assemblies, out of the original order quantity that failed to meet standards that would allow them to be received into inventory.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Kitted Date</p>
</td>
<td valign="top">
<p align="left">The date on which a normal Work Order was kitted to production, or a Backflushed Work Order was created on the system.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Completion Date</p>
</td>
<td valign="top">
<p align="left">The date the batch was received into stock from production or the Operation was recorded as complete. For outwork Operations, this is the date of Purchase Order receipt.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Production Days</p>
</td>
<td valign="top">
<p align="left">The working days, calculated using the Make Calendar in the System Manager functions, from the Kitted Date to the Completion Date. The greatest value of this for a Work Order is comparable to the Lead Time for the assembly. This time can be used to auto-calculate part lead time by using the appropriate Global Change feature.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Standard Setup Time</p>
</td>
<td valign="top">
<p align="left">The setup time in Hours calculated from the Operation in the Process Route for the assembly at receipt time. In the case of multiple sub-batch receipts, this quantity is apportioned across all the receipts for this Operation.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Standard Run Time</p>
</td>
<td valign="top">
<p align="left">The run time in Hours calculated from the Operation in the Process Route for the assembly at receipt time and the quantity completed and scrapped.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Actual Setup Time</p>
</td>
<td valign="top">
<p align="left">The time in Hours, to 2 decimal places, it took to prepare the Work Centre for a production run. It should be the time taken from finishing a previous job to the start of preparation for the next job, less the processing time itself which will be dependant on the quantity in the batch. In the case of multiple sub-batch receipts, this quantity should be apportioned across all the receipts for this Operation. This quantity is entered by you in the Shopfloor Data. or Log WO Performance features.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Actual Run Time</p>
</td>
<td valign="top">
<p align="left">The time in Hours, to 4 decimal places, to carry out this Operation on the completed and scrapped quantity recorded. It should include all time spent on scrapped assemblies, so that true performance can be assessed correctly. This quantity is entered by you in the Shopfloor Data or Log WO Performance features.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Employee Code</p>
</td>
<td valign="top">
<p align="left">Employee code of the person responsible for carrying out the Process Route Operation for the quantity completed. This is entered in either the Shopfloor Data or Log WO Performance functions.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Current costs</p>
</td>
<td valign="top">
<p align="left">Current kit costs are held separately for Material, Labour, Outwork, Labour Overhead, Receiving Overhead, and This-Level elements. Kitting costs are recorded on the Work Order and passed into the Work History at the time of recording the first Operation completion. In the case of multiple sub-batch receipts, this quantity is apportioned across all the receipts for this Operation. If extra items, or shortages, are issued after the recording of the first Operation, these costs will be passed when the next Operation is recorded. This approach ensures that the kit costs are properly recorded against the Work Order&#8217;s history as a whole. However, as a consequence kit costs on any particular history record do not relate directly to the activity the record is associated with.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Planned Labour Cost</p>
</td>
<td valign="top">
<p align="left">The calculated cost of Labour for the Operation based on the Planned setup and run times and Work Centre Labour rates applicable to them. For Outwork Operations this cost must be added to the Planned overhead cost to yield the planned cost of the outwork.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Planned Overhead Cost</p>
</td>
<td valign="top">
<p align="left">The calculated cost of Labour Overheads for the Operation based on the Planned setup and run times and Work Centre Overhead rates applicable to them. For Outwork Operations this cost must be added to the Planned overhead cost to yield the planned cost of the outwork.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Actual Labour Cost</p>
</td>
<td valign="top">
<p align="left">The cost of Labour for the Operation based on the Actual setup and run times recorded in Shopfloor Data or Log WO Performance and the Work Centre rates.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Actual Overhead Cost</p>
</td>
<td valign="top">
<p align="left">The cost of Labour Overheads for the Operation based on the Actual setup and run times recorded in Shopfloor Data or Log WO Performance and the Work Centre rates.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Outwork Supplier</p>
</td>
<td valign="top">
<p align="left">The Supplier code for Operations carried out in Outwork Work Centres, recorded on receipt from the Purchase Order on which the Operation is processed.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Scrap Reason Code</p>
</td>
<td valign="top">
<p align="left">The entered code giving a reason for the scrap recorded. Reason codes must be pre-defined in the System Manager: Index Codes section. Analysis of scrap history should be undertaken using Ad Hoc Reports.</p>
</td>
</tr>
</table>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-40.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> If you are creating an Ad Hoc Report for analysis of Work Order cost performance, it is essential that you design it in such a way that all records of Work History are included for all Work Orders included in the analysis. Otherwise, the analysis may be misleading.</p>
<p/>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 4 Jun 2012 04:49:00.00. Class mWohHistory last modified 18 Apr 2012  12:39:49.</p>
<p id="navline"><img decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Works History</a> &gt; &#8211; Shopfloor Menu</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/mwohhistory/">Works History: &#8211; Shopfloor Menu</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Works History: Work History Operation Comment</title>
		<link>https://caliach.com/knowledge-base/wwohcomment/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 17:02:39 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wwohcomment/</guid>

					<description><![CDATA[<p>Works History: Work History Operation Comment</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohcomment/">Works History: Work History Operation Comment</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Work History Operation Comment</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Works History</a> &gt; Work History Operation Comment</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wwohcomment.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wwohcomment.jpg" width="347" height="98" alt="Work History Operation Comment Dialog"/></a></p>
<p>This window automatically opens when the <a href="../prefs/woptionslist">option</a> <b>optWOHistOpCom</b> is set to 1 or 2 and work history is recorded. When the option is set to 1, the window is available for each <a href="../wohistory/wwohshop">Shopfloor</a> or <a href="../wohistory/wwohperform">Log WO Performance</a> entry. If set to 2, it additionally opens for <a href="../workorders/wwoassyrecv">Receive WO</a> and <a href="../workorders/wwobackflush">Backflush WO</a>. Use the option <b>optWOHistOpComText</b> for default comment text.</p>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Work Order Number</p>
</td>
<td valign="top">
<p align="left">Work History. Work order number. {WOHFILE.WOHWONO char 6 Idx}</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Operation Number</p>
</td>
<td valign="top">
<p align="left">Work History. Operation number of process route. {WOHFILE.WOHOPNO integer}. Only visible when the comment is specific to an operation, otherwise the comment will apply to all operation history records.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Comment</p>
</td>
<td valign="top">
<p align="left">Work History. Work operation history comments. {WOHFILE.WOHCOMM char 10000000}</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">OK</p>
</td>
<td valign="top">
<p align="left">The OK button updates the data you have entered, or confirms the selection and/or processes the function you have called.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Cancel</p>
</td>
<td valign="top">
<p align="left">Aborts the process currently in session. The keyboard equivalent is the Esc key for Windows computers and Command-.(full stop or period) for the Mac.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../wohistory/wwohperform">Log Work Order Operational Performance</a></li>
<li><a href="../wohistory/wwohshop">Shopfloor Work Operation Data Collection</a></li>
<li><a href="../workorders/wwoassyrecv">Receive Work Order Assemblies from Production</a></li>
<li><a href="../workorders/wwobackflush">Work Order Backflush</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 12 Jul 2006 12:01:00.00. Class wWohComment last modified 18 Feb 2015  01:54:57.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Works History</a> &gt; Work History Operation Comment</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohcomment/">Works History: Work History Operation Comment</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Works History: Work Order History Report Selection</title>
		<link>https://caliach.com/knowledge-base/wwohprint/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 17:02:39 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wwohprint/</guid>

					<description><![CDATA[<p>Works History: Work Order History Report Selection</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohprint/">Works History: Work Order History Report Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Work Order History Report Selection</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Works History</a> &gt; Work Order History Report Selection</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wwohprint.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wwohprint.jpg" width="345" height="300" alt="Work Order History Report Selection"/></a></p>
<p>This report setup window provides you with the ability to choose a range of selections, sort order and report types.</p>
<p>You can drag and drop onto the window from the Parts ScratchPad to obtain a report of selected parts only.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-44.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> This window contains fields introduced with version 5 that enable additional search (and sometimes sort controls), such as <b>Adhoc extra where</b>. For more help on their use and examples see the <a href="../sql/introsql">Client-Server SQL Introduction</a> help.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">History Selection</p>
</td>
<td valign="top">
<p align="left">Enter a selection in the <a href="wwohselect">Work Order History Selection</a> subwindow.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Sort</p>
</td>
<td valign="top">
<p align="left">Choose the field for the primary sort on the report.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Substitute planned time where no actual is recorded</p>
</td>
<td valign="top">
<p align="left">Provides a report that lists performance times compared to those planned in the Process Routes.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Report Type</p>
</td>
<td valign="top">
<p align="left">Select a report type. Any custom reports entered in the Settings will appear at the bottom of the list.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Cancel</p>
</td>
<td valign="top">
<p align="left">Aborts the process currently in session. The keyboard equivalent is the Esc key for Windows computers and Command-.(full stop or period) for the Mac.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Print</p>
</td>
<td valign="top">
<p align="left">Will cause a report to be printed of the subject matter. Right-click to change the report destination.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../wohistory/wwohselect">Work Order History Selection</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 3 Jan 2015 11:25:00.00. Class wWohPrint last modified 17 Oct 2017  04:29:57.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Works History</a> &gt; Work Order History Report Selection</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohprint/">Works History: Work Order History Report Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Works History: Work Order History Selection</title>
		<link>https://caliach.com/knowledge-base/wwohselect/</link>
		
		<dc:creator><![CDATA[Brendan Proctor]]></dc:creator>
		<pubDate>Wed, 27 May 2020 17:02:39 +0000</pubDate>
				<guid isPermaLink="false">https://kb.caliach.com/index.php/knowledge-base/wwohselect/</guid>

					<description><![CDATA[<p>Works History: Work Order History Selection</p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohselect/">Works History: Work Order History Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><body></p>
<h2><a name="top"/>Work Order History Selection</h2>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Works History</a> &gt; Work Order History Selection</p>
<p><a href="https://caliach.com/wp-content/uploads/2022/12/wwohselect.jpg"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/wwohselect.jpg" width="299" height="146" alt="Work Order History Selection"/></a></p>
<p>This subwindow is used to define the range criteria for a selection of works history. It is displayed on windows requiring the selection of works history records.</p>
<h4>Parent Windows</h4>
<p><a href="wwohprint">Work Order History Report Selection</a><br />
<a href="../advanced/wlinkmaint">Link System Maintenance</a><br />
<a href="../general/wadhocgraphsmaint#tab2">Graphical Analysis Maintenance &#8211; Graphs Tab</a></p>
<h4>Operation</h4>
<p>Enter data in the data entry boxes to restrict the range of records. Records must meet all criteria entered to be selected. If the left and/or right data entry boxes are left blank for a particular criteria, records will be selected between the first and/or last otherwise qualifying record. Data entry boxes can be populated by finding a single item using <strong>Keyword Search</strong>, drag and drop from the <a href="../scratch/wscratchparts">Parts ScratchPad</a> or by double-clicking a list item from the <a href="../general/wkwdpopup">Keyword Result</a> window.
</p>
<p>Data records can be obtained using one of the following methods or a combination of them (see Tip below):</p>
<ol>
<li>Enter values into the selection ranges and use the <b>Standard Search</b>. The <a href="../general/msearchsub">context menu</a> provides a Clear Selection function.</li>
<li>Define or use a <b>Custom Search</b>.</li>
<li>Create an <b>Ad Hoc Search Calculation</b> using the <a href="../general/msearchsub">context menu</a> function.</li>
<li><b>Drag-and-drop</b> one or more lines from the Parts ScratchPad (or BoM and Where-Used Listing) onto the general window area.</li>
<li>Use the <b>ScratchPad Transfer Selected</b> function</li>
<li>Use the <b>KeyWord Search Transfer Selected</b> function</li>
</ol>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/tip40-40.jpg" width="24" height="24" alt="Tip"/><strong> TIP:</strong> Using an <b><i>Ad Hoc Search Calculation</i></b> (3) overrides any <b><i>Custom Search</i></b> (2) and a Custom Search overrides the <b><i>Standard Search</i></b> (1). In any of the search cases (1, 2 or 3), ScratchPad Transfer and Drag-and-Drop or KeyWord Search Transfer (4, 5 or 6) is <b>combinational</b>, so that records found using any of these methods must <b>also</b> conform to the search criteria adopted.</p>
<p><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/note40-44.jpg" width="24" height="24" alt="Note"/><strong> NOTE:</strong> This window contains fields introduced with version 5 that enable additional search (and sometimes sort controls), such as <b>Adhoc extra where</b>. For more help on their use and examples see the <a href="../sql/introsql">Client-Server SQL Introduction</a> help.</p>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Field</p>
</th>
<th valign="top">
<p align="left">Description</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">From and To</p>
</td>
<td valign="top">
<p align="left">Enter data that restricts the records selected. If left blank, data will be selected from the maximum and minimum extremes in the file. All selections criteria you enter will have to be met by each record processed.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Use custom</p>
</td>
<td valign="top">
<p align="left">To turn on and off the use of the custom search design. A custom search will override the standard search.</p>
</td>
</tr>
<tr>
<td valign="top">
<p align="left">Custom search name</p>
</td>
<td valign="top">
<p align="left">The name of the currently selected custom search. To use it click on the checkbox. To change it click on the Custom Search button.</p>
</td>
</tr>
</table>
<p/>
<table border="1" width="100%" cellspacing="0" cellpadding="2">
<tr>
<th valign="top">
<p align="left">Button</p>
</th>
<th valign="top">
<p align="left">Action</p>
</th>
</tr>
<tr>
<td valign="top">
<p align="left">Custom Search</p>
</td>
<td valign="top">
<p align="left">Opens the <a href="../general/wsearchselect">Custom Search Selection</a> window and checks the <strong>Use custom</strong> checkbox.</p>
</td>
</tr>
</table>
<p/>
<table border="0" cellspacing="0" cellpadding="2">
<tr valign="top" align="left">
<td width="80">See also: &#8211;</td>
<td>
<ul>
<li><a href="../general/msearchsub">Search Options Menu</a></li>
<li><a href="../wohistory/wwohprint">Work Order History Report Selection</a></li>
<li><a href="../scratch/wscratchparts">Parts ScratchPad</a></li>
<li><a href="../general/wkwdpopup">Keyword Result</a></li>
</ul>
</td>
</tr>
</table>
<p id="versionline">Compiled in Program Version 5.10. Help data last modified 3 Jan 2015 11:26:00.00. Class wWohSelect last modified 16 Jul 2016  06:55:56.</p>
<p id="navline"><img loading="lazy" decoding="async" src="https://caliach.com/wp-content/uploads/2022/12/arrowright-45.gif" width="9" height="10" alt="Document path" align="bottom"/> <a href="../index">Reference Contents</a> &gt; <a href="index">Works History</a> &gt; Work Order History Selection</p>
<p></body></p>
<p>The post <a href="https://caliach.com/knowledge-base/wwohselect/">Works History: Work Order History Selection</a> appeared first on <a href="https://caliach.com">Caliach</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
