Title: Conformity Assessment Task Force Meeting
1Conformity Assessment Task ForceMeeting 12
EUROCONTROL Headquarters VEGA Meeting Room 26
February 2008
2Agenda Item 1
Opening Approval of Agenda
3Agenda Item 2
Progress Report on Study Description and
Comparison of Airworthiness and Verification
Processes in EASA and SES Contexts By
Jean-Paul Doré Regulatory Unit EUROCONTROL
4Scope of the study
- Conformity assessment of constituents and systems
- Approval of introduction of changes of ATM systems
- Airworthiness certification
- Operational approval
of products supporting CNS/ATM functions
5Organisation of the study
WP1 Description/Comparison of Airworthiness
Certification Verification of conformity
RECOMMENDATIONS
SES
- AMC 20-11
- MEL Policy
- DL recording
- Non EU a/c
EASA
Findings / Issues
6 Objectives
- Identify similarities and dissimilarities of the
regulatory environments in respect of - Roles and responsibility of various actors
(European Institutions, National Authorities ,
manufacturers, - Process / Procedures to ascertain and certify
airworthiness capacity of parts, appliances
products - Process / Procedures to ascertain and declare
interoperability compliance of constituents and
systems - Process / procedures to ascertain and approve
capacity of organisations involved in the
lifecycle of products - Process / procedures to draft and maintain
Certification Specifications / Community
Specifications - Management of non-compliance cases
7Objectives
- To assess whether those similarities and
dissimilarities of EASA and SES regulatory
environments raise any issues when considering
airborne equipment supporting CNS/ATM functions - To highlight recommendations to sort out these
issues
8Overview of the approach
SES Reg DESCRIPTION
List of Findings Statements of Issues
GenericLife Cycle
COMPARISON
EASA Reg DESCRIPTION
94 series of findings with issues
FINDINGS
Coordination of EASA SES regulatory environments
Management of Specifications / MoCs
Implementation of regulations specifications
Applicability to non EU aircraft
104 series of findings with issues
FINDINGS
Coordination of EASA SES regulatory
environments
- To what extent should EASA and SES regulatory
environments be coordinated in areas such as - principles, mandatory requirements, means of
compliance, presumption of conformity - management of non compliance cases,
- exemptions cases,
- supervision of compliance of airborne
constituents
114 series of findings with issues
FINDINGS
Management of Specifications / MoCs
- To what extent should the development and
maintenance of - Certification Specifications and Community
Specifications applicable to airborne
constituents be based on an integrated lifecycle
? - With a methodical approach to manage dependency
between Certification Specifications, Community
Specifications - With a traceability mechanism between
Specification requirements and regulatory
requirements - With common measures to manage shortcomings of
Specifications
124 series of findings with issues
FINDINGS
Implementation of regulations specifications
To what extent should the verification /
certification of compliance of airborne
constituents be achieved without duplication of
efforts ? (unique process, unique procedure,
common evidences)
134 series of findings with issues
FINDINGS
Applicability to aircraft non Registered within
the Community
How to ensure that aircraft registered outside
the Community are fitted with airborne
constituents compliant with SES interoperability
IRs?
144 series of high level recommendations (HLRs)
HLR1
Coordination of EASA SES Regulatory Environments
Coordinated measures (terminology, non-compliance
cases, principles MoC, presumption of
conformity,)
HLR2
Management of Specifications/MoCs
Measures for the development and maintenance of
Specifications
HLR3
Implementation/ Regulations Specifications
Coordinated measures (unique process for the
verification/ certification of compliance,..)
HLR4
Applicability to non EU aircraft
Specific measures
15Next steps
- WP1 Findings / Statements of Issues / High
Level Recommendations from the top - down
approach - WP2 Description of the DLS case
- WP3 Safety acceptance and verification of
systems -
- WP4 Recommendations
16Question and Answer Session
17Agenda Item 3
Monitoring of EATMN Air-Ground Constituents and
Systems By Peter Martin EUROCONTROL Experimental
Center
18Objective
- Present Monitoring as a New Regulatory Process
- Describe Benefits based on EUROCONTROL Experience
- Feedback and Propose Next Steps
19Monitoring of EATMN Air-Ground Constituents and
Systems
- Operation Phase
- CNS/ATM Products Interoperability
- Collect and Analyse Operational Data
- Identify Anomalies, Inform Check Correction
20Mode-S Airborne Monitoring (1)
- Objectives
- Evaluate aircraft equipage over time
- Check correct operation of aircraft fleet
- Gather and report anomaly information
- Resolve detected anomalies
- Centralized Monitoring at EEC
- Receive data from 8 ANSPs each month
- Analyse data in a fully representative
operational environment - Design anomalies advise manufacturers may
require EASA action - Operation failures local action by airline
advise national regulator - Post monitoring to verify correction
21Mode-S Airborne Monitoring (2)
- Main root causes of anomalies
- Equipment failure Installation faults
- Unforeseen side-effects
- Misapplication of changes to rules or standards
- Failures in certification
- Example Losses of detection of Mode-S
transponders (2006) - Honeywell MST67A After SB with upgrade for
Elementary Surveillance - Honeywell PRIMUS After SB with upgrade for
Enhanced Surveillance - Challenger 604 a/c with Collins Transponder SB
for ADS-B - FILSER TRT800A New transponder manufacturer with
ETSO approval - Collins TPR-901 Generates erroneous squawk after
application of SB
22So Why Do Monitoring?
- Certification errors or inadequacies
- Operational failures
- Unintended consequences of changes
- A collected body of knowledge brings extra
benefits
23Regulatory Considerations
- Implications of Existing Regulations
- Monitoring as part of Regulatory Oversight (e.g.
1315/07) - Monitoring as part of Common Requirements (e.g.
2096/04) - Monitoring as part of Continuing Airworthiness
(e.g. 1592/02, 2042/03) - Independent Monitoring Not Mandated
- Prescriptive or Means of Compliance?
- Treatment of Global Services (e.g. GNSS GSA)
24Conclusion
- Diverse ongoing anomalies and causes imply
monitoring needed - Monitoring not well represented in current
regulatory framework - Possible organisational and regulatory scenarios
should be considered
25Lastly
- Now - Comments and Questions?
- Next Step Possible Scenarios
26Agenda Item 4
- The Use of Constituents Systems
- Supervision of Compliance
- By Bodo Heinzl
- German NSA
27Agenda Item 5
Meteo Systems and Constituents By Volker
Kurz German Meteo Services
28Agenda Item 6
The Use of Constituents Systems The Quality/CA
Approach By Mathy Gonon DSNA France
29Agenda Item 7
First Outcomes of the Conformity Assessment
Questionnaire By Jean-Paul Doré Regulatory Unit
EUROCONTROL
30Regulations, Specifications applicable to EATMN
(End 2007)
No IR, no CS dealing with architecture aspects
31Application of CA /1
- Compliance with ERs of
- systems put into service after 20 October 2005
- all EATMN systems and constituents required by 20
April 2011 (Art 10 of interoperability
Regulation) - ERs are very high level statements,
- Verification of compliance with ERs is open to
interpretation as long as IRs and CSs are not
sufficiently developed
32Application of CA /2
Essential requirements Implementing rules
Community Specs Other sources
Regulations
Specifications
?
?
What must be verified ?
Which EATMN constituent/ system ?
33Application of CA in a harmonised way
- Which EATMN constituents and systems?
- Common basis for the determination of EATMN
constituents and systems - What must be verified?
- Common basis for the allocation of Regulations
and Specifications to EATMN constituents and
systems
34Main Points of the Questionnaire
- I Procurement of COTS products
- II Putting on the market of constituents
- III Putting into service of systems
- IV Organisation of conformity assessment of
EATMN systems - V Needs for further guidelines
35I Procurement of COTS products /1Objectives
- To what extent products purchased by ANSPs for
integration in EATMN should be considered as
constituents - Many products are not designed specifically for
integration in EATMN (electronic appliances,
printers,) - Mark of electronic appliances in compliance with
directive on WEEE directive (waste electronic and
electrical equipment,) - Mark of electronic appliances in compliance with
RTTE directive, Radio equipment and
telecommunications terminal equipment)
36I Procurement of COTS products /2Answers to
questions 6.3.1 to 6.3.5
37I Procurement of COTS products /3Consolidated
position
38II Putting on the market of constituents
/1Objectives
- Manufacturers of EATMN constituents are
responsible for designing and manufacturing of
these constituents with a view to placing it on
the Community market under his own name. - Questions aims at
- qualifying the granularity of constituents
- identifying criteria for determination of
constituents
39II Putting on the market of constituents /2
Answers to questions 7.3.x, 7.4.x, 7.5.x
40II Putting on the market of constituents /3
Consolidated position
Notion of class A B constituents
41II Putting on the market of constituents /4
Consolidated position
Notion of class C constituents
42III Putting into service of systems
/1Objectives
- Qualify the granularity of systems subject to EC
verification - Investigate tracks for the introduction of a
progressive approach to conduct conformity
assessment
EC declarations Technical files
Granularity of systems
Progressive approach
IRs / CSs / Standardised architecture
43III Putting into service of systems /2 EATMN
Systems
EATMN is subdivided into eight systems
(interoperability Regulation)
44III Putting into service of systems /3 EATMN
systems
EATMN system is a system of systems
High level System
High Level Systems
System C
Low Level Systems
System A
System B
45III Putting into service of systems /4 EATMN
systems
High level System /ATC
High level System / ___
High Level Systems
Low Level Systems
No, low level systems for this domain
FDPS
Each high level system can be further subdivided
into low level systems depending on specific
conditions.
46III Putting into service of systems /5Answers
to questions 8.2.x, 8.3.x
47III Putting into service of systems /6
Consolidated position
48IV - Organisation of CA of EATMN systems
Objectives
- To investigate possible practical solutions for
the organisation of CA by ANSPs - To better identify the scope of the verification
activities in relation with the lifecycle of the
systems - To better identify the content of the CA products
(e.g. the technical file) - To investigate the impact of changes on the CA of
systems
49IV - Organisation of CA of EATMN systems Answers
to questions 9.2.x, 9.3.x
50IV - Organisation of CA of EATMN systems
Consolidated position
51IV - Organisation of CA of EATMN systems
Consolidated position
52IV - Organisation of CA of EATMN systems
Consolidated position
53V - Needs for further guidelines /1Answers to
questions 10.1.x, 10.2.x, 10.3.x
54V - Needs for further guidelines /2Consolidated
position
- Conformity assessment of systems supporting ATM
operations
55V - Needs for further guidelines /3 Consolidated
position
- Conformity assessment of systems supporting ATM
operations
56V - Needs for further guidelines /4 Consolidated
position
- Conformity assessment of constituents
57Next steps
- Next steps further analysis of comments
- Next step for the development of Guidelines
- Definition of constituents for Communication,
Navigation and Surveillance - Definition of high level EATMN systems
58Agenda Item 8
Progress Report on SES Mandates
59Agenda Item 9
A.O.B. Date of Next Meeting
60Next Meeting
- CATF13
- Thursday 26th June 2008, 10H00-16H30
- POLLUX meeting room, EUROCONTROL Headquartes.
61Conformity Assessment Task ForceMeeting 12
EUROCONTROL Headquarters VEGA Meeting Room 26
February 2008