Structuring of Assets in a Utilities Environment
-
Upload
vassilis-iliadis -
Category
Documents
-
view
74 -
download
1
description
Transcript of Structuring of Assets in a Utilities Environment
6th SAP INTERNATIONAL UTILITIES CONFERENCE 2007
Structuring of Assets in a Utilities Environment
Ulrich ZaglerSolution Management EAM, SAP AG
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 2
Agenda
Introduction
Type of Technical Objects in T&DEquipments and Functional LocationsOthers
Structuring
Classification System
IS-U Requirements
Processes
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 3
Introduction
What are the main reasons for technical objects withinan asset management system ?
Administration of technical dataLink to the accounting worldLink to document management systemLink to process control systems - the SCADA interface Link to geographical information systems (GIS) Organizational embedding and structuring of assetsLink to planning dataHistorical data and analysis
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 4
Type of Technical Objects in T&D
Typical technical objects in transmission and distribution:
Substations, lines, transformer stations, transformers, circuits, gas transfer stations, gas accumulators, pipes, wires, ...
Technical objects can be classified in two groups:“Point oriented” objects– Transformers, stations, poles, ...
“Line oriented” objects– Circuits, pipes, grids, sections, ...
Mapping into the ERP systemPhysical model: “Real world” objects.Logical model: Connectivity, Topology of a grid.
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 5
Agenda
Introduction
Type of Technical Objects in T&D Equipments and Functional LocationsOthers
Structuring
Classification System
IS-U Requirements
Processes
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 6
Equipment: Definition
Individual physical object to be maintained as anautonomous unit
Equipment Means of production
Means of transport
Test equipment
Production resources/tools
Customer devices
Buildings, property
Systems, system parts
Vehicles
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 7
Criteria for Equipment Master Record
For what purpose is a piece of equipment created?
Management of individual data
Recording of maintenance tasks
Object-based recording of costs
Evaluation of technical data
Recording of usage times
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 8
Equipment Master Record
Equipment usage
ClassificationGeneral
Location
Organization
Structure
Documents / technical drawings
Multilingual texts
Address / partner
Measuring points / counters
Permits
Internal notes
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 9
Creating an Equipment
Create Equipment
Without reference
With equipment as reference
With material as reference
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 10
Documenting Changes
Equipment Master Record
Location data
Cost Center 4300
Cost Center 4110
ChangeDocument
Action LogChanged by date
field old/new
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 11
Equipment and Asset Accounting
Equipment Master Record
Location data Asset number
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 12
Functional Locations
Functional location: Multi-level, hierarchical structure,organized according to …
Spatial Criteria
Technical Criteria
Functional Criteria
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 13
Criteria for Functional Locations
When do you create a functional location?
Execution of maintenance tasks
Documentation of maintenance tasks
Data collection over longer periodsof time
Cost monitoring
How do usage conditions influencethe likelihood of damage to theinstalled aggregates?
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 14
Master Record Structure of the Functional Location
Equipment usage
General
Location
Organization
Structure
Classification
Documents / technical drawings
Multilingual texts
Address / partner
Measuring points / counters
Permits
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 15
Creating Functional Locations
CreateFunctional Locations
Without reference
With functional locationas reference
with reference functional location as reference
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 16
List Entry of Location Structures
Previously entered branch
Z
ZA
ZA1 ZA2
ZA11 ZA12
Location with additional branch
Z
ZA
ZA1 ZA2
ZA11 ZA12
ZB
ZB1 ZB2
ZB11 ZB12
Createsimilarstructure
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 17
Reference Functional Location
Reference Location
Maintenance Data
Classification
Documents / technical drawings
Multilingual texts
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 18
Data Transfer
Reference Location Functional LocationsStructuring dataPlanning dataLocation dataAccount assignment data
Structuring dataPlanning data
Data Transferfrom referencelocation
Individualentry ofdata
HierarchicalData Transfer
HierarchicalData Transfer
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 19
Hierarchical Data Transfer
Reference functional locations
RFL
Data transferby system rules
Individually defineddata transfer
Functional locations
Hierarchicaldata transfer
Withinhierarchicalobjectstructures
Equipment andequipment hierarchies
Equipment
EquipmentEquipment
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 20
Horizontal Data Transfer
Data transferby system rules
Reference functional locations
RFL
Functional locations
Hierarchicaldata transfer
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 21
Data Origin
Equipment
FunctionalLocation
Cost Center
Room
Data origin display
Data origin change
Reference functional location Functional location Equipment
Individual maintenanceFrom superior location
Individual maintenanceFrom superior locationFrom ref. functional location
Individual maintenanceFrom superior equipmentFrom functional location
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 22
Other Types of Technical Objects I
Material Master RecordA data record containing all the basic information required to manage a material.This data is sorted according to various criteria including data of a descriptive nature (such as size, dimension and weight) and datawith a control function (such as material type and industry sector). In addition to this data, which can be directly maintained by the user, it also contains data that is automatically updated by thesystem (such as stock levels).
Serial NumberA number you give to an item of material in addition to the material number, to differentiate that item from other items of the material.The combination of material and serial number is unique.
Bill of Material (BOM)A complete, structured list of the components that make up an object. The list contains the description, the quantity, and unit of measure. The components are known as BOM items.
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 23
Other Types of Technical Objects II
Object LinkThe linking of two technical objects through a third technical object.An object link can only consist of objects in the same object category, that is, a piece of equipment can only be linked with another piece of equipment and a functional location with another functional location. If the object that forms the connection is managed in the system as a piece of equipment or a functional location, then two pieces of equipment can only be linked by a piece of equipment and two functional locations by a functional location.Using object links, you can build object networks and structure your technical systems horizontally. This lets you represent andevaluate dependencies between objects.
Installed BaseAn individual hierarchy for an actual device, machine or system.An IBase can be used to group together all devices of a similar type for each customer.
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 24
Agenda
Introduction
Type of Technical Objects in T&D Equipments and Functional LocationsOthers
Structuring
Classification System
IS-U Requirements
Processes
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 25
Classification System
Lifting heightin meters
Pumps
Power requirement in
WattsConnection type
Class
Characteristics
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 26
Classification System
Class Hierarchy
Pumps
Machines
Motors Gears
Turbine pumps Reciprocating pumps Water pumps
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 27
Characteristic Inheritance
Pumps
Machines
Motors Gears
Turbine pumps Reciprocating pumps Water pumps
PowerrequirementLifting height
Connection typeTransportation capacityLifting height
Characteristic:Lifting height
Power requirement+ Lifting height
Connection typeTransportationcapacity+ Lifting height
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 28
Classifying Technical Objects
Pumps
Machines
Motors Gears
Turbine pumps
Reciprocating pumps Water pumps
Connection type
Transportation capacity
Lifting height
Connection type
Transportationcapacity
+ Lifting height
Equipment isassigned to class
Characteristicsare available atobject
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 29
Agenda
Introduction
Type of Technical Objects in T&D Equipments and Functional LocationsOthers
Classification System
Structuring
IS-U Presettings
Processes
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 30
Equipment Hierarchy
Level 0
Superior
Fleet Object
Level 1Sub-equipment: Drive Unit
Level 2Sub-equipment: Gears
Level 3Sub-equipment: Shaft
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 31
Equipment
Equipment Hierarchy and Functional Location
Equipment
Equipment
Functional Location
Create first an equipment
hierarchy
Equipment
Equipment
EquipmentEquipment
Equipment
Equipment
install top equipment on
functional location
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 32
Structuring Technical Systems
FL 1
FL 11 FL 12
Material I
Material II
Assembly
FL 111 FL 112
Equipment Equipment
Equipment Equipment
BOM
BOM MaterialBOM
MaterialBOM
Material I
Material II
Assembly
Document
Assembly
Material
Material
Document
Assembly
Material
Material
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 33
Basic Elements for the Structuring of Assets
EquipmentHierarchy
Funct. LocationHierarchy
InstalledEquipment
Assembly BoM
EquipmentBoM
Equipment
Equipment
Spare Parts
Assembly
Funct. Location
Funct. Location
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 34
Installation of Equipments on Functional Locations
usage listdate from to Func. Loc.
12.03.91 -16.08.95 : LAB10AA00516.08.95 -03.06.97 : LAB40AA03203.06.97 -15.10.99 : LAB20AA01015.10.99- LAB10AA005
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 35
Equipment
Equipment Hierarchy and Functional Location
Equipment
Equipment Structure of equipment hierarchy
Equipment
Equipment
EquipmentEquipment
Equipment
Equipment
Installation
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 36
Example: Structuring for a Gas Transfer Station
(gas transfer station)Gas Transfer Station No. 471
reducing valve DN 500 DN 400 => valve R853/19 (S487/11)
control and meter section 1
ball valve DN 500 PN 100
TWMT 01
1000645RVAL 10
GST 471
CMS 02
DLSP 01
control and meter section 2
dust and liquid separator DN 400 PN 100turbine wheel meter DN 300 PN 100combustion chamber meter DN 300 PN 100blowoff valve DN 50 PN 100safety valve DN 300 PN 100preheater DN 300 PN 100control valve DN 300 PN 100ball valve DN 400 PN 100
SAV 13
PHEA 01
CVAL 14
BVAL 15
CCMT 01
BVAL 12
CMS 01
BVAL 11
Equipment Functional Location
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 37
Example: Structuring for a Transformer Station
(sub stations, transformers)
ST 435
ST 435-A
ST 435-B
ST 435-A-1
ST 435-A-2
1000645
1000839
....
.............
Substation No. 435
conductor rail A
transformer field 1
transformer 400 kVA... assemblies and spare parts....
transformer field 2
transformer 300 kVA... assemblies and spare parts
conductor rail B
Equipment Functional Location
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 38
Example: Structuring for a Line System
(line systems)
....
L 114
L 114 02
........
Line No. 114
200456
203478
201569
P 188
P 187
L 114 01 section 01 ( 0 ... 14.7 km )
pole no. 187
pole top
crossarm type XA 24
isolators type IS 45/9
pole no. 188... assemblies and spare parts
section 02 ( 14.7 ... 26.8 km)
Equipment Functional LocationAssembly
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 39
Example: Structuring for Electrical Grid
(logical structure)
High Voltage Area 008
sub station no. 114
circuit A 13
sub station no. 117
circuit A 14
circuit A 13 section 1
transformer station No. 1274
circuit A 13 section 2
transformer 400 kVA... assemblies and spare parts
.............
30089654
H 008
ST 117
CC A13
CC A14
CC A13-1
CC A13-2
TS 1274
ST 114
....
....
Equipment Functional Location
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 40
Example: Structuring for a Supply Grid
electricity supply grid
Substation ST 435 Substation ST 571
Field01
Field02
Field 03
Field01
Field02
Field 03
Field01
Field02
Field 03
Substation ST 768
Line No. 187
Line No. 189
Line No. 186
Line No. 188
line system with sections
Object link to connect two systems with different hierarchy
substation withtransformer fields
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 41
Example: Structuring for a Gas Supply Grid
municipal gas supply grid
medium pressureEast
G-XXX
Gas transferstations
object links withdifferent grid ids
medium pressure North
medium pressure South
high pressure East
G-RIE
G-WEI
G-HAM
G-TEN
G-VIE
G-CAS
G-SAL
G-SIE
G-CAR
G-HIL
G-WER
G-HAR
G-KORG-
SIN
G-HEI
G-BRE
G-ESS
G-HAT
high pressure West
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 42
Agenda
Introduction
Type of Technical Objects in T&D Equipments and Functional LocationsOthers
Structuring
Classification System
IS-U Requirements
Processes
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 43
IS-U Data Model
ConnectionObject
HouseConnection
TechnicalInstallation
DeviceLocation
Device(Meter)
Premise Grid
Equipment Functional Location
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 44
Agenda
Introduction
Type of Technical Objects in T&D Equipments and Functional LocationsOthers
Structuring
Classification System
IS-U Requirements
Processes
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 45
Processes
Example EAM standard processesNotification processing– First entry of a maintenance task
Order processing– Planning and execution of a maintenance task
Maintenance Planning (Preventive Maintenance)Work Scheduling– Task lists (e.g. specific for a special kind of technical object)
Example IS-U processes with service orders and/or service notifications
Repair ordersOutage handlingMeter reading order creationPeriodic inspections (German: “Hausinstallationskontrolle”)House connection processingDisconnection
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 46
Thanks for your attention –Any questions?
Ulrich ZaglerSolution Management EAMIBU Utilities
SAP AGDietmar-Hopp-Allee 1669190 Walldorf
F +49 (62 27) 7 – 41647E [email protected]
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 47
You can download the presentations as of March 7, 2007 www.sap.com/community/iuc2007
6th SAP INTERNATIONAL UTILITIES CONFERENCE 2007
© SAP AG 2007, 6th International Utilities Conference 2007 / K2_5 / 48
Copyright 2007 SAP AG. All Rights Reserved
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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.
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.
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.
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.