Enterprise

One standard weld,at every siteyou own.

In brief

For fabrication and OEM groups, the prize is not a faster cell. It is the same weld, the same record and the same evidence across every plant — and the ability to compare them honestly.

The group problem

Six plants, six definitions of first-pass yield

Ask a group quality director how their plants compare on first-pass yield and you will usually get six numbers built six different ways. One counts cosmetic repair, one does not. One measures at the cell, another at final inspection.

This is not a reporting failure. It is a measurement failure, and it makes capital allocation across a fabrication group close to guesswork.

Weldeon fixes it as a side effect of doing the real work. When the platform controls the weld and writes the genealogy, the definition of a first-pass weld is the same everywhere because the same system produced it.

Scope

What Enterprise includes beyond Factory

Everything in Factory, plus the things a group needs and a single plant does not.

Custom models
Material, joint and code (WPS) models trained on your portfolio and your NDT history.
Edge fleet management
Version pinning, staged rollout, rollback and health across every site.
Group benchmarks
One definition of FPY, rework and escapes across plants, with drill-down.
Governance
Role and authority models mapped to your organisation, with segregation of duties.
Commercial structure
Multi-year agreements with usage ramps and outcome-based components.
Support
SLA-backed response, named team, on-prem and air-gapped deployment options.
Rollout

How a group deployment actually goes

Reference site first. Playbook second. Fleet third. Anything else turns into six pilots that never end.

  1. 01

    Reference site

    One plant, one line, full loop. Integration patterns, code configuration and change management are worked out once, properly.

  2. 02

    Scorecard and playbook

    The reference scorecard is published internally, and the integration playbook is written down — controllers, sensors, MES, roles, training.

  3. 03

    Second site, no help

    The second site deploys on the playbook with Weldeon in support rather than in the lead. This is the real test of repeatability.

  4. 04

    Fleet rollout

    Remaining sites deploy on a schedule, version-pinned, with group benchmarks live from the first controlled weld.

  5. 05

    Standardisation

    Weld procedures, genealogy schema and acceptance workflow converge on one group standard — the durable prize.

Evidence

One genealogy schema, group-wide

The record that satisfies your notified body is the same record that lets your group quality director compare plants.

How data is isolated between sites

Group-standard weld genealogy record
The same fields, the same definitions, at every site. Weldeon studio diagram.
Commercials

How Enterprise deals are shaped

$700k

typical landing ACV at the low end of an enterprise agreement

$9M

typical upper bound for a multi-site group agreement

135%

target net revenue retention as scope expands

<14

month payback target on enterprise deployments

Commercial figures are Weldeon's operating targets and typical deal-shape guidance, not reported contract values.

Assurances

What an enterprise buyer needs to hear

In our experience these five questions decide the deal.

It runs air-gapped

The control loop closes at the edge. No site needs an outbound connection for the platform to work.

Your IP stays yours

Part geometry, procedures and NDT data are yours. Cross-site and fleet learning are opt-in per data class.

The envelope is enforced

No agent can write outside a qualified WPS range. The boundary lives in the controller adapter.

Rollback is one action

Model and runtime versions are pinned per cell and revert without a site visit.

Audit survives us

Genealogy exports are open, documented formats — readable if you never renew.

“The group prize is not a faster cell. It is one definition of a good weld, everywhere.”
WeldeonOn multi-site standardisation
Procurement

The paperwork, handled

What our enterprise motion expects to produce, and roughly when.

Security review
Architecture note, data-flow diagram and control questionnaire during evaluation.
Pilot agreement
Paid pilot with a pre-agreed scorecard, exit criteria and conversion terms.
Master agreement
Multi-year MSA with site schedules, usage ramps and outcome components.
Deployment plan
Site-by-site schedule with named owners, training and acceptance gates.
Support model
SLA tiers, escalation paths and a named technical account team.
Questions

Enterprise 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.