---
title: "Part Count Checker"
slug: "part-count-checker"
updated: 2024-01-09T15:20:57Z
published: 2024-01-09T15:20:57Z
canonical: "support.tulip.co/part-count-checker"
---

> ## 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.

# Part Count Checker

We are going to check an example, where we want to monitor the amount of good produced on the machine and get notified if something goes wrong.

---

### Scenario

Let's say you are an operator or supervisor on an automated production line, and one of your tasks is to monitor how much parts a specific machine produces every hour. It's important to check, because if it under- or overproduces, some severe problems can occur on the line. Since you don't want to manually check the amount of goods produced every hour, you're going to use an Automation for that.

### Use case

We are gonna use a prebuilt Library automation to save us some time and effort, so go to the [Library page](https://tulip.co/library-search/) in tulip and search for "Part Count Checker" automation project to download.

### Flow explanation

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

### Configure automation

After importing it to your instance you can see the full flow, but before you start actually using it, you need to configure it to you specific needs. This requires the following steps:

1. Choose or create a Machine, and inside that a Machine Attribute you'd want to monitor.
2. Select or create an Analytics, which is configured to check and display the desired attribute.
3. On the analytics page create a control chart with a specified Lower and Upper limits. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28250%29.png)
4. Select the created analytic under the Automation Event Details.
5. On the E-mail Action Details panel, set the user you'd like to notify in case of problems, and also customize the Subject and the Body of the e-mail as you wish.

In this specific scenario, we will create a Test machine with a Part Count attribute, and also create an Analytics to monitor this attribute every hour. We predetermined a Lower and an Upper Limit in the control chart panel as well. Now you have a 24/7 working automation to alert the user if something goes wrong with the machine.

## Further Reading

- [Getting Started with Automations](/r230/docs/getting-started-with-automations)
- [Overview of the Automations Editor](/r230/docs/overview-of-the-automations-editor)

Check out other [Automations solutions available in the library](/r230/docs/automations-1)!

**Automation**

**Workflow** that performs tasks in the background, without an interface. Automations run logic every time an **event** occurs.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Glossary/Automations1.gif)

**Machine**

A **Machine**is a digital representation of a physical datasource. Machines have **Attributes**that are updated through an OPC-UA Connector or the Tulip API.

**Machine Attribute**

**Machine Attributes**are setpoints and actual values for different parameters of your **Machine.**Attributes can be mapped to OPC-UA datasource Tags.

**Analytics**

**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-1662410510869.png)