A friend of mine who has experience with SAP asked whether
Maximo can handle a “Blanket PO” process similar to SAP. I sent him my answer
based on the scenario and requirement he provided and think it is probably
worth posting here as some other people may find it interesting:
Maximo custom control (Part IV) – Create a chart control
In the previous
posts, we have practised on how to create a JSP page, register it as component, and register a control. We also discussed on how to pass properties from control to its
components and use it with conditional UI.
Maximo custom control (Part III) – Conditional UI with custom properties
In the last exercise, we added new properties to a control,
and by doing so, we have better understanding that the
properties of a control is defined inside the <property-list>…</property-list>
XML element. We also know how properties are passed from control level to its
components.
If you have some experience with Application Designer, you must already know that, we can dynamically modify value of a property using
Conditional UI. We can do the same with the custom properties that we recently
added.
With the two properties: “part1size” and “part2size” added to the multipart
textbox in the previous exercise, let’s configure a simple Conditional UI to demonstrate this capabily:
Maximo custom control (Part II) – Control properties
In my last post, I created a super simple control with just
a “Hello World” label. The goal of the exercise is for us to identify the core
components of a control. In this post, I’ll continue to expand the exercise so
we can better understand Maximo’s controls.
One common requirement the need modify the size of
the multipart textbox control, usually to increase the size of the first
textbox to fully display long ID of item or asset.
Application Designer doesn’t provide us with an option to modify this.
Getting Started with Maximo's Custom Control (Part I)
Application Designer is a powerful tool to customise Maxmo’s GUI. However, in certain situation, it couldn’t do what we want to meet the requirements of our clients. In that case, we can look at customising Web UI module.
In this series, I will provide step-by-step instructions on how to customise controls in Maximo. The aim is to help beginners get familiar with the framework by going from the most basic modification then build up from there.
Part I - Create a simple Label control:
Let’s get started by displaying a ‘Hello World!’ label on the main screen of the Asset application. We can do that by creating our own custom control.
Maximo's ABC Analysis and Physical Count
A friend recently asked me on LinkedIn about Inventory ABC analysis on Maximo and how to setup physical cycle count. After responding to him, I thought it could be posted on this blog to share with other Maximo users who like to know more about this function.
![]() |
| First page of the ABC Analysis Report |
ABC Analysis is the method of categorizing inventory items into three groups: fast moving, average, and low moving. This method is commonly used in ERP systems like SAP or Oracle.
Maximo with Oracle’s InMemory (Part 2) – Huge Performance Gain
Last week, I played around with Oracle’s new toy: the InMemory feature available in Enterprise Edition. Although it made Maximo runs 1.25x faster, but it didn’t meet my expectation which was from 2x to 5x. This has bothered me for the whole week and I kept thinking about it.
If you’ve read my previous blog post, the one thing I pointed out which could lead to no performance improvement is that I ran the test on a tiny demo version. It has only a few hundred assets and less than a thousand work orders. So, any heavy processes or poorly written queries couldn’t make the database 1 second slower. This week, I set out to do a more elaborate test with a setting that looks more similar to a real production environment.
If you’ve read my previous blog post, the one thing I pointed out which could lead to no performance improvement is that I ran the test on a tiny demo version. It has only a few hundred assets and less than a thousand work orders. So, any heavy processes or poorly written queries couldn’t make the database 1 second slower. This week, I set out to do a more elaborate test with a setting that looks more similar to a real production environment.
Subscribe to:
Posts (Atom)



