Workflow, Approval And Escalation Requirement In CCB
(Doc ID 1344552.1)
Last updated on SEPTEMBER 14, 2022
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.3.0.0.0 and laterInformation in this document applies to any platform.
Goal
We need to implement the Workflow, Approval and Escalation process in different modules like Case Management, Billing, Payment and Metering.
Workflow:
a) Org structure of UPPCL cannot be mapped in CCB.
Org Stracture Hierachy
1) SDO
2) EE
3) Senior Engineer
4) Chief Engineer
5) MD
6) CEO
b) System generated To Do entry cannot be targeted to selected users in a particular To Do role based on the data access group
Escalation and Approval -- Example from Case Requirement
- After X days from the Case registered if the status has not been performed then escalate to particular (selected by system) SDO (Sub Divisional Officer) in the particular DISCOM (DISCOM is alias of CISDIVISION). APDRP - UPPCL project will have four CISDIVISION.
- After ( X+a ) days if no action has been performed then escalate to particule EE (Officer) in the particular (selected by system)DISCOM (DISCOM is alias of CISDIVISION). APDRP - UPPCL project will have four CISDIVISION.
- After ( X+a+b ) days if no action has been performed then escalate to particular (selected by system) SE (Senior Engineer Officer) in the particular DISCOM (DISCOM is alias of CISDIVISION). APDRP - UPPCL project will have four CISDIVISION.
- After ( X+a+b+c ) days if no action has been performed then escalate to particular (selected by system) Chief Engineer (Chief Engineer Officer) in the particular DISCOM (DISCOM is alias of CISDIVISION). APDRP - UPPCL project will have four CISDIVISION.
- After ( X+a+b+c+d ) days if no action has been performed then escalate to particular (selected by system) MD in the particular DISCOM (DISCOM is alias of CISDIVISION). APDRP - UPPCL project will have four CISDIVISION.
- After ( X+a+b+c+d+e ) days if no action has been performed then escalate to particular (selected by system) CEO in the particular DISCOM (DISCOM is alias of CISDIVISION). APDRP - UPPCL project will have four CISDIVISION.
For Payment Approval Requirement
For Payment installment Approval (where payment is done in multiple installments)
For all the installment Approval X% of amount needed to be paid by the consumer as down payment.
1) If number of installments = 2
a) SDO (User in CC&B , Sub Divisional Officer ) will review then send for next level of approval to EE (Other User in CC&B Executive Engineer)
2) If number of installments = 3
a) SDO (User in CC&B , Sub Divisional Officer ) will review then send for next level of approval
to EE (Other User in CC&B Executive Engineer)
b) EE will approve and send to next level to Senior Engineer.
3) If number of installments = 4
a) SDO (User in CC&B , Sub Divisional Officer ) will review then send for next level of approval
to EE (Other User in CC&B Executive Engineer)
b) EE will approve and send to next level to Senior Engineer.
c) SE will approve and send to next level to Chief Engineer.
Following is stracture
SNO | Module | Activity | Role | Authorization/Approvals |
---|---|---|---|---|
SDO | ||||
1 | Collection | Installment | EE (Executive Engg.) | For 2 Installments |
2 | Collection | Installment | SE (Superintendent Engg.) | For 3 installments |
3 | Collection | Installment | CE (Chief Engg.) | For 4 and aboveinstallments |
Billable charge approval requirement:
WAM transfers line charges (infrastructure cost for new connection or service augmentation) to CCB. The line charges must be approved or rejected (can be multi-level) by authorized users, before these can be used in billing.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |