PNE-1762

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

• Noticed saas142 was having troubles (CPU high, no batches completing)

• Investigated, found saas142 continually restarting, with no stack-trace

• Event log claimed process restarting with `exception code 0xc00000fd`

• exception code 0xc00000fd = stack overflow

• Confirmed via MDbg that it was a stack overflow during some Npgsql operation

• Adding trace statements, confirmed it was during `BuildQualityResponse::UpdateSpcRecordConfigurations`

CS-7446

CS-7446: CAM - PR-8088-setup logic do not work correctly - Ended sooner than expected

Actual Behaviour

Setup state on the machine ended sooner than anticipated.

Detailed Investigation Steps

Investigated the current configuration of the setup state. Setup ends when machines runs at 90 parts/min for 6 minutes or runs at 90 parts/min and there is a Splice signal for 3 minutes. Neither of the conditions were met but setup still ended.

OPCcombine log shows that the machine ended setup early at 17:17 https://saas141.shoplogix.com/Web/query.axd?type=opccombined&start=20210323&machines=28900CED-2B5D-4D7E-4C03-E77BC1439376

Expected Behaviour

Setup should have ended at 17:50 when the splice signal was received and there machine was running at speeds about 90 parts/min for over 3 minutes

Steps to Reproduce

Review machine production during the time the setup ended to validate the speed and time conditions to end the setup.

CS-7340

CS-7340: API Endpoint Chronotype Reasons not showing Group

The new Chronotypes endpoint option for Reason does not show the Group for the Reason.
It is listed in the schema.

<xs:complexType name="reasonType">
<xs:attribute name="MachineId" type="xs:string"/>
<xs:attribute name="MachineName" type="xs:string"/>
<xs:attribute name="Start" type="slxDateTime"/>
<xs:attribute name="End" type="slxDateTime"/>
<xs:attribute name="Name" type="xs:string"/>
<xs:attribute name="Group" type="xs:string"/>

CS-7320

CS-7320: API Call Reason No Group Data

Description

<Reason Name="Wait For CIP Tank Available" Classification="Capacity" Duration="0.089205833333333331" Occurences="8"/>

Saas39

The configuration has CIP, Method in the Group field in the configuration. But that is not showing up in the output at this time.

From the API document

reasons: When the reasons option is specified the resulting metrics will include a summary of what reasons occurred. For each reason the following will be included:
name: The reason’s name.
group: The reason’s group.
classification: The reason’s classification.
duration: The reason’s duration in hours.
occurrences: The reason’s occurrences.

5.0.1237.16752 is the version, can’t insert it in the Affects field.

Sample URL

https://saas39.shoplogix.com/web/api/export/summary?start=20210201&end=20210202&metrics=,states,reasons,statereasons&groupBy=Machine&format=xml

CS-4264

CS-4264: Breaks not visible

Hi I cannot see the automated breaks for which there was already a ticket for the shift syste.

Can you please check at the machine the config ?

BR Falzbank(Linie 1)/Seaming L1
BR Außenlack/Paint Booth L1
BR Verschließanlage/Closing Unit L1
BR Falzbank (Linie 2)/Seaming L2

PNE-1768

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

See Prod-244:

Events are a more granular data capture of a machine’s complete activity. They are considered more detailed than downtime reason metrics.

Example:

An EVENT could be “machine door open”. Any time machine x’s machine door opens, the event ID turns TRUE, at which point a START time is captured. When the event ID’s state toggles to FALSE again, an END time is captured (and on the plant floor, the machine’s door closed).

Using this low-level Event data, SLX end-users can also create an AUTOMATIC DOWNTIME with a reason of “Machine Door Open” with these common conditions:

• Event ID “machine door” === TRUE

• && machine state === IDLE

Although these sound the same, EVENT DATA DOES NOT ALWAYS EQUATE TO MACHINE STATE CHANGES.

With this in mind, the EVENT of “machine door open” may trigger 35 times in an hour, where an AUTOMATIC DOWNTIME (like above) may only trigger 12 times in the same hour.

This extra level of detail provides some customers with a better understanding of what is occurring with their machines.

Requirements

REQ 1. Pull in the following existing data metrics (currently available in Flash reports):

• Event Name

• Event Group

• Event Classification

• Bucket Time of 1 hour – Event Duration

• Event Occurrences (count of an event being triggered)

REQ 2. Must be able to calculate the following time-based metrics (Ben, we’ll chat about what works best here as these are calculated metrics and may be completely made within Analytics Portal):

• Event instance TOTAL DURATION

  • In Flash reports, currently when an Event (e.g. “machine door open”) ID state turns to TRUE (event triggers), a START time stamp is captured. When the same Event toggles back to a FALSE state, its instance END time stamp is captured.

  • Each of these START and STOP times per event instance get added up to display to a total “DURATION” metric for the overall Event Name.

• Event instance AVERAGE DURATION

  • This metric is simply the average duration length of all START and END times of an Event

REQ 3. Pull in and include the Event data’s colour configurations within the Analytic Portal’s existing colors plugin functionality.

• Currently, SLX end-users configure custom colour codes within the SLX config for each Event. The functionality of bringing these colour codes in should be an addition to the work already done with the SLX colours plugin (which currently includes machine states, reasons, etc.)

PNE-1766

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

ERP Classifications required to be included as attributes in the metric element. Since this requirement was unknown and because future formats will be unknown the most flexible options is to provide the ability to apply an XSL Transformation.

URL:

https://saas141.shoplogix.com:443/web/api/export/summary?start=20210315T060000.000&amp;end=20210315T140000.000&amp;metrics=total,uptimehours,downtimehours,scrap,statereasons,setuphours,setupscrap,erpclassifications&amp;groupby=machine,JobInstance&amp;format=xml&amp;areas=90

Sample of Desired Metrics Element:

PNE-1738

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

See NFR for details: https://slxdev.atlassian.net/browse/NFR-641

Acceptance and testing:

Ensure that SetupScrap and ErpClassifications are available in all Data Export API Job Endpoints

PNE-1722

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

Builds working as expected, performance improved, historical data loaded as expected.