Knowledge base

Formulas

This section details the various formulas used to calculate statistics displayed in the console.

Overall Equipment Effectiveness (OEE)
OEE = ((Reported Bales × Ideal Cycle Time) / Planned Production Time) × 100

Calculates the overall equipment effectiveness as a percentage, measuring how efficiently the machine is operating compared to its theoretical maximum capacity.

Components:

  • Reported Bales: Total number of bales produced during the shift
  • Ideal Cycle Time: The theoretical minimum time to produce one bale under perfect conditions
  • Planned Production Time: Total shift time minus scheduled breaks

Total Time
Total Time = (Timestamp of end message) - (Timestamp of start message)

Calculates the total duration of a shift by finding the time difference between the shift's start and end messages.

Planned Production Time
Planned Production Time = (Total Time) - (Operator break time)

Calculates the time planned for production by subtracting operator break time from the total shift time.

Downtime
Downtime = Sum of all downtimes in shift where the downtime type is not Operator

Calculates the total duration of non-operator-related downtime events during a shift.

Operator Stoppage Time
Operator Stoppage Time = Sum of all downtimes in shift where the downtime type is Operator

Calculates the total duration of operator-initiated stoppages during a shift.

Runtime
Runtime = (Total Time) - (Downtime) - (Operator Stoppage Time)

Calculates the actual running time of the machine by subtracting all downtime and operator stoppages from the total shift time.

Cycle Performance
Cycle Performance = (Total Run Time) / (Total Bales Reported)

Measures the average time taken to produce each bale during the runtime period.

Metric Tonnes Per Hour
Metric Tonnes Per Hour = (Total Production) / (Total Run Time in seconds / 3600)

Calculates the production rate in metric tonnes per hour by converting the total runtime to hours and dividing the total production by this value.

Total Weight

If total weight reported by press:

Total Weight = Reported Weight

Otherwise:

Total Weight = (Total Reported Bales) × (Average Bale Weight)

Calculates the total weight processed during a shift, either using the directly reported weight or calculating it from the number of bales and average weight.

Total Production
Total Production = Total Weight × (press' selected ton type's conversion value)

Converts the total weight into the appropriate unit of production based on the press's configured ton type.

Average Output Weight
Average Output Weight = (shift's reported output average bale weight) / (press' selected bale counter type's multiplier)

Calculates the average weight of output bales, adjusted by the press's bale counter type multiplier.

Total Output Production
Total Output Production = (Total Reported Bales) × (Output Average Bale Weight) × (press' selected ton type's conversion value)

Calculates the total output production based on the number of bales, their average weight, and the press's ton type conversion.

Stack

Stack = Read values from one of the following message types:

  • Message Type 1040: Read items with type ID between 23 and 70
  • Message Types 1048/1049: Read items with type ID between 23 and 70
  • Message Type 2506: Read items with type ID between 23 and 70

Components

  • Message Type 1040:
    • Primary message type for stack data
    • Items with type IDs 23-70 contain stack values
  • Message Types 1048/1049:
    • Alternative message types for stack data
    • Used when type 1040 is not available
    • Items with type IDs 23-70 contain stack values
  • Message Type 2506:
    • Fallback message type for stack data
    • Used when neither 1040 nor 1048/1049 are available
    • Items with type IDs 23-70 contain stack values

Description

This formula retrieves stack data by checking for specific message types in order of priority. It first looks for message type 1040, then 1048/1049, and finally 2506. For each message type found, it extracts values from items whose type IDs fall between 23 and 70, which represent various stack measurements and parameters.

Sales

Sales calculation:

  1. If message type 1041 exists:
    • Read values from items with type ID between 23 and 70
  2. If no messages of type 2501 exist in the shift:
    • Return 0
  3. If the last 2501 message does not have an item type of 17:
    • Return 0
  4. Otherwise:
    • Return the value of item type 17

Components

  • Message Type 1041:
    • Primary message type for sales data
    • Items with type IDs 23-70 contain relevant values
  • Message Type 2501:
    • Required for sales calculation
    • Must contain item type 17
    • Last occurrence in shift is used

Description

This formula calculates sales data by first checking for message type 1041 and reading specific item values. The calculation depends on the presence of type 2501 messages and specifically requires item type 17 from the last 2501 message in the shift. If any of these conditions are not met, the sales value defaults to 0.

Product

Product calculation:

  1. If message type 1042 exists:
    • Read values from items with type ID between 23 and 70

Components

  • Message Type 1042:
    • Primary message type for product data
    • Items with type IDs 23-70 contain relevant values

Description

This formula retrieves product data by checking for message type 1042 and reading values from items whose type IDs fall between 23 and 70. These items contain various product measurements and parameters.

Kickouts

Kickouts calculation:

  1. If message type 2508 exists AND has item type 22:
    • Return the value of item type 22
  2. Otherwise:
    • Return the total count of messages with type 2505

Components

  • Message Type 2508:
    • Primary message type for kickout data
    • Item type 22 contains the kickout count
  • Message Type 2505:
    • Fallback message type for kickout data
    • Each message represents one kickout event

Description

This formula determines the number of kickouts by first checking for a type 2508 message with item type 22. If found, it uses that value. Otherwise, it falls back to counting the total number of type 2505 messages as each represents a kickout event.