Page Comparison

PROD-280

https://slxdev.atlassian.net/browse/PROD-280

SLX leadership recently presented the Paging beta to the potential customers. They are still interested but have 3 main concerns that they say need to be addressed:

• The paging banner is not prominent enough for across the shop-floor

• Each customer wants their own unique group of Paging recipient departments (e.g. Changeover, Quality, Maintenance team, etc.)

• Customers want to trigger pages (trigger them ON) based on an OPC tag

These items are part of this Epic, attached as Issues below.

How this workflow looks in the context of our application

1. Production supervisor configures and manages their group of “responders” to a shop-floor issue ( https://slxdev.atlassian.net/browse/PROD-281 )

2. Production supervisors also want to ensure that not only can pages be triggered near a computer, but also through their own industrial “OPC Events” (e.g. hitting a button on a forklift, etc.) ( https://slxdev.atlassian.net/browse/PROD-296 ).

3. Production supervisor wants some of their TVs to essentially “block” viewers from seeing any other metrics until a page is responded to ( https://slxdev.atlassian.net/browse/PROD-279 )

   For other TVs, the supervisor is OK with regular paging functionality

PROD-243

https://slxdev.atlassian.net/browse/PROD-243

Dev Refine results:

• probably acceptable difference from original report: We can’t provide every 15min for this data. Every hour is best we can do. This is due to the bucketing strategy we use for coredata (hourly).

• Investigated cost per (X) where X is (electricity, water, gas):

  • Export three values onto Dim Machine seems fine. 0 by default.

• Test with machine: https://qatesting.shoplogix.com/web/query.axd?type=coredata&machines=XMLCN_Simulator&start=20201110T090000.000&end=20201111T110000

  • two birds one stone: restore QA13 and copy QATesting’s data…

Acceptance Criteria:

• [Fact Core] 3 new fields:

  • Electricity

  • Water

  • Gas

• [Fact Core Line] will NOT include the 3 new fields.

• [Dim Machines] 3 new fields:

  • Electricity Cost

  • Water Cost

  • Gas Cost

  • Could add unit to each of these: “Per kWh”, “per L”, “per cubic meter”, respectively. Let me know which you prefer

• model _v00012 will contain the changes.

Server Example: saas124

Engineer: Francisco Salgado

Area/Machines: All the filler machines in Industrias Licoreras - Daily or Monthly

Reports: All reports should be moved to analytics. This includes: Consumption Table, Electricity Usage, Electricity Machine Rollup, Job Electricity Scatter

*Connected to core data

Missing Variables

• Electricity (kWh)

• Water (L)

• Gas (Cubic Meter)

• Expected Consumption - comes from jobs

• Cost per Unit of Measurement - INVESTIGATE (This could be built into the dashboard and saved - Can be with machine type) - WE KNOW comes from machine config

Calculated Variables

• Electricity ($)

• Water ($)

• Gas ($)

• Min, Max

More Information:

Consumption Table: Shows consumption of energy every 15 mins during one shift, as electricity usage in kWh, with start and end time.

Electricity Usage: Electricity consumption (kWh) during one shift, during unscheduled time, and total consumption (sum of shift + unscheduled)

Electricity Machine Rollup: Rollup of electricity usage by line

Job Electricity Scatter: Hover over this to see Energy> Electricity → Only way for users to see how much electricity an order (/job) uses → would prefer to have this in a table

Image Removed

Image Added

PROD-242

https://slxdev.atlassian.net/browse/PROD-242

Dev Refine:

• [Fact Core] add:

  • Inventory Name (hidden)

  • Inventory Consumed

• [Dim Inventory] create wit these columns:

  • Inventory Name

  • Inventory Start DateTime

  • Inventory End DateTime

  • Inventory Start Level

  • Inventory End Level

    • (note to self: inventory 0 is most common… but you could scan in a non-zero number… think coil consumption).

  • Inventory Filters 1-5 – Renamable! Translatable! in flash… we can use translations in analytics when thats ready…

    • (107’s example: PO/ItemNumber, etc, were all filters).

• We suspect default inventory records apply before coredata anyway, but wanted to mention they should play nicely.

Server Example: saas107

Report: Inventory Yield Summary

Machines/Areas: Any of the CTL devices in the Steel Drum Group - Weekly Report

Engineer: Brock

New Variables

• Inventory ID

• Inventory Filters 1-5

• Start of inventory record (time)

• End of inventory record (time)

• Start (Level)

• End (Level)

Calculated Variables

• Consumed (Level) - ( Inventory Cycle Factor x Pieces produced )

• Expected (Yield) - ( (start - end)/inventory cycle factor )

• Total (% Yield) - Total pieces made/Expected

• Good (% Yield) - Good pieces made/Expected

• Duration - ( Start time of inventory job - end time of inventory job )