MAXIMO TRAINING

Day 2 – 17th August 2022

Asset Management
What is Enterprise Asset Management (EAM)?

• Enterprise asset management (EAM) is a combination

of software, systems and services used to maintain and
control operational assets and equipment. The aim is to
optimize the quality and utilization of assets
throughout their lifecycle, increase productive uptime
and reduce operational costs.
• Enterprise asset management involves work
management, asset maintenance, planning and
scheduling, supply chain management and
environmental, health and safety (EHS) initiatives.

2
Why is EAM important?

• EAM is important because it helps organizations track, assess, manage and optimize asset quality and
reliability. Organizations of all kinds have hundreds, thousands, even millions of assets. They are asset
intensive.
• Assets come in many shapes and sizes — railroads, pipelines, manufacturing equipment, transportation
fleets, windmills — and include virtually any piece of equipment needed to sustain production, services and
operations. EAM best practices help maintenance teams gain greater control of complex environments to:
 Centralize asset information: A CMMS, as part of EAM, tells maintenance managers where an asset
is, what it needs, who should work on it and when. It automates critical asset management workflows
and makes them accessible and auditable.
 Resolve issues before they happen: Asset management software supports preventive capabilities to
maintain equipment for stable, continuous operations. It helps ensure warranty compliance and
preempt issues that disrupt production.
 Monitor assets smarter: AI-powered remote monitoring delivers actionable insight into current and
expected states of assets. It aggregates data across departments and information silos, allowing for
fewer, more accurate alerts and enhanced decision-making.

3
Why is EAM important?

 Maximize asset utilization: Historical and real-time data collected from IoT devices and analytical and
diagnostic tools help extend the availability, reliability and usable life of physical assets.
 Manage aging assets and infrastructure: Equipment lifecycles are extended through more informed
maintenance strategies and by embedding risk management into business processes to improve
return on investment.
 Elevate maintenance management: IoT, AI and analytics enhance equipment maintenance practices.
Asset tracking and traceability meet increasingly complex environmental, health and safety
requirements.
 Consolidate operational applications: EAM helps establish a single technology system to manage
virtually all asset types. Processes are unified and standardized for wide-ranging asset functions
across an enterprise.

4
ASSET Management

• The Assets module enables us to achieve the control more efficiently track and manage asset and location
data throughout the asset life cycle.

• Track asset detail - including location, work, cost and other attributes and their histories - over time to help
maximize productivity and extend asset life.

• Establish location and asset hierarchies to roll up costs across systems, subsystems, departments, and
locations, enabling a better understanding of the true cost of assets (initial cost, financial value, cost to
maintain, and so on).

• Monitor asset and location conditions to enable proactive - rather than reactive - maintenance that helps
reduce unplanned downtime.

• Support both conventional and linear assets.

5
ASSET Module

• The Assets module contains applications that are designed to manage the assets that are owned or leased
by company from purchase to salvage, from the beginning to the end of the life cycle for an asset.

• Asset records for purchased or leased information technology assets are maintained in the Assets
application. We create these records in the Assets application or when we use the Receive Rotating
Items action in the Receiving application. An information technology asset has a class structure identifier
that belongs to the top-level information technology classification used in enterprise.

• IBM Maximo Asset Management enables us to effectively manage end-to-end asset operations and
business processes to deliver efficient and effective services aligned with our business goals.

• It provides a comprehensive and modular approach to integrated asset control and visibility by providing an
enterprise platform for storing standardized data on asset histories to help integrate people, processes,
information, and technology. Maximo Asset Management offerings include tools, best practices, and
services for incremental value.

6
ASSET Overview

• We use the Assets application to create and to store asset numbers and corresponding information, such as
parent, location, vendor, status, and maintenance costs for each asset.

• We can build the asset hierarchy as an arrangement of buildings, departments, assets, and subassemblies.
The asset hierarchy provides a convenient way to roll up maintenance costs so that we can check
accumulated costs at any level, at any time. We can also find a particular asset quickly.

• Use the Assets application to perform the following tasks:

 Search for asset records.
 View, modify, add, or delete the main record for an asset.
 Create the asset hierarchy and view the subassemblies and parts of an asset.
 View, modify, add, or delete safety records for an asset.
 View or add metering information for an asset.
 Specify or view the specifications for an asset as recorded in the Classifications application

7
Rotating assets and non-rotating assets

• Rotating assets and non-rotating assets

 Assets can be either rotating or non-rotating. Rotating assets are assets that are interchangeable, such
as motors, pumps, fire extinguishers, or PC monitors.
 Rotating assets have both a unique asset number and an inventory item number. We can use the item
number to track assets as a group as assets are moved in and out of inventory and other types of
locations.
 The asset number is useful for tracking instances of assets as they are moved from one location to
another and from one site to another.
 Example: A company might have four identical (same make, same model) centrifugal pumps, so all
four pumps would have the same item number. To track the use, the repairs, and the locations of each
individual pump, each pump has its own, unique asset number.

8
ASSET Topology

• In the Assets application, the Topology tab provides a graphical representation of an asset and its
relationships.
• The Relationships tab shows the direct relationships of an asset and facilitates navigation through a chain
of related assets. The Topology tab view provides an overall graphical representation of an asset and shows
up to five levels of relationships. This view can help us understand the relationships in a networked
infrastructure.
• When we select an asset and click the Topology tab, the selected asset is shown with an outline box. Each
asset in the display has a status icon to show whether it is in operation, not ready, or decommissioned. A
work indicator icon is shown on any assets that have associated scheduled tasks.

UI Item Description
Asset Summary View When you hover the cursor over the graphical representation of an asset, summary
information about the asset is shown. The information shown in this summary
view and the order in which it is shown, is configured using the Configure Topology
Viewer > Asset Summary View action.
Context menu options In the topology display, right-click an asset and select Asset Details from the
context menu to show a detailed list of asset attributes. In the topology display,
right-click an asset and select View. This opens a submenu, listing options to view
historical information, work orders, contracts, or tickets that are associated with
the selected asset.

9
Working with Assets

Creating Assets Adding assets to collections Adding relationships to assets

Viewing related assets Issuing items from a storeroom Modifying assets

10
Creating Assets

• We use the Assets application to create and to store asset numbers and corresponding information, such as
parent, location, vendor, up/down status, and maintenance costs for each asset.

Steps:

On the toolbar of the Assets application, click

the New Asset icon.

In the Asset Description field, type a description.

In the Rotating Item field, if the asset is rotating,

type a value.

If this asset has a parent, type a value in

the Parent field.

Click Save Asset.

11
Adding Assets to Collections

• We use the Assets application to add one or more selected assets to one or more active collections. A
collection is a group that can contain assets, locations, and classification items. An asset can be added to
more than one collection.
Steps:
On the List tab of the Assets application, filter the list to
display the assets that you want to add to a collection.

Click the Select Records check box, and select the check

box for each asset that you want to add to a collection.

Select the Add Assets to Collections action.

In the Collection field of the Add Assets to

Collections window, click Detail Menu to select an option
and to retrieve a value.

Click Ok.
12
Adding Relationship to Assets

• We specify relationships between assets and locations to define a logical connection between separate
assets.
Steps:

Select an asset and click the Relationships tab. In

Relationship table click New Row

Specify a Relationship or use the Detail menu to select a

value.

In the Target Asset field, specify the asset that is the

target in the relationship.

If the Source Asset is not the currently selected asset,

specify the current asset in the Target Asset field.

Click New Row to add further relationships or Save.

13
Viewing Related Assets

• All asset relationships have a source asset and a target asset. We can view all relationships for an asset or
you can filter the view to see a subset of its relationships.
Steps:

Select an asset and click the Relationships tab.

In the Filter By menu, select one of the options. Click the

refresh icon to show the set of relationships you chose.

To sort the relationships list by any of the columns, select

the sort arrow icon next to the field title.

Click the detail menu next to a source or target asset to

move to or view related asset information

To retrace your steps through a series of source or target

asset Move to navigational commands, click the View
History toolbar icon
14
Issuing Items from a Storeroom

• We use the Assets application to issue items to an asset. We also can use this application to return items
from an asset to a storeroom. You can issue both rotating and non-rotating items, and you can issue items
from different storerooms.
Steps:
From the List tab in the Assets application, select the asset to
which you want to issue items. Select the Issue Items from
Storeroom action.

In the Filter By menu, select one of the options. Click the refresh

icon to show the set of relationships you chose. In the Associated
Items table window, click New Row.

In the Item field, specify the item you want to issue. In

the Storeroom field, specify a storeroom. In the Quantity field,
type the number of items that you want to issue.

In the Transaction Type field, select ISSUE if you are issuing the

item to the asset, or RETURN, if you are returning the item to a
storeroom

Click New Row to add another item to be issued to the same asset.

Click OK

15
Modifying Assets

• After we create an asset, we can add it to a collection, change its status, add downtime information, add
meter information, move the asset, swap the asset, change the item number, or zero the year-to-date
amount.

Changing the status of Reporting asset

Adding meters to assets
assets downtimes

Moving assets Swapping assets Changing item numbers

Zeroing out asset costs

16
References

• https://www.ibm.com/topics/enterprise-asset-management
• https://www.ibm.com/docs/en/mam/7.6.0?topic=application-assets-overview
• https://www.ibm.com/docs/en/mam/7.6.0?topic=overview-rotating-assets-non-rotating-assets
• https://www.ibm.com/docs/en/mam/7.6.0?topic=overview-asset-topology
• https://www.ibm.com/docs/en/products
• https://www.ibm.com/docs/en/mas

17