ION Factory OS
  • Welcome to ION
  • Features
    • Procedures
      • Steps
        • Content
        • Datagrid
        • Fields
        • Attributes
      • Dependencies
      • Part-Procedure Relationship
      • Attributes
      • Standard Steps
      • Installation Requirements (Beta)
      • Nested Steps and Nested Standard Steps
      • Procedure Best Practices
    • Runs
      • Run Execution Overview
      • Runs And Step States
      • Batching Runs
        • Batching 2.0 Changes
      • Workcenter execution
      • Split Inventory on a Run
      • Redlines
      • Export run data
      • Scheduling runs
      • Time Tracking
      • Attributes
      • Outside Processing
      • Runs Best Practices
    • Parts Library
      • As-built Bill of Materials (aBOM)
        • Editing aBOM build requirements
        • aBOM Beta Changes
          • aBOM actions for developers
      • Inventory
        • Inventory status
        • Inventory splitting
        • Inventory merging
        • Inventory scrapping
        • Kitting
        • Inventory Movement Automations
      • Manufacturing bill of materials (mBOM)
        • mBOM versions
        • Made on Assembly (MOA)
        • Part Substitutes
        • Reference designators
      • Part Attributes
      • Part revision interchangeability
      • Supplier Part Numbers & Purchase Unit Conversions
    • Kitting and Inventory Fulfilment
      • Kit Statuses and Workflows
      • Inventory requests
      • Kitting and runs
      • Fulfilling Multiple Kits
      • Kanban Kitting
    • Purchasing
      • Purchase Orders
        • Types of Purchases
        • Purchase Order Approvals
        • Purchase Order FAQs
        • Supplier Part Numbers & Unit Conversions
        • PO Requirements, Terms, and Quality Clauses
      • Receiving/Inspection
      • Outside Processing
      • Consigned Parts
    • Barcode Labels
      • Templating
        • ION barcode minimum sizes
        • Sample templates
      • Printing
        • Configuring Zebra Browser Print
        • Server Based Barcode Printing (PrintNode)
      • Scanning
        • Scan barcodes from other systems
    • Quality
      • Issues
      • Further Actions - CAPA
      • Issues States, Dispositions, and Resolutions
      • Quality Best Practices
    • Tools
    • Locations
    • Attributes
    • Labels
      • Deleting labels
    • Notifications
    • Search
    • Settings
      • Role based access control
        • Full Glossary of ION Permissions
    • ION Actions
      • ION Actions examples for Quality
      • ION Actions examples for Runs and Procedures
      • ION ACTIONS examples for Supply Chain
  • Analytics
    • Inventory valuation
    • Part impact analysis
    • Users, Roles, Teams
    • Analytics FAQ
    • Data Connector
    • Data Products
  • Plans and Autoplan
    • Autoplan
    • Autoplan glossary
    • Preparing to use Autoplan
    • Clear to build reporting
    • Running Autoplan on a schedule
    • Firm and blocked plan items
    • Location constraints
    • Autoplan suggested suppliers and procedures
    • Reorder point
    • Plan input serial numbers
    • Applying a calendar
    • Plan Reservations
    • Independent schedules
    • Drive demand from kits
    • Drive demand below buy parts configuration
    • Group plan items with the same date
    • Manualy Changing Autoplan Status
  • API
    • How to create an App with ION
    • Access Tokens
    • About GraphQL
    • Interactive API explorer
    • API Keys
    • Examples
      • Notifications
      • Runs
      • Automatically updating fields in runs
      • Parts and Part Revisioning
      • mBOMs
      • Part Inventory and Kitting
      • aBOM (As-built Bill of Materials)
      • Edit time-tracking session data
    • Changelog
    • Webhooks
    • Pagination
  • Automations
    • Auto-checkout of Run Steps
    • Auto-Consumption of Lineside Inventory
    • Automatically Send Purchases to Suppliers
    • Set Close by Run Step on Issue Creation
    • Intent Management / Grade / Tier / Pedigree
      • Data Imprinting
      • ION Actions for Intent
    • Auto-Update mBOM Revision on Part Revision Update
    • Auto-approve part-procedure relationships
    • Purchase Order PDF and Versions
    • Auto Populate PO Line Attributes
    • Imprint Attributes from One Object to Another on a Desired Event
  • Integrations
    • Deploying Integrations and Automations
    • Arena
    • Cofactr
    • Datum
    • Duro
    • NetSuite
      • Purchasing in NetSuite, Receiving in ION
      • Work Order/Assembly Builds
    • Procurable
    • PDF Generator
    • Quickbooks
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
  • Training
    • Standard Operating Procedures
      • Cycle Counting
      • Tool Utilization
    • Guided Flows
    • ION Sandbox
    • Chat Support for ION
  • Troubleshooting
    • Resetting your password
    • Resetting your Multi-Factor Authentication
    • You have no roles... error
  • Changelog
  • Adminstration
    • Security
      • Backups and Security FAQ
      • Single Sign-On (SSO)
        • Okta SAML connection setup
      • Export Control
      • Report Generator Disclaimer
    • Browser and Device Compatibility
    • Authentication
      • My company is new to ION, logging in for the first time.
      • I'm told I'm not authorized to access the application
      • My account has been deactivated
    • Login Page
  • Tickets Portal
Powered by GitBook
On this page
  • Run batches
  • Creating a batch
  • Viewing a Batch
  • Batch Propagation
  • Adding and removing individual runs

Was this helpful?

  1. Features
  2. Runs

Batching Runs

How behavior changes and what to expect when runs are part of a batch

PreviousRuns And Step StatesNextBatching 2.0 Changes

Last updated 11 months ago

Was this helpful?

Run batches

When working with many parts at once it can get repetitive to manually input information for runs that go through the same operation. The Batch function groups into batches where updates to the runs are synchronized to save time.

Any set of run can batched together, regardless of what steps they contain

Run batches work by propagating changes made to one run to the others it is batched with. It doesn't matter which run you make changes to. The run's assigned user, due date and step progress will be synchronized.

ION will intelligently pick steps to synchronize based on step data - see the full list of rules below in Batch Propagation. This allows runs to be batched together even if they go through different processes in the past or future.

Creating a batch

Runs can be added to batches during creation using the "batch runs" checkbox, any time after creation using the Batch column in the runs table view, or in a run and selecting the batch button as seen below.

A run can only be in one batch at a time, but you can remove a run from a batch and add it to another at any time.

  • During the Run Creation Process

  • From the Runs Table view

  • Within the Run itself from the run header

Viewing a Batch

Runs in a batch display a batch information banner at the top of the run header which can be clicked on to see information at a glance and then expanded to have more control over the batch.

When looking at the batch overview, clicking a different run will navigate you to that run.

Batch Propagation

Batch Siblings

ION automatically picks steps in the batch to synchronize based on data in the step. ION looks for the similarity based on the following criteria:

  • The step title is the same

  • If the step has Fields, the fields must be identical, including order and validations

  • If the step has a Datagrid, the datagrid columns and rows must be identical

  • If the step has any child steps, they must be identical

  • The step must be in a state where it can be worked. Steps already completed, blocked by dependencies, or in administrative states like redline or canceled before batching will not update

  • If a run contains multiple steps that match these criteria, ION will match like with like in order of position. For example, if there are four identical steps at position 1-2 in run A and position 7-8 in run B, ION will synchronize step 1 with 7 and step 2 with 8

The step content does not have to match for ION to synchronize steps. Differences in content are allowed.

Data propagation

When a runstep is synchronized in a batch, changes to the following step data will be made to all synchronized steps:

  • Status

  • Scheduled start

  • Scheduled end

  • Assigned user

  • Lead time

  • Workcenter

  • Field entries

  • Datagrid entries

  • Check-in data

  • Comments

  • File Attachments

Redline propagation

Redline changes are also propagated across all synchronized steps. Along with matching the above criteria, synchronized steps must be from the same procedure to have redline changes propagate between them.

Adding and removing individual runs

If the data/process of a particular run have a need to diverge from other runs in the batch, the run can be removed from the batch and modified independently. Similarly, other runs can be added after batch creation too.

Click on the batch label and use the batch edit sidebar to add and remove individual runs.

Example of batching three runs with different steps
Batching runs during run creation
Run batch status in runs table
Hit the Create batch button to pull up the below model
Add this run to an existing batch or to a new batch!
Run execution highlights runs affected and total runs in batch
Batch information at a glance from clicking on the batch
Detailed batch view by clicking on the blue arrow next to the batch details