ata ispec 2200 overview
TRANSCRIPT
ATA iSpec 2200 Overview
28 October 2004
Presented by
Dr. Andreas SchützeAirbus
28 October 2004ATA iSpec 2200 Overview Page 2
Contents
• History
• Description
• Functional Areas
• Technical Areas
• Digital Deliverables
• ATA SGML Concept
• ATA Data Model
• What’s Next?
28 October 2004ATA iSpec 2200 Overview Page 3
Contents
• History
• Description
• Functional Areas
• Technical Areas
• Digital Deliverables
• ATA SGML Concept
• ATA Data Model
• What’s Next?
28 October 2004ATA iSpec 2200 Overview Page 4
History
Creation of ATA Specification 2100 (ATA 100 appendix deleted)
ATA Specification 100 (early digital data specifications included)
Digital Data Specifications (incl. SGML) become Appendix of ATA 100
Creation of ATA Specification 2200(iSpec 2200) based on:- ATA 100- ATA 2100
< 1989 1989 - 1993 1994 - 1999 2000
28 October 2004ATA iSpec 2200 Overview Page 5
28 October 2004ATA iSpec 2200 Overview Page 6
Description
• Recommended specifications for the content, structure, and deliverables to meet communication requirements [physical, electronic and future technology] of aircraft product technical information.
• A suite of data specifications and data models for the digital representation and exchange of technical data.
• Objective is to:4Minimize cost and effort expended by operators and OEMs4Improve information quality and timeliness 4Ensure that manufacturers provide data that meets airline
operational needs
28 October 2004ATA iSpec 2200 Overview Page 7
Functional Areas
• Generic Resources4ATA Numbering System4Effectivity
• Maintenance Requirements4Scheduled maintenance4Maintenance Planning
• Maintenance Procedures4Maintenance manuals
• Configuration Management4Aircraft, engine and
component configurations4Next Higher Assembly
and Next Lower Assembly• Training (SDS only)• Flight Operations
4Master minimum equipment list
4Flight crew operating manual
28 October 2004ATA iSpec 2200 Overview Page 8
Technical Areas
• Data Model4 Integrated Data Environment
• SGML Specifications4DTD Requirements (GenReq, FuncReq, TechReq)4SGML Document Type Definitions (DTDs)
• Graphics4ATA graphic profile for
TIFF and CGM4 Intelligent graphics,
wiring diagrams4Multi-media4Style guide
• Direct Access and Retrieval4Retrieval requirements,
language and schemata4Direct Access4Digital Security4Digital Certificates4Digital Signatures
• Common Support Data Dictionary
28 October 2004ATA iSpec 2200 Overview Page 9
Digital Deliverables• Aircraft Illustrated Parts Catalog (AIPC)• Aircraft Maintenance Manual (AMM)• Aircraft Recovery Manual (ARM)• Component Maintenance Manual (CMM) • Component Maintenance Manual Parts List (CMMIPL)• Consumable Products Manual (CPM)• Engine (Shop) Manual (EM)• Engine Cleaning Inspection and Repair Manual (CIR) • Engine Illustrated Parts Catalog (EIPC)• Engine Parts Configuration Management Section (EPCM)• Fault Reporting and Fault Isolation Manual (FRM/FIM)• Flight Crew Operations Manual (FCOM)• Illustrated Tool and Equipment Manual (ITEM) • Maintenance Planning Document (MPD) • Maintenance Review Board Report (MRB)• Maintenance Steering Group (MSG-3)• Master Minimum Equipment List (MMEL)• Non-Destructive Testing Manual (NDT)• Power Plant Build-up Manual (PPBM) • Power Plant Build-up Manual Illustrated Parts List
(PPBMIPL) • Production Management Database (PMDB)• Service Bulletin (SB)• Service Bulletin Index (SBI) • Structural Repair Manual (SRM)• System Description Sections (SDS) • Tool and Equipment Manual (TEM) • Weight & Balance Manual (WBM) • Wiring Diagram Manual (WM)• Graphics Exchange (GREXCHANGE) • Intelligent Graphics Exchange (IGEXCHANGE)
28 October 2004ATA iSpec 2200 Overview Page 10
Contents
• History• Description• Functional Areas• Technical Areas• Digital Deliverables
• ATA SGML Concept4What is SGML?4ATA SGML Methodology and DTDs in ATA iSpec 22004Basic ATA SGML Mechanisms (Effectivity, Revisions, …)
• ATA Data Model• What’s Next?
28 October 2004ATA iSpec 2200 Overview Page 11
ATA SGML Concept: What is SGML? (1/4)
A unique source of information …..<PROC><TITLE> Operational Test </TITLE> <WARNING>Make sure that... </WARNING> <STEP>On the maintenance panel<PANEL> 285VU </PANEL>,push the pushbutton switch...</STEP> <STEP>Open the circuit breaker...</PROC>Modifiable
Operational TestWARNING: MAKE SURE
Printing
JOB CARDCOVER PAGE
REFERENCE AMTOSS Task: 27-51-44-200-001Source Requirement: <MRB reference / hyper-reference>Periodicity: 1A
3C5000 hrs
Compliance Plan: <Compliance Matrix ID>Warranty-in-Effect: YESOther References: N/AElectrical Power: YESHydraulic Power: YESPneumatic Power: N/AFuel Load: N/A
SPECIALCONDITIONS(Entry conditionsdiffer from check-defaults) Other: Flaps 30 degreesSKILLS Categories: 38
01CAT
PartNumber
SerialNumber UNI Number FTN Q t y Description
ROTABLES 9791223 13569-98 25-15-132-169 1 EngineCONSUMABLES AC8624271 N/A 25-982-13 1 Screen assembly w/filter
999-04A-84 N/A 10 Lint free cloth and tricloroethaneTOOLING V-800 Series N/A 42-131-93 2 Sump Drain Tool
B18a3221 N/A 32-104-53 1 Access platform 1.8m (5ft. 11in.)9807803501 N/A 02-120-95 1 Zero locking flap slat CTL lever
Zone 835Left Side
A340-300 JC 2-53-80-48-001-01 795612041TITLE: FLAP INTERCONNECTING STRUT – INSPECT Position: L/H
Aircraft Check Station W O DurationDates341 C2 Y U L 12345678 8 Days 3
Mar 1998 – 11 Mar 1998
A340-300 JC 2-53-80-48-001-01 FLAP INTERCONNECTING STRUT – INSPECT Position: R/HAircraft Check Station W O DurationDates341 C2 Y U L 12345678 8 Days 3
Mar 1998 – 11 Mar 1998
Total Sign-off FLAP INTERCONNECTING STRUT – INSPECT
Revision Date: May 21, 1998 Page 1 of 3
Data ConsultationOff-line & On-line
Operational TestWarning : make sure thathidraulic systems are notpressurizedA. On the maintenancepanel
Data Loading
Technical Databases
EOConf.Data
28 October 2004ATA iSpec 2200 Overview Page 12
Structure
Title
Title Para
Chapter
AMM
Layout
Helvetica18pt, Bold
Helvetica12 pt, MediumIndentation ...
Content
This chapter .
FLIGHT CONTROL
• Separates the three main components of a document:4Structure4Contents4Layout
ATA SGML Concept: What is SGML? (2/4)
28 October 2004ATA iSpec 2200 Overview Page 13
• The Document Type Definition (DTD) defines the document structure including:4All elements and their attributes 4Element content model4Element sequence and occurrence
ATA SGML Concept: What is SGML? (3/4)
INTRO
PARA
Char
Char TITLE SECTION
Char Section contents
chapnbr
sectnbr
AMM
CHAPTERopt rep
repTITLE
lang
28 October 2004ATA iSpec 2200 Overview Page 14
<CHAPTER CHAPNBR="24">
<TITLE>FLIGHT CONTROLS</TITLE>
<SECTION SECTNBR="10">
<TITLE>AILERON</TITLE>
<PARA>The ailerons. . .
</PARA>
</SECTION>
</CHAPTER>
Element contents
Attribute initialisation
CHAPNBR="24"
• The SGML document is also called “SGML Instance”
</CHAPTER>End tag
<CHAPTERStart tag
ATA SGML Concept: What is SGML? (4/4)
• SGML mark up language components:4Elements (start tag, end tag)4Element content (nested elements, textual content)4Element attribute initialization
28 October 2004ATA iSpec 2200 Overview Page 15
Chapter 4-2. SGML Based Methodology and Document Type Definitions (DTD)
Blue sensitive zones are links to the CSDD
28 October 2004ATA iSpec 2200 Overview Page 16
Common Support Data Dictionary
Information about an elements / attributes
28 October 2004ATA iSpec 2200 Overview Page 17
Guidelines for working groups defining DTDs with the objective to reach maximum commonality between DTDs.
Chapter 4-2-3. DTD Technical Requirements
The principal common mechanisms are:Revision Management,Effectivity Management, Graphic Referencing Mechanism,Cellular Tables,Internal and External References Management,..
28 October 2004ATA iSpec 2200 Overview Page 18
<SUBTASK
KEY="XX" CHG="R" REVDATE ="XX" ...> ..
<LIST2>< L2ITEM>
<PARA> <REVST> Put a warning ... <REVEND>
<SUBTASK
KEY="XX" CHG="R" REVDATE ="XX" ...> ..
<LIST2>< L2ITEM>
<PARA> <REVST> Put a warning ... <REVEND>
Change bar
ATA SGML Concept: Revision Management
• Marking revisions at anchor element level:4KEY attribute: identification key of an element4REVDATE attribute: date of revision4CHG attribute (N, R, D, U)
• Marking revision of contents4Textual revision surrounded by:
– REVST element (revision start)– REVEND element (revision end)
4Deleted anchor: content replaced by element DELETED
28 October 2004ATA iSpec 2200 Overview Page 19
• EFFECT element 4EFFRG attribute (aircraft range)
• May be completed by:4a Service Bulletin condition SBEFF, 4or a Customer Originated Change condition COCEFF
ATA SGML Concept: Effectivity Management
** ON A/C 101-129, 131-199
<SECTION…..>
<EFFECT EFFRG = "101129 131199 ">
<TITLE> DC GENERATION … </TITLE>
<SECTION…..>
<EFFECT EFFRG = "101129 131199 ">
<TITLE> DC GENERATION … </TITLE>
<EFFECT EFFRG = "101129 131199 ">
28 October 2004ATA iSpec 2200 Overview Page 20
<GRAPHIC ….. KEY= "xx" >
<EFFECT>
<TITLE>
<SHEET .. KEY= "xx" GNBR="xx" SHEETNBR = "xx" ><EFFECT><TITLE>
<SHEET KEY= "xx" GNBR="xx" SHEETNBR = "xx" ><EFFECT><TITLE>
<GRAPHIC ….. KEY= "xx" >
<EFFECT>
<TITLE>
<SHEET .. KEY= "xx" GNBR="xx" SHEETNBR = "xx" ><EFFECT><TITLE>
<SHEET KEY= "xx" GNBR="xx" SHEETNBR = "xx" ><EFFECT><TITLE>
ATA SGML Concept: Graphic Management
• GRAPHIC element: composed of one or several SHEET elements
• SHEET element:4GNBR attribute contains a graphic entity4SHEETNBR attribute specifies the graphic sheet number
• GRPHCREF element: to refer to a graphic or sheet
28 October 2004ATA iSpec 2200 Overview Page 21
<TABLE>
<TGROUP>
<COLSPEC> <COLSPEC> <COLSPEC>
<THEAD><ROW>
< ENTRY> <ENTRY> <ENTRY>
<TBODY><ROW>< ENTRY> <ENTRY> <ENTRY>
<ROW>< ENTRY> <ENTRY> <ENTRY>
<TABLE>
<TGROUP>
<COLSPEC> <COLSPEC> <COLSPEC>
<THEAD><ROW>
< ENTRY> <ENTRY> <ENTRY>
<TBODY><ROW>< ENTRY> <ENTRY> <ENTRY>
<ROW>< ENTRY> <ENTRY> <ENTRY>
TABLE presentation
ATA SGML Concept: Cellular Tables
• Table structure:4THEAD element (header) 4TBODY element (table body)4TFOOT element (footer)4ROW element (table line)4ENTRY element (table cell)4COLSPEC, SPANSPEC element (column description)
28 October 2004ATA iSpec 2200 Overview Page 22
<GRPHCREF REFID="EN1234567890">
</GRPHCREF>
<GRPHCREF REFID="EN1234567890">
</GRPHCREF>
<REFINT REFID="EN244200861001">
</REFINT>
<REFINT REFID="EN244200861001">
</REFINT>
• Internal references
ATA SGML Concept: Management of References
• External references
<REFEXT REFMAN=" SSM" REFLOC="32-31/05">
</REFEXT>
<REFEXT REFMAN=" SSM" REFLOC="32-31/05">
</REFEXT>
28 October 2004ATA iSpec 2200 Overview Page 23
Contents
• History• Description• Functional Areas• Technical Areas• Digital Deliverables• ATA SGML Concept
• ATA Data Model4Vision4What is a Data Model?4Functional Areas4Deliverables
• What’s Next?
28 October 2004ATA iSpec 2200 Overview Page 24
ATA Data Model: Vision
Airport Mtce/Ops
Product Manufacturing
Product Maintenance
Shared Data
Regulatory Agency
Product Marketing
Flight Operations
Business Support
Air Traffic Mgmt
Industry wide agreement on the Information Architecture for information transfer (Structure, Format and Business Rules)
28 October 2004ATA iSpec 2200 Overview Page 25
ATA Data Model: What is a Data Model?
• Structured graphical representation of the processes, business rules and information/data interchanged between a manufacturer/supplier and operator
• Modeling methodology and techniques provide information/data in a standard, consistent, and predictable manner in order to manage data as a resource
• Enables re-engineering of business processes and product life-cycle information targeted to achieve a world-wide accepted Integrated Data Environment
28 October 2004ATA iSpec 2200 Overview Page 26
ATA Data Model: What is a Data Model?
• Critical Success Factors for the industry standard Data Model:4Generic - facilitates development of systems of varying purpose, scope and
complexity4Rigorous and precise - representation of data is complete, correct,
consistent and usable4Concise - facilitates improved understanding, communication, consensus
and validation4Conceptual - represents functional requirements rather than physical or
organizational constraints
• Flexible - supports phasing of the life cycle, i.e., M&E model to be followed by Flight Ops, Training, Material Management
• Application - use of the model enables improved:4Business process analysis4Applications development4Re-engineering4Systems integration4Acquisition of information systems
28 October 2004ATA iSpec 2200 Overview Page 27
ATA Data Model: Functional Areas
• Derived through an affinity analysis between the structured decomposition of the industry functions/processes and the information/data used by those functions/processes
• Functional areas (business areas) were then used in the architecture of iSpec 2200
• The functional areas are also consistent with a value chain analysis
28 October 2004ATA iSpec 2200 Overview Page 28
MaintenanceRequirements
“A”
MaintenanceProcedures
“C”
MaintenanceEvent
Forecasting
MaintenanceEvent
Production
MaintenanceEvent
Archive
ReliabilityAssessment
ConfigurationManagement
“B”
MaintenanceTraining
“D”
MaintenanceEvent
Planning
LineMaintenance
EventPlanning
Component Maintenance
EventPlanning
EnterpriseResource
Management
MaintenanceDiscrepancy
OperationsPlanning
ProductDesign
Engineering
FlightScheduling
FlightOperations
ATA Data Model: Functional Areas
28 October 2004ATA iSpec 2200 Overview Page 29
ATA Data Model: Deliverables
• General explanations on ATA CD, “ATA Data Model”
• Data Model developed using relational Data Modeling tool (COOL:Biz)
• Data Model accessible through Model Browser on Internet (including download capabilities)
• Contains:4Industry Decomposition Diagram4Entity-Relationship Diagrams divided in major subject areas4Entity, attribute and relationship definitions
28 October 2004ATA iSpec 2200 Overview Page 30
28 October 2004ATA iSpec 2200 Overview Page 31
28 October 2004ATA iSpec 2200 Overview Page 32
28 October 2004ATA iSpec 2200 Overview Page 33
28 October 2004ATA iSpec 2200 Overview Page 34
28 October 2004ATA iSpec 2200 Overview Page 35
What’s next?
Future Data Exchange Project
Information Set 3
Information Set 1
Information Set 2
Information Set n
...
INDUSTRYDATA MODEL
GenericResources
Flight Ops
Configur.Managem.
Mainten.Requirem.
Mainten.Procedures
GenericResources
Flight Ops
Configur.Managem.
Mainten.Requirem.
EXCHANGEDATA MODEL
Mainten.Procedures
Methodology &Technical
Requirements
XMLDesign Rules