Semantic Data

Modelling:
Understanding Semantic
Layer and Access Layer
 2

Introduction to Data Models

• Data models are abstract representations of how data is structured
and organized in a database.

Types of Data Models:

• Conceptual: High-level, business-oriented view of data.
• Logical: Detailed view without implementation details.
• Physical: Implementation-specific details on how data is stored.
3
 4

Conceptual Data Model

 5

Logical Data Model

 6

Physical Data Model

 7

Teradata Warehouse
Teradata Data Warehouse
8

Architecture
• Data Acquisition Layer: Handles ETL/ELT processes, ensuring
data is extracted, transformed, and loaded into the Teradata
system from various sources.
• Data Storage Layer: Manages the physical and logical storage
of data within the Teradata Database, ensuring organized,
secure, and optimized data management.
• Data Access Layer: Facilitates data retrieval, query execution,
and interaction with the Teradata system through various tools
and interfaces for analysis and reporting.

8
9
 10

Teradata Architecture
Overview
Data Sourcing -> ETL Process -> Data Warehouse -> Semantic Layer -> BI
Consumption
Diagram: Teradata Architecture Overview (Placeholder for Diagram)
The Datawarehouse Architecture
11

Layers
Source Layer
• Data Collected from databases, transactional systems, APIs, and data streams.

Stage Layer
• The stage layer is the place in the IDW where data from the source is landed with little or no transformation.

Transformation Layer
• The transformation layer is the process of moving and organizing data from the structure of the source to the structure in the Core Data Layer (CDL).

Core Data Layer (CDL)

• The core data layer houses all the integrated data and historical data. This layer is modeled from a collection of industry models supplied by Teradata. It is
as close to third normal (relational) form as possible.

Business Alignment Layer

• The business alignment layer is where data is taken out of the CDL (sometimes virtually, sometimes physically) and put into a view or semantic structure
that the business users can easily understand and use for their reports and analytics.

Semantic Layer
• It is how the business understands the data and can access it with their analytical tools. No data should be extracted from this layer except what the
business intelligence group (BI) may need for their tools in processing.

User Access Layer

• The access layer is what the end user will know best. In this architecture, the main BI tool is MicroStrategy, but Tableau and SAS are other tools that can be
used at this layer instead. SAS processing can be done within the IDW, so no data should be moved into a separate SAS environment
 12

Introduction to Semantic Layer

• Definition: An abstraction layer that translates complex database
schemas into business terms.
Purpose:
• Simplify data access for business users
• Ensure consistency in data interpretation
• Facilitate faster report and dashboard creation.
Semantic Layer Architecture in 13

Teradata
• A semantic layer maps business data into familiar business terms to
offer a unified, consolidated view of data across the organization and
meet the growing analytics needs of an enterprise.
Components:
• De-normalized data (Business Specific)
• Dimensional Modelling (Entities, Attributes, Relationships)
• Hierarchies
• Calculated Measures/Metrics
• Aggregations/Summarized
 14

Challenges:
1. Different analytics tool preferences
2. Slow data integration leading to siloed solutions
3. Inconsistent BI reports across different business units
4. Can’t access the data they need
5. Data integrity issues limit usability
6. Can’t respond to business needs fast enough
 15

Challenges in Oracle BIEE

• We cannot directly connect OBIEE’s Semantic Layer (RPD) to other BI
tools like Power BI. Each tool typically requires its own semantic layer.
• Vender lock in and higher Cost.
• Siloed solutions. Subject Areas confined and not integrated with each
other
• Limited number of questions asked and answered.
• Too many Adhoc reports request.
Global Benchmark: Teradata vs 16

Oracle
Enterprise Information Management 17

Data Modeling
Not just a collection ...but also their
of subjects... relationships
Single, Integrated
System
Party Account Product Activity
Party Product
Account Activity

Don’t model subjects Model your entire

individually! business!

1
Business Intelligence Requires Data Integration 18

Product Data

Customer Data
Account Data
Transaction Data
G/L Data
Market Data
External Data
 19

Benefits of a semantic layer include:

 Democratization(Access to everyone) of data analytics and machine
learning (ML)
 Single source of truth
 Seamless model development and sharing
 Improved query performance and reduced computing costs
 Reduced data cleaning effort
 Better security and governance
Benefits of Semantic Layer –
20

BI/Developer Perspective
 Efficient table joins can be encouraged inside the SDM views.
 Views are low maintenance objects.
 Views do not consume database space.
 Join indexes (JIs) and aggregate join indexes (AJIs) can be created
based on the access paths embedded in the SDMs.
 PDM is not compromised with new application
requirements.
 Protection of code assets.
 21

Semantic Data Modeling

 Semantic data modeling is a logical data modeling technique; the
semantic view of information does not necessarily need to be
physicalized in the database.
 There may be a different semantic data model for each
department/applications that uses the data warehouse.
 Dimensional modeling is a common technique for constructing the
semantic data model for an analytic application, but is not the only
viable approach.
Semantic Models Should be BI Tool 22

Agnostic

MicroStrategy

Teradata OLAP Connector

Tableau

Tier 3 Access

Tier 2 Integrated

Tier 1 Acquisition
 23

Semantic Layer Characteristics

• User-Friendly: Simplifies data access for non-technical users.
• Consistency: Standardizes calculations and business logic.
• Agility: Faster development of reports and dashboards.
• Governance: Ensures controlled and accurate data usage.
• Unified Data: Semantic models can combine data from multiple sources.
Enhance DW with own/new data sources.
Semantic Layer Usage - BI 24

Semantic Layer
 25

Conclusion and Q&A

Introduction

• Importance of Tax Compliance

• Challenges Faced by Tax Agencies
• Overview of Teradata Tax Compliance Solution
• More than $2.2 billion identified and collected in revenue
• Need for a cohesive strategy combining people, processes,
technology, and data

30
Revenue Opportunity
Assessment
• First step toward increasing revenue

• Accurate estimate of recoverable revenue by tax type

• Timeline for revenue recovery

• Documented business case for technology investments

31
Teradata Tax Logical Data Model

• Blueprint for designing a comprehensive state tax data warehouse

• Organizes core requirements for revenue and tax administration

• Ensures resources are optimized

• Flexible to include data from other state agencies and third parties

32
Teradata Tax Data Warehouse

• Incorporates best-of-breed data warehouse techniques

• Optimizes discovery programs, decision support, analytical

applications, and business intelligence

• Supports end-to-end tax compliance solution

• Realizes quick return on investment (ROI)

33
Teradata Tax Discovery

• Identifies non-filing and under-reporting of taxes

• Includes data warehouse hardware and software, matching tools,

and optional case management module

• Enables agency self-sufficiency for discovery work

34
Tax Rapid Analytics for Compliance
and Enforcement
• Applies business rules to known filing patterns

• Detects patterns vs. peer groups to uncover anomalies and new

fraud schemes

• Develops predictive models for unknown fraud relationships

• Discovers entity relationships through link analysis

35
Teradata Case Management
Solution Module
• Flexible, modular solution for managing audits and discovery leads

• Web-based application for automated processes

• Enhances productivity and reduces protests and appeals

36
Revenue Tracking Module

• Tracks revenues identified through Lead Generation Module

• Measures productivity and documents ROI

• Tracks amounts assessed, outstanding, and collected

• Identifies results by tax type, period, year, and discovery program

37
Reporting Module

• Creates impactful reports from data warehouse information

• Provides easy access to structured and ad-hoc reports

• Helps turn business insights into effective decisions

38
Why Choose Teradata?

• Recognized industry leader in data analytics solutions

• Unparalleled blend of technology, insight, and innovation

• Comprehensive support for compliance and revenue programs

39
Conclusion
• Recap of Key Points

• Final Thoughts

40