« November 2009 | Main | January 2010 »

2 posts from December 2009

12/21/2009

Thinking about Reliability, Durability, and Total Cost of Ownership for Sensors

An important part of our 2009 Position Sensor Study is our structured, in-depth one-on-one interviews with manufacturers of proximity sensors. During one such interview, I became extremely interested in one supplier’s comments around replacement costs.

The manufacturer’s dilemma centered on the problem of selling a higher cost, more reliable sensor in the face of strategically priced lower durability sensors being offered by some competitors. His sensors were priced several times higher than the alternative product but they also had a predicted Mean Time Between Failure (MTBF) almost 10x better.

I say the lower-priced offerings were ‘strategically placed’ for a number of reasons, not least of which is their acute appeal to cash-conservation-focused buyers in most markets.

As a selling point to customers he was using a linear calculation that showed the higher MTBF sensors were a much better value when you calculated the replacement cost it was something like this:

Yearly Cost = (1 year /MTBF) * ((MTTR * (lost production + labor cost)) + sensor cost)

MTTR = Mean Time to Repair

Which translated into X number of events per year * event cost.

When he plugged in the numbers the results were impressively in favor of his sensors. Upon thinking about maintenance events, I was convinced that the costs could be even higher. The linear replacement cost model assumes several things:

* The Maintenance person is immediately available when the fault occurs.
* The Maintenance person is an expert that locates the fault and makes the replacement in a short period of time.
* The sensor in question has a hard failure and does not cause product faults before the event.
* The factory is being 100% utilized.
* The sensor application was in a destructive environment.

The biggest drivers in the calculation were the labor and production costs. The customers might not see the numbers the same way however.
1. If the Maintenance person is on staff, they are already being paid.
2. If the factory is not at 100% utilization, the downtime cost may not be as large as modeled.
Even so, I thought that the assumption of the available repair person was the big one particularly in this economic environment. In most cases, factory staffing has been cut to the minimum. At the same time, companies have been more cautious about adding capacity so with any kind of recovery, production lines will be running nearer their maximum capacity.

If you plug in any randomization and ran a Monte Carlo type simulation, I am confident that you would find some really long downtime events mixed in. This would be particularly true if you modeled the idea of several machines/lines with similar sensor issues. A look at the event / time / cost calculation might be something like this:

Cost per event:

( (Wait for Maint. time + Troubleshoot time + Replace Time) * Lost Production Cost) + Sensor cost.

Each time and the production cost could have a random (normal curve) applied to it. The sensor cost would be fixed. The average number of faults per year would be: (365 x 24) / MTBF

In closing, I thought the best sales case for the manufacturer would be the idea of preventative maintenance. This strategy would be a lot more feasible with the high MTBF sensors. In fact, it moves the maintenance event to “planned downtime” therefore eliminating the loss of production cost. In most production lines there are usually some events where material is not available to be processed. Often these events can be predicted and they are the perfect time to replace sensors that are getting near their predicted lifetime. It can be a very efficient and predictable use of limited factory resources. If you look at it this way, the replacement cost is pretty close to the price of the sensor.

That’s my view of it although I’m sure other people might have other thoughts. If so, drop me an e-mail or give me a call. I would be happy to highlight other theories and models in this space. Stay posted!

Connected Factory Projects are Everybody's Business

The top 10 ranked channel management programs in the Connected Factory market -- application integration and database migration projects in plants and factories -- includes 10 different companies, 10 different business models, and 10 different approaches to the same opportunity.

The top ranked channel/ partner management programs in the Connected Factory markets, as rated by more than 120 integrators in a recent VDC survey include: 

       
  Supplier Score  
       
  Oracle 6.094  
  Accenture 6.038  
  Phoenix Contact 5.688  
  DELL 5.450  
  Cisco Systems 5.413  
  HP 5.363  
  Rockwell 5.306  
  ABB 5.238  
  IBM 5.231  
  Advantech 5.025  
       

Note:  The scale included scores 1 (lowest) to 7 (highest).

This list includes the following groups or segments of suppliers:
1. An ERP vendor
2. 3 of the leading systems integrators in the world (Accenture, HP, IBM)
3. 2 of the leading automation and control solution providers in the world (ABB, Rockwell)
4. 2 of the leading IT hardware vendors in the world (DELL, Cisco) -- 4 if you include HP and IBM
5. 2 of the leading automation enabling technology and subsystem vendors

And within each group or segment, are wide variances in market approaches, lead offerings, and specific channel value-add. 

These results evidence (and our Connected Factory study explores):
1.  The Connected Factory opportunity is available to a number of supplier/ channel communities
2.  It can be accessed through a number of go-to-market strategies and business models
3.  Customers are finding solutions from a diversity of sources
4.  Competition will be intense and multilateral