DecisionStream, Transformer, PowerPlay: mdl and mdc

[NetSpace]

Hi!
I am new to Cognos tools.

DecisionStream=>Transformer=>PowerPlay or DecisionStream=>PowerPlay

Using DecisionStream metadata data can be delivered to Transformer.
XXXFactBuild.mdl model for Transformer and XXXFactBuild.mdcÃ,  cube are built during fact build execution phase in DecisionStream.
After the cube is created it can be opened in PowerPlay and different reports are built.

Because the cube (xx.mdc) is automatically built during fact build execution phase, how mdl model is used?

Different cubes can be built based on that model in Transformer that only use/expose part of the model.
Is it correct?

Thank you.

[MFGF]

The DecisionStream Fact Build is invoking Transformer to create the Transformer model, then getting Transformer to build the cube from the model.  DecisionStream itself has no cube-creation capabilities - it's all being done by Transformer behind the scenes.

The idea behind DecisionStream invoking the metadata creation in Transformer is to save you some work in creating the initial Transformer model from the data - chances are the model and cube built as part of the Fact Build will not be complete enough to suit all the reporting requirements anyway, as they do not contain alternate drill paths, special categories, allocations etc, so view these simply as a quick way to get you started rather than a complete reporting solution.  Most developers use DS to get them started with the model, then switch off the export to Transformer afterwards as re-exporting would obliterate any extra work they added to the model in Transformer.

Hope that helps!

MF.

PS - this all goes away in Cognos 8 Data Manager - the export options for Architect, Impromptu, Transformer and MSAS have disappeared from the product.