Robots, power sources, cutting machines
Equipment shipped Hullira-ready, with the controller tags, limits and WPS envelope declared at the factory. The agent runs on the OEM machine; the OEM keeps the machine relationship.
Hullira's distribution plan runs through the companies already on the yard floor: welding-robot and cutting OEMs, CAD/CAM vendors, laser-scan, NDT and coating-equipment vendors, classification societies, yard-software providers and the integrators who connect them. The programme opens with the design-partner cohort; nothing here is a signed partnership.
Illustrative scenario: Block B-214 · double-bottom block · panel line PL-2 · dock D1, one block, one approval gate
How each kind of partner fits the plan.
Equipment shipped Hullira-ready, with the controller tags, limits and WPS envelope declared at the factory. The agent runs on the OEM machine; the OEM keeps the machine relationship.
Nests and drawings in, genealogy and the optimised plan written back into the system of record. Evidence packets for class and naval review.
Station data fused into Quality-and-Anomaly. The vendor keeps the measurement; Hullira adds the prediction, the root cause and the cited disposition.
Assurance readiness for the audit trail, the cited disposition and the as-built evidence the surveyor reviews. A readiness conversation, not an approval claim.
Connection, tag inventory, robot cells and the shadow-mode phase of a pilot, delivered by people the yard already trusts.
The first two to four yards shape the roadmap and get written access terms. See the customers page.
The outline of the programme as planned.
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.
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 weld-parameter controllers (Pemamek, Kranendonk, IMG, Fronius, Lincoln Electric, Panasonic class systems)
Parameter and sequence reads; writes inside the WPS envelope
Dimensional and accuracy-control systems (Hexagon, FARO, BuildIT class tools)
Point clouds per block and stage; as-built registration
X-ray and UT stations and service houses (Waygate, Evident class systems)
Scans and indications per joint; routing and holds
Environmental sensors, dry-film gauges, robotic blast and spray systems
Humidity, dew point, steel temperature, thickness; cell pause and resume
Crane telemetry, dock and berth plans, block transporters
Capacity and position reads; plans under planner approval
Yard MES, scheduling and twin systems (Siemens, Dassault, AVEVA, iBASEt, Aras, in-house systems)
Work packages, block genealogy, disposition write-back
WPS and PQR, ABS, DNV, LR and ClassNK rules, IMO PSPC, naval quality specs
Tenant-isolated retrieval with citations
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
A weld pool is decided in milliseconds and a dock waits by the hour. Perception has to be local, deterministic and fast, so Hullira runs GPU inference at the yard edge and keeps training, simulation and optimisation in the cloud or on-prem.
6 to 24 cameras per process area plus UT, X-ray, thermal, laser-scan, photogrammetry, robot and coating-instrument streams fused at the yard edge. Sub-50 ms weld alerts and sub-150 ms coating or scan prompts are the design targets. Jetson Thor is planned for higher camera density.
Weld-defect, distortion-risk, coating-risk, point-cloud and schedule-risk models behind one orchestrator at the yard edge, versioned with rollback, routed by latency, tenant, sensitivity and cost.
Weld-defect vision, UT and X-ray classification, NeMo class-rule reasoning and weld-thermal FEA surrogates fine-tuned per tenant: 100 to 500 GPU-hours per yard during onboarding, then monthly retraining from engineer corrections and class outcomes. Dedicated training capacity is planned.
Block erection, weld sequence, robot reach, crane paths and yard layout simulated before the shift, as-built against as-designed. GPU weld-thermal and structural FEA is the workload; physics-informed surrogates rank plans at shift cadence.
Rare weld defects, coating failures, distortion modes, occluded seams and erection misalignment cases generated and validated against real NDT and scan distributions before promotion. 50k to 250k variants per vessel class is the target. Planned.
Dock, crane and berth schedules, work-package sequencing, yard logistics and erection order, re-solved as progress changes.
Robotic weld, blast, coat and inspection cells and crawler or drone hull inspection, with paths validated in simulation before they run next to a hull.
Telemetry ETL across weld parameters, scans, NDT results, coating readings, non-conformance and schedule history, for retraining, drift detection and rework, dock-time and schedule benchmarks.
WPS and PQR, class-rule, PSPC, cyber and human-approval policies enforced before any action writes back to robots, MES, QA or work packages; retrieval with citations and tenant isolation.
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.
Control returns to the robot controller, PLC or planner's last known-good state. Hullira is a supervisory layer on top of the controllers and interlocks you already run, never a replacement for them, so an outage degrades the process to its current way of running, not to a stop.
Advisory recommendations start from the physics-based twin, the WPS and the block drawings in the first weeks. Defect, distortion and coating prediction improve as block history and labelled NDT and surveyor outcomes accumulate. Onboarding is sized at 100 to 500 GPU-hours per yard and 50,000 to 250,000 synthetic variants per vessel class, both design targets.
Only if you choose cloud training. Drawings, WPS and PQR, naval data, process models and quality records are isolated per tenant and never used to train another customer's models. Security is defense and ITAR-aware, a fully on-prem deployment at the yard edge is available for naval and regulated yards, and federated learning across yards is planned and waits on data-rights agreements.
You are, the same as with any procedure change, which is why every write is policy-checked, bounded, logged and reversible, and why anything above your risk threshold waits for a named approver. The audit log records the request, the evidence, the WPS or class citation applied and the human decision.
A paid pilot on one process, scoped to a single wedge with a success metric written into the order form: weld rework, fairing hours, coating non-conformance, dock days or class-approval cycle time. Shadow mode comes first and the baseline is measured from your own records. We do not publish a pilot length because we have not run one.
Tell us what you ship or support and which yards run it.
↑↓ navigate↵ openesc close