Feedback from affected parties

2nd IORS WorkshopDecember 7, 2011

Santiago Haya-Leiva

07/12/2011 Feedback from affected parties 2

IntroductionIdentified benefits

Reporting OrganizationsEASA

Identified impactReporting OrganizationsEASA

Your experienceHow can we improve IORS?

Contents of the presentation

Introduction

07/12/2011 Feedback from affected parties 3

Creation of IORS does not modify existing:

Regulations Reporting requirements Responsabilities of involved parties Decision making processes (CAW)

Introduction

07/12/2011 Feedback from affected parties 4

Creation of IORS only modifies:

Means of reporting Entry inbox in EASA Handling of occurrences (EASA)

Benefits and impacts on industry and EASA were identified

Identified benefits

07/12/2011 Feedback from affected parties 5

Agency

Harmonized processing of occurrences

across the Agency

Visibility/treacebility of actions

Single occurrence database (CAW)

Identified benefits

07/12/2011 Feedback from affected parties 6

Individuals (PCMs, OA TLs, Experts)

Single occurrence database for their

products (regardless the source)

Single interface to handle occurrences

and related actions (workflow)

Knowledge bank

Identified benefits

07/12/2011 Feedback from affected parties 7

Reporting Organizations

Harmonized treatment across products

Awareness of occurrences from other

sources (only own products)

Better EASA performance (data driven)

Feedback on actions taken (future)

07/12/2011 Feedback from affected parties 8

Identified impact

Reporting Organizations (TRO)

IT solution to generate reports in XML format (XSD v 4) Modification of procedures to report only to

report@easa.europa.eu Review of other affected procedures

Mitigating measures: Common definition of XSD (TRO-IORS) Exhaustive testing of XSD Compromise to stick to XSD V4 for a long while Flexible implementing programme Continuous communication of IORS status Close coordination in the go-live (telecon with TCH)

07/12/2011 Feedback from affected parties 9

Identified impact

Reporting Organizations (no TRO) Use of new PDF form Modification of procedures to report to

report@easa.europa.eu Review of other affected procedures

Mitigating measures:

Continuous communication of IORS status (i.e., DOA letter)

07/12/2011 Feedback from affected parties 10

Identified impact

EASA Long run project (started in 2009) New section (and department) Recruitment of new officers Development of IT tool with around 500 licences

Mitigating measures: Multi-directorate IORS team (study, definition

and implementation) Provision of sufficient budget Continuous Management support Exhaustive screening of software provider

07/12/2011 Feedback from affected parties 11

Identified impact

EASA staff

New interface to interact with occurrence data Minor modification on the CAP (only input and output) Potential increase of workload (data entry)

Mitigating measures: Representatives part of the IORS project since its

creation Involved in tests of the WFT Intensive training campagne

15 classroom trainings Development of e-learning course

Close coordination in the go-live phase (PCM-DOA TL)

07/12/2011 Feedback from affected parties 12

Your experience

REPORTING

Is the new form easy to use and submit?

Was the implementation of the XML output considered a major modification in your DB?

Have you noticed any disruption of reporting flow since you started reporting to IORS?

Are the reporting requirements clear for each type of organization?

COMMUNICATION

Is the communication on IORS implementation being sufficient?

What is your opinion about the IORS website?

What do you expect from IORS in the next year?

WHAT IS YOUR MAIN CONCERN REGARDING IORS?

07/12/2011 Feedback from affected parties 13

How can we improve IORS?

What is the main deficiency of IORS in your view?

What measure would you propose to simplify reporting to IORS?

Would you request higher IT security for transmitting reports?

What kind of public information would you expect on the IORS website?

What kind of information would you expect for restricted audience (NAAs or Stakeholders)?

…?

Thank you for your attention

Questions and Comments?

07/12/2011