Here's a guide to the names of all parts of Tulip, Tulip Player, and Tulip Factory Kit.

Overall Tulip Platform

Tulip:  The interface used in Google Chrome where Tulip apps and analytics are created and edited.

Tulip Account: An individual instance of Tulip, with the URL pattern your_account.tulip.co

Tulip Player: The interface where individuals can test and run the Tulip apps built on the Tulip App Builder.

Tulip Factory Kit: An IoT Gateway with a set of pre-configured devices that you can deploy on your shop floor. You can also use third-party devices with the IoT Gateway to connect them to Tulip apps.

Tulip

The Menu Bar is the navigation at the top of all pages in Tulip.

Dashboards is where you go to display/edit analytics and create/update alerts associated with KPIs

Apps is where you create and edit manufacturing apps and Connector functions associated with them

Shop Floor is where you administer displays that are running the Tulip Player and their associated IoT devices

People is where you go to update and manage Tulip users

Help Menu: The question mark icon in the top right of the screen.

Tulip Player

Tulip Site Address: The name of your Tulip account in the URL (your_account.tulip.co)

Tulip Factory Kit

USB Wi-Fi Dongle: The small USB card that allows the Tulip IoT Gateway to connect to your local computer.

IoT Gateway: A gateway that allows you to use many types of devices in your Tulip Apps.

Gateway Portal: The page that you can access via the Gateway's Wi-Fi network to configure its settings.

Apps

App Builder: The tool that Tulip administrators use to create and edit manufacturing apps.

Apps List: The list on the left side of the screen in the Apps tab

App Summary View: The view that appears when you click on an app. It contains 5-6 tabs per app.


App Completion List:
A list of every time a given app has been completed or canceled. Separated by version.

Toolbar: The series of icons at the top of the App Builder

Widget: Any individual button, text or image that is created via the Toolbar.

Steps List: All of the existing steps in the app, on the left side of the App Builder

Context Pane: The menu on the right side of the App Builder with multiple tabs

Trigger Editor: The modal where you can create and edit Triggers

Shop Floor Dashboard: An interactive dashboard that is built in the App Builder.

Analytics

Analytics Builder: The tool that allows you to create your own Analyses from scratch.

Analysis: An individual data visualization that is created via the Analytics Builder

Analysis Template: One of the 7 pre-defined combinations of data from the Tulip App Builder

Chart: A way to display data within the pre-selected analysis template

Context Pane: The list of fields on the left side of the Analytics Builder

Field: Each individual component of an Analysis that you can edit

Shop Floor

Display: Any tablet, computer or PC that can run the Tulip Player

Device: Any tool that can collect data and feed it into Tulip, either via a connection to a Windows PC or an IoT Gateway

Context Pane: The menu on the right side of the screen that gives more detail on Devices and Displays and allows you to configure the settings for individual Stations

Station: A container that allows you to connect Devices and Displays and determine which apps can run on specific Displays

Machine: An individual machine that is connected to Tulip via an OPC/UA connector and managed on the Machines page.

Attribute: A field type used to organize individual fields from an OPC/UA server.

Tables

Table List: The list of tables that have been created by Tulip administrators 

Table: Similar to a table in a database or a spreadsheet. It contains many records, which are added when operators use apps.

Record: A single row of data within a Table

Field: An individual column in a table

Record Placeholder: An individual entry in the Records list that ties Trigger logic to a specific Table


Records List: A list of all record placeholders in a given app

Connectors

Function: An individual query that utilizes a Connector to speak to an external database and a Tulip App.

Did this answer your question?