Skip to content

Container E87 Carrier Read

Container Integration with E87#

E87 defines a Carrier State model as following:

CarrierStateModel

Validation of the Container (Carrier) Id and Slot Map should be done as replying to the right transactions of the state model, using Carrier Action Request (S3F17).

As such the following transactions of the state model should be used to trigger the changes using the following workflows:

Transaction Transaction Description Workflow Action Description
E87 CSM -> 7 Id Not Read to Waiting for Host CarrierIdRead_01_EventReceived Request Container Dock, will trigger Dock related System Event and Workflow
E87 CSM -> 14 Slot Map Not Read to Waiting for Host SlotMap_01_SlotMapReceived300mm Validates Slot Map, will trigger Carrier Action Request based on the validation result
E87 CSM -> 15 Waiting for Host to Slot Map Verification Ok SlotMap_02_SlotMapVerificationOk Depending on the configuration it Dispatch, Dispatch and Track or does not execute anything on the Parent Material that have Child Material belonging to the Container. Slot Map Validation on Host Side
E87 CSM -> 13 Slot Map Not Read to Slot Map Verification Ok SlotMap_02_SlotMapVerificationOk Depending on the configuration it Dispatch, Dispatch and Track or does not execute anything on the Parent Material that have Child Material belonging to the Container. Slot Map Validation on Tool Side

Note

Automation Controller must also have the following workflows (they do not require modification):

  • Dock_01_DockRequestReceived300mm
  • CarrierAction_01_ProceedWithCarrier
  • CarrierAction_02_CancelCarrier

Carrier Action Request - Proceed with Carrier Behavior#

Carrier Action request allows for different contents on the Proceed With Carrier message.

Depending on these contents the validation of the Slot Map will be done by either the Host or the Tool.

If the intended behavior is Host driven validation, two Proceed With Carriers will need to be sent:

  • One containing just the Carrier Id triggered by the E87 CSM -> 7.
    • This will be sent by the MES triggered Dock workflow.
  • A second one container the Carrier Id and all the remaining required informations trrigered by the E87 CSM -> 14, if the Slot Map is valid.
    • Note than, in the case the host will send the contents of the Carrier Slot Map on the E87 CSM -> 14.
  • This behavior can be set via a flag on the Template Controller Workflow for the Proceed With Carrier.

Note

In this format you will have the Slot Map on your side, allowing you to validate the Slot Map on the Track In Validator Generic Workflow, this will not be true on the other scenario.

If the intended behavior is Tool driver validation only one Proceed With Carrier will need to be sent:

  • The E87 CSM -> 7 triggered action will contain the entire information.
    • This will be sent by the MES triggered Dock workflow.
  • If the Slot Map is not valid you will receive a E87 CSM -> 14, this should always trigger a Cancel Carrier Carrier Action request.

Note

If you are using this format you will need to disable the Slot Map validation at Track In time, via passing the flag Do Not Validate Slot Map as True to the Track In Validation workflow. This is needed as you are not storing information regarding the Slot Map read by the tool, hence you do not have the information needed.