Académique Documents
Professionnel Documents
Culture Documents
Using SAP XI
Scenario View
Rory Shaffer
Utility Industry Business Unit
SAP Labs LLC
Functional location
Equipment
Bills of material
Assemblies
Install base
Interface to industry-specific
systems
GIS
SCADA
CAD
complexity of assets
complex structure
complex structure
high system load
transformer
stations
power supply
stations
local network stations
high voltage poles
street lights
simple structure
low system load
local network
low voltage
switch boards
medium voltage circuits
house
connections
number of objects
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
simple structure
high system load
characteristic
temperature
pressure
voltage
type of ....
diameter
...........
classes
transformer
switches
valves
pumps
poles
...........
technical
objects
functional
locations
equipments
Functional Location - FL
The object structure depends on the
customers modeling objectives:
Functional / Physical Hierarchy
Region
Voltage
Circuit
Span
Structure
FL - Logical/Location Example
Field
01
Substation ST 571
Field
02
Field
01
Field
02
Field 03
Line No. 188
Object link to connect two systems
with different hierarchy
Field
02
Field 03
Substation ST 768
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
substation with
transformer fields
ST
-A
435
ST 435435-A
transformer field 1
ST
-A-1
435
ST 435435-A-1
1000645
1000645
....
ST
-A-2
435
ST 435435-A-2
transformer field 2
1000839
1000839
....
ST
-B
435
ST 435435-B
conductor rail B
.............
Functional Location
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
Equipment
(line systems)
LL 114
114
LL 114
114 01
01
P
P 187
187
200456
200456
203478
203478
201569
201569
crossarm type XA 24
isolators type IS 45/9
pole Nr. 188
P
P 188
188
....
pole top
....
LL 114
114 02
02
.............
Functional Location
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
Equipment
Assembly
Transformer
Legend:
Functional location
Equipment
Segment
Line
Equipment
installation
Functional location
hierarchy
Circuits
Customer
GIS Integration
Connection Obj.
Transf.Field
Connection
Transformer
Device Loc.
Connection Obj.
Device
Technical
Installation
Premise
Technical
Installation
Premise
Transf. Field
Transf.
Device Loc.
Connection
071619 2
071 6192
0539802
0539 802
125.256.01
125.256.01
Device
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
spatially related
technical data
Every system is
responsible for
the updates in the
other one
spatial related
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
Search Window:
Map It:
Track It:
Navigation/Preview Area
Map it
Track it
Go
Show on map:
Report a
Problem
Map it
Track it
Go
Street Lamp
Search/Tools Area
Hydrant
Suggest
Show on map:
Plants
Traffic light
City projects
Help
Report a
Problem
Streent Lamp
Hydrant
Suggest
Opens Suggestion
Note
Street Lamp
Spatial Rendering
of Local Environment
Help
Driving Citizen Notification of Issues
Street Lamp
Hydrant
Help
Asset/ Layer Scroll
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
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.
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.
IS-U
GIS
Customer
Address
Building
HTTP
http://gisserver/mapservice/map.aspx?street=myStreet&house_number=myNumber
XI Server
GIS Server
J2EE
Spatial Database
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.
From the ESRI ArcMap Side, SAP Structure Tool Using Polygon Selection Method
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
From the ESRI ArcMap Side, Selected Customer with SAP Data Retrieved for GIS User
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
Connection
Connection object
object
Premise
Premise
Connection
Connectionobj.
obj.
Pole
Pole
Premise
Object link
Installation
Installation
Premise
Trafo
Trafo
Connection
Connection
Device
DeviceLoc.
Loc.
0716192
0539802
0716192
0539802
125.256.01
125.256.01
Device
Device
GIS
IS-U Datenmodell
Address
Building
Connection object
Premise
Installation
Device
XI Server
SOAP
GIS Server
XI Adapter
Server Proxy
J2EE
Spatial Database
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.
From the ESRI ArcMap Side, Editing Customer Map Data for Connection Point
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
From the ESRI ArcMap Side, Saving Map Edits to Customer Service Point
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
From the ESRI ArcMap Side, Updates Being Sent to SAP via XI Integration
SAP AG 2006, GIS Integration , Rory Shaffer SAP Labs LLC
Pole
Pole
Count
Countof
ofsupplied
supplied
connections
connections
Length
Lengthof
ofcable
cableto
to
connections
connections
Transformer
Transformer
Transformer with all
supplied buildings and
cable length
GIS
Service Point
Transformer
Value Mapping
Transformer ID, Service points,
Cable Length
PM data model
Equipment
Functional Location
XI Server
SOAP
GIS Server
XI Adapter
Server Proxy
J2EE
Spatial Database
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
B
A
D
I
CU
Estimate
Engine
SAP EAM
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,
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
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
JavaScript
is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
MaxDB
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.