Sorter Scenarios - Modeling and Administration#
Master Data#
To use the Sorter logic, the involved entities' Master Data needs to have the following setup:
- Sorter Resources must have the SemiRequiresMaterialMovement attribute set to True.
- Sorter Services need to have the SemiResourceJobType attribute set - Different Services will be required for each Sorter Job Type (e.g. Scan, Split, Merge, etc)
- Steps that require a Sorter machine for logistics operations must have the SemiRequiresSorterForLogistics attribute set to true, and DefaultFutureLogisticActionExecutionMode set to Manual.
Configuration#
The following table describes the most relevant configuration entries for integrated Sorter MES Scenarios.
| Path | Description |
|---|---|
| /Semi /MaterialPhysicalIdProperty/ | Material Property (Description or ManufacturerLotNumber) or Attribute where the Physical ID (e.g. Wafer Scribe ID) is located. Default = Name |
| /Semi /Sorter /EnableSplitMerge/ | Enable/Disable Sorter Split/Merge feature hooks. |
| /Semi /Sorter /ResourceJobType/* | List of Resource Type Names to be used - Resource Types are defined in Lookup Table, and new Types or other Names can be used. This section allows mapping which ResourceType lookup entry should trigger each Sorter-specific scenario. |
| /Semi /Sorter /ResourceJobSubType/* | List of Resource Sub-Type Names to be used - Similar with Resource Types, Sub-Types are defined in Lookup Table and new can be renamed and remapped to a Sorter-specific scenario. |
| /Semi /Sorter /SkipWaferIdScanValidationOnTrackOut/ | When set to true, allows Track Out on Scan-Validate cases, even if there are Wafer ID Mismatches. |
| /Semi /Sorter /SubMaterialForms/ | Defines the Forms to use when Expanding Materials on Scan-Expand operations. Supports a list of Form names separated by ';' - the system will try to find the first match with a possible sub-material Form Relation during execution. |
| /Semi /Sorter /SubMaterialUnits/ | Defines the possible Quantity Units to use when Expanding Materials on Scan-Expand operations. Supports a list of Form names separated by ';' - the system will try to find the first match with an existing unit (primary or secondary) of the parent Material during execution. |
Assumptions and Restrictions#
- Scan operations and Multi-run Partial execution require the resource to be automated and in Online automation mode.
- Currently only one container can be sent to the equipment on Scan scenarios. When multiple containers are docked, only the first container associated with the resource job will be scanned. To scan another container, the operator must first undock the previously scanned container or remove its lot in the sorter view.
- Standard Move Next is currently not prevented if a Material has a Pending Split/Merge Future Action on Processed waiting for Sorter execution.