What is MobileDbGeneration cron task schedule recommendation from IBM. Is 24- 48 hours ideal? or do we need more time.

Good question, Janvee - the optimal MobileDbGeneration cron task schedule really depends on data volatility and user sync patterns, but here are some general recommendations:

IBM's guidance: Run the cron task once every 24 hours for most production environments. This provides a good balance between performance, data freshness, and server load.

When to run more frequently (e.g., every 12 hours):

• If mobile users depend on rapidly changing data (e.g., work orders, assignments, or inventory).

• If you have automated nightly updates or integrations that feed Maximo data overnightWhen 24–48 hours is sufficient:

• For stable environments where master data and assignments don't change often.

• When device syncs are staggered or offline work is common.

Best practice:
Schedule MobileDbGeneration to run after off-peak batch jobs (like PM generation or integration loads) and ensure it completes before users start their day. Also, monitor generation duration and size - if it's taking too long, consider scoping data by user groups or sites.

- Manu Nagayach
IBM-Certified Maximo Architect | EAM Strategist |