FOE Implementation Basic Process

Slides:



Advertisements
Similar presentations
Define the Scope of Work Long and short term schedules Schedules broken into reasonable tasks Tasks well defined in eList Proof of worker involvement in.
Advertisements

Hosted By: Atlanta, Ga. National Aerospace FOD Prevention, Inc. 25th National Aerospace FOD Prevention Conference 27 – 29 July 2004 Co-hosted By: Delta.
COM Operating Personnel Communications Protocols
Automated Software Testing: Test Execution and Review Amritha Muralidharan (axm16u)
Configuration Management Main issues:  manage items during software life cycle  usually supported by powerful tools.
ISHIKAWA DIAGRAM – Tool for quality management Marit Laos IS Project Management
School Name Here 2010 NECAP Science Test Administrator Workshop.
SAE AS9100 Quality Systems - Aerospace Model for Quality Assurance
Foreign Object Elimination (FOE) Program
Software Quality Engineering Roadmap
Software Configuration Management
Copyright 2006 Northrop Grumman Corporation 0 March 6-9, 2006 Diane Mizukami (Williams) Northrop Grumman Designing Your Tailoring.
Best Practices – Overview
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
Supply Chain Management Handbook (SCMH) Foreign Object Debris (FOD) Guidance Material Overview October
1 Change Management FOR University Medical Group Saint Louis University Click this icon for Audio.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 18 Maintaining.
Network security policy: best practices
Elements of Internal Controls Preventing Fraud, Waste, and Abuse in Urban and Rural Transit Systems.
What is Business Analysis Planning & Monitoring?
Software Project Management
S/W Project Management
Introduction to Software Quality Assurance (SQA)
Lisa Wood, CISA, CBRM, CBRA Compliance Auditor, Cyber Security
© 2012 IBM Corporation Rational Insight | Back to Basis Series Documents and Record Control Liu Xue Ning.
Basics of OHSAS Occupational Health & Safety Management System
Applied Technology Services, Inc. Your Partner in Technology Applied Technology Services, Inc. Your Partner in Technology.
Software Quality Assurance Activities
1 Test Security and Integrity of the Testing Program Mark Billingsley TSNAP Vice-President Austin ISD.
Section Five: Security Inspections and Reviews Note: All classified markings contained within this presentation are for training purposes only.
Summary of Assessment Reports and Gap Analysis
Unit 7: Demobilization, Transfer of Command, and Closeout
Hazards Identification and Risk Assessment
The Audit as a Management Tool Vermont State Auditor’s Office – April 2009.
Risk Management & Corporate Governance 1. What is Risk?  Risk arises from uncertainty; but all uncertainties do not carry risk.  Possibility of an unfavorable.
© Mahindra Satyam 2009 Risk Management QMS Training.
Foreign Object Debris (FOD) Proposal Karen Iftikhar.
Project management Topic 1 Project management principles.
Configuration Management Main issues:  manage items during software life cycle  usually supported by powerful tools ©2008 John Wiley & Sons Ltd.
Internal Auditing ISO 9001:2015
Control Plans Control Kaizen Facilitation.
User Training Renewed focus on the issue of user safety and training Recent instances have highlighted the need for Users to have job specific safety training.
ISM Code 2010: Part A - Implementation Malcolm Maclachlan.
Overview PRINCE Hogeschool Rotterdam. 2 Project definition  A project is a temporary organization that is created for the purpose of delivering.
Day in the Life (DITL) Production Operations with Energy Builder Copyright © 2015 EDataViz LLC.
Supplier Performance Development Process
OHSAS Occupational health and safety management system.
DOCUMENTATION ISO/IEC 17025:2005 Documentation.
Safety Leadership Defining a World Class Safety and Health Program – An Industry Perspective* *Special thanks to GE Global Nuclear Fuels – for the use.
Copyright © 2010 Pearson Education, Inc. or its affiliate(s). All rights reserved.1 | Assessment & Information 1 Online Testing Administrator Training.
ITIL® Core Concepts “Foundations to the Framework” Thatcher Deane 02/12/2010.
Essential Requirements of Pool Management Companies

Pipeline Safety Management Systems
LESSON 5 Control of Manufacturing Environment and Foreign Object Debris 15November2013 Lesson 4: Safety Stock.
Software Project Configuration Management
Why LPA’s? LPA’s can provide low cost system for finding problems and making improvements in Safety, Quality, Delivery, Cost and Morale when used effectively.
Post Survey Protocol Kenny williamson keith Harbuck keith & holmes llc
Chapter 18 Maintaining Information Systems
Software Quality Engineering
Software Configuration Management
Software Quality Engineering
UNIT-6 SOFTWARE QUALITY ASSURANCE
Focus on “How” through SCMH
Foreign Object Elimination
UNIT-6 SOFTWARE QUALITY ASSURANCE
Maintaining Information Systems (SAD- 18)
Why LPA’s? LPA’s can provide low cost system for finding problems and making improvements in Safety, Quality, Delivery, Cost and Morale when used effectively.
Why LPA’s? LPA’s can provide low cost system for finding problems and making improvements in Safety, Quality, Delivery, Cost and Morale when used effectively.
Chapter 18 Maintaining Information Systems
Presentation transcript:

FOE Implementation Basic Process

FOE IMPLEMENTATION PROCESS FLOWCHART

FOE Implementation Process Flowchart The FOE Focal Point is selected for every Area to assist in the implementation of the FOE Program and compliance to the requirements. FOE Implementation Process Flowchart

FOE AREA CONTROL LEVEL ASSESSMENT

FO Control Level Assessment Complete General Information about the area Get minimum Control Level from Requirements Identify Potential FOD Risks to the Product Identify any additional FOD controls that will used beyond the Requirements and identify any exceptions Provide any instructions for FOD prevention that are special to the hardware List the Approvals of the Assessment as required. Examples are FOE Focal Point, Section Manager, Engineering, Program Manger

FO Control Level Assessment Overall Approach Complete a FO Control Level Assessment for the area first to determine FOE Control Level of the overall area (baseline). This level is noted on the external area signage board This assessment should handle all hardware and operations that you would normally expect to process and perform. Revise assessment as required (add rev letter – DO NOT OVERWRITE any assessments). For cases of hardware or processes that do not fit into the overall area assessment performed above, generate an additional assessment to specifically address that hardware or process and understand the FO Control Level required as well as list any special instructions/exemptions. Area Level Assessment (Baseline) Additional Assessments

FOD METRICS

FOD Incident Reporting Metric Definitions: Foreign Object Debris FOD A substance or article alien to the product or assembly that has the potential to cause damage or degrade the product’s required safety and/or performance characteristics. Foreign Object Damage Any damage attributed to a foreign object that can be expressed in physical or economic terms which may or may not degrade the product’s required safety and/or performance characteristics. FOD Incident An Instance where Foreign Object Damage or Debris (FOD) is found

FOD Incident Reporting Metric Standard Reporting Metric (Must be updated monthly and posted): Example

FOD Incident Reporting Metric FOD Metric Chart Input Data Table (Example Only): Manually loaded using data from monthly data sheets Can automate for a specific area if desired

FOD Incident Reporting Metric FOD Metric Monthly Data Sheet (Example Only):

FOE CONTROL AREA IDENTIFICATION

FOE Control Areas Medium Example LOW High Medium Required for FOE Control Levels different from posted level on signage (for Higher or Lower Areas) Use signage, floor markings and/or stanchions to identify area Sub-Areas Overall Area Medium LOW Example High Apply Note for Sub-Areas Overall Area Medium FOE Focal Point is responsible to ensure proper area identification

FOE Control Area Possible Concerns Other users working in the Area may not know enough about FOD control levels yet to notify the FOE Focal Point or other Area personnel when a higher (or lower) level of control is needed It is important that we educate the users to ensure understanding and compliance to the new FOE policy/work instruction at all times The FO Control Level Assessment should capture the possibility of requiring a Control Level change to accommodate a configuration change (planned or unplanned) with the product

Internal Signage Example

DAILY FOE AREA SWEEP CHECKLIST

FOE Area Sweep Checklist FOE Focal Point performs or assigns task Must be performed daily for all Medium and High areas Elements may be combined with area 6S program (if performed daily) Records must be retained Anything found must be fixed or addressed on the checklist Template and sweep elements may be tailored to a specific area

MONTHLY FOE SELF-ASSESSMENT CHECKLIST

FOE Self-Assessment Checklist FOE Focal Point performs or assigns task Must be performed monthly for all Medium and High Records must be retained Anything found must be addressed on the Corrective Actions sheet Template and self-assessment elements may be tailored to a specific area Impractical to do for temporary Medium/High areas unless area is in place at time of assessment No requirement to post the self-assessment checklist Pareto chart as a Metric

MATERIAL CONTROL

Material Control will be the hardest to do! Required for FOE control Levels Medium and High Try to make Material Control area as small as possible Use floor markings or stanchions to identify area Log in/Log out guidelines Requirement was developed primarily for screws, nuts, bolts, q-tips and other small parts instead of glues, paints and sealants Make Log in/Log out sheet that is specific to the operation Consumables too large to be lost or impractical to count can be accounted for using visual confirmation (examples include Kimwipes, tape, glue) Example Material Control will be the hardest to do!

TOOL CONTROL

Recommended Form - May be Tailored to Site/Area Specific Requirements Tool Control Required for FOE control Level of High only Try to make Tool Control area as small as possible Use floor markings or stanchions to identify area Shadowboxing is best method but it may not be practical in an Engineering Lab Controlled Perimeter List is the easiest to implement Lost tools must be reported immediately Controlled Perimeter Tool Checklist: Recommended Form - May be Tailored to Site/Area Specific Requirements

FOD INCIDENT REPORTING

Incident Reporting Follow the FOD Incident Reporting Process Flowchart All FOD Incidents are required to be reported Know the definition of FOD to avoid unnecessary reporting Report a metric for every FOD Incident Share information with others Don’t be afraid to report an Incident (root cause analysis is important) FOE Focal point needs to know about all FOD Incidents If Foreign Object Damage is found, stop work on the hardware, report incident and initiate an investigation. Resume work when authorized

Incident Reporting FOD Incident Reporting Process