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 Step Status
  • Available to Work
  • Run Status
  • Todo
  • In Progress
  • Completed
  • Hold
  • Redline
  • Failed
  • Canceled

Was this helpful?

  1. Features
  2. Runs

Runs And Step States

States step

PreviousRun Execution OverviewNextBatching Runs

Last updated 9 months ago

Was this helpful?

Run Step Status

Steps on runs are like a checklist indicating what work was done and how. Each step in a run has a unique state. That state indicates the status of the work called out in the step's work instructions. Below are all of the states of a Run Step and the different states they can transition to.

Available to Work

Available to Work is a separately calculated attribute that ION uses to help indicate to users whether or not a run step can be worked on. It's calculated by taking into account the following:

  • Are all upstream dependent run steps Completed?

  • If a parent step exists, then is it In Progress?

  • Is the current step in Todo or In Progress?

  • Future State: Are all blocking issues resolved?

If all of the conditions are met then the step is considered Available to Work.

Run Status

The run calculates its status based on the status of its steps. This gives teams a high level overview of the state of the run! Below are the states of a run.

Todo

This is the initial status for steps when they are created. A step in Todo means no work has been done against that step.

A run with steps all in Todo will also show the state as Todo

In Progress

A step In Progress has been started by a user. Steps can only be moved from Todo to In Progress if all their upstream dependencies have been moved to the Complete state. Transitioning a step from In Progress to any of the other states as seen below will automatically check out all users who are currently checked into that run step.

Completed

A Completed step has had all its required fields filled out and all its work completed.

Runs with all steps Completed will also be Complete

Hold

Hold is a special administrative state used to prevent steps from being executed. This could be used to block work from being done or to pause an operation while an issue is being investigated.

A run with at least one step in Hold status will also inherit the Hold status.

Steps in Hold state are called out in yellow.

Redline

A run with at least one step in Redline status will also inherit the Redline status, and the Redline status takes precedence over the Hold status.

Steps in Redline state are called out in light red.

Failed

Failed steps indicate something went wrong. This could be a part or process was found to be non-conforming or an inspection was failed. You can trigger this step by clicking the Fail Step button in execution mode after this step has been started.

A run with at least one step in Failed status will also inherit the Failed status.

Failed steps are colored dark red.

If set up in your organization settings, a Failed step will automatically trigger the creation of an issue ticket. From here, you can insert your cause, expected condition, and disposition.

You are able to freely change a runstep from Failed status to Todo or Redline.

Canceled

If a user with appropriate privileges decides that a step can be skipped, they can cancel the step. Canceled steps can be moved back to Todo to be un-canceled.

If every step in a run is canceled, it will calculate its status as Canceled. If the run is comprised of a mix of Complete and Canceled steps, it will use the status Partial Complete to indicate no more work can be performed but not all the work was done. Otherwise, the run will use the other rules from the above states to calculate its status.

Canceled steps are displayed in dark gray

Redline steps are in an editable state and cannot be executed. See the page for more information.

Redlines
Run Step States
The ION UI will block you from starting a step until its upstream dependencies are complete.