Presentation is loading. Please wait.

Presentation is loading. Please wait.

© 2003 TPSMG S1000D Tutorial Compressed introduction to the Spec AIA/Tri-Service 2004 Publications Workshop San Antonio, TX 2004-02-09.

Similar presentations


Presentation on theme: "© 2003 TPSMG S1000D Tutorial Compressed introduction to the Spec AIA/Tri-Service 2004 Publications Workshop San Antonio, TX 2004-02-09."— Presentation transcript:

1 © 2003 TPSMG S1000D Tutorial Compressed introduction to the Spec AIA/Tri-Service 2004 Publications Workshop San Antonio, TX

2 © 2003 TPSMG Mr Dennis Hoyland BA, MBA Chairman Technical Specification Maintenance Group Assistant Director Corporate Technical Services Technical Documentation Defence Logistics Organisation, United Kingdom

3 © 2003 TPSMG Agenda History – Organization - Overview – Future –Dennis/Carl AIA Activities –Denny/Sean/Ryan Overview of publishing –Paul/Tam/Jan S1000D in the digital world –Svante/Peter/Kathy/Ryan Discussion

4 © 2003 TPSMG S1000D Issue 2.0 The vision – The reality The way to a true international tech pubs spec AECMA S1000D - Tutorial San Antonio, TX

5 © 2003 TPSMG The objective of this introduction is to explain who AECMA and AIA are? give a historical flashback to the development history of AECMA Spec 1000D to S1000D describe the international maintenance organization present the –new structure of Issue 2.0 –Some new features of Issue 2.0

6 © 2003 TPSMG Who are AECMA and AIA?

7 © 2003 TPSMG Who is AECMA? AECMA is an organization –The European Association of Aerospace Industries, AECMA, represents the European defense industries in common issues, with the goal of increasing the competitiveness in the sector All EU countries are represented –Belgium, Denmark, UK, Finland, France, Greece, The Netherlands, Ireland, Italy, Luxembourg, Portugal, Spain, Sweden, Germany, Austria, Czech Republic, …. Produces standards and specifications (among other things), eg –Simplified English. Dictionaries and writing rules. –AECMA Specification 2000M for materiel administration –AECMA S1000D for Technical Publications

8 © 2003 TPSMG Who is AIA? AIA is an organization –The Aerospace Industries Association, AIA, represents the US aerospace industries in common issues, with the goal of increasing the competitiveness in the sector. AIA corresponds to AECMA –BIGGER with more employees and operations –Eg Boeing, Lockheed Martin, General Dynamics … Participants in development of standards and specifications (among other things), eg –iSpec2200 (”owned” by ATA) –Simplified English. Dictionaries and writing rules. –AECMA S1000D for Technical Publications

9 © 2003 TPSMG History

10 History 1984 AECMA countries and MoD customers started the development of an international Specification for Technical Publications to harmonise all national and international specs into a "Western" specification based on ATA Spec First release signed by Air commodore RAF, Generalleutnant GAF, Brigadergeneral SwEF, etc 1998 NCMB - Oslo meeting Goal: Develop an internationally supported Roadmap for Interactive Technical Documentation 2000 NATO ITD WG - Bonn meeting

11 © 2003 TPSMG The NATO ITD Interop Task Force

12 © 2003 TPSMG Result form NATO ITD Interoperability Task Force Extract the Best/Complementary components from the above NATO Roadmap S1000D Change 8 MIL-PRF U.S. DoD NATO Roadmap “ITD” IETP “X” Chap #5 Draft XML MIL-HDBK-511 The JIA

13 © 2003 TPSMG Ch9 → Ch 10 → Issue 2/S1000N Anno 2001 S1000D Ch9 CPF MIL-HBK-511 S1000D Ch10 Restructuring 1 Sea Land S1000N Restructuring 2 SGML Mid 2002 Deadline for CPFs Air Issuing of Issue 2 Approval of final drafts Issuing of Change MIL-PRF MIL-PRF-87269

14 © 2003 TPSMG S1000D – The Roadmap Release of Change 2.x May 2003 Issuing of Issue 2 S1000D Ch9 CPF MIL-HBK-511 S1000D Issue 2 Restructuring 1 Sea Land (+GBF) S1000D Change 2.x SGML Air MIL-PRF MIL-PRF Interactivity 1 (Process DM) Interactivity 2 Oct 2003 Release of Issue 2 XML Schema

15 © 2003 TPSMG Organization

16 S1000D Maintenance organization AECMA - CPSC Customer & Product Support Committee TPSMG Tech Pubs Spec Maint Group D Hoyland/C-J Wilén/ Denny Raitz EPWG Electronic Publications WG Svante Ericsson/Peter Zimmermann Land Publ WG (LPWG) P Haslam /T Faleij Sea Publ WG (SPWG) Tom Malloy AIA Product Support Committee S1000D User Forum TPSMG Exec Air Publ WG (APWG) Ferry Berendi Chair Co-chair EU Co-chair US Secr Chair EPWG Chair LPWG Chair SPWG + 2 representatives from each country The “formal” decision forum Meets only “on condition”

17 © 2003 TPSMG AECMA - CPSC Customer & Product Support Committee TPSMG Tech Pubs Spec Maint Group D Hoyland/C-J Wilén/ Denny Raitz EPWG Electronic Publications WG Svante Ericsson/Peter Zimmermann Land Publ WG (LPWG) P Haslam /T Faleij Sea Publ WG (SPWG) Tom Malloy AIA Product Support Committee S1000D User Forum TPSMG Exec Air Publ WG (APWG) Ferry Berendi TPSMG Chair Co-chair EU Co-chair US Secr Chair EPWG Chair LPWG Chair SPWG Germany ind France ind Italy ind UK MoD USA DoD The common working forum - The decision forum Meets regularly 3-5/year (Europe/US) S1000D Maintenance organization

18 © 2003 TPSMG AECMA - CPSC Customer & Product Support Committee TPSMG Tech Pubs Spec Maint Group D Hoyland/C-J Wilén/ Denny Raitz EPWG Electronic Publications WG Svante Ericsson/Peter Zimmermann Land Publ WG (LPWG) P Haslam /T Faleij Sea Publ WG (SPWG) Tom Malloy AIA Product Support Committee S1000D User Forum TPSMG Exec Air Publ WG (APWG) Ferry Berendi Customers and Vendors Arranged by TPSMG Exec Bi- annual Fall mtg – Europe Spring mtg - US S1000D Maintenance organization

19 © 2003 TPSMG AECMA - CPSC Customer & Product Support Committee TPSMG Tech Pubs Spec Maint Group D Hoyland/C-J Wilén/ Denny Raitz EPWG Electronic Publications WG Svante Ericsson/Peter Zimmermann Land Publ WG (LPWG) P Haslam /T Faleij Sea Publ WG (SPWG) Tom Malloy AIA Product Support Committee S1000D User Forum TPSMG Exec Air Publ WG (APWG) Ferry Berendi Chair and co-chair appointed by TPSMG Exec + workers appointed by the chair/co-chairs Chair (and co-chair) appointed by TPSMG Exec + workers appointed by the chair/co-chairs S1000D Maintenance organization

20 © 2003 TPSMG National supporting organization AECMA - CPSC Customer & Product Support Committee TPSMG Tech Pubs Spec Maint Group EPWG Electronic Publications WG Land Publ WG (LPWG) Sea Publ WG (SPWG) AIA Product Support Committee S1000D User Forum TPSMG Exec Air Publ WG (APWG) National representative/TPSMG Ver Ver National EPWG Electronic Publications WG National Land Publ WG National Sea Publ WG National Air Publ WG

21 © 2003 TPSMG Note to Dennis: The flags at the bottom are: South Africa, Norway, Hungary and The Netherlands

22 © 2003 TPSMG Some basic definitions …

23 © 2003 TPSMG Basic concepts Data module –A stand alone information unit comprising descriptive, procedural, operational data for a Materiel or a component thereof –The unit is produced in such a form that it could be stored and retrieved from a Common Source DataBase by the data module code as the identifier –Produced in SGML/XML according to specific DTDs CSDB (Common Source DataBase) –A store for the data modules and publications DMC (Data Module Code) –A 17- alt 37-charchter code to identify a data module and to facilitate storing and retrieving them from a CSDB ICN (Illustration Control Number) –A 27- alt 45-charchter code to identify an illustration and to facilitate storing and retrieving them from a CSDB Applicability/Effectivity –Defines to which version/mark/serial number of the Materiel the data module is written/The published subset of “applicability”

24 © 2003 TPSMG Restructuring Started in 1998

25 © 2003 TPSMG Four and a half years later More than 100 CPFs has been generated, discussed, analysed, dissected, … … and some rejected 70+ CPFs has been accepted and included The Spec has become a tri-service spec incl Land, Sea, Air Materiel The spec has been completely restructured Change 9 has become Issue 2

26 © 2003 TPSMG Co-Chair Technical Specification Maintenance Group Technical Fellow Informatics Saab Aerosystems Sweden Mr Carl Wilén M Sc

27 © 2003 TPSMG Structure of S1000D

28 © 2003 TPSMG Issue 2 Three becomes one Change 9 The Materiel

29 © 2003 TPSMG Chapter 1Chapter 2Chapter 3 Restructuring – From five to nine chapters Issue 2 Chapter 4 Chapter 5Chapter 6Chapter 7Chapter 8Chapter 9

30 © 2003 TPSMG Chapter 4 Information management Issue 2 Chapter 1 Introduction Chapter 2 Documentation process Chapter 3 Information generation Chapter 5 Information and publication sets Chapter 6 Information presentation/use

31 © 2003 TPSMG Chapter 7 Information processing Issue 2 Chapter 8 Standard Numbering System (SNS) and information codes Chapter 9 Terms - Data dictionary

32 © 2003 TPSMG What’s new?

33 © 2003 TPSMG Chapter 1 Introduction 1.1Purpose 1.2Scope 1.3 How to use this specification 1.4 How to tailor for a specific project 1.5 Request for change Issue 2

34 © 2003 TPSMG Chapter 2 Documentation process 2.1Overview 2.2Use of standards 2.3 Relations to other processes and standards Process diagram referencing S1000D chapters Issue 2

35 © 2003 TPSMG Chapter 3 Information generation 3.1Introduction 3.2Data modules 3.3 Information sets 3.4 Zoning and access 3.5 Updating of data modules 3.6 Security and data restrictions 3.7Quality assurance 3.8Disassembly principles 3.9 Authoring (incl Process modules) Issue 2

36 © 2003 TPSMG Illustration rules - Jointly with AIA/ATA - ATA iSpec2200 rules are accepted - Color - More illustration sizes Chapter 3 Information generation Author and illustrator support: In depth information Project decisions listed Guidance, examples and mark-up examples are added

37 © 2003 TPSMG Improved configuration control and security coding Process data module - a procedural flow script The first step towards full interactivity in standardized form Provides for additional functionality without impacting existing legacy data Chapter 3 Information generation

38 © 2003 TPSMG Process data module Chapter 3 Information generation Process Data module DM-Alts If-DM DMNode DMNod DMNode Data module Data module Data module Data module Data module

39 © 2003 TPSMG Wiring DTD - - New data module type and wiring DTD - - Takes wiring data from engineering into DMs and further to IETP Chapter 3 Information generation

40 © 2003 TPSMG Chapter 4 Information management 4.1Introduction 4.2CSDB 4.3Data module code - DMC 4.4Illustration control number – ICN 4.5Data module lists 4.6Commenting 4.7Version control of data modules 4.8Interchange of data modules 4.9Publication management Issue 2

41 © 2003 TPSMG Ml BATTLETANK1234 -Y-040Y SNS IC/ICV ILC -YYYY SDC DC/DCV Y-Y-04YYY New data module code – DMC An extended, more flexible, numbering system for data module codes Chapter 4 Information management

42 © 2003 TPSMG Commenting - an SGML form for commenting and reporting - on data modules or publication modules - during the verification process and the in-service Chapter 4 Information management

43 © 2003 TPSMG New concept for CSDB Publication module (PM) and Publication Module Code (PMC) has been added to control configuration of IETP content Chapter 4 Information management

44 © 2003 TPSMG Chapter 5 Information sets and Publications 5.1General 5.2Information sets 5.2.1Common information sets 5.2.2Air specific information sets 5.2.3Land/Sea specific information sets 5.3Publications 5.3.1Common requirements 5.3.2Air specific publications 5.3.3Land/Sea specific publications Issue 2

45 © 2003 TPSMG Information set An “information set“ is the definition of scope and depth of the information required, and is listed in the DMRL. (Author’s view). Publication A group of DMs sensibly for the end user defined by a publication module. (User’s view). Chapter 5 Information and publication sets

46 © 2003 TPSMG Chapter 6 Information presentation/use 6.1Introduction 6.2Page-oriented publications 6.3Interactive Electronic Technical Publications – IETP 6.4Functionality Issue 2

47 © 2003 TPSMG Chapter 6 Information presentation/use IETP A non-linear presentation of the data module in an user- interactive manner Page-oriented publication A linear presentation of the data modules either on paper or screen

48 © 2003 TPSMG Introduced XML-oriented IETP (IETP-X) included Removal of - IETP-L (linearly structured SGML publications) - IETP-D (database-oriented SGML/HyTime publications) - IETP-H (linearly structured HTML publications) - IETP-I (integrated processes) Chapter 6.3 Interactive Electronic Technical Publications – IETP

49 © 2003 TPSMG Chap 6.3.1IETP – Look and feel Chap 6.3.2IETP – Output specification Chap 6.3.3IETP – User interface functionality Chapter 6.3 Interactive Electronic Technical Publications – IETP Not yet in the Spec

50 © 2003 TPSMG Chap IETP – Look and feel Introduced - -Common look and feel concept Purpose - -To establish minimum common requirements for the look and feel (style) of IETP. Background - -US AIA/DoD Tri-Service initiative to create a common IETM “Look and feel” document Based on - -Based on Mil Hbk 511 and other national requirements Chapter IETP – Look and Feel

51 © 2003 TPSMG Purpose - -To provide basic rules an guidance for styling of elements for display - -To provide basic rules an guidance for printing output of IETP Chapter IETP – Output Specification Chap IETP – Output specification

52 © 2003 TPSMG Purpose - -To provide general rules for implementation of standard functionality for the user interface of IETP Chapter IETP – User Interface Functionality To be used in conjunction with Chap 6.4 Chap IETP – User interface functionality

53 © 2003 TPSMG Chapter 6.4 Information Presentation/Use - Functionality Functionality matrix for deliverables Chap 6.4.1Functionality - Background and explanation Chap 6.4.2Functionality - Functionality matrix Chap 6.4.3Functionality - Acquisition management Chap Not yet in the Spec

54 © 2003 TPSMG Purpose - Created to rid the industry of the “unofficial” IETM/IETP Classes I - V Background - - Revamped by AIA to update to current capabilities (technologies) - Adopted by AECMA as “Apples to Apples” comparison tool Chapter 6.4 Functionality Chap Functionality - Background and explanation Introduced - -IETP Functionality matrix

55 © 2003 TPSMG Chapter Functionality – Background and Explanation Content - Contains the “How to use”, Category definitions, and Functionality definitions Chap 6.4.2Functionality - Functionality matrix Introduced - -How to use the matrix chapter

56 © 2003 TPSMG Chapter Functionality – Acquisition Management Purpose - -To provide information and guidance on the acquisition of IETP (including lessons learned from fielded systems) Chap Functionality - Acquisition management To be supplied in a later change - -IETP Acquisition Management

57 © 2003 TPSMG Chapter 7 Information processing 7.1Introduction 7.2 Basic concepts 7.3CSDB objects 7.4Generation of publications 7.5Information interchange 7.6Software requirements 7.7Guidance and examples Issue 2

58 © 2003 TPSMG Attribute values - flexibility - using configuration files XML Schema - Now introduced for data modules (in parallel with SGML DM DTD) Chapter 7 Information processing

59 © 2003 TPSMG Chapter 8 Standard Numbering System (SNS) and information codes 8.1Introduction 8.2Maintained SNS 8.3Example SNS 8.4Information codes 8.5Summary Maintained SNS: 8, eg General surface vehicles General communications Air vehicle, engines and equipment Example SNS: 18, eg Combat vehicle project Mil Std 1808 based project Issue 2

60 © 2003 TPSMG Chapter 9 Terms - Data dictionary 9.1Introduction 9.2Glossary of terms 9.3Data dictionary Data dictionary Links to databases (downloadable) for definitions of all elements and attribute for SGML DTD XML Schemata Issue 2

61 © 2003 TPSMG S1000D Issue 2.0 International Specification for Technical Publications utilising a Common Source DataBase AECMA - AIA The European Association of Aerospace Industries Aerospace Industries of America Issue Now free on the web

62 © 2003 TPSMG Mr Dennis Hoyland

63 © 2003 TPSMG Future – Issue 2.1/2.2/2.3 What did we “miss” in Issue 2? New stuff

64 © 2003 TPSMG Issue 2.x Remaining CPFs –50+ to discuss, analyze, … … and some to be rejected Starter Tool kit - The Bike –Will include 45+ DMs and PMs, DDN, DMRL, … –Both SGML/XML instances and output examples –FOSIs, Style sheets XSL/CSS –Conversion script Change 6, 7, 8 or 9 to Issue 2.0 (The Sledgehammer)

65 © 2003 TPSMG Starter Tool kit - The Bike Bicycle data modules –Descriptive –Procedural –Illustarted parts data –Fault isolation –Crew/Operator –Schedules (Maintenance planning) –Wiring –Process data module

66 © 2003 TPSMG Starter Tool kit - The Bike Exchange –Data Module List - DML –Data Dispatch Note - DDN –Publication Module - PM Illustrations –Computer Grahics Metafile (CGM) –Raster

67 © 2003 TPSMG Starter Tool kit - The Bike Scripts (for IETP-X neutral format) –SGML to XML conversion –URL/URN Resolution –XLink attributes –RDF/DC Meta data

68 © 2003 TPSMG Starter Tool kit - The Bike Software –The Sledgehammer Change 1.6 Change 1.7 Change 1.8 Change Change 1.9 Change 2.0 Change 2.x Converter Converts any S1000D version change to any other (both ways)

69 © 2003 TPSMG Starter Tool kit - The Bike Output –XSL Stylesheets –CSS –PDF examples for all data module types –FOSI Framemaker (?!) Epic (?!) –A free basic functionality viewer (?!)

70 © 2003 TPSMG Issue 2.x The remaining chapters: Chap xPage-oriented presentation – Layout examples Chap 6.3.1IETP – Look and feel Chap 6.3.2IETP – Output specification Chap 6.3.3IETP – User interface functionality Chap 6.4.3Acquisition management

71 © 2003 TPSMG Issue 2.x Multimedia formats –audio, video, 3D, Virtual Reality, … Completion of Interactivity and diagnostics interface –An extended Process data module or –A new Interactive data module Common ATA / AECMA / AIA SVG profile Applicability / Effectivity improvements Include new DM type “DACR” (Damage Assessment, Control and Repair)

72 © 2003 TPSMG Issue 2.x Exchange mechanism for project attribute configuration files ADL/SCORM linkage (MoU in development) PLCS/STEP linkage (MoU in place) Close up of procedures – New model

73 © 2003 TPSMG Issue 2.x New CPFs New CPF procedure and more … …

74 © 2003 TPSMG On the web mid April May 2003 Issuing of Issue 2.0 S1000D Issue 2 Oct 2003 Release of Issue 2.0 S1000D – The Roadmap 2003 and onwards S1000D Change 2.1 Cleaning Feb 2004 Release of Change 2.1 S1000D Change 2.2 Nov 04 Release of Change 2.2 New features Mid/Late 2005 Release of Change 2.3 S1000D Change 2.3 Major change

75 © 2003 TPSMG Questions!? Thanks for your attention!

76 © 2003 TPSMG Mr Denny Raitz Associate Technical Fellow – Technical Data Co-Chair Technical Specification Maintenance Group And AIA Representative

77 © 2003 TPSMG AIA Publications Overview Last Two Year’s Accomplishments Current/Ongoing Activities Future Plans –2004 Goals and Objectives

78 © 2003 TPSMG Accomplishments Tri-Services Support –Dec. ’03 – First S1000D Tutorial to US DoD (NAVSEA) –Sept. ’03 – S1000D Published –May ’03 – S1000D Issue 2.0 Released –Feb ’03 – S1000D & Functionality Matrix Update, IETM Subject Matter Expert Meeting, Huntsville –Jan ’03 – “Look & Feel” Requirements Meeting, Tri-Service Technology Working Group, Tyson

79 © 2003 TPSMG Accomplishments – Cont’d Functionality Matrix Support –May ’03 – AECMA Technical Publications Specification Maintenance Group (TPSMG) Meeting, Clearwater –Feb ’03 – S1000D “Emergency” Look and Feel Meeting (Change 10), Washington D.C. –Nov ’02 – S1000D Update, TPSMG Exec. 8 th Meeting, Washington D.C. –Oct ’02 – AIA Fall Conference (MOU, Workshops, Demos), Williamsburg –May ’02 – S1000D Update, TPSMG Meeting, Saint Louis

80 © 2003 TPSMG Accomplishments – Cont’d December 2003 Tyson ’ s Corner, VA (Tutorial) October 2003 Poitier, FR (1 st User ’ s Forum) June Munich, GE May 2003 Clearwater, FL January 2003 Turin, Italy December 2002 Tyson ’ s Corner, VA November,2002 Wash, DC November, 2002 Glasgow, UK October 2002 Williamsburg, VA September 2002 Berlin, GE September 2002 Bordeaux, FR June 2002 Washington, DC May 2002 St. Louis, MO S1000D (Meetings)

81 © 2003 TPSMG Accomplishments – Cont’d Resulting In Issue 2 Impact: –12 Change Proposals with Technical Solutions Submitted and Excepted –Functionality Matrix Incorporated Issue 2.X –Training Incorporation –Diagnostics –Look and Feel Finalization

82 © 2003 TPSMG Accomplishments – Cont’d Since 2000: AIA Provided Approximately 450 Work-Weeks of Labor and 120 Trips of Domestic/International Travel

83 © 2003 TPSMG On-Going Activities Tri-Service Support –Will Continue to Provide Technical Expertise Upon Request –Will Continue to Serve as Interface for S1000D Development S1000D Development –US-TPSMG –US-EPWG –Change Proposal Forms DoD/ADL/AECMA/AIA MOU –To Incorporate Training Requirements Into S1000D Functionality Matrix Updates Look and Feel Finalized Multimedia and Other Graphic Format Investigations

84 © 2003 TPSMG Overview of Publishing Tam Malloy Chair EU Sea WG Paul Haslam Chair EU Land WG Jan Roberson Co-Chair US TPSMG

85 © 2003 TPSMG Areas to be Covered This session covers how information will be: –generated –exchanged and –output We are also going to attempt to answer some of the questions raised through our last workshop We want it to be relaxed and we want to generate discussion

86 © 2003 TPSMG Questions What is done with business rules and any associated documents that support them, like program specific data module selections? And how are those put together so the same kind of manual is generated each time the author starts one? The UK MOD has a standard to tell them how to do this, but the rules documents are not available, as far as I could find. I know we have an idea of what this all means, but a practical example would be helpful. Go over examples of business rules. Explain how business rules are generated and maintained. Explain issues with integrating data modules developed by various vendors (explain how data modules for components can be built independently and lessons learned in the integration process). How are the Data Module contents related/linked to weapon system configuration?

87 © 2003 TPSMG Generation S1000D provides –Data Module Structure Coding –Business Rules –Information Sets Specific Example

88 © 2003 TPSMG One of All of IDSTATUS CONTENT Meta data about the data module What the user sees Issue details DM Address Security Applicability QA Status Descriptive Procedural Fault Crew IPD Schedules Data Module ProcessWiring The Data Module Every data module has this

89 © 2003 TPSMG Applicability

90 © 2003 TPSMG Applicability Part of this allows us to “link” the data contained within the content element to the physical The element could be used to “tie” the content to a specific configuration, build status, etc Notice this links to last question-How are the Data Module contents related/linked to weapon system configuration?

91 © 2003 TPSMG Security Security – Data Restrictions Information Copyright Security Policy Reference Special conditions Instructions Distribution Handling Destruction Disclosure

92 © 2003 TPSMG Data Module Code Model Ident Data Module System Difference SNSDCDCVICICVILC Issue Details Data Module Address IDSTATUS The Data Module

93 © 2003 TPSMG All of IDSTATUS Issue details DM Address Security Applicability QA Status One of CONTENT Descriptive Procedural Fault Crew IPD Schedules ProcessWiring CSDB Data Module Data Module Data Module Data Module Data Module Common Source Database (CSDB)

94 © 2003 TPSMG Item Location Code Info Code Variant Info Code Dis Code Variant Dis Code SubjectSubsectSectionChapnum System Diff Code Modelic Identify the project (No change to pre-issue 2) Variable length between 2 and 14 (inclusive) alpha-numeric characters First 10 can give the project name and can be drawn from the End Item Acronym Code of a b or based LSAR Last 4 can give the equivalent of the End Item Usable On Code (3 characters from b based LSAR and 4 characters from based Identifies differences in the function of a system (No change to pre-issue 2) Variable length between 1 and 4 (inclusive) alpha-numeric characters Eg Can be used as a single character entry in the same way as pre-Issue 2 or 3 characters to capture SLUOC from b based LSAR or 4 characters to capture UOC from Issue 2 DMC Issue 2 Data Module Code First part of the Standard Numbering System (SNS) Now can carry the Material Item Category Code, as defined in Def Stan Variable length at either 2 or 3 alpha-numeric characters Third part of the SNS Fixed length at 1 alpha- numeric character Fourth part of the SNS Variable length at either 2 or 4 alpha- numeric characters 4 characters can be used to cater for large number of LRUs on bigger projects Second part of the SNS Fixed length at 1 alpha- numeric character Disassembly Code No change in function from pre- Issue 2 Fixed length at 2 alpha-numeric characters Disassembly Code Variant Same basic function as pre-Issue 2 Variable length at 1, 2 or 3 alpha-numeric characters Eg 1 characters for use as in pre-Issue 2, 2 characters to capture the ALC from b based LSAR and 3 characters to capture the Alternate Indenture Product Code from Information Code No functional change from pre-Issue 2 Fixed length at 3 alpha-numeric characters with special rules as below: XXX as currently defined XXY Not given (project defined) XYY NOTGIVEN (Projects to apply to TPSMG via CPF for allocations) YYY NOTGIVEN (Projects to apply to TPSMG via CPF for allocations) Information Code Variant No functional change from pre-Issue 2 Fixed length at 1 alpha-numeric character Item Location Code No functional change from pre- Issue 2 Fixed length at 1 alpha-numeric character Same structure as pre- Issue 2, therefore maintains backward compatibility

95 © 2003 TPSMG Implementation Allocate project name as pre-Issue 2 and register with NAMSA Allocate SDC as pre-Issue 2 but can use for example the UOC Optionally use a MICC to allow multiple SNS types Model Ident System Difference SNSDCDCVICICVILC

96 © 2003 TPSMG Implementation Allocate SNS as pre-Issue 2 but –8 SNS‘s that are maintained by TPSMG by CPF –17 example SNS‘s not maintained –If none fit – write your own! Allocate disassembly under the rules for disassembly as pre-Issue 2 Model Ident System Difference SNSDCDCVICICVILC

97 © 2003 TPSMG Implementation Allocate Disassembly Code Variant as pre-Iss 2 but you can populate it with the ALC or AIPC Allocate Information Codes as pre-Iss 2 but with more scope Allocate Information Code Variant as pre-Iss 2 Allocate Item Location Code as pre-Iss 2 Model Ident System Difference SNSDCDCVICICVILC

98 © 2003 TPSMG Data Module IDSTATUS DM Address Issue Details Security Applicability QA Status Content Procedure Basic Structure Interoperability

99 © 2003 TPSMG Integration Issues Integration is only a problem if you do not solve it at initial program stages Traditionally S1000D has not dealt with this aspect, however! Lessons learned from implementation require: –A project infrastructure be created –The next section deals with this

100 © 2003 TPSMG Management – Program Needs S1000D deals with data generically Requirement still exists to establish program constraints Dictated by documents detailed within program: –TDMP –DMP DMRL Business Rules Illustration guide

101 © 2003 TPSMG Document Management Plan Detailed plan covering –Scope of Technical Documentation –Coding, Generation and Storage –Data Module Requirements List (DMRL) –Publishing and Distribution –Amendment Process –Programme Management, Quality, Security –Risk Management

102 © 2003 TPSMG Document Management Plan High level plan detailing documentation requirements for the project –Covers Scope of documentation Security QA Programme Standards

103 © 2003 TPSMG Scope of Technical Publications Covers the type of information required and its scope and depth –Corrective maintenance –Logical, concise, step-by-step procedures shall be produced for tasks detailed in the LSAR. Corrective maintenance includes repair, alignment and adjustment. Repair procedures are to contain instructions for removing, replacing and re-assembling defective equipment. Special procedures for removing, replacing and testing PROMs and similar devices are to be detailed. Where the maintenance procedures require several data modules at a given SNS, then the ICV is to be used commencing with alphanumeric characters 1 – 9 then A onwards. The IC 282 shall not be used on ASTUTE

104 © 2003 TPSMG DMRL What is a DMRL –A Data Module Requirements List identifies all data modules required for a given program –It can detail links to source data (eg LSAR) –It is recommended

105 © 2003 TPSMG DMRL (cont) The DMRL includes: –The elements of the IDSTATUS section required within it and their definitions –Uses the SNS and Information Codes as its prime reference

106 © 2003 TPSMG In the S1000D Context S1000D contains rules in the specification and its DTD/Schema However, –Areas of the specification are open to interpretation by projects –The content of elements may be decided by projects –There is more than one way to mark-up information using the DTD/Schema

107 © 2003 TPSMG Business Rules Business rules are required to: –Provide help, interpretation and guidance in using S1000D –Remove ambiguity in the specification by giving examples –Ensure consistency in CSDB deliverables –Highlight to projects where decisions need to be made

108 © 2003 TPSMG Business Rules Each project may need to define its own project specific Business Rules which will cover: –The population of the content of mandatory elements –How to tailor the content and usage of elements Element level Attribute level

109 © 2003 TPSMG Business Rules Essential in: –Managing customer requirements –Collaborative projects –Providing a requirement to suppliers –Avoiding re-work or disputes

110 © 2003 TPSMG Business Rules IDSTATUS Elements: Detail how to use the address and status section and relate the rules to the DTD eg: –DMC, how to construct and how to mark-up –Relationship between DMC and DMTITLE –Issue Date –Language, etc

111 © 2003 TPSMG Business Rules The element is mandatory for the Type 45. The element comprises technical name element and information name element. The title gives the meaning to the SNS and information code elements of the DMC. To ensure the data modules are generated in a standardised manner, the following rules apply: The is related to the item identifier, detailed in the Terminology database (Reference 6) and contained within the elements,, and in the DMC. In this example AE indicates “Internal Telephones”. The is the short definition of the element in the DMC. In this example, “520” indicates “Remove Procedures”. Data module titles are to be entered in Title Case (e.g. “Internal Telephones” rather than “Internal telephones”). Markup example: Internal Telephones Remove Procedures Example:

112 © 2003 TPSMG Business Rules Content Section Mark-up Rules for all data module types –Required conditions –Rules completion of procedural data module, including mark up –Rules for Descriptive, including rules for primary paragraphs, sub paragraphs etc. –Rules on use illustrations, tables, lists etc

113 © 2003 TPSMG Partner company business rules Business Rules Project Business Rules S1000D Business Rules The AECMA business rules are at the core. Eg for RPC record the NCAGE Project Business Rules: The responsible partner company shall identify itself by: Use of its NCAGE. Company A = K9999. Company B U5647 Company C = D3432 Partner Company Business Rules Responsible Partner Company shall contain the company NCAGE

114 © 2003 TPSMG Business Rules Summary They are required and projects need to recognise this Issue 2 contains many examples where projects can make a choice Other choices will be project specific Business rules are essential for success Example Business Rules will be available for Bike Test Pack

115 © 2003 TPSMG Business Rules Summary (cont’d) Agreed between parties and recorded –Guide to the different types of data modules and explanation of their purpose –Covers optional elements –Records population and content of elements –Details the use of specific values in the configuration file (Svante to explain) –Relates the rules in the specification to the construct of the DTD/Schema –Contains Authoring guide

116 © 2003 TPSMG Info Set/Publication An Information Set defines the scope and depth to meet the requirement (author view) A publication is the compilation and publishing of information for a customer (customer view) –Note that a publication can be a subset of or equal to an info set, but it may also be a superset of several info sets or parts of them

117 © 2003 TPSMG Generic Set S1000D information sets were reviewed by each of the working groups and a generic set was agreed that could be used by all three environments

118 © 2003 TPSMG Generic Info Sets Crew/Operator information Description and Operation Maintenance Information Wiring diagram data Illustrated parts Data Maintenance Planning Mass and Balance Recovery Equipment Weapon loading Cargo loading Stores loading Role change Battle damage repair Illustrated tool and support equipment Service bulletins Material data Common information and data

119 © 2003 TPSMG Specific Info Sets for Land and Sea Crew/operator descriptive information Crew/ operator operation Crew/ operator sequential operation Crew/ operator fault detection, isolation and resolution International, national and regulatory scheduled

120 © 2003 TPSMG Crew/Operator Operation Information Land/sea Materiel operation Operation (physical breakdown orientated) Operation (functional breakdown orientated) Land/sea Materiel operating data Operating under special conditions Heat conditions Cold conditions Dust conditions Recovery or tow away Crossing of stretch water NBC conditions In case of fire at the land/sea Materiel Make unserviceable or destruction of the land/sea materiel Emergency procedures Transportation Equipment stowing What does an Information Set look like?

121 © 2003 TPSMG Information Sets Operation (physical breakdown orientated) The operation data modules shall include all descriptions necessary to perform the operation of Materiel to put into operation, to operate during use or to turn off the defined Materiel. The operation description shall be created as a step by step structure. It shall also include all preliminary requirements as a description or as a reference to the related data modules. Safety conditions and – instructions must be included inside the data modules or inserted as a reference to the related data modules. Data modules shall be coded YY-A-YY-YY-YY-YXA-XXXA-A, where value for IC shall be 111, 112, 121, 131, 141 or 151 Note that this is a 17 character code and is not a mandatory length This defines the scope of the required information This is how that information is coded on data modules What information is presented in an information set?

122 © 2003 TPSMG Publications List of Applicable Publications User Reference Guide (or Operator’s handbook) –Crew/operator information – Description –Crew/operator information – Operation –Crew/operator information – Sequential operation –Crew/operator information – Fault detection, isolation and resolution –Crew/operator information – National checks –Crew/operator information - Maintenance Mass and Balance Maintenance –Description –Maintenance procedures –Check lists –Work cards –Fault detection, isolation and resolution –Schematic diagrams –Wiring data –Cross servicing –Structure repair –Non-destructive testing –Corrosion control –Illustrated parts data –Illustrated tools and equipment –Battle damage repair

123 © 2003 TPSMG Publications Maintenance planning –Maintenance requirements –Check lists – Work cards Loading and storage –Cargo loading –Weapon loading –Stores loading –Storage Operation –Operation –Role change –Recovery Material data –Material data sheets –List of consumables/expendables Service bulletins

124 © 2003 TPSMG Exchange S1000D used to provide the Mil Std 1840 profile This process has been replaced: –The transfer “file type” has to be agreed within the project, and can include: –GZIP, ZIP, TAR, etc

125 © 2003 TPSMG Exchange Several types of packages can be transferred within S1000D, however each must have –A Data Dispatch Note (DDN) and at least one of the following: One or more data modules and associated illustrations One CSDB Status List (CSL) One Data Module Requirement List (DMRL) One or more Comment forms (COM) One or more Publication Modules (PM)

126 © 2003 TPSMG Exchange What S1000D mandates is the contained file types and naming conventions Example –Data dispatch note (DDN) –CONTROLNUMBER is the data dispatch note identifier in the form: –MI-SSSSS-RRRRR-XXXX-NN_III-WW –MI = model identifier –SSSSS = NCAGE code of sending Agency or Partner Company (A/PC) –RRRRR = NCAGE code of receiving A/PC –XXXX = Year (eg 1999, 2001) –NN = Unique sequential hex interchange number per year starting with value "00" –III = Issue number –WW = inwork number –DDN-AE-C0419-K _ SGM

127 © 2003 TPSMG Output S1000D has two output mediums: –Page Oriented –IETP (IETD,ITD,IETM etc) –This is probably the area that will have the most significant input from the US and is currently being developed

128 © 2003 TPSMG Output - Page Oriented Page oriented within the specification is detailed in various areas and covers: –Rules for the page layout of standard and oversize pages –Rules for headers and footers are detailed together with basic rules for paper publications –Rules for all layout elements used to present the SGML/XML information in the data modules to the S1000D standard –Formatted Output Specification Instances (FOSI), XML Style Sheets (written in the XML Style Sheet Language) or cascading style sheets –Examples of S1000D standard presentations of front matter, descriptive, procedural, etc

129 © 2003 TPSMG Output - IETP S1000D will provide details of presentation and use, however this is under development Various browsers will be shown at the AIA Technology Demonstration and some of these will reflect the S1000D constructs

130 © 2003 TPSMG IETP Navigation There are many methods of IETP navigation currently available. These include but are not limited to: –Table of Contents –Graphical

131 © 2003 TPSMG IETP Navigation (TOC) A breakdown of the equipment based on the system structure – Main Equipment System Level – Sub System Level » etc.

132 © 2003 TPSMG IETP Navigation (Graphical) A sequence of figures linked to provide a ‘drill-down’ provides rapid access to data –Rapid access to required data –At each level of drill-down access to Descriptive, Maintenance, Fault Diagnosis and Parts list information may be given by buttons

133 © 2003 TPSMG Simplified Viewer Graphical User Interface (GUI) Interface is clean and simple Buttons provided on tool bar for advanced functions Menu options also provided

134 © 2003 TPSMG Navigation S1000D will define: –Use of Windows –The control pane –Data pane templates –Typographic guidelines –Display of tables –Display of warnings cautions and notes –Display of animation and video –Display of links –Use of colour, etc

135 © 2003 TPSMG Navigation The minimum functional Navigation aids are as follows: The minimum functional Navigation aids are as follows: –Frame forward / backward / return to start –Search (simple search) - To start of module only to avoid possible oversight of Warnings, Cautions or other safety related information –Mark (with a bookmark) –Retrace (list of previous steps)

136 © 2003 TPSMG Output – The Future The following issues are under development: The following issues are under development: –Look and Feel –Navigation –Functionality

137 © 2003 TPSMG Overview of Publishing Summary The following issues have been covered: The following issues have been covered: –The generation of data modules –The exchange of information –Output

138 © 2003 TPSMG Questions

139 © 2003 TPSMG S1000D in a digital world Svante Ericsson, Chairman EPWG Sörman I&M, Sweden

140 © 2003 TPSMG Session agenda Technical concepts, entities and techniques (Svante Ericsson, SI&M) S1000D, XML and the web (Peter Zimmermann, EADS) S1000D data distribution strategy in perspective (Kathy Rainbolt, US AF) S1000D relation to PLCS and Scorm (Ryan Augsburger, CDG) What will happen next? (Svante Ericsson)

141 © 2003 TPSMG Concepts, entities and techniques The Digital Data objects Data modules, publication modules, data dispatch notes, comments, data module lists (illustrations) The Common Source Database (CSDB) Legacy data Tailoring

142 © 2003 TPSMG The Data Module From the very beginning S1000D has provided a standard way for represen- tation of technical publications in a digital format – –Marked-up using SGML – –A number of DTDs for various types of data modules – –Marked-up using XML

143 © 2003 TPSMG The Data Module (contd) Consists of a number of files –a text file Doesn’t contain any layout information – –a number of illustration files Contains its meta data – –identification – –status This is the content section of a data module. It contains all the factual information in one specific respect, applying to a certain materiel item …….. content id & status

144 © 2003 TPSMG The Publication Module Provides a method to collect data modules into publications Hierarchical structures Configurations By referencing A marked-up file (SGML/XML)

145 © 2003 TPSMG The Data Dispatch Note Contains a list of the data objects included in the transfer Mandatory part of an S1000D information interchange A marked-up file (SGML/XML)

146 © 2003 TPSMG The Data Module List Used to identify required data modules in a project (DMRL) Used to identify status about data modules in a project (CSL) A marked-up file (SGML/XML)

147 © 2003 TPSMG The Comment Used to submit comments between parties in a project Question, preliminary and final answer A marked-up file (SGML/XML)

148 © 2003 TPSMG The Illustration Can be in one of the formats –CGM, CALS raster, TIFF, PNG, JPEG, GIF, PDF Can contain hotspots (CGM) S1000D tries to follow ATA iSpec 2200

149 © 2003 TPSMG The CSDB Is a storage for the various digital objects, in particular the Data Modules incl. their illustrations Can be implemented in any thinkable way –It doesn’t have to be a DBMS –It can be any proprietary file system –Usually it is some sort of document administration tool

150 © 2003 TPSMG Legacy data There are a couple of ways of addressing legacy data in accordance with S1000D: –Conversion – –Encapsulation in a data module (as an “illustration”) – –Contained in an publication (referenced by a Publication Module)

151 © 2003 TPSMG Tailoring of S1000D An implementation of S1000D can be tailored in many respects – –Either of SGML or XML – –Implement a subset of DTDs/Schemas – –Implement a subset of a certain DTD/Schema (!) – –Apply a subset of attribute values (project.cfg)

152 © 2003 TPSMG Apart from the specification chapters: DTD/Schema packages for SGML/XML (downloadable) Data dictionaries for all DTDs and Schemas – on-line and downloadable More to come ….

153 © 2003 TPSMG Thank you!

154 © 2003 TPSMG

155 S1000D – XML – The Web S1000D Tutorial San Antonio, TX, USA Peter Zimmermann (EADS Germany)

156 © 2003 TPSMG Transition to XML First step with Issue 1.9 taken in 2001 –New IETP category (XML-oriented) –CSDB data modules only in SGML –Transformation to XML for IETP delivery Why XML? –Optional SGML features not needed/utilized –Make CSDB objects usable over the Internet –More widespread use (not only Tech Pubs) –Supported by more and cheaper tools

157 © 2003 TPSMG SGML in Issue 2.0 Retained as CSDB format All textual information objects in SGML –Data modules (wiring + process types are new!) –Publication modules (new!) –Data dispatch notes –Comments (new!) –Data module lists

158 © 2003 TPSMG XML in Issue 2.0 XML DTDs supporting the publication process object types –Publication modules –Data dispatch notes –Comments –Data module lists

159 © 2003 TPSMG XML in Issue 2.0 (contd.) XML Schemas supporting all textual objects –Data modules –Publication modules –Data dispatch notes –Comments –Data module lists XML Schemas 2.0 reflect SGML DTDs

160 © 2003 TPSMG XML in Issue 2.0 (contd.) Arguments for XML Schemas –Schemas are XML instances (same “language”) –Data typing possibilities –Technological trend Potentials for S1000D with XML Schemas –First step in Issue 2.0 taken (1:1 from SGML) –Incorporation of project business rules –Reduction of effort for guidance document / project specific style guides

161 © 2003 TPSMG Generation of IETP XML neutral translation CSDB source data + Xlink + RDF/DC: - - Translate SGML to XML - Add Xlink attributes - Add RDF/DC metadata IETP display transformation XML neutral form + IETP generated data: - -Apply output transformation (XSLT, XSL-FO) - -Resolve URN to URL - Add navigational links - IETP state management Authored source XML or SGML - Data modules - Publication modules CSDB source data files IETP Entities XML + XLink xlink:href with URN IETP neutral repository Rendered IETP XML output spec - CSS/XSL - Hyperlinks (URL) - View in web browser IETP end user display form repository

162 © 2003 TPSMG Resource resolution Location independence of S1000D resources –Data modules and publication modules –Illustrations –Catalog sequence numbers (references to IPD) –Comments URN Namespace registration: S1000D Example for a unique data module web address URN:S1000D:DMC-AE-A … Resource resolution (URN to URL translation)

163 © 2003 TPSMG XML Namespaces Publication module namespace { "@context": "http://schema.org", "@type": "ImageObject", "contentUrl": "http://images.slideplayer.com/3896926/13/slides/slide_162.jpg", "name": "© 2003 TPSMG XML Namespaces Publication module namespace

164 © 2003 TPSMG XML Namespaces (contd.) ddnhttp://www.s1000d.org/ddn dmlhttp://www.s1000d.org/dml commenthttp://www.s1000d.org/comment

165 © 2003 TPSMG Link transformation example Link transformation example Reference to another data module

166 © 2003 TPSMG refdm – SGML CSDB AE A A 040 A A

167 © 2003 TPSMG refdm – XML Repository AE A A 040 A A

168 © 2003 TPSMG refdm – HTML display AE-A A-040A-A

169 © 2003 TPSMG Questions? Peter Zimmermann EADS Military Aircraft D Munich / Germany Phone: Fax: Thanks for your attention

170 © 2003 TPSMG What is ADL? Advanced Distributed Learning DoD initiative Purpose: “Ensure access to high-quality education and training materials that can be tailored to individual learner needs and made available whenever and wherever they are required.”

171 © 2003 TPSMG What is SCORM? Shareable Content Object Reference Model Suite of Standards –Defines Content Aggregation Model –Defines Run Time Environment SCORM defines meta-data to describe reusable content objects SCORM does not define structure of training content objects (ala S1000D DTD)

172 © 2003 TPSMG Content Aggregation Assets are aggregated into Shareable Content Objects which are sequenced and structured into packages that meet specific learning objectives. Asset WAV Asset HTML Fragment Asset GIF Asset XML Doc Asset JavaScript Functions Asset Flash Object Asset JPEG SCO content.htm Api=getAPI(); Var result = api.LMSInitialize(“”); Var val = api.LMSGetValue(cmi.abc.xyz”); Var result = api.LMSFinish(“”); CSF SCO Tagged Content Aggregation Meta-data

173 © 2003 TPSMG S1000D / ADL / AIA MOU Memorandum of Understanding between S1000D, ADL, and AIA –In signature cycle –“The Parties wish to co-ordinate their activities to develop an integrated approach to development and distribution of learning and technical data/information.”

174 © 2003 TPSMG S1000D / ADL / AIA MOU Benefits Position work with respect to other groups Minimize duplication of effort & unintended differences Minimise effort in preparing future Tech Pub and Training objects by improving alignment of technical data with SCORM. Develop standardized linkage between tech data modules and learning information objects Assist the ADL to achieve the Training Transformation Initiative

175 © 2003 TPSMG S1000D / PLCS What is PLCS? –Product Life Cycle Support –Extension to STEP (ISO ) STEP is traditionally focused on engineering and manufacturing PLCS extends STEP to the maintained fleet –Organized by product structure –Model includes maintenance data as well as operational data

176 © 2003 TPSMG S1000D / PLCS Four pillars of PLCS –Configuration Management As-maintained Bill of Material Enhanced master records center/database –Maintenance and Feedback Management and execution of maintenance tasks Maintenance Feedback / Records Maintenance history Configuration changes –Support Engineering Logistical Support Analysis Reliability Centered Maintenance Maintenance Tech pubs and service bulletins –Resource Management Supply Chain, Spares People, skills, tools, facilities

177 © 2003 TPSMG S1000D / PLCS Memorandum of Understanding between S1000D and PLCS –Dated –Established framework of cooperation –Agreed initial work plan –Potential future work

178 © 2003 TPSMG S1000D / PLCS Agreed Initial Work Plan (verbatim) –Initial agreed work program under the Memorandum of Understanding between PLCS and S1000D. –PLCS will review AECMA 1000D Change 9 to: Identify potential gaps in PLCS Requirements Identify a set of PLCS Ref Data which is consistent with S1000D –The Parties will co-operate in developing a process diagram illustrating how the S1000D process would interact with the PLCS Application Activity Model. –PLCS will offer the Data Modules Requirement Statements for Task & Resource and Document Modules for review by S1000D participants. –S1000D will identify volunteer(s) to work with PLCS to develop a common set of requirements for effectivity/applicability management. –S1000D participants will seek to identify and release compliant sample Data Modules from S1000D for use in testing PLCS. –PLCS will investigate and advise how the S1000D Data Module Code breakdown could best be represented in PLCS and to develop appropriate Reference Data. –The Parties will meet to plan a joint campaign to promote awareness of this co- operation and its potential benefits to both communities.

179 © 2003 TPSMG S1000D / PLCS S1000D and PLCS will be able to peacefully co-exist –PLCS will be able to provide the baseline for writing instruction DMs –PLCS will be able to provide configuration data for use in applicability/effectivity –PLCS will be able to interpret S1000D Data Module ID and Status section

180 © 2003 TPSMG Overview What is a publication? –Linear –IETM –S1000D Data Distribution Concepts Summary

181 © 2003 TPSMG Tech Data Structures A weapon system using linear electronic tech pubs (eg 38784)… All Pubs for the materiel Descriptive Information Procedural Information Operator Manual LOAPs Fault Isolation Procedures Etc. Illustrated Parts Data Each pub is a separate, individually configurable object Their primary relationship to each other is that they are associated with the same materiel Linear tech pubs do not require the use of a DB or a logic engine

182 © 2003 TPSMG Tech Data Structures A weapon system using an IETM… A single IETM DB contains all* the technical data associated with the materiel (*with exception of externally referenced data) The entire IETM DB is the smallest* configurable object (*with exception of graphic objects) The logic and presentation engines are separate from the data Presentation Engine Logic Engine Descriptive Information Procedural Information Illustrated Parts Data Fault Isolation Procedures Operator Manuals LOAPs etc.

183 © 2003 TPSMG Tech Data Structures A weapon system using S1000D… Common Source Data Base (CSDB) contains all the technical data associated with the materiel as individual data modules The Data Module is the smallest configurable object allowed by the spec The logic and presentation engines are separate from the data Presentation Engine Logic Engine A pub is a collection of Data Modules

184 © 2003 TPSMG Linear Distribution Concept ETM or Linear Electronic Tech Data Example: This is meant to represent the concept of distributing electronic TO content to an end user (not Paper). It is not meant to represent an actual architectural view. All Pubs for the materiel Descriptive Information Procedural Information Operator Manual LOAPs Fault Isolation Procedures Etc. Illustrated Parts Data RepositoryUser eTool Linear Pub (eg 38784) S1000D (w/out Process Data Module) Entire CSDB CSDB sub-set Individual Pubs TO–2B TO-1A Newly Requested Pubs TO-3C TO–4D Newly Requested Pubs Modules Procedural Information Fault Isolation Procedures TO–4D TO-3C

185 © 2003 TPSMG Linear Distribution Concept ETM or Linear Electronic Tech Data Change Example: This is meant to represent the concept of distributing electronic TO content to an end user (not Paper). It is not meant to represent an actual architectural view. All TOs for the materiel Descriptive Information Procedural Information Operator Manual LOAPs Fault Isolation Procedures Etc. Illustrated Parts Data RepositoryUser eTool Entire CSDB CSDB sub-set TO–4D TO-3C Individual Pubs TO–2B TO-1A Operator Manual Illustrated Parts Data TO–2B TO-1A Changed data TO–2B – change 001 TO-1A – change 001 Linear Pub (eg 38784) S1000D (w/out Process Data Module)

186 © 2003 TPSMG IETM Distribution Concept IETM or Non-Linear Tech Data Example: Repository User eTool Entire IETM DB S1000D (w/ Process Data Module) This is meant to represent the concept of distributing IETM TO content to an end user. It is not meant to represent an actual architectural view. CSDB sub-set Entire CSDB Newly Requested Pubs Modules Entire IETM DB No standard for distributing IETM sub-sets

187 © 2003 TPSMG IETM Distribution Concept IETM or Non-Linear Tech Data Change Example: Repository User eTool Entire IETM DB This is meant to represent the concept of distributing IETM TO content to an end user. It is not meant to represent an actual architectural view. CSDB sub-set Entire CSDB Changed data No standard for distributing IETM sub-set changes Entire IETM DB S1000D (w/ Process Data Module)

188 © 2003 TPSMG Summary S1000D has discrete data modules with well- defined metadata This allows for more granular configuration management This enables the development of architectures and support process that can handle linear and non-linear data in a consistent and standard manner

189 © 2003 TPSMG What will happen next? Svante Ericsson, Chairman EPWG Sörman I&M, Sweden

190 © 2003 TPSMG Ongoing development To pick some: Consolidated use of XML Support of multimedia objects Mechanism for formalized exchange of business rules Interactivity further developed (US EPWG meeting Tuesday!) Enrichment of online data dictionaries

191 © 2003 TPSMG Thanks again! Questions?

192 © 2003 TPSMG


Download ppt "© 2003 TPSMG S1000D Tutorial Compressed introduction to the Spec AIA/Tri-Service 2004 Publications Workshop San Antonio, TX 2004-02-09."

Similar presentations


Ads by Google