Octo for shipyard PLM and planning
At the shipyard, the product lifecycle management (PLM) system holds the ship as designed, the enterprise resource planning (ERP) system holds what is purchased, and the schedule holds when each block goes up. With a read-only account, Octo can map the data model, compare the bill of materials (BOM) between sister hulls, cross PLM and ERP and propose block erection sequences, all prepared for human review. The one who approves is the engineer in charge; the ones who certify are the classification society and the maritime authority.
Six possible deliverables, drawn from the research. All of them start from a read-only account and a machine that can reach the servers; none changes released data, and all of them go to review by a person.
It can read the PLM item types, attributes and relationships (in Aras Innovator, the base of ShipbuildingPLM, through OData) and propose the shipyard's integration guide: how block, hull and work package are modeled.
Deliverable: table of types and fields + draft guideIt can compare the BOM of two hulls of the same class and point out what was added, removed or changed in quantity or revision, with the effectivity criterion noted in each extraction.
Deliverable: differences report per blockIt can cross a block's BOM with purchase requisitions and orders and list what is still to be ordered, what is in excess and what changed revision after the order. The ones who decide are the buyer and the planner.
Deliverable: list of discrepancies for decisionIt can extract activities from Primavera P6 through Oracle's REST API (/activity with Fields and Filter) and propose a delay dashboard per block and per workshop.
It can build a sequencing model with the precedences and crane capacity the planner provides (OR-Tools, an open-source library) and return alternatives for the planner to assess. It does not replace the shipyard's schedule.
Deliverable: alternative sequences for assessmentProposes the extraction from the old system, the attribute mapping and the load through the new system's API, with a reconciliation trial of the counts between the two.
Deliverable: scripts + count reconciliationThe same Octo cycle, applied to shipyard PLM and planning. Each arm has a narrow role; the ones who approve and grant access are people in your company.
Which PLM, which ERP, which scheduling tool, which versions, own server or cloud. Each shipyard models block, hull and work package in its own way.
Which hull, which effectivity, which revision and which date apply. Without an explicit criterion, two BOMs cannot be compared and PLM and ERP cannot be cross-checked.
A read-only account, with the PLM's permissions by role and by project. In a defense program, nothing is read before approval from the client's compliance team.
OData in Aras Innovator; Teamcenter and 3DEXPERIENCE services; SAP OData APIs; the Primavera P6 REST API. Where there is no API, a file export.
Prepares Python scripts with each system's authentication, CSV output and, for block sequencing, an OR-Tools model with the data the planner provides.
Compares the extraction with what the PLM and ERP screens show for the same block and the same criterion: row count, quantities, revisions. It checks by content, not by the HTTP response.
Only with your OK, it runs on the machine the client cleared, inside its network, and leaves the spreadsheet or the report right there for review.
Item types, attributes, API routes and what was confirmed on your version. The next report starts from this record, and the script for one shipyard is not taken as ready for another.
Octo does not approve class drawings or design changes. 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, system by system. Read-only, with the criterion of each extraction made explicit.
| Task | Path | Notes |
|---|---|---|
| Compare the BOM between sister hulls | Two CSV extractions, one per hull, and a line-by-line comparison | Effectivity noted in each file |
| Read the block schedule | Primavera P6 REST: /activity with Fields and Filter | Read-only account |
| Test an erection sequence | OR-Tools CP-SAT with precedence and crane capacity | A proposal for the planner |
Three steps. Each one only makes sense after the previous one has shown results in your operation.
A proposal, not a promise
With a read-only account and an authorized machine, you ask in business language and Octo proposes the script and the spreadsheet.
The PLM × ERP cross-check and the schedule dashboard can start running on a schedule, in the client's environment.
With the data model documented, the planner can ask for alternative erection sequences and compare them with the shipyard's schedule.
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.
GET /activity with Fields, Filter (operators such as :eq: and :and:) and OrderBy, and POST /login with DatabaseName. The version 25 guides are from Dec/2025.Source: Oracle, P6 EPPM REST API; version 25 guidesOcto 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, used in the research.
The assessment starts with a read-only account in the PLM, the ERP and the schedule, without changing anything. You get a proposal of what can be extracted, cross-checked and simulated at your shipyard, and you decide with that in hand.