Walnut Labs Connected factory demo
walnut labs

Inside the connected factory

Scan. Fill.
Check. Trace.

Follow a batch from the ERP to the Production Record. Open the services below as we walk through the integration.

Service links use the configured demo hostnames. ERPNext and Dagster require an authorised sign-in. Availability is not monitored here.

Your demo workbench

01 — 03 / Connected services
01 / SOURCESign-in required

ERPNext

Start with the manufacturing facts: work orders, bills of material, component lots and quality results.

The source of record
Open ERPNext (new tab)
02 / PIPELINESign-in required

Dagster

Follow the refresh from ERP data to curated tables. Inspect run history and the checks behind the data.

Ingest, transform & test
Open Dagster (new tab)
03 / INTEGRATIONAPI reference

Production Record API

Explore capture fields, engineering endpoints, authentication and response examples in the Swagger reference.

Manufacturing calls require Basic auth
Explore API documentation
The final stop: Production records

During a guided demo, open the configured production record and perform the scan steps. Your presenter will provide access to the record system.

How the systems connect

Enterprise data, at the point of use.

  1. ERPNextWork orders & lots
  2. dltIncremental extraction
  3. Iceberg + dbtVersioned & tested
  4. Trino + FastAPIRead-only serving
  5. Production recordsCapture & check

Dagster orchestrates the refresh. The record system requests data when the operator scans. The integration does not write back to the ERP.

The live demonstration

Follow one batch.
See every decision.

Follow the journey from source data to a checked production record. Use the batch and work-order identifiers from the current demo dataset.

All company, product and manufacturing records in this scenario are fictional.

  1. Issue the materials

    In ERPNext, inspect the work order and its component lots, then follow the presenter’s material issue.

  2. Refresh and verify

    In Dagster, inspect the pipeline run and confirm that the relevant data checks passed.

  3. Scan a good batch

    In the demo production record, scan the selected batch. Observe the captured fields and passing checks.

  4. Catch an expired batch

    Scan the expired example at the record step. Observe the failed expiry check and the visible message.

  5. Trace the answer

    With the presenter, find the request in the audit log and inspect the source snapshot behind the response.