From an Oracle Analytics perspective, you can do the following: Keep only the tables you want the CMMS team to access in the Physical Area of the rpd. If HR Tables are not available to access then they wont be able to build data models using them. If they do need access, create database view(s) with the bare minimum cols…

Maybe sometimes it needs to be an attribute ... like subtract 1 week from <Event Date> which is date datatype and present as attribute. Then the resulting column "Event Date LW" can also be used as an attribute. That said, most of the time, date fields used in calculation formulae result in measures, not attributes…

Will be helpful.

What-If use cases involving a re-adjustment of existing pattern and analysis of a large dataset scored against that pattern would benefit a lot from in-memory operations. The analysis is interactive and involves a lot of back and forth user actions like check and uncheck options for many attributes with each action…