What the data for this category looks like
Energy storage intelligent due diligence report data primarily comes from power station SCADA real-time collection systems, batch quality inspection documents from cell suppliers, grid connection dispatch ledgers, and project completion acceptance documents. Data update rhythms fall into three categories: power station operating parameters are refreshed every 15 minutes, cell batch parameters are updated with production batches, and project compliance documents are only iterated at project milestones.
The document structure is fixed into five modules: basic power station information, core equipment parameters, grid connection operation indicators, operation and maintenance logs, and compliance certificates. Fields include energy storage rated capacity (unit: MWh), charge-discharge conversion efficiency (unit: %), SOC control accuracy (unit: %), grid connection voltage level (unit: kV), and other standardized fields with no redundant non-standard entries.
What constraints these characteristics impose on deployment and upgrade
The high-frequency real-time operating parameters, batch-updated equipment parameters, and fixed-structure compliance documents of energy storage due diligence data impose clear constraints on deployment and upgrade processes. First, the 15-minute real-time data refresh requirement means vector recall task intervals configured during deployment must match this rhythm to avoid data delays or resource waste. Second, batch-updated cell and PCS equipment parameter updates require the upgrade process to support incremental indexing modes to reduce time spent on full data reimport. Third, multi-format compliance documents and fixed standardized fields require pre-configured dedicated document parsing rules during deployment to avoid unit or format deviations in field mapping.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
PARSE_FILE_TIMEOUT_SECONDS | 300-600 seconds | Energy storage due diligence reports include multiple large compliance documents and equipment ledgers, requiring sufficient parsing time |
UPLOAD_FILE_MAX_SIZE | 800 MB | Single compliance documents for energy storage projects typically do not exceed 500 MB, with reasonable redundant space reserved |
mcpserverproxyendpoint | http://localhost:8080 | Applies to versions 4.9.6 and above. Default local listening port for locally deployed MCP Server, must match the actual service startup port |
EXTERNAL_LLM_ENDPOINT | Fill in the actual deployed external indexing model address | Meets external indexing model configuration requirements for version 4.9.6, must match the actual model access path |
maxContext | 8000-12000 characters | Energy storage due diligence reports include multi-dimensional equipment parameters and operating data, requiring sufficient context to carry complete information |
INDEX_INCREMENTAL_ENABLE | Enabled | Energy storage equipment parameters are updated with production batches. Incremental indexing reduces full reimport time during upgrades |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material formats, data volumes, and business rules. Specific issues require targeted analysis, and it is recommended to test on your own samples before finalizing settings.
Three common mistakes
- A local MCP Server call returns
500 Internal Server Errorwith a prompt that the proxy endpoint cannot be connected. The cause is that the port configured inmcpserverproxyendpointdoes not match the actual listening port of the local MCP Server, or the http:// protocol prefix is not added. - After upgrade, login prompts
Invalid credentials, and original account passwords cannot be verified normally. The cause is that incremental backups of the user authentication database were not retained during the upgrade process, or the authentication key in the configuration file was reset. - Energy storage equipment parameter fields in generated due diligence reports are empty, or unit conversion errors occur. The cause is that a general document parsing template was used directly during deployment, and no dedicated mapping rules were configured for the fixed fields and units of energy storage equipment.
How to confirm correct configuration
- Run a local MCP Server connectivity test to check if the address configured in
mcpserverproxyendpointcan normally return the service health status. - Upload a typical energy storage compliance document, and check if the parsed fields match the preset energy storage due diligence fields and units conform to industry standards.
- Trigger an incremental indexing task to confirm that only updated batch data is included in the index, and no full reimport process is triggered.
- Upload a test document of maximum size to confirm that the parsing task does not exceed the preset timeout threshold.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.