Contain Affected Inventory | ION Factory OS 2.0

Overview

When a defect or anomaly is discovered, the first priority is containment—making sure potentially affected parts do not continue down the production line or reach customers. Quickly attaching inventory to an issue ticket allows teams to isolate all related parts, whether they share a lot, serial number, or another attribute. This immediate action reduces risk, prevents costly escapes, and ensures every affected unit is accounted for.

By grouping inventory to a single issue ticket, manufacturers also gain a clear foundation for root cause analysis, disposition, and compliance. Instead of manually tracking affected parts across multiple systems, teams have one structured place to document the issue, evaluate corrective actions, and ensure regulatory traceability. The result is faster response, fewer errors, and stronger overall quality control.

Associating inventory with an issue can also affect its status. Depending on the issue's disposition type and its Availability Behavior, inventory may stay available, become Unavailable until the issue is resolved, or become permanently unavailable. Inventory already in Installed, Work In Progress (WIP), or Scrapped status is not changed by this rule. For configuration details, see Disposition Types.

How To

Key Steps

1. Access the Inventory Screen 0:00

2. Filter Inventory by Shared Attributes 0:55

3. Select Relevant Inventory Items 1:08

4. Open the Command Menu 2:11

5. Create an Issue Ticket 2:22

6. Review the Created Issue 2:59

Cautionary Notes

Tips for Efficiency

Link to Loom

https://loom.com/share/0ec507b8846e4d7fb212fb0713fb6547