Everything needed to deploy and operate Anodela

Written for controls engineers, process engineers and IT/OT teams. Start with the edge runtime, then connect your systems and arm your first envelope.

Overview

Anodela runs as a factory-edge control loop. The edge runtime hosts perception pipelines and agent policies; the control plane handles model governance, fleet updates and reporting. In on-prem mode the control plane runs inside your network and the loop never leaves the site.

Three concepts matter before anything else: agents own a step of the line, envelopes define what an agent may do without a human, and the twin validates every envelope before it can be armed.

Install the edge runtime

The runtime ships as a signed bundle for K3s on Jetson or IGX hardware. Bundles are reproducible and can be inspected before installation.

Connect your systems

Connectors are declarative. You point Anodela at a source, choose read or write scope, and the platform validates the schema and clock alignment before any agent is allowed to observe or act on it.

  • Coating and calendering PLC/SCADA tags over OPC UA
  • Inspection cameras and gauges via the edge perception pipeline
  • Formation and grading cyclers, plus MES batch and genealogy records
  • Historian backfill so the twin starts from your real process history

Install and register an edge node

The installer verifies the bundle signature, registers the node against your tenant and pulls the model set pinned to your line.

install.sh
# Verify and install the signed edge bundle
anodela bundle verify anodela-edge-2026.7.tar.zst
anodela edge install --bundle anodela-edge-2026.7.tar.zst \
  --tenant acme-cells --site plant-2 --line electrode-3

# Confirm health and pinned model versions
anodela edge status --line electrode-3

The four things to understand

Agents

A bounded control loop with grounded perception, an approved action space, a simulation gate and an immutable record.

Envelopes

The precise setpoints, ranges and conditions under which an agent may act without a human approver.

Digital twin

As-built simulation of coating, calendering, assembly and formation that validates envelopes and predicts yield.

Cell genealogy

The graph linking every cell to its roll, coating zone, slitter, weld station, fill batch and formation channel.

Connect coating, inspection, formation and MES

Connectors are declared as configuration and validated before they are allowed to write. Read access can be enabled immediately; write access requires an armed envelope.

connectors.yaml
line: plant-2/electrode-3
connectors:
  - type: opcua        # coating & calendering PLC
    endpoint: opc.tcp://coater-3.plant2.local:4840
    mode: read_write
    envelope: coat-calender/qualified-v14
  - type: vision       # 12 cameras + inline CT
    vendor: cognex
    mode: read
  - type: mes
    vendor: opcenter
    mode: read_write

Envelope fields

An envelope is the contract between your quality team and the agent. It is version-controlled and every change is recorded with a named approver.

FieldMeaningExample
setpointThe controller variable the agent may changedie_gap_um
rangeAbsolute or relative bounds for autonomous action±8 µm
conditionsPreconditions that must holdchemistry = NMC-811, recipe rev ≥ 14
validationTwin scenario set that must passcoat-calender/scenarios-2026-Q2
fallbackBehaviour on loss of confidence or connectivityhold last safe setpoint, alert
approverNamed quality ownersite quality engineer

The daily loop for a process engineer

  1. Review

    Work the proposal queue: evidence, citation, twin result, approve or reject with a reason.

  2. Watch

    Track the accuracy scoreboard against your own baseline per agent and per shift.

  3. Adjust

    Tighten or widen envelopes as confidence changes — every change is logged.

  4. Export

    Generate audit and evidence packs for internal quality or customer audits.

Deeper material

API reference

Resources, schemas, pagination, idempotency keys and rate limits for every endpoint.

Edge runtime

Hardware sizing, camera and CT throughput, network requirements and offline behaviour.

Audit & evidence

Record structure, retention, export formats and mapping to IATF 16949 and IEC 62660.

Twin scenarios

Authoring, validating and versioning scenario sets for a line or chemistry.

Security

Isolation model, key management, deployment modes and vulnerability handling.

Metrics

Definitions for first-pass yield, scrap, formation cost and takt as Anodela computes them.

Operating envelope of the platform

50–250 msInspection-to-decision target
8–24Cameras per line supported
10–50Models served per factory
7 yrDefault audit retention

Export an audit pack

Evidence packs bundle every action, approval and genealogy link for a period or a cell range, signed and ready for an auditor.

audit-export.sh
anodela audit export --line electrode-3 \
  --from 2026-04-01 --to 2026-06-30 \
  --include proposals,approvals,executions,genealogy \
  --format pdf,jsonl --sign

Built for the assurance bar of battery manufacturing

Cell manufacturing is safety-critical and IP-dense. Anodela is designed so quality, IT/OT and EHS approvers can say yes.

SOC 2 & ISO 27001

SOC 2 Type II program with encryption in transit and at rest, SSO/SAML, SCIM and RBAC down to the line.

IP & recipe protection

Chemistry, coat-weight and formation recipes stay in your tenant. Optional fully on-prem deployment with no egress.

Assurance-grade audit trail

Every perception, proposal, approval and executed setpoint change is immutably logged for IATF 16949 and IEC 62660 evidence.

Data residency

EU, US, Korea, Japan and China-domestic regions, or air-gapped factory edge for sovereign programs.

Documentation questions

Typically one IGX or Jetson Orin class node per line for 8–24 cameras, plus additional capacity for inline CT fusion. Sizing is confirmed during the assessment.

Yes. Scenario sets are version-controlled artefacts; your process engineers can extend them and gate envelopes on the extended set.

The full OpenAPI specification is provided with API access, alongside the sandbox line for building against realistic data.

Get API access and a sandbox line.

We will provision credentials, the OpenAPI spec and a simulated line seeded with real defect patterns.