Production Visibility Template

This article summarizes how the Production Visibility template is built and how the logged data is stored in a Tulip Table.

What purposes does a Production Visibility template serve?

The production visibility template allows the user to log Station activity events to a Table such as running and downtime events. It is also possible to specify the reason for downtime and log how many good and defective products were produced during the event.

Table used in the Template

The Tulip table used in the template is called Station Activity History. Each Record in the table is an event.

Fields of the Station Activity History table:

ID:
The unique identifier of the event. This is a text field generated by the application randomly

Hour block:
The hour in which the event took place. This is useful for creating hourly scorecards from the data stored in the table

Status:
“RUNNING” or “DOWN”

Downtime reason:
The reason for downtime (e.g. machine error). In case of events where the Status was RUNNING, this field should be empty.

Duration:
The duration of the event.

Station:
The station where the event occurred.

Actual:
Number of good parts produced during the event.

Target:
The budgeted amount of production for the applicable period (duration). This is calculated from the pre-defined production rate that you can set in the beginning of the production and throughout the duration of the event.

Defect:
Number of defective parts produced during the event

App structure

Summary diagram

Description of Steps

The Start Shift step is the first step of the application where you can start your shift.

On the Setting/Production step, the user can decide to set up the machine or start production immediately. The Set up button navigates you to the Setting in Progress step, whereas the Production button navigates you to the Select Product step.

On the Setting it Progress step the user has to select Finish setting up in order to log that the setup is done. The application then navigates to user back to the Setting/Production step so that they can choose to start production.

On the Select Product step, the user has to enter the product ID and they can change the default value of the production rate. Once the values are entered, they can to start production.

On the Production in Progress step, the Product ID and the time of production start are displayed for the operator. When production needs to be interrupted, the user must select the reason for the interruption, which signifies the end of the production event and the start of a downtime event. By clicking on Log output, the operator can log good and defective products.

If the user selects any of the downtime reasons on the Production in Progress step, the application navigates to the Production Suspended step. To end the downtime event the user has to click Continue production.

If the user selects Log output on the Production in Progress step, the application navigates to the Finish Production step. The user can type in the number of good parts and the number of defects manually. They can also use the buttons to increment or decrement the values by the numbers displayed. As soon as the two values are set, they can be logged into the table and the user can decide to continue the production of the same type of product or to go back to the Select Product page and choose another product to produce.