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!


Linux Package Signing Key Rotation

All signed InfluxData Linux packages have been resigned with an updated key. If using Linux, you may need to update your package configuration to continue to download and verify InfluxData software packages.

For more information, see the Linux Package Signing Key Rotation blog post.

InfluxDB Cloud backed by InfluxDB IOx

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by IOx, this is the correct documentation.

If powered by TSM, see the TSM-based InfluxDB Cloud documentation.

InfluxDB Cloud backed by InfluxDB TSM

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine which enables nearly unlimited series cardinality and SQL query support. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by TSM, this is the correct documentation.

If powered by IOx, see the IOx-based InfluxDB Cloud documentation.

State of the InfluxDB Cloud (IOx) documentation

The new documentation for InfluxDB Cloud backed by InfluxDB IOx is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.