What the data for this category looks like
Technical documents for petroleum refining cover operating procedures, production plans, material balances, distillation outlet quality reports, interlock ledgers, shift handover records, and change management documents. Data sources include DCS/APC systems, LIMS systems, tank farm metering systems, crude oil evaluation databases, equipment management systems, and energy management systems. Update frequencies are divided into real-time (e.g., DCS process parameters), per shift (e.g., shift handover records), and daily (e.g., material balance reports). Document fields include process parameter values, material component proportions, equipment numbers, and timestamps. Units cover temperature, pressure, flow rate, mass fraction, and similar metrics.
What constraints these characteristics impose on tool calling and plugins
Multiple continuous petroleum refining units are coupled via material and hydrogen networks. Raw material properties fluctuate widely, so tool calling must pull real-time DCS data and crude oil evaluation data in real time. Plugins must support short-interval polling or event triggering. There are large differences in fields across multiple document types. Plugins must adapt to return formats of different data sources to avoid field parsing errors. Real-time updated tank farm metering data and daily updated material balance reports need differentiated calling priorities to prevent low-priority data from occupying call quotas. Compliance reviews of interlock ledgers and change management documents require tool call results to carry complete traceability fields, ensuring traceability of cross-reviews.
How to Configure Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | Set to auto and bind the dedicated refining tool group | Limit the scope of tool calls, avoid calling irrelevant plugins, improve review targeting, and comply with FastGPT v4.17.0 tool calling rules |
| Workflow/API function-call configuration | Enable and limit returning the top 5 core field data | Ensure tool return data matches the core process and material information required for reviews, reduce unnecessary processing |
| Plugin trigger timing | Trigger on document update events, poll every 10 minutes when no events occur | Adapt to multi-frequency data update requirements of real-time, per-shift, and daily updates, balance timeliness and resource usage |
| Global variable initialization | Preset typical crude oil density and initial atmospheric unit load values | Resolve the issue of empty variables before plugin calls, avoid initial call failures |
| Call timeout setting | 600 seconds | Cover the response duration of complex calculation tools such as crude oil evaluation and material balance |
| Variable update rule | Synchronously update the corresponding global variables after each tool call | Ensure cross-reviews always use the latest process and material data |
Three Common Mistakes
- Phenomenon: Sporadic empty content returns when calling the company's self-developed model, and the call process gets stuck for 10 seconds before throwing an error. Cause: The dedicated refining tool group is not bound, and
toolChoiceautomatically calls incompatible plugins, causing abnormal model responses. - Phenomenon: Global variables are not updated after plugin execution, and subsequent review steps cannot obtain the latest process data. Cause: Correct variable update trigger rules are not configured, causing valid data returned by the tool to not be synchronized to global variables.
- Phenomenon: An error is reported directly in the tool call link after the workflow starts, with no valid return information. Cause: Core variables are not initialized in advance, and parameters such as crude oil density and unit load required for tool calls are empty, triggering parameter verification failures.
How to Confirm Proper Configuration
- A test request containing refining process parameters can be initiated, and the tool call log reviewed to confirm that only the bound dedicated tools are triggered.
- Plugin calls can be manually triggered, and the global variable panel checked to confirm that returned process data has been synchronized to corresponding variables.
- A document update event can be simulated, and the plugin observed to confirm whether it automatically triggers calls according to the configured timing.
- The timeout setting threshold can be adjusted to verify that tool calls will not terminate early in complex calculation scenarios.
The values provided are common starting points and should be measured against the reader's own samples.