Machining Intelligence

Integrated drawing and machining-program review

Compare drawings, NC, tools, conditions and change records during preparation and review. The 3D experience is the toolpath-viewing component, not the entire machining application.

CURRENT · Internal validation

3D work instructions from machining information

Organize machining paths and operation order by orientation, with a 3D overview and detailed views. Export work instructions containing tools, NC lines, spindle speeds and feed rates to PDF.

  1. Machining informationReview paths, operation order and tool conditions by orientation
  2. Work instructionsCompose the 3D overview and orientation details
  3. Document exportExport a PDF for review and sharing

The public sample uses synthetic geometry and NC in a separate test. It does not establish cutting performance, collision clearance or approval for shop-floor use.

Screens and the PDF are actual outputs from the Korean-language product.

Turn drawings and NC into work people can review.

Support machining preparation by comparing NC, drawings, tool and measurement information. Inspect the synthetic sample toolpath directly in the public browser demo.

Inputs

NC text · drawings/reference geometry · tools/conditions · measurements and change records

Results to review

Per-tool paths · review conditions · machining information and change history · evidence for the next decision

View the toolpath in 3D
Actual Flowmatic browser 3D viewer displaying the public synthetic NC sample
Interactive · public synthetic sample

Browser functionality · program scope · further integration

01

Public browser

Display supported NC paths, tools and diameters, with a basic-motion time estimate for reference.

02

Machining program

The desktop prototype supports draft processes and NC for supported geometry, change review, and 3D work-instruction PDF export. Its scope is separate from the public web demo.

03

Further validation

Drawing interpretation and complete process generation beyond supported geometry, along with general-purpose CNC transfer, USB synchronization and AI integration, require further implementation and validation.

For path review and theoretical time reference. Not a replacement for cutting trials, collision validation, machine safety approval or control.

Technical structure and detailed conditions

Manufacturing Recipe context

The manufacturing contextthat makes separate files one process

Machine Setup connects coordinates and tools with fixtures, reference pins, and setup references in the same process context.

WCSINDEXToolFixtureReference PinPad / Setup Reference
Product / ItemLineProcess GroupOperationFeatureMachine SetupG-code / Measurement / Work Standard

Generate · Safety Contract · Assemble

From feature to unit process.From checked blocks to final NC.

HOLE GROUP
Drill → Tap
FACE A
Milling
BORE B
Rough → Finish
OP20BOUNDARY CHECK
PASS / BLOCK
FINAL NC

Air-gapped / USB operation

One operating baselinewithout a connected factory

Verify revision, hash, manifest, and source. Divergent changes are never overwritten silently; they move to conflict review.

CONNECTED ENVIRONMENTEngineering / ReferenceNAS / Shared FolderLocal Machining Intelligence
AIR-GAPPED ENVIRONMENTVersioned Transfer PackageUSB · Verify revision / hashIsolated Local PCCNC / Local Operation

Same → No update · Newer → Safe update · Divergent → Conflict review

Active development / PoC

01 — Understand Existing NC

Analyze tool changes, WCS, INDEX, cycles, coordinate motion, repeated geometry, and CAD features in unmanaged G-code. Results begin as INFERRED and become CONFIRMED only through user review.

  • Legacy / unmanaged G-code
  • probable Operation / Feature
  • Code Block boundary
  • Tool / WCS / INDEX context
  • INFERRED → USER CONFIRMED

Source-level validated baseline

02 — Manufacturing Recipe

Store the machining plan as a product, process-group, and operation Recipe—not a loose file list. Paths, shared holes, machining operations, temporary G-code, unit-process code blocks, final order, and final assembled G-code share one structure.

  • Product → Process Group → Operation
  • Path / Shared Hole / Machining Operation
  • Unit-process Code Block
  • Final Block Order
  • Final Assembled G-code

Source-level validated baseline

03 — Generate & Assemble

Create machining units from features and assemble multiple unit processes into one final NC program. Complex freeform toolpaths remain within specialist CAM.

  • HOLE GROUP → Drill Block → Tap Block
  • FACE A → Milling Block
  • BORE B → Rough Block → Finish Block
  • OP20 → FINAL NC

Source-level validated

04 — Block Boundary Safety Contract

Code blocks are checked for machine-state continuity before final NC assembly. Under a fail-closed rule, UNKNOWN or UNSAFE state blocks assembly and requires review.

  • distance mode / plane / unit / WCS
  • cutter and tool-length compensation
  • cycle / spindle / coolant / tool state
  • Safe-Z / INDEX / unsupported stateful code
  • PASS → Assemble
  • UNKNOWN / UNSAFE → Block assembly → Review required

Active development / PoC

05 — Measurement / Compensation

Return measurement to the relevant feature and process as a correction target. The current scope is correction targets and operator guidance—not completed machine-side autonomous correction.

  • Measurement → Coordinate Mapping
  • ΔX / ΔY / ΔZ / Δθ
  • Correction Solver
  • Target Feature / NC / Setup
  • future machine adapter

Active development / PoC

06 — Managed G-code Metadata

Carry item, line, and process context in a Managed Metadata Comment Block so another PC can recover the original machining context. Managed content is replaced or refreshed on export rather than appended repeatedly.

  • Required: Item / Product, Line, Process
  • Optional: Operation, Feature, Code Block, Recipe revision
  • Preserve user comments
  • Distinguish managed comments
  • Replace / Refresh; keep one metadata block

Active development / PoC

07 — Air-gapped / USB Operation

Local execution remains available where a central server or NAS cannot be connected. USB is treated as an approved transfer boundary that verifies version, source, and integrity—not as blind file copy.

  • version / revision / hash / manifest
  • signed or approved package / source identity
  • same → no update
  • newer → safe update
  • divergent → conflict review
  • applied revision / rollback history

Modular adapter direction

Machine Connectivity

Direct machine connection is not a starting requirement. Begin with local data and estimated state, then add a dedicated adapter where needed.

  • Base: Central / Local Estimated State
  • Optional future adapter
  • Verified Machine State
  • FOCAS / OPC UA / MTConnect / FTP-DNC / RS-232-custom examples only

Prototype

Work Standard from the Recipe

Turn tool, INDEX, feature, machining order, and review points from the same Manufacturing Recipe into the field work standard.

  • Recipe → NC
  • Recipe → Measurement Context
  • Recipe → Work Standard

Deployment scope

This does not replace specialist CAM. The Safety Contract is a deterministic source-level check, not CNC safety certification. G-code inference, managed metadata, USB synchronization, CMM integration, and machine-side autonomous correction remain development and PoC scope.

Request a demoExplore the products