Adding and Updating Operations
You can add operations to discrete jobs with statuses of Unreleased, Released, Complete, or On Hold. You can add operations to repetitive schedules with statuses of Unreleased. You can add operations to jobs and repetitive schedules with or without routings.
You can create a routing for a job or schedule that does not have a routing by adding operations to it. When you add the first operation, the system automatically defaults an operation sequence of 1 for the new operation and assigns job or schedule material requirements to this operation. If the job or schedule is already released, the system also loads the job or schedule quantity into the Queue intraoperation step of the new operation.
Suggestion: If you add an operation to a job or repetitive schedule, you may want to reschedule the job or repetitive schedule to correctly reflect the start and completion dates.
You can update the operations of discrete jobs with statuses of Unreleased, Released, Complete, or On Hold. You can update the operations of repetitive schedules with statuses of Released, Complete, or On Hold as long as there are no other active schedules for the assembly on the line.
Attention: You cannot update operation dates for repetitive schedules of any status.
You can attach illustrative or explanatory files -- in the form of text, images, word processing documents, spreadsheets, video, and so on -- to operations. See: About Attachments.
Prerequisites
To add or update an operation:
3. If you select a line and assembly, choose the repetitive schedule by selecting the first unit start date of that schedule. If you have selected a discrete job, the system displays the scheduled start date of the job.
4. Optionally, choose the Find button to populate the Operations region.
6. Select the Operation Code of a standard operation or leave the Operation Code blank.
If you add a standard operation by selecting its Operation Code, the Department, Count point, Autocharge and Backflush options, Minimum Transfer Quantity, and Description are automatically defaulted. Resource requirements that are associated with the standard operation are also defaulted. You can update these defaults at any time.
You can update the operation codes of unreleased discrete jobs. If you update the operation code by selecting the operation code of a standard operation, existing operation information is overridden.
If you leave the Operation Code blank, you must manually define the operation.
The Department identifies which group -- people, machines, and/or suppliers -- is performing the operation. Departments are also used for charging resources at an operation and are required even if there are no resources assigned to the operation.
If you add a standard operation, the system displays the Department of that operation as the default. If there are resources assigned to the standard operation, you cannot update this field.
Operations you must always perform, for example, critical, time-sensitive, or bottleneck operations, should be made count point operations. Operations that are not always performed should be made non-count point operations.
When you perform move transactions, the system defaults in the next count point operation as the To operation sequence. For example, suppose you have three operations at sequences 10, 20, and 30 defined as count point, non-count point, and count point respectively. When you select operation 10 as the From operation, the system automatically defaults operation 30, the next count point operation, as the To operation. You can override this default and choose operation 20, if required.
If you add an operation that is not a standard operation, the system automatically makes the operation a count point operation. If you add a standard operation, the system displays the count point option of that operation as the default.
Operations you must always charge resources to should be made autocharge operations. Operations that do not always require resource charges should be made non-autocharge operations. See: WIP Move.
Autocharge operations automatically charge WIP Move resources when you move assemblies through or beyond them. For example, suppose you have three operations at sequences 10, 20, and 30 defined respectively as autocharge, non-autocharge, and autocharge operations. When you move assemblies from the Queue intraoperation step of operation 10 to an intraoperation step that completes assemblies at operation 30 (To Move, Scrap, or Reject), resources at operations 10 and 30 are charged, but those at operation 20 are not. To charge resources to operation 20, you must move assemblies into a completion intraoperation step (To Move, Scrap, or Reject) of that operation. See: Intraoperation Steps.
The count point and autocharge check boxes work together. Operations can be count point/autocharge, non-count point/non-autocharge operations, or non-count point/autocharge. They cannot be count point/non-autocharge. See: Count Point and Autocharge Fields.
If you add a standard operation, the system displays the autocharge option of that operation as the default. If you add an operation that is not a standard operation, the system makes the operation a count point operation.
Operation Pull components that are assigned to backflush operations are automatically backflushed (pulled) from inventory when assemblies are moved and completed at that operation. Also backflushed are all Operation Pull components that have not been backflushed because they are assigned to non-backflush operations prior to the backflush operation.
If you add an operation that is not a standard operation, the system automatically makes the operation a non-backflush operation.
Caution: The last operation in a routing must always be a backflush operation. Materials are not backflushed from inventory if the last operation is a non-backflush operation and operations prior to it are non-backflush operations that have Operation Pull components that have not been backflushed.
If you add a standard operation, the system displays the minimum transfer quantity of that operation as the default. If you add an operation that is not a standard operation, the system displays 0 as the default. See: Creating a Standard Operation..
If you attempt to move fewer that the minimum transfer quantity, you receive a warning message but are allowed to continue.
12. In the Description alternative region, enter the Description.
If you add a standard operation, the system displays the description of that operation as the default.
To midpoint reschedule a discrete job:
To manually schedule/reschedule a discrete job operation:
- You can manually schedule/reschedule a discrete job operation by changing one or more of its dates. The job must have a status of Unreleased, Released, Complete, or On Hold.
Attention: If you change the LUCD of the last operation to a date that is greater than the job completion date, the job completion date is updated to the LUCD. If you change the FUSD of the first operation to a date earlier than the job start date, the job start date is updated to the FUSD.
To update operation resource requirements:
See Also
Working with Attachments
Deleting Operations
Overview of Routings and Operations
Overview of Routings
Creating a Routing
Define at least one standard discrete job, one non-standard discrete job or one repetitive schedule. See: Defining Discrete Jobs Manually and Defining Repetitive Schedules Manually.