What the data for this category looks like
Data related to water utility revenue yield comes primarily from internal production scheduling systems and financial ERP modules of water utilities, as well as public pricing filing data released by local municipal water supply authorities. Data is updated on a daily schedule: a full summary document for the previous day is generated every early morning. The document uses a structured format, including fields such as statistical date, total water supply scale, actual water sold, unit water production cost, total water sales revenue, sewage treatment subsidy income, pipe network loss ratio, total operating cost, and distributable profit amount. All fields use standardized measurement units such as cubic meters, yuan, and ten thousand yuan.
What constraints do these characteristics impose on the form and interaction link
The multi-source nature of water utility data requires forms to support connecting to data sources from multiple internal systems, with controls configured for cross-system data source integration. The daily update rhythm requires forms to load the previous day's data by default, and limit date selection to a single day to avoid confusion caused by pulling multi-day data. The large number of fields strongly tied to operating processes requires splitting the form into four modules: basic statistics, cost accounting, revenue composition, and benefit evaluation, to reduce user operational burden. Standardized measurement units require forms to preset fixed unit controls, and prohibit user custom input, to prevent data errors caused by inconsistent units.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
tool_call_required | true | Water utility revenue yield data must be pulled from multiple systems, so tool calls must be triggered to obtain real data; AI-generated content is prohibited |
max_context_tokens | 8000–12000 | Water utility data has complete fields, so sufficient context must be retained to avoid truncation of key report fields |
rag_recall_count | Top 6 | Associated documents for water utility daily reports are usually operational reports from the past 7 days. Recalling 6 entries covers all relevant data without redundancy |
form_field_unit_lock | Enabled | Standardized metrics are used for water utility data, so locking units prevents users from entering incorrect units |
date_picker_default_range | Yesterday to Yesterday | The daily report scenario loads the previous day's full data by default, which aligns with business usage habits |
tool_call_timeout | 30 seconds | Water utility data must be synchronized from multiple internal systems; 30 seconds covers most synchronization scenarios and avoids timeout failures |
The parameter values given on this page are all conventional recommendations used to determine the starting point for configuration. Actual values are affected by material form, data volume and business rules. Specific issues require specific analysis. It is recommended to test on your own samples before finalizing.
Three common mistakes
- Phenomenon: A
400 Bad Requesterror is returned when calling theget_water_income_reporttool, and the AI generates content directly without triggering the tool. Cause:tool_call_requiredis not configured astrue, allowing the AI to choose whether to call the tool independently. - Phenomenon: When setting
rag_recall_count, only fixed options can be selected, and custom numerical input is not allowed. Cause: The configuration switch for custom recall count is not enabled, and the system only provides preset fixed options. - Phenomenon: When configuring string matching rules, selecting "equals" or "starts with" triggers the ELSE branch, while selecting "contains" or "ends with" triggers the IF branch. Cause: The judgment logic does not match the field format of water utility structured data. Most water utility revenue yield fields are standardized numerical values, so the "equals" rule should be used, and fuzzy matching should not be applied.
How to confirm the configuration is complete
- Trigger a tool call test, check if the preset water utility data pulling tool is automatically called, and no content is generated directly, to confirm that the
tool_call_requiredconfiguration is effective. - Open the form configuration page, check if the units of each data field are preset fixed values, to confirm that the
form_field_unit_lockconfiguration is enabled. - Select the date picker control, check if the default loaded date range is the previous day, to confirm that the
date_picker_default_rangeconfiguration is correct. - Adjust the recall count input box, check if any positive integer can be entered instead of using fixed options, to confirm that the custom recall configuration is enabled.
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.