> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/public-finance/v2.3/exemplar/mgramseva/features/bulk-demand-generation-for-non-metered.md). # Bulk Demand Generation for Non Metered Bulk Demand would be generated in 2 methods - 1. Auto (scheduler based) 2. Manual **Auto**: The demand is generated at end of the month or the first day of next month or as scheduled for the recently completed billing cycle. Use cases are as below - 1. **First demand generated in system**: The demand is generated for the recently completed billing cycle considering the arrears in the master data. The arrears are tagged to the previous billing cycle of the current demand. 2. **Consecutive demands**: The demand is generated for all the months pending from the most recent to the last billing cycle completed. 3. The demand is generated for the recently completed billing cycle. **Manual**: The demand is generated for the billing cycle that is selected by the user. If the demand is already generated, then the demand would be generated only for those consumers for whom demand does not exist for the selected month. 1. **First demand generated in the system**: The demand would be generated for the selected billing cycle. considering the arrears in the master data. The arrears would be tagged to the previous billing cycle of the current demand. 2. **Consecutive demand**: The demand for the selected month is generated only if the previous billing cycle demand exists. If the demand for the previous cycle does not exist, it gives an error message “Demand generation is pending from billing cycle - \. please generate demand from this cycle in sequence”. This validation is done considering the most recent billing cycle that exists in the system. **Charges/Heads and Calculation Logic** As part of V1, only the water charges head is only the head that is applicable. Rate Master is defined at the GPWSC level. **Water Charges** - Charges are applicable as defined in the Rate Masters based on - Validity, Property Type, Service Type where calculation type is **“Per Bill Cycle”** for the given billing period. **Bill Period** - The billing periods are monthly as standard across GPWSC. In future, GPWSC may switch to bi-monthly to reduce the processing effort. The sample billing period data is given in the MDMS data. **Exclusion** * Reversion of Demand is not allowed. This has to be done in the backend. * Exception reporting for every batch processing should be accessed from the backend only. > [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)*​*](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digit.org/public-finance/v2.3/exemplar/mgramseva/features/bulk-demand-generation-for-non-metered.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.