Octo for aerospace manufacturing
Octo can read the NC program (the G-code that goes to the numerically controlled machine), prepare the simulation batch in Vericut and check the coordinate measuring machine (CMM) reports, working on the files the software exports. It doesn't touch the machine or the CMM: it prepares a summary for human review, and release stays with the programmer and Quality.
vericut batchSix possible deliverables, drawn from the research. In all of them, Octo works with read access to the files and prepares the result for human review; nothing goes from it straight to the machine or the CMM.
It can read the already post-processed program and list the tools called, the M06 tool changes, the X, Y and Z travel, the maximum feed and spindle speed, compare the travel with the machine limits and flag a forgotten M00/M01 stop and a switch to incremental (G91). It's a text filter: it doesn't replace the simulator or the prove-out on the machine.
Proposes the batch that runs vericut batch on all the projects in a folder, without a window, with a log, report and comparison with the design model (auto-diff) per part, for an operator to run. Then it can sweep the logs and summarize collisions, errors and excess stock for the programmer to decide.
It can read the CSV exported from the measurement software, flag the features out of tolerance and those already using a large part of the band, and build a trend by lot. The neutral format is QIF (Quality Information Framework, an XML described by an XSD schema); reading QIF requires the schema of the version used. Part disposition (accept, rework, concession) belongs to Quality.
Deliverable: out-of-tolerance and warning list + trendFrom MES (manufacturing execution system) and PLM (product lifecycle management) exports, it can cross-reference serial number, NC program, model revision and inspection report and flag the gaps in the record. It doesn't write to the MES: it shows what's missing to whoever is responsible for the record.
Deliverable: cross-reference table + list of gapsIt can write or review the process sheet, the work instruction and the usage procedure for each script, based on what's in the files. The document is still signed by the person responsible for the process.
Deliverable: process sheet and procedure for reviewIt can write NX Open journals (NX automation scripts) that generate toolpaths and call the post (GenerateToolPath, Postprocess, run through run_journal), Vericut batches and inspection macros. All tested first on a copy and reviewed by whoever is responsible for the process.
The same Octo cycle, applied to manufacturing. Each arm has a narrow role; the decisions are made by a person at your company.
Which CAM (machining programming software) generates the programs, which controls and machines receive them, which Vericut version is installed, which software measures the parts and which MES records the lot. And, for each one, which file it exports.
Surveys the G-code dialect of each control (Fanuc, Sinumerik, Heidenhain), the columns of the CMM CSV, which are specific to each software, the QIF version and what links serial, program and revision.
Works on copies of the exported files. Doesn't operate the licensed software on its own, doesn't send anything to the machine or the CMM and doesn't write to the quality record.
Text check first, Vericut in batch next, a person at the end. Defines where each log and report goes and what the summary needs to show for the programmer to decide quickly.
The G-code reader, the Vericut batch with LGFILNAM=, report= and auto-diff=, the CMM CSV checker, or the NX Open journal the case calls for.
First runs on programs and reports whose result is already known, including one with a deliberate error, and checks by the output: the log has Error and Collision where it should, the CSV flags the out-of-tolerance feature.
With your OK, the script starts running on the real programs and reports. The summary goes to the programmer and Quality; releasing the part stays with them.
Versions, paths, the layout of each export and what was confirmed on your installation. The usage procedure for each script is written down for the audit.
Nothing AI-generated goes to the machine, the CMM or the quality record without human validation and sign-off. AI doesn't replace a qualified tool or the person with authority to release the part.
From the model to the approved part: which software does each step and how it can be automated without the interface.
| Task | Software | Headless path |
|---|---|---|
| Program a 5-axis machined part | NX CAM, hyperMILL, Mastercam, DELMIA Machining | NX Open GenerateToolPath + Postprocess via run_journal; NET-Hook in Mastercam |
| Generate G-code for the machine | CAM post (Post Configurator, .pst) | Post call in the CAM's own script |
| Check collisions and excess stock before the machine | Vericut | vericut batch "vcp=..." "report=..." "auto-diff=..." |
| Optimize feed rates | Vericut Force | optimize option in the batch |
| Quick check of the NC text (tools, travel, feed) | Custom script | Script that reads the program text, before the simulator |
| Design composite plies | Fibersim, CATIA Composites | Inside CAD; flat pattern export |
| Program AFP/ATL (automated fiber placement or tape laying) | Vericut Composite (VCP/VCS), CatFiber, TorFiber/TorLay | NC output of the layup path |
| Program CMM offline | Silma X4, PolyWorks, CMM software | DMIS program (CMM programming language) |
| Inspect and report | PolyWorks, Metrolog X4 | Macro; CSV export |
| Check report tolerances | Custom script | 02_check_cmm_csv.py |
| Trace lot and part (as-built record) | DELMIA Apriso, Opcenter Execution | Database query or MES integration |
| Production sequencing | Opcenter APS, DELMIA | — |
Three steps. Each one only makes sense after the previous one has shown results in your operation.
A proposal, not a promise
You hand over an NC program or a CMM report and Octo prepares the list of what stands out, for human review.
An operator runs vericut batch on the folder of new programs and Octo reads what came out.
Serial, NC program, model revision and inspection report read together, from MES and PLM exports.
Every point below has a source published by the vendor, the project or the responsible agency. The sources are in the next section.
4
points with a published source, each with its reference alongside.
vericut batch "vcp=..." runs and exits; batchp opens the window at the end. LGFILNAM= sets the log, report= the report, auto-diff= compares with the design model and optimize turns on feed rate optimization.Source: online help documented by the Vericut vendor, Batch Vericut and Command Line Options pagesOcto prepares everything, but does not sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and generates the documents: spreadsheets, reports, drawings 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: review by the signerOcto does not sign. Designs, technical reports, ART/RRT (Brazil's professional responsibility records), accountability reports and any official document are still signed by the company's or agency's licensed professional: here, the responsible engineer and the certification authority.
Sign-off: responsible engineer and certification authorityOfficial sources used in the research: software vendor, user company or standards body.
GenerateToolPath, PostprocessThe assessment starts by reading the programs, logs and reports your plant already exports, without changing anything. You get a map of what can be checked and automated, and decide with it in hand.