1 / 14

RAFALE implementation

S1000D in PRACTICE. RAFALE implementation. Michel Doméon Dassault-Aviation michel.domeon@dassault-aviation.fr. The AECMA answer. At the beginning of the program (1991), the French MOD expressed the need to have a full electronic documentation available for the Rafale aircraft.

wei
Download Presentation

RAFALE implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. S1000D in PRACTICE RAFALE implementation Michel Doméon Dassault-Aviation michel.domeon@dassault-aviation.fr

  2. The AECMA answer • At the beginning of the program (1991), the French MOD expressed the need to have a full electronic documentation available for the Rafale aircraft. • This concept had to be : • common for all Rafale versions • applicable to the whole aircraft components : aircraft, engine, avionics, armaments and support equipments • long term valid. French MOD and industry decided to apply the AECMA 1000D specification

  3. DM DM DM DM DM DM t Nb Mach Electronic Technical PublicationsRAFALE process Publications Issues managed by French Mod Documentary Data Base managed by French Mod Main Suppliers ... Rafale Mod MBDA Thalès Snecma SID Dassault Aviation IAPS SED Data Modules - Illustrations CTG (AECMA 1000D) Interactive Aircraft Performance Software (IAPS) CTG :Clauses Techniques Génériques SID : Système d'Information Documentaire SED : Système d'Exploitation Documentaire

  4. Rafale documentation • Based on AECMA 1000D standard • Industrial Organization : • Industrials in charge of the source data • Primary contractors deliver to Airforce • (Dassault Aviation, snecma, Thales…) • Forces (dedicated area at Romorantin) in charge of the CSDB and publications for the Air Force, and the Naval aviation • Publication and Consultation system Owned by Airforce • Control, Storage and Publication (SID) • Electronic Consultation System (SED)

  5. Contractual specification • Standard • SGML, CGM, CALS CCITT G4,JPEG, TIFF • DTD : first issue defined in // to 1.7, 1.8 • but already with the inclusion of some features addressed in 1.9/2.0 issues • Hotspots mechanism, • Wiring structures, • Advance applicability structure, • File base transfert • Electronic commenting process • “Specpara” as per issue 2 • …. • Very strict acceptance conditions • Application by specific Rafale doc. Clauses (CTG) • automatic controls and manual verification on demand

  6. DM Types • Crew : check lists, descriptions all performance and configuration data are handled beside the tech pub viewing system • Descript : descriptive information for aircraft, equipments and Support equipments • Proced : procedural information mainly installation/removal • Schedule: maintenance planning information • IPD: directly issued from 2000M data base • Wiring: Specific “Dassault-Aviation” DTD • Air Fault : Air fault reporting branch • TO: Equipment list with their location and function

  7. Interactive performance and calculation Software • Main module functions • Performance calculations • "Configurations" • "Trends" • ADVANTAGES in regard of traditional documentation • Safety and accuracy of results • Complete and fast calculations • Simplicity of use (Windows) • Control of results • Universality : "no customisation" required • Configurations information on_line • with the calculation module. • With the mission preparation/restitution system

  8. Rafale doc. in figure • 56.000 Data Module in the CSDB • 30.000 active DM (last issue number) • All Rafale systems documentation already delivered(aircraft, equipments, and support equipments documentation) • Use operationally on network (Navy air base and Aircraft Carrier) or on stand alone platform • Network based system for multiple software used for the maintenance of the Rafale (Tech pubs, Logistic and Technical Maintenance, Flight Data Analysis...) • Non dedicated computers • free access of the publications (no control by profiles) • specific classified network for the classified publications • use by pilots, mechanism, and training centre

  9. Specificities • Applicability management • strong applicability structure • Multi standard applicability for Dms and multiple use of effectivity from paragraph level to text level • 2000M to 1000D applicability compliance issues • configuration filtering on viewing system(version, standard, pn) • Icn definition at status level only • same as prelreqs mechanism • ICN ref only within dm core • hotspots defined one’s only

  10. Main features • DMC • use of AVEE and AGE • Specific IPC and IPCN DMC structure (fig, fifv elements..) • DMCOPEN anchor tag • defined to point to an unknowned Data module code • the link is resolved on the SID at the publication generation step

  11. Main features • Strong use of IPC links • descriptive information refer directly to IPC data and illustrations when no other specific maintenance illustration is needed • no duplication of illustrations, • updates only on ipd data modules when references are updated • Use of target element for: • aircrew reference to descriptive information • graphic to graphic links • graphical access • wiring diagrams links

  12. Main features • General use of links text --> graphics/hotspots • not only within IPD, but also used in descriptive and procedural DMs • 98 % of illustrations in 2D format (CGM version 1) • directly issued with CATIA from the Rafale 3D mockup • Color used where needed (nearly all maintenance illustrations) • Common crew/ mechanism descriptive data module when applicable

  13. Lessons learned • Electronic documentation needs a new organisation to manage and analyse the updates because of • IPR flow which is very important • the update delivery every 6 months • the necessity to customise the documentation between two updates in order to integrate: • service Bulletin, technical messages or checks • Due to the amount of links between maintenance documentation and IPD, 1000D contracts must be in line (delivery schedule) with 2000M contracts

  14. Lessons learned • Electronic documentation exploitation needs a good internal training (pilots and mechanics) • on the software to know how to find information • on the 1000D standard to know how the documentation is built • Electronic publications set a new way of documentation approval for the staff because of the difficulties: • to control documentation data • to guarantee the exhaustiveness of the documentation • of a new cycle for the update • More than 45 subcontractors to manage with very variable documentation implication • Huge effort of 1000D concept integration training

More Related