Request Information
ERP Software Solutions for Manufacturers and Distributors The TGI Difference Discover TGI and Enterprise 21 Enterprise 21 Product Demonstrations Customer Case Studies Software Selection

Archive for the ‘Software Evaluation’ Category

ERP Software Evaluation: What Customers Want from ERP Software and What ERP Vendors Want

Tuesday, March 9th, 2010 by Dave Litzenberg

Let’s examine what most customers want from new ERP software and what most ERP vendors want from an ERP selection and implementation.  While there are many layers to the topic of what customers want from new ERP software, the core answer of what businesses want from new ERP software is business results – business owners want to reduce costs, increase revenue, improve operational efficiencies, and make it easier for their customers to do business with them.

Beyond business results, companies also want the following from new ERP software:

  • Efficient software evaluation leading to a successful result – companies want to make excellent decisions in the most efficient manner possible (unfortunately, when businesses aren’t aware of how this process should work, it rapidly becomes very inefficient).
  • Efficient, successful implementation – companies want their new software to deliver the functionality they expect and for the implementation process to be delivered on-time, on-budget, and on-scope.
  • Good long-term customer/vendor relationship (“win-win”) – companies want to be able to work with their ERP vendor, have continuity of the software vendor’s business, continuity of relationships with personnel at that business, and be able to understand how best to utilize their software and to resolve issues as they arise.
  • Ability to grow with the solution – companies want a solution that will last them for an extended period of time, in many cases this is 10-15 years or more.  To be able to do this, the software must be flexible, robust, and have sufficient functionality to be able to be leveraged as the customer’s business continues to grow and evolve.

So, what do ERP vendors want?  Probably not surprising, they likewise want business results.

Additionally, ERP vendors also want the same things the customers want:

  • Efficient software evaluation leading to a successful result – while ERP vendors would love to bat 1.000 by winning every deal they touch, they know that’s not practical.  They want to compete in deals in an efficient manner where they can compete on a level playing field, can win, and it is worthwhile to win.
  • Efficient, successful implementation – vendors want their customers to receive the business benefits they desire from their software and want the implementations to be delivered on-time, on-budget, and on-scope.
  • Good long-term customer/vendor relationship (“win-win”) – vendors want to work with customers who are easy and fair to work with, have continuity of the customer’s business, continuity of relationships of personnel, and are able to understand and internalize how best to use the software they’ve acquired.
  • Ability to grow with the solution – vendors want customers to continue to leverage more and more of their software’s capabilities over time.

While said somewhat under the covers above, I’ll also explicitly state the following which ERP vendors also want:

  • Efficient sales cycles (winnable deals, no “tire kickers”) – again, vendors want to focus their time on evaluations where decisions will be made and customers will move forward.  There is no time to be spent with perennial prospects that go through the same evaluation once a year and never decide to move forward to do anything. Additionally, vendors don’t want to be in a position where a potential new customer has orally committed they are going to move forward with the vendor only to take an inordinate amount of time to make the final commitment and sign contracts.
  • Happy, referencable customers – there is nothing better from a vendor’s perspective than having happy customers who are willing and able to act as references on their behalf.

You’ll note that to this point in time I’ve mentioned these things apply to most customers and most ERP software vendors.  That is because there are still people, including those who set the cultural tones of their businesses, who believe the only way for them to “win” is if the other party with whom they’re working is to “lose.”  This “win-lose” mentality unfortunately still exists frequently in the customer/ERP vendor intersection.

Speaking from an ERP software vendor’s perspective, when it is determined that a potential customer is focused on establishing a “win-lose” relationship, we walk away from those deals as rapidly as possible.  Likewise, if potential customers determine that an ERP vendor is attempting to establish a “win-lose” relationship, those customers need to eliminate that vendor from further consideration as rapidly as possible.

The most prevalent situation in which ERP vendors attempt to establish a “win-lose” relationship is where the functional and cultural fit between the vendor and potential customer is low, and the vendor is so hungry for new sales (i.e., business results are far more important than any of the other desires) that they continue to press on to close the sale.  In doing so, the ERP vendor knows the implementation is going to hit the rocks, but their objective is to get the customer so deeply invested in the project (both time and money) that they cannot turn back.

Those who are unfamiliar with how to structure and perform an ERP Software Evaluation are most highly susceptible to be bitten by a vendor attempting a “win-lose” transaction.  In cases in which the company is unfamiliar and inexperienced in orchestrating a software evaluation on its own, those companies are highly encouraged to find and engage experienced, independent assistance to help with the evaluation.

Here again I want to stress that the most critical word in this statement is “independent.”  There are tons of individuals and businesses that tout themselves as independent.  However, they may be software resellers in a consultant’s clothing or have biases to specific products because they have established implementation practices built around those solutions.

If, for whatever reason, hiring an independent consultant is not feasible, companies are encouraged to adopt a structured, analytical process they can follow on their own.  To help companies establish and manage a structured, analytical evaluation process, TGI offers free software selection tools via our Web site for the do-it-yourself software evaluation.

In closing, through this point in time, I’ve had the opportunity to work with well over 2,000 end companies and roughly 200+ independent consultants in ERP software evaluations since Q4/2003. During that time, I’ve seen some firms and individuals who were very good at performing their roles in their respective evaluation processes, while others were at best ill-prepared. In the end, when participants in the process are unable to successfully play their positions – whether intentional or unintentional – nobody wins.

In an effort to draw upon these experiences to help the various stakeholders of the process learn from these activities, I wanted to summarize those situations into a single statement. In doing so, I was drawn to a famous quote by noted Swiss Psychiatrist and founder of analytical psychology, Carl G. Jung, who said, “The world will ask you who you are, and if you do not know, the world will tell you.”

Here is what I call “Litzenberg’s ERP Software Corollary to Carl Jung’s Statement”…

“The world will ask you what you want in new ERP software, and if you do not know, you’ll likely be sold something you don’t really want, can’t really use, will spend a lot of time, effort, and money trying to get it to do something it was never intended to do, and ultimately, won’t achieve the desired results.”


New ERP White Paper: Five Critical Software Requirements for Improved Product Safety and Traceability

Thursday, February 25th, 2010 by Alex Smith

We just released a new white paper in the TGI Resources Library, Five Critical Software Requirements for Improved Product Safety and Traceability. Given the rise of increasingly stringent FDA and USDA regulatory requirements, companies in the food, beverage, chemical, and pharmaceutical industries are being forced to change their internal business processes and leverage new technology to help them meet evolving industry compliance requirements for product safety and lot traceability. TGI’s Five Critical Software Requirements for Improved Product Safety and Traceability white paper details the necessary ERP software features and functions required for organizations to ensure the highest levels of product safety while simultaneously gaining real-time access to ingredient and finished good lot information. To download the white paper from the TGI Resources Library, please click here.


ERP Selection: The Importance of a Quantitative ERP Software Selection Process

Tuesday, February 2nd, 2010 by Alex Smith

The ERP selection process is one of the most important activities in which an organization engages. Selecting an ERP system represents a technological and business process transformation for the organization; therefore, it is imperative that the organization conduct a thorough, quantitative analysis of various ERP software companies and solutions. In doing so, the business’s software selection team can gain a true “apples to apples” comparison of each software solution and determine which solution offers the best functional fit for the organization.

To help manufacturers and distributors in this process, TGI’s Software Selection Tool Kit offers, among other resources, software demonstration script templates and grading sheets to be used for onsite ERP software demonstrations. The selection team can use these templates to develop a software demonstration script that reflects the key software requirements of the organization. The selection team would then distribute these scripts to a select group (usually 2 or 3) of vendors with sample data (products, parts, ingredients, vendors, customers, etc.). The software vendors, in turn, would use the supplied sample data to follow the demonstration script prepared by the selection team. Using the software demonstration grading sheets contained in TGI’s Software Selection Tool Kit, the selection team can score how each vendor performed for each task in the demonstration script. Following the final onsite software demonstration, the selection team can compile scores for each ERP software vendor and see, quantitatively, how each software solution compared to the other demonstrated software solutions. The end result of this process will be a software vendor and solution that outscored and outperformed the other software solutions that were demonstrated.

By requiring software vendors to follow a demonstration script that reflects the organization’s key software requirements, the selection team will be able to see first hand how each vendor can meet those requirements. This process also prevents the software vendor from shying away from a specific software requirement that it knows it won’t be able to meet and ensures that each software vendor was evaluated in a consistent manner.

To download TGI’s onsite software demonstration templates and grading sheets, please click here.


The ERP Selection Process: 50 Questions for Every ERP Software Supplier

Wednesday, January 13th, 2010 by Alex Smith

We recently added a new white paper to the TGI Resources Library, 50 Questions for Every ERP Software Supplier. This white paper lists 50 questions that are critical to a successful ERP selection project and must be asked of every potential ERP vendor. While there are some basic, general questions about product functionality, the white paper is not intended to be a list of questions relating exclusively to functional features; rather, the questions are designed to give the selection team a better feel for the software vendor’s general business philosophies, organizational longevity, approach to ERP implementation and customer support, annual maintenance fees, software upgrades, etc. One can think of the white paper as a “Getting to Know You” list of questions to ask ERP vendors. To download the 50 Questions for Every ERP Software Supplier white paper from the TGI Resources Library, please click here.


Buying a fully-integrated ERP software suite vs. a best-of-breed solution approach

Friday, December 25th, 2009 by Dave Litzenberg

This article will explore the relative advantages of acquiring and implementing a fully-integrated ERP software system rather than buying application software based on a best-of-breed solution approach.

A typical manufacturing or distribution enterprise will need the following types of functionality:

  • Financial management and reporting;
  • Inventory management, purchasing, and order management;
  • E-commerce;
  • Customer relationship management;
  • Manufacturing planning and execution;
  • Warehouse management;
  • Forecasting and planning; and
  • Decision support and business intelligence.

While one could buy subsets of the above list from separate vendors, here are some of the disadvantages to buying this functionality based on a best-of-breed approach:

  • Separate systems with separate infrastructure – separate database instances potentially requiring separate servers.
  • Different look and feel for various applications – users would have to learn different sets of commands and menu structures for different applications.
  • Sharing of data across separate systems – passing of data would generally be done via a batch process.
  • Timeliness of data across the enterprise – even if the data were shared perfectly across the separate systems, there would be time delays between the time data is initially present in one system and when it becomes visible in the other system.
  • Single version of the truth for the entire business – when data is not fully in-sync, there can be differences of opinion as to whose data is correct (i.e., what were the monthly sales figures for customers in a given category or geographical region?).
  • Everyone in the organization works from the same set of information – provides visibility to data from across the organization to make well-informed decisions that impact customers and the organization as a whole.
  • “Least common denominator” for functionality – often an overlooked point in discussion of this topic. There can be some enhanced functionality in one of the functional areas that is the reason the business decided to buy that specific best-of-breed solution in the first place; however, the functionality and data needed from other functional application areas to support and enable that functionality may not be present or easy to access in those other modules, making the new functionality impossible to use.

The following describes the spectrum of integration methods for enterprise-class application software:

  • Fully-integrated system – designed and built from the ground up as an integrated whole all by the same software development organization and team.
  • Separate systems that are owned by the same software vendor – software vendors may have acquired separate systems and developed integration points between these solutions.  In general there would be separate development teams for the various solutions within the given software development organization. The development teams’ primary focus would be on functionality and ease of use enhancements within their specific product lines, not the integration points between various solutions.  There could be a third, totally separate development team for an integration solution from the software vendor.
  • Systems from different organizations that work together – similar to systems that are owned by the same software vendor above, except in this case the separate development organizations focusing on the separate solutions are not owned by the same parent organization.  As you might imagine, this further complicates matters.  One solution provider may elect to change their complete database schema from one software release to another thus disabling any existing integration points. This approach also poses problems for the upgrade process, software vendor roles and responsibilities, and paying maintenance fees to multiple software vendors year after year.
  • One-off integrations by systems integrators – in this case, a systems integrator who is implementing one or more of the software solutions for a given customer may have developed an integration point between two solutions.  In this case, the systems integrator is the only one concerned with the integration – not the development organizations who own the separate software solutions.  This is the most precarious situation of all of the non-fully integrated solutions scenarios.

Core advantages of fully-integrated systems:

  • Data is timely and accurate across the entire enterprise with single points of data entry.
  • Training of personnel in one functional area can translate into other functional areas because the usability aspects of the system as well as core functions (creating new items, querying for data, etc.) will be the same across all areas of the application suite.
  • Single version of the truth – by having one centralized system, data will be the same for the entire enterprise.
  • Integration between functional areas will be the strongest and will be in the best position to enable a company to implement version upgrades as they become available without risking invalidating an integration point between two separate systems.
  • Should be able to take advantage of all functionality in the system without concern about running up against a “least common denominator” situation where functionality in one area of the system may be unusable because corresponding functionality and data may not exist in other functional areas of the business system.

It has been my experience over the years that most organizations who have adopted a best-of-breed approach have not done so based on a strategic decision; rather, they have had a core set of functionality they have decided is the starting point for ERP selection and implementation purposes of a new system.  Rather than focusing on a superset of functionality they will likely ultimately need over time, they may have made a decision to go with an ERP software package that fit the core subset of capabilities very nicely at a price point that was substantially lower than fully-integrated solutions with broader capabilities.

Over time, however, the business outgrows the functionality originally selected and implemented and is now forced to make a decision of whether it wants to keep its existing software and add a bolt-on solution to what it already has or start over and go with a broader, fully-integrated ERP solution.

Organizations are strongly encouraged to step back and ask themselves where they are going strategically and what complete set of functionality they will ultimately need over time so they can buy a fully-integrated software suite that provides this complete set of functionality even if they don’t take advantage of all of its capabilities day one.


ERP Software Selection: Evaluating Software Functionality and the ERP Vendor

Thursday, November 26th, 2009 by Alex Smith

When evaluating various ERP software solutions, scope of software functionality is an obvious priority for selecting the best functional fit for the manufacturing or distribution organization. Software selection teams should evaluate demonstrated software packages in a quantitative manner to determine the ERP system that best meets the organization’s specific software requirements. That being said, evaluating the software vendor, in addition to software functionality, is often overlooked in the ERP selection process.

It is important to analyze the ERP vendor as a company, not just the software the vendor is selling, as choosing an ERP software solution and vendor is a long-term commitment for the organization; in fact, the typical usage for an ERP software package (including future upgrades) can be anywhere between 10 and 15 years. Software selection teams should analyze the vendor’s approach to ERP implementation (Are implementation services delivered by the software vendor directly, or are they outsourced?), customer support (Are support calls answered by the software vendor directly, or are support calls outsourced to a third-party support provider?), ongoing maintenance, software upgrades, etc.  Please note that if you are acquiring an ERP software solution through a vendor’s value-added reseller (VAR) rather than directly from the ERP software vendor themselves, you should be asking these same questions of the VAR.

On a broader level, ERP selection teams should assess the software vendor’s long-term viability as an organization. A good question to ask potential software vendors is if their proposed software solution was developed by the vendor or if it was developed by a different company that the vendor acquired. In addition, selection teams should ask the vendor to provide the company’s revenue-per-employee ratio. In the ERP industry, once a software vendor’s revenue-per-employee ratio drops below a certain level, the vendor is likely to be acquired, resulting in potentially higher maintenance fees for existing customers. For more information on revenue-per-employee ratios and what they mean in terms of software supplier longevity, please click here. Furthermore, selection teams should ask software vendors if they provide a software acceptance period to validate that the selected solution meets the organization’s requirements that were set forth during the ERP selection process.

While these are just a few of the questions to ask potential software vendors, they are critical to selecting an ERP vendor who can deliver superior software functionality and serve as a technology partner for the organization in the many years following software selection and implementation. For additional information, please visit The TGI Difference.


Visit the New TGI Resources Library for Enterprise 21 Demonstrations, Software Selection Tools, and more

Monday, November 9th, 2009 by Alex Smith

We recently released the TGI Resources Library. Aside from being able to access Enterprise 21 ERP software demonstrations and view past TGI webinars, one of the most useful aspects of the TGI Resources Library is that it gives site visitors immediate access to all of TGI’s ERP selection resources, including the complete version of TGI’s Software Selection Tool Kit. The tool kit is designed to provide software selection teams with the necessary resources for conducting a thorough, well-structured ERP selection process with a comprehensive and quantitative analysis of various ERP vendors and solutions. From the SSTK Downloads page, site visitors can download any of TGI’s software selection resources individually or download the complete Software Selection Tool Kit as a single executable file. With the conclusion of 2009 rapidly approaching, manufacturing and distribution organizations who plan to select a new ERP system for implementation to begin in early 2010 can leverage TGI’s Software Selection Tool Kit as a guide for their software evaluation projects.


Visit TGI at the 2009 STAFDA Technology and Consultants Fair

Tuesday, October 27th, 2009 by Alex Smith

On November 9, 2009, TGI will be attending the 2009 STAFDA Technology and Consultants Fair. TGI representatives will be on hand to showcase TGI’s Enterprise 21 ERP software at Table 6. Conference attendees may arrange for a personalized demonstration of Enterprise 21 while at the STAFDA technology fair. The fair offers a great opportunity for organizations in the specialty tools and fasteners industry to see the latest in business management software technology and gain an understanding of the many benefits a distribution organization can derive from integrated distribution software solutions.

Given such an opportunity, business executives and IT professionals in the tools and fasteners industry should come to the STAFDA Technology and Consultants Fair armed with key questions for software vendors that pertain to their unique industry requirements. Some examples of key questions for software vendors who supply solutions for the tools and fasteners industry include:

  1. What does the software system offer in terms of managing pricing methodologies, promotions, and allowances?
  2. What types of inventory management and replenishment methodologies does the software offer?
  3. Does the system include integrated RF and barcode technology to operate the warehouse in a paperless environment?
  4. Does the software offer integrated procurement functionality that provides RFQ processing, vendor performance management, designation  of a preferred supplier for a given item, accounting for supplier lead times, etc.?
  5. Does the software provide integrated e-Commerce functionality for Internet-based orders?
  6. Does the software interface with EDI translations?
  7. Does the software interface with UPS, FedEx, and LTL shipment manifesting systems concurrently?
  8. Does the software offer both available and capable to promise order management functionality?
  9. Does the software account for landed costs, import duties, drayage charges, etc. for imported items?
  10. Does the software offer MRP/DRP functionality?
  11. Does the software provide functionality for kitting, assembly, light manufacturing, and other value-added services?
  12. Does the software offer integrated financial management?
  13. Does the software feature business intelligence, analytics, and reporting functionality with drill-down capabilities?

While these are just some of the many questions for software vendors, they should provide a good basis for discussion in limited time while at the 2009 STAFDA Technology and Consultants Fair. If you plan on attending the 2009 STAFDA Technology and Consultants fair and would like to schedule a demonstration of TGI’s Enterprise 21 software, please click here to complete TGI’s 2009 STAFDA registration form.


Reviewing ERP Vendors’ Pricing Proposals: Does the Proposal Reflect the Demo? Does the Demo Reflect the Proposal?

Thursday, September 17th, 2009 by Alex Smith

When engaging in an ERP selection process, it is important to require ERP vendors to provide pricing for all demonstrated software functionality and the associated implementation and service fees for such functionality in their pricing proposals. An unfortunate tactic frequently deployed by many software vendors is to demonstrate the full scope of their respective software’s functionality and provide pricing estimates for only a fraction of the software functionality that was demonstrated during the sales process. Some vendors, for example, will demonstrate their software’s ability to allow manufacturers or distributors to operate their warehouse in a completely paperless environment through the use of RF and barcode scanning technology. When these same vendors draft a formal proposal for the selection team, however, the price estimate in the proposal does not reflect a warehouse management system that includes RF and barcode technology. The intent of the software vendor, sadly, is to mislead the selection team, make the selection team believe they are purchasing an ERP system that meets all of their business software requirements – both current and future – and then demand the manufacturer or distributor pay for additional software functionality after the fact. The software selection team should view such practices as completely unacceptable.

There are two ways for software selection teams to ensure that the functionality that was demonstrated to them is reflected in the vendors’ proposals. First, the selection team should require vendors to guarantee, in writing, that all demonstrated functionality is included in the proposals. If a vendor is not willing to agree to honesty and straightforwardness, then why would the selection team ultimately choose to select that vendor as their preferred solution provider from the selection process? Secondly, as part of the software evaluation process, selection teams should look for a software vendor who has provided consistent, straightforward answers to questions and pricing throughout the sales process and has a proven track record of providing upfront pricing for all demonstrated software functionality.

Requiring software vendors to submit proposals that reflect all demonstrated software functionality will provide the selection team with the necessary information to select a software solution that is free of hidden or unexpected software costs.


Gauging Long-Term Viability of Software Vendors – Examining Revenue-per-Employee

Monday, August 17th, 2009 by Dave Litzenberg

One of the key areas companies attempt to gauge as part of their ERP selection projects is the long-term viability of potential ERP software companies.  On the surface, one might initially assume the vendor’s annual revenue is the key element to consider, but is it really?

In recent years, Oracle bought PeopleSoft, who had previously acquired JD Edwards.  In using Software Magazine’s Software 500 as the data source, PeopleSoft reported corporate revenue of $2.27 billion in 2004 – the last year they reported data as a separate business entity prior to their acquisition by Oracle.  Likewise, JD Edwards reported corporate revenue of $904 million in 2003.  Assuming revenue alone could be used to gauge long-term viability, would anyone have come to the conclusion that these software vendors would be gobbled up?  Some other large entities that have been acquired in recent years with their last reported annual corporate revenue from the Software 500 include Siebel at $1.34 billion, Hyperion at $765 million, SSA Global at $712 million, Geac at $444 million, and Intentia at $425 million.

Rather than merely reviewing revenue, it is our recommendation that potential buyers of ERP systems and consultants with whom they work take a good look at the various vendors’ revenue-per-employee ratios.  For example, let’s examine this in light of the recent announcement that SoftBrands was being acquired by Infor.  SoftBrands reported corporate revenue of $93.4 million with 775 employees in 2008.  This equates to a revenue-per-employee ratio of roughly $120,500. 

In reviewing a series of twenty-five software businesses (including ERP, supply chain management, CRM, and financial management software companies) which have been acquired by other ERP software businesses since 2002, seven of these had revenue-per-employee ratios between $100,000-150,000 in their last year of reporting, nine were between $151,000-200,000 (including PeopleSoft and JD Edwards), five were between $201,000-250,000, and three were between $251,000-280,000 (Hyperion, Mapics, and Siebel).

So, what are the revenue-per-employee ratios of some of the familiar ERP software vendors in the market today?  For 2008, Microsoft led the pack at approximately $647,000 in revenue-per-employee, followed by SAP at $344,000, and Oracle at $240,000 respectively; however, these numbers include these organizations’ complete portfolios of products and services rather than ERP software sales and associated services revenue alone.  In reviewing data for the top ten big name Tier 2 ERP vendors included in the study – using 2008 data if they reported or their most recent reporting in 2007 or 2006 otherwise – four of these businesses reported revenue-per-employee ratios between $100,000-$150,000, while the other six were between $151,000-200,000. 

Based on the percentage of employees with strong technical talent that software businesses must attract and retain, and considering a typical employees’ salary and benefits, ERP software companies whose revenue-per-employee ratios are at or below $150,000 may start to raise some serious questions about their long-term viability.

Businesses that are selecting new ERP systems are doing so with the knowledge that they are making a long-term commitment to run their businesses on the new software packages and to work with the associated software vendor for roughly 8-12 years, on average.  In doing so, gauging the long-term viability of the software vendor is a key element to this long-term success.  We encourage software selection teams to examine potential vendors’ revenue-per-employee ratios and trends over the past several years before making a final commitment to move forward together.

Note: Software Magazine’s Software 500 has been the source of all revenue and employee data for this article.