IORS Project Workshop for top reporting design organisations Way forward for Reporting Organisations Dominique ROLAND – Project Team member

Reporting occurrences to EASA TABLE OF CONTENT  Occurrence Reporting to EASA – New IORS Form 44 – Online reporting tool – Data bridge, mapping and exporting data – Process overview – EASA data fields  Next steps – Planning, contacts, actions… 14/06/20102 IORS Project - Workshop for top reporting design organisations

Reporting occurrences to EASA  With a new IORS Form 44 14/06/2010 IORS Project - Workshop for top reporting design organisations 3 Go to EASA web site Download IORS Form 44 Fill the form with initial information Fax or the form to EASA

Reporting occurrences to EASA  With the online reporting tool 14/06/2010 IORS Project - Workshop for top reporting design organisations 4 Go to EASA web site Select the IORS page Select the online reporting link Fill the form Print for archiving Click on the submit button

Reporting occurrences to EASA  With the online reporting tool 14/06/2010 IORS Project - Workshop for top reporting design organisations 5 Form content is attached as XML file Save your own copy of the XML file Add your own attachments Send the generated by the system Validation of data Import into EASA database EASA process

Reporting occurrences to EASA  With the databridge: Mapping and exporting data (Solution for top reporting organisations) 14/06/2010 IORS Project - Workshop for top reporting design organisations 6 Identify corporate data fields to be exported Map with EASA data fields Export data into CSV or XML file in accordance with EASA datamodel Export data Import into EASA database Import data

Reporting occurrences to EASA  Reporting process through databridge overview 14/06/2010 IORS Project - Workshop for top reporting design organisations 7 s with XML or CSV attach- ments for batch of occurrences One per occurrence if pdf, jpg or other attachment specific to the occurrence Initial reporting Communication with EASA PCM s Meetings (ARM) As of today… Management of occurrence Design organisa- tion analysis completed and occurrence closed by DO Design Organisa- tion occurrence data frozen further to the opening of a tracking sheet Update when data frozen Close upon satisfaction Closure by EASA

Reporting occurrences to EASA  EASA key data fields 14/06/2010 IORS Project - Workshop for top reporting design organisations 8 Internal Ref. No Reporting Organisation status Reporting Organisation TRS reference Used for identification of the occurrence,will be also used in the process when occurrence data is updated (update for data frozen)see below Open Tracking Sheet Closed Use to record the reference of the document tracking the actions performed for the purpose to close the occurrence

Reporting occurrences to EASA  EASA data fields table 14/06/2010 IORS Project - Workshop for top reporting design organisations 9

Reporting occurrences to EASA 14/06/2010 IORS Project - Workshop for top reporting design organisations 10 Reporting organisation feedback after workshop and review of the draft of EASA data field table 15/07/10 Finalisation of the databridge specification (including data field table) 30/07/10 Development of databridge by the design organisations 30/10/10 End of test phase 30/12/10 Occurrence reporting through IORS databridge 1st quarter 2011

Reporting occurrences to EASA  Contacts for top reporting organisations: 14/06/2010 IORS Project - Workshop for top reporting design organisations

Reporting occurrences to EASA  Questions and answers… 14/06/2010 IORS Project - Workshop for top reporting design organisations 12

Reporting occurrences to EASA Thank you! 14/06/2010 IORS Project - Workshop for top reporting design organisations 13