Dynamic unit allocation

If you enable dynamic unit allocation (
also referred to as Late Binding
) in the Recipe Editor, there are more options available for unit binding when you create a procedure. First you will assign a unit requirement name to all unit instances of a specific unit class. When a recipe is put on the Batch List and the server encounters the unit requirement name, it looks up all the unit classes or instances that are mapped to the unit requirement name. You assign a binding type that applies to each unit instance assigned to the unit requirement.
FTBMM_GRG_equipment_requirement_definition
  • First Available
    While the batch is running the FactoryTalk Batch Server allocates the first available legal unit to the recipe. Binding occurs when the first unit procedure mapped to the unit requirement name is ready to run. For material phases, if there are multiple equipment modules associated with a container, the first available equipment module is selected. If multiple equipment modules are available, the one with the lowest controller ID is selected. First available binding is also dependent on any binding requirements or preferences in the recipe.
  • Prompt
    While the batch is running the operator is prompted to bind to a specific unit when the first unit procedure mapped to the unit requirement name is ready to run. For material-based recipes, the operator is prompted to select a material or lot when a recipe phase is about to run.
  • At Batch Creation
    When the batch is created the operator binds the recipe to a specific unit.
  • Operator Choice
    When the batch is created, the operator can choose to bind the recipe to a specific unit or choose either the Prompt or First Available binding method.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal