GIS Integration Using SAP XI

GIS Integration Using SAP XIScenario View

Rory Shaffer

Utility Industry Business UnitSAP Labs LLC

Electric Transco- Disco Data Modeling

Demostration of SAP / GIS Integration

Integration Methods

Spatial Planning with SAP

SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC

Structuring of technical assets

� Functional location

� Equipment

� Bills of material

� Assemblies

� Install base

Interface to industry-specific systems

� GIS

� SCADA

� CAD

� Graphical Work Clearance Planning

Close connection between technical and accounting assets

EAM Master Data


Volume and complexity of technical data

Number and complexity of objects for an electricity supply grid

complex structurehigh system load

simple structurehigh system load

complex structure

simple structurelow system load

figures derived from a mid sized utility

co

mp

lexity

of

asse

ts

number of objects

houseconnectionslocal network

low voltageswitch boardsmedium vol-

tage poles

transformerstations

power supplystations

high vol-tage poles

street lights

local net-work stations

medium vol-tage circuits


Search and retrieval functions for technical data

characteristic� temperature

� pressure� voltage

� type of ....� diameter� ...........

classes� transformer� switches� valves� pumps� poles� ...........

technical

objects� functional

locations�equipments

search criteria for

characteristics :

� values� ranges

� ..........

search criteria for

classes :

� catchwords� description

� ..........

result list for

technical objects :

� master data � technical data

� ..........


The object structure depends on the customer’s modeling objectives:

� Functional / Physical Hierarchy

� Logical / Location structures

� Existence of Spatial System

� Level of Detail for Organizations

Functional Location - FL

Region

Voltage

Circuit

Span

Structure


The object structure depends on the physical structure of the supply grids:

� Underground/overhead grids

� Meshed/hierarchical grids

The object structure depends on the customer’s modelingobjectives:

� To represent physical structures

� To represent logical structures

� To match the objects with interfaces to geographical information

systems (GIS) or asset management/facility management (AM/FM) systems

Technical Objects in T&D


FL - Logical/Location Example

FL – Installed Equipment Example


electricity supply grid

Field01

Field02

Field 03

Field01

Field02

Field 03

Field01

Field02

Field 03

Substation ST 435 Substation ST 571

Substation ST 768

Line No. 187

Line No. 189

Line No. 186

Line No. 188

line system with sections

Object link to connect two systemswith different hierarchy

substation withtransformer fields

Example : structuring for a supply grid


TD Utility Customer Example - Distribution

Highest Level Breakdown By

Division

Distribution Circuit

Municipalities

Networks

Sub-Transmission Circuits

Third Party Work



Central Div, Circuits Level Breakdown By Substation

Write Work Against the Substation (Outside Plant)



Central Div, Regional Level Breakdown By Municipalities

Write Work Against the Town



Central Div, Networks Level Breakdown By Street

Write Work Against the Network Street



Central Div, Sub-Transmission Level Breakdown By Voltage

Write Work Against the Circuit - Voltage


TD Utility Customer Example - OH Transmission

Highest Level Breakdown ByOverhead – Underground

OHCircuitsStructures

UGCathodicPumping PlantsSparesCross Over Cabinets



Transmission Overhead - Circuits

Write Inspection Work Against the Circuit



Transmission Overhead – Tower Lines

Write Work Against the Structure



Transmission Overhead – Spans

Write Tree Related Issues Against the Span


TD Utility Customer Example – OH Transmission

Transmission Overhead – Structures

Write Work Related Issues Against the Structure


TD Utility Customer Example – UG Transmission

Transmission Underground – Highest Levels

Cathodic Protection

Pumping Plants

Spares

Cross Over Cabinets



Transmission Underground – Circuits

Write Work Related Issues Against the Circuit


TD Utility Customer Example - UG Transmission

Transmission Underground – Pumping Plants

Write Work Related Issues Against the Pumphouse



Transmission Underground – Cabinets

Write Work Related Issues Against the Cabinet


(sub stations, transformers)

ST 435ST 435ST 435

ST 435-AST 435ST 435--AA

ST 435-BST 435ST 435--BB

ST 435-A-1ST 435ST 435--AA--11

ST 435-A-2ST 435ST 435--AA--22

10006451000645

10008391000839

....

....

.............

Substation Nr. 435

conductor rail A

transformer field 1

transformer 400 kVA

conductor rail B

transformer field 2

transformer 300 kVA

... assemblies and spare parts


Functional Location Equipment

Example : structuring for a transformer station


(line systems)

.............

L 114L 114L 114

L 114 01L 114 01L 114 01

L 114 02L 114 02L 114 02

P 187P 187

P 188P 188

....

200456200456

203478203478

201569201569

....

Line Nr. 114

section 01 ( 0 ... 14.7 km )

section 02 ( 14.7 ... 26.8 km)

pole Nr. 188


pole Nr. 187

pole top

crossarm type XA 24

isolators type IS 45/9

Assembly

Functional Location Equipment

Example : structuring for a line system


Line

Customer

Segment

Circuits

Transformer

StationTransformer

Equipment

installation

Functional location

hierarchy

Functional location

Equipment

Legend:

GIS Integration

Asset Structure in Transmission

Asset Structure in Distribution

Asset Structure in Work Management


Technical Installation

0539802

125.256.01

0716192

0539802

125.256.01

0716192

Connection Obj.

Premise

Connection

Premise

Device

Device Loc.Transf.

Connection Obj.

Connection

Device Loc.

Device

Transformer

Transf.Field

Technical Structure for a Connection in SAP

Transf. Field

Technical Installation


Data Structure Links to Customer Accounts

Transco- Disco Data Modeling


Integration Methods



From:

�Vendor Centric Point to Point

�Project Specific

�Limited Dynamic Capability

To:

�Middleware

Now:

�Web Services SOAP Integration

�Decrease Redundant Data

�Two-way Communication

�Spatial Planning of Facilities / Service

�Packaged Content

�Mobile GIS

Spatial Interfacing Needs Have Evolved


Data mapping with external systems (GIS, NIS)

technical

data

spatially related

technical data

spatial related

data

used by the SAP system

used by the GIS system

Data stored for an asset can be grouped into

� purely technical data (e.g. type of isolator medium)

� spatially related technical data (e.g. length and type of wire)

� purely spatial related data (e.g. x-y coordinates)

SAP system is the

owner of the data

Every system is

responsible for

the updates in the

other one

GIS system is the

owner of the data


SAGRES Project

SAGRES Project

Revisiting GeoSpatial Data Usage with SAP

Launched 2005

Engaging Multiple Industries

Leading Partner Community Involved

Use Cases Out Come


SAGRES Project


SAGRES Concept for Citizen Portal

Help

Show on map:

Map it Track it

Suggest

Go

Report a Problem

Traffic light

Hydrant

Street Lamp

Plants

City projects

+

_

Spatial Rendering of Local Environment

Driving Citizen Notification of Issues

Opens Sticky Note:To report a Problem

Asset/ Layer Scroll

Search Window:

Directional Navigation

Map It: Track It:

Help

Zoooom

Navigation/Preview Area

Search/Tools Area

Shortcut – Legend Search

Report a Problem

Help Street Lamp

Hydrant

Streent Lamp

Street Lamp

Show on map:

Map it Track it

Hydrant

Suggest

Go

Opens Suggestion Note


Object mapping with external systems (GIS, NIS)

asset structure in R/3

geographical information systemnetwork information system



Integration Methods

ESUG Customer Successes

ESRI Application Interaction



Demonstrable Scenarios

To show the power of SAP to GIS Integration we have built up several proof of concept scenarios. The scenarios are utilizing SAP and ESRI ARC GIS Server with integration delivered via SAP XI using SOAP communication protocols.

The scenarios demonstrate that;

Information can be shared across business platforms to deliver end to end business processes.

Processes can originate from SAP or GIS side without user knowledge of both applications.

Data can be called and updated from either side.

Complex calculations can be performed and information updated / shared across platform.




The following scenario(s) screen shots demonstrate;

Locating Customer in SAP using call center data, when displaying customer on GIS map within SAP Call Center Window.

Locating Customer in GIS, Retrieving SAP data and displaying in map environment.

Editing Map information for customer connection position, calculating length of service connection cable and send numerical and spatial data update into SAP.


From the Call Center, Locate the Customer


From the Call Center, Select Customer


Request Location Information for Customer


Map Is Produced With Customers Home Showing Related Spatial Data


Scenario 1: Evaluation Path

GISIS-U

Customer BuildingAddress ��


Scenario 1: System Landscape

Spatial Database

GIS Server

SAP Application Platform

DB

ABAP

J2EE

GIS Client

XI Server

HTTPhttp://gisserver/mapservice/map.aspx?street=myStreet&house_number=myNumber

SAP Front end









From the ESRI ArcMap Side, Customer is Displayed on Map


From the ESRI ArcMap Toolbar, Activating SAP Structure Tool


From the ESRI ArcMap Side, SAP Structure Tool Using Polygon Selection Method


From the Call Center, Select Group of Customers within Polygon


From the ESRI ArcMap Side, Selected Customer with SAP Data Retrieved for GIS User


Scenario 3: Read SAP data

Task: Read data from SAP system to get additional information for a GIS object

Problem: Link object from GIS and SAP system

Example: Read data from IS-U data model for a building

Solution: Mapping of data models


Scenario 3: Data model

Connection objectConnection object

PremisePremise

Address for Building

InstallationInstallation

0539802

125.256.01

0716192

0539802

125.256.01

0716192

Connection obj.Connection obj.

Premise

Connection Connection

Premise

Device Device

Device Loc.Device Loc.

TrafoTrafo

Object link

PolePole



GIS IS-U Datenmodell

Premise

Connection object

Building

Address ��

data Connection object,

Premise, Installation, Device

Installation

Device



Spatial Database

GIS Server


DB

ABAP

J2EE

GIS Client

XI ServerSOAP

XI AdapterServer Proxy

SAP Front end









From the ESRI ArcMap Side, Editing Customer Map Data for Connection Point


From the ESRI ArcMap Side, Moving Connection Point


From the ESRI ArcMap Side, Moved Connection Point


From the ESRI ArcMap Side, Stop Edit


From the ESRI ArcMap Side, Saving Map Edits to Customer Service Point


From the ESRI ArcMap Side, Updates Being Sent to SAP via XI Integration


From the SAP Side, Updates Being Displayed via XI Integration


Scenario 4: Update SAP data

Task: Changing data in GIS requires an update of corresponding SAP data

Problem: Link object from GIS and SAP system

Example: Modifications of the spatial location of service connection leads to modification of a characteristic of the suppling pole

Solution: Mapping of data models and object key value


Scenario 4: Data Model

TransformerTransformer

PolePole

Count of supplied

connections

Count of supplied

connections

Length of cable toconnections

Length of cable toconnections

Transformer with all supplied buildings and

cable length



Value Mapping

GIS

PM data model

Functional Location

Equipment

Service Point

Transformer ID, Service points,

Cable Length ��Transformer



Spatial Database

GIS Server


DB

ABAP

J2EE

GIS Client

XI ServerSOAP

XI AdapterServer Proxy

SAP Front end


Additional Demonstrable Scenarios

From the SAP Customer Interaction Center;

Identify the SAP Technical Object Record for the Customers Pole Supplying Power.

Mark the Customer as Inactive / Active and Reflect Change of Service Status on the GIS Map View.



Integration Methods



Spatial Planning

Initial Offering

�Traditional Tabular Approach

Energy East Customer Live Since 4/2005

New Release Project In Works

�Spatial Design Approach

Multiple Customers Providing Input

Geo Data Base

SAP EAM

B

A

D

ICU

Estimate

Engine


� 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

� IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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.

� MaxDB is a trademark of MySQL AB, Sweden.

� SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 in several other countries all over the world. 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.

� These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Copyright 2006 SAP AG. All Rights Reserved

Documents

GIS Integration Using SAP XI