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
  • What is a procedure?
  • Creating a procedure
  • Updating a procedure
  • Steps
  • Versions and Archiving
  • Reviews

Was this helpful?

  1. Features

Procedures

Instructions for work to be done

PreviousFeaturesNextSteps

Last updated 6 months ago

Was this helpful?

What is a procedure?

Procedures are ways to record work instructions, data collection, and workflow in ION. Procedures are made up of steps and their child steps that define what work is to be done and what data is to be collected. The execution of work is not done from this part of ION - it is done in a .

Users must have the permissions CreateProcedure and UpdateProcedure create and release a procedure.

Creating a procedure

To create a procedure, go to the Procedures section in ION. You will see a list of procedures created at your company. Click New procedure to create a new procedure.

Enter the title and description of your new procedure. Don't worry, you can change these while your procedure is still in draft.

Updating a procedure

Only procedures that are in draft can be updated. Once a procedure has been released, that version can no longer be modified. To modify a procedure, go to the Procedures section and select a procedure to modify. Now, you can modify the procedure's steps, attachments, and data collection fields.

Steps

Procedures can have multiple steps. Each step has its own content, attachments, and fields. During a run, each step will be presented in the Technicians view in sequence.

Versions and Archiving

Procedures are version-controlled, and runs use specific versions of procedures, so that the exact procedure that was used in production is always traceable. There can only be one version of a procedure in draft for a given procedure. From a released or archived procedure, you can "Create new draft", which will create the next incremental procedure version in draft.

You can archive a procedure using the status icon in the top right. Archiving is useful for making sure a procedure does not get utilized in all runs going forward. We recommend this only when you are sure a procedure will never be needed again. When a procedure is archived, it will be removed from the procedure screen and from the run creation screen as an option. Archived procedures can be viewed by clicking show all versions from the procedures home page.

All versions that stem from a procedure will be part of the same Procedure Family.

Reviews

When you are done updating a new version of a procedure, you can submit it for review. In the procedure action selector, select "For review". From there, you can add the reviewers who should review the procedure.

Reviewers will see the pending review requests in their home dashboard. Clicking into the review request will take the reviewer to the procedure to leave a review. Once all reviewers have approved the procedure, it will be automatically set to "released" so that it can be used in production runs.

Select a procedure type. Build, Maintenance, Test, and Inspection Procedures have the same functionality, with one exception -- an inspection procedure can be used in an inspection run, which would be automatically created at the time of receipt of Purchase Order.

while using the workflow here
Run
Procedure edit view