How to Justify a Nesting Software Purchase

Building a Justification for Nesting Software

Building a Justification for Nesting Software

Most project managers we meet tasked with investigating a nesting software purchase inevitably come to the point of making a case – formally or informally – about why the software should be purchased.

The project managers are typically engineers or engineering managers who have first hand experience with the nesting software.  So they are inclined to seek a solution that meets their technical needs – does it work the way I need it to?

However, and as most eventually discover, there is a second line of justification equally important to be addressed.

I’ll break down the two ways to make a case for nesting software here.

There are two ways to justify a nesting software purchase.  Each speaks to a different type of decision maker.  Each is looking at different business from a different perspective.

Technical Justification

The most obvious basis for justification of a nesting software purchase is that of the technical requirements.  The engineers, programmers and potential users are most interested in the features and functions of the nesting software.  Will it do the job they need?  Will it make their lives easier?

  1. Can it perform the function I need?  Creating a nest and generating code.
  2. Can it solve the technical problems I’m having now?  Here are a few, but there are many more.
    1. Dynamic nests
    2. Automatic Order Entry
    3. Automatic Part Entry
    4. JIT Nesting
    5. Automatic Lead Generation
    6. Common Edge Cutting
    7. Reports
  3. Will it improve the speed and/or accuracy of the process?
    1. Order Entry
    2. Part Entry
    3. Nesting
    4. Creating Code
  4. Is it easy to learn?  Easy to use?

Financial Justification

This side of the equation is often overlooked until the technical inspection is complete, which, honestly, is way too late in the game.  These decision makers – the ones who give approvals and sign checks – should be involved at the beginning by setting priorities, establishing means of testing, and looking at how the return on investment will be determined.  They are interested in how the purchase will benefit the company overall.  What kind of financial impact will it have?

Some of the litmus tests used in a financial justification are as follows.

  1.  Material efficiency gains
  2. Programming time reductions
  3. Increased throughput of product
  4. Faster turn-around time for product
  5. Faster or fewer set ups and / or machine changes
  6. Fewer scraped parts due to errors
  7. Less rework
  8. And if JIT is employed, less inventory, faster response to change
For more on financially justifying a project, check out this blog post.

Demonstrations, visits with existing users, benchmarks, and one-on-one discussions are all tools that can be used to build both a technical and a financial justification.

For more on justifying a nesting software purchase contact Optimation.

Notice: This work is licensed under a BY-NC-SA. Permalink: How to Justify a Nesting Software Purchase

Leave a Reply

Your email address will not be published. Required fields are marked *


269,615 Spam Comments Blocked so far by Spam Free Wordpress

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>