Learn the basics of Machine monitoring in Tulip before learning how to set up your first machine
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
Tulip uses the "Machines" page within the Shop Floor option in the Menu Bar to allow you to manage your machine data in Tulip.
There are two ways to monitor machine data in Tulip:
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.
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.
Here are the 7 steps needed to setup machine monitoring in Tulip:
Set up an OPC UA Connector on the "Machine Data Sources"
Create a Machine Type to organize your machines
Create an Attribute to organize data from multiple machines
Connect your machines to Tulip and map their data on the "Machine Library" page
Set up Machine Triggers to map Attributes to Machine States
Create an Analytic for your machine data (optional)
Update machine history from an app (optional)
Here's a quick tour of the capabilities of Tulip's Machine Monitoring feature.
Machine Library
See a list of all machines that are connected to Tulip.
Use the "Grid View" to get a visual overview of all current machines. In the example below, 4 out of 5 machines are offline.
Use the "Progress Bar" view to see the history of every machine over the past 3 hours.
Machine Types
Organize your Machines by type.
For each machine type, create custom states to determine the status of the machine.
Individual Machines
See the history of each individual machine over time.
Machine Attributes
See the list of all attributes that can be used to organize machine data.
Creating Analytics with Machine Data
Use this separate guide to see how to create custom analytics in the Analytics Builder.
Using Machine Data In Apps
Check out this separate guide to learn how to use machine data within your frontline operations apps.
You can also head to community.tulip.co to post your question or see if others have faced a similar question!
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 are how your Tulip apps can connect to other systems. Connectors can make API calls with HTTP Connectors, or pull data directly from SQL databases. Additionally OPC-UA Connectors can be used to retrieve Machine data.
Once pulled, data can be used throughout your applications.
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 the mechanism to do things in Tulip Apps. Store data, move users between Steps, Interface with hardware, Etc.
Triggers can be added to widgets, machines, devices, apps, and steps.
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.
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
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.
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.
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.
Was this article helpful?
Thank you for your feedback! Our team will get back to you