---
title: "Library App Template"
slug: "work-instructions-example-app"
updated: 2024-04-11T14:44:39Z
published: 2024-04-11T14:44:39Z
canonical: "support.tulip.co/work-instructions-example-app"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Work Instructions Example

## Work Instructions Example

*A simple example of how you can use work instructions to guide workers and capture data*

[Video for "VID_Work_Instructions_Example_2023_1920x1080.mp4"](https://tulip.widen.net/view/video/l1arcbpnj6/VID_Work_Instructions_Example_2023_1920x1080.mp4?u=dtggv3)

### Purpose

This application is meant to provide an example of a simple, static work instruction. Static work instructions operate in the same way each time that they run and do not change their content depending on the product selected.

### Setup

There is no setup required for this application, as it does not use Tables and all content required to run the application is built into its logic and design.

### How it works

Users enter in (or scan) a work order number. They then begin the operation of assembling a rotor (which is an example assembly item). This first screen also displays performance metrics using Analytics. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28218%29.png)

To begin the order, the user must enter Lot number information for the components that are going into the assembly. There are custom widgets next to each input which give the user visual feedback. In this example, lot numbers must be 5 characters long. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28219%29.png)

After entering in Lot information, the app presents the user with step-by-step instructions. The user can click the next/previous button or simply click on the bottom row of images to skip to a specific assembly step.

![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28220%29.png)

On the final step, the user may begin logging completed units. There is logic to prevent the user from signing off the order until all units are complete, as well as preventing the user from logging more units than are required. The user can also log defects from any step in the assembly. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28222%29.png)

Once the order is complete, the user is prompted to review the production record and provide an Electronic Signature. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28223%29.png)

All of the data gathered in this application is stored in Completion data.

### Other Features

**Defect logging** The user can log defects by selecting the component with the issue and declaring a quantity and reason. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28224%29.png)

**Andon** The user can press the andon button which may be used to alert support staff that the area needs assistance and production has stopped. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28225%29.png)

**Tulip Tables**

**Tulip Tables**are a global location to store your production data. Tables are made up of Records (rows). A single can be accessed from multiple apps or stations at the same time.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Tulip%20Tables%20Overview%20-%20Feature%20Overview.gif)

**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.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-1662410510869.png)

**Electronic Signatures**

In regulated environments (GxP) getting a user signature to the accuracy of data is critical for process validation. The **E-Sig Widget**allows users to collect user signatures along with associated metadata.

**App Completion**

**App Completions**are a mechanism to store immutable data from a Tulip app. When an app is completed, all **Variable's**current values will be stored in the app completions tab.****This completion data can be analyzed in **Analytics.**

By default, after a Completion users will be brought back to the **Begin Screen**of your application. This behavior can be adjusted with other **Transition**types.