Enterprise

One policy. Every process. Every yard.

Multi-yard groups and naval programs standardise on Hullira for the governance as much as the control: one autonomy policy with per-yard override, one audit trail, fleet-managed yard-edge nodes, and weld, distortion and schedule models that stay private to each yard and each program.

Land $700k to $10M ACVFleet-managed yard edgePer-yard private models

run_4b7e19 · agent graph · block B-214 · scenario 10 nodes · 1 approval gate
01 · orchestrator ingest.package ✓ SUCCEEDED 02 · aligna twin.simulate ✓ SUCCEEDED 03 · cut_profile cut.nest ✓ SUCCEEDED 04 · panel_weld weld.sequence ✓ SUCCEEDED 05 · orchestrator approve.human ◆ APPROVAL 06 · quality_anomaly inspect.fuse ✓ SUCCEEDED 07 · fair_form fair.lineheat ✓ SUCCEEDED 08 · blast_coat coat.window ✓ SUCCEEDED 09 · schedule_yard dock.reoptimise ✓ SUCCEEDED 10 · erect_align erect.align ✓ SUCCEEDED

Illustrative scenario: Block B-214 · double-bottom block · panel line PL-2 · dock D1, one block, one approval gate

Enterprise features

What the Enterprise tier adds

Items marked planned follow the 6 to 12 month roadmap.

Governance

Group autonomy policy

One policy model for the group with per-yard override and approval chains. Tag allow-lists, WPS and coating envelopes and limits reviewed and versioned like code.

Identity

SSO, SCIM and tag-level RBAC

Named approvers, role-based access down to the tag, program-office and cyber approvers for naval work. Planned for the 6 to 12 month release.

Fleet

Yard-edge fleet management

Model versions promoted by process area with canary rollout and automatic fallback across every yard. On-prem options for naval and regulated yards.

Models

Custom weld, distortion and schedule models

Per-yard process models built on the yard's own vessel classes, block geometries and procedures and kept private to that tenant.

Benchmarking

Cross-yard benchmarks

Rework, fairing hours, coating non-conformance, dock days and schedule slips compared across yards without moving drawings or naval data across tenant boundaries. Data-network tiers are planned.

Support

Dedicated engineer, SLAs

A dedicated deployment engineer, quarterly model review per yard and SLA terms set per agreement.

Deployment

Where it runs

The yard edge is always local. The control plane can be cloud, on-prem or absent.

Deployment options
OptionYard edgeControl planeFor
Cloud control planeJetson nodes at the process areaHullira cloud, per-tenant isolationMost commercial yards; cloud training optional
On-prem control planeJetson nodes at the process areaIn the yard's data centre, defense and ITAR-awareNaval programs and IP-sensitive yards
Yard-edge onlyJetson nodes at the process areaNone; models and policy updated by controlled releaseRegulated yards that allow no external link
Edge-only degradationReturns to controller last known-goodUnreachableWhat happens on any control-plane loss
Enterprise

Standardise autonomy across the group

One policy model, one audit trail, one benchmark across every process in every yard, with the weld, distortion and schedule models kept private to each site and each naval program.

Talk to us Enterprise details

  • SSO and role-based access down to the tag level, planned for the 6 to 12 month release
  • Group-wide autonomy policy with per-yard override and approval chains
  • Cross-yard benchmarking on rework, fairing hours, coating non-conformance, dock days and schedule slips
  • On-prem and yard-edge deployment, defense and ITAR-aware, for naval and regulated yards
  • Edge autonomy that survives control-plane loss by returning to the controller's last known-good state
  • Dedicated deployment engineer and quarterly model review per yard
Run timeline · scenario

One scenario run, step by step

Every Hullira run is an ordered, inspectable sequence. This is run_4b7e19 on Block B-214 · double-bottom block · panel line PL-2 · dock D1. Scenario completes in 10 steps with one approval gate. Predicted distortion at the erection joint fell from 4.2 mm to 1.8 mm after a back-step sequence, one porosity precursor on seam S-31 was cleared inside the WPS envelope, the ballast-tank coat ran inside a 3.4 °C dew-point margin, and the block landed at 1.6 mm with its conformance record written.

run_4b7e19 Block B-214 · double-bottom block · panel line PL-2 · dock D1 illustrative scenario SUCCEEDED
  1. 01 ingest.package SUCCEEDED 0.8 s

    Yard Orchestrator · Pulled the work package for B-214 from the yard MES: 46 plates, 212 seams under WPS-117, erection tolerance 2 mm at the D1 joint, PSPC-grade ballast-tank coating, erection slot on D1 in the dock plan. Locked the qualified WPS envelope and the class scope.

  2. 02 twin.simulate SUCCEEDED 1 m 12 s

    Ship Twin · Simulated 18 candidate weld sequences on the as-built twin with the weld-thermal surrogate, ranked on predicted distortion at the erection joint, crane reach on D1 and shift takt. Standing sequence predicts 4.2 mm; candidate #6 predicts 1.8 mm.

  3. 03 cut.nest SUCCEEDED 3 m 40 s

    Cut-and-Profile · Released the nest for 46 plates on CL-1 with the fit-up gaps candidate #6 assumes. As-cut geometry logged per plate and handed to the panel line; material yield 91.4% against the nest plan.

  4. 04 weld.sequence SUCCEEDED 2 m 05 s

    Panel-and-Weld · Loaded the back-step sequence for the non-critical seams on PL-2 and set heat input and travel speed inside WPS-117. Weld-pool and seam cameras streaming on 12 channels.

  5. 05 approve.human APPROVAL 58 s

    Yard Orchestrator · Candidate #6 also re-orders two class-critical butt seams, S-31 and S-32. Sequence changes on class-critical seams stay with a human, so the step was held for the shift welding engineer and approved at 06:12:44.

  6. 06 inspect.fuse SUCCEEDED continuous

    Quality-and-Anomaly · Twelve weld cameras and the UT station fused at the yard edge. One porosity precursor on S-31 at 06:41 flagged and cleared by a 4% wire-feed trim inside the WPS-117 envelope; the joint was routed to UT and passed.

  7. 07 fair.lineheat SUCCEEDED 4 m 30 s

    Fair-and-Form · Post-weld scan registered against the twin: 2.1 mm at the erection joint. Two line-heating passes planned on the inner bottom and executed by the fairing crew; re-scan read 1.8 mm, inside the 2 mm tolerance.

  8. 08 coat.window SUCCEEDED continuous

    Blast-and-Coat · Ballast-tank blast and first coat scheduled to a window with steel temperature 3.4 °C above dew point. Dry-film thickness read 312 µm against a 280 µm minimum on the stripe coats; PSPC evidence assembled per area.

  9. 09 dock.reoptimise SUCCEEDED 41 s

    Schedule-and-Yard · Re-solved the D1 dock and crane plan with B-214 ready 6 hours early and a neighbouring block late: erection slot pulled forward one shift, crane G2 reassigned, no berth conflict. Planner approved the revised plan.

  10. 10 erect.align SUCCEEDED 1 h 48 m

    Erect-and-Align · Both blocks scanned on D1 and registered against the twin; fit predicted at 1.6 mm. Shimming guidance issued to the erection crew, block landed and welded out, final scan 1.6 mm. Conformance record written: welds, scans, coating readings, approvals and class evidence for B-214.

Guardrails

An agent that can move a weld parameter needs a leash

Hullira writes to production equipment. Every capability is scoped, every write is policy-checked against the qualified WPS, class and PSPC constraints, and every action is written to an append-only audit log the yard owns.

  • Bounded action space. Each agent writes only to an explicit tag allow-list, inside per-tag rate and magnitude limits and the qualified WPS, coating, dimensional and schedule constraints for the block.
  • Policy engine before every write. WPS and PQR, class rules, PSPC, safety limits, role permissions, autonomy level and human-approval requirements are evaluated before a parameter moves. NeMo Guardrails is the design for this layer.
  • Human-in-the-loop gates. Class-critical seam changes, lift plans, block release and class evidence wait for a named approver. Robots adapt only inside pre-approved WPS envelopes until class, yard and insurer acceptance supports more.
  • Immutable audit log. Append-only, assurance-grade and exportable. Every action records source evidence, the WPS, class or PSPC citation applied, confidence, estimated rework, dock-time and schedule impact, rollback path, approver and block scope.
  • Hard fallback. Loss of the edge node, the network or a model returns control to the robot controller, PLC or planner's last known-good state. Interlocks are never in Hullira's path.
  • Tenant and defense-aware isolation. Drawings, WPS, naval data, models and memory never cross a customer boundary. Security is defense and ITAR-aware, and on-prem or yard-edge deployment is available for naval and regulated yards.

Compliance posture

Compliance and certification status
ItemScopeStatus
SOC 2 Type ICloud control plane QUEUED Planned, first 6 months, with a defense and ITAR-aware review
SOC 2 Type IICloud control plane QUEUED Planned, 6 to 12 months
SSO and RBACConsole and approvals QUEUED Planned, 6 to 12 months
Class-society and defense assurance packagesDisposition and genealogy evidence QUEUED Planned, 6 to 12 months; not a class approval or certification claim
Cited reasoningWPS and PQR, ABS, DNV, LR, ClassNK, IMO PSPC, naval specs RUNNING In the design, every answer cites its source
Per-tenant and IP isolationDrawings, WPS, naval data, models, memory RUNNING In the design from day one
On-prem and yard-edge deploymentNaval and regulated yards RUNNING Design option

Read the security overview

Autonomy

Four levels, set per agent and per tag

A yard does not go from paper travelers to unattended welding in one step. Hullira makes the level explicit, auditable and reversible at any time. The first release runs shadow mode, then assist mode, then supervised control on low-risk actions. Class-critical seam changes, lift plans and block release stay with named people.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · ShadowReads weld, scan, NDT, coating, robot, crane and MES signals; predicts and recommends; writes nothingRuns the process as today; compares predictions to NDT and surveyor outcomesShadow mode; the baseline is measured from the yard's own records
L2 · AssistProposes weld, fairing, coating, routing and schedule moves with evidence, confidence, envelope and rollback pathApproves each action in the review consoleAssist mode, the remainder of the pilot
L3 · Supervised controlExecutes pre-approved low-risk actions: inspection routing, coating pauses when a window drifts, weld parameters inside the WPS envelope, robot path variants tested in simulationApproves class-critical seam changes, lift plans and block releaseGraduated autonomy, after audited accuracy and ROI
L4 · BoundedSupervised work sequencing and weld adaptation for qualified block types, across processes and yardsSets the envelope; reviews the shift record and the evaluation resultsPlanned; after class, yard and insurer acceptance is earned
Integrations

It speaks yard, not cloud

Hullira reads and writes through the systems already on the floor. No rip and replace, no parallel historian, no new HMI to learn. Vendor names are examples of systems found in yards, not certified integrations; connector availability is confirmed per site.

CAD/CAM and nesting

Shipyard CAD/CAM and production planning (Siemens NX Shipbuilding, Dassault CATIA and 3DEXPERIENCE, AVEVA Marine, SSI ShipConstructor, NAPA class systems)

Nests, drawings, as-designed geometry; guarded cut-program writes

Welding robots and power sources

Welding robots and weld-parameter controllers (Pemamek, Kranendonk, IMG, Fronius, Lincoln Electric, Panasonic class systems)

Parameter and sequence reads; writes inside the WPS envelope

Laser scan and photogrammetry

Dimensional and accuracy-control systems (Hexagon, FARO, BuildIT class tools)

Point clouds per block and stage; as-built registration

NDT

X-ray and UT stations and service houses (Waygate, Evident class systems)

Scans and indications per joint; routing and holds

Coating instruments and cells

Environmental sensors, dry-film gauges, robotic blast and spray systems

Humidity, dew point, steel temperature, thickness; cell pause and resume

Cranes, docks and transporters

Crane telemetry, dock and berth plans, block transporters

Capacity and position reads; plans under planner approval

Yard MES and scheduling

Yard MES, scheduling and twin systems (Siemens, Dassault, AVEVA, iBASEt, Aras, in-house systems)

Work packages, block genealogy, disposition write-back

Class and procedure documents

WPS and PQR, ABS, DNV, LR and ClassNK rules, IMO PSPC, naval quality specs

Tenant-isolated retrieval with citations

See all integrations

FAQ

Straight answers

The questions production directors, welding engineers and class-compliance leads ask in the first meeting.

Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, inside the qualified WPS, coating, dimensional and schedule constraints, and only at the autonomy level your yard has set. Design partners start in shadow mode, where Hullira writes nothing. Class-critical seam changes, lift plans and block release stay with named people.

Get started

Standardise the group

Start with one welding, fairing, coating or erection process and one measurable baseline. A paid pilot on weld inspection, distortion control or coating assurance shows the number before you commit further.