The ETSI Standardisation Process Open Meeting on Interoperability Standards for EATMN ETSI HQ, 7th and 8th September 2005 Dr A. J. R. Ives, STF 293 Member (1)

Purpose We present here a particular case of the standardisation process of a European Standardisation Organisation (ESO): - The ETSI standardisation process The other ESOs are CEN (Comité Europeén de Normalisation) CENELEC (Comité Europeén de Normalisation Electrotechnique) Their standardisation processes are expected to be similar (2)

Initiation A proposal is made to initiate a work item May be made at an ETSI Working Group or at an ETSI Technical Committee by at least 4 ETSI members In this case, (ERM) TG25 (Aeronautical) Working Group, followed by approval at the ERM Technical Committee Decide which Working Group will coordinate the work Decide on the type of standard (Technical Specification (TS), Technical Report (TR), ETSI Standard (ES), ETSI Guide (EG), European Norm (EN) (a form of Community Specification) (3)

Approach Decide on how the work will be carried out: Scope, timescale, rapporteur ETSI may, or may not, propose a Specialist Task Force (STF) If an STF is set up: Paid experts assist the Working Group An STF Steering Committee oversees the STF STF is responsible to TC on technical matters, to ETSI Secretariat on administrative matters In the case of EU funding, the STF experts have a contract with EC/EFTA (4)

Source Documents for Drafting Establish whether there is existing documentation, and determine its status Source documents may or may not be available from which to start drafting an ETSI Standard In this case, source documents will typically be from Eurocae, Eurocontrol, ICAO, ETSI, etc. Source documents may be Finalised, approved and published In draft form Or in the process of being updated (5)

ETSI Drafting Principles ETSI Drafting Rules specify a uniform structure, style, format and presentation, to aid reader understanding ETSI document templates are provided which must be adhered to Documents are produced in English Documents must be clear, consistent and unambiguous, to facilitate communication The drafting rules specify that any referenced documents must be publicly available (6)

ETSI Editing Process Documents are checked before public approval procedures, and again prior to publication Documents cannot proceed unless they are compliant with the ETSI Drafting Rules (7)

ETSI Approval Process (1) Approval takes place at the following levels: at the STF Steering Group if an STF has been set up at the ETSI Working Group in this case (ERM) TG25 (Aeronautical) at the ETSI Technical Committee in this case ERM (8)

ETSI Approval Process (2) The type of approval process is either: A Two-step Approval Procedure (TAP) Documents are submitted for Public Enquiry – they are distributed to nominated organisations in Member States of the EU for approval Any comments received are addressed Documents then sent for National Vote A One-step Approval Procedure (OAP) Documents are sent for National Vote Comments received are addressed (9)

Two-step Approval Procedure (TAP) Following the TAP Public Enquiry phase If comments were received, the standards must be modified as necessary by the ETSI Working Group (TG25) The documents must be approved by the Working Group The documents must be approved again by the ETSI Technical Committee (ERM) Following (final) approval by the ETSI Technical Committee (ERM) Standards are distributed to nominated organisations in States for National Vote Further comments may be received during the voting phase (10)

Publication Documents which have successfully passed the National Vote are published on the ETSI website and/or in the Official Journal of the EU ETSI deliverables may be downloaded individually free of charge from the ETSI Publications Download Area All deliverables available on DVD (ETSI Documentation Service) (11)

Example Timeline An example timeline for the standardisation process (12)

Conversion to ETSI EN (CS) Where there is existing source material (e.g. a Eurocae, Eurocontrol, or ICAO standard), can this (easily) be converted to a document that is acceptable as a European Norm (i.e. a Community Specification)? (13)

EN Conversion – Technical Issues The requirements needed for an EN may not be already existing in the source documentation The test cases required for an EN may not be already existing in the source documentation The technical content required in the EN may or may not reflect the same functionality as described in the source documentation There is a need to ensure consistency between the source documents and the EN throughout the life of the EN (14)

EN Conversion – Editorial Issues The structure and style of the ETSI EN is defined by the ETSI secretariat. These are likely to be different from that of the source documents Conversion to the EN structure and style would have to be carried out (15)

Questions (16)