Maximo

 View Only
  • 1.  General Maximo Mobile questions

    Posted 4 days ago

    Hi All,

    As I am plunging more into Maximo Mobile, I have a couple of questions I want to ask:-

    1. What's the best practice for setup multiple preloaded databases? Are there any use cases where have multiple preloaded databases can benefit the org as opposed to having one?

    2.  Any advice on creating custom applications that are unrelated to the out of the box applications?

    3. When the preloaded CRON task runs to sync data to mobile, does that CRON's user count as having a session opened at the time the CRON task runs, or does it count as open session/using app point when each user logs in? 
    4. Is it recommended to have MAXADMIN only as the preloaded CRON task user? Any issues with having a regular user account on the CRON task.


  • 2.  RE: General Maximo Mobile questions

    Posted 3 days ago
    Edited by Steven Shull 3 days ago

    Most customers utilize a single preloaded database per site. It's important to understand that the various application lookups (such as asset) all filter for the user's default insert site. Organizations that have multiple sites would at a minimum, need a preload database per site. 

    The preload databases are only lookup data (item, inventory, asset, locations, etc.) that are not being modified by the user. All transactional records (Work Orders, SRs, Inventory Usage, etc.) are downloaded as the user interactively via the REST API. For most customers, the lookup data sets can be the same for every user in the site so there's no need to have multiple preload databases in an individual site. However, there are use cases where you may determine that you have different groups of people that should see different inventory records for example and choose to setup separate preload databases.

    Today (we are looking at changes in 9.1), each cron task instance should have an unique user & person group. I recommend customers set up dedicated users (IE BEDFORDDB) for the cron task and a security group (PRELOADDB for example) that provides the necessary site access, labor, storeroom, & permissions to our object structures. Just make sure you apply the security template for every application (Technician, Inspection, etc.) you intend to use to ensure all the necessary security has been granted.

    As for point consumption, cron tasks do not consume app points. When you setup the users, make them concurrent if you're on MAS. If you're on EAM 7.6.1.X, in our client license overview document we explicitly state that users setup exclusively for this purpose do not need to be licensed. 

    ------------------------------
    Steven Shull
    ------------------------------