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.
I am trying to find a good way to explain the difference between and asset and a location. I have a customer who wants to list an office as an asset in Maximo. In my view, the office is a piece of real estate that assets can occupy. I typically think of an asset as something that can potentially change location. An office within an office building doesn't often get uprooted and physically moved to some other area. Does anyone have a clear definition I can use to explain to a customer the difference between an asset and a location?
Hi,
The short answer to your room question is yes a room can be an asset. Whetehr the asset can be moved or not does not matter. We have our buildings and some of the rooms as assets since we have to do work on them.
You're going to get some different definitions but here's how we use locations and assets. This is primarily a manufacturing environment.
Bascially assets are all of the equipment and locations are buckets used to group assets in the same physical area or of the same function or of the same asset type.
We list as assets any individual piece of euipment. That's down to the photoeyes, motors, pumps and up through the fillers and rinsers and air handlers and ammonia compressors. Individual bearings and belts are not listed but in very large industrial applications they do list some of the very expensive beraings and belts as assets.
For our production lines we mostly use physical locations. For instance we have one production line broken down into just seven locations. This allows us to track work and expenses to those locations.
For our ammonia refrigeration system (same asset type or function) we have a location hierarchy just for that so we can track work and expenses there. Since most of this work is done by outside labor it makes it esy to see what work they have done and still have left.
For the electrical system (same function) the location hierarchy there lets us track downstream outages if we work on a part of the electrical system.
So you can use the locations in the most logical way for your environment. But you should keep it as simple as possible. I have heard that some users have a one to one relationship between assets and locations. That would usually only be done where you had to track rotating assets into and out of locations.
You should lay out with your users how the locations and asset hierarchy will be structured before you start putting in the assets and locations. Although in version 7.x it's much easier to fix these than it was in earlier versions.
Dave Bone
Ocean Spray Cranberries
--- In MAXIMO@yahoogroups.com, "mutss1" <mutss1@...> wrote:
>
> I am trying to find a good way to explain the difference between and asset and a location. I have a customer who wants to list an office as an asset in Maximo. In my view, the office is a piece of real estate that assets can occupy. I typically think of an asset as something that can potentially change location. An office within an office building doesn't often get uprooted and physically moved to some other area. Does anyone have a clear definition I can use to explain to a customer the difference between an asset and a location?
>
At Grifols NC, we always use the analogy of the location being a parking
space and the asset being the car that sits in the spot. All of our assets
have locations, it is a one to one relationship. Our former home grown
maintenance database had smart numbers for equipment, and these became the
location numbers. It was simply not an option to update all of our drawings
with new "dumb" asset numbers.
However, all of our buildings and rooms are simply locations with no asset
associated. For work on those locations, we only write the work order to the
location. What is the reason they want to make it an asset?
Kevin J. Wertz
Grifols Inc
Clayton NC
On Tue, Sep 20, 2011 at 12:08 PM, in2data <in2data@yahoo.com> wrote:
> **
>
>
> Hi,
>
> The short answer to your room question is yes a room can be an asset.
> Whetehr the asset can be moved or not does not matter. We have our buildings
> and some of the rooms as assets since we have to do work on them.
>
> You're going to get some different definitions but here's how we use
> locations and assets. This is primarily a manufacturing environment.
>
> Bascially assets are all of the equipment and locations are buckets used to
> group assets in the same physical area or of the same function or of the
> same asset type.
>
> We list as assets any individual piece of euipment. That's down to the
> photoeyes, motors, pumps and up through the fillers and rinsers and air
> handlers and ammonia compressors. Individual bearings and belts are not
> listed but in very large industrial applications they do list some of the
> very expensive beraings and belts as assets.
>
> For our production lines we mostly use physical locations. For instance we
> have one production line broken down into just seven locations. This allows
> us to track work and expenses to those locations.
>
> For our ammonia refrigeration system (same asset type or function) we have
> a location hierarchy just for that so we can track work and expenses there.
> Since most of this work is done by outside labor it makes it esy to see what
> work they have done and still have left.
>
> For the electrical system (same function) the location hierarchy there lets
> us track downstream outages if we work on a part of the electrical system.
>
> So you can use the locations in the most logical way for your environment.
> But you should keep it as simple as possible. I have heard that some users
> have a one to one relationship between assets and locations. That would
> usually only be done where you had to track rotating assets into and out of
> locations.
>
> You should lay out with your users how the locations and asset hierarchy
> will be structured before you start putting in the assets and locations.
> Although in version 7.x it's much easier to fix these than it was in earlier
> versions.
>
> Dave Bone
> Ocean Spray Cranberries
>
>
> --- In MAXIMO@yahoogroups.com, "mutss1" <mutss1@...> wrote:
> >
> > I am trying to find a good way to explain the difference between and
> asset and a location. I have a customer who wants to list an office as an
> asset in Maximo. In my view, the office is a piece of real estate that
> assets can occupy. I typically think of an asset as something that can
> potentially change location. An office within an office building doesn't
> often get uprooted and physically moved to some other area. Does anyone have
> a clear definition I can use to explain to a customer the difference between
> an asset and a location?
> >
>
>
>
It's an ignorance issue. They are mixing the concept of physical locations with systems. For example, a hydraulic unit asset should be associated to a PRESS location. They want to associated it to a hydraulic system location. They don't understand that one system, in this case the Primary system, represents an physical hierarchy and that a seperarte system should be created to associated hydraulic components. I'm attempting to educate them on this subject and want to be as clear as possible when defining the differences between assets, locations, systems, and their relationships.
--- In MAXIMO@yahoogroups.com, Kevin Wertz <wertzee@...> wrote:
>
> At Grifols NC, we always use the analogy of the location being a parking
> space and the asset being the car that sits in the spot. All of our assets
> have locations, it is a one to one relationship. Our former home grown
> maintenance database had smart numbers for equipment, and these became the
> location numbers. It was simply not an option to update all of our drawings
> with new "dumb" asset numbers.
>
> However, all of our buildings and rooms are simply locations with no asset
> associated. For work on those locations, we only write the work order to the
> location. What is the reason they want to make it an asset?
>
> Kevin J. Wertz
> Grifols Inc
> Clayton NC
>
> On Tue, Sep 20, 2011 at 12:08 PM, in2data <in2data@...> wrote:
>
> > **
> >
> >
> > Hi,
> >
> > The short answer to your room question is yes a room can be an asset.
> > Whetehr the asset can be moved or not does not matter. We have our buildings
> > and some of the rooms as assets since we have to do work on them.
> >
> > You're going to get some different definitions but here's how we use
> > locations and assets. This is primarily a manufacturing environment.
> >
> > Bascially assets are all of the equipment and locations are buckets used to
> > group assets in the same physical area or of the same function or of the
> > same asset type.
> >
> > We list as assets any individual piece of euipment. That's down to the
> > photoeyes, motors, pumps and up through the fillers and rinsers and air
> > handlers and ammonia compressors. Individual bearings and belts are not
> > listed but in very large industrial applications they do list some of the
> > very expensive beraings and belts as assets.
> >
> > For our production lines we mostly use physical locations. For instance we
> > have one production line broken down into just seven locations. This allows
> > us to track work and expenses to those locations.
> >
> > For our ammonia refrigeration system (same asset type or function) we have
> > a location hierarchy just for that so we can track work and expenses there.
> > Since most of this work is done by outside labor it makes it esy to see what
> > work they have done and still have left.
> >
> > For the electrical system (same function) the location hierarchy there lets
> > us track downstream outages if we work on a part of the electrical system.
> >
> > So you can use the locations in the most logical way for your environment.
> > But you should keep it as simple as possible. I have heard that some users
> > have a one to one relationship between assets and locations. That would
> > usually only be done where you had to track rotating assets into and out of
> > locations.
> >
> > You should lay out with your users how the locations and asset hierarchy
> > will be structured before you start putting in the assets and locations.
> > Although in version 7.x it's much easier to fix these than it was in earlier
> > versions.
> >
> > Dave Bone
> > Ocean Spray Cranberries
> >
> >
> > --- In MAXIMO@yahoogroups.com, "mutss1" <mutss1@> wrote:
> > >
> > > I am trying to find a good way to explain the difference between and
> > asset and a location. I have a customer who wants to list an office as an
> > asset in Maximo. In my view, the office is a piece of real estate that
> > assets can occupy. I typically think of an asset as something that can
> > potentially change location. An office within an office building doesn't
> > often get uprooted and physically moved to some other area. Does anyone have
> > a clear definition I can use to explain to a customer the difference between
> > an asset and a location?
> > >
> >
> >
> >
>
>
>
>
PAS 55 defines this specific type of asset as "plant, machinery, property, buildings, vehicles, and other items and related systems that have a distinct and quantifiable business function or service". This sets clearly of what an asset is.
On the otherhand, location is a space where are we placed our assets. Location can exist physically or virtually depending on how see, map-out, categorize, use, etc. them to place physical assets. However, going back to the basic definition of asset, a physical location can also be an asset, say a "storeroom" where we place our spareparts and other stocks, "the engine room of the ship", "office" where we do our specific business functions and houses the furniture and equipment, etc.
I have assisted in the implementation at about 20 differrent sites and this always comes up. My practice has been to remind them this is being set up to send maintenance personnel to do their jobs. A location would be where you are sending the person and the asset is the equipment that they are completing the maintenance. In some cases the location and the asset may be the same and would exist as both OR because maintenance can be completed against a location an asset does not need to be identified.
--- In MAXIMO@yahoogroups.com, Toribio Noel Ilao <noel_ilao@...> wrote:
>
> PAS 55 defines this specific type of asset as "plant, machinery, property, buildings, vehicles, and other items and related systems that have a distinct and quantifiable business function or service". This sets clearly of what an asset is.
> Â
> On the otherhand, location is a space where are we placed our assets. Location can exist physically or virtually depending on how see, map-out, categorize, use, etc. them to place physical assets. However, going back to the basic definition of asset, a physical location can also be an asset, say a "storeroom" where we place our spareparts and other stocks, "the engine room of the ship", "office" where we do our specific business functions and houses the furniture and equipment, etc.
> Â
> From the very beginning, we need to define what an asset is and what are considered assets.
>
>
> ________________________________
> From: mutss1 <mutss1@...>
> To: MAXIMO@yahoogroups.com
> Sent: Saturday, October 1, 2011 12:22 AM
> Subject: [MAXIMO List] Re: Location vs Asset
>
>
> Â
>
> It's an ignorance issue. They are mixing the concept of physical locations with systems. For example, a hydraulic unit asset should be associated to a PRESS location. They want to associated it to a hydraulic system location. They don't understand that one system, in this case the Primary system, represents an physical hierarchy and that a seperarte system should be created to associated hydraulic components. I'm attempting to educate them on this subject and want to be as clear as possible when defining the differences between assets, locations, systems, and their relationships.
>
> --- In MAXIMO@yahoogroups.com, Kevin Wertz <wertzee@> wrote:
> >
> > At Grifols NC, we always use the analogy of the location being a parking
> > space and the asset being the car that sits in the spot. All of our assets
> > have locations, it is a one to one relationship. Our former home grown
> > maintenance database had smart numbers for equipment, and these became the
> > location numbers. It was simply not an option to update all of our drawings
> > with new "dumb" asset numbers.
> >
> > However, all of our buildings and rooms are simply locations with no asset
> > associated. For work on those locations, we only write the work order to the
> > location. What is the reason they want to make it an asset?
> >
> > Kevin J. Wertz
> > Grifols Inc
> > Clayton NC
> >
> > On Tue, Sep 20, 2011 at 12:08 PM, in2data <in2data@> wrote:
> >
> > > **
> > >
> > >
> > > Hi,
> > >
> > > The short answer to your room question is yes a room can be an asset.
> > > Whetehr the asset can be moved or not does not matter. We have our buildings
> > > and some of the rooms as assets since we have to do work on them.
> > >
> > > You're going to get some different definitions but here's how we use
> > > locations and assets. This is primarily a manufacturing environment.
> > >
> > > Bascially assets are all of the equipment and locations are buckets used to
> > > group assets in the same physical area or of the same function or of the
> > > same asset type.
> > >
> > > We list as assets any individual piece of euipment. That's down to the
> > > photoeyes, motors, pumps and up through the fillers and rinsers and air
> > > handlers and ammonia compressors. Individual bearings and belts are not
> > > listed but in very large industrial applications they do list some of the
> > > very expensive beraings and belts as assets.
> > >
> > > For our production lines we mostly use physical locations. For instance we
> > > have one production line broken down into just seven locations. This allows
> > > us to track work and expenses to those locations.
> > >
> > > For our ammonia refrigeration system (same asset type or function) we have
> > > a location hierarchy just for that so we can track work and expenses there.
> > > Since most of this work is done by outside labor it makes it esy to see what
> > > work they have done and still have left.
> > >
> > > For the electrical system (same function) the location hierarchy there lets
> > > us track downstream outages if we work on a part of the electrical system.
> > >
> > > So you can use the locations in the most logical way for your environment.
> > > But you should keep it as simple as possible. I have heard that some users
> > > have a one to one relationship between assets and locations. That would
> > > usually only be done where you had to track rotating assets into and out of
> > > locations.
> > >
> > > You should lay out with your users how the locations and asset hierarchy
> > > will be structured before you start putting in the assets and locations.
> > > Although in version 7.x it's much easier to fix these than it was in earlier
> > > versions.
> > >
> > > Dave Bone
> > > Ocean Spray Cranberries
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com, "mutss1" <mutss1@> wrote:
> > > >
> > > > I am trying to find a good way to explain the difference between and
> > > asset and a location. I have a customer who wants to list an office as an
> > > asset in Maximo. In my view, the office is a piece of real estate that
> > > assets can occupy. I typically think of an asset as something that can
> > > potentially change location. An office within an office building doesn't
> > > often get uprooted and physically moved to some other area. Does anyone have
> > > a clear definition I can use to explain to a customer the difference between
> > > an asset and a location?
> > > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
>
>
Thats the simplest definition Ive seen I like it.
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
roy.cline
Sent: October-03-11 7:01 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Location vs Asset
I have assisted in the implementation at about 20 differrent sites and this
always comes up. My practice has been to remind them this is being set up to
send maintenance personnel to do their jobs. A location would be where you
are sending the person and the asset is the equipment that they are
completing the maintenance. In some cases the location and the asset may be
the same and would exist as both OR because maintenance can be completed
against a location an asset does not need to be identified.
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , Toribio
Noel Ilao <noel_ilao@...> wrote:
>
> PAS 55 defines this specific type of asset as "plant, machinery, property,
buildings, vehicles, and other items and related systems that have a
distinct and quantifiable business function or service". This sets clearly
of what an asset is.
> Â
> On the otherhand, location is a space where are we placed our assets.
Location can exist physically or virtually depending on how see, map-out,
categorize, use, etc. them to place physical assets. However, going back
to the basic definition of asset, a physical location can also be an asset,
say a "storeroom" where we place our spareparts and other stocks, "the
engine room of the ship", "office" where we do our specific business
functions and houses the furniture and equipment, etc.
> Â
> From the very beginning, we need to define what an asset is and what are
considered assets.
>
>
> ________________________________
> From: mutss1 <mutss1@...>
> To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> Sent: Saturday, October 1, 2011 12:22 AM
> Subject: [MAXIMO List] Re: Location vs Asset
>
>
> Â
>
> It's an ignorance issue. They are mixing the concept of physical locations
with systems. For example, a hydraulic unit asset should be associated to a
PRESS location. They want to associated it to a hydraulic system location.
They don't understand that one system, in this case the Primary system,
represents an physical hierarchy and that a seperarte system should be
created to associated hydraulic components. I'm attempting to educate them
on this subject and want to be as clear as possible when defining the
differences between assets, locations, systems, and their relationships.
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , Kevin
Wertz <wertzee@> wrote:
> >
> > At Grifols NC, we always use the analogy of the location being a parking
> > space and the asset being the car that sits in the spot. All of our
assets
> > have locations, it is a one to one relationship. Our former home grown
> > maintenance database had smart numbers for equipment, and these became
the
> > location numbers. It was simply not an option to update all of our
drawings
> > with new "dumb" asset numbers.
> >
> > However, all of our buildings and rooms are simply locations with no
asset
> > associated. For work on those locations, we only write the work order to
the
> > location. What is the reason they want to make it an asset?
> >
> > Kevin J. Wertz
> > Grifols Inc
> > Clayton NC
> >
> > On Tue, Sep 20, 2011 at 12:08 PM, in2data <in2data@> wrote:
> >
> > > **
> > >
> > >
> > > Hi,
> > >
> > > The short answer to your room question is yes a room can be an asset.
> > > Whetehr the asset can be moved or not does not matter. We have our
buildings
> > > and some of the rooms as assets since we have to do work on them.
> > >
> > > You're going to get some different definitions but here's how we use
> > > locations and assets. This is primarily a manufacturing environment.
> > >
> > > Bascially assets are all of the equipment and locations are buckets
used to
> > > group assets in the same physical area or of the same function or of
the
> > > same asset type.
> > >
> > > We list as assets any individual piece of euipment. That's down to the
> > > photoeyes, motors, pumps and up through the fillers and rinsers and
air
> > > handlers and ammonia compressors. Individual bearings and belts are
not
> > > listed but in very large industrial applications they do list some of
the
> > > very expensive beraings and belts as assets.
> > >
> > > For our production lines we mostly use physical locations. For
instance we
> > > have one production line broken down into just seven locations. This
allows
> > > us to track work and expenses to those locations.
> > >
> > > For our ammonia refrigeration system (same asset type or function) we
have
> > > a location hierarchy just for that so we can track work and expenses
there.
> > > Since most of this work is done by outside labor it makes it esy to
see what
> > > work they have done and still have left.
> > >
> > > For the electrical system (same function) the location hierarchy there
lets
> > > us track downstream outages if we work on a part of the electrical
system.
> > >
> > > So you can use the locations in the most logical way for your
environment.
> > > But you should keep it as simple as possible. I have heard that some
users
> > > have a one to one relationship between assets and locations. That
would
> > > usually only be done where you had to track rotating assets into and
out of
> > > locations.
> > >
> > > You should lay out with your users how the locations and asset
hierarchy
> > > will be structured before you start putting in the assets and
locations.
> > > Although in version 7.x it's much easier to fix these than it was in
earlier
> > > versions.
> > >
> > > Dave Bone
> > > Ocean Spray Cranberries
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ,
"mutss1" <mutss1@> wrote:
> > > >
> > > > I am trying to find a good way to explain the difference between and
> > > asset and a location. I have a customer who wants to list an office as
an
> > > asset in Maximo. In my view, the office is a piece of real estate that
> > > assets can occupy. I typically think of an asset as something that can
> > > potentially change location. An office within an office building
doesn't
> > > often get uprooted and physically moved to some other area. Does
anyone have
> > > a clear definition I can use to explain to a customer the difference
between
> > > an asset and a location?
> > > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
>
>