The Aerospace Design and Development Procedure AS9100 delineates approved procedures for advanced quality planning, design, and development of new aircraft products or aerospace services. The procedure applies to all new product development, as well as to significant changes to existing products. (20 pages, 3281 words)
The design phase is the most important phase of the aerospace product life cycle, because inherent quality, effectiveness, safety, and customer satisfaction of the product are established here. No matter how carefully a product may be manufactured or how perfect a quality control program, inherent qualities cannot be improved except through design enhancement (Design in Quality). It’s crucial that adequate advanced quality planning and controls be established, implemented, and maintained during the aerospace design phase to optimize quality, effectiveness, safety, and customer satisfaction prior to manufacturing.
All Employees are responsible for ensuring product and process improvement.
The Engineering Manager is responsible for designing, evaluating, testing, and all technical aspects of product and process development.
The Accounting Manager is responsible for evaluating and reporting on the financial aspects of product/process development.
The Marketing Manager is responsible for coordinating product development with the customer base, supervising field trials, finding new markets for the Company’s products/processes, and raising awareness of the Company’s offerings.
Top Management is responsible for final review and approval of design and development (D&D) projects.
The Product Development Team is responsible for managing the product design-and-development process; may also be known as “the Project Team”.
COTS – Commercial off-the-shelf; products manufactured commercially and tailored for a specific use. Compare COTS products with those produced entirely and uniquely for specific applications.
Failure Mode and Effects Analysis (FMEA) – Technique for assessing design of processes, products or services in which failures can occur. FMEA is useful for evaluating reliability, safety, and general quality in order to design in quality, evaluate and address risks, and improve design results.
The probability of each failure occurring and the result of failure are analyzed. If possible, hazards and faulty performance are designed out of the device; if not, hazards/substandard performance are compensated, reduced, detected, or prevented (by interlocks, warning signs, explicit instructions, alarms, etc.).
Risk of failure cannot always be removed from products but can be understood and controlled to the extent possible with technology or countermeasures.
Fault Tree Analysis – Deductive, top-down approach to failure mode analysis, where:
Key characteristic – Feature of a material, part, or process, variation of which will significantly influence a product’s fit, performance, service life, or manufacturability. Key characteristics are essential to meeting product goals.
Quality Function Deployment (QFD) – Structured approach to defining customer needs or requirements and translating needs into specific plans to produce products to meet those needs. The “voice of the customer” (the term used to describe stated and unstated customer needs or requirements) is captured in a variety of ways (e.g., direct discussion or interviews, surveys, focus groups, customer specifications, observation, warranty data, field reports) and then summarized in a product planning matrix – a “house of quality”. Houses of quality are used to translate higher-level “whats” – needs – into lower-level “hows”, product requirements or technical characteristics to satisfy these needs.
Requirement – Condition that must be met in order to do something; something wanted or needed; something essential to the existence or occurrence of something else.
Verification – Evaluating a system or component during or at the end of the development process to determine if it satisfies specified input requirements.
Validation – Evaluating a system or component during or at the end of the development process to determine if it satisfies actual use conditions.