Ignition + Tulip Integration Guide *This guide walks you through how to integrate the Ignition Platform with Tulip Manufacturing Software. You will learn how to exchange data between the two platforms and how to provide a single pane of glass on the application by embedding one application into the other. * The guide provides detailed information on how to integrate these two platforms for a seamless experience for operators. Run Tulip in Ignition Perspective Both Ignition Perspective and Tulip are native HTML web applications. Tulip apps can run directly in Ignition Perspective using inline frames (iframe). Add Ignition’s Hostname/IP to Tulips Domain Allow List Tulip does not allow embedding in an iframe without explicit permission by adding the hostname/IP to the allow list. Login to your Tulip account and go to your account Settings. Select “Domain allowlist”. Add the URL for your Ignition server. The URL may be a

Introducing: The Composable MES Composability represents a paradigm shift in how manufacturing execution systems are architected, implemented, and maintained over time. Rather than relying on rigid, monolithic architectures, composability asserts that solutions should be built such that feature sets can be seamlessly combined and recombined into novel collections. The result is unparalleled flexibility, agility, innovation, and faster time-to-value. The Composable MES (cMES) App Suite is a foundational set of apps that make it easy to deploy a manufacturing execution system in your operation. These apps are built so that they can be configured to meet the exact requirements of your operation. Whether you use them as is, expand them, or subtly configure them to match your unique requirements, these apps are built to be fast to deploy and easy to adapt. The cMES apps are interconnected and work together with a common data model . The Common Data Model

To download the app, visit: Library Purpose This article provides an overview of how the Work Instructions Template is constructed and its intended purpose. Purpose of the Work Instructions Template The Work Instructions Template is designed to guide users through procedures in a task-by-task manner. Users can select an order and a specific product to work on, following step-by-step instructions. Upon completion, the finished product can be submitted for review. The application automatically stores critical process details, such as the status of the order material, the start of the process, and the responsible operator's name. Data Structure All instructions are stored in application variables . While the application does not utilize Tulip Tables, if used in conjunction with an order tracking or defect tracing application, the input fields for order ID and product name can easily be adapted to utilize interactive tables like the Order Materials

How To Create a Pareto Chart of Common Defects Here's how to create a Pareto Chart in Tulip. Tulip allows you to analyze defect data in real time, and across any time period- daily, weekly, monthly and more. But, if operators have been using Tulip apps for weeks or months, you will generate a large number of defect reports. You can use a "Pareto Chart" to quickly understand this data by instantly highlighting the most common defects. This guide will show you how to create a Pareto chart within the Analytics Builder. Before using this guide, you should understand the concept of " app completions because that is how data will be generated from the app. Structuring Your App Before using the Analytics Builder, you will likely want to use a single variable to track all possible defects within the app. This variable is commonly called "defect_name". You can

Overview Connect existing software systems with Tulip Tulip is an open platform designed to integrate seamlessly with your existing IT infrastructure. This integration is facilitated through Connector s . Connectors are a feature of Tulip that allows data exchange between HTTP API, MQTT, and SQL databases and Tulip. They are crucial for connecting to external servers and systems, including the Table API . Setting up a connector enables you to pull external information into your Tulip apps, streamlining your processes. Types of connectors HTTP - Access data from external APIs. MQTT - Write to your MQTT namespace. SQL - Access external databases outside of Tulip. To access connectors, hover over the Apps tab and select Connectors . On the Connectors page, you can view the status, description, and the last update time of your connectors. Hovering over the status pill provides additional information about each Environment ’s status. Each Connector can have multiple Connector Function s

Introduction These automations show AI agentic capabilities of Tulip, showcasing a defect management use case. We built two Tulip automations: one for summarizing defect records from the defects table and creating a daily email, another that gets triggered when a new defect record is created and will try to categorize it like a human engineer would in the Material Review Board application. It can change the disposition of the defect according to the category and send an email. If the automation cannot clearly determine the category then it sends a message to a supervisor to take a look in the MRB app. With the MRB app we can create different types of defects and save them to the table to see how the automations handle them. Setup Both automations use the new Prompt AI action. See release notes here . The Summarization automation uses the Tulip Table API as well to

Purpose Defect tracking is essential to the identification of root cause in nearly every manufacturing operation. Ditch those Excel sheets, paper forms, and manual data entry with a dedicated application to streamline and stabilize the data collection process. Tulip can support every part of the process for building out a robust defect tracking machine . Users can collect data in a dedicated (or integrated) app, stored to Tables , and analyzed with Analytics . Overview This Functional Example will cover the core concepts needed to understand how to approach Defect Tracking within Tulip. This documentation and the Apps associated with it aren't intended to be run in production, but rather as tools to teach all of the core concepts and approaches needed to achieve this use case. Explore the Content This documentation folder should give you enough information to understand. App Architecture Success starts with the right interfaces for your users. The

To download the app, visit: Library Introduction Salesforce is a cloud-based CRM software platform, used in applications varying from sales lead tracking to order and inventory management. Purpose This document details the Salesforce REST API Connector found on the Tulip Library. Once configured, these Connector Functions can be used to retreive, query, and modify Salesforce data from a Tulip App. API Documentation Documentation for the Salesforce REST API can be found here . Note that some Connector Functions included in this article accomplish queries using SOQL (Salesforce Object Query Language), the full syntax of which is documented here . API Variations Note: Salesforce supports a number of API across a variety of methods, the full list of which can be found here . This article and the Connectors to which it is related are built to use the Salesforce REST API. First Time Set-Up Permissions Warning Warning: generating the following values

To download the app, visit: Library Integrating with Microsoft's Graph API for Calendar Introduction Microsoft Calendar API allows the users to create, read and edit Microsoft calendar events with the right access set to their M365 accounts. The Goal of this connector is to integrate Tulip with Microsoft using Microsoft’s Graph API(v1.0) using HTTP Connectors & provide our customers with an out-of-box connector that can be imported into their instance. Purpose We are going to highlight different connector functions that can be built by doing HTTP calls to Microsoft’s Graph Api(v1.0) to interact with the Microsoft Calendar events to showcase various read and write actions on the calendar that could be leveraged for various use cases. API Doc Microsoft Graph API Documentation Pre-Requisites Create an account on Microsoft 365 & configure the OAuth 2.0 credentials in Microsoft Entra ID. Register API

Purpose Learn how to set up an external MQTT broker on Tulip Edge Devices Beginning with OS 50.1, Tulip Edge Devices have an external MQTT broker to which client devices can connect. Instructions Log into the Edge Device Portal . At the bottom of the "Network configuration" section, select the "MQTT Broker" option. Click "Enable", enter in a desired username and password, and hit "Save". Using the MQTT Broker with Node-RED To confirm the broker is available, we can use a Node-RED MQTT IN node. If Node-RED is off, turn it on and log in to the Node-RED editor. Add an MQTT node to your flow and edit the node. Click the pencil button to open the broker configuration and set "Server" to localhost . Click on the "Security" tab and enter the username and password configured for the broker. Click "Update" to save the settings. Click

In this walkthrough, you will: Display a message on a step Input a custom message Create a count of messages Document the date and time of the most recent message display In this walkthrough, you’ll learn the basics of apps by building multiple, functional app components. At the end of the exercises, you’ll have a Hello World app that will look like this: Exercise 1: Create a Hello World app In this exercise, you will create a simple app that displays a message from a button trigger. Create an app In the Apps tab, click Apps . Click + Create App in the top right corner. Name the app “Hello World - Example”. Optionally, you can add a description so other users know what this app is for. Click + Create . From the app details page, you can either click Edit in the top right corner, or click the Untitled Step name

How to use “On A Schedule or Timer” in Automations Learn how to schedule events with Automations. Note This event option is only available for Enterprise plans and above. What are Scheduled Events? In Automations, scheduled events are event that run at a known frequency (e.g. once an hour, once a day, twice a week) at a certain point in time (9:00 AM) in a certain timezone (EST, GMT). How to use Schedules in Automations? Go to Automations in the navigation bar and then click +Create Automation or edit an existing automation. This will open the Automations editor. Choose On A Schedule or Timer. Once selected, the side panel opens up which displays different options for the frequency of your event. You can set the frequency in hours, days, or months. For our more advanced users, the scheduling system is based on rrule. Schedule by Hours Users can

New Content Apps Nymi Overview and Unit Test Streamline Nymi integration in your productions Learn more Mobile Production Scorecard Track hourly production performance easily Learn more Shift Starter Meeting Conduct meetings with a structured key topic workflow Learn more Simple OEE Dashboard Start measuring station OEE with quickstart template Learn more Aras Integration Unit Test Assure connectivity to Aras PLM Learn more Machine Monitoring Dashboard Monitor machines, track status, and visualize performance across your facilities in real-time Learn more Microsoft Teams Unit Test View and send messages to channels in Teams with Microsoft Teams Connector Learn more Microsoft Outlook Unit Test View or send emails within your Tulip App with Microsoft Outlook Connector Learn more Microsoft Excel Unit Test Connect and pull data from your Excel with Microsoft Excel Connector Learn more Microsoft Calendar Unit Test View, create, update or delete calendar events from Tulip with Microsoft Calendar Connector

How To Manage Your Inventory Using Tables Use this guide to set up an inventory management system using Tables In this guide, you will learn... How to create a Table for your inventory How to add to that inventory via a Form Step in an app Note: This topic is featured in the " Build an Advanced Work Instructions App " course in Tulip University. Tulip's Tables feature allows you to control inventory via a no-code database. Within Tulip, you can manage inventory by... Updating the latest quantity of certain materials in your manufacturing process Deducting from inventory every time a product is completed or scrapped Sending warnings when a quantity falls below a certain amount This tutorial will show you how to create an inventory Table, and then update that Table in an app. In order to understand this tutorial, you should first read this overall guide to Tables

Tulip supports several different data types across the platform. These types are important to understand as they can have implications in how you store data, usability within Analytics , and how you convert between data types. List of data types The table below provides information about each data type including descriptions and supported areas, as well as any specific formats or limits. Type Description Format Limits Area Supported Boolean True or false True, false, yes, no Analytics, app variables, connector functions, machine activity fields, machine attributes, table fields Color Color values that can be used to set widget coloring dynamically rgb(0, 0, 0), rgba(0, 0, 0, 0), #FFFF00 App variables, machine activity fields, table fields Datetime Timestamp consisting of a date, time, and timestamp MM/DD/YYYY HH:MM:SS See also: custom datetime formats Analytics, app variables, connector functions, machine activity fields, table fields Enum Selection of predefined

identifies an expired token based on its expires_in attribute received in step 5 of the authentication flow. Services Not Using expires_in If the token's expiration time is not provided via the expires_in key, the "Default Expiration Time (seconds)" field in the authentication configuration will be used to automate token renewal. 2. Token Flow Attempt: Tulip initiates the token flow using the refresh_token grant type, replacing the grant type used in the initial authentication flow. 3. Token Validation: If a new token is obtained, Tulip stores it and proceeds to execute the user-requested connector function. If successful, data is provided to the Tulip app runtime. If the new token fails with an OAuth error, Tulip retries the process up to 5 times, reverting to step 1 each time. If the new token fails with any other error, an error is displayed in the player runtime

I/O Gateway Notice On November 1, 2021, Tulip will no longer sell I/O Gateway devices. Edge IO and Edge MC Devices are still available. Learn More Here's how to set up a new Tulip Gateway for the first time. Here's how to set up a Tulip I/O Gateway using the Gateway Portal. In order to set up a gateway, you need: To be an administrator of a Tulip account Google Chrome Power Outlet Wired Ethernet Connection The Tulip I/O Gateway box includes: Tulip I/O Gateway Wi-Fi USB dongle 24V Power Supply 3-foot Ethernet cord Connect the I/O Gateway to Power Plug in Wi-Fi USB Dongle into an available USB Port. On opposite side, plug in wires for power. Plug other end into a power outlet Verify two lights above the pins are on On USB side, verify green light

Learn how you can configure decimal precision for numbers shown in Analyses Availability This feature is available with the Universal Template in release r279 or later. To use number formatting, consider migrating analyses using other templates to the Universal Template. Overview In the Analytics Editor, number formatting lets you control how many decimal places are displayed for numeric values without affecting the stored data or calculations. You can configure this for each numeric field by opening the Data panel on the right side and clicking the (123) button next to the field. Number formatting is supported by all display types of the Universal Template, except the Slideshow. Example Below you can see an example how number formatting can be changed from the default to a customized state in a table visualization. Example Number 0.1 0.12345 0.123456789 0.123456789123456789 Default formatting By default, Tulip displays each value with

Streamline alerting and messaging with google chat connector -- Built by Bow&Stern Purpose The Google Chat Connector actively enables alerting and messaging to other teams outside of Tulip via Google Chat. Bow & Stern Contact For more information from Bow & Stern (Builder of the Connector), feel free to reach out at: Info@Bownsternps.com Setup Instructions The first step is to create a project and configure credentials. You can follow this guide to set up the Google Chat API (Just remember to use/add the Google Chat app in lieu of the Google Drive app and use the connection details provided below for the Chat API) – https://support.tulip.co/docs/google-drive-connector **You will also need to have a paid Google workspace subscription in order to access the Chat API with active spaces created to send and receive messages from. ** Tulip Connection Details The following information would need to

when the detector makes a prediction that is above the threshold you set earlier: You may also want to add an event when the detection end and clear the variable. Your running app should now show you the results of the custom model from the trigger: Conclusion Custom models enable you to run ML models on the edge in real-time to perform visual inspection tasks automatically. They can be used to replace or augment a manual inspection with a properly trained model. Since the models are running in the edge they incur no extra fees, and make for a faster, more private and secure operation in terms of data. Start using machine learning on Tulip today with Vision custom models. With a fast and simple setup these powerful models can save time and effort on your factory floor. Further Reading Use Azure customvision.ai with Tulip custom widgets for