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. Training
  2. Standard Operating Procedures

Tool Utilization

Set up tools in ION and track where they are being used

PreviousCycle CountingNextGuided Flows

Last updated 3 months ago

Was this helpful?

Effective tool utilization is a key element to guarantee process integrity and product quality through manufacturing cycles.

Understanding which tool was utilized to complete a specific operation is essential in a regulated industry.

More important, guaranteeing the processes in place are enforced and the utilization of a compliant tool and assembly hardware is hard requirement for an operation guarantees success.

ION Tool Requirements Features include the following:

  • Ability to set optional or required tools at a step level

  • Ability to set tool validations at tool selection level, such as specifying the exact tool that must be used for an operation

See Diagram 1 below:

How to Implement Tool Requirements in ION:

Step 1: Complete Tool/Operation Analysis

  • List all operations in your manufacturing process.

  • Identify and list all tools required to perform your manufacturing operations

  • Map each operation with their corresponding tool requirement(s)

Step 2: Complete Tool Maintenance Analysis

  • Identify and list the maintenance cycle and criteria for each tool necessary for your manufacturing processes.

Step 3: Incorporate all Tool requirements and validations identified during the Tool/Operation analysis into the necessary ION procedures.

  • Create a Field Type: Tool at each step/operation necessary. See Image 1 below:

  • Set the proper validations and requirements for the tool field. This is the stage where you tell ION if a tool MUST be used for an operation, if so, which tool(s) can be used.

By completing the above tasks, your organization will:

  • Identify any gaps between your tool inventory and operation requirements

  • Enforce the utilization of a tool at an operation level

Visualize Tools

To build on top of the in process requirements for tools. Organizations can pull this information into reports to manage tools better. Here are some dashboard ideas we have seen work for customers:

Tracking Tool Inventory Attributes

  • Tool

  • Serial Number

  • Location

  • Service Due Date

  • Last Service Date

  • Service Interval

  • URI - Universal Resource Identifier

  • Status - Available/Unavailable

Tool Management Reports

  • Automate the delivery of tool inventory reports based on specific parameters, such as cadence or specific conditions. For example:

    • Get a weekly report on all your tools automatically sent to the tool manager in your organization.

    • Never miss a calibration or maintenance date for your tool inventory by get a report of tools 2 weeks prior to their service due date.

    • Get a report of the tool inventory that is currently unavailable and requires maintenance and/or re-calibration.

    • Get a report of tools that have been 'Unavailable' for a certain period of time.

Diagram 1
Image 1