Bruno Chatel 
bcha@chadocs.com 
ATA Spec 2300, 
implementation perspectives. 
Who, why, what, how… When? 
San Antonio, Jun...
ATA Spec 2300… Ready ? 
 Yes 
 
Cover all the business domains for Flight 
Operations 
 
XML Schema consolidation 
 
X...
Flight Ops data.. Global process 
OEM 
authoring 
validation 
approval 
publishing 
Operator 
Airline 
Ops manuals 
Fleet,...
OEMs implementation perspectives 
 Different cases 
1) New authoring/publishing environment for a new 
program 
2) New au...
New authoring/publishing environment 
for a new program 
 New program development 
– Triggers new Flight Ops documentatio...
Airbus Helicopters case study 
 Choice of a data model standard for the system 
– Detailed study to choose data model 
– ...
New authoring/publishing environment 
for an existing program 
 Same expected value added ! 
 But.. need to manage legac...
Keep an existing authoring/publishing 
system 
 And make a final conversion 
OEM 
authoring 
validation 
approval 
 It w...
Convert to ATA 2300 
 Conversions rules 
– (if applicable) Break monolithic manual/breakdown in PM and DM 
– Generate Cro...
And airlines/operators ? 
 Today only proprietary digital format 
– Dependant of OEM digital deliveries (when there is) 
...
ATA 2300 ? Why ? 
 Developing a new CMS 
– And take advantage of OEM delivery (if any) 
OEM A 
XML/SGML 
OEM B 
XML/SGML ...
How to go…. 
 First case: Wait for ATA 2300 OEM deliveries ! 
OEM A 
XML 
OEM B 
XML 
Customization 
(CMS) 
- revision im...
How to go…. 
 But it is also possible to start without OEM 
delivery 
– Making conversions from OEM proprietary 
publishi...
CMS to Viewer 
 Use ATA 2300 as the exchange data model between 
CMS/Customization and e-Viewer 
– Opportunity to differe...
Implementation of ATA 2300 (CMS, 
eViewer, …):Technical aspects 
 Many compliance with S1000d …but is not 
S1000d 
– S100...
The remaining question is…. 
WHEN? 
16 Bruno Chatel (bcha@chadocs.com) June 24 2014
Thanks ! 
Bruno Chatel 
Chadocs 
bcha@chadocs.com 
http://www.chadocs.com 
+33 4 96 11 14 57 
17 Bruno Chatel (bcha@chadoc...
Prochain SlideShare
Chargement dans…5
×

ATA Spec 2300, implementation perspectives. Who, why, what, how… When? Bruno Chatel

1 188 vues

Publié le

ATA e-Business FORUM 2014, Presentation Proposal, San Antonio, Texas, Bruno Chatel, Chadocs

From the version 2013.1, the ATA Spec 2300 can be considered as ready for implementation. This presentation details the implementation perspectives of the specification in the whole process of Flight Operations data management, from the OEM data producer to the operators’ needs and uses (customization and final pilot uses). It highlights the different possible scenarios to implement the specification, with the triggers, functional areas and the possible approaches, taking into account existing systems and constraints.

After a very short review of the status of ATA Spec 2300 (functional perimeter: Flight Operations data exchange, version 2013.1 all flight crew manuals, ready to implement), the presentation describes the global functional process of Flight Operations data management and identifies where ATA Spec 2300 is designed to be used. It also highlights the expected value-added in the process. OEMs are data producers, providing data to operators who need to customize and publish the flight ops manuals to final users (including on-board/on-ground e-viewer applications)..

Based on this global view, several opportunities to implement systems based on ATA Spec 2300 are studied:
o OEM: producing and delivering ATA Spec 2300 compliant data.
Based on different OEM approaches and taking into account the existing constraints (systems, programs, etc.), several questions are discussed: the triggers for OEM to implement such systems, the possible levels of support of the specification features, and, at a high level, the impacts on the current data production process.

o Operators/airlines: customizing OEM data, producing its own data, publishing in different environments (paper, electronic viewers, on board, on ground).
As an airline would take advantage of receiving ATA 2300 compliant data from OEMs when it will be produced, in the meantime an anticipated approach may be considered. The perspective for an airline to develop a new system to manage its flight operations data needs to consider the advantage of using ATA Spec 2300, a standard business-focused data format, as the core data model of the system and as the internal exchange data format between modules (content management, publishing engines, electronic consultation tools). The advantages and difficulties are discussed with the general principles of using ATA 2300 compliant features at different levels of the airline process.

Finally, for any scenario, the real remaining question is: when?

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

ATA Spec 2300, implementation perspectives. Who, why, what, how… When? Bruno Chatel

  1. 1. Bruno Chatel bcha@chadocs.com ATA Spec 2300, implementation perspectives. Who, why, what, how… When? San Antonio, June 24th 2014 1 June 24 2014
  2. 2. ATA Spec 2300… Ready ?  Yes  Cover all the business domains for Flight Operations  XML Schema consolidation  XML samples  And now? It is time for implementation… Who ? Why ? What ? How ? 2 Bruno Chatel (bcha@chadocs.com) June 24 2014
  3. 3. Flight Ops data.. Global process OEM authoring validation approval publishing Operator Airline Ops manuals Fleet, S/N Customization (CMS) - revision impact - authoring - approval - publishing Flight Manual, MMEL/DDG, FCOM/AOM, QRH Envelop Customized manuals AOM/FCOM, MEL, QRH, Operator manual Flight Manual Fleet, S/N On board/EFB Customized manuals MEL, other Approved manual Fleet, S/N On ground consultation tool (Ops manager, approval approval On board/EFB Local e-Viewer Flight crew authority training…) Flight Manual, Authorities MMEL Envelop (EASA, FAA, ..) e-Viewer (maybe OEM dependant) 3 Bruno Chatel (bcha@chadocs.com) June 24 2014
  4. 4. OEMs implementation perspectives  Different cases 1) New authoring/publishing environment for a new program 2) New authoring/publishing environment on existing program 3) Existing authoring/publishing environment  Why implementing ATA 2300?  What can be done and how ? 4 Bruno Chatel (bcha@chadocs.com) June 24 2014
  5. 5. New authoring/publishing environment for a new program  New program development – Triggers new Flight Ops documentation – Opportunity to develop a new authoring/publishing environment – Choice of a data model  To support business requirements  To deliver digital data – Allowing development of digital delivery and e-Viewer OEM authoring validation approval publishing 5 Bruno Chatel (bcha@chadocs.com) June 24 2014
  6. 6. Airbus Helicopters case study  Choice of a data model standard for the system – Detailed study to choose data model – Assessment of different data models  General requirements  Project business requirements S1000d ATA 2300 Modular XML (Proprietary data model for Flight Ops) SGML/Manual (Proprietary data model) General features Types of Content 70 120 110 85 Content Models 60 120 110 95 Data Management 104,5 129 94,5 42 Authoring 58,5 57 67 42 Approval 10 25 25 15 Publishing Common 60 70 65 65 Publishing Paper 0 0 0 0 Publishing electronic 30 88 83 10 Project Business Req Reqs_Planning,Research&Analysis 20 8 16 0 Reqs._Authoring 225 270 250 115 Reqs._Validation&Approval 0 25 25 10 Reqs._Publishing 161 216 188 138 Reqs._Data Management 0 0 0 0 Reqs._Applicability Matrix 30 30 20 5 TOTAL 759 1038 943,5 537  Following steps: identification of discrepancies/issues, POC data, guidance rules 6 Bruno Chatel (bcha@chadocs.com) June 24 2014
  7. 7. New authoring/publishing environment for an existing program  Same expected value added !  But.. need to manage legacy…. – Re-author….  It is not only a technical issue….  It may impact changes in the content – Take advantage of advanced features – Digital data oriented/data centric approach  It impacts the published manuals  Full Re-Approval of manuals ? 7 Bruno Chatel (bcha@chadocs.com) June 24 2014
  8. 8. Keep an existing authoring/publishing system  And make a final conversion OEM authoring validation approval  It works ! publishing XML/SGML Transformation proprietary data model to ATA 2300 – From SGML monolithic proprietary DTDs – From XML modular proprietary data model  Minor issues – To solve with authoring/publishing system enhancements – Change requests 8 Bruno Chatel (bcha@chadocs.com) June 24 2014
  9. 9. Convert to ATA 2300  Conversions rules – (if applicable) Break monolithic manual/breakdown in PM and DM – Generate Cross Ref Tables DM for applicability declaration – (if applicable) Manage repositories DM (glossary, avionic/dispatch qualifiers, link target) – Manage revision marks and applicability statements (DM and -if applicable-inline applic) – Technical content transformation (translate proprietary structure to ATA 2300 DM content) – Generate Data Management features (Exchange Package Status List, Package Organization, Sub Set if any, TR/TDM, Delivery Scope / revised only / partial)  Issues – Applicability in the PM to propagate at DM level – Identification: PMC/DMC creation (SNS, InfoCode) – Persistent IDs – Applic revision marks – Some applicability computation / declarations – Some issues in matching technical content model : this could come from very different avionics/cockpit design (example: alerting system) 9 Bruno Chatel (bcha@chadocs.com) June 24 2014
  10. 10. And airlines/operators ?  Today only proprietary digital format – Dependant of OEM digital deliveries (when there is) – Or pdf/paper Customization (CMS) - revision impact - authoring -approval - publishing On board/EFB e-Viewer (maybe OEM dependant) On ground consultation tool (Ops manager, Flight crew training…) OEM A XML/SGML Customization (CMS) - revision impact - authoring -approval - publishing On board/EFB e-Viewer (maybe OEM dependant) On ground consultation tool (Ops manager, Flight crew training…) OEM B XML/SGML 10 Bruno Chatel (bcha@chadocs.com) June 24 2014
  11. 11. ATA 2300 ? Why ?  Developing a new CMS – And take advantage of OEM delivery (if any) OEM A XML/SGML OEM B XML/SGML  ATA 2300 Customization (CMS) On board/EFB e-Viewer (maybe OEM dependant) On board/EFB e-Viewer (maybe OEM dependant) - revision impact - authoring -approval - publishing On ground – XML + Provide all the features consultation tool (Ops manager, Flight crew training…)  Business requirements : specific for Flight Ops with 4 major OEM requirements  Fully adapted for eViewer applications – Neutral and standard  Don’t be totally dependent on a specific proprietary format (linked to a solution provider)  Can uncorrelate CMS, e-Viewer, … with different software providers  Insure common data found, share a view for a mixed fleet (consistency)  Allow also to manage “operator manual” 11 Bruno Chatel (bcha@chadocs.com) June 24 2014
  12. 12. How to go….  First case: Wait for ATA 2300 OEM deliveries ! OEM A XML OEM B XML Customization (CMS) - revision impact - authoring -approval - publishing 12 Bruno Chatel (bcha@chadocs.com) June 24 2014
  13. 13. How to go….  But it is also possible to start without OEM delivery – Making conversions from OEM proprietary publishing/exchange digital inputs  What is feasible as a conversion on the OEM side is feasible on the airline side ! – Author what is not delivered OEM A XML OEM B XML Transformation proprietary data model to ATA 2300 Transformation proprietary data model to ATA 2300 Customization (CMS) - revision impact - authoring -approval - publishing 13 Bruno Chatel (bcha@chadocs.com) June 24 2014
  14. 14. CMS to Viewer  Use ATA 2300 as the exchange data model between CMS/Customization and e-Viewer – Opportunity to different software providers – Share common technologies for the whole fleet – Also allow to support Customization “operator manuals” (not related to any specific OEM/Program) (CMS) On board/EFB e-Viewer (maybe OEM dependant) On ground consultation tool (Ops manager, Flight crew training…) – Take advantage of ATA 2300 enhanced features for dynamic eViewer (applicability/filtering, interactive/cascade graphics, tickable procedures, layers, external applications)…. And work in progress for integration eLogBook ? Proprietary data format for OEM EFBs viewers ? • Convert from ATA 2300 ? (to be studied) 14 Bruno Chatel (bcha@chadocs.com) June 24 2014
  15. 15. Implementation of ATA 2300 (CMS, eViewer, …):Technical aspects  Many compliance with S1000d …but is not S1000d – S1000D v4.1 – Data management communalities  Modularity (with separated Status/Content fragments)  (Partially) Identification  Applicability management – Consider using common technical framework !  Very specific (and business oriented) content models – Impacts mostly stylesheet 15 Bruno Chatel (bcha@chadocs.com) June 24 2014
  16. 16. The remaining question is…. WHEN? 16 Bruno Chatel (bcha@chadocs.com) June 24 2014
  17. 17. Thanks ! Bruno Chatel Chadocs bcha@chadocs.com http://www.chadocs.com +33 4 96 11 14 57 17 Bruno Chatel (bcha@chadocs.com) June 24 2014

×