Semantic Modelling - Understanding Semantic Layer - V2 (Autosaved)
Semantic Modelling - Understanding Semantic Layer - V2 (Autosaved)
Modelling:
Understanding Semantic
Layer and Access Layer
2
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).
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.
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
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
1
Business Intelligence Requires Data Integration 18
Product Data
Customer Data
Account Data
Transaction Data
G/L Data
Market Data
External Data
19
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
Agnostic
MicroStrategy
Tableau
Tier 3 Access
Tier 2 Integrated
Tier 1 Acquisition
23
Semantic Layer
25
30
Revenue Opportunity
Assessment
• First step toward increasing revenue
31
Teradata Tax Logical Data Model
• Flexible to include data from other state agencies and third parties
32
Teradata Tax Data Warehouse
33
Teradata Tax Discovery
34
Tax Rapid Analytics for Compliance
and Enforcement
• Applies business rules to known filing patterns
35
Teradata Case Management
Solution Module
• Flexible, modular solution for managing audits and discovery leads
36
Revenue Tracking Module
37
Reporting Module
38
Why Choose Teradata?
39
Conclusion
• Recap of Key Points
• Final Thoughts
40