Last Updated on May 9, 2024 by maximosecrets

Topics

Good morning, I’m Andrew Jeffery and I’m pleased to be giving you an introduction to Maximo Manage the part of the Maximo Application Suite that provides Enterprise Asset Management capabilities.

I’ve split this presentation into four parts, and I will dive quickly into what we mean by core Maximo with a slide on each of the ten core capabilities. For existing Maximo clients this should be what you are already aware of.

In the second part we’ll introduce the Maximo add-ons which are now part of Maximo Manage, the included capabilities which previously needed to be separately licensed. Four of them have been around for some time, you may or may not be using them, but it is worth reminding you that they exist, and they will be available to those who have upgraded to MAS. One is completely new and was only introduced in September 2023. I have a slide for each of these five included capabilities. 

In the third part I have one slide to explain the full scope of Maximo Manage. If you have reviewed the Maximo Application Suite overview, you would have seen the slide before. Finally, I’ll give you my perspective on the road ahead where I think IBM will be focusing over the next few years.

Maximo Manage

In the Maximo Application Suite (MAS) overview, we introduced the applications of the suite Manage, Monitor, Health, Predict, Visual Inspection and Assist. For many existing Maximo clients, they are using what IBM are now calling Maximo Manage, it is the application of the suite where you create and manage your assets. Existing clients who are upgrading to MAS will not see many changes to the applications they currently use and no doubt they will continue to call what they see as Maximo and Maximo Manage might only be a term that is referenced when dealing with IBM. For the purposes of this overview on the Manage element of the Maximo Application Suite I will be referring to Maximo rather than Maximo Manage.

For those of you who have seen the Maximo Application Suite overview then you would have seen a different slide when I spoke about the Manage element. Maximo has a core set of modules which you see in the wheel on the left, but there is an additional set of included capabilities, Linear, Calibration, Mobile, Scheduler and Reliability, the first four of these were all previously add-ons with their own license. For existing clients upgrading to MAS, they will be familiar with the core modules, but for many the included capabilities will be new to them, or at least some of them will be. I am including Reliability as an included capability; this was new in MAS 8.11. IBM are currently calling it an add-on; I think because it currently needs to be installed, but as licensing has been unified to a single part number (apart from Maximo IT) it can be treated as being included.

Maximo has a set of 10 core modules and the five included capabilities, and I’ll be discussing each of these in the following slides. There are additional add-ons Spatial, Service Provider, Health, Safety and Environment Manager (HSE), Asset Configuration Manager (ACM), Maximo IT (formerly known as IBM Control Desk (ICD)) and Maximo Optimizer which is used with Schedule Optimization and Asset Investment Optimization, a part of Maximo Health. Maximo also has Industry Solutions for Transport, Utilities, Oil and Gas (O&G), Nuclear, Aviation and Civil Infrastructure. To include all of these in a single overview would be doubling its size, besides, most of them are so large that they deserve their own set of slides to understand their capabilities, for example the HSE add-on has more than 50 applications. In addition, there are a set of of connectors and integrations to other IBM products which I’ll briefly describe a bit later.

Each of the additional capabilities, add-ons and industry solutions you see on the right provide new applications or they extend the applications which are found in the core modules. Linear Assets could have been covered in the Assets module, but you’ll find that some of its functionality also exists in the Service, Planning and Work Order modules, and it is easier to explain Linear Assets as a subject together rather than spreading it across the text of several modules.  The same applies to everything you see on the right.

You may be thinking that this is a colourful slide, perhaps there are too many colours. Each of these colours (and the icons) will be used across Maximo Secrets and over the next few months I will be aligning the Module descriptions and Application Maps to these colours. The observant of you might have noticed the same colour for HSE and O&G, this is because HSE is a very large subset of the Oil and Gas Industry Solution and so it make sense to consider these together. 

The core modules on the left loosely align with the modules you will find in Maximo. The main differences are that Service also includes Service Level Agreements, and Planning also includes the Preventive Maintenance and Resources module where People, Craft, and  Labor are defined. The Maximo modules are important from two perspectives, they will be where you will find the applications, but they are also used to define the set of applications a Limited User may access without becoming a Base User, a Limited user is restricted to the applications of three modules. Therefore, when considering licenses please do not use these modules as your guide.

Core Maximo

We’ll start by explaining the 10 core Maximo capabilities. For existing clients who have not upgraded to Maximo Application Suite and have no add-ons or industry solutions then these are the capabilities which their Maximo system has.

Asset

At the core of Maximo is the Locations and Assets applications. Locations can exist in multiple systems both hierarchical and network, a location in a network system can have multiple parents. A location can have a service address which defines the latitude/longitude of the location and positions the location on a map. All locations and assets below this in the hierarchy will have the same map position. 

An asset exists at an operating location, or it may exist in a storeroom waiting to be issued. Assets may have an asset hierarchy and/or a set of spare parts. Fixed assets are commissioned at their operating location and do not move until they are decommissioned. Some assets are termed rotating, meaning that we track the asset from the storeroom to the operating location then to the repair shop before it is returned to the storeroom again for issue to another operating location. 

Linear assets (roads, rail, pipelines and cables), mobile assets (plant hire, tools, medical equipment), and transportation assets (trucks, vans, buses, trains) can all be handled in Maximo. Linear assets is an included capability, and it uses Relationships and Features to define how linear assets relate to each other and the features that exist along the path of the linear asset. Relationships can be used to define any relationship between two assets, not just linear ones. 

The characteristics of locations and assets are defined by a classification hierarchy and a set of attributes associated with each class. Classifications can be used for purchased or stocked items and many other record types in Maximo, for example Service Requests or Work Orders. The descriptions of classifications and their attributes can be made multilingual.

Assets can be generated from Asset Templates. The asset template has a classification, may have multiple meters and spare parts, and associated Master Preventive Maintenance records that define how the asset will be maintained, inspected or monitored. Meters are continuous (runtime), gauge (measurements) or characteristic (observations). The meter values can determine when preventive or corrective work is performed. The Condition Monitoring application is used to receive the measurement made against assets and meters of type gauge and characteristic and to raise a work order when they exceed limits.

Finally, there is a Failure Codes application for defining failure classes and the problem, cause and remedy codes used in failure reporting on a work order.

Inventory

Maximo has three types of items and hence three main applications for recording them, Item Master, Service Items and Tools. The characteristics of an item can be described using a classification and the attributes of the classification, the specification. The classification and attribute values can be used to generate the description of the item, this can create a lot of consistency in your data. Users will find lookups which allow you to perform word searches, or searches based on the classification hierarchy or an attribute-based search. The item can have an image and like all Maximo applications document or URL links can be associated with each record.

Items and tools can represent both consumables and items for which assets will be recorded, rotating items. Like items can be grouped using commodity groups and codes. Items can be condition enabled meaning that multiple records can exist for the item but at different values. For example, a new tyre for a truck has a different value to one where the tyre is worn by 20%. Items can be kitted meaning that several items are assembled into a kit of parts waiting to be issued as a whole. Items can also have an item assembly structure, and this is used with assets to quickly build an asset hierarchy and its spare parts. There is also a setting to add an item to the asset spare parts whenever it is used on an asset.

The Inventory application is where balances of the item can be held in a storeroom. The Stocked Tools application is the equivalent storeroom application for tools. In the Inventory application balances can be held for the same item in multiple bins. The balance of items can also be held at the lot level which would be used for chemicals and paints with a shelf life. Item balances can also be recorded against people, for example the custodians of tool assets, and transit locations like couriers and shipping/cargo agents. Some items might be metered, for example fuel used for vehicles.

Logistic functions are supported using two applications Inventory Usage and Shipment Receiving. Inventory Usage is a document that can be used for issues, returns and transfers. It is an application that can be workflow enabled using Maximo’s built-in workflow capabilities, most Maximo applications can be workflow enabled. The Inventory Usage document can go through staging and shipping steps. Staging is used when items are picked and added to a staging bin waiting to be collected. Shipments are used with transfers and create a shipping record which is then received into the destination storeroom using the Shipment Receiving application. Item availability is provided throughout Maximo wherever an item field exists providing the storeroom balances, reservations and staged quantities, and the purchasing documents where the item is referenced.

Contract

There are four main applications in the Contracts Module. The Purchase Contract application is used for purchase, price and blanket contracts. When an item is raised on any of the purchasing applications Maximo will identify whether it exists on one or more active contracts. These are the types of contract that are used in the Purchase Order and Receiving applications.

The Lease/Rental Contracts application is used with assets which are leased or rented from a vendor. The main difference between the two is that a lease contract has options for returning or buying the asset at the end of the lease period.

The Warranty Contract application also supports Service Contracts. These are both asset or location based. When a warranty contract is set up then a warning will be shown on the work order when the asset or its descendent assets is referenced. Service contracts can occur after warranties expire and can also be used on work orders. 

The Labor Rate Contract application is used for defining the vendor rates for different crafts and skill levels including the ways that overtime rates will be calculated. This type of contract will require time being reported against a work order by crews or labor.

The lines of Purchase Contracts can refer to material, service or tool items. Lease/Rental Contracts refer to material or tool items that are marked as rotating which can have assets. Warranty (or Service) Contracts can only reference services. Labor Rate Contracts refer to Crafts. A Work Order can reference a valid Warranty (or Service) Contract. When planned materials or services on a work order are purchased via a purchase requisition, they can consider and reference valid purchase contracts.

The Request for Quotations (RFQ) application is used to obtain quotes from multiple vendors. When the RFQ is awarded, a contract can be created. 

In Maximo invoices may not have had an originating purchase order. Lease, rental, warranty, service and labor rate contracts can all generate invoices waiting to be matched to an incoming physical invoice from the vendor. Service based invoices can also be created directly in the Invoices application, for example where the vendor works from site and the authority to spend is on a work order, the vendor may only have a master framework contract in this case.

Each contract type has a set of properties and a set of terms and conditions. New contract types can be created that use specific properties or terms. There is also a Master Contracts application which can contain the terms and conditions that will apply to all contracts associated with it.

Purchase

The procurement applications in the Purchasing Module follow the processes from requisition through to invoicing. Which of these applications are used depend on whether there is financial integration to an ERP or financial system and then the agreed interface points between those systems. Maximo comes as standard with inbound and outbound integration objects for the supply chain processes of Maximo whether as part of Inventory or Procurement.

Desktop Requisitions is a set of self-service applications for all users of Maximo. The principle one, Create Requisition, guides the user through the process of creating material reservations or ordering new parts or services. When the requisition has been submitted it will create storeroom reservations or inventory usage records waiting to be issued, and purchase requisitions or purchase orders for items needing procurement. Similarly, a work order will create inventory or purchasing demand when it is approved.

The Purchase Requisition (PR) and Purchase Order (PO) applications are similar, centralised purchasing is supported on the purchase order. Both have multiple lines which may indicate that a contract exists for the items, both can reference a purchase contract in the header in which case the selectable items are those that belong to the contract. 

The Request for Quotations (RFQ) application is used to obtain quotes from multiple vendors. PR lines are copied to the RFQ and as quotations are received the prices are entered. Vendor and item analysis can then be performed to determine how the RFQ will be awarded and one, many or all RFQ lines are then copied to a PO or purchase contract.

The Receiving application is used to receive material or service lines against a PO. The receipt of materials can require inspection and if it is an asset then the serialization process will create the Maximo asset records. 

The Invoice application is where financial transactions flow through to an Accounts Payable ledger in a financial or ERP system. Invoices made against purchases can be either two or three way matched and once matched the cost may be distributed across multiple general ledger accounts. Standard Services, like freight can be prorated against other invoice lines. Credit and debit notes and invoices supporting consignment inventory are all supported.

Service

Maximo provides service desk functions with the Service Request (SR) application, an SR is a type of ticket. The SR is classified, and this is used to provide additional questions related to the type of service being requested. The service request can spawn one or more work orders which are handled in the Work Order Tracking application and there are multiple options for how a work order is created from the SR. Incidents are often handled in the SR application, although clients who use the HSE add-on will also be entitled to use the ITIL based Incident and Problem applications. Tickets and work orders can be related to each other. Tickets can also be deemed global, for example several people call-in to report that lights have gone out in an area.

SRs can be reported from a self-service application available to all users or integrated into the company portal. Maximo also has an email listener which would allow requests to be raised by email and automatically transferred to create a SR. Common service requests and incidents can be better supported through a ticket template which should reduce the processing time of a service request by at least 50%. These common requests can be made available to users to make the creation of a service request as painless as possible.

Complex requests may have multiple activities where those activities can be defined to run serially or in parallel. Ownership at group and individual level is tracked for both the SR and the activities. A user can always see the work they need to respond to whether tickets, activities or work orders through the Work View application.

Service Level Agreements (SLA) can be applied to the ticket, work order or activity. This calculates target dates for each record based on the commitment. SLAs are monitored through an escalation which can raise a notification if an SLA breach is approaching. The performance of an SLA can also be monitored over time using a Key Performance Indicator (KPI). 

Service Management extends across both tickets and work orders. Email communications can be generated to keep the originator and other stakeholders abreast of the service request or incident. Log notes added to a work order will be visible from the originating ticket and can be made visible to the originator of the service request. Status changes on follow-up work can update the status on the originating ticket. Tickets and work order records have similar functionality and are closely tied.

A solution is where a knowledge base would be established and are searchable by all Maximo users. Solutions can be applied to Incidents and Problems.

Planning

You plan work with a Job Plan and apply this to a work order to create a work plan. A job plan can be considered a template for a work order and consists of the sequence of tasks, and the labor (craft and crew types), materials, services and tools needed to perform the work as a whole or for each task. A job plan can have a nested job plan which when applied to a work order creates a hierarchy, ideal for a small project. Dynamic job plans flex the resource requirements depending on the number of work units to perform. 

Preventive Maintenance records generate work orders on a time and/or meter-based frequency and are associated with one or multiple job plans. For a 3 monthly PM with a different set of tasks to be performed yearly then two job plans will be required, with the yearly job plan including the quarterly tasks. Seasonal based PMs are supported, to avoid PMs on critical equipment being generated during busy periods. PMs can also exist in hierarchies that produce a work order hierarchy. A Master PM acts as a template for Preventive Maintenance records. The Master PM can be associated with a rotating item defined in the Item Master application, an Asset Template, or directly associated with a PM if it already exists.

Inspections, including the capture of measurements or observations, can be handled through job plan tasks and linked to a Condition Monitoring record which can generate corrective work orders if the measurement exceeds action limits, or a certain observation is made. When a work order is generated, it uses a Job Plan or a PM.

Inspections can also be handled using a Route that defines the set of locations and assets that will be visited as part of the inspection, each route stop may have a different job plan. Inspections can also be scheduled to run periodically by using a PM that references the Route. A wider range of inspections can be handled using the Manage Inspection Forms work center. Sets of inspection questions can be dynamically added depending on the answer to a previous question. Inspection Forms are associated with Locations and Assets.

A Safety Plan consists of the hazards and the precautions to take to mitigate the hazard, and the isolation procedures defined in the Lock Out / Tag Out application. A safety plan can be associated with a job plan and the asset or location that it is designed to be used with, known as the work asset. The Safety Plan is applied to the work order when the Job Plan is applied to the work order.

The Job Plan defines the Craft or Crew Type requirements to fulfil the work order or each task and these get copied to the work order when the job plan is applied, assignments are automatically created. A craft is a work discipline, for example mechanic or electrician, and it may have multiple skill levels. A person defined in the People application may have a Labor record which can have one or multiple crafts and skill levels, that define the hourly rate to be used on a work order. People can also be added to one or more Person Groups, the teams in which they work.

A Crew record is an instance of a Crew Type, a specific crew with the required crafts, tools and qualifications that are needed to perform work. Labor are assigned to crew positions for a period of time. Both Labor and Crews can have an associated calendar and shift that defines normal work hours for each shift day. Periods of unavailability or additional hours modify these shift hours and together they define the availability of the labor or crew. When you assign labor to a crew you can see whether the required crafts, tools and qualifications have been met and also whether the labor and crew are available in the same shift as when the work will be performed.

Locations and assets exist within work zones, typically a geographic area that labor and crews are assigned. When work assignments are made the labor and crew that can be assigned are those that match the work zone where the work will be performed.

Work

All types of work are planned, assigned and completed in the Work Order Tracking application. Frequency based work orders and inspections use a time and/or meter-based preventive maintenance record, the work type is normally PM. Corrective Maintenance work orders may be generated when a Condition Monitoring measurement exceeds its action limits or when an observation of a particular value is made, the work type is normally CM. Emergency work orders with a work type of EM may be created from a Service Request. Capital project work orders may be created directly in the Work Order Tracking application, normally with a work type of CAP.

A work order can reference one or multiple locations and assets, inspections of the same type may be performed on multiple assets. A work order can exist as part of a work package of two levels, or in a work order hierarchy where there is only a practical limit to the number of levels. A work order can also have a series of tasks. The work plan is the labor, materials, services and tools needed to perform the work order. If materials are stocked, then on work order approval a reservation is made on the storeroom selected to fulfil the requirement, the same can also apply for a tool that is held in a storeroom. If materials are not stocked, then they will be purchased, services also follow this procurement route. 

Work is assigned to individuals (referred to as labor) or crews, matching the planned craft or crew type requirements. During the assignment, the shift hours and work zones can be considered, for example is the technician being assigned available at the scheduled time, do they normally work in the area where the work needs to be performed. By using availability, you ensure that the estimates on the planned work can be undertaken by the assigned labor, or crew. The assignment process is looking to maximise the amount of work performed within the availability on any one workday. Work assignments can be made in various applications, Work Order Tracking, Assignment Manager or from the graphical applications available with the Maximo Scheduler (see later).

There is a desktop application called Quick Reporting which is designed for technicians needing to complete the work which has been assigned to them, this also allows them to report work which they did while on site which may not have been planned. When completing work, actual time, materials and tool usage is recorded, meter and measurement values are entered, and if relevant asset downtime and failure reports made. It is the comparison of the plan versus the actual which is important during work management.

For geographically distributed work the Work Order Tracking application has a map tab, this can display the current geographic position of the individual or crew using Maximo’s location-based services which are used by the Technician application, a part of Maximo Mobile (see later). The Work Order Tracking application also supports work on linear assets and work on instrument calibration (see later).

The Labor Reporting application is used to enter time against work orders and tickets, it may be entered by the technician, supervisor or an administrator if time records have been submitted by a vendor or time is being entered for a crew. If Maximo Mobile is being used, then time is collected by starting, pausing and stopping a timer on the work order. The Labor Reporting application can also be used if corrections or approvals are necessary, or time needs to be recorded when it is not against a work order or ticket.

There are a number of role-based applications that use the same technology as that being used for Maximo Mobile. The Technician, Inspections, Work Approvals and Service Requests will be discussed as part of the slide on Maximo Mobile they have similar functionality, the difference being that Maximo Mobile will work offline (or online), whereas the role-based application use a browser and only work online. However, recently IBM has started work on a role-based application called Work Orders which aims to be a simplified version of Work Order Tracking, as of MAS 8.11 it is not yet complete, but it has made significant progress.

The least used application is called Activities and Tasks. A ticket (service request, incident or problem) may have multiple activities, and work orders can also have multiple tasks. Therefore, this application is used when the activity or task to be performed is part of something else. It is most likely to be used as part of service management. 

Financial

Throughout Maximo financial transactions can be generated with general ledger (GL) accounts. There are defaulting rules to derive the GL account on both the debit and credit sides of a financial transaction and where the GL account is not complete a navigator is used to help the user select the right codes. 

The GL account is made up of multiple segments and each segment has a set of values and descriptions. The code combinations and their descriptions can be stored and then used for validation. Both are defined in the Chart of Accounts application which exists at Maximo’s organization level. The structure of the GL account is also defined at the organization level, it is therefore possible for a single Maximo instance to service multiple ERP or financial systems.

Financial transactions are posted against financial periods that are also set up in the Charts of Accounts application. The GL segment values, GL code combinations and financial periods can all be interfaced from an ERP or financial system. The organization supports two base currencies and transactions may need to use the effective exchange rate, also held in Maximo. 

The Cost Management application supports integration from a financial system that has a projects ledger. The cost management records normally represent work breakdown structure elements and will be selected on the top level of one or more work orders that represent a work package. Financial transactions include both debit and credit GL accounts, a financial period and a cost management project identifier and they appear in various places across a work order, a purchase document and in inventory.

Maximo supports asset depreciation schedules, and asset depreciation can also derive the GL accounts to be used. 

Maximo has a Budget Monitoring application for setting and monitoring budgets against estimates, commitments and actuals. This is not limited to budgets set at GL account or GL segment level but may be set for a location, asset, or project identifier. As part of the Assets application there is an action Roll Up Maintenance Costs which will take unprocessed maintenance costs from across Maximo and roll them up to totals on the asset and its asset hierarchy. This can be automated on closure of a work order.

Analytics

The Maximo Start Center is an operational dashboard with tools for configuring it. There are several portlet types. The result set portlet utilises queries created in Maximo applications to fetch a set of records, and this can also be pictured in pie or chart form. The KPI list or KPI graph portlets display the results of one or more KPIs using traffic light colours to represent a warning or action. The KPI can also be generated as a result of a query. In the KPI Manager application a KPI can be scheduled to run at a chosen frequency or immediately and the value recorded will be maintained in history so that a trend is created. The trend of multiple KPIs can also be viewed for comparison purposes. The KPI Templates application is used to generate multiple similar KPIs that differ only by the values selected and a KPI Viewer application can show all a user’s KPIs in one colour coded list, ideal for using from a browser on a smartphone.

Maximo is supplied with a wizard driven ad-hoc report writer, this is an end-user’s tool for generating a listing or detail type report, it is not possible to generate graphical reports using this tool. The standard set of Maximo reports is created using BIRT, these are mostly analytical based. The Maximo Report Administration application provides control over security and performance, for example defining limiters or setting the schedule when a report will run. It is where report parameters are defined, which lookups and default values will be used, it is also the application where the report request page is generated. Reports can be saved and distributed as PDF or viewed from a Start Center portlet or from the Report Viewer application.

A Maximo license entitles the owning organization to download and install Cognos 11 Analytics for use with the Maximo data. This allows up to three power users to create their own analytics and dashboards and to do this iteratively testing the output with stakeholders at each step – a term that is called agile analytics. Cognos Analytics supports descriptive, predictive and prescriptive analytics. 

The Operational Dashboard and Work Queue Manager as of MAS 8.11 are still being developed. The Operational Dashboard is a modernised application that is nearly equivalent to a Start Center but has not yet been built into security and there is no ability yet to create Operational Dashboards and assign them to users. The Work Queue Manager is like the queries that can be created in applications but is currently restricted to work orders. Both are likely to be enhanced in the next release of Maximo Application Suite and they lay the foundation for further improvements into the future.

The Start Centers, Operational Dashboards and KPIs are designed to support operational use of Maximo. Cognos Analytics has been provided for Management Analytics. There is integration between Maximo and Cognos Analytics.

Configuration

Maximo has a rich configuration toolset. All configurations are stored in the Maximo database and are mostly maintained during an upgrade, a utility will need to be used to migrate screen changes.

Maximo has its own Workflow engine and workflow processes can be enabled on any Maximo application. The Task nodes make the assignments to people or person groups, a role is used to make these assignments dynamic. The assignments may send an email using a Communication Template or the user might monitor their workflow inbox for the assignments they need to perform. Workflow may also perform actions which might change status, set a value, perform an application action, for example apply an SLA, or execute a custom action written in Java or a script. The Escalations application uses some of the same elements as workflow, but this is based on monitoring the database for a condition to occur and then performing a set of actions and notifications in the background when it does. 

The Database Configuration application makes changes to the object layer and their underlying data tables, views can also be created. This is the application where you define electronic records (auditing) and electronic signatures (confirming who you are), and where you create formulas and associate them with objects or attributes. It is also the place where the relationships between objects and all messages are defined.

The Application Designer application is where you can modify the user interface (UI) of the application, its dialog boxes, the actions, toolbars, lookups, menus and hover-over dialog boxes. Each of the UI elements can be bound into the security layer of Maximo and set to conditionally display or conditionally change its properties, for example, hide or display a set of fields when a condition is met, display text in red when it is an emergency work order. The Maximo Application Framework is being used to develop Maximo Mobile and the Role-Based applications, it runs in a container using Docker. This is still under development and is XML based, with some visualisation.

The security framework is controlled through the Security Groups application. A user belongs to multiple security groups and each security group builds up a layer of security. The security group provides access rights to Maximo applications and their actions, Start Centers, Storerooms, GL Components, Labor, and Integration Objects. Data security can be controlled at the record or attribute level. 

The Domains application defines sets of ALN and Numeric values which are used with lookups. Numeric Range Domains are used to set a range of values, for example a percentage between 0 and 100 to 2 decimal places. A Table Domain creates a set of values that can be defined by a query from other data in Maximo and a Crossover Domain does something similar but then copies data from the source object record to the current record. For example, a crossover defines what is copied from the service request when a work order is created. 

Migration Manager is a set of applications used to control how configuration data is transferred between the development, test, and production environments. It also migrates some other low volume data but not all data in Maximo can be or should be migrated using Migration Manager, it depends on the complexity and volume of the data.

Customization is performed by extending Maximo’s Java classes or developing Automation Scripts. There are advantages and disadvantages with each, but whichever is used this is the area which should be tested most when upgrades to Maximo are provided. IBM’s policy towards extending the application and feature set of Maximo is to do this incrementally, with release of feature packs, roughly once per year, to add new functionality without changing the existing data. Customization will also be mostly handled as part of an upgrade unless the new Maximo functionality cuts across your custom code. Customization isn’t wrong if it is contained to reasonable levels. The more customization you have the more regression testing should be performed.

The Integration module has a comprehensive suite of integration applications, both inbound and outbound, including REST resources for queries and updates of application data by external applications. Data loading is also performed through the Maximo Integration Framework (MIF). The integration applications are used in the Maximo product, for example Maximo Mobile uses the Object Structures. Maximo comes packaged with many pre-defined object structures which is the starting point for integration points. 

Included Capabilities

As part of Maximo Application Suite there are a new set of capabilities in Maximo (Manage). The first four of these, Maximo Linear, Maximo Calibration, Maximo Mobile and Maximo Scheduler were all add-ons in previous versions and had to be separately licensed. Licensing has been simplified in Maximo Application Suite and as a result these are all now included. If you are going to use a non-IBM mobile product against the Maximo database, then each user will require at least a Limited type of license, the same license is needed for someone using Maximo Mobile.

The Reliability capability introduced Reliability Centered Maintenance (RCM) to Maximo in MAS 8.11. You’ll find there is currently only one application, but this will be built upon in the next few releases. Officially, it is considered an add-on, an installation is required, but it does not require additional AppPoints or 3^rd party licensing, therefore it can be considered as an included capability, and I expect it to become a part of the base installation at some point. 

Linear

Linear Assets is now part of Maximo it is no longer a licensed add-on. Roads, pipelines, and rail tracks are examples of linear assets where if work needs to be performed you need to indicate the position along the linear asset to perform that work. Linear assets have a linear referencing method which can be used to position a point or a segment between two points in three dimensions, x, y and z, where the x dimension is parallel with the linear asset, y is at a tangent, and z is a measure above or below the linear asset. The important aspect here is that you determine where work is performed based on a measure, for example 100m past the 57km marker post on a road. The marker post is a reference point. Work on electric transmission or distribution lines is given by referencing the tower or pole, which will be point assets (or locations), work tends to be performed on the tower or pole, and rarely between them, therefore you need to consider whether the linear assets feature should be used, if measurements are not important.

The Linear Assets functionality touches many parts of Maximo, including the Assets application where the asset is marked as linear. The km marker post is an example of a point feature, and features are added to the linear asset with the measures that position it along the linear asset. Features can also be linear, as a guard rail at the side of the road would be. Relationships are used to connect one linear asset with another, or with a non-linear asset or location. For example, another linear asset crosses the linear asset at a measure, that measurement can use another feature if it has been marked as a reference point, as a marker post would be.

A classification is added to a linear asset to create a specification, but the attribute values in the specification may change over the length of the linear asset. For example, the road speed limit, or the road surface material may change several times. The same attribute may be referenced multiple times with the measurements where the value of the attribute changes. It is different for asset meters; while the asset meter can be positioned along the linear asset, the same meter name cannot exist multiple times. However, when a meter reading is made, you can reference the measurement along the linear asset, so you can take many measurements at different places along the same linear asset. 

Preventive Maintenance, Routes and Service Requests can all reference the start and end of a linear segment. For Service Requests the start and end of a linear segment may be entered multiple times using the Multiple Assets, Locations table. Linear segments are supported on the Self-Service Create Service Requests and View Service Requests applications allowing any user to indicate an issue on a linear asset. The linear details are copied over to the work order, either Work Order Tracking or Quick Reporting can be used. Work orders also allow you to add progress along linear segments.

The Assets application has a linear visual control panel at the bottom of the Specifications, Features, Relationships, and Work tabs. It shows a ruler along the top representing the length of the linear asset and beneath shows the position of each feature, or relationship, bars representing the length where a specification attribute value applies and the point or length where a work order needs to be performed, or where a service request has been raised, for example to reference the position of a pothole.

If you are using Maximo Spatial the linear assets can be visualized on a map with change of colour indicating segments of the linear asset. It is a feature called dynamic segmentation where the segments may represent a change of specification attribute, a feature, or work.

Maximo Mobile does not yet support linear assets; some parts of the linear functionality may start to be supported in the MAS 9.0 release in summer 2024.

Calibration

Calibration is now part of Maximo it is no longer a licensed add-on. It is used for the calibration of instruments and the calibration of the standards, the measurement and test equipment used in the calibration. The instruments are defined in the Assets application in Maximo, the standards, and measurement and test equipment are defined in the Tools application, but they are marked as rotating so that assets are created for each piece of measurement and test equipment.

Calibration checks are normally set up on a frequency basis using a Preventive Maintenance record that generates a work order which is where the calibration results are recorded. Control is provided over the number of PM extensions that are allowed and if the PMs are linked to a Master PM, then you can view the PM extended dates across all the PMs. The Job Plan used by the PM will reference the tools to be used, the type of measurement and test equipment. On the work order you reference the actual tool used, so that if later something is found to be wrong with calibration status or accuracy of the measurement and test equipment then you will be able to check back to see which instruments were calibrated using the tool standard, a process called reverse traceability. This is performed from the Assets application using the action View Tool Usage.

The Data Sheet Template application is where you define the calibration points and identify one or more asset functions. For each asset function you define the input and output parameters and accuracy tolerances for the associated equipment which you reference as Work Assets. The Data Sheets are referenced on a Job Plan with the Work Assets, and when the Job Plan is applied to a work order the data sheets for the asset on the work order are copied and will be found on the Data Sheets tab in the Work Order Tracking application. The records of the Data Sheet Template are under revision control so that you can prepare the changes and go through an approval cycle.

On the work plan of the work order the required measurement and test equipment will be referenced, copied from the records on the Job Plan Tools. You can check the tool status and perform a spot check on the tools being used on the work order. From the Assets application for calibration assets that are also tool assets, you can view the history of spot checks.

The Location application is used to define a group of instruments (assets) which are calibrated together, referred to as loop calibration. The input and output of all instruments in the group will determine whether the calibration is successful or not. You can move multiple instruments (assets) to a Loop Location. You can attach data sheets to the loop location.

There may be several assets or standards (tools) of the same type where the calibration requirements are the same, or similar. An Asset Template represents a type of instrument defined at the level of a manufacturer model. Calibration Details can be defined, and Data Sheet Templates associated. The Asset Template can then be used to generate assets or update existing assets with the same details. 

When performing the calibration in the Work Order Tracking application you record the As-found data, calculations are performed by Maximo to establish whether the measurements are in range. If outside the limits adjustments can be made to bring the instrument back into range and the As-Left results are recorded, creating a calibration history that is stored in Maximo. The Work Order Tracking, Locations and Assets applications allow you to View Calibration History.

You can assign qualifications to tools so that technicians are qualified to use the measurement and test equipment. A validation can be set up to warn or enforce the check that the technician performing the calibration has the qualifications associated with the tool.

Mobile

Mobile applications are something which need to change as technology changes. Maximo Mobile is the current suite of mobile applications. In MAS 8.11 the previous mobile suite Maximo Anywhere is no longer an installable component, it was installable up to MAS 8.8. The functional footprint of Maximo Anywhere has not yet been replicated, and there are a few gaps, most of which are expected to be closed by the MAS 9.0 release in summer 2024. Current Maximo Mobile gaps include Calibration and mobile applications used by the industry solutions.

The same story applies to the Maximo Work Centers, they are being replaced by the role-based applications. There are three applications which remain, Manage Monitoring Information is an application to help administrators manage the Maximo system, not all the functionality of Manage Inventory has moved to the Issues and Transfers role-based application yet, and there is no replacement for Manage Inspection Forms, which allows Inspection Forms to be designed. New role-based applications are expected for all three in the MAS 9.0 release in a few months. Even when MAS 9.0 has been released, there may still be a few gaps if you did a feature-by-feature comparison between the Work Centers and their replacement applications.

The Maximo Mobile applications in MAS 8.11 exist in two forms, as Role Based Applications which are browser based and only work online and a native single mobile application which works both offline and becomes online when a connection is found. When you enter the mobile application, you enter the Navigator which displays each of the applications. A mobile user downloads the application from either the Apple App Store, Google Play Store or from the IBM portal if Windows 10 or 11 is being used. 

The Maximo Mobile and Role Based Applications have been developed using the Maximo Application Framework (MAF), which is based on IBMs Carbon Design System which is being used across all IBM software products. It is based on React js and provides a responsive user interface that flexes based on the device being used and its orientation. When comparing a Maximo Mobile application and its Role Based Application equivalent, they use the same code, but there may be slight differences if you look close enough, for example in Inventory Counting there is no reconcile capability in the Maximo Mobile application whereas it exists for the Role Based Application, because you need to be online to reconcile inventory. The Maximo Application Framework provides tooling for configuring how the application looks and behaves, the framework is still being developed, but it has already come a long way and it is expected to eventually have a greater capability than Application Designer.

The Maximo Mobile applications are set around Work, Inventory and Asset.

• For Work there are applications for creating Service Requests, a supervisors application called Work Approval, the main Technician application for work execution and the Inspections application for conducting an inspection created by the Manage Inspection Forms Work Center. 
• For Inventory there are three applications. Inventory Receiving supports both the receiving of material purchases and receiving of storeroom transfers, Shipment Receiving. Inventory Counting performs the physical counts which may have been defined in the Count Books application. Issues and Transfers is the latest of these applications and performs issues and returns, but not yet staging, or shipping during transfers. 
• For Assets there is an asset data collection application.

There are two other Role Based Applications for general use. Work Orders is a simplified version of Work Order Tracking and Workflow Assignments is an application for responding to or reassigning workflow requests. 

Map capabilities were designed in from the beginning of Maximo Mobile and there is already support for both Assist and Visual Inspection. Barcode, QR code, NFC tags, GPS tracking, electronic signature, physical signatures, and push notifications are all capabilities. You can also share a mobile device between users without sharing the data.

Maximo Everyplace is browser based and preceded Work Centers, it uses Application Designer, and the applications can still be found there.

Scheduler

The Maximo Scheduler is now part of Maximo it is no longer a licensed add-on. It added the Planning and Scheduling module and the Scheduler Administration module found in the Administration module. The applications are associated with scheduling, assigning and dispatching. Planning aspects are performed in core Maximo applications the principle one being Job Plans, you will need to plan work orders to make an effective use of the Scheduler applications. All the scheduling applications are graphical and functionally rich.

The Graphical Scheduling application is for long to short term planning, there is a Gantt chart with histogram below showing the resource loading versus availability for the work orders included in the Gantt chart. Short term planning is best handled by using a rolling project where the work queries pull in work orders scheduled within the next 2-4 weeks. Graphical Scheduling will include the resource requirements of PMs without generating the work orders and will also support the scheduling of work for a set of locations or assets. Network dependencies are added between work orders or tasks allowing the critical path to be shown, float is also calculated. The Graphical Scheduling – Large Projects application might be used when the number of work orders goes above several hundreds and would be used for outages and shutdowns.

The Graphical Assignment application is for short term planning, typically within 2-3 weeks and the assignment of labor and crews to the work order assignments, it has three views. The Work View and Assignment View are both Gantt chart based, a supervisor would use drag and drop functions to assign the labor or crews to the work assignments. The Dispatch View shows the labor and crews assignments visually on a day calendar and map, it takes into account the travel time between work assignments. Using Maximo’s location-based services the latest geographic position of the labor or crew can be displayed along with new emergency work that needs assignment. The dispatcher graphically reassigns work to meet the new demand and street level routes for the labor and crews can be recalculated. With integration the dispatcher can see where there are weather alerts.

The Graphical Work Week application is used for scheduling and assigning work with a focus on the current week, or the next. It shows a Gantt chart of work assignments with a table of remaining hours for each Labor and Crew below. You can easily change availability by double-clicking in a resource cell and entering a reason code, holiday, sick, extra time, etc. Reason codes show up as a different colour. An assignment is also made by double-clicking or using selection boxes. Each resource shows the percentage allocation for the week. Assignments can be emailed or exported to a calendar (.ICS).

The Graphical Resource View application is focused on planning the availability of your Labor and Crews. It is a monthly calendar table with the resources as rows, each cell showing the shift that the labor or crew is working making it easy to see shift rotations. Holiday, sick, or extra time can be assigned across multiple days with a few clicks. Each reason code shows up as a different colour. Training can also be booked for multiple persons with a few clicks. No need to use a spreadsheet or wall planner to plan vacation schedules.

The Graphical Appointment Book application is normally used by a service desk to make appointments against fixed time slots during the day. Notifications are made to confirm the appointment, a reschedule, a cancellation or the estimated time of arrival. With integration the service desk can use weather data to help minimise cancellations and rescheduling.

The Graphical Assignment Repair Facilities application is also used for short term planning and assignment. A repair facility is used by transportation assets and might be a garage, railway shed, shipyard, or airport hanger. The repair facility is a location, and it has a number of slots or bays where work is performed on the mobile asset. A work order can be assigned to one or more repair facility bays and labor or crews assigned that work at the repair facility. 

The Graphical Crew Management application is used to assign labor to crew positions which require a type of craft. This is for week ahead crew management considering the unavailability of labor due to holidays, and the day-to-day management of the crew for short notice absences due to sickness and other reasons. 

The Optimizer add-on is used with Graphical Scheduling and Graphical Assignments applications. It is an optimisation engine that performs resource levelling, capacity planning, automated assignments including considering geographically dispersed work and there is also a model for handling the emergency work scenario, reworking remaining assignments to accommodate the new priority work. Optimizer is also used with Maximo Health for Asset Investment Optimization.

There are two dashboards which started to be added from MAS 8.9. The Scheduling Dashboard looks across one or multiple Graphical Scheduling projects and identifies where there are resource issues or data issues. From the Scheduling Dashboard you can make changes and run the optimizer adjusting any parameters to see the results. The Dispatching Dashboard was introduced in MAS 8.11, and it looks across one or multiple Graphical Assignment projects and identifies issues and allows the optimizer to be run with different parameters. The dashboards are the start of the modernization of the scheduling user interface. They require the Optimizer to be installed.

In the Administration module is the Scheduler Administration module, a set of applications to support the graphical applications. Appointment Book Manager is where the appointment slots are defined. Scheduling Alternate Resources is used with Graphical Scheduling and Graphical Scheduling – Large Projects to set the availability which projects will use, when planning into the future resource availability may not consider holidays or additional subcontract resources. Schedule Data Manager will highlight common issues in your data effecting the graphical applications and allow you to correct those issues. There are two applications for configuring tooltips and weather forecasts if there is integration to the IBM Environmental Intelligence Suite.

Reliability

In MAS 8.11 IBM introduced the Reliability Strategies application, a starting point for introducing Reliability Centered Maintenance to Maximo. Reliability Strategies is a library of failure details for over 800 asset types which has come from numerous RCM studies performed by experts over many years. It contains over 58000 failure mechanisms and provides their mitigating activities and frequencies. Currently there is just the access to the library, IBM acquired the Asset Strategy Library in 2023. MAS 9.0 is expected to see the ability to download from the library or create your own asset types, failure modes and mitigation activities.

Maximo Manage Product Portfolio

This slide shows the product portfolio of Maximo Manage (the bigger picture); you may have seen this in the Maximo Application Suite overview.

Maximo is available both on-premise or cloud based with availability on Microsoft Azure, Amazon Web Services or IBM Cloud. There are three SaaS offerings, Essentials for small businesses, Standard and Premium. What allows it to work across the enterprise is the multiple organization and multiple site data structure.

We have already discovered that core Maximo is a set of tightly coupled applications for managing assets, inventory, contracts, procurement, service, planning and work. There are applications to support financial integration, analytics, and wide-ranging configuration capabilities including workflow. Maximo is often customized and there are tools available to support both live changes or those requiring a maintenance window, these include migrating the changes between environments. 

With Maximo Application Suite there were changes to the software license based on AppPoints. The products which have a magenta colour are now included in Maximo; Linear, Scheduler, Calibration and a suite of mobile applications called Maximo Mobile, I call these the included capabilities, but I also include Maximo Reliability Strategies because I do not believe it will stay as an add-on for long.

Maximo can be extended with Industry Solutions for Transportation, Nuclear, Utilities, Oil and Gas, Aviation and Civil Infrastructure. These are additional sets of applications and changes to core Maximo applications to support a particular industry. In some cases, the functional footprint of these industry solutions is quite extensive. The add-on products also extend core Maximo and can be used with the Industry Solutions, but they are not specific to any one industry. 

• Health, Safety and Environment (HSE) is a large subset of the Oil and Gas Industry Solution and would be used to extend Maximo towards meeting ISO 55000 standards. 
• Service Providers is used where there are external or internal customers where the billing of work or usage/lease of assets is required. 
• Asset Configuration Manager is for the management of complex assets, particular those which may get maintained by different parties and where there is a need to understand the differences over time between as-designed and as-built, it is mainly used by aviation and train companies. 
• Spatial is the integration of ESRI’s ARCGIS in Maximo. It allows users to plan work in a spatial context. Core Maximo also has mapping capability using Google, Bing or Open Maps.
• Optimizer runs schedule optimization models developed in IBM CPLEX Studio. Models are provided for capacity planning, resource leveling, labor assignment and spatial scheduling. Optimizer is also used in Maximo Health for Asset Investment Optimization.

Maximo IT is the most recent add-on and needs a bit of explaining. In 2006 after the IBM acquisition, a group in the IBM Tivoli division set about enhancing Maximo for IT services including those being undertaken by the Global Technical Services part of IBM on behalf of their customers. The product evolved and was until recently called IBM Control Desk (ICD). There are several Maximo clients who have both Maximo and ICD, they have always been able to coexist on the same platform and database, and they use the same configuration and integration applications. I find it easier to consider Maximo IT like an Industry Solution, a large suite of additional applications and functionality which is primarily designed for IT departments and DevOps. However, there is convergence between IT and OT (Operational Technology) the digital information being created by physical assets, and this is applicable to many industries and hence it is being considered an add-on. Bringing Maximo IT into the suite makes a lot of sense.

Maximo has a Connector for SAP including to SAP S/4HANA, and a Connector for Oracle Applications. These provide a wide range of integration points depending on the process split between Maximo and SAP/Oracle. For integration to other finance systems the Maximo Integration Framework (MIF) is used, a part of core Maximo. There is a relatively new Connector for Workday Applications, which does not yet have the same integration points as for the SAP and Oracle Connectors. This uses a product called App Connect which comes with the Maximo Application Suite. App Connect is also being used to provide both the Connector for TRIRIGA, an Integrated Workplace Management System (IWMS) used by real estate and facilities teams to manage a portfolio of building and ground assets, and the Connector for Envizi ESG Suite which pulls together Environmental, Social and Governance (ESG) data across the enterprise for analysis and reporting. Envizi supports the European Union’s CSRD rules to report sustainability disclosures. 

The Maximo Reliability Strategies add-on was also recently introduced in MAS 8.11 and is the start of Maximo’s support for Reliability Centered Maintenance (RCM). It currently consists of a single application that provides access to a large library of RCM studies across 800 asset types, and 58000 failure modes, suggesting over 5000 Preventive Maintenance activities along with the step-by-step tasks to be performed.

There are a set of Integrations to:

• Cognos Analytics 11.2.4. Maximo clients are entitled to use Cognos Analytics when used against the Maximo database, however there is a restriction to three IBM Administrative Base Users who can create/edit dashboards and reports.
• Maximo Archiving is an archiving solution for the transactional records of Maximo like work order and ticket. It uses IBM’s InfoSphere Optim Data Growth Solution which must be separately purchased.
• Environmental Intelligence Suite is a SaaS platform to monitor, predict, and respond to weather and climate impacts. It is mostly, but not exclusively used with electric utilities for outage predictions, vegetation management, renewables forecasting and alerting field technicians to weather conditions. It is also used in conjunction with Envizi and IBM Planning Analytics to provide an Enterprise Carbon Management Software solution and was recognised in the leader quadrant of Verdantix Green Quadrant: Enterprise Carbon Management Software 2023.
• MRO Inventory Optimization is a cloud platform suited to Maximo clients who wish to optimize their Maintenance Repair and Operations (MRO) inventory. It is now part of IBM Sterling Supply Chain Intelligence Suite.
• Maximo Accelerator Catalog is a way for IBM and its Business Partners to provide accelerators that extend the capability of Maximo. It was launched in MAS 8.11 with just a few products, but there is a rich ecosystem of Maximo Business Partners who have developed products over the years who may add to the catalog over time.

The road ahead for Maximo Manage

IBM produces a roadmap for Maximo Application Suite each year around March, with updates in the autumn and at other times. The next release of MAS is expected to be called MAS 9.0 and is due in the summer of 2024. I will provide a summary of what we believe will be in MAS 9.0 that effects Maximo Manage, but I’ll also look ahead with my crystal ball and the areas I believe IBM will be working on. This is not based on any inside knowledge, just an educated guess based on nearly 30 years working with Maximo, I think you’ll find the reasons I give as reasonably obvious. Those areas expected to be in MAS 9.0 are highlighted in blue text.

Mobile – The first area is to continue to build out the functionality of Maximo Mobile, at least to cover the functional footprint of Maximo Anywhere and the Work Centers, it is nearly there but there are some gaps. In MAS 9.0 the three remaining work centers are expected to be replaced, Manage Inspection Forms, Manage Inventory and Manage Monitoring Information. Support is also expected for mobile Calibration in MAS 9.0. For a long time, the Industry Solutions have wanted to develop mobile applications themselves, and I expect IBM will now start on this, replacing the few Anywhere applications, but also expanding to new areas. Support for linear assets on a mobile device is a gap which is expected to be closed.

Configure – IBM has started to create modernised applications starting with Work Orders and further enhancements to this is expected in MAS 9.0. The Operational Dashboard has already come a long way and now needs to be bound into security groups (MAS 9.0). I think longer term IBM would like a set of dashboards for the main core Maximo roles (Asset, Work Planning, Procurement, Inventory) with the ability to launch a modernised application, perhaps aimed at the smaller Essentials clients, but with a foundation that can be tailored for larger enterprises. I don’t think the classic application user interface will be replaced it would be a huge amount of effort to do so, but IBM may create a few additional role-based applications with Desktop Requisitions being an obvious choice. To support this, the Maximo Application Framework used to configure the role-based applications and Maximo Mobile will continue to be enhanced, extending beyond the capability of Application Designer. Longer term, a standard Data Loading tool has been mentioned a few times. Another topic will be to make more use of Cognos Analytics, perhaps resurrecting the Business Intelligence Packs that existed some time ago. BIRT as versatile as it is, now seems a bit old and I see it being replaced with Work Queues for tabular style, dashboards for simple graphics and Cognos for more complex business intelligence. 

Schedule – The Scheduling and Dispatching dashboards are new, and we’ll see these enhanced in MAS 9.0. Scheduling is an area where we see the top Ideas (RFEs) being developed and I don’t see that changing as planning, scheduling and assigning are areas that effect nearly all Maximo clients. Beyond MAS 9.0 the modernization of the graphical applications is likely to continue, and optimization scenarios are likely to expand towards the capabilities of Field Service Management products. MAS licensing will mean more clients adopting optimization and this will feed into future Ideas.

Reliability – IBM recently started its journey into providing Maximo with a Reliability Centered Maintenance capability, with the addition of a library of failure mechanisms for 800+ asset types, the application is called Reliability Strategies. In MAS 9.0 there will be the ability to create your own records, hopefully copy records to build your own library. In the future the RCM data will need to be linked to other Maximo data, starting first with being able to create Preventive Maintenance and Job Plan records. RCM is a continuous process where you learn from feedback and update the strategies, but updating those strategies may affect many assets so there needs to be a way of linking asset types with assets, so that changes update many records, linking to Asset Templates, and Master PMs perhaps.

IT – IBM Control Desk (ICD) has now been added into MAS as Maximo IT, but it is not yet compatible with all the Industry Solutions and add-ons that Maximo has, for example we discovered that Maximo IT and HSE could not be installed together. I expect IBM will want to bring the two products together, not just so that they can operate on the same platform, but to make it easier for existing Maximo clients to use ICD features, and vice versa. I think ultimately it would be better to treat Maximo IT as another Industry Solution, merging the licensing. ICD is likely to take advantage of Maximo Mobile and the role-based applications and there is likely to be development work supporting the IT/OT convergence, for example firmware/software updates on assets would usefully adopt ITIL service management processes, Incident, Problem, Change, and Release. Maximo IT will continue to be enhanced to support its client base.

Envizi+EIS+AI – The recent acquisition of Envizi and the provision of an adapter between Maximo and Envizi is likely to see changes in Maximo to support sustainability initiatives which will feed through to the ESG reporting in Envizi. The Environmental Intelligence Suite (EIS) is where the vegetation management and weather solutions now exist, and I think we will see Maximo and EIS coming closer together through integration. One might also think that the IBM Sustainability solutions will all start to come together over time. The MAS platform supports both AI and optimization, and these are two areas which will expand over the next several years in all parts of the Maximo Application Suite including in Maximo Manage. 

Thank you

I hope you enjoyed the presentation and now have an appreciation of the scope of core Maximo, the Maximo Manage element of the Maximo Application Suite. 

To summarise:

• Maximo Manage is the Enterprise Asset Management part of Maximo Application Suite
• It has a core set of capabilities which existing Maximo clients will be familiar with.
• Maximo Application Suite now includes the previous add-ons of Linear, Calibration, Scheduler and Maximo Mobile.
• Reliability Centered Maintenance (RCM) has been introduced with the Reliabilities Strategy application, a massive library of asset types, failure modes and mitigating activities, it just needs to be installed. 
• Licensing of Maximo has been unified to a single part giving entitlement to the Industry Solutions and add-ons like Health, Safety and Environment, Spatial or Optimizer.

Thank you for listening.