When planning to expand IBM Maximo EAM usage to a mobile deployment , one critical considerations is to ensure that the chosen solution is both scalable & secure. We have already covered some security aspects previously in here. In that regard, mobile solutions that handle LDAP and SAML protocols the way MAXapps do should be prefered to those that rely on the Maximo integration Framework (MIF / OLSC) like Maximo Anywhere for instance.
Generally speaking, scalability can be defined as the overall capacity of any system, process, or network to enlarge and accomodate a growing amount of work.
At iMAXeam, we are always aimed by creating robust, powerful and fun to use Maximo add-ons. Our Maximo mobile app, MAXapps, has been built in this mould. First and foremost, as required for any proper scalable solution, our application can scale up to meet increased work load and yet performs flawlessly.
And by work load, we mean a lot. MAXapps has been runned recently through a Ramp up test and various stress tests to evaluate the behaviour and the performance of the mobile app on various parameters.
The simulation above showcases how MAXapps handles the increase from 10 to 1000 users on a developping platform with basic configuration:
- Maximo JVM will handle the users growth with a minimal 4G heap size configuration.
- Because of the collection garbage process, MAXapps can accomodate more resources to make room for more trafic with minimal configuration.
And on top of the cake, this backend scalability comes with a front-end stability and usability that should not be overlooked. MAXapps was designed to handle a thousand of users and deliver the same UXto each new connecting user.
Integration complexity is another is another cost-related considerations to assess. Multi-tenancy is a principle in software architecture where a single instance of the software serves multiple tenants (or customers). Maximo multi-tenant architecture supports the sharing of data between applications based on a complex Open Services for Lifecycle Collaboration (OSLC) integration.
Some mobile solutions still use old web services technologies with Maximo - installing those services on Maximo server - while others will use new API REST to fully interact with Maximo. That one is an obvious improvement when compared to the default IBM product (Maximo Anywhere) which use OSLC technology to interact with Maximo.
MAXapps has been designed for maintenance and automation and this involves to avoid any single point of failure. Our API first app will push work as far away as possible from the core, cache everything, always, provide as fresh as needed data, and scale horizontally.
What about usability ? well, Sessions management, cluster and instance data load management are all handled within MAXapps the same way that maximo does. At the end of the day, from a end-users and admins perspective, all of this lead to predictable, similar performance as with Maximo UI.