What the data for this category looks like
Data for this category originates from ERP orders and inventory, BOMs and process routes, equipment capacity, staff shifts, work-in-progress items, and supplier deliveries. Daily business documents include sales orders, master production plans, material requirement plans, weekly and daily scheduling tables, work orders, material shortage lists, and delivery change notices. Data updates run daily, weekly, or trigger in real time when orders are released or exceptions occur. Document fields include order numbers, material codes, capacity man-hours, work-in-progress quantities, delivery dates, and more. Corresponding units include pieces, hours, days, and others.
What constraints these characteristics impose on the citation sources and traceability link
The multi-source, high-frequency update nature of the data requires the traceability link to accurately match the version and type of original documents. This prevents citing expired or irrelevant business data. Complex hierarchical document associations—such as work orders linked to corresponding BOMs, and shop scheduling tables linked to sales orders—require the traceability link to display the full association chain. Diverse field and unit attributes require the traceability link to clearly mark specific information and units for corresponding fields. This ensures business personnel can verify cited content. Frequent update trigger scenarios require the traceability link to support real-time or near-real-time document index updates. This ensures cited content aligns with current business status.
How to set the configuration
This configuration applies to FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale for This Setting |
|---|---|---|
quoteMaxToken | 800–1200 token | Single document content for production planning and shop scheduling is lengthy. Sufficient original information must be retained to enable complete traceability |
responseData | Enabled | Original document association fields, update times, and other traceability information must be returned. This ensures citations can be traced to specific business documents |
detail | Enabled | Production scheduling data typically links to multi-layer documents such as work orders, BOMs, and equipment capacity. The full traceability hierarchy must be displayed |
| Single search limit | Top 5–7 entries | Production planning data has many associated items. Enough associated documents must be covered while avoiding interference from redundant information |
| Traceability document filtering | By original document update time | Scheduling data updates frequently. Business documents with the latest versions must be prioritized for citation |
Three common configuration errors
- Setting
quoteMaxTokento less than 600 tokens. This truncates long production planning document texts, leading to query timeouts or incomplete results. The issue occurs because the long text nature of documents in this category is not accounted for, and insufficient token space is reserved. - Failing to enable the
responseDataconfiguration. This prevents the answer from linking to business documents in the original knowledge base, leading to discrepancies between the answer and knowledge base content. The issue occurs because the response data traceability configuration is not enabled, and only AI-generated generic content is used. - Not binding the knowledge base search result variable in workflow nodes. This prevents the first search result from being output, leading to empty variables. The issue occurs because the corresponding knowledge base index is not linked in the node configuration, or search result fields are not mapped correctly.
How to confirm the configuration is properly set
- Initiate a scheduling query that references a specific sales order. Check if the answer includes field information such as the original document’s order number and process man-hours.
- View the traceability module in the answer. Confirm that identifiers or update times for associated work orders, BOMs, and other documents are displayed.
- Initiate a query by simulating a delivery change exception scenario. Confirm that traceability information matches the latest updated delivery change notice.
- Check the variable configuration for the workflow node. Confirm that the first data field of the knowledge base search result is correctly bound.
The values provided are common starting points and should be measured against the reader's own samples.