Option codes in Production
The following topics describe how option codes affect what happens in the FactoryLogix Production client application.
List of operations for a batch
When determining the list of operations for a batch, the system does the following:
For a non-configured operation where no option codes are identified explicitly (the Option Code property is set to All), the operation is listed.
For a configured operation where option codes are identified explicitly (the Option Code property is not set to All), the operation is listed if the option code requirements in the operation’s Option Codes property evaluate to True when using the batch-level and unit-level option codes defined in the batch configuration.
Any unit-level option code with a state of Unknown is treated as Selected.
List of operations for a unit
When determining the list of operations for a serialized CTO unit, the system does the following:
For a non-configured operation where no option codes are identified explicitly (the Option Code property is set to All), the operation is listed.
For a configured operation where option codes are identified explicitly (the Option Code property is not set to All), the operation is listed if the option code requirements in the operation’s Option Codes property evaluate to True when using the batch-level option codes defined in the batch configuration and the unit-level option codes defined against the unit.
Any unit-level option code with a state of Unknown will be treated as Selected.
Steps and activities for an operation
When a shop floor operator opens an operation without starting a WIP transaction, the steps and activities loaded for the operation are determined as follows:
For an unconfigured step/activity where no option codes are identified explicitly (the Option Code property is set to All), the step/activity will be listed.
For a configured step/activity where option codes are identified explicitly (the Option Code property is not set to All), the step/activity will be listed if the option code requirements in the step/activity’s Option Codes property evaluate to True when using the batch-level option codes defined in the batch configuration.
If a configured step/activity includes any unit-level option codes, the step/activity will not be listed.
Starting a single serialized unit from the Home window
When an operator starts work on a serialized unit by entering (or scanning) the unit UID in the Production Home window, the system starts the unit at the operation recorded as its next operation.
Starting a single serialized unit from an open operation
When an operator attempts to start a single serialized unit from within an operation (or from the Home window), the system verifies that it is valid for work to start on the identified unit at that operation. If work at the operation is allowed and the WIP transaction is started, the system does the following:
Compares the steps and activities loaded for the current operation to the steps and activities that should be loaded based on the option code requirements as detailed in each configured step or activity's Option Codes property.
Compares the combination of the batch-level option codes selected in the batch configuration plus the unit-level option codes identified against the identified unit that are in the selected state.
Starting multiple serialized units from an open operation
When an operator attempts to start multiple serialized units from within an operation, the system does the following:
Adds the list of unit UIDs to be started to the list of units to be started.
When the start is triggered, the first UID is started the same way as when starting a single UID (which may include reloading the steps and activities).
After the first UID is started successfully, all subsequent UIDs will only be started if the unit-level option code configuration is an exact match to the unit-level option code configuration associated to the first unit started.
Route status in the Trace window
When the UID of a serialized configurable assembly is used in the Trace window in Production, the list of operations displayed on the Route Status tab is determined as follows:
All unconfigured operations are listed.
All operations at which WIP has been recorded for the identified UID are listed.
All configured operations where the combination of batch-level option codes marked as Selected in the batch configuration and all the unit-level option codes marked as Selected or Unknown against the identified UID meet the option code requirements as detailed in the operation’s Option Codes property are listed.
BOM display on the shop floor
The BOM can be displayed on the shop floor in Production several ways:
In a BOM block in a visual aid
Using the BOM Block operator interface gadget
Using the BOM Item Details operator interface gadget
Using the BOM Viewer operator interface gadget
BOM filtering
If no units are in progress, the BOM is filtered according to the combination of the batch- and unit-level option codes defined in the batch configuration.
If one unit is in progress, the BOM is filtered according to the combination of the batch-level option codes defined in the batch configuration plus the unit-level option codes that are recorded as Selected or Unknown against the unit in progress.
If more than one unit is in progress and activities are being performed By Activity (not By Unit), the BOM is filtered according to the combination of the batch-level option codes (defined in the batch configuration) plus the unit-level option codes that are recorded against the units in progress recorded as Selected or Unknown. If one UID in progress has a unit-level option code set to Not Selected and another in progress has the same unit-level option code set to another state (Selected or Unknown), the option code is considered Selected for the purpose of displaying the BOM information.
Calculating the next operation
When an in-progress transaction is completed, FactoryLogix determines the next operation at which the unit is expected. (The combination of the selected batch-level option codes defined in Batch Configuration plus the unit-level option codes recorded against the unit in progress recorded as Selected or Unknown help determine the next operation.)
Persistence of unit-level option codes
At any point in time a unit is associated with one assembly revision, one process revision, and one batch. However, over time, a unit may be associated with:
A different batch of the same process revision
A different batch of a different process revision of the same assembly revision
A different batch of a different process revision of a different assembly revision
When a unit is transitioned from one batch to another and the assembly revision stays the same, the unit-level option codes for the new batch are inherited from the old configuration—regardless of whether the option code in the old batch was set at the batch or unit level.
When a unit is transitioned from one batch to another, the batch and assembly revision change and the unit-level option codes for the new batch are set to Unknown status.
