What the data for this use case looks like
Business data for petroleum refining scenarios originates from DCS/APC control systems, LIMS laboratory information management systems, tank farm metering systems, crude oil evaluation reports, equipment management systems, and energy management systems. Documents generated daily by business departments include operating procedures, production plans, material balance reports, distillate export quality reports, interlock ledgers, shift handover records, and change management documents. Data update frequencies cover real-time (such as unit operating parameters), shift-based (such as shift handover records), and daily (such as material balance reports). Data fields include material flow, product distillate indicators, equipment operating status, and more, with corresponding units such as tons, cubic meters, degrees Celsius, and others.
What constraints do these characteristics impose on deployment and upgrades?
The data characteristics of petroleum refining scenarios impose multiple constraints on the deployment and upgrade phase. Multi-source and heterogeneous data sources require configuring cross-system permission and data synchronization rules during deployment, and adapting to the interface formats of different systems such as DCS/APC and LIMS. Differentiated update frequencies require setting layered synchronization scheduling mechanisms to match real-time, shift-based, and daily update rates. Diverse document types cover structured reports and unstructured ledgers, requiring preset parsing and chunking logic adapted to different text structures. Bid documents need to integrate logistics and energy data coupled across multiple units, so configuration interfaces for cross-unit data aggregation must be reserved during deployment to ensure the accuracy of bid data.
How to configure the settings
| Configuration Key | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 20–30 entries | Adapts to concurrent data pull requirements from multiple systems in the refining scenario, avoiding connection pool exhaustion |
REDIS_URL | redis://:custom password@redis service address:6379/0 | Stores real-time updated unit operating parameters and temporary retrieval contexts to ensure low-latency access |
STORAGE_S3_ENDPOINT | Enterprise internal object storage service address | Stores large-volume documents such as crude oil evaluation reports and interlock ledgers, adapting to the enterprise's existing storage architecture |
FILE_TOKEN_KEY | String generated according to enterprise unified key rules | Ensures the security of document access tokens, preventing unauthorized access to sensitive process data |
ROOT_KEY | Determined through actual measurement and calibration | Manages the system's highest-privilege account, and must match the enterprise's internal permission control requirements |
Three Common Mistakes
- Phenomenon: A 403 error is returned when calling the model interface, indicating that the token lacks permission to use the model. Cause: Model binding rules were not configured correctly during deployment, or the token does not cover the model call permissions required for the refining scenario.
- Phenomenon: The system's initial administrative account cannot be logged into after deployment using docker-compose. Cause: The
ROOT_KEYparameter was not set correctly, and the initial permission key was not generated in accordance with specifications. - Phenomenon: Cross-departmental access occurs in bid data submitted by multiple departments. Cause: Account permission isolation rules were not configured, and data access scope was not divided by department.
How to Verify a Correct Configuration
- Run the docker-compose ps command to confirm that all service containers deployed with FastGPT v4.17.0 are in a normal running state.
- Upload a distillate export quality report document to verify that the system can correctly extract core fields such as product distillate indicators and flash point.
- Configure a cross-system data synchronization task to verify that real-time, shift-based, and daily update frequencies can be triggered according to preset rules.
- Test access with an unauthorized account to confirm that sensitive process documents cannot be read by unauthorized accounts.
The values provided here are common starting points and should be evaluated against the reader's own samples.