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
  • Maintenance Interval
  • Tool Status
  • Tool Barcodes
  • Tracking tool usage
  • Tools on Runs
  • Tools on Issues
  • Tools on Kits

Was this helpful?

  1. Features

Tools

PreviousQuality Best PracticesNextLocations

Last updated 1 month ago

Was this helpful?

ION Tools can record assets and calibrated equipment in your factory. Tools are laid out in a very similar way to with a few changes.

  • Tools are always serialized - there are no lot-tracked tools

  • Tool models can optionally have a maintenance interval and individual tools can have a last maintained date

  • Tools can be assigned a type used to group tools beyond part number. For example, all torque wrenches of different model numbers can be combined under a single "Torque Wrench" type. This is useful if you want to call out use of a tool in a Run but don't need a specific part number.

Maintenance Interval

The maintenance interval is set in the part in tool library and applies to all tool inventory using that part. The interval is entered with as a list of format {number}{unit} using the following unit shorthand:

Shorthand
Unit

s

Second

m

Minute

h

Hour

d

Day

w

Week

month

Month

y

Year

For example, entering an interval of "1d20m" means an inverval of 1 day and 20 minutes, or 1480 minutes

Tool Status

Tools have two statuses, Available and Unavailable.

The status of a tool can be determined by a couple of factors but also comes with a way to override the built in calculations:

  1. If the tool has a maintenance interval and a last maintenance date, their maintenance status is calculated as Available depending if the next maintenance date is in the future. If the next maintenance date is in the past, the tool is Unavailable.

  2. Tools located at an unavailable location they are marked unavailable.

  3. Either of these calculations can be manually overridden by toggling the Available / Unavailable indicator within the tool inventory panel. This provides flexibility to adjust tool availability based on factors of your choosing, such as integration with a tool management system.

Note: If you are interested in enabling this functionality please reach out to your Customer Success Manager.

Tool Barcodes

Tracking tool usage

Tool usage can be tracked by using a Tool Field on a step in a run. When a technician is working on the run they will fill out the tool field and create an auditable log of the tool's usage.

When creating the data collection field, you can set the field name and help text as usual. Selecting the Available checkbox limits valid tool input to tools with the available status.

Use the Validations menu to constrain what kind of tools are valid input. Acceptable validations are Type for multiple models of tools or Part Number for a specific model.

When executing a run, select the tool you are using from the list to complete the field.

Tools on Runs

Tools on Issues

Tools on Kits

Printing barcodes and using tool works just like Part Inventory. Tools also share with Inventory.

Tools can be associated with to inspect or maintain them. Associate a tool with a run just like you would a part during run creation.

can be opened on tools just like part inventory. Tools will appear in the part inventory dropdown when creating or modifying an issue.

Tools can be used in to move tools between different , or to request tools in a specific area or to a specific user. Requesting or moving a tool works the same as requesting or moving inventory.

barcodes
barcode templates
Runs
Issues
Kits
Locations
Parts
The Tool Library interface used to add tools
Tool inventory showing tool serial number barcode, service status and location
Adding a tool field to a step
Adjusting tool field validations
Successful record of tool usage
Creating a run to maintain a tool