Fundamental Guidelines to Regulatory Approval for Paperless

Fundamental Guidelines to Regulatory
Approval for Paperless Cockpit and
Paperless MRO
Richard McKenna
Skypaq
Toni Kivinen
Development Manager,
Finnair, Flight Operations
Agenda
Current Status within Finnair
How Finnair achieved Paperless Process
Successful Implementation Guidelines
Regulatory Fundamentals
Regulator Approach – Project Example
Roadmap to Paperless Process – Overview
Roadmap to Paperless Process – Example
Current Status within Finnair
• Class 1 EFB Deployed Since 1999
• Full Paperless Cockpit inc:
• Charts
• Electronic Technical log (eLog)
• Electronic Documentation
• Operational manuals
• Information leaflets
• Performance Calculation Software
• Integration with MRO through eLog and Remote
Tool
• Enterprise wide data integration
Current Status within Finnair
• EFB device
• Terminal devices for using EFB’s end user
applications
• COTS product (Commercial Off the Shelf)
• Cockpit EFB devices represent standard PC
hardware with Windows XP SP2 Tablet PC edition
operating system
• M11, A330, A340 : 3 per aircraft
• A32S, B757, E70/90: 2 per aircraft
• EFB devices for training and backoffice purposes are
either cockpit EFB devices or standard workstations
loaded with EFB revision
How Finnair achieved Paperless
Process
• Class 1 EFB in use since 1999, introduced in MD
11
• First use was for charts, other EFB operations
developed over time
• 3G/GPRS/WLAN Connectivity introduced in 2008
• Replacement of paper technical log process with
Skypaq eLog
• Initially on ERJ fleet, now across Airbus as well
• Remote Tool Deployment allows data to be sent
from hangar to cockpit
Successful Implementation
Guidelines
• Strong Business Case
• Regulatory Authorities in at start
• Provide technology platform that benefits both
Flight Crew and Technicians
• Strong relationship with both software and
hardware vendors
• EFB Administrator at senior level
• At start only replace existing work practise
• Plan for enterprise wide data integration
Successful Implementation
Guidelines
• EFB Hardware Management process
• SOPs in place to ensure that are flight operations are
not affected by any hardware malfunctions
• Hardware platform must produce strong commercial
benefits
• EFB Software Selections
• Software selected must improve processes within
cockpit during busy work environment.
• All software must produce strong commercial
benefits and process improvements over existing
paper process
• Strong Revision Control and Release Package
Procedures
Regulatory Fundamentals
• Inform Regulator at very start
• Comply with guidelines set down in EASA regs
• EASA TGL 36 and EASA Part M Sub Part G Technical
Log Process
• Appropriate hardware and hardware management
process must be in place
• New process must assist cockpit and hangar work
environment
• SOPs in place for hardware and software
malfunction – Also part of MEL
• Training plan implemented
• Provide background data on all new software or
hardware providers
Regulator Approach – eLog Project
• Regulator approached at start
• Key users identified
• eLog developed with customization
• Final version signed off and system tested
• Regulator approached again
• Training Plan
• Deployment and Fleet Selection
• Parallel process of 3 months started
• Regulator approached with test results
• Full electronic technical log process approved
Roadmap to Paperless Process –
Overview
• Ensure Strong Business Case
• Must Implement solutions that benefit both
Flight Ops. And Technical Services
• Hardware needs to be selected that makes
commercial sense
• Software products need to be selected that makes
commercial sense
• Enterprise Data Integration Plan
Roadmap to Paperless Process –
Example
• Parallel use with Flight Operations and Technical
Services
• Step 1 - Flight Ops select hardware
• Step 1 – Tech. Services select Ground Based eLog
• Step 2 – Flight Ops Implement Charts
• Step 2 – Tech. Services receive approval from
regulator for eLog
• Step 3 – Deployment of eLog to aircraft
Contact Details
Mr. Richard McKenna
Skypaq,
E-mail: [email protected]
Ph: +353 (87) 264 5194
Toni Kivinen
Development Manager,
Finnair, Flight Operations
E-mail: [email protected]
Ph: +358 (50) 392 6632