ETSI TR 102 579-2007 Electromagnetic compatibility and Radio spectrum Matters (ERM) Report providing guidance for the production of Community Specifications for application under tati.pdf

1、 ETSI TR 102 579 V1.1.1 (2007-08)Technical Report Electromagnetic compatibilityand Radio spectrum Matters (ERM);Report providing guidance for the productionof Community Specifications for applicationunder the Single European Sky InteroperabilityRegulation EC 552/2004ETSI ETSI TR 102 579 V1.1.1 (2007

2、-08) 2 Reference DTR/ERM-TG25-037 Keywords ATM, interoperability, regulation, procedure ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture d

3、e Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions,

4、 the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revisi

5、on or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp

6、 Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of

7、ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 579 V1.1.1

8、 (2007-08) 3 Contents Intellectual Property Rights5 Foreword.5 Introduction 5 1 Scope 6 2 References 6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 Purpose of Community Specifications.8 4.1 Background to the Interoperability Regulation 8 4.2 Origination of Community Spec

9、ifications8 4.3 Role of Community Specifications in Presumption of Conformity8 5 Procedure for the generation of Community Specifications 9 5.1 Standardization need 9 5.2 Standardization mandate 9 5.3 The drafting process .9 5.4 Adoption of candidate Community Specifications.9 5.5 Submission to Euro

10、pean Commission and Publication in the OJEU .9 5.6 Revision of Community Specifications10 5.7 Withdrawal of Community Specifications .10 6 Production of a Community Specification .10 6.1 Guiding principles 10 6.1.1 Level of technological independence10 6.1.2 Assumption.11 6.1.3 Cooperation.11 6.1.4

11、General methodology11 6.1.5 Evaluation principles 12 6.2 Method for approaching the Community Specification .13 6.2.1 Overview 13 6.2.2 Identify regulatory baseline 14 6.2.3 Identify the existing documents14 6.2.4 Optional: clarify scope and draft compliance annex.14 6.2.5 ER/IR breakdown across sys

12、tems/constituents/procedures 15 6.2.6 Draft the body of the CS and complete the checklist15 6.2.6.1 Draft the body of the CS .15 6.2.6.2 Complete the checklist 15 6.2.7 Finalize the CS15 6.2.7.1 The foreword clause15 6.2.7.2 The scope clause .16 6.2.7.3 The Standards Annex(es) SA, SB, etc.16 7 Analy

13、sis of the requirements (ER and IR) .18 7.1 Principle of the analysis .18 7.2 Example of the checklist 19 Annex A: Standards Annex.20 Annex B: Checklist 21 B.1 Interoperability Regulation Annex II Essential Requirements Part A: General requirements.21 B.2 Interoperability Regulation Annex II Essenti

14、al Requirements Part B: Specific requirements.25 B.2.1 Systems and procedures for airspace management.25 ETSI ETSI TR 102 579 V1.1.1 (2007-08) 4 B.2.2 Systems and procedures for air traffic flow management 26 B.2.3 Systems and procedures for air traffic services 27 B.2.3.1 Flight data processing sys

15、tems27 B.2.3.2 Surveillance data processing systems .29 B.2.3.3 Human-machine interface systems .30 B.2.4 Communications systems and procedures for ground-to-ground, air-to-ground and air-to-air communications .31 B.2.5 Navigation systems and procedures .32 B.2.6 Surveillance systems and procedures

16、.33 B.2.7 Systems and procedures for aeronautical information services33 B.2.8 Systems and procedures for the use of meteorological information.34 Annex C: Compliance annex for planning purposes 35 History 37 ETSI ETSI TR 102 579 V1.1.1 (2007-08) 5 Intellectual Property Rights IPRs essential or pote

17、ntially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential

18、, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No g

19、uarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Electromagnetic

20、compatibility and Radio spectrum Matters (ERM). Introduction The European Union launched the Legislation “Single European Sky“ (SES) in 2002 which had been adopted in 2004. The SES legislation is based on a framework of 4 regulations, which includes “the Interoperability Regulation“ (EC 552/2004). T

21、he objective of the Interoperability Regulation is to ensure interoperability of the European Air Traffic Management Network (EATMN) consistent with air navigation services. Under this regulation, the use of a Community Specification (CS) is a means of compliance to the essential requirements of the

22、 Regulation and/or the relevant implementing rules for interoperability. The present document providing guidance for the production of European CS provides a framework for procedural and general content during all phases of the CS development. This will ensure commonality and make it easier and more

23、 cost effective for the working groups to draft clauses in the CSs and provide traceability to the Essential Requirements of the Interoperability Regulation. ETSI ETSI TR 102 579 V1.1.1 (2007-08) 6 1 Scope The present document has been prepared to assist ETSI technical bodies in the preparation of C

24、ommunity Specifications for application under the Interoperability Regulation 1. Where clauses 4 and 5 deliver useful background information on the CS role and generation process, the clauses 6 and 7 establish a methodology to allow those technical bodies to have a consistent production workflow for

25、 CSs and a given interpretation of the essential requirements of the Interoperability Regulation 1. The present document is focussed on ETSI deliverables but is also a suitable basis for Community Specifications produced by other bodies. The existing CEN Guidance Material 2 was noted during the prod

26、uction of the present document. The document may also help other bodies to understand the relationship between various standards and procedural documents produced by the EATMN stakeholders. NOTE: The scope of the present document is to capture guidance for standardization bodies. It is not intended

27、to provide guidance for those, e.g. ANSPs and manufactures, who have to demonstrate and certify compliance of systems, constituents and procedures to the IOP regulation. 2 References For the purposes of this Technical Report (TR), the following references apply: NOTE: While any hyperlinks included i

28、n this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 1 Regulation (EC) No 552/2004 of the regulation of the European Parliament and of the Council of 10 March 2004 on the interoperability of the European Air Traffic Management network (interoperability

29、Regulation), OJ L 96, 31.03.2004. 2 http:/www.cen.eu/boss/supporting/guidance+documents/gd032+-+relation+between+ens+and+er+of+nad/index.asp. 3 Regulation (EC) No 549/2004 of the European Parliament and of the Council of 10 March 2004 laying down the framework for the creation of the single European

30、 sky (the framework Regulation), OJ L 96, 31.03.2004. 4 Council Resolution of 7 May 1985 on a new approach to technical harmonization and standards, OJ C 136, 04.06.1985. 5 ETSI EG 201 399: “Electromagnetic compatibility and Radio spectrum Matters (ERM); A guide to the production of candidate Harmon

31、ized Standards for application under the R and it refers also to the EC Council Resolution of 7 May 1985 on the “New Approach“ 4. The regulation contains essential requirements, which should apply to the European air traffic management network, its systems, constituents and associated procedures. Th

32、ey are split into general requirements, valid for all systems and constituents, and additional specific requirements, referring to defined systems. In addition to the four basic regulations, Implementing Rules (IRs) for interoperability should be drawn up whenever necessary to complement or further

33、refine the essential requirements. Those IRs should also be drawn up where necessary to facilitate the coordinated introduction of new, agreed and validated concepts of operation or technologies; compliance with those IRs shall be permanently maintained; those IRs should rely on standards and specif

34、ications developed by international organizations such as EUROCONTROL or ICAO. NOTE: Standards developed according to 4 under other EC directives/regulations are not within the scope of the present document; there may be separate guidance material to be used for such products (e.g. 5 in case of prod

35、ucts under the R the standard shall follow the withdrawal procedures of the ETSI TWP. The ETSI Secretariat shall ensure that the standard is archived so as to remain available if requested, including traceability that the standard had been published in the OJ, with the relevant dates of publication

36、and withdrawal. 6 Production of a Community Specification 6.1 Guiding principles 6.1.1 Level of technological independence ETSI technical bodies should take note, as a principal goal, that wherever possible, CSs which are technology independent are preferred; i.e. a CS should only specify the detail

37、 of what is required and how it is to be met to an appropriate level. Users of the CS must not be unnecessarily constrained when developing their solution to the requirement(s). The level of technological independence should remain the responsibility of the appropriate TB. NOTE: As an example a CS f

38、or Ground-based VHF hand-held, mobile and fixed radio transmitters, receivers and transceivers will specify the technical characteristics and performance requirements together with the associated methods of measurement; it will not detail the design solution that delivers the characteristics and per

39、formance. In producing CSs for application under the IOP Regulation 1, ETSI shall ensure that the standards do not exceed the degree of regulation envisaged by the Commission, and shall apply discernment in order not to inhibit technological innovation or the meeting of the needs of a free-market ec

40、onomy. ETSI ETSI TR 102 579 V1.1.1 (2007-08) 116.1.2 Assumption It is assumed, that before a mandate is being issued, the consultation process to determine that a new CS is needed has taken into account that there is existing reference material to it. 6.1.3 Cooperation Due to its safety needs, aviat

41、ion has always been a highly regulated sector. Although the safety of citizens is primarily a state task, voluntary bodies on the European level have been in place for more than forty years to ensure a harmonized European approach, mostly but not always, outside of the European standardization bodie

42、s. With aviation policy now being a Community competence, the Community mechanisms for standardization have now to be applied to aviation and with 1 to ATM in particular. Therefore, and in order to build on the existing distributed knowledge, cooperation is a basic principle for the development of C

43、Ss. This includes the cooperation of the European standardization bodies among each other (one ESO being the “lead ESO“, the other(s) being “supporting ESO“) and the cooperation with organizations like EASA, EUROCONTROL, EUROCAE and the relevant aviation stakeholder. The lead ESO is the one mainly i

44、n charge of the mandate. In addition to its technical work, it is the responsibility of the lead ESO to act as the coordinator between the parties mentioned above, to set up the necessary working arrangements and to act as the interface to the Commission. If ETSI takes the role of lead ESO the appli

45、cable TB shall consider the impact on resources and timelines. It should be considered that resources from supporting organizations are needed for drafting, comment resolution and maintenance of the CS. Under the legally required cooperation with EUROCAE the applicable TB shall consider to take adva

46、ntage of the following options when producing a Community Specification: (re-)use of existing EUROCAE documents; (re-)use of EUROCAE documents under development; this includes the possibility to participate in the EUROCAE working groups drafting documents which are (possibly) relevant for a mandated

47、 Community Specification; proposal for new work-items in the EUROCAE working programme to fill identified gaps. 6.1.4 General methodology This methodology is based on the evaluation of applicable documentation for systems, constituents and procedures, which is supposed to contain compliance to the E

48、R or parts thereof, against the essential requirements. The evaluation takes place at two levels: 1) A detailed evaluation conducted by the CS drafting group results in a checklist, providing comprehensive traceability of evidence against sub-clauses of the ER/IR. This evidence is derived from analy

49、sing key words of the essential requirements and relevant IRs, as explained in clause 7. Those keywords mainly address the phases of design, build, operation and maintenance of systems and constituents as well as specifically required qualities or attributes. The analysis provides the WHAT is required from the CS. If the existing document that is evaluated provides the corresponding HOW then the relevant reference shall be captured as evidence in the traceability table. NOTE 1: The application of this generic guidance has to be dependent upon the