The document discusses Cognos data module architectures, focusing on their features, use cases, and comparison with legacy Framework Manager models. It outlines various architectures including IT-driven, hybrid, and end-user driven models, as well as governance and performance considerations. The content also covers common questions and answers regarding data modules, emphasizing the transition towards data modules for new projects while considering existing Framework Manager implementations.

1. Cognos Data Module
Architectures & Use Cases
1
Thumbnail

2. 2
Hundreds of resources
Visit the Resource Library
on the Senturus website
to download this presentation
and explore other assets:
senturus.com/resources
2

3. 3
Pedro Ining
Principle BI Analytics Architect
Senturus, Inc.
Michael Weinhauer
Director
Senturus, Inc.
3
Introductions

4. Agenda
• Introduction
• Cognos data module architectures
• Data set libraries
• Use cases
• Senturus overview
• Additional resources
4

5. Enjoy the full webinar presentation
This slide deck is from the webinar Cognos Data Module
Architectures & Use Cases.
To view the FREE video recording and download this deck,
go to https://senturus.com/resources/cognos-data-module-
architectures-and-use-cases/
5

6. Cognos data modules
• Web-based end-user focused data blending, modeling,
transformation tool debuted on Cognos Analytics 11.0
• IBM’s response to data democratization and other tools
like Tableau and Microsoft Power BI
• 11.1 R7 significantly closed some of the technical gaps
between Framework Manager and data modules
• All future development resources will be focused on
data module enhancements
6

7. What are data modules still missing?
• DMR (dimensionally modeled relational)
• Object-based security
• Model branches and merges – team-based modeling
• Parameter maps
• Multi-lingual packages
• Complex row-level security implementations
• FM style namespaces (but we can somewhat simulate)
• FM style packages
• Search and select prompt for reporting
7

8. Data governance is a framework for
ensuring the availability, accuracy,
and security of data across an
organization.
8
•IT driven enterprise model
•Hybrid model
•End-user driven model
Data module architectures
Many ways to use data modules, but we would like to
discuss potential key architectures that you can use to
implement data modules

9. 9
IT driven enterprise model – classic FM
 IT gathers report
requirements
 IT develops the Framework
Manager model
 IT publishes packages from
the Framework Manager
model
 IT creates standard reports
from the package
 Users may create their own
ad hoc analysis reports from
the package

10. 10
IT driven enterprise model – data modules
• Replace the use of FM with data modules
• For new modeling projects, they are driven by business requirements vs.
modeling the entire database
• For existing legacy FM models, select business relevant subject areas in the
model that need to be redesigned for better self-service
• The data module is READ ONLY and controlled by IT
• End user modelers can ‘link’ to this module or create data sets for their own
modeling purposes

11. 11
Hybrid model
• Uses legacy IT
maintained FM
packages
• Part of the package
can be integrated
into a user or IT data
module
• Legacy packages
used to create
datasets for use in
data modules
• Allows user access
to spreadsheet data

12. 12
End-user driven model
“Point me to the data, I’ll take care of the rest…”
 IT maintains the source
databases or data warehouses
 Use Cognos self-service
modeling components to model
the database for specific
requirements
 Users extract subsets of data
from source databases via
Cognos data sets technology;
which are integrated into data
modules
 Users may upload their own
privately maintained curated
data from spreadsheets or text
files

13. See demos of the three data module
architectures
To view the video recording and download the slide deck go
to https://senturus.com/resources/cognos-data-module-
architectures-and-use-cases/.
13

14. 14
Data set libraries
• Common data sets for use in user or IT defined data modules
• Subject specific dimensional/reference data or summarized fact data
• Not meant to store large amounts of data, typically 10-15M rows max
• Allows for better performing queries/reports
• Stored in common folder structures
Databases FM Packages
Common Data Sets Stored in Team Content

15. Answers to participant questions
15

16. Cognos Data Module Architectures & Use
Cases
16
Q: Is it possible to connect multiple fact tables to the same dimension
table or multiple dimension tables in Cognos? For example, if we have five
fact tables and three DIM tables with four out of the five fact tables
connect to three DIM tables?
A: Yes, this typical star schema model is fully supported by data modules.
Q: If our users have read only access in Cognos, can they copy data
module from their “My Content” and make changes all join?
A: Much like a report, users can copy the data module to their My Content and
then make changes. But they are no longer linked to the READ ONLY data
module and will no longer see any more changes that IT may make.

17. Cognos Data Module Architectures & Use
Cases
17
Q: Users in our environment can see Frameworks, but within modules,
they can’t see tables in our data warehouse. Are there other
configuration/settings that we’re missing? For example, if users go to
Microsoft Access, can they see the tables within the warehouse?
A: When you create the Cognos data source connection be sure you load the
metadata for the schema. This is a button in the data source connection
properties.
Q: How many Cognos Framework Manager packages can be combined in
a data module?
A: There is no limit, but it really is a best practice design issue. Make sure your
data modules are concise and subject specific.

18. Cognos Data Module Architectures & Use
Cases
18
Q: How resource intensive are data modules compared to Framework
Manager? Does Cognos suggest additional resources if using DMs vs.
FM?
A: Since data modules can integrate many different types of data sources – DB
Connections, FM packages, data set and uploaded Excel files it will depend on
the content of the DMs. A DM with only data sets will generally perform better
but you may need to keep an eye on the memory use of the data sets in
Cognos.
Q: When combining a Cognos Framework Manager package with a data
module, does the FM package need to be built in DQM or can it be CQM?
A: The FM model needs to be in DQM.

19. Cognos Data Module Architectures & Use
Cases
19
Q: If I get an error when I try to bring an ODS package into the Cognos
data module will I need help from IT? It says connection information is
missing from data source (ODS). I do not have administrative access.
A: Like running a report against a package, if the data source connection of the
package contains incorrect connection settings, you will need access to that
connection. Try calling IT to fix the package connection.
Q: If the Cognos Framework Manager package can be either CQM or DQM,
are there any advantages or disadvantages between the two?
A: DQM is really the better of the two modes. It is the newest mode and uses a
64BIT java engine vs. the 32bit CQM engine. Most current and future Cognos
Analytics 11x features will require DQM connections.

20. Cognos Data Module Architectures & Use
Cases
20
Q: If I create a hybrid Cognos data module with query subjects that have
object-based security, will that security be preserved?
A: A data module that brings in Framework Manager package objects will
respect the security model of the FM package.
Q: In Cognos 11.1.7 can I copy query objects from reports to a data set?
A: The 11.1.7 release uses the query tools from the report studio tool set. But
we do not believe there is an easy was to import those query objects from
reports to the new 11.1.7 data set editor.
Q: How can I get the presentation for this webinar?
A: Access the deck and the recording at:
https://senturus.com/resources/cognos-data-module-architectures-use-cases/

21. Cognos Data Module Architectures & Use
Cases
21
Q: With the data set library, how do I save different Cognos data sets for
different departments since the data set is saved under the same name?
The security is based on department at my organization.
A: You can use Team Content folder security to create data sets for departments
in different folders. Then the folders are secured for each department. Beyond
data sets, you can have one master data set that is in a data module that
contains security based on Cognos security groups. Then the data module is
the one that is published and then users can link to that data module.
Q: Will the architecture model work in Cognos 11.0.13?
A: Possibly, but there are so many more data module features added through
the 11.1.7 release. We recommend not using that release.

22. Cognos Data Module Architectures & Use
Cases
22
Q: Would you recommend using data modules in Cognos 11.0.11?
A: We recommend waiting to upgrade to the latest release because of the many
improvements to data modules.
Q: How much RAM is used when using Cognos data sets?
A: Depends on the size of the data set. You can adjust how much memory
Cognos devotes to data sets in the advanced settings section of the admin
console. Initially it is set to 4GB.
Q: How are Cognos data modules validated?
A: They are automatically validated in the tool.

23. Cognos Data Module Architectures & Use
Cases
23
Q: To improve the performance of data modules, we’ve been creating data
sets with data modules and then bring it back to data module. Although this
process works, we have been facing issues when trying to combine
package. What are the shortcomings when using packages in data modules?
A: 11.1.7 has an improved data set editor. The full query painter tools in Report
Studio are available in the data set editor. You no longer need to create data
modules to create data sets. Using packages in data modules can become
confusing since you don’t really see the tables on the relationship diagram editor,
and this is by design because of the potential of seeing too many tables. We like to
only expose the tables we need from packages in DMs via views. We’ll analyze
the requirements and if possible, create a data set from that package that is more
subject focused and smaller than the full table in the package.

24. Cognos Data Module Architectures & Use
Cases
24
Q: How do Cognos datasets perform against cloud?
A: When you join a data set to a cloud table, Cognos will bring the data from the
cloud table and join it to the dataset at the Cognos server.
Q: Is there possible versioning on Cognos data modeling?
A: There is no native versioning so you will need to make copies of a data module.
However, Motio has versioning capabilities.
Q: In Cognos Framework Manager, can we do complex joins with SQL
statements? Can we do those complex joins in Cognos data modules as
well? Or are they limited to simple joins?
A: The later releases of data modules allow for complex joins. We recommend you
start your data module journey with the latest release of Cognos 11.1.7.

25. Cognos Data Module Architectures & Use
Cases
25
Q: Can we include several packages in Cognos data modules and then in
report editor join queries from various packages in the data modules?
A: Technically yes, but it will look messy to report writers. We advise exposing
what you need then hide the underlying packages in a data module.
Q: How can we make a translation layer in Cognos data modules for reusing
translations for role playing dimensions?
A: For role playing dimensions, bring in the physical dimension table. Make table
view copies of the table then hide the base physical table. Do this in a folder, it
acts like a physical namespace layer.

26. Cognos Data Module Architectures & Use
Cases
26
Q: When is the auto refresh capability arriving in Cognos? For example, we’d
like to use a flat file loaded from a drive. Every time the file is updated, we
need to reupload the file.
A: Great idea, but we’re not sure when that feature will be arriving. It might be
possible to do this via the SDK.
Q: Does IBM want users to move off Framework Manager and instead use
data modules?
A: For new modeling tasks IBM would like you to start with data modules. There
are so many Framework Manager models in use that we don’t advise doing a
complete 1 for 1 migration of an FM model to a DM. It’s better to just find what
parts of that model needs re-engineering and focus on those.

27. Cognos Data Module Architectures & Use
Cases
27
Q: Where is the data stored from data sets in Cognos?
A: They are stored on the Cognos server in a parquet file format.
Q: What are advantages and disadvantages to storing Cognos datasets in a
content store database vs. external files?
A: Initially they are stored in the content store, but we recommend storing it on the
file system because as your user base uses this feature, the content store is going
to get too large. With a file system you can devote specific storage locations that
could be optimized for retrieval.
Q: Does report execution mode changing to 64-bit help in Cognos datasets
and data modules or in general?
A: Yes.

28. The authority in
Business Intelligence
28
Exclusively focused on BI,
Senturus is unrivaled in its
expertise across the BI stack.

29. Decisions and actions
Business needs
Bridging the gap
29
Analysis-ready data

30. Full spectrum BI services
•Dashboards, reporting and visualizations
•Data preparation and modern data warehousing
•Hybrid BI environments (migrations, security, etc.)
•Software to enable bimodal BI and platform migrations
•BI support retainer (expertise on demand)
•Training and mentoring
30

31. A long, strong history of success
• 20+ years
• 1600+ clients
• 3000+ projects
31

32. Expand your
knowledge
32
Find more resources
on the Senturus website:
senturus.com/senturus-resources

33. Complete BI training
33
Instructor-led online courses Self-paced learning
Mentoring
Tailored group sessions

34. Additional resources
34
Insider viewpoints
Technical tips
Unbiased product reviews
Product demos Upcoming events
More on this subject

35. © 2020 by Senturus, Inc. This presentation may not be reused or distributed without the written consent of Senturus, Inc.
www.senturus.com 888 601 6010 info@senturus.com