Why all these IMMI updates all the time?

Yet another IMMI update, again with bug fixes and corrections ... Many a user might annoyedly ask WHY. After all, IMMI has been under continuous development for many years by a competent development team, right?

Error-free software – does it exist?

Every serious software development must have the goal of delivering error-free products. However, in the case of complex software, practice teaches that this goal cannot be achieved with one hundred percent certainty, despite all efforts at quality assurance. Every now and then, errors – some of them well hidden – creep into the thousands and thousands of lines of software code and then suddenly are detected. Countless studies on software projects and daily experience in dealing with products used millions of times bear witness to this.

Of course, IMMI is no different. Whenever such an error is detected in the software, it is classified in terms of its importance. If in the most serious case it affects the calculation result, it is brought to the attention of our users as soon as possible and corrected with an unscheduled update. Errors that do not affect the results are collected and eliminated with the next scheduled update of the software – along with the addition of performance features.

IMMI is not always "at fault”

In many cases, however, the software itself is not "to blame" for changes and corrections. IMMI implements rules and regulations, and these are often subject to change. Of course, once such a regulation is published, the IMMI user expects it to be implemented in the software without delay so that they can apply it. However, gaps in the interpretation of the regulations are often only discovered after publication, then discussed, and filled by expert committees – such as the NALS Special Committee "Quality Assurance of Software" or the NALS Expert Group "Sound Propagation". Test items that test for special situations or supplementary notes are published for this purpose only after a certain period of time. Thus, weeks or months may pass until the procedure is finally clarified and can be taken into account in the software.

Practical examples: RLS-19 and CNOSSOS for noise mapping

Current examples of such "late findings" are the RLS-19 or the national implementation of CNOSSOS for noise mapping:

  • With the amendment of the 16th BImSchV, the "Traffic Noise Abatement Ordinance", on November 4, 2020, the "new" RLS-19 (Guidelines for Noise Abatement on Roads – 2019 Edition) applies. Only in the course of 2021, individual interpretation gaps were closed and corresponding test tasks were decided by the expert committees, for example, in dealing with parking lots or in the concrete application of the reflection criterion with double reflection. They will be published as DIN/TR 8999-1.
  • The same applies to the national implementation of CNOSSOS for noise mapping in the form of the calculation method for environmental noise from ground sources (roads, railroads, industry, and commerce) – BUB or BUF (aircraft noise) and BEB (analysis of persons affected). The latest amendment to these calculation regulations became official with the establishment of the 34th BImSchV on October 5, 2021, and includes, for example, modified tables as input data for the determination of emissions. Correspondingly adapted test tasks for determining emissions from roads, railroads, industry, and commerce are in progress and will appear as DIN/TR 8999-2 to -4, but have not yet been published. Here, too, changes may still be made if necessary.

As soon as the software development department is sure or officially has received such adaptations, they are implemented and lead to a software update that is delivered to the users as quickly as possible.

Always up to date with a maintenance contract

In many cases, it is not IMMI itself that is the cause of the necessary updates, but rather a changed or "corrected" regulatory situation. It's a good thing to have a maintenance contract as an IMMI user! Please contact us for further information.

Share this article on LinkedIn