PROD-141

Allow scorecard to replace OEE / OEEc with Availability Metric

allow scorecard to replace OEE /OEEc with Availability Metric

Be able to select in settings the ability to use OEE, OEEc, or Availbility in the comparative charting and ranking of lines areas and facilites

“Also it would be great if the Scorecard could go down to area and line level like the new app”

Added last request to new feature request: https://slxdev.atlassian.net/browse/PROD-143

TESTING:

New availability option in settings that function just like OEE and OEEc. third gauge is now Capacity. There is only Machine Status Summary if Availability Selected

PROD-134

Update WalkMe for Maintenance Window alerts

User Story

N/A

Background

SLX is moving away from solely reactive maintenance work on servers to scheduled, bi-weekly server maintenance. Brandon and Dan Follows are working on creating a schedule, which they want to make available to our customers within the application itself. This will help calm customers if they are experiencing less-than-ideal network experience on SLX. They will be able to check whether they are currently being affected by a scheduled maintenance time, and will ideally try to work around it.

Requirements

REQ 1. Update production servers with the latest Walkme packaged folder attached here.

Acceptance Criteria

1. There should be a pop-up alert that appears once, on the home page of SLX, alerting the user of the new schedule.
   Example:

Image Added

When the user clicks either option, a frame will appear showing the maintenance time periods in an iFrame Google Doc (fully aware that this is not an ideal user experience, but the most practical way for someone like Brandon to quickly update time slots without DEV intervention).

1. If user closes pop-up, they should be able to access the maintenance times again on their own, at any time, using the WalkMe help menu:

Image Added

Business Owner

Dan F. / Brandon

PNE-797

OSI PI/Generic REST JSON Connector Integration for Altium

— At the Altium pilot we were using Boomi to integrate with OSI Pi two issues with this is they don't sample more than 1 time per minute which limits our slow running and Microstop analytics from working correctly. 2nd is Boomi wants their partner deal and are threatening to shut us off

• Nick Marchioli

OSI PI provides a REST/JSON API

https://techsupport.osisoft.com/Documentation/PI-Web-API/help.html

The rough idea is that it would be good to have a connection type available that could talk to REST/JSON endpoints. Currently we have OPC, ModBus and MQTT (in beta) that can be configured, REST/JSON? could be a third.

Very rough idea on generalizing solution would be

• store perhaps the URL pattern / authentication in the OPC Server ID section of a machine's configuration

• store JSON path queries as the OPC IDs

But the short term deadline though is to get the specific signals that Altium needs from OSI PI and write them in the OpcCore format and paths so that the connector websocket process (Shoplogix.Connector.Realtime) will send them. So this would be a separate process (EXE) on the connector.

Initial Simplification

Manny Bonilla is looking for ways to minimize risk/timeline and has suggested the following approach

• Assume we have “Unique IDs”, don’t do first query, configuration will contain unique ID (base64’ish value)

• Just go direct to second query for these to save the complication of the first query