Accurate Data + Thorough Analysis + Effective Action = Fewer FOD IncidentsWherever aerospace products are manufactured or flown, a philosophy and culture of FOD Prevention spanning the entire operation is vital to assure product integrity, reliability, and cost savings. The exact costs of FOD can be hard to quantify because the “ripple effect” of even a minor incident affects many areas. While man-hours, component costs, personal injury or death are measurable, reduced customer confidence and lost business are nearly impossible to determine. We know that implementation of an aggressive, well-structured FOD Prevention Program recently saved one aircraft component manufacturer over one million dollars in a single year and contributed significantly to increased sales. Your FOD Prevention Program will bring you countless benefits. There are many elements to an effective FOD Prevention Program:
- Management Support
- Process Controls/Procedures
- Worker Involvement
- Motivation and Incentives
- Corrective Action/ Root Cause Identification
Accurate information is a major step toward arresting the villain: FOD.Without it other elements of your FOD Prevention Program may be misguided, and a waste of valuable time and resources. To develop a database that provides the necessary tracking requires forethought and planning but is easily managed using a desktop computer with spreadsheet (e.g., Excel) capability. Determining the key data elements to track, who will collect the data, input and retrieve it, what formats are desired and who will receive/act on the information are all parts of the planning. The goal is to produce reports/charts in simple, usable language.
If Data isn’t understood, it is useless.Management may want to see trends, set goals and recognize excellence. Supervisors and workers need specific information about problems within their units. Individual reports may be required to analyze a specific problem or gauge effectiveness of a corrective measure. Therefore, different reports may be required from the same database. Once familiar with the procedure, you will find these FOD Program Information Reports surprisingly simple to produce.
Remember: the purpose of your data is to identify problems and implement lasting solutions.
Sources of Data
Audits & InspectionsRandom daily checks of work and operations areas will assure compliance to standards, regulations or procedures. Develop an audit checklist that documents the date/time, auditor, shift, area and problem found. Use codes when possible to reduce the auditor’s time, ease data entry, and facilitate and standardize sorting the data for reports.
Incident ReportsFOD incidents (operational problems and system/component failures directly related to FOD) must be documented and investigated. An Incident Report form is used to document the problem and the findings. Enter information from the report into the FOD database to provide tracking/trending.
Customer FeedbackProducts delivered to the customer are expected to be FOD free. If a customer discovers FOD in the product, immediately communicate with the source to implement corrective measures. Some manufacturers send a form or letter accompanying the delivered product requesting a feedback report detailing the description and location of any FOD found. A timely follow-up report to the customer affirming the corrective actions taken to avoid recurrence is good business practice. Again, the key data elements from the customer’s feedback report should be recorded in the FOD database.
FOD DatabaseUsing Excel, set up a spreadsheet to record all the data elements to be tracked. Consistency and uniformity of codes used is vital for accurate sorting of the data when producing reports. Begin collecting data for a trial period before establishing the FOD database to assure that all the elements desired are included.
Charts & ReportsAfter the FOD database is established, data may be sorted on any of the parameters desired. Using Chart Wizard in the Excel program, select the chart type that best suits the type of report to be produced.
Corrective ActionProblem resolution/corrective action is dependent upon identification of the root cause (primary contributor). Therefore, information tracked in the FOD database must be as specific as possible to facilitate investigation. Root cause is sometimes difficult to determine and often intimidates the department and/or individual(s) that may be the origin of the FOD problem. Two techniques that help the investigator overcome these problems are the “Fishbone” and the “Five Whys.” The Fishbone is a graphic breakdown of contributing factors to a problem. “The Five Whys” has been used by researchers for many years to analyze casual factors to complex problems. Generally, if all five stages of asking “why” to a problem are answered with conviction, the root cause will reveal itself. The “Fishbone” and “Five Whys” should be completed by the investigator for each incident or grouping of similar findings and reviewed/approved by management or a Corrective Action Board.
A Corrective Action Plan based on the root cause should be developed to avoid recurrence of the problem. The Corrective Action Plan plots the planned steps or individual activity planned and assigns target dates for completion. A problem history should accompany the plan.Ideally, a CAB (Corrective Action Board) will be established to review Corrective Action Plans and track problems to resolution. Convene this Board on a weekly or monthly basis to review progress/completion of Corrective Action Plans, problems encountered by investigators and / or action coordinators, and problem recurrences. A formal review emphasizes the importance of solving FOD problems and validates/approves the initial plan and closure action. Periodic communication of the Board’s functions to all levels will remind everyone of the commitment to FOD Prevention.