ion Trace allows you to keep track of which parts, down to the serial number, were in higher-level assemblies.
ION 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. ION's aBOM structure maintains this information in a tree-like data structure that is mostly independent from runs. The design decision to not rebuild the aBOM from runs was made because of the increasing number of use cases and companies where parts are removed and replaced multiple times. The aBOM allows for tracking exactly which parts were installed on a higher-level assembly while keeping flexibility around when/how those parts are installed.
An aBOM is basically a tree of nodes with parent/child relationships. Each node is an inventory item (see: Inventory), whether serial-tracked, lot-tracked, or without any tracking. aBOM nodes do not have a quantity. Rather, they are always quantity 1, as aBOMs are the exploded from the mBOM that defines them.
aBOM nodes become related and bring their inventory information with them that are independent of their installation status. This means that even if a part is removed from a parent part, it keeps all of the information about itself.
Overview showing how inventory items get associated to aBOMs. The parent part is then moved back to inventory, so that it can then be installed on a higher-level assembly.
An aBOM is constructed by "installing" BOM items on higher-level assemblies. The installation happens in the technician interface, where the "Build aBOM" shows a panel where an operator can install components to the part that is being built. As serials are installed in their respective slots, the aBOM is constructed for visualizing later. To build an aBOM from a run, click into a step on the run by clicking "Go to execution". There will be a button that says "Build aBOM" above the fields entry. Click it.
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.
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 number and serial number, which will then load the in-progress or complete aBOM for that specific part.
The aBOM maintains a multi-level relationship across BOM items, including serial and lot numbers
More commonly, companies are swapping parts already installed with other parts. This is possible and simple in ION. 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:
- 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.
Last modified 9mo ago