Documentation

Everything neededto deploy, operateand audit.

In brief

Written for the four people who actually run a Weldeon deployment: the integrator, the welding engineer, the inspector and the operations director.

Next step
Request full accessSee the API
Contents

The documentation set

Nine books. The first three cover ninety per cent of a deployment.

  1. 01

    Integration guide

    Controllers, power sources, sensors and MES. Network topology, appliance placement and the two-week integration plan.

  2. 02

    Envelopes and procedures

    How a qualified WPS becomes an enforced envelope, who owns it, and how changes are reviewed and recorded.

  3. 03

    Inspection workflow

    How machine calls reach your inspector, how acceptance is recorded, and how adjudication feeds model improvement.

  4. 04

    Digital twin setup

    Part import, material behaviour, fixtures and restraint, and calibrating the twin against welds you have already measured.

  5. 05

    Genealogy schema

    Every field, its provenance, its retention and its export format.

  6. 06

    Operations runbook

    Shift start, stop policy, escalation, and what to do when a cell drops to advisory.

  7. 07

    Security and access

    Roles, authorities, sync policy, network segmentation and support-session handling.

  8. 08

    Scorecard and measurement

    Baseline design, metric definitions and the review protocol.

  9. 09

    Release and rollback

    Version pinning, staged rollout across an edge fleet, and single-action rollback.

Operate

The command line, day to day

The CLI is how most shop-floor engineering teams check state, pull a weld record and confirm what the platform did.

shell 
$ weldeon site status --site bay-3
edge appliance    online   runtime 2026.03.1   uptime 41d
cells             6 connected   4 autonomous   2 advisory
loop latency      18 ms p50 · 27 ms p99
cloud sync        disabled (air-gapped)
pending export    0 records

$ weldeon weld show 4471-A --format genealogy
wps               D1.1-GMAW-3G-06        qualified
consumable        ER70S-6 lot 88214      verified
fit-up            gap 1.8 mm rev 07      in tolerance
heat input        1.24 kJ/mm             within WPS
passes            5 (root + 4 fill)      complete
ndt               RT + UT machine read   accepted by J. Okafor
distortion        2.1 mm out-of-plane    in tolerance
Integration

The two weeks that decide the pilot

Integration is not a formality. It is where a pilot is won or quietly lost, and it takes about two weeks when the preparation has been done.

Week one is physical and network: appliance placement, controller and power-source access, sensor mounting and calibration, and a read-only connection to the MES. Nothing is written to any machine during week one.

Week two is baseline and envelope: importing the qualified procedures, agreeing the confidence and stop policy, mapping roles to real people, and beginning the measured baseline period against which the scorecard will be judged.

Envelopes

Turning a WPS into an enforced boundary

The single most important configuration in the platform, and the one your welding engineer owns outright.

Import
Qualified procedures imported from your weld-data system or entered and reviewed in the platform.
Ranges
Current, voltage, travel speed, wire feed, heat input, interpass temperature and position limits.
Ownership
Only the welding-engineer role may change an envelope; every change is versioned and attributed.
Enforcement
Clamping happens in the controller adapter, below the agents — an agent cannot route around it.
Deviation
Any requested value outside the range is clamped, logged and surfaced in the shift review.
Qualification currency
Envelopes tied to expiring PQRs or welder qualifications raise alerts before they lapse.
Inspection

The acceptance workflow, in full

Machine calls never close themselves. This is the exact path from indication to disposition.

Call
The defect agent produces an indication with type, size, location, modality and confidence.
Route
The call enters your inspector queue with the source imagery and the weld's full context attached.
Adjudicate
Your qualified inspector accepts, rejects or requests re-inspection. Their identity is recorded.
Disposition
Accepted rejects raise an NCR linked to the weld record and its upstream causes.
Feedback
Adjudications become labelled data for your models, on your site, under your data policy.
Audit
The complete chain — call, imagery, adjudicator, disposition — exports as one record.
Schema

The weld genealogy record

The canonical object in the platform. Everything else is derived from it.

Weld genealogy record with WPS, consumable, fit-up, heat input, passes and NDT
One record per weld, assembled continuously rather than compiled afterwards. Weldeon studio diagram.
Runbook

A shift, operationally

What the operations team actually does with Weldeon running.

  1. 01

    Shift start

    Check appliance and cell status, review overnight twin plans, confirm consumable lots against the plan.

  2. 02

    First-off

    Run the first assembly with heightened review; confirm fit-up measurements and pass parameters against expectation.

  3. 03

    Steady state

    Monitor exceptions only. The platform surfaces deviations, low-confidence stops and indications; everything else is silent.

  4. 04

    Escalation

    Advisory drops and stops route to the named engineer with the record attached. There is no anonymous alert queue.

  5. 05

    Shift close

    Review deviations, indications and takt against plan. The report is generated from the genealogy, not typed.

Support

How to get help

Four channels, with the response you should expect from each.

Shop-floor escalation

For anything that has stopped a cell. Named contact on Factory and Enterprise; business hours on Cell.

Engineering support

Integration and API questions, handled by the engineers who wrote the adapters.

Quality liaison

For code, envelope and audit questions — staffed by welding and quality engineers, not a helpdesk.

Release notes

Every runtime and model release documented with behavioural changes called out explicitly.

Documentation

What is available today

9

documentation books covering deployment through audit

2 wks

typical integration duration for a single-cell pilot

1

canonical object — the weld genealogy record

100%

of parameter deviations recorded before the next pass

Questions

Documentation questions

Begin

Bring autonomy to thearc, the fit-up andthe inspection bay.

Book a pilot on one cell or line. We agree the scorecard before we start — first-pass yield, rework hours, defect escapes, takt — and we report against it in the open.