IBM Cognos 10 Framework Manager by Terry Curran

Get full access to IBM Cognos 10 Framework Manager and 60K+ other titles, with a free 10-day trial of O'Reilly.

There are also live events, courses curated by job role, and more.

Chapter 6. Creating the Business and Presentation Layers

This chapter will cover the creation of the business and presentation layers. The business layer is where we apply various business information rules to our model. The presentation layer is what the report author will see in Report Studio, Query Studio, and Analysis Studio.

This chapter will cover the following topics:

  • Specifying attributes
  • Renaming columns
  • Adding prompts
  • Adding filters
  • Adding calculations
  • Adding formatting to data items
  • Using folders and namespaces for grouping information
  • Using shortcuts to include the same information in different places

By the end of this chapter, users will have created the business layer and extended the usefulness of their model by adding prompts, filters, ...

Get IBM Cognos 10 Framework Manager now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Don’t leave empty-handed

Get Mark Richards’s Software Architecture Patterns ebook to better understand how to design components—and how they should interact.

It’s yours, free.

Cover of Software Architecture Patterns

Check it out now on O’Reilly

Dive in for free with a 10-day trial of the O’Reilly learning platform—then explore all the other resources our members count on to build skills and solve problems every day.

cognos framework manager presentation layer

Ironside Group

Best Practices in Cognos 8 Framework Manager Model Design: Part 2 – Advanced Modeling Issues

Editor’s Note :  This blog was originally posted on August 1, 2010 and has been reviewed and updated on 10/5/2020 with Cognos Analytics 11.1.7 .  We find that these best practice tips about metadata modeling are still very useful to build solid data foundation for reports, especially cardinality settings and stich query controls as they are critical modeling techniques. These procedures are also applicable to Cognos new web based metadata modeling component – the Data Module , which is greatly adopted by self-service authors and when Cognos is hosted in cloud (no need to install Framework Manger tool).

Last month’s article described the overall approach for best practice model design using the 4 layer architecture. In this month’s article, I’ll describe some advanced issues which arise during model design, and how best to deal with them. Given the limitless and complex situations that can come up during modeling, these techniques may or may not apply to your specific situation.

Last month’s article described the overall approach for best practice model design using the 4 layer architecture. In this month’s article, I’ll describe some advanced issues which arise during model design, and how best to deal with them. Given the limitless and complex situations that can come up during modeling, these techniques may or may not apply to your specific situation.

Data Sources

One area which many modelers neglect is the data sources. A key part of the data source is the Content Manager Data Source, which references a data source configured via the web interface in the Administration area of Cognos Connection. You should have as few of these as possible, ideally only 1 per database, unless there are very specific reasons (such as security). Even so, many security or logon issues can be addressed via multiple connections or signons within a data source.

Framework Manager will automatically create multiple data sources, (one per schema, for example), but they should reference the same Content Manager Data Source. The reason minimizing these is because multiple Content Manager data sources will open separate connections to the database and force Cognos to perform simple joins within the reporting engine instead of in the database where they belong.

Relationships and Cardinality

The area which causes much confusion and difficulties with modeling is relationships and cardinality. There are a number of documents which discuss the handling of data modeling traps, such as the Guidelines for Modeling Metadata document included in the documentation, and so I will not duplicate those discussions here, instead addressing other topics.

A common concern is when to alias a table in the data layer. In general, common dimension tables used across multiple fact tables, or contexts, should not be aliased. This is important in creating conformed dimensional reports. For example, a parts dimension is the same when used for reporting against sales or inventory fact tables. When a table has separate usages, or meanings, it should be aliased. For example, a general purpose address table, which contains branch, customer and employee addresses. These are often identified by having multiple join paths or filters which can signal different usage.

Another situation to use aliases is when there are multiple usages of a dimension table. The most common occurrence of this is the general-purpose date dimension table. Applications such as health and insurance can have many different joins to a date dimension, each of which has a different context. This can be complicated to track, because one usage, such as Admission Date must apply in a conformed manner to many fact tables, while a different usage ( Treatment Date) must also be conformed across many of the same dimension tables. Obviously a meaningful naming convention is required!

If you do decide that your logical query subject requires a different alias, make sure to make liberal use of the Remap to New Source option, available by right-clicking on the query subject.

cognos framework manager presentation layer

Controlling Stitch Queries

One frequent point of confusion, is how the model causes reports to create stitch (or multiple) queries. To resolve this requires a firm understanding of the cardinality in relationships. Also realize that stitch queries are sometimes best way of issuing a query.

Report studio will generate simple, consistent queries when there is consistent progression from “1 to many” relationships. This is a smooth progression from dimensions to facts. It can easily generate facts with correct aggregations with this simple scenario. Remember that Cognos will treat the query subject at the end of one or series of 1:N relationships as fact tables.

Similarly, it also works well in the case where multiple “dimensions” converge on a single fact table, as shown below. An easy visual check is to make sure that the 1:N relationships proceed in the same direction, with the ultimate fact table serving as the “Many” end-point of several dimensions.

The stitch issue occurs when there is more than one “Many” side along the same dimension path, as shown below.

A query which utilizes both of the rightmost, or “fact” tables will result in a stitch query as the only relationship is via a conformed “dimension” table. In a query where inventory (fact) and sales (fact) are compared at a product (dimension) level, a stitch query is the correct approach. However, if this is an unintentional or poorly modeled relationship, incorrect or inefficient queries will be generated. Understanding the implications of cardinality in relationships is the best defense against this.

Naming Conventions and Nomenclature

Another area of confusion is naming conventions and nomenclature, and areas surrounding these subjects. The best practice is to have the query subject and element names all carefully thought out and implemented before developing the model, but that doesn’t always happen.

First, let’s describe how Framework Manager and report studio considers element names. Each element name is uniquely identified within the package by a 3 part name: The element itself, the parent query subject (or shortcut) name, and the parent namespace to the query subject. Element names must therefore be unique within the query subject, and similarly for query subjects within the namespace. However, the namespace name must be unique within the entire model. So you can have multiple references to element “Part Name” within query subject “Part Master”, but the namespace, such as “Purchasing” or “Inventory” can only occur once within the model, making the fully qualified name unique. Notice that folder names do not come into play when defining names. They are used only for organizing other items.

Managing Name Changes

The result of all this, is that names within the model are very important, especially once report writing begins, because they are difficult to change without invalidating existing reports.

So, in order of preference, maintain consistent names across models by:

  • Get it right the first time. If multiple areas of the organization have a stake in naming conventions, involve all organizations early in the design process, even if the first stages do not apply to some of them.
  • Identify situations where a renamed item is used. Here the option “Find Report Dependencies” is invaluable in identifying reports where an item is used. Keep in mind, though, that if your model references a development server, it will not identify reports or queries which exist only in your production environment. Therefore it may not adequately identify issues in every environment. Advanced audit report and SDK script can help identify report<->package dependencies information.  
  • Move the renamed item to a “deprecated” query subject folder, and create a similar element with the new name. While this relies on a certain amount of end-user training, to instruct report and query writers not to use objects within a folder named “DO NOT USE” or similar, it will ensure that existing reports will still run correctly, while using the new, correct name moving forward.

cognos framework manager presentation layer

This article addresses some of the most common advanced issues around model design, but certainly not all of them. With modeling being part science and part art, it’s not possible to address all possible situations. If you have a specific modeling situation you would like me to address, please email us at [email protected] .

cognos framework manager presentation layer

Ironside helps companies translate business goals and challenges into technology solutions that enable insightful analysis, data-driven decision making and continued success. We help you structure, integrate and augment your data, while transforming your analytic environment and improving governance.

  • AWS Ascent Solutions
  • IBM Data Analytic Services



For inquiries: [email protected]

For HR: [email protected]

Office Address 131 Hartwell Ave Lexington, MA 02421

Corporate Mailing Address Ironside Group, LLC 101 Great Rd, Suite #130 Bedford, Massachusetts 01730

Regional offices in Atlanta, Austin, Boston, Charlotte, New York City and Orlando

>> Managed Services Support

  • Determinants – The Answer to a...
  • IBM Cognos CSV Files: The Encoding...
  • IBM Cognos 8 Framework Manager Training...

cognos framework manager presentation layer

  • Welcome to - The IBM Cognos Community .
  • - The IBM Cognos Community

MetaManager - Administrative Tools for IBM Cognos Pricing starting at $2,100 Download Now     Learn More

  • ► IBM Cognos 8 Platform
  • ► COGNOS 8
  • ► Framework Manager
  • ► Why go with 3 layers in Framework Manager Model?

Why go with 3 layers in Framework Manager Model?

Started by alliejoy, 26 May 2010 10:50:52 AM

cognos framework manager presentation layer

  • Never knowingly correct
  • Super Moderator

cognos framework manager presentation layer

  • Posts: 11,815
  • Cognos Software Muppet
  • Join Date: Jul 2005
  • Location: Once long ago near England but now in New Jersey
  • Global Moderator

cognos framework manager presentation layer

  • Posts: 1,912
  • Join Date: Jan 2009
  • Location: Israel
Quote This is especially visible if you create a report that selects 2 columns out of 10 in a table. The underlying query might be selecting all columns and then doing a subselect on the 2 required ones. Obviously this drives value of DB indexes (read performance) to nothing.


  • Join Date: Apr 2008
  • Help | Terms and Rules | Go Up ▲
  • SMF 2.1.4 © 2023 , Simple Machines

Best Practices in Modelling IBM Cognos 8 Semantic Layers

In October 2008, we published the below Insight " Best Practices in Modelling IBM Cognos 8 Semantic Layers " on our website. Since then, this page has become the most visited page on our website, with over 50.000 pageviews since publication, clearly showing the need for the topic. Whilst most of the concepts of Framework modelling in Cognos 8 still are valid for Cognos 10, we decided to update the Insight to incorporate new IBM Cognos 10 functionality. We thus are proud to present : " Best Practices in Modelling IBM Cognos 10.2 Semantic Layers" . Below you still can find the original IBM Cognos 8 Insight.

Cognos 8 BI Stack

The IBM Cognos 8 Corporate Performance Management system offers report authors a single platform to create reports, dashboards, events and perform analysis on multidimensional data. Cognos uses a three tier architecture to service the report consumers and authors. The client connects using a zero footprint web-browser to Cognos Connection. Zero Footprint means no additional software or applets at all are installed on the client PC.

  • Query Studio to perform basic reporting using basic queries and formatting
  • Report Studio to perform advanced, pixel perfect reporting with complex queries
  • Analysis Studio to perform multidimensional analysis
  • Metrics Studio to follow metric performance over time and define actions as necessary
  • Event Studio to create agents to follow up on triggers

Semantic Layers

Flexible models, framework objects.

  • Data source query subject: performs a query on the underlying data source
  • Model query subject: refers to an existing query subject in the model.
  • Stored procedure query subject: used to retrieve data from stored procedures.

Best Practices in Modelling IBM Cognos 8 Semantic Layers

Query subjects are linked together using relationships. A query subject can be edited by replacing the standard SQL with custom written SQL. The same can be done for relationships between query subjects. For maintenance purposes, it is however recommended never to make any changes at all in freehand SQL. When a physical table is changed, the new definition has to be manually adjusted or the table needs to be imported again. Importing is by far the easiest way to allow for bulk changes. When freehand SQL was entered, all these changes are lost following a new import. Calculations and determinants can be added without making changes to the SQL code by using the proper tab pages. A determinant is needed to identify certain levels of aggregation within the query subject. This is a particularly useful feature while dealing with multifact, multigrain queries. For OLAP functionality, two additional objects are available: a measure dimension and a regular dimension. A measure dimension contains a collection of "facts”. The regular dimension provides the accompanying set of descriptions and identifiers. The measure and regular dimensions are linked with scope relationships to define the level at which the measures are available for reporting.

Creating Durable Models

Best Practices in Modelling IBM Cognos 8 Semantic Layers

Model for predictable results

Simplify with dimensional concepts.

  • cardinality is always applied in the scope of a query performed by the user
  • 1 or 0-to-n relationship implies a fact but only if ALL relationships to that query subject are 1 or 0-to-n
  • 1 or 0 to 1 implies a dimension

Handle Ambiguous Relationships

Multi fact multi grain queries, consolidate, presentation, multilingual.

  • separate column for every language for example PRODUCT_EN, PRODUCT_DU, PRODUCT_FR
  • separate row for every language
  • #'[NAMESPACE].[QUERY SUBJECT].[QUERY ITEM_'+ $Language_lookup{$runLocale}+ '] '#
  • [NAMESPACE].[QUERY SUBJECT].[LANGUAGE] = #$Language_lookup{$runLocale}+ '] '#

Enhance performance

Reuse metadata.

  • when the centralized data warehouse changes, changes only need to propagated once to the Framework Model
  • the master project has access to the entire model, the central data warehouse team can analyse impact immediately
  • the centralized team can see how other teams are using the original framework

Cognos 8 Framework Manager manages the semantic layer of a Cognos 8 deployment. A modeller's main focus is creating a user-friendly, comprehensive model that provides in repeatable and predictable query results. Modeling a metadata layer requires an extensive business and underlying data source knowledge. To create a model that offers repeatable and predictable results, the model should always, physically or virtually be conceived as one or multiple star schemas. By structuring the framework in a layered approach, any downstream effects of database changes can be minimized. Cognos Framework Manager offers a well featured metadata modelling tool that allows a durable approach in modelling semantic layers.

Related insights

Planning analytics workspace guided planning, planning analytics workspace administration, what’s new in ibm planning analytics workspace 2.0.52 - 2.0.57 sc.

Rohit Ganesh Santoshwar

Published on

Framework Manager Layers

Hello, I""m looking at a Model developed earlier by someone else and am a bit confused. Since our datawarehouse is a straight star-schema implementation, importing all the tables with relationships in the Database Layer does the job. I understand that once this is done, there is no need to create the same relationships in the Business Layer as it (relationship) will be carried over. All our tables have been imported this way and relationships created similarly, hence, we only have 2 Layers in our model (DB Layer & Business/Presentation Layer). Though, this is the case, I see something weird. Say Table A & B that have a 1-N many relationship and when imported you see that relationship in the DB Layer. When Model Query Subjects are created in Business Layer for these tables, and you check the context explorer in this layer, you dont see the relationships for either. In short, you see the relationship in the DB Layer but its hidden in the Business Layer. That is how it should be, if I’m not wrong. On the other hand, there are other tables, say X and Y that have 1-N many relationship and are imported similarly in the DB layer. Here you see the relationships and when you create Model Query Subjects in the Business Layer, from these 2 objects, the relationships are not hidden i.e. you see the relationship between the 2 objects even in the Business Layer. I wonder why are these two scenarios are inconsistent when the same process has been used?

Usually you would have three layers

  • Database layer - just the tables with any filters applied!
  • Modelling layer - the tables from the database with all the joins between them, and any special formatting conversion, etc
  • Business Layer- the tables with nice friendly names, grouped into folders

You should only make the joins between the tables in one layer, then you can see all the joins n one place

P Please consider the environment before printing this e-mail

This email is confidential and intended solely for the addressee[s].

For your security this email contains a digital signature which verifies the identity of the email sender.

If you are not the intended recipient you must not copy, distribute, disseminate, nor act upon the information. If you have received this message in error do not open any attachment, instead please inform the sender and then delete the message from your system.

We have taken reasonable steps to reduce risks against viruses but please rely on your own virus check as no responsibility or liability can be accepted for any damage sustained as a result of this transmission.

First of all welcome to FM Suhel Deshmukh,

look like TMI.

We totally understood what you were talking about day and night.

here is the solution for your issue. not sure what version of Cognos you are using anyhow based on 8.4.1 FM.

just right click on the query subject where you will see few option. simply untick or unselect the option “show immediate References”.

you won’t see the relationship with anyone anymore.

I like to use standards whenever possible, because someone will eventually pick up my work, and it will help them greatly if they can easily see that my project organization adheres to a well known, well documented, proven pattern. Of course, sometimes reporting requirements are such that you have to extend or vary from standards, which is fine, and I do when necessary. But I’m always thinking about the poor person who has to inherit this mess someday, and how much it would help them to understand what I’ve done because it was based on an existing pattern.

Terry, Actually really makes sense what you have mention it. I am with you.

Thanks Winson

However many layers you have in FM, and how you name your layers, or how you create your relationships is a matter of personal preference, or in some cases you have to follow company requirements (or standards). If there are no standards then I would go with the personal preferences option, or follow Cognos guidance. It not how you put your model together but it how you use it afterwards that is important, you have to consider if you are creating reports or your users are doing it as it will influence how the model is presented to users!

Thanks Randy,

Some of my replies toolbox reject automatically why this is the reason. Actually I replied to ur post while back but got reject it.

Randy, “I really like the way you put all together in one sentence as “I’m not trying to be a wiseguy”. That would explain a lot. Actually ur sharing ur thought and experience that all.”

Winson, I gotta say, I love reading your posts. They always put a smile on my face!

You see both red & Blue . Blue is the latest.

or search on amazon cognos framwork manager

What’s the actual name of the blue book? Can’t seem to find anything on Amazon.


Also on Amazon they sell bluebook as well that explain a lot. So far Red/Blue book on the market, sooner there will be Green since everything changing it to Green (paper less); make more sense than (Red/Blue).

Thanks, Winson

It might be. I am referring to the documenst on the Proven Practices ibm area.? I believe these are the same docs.

Randy - to be specific, are you referring to the IBM/Cognos guidelines found in the Redbook?

My best opinion on all of this is actually quite simple - follow the IBM/cognos guidelines and deviate only when you know you have to. If you follow the guidelines and can’t come up with a reason to deviate from them, then you don’t have a reason. I’m not trying to be a wiseguy, its just that Cognos has far more experience with far more consultants and their proven practices are just that - Proven to work 99% of the time. Also, make a very small model with just a few tables. Model it the way the guidelines indicate and then model it in other ways. You will then really understand the pros and cons of each way. In the end all ways will work. But some will cause more grief down the road.

I don’t understand why there should be no relationships between the imported tables. Cognos will do this for you for free with the metadata wizard, and then you don’t have to do it in the business layer. It doesn’t make much sense to me to create tables/relationships in your database modeling tool (e.g. ERWin), generate tables from the tool into the database, and then import those tables into Cognos, only to recreate all the tables/relationships in the business layer. I realize that the business layer gives you an abstraction layer, but why recreate all the relationships you already created in generating the database?

There are 2 different scenarios of why half community suggests relationships between business layer and database layer.

Feasibility and Scalability: If you have datatypes changing or number of columns in tables changing frequently always use relationships in business layer. This way you won’t have to create them again and again when you refresh query subject which is mapped to that table.

For better query joins: If you are sure, your tables physical structure is not going to change use relationships in database layer, Cognos suggests it gives better performances when joins are made in database layer due to most optmized query.

Also, just to add when you create relationship in database layer, relationship is never on imported tables. It is always on query subjects that you have mapped to imported tables.

Hope this helps!

Dipti Loya

Thank you all for your responses. The differences in your responses pinpoints why I was confused about this.

Randy advises to put relationships in the database layer, not the business layer (this also appears to be the Cognos guidance in the redbook), as well as the samples.

Others advise to create relationships in the business layer. With this approach, are the following assumptions true?

You need to create a query subject for each table that you import

The only relationships are between query subject, NOT imported tables

Since the relationships are created in the business layer, you would not want to have FM automatically create relationships between tables that are imported.

Good Comments Randy! Could you please explain how more sql is generated than one needs in business layer and how come less sql is generated in DB layer?

Just to add my .02 to the whole mess. In your database layer, put your relationships. If you put these in the business layer, you can have far more sql generated that you need. Keep the relationships as “low” as possible - as close to the real data as possible.

You import the tables into the database layer by using metadata import. You create the table in the modelling layer by using create query!

Related Topics

Topic Replies Views Activity
Business 8 65 December 8, 2011
Business 7 27 December 11, 2008
Business 3 28 July 22, 2009
Business 6 110 July 30, 2010
Business 6 171 February 5, 2015

cognos framework manager presentation layer

Create strategy, not spreadsheets! Evolving Finance through AI & Automation | Free live webinar >> Dismiss

  • Cognos Framework Manager vs. Data Modules
  • Knowledge Center
  • Instructor-led online
  • June 25, 2020

Each release of Cognos sees incremental improvements to data modules. Over time, the functionality gaps between data modules and Framework Manager have narrowed substantially. In fact, data modules are a powerhouse of a tool.

But does that mean you can use data modules as the primary Cognos metadata modeling tool? Now is your chance to find out.

In this on-demand demo and comprehensive comparison between Framework Manager and data modules, we explore data module advantages over Framework Manager and the feature and functionality gaps that exist. And answer participant questions.

Pedro Ining Senior BI Architect Senturus, Inc.

Pedro joined Senturus in 2010 and brings over 20 years of BI and data warehousing experience to his role. He has been instrumental in implementing data warehousing systems from scratch and has experienced the evolution of the BI industry through several iterations of BI products including Cognos, MicroStrategy and Tableau.

Questions log

Q: Can Cognos data modules call stored procedure like Framework Manager? A:  This is currently not supported. You can make custom tables based on SQL, but you cannot call a stored procedure.

Q: Can DMR be used in Cognos data modules? A:  As of Cognos release 11.1.6 DMRs cannot be created in data modules. This may be addressed in later versions, but we don’t think it is high on IBMs priority list.

Q: Is IBM considering migrating Framework Manager as a web-based tool? A:  No. FM will not undergo any further new development; however, It will be continually supported for a long time. (Think Transformer, that product is still supported.)

Q: Can Cognos data modules read synonyms? A:  Yes. If the logon to the data source connection can read the synonym then you should be able to read it.

Q: Is there a way to automate the refresh of Cognos data modules, instead of doing it manually? A:  If the datasets are contained in a data module, then yes you can. You just need to set a refresh schedule on each dataset’s properties.

Q: With Cognos data modules is there a way to control a version of the truth since the sources can come from anywhere and the transformations are different? A:  Since you can create your own data modules, the control of the version of the truth will need to rely on your internal organization’s processes and control to data sources. Even in very controlled environments the single source of truth goal can easily get lost as users can use Excel and other tools that integrate data on their desktops.

Q: We have filters on Cognos FM database Query Studio that are based on session parameters. Can we replicate that in data modules? A:  You can create filters based on expressions which in turn call macros. We have not tested this on a specific use case.

Q: Does the Senturus Analytics Connector for Tableau recognize data modules? A:  Yes, the Senturus Analytics Connector supports data modules! Learn more about the  Analytics Connector .

Q: Can Cognos data modules do the impact analysis like Framework Manager? A:  Currently no.

Q: Are easy hierarchy creation – navigation paths more like Cognos data modeling or dimension layers in Transformer? A:  Navigation paths are not a true dimension like Transformer. It simulates a dimension, but the flexibility of navigation paths is that you can create relationship among any attributes.

Q: Will Event Studio support Cognos data modules in the future? A:  No. There are no current plans to update Event Studio.

Q: How do we backup Cognos data modules? A:  Either manually via standard copy or you can use regular content store backups using a third-party such as Motio.

Q: If we are creating a view of tables and forget to include a field, is there a way to re-add the field again? A:  Simply edit the view and add the field. Cognos 11.1.6 adds a new refresh metadata button that will allow you to add the new field to the source table with a drag and drop.

Q: What’s the maximum number of tables Cognos data modules can handle? A:  There is no limit; however, you may want to architect the solution with multiple DMs if you have many tables.

Q: Are data servers the same as data sources in Cognos? A:  Data servers are very similar to traditional Cognos data sources. One big difference is that they only support DQM connections. Data servers are created from the main web Interface, while traditional data source connections are created in the administration console.

Q: Does IBM have any plans to have aggregate awareness available in Cognos data modules? A:  Not that we are aware. That feature was not available in FM either.

Q: Why do we have to define a join between the two custom tables? Are the original joins recognized by Cognos data modules? A:  If you create a view from several tables, it will inherit the joins of those tables in the view. If you create a view from one table, it will not inherit any joins defined from the base table.

Q: If I create a custom table and then decide I want to include an additional table, how can I add one? A:  You will need to recreate the custom table from scratch, sorry.

Q: Is there a verify model in Cognos? A:  Validation is automated and usually occurs every few seconds. You can control this behavior to be manual.

Q: Which is easier to use for creating data modules, Tableau or Cognos? A:  Tableau requires you to model data first before you can begin creating visualizations. It is a different paradigm. Cognos allows you to create reports/visualizations against packages or data modules that are available in Cognos. Both tools require you to understand data joins and both are fairly simple to use if you understand the basic concepts of data modeling.

Q: How do we move Cognos data modules between environments such as development, general availability and production? A:  The usual migration deployment package concepts will work.

Q: Is there a way for us to implement relative time calculations like PeriodToDate MDX functions in Cognos data modules? A:  Yes. relative time is now easy to implement in data modules. Check out my on-demand webinar,  Using the New Cognos KPI Capability & Relative Time Structures , to learn more.

Q: As an Admin – in the FM paradigm – I have knowledge and oversight of packages. What happens when a modeler leaves the company? And nobody has access to that user’s content? A:  Admins can always get access to a user’s My Content. But as you expand self-service across your organization, you’ll have some problems with decentralized content. This will become an organization process issue that you’ll need to address to monitor and track Cognos use and development.

Q: Can we go back and add fields to the products later as requirements change? A:  Yes, you can, they’ve made it easier in Cognos 11.1.7.

Q: How do I add descriptions and screen tips? A:  In the properties of a data modules table or fields you will find a screen tip entry field. Add your screen tips there.

Q: Where did the column names and no timeframe of week in the time dimension come from? A:  Column names came from the basetable. In the demo, I only selectively chose certain columns.

Q: If I use PA/TM1 as a source, does it slow things down? A:  We haven’t tried this source as of yet but you should get the same performance as a normal Cognos connection.

Q: Would it be a good practice if I always use views to simulate a physical and presentation layer in Cognos data modules like we did in Framework Manager? A:  End user modeling would probably only use views when they are needed. If you are deploying IT maintained data models that are typically locked down, it would be a good idea to use this practice. Then end-users would simply link to those data modules.

Q: Is it possible to convert an existing Cognos Framework Manager package into a data module? A:  There is no existing migration utility; although some folks are working on one. You would have to do this manually.

Q: How do we show the metadata for the table in custom product view? A:  Several different ways, with view definition, edit view or the properties pane.

Q: How do we add new fields to custom views? A:  You will need to edit the view definition.

Q: How would a master Cognos data module approach be done so that only one data module needs to be managed and propagated to all the sub modules? A:  This is a scenario where IT creates a master data module that contains all the necessary joins, calcs, etc. from a source database. You can then publish this data module as read only so no users can modify the data module. User can read the data module and then create other data modules from this source data module. This establishes a linked data module.

Q: Can I use session parameters and prompt macros within Cognos data modules? A:  Prompt macros are not supported, but you may be able to use session parameters in custom filter definitions.

Q: Cognos Framework Manager allows us to call stored procedures in databases. Are there any plans to implement invoking of stored procedures with parameters in data modules? A:  This is probably on IBM’s development list.

Q: To have multilingual reports with parameter maps do we need to use Cognos Framework Manager or is there any way to have multilingual reports using only data modules? A:  Parameter maps are critical to supporting multilingual reports. This is not yet supported in data modules.

Q: Is it possible to see SQL query from the report query built from Cognos data modules? A:  You can view the SQL query of each table or view it within the Cognos data module. That would then get interpreted in reports. You should be able to see the queries in that tool as well.

Q: Do we have Stich queries issued in Cognos Framework Manager? A:  Stitch queries using COALESCE are supported in data modules.

Q: Do we have an option to find report dependency in Cognos data modules like we have in Framework Manager? A:  No.

Q: How do I find the list of all reports that is using a particular field? A:  Data modules do not have that type of dependency checks yet.

Q: How do we manage the security of users on Cognos data modules? A:  The Cognos data module is like any other object in Cognos. You can grant the usual set of permissions on the data module.

Q: How is data security and object security done in Cognos data modules? A:  Currently object-level security is not possible inside a Cognos data module. Data-level security is supported by creating filters on the data source and applying specific Cognos or Admin user groups to the filters. Advanced row-level security via parameter maps, security tables, etc. is not yet supported.

Q: Can Cognos data modules read TM1 or planning databases? A:  Yes. Create a data server connection to TM1 and then create a data module from it.

Q: Are there governed settings like stopping cross join in Cognos data modules? A:  Data modules do not contain governor settings like that of Framework Manager.

Q: Do you or IBM have a recommendation for timelines in moving away from converting Cognos Framework Manager packages to data modules? A:  Framework Manager will be around for a long time. Our recommendation is that if your production packages are working fine and are complex you should not invest too much time converting those packages to data modules. Maybe specific areas of those packages could be converted so that users can take advantage of certain data module features.

For new modeling projects, you should start to spec out a data module implementation unless a specific FM feature that is not supported in data modules like perhaps parameter maps or complex security requirements.

Q: Can I add an additional table to a custom table after it is already built? A:  You would need to redefine the custom table.

Q: Can we extract data instead of a live connection in Cognos data modules similar to dataset schedules? A:  Yes, you can integrate datasets into data modules.

Q: Where can I get a recording of today’s presentation of Cognos Framework Manager vs. data modules? A:  This on-demand webinar is available at: .

Machine transcript

0:08 Greetings everyone and welcome to this latest installment of the Senturus knowledge series. Today, we’re excited to be presenting to you on the topic of Cognos Framework Manager versus data modules. We’ll do a comprehensive comparison and discuss some key feature gaps.

0:25 Before we get into the presentation, a few housekeeping items, please feel free to use the GoToWebinar control panel to make this session interactive. We’re usually able to respond to your questions while the webinar is in progress, and encourage you to enter your questions via the question pane in that Control Panel. Which, you can minimize or restore using the orange arrow.

0:50 If however, we’re unable to respond to your question during the live webinar, we will cover it in a written response document that we post on

1:00 Which brings us to the next question we get early and often throughout the presentation, is, can I get a copy of the presentation? And the answer is absolutely.

1:09 It will be available shortly on You can select the resources tab and head to the resources library. Or you can click on the link that we’ll put in the GoToWebinar control panel if we haven’t already and be sure while you’re there to bookmark the resource library as it has tons of valuable content addressing a wide variety of business analytics topics.

1:31 Our agenda, today, after some quick introductions, we’ll do an introduction of those Framework Manager and data modules and provide some comparisons between the two.

1:42 Discuss some key framework manager model issues versus data modules, and demonstrate some solutions to give you an idea of what that looks like in real time. And then stick around for the Senturus overview, for those of you who may not be familiar with who we are, and what we do. Some additional, almost entirely free resources, and then at the end, we always have our great Q and A so, again, get your questions in the Q and A, and we’ll get to those at the end of the presentation.

2:09 So joining me today, I’m pleased to be joined by mister Pedro Ining , Pedro joins Senturus back in 2010 and brings over 20 years of BI and data warehousing experience to his role. In addition to being a regular contributor to our Senturus is Knowledge Series here. He’s been instrumental in implementing data warehousing system from scratch and has experienced the evolution of the BI industry through several iterations of BI products, including Cognos, MicroStrategy, and Tableau.

2:37 My name is Mike Weinhauer. I wear a number of different hats at Senturus. One of them being the emcee for the Knowledge Series, and I’m pleased to be here hosting you today. And with that, I’ll hand the floor and the mic over to Pedro.

2:48 Pedro floor is yours OK, hi, everybody. So today, Framework Manager versus data modules.

2:55 It’s worth mentioning that Cognos has been around for quite awhile since the mid nineties and has quite a bit of a modeling legacy as products that have been around for a while and have morphed with the industry contain.

3:09 So, we all remember modeling with transformer and then Framework Manager and with DMR, we’re just trying to make Framework Manager look like transformer who can never forget dynamic cubes and anybody using that out there. So, dynamic cubes hasn’t been used for awhile.

3:25 We have Cognos data modules with the Cognos Analytics 11.

3:36 The product has evolved quite a bit over the years and we always have to change our ways and how to work with these tools.

3:58 IBM has really pushed data Models.

4:13 It doesn’t really, really advertise Framework Manager as part of the 11, as a feature set, but it’s there.

4:20 And we’re kind of taking the point of, you know, if you’ve got existing Framework, manage your production packages that are working fine. In production you’ve got a 500 reports, again assembler fairly complicated packages and they’re working, OK. Yeah, there may not be a need to port a 1 for 1 implementation.

4:43 To a data module.

4:45 It may not be worth the cost benefit and IBM has no plans to remove product support for Framework Manager.

4:54 It’s not going to be deprecated. Much like transformer which has been around since the mid nineties. Transformers as product line, it can be used with Cognos Analytics 11. The same can be saId for a Framework Manager. Now, as you look across your existing models and framework packages, there might be some opportunity to take maybe portions of it.

5:15 And there might be some packages that you might want to really port over, so that you can take advantage of some of the new functionality with data models. But I would say that you don’t want to take a complete blanket approach and say, I have to move over. Because IBM is not going to support this at this particular product to any longer. So, that’s, kind of like a general statement. I wanted to get that question off the top.

5:39 So, if you are going to be starting a new modeling task, you might want to give a serious look at data modules.

5:50 If some of your modeling tasks don’t need some of the features that are still kind of considered gaps, you might want to give it a serious look. And, in fact, some of the product managers at IBM even stated that you look at data warehouses, maybe start with data models for new projects until you get to the point where you realize that you go through your requirements. Maybe it’s not the right tool yet for the job.

6:16 So, let’s talk quickly about Cognos Framework Manager.

6:19 I’m sure that a lot of you out there who are career manager guru’s developers, have been using it for quite a long time, but, in case of some people out there who wanted to see what’s available in terms of the cross, if they are Cognos landscape, let’s talk about these quick bullets.

6:33 But, a framework manager is been the primary modeling tool since Cognos Reports, for those of you who remember that initial release of Cognos on the web than Cognos 8 in Cognos 10.

6:46 And it’s still widely used in Cognos 11 and 11.1.

6:52 In fact, there are a lot of customers out there who had migrated from Cognos 10 to Cognos 11, who really still only use the framework manager package model paradigm, where the modeling is really IT controlled and centric, and they have not even scratched the surface of using some of the newer modeling tools, like data modules within Cognos 11.

7:14 And historically, Framework Manager has been that IT centric tool used by developers and data modules.

7:22 Data mining, data modelers.

7:24 And it was never really meant for end users, you know, but I’m sure there’s some organizations that I’ve tried.

7:30 They’ve actually let end users get framework manager install on a PC and try to do some packages, But, I think, in general, some users, power users, have kind of throw their hands up in the air.

7:43 So, this is too complicated for what I want to do because I don’t need all that complex functionality of that Cognos Framework Manager has had because its development. Genesis has been more for a very centrally maintained metadata structure for developers and data model modelers.

8:01 It’s kind of like from an era from the single source of truth data warehouse, we all remember, this was the, the, really the end goal, I think, of maybe 10, 15 years ago.

8:10 We need a data warehouse is going to have everything in it that’s going to have a pure, pristine metadata layer.

8:16 And everybody will go to that for all their analytics. And as we know, now, we do need data warehouses. That’s definitely there. We do need some controlled governance on metadata and data warehouses.

8:29 But I think it’s become kind of one of your new sources, one of your sources, to newer BI analytic processes to your data scientists, and your power users, who actually maybe extract data from that data warehouse through a framework package, and then integrate it in other tools that allow them to do that data modeling, much like Tableau and Power BI.

8:51 You know, they’ve come from the perspective.

8:53 Like, users want to model, users want to integrate different sources of data. They don’t want to be hamstrung by data warehouse. Where it takes months, weeks, whatever to add more tables. When I go and get the tables myself, so, it’s a kind of a changing landscape, and it’s good to be aware of that. And also the fact that IBM has stated there will be no future enhancements for this product.

9:18 It might be a good time to start looking at when how can I use a newer modeling tools like data modules, in Cognos Analytics 11?

9:30 Now, Cognos data models itself on the converse is a web based tool.

9:37 Unlike Framework Manager, which requires installation on the PC desktop, it’s end user focused.

9:44 It allows the end user to do their own data blending.

9:48 A term that you always hear in Tableau, we can data blend. Well, as what data models can do, it’s also a good modeling tool from even basic modeling, much like, framework manager against a relational database, and there’s some transformation things you can do within the tool.

10:04 And this tool debuted initially with Cognos 11.

10:08 And it’s really IBM’s response to the whole data democratization trend in the industry.

10:14 But we need to be able to have end users, power users, data, scientists, access, to more data, and have a more agile approach to blending and data modeling.

10:32 So, it’s IBM’s response, I believe to tools that really kind of got the mindshare over the last 5, 10 years like Tableau and Microsoft Power BI.

10:43 And, for those of you who might be struggling out there with people in your organization using Tableau on Power BI and maybe just using Cognos Analytics as an extraction tool, Allowing users to use the newer tools within Cognos will help you maintain that foot footprint if that’s something you’re interested in doing. And trying to maybe standardize a little bit more on Cognos analytics and give it a lot more use across the end user community.

11:12 11.1 significantly closed some on the lot of the technical gaps between FM and data modules. So you modelers out there who have looked at data modules and 11 point no, throw your hands up in the air and say, well, I can’t do this. Can’t do that. 11.1 was released. That really focused on that. We’re going to talk about some of those things here.

11:37 And, of course, all future developmental resources within IBM will be focused on data module enhancements.

11:44 So data modules will continually get better, and a framework manager will be, will be staying exactly where it is in terms of its current development life cycle.

11:59 This slide is just really trying to show you that data modules is an integration point of many different sources. Now.

12:07 On the right are the data modules.

12:10 We basically have databases that data modules can connect to directly, and bring in tables through data server connections.

12:17 We can actually use data modulates to go against your FM packages if you need to. So if you have a lot of FM packages out there already, you still want to leverage data models for certain use case that you could connect directly to the F and packages that are out there, which will eventually go back to your databases.

12:35 And, one of the big things, of course, is uploaded files.

12:38 Your users can upload your Excel files, CSV files, into data modules for datasets, data modules for data blending, And then the new dataset feature up there on the upper right allows people to extract data from Cognos database from databases that are exposed to Cognos create subsets of data that are now stored on Cognos or faster, faster performance and integrate that in the data modules.

13:08 And what’s really interesting so data models can feed other data module. So the permutations is quite large of what you can do and it just really a matter of architecting it properly. But it allows you, that functionality is it allows you a lot of different ways to model and integrate and blend and cleanse.

13:28 So the key thing a lot of FM folks are waiting for, potentially, like, what are the what, and the current state level zero point one, release six?

13:38 What our data module is still missing that might stop you right now, anyhow, to use data models?

13:47 Well, first of all, it does not do DMR demand dimensionally model, relational models, at this point.

13:53 Now, for those of you who have never used it, this may not be a point that you care about.

13:59 Personally, I think GMR models are not necessary anymore, especially with the way a lot of the features are available in Cognos, like, navigation past, you could kind of simulate that hierarchical model.

14:13 And DMR models require a different skill set and reporting, so you’ve got a certain set of report developers, who can write reports against relational models. But DMR is another different set of skill sets you have to have.

14:27 But, again, if you, if you are, if you have DMR requirements, you need to use it. Data Module, student that still did not do that.

14:35 Object based Security, and I hope they could really fix this one up soon. That doesn’t exist still in data modules.

14:43 You want to hide a particular table, are a particular field from within the model of data models, on only exposed at a certain groups, we pay can see this table, group B can’t see that table, that doesn’t exist. So, you have to do workarounds around that. And I’m thinking this is going to be on the upcoming release. I would love to see that there. We could simulate packages better with that one object based security is in place.

15:08 I don’t know how many people out there have used team based modeling.

15:12 I personally have only used team based modeling once where multiple modelers can model against the same FM model, using model of branches and bridges.

15:25 That’s not in there. I don’t know if that’s going to be in there, But, again, I don’t know how many teams out there have actually use it, but, if you absolutely have to have that, that’s not in there.

15:36 Another Big one is parameter maps. This allows for the, is, in one particular, use case for multilingual packages, depending upon your locale of Cognos. So, it could tell you where it could it could based on where the locale of Cognos is set up? If I’m using it for English, if I’m using it for France, He could dynamically change the views of the data through parameter maps. That’s not in there. Another case where I’ve seen parameter maps users for fairly complex row level data security implementations, you might have security tables. You might have to have some fancy macro substitutions in your query subjects. And then, leverage and Parent parameter Maps For that. That’s currently not there. I think that’s on the development timeline, but that’s not in there, either.

16:26 From a style perspective, FM style namespaces packages the whole way we model on FM is different and Data Module. This can become somewhat simulated.

16:39 But it’s a different kind of thinking.

16:41 If you’re trying to do a 1 for 1, Manage the data modules is not really there, but I think some of the functionality is there, sit through some of the newer features that are there in data models, and we’re going to go ahead and discuss that.

16:56 But what do data modules do, what data models do, that framework manager can’t do. Some of, these are pretty big.

17:02 Because as the development of data module’s continues, the gap between data models versus Fabric Manager gets bigger.

17:10 The number 1 big that I can see is the easy integration, uploaded files Like Excel CSV can’t do that in a famous manager.

17:18 And a lot of times, your data warehouse or your model out there, and the databases that are centrally maintained and govern don’t have other things that users need to be able to do analytics. They might have an Excel spreadsheet with a lot of different kind of roll ups from accounting codes to job categories are things like that that they maintain. And they want to be able to blend enjoined that in their queries. So what happens is they get the extract from Cognos bring it down to Excel. They’ve got there.

17:49 Roll up file on a different tab and they do their V lookups there. Well, now, with this weekend, have end users, bring those files up, and then do the data blending within data modules there.

17:58 Simple data cleansing is also built in, for, for debt, for data modules. We can create data groups in that area.

18:07 We can quickly make Uppercase, Lowercase, and Conversions, things like that are kind of built-in to data modules.

18:16 Easy hierarchy creation.

18:18 So, navigation paths, where I could go, create my Hierarchy from Product line, the product type to product, within the model itself. So, the natural drill down is in there.

18:30 When you write reports, are due dashboards, that’s already built into data modules, Automatic creation of relative time, filters are now in there.

18:39 I have a separate webinar that kind of shows you how to do that. You could look it up on the Senturus’s site.

18:45 This has always been kind of a head scratcher within framework manager to kind of do this with complex filters, neighbors, and database changes on a time dimension. But, this automatically is done for you with data modules. Once you put that in, A plugin is fairly simple.

19:01 With the use of datasets, you can bring datasets in and, as you use datasets extracts, did extracts from Cognos itself as you as users use it? They go into in memory. So, these highly formatted parquet files will be placed in memory on the Cognos server and they kind of a job in a round fashion. But, automatically, that’s built in once you integrate datasets into your, into your data module data grouping. We mentioned, and web based interface. The web based interface, I think, to me, is one of a good thing, and a bad thing, especially for those of you who have used Framework Manager for quite a while. Because the PC is, has a lot more finer control Things, like modeling tasks. But what, the web based interface. So, you don’t have to download a program. So I think the web based interface has come a long way since 11.2 release.

19:54 But I think that particular piece of the modeling tool is going to keep getting better and better, OK.

20:02 So, what this webinar is going to address in terms of a demo, are things that typical FM modeling tasks that have been maybe more of an issue within data modules, or they weren’t there 11.

20:17 And you might want to see how we can maybe work around that, or have the new features kind of remedy that.

20:25 Um, like I mentioned, the web UI is not as precise and snappy as FM, but it’s getting better. The three demos we’re going to kind of do is the fact that FM does not have the kind of, data models, do not have the cost of the layers, and namespaces and mala query subjects.

20:42 Alias shortcuts for time dimension type role playing things and determinants, OK? So, we’re going to go and talk about that real quick.

20:50 So, namespace is a model a query subjects. So, the typical FM paradigm of layers and namespaces are missing and data modules.

20:59 No, I want a physical layer. I want to be able to hide that. How can I publish a centrally controlled data module on the right you see?

21:07 And, after working with data models for quite a Bit and I keep looking back or fabric manager, I look at it as it looks pretty complex. Actually, if I was an end user, so, those namespaces are aren’t there, but for those of us who do Favorite Manager every day, this is something that maybe stops me from wanting to do this. So, let’s go over to Cognos right now.

21:31 OK, so, this is actually, we’re running 11.1 Release six and, for those of you who haven’t seen it, there’s some cleanup that they’ve done, Some of the icons Look a little Bit different.

21:42 I think it looks a lot better if, tighten it up and we’re going to go here and create a new data module right away.

21:49 OK, I’m going to go into my Data Source Connections data servers. And I’m going to go ahead and pick the Great Outdoors Sales database that’s available.

22:01 With Cognos.

22:02 I’m going to select my tables and I’m going to pick the order details, the order header, the product table, the product line table, and expand on that a little Bit here: the product name, lookup table, and the product type.

22:20 So, I’ve got details, header, product, line, name, and tight, and say, OK, brings us into the data modules in, if you haven’t seen data modules in awhile has been a lot of changes.

22:34 The relationship view is here and right away, data modules will inherit the joins that are in the database if the joins are defined by foreign and primary key constraints, and that’s what it has done. And you can delete them if you want.

22:53 I’m going to bring the product name. Organize this a little Bit better.

22:57 Product Name Lookup over here, Product line, product type, OK.

23:04 Then over here is Older Details and order header. So this is a typical scenario, right? Is more of a maybe an OLTP type schema basically brought in my physical tables? My database for you if you’d like.

23:20 I’ve got it over here, and generally what I want to do is try to make this schema more presentable to the user, and make it maybe more dimensional, right.

23:31 Let’s go through some of those activities then.

23:34 So, for example, I want to maybe, really just have a sales fact table.

23:39 Now, with the new release of data modules, and 11.1, we were, we were able to create custom tables.

23:48 The newest release, and I think it was five, they have custom tables over here, so, you can kind of see what they are.

23:54 But, I’m going to create a custom table across a two tables, details a header, with new table, and, I’m going to create a new view, when I create a view of the tables, it’s going to inherit the joints that are physically are recreated across those two tables.

24:11 If they’re not joined, I can create a join view here, as well.

24:14 There’s a lot of different areas where I can actually create different views with tables, but we’re going to go ahead and create a view of those tables.

24:23 And I’m going to create those beamed by just clicking Finish, and right away here is my new view of the tables.

24:31 This is kind of U 2 Release 5 custom tables. If I click on this, it shows me what those tables are made up of, OK.

24:41 And also, new to Release five is the ability.

24:44 And this was a big asked by FM modelers the query information underneath that.

24:49 So this didn’t exist for awhile and a lot of FM modelers, throw their hands up, and say, well, if I can’t see, what query is made up of that view, I can’t have fine grained control over that, OK?

24:59 So over here, it shows you the fact that it did inherit the join across those two tables. It shows you the SQL. So that’s kind of you, and that’s kind of really, what these features have been added in, to kind of addressed the gaps that FM has, versus Data modular data models has, versus FM.

25:16 OK, I’m going to go ahead and rename this table to Sales Fact.

25:26 And you can see by the icon, it’s a little different.

25:29 So this is basically a view. And what, basically, this is as a model, a query subject in a sense, create a model Query, subject across order, header and details.

25:39 And I have it over here. Now. If I could really draw a line across this here, I have my physical namespace layer. And here is my presentation layer in the sets.

25:49 Now I want to flatten these tables out here also, because I want to make a product dimension. So people don’t have to go to multiple tables. I could do a shift, click over this.

25:59 Highlights it over here, it highlights it here, right click. And I’m going to create a table. Again, I’m going to create via tables, and say next.

26:06 And I’m going to select the columns I want, because I don’t want all of these to these columns because these tables have a lot of support for multiple languages. And I don’t need all that stuff.

26:16 I guess. I just need, I’m going to go clear all and de select the columns.

26:20 I was like product number, base, introduction date, discontinued date, OK From product line.

26:29 I’m going to pick the product line curve the English name version of that from product name, look up.

26:35 I’m going to want the product name and description. I’m also going to want the product language. And we’ll talk about why I want that in a second.

26:45 And on product type, I’m going to want the product code, Type curd and the product type English name.

26:55 Do I got everything in here, Product line, everything, good things I’ve finished?

27:00 And there it shows you exactly what this view is made up of this Model query subject can assess. I’m going to rename this guy to my Product dimension.

27:15 Now one thing I want to show is the product name, look up lookup table. Then we have a grid panel where you can see that. The data, and that’s one of the cool things about it as I started working with as being of being an FM model for quite a while. The ability to just kind of look at data really quickly, is very nice. OK, you can see that we have multiple product languages for each product, and if I left it as that, I’d get double counting when I joined this to my sales fact table. So it wasn’t a pair when I edit that. When I created this View as well, where do I put that filter?

27:47 And it wasn’t really in the Create Table dialog box where that is actually over here now, Properties. So you see filters over here.

27:59 I could put a filter on that view, and it allows me to say, well, what kind of filter do you want to put as a column? Do you want me doing a column, which I do? But it also has this expression editor. Now, I’m going to click add a filter for expression editor. It basically comes up with the expression editor for reports.

28:16 I can even use macro substitutions in here. If I do want to do something more complex things for this view, OK? So that’s, that’s in there now.

28:26 But what I want to do is, I want to add a filter based on the product language.

28:32 I want to do add a filter is going to distinct on that, and I only want to filter on English.

28:39 And I’m going to say, OK. So right now, the icon now is showing you that we’re filtering this product Dimension view.

28:47 And this is the filter we’ve added. And if we again, look at the query information, we could see that as put the where clause right there, OK.

29:00 Going back to my relationships, the next thing I’m going to do is create a join relationship, a typical star schema type, Join relationships here, from product to Sales, fact, product number two, product number, match, my selected columns, and say, OK.

29:19 Yeah.

29:22 So I’ve done kind of the core thing of creating the start of a star schema. And within here, within here, I could much like a Model Query subject, presentation layer.

29:33 I could actually move my columns around within the product dimension here. I can rename my columns.

29:42 Just get rid of that, Ian, for example.

29:48 And I could also know Crepe folders here for measures.

29:57 Make it more, presentable.

30:04 To the end user, much like you do in the presentation layer and FM.

30:10 Like that, OK, I’m going to go ahead and save this guy, save as in my live webinar folder. I have a backup there, in case I need to, but I’m going to call this as DM two, for example.

30:26 Save that off.

30:30 And the other thing I’m going to do to make it more presentable to users, I have all these tables here which now these reviews off and Manager, I would create a package and hide the tables that I don’t want people to see.

30:44 What I could do here is create a New Folder, and we’ll call this the physical layer.

30:53 And I’m going to just pop all these physical table’s back into here.

30:57 And I’m going to go ahead and say Hi.

31:03 OK, so now I’m going to go, Dave, that one more time. I’m going to go back out here. Now you could, if you wanted to, click, try it, it’ll bring you right to the reporting tool. I’m going to go a little, some different I’m going to do, but a typical user would do, I’m going to go to my DM two. I’m going to right click on this and say create Report.

31:26 So now my data module looks kind of like a package, right?

31:30 And I’ve hidden the physical illness of that, and users can now write reports against this, any easier fashion, because my measures are over here. My product dimension is all one flat dimension.

31:44 And I want to, maybe, product line by, product type, insert that. I’m going to insert quantity.

31:55 And then run that query.

32:02 So there we go, OK.

32:06 Let me go back to my data module.

32:08 So we’ve, we’ve done that. So let’s go back to that, what we were talking about. So namespace is the mala query. Subs, OK? It’s not a 1 for 1, right? But it’s kind of a leaf. We’ve kind of fill some of the functional requirements to maybe do something like that.

32:22 The other option, as I say, how can I publish a simply controlled data module?

32:26 What some people might want to do is crater on data modules but they don’t want to know how to bring all the tables and do all the join from a physical perspective. But we can do is maybe just publish out a data model that only has a physical layer in it. It’s it has everything there. We might put a read only stamp on that and then people can work from there. So, if I go over here, let me go to.

32:56 This folder, I have a physical layer over here.

32:58 I could actually create another data module off of that.

33:03 These are links.

33:05 The end user will have no way to change that.

33:08 But then I could leverage the ones, the links here, that IT has created. And I could then create my table over here that I can create my sales fact this way.

33:22 This becomes my sales fact folder or query subject, model query subject, OK, another alternative way to do it, uh, in publishing centrally control type IT maintain data modules so that some of your more power users, your data scientists, whatever. Can use those. And create their own data modules and build their own presentation layer on top of that, OK.

33:53 So as you saw, one thing that I kind of glossed over, I kept changing this and saving it. And what’s the reporting to the right away? I didn’t have to publish a package, right. I saved it and published the package, I save, than I went to the reporting tool. I wrote my own reports real quickly.

34:06 So, the Prototyping the Agile ness of the tool is much faster than, obviously, framework manager, where I have to model everything on the PC. I’ve got to set up my package.

34:20 I got to publish it, you know, and then I go back into Cognos, then I look at the package and, you know, that whole thing is all within the web tool, OK?

34:29 That’s another differentiating factor.

34:31 OK, let’s go back to our slide deck real quick. The next one here is the concept of alias shortcuts. This is a very important piece of modeling the modelers love to use. If you look at the framework, manage your package, a model of there. We have the sales fact. They’ve got two dates over there. They have the order date, and they have the ship date, and I need to be able to analyze across two different time dimensions. I got one physical time dimension table.

34:59 And in Fabric Manager, I was able to right click and create alias shortcut off that physical time dimension, and use that and leverage that, OK?

35:08 There is no right click Create Alias shortcut in data modules. But let’s go back to data models again.

35:16 So I’m going to bring into my time dimension.

35:21 Over here, Add more tables, I’ll look for it.

35:27 Again see, the search is pretty nice, is pretty quick time dimension, and say, OK, there’s my time dimension. The one thing I also mentioned, as aside from a maintenance perspective, released six got really good to happy. From a usability to maintain these modules, because what we didn’t really have before as a way to reload the metadata to see what tables we have in our data model versus the physical tables.

35:58 Here in our sources, we see all the physical tables that are available. I’m going to go on my time dimension over here.

36:05 And I’m going to maybe delete some of these fields. I don’t need these fields.

36:12 From the physical table that I brought in.

36:15 There’s a new feature in here, which shows unused items.

36:19 And if I expand my time dimension over here, scroll down.

36:24 These aren’t there, so if I did, not, if I deleted them here, I can actually, now, individually, from a field perspective, just drag it in before there was a real pain to kind of get that done. And also before, somebody, physically, if the DBA changed a table, and added more fields, it was hard to refresh. That had to go back to the data source connection and refresh it. Well, now you have a right click here and you can see reload metadata.

36:50 OK, so another FM modeling issue was, Alice too hard to maintain the field’s command? It’s really hard to bring in a new fields on that, OK, so that was another thing that was kind of fixed. And basically major your life easier to use.

37:07 All right, so back to the original thing, the alias shortcut. I have a time dimension over here.

37:13 Aye, want to be able to create alias shortcut? Well, it’s not there but we can leverage this whole concept of custom tables. We’ve already created a couple of these. We can go to the time dimension.

37:25 Say, you table.

37:26 We’ll create a view of the table.

37:31 And I don’t want all these fields, for the purposes of this demo, I’m going to clear all, I want only the day date. I want the month key. I want the current month.

37:42 I want the core to key our current quarter, I want the current year, and maybe I want the month, English name.

37:51 I’m going to bring that in.

37:53 Say, Finish.

37:54 Now, I’ve got a view. Now, my views are kind of building up, I have another view over there, OK.

38:00 Um, and the one thing about this, and brought the current month number, and current core number and as Measures, by default, because it’s in America.

38:10 Variant Manager had a really nice feature where if I did that and drag down the attribute column and it’ll change that, thought, we have something similar here as well, I can multi select that column over here, go over to my properties, pain, which is over here.

38:29 And change the usage over here to say attribute, which is what I want to do. OK, and I want to make this, the ship dimension.

38:42 So I’m going to, I’m going to rename this, the ship date dimension.

38:52 Now I also want to be able to have an auto date dimension here as well. I could do the same thing, I could create a custom view of time dimension. But it’s a really nice copy and paste type feature over here. I’m going to go ahead and paste.

39:06 And I’m going to rename that guy to be order date dimension.

39:15 OK, then I can rename my fields, making them more pertinent to be whether it’s ship or to date like I would want maybe.

39:24 This one here to be, you know, rename this to be the ship date.

39:31 Etcetera, I want that to be the ship year.

39:38 Same thing with Order Date Dimension. I want this to be the order date.

39:45 And I want current year, to be order you.

39:53 These are my roleplaying dimensions.

39:57 Order date.

39:58 Ship Date, OK, get this filtered out of the way.

40:05 And, I want to now just simply join ship Date to my Sales Fact.

40:10 I’m going to clear relationship from here to my sales fact: Ship, date to ship date.

40:19 Or a date relationship, too.

40:22 Sales fact, or due date, or a date match?

40:27 Refresh.

40:28 We’re good, OK?

40:30 So, you can see my star schema is getting linsey built out over here.

40:35 I’m going to save this.

40:38 Also, what’s a nice feature? I’m going to go back to my reporting tool to test this out.

40:42 All I have to do is refresh loads backs back up.

40:48 And I’ll bring it back in.

40:55 Well, it should have.

40:58 Live demos.

40:59 So I did that, say, uh.

41:09 Say that again.

41:10 Let me go back out here and OK, I did bring it in. I just wasn’t waiting long enough. There we go. So there’s my ship date dimension.

41:20 And I’m going to go over here, delete that.

41:24 I’m going to do a list.

41:28 We’re getting an error as heroes.

41:31 I’m going to close this report down.

41:35 Going to go back over here to my live webinar, Enter, or write that report again, Create report.

41:49 OK, now let’s dial list.

41:52 OK, so my ship date, I’m going to bring in a ship beer.

41:58 I’m going to bring in order here.

42:03 And I’m going to bring in for my sales fact.

42:08 The measures?

42:11 Order quantity, OK, and I’m going to go ahead and run this.

42:24 I actually should have put order here. Let me do that one more time. I’m going to actually, put order for us to make it easier to look at.

42:33 Me too!

42:36 Order year! Over year.

42:38 All right, let’s rerun that again.

42:46 So I’m basically now running a query across two roleplaying time dimensions, so as you can see, things that were ordered in 2010.

42:57 Had things that were shipped in 2011, the next year. And things that are ordered in 2010 had things that were shipped, and also in 2010.

43:05 OK, same thing across here, so that shows you the fact that I’ve been able to slice across two time dimensions with that data module.

43:16 So going back to the data module.

43:18 Let’s clean it up again, and I’m going to put the time dimension back into my physical layer.

43:24 I’m going to go back over here.

43:26 Now, guys, ship date order, product sales, save.

43:33 Let’s test the Cognos gods and go back to that, you report and refresh that and see how fast now? It was faster? That was good, OK?

43:45 By the way, our instance of this is on Azure. We have Cognos on Azure installed so I am going to go into the cloud to run this. It’s pretty snappy, as you can see just a little side note, so I made my change the data models real-time. I saved it. I went back to my report refresh data and now I’m building out my model here. Now, I’ve got to ship date, order date, product dimension, sales fact that I’ve done fairly quickly in this modeling exercise.

44:14 Trying to address some of the key issues as you move from framework manager, how I do, for example, uh, roleplaying dimensions and namespaces, et cetera.

44:26 The last topic we did alias shortcuts, custom tailored views, and it’s always been kind of a head scratcher and but for those professional modelers are those Mahler’s power users and know how to do this and framework manager. It’s a really important feature to have. This feature did not exist in Cognos Data modules: Data Module 11.

44:50 It now, it started to exist and 11.1 and has done better for the releases, determinants, manager, versus columned dependencies.

44:59 We need determinants when we need to use one time dimension, as say, the day, grain, and we want to use that same time dimension and cross multigrain facts.

45:11 So, for example, I’ve the sales fact that I’ve created is at the date granularity, but I have sales targets at a month level.

45:23 I want to be able to do cross joins across those things across the two for cross fax multi queries with the same time dimension.

45:31 In Fabric Manager, we use determinants, and here’s the screenshot. And every time I don’t do framework manager modeling for awhile and I have to look at the determinant screen, I always have to scratch my head and say, how does this work? Again?

45:44 It was never really that intuitive.

45:47 And if you can imagine, end user looking at this screen, they would, again, probably just throw their hands up in there and say, that this is too hard, right? And that’s what we’re trying to get away from. Would not want that? We want this power to be enabled in the end user’s hands.

46:04 So Data module’s has simplified this concept with the concept of column dependencies.

46:11 So let’s go back over here, and I’m going to bring in another table.

46:19 Add more tables, select tables.

46:21 And I’m going to bring in my, look for it, look for it. Sales target, here we go.

46:30 It inherited a relationship. I got to get rid of that for the purposes of this demo.

46:35 Here’s my sales target.

46:37 If we look at this data from the Grid view, we have sales targets over here, at the grain of Year, month. And even at a higher level of product.

46:49 We could put determinants on product as well.

46:53 But what I want to do, and, again, for the purposes of this demo, I want to be able to use one time dimension, we’ll say, ship date dimension across the two, Right, if I were to create a relationship to sales target right now, and the grain of sales target is year and period.

47:14 And I went from ship year to sales year and current month to sales period, Mats selected column, and say, OK, right, and say I’m done.

47:27 The effect is this, I’m going to save this go back to my report, Refresh.

47:36 Sales target is now there.

47:39 We’re going to delete this real quickly here.

47:40 We’re going to create a two column report, over here.

47:45 I’m going to create a list, and I’m going to query my sales target table directly.

47:52 I’m going to bring in these three guys.

47:56 Over here, I did a join to my ship date dimension.

48:02 And I’m going to leverage the date field from ship date.

48:06 I’m going to put in that **** beer.

48:09 Click off of this. I’m going to put ***** Beer.

48:14 Current month number.

48:16 And I’m going to put in that sales target, and start over there. Let’s run that query.

48:28 Alright, so this left one is from the Ross, the raw sales fact.

48:34 Table by itself. This is the right number.

48:37 Sales target for January’s, $57 million.

48:43 But, over here, the sales target was inflated 31 times because the date dimension is at a granularity of the day. So for January, multiply 2 times 31, February maybe 28, et cetera. So how do I fix that is the question.

49:02 Let’s go back to Data Modules.

49:06 I need to be able to create a determinant on the date dimension.

49:09 And with data models, we now create column dependencies. If you right click on here, there’s an option called Specify, Column, Dependencies, and this is really easy.

49:20 Very intuitive.

49:22 So, for example, I’m going to start with ship year. That’s a top level.

49:27 And I’m going to bring in the key for quarter level is the quarter key.

49:33 And all you have to do is drag the relationship here. So ship goes to Quarter.

49:39 Quarter goes to month, and drag it over here.

49:43 Month goes to Day.

49:51 And one thing about data modules, it does a constant data validation, or validation of your model. And right away, it tells me there’s something still wrong.

50:00 If you click on this validation issue, and you show the details, what it shows you is that there are certain columns in your column dependencies that you have not accounted for, current month, current quarter, month, English name. If you actually went and query included, those who wouldn’t know what the dependencies are.

50:18 So, all we have to do is clean that up. So, current month.

50:22 Number is really an attribute of month key. We’ll put that over here.

50:28 It really validates and the list is getting smaller.

50:32 Current quarter is an attribute over here.

50:36 OK, and we’re down to month end, which is the month, English name or the short abbreviation, and that’s going to go over here, and the validation will go away.

50:48 I’ve established my column dependency, and there’s also a vertical view you can look at.

50:53 However you feel, it’s most useful, OK, so now, this relate this, this. This date dimension is now properly set up.

51:02 Let’s save it.

51:05 I’m going to go back into my report.

51:09 Refresh the data.

51:12 Let’s rerun the report.

51:20 I was hoping you would come up with the right answer, and I did this being a live demo.

51:25 So you see now, even though I’ve used a time dimension that’s at the day grAIn, across a fact table, that’s at the month green, I get the right answer.

51:40 OK, and now I can make proper queries with sales Face to get me a multi grain, a multi fact query. I’m just going to use Quantity for this example.

51:53 I’m going to put it over here, and then, run that. It’s not going to be really a good comparison of Sales target, MLIS. I just wanted to kind of show the query information on that.

52:07 OK, so that works, what does a query look like for that?

52:14 Query two?

52:18 Lot of query, But what I want to show you is, it has the Coalesce statement right here.

52:24 That’s what it’s doing.

52:25 Two queries against two fact tables, using a date dimension, that a different grain, then one of the fact tables, OK?

52:34 Go back to my data module.

52:36 OK, so in the span of, really, actually, if I were to do this without talking, and I knew what I was kind of doing. This is really a 15 minute deal. Right?

52:45 And I’ve kind of addressed some of those issues with Fabric Manager, Right? So back to my slides, over here.

52:54 To me, that was a lot easier than trying to figure this out, and then publishing the package.

52:59 As you can see here, there’s a determinist uniquely identified group by, what are the attributes for it? Very complicated, from an end user perspective.

53:10 So those were the three things I wanted to demo today. The takeaway from this webinar, as, I hope, that you can see that the gap between Data Module modeling from a professional modeling perspective. From those folks, who are you constantly used to using framework manager and creating a package?

53:30 That Gap is definitely narrowing release six with that refresh metadata, but there’s a simple button, but I remember I was working with customers and saying, until I can do that, I’m not going to touch it because I don’t want to be able to delete tables and bring things and all the mast and redo everything. There’s no way I’m going to put that out into production. I can’t, I can’t maintain it, OK. They fix that. That’s done, and that was a huge thing. Again, this webinar was kind of tailored to the FM folks and to show you what you can and cannot do.

54:05 You’re going to have to make your decisions on whether you want to start that new modeling project with data modules. I think you should definitely give it a hard look at first.

54:18 Before you think about maybe starting a brand-new project with framework manager packages, you go through the list of what it can’t do.

54:25 If you have slightly habitat parameter maps for link languages, complicated security models, you need object level security, for whatever reason, and I think that’s going to get fixed soon. Then, you go, you’re going and you have a deadline. You’re going to have to go back to your fabric Manager packages, you know, but it allows a lot more functionality and we didn’t really talk about the functionality that end users can use us for. This webinar was more geared for framework manager versus data models. But, there are probably a whole set of customers out there who are bringing coming in, maybe Cognos Analytics, 11 clean without any of the legacy history of it.

55:04 And using data models. Because that’s the modeling to know. And even consultants out there, you’re going to have to maybe go into customer bases where they’re going to maybe say, I don’t want to use Frank Manager and for whatever reason, to use a data modeling tool. But you have this correct, or you’re the kind of still leveraging your knowledge on…

55:20 Manager, and you want to be able to take those best practices that you’ve learned framework manager and possibly. Go and use it in the new modeling tool the modeling tool.

55:31 That’s going to be enhanced and all development resources are going to so that is I was able to do it.

55:40 At 11 55 I was a little worried about was a fairly complex demo with Pedro that up so I’ll get back to Mike.

55:50 We’re moving going to move pretty quickly here. We might run a little past the top of the hour mm stick around, folks. So there’s a there’s a million questions, Pedro. So go ahead and take a look at those projects working from the top-down. If you don’t mind random past the top of the hour, people will get into those questions in just a few minutes before. We do a quick poll in terms of asking you going forward. What do you plan to do in terms of Cognos metadata modeling? And you can select all that apply. So are you going to use framework manager data, modules something like Microsoft Analysis Services, or something else?

56:23 So go ahead and get your votes in there.

56:26 Give me all about Nan to do this, since we’re on pretty tight time here.

56:36 Great. Kind of a two thirds, you getting your votes in here. That’s great. Alright, I’m going to close it and show it. And so it’s still two thirds, and then a whole ton, almost 83, 83% here using data modules. And than a smaller percentage of Microsoft, and other undecided.

56:53 All right. Thank you very much.

56:55 So, before we get to the, if you could advance the slides, a couple of them, Pedro, to the gut cognitive challenges. So in your organization, one more if you have if you’re suffering from time consuming data prep, where you can’t drill down to from summary to detail, you have performance issues, or for user adoption, we can help you with an architectural assessment that we do, that involves best practices, modeling.

57:19 We do a health check on your metadata, performance tuning, tips on enabling self-service culture, and selecting the best tool for the job, for example, using framework manager and or data module’s as appropriate.

57:33 So a little Bit about send tourists here. We are the authority in business intelligence. We concentrate our expertise.

57:41 We go to the next slide, Pedro, on business intelligence with a depth of knowledge across the entire BI stack and next slide, please. Our clients know us for providing clarity from the chaos of complex business requirements, disparate data sources, constantly moving targets, and ever changing regulatory environments. We’ve made a name for ourselves because of our strength and bridging the gap between IT and the business, by delivering solutions to give you access to reliable analysis ready data across your organization, enabling you to quickly and easily get answers at the point of impact, in the form of the decisions made, and the actions taken.

58:15 Next slide, our consultants are leading experts in the field of analytics with years of pragmatic world expertise. And experience advancing the state-of-the-art, everything from front end dashboard, reporting, and visualization creation, through Data prep operation, all the way through infrastructure, and, of course, training and mentoring.

58:31 We’re so confident in our team and our methodology that we back our projects for the 100% money back guarantee that’s unique in the industry.

58:39 We’ve been doing this for awhile, but at it for almost two decades, Focus exclusively on business intelligence. We work across the spectrum, from Fortune 500 to mid-market companies, solving business problems, across every industry and functional area, including the Office Finance, sales, and Marketing, Manufacturing, Operations, HR, and IT. Teams both large enough to meet all of your business analytics needs, and yet small enough to provide personalized attention.

59:04 Again, we invite you to visit the Senturus’s website, the Senturus Resources tab, where you can find all our webinars and the recordings on the deck and everything behind those until all kinds of great information. Our blogs and tips and tricks and everything on that site bookmarked upcoming events. We’ve got another great webinar coming up on Tuesday, July 28th, same time, same Channel, Cognos analytics dashboards, or reports. So, come in.

59:31 Visit us for that. And, of course, we would be remiss if we didn’t talk about our fabulous training.

59:37 We offer training in the top three, three top BI platforms, IBM Cognitive Analytics, Power BI, and Tableau, right? Deal for organizations running multiple platforms, or those moving from one to another. And we provide training and many different modes, It can mix and match those to meet and suit the needs of your user community.

59:59 Senturus provides hundreds of free resources on our website, and we’ve been committed to sharing our BI expertise for over a decade.

1:00:07 And now we finally get to the illustrious Q and A and so as you can see, Pedro, there’s a whole ton of questions here. I know, are at the top of the hour, so I don’t we try to bang out a few of those, and anyone, you can continue to put questions in the question panel here.

1:00:23 We do save that question log, and we will answer any questions we’re not able to get to, via that login will posted, along with the recording and the deck on, and that Resources section.

1:00:35 So go ahead, Pedro.

1:00:36 If we want to bang out a few of these, we can we can do that. Yeah, and stay on the moon.

1:00:42 See, some can expand this one box, but maybe you could address this. Mike is IBM at least considering, I think. It’s a migration tool.

1:00:50 I don’t, I’m not aware that they are It’s certainly something that we in our labs are actively pursuing because we know that it’s, it’s, it’s feasible. So we’re looking to do exactly that to help people if they want to migrate from Framework, Benadryl models to data modules and have some technology to help them with that.

1:01:10 So if you’re interested in that that’s a need in your organization, definitely give us a call OK, can data modules reads synonyms? Well, that’s an Oracle question, I think, more specifically as you connect to an Oracle database through the data server.

1:01:33 If it’s part of the schema that you’re trying to get to my initial gut, is it does.

1:01:38 I’d have to actually verify that and look at it from an Oracle database and see that it can read a synonym, but if the user that you are logged into, can see it, I’m pretty sure the data module can see it.

1:01:52 Procedures, stored procedures? That’s a good one. There is a widower, right?

1:01:59 I haven’t tried it was stored procedures yet. But you can write manual SQL and if you can make manual SQL, you can do a create table and I didn’t show this one.

1:02:08 Create a manual table with, create a table, with Manual SQL. You could potentially, maybe, call a stored procedure, but I’d have to try that out, that’s a good question, sure, Sure, and then, someone mentioned about DMR and framework manager can. And I know you can create hierarchies and data module. So that’s kind of similar to that functionality, but not exactly equivalent, right? Not exactly equivalent. I mean, the EMR is very specific corner section of bench they can do, which makes it look exactly like an old … cube. That kind of functionality is not built into data models. Whether it goes in there or not, I’m not sure. We haven’t got to read from that an IBM yet.

1:02:48 OK, we had a question about Automating the Refresh, the data modules, I’m not sure exactly what that means, necessarily, because they’re not really.

1:02:56 Yeah, I think maybe it might. Unless you have less, you’re referring to data, sets, extract data that can be put into data modules, those things can be automated to be refreshed, because you can set the set those on a schedule.

1:03:11 It’s very easy to do from the user interface.

1:03:13 You create your dataset, and you set a property about a schedule, you enable that. And then when, when people hit the data modular, which contains a dataset, it’ll show the most refresh data. So, that’s the only thing about refresh that related to data models. Yeah. Yeah, exactly. Someone asked about the Senturus’s analytics connector and if it supports data module. So for those of you an initiated, we have a product called the Analytics Connector that allows you to use Tableau or Power BI to access your cognitive metadata. So, Framework Manager Models, reports, and Data module. So, they asked if we supported data modules. And the answer is, yes, we do.

1:03:50 Filters on the FM, Database Query subject, based on session parameters. Can you replicate that in data models? And I’m guessing that you can’t do that because of that. We don’t support parameter maps.

1:04:02 We don’t support parameter masks what I haven’t tried out. It does create a filter with an expression editor. And I’ve seen that it can reference macro substitutions.

1:04:11 Um, So that’s something to look into and try.

1:04:16 We’ve done that I’ve done some very complicated thing was parameter maps Macro substitutions and FM, like getting to security table and just in the where clause with session parameters, based on your ID, the user IDs, and the security table, etcetera. I would think that’s going to get better. And I know parameter maps are number one thing. They want to add data modules, but you might want to take a look at the area of filters, where you do a filter by an expression editor and see if you could use the macro substitutions to get. Maybe this has parameters there.

1:04:44 And try, try to play with it there and see that that, and that, that satisfies your requirements, OK, we’ll do one more here, and then we’ll probably to let people go here, shared data modules, Can they do the impact analysis like FM does, in terms of determining and showing you impacted reports by changes that you make?

1:05:02 No. Not that I’m aware of. Right. So, yeah, you’re right.

1:05:05 If data modules are being used by a bunch of reports, that particular functionality is not there OK. Great. Well, again, we have a ton of questions here. We will save the question. Login will answer that posted to the website, if you want to go to the last site. The last slide, Pedro. I want to thank everybody for joining us today.

1:05:27 And thank our speaker, Pedro Ining, for a very informative and information filled session. On behalf of myself and Senturus, thank you for joining us. We look forward to seeing you on one of our upcoming events knowledge series. Or you can reach out to us for any of your business analytics, needs, your training at

Connect with Senturus

Sign up to be notified about our upcoming events

Subscribe to our newsletter

cognos framework manager presentation layer

Book image

IBM Cognos Framework Manager [Video]

By : aaron solar.

Book Image

By: Aaron Solar

Overview of this book, related content you might be interested in, current title:.

Small book image


  1. Model design and presentation

    In Framework Manager, it's recommended to model multiple layers that include: The database layer for the imported tables. This layer is considered the metadata cache. The business layer for model enhancements and presentation. This layer also acts as an insulation layer for reports to protect them from changes to the underlying database layer.

  2. Best Practices in Cognos 8 Framework Manager Model Design

    One of the basic tenets for best practice model design is to segment the model into four specific sections or layers (Data, Logical, Presentation and Dimensional). Each layer has a specific function and set of modeling activities. Generally, the layers build upon one another, with the data layer being the foundation of the model.

  3. Creating the presentation layer

    The first thing we must consider while creating our presentation layer is how to create groupings of related items. For example, order lines, order headers, customers, and order items could be a group of items that logically go together; invoice lines, invoice headers, customers, and invoiced items could be another logical group. Generally, we ...

  4. IBM Cognos Framework Manager

    A proven practice for Framework Manager Meta Modeling is to divide your model into a series of layers, each layer having a specific purpose. (Originally IBM recommended the use of two layers (data and modeling), but later added a presentation layer, and (optionally) a separate dimensional layer). The layers should be: The top layer - or the ...


    englishspacedog YouTube tutorial from Canada Framework Manager - Presentation Layer & Report Studio

  6. IBM Cognos 10 Framework Manager

    Chapter 6. Creating the Business and Presentation Layers This chapter will cover the creation of the business and presentation layers. The business layer is where we apply various business information … - Selection from IBM Cognos 10 Framework Manager [Book]

  7. Cognos Framework Manager Layers Theory

    Cognos Framework Manager LayersData Layer - Data Layer, Database Layer, Import Layer.Business Layer - Business Layer, Logic Layer.Presentation LayerThis vide...

  8. Best Practices in Modeling IBM Cognos 10.2

    The Presentation Layer is built from several Star Schema Groupings. Star Schema Groupings make the model more intuitive to the end user by showing only related facts and dimensions. ... IBM Cognos Framework Manager offers a well featured metadata modeling tool that allows a durable approach in modeling semantic layers. The introduction of ...

  9. Best Practices in Cognos 8 Framework Manager Model Design ...

    Framework Manager will automatically create multiple data sources, (one per schema, for example), but they should reference the same Content Manager Data Source. The reason minimizing these is because multiple Content Manager data sources will open separate connections to the database and force Cognos to perform simple joins within the ...

  10. Calculations in Presentation Layer

    Cognos 10 BI Framework Manager Calculations in Presentation Layer; Calculations in Presentation Layer. Started by raj_aries81, 20 Aug 2017 07:20:15 PM. Previous topic - Next topic. ... --->Intermediate Layer (..where I model my star schema) ---> Presentation Layer (..mere short-cut to my Intermediate Layer using create star schema grouping).

  11. Why go with 3 layers in Framework Manager Model?

    Hi, If you are modelling a normalized source, then three layers are really the minimum you can get away with. The foundation layer will reflect the underlying tables and joins in the database (s), the logical layer will typically be used for resolving traps and conforming to structures providing accurate, consistent query generation at runtime ...

  12. Best Practices in Modelling IBM Cognos 8 Semantic Layers

    The presentation layer is build from several star schema groupings. Star schema groupings make the model more intuitive to the end user. ... Cognos 8 Framework Manager manages the semantic layer of a Cognos 8 deployment. A modeller's main focus is creating a user-friendly, comprehensive model that provides in repeatable and predictable query ...

  13. Framework Manager Layers

    Cognos will do this for you for free with the metadata wizard, and then you don't have to do it in the business layer. It doesn't make much sense to me to create tables/relationships in your database modeling tool (e.g. ERWin), generate tables from the tool into the database, and then import those tables into Cognos, only to recreate all ...

  14. PDF IBM Cognos Framework Manager Version 11.1.0 : User Guide


  15. Cognos Framework Manager vs. Data Modules Comparison

    Knowledge Center. Instructor-led online. Cognos Framework Manager vs. Data Modules. June 25, 2020. Share. Each release of Cognos sees incremental improvements to data modules. Over time, the functionality gaps between data modules and Framework Manager have narrowed substantially. In fact, data modules are a powerhouse of a tool.

  16. IBM Cognos Framework Manager

    If you are upgrading Framework Manager from an older version, you must first uninstall the older version of Framework Manager. For more information, see Uninstalling IBM Cognos Analytics . Before you install Framework Manager, close all programs that are currently running to ensure that the installation program copies all the required files to ...

  17. IBM Cognos Framework Manager [Video]

    Framework Manager, part of the IBM Cognos Business Intelligence suite, allows users to model data to facilitate report development and delivery. Framework Manager acts as the middleware between the database and report-writing tools such as Workspace Advanced and Report Studio. ... Learn how a good presentation layer saves time for the report ...