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
  • Pain Points and Use Case
  • Step Assignments
  • Substitutes
  • Reference Designators
  • Installing Inventory on Run Step Installation Requirements
  • Permissions
  • Modifying your mBOM
  • Best Practices
  • Coming Soon

Was this helpful?

  1. Features
  2. Procedures

Installation Requirements (Beta)

Assign and enforce parts to be installed from your mBOM to a particular step in a procedure

PreviousStandard StepsNextNested Steps and Nested Standard Steps

Last updated 23 days ago

Was this helpful?

Before implementing installation requirements, please review the Best Practices below!

Pain Points and Use Case

Have you ever been close to the end of an assembly or worse, needed to investigate a part that has been installed only to realize that the digital aBOM doesn't reflect the state of the physical build? Do you spend valuable time at the end of your build cycle or in deep investigations to rectify these differences? Now you can assign required installations at each step in a given procedure. This will prevent the run step from closing until all of the required installations are complete, similar to required fields. When a run is closed, you will have the utmost confidence that the aBOM digitally represents your physical assembly. Not only does this mean that you can trust run execution will occur correctly, but you can also build your procedure faster by understanding at a glance which components you have digitally assembled and what remains. Take an example where you have hundreds of fasteners to install. With this feature, you can ensure that from the procedure, all of the fasteners are assigned to a step before releasing the procedure.

Step Assignments

The part assignment view is split into two distinct sections. The top section represents installation requirements assigned to the step that is currently selected via the procedure step queue. The bottom section represents the selected part's selected mBOM version.

To add assigned installs to the step that is currently displayed in the procedure window, select the + button next to the mBOM item on the bottom right of the panel.

The quantity assigned is the minimum required installation quantity to complete a run step.

When you have installation requirements assigned to a step, they will show up in the upper half of the panel. mBOM items can be partially assigned to steps. The formatting is represented as Qty Assigned to Step / Total Quantity in mBOM (Unit).

When creating a run, you can only create a run against the latest released mBOM version, or if none are released, than the latest draft. Please ensure you release mBOMs as needed to be used in runs.

We recognize there will be situations to release a procedure for a released mBOM while drafting up a future version of the same mBOM. Please keep the above note in mind when building procedures.

Once mBOM items have been completely assigned, they will shaded green on the mBOM panel if the "Show All" toggle is on. With the "Show All" toggle off, completely assigned mBOM items will be removed from the view for a more streamlined assignment process.

Substitutes

The crossing arrows highlight substitutes on the mBOM, showing what other parts are listed as substitutes.

Reference Designators

Similar to assigning the minimum quantity to close a step, you can also assign reference designators that are required to close a step.

Installing Inventory on Run Step Installation Requirements

Similar to installing inventory on the aBOM, now it is much more accessible from the run step itself.

You will not be able to complete a step until all run step build requirements have their minimum quantities and reference designators satisfied. The inventory list will include any available substitutes.

Permissions

To create, update, and delete installation requirements on procedures, please grant yourself a role with StepPartRequirement permissions.

Modifying your mBOM

Oftentimes, your mBOM changes even after you have released a procedure. Our aim is to prevent you from having to manipulate the procedure in as many cases as possible so you can make changes on the fly. Here is how ION handles the different types of changes on a mBOM.

No Changes to the Procedure are Required:

  • Removing a part:

    • This removes the associated installation requirements from associated procedures. This will mean you can safely remove parts without needing to revise the procedure to effect those changes.

  • Updating the part number on an existing mBOM requirement:

    • This will update all installation requirements in associated procedures automatically with the new part number.

  • Updating the name of a reference designator:

    • This will update all installation requirements in associated procedures automatically with the new reference designator if called out.

  • Adding substitutes:

    • All installation requirements will now show those new substitutes.

Procedure Revision Required:

  • Adding a part:

    • There is no impact on associated procedures.

  • Updating the quantity of an mBOM requirement:

    • You cannot reduce the quantity past what is assigned to a procedure. In this instance, you will need to create a new procedure and then up version the mBOM as well.

    • You can increase the quantity with no impact on associated procedures.

In every case, there is no impact on existing runs and aBOMs at the time of change.

Best Practices

  1. Installs will not be propagated across batches.

    • Each batch is designed to ensure traceability for every run within it. Since you need to select the specific inventory you install, allowing installs across different runs would compromise this traceability and could lead to inconsistencies in inventory tracking. By restricting installs to individual runs, you maintain the integrity and accuracy of the manufacturing process.

  2. You can only assign installation requirements on standard steps when they are called out in a procedure.

    • Each procedure is unique to a set of parts and mBOM versions, you can assign installation requirements on the procedure that calls out a released standard step. You cannot add installation requirements on standard steps when they are in a draft or any state.

  3. The installation requirements on steps are a minimum requirement therefore, proper training is required with technicians.

    • If technicians continue to install through the aBOM manually, ION will ask them to install again to meet the minimum requirement needed to complete the step. Therefore it's best to train technicians to use installation requirements so this issue does not occur. Redlining is coming at a later date so if you are not confident that your procedures will change then we recommend setting the minimum installation requirement quantity to zero with the quantity needed listed on the step content itself to allow you to make changes as needed.

  4. Redlining: At the moment, redlining of new part step requirements is not available. If you do not want to require installs on run steps because of the inability to redline, go into your Org Settings, and under runs, tick the box Allow run steps to be complete without required install.

Coming Soon

  1. mBOM Importer improvements: We want to improve how you import mBOMs to allow you to preserve as many connections with existing procedures as possible. This will enable you to make small changes to mBOMs without recreating all of your required installations on procedure steps.

  2. Parts Panel and Step Build Requirements Assignment Panel Workflow Improvements: At the moment, to access the step build requirements assignment panel, you need to click through the parts panel on the procedure. We know that manufacturing engineers will spend more time on assigning mBOM items to steps and not adding top-level assemblies to the procedure. We'll make improvements to make these views more streamlined and accessible from the procedure.

v4 mBOM is in Review
Select which reference designators are needed on which step