What Data for This Category Looks Like
This category of data originates from engineering orders, sand, gravel, cement admixture inspection records, aggregate moisture content test results, mixing plant control system data, and laboratory test records. Regularly generated documents include mix proportion notices, opening identifications, production and transport slips, raw material inspection reports, test block records, strength reports, and others. Data updates follow this rhythm: one production and transport slip per vehicle, one inspection record per batch of raw materials, and daily aggregation of laboratory test data. Document fields include mix proportion parameters, aggregate moisture content, mixing feeding amount, slump index, test block strength values, and others. Data updates occur in real time or in batches throughout the production process.
What Constraints These Characteristics Impose on the Source Citation and Traceability Link
Data for this category is updated per vehicle, per batch, and per day. Strong correlations exist between different documents. For example, production and transport slips must link to corresponding raw material inspection records. Test block reports must link to opening identifications. The traceability link requires precise matching of unique identifiers such as vehicle numbers and raw material batch numbers. This prevents mixing data sources across batches or vehicle trips. Correlation fields vary across document types. Dedicated correlation rules must be configured for different document types such as mix proportion notices and strength reports. Production data updates in real time. Traceability must call the latest source data copy. Relying on expired cached data may cause process documents to mismatch actual production parameters. This can lead to quality issues.
Configuration Settings
These configurations are developed based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 1200–1500 token | Ready-mixed concrete documents have long single-block content. This range accommodates multiple sets of parameters such as mix proportions and moisture content, avoiding truncation of critical information |
responseData | Return only metadata and fragments of matching source documents | Precise correlation with unique identifiers of production and transport slips and inspection reports is required. Redundant content must be avoided to interfere with drafting |
detail | Enable full traceability mode | Responsibility fields such as source document generation time and operating personnel must be displayed to meet quality traceability requirements |
| Single search limit | Top 6 results | Source documents linked to single-vehicle production data do not exceed 6 copies. This avoids introducing irrelevant data |
| Knowledge base variable reference | Bind vehicle number and batch number fields | Precisely recall corresponding source data using unique identifiers from the production link |
| Document chunk length | 800–1000 characters | Matches the typical content length of single ready-mixed concrete documents. This ensures complete parameter groups are retained after splitting |
Three Common Misconfigurations
- Phenomenon: When calling knowledge base search, returned source documents do not include the production and transport slip for the corresponding vehicle number, or fields are empty. Cause: Vehicle number and batch number are not bound as knowledge base variables. Only keyword search is used for recall, so precise matching of exclusive data for a single vehicle trip is not possible.
- Phenomenon: The generated process document references expired raw material inspection data. Cause: Rules for real-time source data pulling are not configured. Cached old data copies are used, leading to parameters such as moisture content not matching the current batch.
- Phenomenon: Recalled source document types are mixed. Test block records and transport slips are included together. Cause: Dedicated correlation field rules are not configured for different document types, leading to confused correlation logic.
How to Verify Proper Configuration
- Input the vehicle number and raw material batch number for a single vehicle trip. Check that recalled source documents only include inspection reports and production and transport slips for the corresponding batch.
- Review the end of the generated process document. Confirm that traceability information such as generation time and operating personnel for all cited source documents is labeled.
- Simulate updating aggregate moisture content data for a specific batch. Check that the generated process document automatically updates to the latest parameters.
- Review system logs. Confirm that no errors truncating critical parameters occur during each call.
The values provided here are common starting points. They should be evaluated against the reader's own samples.