This article was published as a part of the Data Science Blogathon.
The automotive industry has mobilized the economy for decades. In the Automobile industry, the value chain starts at Inbound Logistics (raw material, warehouse) Production (Operation), Marketing and Sales, Maintenance (Service) given the Car design, vendors, the process is already ready.
Though Data science is used at all levels in this value chain like optimization the schedule, transportation optimization, inventory management, workforce optimization, process optimization, and process control, targeting the right audience for the right segment of car, today I will be describing more on Maintenance or Warranty period analytics use case I have worked on.
After-sales, automobiles get post-sale services from dealers. A warranty analysis is mainly based on the data collected from those services, claims over a certain period.
In the Warranty Analysis typically Gamma, Weibull, or lognormal Distribution is observed for the failure of the product over the period.
A warranty analysis is the analysis of time-to-event/failure data. In our example, the individual part is followed from the car sold time to its failure.
As in typical model building, we split the data into train and test datasets. With the training data, we first estimate the parameters of the distribution, and then using test data, we see if the model fitted works well on that data or not.
Gamma: The probability density function (pdf) of the Gamma distribution can be expressed as:
with α >0 and β >0 and x ≥0.
This also means it has two parameters, alpha– which represents the shape parameter, and beta- which represents the scale parameter, and its support consists only of positive values.
In Gamma distribution, using all xi ‘s, and using Maximum likelihood estimates, I estimated the α and β for each item(spare part in analysis). But I observed that Gamma distribution when fitted on test data, the actual time to fail was not close to the predicted time to fail by model for that item. So I discarded the Gamma Distribution approaches.
Weibull: The probability density function (pdf) of the Weibull distribution can be expressed as:
with α >0 and β >0 and 0 < x < ∞
This means, it has two parameters, alpha– which represents the shape parameter, and beta- which represents the scale parameter, and its support consists only of positive values.
Again here using the maximum likelihood estimate for each spare item’s data I estimated α and β and tested with test data. The accuracy of the time to fail for each item was on test data with the estimated α and β for all items were in acceptance criteria. and hence all the items of cars were modeling using Weibull distribution. For each item, I had different α and β, and all those models were stored for scoring purposes for the future.
The scenarios under which conditions the car is driven, driver’s driving skills, the age of the part are a few of the parameters of which some can be measured, and some are qualitative. And hence the modeling of the item failure needs to be done on a large amount of data. Else model will have a bias from the modeling data and the accuracy of the model will drop over the period of deployment /implementation.
Challenges: Typical challenges would be the accuracy and timeliness of data, the length of historical data, the number of parts to be modeled, and model selection based on accuracy on testing data. In my analysis I had the last two challenges due to the reasons like the car will have 1000’s of items in it and the model which fits best for one item may not fit well for another item.
Solution: There are many research papers that have explained this problem, mentioned the three distribution is way forward. To the problem, I was solving Weibull distribution fit well to all the part items. Once that is fit, testing data should support the model chosen and once that is done, I developed the process so that each item is modeled, and its scoring function is stored in such a way that periodically the forecast of failures per item is generated.
Once this solution is implemented in the business process, every month, manufactures will have an estimate of which items and their count he needs to be ready with for possible warranty claims. This enables saving in customer wait time for parts to be available, better inventory management, reduction in the cost of unnecessary storage of non-required parts and check on fraudulent warranty claims too.
Conclusion: For every manufacturer, warranty analytics can solve the following problems:
The benefits of the warranty analytics are:
It can also help answers the questions like:
This article summarizes the background, solution approach, and benefit for Warranty analytics which is a very big industry due to the increase in the sale and competition in the automobile market.
The media shown in this article are not owned by Analytics Vidhya and is used at the Author’s discretion.
Step-by-Step Exploratory Data Analysis (EDA) us...
Top 10 Data Analytics Projects with Source Codes
Application of AI in Predictive Maintenance of ...
What is Predictive Analytics | An Introductory ...
Cross Sell Prediction : Solution to Analytics V...
Playing Data with Statistics
Solving Accuracy vs. Cost using probabilities (...
Top Customer Analytics Interview Questions
Is survival analysis the right model for you?
A Comprehensive guide to Parametric Survival An...
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s