Appearance
Batching task executions
Table of Contents
A batch groups multiple work order tasks into one execution view. Operators can enter shared data and fulfill compatible part requirements across the group while Factorial retains the execution record for each individual task.
Tasks in a batch do not need to belong to the same work order or procedure. This makes batching useful for both repeated production and work organized around shared equipment.
When to use a batch
Repeated serialized production
Use a batch when several serialized units follow the same procedure. An operator assembling 80 identical units might execute a corresponding task for all 80 units together or process them in smaller groups.
Shared equipment
A batch can also combine compatible tasks that use the same equipment. For example, an oven operator can select tasks from an oven queue and group as many compatible items as the next run can hold. Those tasks may come from different work orders or procedures.
Bottom line: if you need to input the outcome of many part requirements and/or values for data inputs, use a batch.
Creating a batch
From a task list
A batch can be created from any view that lists work order tasks. Select the tasks, then use the bulk action to create a batch.
Factorial assigns the batch an ID and displays a batch indicator on every included task. Select the indicator to open the batch.
While creating work orders
When creating work orders for multiple serialized units, select the units that should be batched. Factorial automatically groups matching tasks across those work orders into batches.
This is useful when the same operators will execute corresponding tasks for several units at once.
Finding a batch
The Batches page lists all batches and supports search. A batch can also be favorited to keep it available in the sidebar.
A batched task displays a banner linking to its batch. Use the batch view for shared execution. Open the individual task when a one-off action or its complete instructions require separate attention.
Executing a batch
The batch view presents tasks as columns. Tasks created from the same procedure step appear together in a subgroup. Each subgroup links to the individual task pages, where operators can review the complete work instructions and execution context.
Rows represent data inputs and part requirements. Expand a row to see or action the values for every task in the batch.
Navigation above the table links to other relevant batched tasks and to the next available task in the queue, similar to the right rail on an individual task page.
Entering shared data
The shared input at the left of a data row applies one value across the tasks in that row. Use it when the same result applies to the entire batch, such as an oven temperature recorded for one equipment run.
To record a different value for one task, enter or paste the value directly into that task's cell. The cell-specific value overrides the shared value. Factorial distinguishes overrides through the cell styling and an override indicator.
Tasks do not need to originate from the same procedure step to share a data row. Factorial aligns inputs that use the same reusable data-field definition, even when the tasks belong to different procedures.
Batch entry does not change task validation. Each task must still contain values for its required fields before it can be marked as completed.
Fulfilling part requirements
Factorial aligns compatible part requirements in one row based on the required part and its accepted substitutes. Each cell displays the quantity required for its task.
Quantities may differ across the row. Different procedure definitions may require different quantities, and a work order producing multiple output units may require more installations than a work order producing one.
When the requirements align and one inventory lot contains enough quantity, scan the lot from the shared control to action it across the row. Otherwise, action the part requirement in each task's cell. Per-cell actions also support tasks that require different inventory or require an inventory line to be split.
Part requirements with reference designators must be actioned one cell at a time. Open the installation dialog for each task and assign the inventory to its specific reference designator. This preserves the exact relationship between an inventory item and its installed position.
Moving tasks between batches
A task can be removed from a batch without affecting the other tasks. To split a batch, select one or more task columns and use the bulk action to move them into a new batch.
Splitting a batch is useful when part of the group needs different execution data, material, equipment, or timing.