Version 1

Important general rules discussed in this document that everyone should be aware of when creating dashboards:

• [ReasonState] is the preferred metric when dealing with downtime/slow running/micro stoppage/etc. reasons. This means this is preferred over [Reason] metric.
  

• Users should avoid adding machine “activity-level” metrics to Dashboard-level filters. These include metrics like:

  • ReasonState

  • Scrap Reason

  • Reason Name

  • ReasonState Group

  • etc.

These metrics should be at the Widget-level in almost all cases.

• Safe/recommended metrics to add to Dashboard-level filters are anything not directly related to a machine’s “activity” (state, reason, scrap reason, etc.). Examples of safe Dashboard-level filters include:

  • Shift

  • Plant

  • Area

  • Machine Name

  • Job Name

  • Job Filter

  • etc.

Continuous Improvement Dashboard

Widget affected:

Previous incorrect:

Updated: filtered correctly for downtime state

FORMULA:

([Total Scheduled Hours], [ReasonState Type])

THEN: click on the blue [ReasonState Type] field > Filter > by only Downtime

Widget affected:

Previous incorrect:

Updated: filtered correctly for downtime state

FORMULA:

([Total Total Hours], [ReasonState Type])

THEN: click on the blue [ReasonState Type] field > Filter > by only Downtime

Widget affected:

Previous incorrect:

Updated: changed [Reason Group1] to [ReasonState Group1]

What does this mean?

• Have been informed that our customers prefer the behavior of ReasonState over Reason.

  • Reason = show only reasons

  • State = show only states

  • ReasonState = show reasons when available. When not available (operator did not enter a reason), then show the state

Widget affected:

Previous incorrect:

Updated:

Columns:

• ReasonState

• ReasonState Occurrences

• Total Scheduled Hours

• Total Hours

• We’ve identified certain use cases where dashboard-level filters may inadvertently cause “No Results” to display in some widgets. More details below.

Widget affected: DASHBOARD-LEVEL FILTERS

Updated:

• Removed anything related to either Reasons (ReasonState, Scrap Reason, Reason Group, etc.)

Rationale:

• The dashboards do not appear to filter well when there are Reason or State-type filters at dashboard filter level (scrap reasons, downtime reasons, state reasons, state, reasonstate, etc.)
  

• It is highly recommended that customers who need to filter by these should do it at widget-level
  

• Rule of thumb for deciding when to use Dashboard vs. Widget-level filters:

• Dashboard filters should stay limited to “anything not directly related to a machine’s recorded status/state/issues”

  • Examples of safe dashboard filters: Machine Name, Area, Plant, Shift, Calendar DateTime, Job Name, Job Filter x, etc.

• Widget filters are where you can better isolate your filtered data at machine’s “activity” level

  • Examples of safe widget filters: ReasonState, Scrap Reason, etc. along with any other filter (Date, Shift, etc. these are always safe)

Executive Dashboard

Widgets affected:

Previous incorrect: The following rows of widgets (left to right) existed:

Row 1:

• KPI Cards

Row 2:

• “Machine Type Pending” text field – incorrect label, not needed

• Bar chart of OEE at machine level – Machine level should not be this high up in dashboard

• OEE at plant level

Row 3:

• “Facilities” - a repeat of OEE at plant level

Row 4:

• “Facility Production” - bar chart of total production per plant

Row 5:

• “Facility Good vs. Scrap” – bar chart comparing good vs. scrap at plant level

Row 6:

• “Downtime Plant level” - bar chart comparing plant and total hours – Downtime filter missing

Updated: The following rows of widgets (left to right) now exist:

Row 1:

• KPI Cards

Row 2:

• “Facility OEE” - bar chart of OEE per plant

• “OEE Trends” - line chart of OEE, Perf, Avail, Qual %

Row 3:

• “Machine level OEE”

Row 4:

• “Production by Plant” - bar chart of total production per plant → includes total, good, scrap

• “Production by Machine” - bar chart of total production per machine→ includes total, good, scrap

Quality Dashboard

• It is highly advised that anything related directly to a machine-level activity (e..g. ReasonState, Scrap Reason, Scrap Group, etc.) should be at widget-level filters from now on, NOT dashboard level filters.

• Dashboard filters work very well with anything above the machine’s direct activity (e.g. Machine Name, Shift, Job, Job Filter, Plant, Area, Calendar DateTime, etc.)

Widget affected: dashboard filters

Previous incorrect: Scrap Reason (and in some versions, Reason Name) were present in dashboard-level filters

Updated: Removed all instances of “Reason”s

Production Combined Dashboard

Widgets affected: Production Summary Table

Previous incorrect: sum([Job Expected Runspeed]) is incorrect, should be [Average Job Rate]

Updated: Replaced metric with [Average Job Rate]

Widgets affected: Production Summary Table

Previous incorrect: sum([Total Production])/[Total Scheduled Hours], we need field for uptime hours

Updated: Replaced metric with SUM([Total Production])/[Total Uptime Hours]

Widgets affected: Job Summary Table

Previous incorrect: Currently, SUM([Job Cycle Factor]), should be Average job cycle factor.

Updated: AVG([Job Cycle Factor])