Deprecated: wpml_sticky_post_sync(): Implicitly marking parameter $sitepress as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/inc/functions.php on line 820

Deprecated: WPML\Container\make(): Implicitly marking parameter $args as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/container/functions.php on line 26

Deprecated: WPML\Collect\Support\Arr::first(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/collect/src/Illuminate/Support/Arr.php on line 134

Deprecated: WPML\Collect\Support\Arr::last(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/collect/src/Illuminate/Support/Arr.php on line 163

Deprecated: WPML\Auryn\Injector::__construct(): Implicitly marking parameter $reflector as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/auryn/lib/Injector.php on line 51

Deprecated: WPML\Auryn\Injector::provisionFuncArgs(): Implicitly marking parameter $reflParams as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/auryn/lib/Injector.php on line 447

Deprecated: WPML\Auryn\CachingReflector::__construct(): Implicitly marking parameter $reflector as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/auryn/lib/CachingReflector.php on line 16

Deprecated: WPML\Auryn\CachingReflector::__construct(): Implicitly marking parameter $cache as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/auryn/lib/CachingReflector.php on line 16

Deprecated: WPML_Resolve_Object_Url_Helper::__construct(): Implicitly marking parameter $sitepress as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/class-wpml-resolve-object-url-helper.php on line 37

Deprecated: WPML_Resolve_Object_Url_Helper::__construct(): Implicitly marking parameter $wp_query as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/class-wpml-resolve-object-url-helper.php on line 37

Deprecated: WPML_Resolve_Object_Url_Helper::__construct(): Implicitly marking parameter $wpml_term_translations as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/class-wpml-resolve-object-url-helper.php on line 37

Deprecated: WPML_Resolve_Object_Url_Helper::__construct(): Implicitly marking parameter $wpml_post_translations as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/resolver/class-wpml-resolve-object-url-helper.php on line 37

Deprecated: WPML_URL_Converter_Url_Helper::__construct(): Implicitly marking parameter $wpdb as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/converter/helper/class-wpml-url-converter-url-helper.php on line 24

Deprecated: WPML_URL_Converter_Url_Helper::__construct(): Implicitly marking parameter $wpml_include_url_filter as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/converter/helper/class-wpml-url-converter-url-helper.php on line 24

Deprecated: WPML\Collect\Support\Collection::filter(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/collect/src/Illuminate/Support/Collection.php on line 279

Deprecated: WPML\Collect\Support\Collection::first(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/collect/src/Illuminate/Support/Collection.php on line 384

Deprecated: WPML\Collect\Support\Collection::last(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/collect/src/Illuminate/Support/Collection.php on line 576

Deprecated: WPML\Collect\Support\Collection::sort(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/collect/src/Illuminate/Support/Collection.php on line 995

Deprecated: WPML_Config_Update_Integrator::__construct(): Implicitly marking parameter $worker as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/class-wpml-config-update-integrator.php on line 13

Deprecated: WPML_Absolute_To_Permalinks::__construct(): Implicitly marking parameter $auto_adjust_ids as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/class-wpml-absolute-to-permalinks.php on line 16

Deprecated: WPML\Utils\AutoAdjustIds::__construct(): Implicitly marking parameter $wp as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/utilities/AutoAdjustIds.php on line 22

Deprecated: WPML_Translation_Element_Factory::__construct(): Implicitly marking parameter $wpml_cache as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/translations/class-wpml-translation-element-factory.php on line 18

Deprecated: TranslationManagement::__construct(): Implicitly marking parameter $wpml_cookie as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/inc/translation-management/translation-management.class.php on line 85

Deprecated: WPML_Post_Status_Display_Factory::__construct(): Implicitly marking parameter $sitepress as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/menu/class-wpml-post-status-display-factory.php on line 8

Deprecated: WPML_Canonicals::__construct(): Implicitly marking parameter $wpml_translations as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/canonicals/class-wpml-canonicals.php on line 23

Deprecated: WPML_Compatibility_Gutenberg::__construct(): Implicitly marking parameter $php_functions as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/compatibility/gutenberg/wpml-compatibility-gutenberg.php on line 14

Deprecated: WPML_User_Language::__construct(): Implicitly marking parameter $wpdb as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/user-language/class-wpml-user-language.php on line 37

Deprecated: Creation of dynamic property brozzme_fullwidth_divi::$basename is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/brozzme_fullwidth_divi.php on line 17

Deprecated: Creation of dynamic property brozzme_fullwidth_divi::$directory_path is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/brozzme_fullwidth_divi.php on line 18

Deprecated: Creation of dynamic property brozzme_fullwidth_divi::$directory_url is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/brozzme_fullwidth_divi.php on line 19

Deprecated: Creation of dynamic property brozzme_fullwidth_divi::$plugin_dev_group is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/brozzme_fullwidth_divi.php on line 22

Deprecated: Creation of dynamic property brozzme_fullwidth_divi::$plugin_dev_group_id is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/brozzme_fullwidth_divi.php on line 23

Deprecated: Creation of dynamic property brozzme_fullwidth_divi::$plugin_name is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/brozzme_fullwidth_divi.php on line 26

Deprecated: Creation of dynamic property brozzme_fullwidth_divi::$settings_page_slug is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/brozzme_fullwidth_divi.php on line 27

Deprecated: Creation of dynamic property brozzme_fullwidth_divi::$plugin_version is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/brozzme_fullwidth_divi.php on line 28

Deprecated: Creation of dynamic property brozzme_fullwidth_divi::$plugin_txt_domain is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/brozzme_fullwidth_divi.php on line 29

Deprecated: Creation of dynamic property brozzme_fullwidth_divi_settings::$options is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/includes/brozzme_fullwidth_divi_settings.php on line 14

Deprecated: Creation of dynamic property brozzme_fullwidth_divi_settings::$tools_options is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/includes/brozzme_fullwidth_divi_settings.php on line 15

Deprecated: Creation of dynamic property brozzme_fullwidth_divi_settings::$settings_page_slug is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/includes/brozzme_fullwidth_divi_settings.php on line 17

Deprecated: Creation of dynamic property brozzme_fullwidth_divi_settings::$plugin_text_domain is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/includes/brozzme_fullwidth_divi_settings.php on line 18

Deprecated: Creation of dynamic property brozzme_fullwidth_divi_settings::$plugin_name is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/includes/brozzme_fullwidth_divi_settings.php on line 19

Deprecated: Creation of dynamic property brozzme_fullwidth_divi_core::$options is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/brozzme-fullwidth-divi/includes/brozzme_fullwidth_divi_core.php on line 14

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the et_builder 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 /home/nvpzkhc/testwww/wp-includes/functions.php on line 6131

Deprecated: Return type of JuiceContainer::offsetExists($id) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/nvpzkhc/testwww/wp-content/plugins/quform/library/JuiceContainer.php on line 126

Deprecated: Return type of JuiceContainer::offsetGet($id) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/nvpzkhc/testwww/wp-content/plugins/quform/library/JuiceContainer.php on line 79

Deprecated: Return type of JuiceContainer::offsetSet($id, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/nvpzkhc/testwww/wp-content/plugins/quform/library/JuiceContainer.php on line 46

Deprecated: Return type of JuiceContainer::offsetUnset($id) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/nvpzkhc/testwww/wp-content/plugins/quform/library/JuiceContainer.php on line 136

Deprecated: Automatic conversion of false to array is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/wpml-sticky-links/classes/class-wpml-sticky-links.php on line 19

Deprecated: OTGS_UI_Loader::__construct(): Implicitly marking parameter $locator as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/ui/src/php/OTGS_UI_Loader.php on line 22

Deprecated: OTGS_UI_Loader::__construct(): Implicitly marking parameter $assets as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/otgs/ui/src/php/OTGS_UI_Loader.php on line 22

Deprecated: WPML_ST_Upgrade::__construct(): Implicitly marking parameter $command_factory as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/wpml-string-translation/classes/upgrade/class-wpml-st-upgrade.php on line 42

Deprecated: WPML\ST\TranslationFile\UpdateHooks::__construct(): Implicitly marking parameter $resetDomainsCache as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/wpml-string-translation/classes/translation-files/UpdateHooks.php on line 26

Deprecated: WPML\ST\MO\Hooks\CustomTextDomains::__construct(): Implicitly marking parameter $syncMissingFile as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/CustomTextDomains.php on line 29

Deprecated: WPML_Package_Translation::loaded(): Implicitly marking parameter $sitepress as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/wpml-string-translation/inc/package-translation/inc/wpml-package-translation.class.php on line 13

Deprecated: WPML_ST_Package_Factory::__construct(): Implicitly marking parameter $cache_factory as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/wpml-string-translation/inc/package-translation/inc/wpml-package-factory.class.php on line 8

Deprecated: WPML_File::__construct(): Implicitly marking parameter $wp_api as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/class-wpml-file.php on line 32

Deprecated: WPML_File::__construct(): Implicitly marking parameter $filesystem as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/class-wpml-file.php on line 32

Deprecated: WPML\LIB\WP\User::hasCap(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wp/classes/User.php on line 191

Deprecated: WPML\LIB\WP\User::canManageTranslations(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wp/classes/User.php on line 202

Deprecated: WPML\LIB\WP\User::canManageOptions(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wp/classes/User.php on line 212

Deprecated: WPML\LIB\WP\User::isAdministrator(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wp/classes/User.php on line 221

Deprecated: WPML\LIB\WP\User::isEditor(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wp/classes/User.php on line 230

Deprecated: WPML\LIB\WP\User::isTranslator(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wp/classes/User.php on line 244

Deprecated: WPML_Language_Switcher::__construct(): Implicitly marking parameter $dependencies as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/language-switcher/class-wpml-language-switcher.php on line 19

Deprecated: WPML_LS_Templates::__construct(): Implicitly marking parameter $wpml_file as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/language-switcher/class-wpml-ls-templates.php on line 25

Deprecated: WPML_LS_Public_API::__construct(): Implicitly marking parameter $slot_factory as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/language-switcher/public-api/class-wpml-ls-public-api.php on line 27

Deprecated: WPML_TM_Word_Count_Refresh_Hooks::__construct(): Implicitly marking parameter $st_package_factory as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/words-count/hooks/wpml-tm-word-count-refresh-hooks.php on line 21

Deprecated: WPML_Upgrade_Command_Factory::create_command_definition(): Implicitly marking parameter $factory_method as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/upgrade/class-wpml-upgrade-command-factory.php on line 13

Deprecated: WPML\ST\Batch\Translation\Module::batchStringsStorage(): Implicitly marking parameter $saveBatch as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/wpml-string-translation/classes/batch-translation/Module.php on line 87

Deprecated: WPML\ST\Batch\Translation\Records::get(): Implicitly marking parameter $wpdb as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/wpml-string-translation/classes/batch-translation/Records.php on line 39

Deprecated: Quform::date(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/quform/library/Quform.php on line 6038

Deprecated: Quform::date(): Implicitly marking parameter $timezone as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/quform/library/Quform.php on line 6038

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the quform 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 /home/nvpzkhc/testwww/wp-includes/functions.php on line 6131

Deprecated: WPML_PB_Shortcode_Strategy::register_strings_in_content(): Implicitly marking parameter $stringCleanUp as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/addons/wpml-page-builders/classes/Shared/st/strategy/shortcode/class-wpml-pb-shortcode-strategy.php on line 119

Deprecated: WPML\BlockEditor\Blocks\LanguageSwitcher\Repository::__construct(): Implicitly marking parameter $dependencies as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/block-editor/Blocks/LanguageSwitcher/Repository.php on line 13

Deprecated: WPML\UIPage::isSettings(): Implicitly marking parameter $get as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/core-api/core/UIPage.php on line 86

Deprecated: WPML\UIPage::isMainSettingsTab(): Implicitly marking parameter $get as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/core-api/core/UIPage.php on line 101

Deprecated: WPML\UIPage::isNotificationSettingsTab(): Implicitly marking parameter $get as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/core-api/core/UIPage.php on line 110

Deprecated: WPML\UIPage::isCustomXMLConfigSettingsTab(): Implicitly marking parameter $get as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/core-api/core/UIPage.php on line 119

Deprecated: WPML\UIPage::isSettingTab(): Implicitly marking parameter $get as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/core-api/core/UIPage.php on line 130

Deprecated: WPML_Integrations_Requirements::__construct(): Implicitly marking parameter $third_party_dependencies as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/requirements/class-wpml-integrations-requirements.php on line 41

Deprecated: WPML_Integrations_Requirements::__construct(): Implicitly marking parameter $requirements_notification as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/requirements/class-wpml-integrations-requirements.php on line 41

Deprecated: Creation of dynamic property wpml_cms_nav_cache::$name is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/wpml-cms-nav/inc/cache.class.php on line 36

Deprecated: Creation of dynamic property wpml_cms_nav_cache::$cache_to_option is deprecated in /home/nvpzkhc/testwww/wp-content/plugins/wpml-cms-nav/inc/cache.class.php on line 37

Deprecated: WPML_Upgrade_Command_Definition::__construct(): Implicitly marking parameter $factory_method as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/upgrade/class-wpml-upgrade-command-definition.php on line 25

Deprecated: WPML_Upgrade::__construct(): Implicitly marking parameter $command_status as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/upgrade/class-wpml-upgrade.php on line 34

Warning: Constant COOKIE_DOMAIN already defined in /home/nvpzkhc/testwww/wp-config.php on line 112

Deprecated: WPML_URL_Converter_CPT::__construct(): Implicitly marking parameter $slash_helper as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/converter/class-wpml-url-converter-cpt.php on line 12

Deprecated: WPML_Menu_Element::__construct(): Implicitly marking parameter $wpml_cache as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/translations/class-wpml-menu-element.php on line 15

Deprecated: WPML_Term_Element::__construct(): Implicitly marking parameter $wpml_cache as nullable is deprecated, the explicit nullable type must be used instead in /home/nvpzkhc/testwww/wp-content/plugins/sitepress-multilingual-cms/classes/translations/class-wpml-term-element.php on line 18
[On parle de nous] « Comment garantir le ROI de sa maintenance prédictive » - WATTECO

Pour atteindre au plus vite un retour sur investissement, avoir l’adhésion des équipes et une bonne disponibilité des données sont des prérequis indispensables.

Point de départ de tout projet de maintenance prédictive : le ROI. Ce critère du retour sur investissement est « essentiel pour les industriels », explique Pierre Savary, responsable commercial chez le fabricant français de capteurs IoT nke Watteco, qui a racheté à son homologue Eolane la business-unit dédiée au capteur de maintenance prédictive Bob assistant. Car le coût d’un projet peut freiner certains dirigeants, en représentant un budget moyen « de 15 à 30 euros par capteur et par mois pour l’analyse vibratoire d’une pompe », par exemple en intégrant l’amortissement du capteur, le cout de la connectivité et l’accès à une solution applicative. Selon une étude OnePoll réalisée en février 2021 pour le fabricant allemand Reichelt Elektronik, 29% des entreprises françaises sondées hésitent à adopter la maintenance prédictive en raison de contraintes budgétaires. « Le coût est néanmoins très variable, il dépend du métier, de son avancée technologique et de sa capacité à intégrer les outils », poursuit Pierre Savary.

Pourtant, si le ROI est la première préoccupation des industriels, le calculer avant la mise en place d’une solution IoT se révèle impossible. « Il ne suffit pas de se baser sur le coût du service annuel et de faire un POC pour voir si la technologie fonctionne », prévient Pierre Savary, pour qui la valeur d’un projet de maintenance prédictive ne peut s’estimer qu’en effectuant un pilote d’envergure pour évaluer comment les process peuvent être changés.

Pour réussir et rentabiliser son projet, le premier conseil de David Dorval, PDG et fondateur de Stimio, société nantaise spécialisée dans la fourniture de solutions connectées pour l’industrie, est de trouver un usage pertinent, c’est à dire pour lequel adopter la maintenance prédictive a un réel impact. « Dans le ferroviaire, cela peut être un équipement destiné au grand public, par exemple les portes d’un train pour éviter qu’elles ne se bloquent », précise le PDG, qui va monitorer d’ici 2025 plus de 20 000 capteurs pour la SNCF. Un avis partagé par Fabien Treillaud, directeur commercial chez l’entreprise d’origine britannique de maintenance prédictive Senseye, qui monitore plus de 20 000 équipements dans le monde.

« La maintenance prédictive ne convient pas à tous les équipements, il faut qu’il y ait des conséquences importantes d’une panne sur la production. Ainsi, la maintenance prédictive est particulièrement adaptée pour la métallurgie, l’automobile ou encore la gestion de biens comme les ascenseurs. »

Deuxième étape : identifier les bonnes données. Il est nécessaire de disposer des informations pertinentes au bon moment. « Le coût de la captation des données peut casser certains ROI, il faut que les directeurs de maintenance sachent exactement quelles pièces tombent les plus souvent en panne », met en garde Stéphane Roder, PDG et fondateur de la société de conseil en stratégie data AI Builders. Cela implique pour l’équipe de maintenance prédictive de « travailler avec le CDO de l’entreprise pour rassembler les data de manière transverse et anticiper », conseille de son côté Sébastien Wallet, directeur du département IoT chez Artefact, agence-conseil spécialisée en data et intelligence artificielle. L’un des prérequis est ainsi une bonne adhésion des équipes.

De nombreux KPI à suivre

Lors du déploiement, Pierre Savary, de nke Watteco, rappelle que si équiper une seule machine critique peut se révéler efficace, les économies d’échelle ne sont pas à négliger. « Plus de capteurs sont déployés, plus l’investissement est amorti car mettre en place une infrastructure réseau pour trois capteurs est plus compliqué à rentabiliser que pour des milliers. » C’est la raison pour laquelle Senseye recommande de démarrer avec 50 à 100 équipements minimum.

Le projet lancé, une multitude de facteurs entrent en jeu. Le premier concerne les arrêts des machines, en comparant le taux de panne évité par la maintenance prédictive. « Dans le ferroviaire, éviter des incidents induits des économies de centaines de milliers voire de millions d’euros. Par exemple, 5% des locomotives d’un parc en moyenne auront un incident sur un caténaire par an, revenant pour chacun à près de 100 000 euros. Anticiper ces incidents est donc un enjeu important », raconte David Dorval, de Stimio. Mais il n’est pas le seul. « Il faut aussi prendre en compte les gains de temps en déplacement si les machines sont situées dans des zones difficile d’accès, tout comme le gain de temps concernant la commande de pièces, l’évolution des contrats de maintenance, la prolongation de la durée de vie des machines, etc. », souligne Pierre Savary. Bosch, qui a connecté 120 000 contrôleurs de machines et 250 000 dispositifs dans ses usines, a réduit ses coûts de maintenance de 25%.

Dans le ferroviaire, le ROI est atteint entre 12 et 36 mois, indique David Dorval. Dans l’industrie 4.0, notamment pour la surveillance de pompes, le ROI est inférieur à un an. « Dans de nombreux cas, il peut être atteint en trois mois », assure Fabien Treillaud, de Senseye, en citant l’exemple du constructeur automobile Nissan. Plus de 9 000 équipements connectés de 30 types de machines différents (des convoyeurs, des élévateurs, des pompes, des moteurs et des presses, ndrl) sont surveillés à distance par Senseye, ce qui a permis de réduire les temps d’arrêt de production jusqu’à 50% et économiser ainsi plusieurs millions de dollars en temps d’arrêt imprévus.

Pour encourager les industriels à vérifier les bénéfices de la maintenance prédictive, Senseye a lancé en décembre 2020 une offre en partenariat avec l’assureur Scor, ROI Lock, afin de garantir un remboursement du coût d’abonnement si les économies réalisées en évitant les arrêts machines imprévus sont inférieurs au coût dudit abonnement dans un délai d’un an. De son côté, nke Watteco renforce ses partenariats avec des intégrateurs pour s’adresser aux PME, qui ont encore peu déployé des solutions de maintenance prédictive et constitue le gros du marché, selon Pierre Savary. Stimio rappelle que la maintenance du matériel roulant représente à elle seule un marché de 7 milliards d’euros par an en Europe.

Source : ©Le Journal du Net 14 avril 2021

Consultez l’article sur le site Le Journal du Net « Comment garantir le ROI de sa maintenance »