ICB. Industry Consultation Body. Community Specifications: from the perspective

Transcription

1 Community Specifications: from the perspective of the IOP Vice Chairman ETSI-CEN Joint Workshop on Community Specifications 17 th March 2011, Brussels Michael Mowinski Vice Chairman interoperability sub group

2 Overview Who the is and what they do Lessons learnt Personal views on some of the challenging issues industry now faces in the pursuit of interoperability 2

3 Who is the? The represents the ATM industry in its widest sense: Air Traffic Service Providers and Communication, Navigation Surveillance Service Providers Airspace Users Airports Manufacturing industry Professional staff representative bodies Meteorological Service Providers Observers Eurocontrol, Non-European Interests (FAA and AIA) Military (CMIC), Research Establishments (EATRADA) Standardisation Bodies (ATMSCG) SJU 17 March

4 What does the IOP SG do? The interoperability sub group (IOP SG) of the develops draft positions and recommendations to the European Commission on the requirements and priorities for the production of legislative material in support of improved future ATM interoperability Standardisation is a key subject within this role and as such the IOP SG identifies, within its work programme, the need to provide advice to the EC on: the process of standards development the way organisations or stakeholders are involved subjects on which European standards are needed (e.g. MET) 17 March

5 What has the (IOP SG) recommended? The IOP SG has advised the European Commission on numerous aspects of interoperability - all with industry wide support The European Commission has followed this advice Development of guidance document on CS process Recommended that a CS on FDP should not cover civil-military interoperability Five specific recommendations for development of future IRs Recommended a MET inventory and subsequently a MET CS Recommendations on the IP1 regulatory roadmap Postponement of CS on datalink security Developed views on European standardisation Added a transitional clause to the FMTP IR Exemptions for the datalink IR Mandate for an IR on PBN CS on CCD/CDA should not be developed Recommended that IR on SPI is too premature to publish Recommended CS on AMHS, GBAS, APV, ADQ and 17 March 2011 DLS 5

6 Lessons learnt 6

7 Resources & Timing Development of a CS should not require significant resource CS development relies on industry-initiated funding CSs should only be developed when the technical input material is mature Insufficient synchronization between the deployment schedule of IRs and the publication of their means of compliance CS should clearly reference technical specifications rather than repeat material Focus on the traceability between the core input material and the relevant IR regulatory requirements EC have not issued mandates for development of SES standards for some time The standardisation roadmap could enable a clear plan to be developed 17 March

8 Organisations & responsibilities There are many organisations competing for the same work The institutional landscape is confusing with EASA certification specifications, EUROCAE specifications, ETSI standards, Eurocontrol specifications, Community Specifications, SARPS, etc SESAR is cooperating with FAA and providing input to ICAO, but SESAR only represents its members and not European industry in the wider sense advice is to the Commission, and there is no direct input to SESAR and EASA processes More on this later 17 March

9 A-CDM: A success story? Initiation based on recommendation in 2006 (M/390) Drafting & review by EUROCAE WG 69 and Eurocontrol CDM project between 2006 and 2008 CS developed by ETSI between 2008 and 2010 Consultation periods of 4 months (PE) and 2 months (NV) Listing in OJEU Summer airports using A-CDM CS for implementation (including MUC, BRU, CDG, FRA) 17 March

10 Personal views on some of the challenging issues industry now faces in the pursuit of interoperability 10

11 Overlapping legislation is adding confusion With SES II now two regulations co-exist for Interoperability SES IOP Regulation (EC ) No 552/2004 (amd. by (EC) No 1070/2009) EASA Regulation (EC) No 216/2008 Dual meaning of a CS adds confusion Community Specifications - Contain technical and operational requirements EASA Certification Specifications - Contain detailed technical standards - Non-binding, voluntary - Are soft law but made binding through certification basis - Provide a presumption of compliance with the applicable SES IR and relevant SES ERs - Provide a presumption of compliance with the essential requirements of EASA regulations 17 March

12 Interoperability and safety are complementary but different Clear and efficient coordination between EASA and SES system necessary EASA ERs for systems and constituents are considerably different to the ERs of the Interoperability Regulation Avoid overlapping and duplicating work Responsibilities must be clear and timely coordination between activities in same areas important, e.g. Datalink with ground and airborne parts EASA is participating in, this relationship is important No representative in EASA SSCC 17 March

13 Finding the level at which to standardise is difficult To maximise the single market whilst ensuring interoperability, regulation should set requirements at the performance level with the means of compliance providing the link to technology. CSs would support and accelerate procurement and deployment of technology required from the ATM Masterplan Industry only recognises technology standards, and the aviation industry is very specific and small How could future IRs and CSs support the ATM Masterplan whilst enabling ANSP freedom to manage the system towards performance targets? 17 March

14 Future standardisation and regulation must include industry Standardisation and Regulatory Roadmap provided by SJU SWP C.3 Provides a detailed plan of standardisation activities Provides Roadmap of proposed activities required to meet the needdates of the European ATM Master Plan Triggers global harmonisation activities (ICAO) Close coordination and consultation with required 17 March

15 Thank you for your attention 17 March