What the data for this category looks like
Data for this category is generated around the VIN of a single vehicle. Sources include ERP/MES systems, VIN and configuration systems, supplier batch libraries, workshop tightening tools, EOL offline inspection lines, and quality traceability systems. Daily documents cover production orders, VIN lists, assembly work instructions, tightening torque data, offline inspection reports, rework records, and consistency release documents. Data is generated in real time per vehicle, with batch data aggregated per shift. Fields include VIN, tightening torque values, inspection item results, part batch numbers, and more. Some parameters have clear units, such as newton meters for tightening torque.
What constraints these characteristics impose on the tool calling and plugins workflow
The single-vehicle VIN acts as the core matching field. Tool calls must use the VIN as an exact retrieval key to avoid configuration mismatches caused by fuzzy matching. Real-time generated tightening data and offline inspection data require plugin calls to support low-latency responses, to fit workshop production cycles. Concurrent requests from multiple data sources due to mixed-model production across multiple workstations require limiting the number of data sources per single call, to prevent excessive server load. Batch rework records and release documents require plugins to support filtering data by time range or batch, to fit shift-level aggregated analysis needs.
How to set the configuration
toolChoice and functionCall are core tool calling configuration items. The following configurations are based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Adapt to multi-type data source call requirements in mixed-model production, automatically match corresponding tools |
| Workflow/API function-call configuration | Enabled | Support precise calling of corresponding assembly work instructions, tightening data and other documents by VIN |
| Plugin timeout threshold | 600 seconds | Cover time requirements for batch VIN data retrieval and multi-station data aggregation |
| Maximum number of data sources per single call | Top 6 | Match the maximum 6 core data source configurations involved in a single workshop vehicle |
| Data filtering rule | Match by VIN | Align with the VIN-centric traceability logic of this category, avoid interference from irrelevant data |
Three common errors
- Symptom: An internal server error prompt appears when installing a database connection plugin. Cause: The whitelist permission for database connections is not configured, or the driver files required by the plugin were not correctly uploaded to the FastGPT deployment directory.
- Symptom: Data cannot be saved normally when calling the MinIO storage plugin. Cause: The MinIO access key and bucket permissions are not correctly configured, and the connectivity of the storage bucket was not verified.
- Symptom: An empty value is returned when calling an API to obtain dataId. Cause: The correct VIN was not passed as a retrieval parameter, or no associated data record for the corresponding VIN was generated in the data source.
How to confirm the configuration is correct
- Run a tool call test for a single VIN, check whether the corresponding assembly work instructions and tightening data can be returned.
- Trigger a plugin call for batch VIN data, check whether the server load is within a reasonable range.
- Call the MinIO storage plugin to save test data, check whether the target file is generated in the corresponding storage bucket.
- Check the running logs of the database connection plugin, confirm that there are no permission error or connection timeout records.
The values provided here are common starting points and should be evaluated against local samples.