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.
99% of customers will ever only use filters at Dashboard or Widget levels. However, there is technically a way to add a filter directly on a formula within the Formula Editor. SLX development team already built out all common formulas and they are now Saved Formulas. Many of these Saved Formulas use filters directly
Table of contents:
General changes (new formulas etc.)
Dashboard changes
Continuous Improvement Dashboard
| Tip |
|---|
Fixed formula: Total Scheduled Downtime Hours |
Widget affected:
...
Previous incorrect:
...
Updated: filtered correctly for downtime state
...
| Code Block |
|---|
([Total Scheduled Hours], [ReasonState Type]) |
THEN: click on the blue [ReasonState Type] field > Filter > by only Downtime
...
| Tip |
|---|
Fixed formula: Total Downtime Hours |
Widget affected:
...
Previous incorrect:
...
Updated: filtered correctly for downtime state
...
| Code Block |
|---|
([Total Total Hours], [ReasonState Type]) |
THEN: click on the blue [ReasonState Type] field > Filter > by only Downtime
...
| Tip |
|---|
Updated metric: ReasonState Group |
Widget affected:
...
Previous incorrect:
...
Updated: changed [Reason Group1] to [ReasonState Group1]
...
| Tip |
|---|
Updated table: fixed columns that were not accurate |
Widget affected:
...
Previous incorrect:
...
Updated:
...
Columns:
ReasonState
ReasonState Occurrences
Total Scheduled Hours
Total Hours
...
Widget affected: DASHBOARD-LEVEL FILTERS
...
Updated:
Removed anything related to either Reasons (ReasonState, Scrap Reason, Reason Group, etc.)
...