Reference · built on requestConnectorPLC, SCADA & MES

Oden

Line, run, batch, and state intervals, scrap and yield, targets, and OQL metrics from the Oden API v2.

About

Oden is a manufacturing analytics platform for process lines, published by Oden Technologies. Its API v2 at https://api.oden.app/v2 models an organization's factories, lines, and machines; runs, batches, and states as intervals; products and targets; scrap and yield records; quality tests; and metrics collected from machine tags. Every endpoint is a POST of the form /v2/{object}/{action} with the actions search, set, and delete, and POST /v2/oql/query runs Oden Query Language.

Through Fibric, an operator queries OEE, availability, and scrap by line with OQL on a schedule, then proposes what follows: a reason on a downtime state, a scrap record on a batch, or a maintenance work order tied to a line. You sign off on each one. Each write goes once and leaves a receipt.

This is a reference listing. It documents what Fibric would read from Oden and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Factories, lines, and machine groups through /v2/factory/search and /v2/line/search
  • Runs, batches, states, and custom intervals through /v2/interval/search, by id, by start_time and end_time, or with match: last
  • State categories and state reasons, such as downtime and why it happened, through /v2/state_category/search and /v2/state_reason/search
  • Scrap and yield records per run or batch through /v2/scrap_yield/search, and quality tests through /v2/quality_test/search
  • Products, product mappings, and targets with upper and lower thresholds through their search endpoints
  • Aggregations such as aggregation.oee, aggregation.availability, aggregation.scrap, and metric_group values through POST /v2/oql/query
  • Maintenance work orders linked to a line through /v2/maintenance_work_order/search

Proposed actions

  • Target capability: propose a state reason or comment on a downtime interval through /v2/interval/update
  • Target capability: propose a scrap or yield record with a scrap code on a run or batch through /v2/scrap_yield/set
  • Target capability: propose creating or updating a maintenance work order on a line through /v2/maintenance_work_order/set
  • Target capability: propose a target value with upper and lower thresholds for a product on a line through /v2/target/set

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Name the reason for each downtime

    States in the downtime category without a reason are listed each shift. The operator drafts a reason from nearby metrics and events and proposes /v2/interval/update, one state at a time.

    With Line Downtime

  • Watch OEE by line, daily

    An OQL query groups aggregation.oee by line.name with bucket 1D. The operator flags lines whose trend falls and attaches the availability, performance, and quality components it read.

    With OEE Loss, KPI Drift

  • Raise a work order from a repeating fault

    When the same state reason recurs on a line, the operator proposes a maintenance work order with an external_id for your CMMS and the interval ids it used.

    With Predictive Maintenance

  • Catch scrap outside its target

    Scrap per batch is compared with the run's target and its thresholds. Above the upper limit, the operator proposes a review note and files the scrap records behind it.

    With Scrap Rate, Batch Deviation

Requirements

  • An Oden organization and an API token that Oden issues for it
  • Line and factory ids or names; some endpoints must be called per line or factory, so request counts grow with the number of lines
  • Timestamps in ISO 8601 form, YYYY-MM-DDTHH:MM:SSZ, on every POST body
Authentication
A token issued by Oden, sent on every request as Authorization: Token <credentials>; an invalid token returns 401 and one without access to the data returns 403.

Limits

  • Oden states it does not rate limit today but will, and asks clients to stay at or under one request per second
  • The v2 specification lists no webhook or push endpoint; intervals and states are found by polling with start_time and end_time
  • Scrap and yield for an interval is the sum of its records; correct it with an offset record or by updating one
  • OQL does not support plain UNION, or GROUP BY with WINDOW in one query; use UNION ALL or a helper query

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Oden ↗

Questions and answers

What does an Oden request look like?
A POST to https://api.oden.app/v2/{object}/{action}, for example /v2/factory/search, with a JSON body and Authorization: Token <credentials>. POST is the only HTTP method: search reads, set creates or updates, delete removes. Responses are JSON with ISO 8601 timestamps and durations.
What is OQL?
Oden Query Language, a SQL-like language for factory data. Every query starts with aggregate, takes a where time from ... to ... range, and can group by line.name or bucket 1h. It runs through POST /v2/oql/query and in the OQL Tester and Forge inside the Oden platform.
Does Oden rate limit?
Not under the current implementation, according to the API description. Oden says rate limiting will be introduced and recommends clients stay at or below one request per second. The OQL query endpoint already defines a 429 Too Many Requests response.
Ask about Oden

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.