Thursday, August 18, 2011

Biofouling–A life of its own.

Is your system ready to take on a new life? Many technology solutions require clean water for their process. In the semiconductor industry, ultra-high purity water is a must with extreme deionization of water. Residential water heaters even have problems with scaling, and many of the high-efficiency tankless systems cannot be installed in areas with hard water.

Scaling issues with calcium and magnesium are commonly on the mind of a system developer maybe because it is something we experience everyday. On the other hand, biofouling is not always considered until it is too late. Much like scaling, once biofouling starts it may be impossible to treat, control or recover from the growth.

In system testing, it is common to set specifications for the end user and test for the environment that is readily available. Water quality around the world is not equal.

Crazy_Red_BugA Tale of Two Microbes

A problem was experienced when multiple systems tested in the Boston Massachusetts area over several years had no indication of problems with water except for hardness, which was treated with standard filtration and ion exchange materials. A major market was a well developed European country. The problem started with system overheating that required a tweak to the cooling pump curves every few months to keep the system operational. When a shutdown occurred and the system

Tuesday, August 16, 2011

Process Temperature Sensitivity

Temperature sensitivity of processes should be considered early in the design before specifying equipment. Frequently, designers specify a single thermal measurement device for ease of use, replacement, and inventory. Not a bad idea if all temperaturTemperature_Displayes are near the same range or the process is not sensitive. K-Type thermocouples are very popular due to their wide range of temperatures (-200˚C to 1250˚C), but when measuring high temps of 1000˚C and water temperatures around 50˚C what is the error associated with them?

Many designers do not realize that an error even exists and even process interfaces and data files will be set up with one or two decimal places. The standard error of a K-Type thermocouple is a minimum of 2.2˚C and at temperatures nearing 1000˚C the error nears 7˚C. So with even a 4.4 degree spread on error, reading temperatures in tenths of a degree is useless, requires more data-storage  space and adds irrelevant

Wednesday, July 20, 2011

Design for Usability–Computer Design Failure

According to research performed by Deliotte, 2012 will be the year to exceed 1 billion computers produced annually. With 500 million units shipped in 2009 you would think that the computer industry would have things fairly well worked out for design, but do they? Consumer usability is always an issue and frequently overlooked. Take a few new cars for test drives and you are bound to say “I really don’t like where that thing is placed.”

computer faceHere is a PC that is just a few years old.

Look at the power switch.

It seems that every time a disc is placed in the lower drive the computer shuts down and needs to be rebooted. Sometimes when the headset cords are plugged in, a wild finger will cause a reboot. It also happens when installing or removing a thumb drive in the USB port. Very frustrating to have your system shut down from attempting normal use.

Yes, the computer

Friday, June 24, 2011

Design for X (DfX), Excellence or ‘X’ as a Variable?

“When you say DfX or Design for X, is the ‘X’ intended to be for "’excellence’ or the use of X as a variable as used in an algebraic equation?’” This question was asked of me when explaining what I do. “Well, it is dependent on the person you ask or where you look for the definition. If you use it as a variable it should cover the term ‘excellence' as well as any other term you want to use. Let’s go with ‘X’ as a variable.” was my response.

Regardless of the term you use for ‘X’ there are certain realities that are inescapable. If a system cannot  be

Monday, April 11, 2011

Failures and Unintended Component Applications

Extending the limits and the specification boundaries of components is common in innovative environments, as often a standard component does not exist yet for a new technology.  In this case, a pump designed to deliver low temperature liquids was used in an application due to its specified flow curve, operating pressures, and cost. The vendor specification did not

Monday, April 4, 2011

Compressor Filter Failure

This small compressor has a filter located on the upper port. The function of this compressor was critical to system operation and life time. Several systems using these compressors ran well for long periods, but ultimately a unit failed.  The post mortem analysis discovered a small piece of material in the outlet Compressor_Filtervalve, and further investigation showed degradation of the filter material.
What went wrong? The filter, in this application, was being used was an exhaust filter designed for outbound flow., while the original configuration of the compressor was to be used as a vacuum pump. The person specifying the filter was unaware that the default setting set by the vendor was as a vacuum pump, nor that one filter could be configured in two ways. could be configured in more than one way.  
Prior to this failure, another problem plagued the system: an orifice manifold located near a hot entry point was being clogged with small brown chucks of material that were thought to be reversing through the system when the compressor was not running. The clogged orifice caused severe operating problems and resulted in the degradation and reduced the life expectancy of a downstream component nearly one quarter of the total system cost. The system was redesigned with expensive check valves to eliminate the reverse flow situation. After the compressor filter was found to be an issue, testing of old orifice was found to contain melted fibers from the filter and not material from back-flow.  That same filter caused these problems as well.
Concurrent engineering practices that involve persons who understand the consequences of even the simplest failures can reduce errors like this. The proper use of tools such as an FMEA may have identified this as a potential failure, but required a person knowledgeable enough to identify it. The FMEA in this case identified the compressor as a component and did not take the filter itself into consideration. It is critical to involve the right people early in the process to reduce failures and hidden lifecycle costs Blogger Labels: Case Study,FMEA,Compressor,Filter,Failure
.

Wednesday, March 30, 2011

A Breakdown in Communication

A communications cable was manufactured by a custom cable and harness supply house, and due to use, the housing had been removed along with the heat shrink so as to expose the blue and white wires.  What was visible is that the white wire on this cable is exposed; what you could not see was a single strand from the white wire hovering dangerously close to the blue wire. As the system vibration frequency changed within operation modes, the close proximity of the blue and white wires would cause an intermittent fault.  The result of the fault, considered by itself, was not too severe: the system shut down.  The resulting system-wide damage was costly, however, due to the thermal stress of multiple shutdowns.  Additionally customer perception declined quickly.COM_Cable_1

The failure is in the design, rather than in the manufacturer. The cable specified a wire gauge too large for the connector, causing the close proximity of the blue and white wires. An off-the-shelf bulkhead connector was specified due to cost and availability, while a custom design with smaller gauge wires would have cost more initially, it would have saved service time, product life, and customer perception.  How could the team have chosen the correct connector up front? Manufacturing drawings, tied together with an electrical design review, could have brought this problem to light prior to deployment.  While the hardware cost for the correct connectors was $100, compared to $5.00 for the bulkhead connectors, the overall cost of using the bulkhead connectors exceeded $8,000 due to travel expenses, service engineer cost and the cost of the software development tool to detect the problem.  The frustration level of the customer was elevated enough to call off the installation of another system Blogger Labels: case study,Failures,Breakdown,Communication,system
.

Monday, March 28, 2011

Prototype Contract Technicalities

From early on the thought is to secure customers; otherwise, why go into business? When the first advanced prototype is approaching completion, the anticipation of putting a demo unit in the field builds. Sales or management go out with a list of prospects to secure a demonstration partner. The specifications that were developed with goals for the system are discussed and some considerations are made of the prototype’s capabilities, but sales, and management want to find a site, and the developers are

Friday, March 25, 2011

Customer Expectation

Frequently, understanding customers’ needs and expectations can be difficult. Sometimes identifying the actual customer is misunderstood and even overlooked. Identifying target markets is critical. Exploring all avenues at the onset of the project and eliminating the least favorable ones is better than attempting to focus on only one or two markets. Designs will be made with some knowledge of alternative markets in mind, even if they are not the target. Finding the best fit and then attempting to recover with redesigns is costly.

Exploring a large list of potential markets might consume more time in the beginning, but will identify additional opportunities and reduce affects if the market shifts.

Performing voice-of-the-customer (VOC) data collection helps to identify customers’ wants, but something that a customer has not experienced is merely an expression of someone else’s experience and does not truly reflect the customer’s needs. Experience with similar products enables customers to express their expectations, but identifying potential customers’ needs and expectations requires some additional analysis to apply the information gained to the design specifications. Start with a good list and eliminate the outliers, focus on the major issues, and keep in mind the questionable items. The remaining items become a list of potential features down the road.

Blogger Labels: Voice of the customer,VOC,Customer

Tuesday, February 1, 2011

Management of Field Replaceable Units (FRU)

For the inventory controller, manufacturing, and document change control, field replaceable units (FRUs) are evil. Added SKUs, additional space requirements, documentation management, and possible disruptions to normal manufacturing flow are problems. To the field service personnel, the FRU is a time saving, frustration reducing, wonderful thing, when configured properly. When considering equipment that demands high availability, FRUs can effectively reduce

Thursday, January 6, 2011

Key Elements of Choosing a Product Development Process

A question that is frequently asked is “What product development process should we follow?” There is no single answer, but to say “It depends.” There are several product development process (PDP) models available: Spiral, Waterfall, StageGate™. Both iterative and linear methods to choose from. Linear methods that do not incorporate concurrent engineering practices are dead. The need for speed to move to the top or maintain your position is required in defining a good PDP.
There are a few things that are elemental to developing and executing a good process. Investors like The Fundable Entrepreneur point out;

Wednesday, January 5, 2011

Smart Phones for Reliability and Field Operation Data

Over the years as a field service engineering manager, I created several databases and applications to reliably collect operations and failure data for FRACAS (failure reporting analysis and corrective action system) from engineers and operators in the field. Commercial FRACAS systems are great for analyzing data and collecting the “big” failures, but the

Tuesday, January 4, 2011

Ford and Chrysler start out 2011 with recalls

At Chrysler, nearly 145,000 trucks and crossover vehicles are being recalled for three different issues; Airbags, steering issues and noisy rear axles. A CNN report initially calls the axle problem a stalling issue then states it is an axle bearing problem that may cause the vehicle noise or failure. Another report at DailyFinance states that the axle may seize causing a crash. A very different view of the reported potential outcomes.
The Ford body control module (BCM) installed in the Super Duty Trucks, Edge, and Lincoln MKX were found to be defective when two F-150 trucks caught fire

Sunday, January 2, 2011

Where it begins

Welcome to the new blog of Applied Product Development Solutions.

The thought of blogging on something like reliability and product development was not promising at first. When someone told me that I should start a blog, I told them that many will find it boring and no one would want to read it. “You like it and you have a lot of good info to share,” I was told. So we started discussing what I could write about.

Out came the pen and the napkin from under my coffee cup. The interface between a tiny ink coated ball and formed fibers from a dead tree is often the place where thoughts are transformed to the physical world. The ideas are captured to communicate to others or remind ourselves of the past.

IdeasPic

Most endeavors require a good plan. However, on a summer weekend, I jump on the motorcycle and drive through to back roads with no particular destination. Often finding great food, nice people, and odd places that results in the statement “that was a good ride.”

Let’s see where this ride takes us.