Documentation

oee.APQ() function

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

oee.APQ() computes availability, performance, quality (APQ) and overall equipment effectiveness (OEE) in producing parts.

Provide the required input schema to ensure this function successfully calculates APQ and OEE.

Required input schema

Input tables must include 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.
  • partCount: Cumulative total of parts produced.
  • badCount: Cumulative total of parts that do not meet quality standards.

Output schema

For each input table, oee.APQ outputs a table with a single row that includes 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
(
    <-tables: stream[D],
    idealCycleTime: A,
    plannedTime: B,
    runningState: C,
) => stream[{
    E with
    runTime: G,
    quality: float,
    performance: float,
    oee: float,
    availability: float,
    _time: F,
    _stop: F,
}] where C: Equatable, D: Record
For more information, see Function type signatures.

Parameters

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.

tables

Input data. Default is piped-forward data (<-).


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: