This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hi,
One of my scientific division wants to create Asset Hierarchy, same way
there is for Location Hierarchy, so that it would give them a clear view of
the Assets and its child assets.
eg., MainAsset1, Controller, ChildAsset1, ChildAsset2, SubChildAsset1,
SubChildAsset2, SubChildAsset3, SubChildAsset4, SubChildAsset5,
SubChildAsset6
MainAsset2, Controller, ChildAsset3, ChildAsset4, SubChildAsset7,
SubChildAsset8, SubChildAsset9, SubChildAsset10, SubChildAsset11,
SubChildAsset12
Controller is a common asset in both the hierarchies.
MainAsset1
|
|________Controller
|
|________ChildAsset1
| |
| |_________SubChildAsset1
| |_________SubChildAsset2
| |_________SubChildAsset3
|
|________ChildAsset2
|
|_________SubChildAsset4
|_________SubChildAsset5
|_________SubChildAsset6
MainAsset2
|
|________Controller
|
|________ChildAsset3
| |
| |_________SubChildAsset7
| |_________SubChildAsset8
| |_________SubChildAsset9
|
|________ChildAsset4
|
|_________SubChildAsset10
|_________SubChildAsset11
|_________SubChildAsset12
thanks,
Praveen
Hi,
You can have both a location and asset hierarchy. In fact you should have both.
Locations and assets are not a one to one relationship. You use locations to group like assets based on how you want the hierarchy to work. For instance for a production line we have six locations based on the physical location. Location 1 is the beginning of the line and Location 6 is the end of the line. Then we place assets in those locations based on where the asset is physically located.
We have a bottle filler asset in location 3. Then that asset has several sub-assets like in feed, filler valve assembly and out feed. Those sub-assets also have sub-assets. For instance the filler valve assembly has a sub-asset for each valve asset since we track rebuilds and actually have rebuild PMs for each valve.
For our blending area a blend tank is one location and all of the assets like pumps, motors, sensors and valves are in that location.
For our HVAC we actually have a location hierarchy that includes all of the HVAC assets. Again the locations tell us where the location is physically like warehouse roof, office roof and blending roof. Then the assets are placed there.
You also can make systems so if you have an electrical system you can easily determine of you turn of a panel all of the downstream assets that will also be turned off.
If you sandbox this you can get it set up the way you want. You should definitely do this first in a sandbox.
Dave Bone
--- In MAXIMO@yahoogroups.com, Praveen M <praveen.muramalla@...> wrote:
>
> Hi,
>
> One of my scientific division wants to create Asset Hierarchy, same way
> there is for Location Hierarchy, so that it would give them a clear view of
> the Assets and its child assets.
>
> eg., MainAsset1, Controller, ChildAsset1, ChildAsset2, SubChildAsset1,
> SubChildAsset2, SubChildAsset3, SubChildAsset4, SubChildAsset5,
> SubChildAsset6
>
> MainAsset2, Controller, ChildAsset3, ChildAsset4, SubChildAsset7,
> SubChildAsset8, SubChildAsset9, SubChildAsset10, SubChildAsset11,
> SubChildAsset12
>
> Controller is a common asset in both the hierarchies.
>
> MainAsset1
> |
> |________Controller
> |
> |________ChildAsset1
> | |
> | |_________SubChildAsset1
> | |_________SubChildAsset2
> | |_________SubChildAsset3
> |
> |________ChildAsset2
> |
> |_________SubChildAsset4
> |_________SubChildAsset5
> |_________SubChildAsset6
>
>
> MainAsset2
> |
> |________Controller
> |
> |________ChildAsset3
> | |
> | |_________SubChildAsset7
> | |_________SubChildAsset8
> | |_________SubChildAsset9
> |
> |________ChildAsset4
> |
> |_________SubChildAsset10
> |_________SubChildAsset11
> |_________SubChildAsset12
>
> thanks,
> Praveen
>
>
>
>
Thanks Dave.
On Tue, Feb 28, 2012 at 9:34 AM, in2data <in2data@yahoo.com> wrote:
> **
>
>
> Hi,
>
> You can have both a location and asset hierarchy. In fact you should have
> both.
>
> Locations and assets are not a one to one relationship. You use locations
> to group like assets based on how you want the hierarchy to work. For
> instance for a production line we have six locations based on the physical
> location. Location 1 is the beginning of the line and Location 6 is the end
> of the line. Then we place assets in those locations based on where the
> asset is physically located.
>
> We have a bottle filler asset in location 3. Then that asset has several
> sub-assets like in feed, filler valve assembly and out feed. Those
> sub-assets also have sub-assets. For instance the filler valve assembly has
> a sub-asset for each valve asset since we track rebuilds and actually have
> rebuild PMs for each valve.
>
> For our blending area a blend tank is one location and all of the assets
> like pumps, motors, sensors and valves are in that location.
> For our HVAC we actually have a location hierarchy that includes all of
> the HVAC assets. Again the locations tell us where the location is
> physically like warehouse roof, office roof and blending roof. Then the
> assets are placed there.
>
> You also can make systems so if you have an electrical system you can
> easily determine of you turn of a panel all of the downstream assets that
> will also be turned off.
>
> If you sandbox this you can get it set up the way you want. You should
> definitely do this first in a sandbox.
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, Praveen M <praveen.muramalla@...> wrote:
> >
> > Hi,
> >
> > One of my scientific division wants to create Asset Hierarchy, same way
> > there is for Location Hierarchy, so that it would give them a clear view
> of
> > the Assets and its child assets.
> >
> > eg., MainAsset1, Controller, ChildAsset1, ChildAsset2, SubChildAsset1,
> > SubChildAsset2, SubChildAsset3, SubChildAsset4, SubChildAsset5,
> > SubChildAsset6
> >
> > MainAsset2, Controller, ChildAsset3, ChildAsset4, SubChildAsset7,
> > SubChildAsset8, SubChildAsset9, SubChildAsset10, SubChildAsset11,
> > SubChildAsset12
> >
> > Controller is a common asset in both the hierarchies.
> >
> > MainAsset1
> > |
> > |________Controller
> > |
> > |________ChildAsset1
> > | |
> > | |_________SubChildAsset1
> > | |_________SubChildAsset2
> > | |_________SubChildAsset3
> > |
> > |________ChildAsset2
> > |
> > |_________SubChildAsset4
> > |_________SubChildAsset5
> > |_________SubChildAsset6
> >
> >
> > MainAsset2
> > |
> > |________Controller
> > |
> > |________ChildAsset3
> > | |
> > | |_________SubChildAsset7
> > | |_________SubChildAsset8
> > | |_________SubChildAsset9
> > |
> > |________ChildAsset4
> > |
> > |_________SubChildAsset10
> > |_________SubChildAsset11
> > |_________SubChildAsset12
> >
> > thanks,
> > Praveen
> >
> >
> >
> >
>
>
>