The Require Validation at Synchronized Operations global option (NPI>System Configuration>Production Portal>Option Type: Synchronized Operations>Require Validation at Synchronized Operations) allows you to specify whether synchronized operations (primary work) must be confirmed by shop floor operators in Production—either by scanning the barcode of a serialized item or by checking a non-serialized quantity—before they can move on tosecondary work. The default setting for this option is False (no validation required).

...

Consider the following example of manufacturing custom cabinetry when the Require Validation at Synchronized Operations global option is set to False.

• All cabinet interiors and shelves are painted the same color as the cabinet frame.

• All drawer interiors are clear lacquered.

• Each upper cabinet has two shelves.

• Each lower cabinet has one shelf.

• The worktop backsplash is the same color as the worktop.

• All upper cabinets share the same height, width, and length.

• All lower cabinets share the same height, width, and length.

• Lower cabinets have different height, width, and length values from upper cabinets.

• Shelves, backsplashes and kickboards are all built using the Shelf process.

The following illustration shows some of the different cabinetry components (work top, shelf, cabinet, and so on) to be manufactured and the high-level process associated with each component (cut, paint, assemble, add hardware, and so on).

Image RemovedImage Added

To build the cabinets, the sales order is split into batches as shown in the following table.

• All units are the same width and all shelves are the same depth—this allows all shelves across all cabinets to be the same dimensions and as a result, they share the same batch.

• When building the shelves (Batch D) in Production, when the operator starts work on any quantity of the non-serialized shelves at the Paint operation, the system will verify that every shelf in Batch D is ready to be worked on at the Paint operation. If every shelf is ready, the primary work is valid and processing continues to validate all secondary work.

• The secondary work is every batch with the same batch attribute value (the paint color SO#1White) and an operation with its Synchronize Work property identifying the batch attribute—in this example the Upper Cabinets and Lower Cabinets (Batches E and F respectively).

• If all work for Batches E and F is valid to start work at their respective synchronized operations, the secondary work is considered valid and the WIP transaction for both the primary and secondary work will be started. The operator transacts the primary work normally; the secondary work is transacted in parallel.

• When the operator finishes theprimary work, they are also required to finish the secondary work. For each serialized unit and each non-serialized batch in the secondary work, the operator identifies the exit pathway and status. The WIP transaction is complete when the operator completes all primary work and allsecondary work.

Example 2

Consider the following example of manufacturing the same custom cabinetry as Example 1 when the Require Validation at Synchronized Operations global option is set to True.

• When the operator attempts to start a quantity of one or more at the Paint operation in Batch D in Production, the system will start the primary work as described in Example 1. When the secondary work is listed, the operator is required to verify that every item listed as secondary work (each serialized unit and each non-serialized batch) is present.

  • For serialized units, the operator is required to scan or enter the unit barcode (UID).

  • For non-serialized batches, the operator is required to scan or enter the batch name or selecting the check box in the Validation window.

• When every secondary work item listed is verified as present, the operator can select the Submit button and the WIP transaction starts.

• If the primary work includes serialized units, they are verified the same way as described previously for secondary work (the operator is required to scan or enter the unit barcode (UID)).

Example 3

Consider the same custom cabinetry example as Example 1 and Example 2 with the following exceptions:

• The Upper Cabinet is a separate sales order from the Lower Cabinet sales order.

• To optimize production, painting the colored Cabinet Doors needs to be synchronized to reduce the number of paint color changes required.

• The Cabinets and Shelves don't need to be synchronized across batches because SO#1Whiteis the predominant color used across all batches.

• The batch attribute value for the Cabinet Doors is shared across the two sales orders but the batch attribute value for the Cabinets and Shelves is not shared.