Powerplay Cubes Modeling and Development Process: Main Powerplay Transformer Features
Powerplay Cubes Modeling and Development Process: Main Powerplay Transformer Features
Advanced modelling capabilities Leverages aggregate and fact tables Intergation of the query data into the model The models are defined by dimension structures and measures which can be easily customized No custom programming required Time periods are handled in a specific way which makes data delivery easy High flexibilty and portability
Gather business users requirements Create a Model Plan which will include design and data requirements for the model and decide on the cube distribution methodology Select measures Plan dimensions and levels Design and develop the PowerPlay model in Transformer Create PowerPlay cubes and distribute them to the end users Analyze and explore the cube data using PowerPlay
A Transformer Model can be also created using a wizard with AutoDesign function or manually. We strongly recommend to avoid the AutoDesign function as in most cases it does not provide the results expected.
Dimension Map manages the dimensions and levels hierarchy in the data model. It allows creating new dimensions and modifying existing using an user-friendly graphical interface. Dimensions and underlaying Levels are created by moving columns from the Data Sources window to the corresponding dimension column. Measures - drag & drop columns to manage number figures (facts) in a PowerPlay model. PowerCubes - you can specify here a list of cubes created by the model. User Classes - define the security. Signons - datasource connection information. Cognos Powerplay Transformer model for the palm nursery business scenario:
Cognos Powerplay Transformer - multiple data sources in a model with the data source definition:
The data source properties window also allows users to choose the datasource type, point to the right file or database server and set up a number of processing options, like: define timing, uniqueness verification, specify number separators and indicate current period in the time dimension. We will get into more details on that options later on in this tutorial.
Relational sources - including Oracle, SQL, IBM, Teradata, Sybase, and any other ODBC source Dimensional sources - Cognos OLAP, SAP BW, Microsoft SQL Server Analysis Services, Essbase, Oracle 10G, IBM DB2 CubeViews ERP systems - SAP, PeopleSoft and Siebel XML, Java beans, JDBC, LDAP, WSDL Excel files, Access files and csv or text files Legacy and Mainframe systems - like VSAM, IMS, IDMS, Cobol Copybooks Content management data - FileNet, Documentum, and OpenSoft
Time dimension
Time dimension is a special type of dimension. Cognos provides an automatic support for handling time dimensions which is working very well.
Go to Tools -> Date wizard (or use a date wizard icon located in the toolbar) and follow the wizard steps (values entered in our example in blue): 1. Provide name of the dimension - TIME 2. Choose Date Source Type ( Column ) and point the coumn name which contains date values ( DT ). 3. Do you want years in the dimension? Yes 4. Choose the kind of years between Calendar years (355 or 356 days) and Lunar years of 52 weeks 5. Do you want quarter-years in the time dimension? Yes 7. Do you want months in the time dimension? Yes 9. Do you want months in the time dimension? Yes 10. Do you want days in the time dimension? No 11. Choose the first day of the week. Default is Sunday, we will choose Monday 12. How to treat a week which spans a month? Split between the two 13. Enter ther first day of a particular year (yyyymmdd) - year value in this setting is not important. This options allows users for instance to report fiscal years starting from 1 March. We leave the default 20070101 14. Do you want to generate categories? If not needed, we suggest to generate them based on the data and do not generate a category for each day. No
We can see a new time dimension in the Dimension Map of the model:
4. Create the PowerCube by clicking Run -> create PowerCubes and the model will become ready for exploration and analysis The final model structure is shown below:
The Cognos OLAP cube created from the model illustrated above:
Measures allocation
Measures Allocation is a techique that allows comparing data in a report even though it is grouped on a different level of detail. Usually it is required to perform allocation when part of the data is available only on a higher detail level than other data. In real-life, the measures that usually need to be allocated are fixed costs, forecasts, budget plan, discounts, rebates, customer bonus. This is because in most cases those figures are calculated on a monthly (for example COSTS), quarterly (CUSTOMER BONUS) or yearly (BUDGET) basis and very often the SALES reports are generated on a daily basis. It is also very important to remember that in some business cases allocation is logically inappropriate and may not make any sense. There are two ways of implementing allocation:
Fixed allocation - which means that there is a constant value allocated to all levels in a dimension. Users may filter the report, drill up, down, slice and dice and the figure will remain constant. It may be sometimes confusing to the end users and before putting such a figure it is necessary to make clear to the end users that the number is constantly allocated and may not act as expected when analyzing data (especially when calculating summaries). Dynamic allocation (weighted, proportional) - values are allocated using subtotals of an another measure. First a percent of total of a allocation base measure is calculated and based on that figure, the corresponding values for allocated measure are calculated. The weighted type of allocation is often used in real-life datawarehouse environments.
We will perform a constant value allocation to the FIXED COSTS in a YEAR dimension and dynamic allocation to the VARIABLE COSTS in a MONTH dimension (the allocation key is QUANTITY). To allocate a measure in PowerPlay Transformer go to a dimension level properties to the allocation tab and choose the corresponding option.
We see below that fixed costs have been allocated in a constant fashion:
PowerPlay Excel Impromptu Cognos WebPortal Visualizer DecisionStream PowerPlay Transformer / Impromptu Administrator Metrics Manager Notice cast Planning
Comments Desktop Query and Analysis tool Web-based multidimensional analysis MS Office / Spredsheet integration Reporting Web Portal Visual dashboards ETL & Data integration tool Modeling framework Scorecarding Business activity monitoring Planning, budgeting, forecasting
The data model and flow of the data in Cognos is as follows: Analyze and define the data structure in source systems Use PowerPlay Transformer to connect to one or more sources of data and build multidimensional models Create the Cognos PowerCubes in Transformer and distribute those multidimensional models (and/or use PowerPlay Enterprise Server for distribution and to apply security to the OLAP cubes) View the distributed PowerCubes using Cognos PowerPlay for Windows, PowerPlay for Excel, Powerplay Web or Cognos Visualizer