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
  • Introduction
  • Part Interchangeability
  • Setup
  • Getting Started
  • Setup
  • Configuring the Automation

Was this helpful?

  1. Automations

Auto-Consumption of Lineside Inventory

Consume non-serial-tracked inventory from inventory location.

Introduction

This automation will speed up your production processes by reducing the manual input of data into your assemblies' as-built records. When you complete either the first or last step of a run, the automation will search for available locations and consume inventory based on the mBOM for that run. Serial-tracked items will not be consumed. This automation will consume older revisions of the same part.

Part Interchangeability

This automation will consume older revisions of the same part if they are available. For example, let say you have 3 revisions of the same part with inventory at the location:

  • Rev A - Quantity of 10 on hand at the location

  • Rev B - Quantity of 30 on hand at the location

  • Rev C - Quantity of 5 on hand at the location

If the mBOM requires a quantity of 40 of that part then auto consumption will consume:

  • 5 of Rev C

  • 30 of Rev B

  • 5 of Rev A

Setup

This manual guides users through setting up an auto consumption system to automatically consume lineside inventory upon completion of a designated run step.

Getting Started

Key Concepts

  • aBOM (As-Built Record): A digital record of components used in production.

  • Auto Consumption: Automated consumption of inventory items from predefined locations.

Setup

To ensure the automation runs correctly you need to set up a location hierarchy and locations on the procedures you want to run Auto Consumption for.

Location Hierarchy:

Below is an example of the location hierarchy you will need to set up in order for the automation to run.

  • Workstation: This is where the run steps are being completed. Can have inventory stored on itself or have child racks/totes under it.

  • Child: The parent location is a workstation. Tote or rack.

  • Parent: This is a work cell or work area. Can contain workstations and one lineside rack. Workstations under this parent will pull from the one rack.

  • Sibling: Lineside rack location. Workstations have access to this location (MOST COMMON METHOD OF CONSUMPTION)

  • In the above example, the work is being done at the location called "Workstation." Because both "Lineside Rack 1" & "Lineside Rack 2" are siblings of "Workstation," both are candidates for autoconsumption.

Procedure Configuration:

To get the automation to run correctly you will need to specify a location on the procedure step. This will be the workstation location. To do so, use the drop-down in the procedure editor as shown here:

  • We recommend that you set up a location on every step but at this time only the first or last steps need to have a location specified for the automation to run correctly

Configuring the Automation

Step 1: Configure ion-api Connection

  • input your API keys into the following boxes and select your environment

Step 2: Setup Consumption Methodology

  • Consumption Method:

    • First: first step of run (recommended)

    • Last: last step of run

  • Consumption Location (see diagram above for more information):

    • workstation: consume directly from inventory at the workstation where the run step is being worked on

    • child: consume from child rack or tote of the workstation (limit 1 per workstation)

    • sibling: consume from the rack that is a sibling of the workstation (has the same parent as the workstation limit 1 per parent). Example: lineside rack

Coming Soon:

  1. Consumption of substitute parts

PreviousAuto-checkout of Run StepsNextAutomatically Send Purchases to Suppliers

Last updated 1 month ago

Was this helpful?

Navigate to our and search for Auto-Consumption. Press configure

refer to the documentation for information on how to get your API keys

integrations page
API key
Location Hierarchy Diagram
Example Location Hierarchy in ION