...
| Info |
|---|
Closed The issue is not reproducible |
...
PNE-670 - Plant Meeting values are not matching Shift Line
Description
Plant Meeting Cycle, Expected Production and values in Micro Stoppage and other states other then Running are not matching with Shift Line
| Tip |
|---|
Fixed QA tested and no longer reproducible after code fix |
...
Downtime Pareto Updates:
Prevent the same filter from being picked twice (i.e. see comment from #1000 level1=jobFilter2&level2=jobFilter3&level3=jobFilter2)
Fix for occurrences/durations for states shown with no reasons (i.e. Idle, Slow Running, Micro Stoppage, etc...)
Setup Exceeded should be shown (would be shown when this state has occurred in the same places Setup is shown in Pareto)
No Job in the hour, the respond is blank → should be ‘No Job Recorded’
Not showing reason for part of the hour where there is no job
...
The ability to select which lines to show or hide under the plant view since some lines, due to complexity, are configured in SLX but data is not used for site consolidation.
For multi-category big plants (i.e. Curitiba) provide the ability to see lines based upon individual category. Possibly with a selection option (i.e. plants within a plant).
Settings to configure Line specific & KPI specific targets for each gauge for example Line 1 targets for GE gauge R-Y-G ->60%-70%-75% vs. Line 2 targets for GE gauge R-Y-G ->70%-80%-85%. Similar ability for other gauges on this view such as Rejects/Scrap.
Summary of Deliverables
Phase 1 Deliverable Functionality | Phase 2 Deliverable Functionality |
All lines within an area will be displayed as specified in mock-ups below. View will include GE and Reject gauges | The ability to select which lines are shown and hidden. (cross product) |
| See multiple categories of plants if they exist within the larger plant. (need to double check functionality, weighting?, rollup metrics?) |
Gauge targets configurable for the overall view (not line specific). | Line specific targets for each gauge. (cross product, to confirm just line specific, not job specific?) |
...
The scope states that there will be one report per server. A server can host one or many plants, and although it is implied, can you please ensure that the reporting will allow reporting by plant and 'plant within a plant' etc.?
ADD EXAMPLE
On the Functional Requirements screenshot for the Plant Level Line View, the header shows E4 CDM – Nov 3rd 2019, 06:00 – Nov 4th, 06:00. would this show the plant and or 'plant within a plant' rather than a line?
...
Correction of Line OEE Unit Conversion and Cycle Factor Issues
Unit conversion - full stack
the counts from the EOL machines and the rates from the BN machine are not being converted to line units. The issue with this is that the base units for most BN machines is something like cookies and the base units for EOL machines are usually cases, pallets, bags, etc. So you'd need to convert them to line units which will always be a weight (KG or LBS) this way you're comparing weight to weight in the numerator and denominator of the shiftline view.
Cycle factor respected if job from bottleneck is taken from the past
In this case if the job on the BN exists outside of the query period, the job is still stitched forward and the rate is used at the correct intersection point but the cycle factor of that job will not be pulled into shift line. Ideally it would be pulled in so the rate matches that of the BN machine.
...