Recommended procedure

The aim is to develop the basics for the decision-makers and to present them in an appealing way. It is highly recommended to proceed according to a concept. The more structured the procedure and the more transparent the design of the evaluation, the greater the chance that the result and the resulting decision will be understood and supported by all those involved.

We recommend assessment according to the “magic triangle”.

Magic triangle displaying the selection criteria risk, costs, and benefits.

The risk assessment should show how business-critical the labeling process is.

  • How many products are labeled with the process?
  • How many people use the process?
  • What happens if the process fails?
  • How many systems are involved?
  • How is availability ensured?

A clear and comprehensible risk assessment is essential for every decision-maker.

As a rule, the benefit is determined by means of a utility value analysis. One danger here is that errors or an inadequate approach can lead to incorrect results. The more criteria are taken into account, the greater the risk that essential criteria cannot be adequately distinguished from non-essential criteria.

Payback / Return on Investment (ROI)

Calculating the payback period or return on investment (ROI) regularly proves to be very useful. The difficulty in this approach lies in determining the costs, as many are not directly available.

Total Cost of Ownership (TCO)

We find this approach useful when a decision has to be made between very different IT infrastructures or license models. For example, SaaS (Software as a Service) versus subscription or an on-premise model.

Investment considerations

Investment considerations

An assessment regarding the investment in an LBM is both simple and very difficult:

  • Simply because, in our experience, the “payback period” has proven to be a very pragmatic approach.
  • Difficult, as the costs of the labeling processes to be replaced are usually not transparently available for calculating the payback (hidden costs). These hidden costs must be derived so that an adequate payback can be calculated.

Costs of all operational hours spent on labeling.

Potential: 50%

Digitization and automation eliminates the need for administration and control (overhead) as well as manual selection of label templates and filling in data for the print job.

A product recall is certainly one of the most costly mistakes that can occur in a company. If the error on the label concerns identification or traceability, the damage is even greater.

Any manual intervention in the selection of the label layout or data determination doubles the risk of this occurring.

Errors that are noticed before delivery lead to unplanned additional costs and often delay delivery.

Analyses of production and packaging often reveal that labeling efforts are inadequately mapped and are often responsible for delays. Delays in labeling can be reduced with an efficient process.

Faults that cannot be rectified during operations and do not require recalls become quality cases. A quality manager usually has to find the cause of the defect and take measures to avoid it in the future. Companies that do not have access to historical print data usually bear the high costs of processing the quality case without being able to determine the exact cause.

Poor system availability, fluctuating network stability and a lack of replacement processes mean production downtime and delivery delays.

If customers have special labeling requirements, such as a private label, which cannot be implemented with the previous labeling system, opportunity costs can also arise due to lost business opportunities.

Companies that have to carry out a visual inspection again after marking or have to release parts from the marking process in other systems or manually also have hidden costs in the process here.

What counts here is the effort required to implement new requirements. Here, the number of people implementing a change and the number of system interfaces are the cost drivers.

Dollar bill in water on a fishing hook as a symbol for the hidden costs

Tipp zur Ermittlung von versteckten Kosten

A problem tree analysis helps to identify hidden costs, but also to create and interpret the benefit analysis.

  1. First identify the three most important “pain points” in your existing process. If you find out, for example, that these are quality, time and costs, you are in good company.
  2. Enter these pain points in a problem tree model under Problem.
  3. Determine the cause and effect of each problem.

Tip for determining hidden costs

A problem tree analysis helps to identify hidden costs, but also to create and interpret the benefit analysis.

  1. First identify the three most important “pain points” in your existing process. If you find out, for example, that these are quality, time and costs, you are in good company.
  2. Enter these pain points in a problem tree model under Problem.
  3. Determine the cause and effect of each problem.

Calculation of ROI and payback

Payback is nothing other than the reciprocal value of the return on investment (ROI).

Mathematic equations for return on investment and payback.

Return

The return represents all the savings you achieve with the new LBM. To do this, you need to go through all operational and hidden costs and make an estimate of the savings. For example, if you save one minute per print job and you carry out 1 million print jobs per year, you have a return of one million euros (assuming 1 minute = 1 euro).

Investment

The investment is the sum of all expenses. This includes project, license and maintenance costs. Infrastructure costs such as server rental can also be included. We recommend only including the additional servers, as otherwise the servers of the old system should be added back to the “return”.

Utility value analysis

In most cases, there is not enough time to present the results of a benefit analysis in detail to the decision-makers. For this reason, it is important to limit yourself to the essential points of the benefit analysis. The following points should be addressed:

  • Who determined the selection criteria and how?
  • Who evaluated and how?
  • Who weighted and how?
Presentation of the results from a benefits analysis with a spider web diagram.

Tipp für die Gliederung von Kriterien

Think about grouping the requirements. This makes it easier to present and discuss the results of the analysis at the end. Example of a grouping:

  • Functional designer requirements
  • Functional management requirements
  • Safety requirement
  • Performance requirements
  • Fulfillment of the killer criteria
  • Special functionalities

Tipp zur Bewertung der Anforderungen

A scale of 1-10 is often used when assessing the requirements. Our opinion on this is that it is very difficult to evaluate with such a scale. We advocate a scale of just 0-3:

0: Requirement is not fulfilled
1: Requirement can only be fulfilled via a workaround
2: Requirement is fulfilled, but could be done better
3: Request is fulfilled as desired

With this scale, there is much less discussion about the grading. As there is no middle ground, you have to decide for each function whether it is sufficient or not.

Tip for structuring criteria

Think about grouping the requirements. This makes it easier to present and discuss the results of the analysis at the end. Example of a grouping:

  • Functional designer requirements
  • Functional management requirements
  • Safety requirement
  • Performance requirements
  • Fulfillment of the killer criteria
  • Special functionalities

Tip for evaluating the requirements

A scale of 1-10 is often used when assessing the requirements. Our opinion on this is that it is very difficult to evaluate with such a scale. We advocate a scale of just 0-3:

0: Requirement is not fulfilled
1: Requirement can only be fulfilled via a workaround
2: Requirement is fulfilled, but could be done better
3: Request is fulfilled as desired

With this scale, there is much less discussion about the grading. As there is no middle ground, you have to decide for each function whether it is sufficient or not.

Tipp zur Gewichtung der Resultate

The weighting of requirements can be used to control practically any desired result. For this reason, it is important to be particularly careful here if you do not want to gamble away your credibility. In our opinion, there are only two possible approaches to avoid mistakes here:

  • No weighting of all requirements. With this approach, care should be taken to ensure that the requirements make a similarly significant contribution to achieving the objective.
  • Weighting of the requirements. If this approach is chosen, then each requirement must be compared individually with all other requirements and the weighting calculated accordingly.

The weighting of the requirements usually does not contribute to transparency and a simple overview.

Tip for weighting the results

The weighting of requirements can be used to control practically any desired result. For this reason, it is important to be particularly careful here if you do not want to gamble away your credibility. In our opinion, there are only two possible approaches to avoid mistakes here:

  • No weighting of all requirements. With this approach, care should be taken to ensure that the requirements make a similarly significant contribution to achieving the objective.
  • Weighting of the requirements. If this approach is chosen, then each requirement must be compared individually with all other requirements and the weighting calculated accordingly.

The weighting of the requirements usually does not contribute to transparency and a simple overview.

Do you have questions about evaluating an LBM?

We will be happy to help you evaluate the right solution for you. We also have templates in Excel and PowerPoint that we will be happy to provide you with.

Show me modern SAP integration








    Show me modern SAP integration








      About the author:

      Urs Bartholdi Product Manager and Compliance Officer OPAL LABELMANAGEMENT

      Urs Bartholdi

      Produkt Manager & Compliance Officer

      The Product Manager of OPAL Professional Service and with OPAL Associates AG since 2018. He was already there at the birth of OPAL LABELMANAGEMENT on the customer side, which is why his DNA can also be found in the product.

      Did you like the article?
      Share it with just one click.