general process manual - asd- · pdf filethe project teams, composed of experts of a sector...

General Process Manual

Document Reference: 2.5209 Issue 6, 15/09/2014

General Process Manual DOC REF:

2.5209 Issue 6 DATE:

06-2014 PAGE: 2 of 52

RECORD OF REVISIONS

List of ASD-STAN Domain Technical Coordinators: The current list is available and maintained via the ASD-STAN website (www.asd-stan.org) and ASD-STAN CENCENELEC Livelink

List of ASD-STAN Focal Points: The current list is available and maintained via the ASD-STAN website (www.asd-stan.org)

* The masculine gender is used throughout this process manual to allege the text, with no prejudice

and is understood to designate either male or female participants.

Iss. Date Reason for Revision Issued by Verified by Approved by

3 August

2000

First Release

A. Swan

A. Swan F. Jäger

4 June

2010

Upgrades and Modifications to process G. Lessmann ASD-STAN

Board

S. Drogoul

5 July

2012

Upgrades and Modifications to process

-Fast Track Process description

-5 years EN review

-Forms updated

-Abandon ASD-STAN Generic Template

ASD-STAN

Technical

Authority

ASD-STAN

Board

6 Sept.

2014

Upgrades and Modifications to process

- Livelink integrated as exchange / archiving

media for all ASD-STAN

- Preference for referencing CEN

(CENELEC) standards whenever existing

- Guaranty for the interchangeability

- Checking of Titles

- Declassification and Withdrawal processes

are clarified

- Standard Evolution Form applies to all

domains

- Review of Process for the Technical

Reports

- Illustration of CEN-CENELEC Process to

transform prEN into EN Standard

- Transversal project

ASD-STAN

Technical

Authority

ASD-STAN

Board

Mail of Andreas

Jain

dated : 2014/07/17

subject :

ASD-STAN

Board - AI 31:

Approval of the

GPM 2.5 Issue 6

http://www.asd-stan.org/

http://www.asd-stan.org/



06-2014 PAGE: 3 of 52

Table of Contents Table of Contents .................................................................................................................................... 3

INTRODUCTION ....................................................................................................................................... 6

1. TERMS OF REFERENCE ..................................................................................................................... 7

1.1 TECHNICAL ORGANIZATION .................................................................................................... 7

1.2 ASD-STAN BOARD .................................................................................................................... 9

1.3 TECHNICAL AUTHORITY (TA) ................................................................................................... 9

1.4 DOMAIN TECHNICAL COORDINATORS (DTC’S) ..................................................................... 10

1.5 SECTOR LEADERS (SL’S) ......................................................................................................... 10

1.6 SECTOR SECRETARIAT ............................................................................................................ 11

1.7 EXPERTS (SECTOR MEMBERS) ............................................................................................... 11

1.8 SECTOR PROJECT TEAM ......................................................................................................... 12

1.9 ORIGINATOR .......................................................................................................................... 12

1.10 NATIONAL COORDINATORS................................................................................................... 13

1.11 FOCAL POINTS (FP’S) ............................................................................................................. 13

1.12 THE EXECUTIVE ...................................................................................................................... 13

1.13 THE CEN-CENELEC LIVELINK .................................................................................................. 15

2. THE PROCESS ................................................................................................................................. 16

2.1 REGULAR PROCESS ................................................................................................................ 22

2.1.1 THE PROPOSAL STAGE (00.00) – FORM 1 .......................................................................... 22

2.1.2 NEW WORK PROPOSAL ASSESSMENT (00.20) – FORMS 2-1 & 2-2 ................................... 22

2.1.3 VOTE ON NEW WORK PROPOSAL (10.00) – FORM 3 ........................................................ 22

2.1.4 FINAL ASSESSMENT AND LAUNCH OF PROJECT (20.00) – FORM 4 ................................... 23

2.1.5 PREPARATION OF WORKING DRAFT (WD) (20.20) ............................................................ 23

2.1.6 AGREEMENT ON CONSENSUS DRAFT (CD) (20.99) – FORMS 6 ......................................... 24

2.1.7 NATIONAL DOMAIN BALLOT (NDB) ON CONSENSUS DRAFT / CEN-CENELEC ENQUIRY

(30.00) – FORMS 7 & 9 ...................................................................................................................... 24

2.2 FAST TRACK PROCESS ............................................................................................................ 25

2.2.1 BALLOTING ........................................................................................................................ 25

2.2.2 FINAL RESULT: WITH THE RULES DEFINED IN THE PROCESS MANUAL SECTIONS 2.1.4 AND

2.3: 26

2.3 RESULTS OF NATIONAL DOMAIN BALLOT (30.70) – FORM 8 ................................................ 26



06-2014 PAGE: 4 of 52

2.4 PUBLICATION (40.00) – FORMS 10 ........................................................................................ 27

2.5 REVIEW BY USERS / PREN TO EN PROCESS – FORM 9 ........................................................... 27

2.6 CEN-CENELEC FORMAL VOTE (50.00 – 50.20) ....................................................................... 28

2.7 FORMAL VOTE RESULTS (50.70) ............................................................................................ 28

2.8 CEN-CENELEC PUBLICATION AND AUTOMATIC WITHDRAWAL OF PREN(60.60 & 60.97) .... 28

2.9 REVIEW OF EN STANDARD (5 YEAR REVIEW) (STAGE 90)–FORM 13 .................................... 29

2.10 REVISION OF PUBLISHED DOCUMENT................................................................................... 29

2.11 DECLASSIFICATION (DC) ........................................................................................................ 30

2.12 WITHDRAWAL (RT) ................................................................................................................ 30

2.13 TRANSVERSAL PROJECT ......................................................................................................... 31

2.14 PUBLICATION OF ASD-STAN Technical Report ...................................................................... 31

3. SPECIAL PROJECTS ......................................................................................................................... 32

3.1 VIENNA AGREEMENT ............................................................................................................. 32

3.2 EU PROJECTS.......................................................................................................................... 32

3.3 IAQG QUALITY STANDARDS ................................................................................................... 32

3.4 AIRBUS EUROPEAN STANDARDS RELATIONSHIP WITH ASD-STAN ....................................... 32

4. GLOSSARY ...................................................................................................................................... 34

4.1 BOARD ................................................................................................................................... 34

4.2 BUSINESS CASE/ COST EFFECTIVENESS ................................................................................. 34

4.3 CANCELLATION ...................................................................................................................... 34

4.4 CEN-CENELEC FORMAL VOTE ................................................................................................ 34

4.5 CONSENSUS ........................................................................................................................... 34

4.6 CONSENSUS DRAFT (CD)........................................................................................................ 35

4.7 COVERSHEET (CS) .................................................................................................................. 35

4.8 DEFINITIVE TEXT .................................................................................................................... 35

4.9 DISCIPLINE ............................................................................................................................. 35

4.10 DOMAIN................................................................................................................................. 36

4.11 DOMAIN TECHNICAL COORDINATOR .................................................................................... 36

4.12 ESCALATION IN CASE OF MAJOR ERRORS DETECTED IN STANDARDS .................................. 36

4.13 EUROPEAN STANDARD (EN) .................................................................................................. 36

4.14 EXECUTIVE ............................................................................................................................. 36



06-2014 PAGE: 5 of 52

4.15 EXPERT ................................................................................................................................... 36

4.16 FINAL DRAFT .......................................................................................................................... 37

4.17 FIT/FORM/FUNCTION ............................................................................................................ 37

4.18 FOCAL POINT ......................................................................................................................... 37

4.19 INTELLECTUAL PROPERTY ...................................................................................................... 37

4.20 INTERCHANGEABILITY ........................................................................................................... 37

4.21 NEW WORK PROPOSAL (NWP) .............................................................................................. 38

4.22 NORMATIVE REFERENCE ....................................................................................................... 38

4.23 ORIGINATOR .......................................................................................................................... 38

4.24 PATENTED ITEMS / TRADE NAMES ........................................................................................ 38

4.25 PLATFORM ............................................................................................................................. 38

4.26 PROJECT ................................................................................................................................. 39

4.27 PROJECT TEAM / -LEADER ..................................................................................................... 39

4.28 SECTOR .................................................................................................................................. 39

4.29 SECTOR LEADER ..................................................................................................................... 39

4.30 STANDARD ............................................................................................................................. 39

4.31 TECHNICAL AUTHORITY ......................................................................................................... 39

4.32 TECHNICAL REPORT (TR) ....................................................................................................... 40

4.33 VOTING .................................................................................................................................. 40

4.34 WORKING DRAFT (WD) ......................................................................................................... 40



06-2014 PAGE: 6 of 52

INTRODUCTION a) The process manual describes the composition, structure and rules of procedure of the technical

organization of ASD-STAN for the establishment and publication of standards (prEN & EN) and

standard-like documents.

b) Rules for the functioning of ASD-STAN as a registered association are part of the legal statutes

and not contained in this process manual. The same applies to the procedures for the sales of

ASD-STAN document which are on separate documents and not included in this process manual.

c) The process manual is reviewed periodically in line with business requirements in order to

continuously improve ASD-STAN process and operating procedures.

d) This process manual consists of four sections.

Section one outlines the ASD-STAN terms of reference (ToR) laying out clearly the

composition, structure and responsibilities of the personnel involved in the Standardization

process.

Section two builds on section one by detailing the steps in the Standardization process, the

personnel responsible and the procedures to be followed.

Section three defines the terms for special projects.

Section four provides a comprehensive glossary of Standardization terms used in the process

manual.

e) While the Forms that support the process presented here are in paper format, we are also

integrating the use of electronic tools for internal and external communications, by use of the

email and IT standardization platforms. In case of IT inaccessibility, the paper forms can still be

sent by the traditional channels and the process remains intact.

f) As an affiliated body to CEN-CENELEC, the European Committee for Standardization, ASD-

STAN acts as sole provider of aerospace EN standards. Our process is based upon the statutes of

ASD-STAN and in agreement with CEN-CENELEC. It is based on the principles of

OPENNESS, TRANSPARENCY, CONSENSUS and BALANCE.

On Openness, while the ASD-STAN member countries’ companies form the vast majority of

the ASD-STAN sectors. In addition there is also a possibility, following Board approval on a

case by case basis, for CEN-CENELEC members and for non-member individuals from

companies or organizations outside of the ASD-STAN membership community to be admitted

to participate (as nominated expert) into the ASD-STAN sectors for specific projects, against

the payment of a membership fee for ad-hoc participation.

On Transparency, the CEN-CENELEC members are in copy for information of the voting

ballots on New Work Proposals and National Domain Ballots. Additionally, the database of

ongoing and published projects can be viewed on our website & CENCENELEC Livelink.

On Consensus, we achieve consensus among a BALANCED group of experts at the drafting

stage of prENs. The enquiries allow validating the content and there shouldn’t be any

technical changes requested at the CEN-CENELEC Formal Vote Stage.

On Balance, we aim at balanced representation from all interested parties and ASD-STAN

members in the preparation of standards documents.



06-2014 PAGE: 7 of 52

1. TERMS OF REFERENCE The Terms of Reference have been written so as to identify clearly the composition, structure and

responsibilities of the personnel involved in the Standardization process. The Figure 1 shows in

schematic form how the various organizations, bodies and teams interact with one another during the

Standardization process and should be used as a reference throughout this Section.

1.1 TECHNICAL ORGANIZATION a) The Technical Organization shall be structured to provide market-driven technology-oriented

activities within the working bodies.

b) The Technical Organization comprises of:

The Technical Authority, composed of the Domain Technical Coordinators (DTC’s) and

additional member representatives as nominated and assigned by the ASD-STAN Board;

The Domains managed by Domain Technical Coordinators (DTC’s);

The Sectors, as sub-domains, managed by Sector Leaders and supported by Sector

Secretariats;

The Project Teams, composed of Experts of a Sector for particular standardization projects

supported by Originators of New Work Proposal and/or external Experts participating as

applicable;

The Experts;

The Secretariats provided by the ASD-STAN members or their National Standardization

Organizations supporting the Sectors and their Project Teams;

The National Coordinators;

The Focal Points;

The ASD-STAN Manager Technical Services and other Executives, who support and

coordinate the communication between the structures and manage the interface with the CEN-

CENELEC Management Centre.

c) The Technical Organization shall:

Provide a structure in which technical Experts can work together efficiently and effectively;

Be open and transparent to all members of ASD-STAN and to other organizations with which

ASD-STAN maintains working liaisons;

Be responsible for creating the technical content of the document on a consensus basis;

Be constituted by representatives nominated by the members of ASD-STAN;

Participate as required to European or worldwide activities in order to supply expertise and

promote European Aerospace & Defence Industry point of view on standardization matters.

d) All nominations and assignments to participate in the Technical Organization are valid for an

indefinite period of time and will be reviewed periodically by the ASD-STAN Board. A balanced

representation of ASD-STAN members in appropriate functions in the Technical Organization is

foreseen.



06-2014 PAGE: 8 of 52

Figure 1: Overview of the Technical Organization and Relationships

Th

is is

the

AS

D-S

TA

N T

echn

ical O

rganiz

atio

n

Sector 1 = Project Team

Exp

SL = PTL

Exp Exp

Exp

Project Team 1

Exp PTL Exp Exp Orig

Sector 2

SL Exp Exp Exp Exp

Project Team 2


Sector 1

Domain 1

TA Technical Authority DTC

Project Team 2

Exp PTL Exp Orig Ext

CEN

CMC

CEN

Mem-

bers

United Kingdom Germany Italy Spain Sweden France ASD-STAN Board – ASD-STAN General Assembly

Legend:

FP National Focal Point for Technical Domain NC National Coordinator (if assigned) Exp Expert PTL Project Team Leader

Orig Originator of New Work Proposal (“Sponsor”) Ext External participant in Project Team admitted on exceptional basis

CEN European Standardization Organization CCMC CEN Management Center Exec ASD-STAN Central Executive TC Technical Committee DTC Domain Technical Coordinator SL Sector Leader

Sec Secretariat provided by ASD-STAN member

Usually the entire Sector acts as Project

Team for all Standardization Projects

assigned to this Sector with the Sector

Leader acting as Project Team Leader

Exceptionally Project Teams can be formed by selected members of the Sector

with a dedicated Project Team Leader assigned but with the entire Sector remaining

responsible for all Standardization Projects assigned to this Sector

Exec FP NC plus selected participants assigned by the ASD-STAN Board

Sec

Sec Sec Exp Exp

SL DTC Exec FP NC

Domain 2

Sec SL DTC Exec FP NC

SL Exp Exp Exp Exp Sec Exp

Project Team 1


http://upload.wikimedia.org/wikipedia/commons/b/b7/Flag_of_Europe.svg

http://upload.wikimedia.org/wikipedia/commons/4/4c/Flag_of_Sweden.svg

http://upload.wikimedia.org/wikipedia/commons/9/9a/Flag_of_Spain.svg

http://upload.wikimedia.org/wikipedia/commons/0/03/Flag_of_Italy.svg

http://upload.wikimedia.org/wikipedia/commons/b/ba/Flag_of_Germany.svg

http://upload.wikimedia.org/wikipedia/commons/c/c3/Flag_of_France.svg

http://upload.wikimedia.org/wikipedia/commons/a/ae/Flag_of_the_United_Kingdom.svg



06-2014 PAGE: 9 of 52

1.2 ASD-STAN BOARD Extract from the ASD-STAN Statutes:

“The Board shall exercise the most extended powers for the administration and management of the

Association except for the acts reserved to the competence according to the present Statutes.”

“The Board can be assisted by or delegate to one or several management committees and/or one or

several persons, chosen within or outside the Association, part of its competences, notably the daily

management of the Association with the use of the signature related to this management. The board

shall determine the powers and possibly the remuneration of those committees and/or persons.”

“If necessary, the Board shall determine the composition and competences of these management

committees. It shall also appoint its members and their representatives. It shall fix the duration of their

mandate.”

“The powers of the Board shall include:

Approval of yearly balance sheet and budget for submission to the General Assembly;

Preparation and monitoring of budgets and development plans;

Fixation of yearly membership fees for Promoting, Regular, Associate and Observer

members;

Selection and appointment of the Executive Staff, including the Director and delegation of

powers to the Executive Staff;

Preparation and updating of possible modification to the Statutes and to the Rules of

Procedure for approval by the General Assembly;

Ensure implementation of any agreement between ASD and the Association.”

1.3 TECHNICAL AUTHORITY (TA) a) The Technical Authority (TA) is composed of all the Domain Technical Coordinators and

additional member representatives as nominated and assigned by the ASD-STAN Board.

b) The TA is responsible for setting basic rules for standards development, e.g. co-operation with

other CEN-CENELEC Technical Committees, application of the Vienna Agreement (co-

operation with ISO). They review the process and propose improvements when a need is

identified. They are responsible for reviewing appeals.

c) It is also the responsibility of the TA to manage the general technical activities and to ensure

the quality function in regards with the Technical Organisation in general.

d) The Board will establish the Terms of References for the TA, in accordance with the

principles established in this Manual. The TA may propose modifications to the Terms of

Reference.

e) The TA will elect a chairman. The TA chairmanship is valid for an unlimited period of time

and will be reviewed periodically by the ASD-STAN TA members



06-2014 PAGE: 10 of 52

1.4 DOMAIN TECHNICAL COORDINATORS (DTC’S) a) Each Domain shall have a Technical Coordinator (DTC) nominated by the ASD-STAN members

and validated by the Board. The nominations are valid for an unlimited period of time and will be

reviewed periodically by the Technical Authority.

b) The DTC, in coordination with the Executive, is responsible for:

The creation and management of Sectors formed by the identified Experts;

The Validation of the nominations of Sector Leaders based on their qualification and

competence;

The approval of the action plan proposed for the work to be carried out and facilitate the work

in accordance with the defined process and in line with the agreed time schedule;

Participating in Technical Authority;

liaising between Domains or Sectors, with National Coordinators, Focal Points and with

external Organizations;

Assisting in the generation of business cases for standards (see Form 2-2);

Ensuring that for approved projects, there is no duplication with published or draft standards

at European or International level (in cooperation with the Sector Leader);

The validation of the technical content of documents;

Ensuring the good quality of the documents, including documentary architecture (Form 10-2);

Ensuring the process is being adhered too, including asking for feedback on any particular

concerns and for suggestions for improving the existing process;

For the organization of reviews of Sector Leaders activities and to report to the ASD-

STANTA and the Executive on the activities of the Domain.

c) Secretariat function in support of all the Domain Technical Coordinators is performed by the

Executive or by a National Standardization Body if available.

1.5 SECTOR LEADERS (SL’S) a) A Sector shall be chaired by a Sector Leader nominated by the sector members and confirmed by

the Domain Technical Coordinator. The nomination is valid for an unlimited period of time and

will be reviewed periodically by the DTC.

b) The Sector Leader proposes a Secretariat from one of the ASD-STAN members or its National

Standardization Organization to support all projects developed, to ensure the correct use and

application of the standardization process and to manage the communication amongst its

members.

c) The tasks of the Sector Leaders are to:

Define objectives, to own, to monitor and to update the agreed work program;

Facilitate the communication between all members within the Sector;

Maintain and make available a list of experts of its own sector;

Liaise with and report to the Domain Technical Coordinator, the Focal Points and the ASD-

STAN Executive;

Ensure liaisons to other Sectors, Domains and external organizations;

Ensure that for approved projects, there is no duplication with published or draft standards at

European or International level (in cooperation with the Domain Technical Coordinator);



06-2014 PAGE: 11 of 52

Achieve consensus and validate the technical content of their projects;

Manage the assessment and the validity of published EN standards in the context of the 5-

years review (Form 13);

Provide the Consensus Draft standards for ballot prepared by the Sector/Project Team

according to the Rules for drafting of European Standards (see Annex 2), accompanied by the

Form 6;

Ensure the good quality of the documents and ensure that drafts are prepared in line with the

rules for presentation including documentary architecture;

Ensure the consistency of draft documents with the general Organization of the relevant

Domain, in particular ensuring that any issued standards cannot be amended to reduce

(downgrade) the technical requirements that affect form, fit or function;

Ensure that the development of standards is done within the planned schedule;

If the Sector feels the need to determine a Vice Sector Leader, such decision may be

unanimously made by the Sector. The role of the Vice Sector Leader is to replace the Sector

Leader in case of absence.

1.6 SECTOR SECRETARIAT a) For each sector, a secretariat from one of the ASD-STAN member or National Standardization

Body is allocated in order to ensure the implementation of the standardization process and general

aspects of standardization. With its specific expertise on standardization, the secretariat supports

the Sector Leader and the Sector/Project Teams in all their duties.

b) The Executive ensures the balanced allocation of secretariats to the Sectors.

c) The allocated secretariat shall ensure the communication throughout the Sector and in particular

the identified Sector/Project Team. It shall support the activities of the Sector/Project Team,

invite for meetings as applicable, maintain meeting minutes and centrally collate and collect all

data and information related to the Working Draft development. The Sector Secretariat shall

supervise the compliance with action plans projected by Sector/Project Teams and with related

timing.

d) The Quality function in cooperation with the Sector Leader (see 1.5) is essential and has to be

coordinated through the relevant Sector Secretariat. This applies in particular to the rules

provided in Annex 2, to the rules of documents consistency (see fit-form-function in the glossary

section), to the referencing of Technical Specification for Product Standards, etc.

e) The Sector Secretariat has to ensure that the figures of the document are in line with the figures

drawing rules according to rules for the Drafting of European Standards.

1.7 EXPERTS (SECTOR MEMBERS) a) The Experts are nominated by the National Focal Points or by the CEN-CENELEC members as

their national representative via CEN Livelink, and notified to the Sector Leader and to the Sector

Secretariat. Their membership has to be recorded and has to be notified to the Executive.

Non-member individuals from companies or organizations outside of the ASD-STAN

membership community have to be notified to the Executive.



06-2014 PAGE: 12 of 52

b) The Experts within one Sector shall have a view on all projects within the sector and should

actively participate in several, if not all of the projects as a knowledgeable expert. An expert can

also take the task of Project Team Leader and can submit New Work Proposals (Originator).

c) Organizations as well as individuals are welcomed in order to provide additional expertise.

External (non-ASD-STAN member) participants in the Sectors or Project shall notify the

Executive and participation fees may apply (decision on a case by case basis). They however are

not part of the consensus building process and/or any voting.

1.8 SECTOR PROJECT TEAM Project Team members are the Expert members of a Sector. Usually a Project Team is formed by all

Experts of a Sector with the Sector Leader acting as Project Team Leader. Under specific

circumstances, such as not all Experts being available or sufficiently knowledgeable in respect of a

particular standard development, the Project Team may be formed by only the relevant Experts of the

Sector. The Project Team shall nominate a Project Team Leader in case the Sector Leader may not

already perform this task, and:

Define the action plan in order to prepare the Working Draft and implement it within the

agreed time scale;

Respect the purpose of the NWP / Standard project;

Respect the communication rules in cooperation with the Sector Secretariat;

Respect the rules for presentation of standards;

Gain consensus within the Team, and via the Sector Leader within the Sector, concerning the

technical content of a document;

Prepare the Consensus Draft based on the CEN-ISO template (see Annex 2);

Dispose of comments received within the Sector, after the National Domain Ballot, and after

the CEN-CENELEC Formal Vote (Form 9);

Report to the Sector Leader on the progress of the project

Submit all relevant documentation to the Executive;

Act with the support of the Secretariat allocated to the Sector.

1.9 ORIGINATOR a) The Originator of a standardization project can be any person from inside or outside the ASD-

STAN organization. The Originator submits a New Work Proposal (Form 1) and provides as

much as possible related information. The Originator will usually participate in the Sector/Project

Team which will prepare the related Working Draft document. If the Originator is from outside

the ASD-STAN organization, approval for his participation and the acceptance of related work

will be sought by the Executive at the ASD-STAN Board; participation fees may then apply.

b) New Work Proposal Originators are expected to propose particular Sector/Project Team members

for providing specific expertise in the standard development.

c) The Originator liaises with the Sector/Project Team regarding the disposition of comments.



06-2014 PAGE: 13 of 52

1.10 NATIONAL COORDINATORS a) Each country can have a National Coordinator nominated by its ASD-STAN Member Association

and appointed by the Board.

b) Such a National Coordinator will:

Arrange for a structure to ensure the representation of a national consolidated position;

Create, maintain and make available the national lists of Domain-competent Experts;

Facilitate the national work to be carried out, and monitor the voting / comment activities of

the national Focal Points for all the Domains;

Ensure sufficient communication within the national Technical Organization, and liaison with

external Organizations;

c) Respond, together with the national Focal Points where applicable, to inquiries and carry out any

actions required by the Board / Executive.

NOTE: This Process Manual does not imply any rules for ASD-STAN member’s internal national

work but only for cooperation within the ASD-STAN Technical Organization.

1.11 FOCAL POINTS (FP’S) a) Each Country shall have one Focal Point per Domain, nominated by the ASD-STAN Members

and validated by the Board. The Focal Point should arrange for a structure to ensure the

representation of a consolidated position on the projects.

b) Focal Points shall:

Arrange the vote on new projects (Form 3);

Ensure the representation of a consolidated position on the project;

Identify Experts for participation in Sectors (Form 3);

Arrange the vote on documents (Form 7);

Respond to inquiries and carry out any actions required by the Board/Executive or the Domain

Technical Coordinators;

Create, maintain and make available a list of competent Experts for nomination.

c) If a National Coordinator is implemented, the Focal Point shall:

Arrange the vote on new projects (Form 3);

Ensure the representation of a consolidated position on the project;

Identify Experts for participation in Sectors (Form 3);

Arrange the National vote on Consensus Draft (Form 7);

Respond, together with the National Coordinator where applicable, to inquiries and carry out

any actions required by the Board/Executive or the Domain Technical Coordinators.

1.12 THE EXECUTIVE The Executive is the permanent staff of the ASD-STAN Association according to the Statutes of the

organization. It currently comprises 1 Director and 2 Managers.

a) The Director is nominated by Promoting or Regular members, selected by the Board and

appointed by the General Assembly.



06-2014 PAGE: 14 of 52

The Director is the Chief Operating Officer according to the Statutes of the Association as registered

in Belgium, and is responsible for:

The achievement of the short and long term objectives of the Association in terms of quality,

users satisfaction and financial sustainability;

Preparing the business plan and the required reporting;

The management and day to day administration of the Association;

The administrative management of the activities of the Technical Organization;

Defining the working procedures of the Technical Organization;

The management of legal documents in accordance with Belgian law and the prescriptions of

the Board;

The operation of Information Technology Services to support the activities of the Association;

Proposing to the Board objectives and the most cost effective and efficient means for

achieving them, these may include:

Outsourcing of specific technical activities on competitive basis;

Adapting the in-house capabilities and capacities to the real needs;

Support to particular standardization projects;

The management of all external relations and collaboration issues;

The external representation and promotion reporting to the Board;

Organize reviews as necessary in order to fulfil the objectives;

Report to the board.

Ensure the application of the processes as defined in this General Process Manual.

b) The Technical Services Manager is nominated by the ASD-STAN Members and appointed by

the Board. He shall:

Assist the Director in his activities;

Be responsible for the co-ordination of the activities of the Technical Organization;

Ensure the Secretariat in support of the Domain Technical Coordinators in case no National

Standardization Body provides the Secretariat;

Support Sector Leaders and their Secretariats in their activities;

Facilitate liaisons between Domains or Sectors and external Organizations;

Establish and maintain a monitoring system (central data base) using the information provided

by the Domains, the Sectors and from the CEN-CENELEC;

Monitor and co-ordinate all standardization efforts;

Implement the procedures and establish tools for: ballots on drafts, publication of ASD

standards, presentation of standards to CEN-CENELEC for Formal Vote, presentation of

definitive text to CEN-CENELEC MANAGEMENT CENTRE;

Monitor the work planning;

Advise the Sectors Secretariats of CEN-CENELEC allocated WI numbers and of EN

numbers;



06-2014 PAGE: 15 of 52

Manage the publication and circulation of standards according to signed contracts between

ASD-STAN, the Subscribers, the Printing House or other Service Providers;

File all relevant documents (electronic);

Monitor and ensure balance of sectors secretariats allocation;

Be responsible for the start of the 5 year review of existing standards.

Use and maintain the content of the Livelink tool for ballots and communication with the

Domains, the Focal Points and the TA.

c) The Sales & Services Manager may be hired locally or nominated by the ASD-STAN Members.

He shall:

Manage the sales of standards documents, the contacts with customers and sub-contracted

distributors;

Monitor the payments of customers and suppliers, liaise with the accountant, the bank and the

Belgian authorities;

Ensure the availability of sustainable IT facilities supporting the ASD-STAN process;

Provide support to the other activities for which ASD-STAN is committed to (e.g. ASD,

IAQG, EDA);

Act as the Association’s representative in the Brussels central office and interact with the

regional representation offices.

The detailed description of the sales related processes is not part of this Process Manual. This is

covered by separate procedures

1.13 THE CEN-CENELEC LIVELINK 1. All ASD-STAN Domains and Sectors have to use the electronic IT system "CEN Livelink" and

the committee documents are available in CEN Livelink. Each ASD-STAN Domains and

sectors) have its own restricted CEN Livelink area. Only the members of the specific committee

have access to the documents in CEN Livelink.

2. Documents can be uploaded by the Domain/Sector Secretary and the Domain/Sector members

will be informed by e-mail automatically if new documents are online for download.

3. For each Domain and Sector, the members (Expert, Sector Leader, DTC and Secretary) have to

be registered by their National Standardization Body member of CEN. Contacts can be provided

by the Executive on demand.

4. The Executive is using CEN Livelink to distribute New Work Proposal, National Domain

Ballots, Fast Track and their results to the ASD-STAN Focal Points and the CEN-CENELEC

members. Even if ASD-STAN is not able to register members to CEN Livelink, the Executive

has to check and if necessary to remind that all ASD-STAN Focal Points and CEN-CENELEC

members have been registered in CEN Livelink in order to guarantee participation within the

NWP and ND Ballots



06-2014 PAGE: 16 of 52

2. THE PROCESS This section details the standardization process building on the definitions outlined in Section One and

identifies the steps in the process, the personnel responsible for each step and the procedures to be

followed. Figures 2a & 2b shows a high level view of the process and should be used, in conjunction

with Section One, as a reference throughout this section.

Besides the regular process (see 2.1) a Fast Track process (see 2.2) is available. The aim of the Fast

Track process is to offer a faster process under specific requirements. The New Work Proposal and the

National Domain ballots are starting at the same date and run in parallel with their respectives end

dates being after one month and after four months. In case the New Work Proposal ballot results

indicated that a new sector member wishes to participate in the project, the Fast Track is stopped and

the project is back to the regular process. Each ballot keeps the rules defined in the general process

manual (i.e. ballot closing date, Final result…) in order to be in compliance with the statutes of ASD-

STAN and in agreement with CEN-CENELEC. The Figure 3 and Figure 4 show the general view of

both processes.

A complete set of Forms can be found in the Annex 1 attached to this process manual.

There are no particular response times designated to the interaction between Project Team, Sector

Leader, Domain Technical Coordinator, Focal Points, Executive and other actors of the process. The

overall timing of the process is shown on Annex 3, CEN-CENELEC procedure.

The primary duty of ASD-STAN is the development and systematic review of self-generated EN

standards and Aerospace Industry standards.

ASD-STAN generated standards shall be developed on the basis of a project approach as shown in

Figure 2a and Figure 2b.



06-2014 PAGE: 17 of 52

Figure 2a: Project stages and associated documents for the Regular process

Process Step Stage Code Form Exec DTC FP SL PTL Orig

NWP issue 00.00 1 FA I S

NWP Assessment 00.20

(00.98)

2-1

2-2

A

I

I

A

I

I

Vote on NWP 10.00 3

(1 + draft)

S I V

Final Assessment, Launch

Project

20.00 (10.98) 4 S I

(A)

I C I

Preparation of WD,

Agreement of Sector/PT on

WD

20.20

20.99

(20.98)

6-1 + 6-2

6-1 or 6-2

FA

FA

I

I

S

S

FA

S

S

I

I

NDB / CEN-CENELEC

Enquiry

30.00 7+9(+CD) S

FA

I V

NBD / CEN-CENELEC

Enquiry Results

Disposition of comments

Summary Disposition of

comments

30.70 8

9

S

S

FA

I

I

I

I

FA

S

FA

Editing / Preparation of prEN

Publication - prEN Published

30.90

40.00

10-1,10-2,10-3 FA

FA

S S S

Review by users 9 C FA

Submission to CCMC for FV 50.00 S

CEN-CENELEC FV

CEN-CENELEC FV

results/comments

50.20

50.70

FA

C

I

FA

I

Preparation for publication 50.90

50.95

FA

C

EN publication 50.99

60.60

S

FA

Withdrawal of prEN 60.97 FA

S= Submit, V= Vote, I= Information, A= Approval, C= Communication, FA= Further Action

Note: timing according the Annex 3



06-2014 PAGE: 18 of 52

Figure 2b: Project stages and associated documents for the Fast Track process

Process Step Stage

Code

Form Exec DTC FP SL PTL Orig

NWP issue and Preparation of WD 00.00 1 + draft FA I S

NWP Assessment

00.20

(00.98)

2-1

2-2

A

I

I

A

I

I

Agreement of Sector/PT on WD 20.20

20.99

(20.98)

6-1 + 6-2

6-1 or 6-

FA

FA

I

I

S

S

FA

S

S

I

I

Vote on NWP 10.00 3

(1 + draft)

S I V

NDB / CEN-CENELEC Enquiry 30.00 7+9(+CD) S

FA

I V

Final Assessment, Launch Project 20.00

(10.98)

4 S I

(A)

I C I

Preparation of WD,

Agreement of Sector/PT on WD

20.20

20.99

(20.98)

6-1 + 6-2

6-1 or 6-2

FA

FA

I

I

S

S

FA

S

S

I

I

NDB / CEN-CENELEC Enquiry 30.00 7+9(+CD) S

FA

I V

NBD / CEN-CENELEC Enquiry Results

Disposition of comments

Summary Disposition of comments

30.70 8

9

S

S

FA

I

I

I

I

FA

S

FA

Editing / Preparation of prEN Publication -

prEN Published

30.90

40.00

10-1,10-

2,10-3

FA

FA

S S S

Review by users 9 C FA

Submission to CCMC for FV 50.00 S

CEN-CENELEC FV

CEN-CENELEC FV results/comments

50.20

50.70

FA

C

I

FA

I

Preparation for publication 50.90

50.95

FA

C

EN publication 50.99

60.60

S

FA

Withdrawal of prEN 60.97 FA

S= Submit, V= Vote, I= Information, A= Approval, C= Communication, FA= Further Action

Note: timing according the Annex 3



06-2014 PAGE: 19 of 52

Figure 3: Regular ASD-STAN Standardization Process

Form 1 Form 1

DTC

Form 1

Forms 2

Form 4 Form 7 Form 8

prEN

Forms 10

S S

New Work Proposal (NWP) Stage

2 months

Working Draft Stage

4 months

National Domain Ballot (NDB) Stage

6 months

Forms 6 Form 3

NWP Ballot 1 month

Form 7

ND Ballot 4 months

CEN Members :

for information CEN Members :

for comments

DTC Domain

Technical Coordinator

S = Signature

Executive

Sector Form 9

S

Form 3

6 FP

Draft

Draft Draft Draft

Form 9

Draft

CEN: European Standardization

Organization

Originator

Form 9



06-2014 PAGE: 20 of 52

Figure 4: Fast Track ASD-STAN Standardization Process

New Work Proposal (NWP) and National Domain Ballot (NDB)

Fast track Stage

7 months

DTC

Form 1 Form 4 Form 7 Form 8

prEN

Forms 10

S S

Form 1

NWP Ballot 1 month

Form 7

ND Ballot 4 months

CEN Members : for information

CEN Members :

for comments

Sector Form 9 Form 3

Executive

6 FP

DTC Domain

Technical Coordinator

S = Signature

CEN: European Standardization

Organization

Forms 2

Forms 6

Draft

Draft

Form 1

Originator Draft

Form 3

Forms 2

Form 9

Draft

Form 9



06-2014 PAGE: 21 of 52

Figure 5: CEN-CENELEC Process to transform prEN into EN Standard

Formal Vote (FV) Stage EN Publication Stage

Enquiry stage

2 months

5.5 Months 3 Months

EN



06-2014 PAGE: 22 of 52

2.1 REGULAR PROCESS This section describes the steps as a basis canvas that can be followed chronologically (regular

process) or some steps carried on in parallel (Fast Track process, see section 2.2). While the Fast

Track Process is most likely to be preferred, each project will determine the best procedure to be

carried out to get a robust standard.

2.1.1 THE PROPOSAL STAGE (00.00) – FORM 1 a) A New Work Proposal (NWP) is a proposal for a new standard, a new part of an existing

standard, a Technical Report, a Revision of an existing standard or part i.e. after the review of a

standard has indicated a need for a Revision.

b) A New Work Proposal can be submitted by Sector Leaders, Focal Points, Domain Technical

Coordinators, National Coordinators and Experts. The person submitting the NWP is called the

Originator.

c) Each New Work Proposal shall be presented by the Originator using the Form 1.

d) The Originator shall:

Indicate which kind of deliverable is proposed;

provide a first working draft or an outline of such a working document;

Suggest potential additional participants to a related Sector / Project Team if possible.

Indicate potential implications from patents, licenses, intellectual property rights.

e) The completed Form 1 shall be sent to the Executive by the Originator or on behalf of the

Originator by the National Standardization Body. The responsibility remains with the Originator.

f) Each New Work Proposal shall be submitted by using separate Form 1.

2.1.2 NEW WORK PROPOSAL ASSESSMENT (00.20) – FORMS 2-1 & 2-2 a) The New Work Proposal (NWP) shall be evaluated:

Commercially by the Executive.

Technically by the relevant Domain Technical Coordinator.

b) The Executive shall complete the Form 2-1 and the Domain Technical Coordinator shall

complete Form 2-2. They will identify applicability of the Vienna Agreement. In case a Domain

Secretariat is identified to support the DTC, the Secretariat may complete the Form 2-2 but the

responsibility remains with the DTC.

c) They will take a joint decision on the further progress of the New Work Proposal.

d) If the NWP is rejected (00.98) by the Domain Technical Coordinator and/or by the Executive, the

completed Form 2-1 shall be sent with comments by the Executive to the Originator and the

Domain / Sector Secretariat. The Originator may appeal to the Technical Authority regarding the

rejection.

2.1.3 VOTE ON NEW WORK PROPOSAL (10.00) – FORM 3 a) In order to establish project support, the NWP shall be submitted to the Focal Points of the

relevant Domain for vote.

b) The Executive shall send to the Focal Points and the Originator:

The Form 3 with the first frame pre-filled with the project info, reference numbers and ballot

dates;



06-2014 PAGE: 23 of 52

The Form 1 and the draft (if available);

c) The Executive will also send the NWP to the CEN-CENELEC members for advanced

information and invitation to participate.

d) The Focal Points shall:

Issue the Form 1 and the draft to interested parties in their area for comments;

Rationalize comments and complete the Form 3;

Review the list of experts from their country, confirm the participants and/or propose new or

additional Experts;

Return the completed Form 3 to the Executive within the time limit specified on the Form 3

(ballot closing date).

e) The New Work Proposal Ballot is open for 1 month and closes at 11:59 pm of the closing date.

2.1.4 FINAL ASSESSMENT AND LAUNCH OF PROJECT (20.00) – FORM 4 a) The Executive shall compile the results of voting using the Form 4.

b) There shall be at least 3 valid votes and the result is established by simple majority. There is one

vote per ASD-STAN member country.

In case of insufficient votes, the Executive will contact the responsible Focal Points for a

reminder.

c) The Domain Technical Coordinator and the Executive shall take a joint decision on the further

progress of the New Work Proposal in case of an insufficient number of votes or rejection

(10.98).

d) The Domain Technical Coordinator and the Executive shall take a joint decision on the further

progress of the New Work Proposal in case of an insufficient number of votes, tie or rejection

(10.98)

e) If the proposal is supported, the Executive establishes a work planning.

f) The completed Form 4 is sent to the Sector Leader who forwards the Form 4 to the identified

Sector/Project Team, with support from the Sector Secretariat. It is also sent in copy to the

Originator, the Focal Points, the Domain Technical Coordinator and to the ASD-CERT Executive

Board.

g) The Executive informs CEN-CENELEC after a positive NWP result in order to request to

generate a new project in the CEN-CENELEC database. (See Annex 3)

2.1.5 PREPARATION OF WORKING DRAFT (WD) (20.20) Based on the Form 4, the Sector Leader with the support of the Sector Secretariat and the Originator

has to decide if a Project Team is established or if all Experts of the Sector will be working on the

project. In case a Project Team is established, a Project Team Leader has to be assigned.

The Sector/Project Team is responsible for the preparation of the Working Draft (WD)

a) The identified Sector/Project Team, under the leadership of the Sector/Project Team Leader and

with the support of the Sector Secretariat shall prepare the Working Draft in English and in

accordance with the Rules for the Drafting of European Standards (see Annex 2).

b) The Sector/Project Team shall work within the Work Plan established on the Form 4.



06-2014 PAGE: 24 of 52

c) The Sector/Project Team shall be responsible to instruct EN 9133 as a mandatory requirement in

Product Standards when a Technical Specification exists.

d) The Working Draft shall be circulated to the Sector/Project Team and potentially to the other

Sector members for consensus. It is the responsibility of the Sector/Project Team Leader to

achieve consensus on a WD. It is expected that consensus be achieved with no actual voting. In

exceptional cases, the issues might be escalated to the Domain Technical Coordinator.

e) The responsibility for technical content is with the Sector/Project Team preparing the standard

and with the appropriate Sector and its Sector Leader.

2.1.6 AGREEMENT ON CONSENSUS DRAFT (CD) (20.99) – FORMS 6 a) The Sector/Project Team Leader shall confirm Team consensus (20.99) and the Sector Leader

shall send to the ASD-STAN Executive the Consensus Draft confirming that consensus has been

reached amongst all Sector members by use of the Form 6-1 and/or Form 6-2 to the Executive

for further action, and to the DTC and to the Originator for information.

b) If a project is intended to be cancelled (20.98) for any reason, and as agreed by the sector, the

Sector/Project Team Leader shall immediately notify the Executive by return the Form 6-2,

including a justification for the cancellation for further announcement to the Technical Authority.

c) In case the project team recommends the cancellation of a project, the Project Team Leader shall

immediately notify the Sector Leader with Form 6-1. Afterwards the Sector has to agree as

described above.

NOTE: When the whole sector acts as a Project Team, only the Form 6-2 is sufficient.

2.1.7 NATIONAL DOMAIN BALLOT (NDB) ON CONSENSUS DRAFT / CEN-

CENELEC ENQUIRY (30.00) – FORMS 7 & 9 a) The Executive will prepare a Form 7 by filling in the project information in the first frame,

references and ballot dates. He shall circulate the Consensus Draft (CD) together with the Form 7

for completion to the Focal Points of the relevant Domain for ballot and to the Domain Technical

Coordinator for information.

b) Focal Points shall:

Issue the CD to interested parties in their area for approval/comments;

Compile comments received from the interested parties onto the Form 9;

Return the duly completed and signed Form 7 and Form 9 (if applicable) to the Executive

within the time limit specified on Form 7 (4 months).

c) The UK Focal point shall check the English Title and the French and the German Focal Points

shall check the translation of the proposed title of the draft. If necessary a corrected translation

shall be provided with the comments in the Form 9

d) There shall be at least 3 valid votes and the result is established by simple majority. There is one

vote per ASD-STAN member country. The answer "no national interest/expertise" in Form 7 is

counted as a valid and positive vote.

e) The CD is also distributed by the Executive to all CEN-CENELEC members for their comments.



06-2014 PAGE: 25 of 52

2.2 FAST TRACK PROCESS The Fast Track process provides a faster process than the regular process. The Fast Track process is

open for all kind of projects e.g. revisions, a new part to an existing prEN family or even a completely

new prEN. However the following described conditions have to be fulfilled to start the Fast Track.

Even then the Fast Track process might fail because new experts have to be included into the

standardization work and/or major comments occur in the New Work Proposal ballot. The process is

based on the principles of openness, transparency, consensus and balance

a) All following conditions shall be met:

1) An Originator and Project Team Leader and/or a Sector Leader shall be identified and

required to do the report to the sector and manage the disposition of comments with the Sector

(Form 1). A responsible existing Sector Leader is necessary.

2) A Consensus Draft shall be attached to Form 1 and its content shall conform to the Rules for

Drafting of European Standards and be mature in regards to the technical content (to be

checked by the Domain Technical Coordinator and by the Sector Leader).

3) Approval from the Executive (Form 2-1) for a Fast Track.

4) Approval from the Domain Technical Coordinator (Form 2-2) for a Fast Track.

5) In case there is a specific Project Team Leader (who is not the Sector Leader) the approval

from the Project Team Leader (Form 6-1) for a Fast Track is necessary. The Project Team

Leader has to confirm that the consensus has been reached within the European ASD-STAN

project team members for the Fast Track and for the submitted Consensus Draft. In case there

is no specific Project Team Leader or the Project Team Leader is the Sector Leader Form 6-1

is not necessary but Form 6-2 has to be provided.

6) Approval from the Sector Leader (Form 6-2) for a Fast Track. The Sector Leader has to

confirm that the consensus has been reached within the ASD-STAN sector for the Fast Track

and for the submitted Consensus Draft.

When all conditions are met, the ASD-STAN Executive will start the Fast Track process.

b) Other Conditions:

The details of the other conditions that are not described in this process are identical to the Regular

process (see 2.1).

2.2.1 BALLOTING The Executive conducts both ballots at the same time: a New Work Proposal (NWP) ballot and a

National Domain Ballot (NDB) (including CEN-CENELEC enquiry). All information is recorded by

the Executive in the ASD-STAN database and the 2 ballots get the same start date.

Time: 4 months = 4 months for NDB, including 1 month for NWP ballot.

Focal Points shall send 2 answers with the associated forms, one reply for the NWP ballot and one

reply for the NDB.



06-2014 PAGE: 26 of 52

This Fast Track process could be stopped by national Focal Points during the NWP ballot (i.e. major

comments or new expert(s) participation is required).

2.2.2 FINAL RESULT: WITH THE RULES DEFINED IN THE PROCESS MANUAL

SECTIONS 2.1.4 AND 2.3: 1st case: The NWP is accepted and the NDB is accepted without comments. The Executive sends the

final results (Form 4 and Form 8) and prepares the document for publication.

2nd case: The NWP is accepted and the NDB is accepted with comments. The Executive sends the

final results (Form 4, Form 8 and Form 9) and the Sector Leader shall prepare the disposition of

comments. Then the Executive sends the document for publication

3rd case: The NWP is accepted and the NDB is refused. The Executive sends the final results (Form

4, Form 8 and Form 9) and the Sector shall prepare a new draft for a new National Domain ballot. In

this case, the project returns to the regular process, after the New Work Proposal ballot, i.e.

preparation of Working Draft (stage code 20.20).

4th case: The NWP is refused. The Fast Track is stopped (early termination of the NDB) and the

Executive sends the final results (Form 4) and the project is cancelled (10.98).

5th case: The NWP is accepted but a Focal Point proposes a new member to participate to the project.

In this case the Fast Track is stopped and the project returns to the regular process. The Executive

sends the final result (Form 4) and the Sector Leader shall form a Project Team and invite the new

expert to prepare a new draft for a new National Domain Ballot.

NOTE: Whenever the Fast Track process is stopped, due to whatever reason, all results and documents

from completed working processes are maintained and applied in the regular process steps.

2.3 RESULTS OF NATIONAL DOMAIN BALLOT (30.70) – FORM 8 a) Upon expiry of the ballot, the Executive shall prepare the report of National Domain Ballot

voting and CEN-CENELEC Enquiry and take decision on the further progress, see Form 8. The

Executive will also allocate a prEN number.

b) If there are any comments, the Executive shall send the consolidated Form 9 to:

The Sector Secretariat;

Sector Leader or Project Team Leader.

c) The Executive will send to the Focal Points for information:

The ballot results (Form 8) and;

The consolidated comments (Form 9), if any.

d) The Sector/Project Team with the support from the Secretariat shall do the disposition of

comments on Form 9 and incorporate the result of the disposition of comments into the

Consensus Draft and submit them to the Executive for further action. The Sector Secretariat shall

provide the result of the disposition of comments (in Form 9) and the adapted consensus draft to

the Sector for information only.

e) In case no consensus can be reached regarding the disposition of comments and the incorporation

in the document, the issue is to be escalated to the Domain Technical Coordinator for mediation.



06-2014 PAGE: 27 of 52

If necessary the DTC may advise the Technical Authority for final level of escalation and

decision.

2.4 PUBLICATION (40.00) – FORMS 10 The Executive asks a contracted service provider (with the responsible sector secretary in copy) to

prepare the prEN publication version based on the National Domain Ballot result and the results by the

Sector of the disposition of comments with the Definitive Text. The service provider provides to the

executive the final prEN publication version. The Executive provides the final prEN publication

version to the responsible Sector Leader, to the Domain Technical Coordinator and to the Sector

Secretary for final approval with the individual Forms 10. In addition, the UK, FR and DE focal

points will be asked by the Executive to approve the correct translation of the national title, see 2.4 a.

a) After approval:

By the Sector / Project Team Leader, having checked that the disposition of comments has

been integrated and interchangeability is guaranteed (Form10-1);

By the DTC for approval of the technical content, see Form 10-2;

By the Sector Secretariat for the quality of the revised CD and for ensuring that the procedures

for the preparation of ASD-STAN generated standards have been followed, see Form 10-3;

By the UK, FR and DE focal point approval of the correct translation of the national title

The Executive shall launch the publication of the revised Consensus Draft as prEN. The publication

notice will appear in the next Newsletter.

First edition of prEN is called P1 on prEN title page, following possible revisions has to be named P2,

P3…

b) The Executive shall launch the prEN/EN transformation procedure upon the publication of any

prEN standard. It is expected that the transforming process into EN standard covers enough time

to allow for a review by users.

2.5 REVIEW BY USERS / PREN TO EN PROCESS – FORM 9 a) The published prEN will be reviewed by users.

b) All comments on published prEN shall be sent to the Executive using a Form 9 within 6 months

after the date of prEN publication. Such review may already happen during the phase of CEN-

CENELEC Formal Vote.

c) If comments are received by the Executive, the Form 9 shall be sent to the Sector/Project Team

Leader of the relevant prEN. The Sector/Project Team Leader shall prepare the summary and, in

cooperation with the Sector / Project Team, the disposition of comments onto Form 9.

d) If modifications to the prEN do not affect interchangeability, the Sector/Project Team Leader

shall incorporate the approved modifications in the final draft before submission to CEN-

CENELEC MANAGEMENT CENTRE for Formal Vote. If the EN publication process has

already passed the FV stage, the Executive advises the CEN-CENELEC Management Center.

e) If modifications to the prEN affect interchangeability, the prEN shall be declassified (40.96), and

the EN publication process shall be stopped. The Sector/Project Team Leader shall initiate the

preparation of a new Working Draft according to the procedures after, and including, 2.1.7. This



06-2014 PAGE: 28 of 52

new WD may result in a standard with a new prEN number or a new variant to the previously

allocated prEN number.

f) The ASD-STAN Executive will prepare the prEN document for submission to CEN-CENELEC

Formal Vote. This work may be done with the help of a service provider.

g) Stage 1 of the prEN-EN transforming process should be initiated within one month after prEN

publication.

2.6 CEN-CENELEC FORMAL VOTE (50.00 – 50.20) a) Stage 50.20 should not be initiated before 6 months after the publication 40.00

b) The Executive shall submit the Final Draft to CEN-CENELEC Management Center using the

relevant procedure agreed with CEN-CENELEC.

c) For circulation procedure to CEN-CENELEC members, see CEN-CENELEC Internal Rules as

published by CEN-CENELEC on their website.

2.7 FORMAL VOTE RESULTS (50.70) a) The CEN-CENELEC Management Center will submit the results of the Formal Vote to the

Executive.

b) The Executive shall submit the results of the Formal Vote together with comments:

To the service provider for “Transforming prEN-EN – stages 2 & 3”;

In copy to the Sector/Project Team Leader for disposition of comments if there were any

comments.

c) The Sector/Project Team Leader shall:

Prepare the disposition of comments, if any, see Form 9, and according to the rules about

interchangeability established in 2.4 above;

Revise the final draft accordingly;

Submit the revised final draft to the service provider.

d) The service provider shall prepare the definitive text and send it to the Executive.

The Executive makes a final check and sends the document to the CEN-CENELEC Management

Center using the relevant CEN-CENELEC procedure for EN publication.

e) There is no change of the technical content of a standard allowed to result from the Formal Vote

process. In case of such change requirements occurring, the prEN needs to be withdrawn and a

New Work Proposal is prepared.

2.8 CEN-CENELEC PUBLICATION AND AUTOMATIC WITHDRAWAL OF

PREN(60.60 & 60.97) a) The relevant ASD-STAN standards which have been adopted by CEN-CENELEC and which

have been made available by the CEN-CENELEC Management Center as EN shall be withdrawn

by ASD within a period of six months after the date of availability.

b) This withdrawal shall be recorded by ASD-STAN with periodical updates.

NOTE: Procedure for ratification, availability and publication as National Standards, see CEN-

CENELEC Internal Rules.



06-2014 PAGE: 29 of 52

2.9 REVIEW OF EN STANDARD (5 YEAR REVIEW) (STAGE 90)–FORM 13 a) According the Rules of CEN-CENELEC, EN standards have to be reviewed after a 5-year period

in order to check, if the EN standard represents the best possible solution for European

application at present.

b) Every January of a year, the Executive provides a list of ENs that has to be reviewed by the end

of the year. The Executive contacts the ASD-STAN focal points and the CEN-CENELEC

members and starts a 3 month periodic review ballot with the Form 13 and the Form 9.

c) Each ASD-STAN Focal Point and the CEN-CENELEC members have to vote with the Form 13

for each EN and give one of the following answers:

Confirmation without changes (for further 5 years);

Withdrawal (explanation is necessary);

Revision with editorial and/or technical changes (explanation is necessary);

Declassification (explanation is necessary).

d) The Executive provides the results with Form 14 to the ASD-STAN Focal Points and the CEN-

CENELEC members for information only. The Executive provides the results ordered by sector

to each Sector Leader and sector secretariat.

e) The Sector Leader and Sector Secretariat inform his sector about the results. The Sector checks

the review result and starts with the implementation of the result in case a consensus can be

agreed by the sector.

f) By the end of each year the Sector Leader and Sector Secretariat inform the responsible Domain

Technical Coordinator and the Executive about the decision of the sector and the status of the

implementation of the review result.

g) If the result of voting indicates that a revision or new edition of the EN standard is necessary, the

next step shall be the New Work Proposal ballot (Revision).

2.10 REVISION OF PUBLISHED DOCUMENT a) All comments including user feedback shall be sent to the Executive using a Form 9. The Form

9 shall be sent to the Sector/Project Team Leader of the relevant prEN. The Sector/Project Team

Leader shall prepare the summary and, in cooperation with the Sector / Project Team, the

disposition of comments onto Form 9. The Sector/Project Team Leader can give a

recommendation to initiate, postpone or reject a revision with a NWP ballot

b) In any case, the originator of the comments is informed about the decision.

c) To respect the principle of transparency, the process for the Revision has to follow the complete

ASD-STAN process, from the New Work Proposal stage (See 2.1.1).

d) A record of the changes and related justification shall be added and be marked with a line in front

of the affected text for easy identification to the document.

e) The modifications to the standard shall not affect interchangeability. If the modifications affect

interchangeability, the Revision shall be treated as a New Work Proposal and result in a standard

with a new number or if possible, with a new code in the identity block of designation.

Additionally a decision by the Domain Technical Coordinator has to be taken, if there is the

necessity to declassify the standard, for which the revision was intended.

f) An evolution sheet (see Annex 6) has to be submitted with Form 1 for each revision by the

originator. The Evolution sheet should contain only the main changes in comparison with the



06-2014 PAGE: 30 of 52

previous edition (especially about interchangeability purpose. In the future revisions, the

evolution sheet may cumulate the history of the changes between previous editions. The Final

version of the Evolution sheet is under the control of the Sector. The evolution sheet will be

published as an informative Annex with the prEN and with the EN.

2.11 DECLASSIFICATION (DC) a) A published prEN or EN shall be declassified i.e. inactive for new design (stage code 40.96), for

the following reasons:

Modifications of the technical content affecting interchangeability and/or;

Availability of another standard recognised world-wide which is applicable and/or;

The technical content became obsolescent but it can be used by an old programme.

a) The Sector shall submit the request for declassification to the Domain Technical Coordinator and

Executive for approval. The sector shall investigate the impact of the declassification before such

a request.

b) This process is eligible for a Fast track process.

c) In case of a replacement document exists, it shall be mentioned on the coversheet.

d) In exceptional cases prEN Standard can be declassified without a replacement document.

e) Declassification is initiated by ASD-STAN and appropriate notification given to CEN-CENELEC

Management Center.

f) An appropriate indication is printed onto the cover of the declassified standard. A coversheet is

published with the mention in the front page "Inactive for New Design" (See example in Annex

5) replaced by EN XXXX (if applicable) and the previous content is attached to the coversheet.

g) Declassification may also apply to a part of a standard (e.g. For such and such sizes or options)

2.12 WITHDRAWAL (RT) a) A prEN/EN shall be withdrawn (stage code 40.95) for the following reasons:

Availability of the corresponding EN Standard; The withdrawal of the prEN by ASD-STAN

after EN publication by CEN-CENELEC is an automatic process and does not include a

further decision step nor publication of a coversheet;

Previous modifications of the technical content affecting Interchangeability;

Impossibility to meet the requirements of the standard.

b) The Sector shall submit the proposal for withdrawal with a Form 1 explaining the reason, to the

Domain Technical Coordinator and Executive for approval. This process is eligible for a Fast

track process.

c) When the decision for withdrawal is taken if the replacement document is available, it shall be

referenced in the cancelled document.

d) Withdrawal is initiated by ASD-STAN and appropriate notification given to CEN-CENELEC

Management Center

e) An appropriate indication is printed onto the cover of the withdrawn standard. A coversheet is

published with the mention in the front page "WITHDRAWN STANDARD" (See example in

Annex 7) and the previous content is removed from the standard.



06-2014 PAGE: 31 of 52

2.13 TRANSVERSAL PROJECT a) Transfer of a project from a domain to another domain

The sector requesting to integrate the project to their Work Program, shall contact the ASD-STAN

Executive and the Sector Leader shall justify his request.

The ASD-STAN Executive shall contact the original Domain Technical Coordinator and Sector

Leader in order to get both of their approval.

Disapproval shall be justified and the Sector, requesting the transfer, shall be informed of the Final

decision by ASD-STAN Executive.

In the case of an approval, the original Domain Technical Coordinator/Sector Leader can decide to

transfer all activities of the project to the new Domain Technical Coordinator/Sector Leader or can

decide to do cooperation (see 2.13 b). The lead of the project is decided by the original Domain

Technical Coordinator/Sector Leader.

b) Cooperation between several domains

The Domain/Sector requesting the cooperation, shall contact the ASD-STAN Executive.

A project involving several domains shall have only one lead Domain/Sector.

The lead is defined at the NWP stage by the ASD-STAN Executive, if applicable or by the TA.

The ASD-STAN Executive shall contact the lead Domain and Sector in order to get both of their

approval.

Disapproval shall be justified and the sector, requesting the cooperation, shall be informed of the final

decision by the ASD-STAN Executive.

In the case of an approval, the project follows the process of ASD-STAN for the establishment and

publication of the standard with the following dispositions:

For each ballot (NWP & NDB), only the lead Domain can vote and the other Domain involved

can only provide comments.

The lead Domain/Sector shall involve all Domains/Sectors concerned in the preparation of the

Working Draft, the agreement on the Consensus Draft, the Disposition of Comments and the

Revision.

2.14 PUBLICATION OF ASD-STAN Technical Report The regular process without National Domain Ballot meaning after the agreement in the sector (Form

6-1), the publication process with Forms 10 applies.



06-2014 PAGE: 32 of 52

3. SPECIAL PROJECTS

3.1 VIENNA AGREEMENT Acting within the procedural environment of CEN-CENELEC standards development, ASD-STAN

commits to the so-called Vienna Agreement between CEN-CENELEC and ISO, allowing common

standards development. As part of the evaluation New Work Proposal, it will be determined if

resulting standards work should be directed to or performed in cooperation with ISO.

3.2 EU PROJECTS Based upon particular contracts, European Union tasked activities may require the work results being

published as European Standards. For such purpose ASD-STAN provides the organizational

environment. Appropriate initiation of standards development will be mirrored as New Work Proposal

and published similar to regular ASD-STAN standards work for participation of interested parties. All

steps of related standards work will be identical to regular ASD-STAN standards work. Regular

processes apply to the sequence of forms and signatures.

3.3 IAQG QUALITY STANDARDS The International Aerospace Quality Group is regionally supported by ASD-STAN for the

development and publication of their standards for Europe. For this purpose the initiation of standards

development will be mirrored as New Work Proposal and published similar to regular ASD-STAN

standards work for participation of interested parties. All steps of related standards work will be

identical to regular ASD-STAN standards work. Regular processes and timing apply to the sequence

of forms and signatures.

3.4 AIRBUS EUROPEAN STANDARDS RELATIONSHIP WITH ASD-STAN Airbus, as major European aircraft manufacturer, produces many internal technical standards which

may be desired to be made publicly available. In order to allow for such public availability, ASD-

STAN accepts the submission of Airbus technical standards for recognition as ASD-STAN standards

and subsequent transformation to EN standards. For this purpose ASD-STAN reserves the EN6000-

series numbering for Airbus originating technical standards.

An appropriate Airbus technical standard is submitted by the Airbus Technical Documentation

department to the ASD-STAN Executive. This submission includes a properly prepared standard

document according to the ASD-STAN and CEN-CENELEC rules. The ASD-STAN Executive

allocates it to the applicable ASD-STAN Domain/Sector. The Airbus originating standard document

will follow Fast Track process if the conditions are fulfilled, beginning with ASD-STAN Form 1.

NOTE 1: ASD-STAN retains the right to accept or to reject Airbus technical standard submissions. It

also requires Airbus to properly dispose all comments following completion of the National Domain

Ballot. The final decision to accept the completed disposition of comments (acceptance or rejection of

comments) remains with the appropriate ASD-STAN Sector Leader and, in case of escalation, with the

ASD-STAN Domain Technical Coordinator.

NOTE 2: The primary aim of above process is to allow for internal Airbus technical standards to

become publicly available as European Aerospace standards without major changes to the content of



06-2014 PAGE: 33 of 52

the original internal Airbus technical standards. Revisions to such standards can at any time be

processed through the appropriate ASD-STAN Domain/Sector as part of their regular technical work

and processes.



06-2014 PAGE: 34 of 52

4. GLOSSARY This section provides a comprehensive glossary of Standardization terms used in the process manual

and associated documents.

4.1 BOARD The decision making body of ASD-STAN. Decisions will be taken by correspondence or at meetings.

4.2 BUSINESS CASE/ COST EFFECTIVENESS Procedures which take into account the total cost of the standardization work. The total cost includes

direct expenditures by ASD-STAN members, expenditures by the Executive, travel costs and the value

of the time spent by the designated, Experts and Specialists in the Sectors.

NOTE: The following rules shall be applied:

Avoid any duplication of work being carried out by other European or International

Standardization Organisations;

Rationalise and limit the range of subjects to be standardized to program/project needs;

Take note of the requirements of European Aerospace program/projects;

Take into account the respective level of science, technology and experience and promote the

technical development.

4.3 CANCELLATION In the case that insoluble profound disagreement affecting the content or the application of the

Working Draft occurs, the Sector Leader may ask the Executive and the Domain Technical

Coordinator to remove the study from the work program of the Sector (related stage code: 20.98).

4.4 CEN-CENELEC FORMAL VOTE CEN-CENELEC procedure through which a prEN is adopted by CEN-CENELEC as a European

Standard.

NOTE: All votes shall be unconditional. Technical comments shall be noted and considered for a next

edition. Editorial comments may be incorporated.

4.5 CONSENSUS a) General agreement characterised by the absence of sustained opposition to substantial issues by

any important part of the concerned interest and by a process that involves seeking to take into

account the views of all parties concerned and to reconcile any conflicting arguments.

NOTE: Consensus needs not to imply unanimity.

b) Consensus is an essential principle and necessary for the preparation of European Aerospace

standards, which will be widely accepted and used. This consensus shall respect the need

expressed in the initial request.

c) Although it is necessary for the standardization work to progress speedily, sufficient time shall be

allowed before the approval stage for discussing, negotiating and solving significant technical



06-2014 PAGE: 35 of 52

disagreements. All available electronic tools should be used wherever possible along the entire

Standardization process so as to maximise the time spent on value added activities.

d) The standards shall not contain any requirement, which is contrary to legal restrictions, nor

encourage any privilege.

4.6 CONSENSUS DRAFT (CD) Working draft document, having achieved consensus/approval within a Sector and being ready for

submission to National Domain Ballot.

4.7 COVERSHEET (CS) In exceptional cases, specific sheet with a prEN number allocated which can be used for the

recognition of a document originating from outside of the ASD-STAN environment.

NOTE 1: Reasons could be:

Lack of time;

Reference to a specific edition of a recognised standard (excluding ISO/IEC or EN standards);

A Sector may propose the coversheet method for a well-recognised standard. The proposal

shall be submitted to the Domain Technical Coordinator and Executive for approval.

NOTE 2: It is common understanding that those coversheets shall be transformed into full EN

standards or replaced by direct normative reference.

NOTE 3: This process has been used in the past to allow the inclusion of foreign normative references.

However current European Standardization rules make the use of Coversheets in those circumstances

obsolete.

4.8 DEFINITIVE TEXT Text of a CEN-CENELEC adopted prEN prepared by Executive for submission to CEN-CENELEC

Management Center to make an EN available.

4.9 DISCIPLINE a) Each Sector shall have a Sector Leader.

b) Designated Focal Points, Technical Coordinators, Sector Leaders and Project Team Leaders and

Experts shall ensure discipline with respect to deadlines and timetables.

c) To avoid re-discussion, any designated member shall ensure that the technical standpoint of his

area is established taking into account all interests concerned at his level, and that this standpoint

is made clear at an early stage of the work rather than at an advanced stage in the procedure (for

example, at the final draft stage for presentation to CEN-CENELEC Formal Vote).

d) Moreover, designated members shall recognise that substantial comments tabled at meetings are

counter-productive since there is no opportunity for other representatives to carry out the

necessary consultations on their level.

e) Domains may take resolutions covering their internal procedures. These resolutions however,

shall not be in contradiction with the Process Manual or decisions of the ASD-STAN Board or

Technical Authority.



06-2014 PAGE: 36 of 52

4.10 DOMAIN a) Domains are established by the Board in order to provide coherent coordination, planning and

programming of standardization activities within a particular area. On request of a Domain the

Board will decide on its possible subdivision.

b) The Domains are established by the Board.

c) The members of a Domain are:

The Domain Technical Coordinator;

Delegates nominated from ASD-STAN Board members acting as Focal Points;

The Sector Leaders;

The Sector members (Experts) acting in Sector/Project Teams;

Representatives of National Standardization Organizations in liaison with the relevant

Domain;

National Coordinators who may participate in the Domains and in the Sector/Project Teams.

4.11 DOMAIN TECHNICAL COORDINATOR A person delegated by the Board to guide all Sectors in the relevant Domain in accordance with the

processes described in this General Process Manual.

4.12 ESCALATION IN CASE OF MAJOR ERRORS DETECTED IN STANDARDS Any major error in standard reported to the ASD-STAN Executive is investigated by the Executive

with the relevant Domain/Sector Leader. Appropriate measures will be taken by the Executive (e.g.

publication of a warning note, withdrawal of prEN/EN, technical occurrence report to EASA).

4.13 EUROPEAN STANDARD (EN) ASD-STAN has the authority to generate “Aerospace Series” prEN standards which are submitted to

the CEN-CENELEC Formal Vote to be published as EN standards. Once approved by CEN-

CENELEC members the EN standard carries with it the obligation that it shall be implemented at

national level by being given the status of a national standard and by withdrawal of any conflicting

national standards.

4.14 EXECUTIVE The Board has delegated the authority for the operational work of the ASD-STAN Organisation to the

Executive. The Executive is composed of a Director and Managers responsible for defined Domains.

4.15 EXPERT Person with technical expertise in a specified area contributing to the consensus on the technical

content of a draft document within a specified Sector, available to act as member of particular

Sector/Project Teams.

NOTE 1: An Expert is nominated by an ASD-STAN member through its Focal Point or by

participating CEN-CENELEC member.

NOTE 2: An Expert within one Sector could be also member of another Sector and can also act as

Leader of the Sector and/or as Project Team Leader.



06-2014 PAGE: 37 of 52

4.16 FINAL DRAFT The text of a published prEN prepared by the relevant Sector for submission to CEN-CENELEC

Formal Vote, including the consolidated comments disposition.

4.17 FIT/FORM/FUNCTION NOTE: The following definitions of fit, form and function are provided as guidance in order to clarify

that interchangeable parts (same part number) shall be capable to be handled with the same tools, setup

and work processes.

Fit: The ability of an item to physically interface or interconnect with or become an integral part of

another item (after installing with the same process, tool and tool-adjustment).

Form: The shape, size, dimensions, mass, weight and other visual and/or physical parameters (e.g. it

can be surface treatment, material, strength) which uniquely characterize an item. For software, form

denotes the language and media.

Function: The action or actions which an item is designed to perform.

4.18 FOCAL POINT Person nominated by an ASD-STAN member for a Domain in order:

To receive and distribute documents to all interested parties in his country / area;

To compile and consolidate votes and comments on documents distributed within a Domain.

NOTE 1: There shall be only one Focal Point per country and per Domain.

NOTE 2: A Focal Point shall deliver only one vote to a certain subject.

NOTE 3: All Focal Points have an obligation to vote on the New Work Proposals/Revision Requests

and on the National Domain Ballots.

4.19 INTELLECTUAL PROPERTY All documents established under the authority of ASD-STAN are owned by ASD-STAN. Only after

the publication of an ASD-STAN prEN document as EN European Standard via CEN-CENELEC and

the subsequent national publication by the CEN-CENELEC members, these documents are transferred

into the ownership of the appropriate CEN-CENELEC national member(s).

4.20 INTERCHANGEABILITY There are two types of Interchangeability, geometrical and functional:

Geometrical Interchangeability is achieved when an item is designed and produced in such a

way that it can be readily exchanged for another item without the need to select for fit and

without alteration, forcing or damage to the item itself or the adjoining structure.

Functional Interchangeability is achieved when operational or performance characteristics are

maintained on interchange or replacement of item.



06-2014 PAGE: 38 of 52

Full Interchangeability is achieved when both are met. For all types of standards full

Interchangeability of the related products shall be considered.

4.21 NEW WORK PROPOSAL (NWP) A New Work Proposal is a proposal for:

A new standard;

A new part of an existing standard;

A Technical Report;

A Revision of an existing standard or part i.e. after the review of a standard has indicated a

need for a Revision.

A project could comprise of several New Work Proposals.

4.22 NORMATIVE REFERENCE Referenced documents have to be recognized by the responsible sector concerned as having wide

acceptance and active status as well as being publicly available. In principle, ISO, EN or prEN

standards shall be referenced instead of other publication for a same subject

Need to consider the availability of a standard for the purpose of subsequent certification.

Please refer to CEN-CENELEC rules for guidelines on Normative References.

4.23 ORIGINATOR A person requesting the preparation of a standard or a document, and responsible for the completion of

the NWP (Form 1).

NOTE: An Originator may be also the Sector/Project Team member or Leader for a standard or a

document development

4.24 PATENTED ITEMS / TRADE NAMES In principle, a standard shall not include material, processes, characteristics or equipment which is

protected by patents. If, in exceptional cases, technical reasons justify the preparation of a standard

which includes the use of a patented item, the ASD-STAN Secretariat/Executive shall ask the patent

holder for a statement allowing the negotiation of licences with applicants on reasonable terms and

conditions. A record of this statement shall be kept by the Secretariat and shall be referred to in the

relevant standard. Should it be revealed, after the publication of the standard, that the licences cannot

be obtained under reasonable terms and conditions, the relevant standard shall be withdrawn.

For patent rights, see Annex F to Part 3 CEN-CENELEC Internal Regulations.

For use of trade names, see 6.6.3 of Part 3 CEN-CENELEC Internal Regulations.

4.25 PLATFORM A platform could be any of the following – aircraft, helicopters, engines, missiles, launchers, satellites

etc.



06-2014 PAGE: 39 of 52

4.26 PROJECT A project could be:

A single general standard (e.g. Quality, Procedures);

A set of standards covering a family of products or a package of Test Methods;

A range of standards covering the same subject e.g. product standard and related Technical

Specification, Design Standard or Test Methods.

4.27 PROJECT TEAM / -LEADER Selected members of the Sector forming the team for drafting standardization documents (Working

Draft, Consensus Draft, prEN, TR) based on approved New Work Proposals. The Project Team elects

a Project Team Leader who manages the activities of the Project Team with the support of the

allocated Secretariat (see also paragraph 1.8).

4.28 SECTOR A Team of Experts and Specialists nominated by ASD-STAN or by participating CENCENELEC

members to prepare standards related to approve New Work Proposals within a target date. A Sector is

established by the relevant Domain Technical Coordinator in co-ordination with the Executive.

NOTE: The work of a Sector could comprise of one or more New Work Proposals.

4.29 SECTOR LEADER Expert, member of a Sector and nominated by the sector members. He is confirmed by the Domain

Technical Coordinator. The Sector Leader shall guide the sector members according to the principles

established in section 1.5.

NOTE 1: A Sector Leader may also be a Project Team member or Leader for single New Work

Proposals.

NOTE 2: The Sector Leader should be prepared to act as a consultant regarding technical matters

arising after the PT has been disbanded.

4.30 STANDARD Document, established by consensus and approved by a recognised body, that provides, for common

and repeated use, rules, guidelines or characteristics for activities or their results, aimed at the

achievement of the optimum degree of order in a given context. Standards should be based on the

consolidated results of science, technology and experience, and aimed at the promotion of optimum

community benefits.

4.31 TECHNICAL AUTHORITY The Domain Technical Coordinators plus nominated member representatives form the Technical

Authority responsible for the supervision of technical processes and related improvements.



06-2014 PAGE: 40 of 52

4.32 TECHNICAL REPORT (TR) Consensus Draft published in the following exceptional cases:

The subject to be covered by the TR is still under technical development requiring wider

exposure but needs to be laid down at its current status for further development;

Informative publication containing collected data of a different kind, which currently cannot

be published as a European Standard.

If required, a TR could be published as a trilingual version (English, German and French).

A published ASD-STAN TR will not be transformed into CEN TR and TR will be part of the 5 years

periodic review.

4.33 VOTING Designated Focal Points are obliged to answer the various ballot forms (whatever the physical

presentation).

In all inquiries, ballots, resolutions and decisions, each ASD-STAN member country is entitled to one

vote only.

There shall be at least 3 valid votes (abstentions not counted) and the result is established by simple

majority.

4.34 WORKING DRAFT (WD) Draft prepared by a Sector/Project Team for examination within a Sector prior to submission to

Domain Ballot.



06-2014 PAGE: 41 of 52

ANNEX 1: FORMS

The Forms, listed below, are available in the ASD-STAN CEN Livelink.

List of Forms:

Form 1: New Work Proposal

Form 2-1: New Work Proposal Assessment by the ASD-STAN Executive

Form 2-2: New Work Proposal Assessment by the Domain Technical Coordinator

Form 3: Vote on New Work Proposal

Form 4: Results of Voting, Decision on New Work Proposal and Launch of Project

Form 5: cancelled (formation of Sector/Project Team now onto forms 3 and 4)

Form 6-1: Confirmation of Agreement on Consensus Draft (1) Agreement of Project Team

Form 6-2: Confirmation of Agreement on Consensus Draft (2) Sector Consensus

Form 7: Vote on Consensus Draft (National Domain Ballot)

Form 8: Voting results on National Domain Ballot

Form 9: Comments

Form 10-1: Approval for publication (1) by the Sector Leader

Form 10-2: Approval for publication (2) by the Domain Technical Coordinator

Form 10-3: Approval for publication (3) by the Sector Secretariat

Form 11: cancelled (decision to proceed to CEN-CENELEC Formal Vote is systematically)

Form 12: cancelled (disposition of Formal Vote comments done between the Project Team Leader and

the editing service)

Form 13: Review of European Standards

Form 14: Voting results on Review of European Standards



06-2014 PAGE: 42 of 52

ANNEX 2: CONSENSUS DRAFT GENERIC TEMPLATE

The rules for the Drafting of European Standards (Electronic preparation and Electronic figures and

graphics and their embedding in WORD files), shall be in accordance with CEN/CENELEC internal

regulation available on http://www.cen.eu/BOSS/Pages/default.aspx

The ASD-STAN Template shall be the CEN/ISO Template (STD Software) which is available on

http://boss.cen.eu/formtemp/std2.5a.zip

http://boss.cen.eu/formtemp/std2.5a.zip



06-2014 PAGE: 43 of 52

ANNEX 3: CEN-CENELEC PROCEDURE



06-2014 PAGE: 44 of 52

ANNEX 4: ACRONYMS

ASD AeroSpace & Defence Industries Association of Europe

ASD-STAN ASD Standardization

CD Consensus Draft

CEN European Committee for Standardization

CENELEC European Committee for Electrotechnical Standardization

CCMC CEN-CENELEC Management Centre

CS Cover Sheet

DC Declassification

DTC Domain Technical Coordinator

EDA European Defence Agency

EN European Standard

Exec Executive

Exp Expert

Ext External Participant in Sector/Project Team

FP National Focal Point for Technical Domain

FV Formal Vote

IAQG International Aerospace Quality Group

ISO International Organization for Standardization

NC National Coordinator

ND New Document

NDB National Domain Ballot

NWP New Work Proposal

Orig Originator

prEN projected EN

PT Project Team

PTL Project Team Leader

RT Withdrawal

SL Sector Leader

TA Technical Authority

TC Technical committee

ToR Term of Reference

TR Technical Report

WD Working Draft

WI Work Item number, allocated by CEN-CENELEC Management Center



06-2014 PAGE: 45 of 52

ANNEX 5: COVERSHEET FOR INACTIVE FOR NEW DESIGN



06-2014 PAGE: 46 of 52

Example 1:

ASD STANDARD NORME ASD ASD NORM

prEN «RegNo»

Edition «NEW_Edition» Decembre 2010

PUBLISHED BY THE AEROSPACE AND DEFENCE INDUSTRIES ASSOCIATION OF EUROPE - STANDARDIZATION

Avenue de Tervuren, 270 - B-1150 Brussels - Tel. 32 2 775 8126 - Fax. 32 2 775 8131 - www.asd-stan.org

ICS:

Descriptors:

ENGLISH VERSION

Aerospace series

«Titleen»

Série aérospatiale

«Titlefr»

Luft- und Raumfahrt

«Titlede»

This "Aerospace Series" Prestandard has been drawn up under the responsibility of ASD-STAN (The AeroSpace and Defence

Industries Association of Europe - Standardization). It is published for the needs of the European Aerospace Industry. It has

been technically approved by the experts of the concerned Domain following member comments.

Subsequent to the publication of this Prestandard, the technical content shall not be changed to an extent that

interchangeability is affected, physically or functionally, without re-identification of the standard.

After examination and review by users and formal agreement of ASD-STAN, it will be submitted as a draft European Standard

(prEN) to CEN (European Committee for Standardization) for Formal Vote and transformation to full European Standard (EN).

The CEN national members have then to implement the EN at national level by giving the EN the status of a national standard

and by withdrawing any national standards conflicting with the EN.

Edition approved for publication

31 Decembre 2010

Comments should be sent within six months

after the date of publication to

ASD-STAN

«DoMayn» Domain



06-2014 PAGE: 47 of 52

Example 2:

ASD

STANDAR

D

NORME

ASD

ASD

NORM

prEN

«RegNo»

Edition

«NEW_Edition

»

Decembre 2010



ICS:

Descriptors:

ENGLISH VERSION

Aerospace series

«Titleen»


«Titlefr»

Luft- und Raumfahrt

«Titlede»










Edition

approved

for

publication

31

Decembre

2010



ASD-STAN

«DoMayn» Domain



06-2014 PAGE: 48 of 52

ANNEX 6: EVOLUTION SHEET FOR ALL REVISIONS



06-2014 PAGE: 49 of 52

Annex A

(informative)

STANDARD EVOLUTION FORM

The main changes with respect to the previous editions are listed in Table A.1.

Table A.1 — Main changes to previous editions

prEN/EN

Number

Edition Publication

Date

Modification

Reason and validation

prEN XXXX P1 MM/YYYY



06-2014 PAGE: 50 of 52

ANNEX 7: COVERSHEET FOR WITHDRAWAL



06-2014 PAGE: 51 of 52

Example 1:

ASD STANDARD NORME ASD ASD NORM

prEN «RegNo»

Edition «NEW_Edition» Decembre 2010



ICS:

Descriptors:

ENGLISH VERSION

Aerospace series

«Titleen»


«Titlefr»

Luft- und Raumfahrt

«Titlede»










Edition approved for publication

31 Decembre 2010



ASD-STAN

«DoMayn» Domain



06-2014 PAGE: 52 of 52

Example 2:

ASD

STANDAR

D

NORME

ASD

ASD

NORM

prEN

«RegNo»

Edition

«NEW_Edition

»

Decembre

2010



ICS:

Descriptors:

ENGLISH VERSION

Aerospace series

«Titleen»


«Titlefr»

Luft- und Raumfahrt

«Titlede»










Edition

approved

for

publication

31

Decembre

2010



ASD-STAN

«DoMayn» Domain