Maximo Open Forum

Would you give me idea which approach would you vote for when designing solution and data presentation in UI:

a) DBO has two extra fields with persistent storage which are updated by cron jobs from table B based on key; in UI fields are loaded from MBO

b) DBO has two extra fields which are non persistent and their information is loaded in UI when it is presented

While approach A adds complexity, data duplication, brings other problems - approach B relies on longer load time.

What are your criteria, when designing such solutions and making decisions?

Let me know how you deal with such tasks in your projects.

Thanks,

/Saulius

Assuming I understand your requirement, I would create an Option C. In Maximo, it's easy to display data through relationships. For example, when you're on a WORKORDER, you can display fields from ASSET like the description using ASSET.DESCRIPTION. This looks for a relationship in the Database Configuration application with the name ASSET. This gives you the ability to search on it like a persistent attribute without storing it redundantly, without data inconsistency (when the value changes waiting for a synchronization to occur), without the performance impact of large writes to the database, etc. 

If a relationship doesn't already exist you can add it really easily.