Bug Fixes:

...

Downtime Pareto Updates:

...

Prevent the same filter from being picked twice (i.e. see comment from #1000 level1=jobFilter2&level2=jobFilter3&level3=jobFilter2)

...

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

...

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

...

1. 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.

2. 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).

3. 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

...

• 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 3^rd 2019, 06:00 – Nov 4^th, 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.

...

Downtime search function for Linesummary view

Goal:

• Line summary view will get a search bar at the top to allow users to filter downtimes displayed

Approach:

• when user types into the search bar, the search handler will update the splat.search with URI encoded string and update the url

• on render, the view will utilize the search.js with decoded splat search to pass the filtered downtimes to the children components. This will allow the children to be as simple and modular as possible.

Risks:

• the users want to be able to search through ALL downtimes and display only the top 5 of the filtered data. This is different from getting top 5 downtimes and then filtering through.

• Therefore this requires backend to return all downtimes.

• the decision need to be made to either get rid of TopCount function from backend completely or apply a default value and keep TopCount function.

• ignore capacity downtimes feature is kept and should be applied before applying the search commands

Notes:

• the users want the search to be shown up in the URL so they can share it with each other.

  • ex. https://qa7.shoplogix.com/whiteboard/#/linesummary/area/7/search=micro

• This will have the same interaction as any other splat settings with caching.

• when the user opens the new link with search splat, the search bar will not automatically show the search string / command. This is the current expected behaviour. If they want that to change, it will need a new enhancement request.

...

Line OEE calculation changes for line summary

Goal:

• Two linesummary queries currently just use the line machine's oee. It needs to be changed so that when the requests are made, it will use line oee calculations instead.

• in the returned data of api/linesummary/currentshift?areaid=2 also return total and scrap of the line.

Queries:

• api/linesummary/prevshifts

• api/linesummary/currentshift

Expected Output:

• oee of each shift data should use line calculation instead of line machine's oee

• oee of currentshift output should use line calculation instead of line machine's oee

• **Note as per standard JSON output values of 0 will not be outputted (this is also true for nulls)

Expected Output of scrap:

currentShift: {
  shiftName: “Day”,
  oee: 0.77,
  startDate: “20200220T070000.000“,
  endDate: “20200220T190000.000“,
  scrap: 1337,
  total: 9001
}

...

New Settings Options for LineSummary view

Goal:

• Adding the following UI settings to the linesummary view

• Apply layout data or not to the doughnut component

• Hide Goal gauge

• Goal targets

• Shift statistics from shiftpace view (Uptime, Remaining, Elapsed, and Production)

Approach:

• Mock up can be found in the epic's spec.

• Layout View option will lead to following behaviours

  • GRID: do not pass the layout data to doughnut component even if received from backend

  • Layout: same as current

  • Hide: skip rendering the doughnut component completely

• Hide Goal: just a boolean setting to skip rendering in the gauge. Leave empty space if hidden.

• Goal targets will be applied to the SummaryGauge component, which currently receives it's default goal target values from the store. Strip the default target values out of the store, and merge the target values from the setting / splat with the data from getCurrentShiftSummary() in the render function to create a new "dataset" prop object. This will leave the child component (SummaryGauge) untouched.

• Copy and Pasta SHIFT STATISTICS sections of the code from shiftpace view. Once the settings are done, passing the values to the children components will be done automatically due to splat passing that's already implemented.

Risk:

• when the doughnut is not rendered in, create an empty space equivalent to the space that the component would have taken. Follow up cards will be made to deal with the spacing.

• Use "Hide Goal" (same as other views) instead of "Hide OEE" (as stated in the spec) for consistency that can be dealt with translation function. Same goes to "Goal Target" instead of "OEE Target"

• dataset prop of SummaryGauge still require a percent value for the targets (which is omitted for this view). Include a default value of 1.

• Enabling extra data from SHIFT STATISTICS will make doughnut display even smaller text than before. This will be dealt with in the future.

...

Important Note on Scrap Edit