What This Category of Data Looks Like
This category of data covers core documents including bid invitations, qualification prequalification documents, bidding documents, bid submissions, bid evaluation reports, successful bid candidate notices, and successful bid result announcements. Data sources include the national public resource trading platform, local public resource trading platforms, engineering approval systems, and bidding supervision systems, with a daily update frequency. Documents include dedicated fields such as section number, qualification requirements, bill of quantities, bid evaluation expert records, and successful bid results. The field structure varies significantly across different document types, and the length of core review content for a single document spans a wide range.
Constraints on the "Citation Source and Traceability" Link
Daily updated data sources require the citation traceability process to support incremental synchronization and real-time verification, to ensure recalled content is the latest valid documents. Multiple document types and differentiated fields require precise field matching rules to be set for different documents, to avoid including irrelevant content in review references. Differences in data source permissions across entities require the process to support unified permission management for multi-source data, to ensure reviewers can only access documents within their corresponding permission scope. The serious consequences of incorrect successful bid results require traceability information to include complete source identifiers, to facilitate subsequent verification and accountability.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Maximum citation token count | Set quoteMaxToken to 800–1200 tokens | Matches the field length of core review documents for a single bidding project, to avoid truncating key content such as qualification requirements and bill of quantities |
| Number of recalled citations per request | Top 5 entries | Aligns with the range of reference document counts for a single section in the engineering bid evaluation process, to avoid information overload that reduces review efficiency |
| Minimum citation relevance threshold | Calibrated based on actual testing | Adapts to differences in document similarity across source platforms, to ensure recalled content matches the review needs of the current declaration project |
| Response data format | Set responseData to a structured format with source identifiers | Facilitates quick traceability to original documents on the corresponding trading platform during file review, to meet archiving requirements |
| Detail display toggle | Enable detail | Displays field details of cited documents, to facilitate verification of consistency between declaration materials and original documents |
Three Common Misconfigurations
- Consistent output when configuring knowledge base IDs or citation variables, with errors after applying variables. Phenomenon: An error status code for parameter errors is returned when calling the review interface, or citation source fields are empty. Cause: The data source permissions for the corresponding public resource trading platform were not bound in the FastGPT v4.17.0 system configuration, and the variable mapping was not associated with the correct data source ID.
- Unable to filter irrelevant citations during mixed retrieval. Phenomenon: Recalled results include bid invitations for non-current sections or irrelevant performance documents. Cause: Filter rules were not set based on dedicated fields such as section number and project code, and the retrieval scope was not limited to documents associated with the current declaration project.
- Citation parameter settings do not match business requirements. Phenomenon: Too many recalled results increase review time, or too few recalled results fail to cover core review content. Cause: The
quoteMaxTokenand citation recall count parameters were not set reasonably based on the update frequency and field characteristics of bidding documents.
How to Confirm Proper Configuration
- Upload a test bid submission and corresponding bid invitation document, trigger the review process, and check whether the returned results include the source platform name and document identifier for each citation.
- Manually enter a section number that does not belong to the current project, to verify whether irrelevant documents of this type are automatically filtered from retrieval results.
- Trigger a complete review process, and check that the returned cited content is not truncated and covers core review fields such as qualification conditions and performance requirements.
- Call the historical conversation interface to confirm that past bid evaluation records can be normally retrieved and used as citation sources.
The values provided are common starting points and should be measured against the reader's own samples.
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-28.