Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ga-google-analytics domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/clients/client1/web2/web/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/clients/client1/web2/web/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the antispam-bee domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/clients/client1/web2/web/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/clients/client1/web2/web/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the translatepress-multilingual domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/clients/client1/web2/web/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/clients/client1/web2/web/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the simple-history domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/clients/client1/web2/web/wp-includes/functions.php on line 6131
Audimus setzt den nächsten Benchmark! - Audimus Consulting

Audimus setzt den nächsten Benchmark!

By Audimus ConsultingIn NewsPosted 7. January 20210 Comment(s)

Audimus hat in der Zwischenzeit bei zwei Kunden den Audimus FMEA Designer hocheffizient und erfolgreich eingeführt.

Ein Kunde aus dem Bereich Kontraktlogistik mit OEM nahen Standorten konnte in nur 7 Tagen einen vollständigen Prozess FMEA zu 100 % konform nach neuem harmonisiertem Stand erstellen und mit den zufriedenen Kunden eine Review unterziehen.

Bis zum Jahresende hat Audimus ebenfalls bei einem deutschen Stahlhersteller den Prozess FMEA mit dem neuen Audimus FMEA Designer abgeschlossen. Hier wurde innerhalb von nur 12 Arbeitstagen in mehreren kleinen Teams die Herstellung von Stahlböcken und Stäben in einer bisher unerreichten Detailtiefe dargestellt.

Die direkte Verknüpfung der Merkmale zu bekannten und standardisierten Ausfallgründen wurde über eine Filtercodierung mit eingebracht

Das Ergebnis: In der Problemlösung können nur per Knopfdruck alle potenziellen Ursachenelemente aus dem gesamten Herstellprozess angezeigt werden.