IBM Maximo Asset Management (or ‘Maximo’ in short) is an integrated key productivity tool and a database designed to manage all the asset types of an organization in one single solution platform. Maximo, built on a SOA(Service Oriented Architecture) delivers a complete view of all asset types, their locations and conditions, work processes that support them and also provides control, optimal planning, compliance capability and audit.
Maximo database provides crucial information about asset resources, their configuration, key attributes and their logical and physical relationships to other resources.
Using Maximo user interface, you can build Key Performance Indicators(KPI) to manage asset locations and their conditions, and generate automated action depending on the changes. You can create, monitor, notify, assign and report on important process components right from beginning to end point such as purchase orders, work orders, service desk tickets, including status, and so forth. For better productivity and communication in future aspects, you can add attachments, urls, pictures and maps to each task or record. All these aspects are detailed in IBM Maximo Training in a clear and precise manner.
Galvanic Presence Of Maximo In Oil & Gas Industry:
Maximo for oil & gas company adds a feather of industry-specific performance to Maximo Asset Management, by that delivering the following functionalities or capabilities that are designed to gear up operational excellence.
Apart from the above mentioned, there are other concentric areas like Procurement, Risk Analysis, Regulatory Compliance, Investigations, Incident Management, Failure reporting, IBM Integrated Information Framework Integration, Materials Management, Operator’s Log, Linear Asset Modeling, Risk Matrices and Solutions wherein Maximo is the reason for effective operational excellence achievement by Oil & Gas industry.
Oil & Gas industry is a critical sector for any nation and Maximo is supporting this sector facing evolving and complex issues in operational processes. Maximo solution provides necessary Internet of Things (IoT) applications in collecting valuable information, knowledge, improving operational efficiency, operate and manage mission-critical assets productively and safely. As oil and gas companies are growing though at a slower rate, but have smarter software solutions like Maximo for new upcoming projects in this energy space.
Numbered lists in Birt reports do not in sync with Maximo Birt report output when working with a Maximo UI record that has a rtf formatted Long Description.
This is logged as a Bug at the Birt Eclipse sit for version 3.7.1 and still remains at Status: OPEN since 2013.
Bug 422063 - Numbered bullets do not increment correctly
You may sign up to a Bugzilla account and add your vote for this.
Create a rtf formatted longdescription, i.e. in Job Plans, like this:
Use the buttons for „Numbered List“, „Bullet List“ and „Indent“ to format text
Run a report which displays this longdescription, i.e. Job Plan Details:
The numbering differs between Maximo and Birt.
EdMaxwell 270002CMGQ 790 Visualizações
How can I let my report developers create and publish reports and ensure that these reports do not have a negative performance impact on my production database & UI?
We have created a couple methods to protect the UI from Report performance issues.
To configure some reports, (This leaves the Out of Box reports, including update reports pointing at Production) (See Page 8 of the Guide)
These users (or report developers) will have the Eclipse Report Designer installed locally. The Designer includes a properties file, mxreportdatasources.properties that points the report to the appropriate database. The default points to the Maximo primary db. This can be changed from the default, to a secondary database.
See page 9 of the guide for the complete data source entry.
After making the one time change in the properties file, each report will need to point to the new data source. Page 12.
<script-data-source name=”maximoDataSource” becomes <script-data-source name=”external”
Do my users have to make this change with every report? Yes, but if you edit the report templates to point to the correct datasource, each new report will automatically point to the correct Datasource.
Finally, you will need to tell Maximo about the new secondary database and datasource. This is done under Report Admin, Configure Data Sources.
So, all reports uploaded by these users will be loaded to the Production database, but will report from the secondary (external) database.
You will need to provide these report writers with the following.
Is there any way that these users can upload a report that points to the Production database?
To upload a report that point to production, these users would have to upload an existing report that points to prod or modify a new report so that it points to ‘maximoDataSource’. So it remains possible that a user could point a report to Production, but this would have to be intentional.
So, at this point, we have a strategy to create reports that will point to a secondary database. To take the remaining pressure off of the UI Server, you need to enable the BROS server.
The BROS server is just another Maximo server pointing at the same primary database. Any immediate or scheduled reports will run on this server. The UI server will still host QBR report Previews and any Direct Print reports.
#2 Points the custom reports at the secondary db, but leaves report processing on the UI.
Using both #1 & #2 ..
With Maximo 7.5 you can download reports as an Excel file.
Normally, this means saving the file locally with an XLS extension. However sometimes users have later versions of Microsoft Office installed. This can cause Excel to display a Warning "The file you are trying to open, 'wotrack.xls', is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file now ?
Users can find this warning tiresome if they have to repeat this several times daily.
The question is...
Is there any way I can export Microsoft Excel files to *.xlsx format instead of *.xls format ?
I gave this advice out recently and it worked like a charm.
As this is really an Excel issue and not a Maximo problem, I googled 'excel warnings xls' and found the following.
On that page, HansV suggests that this can be changed by tweaking the registry on the clients workstations.
I certainly would not attempt this unless I was comfortable tweaking the registry. But if you are up to the task, I can say that this works.
Not everyone will be comfortable with users changing the registry for this. For those folks Maximo will be providing xlsx downloads in the 7.6 release of Maximo.
There is known issue with AdHoc reports in a multilingual environment.
It works like this.
A user, who is not using the Maximo primary language, creates and saves an Ad Hoc report.
In doing so, the user enters a report description. This is a required field and and is part of the search index for this report in the Select Actions / Run Reports window.
The problem is that there is no Report Description entered for the Primary version of the report entry. If a user opens the Select Actions / Run Reports window in the primary language, they will see an error and be unable to search the report list.
There are a couple ways to handle this.
If you do not have a lot of users creating AdHoc reports, the Administrator can add the Report Descriptions in Report Administration. If this task becomes too much to handle, you can create an Automation Script that will automatically populate the Primary Language Report Description.
Here are the values for creating this script.
Script Language: jython
Log Level: ERROR
from psdi.mbo import MboConstants
userLang = mbo.getUserInfo().getLangCode()
# If the current user is not a base language user, set a value on the base language description
This Script is specifically targeted the AdHoc issue. It is only triggered when saving a new report (as specified by the Add Option in Launch Points)
The Script uses the reportname as the default description. This could be modified if you prefer.
I was recently asked the question "Do you know if Maximo 126.96.36.199 supports Cognos 10.2.2"?
The answer is no.
To which the next question was "do you know if there's a web site / resource to show the supported version as the Maximo Product Matrix does not contain information on Cognos?"
Maximo Product Matrix
The EXT_Platform_Matrix.xls is the document which contains the confirmation that Maximo 750x only supports upto Version 10.1.1 .
As a support analyst, one of the first reports that you become familiar with is the Maintenance Cost Rollup report. In the past this report has been known as the Asset Cost Rollup and going way back to Maximo 4, DBRollup.
The Cost Rollup report is actually 2 separate reports. Since this was introduced, the report acts basically the same. It's primary function is to update the the Asset Year to Date & Total Costs fields in the Asset Record.
These costs include the following.
Given that this report updates the YTD Total Charges in the Asset, one would think that this report would be run on a frequent basis.. (so that the YTD Totals reflect current values). Unfortunately, that is not what happens. I think that folks get busy with the day to day operations of the software and forget about this report. In the past, it is not uncommon for people to forget about this until they are performing their year end activities. By this time, they have accumulated a ton of transactions.
With any database operation, the more data that needs to be searched & updated the longer it takes and the greater resource burden it becomes. Occasionally, you may find that the report will just not complete any more. If you in this situation, you will need to break the transactions down into smaller chunks.
You can get the Rollup and Rollup Update reports to filter on the Asset Location in the Report Request page. You will need to to add the location parameter to both reports for this to work. You can run either report, but if you just want to rollup the transactions you need only run the update report. When setting up the Location parameter, set it to allow multiple values (so you can update multiple locations) and set it to Not Required.
The idea here is to run the Update report against some of your larger locations first. Later you can run it against several smaller locations at a time, and finally run with no parameter to run on the balance of the locations.
The following SQL will give you a rough idea of what locations have the most non rolled up transactions.
Select siteid, location, loc_total from (
Select siteid, location, assetnum, site_total
One of the benefits of BIRT reporting in Maximo is that our users can generate all manner of reports that put the accumulated Maximo data in perspective.
This ranges from transaction reports like the Work Order Detail report to high level reports (Asset Cost Rollup) that summarize vast swaths of Maximo Data.. Add to this, custom reports and the reporting possibilities are endless.
However, this does come at a cost. The Work Order Detail report uses 17 different SQL statements (or more) and operates on a table that is typically huge. The Asset Cost Rollup report summarizes Labor, Materials, Services & Tool costs assigned to closed Work Orders. In the past it has not been uncommon for this report to run over several days. All this activity consumes server resources.
If you have been using Maximo for some time, you will remember some of the lessons learned in the past. In Maximo 5, we found that users could run the Work Order Detail report against all the Workorders in the database. If you ran this a couple times in a row, you would be successful in overloading the UI server to the point that it crashed.
In an effort to protect the UI server, we added some features..
There were some limitations (Direct Print reports still run on the UI Server), but generally, this approach was successful.
Later we introduced AdHoc reporting. This allows users with limited technical ability to create reports. Unfortunately, only AdHoc reports that have been saved and are run from Select Actions / Run Reports run on the BROS. Previewing AdHoc Reports from the AdHoc Query Tool, runs on the UI server. This puts these non technical users in a position to seriously impact the UI server performance. This led to the introduction of the mxe.report.adhoc.previewLimit property.
This property while configurable, defaults at 50 records. The best practice is to give your users enough data to develop their report. Once the report is saved, the Administrator can assign a specific record limit (or none at all) to the saved QBR report. This report, when run, will execute on the Birt Reporting Only Server.
In summary, to protect your UI server from overload by reporting tasks, you want to do the following.
Limit the reporting load on the UI server. This includes Direct Print reports and the number of records that can be run on Direct Print reports. This also includes the number of reports that can be run on a server. This can be limited by the system property mxe.report.birt.maxconcurrentrun.
Limit the number of records that can be previewed on the UI server in the QBR (AdHoc) builder. This is the mxe.report.adhoc.previewLimit property.
For more information see the QBR (AdHoc) Reporting and Report Object Structures Guide Page 68
NKKhan 2700001B9H 3.759 Visualizações
If your looking for the right approach to migrate your own developed Cognos reports from one environment to another, here is a bunch of links that cover the process involved.
Deploying Selected Public Folders and Directory Content
IBM Cognos Proven Practices: IBM Cognos BI Deploy Content Between Environments
As a Maximo administrator you might notice the accumulation of temporary BIRT files on your TPAE/Maximo server. As this can consume the free diskspace on the server, this can be a serious issue. These temporary files are created by BIRT at the report execution time. Usually they are removed when the report completes.
The resolution to this is to direct the output to a specific folder so that it does not interfere with the performance of the Maximo JVM.
This can be done by adding a parameter to the Generic Java Parameters in either WebSphere or WebLogic.
This process varies in WebLogic and Websphere, but in both cases, the Directory Path to this folder should contain no spaces,
For detailed steps to setting this up in WAS, see page 25 in the V 7.5 Report Feature Guide mentioned at the link below.
For further information see.
Maintenance managers across industries are forced to improve their business. In the increasingly competitive market the maintenance department needs to add more value to the overall company results. Fortunately, many maintenance organizations contain a value potential that has not yet been realised. But where is this treasure hidden and how can it be revealed? Should you focus on uptime or on cost reduction? And how important is safety, health & environment with respect to value creation?
Questions that can only be answered with the right maintenance and reliability information. Although this information is often captured in IBM Maximo, it is rarely used to steer maintenance performance. Today you can create new and innovative KPI Dashboards that are built in IBM Cognos technology and are fully integrated with IBM Maximo. When you use the out of the box Cognos functionalities you will be able to create a powerfull Performance Management environment.
Watch a demo movie on youtube to get a good idea Demo movie VDM Inside
Maintenance KPIs Dashboards
The idea of a dashboard is simple. When you start up a dashboard, the first thing you need to see is your overall maintenance performance represented by a fixed number of key performance indicators like in example above. Each KPI then shows the performance of one of the competences in a maintenance organization: Cost Control, Asset Utilization, SHE Management, Reliability Engineering, Planning & Preparation, Maintenance Execution, MRO Supply Chain Management, Service Supply Chain Management, Skill & Tool Management and Equipment Knowledge Management.
Management by exception
Using the out of the box Cognos functionality you can conditionally format a dashboard. Using the the conditional colour, a KPI tells you if your performance meets your target. You should consider setting targets per time period and for each location in your Maximo system. KPIs that deviate from your target are then displayed in red and are subject for further analysis. By using colours, management will be stimulated to focus on areas that need improvement. Prioritize on things that create the greatest economic added value.
Drill down analysis
Using Cognos drill down/drill through functionality you can make your application even more powerfull. It will help you to explain why certain KPIs deviate from target. Which assets, planner group, reliability engineer, maintenance team, contractor and/or stores are responsible for the measured underperformance? By clicking on a KPI, you will be able to enter a preconfigured dashboard.
These graphs help you to indentify the root cause of your problem. A further drill down analysis is possible by double clicking on each graph in the dashboard. More detailed graphs can be consulted, until you have found the root cause that can be solved by a corrective action from management. These actions can be logged in the system and monitored on their contribution to the performance improvement. The strength of the predefined drill downs lies in the fact that you do not have to reinvent the wheel each time you need to do the analysis of a deviation.
Besides drilling down data, it is also possible to roll up data.This way you can create a benchmarking module where the KPIs of an asset can be compared against KPIs of similar assets from the same organization. It is even possible to group assets into a division and perform a benchmark analysis between different divisions of an organization. These kinds of analyses are especially useful in multi site maintenance organizations.
Thing to consider are using a data warehouse, develop a Dimensionally Modelled Relational Package to benefit from drill down functionality, use predefined standard applications to reduce the time to implement your performance management solution.
Feel free to contact me with any questions.