Hi All,
I would like to know what is the point in creating Asset Trees in Computerized Maintanence systems. Is it about cost of maintanence? Or they just want to keep track of their assets in the form of a tree structure. What is the case in SAP? Any help is appreciated.

Best Regards,
Salim

In SAP R/3 you can structure your assets using the functional locations hierarchy and then link your equipments to the functional locations. At the equiment level you can also set a parent-child structure of several levels.

This Asset Tree funtion eases prepare costs analysis by grouping costs at any level.

For example, if you create a "equipment" named Compressed Air System and define it as the superior equipment of all the Air compressors, air recievers, and main lines. The air compressors at the same time are the superior equipment for their ancilliary equipments / instrument and so on. If you are required to answer how much were the maintenance costs for air compressing during last year the report is obtained in a breeze, rather to start grouping costs equipment by equipment.

Most good CMMS systems now include a logical parent/child type hierarchy similar to this.

Site ...
......... Department 1 ...
.......................... Process 1 ...
........................................ Asset 1
........................................ Asset 2
........................................ Asset 3

......... Department 2 ...
.......................... Process 1 ...
........................................ Asset 1
........................................ Asset 2
........................................ Asset 3


etc.

Clearly this structure makes it much easier to locate assets and to organise them within the CMMS system.

In my implementation of SAP R/3 we designed the functional locations in four levels and at the appropriate level the equipments are entered with the parent / child relationship.

Site
...Building100
......ProcessingArea1
......TechnicalArea1
.........MechanicalRoom101
.........MechanicalRoom207
............Boiler 100B001
...............BoilerFeedPump 100P023
..................Pressure Indicator 100P023PI001
...Building200
...etc.

Hi All,
Thank you for your replies. It helped a lot.

Best regards,
Salim

Basically, the asset hierarchy will enable users to do analysis vertically and horizontally of the asset structure.

The aim of creating an asset tree is to manage plant. I mean, you can determine the exact value of your plant with decreasing the value with time and you can use it to determine the MRP values. But antoher thing is to analyze the maintenance orders which have been created to every each equipment (pump, valve etc.) and revise the preventive maintenance data according to the collected maintenance data. I think this is the best...
I have only one question can we change a brach of our asset tree with maintenance order. If yes, can you tell me the transaction??

quote:

Originally posted by Eugene:
Site
...Building100
......ProcessingArea1
......TechnicalArea1
.........MechanicalRoom101
.........MechanicalRoom207
............Boiler 100B001
...............BoilerFeedPump 100P023
..................Pressure Indicator 100P023PI001
...Building200
...etc.

If the up diagram I try to represent a section of an asset tree with four levels of "Functional Locations" and then at the Functional Location "Mechanical Room 207" set a equipment with a several "child" equipment linked to it. The asset tree can be modified adding more functional locations and reorganizing the parent-child relationship of equipment to functional locations, or to functional location to parent functional location.
For example, if the previous Building100 is subject to a remodelation and it is divided in two processing areas a new functional location "ProcessingAreaZ" can be created with IL01, the previous child functional location TechnicalArea1 can be edited with IL02 and the new "ProcessingAreaZ" be set as the new superior functional location. With that change the whole branch from the TechnicalArea1 to the last pressure indicator was removed from one side of the tree and injerted on the new branch.

Changing functional location at the equipment record (IE02) has the same effect at the equipment level.

Is this of help?

This message has been edited. Last edited by: Eugene,

Can some one descirbe how they create Asset structure for network type of Asset that is not in hierarchy, example Elctrical grid or Water/oil pipelines etc.

Can't you put them in the hierarchy? I mean can't you put the electrical grid in the system as the top level like a department and put its children below it as shown above?

Hello Bryan,

I think dividing parts of network and putting in Parent - child relation can be done hypothatically.

But we need to put lot of assumptions. In a Network there could be many nodes and each node can have many branches and each branch gets terminated at two nodes.

I am not too sure how others have solved these type of issue. Is it fair to assume that we have to take set of nodes and branches and attach them to a hypothatical parent? In such case it may happen that a branch has one of its node belonging to a totally differant parent. When we see such structure in heirarchical view (partially) these node may not be visible.

Regards

Defining the hierarchy correctly is the real trick. Clearly I am nor familiar with your situation but I did have some involvement in HV distribution a few years ago and if it were me I think I would be creating the hierarchy based on location of the equipment.

We would like to know how to development asset register , I mean asset coding in SAP.

Now, we have some problem in our plant
Existing asset coding -> Functional Location = 100-P1 Bottom Feed Pump and Equipment = 1 (internal running number) Pump

Confusion to use and tracking when pump remove from one location to another location. Coding 100-P1 is fixed in location and everybody know this is equipment not location.

How to new design coding for tracking equipment install/dismantle?

Tag no like 100-P1 is fixed but the eqpt for this tag no can be dismantled and installed at another functloc.

quote:

Originally posted by BobV:
Can some one descirbe how they create Asset structure for network type of Asset that is not in hierarchy, example Elctrical grid or Water/oil pipelines etc.

Pipelines:
I have seen water systems where a parent/child structure is applied where the equipment (Tanks, Vessels, Pumps) are "parent" to those pipelines emerging from them. In other plants I have seen a simplified approach: for example process water distribuion lines are given a equipment number by building, floor or process area; not branch by branch.