Documentation

oee.computeAPQ() function

oee.computeAPQ() is experimental and subject to change at any time.

oee.computeAPQ() computes availability, performance, and quality (APQ) and overall equipment effectiveness (OEE) using two separate input streams: production events and part events.

Output schema

For each input table, oee.computeAPQ outputs a table with a single row and the following columns:

  • _time: Timestamp associated with the APQ calculation.
  • availability: Ratio of time production was in a running state.
  • oee: Overall equipment effectiveness.
  • performance: Ratio of production efficiency.
  • quality: Ratio of production quality.
  • runTime: Total nanoseconds spent in the running state.
Function type signature
(
    idealCycleTime: A,
    partEvents: stream[B],
    plannedTime: C,
    productionEvents: stream[D],
    runningState: E,
) => stream[{
    F with
    runTime: H,
    quality: float,
    performance: float,
    oee: float,
    availability: float,
    _time: G,
    _stop: G,
}] where B: Record, D: Record, E: Equatable

For more information, see Function type signatures.

Parameters

productionEvents

(Required) Production events stream that contains the production state or start and stop events.

Each row must contain the following columns:

  • _stop: Right time boundary timestamp (typically assigned by range() or window()).
  • _time: Timestamp of the production event.
  • state: String that represents start or stop events or the production state. Use runningState to specify which value in the state column represents a running state.

partEvents

(Required) Part events that contains the running totals of parts produced and parts that do not meet quality standards.

Each row must contain the following columns:

  • _stop: Right time boundary timestamp (typically assigned by range() or window()).
  • _time: Timestamp of the parts event.
  • partCount: Cumulative total of parts produced.
  • badCount Cumulative total of parts that do not meet quality standards.

runningState

(Required) State value that represents a running state.

plannedTime

(Required) Total time that equipment is expected to produce parts.

idealCycleTime

(Required) Ideal minimum time to produce one part.


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Read more

InfluxDB v3 enhancements and InfluxDB Clustered is now generally available

New capabilities, including faster query performance and management tooling advance the InfluxDB v3 product line. InfluxDB Clustered is now generally available.

InfluxDB v3 performance and features

The InfluxDB v3 product line has seen significant enhancements in query performance and has made new management tooling available. These enhancements include an operational dashboard to monitor the health of your InfluxDB cluster, single sign-on (SSO) support in InfluxDB Cloud Dedicated, and new management APIs for tokens and databases.

Learn about the new v3 enhancements


InfluxDB Clustered general availability

InfluxDB Clustered is now generally available and gives you the power of InfluxDB v3 in your self-managed stack.

Talk to us about InfluxDB Clustered