Split Inventory on a Run | ION Factory OS

The manual for the New ION Experience has been released.

For the complete documentation index, see llms.txt. This page is also available as Markdown.

Use Case:

During the receiving process, you're looking at 10 parts provided by a supplier. After conducting an inspection, you note that 3 of those 10 parts contain visual defects that deviate from the expected condition.

How do you address the issue with those 3 parts without holding up the progression of the other 7 through your process?

In ION you can create an issue ticket to handle just those three parts, assign a location to them such as an MRB cage, and continue running the remaining seven.

For information specific to issues check out this page with more details.

The video bellow shows you how to execute this functionality in the run execution window.

Split WIP Functionality Demo

Split WIP Functionality Demo
1 min 16 sec

Case Study: Create 5 "New York Cheesecakes" and Split Off 2 Mid-Process

This is a more complicated case where the parent inventory item has multiple child components required to build it; these are the aBOM build requirements.

Split WIP Project Demo - New York Cheesecake Recipe

Split WIP Project Demo - New York Cheesecake Recipe
6 min

How ION handles splitting build requirements on a split WIP assembly

Steps followed in the video:

  1. Establish the run to produce those five cheesecakes.
  2. Once the run has been created you will see these in inventory as WIP. They will also be assigned a location of your choosing, in this case the "Great Place".
  3. The build requirements (aBOM) for a singular cheesecake is set up to be 3 Sugar, 2 Cream Cheese, and 1 Egg. This will be important when we create a split WIP issue with partially installed quantities.
  4. Total Build requirements for the five cheesecakes is thus: 10 cream cheese, 15 sugar, 5 eggs.
  5. During the procedure you have installed 2 sugar and 1 cream cheese when you notice there is an issue with two of the cheesecakes. The location of the installed goods at this point is in the "Great Place" where the cheesecakes were originally destined for.
  6. You create an issue ticket to split those two cheesecakes off the run and put them in a location called "Bad Place".
  7. From the inventory page, you will now see that those two split cheesecakes are now available in the "Bad Place". If "Bad Place" was an "Unavailable" inventory location, users could use it as a way to make split-off inventory "Unavailable" for use elsewhere.
  8. Likewise the current logic is that all components installed into the split-off inventory will also move to the new location "Bad Place".
  9. Looking at the aBOM now for this run you will see a couple additional pieces of information:
    1. For build requirements that had some inventory installed before the split, they will now show a UI indication that they are shared between the two parent part inventories. In the video's example, it shows the build requirement is linked to inventory ID 12 and 15.
    2. The quantity looks like Qty: 1 of 6 (10). Hovering on the tooltip shows you that 1 inventory is still installed on the build requirement, quantity 6 is the current quantity required by the build requirement of the part, and quantity 10 was the original build requirement quantity. Since it's impossible to exactly know whether the qty 1 was a component of the newly-split off inventory or still in inventory attached to the Run, the previously installed inventory will remain visible on the Run's aBOM even after the split.
    3. 6 total sugar are needed for the remaining three cheesecakes down from the original 10 demanded.

Logic Diagrams:

Imagine you’re overseeing a production process where items (like machines or baked goods) are built from several parts or materials. In some cases, problems come up, so you need to separate out certain items from the production line while still keeping track of what’s been done. These scenarios explain how the system manages and tracks parts, depending on how far along they were in the assembly process.

Scenario 1: No Parts or Materials Installed Yet

In this scenario, nothing has been added to the items being produced yet—no materials or components are installed. Let’s say you need to separate out a few of these items before any work has begun.

Scenario 2: Some or All Parts or Materials Installed

Now, let’s say work has already started, and some of the materials or parts have been installed. You then realize there’s an issue with a few items and need to separate them.

Scenario 3: Mix of Installed and Uninstalled Parts

In this case, some parts or materials are installed, but others haven’t been added yet. Let’s say half the materials for each item are installed, while the rest are still waiting to be added, and you need to split out a few items due to an issue.

aBOM Installation Sharing amongst Parent Assemblies

As mentioned above, when parent assemblies are split, we make no assumptions as to where the installations should belong.

Uninstalling a shared installation

Because a shared aBOM installation is a single record linked to every lot produced by the split, uninstalling it removes it from all of those lots — not only the one you are viewing.

ION makes the shared relationship visible so the change is deliberate: