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
  • Why the Changes?
  • What are the Changes?
  • 🧩 1. Batch Matching Logic: From Visual Similarity to Structural Identity
  • 🔄 2. Batching Impacts Nested Steps and Enforces Parent-Child Hierarchy Matching
  • 📤 3. Expanded Scope of Data Shared Across Batches
  • 🚧 4. Stricter Rules on Step Status and Batching
  • 🔗 5. Stronger Enforcement of Dependency Logic in Batches
  • 6. Performance Improvements
  • Converting Old Batches

Was this helpful?

  1. Features
  2. Runs
  3. Batching Runs

Batching 2.0 Changes

Why the Changes?

  • Instant Batch Creation

    • Old: Async job took minutes, required manual refresh—and early steps didn’t batch.

    • New: Fully synchronous, completes in ~1 second for any batch size.

  • Scalable Step Operations

    • Run‑step check‑in: 100‑run batch goes from ~20 sec → 1 sec.

    • Redlining: Once timed out on large DAGs → now ~2 sec (same as single runs).

  • Batch‑Size‑Independent Performance

    • Old: Every write slowed linearly—10 runs = 10× slower.

    • New: Core operations execute in constant time, whether you batch 5 or 500.

Bottom Line

  • No more “wait & refresh”—you get instant feedback.

  • Predictable, fast performance at any scale.

  • Full DAG support unlocks complex workflows without timeouts.

What are the Changes?

🧩 1. Batch Matching Logic: From Visual Similarity to Structural Identity

Before:

Batchable steps were determined primarily by surface-level similarity:

  • Matching titles, fields, datagrid structures, and child steps.

Now:

Batchable steps are determined by system-defined identities:

  • Last redline is the same

  • Standard Step ID is identical (for standard steps)

  • Or, the origin step ID is the same (for procedure steps)

  • Step must be in TODO status

What this means:

Your customers now rely less on surface-level matching, minimizing surprises and reducing hidden mismatches in critical workflows.


🔄 2. Batching Impacts Nested Steps and Enforces Parent-Child Hierarchy Matching

Before:

  • Child steps needed to be identical, but no explicit callout was made about the full parent-child hierarchy.

Now:

  • The entire step hierarchy—including nested steps—must match for batching to occur.

  • Nested steps to a depth of more than 1 will now also batch.

Impact:

This prevents partially batched workflows due to hidden structural differences and reinforces step-by-step alignment across runs.


📤 3. Expanded Scope of Data Shared Across Batches

Before:

Data shared included core operational fields like status, scheduled times, field entries, datagrid entries, attachments, etc.

Now:

New and more consistent batch-shared data:

  • Redlines to existing steps

  • Adding new steps

  • Dependencies

  • Check-in session data

Takeaway:

The system now treats batches more like a living procedural container—including structural changes (like added steps or redlines), not just step updates. This means changes ripple through the batch more comprehensively.


🚧 4. Stricter Rules on Step Status and Batching

New behavior:

  • You cannot un-batch a run if any of its steps are in a REDLINE status.

  • Only steps in TODO status are eligible for batching.

  • To reapply changes to completed steps via batching, users must reset to TODO, batch, then reapply changes.

Why this matters:

This protects data integrity by ensuring batches reflect only modifiable, aligned steps—and keeps post-execution changes deliberate and controlled.


🔗 5. Stronger Enforcement of Dependency Logic in Batches

Before:

Dependency rules were implicit.

Now:

Clear rule: A downstream step in any run can only begin when the equivalent upstream steps in ALL batched runs are complete.

Consequence:

As you may change one run that had an issue to ensure it got repaired before rejoining a batch, this ensures those repairs are completed in advance of that part rejoining the batch, as an example.


Now:

  • Batches are much, much faster. You can now reliably batch 100 runs and see the same performance when executing the runs as you would when executing just one run. No more waiting long periods of time to see changes occur in a batch and seeing issues of data not being shared when you expect it to be shared.


Converting Old Batches

All batches created after Wednesday, May 14th, 2025 are already using the new architecture. However, if you want to convert batches created before that date, please do the following:

  • Find the batch and ensure all steps you want to batch are in the TODO status.

  • Unbatch all runs from the old batch.

  • Create a brand new batch and add the runs to the batch.

You should now see those runs are on the new batching architecture as described above!

PreviousBatching RunsNextWorkcenter execution

Last updated 3 days ago

Was this helpful?

6. Performance Improvements

🚤