---
title: "Quality Inspection Use Case"
slug: "quality-inspection-use-case"
updated: 2024-05-03T15:19:27Z
published: 2024-05-03T15:19:27Z
canonical: "support.tulip.co/quality-inspection-use-case"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Quality Inspection Use Case

*Imagine you’re a quality manager who’s noticed a consistent defect of an item in each product over the last month. Because you’ve been manually compiling quality inspection information into a spreadsheet and assessing the data, it took a few weeks to realize that there was an issue with the machine itself. While you’ve identified the issue and implemented repairs, you’re frustrated that it took so long to detect in the first place. A paper process will always require more manual labor and time, but a digital quality inspection process can analyze information in real time. By implementing quality inspection apps at your facility, you start immediately flagging anomalies, which results in reduced downtime and scrap rates and improved yield.*

Quality inspection involves guidance on proper evaluation of parts, sub-assemblies, and products against a standard. This use case can help you identify root causes with quality issues to drive process improvements.

![QA 3](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202023-11-26%20at%2014.09.46.png)

Quality inspection can identify many opportunities to improve your process. See the table below to understand how applications can support your quality goal.

| Goal | How to Achieve |
| --- | --- |
| Improve data integrity, Automate data collection | Automatically capture data into tables and completions |
| Detect defects | Error proof and automatically catch anomalies with alerts and spec requirements |
| Drive process improvements | Visualize areas of the process and identify which ones perform below expectations |
| Identify root causes | Organize defect types and locations into a pareto chart; collect sufficient data to support RCA |
| Compliance | Adhere to quality standards across all personas with set access privileges to apps and analytics |
| Traceability (rework) | Capture data that reveals the history to accurately report where rework needs to happen |
| Trustworthiness and reliability | Prove that you can catch defects with the results to back it up |
| Bottom line - reduce scrap | Intervene early, initiate rework loops, and improve handling of materials |
| Automate quality inspection processes | Reduce time spent on data entry and re-entry, and reduce the likely of paperwork errors |
| Quality control | Employ better management overall when all personas who need visibility can have it immediately |

## Impact and Requirements

Traditionally, companies either have a manual quality inspection process or a rigid process built into their MES. Both methods can be painful when it comes to managing updates, analyzing data, and reducing human errors.

Digitizing quality inspection is a scalable and sustainable approach that can be easily adapted for new products or processes.

1. **Quality escapes** Inevitable human errors mean quality escapes are bound to get through an inspection process if not flagged. When moving through quality inspection apps, you can create and send defect reports for any failed inspection. This ensures information reaches the right people before customers receive the products.
2. **Reduce cost of quality** If your quality process takes significant time, and therefore has a high cost, quality inspection apps are a great solution to mitigate those issues. Streamline the process with automatic data collection, reusable processes, and analyses that reveal areas to focus and improve efforts.
3. **Scrap reduction and yield improvement** Use quality inspection app data to draw attention to where issues are. Visualizing data with analyses automatically show insights that otherwise must be manually calculated with a paper process. For example, these insights can lead to investigating scrap issues in order to increase yield. Make quality improvements that save time and costs.

![5S_Dashboard.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/5S_Dashboard.png)

Any industry can benefit from deploying quality inspection apps, but they are especially ideal for scenarios with high cost of goods and high value materials. Additionally, any operation with high variation from piece to piece can be prone to mistakes and therefore gain significant value.

This use case is an ideal starting point for quality solutions because it’s easy to implement from manual inspection. Quality inspection is scalable and offers quick value. You can also use minimal ERP and device integrations.

## How to Get Started

Before you build an app, it’s important to obtain a snapshot of your current inspection process and decide where you want to go. Complete the following steps in order to ensure success:

1. **Capture baseline quality data.** Taking note of the current state allows you to measure improvements from your starting point. Get quick-to-value digital insights to inform KPIs and improve business value. Ex. current pass/fail rates, current count of defects by reason code, etc.
2. **Agree on measurable business objectives.** What areas of quality are you concerned with? What do you want to see improve? What are the goal metrics you want to hit? Ex. Reduce time spent dispositioning
3. **Determine the personas involved and capture high-level user stories.** Who does quality inspection concern and how do they benefit? This information will inform the various functionalities within the app, what data needs to be captured, and what you need to do with that data. Ex. Operators need to log quality events so they can be reviewed and dispositioned, Supervisors need real-time visibility into quality events, Quality team needs ability to review and disposition quality events

### App Architectures

Once you complete the above steps, you can start app building. Because quality inspection can take different forms, there are multiple ways you can create apps to go through this process. **Start with a simple app and iteratively build in more complexity, including integrations.** Let’s go through different types of apps with variations in complexity and features.

#### Checklist App

The simplest and quickest way to deploy a quality inspection app is to create a checklist of your inspection process. This looks like a series of steps that ask questions or collect information. Capture data through Variables or Table Records, then visualize the data with Analytics.

![QA 5](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202023-11-26%20at%2014.12.18.png)

#### Work Instructions-Centric

Integrate quality checks into a work instructions app that uses existing Completion records. This model replicates a step-by-step instructions flow for inspection.

![Work Instructions Quality Inspection.webp](https://tulip.widen.net/content/vvafqudplr/webp/Work%20Instructions%20Quality%20Inspection.webp?position=c&color=ffffff00&quality=80&u=gimbls)

### QMS Integration

Integrating with a QMS, such as [Arena](/r230/docs/arena-integration), allows for more advanced statistical processing. Use data that you already have and get advanced statistics for your analytics.

[Check out the QMS App Suite available in the library.](https://tulip.co/library/suites/qms-app-suite/)

#### AI-powered with Vision

Automated visual inspections rely on visual data to make assessments. With machine-based analysis, they offer a way to substitute human visual judgment. This method requires integration with Tulip Vision, which is recommended for advanced users.

![Elementary Drill Inspection App.webp](https://tulip.widen.net/content/mlbqpgbqvv/webp/Elementary%20Drill%20Inspection%20App.webp?position=c&color=ffffff00&quality=80&u=gimbls)

The deployment path below shows how you can progress from one quality inspection method to another by integrating other use cases and features into your app architecture.

![Quality%20Inspection%20Advancement%20Path](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Quality%20Inspection%20Advancement%20Path.png)

### Best Practices

**Review Tulip’s [data collection methodology](/r230/docs/gxp-data-collection).** It’s important to differentiate when to store data in a table vs in completion records. For example, quality events are an operational artifact and should therefore log into a dedicated table. Cycle times and app operator data should be stored into completion records.

**Provide real-time visibility to all personas via [Analytic](/r230/docs/what-are-analytics)s.** Visualize your data to determine if you’re meeting your business goals and drive continuous improvement. Each persona has particular information relevant to their process. Create dashboards that provide insights and compile a picture of current state.

### Tulip Resources

Whether you want to learn more about Tulip features to build quality inspection apps or you want to use Tulip’s ready-made templates, we have the tools to help you get started.

#### Videos

- [Quality Inspection](https://tulip.co/library/videos/quality-inspection/)
- [Quality Inspection at Stanley Black & Decker](https://tulip.co/library/videos/quality-inspection-at-stanley-black---decker/)

#### University Courses

- [Quality and Validation](https://university.tulip.co/path/tulips-digital-approach-to-quality-and-validation)
- [Guided App Building](https://university.tulip.co/how-to-build-your-first-app?next=%2Fhow-to-build-your-first-app%2F270)

#### Library Apps

- [Quality Inspection Template](https://tulip.co/library/apps/quality-inspection-template/)
- [Quality Management Dashboard](https://tulip.co/library/apps/quality-management-dashboard/)
- [Audit Checklist App Suite](https://tulip.co/library/suites/audit-checklist-app-suite/)
- [5S Checklist](https://tulip.co/library/apps/5s-checklist/)

#### Examples

- [Inspection Functional Example](https://tulip.co/library/apps/inspection-functional-example/)
- [Simple Checklist Functional Example](https://tulip.co/library/apps/simple-checklist-functional-example/)

**Variable**

**Variables**are a location to store app information. Variables have a specific type that must match the contents they can store.

Variables are only accessible within a single application and are cleared when the app is restarted or completed.

**Table Record**

A **Table Record** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from with an App Trigger.

To edit a record it must be loaded into a **Table Record Placeholder.**

**Analytic**

**Analytics** are live updating graphs and metrics calculated based on app data, Table data, and machine data. Analytics can be embedded and dynamically filtered within an application.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-1662410531382.png)

**App Completion**

**App Completions**are a mechanism to store immutable data from a Tulip app. When an app is completed, all **Variable's**current values will be stored in the app completions tab.****This completion data can be analyzed in **Analytics.**

By default, after a Completion users will be brought back to the **Begin Screen**of your application. This behavior can be adjusted with other **Transition**types.

**Tulip Vision**

**Vision**is a simple no-code tool to use cameras for visual inspection, process adherence, equipment, personnel, and material tracking on the shop floor.