Intent Management

Deploy Intent/Pedigree/Tiers/Grades to the production floor

ION's Intent Management lets your organization track, enforce, and propagate intent designations across parts, inventory, purchases, procedures and runs. Examples of intent designations include flight vs. non-flight, production vs. prototype, or any graded quality level your team uses.

Note: Contact your Manufacturing Success Manager to enable this feature for your organization.

---

What Problems Does Intent Management Solve?

Without intent enforcement, teams must rely on manual processes to ensure that only the right-grade parts end up in critical assemblies. ION's intent management automates these checks by:

• Validating that inventory meets intent requirements when it is kitted or installed.

• Propagating intent automatically from purchase orders, runs, and issues.

• Blocking or downgrading intent assignments that would violate your quality policies.

• Requiring that users set intent at key workflow steps (run creation, step start, etc.).

---

Navigating to Intent Settings

1. Navigate to the Settings from user user icon at the bottom of the side bar.

2. Select Intent from the left sidebar.

From this page you can configure all settings described below.

Setting Up Intent Options

Before enabling enforcement policies, define your organization's intent options (e.g. Flight, Dev ...), and put them in the correct order.

How Intent Options work

• Each option has a label (for example, Flight, Production, Development).

• Each option also has a rank.

• Lower rank means higher/stricter quality (rank 0 is most strict).

This ranking is what settings like require_kit_intent_match and require_install_intent_match compare.

Aliasing Intent

For various reasons, an organization may refer to Intent by a different name. Common alternatives include pedigree, quality level, and tier — driven by regulatory requirements or internal conventions.

ION's intent management supports this flexibility through the intent_alias organization setting, which lets you define what your organization calls Intent within ION. The configured alias is used as the label wherever Intent appears in the UI.

Note: Regardless of the configured alias, the API field remains intentOption.

Recommended setup flow

1. List your quality tiers from most strict to least strict.

2. Create each intent option.

3. Order them so strictest is first (lowest rank).

4. Verify the hierarchy with your quality/manufacturing owners.

5. Then enable policy settings in this guide.

Example hierarchy

Rank	Intent Option
1	Flight
2	Critical Non-Flight
3	Development

If this order is wrong, enforcement behavior will be wrong (for example, allowing lower-grade inventory where it should be blocked).

---

Quick Reference: All 11 Settings

Setting	Description
Intent Label	Rename "Intent" to a custom label throughout the UI.
Kit Intent Match	Enforce intent requirements when inventory is kitted or delivered
Install Intent Match	Enforce intent requirements on aBOM installation
Required at Run Create	Require intent to be set when creating a run
Required at Run Step Start	Require intent to be set before starting work on a run step
Required on Run Intent Update	Prevent intent from being cleared on a run
Part Quality Check	Block or downgrade intent assignments that exceed the part's own intent
Downgrade on Install	Automatically downgrade inventory intent to match the parent assembly on install
Run Intent Side Effect	Assign a run's intent to inventory built on the run
PO Line Side Effect	Assign intent from a PO line to on order inventory
Issue Intent Update	Update inventory intent automatically when an issue is resolved