Release Notes 5.0.0.16656
When customers can expect this update:
Group 1: February 23, 2021
Group 2: February 24, 2021
Group 3: March 4, 2021
Highlights this release:
Analytics - Blended Expected Job Rate: If you need to understand jobs with different cycle factors in the same report, we need to “blend” this value by adding all [Expected Production], then dividing by all [Expected Cycles]. See PNE-1468.
Bug cleanup and continued stabilization of the Analytics Portal
Bug Fixes
PNE-1649 | https://slxdev.atlassian.net/browse/PNE-1649 Example: For expected result refer to the following cases: |
PNE-995 | https://slxdev.atlassian.net/browse/PNE-995 Precondition: Steps to reproduce:
Expected behavior: Cycle Factor = default machine Cycle Factor (or '1' if default machine Cycle Factor=0)
Edit: Same behavior is reproducible for Scrap Cycle Factor |
CS-6565 | https://slxdev.atlassian.net/browse/CS-6565 I have been trying a lot to have TV screens to stay logged in,
TV screens do not last more than 2 hours logged in, and some screens have a couple tabs rotating and sometimes is only one of them failing Can you please check if recent update is the root cause, it started yesterday on this account Account: Industrias Licoreras If so please revert it o something as customer is receiving reports of Screens failing several times at day, and it is taking a lot of time going to remote connection and testing Thanks Sample URL |
CS-6437 | https://slxdev.atlassian.net/browse/CS-6437 Customer identified an issue when a machine stops running the machine defaults to an idle state with a specific reason "Run Time - Roll change" without the reason applied to the machine. This seems to be occurring on multiple machines. Further investigation shows that the reason has no OPC ID and not configured to be used in the idle machine state. the machine does not have downtime hold configured either. Sample URL |
CS-6399 | https://slxdev.atlassian.net/browse/CS-6399 Hello, we received a report within values gap with whiteboard result (more than 20% on OEE) I verified dashboard filter, date, widget filter, and also the date on whiteboard. Nothing seems to be anormal in term of filtering. May you please have a look on this report and tell me what's the problem? many thanks Alexandre Sample URLhttps://fareva.shoplogix.com/whiteboard/#/areameeting/area/2/start/2021-02-01T00:00:00.000/end/2021-02-08T00:00:00.000 https://portal.shoplogix.com/app/main#/dashboards/601bc057cff20a002d699ca9 |
CS-6394 | https://slxdev.atlassian.net/browse/CS-6394 URGENT: All shoplogix do not work Sample URL |
CS-6370 | https://slxdev.atlassian.net/browse/CS-6370 https://saas55.shoplogix.com/shiftCalendar/#/?machine=BA6B6860-07B5-530F-59C9-C9DB47D56C2B
https://saas55.shoplogix.com/shiftCalendar/#/?machine=0BBB4F10-8D3D-C7E9-C3AE-72761B5A4402 If you go to each these links you will see correct shifts.
This is confusing for the engineer/customer AND if you then hit save (say you're doing dozens of calendars) you could then double save the shifts. This process can be repeated with additional links, and or break combinations so if I go to a thirds link that will be added.
As a temporary work around I simply hitting refresh whenever entering a shift scheduler will clear the phantom break. While we wait for a fix. ~Hino Sample URLhttps://saas55.shoplogix.com/shiftCalendar/#/?machine=BA6B6860-07B5-530F-59C9-C9DB47D56C2B https://saas55.shoplogix.com/shiftCalendar/#/?machine=0BBB4F10-8D3D-C7E9-C3AE-72761B5A4402 |
CS-6347 | https://slxdev.atlassian.net/browse/CS-6347 [Site]: Fairlawn and Ringwood [issue]: Running state is missing from the standard machine state configuration owing to which data is not available on the whiteboard. [Machine Impacted for Fairlawn] [Machine Impacted for Ringwood] Sample URLSaaS72 & SaaS85 |
CS-6068 | https://slxdev.atlassian.net/browse/CS-6068 DescriptionHi Evan, Sample URLhttps://fareva.shoplogix.com/whiteboard/#/productionsummary/D6238371-5519-E906-58DD-93A5C3DEDAD1/start/2021-01-25T09:50:00.000/end/2021-01-25T10:50:00.000 https://fareva.shoplogix.com/whiteboard/#/productionsummary/D61B19E5-7815-44D6-6481-93A5C3AC2C99/start/2021-01-25T08:50:00.000/end/2021-01-25T09:50:00.000 |
CS-5124 | https://slxdev.atlassian.net/browse/CS-5124 Cavitation Factor Not Appearing Correctly When Filter Is Used With automotive customers they use the cycle factor extensively and the Analytics Portal Defaults to the Part Cycle Time. This causes the customer confusion as the Cycle time appears wrong because they are not using the correct measure. Additionally the cycle factor needs a formula tweak to allow for easier use. Hino’s notes → I managed to successfully give Robert what he wanted using this equation (sum([Total Good Production])) * (Sum([Job Cycle Factor]),[Job Name]) (sum([Total Good Production])) << sum of part * (Sum([Job Cycle Factor]),[Job Name]) << Sum of parts based on job name? This is because he’s trying to back calculate variables on his machine based on the production. |
CS-5035 | https://slxdev.atlassian.net/browse/CS-5035 Issue was found while looking at peconfig Microstop, while defined in the configuration GUI, does not show in peconfig (missing MS.png) Similar to https://slxdev.atlassian.net/browse/CS-4125#icft=CS-4125 where Microstop was changing to a running state Sample URLhttps://saas25.shoplogix.com/configuration.html https://hunteramenities.shoplogix.com/whiteboard/#/shifthours/AC107D13-6B36-5E5E-F4AD-8FB4E21BD17E/quality=true&cycle=1&gauge1=1&gauge2=8&gauge3=0&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://wpinnova.shoplogix.com/peconfig/#/ |
CS-5009 | https://slxdev.atlassian.net/browse/CS-5009 Formerly : AP IAC Yesterday master dashboard
The "OEE performance By Area" conditional formatting does not behave the same as the top numeric Widgets, and "OEE elements by Area" and graphs in general |
CS-4864 | https://slxdev.atlassian.net/browse/CS-4864 e-mail report has wrong time From Subject Received Size In Folder |
CS-4388 | https://slxdev.atlassian.net/browse/CS-4388 Abbott is ready to trial with Active Directory Not sure what format is required for the documentation or what next steps are Sample URL |
New Features / Status on Long-term Work
PNE-1543 | https://slxdev.atlassian.net/browse/PNE-1543 SummaryCurrently the Downtime Reason edit dialog box is different when launching from the Dashboard view vs Period Detail. This dialogue box should be made consistent since it presents the same information and has a similar click flow. DetailsDowntime Edit from DashboardDowntime Edit from Period Detail |
PNE-1530 | https://slxdev.atlassian.net/browse/PNE-1530 SummaryCurrently the Now option isn't available in the start box for a job from the dashboard view. Details
|
PNE-1486 | https://slxdev.atlassian.net/browse/PNE-1486 As a user, I need blended expected job rate based on duration of the job within requested time period. Examples: Same problem is reproducible for Line Jobs: Even when 2 jobs are exactly on half of specified time Average Job Rate is still incorrect: Example: |