Obsolescence is a significant risk factor for an organisation and/or a programme activity regarding the continuity of productions, services and maintenance in operational conditions of equipments and systems. It can appear in any phase of the product life cycle. Thus it is essential that the organisation determines the best strategy to be implemented in order to control these risks, implying its customers and suppliers in the definition of this strategy.
This recommendation is a document meant to be used as guidelines, for an organisation and/or a given programme, for the implementation of a coordinated management process of obsolescence risks related to chemical products and to their effects on products, especially on materials, processes and mechanical parts.
Can be subject to obsolescences:
—   all categories of equipments as well as their components;
—   materials and processes used to produce, operate or maintain a product;
—   all that can be bought, manufactured, repaired, be it done internally or externally;
—   means of production, test and maintain.
This document excludes obsolescences related to electronic components and softwares (for more information on that subject see EN 62402).

  • Standard
    29 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document explains the wording in use within the following standards:
EN 9223-100, Programme Management - Configuration Management - Part 100: A guide for the application of the principles of configuration management
EN 9223-101, Programme Management - Configuration Management - Part 101: Configuration identification
EN 9223-102, Programme Management - Configuration Management - Part 102: Configuration status accounting
EN 9223-103, Programme Management - Configuration Management - Part 103: Configuration Verifications, Reviews and Audits
EN 9223 -04, Programme Management - Configuration Management - Part 104: Configuration Control

  • Standard
    14 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document:
-   is based on internationally-recognised concepts;
-   proposes organisational principles and implementation processes for Configuration Management from both viewpoints: "programme" and "company", with emphasis on the "programme" viewpoint;
-   deals with capture, safekeeping and release of configuration information. It details the principles described in EN 9223-100.
It is up to each programme responsible person to define the necessary details of application and tailoring in the Configuration Management plan.

  • Standard
    21 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document:
-   is based on internationally-recognized concepts;
-   proposes organisational principles and implementation processes for configuration management from both viewpoints: "programme" and "company", with emphasis on the "programme" viewpoint.
The required procedures for implementation and necessary tailoring have to be prescribed for each programme.
This document encompasses some aspects of the relationship between configuration management and contract management, but does not address contract management procedures.
Intended for use in complex programmes (aerospace, defence, etc.), this document is an extension of standard ISO 10007 Quality management systems - Guidelines for configuration management.
This document is coherent with EN 9200 Programme management - Guidelines for project management specifications.
The described principles concern all the stakeholders in the programme (authorities, manufacturers, skills, etc.) from the feasibility phase to disposal. These principles can be applied or tailored to any products (material or software).

  • Standard
    32 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document is declined from the principles described in the EN 9223-100, it:
-   is based on internationally-recognised concepts;
-   proposes organisational principles and implementation processes for configuration management from both viewpoints: "programme" and "company", with emphasis on the "programme" viewpoint;
-   deals with configuration control but not contract management methods.
It is up to each person responsible for a programme to define the detailed methods of application and tailoring as necessary.

  • Standard
    33 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document is declined from the principles described in the EN 9223-100, it:
-   is based on internationally-recognised concepts;
-   proposes organisational principles and implementation processes for Configuration Management from both viewpoints: "programme" and "company", with emphasis on the "programme" viewpoint;
-   deals with configuration identification but not contract management methods.
It is up to each person responsible for a programme to define the detailed methods of application and tailoring as necessary.

  • Standard
    23 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document:
-   is based on internationally-recognized concepts;
-   proposes organisational principles and implementation processes for Configuration Management from both viewpoints: "programme" and "company", with emphasis on the "programme" viewpoint;
-   deals with verifications, reviews and audits tending towards the validation of the configuration information consistency. It details the principles described in EN 9223-100.
It is up to each programme responsible person to define the necessary details of application and tailoring in the Configuration Management plan.
Important remark:
Configuration audit doesn’t be confused with quality audit (for detailed information, see 4.1).
This document does not deal with configuration system audits (quality audit) deployed within the scope of a programme. These audits stem from quality audits as defined in EN ISO 9001 (process conformity or efficiency audits).

  • Standard
    25 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document belongs to the documents going along with EN 9200 relating to Project Management Specification.
The aims of this document are as follows:
-   to specify/remind the concept of (Need) Technical Specification (N)TS;
-   to define the principles and conditions for drawing up, approving, using and updating a (N)TS;
-   to propose a template of (N)TS.
The template identifies topics and types of related requirements to be covered in a (N)TS without being completely exhaustive or mandatory. It is due to be analysed like a check-list and tailored according to the type of the product of interest, the context of the bodies involved and the contractual details.
The principle of drawing up a (N)TS applies to both tangible and intangible products (e.g. services).
The customer/supplier relationship addressed by these principles may also apply within a single organization. The concepts of customer and supplier are discussed in this document without distinction between internal or external relationship.
This document implements and adapts EN 16271 to the context, in order to meet the specific needs of the aeronautical field and more generally the needs of other fields.
This document is more explicit about certain aspects of ISO/IEC/IEEE 29148 dedicated to requirements engineering, such as the responsibility for drawing up a (N)TS on a contractual basis and also the process of drawing it up within a programme (stages and milestones). It also supplements the technical specification framework proposed by ISO/IEC/IEEE 29148, in particular with requirements relating to safety of operation and result assurance.
The relationships existing between Functional Performance Specification (FPS) and (N)TS for expression of needs are given in Annex A.

  • Draft
    42 pages
    English language
    sale 10% off
    e-Library read for
    1 day