spec 2000 overview

ATA e-Business Standards to facilitate Paperless Operations

Nov 2015, Ken Jones

History – from here

History – from here

Airlines maintained their own aircraft and components

A few disparate mainframe systems

Internal development staff

Information exchange was mostly paper

Unfortunately, paper is still all too common as a method of data storage and data exchange today.

Opportunities

4

Today

More maintenance partner companies

Fewer disparate systems (but still many)

Newer ERP and/or Best of Breed Solutions and new IT competition every day

Fewer internal development staff

More information, often available electronically

More mobile access and maintenance tools

Today – to here

Some of the challenges

Legacy data is sitting on paper

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.

8

Visualizing the problem

Simple Component Life

9

Fault

Remove component

Send to shop

Receive from shop

Install component

Selected Information Flow

10

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. etc.)


11

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


12

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.


13

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


14

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

15

The paper 8130-3

A representative Use Case (courtesy Airbus, P&W)

Authorized Release Certificate

16

17

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

18

The electronic 8130-3 using Spec 2000 Chapter 16 XML

XML – doesn’t look friendly

19

<?xml version="1.0" encoding="UTF-8"?> 

<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

20

<?xml version="1.0" encoding="UTF-8"?> 

<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

21

22

ATA e-Business Specifications

ATA e-Business Program

International standards program for

information exchange to support engineering,

maintenance, materiel and flight operations.

Open membership

Neutral/consensus-based environment

118 Member Companies

30% Operators, 30% Manuf, 40% Others

700+ Individual volunteers

Collaborative web site: www.ataebiz.org for documents, balloting, calendars, email

http://www.ataebiz.org/

Functional / Lifecycle Scope

24

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)

Electronic Aircraft Transfer Records

ATA e-Business Specifications

Spec 2000 “Suite” – ATA 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

25

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

26

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.)

28

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

29

30

Visualizing the Standards with Tagged Data

Spec 2000 - Tagged/Formatted Data

31

Optional area that may be used for company name, address, or additional bar coded data

SPL 81205

BOX 12345

CPO BS56877

PNR HLT8100-13-91

SHQ 1

UNT EA

PSN PS789254

NSN 1234128679632

Typical

7 3/8" (card stock)

8 ½ “ (std paper)

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

32

The Specifications

Spec 2000

33

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

34

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

35

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

36

Warranty Processing (ch. 14)

Initial Delivered Parts List (ch. 15)

Electronic Airworthiness Release Certificate (ch. 16)

Electronic Logbook (ch. 17)

Information exchange between e-Logbook systems and M&E IT systems

Maintenance Execution (TBD)

Formats and content definition for work packages, jobs / tasks

Formats for signoff’s and completion records

Spec 2000

37

Electronic Aircraft Transfer Records (TBD)

Facilitate the preparation, review and exchange of information associated with return / exchange of aircraft

Meant to replace scanning and tagging exercise done today with data that can be entered into system without keying

Start with:

• Electronic CRATE

• AD Status

• Installed Parts Status

• Repair / Damage Status

• Last done / next due Status

• SB / Modification Status

iSpec 2200

38

Industry standard for the development, management and exchange of digital technical manuals

Most widely adopted standard for technical data in the Civil Aviation industry

Based on the Standard Generalized Markup Language (SGML)

Home of the ATA Standard Numbering System (aka ATA Chapters; ATA Numbers)

iSpec 2200

39

Provides SGML Document Type Definitions (DTDs) for 18 manuals including:

Aircraft and Engine Illustrated Parts Catalogs (AIPC and EIPC)

Aircraft and Component Maintenance Manuals (AMM and CMM)

Fault Reporting/Fault Isolation Manual (FRM/FIM)

Service Bulletin (SB)

Structural Repair Manual (SRM)

Wiring Manual (WM)

S1000D

40

Collaborative effort between ATA e-Business, AIA, ASD, bringing together defense and commercial requirements.

Next generation “Technical Documents” using XML

Supersedes iSpec2200 for some new aircraft models

Data centric rather than document centric

Civil Aviation’s requirements are represented by the ATA e-Business Program through the CAWG

ATA e-Business Publishes a “Business Rules” specification helping define implementation details

Spec 2300

41

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 42

42

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

43

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

44

Component Life Revisited

45

Fault

Remove component

Send to shop

Receive from shop

Install component

Troubleshooting –S1000D, iSpec2200 Logbook – Spec 2000 Ch. 17

Reliability – Spec 2000 Ch. 11ID/Traceability – Spec 2000 Ch. 9

Repair / Procurement – Spec 2000 Ch. 3, 7Reliability – Spec 2000 Ch. 11ID/Traceability – Spec 2000 Ch. 9Regulatory – Spec 2000 Ch. 16

Reliability – Spec 2000 Ch. 11ID/Traceability – Spec 2000 Ch. 9Tech Info – iSpec2200, S1000DRecords – Spec 2000 Ch. 18

So what can you do?

Actively participate in standards development

Encourage staff to participate in standards development

Encourage internal development projects to implement and adopt information exchange standards

Encourage system providers to become standards compliant

Evaluate the system providers to understand what they really can do if they say they are standards compliant

46

Questions

202-626-4039

[email protected]

www.ataebiz.org

[email protected]

47

mailto:[email protected]

http://www.ataebiz.org/

mailto:[email protected]