IORS Project Workshop for top reporting design organisations

Download Report

Transcript IORS Project Workshop for top reporting design organisations

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/2010
IORS Project - Workshop for top reporting
design organisations
2
Reporting occurrences to EASA
 With a new
IORS Form 44
Go to EASA
web site
Download
IORS Form
44
Fax or email
the form to
EASA
Fill the form
with initial
information
14/06/2010
IORS Project - Workshop for top reporting
design organisations
3
Reporting occurrences to EASA
 With the
online
reporting
tool
Go to
EASA web
site
Click on
the submit
button
Select the
IORS page
Print for
archiving
Select the
online
reporting
link
Fill the
form
14/06/2010
IORS Project - Workshop for top reporting
design organisations
4
Reporting occurrences to EASA
 With the
online
reporting
tool
• Form content is attached as
XML file
• Save your own copy of the
XML file
• Add your own attachments
• Send the email
EASA process
• Validation of data
• Import into EASA database
Email generated
by the system
14/06/2010
IORS Project - Workshop for top reporting
design organisations
5
Reporting occurrences to EASA
 With the databridge: Mapping and exporting data
(Solution for top reporting organisations)
• Identify corporate data
fields to be exported
• Map with EASA data fields
• Export data into CSV or
XML file in accordance with
EASA datamodel
Import data
• Import into EASA database
Export data
14/06/2010
IORS Project - Workshop for top reporting
design organisations
6
Reporting occurrences to EASA
 Reporting process
through databridge
overview
• E-mails with XML
or CSV attachments for batch
of occurrences
• One email per
occurrence if pdf,
jpg or other
attachment
specific to the
occurrence
Initial
reporting
14/06/2010
Management
of occurrence
• Communication
with EASA PCM
• E-mails
• Meetings (ARM)
• As of today…
• Design organisation analysis
completed and
occurrence closed
by DO
• Design Organisation occurrence
data frozen
further to the
opening of a
tracking sheet
Closure by
EASA
• Close upon
satisfaction
Update when
data frozen
IORS Project - Workshop for top reporting
design organisations
7
Reporting occurrences to EASA
 EASA key data fields
Internal Ref. No
Reporting
Organisation
status
Reporting
Organisation TRS
reference
14/06/2010
• 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
IORS Project - Workshop for top reporting
design organisations
8
Reporting occurrences to EASA
 EASA data fields table
Input Att
Input Attribute
Number
Airbus, Dassault
Aviation,
Eurocopter, Rolls
Royce
Deutschland,…
List of Countries
EASA Approval
Number
Default value
Mandatory Field
1
Reporting Organisation Name
RI
Yes
Text
2
Reporting Organisation Country
RI
Yes
Pick-List
3
Reporting Org EASA Approval Ref.
RI
No
Text
RI
No
Text
AOC number
Empty
RI
RI
RI
RI
RI
RI
No
No
No
No
No
No
Text
Text
Text
text
Date
Date
Free text
Free text
Free text
Free text
yyyy-mm-dd
yyyy-mm-dd
Initial report
Full report
Follow-up report
Free text
yyyy-mm-dd
Free text
Open, Tracking
Sheet, Closed
Free Text
Free text
State of Registry,
Type Certificate /
Design Approval
Holder, Operator,
CAMO
Empty
Empty
Empty
Empty
Empty
Empty
Free text
Empty
Free text
Empty
5
6
7
8
9
10
Operator AOC number (for operator
reporting)
Internal Ref. No
Name of Submitter
Telephone number
E-mail address
Date of finding
Report Date
11
Report Type
RI
No
Pick-List
12
13
14
Initial Report Reference
Initial Report Date
Issue
RI
RI
RI
No
No
No
Text
Date
Text
15
Reporting Organisation status
RI
No
Pick-List
16
17
Reporting Organisation TRS reference
Reporting Organisation Classification
RI
RI
No
No
Text
Text
4
14/06/2010
Category Mandatory Data Type Possible Values
18
Parties informed
RI
No
Pick-List,
multiple
entry
19
Name of informed Type
Certificate/Design Approval Holder
RI
No
Text
20
References
RI
No
21
Title/Summary
OS
No
Text,
multiple
entry
Text
22
Occurrence Class
OS
No
Pick-List
23
ATA
OS
No
Pick-List
(2 digit)
24
Detection phase
OS
No
Pick-List
+Text
OS
No
Pick-List
(multiple
entry)
+Text
Location of Occurrence
Last departure point
Planned destination
FI
FI
FI
No
No
No
Text
Text
Text
Aircraft Make and Model
AI
No
Text
25
Cause of Occurrence
26
27
28
29
Free text
Accident, serious
incident, incident,
not determined
List of ATA chapter
numbers
Scheduled, NonScheduled, Taxi,
Take-Off, Climb,
En-Route,
Descent,
Approach,
Landing, Hovering,
Ground Handling,
Manufacturing,
Unknown, Other
(specify)
Design,
Production,
Inadequate
Maintenance,
Operational,
Fatigue, Corrosion,
Unapproved Parts,
Human Factors,
Part Condition
specify, Not
determined, Other Specify (Text)
Free text
Free text
Free text
List of Aircraft
Make and Models
Mandatory Field
Empty
Empty
Empty
Empty
Empty
Empty
Empty
Empty
Empty
Empty
Incident
Empty
Empty
Empty
Empty
Empty
Empty
Empty
IORS Project - Workshop for top reporting
design organisations
9
Reporting occurrences to EASA
• Reporting
organisation
feedback
after
workshop
and review of
the draft of
EASA data
field table
15/07/10
14/06/2010
30/07/10
• Finalisation
of the
databridge
specification
(including
data field
table)
30/12/10
• Development
of databridge
by the design
organisations
30/10/10
IORS Project - Workshop for top reporting
design organisations
• End of test
phase
• Occurrence
reporting
through IORS
databridge
1st quarter
2011
10
Reporting occurrences to EASA
 Contacts for top reporting organisations:
14/06/2010
[email protected]
4038
[email protected]
4060
[email protected]
2014
IORS Project - Workshop for top reporting
design organisations
11
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