One of the most daunting aspects of supply chain software, like WMS, TMS or Labor software, is the evaluation and selection of something that will work for your organization, at a price that is within your budget and with enough features to solve today’s business needs (and tomorrows).

The supply chain software market can be confusing, with products that look very similar from one provider to the next and sometimes make very similar promises. Even just figuring out where to begin in the supply chain software evaluation and selection process can be a huge challenge. And, how do you even know that replacing your existing software is the right answer for your organization?

Here are three things to consider as you work through the process of supply chain software evaluation and selection:

  1. Contact us for a brief questionnaire – If you can answer yes to any of the questions, you are headed in the right direction and have some compelling reasons to evaluate new supply chain software. If the answers are all “no”, there’s probably a different answer to the challenge that started your consideration of new software.
  2. Phone a friend – Talk to your peers or get in on the discussion groups on LinkedIn. Talk to people who have walked in your shoes already – they may have some very helpful suggestions and offer up things you hadn’t yet considered for evaluating and selecting supply chain software. Go to supply chain conferences (like ProMat) or user conferences held by software vendors (i.e., click here to learn more about JDA FOCUS, formerly RedPrairie RedShift) and talk to other people who have installed systems like what you are considering.
  3. Throw caution to the wind – Just close your eyes and pick one. How bad can it be, right? (ok – this one is a joke and not recommended)

All kidding aside, we have seen companies embark on this mission of supply chain software evaluation and selection when they didn’t need to – there was a simpler and less expensive answer to their challenges. If you answered “Yes” to any of the questions from our questionnaire, rest assured that you have some solid reasons to consider new supply chain software. Here are some of the next steps to follow (some might seem like no-brainers, but they are important):

  • Build a Team – Depending on the size of your company, you’ll want to put together a team of individuals that represents all of the different parties (stakeholders) who will use the software, and thus have a vested interest in the process. For example, if there are multiple facilities in your organization, you may want to reach out to all the General Managers and ask them to each select a resource for the team (it can be helpful to give them a few characteristics you’re looking for such as responsibility level, experience, etc. – this will help ensure you build the best team possible and give your project a greater chance for success).
  • Conduct a Current State Analysis – It’s helpful to build some kind of analyses of what is commonly called the “current state.” Basically, this is information on your company as it stands today, i.e., the number of users at each level, square footage, inbound and outbound detail, etc.
  • Create a list of Functional Requirements – It’s a good idea to involve the team you’ve built/are building; they should provide you with functional requirements of what exactly this system needs to do. The list will probably need some level of compilation by you or a group of team members, to merge duplicates and to finalize remaining requirements. After that, there are a number of things you can do such as categorizing and giving the different categories a weight to make sure you get your most important requirements met. This final document will help when you begin soliciting the different software vendors for information – sometimes the process involves sending each vendor a request for information (RFI) or request for proposal (RFP). There really is no difference between these although it’s commonly assumed that RFI’s indicate that a company is not as close to purchasing software as a company that is requesting an actual proposal.
  • Schedule Software Demonstrations – Once you get the responses back from the vendors, it’s a good idea to see some demonstrations of the software in action. These are going to differ from one to the next, so you’ll want to provide a guide to help the vendors understand what you’d like to see not only so you get as close to an apples-to-apples kind of comparison as you can get, but also to make sure that the software can meet your top level functional requirements, i.e., can the product(s) do what you need it to do? As you’ll see once you go through this stage, it can be difficult to keep the products straight, particularly if you’ve not kept the vendor list to three or less. Some pitfalls here are caused by the obvious fact that all software vendors want you to buy their software. Everyone wants and needs to make a living, right? So, you may experience all of your selected vendors telling you they can meet all of your requirements. When that happens, it makes the job of selecting one even more difficult. For example, integration is generally pretty high on the list for most companies – you need to know that what you’re buying will work/talk to/integrate with everything else you already have. You may hear that each vendor offers standard integration – but what does that mean? If you don’t know where to ask the deeper questions, you may end up selecting a software package that will need major additional effort (and money) to work with your existing systems. Like buying a refrigerator when your main requirement outside of price is that it makes A LOT of ice. When you get to the appliance store, however, the sales rep shows you the bells and whistles of how your microwave and stove integrate with a given refrigerator, how well they match, and on and on. They don’t bother to start you out with the models having high volume ice makers or, suggesting that you might be better off buying an ice maker given how much ice you go through in a day.
  • Appoint an Objective Reviewer – Regardless of the type of experience on your team, some people may develop favorites. You or someone you select needs to be in charge of objectively reviewing the software on how well it meets your top requirements across the board, not how well it does one individual task (unless of course, that’s absolutely the most critical task your organization does in a day). This is also where weighting particular functionality is important and will help you arrive at the best decision.
  • Examine the True Cost of Purchase – Now that the demos are done, the notes are taken and features are compared, you need to examine what the true cost of actually owning these different products might mean. The costs range from the obvious, like license fees and maintenance costs to items you may not have considered like training, custom integration, enhancements, software installation and hardware setup and configuration.

Open Sky consultants have experience from all sides of the supply chain software evaluation and selection equation – many have worked for end users and some for the software vendors themselves. We know the market and the potential pitfalls and can help you understand if JDA WMS, WLM or TMS is the right software for your organization. Contact us today to get started.