SAP Q&A - Solution Overview Smart Meter Rollout...Define regional structure of device locations Import device location to “planning scenario” Use existing regional (postal) structure

Solution Overview

Smart Meter Rollout

Joerg Kiel

04-15-2010

© SAP AG 2009. All rights reserved. / Page 2

1. Key trends and issues

2. SAP solution overview

3. Why SAP? Top reasons

Agenda





Agenda


Smart Meter Rollout

Not just an Option but a Law!

As part of the Third Package of Energy Liberalization Measures adopted

on 13 July 2009, EU Member States are obliged to:

"ensure the implementation of intelligent metering systems that

shall assist the active participation of consumers in the gas and

electricity markets"

In other words, to roll out some form of smart metering.

http://www.amplifier.cd/Natur/Technik-Elektronik/images/Stromzaehler.jpg


So what – just swap them!

The UK facts as an example

47 Million gas and electricity meters in residential homes have to be replaced.

3,7 Million gas and electricity meters in small and medium enterprises have to be replaced.

In total 50,7 Million smart meters have to be implemented within a 10 years timeframe.

The UK recently released a law to replace every Ferraris-meter by a smart meter by 2020.

Rough assumptions for the physical onsite replacement: Installation on site 30 minutes

Configuration

onsite/remotely

10 minutes

Traveltime (average) 10 minutes

Site documentation 5 minutes

Back-office logistics incl.

asset management

15 minutes

Total effort per meter: 70 minutes

In the UK the total effort just to replace smart meters onsite

equals 3360 FTEs for a 10 years period

A replacement within 3 years would equal 11200 FTEs for a 3 years period


Nowadays meters are replaced after decades of lifetime.

In parallel old-fashioned meters are subject to an onsite reading task (or mail-based task)

at least once a year.

Assuming that the initial smart meter rollout would be done based on regular replacement cycles

the initial smart meter rollout would take decades - unacceptable - as utilities companies

request to benefit sooner.

Based on the more complex implementation procedure to install a

smart meter (communication, integration, parameters) installing

a smart meter is more sophisticated and demanding than just

swapping an old-fashioned meter

Once a meter is replaced by a smart meter the dispatching and planning

of the meter reading resources needs to be updated accordingly

and in real-time while the integrated smart meters will be controlled

remotely.

The Uncensored Challenge

The Initial Smart Meter Rollout

That’s what resources are made available for by the utilities companies

- no more no less -

http://www.ka-news.de/wirtschaft/karlsruhe/Karlsruhe-EnBW-CeBIT-Intelligenter-Stromzaehler-Green-IT;art127,158517,B?bn=211538


What Does This Mean for your Business?

Smart meter rollout - top executive issues

How to assess and manage the enormous

field services workload peak for the initial

smart meter rollout?

How to supervise the progress of the initial

smart meters rollout with minimized internal

planning resources?

How to integrate asset management and

telco infrastructure?

How to plan a rollout sub-area by sub-area

to benefit from smart meter benefits prior to a

final comprehensive rollout?

How to involve field service sub-

contractors efficiently?


Insufficient Rollout Planning Results in Major Cost

Risk and Customer Dissatisfaction

Demand and supply not aligned,

excessive travel time

Can’t balance capacity and maximize

throughput

Can’t manage escalating costs

high commercial risk in

workforce management

Can’t satisfy demand

Can’t balance capacity and

maximize throughput

Can’t manage escalating costs

escalating costs due to

poor asset management

Short notice privacy disturbance

Multiple customer disturbances

risk of customer

dissatisfaction

Poor delivery execution

Delay in roll-out

lack of logistic guidelines

Poor demand visibility leads to failing deliveries

Poor customer service levels

lack of demand visibility for telco-infrastructure


Professional Rollout Planning Results in Minimized

Cost Risk and Customer Satisfaction

minimize commercial risk

in workforce management

Ensure optimized

asset management

achieve customer

satisfaction

define logistic guidelines

improve demand visibility

for telco-infrastructure


Agenda





The Uncensored Challenge in a Picture

Part 1

Status today:

Each meter is linked to an equipment location and is subject to preventive and corrective maintenance

Each meter has to be subject to both a meter reading planning/dispatching and a smart meter

replacement dispatching/planning

Today‘s maintenance resources are driven by a given district planning and almost predictable

maintenance effort

Today‘s meter

reading districts

Today‘s meter

locations


The Uncensored Challenge in a Picture

Part 2

The planning risk:

► Meter reading planning/dispatching will not be updated in parallel obsolete site visits = additional work and expenses

► Meter reading becomes more and more inefficient as travel time will exceed additional expenses per meter reading

► Smart meter implementation will be inefficient due to excessive travel time additional expenses/smart meter‘ installation

► Poor asset management and unpredictable telco infrastructure will cause tremendous budget increase

Smart meter

location after

replacement


Smart Meter Rollout

Various Benefits – One Solution

What impact is caused by insufficient rollout planning?

Manual meter reading and maintenance effort of still remaining meters

Total amount of replaced meters

Average travel distance/meter

Total amount of replaced meters

Obsolete site visit for reading

purposes at smart meter

site

Implementation per smart meter

Quality of planning

Average travel time

per smart meter

Effort spent in

device logistics

Quality of planning

Effort spent in

telco infrastructure

Quality of planning


How the process works

Smart Meter Rollout Planning

Fully integrated into SAP IS-Utilities


1

Preparation

3

Activation

4

Order

creation

Planning

5 Execution

2


1

Preparation

3

Activation

4

Order

creation

Planning

5 Execution

2


Step 1: Preparation

Define task lists per meter category

Create general task list per device

category as a template to define tasks to

be execute to install that kind (category)

of smart meter

Apply task list to device category

enabling automated maintenance plan/

task-list assignment for every single

device later on


1

Preparation

3

Activation

4

Order

creation

Planning

5 Execution

2


Step 2: Planning

The principals:

Import device location to “planning scenario” e.g. roughly

separated by ZIP-code

Cut planning scenario into regional “districts” representing the

estimated target workload e.g. “for next week”; each district

may be subdivided to reflect e.g. different teams

Assess (workload per district) or (workload per team) based

on KPIs

Improve and rework scenario according to target KPIs

Activate scenario to trigger order creation for that specific

scenario or just a single district


Step 2: Planning – device location based

Define regional structure of device locations

Import device location to “planning scenario”

Use existing regional (postal) structure of

device locations or set-up a regional structure

by drag&drop in the tree

Define individual regional districts in the map

via rectangles/ polygons as a rough (regional)

pre-planning

Each district (will) represent the workload for a

certain period of time, e.g. 1 week

granularity may be improved in an iterative

approach

Each district may be divided in sub-district e.g.

to represent teams working the same district in

parallel


Step 2: Planning – device location based

(automatically) assign device locations

within the defined area to regional

district

Apply default device category to every

district

or any other level of the regional structure

If necessary device category

maybe reworked even on device

location level

automated process possible if

decision making attributes

available


Step 2: Planning

Improve and balance workload per

district/per team

Assess district workload based on KPIs

Improve and Rework district assignment

to meet the expected KPIs/Workload


1

Preparation

3

Activation

4

Order

creation

Planning

5 Execution

2


Step 3: Activation

Activate planning scenario of

choice

Press “activate”-button

e.g per district or per scenario (controlling the amount of data in the

upcoming order creation job)

automated creation of maintenance

plans for every single device

automated assignment of task lists

to maintenance plans based on the

applicable device category


1

Preparation

3

Activation

4

Order

creation

Planning

5 Execution

2


Step 4: Scheduling/order creation

Execute order creation in line with

given scheduling

Automatically create orders based

on maintenance plans (parallelize processes on scaled application

servers)


1

Preparation

3

Activation

4

Order

creation

Planning

5 Execution

2


Questions and comments

Do you have further questions?

We kindly ask you to contact: [email protected]

mailto:[email protected]

© 2011 SAP AG. All rights reserved. 40

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries..

© 2010 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Documents

SAP Q&A - Solution Overview Smart Meter Rollout...Define regional structure of device locations Import device location to “planning scenario” Use existing regional (postal) structure