Input data checked
It can organize scantling, material and loading condition tables in the format each tool accepts, checking units, empty fields and unmatched items before running.
Deliverable: input spreadsheet + list of open issuesOcto for hull structure and classification
Each classification society distributes its own software to check hull structure against its rules and the Common Structural Rules (CSR) of IACS, the international association of classification societies. Around these tools, Octo can prepare input data, run what accepts scripts, read finite element results and draft reports, all for human review. The one who signs is the engineer in charge; the one who approves is the classification society.
Six possible deliverables, drawn from the research. All of them use the tools the client already has installed and licensed; none replaces the check in the classification society's tool, and all of them go to review by the engineer in charge.
It can organize scantling, material and loading condition tables in the format each tool accepts, checking units, empty fields and unmatched items before running.
Deliverable: input spreadsheet + list of open issuesIt can launch the checks that the tool allows by script: Sesam Core, Sestra and Wasim through the Python package dnv-sesam-commands; GeniE through JavaScript; Femap through its API. Each run is logged.
It can read Nastran files (.bdf and .op2) with the open-source pyNastran and list the maximum stress by property or region, against a limit the engineer provides from the rule.
It can compare two runs (thickness, material, result) and show what changed, for whoever will answer the classification society's comments.
Deliverable: differences reportProposes the draft of the calculation report or of the reply to comments, with every number linked to its source file, for the engineer to review and sign.
Deliverable: traceable draftIt can cross the measurement company's spreadsheet with the design thickness and the allowable wastage provided by the engineer, separating what is within limits, in attention or beyond, for the surveyor and the shipowner to decide.
Deliverable: status point by pointThe same Octo cycle, applied to structure and classification. Each arm has a narrow role; the one who signs is the engineer in charge and the one who approves is the classification society.
Which classification society, which software and version, which rule edition applies to the ship. The tool version has to match the contracted edition.
Model units, names of properties, materials and load cases. Without this agreement, two runs cannot be compared.
Client designs are confidential; a naval vessel may involve controlled data. Nothing leaves the client's machine without approval from the responsible team.
Python in Sesam, JavaScript in GeniE, the Femap API, pyNastran to read results, PyMAPDL for studies. The rule check always stays in the classification society's tool.
Prepares the batch or reading script with the limit and the rule provided by the engineer, never taken from memory.
Compares the script output with what the tool itself shows for the same element and the same load case. It checks by the number, not by the absence of errors.
Only with your OK, it runs on the machine where the tool is licensed and leaves the spreadsheet or the draft right there for review.
Tool, version, rule edition and what was checked. The script for one ship is not taken as ready for another.
Octo does not approve designs or assign class. Approval, class and certificates belong to the classification society and the maritime authority; the design has a qualified engineer in charge. Sending controlled data (ITAR/EAR, U.S. export control regulations) to any external service, including AI, must first be assessed by the client's compliance team.
The criteria Octo uses to choose. The rule check stays in the classification society's tool.
| Task | Path | Notes |
|---|---|---|
| Run Sesam checks in batch | dnv-sesam-commands (SesamCoreCommand, execute_command) | Sesam installed and licensed |
| Repetitive geometry or loads in GeniE | GeniE JavaScript script | Commands in the GeniE documentation, behind a login |
| Read stresses from a Nastran model (VeriSTAR Hull, Femap) | pyNastran (read_bdf, read_op2) | CSV for the engineer to check |
| Parametric study of a detail | PyMAPDL (Mechanical APDL) | A study, not a rule check |
| Take the model from CAD to the classification society's tool | NAPA Steel ↔ ABS UDM Utility; NAPA Designer → PrimeShip-HULL; NAPA and Tribon → RulesCalc | Each path comes from the tool vendor |
| Check thickness measurement | Measurement spreadsheet + comparison script | Allowable wastage provided by the engineer |
Three steps. Each one only makes sense after the previous one has shown results on your project and passed review by the engineer in charge.
A proposal, not a promise
On the machine where the tool is licensed, you ask in engineering language and Octo proposes the script and the spreadsheet.
Batch runs and the comparison between revisions can start running with each new model version, in the client's environment.
The calculation report can come out as a traceable draft, and each new rule edition can become an impact list for the engineer to assess.
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.
dnv-sesam-commands package (5.23.1.0, MIT license) runs Sesam Core, Wasim and Sestra commands as from the command line, with SesamCoreCommand and execute_command.Source: package page on PyPI, May 2, 2025Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and produces the documents: spreadsheets, reports, lists and drafts.
Deliverable: material ready to checkThe 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 signsOcto 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 societyDocumentation and pages from the classification societies themselves, IACS and the vendors, used in the research.
The assessment starts with the tools you already have and the rule contracted for the ship, without changing anything. You get a proposal of what can be prepared, run and checked around them, and you decide with that in hand.