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

Version 1 Current »

When customers can expect this release:

Group 1: July 28, 2020

Group 2: Jul 29, 2020

Group 3: August 6, 2020

Bug Fixes:

PNE-763

Fix Problem with Futuristic Jobs

Summary

Seeing cases where a job is in the future which causes Job Command checks to fail thus from the customer’s perspective breaks job functionality (e.g. can’t start/stop jobs)s

Things to Fix

  • Need to change IIS settings to allow the error response to be passed through. Whiteboard should be showing the response when there’s and error but due to IIS settings this message is getting blocked see: Custom errors on ASP.NET

  • Investigate why CheckFutureOrphans isn’t picking up these cases

Possible Scenarios

  • Future orphan might occur through the possible steps

    • Job Starts where no end time is set and so the end is set to the default 1 year in the future

  • Another Job Starts with a start date less than the previous job started with no end time so the future end date is also less than the previous job’s end date

  • Example: Job Start → Name = “Job-001”, StartDate = 2020/03/13 08:00 Job Start → Name=”Job-002”, StartDate= 2020/03/12 08:00

FIXED

PNE-259

Schedule Optimizer - Filter bugs

#1141 Link for all bugs and steps to reproduce (use Filters sheet):

https://docs.google.com/spreadsheets/d/186W93J65hZCoHIrFgOgBKZvlpV9qfGDsbo4pWjtagNQ/edit?usp=sharing

FIXED

CS-3006

Time zone change

time zone was assigned to the machines of the company Watts (saas5) America / Santiago was assigned to all the lines are more than 40 machines, the problem is that all the data is historically out of date in terms of stops and rejections several hours of lag that is to say, if the strike was attributed at 18 hours, it now moved between 4 and 6 hours apart.
The data can be retrieved at its correct time.

Regards

Sample URL

https://saas5.shoplogix.com/

FIXED

CS-2668

Line summary view is not showing OEE nor scrap

In Rica/ CocaCola the line summary view shows no OEE as well as the scrap count also in zero.
sw version 5.0.699.13580
saas11.shoplogix.com
it is not working in other servers/customers either
saas119 ver v5.0.699.13580
saas123 ver: v5.0.0.13406

Sample URL

https://lasmargaritas.shoplogix.com/whiteboard/#/linesummary/area/135/layoutoption=1&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&remain=false&elapsed=false https://saas11.shoplogix.com/whiteboard/#/linesummary/area/135/layoutoption=1&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&remain=false&elapsed=false

FIXED

CS-2280

Display problem of the whiteboard on the screen hour by hour Softys Argentina Plant (papelera de la Plata)

Hello guys.

They support me with this case, the client Softys Argentina notified us that on the whiteboard in Line MP1 the hourly graphics of the screen are not shown well, they can verify what happens, it is only in that Line the others are working well.

Attached image and URL of the problem.

Server = saas65

Thank you

Sample URL

https://saas135.shoplogix.com/whiteboard/#/shifthours/XMLCN_PapeleraLaPlata250/start/20200515T140000.001/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

FIXED

CS-1373

Seeing job record created when one should not be created - For AIC Birmingham

Press A Line has the following job logic set up.
######s.Integer("Om027.ShopFloor.5331.Job Status") != 2 ? s.Integer("Om027.ShopFloor.5331.Job Number") : IGNORE

But getting duplicate job records (two records for Job 24 with start of A / End of B and start of B / End of C and
should be just one record starting at A and ending at C. There are current state records for the Job Number. Would like to know why happening.

XML DATA
https://saas16.shoplogix.com/web/xmldata/E4A7B7D6-FAEC-0CAE-47A1-F3ED723C4E55/202002/OpcCore_20200225.xml?contentType=text/plain

Key data from above
<CurrentState Name="Om027.ShopFloor.5331.Job Status" Time3="2020-02-24T23:59:35.2440118-06:00" Value="0" Rec="993" />
{<CurrentState Name="Om027.ShopFloor.5331.Job Number" Time3="2020-02-24T23:59:35.2440118-06:00" Value="24" Rec="994" /> NOTE JOB NUMBER VALUE

<S Name="Om027.ShopFloor.5331.Job Status" Time3="2020-02-25T00:01:45.3530214-06:00" Value="1" Rec="1003" /> NO NEW RECORD
<S Name="Om027.ShopFloor.5331.Job Status" Time3="2020-02-25T00:01:55.3730233-06:00" Value="0" Rec="1005" /> AT THIS POINT NEW JOB RECORD
<S Name="Om027.ShopFloor.5331.Job Status" Time3="2020-02-25T00:02:45.4090264-06:00" Value="1" Rec="1008" /> NO CHANGE
<S Name="Om027.ShopFloor.5331.Job Status" Time3="2020-02-25T00:02:55.4140268-06:00" Value="0" Rec="1009" /> NO CHANGE
<S Name="Om027.ShopFloor.5331.Job Status" Time3="2020-02-25T00:02:55.4140268-06:00" Value="0" Rec="1009" /> NO CHANGE
<S Name="Om027.ShopFloor.5331.Job Status" Time3="2020-02-25T00:05:55.5670403-06:00" Value="1" Rec="1012" / NO CHANGE

Job Query
https://saas16.shoplogix.com/web/query.axd?type=job&machines=E4A7B7D6-FAEC-0CAE-47A1-F3ED723C4E55&start=20200224

Key Data from above
<Job Name="24" Instance="d964749dabd04892a74b44b1a30beec0" Source="Actual" Operation="Press" Start="02/24/2020 23:14:02.106" End="02/25/2020 00:01:45.353" TimeStamp="02/26/2020 00:02:16.897" Created="12/04/2019 18:51:49.232"/>

Note the end of above and start of below the transition record above

<Job Name="24" Instance="c79971fd01fd43f2a0fce91f4139c643" Source="Actual" Operation="Press" Start="02/25/2020 00:01:45.353" End="02/25/2020 00:48:17.814" TimeStamp="02/26/2020 00:02:16.897" Created="12/04/2019 18:51:49.232"/>

Job Command Query
https://saas16.shoplogix.com/web/query.axd?type=jobcommand&machines=E4A7B7D6-FAEC-0CAE-47A1-F3ED723C4E55&start=20200224

<JobCommand Command-Id="1205032d017d466ba7603dec8979244c" Command-Action="1" Command-TimeStamp="02/26/2020 00:02:16.897" Command-Username="ConnectorProcessService" Command-GenerateInstance="1" Name="24" Instance="c79971fd01fd43f2a0fce91f4139c643" CurrentJob="1" Source="Actual, Command" Operation="Press" Start="02/25/2020 00:01:45.353" End="02/25/2020 00:48:17.814" Created="12/04/2019 18:51:49.232"/>

<JobCommand Command-Id="cb1a277c96da4a838833b3780fba35dd" Command-Action="1" Command-TimeStamp="02/26/2020 00:07:14.470" Command-Status="3" Command-Username="ConnectorProcessService" Command-GenerateInstance="1" Command-StatusReason="Duplicate of Command for 24 Start: 2/25/2020 12:01:45 AM End: 2/25/2020 12:48:17 AM received within 5 minutes of last command." Name="24" Instance="bccb9269b3e0209f6d07620cef6af1dcbf5c587a" Source="Actual, Command" Operation="Press" Start="02/25/2020 00:01:45.353" End="02/25/2020 00:48:17.814" Created="12/04/2019 18:51:49.232"/>

Sample URL

Listed below in the description as several.

FIXED

New Features / Status on Long-term Work:

PROD-144

Whiteboard Dashboard Scrap Reason Reassigning

User Story:

As an operator, I want to reassign a scrap reason to automated scrap that have no reason, from the Dashboard view.

Background:

Coveris is requesting the ability to reassign a scrap reason to automated scrap that have no reason. This functionality exists in the hourly view but not the dashboard which is where Coveris Operators are using the system. Enhancement is add the functionality in the dashboard view.

Requirements:

Add navigation to scrap edit dialogue from Dashboard view to reassign automated scraps that have no reason. This feature should be the same as that in Hourly & Chrono views.

The navigation to the scrap edit dialogue that must be added is highlighted below:

UI Component Requirements:

REQ 1. The scrap edit dialogue should contain

  • Brown, horizontal bars with text depicting scrap reasons to apply

    • Some of these may be drop-down bars from which collections of reasons may be grouped together

REQ 2. After assigning a reason to scraps, text depicting the scrap, its corresponding reason, and the number of scraps should be visible below other scraps, next to a brown square (indicating scraps). E.g. “Ink Pumps Scrap, 5”, see below.

Functionality Requirements:

Scrap Edit Flow

FR 1. Users must navigate from the Dashboard view to reassign the scrap reason as follows:

  • Click ‘Scrap’ > click bar under ‘Reassign Scrap Reason' with desired Reason > Toggle ‘+'/’-' buttons to choose the number of scraps to assign this Reason to > Click ‘Save’.

Where to make this available:

This component is to be made available in the following view:

  • Machine Dashboard

Prototype / Screenshots / Examples:

Link below showing how the new feature works in the Hourly view:
/wiki/spaces/SD/pages/292814849

Example of current scrap edit dialogue on dashboard:

https://saas126.shoplogix.com/whiteboard/#/dashboard/49BB815C-FBC2-3F47-75B5-5D8ACB27A2A6/duration/60/bucket/10/gauge1=1&gauge2=6&gauge3=0&timeMetric=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&alloweditreason=true

Acceptance Criteria:

  • User is able to select Scrap with no associated reason from Dashboard, to navigate directly to Scrap Edit Dialogue

  • User is able to apply a Reason to a desired number of scraps

  • Scrap Reason and corresponding number of scraps will become visible below existing Scraps on Dashboard

FIXED

PNE-1029

New Config Alerts add validation on the alert Modal to make sure all necessary fields are filled before the modal is closed

This needs to be implemented before we can work on the alert dropdown edits that affect further selection.


For example changing alert type will require refilling of some other fields.
Validation will make sure that all necessary fields are set prior to saving the alert.

 

Need to make sure the required fields are filled (depending on which fields become available) before being able to close modal. There should be some some user feedback to which field needs changing.

Required Fields:

  • state type

  • alert type

  • name

  • time range

  • window alerts

  • window size

  • at least one escalation field

Window Alerts values in Escalation Level(s)

  • at least one email + shift with it

Please see the epic https://slxdev.atlassian.net/browse/PNE-812 for the individual alerts and which fields/dropdowns become available.

 

Testing:

Try to edit an alert, leave any of the above fields blank (if that field applies to the alert) and try to close the modal.

  • Modal will not close, and small red error text will appear under the problematic field telling the user that it's required.

FIXED

PNE-970

Adoption metric percentTargetComments > 100%

The adoption metrics from servers have adoption scores of > 1, due to the percentTargetComments metric having a score >1. The example URL shows a percentTargetComments of ~891%

Where to find the issue

As of 2020-04-17

Steps to recreate

Use below to find all occurrences where percentTargetComplete is >100% for the day.

SELECT plant_id, date_day,scheduled_time, total_time, online_machines, reporting_scrap, scheduled_machines, using_comments
FROM pne.scorecard_plant_day
where 
  using_comments > scheduled_machines 
  and scheduled_machines > 0;

Calculation

We assume the formula for percentTargetComments is as follows, calculated daily:

(# of machines with a comment) / (# of machines scheduled for the day)

FIXED

  • No labels