Sort By:
Viewing 21 to 40 of 646

(also referred to as Permanent Corrective Action)

  1. Action implemented to address the root cause(s) and contributing cause(s) of the undesirable condition, situation, nonconformity, or failure; action taken to prevent recurrence. [9136]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 21 Apr 2017
Updated: 21 Apr 2017
  1. The process of identifying all the causes (root cause and contributing causes) that have or may have generated an undesirable condition, situation, nonconformity, or failure. [9136]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 21 Apr 2017
Updated: 21 Apr 2017

1. The original event(s), action(s), and/or condition(s) generating (directly or in cascade) an actual or potential undesirable condition, situation, nonconformity, or failure.
NOTE: There is sometimes more than one root cause associated to a single nonconformity or one root cause with multiple contributing causes. [9136]

Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 21 Apr 2017
Updated: 21 Apr 2017
  1. Action to eliminate the cause of a potential nonconformity or other undesirable potential situation.
    NOTE 1: There can be more than one cause for a potential nonconformity.
    NOTE 2: Preventive action is taken to prevent occurrence whereas corrective action is taken to prevent recurrence. (ISO 9000:2005) [IAQG-history]
  2. Action to eliminate the cause of a potential nonconformity or other undesirable potential situation (see ISO 9000).

NOTE: Preventive action is taken to prevent occurrence whereas corrective action is taken to prevent recurrence. [9136]

Chinese:
预防措施
Chinese Taiwan:
預防措施
Dutch:
preventieve actie
French:
action préventive
German:
Vorbeugungsmaßnahme
Hebrew:
פעולה מונעת
Indonesian:
tindakan pencegahan
Italian:
azione preventiva
Japanese:
予防措置
Korean:
예방조치
Portuguese:
Ação preventiva
Russian:
Предупреждающие действия
Spanish:
acción preventiva
Turkish:
önleyici faaliyet
Created: 11 Jul 2013
Updated: 21 Apr 2017
  1. The absence of, or the failure to implement and maintain, one or more quality management system requirements, or a situation that would, on the basis of available objective evidence, raise significant doubt as to the quality of what the organization is supplying. Major: The absence of, or total breakdown of a quality management system element specified in the AQMS standard or any non-conformities where the effect is judged to be detrimental to the integrity of the product, processes or service. Minor: A single system failure or lapse in conformance with a procedure relating to the AQMS standard. NOTE: A number of minor non-conformities against one requirement can represent a total breakdown of the system and this can be considered as a major nonconformity. Any finding (e.g., comments, observations) that equates to the above definition shall be documented as a nonconformity, categorized as major or minor, and dealt with in accordance with 8.3. [9104]
  2. The non-fulfilment of a requirement that is stated, generally implied, or obligatory (see 9101 standard for definitions of major and minor nonconformities). [9104/2]
  3. A specific occurrence of a condition that does not conform to a specification or other inspection standard. [9013]
  4. Non-fulfillment of a requirement (see ISO 9000).

NOTE: It may be a nonconforming product, but may also be a late delivery, incorrect paperwork, incorrect process [production or Quality Management System (QMS) related], etc.[9136]

Chinese:
不符合(不合格)
Chinese Taiwan:
不符合性
Dutch:
afwijking
French:
non-conformité
German:
Abweichung/Fehler
Hebrew:
אי תאימות
Indonesian:
ketidaksesuaian
Italian:
non conformità
Japanese:
不適合
Korean:
부적합
Portuguese:
Não-conformidade
Russian:
Несоответствие
Spanish:
no conformidad
Turkish:
uygunsuzluk
Created: 11 Jul 2013
Updated: 21 Apr 2017
  1. The evaluation of an implementation of requirements to determine that they have been met; confirms the organization built the aircraft system/function/item correctly [based upon ARP4754]. [9115]
  2. Confirmation through the provision of objective evidence that specified requirements have been fulfilled. [9162]
  3. Processes of evaluation to assure input requirements are achieved at the end of a development stage. Verification can occur at various times during a software process. Verification includes review, analysis, inspection, and test. [9005]
  4. confirmation, through the provision of objective evidence, that specified requirements have been fulfilled.
    NOTE 1" The term “verified” is used to designate the corresponding status.
    NOTE 2" Confirmation can comprise activities such as
    – performing alternative calculations,
    – comparing a new design with a similar proven design ,
    – undertaking tests and demonstrations and
    – reviewing documents prior to issue (ISO 9000:2005) [IAQG-history]
  5. Confirmation by examination and provision of objective evidence that the specified requirements have been fulfilled. Relevant types of verification include:
  • Design Verification - Confirmation through the provision of objective evidence, that the specified product requirements have been fulfilled. Testing and/or analysis to ensure that all design outputs satisfy requirements may include activities such as: design review, performing alternate calculations, understanding tests and demonstrations, and review of design stage documents before release (reference AIAG Advanced Product Quality Planning and Control Plan). This may involve pre-production products.
  • Product Verification - The evaluation of a product's compliance to regulations, requirements, specifications, or physical conditions as designed. This is typically accomplished by testing and/or inspecting a product against its design requirements [i.e., First Article Inspection (FAI)]. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 11 Jul 2013
Updated: 19 Apr 2017
  1. The determination that the requirements for a product are correct and complete; confirms the organization is building the right aircraft system/function/item [based upon ARP4754]. [9115]
  2. The process of determining that software complies as follows: (1) conforms to its development standards (2) requirements and or specifications are fulfilled, (3) works as intended in the target environment. Validation determines that the fully integrated software functions correctly, completely, and consistently with system specifications and requirements. [9005]
  3. confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled.

  NOTE 1: The term "validated" is used to designate the corresponding status.

  NOTE 2: The use conditions for validation can be real or simulated.

  NOTE 3: Definition for a baseline: the demonstration that it has its required attributes, that any assumptions necessary in its development are valid (i.e. acceptable to the customer), and that the effectiveness of the emerging system design can affordably satisfy the system technical requirements and constraints.

  NOTE 4: Definition for a system: The assessment of the operational test authority that the system is suitable for operation and continued production, if planned. (ISO 9000:2005 and MIL-STD-499C:2005) [IAQG-history]

4. The assurance that a product, service, or system fulfills the needs of the customer and other identified stakeholders. It often involves acceptance with external customers (defined in IEEE 1490:2011). Relevant types of validation include:

  • Design Validation - Confirmation through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled. Testing and/or analysis to ensure the product design conforms to defined user needs and/or requirements. Design validation follows successful design verification and may involve pre-production product (e.g., development, prototype) [reference AIAG Advanced Product Quality Planning and Control Plan].
  • Process Validation - Confirmation through physical demonstration that a process consistently produces a result or product fulfilling its predetermined specifications, including key product or process characteristics which are stable and capable at the desired level.
  • Product Validation - The assurance that a product in the production configuration fulfills the needs of the customer and other identified stakeholders. It often involves acceptance with external customers (i.e., qualification testing). [9145]

Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 11 Jul 2013
Updated: 19 Apr 2017
  1. Those requirements identified by the customer, or determined by the organization, which have high risks of not being met, thus requiring their inclusion in the operational risk management process. Factors used in the determination of special requirements include product or process complexity, past experience, and product or process maturity. Examples of special requirements include performance requirements imposed by the customer that are at the limit of the industry’s capability, or requirements determined by the organization to be at the limit of its technical or process capabilities. [9100]
  2. The definition in 9100 (see clause 3.5) applies with the following clarification for software. Examples of special requirements that may introduce high risk for software include: the introduction of a new compiler, new advanced modeling technique, qualification of tools, specific test equipment capabilities, introduction of a new type of interface, or specific customer technical requirements. These requirements are included in the risk management process. [9115]
  3. Those requirements identified by the customer, or determined by the organization, which have high risks of not being achieved, thus requiring their inclusion in the risk management process. Factors used in the determination of special requirements include product or process complexity, past experience, and product or process maturity. Examples of special requirements include performance requirements imposed by the customer that are at the limit of the industry’s capability, or requirements determined by the organization to be at the limit of its technical or process capabilities (reference 9100 and 9110 standards). [9145]

Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 11 Jul 2013
Updated: 19 Apr 2017
  1. A review of the manufacturing process (e.g., equipment, operator training, manufacturing documentation, control plan, associated measurement tools) by a multi-disciplinary team to verify that the production processes are appropriately defined, documented, and ready for production. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
  1. A plan that identifies all resources (e.g., production and test/inspection equipment, tooling, jigs, fixtures, computing processes, materials, supply chain, trained work force, facilities) required to produce a product in sufficient quantity to satisfy the customer demand rate; additionally, it defines the timing of the release of work instructions, operator training, and commissioning of the machines. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
  1. A file containing objective evidence in support of PPAP requirements. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
  1. A generically applied term referring to an organization's process(es) for product realization. The process begins with conceptual product needs and expands throughout the life of the product. Common milestones include: kick-off, end of concept [i.e., Preliminary Design Review (PDR)], design release [i.e., Critical Design Review (CDR)], initial production approval, and production launch (see Figure 1). [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017

[also known as a High-level Bill of Material (BOM)]

  1. A breakdown of a product into its subsystems and major components; it is used to support early planning activities, including sourcing decisions. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
  1. A study that compares the output of an in-control process to the specification limits, expressed in terms of process capability index (e.g., Cpk) or as a process performance index [e.g., Ppk, Parts Per Million (PPM)]. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
  1. An assessment performed early in the process planning and development phase to determine resources (e.g., people, equipment, facilities) necessary to produce product at the customer demand rate. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
  1. An initial BOM completed, prior to design validation and release of design record, for production use. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
  1. A set of design related activities that establishes a preliminary concept design based upon the product specifications and requirements. This may include sketches, drawings, and physical or mathematical models that provide an understanding of the principle of operation and a high-level product structure. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
  1. Service rendered to the customer or to end users in support of the product's successful continuing use. This includes, but is not limited to, providing documents (e.g., maintenance manuals, service bulletins), product use training, repair or overhaul activity, service hot lines, and spare parts provisioning. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
  1. A collection of processes, activities, tasks, and outcomes within the software life cycle [see IEEE 24765]. [9115]
  2. Period of time (during the PDP) in which specific processes, tasks, deliverables, and outcomes of APQP occur; phases may overlap as illustrated in Figure 1. The end of a phase is indicated by fulfillment of phase deliverables (see Appendix B). [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 11 Jul 2013
Updated: 19 Apr 2017
  1. A study of the effects of selected elements of a measurement process (i.e., people, machines, tools, methods, materials, environment) on accuracy, precision, and uncertainty of measurement. [9145]
Chinese:

Chinese Taiwan:

Dutch:

French:

German:

Hebrew:

Indonesian:

Italian:

Japanese:

Korean:

Portuguese:

Russian:

Spanish:

Turkish:

Created: 19 Apr 2017
Updated: 19 Apr 2017
Viewing 21 to 40 of 646