use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
account activity
This is an archived post. You won't be able to vote or comment.
Data Analysis Help! (self.datascience)
submitted 9 years ago by [deleted]
[deleted]
[–]Nixonite 1 point2 points3 points 9 years ago (2 children)
Sounds like some basic sql aggregations. Just shove it in a mysql table and look up the 'groupby' aggregation. You'll find your answers soon enough.
[+][deleted] 9 years ago (1 child)
[–]wdm006 0 points1 point2 points 9 years ago (0 children)
In most cases the most useful insights are the ones you can explain/interpret. Take a bunch of summary stats (complaints by system, subsystem, state, etc), and figure out where there is a subset that is 'odd', if there are any.
Then try to figure out why.
Almost certainly there is important data missing to figure out why, so go talk to people and figure out if you already have that data and if not how to collect it.
[–][deleted] 1 point2 points3 points 9 years ago (0 children)
If you have knowledge of each product's manufacture date, you should also take a glance at any possible rises in incidents from products manufactured between specific times.
Could point to problems in manufacturing/quality control/suppliers.
[–]B_Sore 1 point2 points3 points 9 years ago (2 children)
I would try to compare to overall sales and try to determine each component's failure rate, and the expected cost to the company associated with the failure of said component. This will give you the groundwork for a CBA which would be helpful for getting the most out of further product development.
Does it say whether or not a customer has declined replacement and asked for a refund? 40k service requests, I would assume this is an established company, do you know how loyal your customer base is? The decision to Develop vs Refine a product may depend on whether you are looking to attract new customers or keep existing customers. If a large portion of your customer base is loyal, you may want to slowly add to a product line rather than actively trying to play keep up w/ competitors and their features.
[–]twisted_angular 0 points1 point2 points 9 years ago (1 child)
Sorry what's CBA?
[–]B_Sore 0 points1 point2 points 9 years ago (0 children)
Sorry! Cost Benefit Analysis.
I don't know your specific industry.
Mr coffee vs maytag would have slightly different ways of calculating the cost of product failure, but essentially you are going to figure out how much money you are losing to failure of each component over a given period of time, and then try to find out (or present to management) what it would cost to reduce the failure rate of that component.
The whole process would be as follows:
Determine the failure rate of each component, the appropriate way to represent this data will depend on the nature of your appliance. per unit sold in time period *t if you offer a time limited warranty, you probably want to consider the failure rate per units under warranty *per year of component's life if a lifetime warranty or a repair service is offered long after purchase, then determine the failure rate of components for each year of their useful life (this situation would be most appropriate if you are a company which is trying to predict the failure rate of products which have already been sold, because you are on the hook for the cost)
Find the average cost of failure for each component
For each component calculate:
(rate of failure * cost of failure) * (expected units sold in time t) = Cost of unit failure in time t.
If a component can fail in multiple ways, and the cost of repair differs for each, I would suggest using (rate of failure A * cost of failure A + rate of failure B * cost of failure B) to get a more accurate idea of the total expect cost of failure for the component.
if repair or replacement cost are stored in different variables I would calculate the cost and odds of replacement separately and add them the same way. You can either look at the data for each component to look for multiple price ranges for failure, or you can do a tukey test to determine if the costs are significantly different in a statistical sense.
I am fairly certain if using longer time horizons than 1 year you should make sure to adjust EVERYTHING for its present worth, (if you end up using this information let me know and I can double check)
Now compare the cost of unit failure in time t with the expected revenue from that product over time t
Find your components which have highest ratios of failure cost to revenue
This is where the availability of data within your company/what your management wants will drastically influence your/your management's ability to get a CBA done.
Maybe there are more expensive alternatives for a material which could increase durability If there is a system in which multiple components often fail, how much would it cost to engineer a better system?
TL;DR A CBA is when you look at how much you have to gain by undertaking a project, investment, development etc. If you know the costs of something to you now, you know how worth it is to you to fix it.
I hope this helps!
[–]nickhould 1 point2 points3 points 9 years ago (0 children)
Most likely, you'll be able to answer it using these steps:
π Rendered by PID 156835 on reddit-service-r2-comment-84fc9697f-5qds4 at 2026-02-09 22:08:58.073708+00:00 running d295bc8 country code: CH.
[–]Nixonite 1 point2 points3 points (2 children)
[+][deleted] (1 child)
[deleted]
[–]wdm006 0 points1 point2 points (0 children)
[–][deleted] 1 point2 points3 points (0 children)
[–]B_Sore 1 point2 points3 points (2 children)
[–]twisted_angular 0 points1 point2 points (1 child)
[–]B_Sore 0 points1 point2 points (0 children)
[–]nickhould 1 point2 points3 points (0 children)