Time tracking plan

Type in or select the production site at which operator time is to be recorded. This field is mandatory.

Use this field to identify a specific operator for which time and progress is to be recorded.

This field displays the description from the employee profile and cannot be modified.

Filter for results within a date range. For a single day, enter the same date in the from/start tracking date and To/End date fields. You can leave the from date field blank to search all records to date.

Use this field to filter the records to be tracked. Select one of the following values:

• All
• Closed
• Not closed

Filter for results within a range of work orders. For a single work order, enter the same work order number in the from/start Work order and to/end Work order fields.

Filter for results within a range of operation sequence numbers. For a single operation sequence number, enter the same sequence number in the from/start Operation and to/end Operation fields.

Filter for results within a range of finished products (BOMs). For a single bill of materials (BOM), enter the same product code in the from/start Released product and to/end Released product fields.

Filter for results within a range of routings. For a single route, enter the same routing code in the from/start Routing and to/end Routing fields.

Filter for results within a range of routing codes. Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality (for use in a manufacturing environment, for costing or for capacity planning).

For a single routing code, enter the same sequence number in the from/start Code and to/end Code fields.

Filter for results within a range of actual work centers. For a single work center, enter the same work center code in the from/start Work center and to/end Work center fields.

Use this field to define the cumulative time worked between the defined period (dates) if you want the time to be apportioned proportionally over the selected records. Global time is apportioned according to the planned times.

Use this field to define the time unit in which the defined (global) operator time is expressed. The time unit can be 'hours' or 'minutes'.

The presence of this field is subject to the activity code WRH.

It represents the movement warehouse for all order lines.

• It can be modified if it is defined as enterable in the entry transaction.
  If it is entered, it serves as a filter for stock detail line selection.
  If it is not entered, the warehouse defined by default for this type of movement in the product-site record will serve as a filter for the selection.
• It cannot be modified when the entry transaction is set up as single-warehouse managed. The header warehouse is then mandatory.
  To manage multiple warehouses on the lines the entry transaction must be set up so that it can be entered. The selection of a single product line distributed over multiple warehouses is available by clicking Enter detailed quantites from the Actions icon.
  If a single product line is distributed over multiple warehouses, the corresponding fields display the '$' character.

This tracking date defaults to today's date. This date will be used as the posting date for all stock transactions linked to this tracking.
You can enter an earlier date than today but not a later date. The system will validate that the date falls in a period for which stock updates are authorized.

This field displays one of the following values:

• Work order. The declared time relates to an operation for a work order;
• Product. The declared time relates to a routing operation;
• Miscellaneous. The declared time relates to time on a work center such as maintenance of a machine. Miscellaneous time is usually used for recording non-productive time.
  
  

This field displays the work order number (unique ID) progress for this operation is being recorded against.

Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality (for use in a manufacturing environment, for costing or for capacity planning).

This product code describes what is referred to as a "Bill of Materials" or a "BOM". A BOM contains structured information for making and costing a product. It defines the components that make up a product, and given this, the cost of the product.

The BOM code matches the product code.

Multiple bills of materials (BOMs) can be defined for a single product. Each BOM code can be assigned specific management features. For manufactured or subcontracted products this includes restriction of the BOM to a specific site and to specific areas of functionality (for costing or for capacity planning).

The first valid BOM code for this product at this production site is displayed by default.

This field displays the sequence number of this operation.

The operations in a routing used for manufacturing a product are assigned operation numbers. Each operation number corresponds to a task carried out on a given resource, with given times.

This field displays the description defined for the routing operation.

This field identifies the standard operation used to create this operation. Standard operations are simply 'template' operations that provide default information to be assembled into routings for producing or processing a particular product.

This field identifies the production resource used for this operation, that is the actual work center used. This work center is the main (principal) work center for this operation. It can be a machine or labor work center. The work center is attached to a work center group.

This field identifies the labor work center assigned to this machine. For example, the labor work center that relates to the crew that operates this machine.

The work center site of a 'labor' work center must match the site for the routing code, if defined.

Scheduling is not carried out for labor work centers as they are considered secondary and 'always available' (or available at the same time as the main work center). Their load is managed for information purposes only using the coefficients defined for the main work center.

If the main work center is of type 'subcontracting' there is no associated secondary work center.

This is the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center.

This coefficient applied to the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center.
This field is only available for entry if the labor work center is entered.

This is the coefficient applied to the planned operation time. It is used to obtain the operation time for the labor work center linked to the principal work center. This field is only available for entry if the labor work center is defined.

Operation times are subdivided as follows:

Proportional times are expressed for the production of an operation unit (and not in the stock unit of the finished product using the routing).

Work order operation quantities are expressed in the operation unit. Use this operation unit to express operating time in a different unit to that of the product being produced by the routing.

For example, a product managed by unit is subject to three different operations, none of which produce intermediate stock:

• Mixing time (operation 1) is expressed for a lot with Kilogram as the unit;
• Extrusion time (operation 2) is a rate in meters per hour;
• Cutting time (operation 3) is expressed in hours per unit.

There is no need to create semi-finished products for each production phase.

The operation unit is associated with a conversion coefficient for the stock unit of the product being produced by the routing and the operation unit.

This is the coefficient applied to the planned operation time. It is used to obtain the operation time for the labor work center linked to the principal work center. This field is only available for entry if the labor work center is defined.

Operation times are subdivided as follows:

Proportional times are expressed for the production of an operation unit (and not in the stock unit of the finished product using the routing).

This field displays the unit in which this work order operation quantity is expressed. Work order operation quantities are expressed in the operation unit.

Use this field to record the actual completed quantity, in total. This includes the rejected quantity. The quantity is expressed in the operation unit.

Use this field to record the actual quantity rejected. This figure cannot exceed the produced quantity. Click Detail entry action from the Actions icon in the field to assign a rejection code to a rejection quantity.

The time unit defines how time for the operations in this routing is expressed. The time unit can be 'hours' or 'minutes'.

It applies to the setup time, run time and the rate for all operations in the routing.

Use this field to define the actual time taken to set up this machinery ready for use. The time is expressed in the defined time unit. The time can be zero (0).

Use this field to record the actual time taken to produce a single unit for this operation. The time is expressed in the defined time unit.

Use this field to record the actual time taken to perform this operation for the required number of items.

Click the Entry by range action from the Actions icon in the field to record actual setup and run times for an operation over a range of dates and times. The actual operation time is calculated from the entered values.

The operating time:

• Is defined in hours or minutes (field Time unit).
• Is expressed for 1, 100, 1000 or a lot of units of the operation based on the management unit,
• Can be proportional or fixed based on the operating time type.
  For example:
  Time unit = Hours
  Time type = proportional
  Management unit = Time for 100
  Operating time = 2
  Operating unit = Kg
  Finished product unit = Un
  REL-OPE conversion coefficient = 0.5
  The operation time is equal to 2 hours for 100 Kg. If the Work order is launched for 1000 units of the finished product, the time necessary to produce this operation is 10 hours to obtain 500 Kg.

Use this field to specify whether the line must be closed or not ('Yes'/'No').

Use this field to identify the operator that performed this operation.

Use this field to associate a predefined information message with the information recorded against this operation.

Use this field to associate a predefined rejection message with the rejection quantity recorded against this operation. Click Detail entry action from the Actions icon in the field to assign a rejection code to a rejection quantity.

This field displays the code of the quality record or the technical sheet used for quality control.

This field displays the operation end date.

The setup determines if the analytical dimensions can be modified. They are initialized based on the setup of the default dimension.

In creation mode, if no order line has been entered and the project code is modified, the analytical dimensions are reset based on the setup of default dimensions.

In creation mode, as in modification mode, if an order line is entered and the project code is modified, the analytical dimensions are not reset.

Click this check box to raise (or report) an incidence of non-conformance against this specific routing operation immediately you validate this tracking record.

Essentially this check box identifies if you are authorized to raise a non-conformance incident requesting an investigation into the 'cause' of a problem. You should report an incidence of non-conformance if you have observed or been informed of a problem, or failure or potential failure in a service, or in a process, or in the system. Typical routing operations within a manufacturing environment that could give rise to a non-conformity might be that the setup and run time are not adapted to the machine, the order of an operation must be changed, additional operations are necessary or a more stable machine must be used. The non-conformance incident forms the details of the non-conformity; it becomes the source of the information to support investigations into the root cause, or failure.

Click this check box to raise (or report) an incidence of non-conformance against this specific routing operation immediately you validate this tracking record.

This check box is displayed if you are authorized to raise a non-conformance incident requesting an investigation into the 'effect' of a problem. You should report an incidence of non-conformance if you have observed or been informed of a problem, or failure or potential failure in a resource used for the routing operation. Typical operational resources within a manufacturing environment that could give rise to a non-conformity often occur at run-time such a broken machine or a defective tool. The non-conformance incident forms the details of the non-conformity; it becomes the source of the information to support investigations into the root cause, or failure.

 If you select either of these check boxes (Non-conformance - process (field NCSPRO)/Non-conformance - resource (field NCSRES)) you are indicating that a non-conformance incident should be raised against this routing operation or the resource used for this operation. Essentially you are triggering the creation of a non-conformance incident requesting an investigation into the 'cause' or 'effect' of a problem. Whatever your role within your organization you are only required to provide minimal details for any non-conformance incident. If the Probable cause and/or Non-conformance description fields are displayed you can leave the default values or change them. You do not need to think about a possible or probable cause of the incident, or describe the details of the 'problem'.

Leave the default probable or possible cause code, or select a different code. This field is mandatory.

You can support your selected value by adding your suggested reason for raising a non-conformance incident to the free-format Non-conformance probable cause field which is available from the Actions icon on each applicable line in the grid. Providing additional information is optional but it will be used to help establish what the root cause of this incident might be. This action is only displayed if the Non-conformance - process (field NCSPRO) or Non-conformance - resource (field NCSRES) field is selected.

The default code and the list of probable causes is defined in Miscellaneous table 804 - Probable cause.

Leave this field blank or type in a short description of this incidence of non-conformance.

Whatever your role within your organization you are only required to provide minimal details for any non-conformance incident. If you leave this field blank it will be set to the default value. So that you do not need to describe the details of the 'problem' the default Non-conformance description will identify that you are raising a non-conformance against this operation. It will include references to the origin of this request and any applicable line or operation numbers. For example, if you are recording time against an operation for a work order and you click the Non-conformance - resource (field NCSRES) field to raise a non-conformance against a resource used for this operation, the default description will reflect this as 'Operation tracking – resource WOTFR0120066 15'.

If you know or understand, or have additional details about the 'problem', you can add this information to the free-format Non-conformance probable cause field which is available from the Actions icon on each applicable line in the grid.