Browse Prior Art Database

Commodity End of Life Event Integration into Problem Reporting and Service Procedures

IP.com Disclosure Number: IPCOM000246917D
Publication Date: 2016-Jul-14
Document File: 2 page(s) / 24K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for adapting service infrastructure in a system and in service publications to provide information about a commodity part that is at or near the end of useful life without implying a failure of the component.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Commodity End of Life Event Integration into Problem Reporting and Service Procedures

When commodity components reach points at which their expected function or usefulness is near exhausted or exhausted, the system must provide the appropriate warning without implying a part failure which has implications in terms of warranty and service contracts. This article describes the adaptation of existing service infrastructure for notifying clients, service providers, and system suppliers when a commodity component is at or near end of life without framing the notification as a part failure.

    Disclosed is a method for adapting service infrastructure in a system and in service publications to provide information about a commodity part that is at or near the end of useful life without implying a failure of the component. Problem reporting from device firmware, system firmware, licensed internal code, etc., is generally about predictive failure warnings (PFA) or hard failures. There are some commodity parts, such as read intensive solid state drives (SSDs), that report events to indicate they are nearing end of life or at end of life. This situation is not a failure in the componentry. The situation is not a typical predictive failure where conditions in the componentry are experiencing some kind of degradation in performance or capability or capacity that is indicative a failure scenario approaching. Hard failures and PFAs are typically problem reports that list the part identifier, such as the part number, and the part location. That kind of problem report typically triggers behaviors in system code to engage service infrastructure and ties to service documentation. The typical response to that engagement is for the service provider to replace the part.

    For commodities that are designed and sold with an expected progression towards a wear-out end of life, the service policies may vary from normal system parts under warranty or, after warranty runs out, a maintenance contract. Normal parts under warranty or maintenance contract are simply replaced as normal service. However, a commodity part with an expected life that can be less than a similar normal part, for example read intensive SSDs, may be offered under a policy that replaces the part while under warranty but not under a maintenance contract. In that case, the policy for replacement becomes a consideration in the delivery of service.

    The problem is to interrupt or change normal behavior in the system's service infrastructure path and also in the service provider's service delivery process path, which includes service documentation. Those paths must cause the system owner and the service provider to co...