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
  • Overview
  • MOA Frequently Asked
  • MOA in aBOMs
  • MOA in kits
  • Made on Assembly philosophy
  • Made on Assembly in Autoplan

Was this helpful?

  1. Features
  2. Parts Library
  3. Manufacturing bill of materials (mBOM)

Made on Assembly (MOA)

Design your mBOM to build multiple levels of an assembly on the same work instructions.

PreviousmBOM versionsNextPart Substitutes

Last updated 7 months ago

Was this helpful?

Overview

Made on Assembly is a useful tool for the cases where a single procedure will always build two or more levels of an mBOM. Consider the mBOM below:

If based on the workflow, part B is built in the process of building part A, and there is no need to inventory part B separately, it might make sense to set part B to MOA. The information below will show how Made on Assembly is handled across ION and help you decide which parts should be designated as MOA.

MOA Frequently Asked

Here are some other notes on MOA:

  • Where can MOA be set?: toggle MOA on the mBOM via the part library

  • How can the grandchildren parts be installed?: multiple levels of the aBOM can be accessed via the aBOM manager on a run

  • How are MOA inventories generated?: part inventories are autogenerated for the MOA part when the aBOM is created (if serial-tracked, serial number is autogenerated, otherwise will autogenerate a lot number)

MOA in aBOMs

Defining as assembly as Made on Assembly will allow you to build the aBOM for that assembly while building the parent.

In the example below the wheel assembly has been set to be MOA in the mBOM.

The expanded mBOM for the car assembly looks like this:

When a run is created for the car assembly (part number 12345-01-01) and the aBOM is opened, you'll notice 2 things:

  1. An inventory item has been created with an auto-generated lot number for the Made on Assembly (MOA) part.

  2. You can install the children for the wheel the assembly. This allows you to build multiple levels of the aBOM in one process!

From here, you can proceed to install components as usual.

MOA in kits

When kitting an assembly that has MOA assemblies, MOA parts are not included in the kit, but their children are.

This kit was generated from the same mBOM as above. Notice how the wheel assembly is not an item, but the tire and wheel hub parts are.

Made on Assembly philosophy

The reason that we construct multiple levels of the aBOM for MOA parts is so that you can remove MOA assemblies easily.

For instance, in the example above, if you were to remove the wheel assembly later on after it had been built, its children would also come with it. If we were to flatten the BOM to include the children parts, you would have to remove each child part (tire and wheel hub) individually.

Made on Assembly in Autoplan

In Autoplan, Made on Assembly components will be marked as Placeholder within the plan results. Placeholder items cannot be converted directly into runs/purchases. They are purely there to fully represent the hierarchy of the BOM, but they should not be actioned themselves.