utilties go are mobile christoph wobbe ibu utilities, sap ag

Utilties go are mobile

Christoph Wobbe

IBU Utilities,

SAP AG

Utiltiies are mobile, Christoph Wobbe, SAP AG ASUG 2003 2

SAP for Utilities- Mobile Asset Management Topics

Backend BusinessProcesses

TechnologyMiddleware

Mobile Business Processes


Utilities are mobile

Field Service requires mobile Processes

Important Questions are:

Quality of Service?

Costs of Service?

Who are my Customers? Internal External


Optimization of Field Service

Minimize the Administration

Field Service should work

in the field, not in the office

Optimize your stock

Optimize business processes


Optimization of Field Service means

Improvement of Customer Relationship

Reduce response time

Optimize appointments

Increase customer satisfaction

Increase customer information


Mobile Applications

Simple User Interface

Mobile Applications have to cover all required business processes

Easy way to change User Interface

State-of-the-art Technology


Workforce Management Prozess

NotificationNotification

SCADA/Customer

SCADA/Customer

OrderCreate

OrderCreate

Order Release

Order Release

OrderConfirmation

OrderConfirmation

OrderTermination

OrderTermination

Analyse History Analyse History

OrderPlanning

OrderPlanning

MaintenancePlan

MaintenancePlan


Mobile Service – C Business Map


MAM 2.0 Standard - Functional Overview

SAP BackendData creation and assignment

Order Management

Contract Management

Inventory Management

Measurement & Counter Readings

Notification Management

Data update in backend

Technical Object

Management

Business Partner Management


mySAP Mobile Business Szenarios

ReconnectionOrders/

Orientation

Disconnections

Collection

Notifications

Display of technical Data

Outages/

Malfunctions

Mobile Service

Nonperiodic Meter Readings

Confirmation


Mobile Utility Enhancement - Functional Overview

My SAP Utilities

Disconnections /Collections / Reconnections

Non periodic meter readings

Meter replacements

Outages /Malfunctions


Important data for Mobile Utility

• Business partner

• Contract and contract account (open items)

• Installation and premise

• Connection object and device location (meter reading notes)

• Meter data (certification data)

• Register data and meter reading data

• House connections

• Technical installations (inspection data)

• Disconnection and reconnection data

• Appointments (for service orders)

• Business partner

• Contract and contract account (open items)

• Installation and premise

• Connection object and device location (meter reading notes)

• Meter data (certification data)

• Register data and meter reading data

• House connections

• Technical installations (inspection data)

• Disconnection and reconnection data

• Appointments (for service orders)


1. Meter replacement (periodic replacement)

Processing in IS-U CCS:• Creation of orders or notifications


IS-U data that should be displayed (Download):• Customer data

• Connection object and device location data (reading notes)

• Installation and device data

• Certification data

• Responsible person for object (e.g. caretaker)

• Last meter reading result and estimated meter reading result

for meter replacement data (consistency check)




• Certification data



for meter replacement data (consistency check)

IS-U data that should be entered (Upload):• Meter replacement, meter installation, meter removal

• Meter reading results

• Meter reading notes

IS-U data that should be entered (Upload):• Meter replacement, meter installation, meter removal

• Meter reading results



2. Disconnection/Collection/Reconnection



IS-U data that should be displayed (Download):• Customer data and contract account data (open items)

• Disconnection information (disc. reason, disc. object)

• Disconnection history


• Dunning information (dunning level)



IS-U data that should be displayed (Download):• Customer data and contract account data (open items)

• Disconnection information (disc. reason, disc. object)

• Disconnection history


• Dunning information (dunning level)



IS-U data that should be entered (Upload):• Meter reading results

• Confirmation of disconnection

• Payments


• Confirmation of disconnection

• Payments


3. Repairs/Malfunctions/Outages

Processing in IS-U CCS:• Creation of orders or notifications in CIC

Processing in IS-U CCS:• Creation of orders or notifications in CIC


• Damage codes


• Meter data

• Disconnection information

• Additional information (long text)


• Damage codes


• Meter data

• Disconnection information

• Additional information (long text)




4. Non periodic meter reading






• Installation and premise data

• Meter and register data


for meter reading data (consistency check)




• Installation and premise data

• Meter and register data


for meter reading data (consistency check)






Searching the mobile device...

DataEntry

Browser

DataTransfer

ScreenSize

...

...


Decision for Mobile Devices

Which Business Processes?

Requirements

Following Questions should be answered:

1. Do you need a permanent connection to the SAP System?

2. Which Screen Size and Resolution do you need ?

3. Do you need a complete keyboard?

4. What is the Working Enviroment of your Field Service?


Synchronisation of Data

Mobile Device Backend

XML

Generic SyncAPI

SOAP Container

Synchronization Layer

SmartSyncAPI

Generic SyncAPI

SmartSyncAPI

Application(client-side)

Application(server-side)


Browser Browser

Mobile Device Backend system

Native UI Native UI

Middleware

http,

https Mobile Engine

2.1 SP 01 Mobile Engine

2.1 SP 01

S

AP

We

b A

pp

lica

tio

n

Ser

ver

6.20

SP

20

SA

P W

eb

Ap

pli

cati

on

S

erve

r 6.

20 S

P 2

0

SAPIS-U CCSRelease 4.64


ME

ser

vic

es M

E s

ervi

ces

IS-U Release 4.64

PI 2003.1 PI 2003.1

Architecture for IS-U Release 4.64


Browser Browser

Mobile DeviceBackend system with middleware

Native UI Native UI

http,

https Mobile Engine

2.1 SP 01 Mobile Engine

2.1 SP 01

S

AP

We

b A

pp

lica

tio

n

Ser

ver

6.20

SP

20

SA

P W

eb

Ap

pli

cati

on

S

erve

r 6.

20 S

P 2

0



ME

ser

vic

es M

E s

ervi

ces

IS-U Release 4.71

PI 2003.1 PI 2003.1

Architecture for IS-U Release 4.71


Schedule Mobile Utility

Project start: February 1st 2003

Development Closure: August 1st 2003

Test until September 1st 2003

Production&Assemb. October 1st 2003

Rampup October 2003

Unrestricted Shipment January 2004

Project start: February 1st 2003

Development Closure: August 1st 2003

Test until September 1st 2003

Production&Assemb. October 1st 2003

Rampup October 2003

Unrestricted Shipment January 2004

utilties go are mobile christoph wobbe ibu utilities, sap ag

Documents