Performance Visibility Dashboard
  • 15 Jan 2024
  • 3 Minutes to read
  • Contributors

Performance Visibility Dashboard


Article Summary

To download the app, visit: Library

This article explains the analytics of the Production Visibility Dashboard and summarizes how they are built.

The Production Visibility Dashboard visualizes data logged on the shop floor. The data is stored in Tulip Tables and contains crucial information about the production, such as up and downtime events or the number of products produced.

Tables Used

The Production Visibility Dashboard uses two Tulip Tables. The first is called Station Activity History. All the records in this table are events with a status that can be either RUNNING, OFF, or DOWN. Downtime events can also have a reason for downtime. For each station activity event, there’s a target amount of good products produced and an actual amount of good and defective parts. The station and the user are also saved in the table.

The second table used in the analytics of the production visibility dashboard is the Stations table. In the table, each record is a station and the fields contain information about the station's current state such as the station's status or the product currently produced there.

Fields of Station Activity History:

ID: the unique identifier of each event
Hour Block: the hour where the event occurred, can be used to create hourly scorecards
Status: the status of the event e.g.: RUNNING, DOWN, OFF
Downtime reason: if the status of the event is DOWN, the user can select the reason for the downtime which will be stored in the downtime reason field of the record
Duration: the time interval of the event
Station: the station on the shop floor where the event occurred
Actual: number of good parts produced during the event
Target: a target number of products that is calculated automatically from the duration and the event and the manually predefined production rate
Defects: number of bad parts produced during the event
Product ID: the unique identifier for the product type made during the event

Fields of Stations:

ID: the unique name of the workstation
Status: the current status of the station e.g.: RUNNING
Current operator: the operator working at the station (the one who logs in to the app to log events)
Status color: the color of the current status (this is not additional information, but helps the visual representation in the application)
Current product ID: the ID of the product that is currently produced by the station

Analytics

There are six analytics in the dashboard. These analyses show typical examples of production visibility charts.

Daily status distribution

On this chart, the user can see the distribution of the different station statuses of all days.

Table: This analysis is based on the Station Activity History Table
Template: One Operation
Display as: Stack Column Bar
X-axis: Date Created grouped by “day”
Y-axis: Sum of Durations
Compare by: Status

Downtime reasons Pareto

On this chart, the user can view the number of downtime events by downtime reasons, so that it is easy to decide which are the most common reasons for downtime.

Table: This analysis is based on the Station Activity History Table
Template: One Operation
Display as: Pareto Chart
X-axis: Downtime reason
Y-axis: Count where true: Status equals DOWN

Uptime percentage

On this chart, the user can see how much of the station's time was spent running.

Table: This analysis is based on the Station Activity History Table
Template: Single number
The value is generated by an expression that divides the sum of all the durations of the Running events by the sum of the duration of all the events that are not in OFF status.

First pass yield

This chart measures quality units produced as a percentage of the total units that began the process.
Table: This analysis is based on the Station Activity History Table
Template: Single number
The value is generated by an expression that divides the sum of the actual number of good products produced by the number of all the products (good products or defects).

Station statuses

On this chart, the user can view the current status of all stations in table format

Table: This analysis is based on the Stations table
Template: Table
Operations: ID and Status

Running time of stations

On this donut chart, the user can compare the total running time of the stations.

Table: This analysis is based on the Station Activity History Table
Template: One Operation
Display as: Donut Chart
X-axis: Stations
Y-axis: An expression that sums the duration of RUNNING events.


Was this article helpful?