Change Request Q
Change Request Q
1. Background:
The current system lacks a process for charging MDI (Maximum Demand Indicator) penalties on
DS (Domestic Supply) and NDS (Non-Domestic Supply) connections when their MDI exceeds
110% of the sanctioned load. This CR aims to develop a systematic approach to identify, flag,
and charge MDI penalties under the specified conditions.
2. Description of Change:
Objective:
o Implement a process to charge MDI penalties on DS & NDS connections if their
MDI exceeds 110% of the sanctioned load.
Scope:
o The new process will apply to:
DS connections where the previous three bills are generated on MMC
(Minimum Monthly Charge) and MDI exceeds more than 110% of the
sanctioned load.
NDS connections where MDI exceeds 110% of the sanctioned load.
3. Detailed Requirements:
Functional Requirements:
1. Identification and Flagging:
Implement a mechanism to identify and flag DS & NDS connections
where MDI exceeds 110% of the sanctioned load.
For DS connections, ensure the system verifies that the previous three bills
are generated on MMC.
2. Notification Process:
Develop a process for the sub-division staff to issue formal notices to
consumers whose MDI exceeds the threshold.
3. Auto-Extension Option:
Provide an option for consumers to participate in the auto-extension of the
sanctioned load process.
4. Charging ACD Amount:
Charge the ACD (Additional Consumption Deposit) amount in the
subsequent energy bill for consumers who have not extended the load
themselves.
4. Impact Analysis:
System Impact:
o Changes will affect the billing system, notification system, and customer service
processes.
User Impact:
o Training will be required for sub-division staff on the new processes.
o Consumers will receive notifications and may need to extend their sanctioned
load.
5. Implementation Plan:
Development Phase:
o Duration: 2 months
o Activities: Requirement gathering, design, coding, and initial testing.
Testing Phase:
o Duration: 1 month
o Activities: Comprehensive testing, including unit, integration, and user
acceptance testing.
Deployment Phase:
o Duration: 2 weeks
o Activities: Deployment to the live environment and post-deployment support.
6. Approval:
Requested By:
o Name: [Your Name]
o Position: [Your Position]
o Date: [Today's Date]
Approved By:
o Name: [Approving Authority]
o Position: [Their Position]
o Date: [Approval Date]