Page Comparison

...

PNE-944

QualityCheckService null exception

Description

`jobRepo.GetCurrentJob` can return null if no current job

https://gitlab.com/shoplogix/pne/-/blame/develop/visualstudionet/Server/Shoplogix.Server/Services/Quality/QualityChecksService.cs#L178

Code Block
currentJob: jobRepo.GetCurrentJob(machine).Clone(),

https://qatesting.shoplogix.com/logs/2020-05-28%20Web.txt

Code Block

2020-05-28 08:22:17.9594 04044:019 FATAL Shoplogix.Server.Web.WebApplication AppDomain Unhandled Exception: IsTerminating=True: Object reference not set to an instance of an object.
 EXCEPTION System.NullReferenceException: Object reference not set to an instance of an object.
   at Shoplogix.Server.QualityChecksService.ExecuteQualityChecksService() in D:\BuildAgent\work\3378db5a28cef30e\visualstudionet\Server\Shoplogix.Server\Services\Quality\QualityChecksService.cs:line 176
   at Shoplogix.Server.QualityChecksService.RepeatRun(CancellationToken token) in D:\BuildAgent\work\3378db5a28cef30e\visualstudionet\Server\Shoplogix.Server\Services\Quality\QualityChecksService.cs:line 241
   at Shoplogix.Service.RepeatingService.RepeatingRun(CancellationToken token) in D:\BuildAgent\work\3378db5a28cef30e\visualstudionet\Server\Shoplogix\Service\RepeatingService.cs:line 62
   at Shoplogix.Service.ExpandingTimer.<>c__DisplayClass7_0.<.ctor>b__0(Object state, CancellationToken ct) in D:\BuildAgent\work\3378db5a28cef30e\visualstudionet\Server\Shoplogix\Service\Timer.cs:line 29
   at Shoplogix.Service.ExpandingTimer.RunInternal(CancellationToken parentToken) in D:\BuildAgent\work\3378db5a28cef30e\visualstudionet\Server\Shoplogix\Service\Timer.cs:line 101
   at Shoplogix.Service.ExpandingTimer.Run(CancellationToken parentToken) in D:\BuildAgent\work\3378db5a28cef30e\visualstudionet\Server\Shoplogix\Service\Timer.cs:line 79
   at Shoplogix.Service.RepeatingService.ServiceRun(CancellationToken token) in D:\BuildAgent\work\3378db5a28cef30e\visualstudionet\Server\Shoplogix\Service\RepeatingService.cs:line 51
   at Shoplogix.Service.ServiceBase.Run(CancellationToken haltToken) in D:\BuildAgent\work\3378db5a28cef30e\visualstudionet\Server\Shoplogix\Service\ServiceBase.cs:line 84
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Tip
FIXED

PNE-926

Opportunity Pareto - Area filter is not available for Area/Line Pareto if user navigates from Machine level Pareto

Description

Steps to reproduce:

In Whiteboard Homepage select any machine with Pareto enabled > Select Pareto
Navigate back to Whiteboard Homepage > Select Area/Line with Pareto enabled
Click on Level 1

Expected behavior: Area option is available
Actual behavior: Area option is not available

Workaround: Refresh the page and Area will be available in Level 1

Acceptance should be done by Jesse Hildebrand (Unlicensed)

Tip
FIXED

PNE-925

Opportunity Pareto - Time Window in splat issues

Description

Changing default time with chevrons and applying an additional grouping level is not working as expected

Steps to reproduce:

In Whiteboard Homepage select any machine with Pareto enabled > Select Pareto
Click on left chevron --> time window has changed as expected
Add any option available in Level 2 > Update

Expected behavior: Time window stays the same
Actual behavior: Time window is set back to default time

Note: In addition, chevrons are not working after Update (time window is header is changing, but displayed data stays the same).

Acceptance should be done by Jesse Hildebrand (Unlicensed)

Tip
FIXED

PNE-922

Opportunity Pareto - Custom Areas does not work

Description

Custom Areas don't appear to be working, no data loaded

https://saas54.whiteboard/#/opportunitypareto/areas/1003/start/20200302T071500.000/end/20200306T151500.000/level1=machine&maxsub=3&level2=reason&level3=comment

Tip
FIXED

PNE-914

OEE Waterfall Cleanup

Description

Issues:

For food and bev customers with high speed machines the cycle times of their jobs is regularly less than 1 second however the cycle time field in Waterfall only shows HH:MM:SS so it just shows as 00:00:00, example below:

https://saas60.shoplogix.com/Whiteboard/#/oeewaterfall/area/3/start/20190904T071500.000/end/20190905T151500.000/line

2. The units of the pieces that are displayed isn't captured anywhere. Mondelez makes use of various units compared to other customers so there's the possibility for confusion if the units aren't displayed anywhere. Options are to show them in the title bar like in other views (Shifthours) or show them in the table next to the value or label. Options shown below:

3. MTBF is for the bottleneck machine for lines, want that to be specified in the table. Example below:

If any of these aren't clear or you need more info we can do a quick call to clarify. Thanks!

Attachments

Image RemovedImage Added
Image RemovedImage Added
Image RemovedImage Added
Image RemovedImage Added
Image RemovedImage Added

Tip
FIXED

PNE-906

Database Changes Performance on MDLZ-BADDIQA

Description

When comparing performance on version 13132 vs 12521 I noticed there were a few queries that would fail under certain situations and also that the web logs were filled with fatal errors. Link to logs and results of performance testing are below:

https://mdlz-baddiqa.shoplogix.com/logs/

https://mdlz-baddiqa.shoplogix.com/logs/2020-05-20%20[00028]%20Web.txt

Attachments

View file

name	Whiteboard Regression Testing for Version 5.0.0.13132.xlsx

Tip
FIXED

PNE-847

New Config - Machine Types Clean up 1.0

Description

Issue # 1

PN 360, New 360, - Machine States - editable only Colour, Time Offset, MTBF Failure and Checkboxes

Issue # 2

PN 360 and New 360 - Remove ID and Frequency from variables, part counts

Issue # 3

XML and Plantnode Cloud, - remove Frequency from machine states, variables, job settings and employee settings

Issue # 4

Plantnode Cloud - add ID in machine states

Issue # 5

Add Order field to Device Settings GUI and API

Issue #6

Remove Plantnode, Manual, Red Lion and Hydra machine types from adding new machine dropdown

Issue #7

Need 'Disable Microstops' in Downtime machine states as a checkbox option

ADDITIONAL ISSUES caught in the final round of testinghttps://slxdev.atlassian.net/browse/PNE-825 :

Issue #8

Thresholds are messed up when saving in peconfig → This was working fine before (Regression)

Steps to reproduce:

In flash config select any OPC machine (ex: Test_Machine_AD) > Device Settings > Set DT Threshold = 120 > Machine States > Micro Stoppage > Set Threshold = 150 > Save > Tools > Save
In peconfig select the same machine > Machine States → Thresholds are as expected
Edit > Save > Refresh
Select the same machine > Machine States

Expected Behavior: Thresholds are not changed
Actual Behavior: Thresholds are changed (DT Threshold = 1.2 and Micro Stoppage threshold = 1.5)

Issue #9

Categories with space (Operator Efficiency, Slow Running and Material Handling) in Generic variable are not saved

Alex Karyakin (Unlicensed) feel free to amend/add/remove anything from Description, if needed.

Hino Pringnitz → Not part of UAT would like to discuss adding them in the future

Please add a Manual Machine checkbox for Manual operation machines this would be added to OPC machines (manual machines are actually OPC machines)
Please consider adding the ability to add manual variables
Please test a Red lion, hydra, and manual machine just to make sure your configuration won’t overwrite.

PS I am willing to do the testing but I am not sure how that Fits in your design.

AK:

Issue #10

When saving flash config with modified Slow Running name and Micro Stop states the New config is not saving the type of the threshold which is causing the issues. Need to add the threshold type to Slowr Run and Micro Stop

Tip
FIXED

PNE-844

Description

Precondition:

In config file on Plant level set <PagingEnabled>1</PagingEnabled>, <OeeWaterfallEnabled>1</OeeWaterfallEnabled> and <OpportunityParetoEnabled>1</OpportunityParetoEnabled>

Spanish:

French:

German:

Acceptance Criteria:

Paging, OEE Waterfall and Opportunity Pareto are translated and in upper case in Spanish/French/German

Tip
FIXED

PNE-820

Cycle gauge value doesn’t match on Plant Meeting and Shift Line if Cycle Gauge is set as ‘Cycle' or 'SPH’

Description

Example:

Shift Line: https://qatesting.shoplogix.com/whiteboard/#/shiftline/FFD4D9CF-EFAA-ED58-0298-AD1A4F13C386/start/20200219T145504.000/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&overCycling=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1

Plant Meeting: https://qatesting.shoplogix.com/whiteboard/#/plantlevellinemeeting/area/5/start/2020-02-19T07:00:00.000/end/2020-02-19T15:00:00.000/snaptoshift=false&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&cycleTOL=0&gaugeTOL=0&cycleDP=1

Hank Shin (Unlicensed) investigated the issue in https://slxdev.atlassian.net/browse/PNE-768:

in many shift based views, they are using a derived cycle factor (expectedCycles / target production)

unfortunately, in multi job multi cycle factor scenarios, real cycles != derived cycle factor * total

an overhaul is required to every component that uses this derived cycle factor.

tl;dr - shiftline is wrong

Affected Views:

Shift Hours
Shift Line
Shift Rollup
Area Meeting

Affected Gauges:

PPH
PPM
Strikes Per Hours
Strikes Per Minute
Part Cycle Time

Tip
FIXED

PNE-814

Changeover time on Shift Line is incorrect in Job bar

Description

Ex: https://qatesting.shoplogix.com/whiteboard/#/shiftline/FFD4D9CF-EFAA-ED58-0298-AD1A4F13C386/start/20200219T131656.000/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&overCycling=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&units=3

Based on Job bar, 'Jesse Job' is ended after start of hour 5 (11 am), however the changeover happened before the end of hour 4.

Similar bug was fixed for Shift Hours in https://slxdev.atlassian.net/browse/CS-434

Tip
FIXED

PNE-708

Pareto Translation to Spanish

Description

The following is not translated:

Shifts:
Day
Night
Afternoon

No values to display:
unscheduled
No Comment Entered
No Job Recorded
No Group Defined
No Job Filter Defined

Automatic States:
Idle
Micro Stoppage
Slow Running
Setup
Plantnode Downtime
Late Start
Early Departure
Shift Start Up
Break
Unscheduled

Tip
FIXED

CS-2364

Unable to enter scrap on Dashboard

Description

Customer is unable to enter reasons scrap on Dashboard view. The scrap entry works on the hourly and other views but not on the Dashboard.

Logs show this warning "WARN Shoplogix.Server.Services.ApiScrapService Failed: No scrap match edit:"
Dev tools show: bundle-5.0.0.13148.js?132345575945900000:1 PUT https://saas126.shoplogix.com/web/api/scrap/A085D026-0FF4-8648-CF6D-95B6D992B5D5/?1.16.18 400 (Bad Request)
r._onFinish @ bundle-5.0.0.13148.js?132345575945900000:1
(anonymous) @ bundle-5.0.0.13148.js?132345575945900000:1
(anonymous) @ bundle-5.0.0.13148.js?132345575945900000:1
r.emit @ bundle-5.0.0.13148.js?132345575945900000:1
S @ bundle-5.0.0.13148.js?132345575945900000:1
p @ bundle-5.0.0.13148.js?132345575945900000:1
(anonymous) @ bundle-5.0.0.13148.js?132345575945900000:1
m.run @ bundle-5.0.0.13148.js?132345575945900000:1
f @ bundle-5.0.0.13148.js?132345575945900000:1
setTimeout (async)
l @ bundle-5.0.0.13148.js?132345575945900000:1
i.nextTick @ bundle-5.0.0.13148.js?132345575945900000:1
i @ bundle-5.0.0.13148.js?132345575945900000:1
u.exports @ bundle-5.0.0.13148.js?132345575945900000:1
(anonymous) @ bundle-5.0.0.13148.js?132345575945900000:1
d @ bundle-5.0.0.13148.js?132345575945900000:1
t.exports @ bundle-5.0.0.13148.js?132345575945900000:1
then @ bundle-5.0.0.13148.js?132345575945900000:1
(anonymous) @ bundle-5.0.0.13148.js?132345575945900000:1
r.dispatch @ bundle-5.0.0.13148.js?132345575945900000:1
scrapAdjustHandler @ bundle-5.0.0.13148.js?132345575945900000:1
saveClickHandler @ bundle-5.0.0.13148.js?132345575945900000:1
executeDispatch @ bundle-5.0.0.13148.js?132345575945900000:1
executeDispatch @ bundle-5.0.0.13148.js?132345575945900000:1
(anonymous) @ bundle-5.0.0.13148.js?132345575945900000:1
executeDispatchesInOrder @ bundle-5.0.0.13148.js?132345575945900000:1
r @ bundle-5.0.0.13148.js?132345575945900000:1
t.exports @ bundle-5.0.0.13148.js?132345575945900000:1
processEventQueue @ bundle-5.0.0.13148.js?132345575945900000:1
handleTopLevel @ bundle-5.0.0.13148.js?132345575945900000:1
p @ bundle-5.0.0.13148.js?132345575945900000:1
perform @ bundle-5.0.0.13148.js?132345575945900000:1
batchedUpdates @ bundle-5.0.0.13148.js?132345575945900000:1
batchedUpdates @ bundle-5.0.0.13148.js?132345575945900000:1
dispatchEvent @ bundle-5.0.0.13148.js?132345575945900000:1
bundle-5.0.0.13148.js?132345575945900000:1 Error: No scrap match edit
at r.IncomingMessage.<anonymous> (bundle-5.0.0.13148.js?132345575945900000:1)
at bundle-5.0.0.13148.js?132345575945900000:1
at r.IncomingMessage.r.emit (bundle-5.0.0.13148.js?132345575945900000:1)
at k (bundle-5.0.0.13148.js?132345575945900000:1)
at bundle-5.0.0.13148.js?132345575945900000:1
at m.run (bundle-5.0.0.13148.js?132345575945900000:1)
at f (bundle-5.0.0.13148.js?132345575945900000:1)

Sample URL

https://saas126.shoplogix.com/whiteboard/#/dashboard/A085D026-0FF4-8648-CF6D-95B6D992B5D5/alloweditreason&cycle=1&gauge1=1&gauge2=8&gauge3=6&timeMetric=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1

Tip
FIXED

CS-2250

Messaging through Real Time Variables not functioning

Description

The messaging at Kellogg's Rome using Real Time Variables has stopped functioning
All of the machines in areas 38 and 39 have it turned on using RTV but are not displaying anything
This was configured on 5May2020
It has previously worked, but those areas have stopped updating
The XML data from the machines shows the tags sending the correct data; the Hourly and Analysis shows the values changing

This would not be urgent if it wasn't for multiple previous issues at the facility

Sample URL

https://saas123.shoplogix.com/whiteboard/#/shiftrollup/areas/38 https://saas123.shoplogix.com/whiteboard/#/shiftrollup/areas/39

Tip
FIXED

CS-2013

Possible XML bug - Machine state/reason changed without input from XML system

Description

https://saas77.shoplogix.com/whiteboard/#/perioddetail/XMLCN_IACLogrono12/start/2020-01-23T06:00:00.000/end/2020-01-26T14:00:00.000/bucket/60/gauge1=1&gauge2=8&gauge3=6&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&overCycling=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.01&scrapyellow=0.02&scrapred=0.05

Over the course of a week no changes occurs in the input, yet during this time the system went through multiples changes

https://saas77.shoplogix.com/Web/xmldata/XMLCONECTORLCN_IAC001/XMLCN_IACLogrono12/202002/OpcCore_20200212.xml?contentType=text/plain

most egregious example was at midnight on the 11th 00:00 of the 12th when the system just went into setup spontaneously.

During this time the customer did not do anything and yet the system changed (multiple times!)

At no point did this machine do anything in the real world it was offline.

The OPC core is unhelpful as it simply says Automatically Edited which I believe means our system is changing.

~ Hino

Tip
FIXED

CS-2007

Machine and User Reasons Resets On New Shift does not work for setup

Description

Hi Guys,

Machine Reasons & Manual reasons will not reset on a new shift.

Here is a sample:
https://saas117.shoplogix.com/whiteboard/#/shiftrollup/areas/46/start/20200417T222859.000/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&overCycling=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1

and here is another sample:
https://saas117.shoplogix.com/whiteboard/#/shiftrollup/areas/46/start/20200417T222859.000/offset/-1/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&overCycling=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1

Customer is complaining and requesting that this is urgently fixed as this is ruining their OEE figures. I have tried disabling Automatic Setup on a job change to see if it will remove the historic events of setup but it doesn't work.

Today I've noticed that if operators manually select any of the downtimes reasons labelled as setup and when the shift resets, the reason is removed and displays machine state "Setup" on new shift even though I have auto setup disabled. I will try to get a screenshot as the customer is using this system live so it's hard to get a screenshot on time to show this behaviour.

This is happening on all of Fareva BCM machines and potentially the entire server.

Sample URL

https://saas117.shoplogix.com/whiteboard/#/shiftrollup/areas/46/start/20200417T222859.000/offset/-1/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&overCycling=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1

Tip
FIXED

CS-1551

API Calls for Reason returns time but no occurrences for Setup Reasons

Description

In HTML - Appears that the first reason pulled will show occurrences but many others will have occurrences = 0. They are machine reasons with downtime edit and coming off a PLC. These are steps of the setup process. In JSON - just no occurrence tag

<Machine MachineId="2F7A21DB-1165-653C-118D-B6E38D096B0E" MachineName="RDG Evap 2"

If you look at the details of the machine in the 2nd query, you will see some steps have occurrences and others do not.

Sample URL

dfa.shoplogix.com/web/api/export/summary?Start=20200301&End=20200313&metrics=reasons,&groupBy=machine,&machines=2F7A21DB-1165-653C-118D-B6E38D096B0E&format=xml https://dfa.shoplogix.com/web/api/export/summary?start=20200301&end=20200313&metrics=,states,reasons&groupBy=Machine&Machines=,,,894B4B12-D324-FF85-319F-ACD8F848AD6B,2FAEBDB5-A3EA-25FE-18D9-20196D6F82F6,OPCCN_DFA_Portales021,2B600A89-D911-322D-CB51-B70FAA10DE3D,710DD708-C6B3-9146-21AF-B710DA346381,DC93CEA6-FCB0-F3CD-380E-B712BAAC3B9A,E1A224A4-8253-97E6-8A36-67691129B2A8,E801D753-8D22-CC9E-9FA7-6769112995F5,&format=xml&rnd=2 JSON Call https://dfa.shoplogix.com/web/api/export/summary?start=20200301&end=20200313&metrics=,states,reasons&groupBy=Machine&Machines=,,,894B4B12-D324-FF85-319F-ACD8F848AD6B,2FAEBDB5-A3EA-25FE-18D9-20196D6F82F6,OPCCN_DFA_Portales021,2B600A89-D911-322D-CB51-B70FAA10DE3D,710DD708-C6B3-9146-21AF-B710DA346381,DC93CEA6-FCB0-F3CD-380E-B712BAAC3B9A,E1A224A4-8253-97E6-8A36-67691129B2A8,E801D753-8D22-CC9E-9FA7-6769112995F5,&rnd=2

Tip
FIXED

CS-760

Production Summary shows Comment that Shift Hours does not

Description

The meeting view of a machine shows a comment for a non-existent reason. the internal comment query shows a comment but the hourly view don't show any reason .

saas113 - Huercasa
Username: Huercasa
Password: Veg360SLXpack

API query: https://saas113.shoplogix.com/web/api/comments/machines/72E1868A-E681-BB40-F5BB-81943805CB0B/start/20200124T060000.000/end/20200125T060000.000

hourly view: https://saas113.shoplogix.com/whiteboard/#/shifthours/72E1868A-E681-BB40-F5BB-81943805CB0B/start/20200124T100000.000/gauge1=1&gauge2=8&gauge3=6&cycleDP=2&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&nowrap=true&timeMetric=0&cycle=1&cycleTOL=0&gaugeTOL=0&overCycling=0

Meeting view: 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

the image shows the comment and the reason

Underlying issue is each comment pulls a little bit differently -

The “MEETING VIEW” Should match the SHIFT ROLLUP query.

So please change the underlying query used in the Meeting view to be the same query as the Shift rollup.

there are 3 linked bugs that may or may not be resolved by solving this.