From blogs to case studies to news, we love sharing our tips and tricks for asset management, cloud, IoT and smarter operations.

by | Feb 11, 2020

Maximo buzz kills – working your way around them

In the world of Maximo, there are often little things that you wish you wouldn’t have to encounter. Slow start centers, slow search results and that dreaded spinning wheel on the screen are just some of the Maximo buzz kills that users report. If you can rule out issues of network latency, CPU utilization and other obvious reasons, then simple tweaks like the ones mentioned below may be able to help you.

~ Maximo buzz kills can be frustrating and time consuming ~

Start Center slowness

Start Center is a pretty nifty tool. To have everything stored in one place is a major time saver. So, when a start center lags, it can be pretty frustrating. What goes on behind those lovely result sets and KPI portlets, you ask? Every portlet runs queries. This is what fetches the results from the database in each portlet. Assuming each query takes about a second to execute, 5 portlets in your start center would mean that it would take 5 seconds to load everything on the start center. To solve these Maximo buzz kills, try to make sure that too many queries are not being run simultaneously. Furthermore, the default query should be compact rather than too complicated as this will also increase lag time.

~ Time lags in Start Center ~

Problems with displaying more information in the List tab

It is a common request from clients to make available a field in an application. A common belief might be that one or two fields on the List tab won’t significantly affect performance. Such customizations are performed using the Application Designer, or by directly modifying the XML for an application. While the original intent of the customizations is convenience and being able to easily download data using the “Download” feature, there is a downside. Such customizations can create an unnecessary drain on system performance. Every time the List tab is displayed when a user hits enter in the application; the added information also needs to be fetched from the database. There is, however, a simple solution to this – instead of customizing applications to make available additional information, using ad hoc reports can help the performance. Additionally, the information you need is not displayed every time the application is loaded, but only when it is needed.

Long running queries – how to identify and tune them

When analysing logs, long running queries are common Maximo buzz kills that most of us have experienced. Sometimes users can run poor queries, oblivious of the impact it can have on the system. Fortunately, there are some properties available in Maximo to tackle this.

Maximo provides configurable system properties that determine how long queries can run. A control is provided in the user interface so you can cancel your own queries before a configured timeout property cancels them. These configurable attributes are set in the System Properties application.

Query timeout: mxe.db.QueryTimeout.

This property represents the amount of time in seconds before the SQL query times out and is stopped.

Identify long running queries: mxe.db.logSQLTimeLimit

This property can be used to identify long running SQL statements. By setting appropriate logging levels and monitoring logs you can identify performance problems caused by inefficient user queries or the lack of a good index for a frequently used query.

Long running reports

We have seen cases where a report goes rogue, running for a long time and affecting negatively on system performance. There are two ways to ensure reports don’t degrade system performance.

  1. Specifying record limits – To minimize performance impacts of users inadvertently running reports against very large record sets, you can specify record limits. These record limits can be set for individual reports, or at the security group level. This will prevent a very large report from executing or can even cancel it when it reaches a certain value.
  2. Sending notifications – Did you know that you can configure notifications to be sent to your administrator when reports are processing either for a very long time, or if reports are hung in the queue? This would help nip the problem in the bud before it degrades system performance any further.

~ Specify record limits and send notifications to your administrator to avoid long running reports ~

If there are any other handy tips and tricks that you think we missed, contact BPD Zenith and let us know!

Deepa Thomas

Deepa Thomas

Deepa is a Graduate consultant at BPD Zenith. Before shifting her focus onto Maximo, Deepa worked with IBM Mainframe systems in India. She is now an integral part of the ANZ Support team and enjoys solving day to day issues faced by clients. When not exploring and tinkering with Maximo she loves doodling, painting and exploring art.


Submit a Comment

Your email address will not be published. Required fields are marked *

9 Recommendations For A Successful SAP & IBM Maximo EAM Interface

9 Recommendations For A Successful SAP & IBM Maximo EAM Interface

Integration is often a key component for getting the most out of your critical IT applications. Modern Enterprise Asset Management systems such as IBM Maximo are designed for integration which can expand their capabilities and allow the flexibility that the industry...

Reinvent the Wheel with BPD Zenith’s Maximo Accelerators

Reinvent the Wheel with BPD Zenith’s Maximo Accelerators

I was recently involved in preparing a business case for a Maximo implementation, and as a part of process I spent considerable time analyzing and evaluating the best approach. In essence, I was trying to find the optimum balance between minimizing the length of the...

Defence Seaworthiness – A session from AMPEAK 2021

Defence Seaworthiness – A session from AMPEAK 2021

I recently got the opportunity to attend Asset Management Council of Australia’s AMPEAK conference. It has been a great experience interacting directly with the true practitioners of Asset Management, and understanding some of the technology challenges that they are...

How to call a Report directly from the Action Menu in IBM Maximo

How to call a Report directly from the Action Menu in IBM Maximo

In IBM Maximo, it’s possible to add a direct print option to a report. This adds a printer icon to the toolbar and allows you to run the report with just one click. But for reports where there are parameters required before running, this is not possible… Usually, a user will have to click the “Run Reports” action, then find their report in the list of all reports available for that application. They then click on the one they want before being taken to the IBM Maximo Reports Request page. In this blog I’ll show you how to get around that problem. in our example we use an Action launch point for an Automation Script and link it to a menu item in IBM Maximo Application Designer…

Sign up to our free newsletter to explore emerging technologies, industry events and Maximo best practice.

Come with BPD Zenith to the future of Asset Management

Listen to your assets!

Most companies are aware of waste in their preventative maintenance efforts, but aren’t quite sure how to eliminate it.