Material requirements
When using material-based recipes, the
FactoryTalk Batch
Server also looks at the material requirements when selecting equipment to bind to a recipe. For example, if there are two units (Unit_1 and Unit_2) in the area model and only Unit_1 can draw from a container that holds vanilla, then the FactoryTalk Batch
Server selects Unit_1 over Unit_2 for any recipe requiring vanilla.
TIP:
If dynamic unit allocation is enabled, the actual material does not have to exist but the capability of meeting the material requirement must exist.
The following examples use the class-based recipe and area model shown in this diagram to explore the different factors that help the
FactoryTalk Batch
Server determine if material is available.
TIP:
In the following examples, all lots and containers are in a Ready to Use state and the container priorities are all equal. Also, it is assumed that there is only one area model. If there is more than one
FactoryTalk Batch
Server interacting with the Material Server, it is vastly important that the AREA name be unique in each .cfg
file.Provide Feedback