WO2017115341A1

WO2017115341A1 - Method and system for utility management

Info

Publication number: WO2017115341A1
Application number: PCT/IB2016/058129
Authority: WO
Inventors: Niranjan Reddy PARVATHA; Sudheer POLAVARAPU
Original assignee: Fluentgrid Limited
Priority date: 2015-12-31
Filing date: 2016-12-31
Publication date: 2017-07-06

Abstract

The present disclosure discloses a method and a system for utility management. In one embodiment, the data from one or more utility related processes is collected and analyzed to generate a plurality of exceptions and determine one or more actionable workflow activities based on the analysis. The actionable workflow activities thus determined are monitored for closure using a mobile workforce management system and the performance efficiency of the utility management system is determined associated with the closure of the workflow activities by the mobile workforce management system. The present disclosure thus provides a solution to closed-loop utility management primarily meant for plugging leakages and maximizing operational realization of electricity/water/gas and other such utilities by analyzing the anomalies or exceptions cropping up in the life line commercial functions of the utilities viz. metering, billing, collection and accounting functions.

Description

METHOD AND SYSTEM FOR UTILITY MANAGEMENT FIELD OF THE DISCLOSURE the present subject matter is related, in general to utility management, and more particularly, but not exclusively to a method and system for enabling utility management improving the performance of the utility systems. BACKGROUND

Electricity, water, gas and other such utilities around the world are in dire straits today. Their ageing infrastructure begs for modernization, their informed customers are demanding better service but they don't have the resources like money and manpower to address any of these initiatives. Metering, billing, collection and accounting are the key related business processes of a utility whose wellbeing is critical to the health of the utility. However, many discrepancies creep-up in these business processes either because of inadequacy of systems and management or through deliberate fraud. Such discrepancies or anomalies are generally called as exceptions in utility parlance. There are hundreds of such exception types, each of which requires a different method of dealing with.

Utility executives generally prepare a list of such exceptions and pass on to concerned staff for resolution. But, even the highly process oriented utilities rarely close all the exceptions as expected, within time and report back. This creates an environment where exceptions are the norm and accountability takes a back seat. Finally, the utilities continue to suffer from low or negative cash flows knowing fully well that commercial losses are something that can be brought down, with some serious effort. Many utilities do not learn from experience as they do not have a formal knowledge base to record new and innovative means of fraud. They also do not keep up with the times unlike fraudsters who continue to innovate new means of tricking the utility for personal gain. Hence, the utilities keep churning out a standard set of exceptions for which fraudsters had already found alternatives and those new types of fraud and exceptions go unnoticed resulting in performance and loss, and generally brushed aside by the utilities as technical losses. Some of the utilities have thoroughly defined processes for acting on each type of exceptions. But most of them do not have workflow management systems to satisfactorily take these exceptions through the pre-defined flow until closure. Hence, many exceptions take months or years to close, affecting the operation and performance in the utility. Even in those places, where these workflow systems exist, they usually fail because of the inherent rigidity of the traditional workflow systems. If a certain exception demands an alternative midway course change, it is just not possible in these kinds of systems. This rigidity becomes a hindrance and the entire system is usually abandoned after some time.

Field personnel of a utility are the key to investigating the exceptions and taking necessary action. Often, there is no dedicated field staff to handle exceptions. So, exception handling becomes an additional burden on these people who may not take it very seriously. In addition, collusion of field men and the consumers makes it even more difficult to utility to arrest performance leakage. An additional layer of supervision will only add to administrative overheads without any real benefit.

Therefore, there is a need for a method and a system for enabling utility management, performing intelligent analysis, dynamic workflow management, mobile field service management and the system performance management addressing the existing drawbacks and improve the general health of utilities around the world.

SUMMARY

One or more shortcomings of the prior art are overcome and additional advantages are provided through the present disclosure. Additional features and advantages are realized through the techniques of the present disclosure. Other embodiments and aspects of the disclosure are described in detail herein and are considered a part of the claimed disclosure.

Accordingly, the present disclosure relates to a method of enabling utility management. In one embodiment, the method comprising steps of receiving utility service data collected from a plurality of utility systems coupled with the UMS and generating a plurality of exceptions based on the received utility service data. In one embodiment, the plurality of exceptions includes at least technical and non-technical loss related data associated with the plurality of utility systems. The method further comprising steps of determining a plurality of actionable work items, corresponding to the plurality of generated exceptions, associated with the plurality of utility systems and receiving feedback data in response to execution of the plurality of actionable work items. Based on the received feedback data, the method determines a performance score of the utility management system.

Further, the present disclosure relates to a utility management system. The system comprises at least a processor and a memory communicatively coupled with the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to receive utility service data collected from a plurality of utility systems coupled with the UMS. Further, the processor is configured to generate a plurality of exceptions based on the received utility service data and determine a plurality of actionable work items corresponding to the plurality of generated exceptions, associated with the plurality of utility systems. In one embodiment, the plurality of exceptions includes at least technical and non-technical loss related data associated with the plurality of utility systems. Furthermore, the processor is configured to receive feedback data in response to execution of the plurality of actionable work items and determine a performance score of the utility management system based on the received feedback data.

The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed embodiments. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and with reference to the accompanying figures, in which: Figure 1 illustrates an exemplary architecture of a system that enables utility management in accordance with some embodiment of the present disclosure;

Figure 2 illustrates an exemplary block diagram of utility management system of Figure 1 in accordance with an embodiment of the present disclosure;

Figure 3 illustrates an exemplary flowchart showing a method for enabling utility management in accordance with an embodiment of the present disclosure; and

Figure 4 is a block diagram of an exemplary computer system for implementing embodiments consistent with the present disclosure.

It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.

DETAILED DESCRIPTION

In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the spirit and the scope of the disclosure.

The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by "comprises... a" does not, without more constraints, preclude the existence of other elements or additional elements in the system or apparatus.

The present disclosure discloses a method and a system for utility management. In one embodiment, the data from one or more utility related processes is collected and analyzed to generate a plurality of exceptions and determine one or more actionable workflow activities based on the analysis. The actionable workflow activities thus determined are monitored for closure using a workforce management system and the performance efficiency of the utility management system is determined associated with the closure of the workflow activities by the mobile workforce management system. The present disclosure thus provides a solution to closed-loop utility management primarily meant for plugging performance leakages and maximizing ease of operational realization of electricity/water/gas and other such utilities by analyzing the anomalies or exceptions cropping up in the life line commercial functions of the utilities viz. metering, billing, collection and accounting functions.

In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

Figure 1 illustrates an architecture diagram of an exemplary system for utility management system in accordance with some embodiments of the present disclosure. As shown in Figure 1, the exemplary system 100 comprises one or more components configured for utility management system. In one embodiment, the exemplary system 100 comprises a utility management system 102 (hereinafter referred to as UMS 102), a utility data repository (interchangeably referred to as utility base) 104, and one or more field force 106-1, 106-2, ... 106-N (collectively referred to as field force 106) using one or more user devices 107-1, 107-2, .. 107-N (collectively referred to as user device 107) connected via a communication network 108. The network 108 can be a LAN (local area network), WAN (wide area network), wireless network, point-to-point network, or other configuration. One of the most common types of network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network for communication between database client and database server. Other common Internet protocols used for such communication include HTTPS, FTP, AFS, and WAP and using secure communication protocols etc.

In one embodiment, the UMS 102 is configured to enable utility management improving the performance and efficiency. In one aspect, the UMS 102 receives utility service data as input from multiple sources. The utility service data may include, for example energy audit data, metering data, billing data, collections data, home-entity profile, peer group consumption data, distribution utility system's distribution hierarchy data, data from other utilities and external data such as weather, demographic data and economic indicators. The UMS 102 assess exceptions or anomalies by comparing the received utility service data with the historical utility service data 122 recorded in the utility base 104, generates actionable work items and, tracks the work items to closure, and estimates the performance of the system. In one example, the UMS 102 may be configured as a standalone system. In another example, the UMS 102 may be configured in cloud environment. In yet another example, the UMS 102 may include a desktop personal computer, workstation, laptop, PDA, cell phone, or any WAP-enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection. The UMS 102 typically includes one or more user interface devices, such as a keyboard, a mouse, touch screen, pen or the like, for interacting with the GUI provided on a display. The UMS 102 also includes a graphical user interface (GUI) provided therein for interacting with the utility base 104 to access data and to perform utility management processes. The UMS 102 comprises one or more components coupled with each other that may be deployed on a single system or on different systems. The UMS 102 may also be configured in Service Oriented Architecture (SOA) based architecture model, where the UMS 102 will be implemented and accessed through one or more of Application Programming Interface (API), Web Services, Representational State Transfer (RESTful) services or any other equivalent technology. In one embodiment, the UMS 102 comprises a central processing unit ("CPU" or "processor") 110, a memory 112, an Actilligence processing module (APM) 116, a Dynamic Case Manger (DCM) 118, a Workflow Manager (WM) 118 and a user interface module (UIM) 120. The UMS 102 is configured to determine exceptions/anomalies based on historical utility service data 122 and real time utility service data 124 previously stored in the utility base 104. In one example, the historical utility service data 122 comprises anomalies/exceptions, work items and performance data associated with the field force 106 and the UMS 102 recorded in the past and the real time utility service data 124 comprises anomalies/exceptions, work items and performance data associated with the field force 106 and the UMS 102 captured in real time.

As illustrated in Figure 2, the UMS 102 may be a typical utility management system. In one embodiment, the UMS 102 comprises the processor 110, the memory 112 and an I/O interface 202. The I/O interface 202 is coupled with the processor 110 and an I/O device. The I/O device is configured to receive inputs via the I/O interface 202 and transmit outputs for displaying in the I/O device via the I/O interface 202.

The UMS 102 further comprises data 204 and modules 206. In one implementation, the data 204 and the modules 206 may be stored within the memory 112. In one example, the data 204 may include utility service data 208, a plurality of exceptions/anomalies 210, one or more actionable work items 212, field force data 214, field force reports 216 and other data 218. In one embodiment, the data 204 may be stored in the memory 112 in the form of various data structures. Additionally, the aforementioned data can be organized using data models, such as relational or hierarchical data models. The other data 218 may be also referred to as reference repository for storing recommended implementation approaches as reference data. The other data 218 may also store data, including temporary data and temporary files, generated by the modules 206 for performing the various functions of the UMS 102. The modules 206 may include, for example, the APM 116, the DCM 116, the WM 118, the UIM 120, a gamification manager 220, a field incident manager (FIM) 222, a performance manager 224 and an integration manager 226. The modules 206 may also comprise other modules 228 to perform various miscellaneous functionalities of the UMS 102. It will be appreciated that such aforementioned modules may be represented as a single module or a combination of different modules. The modules 206 may be implemented in the form of software, hardware and or firmware. In operation, the UMS 102 receives the utility service data 208 as input from one or more data sources for example, Customer Information System (CIS) or Customer Relationship Management System (CRM), Advanced Metering Infrastructure (AMI), Energy Audit reports generated or published during the course of a utility company performance or audit and so on. Other examples of the utility service data 208 include information like application forms submitted by customers, written compliments either in electronic form or on paper, data collected by field person or any employee of the company while servicing the customers, environmental data like weather, demographic or the data which can affect the price, consumption, production and usage of the utility company. For example, in case of hand written application forms/complaints on paper, the utility service data 208 are extracted by scanning these documents and converting them to free flow text documents.

In one embodiment, the utility service data 208 comprises at least energy audit data, metering data, billing data, collections data, home-entity profile, peer group consumption data, utility system's distribution hierarchy data and external data comprising weather conditions, geographical data, and other related data. Utility system's distribution hierarchy data comprises meter data mapped with location or premise information, transformers, substations, regions and so on. The other related data include seasonal holiday and public events data and data from other utilities and entities. In one example, the utility service data 208 is extracted from the one or more sources by means of a utility service bus or Application Programming Interface (API). The utility service bus or API stores the extracted utility service data 208 as real time utility service data 124 in the utility base 104 using transferring methodologies such as web service, remote procedure call (RPC), API call, or RESTful services known in the art. During the transferring process of the utility service data 208, the UMS 102 performs Extract, Transform and Load (ETL) processes the extracted utility service data 208 to transform the unstructured data format to a corresponding structured format for loading onto the utility base 104 as real time utility service data 124.

The utility base 104 is configured to store historical utility data that has undergone ETL processes as well as the real time ETL processed utility data. In one example, the utility base 104 may be configured to store relational data, structured data, un-structured data by using tools/products such as for example, SQL Server, Oracle, MySQL, HBase, MongoDB, Cassandra, Redis. The utility base 104 stores the utility Data in mega/Giga bytes in size or could be in Tera bytes and require big data technologies such as Hadoop, HBase to process/store therein. Based on the processed utility service data 208, the UMS 102 is configured to determine the plurality of exceptions/anomalies 210.

In one embodiment, the APM 114 is configured to receive the processed utility service data 208 and determine the plurality of exceptions/anomalies 210 in real time using machine learning techniques and components that can process, analyze relational, structured and unstructured data, and find out hidden patterns, anomalies that are causing performance degradation to the utility company. Anomalies can be categorized as technical-loss, nontechnical loss and commercial loss. Anomalies may be different causes/cases/reasons/forms of loss categories identified and approximate value of loss for each category of case/cause/reason/form. In one example, the anomalies may be customer contract was expired long back and the customer was charged with less energy rates, loss due customer contract was opted for one usage plan/capacity, loss during billing the customer was charged less/ or the caution deposit collected from the customer is not following under customer usage plan, loss caused due to time it took to replace the burned meter in customer premises, loss caused by utility company demand/forecast system. The demand/forecast system predicted the demand/forecast accurately, and determines how much amount the utility company might save if they placed purchase order before/after demand/forecast system predictions. In one example, the APM 114 comprises components such as Unsupervised component, Supervised component, Reinforcement Learning component and Pattern recognition tool and Utility Rules component. The unsupervised component has set of unsupervised machine learning techniques to identify/cluster the customers/users based on usage, registered load profiles, income groups, payment methodologies, defaulter behaviors and amount of loss the utility company is experiencing in each such category of the cluster/user base. This will enable the utility company to adopt different policies/procedure to cease the loss. The unsupervised component further comprises one or more machine learning techniques like K-means clustering, Hierarchical clustering, Self-Organizing Maps (SOM) and other machine learning techniques which can be used for unsupervised clustering. The supervised component comprises a plurality of machine learning techniques like regression, Support Vector Machine (SVM), k-nearest neighbor (KNN) methodologies to predict the loss. The reinforcement learning component comprises a plurality of methodologies that will consider the exceptions/anomalies, predictions/estimates of the previous execution, actionable work items generated by the system, field incidents report submitted by the field force and improves prediction of the next run. By improving the prediction, the accuracy of the APM 114 also improves thereby increasing the effectiveness of the UMS 102.

The Pattern Recognition tool, for example, is configured to identify an anomaly/exception pattern and predict loss experienced due to existence of the anomaly/exception pattern. For example, one set of utility meters fail after servicing 24 months and the utility company is taking three days to identify the meter failure and replace the meter with new one. The pattern recognition tool/component is configured to identify such kind of anomaly/exception patterns in the data, calculate the loss incurred to the utility company due to the meter failure and predict or estimate the meters that might fail in next few days & predict losses that may be incurred due to such failure. The utility rules component is configured to provide the utility companies any set of rules that they can define and identify as part of UMS 102. Upon determining the plurality of exceptions or anomalies 210, the UMS 102 generates one or more actionable work items 212 that can be implemented to reduce/minimize the performance degradation to the utility company.

In one embodiment, the DCM 116 is configured to identify the one or more actionable work items 212 and work flow to be followed to implement the actionable work items 212. For example, the plurality of actionable work items 212 comprises at least workflow and category information, Value number, Service Level Agreement (SLA) number, approximate time to complete the work item, potential loss information, field force skills required to complete the work item, preparatory actions required and task data including consumer information, asset information, utility system's distribution hierarchy data, peer group details, asset location co-ordinates, and other related information. The Value number may be derived from for example, potential loss, type of customer including domestic, commercial and industrial type of users, and accuracy of analysis based on previous hit ratio. The hit ratio is defined as ratio of anomalies or exceptions successfully completed as actionable work items to the total number of anomalies or exceptions identified. The DCM 116 compares the plurality of exceptions/anomalies thus determined by the APM 114 with the previously stored historical anomaly patterns/exceptions 124 and identifies actionable work items 212 based on the comparison. The DCM 116 identifies the one or more actionable work items 212 corresponding to the plurality of exceptions/anomalies that are mapping with the historical anomaly patterns/exceptions 124 and stores in the utility base 104. Upon identifying the one or more actionable work items 212, the UMS 102 assigns the one or more identified actionable work items 212 to work force or field force 106 for implementation.

In one embodiment, the WM 118 is configured to identify the field force 106 for implementing the one or more identified actionable work items 212 at the customer location. The WM 118 identifies the field force 106 to be assigned to perform the one or more identified actionable work items 212 based on the field force data 214. In one example, the field force data 214 comprises for example, at least current location coordinates of the field force 106, proximity score of the service location, asset replacement requirement, route information and real time traffic information, availability information of the field force 106, relevant technical skill information associated with the field force 106. The field force data 214 may also comprise business calendar of the field force 106, skill mapping and the availability information of the field force 106. Proximity score of the service location defines distance indicating how nearer is the field force to the service location where a new actionable work item is to be carried out. The WM 118 allocates the one or more actionable work items 212 to the identified field force 106 based on the field force data 214 and the Value number assigned to the one or more actionable work items 212. Resources like for example, meters, pipes, cables, mobiles, wearable devices, field force equipment, or any other devices or equipment that is required or helpful to close the one or more actionable work item 212 is determined and allocated to the field force 106. Transport requirements include vehicle, route map, etc. Documents like technical documents/utility company process documents/other documents customer needs to fill/sign are also provided. The WM 118 is further configured to identify optimal routing that the field force 106 will implement and optimal assignment of one or more actionable work items 212 to the field force 106 using routing and machine learning techniques. In another embodiment, the WM 118 may also determine average time required by the field force 106 to complete the ongoing assigned actionable work item 212 and dynamically assign the field force 106 with another actionable work item 212. In one embodiment, the field force 106 dynamically assigns the field force 106 based on status of the each of the ongoing one or more actionable work items 212 that are in progress, corresponding average time required to complete, and proximity score of the service location of another plurality of actionable work items 212. Upon completing the one or more actionable work items 212, the FIM 222 generates the field force analysis reports 216 based on one or more evidences or field force reports 216 recorded and uploaded by the field force 106 via the UIM 120. In one aspect, the evidences or field force reports 216 recorded may also be interchangeably referred to as feedback data. In one embodiment, the UIM 120 may be implemented as application downloaded on a mobile or WAP enabled device, for example, capable of tracking/recording the route the field force 106 used to reach the customer location, the location where the field force 102 updates status information of the one or more actionable work items 212 thus assigned. The status information may indicate one of closed, open, cancelled information associated with the one or more actionable work item allotted to the field force 106. In another embodiment, the field force 106 may also capture one or more images associated with the plurality of exceptions or anomalies at the customer location using an imaging sensor coupled with the UIM 120.

The UIM 120 receives the one or more images or field force reports or feedback data 216 captured by the user device 107 such as a mobile device used by the field force 106 and stores in the utility base 104. In another example, the UIM 120 may be implemented as application downloaded on wearable devices like Google ® glass associated with the field force 106 to enable recording of any evidences that might help/required to the utility company to file a judicial complaint. In one embodiment, the feedback data comprises at least status of the plurality of actionable work items 212, field force action data associated with the plurality of actionable work items 212, availability data, one or more unpredicted exceptions, and the Global Positioning System (GPS) location co-ordinates of the one or more field force recording the consumption field force action data. The UIM 120 also updates a field force performance number associated with the plurality of actionable work item 212 based on the received feedback data 216 and corresponding SLA number. In one example, the field force performance number is a representation or indicator of success rate of the field force 106 in completing the plurality of assigned actionable work items 212.

Based on the one or more evidences or field force reports 216 recorded and uploaded in the UIM 120 by the field force 106, the FIM 222 generates analysis reports and identifies any disturbances/gaps/mistakes performed by the field force 106. The analysis could be for example, whether the field force 106 updated the actionable work item information at the desired customer location, the one or more images has been captured at the customer location, the data updated by the field force 106 is valid or invalid. In one embodiment, the FIM 222 determines the GPS location co-ordinates of the field force 106 recording the field force action data from the received feedback data 216 and compares the GPS location co- ordinates with the asset location co-ordinates associated with the corresponding actionable work item assigned to the field force. Based on the comparison, the FIM 222 optionally generates one or more actionable work items 212 on the field force 106 if there are any gaps/mistakes in the performance of the field force 106.

Based on the analysis reports, the integration manager 226 of the UMS 102 integrates with existing utility systems to read and update data back into the systems. For example, if the analysis reports indicate closure of one or more actionable work items, then the integration manager 226 reads and updates the corresponding customer's data in the existing utility systems to reflect the correction of the anomaly detected at the customer's location. Upon generating the analysis reports, the UMS 102 allocates grades or ranks or performance score to each of the field force 106 involved in restricting the leakage based on the analysis reports thus generated.

In one embodiment, the gamification manager 220 determines the ranks or grades or performance score associated with the field force 106 based on the field incident reports 216 that indicate the performance of the field force 106 towards the allotted actionable work items 212. In one example, the gamification manager 220 determines rank of each of the field force 106 based on average time required to execute the plurality of actionable work items 212 assigned to each field force 106 and the field force performance number updated based on the received feedback data 216. Further, the gamification manager 220 publish the analysis reports and the ranks or grades or performance score in social enterprise platform under one or more categories like saving, honesty, transparency and dependability to improve the competitiveness within the employees/staff, based on the ranks/grades. Further, the performance of the UMS 102 is determined.

In one embodiment, the performance manager 224 is configured to determine performance of the UMS 102 based on determination of effectiveness and efficiency associated with the UMS 102. The performance manager 224 determines the effectiveness of the UMS 102 based on an effectiveness score. The effectiveness score is determined based on an accuracy score associated with identifying the plurality of exception/anomalies 210, a correctness score related with mapping of the plurality of identified exception/anomalies 210 into corresponding one or more actionable work items 212, an assignment score associated with accuracy of recommendations made towards one or more actionable work item 212 assignment and quicker closure, and the performance score of the field force 106 to close the work items.

Further, the performance manager 224 determines the efficiency of the UMS 102 based on an efficiency score. The efficiency score is determined based on value number associated with each actionable work item 212 assigned to the field force 106 and value number associated with each actionable work item 212 completed by the one or more assigned field force 106. Based on the effectiveness score and the efficiency score thus determined, the performance of the UMS 102 is determined by the performance manager 224. The performance manager 224 also dynamically updates the hit ratio based on conversion of anomalies / exceptions 210 into or generation of the plurality of actionable work items 212 and successful completion of the plurality of actionable work items 212.

In one embodiment, the performance manager 224 compares the effectiveness score and the efficiency score of the UMS 102 with a predetermined threshold effectiveness score and a predetermined threshold efficiency score respectively. Based on the comparison, the performance of the UMS 102 is determined. The threshold effectiveness score and the predetermined threshold efficiency score are predetermined and stored in the utility base 104. In another embodiment, the performance manager 224 compares the effectiveness score and the efficiency score of the UMS 102 with a historical effectiveness score and the efficiency score determined in the past and stored in the utility base 104. Thus, the UMS 102 therefore enables utility companies to automatically identify the causes of loss and estimates of possible loss, identify the un-seen, underneath customers who are not properly metered/billed and identify actionable work items and define a process to track all the actionable work items to closure and further to identify how much time it is taking to complete each actionable work item and any improvements required to for long taking actionable work items. Hence, the UMS 102 enables utility companies to automatically identify the anomalies, determine suitable actionable work items and define a process to track all the actionable work items to closure thereby improving the utility process management

Figure 3 illustrates a flowchart of a method of enabling utility management in accordance with some embodiments of the present disclosure.

As illustrated in Figure 3, the method 300 comprises one or more blocks implemented by the processor 110 for utility management. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method 300 can be implemented in any suitable hardware, software, firmware, or combination thereof.

At block 302, receive and pre-process utility service data. In one embodiment, UMS 102 receives the input utility data 208 from one or more sources for example, Customer Information System (CIS) or Customer Relationship Management System (CRM), Actionable Market Intelligence (AMI), Energy Audit reports generated or published during the course of a utility company performance or audit and so on. In one embodiment, the utility service data 208 comprises at least energy audit data, metering data, billing data, collections data, home-entity profile, peer group consumption data, utility system's distribution hierarchy data and external data comprising weather conditions, geographical data, and other related data. Utility system's distribution hierarchy data comprises meter data mapped with location or premise information, transformers, substations, regions and so on. The other related data include seasonal holiday and public events data and data from other utilities and entities. In one example, the utility service data 208 is extracted from the one or more sources by means of a utility service bus or Application Programming Interface (API). The utility service bus or API stores the extracted utility service data 208 as real time utility service data 124 in the utility base 104 using transferring methodologies such as web service, remote procedure call (RPC), API call, or RESTful services known in the art. During the transferring process of the utility service data 208, the UMS 102 performs Extract, Transform and Load (ETL) processes the extracted utility service data 208 to transform the unstructured data format to a suitable structured format for loading onto the utility base 104. Based on the received utility service data 208, the UMS 102 is configured to determine the plurality of exceptions/anomalies 210. At block 304, determine exceptions/anomalies. In one embodiment, the APM 114 is configured to receive the input utility data 208 and determine the plurality of exceptions/anomalies 210 in real time using machine learning techniques and components that can process, analyze relational, structured and unstructured data, and find out hidden patterns, anomalies that are causing loss to the utility company. Anomalies may be different causes/cases/reasons/forms of loss categories identified and approximate value of loss for each category of case/cause/reason/form. In one example, the anomalies may be customer contract was expired long back and the customer was charged with less energy rates, loss due customer contract was opted for one usage plan/capacity, loss during billing the customer was charged less/ or the caution deposit collected from the customer is not following under customer usage plan, loss caused due to time it took to replace the burned meter in customer premises, loss caused by utility company demand/forecast system. In one example, the APM 114 comprises components such as unsupervised component, supervised component, Reinforcement Learning component and Pattern recognition tool and Utility Rules component to determine the plurality of exceptions or anomalies 210. Upon determining the plurality of exceptions or anomalies 210, the UMS 102 generates one or more actionable work items 212 that can be implemented to reduce/minimize the loss to the utility company.

At block 306, generate actionable work items and assign to workforce. In one embodiment, the DCM 116 is configured to identify the one or more actionable work items 212 and work flow to be followed to implement the actionable work items 212. For example, the plurality of actionable work items 212 comprises at least workflow and category information, Value number, Service Level Agreement (SLA) number, approximate time to complete the work item, potential loss information, field force skills required to complete the work item, preparatory actions required and task data including consumer information, asset information, utility system's distribution hierarchy data, peer group details, asset location co-ordinates, and other related information. The Value number may be derived from for example, potential loss, type of customer including domestic, commercial and industrial type of users, and accuracy of analysis based on previous hit ratio. The hit ratio is defined as ratio of anomalies or exceptions successfully completed as actionable work items to the total number of anomalies or exceptions identified. The DCM 116 compares the plurality of exceptions/anomalies thus determined by the APM 114 with the previously stored historical anomaly patterns/exceptions 124 and identifies actionable work items 212 based on the comparison. The DCM 116 identifies the one or more actionable work items 212 corresponding to the plurality of exceptions/anomalies that are mapping with the historical anomaly patterns/exceptions 124 and stores in the utility base 104. Upon identifying the one or more actionable work items 212, the UMS 102 assigns the one or more identified actionable work items 212 to work force or field force 106 for implementation. The WM 118 is configured to identify the field force 106 for implementing the one or more identified actionable work items 212 at the customer location. The WM 118 identifies the field force 106 to be assigned to perform the one or more identified actionable work items 212 based on the field force data 214. In one example, the field force data 214 comprises for example, at least current location coordinates of the field force 106, proximity score of the service location, asset replacement requirement, route information and real time traffic information, availability information of the field force 106, relevant technical skill information associated with the field force 106. The field force data 214 may also comprise business calendar of the field force 106, skill mapping and the availability information of the field force 106. The WM 118 allocates the one or more actionable work items 212 to the identified field force 106 based on the field force data 214 and the Value number assigned to the one or more actionable work items 212.

The WM 118 is further configured to identify optimal routing that the field force 106 will implement and optimal assignment of one or more actionable work items 212 to the field force 106 using routing and machine learning techniques. In another embodiment, the WM 118 may also determine average time required by the field force 106 to complete the ongoing assigned actionable work item 212 and dynamically assign the field force 106 with another actionable work item 212. In one embodiment, the field force 106 dynamically assigns the field force 106 based on status of the each of the ongoing one or more actionable work items 212 that are in progress, corresponding average time required to complete, and proximity score of the service location of another plurality of actionable work items 212. Upon completing the one or more actionable work items 212, the FIM 222 generates the field force analysis reports 216 based on one or more evidences or field force reports 216 recorded and uploaded by the field force 106 via the UIM 120.

At block 308, generate field analysis reports and evaluate performance of the field force. In one embodiment, UIM 120 may be implemented as application downloaded on a mobile or WAP enabled device, for example, capable of tracking/recording the route the field force 106 used to reach the customer location, the location where the field force 102 updates status information of the one or more actionable work items 212 thus assigned. In another embodiment, the field force 106 may also capture one or more images associated with the plurality of exceptions or anomalies at the customer location using an imaging sensor coupled with the UIM 120.

The UIM 120 receives the one or more images or field force reports or feedback data 216 captured by the user device 107 such as a mobile device used by the field force 106 and stores in the utility base 104. In one embodiment, the feedback data comprises at least status of the plurality of actionable work items 212, field force action data associated with the plurality of actionable work items 212, availability data, one or more unpredicted exceptions, and the Global Positioning System (GPS) location co-ordinates of the one or more field force recording the consumption field force action data. The UIM 120 also updates a field force performance associated with the plurality of actionable work item 212 based on the received feedback data 216 and corresponding SLA number. In one example, the field force performance number is a representation or indicator of success rate of the field force 106 in completing the plurality of assigned actionable work items 212. Based on the one or more evidences or field force reports 216 recorded and uploaded in the UIM 120 by the field force 106, the FIM 222 generates analysis reports and identifies any disturbances/gaps/mistakes performed by the field force 106. The analysis could be for example, whether the field force 106 updated the actionable work item information at the desired customer location, the one or more images has been captured at the customer location, the data updated by the field force 106 is valid or invalid. In one embodiment, the FIM 222 determines the GPS location co-ordinates of the field force 106 recording the field force action data from the received feedback data 216 and compares the GPS location coordinates with the asset location co-ordinates associated with the corresponding actionable work item assigned to the field force. Based on the comparison, the FIM 222 optionally generates one or more actionable work items 212 on the field force 106 if there are any gaps/mistakes in the performance of the field force 106.

Based on the analysis reports, the integration manager 226 of the UMS 102 integrates with existing utility systems to read and update data back into the systems. For example, if the analysis reports indicate closure of one or more actionable work items, then the integration manager 226 reads and updates the corresponding customer's data in the existing utility systems to reflect the correction of the anomaly detected at the customer's location. Upon generating the analysis reports, the UMS 102 allocates grades or ranks or performance score to each of the field force 106 involved in restricting the utility leakage based on the analysis reports thus generated. In one embodiment, the gamification manager 220 determines the ranks or grades or performance score associated with the field force 106 based on the field incident reports 216 that indicate the performance of the field force 106 towards the allotted actionable work items 212. In one example, the gamification manager 220 determines rank of each of the field force 106 based on average time required to execute the plurality of actionable work items 212 assigned to each field force 106 and the field force performance number updated based on the received feedback data 216. Further, the gamification manager 220 publish the analysis reports and the ranks or grades or performance score in social enterprise platform under one or more categories like saving, honesty, transparency and dependability to improve the competitiveness within the employees/staff, based on the ranks/grades, and help incentivize the field force 106.

At block 310, determine performance of the system. In one embodiment, the performance manager 224 is configured to determine performance of the UMS 102 based on determination of effectiveness and efficiency associated with the UMS 102. The performance manager 224 determines the effectiveness of the UMS 102 based on an effectiveness score. The effectiveness score is determined based on an accuracy score associated with identifying the plurality of exception/anomalies 210, a correctness score related with mapping of the plurality of identified exception/anomalies 210 into corresponding one or more actionable work items 212, an assignment score associated with accuracy of recommendations made towards one or more actionable work item 212 assignment and quicker closure, and the performance score of the field force 106 to close the work items.

In one embodiment, the performance manager 224 compares the effectiveness score and the efficiency score of the UMS 102 with a predetermined threshold effectiveness score and a predetermined threshold efficiency score respectively. Based on the comparison, the performance of the UMS 102 is determined. The threshold effectiveness score and the predetermined threshold efficiency score are predetermined and stored in the utility base 104. In another embodiment, the performance manager 224 compares the effectiveness score and the efficiency score of the UMS 102 with a historical effectiveness score and the efficiency score determined in the past and stored in the utility base 104.

The method 300 thus enables utility companies to automatically identify the anomalies, determine suitable actionable work items and define a process to track all the actionable work items to closure thereby improving the utility process management.

Variations of computer system 401 may be used for implementing all the computing systems that may be utilized to implement the features of the present disclosure. Computer system 401 may comprise a central processing unit ("CPU" or "processor") 402. The processor 402 may comprise at least one data processor for executing program components for executing user- or system-generated requests. The processor 402 may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc. The processor 402 may include a microprocessor, such as AMD Athlon, Duron or Opteron, ARM's application, embedded or secure processors, IBM PowerPC, Intel's Core, Itanium, Xeon, Celeron or other line of processors, etc. The processor 402 may be implemented using mainframe, distributed processor, multi-core, parallel, grid, or other architectures. Some embodiments may utilize embedded technologies like application-specific integrated circuits (ASICs), digital signal processors (DSPs), Field Programmable Gate Arrays (FPGAs), etc.

Processor 402 may be disposed in communication with one or more input/output (I/O) devices via I/O interface 403. The I/O interface 403 may employ communication protocols/methods such as, without limitation, audio, analog, digital, monoaural, RCA, stereo, IEEE- 1394, serial bus, universal serial bus (USB), infrared, PS/2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), RF antennas, S-Video, VGA, IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., code- division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMax, or the like), etc.

Using the I/O interface 403, the computer system 401 may communicate with one or more I/O devices. For example, the input device 404 may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, sensor (e.g., accelerometer, light sensor, GPS, gyroscope, proximity sensor, or the like), stylus, scanner, storage device, transceiver, video device/source, visors, etc. Output device 405 may be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light- emitting diode (LED), plasma, or the like), audio speaker, etc. In some embodiments, a transceiver 406 may be disposed in connection with the processor 402. The transceiver 406 may facilitate various types of wireless transmission or reception. For example, the transceiver may include an antenna operatively connected to a transceiver chip (e.g., Texas Instruments WiLink WL1283, Broadcom BCM4750IUB8, Infineon Technologies X-Gold 618-PMB9800, or the like), providing IEEE 802.11a/b/g/n, Bluetooth, FM, global positioning system (GPS), 2G/3G HSDPA/HSUPA communications, etc.

In some embodiments, the processor 402 may be disposed in communication with a communication network 408 via a network interface 407. The network interface 407 may communicate with the communication network 408. The network interface 407 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/40/400 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc. The communication network 408 may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc. Using the network interface 407 and the communication network 408, the computer system 401 may communicate with devices 409, 410, and 411. These devices 409, 410 and 411 may include, without limitation, personal computer(s), server(s), fax machines, printers, scanners, various mobile devices such as cellular telephones, smartphones (e.g., Apple iPhone, Blackberry, Android-based phones, etc.), tablet computers, eBook readers (Amazon Kindle, Nook, etc.), laptop computers, notebooks, gaming consoles (Microsoft Xbox, Nintendo DS, Sony PlayStation, etc.), or the like. In some embodiments, the computer system 401 may itself embody one or more of these devices.

In some embodiments, the processor 402 may be disposed in communication with one or more memory devices (e.g., RAM 413, ROM 4Error! Reference source not found.14, etc.) via a storage interface 412. The storage interface 412 may connect to memory devices including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as serial advanced technology attachment (SATA), integrated drive electronics (IDE), IEEE-1394, universal serial bus (USB), fiber channel, small computer systems interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, redundant array of independent discs (RAID), solid-state memory devices, solid-state drives, etc.

The memory 415 may store a collection of program or database components, including, without limitation, an operating system 4Error! Reference source not found.16, a user interface application 5Error! Reference source not found.17, a web browser 418, a mail server 419, a mail client 420, user/application data 421 (e.g., any data variables or data records discussed in this disclosure), etc. The operating system 416 may facilitate resource management and operation of the computer system 401. Examples of the operating system 416 include, without limitation, Apple Macintosh OS X, UNIX, Unix-like system distributions (e.g., Berkeley Software Distribution (BSD), FreeBSD, NetBSD, OpenBSD, etc.), Linux distributions (e.g., Red Hat, Ubuntu, Kubuntu, etc.), IBM OS/2, Microsoft Windows (XP, Vista/7/8, etc.), Apple iOS, Google Android, Blackberry OS, or the like. The user interface application 417 may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to the computer system 401, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc. Graphical user interfaces (GUIs) may be employed, including, without limitation, Apple Macintosh operating systems' Aqua, IBM OS/2, Microsoft Windows (e.g., Aero, Metro, etc.), Unix X-Windows, web interface libraries (e.g., ActiveX, Java, Javascript, AJAX, HTML, Adobe Flash, etc.), or the like. In some embodiments, the computer system 401 may implement a web browser 418 stored program component. The web browser 418 may be a hypertext viewing application, such as Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, Apple Safari, etc. Secure web browsing may be provided using HTTPS (secure hypertext transport protocol), secure sockets layer (SSL), Transport Layer Security (TLS), etc. The web browser 418 may utilize facilities such as AJAX, DHTML, Adobe Flash, JavaScript, Java, application programming interfaces (APIs), etc. In some embodiments, the computer system 401 may implement a mail server 419 stored program component. The mail server 419 may be an Internet mail server such as Microsoft Exchange, or the like. The mail server 419 may utilize facilities such as ASP, ActiveX, ANSI C++/C#, Microsoft .NET, CGI scripts, Java, JavaScript, PERL, PHP, Python, WebObjects, etc. The mail server 419 may utilize communication protocols such as internet message access protocol (IMAP), messaging application programming interface (MAPI), Microsoft Exchange, post office protocol (POP), simple mail transfer protocol (SMTP), or the like. In some embodiments, the computer system 401 may implement a mail client 420 stored program component. The mail client 420 may be a mail viewing application, such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Mozilla Thunderbird, etc.

In some embodiments, computer system 401 may store user/application data 421, such as the data, variables, records, etc. as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle or Sybase. Alternatively, such databases may be implemented using standardized data structures, such as an array, hash, linked list, struct, structured text file (e.g., XML), table, or as object-oriented databases (e.g., using ObjectStore, Poet, Zope, etc.). Such databases may be consolidated or distributed, sometimes among the various computer systems discussed above in this disclosure. It is to be understood that the structure and operation of the any computer or database component may be combined, consolidated, or distributed in any working combination.

ADVANTAGES

• Disclosed method and system enables efficient utility management processes and improving performance of the utility management system. · Further the disclosure serves as an invaluable tool for performance monitoring of the meter readers and Utility staff as well.

• The disclosed method and system also contributes in increasing the productivity of Utility employees as it becomes quite possible as they no longer require to inspect door to door to trace the trouble spots for plugging leakages, and they can straight away undertake focused and targeted inspections for booking the cases of malpractice or meter defect abnormalities etc. The time thus saved can be utilized in a proactive manner for other important tasks such as preventive maintenance to minimize break downs and supply interruptions, etc.

• Promptly paying consumers get encouraged as disclosed method and system automatically closes the doors and help in bringing the unscrupulous elements to books who otherwise become burden to the sincerely paying consumers.

• With the turnaround potential of the UMS, Utilities become healthier and would have enough resources to provide good quality uninterrupted power supply to its consumers at a lower rate and avoids the society from suffering power cuts, increasing tariffs and reducing power quality.

• The customers receive certain important consumption related data such as Historical, per capita consumption of the neighborhood, consumption not matching the connected load etc. through Consumer energy portal (CEP) in the disclosed method and system.

· By knowing the consumption trends, comparative analysis made available such as specific consumption within the same categories, same geography or of the same transformer etc. the consumers get inspired to regulate their consumption through energy conservation and energy efficiency practices and related tips offered through CSS as a part of Demand -response stimuli, with the disclosed method and system being embedded therein.

The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments. Also, the words "comprising," "having," "containing," and "including," and other similar forms are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.

Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., are non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, nonvolatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.

It is intended that the disclosure and examples be considered as exemplary only, with a true scope and spirit of disclosed embodiments being indicated by the following claims.

Claims

The Claims:

1. A method of enabling utility management by a utility management system (UMS), said method comprising:

receiving, by a processor of the UMS, utility service data collected from a plurality of utility systems coupled with the UMS;

generating, by the processor, a plurality of exceptions based on the received utility service data, the plurality of exceptions includes at least technical and non-technical loss related data associated with the plurality of utility systems;

determining, by the processor, a plurality of actionable work items, corresponding to the plurality of generated exceptions, associated with the plurality of utility systems;

receiving, by the processor, feedback data in response to execution of the plurality of actionable work items; and

determining, by the processor, a performance score of the utility management system based on the received feedback data.

2. The method as claimed in claim 1, wherein the utility service data comprising at least energy audit data, metering data, billing data, collections data, home- entity profile, peer group consumption data, utility system's distribution hierarchy data and external data comprising weather conditions, geographical data, and other related data.

3. The method as claimed in claim 1, wherein each of the plurality of actionable work items comprises at least workflow and category information, Value number, Service Level Agreement (SLA) number, approximate time to complete each actionable work item, potential loss information, field force skills required to complete each actionable work item, preparatory actions required and task data including consumer information, asset information, utility system's distribution hierarchy data, peer group details, asset location co- ordinates, and other related information.

4. The method as claimed in claim 1, further comprising:

assigning each of the plurality of actionable work items to one or more field force based on field force data associated with the one or more field force, wherein the field force data comprises at least field force current location coordinates, proximity score of the service location, asset replacement requirement, route information and real time traffic information, availability data of the field force, relevant technical skill information of the field force; determining average time required by the one or more field force to complete the assigned actionable work item; and

dynamically assigning each field force with another plurality of actionable work items based on status of each plurality of actionable work items in progress, corresponding average time required to complete, and proximity score of the service location of another plurality of actionable work items.

5. The method as claimed in claim 1, wherein receiving the feedback data comprising steps of:

executing the plurality of actionable work items by the one or more field force; and

receiving, the feedback data from a user device used by the field force upon execution, wherein the feedback data comprising at least status of the plurality of actionable work items, field force action data associated with the plurality of actionable work items, availability data of the field force, one or more unpredicted exceptions, and the Global Positioning System (GPS) location co-ordinates of the one or more field force recording the field force action data; and

updating a field force performance number associated with the plurality of actionable work item based on the received feedback data and corresponding SLA number.

6. The method as claimed in claim 5, wherein upon receiving the feedback data, the method comprising steps of:

determining the GPS location co-ordinates of the one or more field force recording the field force action data from the received feedback data;

comparing the GPS location co-ordinates with the asset location coordinates associated with the corresponding actionable work item assigned to the field force; and generating one or more actionable work items on the field force based on the comparison.

7. The method as claimed in claim 5, further comprising determining rank of each of the field force based on average time required to execute the plurality of actionable work items assigned to each field force and the field force performance number updated based on the received feedback data.

8. The method as claimed in claim 1, wherein the performance score of the UMS is determined based on effectiveness score and efficiency score associated with the UMS, wherein the effectiveness score is determined based on accuracy score associated with determining the plurality of exceptions and mapping of the plurality of exceptions to the plurality of actionable work items, wherein the efficiency score is determined based on value number associated with each actionable work item assigned to the one or more field force and value number associated with each actionable work item completed by the one or more assigned field force.

9. The method as claimed in claim 3, wherein the Value number is determined based on previously determined hit ratio, type of customer, and previously determined efficiency score.

10. The method as claimed in claim 9, further comprising dynamically updating the hit ratio based on generation of the plurality of actionable work item and successful completion status of the plurality of actionable work item.

11. A utility management system (UMS), said system comprising at least:

a processor;

a memory, communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the proces sor to :

receive utility service data collected from a plurality of utility systems coupled with the UMS;

generate a plurality of exceptions based on the received utility service data, the plurality of exceptions includes at least technical and non-technical loss related data associated with the plurality of utility systems;

determine a plurality of actionable work items corresponding to the plurality of generated exceptions, associated with the plurality of utility systems;

receive feedback data in response to execution of the plurality of actionable work items; and

determine a performance score of the utility management system based on the received feedback data.

12. The system as claimed in claim 11, wherein the processor receives the utility service data comprising at least metering data, billing data, collections data, home-entity profile, peer group consumption data, utility system's distribution hierarchy data and external data comprising weather conditions, geographical data, and other related data.

13. The system as claimed in claim 11, wherein the processor determines the plurality of actionable work items that comprises at least workflow and category information, Value number, Service Level Agreement (SLA) number, approximate time to complete the work item, potential loss information, field force skills required to complete the work item, preparatory actions required and task data including consumer information, asset information, utility system's distribution hierarchy data, peer group details, asset location co-ordinates and other related information.

14. The system as claimed in claim 11, wherein the processor is configured to:

assign each of the plurality of actionable work items to one or more field force based on field force data associated with the one or more field force, wherein the field force data comprises at least field force current location coordinates, proximity score of the service location, asset replacement requirement, route information and real time traffic information, availability data of the field force, relevant technical skill information of the field force; determine average time required by the one or more field force to complete the assigned actionable work item; and dynamically assign each field force with another plurality of actionable work items based on status of each plurality of actionable work items in progress, corresponding average time required to complete, and proximity score of the service location of another plurality of actionable work items.

15. The system as claimed in claim 11, wherein the processor is configured to receive the feedback data performing steps of:

executing the plurality of actionable work items by one or more field force; and

receiving, the feedback data from a user device used by the field force upon execution, the feedback data comprising at least status of the plurality of actionable work items, field force action data associated with the plurality of actionable work items, availability data of the field force, one or more unpredicted exceptions, and the Global Positioning System (GPS) location coordinates of the one or more field force recording the field force action data; and updating a field force performance number associated with the plurality of actionable work item based on the received feedback data and corresponding SLA number.

16. The system as claimed in claim 15, wherein upon receiving the feedback data, the processor is configured to:

determine the GPS location co-ordinates of the one or more field force recording the consumption data from the received feedback data;

compare the GPS location co-ordinates with the asset location coordinates associated with the corresponding actionable work item assigned to the field force; and

generate one or more actionable work items on the field force based on the comparison.

17. The system as claimed in claim 11, wherein the processor is further configured to determine rank of each of the field force based on average time required to execute the plurality of actionable work items assigned to each field force and field force performance number updated based on the received feedback data.

18. The system as claimed in claim 11, wherein the processor determines the performance score of the UMS based on effectiveness score and efficiency score associated with the UMS, wherein the effectiveness score is determined based on accuracy associated with determining the plurality of exceptions and mapping of the plurality of exceptions to the plurality of actionable work items, wherein the efficiency score is determined based on value number associated with each actionable work item assigned to the one or more field force and value number associated with each actionable work item completed by the one or more assigned field force.

19. The system as claimed in claim 13, wherein the Value number is determined based on previously determined hit ratio, type of customer, and previously determined efficiency score.

20. The system as claimed in claim 11, wherein the processor is further configured to dynamically update the hit ratio based on completion status of the plurality of actionable work item.