Checklist Functional Example

The guide walks you through how to understand the Checklist Functional Example, available in the Tulip Library

Purpose

This app walks the user through building a checklist application for use while on the production floor. It covers checklist set up, performing a checklist, and analyzing checklist results.

Setup

There is no set up needed. This app only uses Variables app-based data (i.e. Completion records). The variables are already configured. The app primarily has an educational goal, and it is not suitable to immediately deploy on the shop floor.

Copy and paste to your own configuration of the steps from the stepgroup "Functional Examples". Triggers; variables carry over to your own solution.

How it works

Run the app in the Tulip Player and learn how to build checklists for your shop floor. Each step is designed to educate and instruct the user on the various methods of configuring a checklist.

Introduction Steps

The introduction steps provide context for the logic and data records in the functional example steps.

1. Introduction
   The app flow transitions from question to question, with variables storing the responses. The user reviews the checklist after answering all of the questions and they choose to either accept or reject their responses. If saved, the responses will populate into the analyses in the very last step.

2. App Data
   All the responses from the questions in the checklist are collected in Completion records. They are immutable histories of any data entry action performed while running the app in the Player and saving the app data via Variables.

Functional Example Steps

1. Begin Checklist
   The Begin Checklist step shows a series of analyses above the Begin Checklist button, which transitions to the next step. The analyses are numbers pulled from the app's Completion data.

2. Question 1
   This step shows the checklist question above two buttons: Yes and No. To submit a response, simply select the appropriate button. Either a "Yes" or "No" response saves into the Variable labeled "Guards". Click Next to transition to the next question.

3. Question 2
   Question 2 follows a similar logic to the previous question; however, instead to two separate buttons, the response triggers via a Boolean checkbox. Clicking the box adds a check and therefore saves a "Yes" response into the "Clean Check" variable. To submit a "No" response, click the box twice to "uncheck" it. Click Next to transition to the next question.

3. Question 3
   This step builds off of Question 2, adding a series of checkboxes which each save responses into different variables: "Rotor", "Belts", "Fasteners", and "Gears". For this list, you can also click the Select All button to check every box rather than doing each one individually. Click Next to transition to the next question.

4. Question 4
   Question 4 mirrors Question 1 with the extra asset of a text Input Widget. With the question requiring a reponse if the "Machine Damage" variable response is "Yes", the user types a comment into the text box which saves into the "Damage to Machine" text variable. This text field will only save if the user selects the "Yes" button, so that the comment saves as necessary. Click Next to transition to the next question.

5. Question 5
   Question 5 is a series of buttons that act as a 1-5 scale. Each button saves its response into the "Electrical Cables" variable, noting the condition of the cables with a text input. Click Next to transition to the next step.

6. Review Checklist
   Before the responses save into the app's data, the user must review their checklist answers to ensure they want to submit. This page uses text boxes to label the variables, which display the response recently selected by the user. Selecting Submit completes the app, saving all data into completion records, and transitions to the Analysis step. Selecting Reject erases the responses and transitions back to the "Begin Checklist" step.

7. Analysis
   The Analysis step shows a dashboard of Analytics all derived from the completion data of the app. Numbers, charts, and graphs reveal common trends, rates of habits, and data insights that inform the state of the production floor.

Further Reading

• How to Complete an App
• How To Create And Use Variables
• Intro to Analytics Builder