This Article summarizes how the Performance Visibility Scorecard application is structured and built.
What purpose does the Performance Visibility Scorecard application serve?
The application provides a simple solution for logging machine activity manually. The user can easily switch between the machine’s statuses and log good and bad parts during production.
The table used in the application is called Station Activity History. Each record in the table is a station activity event that has a status. When using the application, data is logged in this table. The user can view the analysis of the table’s data on the Analytics step.
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
On the Select Product step, the user has to enter the product ID and the production rate. If the values are entered it is possible to start production.
On the Main step, the user switch between production statuses and they can also log good parts and defects. If the selected status is DOWN the app navigates the user to the Change status to down step where they must select a downtime reason to proceed.
During a Machine Status Change, the app references a variable called No Target Statuses. Users can set the default value for this variable in the Variables - Default Value section of the app's side menu.
The importance of this variable lies in its function: if a status is included in this variable, the app will not log a target for the duration of that status period.
Currently, we have set it up so that the variable only contains the OFF status. This means that if we change the status of the machine to OFF and later we change it to a different status, the app will not calculate a target number for that downtime period.
The Analytics step can be reached from any of the other steps. The user can view analytics about the performance of the production.
- For managing performance across multiple stations, check out the centralized performance visibility scorecard
- For alternate designs, check out the hourly production scorecard