What the Data for This Category Looks Like
Competitor pricing data is primarily sourced from public bidding announcements, manually submitted bidding documents, industry compliance-registered pricing databases, and enterprise archived historical winning bid records. Data updates follow bidding project cycles. Individual project pricing documents receive 1 to 2 supplementary adjustments before the project opens for bidding. Archived historical data only updates when qualifications or pricing rules change. Most documents are structured tables, with fields including project number, competitor entity name, itemized pricing details, total bid price, pricing validity period, qualification level, and more. Units include CNY, natural days, percentage rates, and other standard units.
Constraints Imposed by Data Characteristics on Knowledge Base Retrieval and Recall
The large number of structured fields and version differences require retrieval to support precise filtering by fields such as project number and competitor entity, to avoid retrieving irrelevant documents. Data updates fluctuate with project cycles, so retrieval must support non-fixed-cycle incremental update trigger logic to prevent retrieving expired pricing information. Individual documents have high proportions of itemized details, so retrieval must support retrieval by content blocks, to avoid interference from irrelevant information caused by retrieving full long documents. Some documents contain sensitive internal negotiation details, so permission configuration must be used to limit retrieval scope and ensure compliance.
Configuration Recommendations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
Recall Count | Top 10-15 entries | Competitor pricing documents are mostly precise single-project matches. Excessive recall will introduce irrelevant project information |
Similarity Threshold | 0.75-0.85 | Balance precision and recall completeness, avoid missing valid information for same category with different pricing |
Chunk Length | 800-1200 characters | Adapt to the paragraph length of itemized details in competitor pricing documents, ensure each chunk contains complete itemized pricing logic |
Incremental Update Trigger Condition | File update time + project status tag | Align with bidding project update rhythm, only recall latest documents after project opening or status change |
Field Filter Rules | Enable matching for project number and competitor entity fields | Directly filter out non-target project pricing documents, reduce invalid recall |
Reranked Return Count | Top 5 entries | Prioritize displaying the most matching core pricing information, align with user needs to quickly locate competitor pricing |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Misconfigurations
- Symptom: Empty results are returned after calling the knowledge base retrieval interface and specifying the target knowledge base via a variable. Cause: The valid ID of the
knowledge_base_idparameter was not filled correctly, or the current session was not granted permission to access the specified knowledge base. - Symptom: Retrieved documents include expired competitor pricing versions. Cause: The
incremental update trigger conditionwas not configured, or old version documents were not filtered via project status tags. - Symptom: Empty processing results are returned when executing knowledge base data processing in a local deployment environment. Cause: The value of the
PARSE_FILE_TIMEOUT_SECONDSparameter was not set correctly, or file parsing failed due to insufficient local storage permissions.
How to Verify Correct Configuration
- Input a search term containing a clear target project number. Verify that returned results only include competitor pricing documents corresponding to that project.
- View the knowledge base's incremental update records. Confirm that update tasks trigger according to preset logic, and only process documents with valid update statuses.
- Call the retrieval interface and specify different similarity thresholds. Verify that the number of returned results changes as expected with threshold adjustments.
- Check the permission configuration of the current calling identity. Confirm that all valid documents in the target competitor pricing knowledge base are accessible.
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.