Tendering Document and Quotation Preparation for Lithium-ion Cell Manufacturing: Deployment and Upgrade

Daily documents for lithium-ion cell manufacturing include batching records, coating and calendering parameters, winding or lamination records, liquid

What Data for This Category Looks Like

Daily documents for lithium-ion cell manufacturing include batching records, coating and calendering parameters, winding or lamination records, liquid injection records, formation and grading data, OCV and safety test reports. Data is sourced from raw material batch ledgers, production MES systems, slurry and coating testing equipment, dew point monitoring devices, formation and grading cabinets, and laboratory test data. Data is updated in real time per production batch and per individual cell. Fields include batch number, test values, collection time, associated equipment number, and more. Units involve electrochemical-specific measurement standards such as voltage, capacity, and dew point temperature.

Constraints on Deployment and Upgrade from These Data Characteristics

The data characteristics of this category impose multiple constraints on the deployment and upgrade process. Multi-source and heterogeneous data sources require adapting to docking protocols for multiple types of equipment during deployment, and compatibility with data access from newly added formation and grading cabinets and dew point monitoring devices during upgrades. The high real-time update rhythm requires the knowledge base’s incremental synchronization frequency to match the production batch cycle, preventing index data from lagging behind production progress. Electrochemically specific fields and units must retain their original format during configuration, and measurement standards must not be adjusted arbitrarily, to ensure parameters in tendering documents are accurate and traceable. Additionally, production data involves security and compliance requirements, so tiered permissions must be configured during deployment to prevent unauthorized access to sensitive test data.

Configuration Settings

This configuration applies to FastGPT v4.17.0.

Configuration ItemRecommended ValueRationale
MONGODB_URImongodb://fastgpt:securepass@mongodb1:27017,mongodb2:27017/fastgpt_lithium?replicaSet=rs-lithiumThis category has large data volumes and real-time updates. Replica set configuration ensures read/write stability and data persistence
REDIS_URLredis://:redispass@redis-cache:6379/1High real-time production data retrieval requires cached results. Database 1 isolates business cache from other system caches
STORAGE_S3_ENDPOINThttp://local-storage:9000Most production documents are test reports and parameter records. Local object storage ensures data read speed and permission control
Knowledge Base Single Recall LimitTop 6–10 entriesTendering documents require linking multi-dimensional batch data. An appropriate number of recall results covers core parameters and test records
Document Chunk Length900–1300 charactersDocuments contain long parameter sequences and test reports. This range preserves parameter association logic and avoids truncation of critical information
FE_DOMAINhttps://lithium-manu.fastgpt.siteThis domain is used to bind the official website access address, ensuring compliance of the access path after deployment

Three Common Configuration Mistakes

  • Phenomenon: When creating a new knowledge base and uploading documents, no image indexing model options appear in the interface. Cause: Local deployment did not configure FILE_TOKEN_KEY and associated image processing services, resulting in the image indexing function being disabled.
  • Phenomenon: After Docker deployment is complete, accessing the configured domain name returns no response, and the browser shows a connection timeout or 502 error. Cause: Container ports were not correctly mapped, or the FE_DOMAIN configuration does not match the actual access domain name, causing requests to fail to route correctly.
  • Phenomenon: A version update description pop-up appears every time a new conversation window is opened. Cause: The version update prompt switch was not disabled in the configuration file, causing the pop-up to trigger for every session.

How to Confirm Successful Configuration

  • Access the configured FE_DOMAIN address, confirm the page loads normally without 502, 404, or connection timeout errors.
  • Upload a production document containing coating and calendering parameters, perform a batch number search, and confirm the returned results include matching document content.
  • Check the database connection logs, confirm that stable connections have been successfully established with the services configured in MONGODB_URI and REDIS_URL.
  • Disable the version update prompt switch and restart the service, confirm that no version update description pop-up appears for new conversations.

The values provided are common starting points and should be measured against the reader's own samples.