All companies are dependent on critical assets — those assets that have a direct and significant impact on corporate performance. Precisely what these assets are varies by company and by industry, but caring for them is critical.
Asset Management is the process that helps organizations to automate the complete asset lifecycle management process from the time they decide to purchase an asset to the time they decided to retire it.
Birlasoft has set-up a dedicated team of consultants certified and trained on Maximo. This team has experience of implementation of Maximo for Asset Management in various domains such as:
Life Science and Pharmaceuticals
Transportation
Government Institutions
Manufacturing
Oil and Gas
Utilities
Information Technology
Birlasoft team has implemented all modules of Maximo and has experience on all version right from 4.x to the latest version i.e. Maximo 7.1. The learning from each of these assignments is shared and reused for future engagements by the CoE. The various modules that Birlasoft team have implemented are:
Assets
Contracts
Financials
Integration
Planning
Preventive Maintenance
Reporting
Resources
Safety
Self Service
Service Desk
Service Management
Work Orders
The CoE at Birlasoft offers the following services:
Upgrading your Maximo® solution to IBM Maximo Asset Management, release 6 or 7 is an important initiative that requires careful planning and strategy. Various implications of upgrading should be considered, and each has an impact on the duration, scope and financial investment of the project.
This web page will provide answers to some of your questions and guide you to appropriate resources as well.
Why Upgrade?
Below are reasons why customers should migrate to either release 6 or 7.
Following are the main reasons why customers should upgrade/migrate to Maximo Enterprise Suite, release 6:
Improve return on assets and decrease costs and risk
Increase productivity and asset-related decision making
Increase asset service delivery responsiveness and revenue
Facilitate regulatory compliance efforts
Lower total cost of ownership
New features are introduced in Maximo Enterprise Suite (MXES). These feature can be groped under the following categories:
Multisite and Multilanguage
Interface and Navigation
Administration and Set Up (Configuration, Security)
Asset Management
Contract Management
IT Asset Management
Materials Management
Maximo Enterprise Adapter (MEA)
Purchasing
Service Desk
Service Management
Workflow
Work Management (Resources, PMs, Planning, Safety)
Reporting
Following are the three main reasons why customers should upgrade/migrate to IBM Maximo Asset Management, release 7:
One platform for the key processes that go hand in hand: Maximo Asset Management, Tivoli Asset Management for IT, Tivoli Service Request Manager and Configuration and Change Management Database
Lowering both the cost of ownership and the cost of environment migration
Specific market driven functionality such as Linear Assets, enhancements to work and process management and enhancements to usability
Upgrade versus Migration
Upgrade - Employs IBM-provided utilities to move database from ‘old to new,’ through each system version in succession, [i.e. 4.1.1 to 5.2, to 6.2,] to reach the target system
Requires data cleansing
Requires documentation of all screen changes and re-development of customizations for target system
May require additional data input
Maximo Upgrade cycles not as simple as before
Rapid technology advances caused technology gaps that may require bypassing multiple Maximo releases to achieve desired level
Important objective: Reframe client perceptions, understanding, and expectations of process required, and provide bridge to transport them there
Migration – Starts and takes place on target system, receiving exported data from existing environment
Requires data cleansing and importing through mechanism through the Upgrade Scripts or some other medium
»
SQL Scripts / MEA for data loading
»
Requires no intermediate system iterations
»
Requires thorough database model knowledge
Matches existing business process to new functional capabilities, versus moving from past to present