Page Comparison

PNE-1149

https://slxdev.atlassian.net/browse/PNE-1149

Should return the list of machines states. Instead it only includes active states.

This blocks parts of https://slxdev.atlassian.net/browse/PNE-860#icft=PNE-860 involving inactive machine states.

PNE-1136

https://slxdev.atlassian.net/browse/PNE-1136

When grouped only by area occurrences and duration are correct:

https://qatesting.shoplogix.com/web/api/export/summary?Start=20200729T080000&End=20200729T090000&metrics=Reasons&groupBy=area,&areas=7&format=xml

When additionally grouped by ShiftName, ShiftInstance or JobName, occurrences and duration are incorrect:
https://qatesting.shoplogix.com/web/api/export/summary?Start=20200729T080000&End=20200729T090000&metrics=Reasons&groupBy=area,shiftname&areas=7&format=xml
https://qatesting.shoplogix.com/web/api/export/summary?Start=20200729T080000&End=20200729T090000&metrics=Reasons&groupBy=area,shiftinstance&areas=7&format=xml
https://qatesting.shoplogix.com/web/api/export/summary?Start=20200729T080000&End=20200729T090000&metrics=Reasons&groupBy=area,jobname&areas=7&format=xml

When grouped by AreaGroupRoot occurrences and duration are correct:
https://qatesting.shoplogix.com/web/api/export/summary?Start=20200729T080000&End=20200729T090000&metrics=Reasons&groupBy=area,&areaGroupRoot=7&format=xml

When additionally grouped by ShiftName, ShiftInstance or JobName, occurrences and duration are incorrect:
https://qatesting.shoplogix.com/web/api/export/summary?Start=20200729T080000&End=20200729T090000&metrics=Reasons&groupBy=area,shiftname&areaGroupRoot=7&format=xml
https://qatesting.shoplogix.com/web/api/export/summary?Start=20200729T080000&End=20200729T090000&metrics=Reasons&groupBy=area,shiftinstance&areaGroupRoot=7&format=xml
https://qatesting.shoplogix.com/web/api/export/summary?Start=20200729T080000&End=20200729T090000&metrics=Reasons&groupBy=area,jobname&areaGroupRoot=7&format=xml

Additional example:

https://qatesting.shoplogix.com/Web/Api/Export/Summary?start=20200806T150000000&end=20200807T150000000&areaGroupRoot=11&groupby=area,shiftInstance&metrics=uptimeHours,uptimeSeconds,downtimeHours,downtimeSeconds,setupHours,setupSeconds,total,scrap,oee,oeeC,availability,performance,performanceC,quality,qualityC,capacity,cycleTimeSeconds,jobs,subJobs,scrapReasons,states,reasons,stateReasons,comments,adoption

For Shift Instance = Afternoon 2020-08-06 15:15:00 the reason REFRIG UNIT COMPRESSOR BREAKER OFF FAULT has a duration of 32 hours even though the request time frame is only 24 hours and the reason only occurs on a single machine.

PNE-1087

https://slxdev.atlassian.net/browse/PNE-1087

Steps to reproduce:

1. On qatesting server, select Test_Machine_AD machine > Hourly

2. Select Create Page icon in upper right corner > Select Department and enter Message > Submit (the Page is displayed in the banner)

3. Select Palo Alto plant > Paging

Expected behavior: The page is displayed in Paging List (under Pending)
Actual behavior: The page is not displayed in Paging List

PNE-1046

https://slxdev.atlassian.net/browse/PNE-1046

OEE is incorrect and changing when changing units in Perioddetail

Perioddetail:
https://qatesting.shoplogix.com/whiteboard/#/perioddetail/E570F0B2-2E93-92ED-9CAE-AD171B401DFA/start/2020-05-26T09:00:00-04:00/end/2020-05-26T10:00:00-04:00/bucket/60/cycle=5&timeMetric=0&units=3

Shifthours:
https://qatesting.shoplogix.com/whiteboard/#/shifthours/E570F0B2-2E93-92ED-9CAE-AD171B401DFA/start/20200526T070000.000/gauge1=1&gauge2=8&gauge3=6&timeMetric=0&overCycling=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&cycle=5&cycleDP=1&cycleTOL=0&gaugeTOL=0&units=3

Hour 3 (09:00=10:00)

Productionsummary:
https://qatesting.shoplogix.com/whiteboard/#/productionsummary/E570F0B2-2E93-92ED-9CAE-AD171B401DFA/start/2020-05-26T09:00:00-04:00/end/2020-05-26T10:00:00-04:00/bucket/60/gauge1=2&gauge2=8&gauge3=3&timeMetric=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&cycle=5&cycleDP=1&gaugeTOL=0&units=3&cycleTOL=0

OEE Waterfall:
https://qatesting.shoplogix.com/whiteboard/#/oeewaterfall/machine/E570F0B2-2E93-92ED-9CAE-AD171B401DFA/start/20200526T090000.000/end/20200526T100000.000/yesoee=true

Expected behavior: OEE should match on different views.

Note: Before starting, check with Product team if OEE gauge in perioddetail should show OEE or OEEc.

PNE-927

https://slxdev.atlassian.net/browse/PNE-927

Issue # 1

As per https://slxdev.atlassian.net/browse/CS-760 Production Summary comments should reflect Shift Hours, however that is not a case.
Steps to reproduce are in a video https://www.loom.com/share/00d31125e4114bc4b43a05289df0b681 up until 2:09.
In addition, need a clarification if there is a limit of displayed comments within an hour in Production Summary.

Issue # 2
Comments are duplicated when changing a screen resolution.
Reproducible on saas113 (original URL from https://slxdev.atlassian.net/browse/CS-760#icft=CS-760).
https://saas113.shoplogix.com/whiteboard/#/productionsummary/72E1868A-E681-BB40-F5BB-81943805CB0B/start/2020-01-24T06:00:00+01:00/end/2020-01-25T06:00:00+01:00/bucket/60/gauge1=2&gauge2=8&gauge3=6&timeMetric=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&cycleDP=1&cycleTOL=0&gaugeTOL=0

Steps to reproduce are in the video https://www.loom.com/share/00d31125e4114bc4b43a05289df0b681 as of 2:10.
You can also reproduce it by minimizing, maximizing and restoring the window.

CS-3436

https://slxdev.atlassian.net/browse/CS-3436

Previously, in the Saas5 server, the time zone was assigned to all the machines (Watts Company) the time zone America / Santiago that is currently in UTC -4 for some reason our system is seeing it in UTC -3, which means that the production data is displayed out of phase one hour later. This company urgently needs to obtain the data in real time.

Sample URL

https://saas5.shoplogix.com/

CS-3425

https://slxdev.atlassian.net/browse/CS-3425

[Site]: BaddiQA

[Issue]: While validating new version on the BaddiQA server we found “No demand” functionality is not behaving correctly.
Even if the machine is into no production for more than shift+2 hours, it does not flip to no demand state.

Eg: https://mdlz-baddiqa.shoplogix.com/whiteboard/#/perioddetail/F34B35A4-5C20-4E7B-D507-81E53A4C5AD2/start/20200809T220000.000/end/20200809T230000.000/bucket/5/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1

Apart from the current feature validation, we were also testing, SKU with CF=0 and it seems instead of blocking all the counts, the goods were recorded as excess good which is not the case for the current version on prod server.

Eg: https://mdlz-baddiqa.shoplogix.com/whiteboard/#/perioddetail/F34B35A4-5C20-4E7B-D507-81E53A4C5AD2/start/20200801T220000.000/end/20200801T230000.000/bucket/5/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1

CS-3034

https://slxdev.atlassian.net/browse/CS-3034

System has a large number of messages

I do not seem to be able to delete them

I cannot dismiss them either.

Sample URL

https://saas48.shoplogix.com/whiteboard/#/shifthours/25E5D1F4-F13E-36F3-3D57-FC1CCE67DE9E/cycleDP=1&cycleTOL=0&gaugeTOL=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&target=NaN%2CNaN%2CNaN&rotatejobs=true&gauge1=3&gauge2=8&gauge3=0&timeMetric=0&overCycling=0&

CS-2914

https://slxdev.atlassian.net/browse/CS-2914

Hi,

You could check the Quality module, when starting a new Job with the same name as the previous job, the generation of checks stops.

Following to be handled by NFR
In the client we have already manual measurement checks but in the SPC Whiteboard or Job quality SPC of flash, they are not generating information or graphics. Attached images.

Thanks and regards.

Edit: Joseph Kingry (Unlicensed) breaking apart two parts of this issue.

Sample URL

https://saas102.shoplogix.com/ https://tecnova.shoplogix.com/whiteboard/#/perioddetail/XMLCN_Tecnova1/start/2020-07-02T08:00:00.000/end/2020-07-02T16:00:00.000/bucket/10/quality=true&timeMetric=0 https://tecnova.shoplogix.com/whiteboard/#/perioddetail/XMLCN_Tecnova2/start/2020-07-02T08:00:00.000/end/2020-07-02T16:00:00.000/bucket/15/quality=true&timeMetric=0 https://tecnova.shoplogix.com/whiteboard/v3/#/qualityaudit/machine/XMLCN_Tecnova1/start/20200701T000000.000/end/20200703T000000.000 https://tecnova.shoplogix.com/whiteboard/v3/#/qualityaudit/machine/XMLCN_Tecnova2/start/20200701T000000.000/end/20200704T000000.000 https://tecnova.shoplogix.com/whiteboard/v3/#/qualityanalysis/machine/XMLCN_Tecnova1/start/20200701T000000.000/end/20200703T000000.000 https://tecnova.shoplogix.com/quality/

CS-2678

https://slxdev.atlassian.net/browse/CS-2678

There is inconstant delivery of comments across views. This was noticed by Timothy Goodwin of Kamtek.

Sample URL

https://saas16.shoplogix.com/whiteboard/#/productionsummary/AE5A13C7-A5F5-909C-2C5A-F3EC6EF2045B/start/2020-06-16T06:10:00-04:00/end/2020-06-16T14:10:00-04:00/gauge1=2&gauge2=8&gauge3=6&timeMetric=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&cycleDP=1&cycleTOL=0&gaugeTOL=0 https://saas16.shoplogix.com/whiteboard/#/shifthours/AE5A13C7-A5F5-909C-2C5A-F3EC6EF2045B/start/20200617T072835.000/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1 https://saas16.shoplogix.com/whiteboard/#/opportunitypareto/machine/AE5A13C7-A5F5-909C-2C5A-F3EC6EF2045B/start/20200617T061000.000/end/20200617T141000.000/level1/reason/level2/comment/maxsub=3

CS-2546

https://slxdev.atlassian.net/browse/CS-2546

Fannie has parts that were "incycle" but no parts were created.

HP - Thinks there is a mismatch between previous Part count changes and the new microstoppage adjustments.

HP to investigate.

Sample URL

https://saas48.shoplogix.com/whiteboard/#/perioddetail/25E5D1F4-F13E-36F3-3D57-FC1CCE67DE9E/start/2020-06-08T11:00:00-04:00/end/2020-06-08T12:00:00-04:00/bucket/1/timeMetric=0

CS-2467

https://slxdev.atlassian.net/browse/CS-2467

Hello,

We don't understand how the expected quantity lost during unscheduled is calculated for the area.
It is not equal to the sum of expected quantity lost during unscheduled of avery lines..

Please find attached an exemple.

Sample URL

https://saas117.shoplogix.com/whiteboard/#/areameeting/area/24

CS-2349

https://slxdev.atlassian.net/browse/CS-2349

Sorting by name works correctly, ascending and descending, but when sorting by due date the system sorts the hours BUT NOT THE DAYS/DATE. See attached pictures.

Sample URL

https://saas132.shoplogix.com/optimizer/#/optimizer/area/4