oSIST prEN 9241:2025
(Main)Aerospace series - Programme management - Execution logic
Aerospace series - Programme management - Execution logic
The scope of the present document is to provide the elements needed for elaborating the programme execution logic and drafting the execution plan for the realization of a product.
NOTE 1 In this document, the term “logic” alone is sometimes used for “execution logic”.
NOTE 2 In this document, the term “product” is used to designate the object of the program concerned, and the term “system” is used to designate the product for anything related to system engineering.
NOTE 3 The product is also considered a “system-of-interest” and its enabling systems are also taken into account.
The execution logic and plan enable customers/suppliers to reach an agreement on how their respective processes and activities can be organized.
The aim is to enable each actor in the programme to manage their activities with sufficient visibility of the sequencing of the other stakeholders’ activities.
This document belongs to the documents supporting EN 9200 relating to the programme management specification.
The present document describes the principles of programme execution logic and defines the corresponding management requirements. This description is supplemented:
- on the one hand, in terms of execution logic principles, by:
o the challenges of a basic logic common to all actors (synchronization);
o the applicable criteria to set up this basic logic;
o the translation of this logic into the programme processes;
- on the other hand, in terms of implementing the execution logic, by:
o the procedures for practical implementation of the management requirements defined in EN 9200;
o adaptations of the logic according to the various constraints and specificities of the programme, and justification of these adaptations;
o the consistency between the basic logic at system level and the logics at subsystem and constituent levels.
The breakdown of clauses as used in this document gives a gradual understanding of the approach to be adopted to construct an execution logic. For instance:
- Clause 5 presents the end-purpose of a programme execution logic as well as the associated basic concepts and the constituents of this logic;
- Clause 6 describes and characterizes the process for building the logic;
- Clause 7 concerns change control to the execution logic;
- Clause 8 concentrates on the importance of capitalization and lessons learned.
This document applies to aeronautical, space and defence programmes. The principles can be extended to other areas of activity.
It applies to realization of a single product, of several samples or of a series. It applies to any customer/supplier level, while ensuring consistency between successive levels.
The principles described concern all programme actors, from initial expression of need through to closure of the programme.
Luft- und Raumfahrt - Programmmanagement - Ausführungslogik
Série aérospatiale - Management de programme - Logique de déroulement
Aeronavtika - Vodenje programa - Izvedbena logika
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-februar-2025
Aeronavtika - Vodenje programa - Izvedbena logika
Aerospace series - Programme management - Execution logic
Luft- und Raumfahrt - Programmmanagement - Ausführungslogik
Série aérospatiale - Management de programme - Logique de déroulement
Ta slovenski standard je istoveten z: prEN 9241
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
November 2024
ICS 49.140; 49.020
English Version
Aerospace series - Programme management - Execution
logic
Série aérospatiale - Management de programme - Luft- und Raumfahrt - Programmmanagement -
Logique de déroulement Ausführungslogik
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 9241:2024 E
worldwide for CEN national Members.
Contents Page
European foreword . 3
1 Scope . 4
2 Normative references . 5
3 Terms and definitions . 5
4 List of acronyms . 8
5 Execution logic: end-purpose, concepts and constitutive elements . 9
5.1 End-purpose of programme execution logic . 9
6 Concepts . 9
6.1 Programme execution logic . 9
6.2 Execution plan . 9
6.3 Constitutive elements of execution logic . 10
7 Execution logic construction process . 14
7.1 General. 14
7.2 Inputs for the execution logic construction process . 16
7.3 Description of the execution logic construction activity . 17
7.4 Interfaces with the other disciplines . 19
7.5 Process output: execution logic . 21
8 Execution logic change control . 22
8.1 General. 22
8.2 Triggers for updating the logic . 22
8.3 Impact analysis . 23
8.4 Decisions and baselining . 23
9 Capitalization and lessons learned about the logic . 23
Annex A (informative) Contents of an execution plan . 25
Annex B (informative) Example of execution logic for an entire programme . 28
B.1 General. 28
B.2 Description of phases and milestones . 30
Annex C (informative) Examples of specificities to be taken into account . 38
C.1 Incrementally realized product . 38
C.2 Integration of a commercial off-the-shelf (COTS) product . 39
C.3 Integration of a multi-programme product . 40
Bibliography . 41
European foreword
This document (prEN 9241:2024) has been prepared by ASD-STAN.
This document is currently submitted to the CEN Enquiry.
1 Scope
The scope of the present document is to provide the elements needed for elaborating the programme
execution logic and drafting the execution plan for the realization of a product.
NOTE 1 In this document, the term “logic” alone is sometimes used for “execution logic”.
NOTE 2 In this document, the term “product” is used to designate the object of the program concerned, and the
term “system” is used to designate the product for anything related to system engineering.
NOTE 3 The product is also considered a “system-of-interest” and its enabling systems are also taken
into account.
The execution logic and plan enable customers/suppliers to reach an agreement on how their
respective processes and activities can be organized.
The aim is to enable each actor in the programme to manage their activities with sufficient visibility of
the sequencing of the other stakeholders’ activities.
This document belongs to the documents supporting EN 9200 relating to the programme management
specification.
The present document describes the principles of programme execution logic and defines the
corresponding management requirements. This description is supplemented:
— on the one hand, in terms of execution logic principles, by:
o the challenges of a basic logic common to all actors (synchronization);
o the applicable criteria to set up this basic logic;
o the translation of this logic into the programme processes;
— on the other hand, in terms of implementing the execution logic, by:
o the procedures for practical implementation of the management requirements defined in
EN 9200;
o adaptations of the logic according to the various constraints and specificities of the programme,
and justification of these adaptations;
o the consistency between the basic logic at system level and the logics at subsystem and
constituent levels.
The breakdown of clauses as used in this document gives a gradual understanding of the approach to be
adopted to construct an execution logic. For instance:
— Clause 5 presents the end-purpose of a programme execution logic as well as the associated basic
concepts and the constituents of this logic;
— Clause 6 describes and characterizes the process for building the logic;
— Clause 7 concerns change control to the execution logic;
— Clause 8 concentrates on the importance of capitalization and lessons learned.
This document applies to aeronautical, space and defence programmes. The principles can be extended
to other areas of activity.
It applies to realization of a single product, of several samples or of a series. It applies to any
customer/supplier level, while ensuring consistency between successive levels.
The principles described concern all programme actors, from initial expression of need through to
closure of the programme.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions 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
life cycle (of a product)
set of successive maturity states that the product takes during the different phases of a programme
Note 1 to entry: States of maturity during which the product is gradually processed are typically: concept,
development, realization, use including in-service support, disposal.
Note 2 to entry: The life cycle is generally illustrated as a series of stages, from production (extraction and
harvesting of raw materials) to final disposal (disposal or recovery), including manufacturing, packaging,
transport, use and recycling or disposal.
Note 3 to entry: Notion not to be confused with life profile.
3.2
life cycle (of a programme)
set of phases that a programme passes through from its initiation to its closure
Note 1 to entry: The phases of the programme are typically: initial expression of need, feasibility, definition,
development, production, operation, disposal.
Note 2 to entry: The life cycle is a structured and exhaustive scenario, elaborated as a common reference for all
stakeholders concerned and aimed at taking account of all contexts and processes in which the product shall be
involved during its life.
3.3
milestone
significant and planned event used to measure the progress of a programme to allow the next
phase to start
3.4
execution logic
phased and articulated sequence of activities, tasks and milestones covering the entire lifecycle of
the product
Note 1 to article: Execution logic enables each actor to control own activities and coordinate them with those of
the other actors.
3.5
phase of a programme
period of a programme, delineated by milestones, during which a coherent and orderly set of activities
is performed to achieve an objective
3.6
process
sequence of correlated or interacting activities that transforms inputs into outputs according to one or
more defined objectives
Note 1 to entry: The inputs of a process are usually the outputs of other processes.
Note 2 to entry: A process shall be planned and implemented under controlled conditions.
Note 3 to entry: A process is characterized by the following elements:
— object;
— objective(s);
— inputs, including prerequisites;
— results/purposes/effects;
— criteria of success;
— rules;
— constraints;
— definition and organization of activities;
— means (human and technical resources) to be implemented;
— methods to be applied.
Note 4 to entry: The French term “procédé” is generally used in the context of manufacturing processes. A process
is called “special process” when the conformity of the outputs cannot be verified by subsequent monitoring or
measurement and requires special provisions for process control.
3.7
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.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.