Intent Management / Grade / Tier / Pedigree
This page exemplifies the ability ION has to deploy intent management to your production floor.
Last updated
Was this helpful?
This page exemplifies the ability ION has to deploy intent management to your production floor.
Last updated
Was this helpful?
Intent literally defines the intended use case for each manufacturing step or object. That step can range from the receiving inspection associated with a part, to the final sign off before being installed on a spacecraft destined for the moon. Different tiers of this intent signify varying tiers of requirements and quality. In the aerospace industry intent tiers could be defined as the following:
FLIGHT: Demanding stringent qualification, usually for customer-facing and locked product designs.
DEVELOPMENT: Mid-level qualification, often seen in developmental processes when testing is taking place and there is still iteration.
ENGINEERING: Little to no qualification, typically reserved for research and development and often serving as proof of concept.
ION Implements Intent Management in the following manors, both accessible from the ION Marketplace.
: Facilitates seamless pedigree data transfer, ensuring comprehensive management.
: Enforces strict pedigree adherence during processes utilizing logic checks, safeguarding against invalid assemblies.
The logic behind intent management is as follows. Case 1 represents a highest intent, tier 1 flight part. Case 2 represents a development intent, tier 2 developmental assembly.
When ION's rules are deployed and catch a situation that needs to be blocked by logic the system response will populate an error message with the title of the rule that was triggered.
Prevent lower tier parts from being kitted on a kit destined for a higher tier assembly.
Prevent lower tier parts from being installed on a higher tier assembly.
Check on run completion that intent still matches parent assembly incase a part has been downgraded after install.
Determine receiving inspection based on intent indicated on a PO.
Demand intent is tied to purchase orders to drive inspections.
Auto assign intent to all runs or enforce intent to be assigned on runs.
Have part inventory adopt part intent based on that parts current lifecycle stage.
The next two pages detail how to deploy both Data Imprinting logic to transfer production intent attributes from one object to another and automated ION Actions that serve as blockers when the intent rules are violated.
