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

Was this helpful?

  1. Features
  2. Runs

Run Execution Overview

This page outlines all of the changes in IONs new run execution view, rolled out 4/24/24.

PreviousRunsNextRuns And Step States

Last updated 9 months ago

Was this helpful?

For a walkthrough of the new streamlined features in run execution, check out this walkthrough:

Our plan will be to entirely replace our legacy view of ION with the new and improved Runs 2.0. The emphasis of this new version is to deliver performance and intuitive workflows for technicians, who have the highest touch point and throughput needs in ION. 2.0 will ensure that the software works for your production teams, and does not slow them down. Below is a list of improvements we have made and will continue to improve upon.

  • Performance: Throughout the new execition, performance is embedded in every transaction. Try loading a large content step, or quickly updating a series of values in a datagrid and comparing that to the legacy view. You will see in many places up to 10x performance increases.

  • Scrollable Run Header:

  • File Viewer: View PDFs and image file types right in the application without having to download by clicking on the image's thumbnail to pull up the file viewer. You can flip through different images and pages in a PDF.

  • Finger-Friendly Sizing: Our goal is for technicians who are using iPads or other touchscreen devices to be able to quickly and confidently interact with ION without being worried about clicking the wrong button or worse, inputting the wrong value into ION. We made buttons and interactions on Runs 2.0 much larger to assist.

  • Action Bar: The action bar now reacts to the state of the step at any given time. For example, if the step is in TODO, you will see a Start button which will bring the step in progress and check you in automatically. We utilized this opportunity to eliminate the confusion of beginning a step and checking in. There is always an overflow menu that allows you to perform less frequent actions.

  • Check In Status Bar: Now at all times if you are checked into any run step from the color of the top bar in ION. If it's green, you have an estimated labor time remaining on that run step. If's orange, you are out of estimated labor time on that run step. In addition, there is a new pop up that shows you all steps you have checked into for easy check out and navigation purposes.

  • Run Execution and Run Summary are combined: Frustrated with having to navigate to the run summary to change the location or assignee of a run step, view kits, see redline history and merge, etc.? This is now all accessible directly at the top of the run execution screen. It is hidden by default, but can be accessible by clicking the expand button!

  • Digital Run Step QR Code: You can use the digital QR code on every run step to quickly send the URL to multiple team members or have a team of technicians quickly scan the barcode to check in on their mobile device to ensure accurate labor hours or an inspector can scan the barcode to signoff on a quality inspection on their mobile device instead of carrying around a laptop or tablet. You will need to login on your phone just as you would on any device.

  1. Redlines

  2. aBOM Beta Changes

  3. Batching Runs

Expanded Issue Creation: The issue creation pop-up now allows you to assign users and add information for all of the attributes your organization has configured for issues. Combined with , you can now ensure that information is captured on every issue.

ION actions
File Attachments
File Previewer in Application
Start and Check In are Combined when Step is in TODO
The Top Bar is Orange Because you are past the expected labor time
Check Out Pop Up
Issue Creation in Beta
Attributes can be Populated on Issue Creation
Digital Run Step QR Code
Mobile Check in via Web Browser
Quickly Sign off on Fields on Run Steps