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

The Work Instruction Configurator is used to define the content for all work instructions. It allows to create tasks, procedures and routings and link them together. (A procedure will contain one or many tasks and a routing will contain one or main procedures.) Using this app, you build the data backbone of your DWI bundle.

General Overview

This bundle enables users to take advantage of a sophisticated table structure which organizes work instruction content (tasks) into step-by-step instructions (procedures) which are called upon in a sequence of different stations (routings). Users define the content they’d like to display and can assign it to any number of products whose manufacturing process can then be planned and tracked as jobs/work orders.

The Work Instruction Configurator is used to define the content for all work instructions. It allows to create tasks, procedures and routings and link them together. (A procedure will contain one or many tasks and a routing will contain one or main procedures.) Using this app, you build the data backbone of your DWI bundle.

The Job and Product Manager enables you to describe the products you manufacture within Tulip and link them to one of the routings you configured. You can also change a product to use a different routing if your current operational requirements lead to the need to do so. Additionally, this app is the tool with which you create now jobs for manufacturing a product. If you want to do this automatically based on input from another system (i.e. your ERP) please contact us to discuss the options.

The Operator Terminal is central interface to your operators on the shop floor. After scanning a jobID, it will guide the operator through the steps you have defined in the configurator for each product based on the routing (and therefore the linked procedures and tasks). The system will automatically collect data on time spent per task, procedure and routing. It also allows to collect pause and stoppage times based on your operators' input. This will allow you to build analyses to get detailed insights into throughput times and their elements. You can also include issue reporting into the system to collect insights on the main drivers of downtime. The system will in addition support correct routing of any job through your operations by providing routing instructions to operators and prevent jobs to be started at the wrong station.

App Names: Work Instruction Configurator, Job and Product Manager, Operator Terminal

Benefits:

  • Flexible creation and updating of multi-station work instructions
  • Automatic capturing of detailed throughput time data
  • Support of job routing on the shop floor

Features:

  • “Mix&Match” approach for tasks, procedures and routings
  • Integrated job manager to enable immediate deployment
  • Preconfigured for barcode scanner use

Installation Guide

The Digital Work Instruction only requires minor setup to work on your instance. There are two steps:

  1. Setting up two Table API functions within your Tulip instance
  2. Creating the stations you want to use the DWI bundle on in the Tulip Shopfloor as well as the *Stations table.

Setting up the Table API

The following steps are required to setup up the Table API functions corrects:

  1. Create a table API bot following the “Adding an API” instructions on this support page. Make sure to note down your credentials!
  2. Go to the “Connectors” section within your instance by clicking on “App” (top left) and the “Connectors”.
  3. Click on the “Table API” connector.
  4. Click on the connector configuration on the left (see below).


5. Select “Cloud Connector Host” in the “Running On” field. (If you are using an on-prem installation, please contact the Tulip Support.) Enter your instance URL in the “Host” field. (Please make sure to enter it in the format <my-instance-name>.tulip.co - do not add any additional characters like https or /)

Then click on “Edit Headers”.

6. Select “Basic Auth” in the Authentication section. Then enter the API key you received when setting up the bot as the Username and the secret as the password. You do not need to enter the Auth Header anywhere.


7. Click “Back”, then “Test” and then “Save”. If the test is not passed, please make sure you entered all data correctly.

Setting up your stations

The DWI bundle needs to know which stations the Work Instruction Terminal app will be running on. For this, those stations need to be added as a record to the *Stations table with the exact same name as they have in the “Shopfloor => Stations” section of Tulip.

  1. Go to the Stations section of Tulip and create the stations you want to use the WI Terminal app on. More information on how to do this can be found here.
  2. For each station, create a record in the *Stations table, using the same name you gave the station. You do not need to add any additional information to the table manually. All additional data will be automatically populated by the apps as needed.


Hint: If you have multiple stations that serve an identical purpose in your operations, you can combine those into a station group. Just add an additional record which has a group name of your choice as the ID and add the names of the relevant stations separated by a pipe (“|”) into the “Stations in group” field. Station groups will be available to be selected for procedures the same way stations are.

Now you have successfully set up the DWI bundle on your instance. The next step will be to create your tasks, procedures and routings using the WI configurator and creating products and jobs in the Job and Product Manager. After this you are ready to use your newly created WIs in production.

Hint: Make sure that the Tulip player at each station is assigned to the correct Tulip station.

Did this answer your question?