Conformity Assessment Task Force Meeting # 13 EUROCONTROL Headquarters POLLUX Meeting Room 26 June 2008

Transcription

1 Conformity Assessment Task Force Meeting # 13 EUROCONTROL Headquarters POLLUX Meeting Room 26 June 2008 European Organisation for the Safety of Air Navigation

2 Agenda Item 1 Opening & Approval of Agenda European Organisation for the Safety of Air Navigation

3 Agenda Item 2 Progress Report on EASA SES Frameworks Comparison Study Philippe Crebassa Egis Avia European Organisation for the Safety of Air Navigation

4 Conformity Assessment Task Force 13th Meeting Description & Comparison of airworthiness and verification processes in EASA & SES contexts Progress Report 26 June 2008 Presented by Philippe Crebassa

5 Content Background Organisation Progress Report Proposed measures CATF#13 IP 13.1 Brussels, 26 June

6 BACKGROUND Emergence of Interoperability conformity assessment processes Safety assessment of ATM changes Significant modification in practices for the management of CNS/ATM systems EASA regulations Airworthiness certification of products, parts and appliances Operational approval for on-board equipment related to ATM programmes. EASA and SES specific conformity processes wrt applicable regulations. Juxtaposition of EASA and SES environments for A/G CNS/ATM A complex regulatory environment with intertwined technical requirements, obligations of operators, ANSPs, and responsibility of authorities Objectives of the study To provide recommendations so as to increase the homogeneity and complementarities of EASA and SES conformity processes. Not to reshape both environments to get a unique model for EASA and SES regulations. CATF#13 IP 13.1 Brussels, 26 June

7 ORGANISATION Regulatory Unit, The European Commission, the EASA, Safety Regulatory Unit 2 Steps 3 assessments Comparison of airworthiness certification and verification of conformity [deliverable D1] Description of the certification and approval processes applicable to products supporting data link services [deliverable D2] Comparison of the processes for the safety acceptance and conformity assessment of EATMN systems [deliverable D3] Identification of recommendations for improvement and associated measures [deliverable D4] CATF#13 IP 13.1 Brussels, 26 June

8 PROGRESS REPORT D1 : final version delivered and accepted D2, D3 : draft final versions submitted for review D4 : initial draft presented to the last SG End of Study expected in September 08 CATF#13 IP 13.1 Brussels, 26 June

9 PROPOSED MEASURES

10 METHODOLOGY "WHAT" "HOW" High level objective Issue 1 Issue 2 Issue 3 Issue 4 Issue 5 Inputs from D1, D2 & D3 Class 1 Recommendation Recommendation Recommendation Recommendation Recommendation Class 2 Measure M1.1 Measure M1.2 CATF#13 IP 13.1 Brussels, 26 June

11 Four classes Rulemaking and standardisation Terminology, structure, development and management of regulatory materials Implementation of regulations and specifications before the operation phase Certification, conformity assessment and safety acceptance before the entry into service / putting into service. Monitoring of compliance during the operations Verification of compliance during the operation phase. SES Interoperability of non EU aircraft Aircraft designed or registered outside the EU and entering the EATMN airspace. CATF#13 IP 13.1 Brussels, 26 June

12 Rulemaking and Standardisation

13 Measure 1: Common terminology A common core terminology reference The most important terms used in both systems have one single definition Deviations from the reference Need for justification and traceability Terminology repository should include Basic common notions Most frequently used terms relating to A/G CNS/ATM functions CATF#13 IP 13.1 Brussels, 26 June

14 Measure 2: Harmonisation of the structure of SES and EASA regulatory materials Common principles to define the mandatory and voluntary requirements Regulatory materials should have the same level in terms of legal binding power Means of compliance of both environments (i.e. EASA CS and AMC/GM and SES CS) should have the same status with respect to mandatory requirements CATF#13 IP 13.1 Brussels, 26 June

15 Measure 3: Approach for the development of SES and EASA regulatory materials for air-ground CNS/ATM Development of EASA and SES regulatory materials should be supported by a methodical approach: Allocation of regulatory requirements affecting the same subjects between EASA and SES materials Management mechanisms defining traceability information of applicable requirements originating from different documents Definition of the object subject to the assessment of conformity or suitability for use, and/or the verification Consideration by SES rulemaking of other requirements with a direct impact on the implementation of these regulations CATF#13 IP 13.1 Brussels, 26 June

16 Implementation of regulations and specifications before the operation phase

17 Measure 1: Extension of EASA certification process to SES conformity assessment How EASA certification process and operational approval process might be extended to the verification of compliance of airborne constituents Role and responsibility of manufacturers, of EASA and NSA authorities with respect to conformity of airborne constituents Supervision of compliance by NSAs Application to airborne constituents Interface with EASA procedures CATF#13 IP 13.1 Brussels, 26 June

18 Measure 2: Harmonization of the role and responsibility of Notified Bodies and Qualified Entities How roles and responsibilities of Qualified Entity and Notified Body in both EASA and SES environment might be harmonized Role as EASA/ NSA delegates in The different phases of the certification and verification of conformity processes The organisation capacity approval process CATF#13 IP 13.1 Brussels, 26 June

19 Measure 3: Notion of organisation capacity approval in SES environment Applicability of organisation capacity approval under SES environment as a means to alleviate the implementation of conformity processes This organisation capacity approval is not directly related to the certification of providers of services How the EASA organisation capacity approval principles Might apply to organisations maintaining EATMN constituents and systems Might be extended to other phases of the system life cycle. CATF#13 IP 13.1 Brussels, 26 June

20 Measure 4: Applicability of "Type Certification" in SES environment Conformity processes based on type certificate apply to products manufactured by replicating the type-design product Applicability of type certificate as a means to alleviate the implementation of conformity processes The measure consists in defining: How the type certificate might apply to EATMN CNS constituents How the type certificate might apply to EATMN systems that are replicated with specific configuration items CATF#13 IP 13.1 Brussels, 26 June

21 Measure 5: Harmonisation of conformity assessment and safety assessment processes in SES environment Support organisations in the delineation of the object to be considered within assessment Clarify the terms upgrade for a conformity assessment and change for a safety assessment and acceptance Refine the status of the Certificate of Conformity delivered by a Notified Body Make best use of conformity assessment and safety assessment processes to avoid duplication of effort CATF#13 IP 13.1 Brussels, 26 June

22 Measure 6: Supervision of compliance before putting into service How the supervision of compliance before putting into service might be implemented by adapting EASA mechanisms to the SES environment How the supervision of compliance might be interfaced with the SES safety oversight process CATF#13 IP 13.1 Brussels, 26 June

23 Monitoring of compliance during the operations

24 Measure 1: Implementation of the supervision of compliance To ensure that the EATMN constituents and systems continue to comply with the relevant interoperability requirements How EASA continuing airworthiness principles might apply to the supervision of compliance for EATMN constituents and systems How to ensure that this supervision of compliance is coordinated with EASA continuing airworthiness for airborne constituents CATF#13 IP 13.1 Brussels, 26 June

25 Measure 2: Management of the maintenance Role of maintenance organisations with regards to interoperability requirements Ad-hoc qualification process for the organisations maintaining EATMN constituents and systems Application of this qualification process to ANSPs and its extension to third parties CATF#13 IP 13.1 Brussels, 26 June

26 Measure 3: Management of the decommissioning of EATMN constituents The impact of the decommissioning and a possible future reuse The measure consists in defining: How to ensure that the modified EATMN system (after decommissioning) still complies with SES interoperability requirements How to manage the possible re-use of constituents with regards to interoperability requirements CATF#13 IP 13.1 Brussels, 26 June

27 Measure 4: Management of the non-compliance cases How operators, avionics manufacturers should point out to CAs any non-compliance cases of airborne constituents How manufacturers and ANSPs should advise NSAs any non-compliance cases of constituents How the European Commission, CAs and NSA should manage non-compliance cases, safeguard measures and coordinate their actions CATF#13 IP 13.1 Brussels, 26 June

28 SES Interoperability of non EU aircraft

29 Measure : Procedures ensuring interoperability of third country aircraft Conformity of aircraft to SES interoperability requirements should be fully guaranteed by The application of the relevant international standards and The means of compliance to these standards evidenced during the certification process Harmonised standards would be the basis on which Conformity of aircraft of non-european design could be assessed through the EASA bilateral validation processes in place with the State of Design Conformity of non-european operators fleets and procedures could be shown or acknowledged through the future Implementing Rule of the new EASA Basic Regulation, taking into account possible bilateral provisions with the State of the Operator CATF#13 IP 13.1 Brussels, 26 June

30 Questions CATF members are invited To take note of the progress achieved To comment on the proposed measures. CATF#13 IP 13.1 Brussels, 26 June

31 Agenda Item 4 Extension of Guidelines for the Verification of Constituents and Systems Jean-Paul Doré Regulatory Unit European Organisation for the Safety of Air Navigation

32 Implementation of conformity assessment of EATMN constituents & systems Harmonisation of the implementation of conformity assessment of constituents and systems Define guidance materials to address key issues: Objects, subject to verification and declaratio n (constituents & systems) Scope of verifications Criteria to renew EC declarations (upgrade of systems ) 32

33 Definition of EATMN constituents and systems For the short term: Definition of EATMN systems at rather high level by reusing elements of definition from legacy solutions, OATA/SESAR architecture Support to the identification of EATMN systems subject to EC verification For the medium term: Definition of EATMN reference architecture used by interoperability implementing rules (possible update of Annex I) in consistency with SESAR architecture 33

34 Scope of the guidelines Three main parts: Part A: Definition of EATMN systems Part B: Notion of operational characteristics of systems Part C: Definition of CNS-type constituents 34

35 Part A : Definition of EATMN systems Approach for the definition of EATMN systems Development plan for the definition of EATMN systems Definition of the first subset of EATMN systems Validation of the proposed definitions 35

36 Part A: Definition of EATMN Systems Definition of EATMN Relationship between EATMN elements Criteria for belonging to EATMN (test systems, shadow systems,..) Administration of EATMN (from regulatory standpoints) Identification, naming of EATMN systems Integration, putting into service 36

37 Part A: Definition of EATMN systems General definition of EATMN systems Single system for CA Assembly of constituents EC Declaration/Technical File Definition of EATMN systems supporting ATM operations Definition of EATMN systems supporting CNS operations Sources of definition of architecture elements (SESAR arch ) Link between EATMN system and external sources of definition of architecture elements Sources of definition of architecture elements (ARTAS, SESAR arch ) Link between EATMN system and external sources of definition of architecture elements Organisational context 37

38 Part B: Notion of operational characteristics Analysis of modifications of systems through 3 views to screen them into 2 categories: Modification with impact on operational characteristic Modification without impact on operational characteristic 3 views SES compliance view System architecture view End users view 38

39 Part B: SES compliance view All along the lifetime of a system, identification and upgrade of: Regulatory baseline Community Specifications baseline Modification of the regulatory baseline must entail a revised EC declaration and TF Modification of CS baseline might entail a revised EC declaration and TF, or a revised TF only 39

40 Part B: System architect view Analysis of modification of systems architecture Modifications of the infrastructure and platform layer should not be considered as an operational upgrade Modification of domain-dependent layers might be considered as an operational upgrade 40

41 Part B: End users view Analysis of modifications in: Use Cases, ATC Manuals Provision and use of communication, navigation, surveillance services Provision and use of aeronautical information services Provision and use of meteorological information services 41

42 Part C: Definition of CNS typeconstituents Approach for drafting the definition of CNS type-constituents Definition of the first subset of CNS type-constituents Recommendations for manufacturers 42

43 Key milestones Tender submission deadline: 2 July 2008 Start date: First half of September Draft guidelines February

44 Agenda Item 7 Overview of SES Architecture Activities Shanda Cordingley SESAR & ATM Strategy European Organisation for the Safety of Air Navigation

45 Overview of SESAR Architecture Activities European ATM Architecture for 2020: from Data Exchange to SWIM Shanda Cordingley, O level CATF#13-26 June 08 45

46 Main Drivers for Change Key ATM Target Concept elements impacting EATMS architecture: SWIM No more current data exchange based on point to point messages sharing of information to support all ATM operations BUSINESS TRAJECTORY No more partial trajectories used independently shared trajectory, gate-to-gate NETWORK MANAGEMENT Network management functionalities distributed in numerous systems ASAS More ATM functionalities on the airborne side Ground systems to integrate ASAS manoeuvres Page: 46

47 Logical Architecture the link to the ConOps System functions identified from ConOps Allocated to logical architecture modules represent functions and information to be managed by the ATM system ATM Operations Air Surveillance Surface Surveillance En-route/APP ATC Aerodrome ATC Airport Operations Airspace User Operations ATFCM Airspace Organisation & Management ATM Support Aircraft Communication Ground Communication Distributed System Services (Middleware) Aircraft Navigation Aircraft Surveillance Meteo Aircraft Flight Airspace Organisation Aerodrome Navigation Aids ATM Shared Concepts Page: 47

48 Technical Architecture - ATM Systems and Sub- Systems Aircraft Local/Sub-regional systems Regional systems Integrates the aircraft SWIM mechanisms G/G and A/G Safety requirements high levels of availability, continuity, integrity Information security increases needed due to increased information access through SWIM Manage environmental constraints and measure performances provisions within each stakeholder s systems En-route /Approach ATC Aerodrome ATC Airport Airside Operations A/G Datalink Ground Management Local and Subregional Systems Ground SWIM Network AOC ATM SWIM Supervision External Systems Regional Systems Aeronautical Information Management Advanced Airspace Management Network Information Management Page: 48

49 SWIM Principles SWIM services : added-value information management services Flexible and modular sharing of information Transparent access to ATM services Overall consistency Data Model for agreed & precise definition of information Page: 49

50 Main Aircraft Architecture Evolutions New Flight Manager and Flight Guidance sub-systems 4D trajectories and special approaches (curved, steep and offset optimised trajectories) to improve performance and reduce environmental impact Direct air to air exchanges to support ATSAW, ASAS Spacing and Separation and ASAS Self Separation impacts all communication, navigation and surveillance subsystems En-route /Approach ATC Aerodrome Aircraft Airport Airside Operations A/G Datalink Ground Management Local and Subregional Systems Ground SWIM Network AOC ATM SWIM Supervision External Systems Regional Systems Aeronautical Information Management Advanced Airspace Management Network Information Management Page: 50

51 Main Regional Systems Architecture Evolutions Aeronautical Information Management Regional, Subregional and Local greater co-operation via SWIM to share static and dynamic information for the benefit of all EATMS Stakeholders. Advanced Airspace Management support and facilitate the design, development and publication of an optimal European airspace structure. Network Information Management regional collaborative Air Traffic Flow & Capacity Management processes with local/sub-regional actors through Network Operations Plan (NOP). En-route /Approach ATC Aerodrome ATC Aircraft Airport Airside Operations A/G Datalink Ground Management Local and Subregional Systems Ground SWIM Network AOC ATM SWIM Supervision External Systems Regional Systems Aeronautical Information Management Advanced Airspace Management Network Information Management Page: 51

52 Main Sub-Regional/Local Systems Architecture Evolutions En-route and Approach ATC Centres more system automation (several roles more strategic planning and monitoring in execution phases of a flight) sub-regional coordination regarding Traffic Demand and Capacity Balancing, Traffic Flow, and Resource management and collaboration with the regional instances Aerodrome ATC and Airport Airside Operations systems provision and access to a commonly shared data available through SWIM for queue management improvements AOC ATM change from submission of flight plans to pre-departure management and Page: 52 En-route /Approach ATC Aerodrome ATC Aircraft Airport Airside Operations A/G Datalink Ground Management Local and Subregional Systems Ground SWIM Network AOC ATM SWIM Supervision External Systems Regional Systems Aeronautical Information Management Advanced Airspace Management Network Information Management

53 Definition Phase Architecture Conclusion an EATMS architecture is feasible and will provide the required information sharing capability that is essential to make the SESAR Concept work but note, The ConOps and its associated performance framework require a new approach for future systems architecture and development more modular multi-domain collaboration with each stakeholder group to ensure that all business needs and access to information are fairly addressed addressing the whole life-cycle right from operational concept development Architecture design principles, based on modern system engineering techniques, have been identified for the development of the future European ATM system, e.g.: Enterprise Architecture Service-Oriented approach SWIM mechanisms Page: 53

54 Next Steps SESAR Joint Undertaking (SJU) SJU SJU A/1 Work Programme Management B (High Level) Target Concept & Architecture Maintenance D - ATM Network R&D Programme C - Master Plan Maintenance E Long-Term & Innovative Research Programme 2 - R&D Overall Consistency 3 - Validation Infrastructure Adaptation and Integration 16 Transversal Areas Transversal Thread 5 - TMA Operation 7 - Network Operation 9 Aircraft System 11 Flight Operation Centre System 13 Network System 4 - En Route Operation 6 - Airport Operations 8 - Information Management 14 - SWIM 10 EN-Route & TMA ATC System 12 - Airport System 15 CNS System Operational Thread SWIM Thread System Thread Page: 54

55 Mapping of Systems to SJU WPs 9 Aircraft System Aircraft 10 EN-Route & TMA ATC System En-route /Approach ATC Aerodrome ATC 12 - Airport System Airport Airside Operations A/G Datalink Ground Management Local and Subregional Systems Ground SWIM Network 14 SWIM AOC ATM SWIM Supervision 15 CNS System 11 Flight Operation Centre System External Systems 13 Network System Regional Systems Aeronautical Information Management Advanced Airspace Management Network Information Management Page: 55

56 Overview of SESAR Architecture Activities Questions? CATF#13-26 June 08 56

57 Agenda Item 5 Implementation of Conformity Assessment of Systems The Spanish Approach Enrique Gismera Gomez AENA European Organisation for the Safety of Air Navigation

58 CA Spanish Approach - CATF#13 - June 2008 CATF #13 Implementation of conformity assessment of systems The Spanish Approach (AENA) ENRIQUE GISMERA DIVISIÓN DE VERIFICACIÓN DE SISTEMAS DIRECCIÓN DE INGENIERÍA Y EXPLOTACIÓN TÉCNICA

59 CA Spanish Approach - CATF#13 - June 2008 Contents 1 Introduction: System Verification Division 2 Status of System Verification activities in Aena 3 EC Declaration & Technical File: Aena s View 4 Other issues found PAG 59

60 CA Spanish Approach - CATF#13 - June 2008 Introduction (I) The System Verification Division: Was created in December 07. Within the Engineering and Technical Exploitation Directorate of Aena. To deal with: Coordination of Interoperability Regulation application. RE 2096/2005 (safety aspects): mainly Safety Management. Key aspect: System Verification Division independency (agreement with NSA). PAG 60

61 CA Spanish Approach - CATF#13 - June 2008 Introduction (II) Aena Airports Directorate Air Navigation Directorate Other Corporate Directorates Planification Directorate Deputy Directorate Engineering and Technical Exploitation Directorate Engineering ATM Operations Directorate Other Air Navigation Directorates System Verification Division Comms Division Automated System Division Navigation and Survaillance Division Satellite Navigation Division Other DIET Divisions DCOM Communicatio n Division DAUT Automated Systems Division DNV/DNS Surv&Nav Divisions PAG 61

62 CA Spanish Approach - CATF#13 - June 2008 Introduction (III) DAUT Automated Systems Division DAUT PROCEDURES REQ IOP CE VERIFICATION PROCEDURE CE.DECL SISTEM a SISTEM b SISTEM c Engineering DCOM Communication Division Engineering DCOM PROCEDURES REQ IOP CE.DECL SISTEM l SISTEM m SISTEM n DCOM Communicatio n Division IOP DAUT Automated Systems Division DNV/DNS Surv&Nav Divisions DNV/DNS PROCEDURES DNV/DNS Surv&Nav Divisions INTEROPERABILITY REGULATION (IOP) REQ IOP CE.DECL SISTEM x SISTEM y SISTEM z IOP IOP Regulation 552/2004, 1032/2006, 1033/2006, 633/2007, 1265/2007,... PAG 62

63 CA Spanish Approach - CATF#13 - June 2008 Aena CA Status - SYSTEMS DAUT Automated SACTASystems Division 1 VOR 74 VCS 49 ICARO 1 ILS 46 G/G 40* NDB 72 G/A 72 DCOM Communication Division DME 79 REDAN AMHS 1 1 VOLMET 1 ATIS 16 PSR DNV/DNS DNS Satellite Surveillance Surv&Nav Nav-Aids Divisions Area12 GBAS 1 SMR SSR SMMS ADS Reg. 552/ Annex I - Systems: 3. ATS: 1 4. COM: 180* 5. NAV: SUR: AIS: 1 TOTAL 502 PAG 63

64 CA Spanish Approach - CATF#13 - June 2008 Aena CA Status CONSTITUENTS (I) Issue 1: Definition of Constituent Just one Constituent defined in IOP Regulation (Tx/Rx in Reg.1265/2007). Aena finds no advantage in defining constituents by itself: Therefore SYSTEM=CONSTITUENT is a valid approach (except for Tx/Rx) until Eurocontrol finally issues their Guidelines. Some aspects in Aena procedures (and maybe Manufacturer) depend on the definition and number of Constituents: A solid definition may be undertaken with strong participation of Manufacturers. The development of Eurocontrol-Guidelines should be carried out jointly with the Manufacturers. PAG 64

65 CA Spanish Approach - CATF#13 - June 2008 Aena CA Status CONSTITUENTS (II) Issue 2: Constituent definition approaches There are different approaches depending on who defines the constituent: Regulation: the Declaration of Constituents MUST be issued. Manufacturer: the Declaration of Constituents is part of the strategy of putting something in the market. ANSP: Declaration of Constituents should fit into the verification of the System. Strong relationship foreseen between Declaration of Systems and Declaration of Constituents, though not explicit in Regulation. The Manufacturer is not obliged by Regulation. AENA: fits the Declaration of Constituents into its process (mandatory at least Suitability for Use), but some problems may arise. PAG 65

66 CA Spanish Approach - CATF#13 - June 2008 Aena CA Status CONSTITUENTS (III) Issue 3: Declaration of Constituents content RE EC Nº 552/2004 defines: Declaration of Systems: content clearly described (Annex IV). Declaration for Constituents: content vaguely described (Annex III). RE EC Nº 1032/2006 and RE EC Nº 633/2006 define: Declaration of Systems: reference to 552/2004 (Annexes IV-B/C and IV-A/B). Declaration of Constituents: very detailed description of how to carry out the process (Annexes IV-A and II). What to do if only 552/2204 applies? Eurocontrol Guidelines And/or European Commision What to do if 552, 1032 and 633 apply? (i.e. OLDI in ATM Systems): different depth in Declarations of Constituents depending on which Regulation PAG 66

67 CA Spanish Approach - CATF#13 - June 2008 System Verification Status - PROCEDURE NEW SYSTEM SYSTEM UPGRADE 1.1 DETERMINATION OF THE EATMN SYSTEM EXECUTION OF THE EC VERIFICATION 2.1 MANAGEMENT OF THE CA PLAN 1.2 DETERMINATION OF THE REGULATORY BASELINE 2.2 VERIFICATION OF THE OVERALL DESIGN PREPARATION OF THE EC DECLARATION 2.3 VERIFICATION OF THE DEVELOPMENT AND INTEGRATION OF THE SYSTEM 2.4 VERIFICATION OF THE OPERATIONAL SYSTEM Procedure agreed with NSA 2.5 VERIFICATION OF THE SPECIFIC SYSTEM MAINTENANCE PROVISIONS (from Eurocontrol Initial Guidelines) 2.6 MAKING THE TECHNICAL FILE 2.7 MAKING THE EC DECLARATION PAG 67

68 CA Spanish Approach - CATF#13 - June 2008 EC Declaration & Technical File One EC Declaration & Technical File per system. At first, the validity of EC Declaration is associated to the system lifetime. However some events shall trigger the modification of the Declaration: New Regulation. System Requirements major changes. Technical File contains all the evidences to support the EC Declaration. The Verification Matrix summarizes the whole process. PAG 68

69 CA Spanish Approach - CATF#13 - June 2008 Verification Matrix For a particular System it presents traceability among: User requirements (1). Interoperability requirements aplicable to the system (2). Reference material (4). (3) Traceability must be assured in the four verification phases : Overall Design, Development and Integration, Operational and Maintenance. To carry out the Verification Matrix means to give enough evidences of the Interoperability Requirements fulfilment in every verification phase. PAG 69

70 CA Spanish Approach - CATF#13 - June 2008 Example: introduction of new ATM function X Function Change in ATM-System EC Declaration & T.F. USER REQUIREMENTS IOP REQUIREMENTS Verif.PHASES REF.MAT FDP D DI OP M CS-SPEC-106 ATM-SYSTEM CONSTITUENTS HMI USER SDP REQUIREMENTS (1) SPV RECORDING INTEROPERABILTY REQUIREMENTS (ENTIRE APLICABLE REGULATION) (2) VERIFICATION PHASES (4) AENA-SPEC REFERENCE MATERIAL OACI-SPEC (3) DATA BASE VERIFICATION MATRIX PAG 70

71 CA Spanish Approach - CATF#13 - June 2008 Example: introduction of new ATM function X Function Change in ATM-System EC Declaration & T.F. DECLARATION USER REQUIREMENTS of ATM-SYSTEM IOP REQUIREMENTS TECHNICAL Verif.PHASES FILE (EVIDENCES) REF.MAT FDP HMI D DI OP M OVERALL DESIGN: CS-SPEC DECLARATIONS OF CONSTITUENTS: 1 Conformity 2 Suitability AENA-SPEC DEVELOPMENT & INTEGRATION FAT Report FAT Protocols OPERATIONAL INTEGRATION SPV SAT Report SAT Protocols Operational Readiness Report MAIENTENANCE User Manuals Maintenance Manuals OACI-SPEC PAG 71

72 CA Spanish Approach - CATF#13 - June 2008 AENA: Other issues to be solved Question 1: Ground/Ground Communications System Verification Mainly composed by non aeronautical COTS. Based on non aeronautical standards (i.e. TCP-IP) and use of Telco (not SES certified) networks (based on SLA). System verification difficult to be done as per the rest of systems (i.e. Safety Evidences). Question 2: ARINC/SITA/INMARSAT not obliged to be Certified under SES Regulation, Will they be certified for DLS services? Recommendation 1: It is not easy to track the publication of Regulations and CSs A Communication (via CATF?) would be advisable. PAG 72

73 CA Spanish Approach - CATF#13 - June 2008 QUESTIONS PAG 73

74 Agenda Item 6 Relationship between Implementing Rules, Specifications and Means of Compliance Jean-Paul Doré Regulatory Unit European Organisation for the Safety of Air Navigation

75 Overview of interoperability IR Relationship with MOCs Interoperability Implementing Rule Obligations of stakeholders to ensure interoperability of EATMN constituents & systems Interoperability requirements Performance requirements Associated procedures reqts Conformity assessment requirements Obligations of stakeholders to ensure coordinated introduction of new technology, concepts of operations Aircraft equipage, exemption cases Geographic coverage Dates of implementation Transitional arrangements 75

76 Notion of CS/Presumption of Conformity Recital (15) The putting into service of ATM systems should be subject to verification of compliance with the ERs and relevant IRs for interoperability; use of CSs creates a presumption of conformity with ERs and relevant IRs for interoperability A CS contains requirements refining EATMN solution compliant with relevant IR(s) Relationship between CS / IR Relationship between CS requirements and IR regulatory requirements 76

77 Overview of interoperability IR Relationship with CSs Interoperability implementing rule Obligations of stakeholders to ensure interoperability of EATMN constituents & systems Interoperability requirements Performance requirements Associated procedures reqts Conformity assessment requirements Obligations of stakeholders to ensure coordinated introduction of new technology, concepts of operations Aircraft equipage, exemption cases Geographic coverage Dates of implementation Transitional arrangements Requirements + Explanatory notes CS Requirements + Explanatory notes CS Dependent on requirements from external sources 77

78 Regulation & Community Specifications (SESAR View) CS specific Material and Compliance Annex Community Specification Reference to Core Technical Material Co m pli an ce SES Essential Requirements Implementing Rules Interoperability EUROCAE Document ED-XXX RTCA Documents DO-XXX Other technical specifications Eurocontrol or ICAO Documents Regulation 78

79 CS Requirements CS requirements independent from any external source to specify functional, operational properties CS requirements dependent on external source to filter out which requirements from an external source are applicable to overwrite specific requirements from an external source to specify requirements solving well-identified PDRs (Defect Reports) of external source to make reference to the appropriate version/edition of external documents 79

80 CSs specifying several means of compliance Why several MOCs? To divide a complex function spanning several layers into smaller independent units To create a well-bounded window to manage dependency with external sources of requirements To define alternative solutions Example: DLS Specification Air-ground data link services (DLIC, ACM, ACL, AMC) End-to-end communications Air-ground mobile data communications Operational procedures 80

81 CS / MOCs Interoperability implementing rule Obligations of stakeholders to ensure interoperability of EATMN constituents & systems Interoperability requirements Performance requirements Associated procedures reqts Conformity assessment requirements Obligations of stakeholders to ensure coordinated introduction of new technology, concepts of operations Aircraft equipage, exemption cases Geographic coverage Dates of implementation Transitional arrangements MOC 1 MOC 2 CS MOC 3 CS MOC 1 MOC 2 81

82 CS / MOCs MOC 1 (MOC 2 MOC 3 ) Obligations of stakeholders to ensure interoperability of EATMN constituents & systems Interoperability requirements Performance requirements Associated procedures reqts Conformity assessment requirements Obligations of stakeholders to ensure coordinated introduction of new technology, concepts of operations Aircraft equipage, exemption cases Geographic coverage Dates of implementation Transitional arrangements MOC 1 MOC 2 CS MOC 3 CS MOC 3 82

83 MOC Declaration in CS MOC Descriptor MOC Identifier MOC Change Record Traceability history towards Regulatory provisions Traceability towards international standards 83

84 EASA and SES dependent specifications Two regulatory systems EASA SES Regulations SES Community Specs ECTRL Specs EASA AMCs, GMs, TGLs A/C, CNS/ATM equipt Operators, orgs ANSPs, etc SES Safety acceptance CA of constituents & systems EASA Airworthiness cert. Operational approval Approval of orgs. MOC CONFORMITY? 84

85 EASA and SES dependent specifications Air-ground interoperability EASA and SES dependent specifications should rely on the relevant set of interoperability requirements EASA and SES conformity processes must be applied with the appropriate interoperability requirements baseline to ensure end-to-end interoperability of airborne and ground constituents 85

86 EASA and SES dependent specifications (SESAR View) CS specific Material and Compliance Annex Community Specification Reference to Core Technical Material Co m pli an ce SES Essential Requirements Implementing Rules Interoperability EUROCAE Document ED-XXX RTCA Documents DO-XXX Other technical specifications Eurocontrol or ICAO Documents Regulation Reference to Means of Compliance EASA CS: ETSO (& FAA TSO) Certification Specification Airworthiness* EASA Rulemaking and Regulatory Requirements 86

87 87 Question and Answer Session

88 Agenda Item 8 Open Tour de Table for Reporting on Conformity Assessment Activities European Organisation for the Safety of Air Navigation

89 Agenda Item 9 Outcomes of CATF#12 Actions: MET Systems Conformity Assessment Training European Organisation for the Safety of Air Navigation

90 MET SYSTEMS - Responses (1/2) Action 1: NSAs and ANSPs are invited to communicate their interpretation of the applicability of the interoperability Regulation requirements to MET systems. 6 responses: ANSP not certified to provide MET services. MET information to be verified as part of other groups of systems (e.g. AIS or ATS systems). Gathering of MET data is outside scope IOP regulation. IOP applies to the MET systems (and procedures) that process, display and communicate MET data (i.e. exporting it from the ANSP with systems such as ATIS and AFTN). Example: SAMOS & PAMOS. 90

91 MET SYSTEMS - Responses (2/2) MET data =SERVICE Therefore consider: MET info systems i.e. data processing (not: MET data systems i.e. acquisition and display). IOP regulation: no systems for acquisition of MET information Except: IRVR (could be considered a constituent of Navigation Systems). Weather radar systems (could be considered as constituents of Surveillance Systems). Attention thus on: ANSP end user systems & constituents; DSUs only for such end user systems. The following MET systems can be broken down into constituents: Automated Weather Observing Systems (AWOS) at airports Automated self-briefing systems at airports Dedicated information systems at ACCs ATIS, D-ATIS VOLMET, D-VOLMET 91

92 MET SYSTEMS Proposed Approach OUTSIDE EATMN: MET systems to collect, process and provide MET information to the first 7 systems (mainly systems for air traffic flow management, air traffic services) identified in Annex I of the interoperability Regulation PART OF EATMN: MET systems providing MET information to pilots via data link (D-ATIS and D-VOLMET). PLEASE SEND BACK YOUR VIEWS! 92

93 Training Requirements in Conformity Assessment (1/2) Action 2 NSAs and ANSPs are invited to communicate their requirements on training material to be developed in the conformity assessment area. 3 responses: CA = Assurance Activity (safety assurance, software assurance, quality assurance, test & integration assurance). Such courses run by certification bodies (e.g. DNV, BSI, SGS, Bureau Veritas). Basic training on verification activities = CBT. Once more IRs and CSs; more detailed training List of proposed subject areas (ref. AP CATF 13.5, item 3.3) 93

94 Training Requirements in CA Proposed Way Forward (2/2) 1 st step - extension of Guidelines to support CA of EATM systems and constituents by ANSPs and manufacturers 2 nd step complement, as appropriate, general regulatory training package with conformity assessment material 94

95 EUROCONTROL Regulatory Training Current and planned (1/3) Current ATM training courses at IANS (Institute of Air Navigation Services, Luxembourg) addresses safety regulations and other regulatory requirements Revised training package current courses will be updated to reflect changes in the European regulatory framework (SES I & II, EASA, SESAR aspects) and based on a customer survey 95

96 EUROCONTROL Regulatory Training incl. CA Planned (2/3) Safety regulatory training mandatory and optional courses aimed at giving NSA participants skills and competencies Other regulatory training voluntary participation at courses aimed at raising awareness and knowledge for participants from civil/military ATM stakeholders (NSAs, ANSPs, AOs, manufacturers, notified bodies) A revised training package for classroom and e-learning courses will address; Regulatory framework - ICAO SARPS, SES Regulations/Implementing Rules/ Community Specifications, EASA and SESAR aspects Specific on interoperability - essential requirements, conformity assessment of EATM systems and constituents, notified bodies and actual interoperability implementing rules 96

97 EUROCONTROL Regulatory Training incl. CA Next steps and Recommendation (3/3) Next steps A customer survey performed by IANS during Summer/Autumn 2008 to determine stakeholders requirements Present outcome of survey and draft training package at workshop in Autumn 2008 Updated/new training package will be implemented during 2009 Recommendation CATF members support the proposed way forward for regulatory training incl. CA training and contribute to the customer survey 97

98 Agenda Item 10 Any Other Business Date of next Meeting European Organisation for the Safety of Air Navigation

99 Proposed Date for CATF#14 Thursday 27th November 2008, 10H00 16H30 EUROCONTROL HQ, VEGA Meeting Room 99

100 Conformity Assessment Task Force Meeting # 13 EUROCONTROL Headquarters POLLUX Meeting Room 26 June 2008 European Organisation for the Safety of Air Navigation