PNE-750

Plant Meeting Crashing on build 5.0.0.12014

Reporter: Aleksandar Dimitrijevic

Example:
https://qatesting.shoplogix.com/whiteboard/#/plantlevellinemeeting/area/7/

Console error when on Plant Meeting view:

Data doesn't seem to be rendered completely and cannot go to Settings.

Note: The issue wasn't reproducible on build 5.0.0.11904.

PNE-768

Cycle and Production Block issues in Shift Line / Plant Level Meeting as of build 5.0.0.12004

Reporter: Aleksandar Dimitrijevic

Ex. ShiftLine: https://qatesting.shoplogix.com/whiteboard/#/shiftline/FFD4D9CF-EFAA-ED58-0298-AD1A4F13C386/start/20200219T084741.000/gauge1=1&gauge2=8&gauge3=2&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

Ex. Plant Level Meeting: https://qatesting.shoplogix.com/whiteboard/#/plantlevellinemeeting/area/5/start/2020-02-19T07:00:00.000/end/2020-02-19T15:00:00.000/snaptoshift=false&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&cycleTOL=0&gaugeTOL=0&cycleDP=0

In Shift Line view Cycle gauge is blank. In addition, on build 5.0.0.11960 Cycle (which can be verified on Plant Meeting view) and Production Block values are different from values on build 5.0.0.12004, although they should be same (5.0.0.11960 should be correct one based on https://slxdev.atlassian.net/browse/PNE-670).

Shift Hours on 5.0.0.11960

Image Added

Shift Hours on 5.0.0.12004

Image Added

Plant Level Meeting on 5.0.0.11960 (Line 15)

Image Added

Plant Level Meeting on 5.0.0.12004

Image Added

Note: On build 5.0.0.11990 I couldn't load Shift Line or Plant Level Meeting, so it could be that is the version which introduced the bug.

PNE-801

OEE Waterfall is not working on IE 11

Reporter: Aleksandar Dimitrijevic

Description

Steps to reproduce:

1. In config file add <OeeWaterfallEnabled>1</OeeWaterfallEnabled> on any Area with <Plant>1</Plant>

2. In Internet Explorer navigate to Whiteboard Homepage > Select Plant where OEE Waterfall is enabled > Select OEE Waterfall

Expected Result: OEE Waterfall is rendered with correct results
Actual Result: OEE Waterfall page is blank

Image Added

PNE-803

Numerator and OEE gauge in Shift Line are incorrect

Reporter: Aleksandar Dimitrijevic

Description

Numerator and OEE gauge in Total section of Shift Line are incorrect.

Ex:
Shift Line: https://qatesting.shoplogix.com/whiteboard/#/shiftline/FFD4D9CF-EFAA-ED58-0298-AD1A4F13C386/start/20200219T141455.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&units=3EoL 1: https://qatesting.shoplogix.com/whiteboard/#/shifthours/E570F0B2-2E93-92ED-9CAE-AD171B401DFA/start/20200219T070000.000/gauge1=1&gauge2=8&gauge3=0&timeMetric=0&cycleDP=1&cycleTOL=0&gaugeTOL=0&overCycling=0&

Numerator in Shift Line total should be sum of good production from all End of Line machines.
Expected Numerator (sum of all Good Production from End of Line machines) = 27178
Actual Numerator = 67260

Expected OEE Gauge value = 68%
Actual OEE Gauge value = 77%

2020-04-06 - Discussed with Aleksandar Dimitrijevic (Unlicensed) , ratio below OEE gauge is good & expected production, and it does not equal the OEE

Bottleneck machine: https://qatesting.shoplogix.com/whiteboard/#/shifthours/FFD4D9CF-EFAA-ED58-0298-AD1A4F13C386/start/20200219T070000.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&units=3

EoL 21: https://qatesting.shoplogix.com/whiteboard/#/shifthours/76FF2128E570F0B2-2DF62E93-382A92ED-0ED79CAE-AD1CAFC21B52AD171B401DFA/start/20200219T070000.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&units=3

EoL 3: https://qatesting.shoplogix.com/whiteboard/#/shifthours/9AA9FA61-0908-66D7-EB56-AD1B43DD68B6/start/20200219T070000.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&units=3

In addition, scrap value in Shift Line total section is incorrect.

Case 1: If sum of good production from all End of Line machines is less then good production from Bottleneck machine, the difference should show as Scrap in Shift Line.
This is what we have in the example above and Scrap should be 768.

Case 2: If sum of all good production from End of Line machines is greater then good production from Bottleneck machine, the difference should show as Excess Good in Shift Line.

In both cases OEE gauge should be Sum of Good Production from all End of Line machines divided by Expected Production.

If anything is unclear, please contact Aleksandar Dimitrijevic (Unlicensed) or Jesse Hildebrand (Unlicensed)

PNE-607

=0&goalgreen=1&goalyellow=0.75&goalred=0.5&scrapgreen=0.02&scrapyellow=0.05&scrapred=0.1&units=3

EoL 2: https://qatesting.shoplogix.com/whiteboard/#/shifthours/76FF2128-2DF6-382A-0ED7-AD1CAFC21B52/start/20200219T070000.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&units=3

EoL 3: https://qatesting.shoplogix.com/whiteboard/#/shifthours/9AA9FA61-0908-66D7-EB56-AD1B43DD68B6/start/20200219T070000.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&units=3

In addition, scrap value in Shift Line total section is incorrect.

Case 1: If sum of good production from all End of Line machines is less then good production from Bottleneck machine, the difference should show as Scrap in Shift Line.
This is what we have in the example above and Scrap should be 768.

Case 2: If sum of all good production from End of Line machines is greater then good production from Bottleneck machine, the difference should show as Excess Good in Shift Line.

In both cases OEE gauge should be Sum of Good Production from all End of Line machines divided by Expected Production.

If anything is unclear, please contact Aleksandar Dimitrijevic (Unlicensed) or Jesse Hildebrand (Unlicensed)

PNE-607

Slider edit is not rounding scrap

Reporter: Joseph Kingry

Expected Result

Slider edit should increase/decrease values in integer numbers

Actual

Job/Sub-Job Total is not rounded when picking Job/Sub-Job

Prerequisite

Running 1 job with 2 sub-jobs or 2 Jobs no sub-jobs with decimal cycle factor

Reproduction
Click on running state for hour with 2 jobs or multiple sub-jobs

Expected Result
Total is rounded when picking job/sub-job

PNE-608

Rounding is creating excess scrap

Reporter: Joseph Kingry

Description

Prerequisite: Running 1 job with 2 sub-jobs with odd number as total production for the hour

Click on running state in the hour with odd number as total production (e.g 101)

Select sub-job 1 > Set all production to scrap (51) > Save

Click on running state in the hour with odd number as total production

Select sub-job 2 > Set all production to scrap (51) > Save

Expected Result: Rounding for sub-job 1 should be as is (51), however for sub-job 2, it should take total production - assigned scrap for sub-job 1 (101-51=50)

Actual Result: Scrap for sub-job 1 = 51; Scrap for sub-job 2 = 51; Excess Scrap = 1

PNE-623

Action Plan icons (Archive, Delete, etc.) appear as disabled when they are actually active

Reporter: Steven Arrol

Description

To be assigned to when it comes through the Kanabn

Issue:

The appearance state of the archive/delete buttons appears greyed out / light-opacity, as though it is not clickable. Users may not realize these buttons are active and available to them.

Steps to reproduce:

1. User goes into Action Plan portal

2. User selects >=1 action plan record in the table row using the left-side checkboxes

3. User hovers over Archive or Delete buttons

Expected Result:

• Buttons should appear as available (solid) and their hover-over effect should just be to darken slightly

Actual Result:

• Buttons appear “greyed out” and light, as though they are not available to the user

PNE-659

Null Exception State Data Export API

Reporter: Anthony Scaletti

PNE-699

Cannot add variables in New Config

Reporter: Aleksandar Dimitrijevic

Steps to reproduce:

1. Go to new config

https://<ServerID>.shoplogix.com/peconfig/#/

1. Select any machine > Select Variables tab > Edit

2. Select 'Scrap' in drop down

3. Select 'Add Variable'

Expected Result: New variable is added
Actual Result: New variable is not added

The same bug is replicated for the following variables:

• Scrap

• Event

• Setup Stop

• Generic

PNE-748

Blocked Cavity - Job Dialog issues

Reporter: Aleksandar Dimitrijevic

Description

Issue # 1

• Blocked Cavities value cannot be changed in Default or Scheduled job

Steps to Reproduce:

1. Go to any machine > Job List

2. Select any Default or Scheduled job

3. Change Blocked Cavities value > Save

4. Select the same Default / Scheduled job again

Expected Result: Blocked Cavity value is changed
Actual Result: Blocked Cavity value is NOT changed

Issue # 2

• Blocked Cavities option is not displayed in Job dialog, if Job with sub-jobs was previously opened

Steps to Reproduce:

1. Go to any machine > Job List

2. Select any job with sub-jobs --> Blocked Cavities option is not displayed which is expected

3. Close

4. Select another job without sub-jobs or click on New Job

Expected Result: Blocked Cavities is displayed in job dialog
Actual Result: Blocked Cavities is NOT displayed in job dialog

Issue # 3

• If Cycle Factor = Blocked Cavities, there is no production (Good or Blocked) displayed.
  Proposed Solution: Change Blocked Cavities maximum to be Cycle Factor - 1.
  This needs to be discussed with since there are situations when Cycle Factor will be set to '0'.

PNE-749

Blocked is not displayed in Shift Roll Up Total section

Reporter: Aleksandar Dimitrijevic

PNE-755

New Config - issues with Variables

Reporter: Aleksandar Dimitrijevic

Description

Changing Variable Type while Variable Edit is open crashes peconfig
Steps to reproduce:

1. Select any machine > Variables > Edit > Click on Edit sign at the end of Variable row > Change Variable Type outside of Variable Edit screen

Expected behavior: Variable Type is changed
Actual behavior: Blank page is displayed

Time Given (min) is not saved in Downtime, Setup, Scrap, Event, Setup Stop variables
Steps to reproduce:

1. Select any machine > Variables > Variable Type = Downtime > Edit > Click on Edit sign at the end of Variable row > Enter ‘Time Given (min)’ > Save > Refresh

2. Select the same machine > Variables > Variable Type = Downtime > Edit > Click on Edit sign at the end of Variable row

Expected behavior: ‘Time Given (min)’ is saved
Actual behavior: ‘Time Given (min)’ is not saved

Count Type = Cumulative Count is not saved
Steps to reproduce:

1. Select any machine > Variables > Variable Type = Scrap > Edit > Click on Edit sign at the end of Variable row > Set Count Type = Cumulative Count > Save > Refresh

2. Select the same machine > Variables > Variable Type = Scrap > Edit > Click on Edit sign at the end of Variable row

Expected behavior: Count Type = Cumulative Count
Actual behavior: Count Type <> Cumulative Count
Note: There is also a typo ‘Cummulative’ should be ‘Comulative’

• Target, Standard Deviation and Style are not saved in Generic variable

Steps to reproduce:

1. Select any machine > Variables > Variable Type = Generic > Edit > Click on Edit sign at the end of Variable row > Enter value for Target, Standard Deviation and Style > Save > Refresh

2. Select the same machine > Variables > Variable Type = Generic > Edit > Click on Edit sign at the end of Variable row

Expected behavior: Target, Standard Deviation and Style values are saved and displayed.
Actual behavior: Target, Standard Deviation and Style values are NOT saved and displayed.

PNE-756

New Config - issues with Machine States

Reporter: Aleksandar Dimitrijevic

ONE

• Cannot Save changes in Machine States

Steps to reproduce:

1. Select any machine > Machine States > Edit > Click on + sign next to Slow Running/Micro Stoppage > Make any change > Save

Expected behavior: Changes are saved successfully
Actual behavior: Changes are not saved

TWO

• Cannot turn off checkboxes in Micro Stoppage

Steps to reproduce:

1. Select any machine > Machine States > Edit > Click on + sign next to Micro Stoppage > Turn off ‘Accept Automatic Reasons’, ‘Accept User Reasons’ and ‘Accept Machine Reasons’

Expected behavior: Checkboxes are turned off
Actual behavior: Checkboxes stay turned on

THREE

• Cannot make changes in Automatic Setup

Steps to reproduce:

1. Select any machine > Machine States > Edit > Click on + sign next to Automatic Setup

2. Change ‘Setup Stop Condition’ to ‘Production Threshold’ > Enter ‘Production Threshold’, change selection for ‘Automatic Reason Override’ and ‘Enforce Status Reasons’ > Save

3. Refresh > Select the same machine > Machine States > Edit > Click on + sign next to Automatic Setup

Expected behavior: Changes are saved
Actual behavior: Changes are not saved

FOUR

• Cannot select all options in Slow Running/Micro Stoppage > Production Override

Steps to reproduce:

1. Select any machine > Machine States > Edit > Click on + sign next to Slow Running/Micro Stoppage > Click on Production Override

Expected behavior: All 4 options can be selected
Actual behavior: Only first 2 options can be selected
Workaround: Use arrows on keyboard to navigate to rest of the options

FIVE

• Selected Production Override option is displaying different name

Steps to reproduce:

1. Select any machine > Machine States > Edit > Click on + sign next to Slow Running > Click on Production Override > Select ‘All Good’

Expected behavior: ‘All Good’ is displayed as selected option
Actual behavior: ‘CountAsProduction’ is displayed as selected option
Note: All Scrap = CountAsScrap; All Zero = RemoveFromCount

PNE-780

Shift Line - Denominator is not correct due to Unit Conversion

Reporter: Aleksander

Description

Ex: https://qatesting.shoplogix.com/whiteboard/#/shiftline/FFD4D9CF-EFAA-ED58-0298-AD1A4F13C386/start/20200219T132642.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&units=3

• For example on the first hour, denominator = 60750 while it should be the same as on Bottleneck machine (6750)

https://qatesting.shoplogix.com/whiteboard/#/shifthours/FFD4D9CF-EFAA-ED58-0298-AD1A4F13C386/start/20200219T070000.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&units=3

Note: Running job on bottleneck machine have Line Cycle Factor <> Cycle Factor and Units are set to Line.

PNE-217

Paging - As an employee, I want the ability to view all pages from a single plant

Reporter: Steven Arrol

As an employee, I want the ability to view all pages from a single plant so that I can easily determine which pages are still "pending" and which are being worked on.

1.  

   1. The Problem:
      Currently, there is no central place to list all paging message [paging is new functionality]

1.  

   1. Requirements

      1. Develop a UI where the end-user can view all pages, sorted by IN PROGRESS and OPEN

1. The user is able to view all possible details related to that page (machine info, when it was created, the message, the owner, etc.) – whether this is included in the same tabled list, or in a popup modal is on the designer/developer's best judgement.

1.  

   1. Development Tasks

• [ ] Finish design / development of the "Page Analysis" view.

  1. "Page Card" component styling.

  2. List structure styling.

• [ ] Develop functionality to grab all OPEN or IN PROGRESS pages from DB and display in the list.

• [ ] Develop functionality to allow user to change the state of a page (By STARTING / RESOLVING / CLOSING).

1.  

   1. Risks / Assumptions

      1. N/a

1.  

   1. Business Owner
      Manny / Nick

1.  

   1. Related CEX
      HQ-1567133519

PNE-677

Capability for Clients to Configure Blocked Cavities on a Job

Reporter: Steven Arrol

User Story:

I want the ability to configure a machine as having n number of mold cavities within the Shoplogix configuration, so that my machines can properly track their Performance % during a production run.

Background:

CCC is a new customer deal that is currently being finalized. For the deal to close, they require an update to our system:

Their machines have a set number of “cavities” (e.g. Machine A has 10 cavities). Each cavity correlates to the machine’s cycles (for example: in 1 cycle, 10 cavities might produce 10 components).

If >=1 of these cavities is blocked, the output will be affected, and Shoplogix performance monitoring will not accurately reflect what is occurring on the shopfloor.

These cavities will roll up in as fractions of the machine’s Performance metric within OEE.

Requirements:

REQ 1. In the Shoplogix Configuration, provide an interface control (e.g. a checkbox) where an end-user can identify that a machine has multiple cavities.

IF
user flags a machine as having “Multiple Cavities” (multiple cavities = true)
THEN
system to prompt user to input the number of cavities for the machine
(data type: Numeric, Required to save config: true)

Machine is treated as having Multiple Cavities, and the new Blocked Cavities field within the Job List screen’s pop-up is now available to user
ELSE
Machine does not have multiple cavities (default behavior); the Blocked Cavities field within the Job List screen’s pop-up is HIDDEN and not available

REQ 2. When a machine is flagged as having multiple cavities, then the system shall treat each cavity as a fraction of the machine’s total Performance metric for OEE.

Example of how multiple cavities affects OEE’s Performance metric:

• A machine is flagged as having multiple cavities, end-user defines machine as having 8 cavities.

• 1 cavity in the machine now equates to 12.5% of machine’s OEE total Performance %

By default, each cavity should be considered “operational” and available to produce parts.

Example of how multiple cavities affects OEE’s Performance metric:

• A machine is marked as having 8 cavities, and 2 cavities are blocked

• In this scenario, the machine’s Performance OEE will always be:
  {Current Performance %} - { 25% of the expected goal Performance }

• Reason for this: with 8 cavities total, 1 cavity = 12.5% of Performance. With 2 cavities blocked = 25% of unavailable performance.

User Interface requirements:

REQ 1. On the JOB LIST view interface in Whiteboard, make a new field available in the job modal for Blocked Cavities:

REQ 2. Show/Hide behavior of this section:

Default behavior: HIDDEN FROM USER.
IF
End-user flagged Machine as “Multiple Cavities” within the Shoplogix configuration (Multiple Cavities = TRUE)
(see PROD-103: CONFIG - Ability to configure a machine's number of cavities (CCC 1 of 2)REFINE-DONE )
THEN
Show this field in the Machine’s JOB LIST screen
ELSE
HIDE this field

REQ 3. In the CAVITIES section, the Blocked Cavities field allows a user-defined range based on the Cycle Factor.

In other words:

• Min value allowed for Blocked Cavities field = 0

• Max value allowed for Blocked Cavities field = { the value of corresponding Cycle Factor field }

  • Example: if Cycle Factor = 6, user can only increase Blocked Cavities up to and including 6

REQ 4. Blocked Cavities should show up in the following screens:

• Production Summary (example screenshot below)

• Operator Dashboard

• Shift Hourly

• Image Added

  Functionality requirements:

  REQ 5. The number of blocked cavities reduces the possible OEE Performance % during the job’s production run using fractions of the total cavities

  Example scenario if Total cavities = 8, and end-user sets Blocked Cavities = 2

  • During the specified job’s production run, Performance % will always be { Performance % } - 25%

    • Why? because ( 2 / 8 ) * 100 = 25%

    • This means 25% of the machine’s cavities are blocked, and therefore every time the machine attempts to produce parts, 25% of the parts are never made

Acceptance Criteria:

• End-user is able to flag a machine as having multiple cavities

• When multiple cavities is set to TRUE, Blocked Cavities field shows up in the Job List screen view

• User is able to open the JOB LIST modal and interact with a BLOCKED CAVITIES field, only when the same machine is flagged with Multiple Cavities in config

• User is able to increase and decrease Blocked Cavities based on Cycle Factor available cavities

• When n cavities are blocked, they are treated as a constrained fraction of total possible Performance % during the production run of the job.

Business Owner:

Nick and Ian

Original Epic Description Below

User Story:

As an operator/job scheduler, I need the ability to mark how many mold cavities in my machine are BLOCKED, so that my OEE Performance can accurately reflect the max potential performance of my machine during a production run.

Clients need to be able to block a single or multiple cavities in a machine that is configured on a job. Any blocked cavity/cavities will decrease output while maintaining rate. This will cause their overall performance to decrease.

A blocked cavity does not constitute a scrap and is treated purely as a performance indicator.

From a technical outlook, this new metric will be handled as any CycleFactor that Shoplogix has implemented, and will be named BlockedCycleFactor.

This new metric will be displayed on a Shift Period's Type column, and integrated into the Plot Component within that Period as well. First iteration will be implemented on Shift hours as a testing ground.

Image Added

NOTE: For above mock-up, pareto doesn’t make sense to show Blocked. Not in scope.

Architectural Wire frame:

Image Added

PNE-726

Change to Dashboard vi

Current defaults are

Last 10 minutes?
1 minute buckets

Change defaults to

last 60 minutes
5 minute bucketsew default times for all customers

Reporter:

PNE-589

PAGING - As a supervisor, I want to navigate to a screen where I can see all my active "pages"

Reporter: Steven Arrol

Description

User Story

As a supervisor, I want to navigate to a screen where I can see all my active “pages”, so that I don’t need to go through every machine in my plant to find more details about what is going on.

Requirements

REQ 1. In the home page (“/whiteboard”), include a new ICON at the Plant level for “Paging Portal”

REQ 2. In the top-right apps-nav menu, include a new ICON at the Plant level for “Paging Portal”

REQ 3. The Icon should only show if the user is licensed for Messaging Module.

IF
Customer account has Messaging Module LICENSED
THEN
show “Paging Portal” in the Plant-level navigation
ELSEIF
Customer account does not have Messaging Module LICENSED
THEN
show “Paging Portal” in the Plant-level navigation, DISABLED and not clickable, with the “Unlicensed” state

REQ 4. Ensure that the user cannot access the paging portal through a URL
IF
user attempts to access Paging Portal via a URL and the customer account is NOT licensed for Messaging Module
THEN
Page should load with a modal and redirect link. Please see previously created component by Ryan below:

Text for this Redirect Modal:
”Unlicensed Module
The Messaging Module provides your shop-floor operators and supervisors with a fast way to communicate and quickly resolve issues.

• Broadcast messages across your shopfloor for announcements and safety concerns

• Request immediate help at the machine level by paging Quality, Maintenance, Changeover, and other teams

• Receive instant email notifications every time the status of an issue changes”

Buttons available:
“Return To Home” (redirect to=”/whiteboard”
Contact Sales (redirect to=https://shoplogix.com/contact/)

Acceptance Criteria

• User is able to navigate to Paging Portal from home screen (if they have Messaging licensed), via new icon

  • User is able to navigate to Paging Portal from any screen in the Plant-level (if they have Messaging licensed), via new icon

• User cannot access Paging Portal through URL if they do not have Messaging module licensed

Business Owner

Manny

PNE-638

Redesign Machine States graphical component and logic for Micro Stops

Reporter:

Description

Micro Stops should be calculated as a static duration after Running and Slow running.
Visually it should always append the running + slow running chunks and threshold value should not be sorted based on its value, instead always appended to the visual representation as a static chunk.

Micro Stops are clculated separately not based on the last part pulse but more based on duration of the Downtime record. If its set in % it will calculate the duration based on cycle time, and if set in seconds it will look at any DT states less than that threshold in seconds and mark them as Micro Stops.

This logic needs to be redesigned and implemented into the config.

PNE-745

Ability to navigate to OEE Waterfall from whiteboard (new icon and router)

Reporter: Steven Arrol

User Story

N/A --Icon and navigation enhancement

Background

OEE Waterfall has been deployed to some MDLZ servers already and SLX leadership wants to roll this new view out with some limited control over which customers can access it.

Requirements

REQ 1. User must be able to navigate via a new icon from the HOME page

• The icon should be at both the MACHINE and AREA level

REQ 2. User must be able to navigate via an icon in the top-right “Apps Nav” menu

REQ 3. When the user navigates to the OEE Waterfall view, it should default to the last full 24 hours based on shift calendar

REQ 4. The data displayed within OEE Waterfall should be conditional for AREAS:

IF
The area is set up as a LINE
THEN
When OEE Waterfall loads, get data from LINE DATA
ELSE
Get data from MACHINE ROLL-UP

Config toggle to control visibility of icons

REQ 5. Create a new toggle option in SLX CONFIGURATION at the Plant level:

• OEE Waterfall (boolean, ON/OFF). Default value = OFF

IF
”OEE Waterfall”” toggle = TRUE ( on )
THEN
OEE Waterfall icons appear within SLX whiteboard (both at the home page, and accessible with apps-nav)
ELSE
OEE Waterfall icons do not appear within SLX whiteboard

Relevant History

Ali Sanaknaki (Unlicensed) was the lead designer of the current icon set

Acceptance Criteria

• New config toggle at the PLANT LEVEL

• Config toggle controls SHOW/HIDE of OEE Waterfall icons (default = hide)

• User can access OEE Waterfall through home page (tree view) or through apps nav

• User experiences the correct Area-level data set (Line data vs. Machine rollup)

Business Owner

Manny