easa regulatory changes on the usage of software & systems

29
EASA crackdown on Aviation IT Systems How upcoming regulation changes will impact Software Keynote by: Sander de Bree, CEO – EXSYN Aviation Solutions Airline and Aerospace MRO & Flight Operations IT Conference, EMEA 2017

Upload: exsyn-aviation-solutions

Post on 22-Jan-2018

27 views

Category:

Presentations & Public Speaking


4 download

TRANSCRIPT

EASA crackdown on Aviation IT SystemsHow upcoming regulation changes will impact Software

Keynote by: Sander de Bree, CEO – EXSYN Aviation Solutions

Airline and Aerospace MRO & Flight Operations IT Conference, EMEA 2017

Please meet the star of the show:

www.easa.europa.eu/rulemaking-

tasks/rmt0276

Feel free to have a look

Important to know 1st introduction in February 2014

No technical consultation from EASA during proposal drafting

3 months NPA consultation started in jan-2017, now closed for consultation

We’re stuck with it!

Scope

Aircraft Technical Logbook data How to demonstrate AD compliance How to demonstrate compliance with repairs and modifications How to display compliance with scheduled maintenance How to diplay compliance with component requirements Counters and life time tracking on components Handling of historic data Management of data corrections and protection againts manipulation Aircraft Airworthiness data transfer between MRO / M&E systems Data integrity protection System Back-up control

Specific requirements and guidelines addressing how MRO / M&E systems handle:

ScopeToday I would like to focus on:

Aircraft Technical Logbook data How to demonstrate AD compliance How to demonstrate compliance with repairs and modifications How to display compliance with scheduled maintenance How to diplay compliance with component requirements Counters and life time tracking on components Handling of historic data Management of data corrections and protection againts manipulation Aircraft Airworthiness data transfer between MRO / M&E systems Data integrity protection System Back-up control

And also look at what we can do today to prepare ourselves

Highlighted items

Counters and life time tracking on components Handling of historic data Management of data corrections and protection againts manipulation Aircraft Airworthiness data transfer between MRO / M&E systems

Counters & lifetime trackingMain topics:

A full in-service history record for time controlled components must be available in the MRO / M&E system

Time controlled parts must be clearly identified in the system by their partnumber & serialnumber

The identified system must be able to track limits in calendar days, flight hours, flight cycles and landings

Counters & lifetime trackingMain topics:

A full in-service history record for time controlled components must be available in the MRO / M&E system

TSN & CSN of components can no longer be unknown in IT systems

Pool parts have their data sitting across multiple systems. This will need to be consolidated

Centralized parts tracking is very likely to emerge

Interface requirements between Pool providers and airlines

Counters & lifetime trackingMain topics:

Time controlled parts must be clearly identified in the system by their partnumber & serialnumber

Non aviation specifc manufacture software repurposed as aviation MRO software.

SAP productnumber instead of PN/SN no longer allowed

The identified system must be able to track limits in calendar days, flight hours, flight cycles and landings

Highlighted items

Counters and life time tracking on components Handling of historic data Management of data corrections and protection againts manipulation Aircraft Airworthiness data transfer between MRO / M&E systems

Handling of historic dataMain topics:

An IT system used for Airworthiness purposes must contain data of a minimum of 24 months of aircraft operation, with at least 36 months of Aircraft Techlog data

Exception is made when aircraft is younger then 24 months. In this case all relevant data since manufacture date must available

Historic data must be searchable and be able to be reviewed in a simple and easy interpretable manner

Handling of historic data

Any MRO / M&E software implementation currently taking place at an airline will need to transfer at least 2 years of historic data for:

Schedule maintenance compliance Component removals & installations AD compliance SB, Modifications compliance

Structural Damages & repairs Aircraft utilization Aircraft Technical logbook entries (at

least 3 years)

Same applies for any future MRO / M&E software implementation

Highlighted items Counters and life time tracking on components Handling of historic data Management of data corrections and protection againts manipulation Aircraft Airworthiness data transfer between MRO / M&E systems

Data corrections & protection

Main topics:

It must be traceable which user made which ammendments on airworthiness records

For any data change made, both the original and changed entry must be available

Safeguards againts unauthorized user acces

Data corrections & protection

The end of EXCEL in airworthiness management

MRO softwares will require full logging of DB field changes

Highlighted items

Counters and life time tracking on components Handling of historic data Management of data corrections and protection againts manipulation Aircraft Airworthiness data transfer between MRO / M&E systems

Airworthiness Data TransferMain topics:

Airline software architecture must allow for transfer of the aircraft continuing airworthiness records data to another system

An industry wide/worldwide format for data transfer needs to be used

Airworthiness Data Transfer

OEM centralized management systems need to be opened up to export and transfer of data

Airlines need to adopt a solution in their architecture that allows exporting & importing all aircraft airworthiness data in or out of their system(s)

Any Airworthiness Data Transfer Solution will need to comply to industry worldwide format

Airworthiness Data Transfer

Any Airworthiness Data Transfer Solution will need to comply to industry worldwide format Format not defined Currently most used formats are:

XML and SGML based on S1000D formatting Spec2000 expected to be starting bases

Highlighted items Counters and life time tracking on components Handling of historic data Management of data corrections and protection againts manipulation Aircraft Airworthiness data transfer between MRO / M&E systems

How about timelines?

What shall we do?

Fit/Gap Assessment

Download the RMT

Setup and implement your plan of approach

To SummarizeBy Q4 2019 EASA will implement new regulations for technical records,

specifically aimed at IT systems:

It will impact functional requirements as well as data requirements

The days of Excel are numbered, make sure to be ready for it

Fit / Gap analysis need to be made by airlines to ensure compliance and or how to reach compliance

Cross industry action will be required to address the issue of component life time values and aircraft data transfer

It’s T – 2 years

A small bonus

By Q3-2017 EASA to publish its data security NPA for

EFB & ETL

Introduction of on board

weight&balance NPA by Q1 2018

IATA standard for digital record

keeping by 2020

Publications:Human interaction with IT system in Aircraft MaintenanceEnhancing Airline Competitive Advantage thru IT systems

Aircraft Continued Airworthiness, vision 2030(Big) Data in Aircraft Maintenance

NextGEN Aircraft Reliability Monitoring

Sander de Bree

Founder & CEO EXSYN Aviation Solutions