oSIST prEN 9242:2024

SLOVENSKI STANDARD
01-november-2024
Aeronavtika - Vodenje programov - Smernice za vzpostavitev in izvajanje
razvojnega načrta
Aerospace series - Programme management - Guide for establishing and implementing
a development plan
Luft- und Raumfahrt - Programm-Management - Richtlinien für die Erstellung und
Übernahme eines Entwicklungsplanes
Série aérospatiale - Management de programme - Guide pour l’établissement et la mise
en œuvre d’un plan de développement
Ta slovenski standard je istoveten z: prEN 9242
ICS:
49.020 Letala in vesoljska vozila na Aircraft and space vehicles in
splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT
EUROPEAN STANDARD
NORME EUROPÉENNE
EUROPÄISCHE NORM
August 2024
ICS 49.020
English Version
Aerospace series - Programme management - Guide for
establishing and implementing a development plan
Série aérospatiale - Management de programme - Luft- und Raumfahrt - Programm-Management -
Guide pour l'établissement et la mise en œuvre d'un Richtlinien für die Erstellung und Übernahme eines
plan de développement Entwicklungsplanes
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee ASD-
STAN.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations
which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.

This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 9242:2024 E
worldwide for CEN national Members.

Contents Page
European foreword . 3
1 Scope . 4
2 Normative references . 4
3 Terms and definitions . 5
4 List of acronyms . 5
5 End-purpose of the development plan . 5
5.1 Position of development in the programme . 5
5.2 Purposes of the development plan . 6
6 Content of the development plan . 7
6.1 General. 7
6.2 Outcomes . 8
6.2.1 Customer-supplied input data . 8
6.2.2 Reference documents . 8
6.2.3 Other assumptions and constraints taken into account . 9
6.2.4 Incorporation of the risks and opportunities . 9
6.2.5 Development logic . 9
6.2.6 Sequencing of the sub-phases, key dates, processes, main tasks and reviews specific to
development . 10
6.2.7 Services . 10
6.2.8 Necessary materials and means . 11
6.2.9 Methods and techniques needed for development . 12
6.2.10 Human and financial resources . 12
6.3 Development reference framework . 13
6.3.1 General. 13
6.3.2 Development schedule . 13
6.3.3 Monitoring indicators . 13

European foreword
This document (prEN 9242:2024) has been prepared by ASD-STAN.
After enquiries and votes carried out in accordance with the rules of this Association, this document has
received the approval of the National Associations and the Official Services of the member countries of
ASD-STAN, prior to its presentation to CEN.
This document is currently submitted to the CEN Enquiry.
1 Scope
The purpose of this document is to:
— remind the end-purpose of the development phase (see Clause 5);
— precise the content and outcomes of a development plan (see Clause 6).
This document is a supporting document that supplements RG.Aero 000 41 regarding the specific aspects
to be taken into account in the development plan.
The iteratively realized development plan is consistent with the documents identified in 6.2.2.
This document applies to each level of the product breakdown structure. In particular, it takes account of
the customer/supplier relationships.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 9200, Aerospace series — Programme management — Guidelines for project management specification
EN 9208, Aerospace series — Programme management — Expression of need — Guidance on and format
for (need) technical specification
EN 9215, Programme management — Definition justification and qualification — A guide to drawing up
the definition justification plan and the definition justification dossier
EN 9223-100, Programme management — Configuration management — Part 100: A guide for the
application of the principles of configuration management
EN 9227-1, Programme management — Guide to dependability and safety control
EN 9239, Aerospace series — Programme management — Recommendations to implement risk
management and opportunity management
RG.Aero 000 30, Programme management — Work breakdown structure establishment
RG.Aero 000 41, Programme management — Execution logic
RG.Aero 000 43, Programme management — Guide for establishing and implementing a production plan
RG.Aero 000 48, Programme management — Guide for establishing and implementing an industrialization
plan
RG.Aero 000 61, Programme management — Cost and schedule management in programme phasing
RG.Aero 000 76, Programme management — Recommendations for the implementation of the integrated
logistic support
ISO 10005, Quality management — Guidelines for quality plans

Published as ASD-STAN prEN at the date of publication of this document, available at: https://www.asd-stan.org/.
3 Terms and definitions
For the purposes of this document, the following term and definition apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp/
— IEC Electropedia: available at https://www.electropedia.org/
3.1
product
result of activities or processes
Note 1 to entry: Product categories can be services, hardware, software, processed materials, intermediate work
products from elementary activities, such as documents, models, etc.
Note 2 to entry: In the frame of a product developed to satisfy a customer’s need, the processes involved are the
expression of the need, the establishment of the definition, the industrialization and the production.
Note 3 to entry: The product can be either a final product to be delivered to a customer (aircraft, equipment, etc.)
or one of its components. In both cases, it represents the supply due under the contract.
4 List of acronyms
AR acceptance review
CDR critical design review
DDF definition data file
ELR end-of-life review
FR feasibility review
IQR integrated qualification review
IRR integration readiness review
(N)TS (need) technical specification
PDR preliminary design review
PRR production readiness review
SVR system verification review
5 End-purpose of the development plan
5.1 Position of development in the programme
The development phase is positioned between the definition phase and the production phase.
The development phase begins with passing the preliminary design review (PDR), which validates the
preliminary definition data file (DDF), including the reference (need) technical specification [(N)TS]. It is
concluded by the qualification pronouncement, which verifies that the product definition (during the
integrated qualification review – IQR):
— meets the needs of the customer, as expressed in the (N)TS (see EN 9208);
— is producible, maintainable and free of unacceptable risks;
— achieves the performance, costs, deadlines and quality compromises.

Figure 1 — Position of the development plan in the programme
The development phase consists of activities that are part of other processes (see Figure 1), which will
be taken into account when drawing up the development plan (see Clause 6). The input to be taken into
account includes:
— the execution plan (according to RG.Aero 000 41);
— the qualification and certification plans;
— the support plan (according to RG.Aero 000 76);
— the industrialization plan (according to RG.Aero 000 48);
— the production plan (according to RG.Aero 000 43);
— the disposal plan.
Depending on the product, some strategic items may be defined in advance of the development plan.
5.2 Purposes of the development plan
The development plan is established in order to:
— ensure the consistency of product development in terms of:
o links with the upstream level (development plan of the higher-level system); and
o links with the downstream levels (development plan of subsystems and components);
— control the execution, in the form of an effective and robust steering reference framework
(see subclause 6.3) to handle the contingencies encountered during development.
The development plan includes:
— the identification, scheduling and planning of the tasks of the various participants (development
tasks and associated realization tasks);
— the identification of human and material resources (scheduling, provision, etc.);
— the organization of measurements (dates and other indicators) of development progress
(performance control, justifications acquired, etc.).
As an essential tool for steering decision-making, it is important for the development plan:
— to be available in right time: its establishment is undertaken as soon as development is envisaged;
— to be kept up to date according to the management decisions recorded (first and subsequent issues);
— to contain a level of detail appropriate to management decision-making. Excessive and inadequate
breakdown of work should be avoided: although it is based on the work breakdown structure, the
development plan is established with different aims.
The criteria to be taken into account when agreeing on the level of detail are as follows:
— p
...