Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

When customers can expect this release:

Group 1: October 6, 2020

Group 2: October 7, 2020

Group 3: October 15, 2020


Highlights this release:

  • A functionality to configure job filter labels for any Area that is a line has been created on the New Configuration Interface (PNE-1018)

  • Still active development ongoing for the Analytics Portal.

Bug Fixes:

PNE-1265

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

Recent changes to Shoplogix.Server.Web.CustomAuthentication have led to a binding problem in main/config.axd when Machine licensing (not CEX licensing) is set

PNE-1261

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

Shift starts at 7 am after the change in Shift Calendar, it used to start at 3 am.

First hour should be marked as Unscheduled, but both hours are displayed as Scheduled time.

PNE-1244

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

Cannot save changes if <ExternalAuth>1</ExternalAuth> in config file.

Error 401 occurs

CS-4019

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

Whiteboard will not open. Page is blank.

CS-3955

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

Calendars keep reverting to older versions on saas12
When trying to fix, I found on P270 overlapping shifts, and Unscheduled shifts
If an attempt is made to correct the issue, like deleting one of the shifts, the breaks disappear;
Attempts to copy shifts created gaps in the calendar
The Flash calendar and the shift report both seem normal

CS-3705

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

As an example; The Grados Brix aplicacion de tambor SPC, in the table, reflect a median number of 81.9791 but the gauge only shows 1.9791 missing the left-most significant figure (8)

It is in all gauges, as in temperature zona 3 it is loosing almost two digits in the left.

CS-3681

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

The API metrics Cycle time and uptimeHours do not match the whiteboard values such as what is seen on the waterfall view.

This is a source of confusion to the customers.

I would like the cycletime seconds to match the waterfall and the uptime value to match as well

Likely these variables are based on something and should be added as new metrics, though I am uncertain what those values are.

Alternatively, if I can get an answer how to dervice a matching value

CS-3553

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

Unable to translate "Expected Parts" from the dashboard view

I tried different combinations, and none of them work

CS-3474

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

SAAS Customer Lithotech (Bidvest paper plus) calendar and shift planning schedule is out of sequence again.
Please have a look at it, as its changing by itself...

Fixes / Small Enhancements

PNE-1246

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

The <MicroStopStatus> and <RunningSlowStatus> tags are not written for default status names and as a result not being used when enabled.
Have to always write default value into XML to avoid this issue

In LegendDeviceSettings.cs need to set defaults for read so it will match to the write values

PNE-1202

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

Currently `CustomAuthentication.cs` checks if a user can read any configured machine. Want to change this check to if a user can read any licensed machine.

eg. this code needs to be adjusted

            if (IsAuthenticated(context))
            {
                var rules = _accessManager.CurrentRules;

                if (!_configManager.CurrentConfig.Machines.Any(m => rules.CanRead(_roles, context.User.Identity.Name, m)))
                {
                    _log?.Trace($"401: CustomAuthentication: {context.User} can not read any machines: {context.Request.Url} {context.Request.UserHostAddress} {context.Request.UserAgent}");
                    context.Response.StatusCode = 401;
                    context.ApplicationInstance.CompleteRequest();
                    return;
                }
            }

PNE-1197

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

Currently when there is a ramp/counter value for total/scrap/good we do a sanity check of

countDelta = Current Count - Last Count
minuteDelta = (Current Timestamp - Last Timestamp).TotalMinutes
effective rate = countDelta / minuteDelta

IF effective rate > (machine expected production rate * 10.0) THEN
  IGNORE
END IF

Where 10 = hard-coded RateLimitFactor

For some scenarios (See https://slxdev.atlassian.net/browse/CS-3016 ) it would be helpful to be able to configure said threshold.

Added Error signal for when rate limiter triggered.

New Features / Status on Long-term Work:

PNE-1018

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

Summary

For Schedule Optimizer and (Flash) Quality Config job filter labels are configured at the Line level and needs to be available in the New Configuration Interface for any Area that is a Line (has a line machine configured)

Details

  • Need to implement settings interface that match Schedule Optimizer - Job Filters

  • Need to investigate possibly removing Machine level Job Filter labels since their current usage is unknown (The filter on machine level are used in Flash reports for re-labeling generic filters on some reports)

  • Need to implement changes to api call for area level that will return filters

  • Need to add Checkbox for enabling <ScheduleOptimizerEnabled>1</ScheduleOptimizerEnabled> tag on Plant level

  • No labels