Billing & CRM as a Management tool for Utilities including SaaS. Dr. M.V. Krishna Rao

Size: px

Start display at page:

Download "Billing & CRM as a Management tool for Utilities including SaaS. Dr. M.V. Krishna Rao"

Kory Blankenship
8 years ago
Views:

1 Billing & CRM as a Management tool for Utilities including SaaS Dr. M.V. Krishna Rao

2 Agenda Power Utility Customer Requirements Prerequisite Systems Description of Systems Delivery Model - SaaS

3 Power Utility Customer Requirements- 1 Supply Related Registration and Prompt attendance of Fuse-Off Call or Trouble call Quick Restoration of Power supply in event of outage Quick Release of Power supply to new customer Maintenance of Voltage as per standards Adequate Reliability of Power supply

Power supply in event of outage Quick Release of Power supply to new

4 Power Customer Requirements- 1 Bill Related Regular Meter reading Timely delivery of Electricity Bill Easy Facilities for Payment of Bill Proper accounting of amounts paid by him Prompt attendance of Service calls General Service Single point Customer Service Centre Ready access to Information on Tariffs and Procedures and Processes

amounts paid by him Prompt attendance of Service calls General Service Single point

5 Prerequisite Systems Mapping of Network & Creation of GIS Indexing of Customers Integration of GIS and CIS Computerization of Billing Data Acquisition

Database Trouble Call management New Customer management Energy Audit & accounting

6 GIS & CI Implementation methodology GPS Survey GIS based Applications Assets Data Customer Data Base Maps Network Topology Base Map Network overlay Integrity checks Database Trouble Call management New Customer management Energy Audit & accounting Revenue Protection Asset management Power supply management Technical Loss reduction HVDS

8 DISPLAY OF POLE WISE NO. OF CONSUMERS IN UMRETH VLLAGE

9 INDICATION OF CONSUMERS ON POLE

10 CONSUMER INDEXING CONSUMER_CODE: kV Umreth SS 11kV-Town1 DTR E1140

11 Trouble Call Management Call registration Call Monitoring Call Analysis Quick Restoration Preventive Steps

14 Service call Management Components Registration of Service Call Job Card Creation Call Monitoring Identification Of Trouble spots

15 Service call Registration

16 Dispatching Service calls

17 New Customer Registration Identification of Location on GIS Computer aided Planning of supply arrangements, Estimate Follow up from Registration to Release

18 Registration Of New LT Customer

19 Supply Arrangements for New Customer

20 Evaluation Report

21 Power Quality & Reliability Guaranteed Customer Service Standards Regulatory Requirements Data acquisition Estimation of Voltage at Customer Premises Reliability indices

22 Reporting and Database server Plasma Screen Operator Workstation Reports Printer TOWN POWER MONITORING CONTROL CENTER LAN Virtual Private Network Server of Telecom Service Provider GIS/TCMS Field Wiring CDMA/GPRS Modem With Antennae Field Wiring CDMA/GPRS Modem With Antennae Data Concentrator Substation 1 Electronic Energy Meters multi-dropped Data Concentrator Substation 5 Electronic Energy Meters multi-dropped

23 State Estimator for Dagjipura 11kV Load : 838kW,628kVAR

24 State Estimator for Dagjipura 11kV Load : 1828kW,1371kVAR

25 State Estimator for Dagjipura 11kV Load : 1143kW,857kVAR

26 State Estimator for Dagjipura 11kV Load : 1524kW,1143kVAR GECE,Hyderabad

27 POWER SUPPLY RESTORATION Identifies the section on which the fault has occurred Selects on alternative a radial distribution sources for feeder Restoration of Supply, Isolates considering the faulty Section by opening the switches at both Transformer ends of the section capacity of the adjoining substations and Reports the current the sequence loading of status switching operations to isolate the Present faulty loading sections status of alternative feeder, conductor Network size, thermal display limits, with faulty over part current in different relay settings colour. for the feeders and node voltage limits Optimum selection from available alternatives Switching schedule to be performed to isolate fault and extend supply to dark regions Minimizes the affected area GECE,Hyderabad

28 CRM Delivery Model Traditional Model ASP Model SaaS Model

29 What is Saas SAAS is a software application delivery model where a software vendor develops a webnative software application and hosts and operates (either independently or through a third-party) the application for use by its customers over the Internet.

30 Key Characteristics Customers do not pay for owning the software itself but rather for using it. Network-based access to, and management of, commercially available (i.e., not custom) software Activities that are managed from central locations rather than at each customer's site, enabling customers to access applications remotely via the Web.

31 Partnerships Hosters Application management services Infrastructure hosting service Co-location services Solution Integrators Deployment management Application development and integration Solution Partner Complementary value-add services

32 Advantages No large upfront costs - usually free trials High levels of security physical, power, pipes No installation costs low one-time costs Minimal training Anywhere, anytime, anyone mobility Operating costs only Can be terminated; re-sized No Capex hoops.

33 Disadvantages Core functionality out-sourced Broadband risk Limited personalization/tailoring No competitive uniqueness advantage Not suited to high volume data entry

34 Business Model From TO Procurement Long Evaluation Process Try Before You Buy cost Capital Expenditure Operating Expenditure Deployment Customization Configuration Management Reliance on Internal IT Department Service Level Agreement

35 Opportunity - Value Proposition New market opportunity Predictable revenue Lower TCO ISV Benefits Positive customer experience Add-ons as value-added services Lower support cost End-User Benefits Lower cost of entry Reduce risk Higher ROI Quick response to change in demand Rapid deployment of new services Focus on core business

36 Factors Limiting SaaS Adoption Big Customers want to keep their data under Internal Control Not suitable, if extensive customisation is required Availability of Open source applications, Inexpensive software and Band width make SaaS model less attractive Considered Potential Security & Operational Risk vs SaaS provides better security and Level of Service as specialists are engaged to handle tasks

37 ASP vs SaaS ASP : Separate Data base for each Customer Separate Customized Application for each customer SaaS Separate or Common Data base for each Customer Common Application, configurable for each customer

38 SaaS Architecture Approach Three approaches 1 :Separate database for each customer 2: Common database, with a set of Predefined custom fields for each customer in same Table 3: Common database, with any number of fields in Supplemental Table

39 SaaS Architecture Model - 1 Features Similar to the traditional ASP Model Separate database feach customer has its own customized version of the hosted application Each customer runs its own instance of the application on the Host s Server.

40 SaaS Architecture Model -1 Features Separate database for each customer Merits Easy to implement Demerits Sub- Optimal Utilization of Database and database server High Infrastructure cost

41 SaaS Architecture Model -2 Features All customers data in one database. Custom fields provide for different customers in the same table Merits Maximize number of customers per database Demerits Sparse Population of data in table against Custom fields All custom fields have to be predefined

42 SaaS Architecture Model -2( contd) Customer ID Common Field 1 Common Field 2 Custom Field 1 Custom Field 2

43 SaaS Architecture Model -3 Features: All Customers data in One database Separate Table to store Custom fields of different customers with Name and Value Merits : No Restriction on number of custom fields to each customer Suitable if custom fields are difficult to identify in advance Best utilization of database and database Server Demerits : Complex Search /Query

44 SaaS Architecture Model -3( Contd) Main Table Customer ID Common Field 1 Common Field 2 Record ID Supplemental Table Record ID Name of custom Field Value

45 Thank YOU

GEOGRAPHIC INFORMATION SYSTEM ECG S EXPERIENCE

UPDEA 15 TH CONGRESS, JUNE 2005, ACCRA-GHANA GEOGRAPHIC INFORMATION SYSTEM ECG S EXPERIENCE Presented By: Ing Patrice Afenyo In This Presentation.. ECG Brief Components of a GIS Why ECG Needs GIS Our Approach