What this category of data looks like
This category of data covers the entire electronic assembly workflow. Daily documents include BOM and coordinate files, line change lists, stencil and reflow oven temperature records, first article confirmation reports, SPI/AOI inspection reports, maintenance records, and traceability labels. Data sources include BOM, Gerber and coordinate files provided by customers, factory MES systems, solder paste and component batch ledgers, data collected from mounters, SPI/AOI equipment, and reflow oven temperature collection systems. Data updates are triggered in real time by work orders and line change operations. Fields in a single document include part number, reference designator, component batch, inspection parameters, reflow oven temperature curve, and no additional statistical percentage data.
What constraints these characteristics impose on the "source citation and traceability" link
Data sources for this category are scattered and updated in real time. Citation and traceability processes must bind exclusive data sources for corresponding work orders to avoid mixing data across work orders. Single documents have multiple fields linked to production steps. Citations must accurately match fields such as part number, reference designator, and component batch to prevent invalid matches. Data updates in real time with work orders and line changes. Traceability must link document generation timestamps and work order IDs to ensure cited content is valid for the current production step. Citations for exception reports and process documents must directly link to original inspection equipment and MES records to provide clear basis for subsequent quality traceability.
How to set the configuration
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | SMT documents contain long text such as reflow oven temperature curves and inspection reports, and need to cover complete cited content |
responseData | Associate work order ID and component batch fields | Accurately match exclusive data for production work orders to avoid confusion across work orders |
detail | Enabled | Display original fields of cited content such as part number and reference designator to meet traceability requirements |
| Single search limit | Top 6 entries | SMT documents have many associated fields, need to cover sufficient matching results while avoiding redundancy |
| Cited content template | Include document generation timestamp, work order ID, and original inspection parameters | Provide clear original data identifiers for traceability |
Three common errors
- Scenario: No optional values appear when selecting variable references in citation configuration. Cause: Variable output for corresponding work order ID and component batch was not configured in the preceding node.
- Scenario: Cited content cannot match corresponding reflow oven temperature records. Cause: Real-time updated data source timestamp was not bound, and old version line change list data was cited.
- Scenario: Cited content is truncated and original documents cannot be traced. Cause:
quoteMaxTokenvalue is too small, failing to cover complete inspection report content.
How to confirm configuration is complete
- Generate a process document for a simulated work order, check whether cited content is linked to BOM and reflow oven temperature record data for the corresponding work order.
- Manually modify fields of a test document, verify whether cited content updates synchronously to confirm binding to real-time data sources.
- View the citation log in FastGPT v4.17.0, confirm that each piece of cited content is marked with document generation timestamp and work order ID.
- When drafting an exception report, cite content from SPI/AOI reports, check whether detection data for the corresponding component batch can be matched.
The values provided here are common starting points, and should be measured against the reader's own samples.