S1000D User Forum 2003

1. S1000D User Forum 2003 CORENA NORGE AS Applicability Management An integrator’s considerations 1-2 October 2003 By: Toralf Johannessen Managing Director Title Field

2. Agenda • About CORENA (max 30 seconds) • The purpose of applicability and its consequences • The OEM’s source data • Applicability at DM top level • In-line applicability in DMs • The IETM • Methods of utilization • Different approaches to applicability management • Applicability assignment • By serial numbers • By labels and logical expressions Title Field

3. CORENA offices CORENA HOLDING A/S Employees: ~180 Represtented in 9 countries Temasek 32% 50% 20% 25% GN Resources International (CZ) A.S CORENA DANMARK A/S CORENA DEUTCHLAND GmbH CORENA NORGE AS Bysted HQ A/S ASPrecise.com Pte Ltd. CORENA USA Inc. CORENA USA Inc. GN Resources International (SK) A.S Title Field

4. Engines Qualifying References Aerospace, Defense & Aviation Rolls-Royce Airlines, UK Rolls-Royce Defence, UK Rolls-Royce Deutschland, DE Rolls-Royce Indianapolis, US Rolls-Royce Aero Repair and Overhaul Value chain efficiency Manufactures Operators Title Field

5. Purpose of applicability • The purpose of applicability management is twofold: • On the OEM’s side: • Establish relation between configuration of equipment and relevant documentation • Applicability provides a means for obtaining a larger degree of data reuse accross the different material configurations, and thereby a reduction of the total amount of DataModules required in a project. • On the operators side: • Applicability provides possibilities for customized presentation of IETM content based on ”tailnumber” filtering. Title Field

6. change change change Xxxxxxxxx ZZZZZZ xxxxxxxxxxxxxxxxxxxxxx Xxxxxxxxx ZZZZZZ xxxxxxxxxxxxxxxxxxxxxx 2. Xxxx ZZZZZZZ xxxxx xxxxx xxxx xxxxxxx xxxx xx 2. Yyyy yyyy yyyyy yyy yyyyyyy ZZZZZZZ yyyyyy yyy yyyyy ISSUE 3 ISSUE 2 ISSUE 2 ISSUE 3 The OEM’s source data Applicability on DM level ALL ALL xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ALL 1.xxxxxxxx xxxxxxx xxx xx xxxx xxxxxxxx xxx ALL 1.xxxxxxxx xxxxxxx xxx xx xxxx xxxxxxxx xxx ALL BUT B & C 2. Yyyy yyyy yyyyy yyy yyyyyyy yyyy yyy yyyyyy yyy yyyyy 2. Xxxxxxxx xx xxxxx xxxxx xxxx xxxxxxx xxxx xx B & C ONLY ALL ALL 3. Xxxx xxxxxxx 3. Xxxx xxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ALL ALL ISSUE 1 ISSUE 1 Title Field

7. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx PUBLISH FORALL BUT B & C 1.xxxxxxxx xxxxxxx xxx xx xxxx xxxxxxxx xxx 2. Yyyy yyyy yyyyy yyy yyyyy yyyy yyyy yyy yyyyy 2. Yyyy yyyy yyyyy yyy yyyyyZZZZZZZyyyy yyy yyyyy xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2. Xxxx ZZZZZZZxxxxx xxxxx xxxx xxxxxxx xxxx xx 3. Xxxx xxxxxxx 1.xxxxxxxx xxxxxxx xxx xx xxxx xxxxxxxx xxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2. Yyyy yyyy yyyyy yyy yyyyyZZZZZZZyyyy yyy yyyyy 2. XxxxZZZZZZZxxxxx xxxxx xxxx xxxxxxx xxxx xx 2. Xxxx xxxxxxx xxxxx xxxxx xxxx xxxxxxx xxxx xx ISSUE 1 ISSUE 2 3. Xxxx xxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx PUBLISH FOR B & C ONLY ISSUE 2 ISSUE 3 ISSUE 2 ISSUE 1 The OEM’s source data • In-line applicability ALL xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ALL 1.xxxxxxxx xxxxxxx xxx xx xxxx xxxxxxxx xxx 2. Xxxx xxxxxxx xxxxx xxxxx xxxx xxxxxxx xxxx xx B & C ONLY 2. Yyyy yyyy yyyyy yyy yyyyy yyyy yyyy yyy yyyyy ALL BUT B & C ALL 3. Xxxx xxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ALL ISSUE 1 Title Field

8. The IETM • Approaches: • One IETM per material/system configuration • Inappropriate for larger series with variations • One IETM per set of material/system configurations • If the viewer has no applicability support the reader must filter the information himself – safety issue? • Viewer with applicability support – probably best solution but demands more ”complex” viewer. Title Field

9. Applicability Assignment • To assist the authors and ensure assignment of only legal values the authoring environment must be integrated with the configuration database. CONFIGURATION DATABASE XML/SOAP Title Field

10. Applicability Assignment • Assignment by • Serial numbers: • Extreme demand on the authors: need to know serial-number/ options/mods/sb-status • Extreme consequences when introducing a new serial-number: New issue number of a vaste amount of DMs. • Less demands for complex software – the hard work and the responsibilities are with the authors Title Field

11. Applicability Assignment • Assignment by • Logic Expressions: • Demands more functional and complex software • Increases the reuse of DMs. • Great help for authors. • Logic expressions automatically converted to the customers’ serial numbers during publishing. Title Field

12. Applicability Logic Principles used to describe logical combination of modifications and Service Bulletins. Title Field

13. Change Drivers Label Constructor AND NOT OR LOGIC EXPRESSIONS & LABELS Customer Selection Resulting Effectivity Author Applicability Assignment Proposed further refinement: Title Field

14. Label Authors pick-list Type B air conditioning Logic Expression Mod123 AND [(Pre SB S1 OR Pre SB S2) AND Post SB S3] Constructors view On A/C 101,102,103, 106-110 and on A/C 111 Pre SB S1 Resolved Effectivity End users applicability Applicability Abstraction Title Field

15. Applicability Software Requirements • Label Editor • Build Logic Expressions • Full History Tracking • on configuration data • on resolved applicability labels per customer • on customized /delivered Data Modules • Automatic Creation of Revision Markings • Reason for Change • Issue no and DM status • Applicability Resolving Title Field

16. Applicability Conclusion • Is the S1000D DTD structure for applicability sufficient? For the IETM : <!ELEMENT applic - O (type?,model?) > For the OEM : <!ELEMENT applic - O (label?, type?,model?) > Title Field

17. Contact www.corena.com • S1000D Introduction course for project leaders and authors • Products (CSDB & IETM) • Integrated solutions (LSAR, S2000M) • Services sales@corena.no Title Field