What this type of data entails
Petroleum refining scenario process specification and technical standard Q&A data covers daily documents including operating procedures, production plans, material balance, distillation outlet quality reports, interlocking ledgers, shift handover records, change management files, and more. Data sources include DCS/APC systems, LIMS laboratory management systems, tank farm metering systems, crude oil evaluation databases, equipment management systems, and energy management systems. Data update cycles cover three levels: real-time, per shift, and daily. Documents include fields with clear units such as distillation temperature, material flow, tank farm liquid level, and equipment interlocking values.
What constraints these characteristics impose on the tool calling and plugins workflow
Multi-source heterogeneous data sources require tool calling to adapt to interface formats of different systems, to avoid calling failures caused by format incompatibility. Real-time updated DCS/APC data requires tool calling to have low-latency capabilities. Set reasonable timeout thresholds to match data return rhythms. For ledger-style documents updated per shift or daily, limit the time range of data retrieval during tool calling, to avoid introducing expired information that affects process judgment. Material balance data from multiple coupled devices requires tool calling to associate logs and reports from multiple nodes, and support joint querying of multiple parameters. Fields with clear units require tools to automatically match unit formats during calling, to prevent unit confusion during calculation or display.
How to set the configurations
These configuration items are compatible with FastGPT v4.17.0.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Allows the model to independently select tools suitable for petroleum refining scenarios, covering multi-source data retrieval needs |
| Single tool call return count | Top 3 entries | Avoid exceeding the context window, while covering core process parameters |
| Tool call timeout duration | 600 seconds | Matches the real-time data query latency of DCS/APC systems |
| Context window retention duration | Within one shift update cycle | Matches the per-shift update rhythm of shift handover records and interlocking ledgers |
functionCall parameter validation | Enable unit matching rules | Adapts to fields with units such as distillation temperature and tank farm liquid level in refining data |
| Maximum context length for tool calls | 8000 token | Adapts to the needs of multi-document joint retrieval in petroleum refining scenarios |
Three common configuration errors
- Fail to parse unit formats after calling interfaces that return streaming data, leading to missing or confused units in displayed distillation outlet quality data. This occurs because the field unit matching validation for tool calls is not enabled, and raw values returned by interfaces are used directly.
- Do not filter tool call output content before displaying it in conversation results, causing process personnel to fail to quickly obtain core Q&A conclusions. This occurs because the switch to hide original tool call logs is not configured, and only AI-sorted conclusions are not set to be output.
- Do not limit the time range of data retrieval, leading to retrieval of expired shift handover records or change management files, which affects the accuracy of process judgment. This occurs because time dimension parameters for data updates are not bound, and tool calls retrieve full historical data by default.
How to confirm configurations are properly set
- Initiate a query containing crude oil evaluation parameters, verify that the data sources returned by tool calls include the crude oil evaluation database, and that fields have correct units.
- Simulate a process fluctuation scenario to initiate a query, check that the tool call timeout duration matches the preset 600 second threshold, and no timeout errors occur.
- Initiate a material balance query associated with multiple devices, confirm that the number of results returned by tool calls is the top 3 entries, and do not exceed the context window limit.
- View the conversation interface, confirm that only AI-sorted process conclusions are displayed, and no original tool call request and response logs are shown.
The values provided here are common starting points, and should be measured against the reader's own samples.