Interested? Reach out to support@tulip.co or the Chat in the bottom right and we will get you this application imported to your site.

Purpose

Many of the machines throughout the manufacturing industry communicate their data over the internet using machine tags. These tags represent various parameters or attributes that communicate their state. These could be spindle speeds, alarms, or many other data points. The Tulip platform is designed to work with these signals and let you use them in your applications to improve process visibility and control. This application is a template that you can use when connecting your first machine and is an attempt to share best practices for machine monitoring app development as well as introduces ways to expand the scope of the terminal to connect to other application structures such as andon management and work order tracking. Since every machine needs to be connected individually, this document will walk you through setting up your machine and connecting it to the application.

Prerequisites and Other refereces

This article describes how to configure the Machine Terminal. If you already have a machine connected to Tulip then you can keep reading below. However, if you are new to machine monitoring or would like more information on how to connect a machine to Tulip, please take a look at the material listed below. After that, come back and continue setting up the machine terminal!

Getting Started

Before we get into the installation of your machine, let’s take a look at how the application works once your machine is connected. The application is centered around a single screen which displays the terminal and presents multiple opportunities for the users to view machine status and interact.

App Structure

This app has a limited number of Steps as you can see below. The primary step is Machine Terminal. This is the starting point for viewing the status of your machine. From there you can select from a number of actions such as Log Defects, Log Parts or Add Note. Each of these actions have an app step within the Actions group.

Installation

Since this application relies on the output data from a machine, when the application is first loaded onto your instance there will need to be a number of connections made to make sure the analytics and widgets display properly.

Step 1 - Connect or Create Analytics

When first opening this app, the analytics on the Machine Terminal step may appear as shown below.

If you already have analytics built, choose Select from Existing and navigate to the desired chart. If not, you will need to create new ones. Beware: you cannot use the Create an Analysis option for machine analytics as of now. Instead you must go to Dashboards and choose Edit > Add Analysis.


This will bring up a window which will provide an option for creating a machine analytic. From there you can choose from several analytic templates specific for machines. We have chosen to start with single number analytics for OEE and its components, but feel free to choose whatever is most useful for you.

Step 2 - Configure Your Station

The machine terminal is an application and, as such, needs to be run on a Tulip station like any other application. It is also very important that the machine you are monitoring is assigned to the same station. Refer to How to Set Up a Station for more information on general station setup. To assign a machine to a station:

  • Navigate to the machine by going to Machines and clicking the machine you are configuring.
  • Navigate to the Configuration tab for the machine and the Machine Details section.
  • Change the Station to be the same station as the tablet of PC where you are running the Machine Terminal App.

Summary

At this point you have added the Machine Terminal to your Tulip Instance, configured the analytics and configured a Station. The app can now be used to monitor the state of your machine and collect feedback from operators. If you have any questions or issues, please contact Tulip Support via support@tulip.co or via the Live Chat menu in your Tulip instance.

Did this answer your question?