Action Codes
- Last UpdatedNov 03, 2021
- 5 minute read
Any operation performed on a batch, phase, or unit, during batch execution in the Batch Display has a corresponding Event Action Code. These codes are stored in the BatchDetail, BatchQuestion, and BatchIdLog tables in the BatchHistory database.
For example: When a batch is started, the Action Code 201 (Batch set Start) is stored in the BatchDetail table. After the Status of the batch changes to Run, the Action Code 400 (Batch received Run) is stored in the BatchDetail table.
The following table lists all the Action Codes generated during the batch execution, depending on the operations performed by user.
|
Action Code |
Action Description |
Event Label |
Event Details |
|---|---|---|---|
|
201 |
Batch set Start |
Batch |
Set is when the Batch Manager sends a command (e.g. sets Start bit). |
|
202 |
Batch set Hold |
Batch |
|
|
203 |
Batch set Restart |
Batch |
|
|
204 |
Batch set Abort |
Batch |
|
|
400 |
Batch received Run |
Batch |
Received is when the Batch Manager gets a status update (e.g. sees Run bit go true). |
|
401 |
Batch received Held |
Batch |
|
|
402 |
Batch received Aborting |
Batch |
|
|
209 |
Batch received Aborted |
Batch |
|
|
205 |
Batch received Done |
Batch |
|
|
206 |
Batch received Closed |
Batch |
|
|
260 |
Batch mode changed to Automatic |
Batch |
The recipe procedure is processed exactly as defined in the recipe. |
|
261 |
Batch mode changed to Semi-Automatic |
Batch |
Each phase must be acknowledged by the operator before it is processed. Prior to acknowledging the phase, phase parameter values can be edited by the operator. When a batch is running in the Semi-Automatic mode, the Batch Manager will stop at each phase before executing. The operator can execute the phase by clicking the Ack button, or skip the phase by clicking the Skip button. The phase Abort button becomes the phase Skip button in Semi-Automatic mode if the phase is not yet started The batch is automatically placed in the Semi-Automatic mode when a phase is cancelled if the parameter "Semi-auto on abort" is on. |
|
262 |
Batch mode changed to Manual |
Batch |
Any phase in the recipe defined for equipment that is allocated to the batch can be manually processed. |
|
403 |
Batch received Lock |
Batch |
The batch is in the process of aborting phases and entering the Jump mode. |
|
404 |
Batch received Locking |
Batch |
|
|
405 |
Batch received Locked |
Batch |
The batch has been successfully locked and the Jump mode is enabled. |
|
406 |
Batch received Unlock |
Batch |
The batch has been successfully unlocked and the Jump mode is disabled. |
|
207 |
Batch Warm Restart |
Batch |
The Batch Manager is restarted and the batches prior to shutdown are restored to the Batch Scheduler. |
|
208 |
Batch Redundancy Switchover |
Batch |
Changeover between primary and secondary batch servers. |
|
210 |
Unit Allocate |
Unit |
Equipment (Unit) allocated to a batch. The unit is acquired by the batch and cannot be used by other batches. |
|
211 |
Unit Release |
Unit |
Equipment (Unit) released from a batch. The unit is released by the batch and is available to be used by other batches. |
|
221 |
Unit Wait for Allocate |
Unit |
Waiting for the user to allocate equipment. |
|
222 |
Unit Received Allocate |
Unit |
Manual equipment allocation is complete. |
|
410 |
Unit received Ready |
Unit |
Received is when the Batch Manager gets a status update (e.g. sees Run bit go true). |
|
411 |
Unit received Run |
Unit |
|
|
412 |
Unit received Held |
Unit |
|
|
413 |
Unit received Alarm |
Unit |
|
|
270 |
Unit set Hold |
Unit |
Set is when the Batch Manager sends a command (e.g. sets Start bit). |
|
271 |
Unit set Restart |
Unit |
|
|
272 |
Unit set Abort |
Unit |
|
|
500 |
Unit Procedure Received Run |
Unit Procedure |
Unit procedure starting |
|
501 |
Unit Procedure Received Done |
Unit Procedure |
Unit procedure done |
|
502 |
Operation Received Run |
Operation |
Operation starting |
|
503 |
Operation Received Done |
Operation |
Operation done |
|
223 |
Phase Wait for Entry Ack |
Phase |
Can relate to the batch in the Semi-Automatic mode OR if the phase is set to require an entry acknowledgement in the recipe configuration. |
|
224 |
Phase Received Entry Ack |
Phase |
|
|
245 |
Phase Wait for Exit Ack |
Phase |
If the phase is set to require an exit acknowledgement in the recipe configuration. |
|
246 |
Phase Received Exit Ack |
Phase |
|
|
241 |
Phase Wait for Req Edits |
Phase |
If a phase parameter is marked as “Edit Required”, the phase will not start until the parameter value has been set by the operator. |
|
242 |
Phase Received Req Edits |
Phase |
|
|
243 |
Phase Wait for Req Cmmt |
Phase |
If a phase parameter is marked as “Comment Required”, the phase will not start until a comment has been entered by the operator. |
|
244 |
Phase Received Req Cmmt |
Phase |
|
|
250 |
Phase Wait for Entry Doc View |
Phase |
Phase is set with the Document settings, which require the operator to view an external document and also require acknowledgement on Phase entry. |
|
251 |
Phase Received Entry Doc ViewAck |
Phase |
|
|
252 |
Phase Wait for Entry Doc Ack |
Phase |
|
|
253 |
Phase Received Entry Doc Ack |
Phase |
|
|
254 |
Phase Wait for Exit Doc View |
Phase |
Phase is set with the Document settings, which require the operator to view an external document and also require acknowledgement on Phase exit. |
|
255 |
Phase Received Exit Doc View |
Phase |
|
|
256 |
Phase Wait for Exit Doc Ack |
Phase |
|
|
257 |
Phase Received Exit Doc Ack |
Phase |
|
|
225 |
Phase Received Interlock |
Phase |
Received is when the Batch Manager gets a status update (e.g. sees Run bit go true) |
|
226 |
Phase Received Ready |
Phase |
|
|
228 |
Phase Received Run |
Phase |
|
|
230 |
Phase Received Held |
Phase |
|
|
233 |
Phase Received Aborted |
Phase |
|
|
234 |
Phase Received Done |
Phase |
|
|
227 |
Phase Set Start |
Phase |
Set is when the Batch Manager sends a command (e.g. sets Start bit) |
|
229 |
Phase Set Hold |
Phase |
|
|
231 |
Phase Set Restart |
Phase |
|
|
232 |
Phase Set Abort |
Phase |
|
|
235 |
Phase Set Reset |
Phase |
|
|
236 |
Received Bad Ready |
Phase |
If the Batch Manager gets an unexpected or invalid phase status transition. For example: a phase going from Run to Ready. |
|
237 |
Received Bad Run |
Phase |
|
|
238 |
Phase Received Bad Held |
Phase |
|
|
239 |
Phase Received Bad Done Aborted |
Phase |
|
|
240 |
Phase Received Bad Interlock |
Phase |
|
|
247 |
Phase Wait for Start |
Phase |
When the Batch Manager sends a Start command to a phase, it goes into the Wait for Start status until the phase goes to Run. |
|
248 |
Phase Received Start |
Phase |
Received Start will be seen when a phase is started in the Manual mode. |
|
249 |
Phase Resync |
Phase |
Resync will be seen when the Batch Manager first starts up and the last status of the phase stored in the Batch Manager is different from its current status in the control system. |
|
265 |
Phase set Control Button1 |
Phase |
Phase control button activated by the user. |
|
266 |
Phase set Control Button2 |
Phase |
|
|
414 |
Phase Skip |
Phase |
Skip is triggered after “Phase Skip” for any phase that is in “Waiting for Entry Acknowledge” (For example: in the Semi-Automatic mode). |
|
415 |
Phase Done |
Phase |
Done is triggered after Phase Abort when a phase is Waiting for Exit Acknowledgement or when a manual phase is complete. |
|
275 |
Force Transition True |
Transition |
Transition forced to complete by the user. |
|
276 |
Transition Start |
Transition |
Transition starts |
|
277 |
Transition Stop |
Transition |
Transition is done/completed and the phase execution moves ahead. |
|
278 |
Transition True |
Transition |
Transition evaluates true |
|
279 |
Transition False |
Transition |
Transition goes to false state. For example: In the ‘execute one’ branch, when one leg sets to true, other leg fails and the transition on that leg is set to false. |
|
300 |
Yes |
Transition |
Response to a batch question. When a user answers a batch question with Yes or No, these codes are logged into the BatchQuestion table. |
|
301 |
No |
Transition |
|
|
305 |
Approved for Production |
Batch |
Recipe is set to approved for production in the Recipe Editor. During execution, these codes are logged into the Recipe_Approval_CD column of the BatchIdLog table. |
|
306 |
Approved for Test |
Batch |
Recipe is set to approved for test in the Recipe Editor. During execution, these codes are logged into the Recipe_Approval_CD column of the BatchIdLog table. |