Reuse certain namespaces, (and/or) query subjects, other artifacts from a base

[allanvsouza]

Our situation and challenge:
We like to think of each subject area/mart as a combination of certain common dimensions and usually one FACT table (or physical query subject or logical query subject, if you prefer). 
Most of our Framework manager models end up having the SAME large set of dimension tables and one (or few ) fact tables.
Among multiple other challenges, like the repeat of dimension query subjects across every model -- when the definition of a dimension table changes then we have to go back to each one of the models and make the corresponding changes.

What we want to do:
Have one "place" ("global" dimension model) where we can have all the dimension tables in a certain namespace perhaps.
Then "include"/link/associate this one gloabl model to all the fact area models. 

Model "Parent" has dimensions Product, Customer, Account, Time.

Model "Child 1" has Revenue Allocation Fact Query subject.  It also includes a reference to Model "Parent"

Model "Child 2" has Cost Allocation Fact Query subject.  It also includes a reference to Model "Parent"

If I make a change to the base Model "Parent" then all changes will automatically ripple through ALL dependent child projects (Model "Child 1", Model "Child 2", etc)

Questions:
Besides Segment Linking, or
Using Meta-data Wizard to use a dependent CPF file (this is hoaky because there is only a "static" dependency, no dynamic dependency exists), Is there any other way?

What other options are available?  We are extremely surprised that the basic concept of reuse and "layering" is not build into modeling tool.

Any help will be highly appreciated!

[cognostechie]

The concept of re-use is definately built in Framework Manager. First of all, why do you have separate models to begin with if the Dimensions are the same? Having separate models means increasing the content and maintenance by making separate reports ! Why not create one model with Product, Customer , Account and Time as the Dimensions and Revenue Allocation and Cost Allocation as the Facts?

[bdbits]

Like cognostechie, I am not real sure why you have separate models to begin with, unless they are very large. You do not need to create multiple models to have subject area specific packages, as you can quite easily generate multiple packages from one model, each having a limited set of objects. I do this myself, to keep it simpler for various types of users.

Your issue is not with Framework Manager, but with how you are using it.

If you really want/need multiple models, a gentleman from Boeing had a good presentation at IOD 2011, session 1724. I have a copy of the slides but I am not sure it is kosher for me to make it available. Fortunately I just googled it and you can see it here: http://www.slideshare.net/Envisn/iod-2011-1724-bob