Sample project overview

The Sample project is included in Insight so that a new user can gain some knowledge and later (if desired) apply it for training purposes. Going through the dashboards, you can gradually:

Understand the basics of an Insight project.
See all the project details.
Modify and adjust the data for practice.

The Sample project uses a database based on a fictitious company named "Adventure Works," created by Microsoft, Inc. As noted by Microsoft, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, places, or events is intended or should be inferred.

For more information about the fictitious AdventureWorks database, see the Microsoft website.

The Sample project contains the following preloaded Insight objects (documents) which can be viewed in Studio:

Records

The Sample project is intended primarily for demonstration purposes, to help you learn how to use Insight to create analytical dashboards based on information about Adventure Works sales and goods.

The Sample project has several pre-configured records: Order, Order Details, Product Inventory, and Product Photo.

Important In Insight, a record is an ETL (Extract, Transform, Load) model that defines how the data is extracted, transferred, or loaded.

Record	Source for the record	Description
Order	dbo.SalesOrderHeader(Sample AW) joined with other tables: dbo.Customer(Sample AW) dbo.DeliveryShippingHeaderTable(Sample AW) dbo.SalesTerritory(Sample AW) dbo.vSalesPerson(Sample AW)	Contains the data required for processing metrics and processes. Verify that the Data DB has the latest data, because this record has an "Overwrite" type of storage. To achieve this, the record is configured for regular updates and is included in the execution plan.
Order Details	dbo.SalesOrderDetail(Sample AW) joined with other tables: dbo.Product(Sample AW) dbo.ProductSubcategory(Sample AW) dbo.ProductCategory(Sample AW) dbo.SalesOrderHeader(Sample AW) dbo.SalesTerritory(Sample AW) dbo.vSalesPerson(Sample AW) dbo.SpecialOffer(Sample AW)	Contains all details for each order and has an "Overwrite" type of storage. All the used fields are supposed to remain intact after they are written initially in AdventureWorks and hence no special logic is required (Overwrite fields and Time filter configurations). To load details to the record form component, the Sales Order Detail ID field is marked as the key field.
Product Inventory	dbo.Product(Sample AW) joined with other tables: dbo.ProductInventory(Sample AW) dbo.ProductModel(Sample AW) dbo.ProductDescriptionCulture(Sample AW) dbo.ProductDescritpion(Sample AW) dbo,ProductProductPhoto (Sample AW) dbo.ProductPhoto(Sample AW) dbo.ProductSubcategory(Sample AW) dbo.ProductCategory(Sample AW)	Contains information about products and their availability in stock. This record is based on relatively small tables and the data can be retrieved from AdventureWorks with no significant effort. For this reason, this record has an "On-demand" type of storage and it contains no Date/Time field because grouping and filtering by time make no practical sense.
Product Photo	dbo.ProductProductPhoto(Sample AW) joined with the table: dbo.ProductPhoto(Sample AW)	Contains full-sized pictures of products. The ProductID field has an Overwrite field enabled and with the following time filter: <FromDate> <=ModifiedDateANDModifiedDate <<ToDate>>.

Process

Virtually all business activities do not happen by themselves but rather, in connection with some process. The Sample project has one process.

Process	Description
Order to Cash	Shows a probable life cycle of an order placed in the Adventure Works company.

Metrics

Metrics contain calculation and aggregation definitions for a particular KPI (Key Performance Indicator). A metric is a number that shows a particular aspect of operations for the company.

Metric	Description
Marketing	Contains all metrics related to marketing promotions. The Order Received field stands for the time field in these metrics. As a result, the order is taken into account immediately after it is received. Includes the following metrics: Discount Value Order Count with Discount Revenue from Marketing Promotion
Order Pool Completed	Contains all metrics that calculate the total pool of orders and are based on completed orders. .
Order Details Pool	Contains all metrics related to order details. The Order Received field stands for the time field in these metrics, that means the order is taken into account immediately after it has been received. The metrics within one year are calculated with an accuracy of one hour and with an accuracy of one day after one year. For better productivity, an MPAT (Metric Pre-Aggregated Table) is created for this metric on the Overview Subview. Includes the following metrics: Count Orders Sales Revenue Shipping Cost
Order On Hold	Calculates the number of orders at the
Profit	Contains metrics that calculate how effective and profitable the business cycle is. Includes the following metrics: List Price Profit Profit Profit Margin
Stock Levels	Contains metrics related to the number of goods in stock. Includes the following metrics: Quantity Safety Stock Level
Percent of Safety Stock Levels	Calculates the percentage of goods required to attain a certain cycle service level.
Turnaround Time	Calculates the time interval between the time when the order is received and shipped.

Execution plan

The data for each record changes over time and must be refreshed periodically. Execution plans are scheduled to keep the data current.

Execution plan	Description
Daily plan	Used for daily updates for the data that is changed infrequently.
Hourly plan	Used for loading current data.
Initialization plan	Used for loading historic data.
Post Aggregate (Monthly)	Used for aggregating the historic data to reduce the size of the Data database. All data in the Order Detail Pool that is older than one year is aggregated to days.

View