--- title: "Machine Monitoring" slug: "machine-monitoring" status: "update" updated: 2025-12-19T21:38:28Z published: 2025-12-19T21:38:28Z canonical: "support.tulip.co/machine-monitoring" --- > ## 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 *Learn the basics of Machine monitoring in Tulip before learning how to set up your first machine.* [Embedded content](https://www.youtube.com/embed/Lmc75mjiZFI) **In this article, you will learn about:** - **The capabilities of the machine monitoring feature in Tulip** - **How to track machine data without setting up an app** The **Machines** page, within the Shop Floor tab, lets you manage your machine data in Tulip. ![Go to machines pages](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Go%20to%20machines%20pages.png) There are two ways to monitor machine data in Tulip: 1. **Without Apps:** By simply setting up an OPC UA Connector and connecting your OPC UA fields to atrributes in Tulip, you can begin tracking and analyzing data. 2. **Within Apps:** If you have to combine human-centric data (audits, machine inspections, maintenance history) with machine data in real-time, you will need to set up an app that can be run in the Tulip Player to combine the human data with machine data. Tulip can help you monitor one machine or hundreds of machines. You can track data across multiple machines under one category. ## Set up machine monitoring Here are the 7 steps needed to setup machine monitoring in Tulip: 1. **Set up an OPC UA** Connector on the "Machine Data Sources" 2. Create a Machine Type to organize your machines 3. Create an Attribute to organize data from multiple machines 4. Connect your machines to Tulip and map their data on the "Machine Library" page 5. Set up Machine Triggers to map Attributes to Machine States 6. Create an Analytic for your machine data (optional) 7. Update machine history from an app (optional) Read more about how to set up your first machine [here](/r230/docs/how-to-set-up-your-first-machine-1). ## Machines page See a list of all machines that are connected to Tulip. ![Machines page ex](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Machines%20page%20ex.png) Use the **Grid View** to get a visual overview of all current machines. In the example below, 4 out of 5 machines are offline. ![Machines grid view](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Machines%20grid%20view.png) Use the **Progress Bar** view to see the history of every machine over the past 3 hours. ![Machines progress view](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Machines%20progress%20view.png) Select a machine to view its details, activity, and configuration. ## Machine types Organize your machines by type. A Machine Type is a defined set of criterea to categorize similar machines. ![Machine types(2)](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Machine%20types%282%29.png) When you assign a machine type to a new machine, it assigns the configured states, downtime reasons, attributes and triggers. ![Machine types configuration.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Machine%20types%20configuration.png) Learn how to set up machine types [here](/r230/docs/set-up-machine-types). ### Machine attributes Define and manage all Attributes that can be used to organize machine data. Machine attributes are necessary to capture data coming from machines. ![Machine attributes](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Machine%20attributes.png) ### Activity fields The activity fields determine the data in a machine's activity table. ![Machine activity fields](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Machine%20activity%20fields.png) ### Downtime reasons Downtime reasons provide context for downtime events. Downtime reasons come default, but you can also create your own. ![Machine downtime reasons](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Machine%20downtime%20reasons.png) ### States States are used in analytics, such as OEE calcuations. These can also be useful to track what state your machines are actively in throughout the day. ![Machine states](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Machine%20states.png) ## Create analytics with machine data ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Intro%20to%20Machine%20Monitoring_195037915.png) Read about how to create analyses using machine data [here](/r230/docs/machine-data-analysis). ## Use machine data in apps Read about how to use machine data within your frontline operations apps [here](/r230/docs/how-to-use-machine-outputs-in-triggers). ## FAQ ### Can I use machine triggers and Automations on the same machine? A: Yes. Machine triggers execute first, then Automations. This is useful for hybrid scenarios where a machine trigger updates state and an automation writes to a Tulip table. ### How do I monitor machines 24/7 without Automations? A: Use machine triggers exclusively. They are included with the platform and run headless. However, machine triggers cannot write to Tulip tables or call connector functions. ### Can I copy machine types across instances (Development → Production)? A: Yes, with [Import and export configuration](/r230/docs/export-and-import-configuration-v2). You cannot export and import the Machine(s) nor Machine Type(s) directly. The Machine(s) and Machine type(s) gets exported and imported as part of a related app (in which the Machine is being used in some way). ### What happens if my OPC UA server goes offline? A: Tulip marks affected machines as "Offline". When the connection restores, machines return to their previous state (Running/Stopped) based on attribute values. OPC UA queues attribute values during downtime, so no data is lost. ### Can I use machine monitoring in GxP-validated environments? A: Yes. Machine triggers and Automations are deterministic and audit-logged. Include machine types and triggers in validation documentation (IQ/OQ) and use change control procedures before modifying production machine types. ### How do I handle time zones for multi-site deployments? A: Tulip stores all timestamps in UTC. Configure your Instance timezone in **Settings**. Machine data timestamps use the instance's timezone. For multi-timezone analytics, use timezone conversion expressions in analytics. ### Can I integrate Tulip machine data with external MES/ERP systems? A: Yes. Use Automations to write machine data to Tulip tables, then use connector functions to push data to external systems. Alternatively, external systems can pull data using Tulip table APIs. ## Further reading - [How To Build Your First OPC UA Connector](https://support.tulip.co/docs/how-to-build-your-first-opc-ua-connector) --- 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 solved a similar topic! **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. **Shop Floor** The area of the platform responsible for moving applications into production. Under the shop floor, you can manage **Stations**, **Edge Devices,** and the app publication details such as which **Version** is accessible to users, which **Devices** are connected to the app, and which **Interface (display device)** the app is run on. **Connectors** **Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions. - **HTTP Connectors** utilize HTTP API endpoints. - **SQL Connectors** can enable connectivity with certain SQL databases. - **MQTT Connectors** can connect to MQTT brokers for machine monitoring. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/connector.gif) **Tulip Player** **Tulip Player** is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser and allows increased IT controls. **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.* **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**. **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) **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* **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.