Thanks @rob_marshall !! I understood the System Time Module now. Just to confirm, though it is called System Time module it is not an inbuilt anaplan module (rather a model builder created module), correct?
This greatly helps me because I have several multiple fake time dimensions (because of the cohort modeling) which have multiple different offsets - say for example, in one case we lookback 365 days and I have a list of 0-365 there. In another case, we look back 1000 days!
Having a common time module and having these calculations does save a lot of redundant calculations. Thanks again.
Yes, the "system" module is just a term we use but it could also be Structure. It is not inherit to they system at all, but helps with mapping, filtering, master/meta data of lists. The one above is based off of Time, where you can do the mapping to the Month Names as well as filter out all quarters or years. Another example could be on the base member of a Product Hierarchy where you are figuring out what the parents are (P3, P2, P1). If you have these in one module, all module builders will know where to get the data instead of recreating the wheel in their own modules.
Again, the main benefits are:
Reduced dimensionality for calucaltions (having the calculation being kicked off more times than needed)
Reduced redundant calculations (having the code of Product or the Time mapping to the Month Name list is done one time instead of many times)
Auditability - makes it easier to find where the data is coming from than in serveral different modules.
Scalability - helps the system scale when larger and larger data/list volumes occur.