Overview
The primary purpose for this dashboard is to be on an overhead display so anyone at a site can see how a line has been running for that shift. As this display is designed to be viewed from far away and left on a screen unattended it does not have any drill-down functionality. This display is designed to complement the Operator Console.
Who: I am a leader or supervisor managing frontline employees, I spend most of my day on the shop floor assisting wherever I am needed most. When I am away from my desk it is difficult for me to see how my lines are performing. With this Lineside Display I can see from a distance how the shift has been going and see if we are winning or losing. This allows me to utilize my time where it is most effective.
You'll find this feature under Dashboards in the left hand menu.
The filter for Lines can be found at the top of the page to the right and the Line description is listed at the top center.
'Line Running' - is the default tile shown when there are no “down” dispatches open against machines on the line. The counter shows how long since the last “down” dispatch was closed. When the Line is has a down impacting Dispatch against it, the Dispatch Type Code will be listed along with a timer for how long that Dispatch has been open. The Tile will be colored based on the Dispatch Type color indicated in Setup.
Target - Will match OC, comes from pitch data. Target will include the entire shift and uses the LCT on the Order or Table. It will account for downtime. Note: If there is no order assigned to the line and no cycle times set up, the target will read '0'.
OR
Demand - Includes the entire shift demand and uses the LCT on the order or Table. It will NOT account for downtime.
Actuals - Will Match OC, starts at 0 for the shift and counts up
Efficiency - or Theoretical Efficiency = (Target * % shift completed)/ actual
This will change colors according to Theoretical Efficiency settings for the line. The calculation uses a percentage of the shift that is complete. Note: This is different from the Op Portal where the metric is prorated and uses Planned Minutes/ Ideal Cycle Time. See Example below for calculation data.
Shift Downtime - Cumulative downtime for that shift, looks only at down impacting Dispatches
EXAMPLE:
In the screenshot above Line 54 - AQPC has been without a “down” dispatch for 2 hours 25 minutes and 16 seconds. The total downtime for the line on this current shift is 12 minutes, and 17 Seconds.
The efficiency is calculated like this, let’s say we are 60% of the way through the shift.
- (Target*% shift completed)/(actual) =5400*60%/3136 =96.7%
Note: Efficiency does not take into account production time missed for downtime.