Skip to content
Octo × Fabrication PT Request an assessment

Octo for shipbuilding fabrication

From hull to cut plate, every file checked.

Between the hull design and the cutting machine, the shipyard exchanges files: parts in DXF (a 2D drawing format), cutting programs, profiles in DSTV, reports of parts nested on the plate (nesting) and measured block points. Octo can read these files, cross them with the parts list and point out what diverges, all prepared for human review. The ones who release cutting, welding and the block are the shipyard's qualified people, with the classification society.

Steel plate in perspective with nested parts and the torch path; from the center, Octo sends flows that become a parts list check, plate utilization and block measurement deviations DSTV DXF READ-ONLY PARTS REMNANT Parts list Utilization BLOCK DEVIATIONS python3 01_conferir_dxf_pecas.py bloco.dxf lista.csv OCTO × FABRICATION READ ONLY N-06
Exchange formatsDXF · ESSI · DSTVplus XML, CSV and reports
CADMATIC Hull2025H2released on Dec 2, 2025
NAPA2026.1handover to production at actual thickness (Jun 26, 2026)
Sources16listed at the end of the page
01

What Octo does in fabrication.

Six possible deliverables, drawn from the research. All of them start from files the shipyard already exports; none touches the cutting machine or the robot, and all of them go to review by a person.

DXF parts against the block list

It can cross the coded parts that come out of AVEVA, CADMATIC Hull, ShipConstructor or NAPA with the block's parts list and point out missing parts, extra parts and diverging areas.

Deliverable: list of discrepancies per block

Plate utilization

It can read nesting reports in batch and summarize utilization per plate and per block, list remnants and point out nestings that mix parts from different blocks, for planning to decide.

Deliverable: summary per plate and per block

Profile files in DSTV

It can open the profile files, count contour and hole blocks and point out files with no start, no end or no outer contour before they go to the profile line.

Deliverable: check table per file

Block measurement deviations

It can compare the points measured by total station or laser tracker with the design nominal and set apart those above the tolerance defined by quality. The one who releases the block is a qualified person.

Deliverable: deviation report per point

Material traceability

It can link the steel heat number, plate, nesting and block from the exports of the design system, the cutting CAM and the management system (ERP), and point out gaps in the record.

Deliverable: traceability table with gaps flagged

Documented data flow

Proposes a diagram of the data path between design, nesting, cutting, welding and measurement, with the formats of each handoff and the procedure for using the scripts.

Deliverable: draft of the flow and the instructions
02

Eight arms, one plate at a time.

The same Octo cycle, applied to shipbuilding fabrication. Each arm has a narrow role; the ones who approve and release are shipyard people.

  1. Discovery

    Maps the path of the parts

    Which design system, which cutting CAM, which machines and which formats: coded DXF, ESSI or G-code, DSTV, nesting return XML.

  2. Data

    Pins down the coding standard

    How the shipyard names part, block, thickness and material in each file. Without this explicit standard, one list cannot be compared with another.

  3. Security

    Defines what can be read

    Read-only access to the exported folders. In naval defense work, nothing leaves before approval from the client's compliance team.

  4. Architecture

    Chooses the reading point

    The file that already comes out of the system (DXF, report, XML, CSV) instead of touching the CAD database or the machine control.

  5. Development

    Writes the check script

    Prepares Python scripts that only read and report: DXF through the open-source ezdxf library, the rest through the standard library.

  6. Review

    Checks against a known block

    Runs the script on a block already cut and checked and compares it with what planning and quality know about it. It checks by content, not by "it ran without errors".

  7. Release

    Runs in the authorized environment

    Only with your OK, it runs on the machine the shipyard cleared, inside its network, and leaves the report right there for review.

  8. Documentation

    Records what applies to your shipyard

    Coding standard, formats and what was checked in each version. The script for one shipyard is not taken as ready for another.

Octo does not release cutting, welding or blocks. Tolerances, welding procedures and structural approval belong to qualified people, the classification society and the maritime authority.

03

Every task, its own path.

The criteria Octo uses to choose, stage by stage. Only on the exported file, never on the machine control.

TaskPathNotes
Generate coded parts for cuttingAVEVA, CADMATIC Hull (Autopart), ShipConstructor, NAPAOutput in coded DXF; the naming standard changes by shipyard
Nest plates and profilesAVEVA Plate and Bar Nesting, CADMATIC Plate Nesting, ShipConstructor Nest, Nestix, Almacam, Lantek, SigmaNEST, ProNestBatch import documented by the CAM vendors
Return the nesting to the modelCADMATIC with AlmaCAM: CadmaticExport.exe <bloco> generates the XML that Hull importsDocumented by CADMATIC; the exporter comes from Alma
Check DXF parts against the listScript with ezdxfBlock parts list exported from CAD
Check profile filesScript over the DSTV blocks (ST, AK, IK, BO, EN)DSTV file that goes to the profile machine
Summarize utilizationScript over the nesting report exported as CSVThe CSV columns change by software
Program a welding robotRinasWeld (reads .STEP, .IGES, .IFC, .ATX), Almacam Weld; Inrotech needs no CADOcto reads what comes out; it does not program the robot
Compare block measurement with the nominalScript over points exported as CSVAlignment done in the measurement software
04

From checking to monitoring.

Three steps. Each one only makes sense after the previous one has shown results in your operation.

A proposal, not a promise

1 Today

On-demand checks

With read access to the exported folders, you ask in business language and Octo proposes the script and the report.

  • “Check the parts of block 312 against the list” becomes a script + report
  • Test first on a block already checked
  • Coding standard noted in each report
Gain: discrepancies show up before cutting
2 Next

Routine reports

The parts check and the nesting summary can start running at each block release, in the shipyard's environment.

  • Utilization per block at each nesting batch
  • Steel heat traceability with gaps flagged
  • Dimensional control deviations per block
Gain: the team just reads the report and decides
3 Later

Documented flow

The data path from design to measurement can become a document, and a change of cutting CAM can count on a check prepared for review.

  • Map of formats between design, cutting, welding and measurement
  • Comparison of outputs from the old and the new system
  • Work instructions revised from the files
Gain: the data handoff gets documentation
05

Confirmed by a source.

Every point below has a source published by the vendor, by the project or by the responsible agency. The sources are in the next section.

4

points with a published source, each with its reference shown alongside.

ConfirmedNesting returns to the model through XML
In the CADMATIC documentation, Hull cutting data goes to a nesting system such as Nestix or AlmaCAM; with AlmaCAM, CadmaticExport.exe runs with the block name and generates the XML that Hull imports.Source: CADMATIC Hull 2025H2 documentation
ConfirmedNC returns cutting time to the model
According to SSI, NC-Pyros generates the program for oxy-fuel, plasma, laser, waterjet and milling, and returns cutting time, date and operator to the model; NC-Pyros-Bevel does variable-angle beveling.Source: ShipConstructor page (SSI)
ConfirmedWho uses it, with a source
According to an Alma case study (undated), Volkswerft Stralsund had worked with act/cut since 1993 and read plates directly from the design system. According to a NAPA release (Jun 26, 2026), Chantiers de l'Atlantique is piloting the handover of the model to production at actual thickness. An announcement says what was done on that date, not what is in production today.Source: Alma, case study; NAPA, Release 2026.1
ConfirmedWelding robot from the 3D model
Kranendonk's RinasWeld reads .STEP, .IGES, .IFC and .ATX, picks parameters from a WPS (welding procedure specification) library and generates the robot program; Inrotech (acquired by Lincoln Electric on Jun 3, 2024, according to a Lincoln Electric press release) finds joints by vision, without CAD.Source: RinasWeld page; Lincoln Electric press release (Jun 3, 2024)
06

What Octo does, and what stays with you.

Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.

Octo prepares

Surveys, calculates, organizes and produces the documents: spreadsheets, reports, lists and drafts.

Deliverable: material ready to check

Your team checks

The licensed professional checks what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.

Step: checked by the person who signs

Who signs

Octo does not sign. Designs, technical reports, ART/RRT, statements of account and any official document are still signed by the licensed professional at the company or agency: here, the naval engineer in charge and the classification society.

Signature: naval engineer and classification society
07

Sources.

Documentation and announcements from the vendors themselves, used in the research.

Your cutting files, read-only.

The assessment starts with one exported folder and a block already checked, without changing anything. You get a proposal of what can be checked in your fabrication, and you decide with that in hand.