be_ixf;ym_202412 d_28; ct_150

TGI - ERP Software Solution

Main Menu
ERP Insights
Request Online Demo

ERP Insights



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

March 9th, 2010 by admin

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. Read More…

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.”


ERP for Small Businesses: Taking Advantage of all Your ERP System Has to Offer

March 2nd, 2010 by admin

Many small businesses with whom I speak, generally, want the same basic functional features in an ERP system. Fully-integrated order management, inventory control, warehouse management, purchasing, manufacturing, financials, CRM, and business intelligence are critical elements to any ERP selection project. That being said, many small businesses also question how they can take advantage of all the software functionality a small business ERP software solution has to offer given their relatively limited internal resources and their desire to complete ERP implementation in a timely, cost-effective manner. How, then, can small businesses take advantage of the complete set of software functionality inherent in their ERP system while still completing ERP implementation in a relatively short time frame? Read More…

When going through ERP implementation, a small business should work closely with its project manager in determining the project scope, which consists of those core functions, rules, and processes that the system must deliver by the project go-live date. At the conclusion of the implementation process, the business must be able to perform all necessary transactions in the ERP system to conduct business on a daily basis in a manner that is faster, easier, more cost-effective, etc. than prior to implementation. The small business, should, in turn, begin to realize a return on its ERP investment.

Following software implementation, the small business should continue to work closely with its project manager in developing a post-go-live plan to roll out additional software functionality, such as leveraging wireless warehouse management with RF and barcode scanning devices, paperless AP functionality to operate the AP department in a completely paperless environment, and/or using automated supply chain processes to continue to streamline the organization’s purchasing, inventory, order entry, and manufacturing departments. Again, this will allow the small business to continue to realize a return on its ERP investment in the months following ERP implementation while taking advantage of incremental software functionality that is already built into the ERP system.

As mentioned in a previous article by Dave Litzenberg, TGI conducts six-month ROI workshops with our customers. These workshops, which consist of the customer’s core team and a combination of TGI’s executive, project management, and sales teams, are designed to initiate plans for the customer to take advantage of additional functionality in Enterprise 21 so the customer can continue to realize an increasing return on its investment in TGI and Enterprise 21.

By closely working with the ERP vendor in the months and years following ERP software implementation, small businesses can develop post-go-live plans to take advantage of additional software functionality and continue to realize ROI without having to purchase additional software, modules, features, functions, or bolt-ons at a later date.


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

February 25th, 2010 by admin

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.


Leveraging Your ERP System for Continuous Business Improvement

February 23rd, 2010 by admin

So, you’re an owner of a small to mid-market manufacturing or distribution company. Your business is making a nice profit and you’re pleased with your personal earnings from the venture.  Even so, it’s not time to rest on your laurels and be satisfied with the status quo. Read More…

Every day, there’s someone out there who wants to eat your lunch. It could be an existing competitor who wants to get the upper hand, or it could be someone with a new idea to turn your industry upside down. Whatever the source of the threat, it is real, and it is coming.

Thus, it is imperative to make on-going adjustments in your business for purposes of continuous improvement unless you want to wake up some day to be the person wondering, “What hit me?”’

There are so many manufacturing and distribution businesses we walk into where “that’s just the way we do things around here” is a widely-used term. For example:

  • We always buy substantially more product than we need at the time because we get an additional discount from our supplier.
  • We always have three people sequentially check the same order and its pricing before it is billed so our customers always receive a clean invoice.
  • We couldn’t possibly require the receiving people to record lot numbers because it will hurt their productivity.
  • We allow our customer to buy a full container of product and pay us for it over a twelve month period, even though the customer sells all of the associated product in six months and is using us as their bank for interest-free money for the last six months.
  • We aren’t interested in going out and finding any new customers; we have more than enough business from the two big customers we’re already working with.

These are but five of the countless statements we’ve heard over the past several years about why businesses do quirky things – just because, “that’s the way it’s done here.”

Every day in business is a new opportunity to change old ways and to make improvements that can lead to improved operational efficiencies and customer service.  No one can afford waste in their businesses.  Customers are unwilling to pay a premium for your products to absorb your excess costs because you’re doing things the way they’ve always been done.

You’re encouraged to challenge the norm by setting up continuous improvement teams and rewarding your personnel to cut waste and streamline business processes.  And, assuming you have a high-quality manufacturing or distribution software system in place like Enterprise 21 in which data and metrics are available for ease of access and analysis through fully-integrated decision support and workbench technologies and are working with a software vendor like Technology Group International who is seen as a strategic partner to many customers bringing best-practice experience from working with a myriad of small to mid-market manufacturing and distribution customers, your ERP system can be a key enabler for your company’s continuous improvement efforts.

Technology Group International is such a strong believer in continuous improvement that we perform return on investment (ROI) workshops with our customers some six to twelve months after their initial Go Live with TGI’s Enterprise 21 ERP software. During an ROI workshop, the customer reviews key business practices from across their enterprise and how they’re using Enterprise 21 in those situations.  While there are numerous recommendations as to how the manufacturer or distributor can take better advantage of the software they’ve already bought, some 3-5 key elements tend to emerge for improvement out of the workshop that can help the given manufacturer or distributor derive substantial incremental ROI with the software they’ve already installed.


Food Manufacturing Software: What Software Features Can Improve Product Traceability?

February 16th, 2010 by admin

The Institute of Food Technologists (IFT) recently submitted a report to the FDA that discusses various ways in which food manufacturing software solutions and other technology tools can aid food processors in achieving more comprehensive ingredient and finished good lot traceability. For food manufacturers engaging in an ERP selection project, there are two primary functional requirements an ERP solution must meet to provide the food processor with the ability to track ingredient and finished good lots accurately and efficiently. Read More…

First, an ERP manufacturing software solution must provide both forward and backward lot traceability functionality. The system must be able to track the lot numbers of all ingredients received into inventory, when these ingredients were received, when these ingredients (and their associated lot numbers) were used in manufacturing, the lot numbers of the finished goods that were produced with these ingredient lots, and which of the food processor’s customers were shipped a particular lot number for a finished good. Such functionality gives the organization complete visibility to a particular lot of ingredient from a supplier from receipt into inventory and consumption in manufacturing to finished good shipment to a customer on a specific customer order. In the event of a product recall, system users must be able to generate lot history reports from directly within the ERP system to provide to the FDA and any other regulatory agencies to aid in the recall process.

Click here to watch the Enterprise 21 lot traceability demo.

Secondly, the food manufacturing software solution must deliver a fully-integrated wireless warehouse management system with RF and barcode scanning capabilities. By selecting a manufacturing software solution that provides the organization with the functionality to deploy RF and barcode scanning devices for use in inventory, manufacturing, and shipping operations, food processors can see improvements in ingredient and finished good lot data accuracy. Using such technology, lot codes can be generated automatically and barcodes applied for receipt of ingredients into inventory, finished goods produced and placed into inventory, and finished goods shipped to customers. An employee in the shipping and receiving or manufacturing department would simply scan the barcode and enter the quantity received, produced, or shipped – the system would automatically identify the lot number(s) for the items and store the data, reducing the likelihood of inaccurate ingredient or finished good lot information. As a side benefit, food processors can achieve improvements in overall warehouse productivity as a result of more streamlined picking operations and faster data entry with the use of RF and barcode scanning devices.

By selecting a manufacturing software system with fully-integrated forward and backward lot traceability and wireless warehouse management technology, food processors can strengthen their overall level of ingredient and finished good lot traceability while simultaneously improving ingredient and finished good lot data accuracy.


Wholesale Distribution Software: Leveraging Order Frequency to Increase Sales Revenue and Improve Customer Satisfaction

February 9th, 2010 by admin

Who is your worst customer?  If you are like most wholesale distributors and were to ask this of your inside sales team, they could probably tell you without blinking an eye.  “It’s ‘Fred’ – he’s always complaining and griping.  He just never seems satisfied.”  However, from a management team perspective, ‘Fred’ is a great customer.  He places consistent orders with you at a strong profit margin. Read More…

Does the following scenario sound familiar?  You and your sales team are having a monthly sales meeting.  It’s the middle of the month, and you’re reviewing the sales results for the prior month.

You look at the results and there’s one of your biggest customers – The ABC Company, who typically does $250,000 sales per month – showing last month’s revenue at $30,000.  You wonder what has happened to The ABC Company’s business.  It could be that The ABC Company’s business is slow; however, with this dramatic reduction in order activity, it is quite possible that one of your biggest customers may have gotten sufficiently annoyed with you that they quietly took their business and went elsewhere.

So, is there a way for wholesale distribution software to programmatically help prevent this from happening?  With TGI’s Enterprise 21 ERP software, the answer is absolutely!

Using Enterprise 21’s fully-integrated customer relationship management functionality, a customer order frequency value can be established for each customer.  Let’s say in this example, the order frequency for The ABC Company is set to 10 days.  Should we not receive an order from The ABC Company by the evening of the 10th day from their previous order, the Enterprise 21 system will automatically generate an alert notification to the parties you’ve specified in the system – the sales rep, the CSR, the inside sales rep, etc. – alerting them that this customer has not ordered within normal order frequency and that a follow up call needs to be made to them.

By proactively contacting this customer, you should hear one of three things from The ABC Company:

  1. We have been consuming your product at a slower than usual pace.  We’ll be placing an additional order with you in the next couple of days.
  2. We got busy and forgot to place our order.  You really saved us from getting too low on the stock of your products.  Let’s place an order right now.  We really appreciate you looking out for us.
  3. We were really displeased with how your company handled (fill in the blank) and we have been considering taking our business elsewhere.

In all of these cases, you have the opportunity to positively impact this customer’s satisfaction with your business.  Assuming you have effective problem resolution in place (a topic we’ll address another day – for now, see Service Management), numerous studies have shown that you can achieve higher customer satisfaction levels by resolving customer issues than with those customers who have never experienced any issues with you.

Order frequencies can also be set at a customer-product level, where, for example, some products or classes of products are ordered by a given customer every 10 days while other products or product classes are ordered every 30 days.

So, let’s rewind and go back to the monthly sales meeting.  In this case, The ABC Company has monthly revenue of $240,000 for the month.  When asked why their revenue had fallen off for the previous month, the sales rep can describe the issue that had occurred, how it was resolved, and the customer’s satisfaction with that resolution.  This is a far better scenario than the meeting where The ABC Company’s revenue was $30,000 for the prior month, may be $0 for the following month, and the assigned sales rep is looking for a new job by the next monthly sales meeting.

Nobody likes negative surprises.  And, wholesale distributors running Enterprise 21 will be able to discover and correct customer issues and keep sales revenue high and improve customer satisfaction through the use of Enterprise 21’s CRM software functionality with built-in order frequency features.


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

February 2nd, 2010 by admin

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. Read More…

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.


ERP System Implementation Critical Success Factor: Proper Establishment and Execution of an Implementation Test Plan

January 26th, 2010 by admin

The top three critical factors for a successful ERP implementation are the proper establishment and execution of a training plan, data migration plan, and a comprehensive implementation test plan.  From my experience, the proper establishment and execution of a comprehensive implementation test plan is perhaps the most overlooked of the three plans. Read More…

The test plan needs to be representative of how the company does business as a whole and should include the following:

  • Customer-facing (i.e., quote to cash, customer service, customer self-service);
  • Operational (i.e., demand to pay on the procurement side, inventory management and warehouse operations, manufacturing planning and execution); and
  • Compliance and control (i.e., financial management and reporting, lot traceability, quality management, industry compliance).

Let’s discuss how a company goes about establishing a comprehensive implementation test plan.  The starting point for the creation of a test plan can be to select some 50-100 customer orders out of the existing customer order files at random.  Experienced personnel can review these randomly-selected orders to make sure they collectively establish how the company does business as a whole.  Should there be some nuances that need to be added, specific customer orders meeting those scenarios can be pulled from the files as well and added to the list.

Assuming you did a good job of establishing a software demonstration script during the software evaluation process, the script can be another key input into the test plan creation process.  The test plan should consist of a series of test scenarios which may also be called “use cases.”  Associated with each test scenario would be some narrative about what is being tested, specific data that is to be used in the test, and the expected results of the test.

The test plan should also include some test cases to stress test the system to verify there are no issues with data tables that need to be re-indexed or infrastructure bottlenecks that need to be addressed (network capacity, memory requirements, processor speed, etc.).

The test plan should be executed by functional end user personnel – not just a couple of IT people running through the process by themselves.  There are two key benefits to this process.  First, the functional end users will be aware of nuances that may not have been addressed in the existing test cases.  These process anomalies need to be identified and added to the test plan.  Second, this process reinforces the training functional end users have received to date to verify whether or not additional training is necessary to ensure a smooth go live experience.

The test plan document should include space on each scenario to document the actual results of the test, the names of the individuals who performed the specific test case and the date it was performed, and any pertinent observations made during the test run.  Results should be documented in writing – or electronically – so the results can be shared with the implementation core team consisting of both customer and software vendor personnel and the customer’s executive sponsor.

The test plan should be a living document, which is updated as the business changes over time.
The test plan should be re-executed when a version upgrade is being implemented to validate there are no business processes that have become broken as a result of the upgrade process.

Additionally, a good rule of thumb for ERP software system enhancements is to establish the associated functional test plan or use case for that enhancement at the same time the enhancement is being defined.  This incremental portion of the test plan can be incorporated into the overall test plan.

By effectively establishing and executing of a comprehensive implementation test plan, companies implementing Enterprise 21 can expect their go live experiences to be as smooth as possible with the successful entry, picking, packing, shipping, and invoicing of customer orders day one.


Small Business ERP Total Cost of Ownership: Looking Beyond Upfront and First Year Costs

January 19th, 2010 by admin

One of the most significant hurdles a small business faces in deciding whether or not to migrate to an ERP system is project cost. Generally speaking, the total cost of ERP implementation can be divided into three main categories, including software licensing fees, implementation and training fees, and annual maintenance fees. This third category, annual maintenance, is often overlooked in the software evaluation process. It is imperative that the small business’s selection team consider not only the software vendor’s maintenance fee during implementation but the software vendor’s maintenance fees for the years following implementation (and what is included with such maintenance fees) in order to calculate an estimated five-year total cost of ownership. This five-year total cost of ownership calculation will give the selection team a better view of what the business’s projected cash requirements will be for implementation as well as the years following implementation to determine the most cost-effective long term solution for the organization. Read More…

Many software vendors begin to charge their new customers annual maintenance fees the day contracts are signed. At TGI, we believe charging new customers maintenance fees during ERP implementation is inappropriate. Given that a small business ERP implementation may take anywhere between three and six months, we do not believe a business should have to pay maintenance fees on Enterprise 21 when the software is not yet being used in a live transaction environment – annual maintenance for Enterprise 21 is free for one year from the date of software installation, allowing for a more cost-effective first year of ERP ownership.

Secondly, the business’s selection team should consider each software vendor’s maintenance fees for each year following ERP implementation. Do the software vendor’s fees increase after the first year? Do the vendor’s maintenance fees increase each and every year over time? In addition, two great questions to ask ERP vendors are, “What is your annual maintenance fee today? What was your annual maintenance fee five years ago?” While these two questions may seem inconsequential at first, they are crucial to determining the most cost-effective long term ERP solution for the business. The business does not want to be faced with a situation in which its maintenance fees have doubled in the first three years following ERP implementation. When a given vendor’s new software sales start to slump in times of economic downturn, the easiest way for the vendor to make up for its loss in revenue is to increase its maintenance fees for its existing customers; therefore, it is crucial that the selection team search for an ERP vendor with a track record of consistent, non-escalating maintenance fees over time. At TGI, we are proud to say that we have never increased our annual maintenance fees since the company was founded in 1990.

By analyzing ERP vendors’ total long term solution cost, not just the cost to be incurred during the first year of ERP ownership, the small business will have a more accurate view of its budgetary requirements for the years following implementation and be in a position to determine the most cost-effective long term ERP software solution.


50 Critical Questions to ask ERP Vendors

January 13th, 2010 by admin

When evaluating ERP software solutions, it is imperative to understand the types of questions to ask ERP vendors when considering the that should be asked of each and every ERP vendor being considered. Our 50 Questions for Every ERP Software Supplier white paper in the TGI Resources Library lists 50 questions that are critical to a successful ERP selection project. While finding the best software fit from a functional perspective is of the utmost importance, selection teams need to ask questions geared towards finding an ERP vendor who can deliver the best solution and be a strategic partner for the organization in the long-run as well. Read More…

While the white paper poses 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.

Examples of questions to ask an ERP Vendor:

1. How long has the vendor been in business?

2. Was the software being proposed developed by the vendor, or was it acquired from a third-party?), approach to ERP implementation and customer support (Where is the support team located geographically? Are ERP implementation services delivered directly by the software vendor or by a third party), annual maintenance fees

3. Does the vendor guarantee that their ERP maintenance fees will never increase?), software upgrades

4. Are upgrades included in the vendor’s annual maintenance fee?)

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.