On-Demand Webinar
TRUE OR FALSE? CLEARING MISCONCEPTIONS ABOUT WMS, WES, AND WCS
Watch the webinar
Read the full webinar transcript
Speaker: Claes Jönsson, Automation Expert, Consafe Logistics
Hi everyone and welcome to our webinar. My name is Claes Jönsson. I'm an automation expert here at Consafe Logistics and I will be your host for this session. Today, our discussion will be about how to integrate automation into warehouse operations. We're going to review the methods and clear up some misconceptions about the key software involved in this process. And as always, in our webinars, if you have questions, we hope you will just add them to the Q&A as a part of this Zoom stream and we will answer them live as best as we can.
But now let's go right into our topics. So we talk about misconceptions. So the first obvious question might be, are there misconceptions and why do we feel the need to talk about this? After all, automation integration is not new. It's been around for some time. So what is the confusion? Well, first it has to do with the evolution of warehousing. In the past, warehouse management solutions, including automation, was mostly about moving full pallets using high base and perhaps some conveyors.
AGVs integration as a topic was not always standardized far from it, and most solutions were built for large warehouses, adapted per sites to meet specific needs, often very separated from manual flows. Functionality could be basic or straightforward. It could also be complex to meet perhaps throughput demands, but in general, it was not so flexible. Today it's a different story and a different scene. There are literally hundreds if not thousands of different suppliers of automation. Integration comes in more and more flavors and software is more than ever a crucial factor for success. If we look at the market, warehouse automation grows by more than 10% per year.
There are different sources for this, but it's more or less always, the same figures that fi figure there. All in all, the warehouse market is expected to double in size by 2029. Still most warehouses, if not all, have manual work in different percentages. That means automated and manual processes must be harmonized to give the full efficiency in the warehouse. So when we talk about integration, it's not just about integration of the automation solutions, but it's also integration on the topic of the manual and automated processes into one whole warehouse operation instead of operating isolated islands, so to speak.
So this might call for a different integration strategy between the WMS and the automation solutions than was existing before. And that's what we're gonna talk about here today as well. So to get this rolling and started, we will like to first ask you a poll question and we would like to see if you can state which statement is true here, outta these four statements and, I will read them out to you. The first one is, WES is the same as WCS, warehouse execution system is the same as warehouse control system.
The second WMS management system, orchestrates warehouse automation. And number three, warehouse control system is part of the business logic layer. And number four is none of the above. We will explain this more in detail further in this webinar, but just to see a little bit where you are here now we do get the answers popping in here and it seems, to be a little bit spread out and mixed between the different parties here.
Okay, so we have the final poll result here. So none of the above, which is, to our view also the right one that none of these are true in its entirety. We do know that some claim WES to be the same as WCS. We will try to explain a little bit why we don't think this is the case. WMS orchestrates warehouse automation, yes, to some extent, but not in the level of detail that is required to make efficient operations. And number three here, WCS is part of the business logic layer. That's one of the areas where we also hope to give some clarity during this webinar.
So our view is that the fourth one is true, none of the above, and we will try now to explain why and to do that, first we will talk a little bit about the different software layers and, and the labels that are put to them. If you look at the market, and you browse some web page and you talk to suppliers and you talk to perhaps logistics consultants, you get a lot of different statements about integration of warehouse automation and into software and warehouses.
And some of them you can see on this slide, for example, as we had in the former former, poll question, WES is the same as WCS, it's just different wording, it's different geographical areas, et cetera. We also see a lot of times different statements regarding who is really orchestrating the automation. Is it warehouse management? Is it warehouse execution? Is it warehouse control system? Well, all of them can't be true at the same time. It's perhaps obvious, but how should we look at it?
So this is our ambition with this webinar to, give you a clear explanation how we see it, and also in our opinion, how to best run your warehouse from the holistic view combining manual and automated operations. So let's start with a little bit more explanation here on the different software layers and see which software does what. And we start from the high level here. Warehousing is all about following different chain of activities for the different software layers to how they interact.
The point is to use the high level information and pass it down in the chain to in the end, low level instructions that actually gets the robots or whatever type of automation you have moving. So the first part is the warehouse management system, which is the overall order planner and the high level resource supervisor. Then in turn is the warehouse execution system. This software acts as a coordination layer between the manual and automated parts, but also contains optimization parts for how to optimize, optimize both the manual and the automated parts.
So it ensures in, in short to that the overall plans done by WMS will be executed in the best way. And here we are at the intersection between the actual connection to the equipment. So operators will do their picking activities in some clients, some screens. But what about the automation? This is where the warehouse control system comes into play. So it translates the business transactional information coming from the warehouse execution system into machine specific commands. And it has also the role of acting as, yeah, flow control engine to make sure that there are no bottleneck and that load balancing done is done in the best way.
So this is the high level explanation, but we will go a little bit more in detail here now and explain exactly what goes on in the different layers. So the obvious question here is how does the information from the overall planning reach the machine and what happens in the meantime? So this slide here gives a little bit, deeper, explanation of this. So we, it all starts with ERP having the first initial route planning, et cetera.
So to the left here you see information passed between the systems and to the right of the abbreviations, you will see the main tasks associated with that software layer. So ERP does the overall planning and sends orders to the warehouse management system. The warehouse management system in turn will split up the orders according to where it should be picked or handled in the warehouse. It'll make box calculation, for what should be picked, and and how it should be consolidated. The warehouse execution system then takes over and has the task of the graphic graphical user interface for the operators.
It also allocates the goods and thus the high level optimization to make sure that the manual and automated parts run together in a good way. And this also marks the end of the business logic layer. This is where all your rules about what you can pick and cannot pick together and things like that. We will come back to that is, is handled in the warehouse control system layer and below. It's on the machine control layer.
So here we have the flow control and the low level optimization of what is the best way to operate the machinery. So here the task or assignments to work with the picking tasks, the movement tasks, they are broken down into smaller beats and pieces and conveyed to watch the automation. So the last layers here, the material flow controller and the programmable logic controller is all about the fine level of detail of moving the actual robots, but it's all orchestrated and run by WES and WCS in different, aspects and different layers, high level and low level.
And of course there are also movement or, information, going back from these, different layers up. But this is the main flow of how to send information between the systems. So with this explained, we hope, let's move on to clear some of the misconceptions that exist. So to do that we will check three statements, and the first one being the following, this is what we sometimes hear. Automation integration with WMS is only possible with black box integration and to some WMS is this is true actually.
If there is not a possibility to, control automation in a more detailed way, and perhaps to understand this, we might explain also what black box integration is. This is the situation when the warehouse management system WMS connects to the automation solution via the automation suppliers own, warehouse execution software. So business logic for the automation is kept within the automation vendor and the automation solution in that software layer. And well, how do we look at that? Well, this is what how we, what we see on this graph.
The automated processes are separated from the manual process of the warehouse and the term black comes from the notion that, WMS does not see into the automations business logic and does not perhaps always also see into this the stock contents. It's all kept within the domain of the automation vendor solution. This is an integration method, which has been around now for quite some years and is elaborating on the software from the automation vendors. So, it's well established, but it's not the only possible solution. A best of breed WMS solution with an embedded warehouse execution system part can also steer the business logic out of one system for both these worlds.
The manual and the automated part, and this is what we call the white box integration. And also what we see in this slide here. So the term white here refers to the transparency between the manual and automated processes and that there is full visibility into the stock and where all the goods is located in the warehouse. We have implemented multiple products with this set setup and thus the customer will use our WMS with an embedded WES to also connect to the actual automation.
So this is one misconception that we often hear that we hope we have cleared out, but it comes a natural question as a result of this. Okay, fine. We can integrate also the automation in the white box concept, but what about the results? What about the efficiency? So that's the next statement we want to address about efficiency. This is also very common to here that when it comes to efficiency, you can only achieve efficiency in the automation via black box integration.
And this might seem reasonable, since well, automation investments are after all often quite, of a huge extent talking about lots of money here and it'll greatly impact also the warehouse operations. So it's perhaps natural to think that these solutions should also dictate how you look at efficiency and also then be operated by the automation vendors software. However, there are cases we think where this might not always lead to the most optimal operations. And why is that? Well, as we stated before here, most if not all warehouses have a mix of manual and automated processes.
So it's no good to have efficiency just in one area if the other area or areas are lagging behind. So if you keep them separated, you can end up in situations where you need to work with what we call information islands. And we will show a little bit a graph here showcasing that situation. If you keep the business logic separated on the automation level as this integration, which is then referring to the black box integration we talked about before, where, warehouse execution system solutions and warehouse control system solutions from the automation vendor, you will actually need to deal with more than one business logic.
There will be one for the manual processes and there will be one, at least one for the automation. If there are multiple vendors with different systems, you will also multiply the number of business logics that you have to work with. So here it can be difficult to get the full overview of your business flows and also to optimize them as a whole. Each of the individual technical solutions might do its job and perform according to agreed values or throughput figures. But still, you might not get the full efficiency in the complete warehouse solution. And why is that?
Well, as we said, it might be hard to optimize all of the different processes and areas together and with this set there might be information islands that you have to be sure that you can control and get them to work together. So we have seen this in practice and we think that in these cases a black box setup might not be the best solution for efficiency.
So this is yet another example of a common misconception that we hear, but now we have mentioned the possible problems or what could be the downside of the black box, integration. But is there an alternative then? Yeah, we already mentioned the white box and we will try to explain a little bit how that can help you to become more efficient. So in this case, and which is our suggestion then is to use one business logic for the entire warehouse operations.
So some practical examples might be that you could have rules depending on your business for picking tobacco, which are certain rules are associated to that. Some of our customers have, black and stainless steel that can't be picked together. There could be rules for specific labels printed and certain other business requirements for certain products or certain customers. And these rules will apply across all your warehouse, both the manual and automated picking.
So in the case of a black box solution, as you can see to the left here, the automation vendor need to build in these rules into their system and it's also needs to be in the manual area. So also the WMS and WES vendor need to build that. And if you have multiple automation solutions, all the vendors where you pick these products need to build that logic.
So this will add to the overall complexity of the, of the operations. So with a white box solution, as you see to the right, you can incorporate these rules into one integrated warehouse execution solution without the need for all the different vendors to embed them into their systems. So in this case, you will have one integrated warehouse execution system solution connecting the manual and automated process into, you can call it one, let's say one brain or one super brain that handles everything in this case.
But now we talked a lot about integration methods. So let's see and try to connect that also to another poll question, to also get you, also a little bit, working here in an interactive stance. So last time we looked for a true statement. This time we were looking for the full statements from the list. So the first one is black box integration creates separate business logic from manual and automated processes. And mind you now we are looking for the full statement here.
The second one, the term white in the naming of white box integration refers to the transparency between the manual and automated business logic. And the third one, keeping the warehouse control system WCS in the business logic layer being responsible for goods allocation and optimization gives you the highest throughput. So we will give you some time here to reflect on this, and also put your answers in.
So we have a total of 69% of you saying that keeping the warehouse control system in the business logic layer being responsible goods allocation optimization gives you the highest throughput that is the full statement. And that's also our point in what we say here, that there might be situations where this is fine, but from an overall perspective, we think that there are cases when this is not the most optimal setup. The black box integration will create separate business logic for manual and automated processes. And the term white does refer to transparency between manual and automated business logics.
So those statements were true is the third one that we see there is, at least not always the the right, the right way to go. Okay, so then let's go to the third statement here, which we will try to, clear as a misconception. We often hear this as well. When it comes to maintenance and upgrades, it doesn't matter which setup you have, if it's black box or white box, it, it's all the same. It's just the question of who, who we are paying for that service.
Well if you look at it from a first glance, it might seem easier to go for a black box integration or interface where the automation vendor handles all the automation related support. It might also be, from the point of view where, you look at the contracting, which might be easier to have one party to do that. Let's see, we have a question here. Certainly, that would mean that, the pallet control, the tote control, whatever it is, the full logic of allocation of goods is handled by the same software, the same various execution system, solution that's also handling the manual parts.
And from our customer range, we have quite a big portfolio of customers using this. So, if you look at that from, an example point of view, well there are, many customers looking into this and sometimes they use also our warehouse control system and sometimes not, but it gives them the benefits that they can use the same interface all through, the warehouse. And you can also, yeah, when it comes to upgrades, et cetera, it's all done by the same. So, if you're looking at specific customer cases, I think we have that in all the areas, more or less from, our main areas, food and beverage. Yeah, let's see.
We have also wholesalers. We have more or less all the, all the business branches represented in this area. And it goes from large customers to small customers, but the main focus here is large customers with multi-site, they have a more, more use of this. Okay, so when you look at this, there are three things to consider. We think when it comes to, how to work with maintenance and support, the first one being system knowledge.
With the black box integration, you have to learn the external software suppliers individual language, and you have to also be an expert in their systems. With the white box integration, you will learn one system and you only need to learn that system. You still need to have the hardware support, but it's on a machine level rather than software and logic level, and it's often quite easy to, to separate those from each other.
The second aspect would be the long-term operations. An automation solution will stay with you for 15, 20, maybe 25 years, even after the guaranteed period for support is over. There's going to be a need for new upgrades, new functionality and changes because we know your business will change. And this should of course be as easy and cost effective as possible. But if all parties need to update their business logic, their software, when you need to do a change, the process will be more complex, more cumbersome, and thus more costly for you.
So especially through if you want to expand your solution with additional, offerings in the automation market from different suppliers, if the logic is one integrated solution in the white box case, it'll be easier to handle this as you will only need to talk to one party. And you can also handle a core solution with upgrades to multiple sites at the same time. And third and the last one, the multi-site aspect is also as important.
We think if you want to unify your ways of working across multiple sites with a white box integration, you can have different technical solutions, but the same control systems in all warehouses and which adds more flexibility to your business. So mainly we talk now about WMS & WES integration, but there is also one more system layer and one more case of flexibility that we addressed before, and that would be, the machine control level and using a generic WCS.
So we will also look into that in the next slide here. It is possible to have warehouse control system solutions both from the automation vendor and also from another supplier, a generic solution which is not connected to any specific hardware vendor. And the question might be why should you go with that setup? Why is that a more flexible setup? First of all, we think it simplifies the software ecosystem you need to manage as this graph shows. Without too much effort, too much trouble, you can integrate your WCS to multiple types of automation equipment.
But it's at the same time, it'll keep the same, interface towards the higher levels to WES, to WMS. So no matter if you have 1, 2, 3, 5, 10 different automation solutions, it'll all be channeled through the WCS to your WES and WMS. Second part, it's also generic, so it means that you can choose automation equipment from whichever supplier you like. So it's also a little bit more future proof there. It helps you now, but it also helps you in the future want if you want to expand your solutions.
And third, if it comes also from the same supplier as your WMS and WES, it'll also provide you with known interfaces and a known partnership with, your existing supplier. So it provides you a single point of contact for support and maintenance. So we think this is also could be a good option with which office you create flexibility for the future. With that, we are reaching towards the end of this session, so we will now summarize the key learnings here and the key takeaways. This is what we want to bring with you from this session.
First of all, don't separate the manual and automated warehousing parts. Too much manual processes are and will still be a main part of your logistics operations in almost all cases. So it's important to have a holistic view on that, not operating separate automation and information islands. Work with it together as a whole and when you choose your solutions, go for the integration solution that supports your flexibility best long term. So, we know that black box integration is a common, way to integrate and it has been a long, around for a long time, but so has also white box integrations.
So look at your plans for current and future automation and the more types of automation you want to include and also longer term, many sites, many different suppliers, DevOps for a white box solution. Third one, you can also add flexibility to your machine control using a generic WCS and especially important as we talked about already for the flexibility part. If you plan to use more than one automation solution, a generic WCS will give you the freedom to integrate any type of solution and simplify the software ecosystem you have to work with and your IT platforms.
We have a question again here. Good question. I would say that it keeps up very well since we keep the information exchange on a minimal level. So it's more about transferring information about moving from A to B. So what's important to keep up with is the integration part to be able to interact and interface to many different solutions. So with that done then the WCS is a good way of, keeping up with those updates. New types of automation equipment, fine, we need to integrate with that, but then that's already integrated into your solution. Well, yes and no actually.
We think that it's clearer and easier to understand how the different layers interact with the setup that we put here, but we also understand that there are players in the market who will position themselves differently or at least they will encompass or embed that type of functionality from another layer into their solution. So, WES supplier providing they have a WES but not a WCS might from our point of view, have that as an embedded functionality that it's an overlapping area that also can take over that responsibility.
So it's all in the, let's say in what the offerings from the different suppliers are. That's a very good question. Very often we see that the journey starts with the automation vendor and that might be fine, but as we said, it's often then forgotten about business logic parts, which applies both to the manual and automated part of the warehouse. And how should it work together as a whole, if you just look at the automation part with the area you want to automate and you need to think still about how to integrate that into your existing systems in a good way.
Too often we see that this is saved for the last moment when you say, now we have decided for the automation integration, we just need to integrate it into our existing systems. And then many things pops up to the surface, which could have been handled in a better way if addressed already from the start. So we think we should start with looking at both parts at the same time, not just, the automation part. And if you have a generic WCS then even so you could start looking at it from the software side.
So, we are already at the questions, part, so let's see if we have any more questions coming up. You are free to, to fire away any more questions that you might have. Yeah, there are so many different standards and so many different, abbreviations in in this area. So it's, it's hard to to put anything specific, to, to all of this. But we in general, we see that. Just to give a general answer to that, that question, like when it comes to, high level optimization that is put in the WES when it comes to low level optimization of moving tasks between different areas, that's done in the WCS layer.
When it comes to specifics like fleet management, like interacting with different PLC standards, with all things like that, that is typically put down in the MFC layer with that low level integration to that part. That said, our WCS also has an embedded MFC function, so we could also put that, but we see it typically like that. We hope that you have found this presentation useful and found some useful information. And if you want to read more on the trends shaping warehousing and how a WMS & WES and for that part WCS can help tackle those challenges.
Please download our latest trend report, which you can find in the chat and you can also scan the QR code here to, to see that. Actually there is one more question. I will try to answer that very quickly. Well, that's the like beauty of this white box concept that the custom, the customized solutions, they can stay from an automation point of view in the WCS layer and below and the WMS & WES layers can handle the business logic in the same way.
Now there might be different solutions, but if you have a multi-site concept, most often it's possible to handle that in a core solution, but you can also allow certain adaptations to the business logic depending on the site. Okay, with that, we thank you very much for your time and we hope you enjoyed it as we said. And we will close the webinar now and it's always possible to watch it also, after this session when you will get the recorded version so we close the webinar and would like to wish you a continued nice rest of the day. Thank you very much and goodbye!
Webinar details
Duration: 30 minutes
Are you new to warehouse automation, or do you want to extend it in your operations? Either way, system integration is a key aspect to consider. However, with solutions coming in all shapes and sizes, it’s becoming harder to identify the best setup between different hardware and software.
In this webinar, we dive into three key software systems typically involved in automation projects: WMS, WES, and WCS. What roles do they play in automated warehouse processes? How can you integrate them perfectly to maximize your warehouse automation solution? Join our Automation Expert, Claes Jönsson, as he clears up misconceptions and guides you toward the best approach for lasting benefits.
In this webinar, you will learn:
Meet the speaker
Claes Jönsson
Automation Expert
Consafe Logistics
Ready to automate your warehouse with confidence?
Talk to our warehouse automation experts about the right WMS, WES and WCS setup for your operations.