Part-Procedure Relationship

Procedures may be associated with one or more parts to relate a workflow with a specific workpiece. Link a part and a procedure from the Parts tab on a procedure. Note that this isn't a parts list that are in an assembly - by setting this relationship you are telling ION which procedures are used to produce a certain part or assembly.

You can also set up the part-procedure relationship from the parts library sidebar.

When you link parts through this relation when you have the "Require part-procedure relationship to be approved" box checked in your organization settings, ION will not allow you to create runs unless the selected part is linked to the selected procedure.

With this box checked, when you attempt to create a run with a procedure that is not linked to the selected part, you will get an error that looks like this:

Required vs. Optional Part Procedure Relationships

When linking parts to an inspection procedure, the Required or Optional setting determines whether an inspection run is automatically created upon receipt.

• This toggle ONLY effects INSPECTION type procedures their parts upon receipt.
• Required: When a part marked as required is received, an inspection run is automatically generated for that part according to the associated procedure.
• Optional: When a part marked as optional is received, no inspection run is automatically created. You can still initiate an inspection manually if needed.

This setting helps control which parts must go through inspection by default and which can be inspected at your discretion. See it in action below.

{% embed url="https://www.loom.com/share/36a69ebc5462407894e8ee3deb86c2af" %}

Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the ask query parameter, and the optional goal query parameter:

GET https://manual.firstresonance.io/features/procedures/part-procedure-relationship.md?ask=<question>&goal=<endgoal>

ask is the immediate question: it should be specific, self-contained, and written in natural language. goal is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.