Release Notes 5.0.0.13861

PNE-1051

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

problem: db backloader is not loading machines with timezone on the east of UTC.
solution:

• PARTIAL SOLUTION: make backloader use its time more efficiently and power through the unchanged but invalidated days faster. This won’t be enough.

• the rest of a solution: make batches responsible for refreshing every day they invalidate.

PNE-1045

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

problem: db backloader is not loading all machines.
solution: make backloader aware of all machines instead of just ones in the batch.

• snippet for manually correcting the problem on released machines, including instuctions: https://gitlab.com/shoplogix/pne/snippets/1991179

• code solution will be in an MR attached

PNE-993

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

Production Summary example:
https://qatesting.shoplogix.com/whiteboard/#/productionsummary/3CBE1E62-F873-2596-A9F4-268FFE0B9CC0/start/2020-05-05T10:00:00-04:00/end/2020-05-05T12:00:00-04:00/gauge1=1&gauge2=8&gauge3=4&timeMetric=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&cycle=3&cycleDP=1&cycleTOL=0&gaugeTOL=0&capacity=true

Open

Expected behavior: OEE should be the same as in Period Detail for the specific time period (OEEc actually) or OEEc in Waterfall.

Perioddetail:
https://qatesting.shoplogix.com/whiteboard/#/perioddetail/3CBE1E62-F873-2596-A9F4-268FFE0B9CC0/start/2020-05-05T10:00:00-04:00/end/2020-05-05T12:00:00-04:00/bucket/120/quality=true&gauge1=1&gauge2=8&gauge3=6&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&search=NOT%20micro

Open

Waterfall:
https://qatesting.shoplogix.com/whiteboard/#/oeewaterfall/machine/3CBE1E62-F873-2596-A9F4-268FFE0B9CC0/start/20200505T100000.000/end/20200505T120000.000/yesoee=true

PNE-992

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

In Shift Hours view, if Line Cycle Factor is set to 1, it will show as 0 and remove any production counts, causing Line OEE views to show as 0 OEE.
https://qatesting.shoplogix.com/whiteboard/#/shifthours/FFD4D9CF-EFAA-ED58-0298-AD1A4F13C386/start/20200615T070000.000/search=idl&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&units=3

In Line Summary and Shiftline OEE is showing as 0, likely related to this issue as well.
https://qatesting.shoplogix.com/whiteboard/#/linesummary/area/7/start/2020-06-08T15:00:00.000/end/2020-06-10T23:00:00.000/snaptoshift=false&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1

After talking to Ben and Aleks, the root issue here was that the search terms typed into the search bar stick around after refresh or navigation, causing data display issues.

Desired functionality

Type “idle” into search

• case one: on refresh

  • current: idle stays in splat and data stays filtered, but “idle” is missing from the search bar

  • desired: idle stays in splat but we should see “idle” in the search bar

  • same applies to if the refresh occurs by changing settings

• case two: navigating away from the view in any way (nav icons or Shoplogix logo)

  • current: go back to the view, search bar is empty but the search term is still in the splat

  • desired: go back to the view, search term should NOT be in the splat or search bar and data should not be filtered

I will fix this for line summary first, and then evaluate if the rest of the views can be done as part of this card, or if they should be completed in a new case (to meet cycle time).

PNE-946

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

Shift Hours
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&units=3&cycleDP=1&cycleTOL=0&gaugeTOL=0

Check hour 3 (9: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/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&cycle=5

Discrepancy is there for SPH, SPM and Part Cycle Time.

CS-2908

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

Hi Guys,

Operators no longer have access to enter in true or false of manual buttons.

They are now invisible:

https://saas126.shoplogix.com/whiteboard/#/dashboard/761F465B-E199-01D7-5C28-895DA919C3B4/alloweditreason&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&cycle=1

CS-2081

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

Hi,

Please check the machine "Comprobador de Amperaje", the reason "No Programado para Producción" in the Whiteboard it is showing expected production (availability) despite it is a capacity reason.

Thanks and regards.

Sample URL

https://tecnova.shoplogix.com/whiteboard/#/perioddetail/00d0c9bb711f/start/2020-04-14T00:00:00.000/end/2020-04-18T08:00:00.000/bucket/60/timeMetric=0

PNE-1041

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

Customer is sending job data from their ERP to our system saving an XML file in the collector PC so we can populate the Job List in each of their machines automatically. This is working fine.

Now they need to feedback their ERP with job data from us. We already provided the API query to do this, but IT IS MISSING the ErpCode the customer provided to identify the machines.

We need to correct the API output to include the ErpCode please.

Enhancement Request

PNE-1003

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

Icons should be re-designed + consistent with each other for the view, for the action icons as well as the tree legend machine/area icons.

Seeing as PEConfig is a different product than Whiteboard, it is normal for it to have it's own icon set that differs, just as the Advanced Portal has it's own icons that differ. If this product has the potential to be customer-facing, then we should be ready stylistically to present a cohesive platform.

Currently the icons are already considered temporary placements (CC @Alex Karyakin (Unlicensed)) so I do believe bringing in the UX view into this card a big factor.

Icon Set

Tree Legend

Menu

Area

Machine

PNE-979

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

Configure PagingEmailSender to send an email template

Whenever a page status change transaction takes place, there should be an email sent with the the page detail parameters, the template should be designed to be easily readable and understood.

For now, there will not be a link to the specific page from the email, we may add a link to the Paging List View (tbd).

Parameters for email:

• Current status of the page.

• Assignee (if available).

• Message text.

• Department page is created for.

• Machine/Area of page.

• Time of update (Created)

Design Iteration 1 :

PNE-977

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

configure this PagingEmailSender to send emails upon creation of new page using the departments table in the database

i.e. when a page is created, an arbitrary email should be sent to the email address associated with that department

PNE-965

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

Add the ability to edit existing alerts in the new config.

Have to save the alert and be able to edit the existing alerts

This case will only cover the editing of the actual values within the fields as editing the options (like type ) will affect all other options further down.

This will be in a separate issue, changing the alert type and some options that affect further selections and options.

PNE-954

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

Description: Put line data in the cube in a reasonable structure so we can have line dashboards. (this story enables the iterating with product/Jesse to begin).

Acceptance Criteria:

• Line data must be stored in the core data table

  • MachineId = “Line_” + LineMachineId

• Machine, Area, and any related tables must have these “Line machine ids”

• Machine table must have a “line filter”

• If there are no lines in a plant, there must be no line core data (duh).

• Build a sample dashboard showing how this all works together.

Technical notes:

Dim Machines:

• MachineId = “Line”+MachineId

• MachineName = Line.Name

• Area = parent area (no change to default machine logic)

Dim Areas:

• Stays in Areas, as is. Allows area level grouping of machines. (not sure if that's desired?)

Dim Machine Security:

• Customer Account (from Area) unchanged.

• Machine Id will be “Line” + MachineId

PNE-904

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

Create signed installer for screen management windows client

Code Signing Options:

1. Digicert: https://www.digicert.com/code-signing/

   1. PROS: Used by majority, highly recommended by most including Microsoft.

   2. CONS: Slower load times then GlobalSign (Applies to website SSL only).

   3. 3 YEAR VALIDITY COST: CodeSigning: USD $474, EV CodeSigning: USD $664.

2. GlobalSign: https://shop.globalsign.com/en/code-signing

   1. PROS: Faster load times then Digicert (Applies to website SSL only).

   2. CONS: Not widely used, costly.

   3. 3 YEAR VALIDITY COST: CodeSigning: USD $599, EV CodeSigning: USD $950.

3. Evaluated Trustcenter and SSL, not worth our time compared to options above.

After thorough research, analysis, and evaluation, by recommendation is to move forward with Digicert and purchase their EV CodeSigning package with a 3 year validity as that is the most secure and mature option.

Furthermore, I recommend we purchase the Advanced Installer Professional Edition that comes with a perpetual license at a single cost of USD $499 per user (We only need one user). This allows us to create installers for our applications and digitally sign them with our certificates. Link provided below:

https://www.advancedinstaller.com/purchase.html