---
title: "Machine attributes, downtime reasons, and states"
slug: "machine-attributes-downtime-reasons-and-states"
updated: 2022-09-30T16:58:36Z
published: 2022-09-30T16:58:36Z
canonical: "support.tulip.co/machine-attributes-downtime-reasons-and-states"
---

> ## 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 attributes, downtime reasons, and states

## How to Add Machine Attribute, Downtime Reasons, and States

*Configure your Machine Monitoring to easily create Machine Types*

This article will outline how to create centralized data for Machine Attributes, as well as Machine Downtime Reasons and Machine States. Make sure you've finished setting up your [OPC UA connector](https://support.tulip.co/docs/how-to-build-your-first-opc-ua-connector) before configuring these values.

In the Machine page, select the dropdown to get a list of the configuration options. Select States, Downtime Reasons, or Attributes to start adding!

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Machine%20Attributes%2C%20Downtime%20Reasons%2C%20and%20States_228785862.png)

## Machine States

States are used in OEE calculations as well as other Analytics. These can also be useful to track what State your machines are actively in throughout the day.

By default, the States: Running, Stopped, and Idle are included.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Machine%20Attributes%2C%20Downtime%20Reasons%2C%20and%20States_228789793.png)

To add new States, select the Create Machine State button in the top right of the page.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Machine%20Attributes%2C%20Downtime%20Reasons%2C%20and%20States_228790011.png)

The following modal will appear, which can be easily filled and saved as desired.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Machine%20Attributes%2C%20Downtime%20Reasons%2C%20and%20States_228790354.png)

Once added, the State will be added to the page, which serves as a library when configuring a Machine Type.

## Machine Downtime Reasons

In the Machine Downtime Reasons page, the following options are given by default:

- Changeover
- Maintenance
- Material
- No Operator
- On Break
- On Lunch
- Other
- Set up
- Team Meeting
- Tooling

Select Create Machine Downtime Reason to create a custom Downtime Reason.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Machine%20Attributes%2C%20Downtime%20Reasons%2C%20and%20States_228795981.png)

Add a Name and Color to the Reason, then click Create. This will add the Downtime Reason to the list to be used when setting up Machine Types.

## Machine Attributes

Machine Attributes are necessary to capture data coming from Machines. Machine Tags will be paired to these Attributes to be used in App logic and Machine Triggers.

Similar to the other two, Attributes can also be added to the respective page. Creating a new Attribute will give a modal prompting a name and a data type.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Machine%20Attributes%2C%20Downtime%20Reasons%2C%20and%20States_228798839.png)

Note: Make sure the Type matches to the data that the tag will need before creating.

Once you have created all the States, Downtime Reasons, and Attributes you are interested in, you are ready to move on to creating [Machine Types.](https://support.tulip.co/docs/how-to-set-up-machine-types)

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question!

**Attribute**

**Attributes**are properties. In Tulip, an attribute generally references a property of a machine. Attributes can be either set points or actuals.

*Ex. Cycle time, Spindle speed, Feed rate, ect.*

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

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

**Machine Attribute**

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

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

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