IBM Maximo Asset Management software provides asset lifecycle and maintenance management for all asset types on a single, extensible platform. It is built on Java, makes heavy use of SQL where clauses, and supports "automation scripting" out of the box in Jython/Python and JavaScript in predefined contexts.
IBM Maximo Asset Management software is the foundation and framework of an Enterprise Asset Management (EAM), Change and Configuration Management Database (CCMDB), Service Management and IT Asset Management (ITAM) suite of applications that provides asset lifecycle and maintenance management for all asset types on a single platform. Businesses across all industries use Maximo to maximize the realized value of critical physical and IT assets, from purchase authorization to decommissioning, by augmenting business processes with automation and enforcement of best practices. Industry-tailored solutions are available for IT, utilities, nuclear power, transportation, government, telecommunications, life sciences, oil & gas, and more.
The current release, IBM Maximo Asset Management 7.6, is the latest release built upon a Java Enterprise Edition (JEE) Service Oriented Architecture (SOA). The Maximo framework is scalable, can be easily integrated into existing Enterprise Resource Planning (ERP) systems via REST, database tables, Remote Method Invocation (RMI) or a host of other options, can be extended with custom Java or via Automation Scripting (scripting in Jython/Python or JavaScript in predefined contexts), and can be configured with SQL where clauses in many of its internal configuration tools. It also sports tight integration with Actuate's Business Intelligence Reporting Tool (BIRT).
As Maximo is a Commercial Off The Shelf (COTS) product, related Java, Python, JavaScript, BIRT and SQL questions may have constraints not normally imposed on developers working with those languages/tools. For example, Automation Scripting contexts, for scripting in Python or JavaScript, are predefined but dynamic, so the scripter doesn't know at coding time what all the variable names will be. For another example, Maximo does select * from table where and appends your where clause, so the developer can't change the columns selected or the grouping.
