Home > Process Modeling and Simulation Concepts > Input Collections > Batch Inputs

Batch Inputs

A batch is a temporary collection of transactions into a set, like holding them in a basket. You can unbatch the collection, or empty the basket, at any step after the batch has occurred. If you have not explicitly unbatched the collection, when the batch transaction– the basket that represents the set of transactions collected–reaches the end of a process or subprocess, iGrafx forces the batch collection to be unbatched and empties the basket and restores the transactions to their individual identities instead of being in a batch. If you want the transactions to be batched at the end of a subprocess, you must re-batch them in the parent process.

Batch collections queue incoming transactions before processing them as a single transaction. Batching allows all transactions to maintain their identity whereas joining eliminates individual transactions. Batched transactions can be unbatched later and processed individually. Batching models many real world situations, such as loading automobiles on a rail car or trailer for shipment.

Batched transactions can also be further batched. In this case, each individual transaction still maintains its identity. Using the example above, the rail cars containing automobiles can be collected into a train. For more information on input collections, see Properties dialog box - Inputs page.

Related Topics

See Also