---
title: "Machine Monitoring Terminal"
slug: "machine-monitoring-terminal"
updated: 2024-04-17T20:03:25Z
published: 2024-04-17T20:03:25Z
---

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

# Machine Monitoring Terminal

The first step to driving business value from your machines is understanding their state. Collect machine state, track the key components of OEE, and drive business value with the Machine Monitoring Terminal Application.

### Machine kit configuration

Before you can use this application with the *Machine Kit* offering, you have to configure the analytics first. Open every analysis for editing, and on the *Machine* panel make sure that the *Machine Kit* type is selected as well. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28216%29.png)

### Setup

Setup for this application is minimal. This application allows users to select any Machine that has been configured in your Instance.

![Screenshot 2023-09-26 at 13.46.59.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202023-09-26%20at%2013.46.59.png)

#### Machine Type

Along with this application comes an example Machine Type. The *Machine Kit* type is a barebones starting point for leveraging the Tulip Machine Monitoring offering.

This machine has a *Machine Current* attribute that can be mapped to various different data sources. When this attribute goes above 10, the machine will be set to a running state, when it goes below 10, the machine will be set to Stopped. These thresholds can be adjusted in the Machine Type Triggers.

### How it works

When a machine is selected, the machine terminal will automatically update with the data for the selected machine. You can leverage the machine type that comes with this application, or leverage your own.

#### Downtime Tracking

When your machine enters a downtime state, a downtime reason can be assigned to that state to drive further visibility into root cause. Clicking on the *Change Downtime Reason* to select some example downtime reasons. Picking any downtime reason will assign a reason to the current downtime state.

![Screenshot 2023-09-26 at 14.04.38.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202023-09-26%20at%2014.04.38.png)

#### OEE Tracking

Overall Equipment Effiency is built on 3 component parts:

1. Quality
2. Performance
3. Availability

$OEE = Quality * Performance * Availability$

The definition of each of these components is heavily contested, but this app has these components implements by their widely accepted definitions:

#### Quality

Quality is the ratio of good parts reletive to the total number of parts. In short, this is the percent of *good* parts.

$\frac{\text{number of good parts}}{\text{number of total parts}} = Quality$

For example:

$\frac{80\text{ good parts}}{100\text{ total parts}} = .8$

Within the Machine Terminal app, we track total parts and defective parts with the *Add* buttons under the *Parts made* and *Defects* part. We can also set an ideal *Parts / HR* value by the + and - buttons

![Screenshot 2023-09-26 at 15.19.17.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202023-09-26%20at%2015.19.17.png)

#### Performance

Performance is the component to identify opportunity to run closer to the ideal run rate.

$\frac{\text{Units produced in the last hour}}{\text{Units produced in 1hr at ideal run rate}} = Performance$

*ex. Our CNC machine when running ideally can produce 45 parts an hour, but in the last hour, we have only produced 32 parts.*

$\frac{\text{32}}{\text{45}} = .711$

In the Machine Terminal Application we track units produced with the *Add* buttons mentioned above and the ideal run rate (per hour) is set with the *Parts / HR* + and - buttons.

#### Availability

Availability is the component that tracks the *uptime* of your asset reletive to the *available* time. Within the Machine Terminal Application, we assume 24-hr operations, but this may differ for your facility.

$\frac{\text{Time Spent Running}}{\text{Total Time}} = Availability$

Availability is automatically tracked by the Tulip Machine Monitoring offering. The "Running" state is tracked as uptime, and the "Stopped" state is tracked as downtime.

![Screenshot 2023-09-26 at 15.27.21.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202023-09-26%20at%2015.27.21.png)

You can also see the the 3 OEE parameters individually and together as well on the top part of the application.

![Screenshot 2023-09-26 at 15.31.49.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202023-09-26%20at%2015.31.49.png)

#### Analytics

Select the *Analytics* icon in the app ribbon or the button in the footer to see detailed historic breakdowns of each downtime reasons, along with hour-by-hour OEE logging.

![Screenshot 2023-09-27 at 9.16.22.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202023-09-27%20at%209.16.22.png)

#### Notes

In the highlighted section you can see the added notes, which is useful for communicating important information during shift changes for example. If you want to add notes just click on the *Add Notes* button, which brings you to a page where you can do that.

![Screenshot 2023-09-27 at 9.20.36.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202023-09-27%20at%209.20.36.png)

### Further Reading

This application is just a starting point for machine monitoring. Check out some of the other documents to go deeper!

- [Machine Monitoring](/r230/docs/machine-monitoring)
- [Managing Machine States and Part Counts with Edge IO and Node-RED](/r230/docs/managing-machine-states-and-part-counts-with-edge-io-and-node-red)
- [Using Machine Data in the Analytics Editor](/r230/docs/using-machine-data-in-the-analytics-editor)

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

**Tulip Instance**

A Tulip customer account. Your instance can be found at https://[your-instance].tulip.co

When *your instance*is referenced, we are just talking about your Tulip account on an organization-level, not user-level.

**Machine Type**

**Machine Types** are global definitions of what data to expect from machines of different types. Each Machine Type will have different states, **triggers**, and **attributes**.*EX. We have 5 makes/models of CNC mill, but they all have the same set of attributes (Spindle speed, feed rate, etc.) These can all be combined into a single "CNC Mill" Machine Type*

**Trigger**

**Triggers** are groups of logic that are tied to an app event, such as step open, timer, widget interaction, etc. App builders can add triggers to **widgets**, **machines**, **devices**, **apps**, and **steps**.

**Triggers** can contain **actions**, **transitions**, and **conditions**.