Join / Log in
Learn how to increase the operational efficiency of the assets you manage, and improve overall equipment effectiveness by using IoT data and AI.
Reduce the operational costs of the facilities you manage, and create more engaging occupant experiences through the application of IoT data and AI.
Learn how IoT data and AI are being applied to transform the end-to-end engineering lifecycle.
Speaking purely based on what I've seen in public roadmap sessions. Similar to Alex, I do not work for IBM. 1) Maximo Application Suite is taking a lot of existing products that were under the Maximo brand (some of them relatively recently renamed) and creating a more coherent solution that includes all of those products together. As an example, creating a single identity that all the products can utilize and enabling single sign on to each product so that it doesn't feel like you're using different products.As Alex mentions, the core Maximo product (along with industry solutions/add-ons) is referred to as Manage (which they separate Mobile & Scheduler into separate apps, but I still include mentally in this category), and there are Monitor, Health, Predict, Assist, Safety, & Visual Inspection applications that are added to that. These were previously additional offerings you would have to license that had varying levels of integration inside of core Maximo. 2) You can buy Maximo Application Suite today as a generally available product but it does not contain all of the applications. While you are given entitlements to core Maximo for example, it isn't inside the Application Suite today and would have to be installed and configured similar to how it is managed today. As Alex mentions, IBM is targeting getting the core Maximo product in the Application Suite in Q1 of 2021 with some of the other apps planning to be added in between.3) Different is hard to describe until everything is implemented as I think the list will grow pretty quickly but there are a few ways that we know now make it very different than core Maximo. The first is that everything will be running entirely in OpenShift. Very few customers are using containers to run Maximo today because there have been various limitations. Up until 220.127.116.11 for example, you had to pay and host a WebSphere MQ if you wanted high availability JMS. With 18.104.22.168 IBM has added the ability to use Kafka as an alternative JMS.
Second is around licensing. The Application Suite will use a concept similar to token licensing (but unique to application suite) called App Points. This makes licensing based on concurrent users instead of named users. These licenses also include multiple products, depending on which level you choose. For example, the first tier (5 app points) includes Limited user entitlements (including for industry solutions), calibration, spatial, linear, Monitor, and Mobility (Maximo Anywhere). Traditionally you would have to buy licenses for each of those, so it might be more cost effective depending on what you intend to utilize.
Note that unlike Maximo today, there isn't an Express license equivalent or an Anywhere only user license. Self-service is still allowed at no charge.
Hi 1971,MAS is 3 things, in my opinion. Firstly it's a broadening of scope. Maximo is moving into Operations and APM. MAS brings together Maximo, Connect, Health, Predict, and in the future, Assist and MROIO.Secondly it's a new technology platform. Maximo and all the components listed above used to be separate monolithic applications. They have been, or are in the process of being, refactored on to OpenShift. This will allow for easier management, and deployment on internal servers, or on IBM or 3rd party Clouds.Thirdly, its a new licensing paradigm. We are no longer licensing sub-modules and add-ons separately. Maximo users will map to one of 3 t-shirt sizes (I hate that term, but it is descriptive). Ultimately all Maximo users will get access to everything they need to be effective without having to go back to their mgmt, or IBM, to license components.Your second question - is it stable? Yes, the team is being careful to manage the migration to ensure it can be supported. I'm not a technologist but I think moving to Openshift will improve reliability - it certainly improves scalability - which is correlated at our largest clients.
Your third question - how is it different? Mx v7.6 is just business as usual. It will be supported per the support policy. It won't have the new licenses, new platform and new functions explained above. Feel free to call or email me if you'd like to discuss.