Warehouse Analytics : A Cheat Sheet Design approach

Note: As a standard practice, I will include a plagarism detection link in all the articles on my blog site. You can use the online tool below to evaluate any article published on the web for plagarized content. All you have to do is to paste the url of the article there and it will go through every sentence in the article and flag any plagarism. I believe as a follower of “writer’s integrity” I should include this tool in all my articles:



Your warehouses already generate tons of data

With all the hype around smart warehouses (most of that hype is well deserved), you may develop a notion that in order to gain the full advantage of advanced analytics in your warehouse operations, and have maybe a solution that allows you to perform an end to end analytics on your waregouse operations,  you need to wait till your warehouse is fully automated and/or smart. Fortunately, that is not the case. There is a long list of analytical approaches that you can leverage with your current ecosystem of factory information systems. We will review some of those approaches in the post.

Warehouse information systems landscape

The illustration below shows the most common warehouse information systems landscape and how these systems generally interact with each other.

Note that WMS is usually core to the warehouse systems landscape shown above and all other systems interact with it. The integration of warehouse specific systems like LPS, WSS, WPM and YMS is generally much tighter vs that between WMS and ERP systems.

The Process view of systems

In order to understand what type of Analytics can be leveraged within a warehouse and how, we first need to understand which aspects of a warehouse process interfaces with which system. Below is an illustration that maps the process to systems that the process interfaces (I am assuming that the readers are familiar with warehouse processes).


The Information view of Systems

The next piece of information that we need to know is what type of information/data is generated/captured during that particular interface. So we will now add another layer into our diagram that illustrates the details of information generated. The type of information/data generated will then help us determine the analytical approaches we can leverage.


Adding the Analytics view

Now that we have the insights on what type of data is being generated by each system, we will now determine what type of useful insights can be drawn from the data and what type of analytical approach can be leveraged to generate that insight.


Based on why you are trying to build this “structure”, other elements and relationships can be added to the above view.

Views expressed are my own.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s