First init.
This commit is contained in:
BIN
1. Projects/1. Active/Enhanced Quality/.DS_Store
vendored
Normal file
BIN
1. Projects/1. Active/Enhanced Quality/.DS_Store
vendored
Normal file
Binary file not shown.
@@ -0,0 +1,181 @@
|
||||
Article last updated: September 9, 2025 at 9:56 PM
|
||||
|
||||
After you run an inspection, you need to collect inspection information. Use the **Inspection Results Entry** app to enter and analyze inspection data for parts, operations, resources, equipment, and fixed assets.
|
||||
|
||||
Once you adjust the inspection quantity, you then enter inspection results for each item using the configured panel and rules created for the inspection plan and specification defined. From this test data, the application determines if the item has passed or failed. In some cases, the quantity passed and failed returns to the calling process.
|
||||
|
||||
```ad-info
|
||||
You can launch **Inspection Results Entry** from multiple apps or from the main menu directly. In this article, we will inspect the items using the 'Data Collection' app, while you end activity. However, you can launch the 'Inspection Results Entry' app from the 'Main Menu'.
|
||||
|
||||
![[IMG-20250919070126086.png]]
|
||||
```
|
||||
|
||||
```ad-info
|
||||
You can launch **Inspection Results Entry** from multiple apps or from the main menu directly. In this article, we ill inspect the items using the 'Data Collection' app.
|
||||
```
|
||||
|
||||
```ad-warning
|
||||
Before reviewing the steps in this article, look at the 'Data Used in this Article' element below.
|
||||
```
|
||||
|
||||
```ad-example
|
||||
collapse:close
|
||||
title: Data Used in this Article
|
||||
##### Data Used in this Article
|
||||
|
||||
1. We a have a job with one operation and material. The material is set to 'Backflush'. The job is for '5' units of part 'DCD-100-SP'.
|
||||
|
||||
![[IMG-20250919070126110.png]]
|
||||
|
||||
2. The operation in the job's method of manufacture is tied to an inspection plan and specification.
|
||||
|
||||
![[IMG-20250919070126133.png]]
|
||||
|
||||
1. The specification tied to the operation holds three 'Inspection Attributes'.
|
||||
|
||||
![[IMG-20250919070126173.png]]
|
||||
|
||||
> [!info]
|
||||
>The 'Results Entry Page ID' field is used for the 'Application Studio' purposes only. Review step #13 in this article to see an example.
|
||||
|
||||
|
||||
2. We start production using the 'Data Collection' app. Again, the job is for '5' units of part 'DCD-100-SP'.
|
||||
|
||||
> [!warning]
|
||||
> The first step in this article will end production activity using the 'Data Collection' app.
|
||||
```
|
||||
|
||||
1. In the **Data Collection** app, select the **End Activity** button.
|
||||
|
||||
The **End Labor Activity** panel opens.
|
||||
|
||||
![[IMG-20250919070126229.png]]
|
||||
|
||||
2. In the **Current** field, we enter **5**.
|
||||
|
||||
Remember, the job was for five units of part 'DCD-100-SP'.
|
||||
|
||||
![[IMG-20250919070126250.png]]
|
||||
|
||||
3. Next, in the **End Labor Activity** panel, we select the **Inspection Data** button.
|
||||
|
||||
The **Inspection Results Entry** panel opens.
|
||||
|
||||
![[IMG-20250919070126270.png]]
|
||||
|
||||
4. In the **Inspection Results Entry** panel, select the **Generate Test Set** button.
|
||||
|
||||
![[IMG-20250919070126289.png]]
|
||||
|
||||
5. Next, select the **Enter Results** button.
|
||||
|
||||
The **Inspection Results** panel opens.
|
||||
|
||||
![[IMG-20250919070126307.png]]
|
||||
|
||||
6. In the **Inspection Results** panel, enter the results of you inspection.
|
||||
|
||||
![[IMG-20250919070126323.png]]
|
||||
|
||||
```ad-info
|
||||
title: Display order
|
||||
collapse: close
|
||||
In this case, we would enter the 'Thickness', 'Width', and 'Tolerance' results. These are the three attributes defined on the specification linked to the job's operation.
|
||||
|
||||
![[IMG-20250919070126340.png]]
|
||||
|
||||
Notice they display in a specific order. This is based 'Display Order' values entered for each inspection attribute. However, you can switch the display order if required. To do so, rearrange the 'Display Order' number. For example, we want the 'Inspection Results' panel to displays 'Tolerance' first. As a result, we would enter the value of '1' for 'Tolerance'.
|
||||
|
||||
![[IMG-20250919070126363.png]]
|
||||
|
||||
If we entered inspection results now then the 'Tolerance' column would display first.
|
||||
|
||||
![[IMG-20250919070126383.png]]
|
||||
```
|
||||
|
||||
7. In the **Inspection Results** panel, we enter the results and select the **OK** button to confirm.
|
||||
|
||||
![[IMG-20250919070126409.png]]
|
||||
|
||||
In this case, we enter results using the 'Results' card. However, you can also enter results using the 'Results Entry Detail' button. This would be the case if your 'Results' card includes many columns, so you do not have to scroll do the right to displays all the columns.
|
||||
|
||||
```ad-example
|
||||
title: Results Entry Detail example
|
||||
collapse: close
|
||||
##### Results Entry Detail Example
|
||||
|
||||
Assume you are entering inspection results and your 'Results' card holds many inspection attributes (columns). Therefore, you select the 'Results Entry Detail' button to enter your inspection results in a single panel.
|
||||
|
||||
![[IMG-20250919070126430.png]]
|
||||
|
||||
|
||||
As a result of the entries, all '5' items failed inspection.
|
||||
|
||||
![[IMG-20250919070126448.png]]
|
||||
```
|
||||
|
||||
8. In the **Inspection Results Entry** panel, select **Save**.
|
||||
|
||||
![[IMG-20250919082644043.png]]
|
||||
|
||||
9. In the **Inspection Results Entry** panel, select the **Close** button.
|
||||
|
||||
10. In the **End Labor Activity** panel, the quantity of **5** displays in the **Non-Conform Qty** field.
|
||||
|
||||
![[IMG-20250919082650761.png]]
|
||||
|
||||
11. Finally, select the reason code that specifies why the items failed.
|
||||
|
||||
![[IMG-20250919082658426.png]]
|
||||
|
||||
12. In the **End Labor Activity** panel, select the **OK** button to confirm.
|
||||
|
||||
13. You can also configure your inspection result using the **Application Studio** by selecting the **Application Studio** command in the **Overflow** menu.
|
||||
|
||||
![[IMG-20250919082702737.png]]
|
||||
|
||||
```ad-example
|
||||
title: Application Studio example
|
||||
collapse: close
|
||||
##### Application Studio
|
||||
|
||||
> [!info]
|
||||
>When you configure you 'Inspection Results Entry' screen and link it to the 'Specification' tied to job's operation then the configured screen displays once you select the 'Enter Results' button in the 'Inspection Results Entry' app.
|
||||
|
||||
The 'Inspection Result Entry' configured in the 'Application Studio' app and used in this section has been pre-entered and is just an example. You can configure any other 'Inspection Results Entry' page, based on your requirement.
|
||||
|
||||
For example:
|
||||
|
||||
1. You select the **Application Studio** command in the **Inspection Results Entry** app.
|
||||
|
||||
The **Application Studio** app displays.
|
||||
|
||||
![[IMG-20250919082708366.png]]
|
||||
|
||||
2. Next, we select the **Edit** icon.
|
||||
|
||||
![[IMG-20250919082715877.png]]
|
||||
|
||||
The configured page displays. However, this is just an example and you can configure any 'Inspection Results Entry' screen.
|
||||
|
||||
![[IMG-20250919082721026.png]]
|
||||
|
||||
3. Open **Properties**.
|
||||
|
||||
![[IMG-20250919082724683.png]]
|
||||
|
||||
4. Define a name. In this example, the name is **Slider.305RTD**.
|
||||
|
||||
![[IMG-20250919082734795.png]]
|
||||
|
||||
5. You then enter the added name to the **Results Entry Page ID** field located in the **Specification** app.
|
||||
|
||||
> [!info]
|
||||
> Remember, your job operation is linked to this specification.
|
||||
|
||||
![[IMG-20250919082744597.png]]
|
||||
|
||||
6. When you select the **Result Entry** button to enter your inspection results, the configured page displays.
|
||||
|
||||
![[IMG-20250919082750141.png]]
|
||||
```
|
||||
Reference in New Issue
Block a user