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
  • Why is it valuable
  • Getting into the details
  • aBOM construction
  • Substitutes
  • Visualizing aBOMs
  • Modifying an aBOM
  • Sharing Installations Amongst Parent Assemblies

Was this helpful?

  1. Features
  2. Parts Library

As-built Bill of Materials (aBOM)

Trace the genealogy of your build in REAL-TIME.

PreviousParts LibraryNextEditing aBOM build requirements

Last updated 29 days ago

Was this helpful?

Overview

IONs aBOM is a powerful tool that allows you to keep track of which parts, down the serial or lot number, were used in higher-level assemblies, across multiple levels of assemblies. The aBOM is a living and real-time document, meaning that changes are reflected instantaneously as parts are installed or uninstalled.

The aBOM can be accessed from either runs associated to the assembly, or from the inventory screen as seen below.

Why is it valuable

The aBOM is a massively valuable dataset within the factory. The traceability allows for:

  • Finding all places that a component is installed if something goes wrong (i.e. containment for recalls)

  • Understanding all data that was part of a build: runs, inventory, purchases, etc. This enables aggregations such as understanding the cost of the build or how long it took.

Getting into the details

The aBOM follows the requirement and fulfillment model like other parts of ION (for instance, kits). Parent inventories have build requirements that define:

  • which part is required (including potential substitutes)

  • the minimum quantity required

  • reference designators (optional)

Inventories get installed into build requirements via aBOM installations. The aBOM installation tracks:

  • the inventory installed

  • the quantity installed. The exception to this is when the build requirement quantity is set to 0. This allows the operator to install without setting the quantity and just select the trace information such as lot number.

  • if it was installed into a specific reference designator

When an inventory is uninstalled, all of its children travel with it. This means that the data for the entire assembly moves with the inventory to match the physical reality.

aBOM construction

You can install into the aBOM as seen in from the run execution screen. From here, you can start adding parts to your aBOM, and even use the "Install from Kit" button to install all the same lot numbers and serial numbers from the kit associated with the run. You can also add parts to the aBOM at the time of execution if needed.

After installing your parts, the build aBOM changes to Build aBOM (100%) to show that you have installed all of the parts for the run. Build requirements that do not have a quantity greater than 0 do not count towards the final aBOM build percentage.

Substitutes

On the aBOM, substitutes will appear with the "double arrow" icon shown below.

Here is how they will display within the aBOM interface:

  1. The icon indicates that a substitute can be used to fulfill the requirement

  2. Expanding the requirement will display the part numbers for the acceptable substitutes

  3. When a substitute is installed, the icon will appear next to the installed part

Visualizing aBOMs

Even while an aBOM is being constructed, you can visualize the parts that make up the part you are interested in by going to Parts > Trace. From here, you can search for a part, which will then load the in-progress or complete aBOM for that specific part.

Modifying an aBOM

Simply create a new run for the top-level assembly that you are affecting. For example, if you are changing the engine controller on the following BOM:

  • Vehicle

    • Engine

      • Engine controller

Create a run with the part number and serial number for the engine. Include a procedure with the instructions for changing the engine controller. This will allow the operator to remove the old engine controller and install a new one, by serial (or lot) number. The resulting aBOM will be updated for all levels up the vehicle's aBOM.

Permissions

Modifying the requirements of an aBOM has different permissions than installing/uninstalling.

Here is the mapping of permissions to those actions:

  • Install a part -> CreateABomInstallation permission

  • Uninstall/remove a part -> DeleteABomInstallation permission

  • Update the aBOM requirements (build requirements) -> Create/Update/DeleteBuildRequirement permission

Sharing Installations Amongst Parent Assemblies

See Split Inventory on a Run for more details.

An aBOM is a tree-like scaffolding that connects parent and children inventory. Each node is an inventory item (see: ), whether serial-tracked, lot-tracked, or untracked.

Inventory
If the Build Requirement quantity is set to 0, a tool tip is displayed informing the operator that the quantity is optional
The aBOM maintains a multi-level relationship across BOM items, including serial and lot numbers