Data Models for Flexera Analytics

FlexNet Manager Suite 2022 R1 (On-Premises)
Two separate packages are supplied with FlexNet Manager Suite for use in Flexera Analytics:
  • Flexera Data Models consists of two data models (relational and dimensional) that organize your asset-management data and define how the data relates to each another. The relational model organizes data using measures and attributes but uses a flat structure. The dimensional model organizes data using measures and attributes but uses a hierarchy structure that enables you to drill up and drill down to see how data relates to other functionality. For more information, see the "Flexera Data Models" chapter in the FlexNet Manager Suite Schema Reference PDF file, available through the title page of online help.
  • a model of operational data. This model allows you to report on some data stored in the data warehouse database (suggested name: FNMSDataWarehouse), combined with data from the operational compliance database (suggested name: FNMSCompliance). This makes it a powerful model for custom reporting on operational data.
  • FlexNet Manager Platform Reports and Dashboard contains a model of operational data. This model allows you to report on some data stored in the data warehouse database (suggested name: FNMSDataWarehouse), combined with data from the operational compliance database (suggested name: FNMSCompliance). This makes it a powerful model for custom reporting on operational data.
  • FlexNet Manager Platform Data Warehouse (analysis) contains a dimensional model that allows greater flexibility for increased online analytical processing (OLAP). This data comes from the data warehouse database (suggested name: FNMSDataWarehouse), and some report-time specialized queries that calculate trending data sets and the like.
The models consist of the following elements:
  • FolderBoth models provide folders that conveniently group related material together. In the dimensional model, each folder is called an analysis, including Installation analysis for reports about software inventory within your enterprise; and Consumption analysis for reports about license positions. The operational model provides a more sophisticated folder structure to group related database objects.
  • Fact — In the dimensional model, the first child of each analysis folder is the central fact around which the related data dimensions and measures are organized. For example, the Installation analysis contains the Installation fact; and similarly, the Consumption analysis starts with the Consumption fact. The operational model does not include the fact element.
  • Dimension — In the dimensional model, each dimension gives a related data set that you can use to analyze the central fact. For example, it's obvious that when you report on your Installation fact, you need to analyze in terms of individual software applications; so that there is a Software title dimension available. The operational model includes dimensions from which you can select the operational data for your report.
  • Measure — Each measure contains a specific value derived (in general) from one or more fields in one of the source databases. In the dimensional model, some measures are attached directly to the fact. For example, the Installation fact has an Installed (max qty) measure that you can include in your reports. Measures also relate to other dimensions, but here they are referred to as attributes, and you generally choose from individual values of the attribute, rather than selecting the entire attribute. For example, the Software title dimension expands into a hierarchy of the Publisher, Product, and Application measures; but for creating reports, you generally select one of the publisher's names, and so on.
Figure: Elements in the dimensional data model

Elements in the dimensional model visible in Cognos

The dimensional data model is covered in the following sections.

FlexNet Manager Suite (On-Premises)

2022 R1