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.
Dear All,
I would like to employ your help and tap into this groups' vast knowledge of Maximo functionality. Here's my situation. Currently, my organization makes all equipment (assets) a location. An asset will be created, only if needed and then the asset is connected to itself, e.g., Location: GA1034-pump; Asset: 1234-pump. I am trying to develop a business case for implementing a more granular hierarchy system that is more inline with Maximo's best practices for developing this structure that meets the definition of location and asset.
How does our current location structure affect Maximo's functionality? Are there any consequences of doing it this way that may have a negative effect on other functionality within the system e.g., associate a system to a location, rotating assets, calibrations, meters, etc.? What are the benefits of implementing the new design? Should it just be left alone?
Thank you so much in advance for any thoughts or input.
Regards,
Paula
Paula,
This is a pet peeve of mine. Regardless of the industry, to fully utilize Maximo functionality, track asset costs, track maintenance history, and reliability, you have to use locations. Preferably physical locations, but even functional locations are ok.
I’m about to catch a flight, but if you are interested, I can send more later.
Regards
Glen Westling
Sent from my iPhone
> On Feb 23, 2018, at 8:09 PM, paula.schoenherr@yahoo.com [MAXIMO] <MAXIMO@yahoogroups.com> wrote:
>
> Dear All,
> I would like to employ your help and tap into this groups' vast knowledge of Maximo functionality. Here's my situation. Currently, my organization makes all equipment (assets) a location. An asset will be created, only if needed and then the asset is connected to itself, e.g., Location: GA1034-pump; Asset: 1234-pump. I am trying to develop a business case for implementing a more granular hierarchy system that is more inline with Maximo's best practices for developing this structure that meets the definition of location and asset.
> How does our current location structure affect Maximo's functionality? Are there any consequences of doing it this way that may have a negative effect on other functionality within the system e.g., associate a system to a location, rotating assets, calibrations, meters, etc.? What are the benefits of implementing the new design? Should it just be left alone?
>
>
> Thank you so much in advance for any thoughts or input.
>
>
> Regards,
> Paula
>
>
>
>
>
>
>
>
> ------------------------------------
> Posted by: paula.schoenherr@yahoo.com
> ------------------------------------
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com
> Leave : MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMO
> ------------------------------------
>
> Yahoo Groups Links
>
>
>
Hi Glen,
Yes I am interested in your information and experience with this issue. Currently we rely heavily on tribal knowledge and our workforce is getting younger with higher turnover and too much knowledge retires with the retiree.
Safe travels!
Paula
Sent from my iPhone
> On Feb 26, 2018, at 7:13 AM, Glen gwestcal@aol.com [MAXIMO] <MAXIMO@yahoogroups.com> wrote:
>
> Paula,
> This is a pet peeve of mine. Regardless of the industry, to fully utilize Maximo functionality, track asset costs, track maintenance history, and reliability, you have to use locations. Preferably physical locations, but even functional locations are ok.
> I’m about to catch a flight, but if you are interested, I can send more later.
>
> Regards
> Glen Westling
>
> Sent from my iPhone
>
> > On Feb 23, 2018, at 8:09 PM, paula.schoenherr@yahoo.com [MAXIMO] <MAXIMO@yahoogroups.com> wrote:
> >
> > Dear All,
> > I would like to employ your help and tap into this groups' vast knowledge of Maximo functionality. Here's my situation. Currently, my organization makes all equipment (assets) a location. An asset will be created, only if needed and then the asset is connected to itself, e.g., Location: GA1034-pump; Asset: 1234-pump. I am trying to develop a business case for implementing a more granular hierarchy system that is more inline with Maximo's best practices for developing this structure that meets the definition of location and asset.
> > How does our current location structure affect Maximo's functionality? Are there any consequences of doing it this way that may have a negative effect on other functionality within the system e.g., associate a system to a location, rotating assets, calibrations, meters, etc.? What are the benefits of implementing the new design? Should it just be left alone?
> >
> >
> > Thank you so much in advance for any thoughts or input.
> >
> >
> > Regards,
> > Paula
> >
> >
> >
> >
> >
> >
> >
> >
> > ------------------------------------
> > Posted by: paula.schoenherr@yahoo.com
> > ------------------------------------
> >
> > Email addresses you might need:
> > Posting: MAXIMO@yahoogroups.com
> > Join : MAXIMO-subscribe@yahoogroups.com
> > Leave : MAXIMO-unsubscribe@yahoogroups.com
> > Cry : MAXIMO-owner@yahoogroups.com
> > Group : http://groups.yahoo.com/group/MAXIMO
> > ------------------------------------
> >
> > Yahoo Groups Links
> >
> >
> >
>
>
Paula,
I’m headed home now, so I will see what I can do for you tomorrow.
Regards
Glen Westling
Sent from my iPhone
> On Feb 26, 2018, at 1:32 PM, Paula Schoenherr paula.schoenherr@yahoo.com [MAXIMO] <MAXIMO@yahoogroups.com> wrote:
>
> Hi Glen,
> Yes I am interested in your information and experience with this issue. Currently we rely heavily on tribal knowledge and our workforce is getting younger with higher turnover and too much knowledge retires with the retiree.
>
> Safe travels!
> Paula
>
>
>
> Sent from my iPhone
>
>> On Feb 26, 2018, at 7:13 AM, Glen gwestcal@aol.com [MAXIMO] <MAXIMO@yahoogroups.com> wrote:
>>
>> Paula,
>> This is a pet peeve of mine. Regardless of the industry, to fully utilize Maximo functionality, track asset costs, track maintenance history, and reliability, you have to use locations. Preferably physical locations, but even functional locations are ok.
>> I’m about to catch a flight, but if you are interested, I can send more later.
>>
>> Regards
>> Glen Westling
>>
>> Sent from my iPhone
>>
>>> On Feb 23, 2018, at 8:09 PM, paula.schoenherr@yahoo.com [MAXIMO] <MAXIMO@yahoogroups.com> wrote:
>>>
>>> Dear All,
>>> I would like to employ your help and tap into this groups' vast knowledge of Maximo functionality. Here's my situation. Currently, my organization makes all equipment (assets) a location. An asset will be created, only if needed and then the asset is connected to itself, e.g., Location: GA1034-pump; Asset: 1234-pump. I am trying to develop a business case for implementing a more granular hierarchy system that is more inline with Maximo's best practices for developing this structure that meets the definition of location and asset.
>>> How does our current location structure affect Maximo's functionality? Are there any consequences of doing it this way that may have a negative effect on other functionality within the system e.g., associate a system to a location, rotating assets, calibrations, meters, etc.? What are the benefits of implementing the new design? Should it just be left alone?
>>>
>>>
>>> Thank you so much in advance for any thoughts or input.
>>>
>>>
>>> Regards,
>>> Paula
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------
>>> Posted by: paula.schoenherr@yahoo.com
>>> ------------------------------------
>>>
>>> Email addresses you might need:
>>> Posting: MAXIMO@yahoogroups.com
>>> Join : MAXIMO-subscribe@yahoogroups.com
>>> Leave : MAXIMO-unsubscribe@yahoogroups.com
>>> Cry : MAXIMO-owner@yahoogroups.com
>>> Group : http://groups.yahoo.com/group/MAXIMO
>>> ------------------------------------
>>>
>>> Yahoo Groups Links
>>>
>>>
>>>
>>
>>
>
>
>
>
>
>
> ------------------------------------
> Posted by: Paula Schoenherr <paula.schoenherr@yahoo.com>
> ------------------------------------
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com
> Leave : MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMO
> ------------------------------------
>
> Yahoo Groups Links
>
>
>