What the data for this category looks like
Production ledger data for metal cutting machining scenarios originates from product drawings and 3D models, CAPP/CAM systems, machine tool collection terminals, tool management systems, MES, and measurement and inspection tool data. Daily documents include process routes, operation cards, tool lists, CNC programs, first-piece inspection records, patrol inspection forms, and measuring tool calibration records. Most document structures include fields such as operation number, processing parameters, tool model, and inspection tolerance. Units include rotational speed r/min, feed rate mm/r, dimensional tolerance mm, and others. Update frequency is triggered by work orders, single-piece processing, spot checks, or tool changes, with no unified fixed cycle.
What constraints do these characteristics impose on document parsing and chunking
The multiple document types in this scenario bring parsing adaptation constraints: Process routes and operation cards contain structured tables, and cell field associations must be retained. CNC programs are strictly formatted G-code text, and incorrect splitting due to line breaks or spaces must be avoided. Tool lists and measuring tool calibration records often include embedded images or scanned copies, and chunking after image-text parsing must be supported. High-frequency work-order-level data requires chunking logic to adapt to the complete process of a single work order, avoiding invalid context splicing across work orders. Some documents have long text paragraphs, and chunk boundaries must be controlled to match business logic nodes, avoiding random character-based splitting.
Configuration settings
The following configurations are adapted for FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
chunkSize | 800–1200 characters | The single-paragraph content length of operation cards and process routes in this scenario falls within this range, which retains the integrity of process logic |
chunkSplitter | Customized by document type | CNC programs need to be split by G-code blocks, operation cards need to be split by table rows or paragraphs; generic chunkers cannot adapt to multiple document formats |
customPdfParse | Enabled | Process drawings and inspection records in this scenario are mostly in PDF format; enabling this retains the parsing association between text and embedded images |
PARSE_FILE_TIMEOUT_SECONDS | 300–600 seconds | Parsing large CNC programs or multi-page operation cards takes longer, avoiding timeout interruptions |
UPLOAD_FILE_MAX_SIZE | 500 MB | 3D model-related documents or batch work order ledgers in this scenario may occupy large storage space |
chunkSettingMode | Manual configuration | Chunking rules need to be adjusted for different document types to adapt to the exclusive business document structure of metal cutting machining |
Three common mistakes
- Phenomenon: A Word document with embedded images is uploaded to the knowledge base, and the Q&A test cannot call the image content. Cause: The
customPdfParseconfiguration is not enabled, and the chunking logic for establishing image-text association is not implemented. - Phenomenon: After a CNC program G-code file is uploaded, the parsing result has scattered meaningless character fragments. Cause: The
chunkSplitteris not configured to adapt to code block splitting, and the generic chunking rule incorrectly splits code logic. - Phenomenon: When batch work order ledgers are uploaded, the parsing task triggers a timeout error. Cause: The
PARSE_FILE_TIMEOUT_SECONDSsetting value is insufficient, and it does not adapt to the parsing duration of large documents.
How to confirm the configuration is correct
- Upload a single-page PDF of an operation card with a structured table, and verify that the parsing result completely retains the association between operation number, processing parameters, tolerance values and other fields.
- Upload a standard segment of G-code CNC program, and verify that the chunking result is split by code logic blocks, with no scattered character output.
- Upload a process ledger compressed package not exceeding 500 MB, and confirm that the parsing task does not trigger a timeout exception.
- Enable Q&A testing, upload a first-piece inspection record with dimensionally annotated images, and confirm that the answer can associate the inspection data in the images.
The values given are common starting points and should be measured against the reader's own samples.