Hull inventory on Linux
It can read a Rhino model (.3dm) with the open-source rhino3dm library, without Rhino, and list the layer, type and bounding box of each object. Hydrostatics and mass stay with Orca3D or another naval architecture tool.
Octo for ship design
Shipyards and design offices draw the ship in suites such as AVEVA, NAPA, CADMATIC, ShipConstructor, 3DEXPERIENCE and NX, and the hull form in Rhino with Orca3D or in Maxsurf. With a copy of the model or a read-only account, Octo can inventory layers and plates, check the OCX file (open format for exchanging the 3D model with the classification society) and propose scripts, all for human review. The ones who approve the design are the engineer in charge, the classification society and the maritime authority.
Six possible deliverables, drawn from the research. All of them start from a copy of the model or a read-only account, on a machine authorized by the client; none changes the design model, and all of them go to review by a person.
It can read a Rhino model (.3dm) with the open-source rhino3dm library, without Rhino, and list the layer, type and bounding box of each object. Hydrostatics and mass stay with Orca3D or another naval architecture tool.
It can read an OCX file exported from NAPA, CADMATIC Hull or another tool and list panels and plates with their thickness. A plate without a thickness becomes an open issue for the designer, not a conclusion.
Deliverable: chapas.csv + count of open issuesIt can validate the OCX file against the published XSD schema, with xmllint, before sending it to the classification society. It validates the shape of the file, not the ship's structure.
It can compare two extractions of the same model (inventory or plate list) and point out what was added, removed or changed thickness between one revision and the next.
Deliverable: line-by-line differences reportWith a license for the CADMATIC eShare Public REST API and a read-only account, it can list projects and documents; with the CADMATIC Web API, it can read catalog, objects and changes into a spreadsheet.
Deliverable: script + spreadsheet of projects and documentsIt can record existing AVEVA PML macros, NAPA scripts, NX journals and Grasshopper definitions, and propose new drafts for the designer to review and test on the installed version.
Deliverable: inventory of automations + draftsThe same Octo cycle, applied to ship design. Each arm has a narrow role; the ones who approve the design and grant access are people in your company.
Which suite, which version, which modules are licensed, which formats come out of it (OCX, DWG, .3dm) and which automation already exists in the team.
How the shipyard names panels, plates and layers, which unit the model is in and which OCX schema version the export uses.
A copy of the model or a read-only account, on a machine the client authorized. In a defense project, nothing leaves before approval from the compliance team.
rhino3dm for .3dm on Linux; XML reading for OCX; REST for CADMATIC eShare and Web API; PML, the .NET API, NX Open or COM when the work has to happen inside the tool, on Windows.
Prepares Python scripts that read the model and write CSV, without changing the source file, with the criterion of each extraction noted.
Compares the extraction with what the tool shows for the same panel or block: number of plates, thicknesses, layers. It checks by content, not by the success message.
Only with your OK, it runs on the cleared machine and leaves the spreadsheet or the report right there for the designer's review.
Versions, formats, naming conventions and what was confirmed on your installation. The script for one shipyard is not taken as ready for another.
Octo does not approve designs, scantlings or stability: that belongs to the engineer in charge, the classification society and the maritime authority. Sending controlled data (ITAR/EAR, U.S. export control rules) to any external service, including AI, must first be assessed by the client's compliance team.
The criteria Octo uses to choose. Reading comes first; work inside the tool comes later, with the designer.
| Task | Path | Notes |
|---|---|---|
| Inventory a Rhino hull | rhino3dm 8.35.0 on Linux | No mass calculation; hydrostatics stays with Orca3D or similar |
| Summarize plates and thicknesses | OCX file exported from NAPA, CADMATIC Hull or another tool | The schema may change between versions |
| Validate an OCX before sending it to class | xmllint against the published XSD | It validates the shape of the file, not the ship's structure |
| List digital twin projects and documents | CADMATIC eShare Public REST API | Separate license; routes in the server's Swagger |
| Connect the design to the ERP or the PLM | CADMATIC Web API; AVEVA .NET API (marAPI.dll); NX Open | Read-only at first |
| Run hull form calculation series | Maxsurf COM automation; Grasshopper with Orca3D | Windows; the result goes to the naval architect to decide |
Three steps. Each one only makes sense after the previous one has shown results at your shipyard.
A proposal, not a promise
With a copy of the model and an authorized machine, you ask in business language and Octo proposes the script and the spreadsheet.
OCX validation and the comparison between revisions can start running at each export, in the client's environment.
The macros and scripts the team already uses can become documentation, and new ones can be proposed as drafts for the designer to test.
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.
Panel, Plate and Stiffener; 3.0 is in pre-release.Source: OCX Consortium site; OCX_Schema repository/swagger; AVEVA's marine .NET API is in marAPI.dll; the rhino3dm 8.35.0 library has Linux packages on PyPI.Source: CADMATIC and AVEVA documentation; PyPI (Sep 15, 2026)Octo 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 announcements from the vendors themselves and from the standard's body, used in the research.
The assessment starts with a copy of the model or a read-only account, without changing anything. You get a proposal of what can be extracted and checked in your design, and you decide with that in hand.