PNE-818

OEE Waterfall is not rendered completely if pie chart is turned on

Precondition:
In Config file on Plant level enable OEE Waterfall <OeeWaterfallEnabled>1</OeeWaterfallEnabled>

Steps to reproduce:

1. In incognito/private mode go to Whiteboard Homepage

2. Select Area/Machine within Plant from precondition > Select OEE Waterfall

3. Select Settings > Display > Set Show Pie Chart = YES > Save

4. Select Shoplogix logo to navigate back to Whiteboard Homepage

5. Select any other Area/Machine within Plant from precondition > Select OEE Waterfall

Expected Result: OEE Waterfall view is displayed with pie chart.
Actual Result: Only pie chart is displayed.

Open

Workaround: Refresh page or reopen OEE Waterfall for the same machine/area from Whiteboard Homepage

PNE-890

Opportunity Pareto - Start and End are not working properly

Precondition: In config file set <OpportunityParetoEnabled>1</OpportunityParetoEnabled> for any Plant

Steps to reproduce:

1. In Whiteboard Homepage select any Machine within Plant from precondition

2. Select Opportunity Pareto > Select Settings > Change Start to a day before > Save

Expected result: Data is displayed for correct time period and correct time range is displayed in the header
Actual result: Data is displayed for correct time period, however, time range in the header is displaying default time

Open

Additionally, if user goes back to Settings and just click Save, data will show for default time period, but time range in header will show time selected in step 2. These two are shifting with each Save in Settings.

Note: Make

sure that if user navigates back to Whiteboard Homepage and selects Opportunity Pareto for the same machine/area where time range has been changed in step 2, view loads data for the default time.

PNE-869

Opportunity Pareto - Not loading data if Level 2 is changed for another Machine/Area

Precondition: In config file set <OpportunityParetoEnabled>1</OpportunityParetoEnabled> for any Plant

Steps to reproduce:

1. In Whiteboard Homepage select any Machine within Plant from precondition

2. Select Opportunity Pareto

3. Select any opting for Level 2 (ex: Shift)

4. Go back to Whiteboard Homepage by clicking on Shoplogix logo

5. Select different Machine within Plant from precondition > Select Opportunity Pareto

Expected result: Data is displayed for the selected machine with default time range default Level 1 (Reason)
Actual result: Data is not displayed

Note: I've also noticed that selected Levels stay in splat after step # 4. Not sure if it is affecting anything, so I wouldn't call a bug, but still can we please get rid of it?

CS-1979

Opportunity Pareto is not showing the correct duration number for "Scheduled Down" reason

Opportunity Pareto is not showing the correct number for the "Scheduled Down" downtime reason. It is calculating and sorting correctly, but the correct number of hours is not displaying accurately.

See comparison of two screenshots attached, one from the opportunity pareto and one from the flash downtime pareto.

I would like to show the opportunity pareto to the customer, but not like this.

Sample URL

opportunity pareto: https://altiumpkg.shoplogix.com/whiteboard/#/opportunitypareto/areas/12/start/20200405T000000.000/end/20200419T000000.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&maxsub=3&level1=reason

PNE-444

Time Remaining in for Running Job is incorrect

In Schedule Optimizer. Time Remaining in tooltip is displaying incorrect value

Schedule Optimizer:

Period Detail:

CS-2174

Migrated machines to cloud show no job in history

After Migrate machines in Arca Continental Cocacola from PN Outperfom to PN Cloud theu are not showing any previous job.

Saas5. Arca - Plant Guadalajara

L1 00d0c9ea28ea
L2 00d0c9bab107
L4 00d0c9ea5b54
L6 00d0c9e153a1
L7 00d0c9ea2924
L10 ex 00d0c9ea5ae0
L10 in 00d0c9ea5b66

CS-1953

Not able to update current Messages (Messaging Module) - ARCA Coca Cola

Customer is currently using messaging module, the current messages are not able to edit and update, doesn't show the request update. Not able to edit name, link, etc.

Only allow to generate new messages

Sample URL

https://saas11.shoplogix.com/whiteboard/#/shifthours/00d0c9ea5b12/gauge1=2&gauge2=4&gauge3=5&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

CS-1432

Area Meeting view does not snap to shifts

Meeting view does not snap to Shifts

Also should also address:

System to store and save settings during page re-loads or navigation changes: Currently, when user changes setting (example: Snap to shift --> NO) and saves, but then reloads/changes pages and returns back to Area Meeting view, the previously saved settings states are reset (example: Snap to Shift returns back to default Snap to Shift: YES). Save settings states when returning after page change.

Sample URL

https://saas54.shoplogix.com/whiteboard/#/areameeting/area/1003

CS-876

Pending jobs cannot be deleted in Optimizer (Merical)

There are some jobs in the pending queue that just can't be deleted. When you right click on them and select edit, delete, they seem dissappear. After repeating the process with all the jobs when you press save THEY ALL COME BACK. It's very frustrating.

I will appreciate your help to delete all jobs in the pending queue please. EDIT: PLEASE YOUR HELP TO DELETE ALL PENDING JOBS FROM ALL AREAS IN THE UTAH FACILITY. THEY WANT TO START FROM SCRATCH ADDING NEW JOBS.

saas61.shoplogix.com/optimizer/#/optimizer/area/10

Sample URL

saas61.shoplogix.com/optimizer/#/optimizer/area/10

PROD-137

Update to SLX API: Allow requests for Job-specific metrics

User Story:

N/A

Background:

Multiple customers (Nashville Wire, DFA, Coveris) have requested SLX’s API to provide more Job-related metrics data and to require less individual queries to piece this data together.

Customers currently use a combination of:

• Event - Scrap and Downtime (Web Query)

• Summary API endpoint (this Jira story primarily focuses around updates to this API endpoint)

• CurrentJob API endpoint

And then they need to perform their own data wrangling to consolidate and clean up these query responses.

They would prefer a central, simplified way to pull Job data.

Requirements:

REQ1. Make changes to the following existing GET request:

 Expected NEW data to include in API response:

Scaletti note: this will be a new metric called job, look at subjob metric as an example.

REQ 2. Ensure that the above data responses from the API are also able to be broken out by Shift Instance (Day, Name) and Shift Summary (Name)
(allow user to add these as arguments to the endpoint to include)

Default when no arguments: just a job summary

Scaletti note: Since it is now a metric, this requirement is a given.

REQ 3. The current API response includes REASON records, but they are consolidated (totaled). Change this response to break Reasons out by Reason record (each Reason should have a MachineID, Reason Name, start and end time, total duration, etc.). (filter machine status table for Reason).

Manny: We need a toggle between Event data and Core data

Brock: hoping to have options for: machines states, scrap reasons

Default: current state, summarized Reason

(might not be technically feasible ^, will talk to Brock about this, this might be out of scope)

Scaletti Note: Will create boolean options for reasons, states, scrap reasons, and state reasons to decide if I display every occurrence.

REQ 4. Create or edit existing API to allow user to make the following 3 requests:

Scaletti note: Moving existing functionality in Summary endpoint to new Job endpoints

UX Requirements/Prototypes (if needed):

N/A

Risks/Assumptions:

• Assumption 1: There are existing API endpoints for some of this data, I ( @Steven Arrol (Unlicensed) ) have not used this tool personally and some of the above requirements are based on multiple conversations with Brock and Manny

• Assumption 2: Requirements are also based on the attached file below:

Open

Simplified Queries to pull job data:

/web/api/export/jobs/instances/start/20200301/end/20200429?format=xml

Metrics of the Job with the specified query timeframe

<Job Name="Test Job" Instance="234c36414c7a4b6dbb9d501dd8faa75d" 

Start="03/01/2020 00:00:00.000" End="03/11/2020 10:21:24.865">

<Metrics Total="276176" 

Scrap="1412.04" 

OEE="0.63917676099654064" 

Availability="0.57656749882092029" 

Performance="1.1181727064572875" 

Quality="0.99142971595046814" 

UptimeHours="105.69337194448475" 

DowntimeHours="139.25576226499993" 

SetupHours="0" 

CycleTimeSeconds="11.021845171199384">

Metadata about the job. Notice flagged as a partial record as the start time of the job is outside the query timeframe.

<Job Name="Test Job" 

Start="02/28/2020 12:12:28.816" End="03/11/2020 10:21:24.865" 

Instance="234c36414c7a4b6dbb9d501dd8faa75d" 

Duration="115.35690698724707" 

PartialJobRecord="1" 

ExpectedRate="2215.3846153846152" 

ExpectedProduction="355.4568125" 

CycleFactor="8"/>

Business Owner

Brock / Manny

Acceptance Criteria

• Can use POSTMAN or similar tool to ensure the correct metrics are being sent back to user

• Need to ensure Brock is involved in UAT as well, as this is a complex request that does not involve any front-end dev so there may be some metrics inadvertently missed in above specifications. Want to ensure that what he is envisioning as the solution for his customers is correct before considered “Done”
  
  

PNE-886

Make a generic GUI layout for different types of the alert to be configured

Create general layout for the different types of the alert configurable and create a workflow between options selected.
Example:

• Time Range is selected then a duration for that option should be visible. For Last Record type range the duration option should not be visible

PNE-884

Add ability to configure emails based on shifts, would require new api and front end

Need to add new api to retrieve shifts from shift schedule or mapping and make emailed alerts configurable per specific shifts

Add gui and flow to adding email to alerts based on specific shifts or all shifts

PNE-851

Add new navigation to Opportunity Pareto view

Need to activate new navigation inside of Opportunity Pareto.

• Currently Opportunity Pareto has the old navbar style, now allowing the user to navigate to another view from there.

• Need to enable new navigation on all views that are in the same codebase / project that are featured in Apps Nav.

Requirements.

• Apply navigation checker, if it’s on, display new navigation, if it’s off, display old nav.

Updates

• Re-naming “OEE Waterfall” + “Opportunity Pareto” icon titles to “Waterfall” and “Pareto” to fit proper in the apps nav. 

PNE-673

Database Insert Service / Preloading database when we turn it on

Problem: When we turn the core data on, data needs to already be in the database for waterfall, and for performance reasons. Bulk inserting ALL machine data into the database. Get a strategy for pre-loading this data.

Solution chosen:

1. Pre-load the data at upgrade time: ask the disk cache for all data.

Acceptance Criteria:

1. On upgrade, on manual request the system should load as much historical data from 2020 and 2019 core data into the database as it can in 5 minutes (300 seconds).

   1. “Manual request” means this command on the command line in the Enterprise/bin folder:

   2. dataprocessor.exe --importCoredataFromDiskCache --allowedRuntimeInSeconds=300

2. A report for future reference in the cache folder showing machines and days that got loaded vs those that didn't.

3. (see comments for steps to acceptance)

Testing Ideas:

1. See comments

Technical Notes:

• If we go down partitioning – aurora has no disk partitioning options – storage is opaque to us.

• COPY is fastest when used within the same transaction as an earlier CREATE TABLE or TRUNCATE command. In such cases no WAL needs to be written, because in case of an error, the files containing the newly loaded data will be removed anyway. However, this consideration only applies when wal_level is minimal as all commands must write WAL otherwise. (https://dba.stackexchange.com/questions/187061/postgres-copy-is-it-possible-to-load-multiple-files-into-the-same-table)

• Postgres COPY FREEZE is interesting, but hard to apply with our data. Could be a 50% performance improvement for pne673. https://www.cybertec-postgresql.com/en/loading-data-in-the-most-efficient-way/

• Strategy: Get performance benchmarks for each:

  1. existing code, no changes, no db tricks, query monthly coredata per machine for 2 years. (28.8min)

  2. Try disabling indexes.

  3. Try parallel execution. (QA13 is only 2 core… but lets see. ()

  4. COPY FREEZE (depending on if our benchmarks for 1 year of data seem acceptable)

Future considerations:

1. There should be a way for an admin to load older data

2. Data wont be fully populated if not in the disk cache already

3. (These future considerations were spun off into: PNE-843)

PNE-238

Revision of Cycling Gauge Functionality

#1109 HQ-1576438906

1.  

   1. User Story:
      N/A

1.  

   1. The Problem:
      Previous change request from Bway was implemented months ago but when presented to the client, was told that it was not accurate. The original requirements included documentation plus a working prototype, which was assumed to be clear enough for approval. However, client does not believe correct implementation was met.

This time a full table of scenarios is built out to ensure clarity.

1.  

   1. Requirements
      Please see table for requirements and examples of each scenario:
      https://docs.google.com/document/d/16S6Ec7sjkiDK08L7EGaeIbgp08g-HynQVR0eAMn1ptQ/edit?usp=sharing

The following charts depict existing and new behaviour of (-sec) in Threshold limits, in both Cycle and Part Cycle Time settings.

1.  

   1. Prototype / Screenshots (if needed)
      https://1bov3m.axshare.com/

1.  

   1. Risks / Assumptions

1.  

   1. Business Owner
      Thabo M. (on behalf of Bway)

1.  

   1. History
      Hank has worked on this item before and we met briefly to discuss the changes