---
title: "Hands-on Webinar"
canonical: "https://docs.vaultspeed.com/space/VPD/3011379576/Hands-on%20Webinar"
format: markdown
---
# 1. Set up
## 1.0 Prerequisites
VaultSpeed runs in the cloud. All you need for this session is a laptop with an internet connection and one of the following web browsers:
| **Browser** | **Download Link** |
| --- | --- |
| Google Chrome | [https://www.google.com/intl/en/chrome/](https://www.google.com/intl/en/chrome/) |
| Mozilla Firefox | [https://www.mozilla.org/en-US/firefox/new/](https://www.mozilla.org/en-US/firefox/new/) |
| Opera | [https://www.opera.com/en/download](https://www.opera.com/nl/download) |
> ⚠️ Other web browsers are not supported. VaultSpeed runs best on Google Chrome.
---
# 2. Adding a source
## 2.0 Use Case: Multi-Source & Relationship
For this exercise, we will work as a data vault specialist for a hypothetical company selling street-legal vehicles, more specific cars, motorcycles, and bicycles as shown in the picture. The company sells these **products** to **customers**. We call the relationship between customers and products the purchased relationship.
This use case takes into account that there are **multiple** **sources** and that a **relationship** exists between business elements. It is a typical **Master** **data** case. The problem with Master Data is that they are stored in **multiple** **sources**, appear at **different** **levels** within these sources and can be updated, changed, and replicated from one source (Single-Master System) or multiple sources (Multi-Master).
Our client has to deal with two sources with different levels of data. But the organization understandably wants the **Business Model to be implemented at the same taxonomy level**. The Sales source contains a party taxonomy at the third level. Only the person part of the taxonomy is implemented in the source as this is a B2C company that only sells to individual persons.
The Business Model that is used within the organization is at Level 1 of the Product Taxonomy as indicated in Red. The Sales source is implemented at the Third level in the Taxonomy as indicated in Purple.
The Party taxonomy only exists in source 1 at level 2 of the taxonomy: the person level. The Business Model, however, is at the 3rd level of the taxonomy. So, we need separate the Employee and customer business elements.
The second source is our Products ERP system. It is implemented at the Second level in the Taxonomy as indicated in Purple.
Now the organization wants to report on who bought what product. Therefore, we define the Purchased relationship between the customer and the product.
In the source, there are four many-to-many relationships that appear at level 3 in the taxonomy for Party and Products.
## 2.1 The Resulting Data Vault 2.0 Model
The very definitions of the Data Vault 2.0 standard ensure that the Business Model is represented inside the resulting model in the Raw Data Vault by means of Hubs and Links. Adding a Party element to our Sales source with the purchased relationship does not change anything to the HUB & Link Canvas that represents the Business Model. This is why the **Data Vault 2.0** standard is **built for change**.
The subtypes of the Business Elements in the Product Taxonomy at level 2 for SALES and at Level 3 for PRODUCTS become **Satellites** of the Products Hub.
The subtypes of the Business Elements in the Party Taxonomy at level 2 for SALES become Satellites of the Customers Hub.
Even if the Raw Data Vault is built on the Single Version of the Facts, you do have a Business Taxonomy view implemented in the Data Model at the level of your Hubs & Links.
The Satellites contain descriptive information that changes over time. To keep track, the mapping towards attributes in your Business Model needs to be described in the metadata. Typically, these are designed and managed in an Enterprise Metadata Tool.
The next sections will show you how to add these sources to VaultSpeed while ensuring that your data vault model corresponds to our business model. Keep in mind that to be able to automate your development, there must always be a clear **relationship between your source and target models**. VaultSpeed ensures that this is the case.
The metadata for your sources is read in through the VaultSpeed agent using a database link (JDBC connection) defined within the VaultSpeed agent.
> 📝 Note: The database links themselves can be defined from the Sources start screen or the add source wizard. In this demo, we have created the proper database links for you. So no need to add them.
---
---
# Congratulations 🥳 👏
You have successfully created your Data Vault. Thanks a lot for attending our hands-on session. We hope you had fun using Vaultspeed. If you still have questions, please don’t hesitate to ask one of our team members.
> 📝 FURTHER READING 📖 : If you’re interested in using data vault as the physical model to implement your conceptual and logical business models, you should definitely read:
> 📝
> 📝 - The Elephant in the Fridge by John Giles: [https://www.amazon.com/Elephant-Fridge-Success-Building-Business-Centered-ebook/dp/B07RH9C2JK](https://www.amazon.com/Elephant-Fridge-Success-Building-Business-Centered-ebook/dp/B07RH9C2JK)
> 📝 - [https://vaultspeed.com/whitepaper-accelerate-the-mapping-of-your-business-taxonomy/](https://vaultspeed.com/whitepaper-accelerate-the-mapping-of-your-business-taxonomy/) by Dirk Vermeiren, our CTO
> ℹ️ More information can be found on our [website](http://www.vaultspeed.com/). If you are interested in a deep dive demo: fill in this [demo form](https://vaultspeed.com/book-a-demo/).
> ⚠️ All rights reserved. All content on this page is property of Vaultspeed and may not be reproduced, distributed, transmitted or used beyond the purpose of this hands-on session, without written permission of Vaultspeed. ©