Upload
john-upham
View
76
Download
1
Tags:
Embed Size (px)
DESCRIPTION
John Upham Vice President at AirVault shares insights on how to manage aviation maintenance (Mx) records in the cloud in London at the AVM Summit. Topics include: Cloud definition; Saas; IaaS; PaaS; Why Cloud? Cloud benefits; Big Data; Aviation Maintenance Records (Mx) and FAA & EASA regulations.
Citation preview
Records Management in the Cloud
John Upham Vice President, Business Development - EAME
8 November 2012
Event Hashtags: #Aviation
#Cloud Twitter:
@AvMainMag @uphamj
@AirVaultCloud
About the Cloud
It’s Cloudy
– What is it?
Storm Cloud
– Objections
Compliance
– Regulators and Regs
Trends
– Forecast
2
IT’S CLOUDY
3
4
Cloudy
What is Cloud Computing?
5
Remote, on-demand computing, where data and programmes are accessed from any web-connected browser
Types of Cloud Services
6
Why Cloud Computing?
7
Why would an airline or MRO choose a cloud-computing solution for regulatory compliance?
Relieving the Burden on IT
8
What Do Cloud Vendors Provide?
9
SIMPLICITY COMPLEXITY
Choosing a Cloud Vendor
Decide: public cloud or private cloud? Reputation, years in operation, references, discussions and site visits with customers Ask about SLA commitment and actual uptime for the past few years Review security and functionality audits Ask about business continuity, redundancy, backups
10
Storm Cloud
11
A WORLD OF MRO’S
12
The Aviation Ecosystem
13
Airline Global Operations
14
When things fall apart…
15
Cloud as a Marketing Benefit
16
“Smaller MROs operating in countries where MRO services are newly emerging can increase their perceived reliability by
offering cloud-based records management.”
—James G. Brunke Former Chairman and President, Boeing Shanghai
COMPLIANCE
17
If only compliance were this easy
18
Owners are primarily responsible for Mx records – FAA – 14 CFR §121.363 – EASA – Part M, §A, Subpart B, M.A. 201 (a), (b) – Leased Aircraft? Operator responsible
How long must operators retain aircraft Mx records?
– FAA – 1 year, or until work superseded – EASA – 3 years, or until work superseded
For engines: Keep everything until next overhaul To preserve hull value: Keep everything until you transfer the asset—aircraft or engine
Compliance Breeds Documents
19
Mx Records & MROs
FAA - 14 CFR § 145.219 EASA - Part M, § A, Subpart F, M.A. 614 et seq. Must provide Mx record copies to the
owner or operator and retain: – FAA - 2 years – EASA - 3 years
Are electronic Mx records approved? – FAA – YES; Advisory Circular 120-78 – EASA – YES; Part M, § A, Subpart C, M.A. 305(h), and Subpart F, M.A. 614a
Must make all required Mx records available for inspection…at any time
20
TRENDS
21
The average heavy jet produces 15-25,000 records per year
Data Flood from Aircraft
22
New Engine Real Time Data – 230% increase New Plane Real Time Data – 60% increase
What Boeing knows versus
What their customers know
M&E Integration with Mx Records
23
M&E System generates task cards with or without barcodes
Mechanic completes work, signs off, and staff scans directly into Records system
System uses barcodes or uses OCR to recognize form and all machine print to auto-populate index fields and to enable full text searching
Bi-Directional sync updates both systems
E-Link in M&E to “dirty fingerprint” Mx Doc in Records
1
2 3
4
5 M&E System Mx Records System
Mobile apps
24
Unlocking the Hidden Data
25
• ECM Capabilities • Labor/Operational Savings • Enterprise capacity
• Image/Data Saas Infrastructure • Global Access / Best Practices • Security / Compliance Standards
SaaS Records Management
• Supplier Connections • Systems Connections • Application Interfaces
• Ecosystem Views • Application Knowledge • System Connectors
Systems Integration
• Process Definition/Audit • Multi-Systems Interface • Workflow Agility
• Integrated Workflow • Advisory Services • Application Templates
Business Process
• Dashboard /Reporting • Process Optimization • Performance Management
• SQL/Text/Form Data • Inter-System Data Rationalization • Data Analytics
Data Analytics
Customer Requirements
Mx Records System Capabilities
Performance Requirements
Clie
nt
Val
ue
Operational ROI Resource Utilization Transformational
Contact
Visit airvault.com
26
John Upham Vice President, Business Development
[email protected] • +1 978-621-8524
Event Hashtags: #Aviation
#Cloud
Twitter: @AvMainMag
@uphamj @AirVaultCloud