implementation of ata e-business standards to facilitate ... 1 ataebizstds_jon… · ata e-business...
TRANSCRIPT
Implementation of ATA e-Business Standards to facilitate Paperless Operations
Nov 2016, Ken Jones
History – from here
Today – to here
Some of the challenges
� Legacy data is sitting on paper (or scanned PDF like documents).
� Slow, careful change due to regulatory environment
� “That’s how we’ve always done it”
� Even when legacy systems are replaced by new M&E systems, access to data isn’t always easy
� Data quality, “cleanliness”
� Getting data from this system in our company to that system in their company.
ATA e-Business Program
� International standards program for information exchange to support engineering, maintenance, materiel management and flight
operations.
� Open membership
� 120 companies in 33 countries
� Over 800 active individual participants
� Neutral, consensus-based
� Collaborative web site: www.ataebiz.orgfor documents, balloting, calendars, email
History
� 1950’s / 1960’s
� ATA 100 – technical information, ATA numbers
� ATA 200 – material management, IBM punch cards
� Standards Evolved and Expanded
� Changing business needs
� Technological advances (EDI, SGML, XML)
� Today
� Broad suite of industry standards and data definitions
� Long list of adopters
� Standards deeply embedded in industry systems and processes
What were are trying to do
� Vision
� Enable the seamless exchange and availability of digitalinformation throughout the civil aviation industry.
� Mission
� Provide the aviation industry with benchmark information standards in support of aircraft maintenance and operations.
� We are committed to evolving shared standards and promoting implementation to contribute to increased business agility and reduced costs, while maintaining the highest levels of safety.
Functional / Lifecycle Scope
8
Design Production Operation Maintenance
Configuration Management
Maintenance Planning
Maintenance Procedures
Part Identification, Traceability, RFID
Initial Provisioning Delivery Config Reliability Data
Industry Performance Metrics
Supply Chain Mgmt/e-Procurement/Repair Order Admin/Warranty
Electronic Regulatory Documentation
Flight Operations Data/MMEL Data
Electronic Aircraft Logbook
Aviation Marketplace
Digital Data Security
Spec 2000
iSpec 2200/S1000D
Spec 42
Spec 2300
In Development
ATA, AIA, ASD
Collaboration
(S1000D)
Aircraft Transfer Records
ATA e-Business Specifications
� Spec 2000 “Suite” – Materiel, Reliability, Logbook, Regulatory Data, RFID standards
� iSpec 2200 / S1000D – Technical Information standards
� Illustrated Parts Catalog, Maintenance Manuals, Service Bulletin, MPD, Wiring Manuals, etc.
� Spec 2300 – Flight Operations Data
� Spec 42 – Digital Information Security
� Common Support Data Dictionary
� Definitions, characteristics, tags/identifiers for all data.
� World Airlines & Suppliers Guide
9
Typical Benefits
� Harmonization between different manufacturers, operators, software providers allowing movement of important business data in common formats
� Cost reduction – fewer manual processes
� Cut cost of receiving parts
� Cut cost of returning / exchanging aircraft
� Improve quality of data
� Facilitate the use of digital maintenance tools
� Enhanced record keeping
10
Typical ATA e-Biz Standard?
� Describes content for business information exchange
� Part numbers, dates, procedures, conditions, etc.
� Describes the “business rules” for a function
� Information that must always be provided
� information that must be provided if certain conditions exist
� Information that may be provided
� Uses CSDD to define fields to minimize misuse
� Describes the structure/ formats
� XML, flat file, CSV, etc.
� Messages (PO), Large Files (Provisioning, IPC, AMM, etc), ID data (bar-code, RFID, etc.)
11
Why XML?
� XML helps us to separate the structure from the content.
� Separate the formatting from the content
� Make the data application neutral
� Allow additional format validation using parsers, based on Schemas
� Allows hierarchy / relationships to be better depicted
� Easier to support from corporate databases
12
13
� The paper 8130-3
�A representative Use Case (courtesy Airbus, P&W)
Authorized Release Certificate
14
15
North Haven Facility closed
in 2003
Description
not consistent
with other
8130-3 tags
for this part
number
Did not start using page indicators for single
page 8130-3 tags until 5-17-2004.
Obsolete ODAR number
not used since 7-31-98Date format inconsistent
with P&W
This number would include the date
contained in Block #18
Mr. Hatch
retired on 3-
31-99
ARCs issued when Mr. Hatch was an
ODAR stated last name and then first
name
16
� The electronic 8130-3 using Spec 2000 Chapter 16 XML
XML – doesn’t look friendly
17
<?xml version="1.0" encoding="UTF-8"?> <!--Sample XML file generated by XMLSpy v2012 rel. 2 (http://www.altova.com)-->
<ATA_PartCertificationForm version="1.12" id="ID_1" xsi:noNamespaceSchemaLocation="ATA_PartCertificationForm_draft2011_5.xsd" mlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Block2> <CET FVI="2">EASA Form 1</CET> </Block2>
<Block3> <TDN>CERT12345678901</TDN> </Block3>
<Block4> <IssuerDetail> <SPL>D4296</SPL> <WHO>HEAD QUATER AIRBUS</WHO> <ADL> 1 Rond Point</ADL> <ADL>Maurice Bellonte</ADL> <CIY>Blagnac Cedex</CIY> <ZIP>31707</ZIP> <CNT>FR</CNT> </IssuerDetail> </Block4>
<Block5> <CIC>SIA </CIC> <CPO>PO123456789</CPO> <PSN>9998288799</PSN> <WON>4711abc</WON> <MRN>M1234567890</MRN> <BOX>840001</BOX> <CTN>C10000000</CTN> </Block5>
<Block6> <LIN>1</LIN> </Block6> <Block7> <PDT>COMPUTER</PDT> </Block7>
<Block8> <MFR>F6198</MFR> <PNR>A12345678901234</PNR> </Block8> <Block9> <QTY UNT="EA">1</QTY> </Block9>
<Block10> <SER>S12345678901234</SER> </Block10> <Block11> <PSC>NEW</PSC> </Block11>
<ManufacturedParts>
<Block13a> <DDA>A</DDA> </Block13a> <Block13b><DDA>Electronic Signature on File</DDA></Block13b> <Block13c> <ARN>EASA.21G.0001 </ARN> </Block13c> <Block13d> <NME>Klaus Malone</NME> </Block13d> <Block13e> <DAT>2012-06-20</DAT> </Block13e>
<Block12N>
<NewPartsData>
<PUR>Not for ETOPS </PUR> <ARW>AD 4711</ARW> <SBN>SB47114711</SBN> <SBN>a</SBN> <TTM> <OTT>123456</OTT> <TRF>O</TRF> </TTM> <TTM> <OTT>123456</OTT> <TRF>X</TRF> </TTM> <DMF>2011-08-13</DMF> <EXP>2014-08-12</EXP> <DrawingAndRevisionLevel> <SDN>a</SDN> <MFR>aaaaa</MFR> <REV>a</REV> <RVD>1967-08-13</RVD> </DrawingAndRevisionLevel> <DrawingAndRevisionLevel> <SDN>a</SDN> <MFR>aaaaa</MFR> <REV>a</REV> <RVD>1967-08-13</RVD> </DrawingAndRevisionLevel> <DSA>true</DSA> <ADC>C</ADC> <NOH>false</NOH> <AWD>a</AWD> <AWD>a</AWD> <ICC>880330</ICC> <PAH_Data> <SPL>aaaaa</SPL> <WHO>a</WHO> <ADL>a</ADL> <ADL>a</ADL> <CIY>a</CIY> <ZIP>a</ZIP> <CNT>aa</CNT> <STP>a</STP> <PCH>a</PCH> </PAH_Data>
</NewPartsData>
<PreviousCertificate previousCertificateFormat="P"> <SPL>FAPE3</SPL> <TDN>Prev12345678901</TDN> <CET FVI="1">EASA Form 1</CET> </PreviousCertificate>
<REM>This computer has to be configured according to the aircraft documentation AMM4711. This computer has to be configured according to the aircraft documentation AMM4712. This computer has to be configured according to the aircraft documentation AMM4713. This computer has to be configured according to the aircraft documentation AMM4714. This computer has to be configured according to the aircraft documentation AMM4715. This computer has to be configured according to the aircraft documentation AMM4716. This computer has to be configured according to the aircraft documentation AMM4717. This computer has to be configured according to the aircraft documentation AMM4718. This computer has to be configured according to the aircraft documentation AMM4719. </REM>
</Block12N>
</ManufacturedParts>
<Block1> <NAA>EASA</NAA> </Block1>
</ATA_PartCertificationForm>
XML – a closer look
18
<?xml version="1.0" encoding="UTF-8"?> <!--Sample XML file generated by XMLSpy v2012 rel. 2 (http://www.altova.com)-->
<ATA_PartCertificationForm version="1.12" id="ID_1" xsi:noNamespaceSchemaLocation="ATA_PartCertificationForm_draft2011_5.xsd" mlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Block2> <CET FVI="2">EASA Form 1</CET> </Block2>
<Block3> <TDN>CERT12345678901</TDN> </Block3>
<Block4> <IssuerDetail> <SPL>D4296</SPL> <WHO>HEAD QUATER AIRBUS</WHO> <ADL> 1 Rond Point</ADL> <ADL>Maurice Bellonte</ADL> <CIY>Blagnac Cedex</CIY> <ZIP>31707</ZIP> <CNT>FR</CNT> </IssuerDetail> </Block4>
<Block5> <CIC>SIA </CIC> <CPO>PO123456789</CPO> <PSN>9998288799</PSN> <WON>4711abc</WON> <MRN>M1234567890</MRN> <BOX>840001</BOX> <CTN>C10000000</CTN> </Block5>
<Block6> <LIN>1</LIN> </Block6> <Block7> <PDT>COMPUTER</PDT> </Block7>
<Block8> <MFR>F6198</MFR> <PNR>A12345678901234</PNR> </Block8> <Block9> <QTY UNT="EA">1</QTY> </Block9>
<Block10> <SER>S12345678901234</SER> </Block10> <Block11> <PSC>NEW</PSC> </Block11>
<ManufacturedParts>
<Block13a> <DDA>A</DDA> </Block13a> <Block13b><DDA>Electronic Signature on File</DDA></Block13b> <Block13c> <ARN>EASA.21G.0001 </ARN> </Block13c> <Block13d> <NME>Klaus Malone</NME> </Block13d> <Block13e> <DAT>2012-06-20</DAT> </Block13e>
<Block12N>
<NewPartsData>
<PUR>Not for ETOPS </PUR> <ARW>AD 4711</ARW> <SBN>SB47114711</SBN> <SBN>a</SBN> <TTM> <OTT>123456</OTT> <TRF>O</TRF> </TTM> <TTM> <OTT>123456</OTT> <TRF>X</TRF> </TTM> <DMF>2011-08-13</DMF> <EXP>2014-08-12</EXP> <DrawingAndRevisionLevel> <SDN>a</SDN> <MFR>aaaaa</MFR> <REV>a</REV> <RVD>1967-08-13</RVD> </DrawingAndRevisionLevel> <DrawingAndRevisionLevel> <SDN>a</SDN> <MFR>aaaaa</MFR> <REV>a</REV> <RVD>1967-08-13</RVD> </DrawingAndRevisionLevel> <DSA>true</DSA> <ADC>C</ADC> <NOH>false</NOH> <AWD>a</AWD> <AWD>a</AWD> <ICC>880330</ICC> <PAH_Data> <SPL>aaaaa</SPL> <WHO>a</WHO> <ADL>a</ADL> <ADL>a</ADL> <CIY>a</CIY> <ZIP>a</ZIP> <CNT>aa</CNT> <STP>a</STP> <PCH>a</PCH> </PAH_Data>
</NewPartsData>
<PreviousCertificate previousCertificateFormat="P"> <SPL>FAPE3</SPL> <TDN>Prev12345678901</TDN> <CET FVI="1">EASA Form 1</CET> </PreviousCertificate>
<REM>This computer has to be configured according to the aircraft documentation AMM4711. This computer has to be configured according to the aircraft documentation AMM4712. This computer has to be configured according to the aircraft documentation AMM4713. This computer has to be configured according to the aircraft documentation AMM4714. This computer has to be configured according to the aircraft documentation AMM4715. This computer has to be configured according to the aircraft documentation AMM4716. This computer has to be configured according to the aircraft documentation AMM4717. This computer has to be configured according to the aircraft documentation AMM4718. This computer has to be configured according to the aircraft documentation AMM4719. </REM>
</Block12N>
</ManufacturedParts>
<Block1> <NAA>EASA</NAA> </Block1>
</ATA_PartCertificationForm>
<SPL>D4296</SPL><TDN>ABX2012YY1247</TDN>
<CPO>PO12345</CPO>
<PNR>AB123456</CPO>
<SER>S123456</SER>
Great for processing by a system, checking against
databases, etc.
Same XML – with Stylesheet
19
Electronic Aircraft Transfer
Records Project Team
Aircraft Transfer Records
� Charter:
The Aircraft Transfer Records Working Group (ATRWG) is responsible to identify, evaluate and develop electronic data exchange standards for information associated with the transfer, return and re-delivery of an aircraft. The use of these electronic records is envisioned by lessors, lessees, buyers and sellers, including importing the data into the receiving operator’s systems to reduce errors and rekeying of data
21
Active Participants
� Manufacturers: Airbus, Boeing, Embraer, GE Engines (some component MFRs early on)
� Operators: AA, Atlas, FedEx, KLM, QANTAS, Finnair, United
� Solution Providers: AerData, SwissAviationSoftware, CloudCards, JANA
� Lessors: GE Capital, AerCap
� IATA
22
Electronic Aircraft Transfer Records
23
� Which documents would best lend themselves to becoming fully electronic? (e.g. XML tagged)
� Which documents would such fully electronic formats add little value? (e.g. scanned & indexed “electronic paper”)
� Reviewed IATA/ICAO/Lessor documents listing requirements. Prioritization methodology (loosely)
� High volume
� Information already often in database or Maintenance Information System
� Important to review in detail during the transfer
Electronic Aircraft Transfer Records
24
� Gained consensus on the following approach
� Develop an electronic “crate” to contain any type and format of document, with metadata (e.g. aircraft serial number, operator, date, etc.)
� Develop detailed electronic exchange format specifications for selected documents
� Push use of (and modify where necessary) other existing specifications
� “Back to birth” concepts would benefit from fully electronic records at aircraft original delivery
Electronic Aircraft Transfer Records
25
� Top Documents/Data Sets in work (to develop fully electronic):
� CRATE – electronic format to carry records, add metadata and facilitate digital signature
� AD Status
� Modification Status (includes SB / MOD / STC )
� Repair / Damage Status
� Installed Parts Status (HT, LLP, OC, CM)
� Maintenance Status (Last Done / Next Due)
� General Aircraft Status
Latest Activities
� Finalized CRATE structure
� Finalized AD Status
� Accomplished Proof of Concept with real data from FedEx to AerData
� Finalizing publication documents and XML
� Expect approval vote by end of Nov
� Publication December
� Next several data sets published by end of first quarter, depending on Proof of Concept
26
AD Structure
27
Small XML Sample
28
CRATE Structure
29
Relationships
30
AWG/ALAG (ICAO)
ATA e-Business Program, ATR Group
The transition process …
31
� Example “No Finger Prints” (existing digital ATA XML specifications)
E-ARC
� 8130-3, EASA Form 1, other authorities equivalent
� Developed with participation by airlines, MRO’s, manufacturers, regulatory authorities, and software providers
� An XML format for providing regulatory information
� Approved by FAA, EASA, Transport Canada
� Uses PKI based digital signatures to sign
32
Spec 2000 Ch. 17 – eLogbook
� The “Logbook” dataset
� Flight Log / Journey Log
� Maintenance Log (Faults/Squawks)
� Maintenance Action
� Maintenance Action Task
� Maintenance Action Part Replacement
� Maintenance Release
� Fuel Log
� Service Log
� Maintenance Log Resource
33
New Related Projects
34
� Electronic Work Packages / Task Cards
� There are ATA e-Business specifications for MPD and delivery of original maintenance planning processes
� There is no standard for how various software implementations identify which jobs/tasks are accomplished
� This project is beginning the process for development of such standards
� Configuration Management
� Review formats to facilitate a computer to computer comparison of as-flying aircraft configuration with an allowable configuration file
35
� Summary
So what does it mean?
� Rapid changing environments at the operator –the need to manage change
� New systems / old systems – the need to integrate
� More partners – the need to share
� More information – the need to distill
� Same old cost pressure - the need for reduced cost
� THE NEED TO STANDARDIZE
� THE NEED FOR STANDARDS DEVELOPMENT PARTICIPATION
36
38
� Additional Background Info
39
� Visualizing the problem
Simple Component Life
40
Fault
Remove component
Send to shop
Receive from shop
Install component
Selected Information Flow
41
Fault
Remove component
Send to shop
Receive from shop
Install component
• Record Fault in Logbook• Record situational
information (flight, time, altitude, other noticed issues, fault codes, maintcodes, etc.)
Selected Information Flow
42
Fault
Remove component
Send to shop
Receive from shop
Install component
• Review troubleshooting options
• Review maintenance documentation, configuration documentation
• Remove part and tag unserviceable
• Record part number, serial number, identify reason for removal
• Record flight hours, cycles, etc
• Update logbook appropriately
Selected Information Flow
43
Fault
Remove component
Send to shop
Receive from shop
Install component
• Prepare Purchase Order with appropriate part number, serial number, commercial info
• Prepare Work scope for shop
• Provide shop reason for removal and other info to be confirmed
• Pack part• Send part shipped notice• Respond to shop quotes,
etc.
Selected Information Flow
44
Fault
Remove component
Send to shop
Receive from shop
Install component
• Receive shipment information
• Compare part serial number, part number to outgoing order
• Examine part for problems
• Review regulatory forms• Close out commercial
process (e.g. approve for invoice, process warranty)
• Return to shelf• Update inventory system
Selected Information Flow
45
Fault
Remove component
Send to shop
Receive from shop
Install component
• Review configuration• Review maintenance
documentation• Record part and serial
number• Record flight hours,
cycles, etc.• Update inventory system• Close logbook entry
46
� Visualizing the Standards with Tagged Data
Spec 2000 - Tagged/Formatted Data
47
SPL 81205BOX 12345CPO BS56877PNR HLT8100-13-91SHQ 1UNT EAPSN PS789254
NSN 1234128679632
Spec 2000 Receiving Label (data matrix)
Same Spec 2000 data formats in Purchase Order, Electronic Shipping Notice, Shipping Label, RFID, etc.
<ShipNoticeHeader><CIC>CNA</CIC>
<SPL>81205</SPL></ShipNoticeHeader><ShipNoticeDetails><CPO>BS56877</CPO>
<PNR>HLT8100-13-91</PNR><SHQ UNT="EA">10</SHQ>
<SHT>AMD</SHT><SHD>2004-09-30</SHD></ShipNoticeDetails>
Electronic Shipping Notice (XML)
RFID
MFR 81205*SER AB123*PNR HLT8100-13-91
ABC Distributor, 123 Main St.,Miiam, FL, USA 31005 CAM
S1BOOKED/QF2/81205/USD/1/BNO 3/341/EOIJ1234567/HLT8100-13-1/1/EA/25.20/15077
Spec 2000 Legacy EDI order
DirectPartMark
48
� The Specifications (more detail)
Spec 2000
49
� Began as Spec 200 related to materiel management.
� Migrated to Spec 2000 in the late 1980’s
� Material Management:
� Provisioning Data (ch. 1)
� Procurement Planning (ch. 2)
� Parts Order Management (ch. 3)
� Invoicing (ch. 4)
� Surplus Part data (ch. 12)
� Repair Management
� Repair Order Management, Invoicing, Teardown (ch. 7)
Spec 2000
50
� Automated Identification (ch. 9)
� Bar-coded shipping/receiving labels
� Permanent parts ID (bar-code, data matrix)
� RFID on parts
� Part Traceability
� Industry Metrics (ch. 13)
� Parts Delivery, Repair Process
� Warranty, Reliability
� Technical Resolution, Product Support Data
Spec 2000
51
� Reliability Data Collection (ch. 11) – Operational and Maintenance data feedback
� Aircraft Hours / Landings / Cycles
� Events / Delays / Cancelations
� Logbook Data
� LRU Removals (and installs)
� Shop Findings
� Scheduled Maintenance Data / Findings
� Service Bulletin / Mod Data / QPA
� Out of Service Data
Spec 2000
52
� Warranty Processing (ch. 14)
� Initial Delivered Parts List (ch. 15)
� Electronic Airworthiness Release Certificate (ch. 16)
� Electronic Logbook (ch. 17)
� Electronic Aircraft Transfer Records (TBD)
� AD Status
� Installed Parts Status
� Repair / Damage Status
� Last done / next due Status
� SB / Modification Status
Spec 2300
53
� Provides industry standard for management, configuration, and exchange of digital flight operations technical data
� Covers data pertaining to:
� Flight Crew Operating and Training Manuals
� Cabin Crew Operating and Training Manuals
� Weight and Balance Manual
� Master Minimum Equipment List
� Dispatch Deviation Guide
� Configuration Deviation List
Spec 2300
54
� Based on a Data Module paradigm, not document based
� Provides a standard for Phases of Flight
� Includes Flight Operations Markup Language (FOML) – a set of XML Schemas for data exchange
� Original published draft was released in May 2009. Six subsequent revisions since then; most recent published in June 2014
� Developed and maintained by the ATA Flight Operations Interest Group (FOIG)
Spec 42
55
� Provides industry standard for:
� Authenticating the senders and receivers of digital data
� Verification if data has been altered
� Traceability of data to their source (non-repudiation)
� Based on Public Key Infrastructure (PKI)
� Includes Certificate Policies – describe the comprehensive procedures and controls for management of digital certificates and signatures:
� Identity proofing and vetting
� PKI Key management
� Credential assurance level recommendations
56
� Current or Recent Projects
Active / Recent Projects
� Spec 2000 Procurement
� Update the widely used specification to better support new business processes (e.g. Multi-line PO’s, better shipping management, better 2-way communication messages, etc.)
� Flight Operations Data Exchange (Spec 2300)
� Recently published 2014 release which includes Flight Crew Training Manual, Cabin Crew Operating Manual and Weight and Balance Manual
� Digital Security (Spec 42)
� Recent updates include identity authentication assurance levels, non-PKI credentials, updates to certificate policies, and common methods of digital signature interoperability
Active / Recent Projects
� Reliability Data Exchange (Spec 2000 ch. 11 & 13)
� Recently added a short term Out Of Service record
� Recently added a Quantity Per Aircraft Record
� Updating aircraft reliability metrics
� RFID on Parts
� Standardized methods of storing key data on permanent RFID tags
� S1000D / CAWG
� Completed Civil Aviation changes for version 4.2
� Harmonizing graphics styles
� Updating Business Rules for implementation in Civil Industry