Purpose

The purpose of this application is to provide a very simple way for your team to record their activity as they work. This is a very simple way to get started tracking production in your facility using a single device. Within minutes of using this application you will have the ability to see who has worked on what, where, and for how long.

An overview video

How the Application is used

First, a user will walk up to the terminal and badge in. They will be prompted to enter in some information: What product are they working on, where, and what is the target rate of output. These values can be pulled from other sources or stored in Tulip tables if you would prefer. You may also choose to have your users input different information. Once the user begins their activity they can log out of the terminal.

Later on in the day, the user may finish the job or choose to log some output but continue working on the same product. To do this, all the user needs to do is enter their badge ID in and they will be prompted to enter production information. Below, the user elects to complete the activity.

You will notice, in the image above, that an expected output has been calculated based on the target rate that was entered earlier. We've also logged a duration for the activity.

How it works

There are only two steps in this application: one for when the user is creating a new record and another for when they are returning to update their activity.

When a user begins a new activity, we create a record in the *Status History table. The ID of this record is a randomly generated string. We record information into the table: Time started, Station/Location, User, Product, and Target Rate. We also set the status field of the record to "RUNNING".

After this record is created, we store the ID of the record above into the users table so that we can retrieve the activity record when the user returns to the terminal.

The next time the user logs into the terminal, we check this field and if there is anything in it, we load the corresponding record and prompt the user to enter in production information. At this point we calculate how much time has passed and what their target should be. Any information entered in by the user will be stored to this record.

If the user decides to Update and continue the activity, they will create a new activity record with the same product, location, and target rate. Essentially, every time the user enters production information they will be adding a new record to the table.

This table can then be used for all sorts of dashboards and analytics to provide improved production visibility.

Did this answer your question?