Deprecated: ElementorProDeps\DI\create(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/functions.php on line 32

Deprecated: ElementorProDeps\DI\autowire(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/functions.php on line 44

Deprecated: ElementorDeps\DI\create(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/functions.php on line 32

Deprecated: ElementorDeps\DI\autowire(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/functions.php on line 44

Deprecated: ElementorDeps\DI\ContainerBuilder::writeProxiesToFile(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/ContainerBuilder.php on line 231

Deprecated: ElementorDeps\DI\Definition\Source\ReflectionBasedAutowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/Source/ReflectionBasedAutowiring.php on line 17

Deprecated: ElementorDeps\DI\Definition\Source\Autowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/Source/Autowiring.php on line 21

Deprecated: ElementorDeps\DI\Definition\Source\DefinitionFile::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionFile.php on line 25

Deprecated: ElementorDeps\DI\Definition\Source\DefinitionArray::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionArray.php on line 33

Deprecated: ElementorDeps\DI\Definition\Source\DefinitionNormalizer::normalizeRootDefinition(): Implicitly marking parameter $wildcardsReplacements as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionNormalizer.php on line 42

Deprecated: ElementorDeps\DI\Proxy\ProxyFactory::__construct(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Proxy/ProxyFactory.php on line 38

Deprecated: ElementorDeps\DI\Container::__construct(): Implicitly marking parameter $definitionSource as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Container.php on line 87

Deprecated: ElementorDeps\DI\Container::__construct(): Implicitly marking parameter $proxyFactory as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Container.php on line 87

Deprecated: ElementorDeps\DI\Container::__construct(): Implicitly marking parameter $wrapperContainer as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Container.php on line 87

Deprecated: ActionScheduler_Store::save_action(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Store.php on line 29

Deprecated: ActionScheduler_Store::stake_claim(): Implicitly marking parameter $before_date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Store.php on line 188

Deprecated: ActionScheduler_Store::get_scheduled_date_string(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Store.php on line 257

Deprecated: ActionScheduler_Store::get_scheduled_date_string_local(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Store.php on line 274

Deprecated: ActionScheduler_DBStore::save_unique_action(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 55

Deprecated: ActionScheduler_DBStore::save_action(): Implicitly marking parameter $scheduled_date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 68

Deprecated: ActionScheduler_DBStore::save_action_to_db(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 82

Deprecated: ActionScheduler_DBStore::stake_claim(): Implicitly marking parameter $before_date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 795

Deprecated: ActionScheduler_DBStore::claim_actions(): Implicitly marking parameter $before_date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 860

Deprecated: ActionScheduler_Logger::log(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Logger.php on line 28

Deprecated: ActionScheduler_Logger::log_failed_fetch_action(): Implicitly marking parameter $exception as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Logger.php on line 142

Deprecated: ActionScheduler_DBLogger::log(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBLogger.php on line 21

Deprecated: ActionScheduler_QueueRunner::__construct(): Implicitly marking parameter $store as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php on line 39

Deprecated: ActionScheduler_QueueRunner::__construct(): Implicitly marking parameter $monitor as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php on line 39

Deprecated: ActionScheduler_QueueRunner::__construct(): Implicitly marking parameter $cleaner as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php on line 39

Deprecated: ActionScheduler_QueueRunner::__construct(): Implicitly marking parameter $async_request as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php on line 39

Deprecated: ActionScheduler_Abstract_QueueRunner::__construct(): Implicitly marking parameter $store as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php on line 34

Deprecated: ActionScheduler_Abstract_QueueRunner::__construct(): Implicitly marking parameter $monitor as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php on line 34

Deprecated: ActionScheduler_Abstract_QueueRunner::__construct(): Implicitly marking parameter $cleaner as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php on line 34

Deprecated: ActionScheduler_QueueCleaner::__construct(): Implicitly marking parameter $store as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueCleaner.php on line 35

Deprecated: ElementorProDeps\DI\ContainerBuilder::writeProxiesToFile(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/ContainerBuilder.php on line 231

Deprecated: ElementorProDeps\DI\Definition\Source\ReflectionBasedAutowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/ReflectionBasedAutowiring.php on line 17

Deprecated: ElementorProDeps\DI\Definition\Source\Autowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/Autowiring.php on line 21

Deprecated: ElementorProDeps\DI\Definition\Source\DefinitionFile::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionFile.php on line 25

Deprecated: ElementorProDeps\DI\Definition\Source\DefinitionArray::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionArray.php on line 33

Deprecated: ElementorProDeps\DI\Definition\Source\DefinitionNormalizer::normalizeRootDefinition(): Implicitly marking parameter $wildcardsReplacements as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionNormalizer.php on line 42

Deprecated: ElementorProDeps\DI\Proxy\ProxyFactory::__construct(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Proxy/ProxyFactory.php on line 38

Deprecated: ElementorProDeps\DI\Container::__construct(): Implicitly marking parameter $definitionSource as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Container.php on line 87

Deprecated: ElementorProDeps\DI\Container::__construct(): Implicitly marking parameter $proxyFactory as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Container.php on line 87

Deprecated: ElementorProDeps\DI\Container::__construct(): Implicitly marking parameter $wrapperContainer as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Container.php on line 87

Deprecated: WPMailSMTP\Queue\Queue::count_processed_emails(): Implicitly marking parameter $since_datetime as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/wp-mail-smtp/src/Queue/Queue.php on line 305

Deprecated: Elementor\Controls_Stack::get_active_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/base/controls-stack.php on line 352

Deprecated: Elementor\Controls_Stack::get_active_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/base/controls-stack.php on line 352

Deprecated: Elementor\Controls_Stack::get_style_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/base/controls-stack.php on line 799

Deprecated: Elementor\Controls_Stack::get_style_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/base/controls-stack.php on line 799

Deprecated: Elementor\Elements_Manager::create_element_instance(): Implicitly marking parameter $element_type as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/managers/elements.php on line 70

Deprecated: Elementor\Element_Base::__construct(): Implicitly marking parameter $args as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/base/element-base.php on line 1569

Deprecated: Elementor\Repeater::__construct(): Implicitly marking parameter $args as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/elements/repeater.php on line 49

Deprecated: Elementor\Core\Utils\Collection::filter(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/core/utils/collection.php on line 43

Deprecated: ElementorDeps\DI\Definition\ObjectDefinition::__construct(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 62

Deprecated: ElementorDeps\DI\Definition\ObjectDefinition::setClassName(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 75

Deprecated: ElementorDeps\DI\Definition\ObjectDefinition::setLazy(): Implicitly marking parameter $lazy as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 158

Deprecated: ElementorDeps\DI\Definition\Resolver\ObjectCreator::setPrivatePropertyValue(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ObjectCreator.php on line 158

Deprecated: ElementorDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34

Deprecated: ElementorDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $method as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34

Deprecated: ElementorProDeps\DI\Definition\ObjectDefinition::__construct(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 62

Deprecated: ElementorProDeps\DI\Definition\ObjectDefinition::setClassName(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 75

Deprecated: ElementorProDeps\DI\Definition\ObjectDefinition::setLazy(): Implicitly marking parameter $lazy as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 158

Deprecated: ElementorProDeps\DI\Definition\Resolver\ObjectCreator::setPrivatePropertyValue(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ObjectCreator.php on line 158

Deprecated: ElementorProDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34

Deprecated: ElementorProDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $method as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34

Deprecated: ElementorPro\Modules\Forms\Submissions\Actions\Save_To_Database::save_action_log(): Implicitly marking parameter $exception as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/modules/forms/submissions/actions/save-to-database.php on line 159

Deprecated: {closure:ElementorPro\Modules\Forms\Submissions\Actions\Save_To_Database::__construct():193}(): Implicitly marking parameter $exception as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/modules/forms/submissions/actions/save-to-database.php on line 193

Deprecated: Duplicator\Controllers\StoragePageController::getEditUrl(): Implicitly marking parameter $storage as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/duplicator-pro/src/Controllers/StoragePageController.php on line 106
Re-Modelling Sustainment Strategy for Legacy Platforms: A Case for Condition-Based Maintenance – Think Ahead.
Deprecated: Elementor\Core\Files\CSS\Post::add_controls_stack_style_rules(): Implicitly marking parameter $all_controls as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/core/files/css/post.php on line 221

Deprecated: Elementor\Core\Files\CSS\Base::add_controls_stack_style_rules(): Implicitly marking parameter $all_controls as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/core/files/css/base.php on line 552

Deprecated: Elementor\Core\Files\CSS\Base::get_active_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/core/files/css/base.php on line 921

Deprecated: Elementor\Core\Files\CSS\Base::get_active_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/core/files/css/base.php on line 921

Deprecated: Elementor\Core\Files\CSS\Base::get_style_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/core/files/css/base.php on line 949

Deprecated: Elementor\Core\Files\CSS\Base::get_style_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/core/files/css/base.php on line 949

Deprecated: Elementor\Core\DynamicTags\Dynamic_CSS::add_controls_stack_style_rules(): Implicitly marking parameter $all_controls as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/core/dynamic-tags/dynamic-css.php on line 104

Deprecated: Elementor\Stylesheet::add_rules(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/stylesheet.php on line 141

Deprecated: Elementor\Includes\Elements\Container::__construct(): Implicitly marking parameter $args as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/elements/container.php on line 42

Deprecated: Elementor\Includes\Widgets\Traits\Button_Trait::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/widgets/traits/button-trait.php on line 517

Deprecated: Elementor\Includes\Widgets\Traits\Button_Trait::render_text(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor/includes/widgets/traits/button-trait.php on line 648

Deprecated: ElementorPro\Modules\Posts\Traits\Button_Widget_Trait::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/modules/posts/traits/button-widget-trait.php on line 491

Deprecated: ElementorPro\Modules\Carousel\Widgets\Media_Carousel::print_slider(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/modules/carousel/widgets/media-carousel.php on line 305

Deprecated: ElementorPro\Modules\Carousel\Widgets\Base::print_slider(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/modules/carousel/widgets/base.php on line 579

Deprecated: ElementorPro\Modules\Payments\Widgets\Paypal_Button::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/modules/payments/widgets/paypal-button.php on line 225

Deprecated: ElementorPro\Modules\Payments\Classes\Payment_Button::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/modules/payments/classes/payment-button.php on line 499

Deprecated: ElementorPro\Modules\Payments\Widgets\Stripe_Button::render_button(): Implicitly marking parameter $instance as nullable is deprecated, the explicit nullable type must be used instead in /home/spps/public_html/wp-content/plugins/elementor-pro/modules/payments/widgets/stripe-button.php on line 249

Re-Modelling Sustainment Strategy for Legacy Platforms: A Case for Condition-Based Maintenance

Condition-based maintenance holds the key for resolving the inefficiencies of manual, labor-intensive and time-consuming models currently used to deliver asset availability

Sustainment Needs for Efficiency

Defense platforms have advanced to become complex system-of-systems, utilizing hundreds of technologies and suppliers spread across increasingly globalized supply chains.  Military users have gained numerous operational advantages from these advancements, mainly as platforms have been progressively developed with multi-role characteristics and modular architectures to allow for faster reconfigurations or updates. But these advanced capabilities have come at steeply higher costs for military users with each new generation of equipment, not only at the point of acquisition but also – and in particular – when considering life-cycle costs.

The through-life sustainment of defense platforms has presented complex challenges to militaries, which have struggled to overcome these strategically. Steep growth in per unit costs of high-end platforms has translated into the capitalization of smaller operational inventories, leading to user requirements for higher asset availability. Moreover, despite the need to reduce downtime for defense platforms that users are more reliant on than ever, their inherent complexity has typically translated into extended maintenance and repair turnaround times simply because there is a lot more that can go wrong and does go wrong.

Another limiting factor in these scenarios is the technician skill levels needed to maintain and repair high-end defense platforms and the training, tools, and infrastructure required to execute these tasks. These challenges have often meant that for military users, the unavailability of assets can multiply in unexpected ways leading to growing backlogs, extended downtime, and increasing costs – all at the same time, even. As a result, more innovative, more efficient models are needed to sustain legacy platforms, particularly the maintenance, repair, and overhaul (MRO) of equipment that must have high availability to service routine training and operations.

Smart Technologies and Automation

Condition-Based Maintenance (CBM), which exploits real-time data to prioritize and optimize maintenance resources as and when needs arise, holds the key to allowing military users to resolve the inefficiencies of manual, labor-intensive, and time-consuming models currently used to deliver asset availability. Rooted in the condition-based monitoring of assets through vibration, infrared, acoustic, electrical, pressure, and oil analysis, CBM proposes tools, techniques, and methods to ascertain the real-time health of assets and make predictions about their performance.

By scientifically understanding how different components degrade during operations, it is possible to schedule inspections, repairs, and overhauls at appropriate intervals so that any incipient failure can be detected in advance. A mix of data collected continuously or at predetermined intervals using sensors, visual inspections, operational and maintenance data, and scheduled tests can help predict equipment failure before it occurs and help track the remaining useful life (RUL) of life-limited parts. This continuous monitoring is possible non-invasively or without changing how assets are operated – saving time and labor costs on manual inspections.

By scientifically understanding how different components degrade during operations, it is possible to schedule inspections, repairs, and overhauls at appropriate intervals so that any incipient failure can be detected in advance.

Manual inspections routinely require the removal and reinstallation of structures, contributing to wear and tear, damage, and deterioration of assets over their lifespan. Periodic inspections are therefore replaced by automated “continuous” inspections using sensors and analytics to detect imminent failures and predict degradation issues more economically and efficiently. Using CBM, maintenance and repair work becomes essential only after one or more indicators show equipment is likely to fail or that equipment performance is deteriorating. By utilizing real-time operational and maintenance data, operators can yield gains such as:

      • Detection of failures earlier and before they occur

      • Reduced costs of breakdown, unplanned downtime, and labor hours

      • Fixing failures only when they are needed

      • Increased throughput and time between maintenance

      • Increased asset availability for operators

      • Optimized inventories for emergency spare parts, and

      • Extended platform lifespans as a result of slower asset deterioration

    Human Factors are Decisive

    In short, CBM promises improved operational availability and optimized maintenance at once. However, the move to sustainment models utilizing CBMmusto be balanced by reliability so that equipment and operator safety is not compromised. This is less the case for new-generation platforms developed with built-in health monitoring systems. However, vast inventories of legacy platforms currently in operational service were designed by original equipment manufacturers (OEMs) without condition-based monitoring systems. It is here that the most significant performance challenge lies in the sustainment of defense platforms.

    Including more CBM functions in maintenance, repair, and overhaul (MRO) requires close coordination between regulatory authorities, OEMs, and MRO service providers to move to develop smarter sustainment models and maintenance schedules. In addition, for the cost of new resources to be amortized by the potentials savings offered by CBM, low-cost, rapidly deployable toolkits for analytics, prognostics, knowledge management, and actionable intelligence that can lead to the earlier detection of faults and imminent failures, reduced timelines for troubleshooting and improved asset availability are essential.

    Despite intelligent technologies and automation being the key enabler for condition-based maintenance, its practical implementation goes beyond sensor technologies and software.

    Technical teams responsible for the sustainment and MRO of assets must be adequately trained and educated on concepts related to CBM – from the different types of condition monitoring methods, tools, and techniques, and their benefits, to the pitfalls and risks of not collecting and logging data as it is required to achieve the desired results. The viability of CBM models hinges on limiting user error. It will necessarily require buy-in throughout the value chain, encompassing operators, maintenance technicians, inventory managers, and the regulatory authorities which certify equipment safety and worthiness. Despite smart technologies and automation being the key enabler for condition-based maintenance, its practical implementation goes beyond sensor technologies and software.

    © 2022. All rights reserved.

    Disclaimer: The views and opinions expressed in this publication are designed to provide an objective analysis. This analysis does not constitute professional advice. Release: This publication may be reproduced, including photocopying, recording, or other electronic or mechanical methods, and quotations embodied in or for the purpose of critical reviews, academic work and certain other non-commercial uses permitted by copyright law, for which a standard source credit to the author and the publisher (SPPS) is included. All inquiries should be made to the publisher (SPPS) by email on contact@spps.ae


     


    Deprecated: Constant E_STRICT is deprecated in /home/spps/public_html/wp-content/plugins/elementor/core/logger/manager.php on line 250