Sample dataset for Envision - Supply Chain Optimization Software

The sample dataset for Envision












Home » Resources » Here

In order to make it easier to learn and practice Envision, we provide a sample dataset. This dataset is not real data, but we have made significant efforts to make sure it is similar to the data that can be found in a real-world supply chains. All the code snippets provided in the following are expected to work when applied to this dataset.

Dataset overview

The dataset represents the historical data of a small fictitious retailer. The dataset includes multiple tabular files formatted as flat text files.

The fastest way to add those files to your Lokad account is to click the Connect data source button, and then select the sample data at the top of the list. Running the data source automatically copies the files into your account, without the need to go through the download/upload process.

The sample dataset contains the following files:


This dataset includes many interesting pieces of information such as product categories, stock levels, selling and purchasing prices, lead times, etc. This dataset is also representative of the data that can typically be obtained from a company that uses a not-too-ancient ERP.

Using the dataset

You can use the link above to download the ZIP archive that contains all the TSV files. Once you have downloaded the ZIP archive, open the archive and extract the files. Now, go to the Files tab of your Lokad account. Create a folder named /sample – the path /sample is the convention that we follow in the rest of the documentation, and re-upload these files into this newly created folder. Your Lokad account should look like this:

Image

Dataset details

In this section, we document all the different fields in the files contained in the sample dataset.

Lokad_Items.tsv

This file contains the list of products sold by the retailer along with relevant attributes at the product level.

  • Id: the SKU identifier
  • Ref: the identifier of the product
  • Loc: the identifier of the location
  • Name: display name of the product
  • Category: top hierarchical level to organize the products
  • SubCategory: top hierarchical level to organize the products
  • Brand: brand name
  • Supplier: primary supplier from whom the product is purchased
  • StockOnHand: the number of units readily available
  • StockOnOrder: the number of units already ordered from the suppliers but not yet received
  • BackOrder: the number of units already ordered by the clients but not yet shipped
  • BuyPrice: per-unit purchase price, net of tax
  • SellPrice: per-unit selling price, net of tax
  • MOQ: the minimal ordering quantity per product when ordering from the supplier
  • LotMultiplier the lot multiplier constraint when ordering from the supplier
  • Volume: in m3, the volume per unit, typically used to satisfy purchasing constraints

Lokad_Orders.tsv

This file contains the historical sales data disaggregated down to the transaction level as the client identifiers are also provided.

  • Id: a foreign key to the “Id” column in the items file, the SKU identifier
  • Ref: the identifier of the product
  • Loc: the identifier of the location
  • Date: ordering date.
  • Quantity: quantity ordered in units.
  • NetAmount: amount paid for the order line, without taxes.
  • OrderId: the identifier of the client order.
  • Currency: a 3-letter code for the currency.
  • Client: a client identifier, can be used to demo customer loyalty analysis.

Lokad_PurchaseOrders.tsv

This file contains the historical purchase orders data disaggregated down to the transaction level of every shipment.

  • Id: a foreign key to the Id column of the items file.
  • Ref: the identifier of the product
  • Loc: the identifier of the location
  • Date: date when the purchase order was placed.
  • DeliveryDate: date when the goods were delivered, or blank if goods have not been delivered yet.
  • Quantity: ordered quantity in units.
  • Received: received quantity in units.
  • NetAmount: amount paid for the purchase order line, without taxes.
  • Currency: a 3-letter code for the currency.
  • Supplier: identifies the supplier who has received the purchase order.
  • PONumber: identifier of the purchase order.

Lokad_Suppliers.tsv

This file contains the list of suppliers with their respective properties. On purpose, this file is not indexed by an Id column but by a Supplier column.

  • Supplier: the index of the table; acts as a foreign key toward PurchaseOrders.Supplier.
  • MOV: the minimal order volume expressed in USD for the given supplier.
  • ContainerM3: the target size of the container expressed in m3 - cubic meters.

Lokad_BOM.tsv

This file contains the list of bundles with their respective composition. The purpose of this file is to illustrate how Envision can cope with bills of materials.

  • Bundle: a product identifier that identifies the bundle itself.
  • Part: a product identifier that identifiers one element of the bundle.
  • Quantity: the number of units for the part contained in the bundle.