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
  • Editing the mBOM
  • Editing the mBOM by exporting the mBOM
  • Importing the mBOM
  • Substitutes
  • Transfer to the aBOM (As-built bill of materials)
  • Full visualization of the mBOM

Was this helpful?

  1. Features
  2. Parts Library

Manufacturing bill of materials (mBOM)

PreviousInventory Movement AutomationsNextmBOM versions

Last updated 1 month ago

Was this helpful?

Editing the mBOM

The mBOM can be created/updated within the part library.

You are able to define only one bill of materials per part/revision. We recommend creating a new revision for the part if you have an update to the mBOM.

In addition to part and revision, the following attributes can be managed on the mBOM:

  • Substitutes: Parts that can be used interchangeably on this bill of material. This will allow other parts to be installed/kitted further down in the process.

  • Quantity: This is the minimum inventory quantity that needs to be installed to satisfy a build requirement on the aBOM. Suppose the mBOM quantity is set to 0. In that case, technicians can select untracked or lot-tracked inventory without selecting the installed quantity, which is ideal for consumables where only the trace information is relevant and not the quantity. Because the technician can always install more quantity than the requirement suggests, we recommend using this functionality for As-Required materials where you do not know the precise installed quantity in advance.

    • Consumables may include epoxies, kapton tape, or other cleaning materials.

    • As-Required materials may include carbon fiber layup and powder.

Editing the mBOM by exporting the mBOM

You can click on Go to full mBOM above and choose to export the mBOM as a CSV, make your edits in the spreadsheet, and re-import your mBOM into ION.

The mBOM will export in Level notation, so when you import it, make sure you choose that option!

Importing the mBOM

There are two options for importing BOMs - Depth Notation and Level Notation. With depth notation, if you accidentally disorganize your CSV file, you may have mBOMs that don't match eBOMs. See below for an example. The Equivalent "Level" notation is on the right hand side.

In this format, the level 1 is the top level, all the 2s are the next level down, 3s are the next level down from there, etc. But the order matters - if you moved the 3s underneath a different 2, the mBOM would change significantly. Therefore, it is important to make sure that your BOM is in the correct order and has not been rearranged since exporting it from your PLM/CAD software.

In Level notation, 1 is the top level assembly, and 1.1, 1.2, 1.3, 1.4, 1.5 are children of that assembly. 1.1.1 and 1.1.2 are children of 1.1, and 1.1.1.1 is a child of 1.1.1. See example below where the BOM was copied into the table as "manually imported data". Here you also have the option to import your parts via a CSV, TSV, or TXT file.

Faster mBOM import options

There are options to use a faster import that does not have preview capabilities, but will allow BOMs to be imported much faster than our standard options. Check out the below video for more information.

Substitutes

Substitutes should be in the format:

PartNumberA[X];PartNumberB[Z]

Where X and Z are the revisions for PartNumberA and PartNumberB

Transfer to the aBOM (As-built bill of materials)

When an inventory is created for an assembly with a serial number or lot number, that triggers an empty aBOM to be created from the mBOM. Each item in the aBOM maintains a link to each item in the mBOM and it's called the originMbomItemId. The aBOM uses this relationship to reach back to the mBOM for information such as substitutes and if the part is Made on Assembly.

Full visualization of the mBOM

Use the Go to full mBOM link to see entire mBOM in tree or indented views.

Made on Assembly (MOA): If true, it means that this assembly gets built on the same process with its parent. .

Reference designators: Defined positions in the mBOM that you'd like to maintain during installation.

to see this in action.

More on MOA here
More on reference designators here
Here is a click through