Originally Posted by SLO_Town
Originally Posted by StevieC
Whatever I can see in a UOA is really it. Would love to dissemble the engine to take measurements and inspect but that's not going to happen.
Your desire to tear down and engine explains why it is important to use a certified oil that was formally tested using all the proper protocols and methodologies. The certification reports have standards for wear and deposit weights. Here are the ACEA standards:
https://www.acea.be/uploads/news_documents/ACEA_European_oil_sequences_2016.pdf
When a blender makes ambiguous claims that their oil "meets" or is "suitable", they most certainly have not followed all the proper testing protocols and methodologies.
Scott
PS StevieC, in another thread you said you sell machines worth more than a house. In my long, 30 career I mathematically modeled and tested the performance of large, very expensive, mission critical, mainframe computers during their development process. "Cooking numbers" to overlook deficiencies was a common temptation for a variety of reasons - technical obstacles and shortcomings of the system being tested, project deadlines, internal political pressure (!!!), industry pressure, etc. It is my belief that blenders of "uncertified" oils cook numbers for the very same reasons. It's the only way they can get their oil to "pass". In my business, thank God we didn't have organizations like the ACEA overseeing our work. In many cases the performance of our systems would never have been fully "approved" or "certified" because there were areas where the performance goals were not met.
Scott- that is part of my current job, but in my case it is for a large cloud provider. I have had numerous cases where our internal organization or the vendor "certified" that it would meet certain performance goals, only to find out in QA testing that it cannot meet those goals. In looking back at the certification, I find that they either fudged the numbers, or the test was accidentally run under slightly different criteria that does not match our use case. Sort of like claiming that your car can hit 200 in a full speed test run, only to find out that they meant 200 kph when you needed 200 mph.