Stay updated by subscribing to our Blog 

Thank you for submitting!

In this post we review the topic of "setting up scanning properly"; as this is one of the most frequent issues encountered in operations that want to move forward.


⚠ Key towards the usage of "scanning" is the proper setup within the process. Many operations are not or only partially leveraging scanning due to a incomplete setup of scanning.


👉Therefor its vital to do the setup completely. In this post we want to share information and help in building the knowledge related to this topics. But before diving into the topic lets first set the theme by listing the benefits of scanning.


1️⃣ What are the advantages of scanning ?


In many case the first relevance lies in raising the quality and efficiency in processing by the use of scanning. Ie the replacement of manual noting and/or manual entry of information.


The comparison with someone that notes information and then enters into a system compared to direct absorption by the system through scanning does not only generate a gain in time, but especially the possible increase in quality is huge. This not only directly, but also in a later phase. Think in this of all the hours lost in search of stock, causes of problems, etc typically a while after the original administration. The less errors made; the less time lost downstream... Potentially there is an additional investment in timing for some do executed the scanning, but the return is almost there be it not immediately then in the longer run.


An additional - in many cases forgotten - element is the "real-time" update that often follows from using scanning. An extreme comparison is the entry of information next day versus the immediate update of the system. Again this drives many benefits as in extra sales, shipping earlier, less searching, etc.


2️⃣ What is important towards a good functioning of scanning?


💡 Essential is the ease of use of scanning!


Following elements play a role in this:

✅ the scanner used to scan

✅ the code that is being scanned (1D, 2D, etc)

✅ the IT-hardware (RF-scanner, acces-points, network, etc.)

✅ the IT-system in which the scanning functions (WMS, ERP, etc)


The better these elements are "together" setup the better the "scanning" will work.


👉 An enormous advantage towards leveraging scanning is the recent surge in developments within all of these elements .

- E.g. 1: the last years the scanners have improved drastically (incl. towards scanning distance, dealing with light, functionalities, etc.)

- E.g. 2: the codes have with the arrival of the 2D codes have very much improved (incl. towards quality and ability to scan incl. placement of smaller labels then before and still getting the same result).


3️⃣ What to focus on during the setup of scanning?


As indicated before the "proper" setup of scanning is a real challenge. In many occasions the proces has been created and validated only within a testing environment and/or for a simplified scenario. But once the real world situation needs to be tackled the operations faces many different types of issues.


Not systematically foreseeing and or addressing these issues will open the door to less, in-proper or even not using scanning and possibly even the entire system; this with all consequences.

Typical problems that can be evaded:

💡 The remark "Its not practical"!

Make sure - it's the absolute number one thing to do - that its practical. Not only the scanning itself, but everything that goes along; e.g. charging, transferring information, placing the device when not used, etc.

- Many projects have come to a halt due to uncharged devices or the team that was not able to log in due to forgetting their codes.

- An RF device can have a build in scanner, but when the scanning is very frequent, very specific (long distance etc) it can be interesting to have an additional gun.


💡 The remark: "The connection drops all the time"!

All the connection be it wired, BT, Wifi, etc. needs to be adequate. Testing this physically over the entire work-area is a proper thing to do.


A couple of additional tips to help roll out scanning:

- Before go-live: execute additional tests en address change management enough

- Go-live: follow-up and address systematically all issues. Go step-wise towards the roll-out of scanning. Go for a first proces in one area, then for a next one,

✅ Now you should be able to address scanning in a more effective way.

To enable your transformation journey & understand your potential feel free to get in touch 👉

📞 0499/85.42.03

📧 jan.baert@dcwise.eu

💬 "Get in touch"

opt for the free Quick-scan.

#warehousing #warehousesolutions #warehouseoptimization


12 views0 comments

Updated: Aug 13

DCwise.eu shares in this post ideas towards how to approach "warehouse-rearrangement" !


👉 The "rearrangement concept" relates to as well the adaptation of the infrastructure (e.g. racks) as the placement of the goods within the infrastructure.


A common example is the "repair" of racks. In this case the goods first need to be taken out of the racks (in a safe way), then the racks are to be repaired, and finally the goods can be stored again.


But the purpose of the rearrangement can also be to improve the storage method of the goods or to improve the location of the goods towards overall efficiency or space use. In relation to these last elements the rearrangement can for example be the placement of fast-moving goods in the fast-mover zones and the relocation of no longer selling items to slow-moving zones.


💡 Following elements need to be reviewed in relation to setting up a rearrangement:

1️⃣ The Plan

2️⃣ The Process

3️⃣ The System

4️⃣ Quality

5️⃣ Safety

6️⃣ The Operational follow-up


We will now discuss them one by one:

1️⃣ The Plan

The foundation of every rearrangement is "Plan"! This includes the order, the method, etc.


In many cases the first challenge is the move of the first goods to a free space. From this then - like a domino - the rest of the plan can follow. Traditionally a rearrangement project therefor will be split in different steps. The opportunities available will play a big role. What is "already" free or can be made available "easily" for those first goods towards allowing the next steps?


2️⃣ The Process

A second element of importance is to setup a proper process for the rearrangement. The larger the number of goods that needs to be moved the more importance this element will have.


💡 In many cases "rearrangement" has not matured yet to a standard-process which makes it dangerous towards loss of goods, loss of service, etc. So it's a good idea to setup a good process before starting.


3️⃣ The System

In line with the process the system needs to be updated. In many cases this element is absent or incomplete. Challenge is then to keep the system in in sync & / finds methods to minimize the operational impact.


A typical measure is to setup a certain frequency in the system-updates that needs to be (manually) done. Make sure the is frequent enough, because Murphy (resource no longer available, other needs, etc) is just waiting always around corner...


💡 The operational impact...

When looking at the overall process (incl the system) its best to have the proper solutions in place to mitigate issues. Think in this of leaving a note in the original location of what happened "a rearrangement..." and where the goods are now. Through this concept all arriving at the location (for example when the system update has not taken place yet) knows it's not a stock-out, but the goods are being moved. Potentially even the new location can be found in support of the operations.


4️⃣ Quality

In many cases the rearrangement-processes are under (time)pressure. Considering this is a process that only possibly infrequent executed or not fully supported its by fa a solid process. One measure therefor will be to apply the proper quality controls physically and or system-wise.


This can be done by "sampling" or based on reviewing "exceptions" or "deviations" or even a "total control". All of this to make sure that the quality is supported and operationally there is not a large impact.


💡In line with the previous the "check" can be by having a third person taking away the "notes" that were left behind at the time of the move; this to validate the proper execution of the move.


5️⃣ Safety

A rearrangement-process often takes place through the standard processes. The "rearranger" might even be working with means that have issues (damaged goods and racks etc.). Also, his behavior is different than the operators executing the standard processes (e.g. staying longer at the same location, driving in the opposite direction, etc.). This makes that the safety aspect needs to be thoroughly looked at and where needed special agreements &/measures need to be taken.


Examples of this are:

- executing the rearrangement at specifics timings (night, shift change, brakes, etc.)

- placement of additional signage (using cones, special dress-code for the rearrangement crew, etc.)

- setting up reporting- and safety-processes similar to when contractors perform work (incl. singing in & out)

- usage of safety gear (harnesses, etc.)


6️⃣ The Operational follow-up

"Last but not least" there is the Operational follow-up; essential seen the many challenges to do the right follow-up towards progress, quality, safety, etc. As discussed in 1️⃣ to 5️⃣ and where needed to take corrective actions.


💡Now you should be able to approach the "rearrangement challenge" in a more structured way.


More information on DCwise and other interesting topics can be found on our site: www.DCwise.eu


To enable your transformation journey & understand better your potential feel free to get in touch in 👉

📞 0499/85.42.03

📧 jan.baert@dcwise.eu

💬 "Get in touch"

opt for the free Quick-scan.

#warehousing #warehousesolutions #warehouseoptimization



9 views0 comments

Updated: Jul 6

The selection of a Warehouse Management System is a very important decision for a warehouse operation. In this post we explore this topic in collaboration with Lanark.


Important - as with every project - is to approach this question in a structured way. We suggest the following steps:


1️⃣ ASIS Scan – What is the “context” and what are the “decision factors”?


Don't rush straight into functional requirements! First define "the context" in which the decision needs to be made!


Create an image of the organization is created using the following questions:

- How does the operation work in general and what are its strengths and weaknesses?

- Which solutions are already present?

- How flexible is the operation towards changes?

- What is the "technology maturity" of the company?

- What are the future needs towards functionalities and processes?

- What are the exact initiators and/or drivers of the project? Cost? Continuity? Future readiness? Service?

- Is the company prepared to compromise regarding to functional requirements when budget becomes an issue? Or do they work with a wish list without compromises?

- And so on...


This "AS IS" review will later support the selection of the WMS solution.

For example, an organization without its own IT-department needs to watch out with complex WMS-products. Another example is a company that goes for continuous improvement and/or is active in a changing environment needs a flexible solution.


This effort of becoming familiar and clearly describing the company needs, allows in a later phase to evaluate which solutions will work and which ones won't work.


💡 In this phase the decision factors are determined that will be leveraged to make the final choice. Notice that this is all done before going into depth towards the WMS solution.


2️⃣ Functional Analysis – What does the system need to be able to do?


In this step the functional needs are clearly listed. Think in this about the needs towards for example stock management and stock-control, about the methods used to the receive goods and perform order-filling (RF, etc.), or about the special needs such as cross-docking. At the same time the exact criticality and priority is added (crucial, opportunity, etc.).

💡 Tip: do not start reinventing the wheel here... it’s easier to start from existing lists.

👉 Important is to "rewire your brains" and distance yourselves from how the processes work currently and take the crucial step towards functional thinking. It is extremely important to "open-up" for doing things differently! Be aware that WMS' are build on logic and will be able to support most of your processes in an efficient manner!


👉 Also do not forget its "only" a WMS! It will be able to do a lot if its well-constructed and setup, but most likely it’s not going to make your coffee or polish your shoes. It's important to identify the functional scope of the WMS in your overal system landschape and architecture. A WMS is in the first place a transactional system meant to drive a warehouse operation. Some systems dare to go very broad in this "support", but if you drift to far from the core; then at one time you 'll run into the limitations.

Also do not forget in this phase to look at the "non-functional" requirements, meaning elements such as ease of use, hardware, cloud, security, upgrade strategy, support model, ...

3️⃣ Determination of the "long list" of candidates

Next step is to list the possible available WMS solutions and validate them with the input from the "scan" 1️⃣ and the "functional needs" 2️⃣. In many cases its quickly possible to limit the number of candidates and go into depth not taking along all candidates. This off course makes the entire process more efficient.


💡 Important when setting up the long/shortlists – is to understand of the bat in which "tier" your organization resides. Often we refer to 4 tiers: going from basis stock management systems, more expanded local solutions with a clear set of functionalities (e.g., Corax), regional players with flexible extensible systems (e.g., Reflex or Consafe) and the global players (e.g., SAP, Manhattan and JDA/BY). Depending on this basic choice the workload, project time, costs and resulting in a completely different business case.


4️⃣️⃣ The review of the options and The final selection


After making a first "long" list, one needs to quickly push towards a shortlist. Try to reduce this a swiftly as possible to a maximum of 3 parties. In this the weighing factors of step 1️⃣ are to be leveraged incl workload, project time, costs and functional fit. Als take along the “cultural fit” or “gut feeling” element towards the future partner. In the end based on the scoring (based on the weighing factors) the right WMS solution can be selected.


Some last suggestions in respect to this:


💡 Experience of the parties in your sector or with similar companies , but also dare to look beyond this. A keen team with some fresh insights can come with original solutions.


💡 Make sure there is interaction with the parties within the selection process and preferably beyond the sales team of the candidate. That way you become familiar with the supplier and can validate if there is a fit in culture and approach. Don't forget that this might be the start of a long relationship.

💡 To validate the quality it’s possible to request demo's or proof-of-concepts. Preferable already including somewhat your products and/or processes. Also doing interviews of the team that would be assigned is an option often used. All of this to allow you to get a better idea of what you are buying/selecting.

To enable your transformation to journey and understand your potential feel free to get in touch 👉

📧 jan.baert@dcwise.eu or wim.farasyn@lanark.be


#warehousing #warehousesolutions#warehouseoptimization






9 views0 comments