Tag: sales history
Part I: Reporting, Business Intelligence, Data Mining, Analytics: Actionable Tasks!
Software vendors use so many big words and confuse customers. Our customers have often asked us to clarify – so here I go. The definitions in this article are based on research of these terms, and the collective opinion of many of our customers and prospects. Over numerous conversations with our customers and the discussions of the terminology, the clarifications always go back to the origin of the terms and then move on to change in usage. Hence this article folows that flow. I would love your feedback as it is important to help buyers understand this.
Business Reporting
Business Reporting, as the term suggests presents the data from the database in an easy to read format. This originated when business users were frustrated that all the data was locked up in databases. There was a lot of data, but no one could get access to it without calling on IT folks. Hence Business Reporting was born.
Business Intelligence
This is a fancy name for business reporting. Business intelligence (BI) is a broad category of technologies that allows for gathering, storing, accessing and analyzing data to help business users make better decisions. In a 1958 article, IBM researcher Hans Peter Luhn used the term business intelligence. He defined intelligence as: “the ability to apprehend the interrelationships of presented facts in such a way as to guide action towards a desired goal.”
In 1989 Howard Dresner (later a Gartner Group analyst) proposed Business Intelligence as an umbrella term to describe “concepts and methods to improve business decision-making by using fact-based support systems.” Then in the late 1990s the usage became widespread (Remember the Bubble!). Then. everything with any data reporting was called Business Intelligence. So today, Business Intelligence is a glorified term for “Business Reporting”.
Data mining
Simply put, Data mining is hitting the data with all mathematical methods available to a mathematician! The data source can be almost anything – news papers articles, financial reports, sales data, medical data, … . This means that the data can have structure or can be un-structured. And the mathematical methods that can be applied can include neural networks, genetic algorithms, statistics on steroid and anything else they can think of.
One may ask – why are they doing this? What are they mining? Well, the simple answer is that they are mining the data looking for patterns; any patterns that can reveal relationships. So the methods used are varied and the kinds of data that are mined can come from a myriad of sources.
The results of data mining are lots of data! In fact – the result of Business Reporting and BI has been data overload. Now that’s the bad news. In a world of information overload, the last thing that we need is more data. We have less time today than we have ever had before. Business users do not need more data. They need quick conclusions on what the data is saying, converted into actionable tasks. Simply put – “Please tell me what to do”.
… More on the discussion of analytics to action in the next blog.
Stairway to (Product) Complexity (a.k.a. Why Do I have SO Much Stuff!!!)
In the last post I introduced two ideas about the sales history of any product. First, the number of unique configurations, or build combinations, depends on which features are included in its description. Second, the number of unique combinations drops whenever a feature is removed. A natural question to ask at this point is: Which feature, if it were removed, would lead to the greatest decrease in the number of unique configurations?
This is an easy question to answer, if we have a way of counting the number of unique configurations in any input set of configurations. This is really just a matter of sorting, so suppose we have such a counting algorithm. We try removing the features, one at a time. In each case we apply our counting algorithm to get a score. The score is the number of surviving unique configurations. The feature with the lowest score is the winner (like golf).
Now suppose that we permanently remove the winner, and repeat the contest again. This will determine a second winner, which can also be removed. We keep repeating until there are no features left. Now imagine a graph with the number of features removed on the x-axis and the number of surviving unique configurations on the y-axis. This is the stairway to complexity.

The stairway shown above is for a product (commercial stoves) with 23 features. The number of unique configurations starts at 1223 and drops to just 1 as the features are removed. The features are removed by looking for the biggest drop at each step.
Abstract:
Product complexity is driven by large number of options. Companies struggle to determine which feature choices are driving complexity. They typically “randomly cut choices” to streamline and rationalize SKUs. The cost of product complexity is tremendous on engineering. The current PLM systems do not have a method to measure this and provide intelligent feedback to engineers on how to standardize platforms to reduce engineering and maintenance costs. This article clearly details the metrics around product complexity and how to solve this issue.
The Number of Choice Combinations Depend…
The number of choice combinations depend on which product features are included. The build combinations is the product mix or the marketing mix.
Let’s consider the sales history of our product. There are two very important numbers: the number of units sold and the number of unique configurations. The number of units is well defined, but the number of unique configurations is ambiguous. The ambiguity comes from the fact that there will be more unique configurations if we use more features, especially soft features, to describe our product.
One very special soft feature is a Serial Number, or VIN (Vehicle Identification Number). The whole purpose of the Serial Number is to make each instance of the product unique. So if we look at our sales history and include Serial Number, we will see that the number of unique configurations is exactly the same as the number of units of the product (instances).
If we want to begin to understand the demand for our product we have to see which instances are actually the same. That means we have to get rid of the Serial Numbers. When we do, the instances collapse into groups of now unique configurations; that is, unique without Serial Number.
If we are interested in the tangible features of the product, then we may want to take out other soft features as well. Geographic region is important for some purposes, but may be a distraction when we are interested in the physical product. Taking out the geographic region feature will cause another reduction in the number of unique configurations. The red, V8, convertible in Florida will get combined with the red, V8, convertible in New York.
Sometimes we are interested in the variants of our product ignoring color. We know that every real variant is going to come in several colors, but we want to look at the product without the distraction of color. This is sometimes called the “body in white”. So the red, V8, convertible and the green, V8, convertible collapse into the V8, convertible.
The point I am making is that the number of unique configurations depends on which features are included, and this number drops whenever a feature is taken away. Mathematically, this is called “projecting out the feature”.
The number of unique configurations is at most the number of units sold, and at a minimum it is just one. If we take away all of the features, then every unit looks the same, which means just one configuration. There is a path from one extreme to the other that we will introduce next time.
By the way – understanding this is important as product complexity is a key driver of process complexity.
How I want to buy a car
Every five or so years, I shop for a new car. I hate car shopping. The haggling, the long trips to dealerships way outside of town, the hours and hours of waiting, punctuated by furtive whispers to my husband, “Don’t give in! Stick to our budget! But don’t tell them our budget!” and similar. But that’s toward the end of the process. There’s a lot of work leading up to it.
First I hit the Consumer Reports site to research cars. A subscription is just $5.95 a month, but it auto-renews so you have to remember to unsubscribe or it quietly chips away at your wallet forever.
I find the five safest vehicles according to my car type and year. When I say new car, I just mean it’s new to me. I like to benefit from someone else’s new-car depreciation, which is something like 25% the minute you drive off the lot.
Anyway, I get on several different car sites like CarsDirect.com and AutoTrader.com to look for my next set of wheels. First I have to pick make and model, then enter my ZIP Code, then there’s a long list of cars. If I want to, I can see the list from lowest price to highest. The trouble is, I want to compare five different models and several different years. I’ve got to select the same filters over and over for all five and then compare the info. continue reading »
What is sales history, exactly?
We often talk about the sales history of a product, so let’s explain exactly what it means. There is a raw sales history and a collapsed sales history. The sales history, raw or collapsed, is the starting point for all the analytics we will be introducing later.
Raw sales history
A product is a collection of features, where each feature has a set of mutually exclusive options (one of which may be “no,” “none” or “none of the above”). A sales history consists of a record for each unit of the product that has been sold, with a list of the options that were included. Since each record is for a specific unit, there may be a serial number feature. So imagine a table with a row for each unit sold and a column for each feature. The entries in a column are the different option choices for the corresponding feature. Blank cells indicate a “none” choice.

The typical tail graph
In a previous post, I discussed two types of sales history: raw and collapsed. The collapsed sales history can be displayed in a table or spreadsheet, with a special column for volume. If this table is sorted on decreasing volume, then the most popular configurations (popcons) will be at the top. The graph with the volumes displayed in decreasing order (popcons on the left) is called the tail graph
We have drawn tail graphs for cars, computers, washing machines, lighting fixtures, trucks and tractors, and they all look basically the same. The first tail graph shown below is small but typical. It represents 2,884 tractors, with 1,997 unique configurations, or build combinations. On average, there are 1.44 units per unique configuration. The most popular configuration was ordered 23 times. The graph quickly drops to two of a kind and finally one of a kind (our technical terms are “twosies” and “onesies”). Combined, the onesies and twosies account for 2,000 tractors, or 69% of total volume. Rather high, though this number is usually at least 40%.







